
From ietf@augustcellars.com  Sat Jun  1 09:21:16 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4115E21F9C63 for <jose@ietfa.amsl.com>; Sat,  1 Jun 2013 09:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fID2+Ju-Xd47 for <jose@ietfa.amsl.com>; Sat,  1 Jun 2013 09:21:07 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id DD2A021F9C88 for <jose@ietf.org>; Sat,  1 Jun 2013 09:21:06 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id F16412CA08; Sat,  1 Jun 2013 09:21:04 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-use-cases@tools.ietf.org>
Date: Sat, 1 Jun 2013 09:20:15 -0700
Message-ID: <002d01ce5ee3$e6a1beb0$b3e53c10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01CE5EA9.3A43AA00"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5eWthtGlW95v3WS1+ZAltJBFFmYw==
Content-Language: en-us
Cc: jose@ietf.org
Subject: [jose] Comments on draft-ietf-jose-use-cases-02
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 01 Jun 2013 16:21:16 -0000

This is a multipart message in MIME format.

------=_NextPart_000_002E_01CE5EA9.3A43AA00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Richard,

 

Here is my review 

 

1.  I think you should include the abbreviations for CMS and JSON following
the full strings in the abstract

 

2.  Introduction-  Para #1 - You should not assume that people are going to
recognize RFC numbers, esp. as they change over time.  Please insert the
names of the protocols as well as the references for 4301 and 5246.

 

3. Introduction - Para #2 - Please insert a protocol name along with RFC3207
- i.e. STARTTLS

 

4.  The X.609 reference should be updated to the 2002 version  It is the
most current version

 

5.  Introduction - Para #3 - please move the XML reference next to the XML
text.  It currently appears that the XML reference applies to JSON

 

6.  Section #2 - s/JSON Web Algorithms (JWS)/JSON Web Algorithms (JWA)/

 

7.  Section 3 - bullet #3 - s/receiver share only a/receiver share a/

 

8.  Section 3 - The following sentence appears to be missing some words or
punctuation

 
vvvvvv

                However, in order to avoid confusing endpoints that lack the
necessary context need to be able to recognize this and fail cleanly.

 

9.  Section 5.2 -  I have two comments in this section

                a) I don't understand the need for integrity protection from
modifications from the resource owner - it is what is granting the
permissions to start with

                b) You might want to note that using TLS does not protect
confidentiality from the resource owner and client.

 

10.  Section 5.4 - Is Alice sending the message to (Bob) or (B)?

 

11.  Section 5.5 - There was also a discussion in the case of ALTO if the
content should be encoded separately from the integrity (detached content).
Thus the JSON would be carried in the HTTPS header and the body would be the
HTTPS content.

 

12.  Section 5.6 - What is a channel-based digital signature mechanism?

 

13.  Section 5.6 - The document does not say if nested signatures are
sufficient to satisfy the requirement - or if parallel signatures are
required.

 

 

Jim

 


------=_NextPart_000_002E_01CE5EA9.3A43AA00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:659235268;
	mso-list-type:hybrid;
	mso-list-template-ids:-1833894206 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoPlainText>Richard,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Here =
is my review <o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>1.&nbsp; I think you should include the =
abbreviations for CMS and JSON following the full strings in the =
abstract<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>2.&nbsp; Introduction-&nbsp; Para #1 - You should =
not assume that people are going to recognize RFC numbers, esp. as they =
change over time. &nbsp;Please insert the names of the protocols as well =
as the references for 4301 and 5246.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>3. =
Introduction - Para #2 - Please insert a protocol name along with =
RFC3207 - i.e. STARTTLS<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>4.&nbsp; The X.609 reference should be updated to =
the 2002 version&nbsp; It is the most current version<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>5.&nbsp; Introduction - Para #3 - please move the =
XML reference next to the XML text.&nbsp; It currently appears that the =
XML reference applies to JSON<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>6.&nbsp; Section #2 - s/JSON Web Algorithms =
(JWS)/JSON Web Algorithms (JWA)/<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>7.&nbsp; Section 3 - bullet #3 - s/receiver share =
only a/receiver share a/<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>8.&nbsp; Section 3 - The following sentence appears =
to be missing some words or punctuation<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
vvvvvv<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; However, in order to avoid =
confusing endpoints that lack the necessary context need to be able to =
recognize this and fail cleanly.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>9.&nbsp; Section 5.2 -&nbsp; I have two comments in =
this section<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) I don&#8217;t understand the =
need for integrity protection from modifications from the resource owner =
&#8211; it is what is granting the permissions to start =
with<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) You might want to note that =
using TLS does not protect confidentiality from the resource owner and =
client.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>10.&nbsp; Section 5.4 &#8211; Is Alice sending the =
message to (Bob) or (B)?<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>11.&nbsp; Section 5.5 &#8211; There was also a =
discussion in the case of ALTO if the content should be encoded =
separately from the integrity (detached content).&nbsp; Thus the JSON =
would be carried in the HTTPS header and the body would be the HTTPS =
content.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>12.&nbsp; Section 5.6 &#8211; What is a =
channel-based digital signature mechanism?<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>13.&nbsp; Section 5.6 &#8211; The document does not =
say if nested signatures are sufficient to satisfy the requirement =
&#8211; or if parallel signatures are required.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Jim<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_002E_01CE5EA9.3A43AA00--


From ludwig@sics.se  Mon Jun  3 01:19:43 2013
Return-Path: <ludwig@sics.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC0A321F93FB for <jose@ietfa.amsl.com>; Mon,  3 Jun 2013 01:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPVQzOwZOA7b for <jose@ietfa.amsl.com>; Mon,  3 Jun 2013 01:18:22 -0700 (PDT)
Received: from fsmsg2.sics.se (fsmsg2.sics.se [IPv6:2001:6b0:3a:1:250:56ff:fea9:52ad]) by ietfa.amsl.com (Postfix) with ESMTP id 21DBF21F93D4 for <jose@ietf.org>; Mon,  3 Jun 2013 01:18:17 -0700 (PDT)
Received: from pps.filterd (fsmsg2 [127.0.0.1]) by fsmsg2.sics.se (8.14.5/8.14.5) with SMTP id r538GJOK011591 for <jose@ietf.org>; Mon, 3 Jun 2013 10:18:15 +0200
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by fsmsg2.sics.se with ESMTP id 1cr4a19376-1 for <jose@ietf.org>; Mon, 03 Jun 2013 10:18:15 +0200
Received: from [192.168.1.135] (15.90.11.37.dynamic.jazztel.es [37.11.90.15]) (Authenticated sender: ludwig@sics.se) by letter.sics.se (Postfix) with ESMTPSA id DEDDC400E2 for <jose@ietf.org>; Mon,  3 Jun 2013 10:18:14 +0200 (CEST)
Message-ID: <1370247493.16652.6.camel@ubuntu.ubuntu-domain>
From: Ludwig Seitz <ludwig@sics.se>
To: "jose@ietf.org" <jose@ietf.org>
Date: Mon, 03 Jun 2013 10:18:13 +0200
Organization: SICS AB
Content-Type: multipart/signed; micalg="sha256"; protocol="application/x-pkcs7-signature"; boundary="=-PhPFr7BpTMOCaYMcKBhD"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Mime-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-06-03_02:2013-06-03, 2013-06-03, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1211240000 definitions=main-1306030016
Subject: Re: [jose] Dealing with Issue #8 - Direct mode for key agreement
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Jun 2013 08:19:44 -0000

--=-PhPFr7BpTMOCaYMcKBhD
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Mike and Jim,

I'll gladly look at the small devices use case and write something about
my own case, however I'm on a conference this week, so please be
patient.

Would you prefer that I extend the existing small devices use-case
(which seems very specific and narrow to me on a casual glance) or
should I create a new section?

/Ludwig

--=20
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2=20
Scheelev=C3=A4gen 17=20
SE-223 70 Lund

Phone +46(0)70-349 92 51
http://www.sics.se

--=-PhPFr7BpTMOCaYMcKBhD
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEnAw
ggYYMIIFAKADAgECAgMFtYswDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQTAeFw0xMzAxMTUwMjA1MDZaFw0xNDAxMTUxNDM3NDhaMDgxFzAVBgNVBAMMDmx1ZHdpZ0Bz
aWNzLnNlMR0wGwYJKoZIhvcNAQkBFg5sdWR3aWdAc2ljcy5zZTCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBAKpuRavr2swCQsYS7KxOsmeBXI39thxAjIYaB0AFVjLpOtVJxQMYoip7Bm9o
ka8PXxQ9mWT/lVSoqI7jGjc5Z8q1C4fOFMCYZpJugG9qJS0OMV2ajQ7xXu3YzLTDIKg/BK39+Vri
vJq0Y6hz1/4pgxMOFG+l7y+fq54QSkKMwpuRaCBznKJeRxGwDvheF2QN6YEBclFqVhpciDGd52vX
5AgbKbqVmevMrcrcYAdKaKm6iTEmbYHum5D/4GaOnnZ2wMnY5EpKhxxm6SszCVSNdk8iZSUze9GY
PzheBDIHMDdLZib6zaoR96F5ZCpE1pPeKIz/DCd3kL+nXpe5gdbSXLsCAwEAAaOCAtQwggLQMAkG
A1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQUwDv6gyc7uSHK/QBVIZiN86hjKW4wHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4
UYIwGQYDVR0RBBIwEIEObHVkd2lnQHNpY3Muc2UwggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQB
gbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBk
ZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIB
ARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEg
VmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFu
Y2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVs
eWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZo
dHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYD
VR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBCwUAA4IBAQA4bagj
yL3PLei2tbMELKOVOxRdyLObcVq0Fj83LbSTMj6NS83TU/4xxChfd5zqoipudDSEpgxZAUsSjk02
DxSeLYYBXE2X/iue7nL8S/3PjC49z5ZgjDZrXIgmvIMaZXWM+GqG+wk9NikGb1/shlJjk3R5KC3f
RWsUatHouNxAMYxiLFO75YmgKCgkjtKUbHbUqzmDVd30nWQesXfCgYwCbAvD/0NgX3jE+fnyT71+
aX4/IfqshpCQj8dkR4ZH+bUiK5zgKGJL61GRZNSScR/r9Sq19kEQrt38ey/Q90tUDUgg93d5w3DN
rF3bRoOvyspwbcN9TuGKkFoFPV0KfjaGMIIGGDCCBQCgAwIBAgIDBbWLMA0GCSqGSIb3DQEBCwUA
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl
IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ
cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwMTE1MDIwNTA2WhcNMTQwMTE1MTQz
NzQ4WjA4MRcwFQYDVQQDDA5sdWR3aWdAc2ljcy5zZTEdMBsGCSqGSIb3DQEJARYObHVkd2lnQHNp
Y3Muc2UwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCqbkWr69rMAkLGEuysTrJngVyN
/bYcQIyGGgdABVYy6TrVScUDGKIqewZvaJGvD18UPZlk/5VUqKiO4xo3OWfKtQuHzhTAmGaSboBv
aiUtDjFdmo0O8V7t2My0wyCoPwSt/fla4ryatGOoc9f+KYMTDhRvpe8vn6ueEEpCjMKbkWggc5yi
XkcRsA74XhdkDemBAXJRalYaXIgxnedr1+QIGym6lZnrzK3K3GAHSmipuokxJm2B7puQ/+Bmjp52
dsDJ2ORKSoccZukrMwlUjXZPImUlM3vRmD84XgQyBzA3S2Ym+s2qEfeheWQqRNaT3iiM/wwnd5C/
p16XuYHW0ly7AgMBAAGjggLUMIIC0DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAU
BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFMA7+oMnO7khyv0AVSGYjfOoYyluMB8GA1Ud
IwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGCMBkGA1UdEQQSMBCBDmx1ZHdpZ0BzaWNzLnNlMIIB
TAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQg
YWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBT
dGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3Nl
IGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUF
BwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3Mx
L2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3Vi
LmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
LzANBgkqhkiG9w0BAQsFAAOCAQEAOG2oI8i9zy3otrWzBCyjlTsUXcizm3FatBY/Ny20kzI+jUvN
01P+McQoX3ec6qIqbnQ0hKYMWQFLEo5NNg8Uni2GAVxNl/4rnu5y/Ev9z4wuPc+WYIw2a1yIJryD
GmV1jPhqhvsJPTYpBm9f7IZSY5N0eSgt30VrFGrR6LjcQDGMYixTu+WJoCgoJI7SlGx21Ks5g1Xd
9J1kHrF3woGMAmwLw/9DYF94xPn58k+9fml+PyH6rIaQkI/HZEeGR/m1Iiuc4ChiS+tRkWTUknEf
6/UqtfZBEK7d/Hsv0PdLVA1IIPd3ecNwzaxd20aDr8rKcG3DfU7hipBaBT1dCn42hjCCBjQwggQc
oAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNV
BAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3
MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENv
bSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xC
GhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P
3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2Ub
FqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2
JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGp
MA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6W
NU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3Rh
cnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhj
jF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4
n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkU
CTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6h
xHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5X
MEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b
1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLp
XDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/p
Ny8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOg
SF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEw
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCWCGSAFlAwQCAQUAoIIBuzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MDMwODE4MTNaMC8G
CSqGSIb3DQEJBDEiBCCtG3JxZ+knoADoqNy60XTiZoKeVa/Yl3S+70w3Rvrc8DCBpQYJKwYBBAGC
NxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwW1izCBpwYLKoZIhvcNAQkQ
AgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCSqGSIb3DQEBAQUA
BIIBAEfzTmYZ2QL8p3XT4UWU36U2xfY1YNdiULN88WIT91dhgZEZ1compTm4orGUaZX1hgfBGULC
mT0fdMuSaE4JiG7AexUFRmhzGbQGKkDM08GZCeMGwhcCKFswto5KpE0UCfykIsITWCJ3bCRwX1Py
xxNV7DevVBdissvBm6GMi1OHJohllRyiNge61knzvpicA0F2nf9sjnD8CMRuQI4loBSuvIMU8Jfr
28zzAV1QtYcR4E5HeVWW5lEvD5gcPqJy/kWfhc+Eu4M14wJnf0RyznaMzgFKnYT1zUgd8ngo2Ed5
5BnfYi9Z5xJyQ3KA0UAtGGKn5hy6t1F425DERa3sLWAAAAAAAAA=


--=-PhPFr7BpTMOCaYMcKBhD--


From rlb@ipv.sx  Tue Jun  4 10:20:47 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C3D621F9CD0 for <jose@ietfa.amsl.com>; Tue,  4 Jun 2013 10:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.178
X-Spam-Level: **
X-Spam-Status: No, score=2.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lbp2+h4Ut0te for <jose@ietfa.amsl.com>; Tue,  4 Jun 2013 10:20:43 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 9B89821E80A4 for <jose@ietf.org>; Tue,  4 Jun 2013 08:28:58 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so614876obq.35 for <jose@ietf.org>; Tue, 04 Jun 2013 08:28:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=IiNpoxc81Z3ujJMRIRBN7YCMqnrqEYTJWx3V+RnP9oU=; b=gAGAHJG86sL/6ozmyN98sR9J7TO61H9B7fCgLVi1lm80OHFVkDvBNX1BXAsti2ZzS8 WJFoSTI3p+POL2NQsVGQNQGTvdW07YAmIROBGYT4wxwN40W9KYdjuP+2Pjy451eQQNlC r8obV2/zaufhGIicKxQSY7Kbb7oVuQ9viRtCK6bnYYdFN8momfqcxjqMg6Rp8wwduPyE 53aK8Of7uA6Jahz2XTF7+2MpnEg8FK/5kLIPxmnfypJ76+sk1q+EJz4lAQPhpXmpIHNU VskohcUZJAoyQCwId44OxilNRvPcrRiGoVlURx52QGaEN24phySs+Pq5hMvR8XT7EIAm mzIg==
MIME-Version: 1.0
X-Received: by 10.182.236.104 with SMTP id ut8mr12169879obc.75.1370359738010;  Tue, 04 Jun 2013 08:28:58 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 4 Jun 2013 08:28:57 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com>
Date: Tue, 4 Jun 2013 11:28:57 -0400
Message-ID: <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Brian Campbell <bcampbell@pingidentity.com>
Content-Type: multipart/alternative; boundary=001a11c3183866707c04de55bdd9
X-Gm-Message-State: ALoCoQmeYX8Cz852Y2P70vUcYtKGWhdI72prGRVY5ofn91qRo/1LqiDohi3TXga7GJOhb+IVrPZh
Cc: Mike Jones <Michael.Jones@microsoft.com>, Nat Sakimura <sakimura@gmail.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 04 Jun 2013 17:20:47 -0000

--001a11c3183866707c04de55bdd9
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It would be a good point, if it were true :)  In particular, this part:
"[dropping 'typ'] is going to cause each and every application that uses
JOSE to define their own field"

So far, I've heard of exactly one application of JOSE that requires "typ"
in the way it is currently specified, namely JWT.

On the other hand, Dick's applications are apparently using it differently
(and, IMO, properly) to distinguish JWE/JWS.  Then there are all the
applications out there that are OK using application context and "cty" to
recognize what type of object they have.  Apps using CMS have been doing
this for ages.

So it's not at all clear to me that there's any other application that
would use "typ" besides JWT.  And it's not clear to me that JWT needs it.

--Richard





On Fri, May 31, 2013 at 5:45 PM, Brian Campbell
<bcampbell@pingidentity.com>wrote:

> Nat makes a good point here, I think.
>
>
> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com> wrote:
>
>> From what I understand, both typ and cty are something to be consumed by
>> the application and not JOSE processor. From the point of view of the JO=
SE
>> processor, they should be ignored.
>>
>> We could drop both fields from JOSE specs, but that is going to cause
>> each and every application that uses JOSE to define their own field, whi=
ch
>> is a waste. That is why we are defining them here.
>>
>> I would rather drop them than define JOSE processing semantics to these
>> fields.
>>
>>
>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>
>>>  No, =93cty=94 is used by the derived class to determine the type of th=
e
>>> encapsulated field.  But that=92s not a complete description of the **e=
ntire
>>> object** - especially not the additional meaning imbued by the
>>> additional parameters the derived type may add to the JOSE header.  =93=
typ=94
>>> is there to provide the type of the entire object, including what you=
=92re
>>> calling the wrapper parts.****
>>>
>>> ** **
>>>
>>>                                                             -- Mike****
>>>
>>> ** **
>>>
>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>
>>> *To:* Mike Jones
>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>> ** **
>>>
>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is a
>>> crypto wrapper around the real application content.  If you're an
>>> application, you know a JOSE object is the thing you want because it
>>> contains the content you want -- it's a JWT because it contains JWT cla=
ims.
>>> ****
>>>
>>> ** **
>>>
>>> Inheritance is the wrong metaphor.  This is encapsulation of applicatio=
n
>>> data:****
>>>
>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>
>>>     jwtClaims =3D jws.content;****
>>>
>>> }****
>>>
>>> ** **
>>>
>>> --Richard****
>>>
>>> ** **
>>>
>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>> Michael.Jones@microsoft.com> wrote:****
>>>
>>> Thanks for sharing the S/MIME details.  Although I was actually making
>>> the analogy to MIME =96 not S/MIME.  Like many analogies, it=92s imperf=
ect, but
>>> I believe still illustrative.****
>>>
>>>  ****
>>>
>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>> structures are used to build application-specific data structures that =
are
>>> legal JOSE data structures but also have additional properties =96 incl=
uding
>>> additional header fields with specific semantics.  (When we agreed to
>>> ignore not-understood header fields we let that horse out of the barn.)
>>> For instance, Dick Hardt uses JWEs with issuer and audience fields in t=
he
>>> headers, so they can be used by routing software.****
>>>
>>>  ****
>>>
>>> Think of JOSE as the base class and the application types built using i=
t
>>> as derived classes.  JWT is a derived class.  Dick=92s structures are a
>>> derived class.  These derived classes sometimes need names.  That=92s w=
hat
>>> =93typ=94 is for.****
>>>
>>>  ****
>>>
>>>                                                             -- Mike****
>>>
>>>  ****
>>>
>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>
>>>
>>> *To:* Mike Jones
>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>>  ****
>>>
>>> You're mixing up "typ" and "cty".  If you want to make the analogy to
>>> S/MIME, "cty" is the equivalent to Content-Type inside the protected MI=
ME
>>> body; "typ" is the content-type on the outer MIME header.  Pasting in a=
n
>>> example:****
>>>
>>>  ****
>>>
>>> -----BEGIN-----****
>>>
>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>>>
>>>      name=3Dsmime.p7m****
>>>
>>> Content-Transfer-Encoding: base64****
>>>
>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>
>>>  ****
>>>
>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>
>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>
>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>
>>> 6YT64V0GhIGfHfQbnj75****
>>>
>>> -----END-----****
>>>
>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>
>>>  ****
>>>
>>> The outer Content-Type, which is analogous to "typ", MUST be
>>> application/pkcs7-mime, with a parameter indicating the type of CMS obj=
ect.
>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>> Content-Type (ASN.1/base64 encoded in the example) can be anything, jus=
t
>>> like "cty".****
>>>
>>>  ****
>>>
>>> --Richard****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>> Michael.Jones@microsoft.com> wrote:****
>>>
>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 would=
 be analogous
>>> to the MIME spec requiring that the Content-Type: field be only
>>> =93text/plain=94 or =93message/external-body=94.  It would render it us=
eless.***
>>> *
>>>
>>>  ****
>>>
>>>                                                             -- Mike****
>>>
>>>  ****
>>>
>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
>>> Of *Richard Barnes
>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>> *To:* Mike Jones
>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>
>>>
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>>  ****
>>>
>>> If this is the level of "type" you're referring to, I think we should
>>> drop it from the spec.  It's an application-layer thing that the app ca=
n
>>> add or not according to its wishes.****
>>>
>>>  ****
>>>
>>> I'm with Dick on this.  I think we should either have a mandatory
>>> indicator of what type of JOSE object this, or nothing at all.   If the
>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" options =
are
>>> non-sensical -- the app needs to know what it's parsing before it gets =
this
>>> header.  While I have a preference for the former (for clarity), the la=
tter
>>> approach is also OK with me, since the MIME types are specific to JWE/J=
WS.
>>> ****
>>>
>>>  ****
>>>
>>> Another approach here would be to address the JSON and compact forms
>>> separately.  The JSON form has no need of "typ" at all, since the type =
of
>>> the object is completely clear from what fields are there, e.g.,
>>> "recipients" vs. "signatures".  For the compact form, we could do somet=
hing
>>> like James's "E."/"S." prefix idea, which you need because the
>>> dot-separated components have different meanings and no field names to
>>> indicate this.****
>>>
>>>  ****
>>>
>>> --Richard****
>>>
>>>  ****
>>>
>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <Michael.Jones@microsoft.co=
m>
>>> wrote:****
>>>
>>> A standard library is unlikely to know the meanings of all possible
>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*.  It=
=92s the
>>> application=92s job to determine that =93this blob is a JOSE object=94 =
and then
>>> pass it to a standard library, which will then ignore the =93typ=94 val=
ue.**
>>> **
>>>
>>>  ****
>>>
>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 means.  =
It won=92t
>>> know what =93typ=94: =93BCGovToken=94 is, should the BC Government want=
 to declare
>>> that it=92s using a token with particular characteristics.  It won=92t =
know
>>> what =93typ=94: =93XMPP=94 is, should XMPP want to declare that it=92s =
using a JOSE
>>> data structure with particular characteristics.  Etc.****
>>>
>>>  ****
>>>
>>> All these values can be registered in the registry and used by
>>> applications that understand them.  That=92s the application=92s job =
=96 not the
>>> library=92s job.  The =93typ=94 field is just there so that application=
s have a
>>> standard place to make any such declarations that they may need.****
>>>
>>>  ****
>>>
>>>                                                                 -- Mike=
*
>>> ***
>>>
>>>  ****
>>>
>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>> *To:* Mike Jones
>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>
>>>
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>>  ****
>>>
>>> I'd prefer to be able to use standard libraries for creating and parsin=
g
>>> tokens, and not specialized libraries dependent on the use case.****
>>>
>>>  ****
>>>
>>> I strongly think we either drop "typ" or make it required.****
>>>
>>>  ****
>>>
>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <Michael.Jones@microsoft.co=
m>
>>> wrote:****
>>>
>>> It=92s fine for your application to specify that it=92s required for yo=
ur
>>> use case.  Not applications need it, so they shouldn=92t be forced to p=
ay the
>>> space penalty of an unnecessary field.****
>>>
>>>  ****
>>>
>>>                                                                 -- Mike=
*
>>> ***
>>>
>>>  ****
>>>
>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
>>> Of *Dick Hardt
>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>
>>>
>>> *To:* Jim Schaad
>>> *Cc:* jose@ietf.org
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>>  ****
>>>
>>> I use it all the time and my code would barf if it was not there.****
>>>
>>>  ****
>>>
>>> I think it should be required rather than be a hint if it is going ot b=
e
>>> there.****
>>>
>>>  ****
>>>
>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com>
>>> wrote:****
>>>
>>> I think the values just changed****
>>>
>>>  ****
>>>
>>> However the way you are using it would be an argument to say that it
>>> should be a required field.  Are you just using it as a hint if it exis=
ts
>>> and then looking at the rest of the fields if it is not present?****
>>>
>>>  ****
>>>
>>> Jim****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>> *To:* Jim Schaad
>>> *Cc:* jose@ietf.org
>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>
>>>  ****
>>>
>>> Well, I have been using, but now realize the spec changed or I was
>>> confused.****
>>>
>>>  ****
>>>
>>> I had been setting "typ" to be either "JWE" or "JWS" depending on the
>>> type of token I was creating or parsing as it was easier than looking a=
t
>>> "alg"****
>>>
>>>  ****
>>>
>>> As currently defined, I don't see value in "typ".****
>>>
>>>  ****
>>>
>>> -- Dick****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com>
>>> wrote:****
>>>
>>> In reading the documents, I am trying to understand the justification
>>> for having the =93typ=94 header parameter in the JOSE documents.****
>>>
>>>  ****
>>>
>>> The purpose of the field is to hold the type of the object.  In the
>>> past, I believe that values which should now be placed in the cty field
>>> (such as =93JWT=94) were placed in this field as well.  However the par=
ameter
>>> is optional and an implementation cannot rely on its being present.  Th=
is
>>> means that for all practical purposes all of the code to determine the
>>> value of the type field from the values of the alg and enc fields.  If =
the
>>> field was mandatory then this code would disappear at a fairly small sp=
ace
>>> cost and I can understand why the parameter would be present.****
>>>
>>>  ****
>>>
>>> Can anybody justify why this field should be present in the document =
=96
>>> or should it just disappear?****
>>>
>>>  ****
>>>
>>> Jim****
>>>
>>>  ****
>>>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose****
>>>
>>>
>>>
>>> ****
>>>
>>>  ****
>>>
>>> --
>>> -- Dick ****
>>>
>>>
>>>
>>> ****
>>>
>>>  ****
>>>
>>> --
>>> -- Dick ****
>>>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose****
>>>
>>>
>>>
>>> ****
>>>
>>>  ****
>>>
>>> --
>>> -- Dick ****
>>>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose****
>>>
>>>  ****
>>>
>>>  ****
>>>
>>> ** **
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>
>>
>> --
>> Nat Sakimura (=3Dnat)
>> Chairman, OpenID Foundation
>> http://nat.sakimura.org/
>> @_nat_en
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>

--001a11c3183866707c04de55bdd9
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It would be a good point, if it were true :) =A0In particu=
lar, this part: &quot;[dropping &#39;typ&#39;]<span style=3D"color:rgb(80,0=
,80);font-family:arial,sans-serif;font-size:13px">=A0is going to cause each=
 and every application that uses JOSE to define their own field</span>&quot=
;<div>
<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>
<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><div><br></div><div>--Richard</=
div>
<div><br></div><div><br><div><br></div></div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Fri, May 31, 2013 at 5:45 PM, Bria=
n Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:bcampbell@pingidentity.c=
om" target=3D"_blank">bcampbell@pingidentity.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"g=
mail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>


<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>




<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>




<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>




</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>




</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>




<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>




</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>



</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a11c3183866707c04de55bdd9--

From rlb@ipv.sx  Tue Jun  4 10:23:07 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C55921F9C38 for <jose@ietfa.amsl.com>; Tue,  4 Jun 2013 10:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.226
X-Spam-Level: 
X-Spam-Status: No, score=0.226 tagged_above=-999 required=5 tests=[AWL=0.651,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nkKIAFTc3Uo for <jose@ietfa.amsl.com>; Tue,  4 Jun 2013 10:23:03 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 73A4421F9B35 for <jose@ietf.org>; Tue,  4 Jun 2013 08:37:09 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id 16so633977obc.26 for <jose@ietf.org>; Tue, 04 Jun 2013 08:37:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=LU0PM5D5UglP2g0QMsasgSUwxWB4NKBDvHqG5HI1A3U=; b=CW25X2xSprBnQ1NIVOU2hsZqCTi4Ju/f0Uduqql5vkHT9ABUMEyaJjl1Y3Z72gnWwG RsJJED1xYX2PspfYI8FflEm45JGuo/xQ9M/+6CZH+KMzUjCsSJBumMxWt98ZCZSDJTRV i6o17GqFamqWg1NsV+CDYBPkyT5Coy9m+15+SQhleb6oyHkuPYJ1ynRu4H7e4hEFsZBs zspn6KLSUxuUem+mgGLNAkTAAEKRpU7iq3+l+EEagnZb9El49480bzYn8MlsAmflX0Ri HChnfUlhNvc1AnUts+jZgD5qYlUvyBq81c69Pt3DF4mRdsHSWbmq6d3Jd/O/nCSaaiUE fOyQ==
MIME-Version: 1.0
X-Received: by 10.182.78.41 with SMTP id y9mr12120294obw.69.1370360228877; Tue, 04 Jun 2013 08:37:08 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 4 Jun 2013 08:37:08 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <c1lhq819fnka5mga0buluqtmg73jh7qqj6@hive.bjoern.hoehrmann.de>
References: <c1lhq819fnka5mga0buluqtmg73jh7qqj6@hive.bjoern.hoehrmann.de>
Date: Tue, 4 Jun 2013 11:37:08 -0400
Message-ID: <CAL02cgQOxGS1XM--TYF5Wbo6MzrsJRbyNXMK7djgS1CJcmYPpw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary=047d7b2e4710a82ba604de55dac3
X-Gm-Message-State: ALoCoQlVz3KyjQFf5AQP4Sdzgz3xQsQH32gEIM/IVRwjPsZMjVdFCboUwgO0fB+3x2acSdfhM5Q5
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] draft-ietf-jose-use-cases-02, bad references
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 04 Jun 2013 17:23:07 -0000

--047d7b2e4710a82ba604de55dac3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks, Bjoern.  I've gone through my draft copy and reviewed the
references, so this should be better in -03 (to be released after I fix
other LC comments).
--Richard


On Fri, May 31, 2013 at 12:51 PM, Bjoern Hoehrmann <derhoermi@gmx.net>wrote=
:

> Hi,
>
>   In http://tools.ietf.org/html/draft-ietf-jose-use-cases-02 some of the
> references are outdated, for instance, "W3C.CR-xmldsig-core2-20120124"
> is a Working Group Note now, not a Candidate Recommendation anymore, and
> "W3C.REC-xml-1998" should probably reference the 5th Edition instead, or
> it should be clarified why the 1998 version is used. Furthermore, some
> of the references seem incorrectly classified, e.g. "W3C.REC-xml-1998"
> is listed as Normative, but the only time it is used is as an example in
> the Introduction. It should be non-normative, or be referenced with some
> clear normative purpose.
>
> regards,
> --
> Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehr=
mann.de
> Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld=
.de
> 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev=
.de/
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--047d7b2e4710a82ba604de55dac3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, Bjoern. =A0I&#39;ve gone through my draft copy and=
 reviewed the references, so this should be better in -03 (to be released a=
fter I fix other LC comments).<div>--Richard</div></div><div class=3D"gmail=
_extra">
<br><br><div class=3D"gmail_quote">On Fri, May 31, 2013 at 12:51 PM, Bjoern=
 Hoehrmann <span dir=3D"ltr">&lt;<a href=3D"mailto:derhoermi@gmx.net" targe=
t=3D"_blank">derhoermi@gmx.net</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Hi,<br>
<br>
=A0 In <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-use-cases-02" =
target=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-use-cases-02</=
a> some of the<br>
references are outdated, for instance, &quot;W3C.CR-xmldsig-core2-20120124&=
quot;<br>
is a Working Group Note now, not a Candidate Recommendation anymore, and<br=
>
&quot;W3C.REC-xml-1998&quot; should probably reference the 5th Edition inst=
ead, or<br>
it should be clarified why the 1998 version is used. Furthermore, some<br>
of the references seem incorrectly classified, e.g. &quot;W3C.REC-xml-1998&=
quot;<br>
is listed as Normative, but the only time it is used is as an example in<br=
>
the Introduction. It should be non-normative, or be referenced with some<br=
>
clear normative purpose.<br>
<br>
regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Bj=F6rn H=F6hrmann =B7 mailto:<a href=3D"mailto:bjoern@hoehrmann.de">bjoern=
@hoehrmann.de</a> =B7 <a href=3D"http://bjoern.hoehrmann.de" target=3D"_bla=
nk">http://bjoern.hoehrmann.de</a><br>
Am Badedeich 7 =B7 Telefon: <a href=3D"tel:%2B49%280%29160%2F4415681" value=
=3D"+491604415681">+49(0)160/4415681</a> =B7 <a href=3D"http://www.bjoernsw=
orld.de" target=3D"_blank">http://www.bjoernsworld.de</a><br>
25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 <a href=3D"http://www.w=
ebsitedev.de/" target=3D"_blank">http://www.websitedev.de/</a><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</font></span></blockquote></div><br></div>

--047d7b2e4710a82ba604de55dac3--

From sakimura@gmail.com  Wed Jun  5 05:54:01 2013
Return-Path: <sakimura@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4159121F9A15 for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 05:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level: 
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aO5B4U-8fRxU for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 05:53:59 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 63F1521F8609 for <jose@ietf.org>; Wed,  5 Jun 2013 05:53:58 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id ec20so1359218lab.41 for <jose@ietf.org>; Wed, 05 Jun 2013 05:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/tkIb+9XrmtX0DBs+2fbuLyE5nIQREepVEHngTOWuZc=; b=l/DGIPAOZhCjtosui5sCDHUBw4uY6kqGt6pgyjvKk6ruNbYvDVmIUMjl9hyTTW5hkW ZWHLQgaFfG/ITj3R6SZJz3A8UOL4wQvv5hGQsGjKmbMK6d53fZRg5tTtMUKt3jm/vbcn n9OYCJfCADDTjACvnUyRqedlsmmk0PJHABua1M+/C6c4gli1dysbYmFTBGczoonYMhfe 9lGRSXXTiR8nzAehdTiy7o6koocXvCWQpu9EZ7u88VdOF6+x5knOVl7Rguomw/XHexk8 iYl0xSoXHCyljFArQkF+lKHxD4GYSqFlCo12JtcRgSDspYqN3/AMt7Ld62gtZAnLaHW/ /t6w==
MIME-Version: 1.0
X-Received: by 10.112.236.70 with SMTP id us6mr14733744lbc.121.1370436834709;  Wed, 05 Jun 2013 05:53:54 -0700 (PDT)
Received: by 10.112.4.99 with HTTP; Wed, 5 Jun 2013 05:53:54 -0700 (PDT)
In-Reply-To: <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com>
Date: Wed, 5 Jun 2013 21:53:54 +0900
Message-ID: <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=001a11c3c946b8584904de67b053
Cc: Mike Jones <Michael.Jones@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Jun 2013 12:54:01 -0000

--001a11c3c946b8584904de67b053
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

What about such as this?

cty: original
typ: timestamp


2013/6/5 Richard Barnes <rlb@ipv.sx>

> It would be a good point, if it were true :)  In particular, this part:
> "[dropping 'typ'] is going to cause each and every application that uses
> JOSE to define their own field"
>
> So far, I've heard of exactly one application of JOSE that requires "typ"
> in the way it is currently specified, namely JWT.
>
> On the other hand, Dick's applications are apparently using it differentl=
y
> (and, IMO, properly) to distinguish JWE/JWS.  Then there are all the
> applications out there that are OK using application context and "cty" to
> recognize what type of object they have.  Apps using CMS have been doing
> this for ages.
>
> So it's not at all clear to me that there's any other application that
> would use "typ" besides JWT.  And it's not clear to me that JWT needs it.
>
> --Richard
>
>
>
>
>
> On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <
> bcampbell@pingidentity.com> wrote:
>
>> Nat makes a good point here, I think.
>>
>>
>> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com> wrote=
:
>>
>>> From what I understand, both typ and cty are something to be consumed b=
y
>>> the application and not JOSE processor. From the point of view of the J=
OSE
>>> processor, they should be ignored.
>>>
>>> We could drop both fields from JOSE specs, but that is going to cause
>>> each and every application that uses JOSE to define their own field, wh=
ich
>>> is a waste. That is why we are defining them here.
>>>
>>> I would rather drop them than define JOSE processing semantics to these
>>> fields.
>>>
>>>
>>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>>
>>>>  No, =93cty=94 is used by the derived class to determine the type of t=
he
>>>> encapsulated field.  But that=92s not a complete description of the **=
entire
>>>> object** - especially not the additional meaning imbued by the
>>>> additional parameters the derived type may add to the JOSE header.  =
=93typ=94
>>>> is there to provide the type of the entire object, including what you=
=92re
>>>> calling the wrapper parts.****
>>>>
>>>> ** **
>>>>
>>>>                                                             -- Mike***=
*
>>>>
>>>> ** **
>>>>
>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>>
>>>> *To:* Mike Jones
>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>> ** **
>>>>
>>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is a
>>>> crypto wrapper around the real application content.  If you're an
>>>> application, you know a JOSE object is the thing you want because it
>>>> contains the content you want -- it's a JWT because it contains JWT cl=
aims.
>>>> ****
>>>>
>>>> ** **
>>>>
>>>> Inheritance is the wrong metaphor.  This is encapsulation of
>>>> application data:****
>>>>
>>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>>
>>>>     jwtClaims =3D jws.content;****
>>>>
>>>> }****
>>>>
>>>> ** **
>>>>
>>>> --Richard****
>>>>
>>>> ** **
>>>>
>>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>>> Michael.Jones@microsoft.com> wrote:****
>>>>
>>>> Thanks for sharing the S/MIME details.  Although I was actually making
>>>> the analogy to MIME =96 not S/MIME.  Like many analogies, it=92s imper=
fect, but
>>>> I believe still illustrative.****
>>>>
>>>>  ****
>>>>
>>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>>> structures are used to build application-specific data structures that=
 are
>>>> legal JOSE data structures but also have additional properties =96 inc=
luding
>>>> additional header fields with specific semantics.  (When we agreed to
>>>> ignore not-understood header fields we let that horse out of the barn.=
)
>>>> For instance, Dick Hardt uses JWEs with issuer and audience fields in =
the
>>>> headers, so they can be used by routing software.****
>>>>
>>>>  ****
>>>>
>>>> Think of JOSE as the base class and the application types built using
>>>> it as derived classes.  JWT is a derived class.  Dick=92s structures a=
re a
>>>> derived class.  These derived classes sometimes need names.  That=92s =
what
>>>> =93typ=94 is for.****
>>>>
>>>>  ****
>>>>
>>>>                                                             -- Mike***=
*
>>>>
>>>>  ****
>>>>
>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>>
>>>>
>>>> *To:* Mike Jones
>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>>  ****
>>>>
>>>> You're mixing up "typ" and "cty".  If you want to make the analogy to
>>>> S/MIME, "cty" is the equivalent to Content-Type inside the protected M=
IME
>>>> body; "typ" is the content-type on the outer MIME header.  Pasting in =
an
>>>> example:****
>>>>
>>>>  ****
>>>>
>>>> -----BEGIN-----****
>>>>
>>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>>>>
>>>>      name=3Dsmime.p7m****
>>>>
>>>> Content-Transfer-Encoding: base64****
>>>>
>>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>>
>>>>  ****
>>>>
>>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>>
>>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>>
>>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>>
>>>> 6YT64V0GhIGfHfQbnj75****
>>>>
>>>> -----END-----****
>>>>
>>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>>
>>>>  ****
>>>>
>>>> The outer Content-Type, which is analogous to "typ", MUST be
>>>> application/pkcs7-mime, with a parameter indicating the type of CMS ob=
ject.
>>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>>> Content-Type (ASN.1/base64 encoded in the example) can be anything, ju=
st
>>>> like "cty".****
>>>>
>>>>  ****
>>>>
>>>> --Richard****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>>> Michael.Jones@microsoft.com> wrote:****
>>>>
>>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 woul=
d be
>>>> analogous to the MIME spec requiring that the Content-Type: field be o=
nly
>>>> =93text/plain=94 or =93message/external-body=94.  It would render it u=
seless.**
>>>> **
>>>>
>>>>  ****
>>>>
>>>>                                                             -- Mike***=
*
>>>>
>>>>  ****
>>>>
>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>> Behalf Of *Richard Barnes
>>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>>> *To:* Mike Jones
>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>>
>>>>
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>>  ****
>>>>
>>>> If this is the level of "type" you're referring to, I think we should
>>>> drop it from the spec.  It's an application-layer thing that the app c=
an
>>>> add or not according to its wishes.****
>>>>
>>>>  ****
>>>>
>>>> I'm with Dick on this.  I think we should either have a mandatory
>>>> indicator of what type of JOSE object this, or nothing at all.   If th=
e
>>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" options=
 are
>>>> non-sensical -- the app needs to know what it's parsing before it gets=
 this
>>>> header.  While I have a preference for the former (for clarity), the l=
atter
>>>> approach is also OK with me, since the MIME types are specific to JWE/=
JWS.
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> Another approach here would be to address the JSON and compact forms
>>>> separately.  The JSON form has no need of "typ" at all, since the type=
 of
>>>> the object is completely clear from what fields are there, e.g.,
>>>> "recipients" vs. "signatures".  For the compact form, we could do some=
thing
>>>> like James's "E."/"S." prefix idea, which you need because the
>>>> dot-separated components have different meanings and no field names to
>>>> indicate this.****
>>>>
>>>>  ****
>>>>
>>>> --Richard****
>>>>
>>>>  ****
>>>>
>>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <
>>>> Michael.Jones@microsoft.com> wrote:****
>>>>
>>>> A standard library is unlikely to know the meanings of all possible
>>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*.  I=
t=92s the
>>>> application=92s job to determine that =93this blob is a JOSE object=94=
 and then
>>>> pass it to a standard library, which will then ignore the =93typ=94 va=
lue.*
>>>> ***
>>>>
>>>>  ****
>>>>
>>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 means. =
 It won=92t
>>>> know what =93typ=94: =93BCGovToken=94 is, should the BC Government wan=
t to declare
>>>> that it=92s using a token with particular characteristics.  It won=92t=
 know
>>>> what =93typ=94: =93XMPP=94 is, should XMPP want to declare that it=92s=
 using a JOSE
>>>> data structure with particular characteristics.  Etc.****
>>>>
>>>>  ****
>>>>
>>>> All these values can be registered in the registry and used by
>>>> applications that understand them.  That=92s the application=92s job =
=96 not the
>>>> library=92s job.  The =93typ=94 field is just there so that applicatio=
ns have a
>>>> standard place to make any such declarations that they may need.****
>>>>
>>>>  ****
>>>>
>>>>                                                                 -- Mik=
e
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>>> *To:* Mike Jones
>>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>>
>>>>
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>>  ****
>>>>
>>>> I'd prefer to be able to use standard libraries for creating and
>>>> parsing tokens, and not specialized libraries dependent on the use cas=
e.
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> I strongly think we either drop "typ" or make it required.****
>>>>
>>>>  ****
>>>>
>>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <
>>>> Michael.Jones@microsoft.com> wrote:****
>>>>
>>>> It=92s fine for your application to specify that it=92s required for y=
our
>>>> use case.  Not applications need it, so they shouldn=92t be forced to =
pay the
>>>> space penalty of an unnecessary field.****
>>>>
>>>>  ****
>>>>
>>>>                                                                 -- Mik=
e
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>> Behalf Of *Dick Hardt
>>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>>
>>>>
>>>> *To:* Jim Schaad
>>>> *Cc:* jose@ietf.org
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>>  ****
>>>>
>>>> I use it all the time and my code would barf if it was not there.****
>>>>
>>>>  ****
>>>>
>>>> I think it should be required rather than be a hint if it is going ot
>>>> be there.****
>>>>
>>>>  ****
>>>>
>>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com>
>>>> wrote:****
>>>>
>>>> I think the values just changed****
>>>>
>>>>  ****
>>>>
>>>> However the way you are using it would be an argument to say that it
>>>> should be a required field.  Are you just using it as a hint if it exi=
sts
>>>> and then looking at the rest of the fields if it is not present?****
>>>>
>>>>  ****
>>>>
>>>> Jim****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>>> *To:* Jim Schaad
>>>> *Cc:* jose@ietf.org
>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>
>>>>  ****
>>>>
>>>> Well, I have been using, but now realize the spec changed or I was
>>>> confused.****
>>>>
>>>>  ****
>>>>
>>>> I had been setting "typ" to be either "JWE" or "JWS" depending on the
>>>> type of token I was creating or parsing as it was easier than looking =
at
>>>> "alg"****
>>>>
>>>>  ****
>>>>
>>>> As currently defined, I don't see value in "typ".****
>>>>
>>>>  ****
>>>>
>>>> -- Dick****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com>
>>>> wrote:****
>>>>
>>>> In reading the documents, I am trying to understand the justification
>>>> for having the =93typ=94 header parameter in the JOSE documents.****
>>>>
>>>>  ****
>>>>
>>>> The purpose of the field is to hold the type of the object.  In the
>>>> past, I believe that values which should now be placed in the cty fiel=
d
>>>> (such as =93JWT=94) were placed in this field as well.  However the pa=
rameter
>>>> is optional and an implementation cannot rely on its being present.  T=
his
>>>> means that for all practical purposes all of the code to determine the
>>>> value of the type field from the values of the alg and enc fields.  If=
 the
>>>> field was mandatory then this code would disappear at a fairly small s=
pace
>>>> cost and I can understand why the parameter would be present.****
>>>>
>>>>  ****
>>>>
>>>> Can anybody justify why this field should be present in the document =
=96
>>>> or should it just disappear?****
>>>>
>>>>  ****
>>>>
>>>> Jim****
>>>>
>>>>  ****
>>>>
>>>>
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>
>>>>
>>>>
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> --
>>>> -- Dick ****
>>>>
>>>>
>>>>
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> --
>>>> -- Dick ****
>>>>
>>>>
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>
>>>>
>>>>
>>>> ****
>>>>
>>>>  ****
>>>>
>>>> --
>>>> -- Dick ****
>>>>
>>>>
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>
>>>>  ****
>>>>
>>>>  ****
>>>>
>>>> ** **
>>>>
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>
>>>>
>>>
>>>
>>> --
>>> Nat Sakimura (=3Dnat)
>>> Chairman, OpenID Foundation
>>> http://nat.sakimura.org/
>>> @_nat_en
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>
>


--=20
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en

--001a11c3c946b8584904de67b053
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>What about such as this?=A0</div><div><br></div=
>cty: original<div style>typ: timestamp</div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">2013/6/5 Richard Barnes <span dir=3D"=
ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;=
</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">It would be a good point, i=
f it were true :) =A0In particular, this part: &quot;[dropping &#39;typ&#39=
;]<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:=
13px">=A0is going to cause each and every application that uses JOSE to def=
ine their own field</span>&quot;<div>

<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>

<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><span class=3D"HOEnZb"><font co=
lor=3D"#888888"><div>
<br></div><div>--Richard</div>
<div><br></div><div><br><div><br></div></div></font></span></div><div class=
=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <span dir=
=3D"ltr">&lt;<a href=3D"mailto:bcampbell@pingidentity.com" target=3D"_blank=
">bcampbell@pingidentity.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>



<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>




<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>





<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>





<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>





</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>





</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>





<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>





</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>




</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>

</div>

--001a11c3c946b8584904de67b053--

From jricher@mitre.org  Wed Jun  5 06:41:16 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CE621F9AF9; Wed,  5 Jun 2013 06:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.255
X-Spam-Level: 
X-Spam-Status: No, score=-5.255 tagged_above=-999 required=5 tests=[AWL=-0.660, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lffP03vkqsXi; Wed,  5 Jun 2013 06:41:11 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 32A5421F9AFB; Wed,  5 Jun 2013 06:41:11 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 625AE1F04AF; Wed,  5 Jun 2013 09:41:10 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 422B31F0269; Wed,  5 Jun 2013 09:41:10 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 5 Jun 2013 09:41:10 -0400
Message-ID: <51AF3FC6.7080501@mitre.org>
Date: Wed, 5 Jun 2013 09:40:22 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: <Axel.Nennker@telekom.de>
References: <2481701B-912B-4B5B-821C-D86721A4C4C6@adobe.com> <CE8995AB5D178F44A2154F5C9A97CAF40255A5BB872A@HE111541.emea1.cds.t-internal.com>
In-Reply-To: <CE8995AB5D178F44A2154F5C9A97CAF40255A5BB872A@HE111541.emea1.cds.t-internal.com>
Content-Type: multipart/alternative; boundary="------------050000050409010803090807"
X-Originating-IP: [129.83.31.56]
Cc: asanso@adobe.com, oauth@ietf.org, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] [OAUTH-WG] JWS encoding Appendix A
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Jun 2013 13:41:16 -0000

--------------050000050409010803090807
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Also, it's the JOSE working group, not OAuth, that's working on JWS. 
I've CC'd that group on this reply, further discussion (if needed) 
should probably take place there.

  -- Justin

On 06/05/2013 09:37 AM, Axel.Nennker@telekom.de wrote:
>
> Antonio,
>
> Please have a look at this
>
> https://code.google.com/p/jsoncrypto/source/browse/trunk/testsrc/org/jsoncrypto/JcBaseTest.java#104
>
> The \r\n is the important.
>
> Please make sure you have this byte representation of the payload.
>
> The following octet sequence contains the UTF-8 representation of the
>
> JWS Header:
>
> [123, 34, 116, 121, 112, 34, 58, 34, 74, 87, 84, 34, 44, 13, 10, 32,
>
> 34, 97, 108, 103, 34, 58, 34, 72, 83, 50, 53, 54, 34, 125]
>
> Best regards
>
> Axel
>
> *From:*oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] *On 
> Behalf Of *Antonio Sanso
> *Sent:* Wednesday, June 05, 2013 3:27 PM
> *To:* oauth@ietf.org WG
> *Subject:* [OAUTH-WG] JWS encoding Appendix A
>
> Hi *,
>
> while testing my encoding routine against JWS I spot a difference 
> between my encoding and the one in the spec.
>
> More specifically I am referring to Appendix A.1.1 [0] of the JWS spec.
>
> Now it could easily be that the library I wrote is wrong but it works 
> fine with the encoding in the JWT spec for example.
>
> If somebody would like to give a look just for the record the encoding 
> for the header in the spec looks like \
>
> eyJ0eXAiOiJKV1QiLA0KICJhbGciOiJIUzI1NiJ9
>
> while for me would look like
>
> eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9
>
> Same for the payload, spec
>
> eyJpc3MiOiJqb2UiLA0KICJleHAiOjEzMDA4MTkzODAsDQogImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ
>
> my library
>
> eyJpc3MiOiJqb2UiLCJleHAiOjEzMDA4MTkzODAsImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ
>
> Now the difference is probably given from the fact I did not take care 
> in consideration carriage return in my input.
>
> I am on a huge JSON expert but what is the correct way to handle it?
>
> Regards
>
> Antonio
>
> [0] 
> http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#appendix-A.1
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth


--------------050000050409010803090807
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Also, it's the JOSE working group, not OAuth, that's working on JWS.
    I've CC'd that group on this reply, further discussion (if needed)
    should probably take place there.<br>
    <br>
    &nbsp;-- Justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/05/2013 09:37 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:Axel.Nennker@telekom.de">Axel.Nennker@telekom.de</a> wrote:<br>
    </div>
    <blockquote
cite="mid:CE8995AB5D178F44A2154F5C9A97CAF40255A5BB872A@HE111541.emea1.cds.t-internal.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Antonio,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Please
            have a look at this <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><a
              moz-do-not-send="true"
href="https://code.google.com/p/jsoncrypto/source/browse/trunk/testsrc/org/jsoncrypto/JcBaseTest.java#104">https://code.google.com/p/jsoncrypto/source/browse/trunk/testsrc/org/jsoncrypto/JcBaseTest.java#104</a><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            \r\n is the important.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Please
            make sure you have this byte representation of the payload.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">The
            following octet sequence contains the UTF-8 representation
            of the<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;
            JWS Header:<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;
            [123, 34, 116, 121, 112, 34, 58, 34, 74, 87, 84, 34, 44, 13,
            10, 32,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp;
            34, 97, 108, 103, 34, 58, 34, 72, 83, 50, 53, 54, 34, 125]<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            regards<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Axel<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                <a class="moz-txt-link-abbreviated" href="mailto:oauth-bounces@ietf.org">oauth-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:oauth-bounces@ietf.org">mailto:oauth-bounces@ietf.org</a>] <b>On
                  Behalf Of </b>Antonio Sanso<br>
                <b>Sent:</b> Wednesday, June 05, 2013 3:27 PM<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:oauth@ietf.org">oauth@ietf.org</a> WG<br>
                <b>Subject:</b> [OAUTH-WG] JWS encoding Appendix A<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Hi *,<o:p></o:p></p>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">while testing my encoding routine against
            JWS I spot a difference between my encoding and the one in
            the spec.<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">More specifically I am referring to
            Appendix A.1.1 [0] of the JWS spec.<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Now it could easily be that the library I
            wrote is wrong but it works fine with the encoding in the
            JWT spec for example.<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal">If somebody would like to give a look
            just for the record the encoding for the header in the spec
            looks like \<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <pre>eyJ0eXAiOiJKV1QiLA0KICJhbGciOiJIUzI1NiJ9<o:p></o:p></pre>
          <div>
            <p class="MsoNormal">while for me would look like<o:p></o:p></p>
          </div>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Same for the payload, spec<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><span class="apple-style-span"><span
                style="font-family:&quot;Courier New&quot;">eyJpc3MiOiJqb2UiLA0KICJleHAiOjEzMDA4MTkzODAsDQogImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ</span></span><o:p></o:p></p>
        </div>
        <div>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
        </div>
        <div>
          <p class="MsoNormal">my library<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">eyJpc3MiOiJqb2UiLCJleHAiOjEzMDA4MTkzODAsImh0dHA6Ly9leGFtcGxlLmNvbS9pc19yb290Ijp0cnVlfQ<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Now the difference is probably given from
            the fact I did not take care in consideration carriage
            return in my input.<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal">I am on a huge JSON expert but what is
            the correct way to handle it?&nbsp;<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Regards<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Antonio<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
        <div>
          <p class="MsoNormal">[0]&nbsp;<a moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#appendix-A.1">http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#appendix-A.1</a><o:p></o:p></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OAuth mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OAuth@ietf.org">OAuth@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/oauth">https://www.ietf.org/mailman/listinfo/oauth</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050000050409010803090807--

From rlb@ipv.sx  Wed Jun  5 07:14:27 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB0221F9952 for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 07:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.137
X-Spam-Level: *
X-Spam-Status: No, score=1.137 tagged_above=-999 required=5 tests=[AWL=-1.041,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hmg1dx3tRuOs for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 07:14:23 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id BF19821F957B for <jose@ietf.org>; Wed,  5 Jun 2013 07:14:19 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so2620127obb.4 for <jose@ietf.org>; Wed, 05 Jun 2013 07:14:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=XbBpubfLBT0akdQUv+4hlgiOtHOecVN6+qhLwfcPzHE=; b=lhFommC5DYW2tCnBdk8dyJ+2wilhJoBBzw6Akd6izXjk3HYR74qah5pSAKjJ89Bw4w sNPAyI0dxSMiJ5ZrBP0XHCwhDHiqykjw6qsTkVnz8p4V+SPO1M5rj0zkb2XT1y5A7MqW QeRFezlJLC5m3AtRPDdgUZQ2vCTcp+i9xubIlHsrFtkEFdpsFVz2pWx6CUP0vmOxy+L2 q2bOOkFyWaVvfh4gpxi6VQTdrtbIBaA5110aJdOtT5BePELkgPp8lOdKm7u/+5+4JoC7 zwDtIPksZGnoyUMghE85tf+Pjioh8jeqUV7Y7LrhKcg05jg2hoyWxm+isJ+6vXLNVP3t zKXw==
MIME-Version: 1.0
X-Received: by 10.60.134.236 with SMTP id pn12mr15537900oeb.4.1370441659196; Wed, 05 Jun 2013 07:14:19 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Wed, 5 Jun 2013 07:14:19 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com>
Date: Wed, 5 Jun 2013 10:14:19 -0400
Message-ID: <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Nat Sakimura <sakimura@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b471f6a48360004de68d060
X-Gm-Message-State: ALoCoQn3O7Vydoa1hATEUFR4yGOhvEoOVBnBC/jFtfdZDI2hSLQuwaNCqOgSvyzTlEcxmho8Yk6g
Cc: Mike Jones <Michael.Jones@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Jun 2013 14:14:27 -0000

--047d7b471f6a48360004de68d060
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I'm not sure I understand the use case here.  Let me look at a couple of
options, and hopefully one of them will be what you meant :)

If it's just a signed timestamp you're talking about, then that's
adequately described by cty=3D"timestamp", typ=3D"JWS".

If you want to sign something and add a timestamp in the header, then
typ=3D"timestamp" isn't accurate according to the current specification.  T=
he
type of the whole object would have to be something like
"timestamped-content".  And in that case, an application can easily
recognized that it's timestamped content by looking for the timestamp field
in the header, so the "typ" isn't really helpful.


Moving from the example to the general question:

I think we finally have some common understanding on this list as to what
Mike means by "typ" in the current document -- a label for the
application-layer type of the overall object.  Thanks to Mike for
clarifying that in this discussion.

The question is whether this is a sufficiently useful thing to have in the
core spec.  Obviously, applications have to know what type of object
they're dealing with when they get a JOSE object.  That includes (1) what
type of content is in the payload, and (2) what application-layer fields
are required to be in the header.  (1) is covered by "cty".  So "typ" is
only useful in the case where:
A. The application is storing application-layer data in the JOSE header
B. The required application-layer fields can be different for different
objects
C. The required application-layer fields can be different for different
objects of the same content type
D. The required application-layer fields are not indicated by other
application-layer context

Are there any known applications that meet these criteria?  JWT does not,
for several reasons.
1. (!A) JWT does not store application-layer data in the JOSE header, only
in the claims in the body
2. (!C) A JWT object can indicate with "cty" that it contains JWT claims or
another JWT, either of which makes it obvious that this is a JWT
3. (!D) In the OAuth context, the Token Type value indicates what type of
token is being presented, e.g., JWT

So there's not really any known use case for "typ" as currently specified.
 On the other hand, Dick and James have pointed out that it can be useful
to have "typ" indicate whether the object at hand is a JWE or JWS.  Which
brings us back to:
-- Change the definition of "typ" so that it indicates the JOSE-layer type
(JWE/JWS)
-- Remove "typ" altogether







On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <sakimura@gmail.com> wrote:

> What about such as this?
>
> cty: original
> typ: timestamp
>
>
> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>
>> It would be a good point, if it were true :)  In particular, this part:
>> "[dropping 'typ'] is going to cause each and every application that uses
>> JOSE to define their own field"
>>
>> So far, I've heard of exactly one application of JOSE that requires "typ=
"
>> in the way it is currently specified, namely JWT.
>>
>> On the other hand, Dick's applications are apparently using it
>> differently (and, IMO, properly) to distinguish JWE/JWS.  Then there are
>> all the applications out there that are OK using application context and
>> "cty" to recognize what type of object they have.  Apps using CMS have b=
een
>> doing this for ages.
>>
>> So it's not at all clear to me that there's any other application that
>> would use "typ" besides JWT.  And it's not clear to me that JWT needs it=
.
>>
>> --Richard
>>
>>
>>
>>
>>
>> On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <
>> bcampbell@pingidentity.com> wrote:
>>
>>> Nat makes a good point here, I think.
>>>
>>>
>>> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com>wrote=
:
>>>
>>>> From what I understand, both typ and cty are something to be consumed
>>>> by the application and not JOSE processor. From the point of view of t=
he
>>>> JOSE processor, they should be ignored.
>>>>
>>>> We could drop both fields from JOSE specs, but that is going to cause
>>>> each and every application that uses JOSE to define their own field, w=
hich
>>>> is a waste. That is why we are defining them here.
>>>>
>>>> I would rather drop them than define JOSE processing semantics to thes=
e
>>>> fields.
>>>>
>>>>
>>>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>>>
>>>>>  No, =93cty=94 is used by the derived class to determine the type of =
the
>>>>> encapsulated field.  But that=92s not a complete description of the *=
*entire
>>>>> object** - especially not the additional meaning imbued by the
>>>>> additional parameters the derived type may add to the JOSE header.  =
=93typ=94
>>>>> is there to provide the type of the entire object, including what you=
=92re
>>>>> calling the wrapper parts.****
>>>>>
>>>>> ** **
>>>>>
>>>>>                                                             -- Mike**=
*
>>>>> *
>>>>>
>>>>> ** **
>>>>>
>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>>>
>>>>> *To:* Mike Jones
>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>> ** **
>>>>>
>>>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is a
>>>>> crypto wrapper around the real application content.  If you're an
>>>>> application, you know a JOSE object is the thing you want because it
>>>>> contains the content you want -- it's a JWT because it contains JWT c=
laims.
>>>>> ****
>>>>>
>>>>> ** **
>>>>>
>>>>> Inheritance is the wrong metaphor.  This is encapsulation of
>>>>> application data:****
>>>>>
>>>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>>>
>>>>>     jwtClaims =3D jws.content;****
>>>>>
>>>>> }****
>>>>>
>>>>> ** **
>>>>>
>>>>> --Richard****
>>>>>
>>>>> ** **
>>>>>
>>>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>
>>>>> Thanks for sharing the S/MIME details.  Although I was actually makin=
g
>>>>> the analogy to MIME =96 not S/MIME.  Like many analogies, it=92s impe=
rfect, but
>>>>> I believe still illustrative.****
>>>>>
>>>>>  ****
>>>>>
>>>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>>>> structures are used to build application-specific data structures tha=
t are
>>>>> legal JOSE data structures but also have additional properties =96 in=
cluding
>>>>> additional header fields with specific semantics.  (When we agreed to
>>>>> ignore not-understood header fields we let that horse out of the barn=
.)
>>>>> For instance, Dick Hardt uses JWEs with issuer and audience fields in=
 the
>>>>> headers, so they can be used by routing software.****
>>>>>
>>>>>  ****
>>>>>
>>>>> Think of JOSE as the base class and the application types built using
>>>>> it as derived classes.  JWT is a derived class.  Dick=92s structures =
are a
>>>>> derived class.  These derived classes sometimes need names.  That=92s=
 what
>>>>> =93typ=94 is for.****
>>>>>
>>>>>  ****
>>>>>
>>>>>                                                             -- Mike**=
*
>>>>> *
>>>>>
>>>>>  ****
>>>>>
>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>>>
>>>>>
>>>>> *To:* Mike Jones
>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>>  ****
>>>>>
>>>>> You're mixing up "typ" and "cty".  If you want to make the analogy to
>>>>> S/MIME, "cty" is the equivalent to Content-Type inside the protected =
MIME
>>>>> body; "typ" is the content-type on the outer MIME header.  Pasting in=
 an
>>>>> example:****
>>>>>
>>>>>  ****
>>>>>
>>>>> -----BEGIN-----****
>>>>>
>>>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>>>>>
>>>>>      name=3Dsmime.p7m****
>>>>>
>>>>> Content-Transfer-Encoding: base64****
>>>>>
>>>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>>>
>>>>>  ****
>>>>>
>>>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>>>
>>>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>>>
>>>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>>>
>>>>> 6YT64V0GhIGfHfQbnj75****
>>>>>
>>>>> -----END-----****
>>>>>
>>>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>>>
>>>>>  ****
>>>>>
>>>>> The outer Content-Type, which is analogous to "typ", MUST be
>>>>> application/pkcs7-mime, with a parameter indicating the type of CMS o=
bject.
>>>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>>>> Content-Type (ASN.1/base64 encoded in the example) can be anything, j=
ust
>>>>> like "cty".****
>>>>>
>>>>>  ****
>>>>>
>>>>> --Richard****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>
>>>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 wou=
ld be
>>>>> analogous to the MIME spec requiring that the Content-Type: field be =
only
>>>>> =93text/plain=94 or =93message/external-body=94.  It would render it =
useless.*
>>>>> ***
>>>>>
>>>>>  ****
>>>>>
>>>>>                                                             -- Mike**=
*
>>>>> *
>>>>>
>>>>>  ****
>>>>>
>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>> Behalf Of *Richard Barnes
>>>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>>>> *To:* Mike Jones
>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>>>
>>>>>
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>>  ****
>>>>>
>>>>> If this is the level of "type" you're referring to, I think we should
>>>>> drop it from the spec.  It's an application-layer thing that the app =
can
>>>>> add or not according to its wishes.****
>>>>>
>>>>>  ****
>>>>>
>>>>> I'm with Dick on this.  I think we should either have a mandatory
>>>>> indicator of what type of JOSE object this, or nothing at all.   If t=
he
>>>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" option=
s are
>>>>> non-sensical -- the app needs to know what it's parsing before it get=
s this
>>>>> header.  While I have a preference for the former (for clarity), the =
latter
>>>>> approach is also OK with me, since the MIME types are specific to JWE=
/JWS.
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> Another approach here would be to address the JSON and compact forms
>>>>> separately.  The JSON form has no need of "typ" at all, since the typ=
e of
>>>>> the object is completely clear from what fields are there, e.g.,
>>>>> "recipients" vs. "signatures".  For the compact form, we could do som=
ething
>>>>> like James's "E."/"S." prefix idea, which you need because the
>>>>> dot-separated components have different meanings and no field names t=
o
>>>>> indicate this.****
>>>>>
>>>>>  ****
>>>>>
>>>>> --Richard****
>>>>>
>>>>>  ****
>>>>>
>>>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <
>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>
>>>>> A standard library is unlikely to know the meanings of all possible
>>>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*.  =
It=92s the
>>>>> application=92s job to determine that =93this blob is a JOSE object=
=94 and then
>>>>> pass it to a standard library, which will then ignore the =93typ=94 v=
alue.
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 means.=
  It won=92t
>>>>> know what =93typ=94: =93BCGovToken=94 is, should the BC Government wa=
nt to declare
>>>>> that it=92s using a token with particular characteristics.  It won=92=
t know
>>>>> what =93typ=94: =93XMPP=94 is, should XMPP want to declare that it=92=
s using a JOSE
>>>>> data structure with particular characteristics.  Etc.****
>>>>>
>>>>>  ****
>>>>>
>>>>> All these values can be registered in the registry and used by
>>>>> applications that understand them.  That=92s the application=92s job =
=96 not the
>>>>> library=92s job.  The =93typ=94 field is just there so that applicati=
ons have a
>>>>> standard place to make any such declarations that they may need.****
>>>>>
>>>>>  ****
>>>>>
>>>>>                                                                 -- Mi=
ke
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>>>> *To:* Mike Jones
>>>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>>>
>>>>>
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>>  ****
>>>>>
>>>>> I'd prefer to be able to use standard libraries for creating and
>>>>> parsing tokens, and not specialized libraries dependent on the use ca=
se.
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> I strongly think we either drop "typ" or make it required.****
>>>>>
>>>>>  ****
>>>>>
>>>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <
>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>
>>>>> It=92s fine for your application to specify that it=92s required for =
your
>>>>> use case.  Not applications need it, so they shouldn=92t be forced to=
 pay the
>>>>> space penalty of an unnecessary field.****
>>>>>
>>>>>  ****
>>>>>
>>>>>                                                                 -- Mi=
ke
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>> Behalf Of *Dick Hardt
>>>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>>>
>>>>>
>>>>> *To:* Jim Schaad
>>>>> *Cc:* jose@ietf.org
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>>  ****
>>>>>
>>>>> I use it all the time and my code would barf if it was not there.****
>>>>>
>>>>>  ****
>>>>>
>>>>> I think it should be required rather than be a hint if it is going ot
>>>>> be there.****
>>>>>
>>>>>  ****
>>>>>
>>>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com>
>>>>> wrote:****
>>>>>
>>>>> I think the values just changed****
>>>>>
>>>>>  ****
>>>>>
>>>>> However the way you are using it would be an argument to say that it
>>>>> should be a required field.  Are you just using it as a hint if it ex=
ists
>>>>> and then looking at the rest of the fields if it is not present?****
>>>>>
>>>>>  ****
>>>>>
>>>>> Jim****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>>>> *To:* Jim Schaad
>>>>> *Cc:* jose@ietf.org
>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>
>>>>>  ****
>>>>>
>>>>> Well, I have been using, but now realize the spec changed or I was
>>>>> confused.****
>>>>>
>>>>>  ****
>>>>>
>>>>> I had been setting "typ" to be either "JWE" or "JWS" depending on the
>>>>> type of token I was creating or parsing as it was easier than looking=
 at
>>>>> "alg"****
>>>>>
>>>>>  ****
>>>>>
>>>>> As currently defined, I don't see value in "typ".****
>>>>>
>>>>>  ****
>>>>>
>>>>> -- Dick****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com>
>>>>> wrote:****
>>>>>
>>>>> In reading the documents, I am trying to understand the justification
>>>>> for having the =93typ=94 header parameter in the JOSE documents.****
>>>>>
>>>>>  ****
>>>>>
>>>>> The purpose of the field is to hold the type of the object.  In the
>>>>> past, I believe that values which should now be placed in the cty fie=
ld
>>>>> (such as =93JWT=94) were placed in this field as well.  However the p=
arameter
>>>>> is optional and an implementation cannot rely on its being present.  =
This
>>>>> means that for all practical purposes all of the code to determine th=
e
>>>>> value of the type field from the values of the alg and enc fields.  I=
f the
>>>>> field was mandatory then this code would disappear at a fairly small =
space
>>>>> cost and I can understand why the parameter would be present.****
>>>>>
>>>>>  ****
>>>>>
>>>>> Can anybody justify why this field should be present in the document =
=96
>>>>> or should it just disappear?****
>>>>>
>>>>>  ****
>>>>>
>>>>> Jim****
>>>>>
>>>>>  ****
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jose mailing list
>>>>> jose@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>
>>>>>
>>>>>
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> --
>>>>> -- Dick ****
>>>>>
>>>>>
>>>>>
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> --
>>>>> -- Dick ****
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jose mailing list
>>>>> jose@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>
>>>>>
>>>>>
>>>>> ****
>>>>>
>>>>>  ****
>>>>>
>>>>> --
>>>>> -- Dick ****
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jose mailing list
>>>>> jose@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>
>>>>>  ****
>>>>>
>>>>>  ****
>>>>>
>>>>> ** **
>>>>>
>>>>> _______________________________________________
>>>>> jose mailing list
>>>>> jose@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Nat Sakimura (=3Dnat)
>>>> Chairman, OpenID Foundation
>>>> http://nat.sakimura.org/
>>>> @_nat_en
>>>>
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>
>>>>
>>>
>>
>
>
> --
> Nat Sakimura (=3Dnat)
> Chairman, OpenID Foundation
> http://nat.sakimura.org/
> @_nat_en
>

--047d7b471f6a48360004de68d060
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m not sure I understand the use case here. =A0Let me=
 look at a couple of options, and hopefully one of them will be what you me=
ant :) =A0<div><br></div><div>If it&#39;s just a signed timestamp you&#39;r=
e talking about, then that&#39;s adequately described by cty=3D&quot;timest=
amp&quot;, typ=3D&quot;JWS&quot;.</div>
<div><br></div><div>If you want to sign something and add a timestamp in th=
e header, then typ=3D&quot;timestamp&quot; isn&#39;t accurate according to =
the current specification. =A0The type of the whole object would have to be=
 something like &quot;timestamped-content&quot;. =A0And in that case, an ap=
plication can easily recognized that it&#39;s timestamped content by lookin=
g for the timestamp field in the header, so the &quot;typ&quot; isn&#39;t r=
eally helpful.</div>
<div><br></div><div><br></div><div>Moving from the example to the general q=
uestion:</div><div><br></div><div>I think we finally have some common under=
standing on this list as to what Mike means by &quot;typ&quot; in the curre=
nt document -- a label for the application-layer type of the overall object=
. =A0Thanks to Mike for clarifying that in this discussion.</div>
<div><br></div><div>The question is whether this is a sufficiently useful t=
hing to have in the core spec. =A0Obviously, applications have to know what=
 type of object they&#39;re dealing with when they get a JOSE object. =A0Th=
at includes (1) what type of content is in the payload, and (2) what applic=
ation-layer fields are required to be in the header. =A0(1) is covered by &=
quot;cty&quot;. =A0So &quot;typ&quot; is only useful in the case where:</di=
v>
<div>A. The application is storing application-layer data in the JOSE heade=
r</div><div>B. The required application-layer fields can be different for d=
ifferent objects</div><div>C. The required application-layer fields can be =
different for different objects of the same content type</div>
<div>D. The required application-layer fields are not indicated by other ap=
plication-layer context</div><div><br></div><div>Are there any known applic=
ations that meet these criteria? =A0JWT does not, for several reasons.=A0</=
div>
<div>1. (!A) JWT does not store application-layer data in the JOSE header, =
only in the claims in the body</div><div>2. (!C) A JWT object can indicate =
with &quot;cty&quot; that it contains JWT claims or another JWT, either of =
which makes it obvious that this is a JWT</div>
<div>3. (!D) In the OAuth context, the Token Type value indicates what type=
 of token is being presented, e.g., JWT</div><div><br></div><div>So there&#=
39;s not really any known use case for &quot;typ&quot; as currently specifi=
ed. =A0On the other hand, Dick and James have pointed out that it can be us=
eful to have &quot;typ&quot; indicate whether the object at hand is a JWE o=
r JWS. =A0Which brings us back to:</div>
<div>-- Change the definition of &quot;typ&quot; so that it indicates the J=
OSE-layer type (JWE/JWS)</div><div>-- Remove &quot;typ&quot; altogether</di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br>
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sakimura@gmail.com" target=3D"_blank">sakimura@gmail.com</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>What about such as thi=
s?=A0</div><div><br></div>cty: original<div>typ: timestamp</div></div><div =
class=3D"HOEnZb">
<div class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">2013/6/5 Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ip=
v.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">It would be a good point, i=
f it were true :) =A0In particular, this part: &quot;[dropping &#39;typ&#39=
;]<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:=
13px">=A0is going to cause each and every application that uses JOSE to def=
ine their own field</span>&quot;<div>


<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>


<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><span><font color=3D"#888888"><=
div>

<br></div><div>--Richard</div>
<div><br></div><div><br><div><br></div></div></font></span></div><div><div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, May 3=
1, 2013 at 5:45 PM, Brian Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:=
bcampbell@pingidentity.com" target=3D"_blank">bcampbell@pingidentity.com</a=
>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>




<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>





<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>






<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>






<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>






</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>






</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>






<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>






</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>





</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>


</div>
</div></div></blockquote></div><br></div>

--047d7b471f6a48360004de68d060--

From sakimura@gmail.com  Wed Jun  5 17:32:23 2013
Return-Path: <sakimura@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F42021F86FB for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 17:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.296
X-Spam-Level: ***
X-Spam-Status: No, score=3.296 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, TRACKER_ID=2.696]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uuJPTVNFiXlK for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 17:32:21 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1BD21F86D3 for <jose@ietf.org>; Wed,  5 Jun 2013 17:32:01 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id fe20so2047095lab.34 for <jose@ietf.org>; Wed, 05 Jun 2013 17:31:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kK0f2cf3z5D2/mAYxAQhkl6a9gR+HLaGKVDYP3xd2jA=; b=ThxeI6wqdz6YtaN6hGKR6Wk6uoE90SWKxnIyuGiINre69P+9o59TWVaYWIxGkvp0zU TUdD6p1jnMWQIMuTitwRF0K+rcIbGkRFHsZS0IdXyLmSYsGndPjpPBg5tRUuhvZ2VD1W LeeN3MgE3JyoL2pCW/qd3opRajBl5YoeV7B9Til6Qndnw7vGUtEqYuNUvXdgF1V+g/Ei RSPd9SPAvw3vV1xyZmF4JJFc0mK5rb+pC6nXdsnbQ6UyAYbizNF6p/fyyNbiQXmjbp5U d9XWPRtvjid0W1ognbjb3LtpK2DOujTUzHOR11n4vZ9iPElqvlpYGuP8amkbM7xPxhWb /q8g==
MIME-Version: 1.0
X-Received: by 10.152.170.194 with SMTP id ao2mr16332899lac.48.1370478716169;  Wed, 05 Jun 2013 17:31:56 -0700 (PDT)
Received: by 10.112.4.99 with HTTP; Wed, 5 Jun 2013 17:31:55 -0700 (PDT)
In-Reply-To: <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com> <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com>
Date: Thu, 6 Jun 2013 09:31:55 +0900
Message-ID: <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=089e011615f20cb52a04de7171d6
Cc: Mike Jones <Michael.Jones@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 00:32:23 -0000

--089e011615f20cb52a04de7171d6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

What I was thinking as an example was to have 'datetime' as a public header
parameter to be used generally, and then differentiate between two cases of
'agreement' and 'timestamp'. It is the same signing operation over the
original (e.g., a MS word document), but from an application point of view,
it is a bit different. Former constitute an agreement while the later does
not. The type=3Dtimestamp just signifies that the original document existed
at the time indicated.


2013/6/5 Richard Barnes <rlb@ipv.sx>

> I'm not sure I understand the use case here.  Let me look at a couple of
> options, and hopefully one of them will be what you meant :)
>
> If it's just a signed timestamp you're talking about, then that's
> adequately described by cty=3D"timestamp", typ=3D"JWS".
>
> If you want to sign something and add a timestamp in the header, then
> typ=3D"timestamp" isn't accurate according to the current specification. =
 The
> type of the whole object would have to be something like
> "timestamped-content".  And in that case, an application can easily
> recognized that it's timestamped content by looking for the timestamp fie=
ld
> in the header, so the "typ" isn't really helpful.
>
>
> Moving from the example to the general question:
>
> I think we finally have some common understanding on this list as to what
> Mike means by "typ" in the current document -- a label for the
> application-layer type of the overall object.  Thanks to Mike for
> clarifying that in this discussion.
>
> The question is whether this is a sufficiently useful thing to have in th=
e
> core spec.  Obviously, applications have to know what type of object
> they're dealing with when they get a JOSE object.  That includes (1) what
> type of content is in the payload, and (2) what application-layer fields
> are required to be in the header.  (1) is covered by "cty".  So "typ" is
> only useful in the case where:
> A. The application is storing application-layer data in the JOSE header
> B. The required application-layer fields can be different for different
> objects
> C. The required application-layer fields can be different for different
> objects of the same content type
> D. The required application-layer fields are not indicated by other
> application-layer context
>
> Are there any known applications that meet these criteria?  JWT does not,
> for several reasons.
> 1. (!A) JWT does not store application-layer data in the JOSE header, onl=
y
> in the claims in the body
> 2. (!C) A JWT object can indicate with "cty" that it contains JWT claims
> or another JWT, either of which makes it obvious that this is a JWT
> 3. (!D) In the OAuth context, the Token Type value indicates what type of
> token is being presented, e.g., JWT
>
> So there's not really any known use case for "typ" as currently specified=
.
>  On the other hand, Dick and James have pointed out that it can be useful
> to have "typ" indicate whether the object at hand is a JWE or JWS.  Which
> brings us back to:
> -- Change the definition of "typ" so that it indicates the JOSE-layer typ=
e
> (JWE/JWS)
> -- Remove "typ" altogether
>
>
>
>
>
>
>
> On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <sakimura@gmail.com> wrote:
>
>> What about such as this?
>>
>> cty: original
>> typ: timestamp
>>
>>
>> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>>
>>> It would be a good point, if it were true :)  In particular, this part:
>>> "[dropping 'typ'] is going to cause each and every application that
>>> uses JOSE to define their own field"
>>>
>>> So far, I've heard of exactly one application of JOSE that requires
>>> "typ" in the way it is currently specified, namely JWT.
>>>
>>> On the other hand, Dick's applications are apparently using it
>>> differently (and, IMO, properly) to distinguish JWE/JWS.  Then there ar=
e
>>> all the applications out there that are OK using application context an=
d
>>> "cty" to recognize what type of object they have.  Apps using CMS have =
been
>>> doing this for ages.
>>>
>>> So it's not at all clear to me that there's any other application that
>>> would use "typ" besides JWT.  And it's not clear to me that JWT needs i=
t.
>>>
>>> --Richard
>>>
>>>
>>>
>>>
>>>
>>> On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <
>>> bcampbell@pingidentity.com> wrote:
>>>
>>>> Nat makes a good point here, I think.
>>>>
>>>>
>>>> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com>wrot=
e:
>>>>
>>>>> From what I understand, both typ and cty are something to be consumed
>>>>> by the application and not JOSE processor. From the point of view of =
the
>>>>> JOSE processor, they should be ignored.
>>>>>
>>>>> We could drop both fields from JOSE specs, but that is going to cause
>>>>> each and every application that uses JOSE to define their own field, =
which
>>>>> is a waste. That is why we are defining them here.
>>>>>
>>>>> I would rather drop them than define JOSE processing semantics to
>>>>> these fields.
>>>>>
>>>>>
>>>>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>>>>
>>>>>>  No, =93cty=94 is used by the derived class to determine the type of=
 the
>>>>>> encapsulated field.  But that=92s not a complete description of the =
**entire
>>>>>> object** - especially not the additional meaning imbued by the
>>>>>> additional parameters the derived type may add to the JOSE header.  =
=93typ=94
>>>>>> is there to provide the type of the entire object, including what yo=
u=92re
>>>>>> calling the wrapper parts.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>>                                                             -- Mike*=
*
>>>>>> **
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>>>>
>>>>>> *To:* Mike Jones
>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is a
>>>>>> crypto wrapper around the real application content.  If you're an
>>>>>> application, you know a JOSE object is the thing you want because it
>>>>>> contains the content you want -- it's a JWT because it contains JWT =
claims.
>>>>>> ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Inheritance is the wrong metaphor.  This is encapsulation of
>>>>>> application data:****
>>>>>>
>>>>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>>>>
>>>>>>     jwtClaims =3D jws.content;****
>>>>>>
>>>>>> }****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> --Richard****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>
>>>>>> Thanks for sharing the S/MIME details.  Although I was actually
>>>>>> making the analogy to MIME =96 not S/MIME.  Like many analogies, it=
=92s
>>>>>> imperfect, but I believe still illustrative.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>>>>> structures are used to build application-specific data structures th=
at are
>>>>>> legal JOSE data structures but also have additional properties =96 i=
ncluding
>>>>>> additional header fields with specific semantics.  (When we agreed t=
o
>>>>>> ignore not-understood header fields we let that horse out of the bar=
n.)
>>>>>> For instance, Dick Hardt uses JWEs with issuer and audience fields i=
n the
>>>>>> headers, so they can be used by routing software.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Think of JOSE as the base class and the application types built usin=
g
>>>>>> it as derived classes.  JWT is a derived class.  Dick=92s structures=
 are a
>>>>>> derived class.  These derived classes sometimes need names.  That=92=
s what
>>>>>> =93typ=94 is for.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>                                                             -- Mike*=
*
>>>>>> **
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>>>>
>>>>>>
>>>>>> *To:* Mike Jones
>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> You're mixing up "typ" and "cty".  If you want to make the analogy t=
o
>>>>>> S/MIME, "cty" is the equivalent to Content-Type inside the protected=
 MIME
>>>>>> body; "typ" is the content-type on the outer MIME header.  Pasting i=
n an
>>>>>> example:****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> -----BEGIN-----****
>>>>>>
>>>>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>>>>>>
>>>>>>      name=3Dsmime.p7m****
>>>>>>
>>>>>> Content-Transfer-Encoding: base64****
>>>>>>
>>>>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>>>>
>>>>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>>>>
>>>>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>>>>
>>>>>> 6YT64V0GhIGfHfQbnj75****
>>>>>>
>>>>>> -----END-----****
>>>>>>
>>>>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> The outer Content-Type, which is analogous to "typ", MUST be
>>>>>> application/pkcs7-mime, with a parameter indicating the type of CMS =
object.
>>>>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>>>>> Content-Type (ASN.1/base64 encoded in the example) can be anything, =
just
>>>>>> like "cty".****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> --Richard****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>
>>>>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 wo=
uld be
>>>>>> analogous to the MIME spec requiring that the Content-Type: field be=
 only
>>>>>> =93text/plain=94 or =93message/external-body=94.  It would render it=
 useless.
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>                                                             -- Mike*=
*
>>>>>> **
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>> Behalf Of *Richard Barnes
>>>>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>>>>> *To:* Mike Jones
>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>>>>
>>>>>>
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> If this is the level of "type" you're referring to, I think we shoul=
d
>>>>>> drop it from the spec.  It's an application-layer thing that the app=
 can
>>>>>> add or not according to its wishes.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I'm with Dick on this.  I think we should either have a mandatory
>>>>>> indicator of what type of JOSE object this, or nothing at all.   If =
the
>>>>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" optio=
ns are
>>>>>> non-sensical -- the app needs to know what it's parsing before it ge=
ts this
>>>>>> header.  While I have a preference for the former (for clarity), the=
 latter
>>>>>> approach is also OK with me, since the MIME types are specific to JW=
E/JWS.
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Another approach here would be to address the JSON and compact forms
>>>>>> separately.  The JSON form has no need of "typ" at all, since the ty=
pe of
>>>>>> the object is completely clear from what fields are there, e.g.,
>>>>>> "recipients" vs. "signatures".  For the compact form, we could do so=
mething
>>>>>> like James's "E."/"S." prefix idea, which you need because the
>>>>>> dot-separated components have different meanings and no field names =
to
>>>>>> indicate this.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> --Richard****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <
>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>
>>>>>> A standard library is unlikely to know the meanings of all possible
>>>>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*. =
 It=92s
>>>>>> the application=92s job to determine that =93this blob is a JOSE obj=
ect=94 and
>>>>>> then pass it to a standard library, which will then ignore the =93ty=
p=94 value.
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 means=
.  It won=92t
>>>>>> know what =93typ=94: =93BCGovToken=94 is, should the BC Government w=
ant to declare
>>>>>> that it=92s using a token with particular characteristics.  It won=
=92t know
>>>>>> what =93typ=94: =93XMPP=94 is, should XMPP want to declare that it=
=92s using a JOSE
>>>>>> data structure with particular characteristics.  Etc.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> All these values can be registered in the registry and used by
>>>>>> applications that understand them.  That=92s the application=92s job=
 =96 not the
>>>>>> library=92s job.  The =93typ=94 field is just there so that applicat=
ions have a
>>>>>> standard place to make any such declarations that they may need.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>                                                                 --
>>>>>> Mike****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>>>>> *To:* Mike Jones
>>>>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>>>>
>>>>>>
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I'd prefer to be able to use standard libraries for creating and
>>>>>> parsing tokens, and not specialized libraries dependent on the use c=
ase.
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I strongly think we either drop "typ" or make it required.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <
>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>
>>>>>> It=92s fine for your application to specify that it=92s required for=
 your
>>>>>> use case.  Not applications need it, so they shouldn=92t be forced t=
o pay the
>>>>>> space penalty of an unnecessary field.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>                                                                 --
>>>>>> Mike****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>> Behalf Of *Dick Hardt
>>>>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>>>>
>>>>>>
>>>>>> *To:* Jim Schaad
>>>>>> *Cc:* jose@ietf.org
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I use it all the time and my code would barf if it was not there.***=
*
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I think it should be required rather than be a hint if it is going o=
t
>>>>>> be there.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com>
>>>>>> wrote:****
>>>>>>
>>>>>> I think the values just changed****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> However the way you are using it would be an argument to say that it
>>>>>> should be a required field.  Are you just using it as a hint if it e=
xists
>>>>>> and then looking at the rest of the fields if it is not present?****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Jim****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>>>>> *To:* Jim Schaad
>>>>>> *Cc:* jose@ietf.org
>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Well, I have been using, but now realize the spec changed or I was
>>>>>> confused.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> I had been setting "typ" to be either "JWE" or "JWS" depending on th=
e
>>>>>> type of token I was creating or parsing as it was easier than lookin=
g at
>>>>>> "alg"****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> As currently defined, I don't see value in "typ".****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> -- Dick****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com>
>>>>>> wrote:****
>>>>>>
>>>>>> In reading the documents, I am trying to understand the justificatio=
n
>>>>>> for having the =93typ=94 header parameter in the JOSE documents.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> The purpose of the field is to hold the type of the object.  In the
>>>>>> past, I believe that values which should now be placed in the cty fi=
eld
>>>>>> (such as =93JWT=94) were placed in this field as well.  However the =
parameter
>>>>>> is optional and an implementation cannot rely on its being present. =
 This
>>>>>> means that for all practical purposes all of the code to determine t=
he
>>>>>> value of the type field from the values of the alg and enc fields.  =
If the
>>>>>> field was mandatory then this code would disappear at a fairly small=
 space
>>>>>> cost and I can understand why the parameter would be present.****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Can anybody justify why this field should be present in the document
>>>>>> =96 or should it just disappear?****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> Jim****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jose mailing list
>>>>>> jose@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>
>>>>>>
>>>>>>
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> --
>>>>>> -- Dick ****
>>>>>>
>>>>>>
>>>>>>
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> --
>>>>>> -- Dick ****
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jose mailing list
>>>>>> jose@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>
>>>>>>
>>>>>>
>>>>>> ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> --
>>>>>> -- Dick ****
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jose mailing list
>>>>>> jose@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>>  ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> _______________________________________________
>>>>>> jose mailing list
>>>>>> jose@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Nat Sakimura (=3Dnat)
>>>>> Chairman, OpenID Foundation
>>>>> http://nat.sakimura.org/
>>>>> @_nat_en
>>>>>
>>>>> _______________________________________________
>>>>> jose mailing list
>>>>> jose@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>
>>>>>
>>>>
>>>
>>
>>
>> --
>> Nat Sakimura (=3Dnat)
>> Chairman, OpenID Foundation
>> http://nat.sakimura.org/
>> @_nat_en
>>
>
>


--=20
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en

--089e011615f20cb52a04de7171d6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What I was thinking as an example was to have &#39;datetim=
e&#39; as a public header parameter to be used generally, and then differen=
tiate between two cases of &#39;agreement&#39; and &#39;timestamp&#39;. It =
is the same signing operation over the original (e.g., a MS word document),=
 but from an application point of view, it is a bit different. Former const=
itute an agreement while the later does not. The type=3Dtimestamp just sign=
ifies that the original document existed at the time indicated.=A0</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5 Rich=
ard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_b=
lank">rlb@ipv.sx</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">I&#39;m not sure I understand the use case here. =A0Let me=
 look at a couple of options, and hopefully one of them will be what you me=
ant :) =A0<div><br></div><div>If it&#39;s just a signed timestamp you&#39;r=
e talking about, then that&#39;s adequately described by cty=3D&quot;timest=
amp&quot;, typ=3D&quot;JWS&quot;.</div>

<div><br></div><div>If you want to sign something and add a timestamp in th=
e header, then typ=3D&quot;timestamp&quot; isn&#39;t accurate according to =
the current specification. =A0The type of the whole object would have to be=
 something like &quot;timestamped-content&quot;. =A0And in that case, an ap=
plication can easily recognized that it&#39;s timestamped content by lookin=
g for the timestamp field in the header, so the &quot;typ&quot; isn&#39;t r=
eally helpful.</div>

<div><br></div><div><br></div><div>Moving from the example to the general q=
uestion:</div><div><br></div><div>I think we finally have some common under=
standing on this list as to what Mike means by &quot;typ&quot; in the curre=
nt document -- a label for the application-layer type of the overall object=
. =A0Thanks to Mike for clarifying that in this discussion.</div>

<div><br></div><div>The question is whether this is a sufficiently useful t=
hing to have in the core spec. =A0Obviously, applications have to know what=
 type of object they&#39;re dealing with when they get a JOSE object. =A0Th=
at includes (1) what type of content is in the payload, and (2) what applic=
ation-layer fields are required to be in the header. =A0(1) is covered by &=
quot;cty&quot;. =A0So &quot;typ&quot; is only useful in the case where:</di=
v>

<div>A. The application is storing application-layer data in the JOSE heade=
r</div><div>B. The required application-layer fields can be different for d=
ifferent objects</div><div>C. The required application-layer fields can be =
different for different objects of the same content type</div>

<div>D. The required application-layer fields are not indicated by other ap=
plication-layer context</div><div><br></div><div>Are there any known applic=
ations that meet these criteria? =A0JWT does not, for several reasons.=A0</=
div>

<div>1. (!A) JWT does not store application-layer data in the JOSE header, =
only in the claims in the body</div><div>2. (!C) A JWT object can indicate =
with &quot;cty&quot; that it contains JWT claims or another JWT, either of =
which makes it obvious that this is a JWT</div>

<div>3. (!D) In the OAuth context, the Token Type value indicates what type=
 of token is being presented, e.g., JWT</div><div><br></div><div>So there&#=
39;s not really any known use case for &quot;typ&quot; as currently specifi=
ed. =A0On the other hand, Dick and James have pointed out that it can be us=
eful to have &quot;typ&quot; indicate whether the object at hand is a JWE o=
r JWS. =A0Which brings us back to:</div>

<div>-- Change the definition of &quot;typ&quot; so that it indicates the J=
OSE-layer type (JWE/JWS)</div><div>-- Remove &quot;typ&quot; altogether</di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br>

</div></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">On Wed, Jun 5, 2013 at 8:53 AM, Nat =
Sakimura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=
=3D"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>What about such as thi=
s?=A0</div><div><br></div>cty: original<div>typ: timestamp</div></div><div>
<div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5=
 Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">It would be a good point, i=
f it were true :) =A0In particular, this part: &quot;[dropping &#39;typ&#39=
;]<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:=
13px">=A0is going to cause each and every application that uses JOSE to def=
ine their own field</span>&quot;<div>



<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>



<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><span><font color=3D"#888888"><=
div>


<br></div><div>--Richard</div>
<div><br></div><div><br><div><br></div></div></font></span></div><div><div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, May 3=
1, 2013 at 5:45 PM, Brian Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:=
bcampbell@pingidentity.com" target=3D"_blank">bcampbell@pingidentity.com</a=
>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>





<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>






<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>







<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>







<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>







</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>







</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>







<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>







</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>






</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>



</div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>

</div>

--089e011615f20cb52a04de7171d6--

From dick.hardt@gmail.com  Wed Jun  5 17:36:06 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CC921F882A for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 17:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.296
X-Spam-Level: ***
X-Spam-Status: No, score=3.296 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, TRACKER_ID=2.696]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRrTqRs7TzEz for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 17:36:03 -0700 (PDT)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 08C1C21F86D3 for <jose@ietf.org>; Wed,  5 Jun 2013 17:36:02 -0700 (PDT)
Received: by mail-bk0-f53.google.com with SMTP id e11so663693bkh.40 for <jose@ietf.org>; Wed, 05 Jun 2013 17:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yz+nXPlQYMs+flK+lew9qQYmXwWL/cTKbXyAGrXBYvs=; b=WLORkWR7HXKPPu7KjRQuYFeKtsn5h399+5sZM1cISXd8iixJzL7fUsqsZIB61F561A eVQqsCizCUKGFUfLU6WAhUNwbdB24S2NC35DkGilYbYAviuZcLW1JffyJi0g5k4z+Vcl D1aTR8waRZEuO7cGdcgBMk6/8RWsSB9QPHe+m0Vw86md90JaWbi6tCfSCvqbf+/6Nvh9 D4LJgRsJgRvTMlQuxpxV+97geP3h0WwacKpvSfo/XYxObPS5ZdVR7UUgY0NIPWy+z6b2 aNiKx7mqfKSTwJXMSbv7zsxlp1YdBMrLGKT+tG+K4gt11dXnoWBmTHUSw7UU+y6c/QVP /A8w==
MIME-Version: 1.0
X-Received: by 10.204.108.4 with SMTP id d4mr10421211bkp.176.1370478961972; Wed, 05 Jun 2013 17:36:01 -0700 (PDT)
Received: by 10.204.228.8 with HTTP; Wed, 5 Jun 2013 17:36:01 -0700 (PDT)
In-Reply-To: <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com> <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com> <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>
Date: Wed, 5 Jun 2013 17:36:01 -0700
Message-ID: <CAD9ie-s1uWSsRDJHb8Z_NPQvuAWWJmYPkTp8g_PbacA5gaqT1w@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
To: Nat Sakimura <sakimura@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122ecfab39cac04de717f87
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 00:36:06 -0000

--089e0122ecfab39cac04de717f87
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Why would you need that in the header? Why not in the payload?


On Wed, Jun 5, 2013 at 5:31 PM, Nat Sakimura <sakimura@gmail.com> wrote:

> What I was thinking as an example was to have 'datetime' as a public
> header parameter to be used generally, and then differentiate between two
> cases of 'agreement' and 'timestamp'. It is the same signing operation ov=
er
> the original (e.g., a MS word document), but from an application point of
> view, it is a bit different. Former constitute an agreement while the lat=
er
> does not. The type=3Dtimestamp just signifies that the original document
> existed at the time indicated.
>
>
> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>
>> I'm not sure I understand the use case here.  Let me look at a couple of
>> options, and hopefully one of them will be what you meant :)
>>
>> If it's just a signed timestamp you're talking about, then that's
>> adequately described by cty=3D"timestamp", typ=3D"JWS".
>>
>> If you want to sign something and add a timestamp in the header, then
>> typ=3D"timestamp" isn't accurate according to the current specification.=
  The
>> type of the whole object would have to be something like
>> "timestamped-content".  And in that case, an application can easily
>> recognized that it's timestamped content by looking for the timestamp fi=
eld
>> in the header, so the "typ" isn't really helpful.
>>
>>
>> Moving from the example to the general question:
>>
>> I think we finally have some common understanding on this list as to wha=
t
>> Mike means by "typ" in the current document -- a label for the
>> application-layer type of the overall object.  Thanks to Mike for
>> clarifying that in this discussion.
>>
>> The question is whether this is a sufficiently useful thing to have in
>> the core spec.  Obviously, applications have to know what type of object
>> they're dealing with when they get a JOSE object.  That includes (1) wha=
t
>> type of content is in the payload, and (2) what application-layer fields
>> are required to be in the header.  (1) is covered by "cty".  So "typ" is
>> only useful in the case where:
>> A. The application is storing application-layer data in the JOSE header
>> B. The required application-layer fields can be different for different
>> objects
>> C. The required application-layer fields can be different for different
>> objects of the same content type
>> D. The required application-layer fields are not indicated by other
>> application-layer context
>>
>> Are there any known applications that meet these criteria?  JWT does not=
,
>> for several reasons.
>> 1. (!A) JWT does not store application-layer data in the JOSE header,
>> only in the claims in the body
>> 2. (!C) A JWT object can indicate with "cty" that it contains JWT claims
>> or another JWT, either of which makes it obvious that this is a JWT
>> 3. (!D) In the OAuth context, the Token Type value indicates what type o=
f
>> token is being presented, e.g., JWT
>>
>> So there's not really any known use case for "typ" as currently
>> specified.  On the other hand, Dick and James have pointed out that it c=
an
>> be useful to have "typ" indicate whether the object at hand is a JWE or
>> JWS.  Which brings us back to:
>> -- Change the definition of "typ" so that it indicates the JOSE-layer
>> type (JWE/JWS)
>> -- Remove "typ" altogether
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <sakimura@gmail.com> wrote:
>>
>>> What about such as this?
>>>
>>> cty: original
>>> typ: timestamp
>>>
>>>
>>> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>>>
>>>> It would be a good point, if it were true :)  In particular, this part=
:
>>>> "[dropping 'typ'] is going to cause each and every application that
>>>> uses JOSE to define their own field"
>>>>
>>>> So far, I've heard of exactly one application of JOSE that requires
>>>> "typ" in the way it is currently specified, namely JWT.
>>>>
>>>> On the other hand, Dick's applications are apparently using it
>>>> differently (and, IMO, properly) to distinguish JWE/JWS.  Then there a=
re
>>>> all the applications out there that are OK using application context a=
nd
>>>> "cty" to recognize what type of object they have.  Apps using CMS have=
 been
>>>> doing this for ages.
>>>>
>>>> So it's not at all clear to me that there's any other application that
>>>> would use "typ" besides JWT.  And it's not clear to me that JWT needs =
it.
>>>>
>>>> --Richard
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <
>>>> bcampbell@pingidentity.com> wrote:
>>>>
>>>>> Nat makes a good point here, I think.
>>>>>
>>>>>
>>>>> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com>wro=
te:
>>>>>
>>>>>> From what I understand, both typ and cty are something to be consume=
d
>>>>>> by the application and not JOSE processor. From the point of view of=
 the
>>>>>> JOSE processor, they should be ignored.
>>>>>>
>>>>>> We could drop both fields from JOSE specs, but that is going to caus=
e
>>>>>> each and every application that uses JOSE to define their own field,=
 which
>>>>>> is a waste. That is why we are defining them here.
>>>>>>
>>>>>> I would rather drop them than define JOSE processing semantics to
>>>>>> these fields.
>>>>>>
>>>>>>
>>>>>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>>>>>
>>>>>>>  No, =93cty=94 is used by the derived class to determine the type o=
f
>>>>>>> the encapsulated field.  But that=92s not a complete description of=
 the *
>>>>>>> *entire object** - especially not the additional meaning imbued by
>>>>>>> the additional parameters the derived type may add to the JOSE head=
er.
>>>>>>> =93typ=94 is there to provide the type of the entire object, includ=
ing what
>>>>>>> you=92re calling the wrapper parts.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>>                                                             -- Mike=
*
>>>>>>> ***
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>>>>>
>>>>>>> *To:* Mike Jones
>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is a
>>>>>>> crypto wrapper around the real application content.  If you're an
>>>>>>> application, you know a JOSE object is the thing you want because i=
t
>>>>>>> contains the content you want -- it's a JWT because it contains JWT=
 claims.
>>>>>>> ****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Inheritance is the wrong metaphor.  This is encapsulation of
>>>>>>> application data:****
>>>>>>>
>>>>>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>>>>>
>>>>>>>     jwtClaims =3D jws.content;****
>>>>>>>
>>>>>>> }****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> --Richard****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>
>>>>>>> Thanks for sharing the S/MIME details.  Although I was actually
>>>>>>> making the analogy to MIME =96 not S/MIME.  Like many analogies, it=
=92s
>>>>>>> imperfect, but I believe still illustrative.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>>>>>> structures are used to build application-specific data structures t=
hat are
>>>>>>> legal JOSE data structures but also have additional properties =96 =
including
>>>>>>> additional header fields with specific semantics.  (When we agreed =
to
>>>>>>> ignore not-understood header fields we let that horse out of the ba=
rn.)
>>>>>>> For instance, Dick Hardt uses JWEs with issuer and audience fields =
in the
>>>>>>> headers, so they can be used by routing software.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Think of JOSE as the base class and the application types built
>>>>>>> using it as derived classes.  JWT is a derived class.  Dick=92s str=
uctures
>>>>>>> are a derived class.  These derived classes sometimes need names.  =
That=92s
>>>>>>> what =93typ=94 is for.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>                                                             -- Mike=
*
>>>>>>> ***
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>>>>>
>>>>>>>
>>>>>>> *To:* Mike Jones
>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> You're mixing up "typ" and "cty".  If you want to make the analogy
>>>>>>> to S/MIME, "cty" is the equivalent to Content-Type inside the prote=
cted
>>>>>>> MIME body; "typ" is the content-type on the outer MIME header.  Pas=
ting in
>>>>>>> an example:****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> -----BEGIN-----****
>>>>>>>
>>>>>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>>>>>>>
>>>>>>>      name=3Dsmime.p7m****
>>>>>>>
>>>>>>> Content-Transfer-Encoding: base64****
>>>>>>>
>>>>>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>>>>>
>>>>>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>>>>>
>>>>>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>>>>>
>>>>>>> 6YT64V0GhIGfHfQbnj75****
>>>>>>>
>>>>>>> -----END-----****
>>>>>>>
>>>>>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> The outer Content-Type, which is analogous to "typ", MUST be
>>>>>>> application/pkcs7-mime, with a parameter indicating the type of CMS=
 object.
>>>>>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>>>>>> Content-Type (ASN.1/base64 encoded in the example) can be anything,=
 just
>>>>>>> like "cty".****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> --Richard****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>
>>>>>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 w=
ould be
>>>>>>> analogous to the MIME spec requiring that the Content-Type: field b=
e only
>>>>>>> =93text/plain=94 or =93message/external-body=94.  It would render i=
t useless.
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>                                                             -- Mike=
*
>>>>>>> ***
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>>> Behalf Of *Richard Barnes
>>>>>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>>>>>> *To:* Mike Jones
>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>>>>>
>>>>>>>
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> If this is the level of "type" you're referring to, I think we
>>>>>>> should drop it from the spec.  It's an application-layer thing that=
 the app
>>>>>>> can add or not according to its wishes.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I'm with Dick on this.  I think we should either have a mandatory
>>>>>>> indicator of what type of JOSE object this, or nothing at all.   If=
 the
>>>>>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" opti=
ons are
>>>>>>> non-sensical -- the app needs to know what it's parsing before it g=
ets this
>>>>>>> header.  While I have a preference for the former (for clarity), th=
e latter
>>>>>>> approach is also OK with me, since the MIME types are specific to J=
WE/JWS.
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Another approach here would be to address the JSON and compact form=
s
>>>>>>> separately.  The JSON form has no need of "typ" at all, since the t=
ype of
>>>>>>> the object is completely clear from what fields are there, e.g.,
>>>>>>> "recipients" vs. "signatures".  For the compact form, we could do s=
omething
>>>>>>> like James's "E."/"S." prefix idea, which you need because the
>>>>>>> dot-separated components have different meanings and no field names=
 to
>>>>>>> indicate this.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> --Richard****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <
>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>
>>>>>>> A standard library is unlikely to know the meanings of all possible
>>>>>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*.=
  It=92s
>>>>>>> the application=92s job to determine that =93this blob is a JOSE ob=
ject=94 and
>>>>>>> then pass it to a standard library, which will then ignore the =93t=
yp=94 value.
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 mean=
s.  It
>>>>>>> won=92t know what =93typ=94: =93BCGovToken=94 is, should the BC Gov=
ernment want to
>>>>>>> declare that it=92s using a token with particular characteristics. =
 It won=92t
>>>>>>> know what =93typ=94: =93XMPP=94 is, should XMPP want to declare tha=
t it=92s using a
>>>>>>> JOSE data structure with particular characteristics.  Etc.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> All these values can be registered in the registry and used by
>>>>>>> applications that understand them.  That=92s the application=92s jo=
b =96 not the
>>>>>>> library=92s job.  The =93typ=94 field is just there so that applica=
tions have a
>>>>>>> standard place to make any such declarations that they may need.***=
*
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>                                                                 --
>>>>>>> Mike****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>>>>>> *To:* Mike Jones
>>>>>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>>>>>
>>>>>>>
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I'd prefer to be able to use standard libraries for creating and
>>>>>>> parsing tokens, and not specialized libraries dependent on the use =
case.
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I strongly think we either drop "typ" or make it required.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <
>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>
>>>>>>> It=92s fine for your application to specify that it=92s required fo=
r
>>>>>>> your use case.  Not applications need it, so they shouldn=92t be fo=
rced to
>>>>>>> pay the space penalty of an unnecessary field.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>                                                                 --
>>>>>>> Mike****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>>> Behalf Of *Dick Hardt
>>>>>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>>>>>
>>>>>>>
>>>>>>> *To:* Jim Schaad
>>>>>>> *Cc:* jose@ietf.org
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I use it all the time and my code would barf if it was not there.**=
*
>>>>>>> *
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I think it should be required rather than be a hint if it is going
>>>>>>> ot be there.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com=
>
>>>>>>> wrote:****
>>>>>>>
>>>>>>> I think the values just changed****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> However the way you are using it would be an argument to say that i=
t
>>>>>>> should be a required field.  Are you just using it as a hint if it =
exists
>>>>>>> and then looking at the rest of the fields if it is not present?***=
*
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Jim****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>>>>>> *To:* Jim Schaad
>>>>>>> *Cc:* jose@ietf.org
>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Well, I have been using, but now realize the spec changed or I was
>>>>>>> confused.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> I had been setting "typ" to be either "JWE" or "JWS" depending on
>>>>>>> the type of token I was creating or parsing as it was easier than l=
ooking
>>>>>>> at "alg"****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> As currently defined, I don't see value in "typ".****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> -- Dick****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com=
>
>>>>>>> wrote:****
>>>>>>>
>>>>>>> In reading the documents, I am trying to understand the
>>>>>>> justification for having the =93typ=94 header parameter in the JOSE=
 documents.
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> The purpose of the field is to hold the type of the object.  In the
>>>>>>> past, I believe that values which should now be placed in the cty f=
ield
>>>>>>> (such as =93JWT=94) were placed in this field as well.  However the=
 parameter
>>>>>>> is optional and an implementation cannot rely on its being present.=
  This
>>>>>>> means that for all practical purposes all of the code to determine =
the
>>>>>>> value of the type field from the values of the alg and enc fields. =
 If the
>>>>>>> field was mandatory then this code would disappear at a fairly smal=
l space
>>>>>>> cost and I can understand why the parameter would be present.****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Can anybody justify why this field should be present in the documen=
t
>>>>>>> =96 or should it just disappear?****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> Jim****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jose mailing list
>>>>>>> jose@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> --
>>>>>>> -- Dick ****
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> --
>>>>>>> -- Dick ****
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jose mailing list
>>>>>>> jose@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> --
>>>>>>> -- Dick ****
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jose mailing list
>>>>>>> jose@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>>  ****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jose mailing list
>>>>>>> jose@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nat Sakimura (=3Dnat)
>>>>>> Chairman, OpenID Foundation
>>>>>> http://nat.sakimura.org/
>>>>>> @_nat_en
>>>>>>
>>>>>> _______________________________________________
>>>>>> jose mailing list
>>>>>> jose@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Nat Sakimura (=3Dnat)
>>> Chairman, OpenID Foundation
>>> http://nat.sakimura.org/
>>> @_nat_en
>>>
>>
>>
>
>
> --
> Nat Sakimura (=3Dnat)
> Chairman, OpenID Foundation
> http://nat.sakimura.org/
> @_nat_en
>



--=20
-- Dick

--089e0122ecfab39cac04de717f87
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Why would you need that in the header? Why not in the payl=
oad?</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Wed, Jun 5, 2013 at 5:31 PM, Nat Sakimura <span dir=3D"ltr">&lt;<a href=3D"=
mailto:sakimura@gmail.com" target=3D"_blank">sakimura@gmail.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">What I was thinking as an e=
xample was to have &#39;datetime&#39; as a public header parameter to be us=
ed generally, and then differentiate between two cases of &#39;agreement&#3=
9; and &#39;timestamp&#39;. It is the same signing operation over the origi=
nal (e.g., a MS word document), but from an application point of view, it i=
s a bit different. Former constitute an agreement while the later does not.=
 The type=3Dtimestamp just signifies that the original document existed at =
the time indicated.=A0</div>
<div class=3D"HOEnZb"><div class=3D"h5">
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5 Rich=
ard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_b=
lank">rlb@ipv.sx</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr">I&#39;m not sure I understand the use case here. =A0Let me=
 look at a couple of options, and hopefully one of them will be what you me=
ant :) =A0<div><br></div><div>If it&#39;s just a signed timestamp you&#39;r=
e talking about, then that&#39;s adequately described by cty=3D&quot;timest=
amp&quot;, typ=3D&quot;JWS&quot;.</div>


<div><br></div><div>If you want to sign something and add a timestamp in th=
e header, then typ=3D&quot;timestamp&quot; isn&#39;t accurate according to =
the current specification. =A0The type of the whole object would have to be=
 something like &quot;timestamped-content&quot;. =A0And in that case, an ap=
plication can easily recognized that it&#39;s timestamped content by lookin=
g for the timestamp field in the header, so the &quot;typ&quot; isn&#39;t r=
eally helpful.</div>


<div><br></div><div><br></div><div>Moving from the example to the general q=
uestion:</div><div><br></div><div>I think we finally have some common under=
standing on this list as to what Mike means by &quot;typ&quot; in the curre=
nt document -- a label for the application-layer type of the overall object=
. =A0Thanks to Mike for clarifying that in this discussion.</div>


<div><br></div><div>The question is whether this is a sufficiently useful t=
hing to have in the core spec. =A0Obviously, applications have to know what=
 type of object they&#39;re dealing with when they get a JOSE object. =A0Th=
at includes (1) what type of content is in the payload, and (2) what applic=
ation-layer fields are required to be in the header. =A0(1) is covered by &=
quot;cty&quot;. =A0So &quot;typ&quot; is only useful in the case where:</di=
v>


<div>A. The application is storing application-layer data in the JOSE heade=
r</div><div>B. The required application-layer fields can be different for d=
ifferent objects</div><div>C. The required application-layer fields can be =
different for different objects of the same content type</div>


<div>D. The required application-layer fields are not indicated by other ap=
plication-layer context</div><div><br></div><div>Are there any known applic=
ations that meet these criteria? =A0JWT does not, for several reasons.=A0</=
div>


<div>1. (!A) JWT does not store application-layer data in the JOSE header, =
only in the claims in the body</div><div>2. (!C) A JWT object can indicate =
with &quot;cty&quot; that it contains JWT claims or another JWT, either of =
which makes it obvious that this is a JWT</div>


<div>3. (!D) In the OAuth context, the Token Type value indicates what type=
 of token is being presented, e.g., JWT</div><div><br></div><div>So there&#=
39;s not really any known use case for &quot;typ&quot; as currently specifi=
ed. =A0On the other hand, Dick and James have pointed out that it can be us=
eful to have &quot;typ&quot; indicate whether the object at hand is a JWE o=
r JWS. =A0Which brings us back to:</div>


<div>-- Change the definition of &quot;typ&quot; so that it indicates the J=
OSE-layer type (JWE/JWS)</div><div>-- Remove &quot;typ&quot; altogether</di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br>


</div></div><div><div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sakimura@gmail.com" target=3D"_blank">sakimura@gmail.com=
</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>What about such as thi=
s?=A0</div><div><br></div>cty: original<div>typ: timestamp</div></div><div>
<div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5=
 Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">It would be a good point, i=
f it were true :) =A0In particular, this part: &quot;[dropping &#39;typ&#39=
;]<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:=
13px">=A0is going to cause each and every application that uses JOSE to def=
ine their own field</span>&quot;<div>




<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>




<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><span><font color=3D"#888888"><=
div>



<br></div><div>--Richard</div>
<div><br></div><div><br><div><br></div></div></font></span></div><div><div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, May 3=
1, 2013 at 5:45 PM, Brian Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:=
bcampbell@pingidentity.com" target=3D"_blank">bcampbell@pingidentity.com</a=
>&gt;</span> wrote:<br>




<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>






<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>







<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>








<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>








<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>








</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>








</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>








<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>








</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>







</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>




</div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>


</div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
-- Dick
</div>

--089e0122ecfab39cac04de717f87--

From sakimura@gmail.com  Wed Jun  5 18:03:59 2013
Return-Path: <sakimura@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C1121F944C for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 18:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.296
X-Spam-Level: ***
X-Spam-Status: No, score=3.296 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001, TRACKER_ID=2.696]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sDG7vNgGwAcb for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 18:03:57 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DF38B21F9425 for <jose@ietf.org>; Wed,  5 Jun 2013 18:03:56 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id hu16so101976qab.8 for <jose@ietf.org>; Wed, 05 Jun 2013 18:03:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XiGpHmur8t4ddeQr7KNqKR6p8uezUIL9+gqRwwDD7WI=; b=qZDckMxQkHErHZYPSsEJ6WhmkxF7EDtT391YzDu+x8wayaXGt0l71X0ut1cGd5olx6 w3Sd1te05gABQ/s26soBFKPdDa+UidHlR3q4NB9KgRSi2pEwuwvjy21+2Px4rGIRe7il EI7rFLHg6bFQjGfdsKrghIruYuZB2UXEiFabenjZ08RH1H3aKLN1IAt/mxRjwwg4h1tN LE4mytldgRu2E5/Yx1ntjQzG2cClViZcJqi2b3yeWByIvnI7sG7QEVLxkEecQyq8QYp9 mXi+dFKW8UykIS53FgRtryRMJUug9plChgbG1MMt10fTsl87ip+31EVMWoKCMPOsHcPf IcHw==
MIME-Version: 1.0
X-Received: by 10.49.101.74 with SMTP id fe10mr6127853qeb.11.1370480636245; Wed, 05 Jun 2013 18:03:56 -0700 (PDT)
Received: by 10.49.95.230 with HTTP; Wed, 5 Jun 2013 18:03:56 -0700 (PDT)
In-Reply-To: <CAD9ie-s1uWSsRDJHb8Z_NPQvuAWWJmYPkTp8g_PbacA5gaqT1w@mail.gmail.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com> <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com> <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com> <CAD9ie-s1uWSsRDJHb8Z_NPQvuAWWJmYPkTp8g_PbacA5gaqT1w@mail.gmail.com>
Date: Thu, 6 Jun 2013 10:03:56 +0900
Message-ID: <CABzCy2Abnv=Cm=nSN2t4b+B=G-rBrza6nrK+VPxqWUcTFpZEYw@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
To: Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2c6ce7f04f204de71e38e
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 01:03:59 -0000

--001a11c2c6ce7f04f204de71e38e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It is giving the meaning to the signature - metadata about the signature,
so I thought header would be more appropriate, besides, the payload is
binary and I can avoid double base64 encoding that way.


2013/6/6 Dick Hardt <dick.hardt@gmail.com>

> Why would you need that in the header? Why not in the payload?
>
>
> On Wed, Jun 5, 2013 at 5:31 PM, Nat Sakimura <sakimura@gmail.com> wrote:
>
>> What I was thinking as an example was to have 'datetime' as a public
>> header parameter to be used generally, and then differentiate between tw=
o
>> cases of 'agreement' and 'timestamp'. It is the same signing operation o=
ver
>> the original (e.g., a MS word document), but from an application point o=
f
>> view, it is a bit different. Former constitute an agreement while the la=
ter
>> does not. The type=3Dtimestamp just signifies that the original document
>> existed at the time indicated.
>>
>>
>> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>>
>>> I'm not sure I understand the use case here.  Let me look at a couple o=
f
>>> options, and hopefully one of them will be what you meant :)
>>>
>>> If it's just a signed timestamp you're talking about, then that's
>>> adequately described by cty=3D"timestamp", typ=3D"JWS".
>>>
>>> If you want to sign something and add a timestamp in the header, then
>>> typ=3D"timestamp" isn't accurate according to the current specification=
.  The
>>> type of the whole object would have to be something like
>>> "timestamped-content".  And in that case, an application can easily
>>> recognized that it's timestamped content by looking for the timestamp f=
ield
>>> in the header, so the "typ" isn't really helpful.
>>>
>>>
>>> Moving from the example to the general question:
>>>
>>> I think we finally have some common understanding on this list as to
>>> what Mike means by "typ" in the current document -- a label for the
>>> application-layer type of the overall object.  Thanks to Mike for
>>> clarifying that in this discussion.
>>>
>>> The question is whether this is a sufficiently useful thing to have in
>>> the core spec.  Obviously, applications have to know what type of objec=
t
>>> they're dealing with when they get a JOSE object.  That includes (1) wh=
at
>>> type of content is in the payload, and (2) what application-layer field=
s
>>> are required to be in the header.  (1) is covered by "cty".  So "typ" i=
s
>>> only useful in the case where:
>>> A. The application is storing application-layer data in the JOSE header
>>> B. The required application-layer fields can be different for different
>>> objects
>>> C. The required application-layer fields can be different for different
>>> objects of the same content type
>>> D. The required application-layer fields are not indicated by other
>>> application-layer context
>>>
>>> Are there any known applications that meet these criteria?  JWT does
>>> not, for several reasons.
>>> 1. (!A) JWT does not store application-layer data in the JOSE header,
>>> only in the claims in the body
>>> 2. (!C) A JWT object can indicate with "cty" that it contains JWT claim=
s
>>> or another JWT, either of which makes it obvious that this is a JWT
>>> 3. (!D) In the OAuth context, the Token Type value indicates what type
>>> of token is being presented, e.g., JWT
>>>
>>> So there's not really any known use case for "typ" as currently
>>> specified.  On the other hand, Dick and James have pointed out that it =
can
>>> be useful to have "typ" indicate whether the object at hand is a JWE or
>>> JWS.  Which brings us back to:
>>> -- Change the definition of "typ" so that it indicates the JOSE-layer
>>> type (JWE/JWS)
>>> -- Remove "typ" altogether
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <sakimura@gmail.com> wrote=
:
>>>
>>>> What about such as this?
>>>>
>>>> cty: original
>>>> typ: timestamp
>>>>
>>>>
>>>> 2013/6/5 Richard Barnes <rlb@ipv.sx>
>>>>
>>>>> It would be a good point, if it were true :)  In particular, this
>>>>> part: "[dropping 'typ'] is going to cause each and every application
>>>>> that uses JOSE to define their own field"
>>>>>
>>>>> So far, I've heard of exactly one application of JOSE that requires
>>>>> "typ" in the way it is currently specified, namely JWT.
>>>>>
>>>>> On the other hand, Dick's applications are apparently using it
>>>>> differently (and, IMO, properly) to distinguish JWE/JWS.  Then there =
are
>>>>> all the applications out there that are OK using application context =
and
>>>>> "cty" to recognize what type of object they have.  Apps using CMS hav=
e been
>>>>> doing this for ages.
>>>>>
>>>>> So it's not at all clear to me that there's any other application tha=
t
>>>>> would use "typ" besides JWT.  And it's not clear to me that JWT needs=
 it.
>>>>>
>>>>> --Richard
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <
>>>>> bcampbell@pingidentity.com> wrote:
>>>>>
>>>>>> Nat makes a good point here, I think.
>>>>>>
>>>>>>
>>>>>> On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com>wr=
ote:
>>>>>>
>>>>>>> From what I understand, both typ and cty are something to be
>>>>>>> consumed by the application and not JOSE processor. From the point =
of view
>>>>>>> of the JOSE processor, they should be ignored.
>>>>>>>
>>>>>>> We could drop both fields from JOSE specs, but that is going to
>>>>>>> cause each and every application that uses JOSE to define their own=
 field,
>>>>>>> which is a waste. That is why we are defining them here.
>>>>>>>
>>>>>>> I would rather drop them than define JOSE processing semantics to
>>>>>>> these fields.
>>>>>>>
>>>>>>>
>>>>>>> 2013/5/31 Mike Jones <Michael.Jones@microsoft.com>
>>>>>>>
>>>>>>>>  No, =93cty=94 is used by the derived class to determine the type =
of
>>>>>>>> the encapsulated field.  But that=92s not a complete description o=
f the *
>>>>>>>> *entire object** - especially not the additional meaning imbued by
>>>>>>>> the additional parameters the derived type may add to the JOSE hea=
der.
>>>>>>>> =93typ=94 is there to provide the type of the entire object, inclu=
ding what
>>>>>>>> you=92re calling the wrapper parts.****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>>                                                             -- Mik=
e
>>>>>>>> ****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>>>> *Sent:* Thursday, May 30, 2013 7:58 AM
>>>>>>>>
>>>>>>>> *To:* Mike Jones
>>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> Isn't that requirement met by "cty"?  The only thing JOSE adds is =
a
>>>>>>>> crypto wrapper around the real application content.  If you're an
>>>>>>>> application, you know a JOSE object is the thing you want because =
it
>>>>>>>> contains the content you want -- it's a JWT because it contains JW=
T claims.
>>>>>>>> ****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> Inheritance is the wrong metaphor.  This is encapsulation of
>>>>>>>> application data:****
>>>>>>>>
>>>>>>>> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>>>>>>>>
>>>>>>>>     jwtClaims =3D jws.content;****
>>>>>>>>
>>>>>>>> }****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> --Richard****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <
>>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>>
>>>>>>>> Thanks for sharing the S/MIME details.  Although I was actually
>>>>>>>> making the analogy to MIME =96 not S/MIME.  Like many analogies, i=
t=92s
>>>>>>>> imperfect, but I believe still illustrative.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> The reason that the analogy isn=92t perfect is that the JOSE data
>>>>>>>> structures are used to build application-specific data structures =
that are
>>>>>>>> legal JOSE data structures but also have additional properties =96=
 including
>>>>>>>> additional header fields with specific semantics.  (When we agreed=
 to
>>>>>>>> ignore not-understood header fields we let that horse out of the b=
arn.)
>>>>>>>> For instance, Dick Hardt uses JWEs with issuer and audience fields=
 in the
>>>>>>>> headers, so they can be used by routing software.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Think of JOSE as the base class and the application types built
>>>>>>>> using it as derived classes.  JWT is a derived class.  Dick=92s st=
ructures
>>>>>>>> are a derived class.  These derived classes sometimes need names. =
 That=92s
>>>>>>>> what =93typ=94 is for.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>                                                             -- Mik=
e
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>>>>>>> *Sent:* Thursday, May 30, 2013 7:34 AM****
>>>>>>>>
>>>>>>>>
>>>>>>>> *To:* Mike Jones
>>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> You're mixing up "typ" and "cty".  If you want to make the analogy
>>>>>>>> to S/MIME, "cty" is the equivalent to Content-Type inside the prot=
ected
>>>>>>>> MIME body; "typ" is the content-type on the outer MIME header.  Pa=
sting in
>>>>>>>> an example:****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> -----BEGIN-----****
>>>>>>>>
>>>>>>>> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;***=
*
>>>>>>>>
>>>>>>>>      name=3Dsmime.p7m****
>>>>>>>>
>>>>>>>> Content-Transfer-Encoding: base64****
>>>>>>>>
>>>>>>>> Content-Disposition: attachment; filename=3Dsmime.p7m****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>>>>>>>>
>>>>>>>> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>>>>>>>>
>>>>>>>> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>>>>>>>>
>>>>>>>> 6YT64V0GhIGfHfQbnj75****
>>>>>>>>
>>>>>>>> -----END-----****
>>>>>>>>
>>>>>>>> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> The outer Content-Type, which is analogous to "typ", MUST be
>>>>>>>> application/pkcs7-mime, with a parameter indicating the type of CM=
S object.
>>>>>>>>  This is the same as requiring "typ" to be JWE or JWS.  The inner
>>>>>>>> Content-Type (ASN.1/base64 encoded in the example) can be anything=
, just
>>>>>>>> like "cty".****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> --Richard****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <
>>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>>
>>>>>>>> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 =
would be
>>>>>>>> analogous to the MIME spec requiring that the Content-Type: field =
be only
>>>>>>>> =93text/plain=94 or =93message/external-body=94.  It would render =
it useless.
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>                                                             -- Mik=
e
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>>>> Behalf Of *Richard Barnes
>>>>>>>> *Sent:* Wednesday, May 29, 2013 8:03 PM
>>>>>>>> *To:* Mike Jones
>>>>>>>> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>>>>>>>>
>>>>>>>>
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> If this is the level of "type" you're referring to, I think we
>>>>>>>> should drop it from the spec.  It's an application-layer thing tha=
t the app
>>>>>>>> can add or not according to its wishes.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I'm with Dick on this.  I think we should either have a mandatory
>>>>>>>> indicator of what type of JOSE object this, or nothing at all.   I=
f the
>>>>>>>> former, the allowable values are "JWE" and "JWS".  The "+JSON" opt=
ions are
>>>>>>>> non-sensical -- the app needs to know what it's parsing before it =
gets this
>>>>>>>> header.  While I have a preference for the former (for clarity), t=
he latter
>>>>>>>> approach is also OK with me, since the MIME types are specific to =
JWE/JWS.
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Another approach here would be to address the JSON and compact
>>>>>>>> forms separately.  The JSON form has no need of "typ" at all, sinc=
e the
>>>>>>>> type of the object is completely clear from what fields are there,=
 e.g.,
>>>>>>>> "recipients" vs. "signatures".  For the compact form, we could do =
something
>>>>>>>> like James's "E."/"S." prefix idea, which you need because the
>>>>>>>> dot-separated components have different meanings and no field name=
s to
>>>>>>>> indicate this.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> --Richard****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <
>>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>>
>>>>>>>> A standard library is unlikely to know the meanings of all possibl=
e
>>>>>>>> =93typ=94 values =96 and more to the point, *it doesn=92t have to*=
.  It=92s
>>>>>>>> the application=92s job to determine that =93this blob is a JOSE o=
bject=94 and
>>>>>>>> then pass it to a standard library, which will then ignore the =93=
typ=94 value.
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 mea=
ns.  It
>>>>>>>> won=92t know what =93typ=94: =93BCGovToken=94 is, should the BC Go=
vernment want to
>>>>>>>> declare that it=92s using a token with particular characteristics.=
  It won=92t
>>>>>>>> know what =93typ=94: =93XMPP=94 is, should XMPP want to declare th=
at it=92s using a
>>>>>>>> JOSE data structure with particular characteristics.  Etc.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> All these values can be registered in the registry and used by
>>>>>>>> applications that understand them.  That=92s the application=92s j=
ob =96 not the
>>>>>>>> library=92s job.  The =93typ=94 field is just there so that applic=
ations have a
>>>>>>>> standard place to make any such declarations that they may need.**=
*
>>>>>>>> *
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>                                                                 --
>>>>>>>> Mike****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>>>> *Sent:* Wednesday, May 29, 2013 5:18 PM
>>>>>>>> *To:* Mike Jones
>>>>>>>> *Cc:* Jim Schaad; jose@ietf.org****
>>>>>>>>
>>>>>>>>
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I'd prefer to be able to use standard libraries for creating and
>>>>>>>> parsing tokens, and not specialized libraries dependent on the use=
 case.
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I strongly think we either drop "typ" or make it required.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <
>>>>>>>> Michael.Jones@microsoft.com> wrote:****
>>>>>>>>
>>>>>>>> It=92s fine for your application to specify that it=92s required f=
or
>>>>>>>> your use case.  Not applications need it, so they shouldn=92t be f=
orced to
>>>>>>>> pay the space penalty of an unnecessary field.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>                                                                 --
>>>>>>>> Mike****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On
>>>>>>>> Behalf Of *Dick Hardt
>>>>>>>> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>>>>>>>>
>>>>>>>>
>>>>>>>> *To:* Jim Schaad
>>>>>>>> *Cc:* jose@ietf.org
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I use it all the time and my code would barf if it was not there.*=
*
>>>>>>>> **
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I think it should be required rather than be a hint if it is going
>>>>>>>> ot be there.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.co=
m>
>>>>>>>> wrote:****
>>>>>>>>
>>>>>>>> I think the values just changed****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> However the way you are using it would be an argument to say that
>>>>>>>> it should be a required field.  Are you just using it as a hint if=
 it
>>>>>>>> exists and then looking at the rest of the fields if it is not pre=
sent?
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Jim****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
>>>>>>>> *Sent:* Wednesday, May 29, 2013 3:49 PM
>>>>>>>> *To:* Jim Schaad
>>>>>>>> *Cc:* jose@ietf.org
>>>>>>>> *Subject:* Re: [jose] Should we delete the "typ" header field****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Well, I have been using, but now realize the spec changed or I was
>>>>>>>> confused.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> I had been setting "typ" to be either "JWE" or "JWS" depending on
>>>>>>>> the type of token I was creating or parsing as it was easier than =
looking
>>>>>>>> at "alg"****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> As currently defined, I don't see value in "typ".****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> -- Dick****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.co=
m>
>>>>>>>> wrote:****
>>>>>>>>
>>>>>>>> In reading the documents, I am trying to understand the
>>>>>>>> justification for having the =93typ=94 header parameter in the JOS=
E documents.
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> The purpose of the field is to hold the type of the object.  In th=
e
>>>>>>>> past, I believe that values which should now be placed in the cty =
field
>>>>>>>> (such as =93JWT=94) were placed in this field as well.  However th=
e parameter
>>>>>>>> is optional and an implementation cannot rely on its being present=
.  This
>>>>>>>> means that for all practical purposes all of the code to determine=
 the
>>>>>>>> value of the type field from the values of the alg and enc fields.=
  If the
>>>>>>>> field was mandatory then this code would disappear at a fairly sma=
ll space
>>>>>>>> cost and I can understand why the parameter would be present.****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Can anybody justify why this field should be present in the
>>>>>>>> document =96 or should it just disappear?****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> Jim****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jose mailing list
>>>>>>>> jose@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> --
>>>>>>>> -- Dick ****
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> --
>>>>>>>> -- Dick ****
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jose mailing list
>>>>>>>> jose@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> --
>>>>>>>> -- Dick ****
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jose mailing list
>>>>>>>> jose@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/jose****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>>  ****
>>>>>>>>
>>>>>>>> ** **
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> jose mailing list
>>>>>>>> jose@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Nat Sakimura (=3Dnat)
>>>>>>> Chairman, OpenID Foundation
>>>>>>> http://nat.sakimura.org/
>>>>>>> @_nat_en
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jose mailing list
>>>>>>> jose@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/jose
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Nat Sakimura (=3Dnat)
>>>> Chairman, OpenID Foundation
>>>> http://nat.sakimura.org/
>>>> @_nat_en
>>>>
>>>
>>>
>>
>>
>> --
>> Nat Sakimura (=3Dnat)
>> Chairman, OpenID Foundation
>> http://nat.sakimura.org/
>> @_nat_en
>>
>
>
>
> --
> -- Dick
>



--=20
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en

--001a11c2c6ce7f04f204de71e38e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It is giving the meaning to the signature - metadata about=
 the signature, so I thought header would be more appropriate, besides, the=
 payload is binary and I can avoid double base64 encoding that way.=A0</div=
>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/6 Dick=
 Hardt <span dir=3D"ltr">&lt;<a href=3D"mailto:dick.hardt@gmail.com" target=
=3D"_blank">dick.hardt@gmail.com</a>&gt;</span><br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<div dir=3D"ltr">Why would you need that in the header? Why not in the payl=
oad?</div><div class=3D"gmail_extra"><div><div class=3D"h5"><br><br><div cl=
ass=3D"gmail_quote">On Wed, Jun 5, 2013 at 5:31 PM, Nat Sakimura <span dir=
=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D"_blank">sakimu=
ra@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">What I was thinking as an e=
xample was to have &#39;datetime&#39; as a public header parameter to be us=
ed generally, and then differentiate between two cases of &#39;agreement&#3=
9; and &#39;timestamp&#39;. It is the same signing operation over the origi=
nal (e.g., a MS word document), but from an application point of view, it i=
s a bit different. Former constitute an agreement while the later does not.=
 The type=3Dtimestamp just signifies that the original document existed at =
the time indicated.=A0</div>

<div><div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5 Rich=
ard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_b=
lank">rlb@ipv.sx</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div dir=3D"ltr">I&#39;m not sure I understand the use case here. =A0Let me=
 look at a couple of options, and hopefully one of them will be what you me=
ant :) =A0<div><br></div><div>If it&#39;s just a signed timestamp you&#39;r=
e talking about, then that&#39;s adequately described by cty=3D&quot;timest=
amp&quot;, typ=3D&quot;JWS&quot;.</div>



<div><br></div><div>If you want to sign something and add a timestamp in th=
e header, then typ=3D&quot;timestamp&quot; isn&#39;t accurate according to =
the current specification. =A0The type of the whole object would have to be=
 something like &quot;timestamped-content&quot;. =A0And in that case, an ap=
plication can easily recognized that it&#39;s timestamped content by lookin=
g for the timestamp field in the header, so the &quot;typ&quot; isn&#39;t r=
eally helpful.</div>



<div><br></div><div><br></div><div>Moving from the example to the general q=
uestion:</div><div><br></div><div>I think we finally have some common under=
standing on this list as to what Mike means by &quot;typ&quot; in the curre=
nt document -- a label for the application-layer type of the overall object=
. =A0Thanks to Mike for clarifying that in this discussion.</div>



<div><br></div><div>The question is whether this is a sufficiently useful t=
hing to have in the core spec. =A0Obviously, applications have to know what=
 type of object they&#39;re dealing with when they get a JOSE object. =A0Th=
at includes (1) what type of content is in the payload, and (2) what applic=
ation-layer fields are required to be in the header. =A0(1) is covered by &=
quot;cty&quot;. =A0So &quot;typ&quot; is only useful in the case where:</di=
v>



<div>A. The application is storing application-layer data in the JOSE heade=
r</div><div>B. The required application-layer fields can be different for d=
ifferent objects</div><div>C. The required application-layer fields can be =
different for different objects of the same content type</div>



<div>D. The required application-layer fields are not indicated by other ap=
plication-layer context</div><div><br></div><div>Are there any known applic=
ations that meet these criteria? =A0JWT does not, for several reasons.=A0</=
div>



<div>1. (!A) JWT does not store application-layer data in the JOSE header, =
only in the claims in the body</div><div>2. (!C) A JWT object can indicate =
with &quot;cty&quot; that it contains JWT claims or another JWT, either of =
which makes it obvious that this is a JWT</div>



<div>3. (!D) In the OAuth context, the Token Type value indicates what type=
 of token is being presented, e.g., JWT</div><div><br></div><div>So there&#=
39;s not really any known use case for &quot;typ&quot; as currently specifi=
ed. =A0On the other hand, Dick and James have pointed out that it can be us=
eful to have &quot;typ&quot; indicate whether the object at hand is a JWE o=
r JWS. =A0Which brings us back to:</div>



<div>-- Change the definition of &quot;typ&quot; so that it indicates the J=
OSE-layer type (JWE/JWS)</div><div>-- Remove &quot;typ&quot; altogether</di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div><br>



</div></div><div><div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sakimura@gmail.com" target=3D"_blank">sakimura@gmail.com=
</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>What about such as thi=
s?=A0</div><div><br></div>cty: original<div>typ: timestamp</div></div><div>
<div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/6/5=
 Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">It would be a good point, i=
f it were true :) =A0In particular, this part: &quot;[dropping &#39;typ&#39=
;]<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:=
13px">=A0is going to cause each and every application that uses JOSE to def=
ine their own field</span>&quot;<div>





<br></div><div>So far, I&#39;ve heard of exactly one application of JOSE th=
at requires &quot;typ&quot; in the way it is currently specified, namely JW=
T. =A0</div><div><br></div><div>On the other hand, Dick&#39;s applications =
are apparently using it differently (and, IMO, properly) to distinguish JWE=
/JWS. =A0Then there are all the applications out there that are OK using ap=
plication context and &quot;cty&quot; to recognize what type of object they=
 have. =A0Apps using CMS have been doing this for ages.</div>





<div><br></div><div>So it&#39;s not at all clear to me that there&#39;s any=
 other application that would use &quot;typ&quot; besides JWT. =A0And it&#3=
9;s not clear to me that JWT needs it.</div><span><font color=3D"#888888"><=
div>




<br></div><div>--Richard</div>
<div><br></div><div><br><div><br></div></div></font></span></div><div><div>=
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, May 3=
1, 2013 at 5:45 PM, Brian Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:=
bcampbell@pingidentity.com" target=3D"_blank">bcampbell@pingidentity.com</a=
>&gt;</span> wrote:<br>





<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Nat makes a good point here=
, I think.<br></div><div><div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 30, 2013 at 9:31 AM, Nat Sak=
imura <span dir=3D"ltr">&lt;<a href=3D"mailto:sakimura@gmail.com" target=3D=
"_blank">sakimura@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">From what I understand, bot=
h typ and cty are something to be consumed by the application and not JOSE =
processor. From the point of view of the JOSE processor, they should be ign=
ored.=A0<div>







<br></div><div>
We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.=A0</div><div><br></div>
<div>I would rather drop them than define JOSE processing semantics to thes=
e fields.=A0</div></div><div class=3D"gmail_extra"><div><div><br><br><div c=
lass=3D"gmail_quote">2013/5/31 Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microso=
ft.com</a>&gt;</span><br>








<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>









<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM</span></p><div><div><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>









<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>









</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>









</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>









<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>









</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br></div></=
div>Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"htt=
p://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_=
nat_en</div>








</div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>





</div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Nat Sakimura (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://=
nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_=
en</div>



</div>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div></div><=
/div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>-- Dick
</font></span></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Nat Sakimura=
 (=3Dnat)<div>Chairman, OpenID Foundation<br><a href=3D"http://nat.sakimura=
.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_en</div>
</div>

--001a11c2c6ce7f04f204de71e38e--

From James.H.Manger@team.telstra.com  Wed Jun  5 19:19:12 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5346611E80E2 for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 19:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.698
X-Spam-Level: *
X-Spam-Status: No, score=1.698 tagged_above=-999 required=5 tests=[HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIIHTu54ZTAo for <jose@ietfa.amsl.com>; Wed,  5 Jun 2013 19:19:06 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 3F49911E80E4 for <jose@ietf.org>; Wed,  5 Jun 2013 19:19:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,810,1363093200"; d="scan'208";a="139932565"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipocvi.tcif.telstra.com.au with ESMTP; 06 Jun 2013 12:18:59 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7097"; a="136759411"
Received: from wsmsg3754.srv.dir.telstra.com ([172.49.40.198]) by ipccvi.tcif.telstra.com.au with ESMTP; 06 Jun 2013 12:18:59 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3754.srv.dir.telstra.com ([172.49.40.198]) with mapi; Thu, 6 Jun 2013 12:18:59 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Nat Sakimura <sakimura@gmail.com>
Date: Thu, 6 Jun 2013 12:18:57 +1000
Thread-Topic: [jose] Should we delete the "typ" header field
Thread-Index: Ac5iTXXx3btvRzA5Q52SxQXmyk5oHAAA26UQ
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B105B2B@WSMSG3153V.srv.dir.telstra.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com> <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com> <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>
In-Reply-To: <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 02:19:12 -0000

PiB0eXA6IHRpbWVzdGFtcA0KDQpCeSB2ZXJpZnlpbmcgYSBzaWduZWQgSk9TRSBtZXNzYWdlIHlv
dSBrbm93IHRoYXQgdGhlIGhvbGRlciBvZiB0aGUgY29ycmVzcG9uZGluZyBwcml2YXRlIGtleSAi
cHJvY2Vzc2VkIiB0aGUgYnl0ZXMgb2YgdGhlIGNvbnRlbnQuDQpXaGF0IGl0IGRvZXNuJ3QgdGVs
bCB5b3UgaXMgd2hldGhlciB0aGUgc2lnbmVyIG1lYW50Og0KMS4gVGhleSBkaWRuJ3QgbG9vayBh
dCB0aGUgY29udGVudCAoZWcgc2lnbmluZyBhbiBhdXRoZW50aWNhdGlvbiBjaGFsbGVuZ2U7IHRp
bWVzdGFtcGluZyBhcmJpdHJhcnkgZGF0YSkNCjIuIFRoZXkgYXJlIHZvdWNoaW5nIGZvciB0aGUg
c3ludGF4LCBub3QgbWVhbmluZywgb2YgdGhlIGNvbnRlbnQgKGVnIGFudGktbWFsd2FyZSBjaGVj
azsgc3ludGF4IGNoZWNrZXIpDQozLiBUaGV5IGFyZSBjb21taXR0aW5nIHRvIHRoZSBjb250ZW50
IChlZyBzaWduaW5nIGEgY29udHJhY3Q7IHZvdWNoaW5nIGZvciBjbGFpbXMpDQoNCkl0IGlzIHBy
b2JhYmx5IGJlc3QgZm9yIHRoZSBkaXN0aW5jdGlvbiBiZXR3ZWVuIHRoZXNlIHRvIGJlIGJvdW5k
IHRvIHRoZSB2ZXJpZmljYXRpb24gcHVibGljIGtleS4gRm9yIGluc3RhbmNlLCBpbmNsdWRpbmcg
YSBjcml0aWNhbCBleHRlbmRlZEtleVVzYWdlIGV4dGVuc2lvbiBpbiB0aGUgcHVibGljIGtleSdz
IGNlcnRpZmljYXRlIHdpdGggYSB2YWx1ZSBpZC1rcC10aW1lU3RhbXBpbmcgW1JGQzMxNjEgVGlt
ZS1TdGFtcCBQcm90b2NvbF0uDQoNCk5leHQsIHRoZSBjb250ZW50IHR5cGUgKCdjdHknIGZpZWxk
KSBzaG91bGQgZGlzdGluZ3Vpc2ggdGhlc2UgY2FzZXMuIFNpZ25pbmcgdGhlIHNhbWUgSldUIGNs
YWltIHNldCwgYnV0IHdpdGggJ2N0eScgc2V0IHRvICdhcHBsaWNhdGlvbi9vY3RldC1zdHJlYW0n
LCAnYXBwbGljYXRpb24vanNvbicsIG9yICdhcHBsaWNhdGlvbi9qd3QranNvbicoKikgY291bGQv
c2hvdWxkIGltcGx5IGRpZmZlcmVudCBtZWFuaW5ncyAoMSwgMiwgYW5kIDMgcmVzcGVjdGl2ZWx5
KS4NCg0KRXZlbiBpZiB0aGVyZSBhcmUgY2FzZXMgd2hlcmUgYSBoZWFkZXIgcGFyYW1ldGVyIGlz
IHVzZWZ1bCBmb3IgdGhpcyBwdXJwb3NlIChkZXNwaXRlIEpXRS9KV1Mgbm9yIEpXVCBiZWluZyBz
dWNoIGEgdXNlIGNhc2UpLCAndHlwJyBhcyBjdXJyZW50bHkgZGVmaW5lZCBjYW5ub3QgYmUgdGhl
IGFuc3dlciBhcyBpdCBpcyBvcHRpb25hbCBhbmQgaWdub3JhYmxlLiBBIHJlY2lwaWVudCByZWNl
aXZpbmcgYSBKT1NFIG1lc3NhZ2Ugd2l0aCB7InR5cCI6InRpbWVzdGFtcCIuLi59IGNhbiBsZWdp
dGltYXRlbHkgaWdub3JlICJ0eXAiIGFuZCBhc3N1bWUgdGhlIHNpZ25lciBpcyBjb21taXR0aW5n
IHRvIHRoZSBjb250ZW50Lg0KDQoNCigqKSBJIGRvbid0IHRoaW5rIGFwcGxpY2F0aW9uL2p3dCtq
c29uIGlzIGEgZGVmaW5lZCBtZWRpYSB0eXBlLiBJIGRpZG4ndCB1c2UgYXBwbGljYXRpb24vand0
IGFzIGl0IGlzIGRlZmluZWQgaW4gdGhlIEpXVCBkcmFmdCBhcyBhIG1lZGlhIHR5cGUgZm9yIEpP
U0UgbWVzc2FnZXMgKHdoaWNoIGlzIGNyYXp5KSwgaW5zdGVhZCBvZiBhIG1lZGlhIHR5cGUgZm9y
IGEgSlNPTiBvYmplY3QgaG9sZGluZyBjbGFpbXMgKHdoaWNoIGl0IHNob3VsZCBiZSkuDQoNCi0t
DQpKYW1lcyBNYW5nZXINCg==

From rlb@ipv.sx  Thu Jun  6 14:43:57 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0127521F9955 for <jose@ietfa.amsl.com>; Thu,  6 Jun 2013 14:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4I-lGfAsp3mU for <jose@ietfa.amsl.com>; Thu,  6 Jun 2013 14:43:52 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id D49C921F8825 for <jose@ietf.org>; Thu,  6 Jun 2013 14:43:51 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so5523726obb.18 for <jose@ietf.org>; Thu, 06 Jun 2013 14:43:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=zkzrTV6oc0fVY37Y8Y2BMvD9nCF1hP2tywFqrU5avvI=; b=pY0WqRTbR/K+16oZbR6etQLnxgXkkxkIBuu2YYK7KOjmkzJ/rH3VoholUQerGG6o5r 4L4hepHRF23CmgcW+dQsnblXmqNuAzbv0rehj8DL5idJmkrAHACsW1DVmuxkgp7tHrkj Bjp5zlr6kaCLLJ/Z8KE97foAELYyqmjmoTomLx0lZNbf2ImMUDi4j9J6C9kRkO2n5CMI jYYgUF9v9zJRyq8axN/uI5bQdyfDTCbmGVcuVdwW//BsULchUaR7ClX0eR/ES74LI/SN puSIy2Dr53+2pbIlubxOWwuZPtYW6vhTgLTmx09WwXuCAx6p7VCN/OCQwOba81mCbNN9 vQ8Q==
MIME-Version: 1.0
X-Received: by 10.60.33.202 with SMTP id t10mr19636423oei.2.1370555031384; Thu, 06 Jun 2013 14:43:51 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Thu, 6 Jun 2013 14:43:51 -0700 (PDT)
X-Originating-IP: [128.89.254.205]
Date: Thu, 6 Jun 2013 17:43:51 -0400
Message-ID: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "jose@ietf.org" <jose@ietf.org>
Content-Type: multipart/alternative; boundary=089e013c66b4ca843404de8335f0
X-Gm-Message-State: ALoCoQnLqqPkuDpnRyQNgsOzqvqkOSIi6sUG30mGthucNucWb7/HP/GxD0JMniUwf6opfzclHWbu
Subject: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 06 Jun 2013 21:43:57 -0000

--089e013c66b4ca843404de8335f0
Content-Type: text/plain; charset=ISO-8859-1

The conversation about "typ" has brought us back to a familiar question for
this working group -- what are we trying to do here?

The current document is ambiguous on this topic.  On the one hand, it
mostly covers the crypto bases, with things like "alg" and "enc".  On the
other hand, it mixes in application design concepts like "typ" and "crit".
 The result is a spec that's ambiguous in purpose and complex.  If I'm
building an application with this, how do I decide what goes in the "crit"
field, or what values to use for "typ"?
The charter for this working group is not ambiguous on this topic.  This
group is chartered to do signing and encryption.  The JOSE formats should
carry the parameters needed to perform those operations.  Anything else is
extraneous, and in the spirit of "The perfect protocol is one from which
nothing can be removed", should be removed.

Now, I'm not going to be a hard-liner on this.  I won't complain about
"zip" and "cty", since they are clearly defined and have clear use cases.
 But "crit" and "typ" are so ambiguous and so little supported by use
cases*, that they really should go.

</rant>

--Richard

--089e013c66b4ca843404de8335f0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The conversation about &quot;typ&quot; has brought us back=
 to a familiar question for this working group -- what are we trying to do =
here?<div><br></div><div>The current document is ambiguous on this topic. =
=A0On the one hand, it mostly covers the crypto bases, with things like &qu=
ot;alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applica=
tion design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The resu=
lt is a spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m bui=
lding an application with this, how do I decide what goes in the &quot;crit=
&quot; field, or what values to use for &quot;typ&quot;? =A0 =A0</div>
<div>The charter for this working group is not ambiguous on this topic. =A0=
This group is chartered to do signing and encryption. =A0The JOSE formats s=
hould carry the parameters needed to perform those operations. =A0Anything =
else is extraneous, and in the spirit of &quot;The perfect protocol is one =
from which nothing can be removed&quot;, should be removed.</div>
<div><br></div><div>Now, I&#39;m not going to be a hard-liner on this. =A0I=
 won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since they a=
re clearly defined and have clear use cases. =A0But &quot;crit&quot; and &q=
uot;typ&quot; are so ambiguous and so little supported by use cases*, that =
they really should go.</div>
<div><br></div><div>&lt;/rant&gt;</div><div><br></div><div>--Richard</div><=
/div>

--089e013c66b4ca843404de8335f0--

From Michael.Jones@microsoft.com  Thu Jun  6 22:22:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4409521F8ADF for <jose@ietfa.amsl.com>; Thu,  6 Jun 2013 22:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5s9aLVa6itCz for <jose@ietfa.amsl.com>; Thu,  6 Jun 2013 22:22:18 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id DF4F621F86F0 for <jose@ietf.org>; Thu,  6 Jun 2013 22:22:17 -0700 (PDT)
Received: from BN1BFFO11FD006.protection.gbl (10.58.52.200) by BN1BFFO11HUB015.protection.gbl (10.58.53.125) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 7 Jun 2013 05:20:59 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD006.mail.protection.outlook.com (10.58.53.66) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 7 Jun 2013 05:20:58 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Fri, 7 Jun 2013 05:18:58 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] What are we doing here?
Thread-Index: AQHOYv8CR0v9d+v7FEav765iFV2uepkps4Ew
Date: Fri, 7 Jun 2013 05:18:57 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com>
In-Reply-To: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.35]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436780758ETK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(377454002)(47446002)(74662001)(74706001)(56776001)(65816001)(47736001)(56816003)(33656001)(69226001)(80022001)(54356001)(46102001)(53806001)(76482001)(31966008)(74876001)(20776003)(74502001)(63696002)(77982001)(16406001)(15202345002)(16236675002)(49866001)(4396001)(76796001)(47976001)(79102001)(55846006)(71186001)(50986001)(59766001)(77096001)(66066001)(512954002)(81342001)(74366001)(54316002)(6806003)(51856001)(76786001)(81542001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB015; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0870212862
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 05:22:25 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436780758ETK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Excellent question, Richard, because it gets to the heart of why the JOSE s=
pecs are already highly successful and widely adopted.

  - We are building useful tools that solve real problems for developers.
  - We are practically demonstrating the value of rough consensus and runni=
ng code.
  - We are making simple things simple.
  - We are making complex things possible, when necessary (but not at the e=
xpense of keeping simple things simple).
  - We are developing specs with an explicit goal of enabling ubiquitous ad=
option.
  - We are developing specs guided by practical engineering tradeoffs to en=
able commonly useful functionality in a straightforward manner.

The level of adoption, with dozens of deployed implementations, is compelli=
ng evidence that we've already achieved the goals above.  It's time to "shi=
p it", as making the JOSE specs actual standards will only increase their a=
doption and value to the industry.

That's what we're doing here.

                                                            -- Mike

P.S.  I would be careful reasoning from the premise of "The perfect protoco=
l is one from which nothing can be removed".  By that logic, the perfect sp=
ecification is the null specification, which leaves all possibilities open,=
 and solves no actual problems. ;-)

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Thursday, June 06, 2013 2:44 PM
To: jose@ietf.org
Subject: [jose] What are we doing here?

The conversation about "typ" has brought us back to a familiar question for=
 this working group -- what are we trying to do here?

The current document is ambiguous on this topic.  On the one hand, it mostl=
y covers the crypto bases, with things like "alg" and "enc".  On the other =
hand, it mixes in application design concepts like "typ" and "crit".  The r=
esult is a spec that's ambiguous in purpose and complex.  If I'm building a=
n application with this, how do I decide what goes in the "crit" field, or =
what values to use for "typ"?
The charter for this working group is not ambiguous on this topic.  This gr=
oup is chartered to do signing and encryption.  The JOSE formats should car=
ry the parameters needed to perform those operations.  Anything else is ext=
raneous, and in the spirit of "The perfect protocol is one from which nothi=
ng can be removed", should be removed.

Now, I'm not going to be a hard-liner on this.  I won't complain about "zip=
" and "cty", since they are clearly defined and have clear use cases.  But =
"crit" and "typ" are so ambiguous and so little supported by use cases*, th=
at they really should go.

</rant>

--Richard

--_000_4E1F6AAD24975D4BA5B16804296739436780758ETK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly s=
uccessful and widely adopted.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are building =
useful tools that solve real problems for developers.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are practical=
ly demonstrating the value of rough consensus and running code.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making si=
mple things simple.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making co=
mplex things possible, when necessary (but not at the expense of keeping si=
mple things simple).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developin=
g specs with an explicit goal of enabling ubiquitous adoption.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developin=
g specs guided by practical engineering tradeoffs to enable commonly useful=
 functionality in a straightforward manner.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we&#8217=
;ve already achieved the goals above.&nbsp; It&#8217;s time to &#8220;ship =
it&#8221;,
 as making the JOSE specs actual standards will only increase their adoptio=
n and value to the industry.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">That&#8217;s what we&#821=
7;re doing here.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">P.S.&nbsp; I would be car=
eful reasoning from the premise of &#8220;</span>The perfect protocol is on=
e from which nothing can be removed<span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8221;.&nbsp=
;
 By that logic, the perfect specification is the null specification, which =
leaves all possibilities open, and solves no actual problems. ;-)<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> jose@ietf.org<br>
<b>Subject:</b> [jose] What are we doing here?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. &nb=
sp;On the one hand, it mostly covers the crypto bases, with things like &qu=
ot;alg&quot; and &quot;enc&quot;. &nbsp;On the other hand, it mixes in appl=
ication design concepts like &quot;typ&quot; and &quot;crit&quot;. &nbsp;Th=
e result is a
 spec that's ambiguous in purpose and complex. &nbsp;If I'm building an app=
lication with this, how do I decide what goes in the &quot;crit&quot; field=
, or what values to use for &quot;typ&quot;? &nbsp; &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. &nbsp;This group is chartered to do signing and encryption. =
&nbsp;The JOSE formats should carry the parameters needed to perform those =
operations. &nbsp;Anything else is extraneous, and
 in the spirit of &quot;The perfect protocol is one from which nothing can =
be removed&quot;, should be removed.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I'm not going to be a hard-liner on this. &nbsp=
;I won't complain about &quot;zip&quot; and &quot;cty&quot;, since they are=
 clearly defined and have clear use cases. &nbsp;But &quot;crit&quot; and &=
quot;typ&quot; are so ambiguous and so little supported by use cases*, that=
 they really
 should go.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436780758ETK5EX14MBXC283r_--

From Axel.Nennker@telekom.de  Fri Jun  7 02:53:46 2013
Return-Path: <Axel.Nennker@telekom.de>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2F721F9402 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 02:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTPC8fAfcIth for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 02:53:41 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCA821F86F4 for <jose@ietf.org>; Fri,  7 Jun 2013 02:53:39 -0700 (PDT)
Received: from he101250.emea1.cds.t-internal.com ([10.125.92.153]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 07 Jun 2013 11:53:25 +0200
Received: from HE100024.emea1.cds.t-internal.com (10.125.65.200) by HE101250.emea1.cds.t-internal.com (10.125.92.153) with Microsoft SMTP Server (TLS) id 8.3.298.1; Fri, 7 Jun 2013 11:53:25 +0200
Received: from HE111541.emea1.cds.t-internal.com ([10.125.90.97]) by HE100024.emea1.cds.t-internal.com ([2002:769:410c::769:410c]) with mapi; Fri, 7 Jun 2013 11:53:24 +0200
From: <Axel.Nennker@telekom.de>
To: <Michael.Jones@microsoft.com>, <rlb@ipv.sx>, <jose@ietf.org>
Date: Fri, 7 Jun 2013 11:53:22 +0200
Thread-Topic: [jose] What are we doing here?
Thread-Index: AQHOYv8CR0v9d+v7FEav765iFV2uepkps4EwgABM2/A=
Message-ID: <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071C@HE111541.emea1.cds.t-internal.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: multipart/alternative; boundary="_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071CHE111541eme_"
MIME-Version: 1.0
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 09:53:46 -0000

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071CHE111541eme_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+1 to Mike's comments.

Usefulness of the standard is the important thing.



From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mik=
e Jones
Sent: Friday, June 07, 2013 7:19 AM
To: Richard Barnes; jose@ietf.org
Subject: Re: [jose] What are we doing here?

Excellent question, Richard, because it gets to the heart of why the JOSE s=
pecs are already highly successful and widely adopted.

  - We are building useful tools that solve real problems for developers.
  - We are practically demonstrating the value of rough consensus and runni=
ng code.
  - We are making simple things simple.
  - We are making complex things possible, when necessary (but not at the e=
xpense of keeping simple things simple).
  - We are developing specs with an explicit goal of enabling ubiquitous ad=
option.
  - We are developing specs guided by practical engineering tradeoffs to en=
able commonly useful functionality in a straightforward manner.

The level of adoption, with dozens of deployed implementations, is compelli=
ng evidence that we've already achieved the goals above.  It's time to "shi=
p it", as making the JOSE specs actual standards will only increase their a=
doption and value to the industry.

That's what we're doing here.

                                                            -- Mike

P.S.  I would be careful reasoning from the premise of "The perfect protoco=
l is one from which nothing can be removed".  By that logic, the perfect sp=
ecification is the null specification, which leaves all possibilities open,=
 and solves no actual problems. ;-)

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Thursday, June 06, 2013 2:44 PM
To: jose@ietf.org
Subject: [jose] What are we doing here?

The conversation about "typ" has brought us back to a familiar question for=
 this working group -- what are we trying to do here?

The current document is ambiguous on this topic.  On the one hand, it mostl=
y covers the crypto bases, with things like "alg" and "enc".  On the other =
hand, it mixes in application design concepts like "typ" and "crit".  The r=
esult is a spec that's ambiguous in purpose and complex.  If I'm building a=
n application with this, how do I decide what goes in the "crit" field, or =
what values to use for "typ"?
The charter for this working group is not ambiguous on this topic.  This gr=
oup is chartered to do signing and encryption.  The JOSE formats should car=
ry the parameters needed to perform those operations.  Anything else is ext=
raneous, and in the spirit of "The perfect protocol is one from which nothi=
ng can be removed", should be removed.

Now, I'm not going to be a hard-liner on this.  I won't complain about "zip=
" and "cty", since they are clearly defined and have clear use cases.  But =
"crit" and "typ" are so ambiguous and so little supported by use cases*, th=
at they really should go.

</rant>

--Richard

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071CHE111541eme_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>+1 to Mik=
e&#8217;s comments.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>Usefulness of the stand=
ard is the important thing.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><di=
v style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm=
 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif"'> jose-bounces@ietf.org [mailto:jose-bounces@i=
etf.org] <b>On Behalf Of </b>Mike Jones<br><b>Sent:</b> Friday, June 07, 20=
13 7:19 AM<br><b>To:</b> Richard Barnes; jose@ietf.org<br><b>Subject:</b> R=
e: [jose] What are we doing here?<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Excellent que=
stion, Richard, because it gets to the heart of why the JOSE specs are alre=
ady highly successful and widely adopted.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nb=
sp; - We are building useful tools that solve real problems for developers.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; - We are practical=
ly demonstrating the value of rough consensus and running code.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'>&nbsp; - We are making simple things =
simple.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; - We are ma=
king complex things possible, when necessary (but not at the expense of kee=
ping simple things simple).<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&nbsp; - We are developing specs with an explicit goal of enabling ubiqui=
tous adoption.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; - We=
 are developing specs guided by practical engineering tradeoffs to enable c=
ommonly useful functionality in a straightforward manner.<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>The level of adoption, with dozens of deployed implementations=
, is compelling evidence that we&#8217;ve already achieved the goals above.=
&nbsp; It&#8217;s time to &#8220;ship it&#8221;, as making the JOSE specs a=
ctual standards will only increase their adoption and value to the industry=
.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>That&#8217;s what we&#8217;re doing here.<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; -- Mike<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>P.S.&nbsp; I would be carefu=
l reasoning from the premise of &#8220;</span>The perfect protocol is one f=
rom which nothing can be removed<span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'>&#8221;.&nbsp; By that logic, the pe=
rfect specification is the null specification, which leaves all possibiliti=
es open, and solves no actual problems. ;-)<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span=
></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> jo=
se-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of </b>Rich=
ard Barnes<br><b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br><b>To:</b> jo=
se@ietf.org<br><b>Subject:</b> [jose] What are we doing here?<o:p></o:p></s=
pan></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal=
>The conversation about &quot;typ&quot; has brought us back to a familiar q=
uestion for this working group -- what are we trying to do here?<o:p></o:p>=
</p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMs=
oNormal>The current document is ambiguous on this topic. &nbsp;On the one h=
and, it mostly covers the crypto bases, with things like &quot;alg&quot; an=
d &quot;enc&quot;. &nbsp;On the other hand, it mixes in application design =
concepts like &quot;typ&quot; and &quot;crit&quot;. &nbsp;The result is a s=
pec that's ambiguous in purpose and complex. &nbsp;If I'm building an appli=
cation with this, how do I decide what goes in the &quot;crit&quot; field, =
or what values to use for &quot;typ&quot;? &nbsp; &nbsp;<o:p></o:p></p></di=
v><div><p class=3DMsoNormal>The charter for this working group is not ambig=
uous on this topic. &nbsp;This group is chartered to do signing and encrypt=
ion. &nbsp;The JOSE formats should carry the parameters needed to perform t=
hose operations. &nbsp;Anything else is extraneous, and in the spirit of &q=
uot;The perfect protocol is one from which nothing can be removed&quot;, sh=
ould be removed.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal>Now, I'm not going to be a hard-li=
ner on this. &nbsp;I won't complain about &quot;zip&quot; and &quot;cty&quo=
t;, since they are clearly defined and have clear use cases. &nbsp;But &quo=
t;crit&quot; and &quot;typ&quot; are so ambiguous and so little supported b=
y use cases*, that they really should go.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>&lt;/rant=
&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv><div><p class=3DMsoNormal>--Richard<o:p></o:p></p></div></div></div></bo=
dy></html>=

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071CHE111541eme_--

From Axel.Nennker@telekom.de  Fri Jun  7 03:13:04 2013
Return-Path: <Axel.Nennker@telekom.de>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C24121F8F15 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 03:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.947
X-Spam-Level: 
X-Spam-Status: No, score=-1.947 tagged_above=-999 required=5 tests=[AWL=-1.302, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFTLMr-EWNJb for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 03:12:55 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [80.149.113.243]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0DA21F8F7B for <jose@ietf.org>; Fri,  7 Jun 2013 03:12:39 -0700 (PDT)
Received: from he111527.emea1.cds.t-internal.com ([10.125.90.86]) by tcmail21.telekom.de with ESMTP/TLS/AES128-SHA; 07 Jun 2013 12:11:25 +0200
Received: from HE111541.emea1.cds.t-internal.com ([10.125.90.97]) by HE111527.EMEA1.CDS.T-INTERNAL.COM ([2002:7cd:5a56::7cd:5a56]) with mapi; Fri, 7 Jun 2013 12:11:24 +0200
From: <Axel.Nennker@telekom.de>
To: <jose@ietf.org>
Date: Fri, 7 Jun 2013 12:11:23 +0200
Thread-Topic: [jose] Should we delete the "typ" header field
Thread-Index: Ac5iUeXwtS5j7F+KRBSkCLgEI73rjABEykrQ
Message-ID: <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075A@HE111541.emea1.cds.t-internal.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSwsL-ZUnwG-aCXJ5P-Q@mail.gmail.com> <CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com> <CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com> <CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com> <CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com> <CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com> <CAD9ie-s1uWSsRDJHb8Z_NPQvuAWWJmYPkTp8g_PbacA5gaqT1w@mail.gmail.com> <CABzCy2Abnv=Cm=nSN2t4b+B=G-rBrza6nrK+VPxqWUcTFpZEYw@mail.gmail.com>
In-Reply-To: <CABzCy2Abnv=Cm=nSN2t4b+B=G-rBrza6nrK+VPxqWUcTFpZEYw@mail.gmail.com>
Accept-Language: de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: multipart/alternative; boundary="_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075AHE111541eme_"
MIME-Version: 1.0
Cc: rlb@ipv.sx, ietf@augustcellars.com, Michael.Jones@microsoft.com, sakimura@gmail.com, bcampbell@pingidentity.com, dick.hardt@gmail.com
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 10:13:04 -0000

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075AHE111541eme_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


My take on the "typ" header field:


-          "typ" must be optional because some application just knows what =
it is dealing with. It is a waste of space in this case.

-          "typ" is reserved header name and the values SHOULD be JWS, JWE,=
 JWT. No MUST on the values.

-          For a general purpose JOSE library it makes sense to have "typ" =
and I would write it so that it  throws an exception on validateJWS( {"typ"=
:"JWE", ...})
Especially if crit=3D["typ"].

I would like to keep (the first paragraph of)
https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#section-4=
.1.8
as it is.

-Axel

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Nat=
 Sakimura
Sent: Thursday, June 06, 2013 3:04 AM
To: Dick Hardt
Cc: Richard Barnes; Mike Jones; Brian Campbell; Jim Schaad; jose@ietf.org
Subject: Re: [jose] Should we delete the "typ" header field

It is giving the meaning to the signature - metadata about the signature, s=
o I thought header would be more appropriate, besides, the payload is binar=
y and I can avoid double base64 encoding that way.

2013/6/6 Dick Hardt <dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>>
Why would you need that in the header? Why not in the payload?

On Wed, Jun 5, 2013 at 5:31 PM, Nat Sakimura <sakimura@gmail.com<mailto:sak=
imura@gmail.com>> wrote:
What I was thinking as an example was to have 'datetime' as a public header=
 parameter to be used generally, and then differentiate between two cases o=
f 'agreement' and 'timestamp'. It is the same signing operation over the or=
iginal (e.g., a MS word document), but from an application point of view, i=
t is a bit different. Former constitute an agreement while the later does n=
ot. The type=3Dtimestamp just signifies that the original document existed =
at the time indicated.

2013/6/5 Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
I'm not sure I understand the use case here.  Let me look at a couple of op=
tions, and hopefully one of them will be what you meant :)

If it's just a signed timestamp you're talking about, then that's adequatel=
y described by cty=3D"timestamp", typ=3D"JWS".

If you want to sign something and add a timestamp in the header, then typ=
=3D"timestamp" isn't accurate according to the current specification.  The =
type of the whole object would have to be something like "timestamped-conte=
nt".  And in that case, an application can easily recognized that it's time=
stamped content by looking for the timestamp field in the header, so the "t=
yp" isn't really helpful.


Moving from the example to the general question:

I think we finally have some common understanding on this list as to what M=
ike means by "typ" in the current document -- a label for the application-l=
ayer type of the overall object.  Thanks to Mike for clarifying that in thi=
s discussion.

The question is whether this is a sufficiently useful thing to have in the =
core spec.  Obviously, applications have to know what type of object they'r=
e dealing with when they get a JOSE object.  That includes (1) what type of=
 content is in the payload, and (2) what application-layer fields are requi=
red to be in the header.  (1) is covered by "cty".  So "typ" is only useful=
 in the case where:
A. The application is storing application-layer data in the JOSE header
B. The required application-layer fields can be different for different obj=
ects
C. The required application-layer fields can be different for different obj=
ects of the same content type
D. The required application-layer fields are not indicated by other applica=
tion-layer context

Are there any known applications that meet these criteria?  JWT does not, f=
or several reasons.
1. (!A) JWT does not store application-layer data in the JOSE header, only =
in the claims in the body
2. (!C) A JWT object can indicate with "cty" that it contains JWT claims or=
 another JWT, either of which makes it obvious that this is a JWT
3. (!D) In the OAuth context, the Token Type value indicates what type of t=
oken is being presented, e.g., JWT

So there's not really any known use case for "typ" as currently specified. =
 On the other hand, Dick and James have pointed out that it can be useful t=
o have "typ" indicate whether the object at hand is a JWE or JWS.  Which br=
ings us back to:
-- Change the definition of "typ" so that it indicates the JOSE-layer type =
(JWE/JWS)
-- Remove "typ" altogether






On Wed, Jun 5, 2013 at 8:53 AM, Nat Sakimura <sakimura@gmail.com<mailto:sak=
imura@gmail.com>> wrote:
What about such as this?

cty: original
typ: timestamp

2013/6/5 Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
It would be a good point, if it were true :)  In particular, this part: "[d=
ropping 'typ'] is going to cause each and every application that uses JOSE =
to define their own field"

So far, I've heard of exactly one application of JOSE that requires "typ" i=
n the way it is currently specified, namely JWT.

On the other hand, Dick's applications are apparently using it differently =
(and, IMO, properly) to distinguish JWE/JWS.  Then there are all the applic=
ations out there that are OK using application context and "cty" to recogni=
ze what type of object they have.  Apps using CMS have been doing this for =
ages.

So it's not at all clear to me that there's any other application that woul=
d use "typ" besides JWT.  And it's not clear to me that JWT needs it.

--Richard




On Fri, May 31, 2013 at 5:45 PM, Brian Campbell <bcampbell@pingidentity.com=
<mailto:bcampbell@pingidentity.com>> wrote:
Nat makes a good point here, I think.

On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura <sakimura@gmail.com<mailto:sa=
kimura@gmail.com>> wrote:
>From what I understand, both typ and cty are something to be consumed by th=
e application and not JOSE processor. From the point of view of the JOSE pr=
ocessor, they should be ignored.

We could drop both fields from JOSE specs, but that is going to cause each =
and every application that uses JOSE to define their own field, which is a =
waste. That is why we are defining them here.

I would rather drop them than define JOSE processing semantics to these fie=
lds.

2013/5/31 Mike Jones <Michael.Jones@microsoft.com<mailto:Michael.Jones@micr=
osoft.com>>
No, "cty" is used by the derived class to determine the type of the encapsu=
lated field.  But that's not a complete description of the *entire object* =
- especially not the additional meaning imbued by the additional parameters=
 the derived type may add to the JOSE header.  "typ" is there to provide th=
e type of the entire object, including what you're calling the wrapper part=
s.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, May 30, 2013 7:58 AM

To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt
Subject: Re: [jose] Should we delete the "typ" header field

Isn't that requirement met by "cty"?  The only thing JOSE adds is a crypto =
wrapper around the real application content.  If you're an application, you=
 know a JOSE object is the thing you want because it contains the content y=
ou want -- it's a JWT because it contains JWT claims.

Inheritance is the wrong metaphor.  This is encapsulation of application da=
ta:
if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {
    jwtClaims =3D jws.content;
}

--Richard

On Thu, May 30, 2013 at 10:43 AM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
Thanks for sharing the S/MIME details.  Although I was actually making the =
analogy to MIME - not S/MIME.  Like many analogies, it's imperfect, but I b=
elieve still illustrative.

The reason that the analogy isn't perfect is that the JOSE data structures =
are used to build application-specific data structures that are legal JOSE =
data structures but also have additional properties - including additional =
header fields with specific semantics.  (When we agreed to ignore not-under=
stood header fields we let that horse out of the barn.)  For instance, Dick=
 Hardt uses JWEs with issuer and audience fields in the headers, so they ca=
n be used by routing software.

Think of JOSE as the base class and the application types built using it as=
 derived classes.  JWT is a derived class.  Dick's structures are a derived=
 class.  These derived classes sometimes need names.  That's what "typ" is =
for.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, May 30, 2013 7:34 AM

To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt
Subject: Re: [jose] Should we delete the "typ" header field

You're mixing up "typ" and "cty".  If you want to make the analogy to S/MIM=
E, "cty" is the equivalent to Content-Type inside the protected MIME body; =
"typ" is the content-type on the outer MIME header.  Pasting in an example:

-----BEGIN-----
Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;
     name=3Dsmime.p7m
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=3Dsmime.p7m

567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7
77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH
HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh
6YT64V0GhIGfHfQbnj75
-----END-----
<http://tools.ietf.org/html/rfc3851#section-3.4.2>

The outer Content-Type, which is analogous to "typ", MUST be application/pk=
cs7-mime, with a parameter indicating the type of CMS object.  This is the =
same as requiring "typ" to be JWE or JWS.  The inner Content-Type (ASN.1/ba=
se64 encoded in the example) can be anything, just like "cty".

--Richard




On Thu, May 30, 2013 at 12:53 AM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
Requiring that the "typ" value be only "JWS" or "JWE" would be analogous to=
 the MIME spec requiring that the Content-Type: field be only "text/plain" =
or "message/external-body".  It would render it useless.

                                                            -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Wednesday, May 29, 2013 8:03 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt

Subject: Re: [jose] Should we delete the "typ" header field

If this is the level of "type" you're referring to, I think we should drop =
it from the spec.  It's an application-layer thing that the app can add or =
not according to its wishes.

I'm with Dick on this.  I think we should either have a mandatory indicator=
 of what type of JOSE object this, or nothing at all.   If the former, the =
allowable values are "JWE" and "JWS".  The "+JSON" options are non-sensical=
 -- the app needs to know what it's parsing before it gets this header.  Wh=
ile I have a preference for the former (for clarity), the latter approach i=
s also OK with me, since the MIME types are specific to JWE/JWS.

Another approach here would be to address the JSON and compact forms separa=
tely.  The JSON form has no need of "typ" at all, since the type of the obj=
ect is completely clear from what fields are there, e.g., "recipients" vs. =
"signatures".  For the compact form, we could do something like James's "E.=
"/"S." prefix idea, which you need because the dot-separated components hav=
e different meanings and no field names to indicate this.

--Richard

On Wed, May 29, 2013 at 8:30 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
A standard library is unlikely to know the meanings of all possible "typ" v=
alues - and more to the point, it doesn't have to.  It's the application's =
job to determine that "this blob is a JOSE object" and then pass it to a st=
andard library, which will then ignore the "typ" value.

A standard JOSE library won't know what "typ": "JWT" means.  It won't know =
what "typ": "BCGovToken" is, should the BC Government want to declare that =
it's using a token with particular characteristics.  It won't know what "ty=
p": "XMPP" is, should XMPP want to declare that it's using a JOSE data stru=
cture with particular characteristics.  Etc.

All these values can be registered in the registry and used by applications=
 that understand them.  That's the application's job - not the library's jo=
b.  The "typ" field is just there so that applications have a standard plac=
e to make any such declarations that they may need.

                                                                -- Mike

From: Dick Hardt [mailto:dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>]
Sent: Wednesday, May 29, 2013 5:18 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>

Subject: Re: [jose] Should we delete the "typ" header field

I'd prefer to be able to use standard libraries for creating and parsing to=
kens, and not specialized libraries dependent on the use case.

I strongly think we either drop "typ" or make it required.

On Wed, May 29, 2013 at 5:03 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
It's fine for your application to specify that it's required for your use c=
ase.  Not applications need it, so they shouldn't be forced to pay the spac=
e penalty of an unnecessary field.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Dick Hardt
Sent: Wednesday, May 29, 2013 4:56 PM

To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field

I use it all the time and my code would barf if it was not there.

I think it should be required rather than be a hint if it is going ot be th=
ere.

On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
I think the values just changed

However the way you are using it would be an argument to say that it should=
 be a required field.  Are you just using it as a hint if it exists and the=
n looking at the rest of the fields if it is not present?

Jim


From: Dick Hardt [mailto:dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>]
Sent: Wednesday, May 29, 2013 3:49 PM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field

Well, I have been using, but now realize the spec changed or I was confused=
.

I had been setting "typ" to be either "JWE" or "JWS" depending on the type =
of token I was creating or parsing as it was easier than looking at "alg"

As currently defined, I don't see value in "typ".

-- Dick


On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
In reading the documents, I am trying to understand the justification for h=
aving the "typ" header parameter in the JOSE documents.

The purpose of the field is to hold the type of the object.  In the past, I=
 believe that values which should now be placed in the cty field (such as "=
JWT") were placed in this field as well.  However the parameter is optional=
 and an implementation cannot rely on its being present.  This means that f=
or all practical purposes all of the code to determine the value of the typ=
e field from the values of the alg and enc fields.  If the field was mandat=
ory then this code would disappear at a fairly small space cost and I can u=
nderstand why the parameter would be present.

Can anybody justify why this field should be present in the document - or s=
hould it just disappear?

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick



--
-- Dick

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose




_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose





--
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en




--
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en



--
-- Dick



--
Nat Sakimura (=3Dnat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075AHE111541eme_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1404837555;
	mso-list-type:hybrid;
	mso-list-template-ids:-1429959770 -822572398 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'>My take on the &#8220;typ&#8=
221; header field:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoListParagraph style=3D'text-indent:-18.0=
pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span style=3D'mso-=
list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&#8220;typ&#8221; must be optional because some application just knows wh=
at it is dealing with. It is a waste of space in this case.<o:p></o:p></spa=
n></p><p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'><span style=3D'mso-list:Ignore'>-<=
span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&#8220;typ&#8=
221; is reserved header name and the values SHOULD be JWS, JWE, JWT. No MUS=
T on the values.<o:p></o:p></span></p><p class=3DMsoListParagraph style=3D'=
text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><s=
pan style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New Roman"'=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></spa=
n><![endif]><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if";color:#1F497D'>For a general purpose JOSE library it makes sense to hav=
e &#8220;typ&#8221; and I would write it so that it &nbsp;throws an excepti=
on on validateJWS( {&#8220;typ&#8221;:&#8221;JWE&#8221;, &#8230;})<br>Espec=
ially if crit=3D[&#8221;typ&#8221;].<o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would =
like to keep (the first paragraph of)<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#1F497D'><a href=3D"https://tools.ietf.org/html/draft-ietf-jose-json-web=
-signature-11#section-4.1.8">https://tools.ietf.org/html/draft-ietf-jose-js=
on-web-signature-11#section-4.1.8</a><o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#1F497D'>as it is.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>-Axel<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'=
>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans=
-serif"'> jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf=
 Of </b>Nat Sakimura<br><b>Sent:</b> Thursday, June 06, 2013 3:04 AM<br><b>=
To:</b> Dick Hardt<br><b>Cc:</b> Richard Barnes; Mike Jones; Brian Campbell=
; Jim Schaad; jose@ietf.org<br><b>Subject:</b> Re: [jose] Should we delete =
the &quot;typ&quot; header field<o:p></o:p></span></p><p class=3DMsoNormal>=
<o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>It is giving the meaning to =
the signature - metadata about the signature, so I thought header would be =
more appropriate, besides, the payload is binary and I can avoid double bas=
e64 encoding that way.&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNorm=
al>2013/6/6 Dick Hardt &lt;<a href=3D"mailto:dick.hardt@gmail.com" target=
=3D"_blank">dick.hardt@gmail.com</a>&gt;<o:p></o:p></p><div><p class=3DMsoN=
ormal>Why would you need that in the header? Why not in the payload?<o:p></=
o:p></p></div><div><div><div><p class=3DMsoNormal style=3D'margin-bottom:12=
.0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Wed, Jun 5, 2013 at=
 5:31 PM, Nat Sakimura &lt;<a href=3D"mailto:sakimura@gmail.com" target=3D"=
_blank">sakimura@gmail.com</a>&gt; wrote:<o:p></o:p></p><div><p class=3DMso=
Normal>What I was thinking as an example was to have 'datetime' as a public=
 header parameter to be used generally, and then differentiate between two =
cases of 'agreement' and 'timestamp'. It is the same signing operation over=
 the original (e.g., a MS word document), but from an application point of =
view, it is a bit different. Former constitute an agreement while the later=
 does not. The type=3Dtimestamp just signifies that the original document e=
xisted at the time indicated.&nbsp;<o:p></o:p></p></div><div><div><div><p c=
lass=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><=
p class=3DMsoNormal>2013/6/5 Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.s=
x" target=3D"_blank">rlb@ipv.sx</a>&gt;<o:p></o:p></p><div><p class=3DMsoNo=
rmal>I'm not sure I understand the use case here. &nbsp;Let me look at a co=
uple of options, and hopefully one of them will be what you meant :) &nbsp;=
<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p=
 class=3DMsoNormal>If it's just a signed timestamp you're talking about, th=
en that's adequately described by cty=3D&quot;timestamp&quot;, typ=3D&quot;=
JWS&quot;.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p><=
/p></div><div><p class=3DMsoNormal>If you want to sign something and add a =
timestamp in the header, then typ=3D&quot;timestamp&quot; isn't accurate ac=
cording to the current specification. &nbsp;The type of the whole object wo=
uld have to be something like &quot;timestamped-content&quot;. &nbsp;And in=
 that case, an application can easily recognized that it's timestamped cont=
ent by looking for the timestamp field in the header, so the &quot;typ&quot=
; isn't really helpful.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div>=
<div><p class=3DMsoNormal>Moving from the example to the general question:<=
o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><d=
iv><p class=3DMsoNormal>I think we finally have some common understanding o=
n this list as to what Mike means by &quot;typ&quot; in the current documen=
t -- a label for the application-layer type of the overall object. &nbsp;Th=
anks to Mike for clarifying that in this discussion.<o:p></o:p></p></div><d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorma=
l>The question is whether this is a sufficiently useful thing to have in th=
e core spec. &nbsp;Obviously, applications have to know what type of object=
 they're dealing with when they get a JOSE object. &nbsp;That includes (1) =
what type of content is in the payload, and (2) what application-layer fiel=
ds are required to be in the header. &nbsp;(1) is covered by &quot;cty&quot=
;. &nbsp;So &quot;typ&quot; is only useful in the case where:<o:p></o:p></p=
></div><div><p class=3DMsoNormal>A. The application is storing application-=
layer data in the JOSE header<o:p></o:p></p></div><div><p class=3DMsoNormal=
>B. The required application-layer fields can be different for different ob=
jects<o:p></o:p></p></div><div><p class=3DMsoNormal>C. The required applica=
tion-layer fields can be different for different objects of the same conten=
t type<o:p></o:p></p></div><div><p class=3DMsoNormal>D. The required applic=
ation-layer fields are not indicated by other application-layer context<o:p=
></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div>=
<p class=3DMsoNormal>Are there any known applications that meet these crite=
ria? &nbsp;JWT does not, for several reasons.&nbsp;<o:p></o:p></p></div><di=
v><p class=3DMsoNormal>1. (!A) JWT does not store application-layer data in=
 the JOSE header, only in the claims in the body<o:p></o:p></p></div><div><=
p class=3DMsoNormal>2. (!C) A JWT object can indicate with &quot;cty&quot; =
that it contains JWT claims or another JWT, either of which makes it obviou=
s that this is a JWT<o:p></o:p></p></div><div><p class=3DMsoNormal>3. (!D) =
In the OAuth context, the Token Type value indicates what type of token is =
being presented, e.g., JWT<o:p></o:p></p></div><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>So there's not really an=
y known use case for &quot;typ&quot; as currently specified. &nbsp;On the o=
ther hand, Dick and James have pointed out that it can be useful to have &q=
uot;typ&quot; indicate whether the object at hand is a JWE or JWS. &nbsp;Wh=
ich brings us back to:<o:p></o:p></p></div><div><p class=3DMsoNormal>-- Cha=
nge the definition of &quot;typ&quot; so that it indicates the JOSE-layer t=
ype (JWE/JWS)<o:p></o:p></p></div><div><p class=3DMsoNormal>-- Remove &quot=
;typ&quot; altogether<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div></div><div><div><div><p class=3DMsoNormal style=3D'margin-bottom:12.=
0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Wed, Jun 5, 2013 at =
8:53 AM, Nat Sakimura &lt;<a href=3D"mailto:sakimura@gmail.com" target=3D"_=
blank">sakimura@gmail.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=
=3DMsoNormal>What about such as this?&nbsp;<o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>cty: origina=
l<o:p></o:p></p><div><p class=3DMsoNormal>typ: timestamp<o:p></o:p></p></di=
v></div><div><div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>=
<o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>2013/6/5 Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;<o:p></o:=
p></p><div><p class=3DMsoNormal>It would be a good point, if it were true :=
) &nbsp;In particular, this part: &quot;[dropping 'typ']<span style=3D'font=
-size:10.0pt;font-family:"Arial","sans-serif";color:#500050'>&nbsp;is going=
 to cause each and every application that uses JOSE to define their own fie=
ld</span>&quot;<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>So far, I've heard of exactly one applica=
tion of JOSE that requires &quot;typ&quot; in the way it is currently speci=
fied, namely JWT. &nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>On the other hand, Dick's =
applications are apparently using it differently (and, IMO, properly) to di=
stinguish JWE/JWS. &nbsp;Then there are all the applications out there that=
 are OK using application context and &quot;cty&quot; to recognize what typ=
e of object they have. &nbsp;Apps using CMS have been doing this for ages.<=
o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><d=
iv><p class=3DMsoNormal>So it's not at all clear to me that there's any oth=
er application that would use &quot;typ&quot; besides JWT. &nbsp;And it's n=
ot clear to me that JWT needs it.<o:p></o:p></p></div><div><p class=3DMsoNo=
rmal><span style=3D'color:#888888'><o:p>&nbsp;</o:p></span></p></div><div><=
p class=3DMsoNormal><span style=3D'color:#888888'>--Richard<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span style=3D'color:#888888'><o:p>&n=
bsp;</o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'color:#=
888888'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=
=3D'color:#888888'><o:p>&nbsp;</o:p></span></p></div></div></div><div><div>=
<div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p><=
/p><div><p class=3DMsoNormal>On Fri, May 31, 2013 at 5:45 PM, Brian Campbel=
l &lt;<a href=3D"mailto:bcampbell@pingidentity.com" target=3D"_blank">bcamp=
bell@pingidentity.com</a>&gt; wrote:<o:p></o:p></p><div><p class=3DMsoNorma=
l>Nat makes a good point here, I think.<o:p></o:p></p></div><div><div><div>=
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><d=
iv><p class=3DMsoNormal>On Thu, May 30, 2013 at 9:31 AM, Nat Sakimura &lt;<=
a href=3D"mailto:sakimura@gmail.com" target=3D"_blank">sakimura@gmail.com</=
a>&gt; wrote:<o:p></o:p></p><div><p class=3DMsoNormal>From what I understan=
d, both typ and cty are something to be consumed by the application and not=
 JOSE processor. From the point of view of the JOSE processor, they should =
be ignored.&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal>We could drop both fields from JOSE spe=
cs, but that is going to cause each and every application that uses JOSE to=
 define their own field, which is a waste. That is why we are defining them=
 here.&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div><div><p class=3DMsoNormal>I would rather drop them than define J=
OSE processing semantics to these fields.&nbsp;<o:p></o:p></p></div></div><=
div><div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbs=
p;</o:p></p><div><p class=3DMsoNormal>2013/5/31 Mike Jones &lt;<a href=3D"m=
ailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsof=
t.com</a>&gt;<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>No, &#8220;cty&#8221; i=
s used by the derived class to determine the type of the encapsulated field=
.&nbsp; But that&#8217;s not a complete description of the *<b>entire objec=
t</b>* - especially not the additional meaning imbued by the additional par=
ameters the derived type may add to the JOSE header.&nbsp; &#8220;typ&#8221=
; is there to provide the type of the entire object, including what you&#82=
17;re calling the wrapper parts.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif"'> Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>] <br><b>Sent:</b> Thursday, May 30, 2013 7=
:58 AM</span><o:p></o:p></p><div><div><p class=3DMsoNormal><br><b>To:</b> M=
ike Jones<br><b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>; Dick Hardt<br><b>Subject:</b> Re: [jose] Sho=
uld we delete the &quot;typ&quot; header field<o:p></o:p></p></div></div><d=
iv><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-=
margin-top-alt:auto;mso-margin-bottom-alt:auto'>Isn't that requirement met =
by &quot;cty&quot;? &nbsp;The only thing JOSE adds is a crypto wrapper arou=
nd the real application content. &nbsp;If you're an application, you know a=
 JOSE object is the thing you want because it contains the content you want=
 -- it's a JWT because it contains JWT claims.<o:p></o:p></p><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&=
nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'>Inheritance is the wrong metaphor. &n=
bsp;This is encapsulation of application data:<o:p></o:p></p></div><div><p =
class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:au=
to'>if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;application/jwt_claims&qu=
ot;) {<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-to=
p-alt:auto;mso-margin-bottom-alt:auto'>&nbsp; &nbsp; jwtClaims =3D jws.cont=
ent;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'>}<o:p></o:p></p></div><div><p class=3D=
MsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbs=
p;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto'>--Richard<o:p></o:p></p><div><p class=3D=
MsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p=
></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'>On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks =
for sharing the S/MIME details.&nbsp; Although I was actually making the an=
alogy to MIME &#8211; not S/MIME.&nbsp; Like many analogies, it&#8217;s imp=
erfect, but I believe still illustrative.</span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>The reason that the analogy isn=
&#8217;t perfect is that the JOSE data structures are used to build applica=
tion-specific data structures that are legal JOSE data structures but also =
have additional properties &#8211; including additional header fields with =
specific semantics.&nbsp; (When we agreed to ignore not-understood header f=
ields we let that horse out of the barn.)&nbsp; For instance, Dick Hardt us=
es JWEs with issuer and audience fields in the headers, so they can be used=
 by routing software.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'ms=
o-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p>=
</o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>Think of JOSE as the base class and the application=
 types built using it as derived classes.&nbsp; JWT is a derived class.&nbs=
p; Dick&#8217;s structures are a derived class.&nbsp; These derived classes=
 sometimes need names.&nbsp; That&#8217;s what &#8220;typ&#8221; is for.</s=
pan><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMso=
Normal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p><=
/o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style=3D=
'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Richard Barne=
s [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>] <=
br><b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><o:p></o:p></p><div><d=
iv><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto'><br><b>To:</b> Mike Jones<br><b>Cc:</b> Jim Schaad; <a href=3D"ma=
ilto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>; Dick Hardt<br><b>S=
ubject:</b> Re: [jose] Should we delete the &quot;typ&quot; header field<o:=
p></o:p></p></div></div><div><div><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Y=
ou're mixing up &quot;typ&quot; and &quot;cty&quot;. &nbsp;If you want to m=
ake the analogy to S/MIME, &quot;cty&quot; is the equivalent to Content-Typ=
e inside the protected MIME body; &quot;typ&quot; is the content-type on th=
e outer MIME header. &nbsp;Pasting in an example:<o:p></o:p></p><div><p cla=
ss=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'=
>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto'>-----BEGIN-----<o:p></o:p></p></div=
><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'>Content-Type: application/pkcs7-mime; smime-type=3Dsigned=
-data;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-to=
p-alt:auto;mso-margin-bottom-alt:auto'>&nbsp; &nbsp; &nbsp;name=3Dsmime.p7m=
<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'>Content-Transfer-Encoding: base64<o:p></o:=
p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'>Content-Disposition: attachment; filename=3Dsmime.p=
7m<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-al=
t:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>5=
67GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7<o:p></o:p></p></di=
v><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bot=
tom-alt:auto'>77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH<o:p=
></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto'>HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H=
7n8HHGghyHh<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'>6YT64V0GhIGfHfQbnj75<o:p></o:p>=
</p></div></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'>-----END-----<o:p></o:p></p></div><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&=
lt;<a href=3D"http://tools.ietf.org/html/rfc3851#section-3.4.2" target=3D"_=
blank">http://tools.ietf.org/html/rfc3851#section-3.4.2</a>&gt;<o:p></o:p><=
/p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-mar=
gin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal s=
tyle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The outer Conte=
nt-Type, which is analogous to &quot;typ&quot;, MUST be application/pkcs7-m=
ime, with a parameter indicating the type of CMS object. &nbsp;This is the =
same as requiring &quot;typ&quot; to be JWE or JWS. &nbsp;The inner Content=
-Type (ASN.1/base64 encoded in the example) can be anything, just like &quo=
t;cty&quot;.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><di=
v><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'>--Richard<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></=
p></div></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;ma=
rgin-bottom:12.0pt'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal style=3D=
'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Thu, May 30, 2013 a=
t 12:53 AM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" t=
arget=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<o:p></o:p></p><=
div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>Requiring that the &#8220;typ&#8221; value be only &=
#8220;JWS&#8221; or &#8220;JWE&#8221; would be analogous to the MIME spec r=
equiring that the Content-Type: field be only &#8220;text/plain&#8221; or &=
#8220;message/external-body&#8221;.&nbsp; It would render it useless.</span=
><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNor=
mal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:=
p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bott=
om-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href=3D"mail=
to:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</a> [mail=
to:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@=
ietf.org</a>] <b>On Behalf Of </b>Richard Barnes<br><b>Sent:</b> Wednesday,=
 May 29, 2013 8:03 PM<br><b>To:</b> Mike Jones<br><b>Cc:</b> Jim Schaad; <a=
 href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>; Dick Ha=
rdt</span><o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'><br><b>Subject:</b> Re: [jose] Sh=
ould we delete the &quot;typ&quot; header field<o:p></o:p></p></div></div><=
div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso=
-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If this is the level of &q=
uot;type&quot; you're referring to, I think we should drop it from the spec=
. &nbsp;It's an application-layer thing that the app can add or not accordi=
ng to its wishes.<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto'>I'm with Dick on this. &nbsp;I think we should either have a mandat=
ory indicator of what type of JOSE object this, or nothing at all. &nbsp; I=
f the former, the allowable values are &quot;JWE&quot; and &quot;JWS&quot;.=
 &nbsp;The &quot;+JSON&quot; options are non-sensical -- the app needs to k=
now what it's parsing before it gets this header. &nbsp;While I have a pref=
erence for the former (for clarity), the latter approach is also OK with me=
, since the MIME types are specific to JWE/JWS.<o:p></o:p></p></div><div><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'>Another approach here would be =
to address the JSON and compact forms separately. &nbsp;The JSON form has n=
o need of &quot;typ&quot; at all, since the type of the object is completel=
y clear from what fields are there, e.g., &quot;recipients&quot; vs. &quot;=
signatures&quot;. &nbsp;For the compact form, we could do something like Ja=
mes's &quot;E.&quot;/&quot;S.&quot; prefix idea, which you need because the=
 dot-separated components have different meanings and no field names to ind=
icate this.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto'>--Richard<o:p></o:p></p></div></div><div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p></o:p></p><div=
><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto'>On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a href=3D"mailto:M=
ichael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</=
a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>A standard library is u=
nlikely to know the meanings of all possible &#8220;typ&#8221; values &#821=
1; and more to the point, <b>it doesn&#8217;t have to</b>.&nbsp; It&#8217;s=
 the application&#8217;s job to determine that &#8220;this blob is a JOSE o=
bject&#8221; and then pass it to a standard library, which will then ignore=
 the &#8220;typ&#8221; value.</span><o:p></o:p></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</sp=
an><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>A standard JOSE library won&#8217;t know wh=
at &#8220;typ&#8221;: &#8220;JWT&#8221; means.&nbsp; It won&#8217;t know wh=
at &#8220;typ&#8221;: &#8220;BCGovToken&#8221; is, should the BC Government=
 want to declare that it&#8217;s using a token with particular characterist=
ics.&nbsp; It won&#8217;t know what &#8220;typ&#8221;: &#8220;XMPP&#8221; i=
s, should XMPP want to declare that it&#8217;s using a JOSE data structure =
with particular characteristics.&nbsp; Etc.</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'>All these values can be reg=
istered in the registry and used by applications that understand them.&nbsp=
; That&#8217;s the application&#8217;s job &#8211; not the library&#8217;s =
job.&nbsp; The &#8220;typ&#8221; field is just there so that applications h=
ave a standard place to make any such declarations that they may need.</spa=
n><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNo=
rmal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; -- Mike</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>=
From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif"'> Dick Hardt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=
=3D"_blank">dick.hardt@gmail.com</a>] <br><b>Sent:</b> Wednesday, May 29, 2=
013 5:18 PM<br><b>To:</b> Mike Jones<br><b>Cc:</b> Jim Schaad; <a href=3D"m=
ailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a></span><o:p></o:p><=
/p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-marg=
in-bottom-alt:auto'><br><b>Subject:</b> Re: [jose] Should we delete the &qu=
ot;typ&quot; header field<o:p></o:p></p></div></div><div><div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;=
<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'>I'd prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto'>I strongly think we either drop &quot;typ&quot; or make it required.<o=
:p></o:p></p></div></div><div><p class=3DMsoNormal style=3D'mso-margin-top-=
alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNorm=
al style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Wed, May=
 29, 2013 at 5:03 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@micros=
oft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote:<o:p><=
/o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>It&#8217;s fine for your application to sp=
ecify that it&#8217;s required for your use case.&nbsp; Not applications ne=
ed it, so they shouldn&#8217;t be forced to pay the space penalty of an unn=
ecessary field.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p>=
</p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</sp=
an><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-fa=
mily:"Tahoma","sans-serif"'> <a href=3D"mailto:jose-bounces@ietf.org" targe=
t=3D"_blank">jose-bounces@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounc=
es@ietf.org" target=3D"_blank">jose-bounces@ietf.org</a>] <b>On Behalf Of <=
/b>Dick Hardt<br><b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><o:p></=
o:p></p><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso=
-margin-bottom-alt:auto'><br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a href=3D=
"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br><b>Subject:</=
b> Re: [jose] Should we delete the &quot;typ&quot; header field<o:p></o:p><=
/p></div></div><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:a=
uto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNor=
mal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I use it a=
ll the time and my code would barf if it was not there.<o:p></o:p></p><div>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-ma=
rgin-top-alt:auto;mso-margin-bottom-alt:auto'>I think it should be required=
 rather than be a hint if it is going ot be there.<o:p></o:p></p></div></di=
v><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:=
12.0pt'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'>On Wed, May 29, 2013 at 4:40 PM, J=
im Schaad &lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">i=
etf@augustcellars.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMso=
Normal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span s=
tyle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>=
I think the values just changed</span><o:p></o:p></p><p class=3DMsoNormal s=
tyle=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'=
font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</=
span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>However the way you are using it would be=
 an argument to say that it should be a required field.&nbsp; Are you just =
using it as a hint if it exists and then looking at the rest of the fields =
if it is not present?</span><o:p></o:p></p><p class=3DMsoNormal style=3D'ms=
o-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p>=
</o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>Jim</span><o:p></o:p></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span=
><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'bor=
der:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0=
cm'><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma",=
"sans-serif"'> Dick Hardt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" t=
arget=3D"_blank">dick.hardt@gmail.com</a>] <br><b>Sent:</b> Wednesday, May =
29, 2013 3:49 PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a href=3D"mailto:j=
ose@ietf.org" target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: [j=
ose] Should we delete the &quot;typ&quot; header field</span><o:p></o:p></p=
></div></div><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Well, I have=
 been using, but now realize the spec changed or I was confused.<o:p></o:p>=
</p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I had been setting =
&quot;typ&quot; to be either &quot;JWE&quot; or &quot;JWS&quot; depending o=
n the type of token I was creating or parsing as it was easier than looking=
 at &quot;alg&quot;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></=
div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-b=
ottom-alt:auto'>As currently defined, I don't see value in &quot;typ&quot;.=
<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-=
- Dick<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin-to=
p-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p></div></div><di=
v><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12.0p=
t'>&nbsp;<o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-a=
lt:auto;mso-margin-bottom-alt:auto'>On Wed, May 29, 2013 at 3:02 PM, Jim Sc=
haad &lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@a=
ugustcellars.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In reading t=
he documents, I am trying to understand the justification for having the &#=
8220;typ&#8221; header parameter in the JOSE documents.<o:p></o:p></p><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'>&nbsp;<o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'>The purpose of the field is to hold the type =
of the object. &nbsp;In the past, I believe that values which should now be=
 placed in the cty field (such as &#8220;JWT&#8221;) were placed in this fi=
eld as well.&nbsp; However the parameter is optional and an implementation =
cannot rely on its being present.&nbsp; This means that for all practical p=
urposes all of the code to determine the value of the type field from the v=
alues of the alg and enc fields. &nbsp;If the field was mandatory then this=
 code would disappear at a fairly small space cost and I can understand why=
 the parameter would be present.<o:p></o:p></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></=
p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'>Can anybody justify why this field should be present in the docume=
nt &#8211; or should it just disappear?<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D=
'color:#888888'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:#88=
8888'>Jim</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:#888888'>&nbsp;<=
/span><o:p></o:p></p></div></div><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;margin-bottom:12.0pt'><br>_____________________________________=
__________<br>jose mailing list<br><a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/li=
stinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</=
a><o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:aut=
o;mso-margin-bottom-alt:auto'><br><br clear=3Dall><o:p></o:p></p><div><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'>&nbsp;<o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-a=
lt:auto;mso-margin-bottom-alt:auto'>-- <br>-- Dick <o:p></o:p></p></div></d=
iv></div></div></div></div></div><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto'><br><br clear=3Dall><o:p></o:p></p>=
<div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto'>&nbsp;<o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-ma=
rgin-top-alt:auto;mso-margin-bottom-alt:auto'>-- <br>-- Dick <o:p></o:p></p=
></div></div></div></div></div><p class=3DMsoNormal style=3D'mso-margin-top=
-alt:auto;margin-bottom:12.0pt'><br>_______________________________________=
________<br>jose mailing list<br><a href=3D"mailto:jose@ietf.org" target=3D=
"_blank">jose@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listi=
nfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><=
o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto'><br><br clear=3Dall><o:p></o:p></p><div><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&=
nbsp;<o:p></o:p></p></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:=
auto;mso-margin-bottom-alt:auto'>-- <br>-- Dick <o:p></o:p></p></div></div>=
</div></div></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mar=
gin-bottom:12.0pt'><br>_______________________________________________<br>j=
ose mailing list<br><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose=
@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/jose" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p=
></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bot=
tom-alt:auto'>&nbsp;<o:p></o:p></p></div></div></div></div></div></div><p c=
lass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:aut=
o'>&nbsp;<o:p></o:p></p></div></div></div></div></div></div><p class=3DMsoN=
ormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o=
:p></o:p></p></div></div></div></div></div></div></div><p class=3DMsoNormal=
 style=3D'margin-bottom:12.0pt'><br>_______________________________________=
________<br>jose mailing list<br><a href=3D"mailto:jose@ietf.org" target=3D=
"_blank">jose@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listi=
nfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><=
o:p></o:p></p></div><p class=3DMsoNormal><br><br clear=3Dall><o:p></o:p></p=
><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>=
-- <o:p></o:p></p></div></div><p class=3DMsoNormal>Nat Sakimura (=3Dnat)<o:=
p></o:p></p><div><p class=3DMsoNormal>Chairman, OpenID Foundation<br><a hre=
f=3D"http://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</=
a><br>@_nat_en<o:p></o:p></p></div></div><p class=3DMsoNormal style=3D'marg=
in-bottom:12.0pt'><br>_______________________________________________<br>jo=
se mailing list<br><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/jose" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>=
</div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div><p class=3DM=
soNormal><br><br clear=3Dall><o:p></o:p></p><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><p class=3DMsoNormal>-- <br>Nat Sakimura (=3Dnat)<o:p=
></o:p></p><div><p class=3DMsoNormal>Chairman, OpenID Foundation<br><a href=
=3D"http://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a=
><br>@_nat_en<o:p></o:p></p></div></div></div></div></div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div></div></div></div><p class=3DMsoNormal><br><=
br clear=3Dall><o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><p class=3DMsoNormal>-- <br>Nat Sakimura (=3Dnat)<o:p></o:p></p><di=
v><p class=3DMsoNormal>Chairman, OpenID Foundation<br><a href=3D"http://nat=
.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br>@_nat_en<=
o:p></o:p></p></div></div></div></div></div><p class=3DMsoNormal><br><br cl=
ear=3Dall><o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></d=
iv></div></div><p class=3DMsoNormal><span class=3Dhoenzb><span style=3D'col=
or:#888888'>-- </span></span><span style=3D'color:#888888'><br><span class=
=3Dhoenzb>-- Dick </span></span><o:p></o:p></p></div></div><p class=3DMsoNo=
rmal><br><br clear=3Dall><o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p></div><p class=3DMsoNormal>-- <br>Nat Sakimura (=3Dnat)<o:p></o=
:p></p><div><p class=3DMsoNormal>Chairman, OpenID Foundation<br><a href=3D"=
http://nat.sakimura.org/" target=3D"_blank">http://nat.sakimura.org/</a><br=
>@_nat_en<o:p></o:p></p></div></div></div></body></html>=

--_000_CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075AHE111541eme_--

From ve7jtb@ve7jtb.com  Fri Jun  7 04:24:04 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16BC521F9408 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 04:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vcJC7hSkrrE for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 04:24:01 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id DC6BA21F8916 for <jose@ietf.org>; Fri,  7 Jun 2013 04:23:46 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m19so2914251wev.22 for <jose@ietf.org>; Fri, 07 Jun 2013 04:23:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=4VsFl9kGsfd59BzjEjEaRqNRJfWOmBZCYIqvaF3owEc=; b=jjJVv6zXV2HxbXvqJTKYDxKui2ktlkVMXpmgwQN2nSjpBC8Or9S7RY+ysrLYx1SqVk V/XPM8MqybS/1Yi+DnmDVqvmGcpiHnhhzueNxO0qYuGy7LtZ9vfV2aZr7G16kmPzcU9y HkxN7gBeqyNsHrkHxw5QoX+IB3Ea6Mjn9z4prBueh/oeBxhO+VT8PadU7BTPj2YMruwF mJE4tSFXXC9t1QX3yTYmPmOPmQdT6/xwcggLhFqkTu32qm611XeaJ1XHKlZz7q2NvwHx KxtU94Zg5rGKjr3zycKHhSsLXCGSA4gAKciiwQjkoS0m/QknEsjRCUyQEKEyrwU8wUF1 /9WA==
X-Received: by 10.180.189.41 with SMTP id gf9mr1627529wic.32.1370604225815; Fri, 07 Jun 2013 04:23:45 -0700 (PDT)
Received: from [192.168.0.93] ([87.213.45.202]) by mx.google.com with ESMTPSA id h8sm21931176wiz.9.2013.06.07.04.23.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 04:23:43 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_327D7355-3DBA-4569-ADBC-37ABCC85737D"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071C@HE111541.emea1.cds.t-internal.com>
Date: Fri, 7 Jun 2013 13:23:40 +0200
Message-Id: <5086C9DA-68F6-4ECE-87B5-FA12E493E07D@ve7jtb.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071C@HE111541.emea1.cds.t-internal.com>
To: <Axel.Nennker@telekom.de>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQkTR/24bm/vXqvs3zwbIZ6bAAX+I4SP5gz3IJekp6YF29bteiIlfWGFqaGne6DWR6jcJM84
Cc: rlb@ipv.sx, Michael.Jones@microsoft.com, jose@ietf.org
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 11:24:04 -0000

--Apple-Mail=_327D7355-3DBA-4569-ADBC-37ABCC85737D
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_36A31F44-FB7C-4204-891D-731F01878F85"


--Apple-Mail=_36A31F44-FB7C-4204-891D-731F01878F85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

crit was a relatively recent WG consensus that allowed for non critical =
header parameters by default. =20

Richard holds the unrelenting position that headers should not have =
integrity protection, and all header parameters should be optional =
unless defined otherwise in the core spec.

I don't want to rehash the argument, but the compromise allowed for non =
critical to be the default and future extensions to use crit to mark =
parameters that need to be understood by the recipient to securely =
process the message.

I understand the incremental edging towards the outcome you want, but =
endlessly revisiting consensus decisions will never allow us to finish.

As to "typ" I agree that it's main use is by JWT where it is described. =
That is a result of splitting the specs into two workgroups.  =20
It is an optional field, we should clarify its definition so that JWT =
and other specs that need it have it available without potential =
namespace issues.

That is what I thought WG decided.

On the topic of changes the clock is running down for projects with =
dependencies on JOSE.   At some point they will settle for what ever =
draft is current and ship based on that.
That would be an interoperability tragedy.   I have no control over what =
Mozzila and others decide,  but at the moment we don't seem to be =
instilling the confidence in others that we are capable of moving the =
ball the last yard over the line (My attempt at a sports analogy).

I agree with Axel and Mike on finishing.

John B.
On 2013-06-07, at 11:53 AM, <Axel.Nennker@telekom.de> wrote:

> +1 to Mike=92s comments.
> =20
> Usefulness of the standard is the important thing.
> =20
> =20
> =20
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of Mike Jones
> Sent: Friday, June 07, 2013 7:19 AM
> To: Richard Barnes; jose@ietf.org
> Subject: Re: [jose] What are we doing here?
> =20
> Excellent question, Richard, because it gets to the heart of why the =
JOSE specs are already highly successful and widely adopted.
> =20
>   - We are building useful tools that solve real problems for =
developers.
>   - We are practically demonstrating the value of rough consensus and =
running code.
>   - We are making simple things simple.
>   - We are making complex things possible, when necessary (but not at =
the expense of keeping simple things simple).
>   - We are developing specs with an explicit goal of enabling =
ubiquitous adoption.
>   - We are developing specs guided by practical engineering tradeoffs =
to enable commonly useful functionality in a straightforward manner.
> =20
> The level of adoption, with dozens of deployed implementations, is =
compelling evidence that we=92ve already achieved the goals above.  It=92s=
 time to =93ship it=94, as making the JOSE specs actual standards will =
only increase their adoption and value to the industry.
> =20
> That=92s what we=92re doing here.
> =20
>                                                             -- Mike
> =20
> P.S.  I would be careful reasoning from the premise of =93The perfect =
protocol is one from which nothing can be removed=94.  By that logic, =
the perfect specification is the null specification, which leaves all =
possibilities open, and solves no actual problems. ;-)
> =20
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of Richard Barnes
> Sent: Thursday, June 06, 2013 2:44 PM
> To: jose@ietf.org
> Subject: [jose] What are we doing here?
> =20
> The conversation about "typ" has brought us back to a familiar =
question for this working group -- what are we trying to do here?
> =20
> The current document is ambiguous on this topic.  On the one hand, it =
mostly covers the crypto bases, with things like "alg" and "enc".  On =
the other hand, it mixes in application design concepts like "typ" and =
"crit".  The result is a spec that's ambiguous in purpose and complex.  =
If I'm building an application with this, how do I decide what goes in =
the "crit" field, or what values to use for "typ"?   =20
> The charter for this working group is not ambiguous on this topic.  =
This group is chartered to do signing and encryption.  The JOSE formats =
should carry the parameters needed to perform those operations.  =
Anything else is extraneous, and in the spirit of "The perfect protocol =
is one from which nothing can be removed", should be removed.
> =20
> Now, I'm not going to be a hard-liner on this.  I won't complain about =
"zip" and "cty", since they are clearly defined and have clear use =
cases.  But "crit" and "typ" are so ambiguous and so little supported by =
use cases*, that they really should go.
> =20
> </rant>
> =20
> --Richard
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_36A31F44-FB7C-4204-891D-731F01878F85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><base href=3D"x-msg://4701/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">crit was a relatively recent WG =
consensus that allowed for non critical header parameters by default. =
&nbsp;<div><br></div><div>Richard holds the unrelenting position that =
headers should not have integrity protection, and all header parameters =
should be optional unless defined otherwise in the core =
spec.</div><div><br></div><div>I don't want to rehash the argument, but =
the compromise allowed for non critical to be the default and future =
extensions to use crit to mark parameters that need to be understood by =
the recipient to securely process the =
message.</div><div><br></div><div>I understand the incremental edging =
towards the outcome you want, but endlessly revisiting consensus =
decisions will never allow us to finish.</div><div><br></div><div>As to =
"typ" I agree that it's main use is by JWT where it is described. That =
is a result of splitting the specs into two workgroups. =
&nbsp;&nbsp;</div><div>It is an optional field, we should clarify its =
definition so that JWT and other specs that need it have it available =
without potential namespace issues.</div><div><br></div><div>That is =
what I thought WG decided.</div><div><br></div><div>On the topic of =
changes the clock is running down for projects with dependencies on =
JOSE. &nbsp; At some point they will settle for what ever draft is =
current and ship based on that.</div><div>That would be an =
interoperability tragedy. &nbsp; I have no control over what Mozzila and =
others decide, &nbsp;but at the moment we don't seem to be instilling =
the confidence in others that we are capable of moving the ball the last =
yard over the line (My attempt at a sports =
analogy).</div><div><br></div><div>I agree with Axel and Mike on =
finishing.</div><div><br></div><div>John B.</div><div><div><div>On =
2013-06-07, at 11:53 AM, &lt;<a =
href=3D"mailto:Axel.Nennker@telekom.de">Axel.Nennker@telekom.de</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">+1 to Mike=92s =
comments.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">Usefulness of the standard is the important =
thing.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">&nbsp;</span></div><div><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm; "><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> =
[mailto:jose-<a =
href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Mike =
Jones<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Friday, June 07, 2013 7:19 =
AM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span>Richard=
 Barnes; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [jose] What are we =
doing here?<o:p></o:p></span></div></div></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">Excellent question, Richard, because it gets to the =
heart of why the JOSE specs are already highly successful and widely =
adopted.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">&nbsp; - We are building useful tools that =
solve real problems for developers.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">&nbsp; - We are =
practically demonstrating the value of rough consensus and running =
code.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp; - We are making simple things =
simple.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp; - We are making complex things possible, when =
necessary (but not at the expense of keeping simple things =
simple).<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp; - We are developing specs with an explicit =
goal of enabling ubiquitous adoption.<o:p></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times =
New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">&nbsp; - We are =
developing specs guided by practical engineering tradeoffs to enable =
commonly useful functionality in a straightforward =
manner.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">The level of adoption, with dozens of =
deployed implementations, is compelling evidence that we=92ve already =
achieved the goals above.&nbsp; It=92s time to =93ship it=94, as making =
the JOSE specs actual standards will only increase their adoption and =
value to the industry.<o:p></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">That=92s what we=92re doing =
here.<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">P.S.&nbsp; I would be careful reasoning from =
the premise of =93</span>The perfect protocol is one from which nothing =
can be removed<span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">=94.&nbsp; By that logic, the =
perfect specification is the null specification, which leaves all =
possibilities open, and solves no actual problems. =
;-)<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">From:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> =
[mailto:jose-<a =
href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Richard =
Barnes<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, June 06, 2013 =
2:44 PM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[jose] What are we doing =
here?<o:p></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">The =
conversation about "typ" has brought us back to a familiar question for =
this working group -- what are we trying to do =
here?<o:p></o:p></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">The =
current document is ambiguous on this topic. &nbsp;On the one hand, it =
mostly covers the crypto bases, with things like "alg" and "enc". =
&nbsp;On the other hand, it mixes in application design concepts like =
"typ" and "crit". &nbsp;The result is a spec that's ambiguous in purpose =
and complex. &nbsp;If I'm building an application with this, how do I =
decide what goes in the "crit" field, or what values to use for "typ"? =
&nbsp; &nbsp;<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">The =
charter for this working group is not ambiguous on this topic. =
&nbsp;This group is chartered to do signing and encryption. &nbsp;The =
JOSE formats should carry the parameters needed to perform those =
operations. &nbsp;Anything else is extraneous, and in the spirit of "The =
perfect protocol is one from which nothing can be removed", should be =
removed.<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">Now, =
I'm not going to be a hard-liner on this. &nbsp;I won't complain about =
"zip" and "cty", since they are clearly defined and have clear use =
cases. &nbsp;But "crit" and "typ" are so ambiguous and so little =
supported by use cases*, that they really should =
go.<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">&lt;/rant&gt;<o:p></o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; =
">--Richard<o:p></o:p></div></div></div></div>____________________________=
___________________<br>jose mailing list<br><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/jose</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_36A31F44-FB7C-4204-891D-731F01878F85--

--Apple-Mail=_327D7355-3DBA-4569-ADBC-37ABCC85737D
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjA3MTEyMzQxWjAjBgkqhkiG9w0BCQQxFgQUfhMuBzFx
aNC2WEFeLYv8UBFE8BowgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAlZJny+NcIUWPBFJ2vrZ8H8jEkKcrsZ2mtEyvhnAO
5uyjyjBB/u+CfZRMezulsLHGPk8ffXv4SrasgC4NdqC+w+erle5I5R18bdxT+J+hC2xOQBrCPp+W
ZzN97oOjtrA2Ti4AGKZZ2U4MGqJY3kVC75ujHdjprGRXJ0s4Jb5dwySXCLB9YXy4rqt+rW2H0J2r
jnHfxn/APq3g5fMqr2qFl7b2QjoGvSkItGC1k4pLjm5rhc52DQQrRz6nbT3ZTIrfR3zEqe8bWWO6
NTIfEvF1FyLAqCkVnl3k89gZ6adpVdnQ+oEBNC0vQrxaN4rU/x2aLv8YwrnVKITRSRtTKpc5CgAA
AAAAAA==

--Apple-Mail=_327D7355-3DBA-4569-ADBC-37ABCC85737D--

From sal@idmachines.com  Fri Jun  7 05:23:40 2013
Return-Path: <sal@idmachines.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6174021F885A for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 05:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.466
X-Spam-Level: *
X-Spam-Status: No, score=1.466 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x5fyhIrsGbOD for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 05:23:26 -0700 (PDT)
Received: from atl4mhfb03.myregisteredsite.com (unknown [209.17.115.61]) by ietfa.amsl.com (Postfix) with ESMTP id 7922D21F8BC0 for <jose@ietf.org>; Fri,  7 Jun 2013 05:22:59 -0700 (PDT)
Received: from atl4mhob05.myregisteredsite.com ([209.17.115.101]) by atl4mhfb03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r57CMvsO018493 for <jose@ietf.org>; Fri, 7 Jun 2013 08:22:57 -0400
Received: from mailpod1.hostingplatform.com ([10.30.71.117]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r57CMrPd024768 for <jose@ietf.org>; Fri, 7 Jun 2013 08:22:53 -0400
Received: (qmail 11538 invoked by uid 0); 7 Jun 2013 12:22:53 -0000
X-TCPREMOTEIP: 74.104.46.28
X-Authenticated-UID: sal@idmachines.com
Received: from unknown (HELO salPC) (sal@idmachines.com@74.104.46.28) by 0 with ESMTPA; 7 Jun 2013 12:22:51 -0000
From: "Salvatore D'Agostino" <sal@idmachines.com>
To: <Axel.Nennker@telekom.de>, <Michael.Jones@microsoft.com>, <rlb@ipv.sx>, <jose@ietf.org>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071C@HE111541.emea1.cds.t-internal.com>
In-Reply-To: <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA071C@HE111541.emea1.cds.t-internal.com>
Date: Fri, 7 Jun 2013 08:22:45 -0400
Message-ID: <00d101ce6379$b7d22bc0$27768340$@com>
X-Mailer: Microsoft Office Outlook 12.0
MIME-Version: 1.0
Thread-Index: Ac5jZNh42fm3NoNMRqGYhN4btH2nsAAE2Hzw
Content-Language: en-us
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_00C9_01CE6358.2CBED9A0"
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 12:23:40 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00C9_01CE6358.2CBED9A0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00CA_01CE6358.2CBED9A0"


------=_NextPart_001_00CA_01CE6358.2CBED9A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

We don't have as strong opinion on typ and crit.

 

In general the effort has focused on flexibility  and encouraging code and
use meeting the needs for signing and encryption.  I believe these are the
spirit of Mike and Axel's comments an d  +1 to both of these.

 

Apologies if blocked, seems our domain got blacklisted (thanks Register..)

 

From: Axel.Nennker@telekom.de [mailto:Axel.Nennker@telekom.de] 
Sent: Friday, June 07, 2013 5:53 AM
To: Michael.Jones@microsoft.com; rlb@ipv.sx; jose@ietf.org
Subject: Re: [jose] What are we doing here?

 

+1 to Mike's comments.

 

Usefulness of the standard is the important thing.

 

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Friday, June 07, 2013 7:19 AM
To: Richard Barnes; jose@ietf.org
Subject: Re: [jose] What are we doing here?

 

Excellent question, Richard, because it gets to the heart of why the JOSE
specs are already highly successful and widely adopted.

 

  - We are building useful tools that solve real problems for developers.

  - We are practically demonstrating the value of rough consensus and
running code.

  - We are making simple things simple.

  - We are making complex things possible, when necessary (but not at the
expense of keeping simple things simple).

  - We are developing specs with an explicit goal of enabling ubiquitous
adoption.

  - We are developing specs guided by practical engineering tradeoffs to
enable commonly useful functionality in a straightforward manner.

 

The level of adoption, with dozens of deployed implementations, is
compelling evidence that we've already achieved the goals above.  It's time
to "ship it", as making the JOSE specs actual standards will only increase
their adoption and value to the industry.

 

That's what we're doing here.

 

                                                            -- Mike

 

P.S.  I would be careful reasoning from the premise of "The perfect protocol
is one from which nothing can be removed".  By that logic, the perfect
specification is the null specification, which leaves all possibilities
open, and solves no actual problems. ;-)

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
Richard Barnes
Sent: Thursday, June 06, 2013 2:44 PM
To: jose@ietf.org
Subject: [jose] What are we doing here?

 

The conversation about "typ" has brought us back to a familiar question for
this working group -- what are we trying to do here?

 

The current document is ambiguous on this topic.  On the one hand, it mostly
covers the crypto bases, with things like "alg" and "enc".  On the other
hand, it mixes in application design concepts like "typ" and "crit".  The
result is a spec that's ambiguous in purpose and complex.  If I'm building
an application with this, how do I decide what goes in the "crit" field, or
what values to use for "typ"?    

The charter for this working group is not ambiguous on this topic.  This
group is chartered to do signing and encryption.  The JOSE formats should
carry the parameters needed to perform those operations.  Anything else is
extraneous, and in the spirit of "The perfect protocol is one from which
nothing can be removed", should be removed.

 

Now, I'm not going to be a hard-liner on this.  I won't complain about "zip"
and "cty", since they are clearly defined and have clear use cases.  But
"crit" and "typ" are so ambiguous and so little supported by use cases*,
that they really should go.

 

</rant>

 

--Richard


------=_NextPart_001_00CA_01CE6358.2CBED9A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We don&#8217;t have as strong opinion on typ and =
crit.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>In general the effort has focused on flexibility &nbsp;and =
encouraging code and use meeting the needs for signing and =
encryption.&nbsp; I believe these are the spirit of Mike and =
Axel&#8217;s comments an d &nbsp;+1 to both of =
these.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Apologies if blocked, seems our domain got blacklisted (thanks =
Register..)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Axel.Nennker@telekom.de [mailto:Axel.Nennker@telekom.de] =
<br><b>Sent:</b> Friday, June 07, 2013 5:53 AM<br><b>To:</b> =
Michael.Jones@microsoft.com; rlb@ipv.sx; =
jose@ietf.org<br><b>Subject:</b> Re: [jose] What are we doing =
here?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>+1 to Mike&#8217;s comments.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Usefulness of the standard is the important =
thing.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Mike Jones<br><b>Sent:</b> Friday, June 07, 2013 =
7:19 AM<br><b>To:</b> Richard Barnes; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] What are we doing here?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Excellent question, Richard, because it gets to the heart of why the =
JOSE specs are already highly successful and widely =
adopted.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are building useful tools that solve real problems for =
developers.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are practically demonstrating the value of rough =
consensus and running code.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are making simple things simple.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are making complex things possible, when necessary (but =
not at the expense of keeping simple things =
simple).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are developing specs with an explicit goal of enabling =
ubiquitous adoption.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; - We are developing specs guided by practical engineering =
tradeoffs to enable commonly useful functionality in a straightforward =
manner.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The level of adoption, with dozens of deployed implementations, is =
compelling evidence that we&#8217;ve already achieved the goals =
above.&nbsp; It&#8217;s time to &#8220;ship it&#8221;, as making the =
JOSE specs actual standards will only increase their adoption and value =
to the industry.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>That&#8217;s what we&#8217;re doing here.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>P.S.&nbsp; I would be careful reasoning from the premise of =
&#8220;</span>The perfect protocol is one from which nothing can be =
removed<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8221;.&nbsp; By that logic, the perfect specification is the null =
specification, which leaves all possibilities open, and solves no actual =
problems. ;-)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Richard Barnes<br><b>Sent:</b> Thursday, June 06, =
2013 2:44 PM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] What are we doing here?<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>The =
conversation about &quot;typ&quot; has brought us back to a familiar =
question for this working group -- what are we trying to do =
here?<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The current document is ambiguous on this topic. =
&nbsp;On the one hand, it mostly covers the crypto bases, with things =
like &quot;alg&quot; and &quot;enc&quot;. &nbsp;On the other hand, it =
mixes in application design concepts like &quot;typ&quot; and =
&quot;crit&quot;. &nbsp;The result is a spec that's ambiguous in purpose =
and complex. &nbsp;If I'm building an application with this, how do I =
decide what goes in the &quot;crit&quot; field, or what values to use =
for &quot;typ&quot;? &nbsp; &nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>The charter for this working group is not ambiguous on =
this topic. &nbsp;This group is chartered to do signing and encryption. =
&nbsp;The JOSE formats should carry the parameters needed to perform =
those operations. &nbsp;Anything else is extraneous, and in the spirit =
of &quot;The perfect protocol is one from which nothing can be =
removed&quot;, should be removed.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Now, I'm not going to be a hard-liner on this. &nbsp;I =
won't complain about &quot;zip&quot; and &quot;cty&quot;, since they are =
clearly defined and have clear use cases. &nbsp;But &quot;crit&quot; and =
&quot;typ&quot; are so ambiguous and so little supported by use cases*, =
that they really should go.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&lt;/rant&gt;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div></div></div></body></html=
>
------=_NextPart_001_00CA_01CE6358.2CBED9A0--

------=_NextPart_000_00C9_01CE6358.2CBED9A0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITIjCCBDYw
ggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoTC0FkZFRy
dXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZ
QWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0yMDA1MzAxMDQ4Mzha
MG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3Qg
RXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz5vIABC054E5b7R+8bA/Ntfojts7e
mxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl62y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKe
dMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pOrwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCr
TLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1BX3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXE
XSp9t7TWxO6szRNEt8kr3UMAJfphuWlqWCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPV
NFonAgMBAAGjgdwwgdkwHQYDVR0OBBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOk
cTBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0
IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290
ggEBMA0GCSqGSIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7
rEFsR2CDUbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEU
LY69FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvhjJiD
yx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYEMIIEnTCC
A4WgAwIBAgIQND3pK6wnNP+PyzSU+8xwVDANBgkqhkiG9w0BAQUFADBvMQswCQYDVQQGEwJTRTEU
MBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3
b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290MB4XDTA1MDYwNzA4MDkxMFoX
DTIwMDUzMDEwNDgzOFowga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2Fs
dCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0
cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRo
ZW50aWNhdGlvbiBhbmQgRW1haWwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCyOYWk
8n2rQTtiRjeuzcFgdbw5ZflKGkeiucxIzGqY1U01GbmkQuXOSeKKLx580jEHx060g2SdLinVomTE
hb2FUTV5pE5okHsceqSSqBfymBXyk8zJpDKVuwxPML2YoAuL5W4bokb6eLyib6tZXqUvz8rabaov
66yhs2qqty5nNYt54R5piOLmRs2gpeq+C852OnoOm+r82idbPXMfIuZIYcZM82mxqC4bttQxICy8
goqOpA6l14lD/BZarx1x1xFZ2rqHDa/68+HC8KTFZ4zW1lQ63gqkugN3s2XI/R7TdGKqGMpokx6h
hX71R2XL+E1XKHTSNP8wtu72YjAUjCzrAgMBAAGjgfQwgfEwHwYDVR0jBBgwFoAUrb2YejS0Jvf6
xCZU7wO94CTLVBowHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59MA4GA1UdDwEB/wQEAwIB
BjAPBgNVHRMBAf8EBTADAQH/MBEGA1UdIAQKMAgwBgYEVR0gADBEBgNVHR8EPTA7MDmgN6A1hjNo
dHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vQWRkVHJ1c3RFeHRlcm5hbENBUm9vdC5jcmwwNQYIKwYB
BQUHAQEEKTAnMCUGCCsGAQUFBzABhhlodHRwOi8vb2NzcC51c2VydHJ1c3QuY29tMA0GCSqGSIb3
DQEBBQUAA4IBAQABvJzjYyiw8zEBwt973WKgAZ0jMQ+cknNTUeofTPrWn8TKL2d+eDMPdBa5kYeR
9Yom+mRwANge+QsEYlCHk4HU2vUj2zS7hVa0cDRueIM3HoUcxREVkl+HF72sav3xwtHMiV+xfPA+
UfI183zsYJhrOivg79+zfYbrtRv1W+yifJgT1wBQudEtc94DeHThBYUxXsuauZ2UxrmUN3Vy3ET7
Z+jw+iUeUqfaJelH4KDHPKBOsQo2+3dIn++Xivu0/uOUFKiDvFwtP9JgcWDuwnGCDOmINuPaILSj
oGyqlku4gI51ykkH9jsUut/cBdmf2+Cy5k2geCbn5y1uf1/GHogVMIIFGjCCBAKgAwIBAgIQbRnq
pxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVU
MRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr
MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmly
c3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBaFw0yMDA1
MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAw
DgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09N
T0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU
4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHff
sReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kAB
W0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJk
JpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IB
SzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4
Y2QnwS/ioFu8ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQK
MAgwBgYEVR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVRO
LVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVu
dF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcN
AQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjB
MCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T
4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrUyTo8
H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lEuJB+ytF5
OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggUlMIIEDaADAgECAhAxNisl
hAwmPFmhraHt/QtWMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl
YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGlt
aXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVt
YWlsIENBMB4XDTEyMTAyMjAwMDAwMFoXDTEzMTAyMjIzNTk1OVowIzEhMB8GCSqGSIb3DQEJARYS
c2FsQGlkbWFjaGluZXMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyMUItbfY
tMuC9vO6iN41DxtnlxM682Fr96jQQGvpQzUrj4tNMHUlad9Fge5rCHPryqG2bEATpf/fCunOsV9C
9D5+khqCpZlQzk6vdKxnHgv4tFv7KAv+6DxS9GCqgbNSLo1WSh16FnlwRAZT4jUd59GB5uHjxvEZ
E4eOAEKL+izQIEBzpMMDxDOS4J2wU3W88mCPLcuEESGKE5QUgRV2ARmyWMPdJhpFUpZGJv183zYf
JLLa6+mgd+cWbfPp3GUs+/xdpSd3gRY64XCsyPmygWC+zrw2XJW+bL1Ge+m5sUJ5DJSGE1XENdvj
2z6j0q56G1Q8SJrAY76XrTrNnGrMiwIDAQABo4IB4jCCAd4wHwYDVR0jBBgwFoAUehNOAHRbxnhj
ZCfBL+KgW7x5xXswHQYDVR0OBBYEFGSBNSyMTkmxv/++DoKmF05IEiYnMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqgSIZGaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNy
bDCBiAYIKwYBBQUHAQEEfDB6MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9D
T01PRE9DbGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wHQYDVR0RBBYwFIESc2FsQGlkbWFjaGluZXMuY29t
MA0GCSqGSIb3DQEBBQUAA4IBAQA+jYBRYaQc2qf+SipdyHuI7A9W76ZCWAqCmeez66TNECSjbcvA
pw1HEKiehUGT4BiGSqTEBLnXM4pqsD5vUZLMiFnVAXhkgkNAOBZFq9G/bJSPW6pW9cNIjWifyAtn
wdqYXakYWQIuws08lYfGM/751/DXPioEuFSv0pqfCm/r9ashpU9+qMSmX4+nmS5VuUtRrVsyujq9
lQ0Jic737mkW6iVDIJzg4oE2ujL7l6dJBM5VdbCJns4y/R2iBn5JfIcO8ZACDuw/If558mBvhRzI
K5iBLkgqVKM6C/XTQ9Z+rc0YOaooiOn2CO4hILdhicFwr8M6V5cTBMltmrfOLqwyMYIEZTCCBGEC
AQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNV
BAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8g
Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDE2KyWEDCY8WaGtoe39
C1YwCQYFKw4DAhoFAKCCApEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
DxcNMTMwNjA3MTIyMjM5WjAjBgkqhkiG9w0BCQQxFgQUV9ckXYYr/wnJ9t7Pe5tbL6/nZW4wgbcG
CSqGSIb3DQEJDzGBqTCBpjALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAoGCCqGSIb3DQMHMAsG
CWCGSAFlAwQBAjAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcwDQYIKoZIhvcNAwICAUAwDQYIKoZI
hvcNAwICASgwBwYFKw4DAhowCwYJYIZIAWUDBAIDMAsGCWCGSAFlAwQCAjALBglghkgBZQMEAgEw
CgYIKoZIhvcNAgUwgbkGCSsGAQQBgjcQBDGBqzCBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgT
EkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENB
IExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3Vy
ZSBFbWFpbCBDQQIQMTYrJYQMJjxZoa2h7f0LVjCBuwYLKoZIhvcNAQkQAgsxgauggagwgZMxCzAJ
BgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQx
GjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhl
bnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDE2KyWEDCY8WaGtoe39C1YwDQYJKoZIhvcN
AQEBBQAEggEAqjbK0Aj8TIdHHVpPAU+KD2P6tEyrmlrxk3YDVTh+visSI91F+sfL5qd4395vd9XV
AeuIxN1ehmQxn46H4aEukHDJeay9DXhKBhntVP1Bq7sw34rbj/SYEteFTJLH4zXn2FRGdN5f6HHl
CjadlRVf8q/wE7YTxz+iZtS2SVcIHDIfGmsAOES5ha/l5OF7rfv5o3gXjM+eqky7lwLaQdTTScaV
qZ3ung0GPSfjL5yUpWE1rs5U/52zgpNho4CqQ9Wne9wnzMumhSLgqtRRn1f/RBGivYL3l7uyZC/B
jRfIDZUv94NnxcdS4d42J2l9qbb3DcvtBLBTTnAphpFHMn2vkAAAAAAAAA==

------=_NextPart_000_00C9_01CE6358.2CBED9A0--


From rlb@ipv.sx  Fri Jun  7 07:23:09 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C27D21F98AD for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzcdK5BxiFXz for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:23:04 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF0821F9744 for <jose@ietf.org>; Fri,  7 Jun 2013 07:23:03 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id o13so3288793oag.25 for <jose@ietf.org>; Fri, 07 Jun 2013 07:23:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=7z8nw3g7bh5SL+sX+88cHcqXuMT813UUAyNE8m5ytog=; b=TPbSDRaKQsWHDeBdEqS9PMuz0W0kA+u9ZKAei8JYaQIW8POvOjE0LixcqMP/nE/Y1f o+eJPddJ9X6v26hc5oIHSrKkJstr6Jn8vMHY8suID+9iGw16StGbnykWvUmYXM3brXjo dMJ8S7dn/W1CqxivIEy8nCgU6i/dne2bEQXOunSS3SEg/GFXSlia54Z+KIkXDKjSMt3a vq0a/JxGqXwN0Fa/4i1t/tTckZlwzQULlmEMYJa69Jj1HLrm8+mGFhrIoqbRRzOb4a/Q ufvX2XdE0rAVhdF4VeZuTPwI25YBRrUH9BA6tEKMLYKxYZuyZkJcqtC+0Eioq5c3yTab bqog==
MIME-Version: 1.0
X-Received: by 10.182.60.136 with SMTP id h8mr21554536obr.47.1370614983352; Fri, 07 Jun 2013 07:23:03 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Fri, 7 Jun 2013 07:23:03 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 7 Jun 2013 10:23:03 -0400
Message-ID: <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c1c42034f5a504de912bfe
X-Gm-Message-State: ALoCoQn+JZvpu5YTp3U4T+YuCv94aLPbJ3fJCu2Yb5aTLkgpNeavJzFVCVfrUKFdMOqnfUefIDnf
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 14:23:09 -0000

--001a11c1c42034f5a504de912bfe
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Of course, motherhood, apple pie, etc. :)

The question is what we're trying to help developers do.  The developers I
talk to want a simple tool to do crypto stuff, full stop.  They don't want
semantic validation, critical fields, etc.

The adoption you're pointing to is not really relevant to the process here.
 The deployed implementations you're talking about are all in a limited
space, covering one use case.  And the current solution comes with baggage
for that use case that adds complexity for everyone else.  If you wanted to
address that one use case, you should have chartered for that, not general
signing and encryption.

Nonetheless, on timing, I agree that I'm getting a little bored with
fighting over this :)  I'm working on a review of -11 that tries to package
up all the remaining comments such that they can get resolved and we can
move on with life.

--Richard


On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>wro=
te:

>  Excellent question, Richard, because it gets to the heart of why the
> JOSE specs are already highly successful and widely adopted.****
>
> ** **
>
>   - We are building useful tools that solve real problems for developers.=
*
> ***
>
>   - We are practically demonstrating the value of rough consensus and
> running code.****
>
>   - We are making simple things simple.****
>
>   - We are making complex things possible, when necessary (but not at the
> expense of keeping simple things simple).****
>
>   - We are developing specs with an explicit goal of enabling ubiquitous
> adoption.****
>
>   - We are developing specs guided by practical engineering tradeoffs to
> enable commonly useful functionality in a straightforward manner.****
>
> ** **
>
> The level of adoption, with dozens of deployed implementations, is
> compelling evidence that we=92ve already achieved the goals above.  It=92=
s time
> to =93ship it=94, as making the JOSE specs actual standards will only inc=
rease
> their adoption and value to the industry.****
>
> ** **
>
> That=92s what we=92re doing here.****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> P.S.  I would be careful reasoning from the premise of =93The perfect
> protocol is one from which nothing can be removed=94.  By that logic, the
> perfect specification is the null specification, which leaves all
> possibilities open, and solves no actual problems. ;-)****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 06, 2013 2:44 PM
> *To:* jose@ietf.org
> *Subject:* [jose] What are we doing here?****
>
> ** **
>
> The conversation about "typ" has brought us back to a familiar question
> for this working group -- what are we trying to do here?****
>
> ** **
>
> The current document is ambiguous on this topic.  On the one hand, it
> mostly covers the crypto bases, with things like "alg" and "enc".  On the
> other hand, it mixes in application design concepts like "typ" and "crit"=
.
>  The result is a spec that's ambiguous in purpose and complex.  If I'm
> building an application with this, how do I decide what goes in the "crit=
"
> field, or what values to use for "typ"?    ****
>
> The charter for this working group is not ambiguous on this topic.  This
> group is chartered to do signing and encryption.  The JOSE formats should
> carry the parameters needed to perform those operations.  Anything else i=
s
> extraneous, and in the spirit of "The perfect protocol is one from which
> nothing can be removed", should be removed.****
>
> ** **
>
> Now, I'm not going to be a hard-liner on this.  I won't complain about
> "zip" and "cty", since they are clearly defined and have clear use cases.
>  But "crit" and "typ" are so ambiguous and so little supported by use
> cases*, that they really should go.****
>
> ** **
>
> </rant>****
>
> ** **
>
> --Richard****
>

--001a11c1c42034f5a504de912bfe
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Of course, motherhood, apple pie, etc. :)<div><br></div><d=
iv>The question is what we&#39;re trying to help developers do. =A0The deve=
lopers I talk to want a simple tool to do crypto stuff, full stop. =A0They =
don&#39;t want semantic validation, critical fields, etc. =A0</div>
<div><br></div><div>The adoption you&#39;re pointing to is not really relev=
ant to the process here. =A0The deployed implementations you&#39;re talking=
 about are all in a limited space, covering one use case. =A0And the curren=
t solution comes with baggage for that use case that adds complexity for ev=
eryone else. =A0If you wanted to address that one use case, you should have=
 chartered for that, not general signing and encryption.</div>
<div><br></div><div>Nonetheless, on timing, I agree that I&#39;m getting a =
little bored with fighting over this :) =A0I&#39;m working on a review of -=
11 that tries to package up all the remaining comments such that they can g=
et resolved and we can move on with life.</div>
<div><br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"=
_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly s=
uccessful and widely adopted.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are building use=
ful tools that solve real problems for developers.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are practically =
demonstrating the value of rough consensus and running code.<u></u><u></u><=
/span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making simpl=
e things simple.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making compl=
ex things possible, when necessary (but not at the expense of keeping simpl=
e things simple).<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs with an explicit goal of enabling ubiquitous adoption.<u></u><u></u></=
span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs guided by practical engineering tradeoffs to enable commonly useful fu=
nctionality in a straightforward manner.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we=92ve =
already achieved the goals above.=A0 It=92s time to =93ship it=94,
 as making the JOSE specs actual standards will only increase their adoptio=
n and value to the industry.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That=92s what we=92re doi=
ng here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.=A0 I would be carefu=
l reasoning from the premise of =93</span>The perfect protocol is one from =
which nothing can be removed<span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=94.=A0
 By that logic, the perfect specification is the null specification, which =
leaves all possibilities open, and solves no actual problems. ;-)<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?<u></u><u></u></span></p><div=
><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. =A0=
On the one hand, it mostly covers the crypto bases, with things like &quot;=
alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applicatio=
n design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result =
is a
 spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m building a=
n application with this, how do I decide what goes in the &quot;crit&quot; =
field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. =A0This group is chartered to do signing and encryption. =A0=
The JOSE formats should carry the parameters needed to perform those operat=
ions. =A0Anything else is extraneous, and
 in the spirit of &quot;The perfect protocol is one from which nothing can =
be removed&quot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I&#39;m not going to be a hard-liner on this. =
=A0I won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since th=
ey are clearly defined and have clear use cases. =A0But &quot;crit&quot; an=
d &quot;typ&quot; are so ambiguous and so little supported by use cases*, t=
hat they really
 should go.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c1c42034f5a504de912bfe--

From dick.hardt@gmail.com  Fri Jun  7 07:33:13 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F45921F9285 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.348
X-Spam-Level: 
X-Spam-Status: No, score=0.348 tagged_above=-999 required=5 tests=[AWL=2.947,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYd65jutr6F0 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:33:12 -0700 (PDT)
Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id BC7DB21F85EB for <jose@ietf.org>; Fri,  7 Jun 2013 07:33:11 -0700 (PDT)
Received: by mail-bk0-f52.google.com with SMTP id d7so1887029bkh.25 for <jose@ietf.org>; Fri, 07 Jun 2013 07:33:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ae05E4rJtx48SyY8D7P1GX+pbA0rKtoOxe0wzq0cJIE=; b=vp8ilZD9F5ezhk2nQE0VJAy9hKjSyDZTDrbOqkHzAgd3JjLk20BCr1rgvFUtzNuXfp xeIWcTTigZpA2j+VB8yPrK6JV8QOmhjelIEMK0O83dwff5laKx1s/YrFC+SccGG/TxWe BKUewYBfCzShHliDfTQb8mtctyqVzPjlNNClynATcV4GPWduO0A/kTI0JpllddNoNJ7u JEt0aAr3dWF+vuPqKL2v8pDdfjjEb0EgAqzafdTWZnCfaDra1Mwuxu3qVRszJ+CL/ktM xy2CPYHdVZRwa1l1u2+m0dDLOhZ7df5DIm8MlSFkCx4EoVLaM/UuejNd+aYnAOvQ8RnD PY4A==
MIME-Version: 1.0
X-Received: by 10.204.163.130 with SMTP id a2mr12401101bky.62.1370615590558; Fri, 07 Jun 2013 07:33:10 -0700 (PDT)
Received: by 10.204.168.12 with HTTP; Fri, 7 Jun 2013 07:33:10 -0700 (PDT)
In-Reply-To: <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com>
Date: Fri, 7 Jun 2013 07:33:10 -0700
Message-ID: <CAD9ie-uaxx0Yf6sW1-rUYEmD-CcNkJNC0cQ0Bypfs375fYpGYg@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=bcaec52d5531664e0604de914f32
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 14:33:13 -0000

--bcaec52d5531664e0604de914f32
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

MIke: I don't find your response very useful for understanding the question
Richard proposed. I find the spec confusing as to what I am supposed to do
when as an implementer. It seems that it is clear to all the people
associated with OpenID Connect, but without that context, it is confusing,
and frankly, some of the parameters seem like hacks to me. Perhaps some
additional clarification on what the parameters are intended for would
assist?

-- Dick


On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx> wrote:

> Of course, motherhood, apple pie, etc. :)
>
> The question is what we're trying to help developers do.  The developers =
I
> talk to want a simple tool to do crypto stuff, full stop.  They don't wan=
t
> semantic validation, critical fields, etc.
>
> The adoption you're pointing to is not really relevant to the process
> here.  The deployed implementations you're talking about are all in a
> limited space, covering one use case.  And the current solution comes wit=
h
> baggage for that use case that adds complexity for everyone else.  If you
> wanted to address that one use case, you should have chartered for that,
> not general signing and encryption.
>
> Nonetheless, on timing, I agree that I'm getting a little bored with
> fighting over this :)  I'm working on a review of -11 that tries to packa=
ge
> up all the remaining comments such that they can get resolved and we can
> move on with life.
>
> --Richard
>
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>w=
rote:
>
>>  Excellent question, Richard, because it gets to the heart of why the
>> JOSE specs are already highly successful and widely adopted.****
>>
>> ** **
>>
>>   - We are building useful tools that solve real problems for developers=
.
>> ****
>>
>>   - We are practically demonstrating the value of rough consensus and
>> running code.****
>>
>>   - We are making simple things simple.****
>>
>>   - We are making complex things possible, when necessary (but not at th=
e
>> expense of keeping simple things simple).****
>>
>>   - We are developing specs with an explicit goal of enabling ubiquitous
>> adoption.****
>>
>>   - We are developing specs guided by practical engineering tradeoffs to
>> enable commonly useful functionality in a straightforward manner.****
>>
>> ** **
>>
>> The level of adoption, with dozens of deployed implementations, is
>> compelling evidence that we=92ve already achieved the goals above.  It=
=92s time
>> to =93ship it=94, as making the JOSE specs actual standards will only in=
crease
>> their adoption and value to the industry.****
>>
>> ** **
>>
>> That=92s what we=92re doing here.****
>>
>> ** **
>>
>>                                                             -- Mike****
>>
>> ** **
>>
>> P.S.  I would be careful reasoning from the premise of =93The perfect
>> protocol is one from which nothing can be removed=94.  By that logic, th=
e
>> perfect specification is the null specification, which leaves all
>> possibilities open, and solves no actual problems. ;-)****
>>
>> ** **
>>
>> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
>> Of *Richard Barnes
>> *Sent:* Thursday, June 06, 2013 2:44 PM
>> *To:* jose@ietf.org
>> *Subject:* [jose] What are we doing here?****
>>
>> ** **
>>
>> The conversation about "typ" has brought us back to a familiar question
>> for this working group -- what are we trying to do here?****
>>
>> ** **
>>
>> The current document is ambiguous on this topic.  On the one hand, it
>> mostly covers the crypto bases, with things like "alg" and "enc".  On th=
e
>> other hand, it mixes in application design concepts like "typ" and "crit=
".
>>  The result is a spec that's ambiguous in purpose and complex.  If I'm
>> building an application with this, how do I decide what goes in the "cri=
t"
>> field, or what values to use for "typ"?    ****
>>
>> The charter for this working group is not ambiguous on this topic.  This
>> group is chartered to do signing and encryption.  The JOSE formats shoul=
d
>> carry the parameters needed to perform those operations.  Anything else =
is
>> extraneous, and in the spirit of "The perfect protocol is one from which
>> nothing can be removed", should be removed.****
>>
>> ** **
>>
>> Now, I'm not going to be a hard-liner on this.  I won't complain about
>> "zip" and "cty", since they are clearly defined and have clear use cases=
.
>>  But "crit" and "typ" are so ambiguous and so little supported by use
>> cases*, that they really should go.****
>>
>> ** **
>>
>> </rant>****
>>
>> ** **
>>
>> --Richard****
>>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>


--=20
-- Dick

--bcaec52d5531664e0604de914f32
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">MIke: I don&#39;t find your response very useful for under=
standing the question Richard proposed. I find the spec confusing as to wha=
t I am supposed to do when as an implementer. It seems that it is clear to =
all the people associated with OpenID Connect, but without that context, it=
 is confusing, and frankly, some of the parameters seem like hacks to me. P=
erhaps some additional clarification on what the parameters are intended fo=
r would assist?<div>
<br></div><div style>-- Dick</div></div><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <=
span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ip=
v.sx</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Of course, motherhood, appl=
e pie, etc. :)<div><br></div><div>The question is what we&#39;re trying to =
help developers do. =A0The developers I talk to want a simple tool to do cr=
ypto stuff, full stop. =A0They don&#39;t want semantic validation, critical=
 fields, etc. =A0</div>

<div><br></div><div>The adoption you&#39;re pointing to is not really relev=
ant to the process here. =A0The deployed implementations you&#39;re talking=
 about are all in a limited space, covering one use case. =A0And the curren=
t solution comes with baggage for that use case that adds complexity for ev=
eryone else. =A0If you wanted to address that one use case, you should have=
 chartered for that, not general signing and encryption.</div>

<div><br></div><div>Nonetheless, on timing, I agree that I&#39;m getting a =
little bored with fighting over this :) =A0I&#39;m working on a review of -=
11 that tries to package up all the remaining comments such that they can g=
et resolved and we can move on with life.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>--Richard</div></font></span></div><div class=3D"HOEnZb=
"><div class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_=
quote">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <span dir=3D"ltr">&lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly s=
uccessful and widely adopted.<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are building use=
ful tools that solve real problems for developers.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are practically =
demonstrating the value of rough consensus and running code.<u></u><u></u><=
/span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making simpl=
e things simple.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making compl=
ex things possible, when necessary (but not at the expense of keeping simpl=
e things simple).<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs with an explicit goal of enabling ubiquitous adoption.<u></u><u></u></=
span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs guided by practical engineering tradeoffs to enable commonly useful fu=
nctionality in a straightforward manner.<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we=92ve =
already achieved the goals above.=A0 It=92s time to =93ship it=94,
 as making the JOSE specs actual standards will only increase their adoptio=
n and value to the industry.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That=92s what we=92re doi=
ng here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.=A0 I would be carefu=
l reasoning from the premise of =93</span>The perfect protocol is one from =
which nothing can be removed<span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=94.=A0
 By that logic, the perfect specification is the null specification, which =
leaves all possibilities open, and solves no actual problems. ;-)<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?<u></u><u></u></span></p><div=
><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. =A0=
On the one hand, it mostly covers the crypto bases, with things like &quot;=
alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applicatio=
n design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result =
is a
 spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m building a=
n application with this, how do I decide what goes in the &quot;crit&quot; =
field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. =A0This group is chartered to do signing and encryption. =A0=
The JOSE formats should carry the parameters needed to perform those operat=
ions. =A0Anything else is extraneous, and
 in the spirit of &quot;The perfect protocol is one from which nothing can =
be removed&quot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I&#39;m not going to be a hard-liner on this. =
=A0I won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since th=
ey are clearly defined and have clear use cases. =A0But &quot;crit&quot; an=
d &quot;typ&quot; are so ambiguous and so little supported by use cases*, t=
hat they really
 should go.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>-- Dick
</div>

--bcaec52d5531664e0604de914f32--

From Michael.Jones@microsoft.com  Fri Jun  7 07:48:29 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94A721F8FDC for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbpvvnP6HNFB for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:48:23 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id EFEDA21F9050 for <jose@ietf.org>; Fri,  7 Jun 2013 07:48:22 -0700 (PDT)
Received: from BY2FFO11FD028.protection.gbl (10.1.15.203) by BY2FFO11HUB006.protection.gbl (10.1.14.164) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 7 Jun 2013 14:48:20 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD028.mail.protection.outlook.com (10.1.15.217) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 7 Jun 2013 14:48:20 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Fri, 7 Jun 2013 14:48:10 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Dick Hardt <dick.hardt@gmail.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] What are we doing here?
Thread-Index: AQHOYv8CR0v9d+v7FEav765iFV2uepkps4EwgACbi4CAAALTAIAAAgeQ
Date: Fri, 7 Jun 2013 14:48:10 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436780A27F@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com> <CAD9ie-uaxx0Yf6sW1-rUYEmD-CcNkJNC0cQ0Bypfs375fYpGYg@mail.gmail.com>
In-Reply-To: <CAD9ie-uaxx0Yf6sW1-rUYEmD-CcNkJNC0cQ0Bypfs375fYpGYg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436780A27FTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454002)(24454002)(199002)(189002)(31966008)(74502001)(74876001)(56776001)(512954002)(46102001)(51856001)(76796001)(79102001)(76786001)(80022001)(74706001)(69226001)(16406001)(65816001)(77982001)(66066001)(47446002)(63696002)(54356001)(74662001)(33656001)(49866001)(44976003)(54316002)(6806003)(15202345002)(76482001)(81342001)(77096001)(47736001)(56816003)(81542001)(16236675002)(4396001)(50986001)(55846006)(59766001)(47976001)(20776003)(71186001)(53806001)(74366001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB006; H:TK5EX14HUBC106.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0870212862
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 14:48:29 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436780A27FTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree that we should provide some additional clarification on the intende=
d purpose for the "typ" and "cty" parameters.  We just did provide substant=
ial additional clarification for "crit" in -11, based on the working group =
decisions at the interim meeting.  Are there other specific things that you=
'd suggest that we clarify, Dick?

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Dic=
k Hardt
Sent: Friday, June 07, 2013 7:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org
Subject: Re: [jose] What are we doing here?

MIke: I don't find your response very useful for understanding the question=
 Richard proposed. I find the spec confusing as to what I am supposed to do=
 when as an implementer. It seems that it is clear to all the people associ=
ated with OpenID Connect, but without that context, it is confusing, and fr=
ankly, some of the parameters seem like hacks to me. Perhaps some additiona=
l clarification on what the parameters are intended for would assist?

-- Dick

On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.s=
x>> wrote:
Of course, motherhood, apple pie, etc. :)

The question is what we're trying to help developers do.  The developers I =
talk to want a simple tool to do crypto stuff, full stop.  They don't want =
semantic validation, critical fields, etc.

The adoption you're pointing to is not really relevant to the process here.=
  The deployed implementations you're talking about are all in a limited sp=
ace, covering one use case.  And the current solution comes with baggage fo=
r that use case that adds complexity for everyone else.  If you wanted to a=
ddress that one use case, you should have chartered for that, not general s=
igning and encryption.

Nonetheless, on timing, I agree that I'm getting a little bored with fighti=
ng over this :)  I'm working on a review of -11 that tries to package up al=
l the remaining comments such that they can get resolved and we can move on=
 with life.

--Richard

On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com<mai=
lto:Michael.Jones@microsoft.com>> wrote:
Excellent question, Richard, because it gets to the heart of why the JOSE s=
pecs are already highly successful and widely adopted.

  - We are building useful tools that solve real problems for developers.
  - We are practically demonstrating the value of rough consensus and runni=
ng code.
  - We are making simple things simple.
  - We are making complex things possible, when necessary (but not at the e=
xpense of keeping simple things simple).
  - We are developing specs with an explicit goal of enabling ubiquitous ad=
option.
  - We are developing specs guided by practical engineering tradeoffs to en=
able commonly useful functionality in a straightforward manner.

The level of adoption, with dozens of deployed implementations, is compelli=
ng evidence that we've already achieved the goals above.  It's time to "shi=
p it", as making the JOSE specs actual standards will only increase their a=
doption and value to the industry.

That's what we're doing here.

                                                            -- Mike

P.S.  I would be careful reasoning from the premise of "The perfect protoco=
l is one from which nothing can be removed".  By that logic, the perfect sp=
ecification is the null specification, which leaves all possibilities open,=
 and solves no actual problems. ;-)

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Thursday, June 06, 2013 2:44 PM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] What are we doing here?

The conversation about "typ" has brought us back to a familiar question for=
 this working group -- what are we trying to do here?

The current document is ambiguous on this topic.  On the one hand, it mostl=
y covers the crypto bases, with things like "alg" and "enc".  On the other =
hand, it mixes in application design concepts like "typ" and "crit".  The r=
esult is a spec that's ambiguous in purpose and complex.  If I'm building a=
n application with this, how do I decide what goes in the "crit" field, or =
what values to use for "typ"?
The charter for this working group is not ambiguous on this topic.  This gr=
oup is chartered to do signing and encryption.  The JOSE formats should car=
ry the parameters needed to perform those operations.  Anything else is ext=
raneous, and in the spirit of "The perfect protocol is one from which nothi=
ng can be removed", should be removed.

Now, I'm not going to be a hard-liner on this.  I won't complain about "zip=
" and "cty", since they are clearly defined and have clear use cases.  But =
"crit" and "typ" are so ambiguous and so little supported by use cases*, th=
at they really should go.

</rant>

--Richard


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick

--_000_4E1F6AAD24975D4BA5B16804296739436780A27FTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I agree that we should pr=
ovide some additional clarification on the intended purpose for the &#8220;=
typ&#8221; and &#8220;cty&#8221; parameters.&nbsp; We just did provide subs=
tantial additional
 clarification for &#8220;crit&#8221; in -11, based on the working group de=
cisions at the interim meeting.&nbsp; Are there other specific things that =
you&#8217;d suggest that we clarify, Dick?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; jose@ietf.org<br>
<b>Subject:</b> Re: [jose] What are we doing here?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">MIke: I don't find your response very useful for und=
erstanding the question Richard proposed. I find the spec confusing as to w=
hat I am supposed to do when as an implementer. It seems that it is clear t=
o all the people associated with OpenID
 Connect, but without that context, it is confusing, and frankly, some of t=
he parameters seem like hacks to me. Perhaps some additional clarification =
on what the parameters are intended for would assist?<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<=
a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o:=
p></o:p></p>
<div>
<p class=3D"MsoNormal">Of course, motherhood, apple pie, etc. :)<o:p></o:p>=
</p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The question is what we're trying to help developers=
 do. &nbsp;The developers I talk to want a simple tool to do crypto stuff, =
full stop. &nbsp;They don't want semantic validation, critical fields, etc.=
 &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The adoption you're pointing to is not really releva=
nt to the process here. &nbsp;The deployed implementations you're talking a=
bout are all in a limited space, covering one use case. &nbsp;And the curre=
nt solution comes with baggage for that use
 case that adds complexity for everyone else. &nbsp;If you wanted to addres=
s that one use case, you should have chartered for that, not general signin=
g and encryption.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Nonetheless, on timing, I agree that I'm getting a l=
ittle bored with fighting over this :) &nbsp;I'm working on a review of -11=
 that tries to package up all the remaining comments such that they can get=
 resolved and we can move on with life.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<o:p></o:p></=
span></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@m=
icrosoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Excellent question, Richard, because it=
 gets to the heart of why the JOSE specs are already highly
 successful and widely adopted.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are building useful tools t=
hat solve real problems for developers.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are practically demonstrati=
ng the value of rough consensus and running code.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making simple things si=
mple.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making complex things p=
ossible, when necessary (but not at the expense of keeping simple
 things simple).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developing specs with a=
n explicit goal of enabling ubiquitous adoption.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developing specs guided=
 by practical engineering tradeoffs to enable commonly useful functionality
 in a straightforward manner.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The level of adoption, with dozens of d=
eployed implementations, is compelling evidence that we&#8217;ve
 already achieved the goals above.&nbsp; It&#8217;s time to &#8220;ship it&=
#8221;, as making the JOSE specs actual standards will only increase their =
adoption and value to the industry.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">That&#8217;s what we&#8217;re doing her=
e.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">P.S.&nbsp; I would be careful reasoning=
 from the premise of &#8220;</span>The perfect protocol is one from which
 nothing can be removed<span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8221;.&nbsp; By that lo=
gic, the perfect specification is the null specification, which leaves all =
possibilities open, and solves no actual problems. ;-)</span><o:p></o:p></p=
>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The conversation about &quot;typ&quot; has brought us back to a fa=
miliar question for this working group -- what are we trying to do here?<o:=
p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The current document is ambiguous on this topic. &nbsp;On the one =
hand, it mostly covers the crypto bases, with things like &quot;alg&quot; a=
nd &quot;enc&quot;. &nbsp;On the other hand, it mixes in application
 design concepts like &quot;typ&quot; and &quot;crit&quot;. &nbsp;The resul=
t is a spec that's ambiguous in purpose and complex. &nbsp;If I'm building =
an application with this, how do I decide what goes in the &quot;crit&quot;=
 field, or what values to use for &quot;typ&quot;? &nbsp; &nbsp;<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The charter for this working group is not ambiguous on this topic.=
 &nbsp;This group is chartered to do signing and encryption. &nbsp;The JOSE=
 formats should carry the parameters needed to
 perform those operations. &nbsp;Anything else is extraneous, and in the sp=
irit of &quot;The perfect protocol is one from which nothing can be removed=
&quot;, should be removed.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Now, I'm not going to be a hard-liner on this. &nbsp;I won't compl=
ain about &quot;zip&quot; and &quot;cty&quot;, since they are clearly defin=
ed and have clear use cases. &nbsp;But &quot;crit&quot; and &quot;typ&quot;=
 are so ambiguous
 and so little supported by use cases*, that they really should go.<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/rant&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">-- <br>
-- Dick <o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436780A27FTK5EX14MBXC283r_--

From rlb@ipv.sx  Fri Jun  7 07:54:16 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8DE821F969F for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeWS0lQIJtxl for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 07:54:04 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 79FA921F96C2 for <jose@ietf.org>; Fri,  7 Jun 2013 07:53:43 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id dn14so6716556obc.30 for <jose@ietf.org>; Fri, 07 Jun 2013 07:53:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=fYVuXhsytTT3xvuMXLYBwU8mbjzeDV2mMLpJ6YMU4JU=; b=DaHhPdPy61nzUEf3B5s4NFP+Y+OS4EywzSmluxKRXUy/UBNnvovk5lPWvsL/PbPDtz TbEap43N2wgiViW2mgsGmaQJ9TtoaQfe4QFZbDKV8LHvfGob8u+oahNGiQ8W8Gd5xzp8 i7B/FWNvfmO5+HBWR5SMWCMrfzv6D5IWc7Ct2dz3tGzCeVjlwwqKyfBYBckx611u0IIE FCYkLZAyngU6Unyo+ZJ6ZmRUrHLH2eo7PG5fkrnuCKBvCXu52DSj8hvdLIp+UoHGvukZ DCs7Rt1avJ+C8KfpubgEXHqc3Hm28i/onN/FSCIrHqBRMYixbtd3vzGaN3Uu52F8F24m DO9w==
MIME-Version: 1.0
X-Received: by 10.60.33.202 with SMTP id t10mr21754099oei.2.1370616823347; Fri, 07 Jun 2013 07:53:43 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Fri, 7 Jun 2013 07:53:43 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
Date: Fri, 7 Jun 2013 10:53:43 -0400
Message-ID: <CAL02cgTW-ho36gYGZdYJOOem96tj4RRmubxS9cd4k=WbQc3itw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e013c66b4e10ce604de919800
X-Gm-Message-State: ALoCoQkNuHNbLQBdHRA6o3U1Y2ZZCo+UcL5MpWGSfTgbkYuWe6DauPt15z81sNw5L/smGQH0/TfE
Cc: "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: [jose] Use case for "typ" (Re:  What are we doing here?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 14:54:17 -0000

--089e013c66b4e10ce604de919800
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

[Popping out to a separate thread, since we're into specifics here]

Mike:

I asked earlier for an example of an application that that needs "typ",
noting that JWT doesn't count because it can provide that via two other
channels ("cty" and OAuth).  Could you provide one?

Thanks,
--Richard


On Fri, Jun 7, 2013 at 10:48 AM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  I agree that we should provide some additional clarification on the
> intended purpose for the =93typ=94 and =93cty=94 parameters.  We just did=
 provide
> substantial additional clarification for =93crit=94 in -11, based on the
> working group decisions at the interim meeting.  Are there other specific
> things that you=92d suggest that we clarify, Dick?****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Dick Hardt
> *Sent:* Friday, June 07, 2013 7:33 AM
> *To:* Richard Barnes
> *Cc:* Mike Jones; jose@ietf.org
> *Subject:* Re: [jose] What are we doing here?****
>
> ** **
>
> MIke: I don't find your response very useful for understanding the
> question Richard proposed. I find the spec confusing as to what I am
> supposed to do when as an implementer. It seems that it is clear to all t=
he
> people associated with OpenID Connect, but without that context, it is
> confusing, and frankly, some of the parameters seem like hacks to me.
> Perhaps some additional clarification on what the parameters are intended
> for would assist?****
>
> ** **
>
> -- Dick****
>
> ** **
>
> On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx> wrote:****
>
> Of course, motherhood, apple pie, etc. :)****
>
> ** **
>
> The question is what we're trying to help developers do.  The developers =
I
> talk to want a simple tool to do crypto stuff, full stop.  They don't wan=
t
> semantic validation, critical fields, etc.  ****
>
> ** **
>
> The adoption you're pointing to is not really relevant to the process
> here.  The deployed implementations you're talking about are all in a
> limited space, covering one use case.  And the current solution comes wit=
h
> baggage for that use case that adds complexity for everyone else.  If you
> wanted to address that one use case, you should have chartered for that,
> not general signing and encryption.****
>
> ** **
>
> Nonetheless, on timing, I agree that I'm getting a little bored with
> fighting over this :)  I'm working on a review of -11 that tries to packa=
ge
> up all the remaining comments such that they can get resolved and we can
> move on with life.****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> Excellent question, Richard, because it gets to the heart of why the JOSE
> specs are already highly successful and widely adopted.****
>
>  ****
>
>   - We are building useful tools that solve real problems for developers.=
*
> ***
>
>   - We are practically demonstrating the value of rough consensus and
> running code.****
>
>   - We are making simple things simple.****
>
>   - We are making complex things possible, when necessary (but not at the
> expense of keeping simple things simple).****
>
>   - We are developing specs with an explicit goal of enabling ubiquitous
> adoption.****
>
>   - We are developing specs guided by practical engineering tradeoffs to
> enable commonly useful functionality in a straightforward manner.****
>
>  ****
>
> The level of adoption, with dozens of deployed implementations, is
> compelling evidence that we=92ve already achieved the goals above.  It=92=
s time
> to =93ship it=94, as making the JOSE specs actual standards will only inc=
rease
> their adoption and value to the industry.****
>
>  ****
>
> That=92s what we=92re doing here.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> P.S.  I would be careful reasoning from the premise of =93The perfect
> protocol is one from which nothing can be removed=94.  By that logic, the
> perfect specification is the null specification, which leaves all
> possibilities open, and solves no actual problems. ;-)****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 06, 2013 2:44 PM
> *To:* jose@ietf.org
> *Subject:* [jose] What are we doing here?****
>
>  ****
>
> The conversation about "typ" has brought us back to a familiar question
> for this working group -- what are we trying to do here?****
>
>  ****
>
> The current document is ambiguous on this topic.  On the one hand, it
> mostly covers the crypto bases, with things like "alg" and "enc".  On the
> other hand, it mixes in application design concepts like "typ" and "crit"=
.
>  The result is a spec that's ambiguous in purpose and complex.  If I'm
> building an application with this, how do I decide what goes in the "crit=
"
> field, or what values to use for "typ"?    ****
>
> The charter for this working group is not ambiguous on this topic.  This
> group is chartered to do signing and encryption.  The JOSE formats should
> carry the parameters needed to perform those operations.  Anything else i=
s
> extraneous, and in the spirit of "The perfect protocol is one from which
> nothing can be removed", should be removed.****
>
>  ****
>
> Now, I'm not going to be a hard-liner on this.  I won't complain about
> "zip" and "cty", since they are clearly defined and have clear use cases.
>  But "crit" and "typ" are so ambiguous and so little supported by use
> cases*, that they really should go.****
>
>  ****
>
> </rant>****
>
>  ****
>
> --Richard****
>
> ** **
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
> ** **
>
> --
> -- Dick ****
>

--089e013c66b4e10ce604de919800
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">[Popping out to a separate thread, since we&#39;re into sp=
ecifics here]<div><br></div><div>Mike:<br><br>I asked earlier for an exampl=
e of an application that that needs &quot;typ&quot;, noting that JWT doesn&=
#39;t count because it can provide that via two other channels (&quot;cty&q=
uot; and OAuth). =A0Could you provide one? =A0</div>
<div><br></div><div>Thanks,</div><div>--Richard<br><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Fri, Jun 7, 2013 at 10:48 AM, Mike=
 Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com"=
 target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I agree that we should pr=
ovide some additional clarification on the intended purpose for the =93typ=
=94 and =93cty=94 parameters.=A0 We just did provide substantial additional
 clarification for =93crit=94 in -11, based on the working group decisions =
at the interim meeting.=A0 Are there other specific things that you=92d sug=
gest that we clarify, Dick?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] What are we doing here?<u></u><u></u></span></p>=
<div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">MIke: I don&#39;t find your response very useful for=
 understanding the question Richard proposed. I find the spec confusing as =
to what I am supposed to do when as an implementer. It seems that it is cle=
ar to all the people associated with OpenID
 Connect, but without that context, it is confusing, and frankly, some of t=
he parameters seem like hacks to me. Perhaps some additional clarification =
on what the parameters are intended for would assist?<u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<=
a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u>=
</u><u></u></p>
<div>
<p class=3D"MsoNormal">Of course, motherhood, apple pie, etc. :)<u></u><u><=
/u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The question is what we&#39;re trying to help develo=
pers do. =A0The developers I talk to want a simple tool to do crypto stuff,=
 full stop. =A0They don&#39;t want semantic validation, critical fields, et=
c. =A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The adoption you&#39;re pointing to is not really re=
levant to the process here. =A0The deployed implementations you&#39;re talk=
ing about are all in a limited space, covering one use case. =A0And the cur=
rent solution comes with baggage for that use
 case that adds complexity for everyone else. =A0If you wanted to address t=
hat one use case, you should have chartered for that, not general signing a=
nd encryption.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nonetheless, on timing, I agree that I&#39;m getting=
 a little bored with fighting over this :) =A0I&#39;m working on a review o=
f -11 that tries to package up all the remaining comments such that they ca=
n get resolved and we can move on with life.<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><u></u>=A0<u></u></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<u></u><u></u=
></span></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@m=
icrosoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly
 successful and widely adopted.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are building use=
ful tools that solve real problems for developers.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are practically =
demonstrating the value of rough consensus and running code.</span><u></u><=
u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making simpl=
e things simple.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making compl=
ex things possible, when necessary (but not at the expense of keeping simpl=
e
 things simple).</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs with an explicit goal of enabling ubiquitous adoption.</span><u></u><u=
></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs guided by practical engineering tradeoffs to enable commonly useful fu=
nctionality
 in a straightforward manner.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we=92ve
 already achieved the goals above.=A0 It=92s time to =93ship it=94, as maki=
ng the JOSE specs actual standards will only increase their adoption and va=
lue to the industry.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That=92s what we=92re doi=
ng here.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.=A0 I would be carefu=
l reasoning from the premise of =93</span>The perfect protocol is one from =
which
 nothing can be removed<span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=94.=A0 By that logic, th=
e perfect specification is the null specification, which leaves all possibi=
lities open, and solves no actual problems. ;-)</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. =A0=
On the one hand, it mostly covers the crypto bases, with things like &quot;=
alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applicatio=
n
 design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result i=
s a spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m buildin=
g an application with this, how do I decide what goes in the &quot;crit&quo=
t; field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u><=
/p>

</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. =A0This group is chartered to do signing and encryption. =A0=
The JOSE formats should carry the parameters needed to
 perform those operations. =A0Anything else is extraneous, and in the spiri=
t of &quot;The perfect protocol is one from which nothing can be removed&qu=
ot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I&#39;m not going to be a hard-liner on this. =
=A0I won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since th=
ey are clearly defined and have clear use cases. =A0But &quot;crit&quot; an=
d &quot;typ&quot; are so ambiguous
 and so little supported by use cases*, that they really should go.<u></u><=
u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">-- <br>
-- Dick <u></u><u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div></div></div>

--089e013c66b4e10ce604de919800--

From Michael.Jones@microsoft.com  Fri Jun  7 08:19:37 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55EE521F91BC for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w8caZ2PIkqGs for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:19:31 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0211.outbound.protection.outlook.com [207.46.163.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4612E21F9050 for <jose@ietf.org>; Fri,  7 Jun 2013 08:19:31 -0700 (PDT)
Received: from BY2FFO11FD015.protection.gbl (10.1.15.200) by BY2FFO11HUB030.protection.gbl (10.1.14.115) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 7 Jun 2013 15:09:39 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD015.mail.protection.outlook.com (10.1.14.131) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 7 Jun 2013 15:09:39 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Fri, 7 Jun 2013 15:08:38 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Use case for "typ" (Re:  What are we doing here?)
Thread-Index: AQHOY47x/x9/wIdlAEueYq4QJVTT9pkqWFcQ
Date: Fri, 7 Jun 2013 15:08:37 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436780A35A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTW-ho36gYGZdYJOOem96tj4RRmubxS9cd4k=WbQc3itw@mail.gmail.com>
In-Reply-To: <CAL02cgTW-ho36gYGZdYJOOem96tj4RRmubxS9cd4k=WbQc3itw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436780A35ATK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(164054003)(24454002)(377454002)(189002)(199002)(77096001)(79102001)(77982001)(6806003)(76786001)(56816003)(65816001)(20776003)(76796001)(80022001)(54316002)(56776001)(74876001)(66066001)(74662001)(74706001)(81542001)(512954002)(63696002)(33656001)(16406001)(31966008)(76482001)(71186001)(51856001)(46102001)(53806001)(44976003)(59766001)(16236675002)(47976001)(54356001)(49866001)(50986001)(55846006)(69226001)(81342001)(47736001)(74502001)(74366001)(47446002)(15202345002)(4396001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB030; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0870212862
Cc: "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Use case for "typ" (Re:  What are we doing here?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 15:19:37 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436780A35ATK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

"typ" is there to dynamically answer the question "What is this data struct=
ure?" for applications.  It's needed in cases that that's potentially ambig=
uous.  If for instance, a token might be either a Facebook signed request o=
r a JWT, the "typ" value could be used to distinguish between them.

You're wrong that "cty" could be used for that, because "cty" answers the q=
uestion "What is the data structure that is the payload of this JOSE messag=
e?" - not "What is this data structure?".  The distinction is particularly =
important because as of -09 we decided to allow additional header parameter=
s to be added by applications that must be ignored if not understood.  So "=
cty" doesn't provide a comprehensive answer to the question "What is this d=
ata structure?".

I know of no OAuth Mechanism for providing a general-case answer to the que=
stion "What is this data structure?" (other than the use of "typ" :)).  Wha=
t specifically were you thinking of there?

So JWT needs it, and is a valid application.  John Bradley has also describ=
ed a number of other potential uses.  Again, I haven't heard anyone say tha=
t Jim's original logic for why "typ" is the way it is today was wrong - onl=
y that more clarification is needed, which we'll do.

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Friday, June 07, 2013 7:54 AM
To: Mike Jones
Cc: jose@ietf.org; Dick Hardt
Subject: [jose] Use case for "typ" (Re: What are we doing here?)

[Popping out to a separate thread, since we're into specifics here]

Mike:

I asked earlier for an example of an application that that needs "typ", not=
ing that JWT doesn't count because it can provide that via two other channe=
ls ("cty" and OAuth).  Could you provide one?

Thanks,
--Richard

On Fri, Jun 7, 2013 at 10:48 AM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
I agree that we should provide some additional clarification on the intende=
d purpose for the "typ" and "cty" parameters.  We just did provide substant=
ial additional clarification for "crit" in -11, based on the working group =
decisions at the interim meeting.  Are there other specific things that you=
'd suggest that we clarify, Dick?

                                                            -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Dick Hardt
Sent: Friday, June 07, 2013 7:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] What are we doing here?

MIke: I don't find your response very useful for understanding the question=
 Richard proposed. I find the spec confusing as to what I am supposed to do=
 when as an implementer. It seems that it is clear to all the people associ=
ated with OpenID Connect, but without that context, it is confusing, and fr=
ankly, some of the parameters seem like hacks to me. Perhaps some additiona=
l clarification on what the parameters are intended for would assist?

-- Dick

On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.s=
x>> wrote:
Of course, motherhood, apple pie, etc. :)

The question is what we're trying to help developers do.  The developers I =
talk to want a simple tool to do crypto stuff, full stop.  They don't want =
semantic validation, critical fields, etc.

The adoption you're pointing to is not really relevant to the process here.=
  The deployed implementations you're talking about are all in a limited sp=
ace, covering one use case.  And the current solution comes with baggage fo=
r that use case that adds complexity for everyone else.  If you wanted to a=
ddress that one use case, you should have chartered for that, not general s=
igning and encryption.

Nonetheless, on timing, I agree that I'm getting a little bored with fighti=
ng over this :)  I'm working on a review of -11 that tries to package up al=
l the remaining comments such that they can get resolved and we can move on=
 with life.

--Richard

On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com<mai=
lto:Michael.Jones@microsoft.com>> wrote:
Excellent question, Richard, because it gets to the heart of why the JOSE s=
pecs are already highly successful and widely adopted.

  - We are building useful tools that solve real problems for developers.
  - We are practically demonstrating the value of rough consensus and runni=
ng code.
  - We are making simple things simple.
  - We are making complex things possible, when necessary (but not at the e=
xpense of keeping simple things simple).
  - We are developing specs with an explicit goal of enabling ubiquitous ad=
option.
  - We are developing specs guided by practical engineering tradeoffs to en=
able commonly useful functionality in a straightforward manner.

The level of adoption, with dozens of deployed implementations, is compelli=
ng evidence that we've already achieved the goals above.  It's time to "shi=
p it", as making the JOSE specs actual standards will only increase their a=
doption and value to the industry.

That's what we're doing here.

                                                            -- Mike

P.S.  I would be careful reasoning from the premise of "The perfect protoco=
l is one from which nothing can be removed".  By that logic, the perfect sp=
ecification is the null specification, which leaves all possibilities open,=
 and solves no actual problems. ;-)

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Thursday, June 06, 2013 2:44 PM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] What are we doing here?

The conversation about "typ" has brought us back to a familiar question for=
 this working group -- what are we trying to do here?

The current document is ambiguous on this topic.  On the one hand, it mostl=
y covers the crypto bases, with things like "alg" and "enc".  On the other =
hand, it mixes in application design concepts like "typ" and "crit".  The r=
esult is a spec that's ambiguous in purpose and complex.  If I'm building a=
n application with this, how do I decide what goes in the "crit" field, or =
what values to use for "typ"?
The charter for this working group is not ambiguous on this topic.  This gr=
oup is chartered to do signing and encryption.  The JOSE formats should car=
ry the parameters needed to perform those operations.  Anything else is ext=
raneous, and in the spirit of "The perfect protocol is one from which nothi=
ng can be removed", should be removed.

Now, I'm not going to be a hard-liner on this.  I won't complain about "zip=
" and "cty", since they are clearly defined and have clear use cases.  But =
"crit" and "typ" are so ambiguous and so little supported by use cases*, th=
at they really should go.

</rant>

--Richard


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick


--_000_4E1F6AAD24975D4BA5B16804296739436780A35ATK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;typ&#8221; is ther=
e to dynamically answer the question &#8220;What is this data structure?&#8=
221; for applications.&nbsp; It&#8217;s needed in cases that that&#8217;s p=
otentially ambiguous.&nbsp;
 If for instance, a token might be either a Facebook signed request or a JW=
T, the &#8220;typ&#8221; value could be used to distinguish between them.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">You&#8217;re wrong that &=
#8220;cty&#8221; could be used for that, because &#8220;cty&#8221; answers =
the question &#8220;What is the data structure that is the payload of this =
JOSE message?&#8221; &#8211;
 not &#8220;What is this data structure?&#8221;.&nbsp; The distinction is p=
articularly important because as of -09 we decided to allow additional head=
er parameters to be added by applications that must be ignored if not under=
stood.&nbsp; So &#8220;cty&#8221; doesn&#8217;t provide a comprehensive
 answer to the question &#8220;What is this data structure?&#8221;.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I know of no OAuth Mechan=
ism for providing a general-case answer to the question &#8220;What is this=
 data structure?&#8221; (other than the use of &#8220;typ&#8221;
</span><span style=3D"font-size:11.0pt;font-family:Wingdings;color:#1F497D"=
>J</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">).&nbsp; What specifically were you thi=
nking of there?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So JWT needs it, and is a=
 valid application.&nbsp; John Bradley has also described a number of other=
 potential uses.&nbsp; Again, I haven&#8217;t heard anyone say that Jim&#82=
17;s
 original logic for why &#8220;typ&#8221; is the way it is today was wrong =
&#8211; only that more clarification is needed, which we&#8217;ll do.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Friday, June 07, 2013 7:54 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> jose@ietf.org; Dick Hardt<br>
<b>Subject:</b> [jose] Use case for &quot;typ&quot; (Re: What are we doing =
here?)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">[Popping out to a separate thread, since we're into =
specifics here]<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Mike:<br>
<br>
I asked earlier for an example of an application that that needs &quot;typ&=
quot;, noting that JWT doesn't count because it can provide that via two ot=
her channels (&quot;cty&quot; and OAuth). &nbsp;Could you provide one? &nbs=
p;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 10:48 AM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I agree that we should provide some add=
itional clarification on the intended purpose for the &#8220;typ&#8221;
 and &#8220;cty&#8221; parameters.&nbsp; We just did provide substantial ad=
ditional clarification for &#8220;crit&#8221; in -11, based on the working =
group decisions at the interim meeting.&nbsp; Are there other specific thin=
gs that you&#8217;d suggest that we clarify, Dick?</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] What are we doing here?</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">MIke: I don't find your response very useful for understanding the=
 question Richard proposed. I find the spec confusing as to what I am suppo=
sed to do when as an implementer. It
 seems that it is clear to all the people associated with OpenID Connect, b=
ut without that context, it is confusing, and frankly, some of the paramete=
rs seem like hacks to me. Perhaps some additional clarification on what the=
 parameters are intended for would
 assist?<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-- Dick<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<a href=3D"mail=
to:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Of course, motherhood, apple pie, etc. :)<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The question is what we're trying to help developers do. &nbsp;The=
 developers I talk to want a simple tool to do crypto stuff, full stop. &nb=
sp;They don't want semantic validation, critical
 fields, etc. &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The adoption you're pointing to is not really relevant to the proc=
ess here. &nbsp;The deployed implementations you're talking about are all i=
n a limited space, covering one use case.
 &nbsp;And the current solution comes with baggage for that use case that a=
dds complexity for everyone else. &nbsp;If you wanted to address that one u=
se case, you should have chartered for that, not general signing and encryp=
tion.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Nonetheless, on timing, I agree that I'm getting a little bored wi=
th fighting over this :) &nbsp;I'm working on a review of -11 that tries to=
 package up all the remaining comments such
 that they can get resolved and we can move on with life.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">--Richard</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a href=3D"mailto:M=
ichael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</=
a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Excellent question, Richard, because it=
 gets to the heart of why the JOSE specs are already highly
 successful and widely adopted.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are building useful tools t=
hat solve real problems for developers.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are practically demonstrati=
ng the value of rough consensus and running code.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making simple things si=
mple.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are making complex things p=
ossible, when necessary (but not at the expense of keeping simple
 things simple).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developing specs with a=
n explicit goal of enabling ubiquitous adoption.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp; - We are developing specs guided=
 by practical engineering tradeoffs to enable commonly useful functionality
 in a straightforward manner.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The level of adoption, with dozens of d=
eployed implementations, is compelling evidence that we&#8217;ve
 already achieved the goals above.&nbsp; It&#8217;s time to &#8220;ship it&=
#8221;, as making the JOSE specs actual standards will only increase their =
adoption and value to the industry.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">That&#8217;s what we&#8217;re doing her=
e.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">P.S.&nbsp; I would be careful reasoning=
 from the premise of &#8220;</span>The perfect protocol is one from which
 nothing can be removed<span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8221;.&nbsp; By that lo=
gic, the perfect specification is the null specification, which leaves all =
possibilities open, and solves no actual problems. ;-)</span><o:p></o:p></p=
>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The conversation about &quot;typ&quot; has brought us back to a fa=
miliar question for this working group -- what are we trying to do here?<o:=
p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The current document is ambiguous on this topic. &nbsp;On the one =
hand, it mostly covers the crypto bases, with things like &quot;alg&quot; a=
nd &quot;enc&quot;. &nbsp;On the other hand, it mixes in application
 design concepts like &quot;typ&quot; and &quot;crit&quot;. &nbsp;The resul=
t is a spec that's ambiguous in purpose and complex. &nbsp;If I'm building =
an application with this, how do I decide what goes in the &quot;crit&quot;=
 field, or what values to use for &quot;typ&quot;? &nbsp; &nbsp;<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The charter for this working group is not ambiguous on this topic.=
 &nbsp;This group is chartered to do signing and encryption. &nbsp;The JOSE=
 formats should carry the parameters needed to
 perform those operations. &nbsp;Anything else is extraneous, and in the sp=
irit of &quot;The perfect protocol is one from which nothing can be removed=
&quot;, should be removed.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Now, I'm not going to be a hard-liner on this. &nbsp;I won't compl=
ain about &quot;zip&quot; and &quot;cty&quot;, since they are clearly defin=
ed and have clear use cases. &nbsp;But &quot;crit&quot; and &quot;typ&quot;=
 are so ambiguous
 and so little supported by use cases*, that they really should go.<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/rant&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<br>
-- Dick <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436780A35ATK5EX14MBXC283r_--

From prateek.mishra@oracle.com  Fri Jun  7 08:24:17 2013
Return-Path: <prateek.mishra@oracle.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6A21F85DC for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqE0bS8eV8X7 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:24:11 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 9F33D21F85D1 for <jose@ietf.org>; Fri,  7 Jun 2013 08:24:11 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r57FOAi7023721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 7 Jun 2013 15:24:10 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r57FO9u0016798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jun 2013 15:24:09 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r57FO9UW016887; Fri, 7 Jun 2013 15:24:09 GMT
Received: from [192.168.2.2] (/24.91.51.58) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 07 Jun 2013 08:24:08 -0700
Message-ID: <51B1FB0F.40601@oracle.com>
Date: Fri, 07 Jun 2013 11:23:59 -0400
From: prateek mishra <prateek.mishra@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: jose@ietf.org
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com>
In-Reply-To: <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070701070103030609000108"
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: rlb@ipv.sx
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 15:24:17 -0000

This is a multi-part message in MIME format.
--------------070701070103030609000108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+1 to Richard's comments.

I havent been able to review the latest drafts (we will provide comments 
from an internal review soon)
but I am very concerned about the embedding of complex application 
semantics into headers defined by a signature/enryption specification.

- prateek
> Of course, motherhood, apple pie, etc. :)
>
> The question is what we're trying to help developers do.  The 
> developers I talk to want a simple tool to do crypto stuff, full stop. 
>  They don't want semantic validation, critical fields, etc.
>
> The adoption you're pointing to is not really relevant to the process 
> here.  The deployed implementations you're talking about are all in a 
> limited space, covering one use case.  And the current solution comes 
> with baggage for that use case that adds complexity for everyone else. 
>  If you wanted to address that one use case, you should have chartered 
> for that, not general signing and encryption.
>
> Nonetheless, on timing, I agree that I'm getting a little bored with 
> fighting over this :)  I'm working on a review of -11 that tries to 
> package up all the remaining comments such that they can get resolved 
> and we can move on with life.
>
> --Richard
>
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones 
> <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> wrote:
>
>     Excellent question, Richard, because it gets to the heart of why
>     the JOSE specs are already highly successful and widely adopted.
>
>     - We are building useful tools that solve real problems for
>     developers.
>
>     - We are practically demonstrating the value of rough consensus
>     and running code.
>
>     - We are making simple things simple.
>
>     - We are making complex things possible, when necessary (but not
>     at the expense of keeping simple things simple).
>
>     - We are developing specs with an explicit goal of enabling
>     ubiquitous adoption.
>
>     - We are developing specs guided by practical engineering
>     tradeoffs to enable commonly useful functionality in a
>     straightforward manner.
>
>     The level of adoption, with dozens of deployed implementations, is
>     compelling evidence that we've already achieved the goals above. 
>     It's time to "ship it", as making the JOSE specs actual standards
>     will only increase their adoption and value to the industry.
>
>     That's what we're doing here.
>
>     -- Mike
>
>     P.S. I would be careful reasoning from the premise of "The perfect
>     protocol is one from which nothing can be removed". By that logic,
>     the perfect specification is the null specification, which leaves
>     all possibilities open, and solves no actual problems. ;-)
>
>     *From:*jose-bounces@ietf.org <mailto:jose-bounces@ietf.org>
>     [mailto:jose-bounces@ietf.org <mailto:jose-bounces@ietf.org>] *On
>     Behalf Of *Richard Barnes
>     *Sent:* Thursday, June 06, 2013 2:44 PM
>     *To:* jose@ietf.org <mailto:jose@ietf.org>
>     *Subject:* [jose] What are we doing here?
>
>     The conversation about "typ" has brought us back to a familiar
>     question for this working group -- what are we trying to do here?
>
>     The current document is ambiguous on this topic.  On the one hand,
>     it mostly covers the crypto bases, with things like "alg" and
>     "enc".  On the other hand, it mixes in application design concepts
>     like "typ" and "crit".  The result is a spec that's ambiguous in
>     purpose and complex.  If I'm building an application with this,
>     how do I decide what goes in the "crit" field, or what values to
>     use for "typ"?
>
>     The charter for this working group is not ambiguous on this topic.
>      This group is chartered to do signing and encryption.  The JOSE
>     formats should carry the parameters needed to perform those
>     operations.  Anything else is extraneous, and in the spirit of
>     "The perfect protocol is one from which nothing can be removed",
>     should be removed.
>
>     Now, I'm not going to be a hard-liner on this.  I won't complain
>     about "zip" and "cty", since they are clearly defined and have
>     clear use cases.  But "crit" and "typ" are so ambiguous and so
>     little supported by use cases*, that they really should go.
>
>     </rant>
>
>     --Richard
>
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------070701070103030609000108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    +1 to Richard's comments. <br>
    <br>
    I havent been able to review the latest drafts (we will provide
    comments from an internal review soon)<br>
    but I am very concerned about the embedding of complex application
    semantics into headers defined by a signature/enryption
    specification.<br>
    <br>
    - prateek<br>
    <blockquote
cite="mid:CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com"
      type="cite">
      <div dir="ltr">Of course, motherhood, apple pie, etc. :)
        <div><br>
        </div>
        <div>The question is what we're trying to help developers do.
          &nbsp;The developers I talk to want a simple tool to do crypto
          stuff, full stop. &nbsp;They don't want semantic validation,
          critical fields, etc. &nbsp;</div>
        <div><br>
        </div>
        <div>The adoption you're pointing to is not really relevant to
          the process here. &nbsp;The deployed implementations you're talking
          about are all in a limited space, covering one use case. &nbsp;And
          the current solution comes with baggage for that use case that
          adds complexity for everyone else. &nbsp;If you wanted to address
          that one use case, you should have chartered for that, not
          general signing and encryption.</div>
        <div><br>
        </div>
        <div>Nonetheless, on timing, I agree that I'm getting a little
          bored with fighting over this :) &nbsp;I'm working on a review of
          -11 that tries to package up all the remaining comments such
          that they can get resolved and we can move on with life.</div>
        <div><br>
        </div>
        <div>--Richard</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Fri, Jun 7, 2013 at 1:18 AM, Mike
          Jones <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div link="blue" vlink="purple" lang="EN-US">
              <div>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent
                    question, Richard, because it gets to the heart of
                    why the JOSE specs are already highly successful and
                    widely adopted.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are building useful tools that solve real
                    problems for developers.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are practically demonstrating the value of
                    rough consensus and running code.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are making simple things simple.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are making complex things possible, when
                    necessary (but not at the expense of keeping simple
                    things simple).</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are developing specs with an explicit goal of
                    enabling ubiquitous adoption.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;
                    - We are developing specs guided by practical
                    engineering tradeoffs to enable commonly useful
                    functionality in a straightforward manner.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The
                    level of adoption, with dozens of deployed
                    implementations, is compelling evidence that we&#8217;ve
                    already achieved the goals above.&nbsp; It&#8217;s time to
                    &#8220;ship it&#8221;, as making the JOSE specs actual standards
                    will only increase their adoption and value to the
                    industry.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">That&#8217;s
                    what we&#8217;re doing here.</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                    -- Mike</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.&nbsp;
                    I would be careful reasoning from the premise of &#8220;</span>The
                  perfect protocol is one from which nothing can be
                  removed<span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&#8221;.&nbsp;

                    By that logic, the perfect specification is the null
                    specification, which leaves all possibilities open,
                    and solves no actual problems. ;-)</span></p>
                <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                    <a moz-do-not-send="true"
                      href="mailto:jose-bounces@ietf.org"
                      target="_blank">jose-bounces@ietf.org</a> [mailto:<a
                      moz-do-not-send="true"
                      href="mailto:jose-bounces@ietf.org"
                      target="_blank">jose-bounces@ietf.org</a>]
                    <b>On Behalf Of </b>Richard Barnes<br>
                    <b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
                    <b>To:</b> <a moz-do-not-send="true"
                      href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a><br>
                    <b>Subject:</b> [jose] What are we doing here?</span></p>
                <div>
                  <div class="h5">
                    <p class="MsoNormal">&nbsp;</p>
                    <div>
                      <p class="MsoNormal">The conversation about "typ"
                        has brought us back to a familiar question for
                        this working group -- what are we trying to do
                        here?</p>
                      <div>
                        <p class="MsoNormal">&nbsp;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">The current document is
                          ambiguous on this topic. &nbsp;On the one hand, it
                          mostly covers the crypto bases, with things
                          like "alg" and "enc". &nbsp;On the other hand, it
                          mixes in application design concepts like
                          "typ" and "crit". &nbsp;The result is a spec that's
                          ambiguous in purpose and complex. &nbsp;If I'm
                          building an application with this, how do I
                          decide what goes in the "crit" field, or what
                          values to use for "typ"? &nbsp; &nbsp;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">The charter for this
                          working group is not ambiguous on this topic.
                          &nbsp;This group is chartered to do signing and
                          encryption. &nbsp;The JOSE formats should carry the
                          parameters needed to perform those operations.
                          &nbsp;Anything else is extraneous, and in the
                          spirit of "The perfect protocol is one from
                          which nothing can be removed", should be
                          removed.</p>
                      </div>
                      <div>
                        <p class="MsoNormal">&nbsp;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">Now, I'm not going to be a
                          hard-liner on this. &nbsp;I won't complain about
                          "zip" and "cty", since they are clearly
                          defined and have clear use cases. &nbsp;But "crit"
                          and "typ" are so ambiguous and so little
                          supported by use cases*, that they really
                          should go.</p>
                      </div>
                      <div>
                        <p class="MsoNormal">&nbsp;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">&lt;/rant&gt;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">&nbsp;</p>
                      </div>
                      <div>
                        <p class="MsoNormal">--Richard</p>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070701070103030609000108--

From rlb@ipv.sx  Fri Jun  7 08:41:13 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2D421F9732 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxFz4eWughzY for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 08:41:09 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id C96D421F9711 for <jose@ietf.org>; Fri,  7 Jun 2013 08:41:08 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id va7so6836789obc.13 for <jose@ietf.org>; Fri, 07 Jun 2013 08:41:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=JDZj6nfXuNgFM0Hh1kfrnlVQOZNyKTo+h8u7tfzKPZE=; b=aEgk5r87uvGZ24vv1/537uAajz9Y579omvupcqa5hW6jAUMRloFJcthXxM1KeBMG7A I56uM1WLyv1cztOEzWq/dmmwMuIwVMNppxNSvJhcChg5c3uRxqWBqC7oIdmuU1lotu1E zbPWCba8ZJ/mrUKDeDQp4BtjyQ17fbALiD/ectwq7kmseBX+iR6UQzfEJAy8Lqlony21 bdmaP7SHG6TtofbJCyhnCS/Jm3GHXUiWzOn3Pd3DrlWkeLIxVwvNgzf3Ke9QjYslAKlt s15XWcafGkF9+hFJ6i0REkUkwV40XX4uUrGNnO9+DZNt+ZzOSEt1iY9WJIo+lPpNAyog 34Uw==
MIME-Version: 1.0
X-Received: by 10.182.237.77 with SMTP id va13mr22145815obc.65.1370619667925;  Fri, 07 Jun 2013 08:41:07 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Fri, 7 Jun 2013 08:41:07 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436780A35A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTW-ho36gYGZdYJOOem96tj4RRmubxS9cd4k=WbQc3itw@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780A35A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 7 Jun 2013 11:41:07 -0400
Message-ID: <CAL02cgRm+j3dO3QYyH+rJhu2upRfzM456voo6Etm5DavQ-QHug@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cdcc6de20204de92424b
X-Gm-Message-State: ALoCoQls6x126ySGG7Ex2wuqiXJYtoygLlPUGafFGhyiX+GA9Y59Cph/Cia89CYPffBVj3n2/gYU
Cc: "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Use case for "typ" (Re: What are we doing here?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 15:41:13 -0000

--e89a8ff1cdcc6de20204de92424b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 7, 2013 at 11:08 AM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  =93typ=94 is there to dynamically answer the question =93What is this da=
ta
> structure?=94 for applications.  It=92s needed in cases that that=92s pot=
entially
> ambiguous.  If for instance, a token might be either a Facebook signed
> request or a JWT, the =93typ=94 value could be used to distinguish betwee=
n them.
>

A more specific use case would be helpful.  See also the below notes on
"cty" distinction.


> You=92re wrong that =93cty=94 could be used for that, because =93cty=94 a=
nswers the
> question =93What is the data structure that is the payload of this JOSE
> message?=94 =96 not =93What is this data structure?=94.  The distinction =
is
> particularly important because as of -09 we decided to allow additional
> header parameters to be added by applications that must be ignored if not
> understood.  So =93cty=94 doesn=92t provide a comprehensive answer to the
> question =93What is this data structure?=94.
>

"cty" tells you what the object is at the level of "It's this thing,
wrapped in a JWE/JWS".  In your Facebook vs. JWT example, in the one case,
the content would be "application/facebook-request", in the other
"application/jwt-claims" (using fictive MIME types).  So "cty" is
sufficient to distinguish between the two.

The only way this is unclear is if two applications use the same "cty" and
put different things in the header.  But they shouldn't do that, because
it's bad layering -- JOSE Is Just Crypto.


I know of no OAuth Mechanism for providing a general-case answer to the
> question =93What is this data structure?=94 (other than the use of =93typ=
=94 J).
> What specifically were you thinking of there?
>

Maybe I'm confused, but I was envisioning something like what's in RFC 6749=
:
     Authorization: JWT <jwt-object>
<http://tools.ietf.org/html/rfc6749#section-7.1>

Or this in draft-ietf-oauth-jwt-bearer:
     POST /token.oauth2 HTTP/1.1
     Host: authz.example.net
     Content-Type: application/x-www-form-urlencoded

     grant_type=3Durn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Ajwt-bearer
     &assertion=3DeyJhbGciOiJFUzI1NiJ9.
     eyJpc3Mi[...omitted for brevity...].
     J9l-ZhwP[...omitted for brevity...]
<http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-05#section-4>

Those are in addition to the "cty" disambiguation above.  I'm not seeing a
use case here.

--Richard


So JWT needs it, and is a valid application.  John Bradley has also
> described a number of other potential uses.  Again, I haven=92t heard any=
one
> say that Jim=92s original logic for why =93typ=94 is the way it is today =
was
> wrong =96 only that more clarification is needed, which we=92ll do.
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Friday, June 07, 2013 7:54 AM
> *To:* Mike Jones
> *Cc:* jose@ietf.org; Dick Hardt
> *Subject:* [jose] Use case for "typ" (Re: What are we doing here?)****
>
> ** **
>
> [Popping out to a separate thread, since we're into specifics here]****
>
> ** **
>
> Mike:
>
> I asked earlier for an example of an application that that needs "typ",
> noting that JWT doesn't count because it can provide that via two other
> channels ("cty" and OAuth).  Could you provide one?  ****
>
> ** **
>
> Thanks,****
>
> --Richard****
>
> ** **
>
> On Fri, Jun 7, 2013 at 10:48 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> I agree that we should provide some additional clarification on the
> intended purpose for the =93typ=94 and =93cty=94 parameters.  We just did=
 provide
> substantial additional clarification for =93crit=94 in -11, based on the
> working group decisions at the interim meeting.  Are there other specific
> things that you=92d suggest that we clarify, Dick?****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Dick Hardt
> *Sent:* Friday, June 07, 2013 7:33 AM
> *To:* Richard Barnes
> *Cc:* Mike Jones; jose@ietf.org
> *Subject:* Re: [jose] What are we doing here?****
>
>  ****
>
> MIke: I don't find your response very useful for understanding the
> question Richard proposed. I find the spec confusing as to what I am
> supposed to do when as an implementer. It seems that it is clear to all t=
he
> people associated with OpenID Connect, but without that context, it is
> confusing, and frankly, some of the parameters seem like hacks to me.
> Perhaps some additional clarification on what the parameters are intended
> for would assist?****
>
>  ****
>
> -- Dick****
>
>  ****
>
> On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx> wrote:****
>
> Of course, motherhood, apple pie, etc. :)****
>
>  ****
>
> The question is what we're trying to help developers do.  The developers =
I
> talk to want a simple tool to do crypto stuff, full stop.  They don't wan=
t
> semantic validation, critical fields, etc.  ****
>
>  ****
>
> The adoption you're pointing to is not really relevant to the process
> here.  The deployed implementations you're talking about are all in a
> limited space, covering one use case.  And the current solution comes wit=
h
> baggage for that use case that adds complexity for everyone else.  If you
> wanted to address that one use case, you should have chartered for that,
> not general signing and encryption.****
>
>  ****
>
> Nonetheless, on timing, I agree that I'm getting a little bored with
> fighting over this :)  I'm working on a review of -11 that tries to packa=
ge
> up all the remaining comments such that they can get resolved and we can
> move on with life.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> Excellent question, Richard, because it gets to the heart of why the JOSE
> specs are already highly successful and widely adopted.****
>
>  ****
>
>   - We are building useful tools that solve real problems for developers.=
*
> ***
>
>   - We are practically demonstrating the value of rough consensus and
> running code.****
>
>   - We are making simple things simple.****
>
>   - We are making complex things possible, when necessary (but not at the
> expense of keeping simple things simple).****
>
>   - We are developing specs with an explicit goal of enabling ubiquitous
> adoption.****
>
>   - We are developing specs guided by practical engineering tradeoffs to
> enable commonly useful functionality in a straightforward manner.****
>
>  ****
>
> The level of adoption, with dozens of deployed implementations, is
> compelling evidence that we=92ve already achieved the goals above.  It=92=
s time
> to =93ship it=94, as making the JOSE specs actual standards will only inc=
rease
> their adoption and value to the industry.****
>
>  ****
>
> That=92s what we=92re doing here.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> P.S.  I would be careful reasoning from the premise of =93The perfect
> protocol is one from which nothing can be removed=94.  By that logic, the
> perfect specification is the null specification, which leaves all
> possibilities open, and solves no actual problems. ;-)****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 06, 2013 2:44 PM
> *To:* jose@ietf.org
> *Subject:* [jose] What are we doing here?****
>
>  ****
>
> The conversation about "typ" has brought us back to a familiar question
> for this working group -- what are we trying to do here?****
>
>  ****
>
> The current document is ambiguous on this topic.  On the one hand, it
> mostly covers the crypto bases, with things like "alg" and "enc".  On the
> other hand, it mixes in application design concepts like "typ" and "crit"=
.
>  The result is a spec that's ambiguous in purpose and complex.  If I'm
> building an application with this, how do I decide what goes in the "crit=
"
> field, or what values to use for "typ"?    ****
>
> The charter for this working group is not ambiguous on this topic.  This
> group is chartered to do signing and encryption.  The JOSE formats should
> carry the parameters needed to perform those operations.  Anything else i=
s
> extraneous, and in the spirit of "The perfect protocol is one from which
> nothing can be removed", should be removed.****
>
>  ****
>
> Now, I'm not going to be a hard-liner on this.  I won't complain about
> "zip" and "cty", since they are clearly defined and have clear use cases.
>  But "crit" and "typ" are so ambiguous and so little supported by use
> cases*, that they really should go.****
>
>  ****
>
> </rant>****
>
>  ****
>
> --Richard****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
>  ****
>
> --
> -- Dick ****
>
> ** **
>

--e89a8ff1cdcc6de20204de92424b
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Jun 7, 2013 at 11:08 AM, Mike Jones <span dir=3D"l=
tr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Mi=
chael.Jones@microsoft.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=93typ=94 is there to dynamically answer the question=
 =93What is this data structure?=94 for applications.=A0 It=92s needed in c=
ases that that=92s potentially ambiguous.=A0
 If for instance, a token might be either a Facebook signed request or a JW=
T, the =93typ=94 value could be used to distinguish between them.</span></p=
></div></div></blockquote><div><br></div><div>A more specific use case woul=
d be helpful. =A0See also the below notes on &quot;cty&quot; distinction.</=
div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div>

<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">You=92re wrong that =93cty=94 could be used for that,=
 because =93cty=94 answers the question =93What is the data structure that =
is the payload of this JOSE message?=94 =96
 not =93What is this data structure?=94.=A0 The distinction is particularly=
 important because as of -09 we decided to allow additional header paramete=
rs to be added by applications that must be ignored if not understood.=A0 S=
o =93cty=94 doesn=92t provide a comprehensive
 answer to the question =93What is this data structure?=94.</span></p></div=
></div></blockquote><div><br></div><div>&quot;cty&quot; tells you what the =
object is at the level of &quot;It&#39;s this thing, wrapped in a JWE/JWS&q=
uot;. =A0In your Facebook vs. JWT example, in the one case, the content wou=
ld be &quot;application/facebook-request&quot;, in the other &quot;applicat=
ion/jwt-claims&quot; (using fictive MIME types). =A0So &quot;cty&quot; is s=
ufficient to distinguish between the two.</div>
<div><br></div><div>The only way this is unclear is if two applications use=
 the same &quot;cty&quot; and put different things in the header. =A0But th=
ey shouldn&#39;t do that, because it&#39;s bad layering -- JOSE Is Just Cry=
pto.=A0</div>
<div>=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,2=
04);border-left-style:solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"b=
lue" vlink=3D"purple">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">I know of no OAuth Mechanism for providing a general-=
case answer to the question =93What is this data structure?=94 (other than =
the use of =93typ=94
</span><span style=3D"font-size:11pt;font-family:Wingdings;color:rgb(31,73,=
125)">J</span><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">).=A0 What specifically were you thinking of there?</=
span></p>
</div></div></blockquote><div><br></div><div>Maybe I&#39;m confused, but I =
was envisioning something like what&#39;s in RFC 6749:</div><div>=A0 =A0 =
=A0Authorization: JWT &lt;jwt-object&gt;</div><div>&lt;<a href=3D"http://to=
ols.ietf.org/html/rfc6749#section-7.1">http://tools.ietf.org/html/rfc6749#s=
ection-7.1</a>&gt;</div>
<div>=A0</div><div>Or this in draft-ietf-oauth-jwt-bearer:</div><div><div>=
=A0 =A0 =A0POST /token.oauth2 HTTP/1.1</div><div>=A0 =A0 =A0Host: <a href=
=3D"http://authz.example.net">authz.example.net</a></div><div>=A0 =A0 =A0Co=
ntent-Type: application/x-www-form-urlencoded</div>
<div><br></div><div>=A0 =A0 =A0grant_type=3Durn%3Aietf%3Aparams%3Aoauth%3Ag=
rant-type%3Ajwt-bearer</div><div>=A0 =A0 =A0&amp;assertion=3DeyJhbGciOiJFUz=
I1NiJ9.</div><div>=A0 =A0 =A0eyJpc3Mi[...omitted for brevity...].</div><div=
>=A0 =A0 =A0J9l-ZhwP[...omitted for brevity...]</div>
</div><div>&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-oauth-jwt-b=
earer-05#section-4">http://tools.ietf.org/html/draft-ietf-oauth-jwt-bearer-=
05#section-4</a>&gt;</div><div><br></div><div>Those are in addition to the =
&quot;cty&quot; disambiguation above. =A0I&#39;m not seeing a use case here=
. =A0</div>
<div><br></div><div>--Richard</div><div><br></div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-lef=
t:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D""><span=
 style=3D"color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11p=
t">So JWT needs it, and is a valid application.=A0 John Bradley has also de=
scribed a number of other potential uses.=A0 Again, I haven=92t heard anyon=
e say that Jim=92s
 original logic for why =93typ=94 is the way it is today was wrong =96 only=
 that more clarification is needed, which we=92ll do.</span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></=
span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"=
_blank">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Friday, June 07, 2013 7:54 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>; Dick Hardt<br>
<b>Subject:</b> [jose] Use case for &quot;typ&quot; (Re: What are we doing =
here?)<u></u><u></u></span></p><div><div class=3D"h5">
<p class=3D""><u></u>=A0<u></u></p>
<div>
<p class=3D"">[Popping out to a separate thread, since we&#39;re into speci=
fics here]<u></u><u></u></p>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">Mike:<br>
<br>
I asked earlier for an example of an application that that needs &quot;typ&=
quot;, noting that JWT doesn&#39;t count because it can provide that via tw=
o other channels (&quot;cty&quot; and OAuth). =A0Could you provide one? =A0=
<u></u><u></u></p>

</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">Thanks,<u></u><u></u></p>
</div>
<div>
<p class=3D"">--Richard<u></u><u></u></p>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"">On Fri, Jun 7, 2013 at 10:48 AM, Mike Jones &lt;<a href=3D"ma=
ilto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft=
.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">I agree that we should provide some additional clarif=
ication on the intended purpose for the =93typ=94
 and =93cty=94 parameters.=A0 We just did provide substantial additional cl=
arification for =93crit=94 in -11, based on the working group decisions at =
the interim meeting.=A0 Are there other specific things that you=92d sugges=
t that we clarify, Dick?</span><u></u><u></u></p>

<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</span><u></u><u><=
/u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] What are we doing here?</span><u></u><u></u></p>
<div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
<div>
<p class=3D"">MIke: I don&#39;t find your response very useful for understa=
nding the question Richard proposed. I find the spec confusing as to what I=
 am supposed to do when as an implementer. It
 seems that it is clear to all the people associated with OpenID Connect, b=
ut without that context, it is confusing, and frankly, some of the paramete=
rs seem like hacks to me. Perhaps some additional clarification on what the=
 parameters are intended for would
 assist?<u></u><u></u></p>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">-- Dick<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt">=A0<u></u><u></u></p>
<div>
<p class=3D"">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<a href=3D=
"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u></u><u></=
u></p>
<div>
<p class=3D"">Of course, motherhood, apple pie, etc. :)<u></u><u></u></p>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">The question is what we&#39;re trying to help developers do. =
=A0The developers I talk to want a simple tool to do crypto stuff, full sto=
p. =A0They don&#39;t want semantic validation, critical
 fields, etc. =A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">The adoption you&#39;re pointing to is not really relevant to=
 the process here. =A0The deployed implementations you&#39;re talking about=
 are all in a limited space, covering one use case.
 =A0And the current solution comes with baggage for that use case that adds=
 complexity for everyone else. =A0If you wanted to address that one use cas=
e, you should have chartered for that, not general signing and encryption.<=
u></u><u></u></p>

</div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">Nonetheless, on timing, I agree that I&#39;m getting a little=
 bored with fighting over this :) =A0I&#39;m working on a review of -11 tha=
t tries to package up all the remaining comments such
 that they can get resolved and we can move on with life.<u></u><u></u></p>
</div>
<div>
<p class=3D""><span style=3D"color:rgb(136,136,136)">=A0</span><u></u><u></=
u></p>
</div>
<div>
<p class=3D""><span style=3D"color:rgb(136,136,136)">--Richard</span><u></u=
><u></u></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt">=A0<u></u><u></u></p>
<div>
<p class=3D"">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a href=3D"mai=
lto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">Excellent question, Richard, because it gets to the h=
eart of why the JOSE specs are already highly
 successful and widely adopted.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are building useful tools that solve real pr=
oblems for developers.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are practically demonstrating the value of r=
ough consensus and running code.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are making simple things simple.</span><u></=
u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are making complex things possible, when nec=
essary (but not at the expense of keeping simple
 things simple).</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are developing specs with an explicit goal o=
f enabling ubiquitous adoption.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0 - We are developing specs guided by practical eng=
ineering tradeoffs to enable commonly useful functionality
 in a straightforward manner.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">The level of adoption, with dozens of deployed implem=
entations, is compelling evidence that we=92ve
 already achieved the goals above.=A0 It=92s time to =93ship it=94, as maki=
ng the JOSE specs actual standards will only increase their adoption and va=
lue to the industry.</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">That=92s what we=92re doing here.</span><u></u><u></u=
></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</span><u></u><u=
></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">P.S.=A0 I would be careful reasoning from the premise=
 of =93</span>The perfect protocol is one from which
 nothing can be removed<span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">=94.=A0 By that logic, the perfect specifica=
tion is the null specification, which leaves all possibilities open, and so=
lves no actual problems. ;-)</span><u></u><u></u></p>

<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0</span><u></u><u></u></p>
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><u></u><u></u></p>
<div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
<div>
<p class=3D"">The conversation about &quot;typ&quot; has brought us back to=
 a familiar question for this working group -- what are we trying to do her=
e?<u></u><u></u></p>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">The current document is ambiguous on this topic. =A0On the on=
e hand, it mostly covers the crypto bases, with things like &quot;alg&quot;=
 and &quot;enc&quot;. =A0On the other hand, it mixes in application
 design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result i=
s a spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m buildin=
g an application with this, how do I decide what goes in the &quot;crit&quo=
t; field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u><=
/p>

</div>
<div>
<p class=3D"">The charter for this working group is not ambiguous on this t=
opic. =A0This group is chartered to do signing and encryption. =A0The JOSE =
formats should carry the parameters needed to
 perform those operations. =A0Anything else is extraneous, and in the spiri=
t of &quot;The perfect protocol is one from which nothing can be removed&qu=
ot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">Now, I&#39;m not going to be a hard-liner on this. =A0I won&#=
39;t complain about &quot;zip&quot; and &quot;cty&quot;, since they are cle=
arly defined and have clear use cases. =A0But &quot;crit&quot; and &quot;ty=
p&quot; are so ambiguous
 and so little supported by use cases*, that they really should go.<u></u><=
u></u></p>
</div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"">--Richard<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"" style=3D"margin-bottom:12pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D""><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"">=A0<u></u><u></u></p>
</div>
<p class=3D"">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div></div>

--e89a8ff1cdcc6de20204de92424b--

From dick.hardt@gmail.com  Fri Jun  7 10:06:44 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D62E21F9600 for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 10:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.125
X-Spam-Level: 
X-Spam-Status: No, score=-1.125 tagged_above=-999 required=5 tests=[AWL=1.474,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIrY9Y4ww37p for <jose@ietfa.amsl.com>; Fri,  7 Jun 2013 10:06:43 -0700 (PDT)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5F98321F93D2 for <jose@ietf.org>; Fri,  7 Jun 2013 10:06:42 -0700 (PDT)
Received: by mail-bk0-f51.google.com with SMTP id ji1so1595676bkc.24 for <jose@ietf.org>; Fri, 07 Jun 2013 10:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qxXxW3mHxKMeHmco0JT+HOhU2Aw4c5+456A2sjC2lTs=; b=Y9thScrFuA/kCX4r8EiLApp42rqMEmnEp8L4PTLKdQI44TMpDeBG0TE6jqmTIU3e4Z rrougorrZ5vuYE8nFhme2J5/K07d+Fr4h3LRDEgTwV8b7ESzbBQWkMHs3XUCOSepEpTx +g4gm2NDzJKRPwo59tJ1/rnRAxcHvVaAC51TsAFGeF/BfMRX/0bwPfY2pu8kv25tPX8d PLf3aovKXeXbUO1t2diqXqWVWulNmvNSSHktKPMxWz4iC3Nd1ghDSHHhzH8A8u5eZChq 4yCODLco8aY3o47keyxqMQsjESD7xp7P/G2WMOJG8wkbd1D6WE5XTo9F0EYs+mvMhb8o 6bew==
MIME-Version: 1.0
X-Received: by 10.204.70.203 with SMTP id e11mr12866307bkj.16.1370624801143; Fri, 07 Jun 2013 10:06:41 -0700 (PDT)
Received: by 10.204.168.12 with HTTP; Fri, 7 Jun 2013 10:06:41 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436780A27F@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com> <CAD9ie-uaxx0Yf6sW1-rUYEmD-CcNkJNC0cQ0Bypfs375fYpGYg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780A27F@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 7 Jun 2013 10:06:41 -0700
Message-ID: <CAD9ie-tuZqVr7Vq+Gt1j4KVKbH-2RZyW4Grp26hbW30zeyS-fg@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=047d7b87450e64c00904de93742b
Cc: Richard Barnes <rlb@ipv.sx>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 07 Jun 2013 17:06:44 -0000

--047d7b87450e64c00904de93742b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Mike,

Currently I find "typ" and "cty" confusing. Once I understand them, I may
be confused with other aspects. :)

For example, in:

https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11

What "typ" is supposed to be is confusing.

In 3.1, it is defined as "typ":"JWT"

In 4.1.8, it is "typ":"JWS" or "typ":"JWS+JSON"

Which one is it?
When would  you use "cty"?

-- Dick


On Fri, Jun 7, 2013 at 7:48 AM, Mike Jones <Michael.Jones@microsoft.com>wro=
te:

>  I agree that we should provide some additional clarification on the
> intended purpose for the =93typ=94 and =93cty=94 parameters.  We just did=
 provide
> substantial additional clarification for =93crit=94 in -11, based on the
> working group decisions at the interim meeting.  Are there other specific
> things that you=92d suggest that we clarify, Dick?****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Dick Hardt
> *Sent:* Friday, June 07, 2013 7:33 AM
> *To:* Richard Barnes
> *Cc:* Mike Jones; jose@ietf.org
> *Subject:* Re: [jose] What are we doing here?****
>
> ** **
>
> MIke: I don't find your response very useful for understanding the
> question Richard proposed. I find the spec confusing as to what I am
> supposed to do when as an implementer. It seems that it is clear to all t=
he
> people associated with OpenID Connect, but without that context, it is
> confusing, and frankly, some of the parameters seem like hacks to me.
> Perhaps some additional clarification on what the parameters are intended
> for would assist?****
>
> ** **
>
> -- Dick****
>
> ** **
>
> On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx> wrote:****
>
> Of course, motherhood, apple pie, etc. :)****
>
> ** **
>
> The question is what we're trying to help developers do.  The developers =
I
> talk to want a simple tool to do crypto stuff, full stop.  They don't wan=
t
> semantic validation, critical fields, etc.  ****
>
> ** **
>
> The adoption you're pointing to is not really relevant to the process
> here.  The deployed implementations you're talking about are all in a
> limited space, covering one use case.  And the current solution comes wit=
h
> baggage for that use case that adds complexity for everyone else.  If you
> wanted to address that one use case, you should have chartered for that,
> not general signing and encryption.****
>
> ** **
>
> Nonetheless, on timing, I agree that I'm getting a little bored with
> fighting over this :)  I'm working on a review of -11 that tries to packa=
ge
> up all the remaining comments such that they can get resolved and we can
> move on with life.****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> Excellent question, Richard, because it gets to the heart of why the JOSE
> specs are already highly successful and widely adopted.****
>
>  ****
>
>   - We are building useful tools that solve real problems for developers.=
*
> ***
>
>   - We are practically demonstrating the value of rough consensus and
> running code.****
>
>   - We are making simple things simple.****
>
>   - We are making complex things possible, when necessary (but not at the
> expense of keeping simple things simple).****
>
>   - We are developing specs with an explicit goal of enabling ubiquitous
> adoption.****
>
>   - We are developing specs guided by practical engineering tradeoffs to
> enable commonly useful functionality in a straightforward manner.****
>
>  ****
>
> The level of adoption, with dozens of deployed implementations, is
> compelling evidence that we=92ve already achieved the goals above.  It=92=
s time
> to =93ship it=94, as making the JOSE specs actual standards will only inc=
rease
> their adoption and value to the industry.****
>
>  ****
>
> That=92s what we=92re doing here.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> P.S.  I would be careful reasoning from the premise of =93The perfect
> protocol is one from which nothing can be removed=94.  By that logic, the
> perfect specification is the null specification, which leaves all
> possibilities open, and solves no actual problems. ;-)****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 06, 2013 2:44 PM
> *To:* jose@ietf.org
> *Subject:* [jose] What are we doing here?****
>
>  ****
>
> The conversation about "typ" has brought us back to a familiar question
> for this working group -- what are we trying to do here?****
>
>  ****
>
> The current document is ambiguous on this topic.  On the one hand, it
> mostly covers the crypto bases, with things like "alg" and "enc".  On the
> other hand, it mixes in application design concepts like "typ" and "crit"=
.
>  The result is a spec that's ambiguous in purpose and complex.  If I'm
> building an application with this, how do I decide what goes in the "crit=
"
> field, or what values to use for "typ"?    ****
>
> The charter for this working group is not ambiguous on this topic.  This
> group is chartered to do signing and encryption.  The JOSE formats should
> carry the parameters needed to perform those operations.  Anything else i=
s
> extraneous, and in the spirit of "The perfect protocol is one from which
> nothing can be removed", should be removed.****
>
>  ****
>
> Now, I'm not going to be a hard-liner on this.  I won't complain about
> "zip" and "cty", since they are clearly defined and have clear use cases.
>  But "crit" and "typ" are so ambiguous and so little supported by use
> cases*, that they really should go.****
>
>  ****
>
> </rant>****
>
>  ****
>
> --Richard****
>
> ** **
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
> ** **
>
> --
> -- Dick ****
>



--=20
-- Dick

--047d7b87450e64c00904de93742b
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>Hi Mike,=A0</div><div style><br></div><div styl=
e>Currently I find &quot;typ&quot; and &quot;cty&quot; confusing. Once I un=
derstand them, I may be confused with other aspects. :)</div><div style><br=
>
</div><div style>For example, in:</div><div style><br></div><a href=3D"http=
s://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11">https://tool=
s.ietf.org/html/draft-ietf-jose-json-web-signature-11</a><br><div><br></div=
>
<div style>What &quot;typ&quot; is supposed to be is confusing.</div><div><=
br></div><div style>In 3.1, it is defined as &quot;typ&quot;:&quot;JWT&quot=
;</div><div style><br></div><div style>In 4.1.8, it is &quot;typ&quot;:&quo=
t;JWS&quot; or &quot;typ&quot;:&quot;JWS+JSON&quot;</div>
<div style><br></div><div style>Which one is it?</div><div style>When would=
 =A0you use &quot;cty&quot;?</div><div style><br></div><div style>-- Dick</=
div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Fri, Jun 7, 2013 at 7:48 AM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft=
.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I agree that we should pr=
ovide some additional clarification on the intended purpose for the =93typ=
=94 and =93cty=94 parameters.=A0 We just did provide substantial additional
 clarification for =93crit=94 in -11, based on the working group decisions =
at the interim meeting.=A0 Are there other specific things that you=92d sug=
gest that we clarify, Dick?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] What are we doing here?<u></u><u></u></span></p>=
<div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">MIke: I don&#39;t find your response very useful for=
 understanding the question Richard proposed. I find the spec confusing as =
to what I am supposed to do when as an implementer. It seems that it is cle=
ar to all the people associated with OpenID
 Connect, but without that context, it is confusing, and frankly, some of t=
he parameters seem like hacks to me. Perhaps some additional clarification =
on what the parameters are intended for would assist?<u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<=
a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u>=
</u><u></u></p>
<div>
<p class=3D"MsoNormal">Of course, motherhood, apple pie, etc. :)<u></u><u><=
/u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The question is what we&#39;re trying to help develo=
pers do. =A0The developers I talk to want a simple tool to do crypto stuff,=
 full stop. =A0They don&#39;t want semantic validation, critical fields, et=
c. =A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The adoption you&#39;re pointing to is not really re=
levant to the process here. =A0The deployed implementations you&#39;re talk=
ing about are all in a limited space, covering one use case. =A0And the cur=
rent solution comes with baggage for that use
 case that adds complexity for everyone else. =A0If you wanted to address t=
hat one use case, you should have chartered for that, not general signing a=
nd encryption.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nonetheless, on timing, I agree that I&#39;m getting=
 a little bored with fighting over this :) =A0I&#39;m working on a review o=
f -11 that tries to package up all the remaining comments such that they ca=
n get resolved and we can move on with life.<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><u></u>=A0<u></u></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<u></u><u></u=
></span></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@m=
icrosoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly
 successful and widely adopted.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are building use=
ful tools that solve real problems for developers.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are practically =
demonstrating the value of rough consensus and running code.</span><u></u><=
u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making simpl=
e things simple.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making compl=
ex things possible, when necessary (but not at the expense of keeping simpl=
e
 things simple).</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs with an explicit goal of enabling ubiquitous adoption.</span><u></u><u=
></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs guided by practical engineering tradeoffs to enable commonly useful fu=
nctionality
 in a straightforward manner.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we=92ve
 already achieved the goals above.=A0 It=92s time to =93ship it=94, as maki=
ng the JOSE specs actual standards will only increase their adoption and va=
lue to the industry.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That=92s what we=92re doi=
ng here.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.=A0 I would be carefu=
l reasoning from the premise of =93</span>The perfect protocol is one from =
which
 nothing can be removed<span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=94.=A0 By that logic, th=
e perfect specification is the null specification, which leaves all possibi=
lities open, and solves no actual problems. ;-)</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. =A0=
On the one hand, it mostly covers the crypto bases, with things like &quot;=
alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applicatio=
n
 design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result i=
s a spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m buildin=
g an application with this, how do I decide what goes in the &quot;crit&quo=
t; field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u><=
/p>

</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. =A0This group is chartered to do signing and encryption. =A0=
The JOSE formats should carry the parameters needed to
 perform those operations. =A0Anything else is extraneous, and in the spiri=
t of &quot;The perfect protocol is one from which nothing can be removed&qu=
ot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I&#39;m not going to be a hard-liner on this. =
=A0I won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since th=
ey are clearly defined and have clear use cases. =A0But &quot;crit&quot; an=
d &quot;typ&quot; are so ambiguous
 and so little supported by use cases*, that they really should go.<u></u><=
u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">-- <br>
-- Dick <u></u><u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>-- Dick
</div>

--047d7b87450e64c00904de93742b--

From James.H.Manger@team.telstra.com  Sat Jun  8 06:59:23 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CDC21F99E3 for <jose@ietfa.amsl.com>; Sat,  8 Jun 2013 06:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOL+zkjm53kp for <jose@ietfa.amsl.com>; Sat,  8 Jun 2013 06:59:18 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id DBCD221F963C for <jose@ietf.org>; Sat,  8 Jun 2013 06:59:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,827,1363093200"; d="scan'208";a="140231516"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 08 Jun 2013 23:59:16 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7099"; a="189616256"
Received: from wsmsg3754.srv.dir.telstra.com ([172.49.40.198]) by ipcavi.tcif.telstra.com.au with ESMTP; 08 Jun 2013 23:59:16 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3754.srv.dir.telstra.com ([172.49.40.198]) with mapi; Sat, 8 Jun 2013 23:59:15 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mike Jones <Michael.Jones@microsoft.com>, Richard Barnes <rlb@ipv.sx>
Date: Sat, 8 Jun 2013 23:59:14 +1000
Thread-Topic: [jose] Use case for "typ" (Re:  What are we doing here?)
Thread-Index: AQHOY47x/x9/wIdlAEueYq4QJVTT9pkqWFcQgAF4dnA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B21FF65@WSMSG3153V.srv.dir.telstra.com>
References: <CAL02cgTW-ho36gYGZdYJOOem96tj4RRmubxS9cd4k=WbQc3itw@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780A35A@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436780A35A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Use case for "typ" (Re:  What are we doing here?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 08 Jun 2013 13:59:23 -0000

TWlrZSBzYWlkOg0KPiBTbyBKV1QgbmVlZHMgaXQgWyJ0eXAiXQ0KDQpJdCBpcyBoYXJkIHRvIHVu
ZGVyc3RhbmQgaG93IEpXVCBuZWVkcyAidHlwIiB3aGVuIHRoZSBKV1Qgc3BlYyBzYXlzICJ1c2Ug
b2YgdGhpcyBoZWFkZXIgcGFyYW1ldGVyIGlzIE9QVElPTkFMIj8NCltodHRwOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW9hdXRoLWpzb24td2ViLXRva2VuLTA4I3NlY3Rpb24tNS4x
XQ0KDQpFdmVuIGlmIGEgSldUIGNyZWF0b3IgZGVjaWRlcyB0byBpbmNsdWRlIHRoZSAidHlwIiBo
ZWFkZXIgcGFyYW1ldGVyLCB0aGUgc3BlYyBtZXJlbHkgUkVDT01NRU5EUyB1c2luZyBvbmUgb2Yg
dHdvIHZhbHVlczogIkpXVCIgb3IgInVybjppZXRmOnBhcmFtczpvYXV0aDp0b2tlbi10eXBlOmp3
dCIuIFNvIHRob3NlIG9yIGFueSBvdGhlciB2YWx1ZSBjYW4gYmUgaW5jbHVkZWQuDQoNCkkgY2Fu
J3Qgc2VlIGFueSBoaW50IGFib3V0IGhvdyBhIEpXVCByZWNlaXZlciBpcyBzdXBwb3NlZCB0byBy
ZWFjdCBkaWZmZXJlbnRseSBiYXNlZCBvbjogdGhlIGFic2VuY2Ugb2YgdGhlICJ0eXAiIGhlYWRl
cjsgdGhlIHByZXNlbmNlIG9mIGVpdGhlciBvZiB0aGUgdHdvIHJlY29tbWVuZGVkIHZhbHVlczsg
b3IgdGhlIHByZXNlbmNlIG9mIGFueSBvdGhlciAodW5yZWNvZ25pemVkPykgdmFsdWUuDQoNCi0t
DQpKYW1lcyBNYW5nZXINCg==

From ietf@augustcellars.com  Sun Jun  9 22:40:57 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 834BB21F8B90 for <jose@ietfa.amsl.com>; Sun,  9 Jun 2013 22:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o79iWqHpinA0 for <jose@ietfa.amsl.com>; Sun,  9 Jun 2013 22:40:51 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDD821F91B1 for <jose@ietf.org>; Sun,  9 Jun 2013 22:40:51 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 0D1972C9BC for <jose@ietf.org>; Sun,  9 Jun 2013 22:40:50 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com>	<CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com>	<02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com>	<CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com>	<CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com>	<CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com>	<CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com>	<CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com>	<CABzCy2Cd6LJB63b8REsyW0yjS=2DMBaSw sL-ZUnwG-aCXJ5P-Q@mail .gmail.com>	<CA+k3eCT6Dq2jo6Lx6SEMkNDrLKREJTkzwNxT7ggJHDJtvQVG2A@mail.gmail.com>	<CAL02cgSeurHAEsAtEaEDYAko2Or8dFAOx8QWe-G2e4nss_AX4g@mail.gmail.com>	<CABzCy2DtkqzSSC9Xgy7Gkf0_cxuV7Zn5Jux+NRPiF1LO6PtObw@mail.gmail.com>	<CAL02cgTLpoYuh3iMrYtOKrYR82GqWQyzCnEZh6d0Li8Wxgn8bA@mail.gmail.com>	<CABzCy2DpkF=LD13jZb5B6-4fFxZO37Aj9vh8HRBupRxNd6Mpfg@mail.gmail.com>	<CAD9ie-s1uWSsRDJHb8Z_NPQvuAWWJmYPkTp8g_PbacA5gaqT1w@mail.gmail.com> <CABzCy2Abnv=Cm=nSN2t4b+B=G-rBrza6nrK+VPxqWUcTFpZEYw@mail.gmail.com> <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075A@HE111541.emea1.cds.t-internal.com>
In-Reply-To: <CE8995AB5D178F44A2154F5C9A97CAF40255A5CA075A@HE111541.emea1.cds.t-internal.com>
Date: Sun, 9 Jun 2013 22:39:59 -0700
Message-ID: <05fb01ce659c$f28a8170$d79f8450$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQL+gOaQctokYsIF5NqCLBrsp9OxugIREdBOAZxwGYYA+xTLLwL/DSbtAkjfeb0CNOnLqQJml3CFAT+uwjIC8i/K0QKfBA3BAgAu76wCGMPjBQGo9J74AU9RWkABvcif6gJ7dcuLAdSQGswCQZpOCAKG8a7wAkKXKnkBUbCFRpV3M3rw
Content-Language: en-us
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 05:40:57 -0000

<no hat>

I kept trying to send this message out during the last week, but I have been
doing too much physical activity to be awake at night and produce a coherent
message.

The opinions here are my personal opinions, some of them might be things
that I would also advocate as a chair, but don't assume just because it is
here I would.

I have been looking at the conversation on this topic with slight surprise,
I did not really expect this type of firestorm to occur on a part of the
spec that had been in for quite a while.

Givens:
1.  My general inclination is that things in the document generally stay in
the document, however they do need to be shown to be clearly described and
useful.

2.  My general inclination is that things which can be shown to be useful
for multiple applications can be done in the base document.  That said,
there is nothing that says such a thing could not be defined in one of the
application specs which uses it rather than the base document.

My understanding:

My understanding of what Mike has said is that this field is meant to
clearly present that this is a JSON thing for a specific application.  This
is contrary to the expectation that Richard, Dick and myself had where it
was a description of the "security service" rather than the application.

My problem with this understanding is I am not sure when it is a useful
concept to have.  In order for it to be needed you would need to have two
statements being true:

1.  There is no way to know the application from the current protocol being
exercised and
2.  There is no way to correctly infer the application from the value of the
ctyp field (if present).

Under the current circumstances as I understand the JWT specification,
neither of these criteria would be met.

Nat gave an interesting example of a case where it might be useful, that of
a Time Stamp Provider.  My problem with this is that I don't think of this
as being an application protocol, but as being a different security service.
Thus a timestamp JWS is a specialized version of a normal JWS.  As such, yes
it would make sense to me that the type field could be used to differentiate
between a normal JWS and a timestamp-JWS.  But a timestamp would be, by
definition, completely agnostic about the inner content provided.  The same
could not be said of a JWT application.  It needs to understand the specific
inner content that was provided.  

SideBar:  It is not immediately clear to me that a classic timestamp
provider could be done using the JOSE data structures as it normally
requires that one can produce a timestamp without sharing the content with
the timestamp producer.  There are also interesting discussions on if the
fact that it is a timestamp or other special signature should be signaled in
the signature object or as a key parameter.  However none of this paragraph
is relevant to the current discussion.

I think that I would like to see the following things:

1.  Two clear use cases provided, one for JWT and one for something else
where the typ field as an application indicator would be useful/required.  I
think that such a thing needs to address the two points that I presented
previously.

2.  I don't believe that anyone has addressed the question I raised about
the fact that both the ctyp and typ fields are using the same registry, thus
JWT would mean different things depending on which field it is in.

3.  I had a message dated 5/30/13 where I asked a couple of questions.  This
message was not responded to.

Jim



From ietf@augustcellars.com  Sun Jun  9 22:47:19 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D628921F8B90 for <jose@ietfa.amsl.com>; Sun,  9 Jun 2013 22:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soFLKKKloUBc for <jose@ietfa.amsl.com>; Sun,  9 Jun 2013 22:47:14 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 01C5121F8F38 for <jose@ietf.org>; Sun,  9 Jun 2013 22:47:14 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id D3E0238EF0 for <jose@ietf.org>; Sun,  9 Jun 2013 22:47:13 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Sun, 9 Jun 2013 22:46:22 -0700
Message-ID: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05FD_01CE6563.2A4ADCC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5lnSf72X6a3Ku/SKOo5PcgVR4NIg==
Content-Language: en-us
Subject: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 05:47:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_05FD_01CE6563.2A4ADCC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<no hat>

 

I am trying to figure out if I am missing something.  This is not yet a
formal proposal to actual change the document.

 

I was thinking about proposing that we make a change to the content of the
protected field in the JWS JSON serialization format.  If we encoded this as
a UTF8 string rather than the base64url encoded UTF8 string, then the
content would be smaller.  The computation of the signature would be
unchanged in that it would still be computed over the base64url encoded
string.  I believe that the conversion from the UTF8 string to the base64url
encoded UTF8 string is a deterministic encoding and thus would not generate
any problems from that point.

 

At this point I and trying to figure out if I missed anything that would
preclude this from working.  I am not worried about how hard or easy it
would be to do, just if it is even possible.

 

Jim

 


------=_NextPart_000_05FD_01CE6563.2A4ADCC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>&lt;no =
hat&gt;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I am trying to figure out if I am missing =
something.&nbsp; This is not yet a formal proposal to actual change the =
document.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I was thinking about proposing that we make a change =
to the content of the protected field in the JWS JSON serialization =
format.&nbsp; If we encoded this as a UTF8 string rather than the =
base64url encoded UTF8 string, then the content would be smaller. =
&nbsp;The computation of the signature would be unchanged in that it =
would still be computed over the base64url encoded string.&nbsp; I =
believe that the conversion from the UTF8 string to the base64url =
encoded UTF8 string is a deterministic encoding and thus would not =
generate any problems from that point.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>At this =
point I and trying to figure out if I missed anything that would =
preclude this from working. &nbsp;I am not worried about how hard or =
easy it would be to do, just if it is even possible.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_05FD_01CE6563.2A4ADCC0--


From Michael.Jones@microsoft.com  Mon Jun 10 09:07:57 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6963921F9675 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zo+BQyvTjeO9 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:07:52 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id B876221F90EF for <jose@ietf.org>; Mon, 10 Jun 2013 09:07:52 -0700 (PDT)
Received: from BY2FFO11FD013.protection.gbl (10.1.15.202) by BY2FFO11HUB017.protection.gbl (10.1.14.91) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 10 Jun 2013 16:07:51 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD013.mail.protection.outlook.com (10.1.14.75) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 10 Jun 2013 16:07:51 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Mon, 10 Jun 2013 16:07:35 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "odonoghue@isoc.org" <odonoghue@isoc.org>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] jose wg teleconference announcement - 17 June 2013
Thread-Index: AQHOXax8pLabJNdcTESbphgL8YaBOZkvLeN2
Date: Mon, 10 Jun 2013 16:07:34 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436781B290@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <514C5FC3.20007@isoc.org>,<51A814A9.8060208@isoc.org>
In-Reply-To: <51A814A9.8060208@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436781B290TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(479174002)(377454002)(189002)(30513003)(80022001)(16236675002)(46102001)(79102001)(47446002)(49866001)(69226001)(54316002)(65816001)(56816003)(74706001)(47736001)(63696002)(74366001)(51856001)(74876001)(74662001)(74502001)(77096001)(20776003)(31966008)(47976001)(50986001)(71186001)(56776001)(76796001)(55846006)(512954002)(54356001)(76786001)(59766001)(77982001)(81542001)(53806001)(33656001)(44976003)(4396001)(6806003)(15202345002)(76482001)(81342001)(16406001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB017; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087396016C
Subject: Re: [jose] jose wg teleconference announcement - 17 June 2013
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:07:57 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436781B290TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

What is the call-in information?  Sorry if I missed it.

-- Mike

________________________________
From: Karen O'Donoghue
Sent: 5/30/2013 8:11 PM
To: jose@ietf.org
Subject: [jose] jose wg teleconference announcement - 17 June 2013

The jose working group will have a teleconference on Monday 17 June 2013
at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).

The primary objective of the call will be to ensure the results of the
interim meeting were adequately incorporated and to identify any final
issues on the recently published drafts.

The interim meeting minutes are available at:
http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-int=
erim-2013-jose-1

The updated specifications are available at:
http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11
http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11
http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11

An agenda and webex details will be available next week.

Regards,
Karen

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

--_000_4E1F6AAD24975D4BA5B16804296739436781B290TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">What is the c=
all-in information?&nbsp; Sorry if I missed it.<br>
<br>
-- Mike<br>
<br>
</div>
</div>
<hr>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">From:
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">Karen =
O'Donoghue</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">Sent:
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">5/30/2=
013 8:11 PM</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">To:
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">jose@i=
etf.org</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">Subject:
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">[jose]=
 jose wg teleconference announcement - 17 June 2013</span><br>
<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">The jose working group will have a teleconference =
on Monday 17 June 2013
<br>
at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).<br>
<br>
The primary objective of the call will be to ensure the results of the <br>
interim meeting were adequately incorporated and to identify any final <br>
issues on the recently published drafts.<br>
<br>
The interim meeting minutes are available at:<br>
<a href=3D"http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/=
minutes-interim-2013-jose-1">http://www.ietf.org/proceedings/interim/2013/0=
4/29/jose/minutes/minutes-interim-2013-jose-1</a><br>
<br>
The updated specifications are available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11=
">http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11</a><br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-1=
1">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11</a><br=
>
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11">http=
://tools.ietf.org/html/draft-ietf-jose-json-web-key-11</a><br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-1=
1">http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11</a><br=
>
<br>
An agenda and webex details will be available next week.<br>
<br>
Regards,<br>
Karen<br>
<br>
_______________________________________________<br>
jose mailing list<br>
jose@ietf.org<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a><br>
</div>
</span></font>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436781B290TK5EX14MBXC283r_--

From ve7jtb@ve7jtb.com  Mon Jun 10 09:10:26 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7DB721F9619 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZYx5hVBQniA for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:10:25 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBA821F95D7 for <jose@ietf.org>; Mon, 10 Jun 2013 09:10:25 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a12so3186657wgh.4 for <jose@ietf.org>; Mon, 10 Jun 2013 09:10:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=5ar2rlJzXZZrcIwQD/SK+DFEVKubnyCwYsfrCNJKazs=; b=hBnLc/3cuswbkjtAEg8p36R0oBz6A3mCdc/flIwbXF16+nYj9Niv4RTESsdafKnM+o UZRpivUrOG+6P1+3ZelZAguirCz+oeFkovBfjb7Rjym6y35eXCo/KP+tjTajsNb9OYwX kNKgog+kLHUPMJ1e8CFVN5tSE044KUy/phqWclTkiovaYtg0yeXpWHpfIrbBWtfj2t9Y lgnlml/C3oW4rmsQkCSSRiSkvuGAceMwY7ruENUDk9Oz9C+VnHC0pu7y6lvaqZW77/J7 Gj33Ps5BNMEsNEiX0A4o0LGvVjrco0TcTiZvfZb1DnXi8hzNVB1W+LyFKsqMFC65Plv4 8T7A==
X-Received: by 10.181.13.13 with SMTP id eu13mr5113779wid.26.1370880624406; Mon, 10 Jun 2013 09:10:24 -0700 (PDT)
Received: from [10.147.129.63] ([188.207.110.177]) by mx.google.com with ESMTPSA id fu14sm12420717wic.8.2013.06.10.09.10.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Jun 2013 09:10:23 -0700 (PDT)
References: <514C5FC3.20007@isoc.org> <51A814A9.8060208@isoc.org> <4E1F6AAD24975D4BA5B16804296739436781B290@TK5EX14MBXC283.redmond.corp.microsoft.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781B290@TK5EX14MBXC283.redmond.corp.microsoft.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-5718F173-3201-406B-8824-D46B7FF75C72; protocol="application/pkcs7-signature"
Content-Transfer-Encoding: 7bit
Message-Id: <B01D85DA-D311-44BB-929D-4D57CF4D2700@ve7jtb.com>
X-Mailer: iPhone Mail (10B329)
From: John Bradley <ve7jtb@ve7jtb.com>
Date: Mon, 10 Jun 2013 18:10:17 +0200
To: Mike Jones <Michael.Jones@microsoft.com>
X-Gm-Message-State: ALoCoQkLZTladZEgkc4xXSfHhHloaq4EGtAv3d+9U2XsLoeu38ZrN7dSs/zpwBd0x+MccG3c4PhY
Cc: "jose@ietf.org" <jose@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Subject: Re: [jose] jose wg teleconference announcement - 17 June 2013
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:10:27 -0000

--Apple-Mail-5718F173-3201-406B-8824-D46B7FF75C72
Content-Type: multipart/alternative;
	boundary=Apple-Mail-D9D463B5-44DF-4310-B777-B2E67FAE7F4E
Content-Transfer-Encoding: 7bit


--Apple-Mail-D9D463B5-44DF-4310-B777-B2E67FAE7F4E
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

I am on a train. I will call once I arrive=20

Sent from my iPhone

On 2013-06-10, at 6:07 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:

> What is the call-in information?  Sorry if I missed it.
>=20
> -- Mike
>=20
> From: Karen O'Donoghue
> Sent: 5/30/2013 8:11 PM
> To: jose@ietf.org
> Subject: [jose] jose wg teleconference announcement - 17 June 2013
>=20
> The jose working group will have a teleconference on Monday 17 June 2013=20=

> at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).
>=20
> The primary objective of the call will be to ensure the results of the=20
> interim meeting were adequately incorporated and to identify any final=20
> issues on the recently published drafts.
>=20
> The interim meeting minutes are available at:
> http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-in=
terim-2013-jose-1
>=20
> The updated specifications are available at:
> http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11
>=20
> An agenda and webex details will be available next week.
>=20
> Regards,
> Karen
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

--Apple-Mail-D9D463B5-44DF-4310-B777-B2E67FAE7F4E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I am on a train. I will call once I arrive&nbsp;<br><br>Sent from my iPhone</div><div><br>On 2013-06-10, at 6:07 PM, Mike Jones &lt;<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>


<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">What is the call-in information?&nbsp; Sorry if I missed it.<br>
<br>
-- Mike<br>
<br>
</div>
</div>
<hr>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">From:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Karen O'Donoghue</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Sent:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">5/30/2013 8:11 PM</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">To:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt"><a href="mailto:jose@ietf.org">jose@ietf.org</a></span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Subject:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">[jose] jose wg teleconference announcement - 17 June 2013</span><br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">The jose working group will have a teleconference on Monday 17 June 2013
<br>
at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).<br>
<br>
The primary objective of the call will be to ensure the results of the <br>
interim meeting were adequately incorporated and to identify any final <br>
issues on the recently published drafts.<br>
<br>
The interim meeting minutes are available at:<br>
<a href="http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-interim-2013-jose-1">http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-interim-2013-jose-1</a><br>
<br>
The updated specifications are available at:<br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11</a><br>
<br>
An agenda and webex details will be available next week.<br>
<br>
Regards,<br>
Karen<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href="mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a><br>
</div>
</span></font>


</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>jose mailing list</span><br><span><a href="mailto:jose@ietf.org">jose@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a></span><br></div></blockquote></body></html>
--Apple-Mail-D9D463B5-44DF-4310-B777-B2E67FAE7F4E--

--Apple-Mail-5718F173-3201-406B-8824-D46B7FF75C72
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHuTCCB7Uw
ggadoAMCAQICAh5cMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew
HhcNMTIwMzE4MDQzMjQ4WhcNMTQwMzE5MTEwNzMyWjCBmzEZMBcGA1UEDRMQR3JUTTZMUzdYMzU3
NzhzOTELMAkGA1UEBhMCQ0wxIjAgBgNVBAgTGU1ldHJvcG9saXRhbmEgZGUgU2FudGlhZ28xFjAU
BgNVBAcTDUlzbGEgZGUgTWFpcG8xFTATBgNVBAMTDEpvaG4gQnJhZGxleTEeMBwGCSqGSIb3DQEJ
ARYPamJyYWRsZXlAbWUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAskrlBI93
rBTLOQGSwIT6co6dAw/rwDPrRXl6/F2oc4KDn+QN6CdFeHo08H846VJS9CDjLKvnK9jbxxs4wYqe
nKdPb3jgzt8oc7b9ZXtWkOgsxgMf6dBZ/IPm4lWBpCbSr3seDGDXEpiE2lTZXno7c25OguR4E6Qa
hcpHABZjeEWK65mMH25gmoRf5MY1k3quu5y+FCYCHE2iwU5jzq+mI3HmG59+UMFLx1fjV+zTslRw
26cQDC/uepwjeYSp8S26hfWipVWwQj4js/C7RoPtvt2iyeU+LSH81jG4wlAWntiOG1WtoXUuXWSc
ExhciKeKWCnemy9qqmxRfJqBROeGlQIDAQABo4IEDjCCBAowCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBQ/A7/CxKEnzpqmZlLz
9iaQMy24eTAfBgNVHSMEGDAWgBSuVYNv7DHKufcd+q9rMfPIHeOsuzB+BgNVHREEdzB1gQ9qYnJh
ZGxleUBtZS5jb22BD2picmFkbGV5QG1lLmNvbYEQamJyYWRsZXlAbWFjLmNvbYERdmU3anRiQHZl
N2p0Yi5jb22BE2picmFkbGV5QHdpbmdhYS5jb22BF2pvaG4uYnJhZGxleUB3aW5nYWEuY29tMIIC
IQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNj
b3JkaW5nIHRvIHRoZSBDbGFzcyAyIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcC
AjCBjzAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkg
YW5kIHdhcnJhbnRpZXMgYXJlIGxpbWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRh
dGlvbnMiIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUyLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYB
BQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MyL2NsaWVudC9jYTBCBggr
BgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMi5jbGllbnQu
Y2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEAEcfD4PmHrX+W3zaP/KsR4gwLAL0UTaMz14SIng6a9F3kb8ZDbTUneS9ubgpqeJQP2IFc
0U5gQnJ3XeCH6p9I88mvm1NqKQw8WvfglS0aIS19vfpTgXJSPdIO2JJPRqaBtXf3zkdXJwckX9/d
NMrLGeGvaFT9fUNdQdHU4BI1pVUpgKr796T7LTc/ERfH8iFp1+CmdVkJ6Y2iJdWUp4h17XmbxbIT
0CdS4SSk/VW8LFsn/mVz6hB73VthwjGsIku54Wp4pRuq1KX+pATnRk3pHRa1z3mxJMmq7OEXENcC
Vm+bAnyUrYbUilNS9UVTYS8/3dVsKiNupBaOZO+vOgJqVDGCA2wwggNoAgEBMIGTMIGMMQswCQYD
VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwg
Q2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IElu
dGVybWVkaWF0ZSBDbGllbnQgQ0ECAh5cMAkGBSsOAwIaBQCgggGtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDYxMDE2MTAyMVowIwYJKoZIhvcNAQkEMRYEFK/A
bw+O7T9dywPl6l+/YMYXa2wiMIGkBgkrBgEEAYI3EAQxgZYwgZMwgYwxCzAJBgNVBAYTAklMMRYw
FAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0
ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQQICHlwwgaYGCyqGSIb3DQEJEAILMYGWoIGTMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUg
U2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBD
bGllbnQgQ0ECAh5cMA0GCSqGSIb3DQEBAQUABIIBAGfRj1+5Hx4i7Ov/1fklFT/zf14c8E+e+oG7
25Qvhs4glOQEslpBFPY8Nh3rZRZ14IIQSEwrYcm4/xWQ4j8Zxa6XflZxXZ08dsCgfTxmYChMB97e
di6PbCx8GoCQooOlarkJF/fA541VCqcBMGjnNkGLBpRkO5B7hOt+OLZwhHz67bH05ItYYDx1iV1n
3xNV85GdnhpFXglehfFhBJkEIJcIA5cY3F5Pak4liiRFYjTVCztpV9NdowJ8I6JrZem7WJU4Fl3t
RDfBbynoxSK7j/P+Mlkk49RMpuf8cPFPZFvsz0ITMc/nJaqnUiz9td/I4G7mcrgo/xUOwNWBl/dX
2GsAAAAAAAA=

--Apple-Mail-5718F173-3201-406B-8824-D46B7FF75C72--

From ve7jtb@ve7jtb.com  Mon Jun 10 09:11:44 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37C421F95D7 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OE-p9nM5PHJt for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:11:44 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCE121F9619 for <jose@ietf.org>; Mon, 10 Jun 2013 09:11:39 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id m6so1560511wiv.2 for <jose@ietf.org>; Mon, 10 Jun 2013 09:11:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=Wnwcg7aThSvDJtH1NLkJIQbYM+l18nfYz8vIRyNTgw8=; b=W1uzKBZQpePIS8/sd3/Fs4qFxBRv+VeZ3lbO0lUX7rTXrYuyjmhDKG49Vex01EWXrp bBq1sYxyLho2HoaVbutCAfLOXhAijkzyXbOT2Znu+PDEAB/6KbhPRx8lA8APZq7GrkQN AK706LO7rNbrLN2XNhDfosbHPe3X+CraH01ETQfyGL38RnLvTvBOi72BEqYImARqF6ph ASx6xKmW/MfJykDhPilVoDPP204/lPlAlaCN2ApkiUP1B30W4lVSMmYyiNEyKmBRA9jc nB+lBzTk8XltgiZ08ovxV+XcRb7MOSLku3FUg/gpJEvdYXCmF3WAzqoz9uKlHGZ3ZiBc B82g==
X-Received: by 10.180.36.205 with SMTP id s13mr5134000wij.31.1370880698789; Mon, 10 Jun 2013 09:11:38 -0700 (PDT)
Received: from [10.147.129.63] ([188.207.110.177]) by mx.google.com with ESMTPSA id m3sm12441575wij.5.2013.06.10.09.11.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Jun 2013 09:11:37 -0700 (PDT)
References: <514C5FC3.20007@isoc.org> <51A814A9.8060208@isoc.org> <4E1F6AAD24975D4BA5B16804296739436781B290@TK5EX14MBXC283.redmond.corp.microsoft.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781B290@TK5EX14MBXC283.redmond.corp.microsoft.com>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-8AEFF63A-9826-4285-98D1-D8804D46098F; protocol="application/pkcs7-signature"
Content-Transfer-Encoding: 7bit
Message-Id: <AEC52792-316E-43A2-A08D-10849EAD556A@ve7jtb.com>
X-Mailer: iPhone Mail (10B329)
From: John Bradley <ve7jtb@ve7jtb.com>
Date: Mon, 10 Jun 2013 18:11:35 +0200
To: Mike Jones <Michael.Jones@microsoft.com>
X-Gm-Message-State: ALoCoQlUfwLFCLl2Gr+FG9hYaCD/FSZ6vVkMARMynHG7KGg6CPMqMw5NAR6GrEBVBpvqGfFMmc1k
Cc: "jose@ietf.org" <jose@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Subject: Re: [jose] jose wg teleconference announcement - 17 June 2013
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:11:44 -0000

--Apple-Mail-8AEFF63A-9826-4285-98D1-D8804D46098F
Content-Type: multipart/alternative;
	boundary=Apple-Mail-20ACA2DF-FC5D-4666-BC87-D07E250B3B5B
Content-Transfer-Encoding: 7bit


--Apple-Mail-20ACA2DF-FC5D-4666-BC87-D07E250B3B5B
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Wait you tricked me,  it is next Monday.=20

Sent from my iPhone

On 2013-06-10, at 6:07 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:

> What is the call-in information?  Sorry if I missed it.
>=20
> -- Mike
>=20
> From: Karen O'Donoghue
> Sent: 5/30/2013 8:11 PM
> To: jose@ietf.org
> Subject: [jose] jose wg teleconference announcement - 17 June 2013
>=20
> The jose working group will have a teleconference on Monday 17 June 2013=20=

> at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).
>=20
> The primary objective of the call will be to ensure the results of the=20
> interim meeting were adequately incorporated and to identify any final=20
> issues on the recently published drafts.
>=20
> The interim meeting minutes are available at:
> http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-in=
terim-2013-jose-1
>=20
> The updated specifications are available at:
> http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11
> http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11
>=20
> An agenda and webex details will be available next week.
>=20
> Regards,
> Karen
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

--Apple-Mail-20ACA2DF-FC5D-4666-BC87-D07E250B3B5B
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Wait you tricked me, &nbsp;it is next Monday.&nbsp;<br><br>Sent from my iPhone</div><div><br>On 2013-06-10, at 6:07 PM, Mike Jones &lt;<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>


<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">What is the call-in information?&nbsp; Sorry if I missed it.<br>
<br>
-- Mike<br>
<br>
</div>
</div>
<hr>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">From:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Karen O'Donoghue</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Sent:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">5/30/2013 8:11 PM</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">To:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt"><a href="mailto:jose@ietf.org">jose@ietf.org</a></span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Subject:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">[jose] jose wg teleconference announcement - 17 June 2013</span><br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">The jose working group will have a teleconference on Monday 17 June 2013
<br>
at 5:00 pm UTC (10:00 am PDT / 1:00 pm EDT).<br>
<br>
The primary objective of the call will be to ensure the results of the <br>
interim meeting were adequately incorporated and to identify any final <br>
issues on the recently published drafts.<br>
<br>
The interim meeting minutes are available at:<br>
<a href="http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-interim-2013-jose-1">http://www.ietf.org/proceedings/interim/2013/04/29/jose/minutes/minutes-interim-2013-jose-1</a><br>
<br>
The updated specifications are available at:<br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-key-11</a><br>
<a href="http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11">http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11</a><br>
<br>
An agenda and webex details will be available next week.<br>
<br>
Regards,<br>
Karen<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href="mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a><br>
</div>
</span></font>


</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>jose mailing list</span><br><span><a href="mailto:jose@ietf.org">jose@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a></span><br></div></blockquote></body></html>
--Apple-Mail-20ACA2DF-FC5D-4666-BC87-D07E250B3B5B--

--Apple-Mail-8AEFF63A-9826-4285-98D1-D8804D46098F
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHuTCCB7Uw
ggadoAMCAQICAh5cMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew
HhcNMTIwMzE4MDQzMjQ4WhcNMTQwMzE5MTEwNzMyWjCBmzEZMBcGA1UEDRMQR3JUTTZMUzdYMzU3
NzhzOTELMAkGA1UEBhMCQ0wxIjAgBgNVBAgTGU1ldHJvcG9saXRhbmEgZGUgU2FudGlhZ28xFjAU
BgNVBAcTDUlzbGEgZGUgTWFpcG8xFTATBgNVBAMTDEpvaG4gQnJhZGxleTEeMBwGCSqGSIb3DQEJ
ARYPamJyYWRsZXlAbWUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAskrlBI93
rBTLOQGSwIT6co6dAw/rwDPrRXl6/F2oc4KDn+QN6CdFeHo08H846VJS9CDjLKvnK9jbxxs4wYqe
nKdPb3jgzt8oc7b9ZXtWkOgsxgMf6dBZ/IPm4lWBpCbSr3seDGDXEpiE2lTZXno7c25OguR4E6Qa
hcpHABZjeEWK65mMH25gmoRf5MY1k3quu5y+FCYCHE2iwU5jzq+mI3HmG59+UMFLx1fjV+zTslRw
26cQDC/uepwjeYSp8S26hfWipVWwQj4js/C7RoPtvt2iyeU+LSH81jG4wlAWntiOG1WtoXUuXWSc
ExhciKeKWCnemy9qqmxRfJqBROeGlQIDAQABo4IEDjCCBAowCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBQ/A7/CxKEnzpqmZlLz
9iaQMy24eTAfBgNVHSMEGDAWgBSuVYNv7DHKufcd+q9rMfPIHeOsuzB+BgNVHREEdzB1gQ9qYnJh
ZGxleUBtZS5jb22BD2picmFkbGV5QG1lLmNvbYEQamJyYWRsZXlAbWFjLmNvbYERdmU3anRiQHZl
N2p0Yi5jb22BE2picmFkbGV5QHdpbmdhYS5jb22BF2pvaG4uYnJhZGxleUB3aW5nYWEuY29tMIIC
IQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNj
b3JkaW5nIHRvIHRoZSBDbGFzcyAyIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcC
AjCBjzAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkg
YW5kIHdhcnJhbnRpZXMgYXJlIGxpbWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRh
dGlvbnMiIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUyLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYB
BQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MyL2NsaWVudC9jYTBCBggr
BgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMi5jbGllbnQu
Y2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEAEcfD4PmHrX+W3zaP/KsR4gwLAL0UTaMz14SIng6a9F3kb8ZDbTUneS9ubgpqeJQP2IFc
0U5gQnJ3XeCH6p9I88mvm1NqKQw8WvfglS0aIS19vfpTgXJSPdIO2JJPRqaBtXf3zkdXJwckX9/d
NMrLGeGvaFT9fUNdQdHU4BI1pVUpgKr796T7LTc/ERfH8iFp1+CmdVkJ6Y2iJdWUp4h17XmbxbIT
0CdS4SSk/VW8LFsn/mVz6hB73VthwjGsIku54Wp4pRuq1KX+pATnRk3pHRa1z3mxJMmq7OEXENcC
Vm+bAnyUrYbUilNS9UVTYS8/3dVsKiNupBaOZO+vOgJqVDGCA2wwggNoAgEBMIGTMIGMMQswCQYD
VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwg
Q2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IElu
dGVybWVkaWF0ZSBDbGllbnQgQ0ECAh5cMAkGBSsOAwIaBQCgggGtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDYxMDE2MTEzN1owIwYJKoZIhvcNAQkEMRYEFEgS
96R03CA2IOXoCNXC6neZ+WxmMIGkBgkrBgEEAYI3EAQxgZYwgZMwgYwxCzAJBgNVBAYTAklMMRYw
FAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0
ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQQICHlwwgaYGCyqGSIb3DQEJEAILMYGWoIGTMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUg
U2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBD
bGllbnQgQ0ECAh5cMA0GCSqGSIb3DQEBAQUABIIBAFv/aHM/JvmvLMpFYljIp62AU3SSfHvH+7uf
jYTL4nQXHqqDzry86MSZZnyGWsfRDAdUc/II7WSl4PiXcsyEsxwFtVVs/KqocEx+whiVXOJS7G0y
HVGHuBck08D4HcZTXyJ5KMN6lvHCUDsn7mYnOai930A7rLGoFYk4QVV4lxRMx3E+ObJPDCneRlia
OzV370RqfhzZ9oMPHALtfzGNgPtEm7BpkcxzG4L+a5JdNZoxqthNxkIy9Yb/+y8ZOmu20c6GV0G1
1rxTuxpJ8+wn3Z8J/1n31B2yueKvrhN8CjmyOqVkOhnTpu09/gv69BkxEMqE06kL1OHYr0ZnQcEV
UvEAAAAAAAA=

--Apple-Mail-8AEFF63A-9826-4285-98D1-D8804D46098F--

From odonoghue@isoc.org  Mon Jun 10 09:20:50 2013
Return-Path: <odonoghue@isoc.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5CDC21F9732 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.264
X-Spam-Level: 
X-Spam-Status: No, score=-103.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWDHPm9Zk+rM for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:20:46 -0700 (PDT)
Received: from smtp146.dfw.emailsrvr.com (smtp146.dfw.emailsrvr.com [67.192.241.146]) by ietfa.amsl.com (Postfix) with ESMTP id 67F8521F993E for <jose@ietf.org>; Mon, 10 Jun 2013 09:20:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp24.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 6775218077B for <jose@ietf.org>; Mon, 10 Jun 2013 12:20:29 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp24.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id D14A3180787 for <jose@ietf.org>; Mon, 10 Jun 2013 12:20:28 -0400 (EDT)
Message-ID: <51B5FCCB.1000502@isoc.org>
Date: Mon, 10 Jun 2013 12:20:27 -0400
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "jose@ietf.org" <jose@ietf.org>
References: <425517518.61374.1370276346881.JavaMail.nobody@jva2tc003.webex.com>
In-Reply-To: <425517518.61374.1370276346881.JavaMail.nobody@jva2tc003.webex.com>
X-Forwarded-Message-Id: <425517518.61374.1370276346881.JavaMail.nobody@jva2tc003.webex.com>
Content-Type: multipart/alternative; boundary="------------010104000103010807010700"
Subject: [jose] webex information for JOSE teleconference: 17 June 2013 @ 1:00 pm EDT
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.org
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 Jun 2013 16:20:50 -0000

This is a multi-part message in MIME format.
--------------010104000103010807010700
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

Here is the webex information for the call next Monday.

Karen


Cindy Morgan invites you to attend this online meeting.

Topic: JOSE
Date: Monday, June 17, 2013
Time: 11:00 am, Mountain Daylight Time (Denver, GMT-06:00)
Meeting Number: 648 447 409
Meeting Password: 1234


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to 
https://ietf.webex.com/ietf/j.php?ED=225472827&UID=1566381972&PW=NOWQ4YWY3NDc1&RT=MiM2 

2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 1234
4. Click "Join".

To view in other time zones or languages, please click the link:
https://ietf.webex.com/ietf/j.php?ED=225472827&UID=1566381972&PW=NOWQ4YWY3NDc1&ORT=MiM2 


-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
Call-in toll number (US/Canada): 1-650-479-3208

Access code:648 447 409

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://ietf.webex.com/ietf/mc
2. On the left navigation bar, click "Support".

You can contact me at:
cmorgan@amsl.com <mailto:cmorgan@amsl.com>
1-510-492-4085

To add this meeting to your calendar program (for example Microsoft 
Outlook), click this link:
https://ietf.webex.com/ietf/j.php?ED=225472827&UID=1566381972&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAnBS0dxwb5o23cp6D4NhhtUFgQ0Ft4xS6lHRlHHZAwFT&RT=MiM2 


The playback of UCF (Universal Communications Format) rich media files 
requires appropriate players. To view this type of rich media files in 
the meeting, please check whether you have the players installed on your 
computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php.

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+16504793208x648447409#

IMPORTANT NOTICE: This WebEx service includes a feature that allows 
audio and any documents and other materials exchanged or viewed during 
the session to be recorded. By joining this session, you automatically 
consent to such recordings. If you do not consent to the recording, 
discuss your concerns with the meeting host prior to the start of the 
recording or do not join the session. Please note that any such 
recordings may be subject to discovery in the event of litigation.



--------------010104000103010807010700
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Folks,<br>
    <br>
    Here is the webex information for the call next Monday. <br>
    <br>
    Karen<br>
    <br>
    <div class="moz-forward-container"><br>
      <font face="Tahoma, Arial, sans-serif, Helvetica, Geneva" size="2">Cindy
        Morgan invites you to attend this online meeting. <br>
        <br>
        Topic: JOSE <br>
        Date: Monday, June 17, 2013 <br>
        Time: 11:00 am, Mountain Daylight Time (Denver, GMT-06:00) <br>
        Meeting Number: 648 447 409 <br>
        Meeting Password: 1234 <br>
        <br>
        <br>
        ------------------------------------------------------- <br>
        To join the online meeting (Now from mobile devices!) <br>
        ------------------------------------------------------- <br>
        1. Go to <a moz-do-not-send="true"
href="https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;PW=NOWQ4YWY3NDc1&amp;RT=MiM2"
          target="_blank">https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;PW=NOWQ4YWY3NDc1&amp;RT=MiM2</a>
        <br>
        2. If requested, enter your name and email address. <br>
        3. If a password is required, enter the meeting password: 1234 <br>
        4. Click "Join". <br>
        <br>
        To view in other time zones or languages, please click the link:
        <br>
        <a moz-do-not-send="true"
href="https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;PW=NOWQ4YWY3NDc1&amp;ORT=MiM2"
          target="_blank">https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;PW=NOWQ4YWY3NDc1&amp;ORT=MiM2</a>
        <br>
        <br>
        ------------------------------------------------------- <br>
        To join the audio conference only <br>
        ------------------------------------------------------- <br>
        Call-in toll number (US/Canada): 1-650-479-3208 <br>
        <br>
        Access code:648 447 409 <br>
        <br>
        ------------------------------------------------------- <br>
        For assistance <br>
        ------------------------------------------------------- <br>
        1. Go to <a moz-do-not-send="true"
          href="https://ietf.webex.com/ietf/mc" target="_blank">https://ietf.webex.com/ietf/mc</a>
        <br>
        2. On the left navigation bar, click "Support". <br>
        <br>
        You can contact me at: <br>
        <a moz-do-not-send="true" href="mailto:cmorgan@amsl.com">cmorgan@amsl.com</a>
        <br>
        1-510-492-4085 <br>
        <br>
        To add this meeting to your calendar program (for example
        Microsoft Outlook), click this link: <br>
        <a moz-do-not-send="true"
href="https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=AAAAAnBS0dxwb5o23cp6D4NhhtUFgQ0Ft4xS6lHRlHHZAwFT&amp;RT=MiM2"
          target="_blank">https://ietf.webex.com/ietf/j.php?ED=225472827&amp;UID=1566381972&amp;ICS=MI&amp;LD=1&amp;RD=2&amp;ST=1&amp;SHA2=AAAAAnBS0dxwb5o23cp6D4NhhtUFgQ0Ft4xS6lHRlHHZAwFT&amp;RT=MiM2</a>
        <br>
        <br>
        The playback of UCF (Universal Communications Format) rich media
        files requires appropriate players. To view this type of rich
        media files in the meeting, please check whether you have the
        players installed on your computer by going to <a
          moz-do-not-send="true"
          href="https://ietf.webex.com/ietf/systemdiagnosis.php">https://ietf.webex.com/ietf/systemdiagnosis.php</a>.
        <br>
        <br>
        Sign up for a free trial of WebEx <br>
        <a moz-do-not-send="true"
          href="http://www.webex.com/go/mcemfreetrial" target="_blank">http://www.webex.com/go/mcemfreetrial</a>
        <br>
        <br>
        <a moz-do-not-send="true" href="http://www.webex.com"
          target="_blank">http://www.webex.com</a> <br>
        <br>
        CCP:+16504793208x648447409# <br>
        <br>
        IMPORTANT NOTICE: This WebEx service includes a feature that
        allows audio and any documents and other materials exchanged or
        viewed during the session to be recorded. By joining this
        session, you automatically consent to such recordings. If you do
        not consent to the recording, discuss your concerns with the
        meeting host prior to the start of the recording or do not join
        the session. Please note that any such recordings may be subject
        to discovery in the event of litigation. <br>
      </font><br>
    </div>
    <br>
  </body>
</html>

--------------010104000103010807010700--

From rlb@ipv.sx  Mon Jun 10 09:28:35 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB33A21F85C0 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGTbLbPv0Lfi for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:28:31 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A071021F859A for <jose@ietf.org>; Mon, 10 Jun 2013 09:28:31 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id ef5so10423847obb.15 for <jose@ietf.org>; Mon, 10 Jun 2013 09:28:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=FSHLbw2XtWDOHnr219Ppk3c8z9JfAKN98iOFYcSxkyM=; b=RTA8UfWeHjJiu9dehn9mVqfVXFv46DrcwDgstTIjmHfuQAz37FHEUYFOvix0PlAMxY 6sZPwly8DFOVqVdaYniX2ZZACVFVSaLF6FfNsLUKsGuOZBEhsB3AleZIM5iuTgyfScYX cF6dYgmDzk3aisMLyRqFT7uTedIVwBqxWyAohNwZ+zzhagZM/38/ynp4jNngs3g40bGo nVKnAHaNE4ig+t9QixFly2DWXP8pJs4E+eFCBWLGfHfjxqMg/PIgOWw+Q+hzWqj45amJ TEDlj9Yh76WvZwvCc5wKB2tpgOjEUjlcfItyT34ZZE/oMYTTha31Cx+t3jr+AYoLC1lN K5tg==
MIME-Version: 1.0
X-Received: by 10.60.52.15 with SMTP id p15mr8585693oeo.87.1370881711117; Mon, 10 Jun 2013 09:28:31 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 09:28:31 -0700 (PDT)
X-Originating-IP: [192.1.255.206]
In-Reply-To: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>
Date: Mon, 10 Jun 2013 12:28:31 -0400
Message-ID: <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a113309ce6bf3fc04decf458f
X-Gm-Message-State: ALoCoQlkhUUnrobD01byzRKymLAdOgLwi42SxcvaBav4aWxBETYJ41lIjrFyo+YwGQxYpKI7PZab
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:28:35 -0000

--001a113309ce6bf3fc04decf458f
Content-Type: text/plain; charset=ISO-8859-1

This sounds like a fine idea to me.  It saves space and makes the JSON
format more human-readable.  It actually makes kind of a nice analogy to
ASN.1, namely use of OCTET STRING to encapsulate more DER content.

The compact serialization can continue to base64url-encode that field, so
it would not be a breaking change for that serialization.

--Richard


On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com> wrote:

> <no hat>****
>
> ** **
>
> I am trying to figure out if I am missing something.  This is not yet a
> formal proposal to actual change the document.****
>
> ** **
>
> I was thinking about proposing that we make a change to the content of the
> protected field in the JWS JSON serialization format.  If we encoded this
> as a UTF8 string rather than the base64url encoded UTF8 string, then the
> content would be smaller.  The computation of the signature would be
> unchanged in that it would still be computed over the base64url encoded
> string.  I believe that the conversion from the UTF8 string to the
> base64url encoded UTF8 string is a deterministic encoding and thus would
> not generate any problems from that point.****
>
> ** **
>
> At this point I and trying to figure out if I missed anything that would
> preclude this from working.  I am not worried about how hard or easy it
> would be to do, just if it is even possible.****
>
> ** **
>
> Jim****
>
> ** **
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--001a113309ce6bf3fc04decf458f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This sounds like a fine idea to me. =A0It saves space and =
makes the JSON format more human-readable. =A0It actually makes kind of a n=
ice analogy to ASN.1, namely use of OCTET STRING to encapsulate more DER co=
ntent.<div>
<br></div><div>The compact serialization can continue to base64url-encode t=
hat field, so it would not be a breaking change for that serialization.</di=
v><div><br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br>
<br><div class=3D"gmail_quote">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad =
<span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_=
blank">ietf@augustcellars.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al">&lt;no hat&gt;<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u=
></p><p class=3D"MsoNormal">I am trying to figure out if I am missing somet=
hing.=A0 This is not yet a formal proposal to actual change the document.<u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">I was th=
inking about proposing that we make a change to the content of the protecte=
d field in the JWS JSON serialization format.=A0 If we encoded this as a UT=
F8 string rather than the base64url encoded UTF8 string, then the content w=
ould be smaller. =A0The computation of the signature would be unchanged in =
that it would still be computed over the base64url encoded string.=A0 I bel=
ieve that the conversion from the UTF8 string to the base64url encoded UTF8=
 string is a deterministic encoding and thus would not generate any problem=
s from that point.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">At this =
point I and trying to figure out if I missed anything that would preclude t=
his from working. =A0I am not worried about how hard or easy it would be to=
 do, just if it is even possible.<span class=3D"HOEnZb"><font color=3D"#888=
888"><u></u><u></u></font></span></p>
<span class=3D"HOEnZb"><font color=3D"#888888"><p class=3D"MsoNormal"><u></=
u>=A0<u></u></p><p class=3D"MsoNormal">Jim<u></u><u></u></p><p class=3D"Mso=
Normal"><u></u>=A0<u></u></p></font></span></div></div><br>________________=
_______________________________<br>

jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--001a113309ce6bf3fc04decf458f--

From rlb@ipv.sx  Mon Jun 10 09:32:04 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE0521F9675 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQXo+xkpArqF for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:32:00 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 1D23621F8900 for <jose@ietf.org>; Mon, 10 Jun 2013 09:31:43 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id 16so10319377obc.26 for <jose@ietf.org>; Mon, 10 Jun 2013 09:31:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=8NvWVCyFFTBEBYl6yq7fXg9YnK2IEtX5L3Z3VnRdeFE=; b=hvVO6QJaqZZqse5Rhfe5AaNJ8O7K0j44XirwGzEbyeJ/1LkHwYBUmrlfi/Wl2/mH1f 9rtOE7cfDWbfu3L4A9R1DmxJy4/ebJjsl/ojFSTgBash+l+IEEpR4Po+q3FGGQAVm3s9 idsDjortlPASJB0hav+dEn7h6UUg3NaYw5UolYPcs4mIee1ksx2jFlNPi+zMc7F8HKDI hOdQthfMdGYWRUT4URkFRDWDRkCDnclqPFkDcHDthd4sFC+wdJdFdAQlVTZeGLKy22Qf xnw0GXEhk+al2Qof/RkfJqid+6qahLTXw3D8+/PXSue0VJuYc6ZYYcFd4zStqb/3s8dz SW9Q==
MIME-Version: 1.0
X-Received: by 10.182.74.131 with SMTP id t3mr8733861obv.87.1370881902528; Mon, 10 Jun 2013 09:31:42 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 09:31:42 -0700 (PDT)
X-Originating-IP: [192.1.255.206]
In-Reply-To: <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>
Date: Mon, 10 Jun 2013 12:31:42 -0400
Message-ID: <CAL02cgQVz9-A1nGPcE1j3K5oYMzFhC2UUOaYhDVrsb10gSqkHw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a11c1be06d4becd04decf5095
X-Gm-Message-State: ALoCoQmQLsUuq9Y1DhFY/49TqsWlFmxn1d3I65ykarul0kIgwd/7bQeaB6Hl2/5tBuJ67cFOc5A+
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:32:04 -0000

--001a11c1be06d4becd04decf5095
Content-Type: text/plain; charset=ISO-8859-1

On second thought: It seems like the signature should actually be over the
UTF-8 octets, rather than the base64 octets.  To reason by analogy: For
every other field in a JWE, you decode the field before using it in a
cryptographic computation.  So it should be the same with the protected
header.

--Richard


On Mon, Jun 10, 2013 at 12:28 PM, Richard Barnes <rlb@ipv.sx> wrote:

> This sounds like a fine idea to me.  It saves space and makes the JSON
> format more human-readable.  It actually makes kind of a nice analogy to
> ASN.1, namely use of OCTET STRING to encapsulate more DER content.
>
> The compact serialization can continue to base64url-encode that field, so
> it would not be a breaking change for that serialization.
>
> --Richard
>
>
> On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com>wrote:
>
>> <no hat>****
>>
>> ** **
>>
>> I am trying to figure out if I am missing something.  This is not yet a
>> formal proposal to actual change the document.****
>>
>> ** **
>>
>> I was thinking about proposing that we make a change to the content of
>> the protected field in the JWS JSON serialization format.  If we encoded
>> this as a UTF8 string rather than the base64url encoded UTF8 string, then
>> the content would be smaller.  The computation of the signature would be
>> unchanged in that it would still be computed over the base64url encoded
>> string.  I believe that the conversion from the UTF8 string to the
>> base64url encoded UTF8 string is a deterministic encoding and thus would
>> not generate any problems from that point.****
>>
>> ** **
>>
>> At this point I and trying to figure out if I missed anything that would
>> preclude this from working.  I am not worried about how hard or easy it
>> would be to do, just if it is even possible.****
>>
>> ** **
>>
>> Jim****
>>
>> ** **
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>

--001a11c1be06d4becd04decf5095
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On second thought: It seems like the signature should actu=
ally be over the UTF-8 octets, rather than the base64 octets. =A0To reason =
by analogy: For every other field in a JWE, you decode the field before usi=
ng it in a cryptographic computation. =A0So it should be the same with the =
protected header.<div>
<br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Mon, Jun 10, 2013 at 12:28 PM, Richard Barnes <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.=
sx</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">This sounds like a fine ide=
a to me. =A0It saves space and makes the JSON format more human-readable. =
=A0It actually makes kind of a nice analogy to ASN.1, namely use of OCTET S=
TRING to encapsulate more DER content.<div>

<br></div><div>The compact serialization can continue to base64url-encode t=
hat field, so it would not be a breaking change for that serialization.</di=
v><div><br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br>

<br><div class=3D"gmail_quote"><div><div class=3D"h5">On Mon, Jun 10, 2013 =
at 1:46 AM, Jim Schaad <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustc=
ellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt;</span> wrote:<=
br></div>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al">&lt;no hat&gt;<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u=
></p><p class=3D"MsoNormal">I am trying to figure out if I am missing somet=
hing.=A0 This is not yet a formal proposal to actual change the document.<u=
></u><u></u></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">I was th=
inking about proposing that we make a change to the content of the protecte=
d field in the JWS JSON serialization format.=A0 If we encoded this as a UT=
F8 string rather than the base64url encoded UTF8 string, then the content w=
ould be smaller. =A0The computation of the signature would be unchanged in =
that it would still be computed over the base64url encoded string.=A0 I bel=
ieve that the conversion from the UTF8 string to the base64url encoded UTF8=
 string is a deterministic encoding and thus would not generate any problem=
s from that point.<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">At this =
point I and trying to figure out if I missed anything that would preclude t=
his from working. =A0I am not worried about how hard or easy it would be to=
 do, just if it is even possible.<span><font color=3D"#888888"><u></u><u></=
u></font></span></p>

<span><font color=3D"#888888"><p class=3D"MsoNormal"><u></u>=A0<u></u></p><=
p class=3D"MsoNormal">Jim<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=
=A0<u></u></p></font></span></div></div><br></div></div>___________________=
____________________________<br>


jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>

--001a11c1be06d4becd04decf5095--

From Michael.Jones@microsoft.com  Mon Jun 10 09:39:01 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E15821F84B4 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sjc8dfyqnMjE for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 09:38:56 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id D0E8121F84B1 for <jose@ietf.org>; Mon, 10 Jun 2013 09:38:55 -0700 (PDT)
Received: from BY2FFO11FD014.protection.gbl (10.1.15.201) by BY2FFO11HUB012.protection.gbl (10.1.14.83) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 10 Jun 2013 16:38:53 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD014.mail.protection.outlook.com (10.1.14.76) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 10 Jun 2013 16:38:52 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Mon, 10 Jun 2013 16:38:43 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5lnSf72X6a3Ku/SKOo5PcgVR4NIgAWmNmAAAAbQTA=
Date: Mon, 10 Jun 2013 16:38:42 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>
In-Reply-To: <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436781C117TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(24454002)(377454002)(512954002)(50986001)(63696002)(54356001)(53806001)(80022001)(20776003)(74366001)(561944002)(76786001)(69226001)(56776001)(77096001)(47446002)(74706001)(16406001)(33656001)(59766001)(79102001)(56816003)(65816001)(81342001)(77982001)(76482001)(76796001)(47976001)(81542001)(15202345002)(74502001)(66066001)(46102001)(44976003)(31966008)(16236675002)(71186001)(4396001)(6806003)(54316002)(74662001)(51856001)(47736001)(74876001)(55846006)(49866001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB012; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087396016C
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 16:39:01 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436781C117TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The problem with this suggested change is that it requires unencoded JSON o=
bjects to be transmitted with no transformations whatsoever, whereas the pr=
oblems with this assumption are well known.  For starters, on UNIX-based sy=
stems, newlines are typically represented by a bare LF character, whereas o=
n DOS-based systems, newlines are typically represented by a CRLF pair.  In=
 transmission, many systems, including mail agents tend to convert newlines=
 to the system's normal format.  This would break these JOSE objects.

Some agents wrap lines after a certain length.  Particularly when being tra=
nsmitted in HTML or XML, many systems replace two or more consecutive space=
s with a single space.  Others replace two or more spaces with a single spa=
ce and N-1 non-breaking space characters.  I could go on...

I appreciate the attempt to make things appear to be more uniform and reada=
ble, but the CRLF/LF problems alone are enough to make this a non-starter.

                                                                Best wishes=
,
                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Possible change to protected field

This sounds like a fine idea to me.  It saves space and makes the JSON form=
at more human-readable.  It actually makes kind of a nice analogy to ASN.1,=
 namely use of OCTET STRING to encapsulate more DER content.

The compact serialization can continue to base64url-encode that field, so i=
t would not be a breaking change for that serialization.

--Richard

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

I am trying to figure out if I am missing something.  This is not yet a for=
mal proposal to actual change the document.

I was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.  If we encoded this a=
s a UTF8 string rather than the base64url encoded UTF8 string, then the con=
tent would be smaller.  The computation of the signature would be unchanged=
 in that it would still be computed over the base64url encoded string.  I b=
elieve that the conversion from the UTF8 string to the base64url encoded UT=
F8 string is a deterministic encoding and thus would not generate any probl=
ems from that point.

At this point I and trying to figure out if I missed anything that would pr=
eclude this from working.  I am not worried about how hard or easy it would=
 be to do, just if it is even possible.

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B16804296739436781C117TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The problem with this sug=
gested change is that it requires unencoded JSON objects to be transmitted =
with no transformations whatsoever, whereas the problems
 with this assumption are well known.&nbsp; For starters, on UNIX-based sys=
tems, newlines are typically represented by a bare LF character, whereas on=
 DOS-based systems, newlines are typically represented by a CRLF pair.&nbsp=
; In transmission, many systems, including
 mail agents tend to convert newlines to the system&#8217;s normal format.&=
nbsp; This would break these JOSE objects.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Some agents wrap lines af=
ter a certain length.&nbsp; Particularly when being transmitted in HTML or =
XML, many systems replace two or more consecutive spaces with
 a single space.&nbsp; Others replace two or more spaces with a single spac=
e and N-1 non-breaking space characters.&nbsp; I could go on&#8230;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I appreciate the attempt =
to make things appear to be more uniform and readable, but the CRLF/LF prob=
lems alone are enough to make this a non-starter.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">This sounds like a fine idea to me. &nbsp;It saves s=
pace and makes the JSON format more human-readable. &nbsp;It actually makes=
 kind of a nice analogy to ASN.1, namely use of OCTET STRING to encapsulate=
 more DER content.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The compact serialization can continue to base64url-=
encode that field, so it would not be a breaking change for that serializat=
ion.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I am trying to figure out if I am missing something.&nbsp; This is=
 not yet a formal proposal to actual change the document.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was thinking about proposing that we make a change to the conten=
t of the protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. &nbs=
p;The computation of the signature would be unchanged in that it would stil=
l be computed over the base64url encoded string.&nbsp; I believe that the c=
onversion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">At this point I and trying to figure out if I missed anything that=
 would preclude this from working. &nbsp;I am not worried about how hard or=
 easy it would be to do, just if it is even
 possible.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436781C117TK5EX14MBXC283r_--

From rlb@ipv.sx  Mon Jun 10 10:01:03 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82D221F995F for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfSc2Yl46Lqw for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:00:54 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 370E021F9965 for <jose@ietf.org>; Mon, 10 Jun 2013 10:00:54 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id l20so6327479oag.9 for <jose@ietf.org>; Mon, 10 Jun 2013 10:00:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=AWKu7RQh2uQcZFOwVAxLHjWigX3lcyAZMvwYpLQuBMo=; b=Kr9lnULv9yFK/GBV0AKWVdZ9LErymR/PrXUN4gCAaFSnaFauqiz80H67WyCRXMyMoh y/AS19Kt4T5/y8XL9KYEJHgVg/Jn3yXo67IP2lSxfHdX8DG19GBcv0f52aEAtXWFeBdW JLulH4IRxr3altxa01jKz4P0eO9azF90d9//nJY8E9zbkXQoDNiCl9cBnh9BMdm0EVZg K3isQyAqPlhs8sif3llzCoVo+n7/2MIvDNlXbESkYjQAK1Fs3HJSK7zeSNPwHv8eOQRq PnLGWtBAwz4i7j/+mMe2UVlAkpakivdsVvOxnEvNAqfRsAsmfCe/dU9WihMuTvC5ZPIB J0wQ==
MIME-Version: 1.0
X-Received: by 10.60.134.236 with SMTP id pn12mr9138746oeb.4.1370883653684; Mon, 10 Jun 2013 10:00:53 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 10:00:53 -0700 (PDT)
X-Originating-IP: [192.1.255.206]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 13:00:53 -0400
Message-ID: <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=047d7b471f6a353c2104decfb91d
X-Gm-Message-State: ALoCoQk0YdBjUnyDcRfVGialuHOZIxkZ48WQeTFXfP+HIQrYE8fYvaE3q+V3xSHVq4HE2CjwhZ71
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:01:04 -0000

--047d7b471f6a353c2104decfb91d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I think you've misunderstood the proposal.  It's not that the field will be
unencoded, it's that it will be encoded as a UTF-8 string instead of a
base64 string.

OLD: (json) --> UTF-8 --> base64
NEW: (json) --> UTF-8

OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }
NEW: { protected: "{\"alg\":\"RS256\"}" }

Now, there might still be a problem with that, because JSON strings aren't
canonical.  In the example above, the quote characters could also have been
presented as "\u0022".  So if some JSON re-processor were to change the
encoding ot the string, it would break the signature.  However, that's also
a problem for the base64-encoded version ("a" vs. "\u0061").





On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com>w=
rote:

>  The problem with this suggested change is that it requires unencoded
> JSON objects to be transmitted with no transformations whatsoever, wherea=
s
> the problems with this assumption are well known.  For starters, on
> UNIX-based systems, newlines are typically represented by a bare LF
> character, whereas on DOS-based systems, newlines are typically represent=
ed
> by a CRLF pair.  In transmission, many systems, including mail agents ten=
d
> to convert newlines to the system=92s normal format.  This would break th=
ese
> JOSE objects.****
>
> ** **
>
> Some agents wrap lines after a certain length.  Particularly when being
> transmitted in HTML or XML, many systems replace two or more consecutive
> spaces with a single space.  Others replace two or more spaces with a
> single space and N-1 non-breaking space characters.  I could go on=85****
>
> ** **
>
> I appreciate the attempt to make things appear to be more uniform and
> readable, but the CRLF/LF problems alone are enough to make this a
> non-starter.****
>
> ** **
>
>                                                                 Best
> wishes,****
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Monday, June 10, 2013 9:29 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
> ** **
>
> This sounds like a fine idea to me.  It saves space and makes the JSON
> format more human-readable.  It actually makes kind of a nice analogy to
> ASN.1, namely use of OCTET STRING to encapsulate more DER content.****
>
> ** **
>
> The compact serialization can continue to base64url-encode that field, so
> it would not be a breaking change for that serialization.****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> I am trying to figure out if I am missing something.  This is not yet a
> formal proposal to actual change the document.****
>
>  ****
>
> I was thinking about proposing that we make a change to the content of th=
e
> protected field in the JWS JSON serialization format.  If we encoded this
> as a UTF8 string rather than the base64url encoded UTF8 string, then the
> content would be smaller.  The computation of the signature would be
> unchanged in that it would still be computed over the base64url encoded
> string.  I believe that the conversion from the UTF8 string to the
> base64url encoded UTF8 string is a deterministic encoding and thus would
> not generate any problems from that point.****
>
>  ****
>
> At this point I and trying to figure out if I missed anything that would
> preclude this from working.  I am not worried about how hard or easy it
> would be to do, just if it is even possible.****
>
>  ****
>
> Jim****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>

--047d7b471f6a353c2104decfb91d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think you&#39;ve misunderstood the proposal. =A0It&#39;s=
 not that the field will be unencoded, it&#39;s that it will be encoded as =
a UTF-8 string instead of a base64 string.<div><br></div><div>OLD: (json) -=
-&gt; UTF-8 --&gt; base64</div>
<div>NEW: (json) --&gt; UTF-8</div><div><br></div><div>OLD: =A0{ protected:=
 &quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=3D&quot; }</div><div>NEW: { protected: &qu=
ot;{\&quot;alg\&quot;:\&quot;RS256\&quot;}&quot; }</div><div><br></div><div=
>Now, there might still be a problem with that, because JSON strings aren&#=
39;t canonical. =A0In the example above, the quote characters could also ha=
ve been presented as &quot;\u0022&quot;. =A0So if some JSON re-processor we=
re to change the encoding ot the string, it would break the signature. =A0H=
owever, that&#39;s also a problem for the base64-encoded version (&quot;a&q=
uot; vs. &quot;\u0061&quot;).</div>
<div><br></div><div><br></div><div><br><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"=
_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">The problem with this suggested change is that it req=
uires unencoded JSON objects to be transmitted with no transformations what=
soever, whereas the problems
 with this assumption are well known.=A0 For starters, on UNIX-based system=
s, newlines are typically represented by a bare LF character, whereas on DO=
S-based systems, newlines are typically represented by a CRLF pair.=A0 In t=
ransmission, many systems, including
 mail agents tend to convert newlines to the system=92s normal format.=A0 T=
his would break these JOSE objects.<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">Some agents wrap lines after a certain length.=A0 Par=
ticularly when being transmitted in HTML or XML, many systems replace two o=
r more consecutive spaces with
 a single space.=A0 Others replace two or more spaces with a single space a=
nd N-1 non-breaking space characters.=A0 I could go on=85<u></u><u></u></sp=
an></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">I appreciate the attempt to make things appear to be =
more uniform and readable, but the CRLF/LF problems alone are enough to mak=
e this a non-starter.<u></u><u></u></span></p>

<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Best wishes=
,<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u><=
/u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"=
_blank">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field<u></u><u></u>=
</span></p><div><div class=3D"h5">
<p class=3D""><u></u>=A0<u></u></p>
<div>
<p class=3D"">This sounds like a fine idea to me. =A0It saves space and mak=
es the JSON format more human-readable. =A0It actually makes kind of a nice=
 analogy to ASN.1, namely use of OCTET STRING to encapsulate more DER conte=
nt.<u></u><u></u></p>

<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">The compact serialization can continue to base64url-encode th=
at field, so it would not be a breaking change for that serialization.<u></=
u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a href=3D"ma=
ilto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&g=
t; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">I am trying to figure out if I am missing something.=A0 This =
is not yet a formal proposal to actual change the document.<u></u><u></u></=
p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">I was thinking about proposing that we make a change to the c=
ontent of the protected field in the JWS JSON serialization format.=A0 If w=
e encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. =A0T=
he computation of the signature would be unchanged in that it would still b=
e computed over the base64url encoded string.=A0 I believe that the convers=
ion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">At this point I and trying to figure out if I missed anything=
 that would preclude this from working. =A0I am not worried about how hard =
or easy it would be to do, just if it is even
 possible.<u></u><u></u></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">=A0<u></u><u></u></spa=
n></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">Jim<u></u><u></u></spa=
n></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">=A0<u></u><u></u></spa=
n></p>
</div>
</div>
<p class=3D"" style=3D"margin-bottom:12pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div></div></div>

--047d7b471f6a353c2104decfb91d--

From Michael.Jones@microsoft.com  Mon Jun 10 10:08:54 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8019721F85E6 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zd9fismCBfv for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:08:49 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id 0D96121F88AC for <jose@ietf.org>; Mon, 10 Jun 2013 10:08:48 -0700 (PDT)
Received: from BL2FFO11FD012.protection.gbl (10.173.161.203) by BL2FFO11HUB032.protection.gbl (10.173.161.56) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 10 Jun 2013 17:08:46 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD012.mail.protection.outlook.com (10.173.161.18) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 10 Jun 2013 17:08:46 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.03.0136.001; Mon, 10 Jun 2013 17:08:35 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5lnSf72X6a3Ku/SKOo5PcgVR4NIgAWmNmAAAAbQTAAAQYggAAAFDPg
Date: Mon, 10 Jun 2013 17:08:35 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com>
In-Reply-To: <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436781D714TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(24454002)(377454002)(199002)(81542001)(6806003)(51856001)(47976001)(76786001)(63696002)(33656001)(80022001)(66066001)(16236675002)(74876001)(79102001)(49866001)(31966008)(50986001)(44976003)(74706001)(20776003)(56816003)(16406001)(65816001)(76796001)(54316002)(47736001)(56776001)(53806001)(512954002)(4396001)(55846006)(77096001)(76482001)(47446002)(71186001)(74366001)(46102001)(15202345002)(81342001)(74502001)(561944002)(74662001)(77982001)(59766001)(54356001)(69226001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB032; H:TK5EX14HUBC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087396016C
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:08:54 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436781D714TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This would take us down the road to canonicalization.  How would you repres=
ent a CRLF in the value?  How would you represent a bare LF?  How would you=
 represent a tab?  Canonical representations for all of these, and more, wo=
uld have to be specified.

Using a special encoding for this field that is different than the encoding=
 used for all other fields (base64url encoding) is developer-hostile.  It f=
orces them to have (and test) special code to produce a different for this =
field alone.  This would undoubtedly result in interop problems, because th=
e corner cases almost never get tested (and often never get coded correctly=
 either).

We already have a simple means of ensuring the correct transmission of fiel=
ds.  Occam's Razor would suggest just using it.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Monday, June 10, 2013 10:01 AM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org
Subject: Re: [jose] Possible change to protected field

I think you've misunderstood the proposal.  It's not that the field will be=
 unencoded, it's that it will be encoded as a UTF-8 string instead of a bas=
e64 string.

OLD: (json) --> UTF-8 --> base64
NEW: (json) --> UTF-8

OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }
NEW: { protected: "{\"alg\":\"RS256\"}" }

Now, there might still be a problem with that, because JSON strings aren't =
canonical.  In the example above, the quote characters could also have been=
 presented as "\u0022".  So if some JSON re-processor were to change the en=
coding ot the string, it would break the signature.  However, that's also a=
 problem for the base64-encoded version ("a" vs. "\u0061").




On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
The problem with this suggested change is that it requires unencoded JSON o=
bjects to be transmitted with no transformations whatsoever, whereas the pr=
oblems with this assumption are well known.  For starters, on UNIX-based sy=
stems, newlines are typically represented by a bare LF character, whereas o=
n DOS-based systems, newlines are typically represented by a CRLF pair.  In=
 transmission, many systems, including mail agents tend to convert newlines=
 to the system's normal format.  This would break these JOSE objects.

Some agents wrap lines after a certain length.  Particularly when being tra=
nsmitted in HTML or XML, many systems replace two or more consecutive space=
s with a single space.  Others replace two or more spaces with a single spa=
ce and N-1 non-breaking space characters.  I could go on...

I appreciate the attempt to make things appear to be more uniform and reada=
ble, but the CRLF/LF problems alone are enough to make this a non-starter.

                                                                Best wishes=
,
                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Possible change to protected field

This sounds like a fine idea to me.  It saves space and makes the JSON form=
at more human-readable.  It actually makes kind of a nice analogy to ASN.1,=
 namely use of OCTET STRING to encapsulate more DER content.

The compact serialization can continue to base64url-encode that field, so i=
t would not be a breaking change for that serialization.

--Richard

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

I am trying to figure out if I am missing something.  This is not yet a for=
mal proposal to actual change the document.

I was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.  If we encoded this a=
s a UTF8 string rather than the base64url encoded UTF8 string, then the con=
tent would be smaller.  The computation of the signature would be unchanged=
 in that it would still be computed over the base64url encoded string.  I b=
elieve that the conversion from the UTF8 string to the base64url encoded UT=
F8 string is a deterministic encoding and thus would not generate any probl=
ems from that point.

At this point I and trying to figure out if I missed anything that would pr=
eclude this from working.  I am not worried about how hard or easy it would=
 be to do, just if it is even possible.

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B16804296739436781D714TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This would take us down t=
he road to canonicalization.&nbsp; How would you represent a CRLF in the va=
lue?&nbsp; How would you represent a bare LF?&nbsp; How would you represent
 a tab?&nbsp; Canonical representations for all of these, and more, would h=
ave to be specified.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Using a special encoding =
for this field that is different than the encoding used for all other field=
s (base64url encoding) is developer-hostile.&nbsp; It forces
 them to have (and test) special code to produce a different for this field=
 alone.&nbsp; This would undoubtedly result in interop problems, because th=
e corner cases almost never get tested (and often never get coded correctly=
 either).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We already have a simple =
means of ensuring the correct transmission of fields.&nbsp; Occam&#8217;s R=
azor would suggest just using it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I think you've misunderstood the proposal. &nbsp;It'=
s not that the field will be unencoded, it's that it will be encoded as a U=
TF-8 string instead of a base64 string.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: (json) --&gt; UTF-8 --&gt; base64<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal">NEW: (json) --&gt; UTF-8<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: &nbsp;{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=
=3D=3D&quot; }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS=
256\&quot;}&quot; }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Now, there might still be a problem with that, becau=
se JSON strings aren't canonical. &nbsp;In the example above, the quote cha=
racters could also have been presented as &quot;\u0022&quot;. &nbsp;So if s=
ome JSON re-processor were to change the encoding ot the
 string, it would break the signature. &nbsp;However, that's also a problem=
 for the base64-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The problem with this suggested change =
is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.&nbsp; For starters, on UNIX-based systems, newlines are=
 typically represented by a bare LF character, whereas on DOS-based systems=
, newlines are typically represented
 by a CRLF pair.&nbsp; In transmission, many systems, including mail agents=
 tend to convert newlines to the system&#8217;s normal format.&nbsp; This w=
ould break these JOSE objects.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Some agents wrap lines after a certain =
length.&nbsp; Particularly when being transmitted in HTML or XML,
 many systems replace two or more consecutive spaces with a single space.&n=
bsp; Others replace two or more spaces with a single space and N-1 non-brea=
king space characters.&nbsp; I could go on&#8230;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I appreciate the attempt to make things=
 appear to be more uniform and readable, but the CRLF/LF problems
 alone are enough to make this a non-starter.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><o:p></=
o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This sounds like a fine idea to me. &nbsp;It saves space and makes=
 the JSON format more human-readable. &nbsp;It actually makes kind of a nic=
e analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The compact serialization can continue to base64url-encode that fi=
eld, so it would not be a breaking change for that serialization.<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I am trying to figure out if I am missing something.&nbsp; This is=
 not yet a formal proposal to actual change the document.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was thinking about proposing that we make a change to the conten=
t of the protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. &nbs=
p;The computation of the signature would be unchanged in that it would stil=
l be computed over the base64url encoded string.&nbsp; I believe that the c=
onversion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">At this point I and trying to figure out if I missed anything that=
 would preclude this from working. &nbsp;I am not worried about how hard or=
 easy it would be to do, just if it is even
 possible.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436781D714TK5EX14MBXC283r_--

From ietf@augustcellars.com  Mon Jun 10 10:25:48 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798A021F94DC for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xf9Vsd-Afm7q for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:25:43 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id ABA9421F9690 for <jose@ietf.org>; Mon, 10 Jun 2013 10:25:43 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id D3DEB2CA29; Mon, 10 Jun 2013 10:25:42 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Richard Barnes'" <rlb@ipv.sx>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 10:24:50 -0700
Message-ID: <067701ce65ff$6a1d8b30$3e58a190$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0678_01CE65C4.BDC039D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG0QxNjNQen5xE7UI53mmuxyr9BfQI0cZ/ZAVlbblKZRwW1AA==
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:25:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0678_01CE65C4.BDC039D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Mike,

 

I can dispose of the CRLF question quite simply.  I have not removed the
UTF8 string from the protected field so all CRLF characters (along with a
number of others) will be escaped so they will not be transformed.

 

It would still be

 

{"protected":"---UTF8 encoded string ---"}

 

Rather than

 

{"protected":"--- Base64 URL encoded ( -- UTF8 encoded string  -- ) ---" }

 

There are a number of other questions that do come into play that you did
raise however.

 

The first would be space folding -  It has been my experience that this is
normally the XML parser that does it rather than things in transit.  There
will always be a problem with things in the middle that could possibly
change things with this approach.  It is something that I need to be looked
at and think about.

 

If we have a line wrapping issue, this is going to be a problem with JSON
parsers today.  It is not legal to have any of the CRLF characters inside of
a string in JSON according to the current ABNF in the document.  I think
this may already cause parsers to go boom in some cases.  If this is going
to be a real issue then we probably need to start dealing with it sooner
rather than later.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Monday, June 10, 2013 9:39 AM
To: Richard Barnes; Jim Schaad
Cc: jose@ietf.org
Subject: RE: [jose] Possible change to protected field

 

The problem with this suggested change is that it requires unencoded JSON
objects to be transmitted with no transformations whatsoever, whereas the
problems with this assumption are well known.  For starters, on UNIX-based
systems, newlines are typically represented by a bare LF character, whereas
on DOS-based systems, newlines are typically represented by a CRLF pair.  In
transmission, many systems, including mail agents tend to convert newlines
to the system's normal format.  This would break these JOSE objects.

 

Some agents wrap lines after a certain length.  Particularly when being
transmitted in HTML or XML, many systems replace two or more consecutive
spaces with a single space.  Others replace two or more spaces with a single
space and N-1 non-breaking space characters.  I could go on.

 

I appreciate the attempt to make things appear to be more uniform and
readable, but the CRLF/LF problems alone are enough to make this a
non-starter.

 

                                                                Best wishes,

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
Richard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Possible change to protected field

 

This sounds like a fine idea to me.  It saves space and makes the JSON
format more human-readable.  It actually makes kind of a nice analogy to
ASN.1, namely use of OCTET STRING to encapsulate more DER content.

 

The compact serialization can continue to base64url-encode that field, so it
would not be a breaking change for that serialization.

 

--Richard

 

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com> wrote:

<no hat>

 

I am trying to figure out if I am missing something.  This is not yet a
formal proposal to actual change the document.

 

I was thinking about proposing that we make a change to the content of the
protected field in the JWS JSON serialization format.  If we encoded this as
a UTF8 string rather than the base64url encoded UTF8 string, then the
content would be smaller.  The computation of the signature would be
unchanged in that it would still be computed over the base64url encoded
string.  I believe that the conversion from the UTF8 string to the base64url
encoded UTF8 string is a deterministic encoding and thus would not generate
any problems from that point.

 

At this point I and trying to figure out if I missed anything that would
preclude this from working.  I am not worried about how hard or easy it
would be to do, just if it is even possible.

 

Jim

 


_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

 


------=_NextPart_000_0678_01CE65C4.BDC039D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Mike,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I can dispose of the CRLF question quite simply.&nbsp; I have not =
removed the UTF8 string from the protected field so all CRLF characters =
(along with a number of others) will be escaped so they will not be =
transformed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>It would still be<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>{&#8220;protected&#8221;:&#8221;---UTF8 encoded string =
---&#8220;}<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Rather than<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>{&#8220;protected&#8221;:&#8221;--- Base64 URL encoded ( -- UTF8 =
encoded string&nbsp; -- ) ---&#8220; }<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There are a number of other questions that do come into play that you =
did raise however.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The first would be space folding -&nbsp; It has been my experience =
that this is normally the XML parser that does it rather than things in =
transit.&nbsp; There will always be a problem with things in the middle =
that could possibly change things with this approach. &nbsp;It is =
something that I need to be looked at and think =
about.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If we have a line wrapping issue, this is going to be a problem with =
JSON parsers today.&nbsp; It is not legal to have any of the CRLF =
characters inside of a string in JSON according to the current ABNF in =
the document. &nbsp;I think this may already cause parsers to go boom in =
some cases.&nbsp; If this is going to be a real issue then we probably =
need to start dealing with it sooner rather than =
later.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Monday, =
June 10, 2013 9:39 AM<br><b>To:</b> Richard Barnes; Jim =
Schaad<br><b>Cc:</b> jose@ietf.org<br><b>Subject:</b> RE: [jose] =
Possible change to protected field<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The problem with this suggested change is that it requires unencoded =
JSON objects to be transmitted with no transformations whatsoever, =
whereas the problems with this assumption are well known.&nbsp; For =
starters, on UNIX-based systems, newlines are typically represented by a =
bare LF character, whereas on DOS-based systems, newlines are typically =
represented by a CRLF pair.&nbsp; In transmission, many systems, =
including mail agents tend to convert newlines to the system&#8217;s =
normal format.&nbsp; This would break these JOSE =
objects.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Some agents wrap lines after a certain length.&nbsp; Particularly =
when being transmitted in HTML or XML, many systems replace two or more =
consecutive spaces with a single space.&nbsp; Others replace two or more =
spaces with a single space and N-1 non-breaking space characters.&nbsp; =
I could go on&#8230;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I appreciate the attempt to make things appear to be more uniform and =
readable, but the CRLF/LF problems alone are enough to make this a =
non-starter.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; Best wishes,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Richard Barnes<br><b>Sent:</b> Monday, June 10, 2013 =
9:29 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Possible change to protected field<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>This =
sounds like a fine idea to me. &nbsp;It saves space and makes the JSON =
format more human-readable. &nbsp;It actually makes kind of a nice =
analogy to ASN.1, namely use of OCTET STRING to encapsulate more DER =
content.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The compact serialization can continue to =
base64url-encode that field, so it would not be a breaking change for =
that serialization.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&lt;no =
hat&gt;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I am trying =
to figure out if I am missing something.&nbsp; This is not yet a formal =
proposal to actual change the document.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I was =
thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than the base64url encoded UTF8 =
string, then the content would be smaller. &nbsp;The computation of the =
signature would be unchanged in that it would still be computed over the =
base64url encoded string.&nbsp; I believe that the conversion from the =
UTF8 string to the base64url encoded UTF8 string is a deterministic =
encoding and thus would not generate any problems from that =
point.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>At this =
point I and trying to figure out if I missed anything that would =
preclude this from working. &nbsp;I am not worried about how hard or =
easy it would be to do, just if it is even possible.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>Jim<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>______________________________________=
_________<br>jose mailing list<br><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:=
p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0678_01CE65C4.BDC039D0--


From rlb@ipv.sx  Mon Jun 10 10:42:50 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD8721F8ECB for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.125
X-Spam-Level: 
X-Spam-Status: No, score=-0.125 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktq4s0LXnkqF for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:42:46 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id DD95121F8F85 for <jose@ietf.org>; Mon, 10 Jun 2013 10:42:45 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id ta17so10610765obb.36 for <jose@ietf.org>; Mon, 10 Jun 2013 10:42:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=xrkkgNbtPrfaCGe6B8h6PX1su2hhLJUd6+tJtl0X0/Y=; b=Z51rHV9O28ZMQVolfoeVU/83PnsUcwhLmKI3XAXdywUPaVXBV3pKmCqStaBh/rxyuC +OMAdLgjo8P5ivhK9JT8OnbotX3QEKaQDngAOEkd3Uwm5XRVkcZdHzQOMecSmmbV53T/ n7g7RLU1fEqS4k7XwADtVRdfHdp8/Bndr73obqSetcRwtf6ccdHKn1z1frpal80b83WI McP5o2IeVUGvohx4Lfo13Ksx4ytiVBMSf2z5Et1/B4H0kh3hJtSeWTAmNC2d2/8wFFSV AiIRpOjZMuBJ1Fq+DbFAxCW/tE+RzwYPqIQ44p56yK8zWqOYZjW9onoY0fYvIHFH+39A P/ZQ==
MIME-Version: 1.0
X-Received: by 10.182.39.133 with SMTP id p5mr5566841obk.69.1370886165046; Mon, 10 Jun 2013 10:42:45 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 10:42:44 -0700 (PDT)
X-Originating-IP: [192.1.255.206]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 13:42:44 -0400
Message-ID: <CAL02cgTv1nsWj0+0grco1WAN4jOvZkdhHq5inhGphv48zJujxQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2e804e58c5604ded04e8c
X-Gm-Message-State: ALoCoQnQV6x9ehaC67rgFE55J+NkSLRRNzQ/i6gCOm7OZE7riHpgd6jX5kcxw9Mxgyr5uKKawHEI
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:42:50 -0000

--001a11c2e804e58c5604ded04e8c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

It's not canonicalization, it's just UTF-8 serialization.  As to your
questions about CR / LF / tab, let us recall RFC 4627:

         char =3D unescaped /
                escape (
                    %x22 /          ; "    quotation mark  U+0022
                    %x5C /          ; \    reverse solidus U+005C
                    %x2F /          ; /    solidus         U+002F
                    %x62 /          ; b    backspace       U+0008
                    %x66 /          ; f    form feed       U+000C
                    %x6E /          ; n    line feed       U+000A
                    %x72 /          ; r    carriage return U+000D
                    %x74 /          ; t    tab             U+0009
                    %x75 4HEXDIG )  ; uXXXX                U+XXXX


Empirically, it appears that this serialization is stable with regard to
re-encoding, at least for browser JSON engines:
<http://www.ipv.sx/jose/json_test.html>

The only thing that would lead me to prefer this serialization against the
Occam's Razor argument is that it's more readable for someone that receives
a JOSE object.  Instead of staring at base64-encoded junk, you can actually
sort of see what's in there.  But I don't feel very strongly about this.

--Richard




On Mon, Jun 10, 2013 at 1:08 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  This would take us down the road to canonicalization.  How would you
> represent a CRLF in the value?  How would you represent a bare LF?  How
> would you represent a tab?  Canonical representations for all of these, a=
nd
> more, would have to be specified.****
>
> ** **
>
> Using a special encoding for this field that is different than the
> encoding used for all other fields (base64url encoding) is
> developer-hostile.  It forces them to have (and test) special code to
> produce a different for this field alone.  This would undoubtedly result =
in
> interop problems, because the corner cases almost never get tested (and
> often never get coded correctly either).****
>
> ** **
>
> We already have a simple means of ensuring the correct transmission of
> fields.  Occam=92s Razor would suggest just using it.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Monday, June 10, 2013 10:01 AM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org
>
> *Subject:* Re: [jose] Possible change to protected field****
>
> ** **
>
> I think you've misunderstood the proposal.  It's not that the field will
> be unencoded, it's that it will be encoded as a UTF-8 string instead of a
> base64 string.****
>
> ** **
>
> OLD: (json) --> UTF-8 --> base64****
>
> NEW: (json) --> UTF-8****
>
> ** **
>
> OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }****
>
> NEW: { protected: "{\"alg\":\"RS256\"}" }****
>
> ** **
>
> Now, there might still be a problem with that, because JSON strings aren'=
t
> canonical.  In the example above, the quote characters could also have be=
en
> presented as "\u0022".  So if some JSON re-processor were to change the
> encoding ot the string, it would break the signature.  However, that's al=
so
> a problem for the base64-encoded version ("a" vs. "\u0061").****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> The problem with this suggested change is that it requires unencoded JSON
> objects to be transmitted with no transformations whatsoever, whereas the
> problems with this assumption are well known.  For starters, on UNIX-base=
d
> systems, newlines are typically represented by a bare LF character, where=
as
> on DOS-based systems, newlines are typically represented by a CRLF pair.
> In transmission, many systems, including mail agents tend to convert
> newlines to the system=92s normal format.  This would break these JOSE
> objects.****
>
>  ****
>
> Some agents wrap lines after a certain length.  Particularly when being
> transmitted in HTML or XML, many systems replace two or more consecutive
> spaces with a single space.  Others replace two or more spaces with a
> single space and N-1 non-breaking space characters.  I could go on=85****
>
>  ****
>
> I appreciate the attempt to make things appear to be more uniform and
> readable, but the CRLF/LF problems alone are enough to make this a
> non-starter.****
>
>  ****
>
>                                                                 Best
> wishes,****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Monday, June 10, 2013 9:29 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
>  ****
>
> This sounds like a fine idea to me.  It saves space and makes the JSON
> format more human-readable.  It actually makes kind of a nice analogy to
> ASN.1, namely use of OCTET STRING to encapsulate more DER content.****
>
>  ****
>
> The compact serialization can continue to base64url-encode that field, so
> it would not be a breaking change for that serialization.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> I am trying to figure out if I am missing something.  This is not yet a
> formal proposal to actual change the document.****
>
>  ****
>
> I was thinking about proposing that we make a change to the content of th=
e
> protected field in the JWS JSON serialization format.  If we encoded this
> as a UTF8 string rather than the base64url encoded UTF8 string, then the
> content would be smaller.  The computation of the signature would be
> unchanged in that it would still be computed over the base64url encoded
> string.  I believe that the conversion from the UTF8 string to the
> base64url encoded UTF8 string is a deterministic encoding and thus would
> not generate any problems from that point.****
>
>  ****
>
> At this point I and trying to figure out if I missed anything that would
> preclude this from working.  I am not worried about how hard or easy it
> would be to do, just if it is even possible.****
>
>  ****
>
> Jim****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
> ** **
>

--001a11c2e804e58c5604ded04e8c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>It&#39;s not canonicalization, it&#39;s just UTF-8 se=
rialization. =A0As to your questions about CR / LF / tab, let us recall RFC=
 4627:</div><div><br></div><div><pre class=3D"" style=3D"font-size:1em;marg=
in-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
         char =3D unescaped /
                escape (
                    %x22 /          ; &quot;    quotation mark  U+0022
                    %x5C /          ; \    reverse solidus U+005C
                    %x2F /          ; /    solidus         U+002F
                    %x62 /          ; b    backspace       U+0008
                    %x66 /          ; f    form feed       U+000C
                    %x6E /          ; n    line feed       U+000A
                    %x72 /          ; r    carriage return U+000D
                    %x74 /          ; t    tab             U+0009
                    %x75 4HEXDIG )  ; uXXXX                U+XXXX</pre></di=
v><div><br></div><div>Empirically, it appears that this serialization is st=
able with regard to re-encoding, at least for browser JSON engines:</div>
<div>&lt;<a href=3D"http://www.ipv.sx/jose/json_test.html">http://www.ipv.s=
x/jose/json_test.html</a>&gt;</div><div><br></div><div>The only thing that =
would lead me to prefer this serialization against the Occam&#39;s Razor ar=
gument is that it&#39;s more readable for someone that receives a JOSE obje=
ct. =A0Instead of staring at base64-encoded junk, you can actually sort of =
see what&#39;s in there. =A0But I don&#39;t feel very strongly about this.<=
/div>
<div><br></div><div>--Richard</div><div><br></div><div><br></div></div><div=
 class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jun 10, 2=
013 at 1:08 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.=
Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">This would take us down t=
he road to canonicalization.=A0 How would you represent a CRLF in the value=
?=A0 How would you represent a bare LF?=A0 How would you represent
 a tab?=A0 Canonical representations for all of these, and more, would have=
 to be specified.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Using a special encoding =
for this field that is different than the encoding used for all other field=
s (base64url encoding) is developer-hostile.=A0 It forces
 them to have (and test) special code to produce a different for this field=
 alone.=A0 This would undoubtedly result in interop problems, because the c=
orner cases almost never get tested (and often never get coded correctly ei=
ther).<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">We already have a simple =
means of ensuring the correct transmission of fields.=A0 Occam=92s Razor wo=
uld suggest just using it.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] Possible change to protected field<u></u><u></u>=
</div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I think you&#39;ve misunderstood the proposal. =A0It=
&#39;s not that the field will be unencoded, it&#39;s that it will be encod=
ed as a UTF-8 string instead of a base64 string.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: (json) --&gt; UTF-8 --&gt; base64<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">NEW: (json) --&gt; UTF-8<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: =A0{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=
=3D&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS=
256\&quot;}&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, there might still be a problem with that, becau=
se JSON strings aren&#39;t canonical. =A0In the example above, the quote ch=
aracters could also have been presented as &quot;\u0022&quot;. =A0So if som=
e JSON re-processor were to change the encoding ot the
 string, it would break the signature. =A0However, that&#39;s also a proble=
m for the base64-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<u>=
</u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The problem with this sug=
gested change is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.=A0 For starters, on UNIX-based systems, newlines are ty=
pically represented by a bare LF character, whereas on DOS-based systems, n=
ewlines are typically represented
 by a CRLF pair.=A0 In transmission, many systems, including mail agents te=
nd to convert newlines to the system=92s normal format.=A0 This would break=
 these JOSE objects.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some agents wrap lines af=
ter a certain length.=A0 Particularly when being transmitted in HTML or XML=
,
 many systems replace two or more consecutive spaces with a single space.=
=A0 Others replace two or more spaces with a single space and N-1 non-break=
ing space characters.=A0 I could go on=85</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I appreciate the attempt =
to make things appear to be more uniform and readable, but the CRLF/LF prob=
lems
 alone are enough to make this a non-starter.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 Best wishes,</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><u></u>=
<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">This sounds like a fine idea to me. =A0It saves spac=
e and makes the JSON format more human-readable. =A0It actually makes kind =
of a nice analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The compact serialization can continue to base64url-=
encode that field, so it would not be a breaking change for that serializat=
ion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I am trying to figure out if I am missing something.=
=A0 This is not yet a formal proposal to actual change the document.<u></u>=
<u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I was thinking about proposing that we make a change=
 to the content of the protected field in the JWS JSON serialization format=
.=A0 If we encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. =A0T=
he computation of the signature would be unchanged in that it would still b=
e computed over the base64url encoded string.=A0 I believe that the convers=
ion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">At this point I and trying to figure out if I missed=
 anything that would preclude this from working. =A0I am not worried about =
how hard or easy it would be to do, just if it is even
 possible.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c2e804e58c5604ded04e8c--

From ietf@augustcellars.com  Mon Jun 10 10:53:14 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5AB721F9954 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id veIPjvDHDnbX for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 10:53:09 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id ACE5521F9950 for <jose@ietf.org>; Mon, 10 Jun 2013 10:53:02 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id EF67F38EFA; Mon, 10 Jun 2013 10:53:01 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Richard Barnes'" <rlb@ipv.sx>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>	<CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 10:52:09 -0700
Message-ID: <068101ce6603$3b27c440$b1774cc0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0682_01CE65C8.8ECDF550"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG0QxNjNQen5xE7UI53mmuxyr9BfQI0cZ/ZAVlbblICaXzKXgJtpxE3mSBVoqA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 17:53:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0682_01CE65C8.8ECDF550
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I don't understand why you think it takes us down the road to
canonicalization.  If there are canonization problems in this proposal I
would say that they may already exist.

 

I don't know if you are reading the JSON list or not, however you seem to be
confusing the encoded and the unencoded versions of the string.  The string
does need to be encoded into a format that is legal to place into a JSON
string field.  In that case there is a number of ways that it can be done
using quoting.  However when the JSON parser gives that string to the
application - it will be the original UTF8 encoded string.  This means that
a bare LF character would be the "code point" 10.  That is the UTF8 encoding
for a line feed character.  It does not get canonicalized in any way.  A
UTF8 string does have possible code points that are not legal in a JSON
string, but that is JSONs problem not ours.  The JSON string encoding format
is responsible for the string to text and text to string transformations and
making sure that those transformations are loss-less.

 

I agree that it may be harder to do, I have not formally presented this as a
change to the document and will not do so until I have done a full analysis
on how hard it is.  I am currently just trying to figure out if it is even
technically feasible.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Monday, June 10, 2013 10:09 AM
To: Richard Barnes
Cc: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Possible change to protected field

 

This would take us down the road to canonicalization.  How would you
represent a CRLF in the value?  How would you represent a bare LF?  How
would you represent a tab?  Canonical representations for all of these, and
more, would have to be specified.

 

Using a special encoding for this field that is different than the encoding
used for all other fields (base64url encoding) is developer-hostile.  It
forces them to have (and test) special code to produce a different for this
field alone.  This would undoubtedly result in interop problems, because the
corner cases almost never get tested (and often never get coded correctly
either).

 

We already have a simple means of ensuring the correct transmission of
fields.  Occam's Razor would suggest just using it.

 

                                                                -- Mike

 

From: Richard Barnes [mailto:rlb@ipv.sx] 
Sent: Monday, June 10, 2013 10:01 AM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org
Subject: Re: [jose] Possible change to protected field

 

I think you've misunderstood the proposal.  It's not that the field will be
unencoded, it's that it will be encoded as a UTF-8 string instead of a
base64 string.

 

OLD: (json) --> UTF-8 --> base64

NEW: (json) --> UTF-8

 

OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg==" }

NEW: { protected: "{\"alg\":\"RS256\"}" }

 

Now, there might still be a problem with that, because JSON strings aren't
canonical.  In the example above, the quote characters could also have been
presented as "\u0022".  So if some JSON re-processor were to change the
encoding ot the string, it would break the signature.  However, that's also
a problem for the base64-encoded version ("a" vs. "\u0061").

 

 

 

 

On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com>
wrote:

The problem with this suggested change is that it requires unencoded JSON
objects to be transmitted with no transformations whatsoever, whereas the
problems with this assumption are well known.  For starters, on UNIX-based
systems, newlines are typically represented by a bare LF character, whereas
on DOS-based systems, newlines are typically represented by a CRLF pair.  In
transmission, many systems, including mail agents tend to convert newlines
to the system's normal format.  This would break these JOSE objects.

 

Some agents wrap lines after a certain length.  Particularly when being
transmitted in HTML or XML, many systems replace two or more consecutive
spaces with a single space.  Others replace two or more spaces with a single
space and N-1 non-breaking space characters.  I could go on.

 

I appreciate the attempt to make things appear to be more uniform and
readable, but the CRLF/LF problems alone are enough to make this a
non-starter.

 

                                                                Best wishes,

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
Richard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Possible change to protected field

 

This sounds like a fine idea to me.  It saves space and makes the JSON
format more human-readable.  It actually makes kind of a nice analogy to
ASN.1, namely use of OCTET STRING to encapsulate more DER content.

 

The compact serialization can continue to base64url-encode that field, so it
would not be a breaking change for that serialization.

 

--Richard

 

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com> wrote:

<no hat>

 

I am trying to figure out if I am missing something.  This is not yet a
formal proposal to actual change the document.

 

I was thinking about proposing that we make a change to the content of the
protected field in the JWS JSON serialization format.  If we encoded this as
a UTF8 string rather than the base64url encoded UTF8 string, then the
content would be smaller.  The computation of the signature would be
unchanged in that it would still be computed over the base64url encoded
string.  I believe that the conversion from the UTF8 string to the base64url
encoded UTF8 string is a deterministic encoding and thus would not generate
any problems from that point.

 

At this point I and trying to figure out if I missed anything that would
preclude this from working.  I am not worried about how hard or easy it
would be to do, just if it is even possible.

 

Jim

 


_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

 

 


------=_NextPart_000_0682_01CE65C8.8ECDF550
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I don&#8217;t understand why you think it takes us down the road to =
canonicalization. &nbsp;If there are canonization problems in this =
proposal I would say that they may already =
exist.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I don&#8217;t know if you are reading the JSON list or not, however =
you seem to be confusing the encoded and the unencoded versions of the =
string.&nbsp; The string does need to be encoded into a format that is =
legal to place into a JSON string field.&nbsp; In that case there is a =
number of ways that it can be done using quoting.&nbsp; However when the =
JSON parser gives that string to the application &#8211; it will be the =
original UTF8 encoded string.&nbsp; This means that a bare LF character =
would be the &#8220;code point&#8221; 10.&nbsp; That is the UTF8 =
encoding for a line feed character.&nbsp; It does not get canonicalized =
in any way.&nbsp; A UTF8 string does have possible code points that are =
not legal in a JSON string, but that is JSONs problem not ours.&nbsp; =
The JSON string encoding format is responsible for the string to text =
and text to string transformations and making sure that those =
transformations are loss-less.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I agree that it may be harder to do, I have not formally presented =
this as a change to the document and will not do so until I have done a =
full analysis on how hard it is.&nbsp; I am currently just trying to =
figure out if it is even technically feasible.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Monday, =
June 10, 2013 10:09 AM<br><b>To:</b> Richard Barnes<br><b>Cc:</b> Jim =
Schaad; jose@ietf.org<br><b>Subject:</b> RE: [jose] Possible change to =
protected field<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This would take us down the road to canonicalization.&nbsp; How would =
you represent a CRLF in the value?&nbsp; How would you represent a bare =
LF?&nbsp; How would you represent a tab?&nbsp; Canonical representations =
for all of these, and more, would have to be =
specified.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Using a special encoding for this field that is different than the =
encoding used for all other fields (base64url encoding) is =
developer-hostile.&nbsp; It forces them to have (and test) special code =
to produce a different for this field alone.&nbsp; This would =
undoubtedly result in interop problems, because the corner cases almost =
never get tested (and often never get coded correctly =
either).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We already have a simple means of ensuring the correct transmission =
of fields.&nbsp; Occam&#8217;s Razor would suggest just using =
it.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [<a href=3D"mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>] =
<br><b>Sent:</b> Monday, June 10, 2013 10:01 AM<br><b>To:</b> Mike =
Jones<br><b>Cc:</b> Jim Schaad; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Possible change to protected field<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
you've misunderstood the proposal. &nbsp;It's not that the field will be =
unencoded, it's that it will be encoded as a UTF-8 string instead of a =
base64 string.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OLD: (json) --&gt; UTF-8 --&gt; =
base64<o:p></o:p></p></div><div><p class=3DMsoNormal>NEW: (json) --&gt; =
UTF-8<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OLD: &nbsp;{ protected: =
&quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=3D&quot; }<o:p></o:p></p></div><div><p =
class=3DMsoNormal>NEW: { protected: =
&quot;{\&quot;alg\&quot;:\&quot;RS256\&quot;}&quot; =
}<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Now, there might still be a problem with that, because =
JSON strings aren't canonical. &nbsp;In the example above, the quote =
characters could also have been presented as &quot;\u0022&quot;. =
&nbsp;So if some JSON re-processor were to change the encoding ot the =
string, it would break the signature. &nbsp;However, that's also a =
problem for the base64-encoded version (&quot;a&quot; vs. =
&quot;\u0061&quot;).<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The problem with this suggested change is that it requires unencoded =
JSON objects to be transmitted with no transformations whatsoever, =
whereas the problems with this assumption are well known.&nbsp; For =
starters, on UNIX-based systems, newlines are typically represented by a =
bare LF character, whereas on DOS-based systems, newlines are typically =
represented by a CRLF pair.&nbsp; In transmission, many systems, =
including mail agents tend to convert newlines to the system&#8217;s =
normal format.&nbsp; This would break these JOSE =
objects.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Some agents wrap lines after a certain length.&nbsp; Particularly =
when being transmitted in HTML or XML, many systems replace two or more =
consecutive spaces with a single space.&nbsp; Others replace two or more =
spaces with a single space and N-1 non-breaking space characters.&nbsp; =
I could go on&#8230;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I appreciate the attempt to make things appear to be more uniform and =
readable, but the CRLF/LF problems alone are enough to make this a =
non-starter.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; Best wishes,</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank">jose-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank">jose-bounces@ietf.org</a>] <b>On Behalf Of </b>Richard =
Barnes<br><b>Sent:</b> Monday, June 10, 2013 9:29 AM<br><b>To:</b> Jim =
Schaad<br><b>Cc:</b> <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: [jose] =
Possible change to protected field</span><o:p></o:p></p><div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This sounds =
like a fine idea to me. &nbsp;It saves space and makes the JSON format =
more human-readable. &nbsp;It actually makes kind of a nice analogy to =
ASN.1, namely use of OCTET STRING to encapsulate more DER =
content.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The compact =
serialization can continue to base64url-encode that field, so it would =
not be a breaking change for that =
serialization.<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--Richard<o:=
p></o:p></p></div></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p></o:p><=
/p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Jun =
10, 2013 at 1:46 AM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&lt;no =
hat&gt;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I am trying =
to figure out if I am missing something.&nbsp; This is not yet a formal =
proposal to actual change the document.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I was =
thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than the base64url encoded UTF8 =
string, then the content would be smaller. &nbsp;The computation of the =
signature would be unchanged in that it would still be computed over the =
base64url encoded string.&nbsp; I believe that the conversion from the =
UTF8 string to the base64url encoded UTF8 string is a deterministic =
encoding and thus would not generate any problems from that =
point.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>At this =
point I and trying to figure out if I missed anything that would =
preclude this from working. &nbsp;I am not worried about how hard or =
easy it would be to do, just if it is even possible.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>Jim</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>______________=
_________________________________<br>jose mailing list<br><a =
href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:=
p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></div></bo=
dy></html>
------=_NextPart_000_0682_01CE65C8.8ECDF550--


From Michael.Jones@microsoft.com  Mon Jun 10 13:25:15 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70EE21F99E9 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 13:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egQud9S9Df9a for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 13:25:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6C74621F8633 for <jose@ietf.org>; Mon, 10 Jun 2013 13:25:09 -0700 (PDT)
Received: from BY2FFO11FD027.protection.gbl (10.1.15.200) by BY2FFO11HUB033.protection.gbl (10.1.14.117) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 10 Jun 2013 20:25:08 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD027.mail.protection.outlook.com (10.1.15.216) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 10 Jun 2013 20:25:07 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Mon, 10 Jun 2013 20:25:07 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Richard Barnes' <rlb@ipv.sx>
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5lnSf72X6a3Ku/SKOo5PcgVR4NIgAWmNmAAAAbQTAAAQYggAAAFDPgAAG2KYAABP2qQA==
Date: Mon, 10 Jun 2013 20:25:06 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com>
In-Reply-To: <068101ce6603$3b27c440$b1774cc0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436781E496TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(377454002)(24454002)(51856001)(47446002)(47736001)(561944002)(44976003)(16406001)(54316002)(76796001)(63696002)(66066001)(31966008)(76786001)(50986001)(53806001)(80022001)(20776003)(74502001)(69226001)(59766001)(65816001)(79102001)(33656001)(76482001)(54356001)(49866001)(4396001)(74662001)(47976001)(15202345002)(71186001)(6806003)(81342001)(77096001)(81542001)(46102001)(74366001)(55846006)(16236675002)(74876001)(512954002)(74706001)(56816003)(56776001)(77982001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB033; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087396016C
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 20:25:15 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436781E496TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It's a form of canonicalization when you take one representation of a strin=
g and apply a set of rules to transform it to a more stable/transmissible s=
tring.  In this case, we'd be proposing that developers have to translate C=
RLF to \u000DU\u00A, and other similar canonicalization transformations.  T=
hat's a kind of canonicalization.  Worse, it's one that I don't believe the=
re's standard library support for, so developers would have to write it for=
 every implementation and platform.  They'd hate us, and with good reason.

And this isn't academic.  It's commonplace to use newlines in formatted JSO=
N, such as:

{"alg": "RSA-OAEP",
"enc": "A256GCM",
"kid": "7"
}

Occam's Razor suggests always using the same encoding when a stable, transm=
issible string representation is needed - in this case base64url encoding.

The somewhat improved readability of the canonicalization being discussed i=
sn't worth the interop problems or developer pain it would cost.  Therefore=
, I sincerely hope that no one actually proposes this.

                                                            -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Monday, June 10, 2013 10:52 AM
To: Mike Jones; 'Richard Barnes'
Cc: jose@ietf.org
Subject: RE: [jose] Possible change to protected field

I don't understand why you think it takes us down the road to canonicalizat=
ion.  If there are canonization problems in this proposal I would say that =
they may already exist.

I don't know if you are reading the JSON list or not, however you seem to b=
e confusing the encoded and the unencoded versions of the string.  The stri=
ng does need to be encoded into a format that is legal to place into a JSON=
 string field.  In that case there is a number of ways that it can be done =
using quoting.  However when the JSON parser gives that string to the appli=
cation - it will be the original UTF8 encoded string.  This means that a ba=
re LF character would be the "code point" 10.  That is the UTF8 encoding fo=
r a line feed character.  It does not get canonicalized in any way.  A UTF8=
 string does have possible code points that are not legal in a JSON string,=
 but that is JSONs problem not ours.  The JSON string encoding format is re=
sponsible for the string to text and text to string transformations and mak=
ing sure that those transformations are loss-less.

I agree that it may be harder to do, I have not formally presented this as =
a change to the document and will not do so until I have done a full analys=
is on how hard it is.  I am currently just trying to figure out if it is ev=
en technically feasible.

Jim


From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Monday, June 10, 2013 10:09 AM
To: Richard Barnes
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Possible change to protected field

This would take us down the road to canonicalization.  How would you repres=
ent a CRLF in the value?  How would you represent a bare LF?  How would you=
 represent a tab?  Canonical representations for all of these, and more, wo=
uld have to be specified.

Using a special encoding for this field that is different than the encoding=
 used for all other fields (base64url encoding) is developer-hostile.  It f=
orces them to have (and test) special code to produce a different for this =
field alone.  This would undoubtedly result in interop problems, because th=
e corner cases almost never get tested (and often never get coded correctly=
 either).

We already have a simple means of ensuring the correct transmission of fiel=
ds.  Occam's Razor would suggest just using it.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Monday, June 10, 2013 10:01 AM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Possible change to protected field

I think you've misunderstood the proposal.  It's not that the field will be=
 unencoded, it's that it will be encoded as a UTF-8 string instead of a bas=
e64 string.

OLD: (json) --> UTF-8 --> base64
NEW: (json) --> UTF-8

OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }
NEW: { protected: "{\"alg\":\"RS256\"}" }

Now, there might still be a problem with that, because JSON strings aren't =
canonical.  In the example above, the quote characters could also have been=
 presented as "\u0022".  So if some JSON re-processor were to change the en=
coding ot the string, it would break the signature.  However, that's also a=
 problem for the base64-encoded version ("a" vs. "\u0061").




On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
The problem with this suggested change is that it requires unencoded JSON o=
bjects to be transmitted with no transformations whatsoever, whereas the pr=
oblems with this assumption are well known.  For starters, on UNIX-based sy=
stems, newlines are typically represented by a bare LF character, whereas o=
n DOS-based systems, newlines are typically represented by a CRLF pair.  In=
 transmission, many systems, including mail agents tend to convert newlines=
 to the system's normal format.  This would break these JOSE objects.

Some agents wrap lines after a certain length.  Particularly when being tra=
nsmitted in HTML or XML, many systems replace two or more consecutive space=
s with a single space.  Others replace two or more spaces with a single spa=
ce and N-1 non-breaking space characters.  I could go on...

I appreciate the attempt to make things appear to be more uniform and reada=
ble, but the CRLF/LF problems alone are enough to make this a non-starter.

                                                                Best wishes=
,
                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Possible change to protected field

This sounds like a fine idea to me.  It saves space and makes the JSON form=
at more human-readable.  It actually makes kind of a nice analogy to ASN.1,=
 namely use of OCTET STRING to encapsulate more DER content.

The compact serialization can continue to base64url-encode that field, so i=
t would not be a breaking change for that serialization.

--Richard

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

I am trying to figure out if I am missing something.  This is not yet a for=
mal proposal to actual change the document.

I was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.  If we encoded this a=
s a UTF8 string rather than the base64url encoded UTF8 string, then the con=
tent would be smaller.  The computation of the signature would be unchanged=
 in that it would still be computed over the base64url encoded string.  I b=
elieve that the conversion from the UTF8 string to the base64url encoded UT=
F8 string is a deterministic encoding and thus would not generate any probl=
ems from that point.

At this point I and trying to figure out if I missed anything that would pr=
eclude this from working.  I am not worried about how hard or easy it would=
 be to do, just if it is even possible.

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B16804296739436781E496TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It&#8217;s a form of cano=
nicalization when you take one representation of a string and apply a set o=
f rules to transform it to a more stable/transmissible string.&nbsp;
 In this case, we&#8217;d be proposing that developers have to translate CR=
LF to \u000DU\u00A, and other similar canonicalization transformations.&nbs=
p; That&#8217;s a kind of canonicalization.&nbsp; Worse, it&#8217;s one tha=
t I don&#8217;t believe there&#8217;s standard library support for, so deve=
lopers
 would have to write it for every implementation and platform.&nbsp; They&#=
8217;d hate us, and with good reason.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">And this isn&#8217;t acad=
emic.&nbsp; It&#8217;s commonplace to use newlines in formatted JSON, such =
as:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">{&quot;alg&quot;: &quot;R=
SA-OAEP&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&quot;enc&quot;: &quot;A2=
56GCM&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&quot;kid&quot;: &quot;7&=
quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Occam&#8217;s Razor sugge=
sts always using the same encoding when a stable, transmissible string repr=
esentation is needed &#8211; in this case base64url encoding.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The somewhat improved rea=
dability of the canonicalization being discussed isn&#8217;t worth the inte=
rop problems or developer pain it would cost.&nbsp; Therefore, I sincerely
 hope that no one actually proposes this.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:52 AM<br>
<b>To:</b> Mike Jones; 'Richard Barnes'<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I don&#8217;t understand =
why you think it takes us down the road to canonicalization. &nbsp;If there=
 are canonization problems in this proposal I would say that they may
 already exist.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I don&#8217;t know if you=
 are reading the JSON list or not, however you seem to be confusing the enc=
oded and the unencoded versions of the string.&nbsp; The string does
 need to be encoded into a format that is legal to place into a JSON string=
 field.&nbsp; In that case there is a number of ways that it can be done us=
ing quoting.&nbsp; However when the JSON parser gives that string to the ap=
plication &#8211; it will be the original UTF8 encoded
 string.&nbsp; This means that a bare LF character would be the &#8220;code=
 point&#8221; 10.&nbsp; That is the UTF8 encoding for a line feed character=
.&nbsp; It does not get canonicalized in any way.&nbsp; A UTF8 string does =
have possible code points that are not legal in a JSON string, but
 that is JSONs problem not ours.&nbsp; The JSON string encoding format is r=
esponsible for the string to text and text to string transformations and ma=
king sure that those transformations are loss-less.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I agree that it may be ha=
rder to do, I have not formally presented this as a change to the document =
and will not do so until I have done a full analysis on
 how hard it is.&nbsp; I am currently just trying to figure out if it is ev=
en technically feasible.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:09 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><b=
r>
<b>Subject:</b> RE: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This would take us down t=
he road to canonicalization.&nbsp; How would you represent a CRLF in the va=
lue?&nbsp; How would you represent a bare LF?&nbsp; How would you represent
 a tab?&nbsp; Canonical representations for all of these, and more, would h=
ave to be specified.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Using a special encoding =
for this field that is different than the encoding used for all other field=
s (base64url encoding) is developer-hostile.&nbsp; It forces
 them to have (and test) special code to produce a different for this field=
 alone.&nbsp; This would undoubtedly result in interop problems, because th=
e corner cases almost never get tested (and often never get coded correctly=
 either).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We already have a simple =
means of ensuring the correct transmission of fields.&nbsp; Occam&#8217;s R=
azor would suggest just using it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><b=
r>
<b>Subject:</b> Re: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I think you've misunderstood the proposal. &nbsp;It'=
s not that the field will be unencoded, it's that it will be encoded as a U=
TF-8 string instead of a base64 string.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: (json) --&gt; UTF-8 --&gt; base64<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal">NEW: (json) --&gt; UTF-8<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: &nbsp;{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=
=3D=3D&quot; }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS=
256\&quot;}&quot; }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Now, there might still be a problem with that, becau=
se JSON strings aren't canonical. &nbsp;In the example above, the quote cha=
racters could also have been presented as &quot;\u0022&quot;. &nbsp;So if s=
ome JSON re-processor were to change the encoding ot the
 string, it would break the signature. &nbsp;However, that's also a problem=
 for the base64-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The problem with this suggested change =
is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.&nbsp; For starters, on UNIX-based systems, newlines are=
 typically represented by a bare LF character, whereas on DOS-based systems=
, newlines are typically represented
 by a CRLF pair.&nbsp; In transmission, many systems, including mail agents=
 tend to convert newlines to the system&#8217;s normal format.&nbsp; This w=
ould break these JOSE objects.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Some agents wrap lines after a certain =
length.&nbsp; Particularly when being transmitted in HTML or XML,
 many systems replace two or more consecutive spaces with a single space.&n=
bsp; Others replace two or more spaces with a single space and N-1 non-brea=
king space characters.&nbsp; I could go on&#8230;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I appreciate the attempt to make things=
 appear to be more uniform and readable, but the CRLF/LF problems
 alone are enough to make this a non-starter.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><o:p></=
o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This sounds like a fine idea to me. &nbsp;It saves space and makes=
 the JSON format more human-readable. &nbsp;It actually makes kind of a nic=
e analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The compact serialization can continue to base64url-encode that fi=
eld, so it would not be a breaking change for that serialization.<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I am trying to figure out if I am missing something.&nbsp; This is=
 not yet a formal proposal to actual change the document.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was thinking about proposing that we make a change to the conten=
t of the protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. &nbs=
p;The computation of the signature would be unchanged in that it would stil=
l be computed over the base64url encoded string.&nbsp; I believe that the c=
onversion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">At this point I and trying to figure out if I missed anything that=
 would preclude this from working. &nbsp;I am not worried about how hard or=
 easy it would be to do, just if it is even
 possible.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436781E496TK5EX14MBXC283r_--

From rlb@ipv.sx  Mon Jun 10 14:29:36 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5A7021F9A17 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 14:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.357
X-Spam-Level: *
X-Spam-Status: No, score=1.357 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kzBJjWK0RUjy for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 14:29:32 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9F27721F9A11 for <jose@ietf.org>; Mon, 10 Jun 2013 14:29:32 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wc20so10625689obb.4 for <jose@ietf.org>; Mon, 10 Jun 2013 14:29:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+JeKVcNpa7/aK6iMB/L4fCMb8yuqB+a/7kgHCqmnU6o=; b=ToLnsZFkLctU3rBsowxrO/TF0+CrgOPQG3Cnvj9ze/xF8A1q9hNCJb9w2gMUN7AYwG ohZ7LgswLd79ZgqNNaigB5TUFSkAdET+CnmtioHuW2ipNl8f2pqvPJao/IKuWEM9qGxK FR3LfbU1U3GXR1ZIBy8x/tCpmenRaeMlyJM5NuiC1TZJVsQp6x2UQRoqgCUtjzMhRz3t R4dYcFAP/KwEOwx77bwEh5y559O/y2SuB3NxR7voLiFk0lTuJ10464UUngDNQtox/Le5 WgCjI3wMFNBKuO4pOth8eg0T4l/Jmt4zRClqqoHGeUybxym50RQ9tRPGrn+nnHkZ3amk nULA==
MIME-Version: 1.0
X-Received: by 10.60.35.100 with SMTP id g4mr9703630oej.53.1370899771992; Mon, 10 Jun 2013 14:29:31 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 14:29:31 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 17:29:31 -0400
Message-ID: <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e013c68a0ef0ef804ded379a6
X-Gm-Message-State: ALoCoQm+vhALELzxvllU+IwH/qC92MFyUAXhyGCRCS181JYGo0enI17blCTBOyj1Wyieu0Ch1MPT
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 21:29:37 -0000

--089e013c68a0ef0ef804ded379a6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Mike: They already have to do that stuff before they base64-encode it.  All
Jim is talking about is *not* doing the base64.


On Mon, Jun 10, 2013 at 4:25 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  It=92s a form of canonicalization when you take one representation of a
> string and apply a set of rules to transform it to a more
> stable/transmissible string.  In this case, we=92d be proposing that
> developers have to translate CRLF to \u000DU\u00A, and other similar
> canonicalization transformations.  That=92s a kind of canonicalization.
> Worse, it=92s one that I don=92t believe there=92s standard library suppo=
rt for,
> so developers would have to write it for every implementation and
> platform.  They=92d hate us, and with good reason.****
>
> ** **
>
> And this isn=92t academic.  It=92s commonplace to use newlines in formatt=
ed
> JSON, such as:****
>
> ** **
>
> {"alg": "RSA-OAEP",****
>
> "enc": "A256GCM",****
>
> "kid": "7"****
>
> }****
>
> ** **
>
> Occam=92s Razor suggests always using the same encoding when a stable,
> transmissible string representation is needed =96 in this case base64url
> encoding.****
>
> ** **
>
> The somewhat improved readability of the canonicalization being discussed
> isn=92t worth the interop problems or developer pain it would cost.
> Therefore, I sincerely hope that no one actually proposes this.****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* Jim Schaad [mailto:ietf@augustcellars.com]
> *Sent:* Monday, June 10, 2013 10:52 AM
> *To:* Mike Jones; 'Richard Barnes'
> *Cc:* jose@ietf.org
>
> *Subject:* RE: [jose] Possible change to protected field****
>
>  ** **
>
> I don=92t understand why you think it takes us down the road to
> canonicalization.  If there are canonization problems in this proposal I
> would say that they may already exist.****
>
> ** **
>
> I don=92t know if you are reading the JSON list or not, however you seem =
to
> be confusing the encoded and the unencoded versions of the string.  The
> string does need to be encoded into a format that is legal to place into =
a
> JSON string field.  In that case there is a number of ways that it can be
> done using quoting.  However when the JSON parser gives that string to th=
e
> application =96 it will be the original UTF8 encoded string.  This means =
that
> a bare LF character would be the =93code point=94 10.  That is the UTF8
> encoding for a line feed character.  It does not get canonicalized in any
> way.  A UTF8 string does have possible code points that are not legal in =
a
> JSON string, but that is JSONs problem not ours.  The JSON string encodin=
g
> format is responsible for the string to text and text to string
> transformations and making sure that those transformations are loss-less.=
*
> ***
>
> ** **
>
> I agree that it may be harder to do, I have not formally presented this a=
s
> a change to the document and will not do so until I have done a full
> analysis on how hard it is.  I am currently just trying to figure out if =
it
> is even technically feasible.****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* Mike Jones [mailto:Michael.Jones@microsoft.com<Michael.Jones@micr=
osoft.com>]
>
> *Sent:* Monday, June 10, 2013 10:09 AM
> *To:* Richard Barnes
> *Cc:* Jim Schaad; jose@ietf.org
> *Subject:* RE: [jose] Possible change to protected field****
>
> ** **
>
> This would take us down the road to canonicalization.  How would you
> represent a CRLF in the value?  How would you represent a bare LF?  How
> would you represent a tab?  Canonical representations for all of these, a=
nd
> more, would have to be specified.****
>
> ** **
>
> Using a special encoding for this field that is different than the
> encoding used for all other fields (base64url encoding) is
> developer-hostile.  It forces them to have (and test) special code to
> produce a different for this field alone.  This would undoubtedly result =
in
> interop problems, because the corner cases almost never get tested (and
> often never get coded correctly either).****
>
> ** **
>
> We already have a simple means of ensuring the correct transmission of
> fields.  Occam=92s Razor would suggest just using it.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Monday, June 10, 2013 10:01 AM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
> ** **
>
> I think you've misunderstood the proposal.  It's not that the field will
> be unencoded, it's that it will be encoded as a UTF-8 string instead of a
> base64 string.****
>
> ** **
>
> OLD: (json) --> UTF-8 --> base64****
>
> NEW: (json) --> UTF-8****
>
> ** **
>
> OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }****
>
> NEW: { protected: "{\"alg\":\"RS256\"}" }****
>
> ** **
>
> Now, there might still be a problem with that, because JSON strings aren'=
t
> canonical.  In the example above, the quote characters could also have be=
en
> presented as "\u0022".  So if some JSON re-processor were to change the
> encoding ot the string, it would break the signature.  However, that's al=
so
> a problem for the base64-encoded version ("a" vs. "\u0061").****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> The problem with this suggested change is that it requires unencoded JSON
> objects to be transmitted with no transformations whatsoever, whereas the
> problems with this assumption are well known.  For starters, on UNIX-base=
d
> systems, newlines are typically represented by a bare LF character, where=
as
> on DOS-based systems, newlines are typically represented by a CRLF pair.
> In transmission, many systems, including mail agents tend to convert
> newlines to the system=92s normal format.  This would break these JOSE
> objects.****
>
>  ****
>
> Some agents wrap lines after a certain length.  Particularly when being
> transmitted in HTML or XML, many systems replace two or more consecutive
> spaces with a single space.  Others replace two or more spaces with a
> single space and N-1 non-breaking space characters.  I could go on=85****
>
>  ****
>
> I appreciate the attempt to make things appear to be more uniform and
> readable, but the CRLF/LF problems alone are enough to make this a
> non-starter.****
>
>  ****
>
>                                                                 Best
> wishes,****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Monday, June 10, 2013 9:29 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
>  ****
>
> This sounds like a fine idea to me.  It saves space and makes the JSON
> format more human-readable.  It actually makes kind of a nice analogy to
> ASN.1, namely use of OCTET STRING to encapsulate more DER content.****
>
>  ****
>
> The compact serialization can continue to base64url-encode that field, so
> it would not be a breaking change for that serialization.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> I am trying to figure out if I am missing something.  This is not yet a
> formal proposal to actual change the document.****
>
>  ****
>
> I was thinking about proposing that we make a change to the content of th=
e
> protected field in the JWS JSON serialization format.  If we encoded this
> as a UTF8 string rather than the base64url encoded UTF8 string, then the
> content would be smaller.  The computation of the signature would be
> unchanged in that it would still be computed over the base64url encoded
> string.  I believe that the conversion from the UTF8 string to the
> base64url encoded UTF8 string is a deterministic encoding and thus would
> not generate any problems from that point.****
>
>  ****
>
> At this point I and trying to figure out if I missed anything that would
> preclude this from working.  I am not worried about how hard or easy it
> would be to do, just if it is even possible.****
>
>  ****
>
> Jim****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
> ** **
>

--089e013c68a0ef0ef804ded379a6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Mike: They already have to do that stuff before they base6=
4-encode it. =A0All Jim is talking about is *not* doing the base64.</div><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jun 10,=
 2013 at 4:25 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michae=
l.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s a form of canonica=
lization when you take one representation of a string and apply a set of ru=
les to transform it to a more stable/transmissible string.=A0
 In this case, we=92d be proposing that developers have to translate CRLF t=
o \u000DU\u00A, and other similar canonicalization transformations.=A0 That=
=92s a kind of canonicalization.=A0 Worse, it=92s one that I don=92t believ=
e there=92s standard library support for, so developers
 would have to write it for every implementation and platform.=A0 They=92d =
hate us, and with good reason.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">And this isn=92t academic=
.=A0 It=92s commonplace to use newlines in formatted JSON, such as:<u></u><=
u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">{&quot;alg&quot;: &quot;R=
SA-OAEP&quot;,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&quot;enc&quot;: &quot;A2=
56GCM&quot;,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&quot;kid&quot;: &quot;7&=
quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">}<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Occam=92s Razor suggests =
always using the same encoding when a stable, transmissible string represen=
tation is needed =96 in this case base64url encoding.<u></u><u></u></span><=
/p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The somewhat improved rea=
dability of the canonicalization being discussed isn=92t worth the interop =
problems or developer pain it would cost.=A0 Therefore, I sincerely
 hope that no one actually proposes this.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf=
@augustcellars.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:52 AM<br>
<b>To:</b> Mike Jones; &#39;Richard Barnes&#39;<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span></p><div><div class=3D"h5"><br>
<b>Subject:</b> RE: [jose] Possible change to protected field<u></u><u></u>=
</div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I don=92t understand why =
you think it takes us down the road to canonicalization. =A0If there are ca=
nonization problems in this proposal I would say that they may
 already exist.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I don=92t know if you are=
 reading the JSON list or not, however you seem to be confusing the encoded=
 and the unencoded versions of the string.=A0 The string does
 need to be encoded into a format that is legal to place into a JSON string=
 field.=A0 In that case there is a number of ways that it can be done using=
 quoting.=A0 However when the JSON parser gives that string to the applicat=
ion =96 it will be the original UTF8 encoded
 string.=A0 This means that a bare LF character would be the =93code point=
=94 10.=A0 That is the UTF8 encoding for a line feed character.=A0 It does =
not get canonicalized in any way.=A0 A UTF8 string does have possible code =
points that are not legal in a JSON string, but
 that is JSONs problem not ours.=A0 The JSON string encoding format is resp=
onsible for the string to text and text to string transformations and makin=
g sure that those transformations are loss-less.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I agree that it may be ha=
rder to do, I have not formally presented this as a change to the document =
and will not do so until I have done a full analysis on
 how hard it is.=A0 I am currently just trying to figure out if it is even =
technically feasible.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">mailto=
:Michael.Jones@microsoft.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:09 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> RE: [jose] Possible change to protected field<u></u><u></u>=
</span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">This would take us down t=
he road to canonicalization.=A0 How would you represent a CRLF in the value=
?=A0 How would you represent a bare LF?=A0 How would you represent
 a tab?=A0 Canonical representations for all of these, and more, would have=
 to be specified.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Using a special encoding =
for this field that is different than the encoding used for all other field=
s (base64url encoding) is developer-hostile.=A0 It forces
 them to have (and test) special code to produce a different for this field=
 alone.=A0 This would undoubtedly result in interop problems, because the c=
orner cases almost never get tested (and often never get coded correctly ei=
ther).<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">We already have a simple =
means of ensuring the correct transmission of fields.=A0 Occam=92s Razor wo=
uld suggest just using it.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I think you&#39;ve misunderstood the proposal. =A0It=
&#39;s not that the field will be unencoded, it&#39;s that it will be encod=
ed as a UTF-8 string instead of a base64 string.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: (json) --&gt; UTF-8 --&gt; base64<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">NEW: (json) --&gt; UTF-8<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: =A0{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=
=3D&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS=
256\&quot;}&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, there might still be a problem with that, becau=
se JSON strings aren&#39;t canonical. =A0In the example above, the quote ch=
aracters could also have been presented as &quot;\u0022&quot;. =A0So if som=
e JSON re-processor were to change the encoding ot the
 string, it would break the signature. =A0However, that&#39;s also a proble=
m for the base64-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<u>=
</u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The problem with this sug=
gested change is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.=A0 For starters, on UNIX-based systems, newlines are ty=
pically represented by a bare LF character, whereas on DOS-based systems, n=
ewlines are typically represented
 by a CRLF pair.=A0 In transmission, many systems, including mail agents te=
nd to convert newlines to the system=92s normal format.=A0 This would break=
 these JOSE objects.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some agents wrap lines af=
ter a certain length.=A0 Particularly when being transmitted in HTML or XML=
,
 many systems replace two or more consecutive spaces with a single space.=
=A0 Others replace two or more spaces with a single space and N-1 non-break=
ing space characters.=A0 I could go on=85</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I appreciate the attempt =
to make things appear to be more uniform and readable, but the CRLF/LF prob=
lems
 alone are enough to make this a non-starter.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 Best wishes,</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><u></u>=
<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">This sounds like a fine idea to me. =A0It saves spac=
e and makes the JSON format more human-readable. =A0It actually makes kind =
of a nice analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The compact serialization can continue to base64url-=
encode that field, so it would not be a breaking change for that serializat=
ion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I am trying to figure out if I am missing something.=
=A0 This is not yet a formal proposal to actual change the document.<u></u>=
<u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I was thinking about proposing that we make a change=
 to the content of the protected field in the JWS JSON serialization format=
.=A0 If we encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. =A0T=
he computation of the signature would be unchanged in that it would still b=
e computed over the base64url encoded string.=A0 I believe that the convers=
ion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">At this point I and trying to figure out if I missed=
 anything that would preclude this from working. =A0I am not worried about =
how hard or easy it would be to do, just if it is even
 possible.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--089e013c68a0ef0ef804ded379a6--

From Michael.Jones@microsoft.com  Mon Jun 10 14:36:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD7A21F9A13 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 14:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7EO48XDJB5O for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 14:36:20 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id 662CA21F9A29 for <jose@ietf.org>; Mon, 10 Jun 2013 14:36:19 -0700 (PDT)
Received: from BL2FFO11FD006.protection.gbl (10.173.161.203) by BL2FFO11HUB032.protection.gbl (10.173.161.56) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 10 Jun 2013 21:36:16 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD006.mail.protection.outlook.com (10.173.161.2) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 10 Jun 2013 21:36:16 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Mon, 10 Jun 2013 21:36:03 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5lnSf72X6a3Ku/SKOo5PcgVR4NIgAWmNmAAAAbQTAAAQYggAAAFDPgAAG2KYAABP2qQAACmb+AAAAGo1A=
Date: Mon, 10 Jun 2013 21:36:03 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com>
In-Reply-To: <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436781EE0BTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(377454002)(189002)(24454002)(55846006)(4396001)(512954002)(77096001)(76482001)(53806001)(65816001)(56776001)(47736001)(76796001)(54316002)(69226001)(77982001)(46102001)(54356001)(561944002)(47446002)(15202345002)(74366001)(74502001)(74662001)(81342001)(59766001)(33656001)(63696002)(76786001)(66066001)(74876001)(80022001)(16236675002)(71186001)(81542001)(6806003)(47976001)(50986001)(44976003)(56816003)(20776003)(16406001)(74706001)(49866001)(51856001)(79102001)(31966008); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB032; H:TK5EX14HUBC106.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087396016C
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 21:36:25 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436781EE0BTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

My point is that if you just base64url encode the string - line the one bel=
ow - CRLFs and all, you don't have to do any of the canonicalization steps =
to make the representation JSON-string-safe in the first place.  And you're=
 using the same tool you're already using for encoding every other piece of=
 binary content that needs to be encoded in some way for JOSE.

Otherwise, we also still have to worry about "innocuous" transformations th=
at might during transport like space to non-breaking-space, tab to spaces, =
spaces being added at the end of lines (which HTML mail transports are noto=
rious for), etc.

If we apply the KISS principle and use the same encoding in this case that =
we do in all other cases, we don't have to even consider whether those and =
other content integrity threats that we may not have even thought of are go=
ing to hurt anyone in practice, because they can never arise.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Monday, June 10, 2013 2:30 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org
Subject: Re: [jose] Possible change to protected field

Mike: They already have to do that stuff before they base64-encode it.  All=
 Jim is talking about is *not* doing the base64.

On Mon, Jun 10, 2013 at 4:25 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
It's a form of canonicalization when you take one representation of a strin=
g and apply a set of rules to transform it to a more stable/transmissible s=
tring.  In this case, we'd be proposing that developers have to translate C=
RLF to \u000DU\u00A, and other similar canonicalization transformations.  T=
hat's a kind of canonicalization.  Worse, it's one that I don't believe the=
re's standard library support for, so developers would have to write it for=
 every implementation and platform.  They'd hate us, and with good reason.

And this isn't academic.  It's commonplace to use newlines in formatted JSO=
N, such as:

{"alg": "RSA-OAEP",
"enc": "A256GCM",
"kid": "7"
}

Occam's Razor suggests always using the same encoding when a stable, transm=
issible string representation is needed - in this case base64url encoding.

The somewhat improved readability of the canonicalization being discussed i=
sn't worth the interop problems or developer pain it would cost.  Therefore=
, I sincerely hope that no one actually proposes this.

                                                            -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com<mailto:ietf@augustcellars.c=
om>]
Sent: Monday, June 10, 2013 10:52 AM
To: Mike Jones; 'Richard Barnes'
Cc: jose@ietf.org<mailto:jose@ietf.org>

Subject: RE: [jose] Possible change to protected field

I don't understand why you think it takes us down the road to canonicalizat=
ion.  If there are canonization problems in this proposal I would say that =
they may already exist.

I don't know if you are reading the JSON list or not, however you seem to b=
e confusing the encoded and the unencoded versions of the string.  The stri=
ng does need to be encoded into a format that is legal to place into a JSON=
 string field.  In that case there is a number of ways that it can be done =
using quoting.  However when the JSON parser gives that string to the appli=
cation - it will be the original UTF8 encoded string.  This means that a ba=
re LF character would be the "code point" 10.  That is the UTF8 encoding fo=
r a line feed character.  It does not get canonicalized in any way.  A UTF8=
 string does have possible code points that are not legal in a JSON string,=
 but that is JSONs problem not ours.  The JSON string encoding format is re=
sponsible for the string to text and text to string transformations and mak=
ing sure that those transformations are loss-less.

I agree that it may be harder to do, I have not formally presented this as =
a change to the document and will not do so until I have done a full analys=
is on how hard it is.  I am currently just trying to figure out if it is ev=
en technically feasible.

Jim


From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Monday, June 10, 2013 10:09 AM
To: Richard Barnes
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Possible change to protected field

This would take us down the road to canonicalization.  How would you repres=
ent a CRLF in the value?  How would you represent a bare LF?  How would you=
 represent a tab?  Canonical representations for all of these, and more, wo=
uld have to be specified.

Using a special encoding for this field that is different than the encoding=
 used for all other fields (base64url encoding) is developer-hostile.  It f=
orces them to have (and test) special code to produce a different for this =
field alone.  This would undoubtedly result in interop problems, because th=
e corner cases almost never get tested (and often never get coded correctly=
 either).

We already have a simple means of ensuring the correct transmission of fiel=
ds.  Occam's Razor would suggest just using it.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Monday, June 10, 2013 10:01 AM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Possible change to protected field

I think you've misunderstood the proposal.  It's not that the field will be=
 unencoded, it's that it will be encoded as a UTF-8 string instead of a bas=
e64 string.

OLD: (json) --> UTF-8 --> base64
NEW: (json) --> UTF-8

OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }
NEW: { protected: "{\"alg\":\"RS256\"}" }

Now, there might still be a problem with that, because JSON strings aren't =
canonical.  In the example above, the quote characters could also have been=
 presented as "\u0022".  So if some JSON re-processor were to change the en=
coding ot the string, it would break the signature.  However, that's also a=
 problem for the base64-encoded version ("a" vs. "\u0061").




On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
The problem with this suggested change is that it requires unencoded JSON o=
bjects to be transmitted with no transformations whatsoever, whereas the pr=
oblems with this assumption are well known.  For starters, on UNIX-based sy=
stems, newlines are typically represented by a bare LF character, whereas o=
n DOS-based systems, newlines are typically represented by a CRLF pair.  In=
 transmission, many systems, including mail agents tend to convert newlines=
 to the system's normal format.  This would break these JOSE objects.

Some agents wrap lines after a certain length.  Particularly when being tra=
nsmitted in HTML or XML, many systems replace two or more consecutive space=
s with a single space.  Others replace two or more spaces with a single spa=
ce and N-1 non-breaking space characters.  I could go on...

I appreciate the attempt to make things appear to be more uniform and reada=
ble, but the CRLF/LF problems alone are enough to make this a non-starter.

                                                                Best wishes=
,
                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Monday, June 10, 2013 9:29 AM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Possible change to protected field

This sounds like a fine idea to me.  It saves space and makes the JSON form=
at more human-readable.  It actually makes kind of a nice analogy to ASN.1,=
 namely use of OCTET STRING to encapsulate more DER content.

The compact serialization can continue to base64url-encode that field, so i=
t would not be a breaking change for that serialization.

--Richard

On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

I am trying to figure out if I am missing something.  This is not yet a for=
mal proposal to actual change the document.

I was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.  If we encoded this a=
s a UTF8 string rather than the base64url encoded UTF8 string, then the con=
tent would be smaller.  The computation of the signature would be unchanged=
 in that it would still be computed over the base64url encoded string.  I b=
elieve that the conversion from the UTF8 string to the base64url encoded UT=
F8 string is a deterministic encoding and thus would not generate any probl=
ems from that point.

At this point I and trying to figure out if I missed anything that would pr=
eclude this from working.  I am not worried about how hard or easy it would=
 be to do, just if it is even possible.

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose




--_000_4E1F6AAD24975D4BA5B16804296739436781EE0BTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">My point is that if you j=
ust base64url encode the string &#8211; line the one below &#8211; CRLFs an=
d all, you don&#8217;t have to do any of the canonicalization steps to make
 the representation JSON-string-safe in the first place.&nbsp; And you&#821=
7;re using the same tool you&#8217;re already using for encoding every othe=
r piece of binary content that needs to be encoded in some way for JOSE.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Otherwise, we also still =
have to worry about &#8220;innocuous&#8221; transformations that might duri=
ng transport like space to non-breaking-space, tab to spaces, spaces
 being added at the end of lines (which HTML mail transports are notorious =
for), etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If we apply the KISS prin=
ciple and use the same encoding in this case that we do in all other cases,=
 we don&#8217;t have to even consider whether those and other
 content integrity threats that we may not have even thought of are going t=
o hurt anyone in practice, because they can never arise.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Monday, June 10, 2013 2:30 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Possible change to protected field<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Mike: They already have to do that stuff before they=
 base64-encode it. &nbsp;All Jim is talking about is *not* doing the base64=
.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 4:25 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">It&#8217;s a form of canonicalization w=
hen you take one representation of a string and apply a set of rules
 to transform it to a more stable/transmissible string.&nbsp; In this case,=
 we&#8217;d be proposing that developers have to translate CRLF to \u000DU\=
u00A, and other similar canonicalization transformations.&nbsp; That&#8217;=
s a kind of canonicalization.&nbsp; Worse, it&#8217;s one that I
 don&#8217;t believe there&#8217;s standard library support for, so develop=
ers would have to write it for every implementation and platform.&nbsp; The=
y&#8217;d hate us, and with good reason.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">And this isn&#8217;t academic.&nbsp; It=
&#8217;s commonplace to use newlines in formatted JSON, such as:</span><o:p=
></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">{&quot;alg&quot;: &quot;RSA-OAEP&quot;,=
</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&quot;enc&quot;: &quot;A256GCM&quot;,</=
span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&quot;kid&quot;: &quot;7&quot;</span><o=
:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">}</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Occam&#8217;s Razor suggests always usi=
ng the same encoding when a stable, transmissible string representation
 is needed &#8211; in this case base64url encoding.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The somewhat improved readability of th=
e canonicalization being discussed isn&#8217;t worth the interop
 problems or developer pain it would cost.&nbsp; Therefore, I sincerely hop=
e that no one actually proposes this.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Schaad [mailto:<a =
href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars=
.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:52 AM<br>
<b>To:</b> Mike Jones; 'Richard Barnes'<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> RE: [jose] Possible change to protected field<o:p></o:p></p=
>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I don&#8217;t understand why you think =
it takes us down the road to canonicalization. &nbsp;If there are canonizat=
ion
 problems in this proposal I would say that they may already exist.</span><=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I don&#8217;t know if you are reading t=
he JSON list or not, however you seem to be confusing the encoded
 and the unencoded versions of the string.&nbsp; The string does need to be=
 encoded into a format that is legal to place into a JSON string field.&nbs=
p; In that case there is a number of ways that it can be done using quoting=
.&nbsp; However when the JSON parser gives that
 string to the application &#8211; it will be the original UTF8 encoded str=
ing.&nbsp; This means that a bare LF character would be the &#8220;code poi=
nt&#8221; 10.&nbsp; That is the UTF8 encoding for a line feed character.&nb=
sp; It does not get canonicalized in any way.&nbsp; A UTF8 string does
 have possible code points that are not legal in a JSON string, but that is=
 JSONs problem not ours.&nbsp; The JSON string encoding format is responsib=
le for the string to text and text to string transformations and making sur=
e that those transformations are loss-less.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I agree that it may be harder to do, I =
have not formally presented this as a change to the document
 and will not do so until I have done a full analysis on how hard it is.&nb=
sp; I am currently just trying to figure out if it is even technically feas=
ible.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jones [<a href=3D=
"mailto:Michael.Jones@microsoft.com" target=3D"_blank">mailto:Michael.Jones=
@microsoft.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:09 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> RE: [jose] Possible change to protected field</span><o:p></=
o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">This would take us down the road to can=
onicalization.&nbsp; How would you represent a CRLF in the value?&nbsp;
 How would you represent a bare LF?&nbsp; How would you represent a tab?&nb=
sp; Canonical representations for all of these, and more, would have to be =
specified.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Using a special encoding for this field=
 that is different than the encoding used for all other fields
 (base64url encoding) is developer-hostile.&nbsp; It forces them to have (a=
nd test) special code to produce a different for this field alone.&nbsp; Th=
is would undoubtedly result in interop problems, because the corner cases a=
lmost never get tested (and often never get
 coded correctly either).</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">We already have a simple means of ensur=
ing the correct transmission of fields.&nbsp; Occam&#8217;s Razor would
 suggest just using it.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [<a hre=
f=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><o:p></=
o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I think you've misunderstood the proposal. &nbsp;It's not that the=
 field will be unencoded, it's that it will be encoded as a UTF-8 string in=
stead of a base64 string.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">OLD: (json) --&gt; UTF-8 --&gt; base64<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">NEW: (json) --&gt; UTF-8<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">OLD: &nbsp;{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=3D&quot; }=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS256\&quot;}&qu=
ot; }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Now, there might still be a problem with that, because JSON string=
s aren't canonical. &nbsp;In the example above, the quote characters could =
also have been presented as &quot;\u0022&quot;. &nbsp;So
 if some JSON re-processor were to change the encoding ot the string, it wo=
uld break the signature. &nbsp;However, that's also a problem for the base6=
4-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a href=3D"mailto=
:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The problem with this suggested change =
is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.&nbsp; For starters, on UNIX-based systems, newlines are=
 typically represented by a bare LF character, whereas on DOS-based systems=
, newlines are typically represented
 by a CRLF pair.&nbsp; In transmission, many systems, including mail agents=
 tend to convert newlines to the system&#8217;s normal format.&nbsp; This w=
ould break these JOSE objects.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Some agents wrap lines after a certain =
length.&nbsp; Particularly when being transmitted in HTML or XML,
 many systems replace two or more consecutive spaces with a single space.&n=
bsp; Others replace two or more spaces with a single space and N-1 non-brea=
king space characters.&nbsp; I could go on&#8230;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I appreciate the attempt to make things=
 appear to be more uniform and readable, but the CRLF/LF problems
 alone are enough to make this a non-starter.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best wishes,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><o:p></=
o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This sounds like a fine idea to me. &nbsp;It saves space and makes=
 the JSON format more human-readable. &nbsp;It actually makes kind of a nic=
e analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The compact serialization can continue to base64url-encode that fi=
eld, so it would not be a breaking change for that serialization.<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I am trying to figure out if I am missing something.&nbsp; This is=
 not yet a formal proposal to actual change the document.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was thinking about proposing that we make a change to the conten=
t of the protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. &nbs=
p;The computation of the signature would be unchanged in that it would stil=
l be computed over the base64url encoded string.&nbsp; I believe that the c=
onversion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">At this point I and trying to figure out if I missed anything that=
 would preclude this from working. &nbsp;I am not worried about how hard or=
 easy it would be to do, just if it is even
 possible.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436781EE0BTK5EX14MBXC283r_--

From rlb@ipv.sx  Mon Jun 10 15:03:46 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE3621F994A for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 15:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.357
X-Spam-Level: *
X-Spam-Status: No, score=1.357 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfiImkqJGZeA for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 15:03:42 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id DC03E21F9600 for <jose@ietf.org>; Mon, 10 Jun 2013 15:03:41 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so10797206obq.35 for <jose@ietf.org>; Mon, 10 Jun 2013 15:03:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=7Gd5KW+SccRQxgQQgbOQLjH2xqmCXFbusVK1F2aWQ+Y=; b=abNAjJ9Gooj10hMBk9JTvIBs2bDZbsfsbGCcGmgfOl6vE1rPp+4FCsxnm1gOGAXYHl bgK2q1HO9OvVDlOKL6pSMmHX2tYYIv5YF/lyS53GHdTuzSDRQDfj9Hs7V3A84jW7L7Ew WaIGwntOEChv1Jt2VDa3q6+cBEP9UJi4bQMPYjA4U8nRSu3rm8A+wdAGQfGuYaEscDhy qrtN5Uc/my057Oa7QDp/X76A/jfZmWN9odbZaHsfY5xOQCingJ9E8rtqMtwjiOXl8KhS GnpOpiWsPPUZdEHpUM3EFcgFWtNGmeTBZkE3fE3rNHzM1R8IHrzwbmF1Bh9XfF+lwlan FYwg==
MIME-Version: 1.0
X-Received: by 10.60.35.100 with SMTP id g4mr9778765oej.53.1370901328534; Mon, 10 Jun 2013 14:55:28 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Mon, 10 Jun 2013 14:55:28 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 10 Jun 2013 17:55:28 -0400
Message-ID: <CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e013c68a0b5f43304ded3d69a
X-Gm-Message-State: ALoCoQl+SV+T/2/fRu/V8SCYEPIOWgxpmN6sTwGZl8kdCbX39Zl71gsKB0pE/LvZ6ZON0OvFLMG6
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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 Jun 2013 22:03:46 -0000

--089e013c68a0b5f43304ded3d69a
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Oh, I see.  There actually is a new transformation here:
OLD: (json) --> UTF-8 --> base64
NEW: (json) --> UTF-8 --> json-string

I'm not totally convinced that this is actually a new thing, that is, that
JSON.stringify(protect) won't produce a JSON-safe string.  In the JSON
parsers I'm looking at, the output of JSON.stringify() is a JSON-safe
string.

However, in the course of looking at that question, I came across another
thing that I think is a better reason to abandon this proposal.  Namely,
the JSON parsers in both Chrome and Firefox (possible others; haven't
tried) choke on parsing strings that have control characters.  So while the
following line executes with no problem:
   var x =3D {a:"one line \n two lines"}
calling JSON.parse(JSON.stringify(x)) results in either an error (Chrome)
or an incorrect parse (Firefox).

So regardless of "canonicalization" concerns (which aren't really about
canonicalization), it doesn't seem to me that this is a change that would
be very deployable.  Guess that answers Jim's question about "whether it's
even possible" :)

--Richard






On Mon, Jun 10, 2013 at 5:36 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  My point is that if you just base64url encode the string =96 line the on=
e
> below =96 CRLFs and all, you don=92t have to do any of the canonicalizati=
on
> steps to make the representation JSON-string-safe in the first place.  An=
d
> you=92re using the same tool you=92re already using for encoding every ot=
her
> piece of binary content that needs to be encoded in some way for JOSE.***=
*
>
> ** **
>
> Otherwise, we also still have to worry about =93innocuous=94 transformati=
ons
> that might during transport like space to non-breaking-space, tab to
> spaces, spaces being added at the end of lines (which HTML mail transport=
s
> are notorious for), etc.****
>
> ** **
>
> If we apply the KISS principle and use the same encoding in this case tha=
t
> we do in all other cases, we don=92t have to even consider whether those =
and
> other content integrity threats that we may not have even thought of are
> going to hurt anyone in practice, because they can never arise.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Monday, June 10, 2013 2:30 PM
>
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
> ** **
>
> Mike: They already have to do that stuff before they base64-encode it.
>  All Jim is talking about is *not* doing the base64.****
>
> ** **
>
> On Mon, Jun 10, 2013 at 4:25 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> It=92s a form of canonicalization when you take one representation of a
> string and apply a set of rules to transform it to a more
> stable/transmissible string.  In this case, we=92d be proposing that
> developers have to translate CRLF to \u000DU\u00A, and other similar
> canonicalization transformations.  That=92s a kind of canonicalization.
> Worse, it=92s one that I don=92t believe there=92s standard library suppo=
rt for,
> so developers would have to write it for every implementation and
> platform.  They=92d hate us, and with good reason.****
>
>  ****
>
> And this isn=92t academic.  It=92s commonplace to use newlines in formatt=
ed
> JSON, such as:****
>
>  ****
>
> {"alg": "RSA-OAEP",****
>
> "enc": "A256GCM",****
>
> "kid": "7"****
>
> }****
>
>  ****
>
> Occam=92s Razor suggests always using the same encoding when a stable,
> transmissible string representation is needed =96 in this case base64url
> encoding.****
>
>  ****
>
> The somewhat improved readability of the canonicalization being discussed
> isn=92t worth the interop problems or developer pain it would cost.
> Therefore, I sincerely hope that no one actually proposes this.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* Jim Schaad [mailto:ietf@augustcellars.com]
> *Sent:* Monday, June 10, 2013 10:52 AM
> *To:* Mike Jones; 'Richard Barnes'
> *Cc:* jose@ietf.org****
>
>
> *Subject:* RE: [jose] Possible change to protected field****
>
>  ****
>
> I don=92t understand why you think it takes us down the road to
> canonicalization.  If there are canonization problems in this proposal I
> would say that they may already exist.****
>
>  ****
>
> I don=92t know if you are reading the JSON list or not, however you seem =
to
> be confusing the encoded and the unencoded versions of the string.  The
> string does need to be encoded into a format that is legal to place into =
a
> JSON string field.  In that case there is a number of ways that it can be
> done using quoting.  However when the JSON parser gives that string to th=
e
> application =96 it will be the original UTF8 encoded string.  This means =
that
> a bare LF character would be the =93code point=94 10.  That is the UTF8
> encoding for a line feed character.  It does not get canonicalized in any
> way.  A UTF8 string does have possible code points that are not legal in =
a
> JSON string, but that is JSONs problem not ours.  The JSON string encodin=
g
> format is responsible for the string to text and text to string
> transformations and making sure that those transformations are loss-less.=
*
> ***
>
>  ****
>
> I agree that it may be harder to do, I have not formally presented this a=
s
> a change to the document and will not do so until I have done a full
> analysis on how hard it is.  I am currently just trying to figure out if =
it
> is even technically feasible.****
>
>  ****
>
> Jim****
>
>  ****
>
>  ****
>
> *From:* Mike Jones [mailto:Michael.Jones@microsoft.com<Michael.Jones@micr=
osoft.com>]
>
> *Sent:* Monday, June 10, 2013 10:09 AM
> *To:* Richard Barnes
> *Cc:* Jim Schaad; jose@ietf.org
> *Subject:* RE: [jose] Possible change to protected field****
>
>  ****
>
> This would take us down the road to canonicalization.  How would you
> represent a CRLF in the value?  How would you represent a bare LF?  How
> would you represent a tab?  Canonical representations for all of these, a=
nd
> more, would have to be specified.****
>
>  ****
>
> Using a special encoding for this field that is different than the
> encoding used for all other fields (base64url encoding) is
> developer-hostile.  It forces them to have (and test) special code to
> produce a different for this field alone.  This would undoubtedly result =
in
> interop problems, because the corner cases almost never get tested (and
> often never get coded correctly either).****
>
>  ****
>
> We already have a simple means of ensuring the correct transmission of
> fields.  Occam=92s Razor would suggest just using it.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Monday, June 10, 2013 10:01 AM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
>  ****
>
> I think you've misunderstood the proposal.  It's not that the field will
> be unencoded, it's that it will be encoded as a UTF-8 string instead of a
> base64 string.****
>
>  ****
>
> OLD: (json) --> UTF-8 --> base64****
>
> NEW: (json) --> UTF-8****
>
>  ****
>
> OLD:  { protected: "eyJhbGciOiJSUzI1NiJ9Cg=3D=3D" }****
>
> NEW: { protected: "{\"alg\":\"RS256\"}" }****
>
>  ****
>
> Now, there might still be a problem with that, because JSON strings aren'=
t
> canonical.  In the example above, the quote characters could also have be=
en
> presented as "\u0022".  So if some JSON re-processor were to change the
> encoding ot the string, it would break the signature.  However, that's al=
so
> a problem for the base64-encoded version ("a" vs. "\u0061").****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
> On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> The problem with this suggested change is that it requires unencoded JSON
> objects to be transmitted with no transformations whatsoever, whereas the
> problems with this assumption are well known.  For starters, on UNIX-base=
d
> systems, newlines are typically represented by a bare LF character, where=
as
> on DOS-based systems, newlines are typically represented by a CRLF pair.
> In transmission, many systems, including mail agents tend to convert
> newlines to the system=92s normal format.  This would break these JOSE
> objects.****
>
>  ****
>
> Some agents wrap lines after a certain length.  Particularly when being
> transmitted in HTML or XML, many systems replace two or more consecutive
> spaces with a single space.  Others replace two or more spaces with a
> single space and N-1 non-breaking space characters.  I could go on=85****
>
>  ****
>
> I appreciate the attempt to make things appear to be more uniform and
> readable, but the CRLF/LF problems alone are enough to make this a
> non-starter.****
>
>  ****
>
>                                                                 Best
> wishes,****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Monday, June 10, 2013 9:29 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Possible change to protected field****
>
>  ****
>
> This sounds like a fine idea to me.  It saves space and makes the JSON
> format more human-readable.  It actually makes kind of a nice analogy to
> ASN.1, namely use of OCTET STRING to encapsulate more DER content.****
>
>  ****
>
> The compact serialization can continue to base64url-encode that field, so
> it would not be a breaking change for that serialization.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> I am trying to figure out if I am missing something.  This is not yet a
> formal proposal to actual change the document.****
>
>  ****
>
> I was thinking about proposing that we make a change to the content of th=
e
> protected field in the JWS JSON serialization format.  If we encoded this
> as a UTF8 string rather than the base64url encoded UTF8 string, then the
> content would be smaller.  The computation of the signature would be
> unchanged in that it would still be computed over the base64url encoded
> string.  I believe that the conversion from the UTF8 string to the
> base64url encoded UTF8 string is a deterministic encoding and thus would
> not generate any problems from that point.****
>
>  ****
>
> At this point I and trying to figure out if I missed anything that would
> preclude this from working.  I am not worried about how hard or easy it
> would be to do, just if it is even possible.****
>
>  ****
>
> Jim****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
>  ****
>
> ** **
>

--089e013c68a0b5f43304ded3d69a
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Oh, I see. =A0There actually is a new transformation here:=
=A0<div>OLD: (json) --&gt; UTF-8 --&gt; base64</div><div>NEW: (json) --&gt;=
 UTF-8 --&gt; json-string</div><div><br></div><div>I&#39;m not totally conv=
inced that this is actually a new thing, that is, that JSON.stringify(prote=
ct) won&#39;t produce a JSON-safe string. =A0In the JSON parsers I&#39;m lo=
oking at, the output of JSON.stringify() is a JSON-safe string. =A0</div>
<div><br></div><div>However, in the course of looking at that question, I c=
ame across another thing that I think is a better reason to abandon this pr=
oposal. =A0Namely, the JSON parsers in both Chrome and Firefox (possible ot=
hers; haven&#39;t tried) choke on parsing strings that have control charact=
ers. =A0So while the following line executes with no problem:</div>
<div>=A0 =A0var x =3D {a:&quot;one line \n two lines&quot;}</div><div>calli=
ng JSON.parse(JSON.stringify(x)) results in either an error (Chrome) or an =
incorrect parse (Firefox). =A0</div><div><br></div><div>So regardless of &q=
uot;canonicalization&quot; concerns (which aren&#39;t really about canonica=
lization), it doesn&#39;t seem to me that this is a change that would be ve=
ry deployable. =A0Guess that answers Jim&#39;s question about &quot;whether=
 it&#39;s even possible&quot; :)</div>
<div><br></div><div>--Richard</div><div><br></div><div><br></div><div><br><=
/div><div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"=
gmail_quote">On Mon, Jun 10, 2013 at 5:36 PM, Mike Jones <span dir=3D"ltr">=
&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michae=
l.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">My point is that if you j=
ust base64url encode the string =96 line the one below =96 CRLFs and all, y=
ou don=92t have to do any of the canonicalization steps to make
 the representation JSON-string-safe in the first place.=A0 And you=92re us=
ing the same tool you=92re already using for encoding every other piece of =
binary content that needs to be encoded in some way for JOSE.<u></u><u></u>=
</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Otherwise, we also still =
have to worry about =93innocuous=94 transformations that might during trans=
port like space to non-breaking-space, tab to spaces, spaces
 being added at the end of lines (which HTML mail transports are notorious =
for), etc.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If we apply the KISS prin=
ciple and use the same encoding in this case that we do in all other cases,=
 we don=92t have to even consider whether those and other
 content integrity threats that we may not have even thought of are going t=
o hurt anyone in practice, because they can never arise.<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 2:30 PM</span></p><div><div class=3D"h5"=
><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field<u></u><u></u>=
</div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Mike: They already have to do that stuff before they=
 base64-encode it. =A0All Jim is talking about is *not* doing the base64.<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 4:25 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s a form of canonica=
lization when you take one representation of a string and apply a set of ru=
les
 to transform it to a more stable/transmissible string.=A0 In this case, we=
=92d be proposing that developers have to translate CRLF to \u000DU\u00A, a=
nd other similar canonicalization transformations.=A0 That=92s a kind of ca=
nonicalization.=A0 Worse, it=92s one that I
 don=92t believe there=92s standard library support for, so developers woul=
d have to write it for every implementation and platform.=A0 They=92d hate =
us, and with good reason.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">And this isn=92t academic=
.=A0 It=92s commonplace to use newlines in formatted JSON, such as:</span><=
u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">{&quot;alg&quot;: &quot;R=
SA-OAEP&quot;,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&quot;enc&quot;: &quot;A2=
56GCM&quot;,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&quot;kid&quot;: &quot;7&=
quot;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">}</span><u></u><u></u></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Occam=92s Razor suggests =
always using the same encoding when a stable, transmissible string represen=
tation
 is needed =96 in this case base64url encoding.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The somewhat improved rea=
dability of the canonicalization being discussed isn=92t worth the interop
 problems or developer pain it would cost.=A0 Therefore, I sincerely hope t=
hat no one actually proposes this.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf=
@augustcellars.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:52 AM<br>
<b>To:</b> Mike Jones; &#39;Richard Barnes&#39;<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> RE: [jose] Possible change to protected field<u></u><u></u>=
</p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I don=92t understand why =
you think it takes us down the road to canonicalization. =A0If there are ca=
nonization
 problems in this proposal I would say that they may already exist.</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I don=92t know if you are=
 reading the JSON list or not, however you seem to be confusing the encoded
 and the unencoded versions of the string.=A0 The string does need to be en=
coded into a format that is legal to place into a JSON string field.=A0 In =
that case there is a number of ways that it can be done using quoting.=A0 H=
owever when the JSON parser gives that
 string to the application =96 it will be the original UTF8 encoded string.=
=A0 This means that a bare LF character would be the =93code point=94 10.=
=A0 That is the UTF8 encoding for a line feed character.=A0 It does not get=
 canonicalized in any way.=A0 A UTF8 string does
 have possible code points that are not legal in a JSON string, but that is=
 JSONs problem not ours.=A0 The JSON string encoding format is responsible =
for the string to text and text to string transformations and making sure t=
hat those transformations are loss-less.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I agree that it may be ha=
rder to do, I have not formally presented this as a change to the document
 and will not do so until I have done a full analysis on how hard it is.=A0=
 I am currently just trying to figure out if it is even technically feasibl=
e.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">mailto=
:Michael.Jones@microsoft.com</a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:09 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> RE: [jose] Possible change to protected field</span><u></u>=
<u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">This would take us down t=
he road to canonicalization.=A0 How would you represent a CRLF in the value=
?=A0
 How would you represent a bare LF?=A0 How would you represent a tab?=A0 Ca=
nonical representations for all of these, and more, would have to be specif=
ied.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Using a special encoding =
for this field that is different than the encoding used for all other field=
s
 (base64url encoding) is developer-hostile.=A0 It forces them to have (and =
test) special code to produce a different for this field alone.=A0 This wou=
ld undoubtedly result in interop problems, because the corner cases almost =
never get tested (and often never get
 coded correctly either).</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">We already have a simple =
means of ensuring the correct transmission of fields.=A0 Occam=92s Razor wo=
uld
 suggest just using it.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Monday, June 10, 2013 10:01 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><u></u>=
<u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I think you&#39;ve misunderstood the proposal. =A0It=
&#39;s not that the field will be unencoded, it&#39;s that it will be encod=
ed as a UTF-8 string instead of a base64 string.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: (json) --&gt; UTF-8 --&gt; base64<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">NEW: (json) --&gt; UTF-8<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD: =A0{ protected: &quot;eyJhbGciOiJSUzI1NiJ9Cg=3D=
=3D&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">NEW: { protected: &quot;{\&quot;alg\&quot;:\&quot;RS=
256\&quot;}&quot; }<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, there might still be a problem with that, becau=
se JSON strings aren&#39;t canonical. =A0In the example above, the quote ch=
aracters could also have been presented as &quot;\u0022&quot;. =A0So
 if some JSON re-processor were to change the encoding ot the string, it wo=
uld break the signature. =A0However, that&#39;s also a problem for the base=
64-encoded version (&quot;a&quot; vs. &quot;\u0061&quot;).<u></u><u></u></p=
>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 12:38 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The problem with this sug=
gested change is that it requires unencoded JSON objects to be transmitted
 with no transformations whatsoever, whereas the problems with this assumpt=
ion are well known.=A0 For starters, on UNIX-based systems, newlines are ty=
pically represented by a bare LF character, whereas on DOS-based systems, n=
ewlines are typically represented
 by a CRLF pair.=A0 In transmission, many systems, including mail agents te=
nd to convert newlines to the system=92s normal format.=A0 This would break=
 these JOSE objects.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Some agents wrap lines af=
ter a certain length.=A0 Particularly when being transmitted in HTML or XML=
,
 many systems replace two or more consecutive spaces with a single space.=
=A0 Others replace two or more spaces with a single space and N-1 non-break=
ing space characters.=A0 I could go on=85</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I appreciate the attempt =
to make things appear to be more uniform and readable, but the CRLF/LF prob=
lems
 alone are enough to make this a non-starter.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 Best wishes,</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Monday, June 10, 2013 9:29 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Possible change to protected field</span><u></u>=
<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">This sounds like a fine idea to me. =A0It saves spac=
e and makes the JSON format more human-readable. =A0It actually makes kind =
of a nice analogy to ASN.1, namely use of OCTET STRING
 to encapsulate more DER content.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The compact serialization can continue to base64url-=
encode that field, so it would not be a breaking change for that serializat=
ion.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, Jun 10, 2013 at 1:46 AM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I am trying to figure out if I am missing something.=
=A0 This is not yet a formal proposal to actual change the document.<u></u>=
<u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I was thinking about proposing that we make a change=
 to the content of the protected field in the JWS JSON serialization format=
.=A0 If we encoded this as a UTF8 string rather than
 the base64url encoded UTF8 string, then the content would be smaller. =A0T=
he computation of the signature would be unchanged in that it would still b=
e computed over the base64url encoded string.=A0 I believe that the convers=
ion from the UTF8 string to the base64url
 encoded UTF8 string is a deterministic encoding and thus would not generat=
e any problems from that point.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">At this point I and trying to figure out if I missed=
 anything that would preclude this from working. =A0I am not worried about =
how hard or easy it would be to do, just if it is even
 possible.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--089e013c68a0b5f43304ded3d69a--

From Michael.Jones@microsoft.com  Mon Jun 10 17:26:44 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7093121E804B for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 17:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[AWL=-1.602, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_43=0.6, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FsdYXQupRqTl for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 17:26:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id 8704811E80A5 for <jose@ietf.org>; Mon, 10 Jun 2013 17:26:34 -0700 (PDT)
Received: from BN1AFFO11FD009.protection.gbl (10.58.52.201) by BN1BFFO11HUB022.protection.gbl (10.58.53.132) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 11 Jun 2013 00:26:30 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD009.mail.protection.outlook.com (10.58.52.69) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 11 Jun 2013 00:26:30 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Tue, 11 Jun 2013 00:25:02 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Richard Barnes' <rlb@ipv.sx>
Thread-Topic: [jose] Should we delete the "typ" header field
Thread-Index: Ac5ct7bsKO37MhFARcu9P04lU2GoQQABwgsAAAHLQQAAAInWgAAAOgLgAACJDAAAAAUH4AAFwCCAAAMuIUAAFPZtAAAAEXPAAADBZ4AAABGfMAABrzSAAjskL+A=
Date: Tue, 11 Jun 2013 00:25:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678214FF@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <046301ce5d4d$15ecd2b0$41c67810$@augustcellars.com>
In-Reply-To: <046301ce5d4d$15ecd2b0$41c67810$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678214FFTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(52604005)(24454002)(199002)(377454002)(189002)(54356001)(76482001)(47446002)(16406001)(51856001)(46102001)(33656001)(65816001)(56776001)(47736001)(74876001)(53806001)(63696002)(50986001)(79102001)(80022001)(55846006)(16236675002)(20776003)(76786001)(66066001)(15202345002)(69226001)(59766001)(6806003)(74502001)(77982001)(54316002)(4396001)(31966008)(74662001)(512954002)(49866001)(74366001)(76796001)(77096001)(56816003)(47976001)(81342001)(74706001)(81542001)(71186001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB022; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 087474FBFA
Cc: "jose@ietf.org" <jose@ietf.org>, 'Dick Hardt' <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 00:26:44 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678214FFTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Answering Jim's message that inadvertently went unanswered...

Neither of these would be correct because of the last "cty":"JWT" in both e=
xamples.  That's because a JWT Claims Set is not a JWT.  You would need to =
omit the last "cty":"JWT" in both examples for this to be correct.

No, there is no overloading.  JWT uses the absence of a "cty" value to say =
that the payload is a JWT Claims Set - which is the default case.

                                                                -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Thursday, May 30, 2013 8:48 AM
To: Mike Jones; 'Richard Barnes'
Cc: jose@ietf.org; 'Dick Hardt'
Subject: RE: [jose] Should we delete the "typ" header field

Ok - I am having some problems with this.  Looking at some concrete psudo-e=
xamples

{typ:JWT, ctyp:JWT,...{type:JWT, ctyp:JWT,...{jwt claims object } }


1.       would be a legal or a non-legal description of a signed and then e=
ncrypted set of JWT claims?

2.       Does it make a difference if there are or are not other header fie=
lds?

{typ:JWE, ctyp:JWT,...{type:JWS, ctyp:JWT,... {jwt claims object }}


1.        Would be a legal or a non-legal description of a signed and then =
encrypted set of JWT claims?

If typ and ctyp are using the same space, does that mean that a JWT set of =
claims and a JWT token are being overloaded on the what the string means?  =
In one case it means a token and in the other case it means a set of claims=
.




From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Thursday, May 30, 2013 8:06 AM
To: Richard Barnes
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt
Subject: RE: [jose] Should we delete the "typ" header field

No, "cty" is used by the derived class to determine the type of the encapsu=
lated field.  But that's not a complete description of the *entire object* =
- especially not the additional meaning imbued by the additional parameters=
 the derived type may add to the JOSE header.  "typ" is there to provide th=
e type of the entire object, including what you're calling the wrapper part=
s.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, May 30, 2013 7:58 AM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt
Subject: Re: [jose] Should we delete the "typ" header field

Isn't that requirement met by "cty"?  The only thing JOSE adds is a crypto =
wrapper around the real application content.  If you're an application, you=
 know a JOSE object is the thing you want because it contains the content y=
ou want -- it's a JWT because it contains JWT claims.

Inheritance is the wrong metaphor.  This is encapsulation of application da=
ta:
if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {
    jwtClaims =3D jws.content;
}

--Richard

On Thu, May 30, 2013 at 10:43 AM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
Thanks for sharing the S/MIME details.  Although I was actually making the =
analogy to MIME - not S/MIME.  Like many analogies, it's imperfect, but I b=
elieve still illustrative.

The reason that the analogy isn't perfect is that the JOSE data structures =
are used to build application-specific data structures that are legal JOSE =
data structures but also have additional properties - including additional =
header fields with specific semantics.  (When we agreed to ignore not-under=
stood header fields we let that horse out of the barn.)  For instance, Dick=
 Hardt uses JWEs with issuer and audience fields in the headers, so they ca=
n be used by routing software.

Think of JOSE as the base class and the application types built using it as=
 derived classes.  JWT is a derived class.  Dick's structures are a derived=
 class.  These derived classes sometimes need names.  That's what "typ" is =
for.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, May 30, 2013 7:34 AM

To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt
Subject: Re: [jose] Should we delete the "typ" header field

You're mixing up "typ" and "cty".  If you want to make the analogy to S/MIM=
E, "cty" is the equivalent to Content-Type inside the protected MIME body; =
"typ" is the content-type on the outer MIME header.  Pasting in an example:

-----BEGIN-----
Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;
     name=3Dsmime.p7m
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=3Dsmime.p7m

567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7
77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH
HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh
6YT64V0GhIGfHfQbnj75
-----END-----
<http://tools.ietf.org/html/rfc3851#section-3.4.2>

The outer Content-Type, which is analogous to "typ", MUST be application/pk=
cs7-mime, with a parameter indicating the type of CMS object.  This is the =
same as requiring "typ" to be JWE or JWS.  The inner Content-Type (ASN.1/ba=
se64 encoded in the example) can be anything, just like "cty".

--Richard




On Thu, May 30, 2013 at 12:53 AM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
Requiring that the "typ" value be only "JWS" or "JWE" would be analogous to=
 the MIME spec requiring that the Content-Type: field be only "text/plain" =
or "message/external-body".  It would render it useless.

                                                            -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Wednesday, May 29, 2013 8:03 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; Dick Hardt

Subject: Re: [jose] Should we delete the "typ" header field

If this is the level of "type" you're referring to, I think we should drop =
it from the spec.  It's an application-layer thing that the app can add or =
not according to its wishes.

I'm with Dick on this.  I think we should either have a mandatory indicator=
 of what type of JOSE object this, or nothing at all.   If the former, the =
allowable values are "JWE" and "JWS".  The "+JSON" options are non-sensical=
 -- the app needs to know what it's parsing before it gets this header.  Wh=
ile I have a preference for the former (for clarity), the latter approach i=
s also OK with me, since the MIME types are specific to JWE/JWS.

Another approach here would be to address the JSON and compact forms separa=
tely.  The JSON form has no need of "typ" at all, since the type of the obj=
ect is completely clear from what fields are there, e.g., "recipients" vs. =
"signatures".  For the compact form, we could do something like James's "E.=
"/"S." prefix idea, which you need because the dot-separated components hav=
e different meanings and no field names to indicate this.

--Richard

On Wed, May 29, 2013 at 8:30 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
A standard library is unlikely to know the meanings of all possible "typ" v=
alues - and more to the point, it doesn't have to.  It's the application's =
job to determine that "this blob is a JOSE object" and then pass it to a st=
andard library, which will then ignore the "typ" value.

A standard JOSE library won't know what "typ": "JWT" means.  It won't know =
what "typ": "BCGovToken" is, should the BC Government want to declare that =
it's using a token with particular characteristics.  It won't know what "ty=
p": "XMPP" is, should XMPP want to declare that it's using a JOSE data stru=
cture with particular characteristics.  Etc.

All these values can be registered in the registry and used by applications=
 that understand them.  That's the application's job - not the library's jo=
b.  The "typ" field is just there so that applications have a standard plac=
e to make any such declarations that they may need.

                                                                -- Mike

From: Dick Hardt [mailto:dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>]
Sent: Wednesday, May 29, 2013 5:18 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>

Subject: Re: [jose] Should we delete the "typ" header field

I'd prefer to be able to use standard libraries for creating and parsing to=
kens, and not specialized libraries dependent on the use case.

I strongly think we either drop "typ" or make it required.

On Wed, May 29, 2013 at 5:03 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
It's fine for your application to specify that it's required for your use c=
ase.  Not applications need it, so they shouldn't be forced to pay the spac=
e penalty of an unnecessary field.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Dick Hardt
Sent: Wednesday, May 29, 2013 4:56 PM

To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field

I use it all the time and my code would barf if it was not there.

I think it should be required rather than be a hint if it is going ot be th=
ere.

On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
I think the values just changed

However the way you are using it would be an argument to say that it should=
 be a required field.  Are you just using it as a hint if it exists and the=
n looking at the rest of the fields if it is not present?

Jim


From: Dick Hardt [mailto:dick.hardt@gmail.com<mailto:dick.hardt@gmail.com>]
Sent: Wednesday, May 29, 2013 3:49 PM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we delete the "typ" header field

Well, I have been using, but now realize the spec changed or I was confused=
.

I had been setting "typ" to be either "JWE" or "JWS" depending on the type =
of token I was creating or parsing as it was easier than looking at "alg"

As currently defined, I don't see value in "typ".

-- Dick


On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
In reading the documents, I am trying to understand the justification for h=
aving the "typ" header parameter in the JOSE documents.

The purpose of the field is to hold the type of the object.  In the past, I=
 believe that values which should now be placed in the cty field (such as "=
JWT") were placed in this field as well.  However the parameter is optional=
 and an implementation cannot rely on its being present.  This means that f=
or all practical purposes all of the code to determine the value of the typ=
e field from the values of the alg and enc fields.  If the field was mandat=
ory then this code would disappear at a fairly small space cost and I can u=
nderstand why the parameter would be present.

Can anybody justify why this field should be present in the document - or s=
hould it just disappear?

Jim


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick



--
-- Dick

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--
-- Dick

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose




--_000_4E1F6AAD24975D4BA5B1680429673943678214FFTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:451948128;
	mso-list-type:hybrid;
	mso-list-template-ids:1256721746 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:942688222;
	mso-list-type:hybrid;
	mso-list-template-ids:1233967748 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Answering Jim&#8217;s mes=
sage that inadvertently went unanswered&#8230;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Neither of these would be=
 correct because of the last &#8220;cty&#8221;:&#8221;JWT&#8221; in both ex=
amples.&nbsp; That&#8217;s because a JWT Claims Set is not a JWT.&nbsp; You=
 would need to omit the
 last &#8220;cty&#8221;:&#8221;JWT&#8221; in both examples for this to be c=
orrect.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">No, there is no overloadi=
ng.&nbsp; JWT uses the absence of a &#8220;cty&#8221; value to say that the=
 payload is a JWT Claims Set &#8211; which is the default case.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Thursday, May 30, 2013 8:48 AM<br>
<b>To:</b> Mike Jones; 'Richard Barnes'<br>
<b>Cc:</b> jose@ietf.org; 'Dick Hardt'<br>
<b>Subject:</b> RE: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ok &#8211; I am having so=
me problems with this. &nbsp;Looking at some concrete psudo-examples<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">{typ:JWT, ctyp:JWT,&#8230=
;{type:JWT, ctyp:JWT,&#8230;{jwt claims object } }&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">would be a legal =
or a non-legal description of a signed and then encrypted set of JWT claims=
?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Does it make a di=
fference if there are or are not other header fields?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">{typ:JWE, ctyp:JWT,&#8230=
;{type:JWS, ctyp:JWT,&#8230; {jwt claims object }}<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo4"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;Would be a =
legal or a non-legal description of a signed and then encrypted set of JWT =
claims?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If typ and ctyp are using=
 the same space, does that mean that a JWT set of claims and a JWT token ar=
e being overloaded on the what the string means?&nbsp; In one
 case it means a token and in the other case it means a set of claims.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 8:06 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a>; =
Dick Hardt<br>
<b>Subject:</b> RE: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">No, &#8220;cty&#8221; is =
used by the derived class to determine the type of the encapsulated field.&=
nbsp; But that&#8217;s not a complete description of the *<b>entire object<=
/b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.&nbsp; &#8220;typ&#8221; is t=
here to provide the type of the entire object, including what you&#8217;re =
calling the wrapper parts.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a>; =
Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Isn't that requirement met by &quot;cty&quot;? &nbsp=
;The only thing JOSE adds is a crypto wrapper around the real application c=
ontent. &nbsp;If you're an application, you know a JOSE object is the thing=
 you want because it contains the content you want --
 it's a JWT because it contains JWT claims.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. &nbsp;This is enc=
apsulation of application data:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; &nbsp; jwtClaims =3D jws.content;<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">}<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks for sharing the S/MIME details.&=
nbsp; Although I was actually making the analogy to MIME &#8211; not
 S/MIME.&nbsp; Like many analogies, it&#8217;s imperfect, but I believe sti=
ll illustrative.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The reason that the analogy isn&#8217;t=
 perfect is that the JOSE data structures are used to build application-spe=
cific
 data structures that are legal JOSE data structures but also have addition=
al properties &#8211; including additional header fields with specific sema=
ntics.&nbsp; (When we agreed to ignore not-understood header fields we let =
that horse out of the barn.)&nbsp; For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Think of JOSE as the base class and the=
 application types built using it as derived classes.&nbsp; JWT
 is a derived class.&nbsp; Dick&#8217;s structures are a derived class.&nbs=
p; These derived classes sometimes need names.&nbsp; That&#8217;s what &#82=
20;typ&#8221; is for.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [mailto=
:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">You're mixing up &quot;typ&quot; and &quot;cty&quot;. &nbsp;If you=
 want to make the analogy to S/MIME, &quot;cty&quot; is the equivalent to C=
ontent-Type inside the protected MIME body; &quot;typ&quot; is the content-=
type on
 the outer MIME header. &nbsp;Pasting in an example:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-----BEGIN-----<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp; &nbsp; &nbsp;name=3Dsmime.p7m<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Content-Transfer-Encoding: base64<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Content-Disposition: attachment; filename=3Dsmime.p7m<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">6YT64V0GhIGfHfQbnj75<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-----END-----<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#section-3.4.2" t=
arget=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3.4.2</a>&gt;<o=
:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The outer Content-Type, which is analogous to &quot;typ&quot;, MUS=
T be application/pkcs7-mime, with a parameter indicating the type of CMS ob=
ject. &nbsp;This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. &nbsp;The inner Content-Type (ASN.1/base64 encoded in the e=
xample) can be anything, just like &quot;cty&quot;.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a href=3D"mailto=
:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Requiring that the &#8220;typ&#8221; va=
lue be only &#8220;JWS&#8221; or &#8220;JWE&#8221; would be analogous to th=
e MIME spec requiring
 that the Content-Type: field be only &#8220;text/plain&#8221; or &#8220;me=
ssage/external-body&#8221;.&nbsp; It would render it useless.</span><o:p></=
o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">If this is the level of &quot;type&quot; you're referring to, I th=
ink we should drop it from the spec. &nbsp;It's an application-layer thing =
that the app can add or not according to its wishes.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I'm with Dick on this. &nbsp;I think we should either have a manda=
tory indicator of what type of JOSE object this, or nothing at all. &nbsp; =
If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. &nbsp;The &quot;&#43;JSON&quot; options are non-sensi=
cal -- the app needs to know what it's parsing before it gets this header. =
&nbsp;While I have a preference for the former (for clarity), the latter ap=
proach is also OK with me, since the MIME types are specific to JWE/JWS.<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Another approach here would be to address the JSON and compact for=
ms separately. &nbsp;The JSON form has no need of &quot;typ&quot; at all, s=
ince the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. &nbsp;For the compact form, we could do something like James's &quot;=
E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separat=
ed components have different meanings and no field names to indicate this.<=
o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">A standard library is unlikely to know =
the meanings of all possible &#8220;typ&#8221; values &#8211; and more to t=
he
 point, <b>it doesn&#8217;t have to</b>.&nbsp; It&#8217;s the application&#=
8217;s job to determine that &#8220;this blob is a JOSE object&#8221; and t=
hen pass it to a standard library, which will then ignore the &#8220;typ&#8=
221; value.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">A standard JOSE library won&#8217;t kno=
w what &#8220;typ&#8221;: &#8220;JWT&#8221; means.&nbsp; It won&#8217;t kno=
w what &#8220;typ&#8221;: &#8220;BCGovToken&#8221;
 is, should the BC Government want to declare that it&#8217;s using a token=
 with particular characteristics.&nbsp; It won&#8217;t know what &#8220;typ=
&#8221;: &#8220;XMPP&#8221; is, should XMPP want to declare that it&#8217;s=
 using a JOSE data structure with particular characteristics.&nbsp; Etc.</s=
pan><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">All these values can be registered in t=
he registry and used by applications that understand them.&nbsp;
 That&#8217;s the application&#8217;s job &#8211; not the library&#8217;s j=
ob.&nbsp; The &#8220;typ&#8221; field is just there so that applications ha=
ve a standard place to make any such declarations that they may need.</span=
><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Hardt [mailto:<a =
href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail.com=
</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I'd prefer to be able to use standard libraries for creating and p=
arsing tokens, and not specialized libraries dependent on the use case.<o:p=
></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I strongly think we either drop &quot;typ&quot; or make it require=
d.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">It&#8217;s fine for your application to=
 specify that it&#8217;s required for your use case.&nbsp; Not applications
 need it, so they shouldn&#8217;t be forced to pay the space penalty of an =
unnecessary field.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I use it all the time and my code would barf if it was not there.<=
o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I think it should be required rather than be a hint if it is going=
 ot be there.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I think the values just changed</span><=
o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">However the way you are using it would =
be an argument to say that it should be a required field.&nbsp;
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Hardt [mailto:<a =
href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail.com=
</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Well, I have been using, but now realize the spec changed or I was=
 confused.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I had been setting &quot;typ&quot; to be either &quot;JWE&quot; or=
 &quot;JWS&quot; depending on the type of token I was creating or parsing a=
s it was easier than looking at &quot;alg&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">As currently defined, I don't see value in &quot;typ&quot;.<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">-- Dick<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">In reading the documents, I am trying to understand the justificat=
ion for having the &#8220;typ&#8221; header parameter in the JOSE documents=
.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The purpose of the field is to hold the type of the object. &nbsp;=
In the past, I believe that values which should now be placed in the cty fi=
eld (such as &#8220;JWT&#8221;) were placed in this field
 as well.&nbsp; However the parameter is optional and an implementation can=
not rely on its being present.&nbsp; This means that for all practical purp=
oses all of the code to determine the value of the type field from the valu=
es of the alg and enc fields. &nbsp;If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Can anybody justify why this field should be present in the docume=
nt &#8211; or should it just disappear?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<br>
-- Dick <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<br>
-- Dick <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--
<br>
-- Dick <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678214FFTK5EX14MBXC283r_--

From ietf@augustcellars.com  Mon Jun 10 17:49:56 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8BCF21F9798 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 17:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZHvdrbIFpZ4 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 17:49:50 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id B3A7521F9732 for <jose@ietf.org>; Mon, 10 Jun 2013 17:49:50 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 6C53838EF2 for <jose@ietf.org>; Mon, 10 Jun 2013 17:49:50 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
In-Reply-To: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
Date: Mon, 10 Jun 2013 17:48:58 -0700
Message-ID: <06f001ce663d$75b3d100$611b7300$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06F1_01CE6602.C9567FA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIx7parILLNBTeAgjroi/HvPgYQn5honXcA
Content-Language: en-us
Subject: Re: [jose] Working Group Last Call - draft-ietf-jose-use-cases
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 00:49:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_06F1_01CE6602.C9567FA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a reminder to do this in the next week.  We need both positive and
negative reviews to judge consensus.

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Thursday, May 30, 2013 9:16 AM
To: jose@ietf.org
Subject: [jose] Working Group Last Call - draft-ietf-jose-use-cases
Importance: High

 

<chair>

 

This message starts the Working Group Last Call on the Use Cases document.

 

Minor issues should be sent to the list

 

Major issues (those that should block the document from proceeding to the
IESG) should be sent to the list and an issue created in the tracker.

 

The final day for Last Call comments is June 16, 2013

 

 

Jim

 


------=_NextPart_000_06F1_01CE6602.C9567FA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>This is a reminder to do this in the next =
week.&nbsp; We need both positive and negative reviews to judge =
consensus.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of =
</b>Jim Schaad<br><b>Sent:</b> Thursday, May 30, 2013 9:16 =
AM<br><b>To:</b> jose@ietf.org<br><b>Subject:</b> [jose] Working Group =
Last Call - draft-ietf-jose-use-cases<br><b>Importance:</b> =
High<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&lt;chair&gt;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>This message =
starts the Working Group Last Call on the Use Cases =
document.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Minor issues should be sent to the =
list<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Major issues (those that should block the document =
from proceeding to the IESG) should be sent to the list and an issue =
created in the tracker.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The final =
day for Last Call comments is June 16, 2013<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_06F1_01CE6602.C9567FA0--


From James.H.Manger@team.telstra.com  Mon Jun 10 18:46:08 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D9721E805A for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 18:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.617
X-Spam-Level: 
X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5 tests=[AWL=0.284,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHnn7nm3-1Kd for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 18:46:02 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 9977111E80A5 for <jose@ietf.org>; Mon, 10 Jun 2013 18:46:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,841,1363093200"; d="scan'208";a="140701754"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipocvi.tcif.telstra.com.au with ESMTP; 11 Jun 2013 11:45:58 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7102"; a="137283059"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcdvi.tcif.telstra.com.au with ESMTP; 11 Jun 2013 11:45:58 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Tue, 11 Jun 2013 11:45:58 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>
Date: Tue, 11 Jun 2013 11:45:57 +1000
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5mJmedUF/FFx+1TIG2b1GdvdaeoQAEyvaQ
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com>
In-Reply-To: <CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 01:46:09 -0000

Pj4+IEkgd2FzIHRoaW5raW5nIGFib3V0IHByb3Bvc2luZyB0aGF0IHdlIG1ha2UgYSBjaGFuZ2Ug
dG8gdGhlIGNvbnRlbnQgb2YgdGhlIHByb3RlY3RlZCBmaWVsZCBpbiB0aGUgSldTIEpTT04gc2Vy
aWFsaXphdGlvbiBmb3JtYXQuwqAgSWYgd2UgZW5jb2RlZCB0aGlzIGFzIGEgVVRGOCBzdHJpbmcg
cmF0aGVyIHRoYW4gdGhlIGJhc2U2NHVybCBlbmNvZGVkIFVURjggc3RyaW5nLCB0aGVuIHRoZSBj
b250ZW50IHdvdWxkIGJlIHNtYWxsZXIuDQoNCg0KVGhpcyB3b3VsZCB3b3JrLiBNaWtlJ3MgY2Fu
b25pY2FsaXphdGlvbiB3b3JyaWVzIGFyZSBtaXNwbGFjZWQuIFJpY2hhcmQncyBDaHJvbWUvRmly
ZWZveCAiYnVnIiBzZWVtcyB3cm9uZy4NCg0KRXhhbXBsZTogSk9TRSBvcmlnaW5hdG9yIGNyZWF0
ZXMgdGhlIGZvbGxvd2luZyBoZWFkZXIsIHdpdGggVSswMDBBIGZvciBsaW5lIGVuZGluZy4NCg0K
eyJhbGciOiAiUlNBLU9BRVAiLA0KImVuYyI6ICJBMjU2R0NNIiwNCiJraWQiOiAiNyINCn0NCg0K
VGhpcyBoZWFkZXIgY29uc2lzdHMgb2YgMTkrMSsxNysxKzEwKzErMSsxPTUxIGNoYXJhY3RlcnMg
KGluY2x1ZGluZyAzIHNwYWNlcyBhbmQgNCBuZXdsaW5lcykuIFB1dCB0aGVzZSA1MSBjaGFycyBh
cyB0aGUgdmFsdWUgb2YgdGhlICJwcm90ZWN0ZWQiIGZpZWxkLg0KDQp7InByb3RlY3RlZCI6Intc
ImFsZ1wiOiBcIlJTQS1PQUVQXCIsXG5cImVuY1wiOiBcIkEyNTZHQ01cIixcblwia2lkXCI6IFwi
N1wiXG59XG4ifQ0KDQpUaGV5IGFwcGVhciBhcyA1MSsxNj02NyBjaGFycyBpbnNpZGUgdGhlIHF1
b3RlcyBvZiB0aGUgInByb3RlY3RlZCIgZmllbGQ6IDQgbmV3bGluZXMgYXJlIHJlcGxhY2VkIHdp
dGggNCBuIGNoYXJzOyBwbHVzIDE2IHNsYXNoZXMgYXJlIGFkZGVkLiBUaGlzIHN0ZXAgY291bGQg
aGF2ZSB1c2VkIFx1MDAyMiBpbnN0ZWFkIG9mIFwiLCBvciBcdTAwMEEgb3IgXHUwMDBhIGluc3Rl
YWQgb2YgXG4sIG9yIGVzY2FwZWQgYW55IG9mIHRoZSBvdGhlciAzNSBjaGFycy4gQnV0IHRoYXQg
ZG9lc24ndCBtYXR0ZXIgc2luY2UgdGhpcyBlc2NhcGluZyB3aWxsIGJlIHJlbW92ZWQgYnkgdGhl
IGZpcnN0IEpTT04gcGFyc2UgYXQgdGhlIG90aGVyIGVuZCwgd2hpY2ggd2lsbCBnaXZlcyB0aGUg
b3JpZ2luYWwgNTEgY2hhcnMgdG8gaXRzIGNhbGxlciAoaW4gd2hhdGV2ZXIgbmF0aXZlIHN0cmlu
ZyB0eXBlIHRoZSBsYW5ndWFnZSB1c2VzKS4NCg0KSWYgdGhlIG9yaWdpbmF0b3IgdXNlZCBDUkxG
IGluc3RlYWQgKGdpdmluZyA1NSBjaGFycyksIHRoZSB0cmFuc21pdHRlZCBkYXRhIHdpbGwgYmUg
eyJwcm90ZWN0ZWQiOiIuLi5cclxuLi4uXHJcbi4uLlxyXG4uLi5cclxuIn0uIFRoZSBmaXJzdCBK
U09OIHBhcnNlIGF0IHRoZSByZWNpcGllbnQgd2lsbCByZWNyZWF0ZSB0aGUgY29ycmVjdCA1NSBj
aGFycy4gTm8gcHJvYmxlbS4NCg0KVGhlcmUgaXMgcGxlbnR5IG9mIHBvdGVudGlhbCB0byBjb25m
dXNlIGEgaHVtYW4gZG9pbmcgdGhpcyBtYW51YWxseSBhcyB0aGVyZSBhcmUgMiBsYXllcnMgb2Yg
SlNPTiBzdHJpbmcgZXNjYXBpbmcuIEl0IGlzIHdlbGwtZGVmaW5lZCBlbm91Z2ggZm9yIGEgY29t
cHV0ZXIgKG9yIHNwZWMpIHRob3VnaC4NCg0KDQpBcyB0byB3aGV0aGVyIHRoaXMgaXMgd29ydGh3
aGlsZS4uLg0KSW4gdGhpcyBzcGVjaWZpYyBleGFtcGxlIHRoZSBiYXNlNjR1cmwgb3ZlcmhlYWQg
d291bGQgYmUgKzE3IGNoYXJzLCBtZXJlbHkgMSBtb3JlIGNoYXIgdGhhbiB0aGUgb3ZlcmhlYWQg
b2Ygb21pdHRpbmcgdGhlIGJhc2U2NHVybCBzdGVwLg0KDQoNCkEgbW9yZSB2YWx1YWJsZSBjaGFu
Z2Ugd291bGQgYmUgdG8gYXBwbHkgdGhlIGNyeXB0byBvcGVyYXRpb25zIEFGVEVSIHJlbW92aW5n
IHRoZSBiYXNlNjR1cmwgZW5jb2RpbmcuIFRoYXQgaXMsIGFwcGx5IHRoZSBjcnlwdG8gdG8gYSBV
VEYtOC1lbmNvZGVkIEpTT04gaGVhZGVyLCBpbnN0ZWFkIG9mIHRvIHRoZSBVUy1BU0NJSSBlbmNv
ZGluZyBvZiB0aGUgYmFzZTY0dXJsLWVuY29kZWQgVVRGLTgtZW5jb2RlZCBKU09OIGhlYWRlci4g
SW1wbGVtZW50YXRpb25zIGFsd2F5cyBuZWVkIHRoZSBVVEYtOCBmb3JtIGF0IHNvbWUgcG9pbnQg
YW55d2F5LiBJdCBtZWFucyB0aGUgY3J5cHRvIGlzIGFwcGxpZWQgdG8gZmV3ZXIgYnl0ZXMgc28g
aXQgaXMgZmFzdGVyLiBJdCBtZWFucyBhbiBpZGVhIGxpa2UgSmltJ3MgdGhhdCBkb2Vzbid0IG5l
ZWQgYmFzZTY0dXJsIHRvIG1haW50YWluIHRoZSBjb3JyZWN0IGJ5dGVzIGluIHRyYW5zbWlzc2lv
biBkb2Vzbid0IG5lZWQgdG8gYXJ0aWZpY2lhbGx5IGFkZCBhIGJhc2U2NHVybC1lbmNvZGluZyBz
dGVwIGF0IHRoZSByZWNlaXZlciBqdXN0IHRvIGRvIHRoZSBjcnlwdG8uDQoNCg0KUC5TLg0KPj4g
dGhlIEpTT04gcGFyc2VycyBpbiBib3RoIENocm9tZSBhbmQgRmlyZWZveCAocG9zc2libGUgb3Ro
ZXJzOyBoYXZlbid0IHRyaWVkKSBjaG9rZSBvbiBwYXJzaW5nIHN0cmluZ3MgdGhhdCBoYXZlIGNv
bnRyb2wgY2hhcmFjdGVycw0KDQpKU09OIGRvZXMgbm90IGFsbG93IHVuZXNjYXBlZCBjb250cm9s
IGNoYXJzIHdoZW4gcmVwcmVzZW50aW5nIHN0cmluZ3Mgc28gY2hva2luZyBpcyB0aGUgY29ycmVj
dCBiZWhhdmlvdXIuIEpTT04ucGFyc2UoSlNPTi5zdHJpbmdpZnkoeCkpIHdvcmtzIGZvciBtZSBp
biBDaHJvbWUuIEpTT04uc3RyaW5naWZ5IGRvZXMgTk9UIGxlYXZlIHVuZXNjYXBlZCBjb250cm9s
IGNoYXJzIGluIHF1b3RlcyBpbiB0aGUgcmVzdWx0Lg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQo=

From ietf@augustcellars.com  Mon Jun 10 20:40:19 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A5C11E80E0 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 20:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjzbLTVn5g91 for <jose@ietfa.amsl.com>; Mon, 10 Jun 2013 20:40:14 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 2998011E80DE for <jose@ietf.org>; Mon, 10 Jun 2013 20:40:13 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id D40EB38F14 for <jose@ietf.org>; Mon, 10 Jun 2013 20:40:12 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Mon, 10 Jun 2013 20:39:21 -0700
Message-ID: <071f01ce6655$42a620c0$c7f26240$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0720_01CE661A.9647BDF0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5mVS5ztk0JFTUTTRisGqqoBKmpDw==
Content-Language: en-us
Subject: [jose] Interium Meeting Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 03:40:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0720_01CE661A.9647BDF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<chair>

 

Preliminary agenda for next week's teleconference has been posted

 

http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-interi
m-2013-jose-2

 

jim

 


------=_NextPart_000_0720_01CE661A.9647BDF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>&lt;chair&gt;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Preliminary =
agenda for next week&#8217;s teleconference has been =
posted<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/ag=
enda-interim-2013-jose-2">http://www.ietf.org/proceedings/interim/2013/06=
/17/jose/agenda/agenda-interim-2013-jose-2</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0720_01CE661A.9647BDF0--


From James.H.Manger@team.telstra.com  Tue Jun 11 00:50:05 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A971D21F9A7B for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 00:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level: 
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[AWL=0.254,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HM4GcKp+Y8Q3 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 00:49:58 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id 9FFAC21F9A7F for <jose@ietf.org>; Tue, 11 Jun 2013 00:49:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,843,1363093200"; d="scan'208";a="140603728"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 11 Jun 2013 17:49:52 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7102"; a="190028326"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipcavi.tcif.telstra.com.au with ESMTP; 11 Jun 2013 17:49:52 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Tue, 11 Jun 2013 17:49:52 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "jose@ietf.org" <jose@ietf.org>
Date: Tue, 11 Jun 2013 17:49:50 +1000
Thread-Topic: draft-ietf-jose-use-cases: comments
Thread-Index: AQIx7parILLNBTeAgjroi/HvPgYQn5honXcAgABqR+A=
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B4312F3@WSMSG3153V.srv.dir.telstra.com>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com> <06f001ce663d$75b3d100$611b7300$@augustcellars.com>
In-Reply-To: <06f001ce663d$75b3d100$611b7300$@augustcellars.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [jose] draft-ietf-jose-use-cases: comments
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 07:50:05 -0000

QmVpbmcgcmVhc29uYWJseSBlZmZpY2llbnQgd2hlbiBzZWN1cmluZyBsYXJnZSBhbW91bnRzIG9m
IGRhdGEgaXMgYSB3b3J0aHdoaWxlIHJlcXVpcmVtZW50IHRoYXQgc2VlbXMgdG8gYmUgbWlzc2lu
ZyBmcm9tIGRyYWZ0LWlldGYtam9zZS11c2UtY2FzZXMuDQoNCg0KIkVuY3J5cHRpb24iIGFuZCAi
QXV0aGVudGljYXRlZCBlbmNyeXB0aW9uIiBhcmUgbGlzdGVkIGFzIHNlcGFyYXRlIGZ1bmN0aW9u
YWwgcmVxdWlyZW1lbnRzIFtzZWN0aW9uIDYuMV0uIENhbid0IHdlIGRyb3AgIkVuY3J5cHRpb24i
PyBBIGJlbmVmaXQgb2YgSk9TRSBzaG91bGQgYmUgZWxpbWluYXRpbmcgYSB3aG9sZSBjbGFzcyBv
ZiBjcnlwdG8gcHJvYmxlbXMgY2F1c2VkIGJ5IHVuYXV0aGVudGljYXRlZCAoc3ltbWV0cmljKSBl
bmNyeXB0aW9uLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQo=

From hallam@gmail.com  Tue Jun 11 04:47:25 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F15321F938E for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 04:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.386
X-Spam-Level: 
X-Spam-Status: No, score=-2.386 tagged_above=-999 required=5 tests=[AWL=0.213,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXP9J0PTKFdg for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 04:47:24 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 13A2A21F91BF for <jose@ietf.org>; Tue, 11 Jun 2013 04:47:23 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so2338520wgh.14 for <jose@ietf.org>; Tue, 11 Jun 2013 04:47:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=nQV3CEncYmZF2WcbZPfAmgiHSb3ADAeaAURhMgC28NU=; b=GGZk65e6ac9k1bl5NBeoDMdDcbdxuIl+JgYadAdSS/ZW7x2stsxopfsDtFGrgrcI8v NxkXfxK3GO7GIZ0pR7/AyebwQF/JQNcYgcooGdr792u3rsxQ+CsRa1DZzfvp+UV20qSk BD1ygWzewXa8z84lGSg+SVawpvKEMZpQpj2ejhjf0t7RO8u/WR/3jsozR2skILqKdsFe o3XqHp6EOeSnGvF+6OoUygGFGqEqgZAAjmsY7ZRaJDw2maSCjj1nxwbe0qL1izVb3jEJ b3leBcO4ui3/OkEzK/Z55di/0UdYYsLlNDbEEDy+2+m2qissSnFhRGfKucSsOcrVaR0L Alww==
MIME-Version: 1.0
X-Received: by 10.194.157.2 with SMTP id wi2mr8268068wjb.77.1370951243201; Tue, 11 Jun 2013 04:47:23 -0700 (PDT)
Received: by 10.194.44.100 with HTTP; Tue, 11 Jun 2013 04:47:22 -0700 (PDT)
Date: Tue, 11 Jun 2013 07:47:22 -0400
Message-ID: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "jose@ietf.org" <jose@ietf.org>
Content-Type: multipart/alternative; boundary=089e0122f540db0a9204dedf751a
Subject: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 11:47:25 -0000

--089e0122f540db0a9204dedf751a
Content-Type: text/plain; charset=ISO-8859-1

http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00

The big problem I have found with using JSON for crypto is the lack of a
binary encoding for data. This means that binary blobs have to be encoded
as Base64 which is not too bad in itself except that when using nested
structures the base64 overhead expands the data by 33% each time it is
wrapped.

JSON-B is basically just a scheme that adds in a run-length encoding for
strings and binary data to JSON encoding. It is a superset of JSON and it
is very easy to adapt a JSON parser or encoder to add in support for JSON-B.

Unlike other binary encodings for JSON (BJSON etc), there is no need to
distinguish the binary form from the regular. A JSON-B decoder will accept
either form. This simplifies protocol negotiation as the only concern is
ensuring that the sender emits a form that the receiver can understand.

JSON-B also provides binary encodings for integers (including bignums up to
(2^23)  bits long) and doubles. The last being important in scientific
applications as converting to and from decimal form results in precision
loss.


There is also a JSON-C (Compact) and JSON-D (Data) defined.


The practical benefit of using this with JOSE is that it can be used to
frame the crypto data in the same way that ASN.1 is used in CMS but with
the same simplicity as using traditional JSON.


-- 
Website: http://hallambaker.com/

--089e0122f540db0a9204dedf751a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><a href=3D"http://tools.ietf.org/html/draft-hallambaker-js=
onbcd-00">http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00</a><div><=
br></div><div style>The big problem I have found with using JSON for crypto=
 is the lack of a binary encoding for data. This means that binary blobs ha=
ve to be encoded as Base64 which is not too bad in itself except that when =
using nested structures the base64 overhead expands the data by 33% each ti=
me it is wrapped.</div>
<div style><br></div><div style>JSON-B is basically just a scheme that adds=
 in a run-length encoding for strings and binary data to JSON encoding. It =
is a superset of JSON and it is very easy to adapt a JSON parser or encoder=
 to add in support for JSON-B.</div>
<div style><br></div><div style>Unlike other binary encodings for JSON (BJS=
ON etc), there is no need to distinguish the binary form from the regular. =
A JSON-B decoder will accept either form. This simplifies protocol negotiat=
ion as the only concern is ensuring that the sender emits a form that the r=
eceiver can understand.</div>
<div style><br></div><div style>JSON-B also provides binary encodings for i=
ntegers (including bignums up to (2^23) =A0bits long) and doubles. The last=
 being important in scientific applications as converting to and from decim=
al form results in precision loss.</div>
<div style><br></div><div style><br></div><div style>There is also a JSON-C=
 (Compact) and JSON-D (Data) defined.</div><div style><br></div><div style>=
<br></div><div style>The practical benefit of using this with JOSE is that =
it can be used to frame the crypto data in the same way that ASN.1 is used =
in CMS but with the same simplicity as using traditional JSON.</div>
<div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://hal=
lambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0122f540db0a9204dedf751a--

From rlb@ipv.sx  Tue Jun 11 07:10:36 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C9021F9930 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 07:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.404
X-Spam-Level: 
X-Spam-Status: No, score=-0.404 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhbLKSLOz9AD for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 07:10:31 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4E521F8B51 for <jose@ietf.org>; Tue, 11 Jun 2013 07:10:31 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id va7so11671418obc.27 for <jose@ietf.org>; Tue, 11 Jun 2013 07:10:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=1s2jtPFHvF+UsamUqFAKi1NAOpD+ApZYcass26n2fBA=; b=MR2oevVsscG9C+i7P7LiFUN2pKnbzgnXD33PmYRQBdpSwHpdYqLtP0jhH35xju7VAg HA/cq6HF/ftSRbzABWVHbiHJeJhVBqy1zw87m8+j1c1k2rfk6gz07JP8/uG/DZ2L/N/n hauj/pzfS7qfYD73EhzI6epkQa9HmLujDyPF8cNcG5SQ1/188lfdF+fAkNpwlzV4yGYN iZboQlmggAWrVBVwtnm+PqqLZLNPEjD264AJ0X1OTvm1OaIhlvWJ39HI/5BqcVsLKIu5 KWdT9NbhOGENelYX6THvaUSz8loApSRuXJZCo5XPf3588L5QBgM19jwhQ/kTspyzwGqc YPIg==
MIME-Version: 1.0
X-Received: by 10.60.42.237 with SMTP id r13mr12357896oel.61.1370959831072; Tue, 11 Jun 2013 07:10:31 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 07:10:30 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com>
Date: Tue, 11 Jun 2013 10:10:30 -0400
Message-ID: <CAL02cgRK+h+ObexJgH-XHBm9z6K3-O4OegcYcBw+GXcVqK=gSg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=001a11c206aabbdcd104dee17591
X-Gm-Message-State: ALoCoQmcTxVGeXUTJYL2u4j/RTXMxmTvG3rvLLHt4QWEX9ly2QUeQn8jYrq5eZGIN8rGk6u+RjNK
Cc: Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 14:10:36 -0000

--001a11c206aabbdcd104dee17591
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> >>> I was thinking about proposing that we make a change to the content o=
f
> the protected field in the JWS JSON serialization format.  If we encoded
> this as a UTF8 string rather than the base64url encoded UTF8 string, then
> the content would be smaller.
>
>
> This would work. Mike's canonicalization worries are misplaced. Richard's
> Chrome/Firefox "bug" seems wrong.
>
> Example: JOSE originator creates the following header, with U+000A for
> line ending.
>
> {"alg": "RSA-OAEP",
> "enc": "A256GCM",
> "kid": "7"
> }
>
> This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3
> spaces and 4 newlines). Put these 51 chars as the value of the "protected=
"
> field.
>
> {"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\":
> \"7\"\n}\n"}
>
> They appear as 51+16=3D67 chars inside the quotes of the "protected" fiel=
d:
> 4 newlines are replaced with 4 n chars; plus 16 slashes are added. This
> step could have used \u0022 instead of \", or \u000A or \u000a instead of
> \n, or escaped any of the other 35 chars. But that doesn't matter since
> this escaping will be removed by the first JSON parse at the other end,
> which will gives the original 51 chars to its caller (in whatever native
> string type the language uses).
>
> If the originator used CRLF instead (giving 55 chars), the transmitted
> data will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON
> parse at the recipient will recreate the correct 55 chars. No problem.
>
> There is plenty of potential to confuse a human doing this manually as
> there are 2 layers of JSON string escaping. It is well-defined enough for=
 a
> computer (or spec) though.
>
>
> As to whether this is worthwhile...
> In this specific example the base64url overhead would be +17 chars, merel=
y
> 1 more char than the overhead of omitting the base64url step.
>
>
> A more valuable change would be to apply the crypto operations AFTER
> removing the base64url encoding. That is, apply the crypto to a
> UTF-8-encoded JSON header, instead of to the US-ASCII encoding of the
> base64url-encoded UTF-8-encoded JSON header. Implementations always need
> the UTF-8 form at some point anyway. It means the crypto is applied to
> fewer bytes so it is faster. It means an idea like Jim's that doesn't nee=
d
> base64url to maintain the correct bytes in transmission doesn't need to
> artificially add a base64url-encoding step at the receiver just to do the
> crypto.
>
>
> P.S.
> >> the JSON parsers in both Chrome and Firefox (possible others; haven't
> tried) choke on parsing strings that have control characters
>
> JSON does not allow unescaped control chars when representing strings so
> choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works for
> me in Chrome. JSON.stringify does NOT leave unescaped control chars in
> quotes in the result.
>

I have heard multiple independent reports of my incorrectness in this
experiment.  So I retract my assertion of infeasibility, with regard to
control characters.

However, there's still an issue with code points that don't have to be
escaped. Consider the following example:

var x =3D '{"a":"caf\\u00e9"}';
var x2 =3D JSON.stringify(JSON.parse(x))

In a quick test of the environments I have on hand (several browsers +
Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which
would break the signature.  The browsers and Node all converted the
"\u00e9" sequence to an unescaped "=E9" character, while Perl (creatively)
rendered it directly as a Latin-1 0xe9 byte.  Only PHP rendered it back to
the escape sequence.  Test code here:
<http://www.ipv.sx/jose/json_test.html>

Now, even if we think that re-encoding is a problem, there's the question
of whether we think the risk is acceptable to achieve better human
readability.  I'm pretty split, myself.

--Richard



>
> --
> James Manger
>

--001a11c206aabbdcd104dee17591
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H <span dir=
=3D"ltr">&lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_=
blank">James.H.Manger@team.telstra.com</a>&gt;</span> wrote:<br><div class=
=3D"gmail_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><div class=3D"im">&gt;&gt;&gt; =
I was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.=A0 If we encoded this=
 as a UTF8 string rather than the base64url encoded UTF8 string, then the c=
ontent would be smaller.<br>

<br>
<br>
</div>This would work. Mike&#39;s canonicalization worries are misplaced. R=
ichard&#39;s Chrome/Firefox &quot;bug&quot; seems wrong.<br>
<br>
Example: JOSE originator creates the following header, with U+000A for line=
 ending.<br>
<div class=3D"im"><br>
{&quot;alg&quot;: &quot;RSA-OAEP&quot;,<br>
&quot;enc&quot;: &quot;A256GCM&quot;,<br>
&quot;kid&quot;: &quot;7&quot;<br>
}<br>
<br>
</div>This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including=
 3 spaces and 4 newlines). Put these 51 chars as the value of the &quot;pro=
tected&quot; field.<br>
<br>
{&quot;protected&quot;:&quot;{\&quot;alg\&quot;: \&quot;RSA-OAEP\&quot;,\n\=
&quot;enc\&quot;: \&quot;A256GCM\&quot;,\n\&quot;kid\&quot;: \&quot;7\&quot=
;\n}\n&quot;}<br>
<br>
They appear as 51+16=3D67 chars inside the quotes of the &quot;protected&qu=
ot; field: 4 newlines are replaced with 4 n chars; plus 16 slashes are adde=
d. This step could have used \u0022 instead of \&quot;, or \u000A or \u000a=
 instead of \n, or escaped any of the other 35 chars. But that doesn&#39;t =
matter since this escaping will be removed by the first JSON parse at the o=
ther end, which will gives the original 51 chars to its caller (in whatever=
 native string type the language uses).<br>

<br>
If the originator used CRLF instead (giving 55 chars), the transmitted data=
 will be {&quot;protected&quot;:&quot;...\r\n...\r\n...\r\n...\r\n&quot;}. =
The first JSON parse at the recipient will recreate the correct 55 chars. N=
o problem.<br>

<br>
There is plenty of potential to confuse a human doing this manually as ther=
e are 2 layers of JSON string escaping. It is well-defined enough for a com=
puter (or spec) though.<br>
<br>
<br>
As to whether this is worthwhile...<br>
In this specific example the base64url overhead would be +17 chars, merely =
1 more char than the overhead of omitting the base64url step.<br>
<br>
<br>
A more valuable change would be to apply the crypto operations AFTER removi=
ng the base64url encoding. That is, apply the crypto to a UTF-8-encoded JSO=
N header, instead of to the US-ASCII encoding of the base64url-encoded UTF-=
8-encoded JSON header. Implementations always need the UTF-8 form at some p=
oint anyway. It means the crypto is applied to fewer bytes so it is faster.=
 It means an idea like Jim&#39;s that doesn&#39;t need base64url to maintai=
n the correct bytes in transmission doesn&#39;t need to artificially add a =
base64url-encoding step at the receiver just to do the crypto.<br>

<br>
<br>
P.S.<br>
<div class=3D"im">&gt;&gt; the JSON parsers in both Chrome and Firefox (pos=
sible others; haven&#39;t tried) choke on parsing strings that have control=
 characters<br>
<br>
</div>JSON does not allow unescaped control chars when representing strings=
 so choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works f=
or me in Chrome. JSON.stringify does NOT leave unescaped control chars in q=
uotes in the result.<br>
</blockquote><div><br></div><div>I have heard multiple independent reports =
of my incorrectness in this experiment. =A0So I retract my assertion of inf=
easibility, with regard to control characters.</div><div><br></div><div>How=
ever, there&#39;s still an issue with code points that don&#39;t have to be=
 escaped. Consider the following example:</div>
<div><br></div><div>var x =3D &#39;{&quot;a&quot;:&quot;caf\\u00e9&quot;}&#=
39;;</div><div>var x2 =3D JSON.stringify(JSON.parse(x))</div><div><br></div=
><div>In a quick test of the environments I have on hand (several browsers =
+ Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which w=
ould break the signature. =A0The browsers and Node all converted the &quot;=
\u00e9&quot; sequence to an unescaped &quot;=E9&quot; character, while Perl=
 (creatively) rendered it directly as a Latin-1 0xe9 byte. =A0Only PHP rend=
ered it back to the escape sequence. =A0Test code here:</div>
<div>&lt;<a href=3D"http://www.ipv.sx/jose/json_test.html">http://www.ipv.s=
x/jose/json_test.html</a>&gt;</div><div><br></div><div>Now, even if we thin=
k that re-encoding is a problem, there&#39;s the question of whether we thi=
nk the risk is acceptable to achieve better human readability. =A0I&#39;m p=
retty split, myself.</div>
<div><br></div><div>--Richard</div><div><br></div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left=
:1ex">

<br>
--<br>
James Manger<br>
</blockquote></div><br></div></div>

--001a11c206aabbdcd104dee17591--

From James.H.Manger@team.telstra.com  Tue Jun 11 08:11:11 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B847E21F9A2E for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.66
X-Spam-Level: 
X-Spam-Status: No, score=-0.66 tagged_above=-999 required=5 tests=[AWL=0.241,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p42vKxj7uPCK for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:11:05 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 10E9621F9A30 for <jose@ietf.org>; Tue, 11 Jun 2013 08:11:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,845,1363093200"; d="scan'208";a="141892903"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipoani.tcif.telstra.com.au with ESMTP; 12 Jun 2013 01:10:56 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7102"; a="143701120"
Received: from wsmsg3703.srv.dir.telstra.com ([172.49.40.171]) by ipccni.tcif.telstra.com.au with ESMTP; 12 Jun 2013 01:10:56 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3703.srv.dir.telstra.com ([172.49.40.171]) with mapi; Wed, 12 Jun 2013 01:10:56 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "rlb@ipv.sx" <rlb@ipv.sx>
Date: Wed, 12 Jun 2013 01:10:55 +1000
Thread-Topic: [jose] Possible change to protected field
Thread-Index: Ac5mrXCdonLoBQT8QNeG1R007BcVmgACG4Xj
Message-ID: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 15:11:11 -0000

I think you are doing it in the wrong order. The issue is whether
 JSON.parse(JSON.stringify(x))
returns the same string.

--
James Manger

----- Reply message -----
From: "Richard Barnes" <rlb@ipv.sx>
Date: Wed, Jun 12, 2013 12:10 am
Subject: [jose] Possible change to protected field
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Cc: "Mike Jones" <Michael.Jones@microsoft.com>, "Jim Schaad" <ietf@augustce=
llars.com>, "jose@ietf.org" <jose@ietf.org>

On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H <James.H.Manger@team.telst=
ra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
>>> I was thinking about proposing that we make a change to the content of =
the protected field in the JWS JSON serialization format.  If we encoded th=
is as a UTF8 string rather than the base64url encoded UTF8 string, then the=
 content would be smaller.


This would work. Mike's canonicalization worries are misplaced. Richard's C=
hrome/Firefox "bug" seems wrong.

Example: JOSE originator creates the following header, with U+000A for line=
 ending.

{"alg": "RSA-OAEP",
"enc": "A256GCM",
"kid": "7"
}

This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 spa=
ces and 4 newlines). Put these 51 chars as the value of the "protected" fie=
ld.

{"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\": \"7\=
"\n}\n"}

They appear as 51+16=3D67 chars inside the quotes of the "protected" field:=
 4 newlines are replaced with 4 n chars; plus 16 slashes are added. This st=
ep could have used \u0022 instead of \", or \u000A or \u000a instead of \n,=
 or escaped any of the other 35 chars. But that doesn't matter since this e=
scaping will be removed by the first JSON parse at the other end, which wil=
l gives the original 51 chars to its caller (in whatever native string type=
 the language uses).

If the originator used CRLF instead (giving 55 chars), the transmitted data=
 will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON parse=
 at the recipient will recreate the correct 55 chars. No problem.

There is plenty of potential to confuse a human doing this manually as ther=
e are 2 layers of JSON string escaping. It is well-defined enough for a com=
puter (or spec) though.


As to whether this is worthwhile...
In this specific example the base64url overhead would be +17 chars, merely =
1 more char than the overhead of omitting the base64url step.


A more valuable change would be to apply the crypto operations AFTER removi=
ng the base64url encoding. That is, apply the crypto to a UTF-8-encoded JSO=
N header, instead of to the US-ASCII encoding of the base64url-encoded UTF-=
8-encoded JSON header. Implementations always need the UTF-8 form at some p=
oint anyway. It means the crypto is applied to fewer bytes so it is faster.=
 It means an idea like Jim's that doesn't need base64url to maintain the co=
rrect bytes in transmission doesn't need to artificially add a base64url-en=
coding step at the receiver just to do the crypto.


P.S.
>> the JSON parsers in both Chrome and Firefox (possible others; haven't tr=
ied) choke on parsing strings that have control characters

JSON does not allow unescaped control chars when representing strings so ch=
oking is the correct behaviour. JSON.parse(JSON.stringify(x)) works for me =
in Chrome. JSON.stringify does NOT leave unescaped control chars in quotes =
in the result.

I have heard multiple independent reports of my incorrectness in this exper=
iment.  So I retract my assertion of infeasibility, with regard to control =
characters.

However, there's still an issue with code points that don't have to be esca=
ped. Consider the following example:

var x =3D '{"a":"caf\\u00e9"}';
var x2 =3D JSON.stringify(JSON.parse(x))

In a quick test of the environments I have on hand (several browsers + Node=
.JS + PHP + Perl), I see a wide variety of behaviors, most of which would b=
reak the signature.  The browsers and Node all converted the "\u00e9" seque=
nce to an unescaped "=E9" character, while Perl (creatively) rendered it di=
rectly as a Latin-1 0xe9 byte.  Only PHP rendered it back to the escape seq=
uence.  Test code here:
<http://www.ipv.sx/jose/json_test.html>

Now, even if we think that re-encoding is a problem, there's the question o=
f whether we think the risk is acceptable to achieve better human readabili=
ty.  I'm pretty split, myself.

--Richard



--
James Manger


From rlb@ipv.sx  Tue Jun 11 08:26:37 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6239121F9A10 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.405
X-Spam-Level: 
X-Spam-Status: No, score=-0.405 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAHg5lcnhTzL for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:26:32 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3213221F99FE for <jose@ietf.org>; Tue, 11 Jun 2013 08:26:32 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so3184142oag.12 for <jose@ietf.org>; Tue, 11 Jun 2013 08:26:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=AKvC0nH7E40PbKiHYeMToVVkPfbK4UiH0HExgbIs8iY=; b=N98nX+Lm+pqYDMzkPd4uDS6ahYQ1ahtoInxeCSfvZrpvyzxYDlEF05AgnZJthQYuKP dq4lJyqbeHUtxV0+gQQgnXJ8YquKx9pLBwoP9MkGL6wU4sCfsYDa1hFjZ/tsF5sbRH1i QWoJK8PCztouMZwa/2llBn/MUGTvYgCrg+88YSILqMDCVAWG7u2oj7PsZymL/dTxX37M apsa4cZAq/ZoZNU8NfWUbN0FP1Q/HTL2xUEXIlFEYd5vDOgatCFgPd/yKFmtblxHnFli 6fv8jDMMQVpQRvEa8cOCmy7FQQmTXV1+PRd76PJs2YuVuJ2fHRlogEc9iUDusf2Hus7W 0YFw==
MIME-Version: 1.0
X-Received: by 10.60.39.165 with SMTP id q5mr12053191oek.109.1370964391669; Tue, 11 Jun 2013 08:26:31 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 08:26:31 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com>
References: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com>
Date: Tue, 11 Jun 2013 11:26:31 -0400
Message-ID: <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=089e013cbeec91108704dee285fe
X-Gm-Message-State: ALoCoQl98yybUjCyt9RQlzapVGtBCD9mrTEqxbJtifrvRQU4JJEqFS+9VlZb9yCB7VV/eN++HwkK
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 15:26:37 -0000

--089e013cbeec91108704dee285fe
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I thought the concern was that some intermediary would get a JOSE object,
deserialize it, then serialize it back to a different form.  It seems like
that corresponds to JSON.stringify(JSON.parse(x)).


On Tue, Jun 11, 2013 at 11:10 AM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> I think you are doing it in the wrong order. The issue is whether
>  JSON.parse(JSON.stringify(x))
> returns the same string.
>
> --
> James Manger
>
> ----- Reply message -----
> From: "Richard Barnes" <rlb@ipv.sx>
> Date: Wed, Jun 12, 2013 12:10 am
> Subject: [jose] Possible change to protected field
> To: "Manger, James H" <James.H.Manger@team.telstra.com>
> Cc: "Mike Jones" <Michael.Jones@microsoft.com>, "Jim Schaad" <
> ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
>
> On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H <
> James.H.Manger@team.telstra.com<mailto:James.H.Manger@team.telstra.com>>
> wrote:
> >>> I was thinking about proposing that we make a change to the content o=
f
> the protected field in the JWS JSON serialization format.  If we encoded
> this as a UTF8 string rather than the base64url encoded UTF8 string, then
> the content would be smaller.
>
>
> This would work. Mike's canonicalization worries are misplaced. Richard's
> Chrome/Firefox "bug" seems wrong.
>
> Example: JOSE originator creates the following header, with U+000A for
> line ending.
>
> {"alg": "RSA-OAEP",
> "enc": "A256GCM",
> "kid": "7"
> }
>
> This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3
> spaces and 4 newlines). Put these 51 chars as the value of the "protected=
"
> field.
>
> {"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\":
> \"7\"\n}\n"}
>
> They appear as 51+16=3D67 chars inside the quotes of the "protected" fiel=
d:
> 4 newlines are replaced with 4 n chars; plus 16 slashes are added. This
> step could have used \u0022 instead of \", or \u000A or \u000a instead of
> \n, or escaped any of the other 35 chars. But that doesn't matter since
> this escaping will be removed by the first JSON parse at the other end,
> which will gives the original 51 chars to its caller (in whatever native
> string type the language uses).
>
> If the originator used CRLF instead (giving 55 chars), the transmitted
> data will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON
> parse at the recipient will recreate the correct 55 chars. No problem.
>
> There is plenty of potential to confuse a human doing this manually as
> there are 2 layers of JSON string escaping. It is well-defined enough for=
 a
> computer (or spec) though.
>
>
> As to whether this is worthwhile...
> In this specific example the base64url overhead would be +17 chars, merel=
y
> 1 more char than the overhead of omitting the base64url step.
>
>
> A more valuable change would be to apply the crypto operations AFTER
> removing the base64url encoding. That is, apply the crypto to a
> UTF-8-encoded JSON header, instead of to the US-ASCII encoding of the
> base64url-encoded UTF-8-encoded JSON header. Implementations always need
> the UTF-8 form at some point anyway. It means the crypto is applied to
> fewer bytes so it is faster. It means an idea like Jim's that doesn't nee=
d
> base64url to maintain the correct bytes in transmission doesn't need to
> artificially add a base64url-encoding step at the receiver just to do the
> crypto.
>
>
> P.S.
> >> the JSON parsers in both Chrome and Firefox (possible others; haven't
> tried) choke on parsing strings that have control characters
>
> JSON does not allow unescaped control chars when representing strings so
> choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works for
> me in Chrome. JSON.stringify does NOT leave unescaped control chars in
> quotes in the result.
>
> I have heard multiple independent reports of my incorrectness in this
> experiment.  So I retract my assertion of infeasibility, with regard to
> control characters.
>
> However, there's still an issue with code points that don't have to be
> escaped. Consider the following example:
>
> var x =3D '{"a":"caf\\u00e9"}';
> var x2 =3D JSON.stringify(JSON.parse(x))
>
> In a quick test of the environments I have on hand (several browsers +
> Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which
> would break the signature.  The browsers and Node all converted the
> "\u00e9" sequence to an unescaped "=E9" character, while Perl (creatively=
)
> rendered it directly as a Latin-1 0xe9 byte.  Only PHP rendered it back t=
o
> the escape sequence.  Test code here:
> <http://www.ipv.sx/jose/json_test.html>
>
> Now, even if we think that re-encoding is a problem, there's the question
> of whether we think the risk is acceptable to achieve better human
> readability.  I'm pretty split, myself.
>
> --Richard
>
>
>
> --
> James Manger
>
>

--089e013cbeec91108704dee285fe
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I thought the concern was that some intermediary would get=
 a JOSE object, deserialize it, then serialize it back to a different form.=
 =A0It seems like that corresponds to JSON.stringify(JSON.parse(x)).</div><=
div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Tue, Jun 11, 2013 at 11:10 AM, Manger=
, James H <span dir=3D"ltr">&lt;<a href=3D"mailto:James.H.Manger@team.telst=
ra.com" target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I think you are doing it in the wrong order.=
 The issue is whether<br>
=A0JSON.parse(JSON.stringify(x))<br>
returns the same string.<br>
<br>
--<br>
James Manger<br>
<br>
----- Reply message -----<br>
From: &quot;Richard Barnes&quot; &lt;rlb@ipv.sx&gt;<br>
Date: Wed, Jun 12, 2013 12:10 am<br>
Subject: [jose] Possible change to protected field<br>
To: &quot;Manger, James H&quot; &lt;<a href=3D"mailto:James.H.Manger@team.t=
elstra.com">James.H.Manger@team.telstra.com</a>&gt;<br>
Cc: &quot;Mike Jones&quot; &lt;<a href=3D"mailto:Michael.Jones@microsoft.co=
m">Michael.Jones@microsoft.com</a>&gt;, &quot;Jim Schaad&quot; &lt;<a href=
=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a>&gt;, &quot;<a=
 href=3D"mailto:jose@ietf.org">jose@ietf.org</a>&quot; &lt;<a href=3D"mailt=
o:jose@ietf.org">jose@ietf.org</a>&gt;<br>

<div class=3D"im HOEnZb"><br>
On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H &lt;<a href=3D"mailto:Jame=
s.H.Manger@team.telstra.com">James.H.Manger@team.telstra.com</a>&lt;mailto:=
<a href=3D"mailto:James.H.Manger@team.telstra.com">James.H.Manger@team.tels=
tra.com</a>&gt;&gt; wrote:<br>

&gt;&gt;&gt; I was thinking about proposing that we make a change to the co=
ntent of the protected field in the JWS JSON serialization format. =A0If we=
 encoded this as a UTF8 string rather than the base64url encoded UTF8 strin=
g, then the content would be smaller.<br>

<br>
<br>
This would work. Mike&#39;s canonicalization worries are misplaced. Richard=
&#39;s Chrome/Firefox &quot;bug&quot; seems wrong.<br>
<br>
Example: JOSE originator creates the following header, with U+000A for line=
 ending.<br>
<br>
{&quot;alg&quot;: &quot;RSA-OAEP&quot;,<br>
&quot;enc&quot;: &quot;A256GCM&quot;,<br>
&quot;kid&quot;: &quot;7&quot;<br>
}<br>
<br>
This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 spa=
ces and 4 newlines). Put these 51 chars as the value of the &quot;protected=
&quot; field.<br>
<br>
{&quot;protected&quot;:&quot;{\&quot;alg\&quot;: \&quot;RSA-OAEP\&quot;,\n\=
&quot;enc\&quot;: \&quot;A256GCM\&quot;,\n\&quot;kid\&quot;: \&quot;7\&quot=
;\n}\n&quot;}<br>
<br>
They appear as 51+16=3D67 chars inside the quotes of the &quot;protected&qu=
ot; field: 4 newlines are replaced with 4 n chars; plus 16 slashes are adde=
d. This step could have used \u0022 instead of \&quot;, or \u000A or \u000a=
 instead of \n, or escaped any of the other 35 chars. But that doesn&#39;t =
matter since this escaping will be removed by the first JSON parse at the o=
ther end, which will gives the original 51 chars to its caller (in whatever=
 native string type the language uses).<br>

<br>
If the originator used CRLF instead (giving 55 chars), the transmitted data=
 will be {&quot;protected&quot;:&quot;...\r\n...\r\n...\r\n...\r\n&quot;}. =
The first JSON parse at the recipient will recreate the correct 55 chars. N=
o problem.<br>

<br>
There is plenty of potential to confuse a human doing this manually as ther=
e are 2 layers of JSON string escaping. It is well-defined enough for a com=
puter (or spec) though.<br>
<br>
<br>
As to whether this is worthwhile...<br>
In this specific example the base64url overhead would be +17 chars, merely =
1 more char than the overhead of omitting the base64url step.<br>
<br>
<br>
A more valuable change would be to apply the crypto operations AFTER removi=
ng the base64url encoding. That is, apply the crypto to a UTF-8-encoded JSO=
N header, instead of to the US-ASCII encoding of the base64url-encoded UTF-=
8-encoded JSON header. Implementations always need the UTF-8 form at some p=
oint anyway. It means the crypto is applied to fewer bytes so it is faster.=
 It means an idea like Jim&#39;s that doesn&#39;t need base64url to maintai=
n the correct bytes in transmission doesn&#39;t need to artificially add a =
base64url-encoding step at the receiver just to do the crypto.<br>

<br>
<br>
P.S.<br>
&gt;&gt; the JSON parsers in both Chrome and Firefox (possible others; have=
n&#39;t tried) choke on parsing strings that have control characters<br>
<br>
JSON does not allow unescaped control chars when representing strings so ch=
oking is the correct behaviour. JSON.parse(JSON.stringify(x)) works for me =
in Chrome. JSON.stringify does NOT leave unescaped control chars in quotes =
in the result.<br>

<br>
I have heard multiple independent reports of my incorrectness in this exper=
iment. =A0So I retract my assertion of infeasibility, with regard to contro=
l characters.<br>
<br>
However, there&#39;s still an issue with code points that don&#39;t have to=
 be escaped. Consider the following example:<br>
<br>
</div><div class=3D"im HOEnZb">var x =3D &#39;{&quot;a&quot;:&quot;caf\\u00=
e9&quot;}&#39;;<br>
var x2 =3D JSON.stringify(JSON.parse(x))<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">In a quick test of the enviro=
nments I have on hand (several browsers + Node.JS + PHP + Perl), I see a wi=
de variety of behaviors, most of which would break the signature. =A0The br=
owsers and Node all converted the &quot;\u00e9&quot; sequence to an unescap=
ed &quot;=E9&quot; character, while Perl (creatively) rendered it directly =
as a Latin-1 0xe9 byte. =A0Only PHP rendered it back to the escape sequence=
. =A0Test code here:<br>

&lt;<a href=3D"http://www.ipv.sx/jose/json_test.html" target=3D"_blank">htt=
p://www.ipv.sx/jose/json_test.html</a>&gt;<br>
<br>
Now, even if we think that re-encoding is a problem, there&#39;s the questi=
on of whether we think the risk is acceptable to achieve better human reada=
bility. =A0I&#39;m pretty split, myself.<br>
<br>
--Richard<br>
<br>
<br>
<br>
--<br>
James Manger<br>
<br>
</div></div></blockquote></div><br></div>

--089e013cbeec91108704dee285fe--

From cabo@tzi.org  Tue Jun 11 08:56:49 2013
Return-Path: <cabo@tzi.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC0B21F918F for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.14
X-Spam-Level: 
X-Spam-Status: No, score=-106.14 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mipWErHI55bK for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 08:56:42 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEB221F8C1A for <jose@ietf.org>; Tue, 11 Jun 2013 08:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5BFuUpR017686; Tue, 11 Jun 2013 17:56:30 +0200 (CEST)
Received: from [192.168.217.105] (p54893004.dip0.t-ipconnect.de [84.137.48.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4935035F3; Tue, 11 Jun 2013 17:56:30 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com>
Date: Tue, 11 Jun 2013 17:56:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9E403ED-A219-4711-9CBD-32B2BC80622C@tzi.org>
References: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com> <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1508)
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 15:56:49 -0000

I thought the question was:

If x is a JSON-text (the content of the protected field), to transport =
that unharmed through bad_stuff(), do I need to

x' =3D base64url_decode(bad_stuff(base64url_encode(x)))

or is it enough to carry it around in a JSON string:

x' =3D JSON'.parse(bad_stuff(JSON.stringify(x)))
(where JSON and JSON' are the two JSON implementations.)

A prerequisite for that is that

x =3D=3D JSON'.parse(JSON.stringify(x))

which I very much hope is true for all actual Unicode strings x.
(If you have unpaired surrogates or other ill-formed UTF-8 in x, all =
bets are off.)

Then the next question is how bad bad_stuff() is, but CRLF or TAB =
mangling is demonstrably not a problem, because they cannot occur in a =
JSON string representation (only as ignored whitespace around it).

Gr=FC=DFe, Carsten


From rlb@ipv.sx  Tue Jun 11 09:04:13 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3B621F85D1 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.406
X-Spam-Level: 
X-Spam-Status: No, score=-0.406 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVzYZmvW3gj0 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:04:08 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id EE97321F8B51 for <jose@ietf.org>; Tue, 11 Jun 2013 09:04:07 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so3039342oah.11 for <jose@ietf.org>; Tue, 11 Jun 2013 09:04:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=FiX/RkvboGfxkoAP/vpUTKp0l84MENyOYSsOb6mXwkA=; b=btr9HFRwBOOWMdEbt5eogtQwZU0TZzo8Le+Wi2KMXCqG9GxTtoxXVkP0YQ37DNdPbl X7wponh74caS+PhIJPGqdrj8TvKPtptwVhI/lK/FsQfk+EauVN7BF8MeJx5RGNhWFlQa AMdv5i6nvXMKz9WYxm8DgSENZ3kUUtHfCY4BH3vm/1PSdWHZe2yaxCeHF4VvEFOUvfBc vZkWpBIBOLWD1L6vpIYrdaYXaju6iJMSLISP32vvCzq+NA0qSBMS3K5KmFpmxpno/byj r1d/7bobwm3RwcvcO1FUlRcKk3tU0lzi+LPBui5edHXo2ihiLX+U2iEahlHjTVGrQWSt uDqQ==
MIME-Version: 1.0
X-Received: by 10.182.246.198 with SMTP id xy6mr12463972obc.1.1370966647208; Tue, 11 Jun 2013 09:04:07 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 09:04:07 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <A9E403ED-A219-4711-9CBD-32B2BC80622C@tzi.org>
References: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com> <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com> <A9E403ED-A219-4711-9CBD-32B2BC80622C@tzi.org>
Date: Tue, 11 Jun 2013 12:04:07 -0400
Message-ID: <CAL02cgSqSR_qZsckQGv09+8d611aBxLKogLuEaNRzYRD_0X29Q@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a11c1bc0401e3b004dee30c1d
X-Gm-Message-State: ALoCoQmPIFd0mQZmP8S+vUVVNslgohgETjn6B1RxdUMHr2eBfVakaYio0lryjGNX4bbtOHp3qqJ6
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 16:04:13 -0000

--001a11c1bc0401e3b004dee30c1d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The condition you've identified (x =3D=3D JSON'.parse(JSON.stringify(x))) i=
s
necessary, but not sufficient.  In the case we're talking about, you also
need x =3D=3D bad_stuff(x).  x is being used as input to signature
verification, so its bytes cannot change.

It's worth noting that we mandate comparison of strings as unicode code
points.  So it would not be a huge burden on implementations to have them
render x in UTF-8 before putting it into the signature algorithm.  That
should be stable for all the varieties of bad_stuff() we're talking about,
since the only ambiguity is in how the code points are encoded.  (That is,
no sane JSON library is going to change the actual value of a string, just
how it's encoded.)

--Richard


On Tue, Jun 11, 2013 at 11:56 AM, Carsten Bormann <cabo@tzi.org> wrote:

> I thought the question was:
>
> If x is a JSON-text (the content of the protected field), to transport
> that unharmed through bad_stuff(), do I need to
>
> x' =3D base64url_decode(bad_stuff(base64url_encode(x)))
>
> or is it enough to carry it around in a JSON string:
>
> x' =3D JSON'.parse(bad_stuff(JSON.stringify(x)))
> (where JSON and JSON' are the two JSON implementations.)
>
> A prerequisite for that is that
>
> x =3D=3D JSON'.parse(JSON.stringify(x))
>
> which I very much hope is true for all actual Unicode strings x.
> (If you have unpaired surrogates or other ill-formed UTF-8 in x, all bets
> are off.)
>
> Then the next question is how bad bad_stuff() is, but CRLF or TAB manglin=
g
> is demonstrably not a problem, because they cannot occur in a JSON string
> representation (only as ignored whitespace around it).
>
> Gr=FC=DFe, Carsten
>
>

--001a11c1bc0401e3b004dee30c1d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The condition you&#39;ve identified (x =3D=3D JSON&#39;.pa=
rse(JSON.stringify(x))) is necessary, but not sufficient. =A0In the case we=
&#39;re talking about, you also need x =3D=3D bad_stuff(x). =A0x is being u=
sed as input to signature verification, so its bytes cannot change.<br>
<div><br></div><div>It&#39;s worth noting that we mandate comparison of str=
ings as unicode code points. =A0So it would not be a huge burden on impleme=
ntations to have them render x in UTF-8 before putting it into the signatur=
e algorithm. =A0That should be stable for all the varieties of bad_stuff() =
we&#39;re talking about, since the only ambiguity is in how the code points=
 are encoded. =A0(That is, no sane JSON library is going to change the actu=
al value of a string, just how it&#39;s encoded.)</div>
<div><br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">On Tue, Jun 11, 2013 at 11:56 AM, Carsten Borma=
nn <span dir=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">=
cabo@tzi.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I thought the question was:<br>
<br>
If x is a JSON-text (the content of the protected field), to transport that=
 unharmed through bad_stuff(), do I need to<br>
<br>
x&#39; =3D base64url_decode(bad_stuff(base64url_encode(x)))<br>
<br>
or is it enough to carry it around in a JSON string:<br>
<br>
x&#39; =3D JSON&#39;.parse(bad_stuff(JSON.stringify(x)))<br>
(where JSON and JSON&#39; are the two JSON implementations.)<br>
<br>
A prerequisite for that is that<br>
<br>
x =3D=3D JSON&#39;.parse(JSON.stringify(x))<br>
<br>
which I very much hope is true for all actual Unicode strings x.<br>
(If you have unpaired surrogates or other ill-formed UTF-8 in x, all bets a=
re off.)<br>
<br>
Then the next question is how bad bad_stuff() is, but CRLF or TAB mangling =
is demonstrably not a problem, because they cannot occur in a JSON string r=
epresentation (only as ignored whitespace around it).<br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br></div>

--001a11c1bc0401e3b004dee30c1d--

From stpeter@stpeter.im  Tue Jun 11 09:20:28 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01BCC21F8976 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oPoWq9oIc5V for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:20:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id CDD7321F84CA for <jose@ietf.org>; Tue, 11 Jun 2013 09:20:23 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0D27340393; Tue, 11 Jun 2013 10:33:53 -0600 (MDT)
Message-ID: <51B74E44.7040201@stpeter.im>
Date: Tue, 11 Jun 2013 10:20:20 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com>
In-Reply-To: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 16:20:28 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/11/13 5:47 AM, Phillip Hallam-Baker wrote:
> http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00
> 
> The big problem I have found with using JSON for crypto is the lack
> of a binary encoding for data.

Is this json-discuss or the JSON WG list? Binary encodings are way out
of scope, IMHO. Please let's focus on the task at hand.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRt05EAAoJEOoGpJErxa2pAjsP/3Ez0/T/+3D6SzJZe4pRgxbB
gMPLbtTrs+SGbJh4zakepeYp98LyE9Ld+H/ax9eF89HmlfLUWjLuYXdZvcQnSFDF
CaeTzFbz4s7Q6V7ZZzQvyOguIY456goP5DUxA7tb0gNnGt/gTZQrsvCZmm231gfD
Fh416M1fUcTONuzIteP8KigidoYicfdmrokLBMFcMR1dqXpUmreucnI9+AmOjR19
jl1J2b5geHZbS60U1DwEQQ52hcb0hzwDJyhD4vxPG1hEtNWJlwNI/T+gMHVCncAI
iP7RgYaTd9XQaXmUxwECdUBeBN7ZpYfqvTwi/8qq9aNR+O0vaYS5dV+lHxceUlpF
EiwfDbB/NzySNW89iyoBsfiJp0q57+4JNGyLNDCNZGPqJXUrN20ZrXPpJ3gdSfEJ
fwr1FMuhtmST1zNWvTJ4ZgHgYjNII1/KlltkoQ/ZVjvCJReGhG53jWIi72lWaH8I
eVegeTdX95PYxcQHZiQFCBU0ohu4ogMBFJdYFeLYcpfzeXFICyBNWUbs7RHccAVp
RN8svEntxVwxPPan4MVkqSbtP59PmvLbyCXle/GYmWBAfzXWwJyw0VLQaLSIFOZK
W+dxLAuSk6hF0ivVpOMu0YbsSfjrMesdBKrc56Rrpr9s0vs5jVLb2MCd6Adz3pXU
vjNLNyw2mE9wbhd7/Ie4
=I+6N
-----END PGP SIGNATURE-----

From rlb@ipv.sx  Tue Jun 11 09:29:10 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31DD821F8BC0 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.407
X-Spam-Level: 
X-Spam-Status: No, score=-0.407 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id py4EjSoHUML5 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:29:06 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 656F621F8B90 for <jose@ietf.org>; Tue, 11 Jun 2013 09:29:06 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id l20so7913498oag.9 for <jose@ietf.org>; Tue, 11 Jun 2013 09:29:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rXUNft9ODfbmKeM7HNTeMtZWnC49m6dnpZVKQc3qK30=; b=DtUIaxir+Gyb32fflCYqEOSCikM6O8qaCoSeKJiT/E0xxg+2pjPjcks03oxNf9XKce yZlQuFuSt8o+WHzhOgUBUeqFzWBCrbZIbpZcNKNj4xcopPxEODmcqO7hKAeDcePBEFHE mldAXOp75Qf6n4u6vn+p4vBQL+0NDSLxNg7PVJzS39+VTSGiFbfWTL/Wfs+3KoR5Ex7g +NW1hs1oPrDOMqKLHZi4lNQLNLalgrAaklN8/7tF5PnfZf4SCKYe4w1QGVP1ZYJ54rfU ogqRhavRkhr459UbvLcCotm7pl0AbLY/F4jn7/hLSetbXO5/1MYXR2QTV2Lqc4CursRk 4q6A==
MIME-Version: 1.0
X-Received: by 10.182.236.104 with SMTP id ut8mr12333031obc.75.1370968145757;  Tue, 11 Jun 2013 09:29:05 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 09:29:05 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <51B74E44.7040201@stpeter.im>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im>
Date: Tue, 11 Jun 2013 12:29:05 -0400
Message-ID: <CAL02cgRmptVnfhR_QnK16tiqdsB=UyN3JHVXoXz3eG3doP5sWQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=001a11c3183853d5ea04dee3658c
X-Gm-Message-State: ALoCoQk1C89vaTrbiaeWSkP/3NFdqDaZsxwnLO0vXPnWpOyFA44eo1oARFNg8V1e0nV89xkNY+Wy
Cc: Phillip Hallam-Baker <hallam@gmail.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 16:29:10 -0000

--001a11c3183853d5ea04dee3658c
Content-Type: text/plain; charset=ISO-8859-1

+1


On Tue, Jun 11, 2013 at 12:20 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 6/11/13 5:47 AM, Phillip Hallam-Baker wrote:
> > http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00
> >
> > The big problem I have found with using JSON for crypto is the lack
> > of a binary encoding for data.
>
> Is this json-discuss or the JSON WG list? Binary encodings are way out
> of scope, IMHO. Please let's focus on the task at hand.
>
> Peter
>
> - --
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJRt05EAAoJEOoGpJErxa2pAjsP/3Ez0/T/+3D6SzJZe4pRgxbB
> gMPLbtTrs+SGbJh4zakepeYp98LyE9Ld+H/ax9eF89HmlfLUWjLuYXdZvcQnSFDF
> CaeTzFbz4s7Q6V7ZZzQvyOguIY456goP5DUxA7tb0gNnGt/gTZQrsvCZmm231gfD
> Fh416M1fUcTONuzIteP8KigidoYicfdmrokLBMFcMR1dqXpUmreucnI9+AmOjR19
> jl1J2b5geHZbS60U1DwEQQ52hcb0hzwDJyhD4vxPG1hEtNWJlwNI/T+gMHVCncAI
> iP7RgYaTd9XQaXmUxwECdUBeBN7ZpYfqvTwi/8qq9aNR+O0vaYS5dV+lHxceUlpF
> EiwfDbB/NzySNW89iyoBsfiJp0q57+4JNGyLNDCNZGPqJXUrN20ZrXPpJ3gdSfEJ
> fwr1FMuhtmST1zNWvTJ4ZgHgYjNII1/KlltkoQ/ZVjvCJReGhG53jWIi72lWaH8I
> eVegeTdX95PYxcQHZiQFCBU0ohu4ogMBFJdYFeLYcpfzeXFICyBNWUbs7RHccAVp
> RN8svEntxVwxPPan4MVkqSbtP59PmvLbyCXle/GYmWBAfzXWwJyw0VLQaLSIFOZK
> W+dxLAuSk6hF0ivVpOMu0YbsSfjrMesdBKrc56Rrpr9s0vs5jVLb2MCd6Adz3pXU
> vjNLNyw2mE9wbhd7/Ie4
> =I+6N
> -----END PGP SIGNATURE-----
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--001a11c3183853d5ea04dee3658c
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">+1</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 11, 2013 at 12:20 PM, Peter Saint-Andre <span dir="ltr">&lt;<a href="mailto:stpeter@stpeter.im" target="_blank">stpeter@stpeter.im</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 6/11/13 5:47 AM, Phillip Hallam-Baker wrote:<br>
&gt; <a href="http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00" target="_blank">http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00</a><br>
&gt;<br>
&gt; The big problem I have found with using JSON for crypto is the lack<br>
&gt; of a binary encoding for data.<br>
<br>
</div>Is this json-discuss or the JSON WG list? Binary encodings are way out<br>
of scope, IMHO. Please let&#39;s focus on the task at hand.<br>
<br>
Peter<br>
<br>
- --<br>
Peter Saint-Andre<br>
<a href="https://stpeter.im/" target="_blank">https://stpeter.im/</a><br>
<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
Comment: GPGTools - <a href="http://gpgtools.org" target="_blank">http://gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
iQIcBAEBAgAGBQJRt05EAAoJEOoGpJErxa2pAjsP/3Ez0/T/+3D6SzJZe4pRgxbB<br>
gMPLbtTrs+SGbJh4zakepeYp98LyE9Ld+H/ax9eF89HmlfLUWjLuYXdZvcQnSFDF<br>
CaeTzFbz4s7Q6V7ZZzQvyOguIY456goP5DUxA7tb0gNnGt/gTZQrsvCZmm231gfD<br>
Fh416M1fUcTONuzIteP8KigidoYicfdmrokLBMFcMR1dqXpUmreucnI9+AmOjR19<br>
jl1J2b5geHZbS60U1DwEQQ52hcb0hzwDJyhD4vxPG1hEtNWJlwNI/T+gMHVCncAI<br>
iP7RgYaTd9XQaXmUxwECdUBeBN7ZpYfqvTwi/8qq9aNR+O0vaYS5dV+lHxceUlpF<br>
EiwfDbB/NzySNW89iyoBsfiJp0q57+4JNGyLNDCNZGPqJXUrN20ZrXPpJ3gdSfEJ<br>
fwr1FMuhtmST1zNWvTJ4ZgHgYjNII1/KlltkoQ/ZVjvCJReGhG53jWIi72lWaH8I<br>
eVegeTdX95PYxcQHZiQFCBU0ohu4ogMBFJdYFeLYcpfzeXFICyBNWUbs7RHccAVp<br>
RN8svEntxVwxPPan4MVkqSbtP59PmvLbyCXle/GYmWBAfzXWwJyw0VLQaLSIFOZK<br>
W+dxLAuSk6hF0ivVpOMu0YbsSfjrMesdBKrc56Rrpr9s0vs5jVLb2MCd6Adz3pXU<br>
vjNLNyw2mE9wbhd7/Ie4<br>
=I+6N<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
jose mailing list<br>
<a href="mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/jose" target="_blank">https://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote></div><br></div>

--001a11c3183853d5ea04dee3658c--

From cabo@tzi.org  Tue Jun 11 09:32:45 2013
Return-Path: <cabo@tzi.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0175A21F963F for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.153
X-Spam-Level: 
X-Spam-Status: No, score=-106.153 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1Jp0SLr3Jwh for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:32:39 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id BB28521F8BC0 for <jose@ietf.org>; Tue, 11 Jun 2013 09:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5BGWCru019882; Tue, 11 Jun 2013 18:32:13 +0200 (CEST)
Received: from [192.168.217.105] (p54893004.dip0.t-ipconnect.de [84.137.48.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 768D23616; Tue, 11 Jun 2013 18:32:12 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAL02cgSqSR_qZsckQGv09+8d611aBxLKogLuEaNRzYRD_0X29Q@mail.gmail.com>
Date: Tue, 11 Jun 2013 18:32:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC9CB733-4E5C-46C2-9559-80F041B5320B@tzi.org>
References: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com> <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com> <A9E403ED-A219-4711-9CBD-32B2BC80622C@tzi.org> <CAL02cgSqSR_qZsckQGv09+8d611aBxLKogLuEaNRzYRD_0X29Q@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1508)
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 16:32:45 -0000

On Jun 11, 2013, at 18:04, Richard Barnes <rlb@ipv.sx> wrote:

> you also need x =3D=3D bad_stuff(x).=20

I thought the point of the JSON.stringify() was that

x =3D=3D JSON'.parse(bad_stuff(JSON.stringify(x)))

is easier to achieve than

x =3D=3D bad_stuff(x)

just as

x =3D=3D base64url_decode(bad_stuff(base64url_encode(x)))

is easy to achieve.

Gr=FC=DFe, Carsten


From rlb@ipv.sx  Tue Jun 11 09:58:24 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05AFD21F95EF for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.108
X-Spam-Level: 
X-Spam-Status: No, score=-0.108 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lf5FWO33dYcR for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 09:58:19 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id AA2AB21F944C for <jose@ietf.org>; Tue, 11 Jun 2013 09:58:18 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id l20so7958545oag.9 for <jose@ietf.org>; Tue, 11 Jun 2013 09:58:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=B3y4WdgZ3QNdzCN7WRVeexJSXjy13jfiAz/az+1RT8M=; b=im8yF5v97U4L7sufUlXx8kZOx3s24rOD+vMUJ8cgwuI4KP+JAMSSmrAZsUtcvK8PZi BX7iUfLTOs0wheJg2HIjjpXigdiHFFyIbopkqRrHM/z4qsoBCKRw21OyHGlbfu4N09wu ZQTZ9OaH9NM7AD25VtKmzsoU0qyBGTALPk39XUHkXwjB1DC/wXlt8ncK/uu+3eHKf4qt El0JsdEUg7H8n2q82OneyEWqA0xFms495esUC3NjRgJKJ6oCmLhzBHiq7XiLgFi+gaD1 eUPGS1/SukK3y5zGWuvYj83Ii1DkaRjwg2yLb0IQNaCUGvX+DmzE/7qHkCoGoH9omhUe cmUA==
MIME-Version: 1.0
X-Received: by 10.182.246.198 with SMTP id xy6mr12636560obc.1.1370969898071; Tue, 11 Jun 2013 09:58:18 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 09:58:17 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <FC9CB733-4E5C-46C2-9559-80F041B5320B@tzi.org>
References: <9C1E846F-CC1B-4EB5-8877-3E36522173B3@team.telstra.com> <CAL02cgSnROEMMStH1OUn17g7+KWQt1WcMvrY8iEKNFjn4NeVUQ@mail.gmail.com> <A9E403ED-A219-4711-9CBD-32B2BC80622C@tzi.org> <CAL02cgSqSR_qZsckQGv09+8d611aBxLKogLuEaNRzYRD_0X29Q@mail.gmail.com> <FC9CB733-4E5C-46C2-9559-80F041B5320B@tzi.org>
Date: Tue, 11 Jun 2013 12:58:17 -0400
Message-ID: <CAL02cgT8Pnq66y8ubsEtr_u3fPPZUP+H_c2qogcv1ssFYtP_zg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a11c1bc04c5ca3b04dee3cd22
X-Gm-Message-State: ALoCoQn3EY1sI46cIwgRk2GQBHVziSh0esJm/wGPUZPlATqtoV9daK4mtNAaHf+cWHkbndO0h6Ht
Cc: "michael.jones@microsoft.com" <michael.jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "ietf@augustcellars.com" <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 16:58:24 -0000

--001a11c1bc04c5ca3b04dee3cd22
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 11, 2013 at 12:32 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jun 11, 2013, at 18:04, Richard Barnes <rlb@ipv.sx> wrote:
>
> > you also need x =3D=3D bad_stuff(x).
>
> I thought the point of the JSON.stringify() was that
>
> x =3D=3D JSON'.parse(bad_stuff(JSON.stringify(x)))
>
> is easier to achieve than
>
> x =3D=3D bad_stuff(x)
>
> just as
>
> x =3D=3D base64url_decode(bad_stuff(base64url_encode(x)))
>
> is easy to achieve.
>
> Gr=FC=DFe, Carsten
>

Well, this is all happening within the context of a JSON object.  The
question at hand is about a particular field in that object.  That field is
input to a signature validation, so the sender and receiver need to agree
on what octet string it represents.

So the question is, if "x.signedThing" is the field that goes into the
signature algorithm, does x.signedThing =3D=3D
JSON'.parse(bad_stuff(JSON.stringify(x))).signedThing ?

We might also allow for some simple normalization of x.signedThing, e.g.,
converting to UTF-8.

--Richard

--001a11c1bc04c5ca3b04dee3cd22
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 11, 2013 at 12:32 PM, Carsten Bormann <span di=
r=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.or=
g</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Jun 11, 2013, at 18:04, Richard Barnes &lt;rlb@ipv.sx&=
gt; wrote:<br>
<br>
&gt; you also need x =3D=3D bad_stuff(x).<br>
<br>
</div>I thought the point of the JSON.stringify() was that<br>
<br>
x =3D=3D JSON&#39;.parse(bad_stuff(JSON.stringify(x)))<br>
<br>
is easier to achieve than<br>
<br>
x =3D=3D bad_stuff(x)<br>
<br>
just as<br>
<br>
x =3D=3D base64url_decode(bad_stuff(base64url_encode(x)))<br>
<br>
is easy to achieve.<br>
<br>
Gr=FC=DFe, Carsten<br></blockquote><div><br></div><div>Well, this is all ha=
ppening within the context of a JSON object. =A0The question at hand is abo=
ut a particular field in that object. =A0That field is input to a signature=
 validation, so the sender and receiver need to agree on what octet string =
it represents.=A0</div>
<div><br></div><div>So the question is, if &quot;x.signedThing&quot; is the=
 field that goes into the signature algorithm, does x.signedThing =3D=3D JS=
ON&#39;.parse(bad_stuff(JSON.stringify(x))).signedThing ? =A0</div><div><br=
></div>
<div>We might also allow for some simple normalization of x.signedThing, e.=
g., converting to UTF-8.</div><div><br></div><div>--Richard</div><div><br><=
/div><div><br></div><div>=A0</div></div><br></div></div>

--001a11c1bc04c5ca3b04dee3cd22--

From ietf@augustcellars.com  Tue Jun 11 10:13:16 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D910C21F9988 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3z60IXyWZtR for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:13:11 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id D0FB121F9982 for <jose@ietf.org>; Tue, 11 Jun 2013 10:13:10 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id E8DAE38EEE; Tue, 11 Jun 2013 10:13:09 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>, "'Manger, James H'" <James.H.Manger@team.telstra.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>	<CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>	<068101ce6603$3b27c440$b1774cc0$@augustcellars.com>	<4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com> <CAL02cgRK+h+ObexJgH-XHBm9z6K3-O4OegcYcBw+GXcVqK=gSg@mail.gmail.com>
In-Reply-To: <CAL02cgRK+h+ObexJgH-XHBm9z6K3-O4OegcYcBw+GXcVqK=gSg@mail.gmail.com>
Date: Tue, 11 Jun 2013 10:12:17 -0700
Message-ID: <079801ce66c6$d3d59230$7b80b690$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0799_01CE668C.2777F2B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG0QxNjNQen5xE7UI53mmuxyr9BfQI0cZ/ZAVlbblICaXzKXgJtpxE3Aatu5Z8CowcpxwGvHMtuAn9m6/oBuMfIzwIU/XcAAUIWDnWYtXkAwA==
Content-Language: en-us
Cc: 'Mike Jones' <Michael.Jones@microsoft.com>, jose@ietf.org
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 17:13:17 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0799_01CE668C.2777F2B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 7:11 AM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org
Subject: Re: [jose] Possible change to protected field

=20

On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:

>>> I was thinking about proposing that we make a change to the content =
of
the protected field in the JWS JSON serialization format.  If we encoded
this as a UTF8 string rather than the base64url encoded UTF8 string, =
then
the content would be smaller.



This would work. Mike's canonicalization worries are misplaced. =
Richard's
Chrome/Firefox "bug" seems wrong.

Example: JOSE originator creates the following header, with U+000A for =
line
ending.


{"alg": "RSA-OAEP",
"enc": "A256GCM",
"kid": "7"
}

This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 =
spaces
and 4 newlines). Put these 51 chars as the value of the "protected" =
field.

{"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\":
\"7\"\n}\n"}

They appear as 51+16=3D67 chars inside the quotes of the "protected" =
field: 4
newlines are replaced with 4 n chars; plus 16 slashes are added. This =
step
could have used \u0022 instead of \", or \u000A or \u000a instead of \n, =
or
escaped any of the other 35 chars. But that doesn't matter since this
escaping will be removed by the first JSON parse at the other end, which
will gives the original 51 chars to its caller (in whatever native =
string
type the language uses).

If the originator used CRLF instead (giving 55 chars), the transmitted =
data
will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON =
parse
at the recipient will recreate the correct 55 chars. No problem.

There is plenty of potential to confuse a human doing this manually as =
there
are 2 layers of JSON string escaping. It is well-defined enough for a
computer (or spec) though.


As to whether this is worthwhile...
In this specific example the base64url overhead would be +17 chars, =
merely 1
more char than the overhead of omitting the base64url step.


A more valuable change would be to apply the crypto operations AFTER
removing the base64url encoding. That is, apply the crypto to a
UTF-8-encoded JSON header, instead of to the US-ASCII encoding of the
base64url-encoded UTF-8-encoded JSON header. Implementations always need =
the
UTF-8 form at some point anyway. It means the crypto is applied to fewer
bytes so it is faster. It means an idea like Jim's that doesn't need
base64url to maintain the correct bytes in transmission doesn't need to
artificially add a base64url-encoding step at the receiver just to do =
the
crypto.


P.S.

>> the JSON parsers in both Chrome and Firefox (possible others; haven't
tried) choke on parsing strings that have control characters

JSON does not allow unescaped control chars when representing strings so
choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works =
for me
in Chrome. JSON.stringify does NOT leave unescaped control chars in =
quotes
in the result.

=20

I have heard multiple independent reports of my incorrectness in this
experiment.  So I retract my assertion of infeasibility, with regard to
control characters.

=20

However, there's still an issue with code points that don't have to be
escaped. Consider the following example:

=20

var x =3D '{"a":"caf\\u00e9"}';

var x2 =3D JSON.stringify(JSON.parse(x))

=20

In a quick test of the environments I have on hand (several browsers +
Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which
would break the signature.  The browsers and Node all converted the =
"\u00e9"
sequence to an unescaped "=E9" character, while Perl (creatively) =
rendered it
directly as a Latin-1 0xe9 byte.  Only PHP rendered it back to the =
escape
sequence.  Test code here:

<http://www.ipv.sx/jose/json_test.html>

=20

Now, even if we think that re-encoding is a problem, there's the =
question of
whether we think the risk is acceptable to achieve better human =
readability.
I'm pretty split, myself.

=20

Do you thing from your test that this would also be a problem if you did

=20

Base64(JSON.stringify(JSON.parse(Unbase64(x)))

=20

This would appear to be a general re-creation problem even if we use =
base64
encoding

=20

Jim

=20

=20

--Richard

=20

=20


--
James Manger

=20


------=_NextPart_000_0799_01CE668C.2777F2B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Tuesday, June 11, =
2013 7:11 AM<br><b>To:</b> Manger, James H<br><b>Cc:</b> Mike Jones; Jim =
Schaad; jose@ietf.org<br><b>Subject:</b> Re: [jose] Possible change to =
protected field<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Mon, =
Jun 10, 2013 at 9:45 PM, Manger, James H &lt;<a =
href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>&gt;&gt;&gt; I was thinking about =
proposing that we make a change to the content of the protected field in =
the JWS JSON serialization format.&nbsp; If we encoded this as a UTF8 =
string rather than the base64url encoded UTF8 string, then the content =
would be smaller.<br><br><o:p></o:p></p></div><p class=3DMsoNormal>This =
would work. Mike's canonicalization worries are misplaced. Richard's =
Chrome/Firefox &quot;bug&quot; seems wrong.<br><br>Example: JOSE =
originator creates the following header, with U+000A for line =
ending.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>{&quot;alg&quot;: =
&quot;RSA-OAEP&quot;,<br>&quot;enc&quot;: =
&quot;A256GCM&quot;,<br>&quot;kid&quot;: =
&quot;7&quot;<br>}<o:p></o:p></p></div><p class=3DMsoNormal>This header =
consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 spaces and 4 =
newlines). Put these 51 chars as the value of the &quot;protected&quot; =
field.<br><br>{&quot;protected&quot;:&quot;{\&quot;alg\&quot;: =
\&quot;RSA-OAEP\&quot;,\n\&quot;enc\&quot;: =
\&quot;A256GCM\&quot;,\n\&quot;kid\&quot;: =
\&quot;7\&quot;\n}\n&quot;}<br><br>They appear as 51+16=3D67 chars =
inside the quotes of the &quot;protected&quot; field: 4 newlines are =
replaced with 4 n chars; plus 16 slashes are added. This step could have =
used \u0022 instead of \&quot;, or \u000A or \u000a instead of \n, or =
escaped any of the other 35 chars. But that doesn't matter since this =
escaping will be removed by the first JSON parse at the other end, which =
will gives the original 51 chars to its caller (in whatever native =
string type the language uses).<br><br>If the originator used CRLF =
instead (giving 55 chars), the transmitted data will be =
{&quot;protected&quot;:&quot;...\r\n...\r\n...\r\n...\r\n&quot;}. The =
first JSON parse at the recipient will recreate the correct 55 chars. No =
problem.<br><br>There is plenty of potential to confuse a human doing =
this manually as there are 2 layers of JSON string escaping. It is =
well-defined enough for a computer (or spec) though.<br><br><br>As to =
whether this is worthwhile...<br>In this specific example the base64url =
overhead would be +17 chars, merely 1 more char than the overhead of =
omitting the base64url step.<br><br><br>A more valuable change would be =
to apply the crypto operations AFTER removing the base64url encoding. =
That is, apply the crypto to a UTF-8-encoded JSON header, instead of to =
the US-ASCII encoding of the base64url-encoded UTF-8-encoded JSON =
header. Implementations always need the UTF-8 form at some point anyway. =
It means the crypto is applied to fewer bytes so it is faster. It means =
an idea like Jim's that doesn't need base64url to maintain the correct =
bytes in transmission doesn't need to artificially add a =
base64url-encoding step at the receiver just to do the =
crypto.<br><br><br>P.S.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>&gt;&gt; the JSON parsers in both Chrome =
and Firefox (possible others; haven't tried) choke on parsing strings =
that have control characters<o:p></o:p></p></div><p =
class=3DMsoNormal>JSON does not allow unescaped control chars when =
representing strings so choking is the correct behaviour. =
JSON.parse(JSON.stringify(x)) works for me in Chrome. JSON.stringify =
does NOT leave unescaped control chars in quotes in the =
result.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
have heard multiple independent reports of my incorrectness in this =
experiment. &nbsp;So I retract my assertion of infeasibility, with =
regard to control characters.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>However, there's still an issue with code points that =
don't have to be escaped. Consider the following =
example:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>var x =3D =
'{&quot;a&quot;:&quot;caf\\u00e9&quot;}';<o:p></o:p></p></div><div><p =
class=3DMsoNormal>var x2 =3D =
JSON.stringify(JSON.parse(x))<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In a quick test of the environments I have on hand =
(several browsers + Node.JS + PHP + Perl), I see a wide variety of =
behaviors, most of which would break the signature. &nbsp;The browsers =
and Node all converted the &quot;\u00e9&quot; sequence to an unescaped =
&quot;=E9&quot; character, while Perl (creatively) rendered it directly =
as a Latin-1 0xe9 byte. &nbsp;Only PHP rendered it back to the escape =
sequence. &nbsp;Test code here:<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&lt;<a =
href=3D"http://www.ipv.sx/jose/json_test.html">http://www.ipv.sx/jose/jso=
n_test.html</a>&gt;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Now, even if we think that re-encoding is a problem, =
there's the question of whether we think the risk is acceptable to =
achieve better human readability. &nbsp;I'm pretty split, =
myself.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Do you thing from your test that this would also be a problem if you =
did<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Base64(JSON.stringify(JSON.parse(Unbase64(x)))<o:p></o:p></span></p><p=
 class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This would appear to be a general re-creation problem even if we use =
base64 encoding<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><p =
class=3DMsoNormal><br>--<br>James =
Manger<o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_0799_01CE668C.2777F2B0--


From ietf@augustcellars.com  Tue Jun 11 10:15:20 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7792521F93D2 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hviwZDbhd+n6 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:15:16 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 59DFB21F9399 for <jose@ietf.org>; Tue, 11 Jun 2013 10:15:16 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 08B0638EEE; Tue, 11 Jun 2013 10:15:14 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Peter Saint-Andre'" <stpeter@stpeter.im>, "'Phillip Hallam-Baker'" <hallam@gmail.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im>
In-Reply-To: <51B74E44.7040201@stpeter.im>
Date: Tue, 11 Jun 2013 10:14:20 -0700
Message-ID: <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH/sik5iJmRUYrGGqyeCwWmhAFntgF92Vj6mMI674A=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 17:15:20 -0000

<chair>

At this point only the fact that binary encodings exist is in scope for the
WG.

Any concreteness would require a charter modification.

Jim


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> Peter Saint-Andre
> Sent: Tuesday, June 11, 2013 9:20 AM
> To: Phillip Hallam-Baker
> Cc: jose@ietf.org
> Subject: Re: [jose] Binary encoding for JSON
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 6/11/13 5:47 AM, Phillip Hallam-Baker wrote:
> > http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00
> >
> > The big problem I have found with using JSON for crypto is the lack of
> > a binary encoding for data.
> 
> Is this json-discuss or the JSON WG list? Binary encodings are way out of
> scope, IMHO. Please let's focus on the task at hand.
> 
> Peter
> 
> - --
> Peter Saint-Andre
> https://stpeter.im/
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQIcBAEBAgAGBQJRt05EAAoJEOoGpJErxa2pAjsP/3Ez0/T/+3D6SzJZe4pRgxbB
> gMPLbtTrs+SGbJh4zakepeYp98LyE9Ld+H/ax9eF89HmlfLUWjLuYXdZvcQnSFD
> F
> CaeTzFbz4s7Q6V7ZZzQvyOguIY456goP5DUxA7tb0gNnGt/gTZQrsvCZmm231gf
> D
> Fh416M1fUcTONuzIteP8KigidoYicfdmrokLBMFcMR1dqXpUmreucnI9+AmOjR
> 19
> jl1J2b5geHZbS60U1DwEQQ52hcb0hzwDJyhD4vxPG1hEtNWJlwNI/T+gMHVCn
> cAI
> iP7RgYaTd9XQaXmUxwECdUBeBN7ZpYfqvTwi/8qq9aNR+O0vaYS5dV+lHxceU
> lpF
> EiwfDbB/NzySNW89iyoBsfiJp0q57+4JNGyLNDCNZGPqJXUrN20ZrXPpJ3gdSfEJ
> fwr1FMuhtmST1zNWvTJ4ZgHgYjNII1/KlltkoQ/ZVjvCJReGhG53jWIi72lWaH8I
> eVegeTdX95PYxcQHZiQFCBU0ohu4ogMBFJdYFeLYcpfzeXFICyBNWUbs7RHcc
> AVp
> RN8svEntxVwxPPan4MVkqSbtP59PmvLbyCXle/GYmWBAfzXWwJyw0VLQaLS
> IFOZK
> W+dxLAuSk6hF0ivVpOMu0YbsSfjrMesdBKrc56Rrpr9s0vs5jVLb2MCd6Adz3pX
> U
> vjNLNyw2mE9wbhd7/Ie4
> =I+6N
> -----END PGP SIGNATURE-----
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From stpeter@stpeter.im  Tue Jun 11 10:18:31 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E74521F96EA for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeWIh1k8Z7Tz for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:18:27 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 13E1421F9648 for <jose@ietf.org>; Tue, 11 Jun 2013 10:18:27 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 66C4040393; Tue, 11 Jun 2013 11:31:52 -0600 (MDT)
Message-ID: <51B75BDA.7060807@stpeter.im>
Date: Tue, 11 Jun 2013 11:18:18 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jim Schaad <ietf@augustcellars.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im> <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com>
In-Reply-To: <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'Phillip Hallam-Baker' <hallam@gmail.com>, jose@ietf.org
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 17:18:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 6/11/13 11:14 AM, Jim Schaad wrote:
> <chair>
> 
> At this point only the fact that binary encodings exist is in scope
> for the WG.
> 
> Any concreteness would require a charter modification.

Oh, sorry, I got confused between [jose] and [json]. I need to send
those to different folders...

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRt1vaAAoJEOoGpJErxa2pYRIQAJYIjLWvSKj19bUDLXOip2NN
5dcbC2lpogwAqc+0uiFm6M4EH/JyP9VGK2KfUgxx+RUWVbxKi3LlBLDaS+gP2ISC
SsqeeVIofALlBj5TlHxRDE+JRgIbpGWzTpMCa1JZFGETrQ43hHf3F1TFrYOS29Cr
E3XAd0e7Vgyq0aOUJRiCKxCAoB0fytU0M4WhBh5COAHqpnCrfrYxRTlOb27dqsQC
5Y3eHY3rUoTd3uIiRbXKXq7GTOGwRcvsxtpYAo1uBcGJL3GECSpEOITIRMbP6xOr
O8RwtZly87HMD7xB2UbJdjEz2/OmA/RrZLPQZms6iY76Ed7kcDDJEaaDPf/EnwKy
cIqxu/CspXuVyTn57BL7mjLzaAffPTbQjcxs3yq/bSgT7cIY4WKRL7HKPWCGvA4s
7vDsscr5EQWecSVEIXqIGZ4H1Bvo+07jyP/pqCQ9lMsRuF/kbKMCMnu8/SHCFe3y
wIxQ0jSVsrtoZ4FPSeUYEWdKebp4kC7gTl5WVzk8WJrITZvP8tM1KeOz89JrHyAc
VCEbijYKsGFLFFR9zWslurN/FUM4ERlpBwGDmxrf7pwCmhRRd6OtvAkyV/FS+m1t
b0ZKkt+blUMEqllrSmDiul0kLnnrLO/oJ37XjyamD4tZFctrhTF5h6RZm8lMjOgD
OD6vHRg0mK8O6WlTab9G
=Afff
-----END PGP SIGNATURE-----

From rlb@ipv.sx  Tue Jun 11 10:34:20 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8735121F8AD5 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.393
X-Spam-Level: 
X-Spam-Status: No, score=-0.393 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qf+vI2YjhNXm for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:34:15 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E1B3D21F8617 for <jose@ietf.org>; Tue, 11 Jun 2013 10:34:14 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so1029942oag.18 for <jose@ietf.org>; Tue, 11 Jun 2013 10:34:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rV282IEomigO4qZth6DqBNZkq7cgMmdH6jT2nMc5JsU=; b=nlV/l6CVvw6TuVEWdz8Vk/MJbl4qUgQTFjmxndbFpZ0XX2d2UN7iNp0ozlwwneJaki yLwdphHg0aFFqH4SxLotuxJ8uGT5Uc+qv2RZUjjLSVccDQQHOUDGXSXivZMV1/9XbAva oCMt9PNt33R1fMUrqgITJJjfaIibSo+xScVD3Dxr+BERE5PvVMO7lu7G08zyvs+3hAk5 gBImOkZ/kkym6+9spQVqVCN8BvGAeQFOy+XbvqBVE/oP/Tz81fwE29Tt339F/OPgcjsE yvE8Itd6nK8o9WLR/UGd+rcqqZRCYTW5xMFho2EyHVGDwpxvI45MFfwQpFSO9u+plNLs 91tw==
MIME-Version: 1.0
X-Received: by 10.60.35.100 with SMTP id g4mr12532247oej.53.1370972054348; Tue, 11 Jun 2013 10:34:14 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 10:34:14 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <079801ce66c6$d3d59230$7b80b690$@augustcellars.com>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com> <CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com> <068101ce6603$3b27c440$b1774cc0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com> <CAL02cgRK+h+ObexJgH-XHBm9z6K3-O4OegcYcBw+GXcVqK=gSg@mail.gmail.com> <079801ce66c6$d3d59230$7b80b690$@augustcellars.com>
Date: Tue, 11 Jun 2013 13:34:14 -0400
Message-ID: <CAL02cgQQSZnSwMCL9NStO=KtbWSTxCmh_LL6mqV9UzC51GkGiQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e013c68a04bef6204dee44eab
X-Gm-Message-State: ALoCoQlVzjA0oZ8DQoSc8GM4hz5OCq6kPfe9sZyw+CDi3b4RVpvKXtwrxpbhIuaxMbQt8VBehZnP
Cc: Mike Jones <Michael.Jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 17:34:20 -0000

--089e013c68a04bef6204dee44eab
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 11, 2013 at 1:12 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> ** **
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Tuesday, June 11, 2013 7:11 AM
> *To:* Manger, James H
> *Cc:* Mike Jones; Jim Schaad; jose@ietf.org
>
> *Subject:* Re: [jose] Possible change to protected field****
>
> ** **
>
> On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> >>> I was thinking about proposing that we make a change to the content o=
f
> the protected field in the JWS JSON serialization format.  If we encoded
> this as a UTF8 string rather than the base64url encoded UTF8 string, then
> the content would be smaller.
>
> ****
>
> This would work. Mike's canonicalization worries are misplaced. Richard's
> Chrome/Firefox "bug" seems wrong.
>
> Example: JOSE originator creates the following header, with U+000A for
> line ending.****
>
>
> {"alg": "RSA-OAEP",
> "enc": "A256GCM",
> "kid": "7"
> }****
>
> This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3
> spaces and 4 newlines). Put these 51 chars as the value of the "protected=
"
> field.
>
> {"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\":
> \"7\"\n}\n"}
>
> They appear as 51+16=3D67 chars inside the quotes of the "protected" fiel=
d:
> 4 newlines are replaced with 4 n chars; plus 16 slashes are added. This
> step could have used \u0022 instead of \", or \u000A or \u000a instead of
> \n, or escaped any of the other 35 chars. But that doesn't matter since
> this escaping will be removed by the first JSON parse at the other end,
> which will gives the original 51 chars to its caller (in whatever native
> string type the language uses).
>
> If the originator used CRLF instead (giving 55 chars), the transmitted
> data will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON
> parse at the recipient will recreate the correct 55 chars. No problem.
>
> There is plenty of potential to confuse a human doing this manually as
> there are 2 layers of JSON string escaping. It is well-defined enough for=
 a
> computer (or spec) though.
>
>
> As to whether this is worthwhile...
> In this specific example the base64url overhead would be +17 chars, merel=
y
> 1 more char than the overhead of omitting the base64url step.
>
>
> A more valuable change would be to apply the crypto operations AFTER
> removing the base64url encoding. That is, apply the crypto to a
> UTF-8-encoded JSON header, instead of to the US-ASCII encoding of the
> base64url-encoded UTF-8-encoded JSON header. Implementations always need
> the UTF-8 form at some point anyway. It means the crypto is applied to
> fewer bytes so it is faster. It means an idea like Jim's that doesn't nee=
d
> base64url to maintain the correct bytes in transmission doesn't need to
> artificially add a base64url-encoding step at the receiver just to do the
> crypto.
>
>
> P.S.****
>
> >> the JSON parsers in both Chrome and Firefox (possible others; haven't
> tried) choke on parsing strings that have control characters****
>
> JSON does not allow unescaped control chars when representing strings so
> choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works for
> me in Chrome. JSON.stringify does NOT leave unescaped control chars in
> quotes in the result.****
>
> ** **
>
> I have heard multiple independent reports of my incorrectness in this
> experiment.  So I retract my assertion of infeasibility, with regard to
> control characters.****
>
> ** **
>
> However, there's still an issue with code points that don't have to be
> escaped. Consider the following example:****
>
> ** **
>
> var x =3D '{"a":"caf\\u00e9"}';****
>
> var x2 =3D JSON.stringify(JSON.parse(x))****
>
> ** **
>
> In a quick test of the environments I have on hand (several browsers +
> Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which
> would break the signature.  The browsers and Node all converted the
> "\u00e9" sequence to an unescaped "=E9" character, while Perl (creatively=
)
> rendered it directly as a Latin-1 0xe9 byte.  Only PHP rendered it back t=
o
> the escape sequence.  Test code here:****
>
> <http://www.ipv.sx/jose/json_test.html>****
>
> ** **
>
> Now, even if we think that re-encoding is a problem, there's the question
> of whether we think the risk is acceptable to achieve better human
> readability.  I'm pretty split, myself.****
>
> ** **
>
> Do you thing from your test that this would also be a problem if you did*=
*
> **
>
> ** **
>
> Base64(JSON.stringify(JSON.parse(Unbase64(x)))****
>
> ** **
>
> This would appear to be a general re-creation problem even if we use
> base64 encoding
>

The base64 part in your line actually isn't relevant.  It's actually the
outer parse/stringify (on the overall JWE object) that we're worried about
changing the string.

The control case for the experiment would be:

var x =3D '{"a":"validBase64=3D=3D"}';
var x2 =3D JSON.stringify(JSON.parse(x))

That works just fine with my standard test suite.
<http://www.ipv.sx/jose/json_test.html>

--Richard



> ****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> --Richard****
>
> ** **
>
>  ****
>
>
> --
> James Manger****
>
> ** **
>

--089e013c68a04bef6204dee44eab
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 11, 2013 at 1:12 PM, Jim Schaad <span dir=3D"l=
tr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@au=
gustcellars.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D""><span=
 style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125=
)"><u></u>=A0<u></u></span></p><p class=3D""><span style=3D"font-size:11pt;=
font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border-style:none none none solid;border-left-color:blue;bord=
er-left-width:1.5pt;padding:0in 0in 0in 4pt"><div><div style=3D"border-styl=
e:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;pa=
dding:3pt 0in 0in">
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank=
">rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 7:11 AM<br><b>To:</b> Manger, James H<b=
r><b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" targe=
t=3D"_blank">jose@ietf.org</a></span></p><div class=3D"im"><br><b>Subject:<=
/b> Re: [jose] Possible change to protected field<u></u><u></u></div>
<p></p></div></div><p class=3D""><u></u>=A0<u></u></p><div><p class=3D"">On=
 Mon, Jun 10, 2013 at 9:45 PM, Manger, James H &lt;<a href=3D"mailto:James.=
H.Manger@team.telstra.com" target=3D"_blank">James.H.Manger@team.telstra.co=
m</a>&gt; wrote:<u></u><u></u></p>
<div><div><div><div class=3D"h5"><blockquote style=3D"border-style:none non=
e none solid;border-left-color:rgb(204,204,204);border-left-width:1pt;paddi=
ng:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in"><div><p class=3D"" s=
tyle=3D"margin-bottom:12pt">
&gt;&gt;&gt; I was thinking about proposing that we make a change to the co=
ntent of the protected field in the JWS JSON serialization format.=A0 If we=
 encoded this as a UTF8 string rather than the base64url encoded UTF8 strin=
g, then the content would be smaller.<br>
<br><u></u><u></u></p></div><p class=3D"">This would work. Mike&#39;s canon=
icalization worries are misplaced. Richard&#39;s Chrome/Firefox &quot;bug&q=
uot; seems wrong.<br><br>Example: JOSE originator creates the following hea=
der, with U+000A for line ending.<u></u><u></u></p>
<div><p class=3D"" style=3D"margin-bottom:12pt"><br>{&quot;alg&quot;: &quot=
;RSA-OAEP&quot;,<br>&quot;enc&quot;: &quot;A256GCM&quot;,<br>&quot;kid&quot=
;: &quot;7&quot;<br>}<u></u><u></u></p></div><p class=3D"">This header cons=
ists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 spaces and 4 newlin=
es). Put these 51 chars as the value of the &quot;protected&quot; field.<br=
>
<br>{&quot;protected&quot;:&quot;{\&quot;alg\&quot;: \&quot;RSA-OAEP\&quot;=
,\n\&quot;enc\&quot;: \&quot;A256GCM\&quot;,\n\&quot;kid\&quot;: \&quot;7\&=
quot;\n}\n&quot;}<br><br>They appear as 51+16=3D67 chars inside the quotes =
of the &quot;protected&quot; field: 4 newlines are replaced with 4 n chars;=
 plus 16 slashes are added. This step could have used \u0022 instead of \&q=
uot;, or \u000A or \u000a instead of \n, or escaped any of the other 35 cha=
rs. But that doesn&#39;t matter since this escaping will be removed by the =
first JSON parse at the other end, which will gives the original 51 chars t=
o its caller (in whatever native string type the language uses).<br>
<br>If the originator used CRLF instead (giving 55 chars), the transmitted =
data will be {&quot;protected&quot;:&quot;...\r\n...\r\n...\r\n...\r\n&quot=
;}. The first JSON parse at the recipient will recreate the correct 55 char=
s. No problem.<br>
<br>There is plenty of potential to confuse a human doing this manually as =
there are 2 layers of JSON string escaping. It is well-defined enough for a=
 computer (or spec) though.<br><br><br>As to whether this is worthwhile...<=
br>
In this specific example the base64url overhead would be +17 chars, merely =
1 more char than the overhead of omitting the base64url step.<br><br><br>A =
more valuable change would be to apply the crypto operations AFTER removing=
 the base64url encoding. That is, apply the crypto to a UTF-8-encoded JSON =
header, instead of to the US-ASCII encoding of the base64url-encoded UTF-8-=
encoded JSON header. Implementations always need the UTF-8 form at some poi=
nt anyway. It means the crypto is applied to fewer bytes so it is faster. I=
t means an idea like Jim&#39;s that doesn&#39;t need base64url to maintain =
the correct bytes in transmission doesn&#39;t need to artificially add a ba=
se64url-encoding step at the receiver just to do the crypto.<br>
<br><br>P.S.<u></u><u></u></p><div><p class=3D"" style=3D"margin-bottom:12p=
t">&gt;&gt; the JSON parsers in both Chrome and Firefox (possible others; h=
aven&#39;t tried) choke on parsing strings that have control characters<u><=
/u><u></u></p>
</div><p class=3D"">JSON does not allow unescaped control chars when repres=
enting strings so choking is the correct behaviour. JSON.parse(JSON.stringi=
fy(x)) works for me in Chrome. JSON.stringify does NOT leave unescaped cont=
rol chars in quotes in the result.<u></u><u></u></p>
</blockquote><div><p class=3D""><u></u>=A0<u></u></p></div><div><p class=3D=
"">I have heard multiple independent reports of my incorrectness in this ex=
periment. =A0So I retract my assertion of infeasibility, with regard to con=
trol characters.<u></u><u></u></p>
</div><div><p class=3D""><u></u>=A0<u></u></p></div><div><p class=3D"">Howe=
ver, there&#39;s still an issue with code points that don&#39;t have to be =
escaped. Consider the following example:<u></u><u></u></p></div><div><p cla=
ss=3D"">
<u></u>=A0<u></u></p></div><div><p class=3D"">var x =3D &#39;{&quot;a&quot;=
:&quot;caf\\u00e9&quot;}&#39;;<u></u><u></u></p></div><div><p class=3D"">va=
r x2 =3D JSON.stringify(JSON.parse(x))<u></u><u></u></p></div><div><p class=
=3D""><u></u>=A0<u></u></p>
</div><div><p class=3D"">In a quick test of the environments I have on hand=
 (several browsers + Node.JS + PHP + Perl), I see a wide variety of behavio=
rs, most of which would break the signature. =A0The browsers and Node all c=
onverted the &quot;\u00e9&quot; sequence to an unescaped &quot;=E9&quot; ch=
aracter, while Perl (creatively) rendered it directly as a Latin-1 0xe9 byt=
e. =A0Only PHP rendered it back to the escape sequence. =A0Test code here:<=
u></u><u></u></p>
</div><div><p class=3D"">&lt;<a href=3D"http://www.ipv.sx/jose/json_test.ht=
ml" target=3D"_blank">http://www.ipv.sx/jose/json_test.html</a>&gt;<u></u><=
u></u></p></div><div><p class=3D""><u></u>=A0<u></u></p></div></div></div><=
div><div>
<div class=3D"h5"><p class=3D"">Now, even if we think that re-encoding is a=
 problem, there&#39;s the question of whether we think the risk is acceptab=
le to achieve better human readability. =A0I&#39;m pretty split, myself.<u>=
</u><u></u></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p></div></div><p class=3D""=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)">Do you thing from your test that this would also be a problem if y=
ou did<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p><p class=3D""><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Bas=
e64(JSON.stringify(JSON.parse(Unbase64(x)))<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p><p class=3D""><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thi=
s would appear to be a general re-creation problem even if we use base64 en=
coding</span></p>
</div></div></div></div></div></div></div></blockquote><div><br></div><div>=
The base64 part in your line actually isn&#39;t relevant. =A0It&#39;s actua=
lly the outer parse/stringify (on the overall JWE object) that we&#39;re wo=
rried about changing the string. =A0</div>
<div><br></div><div>The control case for the experiment would be:</div><div=
><br></div><div>var x =3D &#39;{&quot;a&quot;:&quot;validBase64=3D=3D&quot;=
}&#39;;</div><div>var x2 =3D=A0<span style=3D"color:rgb(80,0,80)">JSON.stri=
ngify(JSON.parse(x))</span></div>
<div><span style=3D"color:rgb(80,0,80)"><br></span></div><div><span style=
=3D"color:rgb(80,0,80)">That works just fine with my standard test suite. =
=A0</span></div><div><span style=3D"color:rgb(80,0,80)">&lt;</span><font co=
lor=3D"#500050"><a href=3D"http://www.ipv.sx/jose/json_test.html">http://ww=
w.ipv.sx/jose/json_test.html</a></font><span style=3D"color:rgb(80,0,80)">&=
gt;</span></div>
<div><br></div><div>--Richard</div><div><br></div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left=
:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><div style=3D"borde=
r-style:none none none solid;border-left-color:blue;border-left-width:1.5pt=
;padding:0in 0in 0in 4pt"><div><div><div><div><p class=3D""><span style=3D"=
font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=
<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p><p class=3D""><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Jim=
<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p></div><div><p class=3D"">=
<u></u>=A0<u></u></p></div><div><p class=3D"">--Richard<u></u><u></u></p></=
div><div>
<p class=3D""><u></u>=A0<u></u></p></div><div><p class=3D"">=A0<u></u><u></=
u></p></div><blockquote style=3D"border-style:none none none solid;border-l=
eft-color:rgb(204,204,204);border-left-width:1pt;padding:0in 0in 0in 6pt;ma=
rgin-left:4.8pt;margin-right:0in">
<p class=3D""><br><span class=3D""><font color=3D"#888888">--<br>James Mang=
er<u></u><u></u></font></span></p></blockquote></div><p class=3D""><u></u>=
=A0<u></u></p></div></div></div></div></div></blockquote></div><br></div></=
div>

--089e013c68a04bef6204dee44eab--

From trac+jose@trac.tools.ietf.org  Tue Jun 11 10:58:32 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF49C21F9865 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vJpaLGnSwJ7 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 10:58:29 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id BB68621F901F for <jose@ietf.org>; Tue, 11 Jun 2013 10:58:21 -0700 (PDT)
Received: from localhost ([127.0.0.1]:39594 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UmSpo-00012u-Gn; Tue, 11 Jun 2013 19:58:20 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-barnes-jose-use-cases@tools.ietf.org, rlb@ipv.sx
X-Trac-Project: jose
Date: Tue, 11 Jun 2013 17:58:20 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/23
Message-ID: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 23
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-barnes-jose-use-cases@tools.ietf.org, rlb@ipv.sx, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: rlb@ipv.sx
Resent-Message-Id: <20130611175821.BB68621F901F@ietfa.amsl.com>
Resent-Date: Tue, 11 Jun 2013 10:58:21 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 17:58:32 -0000

#23: Make crypto independent of binary encoding (base64)

 The cryptographic operations that JOSE performs should not depend on the
 transfer encoding used for binary components.  The operations should work
 directly on the encoded byte strings, not on the encoded form.

 This is already true for content, IV, ciphertext, encrypted key, and
 authentication tag.  The only thing that needs fixing is the protected
 header value.  That's a little tricky, since the protected header value is
 JSON, which doesn't have a standard encoding.  But it's not that onerous
 just to convert it to UTF-8 -- in fact, senders are already required to
 convert the protected header to UTF-8.

 So the only change is to require recipients to convert the protected
 header to UTF-8 before using it.   This can be accomplished with two minor
 changes:

 <http://tools.ietf.org/html/draft-ietf-jose-json-web-
 signature-11#section-5.2>
 OLD: "The resulting JWS Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627]."
 NEW: "The resulting JWS Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
 valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."

 <http://tools.ietf.org/html/draft-ietf-jose-json-web-
 encryption-11#section-5.2>
 OLD: "The resulting JWE Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627]."
 NEW: "The resulting JWE Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
 valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."

-- 
-------------------------------------+-------------------------------------
 Reporter:  rlb@ipv.sx               |      Owner:  draft-barnes-jose-use-
     Type:  defect                   |  cases@tools.ietf.org
 Priority:  major                    |     Status:  new
Component:  draft-barnes-jose-use-   |  Milestone:
  cases                              |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
jose <http://tools.ietf.org/jose/>


From ietf@augustcellars.com  Tue Jun 11 11:13:05 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4795321F947C for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXeNkxcP2n4H for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:12:59 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 62D7321F9420 for <jose@ietf.org>; Tue, 11 Jun 2013 11:12:59 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id DD6DA38EF2; Tue, 11 Jun 2013 11:12:54 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "Richard Barnes" <rlb@ipv.sx>
Date: Tue, 11 Jun 2013 11:12:02 -0700
Message-ID: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07C9_01CE6694.801BC6A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5mzue82cIT/FA2TpGkbHIImWiqWQ==
Content-Language: en-us
Cc: jose@ietf.org
Subject: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 18:13:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_07C9_01CE6694.801BC6A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<not chair>

 

Richard,

 

I do not currently believe that this is a doable item.  In order for me to
believe otherwise you will need to give a concrete proposal about how to
solve the problem of things drifting back and forth.  Given the text

 

{xxx}\r\r\rThis is the body

 

How does one know where the dividing line between the JSON header and the
body begins?  Until this is completely solved what you propose is not doable
and the current method of base64 encoding will be required.

 

Jim

 


------=_NextPart_000_07C9_01CE6694.801BC6A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>&lt;not =
chair&gt;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Richard,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I do not =
currently believe that this is a doable item.&nbsp; In order for me to =
believe otherwise you will need to give a concrete proposal about how to =
solve the problem of things drifting back and forth.&nbsp; Given the =
text<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>{xxx}\r\r\rThis is the body<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>How does one =
know where the dividing line between the JSON header and the body =
begins?&nbsp; Until this is completely solved what you propose is not =
doable and the current method of base64 encoding will be =
required.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_07C9_01CE6694.801BC6A0--


From rlb@ipv.sx  Tue Jun 11 11:43:22 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C58721F9992 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.395
X-Spam-Level: 
X-Spam-Status: No, score=-0.395 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqMtnfRe4g1P for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:43:17 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 45EF821F9989 for <jose@ietf.org>; Tue, 11 Jun 2013 11:43:17 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so11945701obc.23 for <jose@ietf.org>; Tue, 11 Jun 2013 11:43:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=L9i4U99BnIO5n5qId+jRGNGo9HYmw/j2Fo7f1wCo8SA=; b=LTBnaj08SUij+uB7l5xTQwtTqBgUn2WHMBYvUDb6zAhSd3mhtsekYNMhUl3gchXFAU jD2dfMZh09slM3cxEpSRzo90JgG+Os7gRM0+gurxhhNQYWRZsC2xquyx8E6k/ut28NqY Ma5kfmSE2h+8I3bDi+j+0hjoUvkM9IPseBWWsCupheOf+K3mt9R7rVRs1s/36axehXYe S0mY3OLQQhFejDyA6GiYiGQcac2DKXwLg+xiWfktpm5Fyyi3IWUUT+27yaDWe/W6WOGi pRAeU7JuWer4riX920Qtp6iFlhGFIltnXNwqb5DSZbXYFQcyK1LhAB3JBgY3pj0fOlaM PKjw==
MIME-Version: 1.0
X-Received: by 10.60.33.202 with SMTP id t10mr12803335oei.2.1370976196717; Tue, 11 Jun 2013 11:43:16 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 11:43:16 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com>
Date: Tue, 11 Jun 2013 14:43:16 -0400
Message-ID: <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e013c66b433cb7d04dee54570
X-Gm-Message-State: ALoCoQlCMgabNSfw+yPP1nunZP0VsEpr0fk2mwnxvMqP+aiGijnYxxB4LMoniQkC2D343mV9cG90
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 18:43:22 -0000

--089e013c66b433cb7d04dee54570
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I don't know what you mean by "the problem of things drifting back and
forth".  Let me try to be more concrete.

Consider the following JWE:

{
    "header": { "alg": "dir" }
    "protect":
"eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ"
    ...
}

The "protect" here is the encoding of the header '{"enc": "A128GCM", "kid":
"celui\r\n=E7a\r\n\tl=E0-bas"}'  (hex=3D63 65 6C 75 69 0A 0D C3 A7 61 0A 0D=
 09 6C
C3 A0 2D 62 61 73).

In the current draft, the AAD for the AEAD is the base64-encoded version.
 The proposal here is just to make it the UTF-8 version, before
base64-encoding instead of after:

OLD:
AAD =3D eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ
(=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 53 4=
9 73
49 43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6e 59
51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 51)

NEW:
AAD =3D '{"enc": "A128GCM", "kid": "celui\r\n=E7a\r\n\tl=E0-bas"}'
(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C 20 22 6B 69 6=
4 22
3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73 22 7D)








On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> <not chair>****
>
> ** **
>
> Richard,****
>
> ** **
>
> I do not currently believe that this is a doable item.  In order for me t=
o
> believe otherwise you will need to give a concrete proposal about how to
> solve the problem of things drifting back and forth.  Given the text****
>
> ** **
>
> {xxx}\r\r\rThis is the body****
>
> ** **
>
> How does one know where the dividing line between the JSON header and the
> body begins?  Until this is completely solved what you propose is not
> doable and the current method of base64 encoding will be required.****
>
> ** **
>
> Jim****
>
> ** **
>

--089e013c66b433cb7d04dee54570
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t know what you mean by &quot;the problem of thi=
ngs drifting back and forth&quot;. =A0Let me try to be more concrete.<div><=
br></div><div>Consider the following JWE:</div><div><br></div><div>{</div><=
div>
=A0 =A0 &quot;header&quot;: { &quot;alg&quot;: &quot;dir&quot; }</div><div>=
=A0 =A0 &quot;protect&quot;: &quot;eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2Vs=
dWkKDcOnYQoNCWzDoC1iYXMifQ&quot;</div><div>=A0 =A0 ...</div><div>}</div><di=
v><br></div>
<div>The &quot;protect&quot; here is the encoding of the header &#39;{&quot=
;enc&quot;: &quot;A128GCM&quot;, &quot;kid&quot;: &quot;celui\r\n=E7a\r\n\t=
l=E0-bas&quot;}&#39; =A0(hex=3D63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3=
 A0 2D 62 61 73).</div>
<div><br></div><div>In the current draft, the AAD for the AEAD is the base6=
4-encoded version. =A0The proposal here is just to make it the UTF-8 versio=
n, before base64-encoding instead of after:</div><div><br></div><div>OLD:</=
div>
<div>AAD =3D eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYX=
MifQ=A0</div><div>(=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4=
f 45 64 44 54 53 49 73 49 43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 5=
7 6b 4b 44 63 4f 6e 59 51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 51)<=
/div>
<div><br></div><div>NEW:=A0</div><div>AAD =3D &#39;{&quot;enc&quot;: &quot;=
A128GCM&quot;, &quot;kid&quot;: &quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}&#3=
9;</div><div>(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C =
20 22 6B 69 64 22 3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 =
2D 62 61 73 22 7D)</div>
<div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>=
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad <span dir=3D"ltr">&lt;<=
a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcella=
rs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal">&lt;not chair&gt;<u></u><u></u></p><p cl=
ass=3D"MsoNormal">
<u></u>=A0<u></u></p><p class=3D"MsoNormal">Richard,<u></u><u></u></p><p cl=
ass=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">I do not curr=
ently believe that this is a doable item.=A0 In order for me to believe oth=
erwise you will need to give a concrete proposal about how to solve the pro=
blem of things drifting back and forth.=A0 Given the text<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">{xxx}\r\=
r\rThis is the body<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></=
u></p><p class=3D"MsoNormal">How does one know where the dividing line betw=
een the JSON header and the body begins?=A0 Until this is completely solved=
 what you propose is not doable and the current method of base64 encoding w=
ill be required.<span class=3D"HOEnZb"><font color=3D"#888888"><u></u><u></=
u></font></span></p>
<span class=3D"HOEnZb"><font color=3D"#888888"><p class=3D"MsoNormal"><u></=
u>=A0<u></u></p><p class=3D"MsoNormal">Jim<u></u><u></u></p><p class=3D"Mso=
Normal"><u></u>=A0<u></u></p></font></span></div></div></blockquote></div><=
br></div>

--089e013c66b433cb7d04dee54570--

From ietf@augustcellars.com  Tue Jun 11 11:50:34 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC4B21F9811 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDqIpVP0dtzR for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:50:28 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 55E5E21F9808 for <jose@ietf.org>; Tue, 11 Jun 2013 11:50:28 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 6B4872CA2B; Tue, 11 Jun 2013 11:50:27 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>
References: <05fc01ce659d$d6a93f90$83fbbeb0$@augustcellars.com>	<CAL02cgQnFwsEa_uttfs_autGtjpO3a=jO3DMY-q_R0-g1=im0g@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781C117@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgTApZjGAh7xXGqSSNiGZnr1sFaXj2TmTwd67RMeaW3Bmg@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781D714@TK5EX14MBXC283.redmond.corp.microsoft.com>	<068101ce6603$3b27c440$b1774cc0$@augustcellars.com>	<4E1F6AAD24975D4BA5B16804296739436781E496@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgSHHfphb1PpQ3xpjQz3u-VMehjD1Zok5cJf0mxQiweJrA@mail.gmail.com>	<4E1F6AAD24975D4BA5B16804296739436781EE0B@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgSTqeoA7M86k7grMpR6VRhVACa6E5PmO8XMJT8z+2dq9g@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151B4309CA@WSMSG3153V.srv.dir.telstra.com>	<CAL02cgRK+h+ObexJgH-XHBm9z6K3-O4OegcYcBw+GXcVqK=gSg@mail.gmail.com>	<079801ce66c6$d3d59230$7b80b690$@augustcellars.com> <CAL02cgQQSZnSwMCL9NStO=KtbWSTxCmh_LL6mqV9UzC51GkGiQ@mail.gma il.com>
In-Reply-To: <CAL02cgQQSZnSwMCL9NStO=KtbWSTxCmh_LL6mqV9UzC51GkGiQ@mail.gmail.com>
Date: Tue, 11 Jun 2013 11:49:35 -0700
Message-ID: <07e001ce66d4$6b355400$419ffc00$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07E1_01CE6699.BEDA73A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG0QxNjNQen5xE7UI53mmuxyr9BfQI0cZ/ZAVlbblICaXzKXgJtpxE3Aatu5Z8CowcpxwGvHMtuAn9m6/oBuMfIzwIU/XcAAUIWDnUCLgAi0gITynHymJOFreA=
Content-Language: en-us
Cc: 'Mike Jones' <Michael.Jones@microsoft.com>, "'Manger, James H'" <James.H.Manger@team.telstra.com>, jose@ietf.org
Subject: Re: [jose] Possible change to protected field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 18:50:34 -0000

This is a multipart message in MIME format.

------=_NextPart_000_07E1_01CE6699.BEDA73A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Richard,

=20

Let=92s not confuse the text representation and the memory =
representation.
All that matters is that what would be presented to the hash function is =
the
byte sequence

=20

0x63 0x61 0x66 0xe9

=20

It does not matter what the escaped text string looks like as long as
everyone can read it in and get the correct byte sequence.

=20

Jim

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 10:34 AM
To: Jim Schaad
Cc: Manger, James H; Mike Jones; jose@ietf.org
Subject: Re: [jose] Possible change to protected field

=20

On Tue, Jun 11, 2013 at 1:12 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 7:11 AM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org


Subject: Re: [jose] Possible change to protected field

=20

On Mon, Jun 10, 2013 at 9:45 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:

>>> I was thinking about proposing that we make a change to the content =
of
the protected field in the JWS JSON serialization format.  If we encoded
this as a UTF8 string rather than the base64url encoded UTF8 string, =
then
the content would be smaller.

This would work. Mike's canonicalization worries are misplaced. =
Richard's
Chrome/Firefox "bug" seems wrong.

Example: JOSE originator creates the following header, with U+000A for =
line
ending.


{"alg": "RSA-OAEP",
"enc": "A256GCM",
"kid": "7"
}

This header consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 =
spaces
and 4 newlines). Put these 51 chars as the value of the "protected" =
field.

{"protected":"{\"alg\": \"RSA-OAEP\",\n\"enc\": \"A256GCM\",\n\"kid\":
\"7\"\n}\n"}

They appear as 51+16=3D67 chars inside the quotes of the "protected" =
field: 4
newlines are replaced with 4 n chars; plus 16 slashes are added. This =
step
could have used \u0022 instead of \", or \u000A or \u000a instead of \n, =
or
escaped any of the other 35 chars. But that doesn't matter since this
escaping will be removed by the first JSON parse at the other end, which
will gives the original 51 chars to its caller (in whatever native =
string
type the language uses).

If the originator used CRLF instead (giving 55 chars), the transmitted =
data
will be {"protected":"...\r\n...\r\n...\r\n...\r\n"}. The first JSON =
parse
at the recipient will recreate the correct 55 chars. No problem.

There is plenty of potential to confuse a human doing this manually as =
there
are 2 layers of JSON string escaping. It is well-defined enough for a
computer (or spec) though.


As to whether this is worthwhile...
In this specific example the base64url overhead would be +17 chars, =
merely 1
more char than the overhead of omitting the base64url step.


A more valuable change would be to apply the crypto operations AFTER
removing the base64url encoding. That is, apply the crypto to a
UTF-8-encoded JSON header, instead of to the US-ASCII encoding of the
base64url-encoded UTF-8-encoded JSON header. Implementations always need =
the
UTF-8 form at some point anyway. It means the crypto is applied to fewer
bytes so it is faster. It means an idea like Jim's that doesn't need
base64url to maintain the correct bytes in transmission doesn't need to
artificially add a base64url-encoding step at the receiver just to do =
the
crypto.


P.S.

>> the JSON parsers in both Chrome and Firefox (possible others; haven't
tried) choke on parsing strings that have control characters

JSON does not allow unescaped control chars when representing strings so
choking is the correct behaviour. JSON.parse(JSON.stringify(x)) works =
for me
in Chrome. JSON.stringify does NOT leave unescaped control chars in =
quotes
in the result.

=20

I have heard multiple independent reports of my incorrectness in this
experiment.  So I retract my assertion of infeasibility, with regard to
control characters.

=20

However, there's still an issue with code points that don't have to be
escaped. Consider the following example:

=20

var x =3D '{"a":"caf\\u00e9"}';

var x2 =3D JSON.stringify(JSON.parse(x))

=20

In a quick test of the environments I have on hand (several browsers +
Node.JS + PHP + Perl), I see a wide variety of behaviors, most of which
would break the signature.  The browsers and Node all converted the =
"\u00e9"
sequence to an unescaped "=E9" character, while Perl (creatively) =
rendered it
directly as a Latin-1 0xe9 byte.  Only PHP rendered it back to the =
escape
sequence.  Test code here:

<http://www.ipv.sx/jose/json_test.html>

=20

Now, even if we think that re-encoding is a problem, there's the =
question of
whether we think the risk is acceptable to achieve better human =
readability.
I'm pretty split, myself.

=20

Do you thing from your test that this would also be a problem if you did

=20

Base64(JSON.stringify(JSON.parse(Unbase64(x)))

=20

This would appear to be a general re-creation problem even if we use =
base64
encoding

=20

The base64 part in your line actually isn't relevant.  It's actually the
outer parse/stringify (on the overall JWE object) that we're worried =
about
changing the string. =20

=20

The control case for the experiment would be:

=20

var x =3D '{"a":"validBase64=3D=3D"}';

var x2 =3D JSON.stringify(JSON.parse(x))

=20

That works just fine with my standard test suite. =20

<http://www.ipv.sx/jose/json_test.html>

=20

--Richard

=20

=20

=20

Jim

=20

=20

--Richard

=20

=20


--
James Manger

=20

=20


------=_NextPart_000_07E1_01CE6699.BEDA73A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Richard,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Let&#8217;s not confuse the text representation and the memory =
representation. =A0All that matters is that what would be presented to =
the hash function is the byte sequence<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>0x63 0x61 0x66 0xe9<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>It does not matter what the escaped text string looks like as long as =
everyone can read it in and get the correct byte =
sequence.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Tuesday, June 11, =
2013 10:34 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> Manger, James H; =
Mike Jones; jose@ietf.org<br><b>Subject:</b> Re: [jose] Possible change =
to protected field<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Tue, =
Jun 11, 2013 at 1:12 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>] <br><b>Sent:</b> Tuesday, June 11, =
2013 7:11 AM<br><b>To:</b> Manger, James H<br><b>Cc:</b> Mike Jones; Jim =
Schaad; <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a></span><o:p></o:p></p><div><p =
class=3DMsoNormal><br><b>Subject:</b> Re: [jose] Possible change to =
protected field<o:p></o:p></p></div></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Mon, Jun =
10, 2013 at 9:45 PM, Manger, James H &lt;<a =
href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><div><div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5=
.0pt'><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&gt;&gt;&gt; I =
was thinking about proposing that we make a change to the content of the =
protected field in the JWS JSON serialization format.&nbsp; If we =
encoded this as a UTF8 string rather than the base64url encoded UTF8 =
string, then the content would be smaller.<o:p></o:p></p></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This would =
work. Mike's canonicalization worries are misplaced. Richard's =
Chrome/Firefox &quot;bug&quot; seems wrong.<br><br>Example: JOSE =
originator creates the following header, with U+000A for line =
ending.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>{&quot;alg&quo=
t;: &quot;RSA-OAEP&quot;,<br>&quot;enc&quot;: =
&quot;A256GCM&quot;,<br>&quot;kid&quot;: =
&quot;7&quot;<br>}<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>This header =
consists of 19+1+17+1+10+1+1+1=3D51 characters (including 3 spaces and 4 =
newlines). Put these 51 chars as the value of the &quot;protected&quot; =
field.<br><br>{&quot;protected&quot;:&quot;{\&quot;alg\&quot;: =
\&quot;RSA-OAEP\&quot;,\n\&quot;enc\&quot;: =
\&quot;A256GCM\&quot;,\n\&quot;kid\&quot;: =
\&quot;7\&quot;\n}\n&quot;}<br><br>They appear as 51+16=3D67 chars =
inside the quotes of the &quot;protected&quot; field: 4 newlines are =
replaced with 4 n chars; plus 16 slashes are added. This step could have =
used \u0022 instead of \&quot;, or \u000A or \u000a instead of \n, or =
escaped any of the other 35 chars. But that doesn't matter since this =
escaping will be removed by the first JSON parse at the other end, which =
will gives the original 51 chars to its caller (in whatever native =
string type the language uses).<br><br>If the originator used CRLF =
instead (giving 55 chars), the transmitted data will be =
{&quot;protected&quot;:&quot;...\r\n...\r\n...\r\n...\r\n&quot;}. The =
first JSON parse at the recipient will recreate the correct 55 chars. No =
problem.<br><br>There is plenty of potential to confuse a human doing =
this manually as there are 2 layers of JSON string escaping. It is =
well-defined enough for a computer (or spec) though.<br><br><br>As to =
whether this is worthwhile...<br>In this specific example the base64url =
overhead would be +17 chars, merely 1 more char than the overhead of =
omitting the base64url step.<br><br><br>A more valuable change would be =
to apply the crypto operations AFTER removing the base64url encoding. =
That is, apply the crypto to a UTF-8-encoded JSON header, instead of to =
the US-ASCII encoding of the base64url-encoded UTF-8-encoded JSON =
header. Implementations always need the UTF-8 form at some point anyway. =
It means the crypto is applied to fewer bytes so it is faster. It means =
an idea like Jim's that doesn't need base64url to maintain the correct =
bytes in transmission doesn't need to artificially add a =
base64url-encoding step at the receiver just to do the =
crypto.<br><br><br>P.S.<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&gt;&gt; the JSON =
parsers in both Chrome and Firefox (possible others; haven't tried) =
choke on parsing strings that have control =
characters<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>JSON does =
not allow unescaped control chars when representing strings so choking =
is the correct behaviour. JSON.parse(JSON.stringify(x)) works for me in =
Chrome. JSON.stringify does NOT leave unescaped control chars in quotes =
in the result.<o:p></o:p></p></blockquote><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I have =
heard multiple independent reports of my incorrectness in this =
experiment. &nbsp;So I retract my assertion of infeasibility, with =
regard to control characters.<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>However, =
there's still an issue with code points that don't have to be escaped. =
Consider the following example:<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>var x =3D =
'{&quot;a&quot;:&quot;caf\\u00e9&quot;}';<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>var x2 =3D =
JSON.stringify(JSON.parse(x))<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In a quick =
test of the environments I have on hand (several browsers + Node.JS + =
PHP + Perl), I see a wide variety of behaviors, most of which would =
break the signature. &nbsp;The browsers and Node all converted the =
&quot;\u00e9&quot; sequence to an unescaped &quot;=E9&quot; character, =
while Perl (creatively) rendered it directly as a Latin-1 0xe9 byte. =
&nbsp;Only PHP rendered it back to the escape sequence. &nbsp;Test code =
here:<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&lt;<a =
href=3D"http://www.ipv.sx/jose/json_test.html" =
target=3D"_blank">http://www.ipv.sx/jose/json_test.html</a>&gt;<o:p></o:p=
></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Now, even =
if we think that re-encoding is a problem, there's the question of =
whether we think the risk is acceptable to achieve better human =
readability. &nbsp;I'm pretty split, myself.<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Do you thing from your test that this would also be a problem if you =
did</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Base64(JSON.stringify(JSON.parse(Unbase64(x)))</span><o:p></o:p></p><p=
 class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This would appear to be a general re-creation problem even if we use =
base64 =
encoding</span><o:p></o:p></p></div></div></div></div></div></div></div><=
/blockquote><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The base64 part in your line actually isn't relevant. =
&nbsp;It's actually the outer parse/stringify (on the overall JWE =
object) that we're worried about changing the string. =
&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The control case for the experiment would =
be:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>var x =3D =
'{&quot;a&quot;:&quot;validBase64=3D=3D&quot;}';<o:p></o:p></p></div><div=
><p class=3DMsoNormal>var x2 =3D&nbsp;<span =
style=3D'color:#500050'>JSON.stringify(JSON.parse(x))</span><o:p></o:p></=
p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span style=3D'color:#500050'>That works just fine =
with my standard test suite. &nbsp;</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span style=3D'color:#500050'>&lt;<a =
href=3D"http://www.ipv.sx/jose/json_test.html">http://www.ipv.sx/jose/jso=
n_test.html</a>&gt;</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--Richard<o:=
p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5=
.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br><span =
style=3D'color:#888888'>--<br>James =
Manger</span><o:p></o:p></p></blockquote></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_07E1_01CE6699.BEDA73A0--


From rlb@ipv.sx  Tue Jun 11 11:58:26 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFB121F995A for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.205
X-Spam-Level: *
X-Spam-Status: No, score=1.205 tagged_above=-999 required=5 tests=[AWL=-1.573,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_43=0.6, RDNS_NONE=0.1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fo+BaXhAeXjN for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 11:58:22 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id EF11921F9956 for <jose@ietf.org>; Tue, 11 Jun 2013 11:58:21 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id k14so7907115oag.8 for <jose@ietf.org>; Tue, 11 Jun 2013 11:58:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ZBhHfcHaTmBG0uF4/DzO3IjBYlsXY7Y86IjzXonw7oE=; b=WdGanci2BcLms9GVi7KsE9Y3B7z/aMaU+IDobpauMLLpYV5BEnX07zawcHIwkuAdeC n3PZ40Nv1S2QOywMoWwxe6vNeMi9/VS67M2IcW6hzY6qQidPM4uvTCG8NpxgjkrG/p8Y tyQDAvl9SFh7SFftvuGWd7445VXX1UymFbnNaIpFE8gSJdO5Wxx81QLxUEvu2UjdjjCt v4LzHkeeTNxIItb+kN7xEghXCFN9gKNs8/MY4F8bVufTIxCuGguHXaCr0Bbm/OAJSA1L O8e4yLIRsDdxnfpO7h53iLXCKIwsrPAyblvj3ZpePZpSS3G8p7uEXGZ2O1lkdQ8avIJR Njsg==
MIME-Version: 1.0
X-Received: by 10.182.39.133 with SMTP id p5mr9444798obk.69.1370977101436; Tue, 11 Jun 2013 11:58:21 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 11:58:21 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678214FF@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <02b701ce5cb8$46ae77e0$d40b67a0$@augustcellars.com> <CAD9ie-vK3gY9b9GQrbUa=TACy5KVA1uPH_u_utucoKzVynjuiA@mail.gmail.com> <02f501ce5cc5$ec9a2200$c5ce6600$@augustcellars.com> <CAD9ie-uV-THE0+oL-dNUB0qXF7sx8jHMZDCz8vGESmUHWV=LMg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C58C4@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAD9ie-sm7q6gdzC-aTKt=+b=A8wB68ExTP1FwiT=zQTN7b69zA@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C5C0A@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR=Lh5_HogPtgoFM+qhwNkqOFaW0+TzOCAziUwK8ZqQaw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C7399@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgR6XfSwHxOLym_pkM+9EOE8yRUEncLToKbrLVJxoOgxDg@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9B69@TK5EX14MBXC285.redmond.corp.microsoft.com> <CAL02cgTrpkt0PyvLmnSKTchST5hgbzjkLQMq3hr6O2pij7LgjQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943677C9E95@TK5EX14MBXC285.redmond.corp.microsoft.com> <046301ce5d4d$15ecd2b0$41c67810$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678214FF@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Tue, 11 Jun 2013 14:58:21 -0400
Message-ID: <CAL02cgRDhf-2jjGM5Z1CPqf+AvA8a54nUQA6E0XOfmdXoA+V9A@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2e804206fba04dee57b07
X-Gm-Message-State: ALoCoQksCToJOEe5M/Z+y1e482XRqKlNU/F58QSWRxRJdgFoQdp1io8sMNjBuClWA+SOFHFGHNNL
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, Dick Hardt <dick.hardt@gmail.com>
Subject: Re: [jose] Should we delete the "typ" header field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 18:58:26 -0000

--001a11c2e804206fba04dee57b07
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Let me try to patch Jim's example and illustrate why there's no need for
"typ" here.  Starting with a JWT in an OAuth header:

Authorization: JWT { "typ": "JWT", "cty": "JWT", ... { "typ": "JWT", "cty":
"JWT", ... { "typ": "JWT", ... [ claims ] }}}

They "typ" does nothing here, because the type is always known from a level
up.  Worse, it introduces the possibility of conflict.  What if "cty" is
"JWT", but at the next level down, "typ" is not "JWT"?   I notice you
didn't answer Jim's question about this case, where the next level down has
"typ":"JWS" and not "JWT".

The following syntax, without "typ", gives you the same amount of
information:

Authorization: JWT { "cty": "JWT", ... { "cty": "JWT", ... { ... [ claims ]
}}}

--Richard
















On Mon, Jun 10, 2013 at 8:25 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Answering Jim=92s message that inadvertently went unanswered=85****
>
> ** **
>
> Neither of these would be correct because of the last =93cty=94:=94JWT=94=
 in both
> examples.  That=92s because a JWT Claims Set is not a JWT.  You would nee=
d to
> omit the last =93cty=94:=94JWT=94 in both examples for this to be correct=
.****
>
> ** **
>
> No, there is no overloading.  JWT uses the absence of a =93cty=94 value t=
o say
> that the payload is a JWT Claims Set =96 which is the default case.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Jim Schaad [mailto:ietf@augustcellars.com]
> *Sent:* Thursday, May 30, 2013 8:48 AM
> *To:* Mike Jones; 'Richard Barnes'
> *Cc:* jose@ietf.org; 'Dick Hardt'
>
> *Subject:* RE: [jose] Should we delete the "typ" header field****
>
>  ** **
>
> Ok =96 I am having some problems with this.  Looking at some concrete
> psudo-examples****
>
> ** **
>
> {typ:JWT, ctyp:JWT,=85{type:JWT, ctyp:JWT,=85{jwt claims object } }  ****
>
> ** **
>
> **1.       **would be a legal or a non-legal description of a signed and
> then encrypted set of JWT claims?****
>
> **2.       **Does it make a difference if there are or are not other
> header fields?****
>
> ** **
>
> {typ:JWE, ctyp:JWT,=85{type:JWS, ctyp:JWT,=85 {jwt claims object }}****
>
> ** **
>
> **1.       ** Would be a legal or a non-legal description of a signed and
> then encrypted set of JWT claims?****
>
> ** **
>
> If typ and ctyp are using the same space, does that mean that a JWT set o=
f
> claims and a JWT token are being overloaded on the what the string means?
> In one case it means a token and in the other case it means a set of clai=
ms.
> ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Mike Jones [mailto:Michael.Jones@microsoft.com<Michael.Jones@micr=
osoft.com>]
>
> *Sent:* Thursday, May 30, 2013 8:06 AM
> *To:* Richard Barnes
> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
> *Subject:* RE: [jose] Should we delete the "typ" header field****
>
> ** **
>
> No, =93cty=94 is used by the derived class to determine the type of the
> encapsulated field.  But that=92s not a complete description of the **ent=
ire
> object** - especially not the additional meaning imbued by the additional
> parameters the derived type may add to the JOSE header.  =93typ=94 is the=
re to
> provide the type of the entire object, including what you=92re calling th=
e
> wrapper parts.****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Thursday, May 30, 2013 7:58 AM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
> ** **
>
> Isn't that requirement met by "cty"?  The only thing JOSE adds is a crypt=
o
> wrapper around the real application content.  If you're an application, y=
ou
> know a JOSE object is the thing you want because it contains the content
> you want -- it's a JWT because it contains JWT claims.****
>
> ** **
>
> Inheritance is the wrong metaphor.  This is encapsulation of application
> data:****
>
> if (jws.valid && jws.cty =3D=3D "application/jwt_claims") {****
>
>     jwtClaims =3D jws.content;****
>
> }****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Thu, May 30, 2013 at 10:43 AM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> Thanks for sharing the S/MIME details.  Although I was actually making th=
e
> analogy to MIME =96 not S/MIME.  Like many analogies, it=92s imperfect, b=
ut I
> believe still illustrative.****
>
>  ****
>
> The reason that the analogy isn=92t perfect is that the JOSE data structu=
res
> are used to build application-specific data structures that are legal JOS=
E
> data structures but also have additional properties =96 including additio=
nal
> header fields with specific semantics.  (When we agreed to ignore
> not-understood header fields we let that horse out of the barn.)  For
> instance, Dick Hardt uses JWEs with issuer and audience fields in the
> headers, so they can be used by routing software.****
>
>  ****
>
> Think of JOSE as the base class and the application types built using it
> as derived classes.  JWT is a derived class.  Dick=92s structures are a
> derived class.  These derived classes sometimes need names.  That=92s wha=
t
> =93typ=94 is for.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, May 30, 2013 7:34 AM****
>
>
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
>  ****
>
> You're mixing up "typ" and "cty".  If you want to make the analogy to
> S/MIME, "cty" is the equivalent to Content-Type inside the protected MIME
> body; "typ" is the content-type on the outer MIME header.  Pasting in an
> example:****
>
>  ****
>
> -----BEGIN-----****
>
> Content-Type: application/pkcs7-mime; smime-type=3Dsigned-data;****
>
>      name=3Dsmime.p7m****
>
> Content-Transfer-Encoding: base64****
>
> Content-Disposition: attachment; filename=3Dsmime.p7m****
>
>  ****
>
> 567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4VQbnj7****
>
> 77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUujhJhjH****
>
> HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHGghyHh****
>
> 6YT64V0GhIGfHfQbnj75****
>
> -----END-----****
>
> <http://tools.ietf.org/html/rfc3851#section-3.4.2>****
>
>  ****
>
> The outer Content-Type, which is analogous to "typ", MUST be
> application/pkcs7-mime, with a parameter indicating the type of CMS objec=
t.
>  This is the same as requiring "typ" to be JWE or JWS.  The inner
> Content-Type (ASN.1/base64 encoded in the example) can be anything, just
> like "cty".****
>
>  ****
>
> --Richard****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
> On Thu, May 30, 2013 at 12:53 AM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> Requiring that the =93typ=94 value be only =93JWS=94 or =93JWE=94 would b=
e analogous
> to the MIME spec requiring that the Content-Type: field be only
> =93text/plain=94 or =93message/external-body=94.  It would render it usel=
ess.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Wednesday, May 29, 2013 8:03 PM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org; Dick Hardt****
>
>
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
>  ****
>
> If this is the level of "type" you're referring to, I think we should dro=
p
> it from the spec.  It's an application-layer thing that the app can add o=
r
> not according to its wishes.****
>
>  ****
>
> I'm with Dick on this.  I think we should either have a mandatory
> indicator of what type of JOSE object this, or nothing at all.   If the
> former, the allowable values are "JWE" and "JWS".  The "+JSON" options ar=
e
> non-sensical -- the app needs to know what it's parsing before it gets th=
is
> header.  While I have a preference for the former (for clarity), the latt=
er
> approach is also OK with me, since the MIME types are specific to JWE/JWS=
.
> ****
>
>  ****
>
> Another approach here would be to address the JSON and compact forms
> separately.  The JSON form has no need of "typ" at all, since the type of
> the object is completely clear from what fields are there, e.g.,
> "recipients" vs. "signatures".  For the compact form, we could do somethi=
ng
> like James's "E."/"S." prefix idea, which you need because the
> dot-separated components have different meanings and no field names to
> indicate this.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Wed, May 29, 2013 at 8:30 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> A standard library is unlikely to know the meanings of all possible =93ty=
p=94
> values =96 and more to the point, *it doesn=92t have to*.  It=92s the
> application=92s job to determine that =93this blob is a JOSE object=94 an=
d then
> pass it to a standard library, which will then ignore the =93typ=94 value=
.****
>
>  ****
>
> A standard JOSE library won=92t know what =93typ=94: =93JWT=94 means.  It=
 won=92t know
> what =93typ=94: =93BCGovToken=94 is, should the BC Government want to dec=
lare that
> it=92s using a token with particular characteristics.  It won=92t know wh=
at
> =93typ=94: =93XMPP=94 is, should XMPP want to declare that it=92s using a=
 JOSE data
> structure with particular characteristics.  Etc.****
>
>  ****
>
> All these values can be registered in the registry and used by
> applications that understand them.  That=92s the application=92s job =96 =
not the
> library=92s job.  The =93typ=94 field is just there so that applications =
have a
> standard place to make any such declarations that they may need.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
> *Sent:* Wednesday, May 29, 2013 5:18 PM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org****
>
>
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
>  ****
>
> I'd prefer to be able to use standard libraries for creating and parsing
> tokens, and not specialized libraries dependent on the use case.****
>
>  ****
>
> I strongly think we either drop "typ" or make it required.****
>
>  ****
>
> On Wed, May 29, 2013 at 5:03 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> It=92s fine for your application to specify that it=92s required for your=
 use
> case.  Not applications need it, so they shouldn=92t be forced to pay the
> space penalty of an unnecessary field.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Dick Hardt
> *Sent:* Wednesday, May 29, 2013 4:56 PM****
>
>
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
>  ****
>
> I use it all the time and my code would barf if it was not there.****
>
>  ****
>
> I think it should be required rather than be a hint if it is going ot be
> there.****
>
>  ****
>
> On Wed, May 29, 2013 at 4:40 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> I think the values just changed****
>
>  ****
>
> However the way you are using it would be an argument to say that it
> should be a required field.  Are you just using it as a hint if it exists
> and then looking at the rest of the fields if it is not present?****
>
>  ****
>
> Jim****
>
>  ****
>
>  ****
>
> *From:* Dick Hardt [mailto:dick.hardt@gmail.com]
> *Sent:* Wednesday, May 29, 2013 3:49 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Should we delete the "typ" header field****
>
>  ****
>
> Well, I have been using, but now realize the spec changed or I was
> confused.****
>
>  ****
>
> I had been setting "typ" to be either "JWE" or "JWS" depending on the typ=
e
> of token I was creating or parsing as it was easier than looking at "alg"=
*
> ***
>
>  ****
>
> As currently defined, I don't see value in "typ".****
>
>  ****
>
> -- Dick****
>
>  ****
>
>  ****
>
> On Wed, May 29, 2013 at 3:02 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> In reading the documents, I am trying to understand the justification for
> having the =93typ=94 header parameter in the JOSE documents.****
>
>  ****
>
> The purpose of the field is to hold the type of the object.  In the past,
> I believe that values which should now be placed in the cty field (such a=
s
> =93JWT=94) were placed in this field as well.  However the parameter is
> optional and an implementation cannot rely on its being present.  This
> means that for all practical purposes all of the code to determine the
> value of the type field from the values of the alg and enc fields.  If th=
e
> field was mandatory then this code would disappear at a fairly small spac=
e
> cost and I can understand why the parameter would be present.****
>
>  ****
>
> Can anybody justify why this field should be present in the document =96 =
or
> should it just disappear?****
>
>  ****
>
> Jim****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
>  ****
>
> --
> -- Dick ****
>
>
>
> ****
>
>  ****
>
> --
> -- Dick ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
>  ****
>
> --
> -- Dick ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
>  ****
>
> ** **
>

--001a11c2e804206fba04dee57b07
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Let me try to patch Jim&#39;s example and illustrate why t=
here&#39;s no need for &quot;typ&quot; here. =A0Starting with a JWT in an O=
Auth header:<div><br></div><div>Authorization: JWT { &quot;typ&quot;: &quot=
;JWT&quot;, &quot;cty&quot;: &quot;JWT&quot;, ... { &quot;typ&quot;: &quot;=
JWT&quot;, &quot;cty&quot;: &quot;JWT&quot;, ... { &quot;typ&quot;: &quot;J=
WT&quot;, ... [ claims ] }}}</div>
<div><br></div><div>They &quot;typ&quot; does nothing here, because the typ=
e is always known from a level up. =A0Worse, it introduces the possibility =
of conflict. =A0What if &quot;cty&quot; is &quot;JWT&quot;, but at the next=
 level down, &quot;typ&quot; is not &quot;JWT&quot;? =A0 I notice you didn&=
#39;t answer Jim&#39;s question about this case, where the next level down =
has &quot;typ&quot;:&quot;JWS&quot; and not &quot;JWT&quot;.</div>
<div><br></div><div>The following syntax, without &quot;typ&quot;, gives yo=
u the same amount of information:</div><div><br></div><div>Authorization: J=
WT { &quot;cty&quot;: &quot;JWT&quot;, ... { &quot;cty&quot;: &quot;JWT&quo=
t;, ... { ... [ claims ] }}}<br>
</div><div><br></div><div>--Richard</div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div><div><br></div><div><br></div>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Mon, Jun 10, 2013 at 8:25 PM, Mike Jones <span di=
r=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_bla=
nk">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Answering Jim=92s message=
 that inadvertently went unanswered=85<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Neither of these would be=
 correct because of the last =93cty=94:=94JWT=94 in both examples.=A0 That=
=92s because a JWT Claims Set is not a JWT.=A0 You would need to omit the
 last =93cty=94:=94JWT=94 in both examples for this to be correct.<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, there is no overloadi=
ng.=A0 JWT uses the absence of a =93cty=94 value to say that the payload is=
 a JWT Claims Set =96 which is the default case.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf=
@augustcellars.com</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 8:48 AM<br>
<b>To:</b> Mike Jones; &#39;Richard Barnes&#39;<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>; &#39;Dick Hardt&#39;</span></p><div><div class=3D"h5"><br>
<b>Subject:</b> RE: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Ok =96 I am having some p=
roblems with this. =A0Looking at some concrete psudo-examples<u></u><u></u>=
</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">{typ:JWT, ctyp:JWT,=85{ty=
pe:JWT, ctyp:JWT,=85{jwt claims object } }=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>1.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">would be a legal or =
a non-legal description of a signed and then encrypted set of JWT claims?<u=
></u><u></u></span></p>

<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>2.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Does it make a diffe=
rence if there are or are not other header fields?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">{typ:JWE, ctyp:JWT,=85{ty=
pe:JWS, ctyp:JWT,=85 {jwt claims object }}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>1.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0
</span></span></span><u></u><span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0Would be a legal =
or a non-legal description of a signed and then encrypted set of JWT claims=
?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If typ and ctyp are using=
 the same space, does that mean that a JWT set of claims and a JWT token ar=
e being overloaded on the what the string means?=A0 In one
 case it means a token and in the other case it means a set of claims.<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">mailto=
:Michael.Jones@microsoft.com</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 8:06 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> RE: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">No, =93cty=94 is used by =
the derived class to determine the type of the encapsulated field.=A0 But t=
hat=92s not a complete description of the *<b>entire object</b>*
 - especially not the additional meaning imbued by the additional parameter=
s the derived type may add to the JOSE header.=A0 =93typ=94 is there to pro=
vide the type of the entire object, including what you=92re calling the wra=
pper parts.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:58 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Isn&#39;t that requirement met by &quot;cty&quot;? =
=A0The only thing JOSE adds is a crypto wrapper around the real application=
 content. =A0If you&#39;re an application, you know a JOSE object is the th=
ing you want because it contains the content you want --
 it&#39;s a JWT because it contains JWT claims.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Inheritance is the wrong metaphor. =A0This is encaps=
ulation of application data:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">if (jws.valid &amp;&amp; jws.cty =3D=3D &quot;applic=
ation/jwt_claims&quot;) {<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 jwtClaims =3D jws.content;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">}<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 10:43 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks for sharing the S/=
MIME details.=A0 Although I was actually making the analogy to MIME =96 not
 S/MIME.=A0 Like many analogies, it=92s imperfect, but I believe still illu=
strative.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The reason that the analo=
gy isn=92t perfect is that the JOSE data structures are used to build appli=
cation-specific
 data structures that are legal JOSE data structures but also have addition=
al properties =96 including additional header fields with specific semantic=
s.=A0 (When we agreed to ignore not-understood header fields we let that ho=
rse out of the barn.)=A0 For instance,
 Dick Hardt uses JWEs with issuer and audience fields in the headers, so th=
ey can be used by routing software.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Think of JOSE as the base=
 class and the application types built using it as derived classes.=A0 JWT
 is a derived class.=A0 Dick=92s structures are a derived class.=A0 These d=
erived classes sometimes need names.=A0 That=92s what =93typ=94 is for.</sp=
an><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 7:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt<br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You&#39;re mixing up &quot;typ&quot; and &quot;cty&q=
uot;. =A0If you want to make the analogy to S/MIME, &quot;cty&quot; is the =
equivalent to Content-Type inside the protected MIME body; &quot;typ&quot; =
is the content-type on
 the outer MIME header. =A0Pasting in an example:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-----BEGIN-----<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Content-Type: application/pkcs7-mime; smime-type=3Ds=
igned-data;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0name=3Dsmime.p7m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Transfer-Encoding: base64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Content-Disposition: attachment; filename=3Dsmime.p7=
m<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">567GhIGfHfYT6ghyHhHUujpfyF4f8HHGTrfvhJhjH776tbB9HG4V=
Qbnj7<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">77n8HHGT9HG4VQpfyF467GhIGfHfYT6rfvbnj756tbBghyHhHUuj=
hJhjH<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">HUujhJh4VQpfyF467GhIGfHfYGTrfvbnjT6jH7756tbB9H7n8HHG=
ghyHh<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">6YT64V0GhIGfHfQbnj75<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">-----END-----<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://tools.ietf.org/html/rfc3851#se=
ction-3.4.2" target=3D"_blank">http://tools.ietf.org/html/rfc3851#section-3=
.4.2</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The outer Content-Type, which is analogous to &quot;=
typ&quot;, MUST be application/pkcs7-mime, with a parameter indicating the =
type of CMS object. =A0This is the same as requiring &quot;typ&quot; to
 be JWE or JWS. =A0The inner Content-Type (ASN.1/base64 encoded in the exam=
ple) can be anything, just like &quot;cty&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, May 30, 2013 at 12:53 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Requiring that the =93typ=
=94 value be only =93JWS=94 or =93JWE=94 would be analogous to the MIME spe=
c requiring
 that the Content-Type: field be only =93text/plain=94 or =93message/extern=
al-body=94.=A0 It would render it useless.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Wednesday, May 29, 2013 8:03 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a>; Dick Hardt</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">If this is the level of &quot;type&quot; you&#39;re =
referring to, I think we should drop it from the spec. =A0It&#39;s an appli=
cation-layer thing that the app can add or not according to its wishes.<u><=
/u><u></u></p>

<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;m with Dick on this. =A0I think we should eith=
er have a mandatory indicator of what type of JOSE object this, or nothing =
at all. =A0 If the former, the allowable values are &quot;JWE&quot;
 and &quot;JWS&quot;. =A0The &quot;+JSON&quot; options are non-sensical -- =
the app needs to know what it&#39;s parsing before it gets this header. =A0=
While I have a preference for the former (for clarity), the latter approach=
 is also OK with me, since the MIME types are specific to JWE/JWS.<u></u><u=
></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Another approach here would be to address the JSON a=
nd compact forms separately. =A0The JSON form has no need of &quot;typ&quot=
; at all, since the type of the object is completely clear from
 what fields are there, e.g., &quot;recipients&quot; vs. &quot;signatures&q=
uot;. =A0For the compact form, we could do something like James&#39;s &quot=
;E.&quot;/&quot;S.&quot; prefix idea, which you need because the dot-separa=
ted components have different meanings and no field names to indicate this.=
<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 8:30 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard library is unl=
ikely to know the meanings of all possible =93typ=94 values =96 and more to=
 the
 point, <b>it doesn=92t have to</b>.=A0 It=92s the application=92s job to d=
etermine that =93this blob is a JOSE object=94 and then pass it to a standa=
rd library, which will then ignore the =93typ=94 value.</span><u></u><u></u=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">A standard JOSE library w=
on=92t know what =93typ=94: =93JWT=94 means.=A0 It won=92t know what =93typ=
=94: =93BCGovToken=94
 is, should the BC Government want to declare that it=92s using a token wit=
h particular characteristics.=A0 It won=92t know what =93typ=94: =93XMPP=94=
 is, should XMPP want to declare that it=92s using a JOSE data structure wi=
th particular characteristics.=A0 Etc.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">All these values can be r=
egistered in the registry and used by applications that understand them.=A0
 That=92s the application=92s job =96 not the library=92s job.=A0 The =93ty=
p=94 field is just there so that applications have a standard place to make=
 any such declarations that they may need.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 5:18 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I&#39;d prefer to be able to use standard libraries =
for creating and parsing tokens, and not specialized libraries dependent on=
 the use case.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I strongly think we either drop &quot;typ&quot; or m=
ake it required.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 5:03 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">It=92s fine for your appl=
ication to specify that it=92s required for your use case.=A0 Not applicati=
ons
 need it, so they shouldn=92t be forced to pay the space penalty of an unne=
cessary field.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Wednesday, May 29, 2013 4:56 PM</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I use it all the time and my code would barf if it w=
as not there.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think it should be required rather than be a hint =
if it is going ot be there.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 4:40 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think the values just c=
hanged</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However the way you are u=
sing it would be an argument to say that it should be a required field.=A0
 Are you just using it as a hint if it exists and then looking at the rest =
of the fields if it is not present?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Dick Har=
dt [mailto:<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.h=
ardt@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, May 29, 2013 3:49 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we delete the &quot;typ&quot; header fiel=
d</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Well, I have been using, but now realize the spec ch=
anged or I was confused.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I had been setting &quot;typ&quot; to be either &quo=
t;JWE&quot; or &quot;JWS&quot; depending on the type of token I was creatin=
g or parsing as it was easier than looking at &quot;alg&quot;<u></u><u></u>=
</p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As currently defined, I don&#39;t see value in &quot=
;typ&quot;.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, May 29, 2013 at 3:02 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">In reading the documents, I am trying to understand =
the justification for having the =93typ=94 header parameter in the JOSE doc=
uments.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The purpose of the field is to hold the type of the =
object. =A0In the past, I believe that values which should now be placed in=
 the cty field (such as =93JWT=94) were placed in this field
 as well.=A0 However the parameter is optional and an implementation cannot=
 rely on its being present.=A0 This means that for all practical purposes a=
ll of the code to determine the value of the type field from the values of =
the alg and enc fields. =A0If the field
 was mandatory then this code would disappear at a fairly small space cost =
and I can understand why the parameter would be present.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Can anybody justify why this field should be present=
 in the document =96 or should it just disappear?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">--
<br>
-- Dick <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c2e804206fba04dee57b07--

From ietf@augustcellars.com  Tue Jun 11 12:17:07 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDCF621F99A5 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aooeEwD6UJN for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:17:01 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id DCE1221F939E for <jose@ietf.org>; Tue, 11 Jun 2013 12:17:01 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id B676738F12; Tue, 11 Jun 2013 12:17:00 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com>
In-Reply-To: <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com>
Date: Tue, 11 Jun 2013 12:16:08 -0700
Message-ID: <080001ce66d8$20be6200$623b2600$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0801_01CE669D.74609B70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVND51os6fEx5T7BPLe3ecRAXbKQKjfidwmA4rnTA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 19:17:07 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0801_01CE669D.74609B70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes, it is not a problem for JWE, however consider the case of JWS where
there is no distinction between how the protected data and the content =
are
processed.

=20

Jim

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 11:43 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: Issue #23 - Make crypto indepenent of binary encoding

=20

I don't know what you mean by "the problem of things drifting back and
forth".  Let me try to be more concrete.

=20

Consider the following JWE:

=20

{

    "header": { "alg": "dir" }

    "protect":
"eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ"

    ...

}

=20

The "protect" here is the encoding of the header '{"enc": "A128GCM", =
"kid":
"celui\r\n=E7a\r\n\tl=E0-bas"}'  (hex=3D63 65 6C 75 69 0A 0D C3 A7 61 0A =
0D 09 6C
C3 A0 2D 62 61 73).

=20

In the current draft, the AAD for the AEAD is the base64-encoded =
version.
The proposal here is just to make it the UTF-8 version, before
base64-encoding instead of after:

=20

OLD:

AAD =3D =
eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ=20

(=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 =
53 49 73
49 43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6e =
59
51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 51)

=20

NEW:=20

AAD =3D '{"enc": "A128GCM", "kid": "celui\r\n=E7a\r\n\tl=E0-bas"}'

(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C 20 22 6B =
69 64 22
3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73 22 =
7D)

=20

=20

=20

=20

=20

=20

=20

On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:

<not chair>

=20

Richard,

=20

I do not currently believe that this is a doable item.  In order for me =
to
believe otherwise you will need to give a concrete proposal about how to
solve the problem of things drifting back and forth.  Given the text

=20

{xxx}\r\r\rThis is the body

=20

How does one know where the dividing line between the JSON header and =
the
body begins?  Until this is completely solved what you propose is not =
doable
and the current method of base64 encoding will be required.

=20

Jim

=20

=20


------=_NextPart_000_0801_01CE669D.74609B70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yes, it is not a problem for JWE, however consider the case of JWS =
where there is no distinction between how the protected data and the =
content are processed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Tuesday, June 11, =
2013 11:43 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: Issue #23 - Make crypto indepenent =
of binary encoding<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I don't =
know what you mean by &quot;the problem of things drifting back and =
forth&quot;. &nbsp;Let me try to be more concrete.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Consider the following =
JWE:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>{<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; =
&nbsp; &quot;header&quot;: { &quot;alg&quot;: &quot;dir&quot; =
}<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; =
&quot;protect&quot;: =
&quot;eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ&=
quot;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; &nbsp; =
...<o:p></o:p></p></div><div><p =
class=3DMsoNormal>}<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The &quot;protect&quot; here is the encoding of the =
header '{&quot;enc&quot;: &quot;A128GCM&quot;, &quot;kid&quot;: =
&quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}' &nbsp;(hex=3D63 65 6C 75 69 0A =
0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73).<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In the current draft, the AAD for the AEAD is the =
base64-encoded version. &nbsp;The proposal here is just to make it the =
UTF-8 version, before base64-encoding instead of =
after:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OLD:<o:p></o:p></p></div><div><p class=3DMsoNormal>AAD =
=3D =
eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ&nbsp;<=
o:p></o:p></p></div><div><p class=3DMsoNormal>(=3D=3D 65 79 4a 6c 62 6d =
4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 53 49 73 49 43 4a 72 61 57 =
51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6e 59 51 6f 4e 43 57 =
7a 44 6f 43 31 69 59 58 4d 69 66 51)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>NEW:&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>AAD =3D '{&quot;enc&quot;: &quot;A128GCM&quot;, =
&quot;kid&quot;: =
&quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}'<o:p></o:p></p></div><div><p =
class=3DMsoNormal>(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 =
4D 22 2C 20 22 6B 69 64 22 3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D =
09 6C C3 A0 2D 62 61 73 22 7D)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&lt;not =
chair&gt;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Richard,<o:p=
></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I do not =
currently believe that this is a doable item.&nbsp; In order for me to =
believe otherwise you will need to give a concrete proposal about how to =
solve the problem of things drifting back and forth.&nbsp; Given the =
text<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>{xxx}\r\r\rT=
his is the body<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>How does =
one know where the dividing line between the JSON header and the body =
begins?&nbsp; Until this is completely solved what you propose is not =
doable and the current method of base64 encoding will be =
required.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>Jim<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0801_01CE669D.74609B70--


From trac+jose@trac.tools.ietf.org  Tue Jun 11 12:50:33 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34AE21F997D for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CkO3MEfflubU for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:50:32 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id DAE3021F997C for <jose@ietf.org>; Tue, 11 Jun 2013 12:50:26 -0700 (PDT)
Received: from localhost ([127.0.0.1]:46361 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UmUaC-0006g8-QH; Tue, 11 Jun 2013 21:50:20 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx
X-Trac-Project: jose
Date: Tue, 11 Jun 2013 19:50:20 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:1
Message-ID: <064.88846e82adbed9643c92f330ebd4059d@trac.tools.ietf.org>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 23
In-Reply-To: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130611195031.DAE3021F997C@ietfa.amsl.com>
Resent-Date: Tue, 11 Jun 2013 12:50:26 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 19:50:33 -0000

#23: Make crypto independent of binary encoding (base64)

Changes (by rlb@ipv.sx):

 * owner:  draft-barnes-jose-use-cases@tools.ietf.org => draft-ietf-jose-
     json-web-encryption@tools.ietf.org
 * component:  draft-barnes-jose-use-cases => json-web-encryption


Comment:

 Update: I missed the fact that (1) JWS signs over the encoded octets, and
 (2) JWS adds an unnecessary "." character to the signed value.  So
 consider this proposal extended to include the following change:

 <http://tools.ietf.org/html/draft-ietf-jose-json-web-
 signature-11#section-5.1>
 OLD: JWS Signing Input  The concatenation of the Encoded JWS Header, a
 period ('.') character, and the Encoded JWS Payload.
 NEW: JWS Signing Input  The concatenation of the JWS Header and the JWS
 Payload.

 This is the same as what CMS does, except in the reverse order.  (In CMS,
 you sign over payload || signedAttrs.)

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:1>
jose <http://tools.ietf.org/jose/>


From rlb@ipv.sx  Tue Jun 11 12:50:52 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B39921F997C for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.325
X-Spam-Level: 
X-Spam-Status: No, score=-0.325 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Go8jF6TOI6n for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 12:50:47 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id E502E21F9972 for <jose@ietf.org>; Tue, 11 Jun 2013 12:50:46 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so3386502oah.11 for <jose@ietf.org>; Tue, 11 Jun 2013 12:50:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=4HeQCIySrm/4+vFlCNM6Rjh7pQn4045FPdb/GsPhGLg=; b=l2EHxBEBwO5x51GPqNg7ofrsTwgbeZ2nX65OfzBhE2omMXbRXSQJQMPdbx+7hbeBrt VEQSstmNq3sQsnftZdyDCbpMj6hHH/cM5uMU1bp75BcKmySo7Z4C3uFogzqY2PpxSMRU MND5Th2G3vkhiiONSoR6mhUxnQY9HRzGazAU3eUE+mIch6sA1cCqe0N/GBevnVfrVzZH VHbSOcZQXdiZdphg6djv7LBMrYjGHgnJdgnXD5dKB/wVNCOV0n3OHHsV/R/52we61zTv hUOcxfHJhOCoaUxCZx0SyO7CVuWj+E3hmv/HjTW6F03E2gBHj/RfIY2KHG15GAMpBiCS g8qw==
MIME-Version: 1.0
X-Received: by 10.60.43.232 with SMTP id z8mr12801386oel.138.1370980245456; Tue, 11 Jun 2013 12:50:45 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 12:50:45 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <080001ce66d8$20be6200$623b2600$@augustcellars.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com>
Date: Tue, 11 Jun 2013 15:50:45 -0400
Message-ID: <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a113311fc86a65b04dee63612
X-Gm-Message-State: ALoCoQlRxKxmUurNpC1bN3sH208NOH6xweTCSUBAiQk57FGP6Kq3dOAMa3Q02L+fBZVCPDNjWxzY
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 19:50:52 -0000

--001a113311fc86a65b04dee63612
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Still not understanding the problem.  Things are still clearly separated in
JWS:

{
    "protected_header": "eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9"
    "payload": "AQIDBA"
}

Here the protected_header is base64('{"alg":"RS256","kid":"jim"}') and the
payload is base64(0x01020304).

OLD:
Signature is
over: eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJSUzI1NiIsImtpZCI6Impp=
bSJ9
=3D=3D 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d 74=
 70
5a 43 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 53
55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39

NEW:
Signature is over: {"alg":"RS256","kid":"jim"}
=3D=3D 01 02 03 04 7b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 64=
 22
3a 22 6a 69 6d 22 7d 01 02 03 04

That is, just decode the two octet strings, convert the protected_header to
UTF-8, and concatenate them.  (This extends the proposal to also get rid of
the "." in the middle, since it's not necessary.  I updated the issue.)

No ambiguity.

--Richard






On Tue, Jun 11, 2013 at 3:16 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> Yes, it is not a problem for JWE, however consider the case of JWS where
> there is no distinction between how the protected data and the content ar=
e
> processed.****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Tuesday, June 11, 2013 11:43 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
> ** **
>
> I don't know what you mean by "the problem of things drifting back and
> forth".  Let me try to be more concrete.****
>
> ** **
>
> Consider the following JWE:****
>
> ** **
>
> {****
>
>     "header": { "alg": "dir" }****
>
>     "protect":
> "eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ"****
>
>     ...****
>
> }****
>
> ** **
>
> The "protect" here is the encoding of the header '{"enc": "A128GCM",
> "kid": "celui\r\n=E7a\r\n\tl=E0-bas"}'  (hex=3D63 65 6C 75 69 0A 0D C3 A7=
 61 0A
> 0D 09 6C C3 A0 2D 62 61 73).****
>
> ** **
>
> In the current draft, the AAD for the AEAD is the base64-encoded version.
>  The proposal here is just to make it the UTF-8 version, before
> base64-encoding instead of after:****
>
> ** **
>
> OLD:****
>
> AAD =3D eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMif=
Q *
> ***
>
> (=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 53=
 49
> 73 49 43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6=
e
> 59 51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 51)****
>
> ** **
>
> NEW: ****
>
> AAD =3D '{"enc": "A128GCM", "kid": "celui\r\n=E7a\r\n\tl=E0-bas"}'****
>
> (=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C 20 22 6B 69=
 64
> 22 3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73 2=
2
> 7D)****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <not chair>****
>
>  ****
>
> Richard,****
>
>  ****
>
> I do not currently believe that this is a doable item.  In order for me t=
o
> believe otherwise you will need to give a concrete proposal about how to
> solve the problem of things drifting back and forth.  Given the text****
>
>  ****
>
> {xxx}\r\r\rThis is the body****
>
>  ****
>
> How does one know where the dividing line between the JSON header and the
> body begins?  Until this is completely solved what you propose is not
> doable and the current method of base64 encoding will be required.****
>
>  ****
>
> Jim****
>
>  ****
>
> ** **
>

--001a113311fc86a65b04dee63612
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Still not understanding the problem. =A0Things are still c=
learly separated in JWS:<div><br></div><div>{</div><div>=A0 =A0 &quot;prote=
cted_header&quot;: &quot;eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9&quot;</div><d=
iv>=A0 =A0 &quot;payload&quot;: &quot;AQIDBA&quot;</div>
<div>}</div><div><br></div><div>Here the protected_header is base64(&#39;{&=
quot;alg&quot;:&quot;RS256&quot;,&quot;kid&quot;:&quot;jim&quot;}&#39;) and=
 the payload is base64(0x01020304).</div><div><br></div><div>OLD:=A0</div>
<div>Signature is over:=A0eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJS=
UzI1NiIsImtpZCI6ImppbSJ9</div><div>=3D=3D=A065 79 4a 68 62 47 63 69 4f 69 4=
a 53 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 3=
9 2e 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d 74 7=
0 5a 43 49 36 49 6d 70 70 62 53 4a 39</div>
<div><br></div><div>NEW:</div><div>Signature is over: {&quot;alg&quot;:&quo=
t;RS256&quot;,&quot;kid&quot;:&quot;jim&quot;}</div><div>=3D=3D=A001 02 03 =
04 7b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 64 22 3a 22 6a 69 =
6d 22 7d 01 02 03 04</div>
<div><br></div><div>That is, just decode the two octet strings, convert the=
 protected_header to UTF-8, and concatenate them. =A0(This extends the prop=
osal to also get rid of the &quot;.&quot; in the middle, since it&#39;s not=
 necessary. =A0I updated the issue.)</div>
<div><br></div><div>No ambiguity.</div><div><br></div><div>--Richard</div><=
div><br></div><div><br></div><div><br></div><div><br></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jun 11, 2013 at=
 3:16 PM, Jim Schaad <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcel=
lars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">Yes, it is not a problem for JWE, however co=
nsider the case of JWS where there is no distinction between how the protec=
ted data and the content are processed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D=
"_blank">rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 11:43 AM<br><b>To:</b> Jim Schaad<br><b=
>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</=
a><br><b>Subject:</b> Re: Issue #23 - Make crypto indepenent of binary enco=
ding<u></u><u></u></span></p>
</div></div><div><div class=3D"h5"><p class=3D"MsoNormal"><u></u>=A0<u></u>=
</p><div><p class=3D"MsoNormal">I don&#39;t know what you mean by &quot;the=
 problem of things drifting back and forth&quot;. =A0Let me try to be more =
concrete.<u></u><u></u></p>
<div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"Mso=
Normal">Consider the following JWE:<u></u><u></u></p></div><div><p class=3D=
"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal">{<u></u>=
<u></u></p>
</div><div><p class=3D"MsoNormal">=A0 =A0 &quot;header&quot;: { &quot;alg&q=
uot;: &quot;dir&quot; }<u></u><u></u></p></div><div><p class=3D"MsoNormal">=
=A0 =A0 &quot;protect&quot;: &quot;eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2Vs=
dWkKDcOnYQoNCWzDoC1iYXMifQ&quot;<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">=A0 =A0 ...<u></u><u></u></p></div><div><=
p class=3D"MsoNormal">}<u></u><u></u></p></div><div><p class=3D"MsoNormal">=
<u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal">The &quot;protect&qu=
ot; here is the encoding of the header &#39;{&quot;enc&quot;: &quot;A128GCM=
&quot;, &quot;kid&quot;: &quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}&#39; =A0(=
hex=3D63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73).<u></u><=
u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">In the current draft, the AAD for the AEAD is the base64-enc=
oded version. =A0The proposal here is just to make it the UTF-8 version, be=
fore base64-encoding instead of after:<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">OLD:<u></u><u></u></p></div><div><p class=3D"MsoNormal">AAD =
=3D eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ=A0<u=
></u><u></u></p>
</div><div><p class=3D"MsoNormal">(=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 =
69 51 54 45 79 4f 45 64 44 54 53 49 73 49 43 4a 72 61 57 51 69 4f 69 41 69 =
59 32 56 73 64 57 6b 4b 44 63 4f 6e 59 51 6f 4e 43 57 7a 44 6f 43 31 69 59 =
58 4d 69 66 51)<u></u><u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal">NEW:=A0<u></u><u></u></p></div><div><p class=3D"MsoNormal">A=
AD =3D &#39;{&quot;enc&quot;: &quot;A128GCM&quot;, &quot;kid&quot;: &quot;c=
elui\r\n=E7a\r\n\tl=E0-bas&quot;}&#39;<u></u><u></u></p>
</div><div><p class=3D"MsoNormal">(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 =
32 38 47 43 4D 22 2C 20 22 6B 69 64 22 3A 20 22 63 65 6C 75 69 0A 0D C3 A7 =
61 0A 0D 09 6C C3 A0 2D 62 61 73 22 7D)<u></u><u></u></p></div><div><p clas=
s=3D"MsoNormal">
<u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p=
></div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=
=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"MsoNormal"><u></=
u>=A0<u></u></p>
</div><div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div><div><p =
class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p><di=
v><p class=3D"MsoNormal">On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad &lt;<a=
 href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellar=
s.com</a>&gt; wrote:<u></u><u></u></p>
<div><div><p class=3D"MsoNormal">&lt;not chair&gt;<u></u><u></u></p><p clas=
s=3D"MsoNormal">=A0<u></u><u></u></p><p class=3D"MsoNormal">Richard,<u></u>=
<u></u></p><p class=3D"MsoNormal">=A0<u></u><u></u></p><p class=3D"MsoNorma=
l">I do not currently believe that this is a doable item.=A0 In order for m=
e to believe otherwise you will need to give a concrete proposal about how =
to solve the problem of things drifting back and forth.=A0 Given the text<u=
></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p><p class=3D"MsoNormal">{xxx}\r\=
r\rThis is the body<u></u><u></u></p><p class=3D"MsoNormal">=A0<u></u><u></=
u></p><p class=3D"MsoNormal">How does one know where the dividing line betw=
een the JSON header and the body begins?=A0 Until this is completely solved=
 what you propose is not doable and the current method of base64 encoding w=
ill be required.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0<u></u><u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"color:#888888">Jim<u></u><u></u=
></span></p><p class=3D"MsoNormal"><span style=3D"color:#888888">=A0<u></u>=
<u></u></span></p>
</div></div></div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div><=
/div></div></div></div></blockquote></div><br></div>

--001a113311fc86a65b04dee63612--

From trac+jose@trac.tools.ietf.org  Tue Jun 11 13:23:43 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A145721F99EE for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 13:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xrxt+ULkECeO for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 13:23:39 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id CA26821F99ED for <jose@ietf.org>; Tue, 11 Jun 2013 13:23:34 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48908 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UmV6C-0001T7-KD; Tue, 11 Jun 2013 22:23:24 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, rlb@ipv.sx
X-Trac-Project: jose
Date: Tue, 11 Jun 2013 20:23:24 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/24
Message-ID: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 24
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, rlb@ipv.sx, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130611202334.CA26821F99ED@ietfa.amsl.com>
Resent-Date: Tue, 11 Jun 2013 13:23:34 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #24: Move JWS headers into signature block
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 20:23:43 -0000

#24: Move JWS headers into signature block

 The JWS JSON serialization currently has a header and protected header at
 the top level and at the per-signature level.  The ones at the top level
 are unnecessary, since every signer can do things differently, and each
 can choose to sign different attributes.  So both protected and
 unprotected headers should move into the "signatures" objects.

 OLD:
 """
      {"protected":<integrity-protected shared header contents>",
       "unprotected":<non-integrity-protected shared header contents>",
       "payload":"<payload contents>"
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "signature":"<signature N contents>"}],
      }
 """

 NEW:
 """
      {
       "payload":"<payload contents>"
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "protected":"<per-signature protected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "protected":"<per-signature protected header N contents>",
         "signature":"<signature N contents>"}],
      }
 """

 This makes the compact form equivalent to:

 {
     "payload": "<JWS Encoded Payload>",
     "signatures": [{
         "protected": "<JWS Encoded Header>",
         "signature": "<JWS Signature Value>"
     }]
 }

 It also makes detached signatures natural, since you just can take the
 object out of the signatures array.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |      Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  signature@tools.ietf.org
 Priority:  major        |     Status:  new
Component:  json-web-    |  Milestone:
  signature              |    Version:
 Severity:  -            |   Keywords:
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/24>
jose <http://tools.ietf.org/jose/>


From ietf@augustcellars.com  Tue Jun 11 14:03:48 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F23321F99E2 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8phZ5SXBvAin for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:03:41 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 07CE421F99E3 for <jose@ietf.org>; Tue, 11 Jun 2013 14:03:35 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 9AFAC2CA25; Tue, 11 Jun 2013 14:03:25 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com>	<CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com>	<080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com>
In-Reply-To: <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com>
Date: Tue, 11 Jun 2013 14:02:33 -0700
Message-ID: <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0815_01CE66AC.52150380"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVND51os6fEx5T7BPLe3ecRAXbKQKjfidwAyLgE2MCjiSlRZfgvSmg
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 21:03:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0815_01CE66AC.52150380
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes =96 you are still not understanding the problem.

=20

There is an interesting issue that comes up in computing hash values of
multiple things which are concatenated together.  This issue is that it =
is
possible to move items from one thing to an adjacent thing and still get =
the
same hash value.

=20

Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93aaabbb=94 =
as the value being
hashed.

If field1=3D=94aa=94 and field2=3D=94abbb=94 you still get the same =
=93aaabbb=94 as the
value being hashed but different ideas of what the two fields are.

=20

There are three classic ways to deal with this problem:

=20

1.       Use  length prefix on each field =96 this is the ASN.1 encode =
it
version

2.       Use fields that are well defined in terms of delimiters

3.       Put in separation characters which are not allowed in either =
field.

=20

I once tried to argue that this is what we should do and ended up with =
the
following:  Method one was not considered acceptable, method two was not
possible given the current state of JSON parsers, method three is what =
we
currently do.

=20

JSON parsers allow for indefinite amounts of whitespace following a JSON
object so that will always be a problem.  Additionally there are JSON
parsers which believe they can stop parsing and not produce an error =
once it
has fully built a top level object.  Thus they consider the string
=91{=93a=94:=93b=94}FRED=94 to be something that can be successfully =
parsed.

=20

This allows for an attacker to move items from the content to the =
protected
string unless there is an externally imposed rule about what happens for
trailing characters after the protected content.

=20

Jim

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 12:51 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: Issue #23 - Make crypto indepenent of binary encoding

=20

Still not understanding the problem.  Things are still clearly separated =
in
JWS:

=20

{

    "protected_header": "eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9"

    "payload": "AQIDBA"

}

=20

Here the protected_header is base64('{"alg":"RS256","kid":"jim"}') and =
the
payload is base64(0x01020304).

=20

OLD:=20

Signature is over:
eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9=


=3D=3D 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d =
74 70
5a 43 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a =
53
55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39

=20

NEW:

Signature is over: {"alg":"RS256","kid":"jim"}

=3D=3D 01 02 03 04 7b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 =
64 22
3a 22 6a 69 6d 22 7d 01 02 03 04

=20

That is, just decode the two octet strings, convert the protected_header =
to
UTF-8, and concatenate them.  (This extends the proposal to also get rid =
of
the "." in the middle, since it's not necessary.  I updated the issue.)

=20

No ambiguity.

=20

--Richard

=20

=20

=20

=20

=20

On Tue, Jun 11, 2013 at 3:16 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:

Yes, it is not a problem for JWE, however consider the case of JWS where
there is no distinction between how the protected data and the content =
are
processed.

=20

Jim

=20

=20

From: Richard Barnes [mailto:rlb@ipv.sx]=20
Sent: Tuesday, June 11, 2013 11:43 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: Issue #23 - Make crypto indepenent of binary encoding

=20

I don't know what you mean by "the problem of things drifting back and
forth".  Let me try to be more concrete.

=20

Consider the following JWE:

=20

{

    "header": { "alg": "dir" }

    "protect":
"eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ"

    ...

}

=20

The "protect" here is the encoding of the header '{"enc": "A128GCM", =
"kid":
"celui\r\n=E7a\r\n\tl=E0-bas"}'  (hex=3D63 65 6C 75 69 0A 0D C3 A7 61 0A =
0D 09 6C
C3 A0 2D 62 61 73).

=20

In the current draft, the AAD for the AEAD is the base64-encoded =
version.
The proposal here is just to make it the UTF-8 version, before
base64-encoding instead of after:

=20

OLD:

AAD =3D =
eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ=20

(=3D=3D 65 79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 =
53 49 73
49 43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6e =
59
51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 51)

=20

NEW:=20

AAD =3D '{"enc": "A128GCM", "kid": "celui\r\n=E7a\r\n\tl=E0-bas"}'

(=3D=3D 7B 22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C 20 22 6B =
69 64 22
3A 20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73 22 =
7D)

=20

=20

=20

=20

=20

=20

=20

On Tue, Jun 11, 2013 at 2:12 PM, Jim Schaad <ietf@augustcellars.com> =
wrote:

<not chair>

=20

Richard,

=20

I do not currently believe that this is a doable item.  In order for me =
to
believe otherwise you will need to give a concrete proposal about how to
solve the problem of things drifting back and forth.  Given the text

=20

{xxx}\r\r\rThis is the body

=20

How does one know where the dividing line between the JSON header and =
the
body begins?  Until this is completely solved what you propose is not =
doable
and the current method of base64 encoding will be required.

=20

Jim

=20

=20

=20


------=_NextPart_000_0815_01CE66AC.52150380
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:873157703;
	mso-list-type:hybrid;
	mso-list-template-ids:759726340 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yes &#8211; you are still not understanding the =
problem.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There is an interesting issue that comes up in computing hash values =
of multiple things which are concatenated together.=A0 This issue is =
that it is possible to move items from one thing to an adjacent thing =
and still get the same hash value.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thus if field1=3D&#8221;aaa&#8221; and field2=3D&#8221;bbb&#8221; you =
get &#8220;aaabbb&#8221; as the value being =
hashed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If field1=3D&#8221;aa&#8221; and field2=3D&#8221;abbb&#8221; you =
still get the same &#8220;aaabbb&#8221; as the value being hashed but =
different ideas of what the two fields are.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There are three classic ways to deal with this =
problem:<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Use =A0length prefix on each field &#8211; this is the ASN.1 encode =
it version<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Use fields that are well defined in terms of =
delimiters<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Put in separation characters which are not allowed in either =
field.<o:p></o:p></span></p><p class=3DMsoListParagraph><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I once tried to argue that this is what we should do and ended up =
with the following:=A0 Method one was not considered acceptable, method =
two was not possible given the current state of JSON parsers, method =
three is what we currently do.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>JSON parsers allow for indefinite amounts of whitespace following a =
JSON object so that will always be a problem.=A0 Additionally there are =
JSON parsers which believe they can stop parsing and not produce an =
error once it has fully built a top level object.=A0 Thus they consider =
the string &#8216;{&#8220;a&#8221;:&#8220;b&#8221;}FRED&#8221; to be =
something that can be successfully parsed.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This allows for an attacker to move items from the content to the =
protected string unless there is an externally imposed rule about what =
happens for trailing characters after the protected =
content.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Tuesday, June 11, =
2013 12:51 PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: Issue #23 - Make crypto indepenent =
of binary encoding<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Still =
not understanding the problem. &nbsp;Things are still clearly separated =
in JWS:<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>{<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp; =
&nbsp; &quot;protected_header&quot;: =
&quot;eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9&quot;<o:p></o:p></p></div><div=
><p class=3DMsoNormal>&nbsp; &nbsp; &quot;payload&quot;: =
&quot;AQIDBA&quot;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>}<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Here the protected_header is =
base64('{&quot;alg&quot;:&quot;RS256&quot;,&quot;kid&quot;:&quot;jim&quot=
;}') and the payload is base64(0x01020304).<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OLD:&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Signature is =
over:&nbsp;eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJSUzI1NiIsImtpZ=
CI6ImppbSJ9<o:p></o:p></p></div><div><p class=3DMsoNormal>=3D=3D&nbsp;65 =
79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a =
43 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 53 =
55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a =
39<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>NEW:<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Signature is over: =
{&quot;alg&quot;:&quot;RS256&quot;,&quot;kid&quot;:&quot;jim&quot;}<o:p><=
/o:p></p></div><div><p class=3DMsoNormal>=3D=3D&nbsp;01 02 03 04 7b 22 =
61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 64 22 3a 22 6a 69 6d 22 =
7d 01 02 03 04<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>That is, just decode the two octet strings, convert =
the protected_header to UTF-8, and concatenate them. &nbsp;(This extends =
the proposal to also get rid of the &quot;.&quot; in the middle, since =
it's not necessary. &nbsp;I updated the =
issue.)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>No ambiguity.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Tue, Jun 11, 2013 at 3:16 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yes, it is not a problem for JWE, however consider the case of JWS =
where there is no distinction between how the protected data and the =
content are processed.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>] <br><b>Sent:</b> Tuesday, June 11, =
2013 11:43 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 - =
Make crypto indepenent of binary =
encoding</span><o:p></o:p></p></div></div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I don't =
know what you mean by &quot;the problem of things drifting back and =
forth&quot;. &nbsp;Let me try to be more concrete.<o:p></o:p></p><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Consider =
the following JWE:<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>{<o:p></o:p>=
</p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp; =
&nbsp; &quot;header&quot;: { &quot;alg&quot;: &quot;dir&quot; =
}<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp; =
&nbsp; &quot;protect&quot;: =
&quot;eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ&=
quot;<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp; =
&nbsp; ...<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>}<o:p></o:p>=
</p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The =
&quot;protect&quot; here is the encoding of the header =
'{&quot;enc&quot;: &quot;A128GCM&quot;, &quot;kid&quot;: =
&quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}' &nbsp;(hex=3D63 65 6C 75 69 0A =
0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73).<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In the =
current draft, the AAD for the AEAD is the base64-encoded version. =
&nbsp;The proposal here is just to make it the UTF-8 version, before =
base64-encoding instead of after:<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>OLD:<o:p></o=
:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>AAD =3D =
eyJlbmMiOiAiQTEyOEdDTSIsICJraWQiOiAiY2VsdWkKDcOnYQoNCWzDoC1iYXMifQ&nbsp;<=
o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(=3D=3D 65 =
79 4a 6c 62 6d 4d 69 4f 69 41 69 51 54 45 79 4f 45 64 44 54 53 49 73 49 =
43 4a 72 61 57 51 69 4f 69 41 69 59 32 56 73 64 57 6b 4b 44 63 4f 6e 59 =
51 6f 4e 43 57 7a 44 6f 43 31 69 59 58 4d 69 66 =
51)<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>NEW:&nbsp;<o=
:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>AAD =3D =
'{&quot;enc&quot;: &quot;A128GCM&quot;, &quot;kid&quot;: =
&quot;celui\r\n=E7a\r\n\tl=E0-bas&quot;}'<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>(=3D=3D 7B =
22 65 6E 63 22 3A 20 22 41 31 32 38 47 43 4D 22 2C 20 22 6B 69 64 22 3A =
20 22 63 65 6C 75 69 0A 0D C3 A7 61 0A 0D 09 6C C3 A0 2D 62 61 73 22 =
7D)<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p></o:p><=
/p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Jun =
11, 2013 at 2:12 PM, Jim Schaad &lt;<a =
href=3D"mailto:ietf@augustcellars.com" =
target=3D"_blank">ietf@augustcellars.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&lt;not =
chair&gt;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Richard,<o:p=
></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I do not =
currently believe that this is a doable item.&nbsp; In order for me to =
believe otherwise you will need to give a concrete proposal about how to =
solve the problem of things drifting back and forth.&nbsp; Given the =
text<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>{xxx}\r\r\rT=
his is the body<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>How does =
one know where the dividing line between the JSON header and the body =
begins?&nbsp; Until this is completely solved what you propose is not =
doable and the current method of base64 encoding will be =
required.<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>Jim</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#888888'>&nbsp;</span><o:p></o:p></p></div></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0815_01CE66AC.52150380--


From rlb@ipv.sx  Tue Jun 11 14:44:05 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5485F21F8F15 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.48
X-Spam-Level: 
X-Spam-Status: No, score=0.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3uTtyGr850Cs for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:44:00 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 00D3521F99ED for <jose@ietf.org>; Tue, 11 Jun 2013 14:43:59 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so12400965obb.5 for <jose@ietf.org>; Tue, 11 Jun 2013 14:43:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=V8t1NyVolQ+JHhdwxnMNzdXf13hKKhsEriTf0Jck3bY=; b=MWwx5QFEORUusVcTWcA2KDXiuUrjHhTafeNl2g7AfjXQ4eF8CkrKJaaDrdEmoeys/F F/b8vCJE5BMhjFh4Z0FKOa+gO8shdKl6LgIvCA1ZBuYLeJ9/ZmVhyVnD2eCGqCi5N1zT Be6lPoraHUOWYcIX8mw7tl4ZDnkJB5McZC5ncw+MuZWws8YUqJPEAiEGkJnqFOtELm8W Q+bIYDkyXG+NkE9MLlCI3sE4Z4bmYfQaJInAlewsbfqG0rKEFZPdEQuqKXFNIKTxHcOw ykWhL+dUINRgVCs0a7T0BUdm2CbyPBZ6LX4bmkjtgFHeyCcbup7RMDpLB+GSheTk7Tpx rBCQ==
MIME-Version: 1.0
X-Received: by 10.182.74.131 with SMTP id t3mr13425417obv.87.1370987039260; Tue, 11 Jun 2013 14:43:59 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 14:43:59 -0700 (PDT)
X-Originating-IP: [174.236.199.75]
In-Reply-To: <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com> <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>
Date: Tue, 11 Jun 2013 17:43:59 -0400
Message-ID: <CAL02cgQ6hfi2_5LvXXTXoKc7jOkQRmWUQdpn-xmh0pqis04bxg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a11c1be0677ebe404dee7cb15
X-Gm-Message-State: ALoCoQmfy4Zbd3OiE296Dm7tObbbYH8QaUiIyQcnv+585lTRimKoW8PGxrcNPcp9qZaJuicJ14e7
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 21:44:05 -0000

--001a11c1be0677ebe404dee7cb15
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ah. I see.  Guess that's what the '.' character is for in the base64
version.  :)

In this version, you could just require that the JWS protected header have
no trailing white space.  Then, if you the attacker trims any characters,
it won't be valid.

Senders MUST NOT create a header with trailing white space. Recipient
MUST (1) check that the header is valid JSON, and (2) check that there is
no trailing white space in the header string.

I think this is a flavor of your (2).



On Tuesday, June 11, 2013, Jim Schaad wrote:

> Yes =96 you are still not understanding the problem.****
>
> ** **
>
> There is an interesting issue that comes up in computing hash values of
> multiple things which are concatenated together.  This issue is that it i=
s
> possible to move items from one thing to an adjacent thing and still get
> the same hash value.****
>
> ** **
>
> Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as=
 the value being
> hashed.****
>
> If field1=3D=94aa=94 and field2=3D=94abbb=94 you still get the same =93aa=
abbb=94 as the
> value being hashed but different ideas of what the two fields are.****
>
> ** **
>
> There are three classic ways to deal with this problem:****
>
> ** **
>
> **1.       **Use  length prefix on each field =96 this is the ASN.1 encod=
e
> it version****
>
> **2.       **Use fields that are well defined in terms of delimiters****
>
> **3.       **Put in separation characters which are not allowed in either
> field.****
>
> ** **
>
> I once tried to argue that this is what we should do and ended up with th=
e
> following:  Method one was not considered acceptable, method two was not
> possible given the current state of JSON parsers, method three is what we
> currently do.****
>
> ** **
>
> JSON parsers allow for indefinite amounts of whitespace following a JSON
> object so that will always be a problem.  Additionally there are JSON
> parsers which believe they can stop parsing and not produce an error once
> it has fully built a top level object.  Thus they consider the string
> =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pars=
ed.****
>
> ** **
>
> This allows for an attacker to move items from the content to the
> protected string unless there is an externally imposed rule about what
> happens for trailing characters after the protected content.****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <javascript:_e({}, 'cvml',
> 'rlb@ipv.sx');>]
> *Sent:* Tuesday, June 11, 2013 12:51 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org <javascript:_e({}, 'cvml', 'jose@ietf.org');>
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
> ** **
>
> Still not understanding the problem.  Things are still clearly separated
> in JWS:****
>
> ** **
>
> {****
>
>     "protected_header": "eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9"****
>
>     "payload": "AQIDBA"****
>
> }****
>
> ** **
>
> Here the protected_header is base64('{"alg":"RS256","kid":"jim"}') and th=
e
> payload is base64(0x01020304).****
>
> ** **
>
> OLD: ****
>
> Signature is
> over: eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJSUzI1NiIsImtpZCI6Im=
ppbSJ9
> ****
>
> =3D=3D 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d =
74 70
> 5a 43 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 5=
3
> 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39**=
*
> *
>
> ** **
>
> NEW:****
>
> Signature is over: {"alg":"RS256","kid":"jim"}****
>
> =3D=3D 01 02 03 04 7b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 =
64 22
> 3a 22 6a 69 6d 22 7d 01 02 03 04****
>
> ** **
>
> That is, just decode the two octet strings, convert the protected_header
> to UTF-8, and concatenate them.  (This extends the proposal to also get r=
id
> of the "." in the middle, since it's not necessary.  I updated the issue.=
)
> ****
>
> ** **
>
> No ambiguity.****
>
> ** **
>
> --Richard****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Tue, Jun 11, 2013 at 3:16 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> Yes, it is not a problem for JWE, however consider the case of JWS where
> there is no distinction between how the protected data and the content ar=
e
> processed.****
>
>  ****
>
> Jim****
>
>  ****
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Tuesday, June 11, 2013 11:43 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
>  ****
>
> I don't know what you mean by "the problem of things drifting back and
> forth".  Let me try to be more concrete.****
>
>  ****
>
> Consider the following JWE:****
>
>  ****
>
> {****
>
>     "header": { "alg": "dir" }****
>
>
>

--001a11c1be0677ebe404dee7cb15
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ah. I see. =A0Guess that&#39;s what the &#39;.&#39; character is for in the=
 base64 version. =A0:)<div><br></div><div>In this version, you could just r=
equire that the JWS protected header have no trailing white space. =A0Then,=
 if you the attacker trims=A0any characters, it won&#39;t be valid. =A0</di=
v>
<div><br></div><div>Senders MUST NOT create a header with trailing white sp=
ace. Recipient MUST=A0(1) check=A0that the header is valid JSON, and (2) ch=
eck that there is no trailing white space in the header string.=A0</div><di=
v>
<br></div><div>I think this is a flavor of your (2).=A0</div><div><br></div=
><div><br><br>On Tuesday, June 11, 2013, Jim Schaad  wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">Yes =96 you are still not understanding the =
problem.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is an interestin=
g issue that comes up in computing hash values of multiple things which are=
 concatenated together.=A0 This issue is that it is possible to move items =
from one thing to an adjacent thing and still get the same hash value.<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thus if field1=3D=94aa=
a=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as the value being hashed.=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If field1=3D=94aa=94 and =
field2=3D=94abbb=94 you still get the same =93aaabbb=94 as the value being =
hashed but different ideas of what the two fields are.<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There are three classi=
c ways to deal with this problem:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1f497d"><span>1.<span style=3D"font:7.0pt &=
quot;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u>=
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">Use =A0length prefix on each field =96 this is t=
he ASN.1 encode it version<u></u><u></u></span></p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>2.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Use fields that are well defined in terms of delimi=
ters<u></u><u></u></span></p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>3.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Put in separation characters which are not allowed =
in either field.<u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d">I once tried to argue that this is what we=
 should do and ended up with the following:=A0 Method one was not considere=
d acceptable, method two was not possible given the current state of JSON p=
arsers, method three is what we currently do.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">JSON parsers allow for=
 indefinite amounts of whitespace following a JSON object so that will alwa=
ys be a problem.=A0 Additionally there are JSON parsers which believe they =
can stop parsing and not produce an error once it has fully built a top lev=
el object.=A0 Thus they consider the string =91{=93a=94:=93b=94}FRED=94 to =
be something that can be successfully parsed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">This allows for an att=
acker to move items from the content to the protected string unless there i=
s an externally imposed rule about what happens for trailing characters aft=
er the protected content.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Richard Barnes [mailto:<a href=3D"javascript:_e({}, &#39;cvml&=
#39;, &#39;rlb@ipv.sx&#39;);" target=3D"_blank">rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 12:51 PM<br><b>To:</b> Jim Schaad<br><b=
>Cc:</b> <a href=3D"javascript:_e({}, &#39;cvml&#39;, &#39;jose@ietf.org&#3=
9;);" target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 =
- Make crypto indepenent of binary encoding<u></u><u></u></span></p>
</div></div><p><u></u>=A0<u></u></p><div><p>Still not understanding the pro=
blem. =A0Things are still clearly separated in JWS:<u></u><u></u></p><div><=
p><u></u>=A0<u></u></p></div><div><p>{<u></u><u></u></p></div><div><p>=A0 =
=A0 &quot;protected_header&quot;: &quot;eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ=
9&quot;<u></u><u></u></p>
</div><div><p>=A0 =A0 &quot;payload&quot;: &quot;AQIDBA&quot;<u></u><u></u>=
</p></div><div><p>}<u></u><u></u></p></div><div><p><u></u>=A0<u></u></p></d=
iv><div><p>Here the protected_header is base64(&#39;{&quot;alg&quot;:&quot;=
RS256&quot;,&quot;kid&quot;:&quot;jim&quot;}&#39;) and the payload is base6=
4(0x01020304).<u></u><u></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>OLD:=A0<u></u><u></u></p><=
/div><div><p>Signature is over:=A0eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJh=
bGciOiJSUzI1NiIsImtpZCI6ImppbSJ9<u></u><u></u></p></div><div><p>=3D=3D=A065=
 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43=
 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a=
 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39<u></u><u=
></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>NEW:<u></u><u></u></p></di=
v><div><p>Signature is over: {&quot;alg&quot;:&quot;RS256&quot;,&quot;kid&q=
uot;:&quot;jim&quot;}<u></u><u></u></p></div><div><p>=3D=3D=A001 02 03 04 7=
b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 64 22 3a 22 6a 69 6d 2=
2 7d 01 02 03 04<u></u><u></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>That is, just decode the t=
wo octet strings, convert the protected_header to UTF-8, and concatenate th=
em. =A0(This extends the proposal to also get rid of the &quot;.&quot; in t=
he middle, since it&#39;s not necessary. =A0I updated the issue.)<u></u><u>=
</u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>No ambiguity.<u></u><u></u=
></p></div><div><p><u></u>=A0<u></u></p></div><div><p>--Richard<u></u><u></=
u></p></div><div><p><u></u>=A0<u></u></p></div><div><p><u></u>=A0<u></u></p=
></div>
<div><p><u></u>=A0<u></u></p></div><div><p><u></u>=A0<u></u></p></div></div=
><div><p style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p><div><p>On Tue=
, Jun 11, 2013 at 3:16 PM, Jim Schaad &lt;<a>ietf@augustcellars.com</a>&gt;=
 wrote:<u></u><u></u></p>
<div><div><p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1f497d">Yes, it is not a problem for JWE, h=
owever consider the case of JWS where there is no distinction between how t=
he protected data and the content are processed.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">Jim</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">=A0</span><u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p><b><span style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard=
 Barnes [mailto:<a>rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 11:43 AM<br><b>To:</b> Jim Schaad<br><b=
>Cc:</b> <a>jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 - Make crypt=
o indepenent of binary encoding</span><u></u><u></u></p></div></div><div>
<div><p>=A0<u></u><u></u></p><div><p>I don&#39;t know what you mean by &quo=
t;the problem of things drifting back and forth&quot;. =A0Let me try to be =
more concrete.<u></u><u></u></p><div><p>=A0<u></u><u></u></p></div><div><p>=
Consider the following JWE:<u></u><u></u></p>
</div><div><p>=A0<u></u><u></u></p></div><div><p>{<u></u><u></u></p></div><=
div><p>=A0 =A0 &quot;header&quot;: { &quot;alg&quot;: &quot;dir&quot; }<u><=
/u><u></u></p></div><div><p>=A0 =A0 </p></div></div></div></div></div></div=
></div>
</div></div></div></div></div></blockquote></div>

--001a11c1be0677ebe404dee7cb15--

From rlb@ipv.sx  Tue Jun 11 14:53:49 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F07321F9A3C for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.48
X-Spam-Level: 
X-Spam-Status: No, score=0.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6d4geIcMTey for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 14:53:44 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5392E21F9A2A for <jose@ietf.org>; Tue, 11 Jun 2013 14:53:44 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so12420553obb.19 for <jose@ietf.org>; Tue, 11 Jun 2013 14:53:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Xy0xA7zowL1QalfNxA/owsLwGzZXtbZHZ3KeD+2/SjY=; b=CwyxsQfXpl7pDgk+1Rg37vvb/zuCwFpgkNEoSrxETR/ipfqDuMzJhci1r6Ld8O7km4 YBRrLNAgAGlGEDIlA6m65kji0/7HuMShY0xsWd7IQnBVREwY8oNq63UfD725HjH01XuC 64dkFJlbviFDk2Kui9f9QSPmuAd+5Nx57LmXpHrD9ZMQbJL73Ind6+Q3K4K3+OvbQm2l 6+jSQStRVtiwVKHrHt43uj0/7tzYRGfjMXh8JFVZm7Erj6f3so1kN/2ka3P/4oGueZJd yw8VV2Qq6t2cxB61GO0PYdt+yhvuutqDOkdtmTT0D8q+BTvS8awVcmfKJhqk4QPTbDeX uWBw==
MIME-Version: 1.0
X-Received: by 10.60.52.15 with SMTP id p15mr13198337oeo.87.1370987623771; Tue, 11 Jun 2013 14:53:43 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 14:53:43 -0700 (PDT)
X-Originating-IP: [174.236.2.230]
In-Reply-To: <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com> <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>
Date: Tue, 11 Jun 2013 17:53:43 -0400
Message-ID: <CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a113309ce4ecf5a04dee7ee1a
X-Gm-Message-State: ALoCoQnH7A3PippM3ueSOVzkqWdroTYuX3aZGDZX4Y0uFon7VIu05XCyLylCSjyOZd0quHNnUB5V
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 21:53:49 -0000

--001a113309ce4ecf5a04dee7ee1a
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ah. I see.  Guess that's what the '.' character is for in the base64
version.  :)

In this version, you could just require that the JWS protected header have
no trailing white space.  Then, if you the attacker trims any characters,
it won't be valid.

Senders MUST NOT create a header with trailing white space. Recipient
MUST (1) check that the header is valid JSON, and (2) check that there is
no trailing white space in the header string.

I think this is a flavor of your (2).



On Tuesday, June 11, 2013, Jim Schaad wrote:

> Yes =96 you are still not understanding the problem.****
>
> ** **
>
> There is an interesting issue that comes up in computing hash values of
> multiple things which are concatenated together.  This issue is that it i=
s
> possible to move items from one thing to an adjacent thing and still get
> the same hash value.****
>
> ** **
>
> Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as=
 the value being
> hashed.****
>
> If field1=3D=94aa=94 and field2=3D=94abbb=94 you still get the same =93aa=
abbb=94 as the
> value being hashed but different ideas of what the two fields are.****
>
> ** **
>
> There are three classic ways to deal with this problem:****
>
> ** **
>
> **1.       **Use  length prefix on each field =96 this is the ASN.1 encod=
e
> it version****
>
> **2.       **Use fields that are well defined in terms of delimiters****
>
> **3.       **Put in separation characters which are not allowed in either
> field.****
>
> ** **
>
> I once tried to argue that this is what we should do and ended up with th=
e
> following:  Method one was not considered acceptable, method two was not
> possible given the current state of JSON parsers, method three is what we
> currently do.****
>
> ** **
>
> JSON parsers allow for indefinite amounts of whitespace following a JSON
> object so that will always be a problem.  Additionally there are JSON
> parsers which believe they can stop parsing and not produce an error once
> it has fully built a top level object.  Thus they consider the string
> =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pars=
ed.****
>
> ** **
>
> This allows for an attacker to move items from the content to the
> protected string unless there is an externally imposed rule about what
> happens for trailing characters after the protected content.****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <javascript:_e({}, 'cvml',
> 'rlb@ipv.sx');>]
> *Sent:* Tuesday, June 11, 2013 12:51 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org <javascript:_e({}, 'cvml', 'jose@ietf.org');>
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
> ** **
>
> Still not understanding the problem.  Things are still clearly separated
> in JWS:****
>
> ** **
>
> {****
>
>     "protected_header": "eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9"****
>
>     "payload": "AQIDBA"****
>
> }****
>
> ** **
>
> Here the protected_header is base64('{"alg":"RS256","kid":"jim"}') and th=
e
> payload is base64(0x01020304).****
>
> ** **
>
> OLD: ****
>
> Signature is
> over: eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJhbGciOiJSUzI1NiIsImtpZCI6Im=
ppbSJ9
> ****
>
> =3D=3D 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d =
74 70
> 5a 43 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 5=
3
> 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39**=
*
> *
>
> ** **
>
> NEW:****
>
> Signature is over: {"alg":"RS256","kid":"jim"}****
>
> =3D=3D 01 02 03 04 7b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 =
64 22
> 3a 22 6a 69 6d 22 7d 01 02 03 04****
>
> ** **
>
> That is, just decode the two octet strings, convert the protected_header
> to UTF-8, and concatenate them.  (This extends the proposal to also get r=
id
> of the "." in the middle, since it's not necessary.  I updated the issue.=
)
> ****
>
> ** **
>
> No ambiguity.****
>
> ** **
>
> --Richard****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Tue, Jun 11, 2013 at 3:16 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> Yes, it is not a problem for JWE, however consider the case of JWS where
> there is no distinction between how the protected data and the content ar=
e
> processed.****
>
>  ****
>
> Jim****
>
>  ****
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Tuesday, June 11, 2013 11:43 AM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
>  ****
>
> I don't know what you mean by "the problem of things drifting back and
> forth".  Let me try to be more concrete.****
>
>  ****
>
> Consider the following JWE:****
>
>  ****
>
> {****
>
>     "header": { "alg": "dir" }****
>
>
>

--001a113309ce4ecf5a04dee7ee1a
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Ah. I see. =A0Guess that&#39;s what the &#39;.&#39; character is for in the=
 base64 version. =A0:)<div><br></div><div>In this version, you could just r=
equire that the JWS protected header have no trailing white space. =A0Then,=
 if you the attacker trims=A0any characters, it won&#39;t be valid. =A0</di=
v>
<div><br></div><div>Senders MUST NOT create a header with trailing white sp=
ace. Recipient MUST=A0(1) check=A0that the header is valid JSON, and (2) ch=
eck that there is no trailing white space in the header string.=A0</div><di=
v>
<br></div><div>I think this is a flavor of your (2).=A0</div><div><br></div=
><div><br><br>On Tuesday, June 11, 2013, Jim Schaad  wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">Yes =96 you are still not understanding the =
problem.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is an interestin=
g issue that comes up in computing hash values of multiple things which are=
 concatenated together.=A0 This issue is that it is possible to move items =
from one thing to an adjacent thing and still get the same hash value.<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thus if field1=3D=94aa=
a=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as the value being hashed.=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If field1=3D=94aa=94 and =
field2=3D=94abbb=94 you still get the same =93aaabbb=94 as the value being =
hashed but different ideas of what the two fields are.<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There are three classi=
c ways to deal with this problem:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1f497d"><span>1.<span style=3D"font:7.0pt &=
quot;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u>=
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">Use =A0length prefix on each field =96 this is t=
he ASN.1 encode it version<u></u><u></u></span></p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>2.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Use fields that are well defined in terms of delimi=
ters<u></u><u></u></span></p>
<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>3.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Put in separation characters which are not allowed =
in either field.<u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d">I once tried to argue that this is what we=
 should do and ended up with the following:=A0 Method one was not considere=
d acceptable, method two was not possible given the current state of JSON p=
arsers, method three is what we currently do.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">JSON parsers allow for=
 indefinite amounts of whitespace following a JSON object so that will alwa=
ys be a problem.=A0 Additionally there are JSON parsers which believe they =
can stop parsing and not produce an error once it has fully built a top lev=
el object.=A0 Thus they consider the string =91{=93a=94:=93b=94}FRED=94 to =
be something that can be successfully parsed.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">This allows for an att=
acker to move items from the content to the protected string unless there i=
s an externally imposed rule about what happens for trailing characters aft=
er the protected content.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Richard Barnes [mailto:<a href=3D"javascript:_e({}, &#39;cvml&=
#39;, &#39;rlb@ipv.sx&#39;);" target=3D"_blank">rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 12:51 PM<br><b>To:</b> Jim Schaad<br><b=
>Cc:</b> <a href=3D"javascript:_e({}, &#39;cvml&#39;, &#39;jose@ietf.org&#3=
9;);" target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 =
- Make crypto indepenent of binary encoding<u></u><u></u></span></p>
</div></div><p><u></u>=A0<u></u></p><div><p>Still not understanding the pro=
blem. =A0Things are still clearly separated in JWS:<u></u><u></u></p><div><=
p><u></u>=A0<u></u></p></div><div><p>{<u></u><u></u></p></div><div><p>=A0 =
=A0 &quot;protected_header&quot;: &quot;eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ=
9&quot;<u></u><u></u></p>
</div><div><p>=A0 =A0 &quot;payload&quot;: &quot;AQIDBA&quot;<u></u><u></u>=
</p></div><div><p>}<u></u><u></u></p></div><div><p><u></u>=A0<u></u></p></d=
iv><div><p>Here the protected_header is base64(&#39;{&quot;alg&quot;:&quot;=
RS256&quot;,&quot;kid&quot;:&quot;jim&quot;}&#39;) and the payload is base6=
4(0x01020304).<u></u><u></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>OLD:=A0<u></u><u></u></p><=
/div><div><p>Signature is over:=A0eyJhbGciOiJSUzI1NiIsImtpZCI6ImppbSJ9.eyJh=
bGciOiJSUzI1NiIsImtpZCI6ImppbSJ9<u></u><u></u></p></div><div><p>=3D=3D=A065=
 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a 49 31 4e 69 49 73 49 6d 74 70 5a 43=
 49 36 49 6d 70 70 62 53 4a 39 2e 65 79 4a 68 62 47 63 69 4f 69 4a 53 55 7a=
 49 31 4e 69 49 73 49 6d 74 70 5a 43 49 36 49 6d 70 70 62 53 4a 39<u></u><u=
></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>NEW:<u></u><u></u></p></di=
v><div><p>Signature is over: {&quot;alg&quot;:&quot;RS256&quot;,&quot;kid&q=
uot;:&quot;jim&quot;}<u></u><u></u></p></div><div><p>=3D=3D=A001 02 03 04 7=
b 22 61 6c 67 22 3a 22 52 53 32 35 36 22 2c 22 6b 69 64 22 3a 22 6a 69 6d 2=
2 7d 01 02 03 04<u></u><u></u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>That is, just decode the t=
wo octet strings, convert the protected_header to UTF-8, and concatenate th=
em. =A0(This extends the proposal to also get rid of the &quot;.&quot; in t=
he middle, since it&#39;s not necessary. =A0I updated the issue.)<u></u><u>=
</u></p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>No ambiguity.<u></u><u></u=
></p></div><div><p><u></u>=A0<u></u></p></div><div><p>--Richard<u></u><u></=
u></p></div><div><p><u></u>=A0<u></u></p></div><div><p><u></u>=A0<u></u></p=
></div>
<div><p><u></u>=A0<u></u></p></div><div><p><u></u>=A0<u></u></p></div></div=
><div><p style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p><div><p>On Tue=
, Jun 11, 2013 at 3:16 PM, Jim Schaad &lt;<a>ietf@augustcellars.com</a>&gt;=
 wrote:<u></u><u></u></p>
<div><div><p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1f497d">Yes, it is not a problem for JWE, h=
owever consider the case of JWS where there is no distinction between how t=
he protected data and the content are processed.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">Jim</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">=A0</span><u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p><b><span style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard=
 Barnes [mailto:<a>rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 11:43 AM<br><b>To:</b> Jim Schaad<br><b=
>Cc:</b> <a>jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 - Make crypt=
o indepenent of binary encoding</span><u></u><u></u></p></div></div><div>
<div><p>=A0<u></u><u></u></p><div><p>I don&#39;t know what you mean by &quo=
t;the problem of things drifting back and forth&quot;. =A0Let me try to be =
more concrete.<u></u><u></u></p><div><p>=A0<u></u><u></u></p></div><div><p>=
Consider the following JWE:<u></u><u></u></p>
</div><div><p>=A0<u></u><u></u></p></div><div><p>{<u></u><u></u></p></div><=
div><p>=A0 =A0 &quot;header&quot;: { &quot;alg&quot;: &quot;dir&quot; }<u><=
/u><u></u></p></div><div><p>=A0 =A0 </p></div></div></div></div></div></div=
></div>
</div></div></div></div></div></blockquote></div>

--001a113309ce4ecf5a04dee7ee1a--

From rlb@ipv.sx  Tue Jun 11 15:41:05 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2479721F9A83 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 15:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.48
X-Spam-Level: 
X-Spam-Status: No, score=0.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Px3Ji+BCJB+w for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 15:40:54 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 28E5D21F9A61 for <jose@ietf.org>; Tue, 11 Jun 2013 15:40:53 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id va7so12388308obc.27 for <jose@ietf.org>; Tue, 11 Jun 2013 15:40:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=iUfQxNpP22V6H0vuA9tXvowCjHbPpU0sp+972UXK4Pw=; b=OyoL4+DOV8M1mHzNJRah04I7FJKjnFzVDcwBqJisRW+rU1qMoa/J/yUCH5kUffUoYQ p3dweAaDv3DmlLJkxtbSbuU1rcxxqraNkPiSM4DWy0K4dPrea/yJY8xvNcmiBveGfdnB h5tsZHC+Bn/449Y0ThOyeBbJBKWYKzPdVcj5HC9XPrSdq2298DJG4L/tDm5XJgCoL4vf 1G7eI5ugzFIyBkELc6s83J8NGsrBIMzrrLfBnqAH4oBvD7Kr33+TaH+9Cw8JNiiT6v3n ERjSBt0eJrUcXsxNavUcGB80DQR70dClrXuNfnYLIr9g6b3FhPaxXi7MlhTw7iT5hIQh sEyA==
MIME-Version: 1.0
X-Received: by 10.60.43.232 with SMTP id z8mr13217176oel.138.1370990452695; Tue, 11 Jun 2013 15:40:52 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 15:40:52 -0700 (PDT)
X-Originating-IP: [174.226.3.59]
In-Reply-To: <CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com> <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com> <CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com>
Date: Tue, 11 Jun 2013 18:40:52 -0400
Message-ID: <CAL02cgQD8rWkKw04E3Nt_HP==4f6RHZaf3PPm=wsXbQfRbO+eg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a113311fcecc45804dee89661
X-Gm-Message-State: ALoCoQmO7Gdhq1CWoRmRKThMVe+s6ESI/TFYobNuckeQvoRvAkXRI18WXXYqoMyO30/yfWw+FKX+
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 22:41:05 -0000

--001a113311fcecc45804dee89661
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Note: This is exactly how CMS mitigates this attack.  The SignedAttrs DER
structure is appended after the content, so DER parsing will fail if any
octets are added or removed.


On Tuesday, June 11, 2013, Richard Barnes wrote:

> Ah. I see.  Guess that's what the '.' character is for in the base64
> version.  :)
>
> In this version, you could just require that the JWS protected header hav=
e
> no trailing white space.  Then, if you the attacker trims any characters,
> it won't be valid.
>
> Senders MUST NOT create a header with trailing white space. Recipient
> MUST (1) check that the header is valid JSON, and (2) check that there is
> no trailing white space in the header string.
>
> I think this is a flavor of your (2).
>
>
>
> On Tuesday, June 11, 2013, Jim Schaad wrote:
>
> Yes =96 you are still not understanding the problem.****
>
> ** **
>
> There is an interesting issue that comes up in computing hash values of
> multiple things which are concatenated together.  This issue is that it i=
s
> possible to move items from one thing to an adjacent thing and still get
> the same hash value.****
>
> ** **
>
> Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as=
 the value being
> hashed.****
>
> If field1=3D=94aa=94 and field2=3D=94abbb=94 you still get the same =93aa=
abbb=94 as the
> value being hashed but different ideas of what the two fields are.****
>
> ** **
>
> There are three classic ways to deal with this problem:****
>
> ** **
>
> **1.       **Use  length prefix on each field =96 this is the ASN.1 encod=
e
> it version****
>
> **2.       **Use fields that are well defined in terms of delimiters****
>
> **3.       **Put in separation characters which are not allowed in either
> field.****
>
> ** **
>
> I once tried to argue that this is what we should do and ended up with th=
e
> following:  Method one was not considered acceptable, method two was not
> possible given the current state of JSON parsers, method three is what we
> currently do.****
>
> ** **
>
> JSON parsers allow for indefinite amounts of whitespace following a JSON
> object so that will always be a problem.  Additionally there are JSON
> parsers which believe they can stop parsing and not produce an error once
> it has fully built a top level object.  Thus they consider the string
> =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pars=
ed.****
>
> ** **
>
> This allows for an attacker to move items from the content to the
> protected string unless there is an externally imposed rule about what
> happens for trailing characters after the protected content.****
>
> ** **
>
>

--001a113311fcecc45804dee89661
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Note: This is exactly how CMS mitigates this attack. =A0The SignedAttrs DER=
 structure is appended after the content, so DER=A0<span></span>parsing wil=
l fail if any octets are added or removed.=A0<br><br><br>On Tuesday, June 1=
1, 2013, Richard Barnes  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Ah. I see. =A0Guess that&#39;s what the &#39=
;.&#39; character is for in the base64 version. =A0:)<div><br></div><div>In=
 this version, you could just require that the JWS protected header have no=
 trailing white space. =A0Then, if you the attacker trims=A0any characters,=
 it won&#39;t be valid. =A0</div>

<div><br></div><div>Senders MUST NOT create a header with trailing white sp=
ace. Recipient MUST=A0(1) check=A0that the header is valid JSON, and (2) ch=
eck that there is no trailing white space in the header string.=A0</div><di=
v>

<br></div><div>I think this is a flavor of your (2).=A0</div><div><br></div=
><div><br><br>On Tuesday, June 11, 2013, Jim Schaad  wrote:<br><blockquote =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p><span style=3D"f=
ont-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;colo=
r:#1f497d">Yes =96 you are still not understanding the problem.<u></u><u></=
u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">There is an interesting issue that comes up in computing hash =
values of multiple things which are concatenated together.=A0 This issue is=
 that it is possible to move items from one thing to an adjacent thing and =
still get the same hash value.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93a=
aabbb=94 as the value being hashed.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">If field1=3D=94aa=94 and field2=3D=94abbb=94 =
you still get the same =93aaabbb=94 as the value being hashed but different=
 ideas of what the two fields are.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">There are three classic ways to deal with this problem:<u></u>=
<u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><u></u><span s=
tyle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&q=
uot;;color:#1f497d"><span>1.<span style=3D"font:7.0pt &quot;Times New Roman=
&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1=
f497d">Use =A0length prefix on each field =96 this is the ASN.1 encode it v=
ersion<u></u><u></u></span></p>

<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>2.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Use fields that are well defined in terms of delimi=
ters<u></u><u></u></span></p>

<p><u></u><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><span>3.<span style=3D"font:7.0pt &quo=
t;Times New Roman&quot;">=A0=A0=A0=A0=A0=A0 </span></span></span><u></u><sp=
an style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1f497d">Put in separation characters which are not allowed =
in either field.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">I once tried to argue that this is what we should do and ended=
 up with the following:=A0 Method one was not considered acceptable, method=
 two was not possible given the current state of JSON parsers, method three=
 is what we currently do.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">JSON parsers allow for indefinite amounts of whitespace follow=
ing a JSON object so that will always be a problem.=A0 Additionally there a=
re JSON parsers which believe they can stop parsing and not produce an erro=
r once it has fully built a top level object.=A0 Thus they consider the str=
ing =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pa=
rsed.<u></u><u></u></span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">This allows for an attacker to move items from the content to =
the protected string unless there is an externally imposed rule about what =
happens for trailing characters after the protected content.<u></u><u></u><=
/span></p>

<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d"></span></p>
</div></div></blockquote></div>
</blockquote>

--001a113311fcecc45804dee89661--

From ietf@augustcellars.com  Tue Jun 11 16:03:05 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1D621F9A59 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 16:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiCvK8JJzkS9 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 16:02:59 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFE421F9A27 for <jose@ietf.org>; Tue, 11 Jun 2013 16:02:59 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 9FC992CA25; Tue, 11 Jun 2013 16:02:58 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com>	<CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com>	<080001ce66d8$20be6200$623b2600$@augustcellars.com>	<CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com>	<081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com>	<CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com> <CAL02cgQD8rWkKw04E3Nt_HP==4f6RHZaf3PPm=wsXbQfRbO+eg@mail.gmail.com>
In-Reply-To: <CAL02cgQD8rWkKw04E3Nt_HP==4f6RHZaf3PPm=wsXbQfRbO+eg@mail.gmail.com>
Date: Tue, 11 Jun 2013 16:02:05 -0700
Message-ID: <082e01ce66f7$b1d2a390$1577eab0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_082F_01CE66BD.05768AB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVND51os6fEx5T7BPLe3ecRAXbKQKjfidwAyLgE2MCjiSlRQJqBeVHAawzxUQCJrIu6Jeu+0fg
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 23:03:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_082F_01CE66BD.05768AB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

No - that is not true.

 

CMS mitigates this attack by doing an indirect signing on the content.  Thus
the hash of the content is part of the signed attributes.

 

Jim

 

 

From: Richard Barnes [mailto:rlb@ipv.sx] 
Sent: Tuesday, June 11, 2013 3:41 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: Issue #23 - Make crypto indepenent of binary encoding

 

Note: This is exactly how CMS mitigates this attack.  The SignedAttrs DER
structure is appended after the content, so DER parsing will fail if any
octets are added or removed. 


On Tuesday, June 11, 2013, Richard Barnes wrote:

Ah. I see.  Guess that's what the '.' character is for in the base64
version.  :)

 

In this version, you could just require that the JWS protected header have
no trailing white space.  Then, if you the attacker trims any characters, it
won't be valid.  

 

Senders MUST NOT create a header with trailing white space. Recipient MUST
(1) check that the header is valid JSON, and (2) check that there is no
trailing white space in the header string. 

 

I think this is a flavor of your (2). 

 



On Tuesday, June 11, 2013, Jim Schaad wrote:

Yes - you are still not understanding the problem.

 

There is an interesting issue that comes up in computing hash values of
multiple things which are concatenated together.  This issue is that it is
possible to move items from one thing to an adjacent thing and still get the
same hash value.

 

Thus if field1="aaa" and field2="bbb" you get "aaabbb" as the value being
hashed.

If field1="aa" and field2="abbb" you still get the same "aaabbb" as the
value being hashed but different ideas of what the two fields are.

 

There are three classic ways to deal with this problem:

 

1.       Use  length prefix on each field - this is the ASN.1 encode it
version

2.       Use fields that are well defined in terms of delimiters

3.       Put in separation characters which are not allowed in either field.

 

I once tried to argue that this is what we should do and ended up with the
following:  Method one was not considered acceptable, method two was not
possible given the current state of JSON parsers, method three is what we
currently do.

 

JSON parsers allow for indefinite amounts of whitespace following a JSON
object so that will always be a problem.  Additionally there are JSON
parsers which believe they can stop parsing and not produce an error once it
has fully built a top level object.  Thus they consider the string
'{"a":"b"}FRED" to be something that can be successfully parsed.

 

This allows for an attacker to move items from the content to the protected
string unless there is an externally imposed rule about what happens for
trailing characters after the protected content.

 


------=_NextPart_000_082F_01CE66BD.05768AB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>No &#8211; that is not true.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>CMS mitigates this attack by doing an indirect signing on the =
content.&nbsp; Thus the hash of the content is part of the signed =
attributes.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Tuesday, June 11, =
2013 3:41 PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: Issue #23 - Make crypto indepenent =
of binary encoding<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Note: This =
is exactly how CMS mitigates this attack. &nbsp;The SignedAttrs DER =
structure is appended after the content, so DER&nbsp;parsing will fail =
if any octets are added or removed.&nbsp;<br><br><br>On Tuesday, June =
11, 2013, Richard Barnes wrote:<o:p></o:p></p><p class=3DMsoNormal>Ah. I =
see. &nbsp;Guess that's what the '.' character is for in the base64 =
version. &nbsp;:)<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In this version, you could just require that the JWS =
protected header have no trailing white space. &nbsp;Then, if you the =
attacker trims&nbsp;any characters, it won't be valid. =
&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Senders MUST NOT create a header with trailing white =
space. Recipient MUST&nbsp;(1) check&nbsp;that the header is valid JSON, =
and (2) check that there is no trailing white space in the header =
string.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
think this is a flavor of your (2).&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><br><br>On Tuesday, June 11, 2013, Jim Schaad =
wrote:<o:p></o:p></p><div><div><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Yes &#8211; you are still not understanding the =
problem.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There is an interesting issue that comes up in computing hash values =
of multiple things which are concatenated together.&nbsp; This issue is =
that it is possible to move items from one thing to an adjacent thing =
and still get the same hash value.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thus if field1=3D&#8221;aaa&#8221; and field2=3D&#8221;bbb&#8221; you =
get &#8220;aaabbb&#8221; as the value being =
hashed.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If field1=3D&#8221;aa&#8221; and field2=3D&#8221;abbb&#8221; you =
still get the same &#8220;aaabbb&#8221; as the value being hashed but =
different ideas of what the two fields =
are.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There are three classic ways to deal with this =
problem:</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>1.</span><span =
style=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Use &nbsp;length prefix on each field &#8211; this is the ASN.1 =
encode it version</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>2.</span><span =
style=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Use fields that are well defined in terms of =
delimiters</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>3.</span><span =
style=3D'font-size:7.0pt;color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Put in separation characters which are not allowed in either =
field.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I once tried to argue that this is what we should do and ended up =
with the following:&nbsp; Method one was not considered acceptable, =
method two was not possible given the current state of JSON parsers, =
method three is what we currently do.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>JSON parsers allow for indefinite amounts of whitespace following a =
JSON object so that will always be a problem.&nbsp; Additionally there =
are JSON parsers which believe they can stop parsing and not produce an =
error once it has fully built a top level object.&nbsp; Thus they =
consider the string &#8216;{&#8220;a&#8221;:&#8220;b&#8221;}FRED&#8221; =
to be something that can be successfully =
parsed.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This allows for an attacker to move items from the content to the =
protected string unless there is an externally imposed rule about what =
happens for trailing characters after the protected =
content.</span><o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div></div></div></div></div></body></htm=
l>
------=_NextPart_000_082F_01CE66BD.05768AB0--


From rlb@ipv.sx  Tue Jun 11 16:13:01 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B9F21F9B8B for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 16:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.48
X-Spam-Level: 
X-Spam-Status: No, score=0.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y+fAEXjt5DSx for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 16:12:56 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4CED421F9B88 for <jose@ietf.org>; Tue, 11 Jun 2013 16:12:56 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so3749636oag.40 for <jose@ietf.org>; Tue, 11 Jun 2013 16:12:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=HiFQfK2ZOD/HA6N96pEDG/a44kkNZaZUiGp07ZFokNc=; b=jdnWVxFUDxJCPrlOFmWyhcxtseBvD8h+Wd6NJrKK5xdzm9LfKxD52VxT76+5D/nNCi zCfPWyJH1zoTBFAfIcd97J3H0h/Qqo6+b7OxG31zB02pUTIdVdN7zzjVCx2Xwl0mJUPx tnCTo99BPqResT7WkOwBt2wzhQomH1RA9WEevJmI5wNgOmu8brCc18yypLgwXozc/BkV xYfdbyO+GBmbFK29rg1G/bE2dCMa2RfsymNq2d/pf7pax/+RsONgGw1Td4pp7YiktTTx JiYeXXk3ZjVAtjSLormyukdaZYQ09OlyNWsmrKtSa4p1wcujdpPP92FwUdqM9iTmT6vc sxLw==
MIME-Version: 1.0
X-Received: by 10.60.33.202 with SMTP id t10mr13474968oei.2.1370992373128; Tue, 11 Jun 2013 16:12:53 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Tue, 11 Jun 2013 16:12:53 -0700 (PDT)
X-Originating-IP: [174.254.176.120]
In-Reply-To: <082e01ce66f7$b1d2a390$1577eab0$@augustcellars.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com> <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com> <CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com> <CAL02cgQD8rWkKw04E3Nt_HP==4f6RHZaf3PPm=wsXbQfRbO+eg@mail.gmail.com> <082e01ce66f7$b1d2a390$1577eab0$@augustcellars.com>
Date: Tue, 11 Jun 2013 19:12:53 -0400
Message-ID: <CAL02cgRfYQshb6Dk+36y4p7cC9GV-rz5iDKQjeJkWsG=_965bg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e013c66b464442604dee90975
X-Gm-Message-State: ALoCoQmGQ7zOZK2Y7hWe6NTnNrQmoQwMEWdyzAphWYZ6zbrhZ2Iu2+Peh2EP312XhmaaU7/ABWH2
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 23:13:01 -0000

--089e013c66b464442604dee90975
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

True.  You could also do that here.

But I think my scheme still works, and is a little simpler.



On Tuesday, June 11, 2013, Jim Schaad wrote:

> No =96 that is not true.****
>
> ** **
>
> CMS mitigates this attack by doing an indirect signing on the content.
> Thus the hash of the content is part of the signed attributes.****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <javascript:_e({}, 'cvml',
> 'rlb@ipv.sx');>]
> *Sent:* Tuesday, June 11, 2013 3:41 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org <javascript:_e({}, 'cvml', 'jose@ietf.org');>
> *Subject:* Re: Issue #23 - Make crypto indepenent of binary encoding****
>
> ** **
>
> Note: This is exactly how CMS mitigates this attack.  The SignedAttrs DER
> structure is appended after the content, so DER parsing will fail if any
> octets are added or removed.
>
>
> On Tuesday, June 11, 2013, Richard Barnes wrote:****
>
> Ah. I see.  Guess that's what the '.' character is for in the base64
> version.  :)****
>
> ** **
>
> In this version, you could just require that the JWS protected header hav=
e
> no trailing white space.  Then, if you the attacker trims any characters,
> it won't be valid.  ****
>
> ** **
>
> Senders MUST NOT create a header with trailing white space. Recipient
> MUST (1) check that the header is valid JSON, and (2) check that there is
> no trailing white space in the header string. ****
>
> ** **
>
> I think this is a flavor of your (2). ****
>
> ** **
>
>
>
> On Tuesday, June 11, 2013, Jim Schaad wrote:****
>
> Yes =96 you are still not understanding the problem.****
>
>  ****
>
> There is an interesting issue that comes up in computing hash values of
> multiple things which are concatenated together.  This issue is that it i=
s
> possible to move items from one thing to an adjacent thing and still get
> the same hash value.****
>
>  ****
>
> Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93aaabbb=94 as=
 the value being
> hashed.****
>
> If field1=3D=94aa=94 and field2=3D=94abbb=94 you still get the same =93aa=
abbb=94 as the
> value being hashed but different ideas of what the two fields are.****
>
>  ****
>
> There are three classic ways to deal with this problem:****
>
>  ****
>
> 1.       Use  length prefix on each field =96 this is the ASN.1 encode it
> version****
>
> 2.       Use fields that are well defined in terms of delimiters****
>
> 3.       Put in separation characters which are not allowed in either
> field.****
>
>  ****
>
> I once tried to argue that this is what we should do and ended up with th=
e
> following:  Method one was not considered acceptable, method two was not
> possible given the current state of JSON parsers, method three is what we
> currently do.****
>
>  ****
>
> JSON parsers allow for indefinite amounts of whitespace following a JSON
> object so that will always be a problem.  Additionally there are JSON
> parsers which believe they can stop parsing and not produce an error once
> it has fully built a top level object.  Thus they consider the string
> =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pars=
ed.****
>
>  ****
>
>

--089e013c66b464442604dee90975
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

True. =A0You could also do that here.=A0<div><br></div><div>But I think my =
scheme still works, and is a little simpler.=A0</div><div><br></div><div><s=
pan></span><br><br>On Tuesday, June 11, 2013, Jim Schaad  wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">No =96 that is not true.<u></u><u></u></span=
></p><p class=3D"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></p><p class=3D"MsoNorma=
l"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">CMS mitigates this attack by doing an indirec=
t signing on the content.=A0 Thus the hash of the content is part of the si=
gned attributes.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b>=
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;"> Richard Barnes [mailto:<a href=3D"javascript:_e({}, &#39;cvml&=
#39;, &#39;rlb@ipv.sx&#39;);" target=3D"_blank">rlb@ipv.sx</a>] <br>
<b>Sent:</b> Tuesday, June 11, 2013 3:41 PM<br><b>To:</b> Jim Schaad<br><b>=
Cc:</b> <a href=3D"javascript:_e({}, &#39;cvml&#39;, &#39;jose@ietf.org&#39=
;);" target=3D"_blank">jose@ietf.org</a><br><b>Subject:</b> Re: Issue #23 -=
 Make crypto indepenent of binary encoding<u></u><u></u></span></p>
</div></div><p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNorm=
al">Note: This is exactly how CMS mitigates this attack. =A0The SignedAttrs=
 DER structure is appended after the content, so DER=A0parsing will fail if=
 any octets are added or removed.=A0<br>
<br><br>On Tuesday, June 11, 2013, Richard Barnes wrote:<u></u><u></u></p><=
p>Ah. I see. =A0Guess that&#39;s what the &#39;.&#39; character is for in t=
he base64 version. =A0:)<u></u><u></u></p><div><p><u></u>=A0<u></u></p></di=
v>
<div><p>In this version, you could just require that the JWS protected head=
er have no trailing white space. =A0Then, if you the attacker trims=A0any c=
haracters, it won&#39;t be valid. =A0<u></u><u></u></p></div><div><p><u></u=
>=A0<u></u></p>
</div><div><p>Senders MUST NOT create a header with trailing white space. R=
ecipient MUST=A0(1) check=A0that the header is valid JSON, and (2) check th=
at there is no trailing white space in the header string.=A0<u></u><u></u><=
/p>
</div><div><p><u></u>=A0<u></u></p></div><div><p>I think this is a flavor o=
f your (2).=A0<u></u><u></u></p></div><div><p><u></u>=A0<u></u></p></div><d=
iv><p><br><br>On Tuesday, June 11, 2013, Jim Schaad wrote:<u></u><u></u></p=
><div>
<div><p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1f497d">Yes =96 you are still not understanding =
the problem.</span><u></u><u></u></p><p><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</spa=
n><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">There is an interesting issue that comes up i=
n computing hash values of multiple things which are concatenated together.=
=A0 This issue is that it is possible to move items from one thing to an ad=
jacent thing and still get the same hash value.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">Thus if field1=3D=94aaa=94 and field2=3D=94bbb=94 you get =93a=
aabbb=94 as the value being hashed.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">If field1=3D=94aa=94 and field2=3D=94abbb=94 =
you still get the same =93aaabbb=94 as the value being hashed but different=
 ideas of what the two fields are.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">There are three classic ways to deal with this problem:</span>=
<u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">1.</span><span style=3D"font-size:7.0pt;color:#1f497d">=A0=A0=
=A0=A0=A0=A0 </span><span style=3D"font-size:11.0pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">Use =A0length prefix on each=
 field =96 this is the ASN.1 encode it version</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">2.</span><span style=3D"font-size:7.0pt;color=
:#1f497d">=A0=A0=A0=A0=A0=A0 </span><span style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Use fields t=
hat are well defined in terms of delimiters</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">3.</span><span style=3D"font-size:7.0pt;color=
:#1f497d">=A0=A0=A0=A0=A0=A0 </span><span style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Put in separ=
ation characters which are not allowed in either field.</span><u></u><u></u=
></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">I once tried to argue that this is what we should do and ended=
 up with the following:=A0 Method one was not considered acceptable, method=
 two was not possible given the current state of JSON parsers, method three=
 is what we currently do.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d">JSON parsers allow for indefinite amounts of whitespace follow=
ing a JSON object so that will always be a problem.=A0 Additionally there a=
re JSON parsers which believe they can stop parsing and not produce an erro=
r once it has fully built a top level object.=A0 Thus they consider the str=
ing =91{=93a=94:=93b=94}FRED=94 to be something that can be successfully pa=
rsed.</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1f497d">=A0</span><u></u><u></u></p><p><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1f497d"></span></p>
</div></div></div></div></div></div></blockquote></div>

--089e013c66b464442604dee90975--

From trac+jose@trac.tools.ietf.org  Tue Jun 11 17:02:03 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684C721F9AC9 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 17:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVUH6AhrytSm for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 17:01:57 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id ACA9D21F9AC6 for <jose@ietf.org>; Tue, 11 Jun 2013 17:01:53 -0700 (PDT)
Received: from localhost ([127.0.0.1]:36272 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UmYVR-0003yf-ES; Wed, 12 Jun 2013 02:01:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Wed, 12 Jun 2013 00:01:41 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2
Message-ID: <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 23
In-Reply-To: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130612000154.ACA9D21F9AC6@ietfa.amsl.com>
Resent-Date: Tue, 11 Jun 2013 17:01:53 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 00:02:03 -0000

#23: Make crypto independent of binary encoding (base64)


Comment (by michael.jones@microsoft.com):

 For both serializations, you already need the base64url encoded versions
 of the JWS Header and the JWS Payload to preserve them in transmission, so
 computing them isn't an extra burden.  In the JWS Compact Serialization,
 you already need the concatenation of the Encoded JWS Header, a period
 character, and the Encoded JWS Payload, so computing that concatenation
 isn't an extra burden.  Given you already have that quantity, computing
 the signature over it is the easiest thing for developers to do, and it's
 been shown to work well in practice.  There's no compelling reason to make
 this change.

 Even for the JSON Serialization, the only "extra" step that's required to
 compute the signature is the concatenation with the period character - to
 prevent shifting of data from one field to the other, as described by Jim
 Schaad in the e-mail thread.  So this step isn't actually "extra" at all -
 it's necessary.  It's also highly advantageous to use exactly the same
 computation for both serializations, which is currently the case.

 Since there is no compelling reason to make this change, and since making
 it could enable the "shifting" problem identified by Jim, it should not be
 made.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
jose <http://tools.ietf.org/jose/>


From James.H.Manger@team.telstra.com  Tue Jun 11 18:30:21 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E3A21F9B35 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 18:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.071
X-Spam-Level: 
X-Spam-Status: No, score=-0.071 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_43=0.6, J_CHICKENPOX_53=0.6, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtP+2VlpjCkx for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 18:30:15 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id 8A97221F9B33 for <jose@ietf.org>; Tue, 11 Jun 2013 18:30:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,848,1363093200"; d="scan'208";a="133560290"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipobni.tcif.telstra.com.au with ESMTP; 12 Jun 2013 11:30:12 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7103"; a="143779942"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipccni.tcif.telstra.com.au with ESMTP; 12 Jun 2013 11:30:12 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Wed, 12 Jun 2013 11:30:11 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "jose@ietf.org" <jose@ietf.org>
Date: Wed, 12 Jun 2013 11:30:10 +1000
Thread-Topic: [jose] Issue #23 - Make crypto indepenent of binary encoding
Thread-Index: Ac5m+TwlOriKcbAJQj2Ye1zdwWN1RQABg5QA
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B54D699@WSMSG3153V.srv.dir.telstra.com>
References: <07c801ce66cf$2c7a0260$856e0720$@augustcellars.com> <CAL02cgSDwuEtwhe0N-E-5oNTFY=Et6iwOOfWZfF_e-F54j8utA@mail.gmail.com> <080001ce66d8$20be6200$623b2600$@augustcellars.com> <CAL02cgTNa6BsLYiai3GDJh6EUotxvQQn_ECn8WHRGdS2X30wNw@mail.gmail.com> <081401ce66e6$fe6ef980$fb4cec80$@augustcellars.com> <CAL02cgRRSR1YYZq0oy8bc87D6XELFN7_7F1XPJUheGQeGuRfmg@mail.gmail.com> <CAL02cgQD8rWkKw04E3Nt_HP==4f6RHZaf3PPm=wsXbQfRbO+eg@mail.gmail.com> <082e01ce66f7$b1d2a390$1577eab0$@augustcellars.com> <CAL02cgRfYQshb6Dk+36y4p7cC9GV-rz5iDKQjeJkWsG=_965bg@mail.gmail.com>
In-Reply-To: <CAL02cgRfYQshb6Dk+36y4p7cC9GV-rz5iDKQjeJkWsG=_965bg@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [jose] Issue #23 - Make crypto indepenent of binary encoding
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 01:30:21 -0000

VEw7RFI6IFJlbW92aW5nIHRoZSBzY2FsaW5nIGxpbWl0YXRpb24gdG8gbWFrZSBKT1NFIGJyb2Fk
bHkgYXBwbGljYWJsZSAoYnkgaW5jdXJyaW5nIGFueSAzMyUgb3ZlcmhlYWQgb2YgYmFzZTY0dXJs
LWVuY29kaW5nIG91dHNpZGUgdGhlIGNyeXB0byBjYWxjdWxhdGlvbikgaXMgYSBjb21wZWxsaW5n
IHJlYXNvbiB0byBhY2NlcHQgYSBjb3N0IG9mIGEgZmV3IGRvemVuIGFkZGl0aW9uYWwgbGluZXMg
b2YgY29kZSBpbiBiaW5hcnktdW5mcmllbmRseSBsYW5ndWFnZXMuDQoNCg0KPj4gIzIzOiBNYWtl
IGNyeXB0byBpbmRlcGVuZGVudCBvZiBiaW5hcnkgZW5jb2RpbmcgKGJhc2U2NCkNCj4+DQo+PiBU
aGUgY3J5cHRvZ3JhcGhpYyBvcGVyYXRpb25zIHRoYXQgSk9TRSBwZXJmb3JtcyBzaG91bGQgbm90
IGRlcGVuZCBvbiB0aGUgIHRyYW5zZmVyIGVuY29kaW5nIHVzZWQgZm9yIGJpbmFyeSBjb21wb25l
bnRzLiAgVGhlIG9wZXJhdGlvbnMgc2hvdWxkIHdvcmsgIGRpcmVjdGx5IG9uIHRoZSBlbmNvZGVk
IGJ5dGUgc3RyaW5ncywgbm90IG9uIHRoZSBlbmNvZGVkIGZvcm0uDQoNCg0KVGhhbmtzIGZvciBh
ZGRpbmcgdGhpcyBpc3N1ZSBSaWNoYXJkLg0KDQpUaGUgcmVhc29uIHRoaXMgY2FuIHdvcmsgZm9y
IHRoZSBKV0UgSlNPTiBzZXJpYWxpemF0aW9uIGlzIHRoYXQgdGhlIHNlcGFyYXRlIHNlZ21lbnRz
IChwcm90ZWN0ZWQgaGVhZGVyLCBJViwgcGxhaW50ZXh0KSBhcmUgcGFzc2VkIGFzIHNlcGFyYXRl
IGFyZ3VtZW50cyB0byB0aGUgQUVBRCBhbGdvcml0aG0gKEFBRCwgSVYsIHBsYWludGV4dCkuIEVh
Y2ggQUVBRCBhbGdvcml0aG0gZW5zdXJlcyB0aGVyZSBjYW4gYmUgbm8gY29uZnVzaW9uIGJldHdl
ZW4gdGhlIGFyZ3VtZW50cy4NCg0KQUVTX0NCQ19ITUFDX1NIQTIsIGZvciBpbnN0YW5jZSwgaW5j
bHVkZXMgdGhlIGxlbmd0aCBvZiB0aGUgQUFEIGluIGl0cyBITUFDIGNhbGN1bGF0aW9uOiBITUFD
KEFBRCB8fCBDSVBIRVJURVhUIHx8IExFTkdUSChBQUQpKS4NCg0KQUVTMjU2R0NNLCBmb3IgaW5z
dGFuY2UsIGNhbGN1bGF0ZXMgaXRzIGF1dGhlbnRpY2F0aW9uIHRhZyBhcyBHSEFTSChBQUQgfHwg
cGFkZGluZyB8fCBDSVBIRVJURVhUIHx8IHBhZGRpbmcgfHwgTEVOR1RIKEFBRCkgfHwgTEVOR1RI
KENJUEhFUlRFWFQpKQ0KDQpTaWduaW5nICYgTUFDIGFsZ29yaXRobXMgYWNjZXB0IGEgc2luZ2xl
IGFyZ3VtZW50IGZvciB0aGUgY29udGVudCB0byBiZSBzaWduZWQsIHdoZXJlYXMgSldTIHdhbnRz
IHRvIHNpZ24gdHdvIGZpZWxkczogaGVhZGVyICYgcGF5bG9hZC4gU28gSk9TRSBuZWVkcyB0byBz
cGVjaWZ5IGhvdyB0aGUgaGVhZGVyIGFuZCBwYXlsb2FkIGFyZSBjb21iaW5lZC4NCg0KQSBnb29k
IHNvbHV0aW9uIGZvciBKT1NFIHdvdWxkIGJlIHRvIGZvbGxvdyB0aGUgZXhhbXBsZSBvZiB0aGVz
ZSBBRUFEIGFsZ29yaXRobXMuIEZvciBpbnN0YW5jZSwgc3BlY2lmeSB0aGF0IHRoZSBieXRlcyB0
byBiZSBzaWduZWQgYXJlIEhFQURFUiB8fCBQQVlMT0FEIHx8IExFTkdUSChIRUFERVIpLCB3aGVy
ZSBIRUFERVIgaXMgdGhlIFVURi04IGVuY29kZWQgaGVhZGVyIEpTT04gb2JqZWN0LiANCg0KDQo+
IDEuwqDCoMKgwqDCoMKgIFVzZSDCoGxlbmd0aCBwcmVmaXggb24gZWFjaCBmaWVsZCDigJMgdGhp
cyBpcyB0aGUgQVNOLjEgZW5jb2RlIGl0IHZlcnNpb24NCj4gMi7CoMKgwqDCoMKgwqAgVXNlIGZp
ZWxkcyB0aGF0IGFyZSB3ZWxsIGRlZmluZWQgaW4gdGVybXMgb2YgZGVsaW1pdGVycw0KPiAzLsKg
wqDCoMKgwqDCoCBQdXQgaW4gc2VwYXJhdGlvbiBjaGFyYWN0ZXJzIHdoaWNoIGFyZSBub3QgYWxs
b3dlZCBpbiBlaXRoZXIgZmllbGQuDQo+wqANCj4gSSBvbmNlIHRyaWVkIHRvIGFyZ3VlIHRoYXQg
dGhpcyBpcyB3aGF0IHdlIHNob3VsZCBkbyBhbmQgZW5kZWQgdXAgd2l0aCB0aGUgZm9sbG93aW5n
OsKgIE1ldGhvZCBvbmUgd2FzIG5vdCBjb25zaWRlcmVkIGFjY2VwdGFibGUsIG1ldGhvZCB0d28g
d2FzIG5vdCBwb3NzaWJsZSBnaXZlbiB0aGUgY3VycmVudCBzdGF0ZSBvZiBKU09OIHBhcnNlcnMs
IG1ldGhvZCB0aHJlZSBpcyB3aGF0IHdlIGN1cnJlbnRseSBkby4NCg0KDQpXZSBzaG91bGQgcmVj
b25zaWRlciBhIHZhcmlhbnQgb2Ygb3B0aW9uIDEgKGluY2x1ZGUgdGhlIGxlbmd0aCBvZiB0aGUg
aGVhZGVyIGF0IHRoZSBlbmQpLg0KDQpBcHBseWluZyBjcnlwdG8gKGVnIEhBU0ggb3IgRU5DL0RF
QykgdG8gYSBiYXNlNjR1cmwgZW5jb2RpbmcgbWVhbnMgdGhlcmUgd2lsbCBhbHdheXMgYmUgYSAz
MyUgb3ZlcmhlYWQuIEFwcGx5aW5nIGl0IHRvIGEgY29uY2F0ZW5hdGlvbiBvZiBieXRlcyBwbHVz
IGEgbGVuZ3RoIGZpZWxkIG1lYW5zIHRoZXJlIGlzIGEgZml4ZWQgb3ZlcmhlYWQgKGVnIDggYnl0
ZXMpLiBCb3RoIGNhbiBiZSBpZ25vcmVkIGZvciBzbWFsbCBtZXNzYWdlcy4gQSAzMyUgb3Zlcmhl
YWQgd2lsbCBiZSBhIHNob3dzdG9wcGVyIGZvciBsYXJnZSBtZXNzYWdlcy4NCg0KU21hbGwgbWVz
c2FnZXMgaXMgYSBwcmltYXJ5IHVzZSBjYXNlIGZvciBKT1NFIHRvZGF5LiBXaXRob3V0IGJlaW5n
IGFibGUgdG8gc2NhbGUgZWZmaWNpZW50bHkgdGhvdWdoLCB3ZSBhcmUgY3JpcHBsaW5nIGl0cyB3
aWRlciBhcHBsaWNhYmlsaXR5LiBUaGVyZSB3b3VsZCBiZSBvbmdvaW5nIHByZXNzdXJlIHRvIHVz
ZSBzb21ldGhpbmcgb3RoZXIgdGhhbiBKT1NFIHdoZW5ldmVyIGEgcHJvdG9jb2wgbWlnaHQgaGFu
ZGxlIG1lc3NhZ2VzIHRoYXQgYXJlIG1lZGl1bS1zaXplZCBvciBsYXJnZXIuDQoNClRoZSBkb3du
c2lkZSBvZiBub3Qgc2lnbmluZyB0aGUgYmFzZTY0dXJsLWVuY29kaW5nIGlzIHRoYXQgSk9TRSBs
aWJyYXJpZXMgbmVlZCB0byBoYW5kbGUgYnl0ZXMsIGluc3RlYWQgb2Ygc3RyaW5ncywgaW4gYSBm
ZXcgbW9yZSBwbGFjZXMuIFRoYXQgd2lsbCBhZGQgc29tZSB3b3JrIGluIHNvbWUgYmluYXJ5LXVu
ZnJpZW5kbHkgbGFuZ3VhZ2VzLiBNeSBndWVzcyBpcyB0aGF0IHRoZSBleHRyYSB3b3JrIGlzIG9m
IHRoZSBvcmRlciBvZiBkb3plbnMgb24gbGluZXMgb2YgY29kZS4gUmVtb3ZpbmcgdGhlIHNjYWxp
bmcgbGltaXRhdGlvbiB0byBtYWtlIEpPU0UgYnJvYWRseSBhcHBsaWNhYmxlIGlzIGEgY29tcGVs
bGluZyByZWFzb24gdG8gYWNjZXB0IHRoYXQgZXh0cmEgd29yay4NCg0KLS0NCkphbWVzIE1hbmdl
cg0K

From dick.hardt@gmail.com  Tue Jun 11 20:24:26 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B54121F9A29 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 20:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.617
X-Spam-Level: 
X-Spam-Status: No, score=-1.617 tagged_above=-999 required=5 tests=[AWL=0.983,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DLboCtvVTSdy for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 20:24:25 -0700 (PDT)
Received: from mail-bk0-x22f.google.com (mail-bk0-x22f.google.com [IPv6:2a00:1450:4008:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 33E7F21F9A27 for <jose@ietf.org>; Tue, 11 Jun 2013 20:24:24 -0700 (PDT)
Received: by mail-bk0-f47.google.com with SMTP id jg1so4061256bkc.6 for <jose@ietf.org>; Tue, 11 Jun 2013 20:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1lvr0V29dGdTcYlACI7BY7WqON3GOa4IP1eHaNzkIRk=; b=ayhbDekuAtfr2Lzp4u5K2qYpcWiAa7qp2Tr95VX+JfwjQQ/0EZiwuBzBkmqsw9jnkZ woiVMqswyZBNlJdU9K1S/4LfleYyHdSpwamZhKQPffKukqjMm7pQWYXLTt0BsOZf+Yzd JJjYRv6aCVgVPTTTYoA63XA5q/PjtTVXfHsALo+0AgG8N8bIp81Cra6rUeU46Mgz+pgO S2x6jc+tM5Lt5Ej0i7KyKnxkzfCKjQ2n1qxmqNeQqOlNmD8lUHA4scxL9cxbPvhKO18I dgm+UlCh/h1OASt1+a9hWLYg4ZaZ9Bacc17TAdOTb0R05YM7PE7daO2zruYUPMVvhS7y pJqQ==
X-Received: by 10.205.37.16 with SMTP id tc16mr1168186bkb.100.1371007463904; Tue, 11 Jun 2013 20:24:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.168.12 with HTTP; Tue, 11 Jun 2013 20:24:03 -0700 (PDT)
In-Reply-To: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Tue, 11 Jun 2013 20:24:03 -0700
Message-ID: <CAD9ie-sntiA+nQk9XnwfUNdGDiEZ78zFQB9HAyJ-1TOQvaxNeA@mail.gmail.com>
To: jose issue tracker <trac+jose@trac.tools.ietf.org>
Content-Type: multipart/alternative; boundary=bcaec52c5d49df096604deec8c86
Cc: Richard Barnes <rlb@ipv.sx>, draft-barnes-jose-use-cases@tools.ietf.org, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 03:24:26 -0000

--bcaec52c5d49df096604deec8c86
Content-Type: text/plain; charset=ISO-8859-1

I don't understand what is being suggested. What is the conversion to UTF-8
for?


On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <
trac+jose@trac.tools.ietf.org> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>  The cryptographic operations that JOSE performs should not depend on the
>  transfer encoding used for binary components.  The operations should work
>  directly on the encoded byte strings, not on the encoded form.
>
>  This is already true for content, IV, ciphertext, encrypted key, and
>  authentication tag.  The only thing that needs fixing is the protected
>  header value.  That's a little tricky, since the protected header value is
>  JSON, which doesn't have a standard encoding.  But it's not that onerous
>  just to convert it to UTF-8 -- in fact, senders are already required to
>  convert the protected header to UTF-8.
>
>  So the only change is to require recipients to convert the protected
>  header to UTF-8 before using it.   This can be accomplished with two minor
>  changes:
>
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  signature-11#section-5.2>
>  OLD: "The resulting JWS Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWS Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  encryption-11#section-5.2>
>  OLD: "The resulting JWE Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWE Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>
> --
> -------------------------------------+-------------------------------------
>  Reporter:  rlb@ipv.sx               |      Owner:  draft-barnes-jose-use-
>      Type:  defect                   |  cases@tools.ietf.org
>  Priority:  major                    |     Status:  new
> Component:  draft-barnes-jose-use-   |  Milestone:
>   cases                              |    Version:
>  Severity:  -                        |   Keywords:
> -------------------------------------+-------------------------------------
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--bcaec52c5d49df096604deec8c86
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t understand what is being suggested. What is th=
e conversion to UTF-8 for?</div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:trac+jose@trac.tools.ietf.org" target=
=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">#23: Make crypto independent of binary encod=
ing (base64)<br>
<br>
=A0The cryptographic operations that JOSE performs should not depend on the=
<br>
=A0transfer encoding used for binary components. =A0The operations should w=
ork<br>
=A0directly on the encoded byte strings, not on the encoded form.<br>
<br>
=A0This is already true for content, IV, ciphertext, encrypted key, and<br>
=A0authentication tag. =A0The only thing that needs fixing is the protected=
<br>
=A0header value. =A0That&#39;s a little tricky, since the protected header =
value is<br>
=A0JSON, which doesn&#39;t have a standard encoding. =A0But it&#39;s not th=
at onerous<br>
=A0just to convert it to UTF-8 -- in fact, senders are already required to<=
br>
=A0convert the protected header to UTF-8.<br>
<br>
=A0So the only change is to require recipients to convert the protected<br>
=A0header to UTF-8 before using it. =A0 This can be accomplished with two m=
inor<br>
=A0changes:<br>
<br>
=A0&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-" tar=
get=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a><br>
=A0signature-11#section-5.2&gt;<br>
=A0OLD: &quot;The resulting JWS Protected Header MUST be a completely valid=
 JSON<br>
=A0object conforming to RFC 4627 [RFC4627].&quot;<br>
=A0NEW: &quot;The resulting JWS Protected Header MUST be a completely valid=
 JSON<br>
=A0object conforming to RFC 4627 [RFC4627]. =A0If the JWE Protected Header =
is<br>
=A0valid, convert it to the UTF-8 encoding. =A0Otherwise, reject the JWE.&q=
uot;<br>
<br>
=A0&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-" tar=
get=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a><br>
=A0encryption-11#section-5.2&gt;<br>
=A0OLD: &quot;The resulting JWE Protected Header MUST be a completely valid=
 JSON<br>
=A0object conforming to RFC 4627 [RFC4627].&quot;<br>
=A0NEW: &quot;The resulting JWE Protected Header MUST be a completely valid=
 JSON<br>
=A0object conforming to RFC 4627 [RFC4627]. =A0If the JWE Protected Header =
is<br>
=A0valid, convert it to the UTF-8 encoding. =A0Otherwise, reject the JWE.&q=
uot;<br>
<br>
--<br>
-------------------------------------+-------------------------------------=
<br>
=A0Reporter: =A0rlb@ipv.sx =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0Owner: =
=A0draft-barnes-jose-use-<br>
=A0 =A0 =A0Type: =A0defect =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0<a href=
=3D"mailto:cases@tools.ietf.org">cases@tools.ietf.org</a><br>
=A0Priority: =A0major =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 Stat=
us: =A0new<br>
Component: =A0draft-barnes-jose-use- =A0 | =A0Milestone:<br>
=A0 cases =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =
=A0Version:<br>
=A0Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 Keyw=
ords:<br>
-------------------------------------+-------------------------------------=
<br>
<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/2=
3" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a>&=
gt;<br>
jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">http://t=
ools.ietf.org/jose/</a>&gt;<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote></div><br></div>

--bcaec52c5d49df096604deec8c86--

From tbray@textuality.com  Tue Jun 11 21:20:57 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2017121F9BB4 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 21:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.464
X-Spam-Level: 
X-Spam-Status: No, score=0.464 tagged_above=-999 required=5 tests=[AWL=-0.893,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qk1y4wDCMCJb for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 21:20:48 -0700 (PDT)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id C823C21F9B9E for <jose@ietf.org>; Tue, 11 Jun 2013 21:20:47 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id q12so2827613vbe.13 for <jose@ietf.org>; Tue, 11 Jun 2013 21:20:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ym5Gy/rxAqkdku2KLEtz9ektpfmC9FeB8ihi9WsTAlY=; b=mAOiPWIzz7CY3cJlo6c3nfZG7GZimkk36WeDtnWIA/VgtWzMopLwgVyIyHCYN5Wc9g /vq6dylw5JVdb8Wrda6t0qo23SMhsZCr7q3IAu/4eXxUB5TnepWP4jbPTT98+g9KH6h2 1dacWnG1wJ5ypANGaxfymOeenqJVx1hfsh73yNUpZxS0V9yPSl65j0wFWT9Mb5Z6JXaV O4YHCNOPNsBVqH7eOuWPOC1TgDYSou+ednG91wwUk83T1pPuJIBlRL7ApL9tqwpeb/eD xjjeW/rq/oaCPM09sAmW8IS9z6RecsQg/dhtiMzlG+ce0thftXntu8PHdSciuFlAxWkS gVrw==
MIME-Version: 1.0
X-Received: by 10.58.40.42 with SMTP id u10mr4388603vek.39.1371010846940; Tue, 11 Jun 2013 21:20:46 -0700 (PDT)
Received: by 10.220.25.199 with HTTP; Tue, 11 Jun 2013 21:20:46 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
Date: Tue, 11 Jun 2013 21:20:46 -0700
Message-ID: <CAHBU6isGzV1ZM1xczwK3v-rcusDwv6LHkag3KwX2QH+UFWGzpQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: jose issue tracker <trac+jose@trac.tools.ietf.org>
Content-Type: multipart/alternative; boundary=089e0129420c83f47404deed5691
X-Gm-Message-State: ALoCoQlAvNtlnSji+Lz+1IY1xGRp2XsF9nriaWahrZ3qTXpH8icxtEGgojrzdz7m8Ss0iCMn+ivC
Cc: Richard Barnes <rlb@ipv.sx>, draft-barnes-jose-use-cases@tools.ietf.org, jose <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 04:20:57 -0000

--089e0129420c83f47404deed5691
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I haven=E2=80=99t been following this closely, but someone who uses JWTs (t=
here are
a lot of them out there) asked me =E2=80=9CWouldn=E2=80=99t this break all =
the existing JWT
libraries and software deployed in production?=E2=80=9D  I=E2=80=99m not 10=
0% sure, but it
looks to me like the answer is yes.  Since i observe empirically that JWTs
work very well in production for federated login and many other
applications, and offer a level of security that is acceptable to some of
the most paranoid security organizations in the world, I think this
proposal is not remotely close to being cost-effective.

Forgive me if I=E2=80=99m wrong and this wouldn=E2=80=99t actually break JW=
Ts.  -T


On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <
trac+jose@trac.tools.ietf.org> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>  The cryptographic operations that JOSE performs should not depend on the
>  transfer encoding used for binary components.  The operations should wor=
k
>  directly on the encoded byte strings, not on the encoded form.
>
>  This is already true for content, IV, ciphertext, encrypted key, and
>  authentication tag.  The only thing that needs fixing is the protected
>  header value.  That's a little tricky, since the protected header value =
is
>  JSON, which doesn't have a standard encoding.  But it's not that onerous
>  just to convert it to UTF-8 -- in fact, senders are already required to
>  convert the protected header to UTF-8.
>
>  So the only change is to require recipients to convert the protected
>  header to UTF-8 before using it.   This can be accomplished with two min=
or
>  changes:
>
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  signature-11#section-5.2>
>  OLD: "The resulting JWS Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWS Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  encryption-11#section-5.2>
>  OLD: "The resulting JWE Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWE Protected Header MUST be a completely valid JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>
> --
> -------------------------------------+-----------------------------------=
--
>  Reporter:  rlb@ipv.sx               |      Owner:  draft-barnes-jose-use=
-
>      Type:  defect                   |  cases@tools.ietf.org
>  Priority:  major                    |     Status:  new
> Component:  draft-barnes-jose-use-   |  Milestone:
>   cases                              |    Version:
>  Severity:  -                        |   Keywords:
> -------------------------------------+-----------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--089e0129420c83f47404deed5691
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I haven=E2=80=99t been following this closely, but so=
meone who uses JWTs (there are a lot of them out there) asked me =E2=80=9CW=
ouldn=E2=80=99t this break all the existing JWT libraries and software depl=
oyed in production?=E2=80=9D=C2=A0 I=E2=80=99m not 100% sure, but it looks =
to me like the answer is yes.=C2=A0 Since i observe empirically that JWTs w=
ork very well in production for federated login and many other applications=
, and offer a level of security that is acceptable to some of the most para=
noid security organizations in the world, I think this proposal is not remo=
tely close to being cost-effective.<br>
<br></div>Forgive me if I=E2=80=99m wrong and this wouldn=E2=80=99t actuall=
y break JWTs.=C2=A0 -T<br></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:trac+jose@trac.tools.ietf.org" target=
=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">#23: Make crypto independent of binary encod=
ing (base64)<br>
<br>
=C2=A0The cryptographic operations that JOSE performs should not depend on =
the<br>
=C2=A0transfer encoding used for binary components. =C2=A0The operations sh=
ould work<br>
=C2=A0directly on the encoded byte strings, not on the encoded form.<br>
<br>
=C2=A0This is already true for content, IV, ciphertext, encrypted key, and<=
br>
=C2=A0authentication tag. =C2=A0The only thing that needs fixing is the pro=
tected<br>
=C2=A0header value. =C2=A0That&#39;s a little tricky, since the protected h=
eader value is<br>
=C2=A0JSON, which doesn&#39;t have a standard encoding. =C2=A0But it&#39;s =
not that onerous<br>
=C2=A0just to convert it to UTF-8 -- in fact, senders are already required =
to<br>
=C2=A0convert the protected header to UTF-8.<br>
<br>
=C2=A0So the only change is to require recipients to convert the protected<=
br>
=C2=A0header to UTF-8 before using it. =C2=A0 This can be accomplished with=
 two minor<br>
=C2=A0changes:<br>
<br>
=C2=A0&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-" =
target=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a><=
br>
=C2=A0signature-11#section-5.2&gt;<br>
=C2=A0OLD: &quot;The resulting JWS Protected Header MUST be a completely va=
lid JSON<br>
=C2=A0object conforming to RFC 4627 [RFC4627].&quot;<br>
=C2=A0NEW: &quot;The resulting JWS Protected Header MUST be a completely va=
lid JSON<br>
=C2=A0object conforming to RFC 4627 [RFC4627]. =C2=A0If the JWE Protected H=
eader is<br>
=C2=A0valid, convert it to the UTF-8 encoding. =C2=A0Otherwise, reject the =
JWE.&quot;<br>
<br>
=C2=A0&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-" =
target=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a><=
br>
=C2=A0encryption-11#section-5.2&gt;<br>
=C2=A0OLD: &quot;The resulting JWE Protected Header MUST be a completely va=
lid JSON<br>
=C2=A0object conforming to RFC 4627 [RFC4627].&quot;<br>
=C2=A0NEW: &quot;The resulting JWE Protected Header MUST be a completely va=
lid JSON<br>
=C2=A0object conforming to RFC 4627 [RFC4627]. =C2=A0If the JWE Protected H=
eader is<br>
=C2=A0valid, convert it to the UTF-8 encoding. =C2=A0Otherwise, reject the =
JWE.&quot;<br>
<br>
--<br>
-------------------------------------+-------------------------------------=
<br>
=C2=A0Reporter: =C2=A0rlb@ipv.sx =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 | =C2=A0 =C2=A0 =C2=A0Owner: =C2=A0draft-barnes-jose-use-<br>
=C2=A0 =C2=A0 =C2=A0Type: =C2=A0defect =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0<a href=3D"mailto:cases@tools.ietf.org"=
>cases@tools.ietf.org</a><br>
=C2=A0Priority: =C2=A0major =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 Status: =C2=A0new<br>
Component: =C2=A0draft-barnes-jose-use- =C2=A0 | =C2=A0Milestone:<br>
=C2=A0 cases =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0Version:<br>
=C2=A0Severity: =C2=A0- =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 Keywords:<br>
-------------------------------------+-------------------------------------=
<br>
<br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/2=
3" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a>&=
gt;<br>
jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">http://t=
ools.ietf.org/jose/</a>&gt;<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote></div><br></div>

--089e0129420c83f47404deed5691--

From ve7jtb@ve7jtb.com  Tue Jun 11 23:16:56 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212C521F9C14 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 23:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hv-ilOkEbzCn for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 23:16:54 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE4C21F9A43 for <jose@ietf.org>; Tue, 11 Jun 2013 23:16:54 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id n11so165966wgh.33 for <jose@ietf.org>; Tue, 11 Jun 2013 23:16:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=/aodH3k4QT054dko/eUogm/3OcI9tGE9VG4N79jYzQ8=; b=FMA5qw6NWtIBb5IcOdcm19tunDrv6/byxreC8c4CVAy35FZbMtvi9055OhBQUu2xkj OFPipXJ6Q+Bgl6SoqU+Ui99gIlqtKkoNIdkSQW3nad0nh+lFXEr4JFsCICu/vIy1eDb5 /U80rPythfEs5m+Iavynte1vlhVAJ3/KlvzweUz1Jq+eCO/lYKCU8LOrqh77wV/Be6ZR ygm6OMMmAIZxYsXj/l4GgJtSsVOYN6AhYMLqZER+9Z7vj7tJA4VL8zURjpA0xAUkzCUB eXO1IDZSA+FcOqbf2Lqi2zSzYl7h4IAfDRFvbSBUpZWRSPBzzPton091n3PE2A+L8/iE tDbA==
X-Received: by 10.180.108.3 with SMTP id hg3mr3393921wib.17.1371017809881; Tue, 11 Jun 2013 23:16:49 -0700 (PDT)
Received: from [192.168.50.14] ([87.213.45.202]) by mx.google.com with ESMTPSA id ay7sm989225wib.9.2013.06.11.23.16.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Jun 2013 23:16:47 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_AE67C745-56E4-4731-A6A1-3CE501A6BF7C"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CAHBU6isGzV1ZM1xczwK3v-rcusDwv6LHkag3KwX2QH+UFWGzpQ@mail.gmail.com>
Date: Wed, 12 Jun 2013 08:16:46 +0200
Message-Id: <637787CD-63D9-4FCC-8DFE-AF0692C262B3@ve7jtb.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <CAHBU6isGzV1ZM1xczwK3v-rcusDwv6LHkag3KwX2QH+UFWGzpQ@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmw38fimSJwdpdvVVcpAUYezagw6m+b4SFi4oFzWiirGMjhlMisu+3w+/5gOq+mXcAfnK6O
Cc: Richard Barnes <rlb@ipv.sx>, draft-barnes-jose-use-cases@tools.ietf.org, jose issue tracker <trac+jose@trac.tools.ietf.org>, jose <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 06:16:56 -0000

--Apple-Mail=_AE67C745-56E4-4731-A6A1-3CE501A6BF7C
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_ACCCCBB6-F417-4BF0-893D-27ED3958F8F6"


--Apple-Mail=_ACCCCBB6-F417-4BF0-893D-27ED3958F8F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Changing what the integrity is calculated over is about a big breaking =
change.

I have personally considered alternate encodings for constrained =
environments (internet of things) however the format we have now has the =
advantage that it is hard for developers to get wrong, unlike xmldsig.

Jim made a good point that you have to encode the length of the parts or =
have a separator that cannot appear in the parts.=20

I expect that escaping every "." in the JSON is not going to work very =
well.=20

We know what we have works.  It is possible to have long debates over =
things that won't work.

The integrity has always been calculated this way,  It is not new.

John B.


On 2013-06-12, at 6:20 AM, Tim Bray <tbray@textuality.com> wrote:

> I haven=92t been following this closely, but someone who uses JWTs =
(there are a lot of them out there) asked me =93Wouldn=92t this break =
all the existing JWT libraries and software deployed in production?=94  =
I=92m not 100% sure, but it looks to me like the answer is yes.  Since i =
observe empirically that JWTs work very well in production for federated =
login and many other applications, and offer a level of security that is =
acceptable to some of the most paranoid security organizations in the =
world, I think this proposal is not remotely close to being =
cost-effective.
>=20
> Forgive me if I=92m wrong and this wouldn=92t actually break JWTs.  -T
>=20
>=20
> On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker =
<trac+jose@trac.tools.ietf.org> wrote:
> #23: Make crypto independent of binary encoding (base64)
>=20
>  The cryptographic operations that JOSE performs should not depend on =
the
>  transfer encoding used for binary components.  The operations should =
work
>  directly on the encoded byte strings, not on the encoded form.
>=20
>  This is already true for content, IV, ciphertext, encrypted key, and
>  authentication tag.  The only thing that needs fixing is the =
protected
>  header value.  That's a little tricky, since the protected header =
value is
>  JSON, which doesn't have a standard encoding.  But it's not that =
onerous
>  just to convert it to UTF-8 -- in fact, senders are already required =
to
>  convert the protected header to UTF-8.
>=20
>  So the only change is to require recipients to convert the protected
>  header to UTF-8 before using it.   This can be accomplished with two =
minor
>  changes:
>=20
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  signature-11#section-5.2>
>  OLD: "The resulting JWS Protected Header MUST be a completely valid =
JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWS Protected Header MUST be a completely valid =
JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header =
is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>=20
>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>  encryption-11#section-5.2>
>  OLD: "The resulting JWE Protected Header MUST be a completely valid =
JSON
>  object conforming to RFC 4627 [RFC4627]."
>  NEW: "The resulting JWE Protected Header MUST be a completely valid =
JSON
>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header =
is
>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>=20
> --
> =
-------------------------------------+------------------------------------=
-
>  Reporter:  rlb@ipv.sx               |      Owner:  =
draft-barnes-jose-use-
>      Type:  defect                   |  cases@tools.ietf.org
>  Priority:  major                    |     Status:  new
> Component:  draft-barnes-jose-use-   |  Milestone:
>   cases                              |    Version:
>  Severity:  -                        |   Keywords:
> =
-------------------------------------+------------------------------------=
-
>=20
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_ACCCCBB6-F417-4BF0-893D-27ED3958F8F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><meta http-equiv=3D"Content-Type" =
content=3D"text/html charset=3Dwindows-1252"><meta =
http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Changing what the integrity is calculated over is about a big breaking =
change.<div><br></div><div>I have personally considered alternate =
encodings for constrained environments (internet of things) however the =
format we have now has the advantage that it is hard for developers to =
get wrong, unlike xmldsig.</div><div><br></div><div>Jim made a good =
point that you have to encode the length of the parts or have a =
separator that cannot appear in the =
parts.&nbsp;</div><div><br></div><div>I expect that escaping every "." =
in the JSON is not going to work very =
well.&nbsp;</div><div><br></div><div>We know what we have works. =
&nbsp;It is possible to have long debates over things that won't =
work.</div><div><br></div><div>The integrity has always been calculated =
this way, &nbsp;It is not new.</div><div><br></div><div>John =
B.<br><div><br></div><div><br><div><div>On 2013-06-12, at 6:20 AM, Tim =
Bray &lt;<a =
href=3D"mailto:tbray@textuality.com">tbray@textuality.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div>I haven=92t been following this =
closely, but someone who uses JWTs (there are a lot of them out there) =
asked me =93Wouldn=92t this break all the existing JWT libraries and =
software deployed in production?=94&nbsp; I=92m not 100% sure, but it =
looks to me like the answer is yes.&nbsp; Since i observe empirically =
that JWTs work very well in production for federated login and many =
other applications, and offer a level of security that is acceptable to =
some of the most paranoid security organizations in the world, I think =
this proposal is not remotely close to being cost-effective.<br>
<br></div>Forgive me if I=92m wrong and this wouldn=92t actually break =
JWTs.&nbsp; -T<br></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Tue, Jun 11, 2013 at 10:58 AM, jose issue =
tracker <span dir=3D"ltr">&lt;<a =
href=3D"mailto:trac+jose@trac.tools.ietf.org" =
target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">#23: Make crypto =
independent of binary encoding (base64)<br>
<br>
&nbsp;The cryptographic operations that JOSE performs should not depend =
on the<br>
&nbsp;transfer encoding used for binary components. &nbsp;The operations =
should work<br>
&nbsp;directly on the encoded byte strings, not on the encoded form.<br>
<br>
&nbsp;This is already true for content, IV, ciphertext, encrypted key, =
and<br>
&nbsp;authentication tag. &nbsp;The only thing that needs fixing is the =
protected<br>
&nbsp;header value. &nbsp;That's a little tricky, since the protected =
header value is<br>
&nbsp;JSON, which doesn't have a standard encoding. &nbsp;But it's not =
that onerous<br>
&nbsp;just to convert it to UTF-8 -- in fact, senders are already =
required to<br>
&nbsp;convert the protected header to UTF-8.<br>
<br>
&nbsp;So the only change is to require recipients to convert the =
protected<br>
&nbsp;header to UTF-8 before using it. &nbsp; This can be accomplished =
with two minor<br>
&nbsp;changes:<br>
<br>
&nbsp;&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-"=
 =
target=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a>=
<br>
&nbsp;signature-11#section-5.2&gt;<br>
&nbsp;OLD: "The resulting JWS Protected Header MUST be a completely =
valid JSON<br>
&nbsp;object conforming to RFC 4627 [RFC4627]."<br>
&nbsp;NEW: "The resulting JWS Protected Header MUST be a completely =
valid JSON<br>
&nbsp;object conforming to RFC 4627 [RFC4627]. &nbsp;If the JWE =
Protected Header is<br>
&nbsp;valid, convert it to the UTF-8 encoding. &nbsp;Otherwise, reject =
the JWE."<br>
<br>
&nbsp;&lt;<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-"=
 =
target=3D"_blank">http://tools.ietf.org/html/draft-ietf-jose-json-web-</a>=
<br>
&nbsp;encryption-11#section-5.2&gt;<br>
&nbsp;OLD: "The resulting JWE Protected Header MUST be a completely =
valid JSON<br>
&nbsp;object conforming to RFC 4627 [RFC4627]."<br>
&nbsp;NEW: "The resulting JWE Protected Header MUST be a completely =
valid JSON<br>
&nbsp;object conforming to RFC 4627 [RFC4627]. &nbsp;If the JWE =
Protected Header is<br>
&nbsp;valid, convert it to the UTF-8 encoding. &nbsp;Otherwise, reject =
the JWE."<br>
<br>
--<br>
=
-------------------------------------+------------------------------------=
-<br>
&nbsp;Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a> =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; =
&nbsp;Owner: &nbsp;draft-barnes-jose-use-<br>
&nbsp; &nbsp; &nbsp;Type: &nbsp;defect &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;<a =
href=3D"mailto:cases@tools.ietf.org">cases@tools.ietf.org</a><br>
&nbsp;Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; Status: &nbsp;new<br>
Component: &nbsp;draft-barnes-jose-use- &nbsp; | &nbsp;Milestone:<br>
&nbsp; cases &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp;Version:<br>
&nbsp;Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Keywords:<br>
=
-------------------------------------+------------------------------------=
-<br>
<br>
Ticket URL: &lt;<a =
href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/23" =
target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a>&gt=
;<br>
jose &lt;<a href=3D"http://tools.ietf.org/jose/" =
target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote></div><br></div>
_______________________________________________<br>jose mailing =
list<br><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/m=
ailman/listinfo/jose</a><br></blockquote></div><br></div></div></body></ht=
ml>=

--Apple-Mail=_ACCCCBB6-F417-4BF0-893D-27ED3958F8F6--

--Apple-Mail=_AE67C745-56E4-4731-A6A1-3CE501A6BF7C
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjEyMDYxNjQ3WjAjBgkqhkiG9w0BCQQxFgQUJY6zbwam
57qfLyG0ugwW1dTM0powgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAbQZRXVs13x3F6ziN5hzYB5NTyQd5bYzkBE5y2aT0
q0yOlFKCC6w1a8JGDWe8fUlKWmoIyaQB7FzZzq1Mfqz6Zzm64utaSmUVSrN5ZUWGeqOuak8zHEzJ
5VmjL8RWhVWsEsKdYUV15DwhZHaR3xmOvX3/UiXpFlHsMjNuMkxcg25ciQz5D5X1SL+jp/Z5nGs1
MWeM2FZu8CeB9BmmoiuXwfF1GNXdyh7oOSJLXbI4LBRofhfobue/lwtVMw41y2Tw0qsrMc/zRyM5
RMmCotLBB9OCa6T+koXO1O04qXeLknCVmQ8kH35V+QAdS4QipKM1d2+uTe4m/eTo64qu+u2JLQAA
AAAAAA==

--Apple-Mail=_AE67C745-56E4-4731-A6A1-3CE501A6BF7C--

From roland.hedberg@adm.umu.se  Tue Jun 11 23:41:26 2013
Return-Path: <roland.hedberg@adm.umu.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B365F21F9C14 for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 23:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9LeEOKRrKRRO for <jose@ietfa.amsl.com>; Tue, 11 Jun 2013 23:41:22 -0700 (PDT)
Received: from mail.ad.umu.se (umdac-ch2.ad.umu.se [130.239.1.247]) by ietfa.amsl.com (Postfix) with ESMTP id ED58121F9BFB for <jose@ietf.org>; Tue, 11 Jun 2013 23:41:21 -0700 (PDT)
Received: from UMDAC-CCR1.ad.umu.se ([169.254.1.99]) by UMDAC-CH2.ad.umu.se ([130.239.1.247]) with mapi; Wed, 12 Jun 2013 08:40:42 +0200
From: Roland Hedberg <roland.hedberg@adm.umu.se>
To: John Bradley <ve7jtb@ve7jtb.com>
Date: Wed, 12 Jun 2013 08:41:18 +0200
Thread-Topic: [jose] #23: Make crypto independent of binary encoding (base64)
Thread-Index: Ac5nN8HYCVBz1bCaTZegrAh2UJbqXg==
Message-ID: <AA7739BD-285F-4C94-B503-A2F2C945CC3B@adm.umu.se>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <CAHBU6isGzV1ZM1xczwK3v-rcusDwv6LHkag3KwX2QH+UFWGzpQ@mail.gmail.com> <637787CD-63D9-4FCC-8DFE-AF0692C262B3@ve7jtb.com>
In-Reply-To: <637787CD-63D9-4FCC-8DFE-AF0692C262B3@ve7jtb.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, sv-SE
Content-Type: multipart/mixed; boundary="_003_AA7739BD285F4C94B503A2F2C945CC3Badmumuse_"
MIME-Version: 1.0
Cc: Richard Barnes <rlb@ipv.sx>, "draft-barnes-jose-use-cases@tools.ietf.org" <draft-barnes-jose-use-cases@tools.ietf.org>, jose issue tracker <trac+jose@trac.tools.ietf.org>, Tim Bray <tbray@textuality.com>, jose <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 06:41:26 -0000

--_003_AA7739BD285F4C94B503A2F2C945CC3Badmumuse_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I'm completely behind John on this.
Also, being one that has a JWT library implementation I can support Tim in =
that this is a breaking change.
A change that I'm definitely against.

12 jun 2013 kl. 08:16 skrev John Bradley <ve7jtb@ve7jtb.com>:

> Changing what the integrity is calculated over is about a big breaking ch=
ange.
>=20
> I have personally considered alternate encodings for constrained environm=
ents (internet of things) however the format we have now has the advantage =
that it is hard for developers to get wrong, unlike xmldsig.
>=20
> Jim made a good point that you have to encode the length of the parts or =
have a separator that cannot appear in the parts.=20
>=20
> I expect that escaping every "." in the JSON is not going to work very we=
ll.=20
>=20
> We know what we have works.  It is possible to have long debates over thi=
ngs that won't work.
>=20
> The integrity has always been calculated this way,  It is not new.
>=20
> John B.
>=20
>=20
> On 2013-06-12, at 6:20 AM, Tim Bray <tbray@textuality.com> wrote:
>=20
>> I haven=92t been following this closely, but someone who uses JWTs (ther=
e are a lot of them out there) asked me =93Wouldn=92t this break all the ex=
isting JWT libraries and software deployed in production?=94  I=92m not 100=
% sure, but it looks to me like the answer is yes.  Since i observe empiric=
ally that JWTs work very well in production for federated login and many ot=
her applications, and offer a level of security that is acceptable to some =
of the most paranoid security organizations in the world, I think this prop=
osal is not remotely close to being cost-effective.
>>=20
>> Forgive me if I=92m wrong and this wouldn=92t actually break JWTs.  -T
>>=20
>>=20
>> On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <trac+jose@trac.too=
ls.ietf.org> wrote:
>> #23: Make crypto independent of binary encoding (base64)
>>=20
>>  The cryptographic operations that JOSE performs should not depend on th=
e
>>  transfer encoding used for binary components.  The operations should wo=
rk
>>  directly on the encoded byte strings, not on the encoded form.
>>=20
>>  This is already true for content, IV, ciphertext, encrypted key, and
>>  authentication tag.  The only thing that needs fixing is the protected
>>  header value.  That's a little tricky, since the protected header value=
 is
>>  JSON, which doesn't have a standard encoding.  But it's not that onerou=
s
>>  just to convert it to UTF-8 -- in fact, senders are already required to
>>  convert the protected header to UTF-8.
>>=20
>>  So the only change is to require recipients to convert the protected
>>  header to UTF-8 before using it.   This can be accomplished with two mi=
nor
>>  changes:
>>=20
>>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>>  signature-11#section-5.2>
>>  OLD: "The resulting JWS Protected Header MUST be a completely valid JSO=
N
>>  object conforming to RFC 4627 [RFC4627]."
>>  NEW: "The resulting JWS Protected Header MUST be a completely valid JSO=
N
>>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header i=
s
>>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>>=20
>>  <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>>  encryption-11#section-5.2>
>>  OLD: "The resulting JWE Protected Header MUST be a completely valid JSO=
N
>>  object conforming to RFC 4627 [RFC4627]."
>>  NEW: "The resulting JWE Protected Header MUST be a completely valid JSO=
N
>>  object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header i=
s
>>  valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>>=20
>> --
>> -------------------------------------+----------------------------------=
---
>>  Reporter:  rlb@ipv.sx               |      Owner:  draft-barnes-jose-us=
e-
>>      Type:  defect                   |  cases@tools.ietf.org
>>  Priority:  major                    |     Status:  new
>> Component:  draft-barnes-jose-use-   |  Milestone:
>>   cases                              |    Version:
>>  Severity:  -                        |   Keywords:
>> -------------------------------------+----------------------------------=
---
>>=20
>> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
>> jose <http://tools.ietf.org/jose/>
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>=20

--_003_AA7739BD285F4C94B503A2F2C945CC3Badmumuse_
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Description: smime.p7s
Content-Disposition: attachment; filename="smime.p7s"; size=4507;
	creation-date="Wed, 12 Jun 2013 06:40:41 GMT";
	modification-date="Wed, 12 Jun 2013 06:40:41 GMT"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjEyMDYxNjQ3WjAjBgkqhkiG9w0BCQQxFgQUJY6zbwam
57qfLyG0ugwW1dTM0powgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAbQZRXVs13x3F6ziN5hzYB5NTyQd5bYzkBE5y2aT0
q0yOlFKCC6w1a8JGDWe8fUlKWmoIyaQB7FzZzq1Mfqz6Zzm64utaSmUVSrN5ZUWGeqOuak8zHEzJ
5VmjL8RWhVWsEsKdYUV15DwhZHaR3xmOvX3/UiXpFlHsMjNuMkxcg25ciQz5D5X1SL+jp/Z5nGs1
MWeM2FZu8CeB9BmmoiuXwfF1GNXdyh7oOSJLXbI4LBRofhfobue/lwtVMw41y2Tw0qsrMc/zRyM5
RMmCotLBB9OCa6T+koXO1O04qXeLknCVmQ8kH35V+QAdS4QipKM1d2+uTe4m/eTo64qu+u2JLQAA
AAAAAA==

--_003_AA7739BD285F4C94B503A2F2C945CC3Badmumuse_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=241;
	creation-date="Wed, 12 Jun 2013 06:40:41 GMT";
	modification-date="Wed, 12 Jun 2013 06:40:41 GMT"
Content-Transfer-Encoding: base64

PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBqb3Nl
IG1haWxpbmcgbGlzdA0KPiBqb3NlQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vam9zZQ0KDQotLSBSb2xhbmQNCiJFZHVjYXRpb24gaXMgdGhlIHBhdGgg
ZnJvbSBjb2NreSBpZ25vcmFuY2UgdG8gbWlzZXJhYmxlIHVuY2VydGFpbnR5LpQgLSBNYXJrIFR3
YWluDQoNCg0KDQoNCg==

--_003_AA7739BD285F4C94B503A2F2C945CC3Badmumuse_--

From jricher@mitre.org  Wed Jun 12 06:46:53 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E152D21F9B42 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 06:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.491
X-Spam-Level: 
X-Spam-Status: No, score=-6.491 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id viYFzdwFWmE6 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 06:46:48 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF9221F9B64 for <jose@ietf.org>; Wed, 12 Jun 2013 06:46:47 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 30A4B1F07CF; Wed, 12 Jun 2013 09:46:46 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 1DC0E1F0786; Wed, 12 Jun 2013 09:46:46 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 12 Jun 2013 09:46:45 -0400
Message-ID: <51B87B8E.5040608@mitre.org>
Date: Wed, 12 Jun 2013 09:45:50 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Roland Hedberg <roland.hedberg@adm.umu.se>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <CAHBU6isGzV1ZM1xczwK3v-rcusDwv6LHkag3KwX2QH+UFWGzpQ@mail.gmail.com> <637787CD-63D9-4FCC-8DFE-AF0692C262B3@ve7jtb.com> <AA7739BD-285F-4C94-B503-A2F2C945CC3B@adm.umu.se>
In-Reply-To: <AA7739BD-285F-4C94-B503-A2F2C945CC3B@adm.umu.se>
Content-Type: multipart/alternative; boundary="------------020802090405020007050403"
X-Originating-IP: [129.83.31.56]
Cc: Richard Barnes <rlb@ipv.sx>, Tim Bray <tbray@textuality.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, jose <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "draft-barnes-jose-use-cases@tools.ietf.org" <draft-barnes-jose-use-cases@tools.ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 13:46:54 -0000

--------------020802090405020007050403
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

I agree as well -- one of the best things about how the JWS/JWE systems 
work is that they're very simple and deterministic. With *zero* 
normalization (not even space folding), and all operations on a 
well-known encoding that doesn't get parsed and transformed in transit, 
you've got something that's not only easy to develop, it's easy to get 
*right*, and to get right every time.

Adding "a couple dozen lines of code" and breaking every single deployed 
instance isn't going to make things more secure or scalable -- it's 
going to make JOSE be ignored by the developers of the world. We have 
empirical proof that things work well the way that they're currently 
specified, I say cut it, ship it, call it a day.

  -- Justin

On 06/12/2013 02:41 AM, Roland Hedberg wrote:
> I'm completely behind John on this.
> Also, being one that has a JWT library implementation I can support Tim in that this is a breaking change.
> A change that I'm definitely against.
>
> 12 jun 2013 kl. 08:16 skrev John Bradley <ve7jtb@ve7jtb.com>:
>
>> Changing what the integrity is calculated over is about a big breaking change.
>>
>> I have personally considered alternate encodings for constrained environments (internet of things) however the format we have now has the advantage that it is hard for developers to get wrong, unlike xmldsig.
>>
>> Jim made a good point that you have to encode the length of the parts or have a separator that cannot appear in the parts.
>>
>> I expect that escaping every "." in the JSON is not going to work very well.
>>
>> We know what we have works.  It is possible to have long debates over things that won't work.
>>
>> The integrity has always been calculated this way,  It is not new.
>>
>> John B.
>>
>>
>> On 2013-06-12, at 6:20 AM, Tim Bray <tbray@textuality.com> wrote:
>>
>>> I haven't been following this closely, but someone who uses JWTs (there are a lot of them out there) asked me "Wouldn't this break all the existing JWT libraries and software deployed in production?"  I'm not 100% sure, but it looks to me like the answer is yes.  Since i observe empirically that JWTs work very well in production for federated login and many other applications, and offer a level of security that is acceptable to some of the most paranoid security organizations in the world, I think this proposal is not remotely close to being cost-effective.
>>>
>>> Forgive me if I'm wrong and this wouldn't actually break JWTs.  -T
>>>
>>>
>>> On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <trac+jose@trac.tools.ietf.org> wrote:
>>> #23: Make crypto independent of binary encoding (base64)
>>>
>>>   The cryptographic operations that JOSE performs should not depend on the
>>>   transfer encoding used for binary components.  The operations should work
>>>   directly on the encoded byte strings, not on the encoded form.
>>>
>>>   This is already true for content, IV, ciphertext, encrypted key, and
>>>   authentication tag.  The only thing that needs fixing is the protected
>>>   header value.  That's a little tricky, since the protected header value is
>>>   JSON, which doesn't have a standard encoding.  But it's not that onerous
>>>   just to convert it to UTF-8 -- in fact, senders are already required to
>>>   convert the protected header to UTF-8.
>>>
>>>   So the only change is to require recipients to convert the protected
>>>   header to UTF-8 before using it.   This can be accomplished with two minor
>>>   changes:
>>>
>>>   <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>>>   signature-11#section-5.2>
>>>   OLD: "The resulting JWS Protected Header MUST be a completely valid JSON
>>>   object conforming to RFC 4627 [RFC4627]."
>>>   NEW: "The resulting JWS Protected Header MUST be a completely valid JSON
>>>   object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>>>   valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>>>
>>>   <http://tools.ietf.org/html/draft-ietf-jose-json-web-
>>>   encryption-11#section-5.2>
>>>   OLD: "The resulting JWE Protected Header MUST be a completely valid JSON
>>>   object conforming to RFC 4627 [RFC4627]."
>>>   NEW: "The resulting JWE Protected Header MUST be a completely valid JSON
>>>   object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
>>>   valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."
>>>
>>> --
>>> -------------------------------------+-------------------------------------
>>>   Reporter:  rlb@ipv.sx               |      Owner:  draft-barnes-jose-use-
>>>       Type:  defect                   |  cases@tools.ietf.org
>>>   Priority:  major                    |     Status:  new
>>> Component:  draft-barnes-jose-use-   |  Milestone:
>>>    cases                              |    Version:
>>>   Severity:  -                        |   Keywords:
>>> -------------------------------------+-------------------------------------
>>>
>>> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23>
>>> jose <http://tools.ietf.org/jose/>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose


--------------020802090405020007050403
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I agree as well -- one of the best things about how the JWS/JWE
    systems work is that they're very simple and deterministic. With
    *zero* normalization (not even space folding), and all operations on
    a well-known encoding that doesn't get parsed and transformed in
    transit, you've got something that's not only easy to develop, it's
    easy to get *right*, and to get right every time. <br>
    <br>
    Adding "a couple dozen lines of code" and breaking every single
    deployed instance isn't going to make things more secure or scalable
    -- it's going to make JOSE be ignored by the developers of the
    world. We have empirical proof that things work well the way that
    they're currently specified, I say cut it, ship it, call it a day.<br>
    <br>
    &nbsp;-- Justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/12/2013 02:41 AM, Roland Hedberg
      wrote:<br>
    </div>
    <blockquote
      cite="mid:AA7739BD-285F-4C94-B503-A2F2C945CC3B@adm.umu.se"
      type="cite">
      <pre wrap="">I'm completely behind John on this.
Also, being one that has a JWT library implementation I can support Tim in that this is a breaking change.
A change that I'm definitely against.

12 jun 2013 kl. 08:16 skrev John Bradley <a class="moz-txt-link-rfc2396E" href="mailto:ve7jtb@ve7jtb.com">&lt;ve7jtb@ve7jtb.com&gt;</a>:

</pre>
      <blockquote type="cite">
        <pre wrap="">Changing what the integrity is calculated over is about a big breaking change.

I have personally considered alternate encodings for constrained environments (internet of things) however the format we have now has the advantage that it is hard for developers to get wrong, unlike xmldsig.

Jim made a good point that you have to encode the length of the parts or have a separator that cannot appear in the parts. 

I expect that escaping every "." in the JSON is not going to work very well. 

We know what we have works.  It is possible to have long debates over things that won't work.

The integrity has always been calculated this way,  It is not new.

John B.


On 2013-06-12, at 6:20 AM, Tim Bray <a class="moz-txt-link-rfc2396E" href="mailto:tbray@textuality.com">&lt;tbray@textuality.com&gt;</a> wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">I haven&#8217;t been following this closely, but someone who uses JWTs (there are a lot of them out there) asked me &#8220;Wouldn&#8217;t this break all the existing JWT libraries and software deployed in production?&#8221;  I&#8217;m not 100% sure, but it looks to me like the answer is yes.  Since i observe empirically that JWTs work very well in production for federated login and many other applications, and offer a level of security that is acceptable to some of the most paranoid security organizations in the world, I think this proposal is not remotely close to being cost-effective.

Forgive me if I&#8217;m wrong and this wouldn&#8217;t actually break JWTs.  -T


On Tue, Jun 11, 2013 at 10:58 AM, jose issue tracker <a class="moz-txt-link-rfc2396E" href="mailto:trac+jose@trac.tools.ietf.org">&lt;trac+jose@trac.tools.ietf.org&gt;</a> wrote:
#23: Make crypto independent of binary encoding (base64)

 The cryptographic operations that JOSE performs should not depend on the
 transfer encoding used for binary components.  The operations should work
 directly on the encoded byte strings, not on the encoded form.

 This is already true for content, IV, ciphertext, encrypted key, and
 authentication tag.  The only thing that needs fixing is the protected
 header value.  That's a little tricky, since the protected header value is
 JSON, which doesn't have a standard encoding.  But it's not that onerous
 just to convert it to UTF-8 -- in fact, senders are already required to
 convert the protected header to UTF-8.

 So the only change is to require recipients to convert the protected
 header to UTF-8 before using it.   This can be accomplished with two minor
 changes:

 <a class="moz-txt-link-rfc2396E" href="http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#section-5.2">&lt;http://tools.ietf.org/html/draft-ietf-jose-json-web-
 signature-11#section-5.2&gt;</a>
 OLD: "The resulting JWS Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627]."
 NEW: "The resulting JWS Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
 valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."

 <a class="moz-txt-link-rfc2396E" href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-5.2">&lt;http://tools.ietf.org/html/draft-ietf-jose-json-web-
 encryption-11#section-5.2&gt;</a>
 OLD: "The resulting JWE Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627]."
 NEW: "The resulting JWE Protected Header MUST be a completely valid JSON
 object conforming to RFC 4627 [RFC4627].  If the JWE Protected Header is
 valid, convert it to the UTF-8 encoding.  Otherwise, reject the JWE."

--
-------------------------------------+-------------------------------------
 Reporter:  <a class="moz-txt-link-abbreviated" href="mailto:rlb@ipv.sx">rlb@ipv.sx</a>               |      Owner:  draft-barnes-jose-use-
     Type:  defect                   |  <a class="moz-txt-link-abbreviated" href="mailto:cases@tools.ietf.org">cases@tools.ietf.org</a>
 Priority:  major                    |     Status:  new
Component:  draft-barnes-jose-use-   |  Milestone:
  cases                              |    Version:
 Severity:  -                        |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <a class="moz-txt-link-rfc2396E" href="http://trac.tools.ietf.org/wg/jose/trac/ticket/23">&lt;http://trac.tools.ietf.org/wg/jose/trac/ticket/23&gt;</a>
jose <a class="moz-txt-link-rfc2396E" href="http://tools.ietf.org/jose/">&lt;http://tools.ietf.org/jose/&gt;</a>

_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>

_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
        </blockquote>
        <pre wrap="">
</pre>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------020802090405020007050403--

From ludwig@sics.se  Wed Jun 12 07:04:39 2013
Return-Path: <ludwig@sics.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B30521F9AB1 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 07:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fISXDvZEz65Z for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 07:04:34 -0700 (PDT)
Received: from fsmsg2.sics.se (fsmsg2.sics.se [IPv6:2001:6b0:3a:1:250:56ff:fea9:52ad]) by ietfa.amsl.com (Postfix) with ESMTP id A136821F98AD for <jose@ietf.org>; Wed, 12 Jun 2013 07:04:33 -0700 (PDT)
Received: from pps.filterd (fsmsg2 [127.0.0.1]) by fsmsg2.sics.se (8.14.5/8.14.5) with SMTP id r5CE1UJM023748; Wed, 12 Jun 2013 16:04:32 +0200
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by fsmsg2.sics.se with ESMTP id 1cwcj134aw-1; Wed, 12 Jun 2013 16:04:31 +0200
Received: from [192.168.0.103] (unknown [85.235.11.178]) (Authenticated sender: ludwig@sics.se) by letter.sics.se (Postfix) with ESMTPSA id 00AF7400E2; Wed, 12 Jun 2013 16:04:31 +0200 (CEST)
Message-ID: <1371045871.5715.18.camel@ubuntu.ubuntu-domain>
From: Ludwig Seitz <ludwig@sics.se>
To: jose@ietf.org
Date: Wed, 12 Jun 2013 16:04:31 +0200
In-Reply-To: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
Organization: SICS AB
Content-Type: multipart/signed; micalg="sha256"; protocol="application/x-pkcs7-signature"; boundary="=-o/HAobKBKP5f9OZWTyW7"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Mime-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-06-12_03:2013-06-12, 2013-06-12, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=15 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1211240000 definitions=main-1306120091
Cc: "=?ISO-8859-1?Q?G=F6ran?= Selander \(KI/EAB\)" <goran.selander@ericsson.com>
Subject: Re: [jose] Working Group Last Call - draft-ietf-jose-use-cases
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 14:04:39 -0000

--=-o/HAobKBKP5f9OZWTyW7
Content-Type: multipart/mixed; boundary="=-FLN8+no4WQ99f/YcxA06"


--=-FLN8+no4WQ99f/YcxA06
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

as suggested by Jim Schad and Mike Jones, I've written up a proposal for
an additional small devices (renamed to constrained devices) use case.

I'm grateful for any comments and suggestion you may have.


Regards,

Ludwig Seitz


--=20
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2=20
Scheelev=C3=A4gen 17=20
SE-223 70 Lund

Phone +46(0)70-349 92 51
http://www.sics.se

--=-FLN8+no4WQ99f/YcxA06
Content-Disposition: attachment; filename="JoseUseCase5.8.txt"
Content-Transfer-Encoding: base64
Content-Type: text/plain; name="JoseUseCase5.8.txt"; charset="UTF-8"

NS44LiAgQ29uc3RyYWluZWQgRGV2aWNlcw0KICAgVGhpcyBzZWN0aW9uIGRlc2NyaWJlcyB1c2Ug
Y2FzZXMgZm9yIGNvbnN0cmFpbmVkIGRldmljZXMgYXMgZGVmaW5lZCANCiAgIGluIFtJLUQuaWV0
Zi1sd2lnLXRlcm1pbm9sb2d5XS4gVHlwaWNhbCBpc3N1ZXMgd2l0aCB0aGlzIHR5cGUgb2YgDQog
ICBkZXZpY2VzIGFyZSBsaW1pdGVkIG1lbW9yeSwgbGltaXRlZCBwb3dlciBzdXBwbHksIGxvdyBw
cm9jZXNzaW5nDQogICBwb3dlciwgYW5kIHNldmVyZSBtZXNzYWdlIHNpemUgbGltaXRhdGlvbnMg
Zm9yIHRoZSBjb21tdW5pY2F0aW9uDQogICBwcm90b2NvbHMuDQoNCjUuOC4xIE1BQyBiYXNlZCBv
biBFQ0RILWRlcml2ZWQga2V5DQoNCiAgIEEgc21hbGwsIGxvdyBwb3dlciBkZXZpY2UgbWFrZXIg
aGFzIGRlY2lkZWQgb24gdXNpbmcgdGhlIG91dHB1dCBvZg0KICAgdGhlIEpPU0Ugd29ya2luZyBn
cm91cCBhcyB0aGVpciBlbmNyeXB0aW9uIGFuZCBhdXRoZW50aWNhdGlvbg0KICAgZnJhbWV3b3Jr
LiAgVGhlIGRldmljZSBtYWtlciBoYXMgYSBsaW1pdGVkIGF2YWlsYWJpbGl0eSBvZiBib3RoIHJl
YWwNCiAgIGVzdGF0ZSBmb3IgZ2F0ZXMgYW5kIHBvd2VyLiAgRm9yIHRoaXMgcmVhc29uIHRoZXJl
IGFyZSBhIG51bWJlciBvZg0KICAgc2hvcnQgY3V0cyBhbmQgZGVzaWduIGRlY2lzaW9ucyB0aGF0
IGhhdmUgYmVlbiBtYWRlIGluIG9yZGVyIHRvDQogICBtaW5pbWl6ZSB0aGVzZSBuZWVkcy4NCg0K
ICAgVGhlIGRlc2lnbiB0ZWFtIGhhcyBkZXRlcm1pbmVkIHRoYXQgdGhlIHVzZSBvZiBtZXNzYWdl
IGF1dGhlbnRpY2F0aW9uDQogICBjb2RlcyAoTUFDKSBpcyBnb2luZyB0byBiZSBzdWZmaWNpZW50
IHRvIHByb3ZpZGUgdGhlIG5lY2Vzc2FyeQ0KICAgYXV0aGVudGljYXRpb24uICBIb3dldmVyLCBh
bHRob3VnaCBhIE1BQyBpcyBnb2luZyB0byBiZSB1c2VkLCB0aGV5IGRvDQogICBub3Qgd2FudCB0
byB1c2UgYSBzaW5nbGUgbG9uZyB0ZXJtIHNoYXJlZCBzZWNyZXQuICBJbnN0ZWFkIHRoZXkgaGF2
ZQ0KICAgYWRvcHRlZCB0aGUgZm9sbG93aW5nIHByb3Bvc2FsIGZvciBjb21wdXRpbmcgYSBzaGFy
ZWQgc2VjcmV0IHRoYXQgY2FuDQogICBiZSB2YWxpZGF0ZWQ6DQoNCiAgIG8gIEFuIEVsbGlwdGlj
LUN1cnZlIERpZmZpZS1IZWxsbWFuIChFQ0RIKSBrZXkgaXMgZ2VuZXJhdGVkIGZvciB0aGUNCiAg
ICAgIGRldmljZSBhdCB0aGUgdGltZSBvZiBtYW51ZmFjdHVyaW5nLiAgKE9yIGFzIHBhcnQgb2Yg
dGhlDQogICAgICBjb25maWd1cmF0aW9uIHByb2Nlc3MgZHVyaW5nIGluc3RhbGxhdGlvbi4pDQoN
CiAgIG8gIEFuIEVDREggcHVibGljIGtleSBmb3IgdGhlIGNvbnRyb2xsZXIgaXMgY29uZmlndXJl
ZCBhdCB0aGUgdGltZSBvZg0KICAgICAgY29uZmlndXJhdGlvbi4NCg0KICAgbyAgVGhlIGNvbmZp
Z3VyYXRpb24gc3lzdGVtIHBlcmZvcm1zIHRoZSBleHBvbmVudGlhdGlvbiBhbmQNCiAgICAgIGNv
bmZpZ3VyZXMgdGhlIGRldmljZSB3aXRoIHRoZSByZXN1bHRpbmcgc2hhcmVkIHNlY3JldC4gIFRo
aXMNCiAgICAgIHByb2Nlc3MgZWxpbWluYXRlcyB0aGUgbmVlZCBmb3IgdGhlIGRldmljZSB0byBi
ZSBhYmxlIHRvIHBlcmZvcm0NCiAgICAgIHRoZSByZXF1aXJlZCBleHBvbmVudGlhdGlvbiBwcm9j
ZXNzaW5nLiAgVGhlIHNlY3VyaXR5IHJlcXVpcmVtZW50cw0KICAgICAgb24gcHJvdGVjdGluZyB0
aGlzIGNvbXB1dGVkIHNoYXJlZCBzZWNyZXQgYXJlIHRoZSBzYW1lIGFzIHRoZQ0KICAgICAgcmVx
dWlyZW1lbnRzIG9uIHByb3RlY3RpbmcgdGhlIHByaXZhdGUgRUNESCBrZXkuDQoNCiAgIG8gIEEg
Y291bnRlciBhbmQgYW4gaW5jcmVtZW50IHZhbHVlIGFyZSBjb25maWd1cmVkIG9udG8gdGhlIGRl
dmljZS4NCg0KICAgbyAgV2hlbiBhIG1lc3NhZ2UgaXMgdG8gYmUgc2VudCBieSB0aGUgZGV2aWNl
LCB0aGUgY291bnRlciBpcw0KICAgICAgaW5jcmVtZW50ZWQgYW5kIGEgbmV3IE1BQyBrZXkgaXMg
Y29tcHV0ZWQgZnJvbSB0aGUgRUNESCBzZWNyZXQgYW5kDQogICAgICB0aGUgY291bnRlciB2YWx1
ZS4gIEEgY3VzdG9tIEtleSBEZXJpdmF0aW9uIEZ1bmN0aW9uIChLREYpDQogICAgICBmdW5jdGlv
biBpcyB1c2VkIHdoZW4gaXMgYmFzZWQgb24gdGhlIEFFUy1DQkMgaXMgdXNlZCB0byBkZXJpdmUN
CiAgICAgIHRoZSByZXF1aXJlZCBNQUMga2V5LiAgVGhlIE1BQyBrZXkgaXMgdGhlbiB1c2VkIHRv
IGNvbXB1dGUgdGhlIE1BQw0KICAgICAgdmFsdWUgZm9yIHRoZSBtZXNzYWdlLg0KDQogICBJbiBh
IHNpbWlsYXIgbWFubmVyIHRoZSBLREYgZnVuY3Rpb24gY2FuIHVzZWQgdG8gY29tcHV0ZSBhbiBB
RUFEDQogICBhbGdvcml0aG0ga2V5IHdoZW4gdGhlIHN5c3RlbSBuZWVkcyB0byBwcm92aWRlIGNv
bmZpZGVudGlhbGx5IGZvciB0aGUNCiAgIG1lc3NhZ2UuICBUaGUgY29udHJvbGxlciwgYmVpbmcg
YSBsYXJnZXIgZGV2aWNlIHdpbGwgcGVyZm9ybSB0aGUNCiAgIGV4cG9uZW50aWF0aW9uIHN0ZXAg
YW5kIHVzZSBhIHJhbmRvbSBudW1iZXIgZ2VuZXJhdG9yIHRvIGdlbmVyYXRlIHRoZQ0KICAgc2Vu
ZGVyIG5vbmNlIHZhbHVlLg0KDQo1LjguMiBPYmplY3Qgc2VjdXJpdHkgZm9yIENvQVANCg0KICAg
VGhpcyB1c2UgY2FzZSBkZWFscyB3aXRoIGNvbnN0cmFpbmVkIGRldmljZXMgb2YgY2xhc3MgQzAv
QzEgKHNlZQ0KICAgW0ktRC5pZXRmLWx3aWctdGVybWlub2xvZ3ldKS4gVGhlc2UgZGV2aWNlcyBj
b21tdW5pY2F0ZSB1c2luZyBSRVNUZnVsDQogICByZXF1ZXN0cyBhbmQgcmVzcG9uc2VzIHRyYW5z
ZmVycmVkIHVzaW5nIHRoZSBDb0FQIHByb3RvY29sIA0KICAgW0ktRC5pZXRmLWNvcmUtY29hcF0u
IFRvIHNpbXBsaWZ5IG1hdHRlcnMsIGFsbCBjb21tdW5pY2F0aW9uIGlzDQogICBhc3N1bWVkIHRv
IGJlIHVuaWNhc3QsIGkuZS4gdGhlc2Ugc2VjdXJpdHkgbWVhc3VyZXMgZG9uJ3QgY292ZXIgDQog
ICBtdWx0aWNhc3Qgb3IgYnJvYWRjYXN0Lg0KDQogICBJbiB0aGlzIHR5cGUgb2Ygc2V0dGluZyBp
dCBtYXkgYmUgdG9vIGNvc3RseSB0byB1c2Ugc2Vzc2lvbiANCiAgIGJhc2VkIHNlY3VyaXR5IChl
LmcuIHRvIHJ1biBhIDQgcGFzcyBhdXRoZW50aWNhdGlvbiBwcm90b2NvbCkgc2luY2UNCiAgIHJl
Y2VpdmluZyBhbmQgaW4gcGFydGljdWxhciBzZW5kaW5nIGNvbnN1bWVzIGEgbG90IG9mIHBvd2Vy
LCBpbg0KICAgcGFydGljdWxhciBmb3Igd2lyZWxlc3MgZGV2aWNlcy4gVGhlcmVmb3JlIHRvIGp1
c3Qgc2VjdXJlIHRoZSBDb0FQIA0KICAgcGF5bG9hZCBieSByZXBsYWNpbmcgYSBwbGFpbiB0ZXh0
IHBheWxvYWQgb2YgYSByZXF1ZXN0IG9yIHJlc3BvbnNlDQogICB3aXRoIGEgSldFIG9iamVjdCBp
cyBhbiBpbXBvcnRhbnQgYWx0ZXJuYXRpdmUgc29sdXRpb24sIHdoaWNoDQogICBhbGxvd3MgYSB0
cmFkZS1vZmYgYmV0d2VlbiBwcm90ZWN0aW9uICh0aGUgQ29BUCBoZWFkZXJzIGFyZSBub3QNCiAg
IHByb3RlY3RlZCkgYW5kIHBlcmZvcm1hbmNlLg0KDQogICBJbiBhIHNpbXBsZSBzZXR0aW5nLCBj
b25zaWRlciB0aGUgcGF5bG9hZCBvZiBhIENvQVAgR0VUIHJlc3BvbnNlIGZyb20NCiAgIGEgc2Vu
c29yIHR5cGUgZGV2aWNlLiBUaGUgaW5mb3JtYXRpb24gaW4gYSBzZW5zb3IgcmVhZGluZyBtYXkg
YmUgDQogICBwcml2YWN5IG9yIGJ1c2luZXNzIHNlbnNpdGl2ZSBhbmQgbmVlZHMgYm90aCBpbnRl
Z3JpdHkgcHJvdGVjdGlvbiBhbmQNCiAgIGVuY3J5cHRpb24uDQoNCiAgIEhvd2V2ZXIgc29tZSBz
ZW5zb3IgcmVhZGluZ3MgYXJlIHZlcnkgc2hvcnQsIHNheSBhIGZldyBieXRlcywgYW5kIGluDQog
ICB0aGlzIGNhc2UgZGVmYXVsdCBlbmNyeXB0aW9uIGFuZCBpbnRlZ3JpdHkgcHJvdGVjdGlvbiBh
bGdvcml0aG1zIA0KICAgKHN1Y2ggYXMgMTI4IGJpdCBBRVMgd2l0aCBITUFDX1NIQTI1NikgbWF5
IGNhdXNlIGEgZHJhbWF0aWMgbWVzc2FnZQ0KICAgZXhwYW5zaW9uIG9mIHRoZSBwYXlsb2FkLCBl
dmVuIGRpc3JlZ2FyZGluZyBKV0UgaGVhZGVycy4NCg0KICAgQWxzbyB0aGUgdmFsdWUgb2YgY2Vy
dGFpbiBzZW5zb3IgcmVhZGluZ3MgbWF5IGRlY2xpbmUgcmFwaWRseSwgZS5nLg0KICAgdHJhZmZp
YyBvciBlbnZpcm9ubWVudGFsIG1lYXN1cmVtZW50cywgc28gaXQgbXVzdCBiZSBwb3NzaWJsZSB0
byANCiAgIHJlZHVjZSB0aGUgc2VjdXJpdHkgb3ZlcmhlYWQuDQoNCiAgIFRoaXMgbGVhZHMgdG8g
dGhlIGZvbGxvd2luZyByZXF1aXJlbWVudHMgd2hpY2ggY291bGQgYmUgY292ZXJlZCBieQ0KICAg
c3BlY2lmaWMgSldFL0pXUyBwcm9maWxlczoNCiAgIA0KICAgbyBUaGUgc2l6ZSBvZiB0aGUgc2Vj
dXJlIG9iamVjdCBzaGFsbCBiZSBhcyB0aW55IGFzIHBvc3NpYmxlLg0KICAgICBSZWNlaXZpbmcg
YW4gb2JqZWN0IG1heSBjb3N0IG9yZGVycyBvZiBtYWduaXR1ZGUgbW9yZSBpbiB0ZXJtcyBvZg0K
ICAgICBwb3dlciB0aGFuIHBlcmZvcm1pbmcgc2F5IHB1YmxpYyBrZXkgY3J5cHRvZ3JhcGh5IG9u
IHRoZSBvYmplY3QsIA0KICAgICBpbiBwYXJ0aWN1bGFyIGluIGEgd2lyZWxlc3Mgc2V0dGluZy4N
Cg0KICAgbyBJbnRlZ3JpdHkgcHJvdGVjdGlvbiANCiAgICAgVGhlIG9iamVjdCBzaGFsbCBiZSBh
YmxlIHRvIHN1cHBvcnQgaW50ZWdyaXR5IHByb3RlY3Rpb24sIGkuZS4gaGF2ZQ0KICAgICBhIGZp
ZWxkIGNvbnRhaW5pbmcgYSBkaWdpdGFsIHNpZ25hdHVyZSwgYm90aCBwdWJsaWMga2V5IHNpZ25h
dHVyZXMgDQogICAgIGFuZCBrZXllZCBtZXNzYWdlIGF1dGhlbnRpY2F0aW9uIGNvZGVzIHNoYWxs
IGJlIHN1cHBvcnRlZC4NCg0KICAgbyBFbmNyeXB0aW9uIA0KICAgICBUaGUgb2JqZWN0IHNoYWxs
IGJlIGFibGUgdG8gc3VwcG9ydCBlbmNyeXB0aW9uIGFzIGFuIG9wdGlvbmFsDQogICAgIGFkZGl0
aW9uIHRvIGludGVncml0eSBwcm90ZWN0aW9uLiBJdCBzaGFsbCBiZSBwb3NzaWJsZSB0byBleGNs
dWRlDQogICAgIGNlcnRhaW4gZmllbGRzIGZyb20gZW5jcnlwdGlvbiB3aGljaCBhcmUgbmVlZGVk
IGJlZm9yZSB2ZXJpZnlpbmcgDQogICAgIGludGVncml0eSBvciBkZWNyeXB0aW5nIHRoZSBvYmpl
Y3QuDQoNCiAgIG8gQ2lwaGVyIHN1aXRlcw0KICAgICBJdCBzaG91bGQgYmUgcG9zc2libGUgdG8g
c3VwcG9ydCBhIHZhcmlldHkgb2YgY2lwaGVyIHN1aXRlcyB0bw0KICAgICBzdXBwb3J0IHRoZSBj
b25zdHJhaW5lZCBkZXZpY2VzIHVzZSBjYXNlcy4gRm9yIGV4YW1wbGU6DQogICAgICAtIEJsb2Nr
IGNpcGhlcnMgd2l0aCBibG9jayBzaXplcyBvZiBlLmcuIDk2IGJpdHMsIGluIGFkZGl0aW9uIHRv
DQogICAgICAgIHRoZSBzdGFuZGFyZCAxMjggYml0cw0KICAgICAgLSBNb2RlcyBvZiBvcGVyYXRp
b24gZm9yIGJsb2NrIGNpaHBlcnMgdGhhdCBkbyBub3QgZXhwYW5kIHRoZSANCiAgICAgICAgbWVz
c2FnZSBzaXplIHRvIGJsb2NrIHNpemUsIGUuZy4gR0NNLg0KICAgICAgLSBDaXBoZXIgc3VpdGVz
IHRoYXQgc3VwcG9ydCBjb21iaW5lZCBlbmNyeXB0aW9uIGFuZCBNQUMgDQogICAgICAgIGNhbGN1
bGF0aW9uIChpLmUuIEFFQUQgbW9kZXMgZm9yIGJsb2NrIGNpcGhlcnMpLm==


--=-FLN8+no4WQ99f/YcxA06--

--=-o/HAobKBKP5f9OZWTyW7
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEnAw
ggYYMIIFAKADAgECAgMFtYswDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQTAeFw0xMzAxMTUwMjA1MDZaFw0xNDAxMTUxNDM3NDhaMDgxFzAVBgNVBAMMDmx1ZHdpZ0Bz
aWNzLnNlMR0wGwYJKoZIhvcNAQkBFg5sdWR3aWdAc2ljcy5zZTCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBAKpuRavr2swCQsYS7KxOsmeBXI39thxAjIYaB0AFVjLpOtVJxQMYoip7Bm9o
ka8PXxQ9mWT/lVSoqI7jGjc5Z8q1C4fOFMCYZpJugG9qJS0OMV2ajQ7xXu3YzLTDIKg/BK39+Vri
vJq0Y6hz1/4pgxMOFG+l7y+fq54QSkKMwpuRaCBznKJeRxGwDvheF2QN6YEBclFqVhpciDGd52vX
5AgbKbqVmevMrcrcYAdKaKm6iTEmbYHum5D/4GaOnnZ2wMnY5EpKhxxm6SszCVSNdk8iZSUze9GY
PzheBDIHMDdLZib6zaoR96F5ZCpE1pPeKIz/DCd3kL+nXpe5gdbSXLsCAwEAAaOCAtQwggLQMAkG
A1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQUwDv6gyc7uSHK/QBVIZiN86hjKW4wHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4
UYIwGQYDVR0RBBIwEIEObHVkd2lnQHNpY3Muc2UwggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQB
gbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBk
ZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIB
ARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEg
VmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFu
Y2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVs
eWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZo
dHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYD
VR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBCwUAA4IBAQA4bagj
yL3PLei2tbMELKOVOxRdyLObcVq0Fj83LbSTMj6NS83TU/4xxChfd5zqoipudDSEpgxZAUsSjk02
DxSeLYYBXE2X/iue7nL8S/3PjC49z5ZgjDZrXIgmvIMaZXWM+GqG+wk9NikGb1/shlJjk3R5KC3f
RWsUatHouNxAMYxiLFO75YmgKCgkjtKUbHbUqzmDVd30nWQesXfCgYwCbAvD/0NgX3jE+fnyT71+
aX4/IfqshpCQj8dkR4ZH+bUiK5zgKGJL61GRZNSScR/r9Sq19kEQrt38ey/Q90tUDUgg93d5w3DN
rF3bRoOvyspwbcN9TuGKkFoFPV0KfjaGMIIGGDCCBQCgAwIBAgIDBbWLMA0GCSqGSIb3DQEBCwUA
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl
IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ
cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwMTE1MDIwNTA2WhcNMTQwMTE1MTQz
NzQ4WjA4MRcwFQYDVQQDDA5sdWR3aWdAc2ljcy5zZTEdMBsGCSqGSIb3DQEJARYObHVkd2lnQHNp
Y3Muc2UwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCqbkWr69rMAkLGEuysTrJngVyN
/bYcQIyGGgdABVYy6TrVScUDGKIqewZvaJGvD18UPZlk/5VUqKiO4xo3OWfKtQuHzhTAmGaSboBv
aiUtDjFdmo0O8V7t2My0wyCoPwSt/fla4ryatGOoc9f+KYMTDhRvpe8vn6ueEEpCjMKbkWggc5yi
XkcRsA74XhdkDemBAXJRalYaXIgxnedr1+QIGym6lZnrzK3K3GAHSmipuokxJm2B7puQ/+Bmjp52
dsDJ2ORKSoccZukrMwlUjXZPImUlM3vRmD84XgQyBzA3S2Ym+s2qEfeheWQqRNaT3iiM/wwnd5C/
p16XuYHW0ly7AgMBAAGjggLUMIIC0DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAU
BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFMA7+oMnO7khyv0AVSGYjfOoYyluMB8GA1Ud
IwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGCMBkGA1UdEQQSMBCBDmx1ZHdpZ0BzaWNzLnNlMIIB
TAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQg
YWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBT
dGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3Nl
IGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUF
BwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3Mx
L2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3Vi
LmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
LzANBgkqhkiG9w0BAQsFAAOCAQEAOG2oI8i9zy3otrWzBCyjlTsUXcizm3FatBY/Ny20kzI+jUvN
01P+McQoX3ec6qIqbnQ0hKYMWQFLEo5NNg8Uni2GAVxNl/4rnu5y/Ev9z4wuPc+WYIw2a1yIJryD
GmV1jPhqhvsJPTYpBm9f7IZSY5N0eSgt30VrFGrR6LjcQDGMYixTu+WJoCgoJI7SlGx21Ks5g1Xd
9J1kHrF3woGMAmwLw/9DYF94xPn58k+9fml+PyH6rIaQkI/HZEeGR/m1Iiuc4ChiS+tRkWTUknEf
6/UqtfZBEK7d/Hsv0PdLVA1IIPd3ecNwzaxd20aDr8rKcG3DfU7hipBaBT1dCn42hjCCBjQwggQc
oAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNV
BAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3
MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENv
bSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xC
GhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P
3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2Ub
FqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2
JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGp
MA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6W
NU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3Rh
cnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhj
jF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4
n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkU
CTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6h
xHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5X
MEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b
1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLp
XDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/p
Ny8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOg
SF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEw
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCWCGSAFlAwQCAQUAoIIBuzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MTIxNDA0MzFaMC8G
CSqGSIb3DQEJBDEiBCDyxjO6U4fM2kp4HE7iC9O+P9t7j1d/c8OE7Vl0+5GJeTCBpQYJKwYBBAGC
NxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwW1izCBpwYLKoZIhvcNAQkQ
AgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCSqGSIb3DQEBAQUA
BIIBAIpZZ65GsWDaYI2xHsiN5sEAJNwz3TxJOqRKMksgyOQpmSzZ6/8SrNhXQWtq0fT1cxJskl0F
4RB/V9HZrCu0I/9KcPYhrojnem0uSLwE0vNIX24ZmmA8KcHipiMmHLGIsgtAyhVy8CuAktfuU5v5
SuphMZ+PjrRyJExAsgSGpt1bzFzmqDgaRH8yYj6LraHNlg/VZ+D2A1slt/x5GPhLYePA1N2QKCuO
jnuIEJ2kwz7/9XsfqRDVLOEEhTHRynDQOi2q67UXG+Az5eyQRJyt7Q+udE9uVF8XazPfPdMPv4q1
0wcY4jR813EJrfDF11Es5bB8SnSK3etzjQy8FuP0ozAAAAAAAAA=


--=-o/HAobKBKP5f9OZWTyW7--


From mamille2@cisco.com  Wed Jun 12 07:28:18 2013
Return-Path: <mamille2@cisco.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E7C21F9B9B for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 07:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcopUyyQcX-O for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 07:28:13 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id ABB7421F9BAF for <jose@ietf.org>; Wed, 12 Jun 2013 07:28:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9205; q=dns/txt; s=iport; t=1371047284; x=1372256884; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=sK4+b1XJZJMNsvUCimtplQ/TZXLv2D5p6Dve1spMQpY=; b=lda9nGDyfutBrRLM/VvilgZBHWLUu+u5bpleODQ94WHxj/MemngJz/2Y bDdUXRbVhvAdJvx6W4p3bMyRDaunnNwjBUoGjFEeZZWxPMnoaGLh7IJit p+HR3Gk+gJ5Fsbv9lL9IlhPnqGUC9y1aE+H29fiqVY+Tv2m94rB1D/lM/ 0=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAN6EuFGtJV2Y/2dsb2JhbABagwkwSb5YgQEWdIIkAQEEAQEBawsQAgEIIiQCJQslAgQOBQgGiAAMugCOEQp3MQeCf2EDkAGBLIc8iniFIYMPgXE2
X-IronPort-AV: E=Sophos;i="4.87,852,1363132800";  d="p7s'?scan'208";a="218934585"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 12 Jun 2013 14:27:38 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r5CERcYP024853 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Jun 2013 14:27:38 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Wed, 12 Jun 2013 09:27:38 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: jose issue tracker <trac+jose@trac.tools.ietf.org>
Thread-Topic: [jose] #23: Make crypto independent of binary encoding (base64)
Thread-Index: AQHOZwAXKcNLuE7LHkStdGteSHNX/pkyd8qA
Date: Wed, 12 Jun 2013 14:27:37 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org>
In-Reply-To: <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.129.24.59]
Content-Type: multipart/signed; boundary="Apple-Mail=_20838759-A7A4-43A1-A8A8-1742E0DF34AA"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<rlb@ipv.sx>" <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 14:28:18 -0000

--Apple-Mail=_20838759-A7A4-43A1-A8A8-1742E0DF34AA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I did at first find it curious why the cryptographic operations were =
over the base64url-enccoded values, but I was also very focused on JWE, =
where I think the field separation problem is less of an issue (at least =
now).  For JWS, this would certainly cause problems without some manner =
of unambiguous field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be =
used as a separator between the encoded header and the payload.  I do =
find it interesting if JOSE could more easily and efficiently support =
other encodings.  However, I think that while this is an interesting =
thought experiment, it seems we're too far down the path to seriously =
consider it unless the current state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker =
<trac+jose@trac.tools.ietf.org> wrote:

> #23: Make crypto independent of binary encoding (base64)
>=20
>=20
> Comment (by michael.jones@microsoft.com):
>=20
> For both serializations, you already need the base64url encoded =
versions
> of the JWS Header and the JWS Payload to preserve them in =
transmission, so
> computing them isn't an extra burden.  In the JWS Compact =
Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that =
concatenation
> isn't an extra burden.  Given you already have that quantity, =
computing
> the signature over it is the easiest thing for developers to do, and =
it's
> been shown to work well in practice.  There's no compelling reason to =
make
> this change.
>=20
> Even for the JSON Serialization, the only "extra" step that's required =
to
> compute the signature is the concatenation with the period character - =
to
> prevent shifting of data from one field to the other, as described by =
Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at =
all -
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>=20
> Since there is no compelling reason to make this change, and since =
making
> it could enable the "shifting" problem identified by Jim, it should =
not be
> made.
>=20
> --=20
> =
-------------------------+------------------------------------------------=
-
> Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>     Type:  defect       |  encryption@tools.ietf.org
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> =
-------------------------+------------------------------------------------=
-
>=20
> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_20838759-A7A4-43A1-A8A8-1742E0DF34AA
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMezCCBjQw
ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX
DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK
75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC
+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD
z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr
/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc
fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG
XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt
UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R
HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv
sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq
+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT
zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq
Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1
9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPzCCBSeg
AwIBAgIDBoRIMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN
MTMwNDMwMjE1NDQyWhcNMTQwNTAyMDUzOTA0WjBbMRkwFwYDVQQNExBiN2F6NndOY0t0R3JtMEpF
MRswGQYDVQQDDBJtYW1pbGxlMkBjaXNjby5jb20xITAfBgkqhkiG9w0BCQEWEm1hbWlsbGUyQGNp
c2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJbKBMsG+9UFTx9uq/bhhXgu
vJvO8z7cwKaqqwZhVf5z/kHFyCNijtmTOE+YXjA8mWR4aoBwB5SvGypI/cJUofJ+AlBTC4g+RMx/
K0Ab4/jQqTQz9CDzMOB+Wm+rt8ZJ7A8ZzOJmNDAsf/VvB8l2A1SQz1UsAixgH16NTr8SlblAXEKk
4hwpCudUiNjjQokqJ0H686UBKVorcZSgXaza8XMqGtJF/8mNhR9GQYi7Xht1ky+9LFOrto2daZto
KJRwMeVusVdHUeKEQSu7jztw8HchH3KEb7Q+r5X+hhDZoddfKE8d5eyPuhiZdrzv7OlNZ0fSLdx7
3AE3nx9/R5YlXucCAwEAAaOCAtgwggLUMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQW
MBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUxGd+/qrdVudHrIKkw5xOMY7eaLUwHwYD
VR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWFtaWxsZTJAY2lzY28u
Y29tMIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9m
IHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBw
dXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYG
A1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4G
CCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy
dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAlDhXbGEI7lbqUcu5r2JHZaMsbRZda/99ZqODzWGX
0llou9jGccsAWDPPwRRe2+ROpXfH4cuJZElTcLDeZSp/qpXKhjYieFSX8+Ml9sKEj5UOSqQLyoLk
PtrIJV12Jk3nuG2Jc0UeEnGwK/aqtzy7+bfEVI0ziyVM2gChHh0RH74KyiwYWknbOTRIkZcz/ulE
DVFQp63uj6wfmDNvAUHBAdhKVqA1S/rfP1KcDZpf1NfvwXJibiqTRA6K1EOxTJOP41n/XdvHqHXL
RWL2xrOUI9/URANr/ok3OrsuZEMFnAAGefS1bWS/hFtUGVkHGiKEBbyDW7da2ULXbuC7umrQnzGC
A28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDAJBgUrDgMCGgUA
oIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MTIxNDI3
MzhaMCMGCSqGSIb3DQEJBDEWBBS/zBPrtJYeByiqDzk7+UpK4xzABzCBpQYJKwYBBAGCNxAEMYGX
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3Mg
MSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDCBpwYLKoZIhvcNAQkQAgsxgZeg
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBoRIMA0GCSqGSIb3DQEBAQUABIIBAB3i
AHPMxLmUjYJabydiVByGG+TFDK3IhJsjntzo2QKhwmltaekxSOpp4SluGH2Dsdccphr51Ph+kLaA
H0J6xq2Vc0IbfBsoq3sMOuo5bDeFB559y4ed8WpOZ9tQ3uf1jhMr3O+qcNuFzTiqMQhGbYs7/9Ww
NFE4RdRxXHKxX2o+Mu+RVm7J5z98nS4CEQDijozpOvztOfnQAcrlCTMVoMGb37i/SYMFJ3hqYorF
CK3MjD5RvargrtCubWEH2rcIIL8wOJvSZzfHxw05gNIOEr1jPduXr7tywbHIEhBHDMEFYu4RV01I
BE1nhcVEjKty8lTvg705t4F+n5bDd10O7iEAAAAAAAA=

--Apple-Mail=_20838759-A7A4-43A1-A8A8-1742E0DF34AA--

From hallam@gmail.com  Wed Jun 12 12:52:41 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E5B11E80F8 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 12:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.924
X-Spam-Level: 
X-Spam-Status: No, score=-2.924 tagged_above=-999 required=5 tests=[AWL=0.674,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2JIXdrYq-UX for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 12:52:36 -0700 (PDT)
Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) by ietfa.amsl.com (Postfix) with ESMTP id ADF7F11E80F7 for <jose@ietf.org>; Wed, 12 Jun 2013 12:52:35 -0700 (PDT)
Received: by mail-lb0-f175.google.com with SMTP id r10so4825425lbi.34 for <jose@ietf.org>; Wed, 12 Jun 2013 12:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JCy1D67du4MVNNb8cVctRjhWTCQQXC+GWRf8A9zqyn0=; b=XGjQiidQ3HHHJds8rWl5qTQD2wDTd3qetFBwcHFibN3pQ2CxqyJ6YsAiBaS2+0V8eq pMK6yV+DSMDHT8Z3oi2WfmISyXacn+kscwwH1WCiJNSPmFTAwu8kGK7uAbOF/juyVNd4 lIcm2BXanPwL4Wuaf+J/vlgcdBrCJQX73QcVsbixSmMDVG2Fgq9czcFsd3aQ1rgf27/f lpKc281GDDbcT7Re9S6mOscNI1m7Q5tMl8QhygSjE4IEQoMW7BFFttBSndVatMF56yLt DWKgQGncb9+GZvmqGapdGgHKUdeUx2b/q3Szd/RaonWcfc1Pl02URA1OHVilGlwERYeZ O5mw==
MIME-Version: 1.0
X-Received: by 10.112.138.230 with SMTP id qt6mr11673886lbb.34.1371066754420;  Wed, 12 Jun 2013 12:52:34 -0700 (PDT)
Received: by 10.112.150.161 with HTTP; Wed, 12 Jun 2013 12:52:34 -0700 (PDT)
In-Reply-To: <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im> <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com>
Date: Wed, 12 Jun 2013 15:52:34 -0400
Message-ID: <CAMm+LwgR-5uxvXsc_d4nsJJqey5qDyK==Hetznujw8Nxhargfw@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e0112c742dc57a604defa5a48
Cc: "jose@ietf.org" <jose@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 19:52:41 -0000

--089e0112c742dc57a604defa5a48
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 11, 2013 at 1:14 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> <chair>
>
> At this point only the fact that binary encodings exist is in scope for the
> WG.
>
> Any concreteness would require a charter modification.
>

Any concrete would needs be added in apps area in any case.

The reason for raising it here was simply to make people aware that there
is a binary option and to encourage anyone who might be interested in
making sure that it is suitable for use with JOSE to take a look to check
if anything was left out.

I would like to be able to use JOSE as an alternative to CMS at some point.
But not with the Base64 penalty.

-- 
Website: http://hallambaker.com/

--089e0112c742dc57a604defa5a48
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Jun 11, 2013 at 1:14 PM, Jim Schaad <span dir=3D"l=
tr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@au=
gustcellars.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&lt;chair&gt;<br>
<br>
At this point only the fact that binary encodings exist is in scope for the=
<br>
WG.<br>
<br>
Any concreteness would require a charter modification.<br></blockquote><div=
><br></div><div style>Any concrete would needs be added in apps area in any=
 case.</div><div style><br></div><div style>The reason for raising it here =
was simply to make people aware that there is a binary option and to encour=
age anyone who might be interested in making sure that it is suitable for u=
se with JOSE to take a look to check if anything was left out.</div>
<div style><br></div><div style>I would like to be able to use JOSE as an a=
lternative to CMS at some point. But not with the Base64 penalty.</div><div=
 style><br></div></div>-- <br>Website: <a href=3D"http://hallambaker.com/">=
http://hallambaker.com/</a><br>

</div></div>

--089e0112c742dc57a604defa5a48--

From rlb@ipv.sx  Wed Jun 12 13:09:07 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E21B11E80EA for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.329
X-Spam-Level: 
X-Spam-Status: No, score=-0.329 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Gz6pq+pnzro for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:09:03 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFC311E80F5 for <jose@ietf.org>; Wed, 12 Jun 2013 13:09:01 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so5664058oah.10 for <jose@ietf.org>; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=s2Ts0xUwb5WxVqGdiA+aTij1Z1WC9z5DiVaOAkA2Gdg=; b=N/d1vBXUwxC3P4N1ySY5LbiwdFMtWYDAa4ZhzXFVX0G58cpDmWi7xjI2RlqR9kQ6it N1f0d0cge7KVhXkSlakdSu3DhmUQflGuDdDDlkxcroQXLW/SG3pvqHKHHW0zIwtmg+RX 0FnD0qu3RPpxZQHaopRak2+bWXtUnMz7bSH3k51Wq/I0vliDHYnYh7Z6ydm2ff/eCMg0 LOxI64kE2iGri0DWMd3chx1N/WcCjojS5e33AK3P+iLaNEPAmPFoKEoXk4X++6dd3dk7 Q3+3PbLkbwfFx+6fZOXWWofpXaNGqfq81WFw1v9W1w203gcB/3zPPAZZOcdtM3ujLPXS vxuA==
MIME-Version: 1.0
X-Received: by 10.60.134.236 with SMTP id pn12mr16940046oeb.4.1371067740458; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <CAMm+LwgR-5uxvXsc_d4nsJJqey5qDyK==Hetznujw8Nxhargfw@mail.gmail.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im> <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com> <CAMm+LwgR-5uxvXsc_d4nsJJqey5qDyK==Hetznujw8Nxhargfw@mail.gmail.com>
Date: Wed, 12 Jun 2013 16:09:00 -0400
Message-ID: <CAL02cgTnn16bPpG_i8EtSEym6bV+snvkSwpgrXYyapoGKdMvKQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b471f6aa2372704defa9594
X-Gm-Message-State: ALoCoQkAHFXYc/rC5dDV4ikME4jJqFD9s3MTNtGD8ZK7Ruvqr7iHZz5/Zx/plRCrP+AFMrkrLc1z
Cc: Jim Schaad <ietf@augustcellars.com>, Peter Saint-Andre <stpeter@stpeter.im>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:09:07 -0000

--047d7b471f6aa2372704defa9594
Content-Type: text/plain; charset=ISO-8859-1

Conversely, there's some discussion right now about how to make JOSE
suitable for a binary-capable encoding:
<http://www.ietf.org/mail-archive/web/jose/current/msg02493.html>


On Wed, Jun 12, 2013 at 3:52 PM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> On Tue, Jun 11, 2013 at 1:14 PM, Jim Schaad <ietf@augustcellars.com>wrote:
>
>> <chair>
>>
>> At this point only the fact that binary encodings exist is in scope for
>> the
>> WG.
>>
>> Any concreteness would require a charter modification.
>>
>
> Any concrete would needs be added in apps area in any case.
>
> The reason for raising it here was simply to make people aware that there
> is a binary option and to encourage anyone who might be interested in
> making sure that it is suitable for use with JOSE to take a look to check
> if anything was left out.
>
> I would like to be able to use JOSE as an alternative to CMS at some
> point. But not with the Base64 penalty.
>
> --
> Website: http://hallambaker.com/
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--047d7b471f6aa2372704defa9594
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Conversely, there&#39;s some discussion right now about ho=
w to make JOSE suitable for a binary-capable encoding:<div>&lt;<a href=3D"h=
ttp://www.ietf.org/mail-archive/web/jose/current/msg02493.html">http://www.=
ietf.org/mail-archive/web/jose/current/msg02493.html</a>&gt;</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Jun 12, 2013 at 3:52 PM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Tue, J=
un 11, 2013 at 1:14 PM, Jim Schaad <span dir=3D"ltr">&lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt;</s=
pan> wrote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&lt;chair&gt;<br>
<br>
At this point only the fact that binary encodings exist is in scope for the=
<br>
WG.<br>
<br>
Any concreteness would require a charter modification.<br></blockquote><div=
><br></div></div><div>Any concrete would needs be added in apps area in any=
 case.</div><div><br></div><div>The reason for raising it here was simply t=
o make people aware that there is a binary option and to encourage anyone w=
ho might be interested in making sure that it is suitable for use with JOSE=
 to take a look to check if anything was left out.</div>

<div><br></div><div>I would like to be able to use JOSE as an alternative t=
o CMS at some point. But not with the Base64 penalty.</div><span class=3D"H=
OEnZb"><font color=3D"#888888"><div><br></div></font></span></div><span cla=
ss=3D"HOEnZb"><font color=3D"#888888">-- <br>
Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">http://halla=
mbaker.com/</a><br>

</font></span></div></div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--047d7b471f6aa2372704defa9594--

From rlb@ipv.sx  Wed Jun 12 13:23:44 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C78821E8091 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssq0cB-IqSho for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:23:40 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E398C21E80A5 for <jose@ietf.org>; Wed, 12 Jun 2013 13:23:37 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so14019592obc.34 for <jose@ietf.org>; Wed, 12 Jun 2013 13:23:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=P3pXsvKSULObeVjdqBrhabFno8EyYjr/YcZNxcrFVuU=; b=DSB8aGCA2gKWitkqI37+YuSZoeel33W+fPmRHXaUJnG34xk49Jlypz/3kQOq8qunvW pxrauXVj8km5L2syWA9X+tdH88YAnVRRjbrSKNl0U96YYch1wrVKwV2JpRWhIg3FjapP N0On2pP685W8hh854Fjeb8SJcd216xhOlk9Gp1XGBVD9qSTkCa0n6fH0g0jVdI0rYG/V DsttIw5pgiwbN6Wks8iaNcSYNVasygU4j1ADgkIZ1LazXaHnkcqH5B2i27fOsLYt46se TxwWhjjKRSDEjRNFEYBcmKuBXd2FTO4lhLjA3gV4VLqk1FSHBVvAx/agaB8cfqQrq3hL /CKg==
MIME-Version: 1.0
X-Received: by 10.182.237.77 with SMTP id va13mr16740768obc.65.1371068617348;  Wed, 12 Jun 2013 13:23:37 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Wed, 12 Jun 2013 13:23:37 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com>
Date: Wed, 12 Jun 2013 16:23:37 -0400
Message-ID: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cdcce670fb04defac99f
X-Gm-Message-State: ALoCoQl+Yi4czqiBcOxsZn0wIx/Nnxb9cy/a0iJiQ29NxJFFfIJV2qtDZ1k1CGdVQlll9aXMvRU0
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:23:44 -0000

--e89a8ff1cdcce670fb04defac99f
Content-Type: text/plain; charset=ISO-8859-1

<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor
code.  But I think we're literally talking about something like a 5-line
patch.  And early JWT implementors knew or should have known (to use a DC
phrase) that they were dealing with a draft spec.  As the W3C editor's
draft template says, in big bold red print, "Implementors who are not
taking part in the discussions are likely to find the specification
changing out from under them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE
in place of CMS one day, without the base64 hit.  We should incur the
implementation pain now, and get the design right for the long run.  Base64
is a hack around JSON; we should build the system so that when we no longer
need that hack, it can go away.
</personal-opinion>

--Richard




On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.com
> wrote:

> I did at first find it curious why the cryptographic operations were over
> the base64url-enccoded values, but I was also very focused on JWE, where I
> think the field separation problem is less of an issue (at least now).  For
> JWS, this would certainly cause problems without some manner of unambiguous
> field parameterization.
>
> I will note that unescaped NULL is not valid in JSON, so it could be used
> as a separator between the encoded header and the payload.  I do find it
> interesting if JOSE could more easily and efficiently support other
> encodings.  However, I think that while this is an interesting thought
> experiment, it seems we're too far down the path to seriously consider it
> unless the current state were shown to be horribly broken.
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.
>
> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
> trac+jose@trac.tools.ietf.org> wrote:
>
> > #23: Make crypto independent of binary encoding (base64)
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> > For both serializations, you already need the base64url encoded versions
> > of the JWS Header and the JWS Payload to preserve them in transmission,
> so
> > computing them isn't an extra burden.  In the JWS Compact Serialization,
> > you already need the concatenation of the Encoded JWS Header, a period
> > character, and the Encoded JWS Payload, so computing that concatenation
> > isn't an extra burden.  Given you already have that quantity, computing
> > the signature over it is the easiest thing for developers to do, and it's
> > been shown to work well in practice.  There's no compelling reason to
> make
> > this change.
> >
> > Even for the JSON Serialization, the only "extra" step that's required to
> > compute the signature is the concatenation with the period character - to
> > prevent shifting of data from one field to the other, as described by Jim
> > Schaad in the e-mail thread.  So this step isn't actually "extra" at all
> -
> > it's necessary.  It's also highly advantageous to use exactly the same
> > computation for both serializations, which is currently the case.
> >
> > Since there is no compelling reason to make this change, and since making
> > it could enable the "shifting" problem identified by Jim, it should not
> be
> > made.
> >
> > --
> >
> -------------------------+-------------------------------------------------
> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
> >     Type:  defect       |  encryption@tools.ietf.org
> > Priority:  major        |      Status:  new
> > Component:  json-web-    |   Milestone:
> >  encryption             |     Version:
> > Severity:  -            |  Resolution:
> > Keywords:               |
> >
> -------------------------+-------------------------------------------------
> >
> > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2
> >
> > jose <http://tools.ietf.org/jose/>
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
>
>

--e89a8ff1cdcce670fb04defac99f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>&lt;impartial-analysis&gt;</div>So just to be clear o=
n the trade-off the WG has to make:<div><br></div><div>On the one hand: Bre=
aking every existing JWT implementation in the world</div><div>On the other=
 hand: Eternally binding ourselves to base64 encoding, even if binary-safe =
encodings become available (CBOR, MsgPack, etc.)</div>
<div>&lt;/impartial-analysis=A0&gt;<br></div><div><br></div><div>&lt;person=
al-opinion&gt;</div><div>I have some sympathy with JWT implementors. =A0It =
sucks to have to refactor code. =A0But I think we&#39;re literally talking =
about something like a 5-line patch. =A0And early JWT implementors knew or =
should have known (to use a DC phrase) that they were dealing with a draft =
spec. =A0As the W3C editor&#39;s draft template says, in big bold red print=
, &quot;Implementors who are not taking part in the discussions are likely =
to find the specification changing out from under them in incompatible ways=
.&quot;</div>
<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>
<div>&lt;/personal-opinion&gt;<br></div><div><br></div><div>--Richard</div>=
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) <span dir=3D"ltr">&lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"=
_blank">mamille2@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>

<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>

<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com">mamille2@cisco.com</=
a> &gt;<br>
Cisco Systems, Inc.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org">trac+jose@trac.tools.ietf.org</a>&gt; wrote:<br=
>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com">michael.jon=
es@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">&gt; __________________=
_____________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>

--e89a8ff1cdcce670fb04defac99f--

From breno@google.com  Wed Jun 12 13:30:42 2013
Return-Path: <breno@google.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B36C21E8094 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAMZnoMnmEsi for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:30:37 -0700 (PDT)
Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0E721E8091 for <jose@ietf.org>; Wed, 12 Jun 2013 13:30:37 -0700 (PDT)
Received: by mail-qe0-f46.google.com with SMTP id nd7so3477431qeb.33 for <jose@ietf.org>; Wed, 12 Jun 2013 13:30:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=h+XLaH0QXJTDq5XsMOJ+Z5zPGxvkj+xaoZC20z0xQgE=; b=FX1CEpd9zOts1JAwQ5SYJk+/2ih1y8mqtB8fsAno7wjJw41ddRsWn6umN2I/7cWXle DaXF3s2ZHSo7/MAZ7Bxd1y8W1LHzJikwbA63JDwOw9geLpZI3uTX5NtM8YEQkrOkURt2 pqcM+SAvkSVJEjvN1dMAtcsLvpwY4a0rtElmCUprqjUxYjLvz9Spvze4oZ5UnhpXMU9/ GJ8cOB11UHNiraDOcL5kP2ijTlWPx7wEUECwySTclBUETAIMKoF6E/+QihOfwOXKO2R2 4OrBkjorFPbEGHvVyss0tB2xySXxwu4PRjhBBjs47a7qy9LSfkFWoIYNBExBn35uVlVL dMVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=h+XLaH0QXJTDq5XsMOJ+Z5zPGxvkj+xaoZC20z0xQgE=; b=iaMe7TU84ht9csg5JaPhs5bsMGu9Z3tbZzKOqXK4GUcN7InDp/+zWknZ4AfGjpUg5v MF/RyX7+b89RlGZe2gxexSXV2tTC7Agz0zOvTC8zGKuQYCYkrpLspGeOzwyMXma0Dmld HauWQk5ZzcIyVwYycAMLmWW+q7o1FUECpBF0uSDXXQ1qBNB0EEm12nf59klj6tmpafRt AZk8/cW2WGNEqB5Q503HMiTkaYnOGP5Z0AotjxHYp6zldcR/dpiduwfj0/6LE3mT3E44 DG2Ap6UXg7ZA7E4FlQ3QRaHE2a0K66CfbxfeRnksO8ukH5gutrPecpV82G1q44dox1Mk f/Sg==
MIME-Version: 1.0
X-Received: by 10.49.71.203 with SMTP id x11mr26257783qeu.19.1371069036575; Wed, 12 Jun 2013 13:30:36 -0700 (PDT)
Received: by 10.229.178.195 with HTTP; Wed, 12 Jun 2013 13:30:36 -0700 (PDT)
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
Date: Wed, 12 Jun 2013 13:30:36 -0700
Message-ID: <CAAJ++qGpLJrFRaxXwgSAxQK4+4Q4K6ycp408uhd5tyUnx6ikzA@mail.gmail.com>
From: Breno de Medeiros <breno@google.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQknWu8Zs06lUQzur0est1R0m3EbzT2tOVXUBAD+UuBwg+Zg5/v59PPr5YNwjQh0f5tVRUd5d86wNUlSMlH3mqGdiFK0QscrNdZD4Y87sBSgaEiKCq/0Fm7B6UHyHgAaTAM5ms5AvfwUoPZB0kkx9RTO7HR594yPCBnAIblEC7ks23CZG2psfn2BDi0eambzWy9k30Lg
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:30:42 -0000

The alternative is not only binding to base64 encoding forever. It is
to introduce canonicalization as well -- signature verification will
fail if JSON deserialization modifies blank spacing data, and you can
be a compliant JSON parser and not be faithful with representation of
line-breaks, for instance. As I understand the proposal, it does not
indicate that the encoding is specifiable, it indicates that signature
computation and verification should be applied to the decoded format.

On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
> <impartial-analysis>
> So just to be clear on the trade-off the WG has to make:
>
> On the one hand: Breaking every existing JWT implementation in the world
> On the other hand: Eternally binding ourselves to base64 encoding, even if
> binary-safe encodings become available (CBOR, MsgPack, etc.)
> </impartial-analysis >
>
> <personal-opinion>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's draft
> template says, in big bold red print, "Implementors who are not taking part
> in the discussions are likely to find the specification changing out from
> under them in incompatible ways."
>
> As PHB pointed out in the other thread, it would be nice to use JWS and JWE
> in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base64
> is a hack around JSON; we should build the system so that when we no longer
> need that hack, it can go away.
> </personal-opinion>
>
> --Richard
>
>
>
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2)
> <mamille2@cisco.com> wrote:
>>
>> I did at first find it curious why the cryptographic operations were over
>> the base64url-enccoded values, but I was also very focused on JWE, where I
>> think the field separation problem is less of an issue (at least now).  For
>> JWS, this would certainly cause problems without some manner of unambiguous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be used
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider it
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker
>> <trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versions
>> > of the JWS Header and the JWS Payload to preserve them in transmission,
>> > so
>> > computing them isn't an extra burden.  In the JWS Compact Serialization,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenation
>> > isn't an extra burden.  Given you already have that quantity, computing
>> > the signature over it is the easiest thing for developers to do, and
>> > it's
>> > been shown to work well in practice.  There's no compelling reason to
>> > make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> > to
>> > compute the signature is the concatenation with the period character -
>> > to
>> > prevent shifting of data from one field to the other, as described by
>> > Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at all
>> > -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> > making
>> > it could enable the "shifting" problem identified by Jim, it should not
>> > be
>> > made.
>> >
>> > --
>> >
>> > -------------------------+-------------------------------------------------
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> > -------------------------+-------------------------------------------------
>> >
>> > Ticket URL:
>> > <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose
>>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>



-- 
--Breno

From Michael.Jones@microsoft.com  Wed Jun 12 13:33:16 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5774311E80BA for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WG2gEmyNGcXI for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:33:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 3248821E809B for <jose@ietf.org>; Wed, 12 Jun 2013 13:33:09 -0700 (PDT)
Received: from BL2FFO11FD005.protection.gbl (10.173.161.201) by BL2FFO11HUB037.protection.gbl (10.173.160.241) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 12 Jun 2013 20:33:07 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD005.mail.protection.outlook.com (10.173.161.1) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 12 Jun 2013 20:33:07 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.110]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Wed, 12 Jun 2013 20:32:58 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Thread-Topic: [jose] #23: Make crypto independent of binary encoding (base64)
Thread-Index: AQHOZwAMAj7aO3iBB0SstN6K1FxxM5kyI/iAgABjd4CAAAB88A==
Date: Wed, 12 Jun 2013 20:32:57 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436782C704@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436782C704TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51444003)(24454002)(189002)(51704005)(199002)(377454002)(49866001)(63696002)(44976003)(33656001)(47446002)(76796001)(54356001)(56776001)(74876001)(74706001)(74662001)(74366001)(31966008)(80022001)(69226001)(47976001)(74502001)(20776003)(81542001)(512954002)(76482001)(50986001)(79102001)(51856001)(54316002)(46102001)(76786001)(59766001)(6806003)(66066001)(47736001)(71186001)(56816003)(53806001)(81342001)(65816001)(55846006)(77982001)(77096001)(16236675002)(4396001)(16406001)(15202345002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB037; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08756AC3C8
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:33:16 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436782C704TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We shouldn't be basing decisions now on speculative binary encoding that ma=
y or may not ever come into existence or gain any traction.  We're explicit=
ly building solutions that are intended to be easily usable with JSON as it=
 exists today, for deployment today and into the future.

As Justin pointed out, there's an existence proof that JWS is simple enough=
 that developers get it right.  That's actually very important, and not som=
ething that we should dismiss lightly.

If later a binary encoding has come into existence and gained traction, we =
could decide to recharter and do more work, if necessary.  But I'm not hold=
ing my breath on the precondition to that "if".  Besides, if people are fin=
e with binary encodings, we already have CMS.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Wednesday, June 12, 2013 1:24 PM
To: Matt Miller (mamille2)
Cc: jose issue tracker; <draft-ietf-jose-json-web-encryption@tools.ietf.org=
>; Mike Jones; <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)

<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor c=
ode.  But I think we're literally talking about something like a 5-line pat=
ch.  And early JWT implementors knew or should have known (to use a DC phra=
se) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part i=
n the discussions are likely to find the specification changing out from un=
der them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE=
 in place of CMS one day, without the base64 hit.  We should incur the impl=
ementation pain now, and get the design right for the long run.  Base64 is =
a hack around JSON; we should build the system so that when we no longer ne=
ed that hack, it can go away.
</personal-opinion>

--Richard



On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m<mailto:mamille2@cisco.com>> wrote:
I did at first find it curious why the cryptographic operations were over t=
he base64url-enccoded values, but I was also very focused on JWE, where I t=
hink the field separation problem is less of an issue (at least now).  For =
JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload.  I do find it int=
eresting if JOSE could more easily and efficiently support other encodings.=
  However, I think that while this is an interesting thought experiment, it=
 seems we're too far down the path to seriously consider it unless the curr=
ent state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ietf.=
org<mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com<mailto:michael.jones@microsoft.co=
m>):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
> -------------------------+-----------------------------------------------=
--
> Reporter:  rlb@ipv.sx<mailto:rlb@ipv.sx>   |       Owner:  draft-ietf-jos=
e-json-web-
>     Type:  defect       |  encryption@tools.ietf.org<mailto:encryption@to=
ols.ietf.org>
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> -------------------------+-----------------------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org<mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B16804296739436782C704TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We shouldn&#8217;t be bas=
ing decisions now on speculative binary encoding that may or may not ever c=
ome into existence or gain any traction.&nbsp; We&#8217;re explicitly build=
ing
 solutions that are intended to be easily usable with JSON as it exists tod=
ay, for deployment today and into the future.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As Justin pointed out, th=
ere&#8217;s an existence proof that JWS is simple enough that developers ge=
t it right.&nbsp; That&#8217;s actually very important, and not something
 that we should dismiss lightly.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If later a binary encodin=
g has come into existence and gained traction, we could decide to recharter=
 and do more work, if necessary.&nbsp; But I&#8217;m not holding my
 breath on the precondition to that &#8220;if&#8221;.&nbsp; Besides, if peo=
ple are fine with binary encodings, we already have CMS.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:24 PM<br>
<b>To:</b> Matt Miller (mamille2)<br>
<b>Cc:</b> jose issue tracker; &lt;draft-ietf-jose-json-web-encryption@tool=
s.ietf.org&gt;; Mike Jones; &lt;jose@ietf.org&gt;<br>
<b>Subject:</b> Re: [jose] #23: Make crypto independent of binary encoding =
(base64)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">&lt;impartial-analysis&gt;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">So just to be clear on the trade-off the WG has to m=
ake:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the one hand: Breaking every existing JWT impleme=
ntation in the world<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the other hand: Eternally binding ourselves to ba=
se64 encoding, even if binary-safe encodings become available (CBOR, MsgPac=
k, etc.)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/impartial-analysis&nbsp;&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I have some sympathy with JWT implementors. &nbsp;It=
 sucks to have to refactor code. &nbsp;But I think we're literally talking =
about something like a 5-line patch. &nbsp;And early JWT implementors knew =
or should have known (to use a DC phrase) that they
 were dealing with a draft spec. &nbsp;As the W3C editor's draft template s=
ays, in big bold red print, &quot;Implementors who are not taking part in t=
he discussions are likely to find the specification changing out from under=
 them in incompatible ways.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. &n=
bsp;We should incur the implementation pain now, and get the design right f=
or the long run. &nbsp;Base64 is a hack around
 JSON; we should build the system so that when we no longer need that hack,=
 it can go away.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@c=
isco.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I did at first find it curious why the cryptographic=
 operations were over the base64url-enccoded values, but I was also very fo=
cused on JWE, where I think the field separation problem is less of an issu=
e (at least now). &nbsp;For JWS, this would
 certainly cause problems without some manner of unambiguous field paramete=
rization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. &nbsp;I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. &nbsp;However, I think that while this
 is an interesting thought experiment, it seems we're too far down the path=
 to seriously consider it unless the current state were shown to be horribl=
y broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com">mamille2@cisco.com</=
a> &gt;<br>
Cisco Systems, Inc.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org">trac&#43;jose@trac.tools.ietf.org</a>&gt; wrote=
:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com">michael.jon=
es@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact Seriali=
zation,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, com=
puting<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling reaso=
n to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that'=
s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually &quot;e=
xtra&quot; at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly the=
 same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a> &nbsp; | =
&nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-web-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a href=
=3D"mailto:encryption@tools.ietf.org">encryption@tools.ietf.org</a><br>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp=
;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &n=
bsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;Res=
olution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436782C704TK5EX14MBXC283r_--

From tbray@textuality.com  Wed Jun 12 13:44:35 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C3D21F9811 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.465
X-Spam-Level: 
X-Spam-Status: No, score=-0.465 tagged_above=-999 required=5 tests=[AWL=-0.917, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByRvb0R8xjZF for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:44:31 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id D199A21F9808 for <jose@ietf.org>; Wed, 12 Jun 2013 13:44:30 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db10so7172830veb.12 for <jose@ietf.org>; Wed, 12 Jun 2013 13:44:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=/mEa+4m9+KIpwQZRFD91L52v48DUY4OOuikEZrRFBpk=; b=WnGzWMAEO3mZBEw8MMPRLz/josSjmyyKaWLHV+ZHhkAoyKCVhtafx0i7rNT9cWo7Kr /wo8iTev1dmddXlFZFtoPkd/SBvKu2FIC6Ag4ARgt3n9/mElWYu2OTqg3wwy/Mnzenjd e/r8XzVvWN7SRL8GBhh8JklRRKrQN9mCky35WnPbey9eSou/DoKeY/3s826W983ln6pz fXfr/zKRmVa753fpvRIYUHHR8Y+lGFvWW+9t0+NLe91Zu/ePu59DvGbmDjCuC5PXxPXH 29ZaL/XrPH7nrbi2b2vbcetdkRS14kuTYaAbr/PPEEaz2JfZfx/jHBLjuW0+wa2S2wYR xNGA==
MIME-Version: 1.0
X-Received: by 10.220.248.137 with SMTP id mg9mr10369923vcb.38.1371069869974;  Wed, 12 Jun 2013 13:44:29 -0700 (PDT)
Received: by 10.220.25.199 with HTTP; Wed, 12 Jun 2013 13:44:29 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
Date: Wed, 12 Jun 2013 13:44:29 -0700
Message-ID: <CAHBU6iucjAQ-HDvHsaEARgpve4q3bMeiM02P6npnq5Ljv63JVA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=089e01177275900c8204defb1443
X-Gm-Message-State: ALoCoQmWWPAW4VHjaaThPULoDiOfluoDMnEcakf+LPAwkbzTIsHtIpH/h2ss/jW+Sx2fg8GpK2Fg
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:44:35 -0000

--089e01177275900c8204defb1443
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <rlb@ipv.sx> wrote:

> On the one hand: Breaking every existing JWT implementation in the world
> On the other hand: Eternally binding ourselves to base64 encoding, even i=
f
> binary-safe encodings become available (CBOR, MsgPack, etc.)
>

JWT stands for JSON Web Token. JSON is JSON, not some binary encoding, and
base64 makes it Web-safe at acceptable cost. It meets the stated needs, is
widely implemented, and works.  If at some future time there=E2=80=99s an
interesting binary packaging format X, invent XWT which does a good job for
X.  This is a fishing expedition.

Speaking on behalf of the many who are already using JWT with excellent
results, could the WG please ship this highly successful product?

 -T



>
> <personal-opinion>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base=
64
> is a hack around JSON; we should build the system so that when we no long=
er
> need that hack, it can go away.
> </personal-opinion>
>
> --Richard
>
>
>
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:
>
>> I did at first find it curious why the cryptographic operations were ove=
r
>> the base64url-enccoded values, but I was also very focused on JWE, where=
 I
>> think the field separation problem is less of an issue (at least now).  =
For
>> JWS, this would certainly cause problems without some manner of unambigu=
ous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be use=
d
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider i=
t
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versio=
ns
>> > of the JWS Header and the JWS Payload to preserve them in transmission=
,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serializatio=
n,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenatio=
n
>> > isn't an extra burden.  Given you already have that quantity, computin=
g
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should no=
t
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+----------------------------------------------=
---
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+----------------------------------------------=
---
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose
>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--089e01177275900c8204defb1443
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <span dir=
=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>=
&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">On the one hand: Breaking every existing JWT implementatio=
n in the world<div>On the other hand: Eternally binding ourselves to base64=
 encoding, even if binary-safe encodings become available (CBOR, MsgPack, e=
tc.)</div>
</div></blockquote><div><br></div><div>JWT stands for JSON Web Token. JSON =
is JSON, not some binary encoding, and base64 makes it Web-safe at acceptab=
le cost. It meets the stated needs, is widely implemented, and works.=C2=A0=
 If at some future time there=E2=80=99s an interesting binary packaging for=
mat X, invent XWT which does a good job for X.=C2=A0 This is a fishing expe=
dition.=C2=A0 <br>
<br>Speaking on behalf of the many who are already using JWT with excellent=
 results, could the WG please ship this highly successful product?<br><br>=
=C2=A0-T<br></div><div><br>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><br><div>&lt;personal-opinion&gt;</div><div>I have some sy=
mpathy with JWT implementors. =C2=A0It sucks to have to refactor code. =C2=
=A0But I think we&#39;re literally talking about something like a 5-line pa=
tch. =C2=A0And early JWT implementors knew or should have known (to use a D=
C phrase) that they were dealing with a draft spec. =C2=A0As the W3C editor=
&#39;s draft template says, in big bold red print, &quot;Implementors who a=
re not taking part in the discussions are likely to find the specification =
changing out from under them in incompatible ways.&quot;</div>

<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =C2=
=A0We should incur the implementation pain now, and get the design right fo=
r the long run. =C2=A0Base64 is a hack around JSON; we should build the sys=
tem so that when we no longer need that hack, it can go away.</div>

<div>&lt;/personal-opinion&gt;<span class=3D"HOEnZb"><font color=3D"#888888=
"><br></font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><d=
iv><br></div><div>--Richard</div><div><br></div><div><br></div></font></spa=
n></div>
<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (m=
amille2) <span dir=3D"ltr">&lt;<a href=3D"mailto:mamille2@cisco.com" target=
=3D"_blank">mamille2@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =C2=A0For JWS, this would certainly cause problem=
s without some manner of unambiguous field parameterization.<br>


<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =C2=A0I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. =C2=A0However, I think that while this is an interesting thought expe=
riment, it seems we&#39;re too far down the path to seriously consider it u=
nless the current state were shown to be horribly broken.<br>


<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =C2=A0In the JWS Compact Ser=
ialization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =C2=A0Given you already have that quantity,=
 computing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =C2=A0There&#39;s no compelling r=
eason to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =C2=A0So this step isn&#39;t actually &qu=
ot;extra&quot; at all -<br>
&gt; it&#39;s necessary. =C2=A0It&#39;s also highly advantageous to use exa=
ctly the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =C2=A0rlb@ipv.sx =C2=A0 | =C2=A0 =C2=A0 =C2=A0 Owner: =C2=A0=
draft-ietf-jose-json-web-<br>
&gt; =C2=A0 =C2=A0 Type: =C2=A0defect =C2=A0 =C2=A0 =C2=A0 | =C2=A0<a href=
=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ie=
tf.org</a><br>
&gt; Priority: =C2=A0major =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 =C2=
=A0Status: =C2=A0new<br>
&gt; Component: =C2=A0json-web- =C2=A0 =C2=A0| =C2=A0 Milestone:<br>
&gt; =C2=A0encryption =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =
=C2=A0 Version:<br>
&gt; Severity: =C2=A0- =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0Res=
olution:<br>
&gt; Keywords: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div></div>

--089e01177275900c8204defb1443--

From dick.hardt@gmail.com  Wed Jun 12 13:54:49 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D196F21F8628 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.862
X-Spam-Level: 
X-Spam-Status: No, score=-1.862 tagged_above=-999 required=5 tests=[AWL=0.737,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B0-GEqKCqtu4 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:54:47 -0700 (PDT)
Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com [IPv6:2a00:1450:4008:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 0957F21F85B4 for <jose@ietf.org>; Wed, 12 Jun 2013 13:54:46 -0700 (PDT)
Received: by mail-bk0-f50.google.com with SMTP id ik8so2879119bkc.23 for <jose@ietf.org>; Wed, 12 Jun 2013 13:54:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ckvAAa1vemX5dLeQWOlrrX2xrZAztumYpxvlDFt914k=; b=kYI8FhLgU6y8guw3IoYw80+Pr8BxkGxkMQNrQsDnxyZOIe17N8wWdJrRC61CZkf46a gYl3tBIJtX6hbs7E2EsoZ/qEsSxVd04k1ZMUfoe/kJqyOEWbK4qb3uVcjnz7oGNkoClm nybJDDW/Vu4x8lEIH6GeDD3hMLn17Cxzd8rzh30LYXdNCY4DexhUNN98bjd+dTZzNAv0 SRlE3LOpku9MqshuA3YIjdZv/HiJzpwk/U0qNLO6lkAnzcNTRO3usZX1ntnto/usJvMj QJzM9Rmq7ggzx6D93vjkzQg9btgBBxDtPOPpRPD1krgMv1R6gppcisjwkt9sRkuVfVps Df4w==
X-Received: by 10.204.189.7 with SMTP id dc7mr3423402bkb.108.1371070485117; Wed, 12 Jun 2013 13:54:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.168.12 with HTTP; Wed, 12 Jun 2013 13:54:24 -0700 (PDT)
In-Reply-To: <CAHBU6iucjAQ-HDvHsaEARgpve4q3bMeiM02P6npnq5Ljv63JVA@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <CAHBU6iucjAQ-HDvHsaEARgpve4q3bMeiM02P6npnq5Ljv63JVA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 12 Jun 2013 13:54:24 -0700
Message-ID: <CAD9ie-tkAHXtVYQHwORC2iBRDBvYO8Y1nuvh+Nc8fuJ3kfBgXA@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary=20cf302d4ed63a7e1604defb3937
Cc: Richard Barnes <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:54:49 -0000

--20cf302d4ed63a7e1604defb3937
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

+1


On Wed, Jun 12, 2013 at 1:44 PM, Tim Bray <tbray@textuality.com> wrote:

> On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> On the one hand: Breaking every existing JWT implementation in the world
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)
>>
>
> JWT stands for JSON Web Token. JSON is JSON, not some binary encoding, an=
d
> base64 makes it Web-safe at acceptable cost. It meets the stated needs, i=
s
> widely implemented, and works.  If at some future time there=92s an
> interesting binary packaging format X, invent XWT which does a good job f=
or
> X.  This is a fishing expedition.
>
> Speaking on behalf of the many who are already using JWT with excellent
> results, could the WG please ship this highly successful product?
>
>  -T
>
>
>
>>
>> <personal-opinion>
>> I have some sympathy with JWT implementors.  It sucks to have to refacto=
r
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a D=
C
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur th=
e
>> implementation pain now, and get the design right for the long run.  Bas=
e64
>> is a hack around JSON; we should build the system so that when we no lon=
ger
>> need that hack, it can go away.
>> </personal-opinion>
>>
>> --Richard
>>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:
>>
>>> I did at first find it curious why the cryptographic operations were
>>> over the base64url-enccoded values, but I was also very focused on JWE,
>>> where I think the field separation problem is less of an issue (at leas=
t
>>> now).  For JWS, this would certainly cause problems without some manner=
 of
>>> unambiguous field parameterization.
>>>
>>> I will note that unescaped NULL is not valid in JSON, so it could be
>>> used as a separator between the encoded header and the payload.  I do f=
ind
>>> it interesting if JOSE could more easily and efficiently support other
>>> encodings.  However, I think that while this is an interesting thought
>>> experiment, it seems we're too far down the path to seriously consider =
it
>>> unless the current state were shown to be horribly broken.
>>>
>>>
>>> - m&m
>>>
>>> Matt Miller < mamille2@cisco.com >
>>> Cisco Systems, Inc.
>>>
>>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>>> trac+jose@trac.tools.ietf.org> wrote:
>>>
>>> > #23: Make crypto independent of binary encoding (base64)
>>> >
>>> >
>>> > Comment (by michael.jones@microsoft.com):
>>> >
>>> > For both serializations, you already need the base64url encoded
>>> versions
>>> > of the JWS Header and the JWS Payload to preserve them in
>>> transmission, so
>>> > computing them isn't an extra burden.  In the JWS Compact
>>> Serialization,
>>> > you already need the concatenation of the Encoded JWS Header, a perio=
d
>>> > character, and the Encoded JWS Payload, so computing that concatenati=
on
>>> > isn't an extra burden.  Given you already have that quantity, computi=
ng
>>> > the signature over it is the easiest thing for developers to do, and
>>> it's
>>> > been shown to work well in practice.  There's no compelling reason to
>>> make
>>> > this change.
>>> >
>>> > Even for the JSON Serialization, the only "extra" step that's require=
d
>>> to
>>> > compute the signature is the concatenation with the period character =
-
>>> to
>>> > prevent shifting of data from one field to the other, as described by
>>> Jim
>>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>>> all -
>>> > it's necessary.  It's also highly advantageous to use exactly the sam=
e
>>> > computation for both serializations, which is currently the case.
>>> >
>>> > Since there is no compelling reason to make this change, and since
>>> making
>>> > it could enable the "shifting" problem identified by Jim, it should
>>> not be
>>> > made.
>>> >
>>> > --
>>> >
>>> -------------------------+---------------------------------------------=
----
>>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>>> >     Type:  defect       |  encryption@tools.ietf.org
>>> > Priority:  major        |      Status:  new
>>> > Component:  json-web-    |   Milestone:
>>> >  encryption             |     Version:
>>> > Severity:  -            |  Resolution:
>>> > Keywords:               |
>>> >
>>> -------------------------+---------------------------------------------=
----
>>> >
>>> > Ticket URL: <
>>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>>> > jose <http://tools.ietf.org/jose/>
>>> >
>>> > _______________________________________________
>>> > jose mailing list
>>> > jose@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--20cf302d4ed63a7e1604defb3937
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1</div><div class=3D"gmail_extra"><br><br><div class=3D"g=
mail_quote">On Wed, Jun 12, 2013 at 1:44 PM, Tim Bray <span dir=3D"ltr">&lt=
;<a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality=
.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Wed, J=
un 12, 2013 at 1:23 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br>

</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">On the one hand: Breaking every existing JWT implementatio=
n in the world<div>On the other hand: Eternally binding ourselves to base64=
 encoding, even if binary-safe encodings become available (CBOR, MsgPack, e=
tc.)</div>


</div></blockquote><div><br></div></div><div>JWT stands for JSON Web Token.=
 JSON is JSON, not some binary encoding, and base64 makes it Web-safe at ac=
ceptable cost. It meets the stated needs, is widely implemented, and works.=
=A0 If at some future time there=92s an interesting binary packaging format=
 X, invent XWT which does a good job for X.=A0 This is a fishing expedition=
.=A0 <br>


<br>Speaking on behalf of the many who are already using JWT with excellent=
 results, could the WG please ship this highly successful product?<span cla=
ss=3D"HOEnZb"><font color=3D"#888888"><br><br>=A0-T<br></font></span></div>=
<div>

<div class=3D"h5"><div><br>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><br><div>&lt;personal-opinion&gt;</div><div>I have some sy=
mpathy with JWT implementors. =A0It sucks to have to refactor code. =A0But =
I think we&#39;re literally talking about something like a 5-line patch. =
=A0And early JWT implementors knew or should have known (to use a DC phrase=
) that they were dealing with a draft spec. =A0As the W3C editor&#39;s draf=
t template says, in big bold red print, &quot;Implementors who are not taki=
ng part in the discussions are likely to find the specification changing ou=
t from under them in incompatible ways.&quot;</div>



<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>



<div>&lt;/personal-opinion&gt;<span><font color=3D"#888888"><br></font></sp=
an></div><span><font color=3D"#888888"><div><br></div><div>--Richard</div><=
div><br></div><div><br></div></font></span></div>
<div><div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <span dir=3D"ltr">&lt=
;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com=
</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>




<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>




<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--20cf302d4ed63a7e1604defb3937--

From rlb@ipv.sx  Wed Jun 12 13:56:10 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5CD11E810C for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.337
X-Spam-Level: 
X-Spam-Status: No, score=-0.337 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25x45yRQdCs6 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:56:02 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 75E1111E8108 for <jose@ietf.org>; Wed, 12 Jun 2013 13:56:00 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so4959768oah.39 for <jose@ietf.org>; Wed, 12 Jun 2013 13:56:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=d/IWNCGUFembJw7a+g1cN9EMdqmjRWc07J9PLt9tdXw=; b=Yl3/Ziith4qazIzSAM9pUyovdnKNLoKduTWTj9e2OItVZymSjSKOfOy2zLAB8FBHph hZaYMSQkaM2W0lySKe4ewoftkGeMG5Gpxkf0WlIBqn61J05eiQzXZq7d2ZVZY7m1Nk89 s8yiLh5fKj0xtS3zdgi4s2rZx2CYRGB/1VPmw3qkWoRK3AQcjM5RwrDn8u79AaMZpvJQ d5KkWKvfIbWz5CUz+dP8899cndEXQto/CqcR1c7Ay7o0kX12VWI78ywyTnumpBgkNlyM CoYbWz1/WLidtMml4sTJbxhpkXVQUKvkPcakTg0w7cuRszmd6bci67IM8yZQGRHv4q2T v1Kw==
MIME-Version: 1.0
X-Received: by 10.60.42.237 with SMTP id r13mr17054296oel.61.1371070559816; Wed, 12 Jun 2013 13:55:59 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Wed, 12 Jun 2013 13:55:59 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
Date: Wed, 12 Jun 2013 16:55:59 -0400
Message-ID: <CAL02cgQ+K=dWnhSa7A4w85psuxOuuf9m09uyChcOZPe17BCizQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c206aaae208904defb3d9f
X-Gm-Message-State: ALoCoQlC3qkQqfv6lcReLXxDCP/Tucpk5oq/9khZKL2VL8iaJph04/IFKthyhrDCg4SRWnJ2FjDG
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 20:56:10 -0000

--001a11c206aaae208904defb3d9f
Content-Type: text/plain; charset=ISO-8859-1

To be clear, I structured my message in two parts for a reason, to separate
the analysis from the opinion.  I acknowledge that I am but one voice here,
and I'm increasingly hearing how alone I am :)


On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:

> <impartial-analysis>
> So just to be clear on the trade-off the WG has to make:
>
> On the one hand: Breaking every existing JWT implementation in the world
> On the other hand: Eternally binding ourselves to base64 encoding, even if
> binary-safe encodings become available (CBOR, MsgPack, etc.)
> </impartial-analysis >
>
> <personal-opinion>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base64
> is a hack around JSON; we should build the system so that when we no longer
> need that hack, it can go away.
> </personal-opinion>
>
> --Richard
>
>
>
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:
>
>> I did at first find it curious why the cryptographic operations were over
>> the base64url-enccoded values, but I was also very focused on JWE, where I
>> think the field separation problem is less of an issue (at least now).  For
>> JWS, this would certainly cause problems without some manner of unambiguous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be used
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider it
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versions
>> > of the JWS Header and the JWS Payload to preserve them in transmission,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serialization,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenation
>> > isn't an extra burden.  Given you already have that quantity, computing
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should not
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+-------------------------------------------------
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+-------------------------------------------------
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose
>>
>>
>

--001a11c206aaae208904defb3d9f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">To be clear, I structured my message in two parts for a re=
ason, to separate the analysis from the opinion. =A0I acknowledge that I am=
 but one voice here, and I&#39;m increasingly hearing how alone I am :)</di=
v>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jun 1=
2, 2013 at 4:23 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:=
rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div dir=3D"ltr"><div>&lt;impartial-analysis&gt;</div>So just to be clear o=
n the trade-off the WG has to make:<div><br></div><div>On the one hand: Bre=
aking every existing JWT implementation in the world</div><div>On the other=
 hand: Eternally binding ourselves to base64 encoding, even if binary-safe =
encodings become available (CBOR, MsgPack, etc.)</div>

<div>&lt;/impartial-analysis=A0&gt;<br></div><div><br></div><div>&lt;person=
al-opinion&gt;</div><div>I have some sympathy with JWT implementors. =A0It =
sucks to have to refactor code. =A0But I think we&#39;re literally talking =
about something like a 5-line patch. =A0And early JWT implementors knew or =
should have known (to use a DC phrase) that they were dealing with a draft =
spec. =A0As the W3C editor&#39;s draft template says, in big bold red print=
, &quot;Implementors who are not taking part in the discussions are likely =
to find the specification changing out from under them in incompatible ways=
.&quot;</div>

<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>

<div>&lt;/personal-opinion&gt;<span class=3D"HOEnZb"><font color=3D"#888888=
"><br></font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><d=
iv><br></div><div>--Richard</div><div><br></div><div><br></div></font></spa=
n></div>
<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (m=
amille2) <span dir=3D"ltr">&lt;<a href=3D"mailto:mamille2@cisco.com" target=
=3D"_blank">mamille2@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>


<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>


<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a11c206aaae208904defb3d9f--

From dick.hardt@gmail.com  Wed Jun 12 14:04:14 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9340321F8895 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 14:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[AWL=0.590,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXsb5Ii26Ty0 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 14:04:12 -0700 (PDT)
Received: from mail-bk0-x230.google.com (mail-bk0-x230.google.com [IPv6:2a00:1450:4008:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id A7FE621E8097 for <jose@ietf.org>; Wed, 12 Jun 2013 14:04:09 -0700 (PDT)
Received: by mail-bk0-f48.google.com with SMTP id jf17so4862501bkc.35 for <jose@ietf.org>; Wed, 12 Jun 2013 14:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=isW+PDwYyaeIoKh2KhSzKFqzOa2r3pvjOUIbeP7zRW8=; b=r3IXrZyL5NCBqUFcHunn+ituKuPpVpNS3y2RaZB4GJRgv19S0VL7NzFvFYOe1N0heQ EwB7DeORJJwtBZJgMr7A8HsVZsDqlKwdhIl74PdQsqUNTUACJGn0qkzCvHwS5QMEXtWt emD6PBtadVrZKbk2KEJ2HCGYoIXpQ5i09+IAhrgg1NmfRXaox5E25TYk5oqdx+Cot6lx eoLXmAOGLV0foFdFA+aja2oxg6sfSj/xSxWdHQEcm84Onc7oi/83N+A/t0hsxBn7IJN4 ppxQTZGnpepXspOn4kuNCFTVUmtEHIUw60Y70Qoaojou49bFruCyw/uaD7APaceRQLFY 76tA==
X-Received: by 10.204.70.203 with SMTP id e11mr3507096bkj.16.1371071048654; Wed, 12 Jun 2013 14:04:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.168.12 with HTTP; Wed, 12 Jun 2013 14:03:48 -0700 (PDT)
In-Reply-To: <CAL02cgQ+K=dWnhSa7A4w85psuxOuuf9m09uyChcOZPe17BCizQ@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <CAL02cgQ+K=dWnhSa7A4w85psuxOuuf9m09uyChcOZPe17BCizQ@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Wed, 12 Jun 2013 14:03:48 -0700
Message-ID: <CAD9ie-shVqHGqTt3g0Z7dZVrunQsOF=CJZ+w_etVV_BA9Em2Xg@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=047d7b87450ed152c804defb5aa4
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 21:04:14 -0000

--047d7b87450ed152c804defb5aa4
Content-Type: text/plain; charset=ISO-8859-1

*if* a binary safe representation of JSON becomes popular, then a related
signing specification can be created that deals with the use cases where
this is important

IMHO: The current spec deals with all the real world problems implementors
are wanting to solve or thinking of solving.


On Wed, Jun 12, 2013 at 1:55 PM, Richard Barnes <rlb@ipv.sx> wrote:

> To be clear, I structured my message in two parts for a reason, to
> separate the analysis from the opinion.  I acknowledge that I am but one
> voice here, and I'm increasingly hearing how alone I am :)
>
>
> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> <impartial-analysis>
>> So just to be clear on the trade-off the WG has to make:
>>
>> On the one hand: Breaking every existing JWT implementation in the world
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)
>> </impartial-analysis >
>>
>> <personal-opinion>
>> I have some sympathy with JWT implementors.  It sucks to have to refactor
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a DC
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur the
>> implementation pain now, and get the design right for the long run.  Base64
>> is a hack around JSON; we should build the system so that when we no longer
>> need that hack, it can go away.
>> </personal-opinion>
>>
>> --Richard
>>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:
>>
>>> I did at first find it curious why the cryptographic operations were
>>> over the base64url-enccoded values, but I was also very focused on JWE,
>>> where I think the field separation problem is less of an issue (at least
>>> now).  For JWS, this would certainly cause problems without some manner of
>>> unambiguous field parameterization.
>>>
>>> I will note that unescaped NULL is not valid in JSON, so it could be
>>> used as a separator between the encoded header and the payload.  I do find
>>> it interesting if JOSE could more easily and efficiently support other
>>> encodings.  However, I think that while this is an interesting thought
>>> experiment, it seems we're too far down the path to seriously consider it
>>> unless the current state were shown to be horribly broken.
>>>
>>>
>>> - m&m
>>>
>>> Matt Miller < mamille2@cisco.com >
>>> Cisco Systems, Inc.
>>>
>>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>>> trac+jose@trac.tools.ietf.org> wrote:
>>>
>>> > #23: Make crypto independent of binary encoding (base64)
>>> >
>>> >
>>> > Comment (by michael.jones@microsoft.com):
>>> >
>>> > For both serializations, you already need the base64url encoded
>>> versions
>>> > of the JWS Header and the JWS Payload to preserve them in
>>> transmission, so
>>> > computing them isn't an extra burden.  In the JWS Compact
>>> Serialization,
>>> > you already need the concatenation of the Encoded JWS Header, a period
>>> > character, and the Encoded JWS Payload, so computing that concatenation
>>> > isn't an extra burden.  Given you already have that quantity, computing
>>> > the signature over it is the easiest thing for developers to do, and
>>> it's
>>> > been shown to work well in practice.  There's no compelling reason to
>>> make
>>> > this change.
>>> >
>>> > Even for the JSON Serialization, the only "extra" step that's required
>>> to
>>> > compute the signature is the concatenation with the period character -
>>> to
>>> > prevent shifting of data from one field to the other, as described by
>>> Jim
>>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>>> all -
>>> > it's necessary.  It's also highly advantageous to use exactly the same
>>> > computation for both serializations, which is currently the case.
>>> >
>>> > Since there is no compelling reason to make this change, and since
>>> making
>>> > it could enable the "shifting" problem identified by Jim, it should
>>> not be
>>> > made.
>>> >
>>> > --
>>> >
>>> -------------------------+-------------------------------------------------
>>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>>> >     Type:  defect       |  encryption@tools.ietf.org
>>> > Priority:  major        |      Status:  new
>>> > Component:  json-web-    |   Milestone:
>>> >  encryption             |     Version:
>>> > Severity:  -            |  Resolution:
>>> > Keywords:               |
>>> >
>>> -------------------------+-------------------------------------------------
>>> >
>>> > Ticket URL: <
>>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>>> > jose <http://tools.ietf.org/jose/>
>>> >
>>> > _______________________________________________
>>> > jose mailing list
>>> > jose@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--047d7b87450ed152c804defb5aa4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">*if* a binary safe representation of JSON becomes popular,=
 then a related signing specification can be created that deals with the us=
e cases where this is important<div><br></div><div style>IMHO: The current =
spec deals with all the real world problems implementors are wanting to sol=
ve or thinking of solving.=A0</div>

</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Jun 12, 2013 at 1:55 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">

<div dir=3D"ltr">To be clear, I structured my message in two parts for a re=
ason, to separate the analysis from the opinion. =A0I acknowledge that I am=
 but one voice here, and I&#39;m increasingly hearing how alone I am :)</di=
v>


<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"><div class=3D=
"im">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <span dir=3D"ltr">&lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> w=
rote:<br>

</div><div><div class=3D"h5"><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>&lt;impartial-analysis&gt;</div>So just to be clear o=
n the trade-off the WG has to make:<div><br></div><div>On the one hand: Bre=
aking every existing JWT implementation in the world</div><div>On the other=
 hand: Eternally binding ourselves to base64 encoding, even if binary-safe =
encodings become available (CBOR, MsgPack, etc.)</div>



<div>&lt;/impartial-analysis=A0&gt;<br></div><div><br></div><div>&lt;person=
al-opinion&gt;</div><div>I have some sympathy with JWT implementors. =A0It =
sucks to have to refactor code. =A0But I think we&#39;re literally talking =
about something like a 5-line patch. =A0And early JWT implementors knew or =
should have known (to use a DC phrase) that they were dealing with a draft =
spec. =A0As the W3C editor&#39;s draft template says, in big bold red print=
, &quot;Implementors who are not taking part in the discussions are likely =
to find the specification changing out from under them in incompatible ways=
.&quot;</div>



<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>



<div>&lt;/personal-opinion&gt;<span><font color=3D"#888888"><br></font></sp=
an></div><span><font color=3D"#888888"><div><br></div><div>--Richard</div><=
div><br></div><div><br></div></font></span></div>
<div><div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <span dir=3D"ltr">&lt=
;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com=
</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>




<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>




<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--047d7b87450ed152c804defb5aa4--

From ve7jtb@ve7jtb.com  Wed Jun 12 14:40:45 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033C721E808A for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 14:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ouJQQeM352BD for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 14:40:44 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6706E21E80F1 for <jose@ietf.org>; Wed, 12 Jun 2013 14:40:42 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w57so7434254wes.1 for <jose@ietf.org>; Wed, 12 Jun 2013 14:40:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=I8vqUd3+wYIG3oyBDmTJGYmIOhMVBr/uN2w5NRjQgis=; b=mcA1F7c4RFhIa0NGPukvhccz+h9RTy0Is5SoczH4f1Cp5Lxo3m3t2FXoaM92Cujafj 4B6Rm7z0ep9yci/dQfSYu7U9ePbVIg6PuN49779BWUVl13HyTp9ROfpiWvk+g5NvlcAM 7N1hQou7B3kuD+oAXJ1N39Og3wRWMekiL2RnL78/1/vco5Z48EuNXGZA4Zo6U3xz7BDq opTK8BCfGrX83Seb6e/u09br2wbJB5KtoYpCPRB6L93F/wuyLwKxa2NdSix3ae51V54k 6xfcAKC0zDAxeUzr1FUyogn6ivqDDjUryAPDXGohve4HONsp6221mZXzYO6CMEWalH2m ICVA==
X-Received: by 10.194.91.194 with SMTP id cg2mr11651648wjb.53.1371073242221; Wed, 12 Jun 2013 14:40:42 -0700 (PDT)
Received: from [192.168.0.93] ([87.213.45.202]) by mx.google.com with ESMTPSA id k10sm27530115wia.4.2013.06.12.14.40.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Jun 2013 14:40:40 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_9956CA3D-7280-4E38-9AC4-CF8A828984D4"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
Date: Wed, 12 Jun 2013 23:40:39 +0200
Message-Id: <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQm8DH3/TL4tqbxy/mGv63D9tUExBJx6GcgRCULSpSJgKLDTZVOGcRBUTm0fo9fWmkcwPteS
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Jun 2013 21:40:45 -0000

--Apple-Mail=_9956CA3D-7280-4E38-9AC4-CF8A828984D4
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_45199E5B-98D1-4078-8309-04830232C763"


--Apple-Mail=_45199E5B-98D1-4078-8309-04830232C763
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Independent of the current implementations.   I prefer the current =
base64url encoding of the segments, it is harder for people to get =
wrong.

I have sympathy for the constrained environment people who want BSON =
(binary JSON).   Having a compact binary representation probably makes =
sense for those environments where you can safely transmit binary =
objects.  =20

I however think that alternate binary encodings are future work and what =
we have meets the goal of driving adoption.

If size is the issue then you can always compress a jws on the wire and =
expand it at the other end before validating the signature.

I think changing at this point would be a mistake.

John B.

On 2013-06-12, at 10:23 PM, Richard Barnes <rlb@ipv.sx> wrote:

> <impartial-analysis>
> So just to be clear on the trade-off the WG has to make:
>=20
> On the one hand: Breaking every existing JWT implementation in the =
world
> On the other hand: Eternally binding ourselves to base64 encoding, =
even if binary-safe encodings become available (CBOR, MsgPack, etc.)
> </impartial-analysis >
>=20
> <personal-opinion>
> I have some sympathy with JWT implementors.  It sucks to have to =
refactor code.  But I think we're literally talking about something like =
a 5-line patch.  And early JWT implementors knew or should have known =
(to use a DC phrase) that they were dealing with a draft spec.  As the =
W3C editor's draft template says, in big bold red print, "Implementors =
who are not taking part in the discussions are likely to find the =
specification changing out from under them in incompatible ways."
>=20
> As PHB pointed out in the other thread, it would be nice to use JWS =
and JWE in place of CMS one day, without the base64 hit.  We should =
incur the implementation pain now, and get the design right for the long =
run.  Base64 is a hack around JSON; we should build the system so that =
when we no longer need that hack, it can go away.
> </personal-opinion>
>=20
> --Richard
>=20
>=20
>=20
>=20
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) =
<mamille2@cisco.com> wrote:
> I did at first find it curious why the cryptographic operations were =
over the base64url-enccoded values, but I was also very focused on JWE, =
where I think the field separation problem is less of an issue (at least =
now).  For JWS, this would certainly cause problems without some manner =
of unambiguous field parameterization.
>=20
> I will note that unescaped NULL is not valid in JSON, so it could be =
used as a separator between the encoded header and the payload.  I do =
find it interesting if JOSE could more easily and efficiently support =
other encodings.  However, I think that while this is an interesting =
thought experiment, it seems we're too far down the path to seriously =
consider it unless the current state were shown to be horribly broken.
>=20
>=20
> - m&m
>=20
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.
>=20
> On Jun 11, 2013, at 6:01 PM, jose issue tracker =
<trac+jose@trac.tools.ietf.org> wrote:
>=20
> > #23: Make crypto independent of binary encoding (base64)
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> > For both serializations, you already need the base64url encoded =
versions
> > of the JWS Header and the JWS Payload to preserve them in =
transmission, so
> > computing them isn't an extra burden.  In the JWS Compact =
Serialization,
> > you already need the concatenation of the Encoded JWS Header, a =
period
> > character, and the Encoded JWS Payload, so computing that =
concatenation
> > isn't an extra burden.  Given you already have that quantity, =
computing
> > the signature over it is the easiest thing for developers to do, and =
it's
> > been shown to work well in practice.  There's no compelling reason =
to make
> > this change.
> >
> > Even for the JSON Serialization, the only "extra" step that's =
required to
> > compute the signature is the concatenation with the period character =
- to
> > prevent shifting of data from one field to the other, as described =
by Jim
> > Schaad in the e-mail thread.  So this step isn't actually "extra" at =
all -
> > it's necessary.  It's also highly advantageous to use exactly the =
same
> > computation for both serializations, which is currently the case.
> >
> > Since there is no compelling reason to make this change, and since =
making
> > it could enable the "shifting" problem identified by Jim, it should =
not be
> > made.
> >
> > --
> > =
-------------------------+------------------------------------------------=
-
> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
> >     Type:  defect       |  encryption@tools.ietf.org
> > Priority:  major        |      Status:  new
> > Component:  json-web-    |   Milestone:
> >  encryption             |     Version:
> > Severity:  -            |  Resolution:
> > Keywords:               |
> > =
-------------------------+------------------------------------------------=
-
> >
> > Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> > jose <http://tools.ietf.org/jose/>
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
>=20
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_45199E5B-98D1-4078-8309-04830232C763
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Independent of the current implementations. &nbsp; I prefer the =
current base64url encoding of the segments, it is harder for people to =
get wrong.<div><br></div><div>I have sympathy for the constrained =
environment people who want BSON (binary JSON). &nbsp; Having a compact =
binary representation probably makes sense for those environments where =
you can safely transmit binary objects. =
&nbsp;&nbsp;</div><div><br></div><div>I however think that alternate =
binary encodings are future work and what we have meets the goal of =
driving adoption.</div><div><br></div><div>If size is the issue then you =
can always compress a jws on the wire and expand it at the other end =
before validating the signature.</div><div><br></div><div>I think =
changing at this point would be a mistake.</div><div><br></div><div>John =
B.</div><div><br><div><div>On 2013-06-12, at 10:23 PM, Richard Barnes =
&lt;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr"><div>&lt;impartial-analysis&gt;</div>So just to be clear on =
the trade-off the WG has to make:<div><br></div><div>On the one hand: =
Breaking every existing JWT implementation in the world</div><div>On the =
other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)</div>
=
<div>&lt;/impartial-analysis&nbsp;&gt;<br></div><div><br></div><div>&lt;pe=
rsonal-opinion&gt;</div><div>I have some sympathy with JWT implementors. =
&nbsp;It sucks to have to refactor code. &nbsp;But I think we're =
literally talking about something like a 5-line patch. &nbsp;And early =
JWT implementors knew or should have known (to use a DC phrase) that =
they were dealing with a draft spec. &nbsp;As the W3C editor's draft =
template says, in big bold red print, "Implementors who are not taking =
part in the discussions are likely to find the specification changing =
out from under them in incompatible ways."</div>
<div><br></div><div>As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. =
&nbsp;We should incur the implementation pain now, and get the design =
right for the long run. &nbsp;Base64 is a hack around JSON; we should =
build the system so that when we no longer need that hack, it can go =
away.</div>
=
<div>&lt;/personal-opinion&gt;<br></div><div><br></div><div>--Richard</div=
><div><br></div><div><br></div></div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jun 12, =
2013 at 10:27 AM, Matt Miller (mamille2) <span dir=3D"ltr">&lt;<a =
href=3D"mailto:mamille2@cisco.com" =
target=3D"_blank">mamille2@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">I did at first find it =
curious why the cryptographic operations were over the =
base64url-enccoded values, but I was also very focused on JWE, where I =
think the field separation problem is less of an issue (at least now). =
&nbsp;For JWS, this would certainly cause problems without some manner =
of unambiguous field parameterization.<br>

<br>
I will note that unescaped NULL is not valid in JSON, so it could be =
used as a separator between the encoded header and the payload. &nbsp;I =
do find it interesting if JOSE could more easily and efficiently support =
other encodings. &nbsp;However, I think that while this is an =
interesting thought experiment, it seems we're too far down the path to =
seriously consider it unless the current state were shown to be horribly =
broken.<br>

<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a =
href=3D"mailto:mamille2@cisco.com">mamille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a =
href=3D"mailto:trac%2Bjose@trac.tools.ietf.org">trac+jose@trac.tools.ietf.=
org</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a =
href=3D"mailto:michael.jones@microsoft.com">michael.jones@microsoft.com</a=
>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded =
versions<br>
&gt; of the JWS Header and the JWS Payload to preserve them in =
transmission, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact =
Serialization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a =
period<br>
&gt; character, and the Encoded JWS Payload, so computing that =
concatenation<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, =
computing<br>
&gt; the signature over it is the easiest thing for developers to do, =
and it's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling =
reason to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only "extra" step that's =
required to<br>
&gt; compute the signature is the concatenation with the period =
character - to<br>
&gt; prevent shifting of data from one field to the other, as described =
by Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually =
"extra" at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly =
the same<br>
&gt; computation for both serializations, which is currently the =
case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since =
making<br>
&gt; it could enable the "shifting" problem identified by Jim, it should =
not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; =
-------------------------+------------------------------------------------=
-<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a> &nbsp; =
| &nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-web-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a =
href=3D"mailto:encryption@tools.ietf.org">encryption@tools.ietf.org</a><br=
>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; =
&nbsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp;Resolution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; =
-------------------------+------------------------------------------------=
-<br>
&gt;<br>
&gt; Ticket URL: &lt;<a =
href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" =
target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23#commen=
t:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" =
target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">&gt; =
_______________________________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>jose mailing =
list<br><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/jose<br></blockquote></div><br></div></body></html>=

--Apple-Mail=_45199E5B-98D1-4078-8309-04830232C763--

--Apple-Mail=_9956CA3D-7280-4E38-9AC4-CF8A828984D4
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjEyMjE0MDQwWjAjBgkqhkiG9w0BCQQxFgQUUQ6QpvGH
xjWc5BOvd1MB4GmcTHkwgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAONvyTOo4LAXhFbTzdEbHB/rxGgJiaZV/cK7Q5W1D
hKjkiIwD1h/fOtY1q/cuH1ip7elC7C9U0fU66i+MG7VndoaB1mStP3Ngitir6BzRSHqGGutIykU/
3h2SwApwScIOq9uT/vYm/3k9mQC5QQeZz5aN6b3dRN5zKVVeJXQnBvg69UrqkST1qjiTGsvvqzvw
fcOX5uqRL8o+j6+iCxqWsnpJHzdyy44DcCXUH8UxUy8CuPLqBxXlkJ0LzcTdbP2zQqXV6mvVLed8
YpvzJEsQiaZIl21g/eFwjaVCGH9YQWloqCD/WLES3/xUkY53UV1vxj7FMStLjJMqNQu0+nA33AAA
AAAAAA==

--Apple-Mail=_9956CA3D-7280-4E38-9AC4-CF8A828984D4--

From naa@google.com  Wed Jun 12 17:53:32 2013
Return-Path: <naa@google.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39F9121E805A for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 17:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BaaLfv5wNjzD for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 17:53:27 -0700 (PDT)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id A2CA621E8088 for <jose@ietf.org>; Wed, 12 Jun 2013 17:53:26 -0700 (PDT)
Received: by mail-qe0-f48.google.com with SMTP id 2so6138762qea.35 for <jose@ietf.org>; Wed, 12 Jun 2013 17:53:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=162Q/Cqr3fgnu3LaHqIUsUHymuuDZHj/oIPETaL5zJQ=; b=QYeM8oapwkwusEyFM+Mosu8yeJ6pMURVfUz8dJA9UOhgYgYbj154i7Epc3jFajvx6s BHfvBbm4PkB42Td3X/Uj2gtdMnem/sh2pcTVmf1crHdfU3aBV7WNa/nkSBZ7O8IbjD/l AzBaTu2S6aKCVasZCQK8V82Bn0MBqVvTcVTr70AwlKbTqC6CJBHjQztqpHI3bQoEkZRP JRXY+k9dHC7Y5BgZWyuGUbPyeBFRK88t0ln+cwyjAhJC9pwBPzwLhmO2x6tuep0c4gld PIpKM+VEhrJW7hlrQ0d1S1MzLvTau/jduopzhBIud4IV5spugjOAq8T3z5thSYUb+4Sk iHdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=162Q/Cqr3fgnu3LaHqIUsUHymuuDZHj/oIPETaL5zJQ=; b=I/AEjcLT3NBHmrMXDdHeyq4P+Eh7KOnoOBl4lGFJrdPbdqAeMtdA5S8KYXoA2Cl5XN X1hAblIMJd4jcJcbdeR2Ha0DcIMiFx1s80n41e18PRDbOzII2QFxN5VoiDOt/7IMzmEE Og1ogg4/7EZyz5cixb7NoqIM1v1xVLy25WMBe9T2SzgM3QteYr0WZ2LUx+JtnSYwCizA 8xKhKMaVOwxma/ovS+CFJTY16Ml6fGgcGkaWn8OcKZr4W4xuDsWErpO3u/hqIign27kA PgXrm4uYyWeiXqrtjPluYCs/CoH5//5Q3aYTCQ8D4dFYaVs8uSouz+nF+7BRRO5fcJ91 hw4w==
X-Received: by 10.49.35.132 with SMTP id h4mr27460510qej.29.1371084806029; Wed, 12 Jun 2013 17:53:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.154.69 with HTTP; Wed, 12 Jun 2013 17:53:05 -0700 (PDT)
In-Reply-To: <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com>
From: Naveen Agarwal <naa@google.com>
Date: Wed, 12 Jun 2013 17:53:05 -0700
Message-ID: <CAOKiTbtHGWFA4sdgNWG+KY483gkz5DbxC3jWhTVsn9fNzOb2_w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=047d7b6778a6d21c4204defe8ec6
X-Gm-Message-State: ALoCoQlRS4q6tpB2EJPpTX0xlEXqV0Et9yWv2zPaTiOUNJONVh3HG8FLMnUxILemElLNs8u3nXT6PyePfGLZPtGoT3q9iZNoA57uCapJbJfB2Gs8FKxWoxIvoq1klKkF1NA5u8f8eDoxTYk6ZT2qmSSmHOmWPdtDBRCDTpuJp8MyYWSxmYS1iFGwp7vz0cRX880prp3lsrMl
Cc: "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 00:53:32 -0000

--047d7b6778a6d21c4204defe8ec6
Content-Type: text/plain; charset=ISO-8859-1

But I think we're literally talking about something like a 5-line patch.


Unfortunately there are lot of clients apps that are using jwt and
modifying those apps is not going to be easy.
Whether it is a one line or two line change, it doesn't matter. Breaking
change for something that is working well is bad idea (unless it is for
security reason).


Naveen





On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <rlb@ipv.sx> wrote:

> <impartial-analysis>
> So just to be clear on the trade-off the WG has to make:
>
> On the one hand: Breaking every existing JWT implementation in the world
> On the other hand: Eternally binding ourselves to base64 encoding, even if
> binary-safe encodings become available (CBOR, MsgPack, etc.)
> </impartial-analysis >
>
> <personal-opinion>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base64
> is a hack around JSON; we should build the system so that when we no longer
> need that hack, it can go away.
> </personal-opinion>
>
> --Richard
>
>
>
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:
>
>> I did at first find it curious why the cryptographic operations were over
>> the base64url-enccoded values, but I was also very focused on JWE, where I
>> think the field separation problem is less of an issue (at least now).  For
>> JWS, this would certainly cause problems without some manner of unambiguous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be used
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider it
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versions
>> > of the JWS Header and the JWS Payload to preserve them in transmission,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serialization,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenation
>> > isn't an extra burden.  Given you already have that quantity, computing
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should not
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+-------------------------------------------------
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+-------------------------------------------------
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose
>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--047d7b6778a6d21c4204defe8ec6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><span style=3D"font-fa=
mily:arial,sans-serif;font-size:12.666666984558105px">But I think we&#39;re=
 literally talking about something like a 5-line patch.=A0</span></blockquo=
te>

<div><br></div><div>Unfortunately there are lot of clients apps that are us=
ing jwt and modifying those apps is not going to be easy.=A0</div><div>Whet=
her it is a one line or two line change, it doesn&#39;t matter. Breaking ch=
ange for something that is working well is bad idea (unless it is for secur=
ity reason).</div>

<div><br></div><div><br></div><div>Naveen</div><div><br></div><div><br></di=
v><div>=A0</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <span dir=3D"ltr">=
&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</spa=
n> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>&lt;impartial-analysis=
&gt;</div>So just to be clear on the trade-off the WG has to make:<div><br>=
</div>

<div>On the one hand: Breaking every existing JWT implementation in the wor=
ld</div><div>On the other hand: Eternally binding ourselves to base64 encod=
ing, even if binary-safe encodings become available (CBOR, MsgPack, etc.)</=
div>


<div>&lt;/impartial-analysis=A0&gt;<br></div><div><br></div><div>&lt;person=
al-opinion&gt;</div><div>I have some sympathy with JWT implementors. =A0It =
sucks to have to refactor code. =A0But I think we&#39;re literally talking =
about something like a 5-line patch. =A0And early JWT implementors knew or =
should have known (to use a DC phrase) that they were dealing with a draft =
spec. =A0As the W3C editor&#39;s draft template says, in big bold red print=
, &quot;Implementors who are not taking part in the discussions are likely =
to find the specification changing out from under them in incompatible ways=
.&quot;</div>


<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>


<div>&lt;/personal-opinion&gt;<span class=3D"HOEnZb"><font color=3D"#888888=
"><br></font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><d=
iv><br></div><div>--Richard</div><div><br></div><div><br></div></font></spa=
n></div>

<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (m=
amille2) <span dir=3D"ltr">&lt;<a href=3D"mailto:mamille2@cisco.com" target=
=3D"_blank">mamille2@cisco.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>



<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>



<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--047d7b6778a6d21c4204defe8ec6--

From hallam@gmail.com  Wed Jun 12 20:51:25 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9925C21E8056 for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 20:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4yrT7HT1zPq for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 20:51:25 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A61F121E804D for <jose@ietf.org>; Wed, 12 Jun 2013 20:51:24 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id m46so7540670wev.16 for <jose@ietf.org>; Wed, 12 Jun 2013 20:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yef58B0Erxzcc5DEPkuGZMcPnuSHxBRIBfkKtC42hNQ=; b=f8zEh5YW1OxV6r7qQxFtsLsWYj5GT2s90JrK8vZcUuEnLKLmJytoQ47bQJhCON8PsT 768CYvOod4mVRXulf2mqulBuTKuLyvxvdPt6t+z66Lkc7xJhzsseMbjtaPhMqbs/4OAl bR/yJlgTJm8Y8ALPrFTxZp8HFBxTTZiqpT+P/xWDJyL3Mdptn7fwKZlR+haUVdexSlHS 2R+ZKiKJ8inZ1e4X0vLDxx+eW9PKHoQWZ0zV6YrIzxNLVXSGQrMYA85yGpcCOuncrDjx s+XTmoYHuVf1ZobowQkZljxDi1jOfqUigZGu/TOGrN7odkH2ojO/KO6WxlLudO/N/2df fqvQ==
MIME-Version: 1.0
X-Received: by 10.180.39.136 with SMTP id p8mr78020wik.11.1371095483802; Wed, 12 Jun 2013 20:51:23 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Wed, 12 Jun 2013 20:51:23 -0700 (PDT)
In-Reply-To: <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com>
Date: Wed, 12 Jun 2013 23:51:23 -0400
Message-ID: <CAMm+Lwh0w5bxnvWWdjeQQfCYuMoz73utrg=fUG_HLdtaB3npzw@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Bradley <ve7jtb@ve7jtb.com>
Content-Type: multipart/alternative; boundary=001a11c366d643ed4004df010b3a
Cc: Richard Barnes <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 03:51:25 -0000

--001a11c366d643ed4004df010b3a
Content-Type: text/plain; charset=ISO-8859-1

I also prefer to process bit as they appear on the wire.

A binary encoding is going to need different code for the parser/encoder. I
don't see a problem tweaking aspects of JOSE that were bound to the
particular JSON encoding.

While it would be nice in theory to be able to transform between encodings
and have signatures still work, I don't think that is possible except in
the very specific case where all that is being done is base64 encoding
binary blobs.

I don't believe that any canonicalization scheme has proved to be reliable
enough in practice to actually provide the alleged value. There seem to be
more corner cases than anyone imagines possible.


I certainly would not want to break JWT for the sake of an encoding that
JWT is not using.

--001a11c366d643ed4004df010b3a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I also prefer to process bit as they appear on the wire.<d=
iv><br></div><div style>A binary encoding is going to need different code f=
or the parser/encoder. I don&#39;t see a problem tweaking aspects of JOSE t=
hat were bound to the particular JSON encoding.</div>
<div style><br></div><div style>While it would be nice in theory to be able=
 to transform between encodings and have signatures still work, I don&#39;t=
 think that is possible except in the very specific case where all that is =
being done is base64 encoding binary blobs.</div>
<div style><br></div><div style>I don&#39;t believe that any canonicalizati=
on scheme has proved to be reliable enough in practice to actually provide =
the alleged value. There seem to be more corner cases than anyone imagines =
possible.</div>
<div style><br></div><div style><br></div><div style>I certainly would not =
want to break JWT for the sake of an encoding that JWT is not using.</div><=
div style><br></div></div>

--001a11c366d643ed4004df010b3a--

From ludwig@sics.se  Thu Jun 13 00:38:22 2013
Return-Path: <ludwig@sics.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E36D21F9A1D for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 00:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7Wltw1UGfsf for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 00:38:17 -0700 (PDT)
Received: from fsmsg2.sics.se (fsmsg2.sics.se [IPv6:2001:6b0:3a:1:250:56ff:fea9:52ad]) by ietfa.amsl.com (Postfix) with ESMTP id B8E8D21F9A29 for <jose@ietf.org>; Thu, 13 Jun 2013 00:38:11 -0700 (PDT)
Received: from pps.filterd (fsmsg2 [127.0.0.1]) by fsmsg2.sics.se (8.14.5/8.14.5) with SMTP id r5D7XikQ004085; Thu, 13 Jun 2013 09:38:05 +0200
Received: from letter.sics.se (letter.sics.se [193.10.64.6]) by fsmsg2.sics.se with ESMTP id 1cwcj146dw-1; Thu, 13 Jun 2013 09:38:05 +0200
Received: from [192.168.0.103] (unknown [85.235.11.178]) (Authenticated sender: ludwig@sics.se) by letter.sics.se (Postfix) with ESMTPSA id 387E1400E2; Thu, 13 Jun 2013 09:38:05 +0200 (CEST)
Message-ID: <1371109077.2485.5.camel@ubuntu.ubuntu-domain>
From: Ludwig Seitz <ludwig@sics.se>
To: John Bradley <ve7jtb@ve7jtb.com>
Date: Thu, 13 Jun 2013 09:37:57 +0200
In-Reply-To: <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com>
Organization: SICS AB
Content-Type: multipart/signed; micalg="sha256"; protocol="application/x-pkcs7-signature"; boundary="=-KXk7d+YjsxQmFNu1xJXZ"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Mime-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-06-13_03:2013-06-12, 2013-06-13, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1211240000 definitions=main-1306130005
Cc: Richard Barnes <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 07:38:22 -0000

--=-KXk7d+YjsxQmFNu1xJXZ
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 2013-06-12 at 23:40 +0200, John Bradley wrote:
> Independent of the current implementations.   I prefer the current
> base64url encoding of the segments, it is harder for people to get
> wrong.
>=20
>=20
> I have sympathy for the constrained environment people who want BSON
> (binary JSON).   Having a compact binary representation probably makes
> sense for those environments where you can safely transmit binary
> objects.  =20
>=20
>=20
> I however think that alternate binary encodings are future work and
> what we have meets the goal of driving adoption.
>=20
>=20
> If size is the issue then you can always compress a jws on the wire
> and expand it at the other end before validating the signature.

If size is an issue on the wire, then chances are that it is also an
issue on the device, so just compressing and expanding may not be a good
solution. Note that in a constrained environment even some of the
processing devices have limited RAM memory and space for (decompression)
libraries and such.

I very much subscribe to your previous statement though: It's future
work (but we shouldn't forget it).


/Ludwig

--=20
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2=20
Scheelev=C3=A4gen 17=20
SE-223 70 Lund

Phone +46(0)70-349 92 51
http://www.sics.se

--=-KXk7d+YjsxQmFNu1xJXZ
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEnAw
ggYYMIIFAKADAgECAgMFtYswDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQTAeFw0xMzAxMTUwMjA1MDZaFw0xNDAxMTUxNDM3NDhaMDgxFzAVBgNVBAMMDmx1ZHdpZ0Bz
aWNzLnNlMR0wGwYJKoZIhvcNAQkBFg5sdWR3aWdAc2ljcy5zZTCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBAKpuRavr2swCQsYS7KxOsmeBXI39thxAjIYaB0AFVjLpOtVJxQMYoip7Bm9o
ka8PXxQ9mWT/lVSoqI7jGjc5Z8q1C4fOFMCYZpJugG9qJS0OMV2ajQ7xXu3YzLTDIKg/BK39+Vri
vJq0Y6hz1/4pgxMOFG+l7y+fq54QSkKMwpuRaCBznKJeRxGwDvheF2QN6YEBclFqVhpciDGd52vX
5AgbKbqVmevMrcrcYAdKaKm6iTEmbYHum5D/4GaOnnZ2wMnY5EpKhxxm6SszCVSNdk8iZSUze9GY
PzheBDIHMDdLZib6zaoR96F5ZCpE1pPeKIz/DCd3kL+nXpe5gdbSXLsCAwEAAaOCAtQwggLQMAkG
A1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV
HQ4EFgQUwDv6gyc7uSHK/QBVIZiN86hjKW4wHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4
UYIwGQYDVR0RBBIwEIEObHVkd2lnQHNpY3Muc2UwggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQB
gbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBk
ZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIB
ARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEg
VmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFu
Y2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVs
eWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0
cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZo
dHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYD
VR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBCwUAA4IBAQA4bagj
yL3PLei2tbMELKOVOxRdyLObcVq0Fj83LbSTMj6NS83TU/4xxChfd5zqoipudDSEpgxZAUsSjk02
DxSeLYYBXE2X/iue7nL8S/3PjC49z5ZgjDZrXIgmvIMaZXWM+GqG+wk9NikGb1/shlJjk3R5KC3f
RWsUatHouNxAMYxiLFO75YmgKCgkjtKUbHbUqzmDVd30nWQesXfCgYwCbAvD/0NgX3jE+fnyT71+
aX4/IfqshpCQj8dkR4ZH+bUiK5zgKGJL61GRZNSScR/r9Sq19kEQrt38ey/Q90tUDUgg93d5w3DN
rF3bRoOvyspwbcN9TuGKkFoFPV0KfjaGMIIGGDCCBQCgAwIBAgIDBbWLMA0GCSqGSIb3DQEBCwUA
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl
IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ
cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwMTE1MDIwNTA2WhcNMTQwMTE1MTQz
NzQ4WjA4MRcwFQYDVQQDDA5sdWR3aWdAc2ljcy5zZTEdMBsGCSqGSIb3DQEJARYObHVkd2lnQHNp
Y3Muc2UwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCqbkWr69rMAkLGEuysTrJngVyN
/bYcQIyGGgdABVYy6TrVScUDGKIqewZvaJGvD18UPZlk/5VUqKiO4xo3OWfKtQuHzhTAmGaSboBv
aiUtDjFdmo0O8V7t2My0wyCoPwSt/fla4ryatGOoc9f+KYMTDhRvpe8vn6ueEEpCjMKbkWggc5yi
XkcRsA74XhdkDemBAXJRalYaXIgxnedr1+QIGym6lZnrzK3K3GAHSmipuokxJm2B7puQ/+Bmjp52
dsDJ2ORKSoccZukrMwlUjXZPImUlM3vRmD84XgQyBzA3S2Ym+s2qEfeheWQqRNaT3iiM/wwnd5C/
p16XuYHW0ly7AgMBAAGjggLUMIIC0DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAU
BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFMA7+oMnO7khyv0AVSGYjfOoYyluMB8GA1Ud
IwQYMBaAFFNy7ZKc4NrLAVx8fpY1TvLUuFGCMBkGA1UdEQQSMBCBDmx1ZHdpZ0BzaWNzLnNlMIIB
TAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENl
cnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQg
YWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBT
dGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3Nl
IGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUF
BwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3Mx
L2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3Vi
LmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
LzANBgkqhkiG9w0BAQsFAAOCAQEAOG2oI8i9zy3otrWzBCyjlTsUXcizm3FatBY/Ny20kzI+jUvN
01P+McQoX3ec6qIqbnQ0hKYMWQFLEo5NNg8Uni2GAVxNl/4rnu5y/Ev9z4wuPc+WYIw2a1yIJryD
GmV1jPhqhvsJPTYpBm9f7IZSY5N0eSgt30VrFGrR6LjcQDGMYixTu+WJoCgoJI7SlGx21Ks5g1Xd
9J1kHrF3woGMAmwLw/9DYF94xPn58k+9fml+PyH6rIaQkI/HZEeGR/m1Iiuc4ChiS+tRkWTUknEf
6/UqtfZBEK7d/Hsv0PdLVA1IIPd3ecNwzaxd20aDr8rKcG3DfU7hipBaBT1dCn42hjCCBjQwggQc
oAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNV
BAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3
MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENv
bSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xC
GhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P
3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2Ub
FqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2
JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGp
MA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6W
NU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgw
JwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3Rh
cnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhj
jF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4
n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkU
CTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6h
xHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5X
MEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b
1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLp
XDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/p
Ny8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOg
SF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEw
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCWCGSAFlAwQCAQUAoIIBuzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MTMwNzM3NTdaMC8G
CSqGSIb3DQEJBDEiBCBRBqNi/f04GHSXrUbIPqk1yh22+1wI6wL8jXO8pyKKIjCBpQYJKwYBBAGC
NxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwW1izCBpwYLKoZIhvcNAQkQ
AgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBbWLMA0GCSqGSIb3DQEBAQUA
BIIBAIqMztqVgd0i0hOIMpx14lOAWLOaFzPKQS3whGvsv7dGusXRv42rf/RnyLrJ6SbLXeMYwE82
GuZ1KgtWYComeNcIEk6SW9rT5KWJlOH+Z1EdV3oo/FGk4R4mZxRIOWUy83C/F8NxNTEedf8fNaJk
uZMNlLZBz63764/yhtcSyu3zjUoGXWbz3xE4qP7PJH3fXQeBCYamFtNRFfsUXkN2/Q2MsTAxlVIJ
YX9MGiGp7tr0G07T2yoCemmO09ahGkzaOt6/hTHZyLdHoyHV8W1I/Ysb3RVNz9XCW19y5KK+QJeP
L8VSFzhdV+bDRLAfu8cpOv/5BNALU8VnmcHsFS9dp3gAAAAAAAA=


--=-KXk7d+YjsxQmFNu1xJXZ--


From ve7jtb@ve7jtb.com  Thu Jun 13 01:49:57 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D77021F8F33 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 01:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOFe0RI+QT2K for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 01:49:56 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2111F21F8EF2 for <jose@ietf.org>; Thu, 13 Jun 2013 01:49:55 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id ey16so639135wid.1 for <jose@ietf.org>; Thu, 13 Jun 2013 01:49:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=VyIC8uks+w8gLr+W9gosYwqW5jl6Gy6FROBszn5iY8s=; b=RsbiAz2PyDQfvMY89c+Czut/qax3eMjgaUzHDKi5rAmbCV3pZkFz/w+ANVsnqpYxSq iPjKXhfYzuOqB8O9MzUQMWswzgMHGOcUw8pUAFEU164OFk/lc52EgfjLcDeGxCXveaj9 RHgn0hKd2LXd2vzF3kHfDkZVi7Plu8h5CHXOz6Tz/jQUsmKxOPc5CjoxusnTpiWmJEFH AX+0ALrbAhTZv36XUIX5PbXPmsuI8WmvR+rRQgKWv6KlEr5OnJKcs9Zbb9ee3a/uylvx 10PXLEOwNauhAEdY+oWQwfwdRNAhdYNDIVcj2IQTNF3VsIZiqwHA8mGkABHDr+GZ2PTX JboQ==
X-Received: by 10.180.107.163 with SMTP id hd3mr6764649wib.8.1371113395016; Thu, 13 Jun 2013 01:49:55 -0700 (PDT)
Received: from [10.147.129.63] ([188.207.110.177]) by mx.google.com with ESMTPSA id k10sm29772159wia.4.2013.06.13.01.49.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Jun 2013 01:49:54 -0700 (PDT)
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <F337BFF0-4194-405F-ACDA-644B253BA24E@ve7jtb.com> <1371109077.2485.5.camel@ubuntu.ubuntu-domain>
Mime-Version: 1.0 (1.0)
In-Reply-To: <1371109077.2485.5.camel@ubuntu.ubuntu-domain>
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-FCFC1785-D8B2-4B81-B924-348BDA74FB95; protocol="application/pkcs7-signature"
Content-Transfer-Encoding: 7bit
Message-Id: <2DBFB9B6-85DA-43AA-A0BA-16C5D745425F@ve7jtb.com>
X-Mailer: iPhone Mail (10B329)
From: John Bradley <ve7jtb@ve7jtb.com>
Date: Thu, 13 Jun 2013 10:49:53 +0200
To: Ludwig Seitz <ludwig@sics.se>
X-Gm-Message-State: ALoCoQmmWao8CqsbYxD1P14xy/tWPwgQ+84P/tAmwp3zUoE1q16uRHqLQ6Qg1fCS0cCnj4DpMvnY
Cc: Richard Barnes <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 08:49:57 -0000

--Apple-Mail-FCFC1785-D8B2-4B81-B924-348BDA74FB95
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Agreed compressing and expanding on constrained devices is not ideal.=20

Though I understand people are doing that in some cases to fit in a single p=
acket.  Doing a good job for those environments is however future work and p=
robably requires BSON or some other extension.=20

John B.=20
Sent from my iPhone

On 2013-06-13, at 9:37 AM, Ludwig Seitz <ludwig@sics.se> wrote:

> On Wed, 2013-06-12 at 23:40 +0200, John Bradley wrote:
>> Independent of the current implementations.   I prefer the current
>> base64url encoding of the segments, it is harder for people to get
>> wrong.
>>=20
>>=20
>> I have sympathy for the constrained environment people who want BSON
>> (binary JSON).   Having a compact binary representation probably makes
>> sense for those environments where you can safely transmit binary
>> objects.  =20
>>=20
>>=20
>> I however think that alternate binary encodings are future work and
>> what we have meets the goal of driving adoption.
>>=20
>>=20
>> If size is the issue then you can always compress a jws on the wire
>> and expand it at the other end before validating the signature.
>=20
> If size is an issue on the wire, then chances are that it is also an
> issue on the device, so just compressing and expanding may not be a good
> solution. Note that in a constrained environment even some of the
> processing devices have limited RAM memory and space for (decompression)
> libraries and such.
>=20
> I very much subscribe to your previous statement though: It's future
> work (but we shouldn't forget it).
>=20
>=20
> /Ludwig
>=20
> --=20
> Ludwig Seitz, PhD
> SICS Swedish ICT AB
> Ideon Science Park
> Building Beta 2=20
> Scheelev=C3=A4gen 17=20
> SE-223 70 Lund
>=20
> Phone +46(0)70-349 92 51
> http://www.sics.se
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

--Apple-Mail-FCFC1785-D8B2-4B81-B924-348BDA74FB95
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIHuTCCB7Uw
ggadoAMCAQICAh5cMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew
HhcNMTIwMzE4MDQzMjQ4WhcNMTQwMzE5MTEwNzMyWjCBmzEZMBcGA1UEDRMQR3JUTTZMUzdYMzU3
NzhzOTELMAkGA1UEBhMCQ0wxIjAgBgNVBAgTGU1ldHJvcG9saXRhbmEgZGUgU2FudGlhZ28xFjAU
BgNVBAcTDUlzbGEgZGUgTWFpcG8xFTATBgNVBAMTDEpvaG4gQnJhZGxleTEeMBwGCSqGSIb3DQEJ
ARYPamJyYWRsZXlAbWUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAskrlBI93
rBTLOQGSwIT6co6dAw/rwDPrRXl6/F2oc4KDn+QN6CdFeHo08H846VJS9CDjLKvnK9jbxxs4wYqe
nKdPb3jgzt8oc7b9ZXtWkOgsxgMf6dBZ/IPm4lWBpCbSr3seDGDXEpiE2lTZXno7c25OguR4E6Qa
hcpHABZjeEWK65mMH25gmoRf5MY1k3quu5y+FCYCHE2iwU5jzq+mI3HmG59+UMFLx1fjV+zTslRw
26cQDC/uepwjeYSp8S26hfWipVWwQj4js/C7RoPtvt2iyeU+LSH81jG4wlAWntiOG1WtoXUuXWSc
ExhciKeKWCnemy9qqmxRfJqBROeGlQIDAQABo4IEDjCCBAowCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBQ/A7/CxKEnzpqmZlLz
9iaQMy24eTAfBgNVHSMEGDAWgBSuVYNv7DHKufcd+q9rMfPIHeOsuzB+BgNVHREEdzB1gQ9qYnJh
ZGxleUBtZS5jb22BD2picmFkbGV5QG1lLmNvbYEQamJyYWRsZXlAbWFjLmNvbYERdmU3anRiQHZl
N2p0Yi5jb22BE2picmFkbGV5QHdpbmdhYS5jb22BF2pvaG4uYnJhZGxleUB3aW5nYWEuY29tMIIC
IQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRp
ZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNj
b3JkaW5nIHRvIHRoZSBDbGFzcyAyIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcC
AjCBjzAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkg
YW5kIHdhcnJhbnRpZXMgYXJlIGxpbWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRh
dGlvbnMiIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUyLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYB
BQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MyL2NsaWVudC9jYTBCBggr
BgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMi5jbGllbnQu
Y2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEAEcfD4PmHrX+W3zaP/KsR4gwLAL0UTaMz14SIng6a9F3kb8ZDbTUneS9ubgpqeJQP2IFc
0U5gQnJ3XeCH6p9I88mvm1NqKQw8WvfglS0aIS19vfpTgXJSPdIO2JJPRqaBtXf3zkdXJwckX9/d
NMrLGeGvaFT9fUNdQdHU4BI1pVUpgKr796T7LTc/ERfH8iFp1+CmdVkJ6Y2iJdWUp4h17XmbxbIT
0CdS4SSk/VW8LFsn/mVz6hB73VthwjGsIku54Wp4pRuq1KX+pATnRk3pHRa1z3mxJMmq7OEXENcC
Vm+bAnyUrYbUilNS9UVTYS8/3dVsKiNupBaOZO+vOgJqVDGCA2wwggNoAgEBMIGTMIGMMQswCQYD
VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwg
Q2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IElu
dGVybWVkaWF0ZSBDbGllbnQgQ0ECAh5cMAkGBSsOAwIaBQCgggGtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDYxMzA4NDk1NFowIwYJKoZIhvcNAQkEMRYEFJZV
dBBBpoQFrEmBTgK28vibIMj1MIGkBgkrBgEEAYI3EAQxgZYwgZMwgYwxCzAJBgNVBAYTAklMMRYw
FAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0
ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRl
IENsaWVudCBDQQICHlwwgaYGCyqGSIb3DQEJEAILMYGWoIGTMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUg
U2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBD
bGllbnQgQ0ECAh5cMA0GCSqGSIb3DQEBAQUABIIBAHRjLpsz0QrhpV1Y5v3Sikchlgp8ZvgzknIB
kz+aDjc7VneQ8fBs1CTjMN5YKGUHLAnAurQmhkN62e3Of4JqK4X1pP8JJOWJXfOyzJ3mGcxCGrnN
3i/hjuU1ZwG/AAT8qQZOFJ+YvvEEvKQmYLFRj32mWXkYych/ek2hysJztVrDrUZubH/7LBiEED68
atrVhtaI9WB6NZCue1MJYPo/92lDHCNtqLWCvi/xdrzLTsPDmi6FmRgrnwalGRZj/sgOxbLDCc+v
Wrrd0soht/x3yXqM1QnrJe36IBdQG3IHDWx0syd3jNfaiu7zDFEc/xQ21kvwnOoLmu96DpPyYbZ8
9TAAAAAAAAA=

--Apple-Mail-FCFC1785-D8B2-4B81-B924-348BDA74FB95--

From bcampbell@pingidentity.com  Thu Jun 13 07:02:19 2013
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A092E21F894E for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level: 
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0f0kY8SJ8zZm for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:02:01 -0700 (PDT)
Received: from na3sys009aog132.obsmtp.com (na3sys009aog132.obsmtp.com [74.125.149.250]) by ietfa.amsl.com (Postfix) with ESMTP id 05CF121F901F for <jose@ietf.org>; Thu, 13 Jun 2013 07:01:34 -0700 (PDT)
Received: from mail-ea0-f171.google.com ([209.85.215.171]) (using TLSv1) by na3sys009aob132.postini.com ([74.125.148.12]) with SMTP ID DSNKUbnQuh6R1BC+UC5CnoU6jik3xOHOwCAM@postini.com; Thu, 13 Jun 2013 07:01:47 PDT
Received: by mail-ea0-f171.google.com with SMTP id m14so7860445eaj.30 for <jose@ietf.org>; Thu, 13 Jun 2013 07:01:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=YnF+x95Pqlap6KMA9Ad3D+IA2fFicJ9baota2wBH6LI=; b=NbB7MPJW3LhEjHC5uQ1RU4PkX+l6FX4MQjR+iWgK9WtZzkwzYXa2y/7AB/o/4TZ8po PJVNDV0XXL2vjeJWREHQB4os/e8H5lsvAFe/0XipafPqnklV/reJdASc6DmmXCmJACh8 3Od74crM5g1gWhXgsyFZ/thdsIj0aCSRnzH9pGh3VNYPmo7aMmtVCroO2jfCWu8nA4xU x2GMCHEw4VC28Z8J+dIurYl8qLI3qI7OVNztdk3o6hqB/6DjMcucqszdubBoEP134f0K r5tCwxSvaeF5GK8hv53j8Nn82WYX1Y1W5FUEpTqPtWF7u5l2Sr/vxXd1W77k7BauUosH txZw==
X-Received: by 10.15.76.71 with SMTP id m47mr1347705eey.70.1371132089080; Thu, 13 Jun 2013 07:01:29 -0700 (PDT)
X-Received: by 10.15.76.71 with SMTP id m47mr1347688eey.70.1371132088934; Thu, 13 Jun 2013 07:01:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.134.13 with HTTP; Thu, 13 Jun 2013 07:00:58 -0700 (PDT)
In-Reply-To: <CAOKiTbtHGWFA4sdgNWG+KY483gkz5DbxC3jWhTVsn9fNzOb2_w@mail.gmail.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <CAOKiTbtHGWFA4sdgNWG+KY483gkz5DbxC3jWhTVsn9fNzOb2_w@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 13 Jun 2013 08:00:58 -0600
Message-ID: <CA+k3eCR5kY7run93HHti9+VxVaX6XErS380Ks2Ko6qDD_9jFRA@mail.gmail.com>
To: Naveen Agarwal <naa@google.com>
Content-Type: multipart/alternative; boundary=001a11c1ad341a17ed04df0991b9
X-Gm-Message-State: ALoCoQkGmIEzdgWiBZvXnRzxZlS1a1qRcMpZwaYIgZU6JCDGE7564ThjB1tDEjJa7uAWAMi0AzLqabhKn+poxmZ9DaOAccGFxTy5Z/h8kfue9e/5AxLHxjcmj4r95JRUq88gwxyjPW3p
Cc: Richard Barnes <rlb@ipv.sx>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.com>, jose issue tracker <trac+jose@trac.tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:02:19 -0000

--001a11c1ad341a17ed04df0991b9
Content-Type: text/plain; charset=ISO-8859-1

Big +1 to Naveen's comment here. It's not about the size of the code change
at all. It's about the impact to widely deployed production code that
cannot be simultaneously updated.


On Wed, Jun 12, 2013 at 6:53 PM, Naveen Agarwal <naa@google.com> wrote:

>
>
> But I think we're literally talking about something like a 5-line patch.
>
>
> Unfortunately there are lot of clients apps that are using jwt and
> modifying those apps is not going to be easy.
> Whether it is a one line or two line change, it doesn't matter. Breaking
> change for something that is working well is bad idea (unless it is for
> security reason).
>
>
> Naveen
>
>
>
>
>
> On Wed, Jun 12, 2013 at 1:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> <impartial-analysis>
>> So just to be clear on the trade-off the WG has to make:
>>
>> On the one hand: Breaking every existing JWT implementation in the world
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)
>> </impartial-analysis >
>>
>> <personal-opinion>
>> I have some sympathy with JWT implementors.  It sucks to have to refactor
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a DC
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur the
>> implementation pain now, and get the design right for the long run.  Base64
>> is a hack around JSON; we should build the system so that when we no longer
>> need that hack, it can go away.
>> </personal-opinion>
>>
>> --Richard
>>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:
>>
>>> I did at first find it curious why the cryptographic operations were
>>> over the base64url-enccoded values, but I was also very focused on JWE,
>>> where I think the field separation problem is less of an issue (at least
>>> now).  For JWS, this would certainly cause problems without some manner of
>>> unambiguous field parameterization.
>>>
>>> I will note that unescaped NULL is not valid in JSON, so it could be
>>> used as a separator between the encoded header and the payload.  I do find
>>> it interesting if JOSE could more easily and efficiently support other
>>> encodings.  However, I think that while this is an interesting thought
>>> experiment, it seems we're too far down the path to seriously consider it
>>> unless the current state were shown to be horribly broken.
>>>
>>>
>>> - m&m
>>>
>>> Matt Miller < mamille2@cisco.com >
>>> Cisco Systems, Inc.
>>>
>>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>>> trac+jose@trac.tools.ietf.org> wrote:
>>>
>>> > #23: Make crypto independent of binary encoding (base64)
>>> >
>>> >
>>> > Comment (by michael.jones@microsoft.com):
>>> >
>>> > For both serializations, you already need the base64url encoded
>>> versions
>>> > of the JWS Header and the JWS Payload to preserve them in
>>> transmission, so
>>> > computing them isn't an extra burden.  In the JWS Compact
>>> Serialization,
>>> > you already need the concatenation of the Encoded JWS Header, a period
>>> > character, and the Encoded JWS Payload, so computing that concatenation
>>> > isn't an extra burden.  Given you already have that quantity, computing
>>> > the signature over it is the easiest thing for developers to do, and
>>> it's
>>> > been shown to work well in practice.  There's no compelling reason to
>>> make
>>> > this change.
>>> >
>>> > Even for the JSON Serialization, the only "extra" step that's required
>>> to
>>> > compute the signature is the concatenation with the period character -
>>> to
>>> > prevent shifting of data from one field to the other, as described by
>>> Jim
>>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>>> all -
>>> > it's necessary.  It's also highly advantageous to use exactly the same
>>> > computation for both serializations, which is currently the case.
>>> >
>>> > Since there is no compelling reason to make this change, and since
>>> making
>>> > it could enable the "shifting" problem identified by Jim, it should
>>> not be
>>> > made.
>>> >
>>> > --
>>> >
>>> -------------------------+-------------------------------------------------
>>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>>> >     Type:  defect       |  encryption@tools.ietf.org
>>> > Priority:  major        |      Status:  new
>>> > Component:  json-web-    |   Milestone:
>>> >  encryption             |     Version:
>>> > Severity:  -            |  Resolution:
>>> > Keywords:               |
>>> >
>>> -------------------------+-------------------------------------------------
>>> >
>>> > Ticket URL: <
>>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>>> > jose <http://tools.ietf.org/jose/>
>>> >
>>> > _______________________________________________
>>> > jose mailing list
>>> > jose@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--001a11c1ad341a17ed04df0991b9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Big +1 to Naveen&#39;s comment here. It&#39;s not about th=
e size of the code change at all. It&#39;s about the impact to widely deplo=
yed production code that cannot be simultaneously updated.<br></div><div cl=
ass=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">On Wed, Jun 12, 2013 at 6:53 PM, Naveen =
Agarwal <span dir=3D"ltr">&lt;<a href=3D"mailto:naa@google.com" target=3D"_=
blank">naa@google.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">

<div dir=3D"ltr"><div class=3D"im"><br><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><spa=
n style=3D"font-family:arial,sans-serif;font-size:12.666666984558105px">But=
 I think we&#39;re literally talking about something like a 5-line patch.=
=A0</span></blockquote>



<div><br></div></div><div>Unfortunately there are lot of clients apps that =
are using jwt and modifying those apps is not going to be easy.=A0</div><di=
v>Whether it is a one line or two line change, it doesn&#39;t matter. Break=
ing change for something that is working well is bad idea (unless it is for=
 security reason).</div>

<span class=3D"HOEnZb"><font color=3D"#888888">

<div><br></div><div><br></div><div>Naveen</div><div><br></div><div><br></di=
v><div>=A0</div></font></span></div><div class=3D"HOEnZb"><div class=3D"h5"=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jun =
12, 2013 at 1:23 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto=
:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>&lt;impartial-analysis=
&gt;</div>So just to be clear on the trade-off the WG has to make:<div><br>=
</div>



<div>On the one hand: Breaking every existing JWT implementation in the wor=
ld</div><div>On the other hand: Eternally binding ourselves to base64 encod=
ing, even if binary-safe encodings become available (CBOR, MsgPack, etc.)</=
div>




<div>&lt;/impartial-analysis=A0&gt;<br></div><div><br></div><div>&lt;person=
al-opinion&gt;</div><div>I have some sympathy with JWT implementors. =A0It =
sucks to have to refactor code. =A0But I think we&#39;re literally talking =
about something like a 5-line patch. =A0And early JWT implementors knew or =
should have known (to use a DC phrase) that they were dealing with a draft =
spec. =A0As the W3C editor&#39;s draft template says, in big bold red print=
, &quot;Implementors who are not taking part in the discussions are likely =
to find the specification changing out from under them in incompatible ways=
.&quot;</div>




<div><br></div><div>As PHB pointed out in the other thread, it would be nic=
e to use JWS and JWE in place of CMS one day, without the base64 hit. =A0We=
 should incur the implementation pain now, and get the design right for the=
 long run. =A0Base64 is a hack around JSON; we should build the system so t=
hat when we no longer need that hack, it can go away.</div>




<div>&lt;/personal-opinion&gt;<span><font color=3D"#888888"><br></font></sp=
an></div><span><font color=3D"#888888"><div><br></div><div>--Richard</div><=
div><br></div><div><br></div></font></span></div>

<div><div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <span dir=3D"ltr">&lt=
;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com=
</a>&gt;</span> wrote:<br>




<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I did at first find it curious why the crypt=
ographic operations were over the base64url-enccoded values, but I was also=
 very focused on JWE, where I think the field separation problem is less of=
 an issue (at least now). =A0For JWS, this would certainly cause problems w=
ithout some manner of unambiguous field parameterization.<br>





<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this is an interesting thought experiment=
, it seems we&#39;re too far down the path to seriously consider it unless =
the current state were shown to be horribly broken.<br>





<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<br>
<div><div><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-js=
on-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<br>
</div></div><div><div>&gt; _______________________________________________<=
br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--001a11c1ad341a17ed04df0991b9--

From Michael.Jones@microsoft.com  Thu Jun 13 07:20:23 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D9521F995F for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIC8oXIArngS for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:20:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id C690321F8F9E for <jose@ietf.org>; Thu, 13 Jun 2013 07:20:09 -0700 (PDT)
Received: from BN1BFFO11FD022.protection.gbl (10.58.52.200) by BN1AFFO11HUB018.protection.gbl (10.58.52.128) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 13 Jun 2013 14:20:07 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD022.mail.protection.outlook.com (10.58.53.82) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 13 Jun 2013 14:20:07 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.03.0136.001; Thu, 13 Jun 2013 14:19:50 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>
Thread-Topic: [jose] #23: Make crypto independent of binary encoding (base64)
Thread-Index: AQHOZwAMAj7aO3iBB0SstN6K1FxxM5kyI/iAgABjd4CAAAkMgIAAACqAgAEjO0A=
Date: Thu, 13 Jun 2013 14:19:50 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367849799@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <CAL02cgQ+K=dWnhSa7A4w85psuxOuuf9m09uyChcOZPe17BCizQ@mail.gmail.com> <CAL02cgTDLfrVBYavY1RupxftZ_-Qr2s2vk9qyk7qpBFx4yDn3w@mail.gmail.com>
In-Reply-To: <CAL02cgTDLfrVBYavY1RupxftZ_-Qr2s2vk9qyk7qpBFx4yDn3w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.35]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367849799TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(52044002)(51444003)(189002)(22974005)(199002)(377454002)(51704005)(24454002)(50986001)(53806001)(71186001)(16236675002)(51856001)(79102001)(16406001)(65816001)(77096001)(81542001)(77982001)(512954002)(20776003)(76482001)(31966008)(76796001)(46102001)(4396001)(63696002)(74876001)(74662001)(33656001)(80022001)(81342001)(74366001)(47736001)(6806003)(74706001)(54316002)(74502001)(47976001)(69226001)(15202345002)(59766001)(56776001)(49866001)(55846006)(54356001)(76786001)(56816003)(47446002)(66066001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB018; H:TK5EX14HUBC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0876988AF0
Cc: "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:20:23 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367849799TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jim and Karen, could you please do as Richard suggests and close this issue=
 as "won't fix".

                                                            Thank you,
                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Wednesday, June 12, 2013 1:57 PM
To: jose-chairs@tools.ietf.org; Mike Jones
Subject: Fwd: [jose] #23: Make crypto independent of binary encoding (base6=
4)

In other words: Chairs, feel free to close/wontfix :)

---------- Forwarded message ----------
From: Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
Date: Wed, Jun 12, 2013 at 4:55 PM
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)
To: "Matt Miller (mamille2)" <mamille2@cisco.com<mailto:mamille2@cisco.com>=
>
Cc: jose issue tracker <trac+jose@trac.tools.ietf.org<mailto:trac%2Bjose@tr=
ac.tools.ietf.org>>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org<m=
ailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>" <draft-ietf-jos=
e-json-web-encryption@tools.ietf.org<mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org>>, "<michael.jones@microsoft.com<mailto:michael.jones@m=
icrosoft.com>>" <michael.jones@microsoft.com<mailto:michael.jones@microsoft=
.com>>, "<jose@ietf.org<mailto:jose@ietf.org>>" <jose@ietf.org<mailto:jose@=
ietf.org>>

To be clear, I structured my message in two parts for a reason, to separate=
 the analysis from the opinion.  I acknowledge that I am but one voice here=
, and I'm increasingly hearing how alone I am :)

On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor c=
ode.  But I think we're literally talking about something like a 5-line pat=
ch.  And early JWT implementors knew or should have known (to use a DC phra=
se) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part i=
n the discussions are likely to find the specification changing out from un=
der them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE=
 in place of CMS one day, without the base64 hit.  We should incur the impl=
ementation pain now, and get the design right for the long run.  Base64 is =
a hack around JSON; we should build the system so that when we no longer ne=
ed that hack, it can go away.
</personal-opinion>

--Richard



On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m<mailto:mamille2@cisco.com>> wrote:
I did at first find it curious why the cryptographic operations were over t=
he base64url-enccoded values, but I was also very focused on JWE, where I t=
hink the field separation problem is less of an issue (at least now).  For =
JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload.  I do find it int=
eresting if JOSE could more easily and efficiently support other encodings.=
  However, I think that while this is an interesting thought experiment, it=
 seems we're too far down the path to seriously consider it unless the curr=
ent state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ietf.=
org<mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com<mailto:michael.jones@microsoft.co=
m>):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
> -------------------------+-----------------------------------------------=
--
> Reporter:  rlb@ipv.sx<mailto:rlb@ipv.sx>   |       Owner:  draft-ietf-jos=
e-json-web-
>     Type:  defect       |  encryption@tools.ietf.org<mailto:encryption@to=
ols.ietf.org>
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> -------------------------+-----------------------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org<mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose




--_000_4E1F6AAD24975D4BA5B168042967394367849799TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim and Karen, could you =
please do as Richard suggests and close this issue as &#8220;won&#8217;t fi=
x&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank you,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> jose-chairs@tools.ietf.org; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">In other words: Chairs, feel free to close/wontfix :=
)<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------- Forwarded =
message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a=
>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g">trac&#43;jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<a href=3D"mailto:d=
raft-ietf-jose-json-web-encryption@tools.ietf.org">draft-ietf-jose-json-web=
-encryption@tools.ietf.org</a>&gt;&quot; &lt;<a href=3D"mailto:draft-ietf-j=
ose-json-web-encryption@tools.ietf.org">draft-ietf-jose-json-web-encryption=
@tools.ietf.org</a>&gt;,
 &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com">michael.jones@mic=
rosoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.jones@microsoft.com"=
>michael.jones@microsoft.com</a>&gt;, &quot;&lt;<a href=3D"mailto:jose@ietf=
.org">jose@ietf.org</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org">jose=
@ietf.org</a>&gt;<br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">To be clear, I structured my message in two parts fo=
r a reason, to separate the analysis from the opinion. &nbsp;I acknowledge =
that I am but one voice here, and I'm increasingly hearing how alone I am :=
)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o=
:p></o:p></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">&lt;impartial-analysis&gt;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">So just to be clear on the trade-off the WG has to m=
ake:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the one hand: Breaking every existing JWT impleme=
ntation in the world<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the other hand: Eternally binding ourselves to ba=
se64 encoding, even if binary-safe encodings become available (CBOR, MsgPac=
k, etc.)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/impartial-analysis&nbsp;&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I have some sympathy with JWT implementors. &nbsp;It=
 sucks to have to refactor code. &nbsp;But I think we're literally talking =
about something like a 5-line patch. &nbsp;And early JWT implementors knew =
or should have known (to use a DC phrase) that they
 were dealing with a draft spec. &nbsp;As the W3C editor's draft template s=
ays, in big bold red print, &quot;Implementors who are not taking part in t=
he discussions are likely to find the specification changing out from under=
 them in incompatible ways.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. &n=
bsp;We should incur the implementation pain now, and get the design right f=
or the long run. &nbsp;Base64 is a hack around
 JSON; we should build the system so that when we no longer need that hack,=
 it can go away.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<o:p></o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@c=
isco.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I did at first find it curious why the cryptographic=
 operations were over the base64url-enccoded values, but I was also very fo=
cused on JWE, where I think the field separation problem is less of an issu=
e (at least now). &nbsp;For JWS, this would
 certainly cause problems without some manner of unambiguous field paramete=
rization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. &nbsp;I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. &nbsp;However, I think that while this
 is an interesting thought experiment, it seems we're too far down the path=
 to seriously consider it unless the current state were shown to be horribl=
y broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac&#43;jose@trac.tools.ietf=
.org</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact Seriali=
zation,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, com=
puting<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling reaso=
n to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that'=
s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually &quot;e=
xtra&quot; at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly the=
 same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a> &nbsp; | =
&nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-web-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a href=
=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ie=
tf.org</a><br>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp=
;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &n=
bsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;Res=
olution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367849799TK5EX14MBXC283r_--

From gffletch@aol.com  Thu Jun 13 07:25:22 2013
Return-Path: <gffletch@aol.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1279A21F9992 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RuRe9XmZzAI for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:25:04 -0700 (PDT)
Received: from omr-d03.mx.aol.com (omr-d03.mx.aol.com [205.188.109.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5D99E21F93FB for <jose@ietf.org>; Thu, 13 Jun 2013 07:24:59 -0700 (PDT)
Received: from mtaout-mb01.r1000.mx.aol.com (mtaout-mb01.r1000.mx.aol.com [172.29.41.65]) by omr-d03.mx.aol.com (Outbound Mail Relay) with ESMTP id 8CBBE7006569E; Thu, 13 Jun 2013 10:24:55 -0400 (EDT)
Received: from palantir.local (unknown [10.181.176.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaout-mb01.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id D77A2E00008D; Thu, 13 Jun 2013 10:24:54 -0400 (EDT)
Message-ID: <51B9D637.4060509@aol.com>
Date: Thu, 13 Jun 2013 10:24:55 -0400
From: George Fletcher <gffletch@aol.com>
Organization: AOL LLC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org> <064.e396e921644745f7bd339ad363a7d7f7@trac.tools.ietf.org> <BF7E36B9C495A6468E8EC573603ED94115283F43@xmb-aln-x11.cisco.com> <CAL02cgSpYtAVVNe7AOiNhnBUqP-=CWaXw7NH2XwUu6eXgfZJ+w@mail.gmail.com> <CAL02cgQ+K=dWnhSa7A4w85psuxOuuf9m09uyChcOZPe17BCizQ@mail.gmail.com> <CAL02cgTDLfrVBYavY1RupxftZ_-Qr2s2vk9qyk7qpBFx4yDn3w@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394367849799@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367849799@TK5EX14MBXC283.redmond.corp.microsoft.com>
Content-Type: multipart/alternative; boundary="------------050405060704030000080403"
x-aol-global-disposition: G
X-AOL-VSS-INFO: 5400.1158/91399
X-AOL-VSS-CODE: clean
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1371133495; bh=Gux5JQIM9/U1fG8F63uJZ8RgGRVzwgv8cKePvtxUZV0=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=U5r4uU1UBz2UxL20GkZ6p7UFwNZiGLMno1A6bcYks/BUp6qLRfgwOkZkrzZaI3jdO r+ikGbwzlRSsOLdDnJdCzmVMPe6t/JQR5bRGUrj4/t1yHY94lLCES/tBS59+ceQlhu bvgEq2qlq/sUQZTA9lXYR4TnSFE/hYtBqNZO5Qvo=
X-AOL-SCOLL-SCORE: 1:2:518173280:93952408  
X-AOL-SCOLL-URL_COUNT: 1  
x-aol-sid: 3039ac1d294151b9d6367b37
X-AOL-IP: 10.181.176.48
Cc: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:25:22 -0000

This is a multi-part message in MIME format.
--------------050405060704030000080403
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

+1

Breaking deployed code as raised by Brian, Naveen and others is a 
critical consideration.

Thanks,
George

On 6/13/13 10:19 AM, Mike Jones wrote:
>
> Jim and Karen, could you please do as Richard suggests and close this 
> issue as â€œwonâ€™t fixâ€�.
>
> Thank you,
>
> -- Mike
>
> *From:*Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Wednesday, June 12, 2013 1:57 PM
> *To:* jose-chairs@tools.ietf.org; Mike Jones
> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding 
> (base64)
>
> In other words: Chairs, feel free to close/wontfix :)
>
> ---------- Forwarded message ----------
> From: *Richard Barnes* <rlb@ipv.sx <mailto:rlb@ipv.sx>>
> Date: Wed, Jun 12, 2013 at 4:55 PM
> Subject: Re: [jose] #23: Make crypto independent of binary encoding 
> (base64)
> To: "Matt Miller (mamille2)" <mamille2@cisco.com 
> <mailto:mamille2@cisco.com>>
> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org 
> <mailto:trac%2Bjose@trac.tools.ietf.org>>, 
> "<draft-ietf-jose-json-web-encryption@tools.ietf.org 
> <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>" 
> <draft-ietf-jose-json-web-encryption@tools.ietf.org 
> <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>, 
> "<michael.jones@microsoft.com <mailto:michael.jones@microsoft.com>>" 
> <michael.jones@microsoft.com <mailto:michael.jones@microsoft.com>>, 
> "<jose@ietf.org <mailto:jose@ietf.org>>" <jose@ietf.org 
> <mailto:jose@ietf.org>>
>
> To be clear, I structured my message in two parts for a reason, to 
> separate the analysis from the opinion.  I acknowledge that I am but 
> one voice here, and I'm increasingly hearing how alone I am :)
>
> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx 
> <mailto:rlb@ipv.sx>> wrote:
>
>     <impartial-analysis>
>
>     So just to be clear on the trade-off the WG has to make:
>
>     On the one hand: Breaking every existing JWT implementation in the
>     world
>
>     On the other hand: Eternally binding ourselves to base64 encoding,
>     even if binary-safe encodings become available (CBOR, MsgPack, etc.)
>
>     </impartial-analysis >
>
>     <personal-opinion>
>
>     I have some sympathy with JWT implementors.  It sucks to have to
>     refactor code.  But I think we're literally talking about
>     something like a 5-line patch.  And early JWT implementors knew or
>     should have known (to use a DC phrase) that they were dealing with
>     a draft spec.  As the W3C editor's draft template says, in big
>     bold red print, "Implementors who are not taking part in the
>     discussions are likely to find the specification changing out from
>     under them in incompatible ways."
>
>     As PHB pointed out in the other thread, it would be nice to use
>     JWS and JWE in place of CMS one day, without the base64 hit.  We
>     should incur the implementation pain now, and get the design right
>     for the long run.  Base64 is a hack around JSON; we should build
>     the system so that when we no longer need that hack, it can go away.
>
>     </personal-opinion>
>
>     --Richard
>
>     On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2)
>     <mamille2@cisco.com <mailto:mamille2@cisco.com>> wrote:
>
>     I did at first find it curious why the cryptographic operations
>     were over the base64url-enccoded values, but I was also very
>     focused on JWE, where I think the field separation problem is less
>     of an issue (at least now).  For JWS, this would certainly cause
>     problems without some manner of unambiguous field parameterization.
>
>     I will note that unescaped NULL is not valid in JSON, so it could
>     be used as a separator between the encoded header and the payload.
>      I do find it interesting if JOSE could more easily and
>     efficiently support other encodings.  However, I think that while
>     this is an interesting thought experiment, it seems we're too far
>     down the path to seriously consider it unless the current state
>     were shown to be horribly broken.
>
>
>     - m&m
>
>     Matt Miller < mamille2@cisco.com <mailto:mamille2@cisco.com> >
>     Cisco Systems, Inc.
>
>
>     On Jun 11, 2013, at 6:01 PM, jose issue tracker
>     <trac+jose@trac.tools.ietf.org
>     <mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:
>
>     > #23: Make crypto independent of binary encoding (base64)
>     >
>     >
>     > Comment (by michael.jones@microsoft.com
>     <mailto:michael.jones@microsoft.com>):
>     >
>     > For both serializations, you already need the base64url encoded
>     versions
>     > of the JWS Header and the JWS Payload to preserve them in
>     transmission, so
>     > computing them isn't an extra burden.  In the JWS Compact
>     Serialization,
>     > you already need the concatenation of the Encoded JWS Header, a
>     period
>     > character, and the Encoded JWS Payload, so computing that
>     concatenation
>     > isn't an extra burden.  Given you already have that quantity,
>     computing
>     > the signature over it is the easiest thing for developers to do,
>     and it's
>     > been shown to work well in practice.  There's no compelling
>     reason to make
>     > this change.
>     >
>     > Even for the JSON Serialization, the only "extra" step that's
>     required to
>     > compute the signature is the concatenation with the period
>     character - to
>     > prevent shifting of data from one field to the other, as
>     described by Jim
>     > Schaad in the e-mail thread.  So this step isn't actually
>     "extra" at all -
>     > it's necessary.  It's also highly advantageous to use exactly
>     the same
>     > computation for both serializations, which is currently the case.
>     >
>     > Since there is no compelling reason to make this change, and
>     since making
>     > it could enable the "shifting" problem identified by Jim, it
>     should not be
>     > made.
>     >
>     > --
>     >
>     -------------------------+-------------------------------------------------
>     > Reporter: rlb@ipv.sx <mailto:rlb@ipv.sx>   |       Owner:
>      draft-ietf-jose-json-web-
>     >     Type:  defect       | encryption@tools.ietf.org
>     <mailto:encryption@tools.ietf.org>
>     > Priority:  major        |  Status:  new
>     > Component:  json-web-    | Milestone:
>     >  encryption             | Version:
>     > Severity:  -            |  Resolution:
>     > Keywords:               |
>     >
>     -------------------------+-------------------------------------------------
>     >
>     > Ticket URL:
>     <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>     > jose <http://tools.ietf.org/jose/>
>     >
>
>     > _______________________________________________
>     > jose mailing list
>     > jose@ietf.org <mailto:jose@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/jose
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

-- 
George Fletcher <http://connect.me/gffletch>

--------------050405060704030000080403
Content-Type: multipart/related;
 boundary="------------070302070403010602020300"


--------------070302070403010602020300
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Helvetica, Arial, sans-serif">+1<br>
      <br>
      Breaking deployed code as raised by Brian, Naveen and others is a
      critical consideration.<br>
      <br>
      Thanks,<br>
      George<br>
      <br>
    </font>
    <div class="moz-cite-prefix">On 6/13/13 10:19 AM, Mike Jones wrote:<br>
    </div>
    <blockquote
cite="mid:4E1F6AAD24975D4BA5B168042967394367849799@TK5EX14MBXC283.redmond.corp.microsoft.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim
            and Karen, could you please do as Richard suggests and close
            this issue as â€œwonâ€™t fixâ€�.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
            Thank you,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
            -- Mike<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>Â </o:p></span></p>
        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
            Richard Barnes [<a class="moz-txt-link-freetext" href="mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
            <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:jose-chairs@tools.ietf.org">jose-chairs@tools.ietf.org</a>; Mike Jones<br>
            <b>Subject:</b> Fwd: [jose] #23: Make crypto independent of
            binary encoding (base64)<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>Â </o:p></p>
        <div>
          <p class="MsoNormal">In other words: Chairs, feel free to
            close/wontfix :)<o:p></o:p></p>
          <div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p>Â </o:p></p>
            <div>
              <p class="MsoNormal" style="margin-bottom:12.0pt">----------
                Forwarded message ----------<br>
                From: <b>Richard Barnes</b> &lt;<a
                  moz-do-not-send="true" href="mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt;<br>
                Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                Subject: Re: [jose] #23: Make crypto independent of
                binary encoding (base64)<br>
                To: "Matt Miller (mamille2)" &lt;<a
                  moz-do-not-send="true"
                  href="mailto:mamille2@cisco.com">mamille2@cisco.com</a>&gt;<br>
                Cc: jose issue tracker &lt;<a moz-do-not-send="true"
                  href="mailto:trac%2Bjose@trac.tools.ietf.org">trac+jose@trac.tools.ietf.org</a>&gt;,
                "&lt;<a moz-do-not-send="true"
                  href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;"
                &lt;<a moz-do-not-send="true"
                  href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;,

                "&lt;<a moz-do-not-send="true"
                  href="mailto:michael.jones@microsoft.com">michael.jones@microsoft.com</a>&gt;"
                &lt;<a moz-do-not-send="true"
                  href="mailto:michael.jones@microsoft.com">michael.jones@microsoft.com</a>&gt;,
                "&lt;<a moz-do-not-send="true"
                  href="mailto:jose@ietf.org">jose@ietf.org</a>&gt;"
                &lt;<a moz-do-not-send="true"
                  href="mailto:jose@ietf.org">jose@ietf.org</a>&gt;<br>
                <br>
                <o:p></o:p></p>
              <div>
                <p class="MsoNormal">To be clear, I structured my
                  message in two parts for a reason, to separate the
                  analysis from the opinion. Â I acknowledge that I am
                  but one voice here, and I'm increasingly hearing how
                  alone I am :)<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p>Â </o:p></p>
                <div>
                  <div>
                    <p class="MsoNormal">On Wed, Jun 12, 2013 at 4:23
                      PM, Richard Barnes &lt;<a moz-do-not-send="true"
                        href="mailto:rlb@ipv.sx" target="_blank">rlb@ipv.sx</a>&gt;
                      wrote:<o:p></o:p></p>
                  </div>
                  <div>
                    <div>
                      <blockquote style="border:none;border-left:solid
                        #CCCCCC 1.0pt;padding:0in 0in 0in
                        6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class="MsoNormal">&lt;impartial-analysis&gt;<o:p></o:p></p>
                          </div>
                          <p class="MsoNormal">So just to be clear on
                            the trade-off the WG has to make:<o:p></o:p></p>
                          <div>
                            <p class="MsoNormal"><o:p>Â </o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">On the one hand:
                              Breaking every existing JWT implementation
                              in the world<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">On the other hand:
                              Eternally binding ourselves to base64
                              encoding, even if binary-safe encodings
                              become available (CBOR, MsgPack, etc.)<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">&lt;/impartial-analysisÂ &gt;<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><o:p>Â </o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">&lt;personal-opinion&gt;<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">I have some sympathy
                              with JWT implementors. Â It sucks to have
                              to refactor code. Â But I think we're
                              literally talking about something like a
                              5-line patch. Â And early JWT implementors
                              knew or should have known (to use a DC
                              phrase) that they were dealing with a
                              draft spec. Â As the W3C editor's draft
                              template says, in big bold red print,
                              "Implementors who are not taking part in
                              the discussions are likely to find the
                              specification changing out from under them
                              in incompatible ways."<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><o:p>Â </o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">As PHB pointed out in
                              the other thread, it would be nice to use
                              JWS and JWE in place of CMS one day,
                              without the base64 hit. Â We should incur
                              the implementation pain now, and get the
                              design right for the long run. Â Base64 is
                              a hack around JSON; we should build the
                              system so that when we no longer need that
                              hack, it can go away.<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal">&lt;/personal-opinion&gt;<o:p></o:p></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="color:#888888"><o:p>Â </o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="color:#888888">--Richard<o:p></o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="color:#888888"><o:p>Â </o:p></span></p>
                          </div>
                          <div>
                            <p class="MsoNormal"><span
                                style="color:#888888"><o:p>Â </o:p></span></p>
                          </div>
                        </div>
                        <div>
                          <div>
                            <div>
                              <p class="MsoNormal"
                                style="margin-bottom:12.0pt"><o:p>Â </o:p></p>
                              <div>
                                <p class="MsoNormal">On Wed, Jun 12,
                                  2013 at 10:27 AM, Matt Miller
                                  (mamille2) &lt;<a
                                    moz-do-not-send="true"
                                    href="mailto:mamille2@cisco.com"
                                    target="_blank">mamille2@cisco.com</a>&gt;
                                  wrote:<o:p></o:p></p>
                                <p class="MsoNormal">I did at first find
                                  it curious why the cryptographic
                                  operations were over the
                                  base64url-enccoded values, but I was
                                  also very focused on JWE, where I
                                  think the field separation problem is
                                  less of an issue (at least now). Â For
                                  JWS, this would certainly cause
                                  problems without some manner of
                                  unambiguous field parameterization.<br>
                                  <br>
                                  I will note that unescaped NULL is not
                                  valid in JSON, so it could be used as
                                  a separator between the encoded header
                                  and the payload. Â I do find it
                                  interesting if JOSE could more easily
                                  and efficiently support other
                                  encodings. Â However, I think that
                                  while this is an interesting thought
                                  experiment, it seems we're too far
                                  down the path to seriously consider it
                                  unless the current state were shown to
                                  be horribly broken.<br>
                                  <br>
                                  <br>
                                  - m&amp;m<br>
                                  <br>
                                  Matt Miller &lt; <a
                                    moz-do-not-send="true"
                                    href="mailto:mamille2@cisco.com"
                                    target="_blank">mamille2@cisco.com</a>
                                  &gt;<br>
                                  Cisco Systems, Inc.<o:p></o:p></p>
                                <div>
                                  <div>
                                    <p class="MsoNormal"><br>
                                      On Jun 11, 2013, at 6:01 PM, jose
                                      issue tracker &lt;<a
                                        moz-do-not-send="true"
                                        href="mailto:trac%2Bjose@trac.tools.ietf.org"
                                        target="_blank">trac+jose@trac.tools.ietf.org</a>&gt;
                                      wrote:<br>
                                      <br>
                                      &gt; #23: Make crypto independent
                                      of binary encoding (base64)<br>
                                      &gt;<br>
                                      &gt;<br>
                                      &gt; Comment (by <a
                                        moz-do-not-send="true"
                                        href="mailto:michael.jones@microsoft.com"
                                        target="_blank">michael.jones@microsoft.com</a>):<br>
                                      &gt;<br>
                                      &gt; For both serializations, you
                                      already need the base64url encoded
                                      versions<br>
                                      &gt; of the JWS Header and the JWS
                                      Payload to preserve them in
                                      transmission, so<br>
                                      &gt; computing them isn't an extra
                                      burden. Â In the JWS Compact
                                      Serialization,<br>
                                      &gt; you already need the
                                      concatenation of the Encoded JWS
                                      Header, a period<br>
                                      &gt; character, and the Encoded
                                      JWS Payload, so computing that
                                      concatenation<br>
                                      &gt; isn't an extra burden. Â Given
                                      you already have that quantity,
                                      computing<br>
                                      &gt; the signature over it is the
                                      easiest thing for developers to
                                      do, and it's<br>
                                      &gt; been shown to work well in
                                      practice. Â There's no compelling
                                      reason to make<br>
                                      &gt; this change.<br>
                                      &gt;<br>
                                      &gt; Even for the JSON
                                      Serialization, the only "extra"
                                      step that's required to<br>
                                      &gt; compute the signature is the
                                      concatenation with the period
                                      character - to<br>
                                      &gt; prevent shifting of data from
                                      one field to the other, as
                                      described by Jim<br>
                                      &gt; Schaad in the e-mail thread.
                                      Â So this step isn't actually
                                      "extra" at all -<br>
                                      &gt; it's necessary. Â It's also
                                      highly advantageous to use exactly
                                      the same<br>
                                      &gt; computation for both
                                      serializations, which is currently
                                      the case.<br>
                                      &gt;<br>
                                      &gt; Since there is no compelling
                                      reason to make this change, and
                                      since making<br>
                                      &gt; it could enable the
                                      "shifting" problem identified by
                                      Jim, it should not be<br>
                                      &gt; made.<br>
                                      &gt;<br>
                                      &gt; --<br>
                                      &gt;
-------------------------+-------------------------------------------------<br>
                                      &gt; Reporter: Â <a
                                        moz-do-not-send="true"
                                        href="mailto:rlb@ipv.sx">rlb@ipv.sx</a>
                                      Â  | Â  Â  Â  Owner:
                                      Â draft-ietf-jose-json-web-<br>
                                      &gt; Â  Â  Type: Â defect Â  Â  Â  | Â <a
                                        moz-do-not-send="true"
                                        href="mailto:encryption@tools.ietf.org"
                                        target="_blank">encryption@tools.ietf.org</a><br>
                                      &gt; Priority: Â major Â  Â  Â  Â | Â  Â 
                                      Â Status: Â new<br>
                                      &gt; Component: Â json-web- Â  Â | Â 
                                      Milestone:<br>
                                      &gt; Â encryption Â  Â  Â  Â  Â  Â  | Â  Â 
                                      Version:<br>
                                      &gt; Severity: Â - Â  Â  Â  Â  Â  Â |
                                      Â Resolution:<br>
                                      &gt; Keywords: Â  Â  Â  Â  Â  Â  Â  |<br>
                                      &gt;
-------------------------+-------------------------------------------------<br>
                                      &gt;<br>
                                      &gt; Ticket URL: &lt;<a
                                        moz-do-not-send="true"
                                        href="http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2"
                                        target="_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                      &gt; jose &lt;<a
                                        moz-do-not-send="true"
                                        href="http://tools.ietf.org/jose/"
                                        target="_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                      &gt;<o:p></o:p></p>
                                  </div>
                                </div>
                                <div>
                                  <div>
                                    <p class="MsoNormal"
                                      style="margin-bottom:12.0pt">&gt;
_______________________________________________<br>
                                      &gt; jose mailing list<br>
                                      &gt; <a moz-do-not-send="true"
                                        href="mailto:jose@ietf.org"
                                        target="_blank">jose@ietf.org</a><br>
                                      &gt; <a moz-do-not-send="true"
                                        href="https://www.ietf.org/mailman/listinfo/jose"
                                        target="_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
                                  </div>
                                </div>
                              </div>
                              <p class="MsoNormal"><o:p>Â </o:p></p>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <p class="MsoNormal"><o:p>Â </o:p></p>
              </div>
            </div>
            <p class="MsoNormal"><o:p>Â </o:p></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <a href="http://connect.me/gffletch" title="View full card on
        Connect.Me"><img src="cid:part21.04020107.07020504@aol.com"
          alt="George Fletcher" height="113" width="359"></a></div>
  </body>
</html>

--------------070302070403010602020300
Content-Type: image/png;
 name="XeC"
Content-Transfer-Encoding: base64
Content-ID: <part21.04020107.07020504@aol.com>
Content-Disposition: inline;
 filename="XeC"

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAA
CXBIWXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAI
JLiEoIGgETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlT
p09Lly5dunTpkhC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLl
y5dB/rMr4ubm5ubm5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc
3Nzc3Nzcfgd34uzm5ubm5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zF
HGHAI0sR61oQpSxdUsuBrcbbpFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL
5KL61yAdzP0l4ytwdrCmZQ0B49ngq9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5
xhJQD0ijlA6g5aoPzQXA2i9znjMWcodll8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteB
faB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHnu0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm
5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGzl2e093YQJp4ZK4D+G+NGeT+oM131tF+h
+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRGmAkCkYsLFwDS//NGKvzbkoT3kJCB
AD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o0AicE+TFUiRou8QMPMH3hee3
xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8I6cn2B8meCh34eGjN6Ve
rAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1YO1qH6dbCKnhSYG5
oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ69MW+HWD9Tu2S
0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skjff0g+X5S
BR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBNv1lc
AOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAY
lnko7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm
+Bj0TqE4h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9
bF5rQRrpqG3vCt5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk
00D+UBkr7oI2QPpSCgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2
qwt9Le26NjkA9faXTy79AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3
YG7o/SZiFChhSkm7DkLe+n1ttYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HB
doFdC68EZ7ajSBEJss5l5/IM7hd6qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2
SiNe1wGvbXI153fwpnrSgWc/ws2y92v8PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJ
mfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNpdxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE
+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK63RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQ
d+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1Ej0GgzhSfuayglYmv/7gaaIn2W84t
IN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqvb/8C1AilmagDhgX6FnoPMGzx
MnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUCwLFVHq31B/NoD7P5ETA2
O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgnrBvSZgIG+Yo+GqxD
cuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPoK3/MPEATqdIi
QEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJDQtfUg0ml
oXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRvLQkp
3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAX
Q8B7LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZP
AFvtzIyo2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yM
oDu4grVrTgMoy8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJf
OZ5ZoMXlTEpXQLuY2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZE
GcZ43wHdA+movjR47/b6RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaB
VxGvyrpeYM+yLs/6HuRrzh2uFPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9
lOZgn5ijt9wGfbJezT4I3PY4G1QWjF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B
91zfDX6/wIOlT+LjW0KJbwptCyoOupk6L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGB
LwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZEkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNC
IWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+G9grKgnuz35x32cROPa4Clpfgff1xGr3
KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0dTXrCT4p9s2GMVA6uqRnoZXwqFh8
6hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISLIDZZ14XPhJK1S0WVXQ5BgUEj
fM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJFWNoq4IDeLh2CzJIZJ42d
QL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B+WN6SPNAVPLqbt4O
0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7gXzJ41LAV6D6
Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0Hoqz6hbwI
DFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNTtARz
uuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0f
XAHUFPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm
5/fdHgE7D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3
cmrwrzUguJ7/a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBu
T9rl+6kw8FSbj3qHwKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y
2BpnVfZ8DSU9ixyt8itU/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXO
MlD/ZOGg5lMhIsn/81oWMP5qKilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/u
v90fnjZ82vBpQ1CXq8vV5VD4q8JfFf4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSp
UqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoU
eP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMo
OVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynMcNSzKvCxstVUFLTLjplZPwNztWDxMcj5
fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOmZRGIgXYvewOQ+htjlQSQVPtRVwgo
v9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g9TblevUCkSLaaS/BVV8NdWWC
eaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZLsc8HtRHzkr2EZC9LXt4
ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8W/UqMvUHKHSq0J7g
MJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwClsu4jMQucu5z5
HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZz1ch9JPQ
/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPgAfh1
N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+Gg
inF9wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe
3jjveb1L79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jU
kKkhU0EZrgxXhv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k
6oXAC0jnBbeAGCxiJVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjC
IFfUVQKpirVnVg64ZJrnGkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQld
QaC7us5lAaWqTHxtsB9xzkr5AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6R
tuuag7JUPisvAGNdQwVjfxClDb2kAWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBc
QxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/q
JoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lKQdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJi
mvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazhoZ0SschLk86w2FobUjm/TMy3gW0ye5TCA
+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4rE8LKwDpxbLnmifA6VZJ+61pkLgk
9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULKQ7mUyAE15oHjpHWXawNkdpJd
zvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX3KOOqVC1TalujUxgf5qd
EOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKELZegyewqnT8YBj7f
2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1jLZgePz1+ejw0
/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yuv7n+5vrg
98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQiynr
I5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIh
s05qVsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/
gi7EEGYqBLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5l
lewH2laX3a4Hu5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcg
bZIypRagLRXn1Yug+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0
VOoPmZWz96fHgfm8uRo+kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1
B1xTciv4SvDgw9i714Ph8IsbLTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9
EbyrMabKEXCdoXJmAmRPdk55egZivk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH
41i7Z+BIaFO8VkZzDxjjPajg4CUQ+CbkB6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS7
9fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjtrYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27N
ezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82fArjt4/fPn47tAxpGdIyBHJO55zOOf23
8eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHnjT5vBAltE9omtP1PKvjvI93vRsI7
dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjIyMi7hf/u78O6D+s+rAtd0ruk
d0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf7e+9tf9/iH+0HeoV9Yp6
5benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunLpi9hwYkFJxacAFsp
Wylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8bo5sFhACUh3s
7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9SFX0HT0Dy
NOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNpi1ff
gJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUc
TAS4ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNie
phdP6gOW12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4Km
eJcr8gu4urLXFQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAE
F/BbaS0AhoaefZI1yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4
WJkj6SFgn0ePgK/BY4+SEXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjd
vMqREr/AS8vrC1lDISX3VTnhC35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgy
kjLn+22FtW0OZGzPD/5+/h29e0LRzOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHM
iX6y7xIwV9et9a//x7uVGCwGi8Fw+6fbP93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25
i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8CRxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eX
lxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8xGhB/wX9F/QHeae8U94JXehCl/+i/uO2
j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5FxCFYgvFFoqF6Xun752+F1jMYhb/
69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNTkU1FNhWB/J3yd8rfCWJ3x+6O
3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZWK6vwovqL6i+qw7bobdHb
oiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn40gFrWcva9/C+/bPn
m5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHciiOuqyRkAcnfp
mVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhSYWmZIQK0
eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GBvZVk
MD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2Rlsh
vQV5pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn
3/3wh+aw8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV
1V3RlYWzwbczr/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZ
ajgMnpP0DfJ1htwplqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3
Xzs4Ue9cyPWjcPjolY/OnYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp
+Tv7Fqi8pPjIlpMhJS1mYY4KF3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+n
vRwVPxkeWVO6PA6G89cf3th1Ci6NiHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsti
cJZzlnOWy3s+KCgoKCjob8svsiyyLLLkfZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcf
fABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10
Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5SOcjnY/kbV//YP2D9X8xIvguAdvivcV7
izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659tx+F5h+cdnge7Ju2atGvS38Zdt27d
unXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg7w6A/o7+jv4OHJl9ZPaR2WCz
2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9+3vnm5ubm9v7neMsAy4U
8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlISVKaXAkYKO4JG4gX
4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8HaTldBcjgHoZ
xeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG/CAbdN2M
ceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAYA1Il
eZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd7
3i97+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsT
s+HmTUi+ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQ
u9QfDLNME9Q4SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFa
fkM9cPRhUvEg8PM27U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1b
qArEesefyO0JZxOelLjhAb5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbT
NHBe0k3RjkFGR/uF9DKQkz+3rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPw
z3nlU6JTolOiIbZgbMHYgn8bL6VNSpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYE
a4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O
7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/aMc/237mM5/5/MPe9yoS/13teDfl4t37905N
Q01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9ZdoA1taANFuhbpWqQrEEAAAXlTSt5Xe5tP
aj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76VuIPJLbcUW0CJoJMeBNFMrmpsA8oiA
+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5EBPXkQKCIGKDNAWkVVXgMPGKJ
OABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEXrBscJvEN2FYafjGPAdev
8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4TswFfT53vwtpEdZ4zN6
gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYUyB6Z/VXKc7Au
8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90hWx9cmZD
YEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn3Z1K
Q2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMm
S+tmNNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJf
Qu5q+9cf1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OK
P+wLHlPNY70PgHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA
2T/Wrd7dyi95vuT5kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdf
fPHFF1/8bXzbBdsF2wWgM53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePd
XOcLXODC327+rQRGW64t15b/J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc8
5C8ulHQ6nU73B/43eTc14z+8W/WlCU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RK
bUAK4GutKMjNzeUDfwSxRy6YcwJYLMqxD9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZG
bQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjxufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHT
u4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hm
gscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpNoATJHZTDQG/nRGd3MAyTo6VZEHjY
cNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2zj4L2ncturwumROmK6RIY1kjn
xQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5x+4JjtOZvXIiILtJgr7w
FSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2DjN1Dgq4B63haIcWlv
pGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCuV+c74HNlTWIt
iBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQZyj2U9Tp
oOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrGRNMM
63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998O
baa1mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdj
n4x9MhZiYmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUAr
WtEKIttFtotsB6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2
oW1C2wQ4dPjQ4UOHga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0
aNGiRYu8Ox/tO7Tv0L5DXrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90
rUAMkUZ41AVli2GxshLEE+GlzgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01
C7QFak/ZBnIT+TNJD9p5MV63FpRp2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWflj
b6WWgeSrSTnpl0Ht43ph/xVyxqccT54MLz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBz
YY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wE
hg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcV
papgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP4y5AbFzCgzefQvZcY520L6FswZIH
O9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP+Nf0PubtB47H1o3SS/AdZNju
mwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/77BeIHhwcGPQIevRo8rJH
Czjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9bFU5/fGJSXG/IXF9x
pysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0GXWlDmLYd/Lr5
l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok20RwNBCz
FRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvWrFmz
ZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7b
e2/nfTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDL
gJf/xZco31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAg
cUHigsS8Oxp7w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEm
PEUMALu1BGCbNIwaQBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De
7uXeW54gjwvwL9gP9JmmZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQO
fXUScEU9D/0e4vbGJSZ1BfsP9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9Lkem
gGd749c+JpBidVk0A+c17XTuGbB6W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I
3AykW/IE3XqQjlJIag5Sc3FKqgy63uom9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEi
zNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ
4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQamY/VOQSOfKjerzIXXZXMbPt4Em8qeKLZu
I/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8ToakfInHM3tAzoDsMa5seLEzW3/h
OKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1odT4SA/IapQzLLYYmPqablie
gmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpuxGh4UTLmyNuz4LnE+ytD
UTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCrqcmq9TuIkbNW5XiD
7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWdE3dO3DkRXjR9
0fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA0tJLSy8t
DZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY/Grz
q82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQ
uh3rdqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj2
57f3r5cjdHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99
AHRihisctG/VjfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24
bw8wlAx/FZIBokjWw5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7
mgSZc9NfaVHg+Fn9QUsExaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKr
OTmOcKCiPdD5Ocid9A313cHvcPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0Vd
ClJ70UWuARg1kzYd1A32fdafQZurfs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbO
bAHTaK2UoTDobb4PfQUIEnpkh4DJqi5TB8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0
j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8FazZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa
9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LLgJnAHXHCFQupG9LfpI2CUZX7jvo2P+hX
yw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHFq7fV0wSEFw701i6DlG760ssMvh/q
fih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSVxz9CRp+UUq9uQF3/OqfKfgV2
P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZhkDYno2ruAwivrr9kOQ7S
aO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z774cWPJsybMlz8KN
oTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuXL7/PEWcFgQAy
JA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C1EXzFVNA
quY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ8Iyq
vKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Y
y9s32Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE86
5Ky1j8vqDbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41
PeOgYkbpj6MfQczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1
OuRvJt+u1RO0OtlbdWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/
d35is8CJxGuTz0wE81Pz4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7J
DbMrPIuCjIPWFbcLgtcN77NBo6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3
oPj1Mqsj08E51zZZNkO+7yNvBdnhdpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQ
ddVx3GED23bPbTjAOEAX7+wPzuHKJfMsiJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1w
xYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk40KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWho
uAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtbEK+kafpToMyV4ikIUmG+0caDKCaCJAOI
EY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyDYUqxoWW+B9cM+9eZi8FnctUHzaqD
XFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry+ta/Gej2OLras8E0UnqrdADj
OVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz6yvub4WcMzHnE76E1AI5
g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHOZ5oniMG6IOUaMN5Y
wpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhPaPWMS+HhPk+X
vS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDbBOdKW2PQ
5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhKiocm
b1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbK
ZFSeVT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7
Ro8AV38IqOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9d
fHbxWbhQ5kKZC2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6N
OP/xxNlhz7W9AKmYFC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyAN
FJFiAriWsFC3H+TG+hf6W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8
Kq0Gj4dVTtfzALNX6U7VC4EcSZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7I
LVDPsdSQAt5TvHf5FgaPaGOUR18wV/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb
9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZTQFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9A
pBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFlOGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+f
IMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhqZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6
/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0iGmihBwJWmM1g7Lg/Ez7WssPWi2a
qd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E18P/Efi9CLgREA26guYSxsXg
fJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjbgPO+rBMTQW7pKOh9BHLL
vS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5A9D3MW1wDQNrAfOt
2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3c3Nzc3Nz+yPe
31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQbKK0GkSAK
aN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdAd95z
nXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3
RsI3ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd
5PFyMshdRbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf2
0X5I35bwMtEAOc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRb
QafI6+TvQVsjYrkJ4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhh
Wk/lHmgtxWeulqCOsRfU7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0
CwHvj4wVHSngv9xjhn8zuN3h2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skG
heG635MJj9aA9YTRqq2DwgWL5gZ9D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5Wub
VoOanDkzoTME3vCYKY0Aj/xyTKWv4c76t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5u
bu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQ
MmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1E6H02Obtys8F342hUb71wVnN/2WR5SC2
as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWnP8mQfdTxOGgP2DZnXXFWAWePzA5x
34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y86+t4DiddCJ9LmjbssyuD8BV
U74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3AqZr9/gGRHVRTGsEoqe6
2fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7IU28/SKhHWgX1J9c
HcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPHzPYgxqSPFFdA
3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55IchtlCRugS5H
t1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT9me1
gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy
60UY5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+r
KcCH4pC8EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db
/xbWVSM5PaUGFOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb
2QmgdXattvkBG/Q3pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5T
IWhbQDOvMFB+UvIRAerRN4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NP
kIzSS2kSSEdERyJAVNJiXfVAOS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRS
A95+k7vF4gOJdeJfvTwDKSuevH14FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keY
wdnRct0WCFnPk5+lRoKjq2OwVhaUunIFfSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ
3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGKXJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+
cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYB
y/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4BWjrRIDTCdo1Vz+zE7x6eNbgOOT0
zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBtAVT4oOzXxVeB7q5pZf6ScLnP
nfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5ubm5ubm5/zB9OnHVd9P1M
/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnkBHldQEDAXXBtdHg7
KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7VBZSwYktrXAd5
v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV4c2r+IOJ
seAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bNIAbr
J4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVt
FdVkMDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAq
qowFsZ5BYilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKr
sbpdbQSap3ZDPQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZj
L/Cp4CNMEuT+aM/nGgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSe
AvMh85PU3dJ9cAyU7ruuwdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/D
Ybjz4m47x8fw9PWd/XeiwedMuWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDi
fKbuhZGXRkHNslXuV6kF8jVpi0gAsUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8C
piX2S2C4aCgpfQnaGtWTTWDoFJpaeBSoV7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pf
g35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8Tn
UevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAWjDet7XKiQVmbGpZmAF2kTyvfB6D1cj51
3QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Qa2PQbQFXvN9Rv6GQ6nRGahLEzUge
kvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOfX8Dp5dyozoaURnGz3kwB+al6
jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6FYon6A3SeSkIFEno6Azi
qtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2agNBLNyQfSEKmBVBqU
h/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjBXssxxTYQXGWt
JazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0vC9nTc6zp
CyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx+RdI
JdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ct
Zyx4NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUA
jk9yK4L4QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4
zT9BVwhcjyzhEd/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50
feu8DGK5tlxYQLojjRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v
7IHEZm94NRWUOP8evk3A97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBn
ELw5X1L4CvDN75vtdQJMV/QHDTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAA
jSR/+QcwWHQ6OR/oBks9yAUtUPpaGwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQ
NstfSdGgd0qHpC2gltSechDskprs+glEGaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9
ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9vLqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7
ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/BnuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5N
bwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1MavikIdalHnT/Qv979gEdOTk5OTg7U
21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqqMGTIkCFDhrz/D5BVq1atWrXq
n4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFyitsm2n1AacAGMQNYS7w4
BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3FHSbfBJNRsCXRpIe
tENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+sZ9LTgCYuV2pb
eLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C7yGWwdlW
8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVokvMy8
d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEg
SvOKWSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxV
x6gXwJUp7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71B
mo2TvuC6Kt5KPiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/w
htyHuhH6mpBuzfox2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D
5qOVdSWD64pYrVsMhiuGXVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYU
WVBkAfw85ecpP0+BOhXqVKhTAeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfI
wAoDKwys8Oe9/l9NXBPXxDXY2XRn051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt5
24ufLn66+GmoVatWrVq1fn/5ChUqVKhQAc7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5
X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byc
zn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgAOHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2
FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8FMR90d7pDfr5+qOeHcBpSu3xsi9k
D7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTFXl96BL6i5BjvgqB/qZxO+hDU
yXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwnDGvNd0AqqQYaRoLutHel
4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TPATlNFywNgKxlb1ak
3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXSKoBI0xJwgrCK
QcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaCuCS+YTuI
g/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAagptij
aSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD
/YCkKj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og9
6s/AH0xafXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYP
t2BItSHVhlTLS2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u
627rbuv+NgH6rfjlB5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgs
BovBoC5Xl6vLodTZUmdLnYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkn
s05mnYTmC5ovaL4A8s3MNzPfzD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225u
g0unL52+dBrqUpe6/0U9X058OfHlRBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6L
V1cSJsEvF/cfO/McTIcNNvNXoFUXTVkKRBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA
4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3QvQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw
1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao4AE1HzVy1fMB44rgnMiKkNLGttZzH0gu
r/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxvMgtZfCDjI8u57J/B/tDjc59KkPzG
u53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ceDf0AXNUdDrsK1g/eNkq/B4W+
jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G3RFRVGsGpsVyT3kV6CtT
WP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7NbhIH0hWu36xY4Njj7
u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgugBIkZFEUdFfl
nuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTWSO3AMFDq
RjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqurwze
H+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38I
fR36OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgnt
EuD2j7d/vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz
2cB5yXnJeen3v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJE
iRIlSgBDGcpQ4AY3uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwY
bHq06dGmR7C14daGWxvC8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz
5syZM2fynn8y9snYJ2PhZNGTRU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfh
d2fEnRF3RsCuSbsm7ZoEL8a/GP9iPOx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/H
Hx5xlg3yao+B0GBnBWOd21DNXCm9UDuwOh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0
RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhCFakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SO
O1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73W4D/EuMFwxLIrKwv698UHDuNelMiOFMd
Uzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lHGMHw0KdPwDLIDbA8M7QE61JTTWM9
yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8iwZU8f8UnJ2yI23FQb9VO+66
DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJb8GwWVfOcBxMM/UHDCXB
Mcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC9HetAhGgmoU3uJpp
jygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJKjnxcag5qK9FQ
GgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCeiQ9FTdDq
80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DEfENp
AiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycv
gfo7SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/E
PpAfyY/kR6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESl
v7//5I7JHZM75iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ
8Olrp6+dvgbJ0cnRydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpap
WKZiGdA0TdM0uH7j+o3rN8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95
PvJ8BD3X9lzbcy1ImVKmlAlXGlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifK
J8oH3rR90/ZNW/C/4n/F/wrk5ubm5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1
axAREREREQEtsltkt8iG++vvr7+/Hi71v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1Dmo
cxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+I
SdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPAUcfx2tkd7DucJZ11QdbkSvIbEDvEEhEG
ZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYBaXipVhVc4PNZ47s9N0GwpfWhgR+A
7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk131RQLym7da7MA+xXNyxoOak/H
5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9Wn91z5j487/q47qOeYF/o
vcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjqlq8c7DEcrHbwJaxK
3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3QTQTXNe20+AI4
Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6VdwCfiqigK
an01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4VFd+
JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyr
pXbgHWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBT
OcjZkDtM1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0
I/Iea1e1q9pVkFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/
m1rxbqqH/YL9gv0C5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d
+sfLN3rW6FmjZ5DSKaVTSifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1
L1BxUMVBFQflXWC9G9GucLnC5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1
nPWc9RwkzEiYkTAD8uXLly9fPoiZGDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rC
MmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wp
luiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKfs5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0
rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpnlk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA
/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWBx+QLm542gVc1Ys4nrwDbaKLlGuCq
7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw4nXSw6RJ8Nh+6fMLJ+BZ8uMV
D76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8qcjLfd2C4rd9mHAq3H9w7
cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y84QeVd1awlB0LxRsU
eVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwfmKf5VwXHx/ZL
ji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt4v2R3zIw
7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcBK+nc
BT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0G
jhQhLEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb
0TaiLTyd+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFx
cXFxccBBDnKQ/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se
5S6Vu1TuEtyUb8o3ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU
+/3VFyvFSrES5F5yL7nXb7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH
5ZBySDmUN3XJuNW41bgVTMmmZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X5
6wvL5oHNA5sHQuonqZ+kfgJvD7w98PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfX
Sf7i+TFo5lE7uq0C525dfn45BGxeru726lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZr
N9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYe
p8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GXgcs3NdjSDoylwvsWqg7+HWpOKvkLONdn
f2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36CuxHIroWGA8v92a/theHZwUuRV44
Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZZ59+Gbyc9mZRTEeIO5X0aXwW
2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNcYUIv7kPGzuxo+4+w75cj
B0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qDT2vfix4lodub9t5t
qoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1OrdGQOrKtFGp
/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2MmKEVA22Q
JrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEiUCSB
WoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9
oNzccnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm
1ZtVb8Le2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCC
Eu+//tk9sntk9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m
8ZnFZxaDT0Ofhj4NoerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pS
VamqlLf9VsVbFW9VhOge0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c
6Huh74W+UCy7WHax7Lx4745Lo22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269
GErZStlK2SCqR1SPqB6wK2ZXzK4Y4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G
4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk
+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNSn7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1
B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687
wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJTEl5Nva2/ehRelrg974YFUl5oE+kP
uqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLho60FR3m1jLYPlDjDFIMF1IJq
D9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5qqme1xawVLeGak1BHem0
5Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3BZ5xPCc9zUHZv8bji
/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfBccrxNH0PiAeu
gY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD1l59S35g
oXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0nnRFZ
QF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUs
mD4xfWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1
q9SvUh/23dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39beh
ZL6S+Urmg6Ldi3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk
/ceLSopKikqC5NnJs5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/P
fJh3QfFurnuthbUW1lrIb444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/
6ino5ub230S6dOnSpUuXhKhevXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2x
rlhHWk8orCuypdQxSOyS3fH5Xbg/70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0C
P6PPC/8C4H85aHrIS1AXieZiOqirUs7dfQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl
5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhD
JOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSnV5IGZ1ggt76H2fcc+B7yDPD8CuzdrOus
lSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb0KbLtbQUoI2qF7XBMd0+yzkNxBFR
T+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEduB/IFeYBUFaQp0hKpF7BeMtML
HGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+StCzQJct2XT0wDNJflKeB
Okc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcMQveEhgRvgXyDw46G
F4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6roHQi9b6ieDa
qNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY7mzg6gOu
yfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFloKR4
tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX
25fbl0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c0
6aSTTjrpvGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQ
nZtwLvDGr2fWQ9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfF
nthIeHr3+fzodWC+73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3
oJhqHp/pwGPxOSuAsuKgboB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2f
ptkGgbVMlpH590FQm4oFiz+El8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKi
XlHfBa8PJfaIqwKJ51M+T6oNjFNvij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGC
Xti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRHykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5
Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgrspZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoM
aWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZpM1I/DDKL6KtGwMuPoqcnnobYVrFfvtoB
nvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3AEmFpaA+EJ8uftHpogLJSrSIuQnIu
ZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYmriKc+fxCiUsfQsycV7WjNkDG
XzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7hnitgXNT7GL9AzJKEOYkx
4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA3GZuM7dB1biqcVXj
wJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR4EoxsA00EouP
guCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4MtkHdLaKPi
N+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZlDJO
Qkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7Caw
TMwVOiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADy
nllQrw3KAPE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdS
V7kD5kDjrnkOxOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJg
elkvq4CYZp4U50F8L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMno
pyFq5YuSL1aAj92xxNoW6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+
BC8evT7+WoHYbxO/i1sBrE0YoC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasP
AqWJOl6eBLWB8qXNH7THlr3yKuRwh7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/oc
dXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/uaP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumk
k046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xk
boDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh04lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l
6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8dsaOFAit3TZrlxxgn5k7Z2kH2Hbm
quSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGCcSDzrYgu8PDuxXmXdsOTUtdK
XckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNez2McA/Gd+EmtBZ5IVybP
F6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0ZolYBba2ts9UfxDV
zZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RIMN6XsfIm6Iv0
CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gBGGKj+A70
BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7ymvW
5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghv
AQGf+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8
C94+cV5njiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARF
wqfxzTP0HgF+Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazv
g/u1Z7OeCGKpZrd9BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3e
wgwDz/svyt0cDfENdgzb5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQR
z5TmELDaUdg3E8hA/ZlRBxLPJmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4s
QRaQzeUd2QtEJfZxA0Q1WuAC+aX8SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2e
Ua8EpsW4LzeDvGYW4zqIQOWxkg9kD3lKrgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7M
ZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc
0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/WulpFOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M
/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1CXgyePq7zwHNzJFiKih3lQvqFtD8
NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1iGWAz0WwnbXFBGYBadXClW7g
TnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olzwlev6qeMgkznLc2LFIMe
QY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs7FPk88fg2pOyWZyE
U112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwqPBLMhuYQYxEo
G0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUIPDNeToo7
DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3ZmXAQ
ki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssM
ohh4X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN
1CxaZ207yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2
ahrRoGzSNGU/UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ks
n4FYqnxghoP1pvWa+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUO
MEfIT7QvQD40n0sVon6IGRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZ
b/mN/bvDO5100kknnXTSeZe8deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vf
gFudHt28nx9evHjp++w+KGuseTPkgJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJY
ynhISEo69WIN+Md7NvtOhGw9slTL1ACCy4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tB
OWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjvGweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDg
XFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wzZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3i
jTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh200cpp9TMQEcogMRm8ZfV2ehEQm6gi
ioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CHiCAEmDnN3XIxyAfKCh7zX+8f
3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPlTRDlRX4RCOYnZlGzMYhZ
vC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhDbZCP5RwZAvSUuc1z
IK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPLuyC/li1kTpDH
5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9l52iW4Lv
Pft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ecMlvd
LHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDE
PCWArpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vj
onUgw4KMoXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCq
gzvZ+6GxEMyNZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXI
LcwW7cCM56UMB1FQlmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6
i3CQX5FfmQJmC6y6E+R483OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ2
05AJIHObdrkLaKxkkKvAvGBUNB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUb
MyfIieYrbRVwkm58B1Qhu5kBjBbmA7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqr
lhP0+fpTWoNSWASK3CDK8In5AYjsMqv5CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywF
nmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5
+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWs
XbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGTo1AJeB6RODHqI/C9Zw21Hof7616+
ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0ZR2dJ1D+E8hern+v9FaQUcVqd
g0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx8CCwdwp/bO0PCR2fjH7w
Hlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeBvtBcDuIjkaycBCVa
zab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBGUT4Dacqi8iSI
b0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dgNqIUW8CS
aOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNaSOQX
m0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh
1DR2Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxV
EoGOIi8PwbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9C
oKeTTjrppJNOOm+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dG
ZQTfJq47mj/I0wHdX52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3P
TsPFK5e7HSkKvn1CS+VtCKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC
9eVhoDR1+RyU8uZyMQrMytw1pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu
3/f9RoG6VPlRuQVmoNR4CNYEW3bbaFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaR
BQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWLpaj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds
1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsx
sM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kYLJnULepokCbVOQdGjJzFLTC/ZiTrQD4w
w8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCoJexKJWAB+/kUKMJ88RLED2KEmggi
UviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLtApYUbbPPSZAVzL3KLTBe6qXY
A4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHmTtDvGkP07hDT49X0pJLw
+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwYbD9nHwUJW9yTExtC
RAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzpz6DInBKrssXA
o9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+v/qsUGiz
st2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJfGq6p
Z7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ
+iOoiuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEX
gLHETDYvAhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbY
Wqh+YDxx3fNcAPOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WC
mQvIzXIRDto1Zbj2PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7A
LiqDOo92Sh3AK+clnQfvNM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJ
IE7IfEpRcBxxDLQvAWWd1sh2CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTS
SSedd8VbV5xfdo4Od24Ga7Btsr0bhIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSCl
V0oe5264Uvr5ugO34U71pyOu1IKE2Fd1ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/Lf
tT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZ
rc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYHgAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2z
Dcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcpjdPmYrA1tRRXHoJyVOuk2UDV1Bra
ObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1ZXbjLrhWO4emvAJvZ2+Qpyt4
i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFyAiPlKtkfSKY4I0EsUpxc
ArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6A8gysrCoCdJijjOX
ghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0QmBZpPhaLoB1
j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tfDXJC5ltZ
ovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Zm0DG
I+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf
5X7Q73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7Hs
xbIwYMCAAQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fv
ZLLc/5383X76pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUG
Yh+4/GKnwpO2Ly8oF0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjS
ZqpjICXG9Deng/Os2TFhDuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru
9wYgk2wuQkBmkCVEZxArRCk1C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVM
XFfaQ8pUZ+2Uz8B9Wd40B4LMLqLFZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Y
m+QcszlorbV26gegVlSrq7VAGaOMUCaASBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV
6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoaKB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7m
o80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCUFVVFQaCW3IovqFYxSf0ItKHqYrUsyBSz
sugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5+Vz+DCKKcWIyEC+uKs1BPaw+spYC
z0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oIE+QB2cX4ESgiKtMElCxaDa0C
GPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX7EMhx4pM8ZmOQc5zER1C
/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC+6/yU8JPCT8lwNo7
a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZCm0NtDrU5BJ/7
fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/GH9nhP8VP
/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3Xdx3
MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9S
Knq7JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs
/KEmE+Mh0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7l
nOWOhaTaxiTmg7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKW
u6Dt13ppy8HSW/tEk2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9bi
RxC5hUc0AxbwMeuAkVwxk4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPV
jWCZr23SpoH8Ue6iIrBJLhYlQDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGgu
NtaCaCf6KQqIzqKLehXwECmqgmWJZa9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ
0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWfA/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46C
rCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JC
vYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQlcTjEX0rqkpQA3jNGY89OsLVUp5vX312g
Hog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7uLi4uLg4GDp06NChQ6HBtgbbGmxL
az/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yHDh06dOjQAW5WvVn1ZtW09d27
d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZsmXLlmnH07Bhw4YNG8KS
K0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW0Ug9zj/jXcsVkz0m
e0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P89+1SKzh/ZK83
1c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8DG70v9H/
Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zcM2nb
/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPa
eS4VXdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G
+b+bt06cvYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2w
lo6dCjxMGhijgbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHg
GeEpaXkFkQ0ibyrnwPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc
1wYogRBb90HR+2XhyaNnAU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYu
MRVkLuOq+RwMRa+jFwazES3NvSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5Edg
XjevGhVADBRdBKBGq04RBYpBdZqDfGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZ
Y8C61dLGEgLWbBZpDQVrS0sRa00QBcxXsizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU
3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqHgTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0
fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkO
WmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3kjuD9ytPkNMKeht3jpRPwLUt8de4
dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8hiF/uPk0CRPZ73cNZAaKPOJt5
Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu237f9vm3akPP8HvN7zO8B
P7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFjIsak3emPyzIuy7gs
adsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL07a70OtCrwu9
oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1etTLtwpJ7A
UxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHvCnz3
P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68t
YVvCtoRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz
7c+Vtv7UqVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2
IgwJHBI4JBAOTj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nu
JrubQK21tdbWWgtTf5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQ
R8BeS2dQ8plrjPIQv8JIdhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs
/hkgx/mAXpkTwV5B3tMbgOXXpHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVb
CFJOx1gUK0S2cE12noRVt9e3/rInEJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHc
S32HeQLUjBah9QIxVpRTZkByHufzxHbgXqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzM
VP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHFpiQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7ayl
J4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9GLTmPziCnmZOwg7FZH+ndCMpLsU3sALW3
OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQiRMWELPEbRqDsp4zLARVV2dyErR1
yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQnBC0NjQpYx0Ic2f6JUcVCMsa
USR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnGfn2mezzoQ71RugnmV8YJ
/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1cTQDo76saFSH5HuJ
++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh+s+2jZC0zpOJ
qSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd6naq2ylQ
PlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2WbusXYbY
ybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/
qRfW0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D
6Lmg54KeCyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RM
q8j9VX/4I0rPLz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6d
u3Tu0hkyfpXxq4xf/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0y
N8r8D/aNaR7TPAYu9LzQ80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJo
PPcbDwnT9edGMmg7bbuSBoAc5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2
ik8gAFyv3U2Td4ExUWmpbwGfoRGjbN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH
5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRYZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36Jf
B5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrKsoYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA
9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRNdFR7gznS3IIEsU/8IoqC+qk6TpkKopJo
I9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRXySdiQElR3lOmgTJZOSBegjpIW61t
AeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s20ApbKlhOgBatfaglgzZHLaM1
BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LLQ/zE6LKPvoaEQbFfRD6D
JOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjnPa+9u8BY4A1zjQbD
Ty/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSPy5GgvzDWeDeB
/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157svUD0G97
uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1lKVlK
lgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j
7Xd0jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqN
zx+RWnF5W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDB
QTDuxbgX416kTWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq
1t1ad2vdhe2Zt2fenhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusES
yxLLEgvki88Xny8ePvf93Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9q
p//UOP+dPd+2g9c+ie8bncAcrWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuS
D6iRxhmxCDIe9GsQOBEyfpjhczEDLLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU
6BkDPPFLIGxA1slOCRneC1zkUwiUbfZhfAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW
3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCyy5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD
1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLkeGKc8VVqA+EndrnwOcgFF+QKUFswTNUHM
lS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5zjxi7gXZXXY3u4I6Xp2lDAKlhdJG
1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9LF+D1lzZpuYFrYg6VYsBzUer
ptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/Gaz97HvtOUA2MCeb30FS
nleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBYO1teqSr4Tg+wB5+D
kFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7mnll8JmT+Ifvs
Qj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8Ck0G3+CA
HsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6itv2n9
Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc
7nM5bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVe
EH87B/2sPCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P
/Zs6tJ1aqUu9cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+
qF3qlI05xhxjjpGWSP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/o
mqbX6GbRzaKbQb6EfAn5Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2
fVM7/afG+W956/c422+GR74uC2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6
X7OM38DNKEuXZ8HwIuFuOzMj2E8rJQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk
1athEBn90OE8BhmaOeoETIXkCgGVvQqQmNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL
6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7vOTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro
0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYrOcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKw
uCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj84rX4ECjPeAaA8bNsbGQA85ZcIzeC
fEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1WfrK0D5QhujnQTlmvKTcAPjySqO
g/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0xWisPrnHJ2ZNagvkemzzb
QJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXUE9R62g5bLdClHGgm
gtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsHgWuwMznxIljz
q3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1MujnXf30M+B6
qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepydbm6
HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/B
pD5MGHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3g
WOFY4VgBX2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/a
a0zFMRXHVPzn9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKV
q/+H/hqda3Su0bl3r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7
/FG7wkcLHy18FOyV7JXslf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83N
NBduTb81/db0tETb08PTw9MDyhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hO
mHJ3yt0pdyG2e2z32O7/ej9I5U399F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778
m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56+
+CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Coyavubi8ENKO62Ruim2vjEgaBry1koN4clGtG
eTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4CLhu3em8BXElkh0uN3i3aPvjpkKuKyEl
KvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzKOibXa0iKTd4QvwmeTH5W79EeMPKJ
vNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqAedzcb+4AJYc6QKkIyhpxSZ0P
8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2IoCLdyGx0sBTTsDUA8EIvp
AcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL7Eftl3weglWzZfRp
BepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrijXNWSZwA7GWd8
Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwIcyXIEyJU
U0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+EdA+p
GPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWi
elGFb9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYib
p0Du8jxKHA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ
8/nlMMdC7ks+quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61B
A8RhSMojlj5vBi/8427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGU
MWqDskmrKN4HsVM9LU+C2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZ
C+p1MVu1AFk5RFOQeeUDYoCuZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPA
I3lTvAbpL0+YS4DmopQoD8Z7MruZFRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSB
MkT0sihgWo1OnhVgmsYl8xjYfrVb7fNBy2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkE
wm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/vWmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1
m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5TT/rLATmSnfhlMNgrSt9jevguW8EEwfu
r7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczKme+a7cFe3FHA7gX9oMeQW0CUUbbK
OeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmNCa5NYIzSf5UvICi733d+pUDr
hY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxxyS+ddP4f5K0T5+wvwpcq
fSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEpZY1FsjdoCeom+0Sw
vUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeBfd76juYg5tP/
dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD4DnBHPaA
3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7nAPb
YNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkt
o30agfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCr
gtaaK3I/qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39Lmy
PphLzETdArK/+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g
6my0PXoYxDpe9XvRETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvr
yOD3K8SfSpwSmxPs7/t4rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/h
wGUQPyuxY5Iv+F1QgyyT3jic0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdf
zdu/x3l/YgZXFsjRMWRtJsAvv62QzyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmU
ehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t9
4B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5lr/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpH
nb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0f
ABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuTrREE/RxeJqcDAvSwatn7QmDTDD9E
LAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34Kjs/924acAv98wYMzHgKf4YHf
h+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd9l0B6miry+EPNLDN9fkF
zHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLaDyAqqweUPaBFWSLU
7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSywy3zPpYIn0p0/
/kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZApnyh+YNr
gNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdUKuQZ
hJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTm
Zr+xG4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc
2gMc+wNq8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHU
os2WbaFAgaxZKnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7
Y10a8CkYlc313pfgXZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVo
CKIMHxotQTRWc1IJLEnqMl8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0g
bHKdeQoMyRf4At+IIuYo0N77r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKm
A42UL6wPQMmrxml9wZigR+AFsxUf0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N
73PXREiZEf86NiPYrtun2dqDvbO9t+MI+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ
2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiP
tHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9HYPAG+xclLwFXKdTmiTaIHiCfxP/raDm
U4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukUAgpr27VeAHT4u4M8nXTSSSeddNJ5
N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fyJ0ja4rE448F0uV7a20H4WMfD
HD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZunnGgaOhfbX7BiT/fHmc
awd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9Arl0ZBhbYAA/tN5/e
ygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZVcmjXwVbCMdP/
DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG2jFrfUdP
MNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkDnJXA
W8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1ja
akPAPdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2
zHbbVgosIZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt
2ggiUri9JcHdxlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaI
I0aivha0VcJKELg/cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18
miY1AJvTXtDxOTjj9B7mPgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+
QYmAuENJIdom0Bs6Zxo3IfmeUtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE
7MlBOzz3IcvH5SoEbwTlgqPx6/ehSA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwG
fbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwFtJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2v
Qdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYiJ+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/S
G/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uorn/EgylrzKQfBLOuNdn8JcoyR21sDjFtc
NZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw8Kw1LslvwLPdvcubB6zzNcU2GpQL
SnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3Qe/q6ZHyK6hu5bX2K5iFyC0u
gN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0fPXKuRN8WnuHG8GgzbBU
tQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt27QnIPYaXykVwPOV
9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkBycoMQ1A2t+tZzM
A7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+83jrxNk4
rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZvC2eS
2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9be
lrLW+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGY
j7QxtrkgxxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kO
Zi1PG/dVwKG2UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaK
W1aCPty4Z9jAU8ez1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRR
E5QzYGYy7+hXwLmAFdICZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POM
vGA2MXd4J4MZbT4UA8GMZIUYBpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkp
d8lZ4Gnsfu2dBWYrJcrwgHWE9bTtAehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2
NbBJyFjwCQpyhx8G7pufyxUgh+pT9SpgFvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65
/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aSTTjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J
91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7NgkiMgdvlhGQqXCGW8piSH7pMynlNrCX5bID
KJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5wt2eauyQUexw+uNYT6FOs5bS11yHX
uOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF9o1PWbBp6jTVBsoA5Tj3Qd4T
LY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0FdhpcGh+qb41gXrOR+PZQTY
7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIXSBga/8Gro5BUJmFH
bFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUOzKmsk3fBXtZ+
zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlwPXdmSAiH
lPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6Dczn
5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8
YVnA1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYk
gKW1vbHtKGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoB
NQPSvgCW+mGTp0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2
qz/y5//t/Lvj9d/FlsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Wh
b0nZEpKijXKvTYj5LPb7V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzz
dSoLIGcP/17hU0FL1AqpX4HlolxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3eh
Wpa84P7B9TppJogcMlovBfFXnoe86A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zP
QQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/
bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyBKXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5f
NXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yWB7/OGAG+eXz9/I6B7Ka7jY0g84veamfQ
tmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVnp58WuPMUnJNcj2L3g/s9V1nnfNB3
efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5TeSpjSEERlYRHdwWxDOfEL0EyJ
U6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cKaKiVtBogigpFpIAyR2uo
HQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7PcpnrE/mI2VGWobUD6y
zrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rthBbgPuo6l1gT
3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhybkXYh7Hqq
66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0FrBq0Z
tAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafk
PZi1I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/
dVVocLHg9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+z
YmCba7VbY6BQ/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2
z69g+HrsKZ3A+MVVN/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwB
xjf6e/IUKM2VetbS4L5mjHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW7
7ZVDBz1ZV/RPwBxknDMWgTDN++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FE
zayOQiPAf6Dvr+FfgPmDPsxZH4z3jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5
x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2rQE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBP
s2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXl
YXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9
t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv2076tgJzjTbMkRsshe0bfKq9u0CN
i4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3QsmXLli1bQrPszbI3yw4NGzZs
2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rpabyr8a7Gu2BO8TnF5xR/
8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X7fDP6ue3y79r9127
79pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3Sfn9a7tNyn5aD
8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/zqzeNlz/y
5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpKSkpK
ggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v
/0nI9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJ
AAGihHeKWhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0U
OBIta7RwsOfR/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeD
tOnVvNPB2Kt/7bkGWjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNK
guOc766g8WAbbf/eLwoskbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+6
1fIleGaaK9VmYGnqkxBYAqy/+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u
8SW/hLCkLPNyR0LIjvCh2QMgZGv4sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6f
oVLWK+Do4bcsXAP/+yF5s62G0DZZRxReCqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DU
VsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTW
BKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5Gxi9PB7neFAKyIJmHRDzucVs4KYw5Ufg
Kebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+4jz45LBYZNS7C9TJ+yfvn7wfwh6H
PQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOflPqk1Cel0oYsl15ZemXpFZh7
du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF5WHFyhUrV6x8d3pJpezF
shfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7SO0haYnOuiHrhqwb
Am2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3funJYIfvTRRx99
9BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym/UyNnxo/
NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue7Xi2
4xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k
1QhImSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv
5XFQchCuxoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78C
aHVjfkjpDbKee63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzO
tRa0Btply2VQY+QlmRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauP
tLVg7W/v6jcXxCD1pqUIqIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5
YQwH8R6POQjGfX23uARKqLW9zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1
+KutAK9ntvMyeGd4XiR/BpwxJshPQfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcr
gAzgidIe9PpmG4qA0Vz3cXcFW0HrM6UocM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/
YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYyHNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6
vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCoZgG5DZgkXeIqiMqq1/4tiEuWamY38PWq
jfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmtrFZWp63v3LZz285t4cOPP/z4w4/h
p3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDoRje6/etOMKkXWEuoJdQSCt56
3nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8QcE6Hqzqo7q+6E1RlXZ1yd
ERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Zb5k0/SyusLjC4gpv
b8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEHbGMb2/jrNMrc
KHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou67iswB3u
cAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa82vP
rz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvh
Yq3bZ17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVK
a3FJ+wzkFHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+O
TpAtMdvsrGPhnPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAX
cqkBiB0UUh6Dplm+s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXp
y10aaAlqe2Ul6C/MSPM8WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOc
va19CMhoqYrOgFUGmH3A1ds703kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtz
zDCIa5b4fnJW4LnxUi4H7aIWYz0ISoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU
/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVN
L8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAnuGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq
1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9
qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKyFGh7tb3a3t+vF+fFeXEezCfmE/MJ
DDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+svy63ZYlliWXJm283s+jMojOL
gredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9+fXl15dDl2JdinUpBp/7
fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5Th+wf9HzQ80FPqFih
YoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jReaE972r99P6lT
A9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoVK4jJYrKY
/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2NVxDw
je/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQ
hxA98FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui
+Ly05rWVhcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXs
q/0OgdgssmpfgTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz
1NRzgG2pVkWrB+rXVqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7
bPvWrzlY6lg0bQtoxdXb1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7Uk
qAky0psL5ADrCdUETw33JiMXOH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2
BfWu+qPlfZDzlfFyKzicjoP2xiDmynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4Jyoo
BsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcb
oSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8UZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby
/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVLlyyFKturbK+yHY7PPD7z+EzYennr5a2X
IcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyBmJiYmJgYuNvzbs+7PYFlLGPZH8uX
+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E3Ii5EQOzi88uPrs4JHdO7pzc
GQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+rT6rHat2rNqxtO6md5re
aXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaHbQ6DUudKnSv1BpXE
VN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7vWq9ZxmYZm2Us
TGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P538VbJ84+
twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniGewKh
8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIz
W4OsK8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG
9N3eSE89MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxX
As8+d0XnPVAfKTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1
QajWML8R4PPcZ4AlAFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYj
sERbTM0Aa1fyi2aQNDRxXPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQ
njtofuBN8PfYuir5wbJFW6kUAREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5
BpT+ahl1KhhFZVvzInh/9YxzDwTKskXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjF
YKzXW+sPwZbfOkULBLWlGGoZDXo1Y455AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeber
Ghh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMqk0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2
lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFCRwsdhenzp8+fPh8GMIABQMdCHQt1LATd
5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT8E3DNw0HhjOc4b9fn/o6qVvTb02/
NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN7fi2+mybv23+tvkhpkNMh5gO
sD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+1H9S/0n9JxCSMyRnSE6Y
cnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq1KlTp04dUMup5dRy
/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP+DN/fVP+3f6d
zv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4sLbSrzcqe
oNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+zj3SD
4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5
XtkO7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQf
btQ49MYuJ3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6
geBQtwV+ACZpVn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0Wrp
wBYwnJWXy8XA8LMpxJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALe
Fo6DZtITtH0gf21cYdFA/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TN
Ur4tBOSXjJuMpUGP1qoHJoAwWxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALK
WbWJlAmWry17jCYIG2aNNPQCYVEg3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9
ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsDdcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4
WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ecOw60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A
9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5DIx4+73j7134u4d5UNB/poJa1X+1RvU/
VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/lf9rrGhT0n+DIkSNHjhx5DDPOpAph
4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0GL8+Obln3AHSsWuP797tA7vmc
VFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj4TUQRupZ+kLQGgjT5MXA
VD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19lf/R10D/mKXE3xN4o
VqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNqyxMWBaQk6aK0
BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUHJgNoZ/Re
WhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzEAeJo
8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfA
XT5VL4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1an
g/SupirDQTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3w
jeElkD7wDfA1g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKs
gyyd5H2ghQnLzZNB/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysO
rDiwIqyqt6reqnpQI6ZGTI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZN
BNMFLTXzLHRxRn9d5wS039bu2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuD
GqIvzO4Ckl08EuYGNnFZuAz6Df2uOA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/
pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7osCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsR
As/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+
kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxXrG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLe
EK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10bA0J37XbgI4h6NiTGlgjey55vPN9C
vphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsMfO18G90DQWppaGR8FhyV7d0t
Z0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuAcEv40fQiMJHzgh+sP1m3
GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7hOc+ZD3r7JhTHUyT
DDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhcQlggAgKTNIvw
DuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPieHAXma+ah
oQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZodLL
lV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuC
OFWfLi8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ
3WU1CPvKUC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5
O8DV2vm9OwnCcqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPl
ZfktW3kwP2FND8QARdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinf
gDhNdwr7wVBNjrP4QI+XOmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNX
k6uC2NfwrHEDyHZDFVMMmOymGcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8
m2vKZTD0ML8p3QY668dMGvgmKoP844EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE
26qDwWCYLntM+8CwyYh1EHgG+HsErBBoo1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegf
a98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVi
bTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3D
eoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/FvBfzHixlKUv/0QV1qcu/URL5r/qf
9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577VciJ9VOrNWFLgPCOPFuyCW9Sxz
nYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2Bj2ZD6UBIHzGEf87wAgx
Tk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6PAO2g8r7rU5AOWxaZ
i0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8SNxyML5qnhrwG
OV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO9Bh1sBIC
3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqehsh3E
tfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3f
S/cgLM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0w
dxbtnAOvxZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0J
YWmOKNP7EO61lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWF
peJZyDqUEcjZC2E7QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFB
j8efTpzvN3EOMLaH8Mz4fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7e
mlnAJLWBfyqIy8SexpGg6srBrJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8
eNnRbDjx6umembugd0afeS89CyGzm2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/Mtg
ulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+s
U023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8QKs4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFD
QS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlriaPBleW+4h4A+0Rcv2MC/hQqm78H6uvVo
aFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3BfAENV+TPPJtBDAzGeWJBek3poT4Ld
YR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73VwvZa/L30PRO6KjLV+D+Zmhkzx
fciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUHqC39zfJvgulJ613DaMit
kfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8Jxqetqy0HwVfVH+lN
ANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA4LetE3dAYKna
V28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i+buHd1BQ
UFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+Fb4U
NwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO
96WdIF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuH
rXhlsNQJGRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B
3aF86YsEb+WcvRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJ
A+ublnXmIuDPd77pnAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DY
JRXVuwK7qeM3gatc/iKlC6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP1
7sl6/gsgYRgmx4H/vNZWKwf+K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyo
NADdhlGPAfmEcYI8B/Qs0jCB+oM6S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/
gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9
rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEBiEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoK
CgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVBU6yRYkfwt83skt0QxK/Nm0xRICq8rySB
Ok8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzPxYfomyC/c94mXxEI1cIuh80GTzP/
D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILYKqa0+TMwfBweEvMscNM2MawC
+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeTCs4r6UVudwZPMU+7+M1g
NlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/PVC/VndKFhCXaFOk
NuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0FMV6YbNwJHBNK
e78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQRweG+p6F
wFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4jUCQq
5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQ
iwxmzZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+q
AkIttbGyCDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCg
oKCgx0n8sw1It/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3
QKmQH5v/IqTXPn3w2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZ
JeNOiMuIbRPyOvgauMq63gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVb
ZdD3SPsNkSDk+j92doDS5uIZxfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GN
laqaJoHniDDU9i5cnJ/0UfZYyBvmi9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus
9OS24H7LfTd3Kahn/a+5zoD5PVNAagzWosa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3
Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsGlnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTs
dgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqmgnLGv8h1CHy9PG/53gXfi/7VzgiwbpOy
NQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+IpeCbQ0mkp2EMeq4WoEGMoLHcT5EPVq
qCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhKGV6V5oPQRUokDPy5gZvql+C/
6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX/S3BleVp7twBvhxa6X6Q
Qo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcTX4h0g+mc1l8s+ncP
76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1CfA1+nLn/wvqn
oUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht9fqWi2DY
b3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSIO5Ng
AOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O
+nwtRKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dA
QQSxtt5eHQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUK
tNX7Q86p7LysgeAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhT
cLt/xorMNyC7t2u+9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3c
c712MC6XIqUfIO6bsBrmiSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJ
ZRIpDr523mm+KSAtFyaLyZDTMy/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+
CJSril/7HJRx+hYFENfrMw0/QbHosDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSK
X/peaQHVeXonB//uYR4UFBQUFBT0OPzpGecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5
V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3ICpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1
n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8XvHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZq
r4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupTyJ+hJ+uh4J6cNStjARQLjdgpVgbD
FsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN+BHyxuodZAfkeIRo8wzwfK6M
F/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6PtoVAsKeZa+HtgDGiLfRpI
AfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+sfgW2btapjtLgnuBq
4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqWTmuLoFj96JVR
aXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBlcdaS8sG/
MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7i6t1
bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUy
l8p+AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57z
ffZz4NLuWVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKg
peT/5HkWxPIR7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8f
DsIm9wB5EpAC0k4wrk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6H
ql9VeAnsXfXFMSvgl1XeTUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRx
xqvRVSHvSb2++h0o7/gauVqD4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFP
OwQljsTPihwCruM+QVkKnin5y3NaQpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXP
dPdV53JwpnhSc7eB97hnuccL5u2mU6ZQYLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9Y
jXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGl
KZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJHKa1AT1I3+G+DVo3njN0gp4k6NJAMmujt
qqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZkgRwupqgXwZFm+UQ8A3quPlhPBONG
eY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD1KUyB8qvB0+2ppv6QXR6fKmY
lhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKlSwuP9+nTp0+fPhAWFhYW
Fvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQflI1+Zn+kFik2pan
nwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6YXQd4EPFNQjXQ
r4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814Ex5l7qy/P
AO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBqTr3B
3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/nt
nbnu+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nah
H4N3rK+JZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhN
m01lgTlK3YzycL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU
8Lv8FfQXIWNM7j3np+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/I
SVMsmMrJS9Qs8Lf11xN3gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0iv
mPYaF0NeD+cB7yhwnDJvMayGhPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfI
fcIEp2vcbn5L//sGduPGjRs3blyYQBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzL
L3D16u3b2dl/Xbxy5UqUCA+Ht97q379+fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xP
RITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3LzMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2i
KP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B
+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDvsEWGjwNNU+3C26D3Er6jDQjzuCjE
gFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5/MoV6DFWyroTDilbKuj3P4KE
6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh3YRjvAVdarWMu9wRbg9e
1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L7QgI7cQD7ALhF8Mc
0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEdeU8gemnEv5Qdg
vvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUBJV3MMMeD
O8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQmZtR
/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0E
Wm9K0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8
GkpWKuYsq0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRr
f90Hw6Ps3bt37969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2
QWZmXl4gAGXLli4dFQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRN
EODpp4sVi4j4tT+P83n/2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs8
3t6A/n8mq+7f93h8vsK4bdvGxEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQ
iml3hVRQV8nbmQDCE2JrfSxIcYQYNoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgY
THpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A76qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7
Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmn
IHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w24dObIH80dn709tByJ3IiJgtYGxoMfvr
QsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0V1yoXQBDSeNdxxG4fytvkh4Lvi6u
b30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzIc7l/0i3gK6029JlBLikvFdLB
W0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9yS3vAfCleBZkpYJ6mhm6
FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDqpU3wdwVHTfsFy0nw
NgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGOwbve7wJhgfyy
tTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+QVoVfg9zN
/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1O9jQ
fkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4u
LAwOHbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c
/nTinPzGdePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdB
v6xf8DUBsZQYJX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdA
C8EhW4GvhK8CZUGt4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSul
z4O98InjrZufLIPbpjRD4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5
NnQrpN+Pyi12BLyH0rsmxYL3nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q
2s34klgazHuksEAUXG+b9FLOafB10vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qw
twd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZuAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJ
eALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4
jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoPIKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXP
dTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCNUXcI3UDtpx8Tb4G8XtIDdcDU39xQ
9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHWWGxF8RGgFxU+sgTAfljsYTwD
Jd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAFPPPXfTj8IwW1y0uWLFmy
ZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L9dtSO7s9LCwurjBO
QdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1HTIyFOUfnd+1
a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE6JDXHuRv
BUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpIDoEUK
L4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DM
Gahe/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dp
amlw93a38r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD
3mzPGFdpkB4YLcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH
+jVEVQqpEdISzCfFCOUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+
bcpsfxjkf5P7TH4iJB9JWZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/
cn9peHAs81amFQyfS5H+3WB/wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggL
QSrNp7oMxhjjbnk82CvYo02twFbevNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubs
EpnXQNmlfOf5EaK/jnreuhzi9xWvn3ATxG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDr
sWNRcPTna19d6grp+/P2pXUGZ72srintwD/KMyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vu
u7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrHKscqxx9/3wq2V0ddHXV11N/d+0JTMqdk
TsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Zem3tt/u5n95/77yfo/6aqiqKqoKqq
qmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z+f3g9wcCilK4PXjwo4/eeqtw
+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j24K4j9ufnnGW65axxswA
c0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE8bDQ07ACpN32mJhl
oL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/SzoGawVe4H4o6hZ
DoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4//EPXU8N
hLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbzlfxv
lL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U
+prFcg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBu
XzVC6pm0gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175
/OF50XA+5dZ7rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXz
YhBWCvNNJ0DZL16WloG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9
vU1rwNDJ3N34BBSZFr4+bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98
pQbsTzze7szzkN6ITYEfQVtgnB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmC
mrtGjRo1atSosNb5cYlsGdkysiW8/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12
+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu
3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3Lti7bukB/+tP/736SQf/xFKUgkS1I2f4906aN
GNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUV
BQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3ZNlicTh+v/+o6/+ogriP259OnLOs
9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4RIoB7XOttdYPpNZFR5ZbAuIh
62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt/SPBAPo1Suo24IFu1L8H
vRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJHzTth7dklWVvjoHTH
SmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D5EVy8pVP4EGC
fVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfaaTC0loeJ
30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+2T0S
/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F
7kU2i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpc
uvMx2OOZpnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V
4Pb41FYPhkG5F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2
vg+OvnEq43R1SLmsV9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHi
xIkTJxaeHz9+/Pjx46FEiRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUN
GzZs2LABMjIyMjIyICoqKioqCjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn
5u6su7Puzjo4fvz48ePHC8MXPC4uLi4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQo
VZWqSlWYkTsjd0YubC66uejmolCmTJkyZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0Wdpk
aZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4
i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFrxq4Zf/z9ubHmxpoba2B66emlp5eG8+fP
nz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe8LThacPTHl3b/7DNaZvTNqdB+U/K
f1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiSviV9Szo4nU6n0wk1F9RcUHMB
TJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5oeeHnoc2MW1i2sQ8vnH1
qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z+32+gpng385IV6ky
ePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv1i3Iy7Nao6LA
aHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvtzYgPx33c
/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsCaMNy
W6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4
flL7luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5Ehb
lTw7RI61fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUz
JhVi46JioidBpDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5
H4S+YCirTAebTfrcuxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjt
eBUNwk6b+pcKAWsTw21Lf+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc
3Ku9SfnNoHRqzPHi88H2vpwWvh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fg
bZV/PmAHxyaLKo4BY2v9Y6UEZFRJeeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHu
obzz7uJQ8UTF80USoGTXMkLJb8F0yNQnVAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/
8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyfO++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJ
EyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6ggTmUV/1bym6peiWorD80vJLyy8VfsVe
bm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPUD6Hr1K5Tu06FnF05u3J2wcw9M/fM
3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oePjpO7O3d37m7IL5dfLr/cv9+P
5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlhzwx7Zti/3s7U7VO3T90O
JwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8pflP8Jni35bst3235
z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/vjJ8ZfjKAN84
vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7TuHpc7+v/
Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1K9z2
6VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QI
qUAaJr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqI
AN1NSQRAQgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID
6U2mQ8rqrBrpD0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4
cfXutrvWws6O+7PObgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ
9lsOOHqCb2vWK2nnwD/cednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn
5mG3COlfZg9xfQkPWmdsy/kGzCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1
LFjPmd4wxoM/RnmdhuAdpt7KTYVcMbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdzt
AiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJIH5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODI
jtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLnGTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGT
bWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuFzYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6
hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0CtZxhpOAN003xCd2Ct0FyoA9Jz4alF
40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbDtc4F7RS0WxDnX22/IIFZu3bt
2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03dt3Y38zgPnz9n1WkQ5EO
RToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJvht8Mv/nX9+Phkpqh
5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9G+VJBc+7wMxZ
M2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n8bZO2Tpl
629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW5Bos
PrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpU
q/b79gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6
tlYehHhu6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0e
Jm8GVoi9dS8In+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKm
hSC1NW3Q1oHwjCzKrUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgoc
RqFRycYQ5S3hVn6ECE/EiLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCk
R5ioNof1T2iVyYMTNkPd0oNB25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e
2jZwp+SNTs+BQKQvJL8j2GuY20ivQWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX
0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNB
nyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtO
CdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVfBHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3ua
BsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH+VNQ5G7Rj0sdgbDXw0fGLwV/28BU
qTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR7jmyR6QOAm2GMTJ0GDBffVl4
E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxasXHjxo0bNxbOCP/R9ZgL
apsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQTgonhd98Na4N0AZo
A37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAEJzgBdKMb3f74
6/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E/6PvzweJ
HyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16QmNWHz
zM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBb
t1q1ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/Y
GWfzcVcDuTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNA
HCItQgHKaudZCPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGm
HiRt9E0yFoUrSzLH6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWE
T8WODAblTTXTuwwC9QNLvSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2Wd
cZDvIyhpid4dEQPlo8rVDzkF1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3Ms
eRJwRavJNAg9Ffpz5BiIHZfoK5ELifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30N
qfvTOuZch3M7L5dL+xByt3pD/CvA1tfeOiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUU
y486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSAMgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4
eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEHQBVxWatD1IionxzfwJPnypVNOA+h4baP
QgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/iCyjbo3hGORkqHKpYv1YLsCeFfJf4
M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvnT7x46hSkHsrqd/MoqBHmapZU
0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtNlb2Pb6AWJLDFixcv/tsP
koL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDCgQowadKkSb+txWvR
vEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyXZr80+yVYKCwU
FgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYRthG2whrn
GsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPtwvYf
/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86
vnfvtWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3
+fm/rtf86FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG
6ufg/NwbuZn9ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08
tSkLzledeTk3YO2sdec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf
4CVqC59D4Cn/Lf08iH6pHTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5
Kr5v3wglXzctPDsHskqHp+aMBvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7N
E6/a34Z7FczNS9wD7Xbe7rQx4Oua2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAso
Xf0tIG1nTrQwAFzFPBfVXHDN0p837AYxRi6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD
5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwnos4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2
EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKlY2IrBCB0onQg/mWwbQibhQ+Uyq4zTglS
RiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+okHIfLCPdxjCVoH5A/tsSyXw5ftK
CXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQvu72gOsmyGueq90pAx6MhvBP
QR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTxLeAZ2ujV/88g6fT4BmxB
7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gNozaMglEZozJGZUD0
neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej70bfhTTSSHsM
/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1AfaA+UIcH
ox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWIeqTw
ZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/
HX/hzY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2
h1Ue3n/U4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv
/uST/2iCpyDu4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFf
jPsFjw9sxvB5EYtBvaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75K
fQWE3oYnDeXhZon7SRdWQPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5
GSo8iN9gSAJrd2tRDoJaQW0tPgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36s
BUBviiAkgHhQF5V3wF/TWTGvMxiTDe3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp
6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXR
lqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMvg7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4
BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz
78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfEKEsVuB2ecfv+cTDUk3da+kDUujA1
thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8sr7Tehpjc+E02BSJaRRaPygTD
EPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW0n4y7AJnVEpOSjfwrcwe
dC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDoE+gZaAeBQ8pq31lQ
ZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F4cOHDx8+/K9P
nIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OVKs8+O2MG
VK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0Dk6lY
sfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GO
HDly5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH
546Dtj1gXGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c
97jmkLnAXcc9BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5j
GHBSb6VfBHGysEj0g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bI
KND8asdAKOidDTPU1aAsslRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbU
mOM9Bm+crfnuhW/hl+X7Lp36ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTC
d4TdjmgIYWdDy9ltYGkdeceSD3p9fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+
0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9
G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIWMC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/
RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN620z4BAobAKmk4uCbm/uh7EvI3+C4HngXJ
bM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSsu1/10kYIxOvN8uaD9rH+tvAe5Jdw
V9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/RmBEIBL0idp2dTrop9X+gfqg
BgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7wV8U/M9UsOzcnpV7Vu5Z
CQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6j9Y5/lf5/f+4Ztjn
c7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3az+xst1tRIDTU
YpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTCuI/bn06c
lamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcMy83d
DG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArC
FLGD2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx0
3IyrCYbz9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG
78Kz5Sr0e7oflJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5
W80TIfRLR35UNIQkhawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QX
y4CS6NX0LSB/Uiq/WBfI65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9Fmw
Y3gmYSqkzTS2TX4ZQvbYD9kmQ9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1l
s/01CPi1ndJT4C8aMBEDOTnpC7zPQeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfk
Nr59Mn0TuDpmpST1BeW8sij9I7B1t3+pfQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2g
VNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8atBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLp
h5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9AstYxjKAoQxl6J9tNSgo6HF44onSpSMi
4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHiERFw9uydO5mZIIqhoSEhEBY2ZMgX
X/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/+tPcfj8kJPxaQBEWZrFIEmRl
iaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9HVSE5OTfX7y+M+7j96VKN
B40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/TeHkdCIG+O/pVcDYpc
bVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9IEGNXFcpF852
veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4Wd+mrwJ9
mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqEW0zO
Su9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQ
L3tm590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkz
gL+M+pHiBf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21
IIDJbXrPuA+0zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBM
YHsgA9QG0mLhTZBijMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmX
u0FufprHPxPUE2wJ/AJynNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+
HhBoIpwGPUH4WVwFvC9uk74AXdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+Q
lZWT43RC375vv/3113Dx4rVraY/jJotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnP
PTd27KJFcPr0tWv/aJ3ox6V69bJl4+Phxx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t1
5vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9b
bn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgThJCRMNr5cdBBkD3FXzbPDqYyT2qFZYCln
NIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQejhO/vdwN3hLQhcAu2n9hz8btL4Ovq
p8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl8oE/AeSFNDCfA3edPF/WQLi6
9lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2ARXzN4AF9pYjWGJgibBVD
QIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8ufk6iJsymt8E5Ana
PPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuyZmRdhhxnVn25
E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ/QQAmaZa
MgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgoqVwC
9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+Uv
VoR7i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0
q/p9zQDaSf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp99
9o9v4vt/zZ9OnC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AU
TB/HRIZUB8MKZsibIfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZ
Mze+TBNBPBvyWuJC0BdnrksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294H
AmsCy31TQN5hirA8A+pRbaM3GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itF
xK0G+xVXpKUD3EjdundNHNjnlUmr3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8
YJXQm2zQF+kX0UFIYgzHQaylRwulwdBYT1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtA
jrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRpzoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73n
JIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi6LvFfvQD/RVhseACoTFLhATQv+BHcS3o
U4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTacMBwG+XRIo7A7YJlhmWH7CcwO4zrz
YYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT+mx2Q+N3Grq7TwBnEWegyTsQ
0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPHhWHwnXvFnU13wf9ufs4F
DyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1HjtHGiDlZP6pwCUp8nf
PcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+Fffibt4CuXvU
K+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrWM2YK6B3l
m4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymAb6zr
mfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/O
A54QhodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDg
PereCUJe7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7M
eM3VGzI/dZcMTIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6zn
AzJBjBGHiU+BGGV43/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGq
NZAO2oyMxik1oGnxZzuXbgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDb
YogaI1e05IM+jmrmJZBYrOj+5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0Q
Pzcso9grkHTYvUN/EXZe2PbJfhckz8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgR
hiflX5fPCc45BwUFBQUF/Q/xp2ucg4KCgoKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0Ew
cQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAfEEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU
9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDAj4oAAAAASUVORK5CYII=
--------------070302070403010602020300--

--------------050405060704030000080403--

From rlb@ipv.sx  Thu Jun 13 07:36:04 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC8121F8ECE for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.083
X-Spam-Level: 
X-Spam-Status: No, score=0.083 tagged_above=-999 required=5 tests=[AWL=-0.273,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1, SHORT_HELO_AND_INLINE_IMAGE=0.781]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5FLZU6xfnNOv for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:36:00 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 630F321F9A93 for <jose@ietf.org>; Thu, 13 Jun 2013 07:35:59 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id ef5so15133324obb.15 for <jose@ietf.org>; Thu, 13 Jun 2013 07:35:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=BuMkka6wdfJTNKkG2ilFy1SgYk/B1IFkxZslMnvPDic=; b=pH7vmpIkAwLTAlPRXjsvHgteJG/7/G5VIi5B29pO+S5kls3wSTaxLWnTffFFckkV60 dpkKE6JJ6dyV0Tsi2CAnnpJ7efs45nYfMcK5+JLqAFwPu7foNl6jH0+/RwhHG5M7Umuu 9a+Pa1nc4/1Hc+GtgR2/DtybhgRFpoyeXgZJiPwHSFpLozr1EmEmcRP0EZbgpkb/znmx 6AIbqMd3w4OnJ5ik48qJkWui1BcJndVHnVA/9bYyWAsi4QpyxMzD2/v6kaFTtiN36uB2 yGPC0DCb+41iOVxEbbJmsiWo/sqEzS4e7TX7h3m/lPLooOspQyzBdgYQC+p/juxyAr4o iRtA==
MIME-Version: 1.0
X-Received: by 10.60.52.15 with SMTP id p15mr892901oeo.87.1371134158742; Thu, 13 Jun 2013 07:35:58 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Thu, 13 Jun 2013 07:35:58 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
Date: Thu, 13 Jun 2013 10:35:58 -0400
Message-ID: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: George Fletcher <gffletch@aol.com>
Content-Type: multipart/related; boundary=001a113309ce78b9f604df0a0c2a
X-Gm-Message-State: ALoCoQnQa1/jb4+2vNJNwg3M8S/BcmXAoMvvlacxKLZkSJKC3+me6VEnpmnLj1v6UU1xr2b3wfbQ
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:36:04 -0000

--001a113309ce78b9f604df0a0c2a
Content-Type: multipart/alternative; boundary=001a113309ce78b9f404df0a0c29

--001a113309ce78b9f404df0a0c29
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This would have been a nice discussion to have had 18 months ago, when we
were getting started.

I don't think it's compatible with the IETF ethos to say "Changes to this
document MUST NOT break existing code."  Otherwise, we're not doing
engineering here, we're cleaning up documentation and rubber-stamping.

What would be acceptable is to say "Changes must break cleanly with
existing code".  That is, it should be possible for a JWT implementation
to, say, process both "legacy" JWS syntax and whatever comes out of this
group.  That way, we could come to consensus on the best solution,
incorporating lessons learned from earlier work without being hindered by
them.

Would participants here consider it a acceptable for the output of this
working group to be incompatible with existing JWT implementations, as long
as it had the property that JW* objects in the new format could be clearly
distinguished from "legacy" JW* objects, so that implementations could
adapt their processing?

--Richard




On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com> wrote:

>  +1
>
> Breaking deployed code as raised by Brian, Naveen and others is a critica=
l
> consideration.
>
> Thanks,
> George
>
>  On 6/13/13 10:19 AM, Mike Jones wrote:
>
>  Jim and Karen, could you please do as Richard suggests and close this
> issue as =93won=92t fix=94.****
>
> ** **
>
>                                                             Thank you,***=
*
>
>                                                             -- Mike****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Wednesday, June 12, 2013 1:57 PM
> *To:* jose-chairs@tools.ietf.org; Mike Jones
> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
> (base64)****
>
> ** **
>
> In other words: Chairs, feel free to close/wontfix :)****
>
> ** **
>
> ---------- Forwarded message ----------
> From: *Richard Barnes* <rlb@ipv.sx>
> Date: Wed, Jun 12, 2013 at 4:55 PM
> Subject: Re: [jose] #23: Make crypto independent of binary encoding
> (base64)
> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
> jose@ietf.org>" <jose@ietf.org>
>
> ****
>
> To be clear, I structured my message in two parts for a reason, to
> separate the analysis from the opinion.  I acknowledge that I am but one
> voice here, and I'm increasingly hearing how alone I am :)****
>
> ** **
>
> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:****
>
>  <impartial-analysis>****
>
> So just to be clear on the trade-off the WG has to make:****
>
> ** **
>
> On the one hand: Breaking every existing JWT implementation in the world*=
*
> **
>
> On the other hand: Eternally binding ourselves to base64 encoding, even i=
f
> binary-safe encodings become available (CBOR, MsgPack, etc.)****
>
> </impartial-analysis >****
>
> ** **
>
> <personal-opinion>****
>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."****
>
> ** **
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base=
64
> is a hack around JSON; we should build the system so that when we no long=
er
> need that hack, it can go away.****
>
> </personal-opinion>****
>
> ** **
>
> --Richard****
>
> ** **
>
> ** **
>
> ** **
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:****
>
> I did at first find it curious why the cryptographic operations were over
> the base64url-enccoded values, but I was also very focused on JWE, where =
I
> think the field separation problem is less of an issue (at least now).  F=
or
> JWS, this would certainly cause problems without some manner of unambiguo=
us
> field parameterization.
>
> I will note that unescaped NULL is not valid in JSON, so it could be used
> as a separator between the encoded header and the payload.  I do find it
> interesting if JOSE could more easily and efficiently support other
> encodings.  However, I think that while this is an interesting thought
> experiment, it seems we're too far down the path to seriously consider it
> unless the current state were shown to be horribly broken.
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.****
>
>
> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
> trac+jose@trac.tools.ietf.org> wrote:
>
> > #23: Make crypto independent of binary encoding (base64)
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> > For both serializations, you already need the base64url encoded version=
s
> > of the JWS Header and the JWS Payload to preserve them in transmission,
> so
> > computing them isn't an extra burden.  In the JWS Compact Serialization=
,
> > you already need the concatenation of the Encoded JWS Header, a period
> > character, and the Encoded JWS Payload, so computing that concatenation
> > isn't an extra burden.  Given you already have that quantity, computing
> > the signature over it is the easiest thing for developers to do, and it=
's
> > been shown to work well in practice.  There's no compelling reason to
> make
> > this change.
> >
> > Even for the JSON Serialization, the only "extra" step that's required =
to
> > compute the signature is the concatenation with the period character - =
to
> > prevent shifting of data from one field to the other, as described by J=
im
> > Schaad in the e-mail thread.  So this step isn't actually "extra" at al=
l
> -
> > it's necessary.  It's also highly advantageous to use exactly the same
> > computation for both serializations, which is currently the case.
> >
> > Since there is no compelling reason to make this change, and since maki=
ng
> > it could enable the "shifting" problem identified by Jim, it should not
> be
> > made.
> >
> > --
> >
> -------------------------+-----------------------------------------------=
--
> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
> >     Type:  defect       |  encryption@tools.ietf.org
> > Priority:  major        |      Status:  new
> > Component:  json-web-    |   Milestone:
> >  encryption             |     Version:
> > Severity:  -            |  Resolution:
> > Keywords:               |
> >
> -------------------------+-----------------------------------------------=
--
> >
> > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:=
2
> >
> > jose <http://tools.ietf.org/jose/>
> >****
>
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>
>   ** **
>
> ** **
>
>
> _______________________________________________
> jose mailing listjose@ietf.orghttps://www.ietf.org/mailman/listinfo/jose
>
>
> --
> [image: George Fletcher] <http://connect.me/gffletch>
>

--001a113309ce78b9f404df0a0c29
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This would have been a nice discussion to have had 18 mont=
hs ago, when we were getting started.<div><br></div><div>I don&#39;t think =
it&#39;s compatible with the IETF ethos to say &quot;Changes to this docume=
nt MUST NOT break existing code.&quot; =A0Otherwise, we&#39;re not doing en=
gineering here, we&#39;re cleaning up documentation and rubber-stamping.</d=
iv>
<div><br></div><div>What would be acceptable is to say &quot;Changes must b=
reak cleanly with existing code&quot;. =A0That is, it should be possible fo=
r a JWT implementation to, say, process both &quot;legacy&quot; JWS syntax =
and whatever comes out of this group. =A0That way, we could come to consens=
us on the best solution, incorporating lessons learned from earlier work wi=
thout being hindered by them.</div>
<div><br></div><div>Would participants here consider it a acceptable for th=
e output of this working group to be incompatible with existing JWT impleme=
ntations, as long as it had the property that JW* objects in the new format=
 could be clearly distinguished from &quot;legacy&quot; JW* objects, so tha=
t implementations could adapt their processing?</div>
<div><br></div><div>--Richard</div><div><br></div><div><br><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 10:24=
 AM, George Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:gffletch@aol.c=
om" target=3D"_blank">gffletch@aol.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Helvetica, Arial, sans-serif">+1<br>
      <br>
      Breaking deployed code as raised by Brian, Naveen and others is a
      critical consideration.<br>
      <br>
      Thanks,<br>
      George<br>
      <br>
    </font><div><div class=3D"h5">
    <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim
            and Karen, could you please do as Richard suggests and close
            this issue as =93won=92t fix=94.<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u>=
</span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0
            Thank you,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0
            -- Mike<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u>=
</span></p>
        <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>
            Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank"=
>mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
            <b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=
=3D"_blank">jose-chairs@tools.ietf.org</a>; Mike Jones<br>
            <b>Subject:</b> Fwd: [jose] #23: Make crypto independent of
            binary encoding (base64)<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
        <div>
          <p class=3D"MsoNormal">In other words: Chairs, feel free to
            close/wontfix :)<u></u><u></u></p>
          <div>
            <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=
=A0<u></u></p>
            <div>
              <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">-------=
---
                Forwarded message ----------<br>
                From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.s=
x" target=3D"_blank">rlb@ipv.sx</a>&gt;<br>
                Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                Subject: Re: [jose] #23: Make crypto independent of
                binary encoding (base64)<br>
                To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailt=
o:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
                Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@tr=
ac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;,
                &quot;&lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@=
tools.ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@t=
ools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.=
ietf.org</a>&gt;,

                &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" ta=
rget=3D"_blank">michael.jones@microsoft.com</a>&gt;&quot;
                &lt;<a href=3D"mailto:michael.jones@microsoft.com" target=
=3D"_blank">michael.jones@microsoft.com</a>&gt;,
                &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank=
">jose@ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose=
@ietf.org</a>&gt;<br>
                <br>
                <u></u><u></u></p>
              <div>
                <p class=3D"MsoNormal">To be clear, I structured my
                  message in two parts for a reason, to separate the
                  analysis from the opinion. =A0I acknowledge that I am
                  but one voice here, and I&#39;m increasingly hearing how
                  alone I am :)<u></u><u></u></p>
              </div>
              <div>
                <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></=
u>=A0<u></u></p>
                <div>
                  <div>
                    <p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23
                      PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>&gt;
                      wrote:<u></u><u></u></p>
                  </div>
                  <div>
                    <div>
                      <blockquote style=3D"border:none;border-left:solid #c=
ccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class=3D"MsoNormal">&lt;impartial-analysis&g=
t;<u></u><u></u></p>
                          </div>
                          <p class=3D"MsoNormal">So just to be clear on
                            the trade-off the WG has to make:<u></u><u></u>=
</p>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the one hand:
                              Breaking every existing JWT implementation
                              in the world<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the other hand:
                              Eternally binding ourselves to base64
                              encoding, even if binary-safe encodings
                              become available (CBOR, MsgPack, etc.)<u></u>=
<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/impartial-analysis=
=A0&gt;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;personal-opinion&gt;=
<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">I have some sympathy
                              with JWT implementors. =A0It sucks to have
                              to refactor code. =A0But I think we&#39;re
                              literally talking about something like a
                              5-line patch. =A0And early JWT implementors
                              knew or should have known (to use a DC
                              phrase) that they were dealing with a
                              draft spec. =A0As the W3C editor&#39;s draft
                              template says, in big bold red print,
                              &quot;Implementors who are not taking part in
                              the discussions are likely to find the
                              specification changing out from under them
                              in incompatible ways.&quot;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">As PHB pointed out in
                              the other thread, it would be nice to use
                              JWS and JWE in place of CMS one day,
                              without the base64 hit. =A0We should incur
                              the implementation pain now, and get the
                              design right for the long run. =A0Base64 is
                              a hack around JSON; we should build the
                              system so that when we no longer need that
                              hack, it can go away.<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/personal-opinion&gt=
;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888">--Richard<u></u><u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                        </div>
                        <div>
                          <div>
                            <div>
                              <p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><u></u>=A0<u></u></p>
                              <div>
                                <p class=3D"MsoNormal">On Wed, Jun 12,
                                  2013 at 10:27 AM, Matt Miller
                                  (mamille2) &lt;<a href=3D"mailto:mamille2=
@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;
                                  wrote:<u></u><u></u></p>
                                <p class=3D"MsoNormal">I did at first find
                                  it curious why the cryptographic
                                  operations were over the
                                  base64url-enccoded values, but I was
                                  also very focused on JWE, where I
                                  think the field separation problem is
                                  less of an issue (at least now). =A0For
                                  JWS, this would certainly cause
                                  problems without some manner of
                                  unambiguous field parameterization.<br>
                                  <br>
                                  I will note that unescaped NULL is not
                                  valid in JSON, so it could be used as
                                  a separator between the encoded header
                                  and the payload. =A0I do find it
                                  interesting if JOSE could more easily
                                  and efficiently support other
                                  encodings. =A0However, I think that
                                  while this is an interesting thought
                                  experiment, it seems we&#39;re too far
                                  down the path to seriously consider it
                                  unless the current state were shown to
                                  be horribly broken.<br>
                                  <br>
                                  <br>
                                  - m&amp;m<br>
                                  <br>
                                  Matt Miller &lt; <a href=3D"mailto:mamill=
e2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>
                                  &gt;<br>
                                  Cisco Systems, Inc.<u></u><u></u></p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal"><br>
                                      On Jun 11, 2013, at 6:01 PM, jose
                                      issue tracker &lt;<a href=3D"mailto:t=
rac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf=
.org</a>&gt;
                                      wrote:<br>
                                      <br>
                                      &gt; #23: Make crypto independent
                                      of binary encoding (base64)<br>
                                      &gt;<br>
                                      &gt;<br>
                                      &gt; Comment (by <a href=3D"mailto:mi=
chael.jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a=
>):<br>
                                      &gt;<br>
                                      &gt; For both serializations, you
                                      already need the base64url encoded
                                      versions<br>
                                      &gt; of the JWS Header and the JWS
                                      Payload to preserve them in
                                      transmission, so<br>
                                      &gt; computing them isn&#39;t an extr=
a
                                      burden. =A0In the JWS Compact
                                      Serialization,<br>
                                      &gt; you already need the
                                      concatenation of the Encoded JWS
                                      Header, a period<br>
                                      &gt; character, and the Encoded
                                      JWS Payload, so computing that
                                      concatenation<br>
                                      &gt; isn&#39;t an extra burden. =A0Gi=
ven
                                      you already have that quantity,
                                      computing<br>
                                      &gt; the signature over it is the
                                      easiest thing for developers to
                                      do, and it&#39;s<br>
                                      &gt; been shown to work well in
                                      practice. =A0There&#39;s no compellin=
g
                                      reason to make<br>
                                      &gt; this change.<br>
                                      &gt;<br>
                                      &gt; Even for the JSON
                                      Serialization, the only &quot;extra&q=
uot;
                                      step that&#39;s required to<br>
                                      &gt; compute the signature is the
                                      concatenation with the period
                                      character - to<br>
                                      &gt; prevent shifting of data from
                                      one field to the other, as
                                      described by Jim<br>
                                      &gt; Schaad in the e-mail thread.
                                      =A0So this step isn&#39;t actually
                                      &quot;extra&quot; at all -<br>
                                      &gt; it&#39;s necessary. =A0It&#39;s =
also
                                      highly advantageous to use exactly
                                      the same<br>
                                      &gt; computation for both
                                      serializations, which is currently
                                      the case.<br>
                                      &gt;<br>
                                      &gt; Since there is no compelling
                                      reason to make this change, and
                                      since making<br>
                                      &gt; it could enable the
                                      &quot;shifting&quot; problem identifi=
ed by
                                      Jim, it should not be<br>
                                      &gt; made.<br>
                                      &gt;<br>
                                      &gt; --<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt; Reporter: =A0<a href=3D"mailto:r=
lb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>
                                      =A0 | =A0 =A0 =A0 Owner:
                                      =A0draft-ietf-jose-json-web-<br>
                                      &gt; =A0 =A0 Type: =A0defect =A0 =A0 =
=A0 | =A0<a href=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">enc=
ryption@tools.ietf.org</a><br>
                                      &gt; Priority: =A0major =A0 =A0 =A0 =
=A0| =A0 =A0
                                      =A0Status: =A0new<br>
                                      &gt; Component: =A0json-web- =A0 =A0|=
 =A0
                                      Milestone:<br>
                                      &gt; =A0encryption =A0 =A0 =A0 =A0 =
=A0 =A0 | =A0 =A0
                                      Version:<br>
                                      &gt; Severity: =A0- =A0 =A0 =A0 =A0 =
=A0 =A0|
                                      =A0Resolution:<br>
                                      &gt; Keywords: =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 |<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt;<br>
                                      &gt; Ticket URL: &lt;<a href=3D"http:=
//trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" target=3D"_blank">h=
ttp://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                      &gt; jose &lt;<a href=3D"http://tools=
.ietf.org/jose/" target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                      &gt;<u></u><u></u></p>
                                  </div>
                                </div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12.0pt">&gt;
_______________________________________________<br>
                                      &gt; jose mailing list<br>
                                      &gt; <a href=3D"mailto:jose@ietf.org"=
 target=3D"_blank">jose@ietf.org</a><br>
                                      &gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listi=
nfo/jose</a><u></u><u></u></p>
                                  </div>
                                </div>
                              </div>
                              <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
              </div>
            </div>
            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
    </div></div><span class=3D"HOEnZb"><font color=3D"#888888"><div>-- <br>
      <a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank"><img src=3D"cid:part21.04020107.07020=
504@aol.com" alt=3D"George Fletcher" height=3D"113" width=3D"359"></a></div=
>
  </font></span></div>

</blockquote></div><br></div></div></div>

--001a113309ce78b9f404df0a0c29--
--001a113309ce78b9f604df0a0c2a
Content-Type: image/png; name=XeC
Content-Transfer-Encoding: base64
Content-ID: <part21.04020107.07020504@aol.com>
X-Attachment-Id: 798c4a0d2637fa6e_0.1.1

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAACXBI
WXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAIJLiEoIGg
ETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlTp09Lly5dunTp
khC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLly5dB/rMr4ubm5ubm
5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc3Nzc3Nzcfgd34uzm5ubm
5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zFHGHAI0sR61oQpSxdUsuBrcbb
pFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL5KL61yAdzP0l4ytwdrCmZQ0B49ng
q9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5xhJQD0ijlA6g5aoPzQXA2i9znjMWcodl
l8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteBfaB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHn
u0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGz
l2e093YQJp4ZK4D+G+NGeT+oM131tF+h+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRG
mAkCkYsLFwDS//NGKvzbkoT3kJCBAD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o
0AicE+TFUiRou8QMPMH3hee3xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8
I6cn2B8meCh34eGjN6VerAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1
YO1qH6dbCKnhSYG5oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ6
9MW+HWD9Tu2S0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skj
ff0g+X5SBR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBN
v1lcAOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAYlnko
7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm+Bj0TqE4
h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9bF5rQRrpqG3v
Ct5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk00D+UBkr7oI2QPpS
CgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2qwt9Le26NjkA9faXTy79
AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3YG7o/SZiFChhSkm7DkLe+n1t
tYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HBdoFdC68EZ7ajSBEJss5l5/IM7hd6
qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2SiNe1wGvbXI153fwpnrSgWc/ws2y92v8
PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJmfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNp
dxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK6
3RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQd+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1E
j0GgzhSfuayglYmv/7gaaIn2W84tIN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqv
b/8C1AilmagDhgX6FnoPMGzxMnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUC
wLFVHq31B/NoD7P5ETA2O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgn
rBvSZgIG+Yo+GqxDcuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPo
K3/MPEATqdIiQEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJD
QtfUg0mloXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRv
LQkp3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAXQ8B7
LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZPAFvtzIyo
2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yMoDu4grVrTgMo
y8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJfOZ5ZoMXlTEpXQLuY
2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZEGcZ43wHdA+movjR47/b6
RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaBVxGvyrpeYM+yLs/6HuRrzh2u
FPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9lOZgn5ijt9wGfbJezT4I3PY4G1QW
jF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B91zfDX6/wIOlT+LjW0KJbwptCyoOupk6
L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGBLwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZ
EkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNCIWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+
G9grKgnuz35x32cROPa4Clpfgff1xGr3KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0
dTXrCT4p9s2GMVA6uqRnoZXwqFh86hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISL
IDZZ14XPhJK1S0WVXQ5BgUEjfM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJF
WNoq4IDeLh2CzJIZJ42dQL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B
+WN6SPNAVPLqbt4O0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7
gXzJ41LAV6D6Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0H
oqz6hbwIDFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNT
tARzuuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0fXAHU
FPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm5/fdHgE7
D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3cmrwrzUguJ7/
a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBuT9rl+6kw8FSbj3qH
wKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y2BpnVfZ8DSU9ixyt8itU
/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXOMlD/ZOGg5lMhIsn/81oWMP5q
KilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/uv90fnjZ82vBpQ1CXq8vV5VD4q8Jf
Ff4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSpUqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs
2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoUeP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48
kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMoOVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynM
cNSzKvCxstVUFLTLjplZPwNztWDxMcj5fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOm
ZRGIgXYvewOQ+htjlQSQVPtRVwgov9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g
9TblevUCkSLaaS/BVV8NdWWCeaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZ
Lsc8HtRHzkr2EZC9LXt4ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8
W/UqMvUHKHSq0J7gMJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwCl
su4jMQucu5z5HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZ
z1ch9JPQ/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPg
Afh1N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+GginF9
wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe3jjveb1L
79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jUkKkhU0EZrgxX
hv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k6oXAC0jnBbeAGCxi
JVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjCIFfUVQKpirVnVg64ZJrn
GkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQldQaC7us5lAaWqTHxtsB9xzkr5
AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6Rtuuag7JUPisvAGNdQwVjfxClDb2k
AWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBcQxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL
8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/qJoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lK
Qdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJimvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazho
Z0SschLk86w2FobUjm/TMy3gW0ye5TCA+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4
rE8LKwDpxbLnmifA6VZJ+61pkLgk9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULK
Q7mUyAE15oHjpHWXawNkdpJdzvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX
3KOOqVC1TalujUxgf5qdEOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKE
LZegyewqnT8YBj7f2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1j
LZgePz1+ejw0/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yu
v7n+5vrg98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQ
iynrI5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIhs05q
VsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/gi7EEGYq
BLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5llewH2laX3a4H
u5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcgbZIypRagLRXn1Yug
+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0VOoPmZWz96fHgfm8uRo+
kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1B1xTciv4SvDgw9i714Ph8Isb
LTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9EbyrMabKEXCdoXJmAmRPdk55egZi
vk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH41i7Z+BIaFO8VkZzDxjjPajg4CUQ+Cbk
B6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS79fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjt
rYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27Nezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82
fArjt4/fPn47tAxpGdIyBHJO55zOOf238eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHn
jT5vBAltE9omtP1PKvjvI93vRsI7dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjI
yMi7hf/u78O6D+s+rAtd0rukd0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf
7e+9tf9/iH+0HeoV9Yp65benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunL
pi9hwYkFJxacAFspWylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8
bo5sFhACUh3s7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9S
FX0HT0DyNOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNp
i1ffgJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUcTAS4
ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNiephdP6gOW
12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4KmeJcr8gu4urLX
FQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAEF/BbaS0AhoaefZI1
yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4WJkj6SFgn0ePgK/BY4+S
EXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjdvMqREr/AS8vrC1lDISX3VTnh
C35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgykjLn+22FtW0OZGzPD/5+/h29e0LR
zOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHMiX6y7xIwV9et9a//x7uVGCwGi8Fw+6fb
P93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8C
RxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eXlxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8
xGhB/wX9F/QHeae8U94JXehCl/+i/uO2j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5
FxCFYgvFFoqF6Xun752+F1jMYhb/69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNT
kU1FNhWB/J3yd8rfCWJ3x+6O3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZW
K6vwovqL6i+qw7bobdHboiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn4
0gFrWcva9/C+/bPnm5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHci
iOuqyRkAcnfpmVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhS
YWmZIQK0eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GB
vZVkMD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2RlshvQV5
pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn3/3wh+aw
8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV1V3RlYWzwbcz
r/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZajgMnpP0DfJ1htwp
lqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3Xzs4Ue9cyPWjcPjolY/O
nYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp+Tv7Fqi8pPjIlpMhJS1mYY4K
F3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+nvRwVPxkeWVO6PA6G89cf3th1Ci6N
iHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsticJZzlnOWy3s+KCgoKCjob8svsiyyLLLk
fZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcffABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74
iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5
SOcjnY/kbV//YP2D9X8xIvguAdvivcV7izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659t
x+F5h+cdnge7Ju2atGvS38Zdt27dunXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg
7w6A/o7+jv4OHJl9ZPaR2WCz2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9
+3vnm5ubm9v7neMsAy4U8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlI
SVKaXAkYKO4JG4gX4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8
HaTldBcjgHoZxeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG
/CAbdN2MceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAY
A1IleZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd73i97
+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsTs+HmTUi+
ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQu9QfDLNME9Q4
SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFafkM9cPRhUvEg8PM2
7U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1bqArEesefyO0JZxOelLjh
Ab5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbTNHBe0k3RjkFGR/uF9DKQkz+3
rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPwz3nlU6JTolOiIbZgbMHYgn8bL6VN
SpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYEa4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0
gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/
aMc/237mM5/5/MPe9yoS/13teDfl4t37905NQ01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9Zd
oA1taANFuhbpWqQrEEAAAXlTSt5Xe5tPaj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76Vu
IPJLbcUW0CJoJMeBNFMrmpsA8oiA+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5E
BPXkQKCIGKDNAWkVVXgMPGKJOABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEX
rBscJvEN2FYafjGPAdev8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4Tsw
FfT53vwtpEdZ4zN6gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYU
yB6Z/VXKc7Au8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90
hWx9cmZDYEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn
3Z1KQ2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMmS+tm
NNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJfQu5q+9cf
1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OKP+wLHlPNY70P
gHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA2T/Wrd7dyi95vuT5
kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdffPHFF1/8bXzbBdsF2wWg
M53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePdXOcLXODC327+rQRGW64t15b/
J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc85C8ulHQ6nU73B/43eTc14z+8W/Wl
CU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RKbUAK4GutKMjNzeUDfwSxRy6YcwJYLMqx
D9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZGbQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjx
ufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHTu4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I
0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hmgscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpN
oATJHZTDQG/nRGd3MAyTo6VZEHjYcNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2z
j4L2ncturwumROmK6RIY1kjnxQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5
x+4JjtOZvXIiILtJgr7wFSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2Dj
N1Dgq4B63haIcWlvpGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCu
V+c74HNlTWItiBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQ
Zyj2U9TpoOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrG
RNMM63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998Obaa1
mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdjn4x9MhZi
YmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUArWtEKIttFtots
B6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2oW1C2wQ4dPjQ4UOH
ga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0aNGiRYu8Ox/tO7Tv0L5D
XrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90rUAMkUZ41AVli2GxshLEE+Gl
zgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01C7QFak/ZBnIT+TNJD9p5MV63FpRp
2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWfljb6WWgeSrSTnpl0Ht43ph/xVyxqccT54M
Lz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBzYY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1
rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wEhg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB
4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcVpapgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP
4y5AbFzCgzefQvZcY520L6FswZIHO9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP
+Nf0PubtB47H1o3SS/AdZNjumwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/7
7BeIHhwcGPQIevRo8rJHCzjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9b
FU5/fGJSXG/IXF9xpysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0G
XWlDmLYd/Lr5l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok
20RwNBCzFRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvW
rFmzZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7be2/n
fTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDLgJf/xZco
31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAgcUHigsS8Oxp7
w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEmPEUMALu1BGCbNIwa
QBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De7uXeW54gjwvwL9gP9Jmm
ZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQOfXUScEU9D/0e4vbGJSZ1BfsP
9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9LkemgGd749c+JpBidVk0A+c17XTuGbB6
W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I3AykW/IE3XqQjlJIag5Sc3FKqgy63uom
9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEizNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+
CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQam
Y/VOQSOfKjerzIXXZXMbPt4Em8qeKLZuI/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8
ToakfInHM3tAzoDsMa5seLEzW3/hOKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1
odT4SA/IapQzLLYYmPqabliegmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpu
xGh4UTLmyNuz4LnE+ytDUTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCr
qcmq9TuIkbNW5XiD7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWd
E3dO3DkRXjR90fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA
0tJLSy8tDZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY
/Grzq82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQuh3r
dqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj257f3r5cj
dHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99AHRihisctG/V
jfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24bw8wlAx/FZIBokjW
w5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7mgSZc9NfaVHg+Fn9QUsE
xaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKrOTmOcKCiPdD5Ocid9A313cHv
cPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0VdClJ70UWuARg1kzYd1A32fdafQZur
fs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbObAHTaK2UoTDobb4PfQUIEnpkh4DJqi5T
B8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8Fa
zZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LL
gJnAHXHCFQupG9LfpI2CUZX7jvo2P+hXyw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHF
q7fV0wSEFw701i6DlG760ssMvh/qfih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSV
xz9CRp+UUq9uQF3/OqfKfgV2P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZh
kDYno2ruAwivrr9kOQ7SaO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z
774cWPJsybMlz8KNoTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuX
L7/PEWcFgQAyJA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C
1EXzFVNAquY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ
8IyqvKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Yy9s3
2Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE865Ky1j8vq
Dbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41PeOgYkbpj6Mf
QczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1OuRvJt+u1RO0Otlb
dWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/d35is8CJxGuTz0wE81Pz
4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7JDbMrPIuCjIPWFbcLgtcN77NB
o6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3oPj1Mqsj08E51zZZNkO+7yNvBdnh
dpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQddVx3GED23bPbTjAOEAX7+wPzuHKJfMs
iJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1wxYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk4
0KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWhouAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtb
EK+kafpToMyV4ikIUmG+0caDKCaCJAOIEY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyD
YUqxoWW+B9cM+9eZi8FnctUHzaqDXFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry
+ta/Gej2OLras8E0UnqrdADjOVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz
6yvub4WcMzHnE76E1AI5g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHO
Z5oniMG6IOUaMN5YwpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhP
aPWMS+HhPk+XvS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDb
BOdKW2PQ5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhK
iocmb1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbKZFSe
VT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7Ro8AV38I
qOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9dfHbxWbhQ5kKZ
C2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6NOP/xxNlhz7W9AKmY
FC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyANFJFiAriWsFC3H+TG+hf6
W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8Kq0Gj4dVTtfzALNX6U7VC4Ec
SZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7ILVDPsdSQAt5TvHf5FgaPaGOUR18w
V/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZT
QFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9ApBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFl
OGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+fIMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhq
ZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0
iGmihBwJWmM1g7Lg/Ez7WssPWi2aqd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E
18P/Efi9CLgREA26guYSxsXgfJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjb
gPO+rBMTQW7pKOh9BHLLvS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5
A9D3MW1wDQNrAfOt2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3
c3Nzc3Nz+yPe31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQb
KK0GkSAKaN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdA
d95znXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3RsI3
ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd5PFyMshd
RbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf20X5I35bwMtEA
Oc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRbQafI6+TvQVsjYrkJ
4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhhWk/lHmgtxWeulqCOsRfU
7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0CwHvj4wVHSngv9xjhn8zuN3h
2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skGheG635MJj9aA9YTRqq2DwgWL5gZ9
D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5WubVoOanDkzoTME3vCYKY0Aj/xyTKWv4c76
t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5ubu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4
iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQMmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1
E6H02Obtys8F342hUb71wVnN/2WR5SC2as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWn
P8mQfdTxOGgP2DZnXXFWAWePzA5x34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y
86+t4DiddCJ9LmjbssyuD8BVU74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3
AqZr9/gGRHVRTGsEoqe62fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7
IU28/SKhHWgX1J9cHcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPH
zPYgxqSPFFdA3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55Icht
lCRugS5Ht1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT
9me1gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy60UY
5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+rKcCH4pC8
EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db/xbWVSM5PaUG
FOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb2QmgdXattvkBG/Q3
pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5TIWhbQDOvMFB+UvIRAerR
N4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NPkIzSS2kSSEdERyJAVNJiXfVA
OS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRSA95+k7vF4gOJdeJfvTwDKSuevH14
FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keYwdnRct0WCFnPk5+lRoKjq2OwVhaUunIF
fSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGK
XJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf
9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYBy/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4
BWjrRIDTCdo1Vz+zE7x6eNbgOOT0zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBt
AVT4oOzXxVeB7q5pZf6ScLnPnfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5u
bm5ubm5/zB9OnHVd9P1M/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnk
BHldQEDAXXBtdHg7KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7V
BZSwYktrXAd5v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV
4c2r+IOJseAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bN
IAbrJ4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVtFdVk
MDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAqqowFsZ5B
YilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKrsbpdbQSap3ZD
PQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZjL/Cp4CNMEuT+aM/n
GgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSeAvMh85PU3dJ9cAyU7ruu
wdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/DYbjz4m47x8fw9PWd/XeiwedM
uWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDifKbuhZGXRkHNslXuV6kF8jVpi0gA
sUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8CpiX2S2C4aCgpfQnaGtWTTWDoFJpaeBSo
V7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pfg35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN
+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8TnUevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAW
jDet7XKiQVmbGpZmAF2kTyvfB6D1cj513QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Q
a2PQbQFXvN9Rv6GQ6nRGahLEzUgekvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOf
X8Dp5dyozoaURnGz3kwB+al6jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6
FYon6A3SeSkIFEno6AziqtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2ag
NBLNyQfSEKmBVBqUh/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjB
XssxxTYQXGWtJazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0v
C9nTc6zpCyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx
+RdIJdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ctZyx4
NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUAjk9yK4L4
QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4zT9BVwhcjyzh
Ed/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50feu8DGK5tlxYQLoj
jRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v7IHEZm94NRWUOP8evk3A
97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBnELw5X1L4CvDN75vtdQJMV/QH
DTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAAjSR/+QcwWHQ6OR/oBks9yAUtUPpa
Gwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQNstfSdGgd0qHpC2gltSechDskprs+glE
GaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9v
LqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/B
nuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5NbwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1Ma
vikIdalHnT/Qv979gEdOTk5OTg7U21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqq
MGTIkCFDhrz/D5BVq1atWrXqn4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFy
itsm2n1AacAGMQNYS7w4BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3
FHSbfBJNRsCXRpIetENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+s
Z9LTgCYuV2pbeLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C
7yGWwdlW8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVok
vMy8d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEgSvOK
WSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxVx6gXwJUp
7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71Bmo2TvuC6Kt5K
PiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/whtyHuhH6mpBuzfox
2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D5qOVdSWD64pYrVsMhiuG
XVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYUWVBkAfw85ecpP0+BOhXqVKhT
AeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfIwAoDKwys8Oe9/l9NXBPXxDXY2XRn
051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt524ufLn66+GmoVatWrVq1fn/5ChUqVKhQ
Ac7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl
0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byczn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgA
OHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8
FMR90d7pDfr5+qOeHcBpSu3xsi9kD7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTF
Xl96BL6i5BjvgqB/qZxO+hDUyXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwn
DGvNd0AqqQYaRoLutHel4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TP
ATlNFywNgKxlb1ak3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXS
KoBI0xJwgrCKQcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaC
uCS+YTuIg/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAag
ptijaSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD/YCk
Kj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og96s/AH0xa
fXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYPt2BItSHVhlTL
S2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u627rbuv+NgH6rfjl
B5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgsBovBoC5Xl6vLodTZUmdL
nYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkns05mnYTmC5ovaL4A8s3MNzPf
zD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225ug0unL52+dBrqUpe6/0U9X058OfHl
RBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6LV1cSJsEvF/cfO/McTIcNNvNXoFUXTVkK
RBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3Q
vQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao
4AE1HzVy1fMB44rgnMiKkNLGttZzH0gur/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxv
MgtZfCDjI8u57J/B/tDjc59KkPzGu53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ce
Df0AXNUdDrsK1g/eNkq/B4W+jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G
3RFRVGsGpsVyT3kV6CtTWP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7Nb
hIH0hWu36xY4Njj7u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgu
gBIkZFEUdFflnuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTW
SO3AMFDqRjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqu
rwzeH+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38IfR36
OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgntEuD2j7d/
vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz2cB5yXnJeen3
v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJEiRIlSgBDGcpQ4AY3
uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwYbHq06dGmR7C14daGWxvC
8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz5syZM2fynn8y9snYJ2PhZNGT
RU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfhd2fEnRF3RsCuSbsm7ZoEL8a/GP9i
POx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/HHx5xlg3yao+B0GBnBWOd21DNXCm9UDuw
Oh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhC
Fakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SOO1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73
W4D/EuMFwxLIrKwv698UHDuNelMiOFMdUzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lH
GMHw0KdPwDLIDbA8M7QE61JTTWM9yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8
iwZU8f8UnJ2yI23FQb9VO+66DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJ
b8GwWVfOcBxMM/UHDCXBMcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC
9HetAhGgmoU3uJppjygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJK
jnxcag5qK9FQGgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCe
iQ9FTdDq80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DE
fENpAiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycvgfo7
SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/EPpAfyY/k
R6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESlv7//5I7JHZM7
5iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ8Olrp6+dvgbJ0cnR
ydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpapWKZiGdA0TdM0uH7j+o3r
N8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95PvJ8BD3X9lzbcy1ImVKmlAlX
GlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifKJ8oH3rR90/ZNW/C/4n/F/wrk5ubm
5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1axAREREREQEtsltkt8iG++vvr7+/Hi71
v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1DmocxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X
+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+ISdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPA
Ucfx2tkd7DucJZ11QdbkSvIbEDvEEhEGZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYB
aXipVhVc4PNZ47s9N0GwpfWhgR+A7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk13
1RQLym7da7MA+xXNyxoOak/H5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9W
n91z5j487/q47qOeYF/ovcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjq
lq8c7DEcrHbwJaxK3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3Q
TQTXNe20+AI4Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6Vd
wCfiqigKan01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4
VFd+JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyrpXbg
HWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBTOcjZkDtM
1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0I/Iea1e1q9pV
kFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/m1rxbqqH/YL9gv0C
5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d+sfLN3rW6FmjZ5DSKaVT
SifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1L1BxUMVBFQflXWC9G9GucLnC
5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1nPWc9RwkzEiYkTAD8uXLly9fPoiZ
GDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rCMmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8
WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wpluiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKf
s5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpn
lk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWB
x+QLm542gVc1Ys4nrwDbaKLlGuCq7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw
4nXSw6RJ8Nh+6fMLJ+BZ8uMVD76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8q
cjLfd2C4rd9mHAq3H9w7cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y8
4QeVd1awlB0LxRsUeVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwf
mKf5VwXHx/ZLji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt
4v2R3zIw7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcB
K+ncBT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0GjhQh
LEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb0TaiLTyd
+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFxcXFxccBBDnKQ
/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se5S6Vu1TuEtyUb8o3
ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU+/3VFyvFSrES5F5yL7nX
b7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH5ZBySDmUN3XJuNW41bgVTMmm
ZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X56wvL5oHNA5sHQuonqZ+kfgJvD7w9
8PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfXSf7i+TFo5lE7uq0C525dfn45BGxeru72
6lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZrN9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8
cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYep8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GX
gcs3NdjSDoylwvsWqg7+HWpOKvkLONdnf2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36
CuxHIroWGA8v92a/theHZwUuRV44Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZ
Z59+Gbyc9mZRTEeIO5X0aXwW2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNc
YUIv7kPGzuxo+4+w75cjB0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qD
T2vfix4lodub9t5tqoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1
OrdGQOrKtFGp/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2M
mKEVA22QJrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEi
UCSBWoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9oNzc
cnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm1ZtVb8Le
2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCCEu+//tk9sntk
9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m8ZnFZxaDT0Ofhj4N
oerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pSVamqlLf9VsVbFW9VhOge
0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c6Huh74W+UCy7WHax7Lx4745L
o22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269GErZStlK2SCqR1SPqB6wK2ZXzK4Y
4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd
4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNS
n7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6
vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJT
El5Nva2/ehRelrg974YFUl5oE+kPuqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLh
o60FR3m1jLYPlDjDFIMF1IJqD9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5
qqme1xawVLeGak1BHem05Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3B
Z5xPCc9zUHZv8bji/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfB
ccrxNH0PiAeugY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD
1l59S35goXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0n
nRFZQF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUsmD4x
fWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1q9SvUh/2
3dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39behZL6S+Urmg6Ld
i3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk/ceLSopKikqC5NnJ
s5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/PfJh3QfFurnuthbUW1lrI
b444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/6ino5ub230S6dOnSpUuXhKhe
vXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2xrlhHWk8orCuypdQxSOyS3fH5Xbg/
70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0CP6PPC/8C4H85aHrIS1AXieZiOqirUs7d
fQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15
EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhDJOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSn
V5IGZ1ggt76H2fcc+B7yDPD8CuzdrOuslSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb
0KbLtbQUoI2qF7XBMd0+yzkNxBFRT+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEdu
B/IFeYBUFaQp0hKpF7BeMtMLHGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+S
tCzQJct2XT0wDNJflKeBOkc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcM
QveEhgRvgXyDw46GF4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6
roHQi9b6ieDaqNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY
7mzg6gOuyfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFl
oKR4tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX25fb
l0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c06aSTTjrp
vGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQnZtwLvDGr2fW
Q9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfFnthIeHr3+fzodWC+
73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3oJhqHp/pwGPxOSuAsuKg
boB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2fptkGgbVMlpH590FQm4oFiz+E
l8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKiXlHfBa8PJfaIqwKJ51M+T6oNjFNv
ij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGCXti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRH
ykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgr
spZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoMaWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZp
M1I/DDKL6KtGwMuPoqcnnobYVrFfvtoBnvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3A
EmFpaA+EJ8uftHpogLJSrSIuQnIuZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYm
riKc+fxCiUsfQsycV7WjNkDGXzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7h
nitgXNT7GL9AzJKEOYkx4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA
3GZuM7dB1biqcVXjwJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR
4EoxsA00EouPguCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4Mt
kHdLaKPiN+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZ
lDJOQkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7CawTMwV
OiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADynllQrw3K
APE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdSV7kD5kDjrnkO
xOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJgelkvq4CYZp4U50F8
L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMnopyFq5YuSL1aAj92xxNoW
6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+BC8evT7+WoHYbxO/i1sBrE0Y
oC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasPAqWJOl6eBLWB8qXNH7THlr3yKuRw
h7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/ocdXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/u
aP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumkk046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P
9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xkboDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh0
4lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8
dsaOFAit3TZrlxxgn5k7Z2kH2HbmquSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGC
cSDzrYgu8PDuxXmXdsOTUtdKXckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNe
z2McA/Gd+EmtBZ5IVybPF6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0
ZolYBba2ts9UfxDVzZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RI
MN6XsfIm6Iv0CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gB
GGKj+A70BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7
ymvW5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghvAQGf
+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8C94+cV5n
jiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARFwqfxzTP0HgF+
Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazvg/u1Z7OeCGKpZrd9
BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3ewgwDz/svyt0cDfENdgzb
5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQRz5TmELDaUdg3E8hA/ZlRBxLP
JmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4sQRaQzeUd2QtEJfZxA0Q1WuAC+aX8
SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2eUa8EpsW4LzeDvGYW4zqIQOWxkg9kD3lK
rgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7MZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke
5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/Wulp
FOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1
CXgyePq7zwHNzJFiKih3lQvqFtD8NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1
iGWAz0WwnbXFBGYBadXClW7gTnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olz
wlev6qeMgkznLc2LFIMeQY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs
7FPk88fg2pOyWZyEU112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwq
PBLMhuYQYxEoG0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUI
PDNeToo7DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3Z
mXAQki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssMohh4
X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN1CxaZ207
yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2ahrRoGzSNGU/
UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ksn4FYqnxghoP1pvWa
+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUOMEfIT7QvQD40n0sVon6I
GRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZb/mN/bvDO5100kknnXTSeZe8
deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vfgFudHt28nx9evHjp++w+KGuseTPk
gJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJYynhISEo69WIN+Md7NvtOhGw9slTL1ACC
y4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tBOWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjv
GweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDgXFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wz
ZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3ijTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh20
0cpp9TMQEcogMRm8ZfV2ehEQm6giioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CH
iCAEmDnN3XIxyAfKCh7zX+8f3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPl
TRDlRX4RCOYnZlGzMYhZvC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhD
bZCP5RwZAvSUuc1zIK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPL
uyC/li1kTpDH5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9
l52iW4LvPft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ec
MlvdLHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDEPCWA
rpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vjonUgw4KM
oXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCqgzvZ+6GxEMyN
ZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXILcwW7cCM56UMB1FQ
lmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6i3CQX5FfmQJmC6y6E+R4
83OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ205AJIHObdrkLaKxkkKvAvGBU
NB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUbMyfIieYrbRVwkm58B1Qhu5kBjBbm
A7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqrlhP0+fpTWoNSWASK3CDK8In5AYjsMqv5
CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywFnmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm
2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ
4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWsXbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGT
o1AJeB6RODHqI/C9Zw21Hof7616+ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0Z
R2dJ1D+E8hern+v9FaQUcVqdg0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx
8CCwdwp/bO0PCR2fjH7wHlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeB
vtBcDuIjkaycBCVazab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBG
UT4Dacqi8iSIb0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dg
NqIUW8CSaOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNa
SOQXm0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh1DR2
Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxVEoGOIi8P
wbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9CoKeTTjrppJNO
Om+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dGZQTfJq47mj/I0wHd
X52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3PTsPFK5e7HSkKvn1CS+Vt
CKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC9eVhoDR1+RyU8uZyMQrMytw1
pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu3/f9RoG6VPlRuQVmoNR4CNYEW3bb
aFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaRBQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWL
paj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0
XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsxsM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kY
LJnULepokCbVOQdGjJzFLTC/ZiTrQD4ww8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCo
JexKJWAB+/kUKMJ88RLED2KEmggiUviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLt
ApYUbbPPSZAVzL3KLTBe6qXYA4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHm
TtDvGkP07hDT49X0pJLw+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwY
bD9nHwUJW9yTExtCRAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzp
z6DInBKrssXAo9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+
v/qsUGizst2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJf
Gq6pZ7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ+iOo
iuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEXgLHETDYv
AhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbYWqh+YDxx3fNc
APOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WCmQvIzXIRDto1Zbj2
PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7ALiqDOo92Sh3AK+clnQfv
NM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJIE7IfEpRcBxxDLQvAWWd1sh2
CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTSSSedd8VbV5xfdo4Od24Ga7Btsr0b
hIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSClV0oe5264Uvr5ugO34U71pyOu1IKE2Fd1
ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/LftT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem
/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZrc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYH
gAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2zDcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcp
jdPmYrA1tRRXHoJyVOuk2UDV1BraObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1
ZXbjLrhWO4emvAJvZ2+Qpyt4i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFy
AiPlKtkfSKY4I0EsUpxcArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6
A8gysrCoCdJijjOXghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0
QmBZpPhaLoB1j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tf
DXJC5ltZovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Z
m0DGI+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf5X7Q
73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7HsxbIwYMCA
AQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fvZLLc/5383X76
pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUGYh+4/GKnwpO2Ly8o
F0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjSZqpjICXG9Deng/Os2TFh
DuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru9wYgk2wuQkBmkCVEZxArRCk1
C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVMXFfaQ8pUZ+2Uz8B9Wd40B4LMLqLF
ZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Ym+QcszlorbV26gegVlSrq7VAGaOMUCaA
SBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoa
KB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7mo80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCU
FVVFQaCW3IovqFYxSf0ItKHqYrUsyBSzsugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5
+Vz+DCKKcWIyEC+uKs1BPaw+spYCz0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oI
E+QB2cX4ESgiKtMElCxaDa0CGPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX
7EMhx4pM8ZmOQc5zER1C/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC
+6/yU8JPCT8lwNo7a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZC
m0NtDrU5BJ/7fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/G
H9nhP8VP/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3
Xdx3MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9SKnq7
JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs/KEmE+Mh
0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7lnOWOhaTaxiTm
g7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKWu6Dt13ppy8HSW/tE
k2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9biRxC5hUc0AxbwMeuAkVwx
k4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPVjWCZr23SpoH8Ue6iIrBJLhYl
QDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGguNtaCaCf6KQqIzqKLehXwECmqgmWJ
Za9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWf
A/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46CrCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs
/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JCvYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQl
cTjEX0rqkpQA3jNGY89OsLVUp5vX312gHog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7
uLi4uLg4GDp06NChQ6HBtgbbGmxLaz/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yH
Dh06dOjQAW5WvVn1ZtW09d27d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZ
smXLlmnH07Bhw4YNG8KSK0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW
0Ug9zj/jXcsVkz0me0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P8
9+1SKzh/ZK831c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8
DG70v9H/Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zc
M2nb/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPaeS4V
Xdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G+b+bt06c
vYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2wlo6dCjxMGhij
gbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHgGeEpaXkFkQ0ibyrn
wPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc1wYogRBb90HR+2XhyaNn
AU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYuMRVkLuOq+RwMRa+jFwazES3N
vSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5EdgXjevGhVADBRdBKBGq04RBYpBdZqD
fGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZY8C61dLGEgLWbBZpDQVrS0sRa00QBcxX
sizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqH
gTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+
jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkOWmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3
kjuD9ytPkNMKeht3jpRPwLUt8de4dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8h
iF/uPk0CRPZ73cNZAaKPOJt5Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu2
37f9vm3akPP8HvN7zO8BP7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFj
Isak3emPyzIuy7gsadsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL
07a70OtCrwu9oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1et
TLtwpJ7AUxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHv
Cnz3P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68tYVvC
toRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz7c+Vtv7U
qVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2IgwJHBI4JBAO
Tj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nuJrubQK21tdbWWgtT
f5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQR8BeS2dQ8plrjPIQv8JI
dhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs/hkgx/mAXpkTwV5B3tMbgOXX
pHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVbCFJOx1gUK0S2cE12noRVt9e3/rIn
EJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHcS32HeQLUjBah9QIxVpRTZkByHufzxHbg
XqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzMVP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHF
piQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7aylJ4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9G
LTmPziCnmZOwg7FZH+ndCMpLsU3sALW3OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQ
iRMWELPEbRqDsp4zLARVV2dyErR1yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQ
nBC0NjQpYx0Ic2f6JUcVCMsaUSR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnG
fn2mezzoQ71RugnmV8YJ/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1
cTQDo76saFSH5HuJ++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh
+s+2jZC0zpOJqSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd
6naq2ylQPlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2Wbus
XYbYybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/qRfW
0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D6Lmg54Ke
CyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RMq8j9VX/4I0rP
Lz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6du3Tu0hkyfpXxq4xf
/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0yN8r8D/aNaR7TPAYu9LzQ
80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJoPPcbDwnT9edGMmg7bbuSBoAc
5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2ik8gAFyv3U2Td4ExUWmpbwGfoRGj
bN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRY
ZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36JfB5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrK
soYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRN
dFR7gznS3IIEsU/8IoqC+qk6TpkKopJoI9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRX
ySdiQElR3lOmgTJZOSBegjpIW61tAeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s2
0ApbKlhOgBatfaglgzZHLaM1BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LL
Q/zE6LKPvoaEQbFfRD6DJOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjn
Pa+9u8BY4A1zjQbDTy/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSP
y5GgvzDWeDeB/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157
svUD0G97uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1l
KVlKlgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j7Xd0
jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqNzx+RWnF5
W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDBQTDuxbgX416k
TWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq1t1ad2vdhe2Zt2fe
nhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusESyxLLEgvki88Xny8ePvf9
3Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9qp//UOP+dPd+2g9c+ie8bncAc
rWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuSD6iRxhmxCDIe9GsQOBEyfpjhczED
LLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU6BkDPPFLIGxA1slOCRneC1zkUwiUbfZh
fAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCy
y5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLke
GKc8VVqA+EndrnwOcgFF+QKUFswTNUHMlS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5
zjxi7gXZXXY3u4I6Xp2lDAKlhdJG1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9
LF+D1lzZpuYFrYg6VYsBzUerptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/
Gaz97HvtOUA2MCeb30FSnleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBY
O1teqSr4Tg+wB5+DkFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7m
nll8JmT+IfvsQj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8
Ck0G3+CAHsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6it
v2n9Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc7nM5
bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVeEH87B/2s
PCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P/Zs6tJ1aqUu9
cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+qF3qlI05xhxjjpGW
SP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/omqbX6GbRzaKbQb6EfAn5
Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2fVM7/afG+W956/c422+GR74u
C2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6X7OM38DNKEuXZ8HwIuFuOzMj2E8r
JQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk1athEBn90OE8BhmaOeoETIXkCgGVvQqQ
mNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7v
OTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYr
OcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKwuCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj8
4rX4ECjPeAaA8bNsbGQA85ZcIzeCfEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1Wfr
K0D5QhujnQTlmvKTcAPjySqOg/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0x
WisPrnHJ2ZNagvkemzzbQJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXU
E9R62g5bLdClHGgmgtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsH
gWuwMznxIljzq3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1Mujn
Xf30M+B6qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepy
dbm6HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/BpD5M
GHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3gWOFY4VgB
X2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/aa0zFMRXHVPzn
9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKVq/+H/hqda3Su0bl3
r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7/FG7wkcLHy18FOyV7JXs
lf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83NNBduTb81/db0tETb08PTw9MD
yhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hOmHJ3yt0pdyG2e2z32O7/ej9I5U39
9F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4
c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56++CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Co
yavubi8ENKO62Ruim2vjEgaBry1koN4clGtGeTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4
CLhu3em8BXElkh0uN3i3aPvjpkKuKyElKvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzK
OibXa0iKTd4QvwmeTH5W79EeMPKJvNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqA
edzcb+4AJYc6QKkIyhpxSZ0P8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2Io
CLdyGx0sBTTsDUA8EIvpAcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL
7Eftl3weglWzZfRpBepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrij
XNWSZwA7GWd8Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwI
cyXIEyJUU0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+E
dA+pGPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWielGF
b9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYibp0Du8jxK
HA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ8/nlMMdC7ks+
quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61BA8RhSMojlj5vBi/8
427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGUMWqDskmrKN4HsVM9LU+C
2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZC+p1MVu1AFk5RFOQeeUDYoCu
ZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPAI3lTvAbpL0+YS4DmopQoD8Z7MruZ
FRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSBMkT0sihgWo1OnhVgmsYl8xjYfrVb7fNB
y2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkEwm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/v
WmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5
TT/rLATmSnfhlMNgrSt9jevguW8EEwfur7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczK
me+a7cFe3FHA7gX9oMeQW0CUUbbKOeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmN
Ca5NYIzSf5UvICi733d+pUDrhY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxx
yS+ddP4f5K0T5+wvwpcqfSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEp
ZY1FsjdoCeom+0SwvUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeB
fd76juYg5tP/dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD
4DnBHPaA3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7
nAPbYNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkto30a
gfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCrgtaaK3I/
qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39LmyPphLzETdArK/
+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g6my0PXoYxDpe9XvR
ETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvryOD3K8SfSpwSmxPs7/t4
rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/hwGUQPyuxY5Iv+F1QgyyT3jic
0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdfzdu/x3l/YgZXFsjRMWRtJsAvv62Q
zyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmUehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567
AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t94B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5l
r/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpHnb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM
1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0fABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuT
rREE/RxeJqcDAvSwatn7QmDTDD9ELAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34K
js/924acAv98wYMzHgKf4YHfh+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd
9l0B6miry+EPNLDN9fkFzHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLa
DyAqqweUPaBFWSLU7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSyw
y3zPpYIn0p0//kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZA
pnyh+YNrgNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdU
KuQZhJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTmZr+x
G4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc2gMc+wNq
8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHUos2WbaFAgaxZ
KnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7Y10a8CkYlc313pfg
XZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVoCKIMHxotQTRWc1IJLEnq
Ml8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0gbHKdeQoMyRf4At+IIuYo0N77
r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKmA42UL6wPQMmrxml9wZigR+AFsxUf
0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N73PXREiZEf86NiPYrtun2dqDvbO9t+MI
+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5
oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiPtHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9
HYPAG+xclLwFXKdTmiTaIHiCfxP/raDmU4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukU
Agpr27VeAHT4u4M8nXTSSSeddNJ5N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fy
J0ja4rE448F0uV7a20H4WMfDHD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZ
unnGgaOhfbX7BiT/fHmcawd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9A
rl0ZBhbYAA/tN5/eygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZV
cmjXwVbCMdP/DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG
2jFrfUdPMNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkD
nJXAW8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1jaakPA
PdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2zHbbVgos
IZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt2ggiUri9JcHd
xlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaII0aivha0VcJKELg/
cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18miY1AJvTXtDxOTjj9B7m
PgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+QYmAuENJIdom0Bs6Zxo3Ifme
UtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE7MlBOzz3IcvH5SoEbwTlgqPx6/eh
SA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwGfbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwF
tJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2vQdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYi
J+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/SG/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uor
n/EgylrzKQfBLOuNdn8JcoyR21sDjFtcNZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw
8Kw1LslvwLPdvcubB6zzNcU2GpQLSnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3
Qe/q6ZHyK6hu5bX2K5iFyC0ugN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0
fPXKuRN8WnuHG8GgzbBUtQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt
27QnIPYaXykVwPOV9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkByc
oMQ1A2t+tZzMA7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+
83jrxNk4rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZv
C2eS2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9belrLW
+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGYj7Qxtrkg
xxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kOZi1PG/dVwKG2
UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaKW1aCPty4Z9jAU8ez
1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRRE5QzYGYy7+hXwLmAFdIC
ZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POMvGA2MXd4J4MZbT4UA8GMZIUY
BpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkpd8lZ4Gnsfu2dBWYrJcrwgHWE9bTt
AehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2NbBJyFjwCQpyhx8G7pufyxUgh+pT9Spg
FvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aST
TjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7Ngki
MgdvlhGQqXCGW8piSH7pMynlNrCX5bIDKJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5w
t2eauyQUexw+uNYT6FOs5bS11yHXuOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF
9o1PWbBp6jTVBsoA5Tj3Qd4TLY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0Fdh
pcGh+qb41gXrOR+PZQTY7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIX
SBga/8Gro5BUJmFHbFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUO
zKmsk3fBXtZ+zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlw
PXdmSAiHlPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6
Dczn5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8YVnA
1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYkgKW1vbHt
KGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoBNQPSvgCW+mGT
p0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2qz/y5//t/Lvj9d/F
lsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Whb0nZEpKijXKvTYj5LPb7
V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzzdSoLIGcP/17hU0FL1AqpX4Hl
olxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3ehWpa84P7B9TppJogcMlovBfFXnoe8
6A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zPQQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P
6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyB
KXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5fNXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yW
B7/OGAG+eXz9/I6B7Ka7jY0g84veamfQtmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVn
p58WuPMUnJNcj2L3g/s9V1nnfNB3efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5Te
SpjSEERlYRHdwWxDOfEL0EyJU6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cK
aKiVtBogigpFpIAyR2uoHQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7Pcp
nrE/mI2VGWobUD6yzrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rt
hBbgPuo6l1gT3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhyb
kXYh7Hqq66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0Fr
Bq0ZtAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafkPZi1
I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/dVVocLHg
9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+zYmCba7VbY6BQ
/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2z69g+HrsKZ3A+MVV
N/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwBxjf6e/IUKM2VetbS4L5m
jHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW77ZVDBz1ZV/RPwBxknDMWgTDN
++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FEzayOQiPAf6Dvr+FfgPmDPsxZH4z3
jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2r
QE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBPs2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6
grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXlYXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf
2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv
2076tgJzjTbMkRsshe0bfKq9u0CNi4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3Q
smXLli1bQrPszbI3yw4NGzZs2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rp
abyr8a7Gu2BO8TnF5xR/8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X
7fDP6ue3y79r912779pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3S
fn9a7tNyn5aD8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/z
qzeNlz/y5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpK
SkpKggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v/0nI
9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJAAGihHeK
WhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0UOBIta7RwsOfR
/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeDtOnVvNPB2Kt/7bkG
Wjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNKguOc766g8WAbbf/eLwos
kbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+61fIleGaaK9VmYGnqkxBYAqy/
+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u8SW/hLCkLPNyR0LIjvCh2QMgZGv4
sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6foVLWK+Do4bcsXAP/+yF5s62G0DZZRxRe
CqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DUVsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2
j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTWBKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5
Gxi9PB7neFAKyIJmHRDzucVs4KYw5UfgKebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+
4jz45LBYZNS7C9TJ+yfvn7wfwh6HPQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOf
lPqk1Cel0oYsl15ZemXpFZh7du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF
5WHFyhUrV6x8d3pJpezFshfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7
SO0haYnOuiHrhqwbAm2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3fu
nJYIfvTRRx999BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym
/UyNnxo/NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue
7Xi24xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k1QhI
mSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv5XFQchCu
xoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78CaHVjfkjpDbKe
e63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzOtRa0Btply2VQY+Ql
mRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauPtLVg7W/v6jcXxCD1pqUI
qIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5YQwH8R6POQjGfX23uARKqLW9
zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1+KutAK9ntvMyeGd4XiR/BpwxJshP
QfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcrgAzgidIe9PpmG4qA0Vz3cXcFW0HrM6Uo
cM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYy
HNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCo
ZgG5DZgkXeIqiMqq1/4tiEuWamY38PWqjfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmt
rFZWp63v3LZz285t4cOPP/z4w4/hp3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDo
Rje6/etOMKkXWEuoJdQSCt563nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8Qc
E6Hqzqo7q+6E1RlXZ1ydERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Z
b5k0/SyusLjC4gpvb8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEH
bGMb2/jrNMrcKHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou
67iswB3ucAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa
82vPrz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvhYq3b
Z17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVKa3FJ+wzk
FHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+OTpAtMdvsrGPh
nPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAXcqkBiB0UUh6Dplm+
s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXpy10aaAlqe2Ul6C/MSPM8
WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOcva19CMhoqYrOgFUGmH3A1ds7
03kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtzzDCIa5b4fnJW4LnxUi4H7aIWYz0I
SoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9
zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVNL8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAn
uGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic
72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKy
FGh7tb3a3t+vF+fFeXEezCfmE/MJDDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+s
vy63ZYlliWXJm283s+jMojOLgredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9
+fXl15dDl2JdinUpBp/7fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5T
h+wf9HzQ80FPqFihYoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jRe
aE972r99P6lTA9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoV
K4jJYrKY/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2N
VxDwje/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQhxA9
8FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui+Ly05rWV
hcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXsq/0Ogdgssmpf
gTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz1NRzgG2pVkWrB+rX
VqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7bPvWrzlY6lg0bQtoxdXb
1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7UkqAky0psL5ADrCdUETw33JiMX
OH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2BfWu+qPlfZDzlfFyKzicjoP2xiDm
ynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4JyooBsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5
GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcboSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8U
ZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVL
lyyFKturbK+yHY7PPD7z+EzYennr5a2XIcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyB
mJiYmJgYuNvzbs+7PYFlLGPZH8uX+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E
3Ii5EQOzi88uPrs4JHdO7pzcGQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+
rT6rHat2rNqxtO6md5reaXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaH
bQ6DUudKnSv1BpXEVN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7v
Wq9ZxmYZm2UsTGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P5
38VbJ84+twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniG
ewKh8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIzW4Os
K8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG9N3eSE89
MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxXAs8+d0XnPVAf
KTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1QajWML8R4PPcZ4Al
AFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYjsERbTM0Aa1fyi2aQNDRx
XPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQnjtofuBN8PfYuir5wbJFW6kU
AREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5BpT+ahl1KhhFZVvzInh/9YxzDwTK
skXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjFYKzXW+sPwZbfOkULBLWlGGoZDXo1Y455
AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeberGhh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMq
k0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFC
Rwsdhenzp8+fPh8GMIABQMdCHQt1LATd5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT
8E3DNw0HhjOc4b9fn/o6qVvTb02/NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN
7fi2+mybv23+tvkhpkNMh5gOsD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+
1H9S/0n9JxCSMyRnSE6YcnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq
1KlTp04dUMup5dRy/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP
+DN/fVP+3f6dzv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4s
LbSrzcqeoNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+z
j3SD4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5XtkO
7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQfbtQ49MYu
J3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6geBQtwV+ACZp
Vn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0WrpwBYwnJWXy8XA8LMp
xJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALeFo6DZtITtH0gf21cYdFA
/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TNUr4tBOSXjJuMpUGP1qoHJoAw
Wxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALKWbWJlAmWry17jCYIG2aNNPQCYVEg
3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsD
dcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ec
Ow60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5
DIx4+73j7134u4d5UNB/poJa1X+1RvU/VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/l
f9rrGhT0n+DIkSNHjhx5DDPOpAph4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0G
L8+Obln3AHSsWuP797tA7vmcVFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj
4TUQRupZ+kLQGgjT5MXAVD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19l
f/R10D/mKXE3xN4oVqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNq
yxMWBaQk6aK0BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUH
JgNoZ/ReWhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzE
AeJo8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfAXT5V
L4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1ang/SupirD
QTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3wjeElkD7wDfA1
g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKsgyyd5H2ghQnLzZNB
/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysOrDiwIqyqt6reqnpQI6ZG
TI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZNBNMFLTXzLHRxRn9d5wS039bu
2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuDGqIvzO4Ckl08EuYGNnFZuAz6Df2u
OA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7o
sCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsRAs/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0
n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxX
rG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLeEK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10b
A0J37XbgI4h6NiTGlgjey55vPN9CvphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsM
fO18G90DQWppaGR8FhyV7d0tZ0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuA
cEv40fQiMJHzgh+sP1m3GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7
hOc+ZD3r7JhTHUyTDDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhc
QlggAgKTNIvwDuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPie
HAXma+ahoQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZ
odLLlV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuCOFWf
Li8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ3WU1CPvK
UC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5O8DV2vm9OwnC
cqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPlZfktW3kwP2FND8QA
RdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinfgDhNdwr7wVBNjrP4QI+X
OmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNXk6uC2NfwrHEDyHZDFVMMmOym
GcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8m2vKZTD0ML8p3QY668dMGvgmKoP8
44EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE26qDwWCYLntM+8CwyYh1EHgG+HsErBBo
o1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegfa98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+
F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVibTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF
8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3DeoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/F
vBfzHixlKUv/0QV1qcu/URL5r/qf9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577Vc
iJ9VOrNWFLgPCOPFuyCW9SxznYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2
Bj2ZD6UBIHzGEf87wAgxTk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6P
AO2g8r7rU5AOWxaZi0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8S
NxyML5qnhrwGOV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO
9Bh1sBIC3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqeh
sh3EtfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3fS/cg
LM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0wdxbtnAOv
xZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0JYWmOKNP7EO61
lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWFpeJZyDqUEcjZC2E7
QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFBj8efTpzvN3EOMLaH8Mz4
fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7emlnAJLWBfyqIy8SexpGg6srB
rJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8eNnRbDjx6umembugd0afeS89CyGz
m2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/MtgulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3
ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+sU023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8Q
Ks4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFDQS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlri
aPBleW+4h4A+0Rcv2MC/hQqm78H6uvVoaFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3Bf
AENV+TPPJtBDAzGeWJBek3poT4LdYR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73Vw
vZa/L30PRO6KjLV+D+ZmhkzxfciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUH
qC39zfJvgulJ613DaMitkfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8J
xqetqy0HwVfVH+lNANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA
4LetE3dAYKnaV28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i
+buHd1BQUFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+
Fb4UNwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO96Wd
IF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuHrXhlsNQJ
GRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B3aF86YsEb+Wc
vRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJA+ublnXmIuDPd77p
nAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DYJRXVuwK7qeM3gatc/iKl
C6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP17sl6/gsgYRgmx4H/vNZWKwf+
K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyoNADdhlGPAfmEcYI8B/Qs0jCB+oM6
S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/
5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEB
iEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoKCgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVB
U6yRYkfwt83skt0QxK/Nm0xRICq8rySBOk8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzP
xYfomyC/c94mXxEI1cIuh80GTzP/D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILY
Kqa0+TMwfBweEvMscNM2MawC+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeT
Cs4r6UVudwZPMU+7+M1gNlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/
PVC/VndKFhCXaFOkNuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0F
MV6YbNwJHBNKe78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQ
RweG+p6FwFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4j
UCQq5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQiwxm
zZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+qAkIttbGy
CDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCgoKCgx0n8sw1I
t/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3QKmQH5v/IqTXPn3w
2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZJeNOiMuIbRPyOvgauMq6
3gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVbZdD3SPsNkSDk+j92doDS5uIZ
xfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GNlaqaJoHniDDU9i5cnJ/0UfZYyBvm
i9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus9OS24H7LfTd3Kahn/a+5zoD5PVNAagzW
osa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsG
lnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTsdgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqm
gnLGv8h1CHy9PG/53gXfi/7VzgiwbpOyNQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+Ipe
CbQ0mkp2EMeq4WoEGMoLHcT5EPVqqCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhK
GV6V5oPQRUokDPy5gZvql+C/6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX
/S3BleVp7twBvhxa6X6QQo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcT
X4h0g+mc1l8s+ncP76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1C
fA1+nLn/wvqnoUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht
9fqWi2DYb3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSI
O5NgAOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O+nwt
RKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dAQQSxtt5e
HQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUKtNX7Q86p7Lys
geAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhTcLt/xorMNyC7t2u+
9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3cc712MC6XIqUfIO6bsBrm
iSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJZRIpDr523mm+KSAtFyaLyZDT
My/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+CJSril/7HJRx+hYFENfrMw0/QbHo
sDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSKX/peaQHVeXonB//uYR4UFBQUFBT0OPzp
GecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3I
CpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8X
vHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZqr4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupT
yJ+hJ+uh4J6cNStjARQLjdgpVgbDFsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN
+BHyxuodZAfkeIRo8wzwfK6MF/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6Pt
oVAsKeZa+HtgDGiLfRpIAfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+s
fgW2btapjtLgnuBq4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqW
TmuLoFj96JVRaXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBl
cdaS8sG/MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7
i6t1bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUyl8p+
AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57zffZz4NLu
WVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKgpeT/5HkWxPIR
7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8fDsIm9wB5EpAC0k4w
rk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6Hql9VeAnsXfXFMSvgl1Xe
TUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRxxqvRVSHvSb2++h0o7/gauVqD
4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFPOwQljsTPihwCruM+QVkKnin5y3Na
QpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXPdPdV53JwpnhSc7eB97hnuccL5u2mU6ZQ
YLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9YjXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0
GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGlKZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJH
Ka1AT1I3+G+DVo3njN0gp4k6NJAMmujtqqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZk
gRwupqgXwZFm+UQ8A3quPlhPBONGeY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD
1KUyB8qvB0+2ppv6QXR6fKmYlhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKl
SwuP9+nTp0+fPhAWFhYWFvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQ
flI1+Zn+kFik2pannwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6Y
XQd4EPFNQjXQr4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814E
x5l7qy/PAO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBq
Tr3B3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/ntnbnu
+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nahH4N3rK+J
ZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhNm01lgTlK3Yzy
cL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU8Lv8FfQXIWNM7j3n
p+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/ISVMsmMrJS9Qs8Lf11xN3
gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0ivmPYaF0NeD+cB7yhwnDJvMayG
hPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfIfcIEp2vcbn5L//sGduPGjRs3blyY
QBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzLL3D16u3b2dl/Xbxy5UqUCA+Ht97q379+
fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xPRITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3L
zMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2iKP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR
5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDv
sEWGjwNNU+3C26D3Er6jDQjzuCjEgFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5
/MoV6DFWyroTDilbKuj3P4KE6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh
3YRjvAVdarWMu9wRbg9e1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L
7QgI7cQD7ALhF8Mc0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEde
U8gemnEv5Qdgvvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUB
JV3MMMeDO8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQ
mZtR/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0EWm9K
0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8GkpWKuYs
q0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRrf90Hw6Ps3bt3
7969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2QWZmXl4gAGXLli4d
FQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRNEODpp4sVi4j4tT+P83n/
2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs83t6A/n8mq+7f93h8vsK4bdvG
xEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQiml3hVRQV8nbmQDCE2JrfSxIcYQY
NoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgYTHpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A7
6qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/
EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmnIHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w
24dObIH80dn709tByJ3IiJgtYGxoMfvrQsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0
V1yoXQBDSeNdxxG4fytvkh4Lvi6ub30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzI
c7l/0i3gK6029JlBLikvFdLBW0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9
yS3vAfCleBZkpYJ6mhm6FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDq
pU3wdwVHTfsFy0nwNgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGO
wbve7wJhgfyytTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+Q
VoVfg9zN/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1
O9jQfkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4uLAwO
Hbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c/nTinPzG
dePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdBv6xf8DUBsZQY
JX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdAC8EhW4GvhK8CZUGt
4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSulz4O98InjrZufLIPbpjRD
4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5NnQrpN+Pyi12BLyH0rsmxYL3
nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q2s34klgazHuksEAUXG+b9FLOafB1
0vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qwtwd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZ
uAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJeALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3
GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoP
IKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXPdTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCN
UXcI3UDtpx8Tb4G8XtIDdcDU39xQ9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHW
WGxF8RGgFxU+sgTAfljsYTwDJd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAF
PPPXfTj8IwW1y0uWLFmyZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L
9dtSO7s9LCwurjBOQdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1
HTIyFOUfnd+1a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE
6JDXHuRvBUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpID
oEUKL4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DMGahe
/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dpamlw93a3
8r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD3mzPGFdpkB4Y
LcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH+jVEVQqpEdISzCfF
COUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+bcpsfxjkf5P7TH4iJB9J
WZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/cn9peHAs81amFQyfS5H+3WB/
wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggLQSrNp7oMxhjjbnk82CvYo02twFbe
vNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubsEpnXQNmlfOf5EaK/jnreuhzi9xWvn3AT
xG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDrsWNRcPTna19d6grp+/P2pXUGZ72srintwD/K
MyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vuu7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrH
Kscqxx9/3wq2V0ddHXV11N/d+0JTMqdkTsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Ze
m3tt/u5n95/77yfo/6aqiqKqoKqqqmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z
+f3g9wcCilK4PXjwo4/eeqtw+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j
24K4j9ufnnGW65axxswAc0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE
8bDQ07ACpN32mJhloL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/Szo
GawVe4H4o6hZDoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4
//EPXU8NhLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbz
lfxvlL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U+prF
cg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBuXzVC6pm0
gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175/OF50XA+5dZ7
rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXzYhBWCvNNJ0DZL16W
loG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9vU1rwNDJ3N34BBSZFr4+
bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98pQbsTzze7szzkN6ITYEfQVtg
nB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmCmrtGjRo1atSosNb5cYlsGdkysiW8
/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af
2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3L
ti7bukB/+tP/736SQf/xFKUgkS1I2f4906aNGNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf
3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUVBQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3
ZNlicTh+v/+o6/+ogriP259OnLOs9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4
RIoB7XOttdYPpNZFR5ZbAuIh62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt
/SPBAPo1Suo24IFu1L8HvRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJH
zTth7dklWVvjoHTHSmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D
5EVy8pVP4EGCfVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfa
aTC0loeJ30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+
2T0S/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F7kU2
i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpcuvMx2OOZ
pnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V4Pb41FYPhkG5
F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2vg+OvnEq43R1SLms
V9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHixIkTJxaeHz9+/Pjx46FE
iRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUNGzZs2LABMjIyMjIyICoqKioq
Cjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn5u6su7Puzjo4fvz48ePHC8MXPC4u
Li4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQoVZWqSlWYkTsjd0YubC66uejmolCmTJky
ZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0WdpkaZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w
++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFr
xq4Zf/z9ubHmxpoba2B66emlp5eG8+fPnz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe
8LThacPTHl3b/7DNaZvTNqdB+U/Kf1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiS
viV9Szo4nU6n0wk1F9RcUHMBTJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5
oeeHnoc2MW1i2sQ8vnH1qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z
+32+gpng385IV6kyePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv
1i3Iy7Nao6LAaHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvt
zYgPx33c/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsC
aMNyW6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4flL7
luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5EhblTw7RI61
fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUzJhVi46JioidB
pDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5H4S+YCirTAebTfrc
uxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjteBUNwk6b+pcKAWsTw21L
f+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc3Ku9SfnNoHRqzPHi88H2vpwW
vh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fgbZV/PmAHxyaLKo4BY2v9Y6UEZFRJ
eeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHuobzz7uJQ8UTF80USoGTXMkLJb8F0yNQn
VAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyf
O++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJEyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6
ggTmUV/1bym6peiWorD80vJLyy8VfsVebm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPU
D6Hr1K5Tu06FnF05u3J2wcw9M/fM3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oeP
jpO7O3d37m7IL5dfLr/cv9+P5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlh
zwx7Zti/3s7U7VO3T90OJwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8p
flP8Jni35bst3235z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/
vjJ8ZfjKAN84vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7T
uHpc7+v/Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1
K9z26VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QIqUAa
Jr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqIAN1NSQRA
QgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID6U2mQ8rqrBrp
D0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4cfXutrvWws6O+7PO
bgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ9lsOOHqCb2vWK2nnwD/c
ednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn5mG3COlfZg9xfQkPWmdsy/kG
zCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1LFjPmd4wxoM/RnmdhuAdpt7KTYVc
MbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdztAiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJI
H5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODIjtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLn
GTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGTbWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuF
zYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0Ct
ZxhpOAN003xCd2Ct0FyoA9Jz4alF40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbD
tc4F7RS0WxDnX22/IIFZu3bt2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03
dt3Y38zgPnz9n1WkQ5EORToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJv
ht8Mv/nX9+Phkpqh5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9
G+VJBc+7wMxZM2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n
8bZO2Tpl629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW
5BosPrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpUq/b7
9gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6tlYehHhu
6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0eJm8GVoi9dS8I
n+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKmhSC1NW3Q1oHwjCzK
rUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgocRqFRycYQ5S3hVn6ECE/E
iLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCkR5ioNof1T2iVyYMTNkPd0oNB
25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e2jZwp+SNTs+BQKQvJL8j2GuY20iv
QWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC
6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNBnyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/
Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtOCdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVf
BHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3uaBsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH
+VNQ5G7Rj0sdgbDXw0fGLwV/28BUqTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR
7jmyR6QOAm2GMTJ0GDBffVl4E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxa
sXHjxo0bNxbOCP/R9ZgLapsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQ
Tgonhd98Na4N0AZoA37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAE
JzgBdKMb3f746/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E
/6PvzweJHyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16Qm
NWHzzM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBbt1q1
ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/YGWfzcVcD
uTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNAHCItQgHKaudZ
CPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGmHiRt9E0yFoUrSzLH
6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWET8WODAblTTXTuwwC9QNL
vSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2WdcZDvIyhpid4dEQPlo8rVDzkF
1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3MseRJwRavJNAg9Ffpz5BiIHZfoK5EL
ifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30NqfvTOuZch3M7L5dL+xByt3pD/CvA1tfe
OiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUUy486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSA
MgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEH
QBVxWatD1IionxzfwJPnypVNOA+h4baPQgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/i
Cyjbo3hGORkqHKpYv1YLsCeFfJf4M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvn
T7x46hSkHsrqd/MoqBHmapZU0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtN
lb2Pb6AWJLDFixcv/tsPkoL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDC
gQowadKkSb+txWvRvEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyX
Zr80+yVYKCwUFgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYR
thG2whrnGsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPt
wvYf/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86vnfv
tWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3+fm/rtf8
6FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG6ufg/NwbuZn9
ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08tSkLzledeTk3YO2s
dec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf4CVqC59D4Cn/Lf08iH6p
HTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5Kr5v3wglXzctPDsHskqHp+aM
BvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7NE6/a34Z7FczNS9wD7Xbe7rQx4Oua
2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAsoXf0tIG1nTrQwAFzFPBfVXHDN0p837AYx
Ri6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwno
s4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKl
Y2IrBCB0onQg/mWwbQibhQ+Uyq4zTglSRiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+
okHIfLCPdxjCVoH5A/tsSyXw5ftKCXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQ
vu72gOsmyGueq90pAx6MhvBPQR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTx
LeAZ2ujV/88g6fT4BmxB7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gN
ozaMglEZozJGZUD0neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej
70bfhTTSSHsM/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1A
faA+UIcHox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWI
eqTwZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/HX/h
zY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2h1Ue3n/U
4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv/uST/2iCpyDu
4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFfjPsFjw9sxvB5EYtB
vaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75KfQWE3oYnDeXhZon7SRdW
QPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5GSo8iN9gSAJrd2tRDoJaQW0t
PgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36sBUBviiAkgHhQF5V3wF/TWTGvMxiT
De3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W
3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXRlqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMv
g7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y
/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfE
KEsVuB2ecfv+cTDUk3da+kDUujA1thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8s
r7Tehpjc+E02BSJaRRaPygTDEPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW
0n4y7AJnVEpOSjfwrcwedC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDo
E+gZaAeBQ8pq31lQZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F
4cOHDx8+/K9PnIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OV
Ks8+O2MGVK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0D
k6lYsfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GOHDly
5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH546Dtj1g
XGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c97jmkLnAXcc9
BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5jGHBSb6VfBHGysEj0
g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bIKND8asdAKOidDTPU1aAs
slRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbUmOM9Bm+crfnuhW/hl+X7Lp36
ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTCd4TdjmgIYWdDy9ltYGkdeceSD3p9
fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW
9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIW
MC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN62
0z4BAobAKmk4uCbm/uh7EvI3+C4HngXJbM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSs
u1/10kYIxOvN8uaD9rH+tvAe5JdwV9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/
RmBEIBL0idp2dTrop9X+gfqgBgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7
wV8U/M9UsOzcnpV7Vu5ZCQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6
j9Y5/lf5/f+4Ztjnc7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3a
z+xst1tRIDTUYpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTC
uI/bn06clamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcM
y83dDG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArCFLGD
2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx03IyrCYbz
9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG78Kz5Sr0e7of
lJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5W80TIfRLR35UNIQk
hawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QXy4CS6NX0LSB/Uiq/WBfI
65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9FmwY3gmYSqkzTS2TX4ZQvbYD9km
Q9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1ls/01CPi1ndJT4C8aMBEDOTnpC7zP
QeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfkNr59Mn0TuDpmpST1BeW8sij9I7B1t3+p
fQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2gVNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8a
tBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLph5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9
AstYxjKAoQxl6J9tNSgo6HF44onSpSMi4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHi
ERFw9uydO5mZIIqhoSEhEBY2ZMgXX/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/
+tPcfj8kJPxaQBEWZrFIEmRliaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9H
VSE5OTfX7y+M+7j96VKNB40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/Te
HkdCIG+O/pVcDYpcbVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9
IEGNXFcpF852veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4
Wd+mrwJ9mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqE
W0zOSu9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQL3tm
590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkzgL+M+pHi
Bf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21IIDJbXrPuA+0
zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBMYHsgA9QG0mLhTZBi
jMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmXu0FufprHPxPUE2wJ/AJy
nNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+HhBoIpwGPUH4WVwFvC9uk74A
XdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+QlZWT43RC375vv/3113Dx4rVraY/j
JotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnPPTd27KJFcPr0tWv/aJ3ox6V69bJl4+Ph
xx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t15vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8
wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9bbn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgTh
JCRMNr5cdBBkD3FXzbPDqYyT2qFZYClnNIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQej
hO/vdwN3hLQhcAu2n9hz8btL4Ovqp8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl
8oE/AeSFNDCfA3edPF/WQLi69lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2A
RXzN4AF9pYjWGJgibBVDQIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8
ufk6iJsymt8E5AnaPPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuy
ZmRdhhxnVn25E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ
/QQAmaZaMgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgo
qVwC9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+UvVoR7
i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0q/p9zQDa
Sf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp999o9v4vt/zZ9O
nC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AUTB/HRIZUB8MKZsib
IfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZMze+TBNBPBvyWuJC0Bdn
rksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294HAmsCy31TQN5hirA8A+pRbaM3
GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itFxK0G+xVXpKUD3EjdundNHNjnlUmr
3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8YJXQm2zQF+kX0UFIYgzHQaylRwulwdBY
T1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtAjrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRp
zoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73nJIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi
6LvFfvQD/RVhseACoTFLhATQv+BHcS3oU4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTac
MBwG+XRIo7A7YJlhmWH7CcwO4zrzYYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT
+mx2Q+N3Grq7TwBnEWegyTsQ0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPH
hWHwnXvFnU13wf9ufs4FDyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1Hjt
HGiDlZP6pwCUp8nfPcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+
Fffibt4CuXvUK+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrW
M2YK6B3lm4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymA
b6zrmfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/OA54Q
hodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDgPereCUJe
7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7MeM3VGzI/dZcM
TIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6znAzJBjBGHiU+BGGV4
3/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGqNZAO2oyMxik1oGnxZzuX
bgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDbYogaI1e05IM+jmrmJZBYrOj+
5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0QPzcso9grkHTYvUN/EXZe2PbJfhck
z8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgRhiflX5fPCc45BwUFBQUF/Q/xp2ucg4KC
goKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0EwcQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAf
EEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDA
j4oAAAAASUVORK5CYII=
--001a113309ce78b9f604df0a0c2a--

From gffletch@aol.com  Thu Jun 13 07:42:37 2013
Return-Path: <gffletch@aol.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7605521F9AC8 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NmiBjdV-CDrm for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:42:37 -0700 (PDT)
Received: from omr-d08.mx.aol.com (omr-d08.mx.aol.com [205.188.109.207]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDA321F9AC4 for <jose@ietf.org>; Thu, 13 Jun 2013 07:42:34 -0700 (PDT)
Received: from mtaout-mb06.r1000.mx.aol.com (mtaout-mb06.r1000.mx.aol.com [172.29.41.70]) by omr-d08.mx.aol.com (Outbound Mail Relay) with ESMTP id 4C7A5700028C1; Thu, 13 Jun 2013 10:42:25 -0400 (EDT)
Received: from palantir.local (unknown [10.181.176.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaout-mb06.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 7DA41E0000A4; Thu, 13 Jun 2013 10:42:24 -0400 (EDT)
Message-ID: <51B9DA50.1080807@aol.com>
Date: Thu, 13 Jun 2013 10:42:24 -0400
From: George Fletcher <gffletch@aol.com>
Organization: AOL LLC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Richard Barnes <rlb@ipv.sx>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
In-Reply-To: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040304010605040607060607"
x-aol-global-disposition: G
X-AOL-VSS-INFO: 5400.1158/91399
X-AOL-VSS-CODE: clean
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1371134545; bh=NJ1sb0OXVZebc1Mzc7x9Ix4kCWG+dvRp0s7OLfQ92YU=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=qPMi8lzGBx2XfHzVHlgGUAdgN7BaSsSGDetntWKXNbDMFk/eV5Z4QXeyfJ1lO6Hpm PtQWFp/Q+5LbyM/bmdwmC3fUaRFhuy9/3sCio4pILP4RjsZmwsoEszVOxL3oAfZMwm /H2+x/dZFkdOPx6WHWrH69TrlOl+GUOsryqpWusI=
X-AOL-SCOLL-SCORE: 0:2:515238144:93952408  
X-AOL-SCOLL-URL_COUNT: 0  
x-aol-sid: 3039ac1d294651b9da506aa8
X-AOL-IP: 10.181.176.48
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:42:37 -0000

This is a multi-part message in MIME format.
--------------040304010605040607060607
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

I think that in the current situation the issue isn't just breaking 
deployed code but also the timeliness of completing the spec. If the 
desire is to change the processing at some point in the future, why not 
complete this set of specs and then look to add the backward 
compatibility/migration strategy to an updated/future version of the 
specification? That's effectively what this would be anyway, and 
allowing other specifications and working code to be compliant with the 
current specification is very valuable and doesn't preclude revising the 
mechanism in the future.

Thanks,
George

On 6/13/13 10:35 AM, Richard Barnes wrote:
> This would have been a nice discussion to have had 18 months ago, when 
> we were getting started.
>
> I don't think it's compatible with the IETF ethos to say "Changes to 
> this document MUST NOT break existing code."  Otherwise, we're not 
> doing engineering here, we're cleaning up documentation and 
> rubber-stamping.
>
> What would be acceptable is to say "Changes must break cleanly with 
> existing code".  That is, it should be possible for a JWT 
> implementation to, say, process both "legacy" JWS syntax and whatever 
> comes out of this group.  That way, we could come to consensus on the 
> best solution, incorporating lessons learned from earlier work without 
> being hindered by them.
>
> Would participants here consider it a acceptable for the output of 
> this working group to be incompatible with existing JWT 
> implementations, as long as it had the property that JW* objects in 
> the new format could be clearly distinguished from "legacy" JW* 
> objects, so that implementations could adapt their processing?
>
> --Richard
>
>
>
>
> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com 
> <mailto:gffletch@aol.com>> wrote:
>
>     +1
>
>     Breaking deployed code as raised by Brian, Naveen and others is a
>     critical consideration.
>
>     Thanks,
>     George
>
>     On 6/13/13 10:19 AM, Mike Jones wrote:
>>
>>     Jim and Karen, could you please do as Richard suggests and close
>>     this issue as “won’t fix”.
>>
>>     Thank you,
>>
>>     -- Mike
>>
>>     *From:*Richard Barnes [mailto:rlb@ipv.sx]
>>     *Sent:* Wednesday, June 12, 2013 1:57 PM
>>     *To:* jose-chairs@tools.ietf.org
>>     <mailto:jose-chairs@tools.ietf.org>; Mike Jones
>>     *Subject:* Fwd: [jose] #23: Make crypto independent of binary
>>     encoding (base64)
>>
>>     In other words: Chairs, feel free to close/wontfix :)
>>
>>     ---------- Forwarded message ----------
>>     From: *Richard Barnes* <rlb@ipv.sx <mailto:rlb@ipv.sx>>
>>     Date: Wed, Jun 12, 2013 at 4:55 PM
>>     Subject: Re: [jose] #23: Make crypto independent of binary
>>     encoding (base64)
>>     To: "Matt Miller (mamille2)" <mamille2@cisco.com
>>     <mailto:mamille2@cisco.com>>
>>     Cc: jose issue tracker <trac+jose@trac.tools.ietf.org
>>     <mailto:trac%2Bjose@trac.tools.ietf.org>>,
>>     "<draft-ietf-jose-json-web-encryption@tools.ietf.org
>>     <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>"
>>     <draft-ietf-jose-json-web-encryption@tools.ietf.org
>>     <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>,
>>     "<michael.jones@microsoft.com
>>     <mailto:michael.jones@microsoft.com>>"
>>     <michael.jones@microsoft.com
>>     <mailto:michael.jones@microsoft.com>>, "<jose@ietf.org
>>     <mailto:jose@ietf.org>>" <jose@ietf.org <mailto:jose@ietf.org>>
>>
>>     To be clear, I structured my message in two parts for a reason,
>>     to separate the analysis from the opinion.  I acknowledge that I
>>     am but one voice here, and I'm increasingly hearing how alone I am :)
>>
>>     On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx
>>     <mailto:rlb@ipv.sx>> wrote:
>>
>>         <impartial-analysis>
>>
>>         So just to be clear on the trade-off the WG has to make:
>>
>>         On the one hand: Breaking every existing JWT implementation
>>         in the world
>>
>>         On the other hand: Eternally binding ourselves to base64
>>         encoding, even if binary-safe encodings become available
>>         (CBOR, MsgPack, etc.)
>>
>>         </impartial-analysis >
>>
>>         <personal-opinion>
>>
>>         I have some sympathy with JWT implementors.  It sucks to have
>>         to refactor code.  But I think we're literally talking about
>>         something like a 5-line patch.  And early JWT implementors
>>         knew or should have known (to use a DC phrase) that they were
>>         dealing with a draft spec.  As the W3C editor's draft
>>         template says, in big bold red print, "Implementors who are
>>         not taking part in the discussions are likely to find the
>>         specification changing out from under them in incompatible ways."
>>
>>         As PHB pointed out in the other thread, it would be nice to
>>         use JWS and JWE in place of CMS one day, without the base64
>>         hit.  We should incur the implementation pain now, and get
>>         the design right for the long run.  Base64 is a hack around
>>         JSON; we should build the system so that when we no longer
>>         need that hack, it can go away.
>>
>>         </personal-opinion>
>>
>>         --Richard
>>
>>         On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2)
>>         <mamille2@cisco.com <mailto:mamille2@cisco.com>> wrote:
>>
>>         I did at first find it curious why the cryptographic
>>         operations were over the base64url-enccoded values, but I was
>>         also very focused on JWE, where I think the field separation
>>         problem is less of an issue (at least now).  For JWS, this
>>         would certainly cause problems without some manner of
>>         unambiguous field parameterization.
>>
>>         I will note that unescaped NULL is not valid in JSON, so it
>>         could be used as a separator between the encoded header and
>>         the payload.  I do find it interesting if JOSE could more
>>         easily and efficiently support other encodings.  However, I
>>         think that while this is an interesting thought experiment,
>>         it seems we're too far down the path to seriously consider it
>>         unless the current state were shown to be horribly broken.
>>
>>
>>         - m&m
>>
>>         Matt Miller < mamille2@cisco.com <mailto:mamille2@cisco.com> >
>>         Cisco Systems, Inc.
>>
>>
>>         On Jun 11, 2013, at 6:01 PM, jose issue tracker
>>         <trac+jose@trac.tools.ietf.org
>>         <mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:
>>
>>         > #23: Make crypto independent of binary encoding (base64)
>>         >
>>         >
>>         > Comment (by michael.jones@microsoft.com
>>         <mailto:michael.jones@microsoft.com>):
>>         >
>>         > For both serializations, you already need the base64url
>>         encoded versions
>>         > of the JWS Header and the JWS Payload to preserve them in
>>         transmission, so
>>         > computing them isn't an extra burden.  In the JWS Compact
>>         Serialization,
>>         > you already need the concatenation of the Encoded JWS
>>         Header, a period
>>         > character, and the Encoded JWS Payload, so computing that
>>         concatenation
>>         > isn't an extra burden.  Given you already have that
>>         quantity, computing
>>         > the signature over it is the easiest thing for developers
>>         to do, and it's
>>         > been shown to work well in practice.  There's no compelling
>>         reason to make
>>         > this change.
>>         >
>>         > Even for the JSON Serialization, the only "extra" step
>>         that's required to
>>         > compute the signature is the concatenation with the period
>>         character - to
>>         > prevent shifting of data from one field to the other, as
>>         described by Jim
>>         > Schaad in the e-mail thread.  So this step isn't actually
>>         "extra" at all -
>>         > it's necessary.  It's also highly advantageous to use
>>         exactly the same
>>         > computation for both serializations, which is currently the
>>         case.
>>         >
>>         > Since there is no compelling reason to make this change,
>>         and since making
>>         > it could enable the "shifting" problem identified by Jim,
>>         it should not be
>>         > made.
>>         >
>>         > --
>>         >
>>         -------------------------+-------------------------------------------------
>>         > Reporter: rlb@ipv.sx <mailto:rlb@ipv.sx>   |       Owner:
>>          draft-ietf-jose-json-web-
>>         >     Type:  defect       | encryption@tools.ietf.org
>>         <mailto:encryption@tools.ietf.org>
>>         > Priority:  major        |      Status:  new
>>         > Component:  json-web-    |   Milestone:
>>         >  encryption             |   Version:
>>         > Severity:  -            |  Resolution:
>>         > Keywords:             |
>>         >
>>         -------------------------+-------------------------------------------------
>>         >
>>         > Ticket URL:
>>         <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>>         > jose <http://tools.ietf.org/jose/>
>>         >
>>
>>         > _______________________________________________
>>         > jose mailing list
>>         > jose@ietf.org <mailto:jose@ietf.org>
>>         > https://www.ietf.org/mailman/listinfo/jose
>>
>>
>>
>>     _______________________________________________
>>     jose mailing list
>>     jose@ietf.org  <mailto:jose@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/jose
>
>     -- 
>     George Fletcher <http://connect.me/gffletch>
>
>

-- 
George Fletcher <http://connect.me/gffletch>

--------------040304010605040607060607
Content-Type: multipart/related;
 boundary="------------050204080406070300090103"


--------------050204080406070300090103
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Helvetica, Arial, sans-serif">I think that in the
      current situation the issue isn't just breaking deployed code but
      also the timeliness of completing the spec. If the desire is to
      change the processing at some point in the future, why not
      complete this set of specs and then look to add the backward
      compatibility/migration strategy to an updated/future version of
      the specification? That's effectively what this would be anyway,
      and allowing other specifications and working code to be compliant
      with the current specification is very valuable and doesn't
      preclude revising the mechanism in the future.<br>
      <br>
      Thanks,<br>
      George</font><br>
    <br>
    <div class="moz-cite-prefix">On 6/13/13 10:35 AM, Richard Barnes
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com"
      type="cite">
      <div dir="ltr">This would have been a nice discussion to have had
        18 months ago, when we were getting started.
        <div><br>
        </div>
        <div>I don't think it's compatible with the IETF ethos to say
          "Changes to this document MUST NOT break existing code."
           Otherwise, we're not doing engineering here, we're cleaning
          up documentation and rubber-stamping.</div>
        <div><br>
        </div>
        <div>What would be acceptable is to say "Changes must break
          cleanly with existing code".  That is, it should be possible
          for a JWT implementation to, say, process both "legacy" JWS
          syntax and whatever comes out of this group.  That way, we
          could come to consensus on the best solution, incorporating
          lessons learned from earlier work without being hindered by
          them.</div>
        <div><br>
        </div>
        <div>Would participants here consider it a acceptable for the
          output of this working group to be incompatible with existing
          JWT implementations, as long as it had the property that JW*
          objects in the new format could be clearly distinguished from
          "legacy" JW* objects, so that implementations could adapt
          their processing?</div>
        <div><br>
        </div>
        <div>--Richard</div>
        <div><br>
        </div>
        <div><br>
          <div class="gmail_extra"><br>
            <br>
            <div class="gmail_quote">On Thu, Jun 13, 2013 at 10:24 AM,
              George Fletcher <span dir="ltr">&lt;<a
                  moz-do-not-send="true" href="mailto:gffletch@aol.com"
                  target="_blank">gffletch@aol.com</a>&gt;</span> wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div bgcolor="#FFFFFF" text="#000000"> <font
                    face="Helvetica, Arial, sans-serif">+1<br>
                    <br>
                    Breaking deployed code as raised by Brian, Naveen
                    and others is a critical consideration.<br>
                    <br>
                    Thanks,<br>
                    George<br>
                    <br>
                  </font>
                  <div>
                    <div class="h5">
                      <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
                      </div>
                      <blockquote type="cite">
                        <div>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim

                              and Karen, could you please do as Richard
                              suggests and close this issue as “won’t
                              fix”.</span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">                                                           

                              Thank you,</span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">                                                           

                              -- Mike</span></p>
                          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"> </span></p>
                          <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                              Richard Barnes [<a moz-do-not-send="true"
                                href="mailto:rlb@ipv.sx" target="_blank">mailto:rlb@ipv.sx</a>]
                              <br>
                              <b>Sent:</b> Wednesday, June 12, 2013 1:57
                              PM<br>
                              <b>To:</b> <a moz-do-not-send="true"
                                href="mailto:jose-chairs@tools.ietf.org"
                                target="_blank">jose-chairs@tools.ietf.org</a>;
                              Mike Jones<br>
                              <b>Subject:</b> Fwd: [jose] #23: Make
                              crypto independent of binary encoding
                              (base64)</span></p>
                          <p class="MsoNormal"> </p>
                          <div>
                            <p class="MsoNormal">In other words: Chairs,
                              feel free to close/wontfix :)</p>
                            <div>
                              <p class="MsoNormal"
                                style="margin-bottom:12.0pt"> </p>
                              <div>
                                <p class="MsoNormal"
                                  style="margin-bottom:12.0pt">----------

                                  Forwarded message ----------<br>
                                  From: <b>Richard Barnes</b> &lt;<a
                                    moz-do-not-send="true"
                                    href="mailto:rlb@ipv.sx"
                                    target="_blank">rlb@ipv.sx</a>&gt;<br>
                                  Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                                  Subject: Re: [jose] #23: Make crypto
                                  independent of binary encoding
                                  (base64)<br>
                                  To: "Matt Miller (mamille2)" &lt;<a
                                    moz-do-not-send="true"
                                    href="mailto:mamille2@cisco.com"
                                    target="_blank">mamille2@cisco.com</a>&gt;<br>
                                  Cc: jose issue tracker &lt;<a
                                    moz-do-not-send="true"
                                    href="mailto:trac%2Bjose@trac.tools.ietf.org"
                                    target="_blank">trac+jose@trac.tools.ietf.org</a>&gt;,

                                  "&lt;<a moz-do-not-send="true"
                                    href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org"
                                    target="_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;"

                                  &lt;<a moz-do-not-send="true"
                                    href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org"
                                    target="_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;,


                                  "&lt;<a moz-do-not-send="true"
                                    href="mailto:michael.jones@microsoft.com"
                                    target="_blank">michael.jones@microsoft.com</a>&gt;"

                                  &lt;<a moz-do-not-send="true"
                                    href="mailto:michael.jones@microsoft.com"
                                    target="_blank">michael.jones@microsoft.com</a>&gt;,

                                  "&lt;<a moz-do-not-send="true"
                                    href="mailto:jose@ietf.org"
                                    target="_blank">jose@ietf.org</a>&gt;"

                                  &lt;<a moz-do-not-send="true"
                                    href="mailto:jose@ietf.org"
                                    target="_blank">jose@ietf.org</a>&gt;<br>
                                  <br>
                                </p>
                                <div>
                                  <p class="MsoNormal">To be clear, I
                                    structured my message in two parts
                                    for a reason, to separate the
                                    analysis from the opinion.  I
                                    acknowledge that I am but one voice
                                    here, and I'm increasingly hearing
                                    how alone I am :)</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-bottom:12.0pt"> </p>
                                  <div>
                                    <div>
                                      <p class="MsoNormal">On Wed, Jun
                                        12, 2013 at 4:23 PM, Richard
                                        Barnes &lt;<a
                                          moz-do-not-send="true"
                                          href="mailto:rlb@ipv.sx"
                                          target="_blank">rlb@ipv.sx</a>&gt;

                                        wrote:</p>
                                    </div>
                                    <div>
                                      <div>
                                        <blockquote
                                          style="border:none;border-left:solid
                                          #cccccc 1.0pt;padding:0in 0in
                                          0in
                                          6.0pt;margin-left:4.8pt;margin-right:0in">
                                          <div>
                                            <div>
                                              <p class="MsoNormal">&lt;impartial-analysis&gt;</p>
                                            </div>
                                            <p class="MsoNormal">So just
                                              to be clear on the
                                              trade-off the WG has to
                                              make:</p>
                                            <div>
                                              <p class="MsoNormal"> </p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">On
                                                the one hand: Breaking
                                                every existing JWT
                                                implementation in the
                                                world</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">On
                                                the other hand:
                                                Eternally binding
                                                ourselves to base64
                                                encoding, even if
                                                binary-safe encodings
                                                become available (CBOR,
                                                MsgPack, etc.)</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">&lt;/impartial-analysis &gt;</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"> </p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">&lt;personal-opinion&gt;</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">I
                                                have some sympathy with
                                                JWT implementors.  It
                                                sucks to have to
                                                refactor code.  But I
                                                think we're literally
                                                talking about something
                                                like a 5-line patch.
                                                 And early JWT
                                                implementors knew or
                                                should have known (to
                                                use a DC phrase) that
                                                they were dealing with a
                                                draft spec.  As the W3C
                                                editor's draft template
                                                says, in big bold red
                                                print, "Implementors who
                                                are not taking part in
                                                the discussions are
                                                likely to find the
                                                specification changing
                                                out from under them in
                                                incompatible ways."</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"> </p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">As
                                                PHB pointed out in the
                                                other thread, it would
                                                be nice to use JWS and
                                                JWE in place of CMS one
                                                day, without the base64
                                                hit.  We should incur
                                                the implementation pain
                                                now, and get the design
                                                right for the long run.
                                                 Base64 is a hack around
                                                JSON; we should build
                                                the system so that when
                                                we no longer need that
                                                hack, it can go away.</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal">&lt;/personal-opinion&gt;</p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"><span
                                                  style="color:#888888"> </span></p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"><span
                                                  style="color:#888888">--Richard</span></p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"><span
                                                  style="color:#888888"> </span></p>
                                            </div>
                                            <div>
                                              <p class="MsoNormal"><span
                                                  style="color:#888888"> </span></p>
                                            </div>
                                          </div>
                                          <div>
                                            <div>
                                              <div>
                                                <p class="MsoNormal"
                                                  style="margin-bottom:12.0pt"> </p>
                                                <div>
                                                  <p class="MsoNormal">On
                                                    Wed, Jun 12, 2013 at
                                                    10:27 AM, Matt
                                                    Miller (mamille2)
                                                    &lt;<a
                                                      moz-do-not-send="true"
href="mailto:mamille2@cisco.com" target="_blank">mamille2@cisco.com</a>&gt;

                                                    wrote:</p>
                                                  <p class="MsoNormal">I
                                                    did at first find it
                                                    curious why the
                                                    cryptographic
                                                    operations were over
                                                    the
                                                    base64url-enccoded
                                                    values, but I was
                                                    also very focused on
                                                    JWE, where I think
                                                    the field separation
                                                    problem is less of
                                                    an issue (at least
                                                    now).  For JWS, this
                                                    would certainly
                                                    cause problems
                                                    without some manner
                                                    of unambiguous field
                                                    parameterization.<br>
                                                    <br>
                                                    I will note that
                                                    unescaped NULL is
                                                    not valid in JSON,
                                                    so it could be used
                                                    as a separator
                                                    between the encoded
                                                    header and the
                                                    payload.  I do find
                                                    it interesting if
                                                    JOSE could more
                                                    easily and
                                                    efficiently support
                                                    other encodings.
                                                     However, I think
                                                    that while this is
                                                    an interesting
                                                    thought experiment,
                                                    it seems we're too
                                                    far down the path to
                                                    seriously consider
                                                    it unless the
                                                    current state were
                                                    shown to be horribly
                                                    broken.<br>
                                                    <br>
                                                    <br>
                                                    - m&amp;m<br>
                                                    <br>
                                                    Matt Miller &lt; <a
moz-do-not-send="true" href="mailto:mamille2@cisco.com" target="_blank">mamille2@cisco.com</a>
                                                    &gt;<br>
                                                    Cisco Systems, Inc.</p>
                                                  <div>
                                                    <div>
                                                      <p
                                                        class="MsoNormal"><br>
                                                        On Jun 11, 2013,
                                                        at 6:01 PM, jose
                                                        issue tracker
                                                        &lt;<a
                                                          moz-do-not-send="true"
href="mailto:trac%2Bjose@trac.tools.ietf.org" target="_blank">trac+jose@trac.tools.ietf.org</a>&gt;

                                                        wrote:<br>
                                                        <br>
                                                        &gt; #23: Make
                                                        crypto
                                                        independent of
                                                        binary encoding
                                                        (base64)<br>
                                                        &gt;<br>
                                                        &gt;<br>
                                                        &gt; Comment (by
                                                        <a
                                                          moz-do-not-send="true"
href="mailto:michael.jones@microsoft.com" target="_blank">michael.jones@microsoft.com</a>):<br>
                                                        &gt;<br>
                                                        &gt; For both
                                                        serializations,
                                                        you already need
                                                        the base64url
                                                        encoded versions<br>
                                                        &gt; of the JWS
                                                        Header and the
                                                        JWS Payload to
                                                        preserve them in
                                                        transmission, so<br>
                                                        &gt; computing
                                                        them isn't an
                                                        extra burden.
                                                         In the JWS
                                                        Compact
                                                        Serialization,<br>
                                                        &gt; you already
                                                        need the
                                                        concatenation of
                                                        the Encoded JWS
                                                        Header, a period<br>
                                                        &gt; character,
                                                        and the Encoded
                                                        JWS Payload, so
                                                        computing that
                                                        concatenation<br>
                                                        &gt; isn't an
                                                        extra burden.
                                                         Given you
                                                        already have
                                                        that quantity,
                                                        computing<br>
                                                        &gt; the
                                                        signature over
                                                        it is the
                                                        easiest thing
                                                        for developers
                                                        to do, and it's<br>
                                                        &gt; been shown
                                                        to work well in
                                                        practice.
                                                         There's no
                                                        compelling
                                                        reason to make<br>
                                                        &gt; this
                                                        change.<br>
                                                        &gt;<br>
                                                        &gt; Even for
                                                        the JSON
                                                        Serialization,
                                                        the only "extra"
                                                        step that's
                                                        required to<br>
                                                        &gt; compute the
                                                        signature is the
                                                        concatenation
                                                        with the period
                                                        character - to<br>
                                                        &gt; prevent
                                                        shifting of data
                                                        from one field
                                                        to the other, as
                                                        described by Jim<br>
                                                        &gt; Schaad in
                                                        the e-mail
                                                        thread.  So this
                                                        step isn't
                                                        actually "extra"
                                                        at all -<br>
                                                        &gt; it's
                                                        necessary.  It's
                                                        also highly
                                                        advantageous to
                                                        use exactly the
                                                        same<br>
                                                        &gt; computation
                                                        for both
                                                        serializations,
                                                        which is
                                                        currently the
                                                        case.<br>
                                                        &gt;<br>
                                                        &gt; Since there
                                                        is no compelling
                                                        reason to make
                                                        this change, and
                                                        since making<br>
                                                        &gt; it could
                                                        enable the
                                                        "shifting"
                                                        problem
                                                        identified by
                                                        Jim, it should
                                                        not be<br>
                                                        &gt; made.<br>
                                                        &gt;<br>
                                                        &gt; --<br>
                                                        &gt;
-------------------------+-------------------------------------------------<br>
                                                        &gt; Reporter:  <a
moz-do-not-send="true" href="mailto:rlb@ipv.sx" target="_blank">rlb@ipv.sx</a>
                                                          |       Owner:
 draft-ietf-jose-json-web-<br>
                                                        &gt;     Type:
                                                         defect       |
                                                         <a
                                                          moz-do-not-send="true"
href="mailto:encryption@tools.ietf.org" target="_blank">encryption@tools.ietf.org</a><br>
                                                        &gt; Priority:
                                                         major        |
                                                             Status:
                                                         new<br>
                                                        &gt; Component:
                                                         json-web-    |
                                                          Milestone:<br>
                                                        &gt;  encryption
                                                                    |  
                                                          Version:<br>
                                                        &gt; Severity:
                                                         -            |
                                                         Resolution:<br>
                                                        &gt; Keywords:  
                                                                    |<br>
                                                        &gt;
-------------------------+-------------------------------------------------<br>
                                                        &gt;<br>
                                                        &gt; Ticket URL:
                                                        &lt;<a
                                                          moz-do-not-send="true"
href="http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2"
                                                          target="_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                                        &gt; jose &lt;<a
moz-do-not-send="true" href="http://tools.ietf.org/jose/"
                                                          target="_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                                        &gt;</p>
                                                    </div>
                                                  </div>
                                                  <div>
                                                    <div>
                                                      <p
                                                        class="MsoNormal"
style="margin-bottom:12.0pt">&gt;
_______________________________________________<br>
                                                        &gt; jose
                                                        mailing list<br>
                                                        &gt; <a
                                                          moz-do-not-send="true"
href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a><br>
                                                        &gt; <a
                                                          moz-do-not-send="true"
href="https://www.ietf.org/mailman/listinfo/jose" target="_blank">https://www.ietf.org/mailman/listinfo/jose</a></p>
                                                    </div>
                                                  </div>
                                                </div>
                                                <p class="MsoNormal"> </p>
                                              </div>
                                            </div>
                                          </div>
                                        </blockquote>
                                      </div>
                                    </div>
                                  </div>
                                  <p class="MsoNormal"> </p>
                                </div>
                              </div>
                              <p class="MsoNormal"> </p>
                            </div>
                          </div>
                        </div>
                        <br>
                        <fieldset></fieldset>
                        <br>
                        <pre>_______________________________________________
jose mailing list
<a moz-do-not-send="true" href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/jose" target="_blank">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
                      </blockquote>
                      <br>
                    </div>
                  </div>
                  <span class="HOEnZb"><font color="#888888">
                      <div>-- <br>
                        <a moz-do-not-send="true"
                          href="http://connect.me/gffletch" title="View
                          full card on Connect.Me" target="_blank"><img
                            src="cid:part26.04070101.03050201@aol.com"
                            alt="George Fletcher" height="113"
                            width="359"></a></div>
                    </font></span></div>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <a href="http://connect.me/gffletch" title="View full card on
        Connect.Me"><img src="cid:part28.08090700.06040604@aol.com"
          alt="George Fletcher" height="113" width="359"></a></div>
  </body>
</html>

--------------050204080406070300090103
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part26.04070101.03050201@aol.com>

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAA
CXBIWXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAI
JLiEoIGgETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlT
p09Lly5dunTpkhC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLl
y5dB/rMr4ubm5ubm5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc
3Nzc3Nzcfgd34uzm5ubm5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zF
HGHAI0sR61oQpSxdUsuBrcbbpFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL
5KL61yAdzP0l4ytwdrCmZQ0B49ngq9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5
xhJQD0ijlA6g5aoPzQXA2i9znjMWcodll8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteB
faB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHnu0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm
5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGzl2e093YQJp4ZK4D+G+NGeT+oM131tF+h
+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRGmAkCkYsLFwDS//NGKvzbkoT3kJCB
AD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o0AicE+TFUiRou8QMPMH3hee3
xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8I6cn2B8meCh34eGjN6Ve
rAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1YO1qH6dbCKnhSYG5
oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ69MW+HWD9Tu2S
0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skjff0g+X5S
BR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBNv1lc
AOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAY
lnko7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm
+Bj0TqE4h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9
bF5rQRrpqG3vCt5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk
00D+UBkr7oI2QPpSCgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2
qwt9Le26NjkA9faXTy79AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3
YG7o/SZiFChhSkm7DkLe+n1ttYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HB
doFdC68EZ7ajSBEJss5l5/IM7hd6qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2
SiNe1wGvbXI153fwpnrSgWc/ws2y92v8PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJ
mfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNpdxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE
+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK63RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQ
d+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1Ej0GgzhSfuayglYmv/7gaaIn2W84t
IN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqvb/8C1AilmagDhgX6FnoPMGzx
MnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUCwLFVHq31B/NoD7P5ETA2
O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgnrBvSZgIG+Yo+GqxD
cuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPoK3/MPEATqdIi
QEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJDQtfUg0ml
oXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRvLQkp
3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAX
Q8B7LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZP
AFvtzIyo2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yM
oDu4grVrTgMoy8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJf
OZ5ZoMXlTEpXQLuY2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZE
GcZ43wHdA+movjR47/b6RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaB
VxGvyrpeYM+yLs/6HuRrzh2uFPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9
lOZgn5ijt9wGfbJezT4I3PY4G1QWjF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B
91zfDX6/wIOlT+LjW0KJbwptCyoOupk6L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGB
LwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZEkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNC
IWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+G9grKgnuz35x32cROPa4Clpfgff1xGr3
KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0dTXrCT4p9s2GMVA6uqRnoZXwqFh8
6hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISLIDZZ14XPhJK1S0WVXQ5BgUEj
fM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJFWNoq4IDeLh2CzJIZJ42d
QL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B+WN6SPNAVPLqbt4O
0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7gXzJ41LAV6D6
Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0Hoqz6hbwI
DFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNTtARz
uuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0f
XAHUFPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm
5/fdHgE7D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3
cmrwrzUguJ7/a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBu
T9rl+6kw8FSbj3qHwKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y
2BpnVfZ8DSU9ixyt8itU/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXO
MlD/ZOGg5lMhIsn/81oWMP5qKilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/u
v90fnjZ82vBpQ1CXq8vV5VD4q8JfFf4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSp
UqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoU
eP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMo
OVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynMcNSzKvCxstVUFLTLjplZPwNztWDxMcj5
fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOmZRGIgXYvewOQ+htjlQSQVPtRVwgo
v9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g9TblevUCkSLaaS/BVV8NdWWC
eaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZLsc8HtRHzkr2EZC9LXt4
ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8W/UqMvUHKHSq0J7g
MJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwClsu4jMQucu5z5
HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZz1ch9JPQ
/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPgAfh1
N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+Gg
inF9wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe
3jjveb1L79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jU
kKkhU0EZrgxXhv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k
6oXAC0jnBbeAGCxiJVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjC
IFfUVQKpirVnVg64ZJrnGkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQld
QaC7us5lAaWqTHxtsB9xzkr5AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6R
tuuag7JUPisvAGNdQwVjfxClDb2kAWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBc
QxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/q
JoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lKQdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJi
mvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazhoZ0SschLk86w2FobUjm/TMy3gW0ye5TCA
+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4rE8LKwDpxbLnmifA6VZJ+61pkLgk
9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULKQ7mUyAE15oHjpHWXawNkdpJd
zvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX3KOOqVC1TalujUxgf5qd
EOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKELZegyewqnT8YBj7f
2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1jLZgePz1+ejw0
/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yuv7n+5vrg
98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQiynr
I5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIh
s05qVsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/
gi7EEGYqBLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5l
lewH2laX3a4Hu5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcg
bZIypRagLRXn1Yug+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0
VOoPmZWz96fHgfm8uRo+kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1
B1xTciv4SvDgw9i714Ph8IsbLTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9
EbyrMabKEXCdoXJmAmRPdk55egZivk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH
41i7Z+BIaFO8VkZzDxjjPajg4CUQ+CbkB6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS7
9fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjtrYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27N
ezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82fArjt4/fPn47tAxpGdIyBHJO55zOOf23
8eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHnjT5vBAltE9omtP1PKvjvI93vRsI7
dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjIyMi7hf/u78O6D+s+rAtd0ruk
d0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf7e+9tf9/iH+0HeoV9Yp6
5benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunLpi9hwYkFJxacAFsp
Wylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8bo5sFhACUh3s
7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9SFX0HT0Dy
NOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNpi1ff
gJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUc
TAS4ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNie
phdP6gOW12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4Km
eJcr8gu4urLXFQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAE
F/BbaS0AhoaefZI1yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4
WJkj6SFgn0ePgK/BY4+SEXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjd
vMqREr/AS8vrC1lDISX3VTnhC35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgy
kjLn+22FtW0OZGzPD/5+/h29e0LRzOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHM
iX6y7xIwV9et9a//x7uVGCwGi8Fw+6fbP93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25
i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8CRxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eX
lxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8xGhB/wX9F/QHeae8U94JXehCl/+i/uO2
j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5FxCFYgvFFoqF6Xun752+F1jMYhb/
69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNTkU1FNhWB/J3yd8rfCWJ3x+6O
3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZWK6vwovqL6i+qw7bobdHb
oiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn40gFrWcva9/C+/bPn
m5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHciiOuqyRkAcnfp
mVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhSYWmZIQK0
eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GBvZVk
MD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2Rlsh
vQV5pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn
3/3wh+aw8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV
1V3RlYWzwbczr/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZ
ajgMnpP0DfJ1htwplqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3
Xzs4Ue9cyPWjcPjolY/OnYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp
+Tv7Fqi8pPjIlpMhJS1mYY4KF3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+n
vRwVPxkeWVO6PA6G89cf3th1Ci6NiHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsti
cJZzlnOWy3s+KCgoKCjob8svsiyyLLLkfZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcf
fABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10
Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5SOcjnY/kbV//YP2D9X8xIvguAdvivcV7
izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659tx+F5h+cdnge7Ju2atGvS38Zdt27d
unXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg7w6A/o7+jv4OHJl9ZPaR2WCz
2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9+3vnm5ubm9v7neMsAy4U
8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlISVKaXAkYKO4JG4gX
4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8HaTldBcjgHoZ
xeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG/CAbdN2M
ceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAYA1Il
eZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd7
3i97+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsT
s+HmTUi+ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQ
u9QfDLNME9Q4SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFa
fkM9cPRhUvEg8PM27U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1b
qArEesefyO0JZxOelLjhAb5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbT
NHBe0k3RjkFGR/uF9DKQkz+3rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPw
z3nlU6JTolOiIbZgbMHYgn8bL6VNSpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYE
a4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O
7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/aMc/237mM5/5/MPe9yoS/13teDfl4t37905N
Q01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9ZdoA1taANFuhbpWqQrEEAAAXlTSt5Xe5tP
aj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76VuIPJLbcUW0CJoJMeBNFMrmpsA8oiA
+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5EBPXkQKCIGKDNAWkVVXgMPGKJ
OABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEXrBscJvEN2FYafjGPAdev
8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4TswFfT53vwtpEdZ4zN6
gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYUyB6Z/VXKc7Au
8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90hWx9cmZD
YEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn3Z1K
Q2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMm
S+tmNNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJf
Qu5q+9cf1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OK
P+wLHlPNY70PgHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA
2T/Wrd7dyi95vuT5kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdf
fPHFF1/8bXzbBdsF2wWgM53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePd
XOcLXODC327+rQRGW64t15b/J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc8
5C8ulHQ6nU73B/43eTc14z+8W/WlCU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RK
bUAK4GutKMjNzeUDfwSxRy6YcwJYLMqxD9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZG
bQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjxufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHT
u4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hm
gscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpNoATJHZTDQG/nRGd3MAyTo6VZEHjY
cNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2zj4L2ncturwumROmK6RIY1kjn
xQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5x+4JjtOZvXIiILtJgr7w
FSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2DjN1Dgq4B63haIcWlv
pGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCuV+c74HNlTWIt
iBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQZyj2U9Tp
oOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrGRNMM
63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998O
baa1mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdj
n4x9MhZiYmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUAr
WtEKIttFtotsB6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2
oW1C2wQ4dPjQ4UOHga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0
aNGiRYu8Ox/tO7Tv0L5DXrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90
rUAMkUZ41AVli2GxshLEE+GlzgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01
C7QFak/ZBnIT+TNJD9p5MV63FpRp2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWflj
b6WWgeSrSTnpl0Ht43ph/xVyxqccT54MLz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBz
YY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wE
hg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcV
papgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP4y5AbFzCgzefQvZcY520L6FswZIH
O9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP+Nf0PubtB47H1o3SS/AdZNju
mwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/77BeIHhwcGPQIevRo8rJH
Czjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9bFU5/fGJSXG/IXF9x
pysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0GXWlDmLYd/Lr5
l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok20RwNBCz
FRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvWrFmz
ZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7b
e2/nfTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDL
gJf/xZco31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAg
cUHigsS8Oxp7w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEm
PEUMALu1BGCbNIwaQBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De
7uXeW54gjwvwL9gP9JmmZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQO
fXUScEU9D/0e4vbGJSZ1BfsP9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9Lkem
gGd749c+JpBidVk0A+c17XTuGbB6W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I
3AykW/IE3XqQjlJIag5Sc3FKqgy63uom9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEi
zNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ
4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQamY/VOQSOfKjerzIXXZXMbPt4Em8qeKLZu
I/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8ToakfInHM3tAzoDsMa5seLEzW3/h
OKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1odT4SA/IapQzLLYYmPqablie
gmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpuxGh4UTLmyNuz4LnE+ytD
UTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCrqcmq9TuIkbNW5XiD
7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWdE3dO3DkRXjR9
0fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA0tJLSy8t
DZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY/Grz
q82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQ
uh3rdqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj2
57f3r5cjdHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99
AHRihisctG/VjfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24
bw8wlAx/FZIBokjWw5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7
mgSZc9NfaVHg+Fn9QUsExaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKr
OTmOcKCiPdD5Ocid9A313cHvcPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0Vd
ClJ70UWuARg1kzYd1A32fdafQZurfs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbO
bAHTaK2UoTDobb4PfQUIEnpkh4DJqi5TB8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0
j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8FazZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa
9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LLgJnAHXHCFQupG9LfpI2CUZX7jvo2P+hX
yw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHFq7fV0wSEFw701i6DlG760ssMvh/q
fih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSVxz9CRp+UUq9uQF3/OqfKfgV2
P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZhkDYno2ruAwivrr9kOQ7S
aO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z774cWPJsybMlz8KN
oTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuXL7/PEWcFgQAy
JA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C1EXzFVNA
quY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ8Iyq
vKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Y
y9s32Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE86
5Ky1j8vqDbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41
PeOgYkbpj6MfQczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1
OuRvJt+u1RO0OtlbdWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/
d35is8CJxGuTz0wE81Pz4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7J
DbMrPIuCjIPWFbcLgtcN77NBo6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3
oPj1Mqsj08E51zZZNkO+7yNvBdnhdpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQ
ddVx3GED23bPbTjAOEAX7+wPzuHKJfMsiJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1w
xYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk40KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWho
uAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtbEK+kafpToMyV4ikIUmG+0caDKCaCJAOI
EY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyDYUqxoWW+B9cM+9eZi8FnctUHzaqD
XFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry+ta/Gej2OLras8E0UnqrdADj
OVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz6yvub4WcMzHnE76E1AI5
g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHOZ5oniMG6IOUaMN5Y
wpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhPaPWMS+HhPk+X
vS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDbBOdKW2PQ
5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhKiocm
b1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbK
ZFSeVT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7
Ro8AV38IqOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9d
fHbxWbhQ5kKZC2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6N
OP/xxNlhz7W9AKmYFC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyAN
FJFiAriWsFC3H+TG+hf6W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8
Kq0Gj4dVTtfzALNX6U7VC4EcSZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7I
LVDPsdSQAt5TvHf5FgaPaGOUR18wV/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb
9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZTQFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9A
pBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFlOGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+f
IMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhqZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6
/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0iGmihBwJWmM1g7Lg/Ez7WssPWi2a
qd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E18P/Efi9CLgREA26guYSxsXg
fJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjbgPO+rBMTQW7pKOh9BHLL
vS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5A9D3MW1wDQNrAfOt
2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3c3Nzc3Nz+yPe
31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQbKK0GkSAK
aN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdAd95z
nXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3
RsI3ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd
5PFyMshdRbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf2
0X5I35bwMtEAOc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRb
QafI6+TvQVsjYrkJ4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhh
Wk/lHmgtxWeulqCOsRfU7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0
CwHvj4wVHSngv9xjhn8zuN3h2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skG
heG635MJj9aA9YTRqq2DwgWL5gZ9D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5Wub
VoOanDkzoTME3vCYKY0Aj/xyTKWv4c76t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5u
bu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQ
MmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1E6H02Obtys8F342hUb71wVnN/2WR5SC2
as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWnP8mQfdTxOGgP2DZnXXFWAWePzA5x
34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y86+t4DiddCJ9LmjbssyuD8BV
U74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3AqZr9/gGRHVRTGsEoqe6
2fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7IU28/SKhHWgX1J9c
HcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPHzPYgxqSPFFdA
3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55IchtlCRugS5H
t1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT9me1
gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy
60UY5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+r
KcCH4pC8EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db
/xbWVSM5PaUGFOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb
2QmgdXattvkBG/Q3pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5T
IWhbQDOvMFB+UvIRAerRN4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NP
kIzSS2kSSEdERyJAVNJiXfVAOS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRS
A95+k7vF4gOJdeJfvTwDKSuevH14FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keY
wdnRct0WCFnPk5+lRoKjq2OwVhaUunIFfSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ
3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGKXJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+
cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYB
y/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4BWjrRIDTCdo1Vz+zE7x6eNbgOOT0
zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBtAVT4oOzXxVeB7q5pZf6ScLnP
nfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5ubm5ubm5/zB9OnHVd9P1M
/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnkBHldQEDAXXBtdHg7
KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7VBZSwYktrXAd5
v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV4c2r+IOJ
seAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bNIAbr
J4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVt
FdVkMDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAq
qowFsZ5BYilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKr
sbpdbQSap3ZDPQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZj
L/Cp4CNMEuT+aM/nGgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSe
AvMh85PU3dJ9cAyU7ruuwdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/D
Ybjz4m47x8fw9PWd/XeiwedMuWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDi
fKbuhZGXRkHNslXuV6kF8jVpi0gAsUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8C
piX2S2C4aCgpfQnaGtWTTWDoFJpaeBSoV7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pf
g35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8Tn
UevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAWjDet7XKiQVmbGpZmAF2kTyvfB6D1cj51
3QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Qa2PQbQFXvN9Rv6GQ6nRGahLEzUge
kvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOfX8Dp5dyozoaURnGz3kwB+al6
jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6FYon6A3SeSkIFEno6Azi
qtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2agNBLNyQfSEKmBVBqU
h/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjBXssxxTYQXGWt
JazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0vC9nTc6zp
CyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx+RdI
JdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ct
Zyx4NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUA
jk9yK4L4QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4
zT9BVwhcjyzhEd/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50
feu8DGK5tlxYQLojjRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v
7IHEZm94NRWUOP8evk3A97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBn
ELw5X1L4CvDN75vtdQJMV/QHDTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAA
jSR/+QcwWHQ6OR/oBks9yAUtUPpaGwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQ
NstfSdGgd0qHpC2gltSechDskprs+glEGaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9
ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9vLqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7
ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/BnuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5N
bwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1MavikIdalHnT/Qv979gEdOTk5OTg7U
21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqqMGTIkCFDhrz/D5BVq1atWrXq
n4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFyitsm2n1AacAGMQNYS7w4
BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3FHSbfBJNRsCXRpIe
tENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+sZ9LTgCYuV2pb
eLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C7yGWwdlW
8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVokvMy8
d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEg
SvOKWSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxV
x6gXwJUp7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71B
mo2TvuC6Kt5KPiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/w
htyHuhH6mpBuzfox2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D
5qOVdSWD64pYrVsMhiuGXVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYU
WVBkAfw85ecpP0+BOhXqVKhTAeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfI
wAoDKwys8Oe9/l9NXBPXxDXY2XRn051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt5
24ufLn66+GmoVatWrVq1fn/5ChUqVKhQAc7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5
X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byc
zn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgAOHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2
FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8FMR90d7pDfr5+qOeHcBpSu3xsi9k
D7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTFXl96BL6i5BjvgqB/qZxO+hDU
yXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwnDGvNd0AqqQYaRoLutHel
4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TPATlNFywNgKxlb1ak
3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXSKoBI0xJwgrCK
QcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaCuCS+YTuI
g/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAagptij
aSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD
/YCkKj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og9
6s/AH0xafXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYP
t2BItSHVhlTLS2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u
627rbuv+NgH6rfjlB5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgs
BovBoC5Xl6vLodTZUmdLnYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkn
s05mnYTmC5ovaL4A8s3MNzPfzD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225u
g0unL52+dBrqUpe6/0U9X058OfHlRBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6L
V1cSJsEvF/cfO/McTIcNNvNXoFUXTVkKRBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA
4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3QvQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw
1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao4AE1HzVy1fMB44rgnMiKkNLGttZzH0gu
r/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxvMgtZfCDjI8u57J/B/tDjc59KkPzG
u53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ceDf0AXNUdDrsK1g/eNkq/B4W+
jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G3RFRVGsGpsVyT3kV6CtT
WP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7NbhIH0hWu36xY4Njj7
u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgugBIkZFEUdFfl
nuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTWSO3AMFDq
RjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqurwze
H+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38I
fR36OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgnt
EuD2j7d/vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz
2cB5yXnJeen3v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJE
iRIlSgBDGcpQ4AY3uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwY
bHq06dGmR7C14daGWxvC8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz
5syZM2fynn8y9snYJ2PhZNGTRU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfh
d2fEnRF3RsCuSbsm7ZoEL8a/GP9iPOx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/H
Hx5xlg3yao+B0GBnBWOd21DNXCm9UDuwOh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0
RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhCFakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SO
O1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73W4D/EuMFwxLIrKwv698UHDuNelMiOFMd
Uzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lHGMHw0KdPwDLIDbA8M7QE61JTTWM9
yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8iwZU8f8UnJ2yI23FQb9VO+66
DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJb8GwWVfOcBxMM/UHDCXB
Mcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC9HetAhGgmoU3uJpp
jygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJKjnxcag5qK9FQ
GgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCeiQ9FTdDq
80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DEfENp
AiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycv
gfo7SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/E
PpAfyY/kR6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESl
v7//5I7JHZM75iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ
8Olrp6+dvgbJ0cnRydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpap
WKZiGdA0TdM0uH7j+o3rN8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95
PvJ8BD3X9lzbcy1ImVKmlAlXGlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifK
J8oH3rR90/ZNW/C/4n/F/wrk5ubm5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1
axAREREREQEtsltkt8iG++vvr7+/Hi71v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1Dmo
cxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+I
SdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPAUcfx2tkd7DucJZ11QdbkSvIbEDvEEhEG
ZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYBaXipVhVc4PNZ47s9N0GwpfWhgR+A
7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk131RQLym7da7MA+xXNyxoOak/H
5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9Wn91z5j487/q47qOeYF/o
vcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjqlq8c7DEcrHbwJaxK
3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3QTQTXNe20+AI4
Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6VdwCfiqigK
an01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4VFd+
JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyr
pXbgHWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBT
OcjZkDtM1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0
I/Iea1e1q9pVkFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/
m1rxbqqH/YL9gv0C5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d
+sfLN3rW6FmjZ5DSKaVTSifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1
L1BxUMVBFQflXWC9G9GucLnC5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1
nPWc9RwkzEiYkTAD8uXLly9fPoiZGDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rC
MmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wp
luiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKfs5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0
rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpnlk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA
/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWBx+QLm542gVc1Ys4nrwDbaKLlGuCq
7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw4nXSw6RJ8Nh+6fMLJ+BZ8uMV
D76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8qcjLfd2C4rd9mHAq3H9w7
cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y84QeVd1awlB0LxRsU
eVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwfmKf5VwXHx/ZL
ji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt4v2R3zIw
7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcBK+nc
BT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0G
jhQhLEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb
0TaiLTyd+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFx
cXFxccBBDnKQ/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se
5S6Vu1TuEtyUb8o3ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU
+/3VFyvFSrES5F5yL7nXb7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH
5ZBySDmUN3XJuNW41bgVTMmmZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X5
6wvL5oHNA5sHQuonqZ+kfgJvD7w98PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfX
Sf7i+TFo5lE7uq0C525dfn45BGxeru726lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZr
N9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYe
p8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GXgcs3NdjSDoylwvsWqg7+HWpOKvkLONdn
f2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36CuxHIroWGA8v92a/theHZwUuRV44
Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZZ59+Gbyc9mZRTEeIO5X0aXwW
2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNcYUIv7kPGzuxo+4+w75cj
B0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qDT2vfix4lodub9t5t
qoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1OrdGQOrKtFGp
/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2MmKEVA22Q
JrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEiUCSB
WoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9
oNzccnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm
1ZtVb8Le2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCC
Eu+//tk9sntk9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m
8ZnFZxaDT0Ofhj4NoerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pS
VamqlLf9VsVbFW9VhOge0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c
6Huh74W+UCy7WHax7Lx4745Lo22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269
GErZStlK2SCqR1SPqB6wK2ZXzK4Y4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G
4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk
+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNSn7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1
B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687
wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJTEl5Nva2/ehRelrg974YFUl5oE+kP
uqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLho60FR3m1jLYPlDjDFIMF1IJq
D9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5qqme1xawVLeGak1BHem0
5Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3BZ5xPCc9zUHZv8bji
/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfBccrxNH0PiAeu
gY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD1l59S35g
oXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0nnRFZ
QF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUs
mD4xfWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1
q9SvUh/23dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39beh
ZL6S+Urmg6Ldi3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk
/ceLSopKikqC5NnJs5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/P
fJh3QfFurnuthbUW1lrIb444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/
6ino5ub230S6dOnSpUuXhKhevXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2x
rlhHWk8orCuypdQxSOyS3fH5Xbg/70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0C
P6PPC/8C4H85aHrIS1AXieZiOqirUs7dfQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl
5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhD
JOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSnV5IGZ1ggt76H2fcc+B7yDPD8CuzdrOus
lSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb0KbLtbQUoI2qF7XBMd0+yzkNxBFR
T+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEduB/IFeYBUFaQp0hKpF7BeMtML
HGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+StCzQJct2XT0wDNJflKeB
Okc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcMQveEhgRvgXyDw46G
F4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6roHQi9b6ieDa
qNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY7mzg6gOu
yfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFloKR4
tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX
25fbl0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c0
6aSTTjrpvGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQ
nZtwLvDGr2fWQ9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfF
nthIeHr3+fzodWC+73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3
oJhqHp/pwGPxOSuAsuKgboB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2f
ptkGgbVMlpH590FQm4oFiz+El8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKi
XlHfBa8PJfaIqwKJ51M+T6oNjFNvij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGC
Xti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRHykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5
Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgrspZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoM
aWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZpM1I/DDKL6KtGwMuPoqcnnobYVrFfvtoB
nvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3AEmFpaA+EJ8uftHpogLJSrSIuQnIu
ZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYmriKc+fxCiUsfQsycV7WjNkDG
XzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7hnitgXNT7GL9AzJKEOYkx
4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA3GZuM7dB1biqcVXj
wJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR4EoxsA00EouP
guCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4MtkHdLaKPi
N+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZlDJO
Qkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7Caw
TMwVOiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADy
nllQrw3KAPE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdS
V7kD5kDjrnkOxOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJg
elkvq4CYZp4U50F8L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMno
pyFq5YuSL1aAj92xxNoW6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+
BC8evT7+WoHYbxO/i1sBrE0YoC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasP
AqWJOl6eBLWB8qXNH7THlr3yKuRwh7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/oc
dXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/uaP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumk
k046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xk
boDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh04lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l
6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8dsaOFAit3TZrlxxgn5k7Z2kH2Hbm
quSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGCcSDzrYgu8PDuxXmXdsOTUtdK
XckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNez2McA/Gd+EmtBZ5IVybP
F6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0ZolYBba2ts9UfxDV
zZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RIMN6XsfIm6Iv0
CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gBGGKj+A70
BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7ymvW
5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghv
AQGf+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8
C94+cV5njiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARF
wqfxzTP0HgF+Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazv
g/u1Z7OeCGKpZrd9BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3e
wgwDz/svyt0cDfENdgzb5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQR
z5TmELDaUdg3E8hA/ZlRBxLPJmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4s
QRaQzeUd2QtEJfZxA0Q1WuAC+aX8SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2e
Ua8EpsW4LzeDvGYW4zqIQOWxkg9kD3lKrgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7M
ZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc
0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/WulpFOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M
/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1CXgyePq7zwHNzJFiKih3lQvqFtD8
NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1iGWAz0WwnbXFBGYBadXClW7g
TnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olzwlev6qeMgkznLc2LFIMe
QY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs7FPk88fg2pOyWZyE
U112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwqPBLMhuYQYxEo
G0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUIPDNeToo7
DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3ZmXAQ
ki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssM
ohh4X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN
1CxaZ207yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2
ahrRoGzSNGU/UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ks
n4FYqnxghoP1pvWa+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUO
MEfIT7QvQD40n0sVon6IGRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZ
b/mN/bvDO5100kknnXTSeZe8deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vf
gFudHt28nx9evHjp++w+KGuseTPkgJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJY
ynhISEo69WIN+Md7NvtOhGw9slTL1ACCy4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tB
OWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjvGweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDg
XFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wzZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3i
jTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh200cpp9TMQEcogMRm8ZfV2ehEQm6gi
ioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CHiCAEmDnN3XIxyAfKCh7zX+8f
3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPlTRDlRX4RCOYnZlGzMYhZ
vC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhDbZCP5RwZAvSUuc1z
IK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPLuyC/li1kTpDH
5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9l52iW4Lv
Pft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ecMlvd
LHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDE
PCWArpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vj
onUgw4KMoXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCq
gzvZ+6GxEMyNZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXI
LcwW7cCM56UMB1FQlmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6
i3CQX5FfmQJmC6y6E+R483OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ2
05AJIHObdrkLaKxkkKvAvGBUNB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUb
MyfIieYrbRVwkm58B1Qhu5kBjBbmA7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqr
lhP0+fpTWoNSWASK3CDK8In5AYjsMqv5CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywF
nmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5
+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWs
XbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGTo1AJeB6RODHqI/C9Zw21Hof7616+
ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0ZR2dJ1D+E8hern+v9FaQUcVqd
g0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx8CCwdwp/bO0PCR2fjH7w
Hlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeBvtBcDuIjkaycBCVa
zab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBGUT4Dacqi8iSI
b0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dgNqIUW8CS
aOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNaSOQX
m0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh
1DR2Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxV
EoGOIi8PwbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9C
oKeTTjrppJNOOm+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dG
ZQTfJq47mj/I0wHdX52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3P
TsPFK5e7HSkKvn1CS+VtCKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC
9eVhoDR1+RyU8uZyMQrMytw1pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu
3/f9RoG6VPlRuQVmoNR4CNYEW3bbaFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaR
BQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWLpaj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds
1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsx
sM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kYLJnULepokCbVOQdGjJzFLTC/ZiTrQD4w
w8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCoJexKJWAB+/kUKMJ88RLED2KEmggi
UviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLtApYUbbPPSZAVzL3KLTBe6qXY
A4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHmTtDvGkP07hDT49X0pJLw
+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwYbD9nHwUJW9yTExtC
RAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzpz6DInBKrssXA
o9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+v/qsUGiz
st2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJfGq6p
Z7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ
+iOoiuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEX
gLHETDYvAhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbY
Wqh+YDxx3fNcAPOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WC
mQvIzXIRDto1Zbj2PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7A
LiqDOo92Sh3AK+clnQfvNM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJ
IE7IfEpRcBxxDLQvAWWd1sh2CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTS
SSedd8VbV5xfdo4Od24Ga7Btsr0bhIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSCl
V0oe5264Uvr5ugO34U71pyOu1IKE2Fd1ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/Lf
tT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZ
rc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYHgAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2z
Dcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcpjdPmYrA1tRRXHoJyVOuk2UDV1Bra
ObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1ZXbjLrhWO4emvAJvZ2+Qpyt4
i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFyAiPlKtkfSKY4I0EsUpxc
ArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6A8gysrCoCdJijjOX
ghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0QmBZpPhaLoB1
j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tfDXJC5ltZ
ovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Zm0DG
I+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf
5X7Q73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7Hs
xbIwYMCAAQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fv
ZLLc/5383X76pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUG
Yh+4/GKnwpO2Ly8oF0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjS
ZqpjICXG9Deng/Os2TFhDuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru
9wYgk2wuQkBmkCVEZxArRCk1C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVM
XFfaQ8pUZ+2Uz8B9Wd40B4LMLqLFZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Y
m+QcszlorbV26gegVlSrq7VAGaOMUCaASBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV
6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoaKB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7m
o80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCUFVVFQaCW3IovqFYxSf0ItKHqYrUsyBSz
sugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5+Vz+DCKKcWIyEC+uKs1BPaw+spYC
z0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oIE+QB2cX4ESgiKtMElCxaDa0C
GPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX7EMhx4pM8ZmOQc5zER1C
/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC+6/yU8JPCT8lwNo7
a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZCm0NtDrU5BJ/7
fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/GH9nhP8VP
/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3Xdx3
MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9S
Knq7JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs
/KEmE+Mh0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7l
nOWOhaTaxiTmg7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKW
u6Dt13ppy8HSW/tEk2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9bi
RxC5hUc0AxbwMeuAkVwxk4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPV
jWCZr23SpoH8Ue6iIrBJLhYlQDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGgu
NtaCaCf6KQqIzqKLehXwECmqgmWJZa9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ
0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWfA/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46C
rCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JC
vYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQlcTjEX0rqkpQA3jNGY89OsLVUp5vX312g
Hog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7uLi4uLg4GDp06NChQ6HBtgbbGmxL
az/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yHDh06dOjQAW5WvVn1ZtW09d27
d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZsmXLlmnH07Bhw4YNG8KS
K0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW0Ug9zj/jXcsVkz0m
e0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P89+1SKzh/ZK83
1c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8DG70v9H/
Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zcM2nb
/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPa
eS4VXdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G
+b+bt06cvYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2w
lo6dCjxMGhijgbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHg
GeEpaXkFkQ0ibyrnwPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc
1wYogRBb90HR+2XhyaNnAU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYu
MRVkLuOq+RwMRa+jFwazES3NvSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5Edg
XjevGhVADBRdBKBGq04RBYpBdZqDfGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZ
Y8C61dLGEgLWbBZpDQVrS0sRa00QBcxXsizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU
3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqHgTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0
fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkO
WmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3kjuD9ytPkNMKeht3jpRPwLUt8de4
dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8hiF/uPk0CRPZ73cNZAaKPOJt5
Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu237f9vm3akPP8HvN7zO8B
P7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFjIsak3emPyzIuy7gs
adsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL07a70OtCrwu9
oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1etTLtwpJ7A
UxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHvCnz3
P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68t
YVvCtoRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz
7c+Vtv7UqVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2
IgwJHBI4JBAOTj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nu
JrubQK21tdbWWgtTf5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQ
R8BeS2dQ8plrjPIQv8JIdhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs
/hkgx/mAXpkTwV5B3tMbgOXXpHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVb
CFJOx1gUK0S2cE12noRVt9e3/rInEJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHc
S32HeQLUjBah9QIxVpRTZkByHufzxHbgXqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzM
VP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHFpiQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7ayl
J4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9GLTmPziCnmZOwg7FZH+ndCMpLsU3sALW3
OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQiRMWELPEbRqDsp4zLARVV2dyErR1
yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQnBC0NjQpYx0Ic2f6JUcVCMsa
USR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnGfn2mezzoQ71RugnmV8YJ
/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1cTQDo76saFSH5HuJ
++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh+s+2jZC0zpOJ
qSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd6naq2ylQ
PlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2WbusXYbY
ybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/
qRfW0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D
6Lmg54KeCyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RM
q8j9VX/4I0rPLz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6d
u3Tu0hkyfpXxq4xf/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0y
N8r8D/aNaR7TPAYu9LzQ80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJo
PPcbDwnT9edGMmg7bbuSBoAc5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2
ik8gAFyv3U2Td4ExUWmpbwGfoRGjbN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH
5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRYZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36Jf
B5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrKsoYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA
9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRNdFR7gznS3IIEsU/8IoqC+qk6TpkKopJo
I9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRXySdiQElR3lOmgTJZOSBegjpIW61t
AeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s20ApbKlhOgBatfaglgzZHLaM1
BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LLQ/zE6LKPvoaEQbFfRD6D
JOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjnPa+9u8BY4A1zjQbD
Ty/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSPy5GgvzDWeDeB
/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157svUD0G97
uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1lKVlK
lgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j
7Xd0jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqN
zx+RWnF5W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDB
QTDuxbgX416kTWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq
1t1ad2vdhe2Zt2fenhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusES
yxLLEgvki88Xny8ePvf93Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9q
p//UOP+dPd+2g9c+ie8bncAcrWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuS
D6iRxhmxCDIe9GsQOBEyfpjhczEDLLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU
6BkDPPFLIGxA1slOCRneC1zkUwiUbfZhfAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW
3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCyy5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD
1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLkeGKc8VVqA+EndrnwOcgFF+QKUFswTNUHM
lS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5zjxi7gXZXXY3u4I6Xp2lDAKlhdJG
1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9LF+D1lzZpuYFrYg6VYsBzUer
ptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/Gaz97HvtOUA2MCeb30FS
nleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBYO1teqSr4Tg+wB5+D
kFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7mnll8JmT+Ifvs
Qj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8Ck0G3+CA
HsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6itv2n9
Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc
7nM5bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVe
EH87B/2sPCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P
/Zs6tJ1aqUu9cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+
qF3qlI05xhxjjpGWSP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/o
mqbX6GbRzaKbQb6EfAn5Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2
fVM7/afG+W956/c422+GR74uC2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6
X7OM38DNKEuXZ8HwIuFuOzMj2E8rJQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk
1athEBn90OE8BhmaOeoETIXkCgGVvQqQmNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL
6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7vOTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro
0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYrOcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKw
uCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj84rX4ECjPeAaA8bNsbGQA85ZcIzeC
fEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1WfrK0D5QhujnQTlmvKTcAPjySqO
g/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0xWisPrnHJ2ZNagvkemzzb
QJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXUE9R62g5bLdClHGgm
gtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsHgWuwMznxIljz
q3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1MujnXf30M+B6
qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepydbm6
HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/B
pD5MGHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3g
WOFY4VgBX2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/a
a0zFMRXHVPzn9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKV
q/+H/hqda3Su0bl3r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7
/FG7wkcLHy18FOyV7JXslf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83N
NBduTb81/db0tETb08PTw9MDyhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hO
mHJ3yt0pdyG2e2z32O7/ej9I5U399F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778
m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56+
+CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Coyavubi8ENKO62Ruim2vjEgaBry1koN4clGtG
eTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4CLhu3em8BXElkh0uN3i3aPvjpkKuKyEl
KvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzKOibXa0iKTd4QvwmeTH5W79EeMPKJ
vNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqAedzcb+4AJYc6QKkIyhpxSZ0P
8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2IoCLdyGx0sBTTsDUA8EIvp
AcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL7Eftl3weglWzZfRp
BepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrijXNWSZwA7GWd8
Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwIcyXIEyJU
U0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+EdA+p
GPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWi
elGFb9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYib
p0Du8jxKHA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ
8/nlMMdC7ks+quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61B
A8RhSMojlj5vBi/8427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGU
MWqDskmrKN4HsVM9LU+C2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZ
C+p1MVu1AFk5RFOQeeUDYoCuZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPA
I3lTvAbpL0+YS4DmopQoD8Z7MruZFRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSB
MkT0sihgWo1OnhVgmsYl8xjYfrVb7fNBy2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkE
wm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/vWmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1
m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5TT/rLATmSnfhlMNgrSt9jevguW8EEwfu
r7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczKme+a7cFe3FHA7gX9oMeQW0CUUbbK
OeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmNCa5NYIzSf5UvICi733d+pUDr
hY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxxyS+ddP4f5K0T5+wvwpcq
fSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEpZY1FsjdoCeom+0Sw
vUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeBfd76juYg5tP/
dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD4DnBHPaA
3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7nAPb
YNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkt
o30agfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCr
gtaaK3I/qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39Lmy
PphLzETdArK/+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g
6my0PXoYxDpe9XvRETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvr
yOD3K8SfSpwSmxPs7/t4rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/h
wGUQPyuxY5Iv+F1QgyyT3jic0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdf
zdu/x3l/YgZXFsjRMWRtJsAvv62QzyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmU
ehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t9
4B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5lr/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpH
nb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0f
ABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuTrREE/RxeJqcDAvSwatn7QmDTDD9E
LAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34Kjs/924acAv98wYMzHgKf4YHf
h+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd9l0B6miry+EPNLDN9fkF
zHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLaDyAqqweUPaBFWSLU
7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSywy3zPpYIn0p0/
/kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZApnyh+YNr
gNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdUKuQZ
hJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTm
Zr+xG4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc
2gMc+wNq8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHU
os2WbaFAgaxZKnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7
Y10a8CkYlc313pfgXZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVo
CKIMHxotQTRWc1IJLEnqMl8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0g
bHKdeQoMyRf4At+IIuYo0N77r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKm
A42UL6wPQMmrxml9wZigR+AFsxUf0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N
73PXREiZEf86NiPYrtun2dqDvbO9t+MI+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ
2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiP
tHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9HYPAG+xclLwFXKdTmiTaIHiCfxP/raDm
U4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukUAgpr27VeAHT4u4M8nXTSSSeddNJ5
N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fyJ0ja4rE448F0uV7a20H4WMfD
HD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZunnGgaOhfbX7BiT/fHmc
awd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9Arl0ZBhbYAA/tN5/e
ygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZVcmjXwVbCMdP/
DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG2jFrfUdP
MNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkDnJXA
W8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1ja
akPAPdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2
zHbbVgosIZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt
2ggiUri9JcHdxlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaI
I0aivha0VcJKELg/cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18
miY1AJvTXtDxOTjj9B7mPgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+
QYmAuENJIdom0Bs6Zxo3IfmeUtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE
7MlBOzz3IcvH5SoEbwTlgqPx6/ehSA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwG
fbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwFtJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2v
Qdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYiJ+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/S
G/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uorn/EgylrzKQfBLOuNdn8JcoyR21sDjFtc
NZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw8Kw1LslvwLPdvcubB6zzNcU2GpQL
SnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3Qe/q6ZHyK6hu5bX2K5iFyC0u
gN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0fPXKuRN8WnuHG8GgzbBU
tQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt27QnIPYaXykVwPOV
9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkBycoMQ1A2t+tZzM
A7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+83jrxNk4
rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZvC2eS
2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9be
lrLW+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGY
j7QxtrkgxxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kO
Zi1PG/dVwKG2UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaK
W1aCPty4Z9jAU8ez1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRR
E5QzYGYy7+hXwLmAFdICZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POM
vGA2MXd4J4MZbT4UA8GMZIUYBpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkp
d8lZ4Gnsfu2dBWYrJcrwgHWE9bTtAehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2
NbBJyFjwCQpyhx8G7pufyxUgh+pT9SpgFvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65
/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aSTTjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J
91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7NgkiMgdvlhGQqXCGW8piSH7pMynlNrCX5bID
KJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5wt2eauyQUexw+uNYT6FOs5bS11yHX
uOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF9o1PWbBp6jTVBsoA5Tj3Qd4T
LY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0FdhpcGh+qb41gXrOR+PZQTY
7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIXSBga/8Gro5BUJmFH
bFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUOzKmsk3fBXtZ+
zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlwPXdmSAiH
lPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6Dczn
5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8
YVnA1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYk
gKW1vbHtKGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoB
NQPSvgCW+mGTp0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2
qz/y5//t/Lvj9d/FlsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Wh
b0nZEpKijXKvTYj5LPb7V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzz
dSoLIGcP/17hU0FL1AqpX4HlolxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3eh
Wpa84P7B9TppJogcMlovBfFXnoe86A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zP
QQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/
bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyBKXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5f
NXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yWB7/OGAG+eXz9/I6B7Ka7jY0g84veamfQ
tmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVnp58WuPMUnJNcj2L3g/s9V1nnfNB3
efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5TeSpjSEERlYRHdwWxDOfEL0EyJ
U6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cKaKiVtBogigpFpIAyR2uo
HQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7PcpnrE/mI2VGWobUD6y
zrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rthBbgPuo6l1gT
3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhybkXYh7Hqq
66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0FrBq0Z
tAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafk
PZi1I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/
dVVocLHg9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+z
YmCba7VbY6BQ/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2
z69g+HrsKZ3A+MVVN/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwB
xjf6e/IUKM2VetbS4L5mjHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW7
7ZVDBz1ZV/RPwBxknDMWgTDN++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FE
zayOQiPAf6Dvr+FfgPmDPsxZH4z3jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5
x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2rQE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBP
s2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXl
YXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9
t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv2076tgJzjTbMkRsshe0bfKq9u0CN
i4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3QsmXLli1bQrPszbI3yw4NGzZs
2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rpabyr8a7Gu2BO8TnF5xR/
8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X7fDP6ue3y79r9127
79pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3Sfn9a7tNyn5aD
8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/zqzeNlz/y
5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpKSkpK
ggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v
/0nI9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJ
AAGihHeKWhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0U
OBIta7RwsOfR/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeD
tOnVvNPB2Kt/7bkGWjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNK
guOc766g8WAbbf/eLwoskbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+6
1fIleGaaK9VmYGnqkxBYAqy/+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u
8SW/hLCkLPNyR0LIjvCh2QMgZGv4sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6f
oVLWK+Do4bcsXAP/+yF5s62G0DZZRxReCqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DU
VsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTW
BKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5Gxi9PB7neFAKyIJmHRDzucVs4KYw5Ufg
Kebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+4jz45LBYZNS7C9TJ+yfvn7wfwh6H
PQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOflPqk1Cel0oYsl15ZemXpFZh7
du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF5WHFyhUrV6x8d3pJpezF
shfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7SO0haYnOuiHrhqwb
Am2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3funJYIfvTRRx99
9BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym/UyNnxo/
NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue7Xi2
4xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k
1QhImSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv
5XFQchCuxoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78C
aHVjfkjpDbKee63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzO
tRa0Btply2VQY+QlmRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauP
tLVg7W/v6jcXxCD1pqUIqIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5
YQwH8R6POQjGfX23uARKqLW9zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1
+KutAK9ntvMyeGd4XiR/BpwxJshPQfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcr
gAzgidIe9PpmG4qA0Vz3cXcFW0HrM6UocM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/
YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYyHNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6
vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCoZgG5DZgkXeIqiMqq1/4tiEuWamY38PWq
jfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmtrFZWp63v3LZz285t4cOPP/z4w4/h
p3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDoRje6/etOMKkXWEuoJdQSCt56
3nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8QcE6Hqzqo7q+6E1RlXZ1yd
ERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Zb5k0/SyusLjC4gpv
b8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEHbGMb2/jrNMrc
KHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou67iswB3u
cAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa82vP
rz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvh
Yq3bZ17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVK
a3FJ+wzkFHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+O
TpAtMdvsrGPhnPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAX
cqkBiB0UUh6Dplm+s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXp
y10aaAlqe2Ul6C/MSPM8WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOc
va19CMhoqYrOgFUGmH3A1ds703kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtz
zDCIa5b4fnJW4LnxUi4H7aIWYz0ISoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU
/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVN
L8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAnuGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq
1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9
qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKyFGh7tb3a3t+vF+fFeXEezCfmE/MJ
DDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+svy63ZYlliWXJm283s+jMojOL
gredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9+fXl15dDl2JdinUpBp/7
fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5Th+wf9HzQ80FPqFih
YoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jReaE972r99P6lT
A9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoVK4jJYrKY
/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2NVxDw
je/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQ
hxA98FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui
+Ly05rWVhcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXs
q/0OgdgssmpfgTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz
1NRzgG2pVkWrB+rXVqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7
bPvWrzlY6lg0bQtoxdXb1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7Uk
qAky0psL5ADrCdUETw33JiMXOH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2
BfWu+qPlfZDzlfFyKzicjoP2xiDmynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4Jyoo
BsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcb
oSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8UZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby
/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVLlyyFKturbK+yHY7PPD7z+EzYennr5a2X
IcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyBmJiYmJgYuNvzbs+7PYFlLGPZH8uX
+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E3Ii5EQOzi88uPrs4JHdO7pzc
GQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+rT6rHat2rNqxtO6md5re
aXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaHbQ6DUudKnSv1BpXE
VN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7vWq9ZxmYZm2Us
TGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P538VbJ84+
twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniGewKh
8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIz
W4OsK8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG
9N3eSE89MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxX
As8+d0XnPVAfKTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1
QajWML8R4PPcZ4AlAFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYj
sERbTM0Aa1fyi2aQNDRxXPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQ
njtofuBN8PfYuir5wbJFW6kUAREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5
BpT+ahl1KhhFZVvzInh/9YxzDwTKskXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjF
YKzXW+sPwZbfOkULBLWlGGoZDXo1Y455AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeber
Ghh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMqk0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2
lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFCRwsdhenzp8+fPh8GMIABQMdCHQt1LATd
5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT8E3DNw0HhjOc4b9fn/o6qVvTb02/
NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN7fi2+mybv23+tvkhpkNMh5gO
sD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+1H9S/0n9JxCSMyRnSE6Y
cnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq1KlTp04dUMup5dRy
/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP+DN/fVP+3f6d
zv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4sLbSrzcqe
oNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+zj3SD
4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5
XtkO7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQf
btQ49MYuJ3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6
geBQtwV+ACZpVn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0Wrp
wBYwnJWXy8XA8LMpxJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALe
Fo6DZtITtH0gf21cYdFA/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TN
Ur4tBOSXjJuMpUGP1qoHJoAwWxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALK
WbWJlAmWry17jCYIG2aNNPQCYVEg3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9
ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsDdcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4
WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ecOw60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A
9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5DIx4+73j7134u4d5UNB/poJa1X+1RvU/
VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/lf9rrGhT0n+DIkSNHjhx5DDPOpAph
4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0GL8+Obln3AHSsWuP797tA7vmc
VFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj4TUQRupZ+kLQGgjT5MXA
VD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19lf/R10D/mKXE3xN4o
VqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNqyxMWBaQk6aK0
BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUHJgNoZ/Re
WhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzEAeJo
8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfA
XT5VL4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1an
g/SupirDQTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3w
jeElkD7wDfA1g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKs
gyyd5H2ghQnLzZNB/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysO
rDiwIqyqt6reqnpQI6ZGTI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZN
BNMFLTXzLHRxRn9d5wS039bu2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuD
GqIvzO4Ckl08EuYGNnFZuAz6Df2uOA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/
pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7osCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsR
As/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+
kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxXrG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLe
EK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10bA0J37XbgI4h6NiTGlgjey55vPN9C
vphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsMfO18G90DQWppaGR8FhyV7d0t
Z0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuAcEv40fQiMJHzgh+sP1m3
GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7hOc+ZD3r7JhTHUyT
DDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhcQlggAgKTNIvw
DuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPieHAXma+ah
oQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZodLL
lV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuC
OFWfLi8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ
3WU1CPvKUC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5
O8DV2vm9OwnCcqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPl
ZfktW3kwP2FND8QARdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinf
gDhNdwr7wVBNjrP4QI+XOmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNX
k6uC2NfwrHEDyHZDFVMMmOymGcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8
m2vKZTD0ML8p3QY668dMGvgmKoP844EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE
26qDwWCYLntM+8CwyYh1EHgG+HsErBBoo1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegf
a98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVi
bTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3D
eoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/FvBfzHixlKUv/0QV1qcu/URL5r/qf
9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577VciJ9VOrNWFLgPCOPFuyCW9Sxz
nYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2Bj2ZD6UBIHzGEf87wAgx
Tk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6PAO2g8r7rU5AOWxaZ
i0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8SNxyML5qnhrwG
OV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO9Bh1sBIC
3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqehsh3E
tfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3f
S/cgLM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0w
dxbtnAOvxZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0J
YWmOKNP7EO61lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWF
peJZyDqUEcjZC2E7QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFB
j8efTpzvN3EOMLaH8Mz4fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7e
mlnAJLWBfyqIy8SexpGg6srBrJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8
eNnRbDjx6umembugd0afeS89CyGzm2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/Mtg
ulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+s
U023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8QKs4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFD
QS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlriaPBleW+4h4A+0Rcv2MC/hQqm78H6uvVo
aFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3BfAENV+TPPJtBDAzGeWJBek3poT4Ld
YR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73VwvZa/L30PRO6KjLV+D+Zmhkzx
fciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUHqC39zfJvgulJ613DaMit
kfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8Jxqetqy0HwVfVH+lN
ANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA4LetE3dAYKna
V28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i+buHd1BQ
UFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+Fb4U
NwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO
96WdIF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuH
rXhlsNQJGRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B
3aF86YsEb+WcvRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJ
A+ublnXmIuDPd77pnAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DY
JRXVuwK7qeM3gatc/iKlC6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP1
7sl6/gsgYRgmx4H/vNZWKwf+K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyo
NADdhlGPAfmEcYI8B/Qs0jCB+oM6S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/
gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9
rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEBiEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoK
CgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVBU6yRYkfwt83skt0QxK/Nm0xRICq8rySB
Ok8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzPxYfomyC/c94mXxEI1cIuh80GTzP/
D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILYKqa0+TMwfBweEvMscNM2MawC
+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeTCs4r6UVudwZPMU+7+M1g
NlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/PVC/VndKFhCXaFOk
NuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0FMV6YbNwJHBNK
e78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQRweG+p6F
wFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4jUCQq
5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQ
iwxmzZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+q
AkIttbGyCDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCg
oKCgx0n8sw1It/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3
QKmQH5v/IqTXPn3w2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZ
JeNOiMuIbRPyOvgauMq63gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVb
ZdD3SPsNkSDk+j92doDS5uIZxfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GN
laqaJoHniDDU9i5cnJ/0UfZYyBvmi9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus
9OS24H7LfTd3Kahn/a+5zoD5PVNAagzWosa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3
Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsGlnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTs
dgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqmgnLGv8h1CHy9PG/53gXfi/7VzgiwbpOy
NQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+IpeCbQ0mkp2EMeq4WoEGMoLHcT5EPVq
qCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhKGV6V5oPQRUokDPy5gZvql+C/
6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX/S3BleVp7twBvhxa6X6Q
Qo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcTX4h0g+mc1l8s+ncP
76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1CfA1+nLn/wvqn
oUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht9fqWi2DY
b3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSIO5Ng
AOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O
+nwtRKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dA
QQSxtt5eHQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUK
tNX7Q86p7LysgeAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhT
cLt/xorMNyC7t2u+9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3c
c712MC6XIqUfIO6bsBrmiSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJ
ZRIpDr523mm+KSAtFyaLyZDTMy/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+
CJSril/7HJRx+hYFENfrMw0/QbHosDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSK
X/peaQHVeXonB//uYR4UFBQUFBT0OPzpGecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5
V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3ICpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1
n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8XvHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZq
r4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupTyJ+hJ+uh4J6cNStjARQLjdgpVgbD
FsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN+BHyxuodZAfkeIRo8wzwfK6M
F/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6PtoVAsKeZa+HtgDGiLfRpI
AfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+sfgW2btapjtLgnuBq
4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqWTmuLoFj96JVR
aXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBlcdaS8sG/
MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7i6t1
bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUy
l8p+AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57z
ffZz4NLuWVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKg
peT/5HkWxPIR7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8f
DsIm9wB5EpAC0k4wrk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6H
ql9VeAnsXfXFMSvgl1XeTUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRx
xqvRVSHvSb2++h0o7/gauVqD4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFP
OwQljsTPihwCruM+QVkKnin5y3NaQpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXP
dPdV53JwpnhSc7eB97hnuccL5u2mU6ZQYLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9Y
jXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGl
KZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJHKa1AT1I3+G+DVo3njN0gp4k6NJAMmujt
qqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZkgRwupqgXwZFm+UQ8A3quPlhPBONG
eY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD1KUyB8qvB0+2ppv6QXR6fKmY
lhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKlSwuP9+nTp0+fPhAWFhYW
Fvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQflI1+Zn+kFik2pan
nwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6YXQd4EPFNQjXQ
r4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814Ex5l7qy/P
AO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBqTr3B
3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/nt
nbnu+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nah
H4N3rK+JZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhN
m01lgTlK3YzycL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU
8Lv8FfQXIWNM7j3np+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/I
SVMsmMrJS9Qs8Lf11xN3gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0iv
mPYaF0NeD+cB7yhwnDJvMayGhPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfI
fcIEp2vcbn5L//sGduPGjRs3blyYQBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzL
L3D16u3b2dl/Xbxy5UqUCA+Ht97q379+fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xP
RITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3LzMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2i
KP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B
+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDvsEWGjwNNU+3C26D3Er6jDQjzuCjE
gFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5/MoV6DFWyroTDilbKuj3P4KE
6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh3YRjvAVdarWMu9wRbg9e
1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L7QgI7cQD7ALhF8Mc
0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEdeU8gemnEv5Qdg
vvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUBJV3MMMeD
O8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQmZtR
/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0E
Wm9K0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8
GkpWKuYsq0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRr
f90Hw6Ps3bt37969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2
QWZmXl4gAGXLli4dFQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRN
EODpp4sVi4j4tT+P83n/2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs8
3t6A/n8mq+7f93h8vsK4bdvGxEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQ
iml3hVRQV8nbmQDCE2JrfSxIcYQYNoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgY
THpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A76qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7
Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmn
IHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w24dObIH80dn709tByJ3IiJgtYGxoMfvr
QsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0V1yoXQBDSeNdxxG4fytvkh4Lvi6u
b30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzIc7l/0i3gK6029JlBLikvFdLB
W0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9yS3vAfCleBZkpYJ6mhm6
FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDqpU3wdwVHTfsFy0nw
NgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGOwbve7wJhgfyy
tTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+QVoVfg9zN
/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1O9jQ
fkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4u
LAwOHbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c
/nTinPzGdePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdB
v6xf8DUBsZQYJX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdA
C8EhW4GvhK8CZUGt4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSul
z4O98InjrZufLIPbpjRD4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5
NnQrpN+Pyi12BLyH0rsmxYL3nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q
2s34klgazHuksEAUXG+b9FLOafB10vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qw
twd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZuAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJ
eALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4
jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoPIKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXP
dTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCNUXcI3UDtpx8Tb4G8XtIDdcDU39xQ
9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHWWGxF8RGgFxU+sgTAfljsYTwD
Jd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAFPPPXfTj8IwW1y0uWLFmy
ZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L9dtSO7s9LCwurjBO
QdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1HTIyFOUfnd+1
a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE6JDXHuRv
BUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpIDoEUK
L4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DM
Gahe/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dp
amlw93a38r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD
3mzPGFdpkB4YLcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH
+jVEVQqpEdISzCfFCOUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+
bcpsfxjkf5P7TH4iJB9JWZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/
cn9peHAs81amFQyfS5H+3WB/wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggL
QSrNp7oMxhjjbnk82CvYo02twFbevNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubs
EpnXQNmlfOf5EaK/jnreuhzi9xWvn3ATxG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDr
sWNRcPTna19d6grp+/P2pXUGZ72srintwD/KMyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vu
u7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrHKscqxx9/3wq2V0ddHXV11N/d+0JTMqdk
TsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Zem3tt/u5n95/77yfo/6aqiqKqoKqq
qmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z+f3g9wcCilK4PXjwo4/eeqtw
+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j24K4j9ufnnGW65axxswA
c0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE8bDQ07ACpN32mJhl
oL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/SzoGawVe4H4o6hZ
DoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4//EPXU8N
hLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbzlfxv
lL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U
+prFcg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBu
XzVC6pm0gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175
/OF50XA+5dZ7rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXz
YhBWCvNNJ0DZL16WloG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9
vU1rwNDJ3N34BBSZFr4+bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98
pQbsTzze7szzkN6ITYEfQVtgnB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmC
mrtGjRo1atSosNb5cYlsGdkysiW8/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12
+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu
3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3Lti7bukB/+tP/736SQf/xFKUgkS1I2f4906aN
GNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUV
BQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3ZNlicTh+v/+o6/+ogriP259OnLOs
9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4RIoB7XOttdYPpNZFR5ZbAuIh
62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt/SPBAPo1Suo24IFu1L8H
vRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJHzTth7dklWVvjoHTH
SmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D5EVy8pVP4EGC
fVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfaaTC0loeJ
30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+2T0S
/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F
7kU2i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpc
uvMx2OOZpnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V
4Pb41FYPhkG5F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2
vg+OvnEq43R1SLmsV9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHi
xIkTJxaeHz9+/Pjx46FEiRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUN
GzZs2LABMjIyMjIyICoqKioqCjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn
5u6su7Puzjo4fvz48ePHC8MXPC4uLi4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQo
VZWqSlWYkTsjd0YubC66uejmolCmTJkyZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0Wdpk
aZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4
i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFrxq4Zf/z9ubHmxpoba2B66emlp5eG8+fP
nz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe8LThacPTHl3b/7DNaZvTNqdB+U/K
f1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiSviV9Szo4nU6n0wk1F9RcUHMB
TJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5oeeHnoc2MW1i2sQ8vnH1
qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z+32+gpng385IV6ky
ePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv1i3Iy7Nao6LA
aHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvtzYgPx33c
/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsCaMNy
W6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4
flL7luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5Ehb
lTw7RI61fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUz
JhVi46JioidBpDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5
H4S+YCirTAebTfrcuxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjt
eBUNwk6b+pcKAWsTw21Lf+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc
3Ku9SfnNoHRqzPHi88H2vpwWvh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fg
bZV/PmAHxyaLKo4BY2v9Y6UEZFRJeeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHu
obzz7uJQ8UTF80USoGTXMkLJb8F0yNQnVAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/
8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyfO++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJ
EyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6ggTmUV/1bym6peiWorD80vJLyy8VfsVe
bm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPUD6Hr1K5Tu06FnF05u3J2wcw9M/fM
3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oePjpO7O3d37m7IL5dfLr/cv9+P
5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlhzwx7Zti/3s7U7VO3T90O
JwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8pflP8Jni35bst3235
z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/vjJ8ZfjKAN84
vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7TuHpc7+v/
Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1K9z2
6VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QI
qUAaJr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqI
AN1NSQRAQgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID
6U2mQ8rqrBrpD0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4
cfXutrvWws6O+7PObgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ
9lsOOHqCb2vWK2nnwD/cednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn
5mG3COlfZg9xfQkPWmdsy/kGzCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1
LFjPmd4wxoM/RnmdhuAdpt7KTYVcMbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdzt
AiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJIH5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODI
jtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLnGTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGT
bWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuFzYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6
hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0CtZxhpOAN003xCd2Ct0FyoA9Jz4alF
40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbDtc4F7RS0WxDnX22/IIFZu3bt
2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03dt3Y38zgPnz9n1WkQ5EO
RToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJvht8Mv/nX9+Phkpqh
5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9G+VJBc+7wMxZ
M2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n8bZO2Tpl
629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW5Bos
PrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpU
q/b79gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6
tlYehHhu6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0e
Jm8GVoi9dS8In+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKm
hSC1NW3Q1oHwjCzKrUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgoc
RqFRycYQ5S3hVn6ECE/EiLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCk
R5ioNof1T2iVyYMTNkPd0oNB25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e
2jZwp+SNTs+BQKQvJL8j2GuY20ivQWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX
0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNB
nyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtO
CdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVfBHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3ua
BsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH+VNQ5G7Rj0sdgbDXw0fGLwV/28BU
qTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR7jmyR6QOAm2GMTJ0GDBffVl4
E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxasXHjxo0bNxbOCP/R9ZgL
apsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQTgonhd98Na4N0AZo
A37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAEJzgBdKMb3f74
6/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E/6PvzweJ
HyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16QmNWHz
zM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBb
t1q1ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/Y
GWfzcVcDuTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNA
HCItQgHKaudZCPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGm
HiRt9E0yFoUrSzLH6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWE
T8WODAblTTXTuwwC9QNLvSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2Wd
cZDvIyhpid4dEQPlo8rVDzkF1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3Ms
eRJwRavJNAg9Ffpz5BiIHZfoK5ELifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30N
qfvTOuZch3M7L5dL+xByt3pD/CvA1tfeOiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUU
y486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSAMgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4
eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEHQBVxWatD1IionxzfwJPnypVNOA+h4baP
QgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/iCyjbo3hGORkqHKpYv1YLsCeFfJf4
M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvnT7x46hSkHsrqd/MoqBHmapZU
0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtNlb2Pb6AWJLDFixcv/tsP
koL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDCgQowadKkSb+txWvR
vEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyXZr80+yVYKCwU
FgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYRthG2whrn
GsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPtwvYf
/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86
vnfvtWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3
+fm/rtf86FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG
6ufg/NwbuZn9ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08
tSkLzledeTk3YO2sdec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf
4CVqC59D4Cn/Lf08iH6pHTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5
Kr5v3wglXzctPDsHskqHp+aMBvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7N
E6/a34Z7FczNS9wD7Xbe7rQx4Oua2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAso
Xf0tIG1nTrQwAFzFPBfVXHDN0p837AYxRi6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD
5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwnos4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2
EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKlY2IrBCB0onQg/mWwbQibhQ+Uyq4zTglS
RiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+okHIfLCPdxjCVoH5A/tsSyXw5ftK
CXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQvu72gOsmyGueq90pAx6MhvBP
QR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTxLeAZ2ujV/88g6fT4BmxB
7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gNozaMglEZozJGZUD0
neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej70bfhTTSSHsM
/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1AfaA+UIcH
ox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWIeqTw
ZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/
HX/hzY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2
h1Ue3n/U4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv
/uST/2iCpyDu4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFf
jPsFjw9sxvB5EYtBvaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75K
fQWE3oYnDeXhZon7SRdWQPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5
GSo8iN9gSAJrd2tRDoJaQW0tPgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36s
BUBviiAkgHhQF5V3wF/TWTGvMxiTDe3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp
6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXR
lqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMvg7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4
BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz
78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfEKEsVuB2ecfv+cTDUk3da+kDUujA1
thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8sr7Tehpjc+E02BSJaRRaPygTD
EPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW0n4y7AJnVEpOSjfwrcwe
dC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDoE+gZaAeBQ8pq31lQ
ZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F4cOHDx8+/K9P
nIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OVKs8+O2MG
VK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0Dk6lY
sfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GO
HDly5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH
546Dtj1gXGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c
97jmkLnAXcc9BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5j
GHBSb6VfBHGysEj0g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bI
KND8asdAKOidDTPU1aAsslRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbU
mOM9Bm+crfnuhW/hl+X7Lp36ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTC
d4TdjmgIYWdDy9ltYGkdeceSD3p9fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+
0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9
G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIWMC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/
RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN620z4BAobAKmk4uCbm/uh7EvI3+C4HngXJ
bM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSsu1/10kYIxOvN8uaD9rH+tvAe5Jdw
V9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/RmBEIBL0idp2dTrop9X+gfqg
BgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7wV8U/M9UsOzcnpV7Vu5Z
CQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6j9Y5/lf5/f+4Ztjn
c7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3az+xst1tRIDTU
YpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTCuI/bn06c
lamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcMy83d
DG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArC
FLGD2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx0
3IyrCYbz9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG
78Kz5Sr0e7oflJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5
W80TIfRLR35UNIQkhawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QX
y4CS6NX0LSB/Uiq/WBfI65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9Fmw
Y3gmYSqkzTS2TX4ZQvbYD9kmQ9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1l
s/01CPi1ndJT4C8aMBEDOTnpC7zPQeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfk
Nr59Mn0TuDpmpST1BeW8sij9I7B1t3+pfQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2g
VNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8atBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLp
h5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9AstYxjKAoQxl6J9tNSgo6HF44onSpSMi
4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHiERFw9uydO5mZIIqhoSEhEBY2ZMgX
X/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/+tPcfj8kJPxaQBEWZrFIEmRl
iaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9HVSE5OTfX7y+M+7j96VKN
B40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/TeHkdCIG+O/pVcDYpc
bVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9IEGNXFcpF852
veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4Wd+mrwJ9
mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqEW0zO
Su9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQ
L3tm590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkz
gL+M+pHiBf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21
IIDJbXrPuA+0zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBM
YHsgA9QG0mLhTZBijMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmX
u0FufprHPxPUE2wJ/AJynNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+
HhBoIpwGPUH4WVwFvC9uk74AXdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+Q
lZWT43RC375vv/3113Dx4rVraY/jJotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnP
PTd27KJFcPr0tWv/aJ3ox6V69bJl4+Phxx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t1
5vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9b
bn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgThJCRMNr5cdBBkD3FXzbPDqYyT2qFZYCln
NIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQejhO/vdwN3hLQhcAu2n9hz8btL4Ovq
p8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl8oE/AeSFNDCfA3edPF/WQLi6
9lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2ARXzN4AF9pYjWGJgibBVD
QIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8ufk6iJsymt8E5Ana
PPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuyZmRdhhxnVn25
E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ/QQAmaZa
MgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgoqVwC
9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+Uv
VoR7i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0
q/p9zQDaSf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp99
9o9v4vt/zZ9OnC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AU
TB/HRIZUB8MKZsibIfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZ
Mze+TBNBPBvyWuJC0BdnrksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294H
AmsCy31TQN5hirA8A+pRbaM3GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itF
xK0G+xVXpKUD3EjdundNHNjnlUmr3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8
YJXQm2zQF+kX0UFIYgzHQaylRwulwdBYT1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtA
jrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRpzoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73n
JIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi6LvFfvQD/RVhseACoTFLhATQv+BHcS3o
U4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTacMBwG+XRIo7A7YJlhmWH7CcwO4zrz
YYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT+mx2Q+N3Grq7TwBnEWegyTsQ
0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPHhWHwnXvFnU13wf9ufs4F
DyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1HjtHGiDlZP6pwCUp8nf
PcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+Fffibt4CuXvU
K+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrWM2YK6B3l
m4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymAb6zr
mfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/O
A54QhodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDg
PereCUJe7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7M
eM3VGzI/dZcMTIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6zn
AzJBjBGHiU+BGGV43/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGq
NZAO2oyMxik1oGnxZzuXbgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDb
YogaI1e05IM+jmrmJZBYrOj+5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0Q
Pzcso9grkHTYvUN/EXZe2PbJfhckz8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgR
hiflX5fPCc45BwUFBQUF/Q/xp2ucg4KCgoKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0Ew
cQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAfEEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU
9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDAj4oAAAAASUVORK5CYII=
--------------050204080406070300090103
Content-Type: image/png;
 name="XeC"
Content-Transfer-Encoding: base64
Content-ID: <part28.08090700.06040604@aol.com>
Content-Disposition: inline;
 filename="XeC"

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAA
CXBIWXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAI
JLiEoIGgETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlT
p09Lly5dunTpkhC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLl
y5dB/rMr4ubm5ubm5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc
3Nzc3Nzcfgd34uzm5ubm5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zF
HGHAI0sR61oQpSxdUsuBrcbbpFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL
5KL61yAdzP0l4ytwdrCmZQ0B49ngq9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5
xhJQD0ijlA6g5aoPzQXA2i9znjMWcodll8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteB
faB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHnu0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm
5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGzl2e093YQJp4ZK4D+G+NGeT+oM131tF+h
+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRGmAkCkYsLFwDS//NGKvzbkoT3kJCB
AD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o0AicE+TFUiRou8QMPMH3hee3
xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8I6cn2B8meCh34eGjN6Ve
rAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1YO1qH6dbCKnhSYG5
oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ69MW+HWD9Tu2S
0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skjff0g+X5S
BR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBNv1lc
AOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAY
lnko7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm
+Bj0TqE4h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9
bF5rQRrpqG3vCt5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk
00D+UBkr7oI2QPpSCgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2
qwt9Le26NjkA9faXTy79AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3
YG7o/SZiFChhSkm7DkLe+n1ttYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HB
doFdC68EZ7ajSBEJss5l5/IM7hd6qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2
SiNe1wGvbXI153fwpnrSgWc/ws2y92v8PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJ
mfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNpdxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE
+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK63RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQ
d+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1Ej0GgzhSfuayglYmv/7gaaIn2W84t
IN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqvb/8C1AilmagDhgX6FnoPMGzx
MnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUCwLFVHq31B/NoD7P5ETA2
O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgnrBvSZgIG+Yo+GqxD
cuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPoK3/MPEATqdIi
QEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJDQtfUg0ml
oXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRvLQkp
3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAX
Q8B7LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZP
AFvtzIyo2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yM
oDu4grVrTgMoy8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJf
OZ5ZoMXlTEpXQLuY2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZE
GcZ43wHdA+movjR47/b6RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaB
VxGvyrpeYM+yLs/6HuRrzh2uFPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9
lOZgn5ijt9wGfbJezT4I3PY4G1QWjF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B
91zfDX6/wIOlT+LjW0KJbwptCyoOupk6L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGB
LwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZEkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNC
IWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+G9grKgnuz35x32cROPa4Clpfgff1xGr3
KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0dTXrCT4p9s2GMVA6uqRnoZXwqFh8
6hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISLIDZZ14XPhJK1S0WVXQ5BgUEj
fM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJFWNoq4IDeLh2CzJIZJ42d
QL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B+WN6SPNAVPLqbt4O
0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7gXzJ41LAV6D6
Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0Hoqz6hbwI
DFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNTtARz
uuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0f
XAHUFPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm
5/fdHgE7D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3
cmrwrzUguJ7/a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBu
T9rl+6kw8FSbj3qHwKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y
2BpnVfZ8DSU9ixyt8itU/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXO
MlD/ZOGg5lMhIsn/81oWMP5qKilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/u
v90fnjZ82vBpQ1CXq8vV5VD4q8JfFf4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSp
UqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoU
eP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMo
OVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynMcNSzKvCxstVUFLTLjplZPwNztWDxMcj5
fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOmZRGIgXYvewOQ+htjlQSQVPtRVwgo
v9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g9TblevUCkSLaaS/BVV8NdWWC
eaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZLsc8HtRHzkr2EZC9LXt4
ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8W/UqMvUHKHSq0J7g
MJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwClsu4jMQucu5z5
HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZz1ch9JPQ
/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPgAfh1
N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+Gg
inF9wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe
3jjveb1L79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jU
kKkhU0EZrgxXhv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k
6oXAC0jnBbeAGCxiJVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjC
IFfUVQKpirVnVg64ZJrnGkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQld
QaC7us5lAaWqTHxtsB9xzkr5AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6R
tuuag7JUPisvAGNdQwVjfxClDb2kAWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBc
QxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/q
JoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lKQdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJi
mvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazhoZ0SschLk86w2FobUjm/TMy3gW0ye5TCA
+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4rE8LKwDpxbLnmifA6VZJ+61pkLgk
9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULKQ7mUyAE15oHjpHWXawNkdpJd
zvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX3KOOqVC1TalujUxgf5qd
EOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKELZegyewqnT8YBj7f
2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1jLZgePz1+ejw0
/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yuv7n+5vrg
98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQiynr
I5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIh
s05qVsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/
gi7EEGYqBLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5l
lewH2laX3a4Hu5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcg
bZIypRagLRXn1Yug+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0
VOoPmZWz96fHgfm8uRo+kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1
B1xTciv4SvDgw9i714Ph8IsbLTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9
EbyrMabKEXCdoXJmAmRPdk55egZivk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH
41i7Z+BIaFO8VkZzDxjjPajg4CUQ+CbkB6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS7
9fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjtrYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27N
ezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82fArjt4/fPn47tAxpGdIyBHJO55zOOf23
8eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHnjT5vBAltE9omtP1PKvjvI93vRsI7
dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjIyMi7hf/u78O6D+s+rAtd0ruk
d0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf7e+9tf9/iH+0HeoV9Yp6
5benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunLpi9hwYkFJxacAFsp
Wylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8bo5sFhACUh3s
7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9SFX0HT0Dy
NOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNpi1ff
gJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUc
TAS4ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNie
phdP6gOW12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4Km
eJcr8gu4urLXFQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAE
F/BbaS0AhoaefZI1yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4
WJkj6SFgn0ePgK/BY4+SEXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjd
vMqREr/AS8vrC1lDISX3VTnhC35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgy
kjLn+22FtW0OZGzPD/5+/h29e0LRzOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHM
iX6y7xIwV9et9a//x7uVGCwGi8Fw+6fbP93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25
i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8CRxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eX
lxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8xGhB/wX9F/QHeae8U94JXehCl/+i/uO2
j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5FxCFYgvFFoqF6Xun752+F1jMYhb/
69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNTkU1FNhWB/J3yd8rfCWJ3x+6O
3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZWK6vwovqL6i+qw7bobdHb
oiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn40gFrWcva9/C+/bPn
m5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHciiOuqyRkAcnfp
mVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhSYWmZIQK0
eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GBvZVk
MD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2Rlsh
vQV5pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn
3/3wh+aw8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV
1V3RlYWzwbczr/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZ
ajgMnpP0DfJ1htwplqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3
Xzs4Ue9cyPWjcPjolY/OnYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp
+Tv7Fqi8pPjIlpMhJS1mYY4KF3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+n
vRwVPxkeWVO6PA6G89cf3th1Ci6NiHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsti
cJZzlnOWy3s+KCgoKCjob8svsiyyLLLkfZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcf
fABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10
Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5SOcjnY/kbV//YP2D9X8xIvguAdvivcV7
izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659tx+F5h+cdnge7Ju2atGvS38Zdt27d
unXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg7w6A/o7+jv4OHJl9ZPaR2WCz
2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9+3vnm5ubm9v7neMsAy4U
8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlISVKaXAkYKO4JG4gX
4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8HaTldBcjgHoZ
xeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG/CAbdN2M
ceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAYA1Il
eZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd7
3i97+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsT
s+HmTUi+ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQ
u9QfDLNME9Q4SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFa
fkM9cPRhUvEg8PM27U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1b
qArEesefyO0JZxOelLjhAb5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbT
NHBe0k3RjkFGR/uF9DKQkz+3rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPw
z3nlU6JTolOiIbZgbMHYgn8bL6VNSpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYE
a4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O
7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/aMc/237mM5/5/MPe9yoS/13teDfl4t37905N
Q01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9ZdoA1taANFuhbpWqQrEEAAAXlTSt5Xe5tP
aj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76VuIPJLbcUW0CJoJMeBNFMrmpsA8oiA
+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5EBPXkQKCIGKDNAWkVVXgMPGKJ
OABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEXrBscJvEN2FYafjGPAdev
8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4TswFfT53vwtpEdZ4zN6
gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYUyB6Z/VXKc7Au
8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90hWx9cmZD
YEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn3Z1K
Q2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMm
S+tmNNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJf
Qu5q+9cf1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OK
P+wLHlPNY70PgHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA
2T/Wrd7dyi95vuT5kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdf
fPHFF1/8bXzbBdsF2wWgM53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePd
XOcLXODC327+rQRGW64t15b/J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc8
5C8ulHQ6nU73B/43eTc14z+8W/WlCU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RK
bUAK4GutKMjNzeUDfwSxRy6YcwJYLMqxD9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZG
bQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjxufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHT
u4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hm
gscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpNoATJHZTDQG/nRGd3MAyTo6VZEHjY
cNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2zj4L2ncturwumROmK6RIY1kjn
xQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5x+4JjtOZvXIiILtJgr7w
FSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2DjN1Dgq4B63haIcWlv
pGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCuV+c74HNlTWIt
iBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQZyj2U9Tp
oOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrGRNMM
63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998O
baa1mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdj
n4x9MhZiYmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUAr
WtEKIttFtotsB6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2
oW1C2wQ4dPjQ4UOHga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0
aNGiRYu8Ox/tO7Tv0L5DXrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90
rUAMkUZ41AVli2GxshLEE+GlzgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01
C7QFak/ZBnIT+TNJD9p5MV63FpRp2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWflj
b6WWgeSrSTnpl0Ht43ph/xVyxqccT54MLz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBz
YY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wE
hg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcV
papgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP4y5AbFzCgzefQvZcY520L6FswZIH
O9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP+Nf0PubtB47H1o3SS/AdZNju
mwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/77BeIHhwcGPQIevRo8rJH
Czjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9bFU5/fGJSXG/IXF9x
pysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0GXWlDmLYd/Lr5
l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok20RwNBCz
FRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvWrFmz
ZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7b
e2/nfTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDL
gJf/xZco31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAg
cUHigsS8Oxp7w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEm
PEUMALu1BGCbNIwaQBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De
7uXeW54gjwvwL9gP9JmmZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQO
fXUScEU9D/0e4vbGJSZ1BfsP9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9Lkem
gGd749c+JpBidVk0A+c17XTuGbB6W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I
3AykW/IE3XqQjlJIag5Sc3FKqgy63uom9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEi
zNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ
4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQamY/VOQSOfKjerzIXXZXMbPt4Em8qeKLZu
I/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8ToakfInHM3tAzoDsMa5seLEzW3/h
OKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1odT4SA/IapQzLLYYmPqablie
gmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpuxGh4UTLmyNuz4LnE+ytD
UTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCrqcmq9TuIkbNW5XiD
7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWdE3dO3DkRXjR9
0fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA0tJLSy8t
DZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY/Grz
q82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQ
uh3rdqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj2
57f3r5cjdHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99
AHRihisctG/VjfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24
bw8wlAx/FZIBokjWw5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7
mgSZc9NfaVHg+Fn9QUsExaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKr
OTmOcKCiPdD5Ocid9A313cHvcPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0Vd
ClJ70UWuARg1kzYd1A32fdafQZurfs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbO
bAHTaK2UoTDobb4PfQUIEnpkh4DJqi5TB8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0
j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8FazZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa
9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LLgJnAHXHCFQupG9LfpI2CUZX7jvo2P+hX
yw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHFq7fV0wSEFw701i6DlG760ssMvh/q
fih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSVxz9CRp+UUq9uQF3/OqfKfgV2
P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZhkDYno2ruAwivrr9kOQ7S
aO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z774cWPJsybMlz8KN
oTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuXL7/PEWcFgQAy
JA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C1EXzFVNA
quY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ8Iyq
vKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Y
y9s32Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE86
5Ky1j8vqDbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41
PeOgYkbpj6MfQczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1
OuRvJt+u1RO0OtlbdWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/
d35is8CJxGuTz0wE81Pz4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7J
DbMrPIuCjIPWFbcLgtcN77NBo6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3
oPj1Mqsj08E51zZZNkO+7yNvBdnhdpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQ
ddVx3GED23bPbTjAOEAX7+wPzuHKJfMsiJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1w
xYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk40KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWho
uAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtbEK+kafpToMyV4ikIUmG+0caDKCaCJAOI
EY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyDYUqxoWW+B9cM+9eZi8FnctUHzaqD
XFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry+ta/Gej2OLras8E0UnqrdADj
OVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz6yvub4WcMzHnE76E1AI5
g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHOZ5oniMG6IOUaMN5Y
wpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhPaPWMS+HhPk+X
vS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDbBOdKW2PQ
5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhKiocm
b1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbK
ZFSeVT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7
Ro8AV38IqOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9d
fHbxWbhQ5kKZC2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6N
OP/xxNlhz7W9AKmYFC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyAN
FJFiAriWsFC3H+TG+hf6W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8
Kq0Gj4dVTtfzALNX6U7VC4EcSZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7I
LVDPsdSQAt5TvHf5FgaPaGOUR18wV/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb
9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZTQFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9A
pBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFlOGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+f
IMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhqZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6
/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0iGmihBwJWmM1g7Lg/Ez7WssPWi2a
qd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E18P/Efi9CLgREA26guYSxsXg
fJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjbgPO+rBMTQW7pKOh9BHLL
vS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5A9D3MW1wDQNrAfOt
2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3c3Nzc3Nz+yPe
31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQbKK0GkSAK
aN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdAd95z
nXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3
RsI3ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd
5PFyMshdRbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf2
0X5I35bwMtEAOc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRb
QafI6+TvQVsjYrkJ4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhh
Wk/lHmgtxWeulqCOsRfU7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0
CwHvj4wVHSngv9xjhn8zuN3h2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skG
heG635MJj9aA9YTRqq2DwgWL5gZ9D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5Wub
VoOanDkzoTME3vCYKY0Aj/xyTKWv4c76t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5u
bu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQ
MmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1E6H02Obtys8F342hUb71wVnN/2WR5SC2
as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWnP8mQfdTxOGgP2DZnXXFWAWePzA5x
34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y86+t4DiddCJ9LmjbssyuD8BV
U74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3AqZr9/gGRHVRTGsEoqe6
2fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7IU28/SKhHWgX1J9c
HcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPHzPYgxqSPFFdA
3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55IchtlCRugS5H
t1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT9me1
gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy
60UY5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+r
KcCH4pC8EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db
/xbWVSM5PaUGFOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb
2QmgdXattvkBG/Q3pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5T
IWhbQDOvMFB+UvIRAerRN4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NP
kIzSS2kSSEdERyJAVNJiXfVAOS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRS
A95+k7vF4gOJdeJfvTwDKSuevH14FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keY
wdnRct0WCFnPk5+lRoKjq2OwVhaUunIFfSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ
3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGKXJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+
cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYB
y/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4BWjrRIDTCdo1Vz+zE7x6eNbgOOT0
zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBtAVT4oOzXxVeB7q5pZf6ScLnP
nfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5ubm5ubm5/zB9OnHVd9P1M
/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnkBHldQEDAXXBtdHg7
KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7VBZSwYktrXAd5
v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV4c2r+IOJ
seAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bNIAbr
J4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVt
FdVkMDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAq
qowFsZ5BYilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKr
sbpdbQSap3ZDPQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZj
L/Cp4CNMEuT+aM/nGgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSe
AvMh85PU3dJ9cAyU7ruuwdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/D
Ybjz4m47x8fw9PWd/XeiwedMuWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDi
fKbuhZGXRkHNslXuV6kF8jVpi0gAsUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8C
piX2S2C4aCgpfQnaGtWTTWDoFJpaeBSoV7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pf
g35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8Tn
UevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAWjDet7XKiQVmbGpZmAF2kTyvfB6D1cj51
3QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Qa2PQbQFXvN9Rv6GQ6nRGahLEzUge
kvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOfX8Dp5dyozoaURnGz3kwB+al6
jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6FYon6A3SeSkIFEno6Azi
qtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2agNBLNyQfSEKmBVBqU
h/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjBXssxxTYQXGWt
JazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0vC9nTc6zp
CyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx+RdI
JdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ct
Zyx4NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUA
jk9yK4L4QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4
zT9BVwhcjyzhEd/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50
feu8DGK5tlxYQLojjRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v
7IHEZm94NRWUOP8evk3A97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBn
ELw5X1L4CvDN75vtdQJMV/QHDTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAA
jSR/+QcwWHQ6OR/oBks9yAUtUPpaGwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQ
NstfSdGgd0qHpC2gltSechDskprs+glEGaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9
ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9vLqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7
ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/BnuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5N
bwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1MavikIdalHnT/Qv979gEdOTk5OTg7U
21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqqMGTIkCFDhrz/D5BVq1atWrXq
n4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFyitsm2n1AacAGMQNYS7w4
BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3FHSbfBJNRsCXRpIe
tENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+sZ9LTgCYuV2pb
eLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C7yGWwdlW
8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVokvMy8
d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEg
SvOKWSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxV
x6gXwJUp7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71B
mo2TvuC6Kt5KPiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/w
htyHuhH6mpBuzfox2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D
5qOVdSWD64pYrVsMhiuGXVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYU
WVBkAfw85ecpP0+BOhXqVKhTAeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfI
wAoDKwys8Oe9/l9NXBPXxDXY2XRn051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt5
24ufLn66+GmoVatWrVq1fn/5ChUqVKhQAc7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5
X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byc
zn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgAOHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2
FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8FMR90d7pDfr5+qOeHcBpSu3xsi9k
D7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTFXl96BL6i5BjvgqB/qZxO+hDU
yXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwnDGvNd0AqqQYaRoLutHel
4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TPATlNFywNgKxlb1ak
3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXSKoBI0xJwgrCK
QcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaCuCS+YTuI
g/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAagptij
aSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD
/YCkKj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og9
6s/AH0xafXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYP
t2BItSHVhlTLS2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u
627rbuv+NgH6rfjlB5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgs
BovBoC5Xl6vLodTZUmdLnYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkn
s05mnYTmC5ovaL4A8s3MNzPfzD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225u
g0unL52+dBrqUpe6/0U9X058OfHlRBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6L
V1cSJsEvF/cfO/McTIcNNvNXoFUXTVkKRBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA
4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3QvQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw
1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao4AE1HzVy1fMB44rgnMiKkNLGttZzH0gu
r/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxvMgtZfCDjI8u57J/B/tDjc59KkPzG
u53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ceDf0AXNUdDrsK1g/eNkq/B4W+
jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G3RFRVGsGpsVyT3kV6CtT
WP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7NbhIH0hWu36xY4Njj7
u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgugBIkZFEUdFfl
nuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTWSO3AMFDq
RjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqurwze
H+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38I
fR36OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgnt
EuD2j7d/vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz
2cB5yXnJeen3v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJE
iRIlSgBDGcpQ4AY3uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwY
bHq06dGmR7C14daGWxvC8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz
5syZM2fynn8y9snYJ2PhZNGTRU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfh
d2fEnRF3RsCuSbsm7ZoEL8a/GP9iPOx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/H
Hx5xlg3yao+B0GBnBWOd21DNXCm9UDuwOh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0
RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhCFakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SO
O1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73W4D/EuMFwxLIrKwv698UHDuNelMiOFMd
Uzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lHGMHw0KdPwDLIDbA8M7QE61JTTWM9
yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8iwZU8f8UnJ2yI23FQb9VO+66
DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJb8GwWVfOcBxMM/UHDCXB
Mcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC9HetAhGgmoU3uJpp
jygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJKjnxcag5qK9FQ
GgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCeiQ9FTdDq
80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DEfENp
AiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycv
gfo7SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/E
PpAfyY/kR6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESl
v7//5I7JHZM75iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ
8Olrp6+dvgbJ0cnRydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpap
WKZiGdA0TdM0uH7j+o3rN8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95
PvJ8BD3X9lzbcy1ImVKmlAlXGlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifK
J8oH3rR90/ZNW/C/4n/F/wrk5ubm5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1
axAREREREQEtsltkt8iG++vvr7+/Hi71v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1Dmo
cxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+I
SdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPAUcfx2tkd7DucJZ11QdbkSvIbEDvEEhEG
ZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYBaXipVhVc4PNZ47s9N0GwpfWhgR+A
7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk131RQLym7da7MA+xXNyxoOak/H
5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9Wn91z5j487/q47qOeYF/o
vcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjqlq8c7DEcrHbwJaxK
3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3QTQTXNe20+AI4
Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6VdwCfiqigK
an01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4VFd+
JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyr
pXbgHWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBT
OcjZkDtM1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0
I/Iea1e1q9pVkFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/
m1rxbqqH/YL9gv0C5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d
+sfLN3rW6FmjZ5DSKaVTSifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1
L1BxUMVBFQflXWC9G9GucLnC5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1
nPWc9RwkzEiYkTAD8uXLly9fPoiZGDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rC
MmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wp
luiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKfs5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0
rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpnlk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA
/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWBx+QLm542gVc1Ys4nrwDbaKLlGuCq
7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw4nXSw6RJ8Nh+6fMLJ+BZ8uMV
D76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8qcjLfd2C4rd9mHAq3H9w7
cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y84QeVd1awlB0LxRsU
eVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwfmKf5VwXHx/ZL
ji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt4v2R3zIw
7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcBK+nc
BT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0G
jhQhLEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb
0TaiLTyd+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFx
cXFxccBBDnKQ/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se
5S6Vu1TuEtyUb8o3ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU
+/3VFyvFSrES5F5yL7nXb7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH
5ZBySDmUN3XJuNW41bgVTMmmZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X5
6wvL5oHNA5sHQuonqZ+kfgJvD7w98PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfX
Sf7i+TFo5lE7uq0C525dfn45BGxeru726lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZr
N9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYe
p8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GXgcs3NdjSDoylwvsWqg7+HWpOKvkLONdn
f2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36CuxHIroWGA8v92a/theHZwUuRV44
Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZZ59+Gbyc9mZRTEeIO5X0aXwW
2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNcYUIv7kPGzuxo+4+w75cj
B0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qDT2vfix4lodub9t5t
qoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1OrdGQOrKtFGp
/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2MmKEVA22Q
JrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEiUCSB
WoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9
oNzccnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm
1ZtVb8Le2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCC
Eu+//tk9sntk9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m
8ZnFZxaDT0Ofhj4NoerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pS
VamqlLf9VsVbFW9VhOge0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c
6Huh74W+UCy7WHax7Lx4745Lo22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269
GErZStlK2SCqR1SPqB6wK2ZXzK4Y4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G
4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk
+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNSn7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1
B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687
wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJTEl5Nva2/ehRelrg974YFUl5oE+kP
uqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLho60FR3m1jLYPlDjDFIMF1IJq
D9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5qqme1xawVLeGak1BHem0
5Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3BZ5xPCc9zUHZv8bji
/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfBccrxNH0PiAeu
gY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD1l59S35g
oXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0nnRFZ
QF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUs
mD4xfWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1
q9SvUh/23dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39beh
ZL6S+Urmg6Ldi3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk
/ceLSopKikqC5NnJs5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/P
fJh3QfFurnuthbUW1lrIb444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/
6ino5ub230S6dOnSpUuXhKhevXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2x
rlhHWk8orCuypdQxSOyS3fH5Xbg/70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0C
P6PPC/8C4H85aHrIS1AXieZiOqirUs7dfQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl
5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhD
JOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSnV5IGZ1ggt76H2fcc+B7yDPD8CuzdrOus
lSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb0KbLtbQUoI2qF7XBMd0+yzkNxBFR
T+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEduB/IFeYBUFaQp0hKpF7BeMtML
HGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+StCzQJct2XT0wDNJflKeB
Okc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcMQveEhgRvgXyDw46G
F4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6roHQi9b6ieDa
qNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY7mzg6gOu
yfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFloKR4
tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX
25fbl0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c0
6aSTTjrpvGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQ
nZtwLvDGr2fWQ9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfF
nthIeHr3+fzodWC+73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3
oJhqHp/pwGPxOSuAsuKgboB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2f
ptkGgbVMlpH590FQm4oFiz+El8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKi
XlHfBa8PJfaIqwKJ51M+T6oNjFNvij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGC
Xti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRHykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5
Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgrspZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoM
aWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZpM1I/DDKL6KtGwMuPoqcnnobYVrFfvtoB
nvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3AEmFpaA+EJ8uftHpogLJSrSIuQnIu
ZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYmriKc+fxCiUsfQsycV7WjNkDG
XzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7hnitgXNT7GL9AzJKEOYkx
4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA3GZuM7dB1biqcVXj
wJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR4EoxsA00EouP
guCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4MtkHdLaKPi
N+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZlDJO
Qkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7Caw
TMwVOiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADy
nllQrw3KAPE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdS
V7kD5kDjrnkOxOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJg
elkvq4CYZp4U50F8L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMno
pyFq5YuSL1aAj92xxNoW6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+
BC8evT7+WoHYbxO/i1sBrE0YoC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasP
AqWJOl6eBLWB8qXNH7THlr3yKuRwh7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/oc
dXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/uaP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumk
k046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xk
boDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh04lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l
6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8dsaOFAit3TZrlxxgn5k7Z2kH2Hbm
quSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGCcSDzrYgu8PDuxXmXdsOTUtdK
XckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNez2McA/Gd+EmtBZ5IVybP
F6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0ZolYBba2ts9UfxDV
zZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RIMN6XsfIm6Iv0
CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gBGGKj+A70
BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7ymvW
5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghv
AQGf+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8
C94+cV5njiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARF
wqfxzTP0HgF+Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazv
g/u1Z7OeCGKpZrd9BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3e
wgwDz/svyt0cDfENdgzb5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQR
z5TmELDaUdg3E8hA/ZlRBxLPJmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4s
QRaQzeUd2QtEJfZxA0Q1WuAC+aX8SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2e
Ua8EpsW4LzeDvGYW4zqIQOWxkg9kD3lKrgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7M
ZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc
0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/WulpFOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M
/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1CXgyePq7zwHNzJFiKih3lQvqFtD8
NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1iGWAz0WwnbXFBGYBadXClW7g
TnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olzwlev6qeMgkznLc2LFIMe
QY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs7FPk88fg2pOyWZyE
U112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwqPBLMhuYQYxEo
G0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUIPDNeToo7
DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3ZmXAQ
ki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssM
ohh4X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN
1CxaZ207yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2
ahrRoGzSNGU/UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ks
n4FYqnxghoP1pvWa+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUO
MEfIT7QvQD40n0sVon6IGRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZ
b/mN/bvDO5100kknnXTSeZe8deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vf
gFudHt28nx9evHjp++w+KGuseTPkgJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJY
ynhISEo69WIN+Md7NvtOhGw9slTL1ACCy4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tB
OWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjvGweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDg
XFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wzZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3i
jTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh200cpp9TMQEcogMRm8ZfV2ehEQm6gi
ioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CHiCAEmDnN3XIxyAfKCh7zX+8f
3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPlTRDlRX4RCOYnZlGzMYhZ
vC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhDbZCP5RwZAvSUuc1z
IK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPLuyC/li1kTpDH
5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9l52iW4Lv
Pft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ecMlvd
LHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDE
PCWArpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vj
onUgw4KMoXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCq
gzvZ+6GxEMyNZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXI
LcwW7cCM56UMB1FQlmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6
i3CQX5FfmQJmC6y6E+R483OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ2
05AJIHObdrkLaKxkkKvAvGBUNB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUb
MyfIieYrbRVwkm58B1Qhu5kBjBbmA7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqr
lhP0+fpTWoNSWASK3CDK8In5AYjsMqv5CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywF
nmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5
+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWs
XbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGTo1AJeB6RODHqI/C9Zw21Hof7616+
ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0ZR2dJ1D+E8hern+v9FaQUcVqd
g0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx8CCwdwp/bO0PCR2fjH7w
Hlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeBvtBcDuIjkaycBCVa
zab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBGUT4Dacqi8iSI
b0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dgNqIUW8CS
aOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNaSOQX
m0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh
1DR2Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxV
EoGOIi8PwbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9C
oKeTTjrppJNOOm+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dG
ZQTfJq47mj/I0wHdX52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3P
TsPFK5e7HSkKvn1CS+VtCKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC
9eVhoDR1+RyU8uZyMQrMytw1pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu
3/f9RoG6VPlRuQVmoNR4CNYEW3bbaFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaR
BQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWLpaj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds
1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsx
sM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kYLJnULepokCbVOQdGjJzFLTC/ZiTrQD4w
w8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCoJexKJWAB+/kUKMJ88RLED2KEmggi
UviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLtApYUbbPPSZAVzL3KLTBe6qXY
A4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHmTtDvGkP07hDT49X0pJLw
+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwYbD9nHwUJW9yTExtC
RAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzpz6DInBKrssXA
o9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+v/qsUGiz
st2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJfGq6p
Z7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ
+iOoiuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEX
gLHETDYvAhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbY
Wqh+YDxx3fNcAPOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WC
mQvIzXIRDto1Zbj2PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7A
LiqDOo92Sh3AK+clnQfvNM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJ
IE7IfEpRcBxxDLQvAWWd1sh2CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTS
SSedd8VbV5xfdo4Od24Ga7Btsr0bhIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSCl
V0oe5264Uvr5ugO34U71pyOu1IKE2Fd1ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/Lf
tT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZ
rc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYHgAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2z
Dcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcpjdPmYrA1tRRXHoJyVOuk2UDV1Bra
ObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1ZXbjLrhWO4emvAJvZ2+Qpyt4
i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFyAiPlKtkfSKY4I0EsUpxc
ArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6A8gysrCoCdJijjOX
ghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0QmBZpPhaLoB1
j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tfDXJC5ltZ
ovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Zm0DG
I+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf
5X7Q73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7Hs
xbIwYMCAAQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fv
ZLLc/5383X76pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUG
Yh+4/GKnwpO2Ly8oF0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjS
ZqpjICXG9Deng/Os2TFhDuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru
9wYgk2wuQkBmkCVEZxArRCk1C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVM
XFfaQ8pUZ+2Uz8B9Wd40B4LMLqLFZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Y
m+QcszlorbV26gegVlSrq7VAGaOMUCaASBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV
6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoaKB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7m
o80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCUFVVFQaCW3IovqFYxSf0ItKHqYrUsyBSz
sugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5+Vz+DCKKcWIyEC+uKs1BPaw+spYC
z0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oIE+QB2cX4ESgiKtMElCxaDa0C
GPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX7EMhx4pM8ZmOQc5zER1C
/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC+6/yU8JPCT8lwNo7
a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZCm0NtDrU5BJ/7
fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/GH9nhP8VP
/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3Xdx3
MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9S
Knq7JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs
/KEmE+Mh0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7l
nOWOhaTaxiTmg7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKW
u6Dt13ppy8HSW/tEk2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9bi
RxC5hUc0AxbwMeuAkVwxk4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPV
jWCZr23SpoH8Ue6iIrBJLhYlQDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGgu
NtaCaCf6KQqIzqKLehXwECmqgmWJZa9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ
0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWfA/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46C
rCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JC
vYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQlcTjEX0rqkpQA3jNGY89OsLVUp5vX312g
Hog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7uLi4uLg4GDp06NChQ6HBtgbbGmxL
az/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yHDh06dOjQAW5WvVn1ZtW09d27
d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZsmXLlmnH07Bhw4YNG8KS
K0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW0Ug9zj/jXcsVkz0m
e0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P89+1SKzh/ZK83
1c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8DG70v9H/
Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zcM2nb
/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPa
eS4VXdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G
+b+bt06cvYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2w
lo6dCjxMGhijgbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHg
GeEpaXkFkQ0ibyrnwPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc
1wYogRBb90HR+2XhyaNnAU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYu
MRVkLuOq+RwMRa+jFwazES3NvSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5Edg
XjevGhVADBRdBKBGq04RBYpBdZqDfGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZ
Y8C61dLGEgLWbBZpDQVrS0sRa00QBcxXsizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU
3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqHgTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0
fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkO
WmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3kjuD9ytPkNMKeht3jpRPwLUt8de4
dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8hiF/uPk0CRPZ73cNZAaKPOJt5
Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu237f9vm3akPP8HvN7zO8B
P7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFjIsak3emPyzIuy7gs
adsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL07a70OtCrwu9
oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1etTLtwpJ7A
UxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHvCnz3
P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68t
YVvCtoRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz
7c+Vtv7UqVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2
IgwJHBI4JBAOTj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nu
JrubQK21tdbWWgtTf5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQ
R8BeS2dQ8plrjPIQv8JIdhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs
/hkgx/mAXpkTwV5B3tMbgOXXpHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVb
CFJOx1gUK0S2cE12noRVt9e3/rInEJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHc
S32HeQLUjBah9QIxVpRTZkByHufzxHbgXqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzM
VP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHFpiQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7ayl
J4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9GLTmPziCnmZOwg7FZH+ndCMpLsU3sALW3
OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQiRMWELPEbRqDsp4zLARVV2dyErR1
yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQnBC0NjQpYx0Ic2f6JUcVCMsa
USR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnGfn2mezzoQ71RugnmV8YJ
/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1cTQDo76saFSH5HuJ
++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh+s+2jZC0zpOJ
qSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd6naq2ylQ
PlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2WbusXYbY
ybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/
qRfW0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D
6Lmg54KeCyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RM
q8j9VX/4I0rPLz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6d
u3Tu0hkyfpXxq4xf/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0y
N8r8D/aNaR7TPAYu9LzQ80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJo
PPcbDwnT9edGMmg7bbuSBoAc5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2
ik8gAFyv3U2Td4ExUWmpbwGfoRGjbN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH
5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRYZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36Jf
B5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrKsoYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA
9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRNdFR7gznS3IIEsU/8IoqC+qk6TpkKopJo
I9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRXySdiQElR3lOmgTJZOSBegjpIW61t
AeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s20ApbKlhOgBatfaglgzZHLaM1
BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LLQ/zE6LKPvoaEQbFfRD6D
JOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjnPa+9u8BY4A1zjQbD
Ty/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSPy5GgvzDWeDeB
/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157svUD0G97
uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1lKVlK
lgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j
7Xd0jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqN
zx+RWnF5W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDB
QTDuxbgX416kTWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq
1t1ad2vdhe2Zt2fenhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusES
yxLLEgvki88Xny8ePvf93Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9q
p//UOP+dPd+2g9c+ie8bncAcrWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuS
D6iRxhmxCDIe9GsQOBEyfpjhczEDLLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU
6BkDPPFLIGxA1slOCRneC1zkUwiUbfZhfAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW
3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCyy5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD
1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLkeGKc8VVqA+EndrnwOcgFF+QKUFswTNUHM
lS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5zjxi7gXZXXY3u4I6Xp2lDAKlhdJG
1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9LF+D1lzZpuYFrYg6VYsBzUer
ptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/Gaz97HvtOUA2MCeb30FS
nleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBYO1teqSr4Tg+wB5+D
kFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7mnll8JmT+Ifvs
Qj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8Ck0G3+CA
HsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6itv2n9
Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc
7nM5bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVe
EH87B/2sPCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P
/Zs6tJ1aqUu9cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+
qF3qlI05xhxjjpGWSP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/o
mqbX6GbRzaKbQb6EfAn5Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2
fVM7/afG+W956/c422+GR74uC2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6
X7OM38DNKEuXZ8HwIuFuOzMj2E8rJQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk
1athEBn90OE8BhmaOeoETIXkCgGVvQqQmNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL
6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7vOTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro
0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYrOcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKw
uCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj84rX4ECjPeAaA8bNsbGQA85ZcIzeC
fEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1WfrK0D5QhujnQTlmvKTcAPjySqO
g/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0xWisPrnHJ2ZNagvkemzzb
QJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXUE9R62g5bLdClHGgm
gtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsHgWuwMznxIljz
q3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1MujnXf30M+B6
qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepydbm6
HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/B
pD5MGHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3g
WOFY4VgBX2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/a
a0zFMRXHVPzn9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKV
q/+H/hqda3Su0bl3r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7
/FG7wkcLHy18FOyV7JXslf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83N
NBduTb81/db0tETb08PTw9MDyhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hO
mHJ3yt0pdyG2e2z32O7/ej9I5U399F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778
m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56+
+CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Coyavubi8ENKO62Ruim2vjEgaBry1koN4clGtG
eTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4CLhu3em8BXElkh0uN3i3aPvjpkKuKyEl
KvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzKOibXa0iKTd4QvwmeTH5W79EeMPKJ
vNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqAedzcb+4AJYc6QKkIyhpxSZ0P
8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2IoCLdyGx0sBTTsDUA8EIvp
AcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL7Eftl3weglWzZfRp
BepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrijXNWSZwA7GWd8
Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwIcyXIEyJU
U0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+EdA+p
GPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWi
elGFb9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYib
p0Du8jxKHA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ
8/nlMMdC7ks+quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61B
A8RhSMojlj5vBi/8427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGU
MWqDskmrKN4HsVM9LU+C2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZ
C+p1MVu1AFk5RFOQeeUDYoCuZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPA
I3lTvAbpL0+YS4DmopQoD8Z7MruZFRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSB
MkT0sihgWo1OnhVgmsYl8xjYfrVb7fNBy2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkE
wm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/vWmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1
m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5TT/rLATmSnfhlMNgrSt9jevguW8EEwfu
r7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczKme+a7cFe3FHA7gX9oMeQW0CUUbbK
OeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmNCa5NYIzSf5UvICi733d+pUDr
hY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxxyS+ddP4f5K0T5+wvwpcq
fSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEpZY1FsjdoCeom+0Sw
vUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeBfd76juYg5tP/
dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD4DnBHPaA
3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7nAPb
YNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkt
o30agfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCr
gtaaK3I/qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39Lmy
PphLzETdArK/+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g
6my0PXoYxDpe9XvRETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvr
yOD3K8SfSpwSmxPs7/t4rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/h
wGUQPyuxY5Iv+F1QgyyT3jic0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdf
zdu/x3l/YgZXFsjRMWRtJsAvv62QzyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmU
ehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t9
4B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5lr/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpH
nb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0f
ABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuTrREE/RxeJqcDAvSwatn7QmDTDD9E
LAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34Kjs/924acAv98wYMzHgKf4YHf
h+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd9l0B6miry+EPNLDN9fkF
zHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLaDyAqqweUPaBFWSLU
7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSywy3zPpYIn0p0/
/kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZApnyh+YNr
gNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdUKuQZ
hJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTm
Zr+xG4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc
2gMc+wNq8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHU
os2WbaFAgaxZKnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7
Y10a8CkYlc313pfgXZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVo
CKIMHxotQTRWc1IJLEnqMl8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0g
bHKdeQoMyRf4At+IIuYo0N77r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKm
A42UL6wPQMmrxml9wZigR+AFsxUf0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N
73PXREiZEf86NiPYrtun2dqDvbO9t+MI+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ
2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiP
tHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9HYPAG+xclLwFXKdTmiTaIHiCfxP/raDm
U4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukUAgpr27VeAHT4u4M8nXTSSSeddNJ5
N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fyJ0ja4rE448F0uV7a20H4WMfD
HD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZunnGgaOhfbX7BiT/fHmc
awd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9Arl0ZBhbYAA/tN5/e
ygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZVcmjXwVbCMdP/
DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG2jFrfUdP
MNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkDnJXA
W8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1ja
akPAPdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2
zHbbVgosIZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt
2ggiUri9JcHdxlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaI
I0aivha0VcJKELg/cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18
miY1AJvTXtDxOTjj9B7mPgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+
QYmAuENJIdom0Bs6Zxo3IfmeUtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE
7MlBOzz3IcvH5SoEbwTlgqPx6/ehSA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwG
fbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwFtJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2v
Qdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYiJ+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/S
G/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uorn/EgylrzKQfBLOuNdn8JcoyR21sDjFtc
NZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw8Kw1LslvwLPdvcubB6zzNcU2GpQL
SnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3Qe/q6ZHyK6hu5bX2K5iFyC0u
gN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0fPXKuRN8WnuHG8GgzbBU
tQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt27QnIPYaXykVwPOV
9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkBycoMQ1A2t+tZzM
A7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+83jrxNk4
rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZvC2eS
2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9be
lrLW+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGY
j7QxtrkgxxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kO
Zi1PG/dVwKG2UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaK
W1aCPty4Z9jAU8ez1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRR
E5QzYGYy7+hXwLmAFdICZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POM
vGA2MXd4J4MZbT4UA8GMZIUYBpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkp
d8lZ4Gnsfu2dBWYrJcrwgHWE9bTtAehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2
NbBJyFjwCQpyhx8G7pufyxUgh+pT9SpgFvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65
/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aSTTjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J
91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7NgkiMgdvlhGQqXCGW8piSH7pMynlNrCX5bID
KJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5wt2eauyQUexw+uNYT6FOs5bS11yHX
uOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF9o1PWbBp6jTVBsoA5Tj3Qd4T
LY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0FdhpcGh+qb41gXrOR+PZQTY
7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIXSBga/8Gro5BUJmFH
bFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUOzKmsk3fBXtZ+
zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlwPXdmSAiH
lPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6Dczn
5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8
YVnA1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYk
gKW1vbHtKGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoB
NQPSvgCW+mGTp0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2
qz/y5//t/Lvj9d/FlsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Wh
b0nZEpKijXKvTYj5LPb7V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzz
dSoLIGcP/17hU0FL1AqpX4HlolxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3eh
Wpa84P7B9TppJogcMlovBfFXnoe86A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zP
QQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/
bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyBKXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5f
NXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yWB7/OGAG+eXz9/I6B7Ka7jY0g84veamfQ
tmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVnp58WuPMUnJNcj2L3g/s9V1nnfNB3
efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5TeSpjSEERlYRHdwWxDOfEL0EyJ
U6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cKaKiVtBogigpFpIAyR2uo
HQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7PcpnrE/mI2VGWobUD6y
zrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rthBbgPuo6l1gT
3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhybkXYh7Hqq
66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0FrBq0Z
tAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafk
PZi1I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/
dVVocLHg9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+z
YmCba7VbY6BQ/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2
z69g+HrsKZ3A+MVVN/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwB
xjf6e/IUKM2VetbS4L5mjHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW7
7ZVDBz1ZV/RPwBxknDMWgTDN++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FE
zayOQiPAf6Dvr+FfgPmDPsxZH4z3jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5
x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2rQE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBP
s2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXl
YXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9
t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv2076tgJzjTbMkRsshe0bfKq9u0CN
i4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3QsmXLli1bQrPszbI3yw4NGzZs
2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rpabyr8a7Gu2BO8TnF5xR/
8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X7fDP6ue3y79r9127
79pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3Sfn9a7tNyn5aD
8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/zqzeNlz/y
5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpKSkpK
ggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v
/0nI9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJ
AAGihHeKWhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0U
OBIta7RwsOfR/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeD
tOnVvNPB2Kt/7bkGWjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNK
guOc766g8WAbbf/eLwoskbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+6
1fIleGaaK9VmYGnqkxBYAqy/+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u
8SW/hLCkLPNyR0LIjvCh2QMgZGv4sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6f
oVLWK+Do4bcsXAP/+yF5s62G0DZZRxReCqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DU
VsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTW
BKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5Gxi9PB7neFAKyIJmHRDzucVs4KYw5Ufg
Kebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+4jz45LBYZNS7C9TJ+yfvn7wfwh6H
PQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOflPqk1Cel0oYsl15ZemXpFZh7
du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF5WHFyhUrV6x8d3pJpezF
shfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7SO0haYnOuiHrhqwb
Am2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3funJYIfvTRRx99
9BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym/UyNnxo/
NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue7Xi2
4xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k
1QhImSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv
5XFQchCuxoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78C
aHVjfkjpDbKee63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzO
tRa0Btply2VQY+QlmRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauP
tLVg7W/v6jcXxCD1pqUIqIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5
YQwH8R6POQjGfX23uARKqLW9zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1
+KutAK9ntvMyeGd4XiR/BpwxJshPQfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcr
gAzgidIe9PpmG4qA0Vz3cXcFW0HrM6UocM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/
YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYyHNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6
vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCoZgG5DZgkXeIqiMqq1/4tiEuWamY38PWq
jfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmtrFZWp63v3LZz285t4cOPP/z4w4/h
p3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDoRje6/etOMKkXWEuoJdQSCt56
3nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8QcE6Hqzqo7q+6E1RlXZ1yd
ERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Zb5k0/SyusLjC4gpv
b8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEHbGMb2/jrNMrc
KHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou67iswB3u
cAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa82vP
rz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvh
Yq3bZ17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVK
a3FJ+wzkFHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+O
TpAtMdvsrGPhnPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAX
cqkBiB0UUh6Dplm+s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXp
y10aaAlqe2Ul6C/MSPM8WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOc
va19CMhoqYrOgFUGmH3A1ds703kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtz
zDCIa5b4fnJW4LnxUi4H7aIWYz0ISoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU
/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVN
L8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAnuGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq
1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9
qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKyFGh7tb3a3t+vF+fFeXEezCfmE/MJ
DDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+svy63ZYlliWXJm283s+jMojOL
gredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9+fXl15dDl2JdinUpBp/7
fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5Th+wf9HzQ80FPqFih
YoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jReaE972r99P6lT
A9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoVK4jJYrKY
/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2NVxDw
je/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQ
hxA98FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui
+Ly05rWVhcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXs
q/0OgdgssmpfgTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz
1NRzgG2pVkWrB+rXVqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7
bPvWrzlY6lg0bQtoxdXb1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7Uk
qAky0psL5ADrCdUETw33JiMXOH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2
BfWu+qPlfZDzlfFyKzicjoP2xiDmynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4Jyoo
BsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcb
oSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8UZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby
/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVLlyyFKturbK+yHY7PPD7z+EzYennr5a2X
IcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyBmJiYmJgYuNvzbs+7PYFlLGPZH8uX
+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E3Ii5EQOzi88uPrs4JHdO7pzc
GQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+rT6rHat2rNqxtO6md5re
aXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaHbQ6DUudKnSv1BpXE
VN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7vWq9ZxmYZm2Us
TGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P538VbJ84+
twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniGewKh
8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIz
W4OsK8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG
9N3eSE89MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxX
As8+d0XnPVAfKTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1
QajWML8R4PPcZ4AlAFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYj
sERbTM0Aa1fyi2aQNDRxXPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQ
njtofuBN8PfYuir5wbJFW6kUAREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5
BpT+ahl1KhhFZVvzInh/9YxzDwTKskXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjF
YKzXW+sPwZbfOkULBLWlGGoZDXo1Y455AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeber
Ghh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMqk0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2
lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFCRwsdhenzp8+fPh8GMIABQMdCHQt1LATd
5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT8E3DNw0HhjOc4b9fn/o6qVvTb02/
NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN7fi2+mybv23+tvkhpkNMh5gO
sD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+1H9S/0n9JxCSMyRnSE6Y
cnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq1KlTp04dUMup5dRy
/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP+DN/fVP+3f6d
zv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4sLbSrzcqe
oNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+zj3SD
4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5
XtkO7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQf
btQ49MYuJ3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6
geBQtwV+ACZpVn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0Wrp
wBYwnJWXy8XA8LMpxJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALe
Fo6DZtITtH0gf21cYdFA/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TN
Ur4tBOSXjJuMpUGP1qoHJoAwWxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALK
WbWJlAmWry17jCYIG2aNNPQCYVEg3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9
ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsDdcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4
WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ecOw60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A
9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5DIx4+73j7134u4d5UNB/poJa1X+1RvU/
VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/lf9rrGhT0n+DIkSNHjhx5DDPOpAph
4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0GL8+Obln3AHSsWuP797tA7vmc
VFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj4TUQRupZ+kLQGgjT5MXA
VD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19lf/R10D/mKXE3xN4o
VqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNqyxMWBaQk6aK0
BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUHJgNoZ/Re
WhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzEAeJo
8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfA
XT5VL4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1an
g/SupirDQTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3w
jeElkD7wDfA1g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKs
gyyd5H2ghQnLzZNB/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysO
rDiwIqyqt6reqnpQI6ZGTI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZN
BNMFLTXzLHRxRn9d5wS039bu2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuD
GqIvzO4Ckl08EuYGNnFZuAz6Df2uOA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/
pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7osCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsR
As/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+
kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxXrG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLe
EK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10bA0J37XbgI4h6NiTGlgjey55vPN9C
vphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsMfO18G90DQWppaGR8FhyV7d0t
Z0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuAcEv40fQiMJHzgh+sP1m3
GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7hOc+ZD3r7JhTHUyT
DDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhcQlggAgKTNIvw
DuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPieHAXma+ah
oQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZodLL
lV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuC
OFWfLi8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ
3WU1CPvKUC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5
O8DV2vm9OwnCcqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPl
ZfktW3kwP2FND8QARdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinf
gDhNdwr7wVBNjrP4QI+XOmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNX
k6uC2NfwrHEDyHZDFVMMmOymGcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8
m2vKZTD0ML8p3QY668dMGvgmKoP844EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE
26qDwWCYLntM+8CwyYh1EHgG+HsErBBoo1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegf
a98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVi
bTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3D
eoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/FvBfzHixlKUv/0QV1qcu/URL5r/qf
9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577VciJ9VOrNWFLgPCOPFuyCW9Sxz
nYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2Bj2ZD6UBIHzGEf87wAgx
Tk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6PAO2g8r7rU5AOWxaZ
i0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8SNxyML5qnhrwG
OV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO9Bh1sBIC
3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqehsh3E
tfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3f
S/cgLM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0w
dxbtnAOvxZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0J
YWmOKNP7EO61lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWF
peJZyDqUEcjZC2E7QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFB
j8efTpzvN3EOMLaH8Mz4fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7e
mlnAJLWBfyqIy8SexpGg6srBrJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8
eNnRbDjx6umembugd0afeS89CyGzm2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/Mtg
ulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+s
U023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8QKs4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFD
QS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlriaPBleW+4h4A+0Rcv2MC/hQqm78H6uvVo
aFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3BfAENV+TPPJtBDAzGeWJBek3poT4Ld
YR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73VwvZa/L30PRO6KjLV+D+Zmhkzx
fciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUHqC39zfJvgulJ613DaMit
kfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8Jxqetqy0HwVfVH+lN
ANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA4LetE3dAYKna
V28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i+buHd1BQ
UFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+Fb4U
NwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO
96WdIF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuH
rXhlsNQJGRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B
3aF86YsEb+WcvRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJ
A+ublnXmIuDPd77pnAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DY
JRXVuwK7qeM3gatc/iKlC6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP1
7sl6/gsgYRgmx4H/vNZWKwf+K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyo
NADdhlGPAfmEcYI8B/Qs0jCB+oM6S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/
gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9
rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEBiEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoK
CgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVBU6yRYkfwt83skt0QxK/Nm0xRICq8rySB
Ok8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzPxYfomyC/c94mXxEI1cIuh80GTzP/
D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILYKqa0+TMwfBweEvMscNM2MawC
+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeTCs4r6UVudwZPMU+7+M1g
NlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/PVC/VndKFhCXaFOk
NuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0FMV6YbNwJHBNK
e78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQRweG+p6F
wFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4jUCQq
5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQ
iwxmzZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+q
AkIttbGyCDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCg
oKCgx0n8sw1It/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3
QKmQH5v/IqTXPn3w2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZ
JeNOiMuIbRPyOvgauMq63gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVb
ZdD3SPsNkSDk+j92doDS5uIZxfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GN
laqaJoHniDDU9i5cnJ/0UfZYyBvmi9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus
9OS24H7LfTd3Kahn/a+5zoD5PVNAagzWosa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3
Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsGlnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTs
dgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqmgnLGv8h1CHy9PG/53gXfi/7VzgiwbpOy
NQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+IpeCbQ0mkp2EMeq4WoEGMoLHcT5EPVq
qCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhKGV6V5oPQRUokDPy5gZvql+C/
6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX/S3BleVp7twBvhxa6X6Q
Qo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcTX4h0g+mc1l8s+ncP
76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1CfA1+nLn/wvqn
oUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht9fqWi2DY
b3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSIO5Ng
AOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O
+nwtRKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dA
QQSxtt5eHQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUK
tNX7Q86p7LysgeAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhT
cLt/xorMNyC7t2u+9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3c
c712MC6XIqUfIO6bsBrmiSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJ
ZRIpDr523mm+KSAtFyaLyZDTMy/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+
CJSril/7HJRx+hYFENfrMw0/QbHosDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSK
X/peaQHVeXonB//uYR4UFBQUFBT0OPzpGecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5
V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3ICpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1
n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8XvHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZq
r4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupTyJ+hJ+uh4J6cNStjARQLjdgpVgbD
FsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN+BHyxuodZAfkeIRo8wzwfK6M
F/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6PtoVAsKeZa+HtgDGiLfRpI
AfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+sfgW2btapjtLgnuBq
4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqWTmuLoFj96JVR
aXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBlcdaS8sG/
MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7i6t1
bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUy
l8p+AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57z
ffZz4NLuWVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKg
peT/5HkWxPIR7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8f
DsIm9wB5EpAC0k4wrk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6H
ql9VeAnsXfXFMSvgl1XeTUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRx
xqvRVSHvSb2++h0o7/gauVqD4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFP
OwQljsTPihwCruM+QVkKnin5y3NaQpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXP
dPdV53JwpnhSc7eB97hnuccL5u2mU6ZQYLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9Y
jXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGl
KZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJHKa1AT1I3+G+DVo3njN0gp4k6NJAMmujt
qqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZkgRwupqgXwZFm+UQ8A3quPlhPBONG
eY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD1KUyB8qvB0+2ppv6QXR6fKmY
lhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKlSwuP9+nTp0+fPhAWFhYW
Fvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQflI1+Zn+kFik2pan
nwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6YXQd4EPFNQjXQ
r4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814Ex5l7qy/P
AO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBqTr3B
3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/nt
nbnu+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nah
H4N3rK+JZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhN
m01lgTlK3YzycL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU
8Lv8FfQXIWNM7j3np+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/I
SVMsmMrJS9Qs8Lf11xN3gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0iv
mPYaF0NeD+cB7yhwnDJvMayGhPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfI
fcIEp2vcbn5L//sGduPGjRs3blyYQBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzL
L3D16u3b2dl/Xbxy5UqUCA+Ht97q379+fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xP
RITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3LzMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2i
KP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B
+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDvsEWGjwNNU+3C26D3Er6jDQjzuCjE
gFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5/MoV6DFWyroTDilbKuj3P4KE
6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh3YRjvAVdarWMu9wRbg9e
1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L7QgI7cQD7ALhF8Mc
0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEdeU8gemnEv5Qdg
vvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUBJV3MMMeD
O8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQmZtR
/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0E
Wm9K0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8
GkpWKuYsq0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRr
f90Hw6Ps3bt37969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2
QWZmXl4gAGXLli4dFQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRN
EODpp4sVi4j4tT+P83n/2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs8
3t6A/n8mq+7f93h8vsK4bdvGxEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQ
iml3hVRQV8nbmQDCE2JrfSxIcYQYNoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgY
THpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A76qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7
Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmn
IHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w24dObIH80dn709tByJ3IiJgtYGxoMfvr
QsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0V1yoXQBDSeNdxxG4fytvkh4Lvi6u
b30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzIc7l/0i3gK6029JlBLikvFdLB
W0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9yS3vAfCleBZkpYJ6mhm6
FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDqpU3wdwVHTfsFy0nw
NgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGOwbve7wJhgfyy
tTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+QVoVfg9zN
/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1O9jQ
fkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4u
LAwOHbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c
/nTinPzGdePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdB
v6xf8DUBsZQYJX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdA
C8EhW4GvhK8CZUGt4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSul
z4O98InjrZufLIPbpjRD4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5
NnQrpN+Pyi12BLyH0rsmxYL3nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q
2s34klgazHuksEAUXG+b9FLOafB10vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qw
twd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZuAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJ
eALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4
jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoPIKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXP
dTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCNUXcI3UDtpx8Tb4G8XtIDdcDU39xQ
9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHWWGxF8RGgFxU+sgTAfljsYTwD
Jd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAFPPPXfTj8IwW1y0uWLFmy
ZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L9dtSO7s9LCwurjBO
QdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1HTIyFOUfnd+1
a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE6JDXHuRv
BUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpIDoEUK
L4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DM
Gahe/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dp
amlw93a38r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD
3mzPGFdpkB4YLcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH
+jVEVQqpEdISzCfFCOUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+
bcpsfxjkf5P7TH4iJB9JWZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/
cn9peHAs81amFQyfS5H+3WB/wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggL
QSrNp7oMxhjjbnk82CvYo02twFbevNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubs
EpnXQNmlfOf5EaK/jnreuhzi9xWvn3ATxG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDr
sWNRcPTna19d6grp+/P2pXUGZ72srintwD/KMyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vu
u7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrHKscqxx9/3wq2V0ddHXV11N/d+0JTMqdk
TsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Zem3tt/u5n95/77yfo/6aqiqKqoKqq
qmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z+f3g9wcCilK4PXjwo4/eeqtw
+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j24K4j9ufnnGW65axxswA
c0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE8bDQ07ACpN32mJhl
oL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/SzoGawVe4H4o6hZ
DoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4//EPXU8N
hLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbzlfxv
lL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U
+prFcg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBu
XzVC6pm0gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175
/OF50XA+5dZ7rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXz
YhBWCvNNJ0DZL16WloG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9
vU1rwNDJ3N34BBSZFr4+bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98
pQbsTzze7szzkN6ITYEfQVtgnB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmC
mrtGjRo1atSosNb5cYlsGdkysiW8/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12
+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu
3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3Lti7bukB/+tP/736SQf/xFKUgkS1I2f4906aN
GNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUV
BQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3ZNlicTh+v/+o6/+ogriP259OnLOs
9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4RIoB7XOttdYPpNZFR5ZbAuIh
62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt/SPBAPo1Suo24IFu1L8H
vRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJHzTth7dklWVvjoHTH
SmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D5EVy8pVP4EGC
fVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfaaTC0loeJ
30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+2T0S
/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F
7kU2i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpc
uvMx2OOZpnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V
4Pb41FYPhkG5F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2
vg+OvnEq43R1SLmsV9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHi
xIkTJxaeHz9+/Pjx46FEiRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUN
GzZs2LABMjIyMjIyICoqKioqCjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn
5u6su7Puzjo4fvz48ePHC8MXPC4uLi4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQo
VZWqSlWYkTsjd0YubC66uejmolCmTJkyZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0Wdpk
aZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4
i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFrxq4Zf/z9ubHmxpoba2B66emlp5eG8+fP
nz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe8LThacPTHl3b/7DNaZvTNqdB+U/K
f1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiSviV9Szo4nU6n0wk1F9RcUHMB
TJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5oeeHnoc2MW1i2sQ8vnH1
qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z+32+gpng385IV6ky
ePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv1i3Iy7Nao6LA
aHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvtzYgPx33c
/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsCaMNy
W6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4
flL7luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5Ehb
lTw7RI61fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUz
JhVi46JioidBpDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5
H4S+YCirTAebTfrcuxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjt
eBUNwk6b+pcKAWsTw21Lf+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc
3Ku9SfnNoHRqzPHi88H2vpwWvh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fg
bZV/PmAHxyaLKo4BY2v9Y6UEZFRJeeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHu
obzz7uJQ8UTF80USoGTXMkLJb8F0yNQnVAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/
8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyfO++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJ
EyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6ggTmUV/1bym6peiWorD80vJLyy8VfsVe
bm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPUD6Hr1K5Tu06FnF05u3J2wcw9M/fM
3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oePjpO7O3d37m7IL5dfLr/cv9+P
5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlhzwx7Zti/3s7U7VO3T90O
JwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8pflP8Jni35bst3235
z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/vjJ8ZfjKAN84
vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7TuHpc7+v/
Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1K9z2
6VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QI
qUAaJr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqI
AN1NSQRAQgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID
6U2mQ8rqrBrpD0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4
cfXutrvWws6O+7PObgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ
9lsOOHqCb2vWK2nnwD/cednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn
5mG3COlfZg9xfQkPWmdsy/kGzCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1
LFjPmd4wxoM/RnmdhuAdpt7KTYVcMbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdzt
AiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJIH5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODI
jtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLnGTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGT
bWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuFzYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6
hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0CtZxhpOAN003xCd2Ct0FyoA9Jz4alF
40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbDtc4F7RS0WxDnX22/IIFZu3bt
2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03dt3Y38zgPnz9n1WkQ5EO
RToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJvht8Mv/nX9+Phkpqh
5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9G+VJBc+7wMxZ
M2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n8bZO2Tpl
629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW5Bos
PrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpU
q/b79gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6
tlYehHhu6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0e
Jm8GVoi9dS8In+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKm
hSC1NW3Q1oHwjCzKrUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgoc
RqFRycYQ5S3hVn6ECE/EiLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCk
R5ioNof1T2iVyYMTNkPd0oNB25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e
2jZwp+SNTs+BQKQvJL8j2GuY20ivQWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX
0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNB
nyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtO
CdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVfBHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3ua
BsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH+VNQ5G7Rj0sdgbDXw0fGLwV/28BU
qTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR7jmyR6QOAm2GMTJ0GDBffVl4
E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxasXHjxo0bNxbOCP/R9ZgL
apsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQTgonhd98Na4N0AZo
A37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAEJzgBdKMb3f74
6/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E/6PvzweJ
HyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16QmNWHz
zM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBb
t1q1ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/Y
GWfzcVcDuTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNA
HCItQgHKaudZCPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGm
HiRt9E0yFoUrSzLH6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWE
T8WODAblTTXTuwwC9QNLvSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2Wd
cZDvIyhpid4dEQPlo8rVDzkF1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3Ms
eRJwRavJNAg9Ffpz5BiIHZfoK5ELifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30N
qfvTOuZch3M7L5dL+xByt3pD/CvA1tfeOiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUU
y486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSAMgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4
eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEHQBVxWatD1IionxzfwJPnypVNOA+h4baP
QgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/iCyjbo3hGORkqHKpYv1YLsCeFfJf4
M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvnT7x46hSkHsrqd/MoqBHmapZU
0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtNlb2Pb6AWJLDFixcv/tsP
koL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDCgQowadKkSb+txWvR
vEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyXZr80+yVYKCwU
FgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYRthG2whrn
GsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPtwvYf
/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86
vnfvtWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3
+fm/rtf86FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG
6ufg/NwbuZn9ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08
tSkLzledeTk3YO2sdec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf
4CVqC59D4Cn/Lf08iH6pHTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5
Kr5v3wglXzctPDsHskqHp+aMBvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7N
E6/a34Z7FczNS9wD7Xbe7rQx4Oua2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAso
Xf0tIG1nTrQwAFzFPBfVXHDN0p837AYxRi6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD
5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwnos4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2
EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKlY2IrBCB0onQg/mWwbQibhQ+Uyq4zTglS
RiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+okHIfLCPdxjCVoH5A/tsSyXw5ftK
CXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQvu72gOsmyGueq90pAx6MhvBP
QR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTxLeAZ2ujV/88g6fT4BmxB
7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gNozaMglEZozJGZUD0
neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej70bfhTTSSHsM
/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1AfaA+UIcH
ox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWIeqTw
ZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/
HX/hzY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2
h1Ue3n/U4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv
/uST/2iCpyDu4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFf
jPsFjw9sxvB5EYtBvaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75K
fQWE3oYnDeXhZon7SRdWQPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5
GSo8iN9gSAJrd2tRDoJaQW0tPgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36s
BUBviiAkgHhQF5V3wF/TWTGvMxiTDe3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp
6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXR
lqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMvg7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4
BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz
78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfEKEsVuB2ecfv+cTDUk3da+kDUujA1
thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8sr7Tehpjc+E02BSJaRRaPygTD
EPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW0n4y7AJnVEpOSjfwrcwe
dC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDoE+gZaAeBQ8pq31lQ
ZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F4cOHDx8+/K9P
nIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OVKs8+O2MG
VK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0Dk6lY
sfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GO
HDly5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH
546Dtj1gXGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c
97jmkLnAXcc9BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5j
GHBSb6VfBHGysEj0g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bI
KND8asdAKOidDTPU1aAsslRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbU
mOM9Bm+crfnuhW/hl+X7Lp36ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTC
d4TdjmgIYWdDy9ltYGkdeceSD3p9fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+
0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9
G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIWMC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/
RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN620z4BAobAKmk4uCbm/uh7EvI3+C4HngXJ
bM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSsu1/10kYIxOvN8uaD9rH+tvAe5Jdw
V9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/RmBEIBL0idp2dTrop9X+gfqg
BgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7wV8U/M9UsOzcnpV7Vu5Z
CQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6j9Y5/lf5/f+4Ztjn
c7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3az+xst1tRIDTU
YpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTCuI/bn06c
lamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcMy83d
DG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArC
FLGD2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx0
3IyrCYbz9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG
78Kz5Sr0e7oflJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5
W80TIfRLR35UNIQkhawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QX
y4CS6NX0LSB/Uiq/WBfI65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9Fmw
Y3gmYSqkzTS2TX4ZQvbYD9kmQ9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1l
s/01CPi1ndJT4C8aMBEDOTnpC7zPQeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfk
Nr59Mn0TuDpmpST1BeW8sij9I7B1t3+pfQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2g
VNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8atBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLp
h5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9AstYxjKAoQxl6J9tNSgo6HF44onSpSMi
4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHiERFw9uydO5mZIIqhoSEhEBY2ZMgX
X/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/+tPcfj8kJPxaQBEWZrFIEmRl
iaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9HVSE5OTfX7y+M+7j96VKN
B40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/TeHkdCIG+O/pVcDYpc
bVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9IEGNXFcpF852
veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4Wd+mrwJ9
mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqEW0zO
Su9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQ
L3tm590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkz
gL+M+pHiBf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21
IIDJbXrPuA+0zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBM
YHsgA9QG0mLhTZBijMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmX
u0FufprHPxPUE2wJ/AJynNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+
HhBoIpwGPUH4WVwFvC9uk74AXdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+Q
lZWT43RC375vv/3113Dx4rVraY/jJotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnP
PTd27KJFcPr0tWv/aJ3ox6V69bJl4+Phxx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t1
5vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9b
bn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgThJCRMNr5cdBBkD3FXzbPDqYyT2qFZYCln
NIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQejhO/vdwN3hLQhcAu2n9hz8btL4Ovq
p8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl8oE/AeSFNDCfA3edPF/WQLi6
9lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2ARXzN4AF9pYjWGJgibBVD
QIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8ufk6iJsymt8E5Ana
PPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuyZmRdhhxnVn25
E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ/QQAmaZa
MgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgoqVwC
9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+Uv
VoR7i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0
q/p9zQDaSf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp99
9o9v4vt/zZ9OnC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AU
TB/HRIZUB8MKZsibIfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZ
Mze+TBNBPBvyWuJC0BdnrksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294H
AmsCy31TQN5hirA8A+pRbaM3GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itF
xK0G+xVXpKUD3EjdundNHNjnlUmr3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8
YJXQm2zQF+kX0UFIYgzHQaylRwulwdBYT1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtA
jrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRpzoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73n
JIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi6LvFfvQD/RVhseACoTFLhATQv+BHcS3o
U4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTacMBwG+XRIo7A7YJlhmWH7CcwO4zrz
YYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT+mx2Q+N3Grq7TwBnEWegyTsQ
0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPHhWHwnXvFnU13wf9ufs4F
DyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1HjtHGiDlZP6pwCUp8nf
PcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+Fffibt4CuXvU
K+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrWM2YK6B3l
m4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymAb6zr
mfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/O
A54QhodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDg
PereCUJe7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7M
eM3VGzI/dZcMTIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6zn
AzJBjBGHiU+BGGV43/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGq
NZAO2oyMxik1oGnxZzuXbgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDb
YogaI1e05IM+jmrmJZBYrOj+5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0Q
Pzcso9grkHTYvUN/EXZe2PbJfhckz8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgR
hiflX5fPCc45BwUFBQUF/Q/xp2ucg4KCgoKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0Ew
cQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAfEEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU
9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDAj4oAAAAASUVORK5CYII=
--------------050204080406070300090103--

--------------040304010605040607060607--

From jricher@mitre.org  Thu Jun 13 07:56:13 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F26A21F962D for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7AzOK3XMvrh for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 07:56:13 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4191521F91A5 for <jose@ietf.org>; Thu, 13 Jun 2013 07:56:12 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id ADD271F02ED; Thu, 13 Jun 2013 10:56:11 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 878921F0834; Thu, 13 Jun 2013 10:56:11 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 13 Jun 2013 10:56:10 -0400
Message-ID: <51B9DD51.5040000@mitre.org>
Date: Thu, 13 Jun 2013 10:55:13 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: George Fletcher <gffletch@aol.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <51B9DA50.1080807@aol.com>
In-Reply-To: <51B9DA50.1080807@aol.com>
Content-Type: multipart/alternative; boundary="------------070109000907080604020304"
X-Originating-IP: [129.83.31.56]
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 14:56:13 -0000

--------------070109000907080604020304
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

+1 to George's suggestion. We know that what we have today will 
function, and if this WG doesn't finish its job then the reality is that 
everyone doing "legacy" JWS isn't much going to care what the JOSE WG 
says anymore. In other words, there's enough momentum behind the current 
state of JOSE that it would cause a serious fork if we were to change 
things now.

So let's be smart about the fork. Let's push what we have as "JOSE", 
then "JOSE2" can turn it into the multi-encoded-binary-framework that 
fits other use cases. And it'll be JOSE2's job to come up with 
reasonable backwards compatibility or incompatibility rules and 
functions. If we do this, which is what George is saying, then we can 
actually have some control over both compliance to the "current" specs 
and compliance to the "new" as-of-yet-undefined specs, and we stand a 
chance of people outside of this working group actually paying attention 
to what the working group is saying, both with the current and with the new.

And finally, as the proverb says, "don't let the perfect stand in the 
way of the good."

  -- Justin

On 06/13/2013 10:42 AM, George Fletcher wrote:
> I think that in the current situation the issue isn't just breaking 
> deployed code but also the timeliness of completing the spec. If the 
> desire is to change the processing at some point in the future, why 
> not complete this set of specs and then look to add the backward 
> compatibility/migration strategy to an updated/future version of the 
> specification? That's effectively what this would be anyway, and 
> allowing other specifications and working code to be compliant with 
> the current specification is very valuable and doesn't preclude 
> revising the mechanism in the future.
>
> Thanks,
> George
>
> On 6/13/13 10:35 AM, Richard Barnes wrote:
>> This would have been a nice discussion to have had 18 months ago, 
>> when we were getting started.
>>
>> I don't think it's compatible with the IETF ethos to say "Changes to 
>> this document MUST NOT break existing code."  Otherwise, we're not 
>> doing engineering here, we're cleaning up documentation and 
>> rubber-stamping.
>>
>> What would be acceptable is to say "Changes must break cleanly with 
>> existing code".  That is, it should be possible for a JWT 
>> implementation to, say, process both "legacy" JWS syntax and whatever 
>> comes out of this group.  That way, we could come to consensus on the 
>> best solution, incorporating lessons learned from earlier work 
>> without being hindered by them.
>>
>> Would participants here consider it a acceptable for the output of 
>> this working group to be incompatible with existing JWT 
>> implementations, as long as it had the property that JW* objects in 
>> the new format could be clearly distinguished from "legacy" JW* 
>> objects, so that implementations could adapt their processing?
>>
>> --Richard
>>
>>
>>
>>
>> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com 
>> <mailto:gffletch@aol.com>> wrote:
>>
>>     +1
>>
>>     Breaking deployed code as raised by Brian, Naveen and others is a
>>     critical consideration.
>>
>>     Thanks,
>>     George
>>
>>     On 6/13/13 10:19 AM, Mike Jones wrote:
>>>
>>>     Jim and Karen, could you please do as Richard suggests and close
>>>     this issue as "won't fix".
>>>
>>>     Thank you,
>>>
>>>     -- Mike
>>>
>>>     *From:*Richard Barnes [mailto:rlb@ipv.sx]
>>>     *Sent:* Wednesday, June 12, 2013 1:57 PM
>>>     *To:* jose-chairs@tools.ietf.org
>>>     <mailto:jose-chairs@tools.ietf.org>; Mike Jones
>>>     *Subject:* Fwd: [jose] #23: Make crypto independent of binary
>>>     encoding (base64)
>>>
>>>     In other words: Chairs, feel free to close/wontfix :)
>>>
>>>     ---------- Forwarded message ----------
>>>     From: *Richard Barnes* <rlb@ipv.sx <mailto:rlb@ipv.sx>>
>>>     Date: Wed, Jun 12, 2013 at 4:55 PM
>>>     Subject: Re: [jose] #23: Make crypto independent of binary
>>>     encoding (base64)
>>>     To: "Matt Miller (mamille2)" <mamille2@cisco.com
>>>     <mailto:mamille2@cisco.com>>
>>>     Cc: jose issue tracker <trac+jose@trac.tools.ietf.org
>>>     <mailto:trac%2Bjose@trac.tools.ietf.org>>,
>>>     "<draft-ietf-jose-json-web-encryption@tools.ietf.org
>>>     <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>"
>>>     <draft-ietf-jose-json-web-encryption@tools.ietf.org
>>>     <mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>,
>>>     "<michael.jones@microsoft.com
>>>     <mailto:michael.jones@microsoft.com>>"
>>>     <michael.jones@microsoft.com
>>>     <mailto:michael.jones@microsoft.com>>, "<jose@ietf.org
>>>     <mailto:jose@ietf.org>>" <jose@ietf.org <mailto:jose@ietf.org>>
>>>
>>>     To be clear, I structured my message in two parts for a reason,
>>>     to separate the analysis from the opinion.  I acknowledge that I
>>>     am but one voice here, and I'm increasingly hearing how alone I
>>>     am :)
>>>
>>>     On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx
>>>     <mailto:rlb@ipv.sx>> wrote:
>>>
>>>         <impartial-analysis>
>>>
>>>         So just to be clear on the trade-off the WG has to make:
>>>
>>>         On the one hand: Breaking every existing JWT implementation
>>>         in the world
>>>
>>>         On the other hand: Eternally binding ourselves to base64
>>>         encoding, even if binary-safe encodings become available
>>>         (CBOR, MsgPack, etc.)
>>>
>>>         </impartial-analysis >
>>>
>>>         <personal-opinion>
>>>
>>>         I have some sympathy with JWT implementors.  It sucks to
>>>         have to refactor code.  But I think we're literally talking
>>>         about something like a 5-line patch.  And early JWT
>>>         implementors knew or should have known (to use a DC phrase)
>>>         that they were dealing with a draft spec.  As the W3C
>>>         editor's draft template says, in big bold red print,
>>>         "Implementors who are not taking part in the discussions are
>>>         likely to find the specification changing out from under
>>>         them in incompatible ways."
>>>
>>>         As PHB pointed out in the other thread, it would be nice to
>>>         use JWS and JWE in place of CMS one day, without the base64
>>>         hit.  We should incur the implementation pain now, and get
>>>         the design right for the long run.  Base64 is a hack around
>>>         JSON; we should build the system so that when we no longer
>>>         need that hack, it can go away.
>>>
>>>         </personal-opinion>
>>>
>>>         --Richard
>>>
>>>         On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2)
>>>         <mamille2@cisco.com <mailto:mamille2@cisco.com>> wrote:
>>>
>>>         I did at first find it curious why the cryptographic
>>>         operations were over the base64url-enccoded values, but I
>>>         was also very focused on JWE, where I think the field
>>>         separation problem is less of an issue (at least now).  For
>>>         JWS, this would certainly cause problems without some manner
>>>         of unambiguous field parameterization.
>>>
>>>         I will note that unescaped NULL is not valid in JSON, so it
>>>         could be used as a separator between the encoded header and
>>>         the payload.  I do find it interesting if JOSE could more
>>>         easily and efficiently support other encodings.  However, I
>>>         think that while this is an interesting thought experiment,
>>>         it seems we're too far down the path to seriously consider
>>>         it unless the current state were shown to be horribly broken.
>>>
>>>
>>>         - m&m
>>>
>>>         Matt Miller < mamille2@cisco.com <mailto:mamille2@cisco.com> >
>>>         Cisco Systems, Inc.
>>>
>>>
>>>         On Jun 11, 2013, at 6:01 PM, jose issue tracker
>>>         <trac+jose@trac.tools.ietf.org
>>>         <mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:
>>>
>>>         > #23: Make crypto independent of binary encoding (base64)
>>>         >
>>>         >
>>>         > Comment (by michael.jones@microsoft.com
>>>         <mailto:michael.jones@microsoft.com>):
>>>         >
>>>         > For both serializations, you already need the base64url
>>>         encoded versions
>>>         > of the JWS Header and the JWS Payload to preserve them in
>>>         transmission, so
>>>         > computing them isn't an extra burden.  In the JWS Compact
>>>         Serialization,
>>>         > you already need the concatenation of the Encoded JWS
>>>         Header, a period
>>>         > character, and the Encoded JWS Payload, so computing that
>>>         concatenation
>>>         > isn't an extra burden.  Given you already have that
>>>         quantity, computing
>>>         > the signature over it is the easiest thing for developers
>>>         to do, and it's
>>>         > been shown to work well in practice.  There's no
>>>         compelling reason to make
>>>         > this change.
>>>         >
>>>         > Even for the JSON Serialization, the only "extra" step
>>>         that's required to
>>>         > compute the signature is the concatenation with the period
>>>         character - to
>>>         > prevent shifting of data from one field to the other, as
>>>         described by Jim
>>>         > Schaad in the e-mail thread.  So this step isn't actually
>>>         "extra" at all -
>>>         > it's necessary.  It's also highly advantageous to use
>>>         exactly the same
>>>         > computation for both serializations, which is currently
>>>         the case.
>>>         >
>>>         > Since there is no compelling reason to make this change,
>>>         and since making
>>>         > it could enable the "shifting" problem identified by Jim,
>>>         it should not be
>>>         > made.
>>>         >
>>>         > --
>>>         >
>>>         -------------------------+-------------------------------------------------
>>>         > Reporter: rlb@ipv.sx <mailto:rlb@ipv.sx>   |       Owner:
>>>          draft-ietf-jose-json-web-
>>>         >     Type:  defect | encryption@tools.ietf.org
>>>         <mailto:encryption@tools.ietf.org>
>>>         > Priority:  major  |  Status:  new
>>>         > Component:  json-web-  | Milestone:
>>>         >  encryption           |   Version:
>>>         > Severity:  -  |  Resolution:
>>>         > Keywords: |
>>>         >
>>>         -------------------------+-------------------------------------------------
>>>         >
>>>         > Ticket URL:
>>>         <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>>>         > jose <http://tools.ietf.org/jose/>
>>>         >
>>>
>>>         > _______________________________________________
>>>         > jose mailing list
>>>         > jose@ietf.org <mailto:jose@ietf.org>
>>>         > https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>>
>>>     _______________________________________________
>>>     jose mailing list
>>>     jose@ietf.org  <mailto:jose@ietf.org>
>>>     https://www.ietf.org/mailman/listinfo/jose
>>
>>     -- 
>>     George Fletcher <http://connect.me/gffletch>
>>
>>
>
> -- 
> George Fletcher <http://connect.me/gffletch>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------070109000907080604020304
Content-Type: multipart/related;
	boundary="------------030202080101030400010806"

--------------030202080101030400010806
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    +1 to George's suggestion. We know that what we have today will
    function, and if this WG doesn't finish its job then the reality is
    that everyone doing "legacy" JWS isn't much going to care what the
    JOSE WG says anymore. In other words, there's enough momentum behind
    the current state of JOSE that it would cause a serious fork if we
    were to change things now. <br>
    <br>
    So let's be smart about the fork. Let's push what we have as "JOSE",
    then "JOSE2" can turn it into the multi-encoded-binary-framework
    that fits other use cases. And it'll be JOSE2's job to come up with
    reasonable backwards compatibility or incompatibility rules and
    functions. If we do this, which is what George is saying, then we
    can actually have some control over both compliance to the "current"
    specs and compliance to the "new" as-of-yet-undefined specs, and we
    stand a chance of people outside of this working group actually
    paying attention to what the working group is saying, both with the
    current and with the new.<br>
    <br>
    And finally, as the proverb says, "don't let the perfect stand in
    the way of the good."<br>
    <br>
    &nbsp;-- Justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/13/2013 10:42 AM, George Fletcher
      wrote:<br>
    </div>
    <blockquote cite="mid:51B9DA50.1080807@aol.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <font face="Helvetica, Arial, sans-serif">I think that in the
        current situation the issue isn't just breaking deployed code
        but also the timeliness of completing the spec. If the desire is
        to change the processing at some point in the future, why not
        complete this set of specs and then look to add the backward
        compatibility/migration strategy to an updated/future version of
        the specification? That's effectively what this would be anyway,
        and allowing other specifications and working code to be
        compliant with the current specification is very valuable and
        doesn't preclude revising the mechanism in the future.<br>
        <br>
        Thanks,<br>
        George</font><br>
      <br>
      <div class="moz-cite-prefix">On 6/13/13 10:35 AM, Richard Barnes
        wrote:<br>
      </div>
      <blockquote
cite="mid:CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com"
        type="cite">
        <div dir="ltr">This would have been a nice discussion to have
          had 18 months ago, when we were getting started.
          <div><br>
          </div>
          <div>I don't think it's compatible with the IETF ethos to say
            "Changes to this document MUST NOT break existing code."
            &nbsp;Otherwise, we're not doing engineering here, we're cleaning
            up documentation and rubber-stamping.</div>
          <div><br>
          </div>
          <div>What would be acceptable is to say "Changes must break
            cleanly with existing code". &nbsp;That is, it should be possible
            for a JWT implementation to, say, process both "legacy" JWS
            syntax and whatever comes out of this group. &nbsp;That way, we
            could come to consensus on the best solution, incorporating
            lessons learned from earlier work without being hindered by
            them.</div>
          <div><br>
          </div>
          <div>Would participants here consider it a acceptable for the
            output of this working group to be incompatible with
            existing JWT implementations, as long as it had the property
            that JW* objects in the new format could be clearly
            distinguished from "legacy" JW* objects, so that
            implementations could adapt their processing?</div>
          <div><br>
          </div>
          <div>--Richard</div>
          <div><br>
          </div>
          <div><br>
            <div class="gmail_extra"><br>
              <br>
              <div class="gmail_quote">On Thu, Jun 13, 2013 at 10:24 AM,
                George Fletcher <span dir="ltr">&lt;<a
                    moz-do-not-send="true"
                    href="mailto:gffletch@aol.com" target="_blank">gffletch@aol.com</a>&gt;</span>
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div bgcolor="#FFFFFF" text="#000000"> <font
                      face="Helvetica, Arial, sans-serif">+1<br>
                      <br>
                      Breaking deployed code as raised by Brian, Naveen
                      and others is a critical consideration.<br>
                      <br>
                      Thanks,<br>
                      George<br>
                      <br>
                    </font>
                    <div>
                      <div class="h5">
                        <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
                        </div>
                        <blockquote type="cite">
                          <div>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim


                                and Karen, could you please do as
                                Richard suggests and close this issue as
                                &#8220;won&#8217;t fix&#8221;.</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;


                                Thank you,</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;


                                -- Mike</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                            <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                                Richard Barnes [<a
                                  moz-do-not-send="true"
                                  href="mailto:rlb@ipv.sx"
                                  target="_blank">mailto:rlb@ipv.sx</a>]
                                <br>
                                <b>Sent:</b> Wednesday, June 12, 2013
                                1:57 PM<br>
                                <b>To:</b> <a moz-do-not-send="true"
                                  href="mailto:jose-chairs@tools.ietf.org"
                                  target="_blank">jose-chairs@tools.ietf.org</a>;
                                Mike Jones<br>
                                <b>Subject:</b> Fwd: [jose] #23: Make
                                crypto independent of binary encoding
                                (base64)</span></p>
                            <p class="MsoNormal">&nbsp;</p>
                            <div>
                              <p class="MsoNormal">In other words:
                                Chairs, feel free to close/wontfix :)</p>
                              <div>
                                <p class="MsoNormal"
                                  style="margin-bottom:12.0pt">&nbsp;</p>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-bottom:12.0pt">----------


                                    Forwarded message ----------<br>
                                    From: <b>Richard Barnes</b> &lt;<a
                                      moz-do-not-send="true"
                                      href="mailto:rlb@ipv.sx"
                                      target="_blank">rlb@ipv.sx</a>&gt;<br>
                                    Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                                    Subject: Re: [jose] #23: Make crypto
                                    independent of binary encoding
                                    (base64)<br>
                                    To: "Matt Miller (mamille2)" &lt;<a
                                      moz-do-not-send="true"
                                      href="mailto:mamille2@cisco.com"
                                      target="_blank">mamille2@cisco.com</a>&gt;<br>
                                    Cc: jose issue tracker &lt;<a
                                      moz-do-not-send="true"
                                      href="mailto:trac%2Bjose@trac.tools.ietf.org"
                                      target="_blank">trac+jose@trac.tools.ietf.org</a>&gt;,


                                    "&lt;<a moz-do-not-send="true"
                                      href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org"
                                      target="_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;"


                                    &lt;<a moz-do-not-send="true"
                                      href="mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org"
                                      target="_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;,



                                    "&lt;<a moz-do-not-send="true"
                                      href="mailto:michael.jones@microsoft.com"
                                      target="_blank">michael.jones@microsoft.com</a>&gt;"


                                    &lt;<a moz-do-not-send="true"
                                      href="mailto:michael.jones@microsoft.com"
                                      target="_blank">michael.jones@microsoft.com</a>&gt;,


                                    "&lt;<a moz-do-not-send="true"
                                      href="mailto:jose@ietf.org"
                                      target="_blank">jose@ietf.org</a>&gt;"


                                    &lt;<a moz-do-not-send="true"
                                      href="mailto:jose@ietf.org"
                                      target="_blank">jose@ietf.org</a>&gt;<br>
                                    <br>
                                  </p>
                                  <div>
                                    <p class="MsoNormal">To be clear, I
                                      structured my message in two parts
                                      for a reason, to separate the
                                      analysis from the opinion. &nbsp;I
                                      acknowledge that I am but one
                                      voice here, and I'm increasingly
                                      hearing how alone I am :)</p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal"
                                      style="margin-bottom:12.0pt">&nbsp;</p>
                                    <div>
                                      <div>
                                        <p class="MsoNormal">On Wed, Jun
                                          12, 2013 at 4:23 PM, Richard
                                          Barnes &lt;<a
                                            moz-do-not-send="true"
                                            href="mailto:rlb@ipv.sx"
                                            target="_blank">rlb@ipv.sx</a>&gt;


                                          wrote:</p>
                                      </div>
                                      <div>
                                        <div>
                                          <blockquote
                                            style="border:none;border-left:solid
                                            #cccccc 1.0pt;padding:0in
                                            0in 0in
                                            6.0pt;margin-left:4.8pt;margin-right:0in">
                                            <div>
                                              <div>
                                                <p class="MsoNormal">&lt;impartial-analysis&gt;</p>
                                              </div>
                                              <p class="MsoNormal">So
                                                just to be clear on the
                                                trade-off the WG has to
                                                make:</p>
                                              <div>
                                                <p class="MsoNormal">&nbsp;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">On
                                                  the one hand: Breaking
                                                  every existing JWT
                                                  implementation in the
                                                  world</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">On
                                                  the other hand:
                                                  Eternally binding
                                                  ourselves to base64
                                                  encoding, even if
                                                  binary-safe encodings
                                                  become available
                                                  (CBOR, MsgPack, etc.)</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">&lt;/impartial-analysis&nbsp;&gt;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">&nbsp;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">&lt;personal-opinion&gt;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">I
                                                  have some sympathy
                                                  with JWT implementors.
                                                  &nbsp;It sucks to have to
                                                  refactor code. &nbsp;But I
                                                  think we're literally
                                                  talking about
                                                  something like a
                                                  5-line patch. &nbsp;And
                                                  early JWT implementors
                                                  knew or should have
                                                  known (to use a DC
                                                  phrase) that they were
                                                  dealing with a draft
                                                  spec. &nbsp;As the W3C
                                                  editor's draft
                                                  template says, in big
                                                  bold red print,
                                                  "Implementors who are
                                                  not taking part in the
                                                  discussions are likely
                                                  to find the
                                                  specification changing
                                                  out from under them in
                                                  incompatible ways."</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">&nbsp;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">As
                                                  PHB pointed out in the
                                                  other thread, it would
                                                  be nice to use JWS and
                                                  JWE in place of CMS
                                                  one day, without the
                                                  base64 hit. &nbsp;We should
                                                  incur the
                                                  implementation pain
                                                  now, and get the
                                                  design right for the
                                                  long run. &nbsp;Base64 is a
                                                  hack around JSON; we
                                                  should build the
                                                  system so that when we
                                                  no longer need that
                                                  hack, it can go away.</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">&lt;/personal-opinion&gt;</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"><span
style="color:#888888">&nbsp;</span></p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"><span
style="color:#888888">--Richard</span></p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"><span
style="color:#888888">&nbsp;</span></p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"><span
style="color:#888888">&nbsp;</span></p>
                                              </div>
                                            </div>
                                            <div>
                                              <div>
                                                <div>
                                                  <p class="MsoNormal"
                                                    style="margin-bottom:12.0pt">&nbsp;</p>
                                                  <div>
                                                    <p class="MsoNormal">On

                                                      Wed, Jun 12, 2013
                                                      at 10:27 AM, Matt
                                                      Miller (mamille2)
                                                      &lt;<a
                                                        moz-do-not-send="true"
href="mailto:mamille2@cisco.com" target="_blank">mamille2@cisco.com</a>&gt;


                                                      wrote:</p>
                                                    <p class="MsoNormal">I
                                                      did at first find
                                                      it curious why the
                                                      cryptographic
                                                      operations were
                                                      over the
                                                      base64url-enccoded
                                                      values, but I was
                                                      also very focused
                                                      on JWE, where I
                                                      think the field
                                                      separation problem
                                                      is less of an
                                                      issue (at least
                                                      now). &nbsp;For JWS,
                                                      this would
                                                      certainly cause
                                                      problems without
                                                      some manner of
                                                      unambiguous field
                                                      parameterization.<br>
                                                      <br>
                                                      I will note that
                                                      unescaped NULL is
                                                      not valid in JSON,
                                                      so it could be
                                                      used as a
                                                      separator between
                                                      the encoded header
                                                      and the payload.
                                                      &nbsp;I do find it
                                                      interesting if
                                                      JOSE could more
                                                      easily and
                                                      efficiently
                                                      support other
                                                      encodings.
                                                      &nbsp;However, I think
                                                      that while this is
                                                      an interesting
                                                      thought
                                                      experiment, it
                                                      seems we're too
                                                      far down the path
                                                      to seriously
                                                      consider it unless
                                                      the current state
                                                      were shown to be
                                                      horribly broken.<br>
                                                      <br>
                                                      <br>
                                                      - m&amp;m<br>
                                                      <br>
                                                      Matt Miller &lt; <a
moz-do-not-send="true" href="mailto:mamille2@cisco.com" target="_blank">mamille2@cisco.com</a>
                                                      &gt;<br>
                                                      Cisco Systems,
                                                      Inc.</p>
                                                    <div>
                                                      <div>
                                                        <p
                                                          class="MsoNormal"><br>
                                                          On Jun 11,
                                                          2013, at 6:01
                                                          PM, jose issue
                                                          tracker &lt;<a
moz-do-not-send="true" href="mailto:trac%2Bjose@trac.tools.ietf.org"
                                                          target="_blank">trac+jose@trac.tools.ietf.org</a>&gt;


                                                          wrote:<br>
                                                          <br>
                                                          &gt; #23: Make
                                                          crypto
                                                          independent of
                                                          binary
                                                          encoding
                                                          (base64)<br>
                                                          &gt;<br>
                                                          &gt;<br>
                                                          &gt; Comment
                                                          (by <a
                                                          moz-do-not-send="true"
href="mailto:michael.jones@microsoft.com" target="_blank">michael.jones@microsoft.com</a>):<br>
                                                          &gt;<br>
                                                          &gt; For both
                                                          serializations,

                                                          you already
                                                          need the
                                                          base64url
                                                          encoded
                                                          versions<br>
                                                          &gt; of the
                                                          JWS Header and
                                                          the JWS
                                                          Payload to
                                                          preserve them
                                                          in
                                                          transmission,
                                                          so<br>
                                                          &gt; computing
                                                          them isn't an
                                                          extra burden.
                                                          &nbsp;In the JWS
                                                          Compact
                                                          Serialization,<br>
                                                          &gt; you
                                                          already need
                                                          the
                                                          concatenation
                                                          of the Encoded
                                                          JWS Header, a
                                                          period<br>
                                                          &gt;
                                                          character, and
                                                          the Encoded
                                                          JWS Payload,
                                                          so computing
                                                          that
                                                          concatenation<br>
                                                          &gt; isn't an
                                                          extra burden.
                                                          &nbsp;Given you
                                                          already have
                                                          that quantity,
                                                          computing<br>
                                                          &gt; the
                                                          signature over
                                                          it is the
                                                          easiest thing
                                                          for developers
                                                          to do, and
                                                          it's<br>
                                                          &gt; been
                                                          shown to work
                                                          well in
                                                          practice.
                                                          &nbsp;There's no
                                                          compelling
                                                          reason to make<br>
                                                          &gt; this
                                                          change.<br>
                                                          &gt;<br>
                                                          &gt; Even for
                                                          the JSON
                                                          Serialization,
                                                          the only
                                                          "extra" step
                                                          that's
                                                          required to<br>
                                                          &gt; compute
                                                          the signature
                                                          is the
                                                          concatenation
                                                          with the
                                                          period
                                                          character - to<br>
                                                          &gt; prevent
                                                          shifting of
                                                          data from one
                                                          field to the
                                                          other, as
                                                          described by
                                                          Jim<br>
                                                          &gt; Schaad in
                                                          the e-mail
                                                          thread. &nbsp;So
                                                          this step
                                                          isn't actually
                                                          "extra" at all
                                                          -<br>
                                                          &gt; it's
                                                          necessary.
                                                          &nbsp;It's also
                                                          highly
                                                          advantageous
                                                          to use exactly
                                                          the same<br>
                                                          &gt;
                                                          computation
                                                          for both
                                                          serializations,
                                                          which is
                                                          currently the
                                                          case.<br>
                                                          &gt;<br>
                                                          &gt; Since
                                                          there is no
                                                          compelling
                                                          reason to make
                                                          this change,
                                                          and since
                                                          making<br>
                                                          &gt; it could
                                                          enable the
                                                          "shifting"
                                                          problem
                                                          identified by
                                                          Jim, it should
                                                          not be<br>
                                                          &gt; made.<br>
                                                          &gt;<br>
                                                          &gt; --<br>
                                                          &gt;
-------------------------+-------------------------------------------------<br>
                                                          &gt; Reporter:
                                                          &nbsp;<a
                                                          moz-do-not-send="true"
href="mailto:rlb@ipv.sx" target="_blank">rlb@ipv.sx</a> &nbsp; | &nbsp; &nbsp; &nbsp; Owner:
&nbsp;draft-ietf-jose-json-web-<br>
                                                          &gt; &nbsp; &nbsp; Type:
                                                          &nbsp;defect &nbsp; &nbsp; &nbsp;
                                                          | &nbsp;<a
                                                          moz-do-not-send="true"
href="mailto:encryption@tools.ietf.org" target="_blank">encryption@tools.ietf.org</a><br>
                                                          &gt; Priority:
                                                          &nbsp;major &nbsp; &nbsp; &nbsp;
                                                          &nbsp;| &nbsp; &nbsp;
                                                          &nbsp;Status: &nbsp;new<br>
                                                          &gt;
                                                          Component:
                                                          &nbsp;json-web- &nbsp;
                                                          &nbsp;| &nbsp;
                                                          Milestone:<br>
                                                          &gt;
                                                          &nbsp;encryption &nbsp;
                                                          &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;
                                                          &nbsp; Version:<br>
                                                          &gt; Severity:
                                                          &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                                                          &nbsp;|
                                                          &nbsp;Resolution:<br>
                                                          &gt; Keywords:
                                                          &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
                                                          |<br>
                                                          &gt;
-------------------------+-------------------------------------------------<br>
                                                          &gt;<br>
                                                          &gt; Ticket
                                                          URL: &lt;<a
                                                          moz-do-not-send="true"
href="http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2"
                                                          target="_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                                          &gt; jose &lt;<a
moz-do-not-send="true" href="http://tools.ietf.org/jose/"
                                                          target="_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                                          &gt;</p>
                                                      </div>
                                                    </div>
                                                    <div>
                                                      <div>
                                                        <p
                                                          class="MsoNormal"
style="margin-bottom:12.0pt">&gt;
_______________________________________________<br>
                                                          &gt; jose
                                                          mailing list<br>
                                                          &gt; <a
                                                          moz-do-not-send="true"
href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a><br>
                                                          &gt; <a
                                                          moz-do-not-send="true"
href="https://www.ietf.org/mailman/listinfo/jose" target="_blank">https://www.ietf.org/mailman/listinfo/jose</a></p>
                                                      </div>
                                                    </div>
                                                  </div>
                                                  <p class="MsoNormal">&nbsp;</p>
                                                </div>
                                              </div>
                                            </div>
                                          </blockquote>
                                        </div>
                                      </div>
                                    </div>
                                    <p class="MsoNormal">&nbsp;</p>
                                  </div>
                                </div>
                                <p class="MsoNormal">&nbsp;</p>
                              </div>
                            </div>
                          </div>
                          <br>
                          <fieldset></fieldset>
                          <br>
                          <pre>_______________________________________________
jose mailing list
<a moz-do-not-send="true" href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/jose" target="_blank">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
                        </blockquote>
                        <br>
                      </div>
                    </div>
                    <span class="HOEnZb"><font color="#888888">
                        <div>-- <br>
                          <a moz-do-not-send="true"
                            href="http://connect.me/gffletch"
                            title="View full card on Connect.Me"
                            target="_blank"><img
                              src="cid:part26.07050304.09090705@mitre.org"
                              alt="George Fletcher" height="113"
                              width="359"></a></div>
                      </font></span></div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </blockquote>
      <br>
      <div class="moz-signature">-- <br>
        <a moz-do-not-send="true" href="http://connect.me/gffletch"
          title="View full card on Connect.Me"><img
            src="cid:part28.09030107.04060900@mitre.org" alt="George
            Fletcher" height="113" width="359"></a></div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030202080101030400010806
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part26.07050304.09090705@mitre.org>

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAA
CXBIWXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAI
JLiEoIGgETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlT
p09Lly5dunTpkhC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLl
y5dB/rMr4ubm5ubm5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc
3Nzc3Nzcfgd34uzm5ubm5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zF
HGHAI0sR61oQpSxdUsuBrcbbpFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL
5KL61yAdzP0l4ytwdrCmZQ0B49ngq9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5
xhJQD0ijlA6g5aoPzQXA2i9znjMWcodll8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteB
faB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHnu0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm
5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGzl2e093YQJp4ZK4D+G+NGeT+oM131tF+h
+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRGmAkCkYsLFwDS//NGKvzbkoT3kJCB
AD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o0AicE+TFUiRou8QMPMH3hee3
xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8I6cn2B8meCh34eGjN6Ve
rAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1YO1qH6dbCKnhSYG5
oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ69MW+HWD9Tu2S
0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skjff0g+X5S
BR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBNv1lc
AOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAY
lnko7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm
+Bj0TqE4h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9
bF5rQRrpqG3vCt5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk
00D+UBkr7oI2QPpSCgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2
qwt9Le26NjkA9faXTy79AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3
YG7o/SZiFChhSkm7DkLe+n1ttYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HB
doFdC68EZ7ajSBEJss5l5/IM7hd6qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2
SiNe1wGvbXI153fwpnrSgWc/ws2y92v8PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJ
mfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNpdxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE
+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK63RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQ
d+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1Ej0GgzhSfuayglYmv/7gaaIn2W84t
IN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqvb/8C1AilmagDhgX6FnoPMGzx
MnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUCwLFVHq31B/NoD7P5ETA2
O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgnrBvSZgIG+Yo+GqxD
cuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPoK3/MPEATqdIi
QEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJDQtfUg0ml
oXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRvLQkp
3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAX
Q8B7LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZP
AFvtzIyo2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yM
oDu4grVrTgMoy8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJf
OZ5ZoMXlTEpXQLuY2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZE
GcZ43wHdA+movjR47/b6RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaB
VxGvyrpeYM+yLs/6HuRrzh2uFPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9
lOZgn5ijt9wGfbJezT4I3PY4G1QWjF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B
91zfDX6/wIOlT+LjW0KJbwptCyoOupk6L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGB
LwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZEkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNC
IWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+G9grKgnuz35x32cROPa4Clpfgff1xGr3
KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0dTXrCT4p9s2GMVA6uqRnoZXwqFh8
6hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISLIDZZ14XPhJK1S0WVXQ5BgUEj
fM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJFWNoq4IDeLh2CzJIZJ42d
QL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B+WN6SPNAVPLqbt4O
0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7gXzJ41LAV6D6
Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0Hoqz6hbwI
DFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNTtARz
uuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0f
XAHUFPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm
5/fdHgE7D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3
cmrwrzUguJ7/a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBu
T9rl+6kw8FSbj3qHwKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y
2BpnVfZ8DSU9ixyt8itU/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXO
MlD/ZOGg5lMhIsn/81oWMP5qKilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/u
v90fnjZ82vBpQ1CXq8vV5VD4q8JfFf4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSp
UqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoU
eP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMo
OVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynMcNSzKvCxstVUFLTLjplZPwNztWDxMcj5
fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOmZRGIgXYvewOQ+htjlQSQVPtRVwgo
v9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g9TblevUCkSLaaS/BVV8NdWWC
eaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZLsc8HtRHzkr2EZC9LXt4
ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8W/UqMvUHKHSq0J7g
MJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwClsu4jMQucu5z5
HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZz1ch9JPQ
/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPgAfh1
N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+Gg
inF9wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe
3jjveb1L79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jU
kKkhU0EZrgxXhv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k
6oXAC0jnBbeAGCxiJVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjC
IFfUVQKpirVnVg64ZJrnGkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQld
QaC7us5lAaWqTHxtsB9xzkr5AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6R
tuuag7JUPisvAGNdQwVjfxClDb2kAWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBc
QxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/q
JoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lKQdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJi
mvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazhoZ0SschLk86w2FobUjm/TMy3gW0ye5TCA
+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4rE8LKwDpxbLnmifA6VZJ+61pkLgk
9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULKQ7mUyAE15oHjpHWXawNkdpJd
zvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX3KOOqVC1TalujUxgf5qd
EOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKELZegyewqnT8YBj7f
2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1jLZgePz1+ejw0
/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yuv7n+5vrg
98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQiynr
I5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIh
s05qVsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/
gi7EEGYqBLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5l
lewH2laX3a4Hu5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcg
bZIypRagLRXn1Yug+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0
VOoPmZWz96fHgfm8uRo+kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1
B1xTciv4SvDgw9i714Ph8IsbLTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9
EbyrMabKEXCdoXJmAmRPdk55egZivk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH
41i7Z+BIaFO8VkZzDxjjPajg4CUQ+CbkB6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS7
9fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjtrYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27N
ezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82fArjt4/fPn47tAxpGdIyBHJO55zOOf23
8eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHnjT5vBAltE9omtP1PKvjvI93vRsI7
dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjIyMi7hf/u78O6D+s+rAtd0ruk
d0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf7e+9tf9/iH+0HeoV9Yp6
5benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunLpi9hwYkFJxacAFsp
Wylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8bo5sFhACUh3s
7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9SFX0HT0Dy
NOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNpi1ff
gJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUc
TAS4ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNie
phdP6gOW12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4Km
eJcr8gu4urLXFQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAE
F/BbaS0AhoaefZI1yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4
WJkj6SFgn0ePgK/BY4+SEXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjd
vMqREr/AS8vrC1lDISX3VTnhC35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgy
kjLn+22FtW0OZGzPD/5+/h29e0LRzOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHM
iX6y7xIwV9et9a//x7uVGCwGi8Fw+6fbP93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25
i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8CRxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eX
lxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8xGhB/wX9F/QHeae8U94JXehCl/+i/uO2
j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5FxCFYgvFFoqF6Xun752+F1jMYhb/
69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNTkU1FNhWB/J3yd8rfCWJ3x+6O
3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZWK6vwovqL6i+qw7bobdHb
oiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn40gFrWcva9/C+/bPn
m5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHciiOuqyRkAcnfp
mVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhSYWmZIQK0
eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GBvZVk
MD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2Rlsh
vQV5pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn
3/3wh+aw8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV
1V3RlYWzwbczr/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZ
ajgMnpP0DfJ1htwplqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3
Xzs4Ue9cyPWjcPjolY/OnYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp
+Tv7Fqi8pPjIlpMhJS1mYY4KF3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+n
vRwVPxkeWVO6PA6G89cf3th1Ci6NiHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsti
cJZzlnOWy3s+KCgoKCjob8svsiyyLLLkfZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcf
fABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10
Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5SOcjnY/kbV//YP2D9X8xIvguAdvivcV7
izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659tx+F5h+cdnge7Ju2atGvS38Zdt27d
unXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg7w6A/o7+jv4OHJl9ZPaR2WCz
2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9+3vnm5ubm9v7neMsAy4U
8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlISVKaXAkYKO4JG4gX
4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8HaTldBcjgHoZ
xeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG/CAbdN2M
ceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAYA1Il
eZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd7
3i97+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsT
s+HmTUi+ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQ
u9QfDLNME9Q4SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFa
fkM9cPRhUvEg8PM27U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1b
qArEesefyO0JZxOelLjhAb5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbT
NHBe0k3RjkFGR/uF9DKQkz+3rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPw
z3nlU6JTolOiIbZgbMHYgn8bL6VNSpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYE
a4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O
7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/aMc/237mM5/5/MPe9yoS/13teDfl4t37905N
Q01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9ZdoA1taANFuhbpWqQrEEAAAXlTSt5Xe5tP
aj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76VuIPJLbcUW0CJoJMeBNFMrmpsA8oiA
+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5EBPXkQKCIGKDNAWkVVXgMPGKJ
OABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEXrBscJvEN2FYafjGPAdev
8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4TswFfT53vwtpEdZ4zN6
gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYUyB6Z/VXKc7Au
8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90hWx9cmZD
YEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn3Z1K
Q2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMm
S+tmNNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJf
Qu5q+9cf1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OK
P+wLHlPNY70PgHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA
2T/Wrd7dyi95vuT5kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdf
fPHFF1/8bXzbBdsF2wWgM53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePd
XOcLXODC327+rQRGW64t15b/J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc8
5C8ulHQ6nU73B/43eTc14z+8W/WlCU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RK
bUAK4GutKMjNzeUDfwSxRy6YcwJYLMqxD9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZG
bQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjxufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHT
u4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hm
gscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpNoATJHZTDQG/nRGd3MAyTo6VZEHjY
cNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2zj4L2ncturwumROmK6RIY1kjn
xQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5x+4JjtOZvXIiILtJgr7w
FSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2DjN1Dgq4B63haIcWlv
pGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCuV+c74HNlTWIt
iBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQZyj2U9Tp
oOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrGRNMM
63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998O
baa1mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdj
n4x9MhZiYmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUAr
WtEKIttFtotsB6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2
oW1C2wQ4dPjQ4UOHga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0
aNGiRYu8Ox/tO7Tv0L5DXrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90
rUAMkUZ41AVli2GxshLEE+GlzgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01
C7QFak/ZBnIT+TNJD9p5MV63FpRp2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWflj
b6WWgeSrSTnpl0Ht43ph/xVyxqccT54MLz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBz
YY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wE
hg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcV
papgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP4y5AbFzCgzefQvZcY520L6FswZIH
O9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP+Nf0PubtB47H1o3SS/AdZNju
mwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/77BeIHhwcGPQIevRo8rJH
Czjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9bFU5/fGJSXG/IXF9x
pysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0GXWlDmLYd/Lr5
l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok20RwNBCz
FRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvWrFmz
ZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7b
e2/nfTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDL
gJf/xZco31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAg
cUHigsS8Oxp7w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEm
PEUMALu1BGCbNIwaQBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De
7uXeW54gjwvwL9gP9JmmZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQO
fXUScEU9D/0e4vbGJSZ1BfsP9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9Lkem
gGd749c+JpBidVk0A+c17XTuGbB6W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I
3AykW/IE3XqQjlJIag5Sc3FKqgy63uom9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEi
zNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ
4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQamY/VOQSOfKjerzIXXZXMbPt4Em8qeKLZu
I/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8ToakfInHM3tAzoDsMa5seLEzW3/h
OKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1odT4SA/IapQzLLYYmPqablie
gmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpuxGh4UTLmyNuz4LnE+ytD
UTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCrqcmq9TuIkbNW5XiD
7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWdE3dO3DkRXjR9
0fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA0tJLSy8t
DZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY/Grz
q82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQ
uh3rdqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj2
57f3r5cjdHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99
AHRihisctG/VjfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24
bw8wlAx/FZIBokjWw5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7
mgSZc9NfaVHg+Fn9QUsExaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKr
OTmOcKCiPdD5Ocid9A313cHvcPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0Vd
ClJ70UWuARg1kzYd1A32fdafQZurfs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbO
bAHTaK2UoTDobb4PfQUIEnpkh4DJqi5TB8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0
j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8FazZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa
9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LLgJnAHXHCFQupG9LfpI2CUZX7jvo2P+hX
yw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHFq7fV0wSEFw701i6DlG760ssMvh/q
fih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSVxz9CRp+UUq9uQF3/OqfKfgV2
P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZhkDYno2ruAwivrr9kOQ7S
aO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z774cWPJsybMlz8KN
oTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuXL7/PEWcFgQAy
JA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C1EXzFVNA
quY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ8Iyq
vKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Y
y9s32Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE86
5Ky1j8vqDbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41
PeOgYkbpj6MfQczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1
OuRvJt+u1RO0OtlbdWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/
d35is8CJxGuTz0wE81Pz4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7J
DbMrPIuCjIPWFbcLgtcN77NBo6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3
oPj1Mqsj08E51zZZNkO+7yNvBdnhdpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQ
ddVx3GED23bPbTjAOEAX7+wPzuHKJfMsiJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1w
xYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk40KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWho
uAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtbEK+kafpToMyV4ikIUmG+0caDKCaCJAOI
EY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyDYUqxoWW+B9cM+9eZi8FnctUHzaqD
XFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry+ta/Gej2OLras8E0UnqrdADj
OVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz6yvub4WcMzHnE76E1AI5
g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHOZ5oniMG6IOUaMN5Y
wpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhPaPWMS+HhPk+X
vS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDbBOdKW2PQ
5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhKiocm
b1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbK
ZFSeVT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7
Ro8AV38IqOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9d
fHbxWbhQ5kKZC2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6N
OP/xxNlhz7W9AKmYFC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyAN
FJFiAriWsFC3H+TG+hf6W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8
Kq0Gj4dVTtfzALNX6U7VC4EcSZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7I
LVDPsdSQAt5TvHf5FgaPaGOUR18wV/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb
9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZTQFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9A
pBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFlOGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+f
IMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhqZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6
/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0iGmihBwJWmM1g7Lg/Ez7WssPWi2a
qd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E18P/Efi9CLgREA26guYSxsXg
fJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjbgPO+rBMTQW7pKOh9BHLL
vS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5A9D3MW1wDQNrAfOt
2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3c3Nzc3Nz+yPe
31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQbKK0GkSAK
aN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdAd95z
nXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3
RsI3ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd
5PFyMshdRbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf2
0X5I35bwMtEAOc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRb
QafI6+TvQVsjYrkJ4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhh
Wk/lHmgtxWeulqCOsRfU7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0
CwHvj4wVHSngv9xjhn8zuN3h2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skG
heG635MJj9aA9YTRqq2DwgWL5gZ9D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5Wub
VoOanDkzoTME3vCYKY0Aj/xyTKWv4c76t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5u
bu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQ
MmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1E6H02Obtys8F342hUb71wVnN/2WR5SC2
as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWnP8mQfdTxOGgP2DZnXXFWAWePzA5x
34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y86+t4DiddCJ9LmjbssyuD8BV
U74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3AqZr9/gGRHVRTGsEoqe6
2fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7IU28/SKhHWgX1J9c
HcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPHzPYgxqSPFFdA
3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55IchtlCRugS5H
t1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT9me1
gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy
60UY5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+r
KcCH4pC8EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db
/xbWVSM5PaUGFOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb
2QmgdXattvkBG/Q3pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5T
IWhbQDOvMFB+UvIRAerRN4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NP
kIzSS2kSSEdERyJAVNJiXfVAOS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRS
A95+k7vF4gOJdeJfvTwDKSuevH14FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keY
wdnRct0WCFnPk5+lRoKjq2OwVhaUunIFfSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ
3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGKXJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+
cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYB
y/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4BWjrRIDTCdo1Vz+zE7x6eNbgOOT0
zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBtAVT4oOzXxVeB7q5pZf6ScLnP
nfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5ubm5ubm5/zB9OnHVd9P1M
/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnkBHldQEDAXXBtdHg7
KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7VBZSwYktrXAd5
v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV4c2r+IOJ
seAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bNIAbr
J4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVt
FdVkMDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAq
qowFsZ5BYilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKr
sbpdbQSap3ZDPQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZj
L/Cp4CNMEuT+aM/nGgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSe
AvMh85PU3dJ9cAyU7ruuwdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/D
Ybjz4m47x8fw9PWd/XeiwedMuWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDi
fKbuhZGXRkHNslXuV6kF8jVpi0gAsUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8C
piX2S2C4aCgpfQnaGtWTTWDoFJpaeBSoV7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pf
g35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8Tn
UevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAWjDet7XKiQVmbGpZmAF2kTyvfB6D1cj51
3QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Qa2PQbQFXvN9Rv6GQ6nRGahLEzUge
kvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOfX8Dp5dyozoaURnGz3kwB+al6
jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6FYon6A3SeSkIFEno6Azi
qtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2agNBLNyQfSEKmBVBqU
h/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjBXssxxTYQXGWt
JazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0vC9nTc6zp
CyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx+RdI
JdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ct
Zyx4NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUA
jk9yK4L4QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4
zT9BVwhcjyzhEd/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50
feu8DGK5tlxYQLojjRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v
7IHEZm94NRWUOP8evk3A97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBn
ELw5X1L4CvDN75vtdQJMV/QHDTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAA
jSR/+QcwWHQ6OR/oBks9yAUtUPpaGwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQ
NstfSdGgd0qHpC2gltSechDskprs+glEGaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9
ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9vLqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7
ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/BnuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5N
bwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1MavikIdalHnT/Qv979gEdOTk5OTg7U
21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqqMGTIkCFDhrz/D5BVq1atWrXq
n4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFyitsm2n1AacAGMQNYS7w4
BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3FHSbfBJNRsCXRpIe
tENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+sZ9LTgCYuV2pb
eLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C7yGWwdlW
8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVokvMy8
d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEg
SvOKWSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxV
x6gXwJUp7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71B
mo2TvuC6Kt5KPiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/w
htyHuhH6mpBuzfox2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D
5qOVdSWD64pYrVsMhiuGXVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYU
WVBkAfw85ecpP0+BOhXqVKhTAeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfI
wAoDKwys8Oe9/l9NXBPXxDXY2XRn051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt5
24ufLn66+GmoVatWrVq1fn/5ChUqVKhQAc7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5
X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byc
zn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgAOHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2
FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8FMR90d7pDfr5+qOeHcBpSu3xsi9k
D7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTFXl96BL6i5BjvgqB/qZxO+hDU
yXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwnDGvNd0AqqQYaRoLutHel
4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TPATlNFywNgKxlb1ak
3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXSKoBI0xJwgrCK
QcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaCuCS+YTuI
g/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAagptij
aSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD
/YCkKj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og9
6s/AH0xafXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYP
t2BItSHVhlTLS2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u
627rbuv+NgH6rfjlB5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgs
BovBoC5Xl6vLodTZUmdLnYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkn
s05mnYTmC5ovaL4A8s3MNzPfzD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225u
g0unL52+dBrqUpe6/0U9X058OfHlRBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6L
V1cSJsEvF/cfO/McTIcNNvNXoFUXTVkKRBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA
4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3QvQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw
1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao4AE1HzVy1fMB44rgnMiKkNLGttZzH0gu
r/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxvMgtZfCDjI8u57J/B/tDjc59KkPzG
u53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ceDf0AXNUdDrsK1g/eNkq/B4W+
jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G3RFRVGsGpsVyT3kV6CtT
WP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7NbhIH0hWu36xY4Njj7
u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgugBIkZFEUdFfl
nuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTWSO3AMFDq
RjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqurwze
H+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38I
fR36OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgnt
EuD2j7d/vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz
2cB5yXnJeen3v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJE
iRIlSgBDGcpQ4AY3uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwY
bHq06dGmR7C14daGWxvC8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz
5syZM2fynn8y9snYJ2PhZNGTRU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfh
d2fEnRF3RsCuSbsm7ZoEL8a/GP9iPOx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/H
Hx5xlg3yao+B0GBnBWOd21DNXCm9UDuwOh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0
RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhCFakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SO
O1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73W4D/EuMFwxLIrKwv698UHDuNelMiOFMd
Uzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lHGMHw0KdPwDLIDbA8M7QE61JTTWM9
yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8iwZU8f8UnJ2yI23FQb9VO+66
DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJb8GwWVfOcBxMM/UHDCXB
Mcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC9HetAhGgmoU3uJpp
jygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJKjnxcag5qK9FQ
GgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCeiQ9FTdDq
80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DEfENp
AiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycv
gfo7SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/E
PpAfyY/kR6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESl
v7//5I7JHZM75iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ
8Olrp6+dvgbJ0cnRydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpap
WKZiGdA0TdM0uH7j+o3rN8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95
PvJ8BD3X9lzbcy1ImVKmlAlXGlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifK
J8oH3rR90/ZNW/C/4n/F/wrk5ubm5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1
axAREREREQEtsltkt8iG++vvr7+/Hi71v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1Dmo
cxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+I
SdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPAUcfx2tkd7DucJZ11QdbkSvIbEDvEEhEG
ZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYBaXipVhVc4PNZ47s9N0GwpfWhgR+A
7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk131RQLym7da7MA+xXNyxoOak/H
5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9Wn91z5j487/q47qOeYF/o
vcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjqlq8c7DEcrHbwJaxK
3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3QTQTXNe20+AI4
Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6VdwCfiqigK
an01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4VFd+
JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyr
pXbgHWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBT
OcjZkDtM1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0
I/Iea1e1q9pVkFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/
m1rxbqqH/YL9gv0C5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d
+sfLN3rW6FmjZ5DSKaVTSifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1
L1BxUMVBFQflXWC9G9GucLnC5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1
nPWc9RwkzEiYkTAD8uXLly9fPoiZGDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rC
MmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wp
luiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKfs5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0
rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpnlk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA
/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWBx+QLm542gVc1Ys4nrwDbaKLlGuCq
7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw4nXSw6RJ8Nh+6fMLJ+BZ8uMV
D76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8qcjLfd2C4rd9mHAq3H9w7
cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y84QeVd1awlB0LxRsU
eVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwfmKf5VwXHx/ZL
ji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt4v2R3zIw
7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcBK+nc
BT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0G
jhQhLEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb
0TaiLTyd+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFx
cXFxccBBDnKQ/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se
5S6Vu1TuEtyUb8o3ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU
+/3VFyvFSrES5F5yL7nXb7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH
5ZBySDmUN3XJuNW41bgVTMmmZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X5
6wvL5oHNA5sHQuonqZ+kfgJvD7w98PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfX
Sf7i+TFo5lE7uq0C525dfn45BGxeru726lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZr
N9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYe
p8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GXgcs3NdjSDoylwvsWqg7+HWpOKvkLONdn
f2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36CuxHIroWGA8v92a/theHZwUuRV44
Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZZ59+Gbyc9mZRTEeIO5X0aXwW
2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNcYUIv7kPGzuxo+4+w75cj
B0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qDT2vfix4lodub9t5t
qoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1OrdGQOrKtFGp
/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2MmKEVA22Q
JrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEiUCSB
WoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9
oNzccnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm
1ZtVb8Le2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCC
Eu+//tk9sntk9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m
8ZnFZxaDT0Ofhj4NoerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pS
VamqlLf9VsVbFW9VhOge0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c
6Huh74W+UCy7WHax7Lx4745Lo22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269
GErZStlK2SCqR1SPqB6wK2ZXzK4Y4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G
4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk
+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNSn7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1
B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687
wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJTEl5Nva2/ehRelrg974YFUl5oE+kP
uqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLho60FR3m1jLYPlDjDFIMF1IJq
D9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5qqme1xawVLeGak1BHem0
5Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3BZ5xPCc9zUHZv8bji
/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfBccrxNH0PiAeu
gY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD1l59S35g
oXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0nnRFZ
QF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUs
mD4xfWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1
q9SvUh/23dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39beh
ZL6S+Urmg6Ldi3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk
/ceLSopKikqC5NnJs5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/P
fJh3QfFurnuthbUW1lrIb444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/
6ino5ub230S6dOnSpUuXhKhevXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2x
rlhHWk8orCuypdQxSOyS3fH5Xbg/70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0C
P6PPC/8C4H85aHrIS1AXieZiOqirUs7dfQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl
5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhD
JOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSnV5IGZ1ggt76H2fcc+B7yDPD8CuzdrOus
lSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb0KbLtbQUoI2qF7XBMd0+yzkNxBFR
T+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEduB/IFeYBUFaQp0hKpF7BeMtML
HGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+StCzQJct2XT0wDNJflKeB
Okc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcMQveEhgRvgXyDw46G
F4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6roHQi9b6ieDa
qNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY7mzg6gOu
yfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFloKR4
tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX
25fbl0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c0
6aSTTjrpvGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQ
nZtwLvDGr2fWQ9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfF
nthIeHr3+fzodWC+73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3
oJhqHp/pwGPxOSuAsuKgboB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2f
ptkGgbVMlpH590FQm4oFiz+El8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKi
XlHfBa8PJfaIqwKJ51M+T6oNjFNvij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGC
Xti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRHykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5
Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgrspZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoM
aWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZpM1I/DDKL6KtGwMuPoqcnnobYVrFfvtoB
nvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3AEmFpaA+EJ8uftHpogLJSrSIuQnIu
ZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYmriKc+fxCiUsfQsycV7WjNkDG
XzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7hnitgXNT7GL9AzJKEOYkx
4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA3GZuM7dB1biqcVXj
wJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR4EoxsA00EouP
guCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4MtkHdLaKPi
N+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZlDJO
Qkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7Caw
TMwVOiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADy
nllQrw3KAPE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdS
V7kD5kDjrnkOxOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJg
elkvq4CYZp4U50F8L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMno
pyFq5YuSL1aAj92xxNoW6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+
BC8evT7+WoHYbxO/i1sBrE0YoC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasP
AqWJOl6eBLWB8qXNH7THlr3yKuRwh7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/oc
dXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/uaP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumk
k046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xk
boDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh04lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l
6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8dsaOFAit3TZrlxxgn5k7Z2kH2Hbm
quSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGCcSDzrYgu8PDuxXmXdsOTUtdK
XckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNez2McA/Gd+EmtBZ5IVybP
F6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0ZolYBba2ts9UfxDV
zZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RIMN6XsfIm6Iv0
CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gBGGKj+A70
BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7ymvW
5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghv
AQGf+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8
C94+cV5njiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARF
wqfxzTP0HgF+Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazv
g/u1Z7OeCGKpZrd9BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3e
wgwDz/svyt0cDfENdgzb5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQR
z5TmELDaUdg3E8hA/ZlRBxLPJmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4s
QRaQzeUd2QtEJfZxA0Q1WuAC+aX8SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2e
Ua8EpsW4LzeDvGYW4zqIQOWxkg9kD3lKrgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7M
ZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc
0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/WulpFOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M
/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1CXgyePq7zwHNzJFiKih3lQvqFtD8
NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1iGWAz0WwnbXFBGYBadXClW7g
TnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olzwlev6qeMgkznLc2LFIMe
QY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs7FPk88fg2pOyWZyE
U112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwqPBLMhuYQYxEo
G0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUIPDNeToo7
DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3ZmXAQ
ki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssM
ohh4X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN
1CxaZ207yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2
ahrRoGzSNGU/UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ks
n4FYqnxghoP1pvWa+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUO
MEfIT7QvQD40n0sVon6IGRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZ
b/mN/bvDO5100kknnXTSeZe8deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vf
gFudHt28nx9evHjp++w+KGuseTPkgJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJY
ynhISEo69WIN+Md7NvtOhGw9slTL1ACCy4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tB
OWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjvGweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDg
XFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wzZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3i
jTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh200cpp9TMQEcogMRm8ZfV2ehEQm6gi
ioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CHiCAEmDnN3XIxyAfKCh7zX+8f
3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPlTRDlRX4RCOYnZlGzMYhZ
vC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhDbZCP5RwZAvSUuc1z
IK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPLuyC/li1kTpDH
5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9l52iW4Lv
Pft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ecMlvd
LHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDE
PCWArpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vj
onUgw4KMoXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCq
gzvZ+6GxEMyNZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXI
LcwW7cCM56UMB1FQlmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6
i3CQX5FfmQJmC6y6E+R483OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ2
05AJIHObdrkLaKxkkKvAvGBUNB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUb
MyfIieYrbRVwkm58B1Qhu5kBjBbmA7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqr
lhP0+fpTWoNSWASK3CDK8In5AYjsMqv5CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywF
nmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5
+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWs
XbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGTo1AJeB6RODHqI/C9Zw21Hof7616+
ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0ZR2dJ1D+E8hern+v9FaQUcVqd
g0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx8CCwdwp/bO0PCR2fjH7w
Hlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeBvtBcDuIjkaycBCVa
zab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBGUT4Dacqi8iSI
b0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dgNqIUW8CS
aOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNaSOQX
m0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh
1DR2Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxV
EoGOIi8PwbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9C
oKeTTjrppJNOOm+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dG
ZQTfJq47mj/I0wHdX52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3P
TsPFK5e7HSkKvn1CS+VtCKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC
9eVhoDR1+RyU8uZyMQrMytw1pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu
3/f9RoG6VPlRuQVmoNR4CNYEW3bbaFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaR
BQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWLpaj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds
1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsx
sM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kYLJnULepokCbVOQdGjJzFLTC/ZiTrQD4w
w8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCoJexKJWAB+/kUKMJ88RLED2KEmggi
UviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLtApYUbbPPSZAVzL3KLTBe6qXY
A4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHmTtDvGkP07hDT49X0pJLw
+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwYbD9nHwUJW9yTExtC
RAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzpz6DInBKrssXA
o9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+v/qsUGiz
st2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJfGq6p
Z7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ
+iOoiuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEX
gLHETDYvAhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbY
Wqh+YDxx3fNcAPOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WC
mQvIzXIRDto1Zbj2PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7A
LiqDOo92Sh3AK+clnQfvNM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJ
IE7IfEpRcBxxDLQvAWWd1sh2CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTS
SSedd8VbV5xfdo4Od24Ga7Btsr0bhIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSCl
V0oe5264Uvr5ugO34U71pyOu1IKE2Fd1ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/Lf
tT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZ
rc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYHgAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2z
Dcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcpjdPmYrA1tRRXHoJyVOuk2UDV1Bra
ObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1ZXbjLrhWO4emvAJvZ2+Qpyt4
i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFyAiPlKtkfSKY4I0EsUpxc
ArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6A8gysrCoCdJijjOX
ghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0QmBZpPhaLoB1
j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tfDXJC5ltZ
ovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Zm0DG
I+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf
5X7Q73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7Hs
xbIwYMCAAQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fv
ZLLc/5383X76pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUG
Yh+4/GKnwpO2Ly8oF0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjS
ZqpjICXG9Deng/Os2TFhDuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru
9wYgk2wuQkBmkCVEZxArRCk1C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVM
XFfaQ8pUZ+2Uz8B9Wd40B4LMLqLFZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Y
m+QcszlorbV26gegVlSrq7VAGaOMUCaASBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV
6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoaKB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7m
o80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCUFVVFQaCW3IovqFYxSf0ItKHqYrUsyBSz
sugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5+Vz+DCKKcWIyEC+uKs1BPaw+spYC
z0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oIE+QB2cX4ESgiKtMElCxaDa0C
GPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX7EMhx4pM8ZmOQc5zER1C
/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC+6/yU8JPCT8lwNo7
a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZCm0NtDrU5BJ/7
fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/GH9nhP8VP
/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3Xdx3
MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9S
Knq7JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs
/KEmE+Mh0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7l
nOWOhaTaxiTmg7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKW
u6Dt13ppy8HSW/tEk2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9bi
RxC5hUc0AxbwMeuAkVwxk4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPV
jWCZr23SpoH8Ue6iIrBJLhYlQDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGgu
NtaCaCf6KQqIzqKLehXwECmqgmWJZa9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ
0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWfA/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46C
rCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JC
vYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQlcTjEX0rqkpQA3jNGY89OsLVUp5vX312g
Hog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7uLi4uLg4GDp06NChQ6HBtgbbGmxL
az/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yHDh06dOjQAW5WvVn1ZtW09d27
d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZsmXLlmnH07Bhw4YNG8KS
K0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW0Ug9zj/jXcsVkz0m
e0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P89+1SKzh/ZK83
1c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8DG70v9H/
Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zcM2nb
/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPa
eS4VXdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G
+b+bt06cvYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2w
lo6dCjxMGhijgbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHg
GeEpaXkFkQ0ibyrnwPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc
1wYogRBb90HR+2XhyaNnAU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYu
MRVkLuOq+RwMRa+jFwazES3NvSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5Edg
XjevGhVADBRdBKBGq04RBYpBdZqDfGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZ
Y8C61dLGEgLWbBZpDQVrS0sRa00QBcxXsizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU
3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqHgTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0
fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkO
WmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3kjuD9ytPkNMKeht3jpRPwLUt8de4
dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8hiF/uPk0CRPZ73cNZAaKPOJt5
Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu237f9vm3akPP8HvN7zO8B
P7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFjIsak3emPyzIuy7gs
adsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL07a70OtCrwu9
oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1etTLtwpJ7A
UxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHvCnz3
P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68t
YVvCtoRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz
7c+Vtv7UqVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2
IgwJHBI4JBAOTj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nu
JrubQK21tdbWWgtTf5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQ
R8BeS2dQ8plrjPIQv8JIdhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs
/hkgx/mAXpkTwV5B3tMbgOXXpHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVb
CFJOx1gUK0S2cE12noRVt9e3/rInEJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHc
S32HeQLUjBah9QIxVpRTZkByHufzxHbgXqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzM
VP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHFpiQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7ayl
J4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9GLTmPziCnmZOwg7FZH+ndCMpLsU3sALW3
OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQiRMWELPEbRqDsp4zLARVV2dyErR1
yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQnBC0NjQpYx0Ic2f6JUcVCMsa
USR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnGfn2mezzoQ71RugnmV8YJ
/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1cTQDo76saFSH5HuJ
++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh+s+2jZC0zpOJ
qSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd6naq2ylQ
PlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2WbusXYbY
ybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/
qRfW0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D
6Lmg54KeCyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RM
q8j9VX/4I0rPLz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6d
u3Tu0hkyfpXxq4xf/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0y
N8r8D/aNaR7TPAYu9LzQ80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJo
PPcbDwnT9edGMmg7bbuSBoAc5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2
ik8gAFyv3U2Td4ExUWmpbwGfoRGjbN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH
5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRYZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36Jf
B5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrKsoYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA
9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRNdFR7gznS3IIEsU/8IoqC+qk6TpkKopJo
I9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRXySdiQElR3lOmgTJZOSBegjpIW61t
AeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s20ApbKlhOgBatfaglgzZHLaM1
BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LLQ/zE6LKPvoaEQbFfRD6D
JOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjnPa+9u8BY4A1zjQbD
Ty/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSPy5GgvzDWeDeB
/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157svUD0G97
uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1lKVlK
lgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j
7Xd0jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqN
zx+RWnF5W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDB
QTDuxbgX416kTWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq
1t1ad2vdhe2Zt2fenhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusES
yxLLEgvki88Xny8ePvf93Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9q
p//UOP+dPd+2g9c+ie8bncAcrWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuS
D6iRxhmxCDIe9GsQOBEyfpjhczEDLLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU
6BkDPPFLIGxA1slOCRneC1zkUwiUbfZhfAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW
3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCyy5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD
1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLkeGKc8VVqA+EndrnwOcgFF+QKUFswTNUHM
lS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5zjxi7gXZXXY3u4I6Xp2lDAKlhdJG
1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9LF+D1lzZpuYFrYg6VYsBzUer
ptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/Gaz97HvtOUA2MCeb30FS
nleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBYO1teqSr4Tg+wB5+D
kFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7mnll8JmT+Ifvs
Qj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8Ck0G3+CA
HsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6itv2n9
Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc
7nM5bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVe
EH87B/2sPCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P
/Zs6tJ1aqUu9cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+
qF3qlI05xhxjjpGWSP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/o
mqbX6GbRzaKbQb6EfAn5Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2
fVM7/afG+W956/c422+GR74uC2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6
X7OM38DNKEuXZ8HwIuFuOzMj2E8rJQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk
1athEBn90OE8BhmaOeoETIXkCgGVvQqQmNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL
6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7vOTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro
0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYrOcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKw
uCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj84rX4ECjPeAaA8bNsbGQA85ZcIzeC
fEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1WfrK0D5QhujnQTlmvKTcAPjySqO
g/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0xWisPrnHJ2ZNagvkemzzb
QJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXUE9R62g5bLdClHGgm
gtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsHgWuwMznxIljz
q3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1MujnXf30M+B6
qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepydbm6
HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/B
pD5MGHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3g
WOFY4VgBX2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/a
a0zFMRXHVPzn9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKV
q/+H/hqda3Su0bl3r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7
/FG7wkcLHy18FOyV7JXslf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83N
NBduTb81/db0tETb08PTw9MDyhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hO
mHJ3yt0pdyG2e2z32O7/ej9I5U399F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778
m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56+
+CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Coyavubi8ENKO62Ruim2vjEgaBry1koN4clGtG
eTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4CLhu3em8BXElkh0uN3i3aPvjpkKuKyEl
KvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzKOibXa0iKTd4QvwmeTH5W79EeMPKJ
vNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqAedzcb+4AJYc6QKkIyhpxSZ0P
8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2IoCLdyGx0sBTTsDUA8EIvp
AcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL7Eftl3weglWzZfRp
BepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrijXNWSZwA7GWd8
Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwIcyXIEyJU
U0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+EdA+p
GPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWi
elGFb9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYib
p0Du8jxKHA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ
8/nlMMdC7ks+quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61B
A8RhSMojlj5vBi/8427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGU
MWqDskmrKN4HsVM9LU+C2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZ
C+p1MVu1AFk5RFOQeeUDYoCuZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPA
I3lTvAbpL0+YS4DmopQoD8Z7MruZFRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSB
MkT0sihgWo1OnhVgmsYl8xjYfrVb7fNBy2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkE
wm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/vWmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1
m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5TT/rLATmSnfhlMNgrSt9jevguW8EEwfu
r7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczKme+a7cFe3FHA7gX9oMeQW0CUUbbK
OeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmNCa5NYIzSf5UvICi733d+pUDr
hY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxxyS+ddP4f5K0T5+wvwpcq
fSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEpZY1FsjdoCeom+0Sw
vUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeBfd76juYg5tP/
dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD4DnBHPaA
3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7nAPb
YNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkt
o30agfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCr
gtaaK3I/qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39Lmy
PphLzETdArK/+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g
6my0PXoYxDpe9XvRETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvr
yOD3K8SfSpwSmxPs7/t4rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/h
wGUQPyuxY5Iv+F1QgyyT3jic0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdf
zdu/x3l/YgZXFsjRMWRtJsAvv62QzyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmU
ehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t9
4B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5lr/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpH
nb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0f
ABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuTrREE/RxeJqcDAvSwatn7QmDTDD9E
LAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34Kjs/924acAv98wYMzHgKf4YHf
h+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd9l0B6miry+EPNLDN9fkF
zHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLaDyAqqweUPaBFWSLU
7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSywy3zPpYIn0p0/
/kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZApnyh+YNr
gNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdUKuQZ
hJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTm
Zr+xG4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc
2gMc+wNq8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHU
os2WbaFAgaxZKnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7
Y10a8CkYlc313pfgXZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVo
CKIMHxotQTRWc1IJLEnqMl8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0g
bHKdeQoMyRf4At+IIuYo0N77r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKm
A42UL6wPQMmrxml9wZigR+AFsxUf0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N
73PXREiZEf86NiPYrtun2dqDvbO9t+MI+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ
2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiP
tHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9HYPAG+xclLwFXKdTmiTaIHiCfxP/raDm
U4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukUAgpr27VeAHT4u4M8nXTSSSeddNJ5
N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fyJ0ja4rE448F0uV7a20H4WMfD
HD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZunnGgaOhfbX7BiT/fHmc
awd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9Arl0ZBhbYAA/tN5/e
ygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZVcmjXwVbCMdP/
DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG2jFrfUdP
MNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkDnJXA
W8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1ja
akPAPdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2
zHbbVgosIZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt
2ggiUri9JcHdxlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaI
I0aivha0VcJKELg/cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18
miY1AJvTXtDxOTjj9B7mPgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+
QYmAuENJIdom0Bs6Zxo3IfmeUtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE
7MlBOzz3IcvH5SoEbwTlgqPx6/ehSA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwG
fbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwFtJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2v
Qdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYiJ+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/S
G/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uorn/EgylrzKQfBLOuNdn8JcoyR21sDjFtc
NZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw8Kw1LslvwLPdvcubB6zzNcU2GpQL
SnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3Qe/q6ZHyK6hu5bX2K5iFyC0u
gN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0fPXKuRN8WnuHG8GgzbBU
tQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt27QnIPYaXykVwPOV
9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkBycoMQ1A2t+tZzM
A7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+83jrxNk4
rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZvC2eS
2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9be
lrLW+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGY
j7QxtrkgxxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kO
Zi1PG/dVwKG2UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaK
W1aCPty4Z9jAU8ez1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRR
E5QzYGYy7+hXwLmAFdICZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POM
vGA2MXd4J4MZbT4UA8GMZIUYBpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkp
d8lZ4Gnsfu2dBWYrJcrwgHWE9bTtAehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2
NbBJyFjwCQpyhx8G7pufyxUgh+pT9SpgFvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65
/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aSTTjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J
91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7NgkiMgdvlhGQqXCGW8piSH7pMynlNrCX5bID
KJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5wt2eauyQUexw+uNYT6FOs5bS11yHX
uOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF9o1PWbBp6jTVBsoA5Tj3Qd4T
LY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0FdhpcGh+qb41gXrOR+PZQTY
7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIXSBga/8Gro5BUJmFH
bFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUOzKmsk3fBXtZ+
zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlwPXdmSAiH
lPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6Dczn
5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8
YVnA1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYk
gKW1vbHtKGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoB
NQPSvgCW+mGTp0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2
qz/y5//t/Lvj9d/FlsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Wh
b0nZEpKijXKvTYj5LPb7V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzz
dSoLIGcP/17hU0FL1AqpX4HlolxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3eh
Wpa84P7B9TppJogcMlovBfFXnoe86A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zP
QQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/
bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyBKXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5f
NXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yWB7/OGAG+eXz9/I6B7Ka7jY0g84veamfQ
tmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVnp58WuPMUnJNcj2L3g/s9V1nnfNB3
efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5TeSpjSEERlYRHdwWxDOfEL0EyJ
U6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cKaKiVtBogigpFpIAyR2uo
HQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7PcpnrE/mI2VGWobUD6y
zrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rthBbgPuo6l1gT
3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhybkXYh7Hqq
66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0FrBq0Z
tAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafk
PZi1I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/
dVVocLHg9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+z
YmCba7VbY6BQ/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2
z69g+HrsKZ3A+MVVN/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwB
xjf6e/IUKM2VetbS4L5mjHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW7
7ZVDBz1ZV/RPwBxknDMWgTDN++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FE
zayOQiPAf6Dvr+FfgPmDPsxZH4z3jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5
x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2rQE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBP
s2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXl
YXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9
t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv2076tgJzjTbMkRsshe0bfKq9u0CN
i4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3QsmXLli1bQrPszbI3yw4NGzZs
2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rpabyr8a7Gu2BO8TnF5xR/
8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X7fDP6ue3y79r9127
79pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3Sfn9a7tNyn5aD
8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/zqzeNlz/y
5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpKSkpK
ggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v
/0nI9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJ
AAGihHeKWhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0U
OBIta7RwsOfR/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeD
tOnVvNPB2Kt/7bkGWjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNK
guOc766g8WAbbf/eLwoskbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+6
1fIleGaaK9VmYGnqkxBYAqy/+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u
8SW/hLCkLPNyR0LIjvCh2QMgZGv4sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6f
oVLWK+Do4bcsXAP/+yF5s62G0DZZRxReCqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DU
VsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTW
BKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5Gxi9PB7neFAKyIJmHRDzucVs4KYw5Ufg
Kebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+4jz45LBYZNS7C9TJ+yfvn7wfwh6H
PQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOflPqk1Cel0oYsl15ZemXpFZh7
du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF5WHFyhUrV6x8d3pJpezF
shfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7SO0haYnOuiHrhqwb
Am2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3funJYIfvTRRx99
9BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym/UyNnxo/
NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue7Xi2
4xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k
1QhImSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv
5XFQchCuxoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78C
aHVjfkjpDbKee63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzO
tRa0Btply2VQY+QlmRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauP
tLVg7W/v6jcXxCD1pqUIqIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5
YQwH8R6POQjGfX23uARKqLW9zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1
+KutAK9ntvMyeGd4XiR/BpwxJshPQfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcr
gAzgidIe9PpmG4qA0Vz3cXcFW0HrM6UocM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/
YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYyHNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6
vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCoZgG5DZgkXeIqiMqq1/4tiEuWamY38PWq
jfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmtrFZWp63v3LZz285t4cOPP/z4w4/h
p3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDoRje6/etOMKkXWEuoJdQSCt56
3nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8QcE6Hqzqo7q+6E1RlXZ1yd
ERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Zb5k0/SyusLjC4gpv
b8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEHbGMb2/jrNMrc
KHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou67iswB3u
cAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa82vP
rz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvh
Yq3bZ17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVK
a3FJ+wzkFHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+O
TpAtMdvsrGPhnPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAX
cqkBiB0UUh6Dplm+s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXp
y10aaAlqe2Ul6C/MSPM8WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOc
va19CMhoqYrOgFUGmH3A1ds703kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtz
zDCIa5b4fnJW4LnxUi4H7aIWYz0ISoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU
/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVN
L8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAnuGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq
1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9
qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKyFGh7tb3a3t+vF+fFeXEezCfmE/MJ
DDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+svy63ZYlliWXJm283s+jMojOL
gredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9+fXl15dDl2JdinUpBp/7
fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5Th+wf9HzQ80FPqFih
YoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jReaE972r99P6lT
A9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoVK4jJYrKY
/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2NVxDw
je/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQ
hxA98FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui
+Ly05rWVhcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXs
q/0OgdgssmpfgTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz
1NRzgG2pVkWrB+rXVqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7
bPvWrzlY6lg0bQtoxdXb1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7Uk
qAky0psL5ADrCdUETw33JiMXOH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2
BfWu+qPlfZDzlfFyKzicjoP2xiDmynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4Jyoo
BsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcb
oSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8UZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby
/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVLlyyFKturbK+yHY7PPD7z+EzYennr5a2X
IcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyBmJiYmJgYuNvzbs+7PYFlLGPZH8uX
+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E3Ii5EQOzi88uPrs4JHdO7pzc
GQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+rT6rHat2rNqxtO6md5re
aXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaHbQ6DUudKnSv1BpXE
VN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7vWq9ZxmYZm2Us
TGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P538VbJ84+
twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniGewKh
8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIz
W4OsK8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG
9N3eSE89MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxX
As8+d0XnPVAfKTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1
QajWML8R4PPcZ4AlAFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYj
sERbTM0Aa1fyi2aQNDRxXPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQ
njtofuBN8PfYuir5wbJFW6kUAREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5
BpT+ahl1KhhFZVvzInh/9YxzDwTKskXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjF
YKzXW+sPwZbfOkULBLWlGGoZDXo1Y455AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeber
Ghh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMqk0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2
lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFCRwsdhenzp8+fPh8GMIABQMdCHQt1LATd
5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT8E3DNw0HhjOc4b9fn/o6qVvTb02/
NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN7fi2+mybv23+tvkhpkNMh5gO
sD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+1H9S/0n9JxCSMyRnSE6Y
cnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq1KlTp04dUMup5dRy
/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP+DN/fVP+3f6d
zv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4sLbSrzcqe
oNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+zj3SD
4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5
XtkO7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQf
btQ49MYuJ3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6
geBQtwV+ACZpVn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0Wrp
wBYwnJWXy8XA8LMpxJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALe
Fo6DZtITtH0gf21cYdFA/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TN
Ur4tBOSXjJuMpUGP1qoHJoAwWxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALK
WbWJlAmWry17jCYIG2aNNPQCYVEg3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9
ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsDdcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4
WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ecOw60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A
9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5DIx4+73j7134u4d5UNB/poJa1X+1RvU/
VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/lf9rrGhT0n+DIkSNHjhx5DDPOpAph
4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0GL8+Obln3AHSsWuP797tA7vmc
VFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj4TUQRupZ+kLQGgjT5MXA
VD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19lf/R10D/mKXE3xN4o
VqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNqyxMWBaQk6aK0
BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUHJgNoZ/Re
WhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzEAeJo
8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfA
XT5VL4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1an
g/SupirDQTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3w
jeElkD7wDfA1g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKs
gyyd5H2ghQnLzZNB/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysO
rDiwIqyqt6reqnpQI6ZGTI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZN
BNMFLTXzLHRxRn9d5wS039bu2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuD
GqIvzO4Ckl08EuYGNnFZuAz6Df2uOA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/
pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7osCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsR
As/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+
kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxXrG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLe
EK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10bA0J37XbgI4h6NiTGlgjey55vPN9C
vphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsMfO18G90DQWppaGR8FhyV7d0t
Z0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuAcEv40fQiMJHzgh+sP1m3
GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7hOc+ZD3r7JhTHUyT
DDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhcQlggAgKTNIvw
DuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPieHAXma+ah
oQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZodLL
lV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuC
OFWfLi8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ
3WU1CPvKUC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5
O8DV2vm9OwnCcqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPl
ZfktW3kwP2FND8QARdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinf
gDhNdwr7wVBNjrP4QI+XOmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNX
k6uC2NfwrHEDyHZDFVMMmOymGcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8
m2vKZTD0ML8p3QY668dMGvgmKoP844EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE
26qDwWCYLntM+8CwyYh1EHgG+HsErBBoo1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegf
a98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVi
bTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3D
eoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/FvBfzHixlKUv/0QV1qcu/URL5r/qf
9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577VciJ9VOrNWFLgPCOPFuyCW9Sxz
nYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2Bj2ZD6UBIHzGEf87wAgx
Tk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6PAO2g8r7rU5AOWxaZ
i0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8SNxyML5qnhrwG
OV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO9Bh1sBIC
3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqehsh3E
tfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3f
S/cgLM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0w
dxbtnAOvxZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0J
YWmOKNP7EO61lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWF
peJZyDqUEcjZC2E7QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFB
j8efTpzvN3EOMLaH8Mz4fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7e
mlnAJLWBfyqIy8SexpGg6srBrJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8
eNnRbDjx6umembugd0afeS89CyGzm2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/Mtg
ulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+s
U023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8QKs4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFD
QS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlriaPBleW+4h4A+0Rcv2MC/hQqm78H6uvVo
aFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3BfAENV+TPPJtBDAzGeWJBek3poT4Ld
YR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73VwvZa/L30PRO6KjLV+D+Zmhkzx
fciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUHqC39zfJvgulJ613DaMit
kfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8Jxqetqy0HwVfVH+lN
ANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA4LetE3dAYKna
V28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i+buHd1BQ
UFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+Fb4U
NwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO
96WdIF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuH
rXhlsNQJGRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B
3aF86YsEb+WcvRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJ
A+ublnXmIuDPd77pnAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DY
JRXVuwK7qeM3gatc/iKlC6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP1
7sl6/gsgYRgmx4H/vNZWKwf+K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyo
NADdhlGPAfmEcYI8B/Qs0jCB+oM6S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/
gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9
rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEBiEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoK
CgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVBU6yRYkfwt83skt0QxK/Nm0xRICq8rySB
Ok8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzPxYfomyC/c94mXxEI1cIuh80GTzP/
D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILYKqa0+TMwfBweEvMscNM2MawC
+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeTCs4r6UVudwZPMU+7+M1g
NlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/PVC/VndKFhCXaFOk
NuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0FMV6YbNwJHBNK
e78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQRweG+p6F
wFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4jUCQq
5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQ
iwxmzZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+q
AkIttbGyCDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCg
oKCgx0n8sw1It/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3
QKmQH5v/IqTXPn3w2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZ
JeNOiMuIbRPyOvgauMq63gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVb
ZdD3SPsNkSDk+j92doDS5uIZxfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GN
laqaJoHniDDU9i5cnJ/0UfZYyBvmi9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus
9OS24H7LfTd3Kahn/a+5zoD5PVNAagzWosa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3
Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsGlnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTs
dgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqmgnLGv8h1CHy9PG/53gXfi/7VzgiwbpOy
NQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+IpeCbQ0mkp2EMeq4WoEGMoLHcT5EPVq
qCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhKGV6V5oPQRUokDPy5gZvql+C/
6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX/S3BleVp7twBvhxa6X6Q
Qo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcTX4h0g+mc1l8s+ncP
76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1CfA1+nLn/wvqn
oUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht9fqWi2DY
b3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSIO5Ng
AOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O
+nwtRKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dA
QQSxtt5eHQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUK
tNX7Q86p7LysgeAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhT
cLt/xorMNyC7t2u+9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3c
c712MC6XIqUfIO6bsBrmiSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJ
ZRIpDr523mm+KSAtFyaLyZDTMy/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+
CJSril/7HJRx+hYFENfrMw0/QbHosDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSK
X/peaQHVeXonB//uYR4UFBQUFBT0OPzpGecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5
V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3ICpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1
n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8XvHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZq
r4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupTyJ+hJ+uh4J6cNStjARQLjdgpVgbD
FsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN+BHyxuodZAfkeIRo8wzwfK6M
F/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6PtoVAsKeZa+HtgDGiLfRpI
AfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+sfgW2btapjtLgnuBq
4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqWTmuLoFj96JVR
aXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBlcdaS8sG/
MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7i6t1
bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUy
l8p+AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57z
ffZz4NLuWVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKg
peT/5HkWxPIR7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8f
DsIm9wB5EpAC0k4wrk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6H
ql9VeAnsXfXFMSvgl1XeTUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRx
xqvRVSHvSb2++h0o7/gauVqD4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFP
OwQljsTPihwCruM+QVkKnin5y3NaQpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXP
dPdV53JwpnhSc7eB97hnuccL5u2mU6ZQYLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9Y
jXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGl
KZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJHKa1AT1I3+G+DVo3njN0gp4k6NJAMmujt
qqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZkgRwupqgXwZFm+UQ8A3quPlhPBONG
eY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD1KUyB8qvB0+2ppv6QXR6fKmY
lhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKlSwuP9+nTp0+fPhAWFhYW
Fvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQflI1+Zn+kFik2pan
nwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6YXQd4EPFNQjXQ
r4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814Ex5l7qy/P
AO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBqTr3B
3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/nt
nbnu+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nah
H4N3rK+JZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhN
m01lgTlK3YzycL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU
8Lv8FfQXIWNM7j3np+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/I
SVMsmMrJS9Qs8Lf11xN3gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0iv
mPYaF0NeD+cB7yhwnDJvMayGhPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfI
fcIEp2vcbn5L//sGduPGjRs3blyYQBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzL
L3D16u3b2dl/Xbxy5UqUCA+Ht97q379+fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xP
RITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3LzMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2i
KP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B
+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDvsEWGjwNNU+3C26D3Er6jDQjzuCjE
gFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5/MoV6DFWyroTDilbKuj3P4KE
6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh3YRjvAVdarWMu9wRbg9e
1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L7QgI7cQD7ALhF8Mc
0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEdeU8gemnEv5Qdg
vvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUBJV3MMMeD
O8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQmZtR
/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0E
Wm9K0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8
GkpWKuYsq0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRr
f90Hw6Ps3bt37969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2
QWZmXl4gAGXLli4dFQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRN
EODpp4sVi4j4tT+P83n/2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs8
3t6A/n8mq+7f93h8vsK4bdvGxEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQ
iml3hVRQV8nbmQDCE2JrfSxIcYQYNoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgY
THpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A76qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7
Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmn
IHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w24dObIH80dn709tByJ3IiJgtYGxoMfvr
QsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0V1yoXQBDSeNdxxG4fytvkh4Lvi6u
b30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzIc7l/0i3gK6029JlBLikvFdLB
W0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9yS3vAfCleBZkpYJ6mhm6
FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDqpU3wdwVHTfsFy0nw
NgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGOwbve7wJhgfyy
tTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+QVoVfg9zN
/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1O9jQ
fkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4u
LAwOHbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c
/nTinPzGdePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdB
v6xf8DUBsZQYJX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdA
C8EhW4GvhK8CZUGt4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSul
z4O98InjrZufLIPbpjRD4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5
NnQrpN+Pyi12BLyH0rsmxYL3nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q
2s34klgazHuksEAUXG+b9FLOafB10vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qw
twd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZuAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJ
eALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4
jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoPIKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXP
dTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCNUXcI3UDtpx8Tb4G8XtIDdcDU39xQ
9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHWWGxF8RGgFxU+sgTAfljsYTwD
Jd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAFPPPXfTj8IwW1y0uWLFmy
ZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L9dtSO7s9LCwurjBO
QdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1HTIyFOUfnd+1
a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE6JDXHuRv
BUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpIDoEUK
L4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DM
Gahe/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dp
amlw93a38r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD
3mzPGFdpkB4YLcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH
+jVEVQqpEdISzCfFCOUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+
bcpsfxjkf5P7TH4iJB9JWZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/
cn9peHAs81amFQyfS5H+3WB/wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggL
QSrNp7oMxhjjbnk82CvYo02twFbevNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubs
EpnXQNmlfOf5EaK/jnreuhzi9xWvn3ATxG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDr
sWNRcPTna19d6grp+/P2pXUGZ72srintwD/KMyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vu
u7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrHKscqxx9/3wq2V0ddHXV11N/d+0JTMqdk
TsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Zem3tt/u5n95/77yfo/6aqiqKqoKqq
qmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z+f3g9wcCilK4PXjwo4/eeqtw
+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j24K4j9ufnnGW65axxswA
c0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE8bDQ07ACpN32mJhl
oL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/SzoGawVe4H4o6hZ
DoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4//EPXU8N
hLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbzlfxv
lL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U
+prFcg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBu
XzVC6pm0gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175
/OF50XA+5dZ7rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXz
YhBWCvNNJ0DZL16WloG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9
vU1rwNDJ3N34BBSZFr4+bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98
pQbsTzze7szzkN6ITYEfQVtgnB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmC
mrtGjRo1atSosNb5cYlsGdkysiW8/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12
+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu
3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3Lti7bukB/+tP/736SQf/xFKUgkS1I2f4906aN
GNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUV
BQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3ZNlicTh+v/+o6/+ogriP259OnLOs
9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4RIoB7XOttdYPpNZFR5ZbAuIh
62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt/SPBAPo1Suo24IFu1L8H
vRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJHzTth7dklWVvjoHTH
SmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D5EVy8pVP4EGC
fVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfaaTC0loeJ
30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+2T0S
/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F
7kU2i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpc
uvMx2OOZpnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V
4Pb41FYPhkG5F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2
vg+OvnEq43R1SLmsV9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHi
xIkTJxaeHz9+/Pjx46FEiRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUN
GzZs2LABMjIyMjIyICoqKioqCjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn
5u6su7Puzjo4fvz48ePHC8MXPC4uLi4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQo
VZWqSlWYkTsjd0YubC66uejmolCmTJkyZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0Wdpk
aZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4
i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFrxq4Zf/z9ubHmxpoba2B66emlp5eG8+fP
nz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe8LThacPTHl3b/7DNaZvTNqdB+U/K
f1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiSviV9Szo4nU6n0wk1F9RcUHMB
TJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5oeeHnoc2MW1i2sQ8vnH1
qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z+32+gpng385IV6ky
ePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv1i3Iy7Nao6LA
aHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvtzYgPx33c
/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsCaMNy
W6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4
flL7luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5Ehb
lTw7RI61fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUz
JhVi46JioidBpDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5
H4S+YCirTAebTfrcuxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjt
eBUNwk6b+pcKAWsTw21Lf+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc
3Ku9SfnNoHRqzPHi88H2vpwWvh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fg
bZV/PmAHxyaLKo4BY2v9Y6UEZFRJeeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHu
obzz7uJQ8UTF80USoGTXMkLJb8F0yNQnVAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/
8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyfO++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJ
EyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6ggTmUV/1bym6peiWorD80vJLyy8VfsVe
bm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPUD6Hr1K5Tu06FnF05u3J2wcw9M/fM
3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oePjpO7O3d37m7IL5dfLr/cv9+P
5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlhzwx7Zti/3s7U7VO3T90O
JwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8pflP8Jni35bst3235
z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/vjJ8ZfjKAN84
vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7TuHpc7+v/
Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1K9z2
6VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QI
qUAaJr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqI
AN1NSQRAQgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID
6U2mQ8rqrBrpD0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4
cfXutrvWws6O+7PObgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ
9lsOOHqCb2vWK2nnwD/cednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn
5mG3COlfZg9xfQkPWmdsy/kGzCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1
LFjPmd4wxoM/RnmdhuAdpt7KTYVcMbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdzt
AiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJIH5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODI
jtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLnGTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGT
bWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuFzYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6
hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0CtZxhpOAN003xCd2Ct0FyoA9Jz4alF
40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbDtc4F7RS0WxDnX22/IIFZu3bt
2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03dt3Y38zgPnz9n1WkQ5EO
RToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJvht8Mv/nX9+Phkpqh
5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9G+VJBc+7wMxZ
M2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n8bZO2Tpl
629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW5Bos
PrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpU
q/b79gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6
tlYehHhu6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0e
Jm8GVoi9dS8In+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKm
hSC1NW3Q1oHwjCzKrUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgoc
RqFRycYQ5S3hVn6ECE/EiLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCk
R5ioNof1T2iVyYMTNkPd0oNB25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e
2jZwp+SNTs+BQKQvJL8j2GuY20ivQWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX
0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNB
nyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtO
CdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVfBHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3ua
BsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH+VNQ5G7Rj0sdgbDXw0fGLwV/28BU
qTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR7jmyR6QOAm2GMTJ0GDBffVl4
E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxasXHjxo0bNxbOCP/R9ZgL
apsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQTgonhd98Na4N0AZo
A37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAEJzgBdKMb3f74
6/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E/6PvzweJ
HyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16QmNWHz
zM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBb
t1q1ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/Y
GWfzcVcDuTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNA
HCItQgHKaudZCPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGm
HiRt9E0yFoUrSzLH6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWE
T8WODAblTTXTuwwC9QNLvSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2Wd
cZDvIyhpid4dEQPlo8rVDzkF1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3Ms
eRJwRavJNAg9Ffpz5BiIHZfoK5ELifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30N
qfvTOuZch3M7L5dL+xByt3pD/CvA1tfeOiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUU
y486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSAMgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4
eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEHQBVxWatD1IionxzfwJPnypVNOA+h4baP
QgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/iCyjbo3hGORkqHKpYv1YLsCeFfJf4
M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvnT7x46hSkHsrqd/MoqBHmapZU
0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtNlb2Pb6AWJLDFixcv/tsP
koL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDCgQowadKkSb+txWvR
vEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyXZr80+yVYKCwU
FgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYRthG2whrn
GsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPtwvYf
/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86
vnfvtWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3
+fm/rtf86FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG
6ufg/NwbuZn9ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08
tSkLzledeTk3YO2sdec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf
4CVqC59D4Cn/Lf08iH6pHTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5
Kr5v3wglXzctPDsHskqHp+aMBvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7N
E6/a34Z7FczNS9wD7Xbe7rQx4Oua2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAso
Xf0tIG1nTrQwAFzFPBfVXHDN0p837AYxRi6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD
5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwnos4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2
EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKlY2IrBCB0onQg/mWwbQibhQ+Uyq4zTglS
RiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+okHIfLCPdxjCVoH5A/tsSyXw5ftK
CXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQvu72gOsmyGueq90pAx6MhvBP
QR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTxLeAZ2ujV/88g6fT4BmxB
7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gNozaMglEZozJGZUD0
neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej70bfhTTSSHsM
/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1AfaA+UIcH
ox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWIeqTw
ZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/
HX/hzY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2
h1Ue3n/U4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv
/uST/2iCpyDu4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFf
jPsFjw9sxvB5EYtBvaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75K
fQWE3oYnDeXhZon7SRdWQPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5
GSo8iN9gSAJrd2tRDoJaQW0tPgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36s
BUBviiAkgHhQF5V3wF/TWTGvMxiTDe3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp
6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXR
lqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMvg7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4
BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz
78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfEKEsVuB2ecfv+cTDUk3da+kDUujA1
thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8sr7Tehpjc+E02BSJaRRaPygTD
EPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW0n4y7AJnVEpOSjfwrcwe
dC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDoE+gZaAeBQ8pq31lQ
ZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F4cOHDx8+/K9P
nIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OVKs8+O2MG
VK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0Dk6lY
sfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GO
HDly5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH
546Dtj1gXGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c
97jmkLnAXcc9BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5j
GHBSb6VfBHGysEj0g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bI
KND8asdAKOidDTPU1aAsslRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbU
mOM9Bm+crfnuhW/hl+X7Lp36ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTC
d4TdjmgIYWdDy9ltYGkdeceSD3p9fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+
0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9
G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIWMC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/
RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN620z4BAobAKmk4uCbm/uh7EvI3+C4HngXJ
bM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSsu1/10kYIxOvN8uaD9rH+tvAe5Jdw
V9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/RmBEIBL0idp2dTrop9X+gfqg
BgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7wV8U/M9UsOzcnpV7Vu5Z
CQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6j9Y5/lf5/f+4Ztjn
c7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3az+xst1tRIDTU
YpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTCuI/bn06c
lamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcMy83d
DG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArC
FLGD2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx0
3IyrCYbz9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG
78Kz5Sr0e7oflJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5
W80TIfRLR35UNIQkhawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QX
y4CS6NX0LSB/Uiq/WBfI65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9Fmw
Y3gmYSqkzTS2TX4ZQvbYD9kmQ9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1l
s/01CPi1ndJT4C8aMBEDOTnpC7zPQeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfk
Nr59Mn0TuDpmpST1BeW8sij9I7B1t3+pfQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2g
VNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8atBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLp
h5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9AstYxjKAoQxl6J9tNSgo6HF44onSpSMi
4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHiERFw9uydO5mZIIqhoSEhEBY2ZMgX
X/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/+tPcfj8kJPxaQBEWZrFIEmRl
iaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9HVSE5OTfX7y+M+7j96VKN
B40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/TeHkdCIG+O/pVcDYpc
bVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9IEGNXFcpF852
veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4Wd+mrwJ9
mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqEW0zO
Su9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQ
L3tm590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkz
gL+M+pHiBf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21
IIDJbXrPuA+0zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBM
YHsgA9QG0mLhTZBijMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmX
u0FufprHPxPUE2wJ/AJynNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+
HhBoIpwGPUH4WVwFvC9uk74AXdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+Q
lZWT43RC375vv/3113Dx4rVraY/jJotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnP
PTd27KJFcPr0tWv/aJ3ox6V69bJl4+Phxx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t1
5vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9b
bn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgThJCRMNr5cdBBkD3FXzbPDqYyT2qFZYCln
NIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQejhO/vdwN3hLQhcAu2n9hz8btL4Ovq
p8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl8oE/AeSFNDCfA3edPF/WQLi6
9lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2ARXzN4AF9pYjWGJgibBVD
QIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8ufk6iJsymt8E5Ana
PPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuyZmRdhhxnVn25
E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ/QQAmaZa
MgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgoqVwC
9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+Uv
VoR7i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0
q/p9zQDaSf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp99
9o9v4vt/zZ9OnC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AU
TB/HRIZUB8MKZsibIfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZ
Mze+TBNBPBvyWuJC0BdnrksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294H
AmsCy31TQN5hirA8A+pRbaM3GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itF
xK0G+xVXpKUD3EjdundNHNjnlUmr3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8
YJXQm2zQF+kX0UFIYgzHQaylRwulwdBYT1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtA
jrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRpzoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73n
JIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi6LvFfvQD/RVhseACoTFLhATQv+BHcS3o
U4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTacMBwG+XRIo7A7YJlhmWH7CcwO4zrz
YYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT+mx2Q+N3Grq7TwBnEWegyTsQ
0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPHhWHwnXvFnU13wf9ufs4F
DyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1HjtHGiDlZP6pwCUp8nf
PcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+Fffibt4CuXvU
K+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrWM2YK6B3l
m4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymAb6zr
mfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/O
A54QhodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDg
PereCUJe7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7M
eM3VGzI/dZcMTIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6zn
AzJBjBGHiU+BGGV43/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGq
NZAO2oyMxik1oGnxZzuXbgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDb
YogaI1e05IM+jmrmJZBYrOj+5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0Q
Pzcso9grkHTYvUN/EXZe2PbJfhckz8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgR
hiflX5fPCc45BwUFBQUF/Q/xp2ucg4KCgoKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0Ew
cQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAfEEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU
9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDAj4oAAAAASUVORK5CYII=
--------------030202080101030400010806
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part28.09030107.04060900@mitre.org>

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAA
CXBIWXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAI
JLiEoIGgETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlT
p09Lly5dunTpkhC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLl
y5dB/rMr4ubm5ubm5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc
3Nzc3Nzcfgd34uzm5ubm5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zF
HGHAI0sR61oQpSxdUsuBrcbbpFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL
5KL61yAdzP0l4ytwdrCmZQ0B49ngq9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5
xhJQD0ijlA6g5aoPzQXA2i9znjMWcodll8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteB
faB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHnu0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm
5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGzl2e093YQJp4ZK4D+G+NGeT+oM131tF+h
+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRGmAkCkYsLFwDS//NGKvzbkoT3kJCB
AD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o0AicE+TFUiRou8QMPMH3hee3
xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8I6cn2B8meCh34eGjN6Ve
rAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1YO1qH6dbCKnhSYG5
oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ69MW+HWD9Tu2S
0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skjff0g+X5S
BR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBNv1lc
AOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAY
lnko7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm
+Bj0TqE4h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9
bF5rQRrpqG3vCt5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk
00D+UBkr7oI2QPpSCgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2
qwt9Le26NjkA9faXTy79AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3
YG7o/SZiFChhSkm7DkLe+n1ttYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HB
doFdC68EZ7ajSBEJss5l5/IM7hd6qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2
SiNe1wGvbXI153fwpnrSgWc/ws2y92v8PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJ
mfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNpdxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE
+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK63RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQ
d+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1Ej0GgzhSfuayglYmv/7gaaIn2W84t
IN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqvb/8C1AilmagDhgX6FnoPMGzx
MnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUCwLFVHq31B/NoD7P5ETA2
O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgnrBvSZgIG+Yo+GqxD
cuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPoK3/MPEATqdIi
QEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJDQtfUg0ml
oXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRvLQkp
3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAX
Q8B7LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZP
AFvtzIyo2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yM
oDu4grVrTgMoy8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJf
OZ5ZoMXlTEpXQLuY2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZE
GcZ43wHdA+movjR47/b6RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaB
VxGvyrpeYM+yLs/6HuRrzh2uFPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9
lOZgn5ijt9wGfbJezT4I3PY4G1QWjF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B
91zfDX6/wIOlT+LjW0KJbwptCyoOupk6L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGB
LwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZEkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNC
IWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+G9grKgnuz35x32cROPa4Clpfgff1xGr3
KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0dTXrCT4p9s2GMVA6uqRnoZXwqFh8
6hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISLIDZZ14XPhJK1S0WVXQ5BgUEj
fM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJFWNoq4IDeLh2CzJIZJ42d
QL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B+WN6SPNAVPLqbt4O
0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7gXzJ41LAV6D6
Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0Hoqz6hbwI
DFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNTtARz
uuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0f
XAHUFPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm
5/fdHgE7D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3
cmrwrzUguJ7/a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBu
T9rl+6kw8FSbj3qHwKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y
2BpnVfZ8DSU9ixyt8itU/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXO
MlD/ZOGg5lMhIsn/81oWMP5qKilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/u
v90fnjZ82vBpQ1CXq8vV5VD4q8JfFf4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSp
UqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoU
eP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMo
OVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynMcNSzKvCxstVUFLTLjplZPwNztWDxMcj5
fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOmZRGIgXYvewOQ+htjlQSQVPtRVwgo
v9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g9TblevUCkSLaaS/BVV8NdWWC
eaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZLsc8HtRHzkr2EZC9LXt4
ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8W/UqMvUHKHSq0J7g
MJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwClsu4jMQucu5z5
HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZz1ch9JPQ
/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPgAfh1
N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+Gg
inF9wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe
3jjveb1L79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jU
kKkhU0EZrgxXhv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k
6oXAC0jnBbeAGCxiJVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjC
IFfUVQKpirVnVg64ZJrnGkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQld
QaC7us5lAaWqTHxtsB9xzkr5AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6R
tuuag7JUPisvAGNdQwVjfxClDb2kAWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBc
QxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/q
JoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lKQdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJi
mvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazhoZ0SschLk86w2FobUjm/TMy3gW0ye5TCA
+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4rE8LKwDpxbLnmifA6VZJ+61pkLgk
9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULKQ7mUyAE15oHjpHWXawNkdpJd
zvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX3KOOqVC1TalujUxgf5qd
EOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKELZegyewqnT8YBj7f
2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1jLZgePz1+ejw0
/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yuv7n+5vrg
98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQiynr
I5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIh
s05qVsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/
gi7EEGYqBLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5l
lewH2laX3a4Hu5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcg
bZIypRagLRXn1Yug+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0
VOoPmZWz96fHgfm8uRo+kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1
B1xTciv4SvDgw9i714Ph8IsbLTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9
EbyrMabKEXCdoXJmAmRPdk55egZivk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH
41i7Z+BIaFO8VkZzDxjjPajg4CUQ+CbkB6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS7
9fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjtrYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27N
ezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82fArjt4/fPn47tAxpGdIyBHJO55zOOf23
8eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHnjT5vBAltE9omtP1PKvjvI93vRsI7
dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjIyMi7hf/u78O6D+s+rAtd0ruk
d0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf7e+9tf9/iH+0HeoV9Yp6
5benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunLpi9hwYkFJxacAFsp
Wylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8bo5sFhACUh3s
7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9SFX0HT0Dy
NOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNpi1ff
gJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUc
TAS4ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNie
phdP6gOW12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4Km
eJcr8gu4urLXFQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAE
F/BbaS0AhoaefZI1yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4
WJkj6SFgn0ePgK/BY4+SEXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjd
vMqREr/AS8vrC1lDISX3VTnhC35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgy
kjLn+22FtW0OZGzPD/5+/h29e0LRzOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHM
iX6y7xIwV9et9a//x7uVGCwGi8Fw+6fbP93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25
i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8CRxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eX
lxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8xGhB/wX9F/QHeae8U94JXehCl/+i/uO2
j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5FxCFYgvFFoqF6Xun752+F1jMYhb/
69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNTkU1FNhWB/J3yd8rfCWJ3x+6O
3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZWK6vwovqL6i+qw7bobdHb
oiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn40gFrWcva9/C+/bPn
m5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHciiOuqyRkAcnfp
mVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhSYWmZIQK0
eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GBvZVk
MD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2Rlsh
vQV5pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn
3/3wh+aw8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV
1V3RlYWzwbczr/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZ
ajgMnpP0DfJ1htwplqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3
Xzs4Ue9cyPWjcPjolY/OnYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp
+Tv7Fqi8pPjIlpMhJS1mYY4KF3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+n
vRwVPxkeWVO6PA6G89cf3th1Ci6NiHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsti
cJZzlnOWy3s+KCgoKCjob8svsiyyLLLkfZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcf
fABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10
Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5SOcjnY/kbV//YP2D9X8xIvguAdvivcV7
izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659tx+F5h+cdnge7Ju2atGvS38Zdt27d
unXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg7w6A/o7+jv4OHJl9ZPaR2WCz
2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9+3vnm5ubm9v7neMsAy4U
8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlISVKaXAkYKO4JG4gX
4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8HaTldBcjgHoZ
xeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG/CAbdN2M
ceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAYA1Il
eZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd7
3i97+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsT
s+HmTUi+ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQ
u9QfDLNME9Q4SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFa
fkM9cPRhUvEg8PM27U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1b
qArEesefyO0JZxOelLjhAb5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbT
NHBe0k3RjkFGR/uF9DKQkz+3rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPw
z3nlU6JTolOiIbZgbMHYgn8bL6VNSpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYE
a4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O
7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/aMc/237mM5/5/MPe9yoS/13teDfl4t37905N
Q01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9ZdoA1taANFuhbpWqQrEEAAAXlTSt5Xe5tP
aj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76VuIPJLbcUW0CJoJMeBNFMrmpsA8oiA
+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5EBPXkQKCIGKDNAWkVVXgMPGKJ
OABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEXrBscJvEN2FYafjGPAdev
8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4TswFfT53vwtpEdZ4zN6
gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYUyB6Z/VXKc7Au
8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90hWx9cmZD
YEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn3Z1K
Q2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMm
S+tmNNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJf
Qu5q+9cf1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OK
P+wLHlPNY70PgHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA
2T/Wrd7dyi95vuT5kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdf
fPHFF1/8bXzbBdsF2wWgM53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePd
XOcLXODC327+rQRGW64t15b/J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc8
5C8ulHQ6nU73B/43eTc14z+8W/WlCU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RK
bUAK4GutKMjNzeUDfwSxRy6YcwJYLMqxD9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZG
bQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjxufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHT
u4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hm
gscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpNoATJHZTDQG/nRGd3MAyTo6VZEHjY
cNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2zj4L2ncturwumROmK6RIY1kjn
xQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5x+4JjtOZvXIiILtJgr7w
FSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2DjN1Dgq4B63haIcWlv
pGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCuV+c74HNlTWIt
iBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQZyj2U9Tp
oOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrGRNMM
63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998O
baa1mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdj
n4x9MhZiYmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUAr
WtEKIttFtotsB6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2
oW1C2wQ4dPjQ4UOHga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0
aNGiRYu8Ox/tO7Tv0L5DXrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90
rUAMkUZ41AVli2GxshLEE+GlzgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01
C7QFak/ZBnIT+TNJD9p5MV63FpRp2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWflj
b6WWgeSrSTnpl0Ht43ph/xVyxqccT54MLz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBz
YY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wE
hg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcV
papgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP4y5AbFzCgzefQvZcY520L6FswZIH
O9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP+Nf0PubtB47H1o3SS/AdZNju
mwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/77BeIHhwcGPQIevRo8rJH
Czjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9bFU5/fGJSXG/IXF9x
pysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0GXWlDmLYd/Lr5
l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok20RwNBCz
FRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvWrFmz
ZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7b
e2/nfTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDL
gJf/xZco31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAg
cUHigsS8Oxp7w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEm
PEUMALu1BGCbNIwaQBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De
7uXeW54gjwvwL9gP9JmmZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQO
fXUScEU9D/0e4vbGJSZ1BfsP9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9Lkem
gGd749c+JpBidVk0A+c17XTuGbB6W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I
3AykW/IE3XqQjlJIag5Sc3FKqgy63uom9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEi
zNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ
4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQamY/VOQSOfKjerzIXXZXMbPt4Em8qeKLZu
I/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8ToakfInHM3tAzoDsMa5seLEzW3/h
OKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1odT4SA/IapQzLLYYmPqablie
gmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpuxGh4UTLmyNuz4LnE+ytD
UTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCrqcmq9TuIkbNW5XiD
7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWdE3dO3DkRXjR9
0fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA0tJLSy8t
DZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY/Grz
q82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQ
uh3rdqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj2
57f3r5cjdHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99
AHRihisctG/VjfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24
bw8wlAx/FZIBokjWw5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7
mgSZc9NfaVHg+Fn9QUsExaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKr
OTmOcKCiPdD5Ocid9A313cHvcPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0Vd
ClJ70UWuARg1kzYd1A32fdafQZurfs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbO
bAHTaK2UoTDobb4PfQUIEnpkh4DJqi5TB8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0
j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8FazZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa
9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LLgJnAHXHCFQupG9LfpI2CUZX7jvo2P+hX
yw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHFq7fV0wSEFw701i6DlG760ssMvh/q
fih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSVxz9CRp+UUq9uQF3/OqfKfgV2
P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZhkDYno2ruAwivrr9kOQ7S
aO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z774cWPJsybMlz8KN
oTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuXL7/PEWcFgQAy
JA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C1EXzFVNA
quY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ8Iyq
vKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Y
y9s32Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE86
5Ky1j8vqDbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41
PeOgYkbpj6MfQczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1
OuRvJt+u1RO0OtlbdWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/
d35is8CJxGuTz0wE81Pz4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7J
DbMrPIuCjIPWFbcLgtcN77NBo6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3
oPj1Mqsj08E51zZZNkO+7yNvBdnhdpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQ
ddVx3GED23bPbTjAOEAX7+wPzuHKJfMsiJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1w
xYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk40KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWho
uAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtbEK+kafpToMyV4ikIUmG+0caDKCaCJAOI
EY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyDYUqxoWW+B9cM+9eZi8FnctUHzaqD
XFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry+ta/Gej2OLras8E0UnqrdADj
OVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz6yvub4WcMzHnE76E1AI5
g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHOZ5oniMG6IOUaMN5Y
wpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhPaPWMS+HhPk+X
vS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDbBOdKW2PQ
5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhKiocm
b1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbK
ZFSeVT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7
Ro8AV38IqOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9d
fHbxWbhQ5kKZC2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6N
OP/xxNlhz7W9AKmYFC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyAN
FJFiAriWsFC3H+TG+hf6W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8
Kq0Gj4dVTtfzALNX6U7VC4EcSZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7I
LVDPsdSQAt5TvHf5FgaPaGOUR18wV/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb
9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZTQFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9A
pBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFlOGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+f
IMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhqZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6
/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0iGmihBwJWmM1g7Lg/Ez7WssPWi2a
qd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E18P/Efi9CLgREA26guYSxsXg
fJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjbgPO+rBMTQW7pKOh9BHLL
vS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5A9D3MW1wDQNrAfOt
2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3c3Nzc3Nz+yPe
31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQbKK0GkSAK
aN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdAd95z
nXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3
RsI3ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd
5PFyMshdRbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf2
0X5I35bwMtEAOc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRb
QafI6+TvQVsjYrkJ4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhh
Wk/lHmgtxWeulqCOsRfU7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0
CwHvj4wVHSngv9xjhn8zuN3h2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skG
heG635MJj9aA9YTRqq2DwgWL5gZ9D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5Wub
VoOanDkzoTME3vCYKY0Aj/xyTKWv4c76t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5u
bu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQ
MmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1E6H02Obtys8F342hUb71wVnN/2WR5SC2
as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWnP8mQfdTxOGgP2DZnXXFWAWePzA5x
34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y86+t4DiddCJ9LmjbssyuD8BV
U74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3AqZr9/gGRHVRTGsEoqe6
2fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7IU28/SKhHWgX1J9c
HcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPHzPYgxqSPFFdA
3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55IchtlCRugS5H
t1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT9me1
gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy
60UY5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+r
KcCH4pC8EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db
/xbWVSM5PaUGFOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb
2QmgdXattvkBG/Q3pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5T
IWhbQDOvMFB+UvIRAerRN4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NP
kIzSS2kSSEdERyJAVNJiXfVAOS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRS
A95+k7vF4gOJdeJfvTwDKSuevH14FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keY
wdnRct0WCFnPk5+lRoKjq2OwVhaUunIFfSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ
3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGKXJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+
cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYB
y/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4BWjrRIDTCdo1Vz+zE7x6eNbgOOT0
zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBtAVT4oOzXxVeB7q5pZf6ScLnP
nfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5ubm5ubm5/zB9OnHVd9P1M
/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnkBHldQEDAXXBtdHg7
KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7VBZSwYktrXAd5
v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV4c2r+IOJ
seAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bNIAbr
J4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVt
FdVkMDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAq
qowFsZ5BYilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKr
sbpdbQSap3ZDPQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZj
L/Cp4CNMEuT+aM/nGgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSe
AvMh85PU3dJ9cAyU7ruuwdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/D
Ybjz4m47x8fw9PWd/XeiwedMuWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDi
fKbuhZGXRkHNslXuV6kF8jVpi0gAsUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8C
piX2S2C4aCgpfQnaGtWTTWDoFJpaeBSoV7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pf
g35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8Tn
UevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAWjDet7XKiQVmbGpZmAF2kTyvfB6D1cj51
3QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Qa2PQbQFXvN9Rv6GQ6nRGahLEzUge
kvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOfX8Dp5dyozoaURnGz3kwB+al6
jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6FYon6A3SeSkIFEno6Azi
qtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2agNBLNyQfSEKmBVBqU
h/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjBXssxxTYQXGWt
JazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0vC9nTc6zp
CyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx+RdI
JdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ct
Zyx4NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUA
jk9yK4L4QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4
zT9BVwhcjyzhEd/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50
feu8DGK5tlxYQLojjRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v
7IHEZm94NRWUOP8evk3A97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBn
ELw5X1L4CvDN75vtdQJMV/QHDTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAA
jSR/+QcwWHQ6OR/oBks9yAUtUPpaGwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQ
NstfSdGgd0qHpC2gltSechDskprs+glEGaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9
ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9vLqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7
ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/BnuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5N
bwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1MavikIdalHnT/Qv979gEdOTk5OTg7U
21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqqMGTIkCFDhrz/D5BVq1atWrXq
n4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFyitsm2n1AacAGMQNYS7w4
BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3FHSbfBJNRsCXRpIe
tENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+sZ9LTgCYuV2pb
eLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C7yGWwdlW
8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVokvMy8
d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEg
SvOKWSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxV
x6gXwJUp7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71B
mo2TvuC6Kt5KPiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/w
htyHuhH6mpBuzfox2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D
5qOVdSWD64pYrVsMhiuGXVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYU
WVBkAfw85ecpP0+BOhXqVKhTAeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfI
wAoDKwys8Oe9/l9NXBPXxDXY2XRn051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt5
24ufLn66+GmoVatWrVq1fn/5ChUqVKhQAc7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5
X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byc
zn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgAOHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2
FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8FMR90d7pDfr5+qOeHcBpSu3xsi9k
D7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTFXl96BL6i5BjvgqB/qZxO+hDU
yXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwnDGvNd0AqqQYaRoLutHel
4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TPATlNFywNgKxlb1ak
3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXSKoBI0xJwgrCK
QcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaCuCS+YTuI
g/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAagptij
aSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD
/YCkKj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og9
6s/AH0xafXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYP
t2BItSHVhlTLS2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u
627rbuv+NgH6rfjlB5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgs
BovBoC5Xl6vLodTZUmdLnYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkn
s05mnYTmC5ovaL4A8s3MNzPfzD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225u
g0unL52+dBrqUpe6/0U9X058OfHlRBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6L
V1cSJsEvF/cfO/McTIcNNvNXoFUXTVkKRBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA
4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3QvQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw
1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao4AE1HzVy1fMB44rgnMiKkNLGttZzH0gu
r/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxvMgtZfCDjI8u57J/B/tDjc59KkPzG
u53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ceDf0AXNUdDrsK1g/eNkq/B4W+
jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G3RFRVGsGpsVyT3kV6CtT
WP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7NbhIH0hWu36xY4Njj7
u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgugBIkZFEUdFfl
nuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTWSO3AMFDq
RjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqurwze
H+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38I
fR36OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgnt
EuD2j7d/vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz
2cB5yXnJeen3v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJE
iRIlSgBDGcpQ4AY3uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwY
bHq06dGmR7C14daGWxvC8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz
5syZM2fynn8y9snYJ2PhZNGTRU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfh
d2fEnRF3RsCuSbsm7ZoEL8a/GP9iPOx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/H
Hx5xlg3yao+B0GBnBWOd21DNXCm9UDuwOh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0
RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhCFakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SO
O1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73W4D/EuMFwxLIrKwv698UHDuNelMiOFMd
Uzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lHGMHw0KdPwDLIDbA8M7QE61JTTWM9
yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8iwZU8f8UnJ2yI23FQb9VO+66
DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJb8GwWVfOcBxMM/UHDCXB
Mcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC9HetAhGgmoU3uJpp
jygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJKjnxcag5qK9FQ
GgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCeiQ9FTdDq
80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DEfENp
AiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycv
gfo7SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/E
PpAfyY/kR6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESl
v7//5I7JHZM75iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ
8Olrp6+dvgbJ0cnRydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpap
WKZiGdA0TdM0uH7j+o3rN8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95
PvJ8BD3X9lzbcy1ImVKmlAlXGlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifK
J8oH3rR90/ZNW/C/4n/F/wrk5ubm5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1
axAREREREQEtsltkt8iG++vvr7+/Hi71v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1Dmo
cxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+I
SdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPAUcfx2tkd7DucJZ11QdbkSvIbEDvEEhEG
ZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYBaXipVhVc4PNZ47s9N0GwpfWhgR+A
7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk131RQLym7da7MA+xXNyxoOak/H
5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9Wn91z5j487/q47qOeYF/o
vcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjqlq8c7DEcrHbwJaxK
3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3QTQTXNe20+AI4
Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6VdwCfiqigK
an01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4VFd+
JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyr
pXbgHWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBT
OcjZkDtM1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0
I/Iea1e1q9pVkFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/
m1rxbqqH/YL9gv0C5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d
+sfLN3rW6FmjZ5DSKaVTSifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1
L1BxUMVBFQflXWC9G9GucLnC5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1
nPWc9RwkzEiYkTAD8uXLly9fPoiZGDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rC
MmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wp
luiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKfs5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0
rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpnlk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA
/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWBx+QLm542gVc1Ys4nrwDbaKLlGuCq
7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw4nXSw6RJ8Nh+6fMLJ+BZ8uMV
D76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8qcjLfd2C4rd9mHAq3H9w7
cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y84QeVd1awlB0LxRsU
eVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwfmKf5VwXHx/ZL
ji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt4v2R3zIw
7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcBK+nc
BT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0G
jhQhLEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb
0TaiLTyd+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFx
cXFxccBBDnKQ/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se
5S6Vu1TuEtyUb8o3ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU
+/3VFyvFSrES5F5yL7nXb7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH
5ZBySDmUN3XJuNW41bgVTMmmZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X5
6wvL5oHNA5sHQuonqZ+kfgJvD7w98PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfX
Sf7i+TFo5lE7uq0C525dfn45BGxeru726lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZr
N9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYe
p8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GXgcs3NdjSDoylwvsWqg7+HWpOKvkLONdn
f2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36CuxHIroWGA8v92a/theHZwUuRV44
Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZZ59+Gbyc9mZRTEeIO5X0aXwW
2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNcYUIv7kPGzuxo+4+w75cj
B0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qDT2vfix4lodub9t5t
qoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1OrdGQOrKtFGp
/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2MmKEVA22Q
JrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEiUCSB
WoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9
oNzccnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm
1ZtVb8Le2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCC
Eu+//tk9sntk9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m
8ZnFZxaDT0Ofhj4NoerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pS
VamqlLf9VsVbFW9VhOge0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c
6Huh74W+UCy7WHax7Lx4745Lo22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269
GErZStlK2SCqR1SPqB6wK2ZXzK4Y4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G
4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk
+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNSn7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1
B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687
wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJTEl5Nva2/ehRelrg974YFUl5oE+kP
uqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLho60FR3m1jLYPlDjDFIMF1IJq
D9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5qqme1xawVLeGak1BHem0
5Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3BZ5xPCc9zUHZv8bji
/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfBccrxNH0PiAeu
gY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD1l59S35g
oXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0nnRFZ
QF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUs
mD4xfWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1
q9SvUh/23dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39beh
ZL6S+Urmg6Ldi3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk
/ceLSopKikqC5NnJs5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/P
fJh3QfFurnuthbUW1lrIb444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/
6ino5ub230S6dOnSpUuXhKhevXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2x
rlhHWk8orCuypdQxSOyS3fH5Xbg/70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0C
P6PPC/8C4H85aHrIS1AXieZiOqirUs7dfQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl
5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhD
JOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSnV5IGZ1ggt76H2fcc+B7yDPD8CuzdrOus
lSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb0KbLtbQUoI2qF7XBMd0+yzkNxBFR
T+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEduB/IFeYBUFaQp0hKpF7BeMtML
HGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+StCzQJct2XT0wDNJflKeB
Okc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcMQveEhgRvgXyDw46G
F4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6roHQi9b6ieDa
qNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY7mzg6gOu
yfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFloKR4
tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX
25fbl0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c0
6aSTTjrpvGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQ
nZtwLvDGr2fWQ9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfF
nthIeHr3+fzodWC+73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3
oJhqHp/pwGPxOSuAsuKgboB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2f
ptkGgbVMlpH590FQm4oFiz+El8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKi
XlHfBa8PJfaIqwKJ51M+T6oNjFNvij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGC
Xti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRHykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5
Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgrspZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoM
aWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZpM1I/DDKL6KtGwMuPoqcnnobYVrFfvtoB
nvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3AEmFpaA+EJ8uftHpogLJSrSIuQnIu
ZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYmriKc+fxCiUsfQsycV7WjNkDG
XzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7hnitgXNT7GL9AzJKEOYkx
4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA3GZuM7dB1biqcVXj
wJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR4EoxsA00EouP
guCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4MtkHdLaKPi
N+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZlDJO
Qkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7Caw
TMwVOiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADy
nllQrw3KAPE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdS
V7kD5kDjrnkOxOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJg
elkvq4CYZp4U50F8L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMno
pyFq5YuSL1aAj92xxNoW6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+
BC8evT7+WoHYbxO/i1sBrE0YoC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasP
AqWJOl6eBLWB8qXNH7THlr3yKuRwh7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/oc
dXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/uaP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumk
k046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xk
boDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh04lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l
6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8dsaOFAit3TZrlxxgn5k7Z2kH2Hbm
quSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGCcSDzrYgu8PDuxXmXdsOTUtdK
XckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNez2McA/Gd+EmtBZ5IVybP
F6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0ZolYBba2ts9UfxDV
zZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RIMN6XsfIm6Iv0
CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gBGGKj+A70
BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7ymvW
5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghv
AQGf+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8
C94+cV5njiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARF
wqfxzTP0HgF+Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazv
g/u1Z7OeCGKpZrd9BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3e
wgwDz/svyt0cDfENdgzb5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQR
z5TmELDaUdg3E8hA/ZlRBxLPJmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4s
QRaQzeUd2QtEJfZxA0Q1WuAC+aX8SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2e
Ua8EpsW4LzeDvGYW4zqIQOWxkg9kD3lKrgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7M
ZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc
0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/WulpFOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M
/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1CXgyePq7zwHNzJFiKih3lQvqFtD8
NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1iGWAz0WwnbXFBGYBadXClW7g
TnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olzwlev6qeMgkznLc2LFIMe
QY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs7FPk88fg2pOyWZyE
U112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwqPBLMhuYQYxEo
G0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUIPDNeToo7
DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3ZmXAQ
ki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssM
ohh4X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN
1CxaZ207yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2
ahrRoGzSNGU/UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ks
n4FYqnxghoP1pvWa+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUO
MEfIT7QvQD40n0sVon6IGRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZ
b/mN/bvDO5100kknnXTSeZe8deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vf
gFudHt28nx9evHjp++w+KGuseTPkgJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJY
ynhISEo69WIN+Md7NvtOhGw9slTL1ACCy4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tB
OWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjvGweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDg
XFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wzZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3i
jTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh200cpp9TMQEcogMRm8ZfV2ehEQm6gi
ioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CHiCAEmDnN3XIxyAfKCh7zX+8f
3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPlTRDlRX4RCOYnZlGzMYhZ
vC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhDbZCP5RwZAvSUuc1z
IK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPLuyC/li1kTpDH
5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9l52iW4Lv
Pft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ecMlvd
LHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDE
PCWArpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vj
onUgw4KMoXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCq
gzvZ+6GxEMyNZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXI
LcwW7cCM56UMB1FQlmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6
i3CQX5FfmQJmC6y6E+R483OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ2
05AJIHObdrkLaKxkkKvAvGBUNB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUb
MyfIieYrbRVwkm58B1Qhu5kBjBbmA7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqr
lhP0+fpTWoNSWASK3CDK8In5AYjsMqv5CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywF
nmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5
+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWs
XbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGTo1AJeB6RODHqI/C9Zw21Hof7616+
ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0ZR2dJ1D+E8hern+v9FaQUcVqd
g0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx8CCwdwp/bO0PCR2fjH7w
Hlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeBvtBcDuIjkaycBCVa
zab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBGUT4Dacqi8iSI
b0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dgNqIUW8CS
aOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNaSOQX
m0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh
1DR2Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxV
EoGOIi8PwbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9C
oKeTTjrppJNOOm+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dG
ZQTfJq47mj/I0wHdX52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3P
TsPFK5e7HSkKvn1CS+VtCKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC
9eVhoDR1+RyU8uZyMQrMytw1pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu
3/f9RoG6VPlRuQVmoNR4CNYEW3bbaFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaR
BQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWLpaj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds
1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsx
sM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kYLJnULepokCbVOQdGjJzFLTC/ZiTrQD4w
w8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCoJexKJWAB+/kUKMJ88RLED2KEmggi
UviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLtApYUbbPPSZAVzL3KLTBe6qXY
A4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHmTtDvGkP07hDT49X0pJLw
+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwYbD9nHwUJW9yTExtC
RAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzpz6DInBKrssXA
o9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+v/qsUGiz
st2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJfGq6p
Z7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ
+iOoiuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEX
gLHETDYvAhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbY
Wqh+YDxx3fNcAPOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WC
mQvIzXIRDto1Zbj2PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7A
LiqDOo92Sh3AK+clnQfvNM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJ
IE7IfEpRcBxxDLQvAWWd1sh2CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTS
SSedd8VbV5xfdo4Od24Ga7Btsr0bhIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSCl
V0oe5264Uvr5ugO34U71pyOu1IKE2Fd1ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/Lf
tT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZ
rc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYHgAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2z
Dcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcpjdPmYrA1tRRXHoJyVOuk2UDV1Bra
ObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1ZXbjLrhWO4emvAJvZ2+Qpyt4
i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFyAiPlKtkfSKY4I0EsUpxc
ArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6A8gysrCoCdJijjOX
ghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0QmBZpPhaLoB1
j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tfDXJC5ltZ
ovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Zm0DG
I+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf
5X7Q73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7Hs
xbIwYMCAAQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fv
ZLLc/5383X76pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUG
Yh+4/GKnwpO2Ly8oF0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjS
ZqpjICXG9Deng/Os2TFhDuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru
9wYgk2wuQkBmkCVEZxArRCk1C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVM
XFfaQ8pUZ+2Uz8B9Wd40B4LMLqLFZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Y
m+QcszlorbV26gegVlSrq7VAGaOMUCaASBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV
6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoaKB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7m
o80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCUFVVFQaCW3IovqFYxSf0ItKHqYrUsyBSz
sugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5+Vz+DCKKcWIyEC+uKs1BPaw+spYC
z0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oIE+QB2cX4ESgiKtMElCxaDa0C
GPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX7EMhx4pM8ZmOQc5zER1C
/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC+6/yU8JPCT8lwNo7
a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZCm0NtDrU5BJ/7
fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/GH9nhP8VP
/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3Xdx3
MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9S
Knq7JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs
/KEmE+Mh0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7l
nOWOhaTaxiTmg7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKW
u6Dt13ppy8HSW/tEk2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9bi
RxC5hUc0AxbwMeuAkVwxk4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPV
jWCZr23SpoH8Ue6iIrBJLhYlQDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGgu
NtaCaCf6KQqIzqKLehXwECmqgmWJZa9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ
0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWfA/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46C
rCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JC
vYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQlcTjEX0rqkpQA3jNGY89OsLVUp5vX312g
Hog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7uLi4uLg4GDp06NChQ6HBtgbbGmxL
az/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yHDh06dOjQAW5WvVn1ZtW09d27
d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZsmXLlmnH07Bhw4YNG8KS
K0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW0Ug9zj/jXcsVkz0m
e0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P89+1SKzh/ZK83
1c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8DG70v9H/
Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zcM2nb
/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPa
eS4VXdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G
+b+bt06cvYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2w
lo6dCjxMGhijgbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHg
GeEpaXkFkQ0ibyrnwPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc
1wYogRBb90HR+2XhyaNnAU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYu
MRVkLuOq+RwMRa+jFwazES3NvSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5Edg
XjevGhVADBRdBKBGq04RBYpBdZqDfGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZ
Y8C61dLGEgLWbBZpDQVrS0sRa00QBcxXsizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU
3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqHgTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0
fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkO
WmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3kjuD9ytPkNMKeht3jpRPwLUt8de4
dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8hiF/uPk0CRPZ73cNZAaKPOJt5
Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu237f9vm3akPP8HvN7zO8B
P7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFjIsak3emPyzIuy7gs
adsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL07a70OtCrwu9
oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1etTLtwpJ7A
UxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHvCnz3
P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68t
YVvCtoRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz
7c+Vtv7UqVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2
IgwJHBI4JBAOTj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nu
JrubQK21tdbWWgtTf5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQ
R8BeS2dQ8plrjPIQv8JIdhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs
/hkgx/mAXpkTwV5B3tMbgOXXpHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVb
CFJOx1gUK0S2cE12noRVt9e3/rInEJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHc
S32HeQLUjBah9QIxVpRTZkByHufzxHbgXqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzM
VP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHFpiQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7ayl
J4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9GLTmPziCnmZOwg7FZH+ndCMpLsU3sALW3
OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQiRMWELPEbRqDsp4zLARVV2dyErR1
yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQnBC0NjQpYx0Ic2f6JUcVCMsa
USR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnGfn2mezzoQ71RugnmV8YJ
/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1cTQDo76saFSH5HuJ
++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh+s+2jZC0zpOJ
qSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd6naq2ylQ
PlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2WbusXYbY
ybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/
qRfW0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D
6Lmg54KeCyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RM
q8j9VX/4I0rPLz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6d
u3Tu0hkyfpXxq4xf/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0y
N8r8D/aNaR7TPAYu9LzQ80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJo
PPcbDwnT9edGMmg7bbuSBoAc5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2
ik8gAFyv3U2Td4ExUWmpbwGfoRGjbN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH
5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRYZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36Jf
B5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrKsoYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA
9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRNdFR7gznS3IIEsU/8IoqC+qk6TpkKopJo
I9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRXySdiQElR3lOmgTJZOSBegjpIW61t
AeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s20ApbKlhOgBatfaglgzZHLaM1
BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LLQ/zE6LKPvoaEQbFfRD6D
JOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjnPa+9u8BY4A1zjQbD
Ty/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSPy5GgvzDWeDeB
/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157svUD0G97
uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1lKVlK
lgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j
7Xd0jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqN
zx+RWnF5W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDB
QTDuxbgX416kTWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq
1t1ad2vdhe2Zt2fenhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusES
yxLLEgvki88Xny8ePvf93Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9q
p//UOP+dPd+2g9c+ie8bncAcrWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuS
D6iRxhmxCDIe9GsQOBEyfpjhczEDLLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU
6BkDPPFLIGxA1slOCRneC1zkUwiUbfZhfAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW
3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCyy5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD
1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLkeGKc8VVqA+EndrnwOcgFF+QKUFswTNUHM
lS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5zjxi7gXZXXY3u4I6Xp2lDAKlhdJG
1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9LF+D1lzZpuYFrYg6VYsBzUer
ptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/Gaz97HvtOUA2MCeb30FS
nleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBYO1teqSr4Tg+wB5+D
kFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7mnll8JmT+Ifvs
Qj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8Ck0G3+CA
HsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6itv2n9
Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc
7nM5bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVe
EH87B/2sPCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P
/Zs6tJ1aqUu9cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+
qF3qlI05xhxjjpGWSP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/o
mqbX6GbRzaKbQb6EfAn5Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2
fVM7/afG+W956/c422+GR74uC2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6
X7OM38DNKEuXZ8HwIuFuOzMj2E8rJQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk
1athEBn90OE8BhmaOeoETIXkCgGVvQqQmNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL
6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7vOTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro
0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYrOcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKw
uCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj84rX4ECjPeAaA8bNsbGQA85ZcIzeC
fEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1WfrK0D5QhujnQTlmvKTcAPjySqO
g/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0xWisPrnHJ2ZNagvkemzzb
QJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXUE9R62g5bLdClHGgm
gtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsHgWuwMznxIljz
q3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1MujnXf30M+B6
qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepydbm6
HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/B
pD5MGHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3g
WOFY4VgBX2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/a
a0zFMRXHVPzn9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKV
q/+H/hqda3Su0bl3r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7
/FG7wkcLHy18FOyV7JXslf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83N
NBduTb81/db0tETb08PTw9MDyhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hO
mHJ3yt0pdyG2e2z32O7/ej9I5U399F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778
m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56+
+CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Coyavubi8ENKO62Ruim2vjEgaBry1koN4clGtG
eTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4CLhu3em8BXElkh0uN3i3aPvjpkKuKyEl
KvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzKOibXa0iKTd4QvwmeTH5W79EeMPKJ
vNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqAedzcb+4AJYc6QKkIyhpxSZ0P
8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2IoCLdyGx0sBTTsDUA8EIvp
AcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL7Eftl3weglWzZfRp
BepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrijXNWSZwA7GWd8
Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwIcyXIEyJU
U0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+EdA+p
GPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWi
elGFb9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYib
p0Du8jxKHA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ
8/nlMMdC7ks+quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61B
A8RhSMojlj5vBi/8427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGU
MWqDskmrKN4HsVM9LU+C2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZ
C+p1MVu1AFk5RFOQeeUDYoCuZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPA
I3lTvAbpL0+YS4DmopQoD8Z7MruZFRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSB
MkT0sihgWo1OnhVgmsYl8xjYfrVb7fNBy2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkE
wm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/vWmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1
m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5TT/rLATmSnfhlMNgrSt9jevguW8EEwfu
r7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczKme+a7cFe3FHA7gX9oMeQW0CUUbbK
OeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmNCa5NYIzSf5UvICi733d+pUDr
hY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxxyS+ddP4f5K0T5+wvwpcq
fSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEpZY1FsjdoCeom+0Sw
vUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeBfd76juYg5tP/
dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD4DnBHPaA
3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7nAPb
YNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkt
o30agfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCr
gtaaK3I/qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39Lmy
PphLzETdArK/+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g
6my0PXoYxDpe9XvRETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvr
yOD3K8SfSpwSmxPs7/t4rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/h
wGUQPyuxY5Iv+F1QgyyT3jic0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdf
zdu/x3l/YgZXFsjRMWRtJsAvv62QzyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmU
ehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t9
4B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5lr/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpH
nb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0f
ABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuTrREE/RxeJqcDAvSwatn7QmDTDD9E
LAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34Kjs/924acAv98wYMzHgKf4YHf
h+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd9l0B6miry+EPNLDN9fkF
zHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLaDyAqqweUPaBFWSLU
7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSywy3zPpYIn0p0/
/kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZApnyh+YNr
gNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdUKuQZ
hJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTm
Zr+xG4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc
2gMc+wNq8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHU
os2WbaFAgaxZKnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7
Y10a8CkYlc313pfgXZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVo
CKIMHxotQTRWc1IJLEnqMl8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0g
bHKdeQoMyRf4At+IIuYo0N77r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKm
A42UL6wPQMmrxml9wZigR+AFsxUf0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N
73PXREiZEf86NiPYrtun2dqDvbO9t+MI+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ
2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiP
tHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9HYPAG+xclLwFXKdTmiTaIHiCfxP/raDm
U4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukUAgpr27VeAHT4u4M8nXTSSSeddNJ5
N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fyJ0ja4rE448F0uV7a20H4WMfD
HD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZunnGgaOhfbX7BiT/fHmc
awd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9Arl0ZBhbYAA/tN5/e
ygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZVcmjXwVbCMdP/
DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG2jFrfUdP
MNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkDnJXA
W8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1ja
akPAPdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2
zHbbVgosIZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt
2ggiUri9JcHdxlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaI
I0aivha0VcJKELg/cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18
miY1AJvTXtDxOTjj9B7mPgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+
QYmAuENJIdom0Bs6Zxo3IfmeUtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE
7MlBOzz3IcvH5SoEbwTlgqPx6/ehSA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwG
fbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwFtJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2v
Qdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYiJ+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/S
G/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uorn/EgylrzKQfBLOuNdn8JcoyR21sDjFtc
NZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw8Kw1LslvwLPdvcubB6zzNcU2GpQL
SnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3Qe/q6ZHyK6hu5bX2K5iFyC0u
gN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0fPXKuRN8WnuHG8GgzbBU
tQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt27QnIPYaXykVwPOV
9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkBycoMQ1A2t+tZzM
A7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+83jrxNk4
rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZvC2eS
2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9be
lrLW+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGY
j7QxtrkgxxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kO
Zi1PG/dVwKG2UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaK
W1aCPty4Z9jAU8ez1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRR
E5QzYGYy7+hXwLmAFdICZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POM
vGA2MXd4J4MZbT4UA8GMZIUYBpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkp
d8lZ4Gnsfu2dBWYrJcrwgHWE9bTtAehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2
NbBJyFjwCQpyhx8G7pufyxUgh+pT9SpgFvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65
/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aSTTjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J
91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7NgkiMgdvlhGQqXCGW8piSH7pMynlNrCX5bID
KJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5wt2eauyQUexw+uNYT6FOs5bS11yHX
uOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF9o1PWbBp6jTVBsoA5Tj3Qd4T
LY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0FdhpcGh+qb41gXrOR+PZQTY
7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIXSBga/8Gro5BUJmFH
bFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUOzKmsk3fBXtZ+
zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlwPXdmSAiH
lPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6Dczn
5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8
YVnA1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYk
gKW1vbHtKGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoB
NQPSvgCW+mGTp0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2
qz/y5//t/Lvj9d/FlsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Wh
b0nZEpKijXKvTYj5LPb7V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzz
dSoLIGcP/17hU0FL1AqpX4HlolxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3eh
Wpa84P7B9TppJogcMlovBfFXnoe86A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zP
QQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/
bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyBKXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5f
NXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yWB7/OGAG+eXz9/I6B7Ka7jY0g84veamfQ
tmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVnp58WuPMUnJNcj2L3g/s9V1nnfNB3
efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5TeSpjSEERlYRHdwWxDOfEL0EyJ
U6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cKaKiVtBogigpFpIAyR2uo
HQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7PcpnrE/mI2VGWobUD6y
zrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rthBbgPuo6l1gT
3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhybkXYh7Hqq
66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0FrBq0Z
tAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafk
PZi1I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/
dVVocLHg9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+z
YmCba7VbY6BQ/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2
z69g+HrsKZ3A+MVVN/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwB
xjf6e/IUKM2VetbS4L5mjHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW7
7ZVDBz1ZV/RPwBxknDMWgTDN++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FE
zayOQiPAf6Dvr+FfgPmDPsxZH4z3jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5
x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2rQE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBP
s2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXl
YXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9
t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv2076tgJzjTbMkRsshe0bfKq9u0CN
i4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3QsmXLli1bQrPszbI3yw4NGzZs
2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rpabyr8a7Gu2BO8TnF5xR/
8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X7fDP6ue3y79r9127
79pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3Sfn9a7tNyn5aD
8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/zqzeNlz/y
5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpKSkpK
ggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v
/0nI9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJ
AAGihHeKWhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0U
OBIta7RwsOfR/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeD
tOnVvNPB2Kt/7bkGWjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNK
guOc766g8WAbbf/eLwoskbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+6
1fIleGaaK9VmYGnqkxBYAqy/+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u
8SW/hLCkLPNyR0LIjvCh2QMgZGv4sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6f
oVLWK+Do4bcsXAP/+yF5s62G0DZZRxReCqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DU
VsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTW
BKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5Gxi9PB7neFAKyIJmHRDzucVs4KYw5Ufg
Kebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+4jz45LBYZNS7C9TJ+yfvn7wfwh6H
PQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOflPqk1Cel0oYsl15ZemXpFZh7
du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF5WHFyhUrV6x8d3pJpezF
shfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7SO0haYnOuiHrhqwb
Am2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3funJYIfvTRRx99
9BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym/UyNnxo/
NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue7Xi2
4xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k
1QhImSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv
5XFQchCuxoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78C
aHVjfkjpDbKee63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzO
tRa0Btply2VQY+QlmRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauP
tLVg7W/v6jcXxCD1pqUIqIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5
YQwH8R6POQjGfX23uARKqLW9zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1
+KutAK9ntvMyeGd4XiR/BpwxJshPQfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcr
gAzgidIe9PpmG4qA0Vz3cXcFW0HrM6UocM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/
YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYyHNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6
vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCoZgG5DZgkXeIqiMqq1/4tiEuWamY38PWq
jfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmtrFZWp63v3LZz285t4cOPP/z4w4/h
p3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDoRje6/etOMKkXWEuoJdQSCt56
3nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8QcE6Hqzqo7q+6E1RlXZ1yd
ERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Zb5k0/SyusLjC4gpv
b8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEHbGMb2/jrNMrc
KHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou67iswB3u
cAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa82vP
rz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvh
Yq3bZ17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVK
a3FJ+wzkFHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+O
TpAtMdvsrGPhnPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAX
cqkBiB0UUh6Dplm+s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXp
y10aaAlqe2Ul6C/MSPM8WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOc
va19CMhoqYrOgFUGmH3A1ds703kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtz
zDCIa5b4fnJW4LnxUi4H7aIWYz0ISoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU
/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVN
L8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAnuGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq
1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9
qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKyFGh7tb3a3t+vF+fFeXEezCfmE/MJ
DDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+svy63ZYlliWXJm283s+jMojOL
gredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9+fXl15dDl2JdinUpBp/7
fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5Th+wf9HzQ80FPqFih
YoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jReaE972r99P6lT
A9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoVK4jJYrKY
/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2NVxDw
je/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQ
hxA98FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui
+Ly05rWVhcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXs
q/0OgdgssmpfgTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz
1NRzgG2pVkWrB+rXVqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7
bPvWrzlY6lg0bQtoxdXb1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7Uk
qAky0psL5ADrCdUETw33JiMXOH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2
BfWu+qPlfZDzlfFyKzicjoP2xiDmynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4Jyoo
BsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcb
oSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8UZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby
/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVLlyyFKturbK+yHY7PPD7z+EzYennr5a2X
IcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyBmJiYmJgYuNvzbs+7PYFlLGPZH8uX
+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E3Ii5EQOzi88uPrs4JHdO7pzc
GQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+rT6rHat2rNqxtO6md5re
aXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaHbQ6DUudKnSv1BpXE
VN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7vWq9ZxmYZm2Us
TGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P538VbJ84+
twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniGewKh
8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIz
W4OsK8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG
9N3eSE89MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxX
As8+d0XnPVAfKTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1
QajWML8R4PPcZ4AlAFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYj
sERbTM0Aa1fyi2aQNDRxXPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQ
njtofuBN8PfYuir5wbJFW6kUAREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5
BpT+ahl1KhhFZVvzInh/9YxzDwTKskXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjF
YKzXW+sPwZbfOkULBLWlGGoZDXo1Y455AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeber
Ghh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMqk0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2
lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFCRwsdhenzp8+fPh8GMIABQMdCHQt1LATd
5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT8E3DNw0HhjOc4b9fn/o6qVvTb02/
NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN7fi2+mybv23+tvkhpkNMh5gO
sD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+1H9S/0n9JxCSMyRnSE6Y
cnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq1KlTp04dUMup5dRy
/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP+DN/fVP+3f6d
zv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4sLbSrzcqe
oNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+zj3SD
4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5
XtkO7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQf
btQ49MYuJ3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6
geBQtwV+ACZpVn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0Wrp
wBYwnJWXy8XA8LMpxJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALe
Fo6DZtITtH0gf21cYdFA/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TN
Ur4tBOSXjJuMpUGP1qoHJoAwWxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALK
WbWJlAmWry17jCYIG2aNNPQCYVEg3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9
ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsDdcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4
WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ecOw60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A
9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5DIx4+73j7134u4d5UNB/poJa1X+1RvU/
VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/lf9rrGhT0n+DIkSNHjhx5DDPOpAph
4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0GL8+Obln3AHSsWuP797tA7vmc
VFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj4TUQRupZ+kLQGgjT5MXA
VD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19lf/R10D/mKXE3xN4o
VqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNqyxMWBaQk6aK0
BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUHJgNoZ/Re
WhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzEAeJo
8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfA
XT5VL4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1an
g/SupirDQTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3w
jeElkD7wDfA1g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKs
gyyd5H2ghQnLzZNB/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysO
rDiwIqyqt6reqnpQI6ZGTI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZN
BNMFLTXzLHRxRn9d5wS039bu2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuD
GqIvzO4Ckl08EuYGNnFZuAz6Df2uOA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/
pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7osCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsR
As/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+
kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxXrG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLe
EK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10bA0J37XbgI4h6NiTGlgjey55vPN9C
vphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsMfO18G90DQWppaGR8FhyV7d0t
Z0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuAcEv40fQiMJHzgh+sP1m3
GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7hOc+ZD3r7JhTHUyT
DDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhcQlggAgKTNIvw
DuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPieHAXma+ah
oQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZodLL
lV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuC
OFWfLi8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ
3WU1CPvKUC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5
O8DV2vm9OwnCcqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPl
ZfktW3kwP2FND8QARdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinf
gDhNdwr7wVBNjrP4QI+XOmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNX
k6uC2NfwrHEDyHZDFVMMmOymGcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8
m2vKZTD0ML8p3QY668dMGvgmKoP844EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE
26qDwWCYLntM+8CwyYh1EHgG+HsErBBoo1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegf
a98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVi
bTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3D
eoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/FvBfzHixlKUv/0QV1qcu/URL5r/qf
9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577VciJ9VOrNWFLgPCOPFuyCW9Sxz
nYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2Bj2ZD6UBIHzGEf87wAgx
Tk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6PAO2g8r7rU5AOWxaZ
i0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8SNxyML5qnhrwG
OV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO9Bh1sBIC
3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqehsh3E
tfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3f
S/cgLM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0w
dxbtnAOvxZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0J
YWmOKNP7EO61lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWF
peJZyDqUEcjZC2E7QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFB
j8efTpzvN3EOMLaH8Mz4fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7e
mlnAJLWBfyqIy8SexpGg6srBrJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8
eNnRbDjx6umembugd0afeS89CyGzm2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/Mtg
ulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+s
U023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8QKs4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFD
QS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlriaPBleW+4h4A+0Rcv2MC/hQqm78H6uvVo
aFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3BfAENV+TPPJtBDAzGeWJBek3poT4Ld
YR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73VwvZa/L30PRO6KjLV+D+Zmhkzx
fciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUHqC39zfJvgulJ613DaMit
kfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8Jxqetqy0HwVfVH+lN
ANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA4LetE3dAYKna
V28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i+buHd1BQ
UFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+Fb4U
NwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO
96WdIF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuH
rXhlsNQJGRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B
3aF86YsEb+WcvRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJ
A+ublnXmIuDPd77pnAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DY
JRXVuwK7qeM3gatc/iKlC6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP1
7sl6/gsgYRgmx4H/vNZWKwf+K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyo
NADdhlGPAfmEcYI8B/Qs0jCB+oM6S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/
gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9
rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEBiEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoK
CgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVBU6yRYkfwt83skt0QxK/Nm0xRICq8rySB
Ok8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzPxYfomyC/c94mXxEI1cIuh80GTzP/
D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILYKqa0+TMwfBweEvMscNM2MawC
+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeTCs4r6UVudwZPMU+7+M1g
NlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/PVC/VndKFhCXaFOk
NuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0FMV6YbNwJHBNK
e78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQRweG+p6F
wFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4jUCQq
5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQ
iwxmzZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+q
AkIttbGyCDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCg
oKCgx0n8sw1It/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3
QKmQH5v/IqTXPn3w2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZ
JeNOiMuIbRPyOvgauMq63gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVb
ZdD3SPsNkSDk+j92doDS5uIZxfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GN
laqaJoHniDDU9i5cnJ/0UfZYyBvmi9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus
9OS24H7LfTd3Kahn/a+5zoD5PVNAagzWosa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3
Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsGlnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTs
dgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqmgnLGv8h1CHy9PG/53gXfi/7VzgiwbpOy
NQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+IpeCbQ0mkp2EMeq4WoEGMoLHcT5EPVq
qCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhKGV6V5oPQRUokDPy5gZvql+C/
6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX/S3BleVp7twBvhxa6X6Q
Qo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcTX4h0g+mc1l8s+ncP
76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1CfA1+nLn/wvqn
oUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht9fqWi2DY
b3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSIO5Ng
AOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O
+nwtRKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dA
QQSxtt5eHQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUK
tNX7Q86p7LysgeAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhT
cLt/xorMNyC7t2u+9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3c
c712MC6XIqUfIO6bsBrmiSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJ
ZRIpDr523mm+KSAtFyaLyZDTMy/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+
CJSril/7HJRx+hYFENfrMw0/QbHosDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSK
X/peaQHVeXonB//uYR4UFBQUFBT0OPzpGecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5
V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3ICpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1
n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8XvHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZq
r4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupTyJ+hJ+uh4J6cNStjARQLjdgpVgbD
FsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN+BHyxuodZAfkeIRo8wzwfK6M
F/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6PtoVAsKeZa+HtgDGiLfRpI
AfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+sfgW2btapjtLgnuBq
4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqWTmuLoFj96JVR
aXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBlcdaS8sG/
MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7i6t1
bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUy
l8p+AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57z
ffZz4NLuWVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKg
peT/5HkWxPIR7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8f
DsIm9wB5EpAC0k4wrk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6H
ql9VeAnsXfXFMSvgl1XeTUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRx
xqvRVSHvSb2++h0o7/gauVqD4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFP
OwQljsTPihwCruM+QVkKnin5y3NaQpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXP
dPdV53JwpnhSc7eB97hnuccL5u2mU6ZQYLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9Y
jXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGl
KZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJHKa1AT1I3+G+DVo3njN0gp4k6NJAMmujt
qqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZkgRwupqgXwZFm+UQ8A3quPlhPBONG
eY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD1KUyB8qvB0+2ppv6QXR6fKmY
lhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKlSwuP9+nTp0+fPhAWFhYW
Fvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQflI1+Zn+kFik2pan
nwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6YXQd4EPFNQjXQ
r4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814Ex5l7qy/P
AO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBqTr3B
3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/nt
nbnu+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nah
H4N3rK+JZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhN
m01lgTlK3YzycL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU
8Lv8FfQXIWNM7j3np+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/I
SVMsmMrJS9Qs8Lf11xN3gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0iv
mPYaF0NeD+cB7yhwnDJvMayGhPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfI
fcIEp2vcbn5L//sGduPGjRs3blyYQBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzL
L3D16u3b2dl/Xbxy5UqUCA+Ht97q379+fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xP
RITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3LzMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2i
KP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B
+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDvsEWGjwNNU+3C26D3Er6jDQjzuCjE
gFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5/MoV6DFWyroTDilbKuj3P4KE
6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh3YRjvAVdarWMu9wRbg9e
1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L7QgI7cQD7ALhF8Mc
0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEdeU8gemnEv5Qdg
vvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUBJV3MMMeD
O8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQmZtR
/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0E
Wm9K0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8
GkpWKuYsq0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRr
f90Hw6Ps3bt37969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2
QWZmXl4gAGXLli4dFQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRN
EODpp4sVi4j4tT+P83n/2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs8
3t6A/n8mq+7f93h8vsK4bdvGxEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQ
iml3hVRQV8nbmQDCE2JrfSxIcYQYNoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgY
THpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A76qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7
Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmn
IHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w24dObIH80dn709tByJ3IiJgtYGxoMfvr
QsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0V1yoXQBDSeNdxxG4fytvkh4Lvi6u
b30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzIc7l/0i3gK6029JlBLikvFdLB
W0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9yS3vAfCleBZkpYJ6mhm6
FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDqpU3wdwVHTfsFy0nw
NgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGOwbve7wJhgfyy
tTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+QVoVfg9zN
/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1O9jQ
fkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4u
LAwOHbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c
/nTinPzGdePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdB
v6xf8DUBsZQYJX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdA
C8EhW4GvhK8CZUGt4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSul
z4O98InjrZufLIPbpjRD4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5
NnQrpN+Pyi12BLyH0rsmxYL3nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q
2s34klgazHuksEAUXG+b9FLOafB10vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qw
twd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZuAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJ
eALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4
jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoPIKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXP
dTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCNUXcI3UDtpx8Tb4G8XtIDdcDU39xQ
9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHWWGxF8RGgFxU+sgTAfljsYTwD
Jd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAFPPPXfTj8IwW1y0uWLFmy
ZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L9dtSO7s9LCwurjBO
QdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1HTIyFOUfnd+1
a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE6JDXHuRv
BUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpIDoEUK
L4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DM
Gahe/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dp
amlw93a38r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD
3mzPGFdpkB4YLcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH
+jVEVQqpEdISzCfFCOUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+
bcpsfxjkf5P7TH4iJB9JWZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/
cn9peHAs81amFQyfS5H+3WB/wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggL
QSrNp7oMxhjjbnk82CvYo02twFbevNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubs
EpnXQNmlfOf5EaK/jnreuhzi9xWvn3ATxG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDr
sWNRcPTna19d6grp+/P2pXUGZ72srintwD/KMyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vu
u7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrHKscqxx9/3wq2V0ddHXV11N/d+0JTMqdk
TsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Zem3tt/u5n95/77yfo/6aqiqKqoKqq
qmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z+f3g9wcCilK4PXjwo4/eeqtw
+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j24K4j9ufnnGW65axxswA
c0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE8bDQ07ACpN32mJhl
oL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/SzoGawVe4H4o6hZ
DoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4//EPXU8N
hLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbzlfxv
lL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U
+prFcg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBu
XzVC6pm0gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175
/OF50XA+5dZ7rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXz
YhBWCvNNJ0DZL16WloG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9
vU1rwNDJ3N34BBSZFr4+bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98
pQbsTzze7szzkN6ITYEfQVtgnB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmC
mrtGjRo1atSosNb5cYlsGdkysiW8/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12
+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu
3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3Lti7bukB/+tP/736SQf/xFKUgkS1I2f4906aN
GNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUV
BQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3ZNlicTh+v/+o6/+ogriP259OnLOs
9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4RIoB7XOttdYPpNZFR5ZbAuIh
62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt/SPBAPo1Suo24IFu1L8H
vRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJHzTth7dklWVvjoHTH
SmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D5EVy8pVP4EGC
fVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfaaTC0loeJ
30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+2T0S
/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F
7kU2i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpc
uvMx2OOZpnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V
4Pb41FYPhkG5F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2
vg+OvnEq43R1SLmsV9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHi
xIkTJxaeHz9+/Pjx46FEiRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUN
GzZs2LABMjIyMjIyICoqKioqCjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn
5u6su7Puzjo4fvz48ePHC8MXPC4uLi4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQo
VZWqSlWYkTsjd0YubC66uejmolCmTJkyZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0Wdpk
aZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4
i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFrxq4Zf/z9ubHmxpoba2B66emlp5eG8+fP
nz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe8LThacPTHl3b/7DNaZvTNqdB+U/K
f1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiSviV9Szo4nU6n0wk1F9RcUHMB
TJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5oeeHnoc2MW1i2sQ8vnH1
qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z+32+gpng385IV6ky
ePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv1i3Iy7Nao6LA
aHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvtzYgPx33c
/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsCaMNy
W6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4
flL7luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5Ehb
lTw7RI61fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUz
JhVi46JioidBpDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5
H4S+YCirTAebTfrcuxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjt
eBUNwk6b+pcKAWsTw21Lf+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc
3Ku9SfnNoHRqzPHi88H2vpwWvh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fg
bZV/PmAHxyaLKo4BY2v9Y6UEZFRJeeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHu
obzz7uJQ8UTF80USoGTXMkLJb8F0yNQnVAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/
8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyfO++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJ
EyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6ggTmUV/1bym6peiWorD80vJLyy8VfsVe
bm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPUD6Hr1K5Tu06FnF05u3J2wcw9M/fM
3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oePjpO7O3d37m7IL5dfLr/cv9+P
5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlhzwx7Zti/3s7U7VO3T90O
JwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8pflP8Jni35bst3235
z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/vjJ8ZfjKAN84
vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7TuHpc7+v/
Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1K9z2
6VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QI
qUAaJr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqI
AN1NSQRAQgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID
6U2mQ8rqrBrpD0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4
cfXutrvWws6O+7PObgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ
9lsOOHqCb2vWK2nnwD/cednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn
5mG3COlfZg9xfQkPWmdsy/kGzCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1
LFjPmd4wxoM/RnmdhuAdpt7KTYVcMbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdzt
AiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJIH5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODI
jtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLnGTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGT
bWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuFzYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6
hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0CtZxhpOAN003xCd2Ct0FyoA9Jz4alF
40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbDtc4F7RS0WxDnX22/IIFZu3bt
2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03dt3Y38zgPnz9n1WkQ5EO
RToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJvht8Mv/nX9+Phkpqh
5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9G+VJBc+7wMxZ
M2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n8bZO2Tpl
629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW5Bos
PrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpU
q/b79gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6
tlYehHhu6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0e
Jm8GVoi9dS8In+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKm
hSC1NW3Q1oHwjCzKrUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgoc
RqFRycYQ5S3hVn6ECE/EiLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCk
R5ioNof1T2iVyYMTNkPd0oNB25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e
2jZwp+SNTs+BQKQvJL8j2GuY20ivQWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX
0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNB
nyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtO
CdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVfBHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3ua
BsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH+VNQ5G7Rj0sdgbDXw0fGLwV/28BU
qTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR7jmyR6QOAm2GMTJ0GDBffVl4
E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxasXHjxo0bNxbOCP/R9ZgL
apsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQTgonhd98Na4N0AZo
A37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAEJzgBdKMb3f74
6/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E/6PvzweJ
HyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16QmNWHz
zM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBb
t1q1ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/Y
GWfzcVcDuTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNA
HCItQgHKaudZCPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGm
HiRt9E0yFoUrSzLH6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWE
T8WODAblTTXTuwwC9QNLvSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2Wd
cZDvIyhpid4dEQPlo8rVDzkF1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3Ms
eRJwRavJNAg9Ffpz5BiIHZfoK5ELifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30N
qfvTOuZch3M7L5dL+xByt3pD/CvA1tfeOiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUU
y486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSAMgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4
eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEHQBVxWatD1IionxzfwJPnypVNOA+h4baP
QgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/iCyjbo3hGORkqHKpYv1YLsCeFfJf4
M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvnT7x46hSkHsrqd/MoqBHmapZU
0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtNlb2Pb6AWJLDFixcv/tsP
koL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDCgQowadKkSb+txWvR
vEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyXZr80+yVYKCwU
FgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYRthG2whrn
GsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPtwvYf
/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86
vnfvtWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3
+fm/rtf86FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG
6ufg/NwbuZn9ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08
tSkLzledeTk3YO2sdec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf
4CVqC59D4Cn/Lf08iH6pHTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5
Kr5v3wglXzctPDsHskqHp+aMBvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7N
E6/a34Z7FczNS9wD7Xbe7rQx4Oua2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAso
Xf0tIG1nTrQwAFzFPBfVXHDN0p837AYxRi6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD
5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwnos4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2
EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKlY2IrBCB0onQg/mWwbQibhQ+Uyq4zTglS
RiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+okHIfLCPdxjCVoH5A/tsSyXw5ftK
CXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQvu72gOsmyGueq90pAx6MhvBP
QR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTxLeAZ2ujV/88g6fT4BmxB
7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gNozaMglEZozJGZUD0
neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej70bfhTTSSHsM
/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1AfaA+UIcH
ox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWIeqTw
ZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/
HX/hzY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2
h1Ue3n/U4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv
/uST/2iCpyDu4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFf
jPsFjw9sxvB5EYtBvaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75K
fQWE3oYnDeXhZon7SRdWQPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5
GSo8iN9gSAJrd2tRDoJaQW0tPgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36s
BUBviiAkgHhQF5V3wF/TWTGvMxiTDe3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp
6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXR
lqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMvg7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4
BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz
78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfEKEsVuB2ecfv+cTDUk3da+kDUujA1
thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8sr7Tehpjc+E02BSJaRRaPygTD
EPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW0n4y7AJnVEpOSjfwrcwe
dC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDoE+gZaAeBQ8pq31lQ
ZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F4cOHDx8+/K9P
nIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OVKs8+O2MG
VK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0Dk6lY
sfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GO
HDly5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH
546Dtj1gXGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c
97jmkLnAXcc9BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5j
GHBSb6VfBHGysEj0g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bI
KND8asdAKOidDTPU1aAsslRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbU
mOM9Bm+crfnuhW/hl+X7Lp36ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTC
d4TdjmgIYWdDy9ltYGkdeceSD3p9fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+
0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9
G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIWMC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/
RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN620z4BAobAKmk4uCbm/uh7EvI3+C4HngXJ
bM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSsu1/10kYIxOvN8uaD9rH+tvAe5Jdw
V9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/RmBEIBL0idp2dTrop9X+gfqg
BgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7wV8U/M9UsOzcnpV7Vu5Z
CQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6j9Y5/lf5/f+4Ztjn
c7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3az+xst1tRIDTU
YpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTCuI/bn06c
lamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcMy83d
DG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArC
FLGD2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx0
3IyrCYbz9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG
78Kz5Sr0e7oflJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5
W80TIfRLR35UNIQkhawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QX
y4CS6NX0LSB/Uiq/WBfI65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9Fmw
Y3gmYSqkzTS2TX4ZQvbYD9kmQ9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1l
s/01CPi1ndJT4C8aMBEDOTnpC7zPQeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfk
Nr59Mn0TuDpmpST1BeW8sij9I7B1t3+pfQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2g
VNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8atBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLp
h5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9AstYxjKAoQxl6J9tNSgo6HF44onSpSMi
4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHiERFw9uydO5mZIIqhoSEhEBY2ZMgX
X/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/+tPcfj8kJPxaQBEWZrFIEmRl
iaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9HVSE5OTfX7y+M+7j96VKN
B40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/TeHkdCIG+O/pVcDYpc
bVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9IEGNXFcpF852
veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4Wd+mrwJ9
mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqEW0zO
Su9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQ
L3tm590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkz
gL+M+pHiBf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21
IIDJbXrPuA+0zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBM
YHsgA9QG0mLhTZBijMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmX
u0FufprHPxPUE2wJ/AJynNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+
HhBoIpwGPUH4WVwFvC9uk74AXdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+Q
lZWT43RC375vv/3113Dx4rVraY/jJotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnP
PTd27KJFcPr0tWv/aJ3ox6V69bJl4+Phxx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t1
5vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9b
bn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgThJCRMNr5cdBBkD3FXzbPDqYyT2qFZYCln
NIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQejhO/vdwN3hLQhcAu2n9hz8btL4Ovq
p8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl8oE/AeSFNDCfA3edPF/WQLi6
9lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2ARXzN4AF9pYjWGJgibBVD
QIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8ufk6iJsymt8E5Ana
PPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuyZmRdhhxnVn25
E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ/QQAmaZa
MgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgoqVwC
9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+Uv
VoR7i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0
q/p9zQDaSf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp99
9o9v4vt/zZ9OnC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AU
TB/HRIZUB8MKZsibIfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZ
Mze+TBNBPBvyWuJC0BdnrksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294H
AmsCy31TQN5hirA8A+pRbaM3GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itF
xK0G+xVXpKUD3EjdundNHNjnlUmr3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8
YJXQm2zQF+kX0UFIYgzHQaylRwulwdBYT1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtA
jrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRpzoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73n
JIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi6LvFfvQD/RVhseACoTFLhATQv+BHcS3o
U4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTacMBwG+XRIo7A7YJlhmWH7CcwO4zrz
YYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT+mx2Q+N3Grq7TwBnEWegyTsQ
0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPHhWHwnXvFnU13wf9ufs4F
DyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1HjtHGiDlZP6pwCUp8nf
PcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+Fffibt4CuXvU
K+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrWM2YK6B3l
m4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymAb6zr
mfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/O
A54QhodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDg
PereCUJe7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7M
eM3VGzI/dZcMTIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6zn
AzJBjBGHiU+BGGV43/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGq
NZAO2oyMxik1oGnxZzuXbgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDb
YogaI1e05IM+jmrmJZBYrOj+5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0Q
Pzcso9grkHTYvUN/EXZe2PbJfhckz8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgR
hiflX5fPCc45BwUFBQUF/Q/xp2ucg4KCgoKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0Ew
cQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAfEEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU
9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDAj4oAAAAASUVORK5CYII=
--------------030202080101030400010806--

--------------070109000907080604020304--

From tbray@textuality.com  Thu Jun 13 08:00:11 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA3EE21F997F for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.622
X-Spam-Level: 
X-Spam-Status: No, score=-1.622 tagged_above=-999 required=5 tests=[AWL=1.354,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w+69IJtAkit0 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:00:05 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8241221F8AF4 for <jose@ietf.org>; Thu, 13 Jun 2013 08:00:04 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id ib11so7231088vcb.31 for <jose@ietf.org>; Thu, 13 Jun 2013 08:00:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=4vVe7izrbHqd1QjFbYolWoaMt5qhmqGbcl7UgO1r5zQ=; b=oBdDpS1ZunO95aP8+j8fxe0CnTwFzBFY2JOGIVyg/rhzmpnTkR4scLYAOyXbD38EVv 6r7tQDPKfpYHDGpluiVKR58j+qkllaaqVlWueIfnZOGaZoQSU28IPwQm9UcS2IAQYx/t 0FX0EBpGYtcDv3kHgQhaUZv9d2KGq6wCjYc6aNCMU2jo5n5nxdrETsMQdSSM6p9LwQGI ERW9IHAy3xS6H3J7jcG84D83hFC+/slJYdMh5SnIDr7bRQxKvD7OPgG3dMHrJLx8iajG Sb1sRe4mmVeD1CVKPRVFxu9vSJTLtlTk3AizmohTNAmQp32bFfVEgncAt1SOS/FgjALM 6U8A==
MIME-Version: 1.0
X-Received: by 10.52.27.108 with SMTP id s12mr412260vdg.77.1371135603872; Thu, 13 Jun 2013 08:00:03 -0700 (PDT)
Received: by 10.220.25.199 with HTTP; Thu, 13 Jun 2013 08:00:03 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
Date: Thu, 13 Jun 2013 08:00:03 -0700
Message-ID: <CAHBU6iuTyAcTJ=wCGeqtywVY4_YNKSMvULBsJ6YaoQsB7Oh-=g@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/related; boundary=20cf307f35329ba8ab04df0a624c
X-Gm-Message-State: ALoCoQk2DOBGNdocLikM7OCzG8SHm2YX0gpkH3nTjjZRHgf5Pee1EzHqMzZtkyYJBK7/xZxbY5Wa
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, George Fletcher <gffletch@aol.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 15:00:11 -0000

--20cf307f35329ba8ab04df0a624c
Content-Type: multipart/alternative; boundary=20cf307f35329ba8a804df0a624b

--20cf307f35329ba8a804df0a624b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'm sympathetic to the frustration about not being allowed to do
engineering.  But this is a movie we=E2=80=99ve seen before; sometimes you =
have to
deal with the problems of success, where industry likes what you build and
just adopts it, without bothering to wait for the process to complete. In
this situation, the smartest thing to do is to declare victory, freeze the
working version, and ship the RFC.  At this point, based on the track
record, anything that=E2=80=99s presented as a successor to JW* v1.0 is goi=
ng to
get close and respectful attention from industry.  This is a good position
to be in.

-T


On Thu, Jun 13, 2013 at 7:35 AM, Richard Barnes <rlb@ipv.sx> wrote:

> This would have been a nice discussion to have had 18 months ago, when we
> were getting started.
>
> I don't think it's compatible with the IETF ethos to say "Changes to this
> document MUST NOT break existing code."  Otherwise, we're not doing
> engineering here, we're cleaning up documentation and rubber-stamping.
>
> What would be acceptable is to say "Changes must break cleanly with
> existing code".  That is, it should be possible for a JWT implementation
> to, say, process both "legacy" JWS syntax and whatever comes out of this
> group.  That way, we could come to consensus on the best solution,
> incorporating lessons learned from earlier work without being hindered by
> them.
>
> Would participants here consider it a acceptable for the output of this
> working group to be incompatible with existing JWT implementations, as lo=
ng
> as it had the property that JW* objects in the new format could be clearl=
y
> distinguished from "legacy" JW* objects, so that implementations could
> adapt their processing?
>
> --Richard
>
>
>
>
> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com>wrote=
:
>
>>  +1
>>
>> Breaking deployed code as raised by Brian, Naveen and others is a
>> critical consideration.
>>
>> Thanks,
>> George
>>
>>  On 6/13/13 10:19 AM, Mike Jones wrote:
>>
>>  Jim and Karen, could you please do as Richard suggests and close this
>> issue as =E2=80=9Cwon=E2=80=99t fix=E2=80=9D.****
>>
>> ** **
>>
>>                                                             Thank you,**=
*
>> *
>>
>>                                                             -- Mike****
>>
>> ** **
>>
>> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
>> *Sent:* Wednesday, June 12, 2013 1:57 PM
>> *To:* jose-chairs@tools.ietf.org; Mike Jones
>> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
>> (base64)****
>>
>> ** **
>>
>> In other words: Chairs, feel free to close/wontfix :)****
>>
>> ** **
>>
>> ---------- Forwarded message ----------
>> From: *Richard Barnes* <rlb@ipv.sx>
>> Date: Wed, Jun 12, 2013 at 4:55 PM
>> Subject: Re: [jose] #23: Make crypto independent of binary encoding
>> (base64)
>> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
>> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
>> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
>> jose@ietf.org>" <jose@ietf.org>
>>
>> ****
>>
>> To be clear, I structured my message in two parts for a reason, to
>> separate the analysis from the opinion.  I acknowledge that I am but one
>> voice here, and I'm increasingly hearing how alone I am :)****
>>
>> ** **
>>
>> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:****
>>
>>  <impartial-analysis>****
>>
>> So just to be clear on the trade-off the WG has to make:****
>>
>> ** **
>>
>> On the one hand: Breaking every existing JWT implementation in the world=
*
>> ***
>>
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)****
>>
>> </impartial-analysis >****
>>
>> ** **
>>
>> <personal-opinion>****
>>
>> I have some sympathy with JWT implementors.  It sucks to have to refacto=
r
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a D=
C
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."****
>>
>> ** **
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur th=
e
>> implementation pain now, and get the design right for the long run.  Bas=
e64
>> is a hack around JSON; we should build the system so that when we no lon=
ger
>> need that hack, it can go away.****
>>
>> </personal-opinion>****
>>
>> ** **
>>
>> --Richard****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:****
>>
>> I did at first find it curious why the cryptographic operations were ove=
r
>> the base64url-enccoded values, but I was also very focused on JWE, where=
 I
>> think the field separation problem is less of an issue (at least now).  =
For
>> JWS, this would certainly cause problems without some manner of unambigu=
ous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be use=
d
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider i=
t
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.****
>>
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versio=
ns
>> > of the JWS Header and the JWS Payload to preserve them in transmission=
,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serializatio=
n,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenatio=
n
>> > isn't an extra burden.  Given you already have that quantity, computin=
g
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should no=
t
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+----------------------------------------------=
---
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+----------------------------------------------=
---
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >****
>>
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose****
>>
>> ** **
>>
>>   ** **
>>
>> ** **
>>
>>
>> _______________________________________________
>> jose mailing listjose@ietf.orghttps://www.ietf.org/mailman/listinfo/jose
>>
>>
>> --
>> [image: George Fletcher] <http://connect.me/gffletch>
>>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--20cf307f35329ba8a804df0a624b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;m sympathetic to the frustration about not bein=
g allowed to do engineering.=C2=A0 But this is a movie we=E2=80=99ve seen b=
efore; sometimes you have to deal with the problems of success, where indus=
try likes what you build and just adopts it, without bothering to wait for =
the process to complete. In this situation, the smartest thing to do is to =
declare victory, freeze the working version, and ship the RFC.=C2=A0 At thi=
s point, based on the track record, anything that=E2=80=99s presented as a =
successor to JW* v1.0 is going to get close and respectful attention from i=
ndustry.=C2=A0 This is a good position to be in.<br>
<br></div>-T<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Thu, Jun 13, 2013 at 7:35 AM, Richard Barnes <span dir=3D"ltr">=
&lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">This would have been a nice=
 discussion to have had 18 months ago, when we were getting started.<div><b=
r>
</div><div>I don&#39;t think it&#39;s compatible with the IETF ethos to say=
 &quot;Changes to this document MUST NOT break existing code.&quot; =C2=A0O=
therwise, we&#39;re not doing engineering here, we&#39;re cleaning up docum=
entation and rubber-stamping.</div>

<div><br></div><div>What would be acceptable is to say &quot;Changes must b=
reak cleanly with existing code&quot;. =C2=A0That is, it should be possible=
 for a JWT implementation to, say, process both &quot;legacy&quot; JWS synt=
ax and whatever comes out of this group. =C2=A0That way, we could come to c=
onsensus on the best solution, incorporating lessons learned from earlier w=
ork without being hindered by them.</div>

<div><br></div><div>Would participants here consider it a acceptable for th=
e output of this working group to be incompatible with existing JWT impleme=
ntations, as long as it had the property that JW* objects in the new format=
 could be clearly distinguished from &quot;legacy&quot; JW* objects, so tha=
t implementations could adapt their processing?</div>

<div><br></div><div>--Richard</div><div><br></div><div><br><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 10:24=
 AM, George Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:gffletch@aol.c=
om" target=3D"_blank">gffletch@aol.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Helvetica, Arial, sans-serif">+1<br>
      <br>
      Breaking deployed code as raised by Brian, Naveen and others is a
      critical consideration.<br>
      <br>
      Thanks,<br>
      George<br>
      <br>
    </font><div><div>
    <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim
            and Karen, could you please do as Richard suggests and close
            this issue as =E2=80=9Cwon=E2=80=99t fix=E2=80=9D.<u></u><u></u=
></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
            Thank you,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
            -- Mike<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u><=
/u></span></p>
        <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>
            Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank"=
>mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
            <b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=
=3D"_blank">jose-chairs@tools.ietf.org</a>; Mike Jones<br>
            <b>Subject:</b> Fwd: [jose] #23: Make crypto independent of
            binary encoding (base64)<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
        <div>
          <p class=3D"MsoNormal">In other words: Chairs, feel free to
            close/wontfix :)<u></u><u></u></p>
          <div>
            <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=
=C2=A0<u></u></p>
            <div>
              <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">-------=
---
                Forwarded message ----------<br>
                From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.s=
x" target=3D"_blank">rlb@ipv.sx</a>&gt;<br>
                Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                Subject: Re: [jose] #23: Make crypto independent of
                binary encoding (base64)<br>
                To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailt=
o:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
                Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@tr=
ac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;,
                &quot;&lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@=
tools.ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@t=
ools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.=
ietf.org</a>&gt;,

                &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" ta=
rget=3D"_blank">michael.jones@microsoft.com</a>&gt;&quot;
                &lt;<a href=3D"mailto:michael.jones@microsoft.com" target=
=3D"_blank">michael.jones@microsoft.com</a>&gt;,
                &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank=
">jose@ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose=
@ietf.org</a>&gt;<br>
                <br>
                <u></u><u></u></p>
              <div>
                <p class=3D"MsoNormal">To be clear, I structured my
                  message in two parts for a reason, to separate the
                  analysis from the opinion. =C2=A0I acknowledge that I am
                  but one voice here, and I&#39;m increasingly hearing how
                  alone I am :)<u></u><u></u></p>
              </div>
              <div>
                <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></=
u>=C2=A0<u></u></p>
                <div>
                  <div>
                    <p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23
                      PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>&gt;
                      wrote:<u></u><u></u></p>
                  </div>
                  <div>
                    <div>
                      <blockquote style=3D"border:none;border-left:solid #c=
ccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class=3D"MsoNormal">&lt;impartial-analysis&g=
t;<u></u><u></u></p>
                          </div>
                          <p class=3D"MsoNormal">So just to be clear on
                            the trade-off the WG has to make:<u></u><u></u>=
</p>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the one hand:
                              Breaking every existing JWT implementation
                              in the world<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the other hand:
                              Eternally binding ourselves to base64
                              encoding, even if binary-safe encodings
                              become available (CBOR, MsgPack, etc.)<u></u>=
<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/impartial-analysis=
=C2=A0&gt;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;personal-opinion&gt;=
<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">I have some sympathy
                              with JWT implementors. =C2=A0It sucks to have
                              to refactor code. =C2=A0But I think we&#39;re
                              literally talking about something like a
                              5-line patch. =C2=A0And early JWT implementor=
s
                              knew or should have known (to use a DC
                              phrase) that they were dealing with a
                              draft spec. =C2=A0As the W3C editor&#39;s dra=
ft
                              template says, in big bold red print,
                              &quot;Implementors who are not taking part in
                              the discussions are likely to find the
                              specification changing out from under them
                              in incompatible ways.&quot;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">As PHB pointed out in
                              the other thread, it would be nice to use
                              JWS and JWE in place of CMS one day,
                              without the base64 hit. =C2=A0We should incur
                              the implementation pain now, and get the
                              design right for the long run. =C2=A0Base64 i=
s
                              a hack around JSON; we should build the
                              system so that when we no longer need that
                              hack, it can go away.<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/personal-opinion&gt=
;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=C2=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888">--Richard<u></u><u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=C2=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=C2=A0<u></u></span></p>
                          </div>
                        </div>
                        <div>
                          <div>
                            <div>
                              <p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><u></u>=C2=A0<u></u></p>
                              <div>
                                <p class=3D"MsoNormal">On Wed, Jun 12,
                                  2013 at 10:27 AM, Matt Miller
                                  (mamille2) &lt;<a href=3D"mailto:mamille2=
@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;
                                  wrote:<u></u><u></u></p>
                                <p class=3D"MsoNormal">I did at first find
                                  it curious why the cryptographic
                                  operations were over the
                                  base64url-enccoded values, but I was
                                  also very focused on JWE, where I
                                  think the field separation problem is
                                  less of an issue (at least now). =C2=A0Fo=
r
                                  JWS, this would certainly cause
                                  problems without some manner of
                                  unambiguous field parameterization.<br>
                                  <br>
                                  I will note that unescaped NULL is not
                                  valid in JSON, so it could be used as
                                  a separator between the encoded header
                                  and the payload. =C2=A0I do find it
                                  interesting if JOSE could more easily
                                  and efficiently support other
                                  encodings. =C2=A0However, I think that
                                  while this is an interesting thought
                                  experiment, it seems we&#39;re too far
                                  down the path to seriously consider it
                                  unless the current state were shown to
                                  be horribly broken.<br>
                                  <br>
                                  <br>
                                  - m&amp;m<br>
                                  <br>
                                  Matt Miller &lt; <a href=3D"mailto:mamill=
e2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>
                                  &gt;<br>
                                  Cisco Systems, Inc.<u></u><u></u></p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal"><br>
                                      On Jun 11, 2013, at 6:01 PM, jose
                                      issue tracker &lt;<a href=3D"mailto:t=
rac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf=
.org</a>&gt;
                                      wrote:<br>
                                      <br>
                                      &gt; #23: Make crypto independent
                                      of binary encoding (base64)<br>
                                      &gt;<br>
                                      &gt;<br>
                                      &gt; Comment (by <a href=3D"mailto:mi=
chael.jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a=
>):<br>
                                      &gt;<br>
                                      &gt; For both serializations, you
                                      already need the base64url encoded
                                      versions<br>
                                      &gt; of the JWS Header and the JWS
                                      Payload to preserve them in
                                      transmission, so<br>
                                      &gt; computing them isn&#39;t an extr=
a
                                      burden. =C2=A0In the JWS Compact
                                      Serialization,<br>
                                      &gt; you already need the
                                      concatenation of the Encoded JWS
                                      Header, a period<br>
                                      &gt; character, and the Encoded
                                      JWS Payload, so computing that
                                      concatenation<br>
                                      &gt; isn&#39;t an extra burden. =C2=
=A0Given
                                      you already have that quantity,
                                      computing<br>
                                      &gt; the signature over it is the
                                      easiest thing for developers to
                                      do, and it&#39;s<br>
                                      &gt; been shown to work well in
                                      practice. =C2=A0There&#39;s no compel=
ling
                                      reason to make<br>
                                      &gt; this change.<br>
                                      &gt;<br>
                                      &gt; Even for the JSON
                                      Serialization, the only &quot;extra&q=
uot;
                                      step that&#39;s required to<br>
                                      &gt; compute the signature is the
                                      concatenation with the period
                                      character - to<br>
                                      &gt; prevent shifting of data from
                                      one field to the other, as
                                      described by Jim<br>
                                      &gt; Schaad in the e-mail thread.
                                      =C2=A0So this step isn&#39;t actually
                                      &quot;extra&quot; at all -<br>
                                      &gt; it&#39;s necessary. =C2=A0It&#39=
;s also
                                      highly advantageous to use exactly
                                      the same<br>
                                      &gt; computation for both
                                      serializations, which is currently
                                      the case.<br>
                                      &gt;<br>
                                      &gt; Since there is no compelling
                                      reason to make this change, and
                                      since making<br>
                                      &gt; it could enable the
                                      &quot;shifting&quot; problem identifi=
ed by
                                      Jim, it should not be<br>
                                      &gt; made.<br>
                                      &gt;<br>
                                      &gt; --<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt; Reporter: =C2=A0<a href=3D"mailt=
o:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>
                                      =C2=A0 | =C2=A0 =C2=A0 =C2=A0 Owner:
                                      =C2=A0draft-ietf-jose-json-web-<br>
                                      &gt; =C2=A0 =C2=A0 Type: =C2=A0defect=
 =C2=A0 =C2=A0 =C2=A0 | =C2=A0<a href=3D"mailto:encryption@tools.ietf.org" =
target=3D"_blank">encryption@tools.ietf.org</a><br>
                                      &gt; Priority: =C2=A0major =C2=A0 =C2=
=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0
                                      =C2=A0Status: =C2=A0new<br>
                                      &gt; Component: =C2=A0json-web- =C2=
=A0 =C2=A0| =C2=A0
                                      Milestone:<br>
                                      &gt; =C2=A0encryption =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0
                                      Version:<br>
                                      &gt; Severity: =C2=A0- =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0|
                                      =C2=A0Resolution:<br>
                                      &gt; Keywords: =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt;<br>
                                      &gt; Ticket URL: &lt;<a href=3D"http:=
//trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" target=3D"_blank">h=
ttp://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                      &gt; jose &lt;<a href=3D"http://tools=
.ietf.org/jose/" target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                      &gt;<u></u><u></u></p>
                                  </div>
                                </div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12.0pt">&gt;
_______________________________________________<br>
                                      &gt; jose mailing list<br>
                                      &gt; <a href=3D"mailto:jose@ietf.org"=
 target=3D"_blank">jose@ietf.org</a><br>
                                      &gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listi=
nfo/jose</a><u></u><u></u></p>
                                  </div>
                                </div>
                              </div>
                              <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></=
p>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
              </div>
            </div>
            <p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br><span class=3D"HOEnZb"><font color=3D"#888888">
    </font></span></div></div><span class=3D"HOEnZb"><font color=3D"#888888=
"><span><font color=3D"#888888"><div>-- <br>
      <a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank"><img src=3D"cid:part21.04020107.07020=
504@aol.com" alt=3D"George Fletcher" height=3D"113" width=3D"359"></a></div=
>
  </font></span></font></span></div>

</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--20cf307f35329ba8a804df0a624b--
--20cf307f35329ba8ab04df0a624c
Content-Type: image/png; name=XeC
Content-Transfer-Encoding: base64
Content-ID: <part21.04020107.07020504@aol.com>
X-Attachment-Id: 798c4a0d2637fa6e_0.1.1

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAACXBI
WXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAIJLiEoIGg
ETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlTp09Lly5dunTp
khC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLly5dB/rMr4ubm5ubm
5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc3Nzc3Nzcfgd34uzm5ubm
5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zFHGHAI0sR61oQpSxdUsuBrcbb
pFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL5KL61yAdzP0l4ytwdrCmZQ0B49ng
q9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5xhJQD0ijlA6g5aoPzQXA2i9znjMWcodl
l8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteBfaB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHn
u0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGz
l2e093YQJp4ZK4D+G+NGeT+oM131tF+h+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRG
mAkCkYsLFwDS//NGKvzbkoT3kJCBAD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o
0AicE+TFUiRou8QMPMH3hee3xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8
I6cn2B8meCh34eGjN6VerAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1
YO1qH6dbCKnhSYG5oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ6
9MW+HWD9Tu2S0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skj
ff0g+X5SBR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBN
v1lcAOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAYlnko
7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm+Bj0TqE4
h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9bF5rQRrpqG3v
Ct5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk00D+UBkr7oI2QPpS
CgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2qwt9Le26NjkA9faXTy79
AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3YG7o/SZiFChhSkm7DkLe+n1t
tYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HBdoFdC68EZ7ajSBEJss5l5/IM7hd6
qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2SiNe1wGvbXI153fwpnrSgWc/ws2y92v8
PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJmfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNp
dxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK6
3RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQd+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1E
j0GgzhSfuayglYmv/7gaaIn2W84tIN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqv
b/8C1AilmagDhgX6FnoPMGzxMnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUC
wLFVHq31B/NoD7P5ETA2O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgn
rBvSZgIG+Yo+GqxDcuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPo
K3/MPEATqdIiQEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJD
QtfUg0mloXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRv
LQkp3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAXQ8B7
LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZPAFvtzIyo
2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yMoDu4grVrTgMo
y8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJfOZ5ZoMXlTEpXQLuY
2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZEGcZ43wHdA+movjR47/b6
RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaBVxGvyrpeYM+yLs/6HuRrzh2u
FPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9lOZgn5ijt9wGfbJezT4I3PY4G1QW
jF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B91zfDX6/wIOlT+LjW0KJbwptCyoOupk6
L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGBLwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZ
EkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNCIWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+
G9grKgnuz35x32cROPa4Clpfgff1xGr3KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0
dTXrCT4p9s2GMVA6uqRnoZXwqFh86hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISL
IDZZ14XPhJK1S0WVXQ5BgUEjfM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJF
WNoq4IDeLh2CzJIZJ42dQL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B
+WN6SPNAVPLqbt4O0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7
gXzJ41LAV6D6Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0H
oqz6hbwIDFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNT
tARzuuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0fXAHU
FPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm5/fdHgE7
D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3cmrwrzUguJ7/
a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBuT9rl+6kw8FSbj3qH
wKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y2BpnVfZ8DSU9ixyt8itU
/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXOMlD/ZOGg5lMhIsn/81oWMP5q
KilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/uv90fnjZ82vBpQ1CXq8vV5VD4q8Jf
Ff4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSpUqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs
2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoUeP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48
kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMoOVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynM
cNSzKvCxstVUFLTLjplZPwNztWDxMcj5fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOm
ZRGIgXYvewOQ+htjlQSQVPtRVwgov9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g
9TblevUCkSLaaS/BVV8NdWWCeaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZ
Lsc8HtRHzkr2EZC9LXt4ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8
W/UqMvUHKHSq0J7gMJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwCl
su4jMQucu5z5HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZ
z1ch9JPQ/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPg
Afh1N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+GginF9
wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe3jjveb1L
79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jUkKkhU0EZrgxX
hv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k6oXAC0jnBbeAGCxi
JVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjCIFfUVQKpirVnVg64ZJrn
GkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQldQaC7us5lAaWqTHxtsB9xzkr5
AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6Rtuuag7JUPisvAGNdQwVjfxClDb2k
AWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBcQxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL
8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/qJoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lK
Qdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJimvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazho
Z0SschLk86w2FobUjm/TMy3gW0ye5TCA+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4
rE8LKwDpxbLnmifA6VZJ+61pkLgk9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULK
Q7mUyAE15oHjpHWXawNkdpJdzvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX
3KOOqVC1TalujUxgf5qdEOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKE
LZegyewqnT8YBj7f2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1j
LZgePz1+ejw0/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yu
v7n+5vrg98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQ
iynrI5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIhs05q
VsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/gi7EEGYq
BLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5llewH2laX3a4H
u5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcgbZIypRagLRXn1Yug
+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0VOoPmZWz96fHgfm8uRo+
kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1B1xTciv4SvDgw9i714Ph8Isb
LTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9EbyrMabKEXCdoXJmAmRPdk55egZi
vk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH41i7Z+BIaFO8VkZzDxjjPajg4CUQ+Cbk
B6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS79fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjt
rYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27Nezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82
fArjt4/fPn47tAxpGdIyBHJO55zOOf238eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHn
jT5vBAltE9omtP1PKvjvI93vRsI7dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjI
yMi7hf/u78O6D+s+rAtd0rukd0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf
7e+9tf9/iH+0HeoV9Yp65benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunL
pi9hwYkFJxacAFspWylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8
bo5sFhACUh3s7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9S
FX0HT0DyNOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNp
i1ffgJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUcTAS4
ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNiephdP6gOW
12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4KmeJcr8gu4urLX
FQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAEF/BbaS0AhoaefZI1
yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4WJkj6SFgn0ePgK/BY4+S
EXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjdvMqREr/AS8vrC1lDISX3VTnh
C35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgykjLn+22FtW0OZGzPD/5+/h29e0LR
zOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHMiX6y7xIwV9et9a//x7uVGCwGi8Fw+6fb
P93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8C
RxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eXlxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8
xGhB/wX9F/QHeae8U94JXehCl/+i/uO2j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5
FxCFYgvFFoqF6Xun752+F1jMYhb/69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNT
kU1FNhWB/J3yd8rfCWJ3x+6O3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZW
K6vwovqL6i+qw7bobdHboiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn4
0gFrWcva9/C+/bPnm5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHci
iOuqyRkAcnfpmVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhS
YWmZIQK0eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GB
vZVkMD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2RlshvQV5
pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn3/3wh+aw
8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV1V3RlYWzwbcz
r/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZajgMnpP0DfJ1htwp
lqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3Xzs4Ue9cyPWjcPjolY/O
nYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp+Tv7Fqi8pPjIlpMhJS1mYY4K
F3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+nvRwVPxkeWVO6PA6G89cf3th1Ci6N
iHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsticJZzlnOWy3s+KCgoKCjob8svsiyyLLLk
fZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcffABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74
iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5
SOcjnY/kbV//YP2D9X8xIvguAdvivcV7izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659t
x+F5h+cdnge7Ju2atGvS38Zdt27dunXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg
7w6A/o7+jv4OHJl9ZPaR2WCz2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9
+3vnm5ubm9v7neMsAy4U8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlI
SVKaXAkYKO4JG4gX4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8
HaTldBcjgHoZxeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG
/CAbdN2MceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAY
A1IleZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd73i97
+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsTs+HmTUi+
ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQu9QfDLNME9Q4
SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFafkM9cPRhUvEg8PM2
7U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1bqArEesefyO0JZxOelLjh
Ab5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbTNHBe0k3RjkFGR/uF9DKQkz+3
rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPwz3nlU6JTolOiIbZgbMHYgn8bL6VN
SpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYEa4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0
gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/
aMc/237mM5/5/MPe9yoS/13teDfl4t37905NQ01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9Zd
oA1taANFuhbpWqQrEEAAAXlTSt5Xe5tPaj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76Vu
IPJLbcUW0CJoJMeBNFMrmpsA8oiA+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5E
BPXkQKCIGKDNAWkVVXgMPGKJOABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEX
rBscJvEN2FYafjGPAdev8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4Tsw
FfT53vwtpEdZ4zN6gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYU
yB6Z/VXKc7Au8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90
hWx9cmZDYEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn
3Z1KQ2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMmS+tm
NNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJfQu5q+9cf
1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OKP+wLHlPNY70P
gHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA2T/Wrd7dyi95vuT5
kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdffPHFF1/8bXzbBdsF2wWg
M53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePdXOcLXODC327+rQRGW64t15b/
J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc85C8ulHQ6nU73B/43eTc14z+8W/Wl
CU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RKbUAK4GutKMjNzeUDfwSxRy6YcwJYLMqx
D9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZGbQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjx
ufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHTu4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I
0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hmgscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpN
oATJHZTDQG/nRGd3MAyTo6VZEHjYcNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2z
j4L2ncturwumROmK6RIY1kjnxQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5
x+4JjtOZvXIiILtJgr7wFSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2Dj
N1Dgq4B63haIcWlvpGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCu
V+c74HNlTWItiBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQ
Zyj2U9TpoOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrG
RNMM63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998Obaa1
mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdjn4x9MhZi
YmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUArWtEKIttFtots
B6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2oW1C2wQ4dPjQ4UOH
ga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0aNGiRYu8Ox/tO7Tv0L5D
XrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90rUAMkUZ41AVli2GxshLEE+Gl
zgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01C7QFak/ZBnIT+TNJD9p5MV63FpRp
2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWfljb6WWgeSrSTnpl0Ht43ph/xVyxqccT54M
Lz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBzYY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1
rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wEhg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB
4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcVpapgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP
4y5AbFzCgzefQvZcY520L6FswZIHO9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP
+Nf0PubtB47H1o3SS/AdZNjumwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/7
7BeIHhwcGPQIevRo8rJHCzjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9b
FU5/fGJSXG/IXF9xpysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0G
XWlDmLYd/Lr5l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok
20RwNBCzFRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvW
rFmzZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7be2/n
fTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDLgJf/xZco
31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAgcUHigsS8Oxp7
w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEmPEUMALu1BGCbNIwa
QBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De7uXeW54gjwvwL9gP9Jmm
ZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQOfXUScEU9D/0e4vbGJSZ1BfsP
9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9LkemgGd749c+JpBidVk0A+c17XTuGbB6
W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I3AykW/IE3XqQjlJIag5Sc3FKqgy63uom
9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEizNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+
CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQam
Y/VOQSOfKjerzIXXZXMbPt4Em8qeKLZuI/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8
ToakfInHM3tAzoDsMa5seLEzW3/hOKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1
odT4SA/IapQzLLYYmPqabliegmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpu
xGh4UTLmyNuz4LnE+ytDUTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCr
qcmq9TuIkbNW5XiD7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWd
E3dO3DkRXjR90fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA
0tJLSy8tDZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY
/Grzq82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQuh3r
dqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj257f3r5cj
dHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99AHRihisctG/V
jfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24bw8wlAx/FZIBokjW
w5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7mgSZc9NfaVHg+Fn9QUsE
xaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKrOTmOcKCiPdD5Ocid9A313cHv
cPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0VdClJ70UWuARg1kzYd1A32fdafQZur
fs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbObAHTaK2UoTDobb4PfQUIEnpkh4DJqi5T
B8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8Fa
zZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LL
gJnAHXHCFQupG9LfpI2CUZX7jvo2P+hXyw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHF
q7fV0wSEFw701i6DlG760ssMvh/qfih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSV
xz9CRp+UUq9uQF3/OqfKfgV2P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZh
kDYno2ruAwivrr9kOQ7SaO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z
774cWPJsybMlz8KNoTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuX
L7/PEWcFgQAyJA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C
1EXzFVNAquY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ
8IyqvKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Yy9s3
2Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE865Ky1j8vq
Dbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41PeOgYkbpj6Mf
QczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1OuRvJt+u1RO0Otlb
dWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/d35is8CJxGuTz0wE81Pz
4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7JDbMrPIuCjIPWFbcLgtcN77NB
o6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3oPj1Mqsj08E51zZZNkO+7yNvBdnh
dpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQddVx3GED23bPbTjAOEAX7+wPzuHKJfMs
iJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1wxYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk4
0KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWhouAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtb
EK+kafpToMyV4ikIUmG+0caDKCaCJAOIEY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyD
YUqxoWW+B9cM+9eZi8FnctUHzaqDXFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry
+ta/Gej2OLras8E0UnqrdADjOVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz
6yvub4WcMzHnE76E1AI5g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHO
Z5oniMG6IOUaMN5YwpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhP
aPWMS+HhPk+XvS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDb
BOdKW2PQ5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhK
iocmb1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbKZFSe
VT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7Ro8AV38I
qOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9dfHbxWbhQ5kKZ
C2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6NOP/xxNlhz7W9AKmY
FC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyANFJFiAriWsFC3H+TG+hf6
W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8Kq0Gj4dVTtfzALNX6U7VC4Ec
SZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7ILVDPsdSQAt5TvHf5FgaPaGOUR18w
V/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZT
QFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9ApBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFl
OGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+fIMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhq
ZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0
iGmihBwJWmM1g7Lg/Ez7WssPWi2aqd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E
18P/Efi9CLgREA26guYSxsXgfJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjb
gPO+rBMTQW7pKOh9BHLLvS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5
A9D3MW1wDQNrAfOt2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3
c3Nzc3Nz+yPe31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQb
KK0GkSAKaN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdA
d95znXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3RsI3
ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd5PFyMshd
RbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf20X5I35bwMtEA
Oc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRbQafI6+TvQVsjYrkJ
4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhhWk/lHmgtxWeulqCOsRfU
7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0CwHvj4wVHSngv9xjhn8zuN3h
2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skGheG635MJj9aA9YTRqq2DwgWL5gZ9
D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5WubVoOanDkzoTME3vCYKY0Aj/xyTKWv4c76
t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5ubu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4
iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQMmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1
E6H02Obtys8F342hUb71wVnN/2WR5SC2as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWn
P8mQfdTxOGgP2DZnXXFWAWePzA5x34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y
86+t4DiddCJ9LmjbssyuD8BVU74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3
AqZr9/gGRHVRTGsEoqe62fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7
IU28/SKhHWgX1J9cHcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPH
zPYgxqSPFFdA3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55Icht
lCRugS5Ht1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT
9me1gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy60UY
5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+rKcCH4pC8
EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db/xbWVSM5PaUG
FOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb2QmgdXattvkBG/Q3
pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5TIWhbQDOvMFB+UvIRAerR
N4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NPkIzSS2kSSEdERyJAVNJiXfVA
OS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRSA95+k7vF4gOJdeJfvTwDKSuevH14
FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keYwdnRct0WCFnPk5+lRoKjq2OwVhaUunIF
fSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGK
XJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf
9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYBy/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4
BWjrRIDTCdo1Vz+zE7x6eNbgOOT0zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBt
AVT4oOzXxVeB7q5pZf6ScLnPnfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5u
bm5ubm5/zB9OnHVd9P1M/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnk
BHldQEDAXXBtdHg7KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7V
BZSwYktrXAd5v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV
4c2r+IOJseAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bN
IAbrJ4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVtFdVk
MDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAqqowFsZ5B
YilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKrsbpdbQSap3ZD
PQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZjL/Cp4CNMEuT+aM/n
GgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSeAvMh85PU3dJ9cAyU7ruu
wdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/DYbjz4m47x8fw9PWd/XeiwedM
uWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDifKbuhZGXRkHNslXuV6kF8jVpi0gA
sUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8CpiX2S2C4aCgpfQnaGtWTTWDoFJpaeBSo
V7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pfg35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN
+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8TnUevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAW
jDet7XKiQVmbGpZmAF2kTyvfB6D1cj513QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Q
a2PQbQFXvN9Rv6GQ6nRGahLEzUgekvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOf
X8Dp5dyozoaURnGz3kwB+al6jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6
FYon6A3SeSkIFEno6AziqtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2ag
NBLNyQfSEKmBVBqUh/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjB
XssxxTYQXGWtJazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0v
C9nTc6zpCyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx
+RdIJdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ctZyx4
NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUAjk9yK4L4
QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4zT9BVwhcjyzh
Ed/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50feu8DGK5tlxYQLoj
jRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v7IHEZm94NRWUOP8evk3A
97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBnELw5X1L4CvDN75vtdQJMV/QH
DTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAAjSR/+QcwWHQ6OR/oBks9yAUtUPpa
Gwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQNstfSdGgd0qHpC2gltSechDskprs+glE
GaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9v
LqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/B
nuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5NbwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1Ma
vikIdalHnT/Qv979gEdOTk5OTg7U21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqq
MGTIkCFDhrz/D5BVq1atWrXqn4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFy
itsm2n1AacAGMQNYS7w4BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3
FHSbfBJNRsCXRpIetENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+s
Z9LTgCYuV2pbeLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C
7yGWwdlW8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVok
vMy8d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEgSvOK
WSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxVx6gXwJUp
7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71Bmo2TvuC6Kt5K
PiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/whtyHuhH6mpBuzfox
2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D5qOVdSWD64pYrVsMhiuG
XVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYUWVBkAfw85ecpP0+BOhXqVKhT
AeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfIwAoDKwys8Oe9/l9NXBPXxDXY2XRn
051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt524ufLn66+GmoVatWrVq1fn/5ChUqVKhQ
Ac7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl
0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byczn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgA
OHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8
FMR90d7pDfr5+qOeHcBpSu3xsi9kD7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTF
Xl96BL6i5BjvgqB/qZxO+hDUyXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwn
DGvNd0AqqQYaRoLutHel4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TP
ATlNFywNgKxlb1ak3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXS
KoBI0xJwgrCKQcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaC
uCS+YTuIg/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAag
ptijaSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD/YCk
Kj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og96s/AH0xa
fXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYPt2BItSHVhlTL
S2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u627rbuv+NgH6rfjl
B5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgsBovBoC5Xl6vLodTZUmdL
nYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkns05mnYTmC5ovaL4A8s3MNzPf
zD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225ug0unL52+dBrqUpe6/0U9X058OfHl
RBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6LV1cSJsEvF/cfO/McTIcNNvNXoFUXTVkK
RBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3Q
vQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao
4AE1HzVy1fMB44rgnMiKkNLGttZzH0gur/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxv
MgtZfCDjI8u57J/B/tDjc59KkPzGu53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ce
Df0AXNUdDrsK1g/eNkq/B4W+jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G
3RFRVGsGpsVyT3kV6CtTWP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7Nb
hIH0hWu36xY4Njj7u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgu
gBIkZFEUdFflnuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTW
SO3AMFDqRjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqu
rwzeH+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38IfR36
OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgntEuD2j7d/
vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz2cB5yXnJeen3
v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJEiRIlSgBDGcpQ4AY3
uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwYbHq06dGmR7C14daGWxvC
8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz5syZM2fynn8y9snYJ2PhZNGT
RU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfhd2fEnRF3RsCuSbsm7ZoEL8a/GP9i
POx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/HHx5xlg3yao+B0GBnBWOd21DNXCm9UDuw
Oh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhC
Fakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SOO1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73
W4D/EuMFwxLIrKwv698UHDuNelMiOFMdUzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lH
GMHw0KdPwDLIDbA8M7QE61JTTWM9yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8
iwZU8f8UnJ2yI23FQb9VO+66DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJ
b8GwWVfOcBxMM/UHDCXBMcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC
9HetAhGgmoU3uJppjygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJK
jnxcag5qK9FQGgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCe
iQ9FTdDq80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DE
fENpAiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycvgfo7
SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/EPpAfyY/k
R6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESlv7//5I7JHZM7
5iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ8Olrp6+dvgbJ0cnR
ydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpapWKZiGdA0TdM0uH7j+o3r
N8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95PvJ8BD3X9lzbcy1ImVKmlAlX
GlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifKJ8oH3rR90/ZNW/C/4n/F/wrk5ubm
5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1axAREREREQEtsltkt8iG++vvr7+/Hi71
v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1DmocxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X
+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+ISdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPA
Ucfx2tkd7DucJZ11QdbkSvIbEDvEEhEGZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYB
aXipVhVc4PNZ47s9N0GwpfWhgR+A7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk13
1RQLym7da7MA+xXNyxoOak/H5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9W
n91z5j487/q47qOeYF/ovcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjq
lq8c7DEcrHbwJaxK3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3Q
TQTXNe20+AI4Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6Vd
wCfiqigKan01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4
VFd+JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyrpXbg
HWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBTOcjZkDtM
1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0I/Iea1e1q9pV
kFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/m1rxbqqH/YL9gv0C
5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d+sfLN3rW6FmjZ5DSKaVT
SifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1L1BxUMVBFQflXWC9G9GucLnC
5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1nPWc9RwkzEiYkTAD8uXLly9fPoiZ
GDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rCMmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8
WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wpluiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKf
s5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpn
lk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWB
x+QLm542gVc1Ys4nrwDbaKLlGuCq7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw
4nXSw6RJ8Nh+6fMLJ+BZ8uMVD76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8q
cjLfd2C4rd9mHAq3H9w7cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y8
4QeVd1awlB0LxRsUeVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwf
mKf5VwXHx/ZLji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt
4v2R3zIw7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcB
K+ncBT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0GjhQh
LEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb0TaiLTyd
+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFxcXFxccBBDnKQ
/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se5S6Vu1TuEtyUb8o3
ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU+/3VFyvFSrES5F5yL7nX
b7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH5ZBySDmUN3XJuNW41bgVTMmm
ZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X56wvL5oHNA5sHQuonqZ+kfgJvD7w9
8PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfXSf7i+TFo5lE7uq0C525dfn45BGxeru72
6lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZrN9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8
cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYep8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GX
gcs3NdjSDoylwvsWqg7+HWpOKvkLONdnf2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36
CuxHIroWGA8v92a/theHZwUuRV44Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZ
Z59+Gbyc9mZRTEeIO5X0aXwW2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNc
YUIv7kPGzuxo+4+w75cjB0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qD
T2vfix4lodub9t5tqoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1
OrdGQOrKtFGp/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2M
mKEVA22QJrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEi
UCSBWoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9oNzc
cnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm1ZtVb8Le
2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCCEu+//tk9sntk
9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m8ZnFZxaDT0Ofhj4N
oerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pSVamqlLf9VsVbFW9VhOge
0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c6Huh74W+UCy7WHax7Lx4745L
o22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269GErZStlK2SCqR1SPqB6wK2ZXzK4Y
4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd
4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNS
n7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6
vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJT
El5Nva2/ehRelrg974YFUl5oE+kPuqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLh
o60FR3m1jLYPlDjDFIMF1IJqD9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5
qqme1xawVLeGak1BHem05Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3B
Z5xPCc9zUHZv8bji/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfB
ccrxNH0PiAeugY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD
1l59S35goXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0n
nRFZQF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUsmD4x
fWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1q9SvUh/2
3dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39behZL6S+Urmg6Ld
i3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk/ceLSopKikqC5NnJ
s5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/PfJh3QfFurnuthbUW1lrI
b444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/6ino5ub230S6dOnSpUuXhKhe
vXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2xrlhHWk8orCuypdQxSOyS3fH5Xbg/
70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0CP6PPC/8C4H85aHrIS1AXieZiOqirUs7d
fQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15
EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhDJOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSn
V5IGZ1ggt76H2fcc+B7yDPD8CuzdrOuslSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb
0KbLtbQUoI2qF7XBMd0+yzkNxBFRT+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEdu
B/IFeYBUFaQp0hKpF7BeMtMLHGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+S
tCzQJct2XT0wDNJflKeBOkc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcM
QveEhgRvgXyDw46GF4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6
roHQi9b6ieDaqNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY
7mzg6gOuyfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFl
oKR4tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX25fb
l0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c06aSTTjrp
vGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQnZtwLvDGr2fW
Q9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfFnthIeHr3+fzodWC+
73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3oJhqHp/pwGPxOSuAsuKg
boB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2fptkGgbVMlpH590FQm4oFiz+E
l8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKiXlHfBa8PJfaIqwKJ51M+T6oNjFNv
ij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGCXti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRH
ykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgr
spZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoMaWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZp
M1I/DDKL6KtGwMuPoqcnnobYVrFfvtoBnvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3A
EmFpaA+EJ8uftHpogLJSrSIuQnIuZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYm
riKc+fxCiUsfQsycV7WjNkDGXzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7h
nitgXNT7GL9AzJKEOYkx4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA
3GZuM7dB1biqcVXjwJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR
4EoxsA00EouPguCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4Mt
kHdLaKPiN+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZ
lDJOQkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7CawTMwV
OiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADynllQrw3K
APE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdSV7kD5kDjrnkO
xOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJgelkvq4CYZp4U50F8
L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMnopyFq5YuSL1aAj92xxNoW
6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+BC8evT7+WoHYbxO/i1sBrE0Y
oC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasPAqWJOl6eBLWB8qXNH7THlr3yKuRw
h7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/ocdXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/u
aP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumkk046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P
9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xkboDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh0
4lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8
dsaOFAit3TZrlxxgn5k7Z2kH2HbmquSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGC
cSDzrYgu8PDuxXmXdsOTUtdKXckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNe
z2McA/Gd+EmtBZ5IVybPF6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0
ZolYBba2ts9UfxDVzZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RI
MN6XsfIm6Iv0CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gB
GGKj+A70BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7
ymvW5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghvAQGf
+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8C94+cV5n
jiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARFwqfxzTP0HgF+
Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazvg/u1Z7OeCGKpZrd9
BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3ewgwDz/svyt0cDfENdgzb
5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQRz5TmELDaUdg3E8hA/ZlRBxLP
JmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4sQRaQzeUd2QtEJfZxA0Q1WuAC+aX8
SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2eUa8EpsW4LzeDvGYW4zqIQOWxkg9kD3lK
rgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7MZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke
5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/Wulp
FOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1
CXgyePq7zwHNzJFiKih3lQvqFtD8NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1
iGWAz0WwnbXFBGYBadXClW7gTnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olz
wlev6qeMgkznLc2LFIMeQY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs
7FPk88fg2pOyWZyEU112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwq
PBLMhuYQYxEoG0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUI
PDNeToo7DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3Z
mXAQki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssMohh4
X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN1CxaZ207
yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2ahrRoGzSNGU/
UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ksn4FYqnxghoP1pvWa
+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUOMEfIT7QvQD40n0sVon6I
GRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZb/mN/bvDO5100kknnXTSeZe8
deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vfgFudHt28nx9evHjp++w+KGuseTPk
gJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJYynhISEo69WIN+Md7NvtOhGw9slTL1ACC
y4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tBOWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjv
GweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDgXFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wz
ZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3ijTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh20
0cpp9TMQEcogMRm8ZfV2ehEQm6giioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CH
iCAEmDnN3XIxyAfKCh7zX+8f3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPl
TRDlRX4RCOYnZlGzMYhZvC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhD
bZCP5RwZAvSUuc1zIK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPL
uyC/li1kTpDH5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9
l52iW4LvPft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ec
MlvdLHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDEPCWA
rpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vjonUgw4KM
oXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCqgzvZ+6GxEMyN
ZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXILcwW7cCM56UMB1FQ
lmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6i3CQX5FfmQJmC6y6E+R4
83OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ205AJIHObdrkLaKxkkKvAvGBU
NB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUbMyfIieYrbRVwkm58B1Qhu5kBjBbm
A7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqrlhP0+fpTWoNSWASK3CDK8In5AYjsMqv5
CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywFnmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm
2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ
4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWsXbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGT
o1AJeB6RODHqI/C9Zw21Hof7616+ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0Z
R2dJ1D+E8hern+v9FaQUcVqdg0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx
8CCwdwp/bO0PCR2fjH7wHlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeB
vtBcDuIjkaycBCVazab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBG
UT4Dacqi8iSIb0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dg
NqIUW8CSaOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNa
SOQXm0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh1DR2
Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxVEoGOIi8P
wbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9CoKeTTjrppJNO
Om+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dGZQTfJq47mj/I0wHd
X52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3PTsPFK5e7HSkKvn1CS+Vt
CKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC9eVhoDR1+RyU8uZyMQrMytw1
pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu3/f9RoG6VPlRuQVmoNR4CNYEW3bb
aFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaRBQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWL
paj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0
XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsxsM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kY
LJnULepokCbVOQdGjJzFLTC/ZiTrQD4ww8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCo
JexKJWAB+/kUKMJ88RLED2KEmggiUviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLt
ApYUbbPPSZAVzL3KLTBe6qXYA4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHm
TtDvGkP07hDT49X0pJLw+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwY
bD9nHwUJW9yTExtCRAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzp
z6DInBKrssXAo9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+
v/qsUGizst2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJf
Gq6pZ7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ+iOo
iuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEXgLHETDYv
AhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbYWqh+YDxx3fNc
APOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WCmQvIzXIRDto1Zbj2
PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7ALiqDOo92Sh3AK+clnQfv
NM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJIE7IfEpRcBxxDLQvAWWd1sh2
CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTSSSedd8VbV5xfdo4Od24Ga7Btsr0b
hIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSClV0oe5264Uvr5ugO34U71pyOu1IKE2Fd1
ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/LftT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem
/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZrc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYH
gAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2zDcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcp
jdPmYrA1tRRXHoJyVOuk2UDV1BraObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1
ZXbjLrhWO4emvAJvZ2+Qpyt4i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFy
AiPlKtkfSKY4I0EsUpxcArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6
A8gysrCoCdJijjOXghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0
QmBZpPhaLoB1j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tf
DXJC5ltZovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Z
m0DGI+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf5X7Q
73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7HsxbIwYMCA
AQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fvZLLc/5383X76
pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUGYh+4/GKnwpO2Ly8o
F0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjSZqpjICXG9Deng/Os2TFh
DuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru9wYgk2wuQkBmkCVEZxArRCk1
C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVMXFfaQ8pUZ+2Uz8B9Wd40B4LMLqLF
ZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Ym+QcszlorbV26gegVlSrq7VAGaOMUCaA
SBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoa
KB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7mo80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCU
FVVFQaCW3IovqFYxSf0ItKHqYrUsyBSzsugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5
+Vz+DCKKcWIyEC+uKs1BPaw+spYCz0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oI
E+QB2cX4ESgiKtMElCxaDa0CGPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX
7EMhx4pM8ZmOQc5zER1C/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC
+6/yU8JPCT8lwNo7a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZC
m0NtDrU5BJ/7fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/G
H9nhP8VP/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3
Xdx3MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9SKnq7
JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs/KEmE+Mh
0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7lnOWOhaTaxiTm
g7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKWu6Dt13ppy8HSW/tE
k2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9biRxC5hUc0AxbwMeuAkVwx
k4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPVjWCZr23SpoH8Ue6iIrBJLhYl
QDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGguNtaCaCf6KQqIzqKLehXwECmqgmWJ
Za9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWf
A/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46CrCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs
/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JCvYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQl
cTjEX0rqkpQA3jNGY89OsLVUp5vX312gHog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7
uLi4uLg4GDp06NChQ6HBtgbbGmxLaz/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yH
Dh06dOjQAW5WvVn1ZtW09d27d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZ
smXLlmnH07Bhw4YNG8KSK0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW
0Ug9zj/jXcsVkz0me0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P8
9+1SKzh/ZK831c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8
DG70v9H/Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zc
M2nb/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPaeS4V
Xdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G+b+bt06c
vYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2wlo6dCjxMGhij
gbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHgGeEpaXkFkQ0ibyrn
wPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc1wYogRBb90HR+2XhyaNn
AU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYuMRVkLuOq+RwMRa+jFwazES3N
vSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5EdgXjevGhVADBRdBKBGq04RBYpBdZqD
fGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZY8C61dLGEgLWbBZpDQVrS0sRa00QBcxX
sizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqH
gTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+
jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkOWmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3
kjuD9ytPkNMKeht3jpRPwLUt8de4dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8h
iF/uPk0CRPZ73cNZAaKPOJt5Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu2
37f9vm3akPP8HvN7zO8BP7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFj
Isak3emPyzIuy7gsadsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL
07a70OtCrwu9oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1et
TLtwpJ7AUxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHv
Cnz3P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68tYVvC
toRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz7c+Vtv7U
qVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2IgwJHBI4JBAO
Tj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nuJrubQK21tdbWWgtT
f5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQR8BeS2dQ8plrjPIQv8JI
dhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs/hkgx/mAXpkTwV5B3tMbgOXX
pHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVbCFJOx1gUK0S2cE12noRVt9e3/rIn
EJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHcS32HeQLUjBah9QIxVpRTZkByHufzxHbg
XqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzMVP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHF
piQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7aylJ4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9G
LTmPziCnmZOwg7FZH+ndCMpLsU3sALW3OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQ
iRMWELPEbRqDsp4zLARVV2dyErR1yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQ
nBC0NjQpYx0Ic2f6JUcVCMsaUSR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnG
fn2mezzoQ71RugnmV8YJ/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1
cTQDo76saFSH5HuJ++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh
+s+2jZC0zpOJqSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd
6naq2ylQPlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2Wbus
XYbYybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/qRfW
0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D6Lmg54Ke
CyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RMq8j9VX/4I0rP
Lz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6du3Tu0hkyfpXxq4xf
/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0yN8r8D/aNaR7TPAYu9LzQ
80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJoPPcbDwnT9edGMmg7bbuSBoAc
5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2ik8gAFyv3U2Td4ExUWmpbwGfoRGj
bN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRY
ZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36JfB5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrK
soYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRN
dFR7gznS3IIEsU/8IoqC+qk6TpkKopJoI9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRX
ySdiQElR3lOmgTJZOSBegjpIW61tAeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s2
0ApbKlhOgBatfaglgzZHLaM1BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LL
Q/zE6LKPvoaEQbFfRD6DJOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjn
Pa+9u8BY4A1zjQbDTy/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSP
y5GgvzDWeDeB/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157
svUD0G97uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1l
KVlKlgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j7Xd0
jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqNzx+RWnF5
W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDBQTDuxbgX416k
TWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq1t1ad2vdhe2Zt2fe
nhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusESyxLLEgvki88Xny8ePvf9
3Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9qp//UOP+dPd+2g9c+ie8bncAc
rWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuSD6iRxhmxCDIe9GsQOBEyfpjhczED
LLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU6BkDPPFLIGxA1slOCRneC1zkUwiUbfZh
fAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCy
y5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLke
GKc8VVqA+EndrnwOcgFF+QKUFswTNUHMlS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5
zjxi7gXZXXY3u4I6Xp2lDAKlhdJG1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9
LF+D1lzZpuYFrYg6VYsBzUerptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/
Gaz97HvtOUA2MCeb30FSnleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBY
O1teqSr4Tg+wB5+DkFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7m
nll8JmT+IfvsQj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8
Ck0G3+CAHsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6it
v2n9Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc7nM5
bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVeEH87B/2s
PCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P/Zs6tJ1aqUu9
cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+qF3qlI05xhxjjpGW
SP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/omqbX6GbRzaKbQb6EfAn5
Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2fVM7/afG+W956/c422+GR74u
C2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6X7OM38DNKEuXZ8HwIuFuOzMj2E8r
JQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk1athEBn90OE8BhmaOeoETIXkCgGVvQqQ
mNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7v
OTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYr
OcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKwuCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj8
4rX4ECjPeAaA8bNsbGQA85ZcIzeCfEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1Wfr
K0D5QhujnQTlmvKTcAPjySqOg/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0x
WisPrnHJ2ZNagvkemzzbQJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXU
E9R62g5bLdClHGgmgtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsH
gWuwMznxIljzq3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1Mujn
Xf30M+B6qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepy
dbm6HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/BpD5M
GHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3gWOFY4VgB
X2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/aa0zFMRXHVPzn
9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKVq/+H/hqda3Su0bl3
r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7/FG7wkcLHy18FOyV7JXs
lf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83NNBduTb81/db0tETb08PTw9MD
yhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hOmHJ3yt0pdyG2e2z32O7/ej9I5U39
9F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4
c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56++CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Co
yavubi8ENKO62Ruim2vjEgaBry1koN4clGtGeTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4
CLhu3em8BXElkh0uN3i3aPvjpkKuKyElKvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzK
OibXa0iKTd4QvwmeTH5W79EeMPKJvNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqA
edzcb+4AJYc6QKkIyhpxSZ0P8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2Io
CLdyGx0sBTTsDUA8EIvpAcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL
7Eftl3weglWzZfRpBepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrij
XNWSZwA7GWd8Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwI
cyXIEyJUU0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+E
dA+pGPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWielGF
b9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYibp0Du8jxK
HA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ8/nlMMdC7ks+
quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61BA8RhSMojlj5vBi/8
427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGUMWqDskmrKN4HsVM9LU+C
2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZC+p1MVu1AFk5RFOQeeUDYoCu
ZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPAI3lTvAbpL0+YS4DmopQoD8Z7MruZ
FRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSBMkT0sihgWo1OnhVgmsYl8xjYfrVb7fNB
y2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkEwm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/v
WmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5
TT/rLATmSnfhlMNgrSt9jevguW8EEwfur7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczK
me+a7cFe3FHA7gX9oMeQW0CUUbbKOeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmN
Ca5NYIzSf5UvICi733d+pUDrhY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxx
yS+ddP4f5K0T5+wvwpcqfSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEp
ZY1FsjdoCeom+0SwvUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeB
fd76juYg5tP/dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD
4DnBHPaA3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7
nAPbYNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkto30a
gfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCrgtaaK3I/
qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39LmyPphLzETdArK/
+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g6my0PXoYxDpe9XvR
ETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvryOD3K8SfSpwSmxPs7/t4
rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/hwGUQPyuxY5Iv+F1QgyyT3jic
0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdfzdu/x3l/YgZXFsjRMWRtJsAvv62Q
zyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmUehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567
AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t94B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5l
r/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpHnb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM
1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0fABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuT
rREE/RxeJqcDAvSwatn7QmDTDD9ELAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34K
js/924acAv98wYMzHgKf4YHfh+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd
9l0B6miry+EPNLDN9fkFzHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLa
DyAqqweUPaBFWSLU7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSyw
y3zPpYIn0p0//kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZA
pnyh+YNrgNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdU
KuQZhJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTmZr+x
G4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc2gMc+wNq
8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHUos2WbaFAgaxZ
KnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7Y10a8CkYlc313pfg
XZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVoCKIMHxotQTRWc1IJLEnq
Ml8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0gbHKdeQoMyRf4At+IIuYo0N77
r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKmA42UL6wPQMmrxml9wZigR+AFsxUf
0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N73PXREiZEf86NiPYrtun2dqDvbO9t+MI
+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5
oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiPtHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9
HYPAG+xclLwFXKdTmiTaIHiCfxP/raDmU4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukU
Agpr27VeAHT4u4M8nXTSSSeddNJ5N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fy
J0ja4rE448F0uV7a20H4WMfDHD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZ
unnGgaOhfbX7BiT/fHmcawd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9A
rl0ZBhbYAA/tN5/eygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZV
cmjXwVbCMdP/DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG
2jFrfUdPMNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkD
nJXAW8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1jaakPA
PdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2zHbbVgos
IZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt2ggiUri9JcHd
xlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaII0aivha0VcJKELg/
cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18miY1AJvTXtDxOTjj9B7m
PgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+QYmAuENJIdom0Bs6Zxo3Ifme
UtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE7MlBOzz3IcvH5SoEbwTlgqPx6/eh
SA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwGfbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwF
tJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2vQdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYi
J+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/SG/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uor
n/EgylrzKQfBLOuNdn8JcoyR21sDjFtcNZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw
8Kw1LslvwLPdvcubB6zzNcU2GpQLSnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3
Qe/q6ZHyK6hu5bX2K5iFyC0ugN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0
fPXKuRN8WnuHG8GgzbBUtQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt
27QnIPYaXykVwPOV9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkByc
oMQ1A2t+tZzMA7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+
83jrxNk4rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZv
C2eS2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9belrLW
+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGYj7Qxtrkg
xxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kOZi1PG/dVwKG2
UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaKW1aCPty4Z9jAU8ez
1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRRE5QzYGYy7+hXwLmAFdIC
ZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POMvGA2MXd4J4MZbT4UA8GMZIUY
BpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkpd8lZ4Gnsfu2dBWYrJcrwgHWE9bTt
AehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2NbBJyFjwCQpyhx8G7pufyxUgh+pT9Spg
FvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aST
TjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7Ngki
MgdvlhGQqXCGW8piSH7pMynlNrCX5bIDKJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5w
t2eauyQUexw+uNYT6FOs5bS11yHXuOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF
9o1PWbBp6jTVBsoA5Tj3Qd4TLY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0Fdh
pcGh+qb41gXrOR+PZQTY7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIX
SBga/8Gro5BUJmFHbFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUO
zKmsk3fBXtZ+zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlw
PXdmSAiHlPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6
Dczn5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8YVnA
1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYkgKW1vbHt
KGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoBNQPSvgCW+mGT
p0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2qz/y5//t/Lvj9d/F
lsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Whb0nZEpKijXKvTYj5LPb7
V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzzdSoLIGcP/17hU0FL1AqpX4Hl
olxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3ehWpa84P7B9TppJogcMlovBfFXnoe8
6A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zPQQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P
6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyB
KXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5fNXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yW
B7/OGAG+eXz9/I6B7Ka7jY0g84veamfQtmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVn
p58WuPMUnJNcj2L3g/s9V1nnfNB3efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5Te
SpjSEERlYRHdwWxDOfEL0EyJU6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cK
aKiVtBogigpFpIAyR2uoHQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7Pcp
nrE/mI2VGWobUD6yzrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rt
hBbgPuo6l1gT3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhyb
kXYh7Hqq66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0Fr
Bq0ZtAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafkPZi1
I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/dVVocLHg
9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+zYmCba7VbY6BQ
/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2z69g+HrsKZ3A+MVV
N/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwBxjf6e/IUKM2VetbS4L5m
jHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW77ZVDBz1ZV/RPwBxknDMWgTDN
++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FEzayOQiPAf6Dvr+FfgPmDPsxZH4z3
jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2r
QE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBPs2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6
grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXlYXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf
2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv
2076tgJzjTbMkRsshe0bfKq9u0CNi4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3Q
smXLli1bQrPszbI3yw4NGzZs2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rp
abyr8a7Gu2BO8TnF5xR/8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X
7fDP6ue3y79r912779pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3S
fn9a7tNyn5aD8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/z
qzeNlz/y5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpK
SkpKggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v/0nI
9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJAAGihHeK
WhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0UOBIta7RwsOfR
/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeDtOnVvNPB2Kt/7bkG
Wjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNKguOc766g8WAbbf/eLwos
kbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+61fIleGaaK9VmYGnqkxBYAqy/
+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u8SW/hLCkLPNyR0LIjvCh2QMgZGv4
sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6foVLWK+Do4bcsXAP/+yF5s62G0DZZRxRe
CqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DUVsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2
j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTWBKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5
Gxi9PB7neFAKyIJmHRDzucVs4KYw5UfgKebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+
4jz45LBYZNS7C9TJ+yfvn7wfwh6HPQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOf
lPqk1Cel0oYsl15ZemXpFZh7du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF
5WHFyhUrV6x8d3pJpezFshfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7
SO0haYnOuiHrhqwbAm2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3fu
nJYIfvTRRx999BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym
/UyNnxo/NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue
7Xi24xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k1QhI
mSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv5XFQchCu
xoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78CaHVjfkjpDbKe
e63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzOtRa0Btply2VQY+Ql
mRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauPtLVg7W/v6jcXxCD1pqUI
qIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5YQwH8R6POQjGfX23uARKqLW9
zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1+KutAK9ntvMyeGd4XiR/BpwxJshP
QfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcrgAzgidIe9PpmG4qA0Vz3cXcFW0HrM6Uo
cM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYy
HNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCo
ZgG5DZgkXeIqiMqq1/4tiEuWamY38PWqjfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmt
rFZWp63v3LZz285t4cOPP/z4w4/hp3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDo
Rje6/etOMKkXWEuoJdQSCt563nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8Qc
E6Hqzqo7q+6E1RlXZ1ydERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Z
b5k0/SyusLjC4gpvb8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEH
bGMb2/jrNMrcKHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou
67iswB3ucAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa
82vPrz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvhYq3b
Z17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVKa3FJ+wzk
FHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+OTpAtMdvsrGPh
nPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAXcqkBiB0UUh6Dplm+
s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXpy10aaAlqe2Ul6C/MSPM8
WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOcva19CMhoqYrOgFUGmH3A1ds7
03kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtzzDCIa5b4fnJW4LnxUi4H7aIWYz0I
SoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9
zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVNL8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAn
uGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic
72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKy
FGh7tb3a3t+vF+fFeXEezCfmE/MJDDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+s
vy63ZYlliWXJm283s+jMojOLgredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9
+fXl15dDl2JdinUpBp/7fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5T
h+wf9HzQ80FPqFihYoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jRe
aE972r99P6lTA9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoV
K4jJYrKY/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2N
VxDwje/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQhxA9
8FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui+Ly05rWV
hcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXsq/0Ogdgssmpf
gTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz1NRzgG2pVkWrB+rX
VqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7bPvWrzlY6lg0bQtoxdXb
1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7UkqAky0psL5ADrCdUETw33JiMX
OH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2BfWu+qPlfZDzlfFyKzicjoP2xiDm
ynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4JyooBsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5
GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcboSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8U
ZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVL
lyyFKturbK+yHY7PPD7z+EzYennr5a2XIcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyB
mJiYmJgYuNvzbs+7PYFlLGPZH8uX+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E
3Ii5EQOzi88uPrs4JHdO7pzcGQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+
rT6rHat2rNqxtO6md5reaXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaH
bQ6DUudKnSv1BpXEVN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7v
Wq9ZxmYZm2UsTGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P5
38VbJ84+twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniG
ewKh8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIzW4Os
K8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG9N3eSE89
MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxXAs8+d0XnPVAf
KTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1QajWML8R4PPcZ4Al
AFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYjsERbTM0Aa1fyi2aQNDRx
XPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQnjtofuBN8PfYuir5wbJFW6kU
AREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5BpT+ahl1KhhFZVvzInh/9YxzDwTK
skXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjFYKzXW+sPwZbfOkULBLWlGGoZDXo1Y455
AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeberGhh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMq
k0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFC
Rwsdhenzp8+fPh8GMIABQMdCHQt1LATd5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT
8E3DNw0HhjOc4b9fn/o6qVvTb02/NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN
7fi2+mybv23+tvkhpkNMh5gOsD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+
1H9S/0n9JxCSMyRnSE6YcnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq
1KlTp04dUMup5dRy/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP
+DN/fVP+3f6dzv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4s
LbSrzcqeoNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+z
j3SD4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5XtkO
7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQfbtQ49MYu
J3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6geBQtwV+ACZp
Vn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0WrpwBYwnJWXy8XA8LMp
xJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALeFo6DZtITtH0gf21cYdFA
/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TNUr4tBOSXjJuMpUGP1qoHJoAw
Wxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALKWbWJlAmWry17jCYIG2aNNPQCYVEg
3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsD
dcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ec
Ow60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5
DIx4+73j7134u4d5UNB/poJa1X+1RvU/VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/l
f9rrGhT0n+DIkSNHjhx5DDPOpAph4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0G
L8+Obln3AHSsWuP797tA7vmcVFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj
4TUQRupZ+kLQGgjT5MXAVD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19l
f/R10D/mKXE3xN4oVqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNq
yxMWBaQk6aK0BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUH
JgNoZ/ReWhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzE
AeJo8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfAXT5V
L4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1ang/SupirD
QTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3wjeElkD7wDfA1
g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKsgyyd5H2ghQnLzZNB
/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysOrDiwIqyqt6reqnpQI6ZG
TI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZNBNMFLTXzLHRxRn9d5wS039bu
2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuDGqIvzO4Ckl08EuYGNnFZuAz6Df2u
OA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7o
sCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsRAs/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0
n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxX
rG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLeEK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10b
A0J37XbgI4h6NiTGlgjey55vPN9CvphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsM
fO18G90DQWppaGR8FhyV7d0tZ0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuA
cEv40fQiMJHzgh+sP1m3GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7
hOc+ZD3r7JhTHUyTDDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhc
QlggAgKTNIvwDuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPie
HAXma+ahoQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZ
odLLlV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuCOFWf
Li8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ3WU1CPvK
UC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5O8DV2vm9OwnC
cqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPlZfktW3kwP2FND8QA
RdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinfgDhNdwr7wVBNjrP4QI+X
OmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNXk6uC2NfwrHEDyHZDFVMMmOym
GcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8m2vKZTD0ML8p3QY668dMGvgmKoP8
44EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE26qDwWCYLntM+8CwyYh1EHgG+HsErBBo
o1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegfa98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+
F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVibTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF
8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3DeoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/F
vBfzHixlKUv/0QV1qcu/URL5r/qf9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577Vc
iJ9VOrNWFLgPCOPFuyCW9SxznYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2
Bj2ZD6UBIHzGEf87wAgxTk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6P
AO2g8r7rU5AOWxaZi0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8S
NxyML5qnhrwGOV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO
9Bh1sBIC3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqeh
sh3EtfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3fS/cg
LM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0wdxbtnAOv
xZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0JYWmOKNP7EO61
lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWFpeJZyDqUEcjZC2E7
QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFBj8efTpzvN3EOMLaH8Mz4
fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7emlnAJLWBfyqIy8SexpGg6srB
rJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8eNnRbDjx6umembugd0afeS89CyGz
m2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/MtgulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3
ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+sU023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8Q
Ks4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFDQS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlri
aPBleW+4h4A+0Rcv2MC/hQqm78H6uvVoaFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3Bf
AENV+TPPJtBDAzGeWJBek3poT4LdYR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73Vw
vZa/L30PRO6KjLV+D+ZmhkzxfciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUH
qC39zfJvgulJ613DaMitkfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8J
xqetqy0HwVfVH+lNANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA
4LetE3dAYKnaV28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i
+buHd1BQUFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+
Fb4UNwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO96Wd
IF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuHrXhlsNQJ
GRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B3aF86YsEb+Wc
vRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJA+ublnXmIuDPd77p
nAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DYJRXVuwK7qeM3gatc/iKl
C6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP17sl6/gsgYRgmx4H/vNZWKwf+
K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyoNADdhlGPAfmEcYI8B/Qs0jCB+oM6
S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/
5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEB
iEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoKCgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVB
U6yRYkfwt83skt0QxK/Nm0xRICq8rySBOk8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzP
xYfomyC/c94mXxEI1cIuh80GTzP/D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILY
Kqa0+TMwfBweEvMscNM2MawC+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeT
Cs4r6UVudwZPMU+7+M1gNlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/
PVC/VndKFhCXaFOkNuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0F
MV6YbNwJHBNKe78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQ
RweG+p6FwFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4j
UCQq5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQiwxm
zZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+qAkIttbGy
CDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCgoKCgx0n8sw1I
t/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3QKmQH5v/IqTXPn3w
2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZJeNOiMuIbRPyOvgauMq6
3gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVbZdD3SPsNkSDk+j92doDS5uIZ
xfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GNlaqaJoHniDDU9i5cnJ/0UfZYyBvm
i9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus9OS24H7LfTd3Kahn/a+5zoD5PVNAagzW
osa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsG
lnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTsdgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqm
gnLGv8h1CHy9PG/53gXfi/7VzgiwbpOyNQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+Ipe
CbQ0mkp2EMeq4WoEGMoLHcT5EPVqqCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhK
GV6V5oPQRUokDPy5gZvql+C/6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX
/S3BleVp7twBvhxa6X6QQo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcT
X4h0g+mc1l8s+ncP76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1C
fA1+nLn/wvqnoUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht
9fqWi2DYb3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSI
O5NgAOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O+nwt
RKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dAQQSxtt5e
HQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUKtNX7Q86p7Lys
geAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhTcLt/xorMNyC7t2u+
9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3cc712MC6XIqUfIO6bsBrm
iSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJZRIpDr523mm+KSAtFyaLyZDT
My/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+CJSril/7HJRx+hYFENfrMw0/QbHo
sDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSKX/peaQHVeXonB//uYR4UFBQUFBT0OPzp
GecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3I
CpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8X
vHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZqr4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupT
yJ+hJ+uh4J6cNStjARQLjdgpVgbDFsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN
+BHyxuodZAfkeIRo8wzwfK6MF/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6Pt
oVAsKeZa+HtgDGiLfRpIAfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+s
fgW2btapjtLgnuBq4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqW
TmuLoFj96JVRaXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBl
cdaS8sG/MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7
i6t1bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUyl8p+
AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57zffZz4NLu
WVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKgpeT/5HkWxPIR
7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8fDsIm9wB5EpAC0k4w
rk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6Hql9VeAnsXfXFMSvgl1Xe
TUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRxxqvRVSHvSb2++h0o7/gauVqD
4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFPOwQljsTPihwCruM+QVkKnin5y3Na
QpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXPdPdV53JwpnhSc7eB97hnuccL5u2mU6ZQ
YLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9YjXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0
GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGlKZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJH
Ka1AT1I3+G+DVo3njN0gp4k6NJAMmujtqqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZk
gRwupqgXwZFm+UQ8A3quPlhPBONGeY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD
1KUyB8qvB0+2ppv6QXR6fKmYlhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKl
SwuP9+nTp0+fPhAWFhYWFvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQ
flI1+Zn+kFik2pannwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6Y
XQd4EPFNQjXQr4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814E
x5l7qy/PAO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBq
Tr3B3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/ntnbnu
+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nahH4N3rK+J
ZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhNm01lgTlK3Yzy
cL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU8Lv8FfQXIWNM7j3n
p+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/ISVMsmMrJS9Qs8Lf11xN3
gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0ivmPYaF0NeD+cB7yhwnDJvMayG
hPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfIfcIEp2vcbn5L//sGduPGjRs3blyY
QBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzLL3D16u3b2dl/Xbxy5UqUCA+Ht97q379+
fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xPRITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3L
zMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2iKP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR
5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDv
sEWGjwNNU+3C26D3Er6jDQjzuCjEgFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5
/MoV6DFWyroTDilbKuj3P4KE6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh
3YRjvAVdarWMu9wRbg9e1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L
7QgI7cQD7ALhF8Mc0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEde
U8gemnEv5Qdgvvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUB
JV3MMMeDO8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQ
mZtR/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0EWm9K
0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8GkpWKuYs
q0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRrf90Hw6Ps3bt3
7969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2QWZmXl4gAGXLli4d
FQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRNEODpp4sVi4j4tT+P83n/
2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs83t6A/n8mq+7f93h8vsK4bdvG
xEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQiml3hVRQV8nbmQDCE2JrfSxIcYQY
NoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgYTHpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A7
6qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/
EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmnIHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w
24dObIH80dn709tByJ3IiJgtYGxoMfvrQsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0
V1yoXQBDSeNdxxG4fytvkh4Lvi6ub30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzI
c7l/0i3gK6029JlBLikvFdLBW0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9
yS3vAfCleBZkpYJ6mhm6FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDq
pU3wdwVHTfsFy0nwNgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGO
wbve7wJhgfyytTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+Q
VoVfg9zN/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1
O9jQfkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4uLAwO
Hbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c/nTinPzG
dePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdBv6xf8DUBsZQY
JX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdAC8EhW4GvhK8CZUGt
4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSulz4O98InjrZufLIPbpjRD
4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5NnQrpN+Pyi12BLyH0rsmxYL3
nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q2s34klgazHuksEAUXG+b9FLOafB1
0vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qwtwd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZ
uAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJeALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3
GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoP
IKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXPdTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCN
UXcI3UDtpx8Tb4G8XtIDdcDU39xQ9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHW
WGxF8RGgFxU+sgTAfljsYTwDJd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAF
PPPXfTj8IwW1y0uWLFmyZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L
9dtSO7s9LCwurjBOQdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1
HTIyFOUfnd+1a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE
6JDXHuRvBUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpID
oEUKL4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DMGahe
/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dpamlw93a3
8r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD3mzPGFdpkB4Y
LcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH+jVEVQqpEdISzCfF
COUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+bcpsfxjkf5P7TH4iJB9J
WZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/cn9peHAs81amFQyfS5H+3WB/
wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggLQSrNp7oMxhjjbnk82CvYo02twFbe
vNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubsEpnXQNmlfOf5EaK/jnreuhzi9xWvn3AT
xG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDrsWNRcPTna19d6grp+/P2pXUGZ72srintwD/K
MyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vuu7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrH
Kscqxx9/3wq2V0ddHXV11N/d+0JTMqdkTsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Ze
m3tt/u5n95/77yfo/6aqiqKqoKqqqmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z
+f3g9wcCilK4PXjwo4/eeqtw+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j
24K4j9ufnnGW65axxswAc0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE
8bDQ07ACpN32mJhloL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/Szo
GawVe4H4o6hZDoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4
//EPXU8NhLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbz
lfxvlL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U+prF
cg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBuXzVC6pm0
gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175/OF50XA+5dZ7
rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXzYhBWCvNNJ0DZL16W
loG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9vU1rwNDJ3N34BBSZFr4+
bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98pQbsTzze7szzkN6ITYEfQVtg
nB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmCmrtGjRo1atSosNb5cYlsGdkysiW8
/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af
2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3L
ti7bukB/+tP/736SQf/xFKUgkS1I2f4906aNGNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf
3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUVBQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3
ZNlicTh+v/+o6/+ogriP259OnLOs9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4
RIoB7XOttdYPpNZFR5ZbAuIh62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt
/SPBAPo1Suo24IFu1L8HvRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJH
zTth7dklWVvjoHTHSmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D
5EVy8pVP4EGCfVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfa
aTC0loeJ30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+
2T0S/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F7kU2
i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpcuvMx2OOZ
pnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V4Pb41FYPhkG5
F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2vg+OvnEq43R1SLms
V9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHixIkTJxaeHz9+/Pjx46FE
iRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUNGzZs2LABMjIyMjIyICoqKioq
Cjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn5u6su7Puzjo4fvz48ePHC8MXPC4u
Li4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQoVZWqSlWYkTsjd0YubC66uejmolCmTJky
ZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0WdpkaZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w
++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFr
xq4Zf/z9ubHmxpoba2B66emlp5eG8+fPnz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe
8LThacPTHl3b/7DNaZvTNqdB+U/Kf1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiS
viV9Szo4nU6n0wk1F9RcUHMBTJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5
oeeHnoc2MW1i2sQ8vnH1qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z
+32+gpng385IV6kyePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv
1i3Iy7Nao6LAaHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvt
zYgPx33c/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsC
aMNyW6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4flL7
luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5EhblTw7RI61
fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUzJhVi46JioidB
pDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5H4S+YCirTAebTfrc
uxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjteBUNwk6b+pcKAWsTw21L
f+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc3Ku9SfnNoHRqzPHi88H2vpwW
vh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fgbZV/PmAHxyaLKo4BY2v9Y6UEZFRJ
eeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHuobzz7uJQ8UTF80USoGTXMkLJb8F0yNQn
VAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyf
O++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJEyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6
ggTmUV/1bym6peiWorD80vJLyy8VfsVebm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPU
D6Hr1K5Tu06FnF05u3J2wcw9M/fM3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oeP
jpO7O3d37m7IL5dfLr/cv9+P5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlh
zwx7Zti/3s7U7VO3T90OJwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8p
flP8Jni35bst3235z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/
vjJ8ZfjKAN84vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7T
uHpc7+v/Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1
K9z26VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QIqUAa
Jr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqIAN1NSQRA
QgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID6U2mQ8rqrBrp
D0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4cfXutrvWws6O+7PO
bgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ9lsOOHqCb2vWK2nnwD/c
ednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn5mG3COlfZg9xfQkPWmdsy/kG
zCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1LFjPmd4wxoM/RnmdhuAdpt7KTYVc
MbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdztAiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJI
H5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODIjtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLn
GTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGTbWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuF
zYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0Ct
ZxhpOAN003xCd2Ct0FyoA9Jz4alF40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbD
tc4F7RS0WxDnX22/IIFZu3bt2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03
dt3Y38zgPnz9n1WkQ5EORToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJv
ht8Mv/nX9+Phkpqh5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9
G+VJBc+7wMxZM2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n
8bZO2Tpl629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW
5BosPrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpUq/b7
9gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6tlYehHhu
6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0eJm8GVoi9dS8I
n+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKmhSC1NW3Q1oHwjCzK
rUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgocRqFRycYQ5S3hVn6ECE/E
iLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCkR5ioNof1T2iVyYMTNkPd0oNB
25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e2jZwp+SNTs+BQKQvJL8j2GuY20iv
QWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC
6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNBnyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/
Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtOCdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVf
BHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3uaBsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH
+VNQ5G7Rj0sdgbDXw0fGLwV/28BUqTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR
7jmyR6QOAm2GMTJ0GDBffVl4E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxa
sXHjxo0bNxbOCP/R9ZgLapsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQ
Tgonhd98Na4N0AZoA37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAE
JzgBdKMb3f746/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E
/6PvzweJHyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16Qm
NWHzzM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBbt1q1
ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/YGWfzcVcD
uTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNAHCItQgHKaudZ
CPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGmHiRt9E0yFoUrSzLH
6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWET8WODAblTTXTuwwC9QNL
vSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2WdcZDvIyhpid4dEQPlo8rVDzkF
1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3MseRJwRavJNAg9Ffpz5BiIHZfoK5EL
ifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30NqfvTOuZch3M7L5dL+xByt3pD/CvA1tfe
OiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUUy486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSA
MgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEH
QBVxWatD1IionxzfwJPnypVNOA+h4baPQgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/i
Cyjbo3hGORkqHKpYv1YLsCeFfJf4M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvn
T7x46hSkHsrqd/MoqBHmapZU0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtN
lb2Pb6AWJLDFixcv/tsPkoL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDC
gQowadKkSb+txWvRvEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyX
Zr80+yVYKCwUFgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYR
thG2whrnGsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPt
wvYf/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86vnfv
tWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3+fm/rtf8
6FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG6ufg/NwbuZn9
ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08tSkLzledeTk3YO2s
dec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf4CVqC59D4Cn/Lf08iH6p
HTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5Kr5v3wglXzctPDsHskqHp+aM
BvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7NE6/a34Z7FczNS9wD7Xbe7rQx4Oua
2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAsoXf0tIG1nTrQwAFzFPBfVXHDN0p837AYx
Ri6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwno
s4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKl
Y2IrBCB0onQg/mWwbQibhQ+Uyq4zTglSRiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+
okHIfLCPdxjCVoH5A/tsSyXw5ftKCXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQ
vu72gOsmyGueq90pAx6MhvBPQR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTx
LeAZ2ujV/88g6fT4BmxB7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gN
ozaMglEZozJGZUD0neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej
70bfhTTSSHsM/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1A
faA+UIcHox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWI
eqTwZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/HX/h
zY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2h1Ue3n/U
4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv/uST/2iCpyDu
4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFfjPsFjw9sxvB5EYtB
vaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75KfQWE3oYnDeXhZon7SRdW
QPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5GSo8iN9gSAJrd2tRDoJaQW0t
PgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36sBUBviiAkgHhQF5V3wF/TWTGvMxiT
De3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W
3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXRlqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMv
g7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y
/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfE
KEsVuB2ecfv+cTDUk3da+kDUujA1thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8s
r7Tehpjc+E02BSJaRRaPygTDEPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW
0n4y7AJnVEpOSjfwrcwedC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDo
E+gZaAeBQ8pq31lQZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F
4cOHDx8+/K9PnIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OV
Ks8+O2MGVK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0D
k6lYsfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GOHDly
5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH546Dtj1g
XGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c97jmkLnAXcc9
BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5jGHBSb6VfBHGysEj0
g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bIKND8asdAKOidDTPU1aAs
slRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbUmOM9Bm+crfnuhW/hl+X7Lp36
ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTCd4TdjmgIYWdDy9ltYGkdeceSD3p9
fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW
9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIW
MC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN62
0z4BAobAKmk4uCbm/uh7EvI3+C4HngXJbM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSs
u1/10kYIxOvN8uaD9rH+tvAe5JdwV9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/
RmBEIBL0idp2dTrop9X+gfqgBgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7
wV8U/M9UsOzcnpV7Vu5ZCQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6
j9Y5/lf5/f+4Ztjnc7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3a
z+xst1tRIDTUYpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTC
uI/bn06clamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcM
y83dDG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArCFLGD
2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx03IyrCYbz
9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG78Kz5Sr0e7of
lJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5W80TIfRLR35UNIQk
hawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QXy4CS6NX0LSB/Uiq/WBfI
65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9FmwY3gmYSqkzTS2TX4ZQvbYD9km
Q9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1ls/01CPi1ndJT4C8aMBEDOTnpC7zP
QeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfkNr59Mn0TuDpmpST1BeW8sij9I7B1t3+p
fQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2gVNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8a
tBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLph5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9
AstYxjKAoQxl6J9tNSgo6HF44onSpSMi4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHi
ERFw9uydO5mZIIqhoSEhEBY2ZMgXX/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/
+tPcfj8kJPxaQBEWZrFIEmRliaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9H
VSE5OTfX7y+M+7j96VKNB40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/Te
HkdCIG+O/pVcDYpcbVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9
IEGNXFcpF852veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4
Wd+mrwJ9mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqE
W0zOSu9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQL3tm
590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkzgL+M+pHi
Bf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21IIDJbXrPuA+0
zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBMYHsgA9QG0mLhTZBi
jMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmXu0FufprHPxPUE2wJ/AJy
nNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+HhBoIpwGPUH4WVwFvC9uk74A
XdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+QlZWT43RC375vv/3113Dx4rVraY/j
JotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnPPTd27KJFcPr0tWv/aJ3ox6V69bJl4+Ph
xx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t15vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8
wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9bbn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgTh
JCRMNr5cdBBkD3FXzbPDqYyT2qFZYClnNIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQej
hO/vdwN3hLQhcAu2n9hz8btL4Ovqp8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl
8oE/AeSFNDCfA3edPF/WQLi69lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2A
RXzN4AF9pYjWGJgibBVDQIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8
ufk6iJsymt8E5AnaPPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuy
ZmRdhhxnVn25E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ
/QQAmaZaMgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgo
qVwC9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+UvVoR7
i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0q/p9zQDa
Sf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp999o9v4vt/zZ9O
nC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AUTB/HRIZUB8MKZsib
IfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZMze+TBNBPBvyWuJC0Bdn
rksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294HAmsCy31TQN5hirA8A+pRbaM3
GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itFxK0G+xVXpKUD3EjdundNHNjnlUmr
3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8YJXQm2zQF+kX0UFIYgzHQaylRwulwdBY
T1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtAjrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRp
zoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73nJIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi
6LvFfvQD/RVhseACoTFLhATQv+BHcS3oU4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTac
MBwG+XRIo7A7YJlhmWH7CcwO4zrzYYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT
+mx2Q+N3Grq7TwBnEWegyTsQ0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPH
hWHwnXvFnU13wf9ufs4FDyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1Hjt
HGiDlZP6pwCUp8nfPcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+
Fffibt4CuXvUK+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrW
M2YK6B3lm4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymA
b6zrmfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/OA54Q
hodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDgPereCUJe
7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7MeM3VGzI/dZcM
TIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6znAzJBjBGHiU+BGGV4
3/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGqNZAO2oyMxik1oGnxZzuX
bgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDbYogaI1e05IM+jmrmJZBYrOj+
5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0QPzcso9grkHTYvUN/EXZe2PbJfhck
z8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgRhiflX5fPCc45BwUFBQUF/Q/xp2ucg4KC
goKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0EwcQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAf
EEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDA
j4oAAAAASUVORK5CYII=
--20cf307f35329ba8ab04df0a624c--

From rlb@ipv.sx  Thu Jun 13 08:03:44 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D02A21F9989 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yZeyBjvfYMW for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:03:43 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 78B5321F997F for <jose@ietf.org>; Thu, 13 Jun 2013 08:03:42 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n10so4574787oag.28 for <jose@ietf.org>; Thu, 13 Jun 2013 08:03:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=O3a128esH+6g5DEvO8HuQun2DuJqeqDdGIjuaI3Pdxk=; b=APaJnuWntB1hA0gKtlcSyLWMTGAE1/fXRw9rV+wytyz6wXVrB5mXI7rtpYHWbLPzOC vdCLNLA7AxAw7njdD+AUzUIjopqgXyhyMCwlCMSeb6o0Ri52Fr6tVi0HQQuDOroJME9A Q6nCjscOJcfuB3QqDZHTy79iOwJH1MSyUM9rn7R8aGrpsFG4U996KsmAklqk3stQxJQe NdbfWLj/PWil/qodp0R99Ed1QEpbwflPuV+54dhFMeVnP6dil+q+FpXYVVmR1LgNzHVi yNkvLy4WrLArKJ8ehIzaga0kDvFnD0MWdrjwYip1X0ED95IB//yKJj9B2g6nVIqstceq alBA==
MIME-Version: 1.0
X-Received: by 10.182.60.2 with SMTP id d2mr972577obr.75.1371135821914; Thu, 13 Jun 2013 08:03:41 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Thu, 13 Jun 2013 08:03:41 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <51B9DD51.5040000@mitre.org>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <51B9DA50.1080807@aol.com> <51B9DD51.5040000@mitre.org>
Date: Thu, 13 Jun 2013 11:03:41 -0400
Message-ID: <CAL02cgT=m=wvqADRmSku+UphFJayNawWWcYYXZRPisA+YL8iUg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Justin Richer <jricher@mitre.org>
Content-Type: multipart/related; boundary=089e015387dc9ab4dc04df0a6f13
X-Gm-Message-State: ALoCoQlIIeo+RSfWF2O5WHqsq9VjzkNaE4TpevDfshqQKKG/I5dVmlcV3PcYRFP6TE+ErhlMu4Ia
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, George Fletcher <gffletch@aol.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 15:03:44 -0000

--089e015387dc9ab4dc04df0a6f13
Content-Type: multipart/alternative; boundary=089e015387dc9ab4da04df0a6f12

--089e015387dc9ab4da04df0a6f12
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I have no problem with the authors developing the -00 versions of JW* as
Informational.  But then the Standards Track documents that this group is
developing would be free to break with legacy (cleanly).

This group should have done what OAuth did.  Publish "v1.1" as an
Informational, AD-sponsored draft, then work on a Standards Track "v2".
 Instead, it seems that some of us have been under the impression we were
working on "v2" while others thought "v1.1".  Which, in retrospect, seems
to have been the origin of a lot of the angst here.

If we go back and publish a cleaned up version of -00 as "v1.1", would
anyone here stick around to work on "v2.0"?  I would.



On Thu, Jun 13, 2013 at 10:55 AM, Justin Richer <jricher@mitre.org> wrote:

>  +1 to George's suggestion. We know that what we have today will function=
,
> and if this WG doesn't finish its job then the reality is that everyone
> doing "legacy" JWS isn't much going to care what the JOSE WG says anymore=
.
> In other words, there's enough momentum behind the current state of JOSE
> that it would cause a serious fork if we were to change things now.
>
> So let's be smart about the fork. Let's push what we have as "JOSE", then
> "JOSE2" can turn it into the multi-encoded-binary-framework that fits oth=
er
> use cases. And it'll be JOSE2's job to come up with reasonable backwards
> compatibility or incompatibility rules and functions. If we do this, whic=
h
> is what George is saying, then we can actually have some control over bot=
h
> compliance to the "current" specs and compliance to the "new"
> as-of-yet-undefined specs, and we stand a chance of people outside of thi=
s
> working group actually paying attention to what the working group is
> saying, both with the current and with the new.
>
> And finally, as the proverb says, "don't let the perfect stand in the way
> of the good."
>
>  -- Justin
>
>
> On 06/13/2013 10:42 AM, George Fletcher wrote:
>
> I think that in the current situation the issue isn't just breaking
> deployed code but also the timeliness of completing the spec. If the desi=
re
> is to change the processing at some point in the future, why not complete
> this set of specs and then look to add the backward compatibility/migrati=
on
> strategy to an updated/future version of the specification? That's
> effectively what this would be anyway, and allowing other specifications
> and working code to be compliant with the current specification is very
> valuable and doesn't preclude revising the mechanism in the future.
>
> Thanks,
> George
>
> On 6/13/13 10:35 AM, Richard Barnes wrote:
>
> This would have been a nice discussion to have had 18 months ago, when we
> were getting started.
>
>  I don't think it's compatible with the IETF ethos to say "Changes to
> this document MUST NOT break existing code."  Otherwise, we're not doing
> engineering here, we're cleaning up documentation and rubber-stamping.
>
>  What would be acceptable is to say "Changes must break cleanly with
> existing code".  That is, it should be possible for a JWT implementation
> to, say, process both "legacy" JWS syntax and whatever comes out of this
> group.  That way, we could come to consensus on the best solution,
> incorporating lessons learned from earlier work without being hindered by
> them.
>
>  Would participants here consider it a acceptable for the output of this
> working group to be incompatible with existing JWT implementations, as lo=
ng
> as it had the property that JW* objects in the new format could be clearl=
y
> distinguished from "legacy" JW* objects, so that implementations could
> adapt their processing?
>
>  --Richard
>
>
>
>
> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com>wrote=
:
>
>>  +1
>>
>> Breaking deployed code as raised by Brian, Naveen and others is a
>> critical consideration.
>>
>> Thanks,
>> George
>>
>>   On 6/13/13 10:19 AM, Mike Jones wrote:
>>
>>  Jim and Karen, could you please do as Richard suggests and close this
>> issue as =93won=92t fix=94.
>>
>>
>>
>>                                                             Thank you,
>>
>>                                                             -- Mike
>>
>>
>>
>> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
>> *Sent:* Wednesday, June 12, 2013 1:57 PM
>> *To:* jose-chairs@tools.ietf.org; Mike Jones
>> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
>> (base64)
>>
>>
>>
>> In other words: Chairs, feel free to close/wontfix :)
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: *Richard Barnes* <rlb@ipv.sx>
>> Date: Wed, Jun 12, 2013 at 4:55 PM
>> Subject: Re: [jose] #23: Make crypto independent of binary encoding
>> (base64)
>> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
>> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
>> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
>> jose@ietf.org>" <jose@ietf.org>
>>
>>  To be clear, I structured my message in two parts for a reason, to
>> separate the analysis from the opinion.  I acknowledge that I am but one
>> voice here, and I'm increasingly hearing how alone I am :)
>>
>>
>>
>> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
>>
>>  <impartial-analysis>
>>
>> So just to be clear on the trade-off the WG has to make:
>>
>>
>>
>> On the one hand: Breaking every existing JWT implementation in the world
>>
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)
>>
>> </impartial-analysis >
>>
>>
>>
>> <personal-opinion>
>>
>> I have some sympathy with JWT implementors.  It sucks to have to refacto=
r
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a D=
C
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."
>>
>>
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur th=
e
>> implementation pain now, and get the design right for the long run.  Bas=
e64
>> is a hack around JSON; we should build the system so that when we no lon=
ger
>> need that hack, it can go away.
>>
>> </personal-opinion>
>>
>>
>>
>> --Richard
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:
>>
>> I did at first find it curious why the cryptographic operations were ove=
r
>> the base64url-enccoded values, but I was also very focused on JWE, where=
 I
>> think the field separation problem is less of an issue (at least now).  =
For
>> JWS, this would certainly cause problems without some manner of unambigu=
ous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be use=
d
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider i=
t
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.
>>
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versio=
ns
>> > of the JWS Header and the JWS Payload to preserve them in transmission=
,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serializatio=
n,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenatio=
n
>> > isn't an extra burden.  Given you already have that quantity, computin=
g
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should no=
t
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+----------------------------------------------=
---
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+----------------------------------------------=
---
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >
>>
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jose mailing listjose@ietf.orghttps://www.ietf.org/mailman/listinfo/jose
>>
>>
>>   --
>> [image: George Fletcher] <http://connect.me/gffletch>
>>
>
>
> --
> [image: George Fletcher] <http://connect.me/gffletch>
>
>
> _______________________________________________
> jose mailing listjose@ietf.orghttps://www.ietf.org/mailman/listinfo/jose
>
>
>

--089e015387dc9ab4da04df0a6f12
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have no problem with the authors developing the -00 vers=
ions of JW* as Informational. =A0But then the Standards Track documents tha=
t this group is developing would be free to break with legacy (cleanly).<di=
v>
<br></div><div>This group should have done what OAuth did. =A0Publish &quot=
;v1.1&quot; as an Informational, AD-sponsored draft, then work on a Standar=
ds Track &quot;v2&quot;. =A0Instead, it seems that some of us have been und=
er the impression we were working on &quot;v2&quot; while others thought &q=
uot;v1.1&quot;. =A0Which, in retrospect, seems to have been the origin of a=
 lot of the angst here.</div>
<div><br></div><div>If we go back and publish a cleaned up version of -00 a=
s &quot;v1.1&quot;, would anyone here stick around to work on &quot;v2.0&qu=
ot;? =A0I would.</div><div><br><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">
On Thu, Jun 13, 2013 at 10:55 AM, Justin Richer <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:jricher@mitre.org" target=3D"_blank">jricher@mitre.org</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    +1 to George&#39;s suggestion. We know that what we have today will
    function, and if this WG doesn&#39;t finish its job then the reality is
    that everyone doing &quot;legacy&quot; JWS isn&#39;t much going to care=
 what the
    JOSE WG says anymore. In other words, there&#39;s enough momentum behin=
d
    the current state of JOSE that it would cause a serious fork if we
    were to change things now. <br>
    <br>
    So let&#39;s be smart about the fork. Let&#39;s push what we have as &q=
uot;JOSE&quot;,
    then &quot;JOSE2&quot; can turn it into the multi-encoded-binary-framew=
ork
    that fits other use cases. And it&#39;ll be JOSE2&#39;s job to come up =
with
    reasonable backwards compatibility or incompatibility rules and
    functions. If we do this, which is what George is saying, then we
    can actually have some control over both compliance to the &quot;curren=
t&quot;
    specs and compliance to the &quot;new&quot; as-of-yet-undefined specs, =
and we
    stand a chance of people outside of this working group actually
    paying attention to what the working group is saying, both with the
    current and with the new.<br>
    <br>
    And finally, as the proverb says, &quot;don&#39;t let the perfect stand=
 in
    the way of the good.&quot;<span class=3D"HOEnZb"><font color=3D"#888888=
"><br>
    <br>
    =A0-- Justin</font></span><div><div class=3D"h5"><br>
    <br>
    <div>On 06/13/2013 10:42 AM, George Fletcher
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <font face=3D"Helvetica, Arial, sans-serif">I think that in the
        current situation the issue isn&#39;t just breaking deployed code
        but also the timeliness of completing the spec. If the desire is
        to change the processing at some point in the future, why not
        complete this set of specs and then look to add the backward
        compatibility/migration strategy to an updated/future version of
        the specification? That&#39;s effectively what this would be anyway=
,
        and allowing other specifications and working code to be
        compliant with the current specification is very valuable and
        doesn&#39;t preclude revising the mechanism in the future.<br>
        <br>
        Thanks,<br>
        George</font><br>
      <br>
      <div>On 6/13/13 10:35 AM, Richard Barnes
        wrote:<br>
      </div>
      <blockquote type=3D"cite">
        <div dir=3D"ltr">This would have been a nice discussion to have
          had 18 months ago, when we were getting started.
          <div><br>
          </div>
          <div>I don&#39;t think it&#39;s compatible with the IETF ethos to=
 say
            &quot;Changes to this document MUST NOT break existing code.&qu=
ot;
            =A0Otherwise, we&#39;re not doing engineering here, we&#39;re c=
leaning
            up documentation and rubber-stamping.</div>
          <div><br>
          </div>
          <div>What would be acceptable is to say &quot;Changes must break
            cleanly with existing code&quot;. =A0That is, it should be poss=
ible
            for a JWT implementation to, say, process both &quot;legacy&quo=
t; JWS
            syntax and whatever comes out of this group. =A0That way, we
            could come to consensus on the best solution, incorporating
            lessons learned from earlier work without being hindered by
            them.</div>
          <div><br>
          </div>
          <div>Would participants here consider it a acceptable for the
            output of this working group to be incompatible with
            existing JWT implementations, as long as it had the property
            that JW* objects in the new format could be clearly
            distinguished from &quot;legacy&quot; JW* objects, so that
            implementations could adapt their processing?</div>
          <div><br>
          </div>
          <div>--Richard</div>
          <div><br>
          </div>
          <div><br>
            <div class=3D"gmail_extra"><br>
              <br>
              <div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 10:24 AM,
                George Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:gff=
letch@aol.com" target=3D"_blank">gffletch@aol.com</a>&gt;</span>
                wrote:<br>
                <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
                  <div bgcolor=3D"#FFFFFF" text=3D"#000000"> <font face=3D"=
Helvetica, Arial, sans-serif">+1<br>
                      <br>
                      Breaking deployed code as raised by Brian, Naveen
                      and others is a critical consideration.<br>
                      <br>
                      Thanks,<br>
                      George<br>
                      <br>
                    </font>
                    <div>
                      <div>
                        <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
                        </div>
                        <blockquote type=3D"cite">
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">Jim


                                and Karen, could you please do as
                                Richard suggests and close this issue as
                                =93won=92t fix=94.</span></p>
                            <p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">=A0</span></p>
                            <p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0


                                Thank you,</span></p>
                            <p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0


                                -- Mike</span></p>
                            <p class=3D"MsoNormal"><span style=3D"font-size=
:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497=
d">=A0</span></p>
                            <p class=3D"MsoNormal"><b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</sp=
an></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot=
;sans-serif&quot;">
                                Richard Barnes [<a href=3D"mailto:rlb@ipv.s=
x" target=3D"_blank">mailto:rlb@ipv.sx</a>]
                                <br>
                                <b>Sent:</b> Wednesday, June 12, 2013
                                1:57 PM<br>
                                <b>To:</b> <a href=3D"mailto:jose-chairs@to=
ols.ietf.org" target=3D"_blank">jose-chairs@tools.ietf.org</a>;
                                Mike Jones<br>
                                <b>Subject:</b> Fwd: [jose] #23: Make
                                crypto independent of binary encoding
                                (base64)</span></p>
                            <p class=3D"MsoNormal">=A0</p>
                            <div>
                              <p class=3D"MsoNormal">In other words:
                                Chairs, feel free to close/wontfix :)</p>
                              <div>
                                <p class=3D"MsoNormal" style=3D"margin-bott=
om:12.0pt">=A0</p>
                                <div>
                                  <p class=3D"MsoNormal" style=3D"margin-bo=
ttom:12.0pt">----------


                                    Forwarded message ----------<br>
                                    From: <b>Richard Barnes</b> &lt;<a href=
=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;<br>
                                    Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                                    Subject: Re: [jose] #23: Make crypto
                                    independent of binary encoding
                                    (base64)<br>
                                    To: &quot;Matt Miller (mamille2)&quot; =
&lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.=
com</a>&gt;<br>
                                    Cc: jose issue tracker &lt;<a href=3D"m=
ailto:trac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.too=
ls.ietf.org</a>&gt;,


                                    &quot;&lt;<a href=3D"mailto:draft-ietf-=
jose-json-web-encryption@tools.ietf.org" target=3D"_blank">draft-ietf-jose-=
json-web-encryption@tools.ietf.org</a>&gt;&quot;


                                    &lt;<a href=3D"mailto:draft-ietf-jose-j=
son-web-encryption@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-w=
eb-encryption@tools.ietf.org</a>&gt;,



                                    &quot;&lt;<a href=3D"mailto:michael.jon=
es@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;&quo=
t;


                                    &lt;<a href=3D"mailto:michael.jones@mic=
rosoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,


                                    &quot;&lt;<a href=3D"mailto:jose@ietf.o=
rg" target=3D"_blank">jose@ietf.org</a>&gt;&quot;


                                    &lt;<a href=3D"mailto:jose@ietf.org" ta=
rget=3D"_blank">jose@ietf.org</a>&gt;<br>
                                    <br>
                                  </p>
                                  <div>
                                    <p class=3D"MsoNormal">To be clear, I
                                      structured my message in two parts
                                      for a reason, to separate the
                                      analysis from the opinion. =A0I
                                      acknowledge that I am but one
                                      voice here, and I&#39;m increasingly
                                      hearing how alone I am :)</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12.0pt">=A0</p>
                                    <div>
                                      <div>
                                        <p class=3D"MsoNormal">On Wed, Jun
                                          12, 2013 at 4:23 PM, Richard
                                          Barnes &lt;<a href=3D"mailto:rlb@=
ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;


                                          wrote:</p>
                                      </div>
                                      <div>
                                        <div>
                                          <blockquote style=3D"border:none;=
border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt=
;margin-right:0in">
                                            <div>
                                              <div>
                                                <p class=3D"MsoNormal">&lt;=
impartial-analysis&gt;</p>
                                              </div>
                                              <p class=3D"MsoNormal">So
                                                just to be clear on the
                                                trade-off the WG has to
                                                make:</p>
                                              <div>
                                                <p class=3D"MsoNormal">=A0<=
/p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">On
                                                  the one hand: Breaking
                                                  every existing JWT
                                                  implementation in the
                                                  world</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">On
                                                  the other hand:
                                                  Eternally binding
                                                  ourselves to base64
                                                  encoding, even if
                                                  binary-safe encodings
                                                  become available
                                                  (CBOR, MsgPack, etc.)</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">&lt;=
/impartial-analysis=A0&gt;</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">=A0<=
/p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">&lt;=
personal-opinion&gt;</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">I
                                                  have some sympathy
                                                  with JWT implementors.
                                                  =A0It sucks to have to
                                                  refactor code. =A0But I
                                                  think we&#39;re literally
                                                  talking about
                                                  something like a
                                                  5-line patch. =A0And
                                                  early JWT implementors
                                                  knew or should have
                                                  known (to use a DC
                                                  phrase) that they were
                                                  dealing with a draft
                                                  spec. =A0As the W3C
                                                  editor&#39;s draft
                                                  template says, in big
                                                  bold red print,
                                                  &quot;Implementors who ar=
e
                                                  not taking part in the
                                                  discussions are likely
                                                  to find the
                                                  specification changing
                                                  out from under them in
                                                  incompatible ways.&quot;<=
/p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">=A0<=
/p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">As
                                                  PHB pointed out in the
                                                  other thread, it would
                                                  be nice to use JWS and
                                                  JWE in place of CMS
                                                  one day, without the
                                                  base64 hit. =A0We should
                                                  incur the
                                                  implementation pain
                                                  now, and get the
                                                  design right for the
                                                  long run. =A0Base64 is a
                                                  hack around JSON; we
                                                  should build the
                                                  system so that when we
                                                  no longer need that
                                                  hack, it can go away.</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">&lt;=
/personal-opinion&gt;</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal"><spa=
n style=3D"color:#888888">=A0</span></p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal"><spa=
n style=3D"color:#888888">--Richard</span></p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal"><spa=
n style=3D"color:#888888">=A0</span></p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal"><spa=
n style=3D"color:#888888">=A0</span></p>
                                              </div>
                                            </div>
                                            <div>
                                              <div>
                                                <div>
                                                  <p class=3D"MsoNormal" st=
yle=3D"margin-bottom:12.0pt">=A0</p>
                                                  <div>
                                                    <p class=3D"MsoNormal">=
On

                                                      Wed, Jun 12, 2013
                                                      at 10:27 AM, Matt
                                                      Miller (mamille2)
                                                      &lt;<a href=3D"mailto=
:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;


                                                      wrote:</p>
                                                    <p class=3D"MsoNormal">=
I
                                                      did at first find
                                                      it curious why the
                                                      cryptographic
                                                      operations were
                                                      over the
                                                      base64url-enccoded
                                                      values, but I was
                                                      also very focused
                                                      on JWE, where I
                                                      think the field
                                                      separation problem
                                                      is less of an
                                                      issue (at least
                                                      now). =A0For JWS,
                                                      this would
                                                      certainly cause
                                                      problems without
                                                      some manner of
                                                      unambiguous field
                                                      parameterization.<br>
                                                      <br>
                                                      I will note that
                                                      unescaped NULL is
                                                      not valid in JSON,
                                                      so it could be
                                                      used as a
                                                      separator between
                                                      the encoded header
                                                      and the payload.
                                                      =A0I do find it
                                                      interesting if
                                                      JOSE could more
                                                      easily and
                                                      efficiently
                                                      support other
                                                      encodings.
                                                      =A0However, I think
                                                      that while this is
                                                      an interesting
                                                      thought
                                                      experiment, it
                                                      seems we&#39;re too
                                                      far down the path
                                                      to seriously
                                                      consider it unless
                                                      the current state
                                                      were shown to be
                                                      horribly broken.<br>
                                                      <br>
                                                      <br>
                                                      - m&amp;m<br>
                                                      <br>
                                                      Matt Miller &lt; <a h=
ref=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>
                                                      &gt;<br>
                                                      Cisco Systems,
                                                      Inc.</p>
                                                    <div>
                                                      <div>
                                                        <p class=3D"MsoNorm=
al"><br>
                                                          On Jun 11,
                                                          2013, at 6:01
                                                          PM, jose issue
                                                          tracker &lt;<a hr=
ef=3D"mailto:trac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@t=
rac.tools.ietf.org</a>&gt;


                                                          wrote:<br>
                                                          <br>
                                                          &gt; #23: Make
                                                          crypto
                                                          independent of
                                                          binary
                                                          encoding
                                                          (base64)<br>
                                                          &gt;<br>
                                                          &gt;<br>
                                                          &gt; Comment
                                                          (by <a href=3D"ma=
ilto:michael.jones@microsoft.com" target=3D"_blank">michael.jones@microsoft=
.com</a>):<br>
                                                          &gt;<br>
                                                          &gt; For both
                                                          serializations,

                                                          you already
                                                          need the
                                                          base64url
                                                          encoded
                                                          versions<br>
                                                          &gt; of the
                                                          JWS Header and
                                                          the JWS
                                                          Payload to
                                                          preserve them
                                                          in
                                                          transmission,
                                                          so<br>
                                                          &gt; computing
                                                          them isn&#39;t an
                                                          extra burden.
                                                          =A0In the JWS
                                                          Compact
                                                          Serialization,<br=
>
                                                          &gt; you
                                                          already need
                                                          the
                                                          concatenation
                                                          of the Encoded
                                                          JWS Header, a
                                                          period<br>
                                                          &gt;
                                                          character, and
                                                          the Encoded
                                                          JWS Payload,
                                                          so computing
                                                          that
                                                          concatenation<br>
                                                          &gt; isn&#39;t an
                                                          extra burden.
                                                          =A0Given you
                                                          already have
                                                          that quantity,
                                                          computing<br>
                                                          &gt; the
                                                          signature over
                                                          it is the
                                                          easiest thing
                                                          for developers
                                                          to do, and
                                                          it&#39;s<br>
                                                          &gt; been
                                                          shown to work
                                                          well in
                                                          practice.
                                                          =A0There&#39;s no
                                                          compelling
                                                          reason to make<br=
>
                                                          &gt; this
                                                          change.<br>
                                                          &gt;<br>
                                                          &gt; Even for
                                                          the JSON
                                                          Serialization,
                                                          the only
                                                          &quot;extra&quot;=
 step
                                                          that&#39;s
                                                          required to<br>
                                                          &gt; compute
                                                          the signature
                                                          is the
                                                          concatenation
                                                          with the
                                                          period
                                                          character - to<br=
>
                                                          &gt; prevent
                                                          shifting of
                                                          data from one
                                                          field to the
                                                          other, as
                                                          described by
                                                          Jim<br>
                                                          &gt; Schaad in
                                                          the e-mail
                                                          thread. =A0So
                                                          this step
                                                          isn&#39;t actuall=
y
                                                          &quot;extra&quot;=
 at all
                                                          -<br>
                                                          &gt; it&#39;s
                                                          necessary.
                                                          =A0It&#39;s also
                                                          highly
                                                          advantageous
                                                          to use exactly
                                                          the same<br>
                                                          &gt;
                                                          computation
                                                          for both
                                                          serializations,
                                                          which is
                                                          currently the
                                                          case.<br>
                                                          &gt;<br>
                                                          &gt; Since
                                                          there is no
                                                          compelling
                                                          reason to make
                                                          this change,
                                                          and since
                                                          making<br>
                                                          &gt; it could
                                                          enable the
                                                          &quot;shifting&qu=
ot;
                                                          problem
                                                          identified by
                                                          Jim, it should
                                                          not be<br>
                                                          &gt; made.<br>
                                                          &gt;<br>
                                                          &gt; --<br>
                                                          &gt;
-------------------------+-------------------------------------------------=
<br>
                                                          &gt; Reporter:
                                                          =A0<a href=3D"mai=
lto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a> =A0 | =A0 =A0 =A0 Owner:
=A0draft-ietf-jose-json-web-<br>
                                                          &gt; =A0 =A0 Type=
:
                                                          =A0defect =A0 =A0=
 =A0
                                                          | =A0<a href=3D"m=
ailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ietf.or=
g</a><br>
                                                          &gt; Priority:
                                                          =A0major =A0 =A0 =
=A0
                                                          =A0| =A0 =A0
                                                          =A0Status: =A0new=
<br>
                                                          &gt;
                                                          Component:
                                                          =A0json-web- =A0
                                                          =A0| =A0
                                                          Milestone:<br>
                                                          &gt;
                                                          =A0encryption =A0
                                                          =A0 =A0 =A0 =A0 =
=A0 | =A0
                                                          =A0 Version:<br>
                                                          &gt; Severity:
                                                          =A0- =A0 =A0 =A0 =
=A0 =A0
                                                          =A0|
                                                          =A0Resolution:<br=
>
                                                          &gt; Keywords:
                                                          =A0 =A0 =A0 =A0 =
=A0 =A0 =A0
                                                          |<br>
                                                          &gt;
-------------------------+-------------------------------------------------=
<br>
                                                          &gt;<br>
                                                          &gt; Ticket
                                                          URL: &lt;<a href=
=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" target=3D"=
_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;=
<br>

                                                          &gt; jose &lt;<a =
href=3D"http://tools.ietf.org/jose/" target=3D"_blank">http://tools.ietf.or=
g/jose/</a>&gt;<br>
                                                          &gt;</p>
                                                      </div>
                                                    </div>
                                                    <div>
                                                      <div>
                                                        <p class=3D"MsoNorm=
al" style=3D"margin-bottom:12.0pt">&gt;
_______________________________________________<br>
                                                          &gt; jose
                                                          mailing list<br>
                                                          &gt; <a href=3D"m=
ailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
                                                          &gt; <a href=3D"h=
ttps://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">https://www.ie=
tf.org/mailman/listinfo/jose</a></p>
                                                      </div>
                                                    </div>
                                                  </div>
                                                  <p class=3D"MsoNormal">=
=A0</p>
                                                </div>
                                              </div>
                                            </div>
                                          </blockquote>
                                        </div>
                                      </div>
                                    </div>
                                    <p class=3D"MsoNormal">=A0</p>
                                  </div>
                                </div>
                                <p class=3D"MsoNormal">=A0</p>
                              </div>
                            </div>
                          </div>
                          <br>
                          <fieldset></fieldset>
                          <br>
                          <pre>____________________________________________=
___
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
                        </blockquote>
                        <br>
                      </div>
                    </div>
                    <span><font color=3D"#888888">
                        <div>-- <br>
                          <a href=3D"http://connect.me/gffletch" title=3D"V=
iew full card on Connect.Me" target=3D"_blank"><img src=3D"cid:part26.07050=
304.09090705@mitre.org" alt=3D"George Fletcher" height=3D"113" width=3D"359=
"></a></div>

                      </font></span></div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </blockquote>
      <br>
      <div>-- <br>
        <a href=3D"http://connect.me/gffletch" title=3D"View full card on C=
onnect.Me" target=3D"_blank"><img src=3D"cid:part28.09030107.04060900@mitre=
.org" alt=3D"George
            Fletcher" height=3D"113" width=3D"359"></a></div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div></div></div>

--089e015387dc9ab4da04df0a6f12--
--089e015387dc9ab4dc04df0a6f13
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part28.09030107.04060900@mitre.org>
X-Attachment-Id: e928b81dc41efabd_0.1.2

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAACXBI
WXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAIJLiEoIGg
ETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlTp09Lly5dunTp
khC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLly5dB/rMr4ubm5ubm
5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc3Nzc3Nzcfgd34uzm5ubm
5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zFHGHAI0sR61oQpSxdUsuBrcbb
pFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL5KL61yAdzP0l4ytwdrCmZQ0B49ng
q9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5xhJQD0ijlA6g5aoPzQXA2i9znjMWcodl
l8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteBfaB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHn
u0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGz
l2e093YQJp4ZK4D+G+NGeT+oM131tF+h+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRG
mAkCkYsLFwDS//NGKvzbkoT3kJCBAD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o
0AicE+TFUiRou8QMPMH3hee3xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8
I6cn2B8meCh34eGjN6VerAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1
YO1qH6dbCKnhSYG5oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ6
9MW+HWD9Tu2S0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skj
ff0g+X5SBR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBN
v1lcAOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAYlnko
7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm+Bj0TqE4
h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9bF5rQRrpqG3v
Ct5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk00D+UBkr7oI2QPpS
CgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2qwt9Le26NjkA9faXTy79
AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3YG7o/SZiFChhSkm7DkLe+n1t
tYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HBdoFdC68EZ7ajSBEJss5l5/IM7hd6
qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2SiNe1wGvbXI153fwpnrSgWc/ws2y92v8
PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJmfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNp
dxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK6
3RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQd+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1E
j0GgzhSfuayglYmv/7gaaIn2W84tIN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqv
b/8C1AilmagDhgX6FnoPMGzxMnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUC
wLFVHq31B/NoD7P5ETA2O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgn
rBvSZgIG+Yo+GqxDcuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPo
K3/MPEATqdIiQEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJD
QtfUg0mloXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRv
LQkp3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAXQ8B7
LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZPAFvtzIyo
2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yMoDu4grVrTgMo
y8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJfOZ5ZoMXlTEpXQLuY
2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZEGcZ43wHdA+movjR47/b6
RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaBVxGvyrpeYM+yLs/6HuRrzh2u
FPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9lOZgn5ijt9wGfbJezT4I3PY4G1QW
jF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B91zfDX6/wIOlT+LjW0KJbwptCyoOupk6
L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGBLwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZ
EkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNCIWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+
G9grKgnuz35x32cROPa4Clpfgff1xGr3KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0
dTXrCT4p9s2GMVA6uqRnoZXwqFh86hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISL
IDZZ14XPhJK1S0WVXQ5BgUEjfM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJF
WNoq4IDeLh2CzJIZJ42dQL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B
+WN6SPNAVPLqbt4O0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7
gXzJ41LAV6D6Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0H
oqz6hbwIDFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNT
tARzuuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0fXAHU
FPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm5/fdHgE7
D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3cmrwrzUguJ7/
a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBuT9rl+6kw8FSbj3qH
wKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y2BpnVfZ8DSU9ixyt8itU
/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXOMlD/ZOGg5lMhIsn/81oWMP5q
KilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/uv90fnjZ82vBpQ1CXq8vV5VD4q8Jf
Ff4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSpUqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs
2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoUeP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48
kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMoOVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynM
cNSzKvCxstVUFLTLjplZPwNztWDxMcj5fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOm
ZRGIgXYvewOQ+htjlQSQVPtRVwgov9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g
9TblevUCkSLaaS/BVV8NdWWCeaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZ
Lsc8HtRHzkr2EZC9LXt4ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8
W/UqMvUHKHSq0J7gMJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwCl
su4jMQucu5z5HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZ
z1ch9JPQ/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPg
Afh1N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+GginF9
wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe3jjveb1L
79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jUkKkhU0EZrgxX
hv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k6oXAC0jnBbeAGCxi
JVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjCIFfUVQKpirVnVg64ZJrn
GkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQldQaC7us5lAaWqTHxtsB9xzkr5
AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6Rtuuag7JUPisvAGNdQwVjfxClDb2k
AWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBcQxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL
8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/qJoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lK
Qdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJimvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazho
Z0SschLk86w2FobUjm/TMy3gW0ye5TCA+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4
rE8LKwDpxbLnmifA6VZJ+61pkLgk9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULK
Q7mUyAE15oHjpHWXawNkdpJdzvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX
3KOOqVC1TalujUxgf5qdEOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKE
LZegyewqnT8YBj7f2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1j
LZgePz1+ejw0/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yu
v7n+5vrg98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQ
iynrI5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIhs05q
VsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/gi7EEGYq
BLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5llewH2laX3a4H
u5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcgbZIypRagLRXn1Yug
+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0VOoPmZWz96fHgfm8uRo+
kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1B1xTciv4SvDgw9i714Ph8Isb
LTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9EbyrMabKEXCdoXJmAmRPdk55egZi
vk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH41i7Z+BIaFO8VkZzDxjjPajg4CUQ+Cbk
B6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS79fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjt
rYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27Nezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82
fArjt4/fPn47tAxpGdIyBHJO55zOOf238eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHn
jT5vBAltE9omtP1PKvjvI93vRsI7dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjI
yMi7hf/u78O6D+s+rAtd0rukd0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf
7e+9tf9/iH+0HeoV9Yp65benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunL
pi9hwYkFJxacAFspWylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8
bo5sFhACUh3s7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9S
FX0HT0DyNOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNp
i1ffgJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUcTAS4
ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNiephdP6gOW
12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4KmeJcr8gu4urLX
FQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAEF/BbaS0AhoaefZI1
yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4WJkj6SFgn0ePgK/BY4+S
EXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjdvMqREr/AS8vrC1lDISX3VTnh
C35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgykjLn+22FtW0OZGzPD/5+/h29e0LR
zOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHMiX6y7xIwV9et9a//x7uVGCwGi8Fw+6fb
P93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8C
RxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eXlxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8
xGhB/wX9F/QHeae8U94JXehCl/+i/uO2j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5
FxCFYgvFFoqF6Xun752+F1jMYhb/69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNT
kU1FNhWB/J3yd8rfCWJ3x+6O3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZW
K6vwovqL6i+qw7bobdHboiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn4
0gFrWcva9/C+/bPnm5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHci
iOuqyRkAcnfpmVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhS
YWmZIQK0eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GB
vZVkMD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2RlshvQV5
pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn3/3wh+aw
8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV1V3RlYWzwbcz
r/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZajgMnpP0DfJ1htwp
lqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3Xzs4Ue9cyPWjcPjolY/O
nYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp+Tv7Fqi8pPjIlpMhJS1mYY4K
F3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+nvRwVPxkeWVO6PA6G89cf3th1Ci6N
iHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsticJZzlnOWy3s+KCgoKCjob8svsiyyLLLk
fZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcffABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74
iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5
SOcjnY/kbV//YP2D9X8xIvguAdvivcV7izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659t
x+F5h+cdnge7Ju2atGvS38Zdt27dunXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg
7w6A/o7+jv4OHJl9ZPaR2WCz2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9
+3vnm5ubm9v7neMsAy4U8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlI
SVKaXAkYKO4JG4gX4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8
HaTldBcjgHoZxeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG
/CAbdN2MceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAY
A1IleZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd73i97
+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsTs+HmTUi+
ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQu9QfDLNME9Q4
SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFafkM9cPRhUvEg8PM2
7U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1bqArEesefyO0JZxOelLjh
Ab5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbTNHBe0k3RjkFGR/uF9DKQkz+3
rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPwz3nlU6JTolOiIbZgbMHYgn8bL6VN
SpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYEa4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0
gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/
aMc/237mM5/5/MPe9yoS/13teDfl4t37905NQ01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9Zd
oA1taANFuhbpWqQrEEAAAXlTSt5Xe5tPaj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76Vu
IPJLbcUW0CJoJMeBNFMrmpsA8oiA+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5E
BPXkQKCIGKDNAWkVVXgMPGKJOABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEX
rBscJvEN2FYafjGPAdev8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4Tsw
FfT53vwtpEdZ4zN6gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYU
yB6Z/VXKc7Au8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90
hWx9cmZDYEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn
3Z1KQ2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMmS+tm
NNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJfQu5q+9cf
1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OKP+wLHlPNY70P
gHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA2T/Wrd7dyi95vuT5
kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdffPHFF1/8bXzbBdsF2wWg
M53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePdXOcLXODC327+rQRGW64t15b/
J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc85C8ulHQ6nU73B/43eTc14z+8W/Wl
CU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RKbUAK4GutKMjNzeUDfwSxRy6YcwJYLMqx
D9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZGbQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjx
ufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHTu4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I
0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hmgscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpN
oATJHZTDQG/nRGd3MAyTo6VZEHjYcNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2z
j4L2ncturwumROmK6RIY1kjnxQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5
x+4JjtOZvXIiILtJgr7wFSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2Dj
N1Dgq4B63haIcWlvpGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCu
V+c74HNlTWItiBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQ
Zyj2U9TpoOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrG
RNMM63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998Obaa1
mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdjn4x9MhZi
YmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUArWtEKIttFtots
B6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2oW1C2wQ4dPjQ4UOH
ga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0aNGiRYu8Ox/tO7Tv0L5D
XrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90rUAMkUZ41AVli2GxshLEE+Gl
zgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01C7QFak/ZBnIT+TNJD9p5MV63FpRp
2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWfljb6WWgeSrSTnpl0Ht43ph/xVyxqccT54M
Lz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBzYY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1
rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wEhg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB
4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcVpapgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP
4y5AbFzCgzefQvZcY520L6FswZIHO9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP
+Nf0PubtB47H1o3SS/AdZNjumwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/7
7BeIHhwcGPQIevRo8rJHCzjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9b
FU5/fGJSXG/IXF9xpysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0G
XWlDmLYd/Lr5l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok
20RwNBCzFRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvW
rFmzZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7be2/n
fTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDLgJf/xZco
31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAgcUHigsS8Oxp7
w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEmPEUMALu1BGCbNIwa
QBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De7uXeW54gjwvwL9gP9Jmm
ZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQOfXUScEU9D/0e4vbGJSZ1BfsP
9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9LkemgGd749c+JpBidVk0A+c17XTuGbB6
W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I3AykW/IE3XqQjlJIag5Sc3FKqgy63uom
9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEizNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+
CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQam
Y/VOQSOfKjerzIXXZXMbPt4Em8qeKLZuI/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8
ToakfInHM3tAzoDsMa5seLEzW3/hOKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1
odT4SA/IapQzLLYYmPqabliegmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpu
xGh4UTLmyNuz4LnE+ytDUTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCr
qcmq9TuIkbNW5XiD7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWd
E3dO3DkRXjR90fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA
0tJLSy8tDZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY
/Grzq82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQuh3r
dqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj257f3r5cj
dHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99AHRihisctG/V
jfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24bw8wlAx/FZIBokjW
w5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7mgSZc9NfaVHg+Fn9QUsE
xaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKrOTmOcKCiPdD5Ocid9A313cHv
cPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0VdClJ70UWuARg1kzYd1A32fdafQZur
fs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbObAHTaK2UoTDobb4PfQUIEnpkh4DJqi5T
B8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8Fa
zZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LL
gJnAHXHCFQupG9LfpI2CUZX7jvo2P+hXyw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHF
q7fV0wSEFw701i6DlG760ssMvh/qfih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSV
xz9CRp+UUq9uQF3/OqfKfgV2P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZh
kDYno2ruAwivrr9kOQ7SaO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z
774cWPJsybMlz8KNoTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuX
L7/PEWcFgQAyJA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C
1EXzFVNAquY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ
8IyqvKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Yy9s3
2Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE865Ky1j8vq
Dbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41PeOgYkbpj6Mf
QczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1OuRvJt+u1RO0Otlb
dWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/d35is8CJxGuTz0wE81Pz
4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7JDbMrPIuCjIPWFbcLgtcN77NB
o6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3oPj1Mqsj08E51zZZNkO+7yNvBdnh
dpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQddVx3GED23bPbTjAOEAX7+wPzuHKJfMs
iJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1wxYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk4
0KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWhouAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtb
EK+kafpToMyV4ikIUmG+0caDKCaCJAOIEY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyD
YUqxoWW+B9cM+9eZi8FnctUHzaqDXFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry
+ta/Gej2OLras8E0UnqrdADjOVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz
6yvub4WcMzHnE76E1AI5g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHO
Z5oniMG6IOUaMN5YwpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhP
aPWMS+HhPk+XvS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDb
BOdKW2PQ5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhK
iocmb1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbKZFSe
VT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7Ro8AV38I
qOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9dfHbxWbhQ5kKZ
C2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6NOP/xxNlhz7W9AKmY
FC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyANFJFiAriWsFC3H+TG+hf6
W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8Kq0Gj4dVTtfzALNX6U7VC4Ec
SZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7ILVDPsdSQAt5TvHf5FgaPaGOUR18w
V/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZT
QFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9ApBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFl
OGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+fIMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhq
ZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0
iGmihBwJWmM1g7Lg/Ez7WssPWi2aqd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E
18P/Efi9CLgREA26guYSxsXgfJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjb
gPO+rBMTQW7pKOh9BHLLvS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5
A9D3MW1wDQNrAfOt2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3
c3Nzc3Nz+yPe31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQb
KK0GkSAKaN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdA
d95znXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3RsI3
ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd5PFyMshd
RbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf20X5I35bwMtEA
Oc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRbQafI6+TvQVsjYrkJ
4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhhWk/lHmgtxWeulqCOsRfU
7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0CwHvj4wVHSngv9xjhn8zuN3h
2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skGheG635MJj9aA9YTRqq2DwgWL5gZ9
D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5WubVoOanDkzoTME3vCYKY0Aj/xyTKWv4c76
t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5ubu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4
iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQMmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1
E6H02Obtys8F342hUb71wVnN/2WR5SC2as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWn
P8mQfdTxOGgP2DZnXXFWAWePzA5x34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y
86+t4DiddCJ9LmjbssyuD8BVU74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3
AqZr9/gGRHVRTGsEoqe62fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7
IU28/SKhHWgX1J9cHcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPH
zPYgxqSPFFdA3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55Icht
lCRugS5Ht1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT
9me1gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy60UY
5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+rKcCH4pC8
EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db/xbWVSM5PaUG
FOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb2QmgdXattvkBG/Q3
pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5TIWhbQDOvMFB+UvIRAerR
N4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NPkIzSS2kSSEdERyJAVNJiXfVA
OS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRSA95+k7vF4gOJdeJfvTwDKSuevH14
FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keYwdnRct0WCFnPk5+lRoKjq2OwVhaUunIF
fSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGK
XJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf
9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYBy/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4
BWjrRIDTCdo1Vz+zE7x6eNbgOOT0zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBt
AVT4oOzXxVeB7q5pZf6ScLnPnfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5u
bm5ubm5/zB9OnHVd9P1M/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnk
BHldQEDAXXBtdHg7KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7V
BZSwYktrXAd5v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV
4c2r+IOJseAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bN
IAbrJ4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVtFdVk
MDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAqqowFsZ5B
YilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKrsbpdbQSap3ZD
PQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZjL/Cp4CNMEuT+aM/n
GgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSeAvMh85PU3dJ9cAyU7ruu
wdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/DYbjz4m47x8fw9PWd/XeiwedM
uWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDifKbuhZGXRkHNslXuV6kF8jVpi0gA
sUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8CpiX2S2C4aCgpfQnaGtWTTWDoFJpaeBSo
V7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pfg35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN
+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8TnUevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAW
jDet7XKiQVmbGpZmAF2kTyvfB6D1cj513QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Q
a2PQbQFXvN9Rv6GQ6nRGahLEzUgekvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOf
X8Dp5dyozoaURnGz3kwB+al6jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6
FYon6A3SeSkIFEno6AziqtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2ag
NBLNyQfSEKmBVBqUh/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjB
XssxxTYQXGWtJazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0v
C9nTc6zpCyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx
+RdIJdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ctZyx4
NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUAjk9yK4L4
QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4zT9BVwhcjyzh
Ed/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50feu8DGK5tlxYQLoj
jRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v7IHEZm94NRWUOP8evk3A
97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBnELw5X1L4CvDN75vtdQJMV/QH
DTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAAjSR/+QcwWHQ6OR/oBks9yAUtUPpa
Gwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQNstfSdGgd0qHpC2gltSechDskprs+glE
GaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9v
LqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/B
nuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5NbwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1Ma
vikIdalHnT/Qv979gEdOTk5OTg7U21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqq
MGTIkCFDhrz/D5BVq1atWrXqn4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFy
itsm2n1AacAGMQNYS7w4BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3
FHSbfBJNRsCXRpIetENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+s
Z9LTgCYuV2pbeLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C
7yGWwdlW8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVok
vMy8d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEgSvOK
WSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxVx6gXwJUp
7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71Bmo2TvuC6Kt5K
PiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/whtyHuhH6mpBuzfox
2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D5qOVdSWD64pYrVsMhiuG
XVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYUWVBkAfw85ecpP0+BOhXqVKhT
AeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfIwAoDKwys8Oe9/l9NXBPXxDXY2XRn
051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt524ufLn66+GmoVatWrVq1fn/5ChUqVKhQ
Ac7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl
0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byczn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgA
OHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8
FMR90d7pDfr5+qOeHcBpSu3xsi9kD7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTF
Xl96BL6i5BjvgqB/qZxO+hDUyXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwn
DGvNd0AqqQYaRoLutHel4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TP
ATlNFywNgKxlb1ak3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXS
KoBI0xJwgrCKQcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaC
uCS+YTuIg/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAag
ptijaSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD/YCk
Kj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og96s/AH0xa
fXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYPt2BItSHVhlTL
S2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u627rbuv+NgH6rfjl
B5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgsBovBoC5Xl6vLodTZUmdL
nYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkns05mnYTmC5ovaL4A8s3MNzPf
zD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225ug0unL52+dBrqUpe6/0U9X058OfHl
RBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6LV1cSJsEvF/cfO/McTIcNNvNXoFUXTVkK
RBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3Q
vQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao
4AE1HzVy1fMB44rgnMiKkNLGttZzH0gur/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxv
MgtZfCDjI8u57J/B/tDjc59KkPzGu53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ce
Df0AXNUdDrsK1g/eNkq/B4W+jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G
3RFRVGsGpsVyT3kV6CtTWP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7Nb
hIH0hWu36xY4Njj7u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgu
gBIkZFEUdFflnuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTW
SO3AMFDqRjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqu
rwzeH+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38IfR36
OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgntEuD2j7d/
vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz2cB5yXnJeen3
v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJEiRIlSgBDGcpQ4AY3
uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwYbHq06dGmR7C14daGWxvC
8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz5syZM2fynn8y9snYJ2PhZNGT
RU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfhd2fEnRF3RsCuSbsm7ZoEL8a/GP9i
POx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/HHx5xlg3yao+B0GBnBWOd21DNXCm9UDuw
Oh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhC
Fakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SOO1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73
W4D/EuMFwxLIrKwv698UHDuNelMiOFMdUzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lH
GMHw0KdPwDLIDbA8M7QE61JTTWM9yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8
iwZU8f8UnJ2yI23FQb9VO+66DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJ
b8GwWVfOcBxMM/UHDCXBMcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC
9HetAhGgmoU3uJppjygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJK
jnxcag5qK9FQGgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCe
iQ9FTdDq80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DE
fENpAiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycvgfo7
SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/EPpAfyY/k
R6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESlv7//5I7JHZM7
5iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ8Olrp6+dvgbJ0cnR
ydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpapWKZiGdA0TdM0uH7j+o3r
N8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95PvJ8BD3X9lzbcy1ImVKmlAlX
GlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifKJ8oH3rR90/ZNW/C/4n/F/wrk5ubm
5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1axAREREREQEtsltkt8iG++vvr7+/Hi71
v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1DmocxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X
+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+ISdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPA
Ucfx2tkd7DucJZ11QdbkSvIbEDvEEhEGZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYB
aXipVhVc4PNZ47s9N0GwpfWhgR+A7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk13
1RQLym7da7MA+xXNyxoOak/H5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9W
n91z5j487/q47qOeYF/ovcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjq
lq8c7DEcrHbwJaxK3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3Q
TQTXNe20+AI4Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6Vd
wCfiqigKan01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4
VFd+JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyrpXbg
HWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBTOcjZkDtM
1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0I/Iea1e1q9pV
kFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/m1rxbqqH/YL9gv0C
5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d+sfLN3rW6FmjZ5DSKaVT
SifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1L1BxUMVBFQflXWC9G9GucLnC
5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1nPWc9RwkzEiYkTAD8uXLly9fPoiZ
GDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rCMmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8
WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wpluiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKf
s5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpn
lk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWB
x+QLm542gVc1Ys4nrwDbaKLlGuCq7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw
4nXSw6RJ8Nh+6fMLJ+BZ8uMVD76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8q
cjLfd2C4rd9mHAq3H9w7cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y8
4QeVd1awlB0LxRsUeVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwf
mKf5VwXHx/ZLji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt
4v2R3zIw7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcB
K+ncBT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0GjhQh
LEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb0TaiLTyd
+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFxcXFxccBBDnKQ
/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se5S6Vu1TuEtyUb8o3
ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU+/3VFyvFSrES5F5yL7nX
b7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH5ZBySDmUN3XJuNW41bgVTMmm
ZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X56wvL5oHNA5sHQuonqZ+kfgJvD7w9
8PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfXSf7i+TFo5lE7uq0C525dfn45BGxeru72
6lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZrN9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8
cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYep8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GX
gcs3NdjSDoylwvsWqg7+HWpOKvkLONdnf2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36
CuxHIroWGA8v92a/theHZwUuRV44Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZ
Z59+Gbyc9mZRTEeIO5X0aXwW2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNc
YUIv7kPGzuxo+4+w75cjB0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qD
T2vfix4lodub9t5tqoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1
OrdGQOrKtFGp/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2M
mKEVA22QJrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEi
UCSBWoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9oNzc
cnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm1ZtVb8Le
2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCCEu+//tk9sntk
9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m8ZnFZxaDT0Ofhj4N
oerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pSVamqlLf9VsVbFW9VhOge
0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c6Huh74W+UCy7WHax7Lx4745L
o22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269GErZStlK2SCqR1SPqB6wK2ZXzK4Y
4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd
4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNS
n7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6
vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJT
El5Nva2/ehRelrg974YFUl5oE+kPuqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLh
o60FR3m1jLYPlDjDFIMF1IJqD9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5
qqme1xawVLeGak1BHem05Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3B
Z5xPCc9zUHZv8bji/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfB
ccrxNH0PiAeugY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD
1l59S35goXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0n
nRFZQF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUsmD4x
fWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1q9SvUh/2
3dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39behZL6S+Urmg6Ld
i3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk/ceLSopKikqC5NnJ
s5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/PfJh3QfFurnuthbUW1lrI
b444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/6ino5ub230S6dOnSpUuXhKhe
vXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2xrlhHWk8orCuypdQxSOyS3fH5Xbg/
70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0CP6PPC/8C4H85aHrIS1AXieZiOqirUs7d
fQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15
EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhDJOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSn
V5IGZ1ggt76H2fcc+B7yDPD8CuzdrOuslSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb
0KbLtbQUoI2qF7XBMd0+yzkNxBFRT+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEdu
B/IFeYBUFaQp0hKpF7BeMtMLHGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+S
tCzQJct2XT0wDNJflKeBOkc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcM
QveEhgRvgXyDw46GF4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6
roHQi9b6ieDaqNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY
7mzg6gOuyfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFl
oKR4tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX25fb
l0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c06aSTTjrp
vGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQnZtwLvDGr2fW
Q9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfFnthIeHr3+fzodWC+
73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3oJhqHp/pwGPxOSuAsuKg
boB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2fptkGgbVMlpH590FQm4oFiz+E
l8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKiXlHfBa8PJfaIqwKJ51M+T6oNjFNv
ij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGCXti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRH
ykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgr
spZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoMaWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZp
M1I/DDKL6KtGwMuPoqcnnobYVrFfvtoBnvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3A
EmFpaA+EJ8uftHpogLJSrSIuQnIuZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYm
riKc+fxCiUsfQsycV7WjNkDGXzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7h
nitgXNT7GL9AzJKEOYkx4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA
3GZuM7dB1biqcVXjwJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR
4EoxsA00EouPguCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4Mt
kHdLaKPiN+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZ
lDJOQkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7CawTMwV
OiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADynllQrw3K
APE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdSV7kD5kDjrnkO
xOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJgelkvq4CYZp4U50F8
L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMnopyFq5YuSL1aAj92xxNoW
6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+BC8evT7+WoHYbxO/i1sBrE0Y
oC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasPAqWJOl6eBLWB8qXNH7THlr3yKuRw
h7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/ocdXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/u
aP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumkk046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P
9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xkboDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh0
4lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8
dsaOFAit3TZrlxxgn5k7Z2kH2HbmquSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGC
cSDzrYgu8PDuxXmXdsOTUtdKXckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNe
z2McA/Gd+EmtBZ5IVybPF6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0
ZolYBba2ts9UfxDVzZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RI
MN6XsfIm6Iv0CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gB
GGKj+A70BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7
ymvW5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghvAQGf
+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8C94+cV5n
jiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARFwqfxzTP0HgF+
Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazvg/u1Z7OeCGKpZrd9
BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3ewgwDz/svyt0cDfENdgzb
5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQRz5TmELDaUdg3E8hA/ZlRBxLP
JmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4sQRaQzeUd2QtEJfZxA0Q1WuAC+aX8
SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2eUa8EpsW4LzeDvGYW4zqIQOWxkg9kD3lK
rgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7MZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke
5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/Wulp
FOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1
CXgyePq7zwHNzJFiKih3lQvqFtD8NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1
iGWAz0WwnbXFBGYBadXClW7gTnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olz
wlev6qeMgkznLc2LFIMeQY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs
7FPk88fg2pOyWZyEU112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwq
PBLMhuYQYxEoG0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUI
PDNeToo7DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3Z
mXAQki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssMohh4
X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN1CxaZ207
yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2ahrRoGzSNGU/
UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ksn4FYqnxghoP1pvWa
+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUOMEfIT7QvQD40n0sVon6I
GRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZb/mN/bvDO5100kknnXTSeZe8
deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vfgFudHt28nx9evHjp++w+KGuseTPk
gJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJYynhISEo69WIN+Md7NvtOhGw9slTL1ACC
y4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tBOWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjv
GweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDgXFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wz
ZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3ijTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh20
0cpp9TMQEcogMRm8ZfV2ehEQm6giioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CH
iCAEmDnN3XIxyAfKCh7zX+8f3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPl
TRDlRX4RCOYnZlGzMYhZvC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhD
bZCP5RwZAvSUuc1zIK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPL
uyC/li1kTpDH5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9
l52iW4LvPft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ec
MlvdLHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDEPCWA
rpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vjonUgw4KM
oXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCqgzvZ+6GxEMyN
ZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXILcwW7cCM56UMB1FQ
lmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6i3CQX5FfmQJmC6y6E+R4
83OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ205AJIHObdrkLaKxkkKvAvGBU
NB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUbMyfIieYrbRVwkm58B1Qhu5kBjBbm
A7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqrlhP0+fpTWoNSWASK3CDK8In5AYjsMqv5
CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywFnmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm
2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ
4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWsXbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGT
o1AJeB6RODHqI/C9Zw21Hof7616+ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0Z
R2dJ1D+E8hern+v9FaQUcVqdg0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx
8CCwdwp/bO0PCR2fjH7wHlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeB
vtBcDuIjkaycBCVazab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBG
UT4Dacqi8iSIb0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dg
NqIUW8CSaOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNa
SOQXm0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh1DR2
Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxVEoGOIi8P
wbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9CoKeTTjrppJNO
Om+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dGZQTfJq47mj/I0wHd
X52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3PTsPFK5e7HSkKvn1CS+Vt
CKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC9eVhoDR1+RyU8uZyMQrMytw1
pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu3/f9RoG6VPlRuQVmoNR4CNYEW3bb
aFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaRBQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWL
paj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0
XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsxsM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kY
LJnULepokCbVOQdGjJzFLTC/ZiTrQD4ww8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCo
JexKJWAB+/kUKMJ88RLED2KEmggiUviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLt
ApYUbbPPSZAVzL3KLTBe6qXYA4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHm
TtDvGkP07hDT49X0pJLw+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwY
bD9nHwUJW9yTExtCRAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzp
z6DInBKrssXAo9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+
v/qsUGizst2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJf
Gq6pZ7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ+iOo
iuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEXgLHETDYv
AhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbYWqh+YDxx3fNc
APOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WCmQvIzXIRDto1Zbj2
PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7ALiqDOo92Sh3AK+clnQfv
NM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJIE7IfEpRcBxxDLQvAWWd1sh2
CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTSSSedd8VbV5xfdo4Od24Ga7Btsr0b
hIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSClV0oe5264Uvr5ugO34U71pyOu1IKE2Fd1
ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/LftT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem
/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZrc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYH
gAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2zDcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcp
jdPmYrA1tRRXHoJyVOuk2UDV1BraObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1
ZXbjLrhWO4emvAJvZ2+Qpyt4i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFy
AiPlKtkfSKY4I0EsUpxcArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6
A8gysrCoCdJijjOXghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0
QmBZpPhaLoB1j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tf
DXJC5ltZovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Z
m0DGI+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf5X7Q
73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7HsxbIwYMCA
AQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fvZLLc/5383X76
pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUGYh+4/GKnwpO2Ly8o
F0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjSZqpjICXG9Deng/Os2TFh
DuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru9wYgk2wuQkBmkCVEZxArRCk1
C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVMXFfaQ8pUZ+2Uz8B9Wd40B4LMLqLF
ZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Ym+QcszlorbV26gegVlSrq7VAGaOMUCaA
SBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoa
KB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7mo80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCU
FVVFQaCW3IovqFYxSf0ItKHqYrUsyBSzsugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5
+Vz+DCKKcWIyEC+uKs1BPaw+spYCz0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oI
E+QB2cX4ESgiKtMElCxaDa0CGPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX
7EMhx4pM8ZmOQc5zER1C/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC
+6/yU8JPCT8lwNo7a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZC
m0NtDrU5BJ/7fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/G
H9nhP8VP/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3
Xdx3MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9SKnq7
JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs/KEmE+Mh
0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7lnOWOhaTaxiTm
g7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKWu6Dt13ppy8HSW/tE
k2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9biRxC5hUc0AxbwMeuAkVwx
k4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPVjWCZr23SpoH8Ue6iIrBJLhYl
QDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGguNtaCaCf6KQqIzqKLehXwECmqgmWJ
Za9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWf
A/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46CrCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs
/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JCvYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQl
cTjEX0rqkpQA3jNGY89OsLVUp5vX312gHog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7
uLi4uLg4GDp06NChQ6HBtgbbGmxLaz/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yH
Dh06dOjQAW5WvVn1ZtW09d27d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZ
smXLlmnH07Bhw4YNG8KSK0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW
0Ug9zj/jXcsVkz0me0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P8
9+1SKzh/ZK831c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8
DG70v9H/Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zc
M2nb/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPaeS4V
Xdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G+b+bt06c
vYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2wlo6dCjxMGhij
gbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHgGeEpaXkFkQ0ibyrn
wPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc1wYogRBb90HR+2XhyaNn
AU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYuMRVkLuOq+RwMRa+jFwazES3N
vSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5EdgXjevGhVADBRdBKBGq04RBYpBdZqD
fGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZY8C61dLGEgLWbBZpDQVrS0sRa00QBcxX
sizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqH
gTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+
jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkOWmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3
kjuD9ytPkNMKeht3jpRPwLUt8de4dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8h
iF/uPk0CRPZ73cNZAaKPOJt5Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu2
37f9vm3akPP8HvN7zO8BP7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFj
Isak3emPyzIuy7gsadsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL
07a70OtCrwu9oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1et
TLtwpJ7AUxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHv
Cnz3P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68tYVvC
toRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz7c+Vtv7U
qVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2IgwJHBI4JBAO
Tj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nuJrubQK21tdbWWgtT
f5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQR8BeS2dQ8plrjPIQv8JI
dhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs/hkgx/mAXpkTwV5B3tMbgOXX
pHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVbCFJOx1gUK0S2cE12noRVt9e3/rIn
EJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHcS32HeQLUjBah9QIxVpRTZkByHufzxHbg
XqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzMVP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHF
piQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7aylJ4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9G
LTmPziCnmZOwg7FZH+ndCMpLsU3sALW3OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQ
iRMWELPEbRqDsp4zLARVV2dyErR1yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQ
nBC0NjQpYx0Ic2f6JUcVCMsaUSR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnG
fn2mezzoQ71RugnmV8YJ/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1
cTQDo76saFSH5HuJ++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh
+s+2jZC0zpOJqSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd
6naq2ylQPlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2Wbus
XYbYybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/qRfW
0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D6Lmg54Ke
CyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RMq8j9VX/4I0rP
Lz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6du3Tu0hkyfpXxq4xf
/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0yN8r8D/aNaR7TPAYu9LzQ
80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJoPPcbDwnT9edGMmg7bbuSBoAc
5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2ik8gAFyv3U2Td4ExUWmpbwGfoRGj
bN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRY
ZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36JfB5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrK
soYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRN
dFR7gznS3IIEsU/8IoqC+qk6TpkKopJoI9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRX
ySdiQElR3lOmgTJZOSBegjpIW61tAeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s2
0ApbKlhOgBatfaglgzZHLaM1BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LL
Q/zE6LKPvoaEQbFfRD6DJOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjn
Pa+9u8BY4A1zjQbDTy/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSP
y5GgvzDWeDeB/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157
svUD0G97uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1l
KVlKlgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j7Xd0
jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqNzx+RWnF5
W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDBQTDuxbgX416k
TWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq1t1ad2vdhe2Zt2fe
nhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusESyxLLEgvki88Xny8ePvf9
3Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9qp//UOP+dPd+2g9c+ie8bncAc
rWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuSD6iRxhmxCDIe9GsQOBEyfpjhczED
LLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU6BkDPPFLIGxA1slOCRneC1zkUwiUbfZh
fAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCy
y5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLke
GKc8VVqA+EndrnwOcgFF+QKUFswTNUHMlS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5
zjxi7gXZXXY3u4I6Xp2lDAKlhdJG1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9
LF+D1lzZpuYFrYg6VYsBzUerptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/
Gaz97HvtOUA2MCeb30FSnleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBY
O1teqSr4Tg+wB5+DkFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7m
nll8JmT+IfvsQj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8
Ck0G3+CAHsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6it
v2n9Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc7nM5
bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVeEH87B/2s
PCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P/Zs6tJ1aqUu9
cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+qF3qlI05xhxjjpGW
SP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/omqbX6GbRzaKbQb6EfAn5
Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2fVM7/afG+W956/c422+GR74u
C2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6X7OM38DNKEuXZ8HwIuFuOzMj2E8r
JQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk1athEBn90OE8BhmaOeoETIXkCgGVvQqQ
mNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7v
OTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYr
OcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKwuCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj8
4rX4ECjPeAaA8bNsbGQA85ZcIzeCfEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1Wfr
K0D5QhujnQTlmvKTcAPjySqOg/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0x
WisPrnHJ2ZNagvkemzzbQJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXU
E9R62g5bLdClHGgmgtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsH
gWuwMznxIljzq3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1Mujn
Xf30M+B6qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepy
dbm6HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/BpD5M
GHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3gWOFY4VgB
X2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/aa0zFMRXHVPzn
9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKVq/+H/hqda3Su0bl3
r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7/FG7wkcLHy18FOyV7JXs
lf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83NNBduTb81/db0tETb08PTw9MD
yhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hOmHJ3yt0pdyG2e2z32O7/ej9I5U39
9F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4
c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56++CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Co
yavubi8ENKO62Ruim2vjEgaBry1koN4clGtGeTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4
CLhu3em8BXElkh0uN3i3aPvjpkKuKyElKvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzK
OibXa0iKTd4QvwmeTH5W79EeMPKJvNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqA
edzcb+4AJYc6QKkIyhpxSZ0P8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2Io
CLdyGx0sBTTsDUA8EIvpAcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL
7Eftl3weglWzZfRpBepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrij
XNWSZwA7GWd8Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwI
cyXIEyJUU0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+E
dA+pGPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWielGF
b9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYibp0Du8jxK
HA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ8/nlMMdC7ks+
quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61BA8RhSMojlj5vBi/8
427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGUMWqDskmrKN4HsVM9LU+C
2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZC+p1MVu1AFk5RFOQeeUDYoCu
ZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPAI3lTvAbpL0+YS4DmopQoD8Z7MruZ
FRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSBMkT0sihgWo1OnhVgmsYl8xjYfrVb7fNB
y2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkEwm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/v
WmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5
TT/rLATmSnfhlMNgrSt9jevguW8EEwfur7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczK
me+a7cFe3FHA7gX9oMeQW0CUUbbKOeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmN
Ca5NYIzSf5UvICi733d+pUDrhY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxx
yS+ddP4f5K0T5+wvwpcqfSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEp
ZY1FsjdoCeom+0SwvUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeB
fd76juYg5tP/dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD
4DnBHPaA3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7
nAPbYNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkto30a
gfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCrgtaaK3I/
qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39LmyPphLzETdArK/
+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g6my0PXoYxDpe9XvR
ETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvryOD3K8SfSpwSmxPs7/t4
rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/hwGUQPyuxY5Iv+F1QgyyT3jic
0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdfzdu/x3l/YgZXFsjRMWRtJsAvv62Q
zyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmUehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567
AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t94B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5l
r/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpHnb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM
1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0fABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuT
rREE/RxeJqcDAvSwatn7QmDTDD9ELAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34K
js/924acAv98wYMzHgKf4YHfh+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd
9l0B6miry+EPNLDN9fkFzHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLa
DyAqqweUPaBFWSLU7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSyw
y3zPpYIn0p0//kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZA
pnyh+YNrgNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdU
KuQZhJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTmZr+x
G4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc2gMc+wNq
8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHUos2WbaFAgaxZ
KnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7Y10a8CkYlc313pfg
XZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVoCKIMHxotQTRWc1IJLEnq
Ml8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0gbHKdeQoMyRf4At+IIuYo0N77
r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKmA42UL6wPQMmrxml9wZigR+AFsxUf
0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N73PXREiZEf86NiPYrtun2dqDvbO9t+MI
+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5
oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiPtHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9
HYPAG+xclLwFXKdTmiTaIHiCfxP/raDmU4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukU
Agpr27VeAHT4u4M8nXTSSSeddNJ5N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fy
J0ja4rE448F0uV7a20H4WMfDHD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZ
unnGgaOhfbX7BiT/fHmcawd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9A
rl0ZBhbYAA/tN5/eygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZV
cmjXwVbCMdP/DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG
2jFrfUdPMNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkD
nJXAW8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1jaakPA
PdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2zHbbVgos
IZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt2ggiUri9JcHd
xlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaII0aivha0VcJKELg/
cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18miY1AJvTXtDxOTjj9B7m
PgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+QYmAuENJIdom0Bs6Zxo3Ifme
UtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE7MlBOzz3IcvH5SoEbwTlgqPx6/eh
SA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwGfbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwF
tJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2vQdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYi
J+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/SG/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uor
n/EgylrzKQfBLOuNdn8JcoyR21sDjFtcNZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw
8Kw1LslvwLPdvcubB6zzNcU2GpQLSnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3
Qe/q6ZHyK6hu5bX2K5iFyC0ugN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0
fPXKuRN8WnuHG8GgzbBUtQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt
27QnIPYaXykVwPOV9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkByc
oMQ1A2t+tZzMA7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+
83jrxNk4rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZv
C2eS2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9belrLW
+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGYj7Qxtrkg
xxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kOZi1PG/dVwKG2
UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaKW1aCPty4Z9jAU8ez
1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRRE5QzYGYy7+hXwLmAFdIC
ZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POMvGA2MXd4J4MZbT4UA8GMZIUY
BpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkpd8lZ4Gnsfu2dBWYrJcrwgHWE9bTt
AehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2NbBJyFjwCQpyhx8G7pufyxUgh+pT9Spg
FvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aST
TjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7Ngki
MgdvlhGQqXCGW8piSH7pMynlNrCX5bIDKJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5w
t2eauyQUexw+uNYT6FOs5bS11yHXuOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF
9o1PWbBp6jTVBsoA5Tj3Qd4TLY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0Fdh
pcGh+qb41gXrOR+PZQTY7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIX
SBga/8Gro5BUJmFHbFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUO
zKmsk3fBXtZ+zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlw
PXdmSAiHlPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6
Dczn5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8YVnA
1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYkgKW1vbHt
KGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoBNQPSvgCW+mGT
p0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2qz/y5//t/Lvj9d/F
lsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Whb0nZEpKijXKvTYj5LPb7
V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzzdSoLIGcP/17hU0FL1AqpX4Hl
olxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3ehWpa84P7B9TppJogcMlovBfFXnoe8
6A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zPQQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P
6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyB
KXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5fNXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yW
B7/OGAG+eXz9/I6B7Ka7jY0g84veamfQtmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVn
p58WuPMUnJNcj2L3g/s9V1nnfNB3efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5Te
SpjSEERlYRHdwWxDOfEL0EyJU6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cK
aKiVtBogigpFpIAyR2uoHQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7Pcp
nrE/mI2VGWobUD6yzrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rt
hBbgPuo6l1gT3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhyb
kXYh7Hqq66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0Fr
Bq0ZtAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafkPZi1
I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/dVVocLHg
9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+zYmCba7VbY6BQ
/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2z69g+HrsKZ3A+MVV
N/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwBxjf6e/IUKM2VetbS4L5m
jHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW77ZVDBz1ZV/RPwBxknDMWgTDN
++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FEzayOQiPAf6Dvr+FfgPmDPsxZH4z3
jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2r
QE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBPs2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6
grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXlYXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf
2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv
2076tgJzjTbMkRsshe0bfKq9u0CNi4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3Q
smXLli1bQrPszbI3yw4NGzZs2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rp
abyr8a7Gu2BO8TnF5xR/8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X
7fDP6ue3y79r912779pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3S
fn9a7tNyn5aD8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/z
qzeNlz/y5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpK
SkpKggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v/0nI
9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJAAGihHeK
WhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0UOBIta7RwsOfR
/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeDtOnVvNPB2Kt/7bkG
Wjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNKguOc766g8WAbbf/eLwos
kbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+61fIleGaaK9VmYGnqkxBYAqy/
+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u8SW/hLCkLPNyR0LIjvCh2QMgZGv4
sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6foVLWK+Do4bcsXAP/+yF5s62G0DZZRxRe
CqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DUVsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2
j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTWBKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5
Gxi9PB7neFAKyIJmHRDzucVs4KYw5UfgKebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+
4jz45LBYZNS7C9TJ+yfvn7wfwh6HPQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOf
lPqk1Cel0oYsl15ZemXpFZh7du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF
5WHFyhUrV6x8d3pJpezFshfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7
SO0haYnOuiHrhqwbAm2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3fu
nJYIfvTRRx999BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym
/UyNnxo/NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue
7Xi24xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k1QhI
mSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv5XFQchCu
xoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78CaHVjfkjpDbKe
e63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzOtRa0Btply2VQY+Ql
mRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauPtLVg7W/v6jcXxCD1pqUI
qIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5YQwH8R6POQjGfX23uARKqLW9
zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1+KutAK9ntvMyeGd4XiR/BpwxJshP
QfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcrgAzgidIe9PpmG4qA0Vz3cXcFW0HrM6Uo
cM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYy
HNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCo
ZgG5DZgkXeIqiMqq1/4tiEuWamY38PWqjfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmt
rFZWp63v3LZz285t4cOPP/z4w4/hp3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDo
Rje6/etOMKkXWEuoJdQSCt563nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8Qc
E6Hqzqo7q+6E1RlXZ1ydERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Z
b5k0/SyusLjC4gpvb8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEH
bGMb2/jrNMrcKHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou
67iswB3ucAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa
82vPrz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvhYq3b
Z17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVKa3FJ+wzk
FHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+OTpAtMdvsrGPh
nPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAXcqkBiB0UUh6Dplm+
s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXpy10aaAlqe2Ul6C/MSPM8
WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOcva19CMhoqYrOgFUGmH3A1ds7
03kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtzzDCIa5b4fnJW4LnxUi4H7aIWYz0I
SoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9
zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVNL8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAn
uGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic
72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKy
FGh7tb3a3t+vF+fFeXEezCfmE/MJDDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+s
vy63ZYlliWXJm283s+jMojOLgredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9
+fXl15dDl2JdinUpBp/7fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5T
h+wf9HzQ80FPqFihYoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jRe
aE972r99P6lTA9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoV
K4jJYrKY/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2N
VxDwje/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQhxA9
8FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui+Ly05rWV
hcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXsq/0Ogdgssmpf
gTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz1NRzgG2pVkWrB+rX
VqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7bPvWrzlY6lg0bQtoxdXb
1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7UkqAky0psL5ADrCdUETw33JiMX
OH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2BfWu+qPlfZDzlfFyKzicjoP2xiDm
ynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4JyooBsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5
GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcboSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8U
ZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVL
lyyFKturbK+yHY7PPD7z+EzYennr5a2XIcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyB
mJiYmJgYuNvzbs+7PYFlLGPZH8uX+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E
3Ii5EQOzi88uPrs4JHdO7pzcGQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+
rT6rHat2rNqxtO6md5reaXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaH
bQ6DUudKnSv1BpXEVN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7v
Wq9ZxmYZm2UsTGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P5
38VbJ84+twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniG
ewKh8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIzW4Os
K8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG9N3eSE89
MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxXAs8+d0XnPVAf
KTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1QajWML8R4PPcZ4Al
AFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYjsERbTM0Aa1fyi2aQNDRx
XPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQnjtofuBN8PfYuir5wbJFW6kU
AREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5BpT+ahl1KhhFZVvzInh/9YxzDwTK
skXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjFYKzXW+sPwZbfOkULBLWlGGoZDXo1Y455
AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeberGhh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMq
k0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFC
Rwsdhenzp8+fPh8GMIABQMdCHQt1LATd5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT
8E3DNw0HhjOc4b9fn/o6qVvTb02/NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN
7fi2+mybv23+tvkhpkNMh5gOsD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+
1H9S/0n9JxCSMyRnSE6YcnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq
1KlTp04dUMup5dRy/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP
+DN/fVP+3f6dzv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4s
LbSrzcqeoNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+z
j3SD4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5XtkO
7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQfbtQ49MYu
J3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6geBQtwV+ACZp
Vn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0WrpwBYwnJWXy8XA8LMp
xJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALeFo6DZtITtH0gf21cYdFA
/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TNUr4tBOSXjJuMpUGP1qoHJoAw
Wxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALKWbWJlAmWry17jCYIG2aNNPQCYVEg
3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsD
dcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ec
Ow60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5
DIx4+73j7134u4d5UNB/poJa1X+1RvU/VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/l
f9rrGhT0n+DIkSNHjhx5DDPOpAph4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0G
L8+Obln3AHSsWuP797tA7vmcVFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj
4TUQRupZ+kLQGgjT5MXAVD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19l
f/R10D/mKXE3xN4oVqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNq
yxMWBaQk6aK0BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUH
JgNoZ/ReWhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzE
AeJo8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfAXT5V
L4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1ang/SupirD
QTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3wjeElkD7wDfA1
g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKsgyyd5H2ghQnLzZNB
/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysOrDiwIqyqt6reqnpQI6ZG
TI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZNBNMFLTXzLHRxRn9d5wS039bu
2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuDGqIvzO4Ckl08EuYGNnFZuAz6Df2u
OA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7o
sCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsRAs/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0
n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxX
rG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLeEK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10b
A0J37XbgI4h6NiTGlgjey55vPN9CvphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsM
fO18G90DQWppaGR8FhyV7d0tZ0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuA
cEv40fQiMJHzgh+sP1m3GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7
hOc+ZD3r7JhTHUyTDDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhc
QlggAgKTNIvwDuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPie
HAXma+ahoQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZ
odLLlV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuCOFWf
Li8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ3WU1CPvK
UC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5O8DV2vm9OwnC
cqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPlZfktW3kwP2FND8QA
RdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinfgDhNdwr7wVBNjrP4QI+X
OmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNXk6uC2NfwrHEDyHZDFVMMmOym
GcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8m2vKZTD0ML8p3QY668dMGvgmKoP8
44EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE26qDwWCYLntM+8CwyYh1EHgG+HsErBBo
o1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegfa98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+
F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVibTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF
8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3DeoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/F
vBfzHixlKUv/0QV1qcu/URL5r/qf9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577Vc
iJ9VOrNWFLgPCOPFuyCW9SxznYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2
Bj2ZD6UBIHzGEf87wAgxTk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6P
AO2g8r7rU5AOWxaZi0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8S
NxyML5qnhrwGOV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO
9Bh1sBIC3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqeh
sh3EtfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3fS/cg
LM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0wdxbtnAOv
xZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0JYWmOKNP7EO61
lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWFpeJZyDqUEcjZC2E7
QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFBj8efTpzvN3EOMLaH8Mz4
fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7emlnAJLWBfyqIy8SexpGg6srB
rJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8eNnRbDjx6umembugd0afeS89CyGz
m2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/MtgulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3
ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+sU023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8Q
Ks4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFDQS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlri
aPBleW+4h4A+0Rcv2MC/hQqm78H6uvVoaFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3Bf
AENV+TPPJtBDAzGeWJBek3poT4LdYR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73Vw
vZa/L30PRO6KjLV+D+ZmhkzxfciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUH
qC39zfJvgulJ613DaMitkfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8J
xqetqy0HwVfVH+lNANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA
4LetE3dAYKnaV28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i
+buHd1BQUFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+
Fb4UNwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO96Wd
IF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuHrXhlsNQJ
GRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B3aF86YsEb+Wc
vRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJA+ublnXmIuDPd77p
nAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DYJRXVuwK7qeM3gatc/iKl
C6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP17sl6/gsgYRgmx4H/vNZWKwf+
K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyoNADdhlGPAfmEcYI8B/Qs0jCB+oM6
S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/
5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEB
iEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoKCgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVB
U6yRYkfwt83skt0QxK/Nm0xRICq8rySBOk8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzP
xYfomyC/c94mXxEI1cIuh80GTzP/D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILY
Kqa0+TMwfBweEvMscNM2MawC+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeT
Cs4r6UVudwZPMU+7+M1gNlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/
PVC/VndKFhCXaFOkNuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0F
MV6YbNwJHBNKe78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQ
RweG+p6FwFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4j
UCQq5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQiwxm
zZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+qAkIttbGy
CDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCgoKCgx0n8sw1I
t/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3QKmQH5v/IqTXPn3w
2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZJeNOiMuIbRPyOvgauMq6
3gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVbZdD3SPsNkSDk+j92doDS5uIZ
xfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GNlaqaJoHniDDU9i5cnJ/0UfZYyBvm
i9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus9OS24H7LfTd3Kahn/a+5zoD5PVNAagzW
osa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsG
lnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTsdgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqm
gnLGv8h1CHy9PG/53gXfi/7VzgiwbpOyNQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+Ipe
CbQ0mkp2EMeq4WoEGMoLHcT5EPVqqCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhK
GV6V5oPQRUokDPy5gZvql+C/6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX
/S3BleVp7twBvhxa6X6QQo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcT
X4h0g+mc1l8s+ncP76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1C
fA1+nLn/wvqnoUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht
9fqWi2DYb3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSI
O5NgAOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O+nwt
RKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dAQQSxtt5e
HQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUKtNX7Q86p7Lys
geAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhTcLt/xorMNyC7t2u+
9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3cc712MC6XIqUfIO6bsBrm
iSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJZRIpDr523mm+KSAtFyaLyZDT
My/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+CJSril/7HJRx+hYFENfrMw0/QbHo
sDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSKX/peaQHVeXonB//uYR4UFBQUFBT0OPzp
GecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3I
CpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8X
vHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZqr4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupT
yJ+hJ+uh4J6cNStjARQLjdgpVgbDFsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN
+BHyxuodZAfkeIRo8wzwfK6MF/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6Pt
oVAsKeZa+HtgDGiLfRpIAfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+s
fgW2btapjtLgnuBq4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqW
TmuLoFj96JVRaXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBl
cdaS8sG/MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7
i6t1bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUyl8p+
AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57zffZz4NLu
WVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKgpeT/5HkWxPIR
7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8fDsIm9wB5EpAC0k4w
rk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6Hql9VeAnsXfXFMSvgl1Xe
TUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRxxqvRVSHvSb2++h0o7/gauVqD
4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFPOwQljsTPihwCruM+QVkKnin5y3Na
QpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXPdPdV53JwpnhSc7eB97hnuccL5u2mU6ZQ
YLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9YjXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0
GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGlKZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJH
Ka1AT1I3+G+DVo3njN0gp4k6NJAMmujtqqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZk
gRwupqgXwZFm+UQ8A3quPlhPBONGeY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD
1KUyB8qvB0+2ppv6QXR6fKmYlhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKl
SwuP9+nTp0+fPhAWFhYWFvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQ
flI1+Zn+kFik2pannwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6Y
XQd4EPFNQjXQr4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814E
x5l7qy/PAO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBq
Tr3B3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/ntnbnu
+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nahH4N3rK+J
ZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhNm01lgTlK3Yzy
cL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU8Lv8FfQXIWNM7j3n
p+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/ISVMsmMrJS9Qs8Lf11xN3
gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0ivmPYaF0NeD+cB7yhwnDJvMayG
hPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfIfcIEp2vcbn5L//sGduPGjRs3blyY
QBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzLL3D16u3b2dl/Xbxy5UqUCA+Ht97q379+
fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xPRITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3L
zMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2iKP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR
5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDv
sEWGjwNNU+3C26D3Er6jDQjzuCjEgFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5
/MoV6DFWyroTDilbKuj3P4KE6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh
3YRjvAVdarWMu9wRbg9e1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L
7QgI7cQD7ALhF8Mc0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEde
U8gemnEv5Qdgvvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUB
JV3MMMeDO8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQ
mZtR/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0EWm9K
0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8GkpWKuYs
q0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRrf90Hw6Ps3bt3
7969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2QWZmXl4gAGXLli4d
FQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRNEODpp4sVi4j4tT+P83n/
2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs83t6A/n8mq+7f93h8vsK4bdvG
xEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQiml3hVRQV8nbmQDCE2JrfSxIcYQY
NoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgYTHpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A7
6qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/
EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmnIHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w
24dObIH80dn709tByJ3IiJgtYGxoMfvrQsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0
V1yoXQBDSeNdxxG4fytvkh4Lvi6ub30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzI
c7l/0i3gK6029JlBLikvFdLBW0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9
yS3vAfCleBZkpYJ6mhm6FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDq
pU3wdwVHTfsFy0nwNgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGO
wbve7wJhgfyytTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+Q
VoVfg9zN/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1
O9jQfkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4uLAwO
Hbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c/nTinPzG
dePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdBv6xf8DUBsZQY
JX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdAC8EhW4GvhK8CZUGt
4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSulz4O98InjrZufLIPbpjRD
4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5NnQrpN+Pyi12BLyH0rsmxYL3
nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q2s34klgazHuksEAUXG+b9FLOafB1
0vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qwtwd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZ
uAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJeALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3
GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoP
IKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXPdTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCN
UXcI3UDtpx8Tb4G8XtIDdcDU39xQ9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHW
WGxF8RGgFxU+sgTAfljsYTwDJd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAF
PPPXfTj8IwW1y0uWLFmyZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L
9dtSO7s9LCwurjBOQdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1
HTIyFOUfnd+1a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE
6JDXHuRvBUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpID
oEUKL4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DMGahe
/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dpamlw93a3
8r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD3mzPGFdpkB4Y
LcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH+jVEVQqpEdISzCfF
COUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+bcpsfxjkf5P7TH4iJB9J
WZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/cn9peHAs81amFQyfS5H+3WB/
wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggLQSrNp7oMxhjjbnk82CvYo02twFbe
vNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubsEpnXQNmlfOf5EaK/jnreuhzi9xWvn3AT
xG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDrsWNRcPTna19d6grp+/P2pXUGZ72srintwD/K
MyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vuu7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrH
Kscqxx9/3wq2V0ddHXV11N/d+0JTMqdkTsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Ze
m3tt/u5n95/77yfo/6aqiqKqoKqqqmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z
+f3g9wcCilK4PXjwo4/eeqtw+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j
24K4j9ufnnGW65axxswAc0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE
8bDQ07ACpN32mJhloL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/Szo
GawVe4H4o6hZDoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4
//EPXU8NhLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbz
lfxvlL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U+prF
cg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBuXzVC6pm0
gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175/OF50XA+5dZ7
rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXzYhBWCvNNJ0DZL16W
loG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9vU1rwNDJ3N34BBSZFr4+
bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98pQbsTzze7szzkN6ITYEfQVtg
nB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmCmrtGjRo1atSosNb5cYlsGdkysiW8
/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af
2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3L
ti7bukB/+tP/736SQf/xFKUgkS1I2f4906aNGNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf
3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUVBQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3
ZNlicTh+v/+o6/+ogriP259OnLOs9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4
RIoB7XOttdYPpNZFR5ZbAuIh62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt
/SPBAPo1Suo24IFu1L8HvRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJH
zTth7dklWVvjoHTHSmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D
5EVy8pVP4EGCfVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfa
aTC0loeJ30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+
2T0S/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F7kU2
i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpcuvMx2OOZ
pnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V4Pb41FYPhkG5
F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2vg+OvnEq43R1SLms
V9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHixIkTJxaeHz9+/Pjx46FE
iRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUNGzZs2LABMjIyMjIyICoqKioq
Cjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn5u6su7Puzjo4fvz48ePHC8MXPC4u
Li4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQoVZWqSlWYkTsjd0YubC66uejmolCmTJky
ZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0WdpkaZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w
++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFr
xq4Zf/z9ubHmxpoba2B66emlp5eG8+fPnz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe
8LThacPTHl3b/7DNaZvTNqdB+U/Kf1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiS
viV9Szo4nU6n0wk1F9RcUHMBTJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5
oeeHnoc2MW1i2sQ8vnH1qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z
+32+gpng385IV6kyePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv
1i3Iy7Nao6LAaHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvt
zYgPx33c/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsC
aMNyW6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4flL7
luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5EhblTw7RI61
fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUzJhVi46JioidB
pDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5H4S+YCirTAebTfrc
uxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjteBUNwk6b+pcKAWsTw21L
f+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc3Ku9SfnNoHRqzPHi88H2vpwW
vh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fgbZV/PmAHxyaLKo4BY2v9Y6UEZFRJ
eeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHuobzz7uJQ8UTF80USoGTXMkLJb8F0yNQn
VAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyf
O++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJEyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6
ggTmUV/1bym6peiWorD80vJLyy8VfsVebm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPU
D6Hr1K5Tu06FnF05u3J2wcw9M/fM3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oeP
jpO7O3d37m7IL5dfLr/cv9+P5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlh
zwx7Zti/3s7U7VO3T90OJwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8p
flP8Jni35bst3235z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/
vjJ8ZfjKAN84vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7T
uHpc7+v/Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1
K9z26VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QIqUAa
Jr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqIAN1NSQRA
QgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID6U2mQ8rqrBrp
D0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4cfXutrvWws6O+7PO
bgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ9lsOOHqCb2vWK2nnwD/c
ednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn5mG3COlfZg9xfQkPWmdsy/kG
zCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1LFjPmd4wxoM/RnmdhuAdpt7KTYVc
MbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdztAiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJI
H5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODIjtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLn
GTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGTbWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuF
zYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0Ct
ZxhpOAN003xCd2Ct0FyoA9Jz4alF40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbD
tc4F7RS0WxDnX22/IIFZu3bt2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03
dt3Y38zgPnz9n1WkQ5EORToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJv
ht8Mv/nX9+Phkpqh5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9
G+VJBc+7wMxZM2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n
8bZO2Tpl629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW
5BosPrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpUq/b7
9gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6tlYehHhu
6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0eJm8GVoi9dS8I
n+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKmhSC1NW3Q1oHwjCzK
rUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgocRqFRycYQ5S3hVn6ECE/E
iLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCkR5ioNof1T2iVyYMTNkPd0oNB
25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e2jZwp+SNTs+BQKQvJL8j2GuY20iv
QWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC
6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNBnyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/
Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtOCdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVf
BHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3uaBsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH
+VNQ5G7Rj0sdgbDXw0fGLwV/28BUqTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR
7jmyR6QOAm2GMTJ0GDBffVl4E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxa
sXHjxo0bNxbOCP/R9ZgLapsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQ
Tgonhd98Na4N0AZoA37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAE
JzgBdKMb3f746/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E
/6PvzweJHyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16Qm
NWHzzM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBbt1q1
ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/YGWfzcVcD
uTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNAHCItQgHKaudZ
CPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGmHiRt9E0yFoUrSzLH
6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWET8WODAblTTXTuwwC9QNL
vSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2WdcZDvIyhpid4dEQPlo8rVDzkF
1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3MseRJwRavJNAg9Ffpz5BiIHZfoK5EL
ifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30NqfvTOuZch3M7L5dL+xByt3pD/CvA1tfe
OiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUUy486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSA
MgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEH
QBVxWatD1IionxzfwJPnypVNOA+h4baPQgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/i
Cyjbo3hGORkqHKpYv1YLsCeFfJf4M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvn
T7x46hSkHsrqd/MoqBHmapZU0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtN
lb2Pb6AWJLDFixcv/tsPkoL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDC
gQowadKkSb+txWvRvEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyX
Zr80+yVYKCwUFgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYR
thG2whrnGsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPt
wvYf/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86vnfv
tWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3+fm/rtf8
6FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG6ufg/NwbuZn9
ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08tSkLzledeTk3YO2s
dec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf4CVqC59D4Cn/Lf08iH6p
HTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5Kr5v3wglXzctPDsHskqHp+aM
BvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7NE6/a34Z7FczNS9wD7Xbe7rQx4Oua
2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAsoXf0tIG1nTrQwAFzFPBfVXHDN0p837AYx
Ri6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwno
s4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKl
Y2IrBCB0onQg/mWwbQibhQ+Uyq4zTglSRiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+
okHIfLCPdxjCVoH5A/tsSyXw5ftKCXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQ
vu72gOsmyGueq90pAx6MhvBPQR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTx
LeAZ2ujV/88g6fT4BmxB7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gN
ozaMglEZozJGZUD0neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej
70bfhTTSSHsM/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1A
faA+UIcHox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWI
eqTwZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/HX/h
zY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2h1Ue3n/U
4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv/uST/2iCpyDu
4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFfjPsFjw9sxvB5EYtB
vaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75KfQWE3oYnDeXhZon7SRdW
QPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5GSo8iN9gSAJrd2tRDoJaQW0t
PgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36sBUBviiAkgHhQF5V3wF/TWTGvMxiT
De3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W
3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXRlqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMv
g7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y
/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfE
KEsVuB2ecfv+cTDUk3da+kDUujA1thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8s
r7Tehpjc+E02BSJaRRaPygTDEPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW
0n4y7AJnVEpOSjfwrcwedC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDo
E+gZaAeBQ8pq31lQZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F
4cOHDx8+/K9PnIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OV
Ks8+O2MGVK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0D
k6lYsfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GOHDly
5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH546Dtj1g
XGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c97jmkLnAXcc9
BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5jGHBSb6VfBHGysEj0
g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bIKND8asdAKOidDTPU1aAs
slRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbUmOM9Bm+crfnuhW/hl+X7Lp36
ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTCd4TdjmgIYWdDy9ltYGkdeceSD3p9
fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW
9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIW
MC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN62
0z4BAobAKmk4uCbm/uh7EvI3+C4HngXJbM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSs
u1/10kYIxOvN8uaD9rH+tvAe5JdwV9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/
RmBEIBL0idp2dTrop9X+gfqgBgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7
wV8U/M9UsOzcnpV7Vu5ZCQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6
j9Y5/lf5/f+4Ztjnc7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3a
z+xst1tRIDTUYpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTC
uI/bn06clamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcM
y83dDG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArCFLGD
2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx03IyrCYbz
9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG78Kz5Sr0e7of
lJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5W80TIfRLR35UNIQk
hawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QXy4CS6NX0LSB/Uiq/WBfI
65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9FmwY3gmYSqkzTS2TX4ZQvbYD9km
Q9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1ls/01CPi1ndJT4C8aMBEDOTnpC7zP
QeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfkNr59Mn0TuDpmpST1BeW8sij9I7B1t3+p
fQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2gVNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8a
tBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLph5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9
AstYxjKAoQxl6J9tNSgo6HF44onSpSMi4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHi
ERFw9uydO5mZIIqhoSEhEBY2ZMgXX/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/
+tPcfj8kJPxaQBEWZrFIEmRliaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9H
VSE5OTfX7y+M+7j96VKNB40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/Te
HkdCIG+O/pVcDYpcbVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9
IEGNXFcpF852veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4
Wd+mrwJ9mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqE
W0zOSu9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQL3tm
590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkzgL+M+pHi
Bf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21IIDJbXrPuA+0
zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBMYHsgA9QG0mLhTZBi
jMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmXu0FufprHPxPUE2wJ/AJy
nNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+HhBoIpwGPUH4WVwFvC9uk74A
XdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+QlZWT43RC375vv/3113Dx4rVraY/j
JotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnPPTd27KJFcPr0tWv/aJ3ox6V69bJl4+Ph
xx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t15vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8
wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9bbn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgTh
JCRMNr5cdBBkD3FXzbPDqYyT2qFZYClnNIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQej
hO/vdwN3hLQhcAu2n9hz8btL4Ovqp8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl
8oE/AeSFNDCfA3edPF/WQLi69lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2A
RXzN4AF9pYjWGJgibBVDQIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8
ufk6iJsymt8E5AnaPPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuy
ZmRdhhxnVn25E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ
/QQAmaZaMgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgo
qVwC9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+UvVoR7
i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0q/p9zQDa
Sf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp999o9v4vt/zZ9O
nC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AUTB/HRIZUB8MKZsib
IfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZMze+TBNBPBvyWuJC0Bdn
rksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294HAmsCy31TQN5hirA8A+pRbaM3
GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itFxK0G+xVXpKUD3EjdundNHNjnlUmr
3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8YJXQm2zQF+kX0UFIYgzHQaylRwulwdBY
T1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtAjrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRp
zoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73nJIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi
6LvFfvQD/RVhseACoTFLhATQv+BHcS3oU4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTac
MBwG+XRIo7A7YJlhmWH7CcwO4zrzYYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT
+mx2Q+N3Grq7TwBnEWegyTsQ0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPH
hWHwnXvFnU13wf9ufs4FDyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1Hjt
HGiDlZP6pwCUp8nfPcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+
Fffibt4CuXvUK+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrW
M2YK6B3lm4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymA
b6zrmfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/OA54Q
hodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDgPereCUJe
7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7MeM3VGzI/dZcM
TIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6znAzJBjBGHiU+BGGV4
3/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGqNZAO2oyMxik1oGnxZzuX
bgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDbYogaI1e05IM+jmrmJZBYrOj+
5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0QPzcso9grkHTYvUN/EXZe2PbJfhck
z8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgRhiflX5fPCc45BwUFBQUF/Q/xp2ucg4KC
goKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0EwcQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAf
EEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDA
j4oAAAAASUVORK5CYII=
--089e015387dc9ab4dc04df0a6f13
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part26.07050304.09090705@mitre.org>
X-Attachment-Id: e928b81dc41efabd_0.1.1

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAACXBI
WXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAIJLiEoIGg
ETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlTp09Lly5dunTp
khC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLly5dB/rMr4ubm5ubm
5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc3Nzc3Nzcfgd34uzm5ubm
5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zFHGHAI0sR61oQpSxdUsuBrcbb
pFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL5KL61yAdzP0l4ytwdrCmZQ0B49ng
q9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5xhJQD0ijlA6g5aoPzQXA2i9znjMWcodl
l8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteBfaB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHn
u0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGz
l2e093YQJp4ZK4D+G+NGeT+oM131tF+h+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRG
mAkCkYsLFwDS//NGKvzbkoT3kJCBAD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o
0AicE+TFUiRou8QMPMH3hee3xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8
I6cn2B8meCh34eGjN6VerAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1
YO1qH6dbCKnhSYG5oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ6
9MW+HWD9Tu2S0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skj
ff0g+X5SBR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBN
v1lcAOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAYlnko
7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm+Bj0TqE4
h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9bF5rQRrpqG3v
Ct5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk00D+UBkr7oI2QPpS
CgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2qwt9Le26NjkA9faXTy79
AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3YG7o/SZiFChhSkm7DkLe+n1t
tYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HBdoFdC68EZ7ajSBEJss5l5/IM7hd6
qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2SiNe1wGvbXI153fwpnrSgWc/ws2y92v8
PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJmfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNp
dxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK6
3RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQd+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1E
j0GgzhSfuayglYmv/7gaaIn2W84tIN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqv
b/8C1AilmagDhgX6FnoPMGzxMnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUC
wLFVHq31B/NoD7P5ETA2O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgn
rBvSZgIG+Yo+GqxDcuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPo
K3/MPEATqdIiQEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJD
QtfUg0mloXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRv
LQkp3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAXQ8B7
LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZPAFvtzIyo
2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yMoDu4grVrTgMo
y8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJfOZ5ZoMXlTEpXQLuY
2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZEGcZ43wHdA+movjR47/b6
RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaBVxGvyrpeYM+yLs/6HuRrzh2u
FPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9lOZgn5ijt9wGfbJezT4I3PY4G1QW
jF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B91zfDX6/wIOlT+LjW0KJbwptCyoOupk6
L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGBLwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZ
EkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNCIWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+
G9grKgnuz35x32cROPa4Clpfgff1xGr3KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0
dTXrCT4p9s2GMVA6uqRnoZXwqFh86hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISL
IDZZ14XPhJK1S0WVXQ5BgUEjfM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJF
WNoq4IDeLh2CzJIZJ42dQL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B
+WN6SPNAVPLqbt4O0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7
gXzJ41LAV6D6Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0H
oqz6hbwIDFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNT
tARzuuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0fXAHU
FPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm5/fdHgE7
D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3cmrwrzUguJ7/
a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBuT9rl+6kw8FSbj3qH
wKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y2BpnVfZ8DSU9ixyt8itU
/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXOMlD/ZOGg5lMhIsn/81oWMP5q
KilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/uv90fnjZ82vBpQ1CXq8vV5VD4q8Jf
Ff4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSpUqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs
2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoUeP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48
kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMoOVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynM
cNSzKvCxstVUFLTLjplZPwNztWDxMcj5fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOm
ZRGIgXYvewOQ+htjlQSQVPtRVwgov9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g
9TblevUCkSLaaS/BVV8NdWWCeaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZ
Lsc8HtRHzkr2EZC9LXt4ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8
W/UqMvUHKHSq0J7gMJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwCl
su4jMQucu5z5HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZ
z1ch9JPQ/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPg
Afh1N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+GginF9
wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe3jjveb1L
79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jUkKkhU0EZrgxX
hv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k6oXAC0jnBbeAGCxi
JVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjCIFfUVQKpirVnVg64ZJrn
GkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQldQaC7us5lAaWqTHxtsB9xzkr5
AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6Rtuuag7JUPisvAGNdQwVjfxClDb2k
AWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBcQxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL
8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/qJoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lK
Qdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJimvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazho
Z0SschLk86w2FobUjm/TMy3gW0ye5TCA+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4
rE8LKwDpxbLnmifA6VZJ+61pkLgk9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULK
Q7mUyAE15oHjpHWXawNkdpJdzvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX
3KOOqVC1TalujUxgf5qdEOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKE
LZegyewqnT8YBj7f2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1j
LZgePz1+ejw0/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yu
v7n+5vrg98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQ
iynrI5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIhs05q
VsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/gi7EEGYq
BLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5llewH2laX3a4H
u5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcgbZIypRagLRXn1Yug
+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0VOoPmZWz96fHgfm8uRo+
kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1B1xTciv4SvDgw9i714Ph8Isb
LTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9EbyrMabKEXCdoXJmAmRPdk55egZi
vk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH41i7Z+BIaFO8VkZzDxjjPajg4CUQ+Cbk
B6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS79fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjt
rYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27Nezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82
fArjt4/fPn47tAxpGdIyBHJO55zOOf238eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHn
jT5vBAltE9omtP1PKvjvI93vRsI7dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjI
yMi7hf/u78O6D+s+rAtd0rukd0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf
7e+9tf9/iH+0HeoV9Yp65benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunL
pi9hwYkFJxacAFspWylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8
bo5sFhACUh3s7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9S
FX0HT0DyNOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNp
i1ffgJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUcTAS4
ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNiephdP6gOW
12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4KmeJcr8gu4urLX
FQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAEF/BbaS0AhoaefZI1
yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4WJkj6SFgn0ePgK/BY4+S
EXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjdvMqREr/AS8vrC1lDISX3VTnh
C35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgykjLn+22FtW0OZGzPD/5+/h29e0LR
zOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHMiX6y7xIwV9et9a//x7uVGCwGi8Fw+6fb
P93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8C
RxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eXlxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8
xGhB/wX9F/QHeae8U94JXehCl/+i/uO2j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5
FxCFYgvFFoqF6Xun752+F1jMYhb/69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNT
kU1FNhWB/J3yd8rfCWJ3x+6O3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZW
K6vwovqL6i+qw7bobdHboiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn4
0gFrWcva9/C+/bPnm5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHci
iOuqyRkAcnfpmVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhS
YWmZIQK0eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GB
vZVkMD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2RlshvQV5
pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn3/3wh+aw
8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV1V3RlYWzwbcz
r/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZajgMnpP0DfJ1htwp
lqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3Xzs4Ue9cyPWjcPjolY/O
nYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp+Tv7Fqi8pPjIlpMhJS1mYY4K
F3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+nvRwVPxkeWVO6PA6G89cf3th1Ci6N
iHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsticJZzlnOWy3s+KCgoKCjob8svsiyyLLLk
fZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcffABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74
iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5
SOcjnY/kbV//YP2D9X8xIvguAdvivcV7izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659t
x+F5h+cdnge7Ju2atGvS38Zdt27dunXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg
7w6A/o7+jv4OHJl9ZPaR2WCz2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9
+3vnm5ubm9v7neMsAy4U8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlI
SVKaXAkYKO4JG4gX4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8
HaTldBcjgHoZxeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG
/CAbdN2MceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAY
A1IleZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd73i97
+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsTs+HmTUi+
ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQu9QfDLNME9Q4
SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFafkM9cPRhUvEg8PM2
7U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1bqArEesefyO0JZxOelLjh
Ab5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbTNHBe0k3RjkFGR/uF9DKQkz+3
rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPwz3nlU6JTolOiIbZgbMHYgn8bL6VN
SpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYEa4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0
gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/
aMc/237mM5/5/MPe9yoS/13teDfl4t37905NQ01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9Zd
oA1taANFuhbpWqQrEEAAAXlTSt5Xe5tPaj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76Vu
IPJLbcUW0CJoJMeBNFMrmpsA8oiA+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5E
BPXkQKCIGKDNAWkVVXgMPGKJOABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEX
rBscJvEN2FYafjGPAdev8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4Tsw
FfT53vwtpEdZ4zN6gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYU
yB6Z/VXKc7Au8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90
hWx9cmZDYEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn
3Z1KQ2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMmS+tm
NNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJfQu5q+9cf
1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OKP+wLHlPNY70P
gHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA2T/Wrd7dyi95vuT5
kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdffPHFF1/8bXzbBdsF2wWg
M53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePdXOcLXODC327+rQRGW64t15b/
J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc85C8ulHQ6nU73B/43eTc14z+8W/Wl
CU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RKbUAK4GutKMjNzeUDfwSxRy6YcwJYLMqx
D9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZGbQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjx
ufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHTu4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I
0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hmgscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpN
oATJHZTDQG/nRGd3MAyTo6VZEHjYcNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2z
j4L2ncturwumROmK6RIY1kjnxQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5
x+4JjtOZvXIiILtJgr7wFSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2Dj
N1Dgq4B63haIcWlvpGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCu
V+c74HNlTWItiBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQ
Zyj2U9TpoOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrG
RNMM63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998Obaa1
mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdjn4x9MhZi
YmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUArWtEKIttFtots
B6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2oW1C2wQ4dPjQ4UOH
ga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0aNGiRYu8Ox/tO7Tv0L5D
XrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90rUAMkUZ41AVli2GxshLEE+Gl
zgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01C7QFak/ZBnIT+TNJD9p5MV63FpRp
2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWfljb6WWgeSrSTnpl0Ht43ph/xVyxqccT54M
Lz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBzYY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1
rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wEhg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB
4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcVpapgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP
4y5AbFzCgzefQvZcY520L6FswZIHO9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP
+Nf0PubtB47H1o3SS/AdZNjumwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/7
7BeIHhwcGPQIevRo8rJHCzjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9b
FU5/fGJSXG/IXF9xpysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0G
XWlDmLYd/Lr5l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok
20RwNBCzFRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvW
rFmzZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7be2/n
fTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDLgJf/xZco
31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAgcUHigsS8Oxp7
w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEmPEUMALu1BGCbNIwa
QBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De7uXeW54gjwvwL9gP9Jmm
ZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQOfXUScEU9D/0e4vbGJSZ1BfsP
9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9LkemgGd749c+JpBidVk0A+c17XTuGbB6
W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I3AykW/IE3XqQjlJIag5Sc3FKqgy63uom
9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEizNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+
CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQam
Y/VOQSOfKjerzIXXZXMbPt4Em8qeKLZuI/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8
ToakfInHM3tAzoDsMa5seLEzW3/hOKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1
odT4SA/IapQzLLYYmPqabliegmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpu
xGh4UTLmyNuz4LnE+ytDUTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCr
qcmq9TuIkbNW5XiD7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWd
E3dO3DkRXjR90fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA
0tJLSy8tDZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY
/Grzq82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQuh3r
dqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj257f3r5cj
dHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99AHRihisctG/V
jfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24bw8wlAx/FZIBokjW
w5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7mgSZc9NfaVHg+Fn9QUsE
xaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKrOTmOcKCiPdD5Ocid9A313cHv
cPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0VdClJ70UWuARg1kzYd1A32fdafQZur
fs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbObAHTaK2UoTDobb4PfQUIEnpkh4DJqi5T
B8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8Fa
zZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LL
gJnAHXHCFQupG9LfpI2CUZX7jvo2P+hXyw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHF
q7fV0wSEFw701i6DlG760ssMvh/qfih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSV
xz9CRp+UUq9uQF3/OqfKfgV2P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZh
kDYno2ruAwivrr9kOQ7SaO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z
774cWPJsybMlz8KNoTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuX
L7/PEWcFgQAyJA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C
1EXzFVNAquY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ
8IyqvKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Yy9s3
2Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE865Ky1j8vq
Dbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41PeOgYkbpj6Mf
QczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1OuRvJt+u1RO0Otlb
dWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/d35is8CJxGuTz0wE81Pz
4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7JDbMrPIuCjIPWFbcLgtcN77NB
o6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3oPj1Mqsj08E51zZZNkO+7yNvBdnh
dpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQddVx3GED23bPbTjAOEAX7+wPzuHKJfMs
iJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1wxYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk4
0KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWhouAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtb
EK+kafpToMyV4ikIUmG+0caDKCaCJAOIEY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyD
YUqxoWW+B9cM+9eZi8FnctUHzaqDXFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry
+ta/Gej2OLras8E0UnqrdADjOVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz
6yvub4WcMzHnE76E1AI5g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHO
Z5oniMG6IOUaMN5YwpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhP
aPWMS+HhPk+XvS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDb
BOdKW2PQ5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhK
iocmb1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbKZFSe
VT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7Ro8AV38I
qOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9dfHbxWbhQ5kKZ
C2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6NOP/xxNlhz7W9AKmY
FC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyANFJFiAriWsFC3H+TG+hf6
W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8Kq0Gj4dVTtfzALNX6U7VC4Ec
SZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7ILVDPsdSQAt5TvHf5FgaPaGOUR18w
V/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZT
QFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9ApBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFl
OGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+fIMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhq
ZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0
iGmihBwJWmM1g7Lg/Ez7WssPWi2aqd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E
18P/Efi9CLgREA26guYSxsXgfJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjb
gPO+rBMTQW7pKOh9BHLLvS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5
A9D3MW1wDQNrAfOt2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3
c3Nzc3Nz+yPe31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQb
KK0GkSAKaN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdA
d95znXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3RsI3
ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd5PFyMshd
RbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf20X5I35bwMtEA
Oc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRbQafI6+TvQVsjYrkJ
4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhhWk/lHmgtxWeulqCOsRfU
7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0CwHvj4wVHSngv9xjhn8zuN3h
2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skGheG635MJj9aA9YTRqq2DwgWL5gZ9
D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5WubVoOanDkzoTME3vCYKY0Aj/xyTKWv4c76
t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5ubu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4
iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQMmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1
E6H02Obtys8F342hUb71wVnN/2WR5SC2as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWn
P8mQfdTxOGgP2DZnXXFWAWePzA5x34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y
86+t4DiddCJ9LmjbssyuD8BVU74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3
AqZr9/gGRHVRTGsEoqe62fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7
IU28/SKhHWgX1J9cHcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPH
zPYgxqSPFFdA3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55Icht
lCRugS5Ht1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT
9me1gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy60UY
5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+rKcCH4pC8
EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db/xbWVSM5PaUG
FOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb2QmgdXattvkBG/Q3
pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5TIWhbQDOvMFB+UvIRAerR
N4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NPkIzSS2kSSEdERyJAVNJiXfVA
OS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRSA95+k7vF4gOJdeJfvTwDKSuevH14
FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keYwdnRct0WCFnPk5+lRoKjq2OwVhaUunIF
fSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGK
XJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf
9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYBy/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4
BWjrRIDTCdo1Vz+zE7x6eNbgOOT0zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBt
AVT4oOzXxVeB7q5pZf6ScLnPnfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5u
bm5ubm5/zB9OnHVd9P1M/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnk
BHldQEDAXXBtdHg7KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7V
BZSwYktrXAd5v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV
4c2r+IOJseAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bN
IAbrJ4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVtFdVk
MDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAqqowFsZ5B
YilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKrsbpdbQSap3ZD
PQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZjL/Cp4CNMEuT+aM/n
GgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSeAvMh85PU3dJ9cAyU7ruu
wdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/DYbjz4m47x8fw9PWd/XeiwedM
uWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDifKbuhZGXRkHNslXuV6kF8jVpi0gA
sUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8CpiX2S2C4aCgpfQnaGtWTTWDoFJpaeBSo
V7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pfg35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN
+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8TnUevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAW
jDet7XKiQVmbGpZmAF2kTyvfB6D1cj513QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Q
a2PQbQFXvN9Rv6GQ6nRGahLEzUgekvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOf
X8Dp5dyozoaURnGz3kwB+al6jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6
FYon6A3SeSkIFEno6AziqtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2ag
NBLNyQfSEKmBVBqUh/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjB
XssxxTYQXGWtJazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0v
C9nTc6zpCyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx
+RdIJdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ctZyx4
NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUAjk9yK4L4
QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4zT9BVwhcjyzh
Ed/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50feu8DGK5tlxYQLoj
jRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v7IHEZm94NRWUOP8evk3A
97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBnELw5X1L4CvDN75vtdQJMV/QH
DTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAAjSR/+QcwWHQ6OR/oBks9yAUtUPpa
Gwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQNstfSdGgd0qHpC2gltSechDskprs+glE
GaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9v
LqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/B
nuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5NbwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1Ma
vikIdalHnT/Qv979gEdOTk5OTg7U21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqq
MGTIkCFDhrz/D5BVq1atWrXqn4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFy
itsm2n1AacAGMQNYS7w4BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3
FHSbfBJNRsCXRpIetENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+s
Z9LTgCYuV2pbeLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C
7yGWwdlW8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVok
vMy8d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEgSvOK
WSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxVx6gXwJUp
7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71Bmo2TvuC6Kt5K
PiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/whtyHuhH6mpBuzfox
2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D5qOVdSWD64pYrVsMhiuG
XVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYUWVBkAfw85ecpP0+BOhXqVKhT
AeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfIwAoDKwys8Oe9/l9NXBPXxDXY2XRn
051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt524ufLn66+GmoVatWrVq1fn/5ChUqVKhQ
Ac7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl
0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byczn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgA
OHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8
FMR90d7pDfr5+qOeHcBpSu3xsi9kD7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTF
Xl96BL6i5BjvgqB/qZxO+hDUyXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwn
DGvNd0AqqQYaRoLutHel4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TP
ATlNFywNgKxlb1ak3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXS
KoBI0xJwgrCKQcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaC
uCS+YTuIg/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAag
ptijaSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD/YCk
Kj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og96s/AH0xa
fXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYPt2BItSHVhlTL
S2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u627rbuv+NgH6rfjl
B5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgsBovBoC5Xl6vLodTZUmdL
nYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkns05mnYTmC5ovaL4A8s3MNzPf
zD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225ug0unL52+dBrqUpe6/0U9X058OfHl
RBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6LV1cSJsEvF/cfO/McTIcNNvNXoFUXTVkK
RBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3Q
vQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao
4AE1HzVy1fMB44rgnMiKkNLGttZzH0gur/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxv
MgtZfCDjI8u57J/B/tDjc59KkPzGu53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ce
Df0AXNUdDrsK1g/eNkq/B4W+jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G
3RFRVGsGpsVyT3kV6CtTWP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7Nb
hIH0hWu36xY4Njj7u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgu
gBIkZFEUdFflnuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTW
SO3AMFDqRjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqu
rwzeH+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38IfR36
OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgntEuD2j7d/
vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz2cB5yXnJeen3
v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJEiRIlSgBDGcpQ4AY3
uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwYbHq06dGmR7C14daGWxvC
8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz5syZM2fynn8y9snYJ2PhZNGT
RU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfhd2fEnRF3RsCuSbsm7ZoEL8a/GP9i
POx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/HHx5xlg3yao+B0GBnBWOd21DNXCm9UDuw
Oh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhC
Fakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SOO1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73
W4D/EuMFwxLIrKwv698UHDuNelMiOFMdUzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lH
GMHw0KdPwDLIDbA8M7QE61JTTWM9yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8
iwZU8f8UnJ2yI23FQb9VO+66DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJ
b8GwWVfOcBxMM/UHDCXBMcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC
9HetAhGgmoU3uJppjygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJK
jnxcag5qK9FQGgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCe
iQ9FTdDq80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DE
fENpAiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycvgfo7
SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/EPpAfyY/k
R6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESlv7//5I7JHZM7
5iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ8Olrp6+dvgbJ0cnR
ydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpapWKZiGdA0TdM0uH7j+o3r
N8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95PvJ8BD3X9lzbcy1ImVKmlAlX
GlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifKJ8oH3rR90/ZNW/C/4n/F/wrk5ubm
5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1axAREREREQEtsltkt8iG++vvr7+/Hi71
v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1DmocxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X
+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+ISdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPA
Ucfx2tkd7DucJZ11QdbkSvIbEDvEEhEGZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYB
aXipVhVc4PNZ47s9N0GwpfWhgR+A7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk13
1RQLym7da7MA+xXNyxoOak/H5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9W
n91z5j487/q47qOeYF/ovcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjq
lq8c7DEcrHbwJaxK3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3Q
TQTXNe20+AI4Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6Vd
wCfiqigKan01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4
VFd+JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyrpXbg
HWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBTOcjZkDtM
1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0I/Iea1e1q9pV
kFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/m1rxbqqH/YL9gv0C
5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d+sfLN3rW6FmjZ5DSKaVT
SifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1L1BxUMVBFQflXWC9G9GucLnC
5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1nPWc9RwkzEiYkTAD8uXLly9fPoiZ
GDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rCMmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8
WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wpluiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKf
s5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpn
lk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWB
x+QLm542gVc1Ys4nrwDbaKLlGuCq7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw
4nXSw6RJ8Nh+6fMLJ+BZ8uMVD76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8q
cjLfd2C4rd9mHAq3H9w7cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y8
4QeVd1awlB0LxRsUeVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwf
mKf5VwXHx/ZLji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt
4v2R3zIw7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcB
K+ncBT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0GjhQh
LEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb0TaiLTyd
+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFxcXFxccBBDnKQ
/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se5S6Vu1TuEtyUb8o3
ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU+/3VFyvFSrES5F5yL7nX
b7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH5ZBySDmUN3XJuNW41bgVTMmm
ZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X56wvL5oHNA5sHQuonqZ+kfgJvD7w9
8PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfXSf7i+TFo5lE7uq0C525dfn45BGxeru72
6lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZrN9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8
cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYep8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GX
gcs3NdjSDoylwvsWqg7+HWpOKvkLONdnf2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36
CuxHIroWGA8v92a/theHZwUuRV44Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZ
Z59+Gbyc9mZRTEeIO5X0aXwW2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNc
YUIv7kPGzuxo+4+w75cjB0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qD
T2vfix4lodub9t5tqoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1
OrdGQOrKtFGp/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2M
mKEVA22QJrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEi
UCSBWoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9oNzc
cnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm1ZtVb8Le
2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCCEu+//tk9sntk
9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m8ZnFZxaDT0Ofhj4N
oerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pSVamqlLf9VsVbFW9VhOge
0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c6Huh74W+UCy7WHax7Lx4745L
o22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269GErZStlK2SCqR1SPqB6wK2ZXzK4Y
4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd
4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNS
n7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6
vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJT
El5Nva2/ehRelrg974YFUl5oE+kPuqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLh
o60FR3m1jLYPlDjDFIMF1IJqD9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5
qqme1xawVLeGak1BHem05Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3B
Z5xPCc9zUHZv8bji/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfB
ccrxNH0PiAeugY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD
1l59S35goXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0n
nRFZQF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUsmD4x
fWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1q9SvUh/2
3dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39behZL6S+Urmg6Ld
i3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk/ceLSopKikqC5NnJ
s5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/PfJh3QfFurnuthbUW1lrI
b444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/6ino5ub230S6dOnSpUuXhKhe
vXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2xrlhHWk8orCuypdQxSOyS3fH5Xbg/
70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0CP6PPC/8C4H85aHrIS1AXieZiOqirUs7d
fQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15
EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhDJOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSn
V5IGZ1ggt76H2fcc+B7yDPD8CuzdrOuslSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb
0KbLtbQUoI2qF7XBMd0+yzkNxBFRT+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEdu
B/IFeYBUFaQp0hKpF7BeMtMLHGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+S
tCzQJct2XT0wDNJflKeBOkc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcM
QveEhgRvgXyDw46GF4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6
roHQi9b6ieDaqNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY
7mzg6gOuyfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFl
oKR4tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX25fb
l0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c06aSTTjrp
vGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQnZtwLvDGr2fW
Q9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfFnthIeHr3+fzodWC+
73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3oJhqHp/pwGPxOSuAsuKg
boB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2fptkGgbVMlpH590FQm4oFiz+E
l8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKiXlHfBa8PJfaIqwKJ51M+T6oNjFNv
ij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGCXti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRH
ykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgr
spZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoMaWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZp
M1I/DDKL6KtGwMuPoqcnnobYVrFfvtoBnvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3A
EmFpaA+EJ8uftHpogLJSrSIuQnIuZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYm
riKc+fxCiUsfQsycV7WjNkDGXzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7h
nitgXNT7GL9AzJKEOYkx4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA
3GZuM7dB1biqcVXjwJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR
4EoxsA00EouPguCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4Mt
kHdLaKPiN+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZ
lDJOQkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7CawTMwV
OiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADynllQrw3K
APE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdSV7kD5kDjrnkO
xOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJgelkvq4CYZp4U50F8
L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMnopyFq5YuSL1aAj92xxNoW
6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+BC8evT7+WoHYbxO/i1sBrE0Y
oC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasPAqWJOl6eBLWB8qXNH7THlr3yKuRw
h7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/ocdXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/u
aP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumkk046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P
9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xkboDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh0
4lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8
dsaOFAit3TZrlxxgn5k7Z2kH2HbmquSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGC
cSDzrYgu8PDuxXmXdsOTUtdKXckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNe
z2McA/Gd+EmtBZ5IVybPF6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0
ZolYBba2ts9UfxDVzZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RI
MN6XsfIm6Iv0CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gB
GGKj+A70BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7
ymvW5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghvAQGf
+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8C94+cV5n
jiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARFwqfxzTP0HgF+
Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazvg/u1Z7OeCGKpZrd9
BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3ewgwDz/svyt0cDfENdgzb
5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQRz5TmELDaUdg3E8hA/ZlRBxLP
JmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4sQRaQzeUd2QtEJfZxA0Q1WuAC+aX8
SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2eUa8EpsW4LzeDvGYW4zqIQOWxkg9kD3lK
rgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7MZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke
5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/Wulp
FOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1
CXgyePq7zwHNzJFiKih3lQvqFtD8NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1
iGWAz0WwnbXFBGYBadXClW7gTnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olz
wlev6qeMgkznLc2LFIMeQY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs
7FPk88fg2pOyWZyEU112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwq
PBLMhuYQYxEoG0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUI
PDNeToo7DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3Z
mXAQki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssMohh4
X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN1CxaZ207
yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2ahrRoGzSNGU/
UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ksn4FYqnxghoP1pvWa
+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUOMEfIT7QvQD40n0sVon6I
GRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZb/mN/bvDO5100kknnXTSeZe8
deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vfgFudHt28nx9evHjp++w+KGuseTPk
gJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJYynhISEo69WIN+Md7NvtOhGw9slTL1ACC
y4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tBOWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjv
GweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDgXFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wz
ZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3ijTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh20
0cpp9TMQEcogMRm8ZfV2ehEQm6giioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CH
iCAEmDnN3XIxyAfKCh7zX+8f3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPl
TRDlRX4RCOYnZlGzMYhZvC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhD
bZCP5RwZAvSUuc1zIK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPL
uyC/li1kTpDH5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9
l52iW4LvPft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ec
MlvdLHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDEPCWA
rpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vjonUgw4KM
oXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCqgzvZ+6GxEMyN
ZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXILcwW7cCM56UMB1FQ
lmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6i3CQX5FfmQJmC6y6E+R4
83OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ205AJIHObdrkLaKxkkKvAvGBU
NB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUbMyfIieYrbRVwkm58B1Qhu5kBjBbm
A7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqrlhP0+fpTWoNSWASK3CDK8In5AYjsMqv5
CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywFnmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm
2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ
4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWsXbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGT
o1AJeB6RODHqI/C9Zw21Hof7616+ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0Z
R2dJ1D+E8hern+v9FaQUcVqdg0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx
8CCwdwp/bO0PCR2fjH7wHlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeB
vtBcDuIjkaycBCVazab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBG
UT4Dacqi8iSIb0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dg
NqIUW8CSaOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNa
SOQXm0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh1DR2
Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxVEoGOIi8P
wbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9CoKeTTjrppJNO
Om+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dGZQTfJq47mj/I0wHd
X52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3PTsPFK5e7HSkKvn1CS+Vt
CKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC9eVhoDR1+RyU8uZyMQrMytw1
pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu3/f9RoG6VPlRuQVmoNR4CNYEW3bb
aFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaRBQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWL
paj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0
XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsxsM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kY
LJnULepokCbVOQdGjJzFLTC/ZiTrQD4ww8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCo
JexKJWAB+/kUKMJ88RLED2KEmggiUviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLt
ApYUbbPPSZAVzL3KLTBe6qXYA4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHm
TtDvGkP07hDT49X0pJLw+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwY
bD9nHwUJW9yTExtCRAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzp
z6DInBKrssXAo9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+
v/qsUGizst2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJf
Gq6pZ7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ+iOo
iuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEXgLHETDYv
AhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbYWqh+YDxx3fNc
APOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WCmQvIzXIRDto1Zbj2
PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7ALiqDOo92Sh3AK+clnQfv
NM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJIE7IfEpRcBxxDLQvAWWd1sh2
CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTSSSedd8VbV5xfdo4Od24Ga7Btsr0b
hIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSClV0oe5264Uvr5ugO34U71pyOu1IKE2Fd1
ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/LftT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem
/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZrc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYH
gAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2zDcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcp
jdPmYrA1tRRXHoJyVOuk2UDV1BraObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1
ZXbjLrhWO4emvAJvZ2+Qpyt4i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFy
AiPlKtkfSKY4I0EsUpxcArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6
A8gysrCoCdJijjOXghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0
QmBZpPhaLoB1j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tf
DXJC5ltZovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Z
m0DGI+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf5X7Q
73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7HsxbIwYMCA
AQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fvZLLc/5383X76
pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUGYh+4/GKnwpO2Ly8o
F0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjSZqpjICXG9Deng/Os2TFh
DuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru9wYgk2wuQkBmkCVEZxArRCk1
C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVMXFfaQ8pUZ+2Uz8B9Wd40B4LMLqLF
ZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Ym+QcszlorbV26gegVlSrq7VAGaOMUCaA
SBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoa
KB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7mo80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCU
FVVFQaCW3IovqFYxSf0ItKHqYrUsyBSzsugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5
+Vz+DCKKcWIyEC+uKs1BPaw+spYCz0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oI
E+QB2cX4ESgiKtMElCxaDa0CGPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX
7EMhx4pM8ZmOQc5zER1C/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC
+6/yU8JPCT8lwNo7a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZC
m0NtDrU5BJ/7fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/G
H9nhP8VP/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3
Xdx3MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9SKnq7
JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs/KEmE+Mh
0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7lnOWOhaTaxiTm
g7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKWu6Dt13ppy8HSW/tE
k2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9biRxC5hUc0AxbwMeuAkVwx
k4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPVjWCZr23SpoH8Ue6iIrBJLhYl
QDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGguNtaCaCf6KQqIzqKLehXwECmqgmWJ
Za9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWf
A/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46CrCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs
/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JCvYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQl
cTjEX0rqkpQA3jNGY89OsLVUp5vX312gHog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7
uLi4uLg4GDp06NChQ6HBtgbbGmxLaz/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yH
Dh06dOjQAW5WvVn1ZtW09d27d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZ
smXLlmnH07Bhw4YNG8KSK0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW
0Ug9zj/jXcsVkz0me0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P8
9+1SKzh/ZK831c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8
DG70v9H/Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zc
M2nb/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPaeS4V
Xdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G+b+bt06c
vYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2wlo6dCjxMGhij
gbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHgGeEpaXkFkQ0ibyrn
wPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc1wYogRBb90HR+2XhyaNn
AU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYuMRVkLuOq+RwMRa+jFwazES3N
vSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5EdgXjevGhVADBRdBKBGq04RBYpBdZqD
fGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZY8C61dLGEgLWbBZpDQVrS0sRa00QBcxX
sizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqH
gTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+
jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkOWmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3
kjuD9ytPkNMKeht3jpRPwLUt8de4dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8h
iF/uPk0CRPZ73cNZAaKPOJt5Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu2
37f9vm3akPP8HvN7zO8BP7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFj
Isak3emPyzIuy7gsadsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL
07a70OtCrwu9oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1et
TLtwpJ7AUxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHv
Cnz3P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68tYVvC
toRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz7c+Vtv7U
qVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2IgwJHBI4JBAO
Tj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nuJrubQK21tdbWWgtT
f5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQR8BeS2dQ8plrjPIQv8JI
dhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs/hkgx/mAXpkTwV5B3tMbgOXX
pHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVbCFJOx1gUK0S2cE12noRVt9e3/rIn
EJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHcS32HeQLUjBah9QIxVpRTZkByHufzxHbg
XqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzMVP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHF
piQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7aylJ4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9G
LTmPziCnmZOwg7FZH+ndCMpLsU3sALW3OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQ
iRMWELPEbRqDsp4zLARVV2dyErR1yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQ
nBC0NjQpYx0Ic2f6JUcVCMsaUSR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnG
fn2mezzoQ71RugnmV8YJ/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1
cTQDo76saFSH5HuJ++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh
+s+2jZC0zpOJqSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd
6naq2ylQPlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2Wbus
XYbYybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/qRfW
0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D6Lmg54Ke
CyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RMq8j9VX/4I0rP
Lz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6du3Tu0hkyfpXxq4xf
/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0yN8r8D/aNaR7TPAYu9LzQ
80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJoPPcbDwnT9edGMmg7bbuSBoAc
5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2ik8gAFyv3U2Td4ExUWmpbwGfoRGj
bN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRY
ZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36JfB5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrK
soYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRN
dFR7gznS3IIEsU/8IoqC+qk6TpkKopJoI9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRX
ySdiQElR3lOmgTJZOSBegjpIW61tAeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s2
0ApbKlhOgBatfaglgzZHLaM1BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LL
Q/zE6LKPvoaEQbFfRD6DJOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjn
Pa+9u8BY4A1zjQbDTy/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSP
y5GgvzDWeDeB/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157
svUD0G97uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1l
KVlKlgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j7Xd0
jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqNzx+RWnF5
W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDBQTDuxbgX416k
TWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq1t1ad2vdhe2Zt2fe
nhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusESyxLLEgvki88Xny8ePvf9
3Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9qp//UOP+dPd+2g9c+ie8bncAc
rWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuSD6iRxhmxCDIe9GsQOBEyfpjhczED
LLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU6BkDPPFLIGxA1slOCRneC1zkUwiUbfZh
fAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCy
y5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLke
GKc8VVqA+EndrnwOcgFF+QKUFswTNUHMlS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5
zjxi7gXZXXY3u4I6Xp2lDAKlhdJG1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9
LF+D1lzZpuYFrYg6VYsBzUerptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/
Gaz97HvtOUA2MCeb30FSnleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBY
O1teqSr4Tg+wB5+DkFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7m
nll8JmT+IfvsQj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8
Ck0G3+CAHsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6it
v2n9Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc7nM5
bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVeEH87B/2s
PCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P/Zs6tJ1aqUu9
cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+qF3qlI05xhxjjpGW
SP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/omqbX6GbRzaKbQb6EfAn5
Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2fVM7/afG+W956/c422+GR74u
C2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6X7OM38DNKEuXZ8HwIuFuOzMj2E8r
JQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk1athEBn90OE8BhmaOeoETIXkCgGVvQqQ
mNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7v
OTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYr
OcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKwuCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj8
4rX4ECjPeAaA8bNsbGQA85ZcIzeCfEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1Wfr
K0D5QhujnQTlmvKTcAPjySqOg/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0x
WisPrnHJ2ZNagvkemzzbQJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXU
E9R62g5bLdClHGgmgtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsH
gWuwMznxIljzq3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1Mujn
Xf30M+B6qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepy
dbm6HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/BpD5M
GHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3gWOFY4VgB
X2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/aa0zFMRXHVPzn
9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKVq/+H/hqda3Su0bl3
r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7/FG7wkcLHy18FOyV7JXs
lf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83NNBduTb81/db0tETb08PTw9MD
yhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hOmHJ3yt0pdyG2e2z32O7/ej9I5U39
9F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4
c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56++CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Co
yavubi8ENKO62Ruim2vjEgaBry1koN4clGtGeTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4
CLhu3em8BXElkh0uN3i3aPvjpkKuKyElKvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzK
OibXa0iKTd4QvwmeTH5W79EeMPKJvNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqA
edzcb+4AJYc6QKkIyhpxSZ0P8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2Io
CLdyGx0sBTTsDUA8EIvpAcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL
7Eftl3weglWzZfRpBepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrij
XNWSZwA7GWd8Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwI
cyXIEyJUU0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+E
dA+pGPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWielGF
b9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYibp0Du8jxK
HA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ8/nlMMdC7ks+
quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61BA8RhSMojlj5vBi/8
427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGUMWqDskmrKN4HsVM9LU+C
2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZC+p1MVu1AFk5RFOQeeUDYoCu
ZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPAI3lTvAbpL0+YS4DmopQoD8Z7MruZ
FRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSBMkT0sihgWo1OnhVgmsYl8xjYfrVb7fNB
y2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkEwm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/v
WmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5
TT/rLATmSnfhlMNgrSt9jevguW8EEwfur7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczK
me+a7cFe3FHA7gX9oMeQW0CUUbbKOeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmN
Ca5NYIzSf5UvICi733d+pUDrhY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxx
yS+ddP4f5K0T5+wvwpcqfSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEp
ZY1FsjdoCeom+0SwvUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeB
fd76juYg5tP/dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD
4DnBHPaA3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7
nAPbYNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkto30a
gfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCrgtaaK3I/
qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39LmyPphLzETdArK/
+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g6my0PXoYxDpe9XvR
ETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvryOD3K8SfSpwSmxPs7/t4
rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/hwGUQPyuxY5Iv+F1QgyyT3jic
0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdfzdu/x3l/YgZXFsjRMWRtJsAvv62Q
zyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmUehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567
AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t94B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5l
r/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpHnb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM
1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0fABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuT
rREE/RxeJqcDAvSwatn7QmDTDD9ELAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34K
js/924acAv98wYMzHgKf4YHfh+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd
9l0B6miry+EPNLDN9fkFzHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLa
DyAqqweUPaBFWSLU7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSyw
y3zPpYIn0p0//kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZA
pnyh+YNrgNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdU
KuQZhJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTmZr+x
G4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc2gMc+wNq
8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHUos2WbaFAgaxZ
KnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7Y10a8CkYlc313pfg
XZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVoCKIMHxotQTRWc1IJLEnq
Ml8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0gbHKdeQoMyRf4At+IIuYo0N77
r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKmA42UL6wPQMmrxml9wZigR+AFsxUf
0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N73PXREiZEf86NiPYrtun2dqDvbO9t+MI
+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5
oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiPtHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9
HYPAG+xclLwFXKdTmiTaIHiCfxP/raDmU4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukU
Agpr27VeAHT4u4M8nXTSSSeddNJ5N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fy
J0ja4rE448F0uV7a20H4WMfDHD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZ
unnGgaOhfbX7BiT/fHmcawd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9A
rl0ZBhbYAA/tN5/eygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZV
cmjXwVbCMdP/DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG
2jFrfUdPMNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkD
nJXAW8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1jaakPA
PdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2zHbbVgos
IZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt2ggiUri9JcHd
xlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaII0aivha0VcJKELg/
cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18miY1AJvTXtDxOTjj9B7m
PgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+QYmAuENJIdom0Bs6Zxo3Ifme
UtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE7MlBOzz3IcvH5SoEbwTlgqPx6/eh
SA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwGfbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwF
tJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2vQdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYi
J+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/SG/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uor
n/EgylrzKQfBLOuNdn8JcoyR21sDjFtcNZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw
8Kw1LslvwLPdvcubB6zzNcU2GpQLSnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3
Qe/q6ZHyK6hu5bX2K5iFyC0ugN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0
fPXKuRN8WnuHG8GgzbBUtQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt
27QnIPYaXykVwPOV9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkByc
oMQ1A2t+tZzMA7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+
83jrxNk4rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZv
C2eS2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9belrLW
+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGYj7Qxtrkg
xxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kOZi1PG/dVwKG2
UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaKW1aCPty4Z9jAU8ez
1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRRE5QzYGYy7+hXwLmAFdIC
ZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POMvGA2MXd4J4MZbT4UA8GMZIUY
BpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkpd8lZ4Gnsfu2dBWYrJcrwgHWE9bTt
AehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2NbBJyFjwCQpyhx8G7pufyxUgh+pT9Spg
FvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aST
TjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7Ngki
MgdvlhGQqXCGW8piSH7pMynlNrCX5bIDKJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5w
t2eauyQUexw+uNYT6FOs5bS11yHXuOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF
9o1PWbBp6jTVBsoA5Tj3Qd4TLY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0Fdh
pcGh+qb41gXrOR+PZQTY7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIX
SBga/8Gro5BUJmFHbFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUO
zKmsk3fBXtZ+zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlw
PXdmSAiHlPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6
Dczn5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8YVnA
1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYkgKW1vbHt
KGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoBNQPSvgCW+mGT
p0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2qz/y5//t/Lvj9d/F
lsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Whb0nZEpKijXKvTYj5LPb7
V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzzdSoLIGcP/17hU0FL1AqpX4Hl
olxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3ehWpa84P7B9TppJogcMlovBfFXnoe8
6A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zPQQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P
6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyB
KXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5fNXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yW
B7/OGAG+eXz9/I6B7Ka7jY0g84veamfQtmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVn
p58WuPMUnJNcj2L3g/s9V1nnfNB3efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5Te
SpjSEERlYRHdwWxDOfEL0EyJU6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cK
aKiVtBogigpFpIAyR2uoHQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7Pcp
nrE/mI2VGWobUD6yzrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rt
hBbgPuo6l1gT3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhyb
kXYh7Hqq66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0Fr
Bq0ZtAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafkPZi1
I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/dVVocLHg
9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+zYmCba7VbY6BQ
/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2z69g+HrsKZ3A+MVV
N/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwBxjf6e/IUKM2VetbS4L5m
jHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW77ZVDBz1ZV/RPwBxknDMWgTDN
++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FEzayOQiPAf6Dvr+FfgPmDPsxZH4z3
jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2r
QE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBPs2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6
grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXlYXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf
2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv
2076tgJzjTbMkRsshe0bfKq9u0CNi4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3Q
smXLli1bQrPszbI3yw4NGzZs2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rp
abyr8a7Gu2BO8TnF5xR/8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X
7fDP6ue3y79r912779pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3S
fn9a7tNyn5aD8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/z
qzeNlz/y5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpK
SkpKggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v/0nI
9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJAAGihHeK
WhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0UOBIta7RwsOfR
/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeDtOnVvNPB2Kt/7bkG
Wjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNKguOc766g8WAbbf/eLwos
kbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+61fIleGaaK9VmYGnqkxBYAqy/
+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u8SW/hLCkLPNyR0LIjvCh2QMgZGv4
sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6foVLWK+Do4bcsXAP/+yF5s62G0DZZRxRe
CqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DUVsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2
j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTWBKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5
Gxi9PB7neFAKyIJmHRDzucVs4KYw5UfgKebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+
4jz45LBYZNS7C9TJ+yfvn7wfwh6HPQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOf
lPqk1Cel0oYsl15ZemXpFZh7du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF
5WHFyhUrV6x8d3pJpezFshfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7
SO0haYnOuiHrhqwbAm2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3fu
nJYIfvTRRx999BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym
/UyNnxo/NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue
7Xi24xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k1QhI
mSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv5XFQchCu
xoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78CaHVjfkjpDbKe
e63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzOtRa0Btply2VQY+Ql
mRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauPtLVg7W/v6jcXxCD1pqUI
qIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5YQwH8R6POQjGfX23uARKqLW9
zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1+KutAK9ntvMyeGd4XiR/BpwxJshP
QfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcrgAzgidIe9PpmG4qA0Vz3cXcFW0HrM6Uo
cM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYy
HNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCo
ZgG5DZgkXeIqiMqq1/4tiEuWamY38PWqjfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmt
rFZWp63v3LZz285t4cOPP/z4w4/hp3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDo
Rje6/etOMKkXWEuoJdQSCt563nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8Qc
E6Hqzqo7q+6E1RlXZ1ydERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Z
b5k0/SyusLjC4gpvb8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEH
bGMb2/jrNMrcKHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou
67iswB3ucAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa
82vPrz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvhYq3b
Z17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVKa3FJ+wzk
FHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+OTpAtMdvsrGPh
nPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAXcqkBiB0UUh6Dplm+
s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXpy10aaAlqe2Ul6C/MSPM8
WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOcva19CMhoqYrOgFUGmH3A1ds7
03kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtzzDCIa5b4fnJW4LnxUi4H7aIWYz0I
SoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9
zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVNL8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAn
uGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic
72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKy
FGh7tb3a3t+vF+fFeXEezCfmE/MJDDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+s
vy63ZYlliWXJm283s+jMojOLgredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9
+fXl15dDl2JdinUpBp/7fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5T
h+wf9HzQ80FPqFihYoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jRe
aE972r99P6lTA9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoV
K4jJYrKY/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2N
VxDwje/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQhxA9
8FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui+Ly05rWV
hcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXsq/0Ogdgssmpf
gTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz1NRzgG2pVkWrB+rX
VqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7bPvWrzlY6lg0bQtoxdXb
1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7UkqAky0psL5ADrCdUETw33JiMX
OH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2BfWu+qPlfZDzlfFyKzicjoP2xiDm
ynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4JyooBsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5
GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcboSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8U
ZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVL
lyyFKturbK+yHY7PPD7z+EzYennr5a2XIcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyB
mJiYmJgYuNvzbs+7PYFlLGPZH8uX+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E
3Ii5EQOzi88uPrs4JHdO7pzcGQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+
rT6rHat2rNqxtO6md5reaXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaH
bQ6DUudKnSv1BpXEVN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7v
Wq9ZxmYZm2UsTGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P5
38VbJ84+twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniG
ewKh8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIzW4Os
K8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG9N3eSE89
MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxXAs8+d0XnPVAf
KTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1QajWML8R4PPcZ4Al
AFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYjsERbTM0Aa1fyi2aQNDRx
XPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQnjtofuBN8PfYuir5wbJFW6kU
AREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5BpT+ahl1KhhFZVvzInh/9YxzDwTK
skXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjFYKzXW+sPwZbfOkULBLWlGGoZDXo1Y455
AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeberGhh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMq
k0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFC
Rwsdhenzp8+fPh8GMIABQMdCHQt1LATd5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT
8E3DNw0HhjOc4b9fn/o6qVvTb02/NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN
7fi2+mybv23+tvkhpkNMh5gOsD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+
1H9S/0n9JxCSMyRnSE6YcnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq
1KlTp04dUMup5dRy/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP
+DN/fVP+3f6dzv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4s
LbSrzcqeoNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+z
j3SD4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5XtkO
7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQfbtQ49MYu
J3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6geBQtwV+ACZp
Vn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0WrpwBYwnJWXy8XA8LMp
xJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALeFo6DZtITtH0gf21cYdFA
/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TNUr4tBOSXjJuMpUGP1qoHJoAw
Wxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALKWbWJlAmWry17jCYIG2aNNPQCYVEg
3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsD
dcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ec
Ow60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5
DIx4+73j7134u4d5UNB/poJa1X+1RvU/VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/l
f9rrGhT0n+DIkSNHjhx5DDPOpAph4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0G
L8+Obln3AHSsWuP797tA7vmcVFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj
4TUQRupZ+kLQGgjT5MXAVD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19l
f/R10D/mKXE3xN4oVqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNq
yxMWBaQk6aK0BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUH
JgNoZ/ReWhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzE
AeJo8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfAXT5V
L4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1ang/SupirD
QTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3wjeElkD7wDfA1
g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKsgyyd5H2ghQnLzZNB
/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysOrDiwIqyqt6reqnpQI6ZG
TI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZNBNMFLTXzLHRxRn9d5wS039bu
2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuDGqIvzO4Ckl08EuYGNnFZuAz6Df2u
OA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7o
sCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsRAs/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0
n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxX
rG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLeEK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10b
A0J37XbgI4h6NiTGlgjey55vPN9CvphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsM
fO18G90DQWppaGR8FhyV7d0tZ0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuA
cEv40fQiMJHzgh+sP1m3GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7
hOc+ZD3r7JhTHUyTDDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhc
QlggAgKTNIvwDuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPie
HAXma+ahoQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZ
odLLlV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuCOFWf
Li8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ3WU1CPvK
UC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5O8DV2vm9OwnC
cqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPlZfktW3kwP2FND8QA
RdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinfgDhNdwr7wVBNjrP4QI+X
OmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNXk6uC2NfwrHEDyHZDFVMMmOym
GcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8m2vKZTD0ML8p3QY668dMGvgmKoP8
44EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE26qDwWCYLntM+8CwyYh1EHgG+HsErBBo
o1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegfa98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+
F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVibTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF
8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3DeoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/F
vBfzHixlKUv/0QV1qcu/URL5r/qf9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577Vc
iJ9VOrNWFLgPCOPFuyCW9SxznYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2
Bj2ZD6UBIHzGEf87wAgxTk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6P
AO2g8r7rU5AOWxaZi0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8S
NxyML5qnhrwGOV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO
9Bh1sBIC3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqeh
sh3EtfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3fS/cg
LM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0wdxbtnAOv
xZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0JYWmOKNP7EO61
lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWFpeJZyDqUEcjZC2E7
QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFBj8efTpzvN3EOMLaH8Mz4
fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7emlnAJLWBfyqIy8SexpGg6srB
rJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8eNnRbDjx6umembugd0afeS89CyGz
m2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/MtgulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3
ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+sU023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8Q
Ks4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFDQS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlri
aPBleW+4h4A+0Rcv2MC/hQqm78H6uvVoaFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3Bf
AENV+TPPJtBDAzGeWJBek3poT4LdYR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73Vw
vZa/L30PRO6KjLV+D+ZmhkzxfciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUH
qC39zfJvgulJ613DaMitkfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8J
xqetqy0HwVfVH+lNANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA
4LetE3dAYKnaV28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i
+buHd1BQUFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+
Fb4UNwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO96Wd
IF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuHrXhlsNQJ
GRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B3aF86YsEb+Wc
vRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJA+ublnXmIuDPd77p
nAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DYJRXVuwK7qeM3gatc/iKl
C6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP17sl6/gsgYRgmx4H/vNZWKwf+
K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyoNADdhlGPAfmEcYI8B/Qs0jCB+oM6
S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/
5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEB
iEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoKCgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVB
U6yRYkfwt83skt0QxK/Nm0xRICq8rySBOk8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzP
xYfomyC/c94mXxEI1cIuh80GTzP/D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILY
Kqa0+TMwfBweEvMscNM2MawC+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeT
Cs4r6UVudwZPMU+7+M1gNlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/
PVC/VndKFhCXaFOkNuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0F
MV6YbNwJHBNKe78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQ
RweG+p6FwFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4j
UCQq5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQiwxm
zZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+qAkIttbGy
CDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCgoKCgx0n8sw1I
t/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3QKmQH5v/IqTXPn3w
2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZJeNOiMuIbRPyOvgauMq6
3gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVbZdD3SPsNkSDk+j92doDS5uIZ
xfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GNlaqaJoHniDDU9i5cnJ/0UfZYyBvm
i9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus9OS24H7LfTd3Kahn/a+5zoD5PVNAagzW
osa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsG
lnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTsdgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqm
gnLGv8h1CHy9PG/53gXfi/7VzgiwbpOyNQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+Ipe
CbQ0mkp2EMeq4WoEGMoLHcT5EPVqqCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhK
GV6V5oPQRUokDPy5gZvql+C/6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX
/S3BleVp7twBvhxa6X6QQo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcT
X4h0g+mc1l8s+ncP76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1C
fA1+nLn/wvqnoUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht
9fqWi2DYb3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSI
O5NgAOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O+nwt
RKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dAQQSxtt5e
HQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUKtNX7Q86p7Lys
geAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhTcLt/xorMNyC7t2u+
9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3cc712MC6XIqUfIO6bsBrm
iSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJZRIpDr523mm+KSAtFyaLyZDT
My/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+CJSril/7HJRx+hYFENfrMw0/QbHo
sDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSKX/peaQHVeXonB//uYR4UFBQUFBT0OPzp
GecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3I
CpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8X
vHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZqr4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupT
yJ+hJ+uh4J6cNStjARQLjdgpVgbDFsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN
+BHyxuodZAfkeIRo8wzwfK6MF/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6Pt
oVAsKeZa+HtgDGiLfRpIAfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+s
fgW2btapjtLgnuBq4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqW
TmuLoFj96JVRaXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBl
cdaS8sG/MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7
i6t1bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUyl8p+
AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57zffZz4NLu
WVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKgpeT/5HkWxPIR
7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8fDsIm9wB5EpAC0k4w
rk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6Hql9VeAnsXfXFMSvgl1Xe
TUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRxxqvRVSHvSb2++h0o7/gauVqD
4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFPOwQljsTPihwCruM+QVkKnin5y3Na
QpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXPdPdV53JwpnhSc7eB97hnuccL5u2mU6ZQ
YLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9YjXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0
GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGlKZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJH
Ka1AT1I3+G+DVo3njN0gp4k6NJAMmujtqqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZk
gRwupqgXwZFm+UQ8A3quPlhPBONGeY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD
1KUyB8qvB0+2ppv6QXR6fKmYlhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKl
SwuP9+nTp0+fPhAWFhYWFvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQ
flI1+Zn+kFik2pannwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6Y
XQd4EPFNQjXQr4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814E
x5l7qy/PAO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBq
Tr3B3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/ntnbnu
+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nahH4N3rK+J
ZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhNm01lgTlK3Yzy
cL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU8Lv8FfQXIWNM7j3n
p+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/ISVMsmMrJS9Qs8Lf11xN3
gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0ivmPYaF0NeD+cB7yhwnDJvMayG
hPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfIfcIEp2vcbn5L//sGduPGjRs3blyY
QBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzLL3D16u3b2dl/Xbxy5UqUCA+Ht97q379+
fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xPRITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3L
zMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2iKP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR
5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDv
sEWGjwNNU+3C26D3Er6jDQjzuCjEgFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5
/MoV6DFWyroTDilbKuj3P4KE6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh
3YRjvAVdarWMu9wRbg9e1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L
7QgI7cQD7ALhF8Mc0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEde
U8gemnEv5Qdgvvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUB
JV3MMMeDO8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQ
mZtR/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0EWm9K
0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8GkpWKuYs
q0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRrf90Hw6Ps3bt3
7969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2QWZmXl4gAGXLli4d
FQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRNEODpp4sVi4j4tT+P83n/
2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs83t6A/n8mq+7f93h8vsK4bdvG
xEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQiml3hVRQV8nbmQDCE2JrfSxIcYQY
NoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgYTHpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A7
6qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/
EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmnIHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w
24dObIH80dn709tByJ3IiJgtYGxoMfvrQsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0
V1yoXQBDSeNdxxG4fytvkh4Lvi6ub30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzI
c7l/0i3gK6029JlBLikvFdLBW0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9
yS3vAfCleBZkpYJ6mhm6FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDq
pU3wdwVHTfsFy0nwNgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGO
wbve7wJhgfyytTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+Q
VoVfg9zN/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1
O9jQfkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4uLAwO
Hbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c/nTinPzG
dePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdBv6xf8DUBsZQY
JX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdAC8EhW4GvhK8CZUGt
4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSulz4O98InjrZufLIPbpjRD
4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5NnQrpN+Pyi12BLyH0rsmxYL3
nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q2s34klgazHuksEAUXG+b9FLOafB1
0vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qwtwd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZ
uAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJeALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3
GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoP
IKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXPdTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCN
UXcI3UDtpx8Tb4G8XtIDdcDU39xQ9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHW
WGxF8RGgFxU+sgTAfljsYTwDJd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAF
PPPXfTj8IwW1y0uWLFmyZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L
9dtSO7s9LCwurjBOQdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1
HTIyFOUfnd+1a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE
6JDXHuRvBUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpID
oEUKL4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DMGahe
/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dpamlw93a3
8r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD3mzPGFdpkB4Y
LcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH+jVEVQqpEdISzCfF
COUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+bcpsfxjkf5P7TH4iJB9J
WZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/cn9peHAs81amFQyfS5H+3WB/
wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggLQSrNp7oMxhjjbnk82CvYo02twFbe
vNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubsEpnXQNmlfOf5EaK/jnreuhzi9xWvn3AT
xG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDrsWNRcPTna19d6grp+/P2pXUGZ72srintwD/K
MyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vuu7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrH
Kscqxx9/3wq2V0ddHXV11N/d+0JTMqdkTsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Ze
m3tt/u5n95/77yfo/6aqiqKqoKqqqmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z
+f3g9wcCilK4PXjwo4/eeqtw+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j
24K4j9ufnnGW65axxswAc0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE
8bDQ07ACpN32mJhloL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/Szo
GawVe4H4o6hZDoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4
//EPXU8NhLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbz
lfxvlL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U+prF
cg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBuXzVC6pm0
gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175/OF50XA+5dZ7
rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXzYhBWCvNNJ0DZL16W
loG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9vU1rwNDJ3N34BBSZFr4+
bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98pQbsTzze7szzkN6ITYEfQVtg
nB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmCmrtGjRo1atSosNb5cYlsGdkysiW8
/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af
2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3L
ti7bukB/+tP/736SQf/xFKUgkS1I2f4906aNGNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf
3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUVBQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3
ZNlicTh+v/+o6/+ogriP259OnLOs9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4
RIoB7XOttdYPpNZFR5ZbAuIh62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt
/SPBAPo1Suo24IFu1L8HvRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJH
zTth7dklWVvjoHTHSmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D
5EVy8pVP4EGCfVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfa
aTC0loeJ30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+
2T0S/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F7kU2
i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpcuvMx2OOZ
pnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V4Pb41FYPhkG5
F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2vg+OvnEq43R1SLms
V9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHixIkTJxaeHz9+/Pjx46FE
iRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUNGzZs2LABMjIyMjIyICoqKioq
Cjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn5u6su7Puzjo4fvz48ePHC8MXPC4u
Li4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQoVZWqSlWYkTsjd0YubC66uejmolCmTJky
ZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0WdpkaZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w
++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFr
xq4Zf/z9ubHmxpoba2B66emlp5eG8+fPnz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe
8LThacPTHl3b/7DNaZvTNqdB+U/Kf1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiS
viV9Szo4nU6n0wk1F9RcUHMBTJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5
oeeHnoc2MW1i2sQ8vnH1qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z
+32+gpng385IV6kyePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv
1i3Iy7Nao6LAaHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvt
zYgPx33c/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsC
aMNyW6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4flL7
luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5EhblTw7RI61
fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUzJhVi46JioidB
pDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5H4S+YCirTAebTfrc
uxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjteBUNwk6b+pcKAWsTw21L
f+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc3Ku9SfnNoHRqzPHi88H2vpwW
vh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fgbZV/PmAHxyaLKo4BY2v9Y6UEZFRJ
eeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHuobzz7uJQ8UTF80USoGTXMkLJb8F0yNQn
VAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyf
O++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJEyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6
ggTmUV/1bym6peiWorD80vJLyy8VfsVebm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPU
D6Hr1K5Tu06FnF05u3J2wcw9M/fM3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oeP
jpO7O3d37m7IL5dfLr/cv9+P5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlh
zwx7Zti/3s7U7VO3T90OJwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8p
flP8Jni35bst3235z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/
vjJ8ZfjKAN84vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7T
uHpc7+v/Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1
K9z26VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QIqUAa
Jr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqIAN1NSQRA
QgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID6U2mQ8rqrBrp
D0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4cfXutrvWws6O+7PO
bgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ9lsOOHqCb2vWK2nnwD/c
ednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn5mG3COlfZg9xfQkPWmdsy/kG
zCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1LFjPmd4wxoM/RnmdhuAdpt7KTYVc
MbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdztAiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJI
H5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODIjtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLn
GTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGTbWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuF
zYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0Ct
ZxhpOAN003xCd2Ct0FyoA9Jz4alF40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbD
tc4F7RS0WxDnX22/IIFZu3bt2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03
dt3Y38zgPnz9n1WkQ5EORToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJv
ht8Mv/nX9+Phkpqh5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9
G+VJBc+7wMxZM2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n
8bZO2Tpl629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW
5BosPrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpUq/b7
9gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6tlYehHhu
6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0eJm8GVoi9dS8I
n+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKmhSC1NW3Q1oHwjCzK
rUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgocRqFRycYQ5S3hVn6ECE/E
iLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCkR5ioNof1T2iVyYMTNkPd0oNB
25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e2jZwp+SNTs+BQKQvJL8j2GuY20iv
QWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC
6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNBnyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/
Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtOCdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVf
BHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3uaBsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH
+VNQ5G7Rj0sdgbDXw0fGLwV/28BUqTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR
7jmyR6QOAm2GMTJ0GDBffVl4E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxa
sXHjxo0bNxbOCP/R9ZgLapsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQ
Tgonhd98Na4N0AZoA37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAE
JzgBdKMb3f746/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E
/6PvzweJHyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16Qm
NWHzzM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBbt1q1
ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/YGWfzcVcD
uTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNAHCItQgHKaudZ
CPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGmHiRt9E0yFoUrSzLH
6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWET8WODAblTTXTuwwC9QNL
vSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2WdcZDvIyhpid4dEQPlo8rVDzkF
1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3MseRJwRavJNAg9Ffpz5BiIHZfoK5EL
ifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30NqfvTOuZch3M7L5dL+xByt3pD/CvA1tfe
OiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUUy486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSA
MgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEH
QBVxWatD1IionxzfwJPnypVNOA+h4baPQgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/i
Cyjbo3hGORkqHKpYv1YLsCeFfJf4M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvn
T7x46hSkHsrqd/MoqBHmapZU0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtN
lb2Pb6AWJLDFixcv/tsPkoL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDC
gQowadKkSb+txWvRvEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyX
Zr80+yVYKCwUFgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYR
thG2whrnGsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPt
wvYf/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86vnfv
tWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3+fm/rtf8
6FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG6ufg/NwbuZn9
ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08tSkLzledeTk3YO2s
dec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf4CVqC59D4Cn/Lf08iH6p
HTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5Kr5v3wglXzctPDsHskqHp+aM
BvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7NE6/a34Z7FczNS9wD7Xbe7rQx4Oua
2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAsoXf0tIG1nTrQwAFzFPBfVXHDN0p837AYx
Ri6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwno
s4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKl
Y2IrBCB0onQg/mWwbQibhQ+Uyq4zTglSRiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+
okHIfLCPdxjCVoH5A/tsSyXw5ftKCXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQ
vu72gOsmyGueq90pAx6MhvBPQR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTx
LeAZ2ujV/88g6fT4BmxB7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gN
ozaMglEZozJGZUD0neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej
70bfhTTSSHsM/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1A
faA+UIcHox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWI
eqTwZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/HX/h
zY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2h1Ue3n/U
4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv/uST/2iCpyDu
4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFfjPsFjw9sxvB5EYtB
vaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75KfQWE3oYnDeXhZon7SRdW
QPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5GSo8iN9gSAJrd2tRDoJaQW0t
PgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36sBUBviiAkgHhQF5V3wF/TWTGvMxiT
De3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W
3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXRlqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMv
g7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y
/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfE
KEsVuB2ecfv+cTDUk3da+kDUujA1thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8s
r7Tehpjc+E02BSJaRRaPygTDEPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW
0n4y7AJnVEpOSjfwrcwedC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDo
E+gZaAeBQ8pq31lQZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F
4cOHDx8+/K9PnIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OV
Ks8+O2MGVK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0D
k6lYsfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GOHDly
5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH546Dtj1g
XGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c97jmkLnAXcc9
BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5jGHBSb6VfBHGysEj0
g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bIKND8asdAKOidDTPU1aAs
slRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbUmOM9Bm+crfnuhW/hl+X7Lp36
ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTCd4TdjmgIYWdDy9ltYGkdeceSD3p9
fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW
9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIW
MC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN62
0z4BAobAKmk4uCbm/uh7EvI3+C4HngXJbM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSs
u1/10kYIxOvN8uaD9rH+tvAe5JdwV9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/
RmBEIBL0idp2dTrop9X+gfqgBgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7
wV8U/M9UsOzcnpV7Vu5ZCQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6
j9Y5/lf5/f+4Ztjnc7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3a
z+xst1tRIDTUYpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTC
uI/bn06clamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcM
y83dDG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArCFLGD
2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx03IyrCYbz
9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG78Kz5Sr0e7of
lJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5W80TIfRLR35UNIQk
hawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QXy4CS6NX0LSB/Uiq/WBfI
65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9FmwY3gmYSqkzTS2TX4ZQvbYD9km
Q9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1ls/01CPi1ndJT4C8aMBEDOTnpC7zP
QeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfkNr59Mn0TuDpmpST1BeW8sij9I7B1t3+p
fQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2gVNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8a
tBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLph5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9
AstYxjKAoQxl6J9tNSgo6HF44onSpSMi4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHi
ERFw9uydO5mZIIqhoSEhEBY2ZMgXX/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/
+tPcfj8kJPxaQBEWZrFIEmRliaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9H
VSE5OTfX7y+M+7j96VKNB40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/Te
HkdCIG+O/pVcDYpcbVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9
IEGNXFcpF852veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4
Wd+mrwJ9mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqE
W0zOSu9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQL3tm
590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkzgL+M+pHi
Bf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21IIDJbXrPuA+0
zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBMYHsgA9QG0mLhTZBi
jMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmXu0FufprHPxPUE2wJ/AJy
nNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+HhBoIpwGPUH4WVwFvC9uk74A
XdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+QlZWT43RC375vv/3113Dx4rVraY/j
JotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnPPTd27KJFcPr0tWv/aJ3ox6V69bJl4+Ph
xx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t15vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8
wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9bbn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgTh
JCRMNr5cdBBkD3FXzbPDqYyT2qFZYClnNIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQej
hO/vdwN3hLQhcAu2n9hz8btL4Ovqp8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl
8oE/AeSFNDCfA3edPF/WQLi69lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2A
RXzN4AF9pYjWGJgibBVDQIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8
ufk6iJsymt8E5AnaPPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuy
ZmRdhhxnVn25E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ
/QQAmaZaMgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgo
qVwC9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+UvVoR7
i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0q/p9zQDa
Sf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp999o9v4vt/zZ9O
nC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AUTB/HRIZUB8MKZsib
IfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZMze+TBNBPBvyWuJC0Bdn
rksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294HAmsCy31TQN5hirA8A+pRbaM3
GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itFxK0G+xVXpKUD3EjdundNHNjnlUmr
3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8YJXQm2zQF+kX0UFIYgzHQaylRwulwdBY
T1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtAjrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRp
zoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73nJIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi
6LvFfvQD/RVhseACoTFLhATQv+BHcS3oU4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTac
MBwG+XRIo7A7YJlhmWH7CcwO4zrzYYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT
+mx2Q+N3Grq7TwBnEWegyTsQ0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPH
hWHwnXvFnU13wf9ufs4FDyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1Hjt
HGiDlZP6pwCUp8nfPcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+
Fffibt4CuXvUK+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrW
M2YK6B3lm4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymA
b6zrmfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/OA54Q
hodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDgPereCUJe
7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7MeM3VGzI/dZcM
TIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6znAzJBjBGHiU+BGGV4
3/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGqNZAO2oyMxik1oGnxZzuX
bgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDbYogaI1e05IM+jmrmJZBYrOj+
5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0QPzcso9grkHTYvUN/EXZe2PbJfhck
z8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgRhiflX5fPCc45BwUFBQUF/Q/xp2ucg4KC
goKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0EwcQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAf
EEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDA
j4oAAAAASUVORK5CYII=
--089e015387dc9ab4dc04df0a6f13--

From Michael.Jones@microsoft.com  Thu Jun 13 08:05:55 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E476621F99C5 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QSmPtHk7NvB for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:05:50 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEB421F91B7 for <jose@ietf.org>; Thu, 13 Jun 2013 08:05:48 -0700 (PDT)
Received: from BL2FFO11FD012.protection.gbl (10.173.161.204) by BL2FFO11HUB025.protection.gbl (10.173.161.49) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 13 Jun 2013 15:05:47 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD012.mail.protection.outlook.com (10.173.161.18) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 13 Jun 2013 15:05:44 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Thu, 13 Jun 2013 15:05:35 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, Justin Richer <jricher@mitre.org>
Thread-Topic: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
Thread-Index: AQHOaERPQN1nrUcLW0m4t99Xt6j0/pkzu3uAgAACXYCAAABmgA==
Date: Thu, 13 Jun 2013 15:05:34 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436784A7BA@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <51B9DA50.1080807@aol.com> <51B9DD51.5040000@mitre.org> <CAL02cgT=m=wvqADRmSku+UphFJayNawWWcYYXZRPisA+YL8iUg@mail.gmail.com>
In-Reply-To: <CAL02cgT=m=wvqADRmSku+UphFJayNawWWcYYXZRPisA+YL8iUg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.35]
Content-Type: multipart/related; boundary="_004_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_"; type="multipart/alternative"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(52044002)(377454002)(199002)(479174002)(189002)(22974005)(24454002)(164054003)(52314003)(51444003)(51704005)(47736001)(15202345002)(77982001)(74662001)(31966008)(55846006)(6806003)(33656001)(512954002)(47976001)(47446002)(44976003)(51856001)(74366001)(67866001)(74502001)(15395725003)(81342001)(49866001)(4396001)(77096001)(56816003)(76482001)(54356001)(79102001)(76796001)(74876001)(16406001)(54316002)(56776001)(81542001)(71186001)(20776003)(50986001)(16236675002)(46102001)(59766001)(74706001)(17760045001)(63696002)(53806001)(66066001)(65816001)(80022001)(76786001)(69226001)(66926002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB025; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0876988AF0
Cc: "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 15:05:56 -0000

--_004_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_
Content-Type: multipart/alternative;
	boundary="_000_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_"

--_000_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

To be clear, I don't think anyone brought the JOSE specs to the IETF expect=
ing no changes or engineering to occur.  And in fact, there have been thous=
ands of improvements made since individual submission drafts - and in the c=
ase of JWE, some of these were breaking changes.  No one was or is trying t=
o circumvent the IETF process.

But what I hear people saying now is that the specs are at a sufficient lev=
el of maturity that we should no longer be making breaking changes without =
a compelling reason to do so and that the industry would be well served by =
completing the RFCs in a timely fashion.  I agree with that position.

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Thursday, June 13, 2013 8:04 AM
To: Justin Richer
Cc: Mike Jones; jose-chairs@tools.ietf.org; <jose@ietf.org>; George Fletche=
r
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of=
 binary encoding (base64))

I have no problem with the authors developing the -00 versions of JW* as In=
formational.  But then the Standards Track documents that this group is dev=
eloping would be free to break with legacy (cleanly).

This group should have done what OAuth did.  Publish "v1.1" as an Informati=
onal, AD-sponsored draft, then work on a Standards Track "v2".  Instead, it=
 seems that some of us have been under the impression we were working on "v=
2" while others thought "v1.1".  Which, in retrospect, seems to have been t=
he origin of a lot of the angst here.

If we go back and publish a cleaned up version of -00 as "v1.1", would anyo=
ne here stick around to work on "v2.0"?  I would.


On Thu, Jun 13, 2013 at 10:55 AM, Justin Richer <jricher@mitre.org<mailto:j=
richer@mitre.org>> wrote:
+1 to George's suggestion. We know that what we have today will function, a=
nd if this WG doesn't finish its job then the reality is that everyone doin=
g "legacy" JWS isn't much going to care what the JOSE WG says anymore. In o=
ther words, there's enough momentum behind the current state of JOSE that i=
t would cause a serious fork if we were to change things now.

So let's be smart about the fork. Let's push what we have as "JOSE", then "=
JOSE2" can turn it into the multi-encoded-binary-framework that fits other =
use cases. And it'll be JOSE2's job to come up with reasonable backwards co=
mpatibility or incompatibility rules and functions. If we do this, which is=
 what George is saying, then we can actually have some control over both co=
mpliance to the "current" specs and compliance to the "new" as-of-yet-undef=
ined specs, and we stand a chance of people outside of this working group a=
ctually paying attention to what the working group is saying, both with the=
 current and with the new.

And finally, as the proverb says, "don't let the perfect stand in the way o=
f the good."

 -- Justin

On 06/13/2013 10:42 AM, George Fletcher wrote:
I think that in the current situation the issue isn't just breaking deploye=
d code but also the timeliness of completing the spec. If the desire is to =
change the processing at some point in the future, why not complete this se=
t of specs and then look to add the backward compatibility/migration strate=
gy to an updated/future version of the specification? That's effectively wh=
at this would be anyway, and allowing other specifications and working code=
 to be compliant with the current specification is very valuable and doesn'=
t preclude revising the mechanism in the future.

Thanks,
George
On 6/13/13 10:35 AM, Richard Barnes wrote:
This would have been a nice discussion to have had 18 months ago, when we w=
ere getting started.

I don't think it's compatible with the IETF ethos to say "Changes to this d=
ocument MUST NOT break existing code."  Otherwise, we're not doing engineer=
ing here, we're cleaning up documentation and rubber-stamping.

What would be acceptable is to say "Changes must break cleanly with existin=
g code".  That is, it should be possible for a JWT implementation to, say, =
process both "legacy" JWS syntax and whatever comes out of this group.  Tha=
t way, we could come to consensus on the best solution, incorporating lesso=
ns learned from earlier work without being hindered by them.

Would participants here consider it a acceptable for the output of this wor=
king group to be incompatible with existing JWT implementations, as long as=
 it had the property that JW* objects in the new format could be clearly di=
stinguished from "legacy" JW* objects, so that implementations could adapt =
their processing?

--Richard



On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com<mailto:=
gffletch@aol.com>> wrote:
+1

Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.

Thanks,
George
On 6/13/13 10:19 AM, Mike Jones wrote:
Jim and Karen, could you please do as Richard suggests and close this issue=
 as "won't fix".

                                                            Thank you,
                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Wednesday, June 12, 2013 1:57 PM
To: jose-chairs@tools.ietf.org<mailto:jose-chairs@tools.ietf.org>; Mike Jon=
es
Subject: Fwd: [jose] #23: Make crypto independent of binary encoding (base6=
4)

In other words: Chairs, feel free to close/wontfix :)

---------- Forwarded message ----------
From: Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
Date: Wed, Jun 12, 2013 at 4:55 PM
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)
To: "Matt Miller (mamille2)" <mamille2@cisco.com<mailto:mamille2@cisco.com>=
>
Cc: jose issue tracker <trac+jose@trac.tools.ietf.org<mailto:trac%2Bjose@tr=
ac.tools.ietf.org>>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org<m=
ailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>" <draft-ietf-jos=
e-json-web-encryption@tools.ietf.org<mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org>>, "<michael.jones@microsoft.com<mailto:michael.jones@m=
icrosoft.com>>" <michael.jones@microsoft.com<mailto:michael.jones@microsoft=
.com>>, "<jose@ietf.org<mailto:jose@ietf.org>>" <jose@ietf.org<mailto:jose@=
ietf.org>>
To be clear, I structured my message in two parts for a reason, to separate=
 the analysis from the opinion.  I acknowledge that I am but one voice here=
, and I'm increasingly hearing how alone I am :)

On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor c=
ode.  But I think we're literally talking about something like a 5-line pat=
ch.  And early JWT implementors knew or should have known (to use a DC phra=
se) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part i=
n the discussions are likely to find the specification changing out from un=
der them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE=
 in place of CMS one day, without the base64 hit.  We should incur the impl=
ementation pain now, and get the design right for the long run.  Base64 is =
a hack around JSON; we should build the system so that when we no longer ne=
ed that hack, it can go away.
</personal-opinion>

--Richard



On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m<mailto:mamille2@cisco.com>> wrote:
I did at first find it curious why the cryptographic operations were over t=
he base64url-enccoded values, but I was also very focused on JWE, where I t=
hink the field separation problem is less of an issue (at least now).  For =
JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload.  I do find it int=
eresting if JOSE could more easily and efficiently support other encodings.=
  However, I think that while this is an interesting thought experiment, it=
 seems we're too far down the path to seriously consider it unless the curr=
ent state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ietf.=
org<mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com<mailto:michael.jones@microsoft.co=
m>):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
> -------------------------+-----------------------------------------------=
--
> Reporter:  rlb@ipv.sx<mailto:rlb@ipv.sx>   |       Owner:  draft-ietf-jos=
e-json-web-
>     Type:  defect       |  encryption@tools.ietf.org<mailto:encryption@to=
ols.ietf.org>
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> -------------------------+-----------------------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org<mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose





_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose

--
[George Fletcher]<http://connect.me/gffletch>


--
[George              Fletcher]<http://connect.me/gffletch>


_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">To be clear, I don&#8217;=
t think anyone brought the JOSE specs to the IETF expecting no changes or e=
ngineering to occur.&nbsp; And in fact, there have been thousands of
 improvements made since individual submission drafts &#8211; and in the ca=
se of JWE, some of these were breaking changes.&nbsp; No one was or is tryi=
ng to circumvent the IETF process.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">But what I hear people sa=
ying now is that the specs are at a sufficient level of maturity that we sh=
ould no longer be making breaking changes without a compelling
 reason to do so and that the industry would be well served by completing t=
he RFCs in a timely fashion.&nbsp; I agree with that position.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 13, 2013 8:04 AM<br>
<b>To:</b> Justin Richer<br>
<b>Cc:</b> Mike Jones; jose-chairs@tools.ietf.org; &lt;jose@ietf.org&gt;; G=
eorge Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I have no problem with the authors developing the -0=
0 versions of JW* as Informational. &nbsp;But then the Standards Track docu=
ments that this group is developing would be free to break with legacy (cle=
anly).<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This group should have done what OAuth did. &nbsp;Pu=
blish &quot;v1.1&quot; as an Informational, AD-sponsored draft, then work o=
n a Standards Track &quot;v2&quot;. &nbsp;Instead, it seems that some of us=
 have been under the impression we were working on &quot;v2&quot; while oth=
ers
 thought &quot;v1.1&quot;. &nbsp;Which, in retrospect, seems to have been t=
he origin of a lot of the angst here.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If we go back and publish a cleaned up version of -0=
0 as &quot;v1.1&quot;, would anyone here stick around to work on &quot;v2.0=
&quot;? &nbsp;I would.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:55 AM, Justin Richer &lt;=
<a href=3D"mailto:jricher@mitre.org" target=3D"_blank">jricher@mitre.org</a=
>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&#43;1 to George's suggestion. We know that what we =
have today will function, and if this WG doesn't finish its job then the re=
ality is that everyone doing &quot;legacy&quot; JWS isn't much going to car=
e what the JOSE WG says anymore. In other words,
 there's enough momentum behind the current state of JOSE that it would cau=
se a serious fork if we were to change things now.
<br>
<br>
So let's be smart about the fork. Let's push what we have as &quot;JOSE&quo=
t;, then &quot;JOSE2&quot; can turn it into the multi-encoded-binary-framew=
ork that fits other use cases. And it'll be JOSE2's job to come up with rea=
sonable backwards compatibility or incompatibility rules
 and functions. If we do this, which is what George is saying, then we can =
actually have some control over both compliance to the &quot;current&quot; =
specs and compliance to the &quot;new&quot; as-of-yet-undefined specs, and =
we stand a chance of people outside of this working
 group actually paying attention to what the working group is saying, both =
with the current and with the new.<br>
<br>
And finally, as the proverb says, &quot;don't let the perfect stand in the =
way of the good.&quot;<span style=3D"color:#888888"><br>
<br>
<span class=3D"hoenzb">&nbsp;-- Justin</span></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 06/13/2013 10:42 AM, George Fletcher wrote:<o:p><=
/o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">I think that in the cur=
rent situation the issue isn't just breaking deployed code but also the tim=
eliness of completing the spec. If the desire is to change
 the processing at some point in the future, why not complete this set of s=
pecs and then look to add the backward compatibility/migration strategy to =
an updated/future version of the specification? That's effectively what thi=
s would be anyway, and allowing
 other specifications and working code to be compliant with the current spe=
cification is very valuable and doesn't preclude revising the mechanism in =
the future.<br>
<br>
Thanks,<br>
George</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:35 AM, Richard Barnes wrote:<o:p></o:p=
></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't think it's compatible with the IETF ethos to=
 say &quot;Changes to this document MUST NOT break existing code.&quot; &nb=
sp;Otherwise, we're not doing engineering here, we're cleaning up documenta=
tion and rubber-stamping.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. &nbsp;That is, it should be possi=
ble for a JWT implementation to, say, process both &quot;legacy&quot; JWS s=
yntax and whatever comes out of this group. &nbsp;That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&#43;1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span><o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:<o:p></o:p></p=
>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Jim and Karen, could you please do as R=
ichard suggests and close this issue as &#8220;won&#8217;t fix&#8221;.</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Thank you,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [<a hre=
f=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">In other words: Chairs, feel free to close/wontfix :)<o:p></o:p></=
p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">---------- Forwarded message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac&#43;jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<=
a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=
=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot=
;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">To be clear, I structured my message in two parts for a reason, to=
 separate the analysis from the opinion. &nbsp;I acknowledge that I am but =
one voice here, and I'm increasingly hearing
 how alone I am :)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;<a href=3D"mai=
lto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o:p></o:p></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;impartial-analysis&gt;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">So just to be clear on the trade-off the WG has to make:<o:p></o:p=
></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On the one hand: Breaking every existing JWT implementation in the=
 world<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On the other hand: Eternally binding ourselves to base64 encoding,=
 even if binary-safe encodings become available (CBOR, MsgPack, etc.)<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/impartial-analysis&nbsp;&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I have some sympathy with JWT implementors. &nbsp;It sucks to have=
 to refactor code. &nbsp;But I think we're literally talking about somethin=
g like a 5-line patch. &nbsp;And early JWT implementors
 knew or should have known (to use a DC phrase) that they were dealing with=
 a draft spec. &nbsp;As the W3C editor's draft template says, in big bold r=
ed print, &quot;Implementors who are not taking part in the discussions are=
 likely to find the specification changing
 out from under them in incompatible ways.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">As PHB pointed out in the other thread, it would be nice to use JW=
S and JWE in place of CMS one day, without the base64 hit. &nbsp;We should =
incur the implementation pain now, and get
 the design right for the long run. &nbsp;Base64 is a hack around JSON; we =
should build the system so that when we no longer need that hack, it can go=
 away.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">--Richard</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) &lt;<a hr=
ef=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I did at first find it curious why the cryptographic operations we=
re over the base64url-enccoded values, but I was also very focused on JWE, =
where I think the field separation problem
 is less of an issue (at least now). &nbsp;For JWS, this would certainly ca=
use problems without some manner of unambiguous field parameterization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. &nbsp;I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. &nbsp;However, I think that while this
 is an interesting thought experiment, it seems we're too far down the path=
 to seriously consider it unless the current state were shown to be horribl=
y broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac&#43;jose@trac.tools.ietf=
.org</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact Seriali=
zation,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, com=
puting<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling reaso=
n to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that'=
s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually &quot;e=
xtra&quot; at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly the=
 same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ip=
v.sx</a> &nbsp; | &nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-we=
b-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a href=
=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ie=
tf.org</a><br>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp=
;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &n=
bsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;Res=
olution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&gt; _______________________________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>jose mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><o=
:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" target=3D"_blank" title=3D"View full=
 card on Connect.Me"><span style=3D"text-decoration:none"><img border=3D"0"=
 width=3D"359" height=3D"113" id=3D"_x0000_i1025" src=3D"cid:image001.png@0=
1CE680C.C6F93480" alt=3D"George Fletcher"></span></a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">-- <br>
<a href=3D"http://connect.me/gffletch" target=3D"_blank" title=3D"View full=
 card on Connect.Me"><span style=3D"text-decoration:none"><img border=3D"0"=
 width=3D"359" height=3D"113" id=3D"_x0000_i1026" src=3D"cid:image001.png@0=
1CE680C.C6F93480" alt=3D"George
            Fletcher"></span></a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>jose mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><o=
:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_--

--_004_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_
Content-Type: image/png; name="image001.png"
Content-Description: image001.png
Content-Disposition: inline; filename="image001.png"; size=80612;
	creation-date="Thu, 13 Jun 2013 15:05:33 GMT";
	modification-date="Thu, 13 Jun 2013 15:05:33 GMT"
Content-ID: <image001.png@01CE680C.C6F93480>
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAWcAAABxEAYAAABZ0L78AAAABmJLR0TIyMjIyMhnRJJpAAAACXBI
WXMAAABIAAAASABGyWs+AACAAElEQVR42uzddYAU15r4/W9VtY67MoO7u7u7BQ3uhEAIJLiEoIGg
ETSB4J7gENzd3WdghhnGrae16rx/7LJzf/du9ubecDe7+/bnn6G7Tj91TnWd5qlTp09Lly5dunTp
khC4ubm5ubm5ubm5uf0m3bt/VK9evXr16n92ddzc3Nzc3Nzc3Nz+Z7l8+fLly5dB/rMr4ubm5ubm
5ubm5va/gTtxdnNzc3Nzc3Nzc/sd3Imzm5ubm5ubm5ub2+/gTpzd3Nzc3Nzc3Nzcfgd34uzm5ubm
5ubm5ub2O+j+aACr1W632f79gQw40JEEUig7pPogRkthkh9o+5zFHGHAI0sR61oQpSxdUsuBrcbb
pFdeoF8d4O93BIy5QVcjp4Org/mQ+QIon3HeeBSk70lnG6iL5KL61yAdzP0l4ytwdrCmZQ0B49ng
q9E/gRhji7UkgeOj5wduzwCxUq6v7APuub5TB4P2Ont5xhJQD0ijlA6g5aoPzQXA2i9znjMWcodl
l8rcD7lFciKzh0Jukq2vmgUWb0e67SJYXlijsteBfaB9krUH6J97r/WzgTTOO8QvDSwJGSczMyHn
u0xSuoOro7RaLg+iCh11VUCb7vljQBTY9ufm5h4Bxd9UyHwPMieke6R/Cx6nQm5HZIIWr6z3igGz
l2e093YQJp4ZK4D+G+NGeT+oM131tF+h+qCaH5ZtCNWlCkXDX4BW0rXQdQ+ktaINkSD8pWBxEaRG
mAkCkYsLFwDS//NGKvzbkoT3kJCBAD7nc9DNlhYrA+H11cSHqevgwLrT7S+tBWHUv3CNgp6TGs9o
0AicE+TFUiRou8QMPMH3hee3xnwgL5H85d2gu2rqZj4Gx6edSDpQHzLyWW1qW3iakLTo4hLwehs8
I6cn2B8meCh34eGjN6VerAHpqq6tbSNkNUmZKq5A1sCcMT6fg/dN3VeGOxC81D8p/zUotqNgdqm1
YO1qH6dbCKnhSYG5oRDdMPQ7MRSsn6nZlolQ4JBHbmQ18Oub/4vIaZDbxPos9Uvw8/foELgXLjZ6
9MW+HWD9Tu2S0ggGRDQfOG02OH6SuyofQZlNxT4K3QhPvnj+TXY5ODD64vGlMyDLx2q51g282skj
ff0g+X5SBR9vmHdvYvTy6X92N3dzc3Nzc3N7H97fiLOMQAMyJRN+QC00cR6kJeKNUEEaLm7KvoBN
v1lcAOfD1MWJzcAY4JPP6zxo/tpHWhWgsa6E+WvQn5dVrzOg+YlH6jIQFjHNGQjKNSlC1ALOeb32
7wSGmd7xgf1Am+jq57gAHBd1tCogZNcOeyNw+iT5xe4G9aPcfukdQB3ubGr7FMS8zKTsCeAYlnko
7TpIF5Tn6gwQCbprcjdQVhnuGIaCoZ4pUz8fPJ2e18wHwXzEvNKjChg+0o3TvwLF05Xm+Bj0TqE4
h4NptemivjgoH0hhchDIG1wnXAGgVXBWtBUBpZP6sb0O6BMZ7woCU099Z20CGFM9bF5rQRrpqG3v
Ct5DPQ+bJ4LYp5Z1NoWglSFdAk6D51KfQ2Em0Hnpdfpb8GT4o5yYw2CZbKlk00D+UBkr7oI2QPpS
CgFpHjsIA5EoBWIBQPxVyvxvVEAARaRQBEg1qC2tA2cr8cr1HPLNCPf2qwt9Le26NjkA9faXTy79
AwT9HESAES4Ovq6/8wU8HPai1b0qkBWVPtDiB1yXF8qdwNCRMdI3YG7o/SZiFChhSkm7DkLe+n1t
tYBNyRJ6T6jSu/jWti3BL0dKKHwCMg+n7g1MA9+hHlUDy0HBdoFdC68EZ7ajSBEJss5l5/IM7hd6
qdzWQ8EF4bW9WkMhR4SlTDm4MfHBwYyR8NaeviljGuj2SiNe1wGvbXI153fwpnrSgWc/ws2y92v8
PAO07yyt/AtCWLhHg45bQNfM2Fs3CLxOmUfpoiHJmfRdRgzc/fS579HLkNk0s/fj4+BqlZ2WkwNp
dxJGZRSE3FG2GNfxP7t7u7m5ubm5ub1Pf3jE+T84kRAgFRQ2KQjERZ6KxaDVke6ImSBX1C9RzoK6
3RJvrQhckX8wzAJ5jqGdbi4o45Wh6iUQd+ReogZoA+W+WimQwsQK3WgQ/ppw6kEa7VxgGQJSSf1E
j0GgzhSfuayglYmv/7gaaIn2W84tIN2V5+vWgOGM51D/yeA8YDlrSQbptKuAEgcuf2dv5zhwfWqv
b/8C1AilmagDhgX6FnoPMGzxMnvXATnaNtwxDVDst22twWu+1FI6CdI52SoZQZ3rmmAvCfrH8iUC
wLFVHq31B/NoD7P5ETA2O5/lF1ArapO1aSCW2MzZPUHaoAUpy8CpWkxZn4NnYcMAz+WAgt31MWgn
rBvSZgIG+Yo+GqxDcuS31UC/2ONgcAD4JgUU9p8BmXfSbemL4OWYV1+kB0GFY6Wah/qCK8Y1SAPo
K3/MPEATqdIiQEIWsfxbkvz/JtASBkATsVwB8Vgqw88g3RffKBbQctQG2iywPqWG9gqK2gqMijJD
QtfUg0mloXr3sjuLdIawHgGpoUlg09QDrjOQ8WvWPcfX8GBUasHnP0HaV7afX5eEW1diI+93gJRv
LQkp3qDez56XnQo+ofoit9JBn+K3wbkGGi4p2KFcNXCV1QrICXDmkztnnppA3qL7MaQiSKVIMsZD
g80VSzf6BSrOLeBd+Q1k3Yk8knAB6s2sKXXtAfe/fPT22Rt40vCBZdtreBFoX+u4CBkx+sAXQ8B7
LqppOlQtWuZ8g6rg/2lkin8s+LcK9PfuCGmL3w7N/AxSVmcaxTfwfNWTjxIrg6ivHTZPAFvtzIyo
2eBKUH2yEyCjJDdefwpAvT+7k7u5ubm5ubm9H+8vcZb5t2TMjyxMwH6pCS9A11yMoDu4grVrTgMo
y8UZcR2Um4XLFc0B9Wsx33kLlJPOHpkfgvhM39/kC/ILLUV0AlFTbq3rDVJfOZ5ZoMXlTEpXQLuY
2z6pA+j26Ct65IDtlRorRoDWO3lYfFNw5Vjn2zKAydI3ynWQ+yiNOQZEGcZ43wHdA+movjR47/b6
RCkEjjaO3VJXcBbUhqsdwbVQLYI3GNaI7cZUcPXWBoqboNkJliaBVxGvyrpeYM+yLs/6HuRrzh2u
FPAsoeyTX4B8x3zFGAlyATVdKg7SKnt1ZwOw7nY2txUGNkm9lOZgn5ijt9wGfbJezT4I3PY4G1QW
jF1dPbOHgPOY/RXPIdOV/WFqV/CsFNg/dSboS4VpJQ6B91zfDX6/wIOlT+LjW0KJbwptCyoOupk6
L9EO1IniY9kIcm3JU/wK4o7IRQEUJLT/5x0UOAGBLwWBaaKOeAVyE1lhIOTE5ky0VYfLk25WvNkZ
EkplnI67Bzm1ct5oHaDS2/IfFZ8Ipu4e9YNCIWZxQs8XPeEH64Gftu8BXRXdgdyt4Jqk/zalNxS+
G9grKgnuz35x32cROPa4Clpfgff1xGr3KkBEsH+rkl9AxjF7s1QfKDg2YFn97+D1iLc1Dk6BD9c0
dTXrCT4p9s2GMVA6uqRnoZXwqFh86hMfeJ0Yvzc2HSy3bD9YesBL69tCRy6Da62YpxwH/zLWlISL
IDZZ14XPhJK1S0WVXQ5BgUEjfM6A5686zfoEEtfFX0vRQeKWjG9eHYdXckLE89kQFBt2ibuQueJF
WNoq4IDeLh2CzJIZJ42dQL7j09FzPFCN0X92J3dzc3Nzc3N7P95v4iyDeIZLvAGpDJGkgLAxVQ4B
+WN6SPNAVPLqbt4O0iUO6yeAPFC2Sg6QnxhaRwSCFIBelwViFr5sB8kljoo9oI3NjUteCDzXBXn7
gXzJ41LAV6D6Z3V5PRQki1RVrQ2KGlA2fDpoPyVYYjJBa+JqqE4E5Z6nNSQWuGlSPW6ASMv9Xh0H
oqz6hbwIDFbplfYIpAgtW0sEKcdewGUBVz55qHMZKPWVcnI66A5pucpkkGLEUzEHhKRM1w8HTlNT
tARzuuiotQI1gS5yCZB7mp+Y7oE8T/le5wW4rGGiFljbuNqo00FLljYoX4AtwRJsmweGU7gyV4Oy
TvcZL8H83PDM3BnSotJXWQqB7kditHWQZZU6GSPBJzD4WbQEOUOtrV2X4bU+Tk6bA0VbFe0fXAHU
FPuvaiiI59IC/AEb8J/9wLoEaICKJhUEaTczxUoQR7Tu4gcwHzMtMpqgWXDtpzXWwOGm5/fdHgE7
D51btW0/HOHektNdofr1IsNLbgJdU0n1tULUCN+CYceh9K5CNSssg+QiubNfXYY3cmrwrzUguJ7/
a2chcFyQGliXgn8t80jzR6B4Z9/LTIFHJ98OdfUCi6e11OlbUHpZvvzh9yBuT9rl+6kw8FSbj3qH
wKrjm/W/hEBKD9uaxwOgVmzxEh1HwdPPXqbefwA55cV+zyMQOcirj+4y2BpnVfZ8DSU9ixyt8itU
/Ca/qfgqMP9k1HnmwtulidXTX0BM8cQ9N3bBgevXJ+w+ACEPfXXOMlD/ZOGg5lMhIsn/81oWMP5q
KilVg8zX/t0sK+Ft+dyzcTX+BT22EpWoBIfnHJ5zeA5s99/uv90fnjZ82vBpQ1CXq8vV5VD4q8Jf
Ff4K2u1vt7/dfuiU0imlUwoo1ZRqSrV/Qb3c/ktVqlSpUqXKP/66ic0mNpvYDDrP6Tyn85y/jXPs
2LFjx46Bn5+fn5/fH6/n8+3Ptz/fnve4QIECBQoUeP/nzb+6HW5ubm7/Ku8vcRYIZMAohZACIk48
kT4FjjJHfA5Sb+W8XA0YL030CQbtqtopZxMoOVJtpSYwUqpjGgHipUiRpgNNpTOsAnFH2qidAynM
cNSzKvCxstVUFLTLjplZPwNztWDxMcj5fUWgJ8iWcE9zKsgr9S75NLDBNN1zDUjn5E3mEuD6KmOm
ZRGIgXYvewOQ+htjlQSQVPtRVwgov9qt6kawhzuinN6gOu3XHJ8AC9XNohzoJkolFDNIM3XjpR4g
9TblevUCkSLaaS/BVV8NdWWCeaV6TM4F1y19QWUBKAt0F9UHIB+RGkl60MrmdrH3AvWpYze7wPiZ
Lsc8HtRHzkr2EZC9LXt4ahMwq16D/OqD7zxfp+c2yJma1SH9S6BYSmjMKLBPNVYyeoMhxjcqcgs8
W/UqMvUHKHSq0J7gMJB+kq6JysAV8UguC5RBEq8AD3T4ATYcWAGBhgmkCEmPBuKguIMAougrPwCl
su4jMQucu5z5HHchcKCvpFaEhl7lG0SvBcsnhuXPj4Oupnbs0UiQGmUmV0iHyv3LbK9eAX4K+7XZ
z1ch9JPQ/qaqUH1EqY/rDIZWM8uczjcHnhTKnPAmCXb1O3LxxypgGKvcTCoK1kZqoO90uJXwxDPg
Afh1N6T6roRHni+ky3vhm25bNhocENTN0EGeDNa+GTGBO0EtoYjUkxDxJmB14eOQM9ByLvowWGRL
vfPNwNTOQ5Zqw40CT5pdWgtPa8caHhUDubk5w8MM8Tfe3kpYB+Gpns8DH0LZlICDTa6Bb+GginF9
wN+Zr12JxaA10ZVIegm5bdXVFj/Qh4g9D7dASpmU+MQLABR9nx12/sn5J+efhO2Ntzfe3jjveb1L
79K7+I/E+qHHQ4+HHvCw68OuD7vC9SbXm1xvAvOGzRs2bxhwgxvceM+fJm6/W8jUkKkhU0EZrgxX
hv92OY/RHqM9Rv/31avb/G7zu83Pe/wfCS1++P1ZB8vNzc3tf5D3lzjDv41k6oXAC0jnBbeAGCxi
JVCWMMkMIlRL00aDttDlnTsSpPHyQbMFpOnGA3wN0iKxRJ0PIo1gEQjCIFfUVQKpirVnVg64ZJrn
GkGZ5THStw9Irfwu+fYE3XW5i9wXxEbXdG0LSLsKVworDVJJXQldQaC7us5lAaWqTHxtsB9xzkr5
AJzhmX2zH4ErxXLIFQjWKtbrtt6Q+431u9xX4PJzpYlskL6Rtuuag7JUPisvAGNdQwVjfxClDb2k
AWAf50x2rgXpiDrXVQvUcloxJQSkmloHUQ9kh/TY1RBcQxzDFQk8fUw2ox1cW+2b7btAO+wq4LwL
8g7dDP0CsMXaflCPgl0vQrJLgOmET7ruDRhL6+/qJoLi7VTsW8E+OH18/HPwuuo7L2AbWE9Zq5lK
Qdbs7Au2NPDJ9I433AZ1lzpDvAYa4KA2iEJimvYjSLnSJikGOCEtlXJAZBAu7gEatykKnKOJazho
Z0SschLk86w2FobUjm/TMy3gW0ye5TCA+oFUPyMb0sIyVMqDqs8ccT8dDmZfPfXkPJhem+SU2mB4
rE8LKwDpxbLnmifA6VZJ+61pkLgk9atbOyE529k2xQxq+5wvhBeYHmrV0mqCdsE2KPEmiNvBPULK
Q7mUyAE15oHjpHWXawNkdpJdzvZQ4HDEwFrD4Engkz3x6yEsNHCpf2NIGpC9IG0MJFe1hKW0AEOX
3KOOqVC1TalujUxgf5qdEOgFbx9ltnzUDSbX724a4Au61voJ5o/htTO5RVY5eGSIOXr0NPx64dKE
LZegyewqnT8YBj7f2o+HPIVjda5Ou1EDshdprz1/AHbz9fvoWqdOnTp16hRs/2z7Z9s/A2MtYy1j
LZgePz1+ejw0/r7x942/B+mcdE46B6czT2eezoSpoVNDp4bmJUBnrWetZ61Ql7rU/e/5jHH7T2yu
v7n+5vrg98bvjd+bP7s2bm5ubm6/1/tcx1n691v9Fik/4CGVEV0BM/el2SC9oqTSH9RQx7TUWsBQ
iynrI5AF6bpjoPWhhRwO0mkxlK8BD+mAcgQoZOuZ9RCI01nNz0FZ6ent3wGkOrpJxl4gHaGxooKW
T8txXgH1ufzW8QDkjdoZNgLrHLMc40BUxt/5IzhD7K9yH4FUTTxQJ4MuSnfH0ARsV3N6WLIhs05q
VsYCsGuW0Q4NxAM1S9wB3Tg5XSkHHj6Gu+Zk8PzIMNijKOhbSD3keNAuiZvMB/oqG/W/gi7EEGYq
BLSR+snzwTXLleH8APQf68/Jv4KxodGkNAGvceYEz/ug/1UpaAgAsVKdr9YH/V5llewH2laX3a4H
u5fFI8UGslO+6TKDdkBqqB0B24asHumHIO1OXNEHu0HNcmyx7oacmZaHjpcgbZIypRagLRXn1Yug
+1mJVzaC2WAY5VENlLmyybgM2CyCJA+Qyop50j7gFG3IBQaKUPlTYLE0VOoPmZWz96fHgfm8uRo+
kF1AL5KMkDHUYUq7ADFpb47ELwHXXHlibm9In+0smngO8m/wGxK1B1xTciv4SvDgw9i714Ph8Isb
LTd8Cq+mJW97XhAaly66ruFHYIiUzL4dQbprmKY1AFOGb3O9EbyrMabKEXCdoXJmAmRPdk55egZi
vk1okRQJDSpXsIRdgeLn/QoHy6A7rHxwawpEhgZcMRwH41i7Z+BIaFO8VkZzDxjjPajg4CUQ+Cbk
B6+V0HhS9QKV9oPk8FotxsDBPpeOHdgEv5w83vS79fC40CvT61VQaE5o1cAj8HTHk5jTpyHRlvjt
rYZQ7XaxSSVbQoFjAZtePX9/nWvr1q1bt27Nezxs2LBhw4ZBs13NdjXblXcrXR4uD5eHQ8OnDZ82
fArjt4/fPn47tAxpGdIyBHJO55zOOf238eP3xu+N3wtjN4/dPHYz1H1Y92Hdh1DXo65HXQ/4vNHn
jT5vBAltE9omtP1PKvjvI93vRsI7dOjQoUMHqFGjRo0aNaD9l+2/bP8lbBu3bdy2cXnl38nIyMjI
yMi7hf/u78O6D+s+rAtd0rukd0mHDQ82PNjw4G/3u3Hjxo0bN+Ydj6YBTQOaBsDJoieLniz6t3Hf
7e+9tf9/iH+0HeoV9Yp65benkjRp0qRJkyZwz3DPcM/wt8d9z7Q90/ZMgy6FuhTqUijv/W76sunL
pi9hwYkFJxacAFspWylbqd+u9035pnxT/ts4Ay4PuDzgMrxs+rLpy6Z/vL1/+Hxzc3P7/733N+L8
bo5sFhACUh3s7ACG0l10BLWT1EJeCDI8YzGot5NePHsNWow5M6QLyJ6m2VIZ0OpSgVJAf3FD6g9S
FX0HT0DyNOyXuoP0RPtSiwHsWoC6A0Rj+aQuP+ChnZf6gNSOyspDIFGuJGUAw8VI3WDgE9WpDQNp
i1ffgJ2gH+SXEWoH0U/0VTeD/7jg1iHbwTw9tUVGFGiHrMutHUBOlCaRARRzxNv2gK61XERZAzZP
V7Twgpyx9nbOhsANZ2WXP7g2aWMcj8DpUC+rVYBnYrN6HJSyTOEDkL5S1hsagmEvrbQVgMUcTAS4
ujvO6wsBvahvygBHReePjnmgzROjHGXBdcuxxBoC2k/Oyy5fkE7oihlKgbGLOcPnLNiephdP6gOW
12lF4z0g89us+IjeUKBgvqaBI0C5xUT9l/DqdoZf3FbI7ZjbKu45+F3xuOw7D4KmeJcr8gu4urLX
FQJSGREvFwaENII+INXRglkKhmomncEfopeHJRTxAst34qjoB4nXH/36ajAEF/BbaS0AhoaefZI1
yApKm2Dzg4uLngxM3gHGIcbqmc/Bs5jS2vMNmM9qk/VfQ1BL05lKH4L4WJkj6SFgn0ePgK/BY4+S
EXUE1BuuLOM3UGlRpVIln4ASIW0scB7ODjhf8vxE6OhVJbFZVyjdvMqREr/AS8vrC1lDISX3VTnh
C35nQn+NnAA+oR5HnjjAMMw0xFOFnx7vdB44Bfc2xta8fAgykjLn+22FtW0OZGzPD/5+/h29e0LR
zOhWviNAG5ZTXXOAuYnH/rAXoDugv2ZPg1+jr7Q4VhHMiX6y7xIwV9et9a//x7uVGCwGi8Fw+6fb
P93+CShHOcrlJYZ/T9uIthFtI6DtwbYH2x782+25i3MX5y6GoceHHh96HBITExMTE6H2qNqjao8C
RxlHGUcZOJl1MutkVt4UkK05W3O25oCXl5eXlxfs2Llj546dML/r/K7zu4J+iX6JfglU0ipplbS8
xGhB/wX9F/QHeae8U94JXehCl/+i/uO2j9s+bjskNE1omtAUWM961udt35ewL2FfAixZsmTJkiV5
FxCFYgvFFoqF6Xun752+F1jMYhb/69r/j+rXr1+/fv1+e+5wiRIlSpQoAbM7ze40u9Pfj/fPtmNT
kU1FNhWB/J3yd8rfCWJ3x+6O3Z0XN1++fPny5QNDfUN9w1+czz//8vMvP/+SVz/DdMN0w3SorFZW
K6vwovqL6i+qw7bobdHboiH7aPbR7KPwJV/y5X9S/ylTpkyZMgUiiCCCvAvAOyPujLgzAr50fOn4
0gFrWcva9/C+/bPnm5ubm9v7G3HWAAmkfLjIAfE9+WkNohoLpK0gf0iI6xLIa+U95pvgWJBbMHci
iOuqyRkAcnfpmVQZxBYSOARESpXFFJCOyS+VpyCeiYriF9Aaaz9o+4AFpEg5IFm4RhpQW66lKwhS
YWmZIQK0eG2gpIFUVhTTQkEJkCKNo0GZ4b/GsxVQysNf7QdyJZ/aBjuYtZCTpkgwzzevdS0H71GB
vZVkMD7x+lorCrb6zlGWIZA+Ib1c8hGwvMic8LYLqK9FQWd+0FawRR0OzqX2Ic6vwPWlekv0BcdA
YZLKgPhCLiJ3AeWmvFK3DMxfG7cZ2oDfl15tPceC7xmfVJ9xYGpurGr2BsNwn4IBP4O2RlshvQV5
pyhBLOhWy/fxALHc1c2hA7Wi/cfsHOBz5RNTXci4m6B/OhBSd6fWSasGL5Ner05cAkcn3/3wh+aw
8dSRvks3wdIftx758Qr8dPz45G3l4dWApNGJSaDfLzbpvgc1R/SVvgCtlZZEETDV1V3RlYWzwbcz
r/aGm5XjejxpDUx1pSu/gGeIMspvJZi9PQsbPwNDQX24YoXUKekbUo6DslOZajgMnpP0DfJ1htwp
lqmewyA8wyRFbQb/rT6T9bFg/NrcMec0tF5abVyVPqCGcCP3JpQ+XKS3Xzs4Ue9cyPWjcPjolY/O
nYLa08ut734Vzg64XfDtZ7Bm5rqDh8ZCjH/shEfjwBhsrO/lDWpp+Tv7Fqi8pPjIlpMhJS1mYY4K
F3Nutj7XBOqlVsopfAgCRgW6ii4Gc1/jLscssJS39kgfCM+nvRwVPxkeWVO6PA6G89cf3th1Ci6N
iHHtngf2SFFCPQPO/taC6dcgZmGiXvn1j3cry2LLYsticJZzlnOWy3s+KCgoKCjob8svsiyyLLLk
fZnsr/9+++233377bV75Q8mHkg8l5yUeH3zwwQcffABL+yzts7QPLL+y/MryK3nPvyt34MsDXx74
iwxow8MNDzc8zHv8bgrJ9+W/L/99eZgWOi10Wmje9s0NNjfY3ODvt7/OJ3U+qfMJ7G29t/Xe1tD5
SOcjnY/kbV//YP2D9X8xIvguAdvivcV7izcMEUPEEPHb8d9X+/9RcXFxcXFxeYnqX/99t5/f659t
x+F5h+cdnge7Ju2atGvS38Zdt27dunXroNjCYguLLfyL415nfZ31dfIez2g7o+2MtvDdgO8GfDcg
7w6A/o7+jv4OHJl9ZPaR2WCz2Wz/8YNZf+HdlyB3vNjxYscLWFZ6WellpfO2P6jzoM6Dv9jfv+p9
+3vnm5ubm9v7neMsAy4U8QIIIh0boLCHdBAvtaPqUhBTxTRHezDM8pkeMhCUL5TWclkQi0Rv8RlI
SVKaXAkYKO4JG4gX4rHoClyjsXwG5CDFRiAwl3ViEGATz7UKQCRCGQRSYVFXNAceyv3UMaB1oqy8
HaTldBcjgHoZxeI1yNVedL//EBy56Rsy64Kl7us2KR+D1lIX7ukN2lemdM/zkPthdmv1GxDntdGG
/CAbdN2MceAcplZxvAYypOs2L3CeJkSpDdJpP71XH0i5kC3l5kB2eFZG6iCwzc5ennUMvL80DfAY
A1IleZFcHEz+ylLdByB31Z1WGoJeVn91TQVbd71DXxBc2/hW3ADjBtcsRwughlKaSBBRrldyR7Df
cTzOHQemT/ULjNGgxGppxl2QMzLjePYW2LbiwMsLJ+De1bRra2qAxylDtcJ3QemuzotuCTd73i97
+XPIHWPLsX8H4/d3GzSjMBjayKOVzqA003XX1sGDEvFJT2eBbqyxeFo8yC7NO2MH3JsTs+HmTUi+
ZPNMXgihLXTe/o/ANiFnUu5xMH7vdce4CvyyPXY7Z4BHTfWAfgvYz+sO2j4H06kQu9QfDLNME9Q4
SPS0HImvBFlxruQ3r6CaVxG15R7w3KDb53EearYv2+X+EbjW6e5B602oPKFafkM9cPRhUvEg8PM2
7U3yhaILyhSrng57Xx5/saEx6D4nMiUOMj8yPGtkBGd3613xFgpcDK1bqArEesefyO0JZxOelLjh
Ab5B5jPGqWC/Zi2YPA20g+oMw1Tw7e512FIfXGXSp7s+gdRvnEbTNHBe0k3RjkFGR/uF9DKQkz+3
rLEFABl/pEuZH5gfmB+AtFpaLa3OG4FO75LeJb0LBP8c/HPwz3nlU6JTolOiIbZgbMHYgn8bL6VN
SpuUNnmP7/90/6f7PwHhhBMOO3fu3LlzZ97f3/LuddYEa4I1Ad48fPPwzV8kzg3GNBjTYAzQgha0
gPqb6m+qvylv++uQ1yGvQ347kXpnxI8jfhzx49+O7L573V/fwm8yvsn4JuOBDWxgQ96I+xKWsOS/
aMc/237mM5/5/MPe9yoS/13teDfl4t37905NQ01Dzb+YyhHYLLBZYDO46LjouOj4+3Fr3a11t9Zd
oA1taANFuhbpWqQrEEAAAXlTSt5Xe5tPaj6p+X9yofBb55ubm5vbO+9zOTqBDOKlFEY8SF+I76Vu
IPJLbcUW0CJoJMeBNFMrmpsA8oiA+5H+oHYXzdX9oBvGNhaBOE0mTuAgyeIJSDsZL6WA6CcZhQ5E
BPXkQKCIGKDNAWkVVXgMPGKJOABUlL9hEYgStvnZO4Ab+leeBUFWlcFyb8gu9DzwaSlI0p3scdEX
rBscJvEN2FYafjGPAdev8nprAzCoirclCkyHPD/19wW5ln6UNBckP0mnxYDilJroLoNrjfqj4Tsw
FfT53vwtpEdZ4zN6gK5kzpDM/hC2yHjDfA6s5Vwfi3wg/aQU1F0GLUYEEwe5Ay2eOZXB1jWzXuYU
yB6Z/VXKc7Au8tjk3QbsH7i6umJADHLqcrqDxzljhG8MiGhRVh0Aujl48QUYR9mf5gJKS3mp0x90
hWx9cmZDYEGfgsE1QDfqzZMyTYBUrUvy1xD2YbDRNQ6cN4yfvf4EXm55XNsWBd9u2DD/p6Yw8ESn
3Z1KQ2KLhIdZq+B6WELorQg4/sNLr7lPwWer+CagIKQ/SGlkHwJKfeW+PB/igqUBSkswpeiqmztA
iTPFvzZfgYwGyfucv4DxYvC07EdQspbIr3rDmw8Sar1ZAMYEaZ8+ELyHepnzvQSHar2m3IMmS+tm
NNgFftO9Av0LwptbaRuCX0LxBfna6HbBG/3r85YR0PhczeQCm+FxxOM+8gUoP6banBJfQu5q+9cf
1oVrXR+Nfz0V/CsGXfGZA8+0R7OuRUCLbU3W9FkGh+pdHXAvFOpXKFxCb4MnM+OKP+wLHlPNY70P
gHJAl/pEhuB2+i2WBpDURVfc+zpoQ8Ukz1CQVqk3cvaA7FKWshUC25i2iVrA2T/Wrd7dyi95vuT5
kufhAQ94AOyfsX/G/hnQn/70/4vyc1LnpM5JhTnMYQ6wf//+/fv3wxdffPHFF1/8bXzbBdsF2wWg
M53pDAETAyYGTATvx96PvR//dr1MK00rTSt/fzukG9IN6T9bxePdXOcLXODC327+rQRGW64t15b/
J88P1gZrg//i+A1ThinDAB988Pnz2v+v9t/VDlFZVBaVgYc85C8ulHQ6nU73B/43eTc14z+8W/Wl
CU1o8t/XXnfC7Obm9ve8z+XoJATgL1IJAH5B5hFwR0RKbUAK4GutKMjNzeUDfwSxRy6YcwJYLMqx
D9Br0wkHnjCRQyBG4SckoDlh8hKQftTmaodBnBZGbQjQXhkj9waRIFpL8SAt4rQ2GMTHSpTxJYjx
ufEZ10Hrm9Mzti5IP3kP9Y6B3GfXH94MBrHTu4JPH3AkqTv0ByD3TGqLzFyQ7FLvnCbgWCYUy07I
0GVUS94NuhXyj9IE0D1Wbho8QfKXF+hmgscs7xi/zaDMyG3uJ4NpRU5k1gAI/MFczDgMXCG6ZvpN
oATJHZTDQG/nRGd3MAyTo6VZEHjYcNu3OLgiPM8Ye0LuGceP/r9C6ipbKf1NSPrOOccaCbaiKX2z
j4L2ncturwumROmK6RIY1kjnxQ7wuCOXUcqCsbHTZY8EdemDXtcGgbe9xLRip8FnS/gUZz9IWpA5
x+4JjtOZvXIiILtJgr7wFSjVLapO00EQ+oN3mXwbYf/K46uPd4Tka9LX1h/gZXzCtItzIeCWz2Dj
N1Dgq4B63haIcWlvpGhwWFwa26EowecqnYKLKx4tuugDcS/THuTOh7CF+jp+X0PIiIjV5k/BuFCu
V+c74HNlTWItiBuXWe1pI8jv53E8chKUnRFmrHEB4ja8qRF/FW5PzFj2qgq8/CShVvJayD+5YHhQ
Zyj2U9TpoOvgX9Rf9tsE/pUD1uZ+DKKF3EWXBAU6l1xfoC+kfGz5VE6E9q9btSw3Bw6P359feQrG
RNMM63Co419lYNE14HFF2eL8GUqVK3EpuAvYJfsFQyCcEJebx8wB+wq5lbkn6L829pKegq6kY2z2
IAiN8WkQIMHraFv5+OtQ4Bufc77/NjWh+fvoXt2Odzve7ThMZzrTgVVVVlVZVQX8t/tv998Obaa1
mdZmWl4CctF50XnRCUv2Ltm7ZO9vxy3QqUCnAp0ACQkJOkZ1jOoYBcM7D+88vHNeuSdjn4x9MhZi
YmJiYmIg/9z8c/PPBXNPc09zTwhPCE8IT8j7EtapRacWnVr0HwPOnFp4auGphUArWtEKIttFtots
B6ZppmmmaWDLsGXYMn7/8fDY4LHBYwMExwXHBcdBcnRydHI0nOh2otuJbtA2oW1C2wQ4dPjQ4UOH
ga50pev7b///FP+qdry7w8EOdrADzPfN9833ISwiLCIsIm8KxLtVX1q0aNGiRYu8Ox/tO7Tv0L5D
XrwT3U90P9H9f2573dzc3P6e9ztVA0BCRQKcUgh6YLeQKACyjR90rUAMkUZ41AVli2GxshLEE+Gl
zgS1N9nqfZCeSiu0bSDXEDuVT4EtIk3KBFFC2abVBPkTUc01C7QFak/ZBnIT+TNJD9p5MV63FpRp
2hrnWXDWE01VP8jxvVb98mcgaom5zpOgTI4YHewFWfljb6WWgeSrSTnpl0Ht43ph/xVyxqccT54M
Lz5J3pv1FrIO6FYaOoBywNjAMz8EvZQ/MsZCviBzYY9uoCtjlrJmgHxaF/+6Lfhm+o2Xg8A2Tgx1
rQGpvn68d00wlDeu9NoN9idaD7qA2kKub9wEhg7GU8YpIF/UG/QmkEJ1Jse3YIjzeWwoA6YG0meB
4yEhS11m6QJaZbuUvgA8rxiqiFQwVxcVpapgfisvVvuA8rE8V78dpOr3Cj+6AAEH/Uo5h4DPh9GP
4y5AbFzCgzefQvZcY520L6FswZIHO9QE3ylW/yIP4K53/JCH30JSZkb7a+PA4BusJu4B+bT0mWMP
+Nf0PubtB47H1o3SS/AdZNjumwrZKY55wgFBmeZThsIQPtxzd6QKiU9jDVGrwVA5aIV1I2TOiz/7
7BeIHhwcGPQIevRo8rJHCzjy7NrCLYUhZmLW8qfnIfGivWTGYrjfPyv28nrIzs761rgHAir6fJ9b
FU5/fGJSXG/IXF9xpysVOvg27Rquh6B1gQ+8v4DTAy6ufxgDzR83ksr6wMtZLzq87QQpC9IuZU0G
XWlDmLYd/Lr5l/JJBY8TgYsVT0h7nphu9Yfr9msT7jSElz9ktnkmwH+k/kTwx2A55Nz0XAGvQ7ok
20RwNBCzFRlydjk6Z1QE73xa++APIPuSMlBEABXeT7dq/UvrX1r/Apf3Xd53eR8cbH+w/cH2MGvW
rFmzZsE8j3ke8zxA9pA9ZA9wfOP4xvFN3pfM/mMk9q9GCtsdaHeg3QHYeHzj8Y3H4Uf9j/of9fDU
86nnU8+8kcR3y9hxnetch7XV11ZfWx3oSU96Qp9SfUr1KQVfFf6q8FeFYUbkjMgZkbD39t7be2/n
fTnwnT62PrY+tn/sGPw//n1EsvOazms6r4EVK1asWLECZnWc1XFWR9hcbHOxzcXgZcDLgJf/xZco
31f7/2zvqx3vljm0X7BfsF+AmbNmzpo5C8bEjYkbEwf5buS7ke8G9B7Xe1zvcbAgcUHigsS8Oxp7
w/eG7w2HF6VelHpRKi/Ouzn27+L/6e19wxvcywC6ubn9E95v4vxvy9E5MQEmPEUMALu1BGCbNIwa
QBlRS9NAeEqPpGQQpaQ1uhygqRQueoC0RyziArBbjpUng/pL1uCnk8De7uXeW54gjwvwL9gP9Jmm
ZwYVXLetOtuHoPsxrEyJ9qDJ+suBJ0HXnjpKRXBEvF2c2wDSnqQOfXUScEU9D/0e4vbGJSZ1BfsP
9qvaARBjxDFXENi+t36DCXwqelb1mwYF2hasWjgFAmP9LkemgGd749c+JpBidVk0A+c17XTuGbB6
W09kCOCmJTQ7ErK3pB1PBIx6nx7GR2CMMx2RW4Pusa6I3AykW/IE3XqQjlJIag5Sc3FKqgy63uom
9TgQrV3OHQ2eMZ4D5MngGeCT7OMJrrM5J7gOhnEizNEY9AvVR7ajYH5mP6g+BP0Uj3YBxwBFWZB+
CLQrz/um3oCUKGc+uRHoEw2tPbuBstTS3LUJ4vqY1pwvCwQHXM5dDR47LJWKbgGvRr6fekVAkQam
Y/VOQSOfKjerzIXXZXMbPt4Em8qeKLZuI/h5eDmCz4OtQvI26Qe408ju9PoaPPNpN6qNhJotaqc8
ToakfInHM3tAzoDsMa5seLEzW3/hOKhNHceNEVBnc8mXDftC+LJ4e7664GP0iQv6EFJNSdb4geB1
odT4SA/IapQzLLYYmPqabliegmuhPTZ1F2z9fk/VY/0gnyEqKtwbiraJ8CuwEFwL7b+oI6GMWmpu
xGh4UTLmyNuz4LnE+ytDUTDmNzf3Dgf9Wldb0RUyhfTKURcMT/yKlBoFreTiY+tugOzOGXXiKsCr
qcmq9TuIkbNW5XiD7MlA/RQw2XNK2H8Cyderf3YWmD3IMoW9x77174nijMEzBs8YDBVjK8ZWjIWd
E3dO3DkRXjR90fRFUzCajCajCZrvar6r+S4YPWD0gNEDYMyjMY/GPPrbsGFhYWFhYbByxcoVK1fA
0tJLSy8tDZe+v/T9pe9Bui5dl65DpQqVKlSqAMOl4dJwCUrklsgtkZsXp0vBLgW7FAT1M/Uz9TPY
/Grzq82v4PqB6weuH8jbT6/nvZ73eg6dD3c+3PkweXNK/kn9y/Uv178c5PTK6ZXTK295tMTridcT
r8Nkz8mekz1hRrsZ7Wa0+9e1/8/2vtoxhCEMAdZsWLNhzQa4dOnSpUuXIPdO7p3cO8BCFrIQuh3r
dqzbMZBfyi/ll7Bl65atW7bC9ZXXV15fCX6V/Cr5VYI+0/tM7zMdhg8bPmz4MKAZzWj257f3r5cj
dHNzc/u9pH/7YBSievXq1atX/8cDWK12u83Gf6yqgQfgAm5jQQKxBA/pDMjnWS99AHRihisctG/V
jfY0kGLlJnJzkArInsZuwE3NX6kL2g+6/aIJqN8k37t9EnKHnx5y8DWIeF24bw8wlAx/FZIBokjW
w5R5IA/wXeNdD4xTK7Xs5AVKXekjXTvIjD0z9XIzSO71akjsMnjmF6d7mgSZc9NfaVHg+Fn9QUsE
xaYG2p6AYb1sMNSDsIYBGwNmQ/iI6PmRXwDblM90uaD9Io+URoKrOTmOcKCiPdD5Ocid9A313cHv
cPTl/IUh/vCz0zHfgnRZniIPBnFLniJagK2c/aZtCYhol0VdClJ70UWuARg1kzYd1A32fdafQZur
fs1zsD+Vp2OBtzG5n2cOAOutzAWpM8E31PBMKg7m8fbObAHTaK2UoTDobb4PfQUIEnpkh4DJqi5T
B8OxUaUavk6HR9/KOx5UAJ/+9rJen0PGHnEiQ4P0j9Rd6mkoONkrofpZKO4ZqpQ7DvIY/aTcX8Fa
zZ6m3wABbU39RHe49vOLsGvLITree2zVBZCa9nbk6xugf+LpzFcQkrZmet/JDwULhDZy9QHDF/LL
gJnAHXHCFQupG9LfpI2CUZX7jvo2P+hXyw09EyDW683qh8vhePXb3XcuAP0Zx0ZjGqhlHGtM3eHF
q7fV0wSEFw701i6DlG760ssMvh/qfih8AbTvbK2UnlCtWYX8NQZBkJf/x57dIfxSvvt+TeGo9fSV
xz9CRp+UUq9uQF3/OqfKfgV2P0cB+Sgofro10jIouafI7KiOsDv38I6LLWB7xIkCO45D6A9BfvZh
kDYno2ruAwivrr9kOQ7SaO2ckEBERPqkZkLUpcie3sVhgtLzh2Pf/dnd/P+edyPqKyuvrLyyct7z
774cWPJsybMlz8KNoTeG3hgKQ64PuT7ket5UlvPnzp87fw70a/Vr9Wv/7Na4ubm5uf1Pd/ny5cuX
L7/PEWcFgQAyJA9kkOqI60ggzeQ660DrgEN4g3yPzXIHEMO1cFdnUEpLYz0yQdsimijlgEEsUp+C
1EXzFVNAquY4yQ1gudfA/D+B2JOVlLECrBtjPk4YCdpUR9ucFSD1Te6QkQq61CjzmwsgfR71uuRZ
8IyqvKfEYrAdSg1O/ASCPvSZG1kbnMMNmmU3aC1twpkMfss9q0T9DOb7SqIaBCajKClckLvU+jJr
Aug89WOMMaDfpNrU5eCdofQQJcD0UVBc8Asw7Y26WPA7UIr6T/SoA6JsxibLBcj60Hok9y5Yy9s3
2Byg+17aoTsNaj7pE5EJtJTs0jiQ58stFQuINtoI3XgQB6RB6ldgWKRkKi0gYKZpnE865Ky1j8vq
Dbpw5w/ZJlBX2/o6FNCqmhf7fAoCx6Ps+aCYvKcZ1gJyzmvxOWijM8t41gb/8X41PeOgYkbpj6Mf
QczUZ18XbQKJg1OLB/qC4qHWk9ZC4nZbp8weYIrxskmhwB55SqE18Dwjvqf1OuRvJt+u1RO0Otlb
dWdBfOuKDtoF6jnbiaxECMvxb1ahA1gDsjMy24OjlhRILqj76ZWzBXK/d35is8CJxGuTz0wE81Pz
4dB5cLXxk+2/1IByn+dfHuEAY7h1gF80XO9+JzGzM9Q/WF40fA7JDbMrPIuCjIPWFbcLgtcN77NB
o6FY5ZKBNZtC0ZxiS8J+gZdXnt+P7wSmoRm3jV9Dzr3407G3oPj1Mqsj08E51zZZNkO+7yNvBdnh
dpVbyrNyoN/v6iE8wfRYKZCyH7y+9NwT/xL0h83llAkQddVx3GED23bPbTjAOEAX7+wPzuHKJfMs
iJ/luOh4Dkz/s7v6/02GtYa1hrVwZdCVQVcG5f1wxYbhG4ZvGA6hEaERoX8xB/fdlxCbjGsyrsk4
0KfqU/Wpf3Yr3Nzc3Nz+t/njI865drvNCWhouAANAwpIEaTiBKoQyzUQY/GlAkhOrLIdtCvaKHtb
EK+kafpToMyV4ikIUmG+0caDKCaCJAOIEY612d+BtdW1xyceg/X6k/YP34KrprVo7mgwlPftEyyD
YUqxoWW+B9cM+9eZi8FnctUHzaqDXFzubsgF+5NXPV68hZwxt6bdaAqXDqUZc7fBWy0lf1ohiEry
+ta/Gej2OLras8E0UnqrdADjOVNRfUUwPiLeNRiCo/O9iO4PATFVV1U5D7IcrgY9AMml76XVANvz
6yvub4WcMzHnE76E1AI5g3P2gjXJ/thRBrQFTNNywPHWccNxG0RVaY14BJQVPbWqwFeuRG0RaGHO
Z5oniMG6IOUaMN5YwpgC1nPWk1lzIGNbom/8ZMjOvlX7jgyBD4NGhxwEz2aBh8Lmg5btuzvkAFhP
aPWMS+HhPk+XvS1Y5hseuNqAYbG4p3YD7YV1hWyGrAP271Q/sLTK+EXrD658rmk5m0BNtz5y7gDb
BOdKW2PQ5epdyreg3XXWs/cA1wX1oRwGhqr6WOMwoILSQfiD8ZBptPdB8Hxg6Cl3B92HpvliDjhK
iocmb1Btuo5aCChhugVyCgRu8j3lPANeTr+Dnguh/JriMxqPBeWNK1nLB48fPe379CoEpgaEmhtC
fMv4W49fQN189UOq/wqu19ZPg3dD8M7QOuaH4B3r2cWnJOSm2QdRBN5cjVEyr4J23Op6dRbKZFSe
VT4DHt95tPh1e4jxfVM11gjJnyb5PC8IcXtS98Z9AorFJztNA0+TaU7WfpBHp/d29QH7Ro8AV38I
qOo/1n8mpM539c6eBNbxci+5GuSEZczPSIQfjo/feCHtz+7m/3elzU2bmzYXFp9dfHbxWbhQ5kKZ
C2Ugq0dWj6weeetdN23StEnTJjC82vBqw6uBeYN5g3nDn117Nzc3N7f/Ld6NOP/xxNlhz7W9AKmY
FC6VBPFAvBVxQALJUlVAJY00kDoRJAoBlVmmHAWxXgxzlQMmydOkxyANFJFiAriWsFC3H+TG+hf6
W6BOffT22F54uX3zxE3RkPZrzsemTWB+4PmZzyjw7+kVbbCCWQT8Kq0Gj4dVTtfzALNX6U7VC4Ec
SZxyA9Rvbaase+Bafj3p5o/wTHs67mZvyJ2iZYhfwfsnaV7ILVDPsdSQAt5TvHf5FgaPaGOUR18w
V/Z86RELZmelhKJjgZ+CHb5RIHbaytgug+57y9zMWZAb9PDYKx2k7I6pkPgIsr2sH1srgrOb1EZT
QFgYLuaD44njG8cP4BjsMlq/BnkqwaIocE67yM9ApBatlAdtj9Rb0YBUw2tlI6iVxUCSwHbR9oFl
OGQOfvskdytk3M7oYnsOytbQZQGTQEwzCc+fIMPp2GXtCWlvXFnp3SA1J0mklwCLLmNS5mqwxVhq
ZT4B+zHHOlc66DdxWz4PelnX3LAB5PP6/noNTCFGnSEGpI2yXakFikNfRD8N5EZyX7kSyBPlseI0
iGmihBwJWmM1g7Lg/Ez7WssPWi2aqd4g7mnbhAPksfJEfRdQJhmLmmLAWNT0WKoFhk98jMFrQd/E
18P/Efi9CLgREA26guYSxsXgfJEc97ItZNS0fvQkFAp7ROr0t0Dd5rjnUQMazKgf1b8+mMfqujjb
gPO+rBMTQW7pKOh9BHLLvS3/uBHkvpY+lZsCu7Vr0g5QTaKTsRM8LPmi3UUbiE1Wz2c7IKtnzhj5
A9D3MW1wDQNrAfOt2HnAaMeX0hKwmp01lc/B9Ktfc90jeP0wrXZ6IUitn9Sdy7DXsaTluRp/dnd3
c3Nzc3Nz+yPe31SNXClAmgqisvhGHALJUyqCAegh7vApkMoYOoMoI2ULBaTawiJqAWHKSmkgcFQb
KK0GkSAKaN+B/KPyQtoLui+yVsXWh4cHtui2XoOrH7/YKrpBwSdla1c0QcnEuoMrXQBnQOy6JxdA
d95znXwF9J3D0yM3gByun+v1BWhO1w37YlA+NlTxnAO5w+0W/VQoeD2sSXQLsB7URuWkQsLON1ZH
VZCDzQfMa8GwUZ+q9ABDYd825tnAQEMnOQFc1bN/ybwI+q98thmfAub0kxnZkLPj8auXpSB3RsI3
ORo4e6hnRAIIT8mHqaAdUUeKK6BdoIkWDtIRuaLcCuRmrgDtM1BDRaijBEhh0iH5MMjd5PFyMshd
RbJaEdBrXzIZHPl0M3wPQ+4oz1+97kPukOh1zhKQWs23VO5oyKmZvSBtE6T/GDf20X5I35bwMtEA
Oc9yWthCQI6Vb2tbwSvBa7R3OATe8LvpPxNM2d5nvQ6AcZdHqGkJ6JabovRbQafI6+TvQVsjYrkJ
4oqwit0gRdFKTAZdCekLaT9IF5Tj0h3AKM3QTwclQl5IJMi3xFKpCWhhWk/lHmgtxWeulqCOsRfU
7JCzy55pvQO2plZZrQi5198GJbYEMTT1YlJLyC7wtoqfE0wfe9X0CwHvj4wVHSngv9xjhn8zuN3h
2Sm7gFpqtEUKh2c/3Vl84RVYHHJPj2WQb1noRs9oqLmp+skGheG635MJj9aA9YTRqq2DwgWL5gZ9
D8Z18gQvC+hS1cTSvcGvtO/aKjXA42xA58DZcLLk5WubVoOanDkzoTME3vCYKY0Aj/xyTKWv4c76
t4cvF4LAJiGfmVqCulGUtr9bvSL2z+7ubm5ubm5ubu/DH0+cB4of2ADUke5JFuARTWkGPKSb+Aj4
iTPyGhBRLFYGgFRbe+XSASVFZ6UsME/K4hfQMmlICdD/pI/SxUHOV/c8rsZCatN72ckVIf+Tijm1
E6H02Obtys8F342hUb71wVnN/2WR5SC2as9zh4KrdXbPrPpgvBS2WfICqbGoJGeB1tQx134GRAWn
P8mQfdTxOGgP2DZnXXFWAWePzA5x34G2xzbCNQ8sJdSvpI/AEKzUl3eCsV8pR7QXSL5sdV0EV6+Y
86+t4DiddCJ9LmjbssyuD8BVU74mXwHXOOchrRyIdNcRloH0OSYxDHQN5D1yF3B+raVobYEVkip3
AqZr9/gGRHVRTGsEoqe62fU58EA/1nM6ZNWX5np8BEnZzjKaBVKFtWnWx5C66M2OuDKQdPB111d7
IU28/SKhHWgX1J9cHcDzsv/GgIUQ7VmkcAEXeJj9FK+boP/ecEo5DK4Trs81Kzh62L626iA3NfPH
zPYgxqSPFFdA3i6mSEbQttJe7ARGy7GSD+jyKQt028GQrPgohUApoWQrGujMiq+8HrTi8h55Icht
lCRugS5Ht1kygqGqboFuHbDRXFLvA54ZXkO8ckArqqTLVcCZ4VomqoI9w1rXVQlyL+Z8mFMCbJVT
9me1gJQFyhzDcTCv8tpkToVio0s3qBUOxpd+Ad6HoOzRogfCa0FwbNjxkG5g2m66YRgIxi6GoWI6
VAhssryuN5hmmpvqDgKBLKc2KH0Jl7eBob2HMaAB2N6KFuqH4FvZ/KNxGpTJLNGp1xh45vcy60UY
5LZ26F8fA6+wQJ13bSjQ2Dv26XzIKuKZm3kdwiLy1fUqA7jTZjc3Nzc3t/8z3sOIM5+rKcCH4pC8
EZhBESkBsEsr6AbaLjFa1YFuOW91DcHxVppCC5DaiTMiCOTOSi95DOhauCbJq4Db/xbWVSM5PaUG
FOpeu331zyB6+LBiH4WC9NyrnMEOuSVf1ntQGtQwW8+MnSC/kGNcUWDaWmBb2QmgdXattvkBG/Q3
pWmgNX+9PWMyuOrb96guyPg5e0Z2e8g88HZaym5wbbUG2LpAcC/fiv5TIWhbQDOvMFB+UvIRAerR
N4tSU0FMKRgTshyUrUabzgc4SwHdcRAFpXyuaFAaMlEygnJYm0NPkIzSS2kSSEdERyJAVNJiXfVA
OS/NEAZQVkmT5Z9BKy1dUj4Cscmw3eM22Pvrv/RSIOVzdYRSA95+k7vF4gOJdeJfvTwDKSuevH14
FFJuJD9IOgFKa+NEYy74fxtROPwr8FwR3DqoJcgJ+keYwdnRct0WCFnPk5+lRoKjq2OwVhaUunIF
fSaYPjPbDG/BI8Bzm9dQ8JjmWc1zHRg/91BMjcDQ3fiNMQN02/Xz9adAJyuV9AkgfaIcwBtENaGK
XJCGC4PWBbRL6nDtLmjLtGMuBbSFrquOviC+cVR0DQEtv8ugPgD0zn2OvqBLcX0oWcGA/JnuBXjf
9jIbZoBrh/ddYyI4WzhtWhzkfGIJczYBy/bcrblj4dm+Cx+erAD23IjD4VegmCt0WJ0GEK6Lmhz4
BWjrRIDTCdo1Vz+zE7x6eNbgOOT0zfG1hoB8Tv5YvgQZa9J6Wj4F0wDTUJMDIr8JmO2dA+o51yBt
AVT4oOzXxVeB7q5pZf6ScLnPnfDnR8CWqSx0TIJSIcW2FN0ENw48ytz7A+Qcdix7vAz4H/Trcm5u
bm5ubm5/zB9OnHVd9P1M/UAt6izobAYMk2ZSF5jPGmkOyMl8Im8FRzNXC4cRHDHJ8972A0OYMcnk
BHldQEDAXXBtdHg7KoL8XKdKNcCwskT1YuMhuHu0Xc0G9TMvu1cvYGLWnYS3oFjlLs6vQX1sXZ7V
BZSwYktrXAd5v2mq7yiglppfnQAiWC1t7wi5vV/WSiwEtmVZn9nygaulLUmbBFyTTvtlg+uEVFqV
4c2r+IOJseAKsCdYjBBWKLJY/qEgJ7l6OpeAvgzjxU4QZSOTgj8AfWTIAu+zIDbb4mxTAb/sW/bN
IAbrJ4iroHusXmARuBo5DqgDQMjSQ+qCGMAiqoLuoG62sTPY7Mbl3tshc4nhmHkcJGu2i45ESPzg
TaeYCZBY/v7qO96Q5Pva8WoScMtUwyMUAlsV8i48GcylA4v7NQVHCWcJ52jIHpv0MHUQqFVtFdVk
MDU2DzFcAd/vAn39fgC/tSH1g66A38iAX/x7g+9k7ylevcG82LOgqTPopulf6hqDckAqqowFsZ5B
YilofcQAloD8oQiSEkH0Zy8tgJGio9gA6hV1svYhsIsOoilwSjskLOBar13XdoKrsbpdbQSap3ZD
PQQiwTnceRWcba2DcoNB7Wgvar0HrvXqMccEcKWoC8VkMHTSPZAqgWmh7xZjL/Cp4CNMEuT+aM/n
GgpvB6QOSg6E9UM3Nv+5N/hfCPgoaBuEzA9uF1QSKsWWH1D8VyhTqvSeAvMh85PU3dJ9cAyU7ruu
wdtbCSdTl4BhhiFI/yuU86ziXzgKpI26z+U2oFi1687VUHxRYV/DYbjz4m47x8fw9PWd/XeiwedM
uWmlj0BdtfSm3ofh1ONLn+8uBcAHf3Ynd3Nzc3Nzc3s//nDifKbuhZGXRkHNslXuV6kF8jVpi0gA
sUIkabeA49JwOQXkctLPShnwWBGQFHwNkioldElOAd8CpiX2S2C4aCgpfQnaGtWTTWDoFJpaeBSo
V7J6Zq8BUdWhs/8M0nzplXQQyJI7GeNAP6xwo6pfg35pkIi8ARy338y9C2KMzlP/Auib+7mWBcoN
+wyhgZyqPDXuBM+tnkmGm+Dl6V0/sCE4s8TnUevB4pG4JK40xP3w7MKdLWDdlpaaUhvCfo4OKvAW
jDet7XKiQVmbGpZmAF2kTyvfB6D1cj513QK5uVxBagyGD0RDORrs8zWh7QBddWW/Mh9c9bXaWl9Q
a2PQbQFXvN9Rv6GQ6nRGahLEzUgekvgdJKx6or8zDl5ffRjyYBVYV7mma/nBd110sXytwLgz8HOf
X8Dp5dyozoaURnGz3kwB+al6jXAIrhtUN7AQhKaVPJnPBaH1I1eEzgbf9f6evr7gcco8zpQBhlL6
FYon6A3SeSkIFEno6AziqtpEVADrE9d09QfQnmgztUYgvZAfywbQrrleqePBNVCzasNAKyv2i2ag
NBLNyQfSEKmBVBqUh/IK0QuUSggpGZSLrFaqgYScLQO6MnpheAWOiaZvzIfA1Vut5goBsdZlcVjB
XssxxTYQXGWtJazVwTHEvtA5FJRxqqRlgiHEVFG+CR6fm3L8PgDrPWsnRwlI65tZLK0dJBfJ8k0v
C9nTc6zpCyHtanLFt9lQ71a9S/VugOFn32d++SGoc9B2v0xwVVdHqDNAF6V3KA5Qm7viRSy4FFcx
+RdIJdmY8z3kjMi4lHAGMh2JU55/Dxee5eyM7QXFxxaLLGmHWhtL92i08c/u3m5ubm5ubm7v0x9O
nLNbpUfba4BulJIlFQNXU7W85gdyD+kT9oP4HIeYAVIXua50FZRGnpJHJJgCAif4TgBnZ8ctZyx4
NvEe65cNrpfqWHU1iDXmG0GDQZdpCvc3gato1tvU5qD/ylTKfBWUauFDSs4D6QV1laUAjk9yK4L4
QumvvAJRRqqBL4iW2jNtLIjd8hxRHgjmM+0TkEdKn7jag9cwuYz1BDg/0SKcu8G4zT9BVwhcjyzh
Ed/DW31Cekw7cB6zJj+qDsFfhh8OnAReTfzuRHwCWpS1l/0jELOktsoDcG50feu8DGK5tlxYQLoj
jRCHQO7v7OL4FaT6utn6QmAv6TkqKARiQ+2PbbEQ+33MJ0/6wqusm09v7IHEZm94NRWUOP8evk3A
97PI0hGxoNQSPaQ1kF78TfEkB+hGaXZlAUR+GzknvBzkjyt2uOBnELw5X1L4CvDN75vtdQJMV/QH
DTuB9axRGoLaUlXVVyDP1uoKDVwTGEl1sE9X16n5QBsjQjAAjSR/+QcwWHQ6OR/oBks9yAUtUPpa
Gwmus661SmewjVLvqyXAmcl0cQRcndWv1f7g7KgZxSlQNstfSdGgd0qHpC2gltSechDskprs+glE
GaoyAqQIsU2qBMpF3QbT9yB6Sx8bzaD00z/1SAB9ruuC/XPQL7fWtt4HV7w93X4PdHXUh85WoG9v
LqFkguEL01EfD8jenJtsHwJvWiXsSooE21j7ZGdXIMZY39QJ/Bd5feVVGrIzM7bldAVrHcvonJ/B
nuCo4/CE3ME2f0ca5L6ybs6tAG+S3+5NbwOWVZZ2yQfBd4zvLGUaWIvZw9XmcPfDh5XufQvJu1Ma
vikIdalHnT/Qv979gEdOTk5OTg7U21RvU71Nf1suo1BGoYxCsK/dvnb72kEvSy9LLwusrrq66uqq
MGTIkCFDhrz/D5BVq1atWrXqn4//R1/v5ubm5ub23+kPJ87Xf36h3XkG0fEPW0auhEolyo0sNhFy
itsm2n1AacAGMQNYS7w4BK7ZTovzBvh18FnqvRPYJU5JX4Ejy9nQ9SVIIyWFEyA1U84p5UEEslT3
FHSbfBJNRsCXRpIetENqH9UCcj9KOZoCQ6Re+n6gPRBz1TMgH+SR9gbE1tz8qa3AviU9IzkG7K+s
Z9LTgCYuV2pbeLzqdcnn8ZBaM7F7fDvINyvky5Aa4L/Zf3akCple5teexSDdz9VHegCujm8apC8C
7yGWwdlW8K8Q5Bt+Aow7zNV9zaDVUItqq0AKFqGSFaRnjk7acJAX6Gy+zcFy3Le59wN4MjurQVok
vMy8d/T+anjxyY0dV3MhO9n23FIaPGIjN0XlgqG9X3/Pa2DdmHkl+zloRXNq2H+AcFtEvYjvoHDP
0qWLxENUVP5XUaPB+4TvEJ9jIDdXDsvjQfpSmsBOEJHqae0ZiA5aX1cBEDv5ktbgqip2ieEgSvOK
WSC9kfXyKRBdNW9tOGg/awM1I7jKso9LoDsgvWIu6GsppaQWIPaKUa4DIEo5TovG4AxVx6gXwJUp
7roKgniu3SAepKfqRPYDgwmXuoB4JSS8QYwWWaIciLeiicgPIleME1dAbNEma71Bmo2TvuC6Kt5K
PiD6Kt8YI0Au41HOkAj6CMMz+yiQ7zl+tfUAnd6xwV4NlADHNsfXoN9tbm/whtyHuhH6mpBuzfox
2wkHGh3SnaoMui/0Z8xrQX9KuaqMhNyxWWcy3kL6nLSbKUVArSHFO2+D5qOVdSWD64pYrVsMhiuG
XVIlcIVoHp4B4KfzL+llAmkbzdQ6kHQp7YfM8UANyrD8n+9fRRYUWVBkAfw85ecpP0+BOhXqVKhT
AeRb8i35Vl65dz+5XWheoXmF5oFkkkySCQZeGXhl4JV/3QfIwAoDKwys8Oe9/l9NXBPXxDXY2XRn
051NoUt6l/Qu6b//9dcrX698vTLcunXr1q1bIMuyLMt524ufLn66+GmoVatWrVq1fn/5ChUqVKhQ
Ac7bztvO2yBlTsqclDnASlayEsKmh00Pmw517te5X+f+3/+FxKMFjxY8WhAyjmcczzgOXQp1KdSl
0D9+vP76Qsh9YeTm5vZ/zR9OnF9uSOn99Byczn+raoAFSn5QfHvkANDlyK/khSB+EG2kYkAnYmgA
OHiEC9QzmlHTg1RPWsAwkB7KXzMO2EW2FAAsozQmoJxop60EsUhapCwHXGKu+ino7nFMlAdxEIv8
FMR90d7pDfr5+qOeHcBpSu3xsi9kD7hQ5NRsUAsm9UnqBOKGejq3IrxofH/Z85Jw44uH69/4gbTF
Xl96BL6i5BjvgqB/qZxO+hDUyXh5lwaD008J/xV0V3WFpfOQucN1NK01ONZlBCRbwN/Tuc46GMwn
DGvNd0AqqQYaRoLutHel4PmQVNcrJWABPJiU8PaNDp5fuSZd7Q1PPO8dvp4KjijFadCBz9f55+TP
ATlNFywNgKxlb1ak3gJfxaOauREUz18zsuIFKHC2xIRCCRC0NOBs4C7QT9B/qO8B0n5WUR3EQlXS
KoBI0xJwgrCKQcIMssoPLANlCvMlDdSvpM18CrTUlmnfgfhOBGkRoK9GK6k3iMNSaaaBXEa7JwaC
uCS+YTuIg/TWugBbRT6xCpSqciGRBqbJUrCSC/Yv1cOiGrhkjEIGbbG2UMwG9ZT6ufYEtLIUEAag
ptijaSBaiWlSHyCVtuwAaZ9ow2gQjcRW0RLEj8gEgDpP1BBRQBuRIiWB1lrub/ACKci4X5kJ+nJK
OX05EAelD3InAOOddVy/gDREuk1NUG4pu0zTIPOcJb/8Kdhvq+Oc18A7yPeI9yMwzPVUPcqD/YCk
Kj9CZsm0m0lm4Kl8T64CYqeYrAaAtbNtr2sQJH2bci5nJBjPGwYqr8Grg08j80LQ3og96s/AH0xa
fXx8fHx8wG+c3zi/cfC6wesGrxtAfvKT/y/KvUuc656oe6LuCaAVrWgFP9z64dYPt2BItSHVhlTL
S2Rq3K5xu8ZteOr71PepLzSf1HxS80lwfP7x+cfng7WUtZS1FBRMK5hWMA1u627rbuv+NgH6rfjl
B5QfUH4AvGz6sunLpnkXAFWqVKlSpcrfvr5RQKOARgFw48aNGzdugBgsBovBoC5Xl6vLodTZUmdL
nYUKyyssr/AHLkR+r+fbn29/vh0eb3q86fEmSP8q/av0r/7xOFkns05mnYTmC5ovaL4A8s3MNzPf
zD9efn/b/W33t4X8KflT8qdA035N+zXtBxSlKEXh5rab225ug0unL52+dBrqUpe6/0U9X058OfHl
RBicNjhtcBpQiEL8E4mzm5ub2/918h8NUHCQWRc6Fl6LV1cSJsEvF/cfO/McTIcNNvNXoFUXTVkK
RBDPQ5C+khZJiwAVF04QA8RkfgRpmTgqVQMJIhgA4oQoLD4AaaK0QXkE8gZxXOsJ3KYYK0ArLi3Q
vQEaajtdnqDtlPwYBWpxS6OEueDYnzDi/nSw1o3xe3QYtM9cEek7gCyto/0omNZ7lTatgdqDajao
4AE1HzVy1fMB44rgnMiKkNLGttZzH0gur/n+28DzpdnLYwLoVK/PvTaCZyXvCpHfgFih1A0IgMxv
MgtZfCDjI8u57J/B/tDjc59KkPzGu53/VXh47k29VwZ4tPZsudOP4dH2m4uuhYGju/GIx2Ewh0ce
Df0AXNUdDrsK1g/eNkq/B4W+jjaF7IGG1ZrNrd0KKpytdqv8DxB9I2JYZCnwemmYZLSC0lw7q60G
3RFRVGsGpsVyT3kV6CtTWP4OdFXFl1IVkGJFc74F9qlz1GDQfaCdVSNBiWWe9hiMHyid5U9AL7Nb
hIH0hWu36xY4Njj7u7qAdYjzR1ca5I51Kuoa0MaIFeQH40O9XXwOuv3SQdcgkDtqDbTjoEzRzrgu
gBIkZFEUdFflnuSAclHuJnJAOi8FSaVBuiKNFjVBDqOxaA+6D+V4qT8YNss6+QnoG0kxUmUw9pTW
SO3AMFDqRjAY5krXRHtQQqXu0nBQzusyjRfBIHk8814B5j3mlh5vwWOmvFkqBeaN0rdqH/D18Kqu
rwzeH+lylE2QVSElOuUB2Cvas6zHIfR22KTQBxB5JqJq4dUg3xGXTb1A/ow1whN0fZUZymWwjXQM
0DpCervMqZZ7oN5SW6ldQXaIec7I99dRi2YVzSqaBc+3Pd/2fFve85knMk9kngBnf2d/Z38IfR36
OvT174/bqVOnTp065Y1cFk4vnF44Hbp37969e3fwfer71PfpP17fyBmRMyJnQLuEdgntEuD2j7d/
vP3jb5e/N/LeyHsjofLKyisrr4Rumd0yu2VCh7cd3nZ4C1cHXx18dfA/Xg+bzWaz2cB5yXnJeen3
v877sfdj78dQpkyZMmXK/OP7fSf7VPap7FPgNdZrrNfY91c+sX1i+8T2UKJEiRIlSgBDGcpQ4AY3
uAGlraWtpa0QMylmUsyk345zMutk1smsvMf7I/ZH7I/IO27Hjh07duwYbHq06dGmR7C14daGWxvC
8cLHCx8vnFfu974Pvzfe7t27d+/eDSnRKdEp0Xlx9u7du3fvXjhz5syZM2fynn8y9snYJ2PhZNGT
RU8WBYfD4XA44PDhw4cPH4Yt3lu8t3jDwfYH2x9s/9v1fnfhd2fEnRF3RsCuSbsm7ZoEL8a/GP9i
POx4sePFjhewzXeb7zbfvPo/rv+4/uP6//x54ubm9r/HHx5xlg3yao+B0GBnBWOd21DNXCm9UDuw
Oh1P7W1AjpdPSkdBGsF2kQPikHghagC3ucxFYLY0RfoCxHWtlvYaKK7FkwX8JB+ScoHWfCJOgHhC
Fakv8ISbYiKwhRxxHbQUqZ9kBHmLa0GKD6SOO1B93a+gWS99db8MmH6sualadRBFvZv5DgQp6X73
W4D/EuMFwxLIrKwv698UHDuNelMiOFMdUzy/Ay3CVMfQEsz1DJpxBOjq66Z7jgT1U7537gRDY9lH
GMHw0KdPwDLIDbA8M7QE61JTTWM9yD0f0Dv8R7h76PW9uFJw76MzD8444bn58cxnJnCW9rnqMRA8
iwZU8f8UnJ2yI23FQb9VO+66DeWWV2xeGigxrPyK4nEQZYpenu8keCzRddJPgJyzluGWNWDvJoaJ
b8GwWVfOcBxMM/UHDCXBMcle1/4DKLkY8QJluhzAp6BZNaO2A/hFmiqKgKOMK9DVHbRJ4jx3wNZC
9HetAhGgmoU3uJppjygL8nNpijYRpHxaPrEBnDGiiFQDlOpSAVEQDCv1rUUayGmMFDNBCaS3eAJK
jnxcag5qK9FQGgjOymoiGUAVMUi6A9IONHUpKMNpzV4wHNI1kheAlCaNYy64vlcfaXdBmqFCXdCe
iQ9FTdDq80QygZwh1ScB1PZcxgvEBXGODJC+k27JkaDWNQQb1oLWmX7SR2A02R7YrIDdMdX+I/DE
fENpAiKTNuyH7ELWJpZXYMQsjC4I+TjfipAFIO1Vuhm+gLdj4z56vABctwi2HwR1vnxYqJBrzj2l
tgTbLqvJ8QA8cpTBcsT766iFvyr8VeGv4Gro1dCroeD6zvWd6zt4OfLlyJcjoXD/wv0L9ycvgfo7
SpUqVapUKZCqSFWkKvBG/0b/Rg8NFzVc1HDRX+y3W+FuhbvBmTtn7py58/vrG7EvYl/EPpAfyY/k
R6CuUlepq367fPt87fO1zwcJ+xL2JeyD+7Xv175fG1KOpBxJOQJis9gsNgOVqESlv7//5I7JHZM7
5iVautu627rb0CW3S26XXPDw8PDw8Pjt14dMDZkaMvUvnljFKlb93d3+jXeJ8Olrp6+dvgbJ0cnR
ydEQtCtoV9AuqD+2/tj6Y8G/iX8T/ya/v3xwi+AWwS3ghuOG44YDKpapWKZiGdA0TdM0uH7j+o3r
N8A22jbaNvq369fQp6FPQx94ylOeAm0j2ka0jYBjXY51OdYFPB95PvJ8BD3X9lzbcy1ImVKmlAlX
GlxpcKUBnC99vvT50tD4eePnjZ//9n7O9T7X+1zv3x8vyifKJ8oH3rR90/ZNW/C/4n/F/wrk5ubm
5uaCva+9r70vkE466ZCwP2F/wn6Iehv1NuotXLt27dq1axAREREREQEtsltkt8iG++vvr7+/Hi71
v9T/Un9osKXBlgZbfrve7y4s19VcV3NdTegc1DmocxD4ZPpk+mTmfffg3YVncYpT/B8/Tdzc3P4X
+cMjzo7rhmfxFnjmGfvF0dbgXcyrl1dFkK+ISdoukOzivPgGRE9xCRuQwyteAA94xjOQv5cuSyPA
Ucfx2tkd7DucJZ11QdbkSvIbEDvEEhEGZJEl4kCqiB8ZQFnxnHiQP9NwypCbcaXo6UCQ6qVn5VYB
aXipVhVc4PNZ47s9N0GwpfWhgR+A7+AW0Z2LQ3Cvyj0rZENoasAq7w/A+DnrlcGgfmw65aGCsk13
1RQLym7da7MA+xXNyxoOak/H5+pZsLexT7AUBltnS/OMXeBVPHB4cDVweRU4X1KG+4Y3X7+pAY9W
n91z5j487/q47qOeYF/ovcf4BExPfCr79QBnp5yQ3EjweqpMkptA9VE1Xle2Q6Vfay+q+AtE9Yjq
lq8c7DEcrHbwJaxK3Xh3/XL4aeS2LVu/gZVea6euXQkn754/fOYjeHMy6UzcD2A4bPKR64Fs1p3Q
TQTXNe20+AI4Li/W9QL5rWGMfjjoPzQ1028Ej2OGD/RDwDCEsdIFkB4Ib3UGmAbJOeIyGBrLs6Vd
wCfiqigKan01v2ssWLe7vnEOAuu3trmuCiAPFnWlMuCTaX6tXAfTPL1Oyg96vTRRLQeGotJkdRl4
VFd+JArMS+R+0l3Qb5Kj6QbqTvWpugMc3zk113VwHlYTtY7gmkCW1hdcc2itxYJTFUNcGeC6po1Q
u4HLoi4S28HVWrTWfgFHW1FPJIErSYygKMivdZ76bmDYbPrawwNMT41nTZvAYxnBojSYUkyrpXbg
HWKKVyZD9sn0xqmPwTLOciy7LvgdDhntcwAK5c9/rYAPmCrpz3pbwfDIONUjE7Tp8lBTOcjZkDtM
1APXINdu87T311GNPxl/Mv4E4fHh8eHxEBscGxwbnDdFo8jxIseLHP/98XQjdCN0I/Iea1e1q9pV
kFfLq+XVec9LQ6Qh0j8xN/Wv52D/Pe9GBp8+e/rs6bO8Ed9KgysNrvRPjDS/m1rxbqqH/YL9gv0C
5CzMWZiz8A+/HX/fv881fpfIvZtr3G9Zv2X9lkFUx6iOUR3h1KlTp06d+sfLN3rW6FmjZ5DSKaVT
SifY8HDDww0PYWfgzsCdgeD9xPuJ9xPQfaT7SPfRP17917+8/uX1L1BxUMVBFQflXWC9G9GucLnC
5QqX4dXPr35+9fP7j/fuOLxLnJMPJR9KPpR3J0MeLg+Xh4P1nPWc9RwkzEiYkTAD8uXLly9fPoiZ
GDMxZiKU6FmiZ4meefUoaSlpKWmBuNZxreNa/3Z9//rCMmJGxIyIGXCyx8keJ3vkzUF/lzg3b9a8
WfNm/w3nlZub25/uD484l20VtbXmBDAI+UGmH7wpluiR2ByKli2yqeBtyKqa0yF7JOiP6R/qRwKf
s5FKQF+CqA1cFJe5BpkeGRFZ+yFgWqBngAW0rqKUFg3SZilCGgmki8uiFog7jGYLSNvlFbInuBpn
lk5WwFovNjz+OjgT0gKtNyH4Yt/lA3aA/mxwt4jb4BxhT7Vbwbgp/5HSS0D0s8+0XwP/LlVm+KWB
x+QLm542gVc1Ys4nrwDbaKLlGuCq7AiwnwDDXoO3sID81vlcjQZpv3rcvgSk8kJIG8F2wuuA54fw
4nXSw6RJ8Nh+6fMLJ+BZ8uMVD76ErM4eS41XwTfJq57XMpBTrA3tt8HH5tHKNBUiHhY5GjUQQr8q
cjLfd2C4rd9mHAq3H9w7cr873GvyKOd5bXgdH3v6jR2UEcom/WuwZaovHV/BHf2jD15kwcFvj9Y8
4QeVd1awlB0LxRsUeVgoF5SPdAUM9SBxYGJuYh0I8graF7QYdI3FM30nMM/Qq6oXhJQMnRXSETwf
mKf5VwXHx/ZLji/BucsV5joAzi9cOVonoL7cXJkJynhRWxoAcoDuU50F0pJyDlpKQmbDLH3ySfDt
4v2R3zIw7DAuNaUA9xQT34PrM1cF13pwznKdYyOoXcQAsQ60T8TXJIPaV3yBN7CXp9p3oH0mEBcB
K+ncBT5ltGgJck3Rj68BT3FENAFRiAfiHEhlhCrKgDpEPBG7QLjEWfEI5Mnya+kESAWMxUxDwPCD
lsEJ8Bpkb2E9CiLZUIQNQEERpJSCrDupMcnrwLOp/yCXAP9FAe38SkLoUXFWWgdJxxKvvD0GjhQh
LEmQEZBVyF4RtFf6jzz3vf8OW7RH0R5Fe8DN1TdX31wN6hX1inoFAuYFzAuY98/HjWgb0TaiLTyd
+3Tu07lQkpKUBJ5tf7b92XbgDGc488/H/3sSExMTExOh+/Duw7sPB3OKOcWcAnFxcXFxccBBDnKQ
/0gw/97I+rsLCavRarQawVjLWMtYC0JOh5wOOf2va8d/+Pf61Rtab2i9/6Se5S6Vu1TuEtyUb8o3
ZWAQgxj0+8ubfjL9ZPoJWula6VrpQFIlVVLzyr8bcQ8oG1A2oCxQjnKU+/3VFyvFSrES5F5yL7nX
b7fv3Zcn/178fzReSFxIXEgcpD5JfZL6BN6EvAl5EwJhxcOKhxUH5ZBySDmUN3XJuNW41bgVTMmm
ZFMyWG5YblhuwLpr666tu0beHQMFBQWkc9I56RzQi178J/X56wvL5oHNA5sHQuonqZ+kfgJvD7w9
8PYA3Hx189XNV8BhDnMYWtKSlv+yk8rNze1/gj+cOMfXSf7i+TFo5lE7uq0C525dfn45BGxeru72
6lAwNp8aXROUYLmXshfoIiqJLaC9ZqM2CrQyapZrN9BQ9NG+B+kjUUEeDfJiFspTwLnTtd15E+T8
cpLSHKQIKZqBgFMyYAZe2xZbRoHoar1qLwYep8qXrZYLeo/w0kWqg/badje3G0gBym3jKRAfY5GX
gcs3NdjSDoylwvsWqg7+HWpOKvkLONdnf2ULhPTI7EWuQUAj49e6NNCaqj6OVsB4Z6HMI0Bxta36
CuxHIroWGA8v92a/theHZwUuRV44Ac8j7nW9mQ1pQ/Ul9SvAo4Up29cEru+cvRwlQD4g35BegLLZ
Z59+Gbyc9mZRTEeIO5X0aXwW2PbaSrm6QfyexF+Tb4CtlLWMozLo4uQOSl1QU0RTRyCIVq4McQNc
YUIv7kPGzuxo+4+w75cjB0/1hwuWy5nXaoL8XP5OZ4Wcfbn9cs+BXFv6RCoB5ihToLkmiH1sl1qD
T2vfix4lodub9t5tqoK/j++ggIFg6KKvavQB/XrDNkMtyBqRvSAnGRwznN840+Btw5QuiSFwpfK1
OrdGQOrKtFGp/hB8OrR4wGswZZmKmH8FzxzTZrMvVFDKVSvnAq+uRl/vi6De1L7UWoDWih5sBm2M
mKEVA22QJrMFxC3RXJQH6WNphHQKtJHap1pTEL6oPADNU0SIOqAdEf34AKQYaoimIA3V1jMEtIEi
UCSBWoNqYhtojVkjckC2GOcbLoG+Kt3V9eBRw1rF9hGIzwyT5Hxgrq7VU/qAVcpMSpsNcq5xjr4w
RHTIT2hpKHm4wPPID8FnpuG2eTGYP/AorfcFD13oyoj5ADT4I6tq/LXo6Ojo6Gg43eN0j9M9oNzc
cnPLzeV3T2H4LXXq1KlTpw4c9zruddwL7m6/u/3udihUqFChQoX+YiR6CEP4F6yOUPVm1ZtVb8Le
2ntr760NpmmmaaZpeSPsweHB4cHhcKnNpTaX2kANalDjv4j3bkSyPOUp/5cbSlCCEu+//tk9sntk
9wDvLd5bvLfkTbnYG7Y3bG8YdIzuGN0xOm+KSGxQbFBsEAS/Cn4V/OofL39m8ZnFZxaDT0Ofhj4N
oerKqiurrgSXy+VyufKmKpTKKJVRKuMfb09Uh6gOUR3gdvXb1W9Xh6pSVamqlLf9VsVbFW9VhOge
0T2ie7z/eO9WEwmeHDw5eDI8zP8w/8P80H5/+/3t94Nujm6Obg5c6Huh74W+UCy7WHax7Lx4745L
o22NtjXalje15d1xjvOI84jz+Pv1fmdH0x1NdzSF1otbL269GErZStlK2SCqR1SPqB6wK2ZXzK4Y
4CIXufj+zy83N7f/Of5w4lyqbNGWVaZC7izHk+xL4D3G4675Y0jeHr83+VPI5xHi4x8PWR9aj0gd
4ea0e7suL4KgWr4xYYXgUZXXtc93hgh//zIFmkHk+ZzTxXWQP67IzgLtwLhGn24aC+KBlKvFglNS
n7hmgP6lSBd7gVGyBS8wfJtvdqgGXsbacxu1B1cLOYD7IKs8EPuAYtzRgoF2xlwlFXT1/Rv7A1q6
vqTHUDAHFL9TfAT4FY+fnZEBWuuzl687wRqr/SLVBteDnLepAWD5JPuFMwBcawruL/UWkr/ynOJT
El5Nva2/ehRelrg974YFUl5oE+kPuqNez7zmgsGidGUzZE3NrpAzAtLrq5dsgyB+XEabt/nBNdLh
o60FR3m1jLYPlDjDFIMF1IJqD9UC2iBnJ5cN5KXyHSygbXQtc7UHtaU4q7wBclDUZ+Dq45yjpoO5
qqme1xawVLeGak1BHem05Y4E00DjLtMP4MrU+qj+kOWb3dyqAzXT1UZKgaTSqaasBrBq9PqM7e3B
Z5xPCc9zUHZv8bji/UBdrq3VasGDF4+8Hp8F3QC9RW4A1mq2D2xnwUqul+MEYBYl5CGgdVaayyfB
ccrxNH0PiAeugY6PwVDMmKrvAIUd+V8XGg9+D3zvBcwCMUt9qA0G6TaSOA/6ZUoXXTNw3VSXOCeD
1l59S35goXCJ0iDsnBZLgWYii0CQxuEt+oP2pZgmrwHRWktXvwXpMuWoDlqo2kKdB3Jd5Rx3QJ0n
nRFZQF+9YvADfQ9toLYbzLG2Yc7ywJeGEPkmaLtFPd0qsD5OL506H+Qk790e/aHq1LrLKw2EKm+q
Vq14EzgnlaYSaNGiGPfef4dVqinVlGrQr1q/av2q/f3yf70Kxm8tC5ZaILVAagFoEdsitkUsmD4x
fWL6JO9W+CPTI9Mj0z8f//c+XyazTGaZzPd/3P7VdjXf1XxXc+hHP/oB3g28G3g3gCr1q9SvUh/2
3dp3a9+tvKkj77Y39G7o3dD7Hy+vH6kfqR8Jp1JOpZxKgU2PNz3e9Bj0t/W39behZL6S+Urmg6Ld
i3Yv2v0fb09dj7oedT3g7PGzx88ehy0pW1K2pORtf5fA191Qd0PdDUATmtDk/ceLSopKikqC5NnJ
s5Nng1dxr+JexUEXr4vXxYNlsWWxZXFeOcIIIwwaNGjQoEEDOPPhmQ/PfJh3QfFurnuthbUW1lrI
b444/7UKAysMrDAQ9obvDd8bDtI4aZw0DqSOUkepI9S7Xu96vet/6ino5ub230S6dOnSpUuXhKhe
vXr16tX/+UBakGuQeg1SU9PWJl0Ej0HmZ3574M5PD1+cHA2xrlhHWk8orCuypdQxSOyS3fH5Xbg/
70Wh08EQnuK5LioMXhdKmBR/BFrE1jnYpxh4h3q1Nd0CP6PPC/8C4H85aHrIS1AXieZiOqirUs7d
fQxqmpqtqwKGCeHbS08D+ab9hSqB+kiZqo4BIUtl5EWg81O/lR6D2tvYWi4EumPyFuUWWL0err15
EzIL7Q08FAdvRyQ2yfwWsivYl+Q+A0dM7nhDJOgS85ctYQU1veLOUgHw/MDjubdnwe2wI/l2jYSn
V5IGZ1ggt76H2fcc+B7yDPD8CuzdrOuslSGlYMa01HZg6eQIsD4AXVt9lv4+qHYtRZwGXWvddUMb
0KbLtbQUoI2qF7XBMd0+yzkNxBFRT+sJUoRUE3/QwrTjogQIbxHMbhBZ4rgmg/xE7iw1APmxvEdu
B/IFeYBUFaQp0hKpF7BeMtMLHGMdb9RyYDiub63sBVUSb7TbII0RzZQmILmkL/kVpFApSusLLm+S
tCzQJct2XT0wDNJflKeBOkc9IZqA/FA6qkSBtskVKc4CHZktdKA/YcrVbQfRU9usfg4FZkRXzHcM
QveEhgRvgXyDw46GF4fwtyE7w9LBaXUO1z6GTFtm4/TdELgqcF7gHZAMUoa+J8jl5Y+1maDeUTe6
roHQi9b6ieDaqNZ0+oD0oZQkLQJlv3xGtoGzoWOKVhKU8roSWiWw9XKuEtdBDJIM0gHQraKmNhAY
7mzg6gOuyfaK9ttgXePQqePAtkZNpwhkD7DPcPYBvcs02vwpFFhZoGDUeagTU1ku/zWU6lVqZdFl
oKR4tjPcAfNHhkjz/4JE8P9j763js7jWhe1rzcxj8YSEQHD34u7SIsW1aLECBYq0QLHiVipYcYq7
u0NpcXcvTiCQEOKPzcz6/jgnX/avfXu6Kezd/Z431z/JM7NmzT23zNxzrzUzPyf9nPRzEtiX25fb
l0NpWVqWlnBx0cVFFxdB/Dfx38R/A3Xq1KlTp87b7+9/G1u3bt26dSs0bdq0adOmf7c06aSTTjrp
vGtOnz59+vRpULt37969e/cxY1IfqnhTtv3889hpZcBl9ZZzbgVRSznuexvu82TQnZtwLvDGr2fW
Q9j3AWaeOKi1svrQqlnhhXze+Gl/eNrgWb2HheDVvLg5zlCIGZBcIroHaPfFnthIeHr3+fzodWC+
73zl/ARyzMp+L2d28BZklOYDah+zn2sWWLPbk4IfgnlCreCngPBTrfo3oJhqHp/pwGPxOSuAsuKg
boB39u2hZ0pCfNPj+366BfHF1vfdvQdiB/2662UgeFzMDqkOSn2fptkGgbVMlpH590FQm4oFiz+E
l8rrhMe/wNVPD+l7GsID5+Psz76AuN7aV76PIXCGr2m/CHKiXlHfBa8PJfaIqwKJ51M+T6oNjFNv
ij6gBSn3xD2w9bNu1AaBaCuu6ydBuSJ3mMvA28r7kaGCXti4oTcAOU0Ol0vAOGbc1j8BdqOaAsRH
ykccAKnI62Z5YJ/8iSgwr5onzLxg6tIhc4AxSQr5Aehxxnq9G8gK8on5K1iOaAVFJZBVxU/yBsgr
spZwgVxqNDG6gmk1V5ohYPpQgvbAXrOFeRoMaWYxV4EZL7fJNSBD5QT2gZnJHGvWBbOC/Nl8AuZp
M1I/DDKL6KtGwMuPoqcnnobYVrFfvtoBnvreds57YJzWQ7yREHYs7HF4Dohq+2JhlAOsi2ybbf3A
EmFpaA+EJ8uftHpogLJSrSIuQnIuZznPWrhw5vLmS1MhJnfMuZgqoBW0rtSWgm+Mb0F7W3iZNSYm
riKc+fxCiUsfQsycV7WjNkDGXzO2Ci4A2nX1uiMWiFL2KM9BzUkBsycYQ8zF+kAgUr2t/AjOCq7h
nitgXNT7GL9AzJKEOYkx4MnnrOF+Cn5fGnZxGwK6ZAwMGf7mcfXvJuxU2KmwU2nvaz4x68SsE7PA
3GZuM7dB1biqcVXjwJbTltOW8++W9j+P//+1cOmkk0466fyvJDIyMjIy8h1M1Tjz49mAowIersvR
4EoxsA00EouPguCP/FoEx8LLca4n1y9ByCqPEtwKHh16NOPBEYif7b6faMDZ6Q8PPakKWWJtN4Mt
kHdLaKPiN+CF+rJi8gKwRdr7xe+G64VetjoTAIVG5j1RuCIE9cniyX0MXHO0b/3ngOknP1XWgTpZ
lDJOQkqea8ruLmBZmqFX7u2glQt4FHwLXCeeV//VBe4bD0tEBYL4WQv1iwbffNU9tctDgDejM8t2
sI8LaR/cEV6vOr7rSn4whwcPD7wNzxUze+xSuLf3TO0TMfC0/6PARwkQMwhDPQ0+YT6H7CawTMwV
OiQ3TyqfeA+SwlMCk56A8rn1O2UW2OfYd1u6gBxhRMqX4GlvTHL7Af3ZzyugndldfADynllQrw3K
APE+08HoKf9rbu5MLatSCsQw4775GdgG2PKJuWAmyepqLKQkJCfpJigp6ncYICdSV7kD5kDjrnkO
xOecV+6CskIsZi54c7rjzWgwblGSQsBBbumfg7eSeULWAy2OH5UWwEhWyiJgelkvq4CYZp4U50F8
L14QDCKWLGYhkE9lPqqCLEJvToNSQv9QdActwBJkfAfmaVlFzoKkDMnopyFq5YuSL1aAj92xxNoW
6HbvmLoR7P18Gvg0g/tfP8z66DJ4NE8PswS4rrrmJ34JSRuTqod+BC8evT7+WoHYbxO/i1sBrE0Y
oC2AB4UiZz22QYmj74l8OyHyyJOpKfsg2v917tc1QNSNXasPAqWJOl6eBLWB8qXNH7THlr3yKuRw
h7/MvAXMDsw0coAWKQZrI8BeQzsq8kKiHj8tbhIoX/ocdXwE5xNvtbz/Ah4tf1zk2Xj4hCIJef/u
aP8n8K3mW823GjSlKU3hH/75b7KSlb9wY51OOumkk046/5t468TZ1d5WyaPAw69iOr6MgpB2gT1P
9oF7ox7fdupQ7Ezo/VqhcMBzrvG63OCpb/xkboDsZAvIXQsyBWo/ZQDqNizdq2EHqLGulrvOAXh0
4lHp+wHgPuG+ldIPXMRlNWqCt5t+0P0l6FflaI8OyiPLA/9yQHFjh/4FiGxihLsqeEJ+5c5UeJW8
dsaOFAit3TZrlxxgn5k7Z2kH2HbmquSTBOpVayV1InBSKaY9Am+f2PzPYiEp87l2p0eBVtW6MVGC
cSDzrYgu8PDuxXmXdsOTUtdKXckJL3M4Z7gPgPzOEeD3AmyNravVHyClRErjpKfwqlbi6rhfwHNe
z2McA/Gd+EmtBZ5IVybPF6A3864xCoN3gZlfLgG5W8aLFSAzSJNxID3SafYE4RRtCAIRq7aVo0G0
ZolYBba2ts9UfxDVzZzUBqmYwUY+sM70uadcAL25e4VRBsws+kMjErRILbcoA3KV7GycAz4Rt8RI
MN6XsfIm6Iv0CuYikH3oTxsQ/dUQLROYleUYKUDZJ5eJcSA3ie/kFyArm6PNisAMDvE5iNcim3gB
GGKj+A70BWaC2R7UWAao5cCs66nvPQCqZilMf1DjtRbaTnjdJz5jci+4UP7yrBvXIOe87LcS7SB7
ymvW5vCqbezj2BxgKW8Zox6BgLz+X/nnBM9O7x4JJCYlF0qIh2RvUuek42BMlFNYBa4j7sDEvHCs
zql6idNBTJPV1NEgj1BQLQhKaeV7JSPc6/7gZuQNoKYYJ51gjuO68QO8zPyiclRmyCOyNghvAQGf
+38RvhVEAbWkVgHQ9VtmO0gMiM4Z+zlwQBxRD4H3I88rb+pbBgb83WGeTjrppJNOOum8C94+cV5n
jiQIkoe/CnbFg8V47bRfAlsD3zlB5eGZv6h7xQuW98K76g3AaTc2vvockla8sARFwqfxzTP0HgF+
Taw7fduDmMAscyrk6Z67SUE3xDxMmPTMBy7cSHy9ezUEbvKOL9sRwguoxazvg/u1Z7OeCGKpZrd9
BUZPlhg+oM4I6OafAkErKn9aYR/Yfy5Wp3okiLKm1VseZAfziH4DzA3ewgwDz/svyt0cDfENdgzb
5g+ednFH9UzgP7/clur14bkjeVRCAjz2nh94cgxEbYy98boCpBQRz5TmELDaUdg3E8hA/ZlRBxLP
JmVIXATuy8Ypsx/IFTwVt0H4mDfNDSDride0BtNfzuMjYK4sQRaQzeUd2QtEJfZxA0Q1WuAC+aX8
SerAInMofmBeZ6acCu57en89CbQnorjiD6KzeA878K2eUa8EpsW4LzeDvGYW4zqIQOWxkg9kD3lK
rgc6UFKJAONXmdlsBqynrHwGakvRXREgYkQXuR7MZtKXNmCUNeKNk4CkoNwE6kQls9oXzCmytTke
5Aa5RY4D8YNoIDKC5aBow0XQelka0BfIj8lc0KeYpbgF7pLuJGMsyAdmL1kTRB6xQakAd/b/Wulp
FOguo7eRCdShWkP1DCiJSj7lZ4i1xC2M/xiyWiJmhjWB1+XiX8VlA72NmUG2Ac8J9wHva1CcajG1
CXgyePq7zwHNzJFiKih3lQvqFtD8NKFsBWWsqMAqEFfVbKoJ8kMZJTbDy+2v1ibfAMe31sWvcoJ1
iGWAz0WwnbXFBGYBadXClW7gTnBvdzYDZ+WEIfFbwdjtE2GtCGwk+u8O8nTSSSeddNJJ593w1olz
wlev6qeMgkznLc2LFIMeQY2iB7UF6/3gBd7qcGDxpQJrpoO3g09b11XwPWwPSm4MG5qeGDR9DHQs
7FPk88fg2pOyWZyEU112vD5kAZ/bvvNDNdCrKzuNCZC3f8j5PFfg6Zz4FVGFIaxg4Iynl8HPEdwq
PBLMhuYQYxEoG0Rv2wmwjItYnLsvKN/71wtOBoYoRaQAedNz2FsTZBnlgHYEcGmr5CvwpjxKvrUI
PDNeToo7DurwzAkFKoMnKeSSvxtu9/nl58Pr4emSBzvv9YOX5fWcZn7QZjom+bcCdSSfyOMQfz3Z
mXAQki66SrkGgKWNzVQPgn5FL2ocBsWqJIhzINuwxnwN3k3ebcZXwH4miSegxmq11b5gFjAK6sNA
H6+X1INBsSk9lSBgsRwsZoJ5x8xtrgfvYTlS7gaPlMsxQHEo4eIisJrL4hcw15r3zO0ghssMohh4
X3uG6UeB5qKk2AOUE0dlCzBey5VmFlAHqHHKbuC8GCzLg9nQ+NQoDbK27IAC5hJjpZEN1CxaZ207
yPXyiClAqSwmshO0rFpt9Q7IQTJctgd1n7jB96B+rs3gK9A/Mr6UfYBVMid+YDQ2ahrRoGzSNGU/
UIWZ5nbQe5rnpQZKlDZHyQp6sPSae4DJ+glZA/Qw/YW5Ch62fuT78hVwT9ksn4FYqnxghoP1pvWa
+j5473o97gJgHDY+NheAelBtpC0BGSwDTUBsMNoo/cBcLAZRC9TOOOUOMEfIT7QvQD40n0sVon6I
GRJXHgLC/Ev7LoZMX4R8ZLODkoVr1s9AbSsyiS/Am5y8LOl70NpZb/mN/bvDO5100kknnXTSeZe8
deJccED4yIo7oLds3XRIOPgGBBdwTIGY3i9OvMoNSdmjc/vfgFudHt28nx9evHjp++w+KGuseTPk
gJ2W04UP9gKfiepq3wEQ96131OMM8Lyep9mvJyF5dVJYynhISEo69WIN+Md7NvtOhGw9slTL1ACC
y4cbWVPAvd3ZztMFeEkXuwvUwaGHc2lAbee0V3tBOWMcMcJBL64MFiVA2S8fcAEoZxZxeUHrFxjv
GweqGj7TrwtkuFHp21Kt4JWvK1uyBZ6cvXDgXFuI6pHgdWUB52diqRYAtjLmGOMxpJxNOZmkQ5wz
ZXTCUvA0MYcbnUHtrsdJHeRyuZa54C3ijTI/Bu8ww2UkgzKNYHUJkMxD6oKx27vUOAzmS/O1vh20
0cpp9TMQEcogMRm8ZfV2ehEQm6giioF4Yj6VdpC9RLzoCUYmOVQOAjGKfvIOyDJ0xQXyomhNS1CH
iCAEmDnN3XIxyAfKCh7zX+8f3QBiu9JUnAaxQ0wkF8gr+iMZBdSWLakBmkfbqIWAWK9YRUGgMpPl
TRDlRX4RCOYnZlGzMYhZvC+XgTGW2iwH7xGXJtuBWVReltnBukJbruQC8xdzqNgAZJUNKANymRhD
bZCP5RwZAvSUuc1zIK7JTRQFmcnsJ4+A+TEXmAbe+eY+oxaoK7VPtFCQmN3NDmC+L/cb9UHONrPL
uyC/li1kTpDH5Cp9Big9xWRzDjBW7ahdAksJSxkFoMZ/fTNXr6i/9HQC23LrVjUbOE+7vxH9IfK9
l52iW4LvPft7vm7wM31iQ9aBJ06MFSFg5vdGu8+Aecx5RLkJNKfF3x3k6aSTTjrppJPOu+GtE+ec
MlvdLHPhdPfLSUcbwpE7Z22HssPTYa+/jgwEx5oMlV5PhIB2QZsczeC18myIZwb4dfQZZA+CxKyu
755Wg8SN5qlEIFsz/56BVyFgSmBKmUTw25sxxZEFhIMX0gZlRxdf0+gC3LHczHH2V8jxpMDEPCWA
rpb9thZATb2QaypocYHhmX4EOdm2gDUgTWO9Xh1EWXFbSQTlvhxsNAZZWJqOx2Ark/vjonUgw4KM
oXkM8B2UaU/e7+DKhJU/LhoFzyMfjny0H16PMgrzARg7hJPvwb3cOSx5KOghynCqgzvZ+6GxEMyN
ZizDQT4yPzeXglnPDDNXgTFOtpVbwChlhputQHyglJPXgcWMoRCYPWVB8yXILcwW7cCM56UMB1FQ
lmUNEEZ26oL0o7TMCuQWk9gIoiuFZEWQiWZvGQccFGN5Bkpn6SQauCE6i3CQX5FfmQJmC6y6E+R4
83OqA4XoJ1aBcVwPludA/UEtJoJBfWapqtwFuVW2E9FAPzlI9gJ205AJIHObdrkLaKxkkKvAvGBU
NB+CzGIcFR1BZNQ+VuLAWsoaJmzA19aTyiNQqut75RdgTOUbMyfIieYrbRVwkm58B1Qhu5kBjBbm
A7kaUOUhLRTENiwiK5jdZCm9H8jheJgJFDfjjOwgRgqrlhP0+fpTWoNSWASK3CDK8In5AYjsMqv5
CZhDuSfugDHVLGU0B1FM12UYmKp5W3QE43u9nywFnmqiMxZQ1mk1lUzwKi7W3zkAXtbwD331Gnwm
2WN8doD1mZjpcxRSPhNLzJzg2e884A787yC5+faBevv27du3b/87TgnppJNOOumk87+XAgUKFChQ
4K9v/9aJ85Fs19ftXAaPL8YujO8HPgWsXbS5oD8yDpudQETEzbcakDEsw4vAcuD6KqP9WQ3I1MGT
o1AJeB6RODHqI/C9Zw21Hof7616+ZywB/znx5aM0sHyszdEdoNl8REpX8Oy710Oug1vLr/psbQ0Z
R2dJ1D+E8hern+v9FaQUcVqdg0G1qUV8HCA+9BmduQvwVEbK6qBUJ5TeYB4RFpEZZCSxZgCI9dqx
8CCwdwp/bO0PCR2fjH7wHlxq9XOuo2Xg1RRnBk8cpKxijpgKPntsQT6BoGcTG0UgJJdwXXX6gXeB
vtBcDuIjkaycBCVazab1AvMjfZJnHyjnzeZmHCjRanElJ5gNzfvyGJCNSgwBoQiPuA3MkJPlRsBG
UT4Dacqi8iSIb0RFZSTIbrKTbApabctYrQYY880+5vtgzjDrmd+BWklkFGGg3FRuKS3AfGYGy6dg
NqIUW8CSaOlqKwh6eSOLng1Mw5hgNgc+knaGginNlvIlABPMTKAkKBXVvaCMVC+rx8HIbbQ3OoNa
SOQXm0BmMZ1GWZDr5HPOA6ZaWZwDpggLvUCmUJrXIOd5ipiAWdSoZu4BGStaq8uA6/wkl4I8Iz+Q
vYFStJTLQF4zihIA4keRWRO++cUAAIAASURBVC8KoruiKOeACvK2sh7Mg+ZZsyaQVcTwA4hh1DR2
Ah/LOHMTeN9jpvkeiP1yqZoJOEQh8wSIPerHxkyQA7Th2mIwShg9xQZQ6yua9ANzqQxVEoGOIi8P
wbJcVFBqg7e4PtqwQey61/2TSkFYu2B7kgX8evhgfQTCqk8lK+gn9PLCDXTk6X9CoKeTTjrppJNO
Om+P8rYduNZ69ka7oZgth81sCiXqlGid2Agy/5K9tPgFoqKdVz2D4XbvX4dGZQTfJq47mj/I0wHd
X52B3A0KFshbDqKjUkrLdmAW5lrK1xCzKOn8nQ3w4mZim0efQ2zJlK3PTsPFK5e7HSkKvn1CS+Vt
CKe4VG1fRUjcEtX3fj9QrLbxlt5gfCUz6s/APEhdewWgDl1FNqAC9eVhoDR1+RyU8uZyMQrMytw1
pwEzmOoNgQdxp1acioHIJg/9n1ghZrBnsfwMtK9s931qQ+Bu3/f9RoG6VPlRuQVmoNR4CNYEW3bb
aFDqKBfU+2AuNrcYs0FZr2xQFoMWphXQCoPSR2mnHAaRBQuPQdwWe8WXoHygfKx8CSK7Wlh1gCWL
paj1PMjH8rysBpbiluJaTrAft5+wXwZrZ0sjqwds1W3n7YngOG3v4RgGygplu9Yb1Gpqba0DaNc0
XX0EYrfIRWlQ9iufqmvAYbHNtkeAzwb7bVsxsM+03rTmBOszdYjlFChjJcpHwA4jnzkTRG3ze7kY
LJnULepokCbVOQdGjJzFLTC/ZiTrQD4ww8zjIJKoQnUw6umZZE4wW7ojZAyYh40RyhWQVeRpGoCo
JexKJWAB+/kUKMJ88RLED2KEmggiUviJHcA8FrACaE1HeQ1ERfGeMECONQvJ5mBazSJKS1BUxWLt
ApYUbbPPSZAVzL3KLTBe6qXYA4xnkzoMmGGuohIY6/RyZiQYQk8wLcBh+UQ2AiO/94j+EIwfveHm
TtDvGkP07hDT49X0pJLw+mF8ZFIjoKW0u/uA9oXyMXvAqGlm0sv83eGdTjrppJNOOum8S9664uwY
bD9nHwUJW9yTExtCRAof+HQC37Hyuf4BZI4M/tCeAGGXtX4B8yF7iwxW5RH8ujFh1YuFkK2vvVzp
z6DInBKrssXAo9JPbl9+AEknE0zf4aBh+c6SG9Tblg6JwaAcdW+yTYfgAwFK4HKIehBXKKUu7Km+
v/qsUGizst2VqXkg+ZE8rH0ISgsRK/uBzCruydlARmKVjsBu0Ua2BLMcbWRPUPYrrbRY8NaPuxJf
Gq6pZ7udKgwxA5PDkhdDslcOVr4Hn+6O5r5hoOyRz40T4B3tPuHODTjEGLEFlIviY0WAEq9UNyNB
n+O5rl8HZbS4rrhANNVKq1WALrKt+AHEWuKNL0HaOSwbAbXoLI6C+bm0EAmmj1lGNgXlB2WZ+iOo
iuqj1gUhhamcAEM1XMZAUDqrO5S5ILaKI8opUAdaDO0XMA+apcyToI8x6ug3QZuhjlEXgLHETDYv
AhNkfvaBZaxaRUkA8VhJUCqDUl/pqFQB45reVnqA8kyQycCvYhmTQEwS/cVl0GbYWqh+YDxx3fNc
APOQnknPDEoFxVcpBySa34hYMEuI7KIiiBmyJAdAlla7qY9By6Ru0Bwgk2WCmQvIzXIRDto1Zbj2
PtBJIPMA08QQdTiImYykNgib0k92APGUF+IRiO7qPJEbrOdtxf0DQK7ALiqDOo92Sh3AK+clnQfv
NM9Q5z0wpxn1FRMYYn5lPgVlm7zCbsAmessmYAaZa/VJoK5T22mJIE7IfEpRcBxxDLQvAWWd1sh2
CxInJuc3ToNnobepEQRqEzVA7AUZJe3eRUDrvzvE00knnXTSSSedd8VbV5xfdo4Od24Ga7Btsr0b
hIjQ6FzNwWVXYuIvgKUTReQo0NdaFztPQlS0++vXuSClV0oe5264Uvr5ugO34U71pyOu1IKE2Fd1
ZFmwxDhG2++AjyPklN9iYKN+Vj0Dsr3RzbgDD/LftT4JgcRSry+r3eDZIeP8gwS4s+L+wIWLwOem
/Zq1HphTqGu4gCVcUg8Dl8R9aQIZ5VJ+AJaZrc1NYJ1lqamlwMshtypfvwyP29/reu9TeBXjOaYH
gAwWUy0a2AJtr9Qm4FrvqeS5Aik1dM2zDcxc8oppBc9yT1nvcTAmGft1O2gnLI+s88G7RK9orAcp
jdPmYrA1tRRXHoJyVOuk2UDV1BraObCMtjSy1ANbIctnlmDgMpdlNaAYJWRboB99qQtit9jFWpA1
ZXbjLrhWO4emvAJvZ2+Qpyt4i+rPjJ6gG0ZuYxuoEWpR1QnKNXFOmQrKZ+Iml0AqjDevg7iojFFy
AiPlKtkfSKY4I0EsUpxcArlDhPMFaEu1bdpx0MeZ35tbQG0kl4rqYBtsLWmbCGpT7a61Bqihmo/6
A8gysrCoCdJijjOXghnJJHKBOpf+qgLaY6WpxR/EGooqU8B8bVppDMZu44kZCN5e3o76ZrAsE3u0
QmBZpPhaLoB1j/Vzn4dgfm02koXBLKbvMPeCp5/zZtI08Hyaci+xLKTUTK6bMBiM97yL9YrgW9tf
DXJC5ltZovMXgOC1IUtznAdbe99eGdaBT1DQhxk/gdB9YZNyTIOgb0LbZ8sDjl6BY0J7gX+V4D6Z
m0DGI+HzI2xgmeJYEVQYvJ30zWopsHwrlhoLQGsvqmgj/+7wfnMG1xpca3AtaH2o9aHWh9KWT80z
Nc/UPH+3dP/vUKZMmTJl3mDE4rft/y57/av2G384/nD8Yfhy/Zfrv1wPVW9WvVn1JlTuV7lf5X7Q
73q/6/2uw7PRz0Y/G/3H/Wx5vOXxlscw6dWkV5Ne/XV53tY+/2r+yA7/KX7yZ1wse7HsxbIwYMCA
AQMGpP1NRX4iP5GfwPTp06dPnw41A2oG1AyASssqLau0DPos7rO4z2J4+vTp06fvZLLc/5383X76
pnZ6V3H+r+atE+dspzO2sV6DiAVZMwRGQqQz9s7rY/DY82iI8zC8bJr83NUGYh+4/GKnwpO2Ly8o
F0GrabRz1AXnD3JWUkNwl9NPGdkgJbu3uK0HiLsJeeIrg9KHVwl1wYjSZqpjICXG9Deng/Os2TFh
DuirtN0P6sGTFq8sRjZY3GXnpI0n4HKDY/5LY8Bxw37WtzvoS2Ru9wYgk2wuQkBmkCVEZxArRCk1
C8jhRk73ffh17Pmy5xdATMfXT+JKQGJHz3N0sNyzX3XMBzVMXFfaQ8pUZ+2Uz8B9Wd40B4LMLqLF
ZrCMt8zTEkCbpDa0TAJ1izpYWQHWitYwbQ+Y9+Vqcz+Ym+QcszlorbV26gegVlSrq7VAGaOMUCaA
SBKPWQmc4DGzQfwoVojyYIaZBeQWEF1FJ+ULsJbV6trsYL9se+IYAMpAZa32DZjxshb7QAlVOyoa
KB4Rq64Fo6HxqamA1letp9YBW6JVsecBbZ7mo80A4VQeKBVA1BeIJcBJDL4Ca26trDYUCOI6CaCU
FVVFQaCW3IovqFYxSf0ItKHqYrUsyBSzsugCcjCbzTlAeXzkFNCOaa+VhiAai4csAnOpUUB+D3K5
+Vz+DCKKcWIyEC+uKs1BPaw+spYCz0Fvcc91MMcY241AcM9POZn0HLw/eQ97J4K50JwuV4M4L7oI
E+QB2cX4ESgiKtMElCxaDa0CGPlMm3wO/pf8a/l5IePLzD2z5oVsl7P1z/cYstXIMiLPNMheNWuX
7EMhx4pM8ZmOQc5zER1C/SDToaBljmQIWmjbreWEwBs+n9obglZZuaZ0A6WtGKy0AjVM2aZ0/PsC
+6/yU8JPCT8lwNo7a++svZO2fH3w+uD1wX+3dOn8ESc+PvHxiY/Tfv9d9vpX7Tf1wnto6qGph6ZC
m0NtDrU5BJ/7fe73uV/a8Y8YOWLkiH+4YT3c5nCbw23SEsTJByYfmHwAzs8/P//8/L8uz2/1/Z/G
H9nhP8VP/gj9Pf09/b20G5uTnpOekx44duzYsWPH0todm3FsxrEZsHLlypUrV0LXU11PdT0FfRf3
Xdx3MZyec3rO6TnwdeuvW3/9//Co39/tp29qp78a5/9u3jpx1m9Zkl3z4Xaj+y8eWuHS1FuLb+2A
8KpZq/jlB+d5mfLyGUSfiy3hKA/KXRFs2wbRy5I7mufgdZ/4PAE7wNvYaJ1hP9h6BH8Wfw9SKnq7
JS2BV/sfZ0lWIP74y3HusWCONm7IReDydU5SK8PLpLj28U0hql1sqcgxcDtv5PO4vrDs/KEmE+Mh
0nar++EJYM9qb+VfB8xsZn69E4g1Yp9sAcp97UtlMbjuRW+NKgAP714/cf0VvG7lnOWOhaTaxiTm
g7Wy41tbD/CM9OY3LoJzrmeBMxz0SpQiCYxF5m5jEAhFXKMxmMfNRiYgOrKWu6Dt13ppy8HSW/tE
k2C+NCvKX0H/QP9Q3wlGJiPEaAiyhqwje4M531xtrgW52Oxv7gTZV9biRxC5hUc0AxbwMeuAkVwx
k4EFYp2sACzmO30AiAh2GRpwXz7nCIiOymwlE6hL1Htqc1AWqdPVjWCZr23SpoH8Ue6iIrBJLhYl
QDGYoFwB4aKk2AUMl05+BlnAHC1vgrpMaan0BzagKHfBmGguNtaCaCf6KQqIzqKLehXwECmqgmWJ
Za9WD5TMSqzyMVivWq9Yj4F8go8RB+IG5WUTkCHm18YZ0IP1BP0yyDXmE1kfvBuNgd6SkLzIPVWf
A/oSYxQBoL5U12pjAQ0hPgBvY+9H+i7wzvDOM46CrCjtxnrQu+gHvXcg5ZeUZgkbIKrG8wuPWkDs
/Jh+kbMgpV1ik+hnYCZ6iyZtg+QsyS3iT0JCvYTs8W0h2Sf5bsoX4PrcHeF9CIkFkns4gyHRlVQl
cTjEX0rqkpQA3jNGY89OsLVUp5vX312gHog9EHsgNq0S3Cx7s+zNskOTcU3GNRkH20ZtG7VtVFr7
uLi4uLg4GDp06NChQ6HBtgbbGmxLaz/sg2EfDPsgrd2oyFGRoyLTtu9Vrle5XuV+v7zH+R7ne5yH
Dh06dOjQAW5WvVn1ZtW09d27d+/evTtMmDBhwoQJact3PNvxbMcz+KrBVw2+agB79+7du3cvtGzZ
smXLlmnH07Bhw4YNG8KSK0uuLLnyez2kVkRW3FhxY8UNaJvYNrFtIiQlJSUlJaVVphpFNIpoFJFW
0Ug9zj/jXcsVkz0me0x26K32Vnur0LRp06ZNm6atv778+vLry/9YntQEovGuxrsa74I5xecUn1P8
9+1SKzh/ZK831c+byv1H+/1naTGpxaQWk/644hUVFRUVFQVhW8K2hG2Bnud7nu95Pm27zM8yP8v8
DG70v9H/Rv+07U56T3pPeuHF+BfjX4wHc64515z7z8v1R6TqO1VvqSM1derUqVOnTlqczT0z98zc
M2nb/VU/TdXLTPdM90x3Wv/z5s2bN2/eP2+HP/OT8bvH7x6/G3bu3Llz58609cYZ44xxBuo/qf+k
/hN4tf/V/lf73519U1lVY1WNVTUgZ86cOXPmhKxZs2bNmvX37eyV7ZXtldPOhx07dOzQsUPaeS4V
Xdd1XX9z+77p+fO3dpp1YtaJWSfStutYuGPhjoXhacanGZ9m/Nf7wdv66buy65va6a/G+b+bt06c
vYWNyIBx4I2JtVv6gG8G0xPYAjJe8SH8BygUHrYl9AE4Mvpa4npB4kOl14v6oK2wlo6dCjxMGhij
gbu03i2xMRAnvk1xgTHTr1z8ZfDbavc4XoBvuFrbOhAopW917QTbXv9urmHgGeEpaXkFkQ0ibyrn
wPWlc5arMmi1AhuFHoBFFbc8GDQdEmdG9rxxCrQhts98H4MZpvf0/gwc1wYogRBb90HR+2XhyaNn
AU8Pw+s4Z6i3AhgvlfLqSbA4rWctPcGV5OnufgEpY73F3I1BlBYuMRVkLuOq+RwMRa+jFwazES3N
vSCLGV+YD4A4s67ZF5QB4lehgGgoR4qVYOYxHWYO4Chn5EdgXjevGhVADBRdBKBGq04RBYpBdZqD
fGnkMaqBcUZ/7TkO+itzldkEZFbpldmBgTIXy8FRx6bZY8C61dLGEgLWbBZpDQVrS0sRa00QBcxX
sizwvizCfFB7qH3U5iAeKN+KhaDEKuWU4aB2UUKU3cBqAvgVzD7mfTMAaEQWuoF5RW6Xi4CN4iqH
gTgxiSqgobmsuUHrqpW12cFWz2bzdYLjG0e0fxVwuB09Aq6Bo47PDv86YBtpLeizAwKq+x0OLgj+
jQMehDQCY6yRwXgE5hVusQ/8lwVOCpkOWmtbGfs+kEW5zybw+ult9XAwThsFTDeY0WYVWRlcwSk3
kjuD9ytPkNMKeht3jpRPwLUt8de4dvDCETXx2XV4+NmDRXft8OCbJ70fnYPI5tHz46ZCQif3Fm8h
iF/uPk0CRPZ73cNZAaKPOJt5Q+F1s+QE/QTEhMR/7D4AzuOeFsY+UO5jMeu9u0Adl3Vc1nFZ4fu2
37f9vm3akPP8HvN7zO8BP7f/uf3P7dPaT94/ef/k/RD2OOxx2GPY+Wzns53PYOuTrU+2PoGIMRFj
Isak3emPyzIuy7gsadsvKL2g9ILSf7y8orWitaIVzs0/N//cfPDM8szyzIKYmJiYmBi4vPjy4suL
07a70OtCrwu9oNLVSlcrXYU1d9bcWXMHPin1SalPSqUdz9IrS68svQJzz849O/fsn+tl1cpVK1et
TLtwpJ7AUxP16quqr6q+Cqb9Mu2Xab/8eX/vWq6v836d9+u8aUOOW7du3bp1K/Rd0ndJ3yXwXYHv
Cnz3P7wtpWaNmjVq1oDF5ReXX1weVqxcsXLFyv/BT/7AXm+qnzeV+4/2+65IvbDvybYn255sYFli
WWJZkpbAR+2K2hW1C4p8XOTjIv9QYRuxecTmEZvhu3bftfuu3buTJ5XUG5ugoKCgoKC0G68tYVvC
toRBYtvEtolt09q/rZ+WFWVFWQGLLi66uOgiLKu8rPKyym9uhz9qV69evXr16sH+XPtz7c+Vtv7U
qVOnTp2Cgu0Lti/YHjJ8kOGDDB+8Oz2mJkyrqq+qvqo6DK45uObgmv+DHi6WvVj2IgwJHBI4JBAO
Tj049eBU6OLt4u3ihWwvs73M9hLGNhrbaGyjN5fnTc+fvyW0bmjd0Lqwu8nuJrubQK21tdbWWgtT
f5r609Sf/vV+8Fve1E/fFW9qp78a5/9u3jpxto/3fuzdCyELA9b5NoZQR8BeS2dQ8plrjPIQv8JI
dhwGrZF5V9aFoOHavgxZwLbQtsI4D65zSraobeAp6d0eFw+exORs/hkgx/mAXpkTwV5B3tMbgOXX
pHlqDDjOGbltpcAy0bFBPoIMLzKPtxaH0NAMZfXBEOEOmeVbCFJOx1gUK0S2cE12noRVt9e3/rIn
EJcs46qDmGcZ5NMUtJ2yMk0h6uyTD+8UhFcFXjdNckHcS32HeQLUjBah9QIxVpRTZkByHufzxHbg
XqYneqaCGGI0NlcDOjXFCmC1OUCUA3UgnysfgLzMVP08GFnNr/VoMNoYXmMTsIDhlAWzodlergHF
piQqIaB8Kd5nBVi6a31FVZDfc0gpAWpu7aylJ4jrylA1Axh3zexMBsKJk4dAtBL1lCrAQDFeHQ9G
LTmPziCnmZOwg7FZH+ndCMpLsU3sALW3OlItDbSnPndAdBatRUdQl6tu9RrQSQSwB5S5akW1J/BQ
iRMWELPEbRqDsp4zLARVV2dyErR1yh7lGohbsrQYAFpz6w/aJQifnKVeziGQ+Ubmpvl8wH9c4OPQ
nBC0NjQpYx0Ic2f6JUcVCMsaUSR7AARdzlgiPBeEN8oclms42K/4jA1OhvAfMs/I0waUJZpDHQnG
fn2mezzoQ71RugnmV8YJ/Wswpxi7vAdBrjIOm5fAXM9kpSSI3MSbA0FPNgL0+uBTIuBO0CGwDrf1
cTQDo76saFSH5HuJ++Ivg+cz14qU0mBONb81VoFlr2W/bSw4mvrUCJ4D9iW2IoGZwfxAtHQ8guRh
+s+2jZC0zpOJqSADlc/Ud3hHnHqiHLVj1I5RO2Dp0qVLly5Nu+B89+133373bVr7E51PdD7RGbqd
6naq2ylQPlU+VT4FsVAsFAuh86zOszrPguMfH//4+F84AaUmwOcXnF9wfkFaBaCsUlYpq4B2Wbus
XYbYybGTYyfDReWiclGBChUqVKhQARZXWFxhcQUI2RCyIWQDrBuybsi6ITDn7Jyzc87+eWWwVctW
LVu1TDuu1CkmTXY12dVkV1q75tHNo5tHpw0J/hnvWq7UhOO3clVeWnlp5aUwp8ucLnO6/HF/qRfW
0NDQ0NBQ8HbxdvH+D+3/iDfVz9vK/Wf8tlL1aPOjzY82//64f1fJKkUpSsH2D7d/uP1D6Lmg54Ke
CyD3gdwHch+ASc0mNZvU7K/L9aakDh2nVuY1TdM0Lc3+qTdgf9UOv6VMzzI9y/RMq8j9VX/4I0rP
Lz2/9Hy4/+X9L+9/CQnfJHyT8A3sGrtr7K6x0Ph54+eNn/95P29q39Qbmy6du3Tu0hkyfpXxq4xf
/fNy55iYY2KOiVDVp6pPVR94kvFJxicZYeHFhRcXXvwLdn3L82ejzI0yN8r8D/aNaR7TPAYu9LzQ
80LPf78fvKmfviu7/mU7/YfF+W9568TZNka7pJQG78+eM5bJkBJoPPcbDwnT9edGMmg7bbuSBoAc
5Tgpc4IoIy+6ZoNPDw7SCTyq8av9BWj9xSHnQrCNVX5gASR2ik8gAFyv3U2Td4ExUWmpbwGfoRGj
bN+BeTPpue9VePFTzHNvL1AfKauUDRBYj7W+RyHwakQH5xbwL2kf5B8N5zpExj1bBsfn7W+5+CRY
ZnpKOIeD2GB6XVkhUr2z8lE4vHY5U1wtwX1N36JfB5tpresoAuYFuV++BNcp12vXaeAgW8VJMMrK
soYNZHd50nwCxna5zJgP8pLcYJYCOUMekftA9jRbySSQtWQDuRZYLM6zFLSeWn0tM5itzbIyGIRN
dFR7gznS3IIEsU/8IoqC+qk6TpkKopJoI9oBJzhILVCGsl/9GtQhYqH6GKwXtPyW2sBVc7j5AIRX
ySdiQElR3lOmgTJZOSBegjpIW61tAeWEivIC1ExaaS0vaPfVheoHoIwS15VQUBaqWcQBUDOr76s2
0ApbKlhOgBatfaglgzZHLaM1BssHWrD9IAR3ynA301kIKxQuc5wBsnJavQPxfePXv9gLns3Jl6LL
Q/zE6LKPvoaEQbFfRD6DJOKmRLWDxO9jNzyfCPF9Yu4/GQv+x/2W2I+Cu5KztzMYEsvHff66IRjn
Pa+9u8BY4A1zjQbDTy/vbgjGWH2iJwTMBXK49yaIn+QWvRzogXq0DAbbRp/XgQlgM3y+DRgGfCSP
y5GgvzDWeDeB/6MAV+AvEDwluEvmUNAyW+b5ZgRRR8N+AywV7WV8M4GobxnuUxcsHXyKBeYCe157
svUD0G97uqaEgd7GqOwc+O4C9fsC3xf4vgB8ee/Le1/eA9+BvgN9B8Jiy2LLYgv0H9B/QP8Bae1l
KVlKlgLtinZF+z9MLRDnxXlx/q8PXRc7WexksZNwp+admndqwrkF5xacWwAljZJGSQNKnS11ttRZ
2NdiX4t9LcD/jv8d/zsQvCF4Q/CGtCHKPXv37N2zFyJ2ROyI2AHdTnc73e30n+/ffsN+w34j7Xd0
jugc0Tmg5t2ad2veTTtxV7BWsFawwqvJrya/mvzn/b5ruYy5xlxjLpifmJ+Yn/y+feqNzx+RWnF5
W95UP28r958xs+jMojOLwsaNGzdu3AiZd2TekXlH2vrU5al/3SfcJ9wnYHDQ4KDBQTDuxbgX416k
TWFZXmV5leVVINOzTM8yPXt7ff2ziAvigrjwP6z/7zj7q3b4Le/KH/6I1ESq1t1ad2vdhe2Zt2fe
nhkuLb60+NJiqOqo6qjq+PN+3tS+qXNhU0cy/igxS50qdKbbmW5nusESyxLLEgvki88Xny8ePvf9
3Pdz37SEcufYnWN3jn1zPbzr86eyUFmoLEzr99/tB2/qp+/Krm9qp//UOP+dPd+2g9c+ie8bncAc
rWbwdAbvp3o7EuD5tujBzm9A/z5ZqNkguJJ6IvRXCM8Q+GuSD6iRxhmxCDIe9GsQOBEyfpjhczED
LLUstWJ6Q1hYyEFLYfD52D+jrSf4jbDVZxvEzEk+8foU6BkDPPFLIGxA1slOCRneC1zkUwiUbfZh
fAdJeeM7MgFcL9wB3r7gOeK47WwJawPPdFrXGfYW3RG8aDG4qz5f9cAfnjV65HgaAfHtPIHefJCy
y5hijgG1kaWj5QfwdtFze/eDa5jH6RkMsjAD1ZnAKjoo5cG0yZnmEJA9iJO9QPrJs/IeGLXMaLke
GKc8VVqA+EndrnwOcgFF+QKUFswTNUHMlS+5D3o+/Yx+BsyB0l8+AHlJ/iKPgrHKmGouAHxIQYJ5
zjxi7gXZXXY3u4I6Xp2lDAKlhdJG1AV1uDpWmQ3KarFAfAzqCzVS3Q7KXmWvMhmU78UEkQ8spSz9
LF+D1lzZpuYFrYg6VYsBzUerptUCLVl7bSkB1krW67Z9YNms5bUGgJwsokQEWLPa/K0a+NYJeOx/
Gaz97HvtOUA2MCeb30FSnleLo84D3bwzksuCcltk1fICE+R15QmoVznr6Q1KBTnPGAOWO0p3pSBY
O1teqSr4Tg+wB5+DkFqhlzIugxzhuQYWeAnhzbJtzAtkK5rnzntBkP1C3jmlKkDE5Fx9i38JWW7m
nll8JmT+IfvsQj9BtjJ5EkqWhlxavvmlVoFa25orqAL43QwZkNEN+cq/N6DqcQjOFBFQ6A44Foa8
Ck0G3+CAHsGFQLyvNbcUAuMxa/gC1KXacnUXyMDkltEHISln7LdPvwVnh+QBzt1gVDQWSN93F6it
v2n9Tetv0iqhrV63et3qdVoiffnHyz9e/jGtferctmX9lvVb1i/t6ebUv0uWLlm6ZClUqVKlSpUq
/7wcqdunViwKJRdKLpQMm+puqrupLpQ0S5olzbTKVeqJruLVilcrXk3r59KlS5cuXYI+l/tc7nM5
bUpAagXi/+e/Kw9/RpaxWcZmGQvLKy+vvLwynDt37ty5c2kVi2FDhw0dNvTP+3nXcqVeEH87B/2s
PCvPSvgq01eZvsr07vzkj+z1pvp5W7lT9/uH9mqcpXGWxmlzWa1LrEus/5AIpC5P/Zs6tJ1aqUu9
cUv1v/059+fcnzNtyPvfRerT/qlDzKlzNVMTqgVigVgg/uG435Gf/rP8mR3+qF3qlI05xhxjjpGW
SP9RIvlb3tS+a++uvbv27u8Tr98mZqkja6lTwmYXn118dnH4oesPXX/omqbX6GbRzaKbQb6EfAn5
Et5cb297/tzxfMfzHf9Qmd8ctjlscxiUOlfqXKlz/34/eFM/fVd2fVM7/afG+W956/c422+GR74u
C2K5t7YnHLxXvLq9OyTtcg+Ot0Dwp/Jh2ALI3zLTvMyDIey6X7OM38DNKEuXZ8HwIuFuOzMj2E8r
JQPbgRgnUlJqw4ulyc+MwaCdjitn3QwhHUIGa6fBUzZk1athEBn90OE8BhmaOeoETIXkCgGVvQqQ
mNjd7wfw7xPgkTPA1j5U2MeBxyfq25dDIO6Ut9KL6XCs/J0PDhcAY1tyjGUiRK5NqORaDsnP3Q7v
OTAtIoe5FrTq2vvaSHD9qOf2NAJvcaOWdwro0ygjZoMYbCwwu4OsLzayBeQKOZ4EMOeYw4wwUJYr
OcROMJuZ3Y3doA/Tv9JngdZHm28ZAWKwuCSqgLHemKdPA/IqpjgMRl7PXvMccAVJHVB6iImiFYj8
4rX4ECjPeAaA8bNsbGQA85ZcIzeCfEhJMRfMtfJ94kBdIz6XN4GVjGcYCMQF8RJkXVmPV2Ac1Wfr
K0D5QhujnQTlmvKTcAPjySqOg/xAPparQEwQiloIuK+FKctBE5bC1mSwzLY9dbQEeUfMs34Nym0x
WisPrnHJ2ZNagvkemzzbQJZSy1iTQcQobus80DaKh54JoFlVqxoJakvbQZ8lILJbHlol+E7x3RXU
E9R62g5bLdClHGgmgtmFHuJLsL70nR/QD8RFApQGoPbUWlqtQBtysA3kL4TIdaBEkMW0gaZYblsH
gWuwMznxIljzq3a9FwR2Cvgl649gjmWSkR+Ux+pStRjIYbIsh8HoawpZDcRHYr3sAgHSb7r1Mujn
Xf30M+B6qkVYT4PjUejCiC5giXDM9KsKYowYqEwEBr+bQP34+MfHPz4O3Ut2L9m9JCjRSrQSDepy
dbm6HEYuGLlg5IK09sMzDM8wPANMGjFpxKQR0ORWk1tNbqWtL7y98PbC29MecvkzCh0tdLTQUWh/
pv2Z9mdgNatZDVS6VulapWtw0/em701fyByZOTJzJDjiHHGOOIjOHp09Onva1A5KUIISaQ/BpD5M
GHQv6F7QPShlljJLmWn7mz5/+vzp82EAAxjwP8g3ZsyYMWPGwPgp46eMnwKuLa4tri3gWOFY4VgB
X2T5IssXWf78ON+1XMPfH/7+8PfTEs21EWsj1kaAzwCfAT4DYFSmUZlG/QsS59/aa0zFMRXHVPzn
9fNX5f4jP/kzNg3fNHzTcGA4wxn++/WnZp+afWo2UJOa1ISrFa9WvFoRrnKVq/+H/hqda3Su0bl3
r9ffkvrw2AR9gj5Bh/oZ62esnzFNTy13tNzRcgfQiU50end++qb2/yM7/FG7wkcLHy18FOyV7JXs
lf75KRp/xJ/ZN0fzHM1zNP/9cusk6yTrpLTfEWMjxkaMhUxzM83NNBduTb81/db0tETb08PTw9MD
yhvljfIGDMsxLMewHG8u79ueP++/f//9+++nPUwZkjMkZ0hOmHJ3yt0pdyG2e2z32O7/ej9I5U39
9F3ZNfUG7J+10+DZg2cP/g+M898i/msum5Tly5cvX778m3fQ5b1Rd4vtgVJBeXeWqwuuGP2c5xc4
c+rW0xOXIHCdTz/fEZCpdED5rM/BfKHssXwMr56++CDqHNya/6B4fH0Im5bpuOUGFL8W/lGOM/Co
yavubi8ENKO62Ruim2vjEgaBry1koN4clGtGeTkfnq2IL+WuCcHdxcGs88B8nDQm5WcIn5x5RIY4
CLhu3em8BXElkh0uN3i3aPvjpkKuKyElKvSA/A9DXHUcsO3ioh6LlsClUo+LP7wCzr6ynXURRJzK
OibXa0iKTd4QvwmeTH5W79EeMPKJvNp9MI8aNtkJUMgtr4Jow3WWgBkmTbMQyL3ytOwMIqdoKtqA
edzcb+4AJYc6QKkIyhpxSZ0P8pbxhXwOOERP+QzMT5kiJoD5s3ndOA3KN7hoCJSVa0VTEJWUc2Io
CLdyGx0sBTTsDUA8EIvpAcpIJUpeA6WHsl/dDEqkusU2HrRj2j21N2ih2i1bB5ATyWWuB3lNOqUL
7Eftl3weglWzZfRpBepTpYhaEpSM6gDrabAkWT+3ZQbltfZM7QjGPvEx20ApIx5YDgM3zTDzNrij
XNWSZwA7GWd8Co4e9k72F2CuME57moM+0jXU+S1oFbTt1gEgylp2WEeC+F5dYZ0Fch4r1I/BNMwI
cyXIEyJUU0A8UZYqe8DcZR7S54FrifNxYltQ/NgtE0DWIkDpAN4os6FaApxjE3O8Pg/u3l6nsy+E
dA+pGPoZ+H3vlxT6FbhnuX2dRUA/bT5PGQuWJco2dS9Y8jiGhNQGd6y7tWclBH3hQJsPyn5+8I6C
uBqJnqRvQF1vfez/GNS8yofEgnKAy3oeyF4mY7zNDxbZF19c+PO/P7DTSSeddN6U1ArkRfWielGF
b9t+2/bbtrDGf43/Gv+/W7r/fFJHalIryOn87+L06dOnT59+BxXnF9PicqteOPXDvYibp0Du8jxK
HA6hfXy/8fEHRfc/ppyGmJfWO9Fb4Hzi6ehX58GvvOOEOA62FrK82goyzCI4w1hQ8/nlMMdC7ks+
quUiPD39+FFsPOhbrROTs0J875TZ3uqg5TaP+oaBz0BVWmaDJ687Ua4An61BA8RhSMojlj5vBi/8
427ohcC209bTryj4DzGz+02CskPz7672FAwlrrltIrzOlvBz4mhwfWGUMWqDskmrKN4HsVM9LU+C
2+L+wNsIjIr6EmkBGa0VNQXIpeZYszHIUJlVXgZZngEyE5in5REZC+p1MVu1AFk5RFOQeeUDYoCu
ZjdxAIxRcpMhgBq4JMAtWV9MA3lWhGADpZ9yhJaghInP1KPAI3lTvAbpL0+YS4DmopQoD8Z7MruZ
FRzdbRd8QkCdpHVVVbCOtvf1/RUC5gY+D/0VxAHxmXSBMkT0sihgWo1OnhVgmsYl8xjYfrVb7fNB
y2cbZF8C8pFoa2kCaoo6VBVgOaVu0T4APd4s7KkEwm3U8XwAspI0jGqgVNX8VA/4nvIf4ZsEZj/v
WmM4EGu293QCIXjCILDd9GsR5AUtk9ZECwW1m7ba/gjMY8aPcjCIU6KRvAlmc47I8aDX1z8yqoF5
TT/rLATmSnfhlMNgrSt9jevguW8EEwfur7zz9RwQp8T++LoQJE9L+el1ZtD60EiOBF1xdUn+BczK
me+a7cFe3FHA7gX9oMeQW0CUUbbKOeDdmJw5fhTIybKrOghe7XFXSXaBudQsoDcD0dV6zroHrJmN
Ca5NYIzSf5UvICi733d+pUDrhY96E1j6d4d6Oumkk84/x65xu8btGgffJ3+f/H0yTJo1adakWfxx
yS+ddP4f5K0T5+wvwpcqfSG+s+tEVHcI3K+u8KkNGdppvo7l8NqSkjWpPriHaz/rn0NRM3+wnwEp
ZY1FsjdoCeom+0SwvUy8bhkBZjmny1sHgsygy35TwO50tTQmgK+/+C7LcHCvs3/28jm4LxsznMeB
fd76juYg5tP/dRS4yumdtKugbVGKaQoEDwxtHXIMXDd9rrgGgDnydX/HJQj9KtCaMxR+uXGi45FD
4DnBHPaA3lb/1hwDlk3WoqI1MF+0Igi8k4x+eghYgxym73SwXPMJ9o8DPco7SN4CLuIQgWAf57D7
nAPbYNtVezEw8xu/6j3Ae1iX3ghQbqtj1Z4gJN2V1WDMNtrqn4JyWXlfpoDlljXavwqYVnHfLAOs
klFiA2hzLXVsK4BXMg+HwQjxRrh/BnWAKG0UB22JxWvND1q0VsGaG9QvNatFAxYrQvkSLHkto30a
gfkL0tgHWn9ll/YpiA50k+1ALafOUYPB+NQ8p2cHvuKB0gPEGLGeS8BWWV0+BdlE9tCrgtaaK3I/
qA5rV0dpMOJkK+UxiJlqY/UM6J96q3u7gPyB11QE62eWQbai4Dhk/8h6Hty39LmyPphLzETdArK/
+Y0RBsqvogVuELHcNQLAeI9kpQsY94xuZlvgtKwqc4HfCd8Qn2cg5+rbzW8g6my0PXoYxDpe9XvR
ETwt3FWT7oN5zDhgNgbneW9W8ymYizmk+EPMuegWUUPBd5ZPv8AcYGvryOD3K8SfSpwSmxPs7/t4
rSVBPFHH2deDN9F9xF0TbKNUf0t7sPyk/6KchpTX3izJc8Ant1/hwGUQPyuxY5Iv+F1QgyyT3jic
0kknnXT+Nho9b/S80XNoRCP+wlvc/p9n6+Otj7c+/rulSOdfzdu/x3l/YgZXFsjRMWRtJsAvv62Q
zyNIKqkm6CGgztd/VWMgQ6SW27cGhOTIccn4DOzl7ZmUehDaKEtExFGIUS2RcYXgRZ4XBa0/Q567
AcWKh0JGNTx/0BLI4PK/7TYhQ1tbcng3UL7iE2t94B5r5A7wvnK2ksfANsoyV+sBPrlsDdRp4N5l
r/JyPsQ2ib71YD+8VyjXvZJbQIxS/KkPTwpHnb/XG7xfmlcNB5g3zGr8COILpb4SD2ZuM5foBkqM
1kF9DkHlQo+H7YCwXJmW5vKDLB1z3c0fABGHcpTOq0Nw+4xPstYDX1ewf/hS8Jud4bPM9yBADbuT
rREE/RxeJqcDAvSwatn7QmDTDD9ELAO/oKC6YT7g3yF4X6bN4B8a1Cr8Zwi4GHwtrAw4KvhfD34K
js/924acAv98wYMzHgKf4YHfh+cD6wLfG8GbQY1wNA2oBaKEtZ1vDrDut5fw2w/qT9YExyyw1rLd
9l0B6miry+EPNLDN9fkFzHVKDXUmKOXVw9buoDRXn1osYOtreWxbBfan9mjHfjBamqfMCBDjtfLa
DyAqqweUPaBFWSLU7SCiRZQSDPap9os+Y8C3mW8mv0Sw+/haAj8B2VVksewEpZ/RzXwK2iMRTSyw
y3zPpYIn0p0//kNwZXL2SJoNydXiF8T1B1c7Z5tkP1CeKEuVmaAs13Zbh4Mxz5zkqQxhbYMuOZZA
pnyh+YNrgNJXWWrTwP7I3sHRDjLdzeGXwwoZL2U7k20EBH0YVD5oJwT4BhT2qwCWp7YHWgYIqhdU
KuQZhJYM6hJeC6yGctX8CbR82jmlBJiXFI+IA2O66KMPBltPa21tGTCWETQCfaTozgbwDmQH/8ZP
7KaTTjrppPP3kvVl1pdZX/7dUqTzr+atK86Wz/RvgkaB2TL2J0tjeNnGvcS5FrTQYJezBCTmZr+x
G4zDUd+6D0FwWZ/5WhzYtqqrFT+IGyWPP0gCR4bA7j4HIfmoa1LCGjiz6NrZc4D2hXWc2gMc+wNq
8Qm4xiTG641AL01FfgTfGL/nSg2w1HGd8AkFb9uUR54UcGcKbq01AMv4lAC/9yHUos2WbaFAgaxZ
KnwIsr9ziOIEbY/5k6gC7g/1HkYO8BaWT2VfcDRRh/MMZH5WylJAbk5ro0E7Y10a8CkYlc313pfg
XZgyIOUKyFayobwKyg9af2tPUE9b7/llAXWxWsyxGJQ+anO3DrKfftVoCKIMHxotQTRWc1IJLEnq
Ml8fkGvkam8JMMubNcyioNQTFm0hmE6KGnWB8aK2cgTsyfZP/C0gbHKdeQoMyRf4At+IIuYo0N77
r7duqJPEeNkOeIGP2wDRkhXqChA3iJHNQGtmNtVXg6l7EpKmA42UL6wPQMmrxml9wZigR+AFsxUf
0h0YL3vLhkAduU9kAOOy0cDICEYF/Z6zPxj19e0MBs9N73PXREiZEf86NiPYrtun2dqDvbO9t+MI
+GqBW0O7gQgQU7WJoPQw27mHgTlY7hS5wbwg+/AJ2MarGZUjkFLeXcXbE15b4zcnJgMu/6aOSWC5
oa5W54HfWf+fg65C4L7Q7zNdBNXh8yK8PyiPtHA+BPU920BLOVBnGcMkIGuLUnIiKDM1P0sMYKi9
HYPAG+xclLwFXKdTmiTaIHiCfxP/raDmU4tYO0PKKPe3KWvBaEOUuhf0ArrBFFDzqJXsAtQl1ukU
Agpr27VeAHT4u4M8nXTSSSeddNJ5N7x14vz8QuyPiXPgwSj1UGxrUDf5F+EzsHdKqevXHkwf18fy
J0ja4rE448F0uV7a20H4WMfDHD4Q83XS61tXIE8V28f2PJCSQauqZYW40e68RgcwkhI7pxwG/6LZ
unnGgaOhfbX7BiT/fHmcawd4K1uLaDqEr/J/FdwbfJpRz74OMrRV1/r8DElPPL2imkL1raXcde9A
rl0ZBhbYAA/tN5/eygTuvvKSqYARLoYahcBYzgr9Jsha5iBtP8g8cpCoC7hEgJoHlPctixyVQXZV
cmjXwVbCMdP/DnjXenN7JoNWzxquVQWlonis1QezmF7JWQcIIsr4EPjKTBIjQLmpthRtgEgxQ+sG
2jFrfUdPMNbL1+wEax7rBIsC8paeYNwG+aPRikegebQVYjl4ftTPpkSBOVM+sQ0EbSqD5I8gWxkD
nJXAW8684u0BnjH6WFc2EPWUo3I22Pvbtvj1ANd37oiUYUAHJRd1Qfuaj2yxQB4tszc3CF/jYzqD
qquZtcFgDDDc3o/A/ER/z3sX1OJMN2+Cq0tK0aRGEL82vsqrQ+Du6p7qKgjGUr2aKxdYs1jaakPA
PdV9TZSE5ND4IcpQcN90j3Z2AdOjGLaJQEOzt7cbOOsnJSStBP9nAcf8F4HtkT8hB8G2zHbbVgos
IZZcFhP0w7KCURoc+Ry97V+CVs/xsd8D0L+XR8gOoXcz17JOA/eilN3ez8Bb3Rvt2ggiUri9JcHd
xlkzqQqYYzkmToCyUfk5sRW4qzprJ9YA/zLBQwIt4NPHb5LfKUjOl9Ao6SaII0aivha0VcJKELg/
cduoC55PnGfi74LpUTPiBP9+akHfzH8xqNJJJ5100kknnf9I3v51dJ18miY1AJvTXtDxOTjj9B7m
PgisZ6vrWxzy7MtZz6cQ3Mn85HrsK3CdSPlBfQBJzV2hUXfAut2+QYmAuENJIdom0Bs6Zxo3Ifme
UtSZFRz51CL+x0DceLI5xQ4J7ZwvvBp4b+p7/Y6C226UcGWE7MlBOzz3IcvH5SoEbwTlgqPx6/eh
SA+9UdlHUKZBgeFt6oNPKb+iYdFgPy71O5GgtrzYRTwGfbk+QLwEdZ+ZXVwDo40Y7pkMZlZZzOwF
tJarjOwgl5nbzDtg+dqSX2sEnr5mT6MYqPXsY+2vQdmq1bN8AGKOOUfuBNFez+yNA/2Y0dG8CqYi
J+jnQb0mM1p6g+WYdbU1P3g3eHsb44D1Yp/SG/Sjnub6AlBak0lZBcYn3mfxi8BT1Jnf0x7U9uor
n/EgylrzKQfBLOuNdn8JcoyR21sDjFtcNZeCkl06TX+w3rCss44Bl8Xpn+wPeoReOeUgaF21dZYw
8Kw1LslvwLPdvcubB6zzNcU2GpQLSnH1FBgL9Uvug2AvaLmi7gXX66Q+CVMhqX1i49gxYM7TFxn3
Qe/q6ZHyK6hu5bX2K5iFyC0ugN5VP2jYQTSWA71ZIeW7l/Wfa2AL91nj+wiUfQwQXjAivU5vPMQ0
fPXKuRN8WnuHG8GgzbBUtQeBMkzZoS0FW3vbWKsdjN5isTYYEsq5xxtDwQyWv+IB7yx9rDcTaNOt
27QnIPYaXykVwPOV9xf9Dnj6eAZ5RoO7nrNs4iFQM2m7bQNB9SoZZUPQP/dIzwB4vurF7ZdBkByc
oMQ1A2t+tZzMA7a19rt+XcBSVxvh6wPu8s5bzq9Be6x2tAHKTvOMuxzQGPgL7xFNJ5100kknnXT+
83jrxNk4rS+3FIewa46idhOexSW29G4GTZF2RzNwtvT2MA+Cc8rruRYBARcDcgckw/0ekRmfPAZv
C2eS2gn8ff1n6+1AquZDdSiI+0a7uFlgbldHqwcg9utnE5WKEP5Z8I/2JeBXI9tysxwo9xL7+HQD
/9bWyCQNvLkfFTfHQdu6DStO+ATy/pijUo2p4AnU8zIF1FxKbyMDiKOx4/2fArte/ezNA9belrLW
+2AsVx/I56BcNTppHUHsY4A4DuY9c7j3IDgPJZ6NqQx6sKeyIwiUHkqMGgPmJu2pvQGYj7Qxtrkg
xxlVZQGwLbTXtpcEa7A62ToFnHldLRNOgGzEIPzBe9XYY/wMqrB017KD+M4c6+kOZi1PG/dVwKG2
UYeBKyXpTOJNMBsad/UHYI22F5Zx4PEm3X9ZCWxz7NXsz8BvUkCn4O6gHlaKW1aCPty4Z9jAU8ez
1lUQ1MeWOGUaiNJcNg6CMkdbbLsD3qbS4bwCWh2aKm0hrmHsvqgUsNRRE5QzYGYy7+hXwLmAFdIC
ZjVzspEH1ClqouoPdOSU0hFEJzEXHfTC5jDjBKgB+lnxBXjr6POMvGA2MXd4J4MZbT4UA8GMZIUY
BpSgvlgJ1quW3dbPwLjPURkF3oHyEhLU/qKBMhVkikRWBBkpd8lZ4Gnsfu2dBWYrJcrwgHWE9bTt
AehBnhpmArgX62XivgMRpW/2lgeljNpFPATtO+HWMoM2NbBJyFjwCQpyhx8G7pufyxUgh+pT9Spg
FvT8aEwAx0yf9ZggPFTwjgDaKr9Yk4FGYpnYAv65/O+HfAveg+47RklI6PTK/mIwEPd3h3g66aST
TjrppPOueOuHA7X69mvyJ0ioZ4yJ7gH6Ss8J91l4XTE2k7MzXPXcHpyUC5Ib2LZTH1498NR7Ngki
MgdvlhGQqXCGW8piSH7pMynlNrCX5bIDKJ3VQMtDCOlkOeSdCLaman5zNDysmhQUdw0SRyWH6A5w
t2eauyQUexw+uNYT6FOs5bS11yHXuOx5ai2DlAeu+14/8GT1vh//Izy9/7Ta5SUQ0/RGlshBkDHF
9o1PWbBp6jTVBsoA5Tj3Qd4TLY0zINYoO5WZIDUzikcgdxnN9FmgDVHXWB+Dzy7/8+GR4PdV0Fdh
pcGh+qb41gXrOR+PZQTY7tjeU0uAQPok3QTH6sDDQaXA705AlZDm4HPRUc2WE2zB2hy9DKgDEfIX
SBga/8Gro5BUJmFHbFVQflSfaQmgN9Bneh3gLJtQ/oUDzN16fe99kGNFpBoARksZaK4AfZje1XUO
zKmsk3fBXtZ+zlEZtOyW2tZ9oP1sOeA4AfKastryCuSXIs4iwdPNVdUzGvQ63n6eMpCUJfF+zHlw
PXdmSAiHlPquyUnVQT4WurkSzDXyjlwPopHYLH2BozQTu8H0M5oba8CcYIR4dWCM3skzGIw+3qG6
Dczn5jJvM/Ae9E5zdwAZbLYWt8Bd2jvRUxesA+0X/XqDtk350roBeCa9ZAN1u1ZX6wTeM3o3/Xvw
RHrWOkeA2cd4rd8GsxzfUBEsv9iGOaJAPW6d4l8S2Gc/a3kM9tI++f1qgc+CoCcZnoBvtYB8YVnA
1s2SYCsAlrGWF7Zu4Pbz5DN+Aa2v0lhtAz4bfR7YW4BvHv/mwTEQWD3EGtoJfGMCqwYkgKW1vbHt
KGgHZDNvIVBX2ipZ3tHHT/6TmZpnap6peX6/PPV9pv8uUr/oNX369OnTp0PNgJoBNQPSvgCW+mGT
p0+fPn369O/W2v89rFy5cuXKlWkfMkj9AmS/6/2u97sOMdljssdk//fJ86/2qz/y5//t/Lvj9d/F
lsdbHm95DJNeTXo16dXv1/+n+Xc6/3fw1omzy2YbnrAHHP5BZ3wfg+Whb0nZEpKijXKvTYj5LPb7
V+sg6wJLUuAZiKuQUFBZB345bPsy5wDf7PZvlHOQP0foI79YCIzzdSoLIGcP/17hU0FL1AqpX4Hl
olxmXQjaeK87sCDEnHlxO6khvPddqLXAF9D6Vpfbk06Bz3ehWpa84P7B9TppJogcMlovBfFXnoe8
6A5qR++dwMugrEqMMOZBprjMesBGUBqJu2YlUB+pD2zPQQ40Wnmbg4iQ1fQPwN7f9sg6A3ynBU8P
6wgBH4Z3zvID2GYHLPDPCGqi7ZHtJFg6OVw+68D/bLA9bCl4uuhzkp9Dkk/82RdbQT3rnZPUETyB
KXXj54F7QEqu+GqQUiLpq4SDgEVuMM+An+5fNXgYqNfV2awH5aZ1qdoArNt93I4AsH/p2BNQD/yW
B7/OGAG+eXz9/I6B7Ka7jY0g84veamfQtmrJ6j4wa5ldvbUheVDy0IQvwbnALVNKQuycF32eloVn
p58WuPMUnJNcj2L3g/s9V1nnfNB3efcaNcDcaBwxiwKr5GI2gaeEJ84zEbylvYrnIhhWo4SeG5Te
SpjSEERlYRHdwWxDOfEL0EyJU6YDQWKzWAXaJLWPdQOoh8Vw4QPect5KKe+BckjNqlrBtseWy/cK
aKiVtBogigpFpIAyR2uoHQbVaV9hLwXWB9bO9jBQu6rNlREg6+r79Q9BnJDx3ltgGWNLUU1w7Pcp
nrE/mI2VGWobUD6yzrFHgjWjJdg+CYyNnvOee+D6KmlL/HmgupzlfQaUZ7irE7gtroYJiyBlT8rt
hBbgPuo6l1gT3OeTJyQ/B7OXd4czDmxdfL6yvAeho0NfhH/zd4f3v571weuD1wf/3VLAsRnHZhyb
kXYh7Hqq66mup6Dv4r6L+y6G03NOzzk9B75u/XXrr1v/3dL+53PkyJEjR46k3YhU/7z659U/h0Fr
Bq0ZtAZOfHzi4xMfw3cFvyv4XcG/W9p3x3+KP6fz1zjc5nCbw23SboAmH5h8YPIBOD///Pzz89Pa
/b/q3+m8G946cfY13b0yToAg08+a4yZElA04HvEh1LqdY1WZglBvW/UH5U5ByODg+8IJpafkPZi1
I8h9Wh3DA373faeE3IXHeZOmJzeF+FxOX0tTMMqIIc5coGwSa+0pkHFpUIFMdSDrddX/dVVocLHg
9hIDoKt/z8sz64ErWLYzq4Bx2XPf2Qe0mdpr+1Fwjk0ulhAIjm72RcppeB37JN+zYmCba7VbY6BQ
/1LRpQXYumo/iPdAKyq2WqqAbGpG0Q6MaPGh+i0opvaLfTkoW5X74hbIZ0Y2z69g+HrsKZ3A+MVV
N/El6EdcLZNqgidLStOkD0EaRibLUvCZ42uGLAd35pReybfBmTHlVbwBxjf6e/IUKM2VetbS4L5m
jHSOBO2+bYX2BHzyBFlCE8F21vex/wTwvxsSH34PHMnBq8MXgmW77ZVDBz1ZV/RPwBxknDMWgTDN
++YUYJxRwqgIHo9rnWsoWHvbalhqgnZR225JAP/RIdtCe0FEzayOQiPAf6Dvr+FfgPmDPsxZH4z3
jE3eeeDu5wl2XwWP6jnlbgrGVn2hfhRMr5R6afAO0Tt5x4PuZx40AKMzNeUTMJz6Is8MMJ8Z5z2r
QE1WdotpoFxWd1tagJbLGue3EvxDMlTK+AKCzdBPs2YEaxP7DP8CIBbYp/l8Dmpma4QtHjhnfCP6
grUD71mHgswmYtSNIMfjo+YD9YH2s+VnkCXlYXEblONGXv0lyGLegV4NqGjUNX4BdbNSQskAxKuf
2XODOsl6zaaCfZ3PUd/REPZJxpmZKoG9t2NKYAT4dQ88EF4RAlcFXgwPAyVGa+hzC8RlNZdlNlgv
2076tgJzjTbMkRsshe0bfKq9u0CNi4uLi4tL+3Rqg20NtjXYBk3GNRnXZFzap19T2+3du3fv3r3Q
smXLli1bQrPszbI3yw4NGzZs2LAhLLmy5MqSK7/fzx9Vnn67fFTkqMhRkWm/e5zvcb7H+d9vl1rp
abyr8a7Gu2BO8TnF5xR/8+NvManFpBaT/lg+e2V7ZXtlaH2o9aHWh6Bjh44dOnZI01Mquq7ruv7X
7fDP6ue3y79r912779pBo4hGEY0i4JvD3xz+5nCa3VLfnzuzyMwiM4ukbf9X7fi2+tzdZHeT3U3S
fn9a7tNyn5aD8r3L9y7fG/ZN2jdp36S0TxO/rT5nnZh1YtaJNHt1LNyxcMfC8DTj04xPM/5+uz/z
qzeNlz/y5zftJyoqKioqCrp4u3i7eKFp06ZNmzZNs+uf+cmKGyturLgBbRPbJrZNfPs4ftd6TUpK
SkpKggEDBgwYMCDNn1NHdFL18M8e37vy11ROek96T3rhxfgX41+MT/sS4t/l3+n87+StE+fAnIEH
fHJCUnTSsagV4LmYfCumNejnwPsDjOr/cfLacvBJq4a7+qyDsIz+Ac4UyNsjS93MgyHzPK2v/0nI
9KFPc+syyJA9YwfjODw3PMHWG/D4/aTbMRNAyesufacX1FfLWj6qAR3b9VRmFQGlWWCJAAGihHeK
WhREGzVYvQb6dTncOA4ywPzE8wiSe3sXur6HuK7PX0YNgxzfljhe9SX4zg/LkX0UOBIta7RwsOfR
/CxBYHSU2805oDjwNT4AdZzoLY6C+0FKPdcrcOdz7dOfgJxjXsUFunSHuNeDtOnVvNPB2Kt/7bkG
Wjax3ugF7LVWdrwG7ZY9wM8CDnyqBTiA962nlINg3e6o4vgZ/MICEkNKguOc766g8WAbbf/eLwos
kbKeyA36Leev7lkghmvlLV5Q91rrOqqABT9bSAhYV/sVCD4Goq+61fIleGaaK9VmYGnqkxBYAqy/
+BzOMBh8rAG9I46D3yH//BkLgl+74NJhxcGnTfDo8DmQpV/u8SW/hLCkLPNyR0LIjvCh2QMgZGv4
sew/gt9HwTGZqoOlkC3ZLwiUJEtd35ngXzdwf3h5CJ6foVLWK+Do4bcsXAP/+yF5s62G0DZZRxRe
CqG5s7cpthFCRKaQPN9AaNbwYXkfgr2l7/GME0DUVsqoxcBSW/1ZfALKLOlj/ALGHqNSSklwPnK2
j/sUvF86OyfMAqbrNVwdwAj1fJQSAUpWGWTWBKOGvk7JBmY2QjzzwWwuy1kU8FTwZDViwLvGMze5
Gxi9PB7neFAKyIJmHRDzucVs4KYw5UfgKebe6WkI+nZvjL4SZHbTY84ExVcZKX8APb97o7EBVCu+
4jz45LBYZNS7C9TJ+yfvn7wfwh6HPQ57DDuf7Xy28xlsfbL1ydYnEDEmYkzEmLSK6po7a+6suQOf
lPqk1Cel0oYsl15ZemXpFZh7du7ZuWf/ujzjsozLMi5L2u8FpReUXlD69+1q1qhZo2YNWFx+cfnF
5WHFyhUrV6x8d3pJpezFshfLXoQhgUMChwTCwakHpx6cmpbAZHuZ7WW2lzC20dhGY/+GLzvUHlJ7
SO0haYnOuiHrhqwbAm2mtpnaZios7r249+LesGbtmrVr1qZt96+24x/x5OmTp0/+YUpL586dO3fu
nJYIfvTRRx999BHc9Lnpc9Pn7fcXWje0bmjdtISm1tpaa2uthak/Tf1p6k+/b/9nfvWm8fJH/vym
/UyNnxo/NR4+ePDBgw8ewNatW7du3QrZ9mTbk23PP6+PVStXrVy18u3t/671Om/evHnz5qUlsDue
7Xi24xlUX1V9VfVVMO2Xab9M++WfP753zYjNIzaP2Jx2o/pH/Lv9O53/Xbz1w4FiTciBmCVgr2TZ
HtwaUjbE7fA8Bdsz5jl8Yde4nUOnHwFzs6tr4jDI9yjT1ZpTwZrsXuIZAg9049i1CVDkun1k1QhI
mSI8ryvBTxFnq8fmggIVQ0fkHAKdVnZq82VOyHw635oyNvD08n7t/RH0Tp7t+iJQ7qsv5XFQchCu
xoK+1hvhCgIx2Iw2vOC3wr4upBrkvVXmx6qFIGBvFp/g4pDcJnq6ewJkaBi0z78CaHVjfkjpDbKe
e63bDfKBuYYyoFzVBqsDQMx0HnIdBuenibVj54HHa+3qcxQsxbTnzAaX6fzOtRa0Btply2VQY+Ql
mRPMUdJt1AWxU4SKLaA/1+t4fgGL1XLZ5gDjC9faxFWgf50cZwwEoauPtLVg7W/v6jcXxCD1pqUI
qIm275WloN/WF7t7AxWNq8ZUYJ781cgNIlIJ15aAcVu+UkeDklc5YQwH8R6POQjGfX23uARKqLW9
zALsUU6qk8Gcqec2boN2y9rb+i34ZrOsD/8OfJqb0WHJoHS1+KutAK9ntvMyeGd4XiR/BpwxJshP
QfVonUVvkHPEaqUMWCYqo8UKkB4517gARm2piFIAQlcrgAzgidIe9PpmG4qA0Vz3cXcFW0HrM6Uo
cM3obDHByGu43GXBfk2L0CQYn1sP2RuAsgd/E7B/YKkvZoFx3rwi64Au9TAzBsxiIsYIBWW8stYy
HNQyWgFHMKimuKldAS1QqaUngF7I+8IzEMQ6vlAjQSutZrf0BvcH7stGe3DFem4ZKiitlAaWmWCo
ZgG5DZgkXeIqiMqq1/4tiEuWamY38PWqjfSNYDesndTX/x0kbd4+UE90PtH5RGfYkWlHph2ZQFmt
rFZWp63v3LZz285t4cOPP/z4w4/hp3w/5fspH1zoeaHnhZ6wLm5d3Lo4uH329tnbZ8H80PzQ/BDo
Rje6/etOMKkXWEuoJdQSCt563nreesA5znHuj7dLrTA92vxo86PNf9xvKufOnTt37h/6yzExx8Qc
E6Hqzqo7q+6E1RlXZ1ydERZeXHhx4UUYwQhG/OsO+3cUn118dvHZIBaKhWLh/2H5FrFFbAFvGW8Z
b5k0/SyusLjC4gpvb8c31Weu2FyxuWKBEEIIgf7L+y/vvxyy782+N/teaP99++/bfw8Tc0zMMTEH
bGMb2/jrNMrcKHOjf3h9Y/OY5jHNY+DHUT+O+nEUcIxjHPu9vH/kV28aL3/Em/YjS8qSsiSMyzou
67iswB3ucAfqbqq7qe4mmMhEJv4PemjVslXLVi1BuaHcUG7A4jOLzyw+89ft/671+lPCTwk/JcDa
82vPrz0PdKADHaB5dPPo5tGweM7iOYvnAI1pTOM/P7535a+/jf8/Qy+uF9eL82/z73T+d/HWifOv
1l9beDTIGhvQ2vgI7JOUL83ZcHLd04IXTsDPLR+0PbId8l0OWRYxCgqNznu98DZ42YWA5yvhYq3b
Z17OhqyOzG31ZMCR7OfywntF8n+adxx8lKXNsv71IdiSObhUAri3JE9IOQBGkuWVPAVKa3FJ+wzk
FHOFUR+UglpOuoPR2pWYcgeYpD23ngdlv7LKdz8YF1zTX8wG77fOL2xjIfRWhH+OTpAtMdvsrGPh
nPnw+5g9oJz0GEozMNubPc0k0OpYyti+BrHXm927ENQM9nGWhmBppHQSscAXcqkBiB0UUh6Dplm+
s28EdZajjc8rEDX19l4ByjBzkGkD8aNLT6kG3lzux66ZYGrmR94l4LXpy10aaAlqe2Ul6C/MSPM8
WCo7WvgWAqWkek3rBrKI2Vl2AP2m0GR+kBWN4t6FYC9nm66EgmOcva19CMhoqYrOgFUGmH3A1ds7
03kE9GKuD0UrUGpbK9oHg3JG3FI3g7aWj5gI1ou2aBkJYjtzzDCIa5b4fnJW4LnxUi4H7aIWYz0I
SoS1oXoXjM9dE5yXQe40t7mLQsoscZ8DoBryjJ4VLLvU/VpBEFfkJDMLqM+pYLQC5a4sbxQFNVD9
zHEDfFK0oWpNEJO1h8ZBkA2IUztA4HsBRYJiwZVNL8dVMMKMreZ9sGa0r9dmgZwn8xkjwdvCswAn
uGO8y9zfgsNuG601BnFMmMpd0Pd5txo9QTuq1hBbQM1v62q3g3gg88hXIDoqZcRL8E2SBZVfIXic
72H/IeDaoD8zDoJeznQpX4LMrz+SpUG9qk4054OWwXbYVgoCfracVoeBVdpCRAUAPn0XgSpLyVKy
FGh7tb3a3t+vF+fFeXEezCfmE/MJDDAHmANMCNsbtjdsb1olqUqVKlWqVIHtbGf7P7FfzyzPLM+s
vy63ZYlliWXJm283s+jMojOLgredt523HXxm+8z2mQ2eN3re6Hkj2Lhx48aNG9Pan+l2ptuZbnB9
+fXl15dDl2JdinUpBp/7fu77uS8c2HJgy4EtsDNuZ9zOuHeXOP+z+vltwvxny1NJHRJ/Wzu+qT5T
h+wf9HzQ80FPqFihYoWKFcB+w37DfgOC+wb3De4LL5u9bPay2TtQ5G9QFioLlYVpfv9b/syv3jRe
aE972r99P6lTA9SD6kH14D+0uyAuiAt/ftyp+k3lXdn/Xek1Okd0jugcUHN3zd01dwNlKEMZwIoV
K4jJYrKY/M8f3x/xpv76pgRvCN4QvOHv8+90/u/mrRNnz4b4byz5wHlAa5Cgg/UrMTmoBNgHGY2N
VxDwje/CnEPhVX7lJyMQrpZ7cO96EmTOFXotaBoEVA//1K8evFziCbuRBFXmFyxTryW0K/B+0oDX
YI0IKJI7CrzrnC9S7oJyXXWIQqBFyNVqD5DdZDa9Opi7eWYcA+Um08UF8CzzHnRGgc/MgKjQhxA9
8FmG5zfBMtvS3PAHawefaPs4UDyWDx2VIGJ59opZdoLPT9ZnN36CxKueNrY+YIyRC0Ui+Ly05rWV
hcQj8YXiZwOvXVNd5cEyMPBbRzK4A91Z9Nxga24P8vkQGCXeJxO4Z8SXeXkPbPXsq/0Ogdgssmpf
gTbNMtv+HMQA9UftEdiwBduHAXfFLlEOxEqjr5EVjG/1Cu6xoOZTQtQo8GTz1NRzgG2pVkWrB+rX
VqvNBPmB/EZdBRQwXuoNIbF/nBbzDKhqHHD3BPchvZK8BvanfhcCEkB7bPvWrzlY6lg0bQtoxdXb
1uvAYnOdHgRikdzs+Ra0X8hgaQmOn7UyZiGwNbKfE1fA57bPY7UkqAky0psL5ADrCdUETw33JiMX
OH2M3NIf7MN97vjnA+c5bxviwbuGb5Uj4D6nb9F9wdZczae2BfWu+qPlfZDzlfFyKzicjoP2xiDm
ynpqNdBLyghvXQg87MhiyQJaA7WDNRz0lWYXhoG4JyooBsgZFqf4BLwP9KWEgOUHyzQtCczqZkW5
GpSxjvOWo+Bt513vKgFqE22EqoKoJpfK7GA2MZcboSAyKa9UCUoudmiFwDcbr6UBojwjzKZgnc8U
ZTV4QvRF5m1wXzW/MSLA9ki5I78Gn2HWbNby/x0k7799oKa+HWJZv2X9lvWD3mpvtbeatn7J0iVL
lyyFKturbK+yHY7PPD7z+EzYennr5a2XIcPNDDcz3IRTp06dOnXqHzouRSlKARe4wAWwXLFcsVyB
mJiYmJgYuNvzbs+7PYFlLGPZH8uX+laLP0sE/1myNM7SOMs/VKysk6yTrJPSfufMmTNnzpxpv2/E
3Ii5EQOzi88uPrs4JHdO7pzcGQIqB1QOqAzR7mh3tBsKzyg8o/CMvy7XX9XPX+XSpUuXLl16czu+
rT6rHat2rNqxtO6md5reaXonCJoXNC9oHkRnj84enR2qWatZq1nf/jh3PN/xfMdzaEtb2gKbwzaH
bQ6DUudKnSv1BpXEVN40Xn5Lqj+/aT/J85PnJ8+HPf57/Pf4Q3Oa0xzY12Jfi30tgAlMYMK/z/7v
Wq9ZxmYZm2UsTGw2sdnEZmnx9Gz0s9HPRsOpoaeGnhoK7GMf+/66P7ypv74p1W5Wu1nt5r/Pv9P5
38VbJ84+twNyh86ALJ0DCuYsCCUrhH+Qqw4EXwg84PWH0+avWx4mw/nh0S1vnAJ9U3hNnw0QYniG
ewKh8DrPbEcC1Nn64YgZP0HR4HxdKwWCa5EY7dMLxCAxxdoLZLSYr9cFFLmRFJDviTIMBtFWDlI6
gRqqTFVLgB4vmyrJ4Ghpm+HXDuIfvDga9xR+PX8528k4KNi/1MzyL0HNoD2xrQC5D8QdyLIzW4Os
K8A32L7UfhSUzM7erunAZOOAkgCWKEsG2yywJto3OtaDUdgyVP0E9HJEiQvga/WbHTAG9N3eSE89
MAbofbz5wZHVJzJwDXgH6dF8D0pV7ZnaGdTylmi6gdLX/E7MAZFf2a3sAiPeuKxXAs8+d0XnPVAf
KTe1nSDPy0C5CYjTWioBIHeL8fIT8K7zRKU0BK4pscppMGa4z3nagiwjfxU1QajWML8R4PPcZ4Al
AFjB10Z2MBd5xhiLwHPF9BgPwNtI8XVfAeOE/sK4AfKyXllOAzOCHuYjsERbTM0Aa1fyi2aQNDRx
XPJDMEoYkUwCy2fqAdkUdJMbpgF+jwMnBr4AV6R3gBILMlEx9GEQnjtofuBN8PfYuir5wbJFW6kU
AREmiirVwXveM13/BNShZFQ+ALFKPatISC7vWaP3A8tQ5aG5BpT+ahl1KhhFZVvzInh/9YxzDwTK
skXND95RnhO6DmZmb193I7CNs03XmoGwm4/YCMpzmsjFYKzXW+sPwZbfOkULBLWlGGoZDXo1Y455
AOTXYprZHcRD2cHQQL2k3tQWgDyirlOCwbUzeberGhh3lADZEoxj2jNxHbR+1jh1LzDn3QRq6kMq
k0ZMGjFpBDS51eRWk1tp6wtvL7y98Pa0h5X2lNhTYk8J6N69e/fu3SHoXtC9oHtQyixlljKh0NFC
Rwsdhenzp8+fPh8GMIABQMdCHQt1LATd5nSb020OVP+i+hfVv/hjuVL7aX+m/Zn2Z2A1q1nNu2fT
8E3DNw0HhjOc4b9fn/o6qVvTb02/NT2tIuXp4enh6QHljfJGeQOG5RiWY1iOvy7Hm+rnbUl96OpN
7fi2+mybv23+tvkhpkNMh5gOsD3z9szbM4P7uPu4+3ja6/6Gjxw+cvhIYAMb2PDXj/P++/ffv/8+
1H9S/0n9JxCSMyRnSE6YcnfK3Sl337y/N42XVH7rz3MyzMkw5w36SaqUVCmpUtpc29UtV7dc3RLq
1KlTp04dUMup5dRy/z77v2u9jhkzZsyYMTB+yvgp46eAa4tri2sLOFY4VjhWwBdZvsjyRZY37/fP
+DN/fVP+3f6dzv8uxH/duUpZvnz58uXLv3kHVXL2GJG9O1TYkONSmQPw5S/tH/R+CVey3O17dQ4s
LbSrzcqeoNz0G2yrA893Ri94+hI61ShbqfpuaJHQKN+4Y+Be7W1rnwXKZt8ztj1gWez7wC8cRB+z
j3SD4ZLbkwaBclAMdkwE2VAs+//au+t4qcq18f+fFdMzu3vTKR1SinSLdKmAgrRBKiqggNKggkoI
KCAggkiI0o3S3Z2bze6cnhW/P/zu3/aLh+d4jvh4vs8z73/Wa8Xc1z0z3MO177nWPXI0iCd5XtkO
7NeSpRtAjrG4fBtyu6YPvhsFWVtTT2T2BHWE8mJmcUgcXbpFVQdY11qaR20GaYtpvNQfbtQ49MYu
J3zo+7DGvGlw9Y2U5LSZYDxkKhVyCsIWJfQuVgmcrbJ/THkZfHPVOXobMBhsZ0J6geBQtwV+ACZp
Vn8xED5lnLgaxNZSDcM80I6KGXIOWHuHt427B+oBT313f8gbn10s9TDo0WrpwBYwnJWXy8XA8LMp
xJYE2h6eFi+AqvjSc0+AttBQ2XoG5KHieqkk6Aatlf4VSEfluYYhwALeFo6DZtITtH0gf21cYdFA
/F6PU66Ar6y7aF51COT6B3ongzxf2mXuA8ITUgXBDkJ1cYx2D+TNUr4tBOSXjJuMpUGP1qoHJoAw
Wxuv3QXvu76x3kWgperlVCsoN/yn/I3Bft3az7QfTNiuhALKWbWJlAmWry17jCYIG2aNNPQCYVEg
3t8IjN8arklvg+F5qaVQA8zFDNfFJiD1Ep2Eg79a4Al9ALjTvWs8+SCf1s3qe6AUU8N8EvjDAzsD
dcFwWT5usID6gjaEVkB3YQO7QB+lOhgLnBRHcAR4WncoT4BtuF2KcIN2WmgqVwWppnzNpIO3j3ec
Ow60zcqWQHUwfmUsJ/lB6CHuE+uB4hfGC1+A9pPSRBwAhGrWwBww3jFVkRZA1GrrffscCG0Y8YZ5
DIx4+73j7134u4d5UNB/poJa1X+1RvU/VUENcI3qNarXqA5hN8Nuht2ErKlZU7OmFq4mUbBqw1/l
f9rrGhT0n+DIkSNHjhx5DDPOpAph4afhYq0bg07WgNlNV96c2QY8tZRz9ouQP9vg1UUQ9+aOTm0G
L8+Obln3AHSsWuP797tA7vmcVFdf8Iamdb26DxIPPW1r1gv8g9S1ymIQJ+ollFwQNWGRsS8IuWIj
4TUQRupZ+kLQGgjT5MXAVD5TVoPJKjQ2PAm+SdI1Twbk9ji2Z/NJcA3dOv/MGxA7fXzzCfdBv19l
f/R10D/mKXE3xN4oVqbEKihaOXxbeGO48WxmV+dh8BkCovdD0ErpihAL8gPjDYsJ3Kdym2b1AMNq
yxMWBaQk6aK0BNRutBN6g6GjvM74ANSPtVHSU8Bn6tpAEgR2ulIyF4N/nneXvzZYTptftpQAIZUH
JgNoZ/ReWhvQw3lfWwH+uYGnvFVB+ABFWg/CRtINP4AyP3A+cAdI0nv6nwd5qJivrwH/kcBFJQzE
AeJo8SSIR8Vf9NsgDjBGGR0QsjD0XJgCPKU9E0gEtkk3zEPAN8lT29cP/Mm+Ia6uoMXoCa6z4F7l
Sc35DiwVrBNsbvCtV6qpQ0C9rE1WPwPrbNtV42iQ2lvjjA4wXjWMl6wgfyx7WArG9dJ7+rfAXT5V
L4Czl7+x+DZIzwoB6TVwfesvQygYDoh7uQdCO19kwALGk4bzhrXgL+77NvAdBNr4P1ang/SupirD
QTounRETwDbTejGkJMiLxGfF/uDr7T3p7QquLZ4l3s9A6Sy+Jkng3+0uqlrA3N3wjeElkD7wDfA1
g0Bl9SPPIFB9DPZUBnGOPM60AhRZLSEMBqfdGeruAKbzxu/N/UD93j/bXwKsgyyd5H2ghQnLzZNB
/Vk9KK4C+ZL1iHAKBK+8Vp77dw/zoKCg/04HPAc8BzxwznLOcs4CAysOrDiwIqyqt6reqnpQI6ZG
TI2YPx8nKCjo7/OnE2fLSlMN1/MQku17LgpIWvHAHfgGonbEvaZNBNMFLTXzLHRxRn9d5wS039bu
2Hgv3NnrfS1NA+vV9K/dP0FkscoLnywK2kJtGWdBKKFP0PuDGqIvzO4Ckl08EuYGNnFZuAz6Df2u
OA8IVX/wdwUpzbrM1hTuVrl17FBVuD900kcT1oKp1y8/pPYEraTvgHQXxE+8iWprkBX8cnW4Jx7o
sCsLbHOjpjoWQHmxqrd0Fzg4+87zqYfAn+Cr5XsRAs/4iiofgKGveVj4QRAO5izPehn0cn6jPxn0
n4y/WLYD/fSS0rugrFA26K+CskmJcF0CfGK+kAn+Ddm7UkNB6muYYbCAabPlx/Aa4HnFe9azHCxX
rG2tR0Ato/bXzoOpOp9KDUHaIq2QfwLeEK+zH7TN6vvqRtDSVJfhIAilua1WAekl4T0lF/yaP10b
A0J37XbgI4h6NiTGlgjey55vPN9CvphrzdoMdFWf9o8EPY3vpXVgaWbbGHoPhLLSdrE36Lqy3LsM
fO18G90DQWppaGR8FhyV7d0tZ0EorbnlvqAe0F5WSoHSkorqXPBd9F3Puw/6h9pG7VuQrxsmWjuA
cEv40fQiMJHzgh+sP1m3GgDlpjZdHALU1JszG7wRvvr+b0A7JRwQ+oNhn/G2tRH4Wvq6eoeAZ5v7
hOc+ZD3r7JhTHUyTDDbpKhiuyGMMQyH7gLONfzSE73R8aHWBY7P9oNgM1A5iD8O7kL3Lud7zHZhc
QlggAgKTNIvwDuhHhXj5GsibpbHSAjAdNfWVZ4H/O29/7w0QjUIEx8D/peILbATFrUYqx8DeyPie
HAXma+ahoQ6QzohfyE0BGIf6dw/zoKD/TBvubri74e7f3YvHZ/DCwQsHL4TRtUfXHl0bGlkbWRtZ
odLLlV6u9DJM2jxp86TNf30//qe9rkFB/0n+dOL8ZPewxkUGQM4tcWpIDITNsrVxbIPQyqYugY3Q
s1L3iDcHQ+XKpfq/8BloW6Lzo3ZD2BMXvId3gi0jOq2CA0xNwxZFPABfeOCHwACQntUu+tuCOFWf
Li8CcR4nTYdB7a/P1T8GoQoWf0cwdjG9a94I7minmtYAznz2yfWPSkC5RYe7ZvjBVuOJ3WU1CPvK
UC8kBqw1KgwpcwAUT0BQ8sGaWbRJ0fVgPWFrZ3JCEWvUnahMCGtsPxW2C5zHXPF5O8DV2vm9OwnC
cqObxPcGY0nzbOsa8DdRK6khYB5jHmKNBH2/sF2fA+pz/ht+G1gOGSoYngPlZfktW3kwP2FND8QA
RdR6/i/Ad8V30lMDjD0MTeWPITAw0FZpBkIvaYXcEgzvScPVdFAkNinfgDhNdwr7wVBNjrP4QI+X
OmnHgV56W08nECKETvIUMMwxzTK+DsYJhgvGLPD2cz7I3gSp8oNXk6uC2NfwrHEDyHZDFVMMmOym
GcbtII+SNxp7gH+s97j7NRBTpVPGH0FyGR+YosDQWu4rRoA8m2vKZTD0ML8p3QY668dMGvgmKoP8
44EzWqzUA+goXtJfB/8K70H/EhA/1evmXYXo1mERZhnE26qDwWCYLntM+8CwyYh1EHgG+HsErBBo
o1YM3AO5rjJKFMHQTqijzwBpuzGeeFB86gBxNegfa98FkkAYIyYaW0D4y1EDo5uBf5BvqtoH9JP+
F9R7oIriVqkWmJeZjpnKgXW++TNLPOj79WVibTBtMyyWtoOhllBZSgX1qnLNnwiBk3I2ZUC4Y/rF
8jJ4rL6DSlGwmgyneR5iNoc/YRwC4S3DeoeXAzUQGKDUBvb+3UM8KOg/V5G0ImlF0v7uXjw+Me/F
vBfzHixlKUv/0QV1qcu/URL5r/qf9roGBf0n+dOJcwhyYuwS8I4ObZWfBkVuF68b6Aqd5z9577Vc
iJ9VOrNWFLgPCOPFuyCW9SxznYPQc2V6VJsK3BLnGbZDQPLFer8Awx5xs6kuBCrkl729H8RnrSS2
Bj2ZD6UBIHzGEf87wAgxTk4B75dut+suHCy+7M2vF4K1T86HURIkLHzH0FaH7P6Xpp8rB+hX6t6P
AO2g8r7rU5AOWxaZi0BolcQTJW1gvmKoKO4AOcrxguVdMPe1NLO7wHDfMs+RCy63q1fmOrBVDS8S
NxyML5qnhrwGOV1STtyqBbytPSs0APMR2wr7z6CVVXf5PwJNZIJQAiQLVYSdoJjVxdyEwJtailoO
9Bh1sBIC3Ke0XhowC19Jt0HeqG8XskFroh8MfA6CVxip+UCaLe+xpINlmfGE+BJ4n3OL7tUgDqeh
sh3EtfIQWx1QnxNfkxaCqvknun8B/9iA3fcORH9atHPpumDaIr1r/AIkmeN+H0gNNY/yFSiN/Utd
a0EaYmynhkMg3fehuhl88z1jfUZQW4gfiqEQUtWB9UvQL7KQteBOdb/sTQW1hlbXWxJs9U3fS/cg
LM3xekgpUDzaCN9dkAfpDQw1QTopZAgBsN42LdK/AG9T3wrRA+mf5W739QRLI+My7R0wdxbtnAOv
xZ/uvQB6tL5H6A3mNYZo41tAlnheHAX6TbWK8X3IPJreM20eUEQ2GWeAUl/oID0JYWmOKNP7EO61
lY3cC56A3+g9DLkn3fHqHRCrCvM8S0F+Uvw25BfwDPWc8LUEU3/LIPkGKOWFpeJZyDqUEcjZC2E7
QyJsKWDeJG7VfFDydHEhzAT29Y4Njjhwxbqqe+8B0OXvHuRBQUFBQUFBj8efTpzvN3EOMLaH8Mz4
fmob8CWnv3/7efA8l3MkczzknxRKerqCaa1Ux9IXlOt8qn8MUr7emlnAJLWBfyqIy8SexpGg6srB
rJqgv6Z+r38Fwiemt8LiQH8egzIDmKhd1k6BabqxnHk9HOl8eNnRbDjx6umembugd0afeS89CyGz
m2bXMkH6qn4fDW8FLsVZJLMz5ORvqrjidXCYn3nw/MtgulxyZ9wGyKmX3cRVBO6Vz+1jiYfYlXG3
ohdDetu8Bt6p4O6eb72zG9yvuHyu2mAf4ugVeg+sU023bbNBzwh0dvUGNSSwR08BQ5TJ6HgSdK8Q
Ks4DfT1x+lxQn1aK+q+BoZdxgnwSDE7raxFDQS+hfSQmAze0+coV0PyBta5dEBjqO+O5CvKPhlri
aPBleW+4h4A+0Rcv2MC/hQqm78H6uvVoaFGw97KVEd8GLeA56KwCllT7eW0TuGYqsrkDuKZ7X3Bf
AENV+TPPJtBDAzGeWJBek3poT4LdYR5mbg/MkDItmyH3knDAVx0corzENAn8owKDeB+8XncP73Vw
vZa/L30PRO6KjLV+D+ZmhkzxfciMydvg/AJyy2bPz/dB2MehI+yRoIrCu2IjUNcTLb4MBkveTqUH
qC39zfJvgulJ613DaMitkfu+eg/8XQJjfLWAz8QuHAT5lLzC8A4oF/LH5Q0HeZahkmE+8LG2TO8J
xqetqy0HwVfVH+lNANNblAh0AfGlwEktFORWem3ffAgZYFwlZ4B03dLZOBgCBuWE4X3Q6grPqtXA
4LetE3dAYKnaV28A3jZKvKcSmJONyeIQ8L6QH5PzC5RZW+K4XYIn0iuPKfYd5EVldxBPgJ4ivB7i
+buHd1BQUFBQUNDj9KcT58rXq7Qodg6Sxp8/524Dzb5/2tNrFcR/WMtcbzkw3FTWqoNWXdnGKRC+
Fb4UNwM7hCzDXNANaqb/RRCmimXFTNDfdhqy8sAwVm9lPQbMFr8S24H/pLNkfkUQJgjz1CKgtQ4M
YDPcvXpvgjwYmhhebNkwDaI6PFW6YjK4aqZMSX4FBCFnd95BCDtd5HTJeDDll3y+8nHIfHJO96Wd
IF4a23ngTcip7LQGXgLjV9aomBlQdmqpvaXC4HablKi8KpA7KzfBPhncx/MC6V+C5WuHrXhlsNQJ
GRUugGEQd/NaQsgqRxdZBudPnqNuPzgq2O6GVARqCgelIiDvDa8e/gn47wnRxs9B3aF86YsEb+Wc
vRnDQK+u91NeAuLFa5IA0m5potAExO1ClBgK4jizaHoNzBVtN+0bILSo0WJJA+ublnXmIuDPd77p
nAzqfP92zxeQ8WT+CS0OnPX8c7VtoB+T4sTq4Dgf+qm5Ksh7xfe0W2DYJRXVuwK7qeM3gatc/iKl
C6ht9FX6NdBUwWDcAVoPTdX2gKmlvFNMh5LGMqUSUkBuo5/TRsP17sl6/gsgYRgmx4H/vNZWKwf+
K/rbDITwF0N/CQuDrE05jdzFIcOTezw/GyznzRO1L0G54uyoNADdhlGPAfmEcYI8B/Qs0jCB+oM6
S50IxgOmo6ZQ0GZrgtIQDH1Nk43xoHRSLVp9CKRp3+s/gfUla7bpPgR2qyeEKZBxNKt1xj6wj7W/
5bgMxuOG14zvgxQl9zdfBo/o7u26Byi6Q5kD6hb9rrABUN0VXUkQCJP84gMwV/Vfy10OlS3FTVEB
iEyxLHMkQc7o1EH+6xDaKdruyIb/1p+nCwoKCgoKCvpL/flVNcZ469+9ATWulJxUrihUpnn08xVB
U6yRYkfwt83skt0QxK/Nm0xRICq8rySBOk8YpNjAWNucY38R1BVifX0YqO1yV7vLQKCO/sDeDyzP
xYfomyC/c94mXxEI1cIuh80GTzP/D/56UP9U43fLmiG+c6Ia3hx8Sp4hrQeoam63nOZgTHDp5ILY
Kqa0+TMwfBweEvMscNM2MawC+E/npuSWh6jJsTPjnoeY7faP1TIgJcW8ZokE+/GQk8IGMFYPGxeT
Cs4r6UVudwZPMU+7+M1gNlvWhi8H0e561euAsPLGPeaFYBsvfK80AtmqpqeKIFwQLkjVQXvTMz3/
PVC/VndKFhCXaFOkNuB7IMxV24ByQquhzwT9K/8aXzTILS1tbD+DUEsrobhBdyv1XTtBLeLZJG0F
MV6YbNwJHBNKe78AvaiW5foFhHqGXbYJoK5Xv/cPhlDV0kAuBtYL1pu2TmC9aFimNwDr6/L0kAhQ
RweG+p6FwFn/JPUnsNcOOSIshQiHaZ7hVcjr5R8gzgR/U09j/xooUTJmiUkCJU5ZJF2F3I2uUt4j
UCQq5i1rGLhfck8NlIWs4lpfoTuod31pnl6grHbmZdyEol9ZB6qNwLnRtjdkH6Qb874MdAUtSanq
7AeOmhbRuAIMtQ3ljAnAQZIZBdoPerRQGgKKFqufgsD7SqZ4CITZwmHxPNiOWtrLpSF6cOhQiwxm
zZxoTwdlQyBJGAq6zjUfoA9R3ZoH/FnePd4SIBw0bFWSIX+0MypvKAhe3a29Db662k+qAkIttbGy
CDxn/b3VT6HUzfhTprEQNjaxfslECOiermJZML5q62d5BmytI74PufR3D++goKCgoKCgx0n8sw1I
t/VGeSI8fb6V1lkBrtnmG76EvNDUfvfaw/5JP/RaFQ6u3ffOJa0D98jM7Oy3QKmQH5v/IqTXPn3w
2CpQn3YvcKZCbuWcV1RAfcpyPvRbUI759yhWUFLU65Y8EJbJNwUJQrfZJeNOiMuIbRPyOvgauMq6
3gPxjGNuTAboJZ1HtHUgTsqskvkTiCsNI61ekOaH9As9BkJT2wVbZdD3SPsNkSDk+j92doDS5uIZ
xfZC2IOIr7W64NhhVX35EGoJ7RoTCpJszDUPA/f0rOnJY0GNlaqaJoHniDDU9i5cnJ/0UfZYyBvm
i9DqgOnH0P2JN8Fusn0R0QGyu+SP9AK+r1yz8vdDdpus9OS24H7LfTd3Kahn/a+5zoD5PVNAagzW
osa2dAJTNZPVMgTUq/pJcSIolwMvuipC9pXcskk3Id/pWuQcChn3c+LVwZDcMbN7XgWIXBwSZZsG
lnKm9wz7QT+rPem5DMIp/SXRAY6FFs38OoTsdgwLmwSGaPOTlqEgRks1HRshp3TeZ+IacPbJtfqm
gnLGv8h1CHy9PG/53gXfi/7VzgiwbpOyNQViPw55xjIflO/V9XoYOKf53nRPAXe42l47Cjbd+Ipe
CbQ0mkp2EMeq4WoEGMoLHcT5EPVqqCE8G+Q5po3WjmBNtn5s3QHSM4yUR4K+WHiaAJheEVV5KJhK
GV6V5oPQRUokDPy5gZvql+C/6VupVQGtvB+fBKZhcjwbwdRGfM/wKRiXSW/IpUBoLUw33gDXjbxX
/S3BleVp7twBvhxa6X6QQo2bjVVBbG8pbVkJYbdDBth3Q6njpdKKlgKtt5wRugnSJuVt8c6CuJcT
X4h0g+mc1l8s+ncP76CgoKCgoKDH6U/POBdzWds0ehUSGpZUaxshz5S5OjUBrlY+WevoPMi4Gb1C
fA1+nLn/wvqnoUSuKanYEmgw94WwbgKw1zDeYAeauA5kh0NgW87G9E1gcj6xvHI1yO6Ymnh0H0ht
9fqWi2DYb3q7+izwNwlsURRggHpNnwryaSHHsACEasJA6TIoJ5IXp98BpZ/0oyUVzPGRZWPsIFSI
O5NgAOPXYakh7UG4rlXT64AhyVbf1BKyv7DVuzQFMj7LrXdiKzzx8xM3I9pByqH8vv4h4Kgf9XWx
PMgqc3/F9Ybg3ebsmd8UzM/ZzGEuEL7w57vfhNwXfOX070EbmuZ0bYaQBcZOmgoR78WMjN4O+nwt
RKsI5snOxvnjIXJV6NywOqCfwiC+Aa7P/bc9KZB/3N3O/wl4DJ4y3logpEoDzW1Bu8dAQQSxtt5e
HQwuwbsy3whCe6qxCOJ7R85zTIDQUNOrQiNwDfMu1naA8K7YW9gLlp3GjtJN8JUKtNX7Q86p7Lys
geAvpVxmLng+UeKd34J+Txvhmwn2T42zlM4QuOzzBYqDZ5Z/DoMhrkHYyOhTcLt/xorMNyC7t2u+
9iQEvtaLiwvAMtM0NlAF7KnG1+WywHB1h/IhMMrYXaoK+au8lRgHuY3cc712MC6XIqUfIO6bsBrm
iSAmibulBqBMM3c1mcBYxb/X3xa0w8ImRoA4VEkSSoGerVTXJ4LJZRIpDr523mm+KSAtFyaLyZDT
My/g2g6BquokvR4EYrQ1yrdg2GQ6brWC95wvzXUCQl8OPRq+CJSril/7HJRx+hYFENfrMw0/QbHo
sDPicah8vayhRA+wfGAoaxsOUi95q70VRJSIyAxX4OSKX/peaQHVeXonB//uYR4UFBQUFBT0OPzp
GecnJzWb1+V18HvUbspikE4ZTBYZGBXxhbwFcjq5V+bVgYxx8lRXWQgJS1ykV4ZAk4yPbqSD8Z3I
CpGjgVmeE5lDIeq52GKOWyDVNU8xDoPIytE1n7gEUWvimpbuD8pp5Xt9GAhRbNZrg/idfoG1oF8X
vHwJ2m7QM0D/VC0nhAAbbE0cW0C3+ZZqr4BhkMFi2AKSucTCsCXAZn2quAH8ovu+ew6U3VkkLupT
yJ+hJ+uh4J6cNStjARQLjdgpVgbDFsfUqFZgrumICLsJvonZzdMqgpCgfWicBuaFti9srcFzzddN
+BHyxuodZAfkeIRo8wzwfK6MF/qBtl3rJI0Hw07zTpsHtBHaKDUNXGdct10vgHRezfTvhoTnw6Pt
oVAsKeZa+HtgDGiLfRpIAfV4IB0c1c0LbV+DebNxmaEDWGYbjkp7wPxAPmroCbfapGVnHge/TR+s
fgW2btapjtLgnuBq4w2D+69kJGYug5yKrvN5H4P7OW+N7Gngme2OSq8LyreBfs58cN32NNPCQIqW
TmuLoFj96JVRaXAh/NZL6RGQ1Dw7xNsfsnu5XvPMA2GerqgbIdQkNRTXQsw8W0OxIwjrjY2l0pBl
cdaS8sG/MvC9+i5ER4a1sWwA22LzIYMFCOivapsg/XyWlNcQsmfmvuOygbeWx+r5FLw78n3534J7
i6t1bleQnmeO90NQDd4M8Qzo2XonuT1kn3cu9rWFzHHOYp62kHYjp2FOLmSPdo51L4fso7mtcjqD
8ZzRw1wwlhO3CnsgZJXtaeMnELbYHm7bBoaAIYcZkHigeHLUToi/E9czLgJC15vCbQ+g6NUyl8p+
AYE67mGaCW54T5ovN/67h3dQUFBQUFDQ4/SnZ5wdp6LCEmqB9oa+jAQQdWOE4TSkv57zffZz4NLu
WVJsUGt4hXvVb0Plr6stazIGlJOmefJ9kBpqR3QLqLW9ea7vgUNCV1oBq9UVrjKgpeT/5HkWxPIR
7RLugzQ1sEa5CdrP4hq2A6XEl9HBP0dt6XsFTKP8A/x3QG2vnJC+BD3XlG8fDsIm9wB5EpAC0k4w
rk2sHVsR+E5JCnwK/nYZje4XhbwBjm5pWVC+VU3jk/Xg/LELhxb6oF6Hql9VeAnsXfXFMSvgl1Xe
TUX7Qs7R+0MulwHP8LzXU1eBpX34KxFHQRoSeNM3B7REZZA2HrRxxqvRVSHvSb2++h0o7/gauVqD
4ab6rXYQXC96jrjLgq2rdbHjJITME5pJR8D6kaGj4SeQdjFPOwQljsTPihwCruM+QVkKnin5y3Na
QpEpsSeiI8BZ0Ruq1gaxrvyRbIEiz9o/L3YHRIOOVwXPdPdV53JwpnhSc7eB97hnuccL5u2mU6ZQ
YLaw3/Qx2C9bN4bYwDJYDhVGgGWuVF35EkwTjJ9YjXB92v0bzpngWqjl+AaCZY/hLdNNiN4SUtG0
GJInpg57EAbRCx19rc+DvZWtQ2h1uBC4NzGlKZg+MEXZh4PjOcNMc3mQDUqCaxBo3bU0cR8kmXJH
Ka1AT1I3+G+DVo3njN0gp4k6NJAMmujtqqwB7VnlkmsbOKfJ3+gZINqFGnovCA9E14p7BwKTlIZk
gRwupqgXwZFm+UQ8A3quPlhPBONGeY/2FITcNVsoAuq+wB1fLzDvtO8LN4G+2r9N7wJhP8aWskdD
1KUyB8qvB0+2ppv6QXR6fKmYlhBuTFgfnQzH4tcN+cUGt9anvHIvBOj69wzsnJycnJwcWLp06dKl
SwuP9+nTp0+fPhAWFhYWFvb39C0oKCgoKOj/VX86cdavCon6YlBtrrr5YyFLSZl5LQZKTlNtlspQ
flI1+Zn+kFik2pannwHt+5iWieVAvOW/5UsA8boeIiwC53t32p55Dazpsd6qFUB3ugfnvwF86B6Y
XQd4EPFNQjXQr4hN9EzQ6wsPkEE6oKcJq0GvTYnAafB+5At39YVArZurkraDtkjrT0/I6S/b814E
x5l7qy/PAO+WE71OVAPLk0/sLnkBzFWqa2UOg57irRMyCZ58s8inFg/4hjfffPcGVKpQ8b12kdBq
Tr3B3tqQemb6k992hTNfuofHecD9Sea1+6dAbmxJd7wJpqnmE2E/g+9e/k/ZW8A9OedY9kdg8Jns
xrYgFBfmC73AfVQvIX8ClqZGV1gF8K5Ul7IfclpLS8VW4IsM7KA3RG92PGcTwGQyV7C9D/ntnbnu
+xCIME82tYDQRdanrachtn54ZzkNvM19U/Vx4CQvP/caSH2E2/oHIH1mL2UYB7ab5nahH4N3rK+J
ZSDQWfkkUA3EaINuvAHZ3dw7lO8gsMgvCFOA3fJIsTKc//h2Ylo6BK7JcdoccBhNm01lgTlK3Yzy
cL9T+lixJ9iftHxt8gBpYppHgAxT1o/mLyHsl7Bp0cMgzhiebB0FuXJOzbwU8Lv8FfQXIWNM7j3n
p+Bbr55Sr0LUqpCfzc3AJJre198A24jAIPEwZGgclw+AHCep4Vcgen/ISVMsmMrJS9Qs8Lf11xN3
gacpO9TyIL1gFAw6SFu145YaoFfRGwd+AHWT1k2fDfnL3FVUB0ivmPYaF0NeD+cB7yhwnDJvMayG
hPUJJ2J2glBBPGRdBmo7tbp8GezHYrfHXYHAONcS19tw2HfIfcIEp2vcbn5L//sGduPGjRs3blyY
QBcoSKRPnz59+vTpv69/QUFBQf9TOJ0ul88HM2cuXvzLL3D16u3b2dl/Xbxy5UqUCA+Ht97q379+
fbDbbTaT6bf98fkCAZg2be/eS5fg6tWsLK/3r+xPRITZDO+807hxhQpgt5tMBkPhea9X0zQN9u3L
zMzLg9xcRVGUv64/oaGyLMvQqFFkZEgImM2iKP7p+opCf35VjR2uTa514M13X8lZArbaYWtih0HR
5m2L1q0E2lQu6EchUE55S00Ffb5X9d4B+othejtQjYE3XUYwh4e/Elkb5FpFF1WoBNJMe4OQJqDv
sEWGjwNNU+3C26D3Er6jDQjzuCjEgFaRHnwHpvWCwzET1AY2W/hGCN9ap3pCHThz7H4Trx9O1on5
/MoV6DFWyroTDilbKuj3P4KE6yXfLhYOtrdMfeJfAams+bOwj0FCb+f/EFq80dw/phLon+rZ9APh
3YRjvAVdarWMu9wRbg9e1+7sSsiJcB3OqQDO97OaPMiEMDG2XNH3wVTWFhmyBDy98k9m74HAbE9L
7QgI7cQD7ALhF8Mc0Q7incAky9eghMpVjR+Be4e5vxwP0mrfp55e4MtTX2Il5C9ydcj9CMxnVEde
U8gemnEv5Qdgvvnr8IHA7EBbZROIo+TF6jQwr7asMW0EYTid5VOg5wdCvWchpLfpnlQPNKPksLUB
JV3MMMeDO8o9TqkOrs4eg6c+sEYb4u0H4rPCMes2CMuNuGM3gOuJvJ05DvCkuL/K3QzxpmhD1DuQ
mZtR/VovCOkatqREdQj90jE29m3Ivu/r4b8A/pycN9XzkPGWNyt5Fpi3W74yfQ1Zp/J/8d4FTydv
rK8EFMmKnxtxDgwHDbWsnwEvql280RB+KvQZcxNQJ/pb5Q2E1BhXuKsbZGrCSnkQ6B+Rpn0EWm9K
0xxM3xhcxkRQDwtN9WMQ+En7SJsHvomBz7SfQXlSed3TE6TK2qdCLdCH0tYjgmOdtYR8GkpWKuYs
q0HEgKjLkbXB8JH/ZS0dwn+MdkbvBtNdcakYCocOr197Yjn8fPay8+rHkBavGLRrf90Hw6Ps3bt3
7969cObMmTNnzsCtW7du3bpVeL5kyZIlS5YsvK4gwQ4KCgoK+vdMm/bFF/v2QWZmXl4gAGXLli4d
FQWCIAiC8Pji6Lqu6zqkpWVkOJ2FcSdNGjmyZcvC6yZN2rHj/HnweDRNEODpp4sVi4j4tT+P83n/
2hu4dSsz0+ksjDtt2nPP1ahReN2uXRkZOTlgtUqSJEH16qGhdjs83t6A/n8mq+7f93h8vsK4bdvG
xEREPL44fzpxdpd3Fs9+CoyXjAvNc0HKDZkUfgA8Tm97TzEQiml3hVRQV8nbmQDCE2JrfSxIcYQY
NoO+Q33b/SIYny3+XaULYDxm2+m4AWodfuQmEMMQsSgYTHpv/1MQeEbwsRk4rDcTc0H3Ckf1e0A7
6qphIN727zMUA2uFxm/UfgPyz2eV2JYNOWWT9vg7Q14L9rj3gjqj9LGi1eCXDlcv7M+AlvtDTpd/
EbxhacfNxyHl47uWTAWM9QxLs0ZCdvfkJSmnIHtxyqBryXCm/53nk6LA+r6jScjP4H6Or8p3Au+w
24dObIH80dn709tByJ3IiJgtYGxoMfvrQsDpK577EkgDxE7CMLD3tkaEtAVmGizG4WBsKieJkyE0
V1yoXQBDSeNdxxG4fytvkh4Lvi6ub30vQtYZfZAhD5QGxpwoHYrMCyll/AgyJ2QtcY8EaSF39BzI
c7l/0i3gK6029JlBLikvFdLBW0ErrTUFubUYkjsCHmg5F1z7QBKNNR2VwFjb4DM2BtMUQ2XH82A9
yS3vAfCleBZkpYJ6mhm6FUxDzTu0EFBOqu9qVaFI09jK5aZDeIOIWNs58DzvuiTPg7zk7MuezuDq
pU3wdwVHTfsFy0nwNgskaWXB21vdTmeIfSNmUdRZsM6ztrMUgfuOBxOz3RAYEhjoOQEc1+cEVkGO
wbve7wJhgfyytTEElmh3qQfmzyxfGFeC8ZCcLZ0EZawWLnYBxRhI8RYD2yzDSGEtWL6UHXIZkH+Q
VoVfg9zN/rOBrmCfatwqdoTyw4o2iE2FYgOLTS+WAobVwn1pBMRGRA4LvwFR4ZFfRnWHKyN+KXH1
O9jQfkvpvaGQdN9XzpULchdxh/3NPTDx5QAAOmxJREFU/zNItj/eD4f/SvXq1atXr164P3v27Nmz
Z//z64KCgoKC/j0XLly7lpUF8fGJiWFhcPv2gwd5eX9dPLvdYjEYCuM+7Ny55OTcXChTJi4uLAwO
Hbp7NyPjr+tPXJzNZjYXxn1YerrfryhQqpTdbjDApUsej+cv/IGw8HBJkmVIT/81gX7c/nTinPzG
dePNl8FnTb2XNQmq3+q2vksG+CN85QIvg35aNvMtSOe1UxwHoZUwSFgIeoJ4hrdBv6xf8DUBsZQY
JX8O2k/CPTkRuK71CzQH4UVhseCGwBThdXEaiJe1+2IjIFY4reggDNcPisdAC8EhW4GvhK8CZUGt
4H5J+RrKjkp4o+oncEf1evZ/CBnh8qH83ZBo0q47OkHyc+o38ueQVSulz4O98InjrZufLIPbpjRD
4H2IHGeamjcb9MPKZ87RkBnjWux5BTwL7BuL14D4nkV/LJEAzAt5NnQrpN+Pyi12BLyH0rsmxYL3
nLGpeR84QkLfCrkLwh0W6CXAnC0uDEgQFjDo6nXQ31WvO50Q2s34klgazHuksEAUXG+b9FLOafB1
0vKsDUA9yADJBXoXamnDQf5R6Kafh9TU3BD/XrA1c1Qwtwd5iFzNMhC8NT2ZnvcgNFPuq0ogBnhZ
uAnGcnJ321kwh5nDzTFgnG/f5skAoQhtuAXiDiFJeALUotoHge/AtlxOl26A+SVj6aiZ4H3a1yW3
GggdaG08Cr6cwBPKXPDtdD6TnwOBFqb1Vje4jO5ZuZNBXyi8pXwIxb3hfYSaYHQJkdJEyDZ7FmoP
IKZ76C5LPoSeNqVrpyCnRP6S/F7gVrXPdTcQR7rhE9Cy6UsLMF+2VbHmgOVlw9OG46C20I+pPUCN
UXcI3UDtpx8Tb4G8XtIDdcDU39xQ9kP4xtA5js7gXeEtIV8F90e+2r7KYDtmsEuTofjW2POhFyHW
WGxF8RGgFxU+sgTAfljsYTwDJd4vbUlsA65A9m33DNj63E+bDtyCe91z79yqC5bifOyNA2WOjhAF
PPPXfTj8IwW1y0uWLFmyZAn07du3b9++hecLjgdrnIOCgoIeD0XRNFWF3NxfSzb+fHuBgNcLXq/L
9dtSO7s9LCwurjBOQdyH+f1+fyAAd+/m5DidhcdTU8+cOXSocD82tlq1p5768/0tiFMQ9/fPR1V1
HTIyFOUfnd+1a9u248fhwIFDh27dggYNnnqqZElo1qxVq1q1/vX+FMQpiPu4/emqj2y/2iRjImQE
6JDXHuRvBUW6CUIPfY8WDZRkDSdAmCysEbYB6fp+4SgIHwnLhRrgL3I95GcTKLuz83L2gnhLTpID
oEUKL4gjQN+ORygLwl3hc3oBY4Rq2g2gM0OFSqCLVNargzBeaCUUA3EF0cwAnyK8o2+AohPLLGh8
GVok1p7ZpQ3YnzGXj68FV7dmyBfLgtlsOR2aDQeSDj99qALcvmwx33sL/FZrLc8usLcut6DMGahe
/bn3ns2B0k2ql603BIaVGVi7e3do4Kiox3wIse+xJm8eWBfGtCiyCmR/2I+RncCzP6dpamlw93a3
8r4Hxmb2GiGdQMvURfkEeHp7ZnumgPFJ+V4gH7x4P3H/ABfjb72e8i0kWdK/zbgD3mzPGFdpkB4Y
LcafwOyzvmLrDpwRvFJ/kC4YPMb9oAzUMgx7IW+Aq6rXCqYl5ueMiyHMElLH+jVEVQqpEdISzCfF
COUIMCTgc/aFkHvm8zwN8V9FfBKWBDG3bH57PUj8yNbTsQyMgtjSngP+bcpsfxjkf5P7TH4iJB9J
WZA0DVSH2icwC/JDlDDvS3DzeOaU04tBbiDc8c4G9uhXcs+C+xf/cn9peHAs81amFQyfS5H+3WB/
wlpSehOSjRnFnfPBOcVz178LfJW81b3fgecz39aAE5QU1ggLQSrNp7oMxhjjbnk82CvYo02twFbe
vNr2Psg1jZmiCIGu+n4xEzI/ysvS7sG1ubf7pCdAxubsEpnXQNmlfOf5EaK/jnreuhzi9xWvn3AT
xG/loaY24N3lr6J9AI7Gcc/GdoO8Cc404RXY9mDrsWNRcPTna19d6grp+/P2pXUGZ72srintwD/K
MyPl+8c/YP+ogpsA/+jxP6tWrVq1atX659vuu7rv6r7r73tdHrcuU7pM6TKl8Pk96nUpuO4/xSrH
Kscqxx9/3wq2V0ddHXV11N/d+0JTMqdkTsmELwZ+MfCLgf/64/NfyH8h/wV4yviU8Slj4fO81+Ze
m3tt/u5n95/77yfo/6aqiqKqoKqqqmn//tbn83rdbpgyZejQZs1g48b58wcNKtz+/nG/xn2Y3+/z
+f3g9wcCilK4PXjwo4/eeqtw+/D5P7/9Ne7DAgFNA9C0X9PYh7eHDp05k5kJZnNkZGJi4f6jrv+j
24K4j9ufnnGW65axxswAc0b46vA5oO/iScaB3owXeBWE3VqsPwHUb/S7+psgdBDfNKwFsalQRkoE
8bDQ07ACpN32mJhloL6jf088iB6eVCqA0IKmkhn0Q/o4GoPeCCN9gGgEoRUI3YWn9DeADnod/Szo
GawVe4H4o6hZDoFyWC4WmANFtaJ6ozsgrpWRrkJmpjjm6h246UxNu/kDXE6/ec5TB8qvbpZc/zk4
//EPXU8NhLDBxTs7kqFCdNlllbfC8ydeuNWnEli324qZnoU93XaX+bYYNNsXczd/HIScOpmrbYbz
lfxvlL4HWR9qR5XJ4FucUSR5IRj7SjOLlgN5lP3J8Cjwfeyflfch5PjyVuXNAne5wCyhC2Qf9t7X
s8B0wvCJoTkYvhE2BCqC2Es57hYgEOZ1yUlgnmb50fQsBGb4X/ZZIedI3ovZF8BWxDLXMg6U+prF
cg6cV7xFpA/BWFoubjwNfqM+VzsGysXAMM9VsE0xzLHtAE/H/LWBaeD/ytcu6wa4PlBuXzVC6pm0
gxmrQPpJbsYVMCwXplvGgnejV5S6gb5GijaHAV+KVfMD4PL7u2WdBrE2M+0/Q175/OF50XA+5dZ7
rhJQ6nD8mCgVYs5ZDzoSIblp2lP5B8Hbgyz/eLDUZoy8Dsxl5VSyIWxlaBXzYhBWCvNNJ0DZL16W
loG837BReg/UuMB98SfIDc9/OzsTqEWU1B6sr1lPWCtBzLyQTnprUHP9vU1rwNDJ3N34BBSZFr4+
bD9E3C4mxS0EeYulruMGqLW8rzEaor+Kt0ReBFm19Q3T4dCLP/98pQbsTzze7szzkN6ITYEfQVtg
nB0lg/dpXrj/CQidpBZSJeDBXzFsH62gZnnfvn379u37/fmCmrtGjRo1atSosNb5cYlsGdkysiW8
/vrrr7/++u/PO646rjqu/ve+Jn+n8T+M/2H8D2C32+12+9/dm0L16tWrV68ejF82ftn4ZYXHJ7af
2H5i+0e/j3Er41bGrfy7e19oXat1rda1guKdi3cu3hkGMYhB/8Ljd+7cuXPnTghUDVQNVC08vq3L
ti7bukB/+tP/736SQf/xFKUgkS1I2f4906aNGNGiBZQuXaxYVNTvzz/cfkHch/n9Hk8gAH6/1fpf
3YTn9/9aQqEoHo/LVXhcli0Wmw10XVUVBQIBlys//9fjViuIosHw25sRH477sEDg15sDVbWwDvm3
ZNlicTh+v/+o6/+ogriP259OnLOs9xOS+kDcyPDtZT8E4RM1Xs8CXuN1LIBPz5UugbhBbCp8BgT4
RIoB7XOttdYPpNZFR5ZbAuIh62vR+0GIUF/z7Qdto35LPguMFseyBASLvlEfDnoyoZhBKImLWkAt
/SPBAPo1Suo24IFu1L8HvRUXtP4gdZbrSgmg1Fc/V34GKcUwzbobntgbW7pRT4jI1X8KOQ1RgZJH
zTth7dklWVvjoHTHSmcjXFAjt/oRU2NICrkfe6EyJDRIO6HthMgR9jL2zlC2etgqywgQOmitE56D
5EVy8pVP4EGCfVNoU9BrE1buO3Aue7Dyggx59syfknwQPiNyceJG0GdbZzu8kFM18IJWA9TRXkfa
aTC0loeJ30LM+ojiUc+DoTPJ6nhIPZjV6F5FCK0ZWjHiGdCK+k5LhyE0KkQPmw32XZa70i5w/uz+
2T0S/G28x/L3gXDV0NUYC6TrvX0p4Mrx3PPMAMtY04vyAVCHK5O8LnDf8+a7ioA3L9A60wPaFuMu
Xy+QNxra2qeDe7j76ZxnQMw1z5Xag3WJeR+nQW4kvKufBRF9nO0piAuPjq56DPKnuJ7NuQ5F7kU2
i70J0lfi8vT+kLA1NCpkMmSVz1zqWQ33v8ok5yco/XL8k/YtEIgV8gO1QZxknmWZBMpcuvMx2OOZ
pnjBtFw8o18Gg1PsKFeDzD15LTJWQnSCPd4wDeIuR70b8yOY3zZ/LZ+A5PqZPd0V4Pb41FYPhkG5
F8ssL3IBHFuKvBNdCgyLjN1tp8HTKf9GoA9ENYgpEbMfQpbHzI1qDLfevtD2vg+OvnEq43R1SLms
V9OPgTpK/jTqBjDTH518GIzzrDPl22DqYCkR//zjH7D/TMGMckECPXHixIkTJxaeHz9+/Pjx46FE
iRIlSpR4/PELEsR2Ce0S2iX8gwsSSCABtPnafG0+fFn3y7pf1oUNGzZs2LABMjIyMjIyICoqKioq
Cjp27NixY0fod6TfkX5HQBwiDhGHFM7EFSRM34/5fsz3Ywpn5u6su7Puzjo4fvz48ePHC8MXPC4u
Li4uLg4syy3LLcvBWd5Z3lkeRl4eeXnkZWgR0SKiRQQoVZWqSlWYkTsjd0YubC66uejmolCmTJky
ZcqAp5Onk6cTsI51rPv90y2oMS+aVjStaBo0WdpkaZOlj68fNbQaWg0N7ra+2/pua7j/w/0f7v/w
++f9sJI7Su4ouQNKUpKSvzk+kYlM/K/ex7d4i7cK+19scrHJxSZD3S/rfln3S8jqmtU1qyvsmrFr
xq4Zf/z9ubHmxpoba2B66emlp5eG8+fPnz9/vjBs+RfLv1j+RRh2YdiFYRfgs4OfHfzsNz8sVNDe
8LThacPTHl3b/7DNaZvTNqdB+U/Kf1L+EzAuNS41Lv1N4lyzf83+NYGTnOTkn/939KnvU9+nPtiS
viV9Szo4nU6n0wk1F9RcUHMBTJwwccLECRB1N+pu1N3CeL6DvoO+g9BjRo8ZPWZA3qy8WXmzYOj5
oeeHnoc2MW1i2sQ8vnH1qPd1evfp3ad3f/yfG/+vU5RfE0xF+XOJWpky/3fC3KnTyJFr1/7zuA/z
+32+gpng385IV6kyePCkSYX7EREVK9auDXFxXu9va6Bv3crOzswEg8HtzsmBWrXKli1aFC5fvnfv
1i3Iy7Nao6LAaHQ4wsN/H/dhgcCvCf+j/qyQZbPZbP798enTp03btOnRz79u3Vq1ihSBhg2bNfvt
zYgPx33c/nSphiHfHxq4C+HVTMtCRkOgBFWEN0BvKHwgPAPCcnGVYRPwlOCVMoFVwl5MQG9ljnsC
aMNyW6eNAypqd8WzQDveFpaD0EwcoLsBmZb6Z4BIFtGAQTAjAankcwf0Z+msJ4FQXaimO4BveVb5
BnRBG+qXQO/LTGMvkOYLoVIrUPsqFzynIbyEw1rhOlSoWmp825ngvSt/Z2gGZrFsO1t/6OV4flL7
luBo7hkdMRD891OG5R4Ep3DhSGoShMwz3A3bDcWXRQbieoA+WB4gFYHQ4UVXmfpD5EhblTw7RI61
fyklgXlw3O7yO8B40DDRsgrcjbIc9yVQO3ku+ZwQMjPkmdAW4GgTc7bIJYitHXUzJhVi46JioidB
pDc0NFqHMv2Lhpc5DxE/2s6F7IeoA47ehkpg2qWPdH8CUjPvW1lboERy5CB5H4S+YCirTAebTfrc
uxkM66jgTATrV8bS5sbgHeixB0pA9jeZatrn4Dno3uXTALOW4FgJpjjteBUNwk6b+pcKAWsTw21L
f+C+ajcvAsc+0/7i+ZDd0hVIHw7+5/UZFIWsJqkvuBQwvKW/EtIc3Ku9SfnNoHRqzPHi88H2vpwW
vh9cLX2feY9D7IqIROstsO81LTbtgvjyER3D4yCxUVhR6+fgbZV/PmAHxyaLKo4BY2v9Y6UEZFRJ
eeVuf/D/4N+aOghyEz3LM7rCtdVpFc70gssJ98KTlkHuobzz7uJQ8UTF80USoGTXMkLJb8F0yNQn
VAFXMfdu7TuwnnBUDmsBYcS8G5ULD27e+SarNBx/8kT2mbtwq1T+AfdR8DbUPWJ/8Iz3bMp9HZyf
O++nJYIhy/Igajm4p+mbzQse30AtWD5uwoQJEyZMePR1BYnzo64rSKRv3759+/btR7dT8Ph/ddm6
ggTmUV/1bym6peiWorD80vJLyy8VfsVebm+5veX2wszcmbkzcwv3C86vHLly5MqRj+/1TP0w9cPU
D6Hr1K5Tu06FnF05u3J2wcw9M/fM3FN43bJnlj2z7BlYF70uel00tLzV8lbLW4Vf7ad9mPZh2oeP
jpO7O3d37m7IL5dfLr/cv9+P5SuWr1i+orAfrca0GtNqDJSbVW5WuVmFCfN/t6SkpKSkpMLE/Zlh
zwx7Zti/3s7U7VO3T90OJwedHHRyEEzaPGnzpM0wvdv0btO7QVJsUmxSbOGM+ORJkydN/k0CEL8p
flP8Jni35bst3235z+OlJKQkpCTAqdqnap+qXZjgtghvEd4iHG61uNXiVgu4fv369evXH93OH33/
vjJ8ZfjKAN84vnF844AmjiaOJg6YUnxK8SnF4fLly5cvX4Y5ledUnlP50XE6ftjxw44f/hf/Th7T
uHpc7+v/Fv9uqUZeXlbWgweF24c9fP6PlmoEAj6fz/dr4vzrzPOv23PnFiwYN65wW3B89eoxY/r1
K9z26VOvXtmysHXrpEmvvgpz5gwe3K0bbNs2efLrr0OdOrGxFsvv2y+I+zC//9daY1X9dR2Oh7eS
ZDKZzb/f2myJiWXKPHp7+vT16z7fo9stiPu4/enE2bjYnGF8AsL7hR6KiAFthD5JcYOQL4QIqUAa
Jr0xsFOvIiwH4X3xE2kSCB/7ZubOAfVKXt28EBAXCPPN+0EdIGToa0Coo3/NbKCyPlqIAN1NSQRA
QgDQ88jAC8Jc5gqNQF+JJMwDPUud4ZFA7Oq55ukD9HH7vBsAE59pySDUEKqSBWID6U2mQ8rqrBrp
D0Dce+Op6+kw3vLCmmEjoOqJig3bXYfqDeo+37YjtM16sUXXAWCYUPGjxHD4cfXutrvWws6O+7PO
bgHjmcBcLQ8qNXOEhzeCeIee4HkXSvtN0blPQoWnY64aO0BIibj+ZQWQ9lsOOHqCb2vWK2nnwD/c
ednVF4xJsiW0HOjPmkyR5yBtU94grSrcr5o709cEMnc4y6odIHVn5mG3COlfZg9xfQkPWmdsy/kG
zCfN1SUnCHf9adpwkLszVR0GUdnWl4UqEP2tdYG5JjguyDa1LFjPmd4wxoM/RnmdhuAdpt7KTYVc
MbDvVCSkvZpT68I5yNoV6H1lJDhr+752x4J0j10GGdztAiGeL4BwaaDhAbh7+4w5lSB/Z+Bg0iJI
H5Bz4vYsyPgg52vPA8hY7zSmvQuG58JuOvpDiODIjtoGjo6mr7FDmCHkqLEiCC8p000TIP9SfoLn
GTCeks4pHuAp0U5HUHuKdtt60D4zt/ANAaGTbWBOEuReCRRP7wZXGz4IvREH6ZGecw8uQ5HRpbuF
zYJiR4u1K9MPBEWItw4Ed7H84oF0sMQ6hoS8CqFrY+7FVIH0T5NC8w7AudhjX58R4PbzuYdzw0Ct
ZxhpOAN003xCd2Ct0FyoA9Jz4alF40DZJIfGCyBkiSOFP/Af+B9VsB5zQeJbMGP08DrN/0xBacbD
tc4F7RS0WxDnX22/IIFZu3bt2rVrf79tcKnBpQaXYOf0ndN3Ti983Lhx48aNGwcNVzZc2XAljF03
dt3Y38zgPnz9n1WkQ5EORToUzuAVzBxmTc2amjW18Lp9Pff13NezcH/Y8mHLhy2HQccHHR90HMJv
ht8Mv/nX9+Phkpqh5qHmoWZ4fcnrS15fAiFvhbwV8tbje33+qNCmoU1Dm8Jnvs98n/mg3YN2D9r9
G+VJBc+7wMxZM2fNnAU7sndk78iGoaahpqEmWG5ebl5uhrjkuOS45MLrjUuMS4xLIPbZ2Gdjn/3n
8bZO2Tpl629qhps3b968eXNo9nazt5u9XXh8W9dtXbf9Fz9i9EffvwM/H/j5wM+F+wUlME2uNbnW
5BosPrX41OJT0KtXr169ev0+TuLExImJE+GF/BfyX8gvjJM3M29m3szC6x7XuHpc7+v/Fg+XavzR
7a5dS5e+8Ubh9mEPn3/48Y8u1fh1HeeCGeeHZ54Lr/vHxzt2fPrpGjXA4bBY/tFMcM+eDRpUq/b7
9gviPqxwxvnX/Ye3BTPO/+r2ueeaNKlU6dHt/lUzzn+6VKP4Z5F9iy0Aw23zcasDtFV6tlYehHhu
6XdBt+o9hK0gJjBNaQSMEuZbvwXfUzmz826C/6RHCj0KRoOhl9QLxG7q1cAyYL0eJm8GVoi9dS8I
n+jzyAf9oH6JX0AYIHRnOaiRenstAaQeWinhOvgG5b/lE0BI9ji990HQ5XKmhSC1NW3Q1oHwjCzK
rUFfrB1Tx4Bhk3e1JxYahz7p61QDwm/a7pROAF+4P9s7COwvRA8vPgocRqFRycYQ5S3hVn6ECE/E
iLAnYF+/fcN3fghrUq8cyqwEMTM8DfRLUPpS2GRbBzDGi3u9UVCkR5ioNof1T2iVyYMTNkPd0oNB
25vV/94GCHyYtzF9P/CW2lvvDZbqIc3CD4G2WN4gfAb+pv6e2jZwp+SNTs+BQKQvJL8j2GuY20iv
QWQfm2reAvbzhkPWcuD5RG+mh0FUvfAlhqkQMSgsMSwX0r7K+M6zDGyvyZ+71oFps5wpHYC0YllC
6i5IeCeyf9wLkL7LNyx6GKR/6Wt4bRDYI60NHWNBnyi9a1YhfZ1bu7MBhCV5sfIpCDlp+Ta2KEg/
Wn9wbwJbRUe70PkgvqB8H/EpGH8R7xmTQJtOCdePcKfh/UkZ5cD3ijfduRaKNotZYi8Ft/enVdVf
BHeCsiZ9IBTJCW8j94PAXGWB+Qi4W3uaBsIhO8U9UJsFkWXt3xS5AK5XAoMpDbZo00LjGCjZJWZH
+VNQ5G7Rj0sdgbDXw0fGLwV/28BUqTG4a/sr+kIh9ER454hYcFyNrhTRBbKfSt/mXAa3z56JvbgR
7jmyR6QOAm2GMTJ0GDBffVl4E7QebPSdB7GiqVmYCYTp2rFABGhP+ypmHwIpJaC7YoBSj2egPlxa
sXHjxo0bNxbOCP/R9ZgLapsfVtBOQbuPivvPFCQwJcaUGFNizH9xoQcPv1mOSDghnBBOAC1pSUsQ
Tgonhd98Na4N0AZoA37fzMPH1aPqUfXoP++nOFgcLA7+zf4icZG46PfX6QP0AfoAwIoV62/6WeAE
JzgBdKMb3f746/Sv9iNQLVAtUK1wXxosDZYGg2AX7IIdpDHSGGnMP4/3uIWsClkVsgrEMeIY8R/E
/6PvzweJHyR+kAgdF3Rc0HEBHH3u6HNHn4Mj/Y70O9IPNiduTtycCMunL5++fDqsYQ1r/p0O16Qm
NWHzzM0zN/8m4Sz4g/FhBSUbr9V8reZr/6Bk44++fwUlFL+77v+UvvwzUh2pjlTnn8d52L87rv7Z
+xr0fyss1fjHiezjjPPb9h9VqhEIeL2/vTnwUR51fsWKI0euXoXly48du3UL3n+/TZtq1aBbt1q1
ypSBOnXKly9R4tfHnzjx+7i/j/N/zzg/7FGlGhMndu1avPij+3/vXl5efj643f+43f/YGWfzcVcD
uTkYqtFTKgqgz+MucFOoLFwH0Se/Kt8FFWGqvh4YLhzRj4H6nneWdBl8LaVasXNAHCItQgHKaudZ
CPow4V1uARf1VXok6Ol4iAD24eQi6D30unwBhoHSYflbMLQwzjJWBemIIzGmHiRt9E0yFoUrSzLH
6PMhZ6avmDAUpB/EdrQHZbOyx78bQorEFy/3PYTao0sU7QLe7xWvOwWET8WODAblTTXTuwwC9QNL
vSNBO+0doc6HhL5xFWschY7r6khPV4KGn1apGJEHYUNL1jXUA2WdcZDvIyhpid4dEQPlo8rVDzkF
1XVraE5NeGK0UdJaQ5gSHVJ8OUiENSvWBtQmvls59cAVn3MseRJwRavJNAg9Ffpz5BiIHZfoK5EL
ifeLvl5yKIT6bJUjSoNw0zBLrgChB6MXRgTAYbJMM30NqfvTOuZch3M7L5dL+xByt3pD/CvA1tfe
OiIb7F/YJFsHqNa7xPbiS6Bsr4i4YlFgsNPe9yUUy486UvInqDAkLLvB21D0ir1x0a/Bdt1isTSA
MgklL1ZpDRG2sD6RJyFiUqgpbjLI0yQpojx4eqgnPAooI3V77j4wieaZ5hcgfL39ecIg4aO4zSEH
QBVxWatD1IionxzfwJPnypVNOA+h4baPQgeANFWIlFuDLdSSZOkNVretj9EKYktTB/NRiL0bFl/i
Cyjbo3hGORkqHKpYv1YLsCeFfJf4M+S+4Jqq50POUK9JSQFr3cicyFpgmhj5WWQe5Or3++dWhTvn
T7x46hSkHsrqd/MoqBHmapZU0F+Woo0XQVP0NXpbEEoKn1MESFF3ehuAYvNtcKaAUll9xnUTFCtN
lb2Pb6AWJLDFixcv/tsPkoL/8B/+ae0/quBxDycOBXH+qlroZqubrW62unD/wy0fbvlwCxyocKDC
gQowadKkSb+txWvRvEXzFs0L9wtqcFM3p25O3Qxrmq1ptqYZ3B9/f/z98Y+vn/WH1h9af2jh/uyX
Zr80+yVYKCwUFgqQ3S27W/a/kTD/q+qcqnOqzqnC/U8PfXro00Mw79i8Y/OO/ff144/6V9+fEbYR
thG2whrnGsdqHKtxDIbUGVJnSB2wjrCOsI74/QyrsEhYJCwqrBUuKDF4lGuh10KvhcLNt2++ffPt
wvYf/makYEY4eXzy+OTxcP7r81+f//rffz3qL6u/rP5vbsL8+MDHBz4+ALt77O6xuwe8Mu+Vea/M
g1VXV11d9Sdunv2z4yro31NYOvGvzTg3bz548DffFG4f9vD537fzjxP1QODXZeEeXvXiYY86vnfv
tWupqYXnlyw5dOjatUc/vmBbEPf31xXcHPiPSypk+dfSjIe3+/ffvJmcDBcvulwez++3+fm/rtf8
6FKN/9CbA22/RI6PWwx6Z6mu4QqIKxjPe6Ak+/cG+oDvCc8ad1UwvRyK/VMwFhPG6ufg/NwbuZn9
ILRxiZ4l2oFxLLO04eD9QOggLgThJ37SfaC/zUktCcRZQk/pKAhV2SysBf08tSkLzledeTk3YO2s
dec3WcD3uWqO2AnVdzzVvuEO0IsY7rMHpF5ymnwexGhth1IStAHiKUMf4CVqC59D4Cn/Lf08iH6p
HTuBjXoPMkFYxZviVGCeWEJ9CSiivSZbIdCLNPFNEFcnvl2tJFQ5Kr5v3wglXzctPDsHskqHp+aM
BvFS3nGPDcSPE995wgOVx1XeH7gEiWvT0pzT4UyJLJ+yAc7NE6/a34Z7FczNS9wD7Xbe7rQx4Oua
2SJ1IGhF7V+Gbgf7uyFfhihg+snSwpQI4sf2r+znQAsoXf0tIG1nTrQwAFzFPBfVXHDN0p837AYx
Ri6l3gKGaV/qUXDv1bSzGV5gi/qqIRTCWoUWt5wD5XnpnO8glN4R0q/4cyAnGOZHFIW8cy6PZwno
s4TtvnfAvE0bHLYbaKc1YxCYpsidxK/AeIW2EWlg6G/rn3MZPN95pKzLkGnM7cYCUMf7JyddhLKl
Y2IrBCB0onQg/mWwbQibhQ+Uyq4zTglSRiWprrGQ1seZ6rKA+SWzajoLYgtht3oMHGnmqbZeEFo+
okHIfLCPdxjCVoH5A/tsSyXw5ftKCXvB+b5ziF8A6R3T26ZwiFRjl8QsBXM3827DGMiffLdP6ieQ
vu72gOsmyGueq90pAx6MhvBPQR3GOOProE/T5qq//vsbol4C/Z5+RK8M2ihi9SpAhJClbgDRTrTx
LeAZ2ujV/88g6fT4BmxB7XHB+sy5ubm5ubmF+wXbR80s/7NVNx6O81d5yfOS5yUP+HW/7tdhw6gN
ozaMglEZozJGZUD0neg70XdgcLHBxQYXg16BXoFev/lAHmkbaRtpg9nm2ebZZvh29Lejvx0N0Xej
70bfhTTSSHsM/exbtW/VvlUh5bmU51Keg22Tt03eNhmK7S22t9heiJwaOTVyKmRuz9ye+Rf+0M1A
faA+UIcHox+MfjAaNiVvSt6UDJUjKkdUjigsUShIVP9u/+r7U5DAzlw1c9XMVTDKNso2ygbqEfWI
eqTwZsxRxUcVH/WbPxw7p3dO75wOP7zwwws/vFB40+CjbmIruKmSi1zkIrR9v+37bd//falIwc12
n/M5nwPbpmybsm0KVP6m8jeVv+Ff1r9///79+4NztnO2czZs3bt179a9sPnO5jub70Adfx1/HX/h
zY//rj87roL+Par6609IPyqR/ffb/a/bK4j7sEDA7/f7QZJ+XTXjUQpW1XjYpUv37//2h1Ue3n/U
4wvi/r4/v878Pqpwwmaz2y0W8PkU5bdX7Nx5+HBSEmhaIJCa+vvHPfFEiRJmM1Sv/uST/2iCpyDu
4yYcPnz48OHDul63bt26dev+6w24cTXKrgVcNZy29wAhiw+0qqA18C/wHwFfjPsFjw9sxvB5EYtB
vaq/6esHF6dtjzzZC0pF1h1b4yZYXwk/aRgC6kU1Uy8BHFed+g5gh75KfQWE3oYnDeXhZon7SRdW
QPGtMbXL1AOln9JRj4N9Gfudx2qA8xeXRY0E2jq+K9oTSmWW9hX5GSo8iN9gSAJrd2tRDoJaQW0t
PgCpszCB06BUULd694HoF3rKx0F4VaoszgH9La2TdABYJ36sBUBviiAkgHhQF5V3wF/TWTGvMxiT
De3VRaA+55qa8QZoX2S8lPktSK7ImWHdwHsvc3OKA/Sp6dPT3wBpj6yzCryp0j1PGmSVuLk7Jx3W
3thXMqU1nBye/aOUDv6l3glZn4E/0906eyoI1eXRlqsQNiKkbsQWcLwVusm8GUwOw6v6A2Cw2tMv
g7eSa6P3G/Bl+3cGPgVluX5ZGw7+WP91bzr4BrssOYfA7LRssL4GEdmRb4S9Cd577nHeHuAp5s5y
/gSZ1bJyUpuBOlPY7LwLWifhJUtRcHbz78xOh5A8xyqxKvjT3DuEDyC3oTvX1RvKp8VPKPopyJfE
KEsVuB2ecfv+cTDUk3da+kDUujA1thNE7jNfNJUBbZ8+RukO94fcG+7dAZrXOIQN4JgUKlkFML8s
r7Tehpjc+E02BSJaRRaPygTDEPONkAugva/sNYwAV6qzgpIP3kx1U2AkWJSwC2EnIHR5+NywByBW
0n4y7AJnVEpOSjfwrcwedC8VPD7l89ypkO13vRU4BHk79DFhPUAvI843n4DAJGZJTcGXorzHqxDo
E+gZaAeBQ8pq31lQZgW6ei8Ai9QHnukgVdaX+nrDidQDn2w68/gHbkFiW7B6QEEC/e8KDQ0NDQ2F
4cOHDx8+/K9PnIP+NQXfDCS3S26X3A7ax7ePbx9fWNv84r4X9724r3B/c4fNHTZ3+Lt7HRT0v0OV
Ks8+O2MGVK1aq1aFCv9+OytXfvBBu3aF+z17vv/+f7WqxNmzx49fugTnzm3ePHp04fHo6G7dpk0D
k6lYsfj4wuNJSR999PLLhftFiowatWzZo48/7J9d5/PdvfvgAaSnf/fdO+8UHn/ttePHb92CypUT
EqzW37eblpaSYjDAqVMPHvwrf3j4/fn5WVnQrl3DhqGhvz9//nxystsNc+fWqlWy5B9v91GOHDly
5MiRxzDjrKmeH7wDwfCNsYXlGGjttY/0LiCXM35jqAHyUpNiTgQ1RB+pfQcs9Wz0TwLH546Dtj1g
XGD5wtAXxK1SPdEE4hPCZeEZ0DrwvPo9SNFyhuF1SM3L/iw5H26+cXPhkW1QvH1c97jmkLnAXcc9
BJxO0yTTi1BsddlFlYqCv4j7TdxwZ1bKS67XIMEd3t9+G6zH7OUM2aDX1l5jGHBSb6VfBHGysEj0
g7BU7CovAL2ovkCbBtpAvvdmAZXUDepIkJaIpyyjQT8mDjE+APkzx4bIKND8asdAKOidDTPU1aAs
slRztgK5g+Ve7HtgDotsaP4M6B2TWKY/MNXRPmYqWB5IZjkaIpbUmOM9Bm+crfnuhW/hl+X7Lp36
ETbMPVhW/QoevGo6G1oClCN5XdMPQPahzCop74E3z73ZsgTCd4TdjmgIYWdDy9ltYGkdeceSD3p9
fak6CPRNite/FvxVfRNMO8E13NLAcBZMF+VYaQhkXs7+0vsdeJ9R9gbeAfmicWLgBOQs9fbLHgrW
9uZ9lslgj7RssD0A01FLR18bkNcZJmjbwHUvL8Q9G8KKRcwOKwH5dfxG3zHIWZXfJacvCEelUeIW
MC4wTDK8BFfH3W58Iwdsr1qPGDpC6LawJkY/RI0pdrnIRoicERIZ3gLC74b5HF3BNMvkDNXBUN62
0z4BAobAKmk4uCbm/uh7EvI3+C4HngXJbM0xjIfwEzHXYyWw7LIecZhAeTnvsvcAZGTfu3tnGGSs
u1/10kYIxOvN8uaD9rH+tvAe5JdwV9NWgrOnKufVhEC2VkRbBv7q6rf6KFB26J31J0A9qPRXt4K/
RmBEIBL0idp2dTrop9X+gfqgBgLNfe/9+YH6KAWJbUGiW5BAFyRYd+7cuXPnzqMfX1CKUXCTYEE7
wV8U/M9UsOzcnpV7Vu5ZCQMYwACAmcxkZuFybSMyR2SOyPy7exsU9L+Lpv06M5yfn5WVnw8mk9X6
j9Y5/lf5/f+4Ztjnc7t9vsK4DwsEfv3lPF3Py3M6QRT/8U1+/2oJx6Ou0zSPx+sFRfnHvwzo8/3a
z+xst1tRIDTUYpF/k32WLh0V5fH8uj50SAhcupSZKQjwX8+Xw9NPlywZH//rTLbbXXg8N9fjUZTC
uI/bn06clamufP1HMDQIWynGgbrMv1mtBb45+heB5WBsbGpODMjt5MaGRPAcCXzlawniRWGpNhcM
y83dDG9DyriUu7c3gLJT+cX/HZiQvtJ7g+O4bVj4Ych/KueFPB/YXzHfiBgHpjLmjfbBEBVu32qO
AOdaZ5FzGlxbldwx90tIrBg5KyoNbLssL6oNIfmbtP3+slCsSXgR0xlQWwg+ioAyVikVOArCFLGD
2AQoyiIhDISdpMirQbeJ7uwJINShplgNiFSc6jOg3He6cp4CQzN7iyLtQK0iPFCvgOx03IyrCYbz
9rC4KqA9oxxzZoPa3ns4vyIYG5gbRP8E6i7DWtszoH6uvaRLoFnll8xHwVajwomG78Kz5Sr0e7of
lJ9ctvqmr2Fhj++/OloPrm63yqVPg7eSq2XGGvAMzr+RGwv+XWmb7w8F1xd5W80TIfRLR35UNIQk
hawyHQbbVevL5m8h9J2QDx0KRF2Mqq2mgf+8Z53rGTAotsS88hDYq/QXy4CS6NX0LSB/Uiq/WBfI
65f7plcDU3PDG+bqIN1X14WkgtvgruVfCPaDloFCaYj/IaJS9FmwY3gmYSqkzTS2TX4ZQvbYD9km
Q9SBkDXRe8HZtehbnn5gmGO8wV5wJIdbbQPAcsPsDPsKjI1ls/01CPi1ndJT4C8aMBEDOTnpC7zP
QeBrNYftoP1i7G7uBJavQkdb3gF7tfD1Ec+CVMx3GBfkNr59Mn0TuDpmpST1BeW8sij9I7B1t3+p
fQG+bco1y0LwlvPv878AdtFSQjsC0sbAfHdR8H2gVNTLgN5Qrkg+KHe1/moo6E+Z4vgAlP66SX8a
tBPaFk0E4YpgMPpBEZVV8p/4yvWPKkh0CxLph5eRK1jHtUBBLXP16tWrV6/+1/cv6PGo9kq1V6q9
AstYxjKAoQxl6J9tNSgo6HF44onSpSMi4N695OSMDIiLS0iIinp8CXSBgoQ5JeXXOAVxH1apUvHi
ERFw9uydO5mZIIqhoSEhEBY2ZMgXX/z++kcd/2fX6brH4/GApuXm5uVB1arFi0dG/v5xoaFGoyz/
+tPcfj8kJPxaQBEWZrFIEmRliaIkQfHioaF5eVCvXmKizQaSJAjif3En3p07v8bNz9d1WYacHI9H
VSE5OTfX7y+M+7j96VKNB40uv3NrG0RufGJasVEQSPd0VUuCkqnGBsaAqa+xjeEk6LLi8tkgd/Te
HkdCIG+O/pVcDYpcbVqtfnvI9uR4HjQE3wpluDIWTNnGlWJ1OP/G1YRfkiH3ivpq/ktQtnT0itI9
IEGNXFcpF852veQ8mQcX3rvvv3QFLp+7f1aqC1VHVPqwzXNQd1LlzGJj4YkTUZuENiCUMnQRi4G4
Wd+mrwJ9mtZSvQt6qtheSAPxBaG4oRkIqeI+/VlINWXfvDII0rt759wqBxHDIzqG9AHtE6crexqE
W0zOSu9D6FxHn/INwNdRq+i+BLwvyKIMwh6S5T4gLtAiAsNBmaX/pLUHURerGd4AEvVoLRWEr/T5
+llQ0/VGQgJQiQNSFNgWWKrKTWBN6Kx+H9+HDR2OG2/1Az3BNjPqMrinepsFGoC60V0y9xfQL3tm
590AUdbO+JeB9V05T5oF5j327vZ8cFgcFutnEDLK+qL5LJhnmk0GGQyj5DFqU9B+IVkzgL+M+pHi
Bf20VlrpCdp87WzgBQiYlKdVDTzVva/7x4KwWk4SngVpnhAn1gJphrBQuALaQq21IIDJbXrPuA+0
zUIr7WcwVRXrG18EQ775R+uToIWzTrgA2pRAYzEVvFW8LbUK4NzvLeYPQGBMYHsgA9QG0mLhTZBi
jMdsJ8E40RJuzIfosiH1LEARX+wQ2xW4F0h5I+MnyFdyKqYvgOw6qQmXu0FufprHPxPUE2wJ/AJy
nNJeKwGiSVxtagSsNZrlCJA/EDdIRUF/m7elt8E/SS3HO6B/TL4+HhBoIpwGPUH4WVwFvC9uk74A
XdbO6LVBe1O4Je4GPUO8IM+AH174afR3Ox7/wA0KCgoK+s+QlZWT43RC375vv/3113Dx4rVraY/j
JotHqFixbNmYGFiyZPr0l16CiIiwsN/+Mml6em6u0wnPPTd27KJFcPr0tWv/aJ3ox6V69bJl4+Ph
xx8nTx4wAKKjQ0N/25/s7F/njt9//9y5pCRIS/t15vmvEhNjtcoyfPBBlSpFikB4+ONJoB9bqYY8
wfGtcT0EZubUy3eD/nL2Nzl7QJjoSnZZQR9bbn7pNqCWcfdzrwBn8a0XfnkLwszPv9UxH4QDlgTh
JCRMNr5cdBBkD3FXzbPDqYyT2qFZYClnNIa+CJ4DtnX6HYjaZS0V3xgMbxvLh9eDXWl7wu/1hQej
hO/vdwN3hLQhcAu2n9hz8btL4Ovqp8fXUDqx2cbiDcDiMl2kN6gHtddFDwhnxPvCXBBHC/ukLqDl
8oE/AeSFNDCfA3edPF/WQLi69lrvk6VBOarPNHwB+iLTSM0H0WciIpMuQ6WdRT73lYDoJGuzxD2A
RXzN4AF9pYjWGJgibBVDQIA2xrYgfKDXUCuCvoFebAJ2CsuEySCGC3cpBtpsuioBCGhKEe0wCJX8
ufk6iJsymt8E5AnaPPU9kPuZe9g3gfZcWMnIK6D8HFIt4jqoffyC8zvwD/Rtze8MSnRgnFYLApuy
ZmRdhhxnVn25E5gaGj8Q3wazxbTL0glMlQ0jTWVADDfNlzaBdEuS5cMg1TOUt+4G4z65udgJDOaQ
/QQAmaZaMgheJolLQQjRJX0TaC30O5QDZZieqvUDtbwSyWLIb6WU5WXwrc/p540Fb9/ANEWEgBgo
qVwC9Tj7OQ/yOlOSeT4Yl1lX2aaDsbO5kfUwxI2xrzAug5rdys+OWgc1v631UpVZEPdpiaulp8HW
d7bP+boUpL6RN+V2GajRqJavQ3tYu2Xdg5+Ggr7V84qhFLT4tmrthulwLe5854xycOKbE+UvVoR7
i7MissaB71nlNaU7WMablpv7gHzC8IphAGiV1CL6O6DW1r5UToH+tTBI/AbEVnpPMRS0q/p9zQDa
Sf2AOgZ44a/7cAgKCgoK+vsVJK4bN37xxauv/t29KUxcjxz5/PMRI/7u3hQmrp999o9v4vt/zZ9O
nC1fKFP9bSGw4nbeg41ApK+1pypo9b1F/M+Dca/QvtQ6INQ1x/UTsM1/M7AUTB/HRIZUB8MKZsib
IfNN9/oMAU5uPDnywBxImG3cEfcmuJLMrVzhEJYmjHIkQuyWuJLF+8CZMze+TBNBPBvyWuJC0Bdn
rksOhaJFKoys2gGSa97sd20eXFp43XsjA45tK9EpIgGadq80294HAmsCy31TQN5hirA8A+pRbaM3
GYQzwlxTUaC/XlYIB8P7lsmmPRBTsqJWFkg6esZzbTiU3itFxK0G+xVXpKUD3EjdundNHNjnlUmr
3h6EDUIXqQTod9kodwLDqKI7y/YA+e3o7JJPg75Tb8x8YJXQm2zQF+kX0UFIYgzHQaylRwulwdBY
T1DfB+FrbYnaA1xfOZ/MTAH5FWWvpwyIXc17HZtAjrEcjIgGY57lUuQVEGta5tp+ANNPoe5wAbRp
zoFZseBFidXmQeA9/YGWA9oRvbimg7OVZ73nJIgvufz5V0GR1D36ZaCV7uYcCGuEc+IUMC7iCeEi
6LvFfvQD/RVhseACoTFLhATQv+BHcS3oU4RFhIA2UH9GOQB6mPCuWBb0V4Wi8n0Q1ks75dYgnTac
MBwG+XRIo7A7YJlhmWH7CcwO4zrzYYjLtLq13VCzRfE6FjtUb1unarX6ELe3nFxTAmWxcMEcDYHT
+mx2Q+N3Grq7TwBnEWegyTsQ0Sfh1TKfQ7Sl56Jy+8C+yFG2rAyhV8L6Fn8XKmbWmnF/AJTYXqPH
hWHwnXvFnU13wf9ufs4FDyR1Sf06uxKovcUZkhOMDrNmPQ6GRGmp4QuQzdIisT7wAk6xG+hr1Hjt
HGiDlZP6pwCUp8nfPcyDgoKCgoKCHoc/nThLm+Rj0lnQ3Y6Gth9A2BKTFjsGhM5cEjKByrJfbg6+
Fffibt4CuXvUK+HjQH4vJiL2G/CEBFLya0De2LykB0OgxvYq9eotguiB4TPjbXAo/WKzTWMhPNrW
M2YK6B3lm4YRcGHwyRq79oBxtrVD8SVQfLbtywrRUHtHuetP2eBSo8jepQDhWfVL7WmollHOEymA
b6zrmfR3QXjT0yyrDWhrZNVWHMQV1oE2H+hNDHnG70G6Yt4sRkPy4FPy9cqQfD733UsdwbYw/gNT
FkSkRjUrMRsqvFfF12YoeMyVqt/3g56UVftBEfAtfNDt1vegl3C9m1MNVCm8gmM9GJ6JiI/OA54Q
hodWB84zQJkP+rNcYCxwhiRWg9ZG+IEPwPexv7PeEnz5/k04QRsk3zd0A+/dwGL3csDgPereCUJe
7prMn8GUb8pOsYG1jX1cmB+KbSuWGJUMnaL7N2xZFVLSH9zNfhHurroRfz8f7g7MeM3VGzI/dZcM
TIf80/5FQl1w5+gXlNMgtFMj9dEQCFXR4sF9Sk3XegJPCBP0jaBHC/uYD6znAzJBjBGHiU+BGGV4
3/A9CJukSMNKkDcY2hkbgTRLzpAngzzK4DG+B4YS4pvyCmAi3XgGDNGqNZAO2oyMxik1oGnxZzuX
bgVPP9OeTqXA+67YLuo2+L4IjPdGg35UXOBrCWKsdFXsBtLz5jDbYogaI1e05IM+jmrmJZBYrOj+
5hMgYFKmK9vBn+m/6j8Jxvdse82tIXBRfS2sAzz9So2OVX0QPzcso9grkHTYvUN/EXZe2PbJfhck
z8184/4e8JgN5+WNYBGUr0wnwbTaVMu4CcQj4gHxOMgRhiflX5fPCc45BwUFBQUF/Q/xp2ucg4KC
goKCgoKCgv4nK6hx/tO/HBgUFBQUFBQUFBT0v0EwcQ4KCgoKCgoKCgr6A4KJc1BQUFBQUFBQUNAf
EEycg4KCgoKCgoKCgv6AYOIcFBQUFBQUFBQU9Af8/8vRFdwtGBQUFBQUFBQUFBT0e/8f1v78XDDA
j4oAAAAASUVORK5CYII=

--_004_4E1F6AAD24975D4BA5B16804296739436784A7BATK5EX14MBXC283r_--

From cabo@tzi.org  Thu Jun 13 08:30:31 2013
Return-Path: <cabo@tzi.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDD8621F8F38 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xP88Ffi0cQGx for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 08:30:23 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 09CEB21F8EDF for <jose@ietf.org>; Thu, 13 Jun 2013 08:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5DFU9hP009944; Thu, 13 Jun 2013 17:30:09 +0200 (CEST)
Received: from eduroam-pool7-0357.wlan.uni-bremen.de (eduroam-pool7-0357.wlan.uni-bremen.de [134.102.113.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id A82F934E1; Thu, 13 Jun 2013 17:30:09 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436784A7BA@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 13 Jun 2013 17:30:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <886D4B08-2AF4-4053-8851-8D6426DFC61D@tzi.org>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <51B9DA50.1080807@aol.com> <51B9DD51.5040000@mitre.org> <CAL02cgT=m=wvqADRmSku+UphFJayNawWWcYYXZRPisA+YL8iUg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436784A7BA@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1508)
Cc: Richard Barnes <rlb@ipv.sx>, jose-chairs@tools.ietf.org, jose@ietf.org, Justin Richer <jricher@mitre.org>, George Fletcher <gffletch@aol.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 15:30:31 -0000

On Jun 13, 2013, at 17:05, Mike Jones <Michael.Jones@microsoft.com> =
wrote:

> But what I hear people saying now is that the specs are at a =
sufficient level of maturity that we should no longer be making breaking =
changes without a compelling reason to do so and that the industry would =
be well served by completing the RFCs in a timely fashion.  I agree with =
that position.

Very high level meta-comment:

We don't have any tools in the IETF to find out when these real-world =
phase changes occur.

The IETF standards process does not recognize them.

That tends to cause confusion because some people think protocol =
development is clocked by the real world and some insist that the IETF =
process has not yet completed, so theoretically, we are still wide open =
to changes.

We seem to have no idea how to handle that lack of synchronization.

Gr=FC=DFe, Carsten

PS.: I feel a bit guilty here, but I hope I'm not.
I have been trying to pick the brains of some people how the JOSE work =
might been applicable to future CoRE work without carrying the baggage =
of the JSON format.
In all cases, I have been very explicit that, by starting those thought =
processes, we should be careful about not creating delays to the current =
round of standardization.
But the idea is infectious enough that it escaped without the caveat =
attached.  Sorry about that.


From phil.hunt@oracle.com  Thu Jun 13 09:06:20 2013
Return-Path: <phil.hunt@oracle.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E672721F9A10 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 09:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.611
X-Spam-Level: 
X-Spam-Status: No, score=-5.611 tagged_above=-999 required=5 tests=[AWL=-0.409, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vACi5qNNo6nn for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 09:06:13 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 740E221F8617 for <jose@ietf.org>; Thu, 13 Jun 2013 09:06:13 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r5DG67f0001157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jun 2013 16:06:08 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5DG66aH008657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jun 2013 16:06:07 GMT
Received: from abhmt119.oracle.com (abhmt119.oracle.com [141.146.116.71]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5DG661d025442; Thu, 13 Jun 2013 16:06:06 GMT
Received: from [192.168.1.125] (/24.86.29.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 13 Jun 2013 09:06:05 -0700
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-30371A70-891E-4035-977F-563CF030E073
Content-Transfer-Encoding: 7bit
Message-Id: <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com>
X-Mailer: iPhone Mail (10B329)
From: Phil Hunt <phil.hunt@oracle.com>
Date: Thu, 13 Jun 2013 09:06:04 -0700
To: Richard Barnes <rlb@ipv.sx>
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "<jose@ietf.org>" <jose@ietf.org>, George Fletcher <gffletch@aol.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 16:06:20 -0000

--Apple-Mail-30371A70-891E-4035-977F-563CF030E073
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Seems like many these days are in a rush. They call for consensus before dis=
cussing the issue.=20

Isn't it up to the chair?

This isn't unique to this WG.=20

Too many times the explanation for keeping an apparent 'feature/flaw' is 'be=
cause we don't want change'. Yet often the group can't explain it. Or worse,=
 the group just says "we know the emperor has no clothes, we just don't feel=
 the need to comment." This is where alarm bells go off for me.=20

Phil

On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx> wrote:

> This would have been a nice discussion to have had 18 months ago, when we w=
ere getting started.
>=20
> I don't think it's compatible with the IETF ethos to say "Changes to this d=
ocument MUST NOT break existing code."  Otherwise, we're not doing engineeri=
ng here, we're cleaning up documentation and rubber-stamping.
>=20
> What would be acceptable is to say "Changes must break cleanly with existi=
ng code".  That is, it should be possible for a JWT implementation to, say, p=
rocess both "legacy" JWS syntax and whatever comes out of this group.  That w=
ay, we could come to consensus on the best solution, incorporating lessons l=
earned from earlier work without being hindered by them.
>=20
> Would participants here consider it a acceptable for the output of this wo=
rking group to be incompatible with existing JWT implementations, as long as=
 it had the property that JW* objects in the new format could be clearly dis=
tinguished from "legacy" JW* objects, so that implementations could adapt th=
eir processing?
>=20
> --Richard
>=20
>=20
>=20
>=20
> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com> wrote=
:
>> +1
>>=20
>> Breaking deployed code as raised by Brian, Naveen and others is a critica=
l consideration.
>>=20
>> Thanks,
>> George
>>=20
>> On 6/13/13 10:19 AM, Mike Jones wrote:
>>> Jim and Karen, could you please do as Richard suggests and close this is=
sue as =E2=80=9Cwon=E2=80=99t fix=E2=80=9D.
>>>=20
>>> =20
>>>=20
>>>                                                             Thank you,
>>>=20
>>>                                                             -- Mike
>>>=20
>>> =20
>>>=20
>>> From: Richard Barnes [mailto:rlb@ipv.sx]=20
>>> Sent: Wednesday, June 12, 2013 1:57 PM
>>> To: jose-chairs@tools.ietf.org; Mike Jones
>>> Subject: Fwd: [jose] #23: Make crypto independent of binary encoding (ba=
se64)
>>>=20
>>> =20
>>>=20
>>> In other words: Chairs, feel free to             close/wontfix :)
>>>=20
>>> =20
>>>=20
>>> ---------- Forwarded message ----------
>>> From: Richard Barnes <rlb@ipv.sx>
>>> Date: Wed, Jun 12, 2013 at 4:55 PM
>>> Subject: Re: [jose] #23: Make crypto independent of binary encoding (bas=
e64)
>>> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
>>> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<draft-ietf-jos=
e-json-web-encryption@tools.ietf.org>" <draft-ietf-jose-json-web-encryption@=
tools.ietf.org>, "<michael.jones@microsoft.com>" <michael.jones@microsoft.co=
m>, "<jose@ietf.org>" <jose@ietf.org>
>>>=20
>>>=20
>>> To be clear, I structured my message in two parts for a reason, to separ=
ate the analysis from the opinion.  I acknowledge that I am but one voice he=
re, and I'm increasingly hearing how alone I am :)
>>>=20
>>> =20
>>>=20
>>> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:
>>>=20
>>> <impartial-analysis>
>>>=20
>>> So just to be clear on the trade-off the WG has to make:
>>>=20
>>> =20
>>>=20
>>> On the one hand: Breaking every existing JWT implementation in the world=

>>>=20
>>> On the other hand: Eternally binding ourselves to base64 encoding, even i=
f binary-safe encodings become available (CBOR, MsgPack, etc.)
>>>=20
>>> </impartial-analysis >
>>>=20
>>> =20
>>>=20
>>> <personal-opinion>
>>>=20
>>> I have some sympathy with JWT implementors.  It sucks to have to refacto=
r code.  But I think we're literally talking about something like a 5-line p=
atch.  And early JWT implementors knew or should have known (to use a DC phr=
ase) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part in=
 the discussions are likely to find the specification changing out from unde=
r them in incompatible ways."
>>>=20
>>> =20
>>>=20
>>> As PHB pointed out in the other thread, it would be nice to use JWS and J=
WE in place of CMS one day, without the base64 hit.  We should incur the imp=
lementation pain now, and get the design right for the long run.  Base64 is a=
 hack around JSON; we should build the system so that when we no longer need=
 that hack, it can go away.
>>>=20
>>> </personal-opinion>
>>>=20
>>> =20
>>>=20
>>> --Richard
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco=
.com> wrote:
>>>=20
>>> I did at first find it curious why the cryptographic operations were ove=
r the base64url-enccoded values, but I was also very focused on JWE, where I=
 think the field separation problem is less of an issue (at least now).  For=
 JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.
>>>=20
>>> I will note that unescaped NULL is not valid in JSON, so it could be use=
d as a separator between the encoded header and the payload.  I do find it i=
nteresting if JOSE could more easily and efficiently support other encodings=
.  However, I think that                                   while this is an i=
nteresting thought experiment, it seems we're too far down the path to serio=
usly consider it unless the current state were shown to be horribly broken.
>>>=20
>>>=20
>>> - m&m
>>>=20
>>> Matt Miller < mamille2@cisco.com >
>>> Cisco Systems, Inc.
>>>=20
>>>=20
>>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ie=
tf.org> wrote:
>>>=20
>>> > #23: Make crypto independent                                       of b=
inary encoding (base64)
>>> >
>>> >
>>> > Comment (by michael.jones@microsoft.com):
>>> >
>>> > For both serializations, you already need the base64url encoded versio=
ns
>>> > of the JWS Header and the JWS Payload to preserve them in transmission=
, so
>>> > computing them isn't an extra burden.  In the JWS Compact Serializatio=
n,
>>> > you already need the concatenation of the Encoded JWS Header, a period=

>>> > character, and the Encoded JWS Payload, so computing that             =
                          concatenation
>>> > isn't an extra burden.  Given you already have that quantity, computin=
g
>>> > the signature over it is the easiest thing for developers to do, and i=
t's
>>> > been shown to work well in practice.  There's no compelling reason to m=
ake
>>> > this change.
>>> >
>>> > Even for the JSON Serialization, the only "extra" step that's required=
 to
>>> > compute the signature is the concatenation with the period character -=
 to
>>> > prevent shifting of data from one field to the other, as described by J=
im
>>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at a=
ll -
>>> > it's necessary.  It's also highly advantageous to use exactly the same=

>>> > computation for both serializations, which is currently the case.
>>> >
>>> > Since there is no compelling reason to make this change, and          =
                             since making
>>> > it could enable the "shifting" problem identified by Jim, it should no=
t be
>>> > made.
>>> >
>>> > --
>>> > -------------------------+--------------------------------------------=
-----
>>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>>> >     Type:  defect       |  encryption@tools.ietf.org
>>> > Priority:  major        |      Status:  new
>>> > Component:  json-web-    |   Milestone:
>>> >  encryption             |     Version:
>>> > Severity:  -            |  Resolution:
>>> > Keywords:               |
>>> > -------------------------+--------------------------------------------=
-----
>>> >
>>> > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment=
:2>
>>> > jose <http://tools.ietf.org/jose/>
>>> >
>>>=20
>>> > _______________________________________________
>>> > jose mailing list
>>> > jose@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/jose
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>> =20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>=20
>> --=20
>> <XeC>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

--Apple-Mail-30371A70-891E-4035-977F-563CF030E073
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Seems like many these days are in a ru=
sh. They call for consensus before discussing the issue.&nbsp;</div><div><br=
></div><div>Isn't it up to the chair?</div><div><br></div><div>This isn't un=
ique to this WG.&nbsp;</div><div><br></div><div>Too many times the explanati=
on for keeping an apparent 'feature/flaw' is 'because we don't want change'.=
 Yet often the group can't explain it. Or worse, the group just says "we kno=
w the emperor has no clothes, we just don't feel the need to comment." This i=
s where alarm bells go off for me.&nbsp;<br><br>Phil</div><div><br>On 2013-0=
6-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</=
a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr">T=
his would have been a nice discussion to have had 18 months ago, when we wer=
e getting started.<div><br></div><div>I don't think it's compatible with the=
 IETF ethos to say "Changes to this document MUST NOT break existing code." &=
nbsp;Otherwise, we're not doing engineering here, we're cleaning up document=
ation and rubber-stamping.</div>
<div><br></div><div>What would be acceptable is to say "Changes must break c=
leanly with existing code". &nbsp;That is, it should be possible for a JWT i=
mplementation to, say, process both "legacy" JWS syntax and whatever comes o=
ut of this group. &nbsp;That way, we could come to consensus on the best sol=
ution, incorporating lessons learned from earlier work without being hindere=
d by them.</div>
<div><br></div><div>Would participants here consider it a acceptable for the=
 output of this working group to be incompatible with existing JWT implement=
ations, as long as it had the property that JW* objects in the new format co=
uld be clearly distinguished from "legacy" JW* objects, so that implementati=
ons could adapt their processing?</div>
<div><br></div><div>--Richard</div><div><br></div><div><br><div class=3D"gma=
il_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 10:24 A=
M, George Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:gffletch@aol.com"=
 target=3D"_blank">gffletch@aol.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Helvetica, Arial, sans-serif">+1<br>
      <br>
      Breaking deployed code as raised by Brian, Naveen and others is a
      critical consideration.<br>
      <br>
      Thanks,<br>
      George<br>
      <br>
    </font><div><div class=3D"h5">
    <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim
            and Karen, could you please do as Richard suggests and close
            this issue as =E2=80=9Cwon=E2=80=99t fix=E2=80=9D.<u></u><u></u>=
</span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u=
></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            Thank you,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            -- Mike<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u=
></span></p>
        <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-famil=
y:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"=
font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
            Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">=
mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
            <b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D=
"_blank">jose-chairs@tools.ietf.org</a>; Mike Jones<br>
            <b>Subject:</b> Fwd: [jose] #23: Make crypto independent of
            binary encoding (base64)<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
        <div>
          <p class=3D"MsoNormal">In other words: Chairs, feel free to
            close/wontfix :)<u></u><u></u></p>
          <div>
            <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>&nb=
sp;<u></u></p>
            <div>
              <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">--------=
--
                Forwarded message ----------<br>
                From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx=
" target=3D"_blank">rlb@ipv.sx</a>&gt;<br>
                Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                Subject: Re: [jose] #23: Make crypto independent of
                binary encoding (base64)<br>
                To: "Matt Miller (mamille2)" &lt;<a href=3D"mailto:mamille2@=
cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
                Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@tra=
c.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;,
                "&lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@t=
ools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.i=
etf.org</a>&gt;"
                &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@to=
ols.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ie=
tf.org</a>&gt;,

                "&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D=
"_blank">michael.jones@microsoft.com</a>&gt;"
                &lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D=
"_blank">michael.jones@microsoft.com</a>&gt;,
                "&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose=
@ietf.org</a>&gt;"
                &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<br>
                <br>
                <u></u><u></u></p>
              <div>
                <p class=3D"MsoNormal">To be clear, I structured my
                  message in two parts for a reason, to separate the
                  analysis from the opinion. &nbsp;I acknowledge that I am
                  but one voice here, and I'm increasingly hearing how
                  alone I am :)<u></u><u></u></p>
              </div>
              <div>
                <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u=
>&nbsp;<u></u></p>
                <div>
                  <div>
                    <p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23
                      PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" t=
arget=3D"_blank">rlb@ipv.sx</a>&gt;
                      wrote:<u></u><u></u></p>
                  </div>
                  <div>
                    <div>
                      <blockquote style=3D"border:none;border-left:solid #cc=
cccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class=3D"MsoNormal">&lt;impartial-analysis&gt=
;<u></u><u></u></p>
                          </div>
                          <p class=3D"MsoNormal">So just to be clear on
                            the trade-off the WG has to make:<u></u><u></u><=
/p>
                          <div>
                            <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the one hand:
                              Breaking every existing JWT implementation
                              in the world<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the other hand:
                              Eternally binding ourselves to base64
                              encoding, even if binary-safe encodings
                              become available (CBOR, MsgPack, etc.)<u></u><=
u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/impartial-analysis&n=
bsp;&gt;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;personal-opinion&gt;<=
u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">I have some sympathy
                              with JWT implementors. &nbsp;It sucks to have
                              to refactor code. &nbsp;But I think we're
                              literally talking about something like a
                              5-line patch. &nbsp;And early JWT implementors=

                              knew or should have known (to use a DC
                              phrase) that they were dealing with a
                              draft spec. &nbsp;As the W3C editor's draft
                              template says, in big bold red print,
                              "Implementors who are not taking part in
                              the discussions are likely to find the
                              specification changing out from under them
                              in incompatible ways."<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">As PHB pointed out in
                              the other thread, it would be nice to use
                              JWS and JWE in place of CMS one day,
                              without the base64 hit. &nbsp;We should incur
                              the implementation pain now, and get the
                              design right for the long run. &nbsp;Base64 is=

                              a hack around JSON; we should build the
                              system so that when we no longer need that
                              hack, it can go away.<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/personal-opinion&gt;=
<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#888=
888"><u></u>&nbsp;<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#888=
888">--Richard<u></u><u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#888=
888"><u></u>&nbsp;<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#888=
888"><u></u>&nbsp;<u></u></span></p>
                          </div>
                        </div>
                        <div>
                          <div>
                            <div>
                              <p class=3D"MsoNormal" style=3D"margin-bottom:=
12.0pt"><u></u>&nbsp;<u></u></p>
                              <div>
                                <p class=3D"MsoNormal">On Wed, Jun 12,
                                  2013 at 10:27 AM, Matt Miller
                                  (mamille2) &lt;<a href=3D"mailto:mamille2@=
cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;
                                  wrote:<u></u><u></u></p>
                                <p class=3D"MsoNormal">I did at first find
                                  it curious why the cryptographic
                                  operations were over the
                                  base64url-enccoded values, but I was
                                  also very focused on JWE, where I
                                  think the field separation problem is
                                  less of an issue (at least now). &nbsp;For=

                                  JWS, this would certainly cause
                                  problems without some manner of
                                  unambiguous field parameterization.<br>
                                  <br>
                                  I will note that unescaped NULL is not
                                  valid in JSON, so it could be used as
                                  a separator between the encoded header
                                  and the payload. &nbsp;I do find it
                                  interesting if JOSE could more easily
                                  and efficiently support other
                                  encodings. &nbsp;However, I think that
                                  while this is an interesting thought
                                  experiment, it seems we're too far
                                  down the path to seriously consider it
                                  unless the current state were shown to
                                  be horribly broken.<br>
                                  <br>
                                  <br>
                                  - m&amp;m<br>
                                  <br>
                                  Matt Miller &lt; <a href=3D"mailto:mamille=
2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>
                                  &gt;<br>
                                  Cisco Systems, Inc.<u></u><u></u></p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal"><br>
                                      On Jun 11, 2013, at 6:01 PM, jose
                                      issue tracker &lt;<a href=3D"mailto:tr=
ac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.o=
rg</a>&gt;
                                      wrote:<br>
                                      <br>
                                      &gt; #23: Make crypto independent
                                      of binary encoding (base64)<br>
                                      &gt;<br>
                                      &gt;<br>
                                      &gt; Comment (by <a href=3D"mailto:mic=
hael.jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>)=
:<br>
                                      &gt;<br>
                                      &gt; For both serializations, you
                                      already need the base64url encoded
                                      versions<br>
                                      &gt; of the JWS Header and the JWS
                                      Payload to preserve them in
                                      transmission, so<br>
                                      &gt; computing them isn't an extra
                                      burden. &nbsp;In the JWS Compact
                                      Serialization,<br>
                                      &gt; you already need the
                                      concatenation of the Encoded JWS
                                      Header, a period<br>
                                      &gt; character, and the Encoded
                                      JWS Payload, so computing that
                                      concatenation<br>
                                      &gt; isn't an extra burden. &nbsp;Give=
n
                                      you already have that quantity,
                                      computing<br>
                                      &gt; the signature over it is the
                                      easiest thing for developers to
                                      do, and it's<br>
                                      &gt; been shown to work well in
                                      practice. &nbsp;There's no compelling
                                      reason to make<br>
                                      &gt; this change.<br>
                                      &gt;<br>
                                      &gt; Even for the JSON
                                      Serialization, the only "extra"
                                      step that's required to<br>
                                      &gt; compute the signature is the
                                      concatenation with the period
                                      character - to<br>
                                      &gt; prevent shifting of data from
                                      one field to the other, as
                                      described by Jim<br>
                                      &gt; Schaad in the e-mail thread.
                                      &nbsp;So this step isn't actually
                                      "extra" at all -<br>
                                      &gt; it's necessary. &nbsp;It's also
                                      highly advantageous to use exactly
                                      the same<br>
                                      &gt; computation for both
                                      serializations, which is currently
                                      the case.<br>
                                      &gt;<br>
                                      &gt; Since there is no compelling
                                      reason to make this change, and
                                      since making<br>
                                      &gt; it could enable the
                                      "shifting" problem identified by
                                      Jim, it should not be<br>
                                      &gt; made.<br>
                                      &gt;<br>
                                      &gt; --<br>
                                      &gt;
-------------------------+-------------------------------------------------<=
br>
                                      &gt; Reporter: &nbsp;<a href=3D"mailto=
:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>
                                      &nbsp; | &nbsp; &nbsp; &nbsp; Owner:
                                      &nbsp;draft-ietf-jose-json-web-<br>
                                      &gt; &nbsp; &nbsp; Type: &nbsp;defect &=
nbsp; &nbsp; &nbsp; | &nbsp;<a href=3D"mailto:encryption@tools.ietf.org" tar=
get=3D"_blank">encryption@tools.ietf.org</a><br>
                                      &gt; Priority: &nbsp;major &nbsp; &nbs=
p; &nbsp; &nbsp;| &nbsp; &nbsp;
                                      &nbsp;Status: &nbsp;new<br>
                                      &gt; Component: &nbsp;json-web- &nbsp;=
 &nbsp;| &nbsp;
                                      Milestone:<br>
                                      &gt; &nbsp;encryption &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp;
                                      Version:<br>
                                      &gt; Severity: &nbsp;- &nbsp; &nbsp; &=
nbsp; &nbsp; &nbsp; &nbsp;|
                                      &nbsp;Resolution:<br>
                                      &gt; Keywords: &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; |<br>
                                      &gt;
-------------------------+-------------------------------------------------<=
br>
                                      &gt;<br>
                                      &gt; Ticket URL: &lt;<a href=3D"http:/=
/trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" target=3D"_blank">htt=
p://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                      &gt; jose &lt;<a href=3D"http://tools.=
ietf.org/jose/" target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                      &gt;<u></u><u></u></p>
                                  </div>
                                </div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-b=
ottom:12.0pt">&gt;
_______________________________________________<br>
                                      &gt; jose mailing list<br>
                                      &gt; <a href=3D"mailto:jose@ietf.org" t=
arget=3D"_blank">jose@ietf.org</a><br>
                                      &gt; <a href=3D"https://www.ietf.org/m=
ailman/listinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinf=
o/jose</a><u></u><u></u></p>
                                  </div>
                                </div>
                              </div>
                              <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p=
>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
              </div>
            </div>
            <p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
    </div></div><span class=3D"HOEnZb"><font color=3D"#888888"><div>-- <br>
      <a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank">&lt;XeC&gt;</a></div>
  </font></span></div>

</blockquote></div><br></div></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>____________________=
___________________________</span><br><span>jose mailing list</span><br><spa=
n><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a></span><br><span><a href=
=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman=
/listinfo/jose</a></span><br></div></blockquote></body></html>=

--Apple-Mail-30371A70-891E-4035-977F-563CF030E073--

From odonoghue@isoc.org  Thu Jun 13 11:04:49 2013
Return-Path: <odonoghue@isoc.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1CEC21F88D8 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 11:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8lU08rJzJPid for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 11:04:44 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0156.outbound.protection.outlook.com [207.46.163.156]) by ietfa.amsl.com (Postfix) with ESMTP id A186121F8BB7 for <jose@ietf.org>; Thu, 13 Jun 2013 11:04:43 -0700 (PDT)
Received: from BLUPR06MB180.namprd06.prod.outlook.com (10.242.190.27) by BLUPR06MB179.namprd06.prod.outlook.com (10.242.190.28) with Microsoft SMTP Server (TLS) id 15.0.702.21; Thu, 13 Jun 2013 18:04:41 +0000
Received: from BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.30]) by BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.137]) with mapi id 15.00.0702.005; Thu, 13 Jun 2013 18:04:41 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: thoughts on deployed code and breaking changes
Thread-Index: AQHOaGB5naUsuFvMWkWZkTeaLGe6Lg==
Date: Thu, 13 Jun 2013 18:04:41 +0000
Message-ID: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.245.107.12]
x-forefront-antispam-report: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BLUPR06MB179; H:BLUPR06MB180.namprd06.prod.outlook.com; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C0F601E6E2B51E4C88ACA73575AAA36A@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
Subject: [jose] thoughts on deployed code and breaking changes
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 18:04:49 -0000

Folks,

I *personally* believe the time for major breaking changes is past for this=
 version of the specification. I believe we are now in the phase of final c=
orrections and minor tweaks for a v1.0. We scheduled an interim meeting in =
April to get all remaining issues on the table and discussed. These specifi=
cations have been evolving for a long time. I am sure that they could be im=
proved in a myriad of ways, but at this point, without a strong rationale a=
nd a ground swell of working group support, we should work to complete what=
 we have. Any major refactoring or new  functionality should be deferred as=
 future work. At that time, we can work to "break cleanly with existing cod=
e." We better serve the IETF and the broader community by getting these spe=
cifications out the door.=20

We will have an interim teleconference Monday (with a few more possibly to =
follow) to review the implementation of the interim discussions and to disc=
uss any final issues. I strongly encourage folks to review the specificatio=
ns and the minutes of the interim with that in mind.=20

Regards,
Karen


From phil.hunt@oracle.com  Thu Jun 13 11:43:49 2013
Return-Path: <phil.hunt@oracle.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 537AA21F9A47 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 11:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.282
X-Spam-Level: 
X-Spam-Status: No, score=-6.282 tagged_above=-999 required=5 tests=[AWL=0.317,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NcCvEt1zjF3c for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 11:43:44 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF8321F8BB7 for <jose@ietf.org>; Thu, 13 Jun 2013 11:43:43 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r5DIhgS2012139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jun 2013 18:43:43 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5DIhf0O028663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jun 2013 18:43:42 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5DIhfKv018011; Thu, 13 Jun 2013 18:43:41 GMT
Received: from [192.168.1.128] (/24.86.29.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 13 Jun 2013 11:43:41 -0700
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org>
Date: Thu, 13 Jun 2013 11:43:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <664F0FD7-8DC5-4EAD-86B3-E231359B0A06@oracle.com>
References: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org>
To: "Karen O'Donoghue" <odonoghue@isoc.org>
X-Mailer: Apple Mail (2.1283)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] thoughts on deployed code and breaking changes
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 18:43:49 -0000

When I hear arguments like we can't consider BSON because it requires =
breaking changes, the hair on the back of my neck raises. If BSON =
support requires breaking change now, than it can NEVER be supported =
down the road. To me that makes the issue an omission. =20

Per section 4.1.1 of RFC2026:
>    A Proposed Standard should have no known technical omissions with
>    respect to the requirements placed upon it.  However, the IESG may
>    waive this requirement in order to allow a specification to advance
>    to the Proposed Standard state when it is considered to be useful =
and
>    necessary (and timely) even with known technical omissions.

I think there has been *some* discussion on the issue. But far too many =
do not want to discuss because of the possibility of breaking change, so =
no conclusion can be made as to whether this is an omission or not.

Finally, while the drafts are relatively stable, we are not officially =
stable. Anyone implementing now should know this. I point out that the =
drafts have not been approved as PROPOSED STANDARD yet, so changes =
should be expected.

Again, I have no opinion on this issue, but I am concerned about the =
lack of on-topic discussion.  Size has always been a major driving =
factor in the JOSE discussion. It does seem on topic to me that the B64 =
support method for binary doesn't meet the design criteria that has been =
used regarding small size. I don't necessarily think binary has to be =
solved now. But important questions must be discussed.

Is there a way binary can be supported?  Can BSON be delayed into a =
future draft without breaking the current drafts?  If there is any sense =
of breaking changes, NOW is the time to make those changes - not later.

Finally, I was surprised to learn that 2026 doesn't even require =
deployed code in PROPOSED STANDARD. That just points out that these =
drafts are still incredibly *early* in their design despite assertions =
of stability.  The fact that many are in production doesn't mean the =
process gets skipped. We cannot assume DRAFT STANDARD status when we =
aren't even at PROPOSED STANDARD status.

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com





On 2013-06-13, at 11:04 AM, Karen O'Donoghue wrote:

> Folks,
>=20
> I *personally* believe the time for major breaking changes is past for =
this version of the specification. I believe we are now in the phase of =
final corrections and minor tweaks for a v1.0. We scheduled an interim =
meeting in April to get all remaining issues on the table and discussed. =
These specifications have been evolving for a long time. I am sure that =
they could be improved in a myriad of ways, but at this point, without a =
strong rationale and a ground swell of working group support, we should =
work to complete what we have. Any major refactoring or new  =
functionality should be deferred as future work. At that time, we can =
work to "break cleanly with existing code." We better serve the IETF and =
the broader community by getting these specifications out the door.=20
>=20
> We will have an interim teleconference Monday (with a few more =
possibly to follow) to review the implementation of the interim =
discussions and to discuss any final issues. I strongly encourage folks =
to review the specifications and the minutes of the interim with that in =
mind.=20
>=20
> Regards,
> Karen
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From rlb@ipv.sx  Thu Jun 13 12:31:25 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A52321F9A14 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 12:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.303
X-Spam-Level: 
X-Spam-Status: No, score=-0.303 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48RJGpwkLQfC for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 12:31:21 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4F521F9399 for <jose@ietf.org>; Thu, 13 Jun 2013 12:31:21 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id m1so9384753oag.20 for <jose@ietf.org>; Thu, 13 Jun 2013 12:31:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Lh6gFoiqXVn2iyFsVXvDIZvFb2477gUT5Xgiw1YqolE=; b=P0TM/n84zrWyuDo1YBBuKQxf/mWbpa6MLfWW+Z3FK4931tvvyK2H3w6Hjg6+5nWYo7 1/8gtxSPdlVZ/4cCgVz3d0WHiTvyTw21uG8ew53mZHA3fo6+z59fljP3yP+dycO0GaAc NCphTxwGZOH+d8idh5endHVN8/qZ7zsJ+5sGo6mSltwnSwmr5S8xm49vLeoNY5mDMPUI GHfwTn/AAh2zFYmrK4hXT2iQX7vsyIl6EaUNP5r5U3X/FY+hY98PqkrgYPM76vlHp/Pv W/W5CwDHH26gYqRrDoutPZu2lrbn+OzR9Cq6GX7TtU8qdxny+exKMP1v6pcGGhRaqk1E I79g==
MIME-Version: 1.0
X-Received: by 10.60.42.237 with SMTP id r13mr1895389oel.61.1371151880221; Thu, 13 Jun 2013 12:31:20 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Thu, 13 Jun 2013 12:31:20 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org>
References: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org>
Date: Thu, 13 Jun 2013 15:31:20 -0400
Message-ID: <CAL02cgSMJSPaGmtPmYA=XrtOUfgo=trsAuHxCKXXg9YH3hpc9A@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Karen O'Donoghue" <odonoghue@isoc.org>
Content-Type: multipart/alternative; boundary=001a11c206aac10c3304df0e2cf6
X-Gm-Message-State: ALoCoQnZLn1HzJWWRrz2kO4xv5k1tJxDqI12GXQSqq5ulueYc1e9xfJXfgDozhDhzbVo/EDWi5IJ
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] thoughts on deployed code and breaking changes
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 19:31:25 -0000

--001a11c206aac10c3304df0e2cf6
Content-Type: text/plain; charset=ISO-8859-1

Could we at least clarify that the embargo on breaking changes is to the
*compact* serialization of *JWS*?  All of the backward compatibility
concerns we've heard are for JWT, which is primarily based on JWS.  And as
far as I know, there's been no implementation of the JSON serializations
yet, so we don't have the same compatibility burden.

I don't mean to imply that I've got a bunch of horrible stuff queued up.
 I'm as interested in getting this done as the next guy.  I just want to
make clear that things like ISSUE-20 and Jim's suggestion on unencoded
protected headers are not ruled out of bounds.

--Richard


On Thu, Jun 13, 2013 at 2:04 PM, Karen O'Donoghue <odonoghue@isoc.org>wrote:

> Folks,
>
> I *personally* believe the time for major breaking changes is past for
> this version of the specification. I believe we are now in the phase of
> final corrections and minor tweaks for a v1.0. We scheduled an interim
> meeting in April to get all remaining issues on the table and discussed.
> These specifications have been evolving for a long time. I am sure that
> they could be improved in a myriad of ways, but at this point, without a
> strong rationale and a ground swell of working group support, we should
> work to complete what we have. Any major refactoring or new  functionality
> should be deferred as future work. At that time, we can work to "break
> cleanly with existing code." We better serve the IETF and the broader
> community by getting these specifications out the door.
>
> We will have an interim teleconference Monday (with a few more possibly to
> follow) to review the implementation of the interim discussions and to
> discuss any final issues. I strongly encourage folks to review the
> specifications and the minutes of the interim with that in mind.
>
> Regards,
> Karen
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--001a11c206aac10c3304df0e2cf6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Could we at least clarify that the embargo on breaking cha=
nges is to the *compact* serialization of *JWS*? =A0All of the backward com=
patibility concerns we&#39;ve heard are for JWT, which is primarily based o=
n JWS. =A0And as far as I know, there&#39;s been no implementation of the J=
SON serializations yet, so we don&#39;t have the same compatibility burden.=
 =A0<div>
<br></div><div>I don&#39;t mean to imply that I&#39;ve got a bunch of horri=
ble stuff queued up. =A0I&#39;m as interested in getting this done as the n=
ext guy. =A0I just want to make clear that things like ISSUE-20 and Jim&#39=
;s suggestion on unencoded protected headers are not ruled out of bounds.<d=
iv>
<br></div><div>--Richard =A0</div></div></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 2:04 PM, Karen O&#=
39;Donoghue <span dir=3D"ltr">&lt;<a href=3D"mailto:odonoghue@isoc.org" tar=
get=3D"_blank">odonoghue@isoc.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Folks,<br>
<br>
I *personally* believe the time for major breaking changes is past for this=
 version of the specification. I believe we are now in the phase of final c=
orrections and minor tweaks for a v1.0. We scheduled an interim meeting in =
April to get all remaining issues on the table and discussed. These specifi=
cations have been evolving for a long time. I am sure that they could be im=
proved in a myriad of ways, but at this point, without a strong rationale a=
nd a ground swell of working group support, we should work to complete what=
 we have. Any major refactoring or new =A0functionality should be deferred =
as future work. At that time, we can work to &quot;break cleanly with exist=
ing code.&quot; We better serve the IETF and the broader community by getti=
ng these specifications out the door.<br>

<br>
We will have an interim teleconference Monday (with a few more possibly to =
follow) to review the implementation of the interim discussions and to disc=
uss any final issues. I strongly encourage folks to review the specificatio=
ns and the minutes of the interim with that in mind.<br>

<br>
Regards,<br>
Karen<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote></div><br></div>

--001a11c206aac10c3304df0e2cf6--

From odonoghue@isoc.org  Thu Jun 13 14:00:57 2013
Return-Path: <odonoghue@isoc.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E50AA21F9A36 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 14:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avIkjPD9Yo4C for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 14:00:53 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF0621F8B21 for <jose@ietf.org>; Thu, 13 Jun 2013 14:00:53 -0700 (PDT)
Received: from BLUPR06MB180.namprd06.prod.outlook.com (10.242.190.27) by BLUPR06MB178.namprd06.prod.outlook.com (10.242.190.18) with Microsoft SMTP Server (TLS) id 15.0.702.21; Thu, 13 Jun 2013 21:00:46 +0000
Received: from BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.30]) by BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.137]) with mapi id 15.00.0702.005; Thu, 13 Jun 2013 21:00:46 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] thoughts on deployed code and breaking changes
Thread-Index: AQHOaGB5naUsuFvMWkWZkTeaLGe6Lpk0CGgA///N2IA=
Date: Thu, 13 Jun 2013 21:00:45 +0000
Message-ID: <51BA2C35.9080904@isoc.org>
References: <DD357551-474C-469B-BE1B-19AE1B459EF0@isoc.org> <CAL02cgSMJSPaGmtPmYA=XrtOUfgo=trsAuHxCKXXg9YH3hpc9A@mail.gmail.com>
In-Reply-To: <CAL02cgSMJSPaGmtPmYA=XrtOUfgo=trsAuHxCKXXg9YH3hpc9A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-imapappendstamp: BLUPR06MB180.namprd06.prod.outlook.com (15.00.0702.000)
x-originating-ip: [24.245.107.12]
x-forefront-antispam-report: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BLUPR06MB178; H:BLUPR06MB180.namprd06.prod.outlook.com; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_51BA2C359080904isocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] thoughts on deployed code and breaking changes
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 21:00:58 -0000

--_000_51BA2C359080904isocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

To be clear, I didn't declare an embargo on breaking changes. I just set wh=
at I believe to be a reasonable metric at this stage of the spec developmen=
t as "strong rationale and a ground swell of working group support". I woul=
d imagine that said working group support would be easier to achieve for th=
e JSON serializations than the compact serializations.

I'm also trying to ensure that every thing under consideration is on the ta=
ble. There is a time for more open ended conversations, and there is a time=
 to ship what is done. While I don't think these are the only consideration=
s, I do think we need to be mindful of the amount of time spent on this thu=
s far, the external standards efforts looking to the results of this work, =
and the currently deployed implementations.

Please, I urge everyone, review the latest specs. If there are needed chang=
es, provide a strong rationale and clear concise text for the documents ASA=
P.

Karen

On 6/13/13 3:31 PM, Richard Barnes wrote:
Could we at least clarify that the embargo on breaking changes is to the *c=
ompact* serialization of *JWS*?  All of the backward compatibility concerns=
 we've heard are for JWT, which is primarily based on JWS.  And as far as I=
 know, there's been no implementation of the JSON serializations yet, so we=
 don't have the same compatibility burden.

I don't mean to imply that I've got a bunch of horrible stuff queued up.  I=
'm as interested in getting this done as the next guy.  I just want to make=
 clear that things like ISSUE-20 and Jim's suggestion on unencoded protecte=
d headers are not ruled out of bounds.

--Richard


On Thu, Jun 13, 2013 at 2:04 PM, Karen O'Donoghue <odonoghue@isoc.org<mailt=
o:odonoghue@isoc.org>> wrote:
Folks,

I *personally* believe the time for major breaking changes is past for this=
 version of the specification. I believe we are now in the phase of final c=
orrections and minor tweaks for a v1.0. We scheduled an interim meeting in =
April to get all remaining issues on the table and discussed. These specifi=
cations have been evolving for a long time. I am sure that they could be im=
proved in a myriad of ways, but at this point, without a strong rationale a=
nd a ground swell of working group support, we should work to complete what=
 we have. Any major refactoring or new  functionality should be deferred as=
 future work. At that time, we can work to "break cleanly with existing cod=
e." We better serve the IETF and the broader community by getting these spe=
cifications out the door.

We will have an interim teleconference Monday (with a few more possibly to =
follow) to review the implementation of the interim discussions and to disc=
uss any final issues. I strongly encourage folks to review the specificatio=
ns and the minutes of the interim with that in mind.

Regards,
Karen

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--_000_51BA2C359080904isocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <D4565760ACFD1848B4D757EF1896BF08@isoc.onmicrosoft.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" id=3D"owaParaStyle" style=3D"display: none; ">P {m=
argin-top:0;margin-bottom:0;}</style>
</head>
<body bgcolor=3D"#FFFFFF" dir=3D"ltr" fpstyle=3D"1" aria-label=3D"Message b=
ody" tabindex=3D"0" style=3D"">
<div name=3D"divtagdefaultwrapper" id=3D"divtagdefaultwrapper" style=3D"fon=
t-family: Calibri,Arial,Helvetica,sans-serif; font-size: 12pt; color: #0000=
00; margin: 0">
<div class=3D"moz-cite-prefix">To be clear, I didn't declare an embargo on =
breaking changes. I just set what I believe to be a reasonable metric at th=
is stage of the spec development as &quot;strong rationale and a ground swe=
ll of working group support&quot;. I would imagine
 that said working group support would be easier to achieve for the JSON se=
rializations than the compact serializations.
<br>
<br>
I'm also trying to ensure that every thing under consideration is on the ta=
ble. There is a time for more open ended conversations, and there is a time=
 to ship what is done. While I don't think these are the only consideration=
s, I do think we need to be mindful
 of the amount of time spent on this thus far, the external standards effor=
ts looking to the results of this work, and the currently deployed implemen=
tations.
<br>
<br>
Please, I urge everyone, review the latest specs. If there are needed chang=
es, provide a strong rationale and clear concise text for the documents ASA=
P.<br>
<br>
Karen<br>
<br>
On 6/13/13 3:31 PM, Richard Barnes wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">Could we at least clarify that the embargo on breaking cha=
nges is to the *compact* serialization of *JWS*? &nbsp;All of the backward =
compatibility concerns we've heard are for JWT, which is primarily based on=
 JWS. &nbsp;And as far as I know, there's been
 no implementation of the JSON serializations yet, so we don't have the sam=
e compatibility burden. &nbsp;
<div><br>
</div>
<div>I don't mean to imply that I've got a bunch of horrible stuff queued u=
p. &nbsp;I'm as interested in getting this done as the next guy. &nbsp;I ju=
st want to make clear that things like ISSUE-20 and Jim's suggestion on une=
ncoded protected headers are not ruled out
 of bounds.
<div><br>
</div>
<div>--Richard &nbsp;</div>
</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 2:04 PM, Karen O'Donoghu=
e <span dir=3D"ltr">
&lt;<a href=3D"mailto:odonoghue@isoc.org" target=3D"_blank">odonoghue@isoc.=
org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=0A=
            .8ex; border-left:1px #ccc solid; padding-left:1ex">
Folks,<br>
<br>
I *personally* believe the time for major breaking changes is past for this=
 version of the specification. I believe we are now in the phase of final c=
orrections and minor tweaks for a v1.0. We scheduled an interim meeting in =
April to get all remaining issues
 on the table and discussed. These specifications have been evolving for a =
long time. I am sure that they could be improved in a myriad of ways, but a=
t this point, without a strong rationale and a ground swell of working grou=
p support, we should work to complete
 what we have. Any major refactoring or new &nbsp;functionality should be d=
eferred as future work. At that time, we can work to &quot;break cleanly wi=
th existing code.&quot; We better serve the IETF and the broader community =
by getting these specifications out the door.<br>
<br>
We will have an interim teleconference Monday (with a few more possibly to =
follow) to review the implementation of the interim discussions and to disc=
uss any final issues. I strongly encourage folks to review the specificatio=
ns and the minutes of the interim
 with that in mind.<br>
<br>
Regards,<br>
Karen<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</body>
</html>

--_000_51BA2C359080904isocorg_--

From mamille2@cisco.com  Thu Jun 13 15:04:25 2013
Return-Path: <mamille2@cisco.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F1721F9994 for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 15:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7mjkcEJh1rTg for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 15:04:20 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 1F58B21F997A for <jose@ietf.org>; Thu, 13 Jun 2013 15:04:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8110; q=dns/txt; s=iport; t=1371161060; x=1372370660; h=from:to:subject:date:message-id:references:mime-version; bh=TtVb1caKTU5ao7hrp3CKQoA1nB2hh4CGqiIQ/1jNswE=; b=N26TCl3C3ehbCZhffw4Up5nPvhbW+I7DK6RlPU8aidfERKCZ3C5vOHXo BWalUMcAweAaJD8vmSJNP8rnpJ5LrSsPMM+OQ24sYDBo5YDA0/yVdKQgZ /AL9eM0+gxo95k6RYOTVuh0myb2zDEmLjsUqXIXcsLDJJ34Yq032y9lT/ w=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAKVBulGtJXG+/2dsb2JhbABagwkwQwa+QoECFnSCIwEBAQMBAQEBaxALAgEZAwECCw4WAiULFAcCCAIEEwgBBYd6BgcFuwePFhYKEwsSgmdhA5ABgSyHPYp4hSGDD4In
X-IronPort-AV: E=Sophos;i="4.87,861,1363132800";  d="p7s'?scan'208";a="222580527"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 13 Jun 2013 22:04:16 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r5DM4GRP032219 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <jose@ietf.org>; Thu, 13 Jun 2013 22:04:16 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Thu, 13 Jun 2013 17:04:15 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "<jose@ietf.org>" <jose@ietf.org>
Thread-Topic: I-D Action: draft-miller-jose-jwe-protected-jwk-02.txt
Thread-Index: AQHOaHJLHJXCSldC6UioyqurpQ5EeQ==
Date: Thu, 13 Jun 2013 22:04:14 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411528658D@xmb-aln-x11.cisco.com>
References: <20130613201144.2181.7575.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.129.24.59]
Content-Type: multipart/signed; boundary="Apple-Mail=_0CBECA69-7197-4BA1-9D9B-A50ACF06A529"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Subject: [jose] Fwd: I-D Action: draft-miller-jose-jwe-protected-jwk-02.txt
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 13 Jun 2013 22:04:25 -0000

--Apple-Mail=_0CBECA69-7197-4BA1-9D9B-A50ACF06A529
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

FYI,

This revision incorporates feedback from the JOSE interim.  While there =
were some changes outside of the algorithms, it was merely to keep pace =
wit the current state of JW(K|E) documents.


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: I-D Action: draft-miller-jose-jwe-protected-jwk-02.txt
> Date: June 13, 2013 2:11:44 PM MDT
> To: <i-d-announce@ietf.org>
> Reply-To: <internet-drafts@ietf.org>
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>=20
>=20
> 	Title           : Using JavaScript Object Notation (JSON) Web =
Encryption (JWE) for Protecting JSON Web Key (JWK) Objects
> 	Author(s)       : Matthew Miller
> 	Filename        : draft-miller-jose-jwe-protected-jwk-02.txt
> 	Pages           : 16
> 	Date            : 2013-06-13
>=20
> Abstract:
>   This document specifies an approach to protecting a private key
>   formatted as a JavaScript Syntax Object Notation (JSON) Web Key =
(JWK)
>   object using JSON Web Encryption (JWE).  This document also =
specifies
>   a set of algorithms for protecting such content using password-based
>   cryptography.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-miller-jose-jwe-protected-jwk
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-miller-jose-jwe-protected-jwk-02
>=20
> A diff from the previous version is available at:
> =
http://www.ietf.org/rfcdiff?url2=3Ddraft-miller-jose-jwe-protected-jwk-02
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


--Apple-Mail=_0CBECA69-7197-4BA1-9D9B-A50ACF06A529
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMezCCBjQw
ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX
DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK
75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC
+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD
z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr
/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc
fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG
XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt
UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R
HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv
sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq
+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT
zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq
Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1
9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPzCCBSeg
AwIBAgIDBoRIMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN
MTMwNDMwMjE1NDQyWhcNMTQwNTAyMDUzOTA0WjBbMRkwFwYDVQQNExBiN2F6NndOY0t0R3JtMEpF
MRswGQYDVQQDDBJtYW1pbGxlMkBjaXNjby5jb20xITAfBgkqhkiG9w0BCQEWEm1hbWlsbGUyQGNp
c2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJbKBMsG+9UFTx9uq/bhhXgu
vJvO8z7cwKaqqwZhVf5z/kHFyCNijtmTOE+YXjA8mWR4aoBwB5SvGypI/cJUofJ+AlBTC4g+RMx/
K0Ab4/jQqTQz9CDzMOB+Wm+rt8ZJ7A8ZzOJmNDAsf/VvB8l2A1SQz1UsAixgH16NTr8SlblAXEKk
4hwpCudUiNjjQokqJ0H686UBKVorcZSgXaza8XMqGtJF/8mNhR9GQYi7Xht1ky+9LFOrto2daZto
KJRwMeVusVdHUeKEQSu7jztw8HchH3KEb7Q+r5X+hhDZoddfKE8d5eyPuhiZdrzv7OlNZ0fSLdx7
3AE3nx9/R5YlXucCAwEAAaOCAtgwggLUMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQW
MBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUxGd+/qrdVudHrIKkw5xOMY7eaLUwHwYD
VR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWFtaWxsZTJAY2lzY28u
Y29tMIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9m
IHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBw
dXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYG
A1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4G
CCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy
dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAlDhXbGEI7lbqUcu5r2JHZaMsbRZda/99ZqODzWGX
0llou9jGccsAWDPPwRRe2+ROpXfH4cuJZElTcLDeZSp/qpXKhjYieFSX8+Ml9sKEj5UOSqQLyoLk
PtrIJV12Jk3nuG2Jc0UeEnGwK/aqtzy7+bfEVI0ziyVM2gChHh0RH74KyiwYWknbOTRIkZcz/ulE
DVFQp63uj6wfmDNvAUHBAdhKVqA1S/rfP1KcDZpf1NfvwXJibiqTRA6K1EOxTJOP41n/XdvHqHXL
RWL2xrOUI9/URANr/ok3OrsuZEMFnAAGefS1bWS/hFtUGVkHGiKEBbyDW7da2ULXbuC7umrQnzGC
A28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDAJBgUrDgMCGgUA
oIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MTMyMjA0
MTRaMCMGCSqGSIb3DQEJBDEWBBRehO+a03KMqfyfnHNeE3XGq7N8ITCBpQYJKwYBBAGCNxAEMYGX
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3Mg
MSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDCBpwYLKoZIhvcNAQkQAgsxgZeg
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBoRIMA0GCSqGSIb3DQEBAQUABIIBAGiD
oTTYUYyqapAymE5sNqAtFxiCutFLQMAoopHRx6DG46N44wUGw+rNbiZBholIzJezfrC7dDMJtjvk
2dmzn4MT+TKDwAwUsobPbcoDG1GoqqHKwVvxE2iDkXESCqLJ3qd4KnaiTU4I7RcM9hW0MbFFxrbF
94KYE6grknhWtUmmHQyc37tKdMS15BmI4hhdifhFL7MVdZjMcH6xqpgGjUL05Mv9WCcG5VOD4Vsd
/hInNVfz0g1UqCeDkAEdG6IK9JIrXMhqqgBvOZJvqCTMbzM4+mLXEnDKpYWiGttKQqZqSSZoYJAf
frQimjHosbTHgTMDbwUGdoAVY5v/pcDW/0gAAAAAAAA=

--Apple-Mail=_0CBECA69-7197-4BA1-9D9B-A50ACF06A529--

From Michael.Jones@microsoft.com  Thu Jun 13 18:05:31 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C83D121F9B4B for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 18:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wYXGnavkJWEh for <jose@ietfa.amsl.com>; Thu, 13 Jun 2013 18:05:21 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) by ietfa.amsl.com (Postfix) with ESMTP id A6ABA21F9B23 for <jose@ietf.org>; Thu, 13 Jun 2013 18:05:21 -0700 (PDT)
Received: from BN1BFFO11FD027.protection.gbl (10.58.52.203) by BN1AFFO11HUB030.protection.gbl (10.58.52.140) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 14 Jun 2013 01:05:19 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD027.mail.protection.outlook.com (10.58.53.87) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 14 Jun 2013 01:05:19 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Fri, 14 Jun 2013 01:04:14 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: AES GCM Key Wrapping Draft
Thread-Index: Ac5omxDnZl7l58E+Tzunyo2ac2ccAQ==
Date: Fri, 14 Jun 2013 01:04:14 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678538F7@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678538F7TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377424003)(13464003)(189002)(199002)(377454002)(74876001)(20776003)(16406001)(512874002)(80022001)(74706001)(69226001)(65816001)(15202345002)(66066001)(16236675002)(81342001)(63696002)(81542001)(54316002)(56776001)(55846006)(56816003)(74502001)(77096001)(74662001)(6806003)(74366001)(47736001)(4396001)(59766001)(46102001)(50986001)(76786001)(53806001)(76176001)(77982001)(49866001)(51856001)(31966008)(54356001)(76482001)(76796001)(79102001)(71186001)(47446002)(47976001)(16297215003)(33656001)(6606295001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB030; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08770259B4
Subject: [jose] AES GCM Key Wrapping Draft
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 01:05:32 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678538F7TK5EX14MBXC283r_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QW4gYWN0aW9uIGl0ZW0gSSB0b29rIG9uIGF0IHRoZSBpbnRlcmltIHdvcmtpbmcgZ3JvdXAgbWVl
dGluZyB3YXMgdG8gcHJvZHVjZSBhIGRyYWZ0IHNob3dpbmcgaG93IGtleSB3cmFwcGluZyBjYW4g
YmUgYWNjb21wbGlzaGVkIHdpdGggQUVTIEdDTSBmb3IgSldFLiAgVGhpcyBkcmFmdCBpcyBub3cg
YXZhaWxhYmxlIGFzIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpvbmVzLWpvc2Ut
YWVzLWdjbS1rZXktd3JhcC0wMC4gIFRoZSBzcGVjaWZpY2F0aW9uIGlzIGFsc28gYXZhaWxhYmxl
IGluIEhUTUwgZm9ybWF0IGF0IGh0dHA6Ly9zZWxmLWlzc3VlZC5pbmZvL2RvY3MvZHJhZnQtam9u
ZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwLTAwLmh0bWwuDQoNCg0KDQpUaGUgY29yZSB0ZWNobmlj
YWwgY29udGVudCBpcyBhbGwgaW4gU2VjdGlvbiAzLCB3aGljaCBJ4oCZdmUgaW5jbHVkZWQgaW4g
aXRzIGVudGlyZXR5IGJlbG93IGJlY2F1c2UgaXTigJlzIHNvIHNob3J0Lg0KDQoNCg0KMy4gIEtl
eSBFbmNyeXB0aW9uIHdpdGggQUVTIEdDTQ0KDQpUaGlzIHNlY3Rpb24gZGVmaW5lcyB0aGUgc3Bl
Y2lmaWNzIG9mIGVuY3J5cHRpbmcgYSBKV0UgQ29udGVudCBFbmNyeXB0aW9uIEtleSAoQ0VLKSB3
aXRoIEFkdmFuY2VkIEVuY3J5cHRpb24gU3RhbmRhcmQgKEFFUykgaW4gR2Fsb2lzL0NvdW50ZXIg
TW9kZSAoR0NNKSBbQUVTXTxodHRwOi8vc2VsZi1pc3N1ZWQuaW5mby9kb2NzL2RyYWZ0LWpvbmVz
LWpvc2UtYWVzLWdjbS1rZXktd3JhcC0wMC5odG1sI0FFUz4gW05JU1QuODAw4oCRMzhEXTxodHRw
Oi8vc2VsZi1pc3N1ZWQuaW5mby9kb2NzL2RyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXktd3Jh
cC0wMC5odG1sI05JU1QuODAwLTM4RD4gdXNpbmcgMTI4IG9yIDI1NiBiaXQga2V5cy4gVGhlIGFs
ZyBoZWFkZXIgcGFyYW1ldGVyIHZhbHVlcyBBMTI4R0NNS1cgb3IgQTI1NkdDTUtXIGFyZSByZXNw
ZWN0aXZlbHkgdXNlZCBpbiB0aGlzIGNhc2UuDQoNClVzZSBvZiBhbiBJbml0aWFsaXphdGlvbiBW
ZWN0b3Igb2Ygc2l6ZSA5NiBiaXRzIGlzIFJFUVVJUkVEIHdpdGggdGhpcyBhbGdvcml0aG0uDQoN
ClRoZSBBZGRpdGlvbmFsIEF1dGhlbnRpY2F0ZWQgRGF0YSB2YWx1ZSB1c2VkIGlzIHRoZSBlbXB0
eSBvY3RldCBzdHJpbmcuDQoNClRoZSByZXF1ZXN0ZWQgc2l6ZSBvZiB0aGUgQXV0aGVudGljYXRp
b24gVGFnIG91dHB1dCBNVVNUIGJlIDEyOCBiaXRzLCByZWdhcmRsZXNzIG9mIHRoZSBrZXkgc2l6
ZS4NCg0KTGV0IEpXRSBFbmNyeXB0ZWQgS2V5IHZhbHVlIGJlIHRoZSBjb25jYXRlbmF0aW9uIG9m
IHRoZSBJbml0aWFsaXphdGlvbiBWZWN0b3IgdmFsdWUsIHRoZSBDaXBoZXJ0ZXh0IG91dHB1dCwg
YW5kIHRoZSBBdXRoZW50aWNhdGlvbiBUYWcgb3V0cHV0Lg0KDQpEdXJpbmcga2V5IGRlY3J5cHRp
b24sIHRoZSBKV0UgRW5jcnlwdGVkIEtleSB2YWx1ZSBpcyBzcGxpdCBpbnRvIHRocmVlIGlucHV0
cyB0byB0aGUgQUVTIEdDTSBkZWNyeXB0aW9uIGFsZ29yaXRobTogdGhlIGZpcnN0IDk2IGJpdHMg
YXJlIHRoZSBJbml0aWFsaXphdGlvbiBWZWN0b3IgdmFsdWUsIHRoZSBsYXN0IDEyOCBiaXRzIGFy
ZSB0aGUgQXV0aGVudGljYXRpb24gVGFnIHZhbHVlLCBhbmQgdGhlIHJlbWFpbmluZyBiaXRzIGlu
IGJldHdlZW4gYXJlIHRoZSBDaXBoZXJ0ZXh0IHZhbHVlLg0KDQoNCg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIC0tIE1pa2UN
Cg0KDQoNClAuUy4gIFJpY2hhcmQsIHVubGlrZSB3aGF0IEkgZGVzY3JpYmVkIGluIG91ciBwcml2
YXRlIGNvbnZlcnNhdGlvbiwgdGhpcyBzcGVjaWZpY2F0aW9uIHVzZXMgbm8gYWRkaXRpb25hbCBo
ZWFkZXIgcGFyYW1ldGVyIHZhbHVlcy4NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmddDQpTZW50OiBUaHVyc2RheSwgSnVuZSAxMywgMjAxMyA1OjUzIFBNDQpUbzogTWlr
ZSBKb25lczsgTWlrZSBKb25lcw0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZv
ciBkcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAtMDAudHh0DQoNCg0KDQpBIG5ldyB2
ZXJzaW9uIG9mIEktRCwgZHJhZnQtam9uZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwLTAwLnR4dA0K
DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE1pY2hhZWwgQi4gSm9uZXMgYW5k
IHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5Lg0KDQoNCg0KRmlsZW5hbWU6ICAgICAgICAg
ICAgZHJhZnQtam9uZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwDQoNClJldmlzaW9uOiAgICAgICAg
ICAgICAgMDANCg0KVGl0bGU6ICAgICAgICAgICAgICAgICAgICAgIEtleSBXcmFwcGluZyB3aXRo
IEFFUyBHQ00gZm9yIEpXRQ0KDQpDcmVhdGlvbiBkYXRlOiAgIDIwMTMtMDYtMTMNCg0KR3JvdXA6
ICAgICAgICAgICAgICAgICAgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQoNCk51bWJlciBvZiBwYWdl
czogNQ0KDQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJh
ZnRzL2RyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXktd3JhcC0wMC50eHQNCg0KU3RhdHVzOiAg
ICAgICAgICBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWpvbmVzLWpvc2Ut
YWVzLWdjbS1rZXktd3JhcA0KDQpIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXktd3JhcC0wMA0KDQoNCg0KQWJzdHJh
Y3Q6DQoNCiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIGhvdyB0byBlbmNyeXB0ICh3cmFw
KSBrZXlzIHdpdGggdGhlIEFFUw0KDQogICBHQ00gYWxnb3JpdGhtIGZvciBKU09OIFdlYiBFbmNy
eXB0aW9uIChKV0UpIG9iamVjdHMuDQoNCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQoNCg==

--_000_4E1F6AAD24975D4BA5B1680429673943678538F7TK5EX14MBXC283r_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZlcmRhbmE7DQoJcGFu
b3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAu
TXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToi
Q2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCmgzDQoJe21zby1zdHlsZS1wcmlvcml0eTo5Ow0KCW1z
by1zdHlsZS1saW5rOiJIZWFkaW5nIDMgQ2hhciI7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJn
aW4tbGVmdDowaW47DQoJZm9udC1zaXplOjEzLjVwdDsNCglmb250LWZhbWlseToiSGVsdmV0aWNh
Iiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzMzMzMzMzsNCglmb250LXdlaWdodDpib2xkO30NCmE6
bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNv
SHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBs
ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29Q
bGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MjQuMHB0Ow0KCW1zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjI0LjBwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KdHQNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6IzAwMzM2Njt9
DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7
DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCnNwYW4uSGVhZGluZzNDaGFy
DQoJe21zby1zdHlsZS1uYW1lOiJIZWFkaW5nIDMgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk7DQoJbXNvLXN0eWxlLWxpbms6IkhlYWRpbmcgMyI7DQoJZm9udC1mYW1pbHk6IkhlbHZldGlj
YSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMzMzMzMzM7DQoJZm9udC13ZWlnaHQ6Ym9sZDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjgu
NWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJF
Ti1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlv
bjEiPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QW4gYWN0aW9uIGl0ZW0gSSB0b29rIG9uIGF0
IHRoZSBpbnRlcmltIHdvcmtpbmcgZ3JvdXAgbWVldGluZyB3YXMgdG8gcHJvZHVjZSBhIGRyYWZ0
IHNob3dpbmcgaG93IGtleSB3cmFwcGluZyBjYW4gYmUgYWNjb21wbGlzaGVkIHdpdGggQUVTIEdD
TSBmb3IgSldFLiZuYnNwOyBUaGlzIGRyYWZ0IGlzIG5vdyBhdmFpbGFibGUgYXMNCjxhIGhyZWY9
Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXkt
d3JhcC0wMCI+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtam9uZXMtam9zZS1hZXMt
Z2NtLWtleS13cmFwLTAwPC9hPi4gJm5ic3A7VGhlIHNwZWNpZmljYXRpb24gaXMgYWxzbyBhdmFp
bGFibGUgaW4gSFRNTCBmb3JtYXQgYXQNCjxhIGhyZWY9Imh0dHA6Ly9zZWxmLWlzc3VlZC5pbmZv
L2RvY3MvZHJhZnQtam9uZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwLTAwLmh0bWwiPg0KaHR0cDov
L3NlbGYtaXNzdWVkLmluZm8vZG9jcy9kcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAt
MDAuaHRtbDwvYT4uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoZSBjb3JlIHRlY2hu
aWNhbCBjb250ZW50IGlzIGFsbCBpbiBTZWN0aW9uIDMsIHdoaWNoIEnigJl2ZSBpbmNsdWRlZCBp
biBpdHMgZW50aXJldHkgYmVsb3cgYmVjYXVzZSBpdOKAmXMgc28gc2hvcnQuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxoMz48
c3BhbiBsYW5nPSJFTiI+My4mbmJzcDsgS2V5IEVuY3J5cHRpb24gd2l0aCBBRVMgR0NNPG86cD48
L286cD48L3NwYW4+PC9oMz4NCjxwPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5U
aGlzIHNlY3Rpb24gZGVmaW5lcyB0aGUgc3BlY2lmaWNzIG9mIGVuY3J5cHRpbmcgYSBKV0UgQ29u
dGVudCBFbmNyeXB0aW9uIEtleSAoQ0VLKSB3aXRoIEFkdmFuY2VkIEVuY3J5cHRpb24gU3RhbmRh
cmQgKEFFUykgaW4gR2Fsb2lzL0NvdW50ZXIgTW9kZSAoR0NNKQ0KPGEgaHJlZj0iaHR0cDovL3Nl
bGYtaXNzdWVkLmluZm8vZG9jcy9kcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAtMDAu
aHRtbCNBRVMiPg0KW0FFU108L2E+IDxhIGhyZWY9Imh0dHA6Ly9zZWxmLWlzc3VlZC5pbmZvL2Rv
Y3MvZHJhZnQtam9uZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwLTAwLmh0bWwjTklTVC44MDAtMzhE
Ij4NCltOSVNULjgwMOKAkTM4RF08L2E+IHVzaW5nIDEyOCBvciAyNTYgYml0IGtleXMuIFRoZSA8
L3NwYW4+PHR0PjxzcGFuIGxhbmc9IkVOIj5hbGc8L3NwYW4+PC90dD48c3BhbiBsYW5nPSJFTiIg
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjpibGFjayI+IGhlYWRlciBwYXJhbWV0ZXIgdmFsdWVzDQo8L3NwYW4+PHR0Pjxz
cGFuIGxhbmc9IkVOIj5BMTI4R0NNS1c8L3NwYW4+PC90dD48c3BhbiBsYW5nPSJFTiIgc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjpibGFjayI+IG9yDQo8L3NwYW4+PHR0PjxzcGFuIGxhbmc9IkVOIj5BMjU2R0NNS1c8L3Nw
YW4+PC90dD48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+IGFyZSByZXNwZWN0aXZl
bHkgdXNlZCBpbiB0aGlzIGNhc2UuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBs
YW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+VXNlIG9mIGFuIEluaXRpYWxpemF0aW9uIFZlY3Rv
ciBvZiBzaXplIDk2IGJpdHMgaXMgUkVRVUlSRUQgd2l0aCB0aGlzIGFsZ29yaXRobS4NCjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5U
aGUgQWRkaXRpb25hbCBBdXRoZW50aWNhdGVkIERhdGEgdmFsdWUgdXNlZCBpcyB0aGUgZW1wdHkg
b2N0ZXQgc3RyaW5nLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4i
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6YmxhY2siPlRoZSByZXF1ZXN0ZWQgc2l6ZSBvZiB0aGUgQXV0aGVudGljYXRp
b24gVGFnIG91dHB1dCBNVVNUIGJlIDEyOCBiaXRzLCByZWdhcmRsZXNzIG9mIHRoZSBrZXkgc2l6
ZS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OmJsYWNrIj5MZXQgSldFIEVuY3J5cHRlZCBLZXkgdmFsdWUgYmUgdGhlIGNvbmNhdGVuYXRpb24g
b2YgdGhlIEluaXRpYWxpemF0aW9uIFZlY3RvciB2YWx1ZSwgdGhlIENpcGhlcnRleHQgb3V0cHV0
LCBhbmQgdGhlIEF1dGhlbnRpY2F0aW9uIFRhZyBvdXRwdXQuDQo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cD48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+RHVyaW5nIGtleSBkZWNy
eXB0aW9uLCB0aGUgSldFIEVuY3J5cHRlZCBLZXkgdmFsdWUgaXMgc3BsaXQgaW50byB0aHJlZSBp
bnB1dHMgdG8gdGhlIEFFUyBHQ00gZGVjcnlwdGlvbiBhbGdvcml0aG06IHRoZSBmaXJzdCA5NiBi
aXRzIGFyZSB0aGUgSW5pdGlhbGl6YXRpb24gVmVjdG9yIHZhbHVlLCB0aGUgbGFzdCAxMjgNCiBi
aXRzIGFyZSB0aGUgQXV0aGVudGljYXRpb24gVGFnIHZhbHVlLCBhbmQgdGhlIHJlbWFpbmluZyBi
aXRzIGluIGJldHdlZW4gYXJlIHRoZSBDaXBoZXJ0ZXh0IHZhbHVlLg0KPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0t
IE1pa2U8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+UC5TLiZuYnNwOyBSaWNoYXJkLCB1
bmxpa2Ugd2hhdCBJIGRlc2NyaWJlZCBpbiBvdXIgcHJpdmF0ZSBjb252ZXJzYXRpb24sIHRoaXMg
c3BlY2lmaWNhdGlvbiB1c2VzIG5vIGFkZGl0aW9uYWwgaGVhZGVyIHBhcmFtZXRlciB2YWx1ZXMu
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
PGJyPg0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnXSA8YnI+DQpTZW50OiBUaHVyc2RheSwgSnVuZSAxMywgMjAxMyA1OjUzIFBN
PGJyPg0KVG86IE1pa2UgSm9uZXM7IE1pa2UgSm9uZXM8YnI+DQpTdWJqZWN0OiBOZXcgVmVyc2lv
biBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXktd3JhcC0wMC50
eHQ8L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1qb25lcy1q
b3NlLWFlcy1nY20ta2V5LXdyYXAtMDAudHh0PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij5oYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE1pY2hhZWwgQi4g
Sm9uZXMgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5LjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij5GaWxlbmFtZTombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZHJhZnQtam9uZXMtam9zZS1hZXMtZ2Nt
LWtleS13cmFwPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5SZXZpc2lv
bjombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgMDA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPlRpdGxlOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBLZXkgV3JhcHBpbmcgd2l0aCBBRVMgR0NNIGZv
ciBKV0U8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkNyZWF0aW9uIGRh
dGU6Jm5ic3A7Jm5ic3A7IDIwMTMtMDYtMTM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPkdyb3VwOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBJbmRpdmlkdWFsIFN1Ym1pc3Npb248bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPk51bWJlciBvZiBwYWdlczogNTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+VVJMOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8YSBocmVmPSJodHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAtMDAu
dHh0Ij4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25l
Ij5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qb25lcy1qb3NlLWFl
cy1nY20ta2V5LXdyYXAtMDAudHh0PC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPlN0YXR1czombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAiPg0KPHNwYW4gc3R5bGU9ImNv
bG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtam9uZXMtam9zZS1hZXMtZ2NtLWtleS13cmFwPC9zcGFuPjwvYT48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkh0bWxpemVkOiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8YSBocmVmPSJodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9kcmFmdC1qb25lcy1qb3NlLWFlcy1nY20ta2V5LXdyYXAtMDAiPg0KPHNw
YW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHA6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpvbmVzLWpvc2UtYWVzLWdjbS1rZXktd3JhcC0wMDwv
c3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkFic3RyYWN0OjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IFRoaXMgc3BlY2lm
aWNhdGlvbiBkZWZpbmVzIGhvdyB0byBlbmNyeXB0ICh3cmFwKSBrZXlzIHdpdGggdGhlIEFFUzxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7IEdDTSBh
bGdvcml0aG0gZm9yIEpTT04gV2ViIEVuY3J5cHRpb24gKEpXRSkgb2JqZWN0cy48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+VGhlIElFVEYgU2VjcmV0YXJpYXQ8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_4E1F6AAD24975D4BA5B1680429673943678538F7TK5EX14MBXC283r_--

From housley@vigilsec.com  Fri Jun 14 09:58:47 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC01121F9CE8 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 09:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.824
X-Spam-Level: 
X-Spam-Status: No, score=-101.824 tagged_above=-999 required=5 tests=[AWL=-0.622, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cr+ARm1pnaeY for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 09:58:43 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id BB4B621F9CDD for <jose@ietf.org>; Fri, 14 Jun 2013 09:58:42 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4881AF24078; Fri, 14 Jun 2013 12:58:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id ihgxFSEfpYHk; Fri, 14 Jun 2013 12:58:12 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 01056F24072; Fri, 14 Jun 2013 12:58:55 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-88--67587232
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678538F7@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 14 Jun 2013 12:58:40 -0400
Message-Id: <C61E6C8A-4226-475F-9051-B1759CA63B90@vigilsec.com>
References: <4E1F6AAD24975D4BA5B1680429673943678538F7@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1085)
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] AES GCM Key Wrapping Draft
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 16:58:47 -0000

--Apple-Mail-88--67587232
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I would greatly prefer a document that describe the key wrap algorithm =
as a series of steps (both wrap and unwarp), and then defined the =
identifiers needed to use this algorithm with JOSE and CMS,  The current =
document makes it see that the algorithm is only appropriate for JOSE.

At a minimum, the security consideration need to talk about:
- protection of the key-encryption key, and the consequences if it is =
not.
- generation of the key-encryption key, unless you choose to add that to =
the body of the document.

Implementers will greatly appreciate test vectors.

Russ


On Jun 13, 2013, at 9:04 PM, Mike Jones wrote:

> An action item I took on at the interim working group meeting was to =
produce a draft showing how key wrapping can be accomplished with AES =
GCM for JWE.  This draft is now available as =
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00.  The =
specification is also available in HTML format at =
http://self-issued.info/docs/draft-jones-jose-aes-gcm-key-wrap-00.html.
> =20
> The core technical content is all in Section 3, which I=E2=80=99ve =
included in its entirety below because it=E2=80=99s so short.
> =20
> 3.  Key Encryption with AES GCM
>=20
> This section defines the specifics of encrypting a JWE Content =
Encryption Key (CEK) with Advanced Encryption Standard (AES) in =
Galois/Counter Mode (GCM) [AES] [NIST.800=E2=80=9138D] using 128 or 256 =
bit keys. The alg header parameter values A128GCMKW orA256GCMKW are =
respectively used in this case.
>=20
> Use of an Initialization Vector of size 96 bits is REQUIRED with this =
algorithm.
>=20
> The Additional Authenticated Data value used is the empty octet =
string.
>=20
> The requested size of the Authentication Tag output MUST be 128 bits, =
regardless of the key size.
>=20
> Let JWE Encrypted Key value be the concatenation of the Initialization =
Vector value, the Ciphertext output, and the Authentication Tag output.
>=20
> During key decryption, the JWE Encrypted Key value is split into three =
inputs to the AES GCM decryption algorithm: the first 96 bits are the =
Initialization Vector value, the last 128 bits are the Authentication =
Tag value, and the remaining bits in between are the Ciphertext value.
>=20
> =20
>                                                                 -- =
Mike
> =20
> P.S.  Richard, unlike what I described in our private conversation, =
this specification uses no additional header parameter values.
> =20
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
> Sent: Thursday, June 13, 2013 5:53 PM
> To: Mike Jones; Mike Jones
> Subject: New Version Notification for =
draft-jones-jose-aes-gcm-key-wrap-00.txt
> =20
> A new version of I-D, draft-jones-jose-aes-gcm-key-wrap-00.txt
> has been successfully submitted by Michael B. Jones and posted to the =
IETF repository.
> =20
> Filename:            draft-jones-jose-aes-gcm-key-wrap
> Revision:              00
> Title:                      Key Wrapping with AES GCM for JWE
> Creation date:   2013-06-13
> Group:                  Individual Submission
> Number of pages: 5
> URL:             =
http://www.ietf.org/internet-drafts/draft-jones-jose-aes-gcm-key-wrap-00.t=
xt
> Status:          =
http://datatracker.ietf.org/doc/draft-jones-jose-aes-gcm-key-wrap
> Htmlized:        =
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00
> =20
> Abstract:
>    This specification defines how to encrypt (wrap) keys with the AES
>    GCM algorithm for JSON Web Encryption (JWE) objects.
> =20
> The IETF Secretariat
> =20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail-88--67587232
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
would greatly prefer a document that describe the key wrap algorithm as =
a series of steps (both wrap and unwarp), and then defined the =
identifiers needed to use this algorithm with JOSE and CMS, &nbsp;The =
current document makes it see that the algorithm is only appropriate for =
JOSE.<div><br></div><div><div>At a minimum, the security consideration =
need to talk about:</div><div>- protection of the key-encryption key, =
and the consequences if it is not.</div><div>- generation of =
the&nbsp;key-encryption key, unless you choose to add that to the body =
of the document.</div><div><br></div><div><div>Implementers will greatly =
appreciate test =
vectors.</div></div><div><br></div><div>Russ</div><div><br></div><div><br>=
<div><div>On Jun 13, 2013, at 9:04 PM, Mike Jones wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; ">An action item I took on at =
the interim working group meeting was to produce a draft showing how key =
wrapping can be accomplished with AES GCM for JWE.&nbsp; This draft is =
now available as<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00" =
style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a>. =
&nbsp;The specification is also available in HTML format at<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://self-issued.info/docs/draft-jones-jose-aes-gcm-key-wrap-00.=
html" style=3D"color: blue; text-decoration: underline; =
">http://self-issued.info/docs/draft-jones-jose-aes-gcm-key-wrap-00.html</=
a>.<o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; ">The core technical content is all in Section 3, which I=E2=80=99=
ve included in its entirety below because it=E2=80=99s so =
short.<o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: =
0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; "><o:p>&nbsp;</o:p></div><h3 =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 13.5pt; =
font-family: Helvetica, sans-serif; color: rgb(51, 51, 51); font-weight: =
bold; "><span lang=3D"EN">3.&nbsp; Key Encryption with AES =
GCM<o:p></o:p></span></h3><p style=3D"margin-right: 24pt; margin-left: =
24pt; font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
lang=3D"EN" style=3D"font-family: Verdana, sans-serif; color: black; =
">This section defines the specifics of encrypting a JWE Content =
Encryption Key (CEK) with Advanced Encryption Standard (AES) in =
Galois/Counter Mode (GCM)<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://self-issued.info/docs/draft-jones-jose-aes-gcm-key-wrap-00.=
html#AES" style=3D"color: blue; text-decoration: underline; =
">[AES]</a><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://self-issued.info/docs/draft-jones-jose-aes-gcm-key-wrap-00.=
html#NIST.800-38D" style=3D"color: blue; text-decoration: underline; =
">[NIST.800=E2=80=9138D]</a><span =
class=3D"Apple-converted-space">&nbsp;</span>using 128 or 256 bit keys. =
The<span class=3D"Apple-converted-space">&nbsp;</span></span><tt =
style=3D"font-family: 'Courier New'; color: rgb(0, 51, 102); "><span =
lang=3D"EN">alg</span></tt><span lang=3D"EN" style=3D"font-family: =
Verdana, sans-serif; color: black; "><span =
class=3D"Apple-converted-space">&nbsp;</span>header parameter =
values<span class=3D"Apple-converted-space">&nbsp;</span></span><tt =
style=3D"font-family: 'Courier New'; color: rgb(0, 51, 102); "><span =
lang=3D"EN">A128GCMKW</span></tt><span lang=3D"EN" style=3D"font-family: =
Verdana, sans-serif; color: black; "><span =
class=3D"Apple-converted-space">&nbsp;</span>or</span><tt =
style=3D"font-family: 'Courier New'; color: rgb(0, 51, 102); "><span =
lang=3D"EN">A256GCMKW</span></tt><span lang=3D"EN" style=3D"font-family: =
Verdana, sans-serif; color: black; "><span =
class=3D"Apple-converted-space">&nbsp;</span>are respectively used in =
this case.<o:p></o:p></span></p><p style=3D"margin-right: 24pt; =
margin-left: 24pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span lang=3D"EN" style=3D"font-family: Verdana, sans-serif; =
color: black; ">Use of an Initialization Vector of size 96 bits is =
REQUIRED with this algorithm.<o:p></o:p></span></p><p =
style=3D"margin-right: 24pt; margin-left: 24pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span lang=3D"EN" =
style=3D"font-family: Verdana, sans-serif; color: black; ">The =
Additional Authenticated Data value used is the empty octet =
string.<o:p></o:p></span></p><p style=3D"margin-right: 24pt; =
margin-left: 24pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span lang=3D"EN" style=3D"font-family: Verdana, sans-serif; =
color: black; ">The requested size of the Authentication Tag output MUST =
be 128 bits, regardless of the key size.<o:p></o:p></span></p><p =
style=3D"margin-right: 24pt; margin-left: 24pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span lang=3D"EN" =
style=3D"font-family: Verdana, sans-serif; color: black; ">Let JWE =
Encrypted Key value be the concatenation of the Initialization Vector =
value, the Ciphertext output, and the Authentication Tag =
output.<o:p></o:p></span></p><p style=3D"margin-right: 24pt; =
margin-left: 24pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span lang=3D"EN" style=3D"font-family: Verdana, sans-serif; =
color: black; ">During key decryption, the JWE Encrypted Key value is =
split into three inputs to the AES GCM decryption algorithm: the first =
96 bits are the Initialization Vector value, the last 128 bits are the =
Authentication Tag value, and the remaining bits in between are the =
Ciphertext value.<o:p></o:p></span></p><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; "><o:p>&nbsp;</o:p></div><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; ">P.S.&nbsp; Richard, unlike =
what I described in our private conversation, this specification uses no =
additional header parameter values.<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; "><o:p>&nbsp;</o:p></div><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; ">-----Original =
Message-----<br>From:<span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:internet-drafts@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">internet-drafts@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:internet-drafts@ietf.=
org]<span class=3D"Apple-converted-space">&nbsp;</span><br>Sent: =
Thursday, June 13, 2013 5:53 PM<br>To: Mike Jones; Mike =
Jones<br>Subject: New Version Notification for =
draft-jones-jose-aes-gcm-key-wrap-00.txt</div><div style=3D"margin-right: =
0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-right: 0in; margin-left: =
0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; ">A new version of I-D, =
draft-jones-jose-aes-gcm-key-wrap-00.txt<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; ">has been successfully submitted by Michael B. Jones and =
posted to the IETF repository.<o:p></o:p></div><div style=3D"margin-right:=
 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-right: 0in; margin-left: =
0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; =
">Filename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; draft-jones-jose-aes-gcm-key-wrap<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; =
">Revision:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; 00<o:p></o:p></div><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; =
">Title:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Key =
Wrapping with AES GCM for JWE<o:p></o:p></div><div style=3D"margin-right: =
0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; ">Creation =
date:&nbsp;&nbsp; 2013-06-13<o:p></o:p></div><div style=3D"margin-right: =
0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; =
">Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individual =
Submission<o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: =
0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; ">Number of pages: 5<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; =
">URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/internet-drafts/draft-jones-jose-aes-gcm-key-w=
rap-00.txt" style=3D"color: blue; text-decoration: underline; "><span =
style=3D"color: windowtext; text-decoration: none; =
">http://www.ietf.org/internet-drafts/draft-jones-jose-aes-gcm-key-wrap-00=
.txt</span></a><o:p></o:p></div><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; =
">Status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://datatracker.ietf.org/doc/draft-jones-jose-aes-gcm-key-wrap"=
 style=3D"color: blue; text-decoration: underline; "><span style=3D"color:=
 windowtext; text-decoration: none; =
">http://datatracker.ietf.org/doc/draft-jones-jose-aes-gcm-key-wrap</span>=
</a><o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; =
">Htmlized:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00" =
style=3D"color: blue; text-decoration: underline; "><span style=3D"color: =
windowtext; text-decoration: none; =
">http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</span></=
a><o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; ">Abstract:<o:p></o:p></div><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; =
margin-top: 0in; margin-bottom: 0.0001pt; ">&nbsp;&nbsp; This =
specification defines how to encrypt (wrap) keys with the =
AES<o:p></o:p></div><div style=3D"margin-right: 0in; margin-left: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; ">&nbsp;&nbsp; GCM algorithm for JSON Web =
Encryption (JWE) objects.<o:p></o:p></div><div style=3D"margin-right: =
0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-right: 0in; margin-left: =
0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; =
margin-bottom: 0.0001pt; ">The IETF Secretariat<o:p></o:p></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: =
0.0001pt; =
"><o:p>&nbsp;</o:p></div></div>___________________________________________=
____<br>jose mailing list<br><a href=3D"mailto:jose@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">jose@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/jose</a><br></div></blockquote></d=
iv><br></div></div></body></html>=

--Apple-Mail-88--67587232--

From hallam@gmail.com  Fri Jun 14 14:49:10 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA4121F99ED for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOOTS0lcP6w0 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:49:08 -0700 (PDT)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 688CF21F99FA for <jose@ietf.org>; Fri, 14 Jun 2013 14:49:04 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id e11so929842wgh.30 for <jose@ietf.org>; Fri, 14 Jun 2013 14:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; bh=8jPHzF6PrsFIyYTIMM0ECuAw6YQvDvCv20XMaQkka0g=; b=NGqOonEl04C95hDJ+PYwb7VbZiBnr2wmdOJy4q/LR3HE/ybb4/i1z0dHsMTv45TNEV 6qdYrDt59YbBYknN/IA2/iGszK1pVURq4VICELlukl9k5GLrWfEk/M80+T4q9VEg2DHH spNk92NQuxTu2xVXuH+21563ukpabeM6+MhUCSXFGyoB/vDATPuywchiYCR4ZaOZZl1J DahgQlkupj3qQCUewkJH82klMm568lUiUEexAMNgaUO6g7RryoRTs8GM0F4e/Qbj35Eq Iwbmoz/rDL2tU0QtEYw0qLPjzNelquV7F1vhXt65WC2yKUCfDTs27JZdjb2PbAJqZhTB 7WBQ==
X-Received: by 10.194.104.74 with SMTP id gc10mr2553493wjb.48.1371246538793; Fri, 14 Jun 2013 14:48:58 -0700 (PDT)
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com>
In-Reply-To: <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com>
Mime-Version: 1.0 (1.0)
From: Phillip Hallam-Baker <hallam@gmail.com>
Date: Fri, 14 Jun 2013 17:48:56 -0400
Message-ID: <7188842785648960750@unknownmsgid>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=047d7bf10b46d82ab304df243683
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 21:49:10 -0000

--047d7bf10b46d82ab304df243683
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I think in this case that it is late to bring up binary encoding in Jose

But that does not mean we can't add it later. Specs have revisions. All
that is needed to support binary is a flag to say what was signed. Defaults
to the current scheme.

Now if it was a case where binary had been raised at the start of the
process and the person got told to shut up because of 'focus' well that
would be different. When people pull that trick I have no qualms about
repeating my concerns in IETF last call. I think that all too often there
is too much haste when starting a WG and people get railroaded into a
broken scheme some faction likes. But that did not happen here so I think
it is going to be for the binary camp to work out the solution.

My bigger Jose concern is the bizarre decision to rename all the crypto alg
names. I have a spec that uses mime and JSON. If I take Jose seriously I
need a second crypto alg registry.

That is junk, that is something that was raised at the start of the
process. So yes, I will make it an issue in IETF last call

Sent from my difference engine


On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

Seems like many these days are in a rush. They call for consensus before
discussing the issue.

Isn't it up to the chair?

This isn't unique to this WG.

Too many times the explanation for keeping an apparent 'feature/flaw' is
'because we don't want change'. Yet often the group can't explain it. Or
worse, the group just says "we know the emperor has no clothes, we just
don't feel the need to comment." This is where alarm bells go off for me.

Phil

On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx> wrote:

This would have been a nice discussion to have had 18 months ago, when we
were getting started.

I don't think it's compatible with the IETF ethos to say "Changes to this
document MUST NOT break existing code."  Otherwise, we're not doing
engineering here, we're cleaning up documentation and rubber-stamping.

What would be acceptable is to say "Changes must break cleanly with
existing code".  That is, it should be possible for a JWT implementation
to, say, process both "legacy" JWS syntax and whatever comes out of this
group.  That way, we could come to consensus on the best solution,
incorporating lessons learned from earlier work without being hindered by
them.

Would participants here consider it a acceptable for the output of this
working group to be incompatible with existing JWT implementations, as long
as it had the property that JW* objects in the new format could be clearly
distinguished from "legacy" JW* objects, so that implementations could
adapt their processing?

--Richard




On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com> wrote:

>  +1
>
> Breaking deployed code as raised by Brian, Naveen and others is a critica=
l
> consideration.
>
> Thanks,
> George
>
>  On 6/13/13 10:19 AM, Mike Jones wrote:
>
>  Jim and Karen, could you please do as Richard suggests and close this
> issue as =93won=92t fix=94.****
>
> ** **
>
>                                                             Thank you,***=
*
>
>                                                             -- Mike****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Wednesday, June 12, 2013 1:57 PM
> *To:* jose-chairs@tools.ietf.org; Mike Jones
> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
> (base64)****
>
> ** **
>
> In other words: Chairs, feel free to close/wontfix :)****
>
> ** **
>
> ---------- Forwarded message ----------
> From: *Richard Barnes* <rlb@ipv.sx>
> Date: Wed, Jun 12, 2013 at 4:55 PM
> Subject: Re: [jose] #23: Make crypto independent of binary encoding
> (base64)
> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
> jose@ietf.org>" <jose@ietf.org>
>
> ****
>
> To be clear, I structured my message in two parts for a reason, to
> separate the analysis from the opinion.  I acknowledge that I am but one
> voice here, and I'm increasingly hearing how alone I am :)****
>
> ** **
>
> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:****
>
>  <impartial-analysis>****
>
> So just to be clear on the trade-off the WG has to make:****
>
> ** **
>
> On the one hand: Breaking every existing JWT implementation in the world*=
*
> **
>
> On the other hand: Eternally binding ourselves to base64 encoding, even i=
f
> binary-safe encodings become available (CBOR, MsgPack, etc.)****
>
> </impartial-analysis >****
>
> ** **
>
> <personal-opinion>****
>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."****
>
> ** **
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base=
64
> is a hack around JSON; we should build the system so that when we no long=
er
> need that hack, it can go away.****
>
> </personal-opinion>****
>
> ** **
>
> --Richard****
>
> ** **
>
> ** **
>
> ** **
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:****
>
> I did at first find it curious why the cryptographic operations were over
> the base64url-enccoded values, but I was also very focused on JWE, where =
I
> think the field separation problem is less of an issue (at least now).  F=
or
> JWS, this would certainly cause problems without some manner of unambiguo=
us
> field parameterization.
>
> I will note that unescaped NULL is not valid in JSON, so it could be used
> as a separator between the encoded header and the payload.  I do find it
> interesting if JOSE could more easily and efficiently support other
> encodings.  However, I think that while this is an interesting thought
> experiment, it seems we're too far down the path to seriously consider it
> unless the current state were shown to be horribly broken.
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.****
>
>
> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
> trac+jose@trac.tools.ietf.org> wrote:
>
> > #23: Make crypto independent of binary encoding (base64)
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> > For both serializations, you already need the base64url encoded version=
s
> > of the JWS Header and the JWS Payload to preserve them in transmission,
> so
> > computing them isn't an extra burden.  In the JWS Compact Serialization=
,
> > you already need the concatenation of the Encoded JWS Header, a period
> > character, and the Encoded JWS Payload, so computing that concatenation
> > isn't an extra burden.  Given you already have that quantity, computing
> > the signature over it is the easiest thing for developers to do, and it=
's
> > been shown to work well in practice.  There's no compelling reason to
> make
> > this change.
> >
> > Even for the JSON Serialization, the only "extra" step that's required =
to
> > compute the signature is the concatenation with the period character - =
to
> > prevent shifting of data from one field to the other, as described by J=
im
> > Schaad in the e-mail thread.  So this step isn't actually "extra" at al=
l
> -
> > it's necessary.  It's also highly advantageous to use exactly the same
> > computation for both serializations, which is currently the case.
> >
> > Since there is no compelling reason to make this change, and since maki=
ng
> > it could enable the "shifting" problem identified by Jim, it should not
> be
> > made.
> >
> > --
> >
> -------------------------+-----------------------------------------------=
--
> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
> >     Type:  defect       |  encryption@tools.ietf.org
> > Priority:  major        |      Status:  new
> > Component:  json-web-    |   Milestone:
> >  encryption             |     Version:
> > Severity:  -            |  Resolution:
> > Keywords:               |
> >
> -------------------------+-----------------------------------------------=
--
> >
> > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:=
2
> >
> > jose <http://tools.ietf.org/jose/>
> >****
>
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>
>   ** **
>
> ** **
>
>
> _______________________________________________
> jose mailing listjose@ietf.orghttps://www.ietf.org/mailman/listinfo/jose
>
>
> --
> <XeC> <http://connect.me/gffletch>
>

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

--047d7bf10b46d82ab304df243683
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=
=3Dutf-8"></head><body dir=3D"auto"><div>I think in this case that it is la=
te to bring up binary encoding in Jose</div><div><br></div><div>But that do=
es not mean we can&#39;t add it later. Specs have revisions. All that is ne=
eded to support binary is a flag to say what was signed. Defaults to the cu=
rrent scheme.</div>
<div><br></div><div>Now if it was a case where binary had been raised at th=
e start of the process and the person got told to shut up because of &#39;f=
ocus&#39; well that would be different. When people pull that trick I have =
no qualms about repeating my concerns in IETF last call. I think that all t=
oo often there is too much haste when starting a WG and people get railroad=
ed into a broken scheme some faction likes. But that did not happen here so=
 I think it is going to be for the binary camp to work out the solution.=A0=
</div>
<div><br></div><div>My bigger Jose concern is the bizarre decision to renam=
e all the crypto alg names. I have a spec that uses mime and JSON. If I tak=
e Jose seriously I need a second crypto alg registry.=A0</div><div><br></di=
v>
<div>That is junk, that is something that was raised at the start of the pr=
ocess. So yes, I will make it an issue in IETF last call<br><br>Sent from m=
y difference engine<div><br></div></div><div><br>On Jun 13, 2013, at 12:06 =
PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@oracle.com">phil.hunt@oracle.=
com</a>&gt; wrote:<br>
<br></div><blockquote type=3D"cite"><div><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"><div>Seems like many these days are =
in a rush. They call for consensus before discussing the issue.=A0</div><di=
v><br>
</div><div>Isn&#39;t it up to the chair?</div><div><br></div><div>This isn&=
#39;t unique to this WG.=A0</div><div><br></div><div>Too many times the exp=
lanation for keeping an apparent &#39;feature/flaw&#39; is &#39;because we =
don&#39;t want change&#39;. Yet often the group can&#39;t explain it. Or wo=
rse, the group just says &quot;we know the emperor has no clothes, we just =
don&#39;t feel the need to comment.&quot; This is where alarm bells go off =
for me.=A0<br>
<br>Phil</div><div><br>On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=
=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt; wrote:<br><br></div><blockquote t=
ype=3D"cite"><div><div dir=3D"ltr">This would have been a nice discussion t=
o have had 18 months ago, when we were getting started.<div>
<br></div><div>I don&#39;t think it&#39;s compatible with the IETF ethos to=
 say &quot;Changes to this document MUST NOT break existing code.&quot; =A0=
Otherwise, we&#39;re not doing engineering here, we&#39;re cleaning up docu=
mentation and rubber-stamping.</div>

<div><br></div><div>What would be acceptable is to say &quot;Changes must b=
reak cleanly with existing code&quot;. =A0That is, it should be possible fo=
r a JWT implementation to, say, process both &quot;legacy&quot; JWS syntax =
and whatever comes out of this group. =A0That way, we could come to consens=
us on the best solution, incorporating lessons learned from earlier work wi=
thout being hindered by them.</div>

<div><br></div><div>Would participants here consider it a acceptable for th=
e output of this working group to be incompatible with existing JWT impleme=
ntations, as long as it had the property that JW* objects in the new format=
 could be clearly distinguished from &quot;legacy&quot; JW* objects, so tha=
t implementations could adapt their processing?</div>

<div><br></div><div>--Richard</div><div><br></div><div><br><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 13, 2013 at 10:24=
 AM, George Fletcher <span dir=3D"ltr">&lt;<a href=3D"mailto:gffletch@aol.c=
om" target=3D"_blank">gffletch@aol.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Helvetica, Arial, sans-serif">+1<br>
      <br>
      Breaking deployed code as raised by Brian, Naveen and others is a
      critical consideration.<br>
      <br>
      Thanks,<br>
      George<br>
      <br>
    </font><div><div class=3D"h5">
    <div>On 6/13/13 10:19 AM, Mike Jones wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
     =20
     =20
      <div>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim
            and Karen, could you please do as Richard suggests and close
            this issue as =93won=92t fix=94.<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u>=
</span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0
            Thank you,<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0
            -- Mike<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u>=
</span></p>
        <p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=
=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"=
>
            Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank"=
>mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
            <b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=
=3D"_blank">jose-chairs@tools.ietf.org</a>; Mike Jones<br>
            <b>Subject:</b> Fwd: [jose] #23: Make crypto independent of
            binary encoding (base64)<u></u><u></u></span></p>
        <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
        <div>
          <p class=3D"MsoNormal">In other words: Chairs, feel free to
            close/wontfix :)<u></u><u></u></p>
          <div>
            <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=
=A0<u></u></p>
            <div>
              <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">-------=
---
                Forwarded message ----------<br>
                From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.s=
x" target=3D"_blank">rlb@ipv.sx</a>&gt;<br>
                Date: Wed, Jun 12, 2013 at 4:55 PM<br>
                Subject: Re: [jose] #23: Make crypto independent of
                binary encoding (base64)<br>
                To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailt=
o:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
                Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@tr=
ac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;,
                &quot;&lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@=
tools.ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@t=
ools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.=
ietf.org</a>&gt;,

                &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" ta=
rget=3D"_blank">michael.jones@microsoft.com</a>&gt;&quot;
                &lt;<a href=3D"mailto:michael.jones@microsoft.com" target=
=3D"_blank">michael.jones@microsoft.com</a>&gt;,
                &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank=
">jose@ietf.org</a>&gt;&quot;
                &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose=
@ietf.org</a>&gt;<br>
                <br>
                <u></u><u></u></p>
              <div>
                <p class=3D"MsoNormal">To be clear, I structured my
                  message in two parts for a reason, to separate the
                  analysis from the opinion. =A0I acknowledge that I am
                  but one voice here, and I&#39;m increasingly hearing how
                  alone I am :)<u></u><u></u></p>
              </div>
              <div>
                <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></=
u>=A0<u></u></p>
                <div>
                  <div>
                    <p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23
                      PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>&gt;
                      wrote:<u></u><u></u></p>
                  </div>
                  <div>
                    <div>
                      <blockquote style=3D"border:none;border-left:solid #c=
ccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class=3D"MsoNormal">&lt;impartial-analysis&g=
t;<u></u><u></u></p>
                          </div>
                          <p class=3D"MsoNormal">So just to be clear on
                            the trade-off the WG has to make:<u></u><u></u>=
</p>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the one hand:
                              Breaking every existing JWT implementation
                              in the world<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">On the other hand:
                              Eternally binding ourselves to base64
                              encoding, even if binary-safe encodings
                              become available (CBOR, MsgPack, etc.)<u></u>=
<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/impartial-analysis=
=A0&gt;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;personal-opinion&gt;=
<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">I have some sympathy
                              with JWT implementors. =A0It sucks to have
                              to refactor code. =A0But I think we&#39;re
                              literally talking about something like a
                              5-line patch. =A0And early JWT implementors
                              knew or should have known (to use a DC
                              phrase) that they were dealing with a
                              draft spec. =A0As the W3C editor&#39;s draft
                              template says, in big bold red print,
                              &quot;Implementors who are not taking part in
                              the discussions are likely to find the
                              specification changing out from under them
                              in incompatible ways.&quot;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">As PHB pointed out in
                              the other thread, it would be nice to use
                              JWS and JWE in place of CMS one day,
                              without the base64 hit. =A0We should incur
                              the implementation pain now, and get the
                              design right for the long run. =A0Base64 is
                              a hack around JSON; we should build the
                              system so that when we no longer need that
                              hack, it can go away.<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal">&lt;/personal-opinion&gt=
;<u></u><u></u></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888">--Richard<u></u><u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                          <div>
                            <p class=3D"MsoNormal"><span style=3D"color:#88=
8888"><u></u>=A0<u></u></span></p>
                          </div>
                        </div>
                        <div>
                          <div>
                            <div>
                              <p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><u></u>=A0<u></u></p>
                              <div>
                                <p class=3D"MsoNormal">On Wed, Jun 12,
                                  2013 at 10:27 AM, Matt Miller
                                  (mamille2) &lt;<a href=3D"mailto:mamille2=
@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&gt;
                                  wrote:<u></u><u></u></p>
                                <p class=3D"MsoNormal">I did at first find
                                  it curious why the cryptographic
                                  operations were over the
                                  base64url-enccoded values, but I was
                                  also very focused on JWE, where I
                                  think the field separation problem is
                                  less of an issue (at least now). =A0For
                                  JWS, this would certainly cause
                                  problems without some manner of
                                  unambiguous field parameterization.<br>
                                  <br>
                                  I will note that unescaped NULL is not
                                  valid in JSON, so it could be used as
                                  a separator between the encoded header
                                  and the payload. =A0I do find it
                                  interesting if JOSE could more easily
                                  and efficiently support other
                                  encodings. =A0However, I think that
                                  while this is an interesting thought
                                  experiment, it seems we&#39;re too far
                                  down the path to seriously consider it
                                  unless the current state were shown to
                                  be horribly broken.<br>
                                  <br>
                                  <br>
                                  - m&amp;m<br>
                                  <br>
                                  Matt Miller &lt; <a href=3D"mailto:mamill=
e2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>
                                  &gt;<br>
                                  Cisco Systems, Inc.<u></u><u></u></p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal"><br>
                                      On Jun 11, 2013, at 6:01 PM, jose
                                      issue tracker &lt;<a href=3D"mailto:t=
rac%2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf=
.org</a>&gt;
                                      wrote:<br>
                                      <br>
                                      &gt; #23: Make crypto independent
                                      of binary encoding (base64)<br>
                                      &gt;<br>
                                      &gt;<br>
                                      &gt; Comment (by <a href=3D"mailto:mi=
chael.jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a=
>):<br>
                                      &gt;<br>
                                      &gt; For both serializations, you
                                      already need the base64url encoded
                                      versions<br>
                                      &gt; of the JWS Header and the JWS
                                      Payload to preserve them in
                                      transmission, so<br>
                                      &gt; computing them isn&#39;t an extr=
a
                                      burden. =A0In the JWS Compact
                                      Serialization,<br>
                                      &gt; you already need the
                                      concatenation of the Encoded JWS
                                      Header, a period<br>
                                      &gt; character, and the Encoded
                                      JWS Payload, so computing that
                                      concatenation<br>
                                      &gt; isn&#39;t an extra burden. =A0Gi=
ven
                                      you already have that quantity,
                                      computing<br>
                                      &gt; the signature over it is the
                                      easiest thing for developers to
                                      do, and it&#39;s<br>
                                      &gt; been shown to work well in
                                      practice. =A0There&#39;s no compellin=
g
                                      reason to make<br>
                                      &gt; this change.<br>
                                      &gt;<br>
                                      &gt; Even for the JSON
                                      Serialization, the only &quot;extra&q=
uot;
                                      step that&#39;s required to<br>
                                      &gt; compute the signature is the
                                      concatenation with the period
                                      character - to<br>
                                      &gt; prevent shifting of data from
                                      one field to the other, as
                                      described by Jim<br>
                                      &gt; Schaad in the e-mail thread.
                                      =A0So this step isn&#39;t actually
                                      &quot;extra&quot; at all -<br>
                                      &gt; it&#39;s necessary. =A0It&#39;s =
also
                                      highly advantageous to use exactly
                                      the same<br>
                                      &gt; computation for both
                                      serializations, which is currently
                                      the case.<br>
                                      &gt;<br>
                                      &gt; Since there is no compelling
                                      reason to make this change, and
                                      since making<br>
                                      &gt; it could enable the
                                      &quot;shifting&quot; problem identifi=
ed by
                                      Jim, it should not be<br>
                                      &gt; made.<br>
                                      &gt;<br>
                                      &gt; --<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt; Reporter: =A0<a href=3D"mailto:r=
lb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>
                                      =A0 | =A0 =A0 =A0 Owner:
                                      =A0draft-ietf-jose-json-web-<br>
                                      &gt; =A0 =A0 Type: =A0defect =A0 =A0 =
=A0 | =A0<a href=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">enc=
ryption@tools.ietf.org</a><br>
                                      &gt; Priority: =A0major =A0 =A0 =A0 =
=A0| =A0 =A0
                                      =A0Status: =A0new<br>
                                      &gt; Component: =A0json-web- =A0 =A0|=
 =A0
                                      Milestone:<br>
                                      &gt; =A0encryption =A0 =A0 =A0 =A0 =
=A0 =A0 | =A0 =A0
                                      Version:<br>
                                      &gt; Severity: =A0- =A0 =A0 =A0 =A0 =
=A0 =A0|
                                      =A0Resolution:<br>
                                      &gt; Keywords: =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 |<br>
                                      &gt;
-------------------------+-------------------------------------------------=
<br>
                                      &gt;<br>
                                      &gt; Ticket URL: &lt;<a href=3D"http:=
//trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2" target=3D"_blank">h=
ttp://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2</a>&gt;<br>
                                      &gt; jose &lt;<a href=3D"http://tools=
.ietf.org/jose/" target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>
                                      &gt;<u></u><u></u></p>
                                  </div>
                                </div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12.0pt">&gt;
_______________________________________________<br>
                                      &gt; jose mailing list<br>
                                      &gt; <a href=3D"mailto:jose@ietf.org"=
 target=3D"_blank">jose@ietf.org</a><br>
                                      &gt; <a href=3D"https://www.ietf.org/=
mailman/listinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listi=
nfo/jose</a><u></u><u></u></p>
                                  </div>
                                </div>
                              </div>
                              <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
              </div>
            </div>
            <p class=3D"MsoNormal"><u></u>=A0<u></u></p>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
jose mailing list
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
    </div></div><span class=3D"HOEnZb"><font color=3D"#888888"><div>-- <br>
      <a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank">&lt;XeC&gt;</a></div>
  </font></span></div>

</blockquote></div><br></div></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
____________________________</span><br><span>jose mailing list</span><br><s=
pan><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mai=
lman/listinfo/jose</a></span><br>
</div></blockquote></div></blockquote><blockquote type=3D"cite"><div><span>=
_______________________________________________</span><br><span>jose mailin=
g list</span><br><span><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a></=
span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ie=
tf.org/mailman/listinfo/jose</a></span><br></div></blockquote></body></html=
>

--047d7bf10b46d82ab304df243683--

From Michael.Jones@microsoft.com  Fri Jun 14 14:53:24 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E000521F99FA for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyg-GMAvJ8Xe for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:53:19 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 02BF321F8BE6 for <jose@ietf.org>; Fri, 14 Jun 2013 14:53:18 -0700 (PDT)
Received: from BL2FFO11FD011.protection.gbl (10.173.161.200) by BL2FFO11HUB006.protection.gbl (10.173.160.226) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 14 Jun 2013 21:53:16 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD011.mail.protection.outlook.com (10.173.161.17) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 14 Jun 2013 21:53:16 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Fri, 14 Jun 2013 21:52:57 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Phillip Hallam-Baker <hallam@gmail.com>, Phil Hunt <phil.hunt@oracle.com>
Thread-Topic: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
Thread-Index: AQHOaFADwOjaNxai5EGlTbl2wCmnzpk1wVAAgAAAhpA=
Date: Fri, 14 Jun 2013 21:52:56 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com> <7188842785648960750@unknownmsgid>
In-Reply-To: <7188842785648960750@unknownmsgid>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436785A88BTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(24454002)(479174002)(51704005)(51444003)(52044002)(377454002)(189002)(22974005)(199002)(377424003)(164054003)(79102001)(6806003)(76786001)(76796001)(47976001)(81342001)(512954002)(74662001)(51856001)(31966008)(54356001)(74706001)(16406001)(74366001)(47446002)(74502001)(59766001)(81542001)(46102001)(55846006)(33656001)(54316002)(49866001)(44976003)(16236675002)(15202345002)(56816003)(20776003)(77982001)(63696002)(76482001)(47736001)(80022001)(56776001)(4396001)(77096001)(66066001)(65816001)(50986001)(69226001)(74876001)(53806001)(71186001)(15395725003); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB006; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08770259B4
Cc: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 21:53:25 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436785A88BTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Short names were chosen because of the core compactness requirement for the=
 Compact Serialization.  That was an engineering decision that was consciou=
sly made and for which the rationale is clear.

You can disagree with that decision but it has known clear benefits and is =
far from arbitrary.

                                                                -- Mike

From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
Sent: Friday, June 14, 2013 2:49 PM
To: Phil Hunt
Cc: Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org; <jose@ietf.org>=
; George Fletcher
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of=
 binary encoding (base64))

I think in this case that it is late to bring up binary encoding in Jose

But that does not mean we can't add it later. Specs have revisions. All tha=
t is needed to support binary is a flag to say what was signed. Defaults to=
 the current scheme.

Now if it was a case where binary had been raised at the start of the proce=
ss and the person got told to shut up because of 'focus' well that would be=
 different. When people pull that trick I have no qualms about repeating my=
 concerns in IETF last call. I think that all too often there is too much h=
aste when starting a WG and people get railroaded into a broken scheme some=
 faction likes. But that did not happen here so I think it is going to be f=
or the binary camp to work out the solution.

My bigger Jose concern is the bizarre decision to rename all the crypto alg=
 names. I have a spec that uses mime and JSON. If I take Jose seriously I n=
eed a second crypto alg registry.

That is junk, that is something that was raised at the start of the process=
. So yes, I will make it an issue in IETF last call

Sent from my difference engine


On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com<mailto:phil.h=
unt@oracle.com>> wrote:
Seems like many these days are in a rush. They call for consensus before di=
scussing the issue.

Isn't it up to the chair?

This isn't unique to this WG.

Too many times the explanation for keeping an apparent 'feature/flaw' is 'b=
ecause we don't want change'. Yet often the group can't explain it. Or wors=
e, the group just says "we know the emperor has no clothes, we just don't f=
eel the need to comment." This is where alarm bells go off for me.

Phil

On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>> wrot=
e:
This would have been a nice discussion to have had 18 months ago, when we w=
ere getting started.

I don't think it's compatible with the IETF ethos to say "Changes to this d=
ocument MUST NOT break existing code."  Otherwise, we're not doing engineer=
ing here, we're cleaning up documentation and rubber-stamping.

What would be acceptable is to say "Changes must break cleanly with existin=
g code".  That is, it should be possible for a JWT implementation to, say, =
process both "legacy" JWS syntax and whatever comes out of this group.  Tha=
t way, we could come to consensus on the best solution, incorporating lesso=
ns learned from earlier work without being hindered by them.

Would participants here consider it a acceptable for the output of this wor=
king group to be incompatible with existing JWT implementations, as long as=
 it had the property that JW* objects in the new format could be clearly di=
stinguished from "legacy" JW* objects, so that implementations could adapt =
their processing?

--Richard



On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com<mailto:=
gffletch@aol.com>> wrote:
+1

Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.

Thanks,
George
On 6/13/13 10:19 AM, Mike Jones wrote:
Jim and Karen, could you please do as Richard suggests and close this issue=
 as "won't fix".

                                                            Thank you,
                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Wednesday, June 12, 2013 1:57 PM
To: jose-chairs@tools.ietf.org<mailto:jose-chairs@tools.ietf.org>; Mike Jon=
es
Subject: Fwd: [jose] #23: Make crypto independent of binary encoding (base6=
4)

In other words: Chairs, feel free to close/wontfix :)

---------- Forwarded message ----------
From: Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
Date: Wed, Jun 12, 2013 at 4:55 PM
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)
To: "Matt Miller (mamille2)" <mamille2@cisco.com<mailto:mamille2@cisco.com>=
>
Cc: jose issue tracker <trac+jose@trac.tools.ietf.org<mailto:trac%2Bjose@tr=
ac.tools.ietf.org>>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org<m=
ailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>" <draft-ietf-jos=
e-json-web-encryption@tools.ietf.org<mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org>>, "<michael.jones@microsoft.com<mailto:michael.jones@m=
icrosoft.com>>" <michael.jones@microsoft.com<mailto:michael.jones@microsoft=
.com>>, "<jose@ietf.org<mailto:jose@ietf.org>>" <jose@ietf.org<mailto:jose@=
ietf.org>>
To be clear, I structured my message in two parts for a reason, to separate=
 the analysis from the opinion.  I acknowledge that I am but one voice here=
, and I'm increasingly hearing how alone I am :)

On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor c=
ode.  But I think we're literally talking about something like a 5-line pat=
ch.  And early JWT implementors knew or should have known (to use a DC phra=
se) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part i=
n the discussions are likely to find the specification changing out from un=
der them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE=
 in place of CMS one day, without the base64 hit.  We should incur the impl=
ementation pain now, and get the design right for the long run.  Base64 is =
a hack around JSON; we should build the system so that when we no longer ne=
ed that hack, it can go away.
</personal-opinion>

--Richard



On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m<mailto:mamille2@cisco.com>> wrote:
I did at first find it curious why the cryptographic operations were over t=
he base64url-enccoded values, but I was also very focused on JWE, where I t=
hink the field separation problem is less of an issue (at least now).  For =
JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload.  I do find it int=
eresting if JOSE could more easily and efficiently support other encodings.=
  However, I think that while this is an interesting thought experiment, it=
 seems we're too far down the path to seriously consider it unless the curr=
ent state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ietf.=
org<mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com<mailto:michael.jones@microsoft.co=
m>):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
> -------------------------+-----------------------------------------------=
--
> Reporter:  rlb@ipv.sx<mailto:rlb@ipv.sx>   |       Owner:  draft-ietf-jos=
e-json-web-
>     Type:  defect       |  encryption@tools.ietf.org<mailto:encryption@to=
ols.ietf.org>
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> -------------------------+-----------------------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org<mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose






_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose

--
<XeC><http://connect.me/gffletch>

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose

--_000_4E1F6AAD24975D4BA5B16804296739436785A88BTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas","serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Short names were chosen b=
ecause of the core compactness requirement for the Compact Serialization.&n=
bsp; That was an engineering decision that was consciously made
 and for which the rationale is clear.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">You can disagree with tha=
t decision but it has known clear benefits and is far from arbitrary.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [mailto:hallam@gmail.com]
<br>
<b>Sent:</b> Friday, June 14, 2013 2:49 PM<br>
<b>To:</b> Phil Hunt<br>
<b>Cc:</b> Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org; &lt;jose=
@ietf.org&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I think in this case that it is late to bring up bin=
ary encoding in Jose<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But that does not mean we can't add it later. Specs =
have revisions. All that is needed to support binary is a flag to say what =
was signed. Defaults to the current scheme.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Now if it was a case where binary had been raised at=
 the start of the process and the person got told to shut up because of 'fo=
cus' well that would be different. When people pull that trick I have no qu=
alms about repeating my concerns in
 IETF last call. I think that all too often there is too much haste when st=
arting a WG and people get railroaded into a broken scheme some faction lik=
es. But that did not happen here so I think it is going to be for the binar=
y camp to work out the solution.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">My bigger Jose concern is the bizarre decision to re=
name all the crypto alg names. I have a spec that uses mime and JSON. If I =
take Jose seriously I need a second crypto alg registry.&nbsp;<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">That is junk, that is something that was raised at t=
he start of the process. So yes, I will make it an issue in IETF last call<=
br>
<br>
Sent from my difference engine<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 13, 2013, at 12:06 PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@ora=
cle.com">phil.hunt@oracle.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Seems like many these days are in a rush. They call =
for consensus before discussing the issue.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Isn't it up to the chair?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This isn't unique to this WG.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Too many times the explanation for keeping an appare=
nt 'feature/flaw' is 'because we don't want change'. Yet often the group ca=
n't explain it. Or worse, the group just says &quot;we know the emperor has=
 no clothes, we just don't feel the need
 to comment.&quot; This is where alarm bells go off for me.&nbsp;<br>
<br>
Phil<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx">rl=
b@ipv.sx</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't think it's compatible with the IETF ethos to=
 say &quot;Changes to this document MUST NOT break existing code.&quot; &nb=
sp;Otherwise, we're not doing engineering here, we're cleaning up documenta=
tion and rubber-stamping.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. &nbsp;That is, it should be possi=
ble for a JWT implementation to, say, process both &quot;legacy&quot; JWS s=
yntax and whatever comes out of this group. &nbsp;That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&#43;1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span><o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:<o:p></o:p></p=
>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Jim and Karen, could you please do as R=
ichard suggests and close this issue as &#8220;won&#8217;t fix&#8221;.</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Thank you,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [<a hre=
f=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">In other words: Chairs, feel free to close/wontfix :)<o:p></o:p></=
p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">---------- Forwarded message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac&#43;jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<=
a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=
=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot=
;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">To be clear, I structured my message in two parts for a reason, to=
 separate the analysis from the opinion. &nbsp;I acknowledge that I am but =
one voice here, and I'm increasingly hearing
 how alone I am :)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;<a href=3D"mai=
lto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o:p></o:p></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;impartial-analysis&gt;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">So just to be clear on the trade-off the WG has to make:<o:p></o:p=
></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On the one hand: Breaking every existing JWT implementation in the=
 world<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On the other hand: Eternally binding ourselves to base64 encoding,=
 even if binary-safe encodings become available (CBOR, MsgPack, etc.)<o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/impartial-analysis&nbsp;&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I have some sympathy with JWT implementors. &nbsp;It sucks to have=
 to refactor code. &nbsp;But I think we're literally talking about somethin=
g like a 5-line patch. &nbsp;And early JWT implementors
 knew or should have known (to use a DC phrase) that they were dealing with=
 a draft spec. &nbsp;As the W3C editor's draft template says, in big bold r=
ed print, &quot;Implementors who are not taking part in the discussions are=
 likely to find the specification changing
 out from under them in incompatible ways.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">As PHB pointed out in the other thread, it would be nice to use JW=
S and JWE in place of CMS one day, without the base64 hit. &nbsp;We should =
incur the implementation pain now, and get
 the design right for the long run. &nbsp;Base64 is a hack around JSON; we =
should build the system so that when we no longer need that hack, it can go=
 away.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;/personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">--Richard</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) &lt;<a hr=
ef=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@cisco.com</a>&g=
t; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I did at first find it curious why the cryptographic operations we=
re over the base64url-enccoded values, but I was also very focused on JWE, =
where I think the field separation problem
 is less of an issue (at least now). &nbsp;For JWS, this would certainly ca=
use problems without some manner of unambiguous field parameterization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. &nbsp;I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. &nbsp;However, I think that while this
 is an interesting thought experiment, it seems we're too far down the path=
 to seriously consider it unless the current state were shown to be horribl=
y broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac&#43;jose@trac.tools.ietf=
.org</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact Seriali=
zation,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, com=
puting<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling reaso=
n to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that'=
s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually &quot;e=
xtra&quot; at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly the=
 same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ip=
v.sx</a> &nbsp; | &nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-we=
b-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a href=
=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ie=
tf.org</a><br>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp=
;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &n=
bsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;Res=
olution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&gt; _______________________________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>jose mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><o=
:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" target=3D"_blank" title=3D"View full=
 card on
        Connect.Me">&lt;XeC&gt;</a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436785A88BTK5EX14MBXC283r_--

From trac+jose@trac.tools.ietf.org  Fri Jun 14 14:57:22 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C42521F9AC4 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkpyUvX5tWL5 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 14:57:21 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A1CD021F9ABB for <jose@ietf.org>; Fri, 14 Jun 2013 14:57:21 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48092 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UnbzZ-00083K-9S; Fri, 14 Jun 2013 23:57:09 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, sakimura@gmail.com, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 21:57:09 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/4#comment:6
Message-ID: <069.f293db074dc16f92e9d0c83ae184c2a0@trac.tools.ietf.org>
References: <054.24cd2b074db2dc2bbbcb828a8456fbe9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 4
In-Reply-To: <054.24cd2b074db2dc2bbbcb828a8456fbe9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, sakimura@gmail.com, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614215721.A1CD021F9ABB@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 14:57:21 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #4: Remove wrapped keys from integrity check (allow separation of keys from data)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 21:57:22 -0000

#4: Remove wrapped keys from integrity check (allow separation of keys from
data)


Comment (by michael.jones@microsoft.com):

 This was done in draft-ietf-jose-json-web-encryption-11.  Therefore, I
 believe that this issue should be closed as fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/4#comment:6>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:01:10 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA8F21E805D for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvJUcyr76Sax for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:01:09 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 8888821E805A for <jose@ietf.org>; Fri, 14 Jun 2013 15:01:09 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48405 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Unc3M-0002IS-Us; Sat, 15 Jun 2013 00:01:04 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:01:04 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/11#comment:2
Message-ID: <069.3e78639091b01fcbb5aa6717e3a40900@trac.tools.ietf.org>
References: <054.e72d4c43dc02c0b9f61660ef223433e1@trac.tools.ietf.org>
X-Trac-Ticket-ID: 11
In-Reply-To: <054.e72d4c43dc02c0b9f61660ef223433e1@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614220109.8888821E805A@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:01:09 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #11: Use RFC 5116 and remove MAC field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:01:10 -0000

#11: Use RFC 5116 and remove MAC field


Comment (by michael.jones@microsoft.com):

 We have been using the McGrew algorithm since draft-ietf-jose-json-web-
 encryption-09.  Therefore, I believe that this issue should be closed.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/11#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:05:06 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B47B21F9811 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vL9xiR+6D7kh for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:05:05 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 1D33C21F968B for <jose@ietf.org>; Fri, 14 Jun 2013 15:05:03 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48901 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Unc6u-0000WP-TN; Sat, 15 Jun 2013 00:04:44 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:04:44 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/13#comment:4
Message-ID: <064.62d256a1d861caf827e7e13e11c467f0@trac.tools.ietf.org>
References: <049.6bd4c5bdeedc5862a9b09a5b5d16aadf@trac.tools.ietf.org>
X-Trac-Ticket-ID: 13
In-Reply-To: <049.6bd4c5bdeedc5862a9b09a5b5d16aadf@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614220505.1D33C21F968B@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:05:03 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #13: Enable AEAD key wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:05:06 -0000

#13: Enable AEAD key wrapping


Comment (by michael.jones@microsoft.com):

 draft-jones-jose-aes-gcm-key-wrap-00 demonstrates the ability to perform
 key wrapping with AEAD algorithms.  The working group can make a decision
 whether to incorporate this algorithm into JWA, but as far as satisfying
 the requirement to enable AEAD key wrapping, the current specifications
 already do.  Therefore, I believe that this issue should be closed as
 fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/13#comment:4>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:11:55 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5177B21F9AC5 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UqxCoRYqEM-F for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:11:54 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 732C421F9AC3 for <jose@ietf.org>; Fri, 14 Jun 2013 15:11:54 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49163 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UncDg-0002L4-9w; Sat, 15 Jun 2013 00:11:44 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:11:44 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/14#comment:3
Message-ID: <064.f233e737e3f53bd0adf01b311784a61b@trac.tools.ietf.org>
References: <049.a881241698112408b4f26b7cfb4b9103@trac.tools.ietf.org>
X-Trac-Ticket-ID: 14
In-Reply-To: <049.a881241698112408b4f26b7cfb4b9103@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614221154.732C421F9AC3@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:11:54 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #14: Support longer wrapped keys than OAEP allows
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:11:55 -0000

#14: Support longer wrapped keys than OAEP allows


Comment (by michael.jones@microsoft.com):

 I know of no symmetric keys used in practice that are greater than 1728
 (=2048-320) bits.  Therefore this is a theoretical limitation only - not a
 practical one.

 Should the working group ever decide to support a symmetric key type
 larger than can be wrapped with OAEP with 2048 bit keys AND should it
 decide that wrapping those symmetric keys with OAEP is desirable (and that
 simply doing so with a 4096 bit key isn't sufficient), at that point, this
 issue could be reopened.

 Until then, given that this is a theoretical problem, not an actual one, I
 believe that this issue should be closed as "won't fix".

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/14#comment:3>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:27:34 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F57621F99F3 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMZEiprYsn1G for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:27:33 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A688C21F99D2 for <jose@ietf.org>; Fri, 14 Jun 2013 15:27:33 -0700 (PDT)
Received: from localhost ([127.0.0.1]:50166 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UncSr-0003Ys-8s; Sat, 15 Jun 2013 00:27:25 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ignisvulpis@gmail.com,  michael.jones@microsoft.com, rlb@ipv.sx
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:27:25 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/15#comment:7
Message-ID: <064.de22d3d8e5e0ea0dd800411e031963e1@trac.tools.ietf.org>
References: <049.dec2e6a11006261f47529bfcdfa8c51d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 15
In-Reply-To: <049.dec2e6a11006261f47529bfcdfa8c51d@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ignisvulpis@gmail.com, michael.jones@microsoft.com, rlb@ipv.sx, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614222733.A688C21F99D2@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:27:33 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #15: At least one key indicator should be mandatory
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:27:34 -0000

#15: At least one key indicator should be mandatory


Comment (by michael.jones@microsoft.com):

 draft-ietf-jose-json-web-encryption-11, draft-ietf-jose-json-web-
 signature-11, and draft-ietf-jose-json-web-key-11 incorporate the
 resolution to this issue agreed to at the interim working group meeting in
 Denver.  Specifically, this new section is now present in JWS and a
 corresponding section is present in JWE:

 7.  Key Identification

    It is necessary for the recipient of a JWS to be able to determine
    the key that was employed for the digital signature or MAC operation.
    The key employed can be identified using the Header Parameter methods
    described in Section 4.1 or can be identified using methods that are
    outside the scope of this specification.  Specifically, the Header
    Parameters "jku", "jwk", "x5u", "x5t", "x5c", and "kid" can be used
    to identify the key used.  The sender SHOULD include sufficient
    information in the Header Parameters to identify the key used, unless
    the application uses another means or convention to determine the key
    used.

 Also, this text is now present in the "kid" description in JWK:

    When "kid" values are used within a JWK Set, different
    keys within the JWK Set SHOULD use distinct "kid" values.  The "kid"
    value is a case sensitive string.  Use of this member is OPTIONAL.

    When used with JWS or JWE, the "kid" value can be used to match a JWS
    or JWE "kid" header parameter value.

 Therefore, I believe that this issue should be closed as fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  minor        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/15#comment:7>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:33:49 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F33A21F9B20 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZGBSplHcF2Em for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:33:48 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 4307F21F9B19 for <jose@ietf.org>; Fri, 14 Jun 2013 15:33:48 -0700 (PDT)
Received: from localhost ([127.0.0.1]:50554 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UncYs-0001ZJ-Ob; Sat, 15 Jun 2013 00:33:38 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:33:38 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/18#comment:2
Message-ID: <064.fe6a014d5b1f6a7124fb025225cf5335@trac.tools.ietf.org>
References: <049.d29eb38c96b761dee70b1317e2c051c7@trac.tools.ietf.org>
X-Trac-Ticket-ID: 18
In-Reply-To: <049.d29eb38c96b761dee70b1317e2c051c7@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130614223348.4307F21F9B19@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:33:48 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #18: Address MAC key lifetime concerns
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:33:49 -0000

#18: Address MAC key lifetime concerns


Comment (by michael.jones@microsoft.com):

 What existing security considerations on key lifetimes would it be
 appropriate for us to reference?  These have to exist, albeit, perhaps in
 algorithm-specific contexts.

 Given that JOSE is only defining a representation for the inputs and
 outputs of existing algorithms, not defining new algorithms, perhaps the
 right thing to do is also the simple thing to do: state that they key
 lifetime security considerations in the specifications that define those
 algorithms continue to apply when using those algorithms using JOSE data
 structures.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  signature@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  signature              |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/18#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:35:11 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4968B21F9399 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3-tD8OC7UjY for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:35:10 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A686A21F91BC for <jose@ietf.org>; Fri, 14 Jun 2013 15:35:10 -0700 (PDT)
Received: from localhost ([127.0.0.1]:50645 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UncaG-00016R-9A; Sat, 15 Jun 2013 00:35:04 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ietf@augustcellars.com, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:35:04 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/8#comment:2
Message-ID: <069.02a847a195513e6498c880c98f444be8@trac.tools.ietf.org>
References: <054.96c0b71d4934f695a54309d767dbf877@trac.tools.ietf.org>
X-Trac-Ticket-ID: 8
In-Reply-To: <054.96c0b71d4934f695a54309d767dbf877@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ietf@augustcellars.com, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614223510.A686A21F91BC@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:35:10 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #8: Direct mode for key agreement needs security analysis
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:35:11 -0000

#8: Direct mode for key agreement needs security analysis


Comment (by michael.jones@microsoft.com):

 What existing security considerations on key lifetimes of encryption keys
 would it be appropriate for us to reference?  These have to exist, albeit,
 perhaps in algorithm-specific contexts.

 Given that JOSE is only defining a representation for the inputs and
 outputs of existing algorithms, not defining new algorithms, perhaps the
 right thing to do is also the simple thing to do: state that they key
 lifetime security considerations in the specifications that define those
 algorithms continue to apply when using those algorithms using JOSE data
 structures.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/8#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:42:48 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4A121F9A2F for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5P8Ae7nlztpc for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:42:48 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id C57CC21F99C9 for <jose@ietf.org>; Fri, 14 Jun 2013 15:42:47 -0700 (PDT)
Received: from localhost ([127.0.0.1]:51123 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Unchd-0005QW-1d; Sat, 15 Jun 2013 00:42:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:42:41 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/20#comment:1
Message-ID: <064.43ef764633c118590cd42e21925dc061@trac.tools.ietf.org>
References: <049.92c9829790c8d5776a0efee36c11df4c@trac.tools.ietf.org>
X-Trac-Ticket-ID: 20
In-Reply-To: <049.92c9829790c8d5776a0efee36c11df4c@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614224247.C57CC21F99C9@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:42:47 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #20: Shorter names for JSON serialization
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:42:48 -0000

#20: Shorter names for JSON serialization


Comment (by michael.jones@microsoft.com):

 Following discussion and apparent agreement by the working group on the
 mailing list, the following shorter names are now used:

     initialization_vector was changed to "iv"
     authentication_tag was changed to "tag"

 Given that "payload" and "ciphertext" are different data structures, as
 discussed on the list, they have not been coalesced into a combined "data"
 member.

 Also, given that there is not the same compactness requirement for the
 JSON Serialization as for the Compact Serialization, using full words for
 "signatures", "signature", and "recipients" does not seem excessive.

 Finally, "keys" would be incorrect, because these values represent
 information that is recipient-specific, which includes more than just
 keys.

 Given that reasonable shortenings of multi-word phrases to shorter names
 have been applied, as discussed on the mailing list, I believe that this
 issue should be closed as fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  minor        |      Status:  new
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/20#comment:1>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:44:52 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B1D21F91AB for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVLhNiyYxgBm for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:44:52 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD2C21F911B for <jose@ietf.org>; Fri, 14 Jun 2013 15:44:46 -0700 (PDT)
Received: from localhost ([127.0.0.1]:51396 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Uncjb-0007rJ-PT; Sat, 15 Jun 2013 00:44:43 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-key@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:44:43 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/21#comment:1
Message-ID: <072.a980fe69d7ddc981fcd53f6bd266788e@trac.tools.ietf.org>
References: <057.3a020ce8d5a302c89bd1b870e2763fec@trac.tools.ietf.org>
X-Trac-Ticket-ID: 21
In-Reply-To: <057.3a020ce8d5a302c89bd1b870e2763fec@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-key@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20130614224446.7AD2C21F911B@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:44:46 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #21: JWK and JWKSet do not have media types registered
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:44:52 -0000

#21: JWK and JWKSet do not have media types registered


Comment (by michael.jones@microsoft.com):

 Registrations for these media types were added in draft-ietf-jose-json-
 web-key-11.  Therefore, I believe that this issue should be closed as
 fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  mamille2@cisco.com     |  key@tools.ietf.org
     Type:  enhancement  |      Status:  new
 Priority:  minor        |   Milestone:
Component:  json-web-    |     Version:
  key                    |  Resolution:
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/21#comment:1>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:46:43 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3E821F9AA8 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJdOs4HYF9pC for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:46:43 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 25AE221F9AA7 for <jose@ietf.org>; Fri, 14 Jun 2013 15:46:43 -0700 (PDT)
Received: from localhost ([127.0.0.1]:51555 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UnclR-0006ca-Sr; Sat, 15 Jun 2013 00:46:37 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:46:37 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/22#comment:1
Message-ID: <072.bdcd9912429e47afa10959b84a997555@trac.tools.ietf.org>
References: <057.d511828d9b6553c2cb165ff15b303f78@trac.tools.ietf.org>
X-Trac-Ticket-ID: 22
In-Reply-To: <057.d511828d9b6553c2cb165ff15b303f78@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130614224643.25AE221F9AA7@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:46:43 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #22: JSON Serialization media types not consistent with RFC 6839
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:46:43 -0000

#22: JSON Serialization media types not consistent with RFC 6839


Comment (by michael.jones@microsoft.com):

 The media type registrations in draft-ietf-jose-json-web-signature-11 and
 draft-ietf-jose-json-web-encryption-11 have been changed to those
 suggested in the ticket.  Therefore, I believe that this issue should be
 closed as fixed.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  mamille2@cisco.com     |  encryption@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  minor        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/22#comment:1>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Fri Jun 14 15:56:44 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7141621E805D for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I71GSb0n+aOV for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 15:56:44 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id C86EC21E805A for <jose@ietf.org>; Fri, 14 Jun 2013 15:56:43 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52689 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Uncv7-0002QJ-0I; Sat, 15 Jun 2013 00:56:37 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Fri, 14 Jun 2013 22:56:36 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/24#comment:1
Message-ID: <064.2ecd3b99322f20f71f817a0ba1a3716e@trac.tools.ietf.org>
References: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 24
In-Reply-To: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130614225643.C86EC21E805A@ietfa.amsl.com>
Resent-Date: Fri, 14 Jun 2013 15:56:43 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #24: Move JWS headers into signature block
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 22:56:44 -0000

#24: Move JWS headers into signature block


Comment (by michael.jones@microsoft.com):

 The problem with this proposal is that it makes the structure of the
 headers for the JWS and JWE JSON Serializations no longer parallel.
 Having unnecessary differences between the two can only confuse developers
 and hurt interoperability.

 We decided at the interim meeting in Denver not to have per-recipient
 protected headers and so that's what's in the -11 specs.  It therefore
 doesn't make a lot of sense to add them to the JWS Compact Serialization
 when there are cryptographic reasons that they can't be added to the JWE
 Compact Serialization in the general case (as discussed at length!).

 Also, having shared protected and unprotected header locations in the JWS
 Compact Serialization means that if all signatures are doing something in
 common, such as using the same algorithm, they can represent this in one
 place, rather than being forced to replicate the information for each
 signature.  This capability is already there in the JWE JSON
 Serialization.  Let's not then remove it for JWS.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  signature@tools.ietf.org
 Priority:  major        |      Status:  new
Component:  json-web-    |   Milestone:
  signature              |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/24#comment:1>
jose <http://tools.ietf.org/jose/>


From hallam@gmail.com  Fri Jun 14 16:56:07 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C6611E80E4 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 16:56:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhJiAgkz05nR for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 16:56:06 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5077811E80E1 for <jose@ietf.org>; Fri, 14 Jun 2013 16:56:05 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id c10so2547056wiw.2 for <jose@ietf.org>; Fri, 14 Jun 2013 16:56:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; bh=UHcsUBjdg1S5Os9+k9V7qIwPJPn9lVLbr2nvYN4Rd1k=; b=jcBv4EA4FNvwzzroxPmANNTo12pXWlgFv81nSeOZm2I9KsGBCkx0pUlwd2zKCwSoTg qxA/nyuI/fEAsTwVspm95wn8yt2NKIaEbJ1SsAZ1Cf5wI6u5rmADpGvW1TrlVcIbgqy8 5bM8VJew8NIrs22EP8RUOog09wZqHYL3I7WzYbP0UNap68SVJejsmpLMOOhcVddwD8xg Disy8Omx+/0jp86mFQy7lln7ix3g5aQwJxOHpXsZNOA6TzYbBlnhQOZf52yqomBpOi+D mDzCa0eIAfSB+B66O+h1uitXnxKqn0kv3hq0LPvewprWWTy5BRCBVpO+8a3Eld6uat9p Xb+A==
X-Received: by 10.180.189.136 with SMTP id gi8mr18832wic.11.1371254163014; Fri, 14 Jun 2013 16:56:03 -0700 (PDT)
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com> <7188842785648960750@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com>
Mime-Version: 1.0 (1.0)
From: Phillip Hallam-Baker <hallam@gmail.com>
Date: Fri, 14 Jun 2013 19:55:57 -0400
Message-ID: <-7448156496304357389@unknownmsgid>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2412c488aa904df25fd0f
Cc: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>, Phil Hunt <phil.hunt@oracle.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 23:56:07 -0000

--001a11c2412c488aa904df25fd0f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

So is the idea that a standards organization should seek consistency

I understand the WG rationale. I reject it as a sufficient IETF rationale.
If it stands it is going to require two parallel registries for the same
algs.

I have a spec that crosses HTTP and JSON. Am I supposed to use mime
registry in one and this duplicate scheme in the other?

Blocking that type of move is what IETF last call is for. There is a
negligible benefit in the spec and a huge cost to the community.


Sent from my differenc engine


On Jun 14, 2013, at 5:53 PM, Mike Jones <Michael.Jones@microsoft.com> wrote=
:

  Short names were chosen because of the core compactness requirement for
the Compact Serialization.  That was an engineering decision that was
consciously made and for which the rationale is clear.



You can disagree with that decision but it has known clear benefits and is
far from arbitrary.



                                                                -- Mike



*From:* Phillip Hallam-Baker [mailto:hallam@gmail.com <hallam@gmail.com>]
*Sent:* Friday, June 14, 2013 2:49 PM
*To:* Phil Hunt
*Cc:* Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org; <jose@ietf.or=
g>;
George Fletcher
*Subject:* Re: [jose] Deployed Code (was: Re: #23: Make crypto independent
of binary encoding (base64))



I think in this case that it is late to bring up binary encoding in Jose



But that does not mean we can't add it later. Specs have revisions. All
that is needed to support binary is a flag to say what was signed. Defaults
to the current scheme.



Now if it was a case where binary had been raised at the start of the
process and the person got told to shut up because of 'focus' well that
would be different. When people pull that trick I have no qualms about
repeating my concerns in IETF last call. I think that all too often there
is too much haste when starting a WG and people get railroaded into a
broken scheme some faction likes. But that did not happen here so I think
it is going to be for the binary camp to work out the solution.



My bigger Jose concern is the bizarre decision to rename all the crypto alg
names. I have a spec that uses mime and JSON. If I take Jose seriously I
need a second crypto alg registry.



That is junk, that is something that was raised at the start of the
process. So yes, I will make it an issue in IETF last call

Sent from my difference engine




On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com> wrote:

 Seems like many these days are in a rush. They call for consensus before
discussing the issue.



Isn't it up to the chair?



This isn't unique to this WG.



Too many times the explanation for keeping an apparent 'feature/flaw' is
'because we don't want change'. Yet often the group can't explain it. Or
worse, the group just says "we know the emperor has no clothes, we just
don't feel the need to comment." This is where alarm bells go off for me.

Phil


On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx> wrote:

 This would have been a nice discussion to have had 18 months ago, when we
were getting started.



I don't think it's compatible with the IETF ethos to say "Changes to this
document MUST NOT break existing code."  Otherwise, we're not doing
engineering here, we're cleaning up documentation and rubber-stamping.



What would be acceptable is to say "Changes must break cleanly with
existing code".  That is, it should be possible for a JWT implementation
to, say, process both "legacy" JWS syntax and whatever comes out of this
group.  That way, we could come to consensus on the best solution,
incorporating lessons learned from earlier work without being hindered by
them.



Would participants here consider it a acceptable for the output of this
working group to be incompatible with existing JWT implementations, as long
as it had the property that JW* objects in the new format could be clearly
distinguished from "legacy" JW* objects, so that implementations could
adapt their processing?



--Richard







On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com> wrote:

+1

Breaking deployed code as raised by Brian, Naveen and others is a critical
consideration.

Thanks,
George

On 6/13/13 10:19 AM, Mike Jones wrote:

 Jim and Karen, could you please do as Richard suggests and close this
issue as =93won=92t fix=94.



                                                            Thank you,

                                                            -- Mike



*From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
*Sent:* Wednesday, June 12, 2013 1:57 PM
*To:* jose-chairs@tools.ietf.org; Mike Jones
*Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
(base64)



In other words: Chairs, feel free to close/wontfix :)



---------- Forwarded message ----------
From: *Richard Barnes* <rlb@ipv.sx>
Date: Wed, Jun 12, 2013 at 4:55 PM
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<jose@ietf.or=
g>"
<jose@ietf.org>

To be clear, I structured my message in two parts for a reason, to separate
the analysis from the opinion.  I acknowledge that I am but one voice here,
and I'm increasingly hearing how alone I am :)



On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:

 <impartial-analysis>

So just to be clear on the trade-off the WG has to make:



On the one hand: Breaking every existing JWT implementation in the world

On the other hand: Eternally binding ourselves to base64 encoding, even if
binary-safe encodings become available (CBOR, MsgPack, etc.)

</impartial-analysis >



<personal-opinion>

I have some sympathy with JWT implementors.  It sucks to have to refactor
code.  But I think we're literally talking about something like a 5-line
patch.  And early JWT implementors knew or should have known (to use a DC
phrase) that they were dealing with a draft spec.  As the W3C editor's
draft template says, in big bold red print, "Implementors who are not
taking part in the discussions are likely to find the specification
changing out from under them in incompatible ways."



As PHB pointed out in the other thread, it would be nice to use JWS and JWE
in place of CMS one day, without the base64 hit.  We should incur the
implementation pain now, and get the design right for the long run.  Base64
is a hack around JSON; we should build the system so that when we no longer
need that hack, it can go away.

</personal-opinion>



--Richard







On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m>
wrote:

I did at first find it curious why the cryptographic operations were over
the base64url-enccoded values, but I was also very focused on JWE, where I
think the field separation problem is less of an issue (at least now).  For
JWS, this would certainly cause problems without some manner of unambiguous
field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used
as a separator between the encoded header and the payload.  I do find it
interesting if JOSE could more easily and efficiently support other
encodings.  However, I think that while this is an interesting thought
experiment, it seems we're too far down the path to seriously consider it
unless the current state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.


On Jun 11, 2013, at 6:01 PM, jose issue tracker <
trac+jose@trac.tools.ietf.org> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
>
-------------------------+-------------------------------------------------
> Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>     Type:  defect       |  encryption@tools.ietf.org
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
>
-------------------------+-------------------------------------------------
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>

> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose









 _______________________________________________

jose mailing list

jose@ietf.org

https://www.ietf.org/mailman/listinfo/jose



--=20
<XeC> <http://connect.me/gffletch>



 _______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

  _______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

--001a11c2412c488aa904df25fd0f
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=
=3Dutf-8"></head><body dir=3D"auto"><div>So is the idea that a standards or=
ganization should seek consistency</div><div><br></div><div>I understand th=
e WG rationale. I reject it as a sufficient IETF rationale. If it stands it=
 is going to require two parallel registries for the same algs.</div>
<div><br></div><div>I have a spec that crosses HTTP and JSON. Am I supposed=
 to use mime registry in one and this duplicate scheme in the other?</div><=
div><br></div><div>Blocking that type of move is what IETF last call is for=
. There is a negligible benefit in the spec and a huge cost to the communit=
y.</div>
<div><br><br>Sent from my differenc engine<div><br></div></div><div><br>On =
Jun 14, 2013, at 5:53 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones@mi=
crosoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<br><br></div><block=
quote type=3D"cite">
<div>

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas","serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>


<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Short names were chosen b=
ecause of the core compactness requirement for the Compact Serialization.=
=A0 That was an engineering decision that was consciously made
 and for which the rationale is clear.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">You can disagree with tha=
t decision but it has known clear benefits and is far from arbitrary.</span=
></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [<a href=3D"mailto:hallam@gmail.com">mailto:hallam@gmail.com</=
a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 2:49 PM<br>
<b>To:</b> Phil Hunt<br>
<b>Cc:</b> Richard Barnes; Mike Jones; <a href=3D"mailto:jose-chairs@tools.=
ietf.org">jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"mailto:jose@ietf.o=
rg">jose@ietf.org</a>&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))</span></p>
</div>
</div>
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal">I think in this case that it is late to bring up bin=
ary encoding in Jose</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">But that does not mean we can&#39;t add it later. Sp=
ecs have revisions. All that is needed to support binary is a flag to say w=
hat was signed. Defaults to the current scheme.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Now if it was a case where binary had been raised at=
 the start of the process and the person got told to shut up because of &#3=
9;focus&#39; well that would be different. When people pull that trick I ha=
ve no qualms about repeating my concerns in
 IETF last call. I think that all too often there is too much haste when st=
arting a WG and people get railroaded into a broken scheme some faction lik=
es. But that did not happen here so I think it is going to be for the binar=
y camp to work out the solution.=A0</p>

</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">My bigger Jose concern is the bizarre decision to re=
name all the crypto alg names. I have a spec that uses mime and JSON. If I =
take Jose seriously I need a second crypto alg registry.=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">That is junk, that is something that was raised at t=
he start of the process. So yes, I will make it an issue in IETF last call<=
br>
<br>
Sent from my difference engine</p>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 13, 2013, at 12:06 PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@ora=
cle.com">phil.hunt@oracle.com</a>&gt; wrote:</p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Seems like many these days are in a rush. They call =
for consensus before discussing the issue.=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Isn&#39;t it up to the chair?</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">This isn&#39;t unique to this WG.=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Too many times the explanation for keeping an appare=
nt &#39;feature/flaw&#39; is &#39;because we don&#39;t want change&#39;. Ye=
t often the group can&#39;t explain it. Or worse, the group just says &quot=
;we know the emperor has no clothes, we just don&#39;t feel the need
 to comment.&quot; This is where alarm bells go off for me.=A0<br>
<br>
Phil</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx">rl=
b@ipv.sx</a>&gt; wrote:</p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.</p>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">I don&#39;t think it&#39;s compatible with the IETF =
ethos to say &quot;Changes to this document MUST NOT break existing code.&q=
uot; =A0Otherwise, we&#39;re not doing engineering here, we&#39;re cleaning=
 up documentation and rubber-stamping.</p>

</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. =A0That is, it should be possible=
 for a JWT implementation to, say, process both &quot;legacy&quot; JWS synt=
ax and whatever comes out of this group. =A0That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">--Richard</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0</p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:</p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">+1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:</p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal" style><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim and Karen, coul=
d you please do as Richard suggests and close this issue as =93won=92t fix=
=94.</span></p>

<p class=3D"MsoNormal" style><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal" style><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 Thank you,</span></p>
<p class=3D"MsoNormal" style><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 -- Mike</span></p>
<p class=3D"MsoNormal" style><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span></p>
<p class=3D"MsoNormal" style><b><span style=3D"font-size:10.0pt;font-family=
:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"=
font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ri=
chard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ip=
v.sx</a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span></p>
<p class=3D"MsoNormal" style>=A0</p>
<div>
<p class=3D"MsoNormal" style>In other words: Chairs, feel free to close/won=
tfix :)</p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0</p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------- Forwarded =
message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<a hr=
ef=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=3D"=
_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;</p>
<div>
<p class=3D"MsoNormal" style>To be clear, I structured my message in two pa=
rts for a reason, to separate the analysis from the opinion. =A0I acknowled=
ge that I am but one voice here, and I&#39;m increasingly hearing
 how alone I am :)</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0</p>
<div>
<div>
<p class=3D"MsoNormal" style>On Wed, Jun 12, 2013 at 4:23 PM, Richard Barne=
s &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wr=
ote:</p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style>&lt;impartial-analysis&gt;</p>
</div>
<p class=3D"MsoNormal" style>So just to be clear on the trade-off the WG ha=
s to make:</p>
<div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
<div>
<p class=3D"MsoNormal" style>On the one hand: Breaking every existing JWT i=
mplementation in the world</p>
</div>
<div>
<p class=3D"MsoNormal" style>On the other hand: Eternally binding ourselves=
 to base64 encoding, even if binary-safe encodings become available (CBOR, =
MsgPack, etc.)</p>
</div>
<div>
<p class=3D"MsoNormal" style>&lt;/impartial-analysis=A0&gt;</p>
</div>
<div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
<div>
<p class=3D"MsoNormal" style>&lt;personal-opinion&gt;</p>
</div>
<div>
<p class=3D"MsoNormal" style>I have some sympathy with JWT implementors. =
=A0It sucks to have to refactor code. =A0But I think we&#39;re literally ta=
lking about something like a 5-line patch. =A0And early JWT implementors
 knew or should have known (to use a DC phrase) that they were dealing with=
 a draft spec. =A0As the W3C editor&#39;s draft template says, in big bold =
red print, &quot;Implementors who are not taking part in the discussions ar=
e likely to find the specification changing
 out from under them in incompatible ways.&quot;</p>
</div>
<div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
<div>
<p class=3D"MsoNormal" style>As PHB pointed out in the other thread, it wou=
ld be nice to use JWS and JWE in place of CMS one day, without the base64 h=
it. =A0We should incur the implementation pain now, and get
 the design right for the long run. =A0Base64 is a hack around JSON; we sho=
uld build the system so that when we no longer need that hack, it can go aw=
ay.</p>
</div>
<div>
<p class=3D"MsoNormal" style>&lt;/personal-opinion&gt;</p>
</div>
<div>
<p class=3D"MsoNormal" style><span style=3D"color:#888888">=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style><span style=3D"color:#888888">--Richard</span>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style><span style=3D"color:#888888">=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style><span style=3D"color:#888888">=A0</span></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0</p>
<div>
<p class=3D"MsoNormal" style>On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller =
(mamille2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mami=
lle2@cisco.com</a>&gt; wrote:</p>
<p class=3D"MsoNormal" style>I did at first find it curious why the cryptog=
raphic operations were over the base64url-enccoded values, but I was also v=
ery focused on JWE, where I think the field separation problem
 is less of an issue (at least now). =A0For JWS, this would certainly cause=
 problems without some manner of unambiguous field parameterization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this
 is an interesting thought experiment, it seems we&#39;re too far down the =
path to seriously consider it unless the current state were shown to be hor=
ribly broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.</p>
<div>
<div>
<p class=3D"MsoNormal" style><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.s=
x</a> =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-json-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;</p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
</div>
<p class=3D"MsoNormal" style>=A0</p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>jose mailing list</pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a></=
pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a></pre>
</blockquote>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" target=3D"_blank" title=3D"View full=
 card on
        Connect.Me">&lt;XeC&gt;</a></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a></p>
</div>
</blockquote>
</div>


</div></blockquote></body></html>

--001a11c2412c488aa904df25fd0f--

From Michael.Jones@microsoft.com  Fri Jun 14 16:59:16 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FECD11E80E9 for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 16:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVVjFE3Ycz4E for <jose@ietfa.amsl.com>; Fri, 14 Jun 2013 16:59:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 83AC811E80E8 for <jose@ietf.org>; Fri, 14 Jun 2013 16:59:10 -0700 (PDT)
Received: from BY2FFO11FD010.protection.gbl (10.1.15.203) by BY2FFO11HUB027.protection.gbl (10.1.14.113) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 14 Jun 2013 23:59:03 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD010.mail.protection.outlook.com (10.1.14.74) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 14 Jun 2013 23:59:03 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Fri, 14 Jun 2013 23:59:02 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Thread-Topic: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
Thread-Index: AQHOaFADwOjaNxai5EGlTbl2wCmnzpk1wVAAgAAAhpCAACL2gIAAAE2Q
Date: Fri, 14 Jun 2013 23:59:01 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436785D014@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com> <7188842785648960750@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com> <-7448156496304357389@unknownmsgid>
In-Reply-To: <-7448156496304357389@unknownmsgid>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436785D014TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(24454002)(22974005)(164054003)(51704005)(377424003)(51444003)(377454002)(52044002)(479174002)(79102001)(44976003)(46102001)(81542001)(16406001)(55846006)(56776001)(76482001)(74706001)(74366001)(512954002)(74502001)(51856001)(47446002)(59766001)(53806001)(71186001)(77982001)(1411001)(31966008)(54316002)(74662001)(54356001)(15395725003)(81342001)(56816003)(74876001)(33656001)(63696002)(66066001)(49866001)(15202345002)(80022001)(77096001)(47736001)(50986001)(76786001)(20776003)(65816001)(76796001)(69226001)(16236675002)(6806003)(4396001)(47976001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB027; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08770259B4
Cc: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>, Phil Hunt <phil.hunt@oracle.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 14 Jun 2013 23:59:16 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436785D014TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

What alternative registry of algorithm names were you thinking of?  Are you=
 suggesting that we use the OID numbers used by CMS?

As far as I know, there is no MIME registry of cryptographic algorithm name=
s, so I don't think there's any conflict/duplication there.

                                                                -- Mike

From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
Sent: Friday, June 14, 2013 4:56 PM
To: Mike Jones
Cc: Phil Hunt; Richard Barnes; jose-chairs@tools.ietf.org; <jose@ietf.org>;=
 George Fletcher
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of=
 binary encoding (base64))

So is the idea that a standards organization should seek consistency

I understand the WG rationale. I reject it as a sufficient IETF rationale. =
If it stands it is going to require two parallel registries for the same al=
gs.

I have a spec that crosses HTTP and JSON. Am I supposed to use mime registr=
y in one and this duplicate scheme in the other?

Blocking that type of move is what IETF last call is for. There is a neglig=
ible benefit in the spec and a huge cost to the community.


Sent from my differenc engine


On Jun 14, 2013, at 5:53 PM, Mike Jones <Michael.Jones@microsoft.com<mailto=
:Michael.Jones@microsoft.com>> wrote:
Short names were chosen because of the core compactness requirement for the=
 Compact Serialization.  That was an engineering decision that was consciou=
sly made and for which the rationale is clear.

You can disagree with that decision but it has known clear benefits and is =
far from arbitrary.

                                                                -- Mike

From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
Sent: Friday, June 14, 2013 2:49 PM
To: Phil Hunt
Cc: Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org<mailto:jose-chai=
rs@tools.ietf.org>; <jose@ietf.org<mailto:jose@ietf.org>>; George Fletcher
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of=
 binary encoding (base64))

I think in this case that it is late to bring up binary encoding in Jose

But that does not mean we can't add it later. Specs have revisions. All tha=
t is needed to support binary is a flag to say what was signed. Defaults to=
 the current scheme.

Now if it was a case where binary had been raised at the start of the proce=
ss and the person got told to shut up because of 'focus' well that would be=
 different. When people pull that trick I have no qualms about repeating my=
 concerns in IETF last call. I think that all too often there is too much h=
aste when starting a WG and people get railroaded into a broken scheme some=
 faction likes. But that did not happen here so I think it is going to be f=
or the binary camp to work out the solution.

My bigger Jose concern is the bizarre decision to rename all the crypto alg=
 names. I have a spec that uses mime and JSON. If I take Jose seriously I n=
eed a second crypto alg registry.

That is junk, that is something that was raised at the start of the process=
. So yes, I will make it an issue in IETF last call

Sent from my difference engine


On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com<mailto:phil.h=
unt@oracle.com>> wrote:
Seems like many these days are in a rush. They call for consensus before di=
scussing the issue.

Isn't it up to the chair?

This isn't unique to this WG.

Too many times the explanation for keeping an apparent 'feature/flaw' is 'b=
ecause we don't want change'. Yet often the group can't explain it. Or wors=
e, the group just says "we know the emperor has no clothes, we just don't f=
eel the need to comment." This is where alarm bells go off for me.

Phil

On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>> wrot=
e:
This would have been a nice discussion to have had 18 months ago, when we w=
ere getting started.

I don't think it's compatible with the IETF ethos to say "Changes to this d=
ocument MUST NOT break existing code."  Otherwise, we're not doing engineer=
ing here, we're cleaning up documentation and rubber-stamping.

What would be acceptable is to say "Changes must break cleanly with existin=
g code".  That is, it should be possible for a JWT implementation to, say, =
process both "legacy" JWS syntax and whatever comes out of this group.  Tha=
t way, we could come to consensus on the best solution, incorporating lesso=
ns learned from earlier work without being hindered by them.

Would participants here consider it a acceptable for the output of this wor=
king group to be incompatible with existing JWT implementations, as long as=
 it had the property that JW* objects in the new format could be clearly di=
stinguished from "legacy" JW* objects, so that implementations could adapt =
their processing?

--Richard



On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com<mailto:=
gffletch@aol.com>> wrote:
+1

Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.

Thanks,
George
On 6/13/13 10:19 AM, Mike Jones wrote:
Jim and Karen, could you please do as Richard suggests and close this issue=
 as "won't fix".

                                                            Thank you,
                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Wednesday, June 12, 2013 1:57 PM
To: jose-chairs@tools.ietf.org<mailto:jose-chairs@tools.ietf.org>; Mike Jon=
es
Subject: Fwd: [jose] #23: Make crypto independent of binary encoding (base6=
4)

In other words: Chairs, feel free to close/wontfix :)

---------- Forwarded message ----------
From: Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>>
Date: Wed, Jun 12, 2013 at 4:55 PM
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)
To: "Matt Miller (mamille2)" <mamille2@cisco.com<mailto:mamille2@cisco.com>=
>
Cc: jose issue tracker <trac+jose@trac.tools.ietf.org<mailto:trac%2Bjose@tr=
ac.tools.ietf.org>>, "<draft-ietf-jose-json-web-encryption@tools.ietf.org<m=
ailto:draft-ietf-jose-json-web-encryption@tools.ietf.org>>" <draft-ietf-jos=
e-json-web-encryption@tools.ietf.org<mailto:draft-ietf-jose-json-web-encryp=
tion@tools.ietf.org>>, "<michael.jones@microsoft.com<mailto:michael.jones@m=
icrosoft.com>>" <michael.jones@microsoft.com<mailto:michael.jones@microsoft=
.com>>, "<jose@ietf.org<mailto:jose@ietf.org>>" <jose@ietf.org<mailto:jose@=
ietf.org>>
To be clear, I structured my message in two parts for a reason, to separate=
 the analysis from the opinion.  I acknowledge that I am but one voice here=
, and I'm increasingly hearing how alone I am :)

On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
<impartial-analysis>
So just to be clear on the trade-off the WG has to make:

On the one hand: Breaking every existing JWT implementation in the world
On the other hand: Eternally binding ourselves to base64 encoding, even if =
binary-safe encodings become available (CBOR, MsgPack, etc.)
</impartial-analysis >

<personal-opinion>
I have some sympathy with JWT implementors.  It sucks to have to refactor c=
ode.  But I think we're literally talking about something like a 5-line pat=
ch.  And early JWT implementors knew or should have known (to use a DC phra=
se) that they were dealing with a draft spec.  As the W3C editor's draft te=
mplate says, in big bold red print, "Implementors who are not taking part i=
n the discussions are likely to find the specification changing out from un=
der them in incompatible ways."

As PHB pointed out in the other thread, it would be nice to use JWS and JWE=
 in place of CMS one day, without the base64 hit.  We should incur the impl=
ementation pain now, and get the design right for the long run.  Base64 is =
a hack around JSON; we should build the system so that when we no longer ne=
ed that hack, it can go away.
</personal-opinion>

--Richard



On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <mamille2@cisco.co=
m<mailto:mamille2@cisco.com>> wrote:
I did at first find it curious why the cryptographic operations were over t=
he base64url-enccoded values, but I was also very focused on JWE, where I t=
hink the field separation problem is less of an issue (at least now).  For =
JWS, this would certainly cause problems without some manner of unambiguous=
 field parameterization.

I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload.  I do find it int=
eresting if JOSE could more easily and efficiently support other encodings.=
  However, I think that while this is an interesting thought experiment, it=
 seems we're too far down the path to seriously consider it unless the curr=
ent state were shown to be horribly broken.


- m&m

Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >
Cisco Systems, Inc.

On Jun 11, 2013, at 6:01 PM, jose issue tracker <trac+jose@trac.tools.ietf.=
org<mailto:trac%2Bjose@trac.tools.ietf.org>> wrote:

> #23: Make crypto independent of binary encoding (base64)
>
>
> Comment (by michael.jones@microsoft.com<mailto:michael.jones@microsoft.co=
m>):
>
> For both serializations, you already need the base64url encoded versions
> of the JWS Header and the JWS Payload to preserve them in transmission, s=
o
> computing them isn't an extra burden.  In the JWS Compact Serialization,
> you already need the concatenation of the Encoded JWS Header, a period
> character, and the Encoded JWS Payload, so computing that concatenation
> isn't an extra burden.  Given you already have that quantity, computing
> the signature over it is the easiest thing for developers to do, and it's
> been shown to work well in practice.  There's no compelling reason to mak=
e
> this change.
>
> Even for the JSON Serialization, the only "extra" step that's required to
> compute the signature is the concatenation with the period character - to
> prevent shifting of data from one field to the other, as described by Jim
> Schaad in the e-mail thread.  So this step isn't actually "extra" at all =
-
> it's necessary.  It's also highly advantageous to use exactly the same
> computation for both serializations, which is currently the case.
>
> Since there is no compelling reason to make this change, and since making
> it could enable the "shifting" problem identified by Jim, it should not b=
e
> made.
>
> --
> -------------------------+-----------------------------------------------=
--
> Reporter:  rlb@ipv.sx<mailto:rlb@ipv.sx>   |       Owner:  draft-ietf-jos=
e-json-web-
>     Type:  defect       |  encryption@tools.ietf.org<mailto:encryption@to=
ols.ietf.org>
> Priority:  major        |      Status:  new
> Component:  json-web-    |   Milestone:
>  encryption             |     Version:
> Severity:  -            |  Resolution:
> Keywords:               |
> -------------------------+-----------------------------------------------=
--
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org<mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose





_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose

--
<XeC><http://connect.me/gffletch>

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose

--_000_4E1F6AAD24975D4BA5B16804296739436785D014TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">What alternative registry=
 of algorithm names were you thinking of?&nbsp; Are you suggesting that we =
use the OID numbers used by CMS?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As far as I know, there i=
s no MIME registry of cryptographic algorithm names, so I don&#8217;t think=
 there&#8217;s any conflict/duplication there.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [mailto:hallam@gmail.com]
<br>
<b>Sent:</b> Friday, June 14, 2013 4:56 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Phil Hunt; Richard Barnes; jose-chairs@tools.ietf.org; &lt;jose@=
ietf.org&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">So is the idea that a standards organization should =
seek consistency<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I understand the WG rationale. I reject it as a suff=
icient IETF rationale. If it stands it is going to require two parallel reg=
istries for the same algs.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I have a spec that crosses HTTP and JSON. Am I suppo=
sed to use mime registry in one and this duplicate scheme in the other?<o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Blocking that type of move is what IETF last call is=
 for. There is a negligible benefit in the spec and a huge cost to the comm=
unity.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
Sent from my differenc engine<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 14, 2013, at 5:53 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones=
@microsoft.com">Michael.Jones@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Short names were chosen b=
ecause of the core compactness requirement for the Compact Serialization.&n=
bsp; That was an engineering decision that was consciously made
 and for which the rationale is clear.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">You can disagree with tha=
t decision but it has known clear benefits and is far from arbitrary.</span=
><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [<a href=3D"mailto:hallam@gmail.com">mailto:hallam@gmail.com</=
a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 2:49 PM<br>
<b>To:</b> Phil Hunt<br>
<b>Cc:</b> Richard Barnes; Mike Jones; <a href=3D"mailto:jose-chairs@tools.=
ietf.org">
jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"mailto:jose@ietf.org">jose@i=
etf.org</a>&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">I think in this case that it is late to bring up bin=
ary encoding in Jose<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">But that does not mean we can't add it later. Specs =
have revisions. All that is needed to support binary is a flag to say what =
was signed. Defaults to the current scheme.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Now if it was a case where binary had been raised at=
 the start of the process and the person got told to shut up because of 'fo=
cus' well that would be different. When people pull that trick I have no qu=
alms about repeating my concerns in
 IETF last call. I think that all too often there is too much haste when st=
arting a WG and people get railroaded into a broken scheme some faction lik=
es. But that did not happen here so I think it is going to be for the binar=
y camp to work out the solution.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">My bigger Jose concern is the bizarre decision to re=
name all the crypto alg names. I have a spec that uses mime and JSON. If I =
take Jose seriously I need a second crypto alg registry.&nbsp;<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">That is junk, that is something that was raised at t=
he start of the process. So yes, I will make it an issue in IETF last call<=
br>
<br>
Sent from my difference engine<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 13, 2013, at 12:06 PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@ora=
cle.com">phil.hunt@oracle.com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Seems like many these days are in a rush. They call =
for consensus before discussing the issue.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Isn't it up to the chair?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This isn't unique to this WG.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Too many times the explanation for keeping an appare=
nt 'feature/flaw' is 'because we don't want change'. Yet often the group ca=
n't explain it. Or worse, the group just says &quot;we know the emperor has=
 no clothes, we just don't feel the need
 to comment.&quot; This is where alarm bells go off for me.&nbsp;<br>
<br>
Phil<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx">rl=
b@ipv.sx</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't think it's compatible with the IETF ethos to=
 say &quot;Changes to this document MUST NOT break existing code.&quot; &nb=
sp;Otherwise, we're not doing engineering here, we're cleaning up documenta=
tion and rubber-stamping.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. &nbsp;That is, it should be possi=
ble for a JWT implementation to, say, process both &quot;legacy&quot; JWS s=
yntax and whatever comes out of this group. &nbsp;That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&#43;1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span><o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:<o:p></o:p></p=
>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim and Karen, could you =
please do as Richard suggests and close this issue as &#8220;won&#8217;t fi=
x&#8221;.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank you,</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span><o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">In other words: Chairs, feel free to close/wontfix :=
)<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------- Forwarded =
message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac&#43;jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<=
a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=
=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot=
;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">To be clear, I structured my message in two parts fo=
r a reason, to separate the analysis from the opinion. &nbsp;I acknowledge =
that I am but one voice here, and I'm increasingly hearing how alone I am :=
)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o=
:p></o:p></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">&lt;impartial-analysis&gt;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">So just to be clear on the trade-off the WG has to m=
ake:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the one hand: Breaking every existing JWT impleme=
ntation in the world<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">On the other hand: Eternally binding ourselves to ba=
se64 encoding, even if binary-safe encodings become available (CBOR, MsgPac=
k, etc.)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/impartial-analysis&nbsp;&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I have some sympathy with JWT implementors. &nbsp;It=
 sucks to have to refactor code. &nbsp;But I think we're literally talking =
about something like a 5-line patch. &nbsp;And early JWT implementors knew =
or should have known (to use a DC phrase) that they
 were dealing with a draft spec. &nbsp;As the W3C editor's draft template s=
ays, in big bold red print, &quot;Implementors who are not taking part in t=
he discussions are likely to find the specification changing out from under=
 them in incompatible ways.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. &n=
bsp;We should incur the implementation pain now, and get the design right f=
or the long run. &nbsp;Base64 is a hack around
 JSON; we should build the system so that when we no longer need that hack,=
 it can go away.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/personal-opinion&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">&nbsp;</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard</span><o:p><=
/o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">&nbsp;</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">&nbsp;</span><o:p></o:=
p></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@c=
isco.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I did at first find it curious why the cryptographic=
 operations were over the base64url-enccoded values, but I was also very fo=
cused on JWE, where I think the field separation problem is less of an issu=
e (at least now). &nbsp;For JWS, this would
 certainly cause problems without some manner of unambiguous field paramete=
rization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. &nbsp;I do find i=
t interesting if JOSE could more easily and efficiently support other encod=
ings. &nbsp;However, I think that while this
 is an interesting thought experiment, it seems we're too far down the path=
 to seriously consider it unless the current state were shown to be horribl=
y broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac&#43;jose@trac.tools.ietf=
.org</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn't an extra burden. &nbsp;In the JWS Compact Seriali=
zation,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn't an extra burden. &nbsp;Given you already have that quantity, com=
puting<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t's<br>
&gt; been shown to work well in practice. &nbsp;There's no compelling reaso=
n to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that'=
s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. &nbsp;So this step isn't actually &quot;e=
xtra&quot; at all -<br>
&gt; it's necessary. &nbsp;It's also highly advantageous to use exactly the=
 same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt; Reporter: &nbsp;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ip=
v.sx</a> &nbsp; | &nbsp; &nbsp; &nbsp; Owner: &nbsp;draft-ietf-jose-json-we=
b-<br>
&gt; &nbsp; &nbsp; Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | &nbsp;<a href=
=3D"mailto:encryption@tools.ietf.org" target=3D"_blank">encryption@tools.ie=
tf.org</a><br>
&gt; Priority: &nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp=
;Status: &nbsp;new<br>
&gt; Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; Milestone:<br>
&gt; &nbsp;encryption &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &n=
bsp; Version:<br>
&gt; Severity: &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;Res=
olution:<br>
&gt; Keywords: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>
&gt; -------------------------&#43;----------------------------------------=
---------<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>jose mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><o=
:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" target=3D"_blank" title=3D"View full=
 card on
        Connect.Me">&lt;XeC&gt;</a></span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org=
/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436785D014TK5EX14MBXC283r_--

From hallam@gmail.com  Sat Jun 15 13:02:16 2013
Return-Path: <hallam@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE7621F9DCC for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 13:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6Z8FrpddOI2 for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 13:02:14 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6D421F9D97 for <jose@ietf.org>; Sat, 15 Jun 2013 13:02:13 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id m6so1254159wiv.2 for <jose@ietf.org>; Sat, 15 Jun 2013 13:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4kVbEo/z3hm1qUjhSOdTU+xVNIVUeF5Sx+PG226cBI4=; b=VKy5zd2Ghk/A2Rc8E5YoKux34e0KIVzl1LPAexpu/1FhFldqXZLWArVRkvC8iQieCQ rZqaM8mCyw/GTT2qc+woCXb3Xik4PpuTcGTJTUFpBbOzwI9fVGaFLjcnjm7x5K72eSsd Q1OH8oC/ba2f7ltLQiXya5/3sBpU+YYjnWYl4+hRPLPyLUQxk0iI0x7Y/MlJIH77lX6u WN2ywFwwIba+Erk2be4KP5b4T/zVccoLtnywHlApxna1SS5hmlIvqq+TjEweaMfmjNMB Bzr16ID+Lh+Sg1ylF9bksgHcDZXbgRorDYYfoAMlbaeifaE68JdDHBS/cMJSnzSwKc4y RjzA==
MIME-Version: 1.0
X-Received: by 10.180.9.242 with SMTP id d18mr1551843wib.18.1371326532319; Sat, 15 Jun 2013 13:02:12 -0700 (PDT)
Received: by 10.194.54.10 with HTTP; Sat, 15 Jun 2013 13:02:12 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436785D014@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com> <7188842785648960750@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com> <-7448156496304357389@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785D014@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sat, 15 Jun 2013 16:02:12 -0400
Message-ID: <CAMm+Lwjf6azxD67hKTsjmJv2M1sOX0OqM65-29n2FqRCZsuDwQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2228cd482e104df36d6f0
Cc: Richard Barnes <rlb@ipv.sx>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>, Phil Hunt <phil.hunt@oracle.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 15 Jun 2013 20:02:16 -0000

--001a11c2228cd482e104df36d6f0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The name fields in the following originate from PEM:
http://www.iana.org/assignments/dssc/dssc.xml

The same code points are used in HTTP Digest
http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xml

SSH uses the same code points again and defines HMAC code points:
http://www.iana.org/assignments/ssh-parameters/ssh-parameters.xml#ssh-param=
eters-18


I don't think that when you are using base64 for encoding you can really
make an issue of the difference between hmac-sha2-256 and hs256 as being
serious enough to justify a whole new registry and a whole different set of
encodings.

The JWA algorithm should instead update the DSSC registry which was
originally conceived as being a single registry and point of contact for
all crypto algorithms and canonical identifiers for all protocols that do
not use protocol specific code points (like IPSEC, DNSSEC).


Setting up registries is easy. Maintaining them is not.




On Fri, Jun 14, 2013 at 7:59 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  What alternative registry of algorithm names were you thinking of?  Are
> you suggesting that we use the OID numbers used by CMS?****
>
> ** **
>
> As far as I know, there is no MIME registry of cryptographic algorithm
> names, so I don=92t think there=92s any conflict/duplication there.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Phillip Hallam-Baker [mailto:hallam@gmail.com]
> *Sent:* Friday, June 14, 2013 4:56 PM
> *To:* Mike Jones
> *Cc:* Phil Hunt; Richard Barnes; jose-chairs@tools.ietf.org; <
> jose@ietf.org>; George Fletcher
>
> *Subject:* Re: [jose] Deployed Code (was: Re: #23: Make crypto
> independent of binary encoding (base64))****
>
>  ** **
>
> So is the idea that a standards organization should seek consistency****
>
> ** **
>
> I understand the WG rationale. I reject it as a sufficient IETF rationale=
.
> If it stands it is going to require two parallel registries for the same
> algs.****
>
> ** **
>
> I have a spec that crosses HTTP and JSON. Am I supposed to use mime
> registry in one and this duplicate scheme in the other?****
>
> ** **
>
> Blocking that type of move is what IETF last call is for. There is a
> negligible benefit in the spec and a huge cost to the community.****
>
>
>
> Sent from my differenc engine****
>
> ** **
>
>
> On Jun 14, 2013, at 5:53 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
>  Short names were chosen because of the core compactness requirement for
> the Compact Serialization.  That was an engineering decision that was
> consciously made and for which the rationale is clear.****
>
>  ****
>
> You can disagree with that decision but it has known clear benefits and i=
s
> far from arbitrary.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* Phillip Hallam-Baker [mailto:hallam@gmail.com <hallam@gmail.com>]
> *Sent:* Friday, June 14, 2013 2:49 PM
> *To:* Phil Hunt
> *Cc:* Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org; <
> jose@ietf.org>; George Fletcher
> *Subject:* Re: [jose] Deployed Code (was: Re: #23: Make crypto
> independent of binary encoding (base64))****
>
>  ****
>
> I think in this case that it is late to bring up binary encoding in Jose*=
*
> **
>
>  ****
>
> But that does not mean we can't add it later. Specs have revisions. All
> that is needed to support binary is a flag to say what was signed. Defaul=
ts
> to the current scheme.****
>
>  ****
>
> Now if it was a case where binary had been raised at the start of the
> process and the person got told to shut up because of 'focus' well that
> would be different. When people pull that trick I have no qualms about
> repeating my concerns in IETF last call. I think that all too often there
> is too much haste when starting a WG and people get railroaded into a
> broken scheme some faction likes. But that did not happen here so I think
> it is going to be for the binary camp to work out the solution. ****
>
>  ****
>
> My bigger Jose concern is the bizarre decision to rename all the crypto
> alg names. I have a spec that uses mime and JSON. If I take Jose seriousl=
y
> I need a second crypto alg registry. ****
>
>  ****
>
> That is junk, that is something that was raised at the start of the
> process. So yes, I will make it an issue in IETF last call
>
> Sent from my difference engine****
>
>  ****
>
>
> On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com> wrote:****
>
>  Seems like many these days are in a rush. They call for consensus before
> discussing the issue. ****
>
>  ****
>
> Isn't it up to the chair?****
>
>  ****
>
> This isn't unique to this WG. ****
>
>  ****
>
> Too many times the explanation for keeping an apparent 'feature/flaw' is
> 'because we don't want change'. Yet often the group can't explain it. Or
> worse, the group just says "we know the emperor has no clothes, we just
> don't feel the need to comment." This is where alarm bells go off for me.
>
> Phil****
>
>
> On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx> wrote:****
>
>  This would have been a nice discussion to have had 18 months ago, when
> we were getting started.****
>
>  ****
>
> I don't think it's compatible with the IETF ethos to say "Changes to this
> document MUST NOT break existing code."  Otherwise, we're not doing
> engineering here, we're cleaning up documentation and rubber-stamping.***=
*
>
>  ****
>
> What would be acceptable is to say "Changes must break cleanly with
> existing code".  That is, it should be possible for a JWT implementation
> to, say, process both "legacy" JWS syntax and whatever comes out of this
> group.  That way, we could come to consensus on the best solution,
> incorporating lessons learned from earlier work without being hindered by
> them.****
>
>  ****
>
> Would participants here consider it a acceptable for the output of this
> working group to be incompatible with existing JWT implementations, as lo=
ng
> as it had the property that JW* objects in the new format could be clearl=
y
> distinguished from "legacy" JW* objects, so that implementations could
> adapt their processing?****
>
>  ****
>
> --Richard****
>
>  ****
>
>  ****
>
>  ****
>
> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com>
> wrote:****
>
> +1
>
> Breaking deployed code as raised by Brian, Naveen and others is a critica=
l
> consideration.
>
> Thanks,
> George****
>
> On 6/13/13 10:19 AM, Mike Jones wrote:****
>
>  Jim and Karen, could you please do as Richard suggests and close this
> issue as =93won=92t fix=94.****
>
>  ****
>
>                                                             Thank you,***=
*
>
>                                                             -- Mike****
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
> *Sent:* Wednesday, June 12, 2013 1:57 PM
> *To:* jose-chairs@tools.ietf.org; Mike Jones
> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
> (base64)****
>
>  ****
>
> In other words: Chairs, feel free to close/wontfix :)****
>
>  ****
>
> ---------- Forwarded message ----------
> From: *Richard Barnes* <rlb@ipv.sx>
> Date: Wed, Jun 12, 2013 at 4:55 PM
> Subject: Re: [jose] #23: Make crypto independent of binary encoding
> (base64)
> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
> jose@ietf.org>" <jose@ietf.org>****
>
> To be clear, I structured my message in two parts for a reason, to
> separate the analysis from the opinion.  I acknowledge that I am but one
> voice here, and I'm increasingly hearing how alone I am :)****
>
>  ****
>
> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:****
>
>  <impartial-analysis>****
>
> So just to be clear on the trade-off the WG has to make:****
>
>  ****
>
> On the one hand: Breaking every existing JWT implementation in the world*=
*
> **
>
> On the other hand: Eternally binding ourselves to base64 encoding, even i=
f
> binary-safe encodings become available (CBOR, MsgPack, etc.)****
>
> </impartial-analysis >****
>
>  ****
>
> <personal-opinion>****
>
> I have some sympathy with JWT implementors.  It sucks to have to refactor
> code.  But I think we're literally talking about something like a 5-line
> patch.  And early JWT implementors knew or should have known (to use a DC
> phrase) that they were dealing with a draft spec.  As the W3C editor's
> draft template says, in big bold red print, "Implementors who are not
> taking part in the discussions are likely to find the specification
> changing out from under them in incompatible ways."****
>
>  ****
>
> As PHB pointed out in the other thread, it would be nice to use JWS and
> JWE in place of CMS one day, without the base64 hit.  We should incur the
> implementation pain now, and get the design right for the long run.  Base=
64
> is a hack around JSON; we should build the system so that when we no long=
er
> need that hack, it can go away.****
>
> </personal-opinion>****
>
>  ****
>
> --Richard****
>
>  ****
>
>  ****
>
>  ****
>
> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
> mamille2@cisco.com> wrote:****
>
> I did at first find it curious why the cryptographic operations were over
> the base64url-enccoded values, but I was also very focused on JWE, where =
I
> think the field separation problem is less of an issue (at least now).  F=
or
> JWS, this would certainly cause problems without some manner of unambiguo=
us
> field parameterization.
>
> I will note that unescaped NULL is not valid in JSON, so it could be used
> as a separator between the encoded header and the payload.  I do find it
> interesting if JOSE could more easily and efficiently support other
> encodings.  However, I think that while this is an interesting thought
> experiment, it seems we're too far down the path to seriously consider it
> unless the current state were shown to be horribly broken.
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.****
>
>
> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
> trac+jose@trac.tools.ietf.org> wrote:
>
> > #23: Make crypto independent of binary encoding (base64)
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> > For both serializations, you already need the base64url encoded version=
s
> > of the JWS Header and the JWS Payload to preserve them in transmission,
> so
> > computing them isn't an extra burden.  In the JWS Compact Serialization=
,
> > you already need the concatenation of the Encoded JWS Header, a period
> > character, and the Encoded JWS Payload, so computing that concatenation
> > isn't an extra burden.  Given you already have that quantity, computing
> > the signature over it is the easiest thing for developers to do, and it=
's
> > been shown to work well in practice.  There's no compelling reason to
> make
> > this change.
> >
> > Even for the JSON Serialization, the only "extra" step that's required =
to
> > compute the signature is the concatenation with the period character - =
to
> > prevent shifting of data from one field to the other, as described by J=
im
> > Schaad in the e-mail thread.  So this step isn't actually "extra" at al=
l
> -
> > it's necessary.  It's also highly advantageous to use exactly the same
> > computation for both serializations, which is currently the case.
> >
> > Since there is no compelling reason to make this change, and since maki=
ng
> > it could enable the "shifting" problem identified by Jim, it should not
> be
> > made.
> >
> > --
> >
> -------------------------+-----------------------------------------------=
--
> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
> >     Type:  defect       |  encryption@tools.ietf.org
> > Priority:  major        |      Status:  new
> > Component:  json-web-    |   Milestone:
> >  encryption             |     Version:
> > Severity:  -            |  Resolution:
> > Keywords:               |
> >
> -------------------------+-----------------------------------------------=
--
> >
> > Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:=
2
> >
> > jose <http://tools.ietf.org/jose/>
> >****
>
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
>    ****
>
>  ****
>
> ** **
>
> _______________________________________________****
>
> jose mailing list****
>
> jose@ietf.org****
>
> https://www.ietf.org/mailman/listinfo/jose****
>
>   ****
>
> --
> <XeC> <http://connect.me/gffletch>****
>
>  ****
>
>  _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>   _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>


--=20
Website: http://hallambaker.com/

--001a11c2228cd482e104df36d6f0
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>The name fields in the following originate from=
 PEM:</div><div><a href=3D"http://www.iana.org/assignments/dssc/dssc.xml">h=
ttp://www.iana.org/assignments/dssc/dssc.xml</a><br></div><div><br></div><d=
iv style>
The same code points are used in HTTP Digest</div><div style><a href=3D"htt=
p://www.iana.org/assignments/http-dig-alg/http-dig-alg.xml">http://www.iana=
.org/assignments/http-dig-alg/http-dig-alg.xml</a><br></div><div style><br>
</div><div style>SSH uses the same code points again and defines HMAC code =
points:</div><div style><a href=3D"http://www.iana.org/assignments/ssh-para=
meters/ssh-parameters.xml#ssh-parameters-18">http://www.iana.org/assignment=
s/ssh-parameters/ssh-parameters.xml#ssh-parameters-18</a><br>
</div><div style><br></div><div style><br></div><div style>I don&#39;t thin=
k that when you are using base64 for encoding you can really make an issue =
of the difference between=A0<span style=3D"color:rgb(0,0,0);font-family:san=
s-serif;font-size:13px">hmac-sha2-256 and hs256 as being serious enough to =
justify a whole new registry and a whole different set of encodings.</span>=
</div>
<div style><span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size=
:13px"><br></span></div><div style><span style=3D"color:rgb(0,0,0);font-fam=
ily:sans-serif;font-size:13px">The JWA algorithm should instead update the =
DSSC registry which was originally conceived as being a single registry and=
 point of contact for all crypto algorithms and canonical identifiers for a=
ll protocols that do not use protocol specific code points (like IPSEC, DNS=
SEC).</span></div>
<div style><span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size=
:13px"><br></span></div><div style><span style=3D"color:rgb(0,0,0);font-fam=
ily:sans-serif;font-size:13px"><br></span></div><div style><span style=3D"c=
olor:rgb(0,0,0);font-family:sans-serif;font-size:13px">Setting up registrie=
s is easy. Maintaining them is not.</span></div>
<div style><span style=3D"color:rgb(0,0,0);font-family:sans-serif;font-size=
:13px"><br></span></div><div style><br></div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Fri, Jun 14, 2013 at 7:59 PM, Mike=
 Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com"=
 target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">What alternative registry=
 of algorithm names were you thinking of?=A0 Are you suggesting that we use=
 the OID numbers used by CMS?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">As far as I know, there i=
s no MIME registry of cryptographic algorithm names, so I don=92t think the=
re=92s any conflict/duplication there.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [mailto:<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">=
hallam@gmail.com</a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 4:56 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Phil Hunt; Richard Barnes; <a href=3D"mailto:jose-chairs@tools.i=
etf.org" target=3D"_blank">jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"m=
ailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&gt;; George Fletch=
er</span></p>
<div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">So is the idea that a standards organization should =
seek consistency<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I understand the WG rationale. I reject it as a suff=
icient IETF rationale. If it stands it is going to require two parallel reg=
istries for the same algs.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have a spec that crosses HTTP and JSON. Am I suppo=
sed to use mime registry in one and this duplicate scheme in the other?<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Blocking that type of move is what IETF last call is=
 for. There is a negligible benefit in the spec and a huge cost to the comm=
unity.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
Sent from my differenc engine<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 14, 2013, at 5:53 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones=
@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote=
:<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Short names were chosen b=
ecause of the core compactness requirement for the Compact Serialization.=
=A0 That was an engineering decision that was consciously made
 and for which the rationale is clear.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">You can disagree with tha=
t decision but it has known clear benefits and is far from arbitrary.</span=
><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">mailto:=
hallam@gmail.com</a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 2:49 PM<br>
<b>To:</b> Phil Hunt<br>
<b>Cc:</b> Richard Barnes; Mike Jones; <a href=3D"mailto:jose-chairs@tools.=
ietf.org" target=3D"_blank">
jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I think in this case that it is late to bring up bin=
ary encoding in Jose<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But that does not mean we can&#39;t add it later. Sp=
ecs have revisions. All that is needed to support binary is a flag to say w=
hat was signed. Defaults to the current scheme.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now if it was a case where binary had been raised at=
 the start of the process and the person got told to shut up because of &#3=
9;focus&#39; well that would be different. When people pull that trick I ha=
ve no qualms about repeating my concerns in
 IETF last call. I think that all too often there is too much haste when st=
arting a WG and people get railroaded into a broken scheme some faction lik=
es. But that did not happen here so I think it is going to be for the binar=
y camp to work out the solution.=A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">My bigger Jose concern is the bizarre decision to re=
name all the crypto alg names. I have a spec that uses mime and JSON. If I =
take Jose seriously I need a second crypto alg registry.=A0<u></u><u></u></=
p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That is junk, that is something that was raised at t=
he start of the process. So yes, I will make it an issue in IETF last call<=
br>
<br>
Sent from my difference engine<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 13, 2013, at 12:06 PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@ora=
cle.com" target=3D"_blank">phil.hunt@oracle.com</a>&gt; wrote:<u></u><u></u=
></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Seems like many these days are in a rush. They call =
for consensus before discussing the issue.=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Isn&#39;t it up to the chair?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This isn&#39;t unique to this WG.=A0<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Too many times the explanation for keeping an appare=
nt &#39;feature/flaw&#39; is &#39;because we don&#39;t want change&#39;. Ye=
t often the group can&#39;t explain it. Or worse, the group just says &quot=
;we know the emperor has no clothes, we just don&#39;t feel the need
 to comment.&quot; This is where alarm bells go off for me.=A0<br>
<br>
Phil<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" ta=
rget=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I don&#39;t think it&#39;s compatible with the IETF =
ethos to say &quot;Changes to this document MUST NOT break existing code.&q=
uot; =A0Otherwise, we&#39;re not doing engineering here, we&#39;re cleaning=
 up documentation and rubber-stamping.<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. =A0That is, it should be possible=
 for a JWT implementation to, say, process both &quot;legacy&quot; JWS synt=
ax and whatever comes out of this group. =A0That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">+1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span><u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:<u></u><u></u>=
</p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim and Karen, could you =
please do as Richard suggests and close this issue as =93won=92t fix=94.</s=
pan><u></u><u></u></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 Thank you,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span><u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">In other words: Chairs, feel free to close/wontfix :=
)<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------- Forwarded =
message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<a hr=
ef=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=3D"=
_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">To be clear, I structured my message in two parts fo=
r a reason, to separate the analysis from the opinion. =A0I acknowledge tha=
t I am but one voice here, and I&#39;m increasingly hearing how alone I am =
:)<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">&lt;impartial-analysis&gt;<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">So just to be clear on the trade-off the WG has to m=
ake:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On the one hand: Breaking every existing JWT impleme=
ntation in the world<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On the other hand: Eternally binding ourselves to ba=
se64 encoding, even if binary-safe encodings become available (CBOR, MsgPac=
k, etc.)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/impartial-analysis=A0&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;personal-opinion&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have some sympathy with JWT implementors. =A0It su=
cks to have to refactor code. =A0But I think we&#39;re literally talking ab=
out something like a 5-line patch. =A0And early JWT implementors knew or sh=
ould have known (to use a DC phrase) that they
 were dealing with a draft spec. =A0As the W3C editor&#39;s draft template =
says, in big bold red print, &quot;Implementors who are not taking part in =
the discussions are likely to find the specification changing out from unde=
r them in incompatible ways.&quot;<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. =
=A0We should incur the implementation pain now, and get the design right fo=
r the long run. =A0Base64 is a hack around
 JSON; we should build the system so that when we no longer need that hack,=
 it can go away.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/personal-opinion&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard</span><u></u=
><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@c=
isco.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">I did at first find it curious why the cryptographic=
 operations were over the base64url-enccoded values, but I was also very fo=
cused on JWE, where I think the field separation problem is less of an issu=
e (at least now). =A0For JWS, this would
 certainly cause problems without some manner of unambiguous field paramete=
rization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this
 is an interesting thought experiment, it seems we&#39;re too far down the =
path to seriously consider it unless the current state were shown to be hor=
ribly broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.s=
x</a> =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-json-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>jose mailing list<u></u><u></u></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><u=
></u><u></u></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></pre>
</blockquote>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank">&lt;XeC&gt;</a></span><u></u><u></u><=
/p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
</div></div></div>
</div>

</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--001a11c2228cd482e104df36d6f0--

From ietf@augustcellars.com  Sat Jun 15 13:14:34 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E941321F9D14 for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 13:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=0.930,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmP27TMK9pw0 for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 13:14:28 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC1D21F9CD6 for <jose@ietf.org>; Sat, 15 Jun 2013 13:14:28 -0700 (PDT)
Received: from Philemon (173-160-230-154-Washington.hfc.comcastbusiness.net [173.160.230.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id AF34E2C9F2; Sat, 15 Jun 2013 13:14:27 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-json-signature@tools.ietf.org>
Date: Sat, 15 Jun 2013 13:13:34 -0700
Message-ID: <00f901ce6a04$d0e7d1f0$72b775d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5nqFuZTYR8wZ0pRs+tqSZ/RDYb+w==
Cc: jose@ietf.org
Subject: [jose] Comments on the web signature draft version 11
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 15 Jun 2013 20:14:34 -0000

1.   Going from the string to the UTF8 encoding followed by the base64
encoding in section 3.1 is difficult given that it is not really possible to
figure out where the spaces, returns and new-lines are.   It would be easier
if you included the half-way step or better yet make the header be a single
line.

2.  In section 3.1 rather than saying you are using ASCII, it might be
better to omit the character set entirely.  IMHO, having ASCII in there
confuses the issue rather than clarifies it.

3.  In section 3.1  s/Header.Payload.Signature/Header, Payload, Signature/
you are listing the items and the 'with' clause describes how to put in the
separation character.

4.  In section 4 para #1 - I am having an issue with the first sentence.
	a) Using "object(s)" to describe the possible hierarchy is messy as
it might be possible to interpret this as interdependent rather than nested.

	b) 'optionally additional properties' is difficult for me to parse.
I think that "and, optionally, additional properties" would be better

5.  In section 4 para #2 - Two items, this does not talk about header
parameter not defined in this document and I think it might be more
understandable if this was done as a series of bullet points rather than
just text.

6.  In section 4.1.1 - I think the current text for rejection on alg is
written on the assumption that there is only one signature/MAC on the
object.  If there are two and there is both an implementation and a key for
one signature but the second either does not have an implementation or a key
- is this still a MUST reject situation?

7.  In section 4.1.2 - Are you going to impose a minimum version TLS -
specifically are SSL and TLS v1.0 allowed?

8.  In section 4.1.2 - Is implementation of this parameter required?

9.  In section 4.1.3 - see comment 8

10.  In section 4.1.3 - Should we make a note that the private portions of a
key MUST NOT be included?

11.  In section 4.1.4 - Other than consistency - what is the requirement
here for doing HTTPS - are you expecting self-signed certificates to be
common and trying to get around trust anchor issues?

12. In section 4.1.4 - see comment 8  -- ok - and lots of other sections

13.  In section 4.1.6 - There is a verification statement on X.509
certificates.  There is not a similar statement for x5t or x5u.  Should
there be?

14. In section 4.1.9 - This section gives why I thought that JWT was a cty
value.  It explicitly says so.  Mike has said this is not true.

15.  In section 4.1.9 - The last paragraph states that ctyp and typ values
come from the same values space.  Mike has said this is not true.

16. In section 4.1.10 - I think there is an interesting discussion point on
the use of 'crit' in the following case.  I want to ensure that you
implement a feature in the base specification that the base specification
has said you do not need to implement.  I am not sure based on the current
document language if this is an empty set or not.

17.  In section 5.1 step 3 - I don't know if there is a reason to make a
statement about suggesting that whitespace be removed when you are planning
on doing a compact representation.  This is one of those things that would
lead to a smaller encoding.

18.  In section 5.1, step 4 - the phrase "If the JWS protected header is not
present..." leaves me lost.  I don't understand what this term is coming
from as you have not yet introduced it in terms of how to build a signed
message.  Specifically, there has been nothing at this point which tells me
how to decide what goes where.  I strongly feel that section 8 needs to move
before this section.

19.  In section 5.1, Step 11 - I think this should be moved forward to say -
repeat the steps X to Y for each signature to be processed.  I also don't
think this needs to say anything about the serialization method being used.
It is not relevant.

20.  In section 5.1, step 5 - the last sentence in this step would appear to
be out of place.  This is not a requirement of computing the signature, but
one of building the JWS header which is step 2.  This MUST is just a
re-iteration of one someplace else so it does not add anything.

21. In section 5.1, step 9 - I believe that the compact serialization should
be moved to its own section.  There should not be any apparent preference in
the document for one of the serialization methods.

22. In Section 5 - I am going to make a suggestion that I would like you to
consider, although I think that it might not be to your liking.  My personal
view of the world has been one of: There is a JSON serialization that is the
object.  There is a way to map from the JSON serialization to the compact
serialization.  The mapping requires a set of constraints on the original
serialization.  Thus in my world, I build the internal JSON object
representation, run the computations on that internal representation and
then either run the mapping to the compact serialization or serialize the
JSON object representation to get the output.  Using this as the method
would mean that section 5 would be an object representation for JSON,
section 6 would be how to do the mappings to and from the compact form,
section 7 would be the how to do this.

23.  In section 5.3 - Are steps #1 and #2 not the requirement of the JSON
parser and not my application?  I would suggest reading some of the updated
text on member name string comparison from the JSON mailing list for a
cleaner way to write this section.

24.  Section 6 appears to be extraneous and could be deleted.  What is the
purpose that this is supposed to serve?  Why is that purpose not covered in
the description of the alg member?

25.  Section 7 would appear to be better served by making it section 4.1.2
and making section on jku, jwk, x5u, x5t, x5c and kid as subjections of it.

26.  Section 8 - I found the presentation confusing.  I would have expected
that it would be made in the normal manner - that is you have an object and
a list of members each with its own section - and those members may have sub
members which are listed.  There would then be references back to the
members defined in section 4

27.  Section 9 - I would dispute the content of this section vigorously.

I stopped reviewing after section 9.

Jim



From ietf@augustcellars.com  Sat Jun 15 14:09:01 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB8F21F9D17 for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 14:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level: 
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8UqXQ+EfuVZi for <jose@ietfa.amsl.com>; Sat, 15 Jun 2013 14:08:55 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id ADA5321F9C0F for <jose@ietf.org>; Sat, 15 Jun 2013 14:08:55 -0700 (PDT)
Received: from Philemon (173-160-230-154-Washington.hfc.comcastbusiness.net [173.160.230.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 7913D38EF7; Sat, 15 Jun 2013 14:08:55 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-json-web-encryption@tools.ietf.org>
Date: Sat, 15 Jun 2013 14:08:02 -0700
Message-ID: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5qBROwQiVllCE1TESnJHctXErySQ==
Cc: jose@ietf.org
Subject: [jose] Comments on version 11 of draft-ietf-jose-json-web-encryption
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 15 Jun 2013 21:09:01 -0000

Gentlemen,

Here are a few comments for consideration.  Note that some of the comments
from the JWS review are also applicable to this document as much of the
language in places is the same.

1.  In Section 4.1.2 - You probably want to say an AEAD algorithm not an AE
algorithm

2  In section 4.1.3 - I would suggest changing the text to "This parameter
MUST be omitted unless required by the algorithm in the "alg" member.  This
header parameter MUST be understood if an algorithm is supported that
requires it."

3.  In section 4.1.4 - Does the group agree that compression is a required
feature to implement?

4.  Why not reference sections 4.1.5 - 10 by reference with a comment that
these refer to the key that was used to encrypt the content?  Is there a
benefit of having them listed here?  Is there a difference in the way they
are interpreted other than the recipient/originator thing?

5.  Why not reference sections 4.1.11-12 from the JWS document?  Is there a
difference in the way they are interpreted?

6.  If we are not going with an alphabetic order of names, the I would
suggest that apu should be next to exp as they are used in the same context
and therefore having them adjacent makes sense.

7.  Is there a reason not to reference 4.1.14 from JWS?  Is there a
difference in interpretation?

Jim



From James.H.Manger@team.telstra.com  Sun Jun 16 18:20:41 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF01921F9B66 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 18:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level: 
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[AWL=-0.498,  BAYES_05=-1.11, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRWIpR24Ej63 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 18:20:35 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 7449421F9B63 for <jose@ietf.org>; Sun, 16 Jun 2013 18:20:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,877,1363093200"; d="scan'208";a="142865964"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipoani.tcif.telstra.com.au with ESMTP; 17 Jun 2013 11:20:26 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7108"; a="145157199"
Received: from wsmsg3753.srv.dir.telstra.com ([172.49.40.174]) by ipccni.tcif.telstra.com.au with ESMTP; 17 Jun 2013 11:20:26 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3753.srv.dir.telstra.com ([172.49.40.174]) with mapi; Mon, 17 Jun 2013 11:20:26 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "jose@ietf.org" <jose@ietf.org>
Date: Mon, 17 Jun 2013 11:20:25 +1000
Thread-Topic: Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQ==
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 01:20:42 -0000

VGhlIHVzZSBvZiB0aGUgQ29uY2F0IEtERiBzdGlsbCBkb2VzIG5vdCBsb29rIHJpZ2h0Lg0KDQpK
V0EgW2RyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1hbGdvcml0aG1zLTExXSBzZWN0aW9uIDQuNyBz
YXlzICJFQ0RILUVTIiB1c2VzIENvbmNhdCBLREYgZnJvbSBOSVNUIDgwMC01NkEgc2VjdGlvbiA1
LjguMS4gTklTVCBkZWZpbmVzIDUgZmllbGRzIHRoYXQgZ28gaW50byB0aGUga2V5IGRlcml2YXRp
b246IEFsZ29yaXRobUlELCBQYXJ0eVVJbmZvLCBQYXJ0eVZJbmZvLCBTdXBwUHViSW5mbywgYW5k
IFN1cHBQcml2SW5mby4NCg0KTklTVCBzYXlzIEFsZ29yaXRobUlEIGluZGljYXRlcyB0aGUgYWxn
b3JpdGhtIHRoYXQgd2lsbCB1c2UgdGhlIGRlcml2ZWQga2V5LiBKV0Egc2F5cyB0byB1c2UgdGhl
ICJhbGciIHZhbHVlIChlZyAiRUNESC1FUyIpIGFzIHRoZSBBbGdvcml0aG1JRC4gQWxnb3JpdGht
SUQgc2hvdWxkIGFjdHVhbGx5IGJlIHRoZSAiZW5jIiB2YWx1ZSB3aGVuIHRoZSBkZXJpdmVkIGtl
eSBpcyB1c2VkIGRpcmVjdGx5IGFzIGEgQ0VLLiBXaGVuIHRoZSBkZXJpdmVkIGtleSB1bndyYXBz
IHRoZSBDRUssIEFsZ29yaXRobUlEIHNob3VsZCBiZSB0aGUgbmFtZSBvZiB0aGUga2V5IHdyYXAg
YWxnb3JpdGhtIChlZyAiQTEyOEtXIikuIFBlcmhhcHMgdGhlICJhbGciIHZhbHVlIGNhbiBiZSB1
c2VkIGluIHRoaXMgY2FzZSBhcyBpdCBpZGVudGlmaWVzIHRoZSBrZXkgd3JhcCBhbGdvcml0aG0g
YWxvbmcgd2l0aCB0aGUga2V5IGVzdGFibGlzaG1lbnQgYWxnb3JpdGhtIChlZyAiRUNESC1FUytB
MTI4S1ciKS4NCg0KTklTVCBzYXlzIFBhcnR5VUluZm8gaW5jbHVkZXMgYW4gaWRlbnRpZmllciBm
b3IgcGFydHkgVS4gVGhlIGZpcnN0IHByb2JsZW0gaXMgdGhhdCBKV0EgZG9lcyBub3QgaW5kaWNh
dGUgaWYgdGhlIHNlbmRlciBvciByZWNlaXZlciBpcyBwYXJ0eSBVIChub3IgZG9lcyBKV0UpLiBU
aGUgc2Vjb25kIHByb2JsZW0gaXMgdGhhdCBKV0Egc2F5cyBQYXJ0eVVJbmZvIGlzIHJhbmRvbSAt
LSB3aGljaCBzZWVtcyB0byB0b3RhbGx5IGRlZmVhdCB0aGUgcHVycG9zZSBvZiBiZWluZyBhbiBp
ZGVudGlmaWVyIGZvciBhIHBhcnR5LiBKV0Egc2F5cyBQYXJ0eVVJbmZvIHNob3VsZCB2YXJ5IGZv
ciBlYWNoIHJlY2lwaWVudCwgd2hpY2ggc3VnZ2VzdHMgUGFydHlVSW5mbyBjYW5ub3QgYmUgYW4g
aWQgb2YgdGhlIHNlbmRlci4gRG9lcyB0aGF0IHN1Z2dlc3QgdGhlIHJlY2VpdmVyIGlzIHBhcnR5
IFU/DQoNCk5JU1Qgc2F5cyBQYXJ0eVZJbmZvIGlzIHJlcXVpcmVkIGFuZCBpbmNsdWRlcyBhbiBp
ZGVudGlmaWVyIGZvciBwYXJ0eSBWLiBKV0Egc2F5cyBQYXJ0eVZJbmZvIGlzIGVtcHR5LCB3aGlj
aCBvYnZpb3VzbHkgY2Fubm90IG1lZXQgdGhlIE5JU1QgZGVmaW5pdGlvbi4NCg0KVGhlIEpXQSB2
YWx1ZXMgZm9yIFN1cHBQdWJJbmZvIChsZW5ndGggb2YgZGVyaXZlZCBrZXkgaW4gYml0cykgYW5k
IFN1cHBQcml2SW5mbyAoZW1wdHkpIGFyZSBpbiBsaW5lIHdpdGggdGhlIE5JU1QgZGVmaW5pdGlv
bnMuDQoNCg0KSXQgYXBwZWFycyB0aGUgQ29uY2F0IEtERiB0ZXh0IGluIEpXQSBoYXMgYmVlbiBy
ZXdyaXR0ZW4gYmFzZWQgb24gUkZDMjYzMSAiRGlmZmllLUhlbGxtYW4gS2V5IEFncmVlbWVudCBN
ZXRob2QiLiBSRkMyNjMxIGlzIG5vdCByZWZlcmVuY2VkIGJ5IEpXQSwgYnV0IGl0IGlzIG1lbnRp
b25lZCBpbiB0aGUgImRvY3VtZW50IGhpc3RvcnkiIHNlY3Rpb24gKHdoaWNoIHdpbGwgZXZlbnR1
YWxseSBiZSBkZWxldGVkKS4gUkZDMjYzMSBoYXMgaXRlbXMgc3VjaCBhcyBwYXJ0eUFJbmZvIGFu
ZCBzdXBwUHViSW5mbyB3aG9zZSBuYW1lcyBhcmUgc2ltaWxhciB0byBOSVNUIGl0ZW1zLiBIb3dl
dmVyLCBSRkMyNjMxIHdhcyBwdWJsaXNoZWQgNyB5ZWFycyBiZWZvcmUgTklTVCA4MDAtNTZBIChh
bmQgMTMgeWVhcnMgYmVmb3JlIHRoZSBjdXJyZW50IHZlcnNpb24gb2YgTklTVCA4MDAtNTZBKSBz
byBSRkMyNjMxIGNhbm5vdCBiZSB1c2VkIGFzIGEgZXhhbXBsZSBvZiBob3cgdG8gdXNlIENvbmNh
dCBLREYuDQoNCi0tDQpKYW1lcyBNYW5nZXINCg==

From trac+jose@trac.tools.ietf.org  Sun Jun 16 19:37:22 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C078921F9DA6 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 19:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9c5xi1SVlDA for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 19:37:22 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 3081821F9DA3 for <jose@ietf.org>; Sun, 16 Jun 2013 19:37:21 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49708 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UoPJe-0006vm-U2; Mon, 17 Jun 2013 04:37:10 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, sakimura@gmail.com, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Mon, 17 Jun 2013 02:37:10 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/4#comment:7
Message-ID: <069.cf56b3ec347df6c15ca8274b2faa26e7@trac.tools.ietf.org>
References: <054.24cd2b074db2dc2bbbcb828a8456fbe9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 4
In-Reply-To: <054.24cd2b074db2dc2bbbcb828a8456fbe9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, sakimura@gmail.com, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130617023722.3081821F9DA3@ietfa.amsl.com>
Resent-Date: Sun, 16 Jun 2013 19:37:21 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #4: Remove wrapped keys from integrity check (allow separation of keys from data)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 02:37:22 -0000

#4: Remove wrapped keys from integrity check (allow separation of keys from
data)

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Review of -11 shows this to be done.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:  fixed
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/4#comment:7>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Sun Jun 16 19:50:32 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8D521F9D00 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 19:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGiePwWbcEx1 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 19:50:31 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 851C521F9C59 for <jose@ietf.org>; Sun, 16 Jun 2013 19:50:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:50503 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UoPWM-0002hv-Um; Mon, 17 Jun 2013 04:50:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Mon, 17 Jun 2013 02:50:18 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/11#comment:3
Message-ID: <069.23eda0491874df8321f23deae16d4a02@trac.tools.ietf.org>
References: <054.e72d4c43dc02c0b9f61660ef223433e1@trac.tools.ietf.org>
X-Trac-Ticket-ID: 11
In-Reply-To: <054.e72d4c43dc02c0b9f61660ef223433e1@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130617025028.851C521F9C59@ietfa.amsl.com>
Resent-Date: Sun, 16 Jun 2013 19:50:28 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #11: Use RFC 5116 and remove MAC field
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 02:50:33 -0000

#11: Use RFC 5116 and remove MAC field

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 The WG as a whole has determined that it wants to stay with the current
 separate fields for the use of AEAD algorithms for doing content
 encryption.  This means that there is no desire to adopt this as the
 future path.

 The issue may be raised in respect to using AEAD algorithms for key
 wrapping.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:  wontfix
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/11#comment:3>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Sun Jun 16 20:09:30 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7E621F9DE4 for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 20:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 093M4-BnSMop for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 20:09:29 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 79C0A21F9DE3 for <jose@ietf.org>; Sun, 16 Jun 2013 20:09:28 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52585 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UoPol-0006XL-5h; Mon, 17 Jun 2013 05:09:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Mon, 17 Jun 2013 03:09:19 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:3
Message-ID: <064.576c20d6cc86048b30a118ed43eb62b8@trac.tools.ietf.org>
References: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-Trac-Ticket-ID: 23
In-Reply-To: <049.69ffc5ebf959c6eac7990651822fadf9@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130617030929.79C0A21F9DE3@ietfa.amsl.com>
Resent-Date: Sun, 16 Jun 2013 20:09:28 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 03:09:30 -0000

#23: Make crypto independent of binary encoding (base64)

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => wontfix


-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |      Status:  closed
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:  wontfix
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:3>
jose <http://tools.ietf.org/jose/>


From ietf@augustcellars.com  Sun Jun 16 21:50:34 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC0FD21F96EF for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 21:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLFLuNb--PRC for <jose@ietfa.amsl.com>; Sun, 16 Jun 2013 21:50:29 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0894221F9476 for <jose@ietf.org>; Sun, 16 Jun 2013 21:50:28 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id C24882CA0A for <jose@ietf.org>; Sun, 16 Jun 2013 21:50:21 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Sun, 16 Jun 2013 21:49:27 -0700
Message-ID: <01a401ce6b16$0ca733e0$25f59ba0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A5_01CE6ADB.6049BB70"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5rA4sfPF0KagEuQuyZA1GuBdT2RQ==
Subject: [jose] Current Open Issues List
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 04:50:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01A5_01CE6ADB.6049BB70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<chair>

 

The following represents my current thinking on getting the issues in the
tracker closed.

 

Issue #5 - Not active -- Needs verification that it should be closed by
Richard and chairs

Issue #6 - Active - Blocked on Richard - need evaluation table

Issue #7 - Not active - chairs are monitoring

Issue #8 - Active - On the agenda for tomorrow

Issue #13 - Active - currently gated on the chairs to finish review of
proposals.

Issue #14 - Active - currently blocked on issue #13

Issue #15 - Active - 

Issue #18 - Active - Blocked on Authors - need updated text

Issue #20 - Active - on the agenda for tomorrow

Issue #21 - Active - on the agenda for tomorrow

Issue #22 - Active - on the agenda for tomorrow

Issue #24 - Active - On the agenda for tomorrow

 

Jim

 


------=_NextPart_000_01A5_01CE6ADB.6049BB70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>&lt;chair&gt;<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The =
following represents my current thinking on getting the issues in the =
tracker closed.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Issue #5 =
&#8211; Not active -- Needs verification that it should be closed by =
Richard and chairs<o:p></o:p></p><p class=3DMsoNormal>Issue #6 &#8211; =
Active &#8211; Blocked on Richard &#8211; need evaluation =
table<o:p></o:p></p><p class=3DMsoNormal>Issue #7 &#8211; Not active =
&#8211; chairs are monitoring<o:p></o:p></p><p class=3DMsoNormal>Issue =
#8 &#8211; Active &#8211; On the agenda for tomorrow<o:p></o:p></p><p =
class=3DMsoNormal>Issue #13 &#8211; Active &#8211; currently gated on =
the chairs to finish review of proposals.<o:p></o:p></p><p =
class=3DMsoNormal>Issue #14 &#8211; Active &#8211; currently blocked on =
issue #13<o:p></o:p></p><p class=3DMsoNormal>Issue #15 &#8211; Active - =
<o:p></o:p></p><p class=3DMsoNormal>Issue #18 &#8211; Active &#8211; =
Blocked on Authors &#8211; need updated text<o:p></o:p></p><p =
class=3DMsoNormal>Issue #20 &#8211; Active &#8211; on the agenda for =
tomorrow<o:p></o:p></p><p class=3DMsoNormal>Issue #21 &#8211; Active =
&#8211; on the agenda for tomorrow<o:p></o:p></p><p =
class=3DMsoNormal>Issue #22 &#8211; Active &#8211; on the agenda for =
tomorrow<o:p></o:p></p><p class=3DMsoNormal>Issue #24 &#8211; Active =
&#8211; On the agenda for tomorrow<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01A5_01CE6ADB.6049BB70--


From prateek.mishra@oracle.com  Mon Jun 17 07:14:06 2013
Return-Path: <prateek.mishra@oracle.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305C421F9C32 for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 07:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXiKfN6lYNex for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 07:14:00 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 704B121F9CA4 for <jose@ietf.org>; Mon, 17 Jun 2013 07:13:59 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r5HEDWuc014813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 17 Jun 2013 14:13:33 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5HEDXw4019769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jun 2013 14:13:34 GMT
Received: from abhmt110.oracle.com (abhmt110.oracle.com [141.146.116.62]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5HEDX8B020185; Mon, 17 Jun 2013 14:13:33 GMT
Received: from [192.168.2.5] (/24.91.51.58) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 17 Jun 2013 07:13:33 -0700
Message-ID: <51BF1990.8030003@oracle.com>
Date: Mon, 17 Jun 2013 10:13:36 -0400
From: Prateek Mishra <prateek.mishra@oracle.com>
Organization: Oracle Corporation
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jim Schaad <ietf@augustcellars.com>
References: <071f01ce6655$42a620c0$c7f26240$@augustcellars.com>
In-Reply-To: <071f01ce6655$42a620c0$c7f26240$@augustcellars.com>
Content-Type: multipart/alternative; boundary="------------010006060609020106040309"
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: jose@ietf.org
Subject: Re: [jose] Interium Meeting Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 14:14:06 -0000

This is a multi-part message in MIME format.
--------------010006060609020106040309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Is there a scheduled time and phone number for this meeting?

Thanks,
prateek

> <chair>
>
> Preliminary agenda for next week's teleconference has been posted
>
> http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-interim-2013-jose-2
>
> jim
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------010006060609020106040309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Is there a scheduled time and phone number for this meeting?<br>
    <br>
    Thanks,<br>
    prateek<br>
    <div class="moz-cite-prefix"><br>
    </div>
    <blockquote
      cite="mid:071f01ce6655$42a620c0$c7f26240$@augustcellars.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">&lt;chair&gt;<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Preliminary agenda for next week&#8217;s
          teleconference has been posted<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><a moz-do-not-send="true"
href="http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-interim-2013-jose-2">http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-interim-2013-jose-2</a><o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">jim<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010006060609020106040309--

From Michael.Jones@microsoft.com  Mon Jun 17 08:41:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CA721F9CA2 for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 08:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58WxVVnjhLpN for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 08:41:19 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id B511521F9CA6 for <jose@ietf.org>; Mon, 17 Jun 2013 08:41:13 -0700 (PDT)
Received: from BN1BFFO11FD015.protection.gbl (10.58.52.204) by BN1AFFO11HUB001.protection.gbl (10.58.52.111) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 17 Jun 2013 14:55:48 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD015.mail.protection.outlook.com (10.58.53.75) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 17 Jun 2013 14:55:48 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Mon, 17 Jun 2013 14:55:20 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Prateek Mishra <prateek.mishra@oracle.com>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] Interium Meeting Agenda
Thread-Index: Ac5mVS5ztk0JFTUTTRisGqqoBKmpDwFD6zQAAAFgQuA=
Date: Mon, 17 Jun 2013 14:55:20 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678692C4@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <071f01ce6655$42a620c0$c7f26240$@augustcellars.com> <51BF1990.8030003@oracle.com>
In-Reply-To: <51BF1990.8030003@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.33]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678692C4TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(22804002)(377454002)(164054003)(189002)(15594002)(31966008)(74366001)(76786001)(81342001)(54356001)(53806001)(47736001)(69226001)(59766001)(74706001)(66066001)(512954002)(33656001)(71186001)(16601075002)(80022001)(54316002)(551544002)(65816001)(16799955001)(79102001)(16406001)(63696002)(74876001)(15202345002)(74662001)(47446002)(51856001)(49866001)(20776003)(56776001)(56816003)(76796001)(77982001)(55846006)(16236675002)(74502001)(77096001)(6806003)(76482001)(50986001)(81542001)(47976001)(46102001)(4396001)(563064006); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB001; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0880FB6EC1
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Interium Meeting Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 15:41:25 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678692C4TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The WebEx information that Karen sent on the 10th follows.  The call is two=
 hours from now.

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Kar=
en O'Donoghue
Sent: Monday, June 10, 2013 9:20 AM
To: jose@ietf.org
Subject: [jose] webex information for JOSE teleconference: 17 June 2013 @ 1=
:00 pm EDT

Folks,

Here is the webex information for the call next Monday.

Karen

Cindy Morgan invites you to attend this online meeting.

Topic: JOSE
Date: Monday, June 17, 2013
Time: 11:00 am, Mountain Daylight Time (Denver, GMT-06:00)
Meeting Number: 648 447 409
Meeting Password: 1234


-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to https://ietf.webex.com/ietf/j.php?ED=3D225472827&UID=3D1566381972&=
PW=3DNOWQ4YWY3NDc1&RT=3DMiM2
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 1234
4. Click "Join".

To view in other time zones or languages, please click the link:
https://ietf.webex.com/ietf/j.php?ED=3D225472827&UID=3D1566381972&PW=3DNOWQ=
4YWY3NDc1&ORT=3DMiM2

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
Call-in toll number (US/Canada): 1-650-479-3208

Access code:648 447 409

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://ietf.webex.com/ietf/mc
2. On the left navigation bar, click "Support".

You can contact me at:
cmorgan@amsl.com<mailto:cmorgan@amsl.com>
1-510-492-4085

To add this meeting to your calendar program (for example Microsoft Outlook=
), click this link:
https://ietf.webex.com/ietf/j.php?ED=3D225472827&UID=3D1566381972&ICS=3DMI&=
LD=3D1&RD=3D2&ST=3D1&SHA2=3DAAAAAnBS0dxwb5o23cp6D4NhhtUFgQ0Ft4xS6lHRlHHZAwF=
T&RT=3DMiM2

The playback of UCF (Universal Communications Format) rich media files requ=
ires appropriate players. To view this type of rich media files in the meet=
ing, please check whether you have the players installed on your computer b=
y going to https://ietf.webex.com/ietf/systemdiagnosis.php.

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+16504793208x648447409#

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent to the recording, discuss your concerns =
with the meeting host prior to the start of the recording or do not join th=
e session. Please note that any such recordings may be subject to discovery=
 in the event of litigation.



From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Pra=
teek Mishra
Sent: Monday, June 17, 2013 7:14 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Interium Meeting Agenda

Is there a scheduled time and phone number for this meeting?

Thanks,
prateek

<chair>

Preliminary agenda for next week's teleconference has been posted

http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-inter=
im-2013-jose-2

jim





_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B1680429673943678692C4TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The WebEx information =
that Karen sent on the 10<sup>th</sup> follows.&nbsp; The call is two hours=
 from now.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> jose-bounces@ietf.org [mailto:jose-bounces@ietf.o=
rg]
<b>On Behalf Of </b>Karen O'Donoghue<br>
<b>Sent:</b> Monday, June 10, 2013 9:20 AM<br>
<b>To:</b> jose@ietf.org<br>
<b>Subject:</b> [jose] webex information for JOSE teleconference: 17 June 2=
013 @ 1:00 pm EDT<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Folks,<br>
<br>
Here is the webex information for the call next Monday. <br>
<br>
Karen<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
<span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-s=
erif&quot;">Cindy Morgan invites you to attend this online meeting.
<br>
<br>
Topic: JOSE <br>
Date: Monday, June 17, 2013 <br>
Time: 11:00 am, Mountain Daylight Time (Denver, GMT-06:00) <br>
Meeting Number: 648 447 409 <br>
Meeting Password: 1234 <br>
<br>
<br>
------------------------------------------------------- <br>
To join the online meeting (Now from mobile devices!) <br>
------------------------------------------------------- <br>
1. Go to <a href=3D"https://ietf.webex.com/ietf/j.php?ED=3D225472827&amp;UI=
D=3D1566381972&amp;PW=3DNOWQ4YWY3NDc1&amp;RT=3DMiM2" target=3D"_blank">
https://ietf.webex.com/ietf/j.php?ED=3D225472827&amp;UID=3D1566381972&amp;P=
W=3DNOWQ4YWY3NDc1&amp;RT=3DMiM2</a>
<br>
2. If requested, enter your name and email address. <br>
3. If a password is required, enter the meeting password: 1234 <br>
4. Click &quot;Join&quot;. <br>
<br>
To view in other time zones or languages, please click the link: <br>
<a href=3D"https://ietf.webex.com/ietf/j.php?ED=3D225472827&amp;UID=3D15663=
81972&amp;PW=3DNOWQ4YWY3NDc1&amp;ORT=3DMiM2" target=3D"_blank">https://ietf=
.webex.com/ietf/j.php?ED=3D225472827&amp;UID=3D1566381972&amp;PW=3DNOWQ4YWY=
3NDc1&amp;ORT=3DMiM2</a>
<br>
<br>
------------------------------------------------------- <br>
To join the audio conference only <br>
------------------------------------------------------- <br>
Call-in toll number (US/Canada): 1-650-479-3208 <br>
<br>
Access code:648 447 409 <br>
<br>
------------------------------------------------------- <br>
For assistance <br>
------------------------------------------------------- <br>
1. Go to <a href=3D"https://ietf.webex.com/ietf/mc" target=3D"_blank">https=
://ietf.webex.com/ietf/mc</a>
<br>
2. On the left navigation bar, click &quot;Support&quot;. <br>
<br>
You can contact me at: <br>
<a href=3D"mailto:cmorgan@amsl.com">cmorgan@amsl.com</a> <br>
1-510-492-4085 <br>
<br>
To add this meeting to your calendar program (for example Microsoft Outlook=
), click this link:
<br>
<a href=3D"https://ietf.webex.com/ietf/j.php?ED=3D225472827&amp;UID=3D15663=
81972&amp;ICS=3DMI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DAAAAAnBS0dxw=
b5o23cp6D4NhhtUFgQ0Ft4xS6lHRlHHZAwFT&amp;RT=3DMiM2" target=3D"_blank">https=
://ietf.webex.com/ietf/j.php?ED=3D225472827&amp;UID=3D1566381972&amp;ICS=3D=
MI&amp;LD=3D1&amp;RD=3D2&amp;ST=3D1&amp;SHA2=3DAAAAAnBS0dxwb5o23cp6D4NhhtUF=
gQ0Ft4xS6lHRlHHZAwFT&amp;RT=3DMiM2</a>
<br>
<br>
The playback of UCF (Universal Communications Format) rich media files requ=
ires appropriate players. To view this type of rich media files in the meet=
ing, please check whether you have the players installed on your computer b=
y going to
<a href=3D"https://ietf.webex.com/ietf/systemdiagnosis.php">https://ietf.we=
bex.com/ietf/systemdiagnosis.php</a>.
<br>
<br>
Sign up for a free trial of WebEx <br>
<a href=3D"http://www.webex.com/go/mcemfreetrial" target=3D"_blank">http://=
www.webex.com/go/mcemfreetrial</a>
<br>
<br>
<a href=3D"http://www.webex.com" target=3D"_blank">http://www.webex.com</a>=
 <br>
<br>
CCP:&#43;16504793208x648447409# <br>
<br>
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a=
nd any documents and other materials exchanged or viewed during the session=
 to be recorded. By joining this session, you automatically consent to such=
 recordings. If you do not consent
 to the recording, discuss your concerns with the meeting host prior to the=
 start of the recording or do not join the session. Please note that any su=
ch recordings may be subject to discovery in the event of litigation.
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> jose-bounces@ietf.org [mailto:jose-bounces@ietf.o=
rg]
<b>On Behalf Of </b>Prateek Mishra<br>
<b>Sent:</b> Monday, June 17, 2013 7:14 AM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Interium Meeting Agenda<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is there a scheduled time and phone number for this =
meeting?<br>
<br>
Thanks,<br>
prateek<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">&lt;chair&gt;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Preliminary agenda for next week&#8217;s teleconfere=
nce has been posted<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://www.ietf.org/proceedings/interim/2=
013/06/17/jose/agenda/agenda-interim-2013-jose-2">http://www.ietf.org/proce=
edings/interim/2013/06/17/jose/agenda/agenda-interim-2013-jose-2</a><o:p></=
o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">jim<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>jose mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><o:p></o:p></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.iet=
f.org/mailman/listinfo/jose</a><o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678692C4TK5EX14MBXC283r_--

From housley@vigilsec.com  Mon Jun 17 08:57:38 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5269E21F9D3E for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 08:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id keCP+VxcluX4 for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 08:57:33 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3CB21F9CC1 for <jose@ietf.org>; Mon, 17 Jun 2013 08:57:33 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 82912F24070; Mon, 17 Jun 2013 11:58:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id OD2-eICjqh1K; Mon, 17 Jun 2013 11:57:11 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id A2751F24078; Mon, 17 Jun 2013 11:58:06 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
Date: Mon, 17 Jun 2013 11:57:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <937DC44F-CE30-4E13-8DAB-8F619BBD7AC5@vigilsec.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
X-Mailer: Apple Mail (2.1085)
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 15:57:38 -0000

Agree.  These things have origins in ANSI X9.42 and RFC 2631.

Russ


On Jun 16, 2013, at 9:20 PM, Manger, James H wrote:

> The use of the Concat KDF still does not look right.
>=20
> JWA [draft-ietf-jose-json-web-algorithms-11] section 4.7 says =
"ECDH-ES" uses Concat KDF from NIST 800-56A section 5.8.1. NIST defines =
5 fields that go into the key derivation: AlgorithmID, PartyUInfo, =
PartyVInfo, SuppPubInfo, and SuppPrivInfo.
>=20
> NIST says AlgorithmID indicates the algorithm that will use the =
derived key. JWA says to use the "alg" value (eg "ECDH-ES") as the =
AlgorithmID. AlgorithmID should actually be the "enc" value when the =
derived key is used directly as a CEK. When the derived key unwraps the =
CEK, AlgorithmID should be the name of the key wrap algorithm (eg =
"A128KW"). Perhaps the "alg" value can be used in this case as it =
identifies the key wrap algorithm along with the key establishment =
algorithm (eg "ECDH-ES+A128KW").
>=20
> NIST says PartyUInfo includes an identifier for party U. The first =
problem is that JWA does not indicate if the sender or receiver is party =
U (nor does JWE). The second problem is that JWA says PartyUInfo is =
random -- which seems to totally defeat the purpose of being an =
identifier for a party. JWA says PartyUInfo should vary for each =
recipient, which suggests PartyUInfo cannot be an id of the sender. Does =
that suggest the receiver is party U?
>=20
> NIST says PartyVInfo is required and includes an identifier for party =
V. JWA says PartyVInfo is empty, which obviously cannot meet the NIST =
definition.
>=20
> The JWA values for SuppPubInfo (length of derived key in bits) and =
SuppPrivInfo (empty) are in line with the NIST definitions.
>=20
>=20
> It appears the Concat KDF text in JWA has been rewritten based on =
RFC2631 "Diffie-Hellman Key Agreement Method". RFC2631 is not referenced =
by JWA, but it is mentioned in the "document history" section (which =
will eventually be deleted). RFC2631 has items such as partyAInfo and =
suppPubInfo whose names are similar to NIST items. However, RFC2631 was =
published 7 years before NIST 800-56A (and 13 years before the current =
version of NIST 800-56A) so RFC2631 cannot be used as a example of how =
to use Concat KDF.
>=20
> --
> James Manger
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From ietf@augustcellars.com  Mon Jun 17 09:59:42 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574F521F9D8C for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 09:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qG0Uf+6jJ9kA for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 09:59:36 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id E1ADC21F9D82 for <jose@ietf.org>; Mon, 17 Jun 2013 09:59:35 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 90C5E2CA0A; Mon, 17 Jun 2013 09:59:32 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Prateek Mishra'" <prateek.mishra@oracle.com>
References: <071f01ce6655$42a620c0$c7f26240$@augustcellars.com> <51BF1990.8030003@oracle.com>
In-Reply-To: <51BF1990.8030003@oracle.com>
Date: Mon, 17 Jun 2013 09:58:39 -0700
Message-ID: <01fb01ce6b7b$ea9e5ec0$bfdb1c40$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01FC_01CE6B41.3E415B80"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQJ0h+gdhaYa37O4vd2XExqS7wXqngG9z/1Bl9/5XQA=
Cc: jose@ietf.org
Subject: Re: [jose] Interium Meeting Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 16:59:42 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01FC_01CE6B41.3E415B80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

WebEx info was possted to the list on 6/10 

 

Conference is today @ 1 PM EDT

 

From: Prateek Mishra [mailto:prateek.mishra@oracle.com] 
Sent: Monday, June 17, 2013 7:14 AM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Interium Meeting Agenda

 

Is there a scheduled time and phone number for this meeting?

Thanks,
prateek

 

<chair>

 

Preliminary agenda for next week's teleconference has been posted

 

http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/agenda-interi
m-2013-jose-2

 

jim

 






_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

 


------=_NextPart_000_01FC_01CE6B41.3E415B80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>WebEx info was possted =
to the list on 6/10 <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Conference is today @ 1 =
PM EDT<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Prateek Mishra [mailto:prateek.mishra@oracle.com] <br><b>Sent:</b> =
Monday, June 17, 2013 7:14 AM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: [jose] Interium Meeting =
Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Is there a =
scheduled time and phone number for this =
meeting?<br><br>Thanks,<br>prateek<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>&lt;chair&gt;<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Preliminary =
agenda for next week&#8217;s teleconference has been =
posted<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://www.ietf.org/proceedings/interim/2013/06/17/jose/agenda/ag=
enda-interim-2013-jose-2">http://www.ietf.org/proceedings/interim/2013/06=
/17/jose/agenda/agenda-interim-2013-jose-2</a><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p =
class=3DMsoNormal>jim<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><br><o:p></o:p></span></p><pre>__________________=
_____________________________<o:p></o:p></pre><pre>jose mailing =
list<o:p></o:p></pre><pre><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><o:p></o:p></pre><pre><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/=
mailman/listinfo/jose</a><o:p></o:p></pre></blockquote><p =
class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_01FC_01CE6B41.3E415B80--


From samuel@erdtman.se  Mon Jun 17 14:26:09 2013
Return-Path: <samuel@erdtman.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D95F21F9D72 for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 14:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDHFyw6oJDbN for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 14:26:08 -0700 (PDT)
Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7F021F9476 for <jose@ietf.org>; Mon, 17 Jun 2013 14:26:06 -0700 (PDT)
Received: by mail-ea0-f173.google.com with SMTP id g15so2137193eak.18 for <jose@ietf.org>; Mon, 17 Jun 2013 14:26:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=ZrtcvapIftiGy8FwRbEbcm/T7ODG98GnKWbVpZzTDiU=; b=kZKCbShfgdwFlZd65karLS+o66mgwxXdq0wXuPO5uNsPKpWpm1u12ZVphK6NPfqH/q mPFPtgOjzb0YJYHYAO4A5QAlY8ZeOPUdkF7QXoemJrkSjrHvbRCrZkklXIBs1g3bFGvf hREyHHBc6/LG40epya8fc+NcsREQRhN28urjkKBX3kx2xTxTqR85tVQixwM3H0H3fItA r4zD9igq3sdpX/iQ1V2tqu4HFDfQ+qRjeskIsihU/xOLsuACJJPiC61rtg+9RRkT+mFn W5KqHNs/l+HgmvsJcVeK5RzVkxc+z+w3N6vAZVGd2znB2Tex/dQ4uNY1jA4E8VMJHwXn 4AKQ==
X-Received: by 10.15.35.129 with SMTP id g1mr14031404eev.2.1371504365954; Mon, 17 Jun 2013 14:26:05 -0700 (PDT)
References: <CAL02cgTc8aR=Sp7bN9ZUOJ4EOWE8t3aUPrsNkXhMq4zoFqNR8A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780758E@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSifdSMgb8RsXd=FnhUQvnj0D_-VimhGrnQUfUfNhDs8A@mail.gmail.com> <CAD9ie-uaxx0Yf6sW1-rUYEmD-CcNkJNC0cQ0Bypfs375fYpGYg@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436780A27F@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAD9ie-tuZqVr7Vq+Gt1j4KVKbH-2RZyW4Grp26hbW30zeyS-fg@mail.gmail.com>
From: Samuel Erdtman <samuel@erdtman.se>
In-Reply-To: <CAD9ie-tuZqVr7Vq+Gt1j4KVKbH-2RZyW4Grp26hbW30zeyS-fg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 17 Jun 2013 22:59:08 +0200
Message-ID: <-6293677259754862041@unknownmsgid>
To: Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary=089e0160c9b88a9ce504df603ef7
X-Gm-Message-State: ALoCoQlVFK1M0F+0hmR+tsGxQzXFiGrfveoAmjRfRzPcovK4tjZGqT/c2bcdN5cuzGX1BVYzikpQ
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] What are we doing here?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 21:26:09 -0000

--089e0160c9b88a9ce504df603ef7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Maybe a bit late but anyway.

+1 to Dick,

When I read the specs in May I had the same problem with these fields and
did similar assumptions as Dick and Richard.

Assumptions:
typ would  be used for saying JWE or JWS and
cty would be used to tell what's in the JWE or JWS.

I could not see the need to have a type value for JWT. As it looks today I
do not even see the need for a JWT header at al since as I see the JWT as
content and hence described by cty.

However by reading the conversation hear I can see how the reasoning to get
here has been done. I would prefer to change the meaning of cty and typ in
the way Richard proposes but it might be to much at this stage, in that
case a clarification would be great.

Best Regards
Samuel

Sent from my iPhone

On 7 jun 2013, at 19:06, Dick Hardt <dick.hardt@gmail.com> wrote:

Hi Mike,

Currently I find "typ" and "cty" confusing. Once I understand them, I may
be confused with other aspects. :)

For example, in:

https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11

What "typ" is supposed to be is confusing.

In 3.1, it is defined as "typ":"JWT"

In 4.1.8, it is "typ":"JWS" or "typ":"JWS+JSON"

Which one is it?
When would  you use "cty"?

-- Dick


On Fri, Jun 7, 2013 at 7:48 AM, Mike Jones <Michael.Jones@microsoft.com>wro=
te:

>  I agree that we should provide some additional clarification on the
> intended purpose for the =93typ=94 and =93cty=94 parameters.  We just did=
 provide
> substantial additional clarification for =93crit=94 in -11, based on the
> working group decisions at the interim meeting.  Are there other specific
> things that you=92d suggest that we clarify, Dick?****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Dick Hardt
> *Sent:* Friday, June 07, 2013 7:33 AM
> *To:* Richard Barnes
> *Cc:* Mike Jones; jose@ietf.org
> *Subject:* Re: [jose] What are we doing here?****
>
> ** **
>
> MIke: I don't find your response very useful for understanding the
> question Richard proposed. I find the spec confusing as to what I am
> supposed to do when as an implementer. It seems that it is clear to all t=
he
> people associated with OpenID Connect, but without that context, it is
> confusing, and frankly, some of the parameters seem like hacks to me.
> Perhaps some additional clarification on what the parameters are intended
> for would assist?****
>
> ** **
>
> -- Dick****
>
> ** **
>
> On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes <rlb@ipv.sx> wrote:****
>
> Of course, motherhood, apple pie, etc. :)****
>
> ** **
>
> The question is what we're trying to help developers do.  The developers =
I
> talk to want a simple tool to do crypto stuff, full stop.  They don't wan=
t
> semantic validation, critical fields, etc.  ****
>
> ** **
>
> The adoption you're pointing to is not really relevant to the process
> here.  The deployed implementations you're talking about are all in a
> limited space, covering one use case.  And the current solution comes wit=
h
> baggage for that use case that adds complexity for everyone else.  If you
> wanted to address that one use case, you should have chartered for that,
> not general signing and encryption.****
>
> ** **
>
> Nonetheless, on timing, I agree that I'm getting a little bored with
> fighting over this :)  I'm working on a review of -11 that tries to packa=
ge
> up all the remaining comments such that they can get resolved and we can
> move on with life.****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> Excellent question, Richard, because it gets to the heart of why the JOSE
> specs are already highly successful and widely adopted.****
>
>  ****
>
>   - We are building useful tools that solve real problems for developers.=
*
> ***
>
>   - We are practically demonstrating the value of rough consensus and
> running code.****
>
>   - We are making simple things simple.****
>
>   - We are making complex things possible, when necessary (but not at the
> expense of keeping simple things simple).****
>
>   - We are developing specs with an explicit goal of enabling ubiquitous
> adoption.****
>
>   - We are developing specs guided by practical engineering tradeoffs to
> enable commonly useful functionality in a straightforward manner.****
>
>  ****
>
> The level of adoption, with dozens of deployed implementations, is
> compelling evidence that we=92ve already achieved the goals above.  It=92=
s time
> to =93ship it=94, as making the JOSE specs actual standards will only inc=
rease
> their adoption and value to the industry.****
>
>  ****
>
> That=92s what we=92re doing here.****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> P.S.  I would be careful reasoning from the premise of =93The perfect
> protocol is one from which nothing can be removed=94.  By that logic, the
> perfect specification is the null specification, which leaves all
> possibilities open, and solves no actual problems. ;-)****
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 06, 2013 2:44 PM
> *To:* jose@ietf.org
> *Subject:* [jose] What are we doing here?****
>
>  ****
>
> The conversation about "typ" has brought us back to a familiar question
> for this working group -- what are we trying to do here?****
>
>  ****
>
> The current document is ambiguous on this topic.  On the one hand, it
> mostly covers the crypto bases, with things like "alg" and "enc".  On the
> other hand, it mixes in application design concepts like "typ" and "crit"=
.
>  The result is a spec that's ambiguous in purpose and complex.  If I'm
> building an application with this, how do I decide what goes in the "crit=
"
> field, or what values to use for "typ"?    ****
>
> The charter for this working group is not ambiguous on this topic.  This
> group is chartered to do signing and encryption.  The JOSE formats should
> carry the parameters needed to perform those operations.  Anything else i=
s
> extraneous, and in the spirit of "The perfect protocol is one from which
> nothing can be removed", should be removed.****
>
>  ****
>
> Now, I'm not going to be a hard-liner on this.  I won't complain about
> "zip" and "cty", since they are clearly defined and have clear use cases.
>  But "crit" and "typ" are so ambiguous and so little supported by use
> cases*, that they really should go.****
>
>  ****
>
> </rant>****
>
>  ****
>
> --Richard****
>
> ** **
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>
>
> ****
>
> ** **
>
> --
> -- Dick ****
>



--=20
-- Dick

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

--089e0160c9b88a9ce504df603ef7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=
=3Dutf-8"></head><body dir=3D"auto"><div><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"><div>Maybe a bit late but anyway.</d=
iv><div><br>
</div><div>+1 to Dick,</div><div><br></div><div>When I read the specs in Ma=
y I had the same problem with these fields and did similar assumptions as D=
ick and Richard.=A0</div><div><br></div><div>Assumptions:</div><div>typ wou=
ld =A0be used for saying JWE or JWS and</div>
<div>cty would be used to tell what&#39;s in the JWE or JWS.</div><div><br>=
</div><div>I could not see the need to have a type value for JWT. As it loo=
ks today I do not even see the need for a JWT header at al since as I see t=
he JWT as content and hence described by cty.</div>
<div><br></div><div>However by reading the conversation hear I can see how =
the reasoning to get here has been done. I would prefer to change the meani=
ng of cty and typ in the way Richard proposes but it might be to much at th=
is stage, in that case a clarification would be great.</div>
<div><br></div><div>Best Regards</div><div>Samuel</div><div><br>Sent from m=
y iPhone</div><div><br>On 7 jun 2013, at 19:06, Dick Hardt &lt;<a href=3D"m=
ailto:dick.hardt@gmail.com">dick.hardt@gmail.com</a>&gt; wrote:<br><br></di=
v>
<blockquote type=3D"cite"><div><div dir=3D"ltr"><div style>Hi Mike,=A0</div=
><div style><br></div><div style>Currently I find &quot;typ&quot; and &quot=
;cty&quot; confusing. Once I understand them, I may be confused with other =
aspects. :)</div>
<div style><br>
</div><div style>For example, in:</div><div style><br></div><a href=3D"http=
s://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11">https://tool=
s.ietf.org/html/draft-ietf-jose-json-web-signature-11</a><br><div><br></div=
>

<div style>What &quot;typ&quot; is supposed to be is confusing.</div><div><=
br></div><div style>In 3.1, it is defined as &quot;typ&quot;:&quot;JWT&quot=
;</div><div style><br></div><div style>In 4.1.8, it is &quot;typ&quot;:&quo=
t;JWS&quot; or &quot;typ&quot;:&quot;JWS+JSON&quot;</div>

<div style><br></div><div style>Which one is it?</div><div style>When would=
 =A0you use &quot;cty&quot;?</div><div style><br></div><div style>-- Dick</=
div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Fri, Jun 7, 2013 at 7:48 AM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft=
.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I agree that we should pr=
ovide some additional clarification on the intended purpose for the =93typ=
=94 and =93cty=94 parameters.=A0 We just did provide substantial additional
 clarification for =93crit=94 in -11, based on the working group decisions =
at the interim meeting.=A0 Are there other specific things that you=92d sug=
gest that we clarify, Dick?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 07, 2013 7:33 AM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] What are we doing here?<u></u><u></u></span></p>=
<div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">MIke: I don&#39;t find your response very useful for=
 understanding the question Richard proposed. I find the spec confusing as =
to what I am supposed to do when as an implementer. It seems that it is cle=
ar to all the people associated with OpenID
 Connect, but without that context, it is confusing, and frankly, some of t=
he parameters seem like hacks to me. Perhaps some additional clarification =
on what the parameters are intended for would assist?<u></u><u></u></p>


<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-- Dick<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 7:23 AM, Richard Barnes &lt;<=
a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u>=
</u><u></u></p>
<div>
<p class=3D"MsoNormal">Of course, motherhood, apple pie, etc. :)<u></u><u><=
/u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The question is what we&#39;re trying to help develo=
pers do. =A0The developers I talk to want a simple tool to do crypto stuff,=
 full stop. =A0They don&#39;t want semantic validation, critical fields, et=
c. =A0<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The adoption you&#39;re pointing to is not really re=
levant to the process here. =A0The deployed implementations you&#39;re talk=
ing about are all in a limited space, covering one use case. =A0And the cur=
rent solution comes with baggage for that use
 case that adds complexity for everyone else. =A0If you wanted to address t=
hat one use case, you should have chartered for that, not general signing a=
nd encryption.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Nonetheless, on timing, I agree that I&#39;m getting=
 a little bored with fighting over this :) =A0I&#39;m working on a review o=
f -11 that tries to package up all the remaining comments such that they ca=
n get resolved and we can move on with life.<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><u></u>=A0<u></u></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<u></u><u></u=
></span></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 7, 2013 at 1:18 AM, Mike Jones &lt;<a hr=
ef=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@m=
icrosoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Excellent question, Richa=
rd, because it gets to the heart of why the JOSE specs are already highly
 successful and widely adopted.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are building use=
ful tools that solve real problems for developers.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are practically =
demonstrating the value of rough consensus and running code.</span><u></u><=
u></u></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making simpl=
e things simple.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are making compl=
ex things possible, when necessary (but not at the expense of keeping simpl=
e
 things simple).</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs with an explicit goal of enabling ubiquitous adoption.</span><u></u><u=
></u></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0 - We are developing s=
pecs guided by practical engineering tradeoffs to enable commonly useful fu=
nctionality
 in a straightforward manner.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The level of adoption, wi=
th dozens of deployed implementations, is compelling evidence that we=92ve
 already achieved the goals above.=A0 It=92s time to =93ship it=94, as maki=
ng the JOSE specs actual standards will only increase their adoption and va=
lue to the industry.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That=92s what we=92re doi=
ng here.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">P.S.=A0 I would be carefu=
l reasoning from the premise of =93</span>The perfect protocol is one from =
which
 nothing can be removed<span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=94.=A0 By that logic, th=
e perfect specification is the null specification, which leaves all possibi=
lities open, and solves no actual problems. ;-)</span><u></u><u></u></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 06, 2013 2:44 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> [jose] What are we doing here?</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">The conversation about &quot;typ&quot; has brought u=
s back to a familiar question for this working group -- what are we trying =
to do here?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current document is ambiguous on this topic. =A0=
On the one hand, it mostly covers the crypto bases, with things like &quot;=
alg&quot; and &quot;enc&quot;. =A0On the other hand, it mixes in applicatio=
n
 design concepts like &quot;typ&quot; and &quot;crit&quot;. =A0The result i=
s a spec that&#39;s ambiguous in purpose and complex. =A0If I&#39;m buildin=
g an application with this, how do I decide what goes in the &quot;crit&quo=
t; field, or what values to use for &quot;typ&quot;? =A0 =A0<u></u><u></u><=
/p>


</div>
<div>
<p class=3D"MsoNormal">The charter for this working group is not ambiguous =
on this topic. =A0This group is chartered to do signing and encryption. =A0=
The JOSE formats should carry the parameters needed to
 perform those operations. =A0Anything else is extraneous, and in the spiri=
t of &quot;The perfect protocol is one from which nothing can be removed&qu=
ot;, should be removed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now, I&#39;m not going to be a hard-liner on this. =
=A0I won&#39;t complain about &quot;zip&quot; and &quot;cty&quot;, since th=
ey are clearly defined and have clear use cases. =A0But &quot;crit&quot; an=
d &quot;typ&quot; are so ambiguous
 and so little supported by use cases*, that they really should go.<u></u><=
u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/rant&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">-- <br>
-- Dick <u></u><u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>-- Dick
</div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
____________________________</span><br><span>jose mailing list</span><br><s=
pan><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a></span><br><span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mai=
lman/listinfo/jose</a></span><br>
</div></blockquote></div></body></html>

--089e0160c9b88a9ce504df603ef7--

From iesg-secretary@ietf.org  Mon Jun 17 16:13:59 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A83DC21F9E7F; Mon, 17 Jun 2013 16:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AuvPxkq5RiLH; Mon, 17 Jun 2013 16:13:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D2621F9E7D; Mon, 17 Jun 2013 16:13:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130617231359.23431.62465.idtracker@ietfa.amsl.com>
Date: Mon, 17 Jun 2013 16:13:59 -0700
Cc: jose@ietf.org
Subject: [jose] JOSE WG Virtual Interim Meeting, July 1, 2013
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 17 Jun 2013 23:13:59 -0000

The JOSE Working Group will hold a virtual interim meeting on Monday, =

July 1, 2013 at 10:00 AM PDT.

Additional information will be announced on the JOSE WG mailing list:
http://www.ietf.org/mail-archive/web/jose/current/maillist.html

From rlb@ipv.sx  Mon Jun 17 20:55:18 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E51C21E8050 for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 20:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a9MiwJYe2knn for <jose@ietfa.amsl.com>; Mon, 17 Jun 2013 20:55:14 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 8C18A11E80C5 for <jose@ietf.org>; Mon, 17 Jun 2013 20:55:14 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k14so4457948oag.12 for <jose@ietf.org>; Mon, 17 Jun 2013 20:55:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=PFxcVRlUxA18FZshAX4gObTJspy5E8OpXpGnSMjP/ig=; b=kqMiqeySuYXADu216UPWg3zoJ7AwanJOGZzTqTqAStrz1vEfEP4RNSv7rhSVkCUtZ3 XL1xMHXIqi1iTixUsg+4VL5VRW72x0KtULOXehzGIWL/gkHnl3jeRVZKsK30truoLQNp HI9ZD9IzBtEeFowl7y32XCZ/soHJtPyEDYBDE1MPTFesGQGnNsE9iNnnLlzS/7Ux1AFg x2QopK61jXG86hoNDPAp7hhV0hxXPUWxxzuoGVUZo7aDf8mbMayhBJLv1MQYXnPOnBHK fyYPyJmVHXhiDowdwzi2XeU4w9jxIrgfKAvLGDaeq6q6FG+a5H8cgeOosGqyyZsvIXxw +ttA==
MIME-Version: 1.0
X-Received: by 10.60.161.206 with SMTP id xu14mr3491160oeb.109.1371527714085;  Mon, 17 Jun 2013 20:55:14 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Mon, 17 Jun 2013 20:55:13 -0700 (PDT)
X-Originating-IP: [12.104.13.2]
In-Reply-To: <CAMm+Lwjf6azxD67hKTsjmJv2M1sOX0OqM65-29n2FqRCZsuDwQ@mail.gmail.com>
References: <CAL02cgRLGaSGFqg6PUoz1KX+7jEjU7rwt-t7B=U0FvEqYZrU-w@mail.gmail.com> <C2C21851-DB8D-4B0A-B134-7C0686192270@oracle.com> <7188842785648960750@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785A88B@TK5EX14MBXC283.redmond.corp.microsoft.com> <-7448156496304357389@unknownmsgid> <4E1F6AAD24975D4BA5B16804296739436785D014@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAMm+Lwjf6azxD67hKTsjmJv2M1sOX0OqM65-29n2FqRCZsuDwQ@mail.gmail.com>
Date: Mon, 17 Jun 2013 23:55:13 -0400
Message-ID: <CAL02cgQMjHV98eXXXBQ_Fp=bo3H76Xq-pA0gbeKhw8LMWQ0X7w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=089e01176a6d32abf304df65ae68
X-Gm-Message-State: ALoCoQlJSVPqv64OfKIyKN6b/30jsvhcV3JLE3zUFqh9k4j1y2CbVgTk+KM4jcn63w+YzImiWAht
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, George Fletcher <gffletch@aol.com>, "<jose@ietf.org>" <jose@ietf.org>, Phil Hunt <phil.hunt@oracle.com>
Subject: Re: [jose] Deployed Code (was: Re: #23: Make crypto independent of binary encoding (base64))
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 03:55:18 -0000

--089e01176a6d32abf304df65ae68
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I like the idea of being able to use standard names here.  What about doing
like we do with "cty" and "typ", i.e., defining short names that expand to
some full registry value?


On Sat, Jun 15, 2013 at 4:02 PM, Phillip Hallam-Baker <hallam@gmail.com>wro=
te:

> The name fields in the following originate from PEM:
> http://www.iana.org/assignments/dssc/dssc.xml
>
> The same code points are used in HTTP Digest
> http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xml
>
> SSH uses the same code points again and defines HMAC code points:
>
> http://www.iana.org/assignments/ssh-parameters/ssh-parameters.xml#ssh-par=
ameters-18
>
>
> I don't think that when you are using base64 for encoding you can really
> make an issue of the difference between hmac-sha2-256 and hs256 as being
> serious enough to justify a whole new registry and a whole different set =
of
> encodings.
>
> The JWA algorithm should instead update the DSSC registry which was
> originally conceived as being a single registry and point of contact for
> all crypto algorithms and canonical identifiers for all protocols that do
> not use protocol specific code points (like IPSEC, DNSSEC).
>
>
> Setting up registries is easy. Maintaining them is not.
>
>
>
>
> On Fri, Jun 14, 2013 at 7:59 PM, Mike Jones <Michael.Jones@microsoft.com>=
wrote:
>
>>  What alternative registry of algorithm names were you thinking of?  Are
>> you suggesting that we use the OID numbers used by CMS?****
>>
>> ** **
>>
>> As far as I know, there is no MIME registry of cryptographic algorithm
>> names, so I don=92t think there=92s any conflict/duplication there.****
>>
>> ** **
>>
>>                                                                 -- Mike*=
*
>> **
>>
>> ** **
>>
>> *From:* Phillip Hallam-Baker [mailto:hallam@gmail.com]
>> *Sent:* Friday, June 14, 2013 4:56 PM
>> *To:* Mike Jones
>> *Cc:* Phil Hunt; Richard Barnes; jose-chairs@tools.ietf.org; <
>> jose@ietf.org>; George Fletcher
>>
>> *Subject:* Re: [jose] Deployed Code (was: Re: #23: Make crypto
>> independent of binary encoding (base64))****
>>
>>  ** **
>>
>> So is the idea that a standards organization should seek consistency****
>>
>> ** **
>>
>> I understand the WG rationale. I reject it as a sufficient IETF
>> rationale. If it stands it is going to require two parallel registries f=
or
>> the same algs.****
>>
>> ** **
>>
>> I have a spec that crosses HTTP and JSON. Am I supposed to use mime
>> registry in one and this duplicate scheme in the other?****
>>
>> ** **
>>
>> Blocking that type of move is what IETF last call is for. There is a
>> negligible benefit in the spec and a huge cost to the community.****
>>
>>
>>
>> Sent from my differenc engine****
>>
>> ** **
>>
>>
>> On Jun 14, 2013, at 5:53 PM, Mike Jones <Michael.Jones@microsoft.com>
>> wrote:****
>>
>>  Short names were chosen because of the core compactness requirement for
>> the Compact Serialization.  That was an engineering decision that was
>> consciously made and for which the rationale is clear.****
>>
>>  ****
>>
>> You can disagree with that decision but it has known clear benefits and
>> is far from arbitrary.****
>>
>>  ****
>>
>>                                                                 -- Mike*=
*
>> **
>>
>>  ****
>>
>> *From:* Phillip Hallam-Baker [mailto:hallam@gmail.com <hallam@gmail.com>=
]
>>
>> *Sent:* Friday, June 14, 2013 2:49 PM
>> *To:* Phil Hunt
>> *Cc:* Richard Barnes; Mike Jones; jose-chairs@tools.ietf.org; <
>> jose@ietf.org>; George Fletcher
>> *Subject:* Re: [jose] Deployed Code (was: Re: #23: Make crypto
>> independent of binary encoding (base64))****
>>
>>  ****
>>
>> I think in this case that it is late to bring up binary encoding in Jose=
*
>> ***
>>
>>  ****
>>
>> But that does not mean we can't add it later. Specs have revisions. All
>> that is needed to support binary is a flag to say what was signed. Defau=
lts
>> to the current scheme.****
>>
>>  ****
>>
>> Now if it was a case where binary had been raised at the start of the
>> process and the person got told to shut up because of 'focus' well that
>> would be different. When people pull that trick I have no qualms about
>> repeating my concerns in IETF last call. I think that all too often ther=
e
>> is too much haste when starting a WG and people get railroaded into a
>> broken scheme some faction likes. But that did not happen here so I thin=
k
>> it is going to be for the binary camp to work out the solution. ****
>>
>>  ****
>>
>> My bigger Jose concern is the bizarre decision to rename all the crypto
>> alg names. I have a spec that uses mime and JSON. If I take Jose serious=
ly
>> I need a second crypto alg registry. ****
>>
>>  ****
>>
>> That is junk, that is something that was raised at the start of the
>> process. So yes, I will make it an issue in IETF last call
>>
>> Sent from my difference engine****
>>
>>  ****
>>
>>
>> On Jun 13, 2013, at 12:06 PM, Phil Hunt <phil.hunt@oracle.com> wrote:***=
*
>>
>>  Seems like many these days are in a rush. They call for consensus
>> before discussing the issue. ****
>>
>>  ****
>>
>> Isn't it up to the chair?****
>>
>>  ****
>>
>> This isn't unique to this WG. ****
>>
>>  ****
>>
>> Too many times the explanation for keeping an apparent 'feature/flaw' is
>> 'because we don't want change'. Yet often the group can't explain it. Or
>> worse, the group just says "we know the emperor has no clothes, we just
>> don't feel the need to comment." This is where alarm bells go off for me=
.
>>
>> Phil****
>>
>>
>> On 2013-06-13, at 7:35, Richard Barnes <rlb@ipv.sx> wrote:****
>>
>>  This would have been a nice discussion to have had 18 months ago, when
>> we were getting started.****
>>
>>  ****
>>
>> I don't think it's compatible with the IETF ethos to say "Changes to thi=
s
>> document MUST NOT break existing code."  Otherwise, we're not doing
>> engineering here, we're cleaning up documentation and rubber-stamping.**=
*
>> *
>>
>>  ****
>>
>> What would be acceptable is to say "Changes must break cleanly with
>> existing code".  That is, it should be possible for a JWT implementation
>> to, say, process both "legacy" JWS syntax and whatever comes out of this
>> group.  That way, we could come to consensus on the best solution,
>> incorporating lessons learned from earlier work without being hindered b=
y
>> them.****
>>
>>  ****
>>
>> Would participants here consider it a acceptable for the output of this
>> working group to be incompatible with existing JWT implementations, as l=
ong
>> as it had the property that JW* objects in the new format could be clear=
ly
>> distinguished from "legacy" JW* objects, so that implementations could
>> adapt their processing?****
>>
>>  ****
>>
>> --Richard****
>>
>>  ****
>>
>>  ****
>>
>>  ****
>>
>> On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher <gffletch@aol.com>
>> wrote:****
>>
>> +1
>>
>> Breaking deployed code as raised by Brian, Naveen and others is a
>> critical consideration.
>>
>> Thanks,
>> George****
>>
>> On 6/13/13 10:19 AM, Mike Jones wrote:****
>>
>>  Jim and Karen, could you please do as Richard suggests and close this
>> issue as =93won=92t fix=94.****
>>
>>  ****
>>
>>                                                             Thank you,**=
*
>> *
>>
>>                                                             -- Mike****
>>
>>  ****
>>
>> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]
>> *Sent:* Wednesday, June 12, 2013 1:57 PM
>> *To:* jose-chairs@tools.ietf.org; Mike Jones
>> *Subject:* Fwd: [jose] #23: Make crypto independent of binary encoding
>> (base64)****
>>
>>  ****
>>
>> In other words: Chairs, feel free to close/wontfix :)****
>>
>>  ****
>>
>> ---------- Forwarded message ----------
>> From: *Richard Barnes* <rlb@ipv.sx>
>> Date: Wed, Jun 12, 2013 at 4:55 PM
>> Subject: Re: [jose] #23: Make crypto independent of binary encoding
>> (base64)
>> To: "Matt Miller (mamille2)" <mamille2@cisco.com>
>> Cc: jose issue tracker <trac+jose@trac.tools.ietf.org>, "<
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>" <
>> draft-ietf-jose-json-web-encryption@tools.ietf.org>, "<
>> michael.jones@microsoft.com>" <michael.jones@microsoft.com>, "<
>> jose@ietf.org>" <jose@ietf.org>****
>>
>> To be clear, I structured my message in two parts for a reason, to
>> separate the analysis from the opinion.  I acknowledge that I am but one
>> voice here, and I'm increasingly hearing how alone I am :)****
>>
>>  ****
>>
>> On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes <rlb@ipv.sx> wrote:****
>>
>>  <impartial-analysis>****
>>
>> So just to be clear on the trade-off the WG has to make:****
>>
>>  ****
>>
>> On the one hand: Breaking every existing JWT implementation in the world=
*
>> ***
>>
>> On the other hand: Eternally binding ourselves to base64 encoding, even
>> if binary-safe encodings become available (CBOR, MsgPack, etc.)****
>>
>> </impartial-analysis >****
>>
>>  ****
>>
>> <personal-opinion>****
>>
>> I have some sympathy with JWT implementors.  It sucks to have to refacto=
r
>> code.  But I think we're literally talking about something like a 5-line
>> patch.  And early JWT implementors knew or should have known (to use a D=
C
>> phrase) that they were dealing with a draft spec.  As the W3C editor's
>> draft template says, in big bold red print, "Implementors who are not
>> taking part in the discussions are likely to find the specification
>> changing out from under them in incompatible ways."****
>>
>>  ****
>>
>> As PHB pointed out in the other thread, it would be nice to use JWS and
>> JWE in place of CMS one day, without the base64 hit.  We should incur th=
e
>> implementation pain now, and get the design right for the long run.  Bas=
e64
>> is a hack around JSON; we should build the system so that when we no lon=
ger
>> need that hack, it can go away.****
>>
>> </personal-opinion>****
>>
>>  ****
>>
>> --Richard****
>>
>>  ****
>>
>>  ****
>>
>>  ****
>>
>> On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamille2) <
>> mamille2@cisco.com> wrote:****
>>
>> I did at first find it curious why the cryptographic operations were ove=
r
>> the base64url-enccoded values, but I was also very focused on JWE, where=
 I
>> think the field separation problem is less of an issue (at least now).  =
For
>> JWS, this would certainly cause problems without some manner of unambigu=
ous
>> field parameterization.
>>
>> I will note that unescaped NULL is not valid in JSON, so it could be use=
d
>> as a separator between the encoded header and the payload.  I do find it
>> interesting if JOSE could more easily and efficiently support other
>> encodings.  However, I think that while this is an interesting thought
>> experiment, it seems we're too far down the path to seriously consider i=
t
>> unless the current state were shown to be horribly broken.
>>
>>
>> - m&m
>>
>> Matt Miller < mamille2@cisco.com >
>> Cisco Systems, Inc.****
>>
>>
>> On Jun 11, 2013, at 6:01 PM, jose issue tracker <
>> trac+jose@trac.tools.ietf.org> wrote:
>>
>> > #23: Make crypto independent of binary encoding (base64)
>> >
>> >
>> > Comment (by michael.jones@microsoft.com):
>> >
>> > For both serializations, you already need the base64url encoded versio=
ns
>> > of the JWS Header and the JWS Payload to preserve them in transmission=
,
>> so
>> > computing them isn't an extra burden.  In the JWS Compact Serializatio=
n,
>> > you already need the concatenation of the Encoded JWS Header, a period
>> > character, and the Encoded JWS Payload, so computing that concatenatio=
n
>> > isn't an extra burden.  Given you already have that quantity, computin=
g
>> > the signature over it is the easiest thing for developers to do, and
>> it's
>> > been shown to work well in practice.  There's no compelling reason to
>> make
>> > this change.
>> >
>> > Even for the JSON Serialization, the only "extra" step that's required
>> to
>> > compute the signature is the concatenation with the period character -
>> to
>> > prevent shifting of data from one field to the other, as described by
>> Jim
>> > Schaad in the e-mail thread.  So this step isn't actually "extra" at
>> all -
>> > it's necessary.  It's also highly advantageous to use exactly the same
>> > computation for both serializations, which is currently the case.
>> >
>> > Since there is no compelling reason to make this change, and since
>> making
>> > it could enable the "shifting" problem identified by Jim, it should no=
t
>> be
>> > made.
>> >
>> > --
>> >
>> -------------------------+----------------------------------------------=
---
>> > Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>> >     Type:  defect       |  encryption@tools.ietf.org
>> > Priority:  major        |      Status:  new
>> > Component:  json-web-    |   Milestone:
>> >  encryption             |     Version:
>> > Severity:  -            |  Resolution:
>> > Keywords:               |
>> >
>> -------------------------+----------------------------------------------=
---
>> >
>> > Ticket URL: <
>> http://trac.tools.ietf.org/wg/jose/trac/ticket/23#comment:2>
>> > jose <http://tools.ietf.org/jose/>
>> >****
>>
>> > _______________________________________________
>> > jose mailing list
>> > jose@ietf.org
>> > https://www.ietf.org/mailman/listinfo/jose****
>>
>>  ****
>>
>>    ****
>>
>>  ****
>>
>> ** **
>>
>> _______________________________________________****
>>
>> jose mailing list****
>>
>> jose@ietf.org****
>>
>> https://www.ietf.org/mailman/listinfo/jose****
>>
>>   ****
>>
>> --
>> <XeC> <http://connect.me/gffletch>****
>>
>>  ****
>>
>>  _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose****
>>
>>   _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose****
>>
>>
>
>
> --
> Website: http://hallambaker.com/
>

--089e01176a6d32abf304df65ae68
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I like the idea of being able to use standard names here. =
=A0What about doing like we do with &quot;cty&quot; and &quot;typ&quot;, i.=
e., defining short names that expand to some full registry value?</div><div=
 class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Sat, Jun 15, 2013 at 4:02 PM, Phillip=
 Hallam-Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" tar=
get=3D"_blank">hallam@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr"><div>The name fields in the following originate from PEM:<=
/div><div><a href=3D"http://www.iana.org/assignments/dssc/dssc.xml" target=
=3D"_blank">http://www.iana.org/assignments/dssc/dssc.xml</a><br></div><div=
><br>
</div><div>
The same code points are used in HTTP Digest</div><div><a href=3D"http://ww=
w.iana.org/assignments/http-dig-alg/http-dig-alg.xml" target=3D"_blank">htt=
p://www.iana.org/assignments/http-dig-alg/http-dig-alg.xml</a><br></div><di=
v>
<br>
</div><div>SSH uses the same code points again and defines HMAC code points=
:</div><div><a href=3D"http://www.iana.org/assignments/ssh-parameters/ssh-p=
arameters.xml#ssh-parameters-18" target=3D"_blank">http://www.iana.org/assi=
gnments/ssh-parameters/ssh-parameters.xml#ssh-parameters-18</a><br>

</div><div><br></div><div><br></div><div>I don&#39;t think that when you ar=
e using base64 for encoding you can really make an issue of the difference =
between=A0<span style=3D"font-size:13px;font-family:sans-serif">hmac-sha2-2=
56 and hs256 as being serious enough to justify a whole new registry and a =
whole different set of encodings.</span></div>

<div><span style=3D"font-size:13px;font-family:sans-serif"><br></span></div=
><div><span style=3D"font-size:13px;font-family:sans-serif">The JWA algorit=
hm should instead update the DSSC registry which was originally conceived a=
s being a single registry and point of contact for all crypto algorithms an=
d canonical identifiers for all protocols that do not use protocol specific=
 code points (like IPSEC, DNSSEC).</span></div>

<div><span style=3D"font-size:13px;font-family:sans-serif"><br></span></div=
><div><span style=3D"font-size:13px;font-family:sans-serif"><br></span></di=
v><div><span style=3D"font-size:13px;font-family:sans-serif">Setting up reg=
istries is easy. Maintaining them is not.</span></div>

<div><span style=3D"font-size:13px;font-family:sans-serif"><br></span></div=
><div><br></div></div><div class=3D"gmail_extra"><div><div class=3D"h5"><br=
><br><div class=3D"gmail_quote">On Fri, Jun 14, 2013 at 7:59 PM, Mike Jones=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" targe=
t=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">What alternative registry=
 of algorithm names were you thinking of?=A0 Are you suggesting that we use=
 the OID numbers used by CMS?<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">As far as I know, there i=
s no MIME registry of cryptographic algorithm names, so I don=92t think the=
re=92s any conflict/duplication there.<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [mailto:<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">=
hallam@gmail.com</a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 4:56 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Phil Hunt; Richard Barnes; <a href=3D"mailto:jose-chairs@tools.i=
etf.org" target=3D"_blank">jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"m=
ailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&gt;; George Fletch=
er</span></p>

<div><div><br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))<u></u><u></u></div></div><p></p>
</div>
</div><div><div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">So is the idea that a standards organization should =
seek consistency<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I understand the WG rationale. I reject it as a suff=
icient IETF rationale. If it stands it is going to require two parallel reg=
istries for the same algs.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have a spec that crosses HTTP and JSON. Am I suppo=
sed to use mime registry in one and this duplicate scheme in the other?<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Blocking that type of move is what IETF last call is=
 for. There is a negligible benefit in the spec and a huge cost to the comm=
unity.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
Sent from my differenc engine<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 14, 2013, at 5:53 PM, Mike Jones &lt;<a href=3D"mailto:Michael.Jones=
@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; wrote=
:<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Short names were chosen b=
ecause of the core compactness requirement for the Compact Serialization.=
=A0 That was an engineering decision that was consciously made
 and for which the rationale is clear.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">You can disagree with tha=
t decision but it has known clear benefits and is far from arbitrary.</span=
><u></u><u></u></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Phillip =
Hallam-Baker [<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">mailto:=
hallam@gmail.com</a>]
<br>
<b>Sent:</b> Friday, June 14, 2013 2:49 PM<br>
<b>To:</b> Phil Hunt<br>
<b>Cc:</b> Richard Barnes; Mike Jones; <a href=3D"mailto:jose-chairs@tools.=
ietf.org" target=3D"_blank">
jose-chairs@tools.ietf.org</a>; &lt;<a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>&gt;; George Fletcher<br>
<b>Subject:</b> Re: [jose] Deployed Code (was: Re: #23: Make crypto indepen=
dent of binary encoding (base64))</span><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I think in this case that it is late to bring up bin=
ary encoding in Jose<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">But that does not mean we can&#39;t add it later. Sp=
ecs have revisions. All that is needed to support binary is a flag to say w=
hat was signed. Defaults to the current scheme.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Now if it was a case where binary had been raised at=
 the start of the process and the person got told to shut up because of &#3=
9;focus&#39; well that would be different. When people pull that trick I ha=
ve no qualms about repeating my concerns in
 IETF last call. I think that all too often there is too much haste when st=
arting a WG and people get railroaded into a broken scheme some faction lik=
es. But that did not happen here so I think it is going to be for the binar=
y camp to work out the solution.=A0<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">My bigger Jose concern is the bizarre decision to re=
name all the crypto alg names. I have a spec that uses mime and JSON. If I =
take Jose seriously I need a second crypto alg registry.=A0<u></u><u></u></=
p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That is junk, that is something that was raised at t=
he start of the process. So yes, I will make it an issue in IETF last call<=
br>
<br>
Sent from my difference engine<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On Jun 13, 2013, at 12:06 PM, Phil Hunt &lt;<a href=3D"mailto:phil.hunt@ora=
cle.com" target=3D"_blank">phil.hunt@oracle.com</a>&gt; wrote:<u></u><u></u=
></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">Seems like many these days are in a rush. They call =
for consensus before discussing the issue.=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Isn&#39;t it up to the chair?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This isn&#39;t unique to this WG.=A0<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Too many times the explanation for keeping an appare=
nt &#39;feature/flaw&#39; is &#39;because we don&#39;t want change&#39;. Ye=
t often the group can&#39;t explain it. Or worse, the group just says &quot=
;we know the emperor has no clothes, we just don&#39;t feel the need
 to comment.&quot; This is where alarm bells go off for me.=A0<br>
<br>
Phil<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On 2013-06-13, at 7:35, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" ta=
rget=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">This would have been a nice discussion to have had 1=
8 months ago, when we were getting started.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I don&#39;t think it&#39;s compatible with the IETF =
ethos to say &quot;Changes to this document MUST NOT break existing code.&q=
uot; =A0Otherwise, we&#39;re not doing engineering here, we&#39;re cleaning=
 up documentation and rubber-stamping.<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">What would be acceptable is to say &quot;Changes mus=
t break cleanly with existing code&quot;. =A0That is, it should be possible=
 for a JWT implementation to, say, process both &quot;legacy&quot; JWS synt=
ax and whatever comes out of this group. =A0That way, we could
 come to consensus on the best solution, incorporating lessons learned from=
 earlier work without being hindered by them.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Would participants here consider it a acceptable for=
 the output of this working group to be incompatible with existing JWT impl=
ementations, as long as it had the property that JW* objects in the new for=
mat could be clearly distinguished
 from &quot;legacy&quot; JW* objects, so that implementations could adapt t=
heir processing?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 13, 2013 at 10:24 AM, George Fletcher &l=
t;<a href=3D"mailto:gffletch@aol.com" target=3D"_blank">gffletch@aol.com</a=
>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Helvetica&quot;,&quot;sans-serif&quot;">+1<br>
<br>
Breaking deployed code as raised by Brian, Naveen and others is a critical =
consideration.<br>
<br>
Thanks,<br>
George</span><u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 6/13/13 10:19 AM, Mike Jones wrote:<u></u><u></u>=
</p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Jim and Karen, could you =
please do as Richard suggests and close this issue as =93won=92t fix=94.</s=
pan><u></u><u></u></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 Thank you,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">mailto:rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Wednesday, June 12, 2013 1:57 PM<br>
<b>To:</b> <a href=3D"mailto:jose-chairs@tools.ietf.org" target=3D"_blank">=
jose-chairs@tools.ietf.org</a>; Mike Jones<br>
<b>Subject:</b> Fwd: [jose] #23: Make crypto independent of binary encoding=
 (base64)</span><u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">In other words: Chairs, feel free to close/wontfix :=
)<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">---------- Forwarded =
message ----------<br>
From: <b>Richard Barnes</b> &lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_bl=
ank">rlb@ipv.sx</a>&gt;<br>
Date: Wed, Jun 12, 2013 at 4:55 PM<br>
Subject: Re: [jose] #23: Make crypto independent of binary encoding (base64=
)<br>
To: &quot;Matt Miller (mamille2)&quot; &lt;<a href=3D"mailto:mamille2@cisco=
.com" target=3D"_blank">mamille2@cisco.com</a>&gt;<br>
Cc: jose issue tracker &lt;<a href=3D"mailto:trac%2Bjose@trac.tools.ietf.or=
g" target=3D"_blank">trac+jose@trac.tools.ietf.org</a>&gt;, &quot;&lt;<a hr=
ef=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" target=3D"=
_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt;&quot;
 &lt;<a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-encryption@tools.ietf.org</a>&gt=
;, &quot;&lt;<a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blan=
k">michael.jones@microsoft.com</a>&gt;&quot; &lt;<a href=3D"mailto:michael.=
jones@microsoft.com" target=3D"_blank">michael.jones@microsoft.com</a>&gt;,
 &quot;&lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a>&gt;&quot; &lt;<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@=
ietf.org</a>&gt;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">To be clear, I structured my message in two parts fo=
r a reason, to separate the analysis from the opinion. =A0I acknowledge tha=
t I am but one voice here, and I&#39;m increasingly hearing how alone I am =
:)<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 4:23 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">&lt;impartial-analysis&gt;<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">So just to be clear on the trade-off the WG has to m=
ake:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On the one hand: Breaking every existing JWT impleme=
ntation in the world<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On the other hand: Eternally binding ourselves to ba=
se64 encoding, even if binary-safe encodings become available (CBOR, MsgPac=
k, etc.)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/impartial-analysis=A0&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;personal-opinion&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have some sympathy with JWT implementors. =A0It su=
cks to have to refactor code. =A0But I think we&#39;re literally talking ab=
out something like a 5-line patch. =A0And early JWT implementors knew or sh=
ould have known (to use a DC phrase) that they
 were dealing with a draft spec. =A0As the W3C editor&#39;s draft template =
says, in big bold red print, &quot;Implementors who are not taking part in =
the discussions are likely to find the specification changing out from unde=
r them in incompatible ways.&quot;<u></u><u></u></p>


</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">As PHB pointed out in the other thread, it would be =
nice to use JWS and JWE in place of CMS one day, without the base64 hit. =
=A0We should incur the implementation pain now, and get the design right fo=
r the long run. =A0Base64 is a hack around
 JSON; we should build the system so that when we no longer need that hack,=
 it can go away.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;/personal-opinion&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard</span><u></u=
><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 12, 2013 at 10:27 AM, Matt Miller (mamil=
le2) &lt;<a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">mamille2@c=
isco.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">I did at first find it curious why the cryptographic=
 operations were over the base64url-enccoded values, but I was also very fo=
cused on JWE, where I think the field separation problem is less of an issu=
e (at least now). =A0For JWS, this would
 certainly cause problems without some manner of unambiguous field paramete=
rization.<br>
<br>
I will note that unescaped NULL is not valid in JSON, so it could be used a=
s a separator between the encoded header and the payload. =A0I do find it i=
nteresting if JOSE could more easily and efficiently support other encoding=
s. =A0However, I think that while this
 is an interesting thought experiment, it seems we&#39;re too far down the =
path to seriously consider it unless the current state were shown to be hor=
ribly broken.<br>
<br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank">ma=
mille2@cisco.com</a> &gt;<br>
Cisco Systems, Inc.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
On Jun 11, 2013, at 6:01 PM, jose issue tracker &lt;<a href=3D"mailto:trac%=
2Bjose@trac.tools.ietf.org" target=3D"_blank">trac+jose@trac.tools.ietf.org=
</a>&gt; wrote:<br>
<br>
&gt; #23: Make crypto independent of binary encoding (base64)<br>
&gt;<br>
&gt;<br>
&gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_=
blank">michael.jones@microsoft.com</a>):<br>
&gt;<br>
&gt; For both serializations, you already need the base64url encoded versio=
ns<br>
&gt; of the JWS Header and the JWS Payload to preserve them in transmission=
, so<br>
&gt; computing them isn&#39;t an extra burden. =A0In the JWS Compact Serial=
ization,<br>
&gt; you already need the concatenation of the Encoded JWS Header, a period=
<br>
&gt; character, and the Encoded JWS Payload, so computing that concatenatio=
n<br>
&gt; isn&#39;t an extra burden. =A0Given you already have that quantity, co=
mputing<br>
&gt; the signature over it is the easiest thing for developers to do, and i=
t&#39;s<br>
&gt; been shown to work well in practice. =A0There&#39;s no compelling reas=
on to make<br>
&gt; this change.<br>
&gt;<br>
&gt; Even for the JSON Serialization, the only &quot;extra&quot; step that&=
#39;s required to<br>
&gt; compute the signature is the concatenation with the period character -=
 to<br>
&gt; prevent shifting of data from one field to the other, as described by =
Jim<br>
&gt; Schaad in the e-mail thread. =A0So this step isn&#39;t actually &quot;=
extra&quot; at all -<br>
&gt; it&#39;s necessary. =A0It&#39;s also highly advantageous to use exactl=
y the same<br>
&gt; computation for both serializations, which is currently the case.<br>
&gt;<br>
&gt; Since there is no compelling reason to make this change, and since mak=
ing<br>
&gt; it could enable the &quot;shifting&quot; problem identified by Jim, it=
 should not be<br>
&gt; made.<br>
&gt;<br>
&gt; --<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt; Reporter: =A0<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.s=
x</a> =A0 | =A0 =A0 =A0 Owner: =A0draft-ietf-jose-json-web-<br>
&gt; =A0 =A0 Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:encryption@=
tools.ietf.org" target=3D"_blank">encryption@tools.ietf.org</a><br>
&gt; Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0new<br>
&gt; Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
&gt; =A0encryption =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 Version:<br>
&gt; Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution:<br>
&gt; Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
&gt; -------------------------+--------------------------------------------=
-----<br>
&gt;<br>
&gt; Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/tic=
ket/23#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac=
/ticket/23#comment:2</a>&gt;<br>
&gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">htt=
p://tools.ietf.org/jose/</a>&gt;<br>
&gt;<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; ________________=
_______________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<pre>_______________________________________________<u></u><u></u></pre>
<pre>jose mailing list<u></u><u></u></pre>
<pre><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><u=
></u><u></u></pre>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></pre>
</blockquote>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- <br>
<a href=3D"http://connect.me/gffletch" title=3D"View full card on
        Connect.Me" target=3D"_blank">&lt;XeC&gt;</a></span><u></u><u></u><=
/p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</blockquote>
</div></div></div>
</div>

</blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span c=
lass=3D"HOEnZb"><font color=3D"#888888">-- <br>Website: <a href=3D"http://h=
allambaker.com/" target=3D"_blank">http://hallambaker.com/</a><br>
</font></span></div>
</blockquote></div><br></div>

--089e01176a6d32abf304df65ae68--

From Michael.Jones@microsoft.com  Tue Jun 18 11:17:13 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66DC421E8098 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 11:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtwiykQvfcwR for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 11:17:08 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 9809C21E805D for <jose@ietf.org>; Tue, 18 Jun 2013 11:16:52 -0700 (PDT)
Received: from BL2FFO11FD023.protection.gbl (10.173.161.201) by BL2FFO11HUB039.protection.gbl (10.173.160.245) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 18 Jun 2013 18:10:09 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD023.mail.protection.outlook.com (10.173.161.102) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 18 Jun 2013 18:10:09 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Tue, 18 Jun 2013 18:09:57 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, Russ Housley <housley@vigilsec.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBU7rtA
Date: Tue, 18 Jun 2013 18:09:56 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367870F5D@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367870F5DTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51914003)(199002)(13464003)(189002)(35774003)(377454002)(56816003)(16236675002)(65816001)(4396001)(81342001)(512954002)(46102001)(221733001)(74366001)(54356001)(77982001)(71186001)(79102001)(74502001)(31966008)(53806001)(54316002)(76482001)(51856001)(80022001)(74662001)(81542001)(55846006)(59766001)(74876001)(16406001)(44976003)(50986001)(20776003)(66066001)(6806003)(69226001)(74706001)(47736001)(15202345002)(63696002)(56776001)(47976001)(76796001)(49866001)(47446002)(76786001)(77096001)(33656001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB039; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0881A7A935
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 18:17:13 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367870F5DTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the careful read, James.  Replies inline marked "Mike>"...



-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Man=
ger, James H
Sent: Sunday, June 16, 2013 6:20 PM
To: jose@ietf.org
Subject: [jose] Concat KDF



The use of the Concat KDF still does not look right.



JWA [draft-ietf-jose-json-web-algorithms-11] section 4.7 says "ECDH-ES" use=
s Concat KDF from NIST 800-56A section 5.8.1. NIST defines 5 fields that go=
 into the key derivation: AlgorithmID, PartyUInfo, PartyVInfo, SuppPubInfo,=
 and SuppPrivInfo.



NIST says AlgorithmID indicates the algorithm that will use the derived key=
. JWA says to use the "alg" value (eg "ECDH-ES") as the AlgorithmID. Algori=
thmID should actually be the "enc" value when the derived key is used direc=
tly as a CEK.



Mike> I can change the draft to use the "enc" value in the direct agreement=
 case, unless people object.



When the derived key unwraps the CEK, AlgorithmID should be the name of the=
 key wrap algorithm (eg "A128KW"). Perhaps the "alg" value can be used in t=
his case as it identifies the key wrap algorithm along with the key establi=
shment algorithm (eg "ECDH-ES+A128KW").



Mike> Agreed - so there is no change needed to the AlgorithmID for the agre=
ement with key wrapping case.



NIST says PartyUInfo includes an identifier for party U. The first problem =
is that JWA does not indicate if the sender or receiver is party U (nor doe=
s JWE). The second problem is that JWA says PartyUInfo is random -- which s=
eems to totally defeat the purpose of being an identifier for a party. JWA =
says PartyUInfo should vary for each recipient, which suggests PartyUInfo c=
annot be an id of the sender. Does that suggest the receiver is party U?



Mike> The sender is Party U.  I'll say so in the draft.  (This is parallel =
to RFC 2631's partyAInfo, which is also supplied by the sender.)



NIST says PartyVInfo is required and includes an identifier for party V. JW=
A says PartyVInfo is empty, which obviously cannot meet the NIST definition=
.



Mike> This was discussed at the in-person working group meeting in Denver a=
nd Jim Schaad stated that I should modify the Key Agreement parameters to m=
irror their use in RFC 2631, which I therefore did.  Jim, Russ, and James, =
can the three of you (and other interested working group members) please ma=
ke a decision among the three of you about text to include about PartyUInfo=
 and PartyVInfo?  If you don't reach an agreement, one option is for me to =
add a note to the spec that PartyUInfo is used in the same manner as PartyA=
Info of RFC 2631 and that since RFC 2631 doesn't have an equivalent of Part=
yVInfo, none is used here either.  The other option is to go back to the "a=
pu" and "apv" language of http://tools.ietf.org/html/draft-ietf-jose-json-w=
eb-algorithms-10 - adding that the sender is Party U and the receiver is Pa=
rty V.  Comments?



The JWA values for SuppPubInfo (length of derived key in bits) and SuppPriv=
Info (empty) are in line with the NIST definitions.



It appears the Concat KDF text in JWA has been rewritten based on RFC2631 "=
Diffie-Hellman Key Agreement Method". RFC2631 is not referenced by JWA, but=
 it is mentioned in the "document history" section (which will eventually b=
e deleted). RFC2631 has items such as partyAInfo and suppPubInfo whose name=
s are similar to NIST items. However, RFC2631 was published 7 years before =
NIST 800-56A (and 13 years before the current version of NIST 800-56A) so R=
FC2631 cannot be used as a example of how to use Concat KDF.



As I stated above, if we keep the current PartyUInfo/PartyVInfo usage, I wi=
ll explicitly add text saying that the usage of these fields is taken from =
RFC 2631.



--

James Manger

_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose



                                                                -- Mike



--_000_4E1F6AAD24975D4BA5B168042967394367870F5DTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Thanks for the careful read, James.&nbsp; Replies=
 inline marked &quot;<span style=3D"color:#558ED5;mso-style-textfill-fill-c=
olor:#558ED5;mso-style-textfill-fill-alpha:100.0%">Mike&gt;</span>&quot;&#8=
230;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Man=
ger, James H<br>
Sent: Sunday, June 16, 2013 6:20 PM<br>
To: jose@ietf.org<br>
Subject: [jose] Concat KDF</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The use of the Concat KDF still does not look rig=
ht.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">JWA [draft-ietf-jose-json-web-algorithms-11] sect=
ion 4.7 says &quot;ECDH-ES&quot; uses Concat KDF from NIST 800-56A section =
5.8.1. NIST defines 5 fields that go into the key derivation: AlgorithmID, =
PartyUInfo, PartyVInfo, SuppPubInfo, and SuppPrivInfo.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">NIST says AlgorithmID indicates the algorithm tha=
t will use the derived key. JWA says to use the &quot;alg&quot; value (eg &=
quot;ECDH-ES&quot;) as the AlgorithmID. AlgorithmID should actually be the =
&quot;enc&quot; value when the derived key is used directly as a
 CEK.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">Mike&gt; I can chan=
ge the draft to use the &#8220;enc&#8221; value in the direct agreement cas=
e, unless people object.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">When the derived key unwraps the CEK, AlgorithmID=
 should be the name of the key wrap algorithm (eg &quot;A128KW&quot;). Perh=
aps the &quot;alg&quot; value can be used in this case as it identifies the=
 key wrap algorithm along with the key establishment algorithm
 (eg &quot;ECDH-ES&#43;A128KW&quot;).<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">Mike&gt; Agreed &#8=
211; so there is no change needed to the AlgorithmID for the agreement with=
 key wrapping case.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">NIST says PartyUInfo includes an identifier for p=
arty U. The first problem is that JWA does not indicate if the sender or re=
ceiver is party U (nor does JWE). The second problem is that JWA says Party=
UInfo is random -- which seems to
 totally defeat the purpose of being an identifier for a party. JWA says Pa=
rtyUInfo should vary for each recipient, which suggests PartyUInfo cannot b=
e an id of the sender. Does that suggest the receiver is party U?<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">Mike&gt; The sender=
 is Party U. &nbsp;I&#8217;ll say so in the draft.&nbsp; (This is parallel =
to RFC 2631&#8217;s partyAInfo, which is also supplied by the
 sender.)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">NIST says PartyVInfo is required and includes an =
identifier for party V. JWA says PartyVInfo is empty, which obviously canno=
t meet the NIST definition.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">Mike&gt; This was d=
iscussed at the in-person working group meeting in Denver and Jim Schaad st=
ated that I should modify the Key Agreement
 parameters to mirror their use in RFC 2631, which I therefore did.&nbsp; <=
/span><span style=3D"color:red">Jim, Russ, and James</span><span style=3D"c=
olor:#558ED5;mso-style-textfill-fill-color:#558ED5;mso-style-textfill-fill-=
alpha:100.0%">, can the three of you (and
 other interested working group members) please make a decision among the t=
hree of you about text to include about PartyUInfo and PartyVInfo?&nbsp; If=
 you don&#8217;t reach an agreement, one option is for me to add a note to =
the spec that PartyUInfo is used in the same
 manner as PartyAInfo of RFC 2631 and that since RFC 2631 doesn&#8217;t hav=
e an equivalent of PartyVInfo, none is used here either.&nbsp; The other op=
tion is to go back to the &#8220;apu&#8221; and &#8220;apv&#8221; language =
of
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-1=
0"><span style=3D"color:#6666FF;mso-style-textfill-fill-color:#6666FF;mso-s=
tyle-textfill-fill-alpha:100.0%">http://tools.ietf.org/html/draft-ietf-jose=
-json-web-algorithms-10</span></a> -
 adding that the sender is Party U and the receiver is Party V.&nbsp; Comme=
nts?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">The JWA values for SuppPubInfo (length of derived=
 key in bits) and SuppPrivInfo (empty) are in line with the NIST definition=
s.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It appears the Concat KDF text in JWA has been re=
written based on RFC2631 &quot;Diffie-Hellman Key Agreement Method&quot;. R=
FC2631 is not referenced by JWA, but it is mentioned in the &quot;document =
history&quot; section (which will eventually be deleted).
 RFC2631 has items such as partyAInfo and suppPubInfo whose names are simil=
ar to NIST items. However, RFC2631 was published 7 years before NIST 800-56=
A (and 13 years before the current version of NIST 800-56A) so RFC2631 cann=
ot be used as a example of how to
 use Concat KDF.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">As I stated above, =
if we keep the current PartyUInfo/PartyVInfo usage, I will explicitly add t=
ext saying that the usage of these fields
 is taken from RFC 2631.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">--<o:p></o:p></p>
<p class=3D"MsoPlainText">James Manger<o:p></o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:jose@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
jose"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#558ED5;mso-style-textfill-f=
ill-color:#558ED5;mso-style-textfill-fill-alpha:100.0%">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:black"><o:p>&nbsp;</o:p></sp=
an></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367870F5DTK5EX14MBXC283r_--

From ietf@augustcellars.com  Tue Jun 18 12:20:55 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1FD21F996F for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 12:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.391
X-Spam-Level: 
X-Spam-Status: No, score=-2.391 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtzHkQbO6hKb for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 12:20:49 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 512A821F9954 for <jose@ietf.org>; Tue, 18 Jun 2013 12:20:45 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id EE1EE38F1B for <jose@ietf.org>; Tue, 18 Jun 2013 12:20:44 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Tue, 18 Jun 2013 12:19:50 -0700
Message-ID: <030f01ce6c58$ce3ba3e0$6ab2eba0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0310_01CE6C1E.21DD8F30"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5sWKIFoFlfi7UoTkS0MD1W5oz//A==
Subject: [jose] Minutes Posted
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 19:20:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0310_01CE6C1E.21DD8F30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The minutes from yesterday's teleconference have been posted.

 

Please review the content if you were on the call for correctness.

 

Please review the content if you were not on the call to see what we talked
about and plan to do. 

 

Jim

 


------=_NextPart_000_0310_01CE6C1E.21DD8F30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>The =
minutes from yesterday&#8217;s teleconference have been =
posted.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please review the content if you were on the call for =
correctness.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please review the content if you were not on the call =
to see what we talked about and plan to do. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0310_01CE6C1E.21DD8F30--


From ietf@augustcellars.com  Tue Jun 18 12:34:44 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B656621E80B6 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 12:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.541
X-Spam-Level: 
X-Spam-Status: No, score=-3.541 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odlJN6DqIMp9 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 12:34:40 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id F339D21E805D for <jose@ietf.org>; Tue, 18 Jun 2013 12:34:39 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 141A32CA0E for <jose@ietf.org>; Tue, 18 Jun 2013 12:34:38 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
References: <030f01ce6c58$ce3ba3e0$6ab2eba0$@augustcellars.com>
In-Reply-To: <030f01ce6c58$ce3ba3e0$6ab2eba0$@augustcellars.com>
Date: Tue, 18 Jun 2013 12:33:43 -0700
Message-ID: <032101ce6c5a$bed7e740$3c87b5c0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0322_01CE6C20.127A47C0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQG2IdQah9WotBlbtwc5Dqpv0gObB5lscbQA
Subject: [jose] FW:  Minutes Posted
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 19:34:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0322_01CE6C20.127A47C0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0323_01CE6C20.127A6ED0"


------=_NextPart_001_0323_01CE6C20.127A6ED0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

And I meant to include the pointer as well.

 

http://www.ietf.org/proceedings/interim/2013/06/17/jose/minutes/minutes-inte
rim-2013-jose-2

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 18, 2013 12:20 PM
To: jose@ietf.org
Subject: [jose] Minutes Posted

 

The minutes from yesterday's teleconference have been posted.

 

Please review the content if you were on the call for correctness.

 

Please review the content if you were not on the call to see what we talked
about and plan to do. 

 

Jim

 


------=_NextPart_001_0323_01CE6C20.127A6ED0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>And I meant to include the pointer as =
well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>http://www.ietf.org/proceedings/interim/2013/06/1=
7/jose/minutes/minutes-interim-2013-jose-2<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of =
</b>Jim Schaad<br><b>Sent:</b> Tuesday, June 18, 2013 12:20 =
PM<br><b>To:</b> jose@ietf.org<br><b>Subject:</b> [jose] Minutes =
Posted<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The minutes =
from yesterday&#8217;s teleconference have been posted.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the content if you were on the call for =
correctness.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please review the content if you were not on the call =
to see what we talked about and plan to do. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_001_0323_01CE6C20.127A6ED0--

------=_NextPart_000_0322_01CE6C20.127A47C0
Content-Type: text/plain;
	name="ATT00001.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="ATT00001.txt"

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

------=_NextPart_000_0322_01CE6C20.127A47C0--


From trac+jose@trac.tools.ietf.org  Tue Jun 18 14:13:13 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705B621F9AEB for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qNNaLV4d-SIp for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:13:13 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id C6FC121F9AE2 for <jose@ietf.org>; Tue, 18 Jun 2013 14:13:12 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54380 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Up3D1-0000e7-Um; Tue, 18 Jun 2013 23:12:59 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ietf@augustcellars.com, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Tue, 18 Jun 2013 21:12:59 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/8#comment:3
Message-ID: <069.7d32fd102a44a0c5aa7ffea7f50578b2@trac.tools.ietf.org>
References: <054.96c0b71d4934f695a54309d767dbf877@trac.tools.ietf.org>
X-Trac-Ticket-ID: 8
In-Reply-To: <054.96c0b71d4934f695a54309d767dbf877@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, ietf@augustcellars.com, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130618211312.C6FC121F9AE2@ietfa.amsl.com>
Resent-Date: Tue, 18 Jun 2013 14:13:12 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #8: Direct mode for key agreement needs security analysis
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:13:13 -0000

#8: Direct mode for key agreement needs security analysis

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 There is now a constrained device use case that appears to need this
 ability.  There are no known additional security considerations that would
 need to be written.  There are potentially some considerations that need
 to be made for longer term private keys, but they are different that for
 MAC keys.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  rbarnes@bbn.com        |  encryption@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:  wontfix
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/8#comment:3>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Tue Jun 18 14:15:16 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE9EF21F9AF9 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79YIdFW5A+Zk for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:15:16 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 31A2B21F9AEB for <jose@ietf.org>; Tue, 18 Jun 2013 14:15:16 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54598 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Up3F6-0003Fi-0n; Tue, 18 Jun 2013 23:15:08 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 18 Jun 2013 21:15:08 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/20#comment:2
Message-ID: <064.4ff2fee9d95bfba8a98cd1cdc9a85f48@trac.tools.ietf.org>
References: <049.92c9829790c8d5776a0efee36c11df4c@trac.tools.ietf.org>
X-Trac-Ticket-ID: 20
In-Reply-To: <049.92c9829790c8d5776a0efee36c11df4c@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130618211516.31A2B21F9AEB@ietfa.amsl.com>
Resent-Date: Tue, 18 Jun 2013 14:15:16 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #20: Shorter names for JSON serialization
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:15:17 -0000

#20: Shorter names for JSON serialization

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Per the discussion on the list and at a tele-chat, the two indicated above
 have been changed and the rest will remain as is.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  minor        |      Status:  closed
Component:  json-web-    |   Milestone:
  encryption             |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/20#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Tue Jun 18 14:15:44 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBA621F965B for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHcNxg+N+jeG for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:15:43 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF7E21F8EC3 for <jose@ietf.org>; Tue, 18 Jun 2013 14:15:38 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54621 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Up3FT-0003zj-IC; Tue, 18 Jun 2013 23:15:31 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 18 Jun 2013 21:15:31 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/22#comment:2
Message-ID: <072.f93423dc7c405aa819feee5f37020626@trac.tools.ietf.org>
References: <057.d511828d9b6553c2cb165ff15b303f78@trac.tools.ietf.org>
X-Trac-Ticket-ID: 22
In-Reply-To: <057.d511828d9b6553c2cb165ff15b303f78@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130618211539.5DF7E21F8EC3@ietfa.amsl.com>
Resent-Date: Tue, 18 Jun 2013 14:15:38 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #22: JSON Serialization media types not consistent with RFC 6839
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:15:45 -0000

#22: JSON Serialization media types not consistent with RFC 6839

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => fixed


-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  mamille2@cisco.com     |  encryption@tools.ietf.org
     Type:  defect       |      Status:  closed
 Priority:  minor        |   Milestone:
Component:  json-web-    |     Version:
  encryption             |  Resolution:  fixed
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/22#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Tue Jun 18 14:16:00 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB5621F9928 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UG89II0ifv0R for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:15:59 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 96A7721F9733 for <jose@ietf.org>; Tue, 18 Jun 2013 14:15:59 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54651 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1Up3Fs-0004wA-Ku; Tue, 18 Jun 2013 23:15:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-key@tools.ietf.org, michael.jones@microsoft.com,  ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 18 Jun 2013 21:15:56 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/21#comment:2
Message-ID: <072.7a894d16efe904136f1f52661f48dead@trac.tools.ietf.org>
References: <057.3a020ce8d5a302c89bd1b870e2763fec@trac.tools.ietf.org>
X-Trac-Ticket-ID: 21
In-Reply-To: <057.3a020ce8d5a302c89bd1b870e2763fec@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-key@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20130618211559.96A7721F9733@ietfa.amsl.com>
Resent-Date: Tue, 18 Jun 2013 14:15:59 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #21: JWK and JWKSet do not have media types registered
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:16:00 -0000

#21: JWK and JWKSet do not have media types registered

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => fixed


-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  mamille2@cisco.com     |  key@tools.ietf.org
     Type:  enhancement  |      Status:  closed
 Priority:  minor        |   Milestone:
Component:  json-web-    |     Version:
  key                    |  Resolution:  fixed
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/21#comment:2>
jose <http://tools.ietf.org/jose/>


From Michael.Jones@microsoft.com  Tue Jun 18 14:36:50 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49EAF21E80A6 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level: 
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2-ZOFrB1faA for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:36:45 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id EDF7711E8109 for <jose@ietf.org>; Tue, 18 Jun 2013 14:36:44 -0700 (PDT)
Received: from BN1BFFO11FD014.protection.gbl (10.58.52.201) by BN1AFFO11HUB007.protection.gbl (10.58.52.117) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 18 Jun 2013 21:36:42 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD014.mail.protection.outlook.com (10.58.53.74) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 18 Jun 2013 21:36:41 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Tue, 18 Jun 2013 21:36:12 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] FW:  Minutes Posted
Thread-Index: AQHObFsbQpA1oNL3OkOUtMqOGukAhpk7/SLA
Date: Tue, 18 Jun 2013 21:36:11 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436787188B@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <030f01ce6c58$ce3ba3e0$6ab2eba0$@augustcellars.com> <032101ce6c5a$bed7e740$3c87b5c0$@augustcellars.com>
In-Reply-To: <032101ce6c5a$bed7e740$3c87b5c0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.70]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436787188BTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(377454002)(189002)(46102001)(49866001)(55846006)(76796001)(77982001)(56816003)(512954002)(47736001)(15202345002)(20776003)(66066001)(77096001)(65816001)(71186001)(50986001)(74876001)(69226001)(31966008)(16236675002)(53806001)(4396001)(51856001)(47976001)(76786001)(6806003)(81342001)(79102001)(56776001)(47446002)(16406001)(80022001)(54356001)(33656001)(54316002)(59766001)(63696002)(74706001)(74502001)(74366001)(74662001)(76482001)(81542001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB007; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0881A7A935
Subject: Re: [jose] FW:  Minutes Posted
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:36:50 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436787188BTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree with that's there.  One thing we discussed is missing, however.  I =
would request that this be added to the minutes:

Mike asked why issue #6 (Unclear requirements levels on fields) has not bee=
n closed as fixed.  He pointed out that text to resolve this issue was incl=
uded in the -09 drafts, which were quite some time ago, and no one has asse=
rted that those text changes were insufficient or incorrect.  Jim said that=
 Richard Barnes had agreed to produce a table of fields to include as suppl=
emental text for this issue at the Denver interim meeting but had not yet d=
one so.

                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Tuesday, June 18, 2013 12:34 PM
To: jose@ietf.org
Subject: [jose] FW: Minutes Posted

And I meant to include the pointer as well.

http://www.ietf.org/proceedings/interim/2013/06/17/jose/minutes/minutes-int=
erim-2013-jose-2

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Tuesday, June 18, 2013 12:20 PM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Minutes Posted

The minutes from yesterday's teleconference have been posted.

Please review the content if you were on the call for correctness.

Please review the content if you were not on the call to see what we talked=
 about and plan to do.

Jim


--_000_4E1F6AAD24975D4BA5B16804296739436787188BTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I agree with that&#821=
7;s there.&nbsp; One thing we discussed is missing, however.&nbsp; I would =
request that this be added to the minutes:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"color:#1F4=
97D">Mike asked why issue #6 (Unclear requirements levels on fields) has no=
t been closed as fixed.&nbsp; He pointed out that text to resolve this issu=
e was included in the -09 drafts, which were
 quite some time ago, and no one has asserted that those text changes were =
insufficient or incorrect.&nbsp; Jim said that Richard Barnes had agreed to=
 produce a table of fields to include as supplemental text for this issue a=
t the Denver interim meeting but had
 not yet done so.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 18, 2013 12:34 PM<br>
<b>To:</b> jose@ietf.org<br>
<b>Subject:</b> [jose] FW: Minutes Posted<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And I meant to include=
 the pointer as well.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"http://www.=
ietf.org/proceedings/interim/2013/06/17/jose/minutes/minutes-interim-2013-j=
ose-2">http://www.ietf.org/proceedings/interim/2013/06/17/jose/minutes/minu=
tes-interim-2013-jose-2</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 18, 2013 12:20 PM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> [jose] Minutes Posted<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The minutes from yesterday&#8217;s teleconference ha=
ve been posted.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the content if you were on the call fo=
r correctness.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the content if you were not on the cal=
l to see what we talked about and plan to do.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436787188BTK5EX14MBXC283r_--

From ietf@augustcellars.com  Tue Jun 18 14:40:17 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70DEE21E80AD for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.544
X-Spam-Level: 
X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZV8z7w7i9jVu for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 14:40:12 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7F06521E8099 for <jose@ietf.org>; Tue, 18 Jun 2013 14:40:12 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id BD1282CA11; Tue, 18 Jun 2013 14:40:11 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Manger, James H'" <James.H.Manger@team.telstra.com>, <jose@ietf.org>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>
Date: Tue, 18 Jun 2013 14:39:17 -0700
Message-ID: <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwZhsufVw
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 21:40:17 -0000

I have gone back a re-read the NIST document from the top, and there are
going to be some problems with trying to comply with them in some cases.

Let's look at the fields from top to bottom

AlgorithmID - I would agree that this should be alg in the case of doing a
key wrap key and enc in the case of doing a CEK.

Identities of PartyU and PartyV - these are well known as PartyU is always
the initiator and PartyV is always the acceptor.  In a store and forward
environment where we are doing static-ephemeral the ephemeral is always
associated with PartyU.  I do not believe that this needs to be made
explicit in the document but that can be addressed later.

IDs - there is a problem with what to use for identifiers in for the JOSE
work.  In many cases there is just a key and not necessarily a well-defined
identifier that both parties are going to agree on.  This is something that
we cannot really do at present because there is no name component of a JWK
and any other name is going to be based on the application and not on what
is known to the JOSE library.  It is even harder because the sender can,
with an ephemeral key, want to remain anonymous and therefore the recipient
has no agreed upon identifier with the sender.

In theory, the names used should not need to be transmitted as part of the
message as it is assumed that both parties will understand what the
identifiers are (or they will have exchanged them in an online protocol).
One possible course is to say that by default the names "Sender" and
"Receiver" will be used as the identifiers unless other names are provided
by the application protocol.  In this case they would not need to be
transmitted as they are known to each entity.

There is also a requirement for a nonce to be sent for a simple
static-static case, this is not a current requirement and would be defined
for the case of a static-static algorithm.  I don't believe that we need to
define the 'nonce' field to carry this value at this time.

Jim


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> Manger, James H
> Sent: Sunday, June 16, 2013 6:20 PM
> To: jose@ietf.org
> Subject: [jose] Concat KDF
> 
> The use of the Concat KDF still does not look right.
> 
> JWA [draft-ietf-jose-json-web-algorithms-11] section 4.7 says "ECDH-ES"
> uses Concat KDF from NIST 800-56A section 5.8.1. NIST defines 5 fields
that
> go into the key derivation: AlgorithmID, PartyUInfo, PartyVInfo,
> SuppPubInfo, and SuppPrivInfo.
> 
> NIST says AlgorithmID indicates the algorithm that will use the derived
key.
> JWA says to use the "alg" value (eg "ECDH-ES") as the AlgorithmID.
> AlgorithmID should actually be the "enc" value when the derived key is
used
> directly as a CEK. When the derived key unwraps the CEK, AlgorithmID
should
> be the name of the key wrap algorithm (eg "A128KW"). Perhaps the "alg"
> value can be used in this case as it identifies the key wrap algorithm
along
> with the key establishment algorithm (eg "ECDH-ES+A128KW").
> 
> NIST says PartyUInfo includes an identifier for party U. The first problem
is
> that JWA does not indicate if the sender or receiver is party U (nor does
> JWE). The second problem is that JWA says PartyUInfo is random -- which
> seems to totally defeat the purpose of being an identifier for a party.
JWA
> says PartyUInfo should vary for each recipient, which suggests PartyUInfo
> cannot be an id of the sender. Does that suggest the receiver is party U?
> 
> NIST says PartyVInfo is required and includes an identifier for party V.
JWA
> says PartyVInfo is empty, which obviously cannot meet the NIST definition.
> 
> The JWA values for SuppPubInfo (length of derived key in bits) and
> SuppPrivInfo (empty) are in line with the NIST definitions.
> 
> 
> It appears the Concat KDF text in JWA has been rewritten based on RFC2631
> "Diffie-Hellman Key Agreement Method". RFC2631 is not referenced by JWA,
> but it is mentioned in the "document history" section (which will
eventually
> be deleted). RFC2631 has items such as partyAInfo and suppPubInfo whose
> names are similar to NIST items. However, RFC2631 was published 7 years
> before NIST 800-56A (and 13 years before the current version of NIST 800-
> 56A) so RFC2631 cannot be used as a example of how to use Concat KDF.
> 
> --
> James Manger
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From Michael.Jones@microsoft.com  Tue Jun 18 15:54:12 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3291511E810D for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 15:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEpqvm0sYm4e for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 15:54:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id DD39511E80E1 for <jose@ietf.org>; Tue, 18 Jun 2013 15:54:09 -0700 (PDT)
Received: from BY2FFO11FD027.protection.gbl (10.1.15.202) by BY2FFO11HUB001.protection.gbl (10.1.14.143) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 18 Jun 2013 22:54:06 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD027.mail.protection.outlook.com (10.1.15.216) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 18 Jun 2013 22:54:06 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Tue, 18 Jun 2013 22:53:32 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Working Group Last Call - draft-ietf-jose-use-cases
Thread-Index: Ac5dUMKDhU7SKzvyR8Su23stBdI8HgPIre1g
Date: Tue, 18 Jun 2013 22:53:32 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367872E2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
In-Reply-To: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.19]
Content-Type: multipart/mixed; boundary="_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(377454002)(20776003)(56816003)(81342001)(76482001)(74502001)(53806001)(6806003)(76796001)(31966008)(56776001)(63696002)(47736001)(4396001)(47976001)(74876001)(47446002)(54316002)(46102001)(54356001)(79102001)(74662001)(80022001)(50986001)(59766001)(33656001)(69226001)(77982001)(512954002)(15202345002)(74706001)(51856001)(49866001)(77096001)(65816001)(71186001)(74366001)(55846006)(44976003)(66066001)(81542001)(16406001)(16236675002)(76786001)(568964001)(552614006)(563144002); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB001; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0881A7A935
Subject: Re: [jose] Working Group Last Call - draft-ietf-jose-use-cases
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 18 Jun 2013 22:54:12 -0000

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: multipart/alternative;
	boundary="_000_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_"

--_000_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

My last call comments are attached in the form of changes applied relative =
to the -02 source.  They can all be easily seen as tracked changes in the a=
ttached .docx version.  Most are editorial in nature, however there are a f=
ew factual corrections also applied.  Those were:


*         Make it clear that the application may specify another means or c=
onvention to determine the key used.

*         Corrected "JWT" -> "OAuth" in the sentence "In OAuth, the "client=
_id" parameter identifies the key to be used."

*         Don't say that OAuth is used in Mozilla Persona.

*         I reverted the "S1" Security Requirements text to the -01 version=
, since the -02 text would prohibit the direct encryption use case.

Once these changes are applied and Ludwig Seitz' direct encryption use case=
 is added, I'm good with seeing the document progress.

                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Thursday, May 30, 2013 9:16 AM
To: jose@ietf.org
Subject: [jose] Working Group Last Call - draft-ietf-jose-use-cases
Importance: High

<chair>

This message starts the Working Group Last Call on the Use Cases document.

Minor issues should be sent to the list

Major issues (those that should block the document from proceeding to the I=
ESG) should be sent to the list and an issue created in the tracker.

The final day for Last Call comments is June 16, 2013


Jim


--_000_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1746757119;
	mso-list-type:hybrid;
	mso-list-template-ids:610946936 67698689 67698691 67698693 67698689 676986=
91 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">My last call comments =
are attached in the form of changes applied relative to the -02 source.&nbs=
p; They can all be easily seen as tracked changes in the attached .docx ver=
sion.&nbsp; Most are editorial in nature, however
 there are a few factual corrections also applied.&nbsp; Those were:<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Make it clear =
that the application may specify another means or convention to determine t=
he key used.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Corrected &#82=
20;JWT&#8221; -&gt; &#8220;OAuth&#8221; in the sentence &#8220;In OAuth, th=
e &#8220;client_id&#8221; parameter identifies the key to be used.&#8221;<o=
:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Don&#8217;t sa=
y that OAuth is used in Mozilla Persona.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I reverted the=
 &#8220;S1&#8221; Security Requirements text to the -01 version, since the =
-02 text would prohibit the direct encryption use case.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Once these changes are=
 applied and Ludwig Seitz&#8217; direct encryption use case is added, I&#82=
17;m good with seeing the document progress.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Thursday, May 30, 2013 9:16 AM<br>
<b>To:</b> jose@ietf.org<br>
<b>Subject:</b> [jose] Working Group Last Call - draft-ietf-jose-use-cases<=
br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&lt;chair&gt;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This message starts the Working Group Last Call on t=
he Use Cases document.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Minor issues should be sent to the list<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Major issues (those that should block the document f=
rom proceeding to the IESG) should be sent to the list and an issue created=
 in the tracker.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The final day for Last Call comments is June 16, 201=
3<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_--

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document;
	name="draft-ietf-jose-use-cases-02+Mike diffs.docx"
Content-Description: draft-ietf-jose-use-cases-02+Mike diffs.docx
Content-Disposition: attachment;
	filename="draft-ietf-jose-use-cases-02+Mike diffs.docx"; size=67830;
	creation-date="Tue, 18 Jun 2013 22:48:19 GMT";
	modification-date="Tue, 18 Jun 2013 22:50:15 GMT"
Content-Transfer-Encoding: base64

UEsDBBQABgAIAAAAIQBJn4PiqwEAAJcGAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC0
lc1u2zAQhO8B+g4Cr4FEJ4eiKCznkCbH1EAdpFeaWtlE+QfuOrHfvivZFpxWtdw4uQiQyJ35OOCu
xjdrZ7NnSGiCL8VVMRIZeB0q4xeleJzd519EhqR8pWzwUIoNoLiZfLoYzzYRMONqj6VYEsWvUqJe
glNYhAieV+qQnCJ+TQsZlf6lFiCvR6PPUgdP4CmnRkNMxt+gVitL2d2aP29JElgU2e12Y+NVChWj
NVoRk8pnX/3hku8cCq5s9+DSRLxkDCF7HZqVfxvs6r5zNMlUkE1VogflGEO+hFTJKuiV4zMUx2V6
OENdGw1dfaMWU9CAyJk7W3QrThm/5+/j0Cuk4H46Kw2Bm6YQ8epsnE600YNEBroM+xjaLPzKzSEx
/dnuf4XRSR8LooVA2ljA9yfY6p5o/2RoeVfXoPnWD18Mh3mDXmwtDmqH3YCI8z7F5HUv5kO3D3fK
gwgvMP/xYRQH4oMgNc+ImZpbOCHx/wyjkx6EIB58INvn+T3Yyhyz5BHRtjsP0vSGY+8nZVOd8+w5
oc87Rx7CZ+cMzZivoOrxlu1vZfIbAAD//wMAUEsDBBQABgAIAAAAIQAekRq38wAAAE4CAAALAAgC
X3JlbHMvLnJlbHMgogQCKKAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAjJLbSgNBDIbvBd9hyH032woi0tneSKF3IusDhJnsAXcOzKTavr2j
ILpQ217m9OfLT9abg5vUO6c8Bq9hWdWg2JtgR99reG23iwdQWchbmoJnDUfOsGlub9YvPJGUoTyM
Maui4rOGQSQ+ImYzsKNchci+VLqQHEkJU4+RzBv1jKu6vsf0VwOamabaWQ1pZ+9AtcdYNl/WDl03
Gn4KZu/Yy4kVyAdhb9kuYipsScZyjWop9SwabDDPJZ2RYqwKNuBpotX1RP9fi46FLAmhCYnP83x1
nANaXg902aJ5x687HyFZLBZ9e/tDg7MvaD4BAAD//wMAUEsDBBQABgAIAAAAIQB3GRqDVQcAAIxH
AAAcAAgBd29yZC9fcmVscy9kb2N1bWVudC54bWwucmVscyCiBAEooAABAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAMxcbY+bRhD+Xqn/4cR33g22ozixlKZSW1WqLhe13yoMa5s7YMnucj7313eW
M45JgHg4WE7KRTGOuZnd2WeeZ2bw2/dPaXLzSBiPabbSbMPSbkgW0ijOdivt892v+kK74SLIoiCh
GVlpR8K19+9+/untLUkCAR/i+zjnN3CXjK+0vRD5G9Pk4Z6kATdoTjJ4Z0tZGgh4yXZmHoQPwY6Y
jmX5Jru8h/auds+b36KVxn6LHF+7uTvm8Kt/fHO63cYh+YWGRUoy0fA7zD3ciSVx9gA3DdiOiPNt
D4eDcXBLG+9u4aO2Y3641cH6iMc7PaSMOLq8Cn9m1Yf/pBHY9fFJEJYFiWa2eGCr8UBQmnAjJmJb
erEXaWKybejPZ0ucwa50UMGSNxkcsWArdOmEfk850e85zfQD2ehBsqMsFvuU67Zc0HL3rtuAmaPG
HxlC5+WPMxkVROilR9xsdeyBHMEjI4+2SK/mr8srGhRi/3W/BH0gmW4tDPEkcI55gEEqwu/a7To5
dhD6hgSMMN3yejjljexUGsSJoG/CIBOUGc6a8sIgUYFbet9VY+X9bv2MtUjzIBmNGhmnRRRxukl6
WThXmK0A23USxXK7ZWaFl/LHWdg9ztxiQsgHo2euhcT0hcxpE+UoMNhzHZlUEEloOShcb2km7oJN
QiojVtr5kgGkpY2LDGpEO5lqyuxym31HGoBYtbki7iRzARjYdJ582zdyjjN7qYhxwE4bjHBasJCU
IJAXmyQuccCE9yQeyEgtIwK17oPanxXphjBQFNUirrTzpa5gtScHU8/3HHyudxRhU12y2Mvlwrz9
+EFqFl2+sBzbMqslv44pl8x6OlSdLbFSpdRiCgxuxwd/7ln4EHEHPWA4IL5QIoGgYaAz8qWIGZGa
meuWpIAIhHYnTCkXntTFIpQw2DGX5Qm8WFSkPppSZKs/zxoRtzGzsRXHqR5zrYyq7xAUVbJAFIz0
0r7e2DoF6duzRORBmjiVSATWgFe+ivQNeSRGGiSErXmRGSFNcZHlj52XTzIMSohlFWWdByw0ngij
T3hj54qUzRVUzJFUEv4fbrXnY7OJ02pzkRMoWa3vgw2wNckmcXYuFCWC9lTsObM+hw7cHIxBcCIE
EN2zXFhp1ZUuouurUDkcCvMRnPwEqvLMSOl/cZIEpWiAOt3nT2ZEQ27+BZ0AmgXInVdEZrqOWFXt
dpeOa8gXOBeWirJ+R/BKnYbOGEtFSV4Gh0EBj7kumzpl2Bz4lkQm/BBWdoLMR9twTMrNA9e/XtXh
os5zEuqU99gYe2z0O2X6JjoG6tmfWzInI/iwrSjfdESStXDxkVTWswbDwXZF0m63bFT1sFth2mns
D4LWKNuD9nN70LWxAkoR9DRF+IXgCKB7oOeMgiKkUD+QFA8R9a4iHJLRg2+x1XqH+BCbKVIbP9ih
dgGF26vZ2Cqjl3g6N3rPjUN0R9RTpEt+p/vM+IOk+TqjD3GA1yT+2DmiElB0V0AfiyVGRMIeZk6b
e6VcwkX2XFEuaDqoQBZcx5IGIGBT4Uls7m7IjgweED0VegXkyrVo39ShR6PHXJGKaSdAZX0Abfdi
Qv4ggx4EFzLoFXKFlqiHdjM+6pcT0gDww5uXxw6BLstB4UXATB+pdnqllS/N8m+7q7Yx6KJxcUxg
APGEsVBcKV93/Xp78lMtm1r4YLOnTWU+DDpWy3xd69BReKobddiL5zTdQUO1WwFfo2Eam3P4SHIH
RYGXu1WXMbVOHd652diUv6M8dCGeW2YfcSfIU0S3m2p5nIQFTNceTdnDMh8dwyr/VRY2dHgli3do
ZuKPjWEnmZMHRZKQdRqHjHK6FXilU4LdxMWvPqOys1dGxOtn+zTZjC5qe2PL414Fim+7u/jjMDYV
OR2HbUwS+fzGOoaafRHG+DHguSJJ8QMphA6cuSIO0qL/5egtDvIXiihHV+cM3pNzgmXjDN2cXoxN
LiqIhynHLA4f1l+KIIGBhRSP8UtFWNm11lWXshzK7NGlHJvtnFabJZt1nD8a/AkXzoOucFhwQdN/
vnZyV5phmOerZixI2qk8B10seATp03e9/YuLnRp0WliSQ6y4fSwrOgroUAuOypFKpMFjw9AFY2gU
ny9uAg4arEOLtHr/DE18yqHeicLpe5F2+RwXLso8RXqG5fs4yakQa8aDSpnhE549OYub+bMezyK5
g6aRl5+FbzvjPaoUr0zQ1GVabRQXzbnL3PJaDvc3Gg13vH1F50UOUMWRAc8Gm3IuipvPF6DWkmUk
FHpKOIdH5OE553+tHhNT/thso5KZ7Ajl94d+j0m+At1TcfGy64bn4nOFlKO5iyXbzXgsWihE1xa7
5YgmGmcWihhSCyeVs8U4OFkqBP3mhZYdQ/xCt5ldK6+az1+1Ib9iY17/Gg/zuSf3N3xVw8ftFvDs
u3bdxVtdqklRNbxlvyV1we13Ofc3USKE/fdg6hNp8OQIJruM+AB1FUXGtdMndTZVb2h1aiWz9h06
7/4HAAD//wMAUEsDBBQABgAIAAAAIQBgAtbISq0AAFiHBgARAAAAd29yZC9kb2N1bWVudC54bWzs
fdty28iW5ftEzD8g2A9tR4g0dbWtc6QOWpbLclm2R1SVq7p74gQIgCJKIMADgJJVT/0hMxH1Nv9R
n9JfMmvtTFwJUpR1I1So023xAiYSmTv3fa/993/7NvaMCyeM3MDfa613ui3D8a3Adv2zvdZPp+/a
r1pGFJu+bXqB7+y1rpyo9W/7//N//P1y1w6s6djxYwND+NHu5cTaa43ieLL74kVkjZyxGXXGrhUG
UTCMO1YwfhEMh67lvLgMQvvFRne9K68mYWA5UYT7HZj+hRm19HDj2dGCiePjXsMgHJtx1AnCsxdj
MzyfTtoYfWLG7sD13PgKY3d3kmGCvdY09Hf1hNrphPiTXTUh/Sf5RTjzFBX3Vb98q1dA7vgidDzM
IfCjkTvJHuN7R8MjjpIpXSx6iIuxl1x3OVnfmrlf+sjL7MHb0LzEVmQDzgxXsRi2+tHYU+vA/c12
tTzienfRw+gd4RDpHJaZQvGeyUzGpuunw3zf0uQXFyfiNvT9QxhMJ+l0Ju7tRjvyz9OxeDBvMLPu
jpy8/KNFNxpg5uj2R+bEaRlja/fozA9Cc+BhRpfrWwYpsrUPZjEwrfMzLIBvG5e7VuAFOGbv5L/W
C/k+sK/4Nx54+s+XUL+YfAnxG88Zxu/CYHzqfIv3WlvbLXwWumejmQ/BzOKeb414hxgX80KMOvml
P3HAU+Q3yWe/qs8scDEnVBPBpV/xi0veA8wQv72a4GHsb2b6/YHjef2JaeGgqCvXZTbVFx6b8hyc
vrq4alCZ1LyvX8j8eVM9Fqb4MQjOcf2F6e21uls9GXPohlF8EmDm65y3Z+p32ZcHgTcdk80n3ycf
yCV+8P4NGD0G5Nd+8LN6t54+91snskJ3Qh6X3Nszr4JpzCvULNNN+yF0be7fGf7iLrge89rZ2cgu
Ta6IQ3wJ+WOf4M7dgzfbW9hc2fpQjWa7F0ekGnnY9a2tV9tbO9svX+tphe8dUkHy/cbGdjrfZfaJ
09b3iS25q6WfwVpIBtEonZLlOWbIJdNkbU7jgG+Hrofdef26i//UnC56nnuWrl2e6kau7WB3z/VC
6jlMMEp5ZZKP3jpDc+rhKHS7L7e7r95syprhrPAhopQ6Bw7EJehX9lS96WF++gL9uTkE+edfz17i
uWQyXF1MgG9OpjzjZvzRAZ2px/vNwneyS/lH06sbvgv8OMIFZmS54H0/O6Ft+iaH4wi9yDX3Wqfu
2ImMT86lcRKMTfDuy91Rz49ylwuzkIVO7pVxEeyl3Ax/9TrIYjz8BLD3nn0wMkPMUb86FS4ycM4g
kdQmq7lxtx5jgq4fxSF5KdUtoRfs5iR0Iie8cFr7xvtfvxyefDz69KPRahn/6RmtOLBaBk95+ks5
84/7FHOWOXImZmjGzrIrfRz4piVndhlS1FcLJQ7UvwfRIrrEefw9odYNzQqi3w94GOS0qM8S6gVD
2v/zj9PPB3/+IUx1dZfZ8e1shXnolBQAG8WbGJTBP6k8F+Y68FIJodnr5ia4I1ZCSc+JpXkJfjfD
vnPXlcVxI2VzUnb95Su9L1jFOxKzS22HbHsiPiuFaW4LRUzKsbmpWMxoqkxM2xS1yxHTy+y6OcQU
B5S/UFs2c2Om12YKXeXXgyCOg/GC3+dUvooB1Ml5CjrfZveVVtUKqmDysXrQpYm0ii3M7uT1dLi+
k1fuU66ztFa3I//xlEFDWWndTaY4R8Poha4J58FyGlh6sQVjUb25O6GHHVtCZUunsIyYTi++j/lS
SH/43D8sSWjoRlhNN7GhwOLEDD12z2Edw2MGnQRKdHd9s93daa+/Ol3f3t16udvt/ntL9ED5R/G0
srqcPs0qPPocnfFrEJ7TJhZHR2FlsL1YGlEIMiUBa1htcTWHkwbS6ux4HQ/nScd4Y4a+E5XpMKM/
kRKipYQ4m3Ps7FPaxd13vc3trQ05pKm3oEIjaiTRIi9C3STRAD62MXwy/dgM6V8iWxfPmW+Owcb/
8UPwBk5N8nX4I97R+aZdKHj7ES4NcHqlICgbuQZ8ff+IflDfidvw2g/j+UenYd16Z1d9U+vIut+8
+WScOtbIR5TgzF2KgydH9VDCC+qgCru51rncGBQ3dQbXjY3Xi/v6tmMz4B5Po13jyFexbgRcTK/h
xgsiFHUjStthSIyMaoMKxBM1FPGUDDHsH5tXxsZrEnDyCV/jYKpPqINnlvPmE14QOA2mvmOsy1rE
8vxqFcQ6liWZGw5aHXuQzo81g26M+TwJO8sIAP8FfZeNK/VF6r2d8fQ3htRTMqRqI4Gr/VqH3yYu
AqO7Ev1MD63wMs3Dt54wy0o49qfgwhkPnNDY7C7JyCVV4IlKtnj/rWOp9dhYL3PBJ8fMG3O/Mfd3
7yuMUkpzgOIw46KlMqHyCJbMiMplkd1PRtQie+POMpuYOKZSx7AAhcymO1mk2bSxST++8hwINUlL
ee+YTAPX+X8Ls/DK8cX5QSpZOM+UzEm5i5PmQ1Ed5INpnxp1xDsbFwmoodw63v8pcowDM0KeGZId
jRPnn1NId+axRwasbeND//Mn4/PgN8eKjT6y9RjQ4oWHvhVeqdzHZxWRPyQ8B8PDkMquymQ5C82x
eI4X+IC/e5lwk/3nBbGDdauaARxi93P/dDmR/D2M264TD9u/BZHTnuL/LS5vuzS/zORFcv7dmLy3
WL9ErelucJrJO75WVIhPimapmCR3oc3cYtLxfnfG5MrFVUEDWNiyrZV8tDBhtPLkbyrSqfvJj/d7
AyQ7mlZVQOPO1uwTq1K8r87gOxZtNiX22qzXTDYw0/s72em93Rf8qdqWOjb9K7g1VZTJMCcTz7VU
0YwxMi8cwzR8Bw5QMuJAeHB7AF4Cj6hjTUPU9hhjBAZM343GkeH6hmnbrqSjx0HlJWZsxCMHY8Yo
EDk3kK0OAwZjgxr8aBIgrCcfdTAluXCCsN2avDogsw/AxCcj1zKOUaFknjlG/8qPzW+YamSA3V4g
8cfGlAeub4ZXagKOnjcfASU8hpo+EuZ7/U+d9Y7xGeUJRow0Z3UbcEsjGCYjqEdOC7AiI5paIwM3
kx/LbQeO4xswxcLYPMerwZXBGge9SknlVrQmK+h8M8cTyPMP5oXZl8z9RLB9CuBhhle5Y5yO3MhI
K7lsZ4jUbkhGPEzMiXF+ws1FBoZlYcnrsDHlh5Z5YGmmLOtacPs1A9Lj0jeGqOvAPS/MEHLkivfN
UUblxuKmIUS2d0UqsJ0LxwsmlOGdopGu9KQ7O+NaI3oyfBH6CeIMXO+YZHDsjIOC0L7j5WtYJFRQ
ahja8bkvhy/hhirmbmAfoulg7MYxDhCIezj1PMMKVCTIt6Cdu/FIMStyINZtyg6+Ofjy5x8vX8k5
Va9fd5rNVK7H+aUndyRnqY8X9xE8FGyRUocsMGGw+qw5mQg89FER4jghrzo1o3PjXRBik58dHZ6+
e94xwKgdbDYESQBBFhosoZtExhgBFdOLAsN2odm4gymumr0XBEdpUuT3juHhRzz0momWLyIJ4oa6
oBA5iyaVp3Mn7FDLl7JbsO1hHL3QA7xoCE3brI9GaLIhOTKDae0qNcoEsXxzx9Mxdzxyvxlj1GGN
lPFLMho4xnSCTXbsNSN0Jp5p8ZXoX1HgOeRCUDIU9WVkDPqgJkdFBspTTJKBEjSBUjRBTjFpNhDd
oUR/1GVCZ+hAdoPIoR+B8E1PNLLAsFyhdQczFVoH2UPDi4z//q//I9obmCHGP4MrPur893/934a5
PRxzq1bmq8TXJYoeDUciJga03sIm5UMmgBW4Gx/APdowiVfg5qGP1zV4utuGMHJuzjuUoiqufK8C
5alp8QfB5EpVE0FbAMBG4cw1KnxFwfEd0mu2+M+s55ITYVB1M07DKZQsOo7pgJgAYIV6OhwGfuwO
XboNIvkmEamGci1GHaMHBirbSVEp5bj2vR6HxiqrssrSfVH2mIQDoNPAsjK0kcV9zbb6XyPjo3MG
XeZLZpWdCCAMFHv8UK58q/FiIuOZ1q5jkonjZJo1/GGODxe6C4PvOe0/ZzhkKAKylDekokZFbjId
JJ6z1HxPptwxvgCRAI6b0LlwUUqP3+FN8m0Efw5UMFiVV2uaCK/gQSGyA1RBoDmECfWReEGBsC8s
gbVRlic+AY4G/GoBBsbiJON2jIPARmQFSDwACmI0BX4pOl1B6+LfKVxtjHk8XN/ypvhR34WfSh2L
N/23xke1BuLZ4hST2Yk93MfNCUCx1ZGF4KKoszaz/Jw/jbDUU0fLGWgVxqUZwv8HR1N5bA5WPZdb
ncCHiUbeyE0/qzXND0tAUbsjhklhpCylJGG7UFshZbaquCIG2oDE65ILc5ndUkF/Q7mWK+C5x4Bw
rbZAWQ/XGq4PQRcgC/CY/b9f7IZkLUyL/cc3Rjj+4a53CTkSMS4NRCHXjke73b+NBPJlt/NyewJ4
n2B3FMLcPQOwjcYdkY+iGMPor+UF8VgEOWSv9S9ml//jwGFw7uDCIcmNRCUTwQsVBkQqQuM9rojT
0+F1SpgnSp8DeBTI8W+jeM4e0GJIMmUItzxjd87JRgB2CQGIQzgmU8NOuT7Iqo3QCM1ACMk4CK9Y
OyYpDfgoDdHmUjCSVIdiCkYyuGKG5aLga0ywgeKgGpxkfpSQm7k+I+HSB1tm1g/i+PrzD7oqw8Ce
igpQIDcs6jUL+wBTlKQIxTuw78ne5QgD8bV6kcXG6pNFtW8KtFKiD6iBizN0Hp9+6JJBAFZC2kVu
Wg/yRrDbtepF4JtFAoewryITnUaFo52e6lXhik+K/N+QgAo5eaVDXAcmjzBIG5kS9ToHW8050DrW
KoiBQlYqk4eyRCk6mKAMB14dBQTSiXRyaK2U4+26Hw4ACho/wQkoec8rylJphfz5h/pfaYqp0M2p
0iCgdgzb3a8Xn91GEmDh6VZRpyC5wM+qMi5PucirymxuSDQBoyx1I5jGBksy5m7o/xBnH1iG+K+W
S5gmPX3ugUgKZ3R1rK8b0vvQsetG7Y1BFq+QIvrOsR0gKSPg9jQOxLcxjLOa6Z6NabZKJ+KX4y9f
nsZZML24ZkGK7U7tLbEn5a7rfTz9/ETOAlwqZt0Ew07Rkmx81yfEaq2IqT5A6C/ePxw74Rny2q+Q
wYfyPBR0PI2jcekMpPK9drLiZXM8VsiSQGW0kSuqvXoah0NlfAgqcD3yPLY7r5pjsULHog/QAM94
i0xddMFc0TOxKKOldoHORmlaJWs6H+hcUeq/qct16kt2munVy5zYKQemGnPiUc2Jdykd1SEf5oaH
hMHbGkqOUiSuOSGPekLSCPXTEyKoeEKpIAIvNfNJ7XSa8N0qqVfo2KzpaEWVq0WmhYv2wPXSoRqP
0yoR/1HvU4+1SfoIECiphqeAqhLgn6J6nYTGybRKJyHVlGp/GsKh1UkBhKIa+V1LYGyN6fCopsNJ
gkG1qhLhhvZ0jY9FKR26fgeDydKCoRK7ALB92pQlzarqEeh63Sl5a1Y10T5t8lYH6llkrwEjsl5K
KqqqHN92v/35R68YE11VUulZ535w6Tn2mWpYUENzhsyjrlTyph5U8lajTBnvFfJEDamE+owGRKsP
hMaf/6+w0ivLRFDdEoTAK+vZNrFUy5O+HeRNNDEtYhmj4YoDCHyA9giqk3qDwppAX5Dv5Zl/XbpE
EExuCfnyEAhG2GyNK7VSsEoD1surfjRsE/AV7Qwm2B2eKQsYceFeC9knzIZJ5HoCt1XA5co1Pc+Q
bRS2jG6RnkPnknZBXI4bICfNgv80ZCT4EjVA50Izn8dF59KdwfBHrRZe4CiCwj1nGL9DZwm2oN1r
bUk7QgHWLH/Ibho9Dd3EY8LjwVF+6QPpcK8lv0k++1V9poHG5BDg0q/4xSXvIcxOHTj7m6nyzPD9
TIPTdZlN9YXHpvAQTl8NWzWoAnyVu85+jeOnb6rHwruPOKoYTtVCbvXkR0M3jOKTADOXI+6h+4m8
y748CLzpGMBq6ffJB3KJH7x/A5RFzb/94Gf1TncMw00Rf5K+IwRs1PdGwxVgMGqeg0vSTfshdG0S
/Rn+4i7q0Xd2NrJLkyuubSm7UGDE4XuBj0smtAGAuWQfl9knLm7SwcHihGNLP4O1kAyikZ3cUniv
MGG0uCcThlzkWyLU7bVev2atqprTRY/AdunvgLLmhOqbEQJ72N1zxbyTOSzZAOreGS5mDEw0SH+u
rn5zMiWGnxl/pEBWD/GbVfVoCRTa/LT924n0d/IfZ0Cxx82jvFKbWAU1QOw5zPOGfo/S7I/Rw92S
XV5m8vpqocuB+lfDuBWKmrMnudyNfk/WckMTT/T7QVT8LHleEC3cVqefD2abL6YLoFZF/o1B50L2
6s+NWjHmyjH0EheB/R4XjbtS3xEvl8IhpSGCCJz0StJsLflJTucRHgVSqpLZ83dbtvU6VD44F+di
3pFqecslD/11O9EAQec4Ak5IdakedsMJ0VAs36JKkLrjBKNZWooR4Tu0RmhpYcXSIIs9lrK+L4Be
JjQ4enihh9kFwIjZXYwNOhLUjVyfM/baQI64DAt8cGmhBj0+wX/mzdEHC303xuifhVeQteyR5jte
uXkaJjPyIXLOXActwi7R2WxkWKFDTOm0k5f+KTvAyIS/zO2aJm3I9Ci5+RCj2gTINFoXecFlGYUv
ZS9gTAlc5sm7g63NbmUwL3+i7hAZc5qwRR9Y1UoULT6I/6Hn+L+FDwobVKf9niYIknCjkXCIm861
mmyNZz9CeVgz+h2hvB87AHgJ1thbJQ0O9/L0yg58eYI1EtipNbReQb2Can795x8b3e52p9iKFGwp
3WUuT/qmuOXbG1vSCLQsVu9pRW+6jPvccs6xxlv+1nXCc5z0U7Xphx2EpyIrCD1Tdv5UsNOTTogf
pTliSg3PTj/2n6e7bgBqlq3GjPXOhlBAb3oGBHfZ/1fX7H+lWJwFIL8jZN65jFt6XwEDK+Osa8Yo
uETvwHCN7MoP4gQqHh0YbYBLtfEn48jA4o+CsW6H2GGfLiDcS4PFNeL0AzdSwbIpmPwcQ2wL58Y1
EBxjx3bZ5RCbModH58YJpp4t4xIUe6xaUKJJsTRLjGNpyRWhf1N8yZ6Q5eHRE8zgI2nsfad0AQ/3
OHK8CwciBYSAhVF9HpGWzYbIc9pvVkkQZzygtMskkpIARNvHuqSCRTe3lGZmlA7oNhCZQ4ouCCsb
QQ32mZoC35cdEWxsQQwcVM6uwHIbnede+5lUCw8yinGAhg2Xjue1GYNCXwrdXJRKi3QpTU8AWkPY
aCyG3hCgMekChmuErzgvjqde7E6m4QStotO+c1BpXM84/AYQcdXO8Fn/xfHR8eHzhPiZuifHCvTE
MZ0xfxBdgVDGRfKYL21ebq+8grGNORaIHap9FRrtvLbij6kglaVk5cRhMillqyAS7nDa96A2nZjj
CI3AvDXjjZKi0KBOp7AAIDUS7enGdJ1I083ORtZbGM5G9EBR7ZBFxn4w/SkaC1PIrnevEbLzlKzN
jcqcjZVSsjDHMvnUiUCcyHet8zXjS2fNOLTxD8gitRKTztFQF9DuULb1sxUHAyesl+7UA8cXrqv1
EAO+a9AquggZEzOK0DM6HqE36RnaVUNlooZDczZTSmBiCpc/ReedaIhOpj1gZaBJ0LPj0170HNLe
wK9xEdoKufgYBTBA0NA9qm/DE0teOBw8G2UF4s7rQdrstZJPxNYqONeWRgysFppfRy7aY0BcQdLx
IbEeEHCiJ10tUv6UtwnryQZLjhuqRUQjJZGCz5zOGUistCRzTv/mRvdlledylU4/51jj0/8+GA7H
pq9OP+XB8ekXKDsh6/kzlUbasSsVyJAr2MEdfauqbS/hEu+cQZhw/+7GNdy/wC4fguT3n0v/epA2
7ZWEZO1ATI4JGo/hcIuqJpQvNojwApx8yQ5IelhrbtIp0fMNtIeHeNrqAw79FZ1rUabHo4oZXyAi
U2k55pdIa7BYoghYQeLzy2weLtYa2uJCuZ2CibJVmy8KtNKHeR9lbCVMeBDY5LQVZhb8N5A32AL8
w1GS+aGUZIh5wrhCy6QYLeC4LQi58SVdkuK8CxBd5JjIFOGVSiVpDLHr41L37cPQdADTCq02YCTD
IUN7KIerg/YJicrRv4Jb+Zuwnohu5cSmh9A9OIZvp3Tm5siQ7Z3t1dcgMcday5Bp5Dk4gCdKeVy4
nbJ3IiH6zgT2b6JJvl41EVHNNNEm8rhP3wBaISFAbIO9USD0BujEBh3H0ESLTrai/BnrxrNe/1Nn
/bkKmISmLd1xRPEEA0XLyWQIHgS51HiLvEcMOoUHHd8e8ireg/Fn0P7bwxMILxX8UJOAyjqAshle
gXvra6G7cjzNuTFKwnHJI6HvBha7nMM7Z4bmGE3SwauXOE5Hpz91ftl53e2sv369tdKKWWGmNT5a
RxKtE1IyPePU8RwrGI+nMNjks8j4yYdarU02JTPp5T5NAmVXRlsTVUoaIclo12AeUGqu09ZRvWvK
1PZGqO3ARKCJ5tIMNR7geyHtJYiWkRdSTl1OOvQj9HOkJniFXENoNtNIhznVOR1J/1UGICnLnple
wMRRqoYBDl9YPpRwfcPnDrMRwAie9k9H6ijD0Boj2TTvhI7gVkZFBbZbjEqJkVJcIr9Lh0XVdkfa
fam8ldoJycaGTK6ZToyPJjgJp/3sl+OPz6HwCWP4YF6YfUltMj4PpDlwyrGefeh//rSUdP26edA5
OTxofxt7bezrq5XmCHqyJS5XMDzu0JF3w2idH7wBFZ2/v5pAYRVLPt7HqtZnstz+GrPZN6EJ9eUU
6ssXM/DcNeMDXlJUHiDOjP6YUFLO2sfW/5oiUiXM9tpztt7plsxgLtE1nG+OCru1s7HybhDOscYE
cBAG1jkYqr1mvMXWwxFyCvUpFxN88VsE7nvM8Kdxis6Ywsuv5aJCAh+mnvjAuzvXbH+BGT2eX6Ax
lB/fUJYkKdi8IbWPHBlSyk+1ajBm2FLUhjAYsB19NJ1MghAhcwh5aP4A5BTbRAWuxcsCtQQurwod
An4WdGmjoZIoJn+DZ8V2HBwIuAevkERlnYvmYA5cOl60z4j3KP6OiVewbhBkCozIHSPNa4iLeZhs
ZfpQ11RTKqd3DZHJBTM/cR1jpvknF4edcXR4+s6ghpLoLX3kF9M6IreG8hpeTehoNp59+NxHAPYy
CM/57Rm88xNoVMw3gBMbuQshjB5obXBJ2fD2ecFkJtKv9KvMU8G7dozULc4v4K3Q+QZjbJRS8JA1
AF+5Uqr0ECZUO9qH7tkoxkeXZmgb7bbBFE0Pcqfk05JHSd1ahXwPUeIxazi3ZA0wiO1G1hQbzRAz
PuZKFx8a20hrgc9KZ5rtDuHEnCGrUTDhOmE54LmTUdTcM0MX2Q1cU6WWZqPkn5+ZGDSNkwK+aDpm
Tt/v3FLMiyOrJA2MrQZz/AuXc8fsMD4Ku3DJBA5Z8e8Vtl9WhaOAQBiEx2Tzt87cRCTOLEdGfqZ3
IzGBoobDPT6H69OwUSkQpA5QJskDNooisEiZp0K1aRIGvi3zjNxOk6j0Tou/UHzC6ozJuG/hFI5h
eZFjaEZDpsFb5hhHSeeuUsloShyc0OyxI/cM6Eahs9FGjJv/t9puETXz0iMW1I6Vs4G4xPWZsNBC
faabEG2NNfdDFON4yENXivuJY555eE377Vd3umb8iBd9pIyrr9+ayDtUsc73qB2zRmvGO1wA91Yc
IB+mj9dkCcg3PQmg2aAPhtgCZBEp10hcvLzwS6ZlIQ4vCaYb2vDLJ79cF/5czGQgtoTHrCses7m+
ufKOloOT+pwBsHGscH3mSxZTTrNbYRYuLAY0+yRZTMYl6DsiR3jXAWyF4ixwIpR0Cx0cmsM51jvr
4i+A49YaSdLcdXyjsO2P6TA4Fbsyp4vR4kkiZNTLqNuJZzxivjqUsERDg8WB9rypIqjTg/o9cNzS
kaxikp97/aN+JzLhgOaxaIP5toNopdljNuXS8xU2c7XUMK5tfWYLIqjPZIOoxowxrzf96IwnSu/6
gsRB2PAo1mI+AJkdCneOzUSZ6iHbEu3F6K/QjFDqTsSAp30vB0Tl29OUTy+fDWiRSzw3fk40rpRv
XlvRVThqj8c35fm/9ttZk9pleF7hByvN6r7263MOsz2o8Xn8UR2yAxy7YwupA0EEA+cY734IAlsy
/vmGp67XMT6ZNlLofDFw2NxMJ31GRrYUueBxgepw6ErldMemCnHUJItHZ+OA2xz0viAnMel8yPUT
16Jyfi5zHDHASh9CzK/GFP0GcgTeapavgGS1LPkAfzGyMaBfHyAZBs7+pGFlVu55kSjT+WKF6wp9
V0QsdJiYO2E2GXKwczWeMCby3s8kHZKCE6my9P7HYWBPLbhV3bHrmaHhMbIhhQxII5l4zjcduJFA
zxrKQZPYB/O/xAebhnniIOAvQwSYgAurctkQHFCljjriAyXf/9fY8NxzVkHq0AFNnlS5d5AM44Q6
LBC58VQNpMfUYQGp4GfMBoEhU+IaCx5TTRNBBoktMV9ZijZwc8aaBFZSyMR2Jl7AiAIcy65KIR7g
aoRsMFXTDpB6KCEHHfzhAoh9MnZ94BB4hjPEsiKSBV4pS3G7kMHBm+0tADixbmGicFr+8gBhCQxJ
AalNPFt02e+1YD0KzqZkwyQX5zBLNjX+zU0QRO4dNkgmuxC96frAC2g07kWuudc6dZG1aXxyLuGN
RBBWxMzdFP2wClnR4ZI87yEmhTm5Vrz/94tdZN3h1AKX6x/fWMT0D3e9ywyYKL4iAtOla8ej3e7f
UFyEeOpu5+X2BJBnwe4IfgWEdvZaGtxMPopiDKO/lhfEqJIyqb3Wv5hd/o8Dh/BC4MJhQlQyEawS
liep2AbWF89vHvILawhMiAanzfNge+nFaXDaXqsa4Qanrdu9d4bL49fgtEH5AxpRZLmoB21w2hLR
tvI4bZIroLSdPE6bRmOr0Hm2KtAHEvfVfAktSslieKiNDnDa3rKiRapT7hhTubgRDUwbNoSqhVLA
5sC0FROpxghwR4AsEYQRVAUwnAJrKYphnzCZLDW4YCzDgiFE2tUyzguigr3eer3SDgw9xxo7Mfoj
ABIhz0+Xx6maHiDw9ROwvB+8IIpQv7WW+tVmQKpe1iV3GL6LJNNzDcmWlklapV+ff0vZf7SuWU4n
+ZHKZ4HKNkYKPU/AqmKxgEj9sMRRX0PgPzoaIiaP8ZdInbRQRrhU9Rrx0JpiUHhuBUFCpMI94M28
D/5KxaCFAEdiKTZ4pgmRQS29u5LyfWQZqKzhYoKzTuYGc/HgsmS2AdmNyvgGr9A1soB3cRydsy25
04UU7Wj3DnYST4scMPsL8MQrLB9/OlYS3/UuiA6ukMyVRofvjlJ0bcHpBS1lPwCbVG4GAJnvvBLo
csFPB9b2jsZKbpxO8M3cJfzNQRFoop2VUhcIp6hlfR8HaOgGezffQOGirqCzco7iTu1O8EgaigFd
z8KkzrdTcfkdCYt6UUxPR/BEdDnfJihwkbqtc+eqpNd+H3vJRZ0aSxzV8KAzkb2Or739iy1xGDRS
0pVUNWUWSsgurDRHoG/AuEFxGRWPFgoWWM9UEBMtVb3WQqYxK9QqvpZII3+ObdcEgR+BFlAIgwgs
IqwMo1YqQABpH0v4F3i/LJihzsO+JQh4qpklEWLaWaL7SL5HUgaDWrmv/efI3WJVHb/JVcPgq0N8
xcmlX/+ICeLzH/F5fnpFSVgNZHrUfttxnXjY/g2FXm2W1LYvnUGbKyYVOSvtiDgqqIildgmrk7AJ
JiGxGCgswfAwZIRK9ekBJXneKmKvKpoorW719O8dgfWWwA31W3yexGbplUR4j8L+EPGkc+1nT3zr
s1pMlaJyQ9KJ98n/nsTSg8Psg4+XnqWQWrA6/JGTTQVOjb3KOguOGZ2ALwEAPdzHCWwJ6tT75rk7
noaqU0Iqu7MqNiX0CcmkczfXN69xMbsEMd9lWobq/kZ4RXb/Okb+FwU3oBfZMKu7vtnu7rTXX52u
b+9uvdztdv+9RRW0QA43O1nfZ9fvrxUIEqwZT/AoM6mGkruFwqTVSCTNNRoTSOuGnLeMtlQ/od1o
TEwFSwy5hxbbjcb0aEvfaEwStwtvJj9vyR+pMWUS52moTCdpI6lDKFDi32DlrmcDthzvpLog1Zpm
HCLfqTZJv7DVV5u4HE9WdYJ7rdGZGp1poZOs8TJdE8C/oUCBq6PRmRqd6YZUUzbTaudlgqh5GsoS
Ki1TXSiL/txECXp4508HVaFnaAQSjxAbo35nJm9RWUR8wSGai0bMSpQ6QITA4D77eqh1wa8/SlJi
AmECYMV0AXLDPitoSfCAOUzsEQ+ZAPauuKqH6Z4ip3gfz84HSd7yNfZLfUJ/Wc7xJxjfK/5YfKBe
YWfwKKvl+lsKXn1OsDSl49XGuWmipfcUNWp8f43v769ovzXR0oeISlcp3ZnEeXrqbF6bg9rwXCPw
qaa110VEH1yrrQ4k3g6b4uV299WbzVaTJUioAXXE5uciwwat3gNkCerOPsgPBOaJpN7hXyCV+Ogq
CSB9ycvLOnulje/N6GqMFlwhsORppmTvAiSjqC5PWcphUkzFOr9IpRoCCR2JgpJ1qHLo1gwntjoq
DdAHlroxQDsiA33pAcmoIbDT/AemDV4E3gXh1HMTkSTF4Cw0JyOgpSDsj8wx/k27iBU6K6IKCwmH
MKU4SjZ/mL/sj9s7iJ43FHo97kdVStH3JT7MpVCmp6IfA3JK0e1B0HakcDRBEpIcVdAs00TjyyBp
cBCgXxjNYmDtxAIgJD050a8oZjEehtSZrhq7M4kUgRZQikNKE+JCq7krLzBtnU1aGg50XRzLdlQr
B/9szbhA09XhFUYBHX2FG43VgaXc25CTJIW20JbUdsKWnKUWgETciYt5z6TSot0VjyjQgdBJD6Fk
qSgsNBTgYeRxUzWLY/OqfE/cjRSPH8vCoDQRJ89ETw69HvyJ9PAas18BwInS69ioQa7ktDvGO6yT
880kfhHWOT1k/P2AYE6SToz2COk46hlxO/xQL5TyYqRXpA8e3e7oNcBF8IWw+AQuBF2EktTlF4CL
pIRalfJLW5CF0EUCEMIBRebCY8SqsRNWjenlTj5CRb4J2qmuJ/vLI0gtqX09RMHJYugiOM0a6KKv
IOrLvdbWtpQvqox0+5upFC6AKh0wOX1iWhQWcqVKMqy+UMMNEXlJXVw1qJRIzvsax0/ftIEuaq1v
bb3a3trZftlAFz0cwwVlNtBFbJqVVgk20EWJjlGs03vvoGu0fyaIhwjTuBe5WvHSyS2bGfOF3zWo
QIv1nQ3ht7PQRXqKiYqEPArsLuNh+IFKXJP8a13NmySxffckGRHeJHSR6l184vxzCqQVacVWjv/c
RNdqPCIKm4AOkWU8IvufBxcuYT9QgZDAL2grEGaJODWUDVMoiYT5QuPRR4dlAb9JmpULMrzYeDB+
BBsWgyjfAtoBhsEkZOtyfIM6SuWigOckaz2xm/NAwDzKOTUSwxRIs5ylVSzwl3nSWSFG1ayfhD8B
wq6q7c7NVdB6xcMihuIa0Wbp9EkfK1kRaZ6HN8DqpW8madYoP82cJhKpzt5mPqDOHVA0DuNdAFQI
QBkYRANQYd4/VOtcj+NpUgycHbXC+YK7INcTVH+VOwPwQfD8kWozjyWQxOg+kcMAH4KDwmP4cNAt
E16h3MGCa+92fgXNYhuCRCRvvrc5E8IrZevOcYHfK0GydWvgE7vbmEwHHlg+aDCVNgmpNkR5/wyp
pkSp3agLWGSVdNeKxzFVlDPH6BXjHgcS91Ahjkz1WZqjanrOpH3DVnfn2wKQFXcUIvkrUvBs5G8u
wSbMFMGLRTxXaQp3wnGb2POSltbcyJ6Er2a7pVNGSoYrDA6YTtKtHS022MZbM0KYKlmDcMSYcmPQ
QmKreJg0fhTDB8GQoQ0D24ohh7X6mBsL9VPBJdv78QewoqhH4r7mReDaYm0pIw4K5iQAr2W8D6ZQ
2nEks5j0fdOoOexAc4DwGQbDzQMEFH9n7A5Tp7U0NF3PsDzHhHbQMT5DpyUAIOKLeHjYmLkJsjM5
ovFxantN0DLQd87Q4UTi7H9j4/qSYTkxQ7SjQLgdwW/q05iLhmiCVbpwMVbHXhOvTGOvXT6IcKFP
KtWEtdJBMp1jpWmySkEqnfSc4jAiNI1wMkg57W2j+uekpwDO05EjFA+vA9k1XotirCPZknSSHfwz
mHM4mYPfcIQL5JlPXd9YZ33c/eR4P4R0zxLZxWWyRFb7xkbdn3iORZYwadFIhduSPvIs3kaba8US
ATOGJAshIGY9MDsErJLMdAzWKl4x8GXQD1s3khXb5IoAGycrVkRHSTPjprpZ4v3DEMi85SqcCWqJ
NwjQ361Ho2HZwPvmqXxUgjhkNk+a/ao0KbpzRacQdUDzbcWoc7oCHWZ5Hgy1AcoGVGY4hwGQntdK
tIkpxzO9V6NWlyNZy1VT3HHCnLj0E+8oMuKSRC9JkTuDFntGTig6IVCo/TN+kHS4ziueEhUYs10V
Lx453mQ49fjTvAaqk9ByVIQGfQnXvkp0V8koUzeldoGOlTZJinr3VZ6scto4hoFqQMUXv2PYgwy+
pIbbCzXjJKqBH+qJq3tzadirMFOjMZvcA/AYYHK8H/4ALgovZE3vhL7vyHssXVUa9fiRee0RzLJR
MPVQjQleiX4Yrjb5pOsJFFkoGUit0wCoyyjWIPbEtFXHaDGdqjMFUi0ozbytUph1F0vdhAU6kJ6u
6eF8Qce+QFmpZG+KtjRM7k2WAGWqUkJkt7yT89C4UW7lRjnFVk+mIWhP1N9Eq9UhW3gbsF3JPvNL
WGEquVh1Do2mw6FrMdkYW69+pDVlsj/+ACYgHMa2GGhqLHHIlCPZ4mpG3u7paArnjEST6d5RvVAy
LwlGcH3Lm5LqbFv6Nplegfl6AXPpUAGtDw+Y8Yp5mLeZFdKw3kdmvSR80VboLtTkLtqt44vfTcgs
IjHTKmQlSFpKn5P1BcqsIHl6BUmuZIh0aaRF+GkULxtWiFaxzOQY4vwJb4Ymk1SjmD5b+VaRfqp6
w4nCAbKRkyIFz3Mn6K9sWNMQ/bSyx7hlqUqTL79UvvxGrtEv3BFt7NeijHlcrvjETQzye+89KQlt
N8rGm7VhHsK8pSNjBftnLGr2i3KKJmO+yZiHgecHP7+B+xyYw2mlwFtpbgDuDYGkWzl45lUwjTWT
yHdo/iF0barF6MhiHwREZ0ENws5OksGGS5Mr4lCbk/lCHP401p6IhSe9afZb1fLqjkuUsEFNxnyT
MY86uesytFcwY35Os19xPl3uVmTM628qM//mqw2ilMzPKGR0cosZ8ye5XHkk1hm9yQRJdSq8+CUM
4gCe1KYNcKlQYVZ/u6OMpOuTfAuF2tpIQz5D0udnFFyWExdUugetLZhOdoA4HX1WbDkLF4SkWPhI
7XD8aBryosTRnHNrwErLskSSDAx4QNgkA/5oVaFNW24mto0YiSraZtYwvdQx7iqZ8mlaiDR1pZkI
m5LG55qBZ1DZI7kAJYw9Vnsn+AlshsQoZeJjN6U7EoKTQ/5aGbHKUQMnIs3F3SLI/qPG9HYaZ8cK
xPS+MukoR2EG2laYRSopZENs1z03IEmAQCyGrrbkLV+runZ8Qj03Q/nbuEec6vmSC9rd3XHTfXdG
eNUpEUEFBsBqY2TqgF2vTmJCw8RWITHhqySGFQMHqY8TaZHw9CsSEpdpQz29yDX3WqfSTf6Tc2mc
BGNTtc7p+ZG71/o53xT9O3IIVtTFNifPCWm6BQlIPkN9H3ocAH6AY2M4UQx9z41GkkTbsJ+4IaC9
FsLnkYNoSWv/q046ZYZ1jtkgMRo2pKuyw21akxBdyPsoZsLANjCjKLBYxSvQy3llLEn9vg3LamIw
y8VgBKJa1fBDTLQlL2dhFOZlE4XReDVPR0QsiMJsAuShicI0URgYZk0UZiEZRCPinAhoBguRgD54
uSssYq+FOoqAb4dwY+21Xr/OMpQueh48Y+nvoHsBtlDctyPkRgCV6lzFvGNLeSEnuHQVgOIwjSYK
00Rh6hmFkf4Vs7hFkodWGYV5pY7k3UdhthmF+Qn+7wMktc44q26S6HJdMOwTMWe8r85APcrCOPaD
Zd3f2GK+O99gdRFtn7EHJFBeBuE54yFnYTCdMMJy4XjBRJLWshBZGwkHqIxKDOdI4bxmhaEmIzOo
lKUXBrq15KCJFSTOZpVix8JbfuESw5VBkkgS4ZCX346DNv6oYA0Rd4fA2kUABTmhR/wJIhyI4zD/
QYCho+l4bIaqJlaiHhqylpEa5LKKjYX7YBr6mViOaLuRNY1UwaDOlhPcrDQOhApfANJmEBs5Iy4J
P90uabkx05Yz03LQsth10Ma54y800xp4WYSZRJH6a5hpqNdtzLSF+nkDL9skyyHC2ZhpU8+BSRp/
ZBRWscjfrCoL9Ho18HZx3HfyH2fAKDTt20wfHF0xv8T1zzEx07dGQbjXQniCRjQ0nzgIr5gMyoh1
iI9SizinBc+ZfQMvm+SBrzq8LD2PcDoBeGWvFQ6tjtZ2O9sdnQU8my6Hn4jIvw9Dbb0IaoB0+jAI
hoch6U/hk6NTylj6AdzXJGAr9pm6BWugEBqZM5dD376nmVQbT8YptdLGin30fMGESGB4ckMkOGci
2288RvIfLVFGecTOVJl9bZbUZpamwgRLe5H0e8cfGaxzQuoPUTEODHZcwak/9/pH/U5kjr22FaAu
fKPTbQer3akym3LpaBV4Sf/Rug5WtWTj2tZntiCC+kw2iGrc5e7A9KEhrRn9zprxozOeAP8Mr76g
xdEkiJHue4J3dP8cdoxjQEfgSvR27mUnnN99SdJB4KcSz5UckFT+GOnlGCI8n06Mj0C+mBIe8xkZ
xnPjZ+y37qMXWqM//9jodrc7zwsUAHUv5R6iysk/j84+O9lT5hgo+KZgAgj+EZHvsupuc4C6IyY5
TwVUS2XQXBnPWpZnumPwPSxhK+OgrefGMAzGUv8aRVMNkJelXLPoGzAgWtKnfj+pu1UsXfvecCOV
kI3Lszp0eBt12nWaza3mAbY/BtvnrVkO66p7Y7NRlDuUj7JEbwKEqOJc04O60aaTU7IQiddO7PIR
qoQv2eGOiCIXbgrUoNCiUErLFKLb+QZzyrwuXSyqrI1LO2c6zS0eqFIGhJbheB46gGdU5R7cYCn3
ABUT7ygyRO7jEDcCHxq+hHXfJ6qOVquT1hXLVYRMk2F8lGGoERaV6DQCH2Ufuw+2tI3A/+sK/DXj
a7/9LuOFBSUlp6OQHrUvqvCDKq9UXpV5PKsh3v+Pr/3S46ywQZPtQY217x+VSn0AJfvYOoImHo3w
Cu9+CALbp7bNN9Sxex3jk2lDwfJFA0dwHppneOECEMjIliKnWReoDio2AIlZ/77e2ch3rO6+roee
jYUIfkdGlGl8wYME/kwBVmoc5A6evnSlj5yeY41pWG+MkGVpk4TSeui/5NGmW69Jd3R14D5PHP/o
rXEQ+MApisuKbYEx3ky3+44YM7IBPfsATXVA3PrVKfTLvdbAAYIk9UNGRR7DLCbQe3gKiLs5bt73
v345PPl49OlHo9Uy/tMzWmpZO7o/BuxdTj0d5fEeZM4CRw7MU9QdzF3jR5XXpcWsMRPpm+fueBqa
a8YnCLw3oWl7DprD0Rf1ASYQYPkpCIFcdwzVyw0DfPAGHxwH8B2M4dpcMyhDtaPqg4mfwk1VOsIJ
zUEGKm9TSdlBWSvOF5sPbt4a0fwOyeLC9FFXJbGqG5qFSeXusSkxoOStZhY4dzOFvJu3BjZfiQeP
9z9M/aK7W3GZGRa5ItOtFI8JS384J+ccJojUwrn87wFk3xzZguOeIfvBQYV0x2AaWsDuQ8+lAOmN
85xVn9mUyVjSW3Xy7mDn5Zak1JWTCVbGbNNzrDH7f2+GNoINb8HDwbfp0s42ibuVbec7dldhyq3o
lp+tOBg4oRyfjbpYMhmqJeMl6kEHKAIR574EYUuCqcq2kT1XrdFXmy63uzWmy1T3ENXiLSDSFaEu
S6S7xhu1sZLugOx9BL3qSriSSy5to6Twcy2LOpUjXyRryxNgY/JiFolroCgqaPzWtBSQMfpFhSgj
X4Lej9pvO64TD9sBh2z/dhm31ZlZaev+qPRkBbPxDnWPGyqG5XhBYj3OpCkBLcnz5uUpPd78431F
DKXVrZ5+dWrT402+vPhEWBOiLj1NQytwp1egbdyQ1uN98IrS0taXUBTPewoSFRa7OZ4MwF+UKU/R
cIAkk8yih5D90P/8yaCvW8nPZx++nj5nugmKY1VSWqYmHiiBQ22xJHCKCuQPITJeIu0D19km13om
qzSwkkRiBttGI5Nsoh19j7Oiii1WcvkV5Ys1Y+OcrpBsiTWu8OrWnvcVGV6O0yW+y+NO4u0E70tz
ah6B3xWo4PFcPE1O2JzKlAR+DP7qKhXpu0JMc9xslSK4xDSWEI+/IWjbvnQGqhy1MdpQjXRDRbYs
IBujTZd9KXUjvBmbuuXi10za149WyC9KXKa+Vhv4XulZCgJ2tXwR4s17GhZmIY5MA/MT8vXTSPMc
+1KbhleVMTkcpFTYzQQTb8aB7lJIE7EdNQVJGYBsYZL4rwq2kPolkpyrQGQOeHOlUZykd0v3rHLu
jlEMn+usGBrTHXi1LZPFYbDHVclYMIzR1zPJFbfg10VOCLHYEWnz3LFL5EY290DJh9M5Q5jn/enp
F+OfKGi4yvfSStqGsgIN9QI5nBFxG/N2ah4xW93xOVBjECgwFalawy0QR/rp5GM7MoccYKKa6Eos
8HbqZAM/goB0sfI6qaoVD3GSO7FJ5c6XUlzlqwdZKhGdXA6PbHaxSl66CXxR06drZiMK4mQ+G7pd
DT6R6Lq6anpRNcIihEjkl0Ssi9xrXbp2PNrt/g14RuhyvNt5uT2JUf20OwKmErCN9lqWAriTj6IY
WTn6a3lBdDxhoHutfzG7/B8HDlHDiguHOltBTUTpPvhXaAzIHuTb+ZZPKBgCOXrOMH6Heicms+21
tgTFP+TUyh+iYCruJTADuJjkjuEmv/TRawLl5/xN8tmv6jP9KOIWw6UN9Ag5RNOnC6uA5mJbKoqv
cAHsb9p72kCPNNAjggO6DM/WQCXCXwbq34NI/haUzAxEBdA2v4P6pFJtQ7P0/8/eue+2kVx//lUa
WiArYyzGkmX5EtiAfIs9sceGpc0ku4sNWmRLYkyyGTZpjQbzx+9FFphnmUfZJ9nP91RVX8gmRYmU
Lc30BIhFsi/V1adOncv3fE/28wtVUZW+k+Z04LPxs99+Pfzw4rdfK25M1Rh2Gpb/H7cNxjtmU9In
p3CXJCO9qI7z5vXpur9b2DtV6pGduVbPtXXqetDaaVVe0Ry6j3kp/WA6zBc6k6pFu79ExYGalhmI
T8472WGwCGBO0OMN7vDVy+Q4nvTYmy/u5tZU+/KamNOweuvB+QXMjsiK6+fQSY67oK2tK337VMDj
vjlekD+OR92jydhoLTHfJ5n9hTNYQPM8DMj9ZP7dlATknjOvNBTHNfjKmXYiVwd8zwnhR5t/IHxl
K9qPPBbA2AfOAM8j0UQJPOgsNhZW1yYpxwwr0kAPEyS/ItI5AcKnAC7+cEZZHsETR4JQ/VqtztMz
UaQqHGMQN5rUJVCnwriga9M1sXJ5VfA5SgcjWNABfpAugsOgQTP4x2lFdNEwAtjwfDOPpoO1lqsP
Z2PwcRDH31q5+ijpJYjcmA6PHkDthgVVrDUNYoTdY/V40dWxDrr0Tz8XwYQ+uysdJYD67NZf+FXt
2h2+z49/dkhNJGatXYQuuX02AZTbG0AhulYJoNzfe9wiclITRhm2sZUeEbBZJqgyoPI47hCWmRdk
abfbS0ZYLmfDeevu4zJm3ZvD9+8+jqRr+vGYiLKzr7sWTVT4BppHmINkjlsQBtf6kfdtqhTme7s7
e48ePdgLVO3Ox5lv1Gp5uWNCBLMS8LRQkQt4HndPDJE21/L3vPHleN38++I81VtuUeW/77aq/31X
/DrzU8Uiu6Ta8L7Z7Xpja53pX4qZtb9Kn0t/up+amfaxhCQvUPaxhGVkWtOZ2yP8/cufeuO/tPx/
fzoZ/+WXKVPql2a+V51vI5TAHNV/JXF2f3pTVT81M73yTNscu/+bmenit2am2WssHnklHTKz+RUz
O/NTI9OrzHQxsfz1fyqf+NCI8UpiXJnOkrZw3zeT20wu+ex1OThrNZcbyZXFW3iPzeTKdxQ+4hpc
87VObsU++GVrq+pS80Xx33eN6bCK6VDZ0CrTrikuzXtjRxBXX9tMyywr1LP+rHjbjUyvPtM+CTU7
01FkSSSb/sZ8u06ZLiT8pmgPYaCVICMBDmKaRkV5iPprhrGvb6+s6uxpfV6/V3qEEP/4AGGOkLRY
vgPGkZdNXVS9vgEVZ78QV0U+vyDrti0yPwWs8wfSiUA4UKUNeBkcXLpXDsIzW2Xez9h11Wvx6V2a
qguVxSzu7e7bNY+7o2z8KdV4lJro0UnLPhU/vkh7kz6I1/z38IUdMkjfPAe170dYhU26MeTT9tdR
t6OnOuFfruFGvrP30LIO7thwyHjEr9NQG0PGetBI1aPY3X30YHfvwUNrFZk/+MWzXfeyNJCATAEq
xiffsHrc9sjY0rso3vs1tb+eRZwVa9Tltf3Muw8k8FN/gP/eL2Qbs/09dYghpurmwSch+SfArmYZ
zOcDsXh9lyj9ZM5tyvnXp7LKOmB6ANfS+KwMHy/Qh6xRm6Ay+tB9F4aMfAApe909oaHtb79uP7GO
F473AWCBeIRmYYlAvSVlKwARmxz5pSSmVJC8LpGVqpxv8i4qMgCR+bvKkUtH+lXbdDVZIBNzsuW0
wE6Oj8FEqR8NyCyvNaJ++sWjmhyKKQd7ocBLsEaf+dqEbVIldgPaoAT0k+uBc0fgMoGhchcqnJI3
2rlzl743sR3k3YISd2XlVOcabOq7nkAOo+jI19p5xJUBK/uJoTPbWTTReHrnsil1jqBWas1yh0JH
EG8nMcSYZ0leIBdTs3d2qlY8gpoV7cmjopvPGH6cbAgLDxV7GvMEirZJpk9divpG/aTTpXd4069n
md37Ehv0Ym03R7IPDWhYeo2niNX4LI3YFEWCRHf6vCa0VEuZPaEt/DjBSgTIp4JQazIPkBcycQNA
FgRKIv0LR3oYn7oIsIr89SjrlPC7Nk/FCnBirGtLKr3Mt+OBOkD10073+NyJKwIF9FGXTAbttGNS
Zr/YkmxFL+NxTEusmpFdPAa/CrnrTJMrt+DPmC0DXlrHe5anF/S69d8SE3y5zVUAWmrs/Zh57DER
R/S4SmCoLtpk1V1LQ6dEtp2MBjyw6wimabLWWF310JKCgd3Azw2jLHUQm1Y2bqohVXSz3Ipe83fe
kbF8FZCeUJlbZ7IsbUs6BgnSMvos7dFXXFYPwMgy2nmNOBDm/i+cUb59K/oBfCmQ0vQsARnqW3w5
cyzujZK4cx5EQ4hRLxclLWX6y5QMpbpMXqZ7etHilkfn0eG7A8glUw1k3oQzgZIkgdLb4945zyE7
MKaYWOySpuVVniyiytWgprPeQbMDX34HPkS4p9+mdIN2FKeFtGrYX9mY+glS6LQDlevddpCmPkop
s9ebUR6qdcMFUBqj86Fk2m9gDhtIkTi7HEvKtSPUCYZKLs7QqtXdEDwgy5zvCxqy8z4DQKrUh6/4
YHdJado7PD13LfdoM03vFa1Th5L2OzL1Esim7axc9IwqVUjr6STBAB1029agxP60O0Tyx2eJx3RL
bWeGB2f0QhMi1qWHOI8AaDJgTJB8iJ/pq8cw0wGHDidHPUbNV1kj8T66MO3WlpyU696ZpfaLXbQq
wyYVtl0UosFfvfRcMh5h2Y1QjaDuM3hzeZvA/nnxkmY1YkQCnAx9kYSo5hnlfUT0UBJeFqhRgPM7
qbL1wkWmKhzcj8a7oF0smxwfS66dGk2mQHYHrl5Be6atJw//Z0c6YmgdPTCVAqbEdSfJp1FCcIDW
YHljN9PF2xCljSLYr6juEdo8gT/CL+JCwIP1Xbu1sh7Y7/OxjPIn8edXljUDNFbjSrrD2iIQXbFG
EHsK2cXmDzzdeN/9nOgz5hJIaTW02bq3t7X96HD7wZPdh0/u3fufG3LVFkVWrkMEQ18H2DH0IOGj
/mYo7huNiy4r4bEe3oLHGj8zq6LybngYnuJbTPIcC1z2TzLNX40QV7u9X4JGGYi7WvucYZsnIxca
WxQGGT9rG+/pv7qdykQRMKgdxKuFfd5n44/XrScL8pdizbpKIykPp1ikQpo97dvvaYe2A5V9HXXe
ieIO1WNttL6nhXfxBS2LOgX93zPbFrwB/3mQnqGtscXcReZEUmRycYZufYptlQxc23m1jdKtrScx
Wl/7D76T+xrvV3ahWIF6PYI/sviw1urGlEWbGZfWntdLY7avmCWnNB1hmySmw21u5cm/1vZC0EVG
nbZryekw7qom0DY473ZgxHVxdbksW2PhniDRtvO7HhAy59rQibBrQpCPNQlvfukjlgBTs2grNj8p
97Km4091nm/d85tVkU+fXY6xmzeM+VHRKyjgy1D1NO6TSwUuyZwzZ5Nh4Tm+rDw2Z0LhnO5uf5hm
VrJtjbTbkx5t4uTDczD+VfA7LLyCSAcx9X1Hgr0lGi1rPXJslbAD51SzfpwKHqojOYspm6Hs0uI1
l/5/fHqbVWWlRJUmI8pT5lDwvbO3bXYVa5re8+dKfM5s6d+OE48+qH6Mt5gE73U36ckjuBt9gmzt
r8l4fI5GUju19+nJBMp1/fl6dE6e5DNkbPoeZ1sB3rvROz69k967G33kT/nZh6J8I1o1yrbeJehb
qPPeqMG1WN6iQ0WMjzHTPwYaga0tk4k/b7e2jU1P3bhI3T1+fGu6jVoiV2Fz+TlH8tFFo7e3Oxn1
2GZcpLKiGOcK++7e7iNZ2zdZ2DXGWyzs36MAj7MsHdyNDhBYhFMa8zkvbHuP5gL8e3/HybH+3tt1
UeVXeo28XtcLoNRJ6t7e7egkpciA+iBgarnIwAA3Gw4y54Mb62LQ/r1kcAITI3aMqelNF5ifZPqm
joRxQGBM4VnZVnYGx5mxh3EwiHbu3tt9VMQpXNxulPzb0Q4QvLMuQZjt+OIn2EgYEa/ld6d9wnvp
kcZ8NIIoAXXiU3JusJh4xJQHUdaHSEEsC6SwKrHcEEfxAYPYGCBD6I/Fmvj4hVoPKTii6xB5+Dlx
13WL2kcD70bsm1n3iON8FNHUJdE8hkfkhTOPEq3+jB1Ws5yy1bV7E3pQyl4tdr3pCVzNYmpYJmdw
B7VF16ZTfdF10tlaxDFpZd6XNFwb+MfMa1gyrPXt4R+g/irwj4Zj8kk9BvJi+F4V4HjLwZIAwo56
L5OsPeoOLRzggZq9+DydjBVrQ0lwyGI45d7eTnHomtCUozdGgoqVaO7izo4Hxfnpv+g9adiLAZUN
x6RM8B7cZsTtmV3/4VPDMdlwTApcV402AGLA8Lvvou8LcdDTQdn5m5+BXOdH8mWeOL1Ta+1Y/2Fn
7VQ5Jv0gw0mE9xFty1x5pHbtrn3lYaJonj1o3W9Nub4zuQYy5f3r5ph8Dc5mZLzuy4zGJz4uaQY2
8ct1xC8PKn0JZqKEJCy90O46EP2tSLfWs9jIsXZxWQnl3FRs7aq8zuzbM2FHLBeP8yqoybFbPQR1
Xa6cvEmIBWdT66n0fqxC5ZakwwN/oYsL0INCgfEyCjIkmwhRoEh6FjRnMpxOyWBtzNoTF/Y+Ail8
s95nvfQ9qQbgr6bsWIuqCzJGtlk3eDDpu32q2/uiZev0g9sq+e2t9h/77qG3kosTbG/yPG17MLPp
Rq4Y/PFeLU/bVNHR9GY7u17m72vca02p7GKnXnIRf41BsS/XS4QCodU+Lvkyr8oK78JyMO7lLkBO
fZ3HOe51XoCD4rX5vwSKeLpxlABR9oLlxnuTBq3E80j9I+rfRfTmnx9ffXr39oe/RRsb0f/uRRvu
zbTeC7t6kmQb9kryq5g/evOecs6ryRLyjySx576dqo2t7BH+2GenOdYpb5fs7Ea6b+o1XEcm5NKr
5hpIoIvOVz+QJan0xvo+hfWbHCDfE99+j23QHaV88ZwvavqU0j3q+/jcMi1TyiWIcrTdumepv/m2
BK1gVoPWfS2BuvqrCPbf+/h8ofnAkmcu5LbtWvekVSysmz8r42fKB1cEg02VOVgXCOBrLjZKUwUE
ncoY3o7dFATTXG19/SXJV6p4cgBol5ID2/Dq4PDPamu3pex8yZXx3o0wX8GroZzu3Ipa+M55aDut
e6BhxnKLHOQQAK2hHdRXTggbWIapTklJnJL8y1vJFSVVHjJjydRUN1IpQfGzgFucTBY0H0Pf7/TR
Jtuf7uASjEV5QmqRadKWRVYyHVDMN6VmB8lJagA3N/C4d0KN1Pi0z0fDYpunp3HljRt4xHIRUVF0
BH6tcpYrhMhHDDm8q7wwWJi8SBXeCGqk3DFPpx6AxaydEjvTA2MKUEdBgne1bKiPv6AcG5dkmeDh
jbLh55jBckmmek1OuyJ1jUI+IkzpIJbRcA1QmktvGZe3Mv0D/F6tS/9KzSicer1mCO5TTNir3SzZ
/PMXPmMC3NR9KAM6l7hir4AQUUucXrIlfMkWm8zmwcGHO4XqN/1pW426mKI5KY2UOtXhbF2253z/
44FHs5hKLracWdXto3YUYoNsKiqA9Qm1b0pd+48UdbfdHRInB8piAGmr3fbCWNkfpMztRLd7UKPa
i7tsKUQMpePzvUs30CYA0MdtFjb2NWv+BgfDnqdgTBFvCkmecvOB3VL3sZ/6w+EiIAzHuhz3ZRDc
sxHA66DHuVSSrYn7SSh8NHQRDwog66xptorBMLfL5pIAC4OFiF7s98EaZo/TAGE2cp63ptlqA4Rp
gDC3AAjj2nLXAWHMtjl7EmykAgjDKYa9qXWN57t9F+B1HBBm90YAYf7x/uPHSjS1pvhXgJwGAjPf
mVxTcnhhHvbVT+MEap0jiglcmkQumZypj1A1UIOQFAVUm3qnd6IRuFQCd7nnZQxlpGpw5Ci3tcJv
BfxivDGFGXHIzig4JS6n0wObyDLBFXVhpXfaNQVX6ib38vETP8briJ/UDfDqWZ85cS8CAirI3Nof
dEaU1ai0jkqlSwvFE4ioOP///df/pWRv1D61kMr2VP7hiiGVunmgfJo4QgB6rFbIatQ5xDwU9wCS
TtGzAt0l5htiDV/S3heF8gdkIntdKKbcKjmPTvgA1ZaLoDsWUKPWDQthcx8CnOQOYj8QlVA40kpl
wwrxa2bz+R2tG60ZipC4R7S5L8Y89/e+ywg8T48oVs/RUVqoipC8/OFA5/ZSq9jWN/4SCre4czpp
X4Xb3MXoIfInUdRHBEeW7ddFLAjkTs/v/lwHDcLSnzqB668WUG/CKlNhFYVXFHRcsmtlEw6Zmj8+
3iQIzqJwCKQ3lXDIrW2d6hdxOSt2EVB5Ta1Td+49eLC3/fgBXVadUe3gYsukpoJlXoleGg2AM+dp
nbqlCKa7cDi6ZMfvXSF6WZM/vPkzVV5Q82d2rqmZNz0I7PtqohL+9vz8tR/r2fmXVIx/6JmmGals
j4jGQK43aW5JTH/zvDiGvfyGtMYrIvqey/7qTSlWUBA3S+yJDGtfK5cDLmpOUM/v/8cML2NSlact
1EhC9Fk0pbi/+yjoc44NhzRNKSY9eqPduze7SRVrtGlKMT9qJ3DIPjEWuBrBirR9x5gjs1WOXmT2
71yH9upNKXaeRC/LzqqLv3hHr+lOsXHYZS6iH5Kz6BOu8cDCTO41BT7MxW9mvhUk982XLNwWNwTm
it+HGzKrpKp1tD8IQdn7MTlyJv2KOf41xaYuLTBruu9cc/2QkNAk9FjYMgou12PBCvIIFoPAUbws
MWofC5jFbcLCFteyOG9oEEHIicV1HrUnoxFIHxFPe05hUEEKJJ2mPYEziQ9DX2On+kgVYeYsnYzg
ULfjUsCpVlgbIJ7uMKJhLlZl4KQY7BBdNexOhityVLrG15MMvlA/MBBw1O7M8OH2geuwl6gGr5t9
1pWTn2DgUXRPY/MjcUPkTjXU8y5ilh/qRplCE2SPEsjnjaKRZz+m2L9DsA0SxUEXWm6F54gMbo3T
LUXP874IDsJ08Of3b9+/uhsdTcbibdRFjmOYgIwAz3XRIBKYDUVwX5rYJWPr9x/vGK7/GoCLdeJ5
pdi6xvh7i627160YwkGJAv7DkZiqIvi/xB0vjLhkQ0J46WC8heHL1GG7tyMQDzkpyHiBuIPyYD2K
yRQFQiVa4CGHhWtAXZolqUoH2npl8Xchm/S9KlwjLi1mt5ICjHG1aHWzw6yj/P4QyTYVGVp9nJBX
HEojIwR6l4D91T5DOrkDAVsvHVrOBdras7LKDDRpLBiPfj2j5kB7Cb8YlZ6RJHZEOmeQUKVMvNJn
25kSL3+JqcR1OQiwoCiwTuvNtevnW495dSl+w1rqTNc2rrwIdNlS0rdbL1uUuEObZ1HUrWQHqnpN
bn6lS5eTru1hvnLFaN24L78lvl0kmVcsslvDyAbpc2yQz7CvkiU0r2n8LLz52zNiBfpvz2hZS7fY
MnpvWsEV9wpwUBhF6zaEpt5oiTdk5X4Ta1xwVwd2hHLe18nRaEKzKT1v+E5/s3m5bxSKKNX0Glfl
N6jprVM3V3/68TNfxjwOO4nbXSzuUg6+3Ih3pZ6xqxTm1s3dOi0MfFCfz3QmT3kCvx1MzfW2KtmD
AtM4AI6MPN9rKyBYzHzEjAy1UA67Q3RArazGyZA+g6/V/NpFH3QpzEDHtiNYW7mV1YsU7nFiFiWn
7G+4I5svXv1NTRjcrav4GTjudYoreHKgHxmzs8M0oA1hgyTrqqldRoMxLN0RRMlDEQVTogpBVTro
+GYP+Q/RBq0ue1QAx+3PGyH44J4C8mCr9tXU4NSXum/9xSxq/6yMByQPYQOuToW/rGUNkf5NCetw
HPF0sBTRVWzIuEo/+5EpDJK39VrNk2pwP1O4FXRXg/u5gkLTvN2ygDvkib+PgPu3w/1s7z16/JAA
4WPPN+mLz+Z71oWYBCRPBfdT4rMMuJ+FlYtGZnnJJfvtECkrzFY5/jF/ducmE/5o2J8bMNM59udP
vfFfZuA/s1+CACp9eXNAQPS0Igrm6fl2APgJXujo+XI4UDWFd3Wd0Ej5bZtpKZZfcu0y+6ny4y+V
QECjtpkBv2HOKw0pzyyQweI/7w/R4WLLe135b4Y0bGbaV6YkOS2ks06XmunytFckmB/K0t4INJuB
paKuNM223+Vya398NL92i5xQ9ftmplea6UagqwJauCHrMjk0wxUNjfz+6CM4hHMq0nxzNHSBHl0Z
4X0DTG57B6uJOqBjRVzLOOUG3j3pDwAfy/AfpG+ek73PP/3dfdr2IevytAXsdgXevXtvJ/B/N/Bu
rD/41D+9TI7jBt6dm8LT6A4P2Eb4bhy8+34V3u2wgx5T04C8s/F+1o2fNiDvjX/9pPL4f3W376mR
ye8j5txA8NYFwTNOAODRBniG/NGQ0j516tuSADoepX3LEVY4iMkwkqA8dlwEcU9N7sk/jn1X+y9d
Nbl3+VOf/QTUSoqyNxF0E5TfOGF35qT2adL+HOn4OHq//4KU6AhShU5x1wzWXtK5fbh7R922IHsu
I+zJ/YWVJXWqHKbQfMlPAlefAEUPo7YG5f0ufVWLI4uEbJ6xPU3PwBnSajp/bmNC0HXtuYtTUofV
BaALGXME+j09yxOmlXEaJv0oidrxaNS1LC/wVtoRwC+Rj6647DA+76Vxx5qhx51OVyhgl6UujvG3
PlMn2EHCJcUYoR6zcTSOT3LMsCbCRn8GZtyYMznOX8VmKn/qzBM+uBSwz/HCEpEe3WHYYqoWDYwE
A3YM7uDz1j6XHOgtzlxOma69NKn14PmQQrb3tYaQkExjn+VrSjqQ8Ev65Puej4fGwelorET/cRKP
J1RBsHgMicuCNpmh1MBkmoXvIehQm2MkxoMkZfECLhIDilH6FIQmyIWO6aorcQ5WAMXw1qF5AS2I
7Ymlr7ZFtMQOrCbtdNJT8YJd06QsADnE5poORMWShsOfR5sakgmniiIAQiC+4ecsenE3enk3omIi
GbdbNnrHQcQKEOk3Y8km7VPkGnJ1VhYkRV/SLmsI2c4Hb/iKAK9QE3m1nE7phaCOy1rEEBrpBHuQ
opTjrptDpzoFq2CB9rqftdTbdK0Hz5yDJty8AjwpTdRdGlG72S8tGxQsKxD9YSsw7qV66cJrBMWK
Pjue2Dv0k8ZDHgr64cbq36dGu1CD9SfZmJkZSjDs2QxHEtRlPjO8dH1nkGxd0/RyGC5hhmizr9lF
48TRi/cH02UoXDQ9fjUSbY/r/ErtUK93UUO+WV7VtYGgxs9eDQxYnnRexuO4oqJQNbXDfeUQUjgM
NwMbhUE3mrRNBCQroRl4/s6Weqhv+g4+BcjT28FxutRwb+47yOBrqjzC1dJMzU4nl8UVaF4Bb+C3
nLzicER4MViIttGhemcq7pzi9mg7FSGdW3UgXR+xfuAEGzvNTwnheGJbpjSgb6Sho4HFsRLRo4Y/
rPrhkSjzZBa5mwTr1ZCHKGuBcIubsCvp0uyhibbZvBaK77TC/feBsKvYo50dftzllA0j/tiINhmL
HkUlUTGGrbuuGWm2OQbdjYWWAWhUZYxuQdcOGprxxNM3wdgt3WVTlytdAtl/x4Z31s3Y3yuPMO8Z
vRF5lLRjdmiYz8LTuS3Zj6MXDFfeQLANNNR8mO5oWe1Yn9MPBo7STWhpluUHQLOm2/1nAvwyM+Z4
Z2uIAd+EJLwztt+O2A3ZD6hA7dFgqrA8dPDhuwNt0WZkc125EOcUtQ5b6lGVYOww8VhU+a1yp0In
ylUZJMA5XT/IMfWpsC8W8mAeAOWo0LhgapmCt6ntdzsdDC3up9pa7/2MT0eJ6mmHzm7oxxkzMqL1
ibZkYTps1o7GooHT+5GTgAODuxX3bNq4fuFp+KluFJrPkk+HBv+ejDrUJa6RNmAugOq5XyDmnFel
Q0oKGWatnlGAE21SXo12k65BNvSStbAkH7JkZd9tWcehotLYDgtyc8dEZIJVNOoed2ORgnprl4sO
U3x2zGaEmZtSJe1YQ3N5rqnmMyvYefpSJ1kqR15GJiNqA3uW1hOYWUY9d9Dy9/BnqwU9O+16a12P
wno9M2ch+L2suti4RWXIZ1na7uomHMkjl69uJrMZwM57zhqZ/vYy/ZodBp5NiRNbJ0WguDV4fHkg
KnikrocWUvqP9+/ump5Way3T6ohm0erD+18mcQiGIi7nupiODnW/5jyh/LgUzqCJ8fhU4SgHwzd5
d2qe3V8yWRYauYtcGAWZdtiJuIz5kk4CUbDu5yw+diQIZombCxVu+EEy7HZHKdqf8CbbrKUXL/cP
97lcR0aGdibzxriToxb15gDbOD6sbuKPlKBrP7ankKvs7m/HUeCauYf8wMYl9l1+7CeUGJgG8VuR
1VO7FcXdOEIdW86tWnZvdzKybdcKaN2Op/mwlxJcTS1ikUJM+jKmMDCIuWXdn23zR0E4x17RBpZj
LOKCEdN8IlXDidoX1ZxltaXYFBD4zFUBKahDNj9w6VPCqE834h4vC54JZ12Ho1+hfF2vR46lgPOS
fktDQDrzHpaMDyyTVgyWxlXpiIhldNvUx315wv6KviCDXkoK0T29khS695fTRAjbJ62HD4bjjSh9
ckofcpgqnm602a+TkfsqG3MZ/7P9cUzEy0o3nm78t/ie/qcLj9LPCQceB6GygSBdTE+QsRrUA2Fe
xFGw39cE8dW8mCakD2RqGfh3+kt0yXh/0D5NR4yEg3UgVx3+42CYtJ9u2Dnhu3+67/yjuFrlo56H
Wey6leLCU3kjDi6lNisHw7itHcU6t2zbaOoPbPqxFJR6e3s7/tWvD3IxemMCyouwLNjOzgOnzJZ8
T8jdOCBf24a3aXt0ZnuhGDT9WJp+LE0/FiXhqrXUWHGoRV+DVS3G2N199GB378FDq5TyWyT/hFLi
+Zuf6eX5oT9tHW7NBgOmXMj1gC0NtJiZO6PjdgtrR4Z160HLK4pwUsnqMRCZbUtrHCaK5hk3bVVC
wjWZhRMyYxfF4K88VxrEb79G++8OPywzDuYk7NUWhmYmDSgmAtBqqd9i7FhVSBrWPWdUh32nnkBn
v2iZufVOjaGjQ2LXMFrRaXnc7Xd/dg7ipt7lHQtPhyp3OWd5V2UZKYOEevfRZ9y6Ia0yTghmk10R
XEEeJr6eoi3QKsEPTUQnpB7Hp/LV/NcWCu7jAB5bvhPv7SghStnlTpzvMQcgHxglTh5J0hBxCree
kra8myoSFXtjTd1THt4zJoqbzEKnMd5irpW/0Vw16ZFzb9HgZcRL73Tdh4NxF1a1UQ+BcUwsP6aT
QYeYzCeOVLD4n63onyANrCfM5YTzk4usK8aQGR/dQTKkNe1RMjIGjJ3bwUjnMjVabgZtSvFvimVG
2qB2dfnoupabIh2VAFQAAnHMm8PDj9VkYanjcHWN7OxtW0+Cm7xGNMapFT+TQV+0z1VtinOlWrqD
z86wzw2G5cAAE2bPPIMBeRt3hfmmhLbH6bVdO3C/MU7ZCGsc9gokOPXbSbT5upv0ZJy5Ff3XZDw+
R91/z+p+n55MUAn68/WIrtHnn+9Gb/R9TLYJJ/9u9I5P7xKgK64rlNTBYSt6nowGwEC23iXE+SBu
gvIL5xufW1vVIDtmN/gICNBWytaWCfmft1vbpgK+nwyS337dfvz48QWrv26rEJVcNxkfb1kAizdk
95Chd2NXxS0ha3PRmBqzdCE+Z42Cf+n16iThIm1jw7/2VXvJwdcx5Umipx6mEj38dlNdN9qw9KaV
5nUN+RrUIvCIPiaQrJyPyWCQzjF4tO0HZeZb253X8nexgnKVZbAw+z9PSBOc3eX2riuQ37CD1et/
Z72QQMOBIEQa8HxmzpCgAdSpfI+4UMU4RVLAms6F92tugR2TJ5FlshyQ9pJLgvUjp8MSSsJTLmvK
PNq+8eb+DmO8xdL9Kcna6agXA4RFwLVHy9L8gAQIq1IW5Hv3LtiIK2v6Wwrym4DNdzgApPcoAaM0
kKuLN0r+0rAFuMDtSY7zF/TBoL4mqU7sB5EDFTiUQMU2D6nj3I8mywukJp2cgGklnQmNrcWRZNSb
jWSM+II12MLRkFgRAhVhNNnAgF+4tQWf2im87eRDBAseClI/+hIOiY+6VjzBZRlVaBypfGyBAzJY
Q0A89XhY8eJrIDrDoRpa0Su1otQXyplbwKfwWsgQy19RynjDZsINDCyv4YE0Fj9BRZggJKItL854
sKm7HQ+xEFRD+LTO7GkcSUdZActDhlpFCIFhz/DT5L9JNgOoAnrEBNqd3Sy2HD9wmc3xMoxoTWHQ
OgqD3kqMlMJHjhyUL29MUMIOgJvgHZPii5UuRGzO4hH5/ApmIodh2Cv2BS4eHV/AeGi/0AFyOAaG
lpFotKoEtpdQvxOAfhJSv9ZsQYENCmv2SIELaYI23gjQJeE1Gd+Y/3eQEocBdOhFoh4Fht2tXdsq
eRoeepAi2wYLNICENjng9pUyJ/Pw8/lx8LyZ1cPvTubVTdaB/1cDOzSyvQ7ZPkQ/9qWmTYV78XB1
SyptsKYmgTg+/7rlVJSHj9lBvrYDkTtS8QiyaAgYWURot1zSfTBI5KNuK/L1L4ZJE1rGJBHiey6U
CTvKGugnJ/HROaLbkvkpEnxJPsreAEcOaBOG4gtEDKFqj4Xktj8jcV02qbHFcBmf/cxQIDflUmxE
Q/ByYQ31wQdxTA7o48zKGvarIcKfamtpsQ2pRG9wYkMHcNzzNKL+WW1TzcsSGpn/9li7t7z5vJ7w
yINJTWEFMZLYWzFVgLexY+s9mvbHR7Cf1WbmnKqfOoRbXJYZ0HmocWyDihyZrs5LooDnsVTYP9yR
2BUxS1ISSpEn4m7VTjAUOMsn3xbYX8qAPktD6DIyJlD9uiYmDt+o7MrVTjFe1kN4MO4RBFQizMrG
IrPjg5yjuO0iE5DZWnxwast8k6FHmgPrSiZeHwAb3LyAsrX0nZvE2rcYWJFnQRXgRml9sZNWQXXa
cbgTm2dmhlkCjFfaiPQMK516SsZEZmUc9bW7VhYoqiJ1+SA3OTbL9nyaONuwmAqhvDf0qFt6YxtO
/ay2Ghu4nU8OX5B/3inyzzFhyngh3i7gYy5j5jZ4u5kXsaSrOj+NrkjyvnVp/LtH9l8P3g7hINze
A4p51u2MT580eDtfDtrg7Y56L4ndjLqu/5dPYlGvQfWYx2QAcfNYtaI/bYXjqMHbCaoaEoBllOcp
tgTIzM8OiDH2mL8lG4lfu8JlxOQ7UQpCM/oPnxq8XYO3uw14O2sjWYe3s27aZ09q8Hb3fWa/LlMy
f4++ABbo8HZ7NwJv9wpgDfGftvXjycOZNVlWgSLqs5Qh4L7KfNRnhnB6FCcbnFTSjrJqG8xflz7d
wQJcp004J0mXywker3snBuyjQEwCJIcupDHMs3v7MUD7smUybgVqwvyQUmAza6ATqNYVs/cNdOIr
4rSmwQi3b/ItGFBRuTX7wa2BrZSVyS1Olx+0Tye9n4k5Dsh1CQIHVn0EIYaDyH4CEU0M7znfCwH3
hrBdRqHZcTLoOljspyJXxCmHyajfHTjEtY5/zeaeGBBbYblXP3UxCSj5Tfv9ycDX+zp4LJ5J+/R2
QWODDeEx6OROjAhPWWsydpZkI1JJUnCgLWxk2QIgJ4mjJ4A74YQAJzXcTLAwim7/CwwfVk9N3o0Q
rJhXPCa9Fb1mGpOfYpArvC0inIr9kjZhUomantJjnlml5lnIlHQ0iDtge2xfzYo4KvcjQkx6vQeY
10Hgw5WGMVXoPquecYH+avHSJmO3vowdzC5ERsTEQ5I4gdtH1JElFWTWUW5CBRq2EMtXHH3CJVQo
X851aVWSJiBRTDs9xNGycKzbY5IhyohgkZkk5vJ3YAxnBNOHAbbhKuiH4CuMzEKIKrcOqpeFkEJQ
B2J+yVY2VCqFJBw6wFjphiORzLURabtlvqI4zmQbKddwbJTgTKAd0sIRC9wohT6DnEFYRHlxPlkQ
R9ihXIKlb+xZlMkJ+XRLYJCMp7ZVhAFcUfUdrMSChkOLwc8CuUlXCuLyK36kgnbYguJsTaRb/D+z
ZB1GxWHQmGas2UjlsrqiH7ix1GHmgjf2jQZ7BMtLr5fnoiKFN2BQAAfc8aPxyZ3iUdyNekr5+xsJ
3hauzuhqEAZc3813PmubjlDC0/JsefKJkYfY+M/9RL93s35D9+XD8PwTnNWvD3Pc96v0nCp3lp60
AgAsEn5lPhnPL8s+5MEfBYJL30xtLA6tFUdAUUjIIZKQ61g+TvAT1qnfTHLpIw9Y7D0mUkaT41J3
x+o2Kq3jSS4Rdu0+xcVPUAyQdDgLg9tYgVaoolJaE7txhHFxdgrYYARDLEgCY/7gMnrKbHKkqDG1
NTxHxby8pEc/m9+7RVV8l3zWa4/oWqzqUuWws0tnfuRnfZEJzZuHKtcF477NoBjTAsoK4o2VFNr9
vcctuCpqiCuGbZgjHqlv3BI0FoM0O4UtbT6tRbvdXpLTYsm0gjcQeZmqsf2oGtuLbMY3h+/ffRwJ
aUoxJxuni6Nevk/evXs7O/fu7+yGwmcnAvPrpAoxCdHcSsn1bpHyVu/Mi9Peu7MB4Pk3nwtxD/1W
viu3uPlO3170zSp68la+tnKCfIWZ/iX64OkhMZ2tHdlF3zQzfbU2ZRdJ8KyUNzN9tZl2WqTcW899
03L/lP6/mlq6pMnxR1Ybbg4rIm0q+7vWzH+NFK8ixSVh9X/e1u6FV7dQ1rTVzU6l++bvjYSuTUIL
jfBdM6trm9Vfor+6mELULH6cK4tCV3twXuhR1Cz+RlYvchKvMqs20Y2Yri6mhXhiWVU/NKp1ZSUw
6x0EDdHI7uqy+/cwmTP/VkR3HlxiDnnewjDHs6oZN+/Sr1bhw7tdgb21ms2FArJwXOm9ln6pvNzG
m2YGFhMElmaRP3+JfvAsf9PKqfRLM8WrqP6SrFbnvhRfbhyX1fX/tAAXk93srivMrhdf909FD1d/
aZTE1ZVERXQXfGjm+OpzXDEPKxM5z2y7fouQvbqUL19oas4pwiiUXBW10TzTk4XT2VjuzkwsUvJr
ksTc2tFWscyHylJs7Pel7fdfopcGPLYE+jIfmom+2uaxjBBXZH2Via7S46+A5hHPiHC4EKUfA2el
980j3w316+F8wmqm4lzbXLnw3HdJsaZSrgMOsN/U4Xn+3Q7malu43pH7dsnOLHabtyAarcWOHpq/
fs89dpjk8sT+ddTtaLIrFf33Hz54qFl0x4ZDxiOmZroxg70oH0FYiDxc+n3UvU4NJIQp6vvnlN5b
IRlfYF29hsr8WbxcsXocISOoOsmR+7CPpPoD/Pd+idkx9vfUIYbjrJuHPFizAPu8LgAnc25Tzr9L
gDXfg1lur7t0Xi2ZQ1Pm7Gcm1LJq9MGyCcp+fkElQfm7MGSkhf4jr7snMEL+9uvuE7a+nhobW8mP
L3NVnbSD4v/2a40GlsQhafoHS0f/OKW0JMqygfpeSnpKxc/rEl/ILSj3CvIxnYldBPUFV/q7gvpK
RfsVfIuw9ciPBu61/gJ9tzYGpTnV8m/VnbzjCrV8QZKr4MkJ4qiTKJUvBQpb6OG+dEWAHSqNVDfo
OOM8N6e6YXtKa7Vx5zh3YTawUM6oEiMVlFmbd8+auDHsQhK3pbauG5yh9t12aRUS6g93kXH8eabG
pPh1lMDxQxWXVXpwY4qVfPVHqFr03XaOJ1RqZbRxVQ2VyAIC0amVsamKS6UweX2XLxoR8bDKREKt
o0buep3bgzAOevu4yit3vo2nBc63OMU46Hy1nWPHU89cK4WhsMVz+M2UgIX6GCuys+fqUszlbuWf
kN6//nY1ep+lgs6YtnLCVy+T43jSA99/MWi+aT/lDMhgttUHpEy6M+z2eNSFrtQKFqnqRRgRSolY
n+nuUlRnL9yz9OY1dJ20PXHtfvJ+UioINIl01XrQ/BbL1NX0Wfd6SjCRXV92qypKVzssIkeWqCgY
uT8VnNXlZYWTuTKg6loNsqDPTlX29xPVocZdSdlk6Z7ZqTUQR2Q36Gw1gUp1I68ipoqRg435UY98
VpwXmCTh0GQgYm6FkCvMixUSq+aQ+amI8CWjeF9FqT5DNTI/k3Gy1FB97vvGaH/EAZ2TTtS7INBE
r7vi7Tq8h4W+2MWb6tewwjCqvVlSW95jnGSO4eksOWqPzocXdJE2t0AXNYMnqGzp6mqUpNxEsLHT
vYlVvIwlza6vISG8ywUleQhIxU5vWC3nBK4O8tje2dONpot0cOcbVsunGxYrQ1Wqk/rTjcePi3jL
NcXOrl3h8jANqyUdMJkHX0d9LaG51/ZfCMRxMwvN7ficQTk0575jfwmeAKG5ww8vZqNupX5Wbhfn
/1eJwc2Gaavhjzc3r4u0tdysY7W0cHwtq6Xnu6zdtefv0RZAXRQgUxfph62LTPZF3TUDO8dKg6CL
9I/J0TLDWOw4rDKIes81emEWKTMwPK0SbjrhxXZhVTSBhHgQKxVy3VG6QwJfP95/IWmpvJlo/+Nb
wkbHEB0rrpCNoUijZxChBvkT9vZoL6KDFG1QgExXmBK4XDNJqfo+0hzmJMCerivqrnOsqw0LWpYj
lwdiXg8K8s3X7TL7v/JR3ma2vF6CC66GicaH97IVvYxPaSRLm7m6t+36vsaDCU00blfrxLcQX4lt
5wzKHxjn6I5jbTqI/yKfFlqikUj8JT4wvnYFquirTXgIPqxhrCCszteUDOMTtaEjFJbRjh2ZDhcl
ckTEV0QeUwvABYIJVhPLtpY/XBP2KrqD0J93/8Vdorm2YjjirsJOZWYrsmqrRUQu2qibUOoyodQP
4iB03fnIKxDijjN1l+KV5x1rghhcJAOiA1aQ8UvaVU6il54pc1oSvXaqJjkc0Vao1ESMe+ogGGLI
s8Y98S+6CC7yR5CzELAp3ivr+pYlCLARX0We286z0NmNuoN/O0rGUmvEUZplW5l1yHHdC7j35j8O
Du54yjoX6xXnnUv6dqZ1OqsnPX41EqbBwT0Wth4OxswsNdH6NrZnyU+4YfTzmWHJxpaoHe1im+c6
xzrHJrKElrZCH7SGLTPXaK3oR2tIKX3Up61j26Kq9oLbFiJ3nSqRmyBPaoHE1jmiK5Jeoqfe9EIs
fYiYfpn0aA4eiBGl8yzPRLg9+SkZtcmRET7P7xuO5qqmI7mAWBC/qDUbI+XeI7JD/g6NUrs4Trw+
6a+XqHIT1luwgnNzq8YtuDWLWMawNWbzBobsZu0oskiwMo4nA5aMKAot4cXigvnQjA3jIC3tEmwQ
yU/os7YyV7pC3l5Tt2DFneE8Dd020Z/ZFpLyhuNoDf2AuJprbukuijniBiHNQhtiWt0OU8fvS7PX
L6JA1c1Z66f0DVSqO4aTVa3OXDrZ0XiGsehQfx87VhfVcJ2O4pN1eLPdjedTnzPoH60Jm82ODtcl
+E1/KqkX7vKjV0MMxF1slsB1Si/aBNplbf7MBCxSo+g6XokU6Ti8m3yXDY+gdxeoT42bVXSvfj+X
wyONJ4Zal9bnrcq44wTjVzW0g6eMbpTht1eGhwhUncfjVqu913zzMgMOOlp8iEit58dmXRlvr+Ry
kslFKMzFTMluGGY7vRnQCE7zeb+f0CKxbZKdNwfs09mIxYunwNWO2FJt55VUlZ0FUZKLAlnf40nI
CmAJOX3ASnBKhctMqYOQSYdwEJpRssckYPNMulr8dnVrA79YX9PuuJHQGyyh41My6B7MY5An/AQT
Ud4/+lqEzmgb3Ab5pkbbjhLNAAQdWfK955AVFbWvVs2owLgqncMYZJHDfrDdJFLOWgUjoatQp5LG
XOTy7Sg3KTPT2iPp7aRj48OQjG1QIEMkwsXGw+hYkBwrI7LHmSXUSn6K0+D2hKW9iBMYR2XgXO01
lx+kg63SLZzG50zWmhBaWicOMRZXNk8R9WooWtpo70rnaN1KzMMgvKEvL5a8jTtT0/SpaBiK5Pwv
uhSqg51w7FrQ5+vPPetwqG1PE8p2WqzR4vJgZSBAB/dlxzONbDWAyXSOC8cxX50u4BAiDJNB2H31
+mO+0VRzgiFfzDTP+det7Tazsdpyn6UdbkAYafpZKr3CsfpQ0U2XkHCBT8/dGhAbeKAc0O083cgr
Bhr4RZtmHIorWErMIOw+LTY/4aKcwS1jRCZX1cAvfF3S7oNS/UnTVLRpKgqjdy4G2al0pCmDdi8B
/8knUxEN/ALMSblm72IDdn4el0m9MBhVgBbQt3azQu/W5fhoYKeXRZyxkt3jqzyvW8pdzBl9A78I
W9uNh188Kqyd0XG7hc2pQFfrQeuRA7rUWD3+l+uAXzy6EfCLA2JSval8OF5BNXdCuPPrNxR9acUg
WWVsDfYioL5KJXUX6sXlbFQSZfVB+v0ok5DcpczmjA5QZ3lkFf9PHa5OlUxO2parJsLo+h3JVaWm
gcKA4JN+/+HgFem/0Wcle05G6WSo2BLH4dEXESVznVUhpaqNtssZHoeWdy6U66uEipvHLgSmiNGX
uNsL2SKcVetrRZawF5HqVqRYjqea4zgX3R7GeeaWbXJJVY0JZ1t9rfD5J3264OgZiE8RHm9PCGzI
5+4kqhiwB1cVmJ6EGILlYo8SQmB9+n4o6jVbT8LlcX0tBLGal1vanJoCQKfC57tgc8X7EEn1L3Oc
xH0vzqS5KQBSVEmvlVdm8QrEwDf2sr5kJRlVojOLNgmB3lHk5SSVlBMMITKSTY6pqutysL4ISQ5d
klaEBMcU+6lKfCvKE2NxT7VBJ6eIIteevjQxlI4FkWhGlloc9ix2t1F0hdAuoyBy64oIeSKEGLEm
NpVQi0VI9e2AukT6xjEYa9XGOZ10aME0hnechlwCgybU7OJ3RKBU76Pn4wbl67m58tE5DOJuh5XW
eVJN7F1NhXubzBgwZjHGLFLnXXd7X+is5T1zJxH89jY30G07ZwTFCRbg6CXHFP1t7zl6CJqRnPLx
8Z53629VrU2tpTILFVjN0F51QxlEr3q97hAFv/ViMiI9X9nk52VS5xBwLShz+0pP+exllxV+PQVw
X+kR6nf+rTc0cuwThd989eLlmzshz0rHWXWQQ49oO5Ui81uy15Tjbt+ST5w5OSY9PBEzQyva/EBZ
ZoFl03kWzIbGwe3zaBnDG3XsBDZP9uxez35r3anKSKNFyDx/Splh82D3B1mpx7yhv38/Ucp5Zila
BKkspWxycfQpcQqFtWEGIZN96LbyIKDhFydijYSN97Nu/HTjkPWbwQT8R5ewwxkN5ZoAB5CteS+W
bxzIEnRKTL5BkCtmsaQdLZGtz+QLVfaOAVUxn+TdIK5BC8JpgwVqvopOykvmS1d09qUl52VZeuiv
u8V/JmTfXDa0NDp/cdPHh1w1z7uV+h4bioADLTMoK1aj8kXemI4Vi09Oku6X0ZTcu3MhD2yV+4AG
8iSjXUo5RwfascVLGngtPlBjH0KmMt/50XZ5A/NP8zQ70jYR1ZsLBgywBHBXJE8RXsUEQUPq8jXW
QcaQ/mJZNAKVNYqcDI2QJzRXTjaeeUxScN1RZ05zGgwOwGAhOw6REcSPA3PRk/WAandEHnLFBQMs
K8YcbmKKzXnYdoquHq5o8tuK9okjkXToR3/jIi9B1ANjFDrvtQdfRpt/e/n6To7F1H3k6gsGwmoA
BRbrEyfo2vuvDrZePLfYgB3Es3V0SaeZvWLvWPjA1O0h55QegEsoaMf1ONGrebuujnHrLZj5fgLX
ssCMxcHppGrioCkHWaYc5K1AdhkWAowzxBoHeGT20pCbQmwUipl+s3y1/2r/JbidE8iUxqd9E2QT
LAmTt3BygBR2gKqQnLrtmJmjhugzEiGhQiWPR8SMktFd4l4uQMTwThiadxDPqEOv2CkCa5XME6JR
RIVZZoya5xvxJ4vEx2C92ymXM42CD2oPzTpG4oWuaidOZFcT0QY+NJM/DbmxCnzocSmhlvxnC503
N5H2WL9c0mufDfT94VFcNyq8t4i9BWRZAx9q4EP4ZYP078/R4yqetsAUTKsvk8xV9WHB+Gg9fIWk
C72SuJDBeG9vpzh0TQTGozeJcRL6Ae3sPMjH+4Iw6EUsO+i2CziM61FkDXxo0sNYj8fvFOp2U/5t
uJEb+BAi3LC3yDGps3ZIB0qbEeh6ulGGD3mGlnBKAZkO+cPaPXt+XseU5PxQjt7RXgvilE+Jhfgs
zFbJn13SympQBDi5ohHUf07/LJz9+lSZhW4xgM2NzyZ9oPZwh7r4byW2mocJ4qMUFx1Hh+Aq7nxG
6R6OTw8wIiUgkxHO2KgaSlWZlSupwAFzHj4ZONXJyHHLL+euFqpXFCqzEo0sJUKLh5ZRzEi9iEZG
NkQ/67oEdTuVu+HBAd1xhZc6KBvLdRNOgmps1VeDCBBfMKMPvqABfLz/iIcmKEzjhq05MRe0TNkN
29suFFNRvbvIG+OMxhtzS/33kyZd5I2BfG28scYba7wxGAcXikHjjTXe2Lrb3BR+5dmTos1Nw6V5
gaNT5KxrjZ6dwuipeGOtuSWsLmZEZLtM3xeYn1b0x7ZvRDFHSB/GN7OiY80eK7uZ6rTmdMWbThXs
X61N14L2eNs7wV+cQgjv7T68/2h3xwvinLqxUgHHfNnjEddU3VGsplrx/2YI4Wevt9cQvLicKPg2
bSu1b6vIxWOUuYbggOONXATZNg1/BQ9rbq0GDXooylDEwQhGFHkwBBtw4yORCPqoRkhaKy5SFDHY
kSLJKGIXN6k2IWRIa2sT7iNUZRFTqYLNbqN6CNeuVcS6J7Ap0RQr9IOJNnN6lT9Xy3QgNhHsAERF
DUvNTQKsN6LV8TzVX2Ornau93qvYC16uKSm6UL6qVEKNYJEnbIDqZXzjq5y9+QbVMDRK50YoHfye
UEsNxLNUaN2Y3ZiLeReVYLLyzdfYI26qOzYvuUmqsEuGUgb1lMHt2N48lyrQ5GqFvyd1DAa5UtZk
W4Xkr7HGhevUHV68P6jqsdtXEXqA9Zh0XsbjuLLM5j0IoAFnzt8s57xeGu7e9pdTUYnNO7qJkvfs
1eBL0gNi8LtdQwJ7LKUbbm7Zu9ZR/p6WepZbpeci6CviPLA09Xx1fGKfXr94sPfAEhPTnGLllMMV
Owb9f/a+djltZFv7VlQ+P05SZRjA3z7Hrpf4Y5yMnfg1zCSzp05NCWhAsZDYkrDj/NoX8p6qXEsu
ZV/J+6zVLZBAwiIGR8Kd2ds2SAi1evXq9fGsZy1sloxgyzC0CXURQi7yucCm47/UAFbRTGjhu78z
Hcvvc4xr0YEkb1vGqwv0+bUFuIZvytxeKNLiC+TXoXfeeHAC84vxClbIa2421BBgRCEWIGo3VDko
v46JAiy5sSzwLEenOswu/bTwesqjiI0gMgCyh1UDLJKFyv4WBR2LK8wYgBbmUJiNmN1TGmvuEplA
xgmKt8gub6KFGYv9e8ATx1K/twZS/zQwooLJYjkskHRceqaJUo50CzrTtBzKE0JTn9di6pBcc9Lh
i/V3/MlyoTOQy6XCSY3hqwzkuAMApSAjjP6M4Q4ZLlBtrdj8J70A4o0px0W4iK0wPYjp+24bTCII
1U1o9zepCt0eyVZnscYAjL2Ofp3WcdjGdFjPIXMfikxhT6DjtrSO03IhpuUi2T1I0nETDcZabZ6y
Ameb7ChJupEZWMP2HxTzmDQDoQtpfaX11dHGjFwen29rfaX11YxczNVXMYm5P+wIooKl3jW7HMUw
Ea10vaONK+tWkA+F6B4qOWuV6lapsluq7jerO4fbe4eVyj82chfHwVia6LWYPHyT48jqFLnt80+8
k7uBpAzhXePD++loeGT+tmm+1mD+jsFHhebJ1ldmeyJ5TZ01kJ+G0rtT9NEH8XHPUPpjrEUR1HGx
qyy3VahTEHqB6J0RqHDVkMNGHhxIC5c9tgGYvogGHKF4arfdRgtTfl8lu1n062/enwPlxYHnKTU2
Di7TEpjEZrd3a9y8q7CxWRrAusZmT0BkfAvrF9zspzLV0KQKbTTVUy0Nfvnsg/rkSnQskwOuLFaR
1rofpCy9dwPJC/eKpERmI96N7AdOROyuQUg2rvMLGXnTEdmlR96Oz3diSrCQcqEjskuXi2TzV0Ur
YhITs/7RyXAtrMfk4a+B9U+ko2gTsGn8fnNZopbrRkDOTvqMsuXzYv0BbmNW5NG/AH8gJruF3L+0
XbP0/ev4fLf4cqHtmqXLRfLGXqc0CjuGk0wwCg3H+WHED8K8Cqdk8BpRBu6froD0AyOWbUZe5iG+
qWrFJLznLNKh553HNgzH53u5VEz1OGcDg0F14f0K+/Okwl4myihB5/hiaKp+YMRGCF560R6BM1BF
RJlokHkOceRhMBCBB7gtdBb1H0R3xHY/JECMqSvuRcDk8GhI050tPTJc1AoR6T3qr6lqKHJjxitR
7iHwFhPqtNqb/OLr29YQIyRfKNNACgWu3+QWFIiJj4T/2ghj5FjcYijwA0BUNefhtCKcOgjfY9k5
B7pAfDEHQ1sAINWlMnxV3UitMVQwntopkXTiLUIjDKjvEj4Aqks8XGrJKYvaEL13sDlOi9HAfEDY
3gNinDgy6WimidAS9TNU1NOgJLrlg0KLTWyURNqtSMsHaPkSqG3nEo2GReCLIGp124eZqchVWeg8
olGIhyYancswid4GWdoJwBKTJ16ZPPnUohhh7HtVURCgSuNoo/PFVMWbqnNB4mGs6Pi18OrSdW9x
OS4Pq2zXuaiga3l+cOPiGkwobINmg19NDp649mjgRI6Hb/ApjnshGz2oV7rtA8+XbvtA+RcbvF1A
W6Gphnpxo4lGNdEoldnEy2HRjR6Nw7akWpsiN9ve39ne3dljm2KMbR+3/06vMOW4QXrp63yLZ09q
s9m2D2VuQTPpFQH3C6JNeEN8hL8ycdf+4duEFkfjh1ouiEYb5OCDSu8xd6jnmYP5bulTHkdy3NR4
ITSjB7Wt6h6Ww74SNhVY/Lklx5O1lCj8P60O+rjxYmhGtVw8uZnLtWp6OaXeJojkPbaQi5yDD4HH
A9FGANXyB9wT17xzgVFFxExwCSJ14QxDr9gA6XGEn6O/scTlO4TenQCW95gBo8gPJzhGhJG6qoKt
kdtOh21VZDmnQFh2ILwplm08iiIBmSeR+HQpX++6CZpjCgpnFevCVyGkFF/gOSAKPikxjslDsaQ6
jd4wigfcK3w9RaiDXS+r6BYeAska2afq+gJLJ6e8Yvcfk8u1QTXKJvJcuUApXjT1NlEJYbtOr2Sj
LX2Hcr++oaghgVmBmYGMHSXgSB2TWuakH+IAMvFG78rGd2GGz3KdX9CePqv4rwFikh5ZTHSKpZgh
B6D87LsjG0yh6B7o+r5FbQQBWiIj03QeQkOTpj9ieQWwTx3rn8gSE20/taLvUIlVAkVoSqGUZmRb
Vh2xZmTbCFmCOby3zK4DeWpEUeXwJfTLUzpR6CjEk6MQv0ETolmr4w9dLzBehXuihIRGSIfy1BBA
y86zAkpT8XokOzFzoXjoN/hyjH+jAEymocxPNPy00HNKlmJ6PU/iMbCA9JJOzwshybbmPdGSJYaW
tNnzhIxITovP6YXeEULrDBKixQcVlQBcAP0KzpE7sXF8jdIR9GbolFpoNh9rBDIRpZHsZ8UueKzB
vGkM1ceXrpkUryqlEFRtxHTnxp9Eoqot2AUs2OPGiyFR1XKxgFwkb2W/I+QTr/WYEKFSdMekCJCD
4g6uDA84UsSMgwPzM2KBzKQjiVEQE2qjq5oAkeA5jsTqAYzzt9cNwFERNDY9MO9QPR1CyHbPBXSl
PzDqFH0Kw48UYxyOPASmhPHJaI0ChvyH7/zJrW8c492HxlkYxqKSAJQRuChoIVpDH+HK2MWjV/zz
aeD0InFP6+WxwPI4buSTl3VJhXdaFhaShdGQIz3oeoNqOqQ4JCU0FBPpPhcqCdZcyRE9NwBDNI5z
UD0snYqG1Nse4TcMUmlSP8Yr8sAspy5Icfe263St3kh9ZUs8uFBn8EFlvN3H90Cz4au6hkVNwCax
e1JwOI+BI1CjcYNxwnVFX0A1bEgxB+NCr/Hd0kVM0qOyHItUMinVnmN9RUkfOtfRpzouwv+kb/vm
HXIGkkvLc0F8TcPEPUzFByJAHa5XKTIWJUz2Mu4zfEHjTUHfoDEw/J8ijzgFpiCZ9WA4wH+BDKAj
nRKEkFRtIib+EPLUlfV8lF4ChsmE+FC56EAgoEorA1J5h8gSLTPIXEcEwhtQb2m6KEk/PteJY22L
lXGLh/9w74uUYOlquJkSrKRquH2GATqMDe8IH8lJaFFzXkEcPoHc0YKzoQviZmYjV+jiOQVxO9DG
uiBOF8RhS3ZcXRCnC+KcHlyCsAZOF8TBUvXblgVWdtcx27ogrgAFcfsM75dGj9dtl0EDwM7obllV
7YWWEvKxUHtUEIePrKwgbitupCfkuakI7TFKjvR8Ed94evEgVeV9/2acjq2/KVcUDrjbPfPgwx/K
mu1ISdyCZuAPRQGnIjnkGnbh6iglxH9PncIDjrEsZaICrFX2trd2qhWJAFEGG37pejQ7qcHJ6Uup
R9Nygfmv8D+pBOfrkivzizWg2FeY+rBs1NnKSCCFJj5unRgfRevEexgibCEDHYpUHkUckvaqRUE9
7jKAMCGyEpw64Q+PP4hM8C0d6nnuaEgBEGpXgBhgD1hcG73rueqJwiZhtoSx95OXBnxdBE+6lvDi
sOQool12jy1yKCqMt2UOvq1rjRCJCEkQ4riYdxl+o3CueYvIrC8cBNm48YUwfHcg7ik617G6XeHR
2RN5pQZgnEOL9EII48N+fCN/QdG2H9rY1Q7eEoigi6ktXO/y3E/m55oeZBme5hMVMSUusxZfJpJf
vbMvsrMnIyHqXHDNPYDaSFE42MrD9lBTKjfMmJWNJmlXC7s9EA1jEkxs5j7ADLSni3+OTBuAhUnl
DGdLPIECK2Q7utYXOotYOiPNqGSOJORNVPyZMCQILba7PfJsthC4cZEVvDbAqEjZSCh4olZEp3Ai
4iTshPqqf44snME5Fo9tELAzhnSgLr57PFhCsw+eho7QyYqZ8HjogrPbGzrhXPcq/XYLpe1z0xQ7
Ok2hqNV+oMqH/Poc0jzPS1MgkaXTFDpNAVWh0xRzxcDvU1CTeRPbtjA9CuWzijjagKPLAeyuZcMw
ODggn1+6/Hd18qnHn4NPJDx5pA8/GgyPtzDBoDWCtlQbQ5zqIZ18Q5EDtb2Fb6HdkQkWYzqy8rww
vlPz9sX6yes0Rbi15Z23b585L2bTFHty4YUWUiRJsSuPJEILnpQf2CsjQ/C2/r5unLiOQokAdxQP
nP1YMiBSNhGfkPcwq00bkRc5qIWYFGdL5X5WwdWSvheaNdn9alKn1o7bHnG8U0azHEIgEuEAU9DT
tGn3BFJ79OTi94lZHC6+mHvC9CdyvRKzOHxHf66Lwgt5wVWz8h2TQylPXGzpugb78ZJWxGQuEtXd
rAZ4jpuC22S1g+P/vjsEBBghDmSO//5CVtTfVrWyg7SzdlHm2qaaWlyi5qV5bpsPwMzT9gdhx6OR
pjX++NWzOrRv9vAbBOZYVKA8391ljII8NTwjoLT9tCFOHw08ebW5Kz3wLoTiZWd/gcivWT9knCe6
F/U9QZu/VbkHQXuuGGgXRVOLayRVEZBUzEs266IoRufQSoq4KCHXM2kDpRrGAJv0HZqVznzYwT65
KCGrt3ZTQic3o3G0JKNsjptC2RZrgFZUyJe0R6ohWtR3wd+UnyfPBZkXcmckV61pUHJJFf3Dro70
ZaPMixmUjbqspLHFnUA+qWv0BEpvTVvWjBH4hExxWdtAXivzD8lcTvSydCKnnFzb7VkC6Sm6H/7G
lGsE5HzJm+B8Ep+PWgo0ueTvyAXHW9LUjmAV8I6OhJ2QW/r81fXXzfkJ8dD9zxQ4MCZe8T4I6O/i
IfZ2Ky8/XuSzhnnSDa45U1vSkH8gTZO63CjFOllwIY6ljeaqIrgXKEkkSWUYSyi9gLWQtPIiRHKW
j+GFpNpAzpXW4CbKGS30OowXM0ZToeDdJroOJ1DVnXQXttm+5dzsVMpUFbJxulXWZdJ9Wm2Ehilx
PKlnQw0lbhfp2XuXb0OlYX2oCvVtcqHSwrMcOSAs8/BugQoDZSMi3R267N3IJt3QIlAa1jhhfgjv
g2I5IMdYK9HQdbzkOeIlkU5sBMPmZDxQfMKXKiPBetDN2JwXldQFfbuOmMx1lTN64tgpdDM2HTHR
Sd0Zp3PWHk13Q7NEr8/5H+1giH6xh4vfCkyTRPAcuG3KwMOTCFzvgToTsmscDdtFCMamXWZ19zqp
Gz7ieA7xInfN2A5SmrGplnCzNg8+wNGPmKcV4oLTRTVDxOSAIiY3hIBkoyvm2ZHMkhxmxHFoAOPM
Wg9nMpohPIiwLcQtXiZVSOrEh49IVbLIdOgk4cx0JC6fZet+yvSFiKl58ZR5SULU32iTV5u82P81
jnGuGOgkoU4S6iRhzpKEidvsE63UKuxUBgMGaL30mMGKMAcDDSJoiVCLHBCVEQIh3Hh+2GZgxTgu
0gDbNBUVMZSiyoUmUx3q4wGUwCXTmDrNJ5076XWfeLjlBoE7mPN5T6Eukq9PsIpYNAevLl33Fhfk
pE5lu84j7VqeH9y4dBEauG2qV5ODAI+MBk7kePiG9FLcizeod1V1mvHtSN7DfERKrbqjCDViQJW9
WoXflpdYElJFPo/HZpG+cj4gJSIijIZnP+pJGPeI975CevCUwMAfYgXdPPyvoaTVlHPqfz0BJaeU
PvkenvRU8CPRIYowsSDDuL1bU+DmRD2yBHO9xfPZOvH5d2rKbZERQqSOKT1KNz+dHg3HPAFAHIQg
LfhzJI0KFsU6axoclSiLK6rE0FIqddmqBG9ponYCPtxbJDnRj/C0vGn8+1//Lxa4QSQxTLwbHlMX
eW87DEyejjBymFEN+gcz9+kbO5RBUo570XVF+eMI0cIvU0OdoSYCm4htpzEl5XWQn33XyTQwaJGE
WGBOh5VcrmBciY5lGk3IKCNk3pl3ZqPtWcPA+ND6TJjp964EDxivCHLwOvZgoDDH0s3iG5XhMCa6
hF1iaYt189//+l8De8P3b7Q7bBrvRvbD929go9o1XsVGFhnYZNkyuK6Qy/ZTMza6ws3b6/L0/U+2
a9q1eZd4IrZaW6xyr83busX8Kjs9tN5iIXzuKC8Rr2z0bc9DtC5BF63UYt3ez2Cxhs7aZAlM7Fbl
AIZwfm2x+sZ7cW/cuGj/wmnd+gJAqkWso4mU5t5ifQdWla4PI2fTaGS1WBkaVsitDxbrGzDOVHc3
+fdWDSw3AFfSe7vbxinY1Y0zMNURD81M+WxxjZvt/U3jQztwW8LLbt+AaJP8hCnkQ9Smy6lte9zU
Bg5N0/ziMW3gFNLAYQLIiYFzsK2gKavaZ1Zp4ODmMxg42+RV04aqQ3JjNvMcBY4Xi/LkzZ2g8HCj
j4qm6RZPycNKjvHkcVCbxk1Wa67K+acibvRviejIEcGksvBX2/V9lLFtGlgi1FvMmGHILKwZB3W5
adRHvZEfsBW3lyVKVeUcThEnV1txvKdrKw5eSGofgYImViNUmQhT7VTAZM4pzwJacXTzGay4COEn
hWh1YjVCeAQBXzhXt5QkSIHCVBfuyLcF9vXsZg3Hgou488nmC2jkMkRBL3JysGjQN6HxgMLdL8Yr
FAK/hhmAols0SGijQWmndIZWkzbaunZKHME6oYao4MWnPN50pqSo1g+pmU2kH+/EIIxiZbN/2GEu
ohRo+0fbP4/2USqo/RPhziT7B9QVxbV/Eng3wtRkBFjG5J86ihUju81RFGtVhvdSzDQKUv2A/cNO
RhF3vsftnzWwahrN0+/f9iowaAmARCoQCVgxDCb2zUGm+A6r0iLOsrZvtH2zrvZNhGsYy3u3GiLx
V7XNrDBLRzefIb4TYUvW8Z0lAMuWYjgUKL7TMC0nKNWdjic2jevMqavCYufPqNGhb7VsoQI83DML
UKRrpmgDGdy154J9BPzBrz5dXV+/PgRrprc24RzSKpsGOpO0+5TLqlYz2Toacu0Hdd8yjzaa1gB8
eM8DZiT3Q0Ou32xtEKhKFwmim1AMch0hGSZbZ69SXMg13XwGW4cHqGM5eY3lJEN30urO8gje+Q3c
p8KOBTmgeTzX7Z55HrKFsvady+kKg0hKrjiToPNMIy3SBMKIu7M6VqZx6RnM4xJsgH94wBTZvZcx
i1fwuTKNtEjr8KM7cjrrCe2kspU/y8afptPLWGdeLWzZTn04tAnqADxn6dJ8ANt40zOJjdz4MAys
gfWVDxmv6pfND6/BQTPpURCTaJhsRYU/kGU6lR+o1rL4zIg86ioe7TNrYp3njZlMIq8hFiDmM0e4
9dlnLnAVz+5epiqeSG8APBuN/7Q0/jPGSHV/mM5SxfgH0+sEC5Dq1Apb1EKsOh8I32nUyhUGerpe
aOGce2ijcu96t+tj11BRS6Q2OaNVo6tadCaA9hGFfwz3kyyEF5oucCPKhP1jtBZJVk0V5NrwNcbF
ybtgrSssrJNu/vFUAA1ZVyfP6R6n61oesWveocUfehlelZmH5LRsXEhDJxNzYK2wJS6ZjJxD440w
PYr2uLfoivc7lcGsj+GzAwDE4oaPLmfRho82fJ4bAjM/nFOtRDrHfNw6KZ/clL4M7I5v9UptgLZq
JSCc6H9MZQLq5SiJ0hKTX6tCgc4dUhYjKdIlRwd/NDgUJhH8BCbDD4HRc4M/ydCBMxDm2+Yt4KLE
tByzC9LAEkVKXd4Is2fHzZ20YRUeQfBuHSfwT2uUSSgLP3u/YfYa6Mq+pgsRJfWB+TJmknD3F2hL
0u5vGuf4+8R00PZSYrQIb9Cc6rydppAKpWdd8CvYwluvGT7OiAmpFbZI9NPVpdGweo4ZjLwxOQYJ
Keom0KTcp3qKMQdYuRKbXhihBQSCfHQ9u2N8tDrC+ChaKAdxfNcLrNHAOLn5/i3V5wCvvemMwInG
hRbZQCOFLSq9aF5dFnuqdaWFrrSYtJqNokaqlUg/polPjvbAHGWoyijDVrWgXGLzRpQlyKBbNyGy
tMRo0gurQNVBBlhFHJlc00KTtQwy3Kyr99KE+0nW/DkyosojzZYSLWxFODk06D3hPQDSDt5iRfeX
4tFUy9Vim7nceyuLRzNr3kTrxrO5M4WtG9fujER0aRJkJEzWjAS5ij7DY7gYGf83ZyeUNi1VDw4K
WkI+PYosbovu36Xdlh/FYwIAm+y2vPFMUCWTDXVturaFEKAyp07WMILfGAoPnMBrVqd7XLpq/9+R
EE7WSH5hqzujVEggFxkNjUsUtY6I8xrUR5evjep6hO+3wPMY3eOQYxMtT0bmac/TXU01xc5hMrA+
0vULqR/Jj1pMaP349rPYRrr1V65to+RAYZGS/w1bgKglFklJwzQUBqZzTD0ywmqCU7NvswHBGWOK
LbncV+LBqF+/5RhMNDm89fgWRPjNls1MaHDe0GKrc3OEeqKTNzvb24wl4LdORdcc2UHkyIq50+YG
CJ6TJN+G6RKCG4WjioP4BvDkFHlcso6P9ATyuu2yJ7rCQ/BL+IobP/wUBBFfYHWONqqVSFcdXD3b
hJzXt3a2a6smsyvUhKwKkJ2aQkuXEkyj1Q6O//vu0BPtwKBp/vsL+Yd/W5huyIgfPNjiaOPe6gT9
w8p/9YXV6weH5b2dYbBhuId9z7SBijnaaKMDjPDkW36Ay6jD/EfXsm2+uaON/zAr9B9d2EOZDU7s
hiVtfCMyK0TCS0tYrX38UqWWLRtCDcGzRTc499xBU3wJjjaUKqBbm37zTnhB3Wn3XXA/BziZYkC4
3PAT3Lj20YZHnwnf+1O+p4bCHbJw6kd84p6+g8sNJRda54sp7SEcPxG23RiabUIA8ZlVXlrJJ4KC
lMZFty9PTroo31TaYakR6UvVtXALl657i/MZ4lzZrvM1u0hjBDcu7pyrBWzAl/nV5OCJa48GmLrx
8fANPsVxL94gGwCdymEz9w/5irH1/AhPhd/2LJk9UN9tmw/uKFDzifsaT9qvntWhcffwG98ix7a7
G+bQcWp4RkCzO63nWRSUWp270gPvggU0fBg1AM7CecwyT/Rw59f4JouB3yclyc+/baOIjB6ZEnhz
FLj0ktbA0cbBAS0ueU93dVo648/JBcR3+6Sa4ZUrXNyxbTlQCvR01YubEWkJM7ikCkw5vM/tpKGt
enM8539KBKc2wjEIDzdmhjrBbdMYpjsa4K2xEKI0d1+BhFLu/sp1zDbPcpYCVHU2z3RL/jzx+TeL
TPjUJiMhsorw3UwVDMffvzU/wP2PWZqQ7fEDmOpwzGIv+x0vZGxFnoyyNYbxJu3CpNb2CiE0d+VO
P9n0B8lPKn1Hw1jUvSRusz98XWiG44Nyrfz921un63oDcIDdCZB/hWbT9LNO27/C7eQgup8M22rR
/OB+ErhkjZGuT9p7JrtN4uGWGwTuYM7nI/tRwgVIeOQu+PM2JHkP87eb2s6+2gziu9DeXlgvtrxt
KJtVwMtO3bTqUBm+UlLCe6+0JHgfYdl/0u4wu2T9se3SEhBsqHH+VvkCxDCuOkG9z2nB6N9Tp/At
Tq/m/BWhhe5NHPEYaRR2Ur+W+1iiGlnCgOaofrIRQithUdX/F248S7BLdwjTwa5+HT0hjjZQt9Ax
HeXRxGyQpwjiG2wrCCnYa0YsjXhXXca7zsqGotMAVOzEHQwAo6qjtCcgTxBlIbKdxh2wUxz5ipAv
VHYej3yRJ4I9eWyFqpBXdldI70FSc+cXo5y8B0WaOb0tnZYtEXRLph24JcS/WaSKuS29LcUsZFjp
XhLB/DOE81e08cqpyjTIlQf3VzTEuBxmsTJ0ny5tZazUykAMbbBmGbVkjJVsRZ9JvTyDDl2alXgt
HMfNNKqVK82ljUlOFUHpF2PM32LHezoUSRZf6E/Ho2sPQKIhEnurDIIlGjqLOp3EhD82eWOziRhH
JOqIkUSHs8Q7Xt7k/ftf/2t0wPcflGZNr1J113hFhLiG5RgwYHronue/pgoBWe68lYUjf6u4XMGf
msWeXF3trKud06qdI43lJn4XHC6z5EU6fGjnaxIvQngiPZ2Cg0mG34o8k5fgfMVU7/r5zyattUxj
XLkluCIhjSmSLN6z7vyYa+8577ZssiPZaPdH9lfPchxwGV6gUCfTmiuST/ne9Tzx4Gca18p1yfIc
E6OBybpxfarReYM/ycG8KBtN8Ke5XeFYWRuzbRW2m0W01RrqzYQ3sBwwAfYeZO1+2K3EQBrbOPti
9QCpAm/VYDByVDu3uEwU3zedMU9LFbigiQ5q2Po8Uwn7VnGZ3rWLShGWuVirjCAjDU/JG+93pI/b
2EX9jA2h9NlHq8p70UKCpof2TUF/4GtHVTuq9zAXBqbDANcEqMeq3JxMhtczGJQrGh+tuExDXLlt
uaIBrnumnrTlek9gfCvIEmrQDTN1qOEpaL9xY6mM/BFb20llF9HkYF5zne8aH94zI3J9bGsZr959
rL+OqZTC+5ZpdmWpWk3xMBdJgXKZQhEz3c2C+5fJMcGZIOA4Z294XPvrve1sFZal+/r0vNhrU6et
ddo6JW1dleW56NN8tJESE0BVv2L51DEBHRPQMQGER1tJBbdPMX91TMAfEg9CYHqqknVVydEVxTxe
RkxgshVkiAlga0ExJxwZlDJTLkCVqJKPFrSzFKquiOBAl7DKh7+qFba0jHUkJnADshD0EzI3jTOV
uX5HTOt2B5SEyGNnDRoUlm19HDQ4GxtjFDQ4W+ugwUTbLCdoUFhe9RccNCgsTawOGvD+ooEEADKv
GxV+NdJAPCVocCsedLRARwt0tEBHC/AEFq0H1AiCow0OiBQWAkIIAuwBWcIEIX2WDhOQqeC3rQil
zo+USC3F/6awTfHCBJl6rm0Xtkx6HAX4TTyQ+//bWrv/UB9L8fu3db20H9T95wYjI8r742ABMH5T
AajlB673QBTDjOwpArxH+/3a7wdXOO8xa+f386p05oEFfFBSm8HIE9r7196/9v6196+9/zANrkiY
guOXgRUY7wRZYgBhJwcdA9AxALLyFw0YRqACaCbasQX6iYZNRN+XjYZ5aw1GHuAD2SIEhS1fHkcI
GqEdRnGCxlrHCcaKZjnRgsIWlrxclIDs36SjBebRRtMaCN94Lx4xvZcSI0aE51iXFujSgrTSAt5F
p6IFLvqQ9Cd8AwF6uHHbwdUxe64I8PuXJiQHf2zR05RSHGPVXevHjPcy/E1WJVl8TW4npmHpTuBr
XzMHvmZhy2LHvmaTNnHyM5tr5mcmGSulyv7T69e3C1uI8IKdzMKWD+iUtE5Jr21KmsN1yU7mfVBq
CdNDW3HZVDIKH1li6wjtYKqG1IsG7V8C6frLcDDvg0wudGHRzFKNZHEut0nXaOdSO5c/qBMjicwT
czBsgRRhwtZ9UjauXPQHHaDNctZUZmELKJPcS+oR1bVswQzdH9A5um/UyhXjxLaIqpte47fi6mZO
b3oLhLZf0W0d3VV/Ra14sGYc3spHHds6pcpOin8aMnhnajIlu8sXMaX2cj3UncIC3bWHqj3UtfVQ
masy0UP1zYFdK7iPqjpMy20oOqAs1vKOtpYPvSWGIpYC6yhQ6V/cRI7YxieKJeiqbCiLOhPwb6ew
ZUeN+tUl28LaQt6c6sA6q5rS27AuZiMXFib6gm3kwsI7tY2sbeS1tZEZBDGxkQeWbQuv9GUwHJZE
rbC1hKflqYFksYl3tU2sbWLmEiZBWLwU5orXzqZxBRN41ujtCBuoL6uDmvoqg1AIj+tCr1xZt4Jq
7jtmAFRnrVLdKlV2S9X9ZnXncHvvsFL5xwbnT1eURF2K53J/2LU7J33TwzjUX00GqbZEz2KYMXwb
3kXkD0VwkjcHDJMg7LeOH3hN8SWFRMG4+PP67Oby7fvfjI1+EAwPf/klcF3bL1si6JZdr/dLPxjY
v3Q81KCXprQQQsQb3LU1+jWctSrCs0mZYl8MTQ+yq7Tn7Ejy2Q8GU0CTfIzUaClwS/hlfGh9Fu3A
iDC9Uj9SpDbQkzQQjm+1kAC5Er5vQqh7nOa49gTaurYF5UfQ09O1jVefrq6vGY4XfgNlJWefSv5k
P2V+hdOZTC2GgmGRKrIcQrFKfcYALa3PchdQ4llanTKD7UiyDUmQ36E12ZKA3YvieVanw4Kiz+m0
9oKwFsCaCo4jsbRpI2IK8QN9PFbEjDlYL0Uc7qKVHRp3+ErtqYnbUU1SAK2VeR0cV3Zj8y71bhFE
OZmLLBEqERshT3Yo2TXOsK+nZJ+jlcLI9B4yyzfnStbrWQTHVyY/gPGGUxwBP/7+jbx249Uc8eWE
xXpNWYq78CI8/vv7+4m/bzmB8BwRlNjn91Nd/3LwJdDu/1B4tuXcyhDbMj2mxYzm0JBQCbnwJS3h
tfbVa5yG05pomZK3pBDq2I9OsZhmA48/ooZ2J2po/IVFd/IKGoIMjqfhAKHyyW18PGXTj3nZuR9E
SmR/ppey3AiKNhdFM8DGWiiz2lsg36JDlLmwtoLji+bV5ZR/VMzlFVN1BXJSNV+Y5gtL4QurRYHy
zd/Ln3YPKuXqwQGXVK5uN28xymLpHZ3/ehsdQgbgD4avS0dz5w9BtRalD85bDgBxpaNpG01hi7Y7
GIwcVQ/pG787KIJkUNBbB5CCgSyKbIp233Ftt/dglIx64325agBK4HYIW+CNbOEfGo2haFvdsK7S
7RpvTN9qE0JBnnZDpxmv3pzdvN40TkzHpe+0Z46f4DjDFU7R1wOXH1l+X3RmTjulyxCGGyuo1Pz+
7YbHgQ1P3u+nMvTCpkGKoRzbymmq2IWkTtN4EfDOHhAYyPOtzg2aMlRO3uxsgy2UEhaB4uPWHSrx
gNatU0UtAij9UG+8bZSpNKmEHtKihIrhkuuryB+nrpbvW61qU0keS5bdJaew0vP61g6a/dA0KD3r
D8026R5YCQJaCmBETqTKF/VR4KoToj1Won9PncK7u1rqOd5d+sApso9keIxm8t52dtgemi7Bjmqz
SCf7cIT5RLkFx9gV0Mpp02jM6OzxyHkpPjK8/MHVskZxxsOMTDArqTWZ4N/EYEic+9Nb8njcL296
E0n+HhHwvK7f675lD90g2DRuXswUmwDjxsQZHekS1HQiL2BBp/kMDDMmSm9iw4YtPR53QVfxcVIt
xHhQEZWcSJdT0Mms+74AW5ALiDSJ8hgbHsLJ2Zg0GqI98qzgwRifDhHwbkdD49KEj2b2hPGKqotf
G3/Acl4/wSBPUz2JAI/J9Drfv007C6imMVVpcGVnRv9pr/Pl2est170dYJk0AtMLoB+4AqHGO74s
Y/wwFM7b07Ks0xBFdTfjg8jiZ+7pKKYuX3xC+eKkVdd7FDDGmnlFuPE6VAHVEZbn+pIeL4H7A7bM
OxN9wGaLIBM2/t3CNgWXisY4cR2HysZChWNUH9us2ZRbfuhrSTCkNL+atuuYERIHaK9hDVgIClTQ
5PAlPQREuPET79BcAsEw3ojWsAIjOH43ckRs6jF2DJrlOOfCrMDZ2nTc0qHeRNNxi/cfaTpeC893
HbOYGQp18xlMRQxZJ7xznJLA5oIdJr8GwvGV+xVcF1mbuu4Wlh1VjdNQS2t6Cxxbs4XYCDmzXx96
li3rlfSWqLfEw+QtkRes3BJvzk9qu1XOYRcPCaZuPsuWWM3nlqiz9HIbHKvaScZgN5EytKAZg3NL
2AT8eklZvth2Gsl0RaY4keezoFP8qwiCBwTNdKY+MsGJpKAFneArtzdCzxA9v5H5XSck1bn34AcP
t5vGxYzpPN6e2BN4RH7XCkq1u05QqiugqwnLvWlc6ikewyF31wlOdSnMdn/TuH4x85sNS7W7Tliq
Ztl4Q4wcnl+6FDOJi6Lr6qyIqt11QlRdEPwvIFLWJlqJ+V3hTVBVpZJx0Wxe/1ItV2MuxVqg5yjr
ijAGQnaIwsC4RCbu+zeU4BzM0A2N5Xpifu0l5tYfMU/yCoSd5kpYg+lNrnif4SFImtnEmHpBZ/a6
sW7r9gkTu05RrUc7ZzwisGvlKe2tUzBrhs7hZWvjdQpjfZoi6liDmT3W5Bea/CKF/GKLN9xJsnO/
ul9M/A8lO3HzWZKdtXwmOyNVtS+6JDn3+J8b4aOgnwBAZ4CKZ4J57yVmAqJAp7z6nRRbMD7cIeLQ
vHzEUYkOJ4e2qySVl9EEaIpN1FY9EBaoUskUTEiM9EeHnNcZfDRyEB1EHudNmy/afEkzX9irHJsv
W7UK14EVEqtFN5/FfNnS5ouudHtCpduF2+0OTIeygFmtl8QUaHTbyOve17iC9dIQ3p2FJmWqjZnr
GFSJzvXnwuAzXLZvKLUydFFWe2k+wN4JC9TnR2ejTyGPmyfjntnoIf2yaYTtNtjyqWWyfBKTo9Fx
53X2teXDvpRmmkOgfd2Y5rY46DqxfA5qbBcU0/LBzWexfJiRFQHZCfEF6BRBukg/JVA6aH/EXN8r
XraAm7Ci24MrY1p3ddvqOTjhzrSPNtqCwE7ySN/qCGIfkYVh4dWG0QSNonAM3zoVXXNkB/imikap
p6LU99YJhdEwAY8r1Z2OJ9YRQpUVWbO/TrCKs0n/2wZ0AxHKEGRsyb1wo229xnAGtqBCdUJ6JBIA
znP5Y8SihN7eND60A7clPDYot7MYlPvrhN541MYs3gz/OHxjf53gGzrJ79xOwHT764Tf0El+zUq+
nnzOyRXNkQ4XCAVtb1W43reQviLdfBZfUXe1wPTmLSBJvrsi9ojGD/N2m4gnJNtAvyFkQFzi7CP8
Vp4mBBt6rts986jzgww9+ENh20zVKMMMuYc2NIQbC3djvhLHBLepICPKmOLYT8QwRoU0r0HuME1h
1MEUawXg4ht5gjMcQV8YsjmLCMb1IrHpnQE3Rgecw1UZgXDQPrBpnIq2GITO504m57OwSJxHPc28
T57GcWgcRxqOI9I3BxbqTm27uJw7dPNZLNScdsaJRCE1DDXPcdhTS3i3YFRBvS+FrEE7PAGmZgKl
7hcX0gjLhithE+AaxisAVV+P7R3jDxRCoxcBeIlr62L7kIbZNOqj3sgPOOy+n8nyKSyKR1s+Gsfh
Fb/XWnJsLtK7gSyfrRqXpxQyNkc3n8XyyWmvBo3jSMVx7CdiAB9JbeY1YgIzCY1iwWRFANizztpx
4WQGcqwTOGcc6FKNKIxz7jQ83+R7RIDzHQEjbRtHX2QyAw/WCb7zqGVYvBlOzjxkYUU5WCdcjUZf
RNEXB+sErNHoC42+eEnoC7adx0j9nb2d4qIv6OazeHhMIpE/pL6ObUsPLzmpXySgwo058NF/zI7Z
9+uAVngjo/nAmDRHROKZEb9wkAjPjGaE8+qNyzrMX65QTGMNR97Q9SOohSvTsid1mz46Av9y9fbq
DD2BVVR/q1wLWw8ajaFoW12rbVLv4ZhgFBjnQBoXxJemMzI9pquoZqKrOCgsnuVRly4q1Hn00DXM
QcMc0mAOHHGTpuDHRukcrWQ91larBdO1UNaIOzrx+feyGqUe/xUbQhaz8IDGqc1CJ6COqabftqyj
DexkHRNdF/GOMP2g7lvm0UbTGgjfeC/ujRsXXA10sF93/Mjpy5tKmo91MQt/M23hxbb+dbAJT5Cn
uGojwu36IO+/wqtfXbfDxiG9IPRHvWy8NzumbTlZDcbC4iA/ilZI6eGDziJUoWDtcHojsyeMVzG9
NLEV1wMBErKWHczkrSZl8VjSASAD9KvFPZozVrKrGnfaLZRK8Idmm4pisX0IsKYIlYWXL+qorFcn
RLPz0b+nTmGtNZeP4jkRVzYkBiNjNgDhqL2Jb2CiExOT9tuRrrlm+7bki7bcwcOzgY/Hha3O0UYV
5443PTxWvA08UicaAQzfenZKgUJNxLPXTqRLB6bRaqOm++7QA9zeoGn++wsxMv1tVSs7QNX5wYON
pXJvdYL+YeW/+sLq9YPD8t7OMNgw3MO+B0Xdc8YUFPyWH+Ay6jD/0bVsm221o43/MCv0H13Yc28F
TuyGQsU3AnGVyx0qYLzmsfTlto4/sJohZbboBueeO2iik8TRxjbvAB7d2vSboEMK6k677wJ1Q20n
yP6gq3wiF/togz8TvvenfC/KpoFTFQ3H9g6vFFkN0/miekvj+AkVxox1Cwg7qnw3ySeCmYPGRbeP
G4mze4wvyjeVdlhqQvpSdS3cwqXr3uJ8Xv2V7TrfaNfy/ODGpfuh8dkwyPjV5OCJa48GmLrx8fAN
PsVxL95gO1Ya0HH/kK9UwBdfegruUM8aUoQi/G7bfHBHgZpPnDKetF89q0Pj7uE3vkWObReNH6U+
wanhGQHN7rRaYVFQ6nTuSg+8CxbQ8IZqNS6e4ynPMk/0cNX3pLCxJIuB3yclKblYbGF69MSVwDNn
C17SGjjaODigxUXDxukF5XDBYGCcQSnQ01UvbkakJcwAXZl8FoD7w89tHJuhp1n1pnjO/5RcTW2A
Y74K3JgZ6gS3TWPoW37geg+0GGhqYkIYCbWn3P0Ves23XbpOFr9Hnc0y0JI/k/zZyUjuD/2v4bOs
KeHxv56Q58XPV75HmlMtuOPv35of0Gom5j7g+PgBTLmuLPY/YGRFnkzod8Vjs8KkXqiKzmnuyp1+
sukPkp9Y+o6Gsah7CS0YTgbgWUkbhrWdjFt43XYZ9g5psHJdrsnwM1GrR6m8mUxDzzMHjyUafngY
UETH9eFQOB3rC1yi2ExihN5UeSbdy/xKxifdyfdvRr1967j3tuj0xAC1o37sjuih07rJaBM+Jjfv
CfBkwzuSk7KQ4MzGIhYKN2QRrIz225K+F5KQDKRp9k3n1jcCF/TPQWBcYYMB1yMRQnYsvz3yqVbA
Nzxhm4Ho0Gmfrq6vDUhUKXBL+GVA9keeFTwYAxcJKOl909WsW2G8cx2EbehibVwFnGIyuhe73vjz
ASw5fBV575+uLsfXReIncoverfHRDHzFWRkTnxSBfmxxrWyqafF5poUekr0s9zl/4a3yLpMFw6By
WUdg0mn+PDH0hI8lS86v/zAYiMCz2sateJAz1rKgY4gsKsD7rVGAaYcQ4BKDqarwBRe59sDVhvzY
jhTpW0FmyHwXPDSZF1G3z4MGf6KWTt+fsHUvSZVOZiKjCn+Om4Lym+OCo6ZCu+DaBcca0C74XDHQ
Lrh2wbULTj5Y7l3wSKeLqAv+Jt0FVxGERLf3MS8hfQ9/JJIQc8Hf5MAFP3XbI/K9jQsZrYr5Jgta
59oFl9FyCseqkFq660+S8FfsaefRY/0LfluWm8ydu9oScFIH6FzRMVoP7LyifNgQHQshWUPmZ43h
qGUrPKRhkuNKzbSN//mfOHHZz18EFuIgYaiRgYuI/3PyiaIqFCHuIBqD0HmlulWq7Jaq+83qzuH2
3mGl8g+p/uYw3f0sL2hJ30urqDQloNHHxcmEBR4XB+r5hwx7r/7JYQTJEZfK1owcYmRhlB3KAhM/
ndQK34rkymeVsjMayMFZ9h2lzaTSkpKCY2/HaacqR6kh/5NPcOKeMo3IaqA3HAkfZxaRLwXxOW9+
WXz26BQxzcoCU8RfMmde0vdm3OySxG7i9EdHwlwFC4xkAWF7jkGlSuIZa03LtDka2zXBoYe/0eSR
8vsUEJ4N6i1HUuNmZ84j+FFJ4Jqm1UjCkiR4VnFCpnnWsKJzogBrMwpwkQilUnxKJV4DdJDQimSi
2R7ThWGQdPKJqC7clW0flC482F1AF+ZGlWWc9p+qim5EV3jCaVPyCQmJdx8bqP74eEY/fpPJpncf
6waIZSelLr4xMG8pGUEf2PCBLMKH3dZnwiYhlzEwg41NYwPX9B6GlNSaOYSsxuREykeZds9Fjqs/
oMyVT5U5uHoXyCH6CtTnjPD/tukj6YE8V9sTgZhVkFqSfxC7ne5RTTblIkhyvdOBsG3ciH+OLHgq
lP42kMdEfn7sk1x7buAC8uMjXq8gBVojLqsGYF3k6A1BHlk/IVHfHwHgvdEIc/DNSQ69zi6j9VXW
0xi/Q0WdQEWFgmWgd5M780lSjB/ok/iDFN/GBE++MXOJBCtQK7kXruROwLjdMa7cr8CRmMY1qlKB
auNYi0FACFuUaD8uQe+9ajQ+vAaUwA/EABso7ajvPjYlmuDdh8aZgRiHqbZhLWnPYYMVazsFzNoG
glT2JyPk2sAkmNEcF/UHlBP5RYmgxJy7phntoeW5lskRrVKlmif7hRNAkHLt0QFfvZzCynSjKjW4
JO1g9s0aAGjaaFpA7ahh84Zu1DJkRq/cjDmptJVbWcYsLCsWs02RZr1ys5UGhBXUHDfnAhJMw2KJ
ymShOPGERAEjrmI5VkAB4rdnzXOj46GdtNGCe9ExRkMYd/xGqWWCscUvfQaFSQlru8QhEtoT7hFL
MXx3IAyzg1BzckR5ke1aw0QzwkQjhAuEmpARa1/mcZLKFiIMBZkTUBopOjMZGe2x57DyMY1zkKLI
Y2ik6FyIIMoMsxQBwvyRJ+piTV2sGYKDdLEmLJHZUpanqb1JiSMMRF2sSXleMpWx5eDnyyrWTNxm
06WLDeS5HuyxjKL/p2/Aa0XqL7lgEZqe3E38Gteqh1vIQbTgf9hWVc1JewhDa9a53h/SGH1CYa1+
rJp/u7bDzTCmivx3KpXQEMUlwk8+sco/YR+fnQO66bAgus2T3FZz3FZTHPkMrGlXmtIrUvSz0C5F
NwO1ujw+mukq6mUrbEbLjivQQ9/08Zp0zIWKxSau87zcJing2ap5eLMkS0qGtCTlhOIt95J0Y7X7
ptcx3nAshWUosr1PpIoVFYtVjHYiEhgJ9dhcuGa2nUlrxeWbsVor6v01L8SXudeKb968N5qi3Xdc
2+1ZIsksV7ut1ou0KSi7SVuLz4K9XZxoKX1fn9iM2u/IRIyVLfu1yBRBhRTF76huVSrGe6O6h/xa
I0iXKq0VtVakJ5BXV1/70ESZKQvfpN7P3cZVIK1Y9wgoGLjgAv+jbtRqtcqBVo2Iu3Ex6dzKUW0w
5m7dadWoVaOkBQ4j5z8aOSJJ+r2hNeFP04TgTMR3y+L6cQXphPFY0oqvygho8YWX2gRn9SbBCm6a
VsHZAH3VDnOftHkeYF1efYKJdI1BDYbHfMze284Bk0osSMAd57h6GAqyE2+V2b3EVmqLBBtIHD27
9X+s4V3Z/zKtnMcj5xzQTPaH3PqEBifxwvibZ7f45macpsVtLlwDA+TzQ1mg3+THUrUst3QY86NE
U+W9BjGfUxODWk22Kunj75192YoEl+gBpIczAneI97flKaqyP3zZcoPAHUwOK0oUdXIfHOUCzSH2
kMXGhbquG0Re9kYBv1QeHRX44iSyrUHiQx9hVdxx24RswBEixr+2gjbucksSC2Cccog87y2388B/
4CPM5XX8/wUAAAD//wMAUEsDBBQABgAIAAAAIQAw3UMpqAYAAKQbAAAVAAAAd29yZC90aGVtZS90
aGVtZTEueG1s7FlPb9s2FL8P2HcgdG9jJ3YaB3WK2LGbLU0bxG6HHmmJlthQokDSSX0b2uOAAcO6
YYcV2G2HYVuBFtil+zTZOmwd0K+wR1KSxVhekjbYiq0+JBL54/v/Hh+pq9fuxwwdEiEpT9pe/XLN
QyTxeUCTsO3dHvYvrXlIKpwEmPGEtL0pkd61jfffu4rXVURigmB9Itdx24uUSteXlqQPw1he5ilJ
YG7MRYwVvIpwKRD4COjGbGm5VltdijFNPJTgGMjeGo+pT9BQk/Q2cuI9Bq+JknrAZ2KgSRNnhcEG
B3WNkFPZZQIdYtb2gE/Aj4bkvvIQw1LBRNurmZ+3tHF1Ca9ni5hasLa0rm9+2bpsQXCwbHiKcFQw
rfcbrStbBX0DYGoe1+v1ur16Qc8AsO+DplaWMs1Gf63eyWmWQPZxnna31qw1XHyJ/sqczK1Op9Ns
ZbJYogZkHxtz+LXaamNz2cEbkMU35/CNzma3u+rgDcjiV+fw/Sut1YaLN6CI0eRgDq0d2u9n1AvI
mLPtSvgawNdqGXyGgmgookuzGPNELYq1GN/jog8ADWRY0QSpaUrG2Ico7uJ4JCjWDPA6waUZO+TL
uSHNC0lf0FS1vQ9TDBkxo/fq+fevnj9Fxw+eHT/46fjhw+MHP1pCzqptnITlVS+//ezPxx+jP55+
8/LRF9V4Wcb/+sMnv/z8eTUQ0mcmzosvn/z27MmLrz79/btHFfBNgUdl+JDGRKKb5Ajt8xgUM1Zx
JScjcb4VwwjT8orNJJQ4wZpLBf2eihz0zSlmmXccOTrEteAdAeWjCnh9cs8ReBCJiaIVnHei2AHu
cs46XFRaYUfzKpl5OEnCauZiUsbtY3xYxbuLE8e/vUkKdTMPS0fxbkQcMfcYThQOSUIU0nP8gJAK
7e5S6th1l/qCSz5W6C5FHUwrTTKkIyeaZou2aQx+mVbpDP52bLN7B3U4q9J6ixy6SMgKzCqEHxLm
mPE6nigcV5Ec4piVDX4Dq6hKyMFU+GVcTyrwdEgYR72ASFm15pYAfUtO38FQsSrdvsumsYsUih5U
0byBOS8jt/hBN8JxWoUd0CQqYz+QBxCiGO1xVQXf5W6G6HfwA04WuvsOJY67T68Gt2noiDQLED0z
ERW+vE64E7+DKRtjYkoNFHWnVsc0+bvCzShUbsvh4go3lMoXXz+ukPttLdmbsHtV5cz2iUK9CHey
PHe5COjbX5238CTZI5AQ81vUu+L8rjh7//nivCifL74kz6owFGjdi9hG27Td8cKue0wZG6gpIzek
abwl7D1BHwb1OnPiJMUpLI3gUWcyMHBwocBmDRJcfURVNIhwCk173dNEQpmRDiVKuYTDohmupK3x
0Pgre9Rs6kOIrRwSq10e2OEVPZyfNQoyRqrQHGhzRiuawFmZrVzJiIJur8OsroU6M7e6Ec0URYdb
obI2sTmUg8kL1WCwsCY0NQhaIbDyKpz5NWs47GBGAm1366PcLcYLF+kiGeGAZD7Ses/7qG6clMfK
nCJaDxsM+uB4itVK3Fqa7BtwO4uTyuwaC9jl3nsTL+URPPMSUDuZjiwpJydL0FHbazWXmx7ycdr2
xnBOhsc4Ba9L3UdiFsJlk6+EDftTk9lk+cybrVwxNwnqcPVh7T6nsFMHUiHVFpaRDQ0zlYUASzQn
K/9yE8x6UQpUVKOzSbGyBsHwr0kBdnRdS8Zj4quys0sj2nb2NSulfKKIGETBERqxidjH4H4dqqBP
QCVcd5iKoF/gbk5b20y5xTlLuvKNmMHZcczSCGflVqdonskWbgpSIYN5K4kHulXKbpQ7vyom5S9I
lXIY/89U0fsJ3D6sBNoDPlwNC4x0prQ9LlTEoQqlEfX7AhoHUzsgWuB+F6YhqOCC2vwX5FD/tzln
aZi0hkOk2qchEhT2IxUJQvagLJnoO4VYPdu7LEmWETIRVRJXplbsETkkbKhr4Kre2z0UQaibapKV
AYM7GX/ue5ZBo1A3OeV8cypZsffaHPinOx+bzKCUW4dNQ5PbvxCxaA9mu6pdb5bne29ZET0xa7Ma
eVYAs9JW0MrS/jVFOOdWayvWnMbLzVw48OK8xjBYNEQp3CEh/Qf2Pyp8Zr926A11yPehtiL4eKGJ
QdhAVF+yjQfSBdIOjqBxsoM2mDQpa9qsddJWyzfrC+50C74njK0lO4u/z2nsojlz2Tm5eJHGzizs
2NqOLTQ1ePZkisLQOD/IGMeYz2TlL1l8dA8cvQXfDCZMSRNM8J1KYOihByYPIPktR7N04y8AAAD/
/wMAUEsDBBQABgAIAAAAIQBCOE7ipQMAADwIAAARAAAAd29yZC9zZXR0aW5ncy54bWycVdtu2zgQ
fV9g/8HQ8zqSHTtJhThFkjZdd5NtUSXoM0WNZSK8gaSseL9+h6QYNY23CPZJ5JyZw7nr/P2T4JMd
GMuUXGWzoyKbgKSqYbJdZQ/3N9OzbGIdkQ3hSsIq24PN3l/8/tt5X1pwDtXsBCmkLQVdZVvndJnn
lm5BEHukNEgEN8oI4vBq2lwQ89jpKVVCE8dqxpnb5/OiOMkGGrXKOiPLgWIqGDXKqo3zJqXabBiF
4ZMszFvejZYfFO0ESBdezA1w9EFJu2XaJjbxf9kwxG0i2f0qiJ3gSa+fFb/SHMLtlWmeLd7injfQ
RlGwFgskeAxXECafaWaLV0TPqT7CVOfx7dxTofmsCKfRc8tf2R+odqziLasNMbHM2ADeC0HLdSuV
ITXHpupni+wCO2rHoJ/ghyB5D3WWe+E/SgkUajAUK4c9WhQRwAjVpnLEAcJWA+ehaSkHgi/0ZWuI
wHZbZVESyBrYkI67e1JXTun01ul8oJTqayep60Jb/AVGImOwo1tiCHVgKk0oCq+VdEbxRNCov5W7
xp42mPLoXexwH0AAK0n0vfpkWLOW1+hq9MabfTeIwJP7ztw2vD5CDxY+EusuLSPyygB5/NZxsAFv
jeovO6c2zEUHw0BVcSTRLUkEJjY6MYzZnWrA56Uz7FXt/rP23iDUA0uED+V9OQaGS6OxPkJ/+KaU
S7pFcboszq6OYyY8+hbkbDk/O50fsrm+Wi4Wy4PIx5P5u3eHkJvL4+UisKHPg6ei9EP61Vycx9MN
VnEiYnzXRNSGkcmdH2OMVJS1ebxiMuE14BqDH5GqqxM4nUbACsL5DXZKAkJfibJhVn+ATaDld8S0
I++gYQ5KsV0/P3P59gfzyahOx9d67Jy1bFCcnpstFgMfk+6WiSS3XV0lK4mj+APUyebLznjCfExP
Xzrc4ODzc0tkm6oHcvpQeVXsAm4qv+XhjmiNA4EqdTtbZZy1WzfzXePw1uC2D5e6nQ/YPGB481i4
EOojQ+3h4BXiEbWGwyg7TrLjUYa7LOotRtkyyZaj7CTJ8G/Tl9s97hTcGY84Deno5RvFueqh+TMJ
V9krUUxCmOy1pLxrALuhUdSupd9IcUbtlmjAsvuNg3OiyiAYVpCd7Eqc+lUGDXP4j9WsEeTJr7f5
iWcftDnZq8690PWYV9YvpJOGOILmoZIvjMPU/uQLbiWgDLu12ot63GNHMS7OrKtA48pzymBGwgL4
IzCPv/2LfwEAAP//AwBQSwMEFAAGAAgAAAAhAHOiBkoxDwAA43wAAA8AAAB3b3JkL3N0eWxlcy54
bWzsXVtz2zYWft+Z/Q8cPe0+pLYulmxP3U6ixJvMJG1aO9tnioIsNhSpJak4zq/vwQEIXkCIByKk
urvrB9sCQXw4F3znEBfq+x+/biLvC0uzMIlvBsPvzgcei4NkGcYPN4NP97cvLgdelvvx0o+SmN0M
nlg2+PGHv//t+8frLH+KWOZBA3F2vQluBus8316fnWXBmm387Ltky2K4uErSjZ/Dx/ThbOOnn3fb
F0Gy2fp5uAijMH86G52fTweymZTSSrJahQF7nQS7DYtzvP8sZRG0mMTZOtxmRWuPlNYek3S5TZOA
ZRkIvYlEexs/jFUzw4nW0CYM0iRLVvl3IMyZ6NEZbwpuH57jf5to4G2C63cPcZL6iwiU9zicDH4A
zS2T4DVb+bsoz/jH9GMqP8pP+Oc2ifPMe7z2syAMbwb34QaU/RN79H5NNj707fGa+Vn+Mgv91ovr
l3HWfluQ6TecccjIjx+g2S9+dDNg8YtPd3UQVbQIl9Cyn764ezmAG89QguJvRZKtkkvUaogNBgPz
3QkvAqWw1fsk+MyWdzlcuBmAJ2Lhp3cf0zBJwVNuBldXsvCObcK34XLJuNMWFeN1uGS/rVn8KWPL
svyXW/RA2WKQ7OL8ZjCaztAUUbZ88zVgW+47gBf7G4D+id8A1gMfr+Bgh3Zh2RtR0EDFwv8UkEOu
INBsG8qa+XyYedj/vUAo9a430KhTIkdA41MBTU4FdHEqIGDCDq9zZKMZB6p6M7Zr5bgQGvo2IYSp
jCl6L/IkEEOnKsT4as+A43fgGLC6A53Z6g70Sqs70L2s7kA/sbpDM3inrjT7dt6hmXPvHYGPtNv0
ojFqg+SJ92Eesc4RM+xJ1DKkeR/91H9I/e3a47G52e19VH+3W+S0rmIwOJzq7/I0iR86NTISw+Dg
iPJms137WQiJVgdZjXqq/p4nTt6/0nDZCXUhnE+TyRyAP0Z+wNZJtGSpd8++Cota3P9T4t1t/QBi
eGfnepr1ffiwzr27NSYMnWBTg9LNmhDtvw8z1MHeXGRqEKWrcZINpwa/NDf+gS3D3aZQDSGXmgo+
tzBzA6I7i5pOuIn0QdwpBTcARQQRLuxFwPYJ/RfBxb59bmNK/0UoOrB9Qv9F4Dqw/e7kdWrNNK/h
udcjDa+Z9didJ1GSrnZRMQY66WFmPYIVBE0E60Gs2ieRxMx6BNfo03sZBPDcSfFTa1uUPGqBYm0O
gYKDjS6LtVEatDe0kMjaQA2skQVWP661ALIm3V/Zl5BPq9kGA2RplWt2DuexQQMQgkg59C+7JO/O
oUcGzqOivIthsidjHg1tbBh5VDTpTyLeWdi4X+CzAOoXAS2A+oVCCyCDf5hzHhUT6SD9g6MFljUt
qyiGbkdm5pk1MysguxDgKG4S8i/D6DX7gh43CSjWBtLjJgHF2jqNWKbiJgHLWdwkYBmihtlGVU61
Eco6blaBVCZAkMgNeROA3JA3AcgNeROA+pN3N4g78iZgWXOD4tQqeROAsIrNo74CqpI3AciaGwTb
yTmjIu5hK/vndxyQNwHF2kA6eRNQrK1jIm8CFlax8YQGlqI6ApYb8iYAuSFvApAb8iYAuSFvApAb
8iYA9SfvbhB35E3AsuYGxalV8iYAWdODAqqSNwEIq9hwQyt546g/OnkTUKwNpJM3AcXaOg1CVUkq
AcvaQA0sRd4ELKxi4wwSC53bRig35E2QyA15E4DckDcByA15E4D6k3c3iDvyJmBZc4Pi1Cp5E4Cs
6UEBVcmbAGTNDa3kjYPx6ORNQLE2kE7eBBRr6zQIVfEcAcvaQA0sRd4ELPSX3uRNAMIqhwLZSOSG
vAkSuSFvApAb8iYA9SfvbhB35E3AsuYGxalV8iYAWdODAqqSNwHImhtayRvHyNHJm4BibSCdvAko
1tZpEKoibwKWtYEaWIrqCFhuyJsAhI7Zm7wJQFjlACAcRTZmckPeBInckDcBqD95d4O4I28CljU3
KE6tkjcByJoeFFCVvAlA1tzA99nCflHy9tShwQmo+wyKXQ1kwJHBSFRAKeCvbMVSOKfFuneH9AQs
JLRANLgHVcRXSfLZo23sHhschAwVLqIwwS3dT7hLp3IQYTzbc5Lg/ue591Yc39HuQ5eq77yBE1LV
w078RBAenoN+5k9bOHC0LXaW89bgIBQ/GiYPMGHFd3CcSR5K4jfzU0pQEQ9qyWJct5Wo+D8cvkIc
sUEZai8YnMQDrOE5rvCIjy93eZKJKhLPX+UMTuHJWvipUQmaB4Fk+3B2jcOkxWm14kzaPZwBBLBN
CIff3shzakKh2bei66NJUTLnB91QHFFWOVKG8ndoTOlI2mSIR7uqWirPWqFyFj6cEPuZH/jSdBiF
8eeivGhuvvZT0dXyxEVRRx44aVH970FRJ+Xbt0UDyS4HBPb+S1RcPOcXzAqVx//esugLy8PA5x4i
z/bVyvipvrJASCl+zzP8G/B9ogXo1dU5/IgufWap0sR4KspKI00ui5LSSKKsp5FGRiONBKKdkUaH
GUm3B57jOIE9ShWXSi9VLMp6qnhsVPH4EBWPXakYDXwCFddcfow/hTMXA2EkaT77VupelPXUvTjp
28ZBkvXs3HviSvdo+aPrvqfyLoyOe3GI4164Uh6a7ujKg+ygjJGSpGv+WYQMDL7QnUNi5NSoYhkC
7Pxz6krFaOCTqngofaqqYlHW7cUBZAZ+ABnTnsRNHh9UO7rx8GAzjTOcMcTIrScd8qxhOSMl6tVO
vECR2TVyfq5uT5/x3N3ejNPDKmI06h2Eg/rYpa4eQgK8iEQKCf+8i5fAy/DWBsxQRWq8/OqLpuD6
nEXRBz/lusuTrblqxFa5uDo8x/mERlOLJM+Tjfl+zNfMDYBaq50RH7kQZn3Hu82CpfKkoDHB58/h
2rCEU4ZYbnAFqqbNfav5cJlKw4NJypNhrUNv1RXsUoMnWr29Z9/lCybgGUYgdmW0O7AdJvb8jR7g
53hXtubOhcVBxCChh0+YIMCrLOApiH9chRG8+gI/wS2gsQ6CbdfcbRJFySNblnpqDna9hpCr/lTy
Z2lyOuWZklDan6vJt/cf3s9DOJ3SVCC/4OGV0yuucCIZmBdl3ihLwkaNsFHjUL/iQoNPhHHIX1bS
rpPK9dNrRiDKwXksLaiptqZPqAt9BYcz69hE9ZFeTnOEeAEMCn8tzRjsMog5d/xtN82Zndo0Q1Ms
edEbemWGRabctskMObDVVFfhrTJiNyd0cP6hmM3xf0/St/zFQpwtm1M9/KKa6oHrOEvRemeQ5XJ6
iN/zCl4nJDq1EKZro/fx9OL2Cucy8VacUQaqxqOcZfEdnJAH9b66Fe1V0uiWWYwRljk3o5iIMJlx
5MiMco6kJfOSoqsXF6FOn6lVJ7eXw1evuTO1WRV7XrGhmpsqCXWEZc5tKGY6TDYcO7JhEWNNQ7GR
PP9X2LDHlG8t2+qmUzFjYrLhxJENpTx/vXFYDWUyES4igd2oPJ1FxTSOyaIXjiwqZwP+ChatzW+O
JuNb8eaXNi4tKFZGyJkeIU9nRzFXZLLj1JEdZbT4K9hxz1j8E61aW5Qs5wXgKeRjytcS4a2eOVu2
P4fUaoisrv5wW122rGWpjebLpLfFkORJpmIxlDoFMMcfkUnBVBm+pRP+FgTJ55d40rJNYNHtaig9
zVRheDmW2ZqpxmhWrLKZaoyn8FIh1KOpxuTiUj63mGpcTK46ejqdDDt6OhuLrBkSNoM6LkeTjp6C
wjp6CovPs46uDs+vrjr6OhxewezfXqUNR9Ddjirj2aSru5PpBXYX8lBQC3qLXFQHJynW3U2r7lgu
V93L/2tr7ogPjRvW3OUS8TzZpSG8ygzeEcudUy4SN0r5MnG1CNVTiyN8YVgsDTtMq9tGtRYAoJJX
JY7egaCBKgxN5pHWfJtrL86SyM+4jpuPwLXdDlUblLcIA8jPoH1LJSselm/6aypRFqNZydMEukrg
BYHYRMscyEK0fcgciOo8n8q6h2nkR3itL6ydNIXA6b3K9b7SUOfI1Tyz2s7SPrTIZq8NyObQ4/4R
8ncRL8WGH6HxxlgcA/OLC5UH4R6pWntQF9H4N7bQTCGueP+Aa/8U/Wh4VTWQ635E17zkthCXgHiA
vRlMIKKBknA1RnwCRyhoEP6iO3HfwX+gpljmqYm45zkxSLZPYmdO0//KK22eV5XYttfKwyrWlNGl
uvwopiC7qYEqKrz5VrMsLztAvJl4pWe7UZR4C9EykSSoYnxmT5oYvOwAMY7sW/C+0qZTQdHz62eW
6+zLy55fT2HhTlMpL3t+PU3ZVuspL3t+PU3ytdZTXvb8espS3U952el6Sp19TFc61fKytp6aVnjN
sY3aizXscOBvNG6SUFF+2t6E8SrRuoKFp+0H2EHfGoyFNv1QQa6ZJX5IYj/AjQTy2atSoCd6C4HZ
ttg1xR/uMt0pgKVH6PJLl5BbihrZnclDXekAkjbckSFzIH0xvZYO3+KPW71wN9SVIkoP8oovfhxm
64Zgj2whvq6kUV4Tr7opm5IfwtzCMi0alFtd4GP27WYgDtfAxn5YDcXzGAh0M5CbYKHWKsWvOil2
klFnxt7gj2CzbMuCf+vSdvusRb6nmwYSvnZfdZKX7xmVXHfzOc37qBKGS11AXtbmeU7kMzicO5tB
9qiLhIVEmcj7tOZzTgdCVeTHRkVcNUXYzHlRTQu8pisCC4mK6C0TjyJu3RXSWF0mLDyNTJwhxZSC
O4eFhFeXCQuJMpEd9vaWu+yzdVjIp3VFYOExFCGY9PGa7OVgccOEDzUFgkxvpKWhWNgm4LFTH4F5
4vRPl1+mf3K+938y/dOVwtO/AzXy//RPhljzeKVGUMj0dNNgYdt4dZIeLcyj8jjpny5guGz3PCfy
1bKe8nnDXTSFTE8XCQuJNiNH0+ef/umKgPTvVMaFL1U9RvqnywTp36lkOlL6p8sE6R9ZJrLDPv/0
T1cEpH/HUYTD9K8WTtQS8ysfTuEkMX6vW3MWVF4TX/rWxUvV3UmVRuf73glA3pgE37usTiXBppeL
88tXclewXFk07CNR+0Wg90DesrJhx8K9v4avDK7sCSkL+Jq0/IR6KKedil1N1WVJUdYdLKgJeVOd
++zUdzNIBUs8gZEXq8026tQ3caPAse3RPkLU9xM11a4uoEvAlyrD1yzjv0dQ2V4NNVyy2KpVdUnT
+0KK7DP74Q8AAAD//wMAUEsDBBQABgAIAAAAIQDvXAGBFA0AAMxRAQASAAAAd29yZC9udW1iZXJp
bmcueG1s7F3bjpvIFn0/0vmHlqV5TDdV3FvpjPDtKKOj0UjJ0XmmbTqNxoCFcfdkHvMz5xPms/IL
U4Ah0OCKKbbT1tF6mZ4AVWYvbnvV2pe3P/8Rba6egnQXJvHdhF1rk6sgXiXrMP50N/nPx+UbZ3K1
y/x47W+SOLibfA52k5/f/fMfb59v4310H6TiwCsxR7y7fd6u7iaPWba9vbnZrR6DyN9dR+EqTXbJ
Q3a9SqKb5OEhXAU3z0m6vuEa04r/26bJKtjtxDwzP37yd5PDdFF3tmQbxOK3HpI08rPddZJ+uon8
9Pf99o2Yfetn4X24CbPPYm7NqqZJ7ib7NL49nNCb+oTyIbflCR3+VCPSjhU9v1uOnCerfRTEWfGL
N2mwEeeQxLvHcPvNDNXZhImP1Sk9yYx4ijbVcc9bZnR+rzb5lGswT/1ncSm+TdiZrgeMdTko2pQ4
5Nf321V9OSPTZMYcrkg+RX0Op5xC+zerM4n8MK6nUYOmCa54JMbc3/9Kk/22Pp1tOG629/Hv9Vz5
kzngzDSrePKapu0GTdB5dD88+ttgchWtbt9/ipPUv9+IM3pmxlV+R07eibeFf7/LUn+V/bqPrlr/
er++m2jFIfEuXIt9T/5GbDEXTGcOn9zkg6P9Jgv/HTwFm4+ft0F1TLF1k28tj8qi7abax7mpzRbu
rNyzecp3hOJP9VvinZZm1cGsPEq80JZRvfF+v9kEWT3+Y/BHvevrl7/q7b+sqlk2wcPh8O1vaX7W
mbD58Lc6RvzERPz/NhF421zLZ7n5dmAY5/bn85R7xT8e/fhT8S7Wrerow+xp+SPpMomznTjS361C
cUt9+BzdJ+KFIIZ6AtDWhjAWE6+DB1/AWRqw+1McWABen0wxrzgpAVZ+8k3oWD5tJt534jX3JC4w
Ky7bKCgTAiCZYVTYVJA3kSx253gMhXKW7NMwSK9+DZ4beL7cOhZUTg/q1y//I4CVs/qW64O12K0C
63/F/Zz7F+ITWd+k7W1jIdUvFlLHkd2pPN99mZAalwqpeC/KIC12Xyak5qVCauj1x6DvwS92Xyak
wuun/kDRvEtNTfqJKnZfJqT2xUJqSz9PZr77MiEVlPoy71LLkH6eit2XAqnwUBuUIvdUG/8UJ9n4
V84wSle1xTCsKbP1hVl6SsMZxtxzjCmbFx+ftptcsplRbjEYBhhGzTvGusNgGIIGg2HkqwpgGHeT
oes0YBitpS+KpQUwDHJIwTDoIQXDaK55Uzz4/8cMg3c1jCUzDd20VBnGgnNNAObVa7mC1kDDgIaR
S/OnykEv1YpSE3q5FQxjoMrWZhMlqO1tYyGFhkFO2qBhkEMKDYMcUmgY5JBCwyCHFBoGAaQDNQy9
wzCYq00tz3ZUGYY3m4nh1oGhNEN9oGEgSqqKq5AHnL3kEmAYzeAzREkNX3AvRIrjkZHQMIZDCg2D
fHUYGgY5pNAw6CGFhgENo0q8+G6UVJmq0YySYh5jnBtLVYYxdZaOZ+qIkmomZoxdG0YehiDfL3nH
WFARJUWwotEOhISGQQ4pNAxySKFhkEMKDYMcUmgY5JBCwyCAdKCGYXY1jJnlMq4paxhL5mmcGcj0
BsNApneZyz80wh2Z3uTrbtAwyCGFhkEOKTQMckihYdBDCg0DGsbJGobVYRicTW3OPVdVw/Bm9sxz
dEM9D2MdrMLIP5SpEmFWzWJSP7HreuJXKiZFW+1JaiynMHZkwad+c1XX/6Xm6hTmjnTP+81VXZuX
mmuQmDuuSFK/uarr5lJzTQpzR7q1/eaqrmlLzbUozB3pcvabq7reLDXXpjB3pDvYb67qWrDUXIfE
3HGuWr+5quu0UnNdCnNHprNW5oq/jXI1343SsLsejqstzcVirurhzHRz4S6NER4OqmWiWiaqZUqC
lvNimpdSOwtRGmcuQKrqbUrfohT1F0Y6m8+3R6oOt3Ofz5EPrerRnh3SkQ7tK0Kq6jWfHdKRTvMr
QqrqmZ8f0nGO+StCqur9nx3Skc7/D4V0IMNwOgxDZ4ZjumWpZZV6/MxzrLmxQBw4ojQQpYEojXyN
Y2SBXAp3GFEa5GItGAY5pGAY5JCCYdBDCoaBKI2TozTcHobhuRabHRjC8Hr8js00jdnQMMAwwDDA
MMAwRhbKhYZBkB3VVtqgYZBDCg2DHFJoGOSQQsMggHSghsG6TYV1zqemox0ownCK4XHHcubmIVUV
5TKLgJaxdVdQzEY8GyhmU3a9RrnM4bUdIWKQr2VCxCCHFCIGOaQQMeghhYgBEeNkEYN1uwrrLjft
qa6rZmJYmqvNtSWq2UDFgIoBFQMqBlSMT+GQhn/IxHgrFgozkU+ZPzvNVhwFA7nMFCyoGATrw22t
DSoGOaRQMQggHapidNsKG8bC0PWpcrI3MyxuuQZUDFAMUAxQDFAMUAxQjNtDk8OKOIi/gio8+Zu7
SbyPcqF7m+zuJlAx6JfcNaNqNFmB32RthchxmawNFIPAH26zNlAMAkiHUoxuX2Ej79mla4e+wMMD
pUyLGS5yMcS1/PA5uk82CJS6ffTjYV7Gy5Ao9BVufhYRKIVAqQtIoEegFLk/DIpBDikCpeghRaAU
AqVOD5TqNhY2PH3GpzNPNVBKN5azJa/SxZGLAYoBihE8ZOXjdNpi5si+Aj+0gF17mUi1ecHZawIi
F4Pc0wDFIIcUFIMcUlAMekhBMUAxTqcY3c7CxpQLEUOzVSmGzTxDn7qLcjwoBigGKAYoRppVgSGs
fDGI+JBlVG8ExUjf5RH44nWZR5Y135qoKEUg7rchRUUpckiRi0EOKQKlyCFFoBQBpEMDpbqthY2p
btpzU71oLXMXjNloi4FAKeRiIBcDuRjIxRgWJYl0b6R750kqX79Q9MOBigEVQ6xuhWLV5m4CivEK
FKPb29uYa7Y5dQ8VoYbnYjjm3LO4xqFiIBfDEKl2Krl0yMWQpSgiFwO5GMjFWAcP/n5zCEDc/VmJ
ZLx6corO4f3CEFQMAk+jLQxBxSCHFCoGOaSgGASQDlUxus29TW3q6QvjEOg0nGLMl97Ctavm4E3J
v+zBMfLj+FdNXX5ZVZ+VvF1Aufm0WHe7/g71FZnI96r4xQ1GUaYnNzagL8agupWgGJWj1HeDgmKA
Yox8i1KsDyMXg3x9GLkY5JBCxaCHFLkYyMU4PRej293b1Oa6rTtu6bMPpxiW7syc2RJFaxEohUAp
BEohUAqBUgiUQtHau8nrJGGBYoBiiAVjBEo93z6WK9/tQNThi98DVQyxYJ/7APEuXFeSgMk003aN
wwthOMVgGne4y41abagvMFQMZWkf3b2FwvdS2xj+dLTFfZ6LVVkQZ34WPgX5N/BS/GFmQcWo3kc0
IdmoKEXuaUDFIIcUKgY5pKAY9JBCxYCKcbKKwbvdvU3TsqwZm6uqGHNjbpiudeirgUApVJRCRamB
gXwoWkv+WQTFIIcUFIMcUlAMckhBMeghBcUAxTidYnS7e5uOY2ieo1y0lumm4zrzQ7q4CsVYB6sw
8je1DPKx8ZD8xK7r7a+UjNGfQqiqM0iN5RTGFuFKN0VNzL7I/u9FM/Wbq6oASM3VKcwd6Z/3m6va
70FqrkFiruNIFY98txAEjnU/7DdXtVCq1FyTwtyRfm2/uarpv1JzLQpzR/qc/eaqpuZKzbUpzB3p
D/abq5o2KzXXITF3nK/Wb65qSqvUXJfCXMuQvqqK3Se8qoTZ/v3udBen213YnPOprasXzeT2wrH5
FKuoiAX/nvd0tEfVy5AMdBdGd+G8WL06qcEqaoMn0sS+jPQ2jz787VhFmvjFdoSWqkt79u4RIz3a
V4RU1W0+O6QjveZXhFTVNT8/pOM881eEVNX9PzukI73/HwrpUIrR7S5sTcXCi1Gliw6PBXcX9mI+
1VE0ExQDFAPpppcSXj9usfmHvsPb/rDqivbZP4ugGOSsDRSDHFJQDHpIQTEQqHG6itHtLmzNtQXj
U+V0U88wDXfujAjUkH4cUTSTKDMyIQh4GRkDctRxg4ohDb7Is1EliuZRWM+/Pqwa0CJ95CkqPELF
IPc0QDHIIQXFIIcUFIMeUlAMUIzTKUa3u7C9nE8Nb6Zcl19bGBqzF1AxoGJAxYCKARUDRTNRNBNF
M1E08/l2WIM6BEoR9KlqK8IIlCKAtBsoFe8jseIp/vt+XdUFbGRrvK+LZfKCFIjx4tCikGZzXJmV
2j+uWnDtG1emevSPK8pqHvm9Mn6rdxwz8+X3I+NKUaZ3nCjec3xcybR6xzHZeZbNmXvHyWApG671
DmNFEssR88ouCr3jZGfJynKlveNkqLCy3lHvuCId+chpMsntUvRrODZOdrtIrp64RPkd23uerGgw
cewHJfeL7DqIi3T8B2UXnkluGC67sZnslpFeC8k9I4PmUE63H1NdcjEORbJ6B0rHSW4aLh0ou2tk
V1EU9j1+FWXPhbhSRwfKLiKX3TayB4NLbhvxsDXea+WNfh+kotXeu78BAAD//wMAUEsDBBQABgAI
AAAAIQAN7UWJ4QAAAFUBAAAYACgAY3VzdG9tWG1sL2l0ZW1Qcm9wczEueG1sIKIkACigIAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJyQQWuEMBCF74X9DzJ3N1Zr1i7GpcEKey0t9JqN
UQMmI0lcWkr/eyM9bY89zbw3zHyPqU8fZk6uynmNlsH9PoNEWYm9tiODt9curSDxQdhezGgVA4tw
anZ3de+PvQjCB3TqHJRJoqFjPbcMvqpD1hbVc5Hyp5ymD5THruJlykuaF91jV3J6+IYkom084xlM
ISxHQryclBF+j4uycTigMyJE6UaCw6ClalGuRtlA8iyjRK4Rb97NDM2W53f7RQ3+Vm7RVqf/S7no
y6xxdGKZPoE0NfmD2vTNK5ofAAAA//8DAFBLAwQUAAYACAAAACEAdD85esIAAAAoAQAAHgAIAWN1
c3RvbVhtbC9fcmVscy9pdGVtMS54bWwucmVscyCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAITPwYoCMQwG4LvgO5Tcnc54EJHpeFkWvIm44LV0MjPFaVOaKPr2Fk8rLOwxCfn+pN0/
wqzumNlTNNBUNSiMjnofRwM/5+/VFhSLjb2dKaKBJzLsu+WiPeFspSzx5BOrokQ2MImkndbsJgyW
K0oYy2SgHKyUMo86WXe1I+p1XW90/m1A92GqQ28gH/oG1PmZSvL/Ng2Dd/hF7hYwyh8R2t1YKFzC
fMyUuMg2jygGvGB4t5qq3Au6a/XHf90LAAD//wMAUEsDBBQABgAIAAAAIQALFTpKKwIAAEIEAAAQ
AAgBZG9jUHJvcHMvYXBwLnhtbCCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJxU
XW/aMBR9n7T/YOVpeygmjLGCjKuJdqqqraAltM+ucxO8JbZnG1T263edFAjrnpan+5Xj43NPwq6e
m5rswHll9DxJB8OEgJamULqaJ+v8y8VlQnwQuhC10TBP9uCTK/72DVs5Y8EFBZ4ghPbzZBOCnVHq
5QYa4QfY1tgpjWtEwNRV1JSlknBt5LYBHehoOJxQeA6gCygu7BEw6RBnu/C/oIWRkZ9/yPcWCXOW
Q2NrEYDfRzr1oDChYfRYZbkJos5VA/wDlo8JW4kKPJ8y2gXs0bjC88vpdMxoF7PFRjghA0rIP6aj
ySdGexX22dpaSRFQXv5NSWe8KQNZtkKQiMBof4ShOBnIrVNhz4eM9lP2VWkkMx7hEV2I9JyonLAb
z9MRjvdylklRwwJV4KWoPTB6KrBbEHHDK6GQNduF2Q5kMI549Rt3PErIk/AQtZsnO+GU0AE1jGNd
0sa19cHxXIUasbHX5W3YH+vHaszTdgCD88EI0HHAxjm79gS/LPFu4R9k0z7ZlkNHtaOz9kAWeBdP
0MLkO/zaKgfRfJ6gMcldtrwny6cfeHuSqUqjJu3gjZZub+PSyLu7ZXbz/tUNW72Q61/sFqaxQu97
q14YZ41rDYDOeGnHVf70a5ub62jKlwWdF3vGelRhk1khcfuTYTpGDU8W6/VYhlaEAj1zQDwV2C1u
09XxWHxXV1AcZl43omkful8CT8eDIT6tSw819NnxW+V/AAAA//8DAFBLAwQUAAYACAAAACEAqchc
qowAAADaAAAAEwAoAGN1c3RvbVhtbC9pdGVtMS54bWwgoiQAKKAgAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAskmyCs4vLUpOLVYITs1JTS5JTQkuqcxJtVWKcQxw1IsI9lFSAAv4JeYC
BYFiSgoVuTl5xVZJtkoZJSUFVvr6xckZqbmJxXr5Bal5QLm0/KLcxBIgtyhdPz8tLTM51SU/uTQ3
Na9E38jAwEw/KTMpJzM/vSixIKMSahhVjLKz0Yd7xo6XCwAAAP//AwBQSwMEFAAGAAgAAAAhAFIp
4X/sAgAACQ4AABIAAAB3b3JkL2ZvbnRUYWJsZS54bWzcll1v2jAUhu8n7T9EuW/jhEBbVKgoK9ou
1ouNbdfGOGAttiPbkPLvdxwnQIvZyDT2FYQSju0T5+E978nt3RPPgzVVmkkxCONLFAZUEDlnYjEI
P00nF9dhoA0Wc5xLQQfhhurwbvj61W3Zz6QwOoD1Qvc5GYRLY4p+FGmypBzrS1lQAYOZVBwb+KkW
Ecfq66q4IJIX2LAZy5nZRAlCvbBOo07JIrOMEfpGkhWnwlTrI0VzyCiFXrJCN9nKU7KVUs0LJQnV
Gp6Z5y4fx0xs08TpQSLOiJJaZuYSHiZyO4psKlgeo+qK52HASf/dQkiFZzmwK+M0HNbggrIvMIfg
xw2fybyKF1hITWMYWuN8EKIufGJkE16hHpy76CqMbAKyxEpTs52YuHCGOcs3TVRJjoUbKJghyya+
xorZ/bghzRYwsNIzBDesj9BFYtDD80hyMKfzPEKqPNd7qyACebaZYfuRU84BiCnjVAePtAw+VDu3
E14SSYBCD3WARArfBK5SPxH0a4g8wMaT0WSyIzKGyNV1GteRHZGbOuIlUj1/7PKcTmQsV4pRZZl4
9ZGALjroBjhYbSTApA0NLudU+QSSsSc6P1THURad38HiCxSnNSXtJdFtBLY7+3XhrRS8MtJN/ycK
5S3N19Qwgr0oEnQPJZJWorDCAFn4UXhLRJdM61Ys/qwsxpjPwM6OkLAm4czCmkY7Eu3t05JAyb5Z
pDaSbiM7s4AuW5nud8zipjKdNmYhtMyxvz6cKJxTpK1RtHYK2zYOQEzGHhAnuGZbEO+lwER6FWH/
jhdHi9rYxyCkmaoVnW4KWnXkZ8ZxxEDrOzd2ud8WnRra6AOhqgWdro8pXkJb9WJpLMOVirWOM1sG
6CN52KoBQNiu2kPd+5edJPmRPmLUuqt+pmqOxd9BYmQrpbdPwloGdPMDEvEZLGMEzul/82wU4RrI
/99EcgZd5EhtTKp3q4pBa+f8iXbq9c7RubyzfhnXw28AAAD//wMAUEsDBBQABgAIAAAAIQDGHNfQ
ygIAAMAaAAAUAAAAd29yZC93ZWJTZXR0aW5ncy54bWzsWVFv2yAQfp+0/xD5vbXB2MZW00pd1WnS
NK1b9wMcmySoYCwg8dpfv7OdpMniSI20ppXGU/Add4H77rg7uLj6LcVoybThqhp76DzwRqwqVMmr
2dj7dX97Rr2RsXlV5kJVbOw9MuNdXX78cNFkDZv8ZNbCTDMCLZXJZDH25tbWme+bYs5kbs5VzSpg
TpWWuYVPPfNlrh8W9VmhZJ1bPuGC20cfB0HsrdTol2hR0ykv2I0qFpJVtpP3NROgUVVmzmuz1ta8
RFujdFlrVTBjYD9S9PpkzquNGkT2FEleaGXU1J7DZvx+RX6rCsRR0I2k8EayyL7MKqXziQALNoh4
l2C+ki/N6nfUZLwE6+OUYEpoGnYTJqp8vOFLYC5zAVzPb6eD9b6yqV1TCQ029B98Nh9k3Kt6aP61
slbJPQ4s7LrU7X/ZZ7kK0Pdgqnkae+AjMKjzAnbTjQslFICWL6zqFyO2Vnic5GRnTcfJ6u39HyPq
d2isNt3i8mnORbkLToQRphEKcYfNXygk+AAKz+QtDJ6Juwis6P+1/Xso9kxPMUrixJn+UMD9C9cf
Mj34PEEIk3h1JAlVPNwtlGXrU2P4VDoYD9uMrYhAwaGY2HBcVCx3owKFhAQkTMM+LCYOGkiSx5z6
TfZqUQNujmmA06BP5A6adwQNCUkQRQlyyeTUyQQHaRymOKGps/0pbN8n9HUxO5jeCaERiaOkR8R1
HG+QQPpOcKDjQDHBMaVRTF24nCJcOiCgrm1bcQwpIkZpBHVpW3W5dq/J9pr8V6ueYpomKYbK1tn+
1H4P7RbGQYiJK48OXm69mt+TmCQhJbi3vWvo2lvPd9LQwXEEF1BR0qdiB837gQYHCQkjBPftXbZw
0LwtNMM9x4rallLr16X1BeKi4vDcxPp3A1VbLvkTu1X6WqvGMN29eeRCqOb7t8/wAZq23p0u/wAA
AP//AwBQSwMEFAAGAAgAAAAhAPY64M69DwAA1H8AABoAAAB3b3JkL3N0eWxlc1dpdGhFZmZlY3Rz
LnhtbOxdS3PbOBK+b9X+B5VOu4fE1sOS7RpnKlHiSaqSmUzs7JwpCoo4pkgtSVnx/PptNECQBAix
IVIaz+76YFsgiA/9wNdNPKgffvy+DnuPLEmDOLrpD16e93ss8uNFEH276X+9v31x2e+lmRctvDCO
2E3/iaX9H1/9/W8/7K7T7ClkaQ8aiNLr3ca/6a+ybHN9dpb6K7b20pfrwE/iNF5mL/14fRYvl4HP
znZxsjgbng/O8b9NEvssTQFt5kWPXtqXza3N1uINiwBrGSdrL0tfxsm3s7WXPGw3L6D1jZcF8yAM
sido+3ySNxPf9LdJdC079EJ1iN9yLTok/+R3JIYUNbjizrexv12zKEPEs4SF0Ic4SlfBphDj0NZA
xFXepcd9Qjyuw7zebjMYG3hKZIoN3ibeDkxRNGg0V6OMhbhpHQo9cPsWVtVbHJzvE0ZahDeh+kDp
QhUz78naCyLVzGGqKSsXxkMb//4pibcb1Z1N0K61D9GDaosPS4eenU9w5JVFS50aMIbu3crbsH5v
7V9/+BbFiTcPoUe7wbjHPbL/CqhiEftv2dLbhlnKPyafE/lRfsI/t3GUpb3dtZf6AajnPlgDu/zM
dr0v8doDS+6umZdmr9PAq724eh2l9bf5IJ/e2hmHDL3oGzT76IU3fRa9+HpXBVFF82ABLXvJi7vX
fbjxDCXI/5Yk2Si5RC1NbCAIoIs7QZugFLb8GPsPbHGXwYWbPlAvFn798DkJ4gS47KZ/dSUL79g6
eB8sFoyzdF4xWgUL9tuKRV9TtijKf71FjpQt+vE2ym76w8kUTRGmi3fffbbhXAV4kbcG6J/5DUAk
QOolHOzQNih6Iwo0VCz8dw454AoCzdahrJjH40oP+78XCKXetgYaNkrUEdDoVEDjUwFdnAoIYnWD
13VkoykHKnsztuvkuJALtW1CCFMaU/ReZLEvhk5ZiNHVngHH78Ax4HQHOrPTHeiVTnegezndgX7i
dIdh8EZdGfZtvMMw5947fA9pV/eiEWqD5In3QRZCqG0YMYOWRC1DWu+zl3jfEm+z6vHYrHd7H9Xf
becZrasYDA6n+rssiXnG2qCRoRgGB0eUd+vNyksDSOybgFqq/p5nT72fkgAy4AaoC+F8hkz2APw5
9Hy2isMFS3r37LuwqMP9P8e9u43n4yNCQ+damvVj8G2V9SCx5AlDoyYmFqXbNSHa/xikqIO9ucjE
IkpT4yQbTix+aW/8E1sE23WuGkIuNRF87mBmDaI5i5qMuYnMQdwoBTcARQQRLtxFwPYJ/RfBxb19
bmNK/0UoOrB9Qv9F4Dqw/ebkdeLMNG9hZqZHGl5T57E7i8M4WW7DfAw00sPUeQQrCJoIzoNYtU8i
ianzCK7QZ++178NzJ8VPnW1R8KgDirM5BAoONroszkbRaG/gIJGzgTSsoQNWO651AHIm3S/sMeDz
yK7BAFla5ZqNw3lk0QCEIFIO/es2zppz6KGF86goHyKY7ElZj4Y2sow8Kpr0JxHvHGzcLvA5ALWL
gA5A7UKhA5DFP+w5j4qJdJD2wdEBy5mWVRRDtyMz89SZmRWQWwjoKG4S8i/L6LX7ghk3CSjOBjLj
JgHF2TpaLFNxk4DVWdwkYFmiht1GZU51Eco5bpaBVCZAkKgb8iYAdUPeBKBuyJsA1J68m0G6I28C
ljM3KE4tkzcBCKu4POoroDJ5E4CcuUGwnZwzyuMetrJ/fqcD8iagOBvIJG8CirN1bORNwMIqLp6g
YSmqI2B1Q94EoG7ImwDUDXkTgLohbwJQN+RNAGpP3s0g3ZE3AcuZGxSnlsmbAORMDwqoTN4EIKzi
wg215I2j/ujkTUBxNpBJ3gQUZ+tohKqSVAKWs4E0LEXeBCys4uIMEgud20WobsibIFE35E0A6oa8
CUDdkDcBqD15N4N0R94ELGduUJxaJm8CkDM9KKAyeROAnLmhlrxxMB6dvAkozgYyyZuA4mwdjVAV
zxGwnA2kYSnyJmChv7QmbwIQVjkUyEWibsibIFE35E0A6oa8CUDtybsZpDvyJmA5c4Pi1DJ5E4Cc
6UEBlcmbAOTMDbXkjWPk6ORNQHE2kEneBBRn62iEqsibgOVsIA1LUR0BqxvyJgChY7YmbwIQVjkA
CEeRi5m6IW+CRN2QNwGoPXk3g3RH3gQsZ25QnFombwKQMz0ooDJ5E4CcuYHvs4X9ouTtqQOLE1D3
GeS7GsiAQ4uRqIBSwC9syRI4mMiad4e0BMwldEC0uAdVxDdx/NCjbeweWRyEDBXMwyDGLd1PuEun
dBBhNN1zkuD+l1nvvTi+Y9yHLlXdeQMnpMqHnfiJIDwtCv3MnjZw4GiT7yznrcFBKH40TB5gwoof
4DiTPJTEb+anlKAiHtSSxbhuK1Hxfzh8hThigzLUnjM4KwpYg3Nc4REfX2+zOBVVJJ63zBic+pS1
8JNWCZoHgWT7cHaNwyT5abX8TNo9nHkFsHUAJ+DeyXNqQqHpH3nXh+O8ZMYPuqE4oqx0pAzlb9CY
0pG0yQCPdpW1VJy1QuXMPTgh9gs/8GXoMAyih7w8b2628hLR1eLERV5HHjipUf3vfl4n4du3RQPx
NgME9vExzC+e8wt2hcrjf+9Z+MiywPe4h8izfZUyfqqvKBBSit+zFP/6fJ9oDnp1dQ4/oksPLFGa
GE1EWWGk8WVeUhhJlLU00tBqpKFAdDPS8DAjmfbAcxwnsEeh4kLphYpFWUsVj6wqHh2i4lFXKkYD
n0DFFZcf4U/uzPlAGEqaT/8odC/KWupenPSt4yDJem7uPe5K92j5o+u+pfIurI57cYjjXnSlPDTd
0ZUH2UERIyVJV/wzDxkYfKE7h8TIiVXFMgS4+eekKxWjgU+q4oH0qbKKRVmzF/uQGXg+ZEx7Ejd5
fFDt6MbDg3oaZzljiJHbTDrkWcNiRkrUq5x4gSK7a2T8XN2ePuO5u70ZZw+riNFodhAO6mOXmnoI
CfA8FCkk/PMhWgAv7+RJfZEaL757oim4PmNh+MlLuO6yeGOvGrJlJq4OznE+QWtqHmdZvLbfj/ma
vQFQa7kz4iMXwq7vaLues0Qe3rMm+Pw53BiWcMoQyy2uQNW0vW8VHy5SaXgwSXgybHTovbqCXdJ4
otbbW/ZdvmACnmEEYlNGuwXbYWLP36QDfo53pSvuXFjshwwSeviECQK8ygKegvjHZRDCqy/wE9wC
Gmsg2HrN3cZhGO/YotCTPtjNGkKu6lPJn6XJyYRnSkJpf64m399/+jgL4HSKrkB+oYdXTq+43Ilk
YJ4XeaMsCbQagVbjUL/iQoNPBFHAX1ZSr5PS9dNrRiDKwXksLaipNt0n1IW2gg+lHcuP9HKaI8C2
waDw19GM/jaFmHPH33ajz+xUphl0seTF3qBXZFhkyq2bzJADW0115d4qI7Y+oYPzD/lsjvd7nLzn
LxbibKlP9fCLaqoHruMsRe2dfprJ6SF+zxt4nZDo1LziQdWnt8nF7RXOZeKtMz6ZAVSNRzmL4js4
IQ/qfXMr2iul0TWzGEMs69yMYiLCZsZhR2aUcyQ1mZcUXb24CHX6TK06vr0cvHnLnanOqtjzkg3V
3FRBqEMs69yGYqbDZsNRRzbMY6xtKGrJ83+FDVtM+VayrWY6FTMmNhuOO7KhlOevNw7LoUwmwnkk
cBuVp7OomMaxWfSiI4vK2YC/gkUrEXI4Ht2KN7/UcWlOsTJCTs0IeTo7irkimx0nHdlRRou/gh33
jMU/0aqVRcliXgCeQj4nfC0RXsqasUX9c0ilhsjqqg+35WXLSpaqNV8kvTWGJE8y5Yuh1CmAGf6I
TAqmyvAtnfA3J0g+v8STlk0Mi25XA+lptgqDy5HM1mw1htN8lc1WYzSBlwqhHm01xheX8rnFVuNi
fNXQ08l40NDT6UhkzZCwWdRxORw39BQU1tBTWHyeNnR1cH511dDXweAKZv/2Km0whO42VBlNx03d
HU8usLuQh4Ja0Fvkojo4Sb7ublt1x3K56l78X1lzR3xo3LLmLpeIZ/E2CeBVZvCOWO6ccpFYK+XL
xOUiVE8ljvCFYbE03GFaXTeqjQAAlXpl4mgdCDRUYWgyj9Tm21x7URqH/N3c5iNwZbdD2QbFLcIA
8jNo31HJioflm/50JcpiNCt5msBUCbwgEJuomQOZi7YPmQNRnedTWfcwjbyD1/rC2okuBE7vla63
lYY6R67mmdV2lvqhpc98WM1eGZD60OP+EfB3ES/Ehh+hcW0sjoD5xYXSg3CLVK0+qIto/BubG6YQ
V3r/gGv/FP3QvKocyE0/omtecluAS0A8wN70xxDRQEm4GiM+gSPkNAh/0Z247+A/UFMs81RE3POc
6MebJ7EzR/e/4kqd55Uldu218rCSNWV0KS8/iinIZmqgigpvvjUsy8sOEG8KfbMaRYk3Fy0TSYIq
xgN7MsTgZQeIcWTfgveV6k4FRc+vn2lmsi8ve349hYU7Q6W87Pn1NGEbo6e87Pn1NIZv1dDdlJc9
v56yxPRTXna6nlJnH5OlSbW8rK6nthVee2yj9mIFOxz4G4116+blp+1NEC1joytYeNp+gB3MrcFY
6NIPFeT0LPFTHHk+biSQz16lAjPRmwtMuVxaSfsm+MNdpjkFcPQIU37pEnJLkZbd2Ty0Kx1AJoE7
MmQOZC6mV/Ryiz/d6oW7oakUUXqQVzx6UZCuNMF2bC6+rkQrr4hX3pRNyQ9hbmGR5A3KrS7wMf3j
pi8O18DGflgNxfMYCHTTl5tgodYywa86yXeSUWfG3uGPYLN0w/x/mdI2+6xDvmeaBhK+el/tJC/f
Myq57mYzmvdRJQwWpoC8rM7zOpHP4nDd2QyyR1MkLCTKRN6nNZtxOhCqIj82KuKqKMJlzotqWuA1
UxFYSFREa5l4FOnWXSGNNWXCwtPIxBlSTCl057CQ8JoyYSFRJrLD3t5yl322Dgv5tKkILDyGIgST
7q7JXg4Wt0z4UFMgyPSGRhqKhXUCHjv1EZgnTv9M+WX6J+d7/yfTP1MpPP07UCP/T/9kiLWPV2oE
hUzPNA0W1o3XTtKjuX1UHif9MwUMFvWe14l8layneN7oLppCpmeKhIVEm5Gj6fNP/0xFQPp3KuPC
1/4eI/0zZYL071QyHSn9M2WC9I8sE9lhn3/6ZyoC0r/jKKLD9K8STtQS8xsPTuHEEX6vmz4LKq+J
L31r4qXy7qRSo7N97wQgb0yCLxpXp5Jg08vF+eUbuStYrixa9pGo/SLQeyBvWdmyY+HeW8FXBvNV
OzkvWRTwNWn5CfVQTDvlu5rKy5KirDlYUBNyXZ377NR2M0gJSzyBkRer7TZq1Ddxo8Cx7VE/QtT3
E+lqVxfQJeBLleFrlvHfI6hsr4Y0l8y3apVd0va+kDz7TF/9BwAA//8DAFBLAwQUAAYACAAAACEA
noh/DowBAADeAgAAEQAIAWRvY1Byb3BzL2NvcmUueG1sIKIEASigAAEAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAjJJPU8IwEMXvzvgdMjnpoaQtikynlBkRDoyIIzA63mKyQKRNYxL+fXvTFiqM
Hjwm+/aXt28Td3dZijagjchlBwcNHyOQLOdCLjp4Nh14bYyMpZLTNJfQwXswuJtcXsRMRSzX8Kxz
BdoKMMiRpImY6uCltSoixLAlZNQ0nEK64jzXGbXuqBdEUbaiCyCh77dIBpZyaikpgJ6qifiA5KxG
qrVOSwBnBFLIQFpDgkZAfrQWdGb+bCgrJ8pM2L1yMx3snrI5q4q1emdELdxut41ts7Th/AfkbfQ4
KUf1hCyyYoCTmLPICptCMjOAetS4gFyK6AW+1kJXxpFLBA0n4yc0/vgEZtFELKQLvhT2JdN7Zd1a
0NVwPOlfx6RGFnCmgdpcJyOxAjR0uzGl4Hhd7Celxo7cKucC+P3+TPm7WjRo2IjiIyRhTE6P7r0y
u+pR4MilEVXZHSuvzd7DdICT0A+ant/ygvY0DKObu8j33wtjZ/1FOtVFdrD3b+Ktf048ApLS8fmP
TL4BAAD//wMAUEsBAi0AFAAGAAgAAAAhAEmfg+KrAQAAlwYAABMAAAAAAAAAAAAAAAAAAAAAAFtD
b250ZW50X1R5cGVzXS54bWxQSwECLQAUAAYACAAAACEAHpEat/MAAABOAgAACwAAAAAAAAAAAAAA
AADkAwAAX3JlbHMvLnJlbHNQSwECLQAUAAYACAAAACEAdxkag1UHAACMRwAAHAAAAAAAAAAAAAAA
AAAIBwAAd29yZC9fcmVscy9kb2N1bWVudC54bWwucmVsc1BLAQItABQABgAIAAAAIQBgAtbISq0A
AFiHBgARAAAAAAAAAAAAAAAAAJ8PAAB3b3JkL2RvY3VtZW50LnhtbFBLAQItABQABgAIAAAAIQAw
3UMpqAYAAKQbAAAVAAAAAAAAAAAAAAAAABi9AAB3b3JkL3RoZW1lL3RoZW1lMS54bWxQSwECLQAU
AAYACAAAACEAQjhO4qUDAAA8CAAAEQAAAAAAAAAAAAAAAADzwwAAd29yZC9zZXR0aW5ncy54bWxQ
SwECLQAUAAYACAAAACEAc6IGSjEPAADjfAAADwAAAAAAAAAAAAAAAADHxwAAd29yZC9zdHlsZXMu
eG1sUEsBAi0AFAAGAAgAAAAhAO9cAYEUDQAAzFEBABIAAAAAAAAAAAAAAAAAJdcAAHdvcmQvbnVt
YmVyaW5nLnhtbFBLAQItABQABgAIAAAAIQAN7UWJ4QAAAFUBAAAYAAAAAAAAAAAAAAAAAGnkAABj
dXN0b21YbWwvaXRlbVByb3BzMS54bWxQSwECLQAUAAYACAAAACEAdD85esIAAAAoAQAAHgAAAAAA
AAAAAAAAAACo5QAAY3VzdG9tWG1sL19yZWxzL2l0ZW0xLnhtbC5yZWxzUEsBAi0AFAAGAAgAAAAh
AAsVOkorAgAAQgQAABAAAAAAAAAAAAAAAAAArucAAGRvY1Byb3BzL2FwcC54bWxQSwECLQAUAAYA
CAAAACEAqchcqowAAADaAAAAEwAAAAAAAAAAAAAAAAAP6wAAY3VzdG9tWG1sL2l0ZW0xLnhtbFBL
AQItABQABgAIAAAAIQBSKeF/7AIAAAkOAAASAAAAAAAAAAAAAAAAAPTrAAB3b3JkL2ZvbnRUYWJs
ZS54bWxQSwECLQAUAAYACAAAACEAxhzX0MoCAADAGgAAFAAAAAAAAAAAAAAAAAAQ7wAAd29yZC93
ZWJTZXR0aW5ncy54bWxQSwECLQAUAAYACAAAACEA9jrgzr0PAADUfwAAGgAAAAAAAAAAAAAAAAAM
8gAAd29yZC9zdHlsZXNXaXRoRWZmZWN0cy54bWxQSwECLQAUAAYACAAAACEAnoh/DowBAADeAgAA
EQAAAAAAAAAAAAAAAAABAgEAZG9jUHJvcHMvY29yZS54bWxQSwUGAAAAABAAEAAcBAAAxAQBAAAA

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: text/xml; name="draft-ietf-jose-use-cases-02+Mike.xml"
Content-Description: draft-ietf-jose-use-cases-02+Mike.xml
Content-Disposition: attachment;
	filename="draft-ietf-jose-use-cases-02+Mike.xml"; size=57531;
	creation-date="Tue, 18 Jun 2013 21:45:51 GMT";
	modification-date="Tue, 18 Jun 2013 22:44:52 GMT"
Content-Transfer-Encoding: base64

PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVMtQVNDSUkiPz4KPCEtLSBUaGlzIHRlbXBs
YXRlIGlzIGZvciBjcmVhdGluZyBhbiBJbnRlcm5ldCBEcmFmdCB1c2luZyB4bWwycmZjLAogICAg
IHdoaWNoIGlzIGF2YWlsYWJsZSBoZXJlOiBodHRwOi8veG1sLnJlc291cmNlLm9yZy4gLS0+Cjwh
RE9DVFlQRSByZmMgU1lTVEVNICJyZmMyNjI5LmR0ZCIgWwo8IS0tIE9uZSBtZXRob2QgdG8gZ2V0
IHJlZmVyZW5jZXMgZnJvbSB0aGUgb25saW5lIGNpdGF0aW9uIGxpYnJhcmllcy4KICAgICBUaGVy
ZSBoYXMgdG8gYmUgb25lIGVudGl0eSBmb3IgZWFjaCBpdGVtIHRvIGJlIHJlZmVyZW5jZWQuCiAg
ICAgQW4gYWx0ZXJuYXRlIG1ldGhvZCAocmZjIGluY2x1ZGUpIGlzIGRlc2NyaWJlZCBpbiB0aGUg
cmVmZXJlbmNlcy4gLS0+Cl0+Cjw/eG1sLXN0eWxlc2hlZXQgdHlwZT0ndGV4dC94c2wnIGhyZWY9
J3JmYzI2MjkueHNsdCcgPz4KPCEtLSB1c2VkIGJ5IFhTTFQgcHJvY2Vzc29ycyAtLT4KPCEtLSBG
b3IgYSBjb21wbGV0ZSBsaXN0IGFuZCBkZXNjcmlwdGlvbiBvZiBwcm9jZXNzaW5nIGluc3RydWN0
aW9ucyAoUElzKSwKICAgICBwbGVhc2Ugc2VlIGh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL2F1dGhv
cmluZy9SRUFETUUuaHRtbC4gLS0+CjwhLS0gQmVsb3cgYXJlIGdlbmVyYWxseSBhcHBsaWNhYmxl
IFByb2Nlc3NpbmcgSW5zdHJ1Y3Rpb25zIChQSXMpIHRoYXQgbW9zdCBJLURzIG1pZ2h0IHdhbnQg
dG8gdXNlLgogICAgIChIZXJlIHRoZXkgYXJlIHNldCBkaWZmZXJlbnRseSB0aGFuIHRoZWlyIGRl
ZmF1bHRzIGluIHhtbDJyZmMgdjEuMzIpIC0tPgo8P3JmYyBzdHJpY3Q9InllcyIgPz4KPCEtLSBn
aXZlIGVycm9ycyByZWdhcmRpbmcgSUQtbml0cyBhbmQgRFREIHZhbGlkYXRpb24gLS0+CjwhLS0g
Y29udHJvbCB0aGUgdGFibGUgb2YgY29udGVudHMgKFRvQykgLS0+Cjw/cmZjIHRvYz0ieWVzIj8+
CjwhLS0gZ2VuZXJhdGUgYSBUb0MgLS0+Cjw/cmZjIHRvY2RlcHRoPSI0Ij8+CjwhLS0gdGhlIG51
bWJlciBvZiBsZXZlbHMgb2Ygc3Vic2VjdGlvbnMgaW4gVG9DLiBkZWZhdWx0OiAzIC0tPgo8IS0t
IGNvbnRyb2wgcmVmZXJlbmNlcyAtLT4KPD9yZmMgc3ltcmVmcz0ieWVzIj8+CjwhLS0gdXNlIHN5
bWJvbGljIHJlZmVyZW5jZXMgdGFncywgaS5lLCBbUkZDMjExOV0gaW5zdGVhZCBvZiBbMV0gLS0+
Cjw/cmZjIHNvcnRyZWZzPSJ5ZXMiID8+CjwhLS0gc29ydCB0aGUgcmVmZXJlbmNlIGVudHJpZXMg
YWxwaGFiZXRpY2FsbHkgLS0+CjwhLS0gY29udHJvbCB2ZXJ0aWNhbCB3aGl0ZSBzcGFjZQogICAg
ICh1c2luZyB0aGVzZSBQSXMgYXMgZm9sbG93cyBpcyByZWNvbW1lbmRlZCBieSB0aGUgUkZDIEVk
aXRvcikgLS0+Cjw/cmZjIGNvbXBhY3Q9InllcyIgPz4KPCEtLSBkbyBub3Qgc3RhcnQgZWFjaCBt
YWluIHNlY3Rpb24gb24gYSBuZXcgcGFnZSAtLT4KPD9yZmMgc3ViY29tcGFjdD0ibm8iID8+Cjwh
LS0ga2VlcCBvbmUgYmxhbmsgbGluZSBiZXR3ZWVuIGxpc3QgaXRlbXMgLS0+CjwhLS0gZW5kIG9m
IGxpc3Qgb2YgcG9wdWxhciBJLUQgcHJvY2Vzc2luZyBpbnN0cnVjdGlvbnMgLS0+CjxyZmMgY2F0
ZWdvcnk9ImluZm8iIGRvY05hbWU9ImRyYWZ0LWlldGYtam9zZS11c2UtY2FzZXMtMDMiCiAgICAg
aXByPSJ0cnVzdDIwMDkwMiI+CiAgPCEtLSBjYXRlZ29yeSB2YWx1ZXM6IHN0ZCwgYmNwLCBpbmZv
LCBleHAsIGFuZCBoaXN0b3JpYwogICAgIGlwciB2YWx1ZXM6IGZ1bGwzNjY3LCBub01vZGlmaWNh
dGlvbjM2NjcsIG5vRGVyaXZhdGl2ZXMzNjY3CiAgICAgeW91IGNhbiBhZGQgdGhlIGF0dHJpYnV0
ZXMgdXBkYXRlcz0iTk5OTiIgYW5kIG9ic29sZXRlcz0iTk5OTiIKICAgICB0aGV5IHdpbGwgYXV0
b21hdGljYWxseSBiZSBvdXRwdXQgd2l0aCAiKGlmIGFwcHJvdmVkKSIgLS0+CgogIDwhLS0gKioq
KiogRlJPTlQgTUFUVEVSICoqKioqIC0tPgoKICA8ZnJvbnQ+CiAgICA8IS0tIFRoZSBhYmJyZXZp
YXRlZCB0aXRsZSBpcyB1c2VkIGluIHRoZSBwYWdlIGhlYWRlciAtIGl0IGlzIG9ubHkgbmVjZXNz
YXJ5IGlmIHRoZQogICAgICAgICBmdWxsIHRpdGxlIGlzIGxvbmdlciB0aGFuIDM5IGNoYXJhY3Rl
cnMgLS0+CgogICAgPHRpdGxlIGFiYnJldj0iSk9TRSBVc2UgQ2FzZXMiPlVzZSBDYXNlcyBhbmQg
UmVxdWlyZW1lbnRzIGZvciBKU09OIE9iamVjdAogICAgU2lnbmluZyBhbmQgRW5jcnlwdGlvbiAo
Sk9TRSk8L3RpdGxlPgoKICAgIDwhLS0gYWRkICdyb2xlPSJlZGl0b3IiJyBiZWxvdyBmb3IgdGhl
IGVkaXRvcnMgaWYgYXBwcm9wcmlhdGUgLS0+CgogICAgPGF1dGhvciBmdWxsbmFtZT0iUmljaGFy
ZCBCYXJuZXMiIGluaXRpYWxzPSJSLkwuIiBzdXJuYW1lPSJCYXJuZXMiPgogICAgICA8b3JnYW5p
emF0aW9uPkJCTiBUZWNobm9sb2dpZXM8L29yZ2FuaXphdGlvbj4KCiAgICAgIDxhZGRyZXNzPgog
ICAgICAgIDxwb3N0YWw+CiAgICAgICAgICA8c3RyZWV0PjEzMDAgTiAxN3RoIFN0PC9zdHJlZXQ+
CgogICAgICAgICAgPGNpdHk+QXJsaW5ndG9uPC9jaXR5PgoKICAgICAgICAgIDxyZWdpb24+VkE8
L3JlZ2lvbj4KCiAgICAgICAgICA8Y29kZT4yMjIwOTwvY29kZT4KCiAgICAgICAgICA8Y291bnRy
eT5VUzwvY291bnRyeT4KICAgICAgICA8L3Bvc3RhbD4KCiAgICAgICAgPGVtYWlsPnJsYkBpcHYu
c3g8L2VtYWlsPgogICAgICA8L2FkZHJlc3M+CiAgICA8L2F1dGhvcj4KCiAgICA8ZGF0ZSB5ZWFy
PSIyMDEzIi8+CgogICAgPCEtLSBJZiB0aGUgbW9udGggYW5kIHllYXIgYXJlIGJvdGggc3BlY2lm
aWVkIGFuZCBhcmUgdGhlIGN1cnJlbnQgb25lcywgeG1sMnJmYyB3aWxsIGZpbGwKICAgICAgICAg
aW4gdGhlIGN1cnJlbnQgZGF5IGZvciB5b3UuIElmIG9ubHkgdGhlIGN1cnJlbnQgeWVhciBpcyBz
cGVjaWZpZWQsIHhtbDJyZmMgd2lsbCBmaWxsCgkgaW4gdGhlIGN1cnJlbnQgZGF5IGFuZCBtb250
aCBmb3IgeW91LiBJZiB0aGUgeWVhciBpcyBub3QgdGhlIGN1cnJlbnQgb25lLCBpdCBpcwoJIG5l
Y2Vzc2FyeSB0byBzcGVjaWZ5IGF0IGxlYXN0IGEgbW9udGggKHhtbDJyZmMgYXNzdW1lcyBkYXk9
IjEiIGlmIG5vdCBzcGVjaWZpZWQgZm9yIHRoZQoJIHB1cnBvc2Ugb2YgY2FsY3VsYXRpbmcgdGhl
IGV4cGlyeSBkYXRlKS4gIFdpdGggZHJhZnRzIGl0IGlzIG5vcm1hbGx5IHN1ZmZpY2llbnQgdG8K
CSBzcGVjaWZ5IGp1c3QgdGhlIHllYXIuIC0tPgoKICAgIDxhcmVhPlNlY3VyaXR5PC9hcmVhPgoK
ICAgIDx3b3JrZ3JvdXA+Sk9TRSBXb3JraW5nIEdyb3VwPC93b3JrZ3JvdXA+CgogICAgPCEtLSBX
RyBuYW1lIGF0IHRoZSB1cHBlcmxlZnQgY29ybmVyIG9mIHRoZSBkb2MsCiAgICAgICAgIElFVEYg
aXMgZmluZSBmb3IgaW5kaXZpZHVhbCBzdWJtaXNzaW9ucy4KCSBJZiB0aGlzIGVsZW1lbnQgaXMg
bm90IHByZXNlbnQsIHRoZSBkZWZhdWx0IGlzICJOZXR3b3JrIFdvcmtpbmcgR3JvdXAiLAogICAg
ICAgICB3aGljaCBpcyB1c2VkIGJ5IHRoZSBSRkMgRWRpdG9yIGFzIGEgbm9kIHRvIHRoZSBoaXN0
b3J5IG9mIHRoZSBJRVRGLiAtLT4KCiAgICA8a2V5d29yZD5KV1MsIEpXRSwgSldLLCBKV0EsIEpX
VCwgQ01TLCBTL01JTUUsIEpPU0UsIFhNUFAsIEFMVE8sIE9BdXRoLCBGZWRlcmF0aW9uLCBTZWN1
cml0eSBUb2tlbjwva2V5d29yZD4KCiAgICA8IS0tIEtleXdvcmRzIHdpbGwgYmUgaW5jb3Jwb3Jh
dGVkIGludG8gSFRNTCBvdXRwdXQKICAgICAgICAgZmlsZXMgaW4gYSBtZXRhIHRhZyBidXQgdGhl
eSBoYXZlIG5vIGVmZmVjdCBvbiB0ZXh0IG9yIG5yb2ZmCiAgICAgICAgIG91dHB1dC4gSWYgeW91
IHN1Ym1pdCB5b3VyIGRyYWZ0IHRvIHRoZSBSRkMgRWRpdG9yLCB0aGUKICAgICAgICAga2V5d29y
ZHMgd2lsbCBiZSB1c2VkIGZvciB0aGUgc2VhcmNoIGVuZ2luZS4gLS0+CgogICAgPGFic3RyYWN0
PgogICAgICA8dD5NYW55IEludGVybmV0IGFwcGxpY2F0aW9ucyBoYXZlIGEgbmVlZCBmb3Igb2Jq
ZWN0LWJhc2VkIHNlY3VyaXR5CiAgICAgIG1lY2hhbmlzbXMgaW4gYWRkaXRpb24gdG8gc2VjdXJp
dHkgbWVjaGFuaXNtcyBhdCB0aGUgbmV0d29yayBsYXllciBvcgogICAgICB0cmFuc3BvcnQgbGF5
ZXIuIEluIHRoZSBwYXN0LCB0aGUgQ3J5cHRvZ3JhcGhpYyBNZXNzYWdlIFN5bnRheCBoYXMKICAg
ICAgcHJvdmlkZWQgYSBiaW5hcnkgc2VjdXJlIG9iamVjdCBmb3JtYXQgYmFzZWQgb24gQVNOLjEu
IE92ZXIgdGltZSwgdGhlCiAgICAgIHVzZSBvZiBiaW5hcnkgb2JqZWN0IGVuY29kaW5ncyBzdWNo
IGFzIEFTTi4xIGhhcyBiZWVuIG92ZXJ0YWtlbiBieQogICAgICB0ZXh0LWJhc2VkIGVuY29kaW5n
cywgZm9yIGV4YW1wbGUgSmF2YVNjcmlwdCBPYmplY3QgTm90YXRpb24uIFRoaXMKICAgICAgZG9j
dW1lbnQgZGVmaW5lcyBhIHNldCBvZiB1c2UgY2FzZXMgYW5kIHJlcXVpcmVtZW50cyBmb3IgYSBz
ZWN1cmUgb2JqZWN0CiAgICAgIGZvcm1hdCBlbmNvZGVkIHVzaW5nIEphdmFTY3JpcHQgT2JqZWN0
IE5vdGF0aW9uLCBkcmF3biBmcm9tIGEgdmFyaWV0eSBvZgogICAgICBhcHBsaWNhdGlvbiBzZWN1
cml0eSBtZWNoYW5pc21zIGN1cnJlbnRseSBpbiBkZXZlbG9wbWVudC48L3Q+CiAgICA8L2Fic3Ry
YWN0PgogIDwvZnJvbnQ+CgogIDxtaWRkbGU+CiAgICA8c2VjdGlvbiBhbmNob3I9ImludHJvLXNl
YyIgdGl0bGU9IkludHJvZHVjdGlvbiI+CiAgICAgIDx0PkludGVybmV0IGFwcGxpY2F0aW9ucyBy
ZXN0IG9uIHRoZSBsYXllcmVkIGFyY2hpdGVjdHVyZSBvZiB0aGUKICAgICAgSW50ZXJuZXQsIGFu
ZCB0YWtlIGFkdmFudGFnZSBvZiBzZWN1cml0eSBtZWNoYW5pc21zIGF0IGFsbCBsYXllcnMuIE1h
bnkKICAgICAgYXBwbGljYXRpb25zIHJlbHkgcHJpbWFyaWx5IG9uIGNoYW5uZWwtYmFzZWQgc2Vj
dXJpdHkgdGVjaG5vbG9naWVzLAogICAgICB3aGljaCBjcmVhdGUgYSBzZWN1cmUgY2hhbm5lbCBh
dCB0aGUgSVAgbGF5ZXIgb3IgdHJhbnNwb3J0IGxheWVyIG92ZXIKICAgICAgd2hpY2ggYXBwbGlj
YXRpb24gZGF0YSBjYW4gZmxvdyA8eHJlZiB0YXJnZXQ9IlJGQzQzMDEiLz48eHJlZgogICAgICB0
YXJnZXQ9IlJGQzUyNDYiLz4uIFRoZXNlIG1lY2hhbmlzbXMsIGhvd2V2ZXIsIGNhbm5vdCBwcm92
aWRlIGVuZC10by1lbmQKICAgICAgc2VjdXJpdHkgaW4gc29tZSBjYXNlcy4gRm9yIGV4YW1wbGUs
IGluIHByb3RvY29scyB3aXRoIGFwcGxpY2F0aW9uLWxheWVyCiAgICAgIGludGVybWVkaWFyaWVz
LCBjaGFubmVsLWJhc2VkIHNlY3VyaXR5IHByb3RvY29scyB3b3VsZCBwcm90ZWN0IG1lc3NhZ2Vz
CiAgICAgIGZyb20gYXR0YWNrZXJzIGJldHdlZW4gaW50ZXJtZWRpYXJpZXMsIGJ1dCBub3QgZnJv
bSB0aGUgaW50ZXJtZWRpYXJpZXMKICAgICAgdGhlbXNlbHZlcy4gVGhlc2UgY2FzZXMgcmVxdWly
ZSBvYmplY3QtYmFzZWQgc2VjdXJpdHkgdGVjaG5vbG9naWVzLAogICAgICB3aGljaCBlbWJlZCBh
cHBsaWNhdGlvbiBkYXRhIHdpdGhpbiBhIHNlY3VyZSBvYmplY3QgdGhhdCBjYW4gYmUgc2FmZWx5
CiAgICAgIGhhbmRsZWQgYnkgdW50cnVzdGVkIGVudGl0aWVzLjwvdD4KCiAgICAgIDx0PlRoZSBt
b3N0IHdlbGwta25vd24gZXhhbXBsZSBvZiBzdWNoIGEgcHJvdG9jb2wgdG9kYXkgaXMgdGhlIHVz
ZSBvZgogICAgICBTZWN1cmUvTXVsdGlwdXJwb3NlIEludGVybmV0IE1haWwgRXh0ZW5zaW9ucyAo
Uy9NSU1FKSBwcm90ZWN0aW9ucyB3aXRoaW4KICAgICAgdGhlIGVtYWlsIHN5c3RlbSA8eHJlZiB0
YXJnZXQ9IlJGQzU3NTEiLz48eHJlZiB0YXJnZXQ9IlJGQzUzMjIiLz4uIEFuCiAgICAgIGVtYWls
IG1lc3NhZ2UgdHlwaWNhbGx5IHBhc3NlcyB0aHJvdWdoIGEgc2VyaWVzIG9mIGludGVybWVkaWF0
ZSBNYWlsCiAgICAgIFRyYW5zZmVyIEFnZW50cyAoTVRBcykgZW4gcm91dGUgdG8gaXRzIGRlc3Rp
bmF0aW9uLiBXaGlsZSB0aGVzZSBNVEFzCiAgICAgIG9mdGVuIGFwcGx5IGNoYW5uZWwtYmFzZWQg
c2VjdXJpdHkgcHJvdGVjdGlvbnMgdG8gdGhlaXIgaW50ZXJhY3Rpb25zCiAgICAgIChlLmcuLCA8
eHJlZiB0YXJnZXQ9IlJGQzMyMDciLz4pLCB0aGVzZSBwcm90ZWN0aW9ucyBkbyBub3QgcHJldmVu
dCB0aGUKICAgICAgTVRBcyBmcm9tIGludGVyZmVyaW5nIHdpdGggdGhlIG1lc3NhZ2UuIEluIG9y
ZGVyIHRvIHByb3ZpZGUgZW5kLXRvLWVuZAogICAgICBzZWN1cml0eSBwcm90ZWN0aW9ucyBpbiB0
aGUgcHJlc2VuY2Ugb2YgdW50cnVzdGVkIE1UQXMsIG1haWwgdXNlcnMgY2FuCiAgICAgIHVzZSBT
L01JTUUgdG8gZW1iZWQgbWVzc2FnZSBib2RpZXMgaW4gYSBzZWN1cmUgb2JqZWN0IGZvcm1hdCB0
aGF0IGNhbgogICAgICBwcm92aWRlIGNvbmZpZGVudGlhbGl0eSwgaW50ZWdyaXR5LCBhbmQgZGF0
YSBvcmlnaW4gYXV0aGVudGljYXRpb24uPC90PgoKICAgICAgPHQ+Uy9NSU1FIGlzIGJhc2VkIG9u
IHRoZSBDcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IGZvciBzZWN1cmUKICAgICAgb2JqZWN0
cyAoQ01TKSA8eHJlZiB0YXJnZXQ9IlJGQzU2NTIiLz4uIENNUyBpcyBkZWZpbmVkIHVzaW5nIEFi
c3RyYWN0CiAgICAgIFN5bnRheCBOb3RhdGlvbiAxIChBU04uMSkgYW5kIHRyYWRpdGlvbmFsbHkg
ZW5jb2RlZCB1c2luZyB0aGUgQVNOLjEKICAgICAgRGlzdGluZ3Vpc2hlZCBFbmNvZGluZyBSdWxl
cyAoREVSKSwgd2hpY2ggZGVmaW5lIGEgYmluYXJ5IGVuY29kaW5nIG9mCiAgICAgIHRoZSBwcm90
ZWN0ZWQgbWVzc2FnZSBhbmQgYXNzb2NpYXRlZCBwYXJhbWV0ZXJzIDx4cmVmCiAgICAgIHRhcmdl
dD0iSVRVLlg2OTAuMTk5NCIvPi4gSW4gcmVjZW50IHllYXJzLCB1c2FnZSBvZiBBU04uMSBoYXMg
ZGVjcmVhc2VkCiAgICAgIChhbG9uZyB3aXRoIG90aGVyIGJpbmFyeSBlbmNvZGluZ3MgZm9yIGdl
bmVyYWwgb2JqZWN0cyksIHdoaWxlIG1vcmUKICAgICAgYXBwbGljYXRpb25zIGhhdmUgY29tZSB0
byByZWx5IG9uIHRleHQtYmFzZWQgZm9ybWF0cyBzdWNoIGFzIHRoZQogICAgICBFeHRlbnNpYmxl
IE1hcmt1cCBMYW5ndWFnZSAoWE1MKSBvciB0aGUgSmF2YVNjcmlwdCBPYmplY3QgTm90YXRpb24K
ICAgICAgKEpTT04pIDx4cmVmIHRhcmdldD0iVzNDLlJFQy14bWwtMTk5OCIvPjx4cmVmIHRhcmdl
dD0iUkZDNDYyNyIvPi48L3Q+CgogICAgICA8dD5NYW55IGN1cnJlbnQgYXBwbGljYXRpb25zIHRo
dXMgaGF2ZSBtdWNoIG1vcmUgcm9idXN0IHN1cHBvcnQgZm9yCiAgICAgIHByb2Nlc3Npbmcgb2Jq
ZWN0cyBpbiB0aGVzZSB0ZXh0LWJhc2VkIGZvcm1hdHMgdGhhbiBBU04uMSBvYmplY3RzOwogICAg
ICBpbmRlZWQsIG1hbnkgbGFjayB0aGUgYWJpbGl0eSB0byBwcm9jZXNzIEFTTi4xIG9iamVjdHMg
YXQgYWxsLiBUbwogICAgICBzaW1wbGlmeSB0aGUgYWRkaXRpb24gb2Ygb2JqZWN0LWJhc2VkIHNl
Y3VyaXR5IGZlYXR1cmVzIHRvIHRoZXNlCiAgICAgIGFwcGxpY2F0aW9ucywgdGhlIElFVEYgSlNP
TiBPYmplY3QgU2lnbmluZyBhbmQgRW5jcnlwdGlvbiAoSk9TRSkgd29ya2luZwogICAgICBncm91
cCBoYXMgYmVlbiBjaGFydGVyZWQgdG8gZGV2ZWxvcCBhIHNlY3VyZSBvYmplY3QgZm9ybWF0IGJh
c2VkIG9uCiAgICAgIEpTT04uIFdoaWxlIHRoZSBiYXNpYyByZXF1aXJlbWVudHMgZm9yIHRoaXMg
b2JqZWN0IGZvcm1hdCBhcmUKICAgICAgc3RyYWlnaHRmb3J3YXJkIC0tIG5hbWVseSwgY29uZmlk
ZW50aWFsaXR5IGFuZCBpbnRlZ3JpdHkgbWVjaGFuaXNtcywKICAgICAgZW5jb2RlZCBpbiBKU09O
IC0tIGRpc2N1c3Npb25zIGluIHRoZSB3b3JraW5nIGdyb3VwIGluZGljYXRlZCB0aGF0CiAgICAg
IGRpZmZlcmVudCBhcHBsaWNhdGlvbnMgaG9waW5nIHRvIHVzZSB0aGUgZm9ybWF0cyBkZWZpbmVk
IGJ5IEpPU0UgaGF2ZQogICAgICBkaWZmZXJlbnQgcmVxdWlyZW1lbnRzLiBUaGlzIGRvY3VtZW50
IHN1bW1hcml6ZXMgdGhlIHVzZSBjYXNlcyBmb3IgSk9TRQogICAgICBlbnZpc2lvbmVkIGJ5IHRo
b3NlIHBvdGVudGlhbCBhcHBsaWNhdGlvbnMgYW5kIHRoZSByZXN1bHRpbmcgcmVxdWlyZW1lbnRz
IGZvcgogICAgICBzZWN1cml0eSBtZWNoYW5pc21zIGFuZCBvYmplY3QgZW5jb2RpbmdzLjwvdD4K
CiAgICAgIDx0PlNvbWUgc3lzdGVtcyB0aGF0IHVzZSBYTUwgaGF2ZSBzcGVjaWZpZWQgdGhlIHVz
ZSBvZiBYTUwtYmFzZWQKICAgICAgc2VjdXJpdHkgbWVjaGFuaXNtcyBmb3Igb2JqZWN0IHNlY3Vy
aXR5LCBuYW1lbHkgWE1MIERpZ2l0YWwgU2lnbmF0dXJlcwogICAgICBhbmQgWE1MIEVuY3J5cHRp
b24gPHhyZWYgdGFyZ2V0PSJXM0MuQ1IteG1sZHNpZy1jb3JlMi0yMDEyMDEyNCIvPjx4cmVmCiAg
ICAgIHRhcmdldD0iVzNDLkNSLXhtbGVuYy1jb3JlMS0yMDEyMDMxMyIvPi4gVGhlc2UgbWVjaGFu
aXNtcyBhcmUgZGVmaW5lZAogICAgICBmb3IgdXNlIHdpdGggc2V2ZXJhbCBzZWN1cml0eSB0b2tl
biBzeXN0ZW1zIChlLmcuLAogICAgICBTQU1MIDx4cmVmIHRhcmdldD0iT0FTSVMuc2FtbC1jb3Jl
LTIuMC1vcyIvPiBhbmQKICAgICAgV1MtRmVkZXJhdGlvbiA8eHJlZiB0YXJnZXQ9IldTLUZlZGVy
YXRpb24iLz4pIGFuZCB0aGUgQ0FQCiAgICAgIGVtZXJnZW5jeSBhbGVydGluZyBmb3JtYXQgPHhy
ZWYgdGFyZ2V0PSJDQVAiLz4uIEluIHByYWN0aWNlLCBob3dldmVyLAogICAgICBYTUwtYmFzZWQg
c2VjdXJlIG9iamVjdCBmb3JtYXRzIGludHJvZHVjZSBzaW1pbGFyIGxldmVscyBvZiBjb21wbGV4
aXR5CiAgICAgIHRvIEFTTi4xLCBzbyBkZXZlbG9wZXJzIHRoYXQgbGFjayB0aGUgdG9vbHMgb3Ig
bW90aXZhdGlvbiB0byBoYW5kbGUKICAgICAgQVNOLjEgYXJlbid0IGxpa2VseSB0byB1c2UgWE1M
IHNlY3VyaXR5IGVpdGhlci4gVGhpcyBzaXR1YXRpb24gbW90aXZhdGVzCiAgICAgIHRoZSBjcmVh
dGlvbiBvZiBhIEpTT04tYmFzZWQgc2VjdXJlIG9iamVjdCBmb3JtYXQgdGhhdCBpcyBzaW1wbGUg
ZW5vdWdoCiAgICAgIHRvIGltcGxlbWVudCBhbmQgZGVwbG95IHRoYXQgaXQgY2FuIGJlIGVhc2ls
eSBhZG9wdGVkIGJ5IGRldmVsb3BlcnMgd2l0aAogICAgICBtaW5pbWFsIGVmZm9ydCBhbmQgdG9v
bHMuPC90PgogICAgPC9zZWN0aW9uPgoKICAgIDxzZWN0aW9uIGFuY2hvcj0iZGVmLXNlYyIgdGl0
bGU9IkRlZmluaXRpb25zIj4KICAgICAgPCEtLQogICAgICA8dD5UaGUga2V5IHdvcmRzICJtdXN0
IiwgIm11c3QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsCiAgICAgICJT
SE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFM
IiBpbiB0aGlzCiAgICAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmli
ZWQgaW4gPHhyZWYKICAgICAgdGFyZ2V0PSJSRkMyMTE5Ij5SRkMgMjExOTwveHJlZj4uPC90Pgog
ICAgICAtLT4KCiAgICAgIDx0PlRoaXMgZG9jdW1lbnQgbWFrZXMgZXh0ZW5zaXZlIHVzZSBvZiBz
dGFuZGFyZCBzZWN1cml0eSB0ZXJtaW5vbG9neQogICAgICA8eHJlZiB0YXJnZXQ9IlJGQzQ5NDki
Lz4uIEluIGFkZGl0aW9uLCBiZWNhdXNlIHRoZSB1c2UgY2FzZXMgZm9yIEpPU0UKICAgICAgYW5k
IENNUyBhcmUgc2ltaWxhciwgd2Ugd2lsbCBzb21ldGltZXMgbWFrZSBhbmFsb2dpZXMgdG8gc29t
ZSBDTVMKICAgICAgY29uY2VwdHMgPHhyZWYgdGFyZ2V0PSJSRkM1NjUyIi8+LjwvdD4KCiAgICAg
IDx0PlRoZSBKT1NFIHdvcmtpbmcgZ3JvdXAgY2hhcnRlciBjYWxscyBmb3IgdGhlIGdyb3VwIHRv
IGRlZmluZSB0aHJlZQogICAgICBiYXNpYyBKU09OIG9iamVjdCBmb3JtYXRzOjxsaXN0IHN0eWxl
PSJudW1iZXJzIj4KICAgICAgICAgIDx0PkNvbmZpZGVudGlhbGl0eS1wcm90ZWN0ZWQgb2JqZWN0
IGZvcm1hdDwvdD4KCiAgICAgICAgICA8dD5JbnRlZ3JpdHktcHJvdGVjdGVkIG9iamVjdCBmb3Jt
YXQ8L3Q+CgogICAgICAgICAgPHQ+QSBmb3JtYXQgZm9yIGV4cHJlc3Npbmcga2V5czwvdD4KICAg
ICAgICA8L2xpc3Q+CgogICAgICBJbiB0aGlzIGRvY3VtZW50LCB3ZSB3aWxsIHJlZmVyIHRvIHRo
ZXNlIGFzCiAgICAgIHRoZSAic2lnbmVkIG9iamVjdCBmb3JtYXQiLAogICAgICB0aGUgImVuY3J5
cHRlZCBvYmplY3QgZm9ybWF0IiwKICAgICAgYW5kIHRoZSAia2V5IGZvcm1hdCIsIHJlc3BlY3Rp
dmVseS4KICAgICAgVGhlIEpPU0Ugd29ya2luZyBncm91cCBpdGVtcyBpbnRlbmRlZCB0byBkZXNj
cmliZSB0aGVzZSBmb3JtYXRzIGFyZSAKICAgICAgSlNPTiBXZWIgU2lnbmF0dXJlIChKV1MpLCBK
U09OIFdlYiBFbmNyeXB0aW9uIChKV0UpLCBhbmQgSlNPTiBXZWIgS2V5IChKV0spLAogICAgICBy
ZXNwZWN0aXZlbHkgPHhyZWYgdGFyZ2V0PSJJLUQuaWV0Zi1qb3NlLWpzb24td2ViLXNpZ25hdHVy
ZSIvPiwKICAgICAgPHhyZWYgdGFyZ2V0PSJJLUQuaWV0Zi1qb3NlLWpzb24td2ViLWVuY3J5cHRp
b24iLz4sIGFuZAogICAgICA8eHJlZiB0YXJnZXQ9IkktRC5pZXRmLWpvc2UtanNvbi13ZWIta2V5
Ii8+LgogICAgICBBbGdvcml0aG1zIGFuZCBhbGdvcml0aG0gaWRlbnRpZmllcnMgdXNlZCBieSBK
V1MsIEpXRSwgYW5kIEpXSyBhcmUgZGVmaW5lZCBpbgogICAgICBKU09OIFdlYiBBbGdvcml0aG1z
IChKV0EpIDx4cmVmIHRhcmdldD0iSS1ELmlldGYtam9zZS1qc29uLXdlYi1hbGdvcml0aG1zIi8+
LgogICAgICA8L3Q+CgogICAgICA8dD5JbiBnZW5lcmFsLCB3aGVyZSB0aGVyZSBpcyBubyBuZWVk
IHRvIGRpc3Rpbmd1aXNoIGJldHdlZW4gYXN5bW1ldHJpYyBhbmQKICAgICAgc3ltbWV0cmljIG9w
ZXJhdGlvbnMsIHdlIHdpbGwgdXNlIHRoZSB0ZXJtcyAic2lnbmluZyIsICJzaWduYXR1cmUiLCBl
dGMuCiAgICAgIHRvIGRlbm90ZSBib3RoIHRydWUgZGlnaXRhbCBzaWduYXR1cmVzIGludm9sdmlu
ZyBhc3ltbWV0cmljIGNyeXB0b2dyYXBoeQogICAgICBhcyB3ZWxsIGFzIG1lc3NhZ2UgYXV0aGVu
dGljYXRpb24gY29kZXMgdXNpbmcgc3ltbWV0cmljIGtleXMgKE1BQ3MpLjwvdD4KCiAgICAgIDx0
PkluIHRoZSBsaWZlc3BhbiBvZiBhIHNlY3VyZSBvYmplY3QsIHRoZXJlIGFyZSB0d28gYmFzaWMg
cm9sZXMsIGFuCiAgICAgIGVudGl0eSB0aGF0IGNyZWF0ZXMgdGhlIG9iamVjdCAoZS5nLiwgZW5j
cnlwdGluZyBvciBzaWduaW5nIGEgcGF5bG9hZCksCiAgICAgIGFuZCBhbiBlbnRpdHkgdGhhdCB1
c2VzIHRoZSBvYmplY3QgKGRlY3J5cHRpbmcsIHZlcmlmeWluZykuIFdlIHdpbGwKICAgICAgcmVm
ZXIgdG8gdGhlc2Ugcm9sZXMgYXMgInNlbmRlciIgYW5kICJyZWNpcGllbnQiLCByZXNwZWN0aXZl
bHkuIE5vdGUKICAgICAgdGhhdCB3aGlsZSBzb21lIHJlcXVpcmVtZW50cyBhbmQgdXNlIGNhc2Vz
IG1heSByZWZlciB0byB0aGVzZSBhcyBzaW5nbGUKICAgICAgZW50aXRpZXMsIGVhY2ggb2JqZWN0
IG1heSBoYXZlIG11bHRpcGxlIGVudGl0aWVzIGluIGVhY2ggcm9sZS4gRm9yCiAgICAgIGV4YW1w
bGUsIGEgbWVzc2FnZSBtYXkgYmUgc2lnbmVkIGJ5IG11bHRpcGxlIHNlbmRlcnMsIG9yIGRlY3J5
cHRlZCBieQogICAgICBtdWx0aXBsZSByZWNpcGllbnRzLjwvdD4KICAgIDwvc2VjdGlvbj4KCiAg
ICA8c2VjdGlvbiBhbmNob3I9ImJhc2ljLXNlYyIgdGl0bGU9IkJhc2ljIFJlcXVpcmVtZW50cyI+
CiAgICAgIDx0Pk9idmlvdXNseSwgZm9yIHRoZSBlbmNyeXB0ZWQgYW5kIHNpZ25lZCBvYmplY3Qg
Zm9ybWF0cywgdGhlIG5lY2Vzc2FyeQogICAgICBwcm90ZWN0aW9ucyB3aWxsIGJlIGNyZWF0ZWQg
dXNpbmcgYXBwcm9wcmlhdGUgY3J5cHRvZ3JhcGhpYyBtZWNoYW5pc21zOgogICAgICBzeW1tZXRy
aWMgb3IgYXN5bW1ldHJpYyBlbmNyeXB0aW9uIGZvciBjb25maWRlbnRpYWxpdHkgYW5kIE1BQ3Mg
b3IKICAgICAgZGlnaXRhbCBzaWduYXR1cmVzIGZvciBpbnRlZ3JpdHkgcHJvdGVjdGlvbi4gSW4g
Ym90aCBjYXNlcywgaXQgaXMKICAgICAgbmVjZXNzYXJ5IGZvciB0aGUgSk9TRSBmb3JtYXQgdG8g
c3VwcG9ydCBib3RoIHN5bW1ldHJpYyBhbmQgYXN5bW1ldHJpYwogICAgICBvcGVyYXRpb25zLjxs
aXN0IHN0eWxlPSJzeW1ib2xzIj4KICAgICAgICAgIDx0PlRoZSBKT1NFIGVuY3J5cHRlZCBvYmpl
Y3QgZm9ybWF0IG11c3Qgc3VwcG9ydCBvYmplY3QgZW5jcnlwdGlvbgogICAgICAgICAgaW4gdGhl
IGNhc2Ugd2hlcmUgdGhlIHNlbmRlciBhbmQgcmVjZWl2ZXIgc2hhcmUgYSBzeW1tZXRyaWMga2V5
LjwvdD4KCiAgICAgICAgICA8dD5UaGUgSk9TRSBlbmNyeXB0ZWQgb2JqZWN0IGZvcm1hdCBtdXN0
IHN1cHBvcnQgb2JqZWN0IGVuY3J5cHRpb24KICAgICAgICAgIGluIHRoZSBjYXNlIHdoZXJlIHRo
ZSBzZW5kZXIgaGFzIG9ubHkgYSBwdWJsaWMga2V5IGZvciB0aGUKICAgICAgICAgIHJlY2VpdmVy
LjwvdD4KCiAgICAgICAgICA8dD5UaGUgSk9TRSBzaWduZWQgb2JqZWN0IGZvcm1hdCBtdXN0IHN1
cHBvcnQgaW50ZWdyaXR5IHByb3RlY3Rpb24gdXNpbmcKICAgICAgICAgIE1lc3NhZ2UgQXV0aGVu
dGljYXRpb24gQ29kZXMgKE1BQ3MpLCBmb3IgdGhlIGNhc2Ugd2hlcmUgdGhlIHNlbmRlcgogICAg
ICAgICAgYW5kIHJlY2VpdmVyIHNoYXJlIG9ubHkgYSBzeW1tZXRyaWMga2V5LjwvdD4KCiAgICAg
ICAgICA8dD5UaGUgSk9TRSBzaWduZWQgb2JqZWN0IGZvcm1hdCBtdXN0IHN1cHBvcnQgaW50ZWdy
aXR5IHByb3RlY3Rpb24gdXNpbmcKICAgICAgICAgIGRpZ2l0YWwgc2lnbmF0dXJlcywgZm9yIHRo
ZSBjYXNlIHdoZXJlIHRoZSByZWNlaXZlciBoYXMgb25seSBhCiAgICAgICAgICBwdWJsaWMga2V5
IGZvciB0aGUgc2VuZGVyLjwvdD4KICAgICAgICA8L2xpc3Q+PC90PgoKICAgICAgPHQ+SW4gc29t
ZSBhcHBsaWNhdGlvbnMsIHRoZSBrZXkgdXNlZCB0byBwcm9jZXNzIGEgSk9TRSBvYmplY3QgaXMg
aW5kaWNhdGVkCiAgICAgIGJ5IGFwcGxpY2F0aW9uIGNvbnRleHQsIGluc3RlYWQgb2YgZGlyZWN0
bHkgaW4gdGhlIEpPU0Ugb2JqZWN0LiAgSG93ZXZlciwKICAgICAgaW4gb3JkZXIgdG8gYXZvaWQg
Y29uZnVzaW5nIGVuZHBvaW50cyB0aGF0IGxhY2sgdGhlIG5lY2Vzc2FyeSBjb250ZXh0IG5lZWQK
ICAgICAgdG8gYmUgYWJsZSB0byByZWNvZ25pemUgdGhpcyBhbmQgZmFpbCBjbGVhbmx5LiAgT3Ro
ZXIgdGhhbiBrZXlzLCBKT1NFIG9iamVjdHMgCiAgICAgIGRvIG5vdCBzdXBwb3J0IHByZS1uZWdv
dGlhdGlvbjsgYWxsIGNyeXB0b2dyYXBoaWMgcGFyYW1ldGVycyBtdXN0IGJlIGV4cHJlc3NlZAog
ICAgICBkaXJlY3RseSBpbiB0aGUgSk9TRSBvYmplY3QuCiAgICAgICAgICA8bGlzdCBzdHlsZT0i
c3ltYm9scyI+CiAgICAgICAgICA8dD5UaGUgSk9TRSBzaWduZWQgYW5kIGVuY3J5cHRlZCBvYmpl
Y3QgZm9ybWF0cyBtdXN0IGRlZmluZSB0aGUgcHJvY2VzcwogICAgICAgICAgYnkgd2hpY2ggYW4g
aW1wbGVtZW50YXRpb24gcmVjb2duaXplcyB3aGV0aGVyIGl0IGhhcyB0aGUga2V5IHJlcXVpcmVk
CiAgICAgICAgICB0byBwcm9jZXNzIGEgZ2l2ZW4gb2JqZWN0IGluIHRoZSBjYXNlIHRoYXQgdGhl
IGFwcGxpY2F0aW9uIGRvZXMgbm90CgkgIHNwZWNpZnkgdGhlIHVzZSBvZiBhbm90aGVyIG1lYW5z
IG9yIGNvbnZlbnRpb24gdG8gZGV0ZXJtaW5lIHRoZSBrZXkgdXNlZC48L3Q+CiAgICAgICAgICA8
dD5FYWNoIGFsZ29yaXRobSB1c2VkIGZvciBKT1NFIG11c3QgZGVmaW5lIHdoaWNoIHBhcmFtZXRl
cnMgYXJlIAogICAgICAgICAgcmVxdWlyZWQgdG8gYmUgcHJlc2VudCBpbiBhIEpPU0Ugb2JqZWN0
IHVzaW5nIHRoYXQgYWxnb3JpdGhtLjwvdD4KICAgICAgICAgIDwvbGlzdD4KICAgICAgPC90PgoK
ICAgICAgPHQ+SW4gY2FzZXMgd2hlcmUgdHdvIGVudGl0aWVzIGFyZSBnb2luZyB0byBiZSBleGNo
YW5naW5nIHNldmVyYWwgSk9TRQogICAgICBvYmplY3RzLCBpdCBtaWdodCBiZSBoZWxwZnVsIHRv
IHByZS1uZWdvdGlhdGUgc29tZSBwYXJhbWV0ZXJzIHNvIHRoYXQgCiAgICAgIHRoZXkgZG8gbm90
IGhhdmUgdG8gYmUgc2lnbmFsZWQgaW4gZXZlcnkgSk9TRSBvYmplY3QuICBIb3dldmVyLAogICAg
ICBzbyBhcyBub3QgdG8gY29uZnVzZSBlbmRwb2ludHMgdGhhdCBkbyBub3Qgc3VwcG9ydCBwcmUt
bmVnb3RpYXRpb24sCiAgICAgIGl0IGlzIHVzZWZ1bCB0byBzaWduYWwgd2hlbiBwcmUtbmVnb3Rp
YXRlZCBwYXJhbWV0ZXJzIGFyZSBpbiB1c2UgaW4gdGhvc2UgY2FzZXMuCiAgICAgICAgICA8bGlz
dCBzdHlsZT0ic3ltYm9scyI+CiAgICAgICAgICA8dD5JdCBzaG91bGQgYmUgcG9zc2libGUgdG8g
ZXh0ZW5kIHRoZSBiYXNlCgkgIEpPU0Ugc2lnbmVkIGFuZCBlbmNyeXB0ZWQgb2JqZWN0IGZvcm1h
dHMKCSAgdG8gaW5kaWNhdGUgdGhhdCBwcmUtbmVnb3RpYXRlZCBwYXJhbWV0ZXJzIGFyZSB0byBi
ZSB1c2VkIHRvIAogICAgICAgICAgcHJvY2VzcyB0aGUgb2JqZWN0LiAgVGhpcyBleHRlbnNpb24g
c2hvdWxkIGFsc28gcHJvdmlkZSBhIG1lYW5zIG9mIGluZGljYXRpbmcgb2YgCiAgICAgICAgICB3
aGljaCBwYXJhbWV0ZXJzIGFyZSB0byBiZSB1c2VkLjwvdD4KICAgICAgICAgIDwvbGlzdD4KICAg
ICAgPC90PgoKICAgICAgPHQ+VGhlIHB1cnBvc2Ugb2YgdGhlIGtleSBmb3JtYXQgaXMgdG8gcHJv
dmlkZSB0aGUgcmVjaXBpZW50IHdpdGgKICAgICAgc3VmZmljaWVudCBpbmZvcm1hdGlvbiB0byB1
c2UgdGhlIGVuY29kZWQga2V5IHRvIHByb2Nlc3MgY3J5cHRvZ3JhcGhpYwogICAgICBtZXNzYWdl
cy4gVGh1cyBpdCBpcyBzb21ldGltZXMgbmVjZXNzYXJ5IHRvIGluY2x1ZGUgYWRkaXRpb25hbCBw
YXJhbWV0ZXJzIGFsb25nCiAgICAgIHdpdGggdGhlIGJhcmUga2V5LjwvdD4KCiAgICAgIDx0Pjxs
aXN0IHN0eWxlPSJzeW1ib2xzIj4KICAgICAgICAgIDx0PlRoZSBKT1NFIGtleSBmb3JtYXQgbXVz
dCBlbmFibGUgaW5jbHVzaW9uIG9mIGFsbCBhbGdvcml0aG0gcGFyYW1ldGVycwogICAgICAgICAg
bmVjZXNzYXJ5IHRvIHVzZSB0aGUgZW5jb2RlZCBrZXksIGluY2x1ZGluZyBhbiBpZGVudGlmaWVy
IGZvciB0aGUKICAgICAgICAgIGFsZ29yaXRobSB3aXRoIHdoaWNoIHRoZSBrZXkgaXMgdXNlZCBh
cyB3ZWxsIGFzIGFueSBhZGRpdGlvbmFsCiAgICAgICAgICBwYXJhbWV0ZXJzIHJlcXVpcmVkIGJ5
IHRoZSBhbGdvcml0aG0gKGUuZy4sIGVsbGlwdGljIGN1cnZlCiAgICAgICAgICBwYXJhbWV0ZXJz
KS48L3Q+CiAgICAgICAgPC9saXN0PjwvdD4KICAgIDwvc2VjdGlvbj4KCiAgICA8c2VjdGlvbiBh
bmNob3I9ImFwcC1yZXEtc2VjIiB0aXRsZT0iUmVxdWlyZW1lbnRzIG9uIEFwcGxpY2F0aW9uIFBy
b3RvY29scyI+CiAgICAgIDx0PgogICAgICAgIFRoZSBKT1NFIHNlY3VyZSBvYmplY3QgZm9ybWF0
cyBkZXNjcmliZSBob3cgY3J5cHRvZ3JhcGhpYyBwcm9jZXNzaW5nIGlzIAogICAgICAgIGRvbmUg
b24gc2VjdXJlZCBjb250ZW50LCBlbnN1cmluZyB0aGF0IHRoZSByZWNpcGllbnQgYW4gb2JqZWN0
IGlzIGFibGUKICAgICAgICB0byBwcm9wZXJseSBkZWNyeXB0IGFuIGVuY3J5cHRlZCBvYmplY3Qg
b3IgdmVyaWZ5IGEgc2lnbmF0dXJlLiAgSW4gb3JkZXIKICAgICAgICB0byBtYWtlIHVzZSBvZiBK
T1NFLCBob3dldmVyLCBhcHBsaWNhdGlvbnMgd2lsbCBuZWVkIHRvIHNwZWNpZnkgc2V2ZXJhbAog
ICAgICAgIGFzcGVjdHMgb2YgaG93IEpPU0UgaXMgdG8gYmUgdXNlZDoKICAgICAgICA8bGlzdCBz
dHlsZT0ic3ltYm9scyI+CiAgICAgICAgICA8dD5XaGF0IGFwcGxpY2F0aW9uIGRhdGEgaXMgdG8g
YmUgcHJvdGVjdGVkPC90PgogICAgICAgICAgPHQ+V2hpY2ggY3J5cHRvZ3JhcGhpYyBhbGdvcml0
aG1zIGFyZSB0byBiZSB1c2VkPC90PgogICAgICAgICAgPHQ+SG93IGFwcGxpY2F0aW9uIHByb3Rv
Y29sIGVudGl0aWVzIGVzdGFibGlzaCBrZXlzPC90PgogICAgICAgICAgPHQ+V2hldGhlciBrZXlz
IGFyZSB0byBiZSBleHBsaWNpdGx5IGluZGljYXRlZCBpbiBKT1NFIG9iamVjdHMsIG9yIAogICAg
ICAgICAgICAgYXNzb2NpYXRlZCBieSBhcHBsaWNhdGlvbiBjb250ZXh0PC90PgogICAgICAgIDwv
bGlzdD4KICAgICAgPC90PgogICAgPC9zZWN0aW9uPgoKICAgIDxzZWN0aW9uIGFuY2hvcj0idXNl
LWNhc2VzLXNlYyIgdGl0bGU9IlVzZSBDYXNlcyI+CiAgICAgIDx0PlNldmVyYWwgd29ya2luZyBn
cm91cHMgZGV2ZWxvcGluZyBhcHBsaWNhdGlvbi1sYXllciBwcm90b2NvbHMKICAgICAgaGF2ZSBl
eHByZXNzZWQgYSBkZXNpcmUgdG8gdXNlIHRoZSBKT1NFIGRhdGEgZm9ybWF0cyBpbiB0aGVpcgog
ICAgICBkZXNpZ25zIGZvciBlbmQtdG8tZW5kIHNlY3VyaXR5IGZlYXR1cmVzLiBJbiB0aGlzIHNl
Y3Rpb24sIHdlIHN1bW1hcml6ZQogICAgICB0aGUgdXNlIGNhc2VzIHByb3Bvc2VkIGJ5IHRoZXNl
IGdyb3VwcyBhbmQgZGlzY3VzcyB0aGUgcmVxdWlyZW1lbnRzIHRoYXQKICAgICAgdGhleSBpbXBs
eSBmb3IgdGhlIEpPU0Ugb2JqZWN0IGZvcm1hdHMuPC90PgoKICAgICAgPHNlY3Rpb24gYW5jaG9y
PSJzZWMtdG9rZW4tc2VjIiB0aXRsZT0iU2VjdXJpdHkgVG9rZW5zIj4KICAgICAgICA8dD5TZWN1
cml0eSB0b2tlbnMgYXJlIGEgY29tbW9uIHVzZSBjYXNlIGZvciBvYmplY3QtYmFzZWQgc2VjdXJp
dHksCiAgICAgICAgZm9yIGV4YW1wbGUsIFNBTUwgYXNzZXJ0aW9ucyA8eHJlZiB0YXJnZXQ9Ik9B
U0lTLnNhbWwtY29yZS0yLjAtb3MiLz4uCiAgICAgICAgU2VjdXJpdHkgdG9rZW5zIGFyZSB1c2Vk
IHRvIGNvbnZleSBpbmZvcm1hdGlvbiBhYm91dCBhIHN1YmplY3QgZW50aXR5CiAgICAgICAgKCJj
bGFpbXMiIG9yICJhc3NlcnRpb25zIikgZnJvbSBhbiBpc3N1ZXIgdG8gYSByZWNpcGllbnQuIFRo
ZSBzZWN1cml0eQogICAgICAgIGZlYXR1cmVzIG9mIGEgdG9rZW4gZm9ybWF0IGVuYWJsZSB0aGUg
cmVjaXBpZW50IHRvIHZlcmlmeSB0aGF0IHRoZQogICAgICAgIGNsYWltcyBjYW1lIGZyb20gdGhl
IGlzc3VlciBhbmQsIGlmIHRoZSBvYmplY3QgaXMKICAgICAgICBjb25maWRlbnRpYWxpdHktcHJv
dGVjdGVkLCB0aGF0IHRoZXkgd2VyZSBub3QgdmlzaWJsZSB0byBvdGhlcgogICAgICAgIHBhcnRp
ZXMuPC90PgoKICAgICAgICA8dD5TZWN1cml0eSB0b2tlbnMgYXJlIHVzZWQgaW4gZmVkZXJhdGlv
biBwcm90b2NvbHMgc3VjaCBhcyBTQU1MIDIuMAoJPHhyZWYgdGFyZ2V0PSJPQVNJUy5zYW1sLWNv
cmUtMi4wLW9zIi8+LAogICAgICAgIFdTLUZlZGVyYXRpb24gPHhyZWYgdGFyZ2V0PSJXUy1GZWRl
cmF0aW9uIi8+LAoJTW96aWxsYSBQZXJzb25hIDx4cmVmIHRhcmdldD0iUGVyc29uYSIvPiwKCWFu
ZCBPcGVuSUQgQ29ubmVjdCA8eHJlZiB0YXJnZXQ9Ik9wZW5JRC5NZXNzYWdlcyIvPiwKCWFzIHdl
bGwgYXMgaW4gcmVzb3VyY2UgYXV0aG9yaXphdGlvbgogICAgICAgIHByb3RvY29scyBzdWNoIGFz
IE9BdXRoIDIuMCA8eHJlZiB0YXJnZXQ9IlJGQzY3NDkiLz4sCglpbmNsdWRpbmcgZm9yIE9BdXRo
IGJlYXJlciB0b2tlbnMgPHhyZWYgdGFyZ2V0PSJSRkM2NzUwIi8+LiBJbiBzb21lIGNhc2VzLAog
ICAgICAgIHNlY3VyaXR5IHRva2VucyBhcmUgdXNlZCBmb3IgY2xpZW50IGF1dGhlbnRpY2F0aW9u
IGFuZCBmb3IgYWNjZXNzCiAgICAgICAgY29udHJvbCA8eHJlZiB0YXJnZXQ9IkktRC5pZXRmLW9h
dXRoLWp3dC1iZWFyZXIiLz48eHJlZgogICAgICAgIHRhcmdldD0iSS1ELmlldGYtb2F1dGgtc2Ft
bDItYmVhcmVyIi8+LjwvdD4KCgk8dD5KU09OIFdlYiBUb2tlbiAoSldUKSA8eHJlZiB0YXJnZXQ9
IkktRC5pZXRmLW9hdXRoLWpzb24td2ViLXRva2VuIi8+CglpcyBhIHNlY3VyaXR5IHRva2VuIGZv
cm1hdAoJYmFzZWQgb24gSlNPTiBhbmQgSk9TRS4gSXQgaXMgdXNlZCB3aXRoIE1vemlsbGEgUGVy
c29uYSwKCU9wZW5JRCBDb25uZWN0LCBhbmQgT0F1dGguIEJlY2F1c2UgSldUcyBhcmUgb2Z0ZW4g
dXNlZCBpbiBjb250ZXh0cwoJd2l0aCBsaW1pdGVkIHNwYWNlIChlLmcuLCBIVFRQIHF1ZXJ5IHBh
cmFtZXRlcnMpLCBpdCBpcyBhIGNvcmUKCXJlcXVpcmVtZW50IGZvciBKV1RzLCBhbmQgdGh1cyBK
T1NFLCB0byBoYXZlIGEgY29tcGFjdCwgVVJMLXNhZmUKCXJlcHJlc2VudGF0aW9uLjwvdD4KCiAg
ICAgIDwvc2VjdGlvbj4KCiAgICAgIDxzZWN0aW9uIGFuY2hvcj0ib2F1dGgtc2VjIiB0aXRsZT0i
T0F1dGgiPgoKICAgICAgICA8dD5UaGUgT0F1dGggcHJvdG9jb2wgZGVmaW5lcyBhIG1lY2hhbmlz
bSBmb3IgZGlzdHJpYnV0aW5nIGFuZCB1c2luZwogICAgICAgIGF1dGhvcml6YXRpb24gdG9rZW5z
IHVzaW5nIEhUVFAgPHhyZWYgdGFyZ2V0PSJSRkM2NzQ5Ii8+LiBBIENsaWVudAogICAgICAgIHRo
YXQgd2lzaGVzIHRvIGFjY2VzcyBhIHByb3RlY3RlZCByZXNvdXJjZSByZXF1ZXN0cyBhdXRob3Jp
emF0aW9uIGZyb20KICAgICAgICB0aGUgUmVzb3VyY2UgT3duZXIuIElmIHRoZSBSZXNvdXJjZSBP
d25lciBhbGxvd3MgdGhpcyBhY2Nlc3MsIGhlCiAgICAgICAgZGlyZWN0cyBhbiBBdXRob3JpemF0
aW9uIFNlcnZlciB0byBpc3N1ZSBhbiBhY2Nlc3MgdG9rZW4gdG8gdGhlCiAgICAgICAgQ2xpZW50
LiBXaGVuIHRoZSBDbGllbnQgd2lzaGVzIHRvIGFjY2VzcyB0aGUgcHJvdGVjdGVkIHJlc291cmNl
LCBoZQogICAgICAgIHByZXNlbnRzIHRoZSB0b2tlbiB0byB0aGUgcmVsZXZhbnQgUmVzb3VyY2Ug
U2VydmVyLCB3aGljaCB2ZXJpZmllcyB0aGUKICAgICAgICB2YWxpZGl0eSBvZiB0aGUgdG9rZW4g
YmVmb3JlIHByb3ZpZGluZyBhY2Nlc3MgdG8gdGhlIHByb3RlY3RlZAogICAgICAgIHJlc291cmNl
LjwvdD4KCiAgICAgICAgPGZpZ3VyZSBhbmNob3I9ImZpZ09BdXRoIiB0aXRsZT0iVGhlIE9BdXRo
IHByb2Nlc3MiPgogICAgICAgICAgPGFydHdvcms+PCFbQ0RBVEFbICAgICAgICAgICAgICArLS0t
LS0tLS0tLS0tLS0tKyAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKwogICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICB8ICAgICAgICAgIHwgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAg
fCAgIFJlc291cmNlICAgIHw8Li4uLi4uLi4+fCBBdXRob3JpemF0aW9uIHwKICAgICAgICAgICAg
ICB8ICAgIFNlcnZlciAgICAgfCAgICAgICAgICB8ICAgICBTZXJ2ZXIgICAgfAogICAgICAgICAg
ICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgIHwgICAgICAgICAgICAgICB8CiAgICAgICAg
ICAgICAgKy0tLS0tLS0tLS0tLS0tLSsgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLSsKICAgICAg
ICAgICAgICAgICAgICAgICAgICAgXiAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAg
ICAgICB8CiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAogICAg
ICAgICAgICAgICstLS0tLS0tLS0tLS18LS0rICAgICAgICAgICstLXwtLS0tLS0tLS0tLS0rCiAg
ICAgICAgICAgICAgfCAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tKyAgICAgICAgICAgIHwK
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgfCAgICAgICAgICB8ICAgUmVzb3VyY2UgICAg
fAogICAgICAgICAgICAgIHwgICAgIENsaWVudCAgICB8ICAgICAgICAgIHwgICAgIE93bmVyICAg
ICB8CiAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgIHwgICAgICAgICAgfCAgICAgICAgICAg
ICAgIHwKICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKyAgICAgICAgICArLS0tLS0tLS0t
LS0tLS0tK11dPjwvYXJ0d29yaz4KCiAgICAgICAgICA8cG9zdGFtYmxlLz4KICAgICAgICA8L2Zp
Z3VyZT4KCiAgICAgICAgPHQ+SW4gZWZmZWN0LCB0aGlzIHByb2Nlc3MgbW92ZXMgdGhlIHRva2Vu
IGZyb20gdGhlIEF1dGhvcml6YXRpb24KICAgICAgICBTZXJ2ZXIgKGFzIGEgc2VuZGVyIG9mIHRo
ZSBvYmplY3QpIHRvIHRoZSBSZXNvdXJjZSBTZXJ2ZXIgKHJlY2lwaWVudCksCiAgICAgICAgdmlh
IHRoZSBDbGllbnQgYXMgd2VsbCBhcyB0aGUgUmVzb3VyY2UgT3duZXIgKHRoZSBsYXR0ZXIgYmVj
YXVzZSBvZgogICAgICAgIHRoZSBIVFRQIG1lY2hhbmljcyB1bmRlcmx5aW5nIHRoZSBwcm90b2Nv
bCkuIFNvIGFnYWluIHdlIGhhdmUgYSBjYXNlCiAgICAgICAgd2hlcmUgYW4gYXBwbGljYXRpb24g
b2JqZWN0IGlzIHRyYW5zcG9ydGVkIHZpYSB1bnRydXN0ZWQKICAgICAgICBpbnRlcm1lZGlhcmll
cy48L3Q+CgogICAgICAgIDx0PlRoaXMgYXBwbGljYXRpb24gaGFzIHR3byBlc3NlbnRpYWwgc2Vj
dXJpdHkgcmVxdWlyZW1lbnRzOiBJbnRlZ3JpdHkKICAgICAgICBhbmQgZGF0YSBvcmlnaW4gYXV0
aGVudGljYXRpb24uIEludGVncml0eSBwcm90ZWN0aW9uIGlzIHJlcXVpcmVkIHNvCiAgICAgICAg
dGhhdCB0aGUgUmVzb3VyY2UgT3duZXIgYW5kIHRoZSBDbGllbnQgY2Fubm90IG1vZGlmeSB0aGUg
cGVybWlzc2lvbgogICAgICAgIGVuY29kZWQgaW4gdGhlIHRva2VuLiBEYXRhIG9yaWdpbiBhdXRo
ZW50aWNhdGlvbiBpcyByZXF1aXJlZCBzbyB0aGF0CiAgICAgICAgdGhlIFJlc291cmNlIFNlcnZl
ciBjYW4gdmVyaWZ5IHRoYXQgdGhlIHRva2VuIHdhcyBpc3N1ZWQgYnkgYSB0cnVzdGVkCiAgICAg
ICAgQXV0aG9yaXphdGlvbiBTZXJ2ZXIuIENvbmZpZGVudGlhbGl0eSBwcm90ZWN0aW9uIG1heSBh
bHNvIGJlIG5lZWRlZCwKICAgICAgICBpZiB0aGUgQXV0aG9yaXphdGlvbiBTZXJ2ZXIgaXMgY29u
Y2VybmVkIGFib3V0IHRoZSB2aXNpYmlsaXR5IG9mCiAgICAgICAgcGVybWlzc2lvbnMgaW5mb3Jt
YXRpb24gdG8gdGhlIFJlc291cmNlIE93bmVyIG9yIENsaWVudC4gRm9yIGV4YW1wbGUsCiAgICAg
ICAgcGVybWlzc2lvbnMgcmVsYXRlZCB0byBzb2NpYWwgbmV0d29ya2luZyBtaWdodCBiZSBjb25z
aWRlcmVkIHByaXZhdGUKICAgICAgICBpbmZvcm1hdGlvbi4gTm90ZSwgaG93ZXZlciwgdGhhdCBP
QXV0aCBhbHJlYWR5IHJlcXVpcmVzIHRoYXQgdGhlCiAgICAgICAgdW5kZXJseWluZyBIVFRQIHRy
YW5zYWN0aW9ucyBiZSBwcm90ZWN0ZWQgYnkgVExTLCBzbyBjb25maWRlbnRpYWxpdHkKICAgICAg
ICBwcm90ZWN0aW9uIGlzIG5vdCBzdHJpY3RseSBuZWNlc3NhcnkgZm9yIHRoaXMgdXNlIGNhc2Uu
PC90PgoKICAgICAgICA8dD5UaGUgY29uZmlkZW50aWFsaXR5IGFuZCBpbnRlZ3JpdHkgbmVlZHMg
YXJlIG1ldCBieSB0aGUgYmFzaWMKICAgICAgICByZXF1aXJlbWVudHMgZm9yIHNpZ25lZCBhbmQg
ZW5jcnlwdGVkIG9iamVjdCBmb3JtYXRzLCB3aGV0aGVyIHRoZQogICAgICAgIHNpZ25pbmcgYW5k
IGVuY3J5cHRpb24gYXJlIHByb3ZpZGVkIHVzaW5nIGFzeW1tZXRyaWMgb3Igc3ltbWV0cmljCiAg
ICAgICAgY3J5cHRvZ3JhcGh5LiBUaGUgY2hvaWNlIG9mIHdoaWNoIG1lY2hhbmlzbSBpcyBhcHBs
aWVkIHdpbGwgZGVwZW5kIG9uCiAgICAgICAgdGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuIHRoZSB0
d28gc2VydmVycywgbmFtZWx5IHdoZXRoZXIgdGhleSBzaGFyZSBhCiAgICAgICAgc3ltbWV0cmlj
IGtleSBvciBvbmx5IHB1YmxpYyBrZXlzLjwvdD4KCiAgICAgICAgPHQ+QXV0aGVudGljYXRpb24g
cmVxdWlyZW1lbnRzIHdpbGwgYWxzbyBkZXBlbmQgb24gZGVwbG95bWVudAogICAgICAgIGNoYXJh
Y3RlcmlzdGljcy4gV2hlcmUgdGhlcmUgaXMgYSByZWxhdGl2ZWx5IHN0cm9uZyBiaW5kaW5nIGJl
dHdlZW4KICAgICAgICB0aGUgcmVzb3VyY2Ugc2VydmVyIGFuZCB0aGUgYXV0aG9yaXphdGlvbiBz
ZXJ2ZXIsIGl0IG1heSBzdWZmaWNlIGZvcgogICAgICAgIHRoZSBBdXRob3JpemF0aW9uIFNlcnZl
ciBpc3N1aW5nIGEgdG9rZW4gdG8gYmUgaWRlbnRpZmllZCBieSB0aGUga2V5CiAgICAgICAgdXNl
ZCB0byBzaWduIHRoZSB0b2tlbi4gVGhpcyByZXF1aXJlcyB0aGF0IHRoZSBwcm90b2NvbCBjYXJy
eSBlaXRoZXIgdGhlCiAgICAgICAgcHVibGljIGtleSBvZiB0aGUgQXV0aG9yaXphdGlvbiBTZXJ2
ZXIgb3IgYW4gaWRlbnRpZmllciBmb3IgdGhlIHB1YmxpYwogICAgICAgIG9yIHN5bW1ldHJpYyBr
ZXkuICBJbiBPQXV0aCwgdGhlIDxzcGFueCBzdHlsZT0idmVyYiI+Y2xpZW50X2lkPC9zcGFueD4g
CiAgICAgICAgcGFyYW1ldGVyIGlkZW50aWZpZXMgdGhlIGtleSB0byBiZSB1c2VkLjwvdD4KCiAg
ICAgICAgPHQ+VGhlcmUgbWF5IGFsc28gYmUgbW9yZSBhZHZhbmNlZCBjYXNlcywgd2hlcmUgdGhl
IEF1dGhvcml6YXRpb24KICAgICAgICBTZXJ2ZXIncyBrZXkgaXMgbm90IGtub3duIGluIGFkdmFu
Y2UgdG8gdGhlIFJlc291cmNlIFNlcnZlci4gVGhpcyBtYXkKICAgICAgICBoYXBwZW4sIGZvciBp
bnN0YW5jZSwgaWYgYW4gZW50aXR5IGluc3RhbnRpYXRlZCBhIGNvbGxlY3Rpb24gb2YKICAgICAg
ICBBdXRob3JpemF0aW9uIFNlcnZlcnMgKHNheSBmb3IgbG9hZCBiYWxhbmNpbmcpLCBlYWNoIG9m
IHdoaWNoIGhhcyBhbgogICAgICAgIGluZGVwZW5kZW50IGtleSBwYWlyLiBJbiB0aGVzZSBjYXNl
cywgaXQgbWF5IGJlIG5lY2Vzc2FyeSB0byBhbHNvCiAgICAgICAgaW5jbHVkZSBhIGNlcnRpZmlj
YXRlIG9yIGNlcnRpZmljYXRlIGNoYWluIGZvciB0aGUgQXV0aG9yaXphdGlvbgogICAgICAgIFNl
cnZlciwgc28gdGhhdCB0aGUgUmVzb3VyY2UgU2VydmVyIGNhbiB2ZXJpZnkgdGhhdCB0aGUgQXV0
aG9yaXphdGlvbgogICAgICAgIFNlcnZlciBpcyBhbiBlbnRpdHkgdGhhdCBpdCB0cnVzdHMuPC90
PgoKICAgICAgICA8dD5UaGUgSFRUUCB0cmFuc3BvcnQgZm9yIE9BdXRoIGltcG9zZXMgYSBwYXJ0
aWN1bGFyIGNvbnN0cmFpbnQgb24gdGhlCiAgICAgICAgZW5jb2RpbmcuIEluIHRoZSBPQXV0aCBw
cm90b2NvbCwgdG9rZW5zIGZyZXF1ZW50bHkgbmVlZCB0byBiZSBwYXNzZWQKICAgICAgICBhcyBx
dWVyeSBwYXJhbWV0ZXJzIGluIEhUVFAgVVJJcyA8eHJlZiB0YXJnZXQ9IlJGQzI2MTYiLz4sIGFm
dGVyCiAgICAgICAgaGF2aW5nIGJlZW4gYmFzZTY0dXJsIGVuY29kZWQgPHhyZWYgdGFyZ2V0PSJS
RkM0NjQ4Ii8+LiBXaGlsZSB0aGVyZSBpcwogICAgICAgIG5vIHNwZWNpZmllZCBsaW1pdCBvbiB0
aGUgbGVuZ3RoIG9mIFVSSXMgKGFuZCB0aHVzIG9mIHF1ZXJ5CiAgICAgICAgcGFyYW1ldGVycyks
IGluIHByYWN0aWNlLCBVUklzIG9mIG1vcmUgdGhhbiAyLDA0OCBjaGFyYWN0ZXJzIGFyZQogICAg
ICAgIHJlamVjdGVkIGJ5IHNvbWUgdXNlciBhZ2VudHMuICBGb3Igc29tZSBtb2JpbGUgYnJvd3Nl
cnMsIHRoaXMgbGltaXQgaXMgCiAgICAgICAgZXZlbiBzbWFsbGVyLiBTbyB0aGlzIHVzZSBjYXNl
IHJlcXVpcmVzIHRoYXQgYSBKT1NFCiAgICAgICAgb2JqZWN0IGhhdmUgc3VmZmljaWVudGx5IHNt
YWxsIHNpemUgZXZlbiBhZnRlciBzaWduaW5nLCBwb3NzaWJseQogICAgICAgIGVuY3J5cHRpbmcs
IHdoaWxlIHN0aWxsIGJlaW5nIHNpbXBsZSB0byBpbmNsdWRlIGluIGFuIEhUVFAgVVJJIHF1ZXJ5
CiAgICAgICAgcGFyYW1ldGVyLjwvdD4KICAgICAgPC9zZWN0aW9uPgoKICAgICAgPHNlY3Rpb24g
YW5jaG9yPSJmZWQtc2VjIiB0aXRsZT0iRmVkZXJhdGlvbiI+CiAgICAgICAgPHQ+U2VjdXJpdHkg
dG9rZW5zIGFyZSB1c2VkIGluIHR3byBmZWRlcmF0ZWQgaWRlbnRpdHkgcHJvdG9jb2xzOjwvdD4K
CiAgICAgICAgPHQ+PGxpc3Qgc3R5bGU9InN5bWJvbHMiPgoJICAgIDx0PlRoZSBPcGVuSUQgQ29u
bmVjdCBwcm90b2NvbCA8eHJlZiB0YXJnZXQ9Ik9wZW5JRC5NZXNzYWdlcyIvPgoJICAgIGlzIGEg
c2ltcGxlLCBSRVNUL0pTT04tYmFzZWQKCSAgICBpZGVudGl0eSBmZWRlcmF0aW9uIHByb3RvY29s
IGxheWVyZWQgb24gT0F1dGggMi4wLgoJICAgIEl0IHVzZXMgdGhlIEpXVCBhbmQgSk9TRSBmb3Jt
YXRzIGJvdGgKICAgICAgICAgICAgdG8gcmVwcmVzZW50IHNlY3VyaXR5IHRva2VucyBhbmQgdG8g
cHJvdmlkZSBzZWN1cml0eSBmb3Igb3RoZXIKICAgICAgICAgICAgcHJvdG9jb2wgbWVzc2FnZXMg
KHBlcmZvcm1pbmcgc2lnbmluZyBhbmQgb3B0aW9uYWxseSBlbmNyeXB0aW9uKS4KCSAgICBPcGVu
SUQgQ29ubmVjdCBuZWdvdGlhdGVzIHRoZSBhbGdvcml0aG1zIHRvIGJlIHVzZWQgYW5kIGRpc3Ry
aWJ1dGVzCgkgICAgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGtleXMgdG8gYmUgdXNlZCB1c2luZyBw
cm90b2NvbCBlbGVtZW50cwoJICAgIHRoYXQgYXJlIG5vdCBwYXJ0IG9mIHRoZSBKV1QgYW5kIEpP
U0UgaGVhZGVyIHBhcmFtZXRlcnMuPC90PgoKCSAgICA8dD5UaGUgTW96aWxsYSBQZXJzb25hIDx4
cmVmIHRhcmdldD0iUGVyc29uYSIvPiBzeXN0ZW0gaXMgYSBzaW1wbGUKCSAgICBzaW5nbGUtc2ln
bi1vbiAoU1NPKSBwcm90b2NvbCB0aGF0IHVzZXMgSldUcyB0aGF0IGFyZSBzaWduZWQKCSAgICBK
T1NFIEpXUyBvYmplY3RzIHRvIHJlcHJlc2VudCBpbmZvcm1hdGlvbiBhYm91dCBpZGVudGl0aWVz
LAoJICAgIGFwcGxpY2F0aW9ucywgYW5kIGtleXMgZm9yIHBhcnRpY2lwYXRpbmcgZW50aXRpZXMu
CgkgICAgUGVyc29uYSBkaXN0cmlidXRlcyB0aGUga2V5cyB1c2VkIGFzIGNsYWltcyBpbiBKV1Qg
bWVzc2FnZXMKCSAgICBhbmQgbm90IGJ5IHVzaW5nIEpPU0UgaGVhZGVyIHBhcmFtZXRlcnMuCgkg
ICAgPC90PgogICAgICAgICAgPC9saXN0PjwvdD4KICAgICAgPC9zZWN0aW9uPgoKICAgICAgPHNl
Y3Rpb24gYW5jaG9yPSJ4bXBwLXNlYyIgdGl0bGU9IlhNUFAiPgogICAgICAgIDx0PlRoZSBFeHRl
bnNpYmxlIE1lc3NhZ2luZyBhbmQgUHJlc2VuY2UgUHJvdG9jb2wgKFhNUFApIHJvdXRlcwogICAg
ICAgIG1lc3NhZ2VzIGZyb20gb25lIGVuZCBjbGllbnQgdG8gYW5vdGhlciBieSB3YXkgb2YgWE1Q
UCBzZXJ2ZXJzIDx4cmVmCiAgICAgICAgdGFyZ2V0PSJSRkM2MTIwIi8+LiBUaGVyZSBhcmUgdHlw
aWNhbGx5IHR3byBzZXJ2ZXJzIGludm9sdmVkIGluCiAgICAgICAgZGVsaXZlcmluZyBhbnkgZ2l2
ZW4gbWVzc2FnZTogVGhlIGZpcnN0IGNsaWVudCAoQWxpY2UpIHNlbmRzIGEgbWVzc2FnZQogICAg
ICAgIGZvciBhbm90aGVyIGNsaWVudCAoQikgdG8gaGVyIHNlcnZlciAoQSkuIFNlcnZlciBBIHVz
ZXMgQm9iJ3MgaWRlbnRpdHkKICAgICAgICBhbmQgdGhlIEROUyB0byBsb2NhdGUgdGhlIHNlcnZl
ciBmb3IgQm9iJ3MgZG9tYWluIChCKSwgdGhlbiBkZWxpdmVycwogICAgICAgIHRoZSBtZXNzYWdl
IHRvIHRoYXQgc2VydmVyLiBTZXJ2ZXIgQiB0aGVuIHJvdXRlcyB0aGUgbWVzc2FnZSB0bwogICAg
ICAgIEJvYi48L3Q+CgogICAgICAgIDxmaWd1cmUgYW5jaG9yPSJmaWcteG1wcCIgdGl0bGU9IkRl
bGl2ZXJpbmcgYW4gWE1QUCBtZXNzYWdlIj4KICAgICAgICAgIDxhcnR3b3JrPjwhW0NEQVRBWwog
ICAgICAgICArLS0tLS0tLSsgICArLS0tLS0tLS0tLSsgICArLS0tLS0tLS0tLSsgICArLS0tLS0r
CiAgICAgICAgIHwgQWxpY2UgfC0tPnwgU2VydmVyIEEgfC0tPnwgU2VydmVyIEIgfC0tPnwgQm9i
IHwKICAgICAgICAgKy0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0t
LS0tK11dPjwvYXJ0d29yaz4KICAgICAgICA8L2ZpZ3VyZT4KCiAgICAgICAgPHQ+VGhlIHVudHJ1
c3RlZC1pbnRlcm1lZGlhcnkgcHJvYmxlbXMgYXJlIGVzcGVjaWFsbHkgYWN1dGUgZm9yIFhNUFAK
ICAgICAgICBiZWNhdXNlIGluIG1hbnkgY3VycmVudCBkZXBsb3ltZW50cywgdGhlIGhvbGRlciBv
ZiBhbiBYTVBQIGRvbWFpbgogICAgICAgIG91dHNvdXJjZXMgdGhlIG9wZXJhdGlvbiBvZiB0aGUg
ZG9tYWluJ3Mgc2VydmVycyB0byBhIGRpZmZlcmVudAogICAgICAgIGVudGl0eS4gSW4gdGhpcyBl
bnZpcm9ubWVudCwgdGhlcmUgaXMgYSBjbGVhciByaXNrIG9mIGV4cG9zaW5nIHRoZQogICAgICAg
IGRvbWFpbiBob2xkZXIncyBwcml2YXRlIGluZm9ybWF0aW9uIHRvIHRoZSBkb21haW4gb3BlcmF0
b3IuIFhNUFAKICAgICAgICBhbHJlYWR5IGhhcyBhIGRlZmluZWQgbWVjaGFuaXNtIGZvciBlbmQt
dG8tZW5kIHNlY3VyaXR5IHVzaW5nIFMvTUlNRSwKICAgICAgICBidXQgaXQgaGFzIGZhaWxlZCB0
byBnYWluIHdpZGVzcHJlYWQgZGVwbG95bWVudCA8eHJlZgogICAgICAgIHRhcmdldD0iUkZDMzky
MyIvPiwgaW4gcGFydCBiZWNhdXNlIG9mIGtleSBtYW5hZ2VtZW50IGNoYWxsZW5nZXMgYW5kCiAg
ICAgICAgYmVjYXVzZSBvZiB0aGUgZGlmZmljdWx0eSBvZiBwcm9jZXNzaW5nIFMvTUlNRSBvYmpl
Y3RzLjwvdD4KCiAgICAgICAgPHQ+VGhlIFhNUFAgd29ya2luZyBncm91cCBpcyBpbiB0aGUgcHJv
Y2VzcyBvZiBkZXZlbG9waW5nIGEgbmV3CiAgICAgICAgZW5kLXRvLWVuZCBlbmNyeXB0aW9uIHN5
c3RlbSB3aXRoIGFuIGVuY29kaW5nIGJhc2VkIG9uIEpPU0UgYW5kIGEKICAgICAgICBjbGVhcmVy
IGtleSBtYW5hZ2VtZW50IHN5c3RlbSA8eHJlZiB0YXJnZXQ9IkktRC5taWxsZXIteG1wcC1lMmUi
Lz4uCiAgICAgICAgVGhlIHByb2Nlc3Mgb2Ygc2VuZGluZyBhbiBlbmNyeXB0ZWQgbWVzc2FnZSBp
biB0aGlzIHN5c3RlbSBpbnZvbHZlcwogICAgICAgIHR3byBzdGVwczogRmlyc3QsIHRoZSBzZW5k
ZXIgZ2VuZXJhdGVzIGEgc3ltbWV0cmljIENvbnRlbnQgRW5jcnlwdGlvbgogICAgICAgIEtleSAo
Q0VLKSwgZW5jcnlwdHMgdGhlIG1lc3NhZ2UgY29udGVudCwgYW5kIHNlbmRzIHRoZSBlbmNyeXB0
ZWQKICAgICAgICBtZXNzYWdlIHRvIHRoZSBkZXNpcmVkIHNldCBvZiByZWNpcGllbnRzLiBTZWNv
bmQsIGVhY2ggcmVjaXBpZW50CiAgICAgICAgImRpYWxzIGJhY2siIHRvIHRoZSBzZW5kZXIsIHBy
b3ZpZGluZyBoaXMgcHVibGljIGtleTsgdGhlIHNlbmRlciB0aGVuCiAgICAgICAgcmVzcG9uZHMg
d2l0aCB0aGUgcmVsZXZhbnQgQ0VLLCB3cmFwcGVkIHdpdGggdGhlIHJlY2lwaWVudCdzIHB1Ymxp
YwogICAgICAgIGtleS48L3Q+CgogICAgICAgIDxmaWd1cmUgYW5jaG9yPSJmaWcteG1wcC1zZWMi
IHRpdGxlPSJEZWxpdmVyaW5nIGEgc2VjdXJlIFhNUFAgbWVzc2FnZSI+CiAgICAgICAgICA8YXJ0
d29yaz48IVtDREFUQVsKICAgICAgICAgKy0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0t
LS0tLS0rICAgKy0tLS0tKwogICAgICAgICB8IEFsaWNlIHw8LT58IFNlcnZlciBBIHw8LT58IFNl
cnZlciBCIHw8LT58IEJvYiB8CiAgICAgICAgICstLS0tLS0tKyAgICstLS0tLS0tLS0tKyAgICst
LS0tLS0tLS0tKyAgICstLS0tLSsKICAgICAgICAgICAgIHwgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgfCAgICAgICAgICAgfAogICAgICAgICAgICAgfC0tLS0tLS0tLS0tLUVuY3J5cHRlZC0t
bWVzc2FnZS0tLS0tLS0tLT58ICAKICAgICAgICAgICAgIHwgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgfCAgICAgICAgICAgfAogICAgICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS1QdWJsaWMt
a2V5LS0tLS0tLS0tLS0tLS18CiAgICAgICAgICAgICB8ICAgICAgICAgICAgIHwgICAgICAgICAg
ICAgIHwgICAgICAgICAgIHwKICAgICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS1XcmFwcGVkIENF
Sy0tLS0tLS0tLS0tLS0+fAogICAgICAgICAgICAgfCAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICB8ICAgICAgICAgICB8XV0+PC9hcnR3b3JrPgogICAgICAgIDwvZmlndXJlPgoKICAgICAgICA8
dD5UaGUgbWFpbiB0aGluZyB0aGF0IHRoaXMgc3lzdGVtIHJlcXVpcmVzIGZyb20gdGhlIEpPU0Ug
Zm9ybWF0cyBpcwogICAgICAgIGNvbmZpZGVudGlhbGl0eSBwcm90ZWN0aW9uIHZpYSBjb250ZW50
IGVuY3J5cHRpb24sIHBsdXMgYW4gaW50ZWdyaXR5CiAgICAgICAgY2hlY2sgdmlhIGEgTUFDIGRl
cml2ZWQgZnJvbSB0aGUgc2FtZSBzeW1tZXRyaWMga2V5LiBUaGUgc2VwYXJhdGlvbiBvZgogICAg
ICAgIHRoZSBrZXkgZXhjaGFuZ2UgZnJvbSB0aGUgdHJhbnNtaXNzaW9uIG9mIHRoZSBlbmNyeXB0
ZWQgY29udGVudCwKICAgICAgICBob3dldmVyLCByZXF1aXJlcyB0aGF0IHRoZSBKT1NFIGVuY3J5
cHRlZCBvYmplY3QgZm9ybWF0IGFsbG93IHdyYXBwZWQKICAgICAgICBzeW1tZXRyaWMga2V5cyB0
byBiZSBjYXJyaWVkIHNlcGFyYXRlbHkgZnJvbSB0aGUgZW5jcnlwdGVkIHBheWxvYWQuIEluCiAg
ICAgICAgYWRkaXRpb24sIHRoZSBlbmNyeXB0ZWQgb2JqZWN0IHdpbGwgbmVlZCB0byBoYXZlIGEg
dGFnIGZvciB0aGUga2V5CiAgICAgICAgdGhhdCB3YXMgdXNlZCB0byBlbmNyeXB0IHRoZSBjb250
ZW50LCBzbyB0aGF0IHRoZSByZWNpcGllbnQgKEJvYikgY2FuCiAgICAgICAgcHJlc2VudCB0aGUg
dGFnIHRvIHRoZSBzZW5kZXIgKEFsaWNlKSB3aGVuIHJlcXVlc3RpbmcgdGhlIHdyYXBwZWQKICAg
ICAgICBrZXkuPC90PgoKICAgICAgICA8dD5Bbm90aGVyIGltcG9ydGFudCBmZWF0dXJlIG9mIFhN
UFAgaXMgdGhhdCBpdCBhbGxvd3MgZm9yIHRoZQogICAgICAgIHNpbXVsdGFuZW91cyBkZWxpdmVy
eSBvZiBhIG1lc3NhZ2UgdG8gbXVsdGlwbGUgcmVjaXBpZW50cy4gSW4gdGhlCiAgICAgICAgZGlh
Z3JhbXMgYWJvdmUsIFNlcnZlciBBIGNvdWxkIGRlbGl2ZXIgdGhlIG1lc3NhZ2Ugbm90IG9ubHkg
dG8gU2VydmVyCiAgICAgICAgQiAoZm9yIEJvYikgYnV0IGFsc28gdG8gU2VydmVycyBDLCBELCBF
LCBldGMuIGZvciBvdGhlciB1c2Vycy4gSW4gc3VjaAogICAgICAgIGNhc2VzLCB0byBhdm9pZCB0
aGUgbXVsdGlwbGUgImRpYWwgYmFjayIgdHJhbnNhY3Rpb25zIGltcGxpZWQgYnkgdGhlCiAgICAg
ICAgYWJvdmUgbWVjaGFuaXNtLCBYTVBQIHN5c3RlbXMgd2lsbCBsaWtlbHkgY2FjaGUgcHVibGlj
IGtleXMgZm9yIGVuZAogICAgICAgIHJlY2lwaWVudHMsIHNvIHRoYXQgd3JhcHBlZCBrZXlzIGNh
biBiZSBzZW50IGFsb25nIHdpdGggY29udGVudCBvbgogICAgICAgIGZ1dHVyZSBtZXNzYWdlcy4g
VGhpcyBpbXBsaWVzIHRoYXQgdGhlIEpPU0UgZW5jcnlwdGVkIG9iamVjdCBmb3JtYXQKICAgICAg
ICBtdXN0IHN1cHBvcnQgdGhlIHByb3Zpc2lvbiBvZiBtdWx0aXBsZSB2ZXJzaW9ucyBvZiB0aGUg
c2FtZSB3cmFwcGVkCiAgICAgICAgQ0VLIChtdWNoIGFzIGEgQ01TIEVudmVsb3BlZERhdGEgc3Ry
dWN0dXJlIGNhbiBpbmNsdWRlIG11bHRpcGxlCiAgICAgICAgUmVjaXBpZW50SW5mbyBzdHJ1Y3R1
cmVzKS48L3Q+CgogICAgICAgIDx0PkluIHRoZSBjdXJyZW50IGRyYWZ0IG9mIHRoZSBYTVBQIGVu
ZC10by1lbmQgc2VjdXJpdHkgc3lzdGVtLCBlYWNoCiAgICAgICAgcGFydHkgaXMgYXV0aGVudGlj
YXRlZCBieSB2aXJ0dWUgb2YgdGhlIG90aGVyIHBhcnR5J3MgdHJ1c3QgaW4gdGhlCiAgICAgICAg
WE1QUCBtZXNzYWdlIHJvdXRpbmcgc3lzdGVtLiBUaGUgc2VuZGVyIGlzIGF1dGhlbnRpY2F0ZWQg
dG8gdGhlCiAgICAgICAgcmVjZWl2ZXIgYmVjYXVzZSBoZSBjYW4gcmVjZWl2ZSBtZXNzYWdlcyBm
b3IgdGhlIGlkZW50aWZpZXIgIkFsaWNlIgogICAgICAgIChpbiBwYXJ0aWN1bGFyLCB0aGUgcmVx
dWVzdCBmb3Igd3JhcHBlZCBrZXlzKSwgYW5kIGNhbiBvcmlnaW5hdGUKICAgICAgICBtZXNzYWdl
cyBmb3IgdGhhdCBpZGVudGlmaWVyICh0aGUgd3JhcHBlZCBrZXkpLiBMaWtld2lzZSwgdGhlIHJl
Y2VpdmVyCiAgICAgICAgaXMgYXV0aGVudGljYXRlZCB0byB0aGUgc2VuZGVyIGJlY2F1c2UgaGUg
cmVjZWl2ZWQgdGhlIG9yaWdpbmFsCiAgICAgICAgZW5jcnlwdGVkIG1lc3NhZ2UgYW5kIG9yaWdp
bmF0ZWQgdGhlIHJlcXVlc3QgZm9yIHdyYXBwZWQga2V5LiBTbyB0aGUKICAgICAgICBhdXRoZW50
aWNhdGlvbiBoZXJlIHJlcXVpcmVzIG5vdCBvbmx5IHRoYXQgWE1QUCByb3V0aW5nIGJlIGRvbmUK
ICAgICAgICBwcm9wZXJseSwgYnV0IGFsc28gdGhhdCBUTFMgYmUgdXNlZCBvbiBldmVyeSBob3Au
IE1vcmVvdmVyLCBpdAogICAgICAgIHJlcXVpcmVzIHRoYXQgdGhlIFRMUyBjaGFubmVscyBoYXZl
IHN0cm9uZyBhdXRoZW50aWNhdGlvbiwgc2luY2UgYSBtYW4KICAgICAgICBpbiB0aGUgbWlkZGxl
IG9uIGFueSBvZiB0aGUgdGhyZWUgaG9wcyBjYW4gbWFzcXVlcmFkZSBhcyBCb2IgYW5kCiAgICAg
ICAgb2J0YWluIHRoZSBrZXkgbWF0ZXJpYWwgZm9yIGFuIGVuY3J5cHRlZCBtZXNzYWdlLjwvdD4K
CiAgICAgICAgPHQ+QmVjYXVzZSB0aGlzIGF1dGhlbnRpY2F0aW9uIGlzIHF1aXRlIHdlYWsgKGRl
cGVuZGluZyBvbiB0aGUgdXNlIG9mCiAgICAgICAgdHJhbnNwb3J0LWxheWVyIHNlY3VyaXR5IG9u
IHRocmVlIGhvcHMpIGFuZCB1bnZlcmlmaWFibGUgYnkgdGhlCiAgICAgICAgZW5kcG9pbnRzLCBp
dCBpcyBwb3NzaWJsZSB0aGF0IHRoZSBYTVBQIHdvcmtpbmcgZ3JvdXAgd2lsbCBpbnRlZ3JhdGUK
ICAgICAgICBzb21lIHNvcnQgb2YgY3JlZGVudGlhbHMgZm9yIGVuZCByZWNpcGllbnRzLCBpbiB3
aGljaCBjYXNlIHRoZXJlIHdvdWxkCiAgICAgICAgbmVlZCB0byBiZSBhIHdheSB0byBhc3NvY2lh
dGUgdGhlc2UgY3JlZGVudGlhbHMgd2l0aCBKT1NFIG9iamVjdHMuPC90PgoKICAgICAgICA8dD5G
aW5hbGx5LCBpdCdzIHdvcnRoIG5vdGluZyB0aGF0IFhNUFAgaXMgYmFzZWQgb24gWE1MLCBub3Qg
SlNPTi4gU28KICAgICAgICBieSB1c2luZyBKT1NFLCBYTVBQIHdpbGwgYmUgY2FycnlpbmcgSlNP
TiBvYmplY3RzIHdpdGhpbiBYTUwuIEl0IGlzCiAgICAgICAgdGh1cyBhIGRlc2lyYWJsZSBwcm9w
ZXJ0eSBmb3IgSk9TRSBvYmplY3RzIHRvIGJlIGVuY29kZWQgaW4gc3VjaCBhIHdheQogICAgICAg
IGFzIHRvIGJlIHNhZmUgZm9yIGluY2x1c2lvbiBpbiBYTUwuIE90aGVyd2lzZSwgYW4gZXhwbGlj
aXQgQ0RBVEEKICAgICAgICBpbmRpY2F0aW9uIG11c3QgYmUgZ2l2ZW4gdG8gdGhlIHBhcnNlciB0
byBpbmRpY2F0ZSB0aGF0IGl0IGlzIG5vdCB0bwogICAgICAgIGJlIHBhcnNlZCBhcyBYTUwuIE9u
ZSB3YXkgdG8gbWVldCB0aGlzIHJlcXVpcmVtZW50IHdvdWxkIGJlIHRvIGFwcGx5CiAgICAgICAg
YmFzZTY0dXJsIGVuY29kaW5nLCBidXQgZm9yIFhNUFAgbWVzc2FnZXMgb2YgbWVkaXVtLXRvLWxh
cmdlIHNpemUsCiAgICAgICAgdGhpcyBjb3VsZCBpbXBvc2UgYSBmYWlyIGRlZ3JlZSBvZiBvdmVy
aGVhZC48L3Q+CiAgICAgIDwvc2VjdGlvbj4KCiAgICAgIDxzZWN0aW9uIGFuY2hvcj0iYWx0by1z
ZWMiIHRpdGxlPSJBTFRPIj4KICAgICAgICA8dD5BcHBsaWNhdGlvbi1MYXllciBUcmFmZmljIE9w
dGltaXphdGlvbiAoQUxUTykgaXMgYSBzeXN0ZW0gZm9yCiAgICAgICAgZGlzdHJpYnV0aW5nIG5l
dHdvcmsgdG9wb2xvZ3kgaW5mb3JtYXRpb24gdG8gZW5kIGRldmljZXMsIHNvIHRoYXQKICAgICAg
ICB0aG9zZSBkZXZpY2VzIGNhbiBtb2RpZnkgdGhlaXIgYmVoYXZpb3IgdG8gaGF2ZSBhIGxvd2Vy
IGltcGFjdCBvbiB0aGUKICAgICAgICBuZXR3b3JrIDx4cmVmIHRhcmdldD0iUkZDNjcwOCIvPi4g
VGhlIEFMVE8gcHJvdG9jb2wKICAgICAgICBkaXN0cmlidXRlcyB0b3BvbG9neSBpbmZvcm1hdGlv
biBpbiB0aGUgZm9ybSBvZiBKU09OIG9iamVjdHMgY2FycmllZAogICAgICAgIGluIEhUVFAgPHhy
ZWYgdGFyZ2V0PSJSRkMyNjE2Ii8+PHhyZWYKICAgICAgICB0YXJnZXQ9IkktRC5pZXRmLWFsdG8t
cHJvdG9jb2wiLz4uIFRoZSBiYXNpYyB2ZXJzaW9uIG9mIEFMVE8gaXMgc2ltcGx5CiAgICAgICAg
YSBjbGllbnQtc2VydmVyIHByb3RvY29sLCBzbyBzaW1wbGUgdXNlIG9mIEhUVFBTIHN1ZmZpY2Vz
IGZvciB0aGlzCiAgICAgICAgY2FzZSA8eHJlZiB0YXJnZXQ9IlJGQzI4MTgiLz4uIEhvd2V2ZXIs
IHRoZXJlIGlzIGJlZ2lubmluZyB0byBiZSBzb21lCiAgICAgICAgZGlzY3Vzc2lvbiBvZiB1c2Ug
Y2FzZXMgZm9yIEFMVE8gaW4gd2hpY2ggdGhlc2UgSlNPTiBvYmplY3RzIHdpbGwgYmUKICAgICAg
ICBkaXN0cmlidXRlZCB0aHJvdWdoIGEgY29sbGVjdGlvbiBvZiBpbnRlcm1lZGlhdGUgc2VydmVy
cyBiZWZvcmUKICAgICAgICByZWFjaGluZyB0aGUgY2xpZW50LCB3aGlsZSBzdGlsbCBwcmVzZXJ2
aW5nIHRoZSBhYmlsaXR5IG9mIHRoZSBjbGllbnQKICAgICAgICB0byBhdXRoZW50aWNhdGUgdGhl
IG9yaWdpbmFsIHNvdXJjZSBvZiB0aGUgb2JqZWN0LiBFdmVuIHRoZSBiYXNlIEFMVE8KICAgICAg
ICBwcm90b2NvbCBub3RlcyB0aGF0ICJBTFRPIGNsaWVudHMgb2J0YWluaW5nIEFMVE8gaW5mb3Jt
YXRpb24gbXVzdCBiZQogICAgICAgIGFibGUgdG8gdmFsaWRhdGUgdGhlIHJlY2VpdmVkIEFMVE8g
aW5mb3JtYXRpb24gdG8gZW5zdXJlIHRoYXQgaXQgd2FzCiAgICAgICAgZ2VuZXJhdGVkIGJ5IGFu
IGFwcHJvcHJpYXRlIEFMVE8gc2VydmVyLiI8L3Q+CgogICAgICAgIDx0PkluIHRoaXMgY2FzZSwg
dGhlIHNlY3VyaXR5IHJlcXVpcmVtZW50cyBhcmUgc3RyYWlnaHRmb3J3YXJkLiBKT1NFCiAgICAg
ICAgb2JqZWN0cyBjYXJyeWluZyBBTFRPIHBheWxvYWRzIHdpbGwgbmVlZCB0byBiZWFyIGRpZ2l0
YWwgc2lnbmF0dXJlcwogICAgICAgIGZyb20gdGhlIG9yaWdpbmF0aW5nIHNlcnZlcnMsIHdoaWNo
IHdpbGwgYmUgYm91bmQgdG8gY2VydGlmaWNhdGVzCiAgICAgICAgYXR0ZXN0aW5nIHRvIHRoZSBp
ZGVudGl0aWVzIG9mIHRoZSBzZXJ2ZXJzLiBUaGVyZSBpcyBubyByZXF1aXJlbWVudAogICAgICAg
IGZvciBjb25maWRlbnRpYWxpdHkgaW4gdGhpcyBjYXNlLCBzaW5jZSBBTFRPIGluZm9ybWF0aW9u
IGlzIGdlbmVyYWxseQogICAgICAgIHB1YmxpYy48L3Q+CgogICAgICAgIDx0PlRoZSBtb3JlIGlu
dGVyZXN0aW5nIHF1ZXN0aW9ucyBhcmUgZW5jb2RpbmcgcXVlc3Rpb25zLiBBTFRPIG9iamVjdHMK
ICAgICAgICBhcmUgbGlrZWx5IHRvIGJlIG11Y2ggbGFyZ2VyIHRoYW4gcGF5bG9hZHMgaW4gdGhl
IHR3byBjYXNlcyBhYm92ZSwKICAgICAgICB3aXRoIHNpemVzIG9mIHVwIHRvIHNldmVyYWwgbWVn
YWJ5dGVzLiBQcm9jZXNzaW5nIG9mIHN1Y2ggbGFyZ2UKICAgICAgICBvYmplY3RzIGNhbiBiZSBk
b25lIG1vcmUgcXVpY2tseSBpZiBpdCBjYW4gYmUgZG9uZSBpbiBhIHNpbmdsZSBwYXNzLAogICAg
ICAgIHdoaWNoIG1heSBiZSBwb3NzaWJsZSBpZiBKT1NFIG9iamVjdHMgcmVxdWlyZSBzcGVjaWZp
YyBvcmRlcmluZ3Mgb2YKICAgICAgICBmaWVsZHMgd2l0aGluIHRoZSBKU09OIHN0cnVjdHVyZS48
L3Q+CgogICAgICAgIDx0PkluIGFkZGl0aW9uLCBiZWNhdXNlIEFMVE8gb2JqZWN0cyBhcmUgYWxz
byBlbmNvZGVkIGFzIEpTT04sIHRoZXkKICAgICAgICBhcmUgYWxyZWFkeSBzYWZlIGZvciBpbmNs
dXNpb24gaW4gYSBKT1NFIG9iamVjdC4gU2lnbmVkIEpPU0Ugb2JqZWN0cwogICAgICAgIHdpbGwg
bGlrZWx5IGNhcnJ5IHRoZSBzaWduZWQgZGF0YSBpbiBhIHN0cmluZyBhbG9uZ3NpZGUgdGhlIHNp
Z25hdHVyZS4KICAgICAgICBKU09OIG9iamVjdHMgaGF2ZSB0aGUgcHJvcGVydHkgdGhhdCB0aGV5
IGNhbiBiZSBzYWZlbHkgZW5jb2RlZCBpbiBKU09OCiAgICAgICAgc3RyaW5ncy4gQWxsIHRoZXkg
cmVxdWlyZSBpcyB0aGF0IHVubmVjZXNzYXJ5IHdoaXRlIHNwYWNlIGJlIHJlbW92ZWQsCiAgICAg
ICAgYSBtdWNoIHNpbXBsZXIgdHJhbnNmb3JtYXRpb24gdGhhbiwgc2F5IGJhc2U2NHVybCBlbmNv
ZGluZy4gVGhpcwogICAgICAgIHJhaXNlcyB0aGUgcXVlc3Rpb24gb2Ygd2hldGhlciBpdCBtaWdo
dCBiZSBwb3NzaWJsZSB0byBvcHRpbWl6ZSB0aGUKICAgICAgICBKT1NFIGVuY29kaW5nIGZvciBj
ZXJ0YWluICJKU09OLXNhZmUiIGNhc2VzLjwvdD4KICAgICAgPC9zZWN0aW9uPgoKICAgICAgPHNl
Y3Rpb24gYW5jaG9yPSJhdG9jYS1zZWMiIHRpdGxlPSJFbWVyZ2VuY3kgQWxlcnRpbmciPgogICAg
ICAgIDx0PkVtZXJnZW5jeSBhbGVydGluZyBpcyBhbiBlbWVyZ2luZyB1c2UgY2FzZSBmb3IgSVAg
bmV0d29ya3MgPHhyZWYKICAgICAgICB0YXJnZXQ9IkktRC5pZXRmLWF0b2NhLXJlcXVpcmVtZW50
cyIvPi4gQWxlcnRpbmcgc3lzdGVtcyBhbGxvdwogICAgICAgIGF1dGhvcml0aWVzIHRvIHdhcm4g
dXNlcnMgb2YgaW1wZW5kaW5nIGRhbmdlciBieSBzZW5kaW5nIGFsZXJ0CiAgICAgICAgbWVzc2Fn
ZXMgdG8gY29ubmVjdGVkIGRldmljZXMuIEZvciBleGFtcGxlLCBpbiB0aGUgZXZlbnQgb2YgaHVy
cmljYW5lCiAgICAgICAgb3IgdG9ybmFkbywgYWxlcnRzIG1pZ2h0IGJlIHNlbnQgdG8gYWxsIGRl
dmljZXMgaW4gdGhlIHBhdGggb2YgdGhlCiAgICAgICAgc3Rvcm0uPC90PgoKICAgICAgICA8dD5U
aGUgbW9zdCBjcml0aWNhbCBzZWN1cml0eSByZXF1aXJlbWVudCBmb3IgYWxlcnRpbmcgc3lzdGVt
cyBpcyB0aGF0CiAgICAgICAgaXQgbXVzdCBub3QgYmUgcG9zc2libGUgZm9yIGFuIGF0dGFja2Vy
IHRvIHNlbmQgZmFsc2UgYWxlcnRzIHRvCiAgICAgICAgZGV2aWNlcy4gU3VjaCBhIGNhcGFiaWxp
dHkgd291bGQgcG90ZW50aWFsbHkgYWxsb3cgYW4gYXR0YWNrZXIgdG8KICAgICAgICBjcmVhdGUg
d2lkZS1zcHJlYWQgcGFuaWMuIEluIHByYWN0aWNlLCBhbGVydCBzeXN0ZW1zIHByZXZlbnQgdGhl
c2UKICAgICAgICBhdHRhY2tzIGJvdGggYnkgY29udHJvbHMgb24gc2VuZGluZyBtZXNzYWdlcyBh
dCBwb2ludHMgd2hlcmUgYWxlcnRzCiAgICAgICAgYXJlIG9yaWdpbmF0ZWQsIGFzIHdlbGwgYXMg
YnkgaGF2aW5nIHJlY2lwaWVudHMgb2YgYWxlcnRzIHZlcmlmeSB0aGF0CiAgICAgICAgdGhlIGFs
ZXJ0IHdhcyBzZW50IGJ5IGFuIGF1dGhvcml6ZWQgc291cmNlLiBUaGUgZm9ybWVyIHR5cGUgb2Yg
Y29udHJvbAogICAgICAgIGltcGxlbWVudGVkIHdpdGggbG9jYWwgc2VjdXJpdHkgb24gaG9zdHMg
ZnJvbSB3aGljaCBhbGVydHMgY2FuIGJlCiAgICAgICAgb3JpZ2luYXRlZC4gVGhlIGxhdHRlciB0
eXBlIGltcGxlbWVudGVkIGJ5IGRpZ2l0YWwgc2lnbmF0dXJlcyBvbiBhbGVydAogICAgICAgIG1l
c3NhZ2VzICh1c2luZyBjaGFubmVsLWJhc2VkIG9yIG9iamVjdC1iYXNlZCBtZWNoYW5pc21zKS48
L3Q+CgogICAgICAgIDx0PkFsZXJ0cyB0eXBpY2FsbHkgcmVhY2ggZW5kIHJlY2lwaWVudHMgdmlh
IGEgc2VyaWVzIG9mCiAgICAgICAgaW50ZXJtZWRpYXJpZXMuIEZvciBleGFtcGxlLCB3aGlsZSBh
IG5hdGlvbmFsIHdlYXRoZXIgc2VydmljZSBtaWdodAogICAgICAgIG9yaWdpbmF0ZSBhIGh1cnJp
Y2FuZSBhbGVydCwgaXQgbWlnaHQgZmlyc3QgYmUgZGVsaXZlcmVkIHRvIGEgbmF0aW9uYWwKICAg
ICAgICBnYXRld2F5LCBhbmQgdGhlbiB0byBuZXR3b3JrIG9wZXJhdG9ycywgd2hvIGJyb2FkY2Fz
dCBpdCB0byBlbmQKICAgICAgICBzdWJzY3JpYmVycy48L3Q+CgogICAgICAgIDx0PjxmaWd1cmUg
YW5jaG9yPSJmaWctYXRvY2Etc2VjIgogICAgICAgICAgICB0aXRsZT0iRGVsaXZlcmluZyBhbiBl
bWVyZ2VuY3kgYWxlcnQiPgogICAgICAgICAgICA8YXJ0d29yaz48IVtDREFUQVsgICAgICAgICst
LS0tLS0tLS0tLS0rICAgICstLS0tLS0tLS0tLS0rICAgICstLS0tLS0tLS0tLS0rCiAgICAgICAg
fCBPcmlnaW5hdG9yIHwgICAgfCBPcmlnaW5hdG9yIHwgICAgfCBPcmlnaW5hdG9yIHwKICAgICAg
ICArLS0tLS0tLS0tLS0tKyAgICArLS0tLS0tLS0tLS0tKyAgICArLS0tLS0tLS0tLS0tKwogICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgIC4gICAgICAgICAgICAgICAgIC4gICAgICAgCiAg
ICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tKy4uLi4uLi4uLi4uLi4uLi4uLiAgICAgICAK
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAg
IAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAgICAgICAg
ICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0rICAgICAgICAgICAgICAg
ICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBHYXRld2F5IHwgICAgICAgICAgICAg
ICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tKyAgICAgICAgICAg
ICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAg
ICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0t
KyAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICBWICAgICAgICAgICAgICAgICAgICAg
ICAgIFYgICAgICAgICAgICAKICAgICAgICAgICAgICArLS0tLS0tLS0tKyAgICAgICAgICAgICAg
ICstLS0tLS0tLS0rICAgICAgIAogICAgICAgICAgICAgIHwgTmV0d29yayB8ICAgICAgICAgICAg
ICAgfCBOZXR3b3JrIHwgICAgICAgCiAgICAgICAgICAgICAgKy0tLS0tLS0tLSsgICAgICAgICAg
ICAgICArLS0tLS0tLS0tKyAgICAgICAKICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAg
ICAgICAgICAgICAgfCAgICAgICAgICAgIAogICAgICAgICAgICArLS0tLS0tKy0tLS0tKyAgICAg
ICAgICAgICstLS0tLS0rLS0tLS0rICAgICAgCiAgICAgICAgICAgIHwgICAgICAgICAgICB8ICAg
ICAgICAgICAgfCAgICAgICAgICAgIHwgICAgICAKICAgICAgICAgICAgViAgICAgICAgICAgIFYg
ICAgICAgICAgICBWICAgICAgICAgICAgViAgICAgIAogICAgICAgICstLS0tLS0tLSsgICArLS0t
LS0tLS0rICAgKy0tLS0tLS0tKyAgICstLS0tLS0tLSsgCiAgICAgICAgfCBEZXZpY2UgfCAgIHwg
RGV2aWNlIHwgICB8IERldmljZSB8ICAgfCBEZXZpY2UgfCAKICAgICAgICArLS0tLS0tLS0rICAg
Ky0tLS0tLS0tKyAgICstLS0tLS0tLSsgICArLS0tLS0tLS0rIAoKXV0+PC9hcnR3b3JrPgogICAg
ICAgICAgPC9maWd1cmU+PC90PgoKICAgICAgICA8dD5JbiBvcmRlciB0byB2ZXJpZnkgYWxlcnQg
c2lnbmF0dXJlcywgcmVjaXBpZW50cyBtdXN0IGJlIHByb3Zpc2lvbmVkCiAgICAgICAgd2l0aCB0
aGUgcHJvcGVyIHB1YmxpYyBrZXlzIGZvciB0cnVzdGVkIGFsZXJ0IGF1dGhvcml0aWVzLiBUaGlz
IHRydXN0CiAgICAgICAgbWF5IGJlICJwaWVjZS13aXNlIiBhbG9uZyB0aGUgcGF0aCB0aGUgYWxl
cnQgdGFrZXMuIEZvciBleGFtcGxlLCB0aGUKICAgICAgICBhbGVydCByZWxheXMgb3BlcmF0ZWQg
YnkgbmV0d29ya3MgbWlnaHQgaGF2ZSBhIGZ1bGwgc2V0IG9mCiAgICAgICAgY2VydGlmaWNhdGVz
IGZvciBhbGwgYWxlcnQgb3JpZ2luYXRvcnMsIHdoaWxlIGVuZCBkZXZpY2VzIG1heSBvbmx5CiAg
ICAgICAgdHJ1c3QgdGhlaXIgbG9jYWwgYWxlcnQgcmVsYXkuIE9yIGRldmljZXMgbWlnaHQgcmVx
dWlyZSB0aGF0IGEgZGV2aWNlCiAgICAgICAgYmUgc2lnbmVkIGJ5IGFuIGF1dGhvcml6ZWQgb3Jp
Z2luYXRvciBhbmQgYnkgaXRzIGxvY2FsIG5ldHdvcmsncwogICAgICAgIHJlbGF5LjwvdD4KCiAg
ICAgICAgPHQ+VGhpcyBzY2VuYXJpbyBjcmVhdGVzIGEgbmVlZCBmb3IgbXVsdGlwbGUgc2lnbmF0
dXJlcyBvbiBhbGVydAogICAgICAgIGRvY3VtZW50cywgc28gdGhhdCBhbiBhbGVydCBjYW4gYmVh
ciBzaWduYXR1cmVzIGZyb20gYW55IG9yIGFsbCBvZiB0aGUKICAgICAgICBlbnRpdGllcyB0aGF0
IHByb2Nlc3NlZCBpdCBhbG9uZyB0aGUgcGF0aC4gSW4gb3JkZXIgdG8gbWluaW1pemUKICAgICAg
ICBjb21wbGV4aXR5LCB0aGVzZSBzaWduYXR1cmVzIHNob3VsZCBiZSAibW9kdWxhciIsIGluIHRo
ZSBzZW5zZSB0aGF0IGEKICAgICAgICBuZXcgc2lnbmF0dXJlIGNhbiBiZSBhZGRlZCB3aXRob3V0
IGEgbmVlZCB0byBhbHRlciBvciByZWNvbXB1dGUKICAgICAgICBwcmV2aW91cyBzaWduYXR1cmVz
LjwvdD4KICAgICAgPC9zZWN0aW9uPgoKICAgICAgPHNlY3Rpb24gYW5jaG9yPSJ3ZWJjcnlwdG8t
c2VjIiB0aXRsZT0iV2ViIENyeXB0b2dyYXBoeSI+CiAgICAgIDx0PlRoZSBXM0MgV2ViIENyeXB0
b2dyYXBoeSBBUEkgZGVmaW5lcyBhIHN0YW5kYXJkIGNyeXB0b2dyYXBoaWMgQVBJIGZvciB0aGUK
ICAgICAgV2ViIDx4cmVmIHRhcmdldD0iV2ViQ3J5cHRvIj48L3hyZWY+LiAgSWYgYSBicm93c2Vy
IGV4cG9zZXMgdGhpcyBBUEksIHRoZW4gCiAgICAgIEphdmFTY3JpcHQgcHJvdmlkZWQgYXMgcGFy
dCBvZiBhIFdlYiBwYWdlIGNhbiBhc2sgdGhlIGJyb3dzZXIgdG8gcGVyZm9ybSAKICAgICAgY3J5
cHRvZ3JhcGhpYyBvcGVyYXRpb25zLCBzdWNoIGFzIGRpZ2VzdCwgTUFDLCBlbmNyeXB0aW9uLCBv
ciBkaWdpdGFsIHNpZ25pbmcuPC90PgoKICAgICAgPHQ+T25lIG9mIHRoZSBrZXkgcmVhc29ucyB0
byBoYXZlIHRoZSBicm93c2VyIHBlcmZvcm0gY3J5cHRvZ3JhcGhpYyBvcGVyYXRpb25zICAKICAg
ICAgaXMgdG8gYXZvaWQgYWxsb3dpbmcgSmF2YVNjcmlwdCBjb2RlIHRvIGFjY2VzcyB0aGUga2V5
aW5nIG1hdGVyaWFsIHVzZWQgZm9yIHRoZXNlCiAgICAgIG9wZXJhdGlvbnMuICBGb3IgZXhhbXBs
ZSwgdGhpcyBzZXBhcmF0aW9uIHdvdWxkIHByZXZlbnQgY29kZSBpbmplY3RlZCB0aHJvdWdoIGEK
ICAgICAgY3Jvc3Mtc2l0ZSBzY3JpcHRpbmcgKFhTUykgYXR0YWNrIGZyb20gcmVhZGluZyBhbmQg
ZXhmaWx0cmF0aW5nIGtleXMgc3RvcmVkIAogICAgICB3aXRoaW4gYSBicm93c2VyLiAgV2hpbGUg
dGhlIG1hbGljaW91cyBjb2RlIGNvdWxkIHN0aWxsIHVzZSB0aGUga2V5IHdoaWxlIHJ1bm5pbmcK
ICAgICAgaW4gdGhlIGJyb3dzZXIsIHRoaXMgdnVsbmVyYWJpbGl0eSBjYW4gb25seSBiZSBleGVy
Y2lzZWQgd2hpbGUgdGhlIHZ1bG5lcmFibGUKICAgICAgcGFnZSBpcyBhY3RpdmUgaW4gYSB1c2Vy
J3MgYnJvd3Nlci48L3Q+CgogICAgICA8dD5Ib3dldmVyLCB0aGUgV2ViQ3J5cHRvZ3JhcGh5IEFQ
SSBhbHNvIHByb3ZpZGVzIGEga2V5IGV4cG9ydCBmdW5jdGlvbmFsaXR5LCAKICAgICAgd2hpY2gg
Y2FuIGFsbG93IEphdmFTY3JpcHQgdG8gZXh0cmFjdCBhIGtleSBmcm9tIHRoZSBBUEkgaW4gd3Jh
cHBlZCBmb3JtLiAgRm9yCiAgICAgIGV4YW1wbGUsIHRoZSBKYXZhU2NyaXB0IG1pZ2h0IHByb3Zp
ZGUgYSBwdWJsaWMga2V5IGZvciB3aGljaCB0aGUgY29ycmVzcG9uZGluZwogICAgICBwcml2YXRl
IGtleSBpcyBoZWxkIGJ5IGFub3RoZXIgZGV2aWNlLiAgVGhlIHdyYXBwZWQga2V5IHByb3ZpZGVk
IGJ5IHRoZSBBUEkgCiAgICAgIGNvdWxkIHRoZW4gYmUgdXNlZCB0byBzYWZlbHkgdHJhbnNwb3J0
IHRoZSBrZXkgdG8gdGhlIG5ldyBkZXZpY2UuICBXaGlsZSB0aGlzCiAgICAgIGNvdWxkIHBvdGVu
dGlhbGx5IGFsbG93IG1hbGljaW91cyBjb2RlIHRvIGV4cG9ydCBhIGtleSwgdGhlIG5lZWQgZm9y
IGFuIGV4cGxpY2l0CiAgICAgIGV4cG9ydCBvcGVyYXRpb24gcHJvdmlkZXMgYSBjb250cm9sIHBv
aW50LCBhbGxvd2luZyBmb3IgdXNlciBub3RpZmljYXRpb24gb3IKICAgICAgY29uc2VudCB2ZXJp
ZmljYXRpb24uPC90PgoKICAgICAgPHQ+VGhlIFdlYiBDcnlwdG9ncmFwaHkgQVBJIGFsc28gYWxs
b3dzIGJyb3dzZXJzIHRvIGltcG9zZSBsaW1pdGF0aW9ucyBvbiB0aGUgCiAgICAgIHVzYWdlIG9m
IHRoZSBrZXlzIGl0IGhhbmRsZXMuICBGb3IgZXhhbXBsZSwgYSBzeW1tZXRyaWMga2V5IG1pZ2h0
IGJlIG1hcmtlZCBhcyAKICAgICAgdXNhYmxlIG9ubHkgZm9yIGVuY3J5cHRpb24sIGFuZCBub3Qg
Zm9yIE1BQy4gIFdoZW4gYSBrZXkgaXMgZXhwb3J0ZWQgaW4gd3JhcHBlZCAKICAgICAgZm9ybSwg
dGhlc2UgYXR0cmlidXRlcyBzaG91bGQgYmUgY2FycmllZCBhbG9uZyB3aXRoIGl0LjwvdD4KCiAg
ICAgIDx0PlRoZSBXZWIgQ3J5cHRvZ3JhcGh5IEFQSSB0aHVzIHJlcXVpcmVzIGZvcm1hdHMgdG8g
ZXhwcmVzcyBzZXZlcmFsIGZvcm1zIG9mCiAgICAgIGtleXMuICBPYnZpb3VzbHksIHRoZSBwdWJs
aWMga2V5IGZyb20gYW4gYXN5bW1ldHJpYyBrZXkgcGFpciBjYW4gYmUgZnJlZWx5IAogICAgICBp
bXBvcnRlZCB0byBhbmQgZXhwb3J0ZWQgZnJvbSB0aGUgYnJvd3Nlciwgc28gdGhlcmUgbmVlZHMg
dG8gYmUgYSBmb3JtYXQgZm9yCiAgICAgIHB1YmxpYyBrZXlzLiAgVGhlcmUgaXMgYWxzbyBhIG5l
ZWQgZm9yIGEgZm9ybWF0IHRvIGV4cHJlc3MgcHJpdmF0ZSBrZXlzIGFuZAogICAgICBzeW1tZXRy
aWMga2V5cy4gIEZvciBub24tcHVibGljIGtleXMsIHRoZSBwcmltYXJ5IG5lZWQgaXMgZm9yIGEg
d3JhcHBlZCBmb3JtLAogICAgICB3aGVyZSB0aGUgY29uZmlkZW50aWFsaXR5IGFuZCBpbnRlZ3Jp
dHkgb2YgdGhlIGtleSBpcyBhc3N1cmVkIGNyeXB0b2dyYXBoaWNhbGx5OwogICAgICB0aGVzZSBw
cm90ZWN0aW9ucyBzaG91bGQgYWxzbyBhcHBseSB0byBhbnkgYXR0cmlidXRlcyBvZiB0aGUga2V5
LiAgSXQgbWF5IGFsc28KICAgICAgYmUgdXNlZnVsIHRvIGRlZmluZSBhIGRpcmVjdCwgdW53cmFw
cGVkIGZvcm1hdCwgZm9yIHVzZSB3aXRoaW4gYSBzZWN1cml0eSAKICAgICAgYm91bmRhcnkuPC90
PgogICAgICA8L3NlY3Rpb24+CgogICAgICAgPHNlY3Rpb24gdGl0bGU9IlNtYWxsIERldmljZXMi
PgogICAgPHQ+CiAgICAgIEEgc21hbGwsIGxvdyBwb3dlciBkZXZpY2UgbWFrZXIgaGFzIGRlY2lk
ZWQgb24gdXNpbmcgdGhlIG91dHB1dCBvZiB0aGUgSk9TRSB3b3JraW5nIGdyb3VwIGFzIHRoZWly
IGVuY3J5cHRpb24gYW5kIGF1dGhlbnRpY2F0aW9uIGZyYW1ld29yay4KICAgICAgVGhlIGRldmlj
ZSBtYWtlciBoYXMgYSBsaW1pdGVkIGF2YWlsYWJpbGl0eSBvZiBib3RoIHJlYWwgZXN0YXRlIGZv
ciBnYXRlcyBhbmQgcG93ZXIuCiAgICAgIEZvciB0aGlzIHJlYXNvbiB0aGVyZSBhcmUgYSBudW1i
ZXIgb2Ygc2hvcnQgY3V0cyBhbmQgZGVzaWduIGRlY2lzaW9ucyB0aGF0IGhhdmUgYmVlbiBtYWRl
IGluIG9yZGVyIHRvIG1pbmltaXplIHRoZXNlIG5lZWRzLgogICAgPC90PgogCiAgICA8dD4KICAg
ICAgVGhlIGRlc2lnbiB0ZWFtIGhhcyBkZXRlcm1pbmVkIHRoYXQgdGhlIHVzZSBvZiBtZXNzYWdl
IGF1dGhlbnRpY2F0aW9uIGNvZGVzIChNQUMpIGlzIGdvaW5nIHRvIGJlIHN1ZmZpY2llbnQgdG8g
cHJvdmlkZSB0aGUgbmVjZXNzYXJ5IGF1dGhlbnRpY2F0aW9uLiAKICAgICAgSG93ZXZlciwgYWx0
aG91Z2ggYSBNQUMgaXMgZ29pbmcgdG8gYmUgdXNlZCwgdGhleSBkbyBub3Qgd2FudCB0byB1c2Ug
YSBzaW5nbGUgbG9uZyB0ZXJtIHNoYXJlZCBzZWNyZXQuCiAgICAgIEluc3RlYWQgdGhleSBoYXZl
IGFkb3B0ZWQgdGhlIGZvbGxvd2luZyBwcm9wb3NhbCBmb3IgY29tcHV0aW5nIGEgc2hhcmVkIHNl
Y3JldCB0aGF0IGNhbiBiZSB2YWxpZGF0ZWQ6CiAgICAgIDxsaXN0IHN0eWxlPSJzeW1ib2xzIj4K
ICAgICAgICA8dD4KICAgICAgICAgIEFuIEVsbGlwdGljLUN1cnZlIERpZmZpZS1IZWxsbWFuIChF
Q0RIKSBrZXkgaXMgZ2VuZXJhdGVkIGZvciB0aGUgZGV2aWNlIGF0IHRoZSB0aW1lIG9mIG1hbnVm
YWN0dXJpbmcuCiAgICAgICAgICAoT3IgYXMgcGFydCBvZiB0aGUgY29uZmlndXJhdGlvbiBwcm9j
ZXNzIGR1cmluZyBpbnN0YWxsYXRpb24uKQogICAgICAgIDwvdD4KICAgICAgICA8dD4KICAgICAg
ICAgIEFuIEVDREggcHVibGljIGtleSBmb3IgdGhlIGNvbnRyb2xsZXIgaXMgY29uZmlndXJlZCBh
dCB0aGUgdGltZSBvZiBjb25maWd1cmF0aW9uLgogICAgICAgIDwvdD4KICAgICAgICA8dD4KICAg
ICAgICAgIFRoZSBjb25maWd1cmF0aW9uIHN5c3RlbSBwZXJmb3JtcyB0aGUgZXhwb25lbnRpYXRp
b24gYW5kIGNvbmZpZ3VyZXMgdGhlIGRldmljZSB3aXRoIHRoZSByZXN1bHRpbmcgc2hhcmVkIHNl
Y3JldC4KICAgICAgICAgIFRoaXMgcHJvY2VzcyBlbGltaW5hdGVzIHRoZSBuZWVkIGZvciB0aGUg
ZGV2aWNlIHRvIGJlIGFibGUgdG8gcGVyZm9ybSB0aGUgcmVxdWlyZWQgZXhwb25lbnRpYXRpb24g
cHJvY2Vzc2luZy4KICAgICAgICAgIFRoZSBzZWN1cml0eSByZXF1aXJlbWVudHMgb24gcHJvdGVj
dGluZyB0aGlzIGNvbXB1dGVkIHNoYXJlZCBzZWNyZXQgYXJlIHRoZSBzYW1lIGFzIHRoZSByZXF1
aXJlbWVudHMgb24gcHJvdGVjdGluZyB0aGUgcHJpdmF0ZSBFQ0RIIGtleS4KICAgICAgICA8L3Q+
CiAgICAgICAgPHQ+CiAgICAgICAgICBBIGNvdW50ZXIgYW5kIGFuIGluY3JlbWVudCB2YWx1ZSBh
cmUgY29uZmlndXJlZCBvbnRvIHRoZSBkZXZpY2UuCiAgICAgICAgPC90PgogICAgICAgIDx0Pgog
ICAgICAgICAgV2hlbiBhIG1lc3NhZ2UgaXMgdG8gYmUgc2VudCBieSB0aGUgZGV2aWNlLCB0aGUg
Y291bnRlciBpcyBpbmNyZW1lbnRlZCBhbmQgYSBuZXcgTUFDIGtleSBpcyBjb21wdXRlZCBmcm9t
IHRoZSBFQ0RIIHNlY3JldCBhbmQgdGhlIGNvdW50ZXIgdmFsdWUuCiAgICAgICAgICBBIGN1c3Rv
bSBLZXkgRGVyaXZhdGlvbiBGdW5jdGlvbiAoS0RGKSBmdW5jdGlvbiBpcyB1c2VkIHdoZW4gaXMg
YmFzZWQgb24gdGhlIEFFUy1DQkMgaXMgdXNlZCB0byBkZXJpdmUgdGhlIHJlcXVpcmVkIE1BQyBr
ZXkuCiAgICAgICAgICBUaGUgTUFDIGtleSBpcyB0aGVuIHVzZWQgdG8gY29tcHV0ZSB0aGUgTUFD
IHZhbHVlIGZvciB0aGUgbWVzc2FnZS4KICAgICAgICA8L3Q+CiAgICAgIDwvbGlzdD4KIAogICAg
ICBJbiBhIHNpbWlsYXIgbWFubmVyIHRoZSBLREYgZnVuY3Rpb24gY2FuIHVzZWQgdG8gY29tcHV0
ZSBhbiBBRUFEIGFsZ29yaXRobSBrZXkgd2hlbiB0aGUgc3lzdGVtIG5lZWRzIHRvIHByb3ZpZGUg
Y29uZmlkZW50aWFsbHkgZm9yIHRoZSBtZXNzYWdlLgogICAgICBUaGUgY29udHJvbGxlciwgYmVp
bmcgYSBsYXJnZXIgZGV2aWNlIHdpbGwgcGVyZm9ybSB0aGUgZXhwb25lbnRpYXRpb24gc3RlcCBh
bmQgdXNlIGEgcmFuZG9tIG51bWJlciBnZW5lcmF0b3IgdG8gZ2VuZXJhdGUgdGhlIHNlbmRlciBu
b25jZSB2YWx1ZS4KICAgIDwvdD4KICA8L3NlY3Rpb24+CgogICAgPC9zZWN0aW9uPgoKICAgIDxz
ZWN0aW9uIGFuY2hvcj0icmVxLXNlYyIgdGl0bGU9IlJlcXVpcmVtZW50cyI+CiAgICAgIDx0PlRo
aXMgc2VjdGlvbiBzdW1tYXJpemVzIHRoZSByZXF1aXJlbWVudHMgZnJvbSB0aGUgYWJvdmUgdXNl
cyBjYXNlcywgYW5kCiAgICAgIGxpc3RzIGZ1cnRoZXIgcmVxdWlyZW1lbnRzIG5vdCBkaXJlY3Rs
eSBkZXJpdmVkIGZyb20gdGhlIGFib3ZlIHVzZSBjYXNlcy4KICAgICAgVGhlcmUgYXJlIGFsc28g
c29tZSBjb25zdHJhaW50cyB0aGF0IGFyZSBub3QgaGFyZCByZXF1aXJlbWVudHMsIGJ1dCB3aGlj
aAogICAgICBhcmUgc3RpbGwgZGVzaXJhYmxlIHByb3BlcnRpZXMgZm9yIHRoZSBKT1NFIHN5c3Rl
bSB0byBoYXZlLjwvdD4KCiAgICAgIDxzZWN0aW9uIGFuY2hvcj0iZnVuY3Rpb25hbC1zZWMiIHRp
dGxlPSJGdW5jdGlvbmFsIFJlcXVpcmVtZW50cyI+CiAgICAgICAgPHQ+PGxpc3Qgc3R5bGU9Imhh
bmdpbmciPgogICAgICAgICAgPHQgaGFuZ1RleHQ9IkYxIj5EZWZpbmUgZm9ybWF0cyBmb3Igc2Vj
dXJlIG9iamVjdHMgdGhhdCBwcm92aWRlIHRoZSBmb2xsb3dpbmcKICAgICAgICAgIHNlY3VyaXR5
IHByb3BlcnRpZXM6CiAgICAgICAgICAgIDxsaXN0IHN0eWxlPSJzeW1ib2xzIj4KICAgICAgICAg
ICAgPHQ+RGlnaXRhbCBzaWduYXR1cmUgKGludGVncml0eS9hdXRoZW50aWNhdGlvbiB1bmRlciBh
biBhc3ltbWV0cmljIGtleSBwYWlyKTwvdD4KICAgICAgICAgICAgPHQ+TWVzc2FnZSBhdXRoZW50
aWNhdGlvbiAoaW50ZWdyaXR5L2F1dGhlbnRpY2F0aW9uIHVuZGVyIGEgc3ltbWV0cmljIGtleSk8
L3Q+CiAgICAgICAgICAgIDx0PkVuY3J5cHRpb248L3Q+CiAgICAgICAgICAgIDx0PkF1dGhlbnRp
Y2F0ZWQgZW5jcnlwdGlvbjwvdD4KICAgICAgICAgICAgPC9saXN0PgogICAgICAgICAgVGhhdCBp
cywgdGhlIHNlY3VyZSBvYmplY3RzIGRlZmluZWQgYnkgdGhpcyB3b3JraW5nIGdyb3VwIHNob3Vs
ZCBwcm92aWRlIAogICAgICAgICAgZXF1aXZhbGVudCBzZWN1cml0eSBwcm9wZXJ0aWVzIHRvIHRo
ZSBDTVMgU2lnbmVkRGF0YSwgQXV0aGVudGljYXRlZERhdGEsIAogICAgICAgICAgRW52ZWxvcGVk
RGF0YSwgYW5kIEF1dGhFbnZlbG9wZWQgZGF0YSBvYmplY3RzIDx4cmVmIHRhcmdldD0iUkZDNTY1
MiI+PC94cmVmPgogICAgICAgICAgPHhyZWYgdGFyZ2V0PSJSRkM1MDgzIj48L3hyZWY+LjwvdD4K
ICAgICAgICAgIDx0IGhhbmdUZXh0PSJGMiI+RGVmaW5lIGEgZm9ybWF0IGZvciBwdWJsaWMga2V5
cyBhbmQgcHJpdmF0ZSBrZXlzIGZvciAKICAgICAgICAgIGFzeW1tZXRyaWMgY3J5cHRvZ3JhcGhp
YyBhbGdvcml0aG1zLCB3aXRoIGFzc29jaWF0ZWQgYXR0cmlidXRlcywgaW5jbHVkaW5nIGEKICAg
ICAgICAgIHdyYXBwZWQgZm9ybSBmb3IgcHJpdmF0ZSBrZXlzLjwvdD4KICAgICAgICAgIDx0IGhh
bmdUZXh0PSJGMyI+RGVmaW5lIGEgZm9ybWF0IGZvciBzeW1tZXRyaWMga2V5cyB3aXRoIGFzc29j
aWF0ZWQgYXR0cmlidXRlcywKICAgICAgICAgIGFsbG93aW5nIGZvciBib3RoIHdyYXBwZWQgYW5k
IHVud3JhcHBlZCBrZXlzLjwvdD4KICAgICAgICAgIDx0IGhhbmdUZXh0PSJGNCI+RGVmaW5lIEpT
T04gc2VyaWFsaXphdGlvbnMgZm9yIHRoZSBhYm92ZSBvYmplY3RzLiAgQW4gb2JqZWN0CiAgICAg
ICAgICBpbiB0aGlzIGVuY29kaW5nIG11c3QgYmUgdmFsaWQgYWNjb3JkaW5nIHRvIHRoZSBKU09O
IEFCTkYgc3ludGF4IAogICAgICAgICAgPHhyZWYgdGFyZ2V0PSJSRkM0NjI3Ij48L3hyZWY+PC90
PgogICAgICAgICAgPHQgaGFuZ1RleHQ9IkY1Ij5EZWZpbmUgY29tcGFjdCwgVVJMLXNhZmUgdGV4
dCBzZXJpYWxpemF0aW9ucyBmb3IgdGhlIGFib3ZlIAogICAgICAgICAgb2JqZWN0cy48L3Q+CiAg
ICAgICAgICA8dCBoYW5nVGV4dD0iRjYiPkFsbG93IGZvciBhdHRyaWJ1dGVzIGFzc29jaWF0ZWQg
dG8gd3JhcHBlZCBrZXlzIHRvIGJlIGJvdW5kIAogICAgICAgICAgdG8gdGhlbSBjcnlwdG9ncmFw
aGljYWxseTwvdD4KICAgICAgICAgIDx0IGhhbmdUZXh0PSJGNyI+QWxsb3cgZm9yIHdyYXBwZWQg
a2V5cyB0byBiZSBzZXBhcmF0ZWQgZnJvbSBhIHNlY3VyZSBvYmplY3QgCiAgICAgICAgICB0aGF0
IHVzZXMgYSBzeW1tZXRyaWMga2V5LiAgSW4gc3VjaCBjYXNlcywgY3J5cHRvZ3JhcGhpYyBjb21w
b25lbnRzIG9mIHRoZSAKICAgICAgICAgIHNlY3VyZSBvYmplY3Qgb3RoZXIgdGhhbiB0aGUgd3Jh
cHBlZCBrZXkgKGUuZy4sIGNpcGhlcnRleHQsIE1BQyB2YWx1ZXMpIG11c3QKICAgICAgICAgIGJl
IGluZGVwZW5kZW50IG9mIHRoZSB3cmFwcGVkIGZvcm0gb2YgdGhlIGtleS4gIEZvciBleGFtcGxl
LCBpZiBhbiBlbmNyeXB0ZWQKICAgICAgICAgIG9iamVjdCBpcyBwcmVwYXJlZCBmb3IgbXVsdGlw
bGUgcmVjaXBpZW50cywgdGhlbiBvbmx5IHRoZSB3cmFwcGVkIGtleSBtYXkgdmFyeSwKICAgICAg
ICAgIG5vdCB0aGUgY2lwaGVydGV4dC48L3Q+CiAgICAgICAgPC9saXN0PjwvdD4KICAgICAgPC9z
ZWN0aW9uPgogICAgICAKICAgICAgPHNlY3Rpb24gYW5jaG9yPSJzZWMtcmVxLXNlYyIgdGl0bGU9
IlNlY3VyaXR5IFJlcXVpcmVtZW50cyI+CiAgICAgICAgPHQ+PGxpc3Qgc3R5bGU9Imhhbmdpbmci
PgogICAgICAgIDx0IGhhbmdUZXh0PSJTMSI+UHJvdmlkZSBrZXkgbWFuYWdlbWVudCBmdW5jdGlv
bnMgZm9yIGVwaGVtZXJhbCBzeW1tZXRyaWMga2V5cywKICAgICAgICBpbmNsdWRpbmcgZW5jcnlw
dGlvbiBrZXlzIGFuZCBNQUMga2V5cy4gIEl0IHNob3VsZCBiZSBwb3NzaWJsZSB0byB1c2UgYW55
CiAgICAgICAgb2YgdGhlIGtleSBtYW5hZ2VtZW50IHRlY2huaXF1ZXMgcHJvdmlkZWQgaW4gQ01T
IDx4cmVmIHRhcmdldD0iUkZDNTY1MiI+PC94cmVmPjoKICAgICAgICAgIDxsaXN0IHN0eWxlPSJz
eW1ib2xzIj4KICAgICAgICAgICAgPHQ+S2V5IHRyYW5zcG9ydCAod3JhcHBpbmcgZm9yIGEgcHVi
bGljIGtleSk8L3Q+CiAgICAgICAgICAgIDx0PktleSBlbmNpcGhlcm1lbnQgKHdyYXBwaW5nIGZv
ciBhIHN5bW1ldHJpYyBrZXkpPC90PgogICAgICAgICAgICA8dD5LZXkgYWdyZWVtZW50ICh3cmFw
cGluZyBmb3IgYSBESCBwdWJsaWMga2V5KTwvdD4KICAgICAgICAgICAgPHQ+UGFzc3dvcmQtYmFz
ZWQgZW5jcnlwdGlvbiAod3JhcHBpbmcgdW5kZXIgYSBrZXkgZGVyaXZlZCBmcm9tIGEgcGFzc3dv
cmQpPC90PgogICAgICAgICAgPC9saXN0PgogICAgICAgIDwvdD4KCiAgICAgICAgPHQgaGFuZ1Rl
eHQ9IlMyIj5Vc2UgY3J5cHRvZ3JhcGhpYyBhbGdvcml0aG1zIGluIGEgbWFubmVyIGNvbXBhdGli
bGUgd2l0aAogICAgICAgIG1ham9yIHZhbGlkYXRpb24gcHJvY2Vzc2VzLiAgRm9yIGV4YW1wbGUs
IGlmIGEgRklQUyBzdGFuZGFyZCBhbGxvd3MgCiAgICAgICAgYWxnb3JpdGhtIEEgdG8gYmUgdXNl
ZCBmb3IgcHVycG9zZSBYIGJ1dCBub3QgcHVycG9zZSBZLCB0aGVuIEpPU0Ugc2hvdWxkCiAgICAg
ICAgbm90IHJlY29tbWVuZCB1c2luZyBhbGdvcml0aG0gQSBmb3IgcHVycG9zZSBZLjwvdD4KICAg
ICAgICAKICAgICAgICA8dCBoYW5nVGV4dD0iUzMiPlN1cHBvcnQgb3BlcmF0aW9uIHdpdGggb3Ig
d2l0aG91dCBwcmUtbmVnb3RpYXRpb24uICAKICAgICAgICBJdCBtdXN0IGJlIHBvc3NpYmxlIHRv
IGNyZWF0ZSBvciBwcm9jZXNzIHNlY3VyZSBvYmplY3RzIHdpdGhvdXQKICAgICAgICBhbnkgY29u
ZmlndXJhdGlvbiBiZXlvbmQga2V5IHByb3Zpc2lvbmluZy4gIElmIGl0IGlzIHBvc3NpYmxlIGZv
ciBrZXlzCiAgICAgICAgdG8gYmUgZGVyaXZlZCBmcm9tIGFwcGxpY2F0aW9uIGNvbnRleHQsIGl0
IG11c3QgYmUgcG9zc2libGUgZm9yIGEgcmVjaXBpZW50CiAgICAgICAgdG8gcmVjb2duaXplIHdo
ZW4gaXQgZG9lcyBub3QgaGF2ZSB0aGUgYXBwcm9wcmlhdGUga2V5IGluIHRoZSBjYXNlIHRoYXQg
dGhlIGFwcGxpY2F0aW9uIGRvZXMgbm90CglzcGVjaWZ5IHRoZSB1c2Ugb2YgYW5vdGhlciBtZWFu
cyBvciBjb252ZW50aW9uIHRvIGRldGVybWluZSB0aGUga2V5IHVzZWQuPC90PgogICAgICAgIDwv
bGlzdD48L3Q+CiAgICAgIDwvc2VjdGlvbj4KCiAgICAgIDxzZWN0aW9uIGFuY2hvcj0iZGVzaWRl
cmF0YS1zZWMiIHRpdGxlPSJEZXNpZGVyYXRhIj4KICAgICAgICA8dD48bGlzdCBzdHlsZT0iaGFu
Z2luZyI+CiAgICAgICAgICA8dCBoYW5nVGV4dD0iRDEiPk1heGltaXplIGNvbXBhdGliaWxpdHkg
d2l0aCB0aGUgVzNDIFdlYkNyeXB0byAKICAgICAgICAgIHNwZWNpZmljYXRpb25zLCBlLmcuLCBi
eSBjb29yZGluYXRpbmcgd2l0aCB0aGUgV2ViQ3J5cHRvIHdvcmtpbmcgZ3JvdXAKICAgICAgICAg
IHRvIGVuY291cmFnZSBhbGlnbm1lbnQgb2YgYWxnb3JpdGhtcyBhbmQgYWxnb3JpdGhtIGlkZW50
aWZpZXJzCgkgIHRvIHRoZSBleHRlbnQgdGhhdCBpdCBtYWtlcyBzZW5zZSBpbiB0aGUgc29tZXdo
YXQgZGlmZmVyZW50IFdlYkNyeXB0byBhbmQgSk9TRSBhcHBsaWNhdGlvbiBjb250ZXh0cy48L3Q+
CgogICAgICAgICAgPHQgaGFuZ1RleHQ9IkQyIj5Bdm9pZCBKU09OIGNhbm9uaWNhbGl6YXRpb24g
dG8gdGhlIGV4dGVudCBwb3NzaWJsZS4KCSAgVGhhdCBpcywgYWxsIG90aGVyIHRoaW5ncyBiZWlu
ZyBlcXVhbCwgdGVjaG5pcXVlcyB0aGF0IHJlbHkgCiAgICAgICAgICBvbiBmaXhpbmcgYSBzZXJp
YWxpemF0aW9uIG9mIGFuIG9iamVjdCAoZS5nLiwgYnkgYmFzZTY0dXJsIGVuY29kaW5nIGl0KSAK
ICAgICAgICAgIGFyZSBwcmVmZXJyZWQgb3ZlciB0aG9zZSB0aGF0IHJlcXVpcmUgY29udmVydGlu
ZyBhbiBvYmplY3QgdG8gYSAKICAgICAgICAgIGNhbm9uaWNhbCBmb3JtLjwvdD4KICAgICAgICA8
L2xpc3Q+PC90PgogICAgICA8L3NlY3Rpb24+CiAgICA8L3NlY3Rpb24+CgogICAgPHNlY3Rpb24g
YW5jaG9yPSJpYW5hLXNlYyIgdGl0bGU9IklBTkEgQ29uc2lkZXJhdGlvbnMiPgogICAgICA8dD5U
aGlzIGRvY3VtZW50IG1ha2VzIG5vIHJlcXVlc3Qgb2YgSUFOQS48L3Q+CiAgICA8L3NlY3Rpb24+
CgogICAgPHNlY3Rpb24gYW5jaG9yPSJzZWMtY29ucy1zZWMiIHRpdGxlPSJTZWN1cml0eSBDb25z
aWRlcmF0aW9ucyI+CiAgICAgIDx0PlRoZSBwcmltYXJ5IGZvY3VzIG9mIHRoaXMgZG9jdW1lbnQg
aXMgdGhlIHJlcXVpcmVtZW50cyBmb3IgYQogICAgICBKU09OLWJhc2VkIHNlY3VyZSBvYmplY3Qg
Zm9ybWF0LiBBdCB0aGUgbGV2ZWwgb2YgZ2VuZXJhbCBzZWN1cml0eQogICAgICBjb25zaWRlcmF0
aW9ucyBmb3Igb2JqZWN0LWJhc2VkIHNlY3VyaXR5IHRlY2hub2xvZ2llcywgdGhlIHNlY3VyaXR5
CiAgICAgIGNvbnNpZGVyYXRpb25zIGZvciB0aGlzIGZvcm1hdCBhcmUgdGhlIHNhbWUgYXMgZm9y
IENNUyA8eHJlZgogICAgICB0YXJnZXQ9IlJGQzU2NTIiLz4uIFRoZSBwcmltYXJ5IGRpZmZlcmVu
Y2UgYmV0d2VlbiB0aGUgSk9TRSBmb3JtYXQgYW5kCiAgICAgIENNUyBpcyB0aGF0IEpPU0UgaXMg
YmFzZWQgb24gSlNPTiwgd2hpY2ggZG9lcyBub3QgaGF2ZSBhIGNhbm9uaWNhbAogICAgICByZXBy
ZXNlbnRhdGlvbi4gVGhlIGxhY2sgb2YgYSBjYW5vbmljYWwgZm9ybSBtZWFucyB0aGF0IGl0IGlz
IGRpZmZpY3VsdAogICAgICB0byBkZXRlcm1pbmUgd2hldGhlciB0d28gSlNPTiBvYmplY3RzIHJl
cHJlc2VudCB0aGUgc2FtZSBpbmZvcm1hdGlvbiwKICAgICAgd2hpY2ggY291bGQgbGVhZCB0byB2
dWxuZXJhYmlsaXRpZXMgaW4gc29tZSB1c2FnZXMgb2YgSk9TRS48L3Q+CiAgICA8L3NlY3Rpb24+
CiAgPC9taWRkbGU+CgogIDwhLS0gICoqKioqQkFDSyBNQVRURVIgKioqKiogLS0+CgogIDxiYWNr
PgogICAgPHJlZmVyZW5jZXMgdGl0bGU9Ik5vcm1hdGl2ZSBSZWZlcmVuY2VzIj4KICAgICAgPD9y
ZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVm
ZXJlbmNlLlJGQy40NjI3LnhtbCI/PgoKICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5y
ZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy40NjQ4LnhtbCI/PgoK
ICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9i
aWJ4bWwvcmVmZXJlbmNlLlJGQy40OTQ5LnhtbCI/PgoKICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0
cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy41MDgz
LnhtbCI/PgoKICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVi
bGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy41NjUyLnhtbCI/PgoKICAgICAgPD9yZmMgaW5j
bHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNl
LlJGQy42MTIwLnhtbCI/PgoKICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJj
ZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy42NzA4LnhtbCI/PgoKICAgICAg
PD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwv
cmVmZXJlbmNlLlJGQy42NzQ5LnhtbCI/PgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1s
LnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjY3NTAueG1sIj8+
CgoKICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3Jm
Yy9iaWJ4bWwyL3JlZmVyZW5jZS5XM0MuUkVDLXhtbC0xOTk4LnhtbCIgPz4KCiAgICAgIDw/cmZj
IGluY2x1ZGU9Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sNC9yZWZl
cmVuY2UuVzNDLkNSLXhtbGRzaWctY29yZTItMjAxMjAxMjQueG1sIiA/PgoKICAgICAgPD9yZmMg
aW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWw0L3JlZmVy
ZW5jZS5XM0MuQ1IteG1sZW5jLWNvcmUxLTIwMTIwMzEzLnhtbCIgPz4KCiAgICAgIDxyZWZlcmVu
Y2UgYW5jaG9yPSJXZWJDcnlwdG8iPgogICAgICAgIDxmcm9udD4KICAgICAgICAgIDx0aXRsZT5X
ZWIgQ3J5cHRvZ3JhcGh5IEFQSTwvdGl0bGU+CiAgICAgICAgICA8YXV0aG9yIGZ1bGxuYW1lPSIi
IGluaXRpYWxzPSJSIiBzdXJuYW1lPSJTbGVldmkiLz4KICAgICAgICAgIDxhdXRob3IgZnVsbG5h
bWU9IiIgaW5pdGlhbHM9IkQiIHN1cm5hbWU9IkRhaGwiLz4KICAgICAgICAgIDxkYXRlIG1vbnRo
PSJKYW51YXJ5IiB5ZWFyPSIyMDEzIi8+CiAgICAgICAgPC9mcm9udD4KICAgICAgPC9yZWZlcmVu
Y2U+CiAgICA8L3JlZmVyZW5jZXM+CgogICAgPHJlZmVyZW5jZXMgdGl0bGU9IkluZm9ybWF0aXZl
IFJlZmVyZW5jZXMiPgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9y
Zy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjUyNDYueG1sIj8+CgogICAgICA8P3Jm
YyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZl
cmVuY2UuUkZDLjUzMjIueG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJl
c291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjU3NTEueG1sIj8+Cgog
ICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2Jp
YnhtbC9yZWZlcmVuY2UuUkZDLjI4MTgueG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRw
Oi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjMyMDcu
eG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJs
aWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjM5MjMueG1sIj8+CgogICAgICA8P3JmYyBpbmNs
dWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2Uu
UkZDLjQzMDEueG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNl
Lm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2UuUkZDLjI2MTYueG1sIj8+CgogICAgICA8
P3JmYyBpbmNsdWRlPSdodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDIv
cmVmZXJlbmNlLk9BU0lTLnNhbWwtY29yZS0yLjAtb3MueG1sJyA/PgoKICAgICAgPD9yZmMgaW5j
bHVkZT0naHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwzL3JlZmVyZW5j
ZS5JLUQuaWV0Zi1vYXV0aC1zYW1sMi1iZWFyZXIueG1sJyA/PgoKICAgICAgPD9yZmMgaW5jbHVk
ZT0naHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwzL3JlZmVyZW5jZS5J
LUQuaWV0Zi1vYXV0aC1qd3QtYmVhcmVyLnhtbCcgPz4KCiAgICAgIDw/cmZjIGluY2x1ZGU9Imh0
dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sMi9yZWZlcmVuY2UuSVRVLlg2
OTAuMTk5NC54bWwiID8+CiAgICAgIAogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJl
c291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDMvcmVmZXJlbmNlLkktRC5pZXRmLWpvc2UtanNv
bi13ZWItc2lnbmF0dXJlLnhtbCI/PgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJl
c291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDMvcmVmZXJlbmNlLkktRC5pZXRmLWpvc2UtanNv
bi13ZWItZW5jcnlwdGlvbi54bWwiPz4KICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5y
ZXNvdXJjZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwzL3JlZmVyZW5jZS5JLUQuaWV0Zi1qb3NlLWpz
b24td2ViLWtleS54bWwiPz4KICAgICAgPD9yZmMgaW5jbHVkZT0iaHR0cDovL3htbC5yZXNvdXJj
ZS5vcmcvcHVibGljL3JmYy9iaWJ4bWwzL3JlZmVyZW5jZS5JLUQuaWV0Zi1qb3NlLWpzb24td2Vi
LWFsZ29yaXRobXMueG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291
cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbDMvcmVmZXJlbmNlLkktRC5pZXRmLWFsdG8tcHJvdG9j
b2wueG1sIj8+CgogICAgICA8P3JmYyBpbmNsdWRlPSJodHRwOi8veG1sLnJlc291cmNlLm9yZy9w
dWJsaWMvcmZjL2JpYnhtbDMvcmVmZXJlbmNlLkktRC5pZXRmLWF0b2NhLXJlcXVpcmVtZW50cy54
bWwiPz4KCiAgICAgIDw/cmZjIGluY2x1ZGU9Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1Ymxp
Yy9yZmMvYmlieG1sMy9yZWZlcmVuY2UuSS1ELmlldGYtb2F1dGgtanNvbi13ZWItdG9rZW4ueG1s
Ij8+CgogICAgICA8IS0tCiAgICAgIDw/cmZjIGluY2x1ZGU9Imh0dHA6Ly94bWwucmVzb3VyY2Uu
b3JnL3B1YmxpYy9yZmMvYmlieG1sMy9yZWZlcmVuY2UuSS1ELm1pbGxlci14bXBwLWUyZS54bWwi
Pz4KICAgICAgLS0+CiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSdJLUQubWlsbGVyLXhtcHAtZTJl
Jz4KICAgICAgICA8ZnJvbnQ+CiAgICAgICAgICA8dGl0bGU+RW5kLXRvLUVuZCBPYmplY3QgRW5j
cnlwdGlvbiBmb3IgdGhlIEV4dGVuc2libGUgTWVzc2FnaW5nIGFuZCBQcmVzZW5jZSBQcm90b2Nv
bCAoWE1QUCk8L3RpdGxlPgogICAgICAgICAgPGF1dGhvciBmdWxsbmFtZT0iIiBpbml0aWFscz0i
TSIgc3VybmFtZT0iTWlsbGVyIiAvPgogICAgICAgICAgPGRhdGUgbW9udGg9J01heScgZGF5PScy
OCcgeWVhcj0nMjAxMycgLz4KICAgICAgPC9mcm9udD4KICAgICAgCiAgICAgIDxzZXJpZXNJbmZv
IG5hbWU9J0ludGVybmV0LURyYWZ0JyB2YWx1ZT0nZHJhZnQtbWlsbGVyLXhtcHAtZTJlLTA2JyAv
PgogICAgICA8Zm9ybWF0IHR5cGU9J1RYVCcKICAgICAgICAgICAgICB0YXJnZXQ9J2h0dHA6Ly93
d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW1pbGxlci14bXBwLWUyZS0wNi50eHQn
IC8+CiAgICAgIDxmb3JtYXQgdHlwZT0iSFRNTCIKCSAgICAgIHRhcmdldD0iaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtbWlsbGVyLXhtcHAtZTJlLTA2IiAvPgogICAgICA8L3JlZmVy
ZW5jZT4KCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJDQVAiPgogICAgICAgIDxmcm9udD4KICAg
ICAgICAgIDx0aXRsZT5Db21tb24gQWxlcnRpbmcgUHJvdG9jb2wgdjEuMTwvdGl0bGU+CiAgICAg
ICAgICA8YXV0aG9yIGZ1bGxuYW1lPSIiIGluaXRpYWxzPSJBIiBzdXJuYW1lPSJCb3R0ZXJlbGwi
Lz4KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IkUuIiBzdXJuYW1lPSJKb25lcyIvPgogICAg
ICAgICAgPGRhdGUgbW9udGg9Ik9jdG9iZXIiIHllYXI9IjIwMDUiLz4KICAgICAgICA8L2Zyb250
PgogICAgICA8L3JlZmVyZW5jZT4KCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJPcGVuSUQuTWVz
c2FnZXMiCiAgICAgICAgICAgICAgICAgdGFyZ2V0PSJodHRwOi8vb3BlbmlkLm5ldC9zcGVjcy9v
cGVuaWQtY29ubmVjdC1tZXNzYWdlcy0xXzAuaHRtbCI+CiAgICAgICAgPGZyb250PgogICAgICAg
ICAgPHRpdGxlPk9wZW5JRCBDb25uZWN0IE1lc3NhZ2VzIDEuMDwvdGl0bGU+CgogICAgICAgICAg
PGF1dGhvciBmdWxsbmFtZT0iTmF0IFNha2ltdXJhIiBpbml0aWFscz0iTi4iIHN1cm5hbWU9IlNh
a2ltdXJhIj4KICAgICAgICAgICAgPG9yZ2FuaXphdGlvbiBhYmJyZXY9Ik5SSSI+Tm9tdXJhIFJl
c2VhcmNoIEluc3RpdHV0ZSwKICAgICAgICAgICAgTHRkLjwvb3JnYW5pemF0aW9uPgogICAgICAg
ICAgPC9hdXRob3I+CgogICAgICAgICAgPGF1dGhvciBmdWxsbmFtZT0iSm9obiBCcmFkbGV5IiBp
bml0aWFscz0iSi4iIHN1cm5hbWU9IkJyYWRsZXkiPgogICAgICAgICAgICA8b3JnYW5pemF0aW9u
IGFiYnJldj0iUGluZyBJZGVudGl0eSI+UGluZyBJZGVudGl0eTwvb3JnYW5pemF0aW9uPgogICAg
ICAgICAgPC9hdXRob3I+CgogICAgICAgICAgPGF1dGhvciBmdWxsbmFtZT0iTWljaGFlbCBCLiBK
b25lcyIgaW5pdGlhbHM9Ik0uQi4iIHN1cm5hbWU9IkpvbmVzIj4KICAgICAgICAgICAgPG9yZ2Fu
aXphdGlvbiBhYmJyZXY9Ik1pY3Jvc29mdCI+TWljcm9zb2Z0PC9vcmdhbml6YXRpb24+CiAgICAg
ICAgICA8L2F1dGhvcj4KCiAgICAgICAgICA8YXV0aG9yIGZ1bGxuYW1lPSJCcmVubyBkZSBNZWRl
aXJvcyIgaW5pdGlhbHM9IkIuIgogICAgICAgICAgICAgICAgICBzdXJuYW1lPSJkZSBNZWRlaXJv
cyI+CiAgICAgICAgICAgIDxvcmdhbml6YXRpb24gYWJicmV2PSJHb29nbGUiPkdvb2dsZTwvb3Jn
YW5pemF0aW9uPgogICAgICAgICAgPC9hdXRob3I+CgogICAgICAgICAgPGF1dGhvciBmdWxsbmFt
ZT0iQ2h1Y2sgTW9ydGltb3JlIiBpbml0aWFscz0iQy4iIHN1cm5hbWU9Ik1vcnRpbW9yZSI+CiAg
ICAgICAgICAgIDxvcmdhbml6YXRpb24gYWJicmV2PSJTYWxlc2ZvcmNlIj5TYWxlc2ZvcmNlPC9v
cmdhbml6YXRpb24+CiAgICAgICAgICA8L2F1dGhvcj4KCiAgICAgICAgICA8YXV0aG9yIGZ1bGxu
YW1lPSJFZG11bmQgSmF5IiBpbml0aWFscz0iRS4iIHN1cm5hbWU9IkpheSI+CiAgICAgICAgICAg
IDxvcmdhbml6YXRpb24gYWJicmV2PSJJbGx1bWlsYSI+SWxsdW1pbGE8L29yZ2FuaXphdGlvbj4K
ICAgICAgICAgIDwvYXV0aG9yPgoKICAgICAgICAgIDxkYXRlIGRheT0iNyIgbW9udGg9Ikp1bmUi
IHllYXI9IjIwMTMiLz4KICAgICAgICA8L2Zyb250PgogICAgICA8L3JlZmVyZW5jZT4KCiAgICAg
IDxyZWZlcmVuY2UgYW5jaG9yPSJXUy1GZWRlcmF0aW9uIgogICAgICAgICAgICAgICAgIHRhcmdl
dD0iaHR0cDovL2RvY3Mub2FzaXMtb3Blbi5vcmcvd3NmZWQvZmVkZXJhdGlvbi92MS4yL29zL3dz
LWZlZGVyYXRpb24tMS4yLXNwZWMtb3MuaHRtbCI+CiAgICAgICAgPGZyb250PgogICAgICAgICAg
PHRpdGxlPldlYiBTZXJ2aWNlcyBGZWRlcmF0aW9uIExhbmd1YWdlIChXUy1GZWRlcmF0aW9uKSBW
ZXJzaW9uIDEuMjwvdGl0bGU+CgogICAgICAgICAgPGF1dGhvciBmdWxsbmFtZT0iQ2hyaXMgS2Fs
ZXIiIGluaXRpYWxzPSJDLiIgc3VybmFtZT0iS2FsZXIiPgogICAgICAgICAgICA8b3JnYW5pemF0
aW9uLz4KICAgICAgICAgIDwvYXV0aG9yPgoKICAgICAgICAgIDxhdXRob3IgZnVsbG5hbWU9Ik1p
Y2hhZWwgTWNJbnRvc2giIGluaXRpYWxzPSJNLiIgc3VybmFtZT0iTWNJbnRvc2giPgogICAgICAg
ICAgICA8b3JnYW5pemF0aW9uLz4KICAgICAgICAgIDwvYXV0aG9yPgoKICAgICAgICAgIDxhdXRo
b3IgZnVsbG5hbWU9Ik1hcmMgR29vZG5lciIgaW5pdGlhbHM9Ik0uIiBzdXJuYW1lPSJHb29kbmVy
Ij4KICAgICAgICAgICAgPG9yZ2FuaXphdGlvbi8+CiAgICAgICAgICA8L2F1dGhvcj4KCiAgICAg
ICAgICA8YXV0aG9yIGZ1bGxuYW1lPSJBbnRob255IE5hZGFsaW4iIGluaXRpYWxzPSJBLiIgc3Vy
bmFtZT0iTmFkYWxpbiI+CiAgICAgICAgICAgIDxvcmdhbml6YXRpb24vPgogICAgICAgICAgPC9h
dXRob3I+CgogICAgICAgICAgPGRhdGUgZGF5PSIyMiIgbW9udGg9Ik1heSIgeWVhcj0iMjAwOSIv
PgogICAgICAgIDwvZnJvbnQ+CiAgICAgIDwvcmVmZXJlbmNlPgoKICAgICAgPHJlZmVyZW5jZSBh
bmNob3I9IlBlcnNvbmEiPgoJPGZyb250PgoJICA8dGl0bGU+TW96aWxsYSBQZXJzb25hPC90aXRs
ZT4KCgkgIDxhdXRob3IgZnVsbG5hbWU9Ik1vemlsbGEiPgoJICAgIDxvcmdhbml6YXRpb24gYWJi
cmV2PSJNb3ppbGxhIj5Nb3ppbGxhPC9vcmdhbml6YXRpb24+CgkgIDwvYXV0aG9yPgoKCSAgPGRh
dGUgbW9udGg9IkFwcmlsIiB5ZWFyPSIyMDEzIiAvPgoJPC9mcm9udD4KCgk8Zm9ybWF0IHRhcmdl
dD0iaHR0cHM6Ly9kZXZlbG9wZXIubW96aWxsYS5vcmcvZW4tVVMvZG9jcy9QZXJzb25hIiB0eXBl
PSJIVE1MIiAvPgogICAgICA8L3JlZmVyZW5jZT4KCiAgICA8L3JlZmVyZW5jZXM+CgogICAgPHNl
Y3Rpb24gYW5jaG9yPSJhY2stc2VjIiB0aXRsZT0iQWNrbm93bGVkZ2VtZW50cyI+CiAgICAgIDx0
PlRoYW5rcyB0byBNYXR0IE1pbGxlciBmb3IgZGlzY3Vzc2lvbnMgcmVsYXRlZCB0byBYTVBQIGVu
ZC10by1lbmQKICAgICAgc2VjdXJpdHkgbW9kZWwsIGFuZCB0byBNaWtlIEpvbmVzIGZvciBjb25z
aWRlcmF0aW9ucyByZWxhdGVkIHRvIHNlY3VyaXR5CiAgICAgIHRva2VucyBhbmQgWE1MIHNlY3Vy
aXR5LiAgVGhhbmtzIHRvIE1hcmsgV2F0c29uIGZvciByYWlzaW5nIHRoZSBuZWVkIGZvciAKICAg
ICAgcmVwcmVzZW50aW5nIHN5bW1ldHJpYyBrZXlzIGFuZCBiaW5kaW5nIGF0dHJpYnV0ZXMgdG8g
dGhlbS48L3Q+CiAgICA8L3NlY3Rpb24+CgogICAgPHNlY3Rpb24gdGl0bGU9IkRvY3VtZW50IEhp
c3RvcnkiIGFuY2hvcj0iaGlzdC1zZWMiPgogICAgICA8dD4KCVtbIHRvIGJlIHJlbW92ZWQgYnkg
dGhlIFJGQyBlZGl0b3IgYmVmb3JlIHB1YmxpY2F0aW9uIGFzIGFuIFJGQyBdXQogICAgICA8L3Q+
CgogICAgICA8dD4KICAgICAgICAtMDMKICAgICAgICA8bGlzdCBzdHlsZT0nc3ltYm9scyc+CiAg
ICAgICAgICA8dD4KICAgICAgICAgICAgRWRpdG9yaWFsIGFuZCBmYWN0dWFsIGNvcnJlY3Rpb25z
LgoJICA8L3Q+CiAgICAgICAgPC9saXN0PgogICAgICA8L3Q+CiAgICAgIDx0PgogICAgICAgIC0w
MgogICAgICAgIDxsaXN0IHN0eWxlPSdzeW1ib2xzJz4KICAgICAgICAgIDx0PgogICAgICAgICAg
ICBSZWZlcmVuY2VkIHRoZSBKV1MsIEpXRSwgSldLLCBhbmQgSldBIHNwZWNpZmljYXRpb25zCgkg
ICAgbWFraW5nIHRoZSAic2lnbmVkIG9iamVjdCBmb3JtYXQiLCAiZW5jcnlwdGVkIG9iamVjdCBm
b3JtYXQiLAoJICAgICJrZXkgZm9ybWF0IiwgYW5kIGFsZ29yaXRobXMgcmVzdWx0aW5nIGZyb20g
dGhlc2UgdXNlIGNhc2VzIGNvbmNyZXRlLgogICAgICAgICAgPC90PgoJICA8dD4KCSAgICBBZGRl
ZCAiUmVxdWlyZW1lbnRzIG9uIEFwcGxpY2F0aW9uIFByb3RvY29scyIgc2VjdGlvbi4KCSAgPC90
PgoJICA8dD4KCSAgICBCcm9rZSBmb3JtZXIgaHVnZSAiU2VjdXJpdHkgVG9rZW5zIGFuZCBBdXRo
b3JpemF0aW9uIiBVc2UgQ2FzZSBzZWN0aW9uCgkgICAgaW50byAiU2VjdXJpdHkgVG9rZW5zIiwg
Ik9BdXRoIiwgYW5kICJGZWRlcmF0aW9uIiBVc2UgQ2FzZSBzZWN0aW9ucy4KCSAgPC90PgoJICA8
dD4KCSAgICBDaXRlZCBNb3ppbGxhIFBlcnNvbmEgYXMgYSBzaW5nbGUtc2lnbi1vbiAoU1NPKSBz
eXN0ZW0gdXNpbmcgSldUcwoJICAgIGFuZCBKT1NFIGRhdGEgZm9ybWF0cy4KCSAgPC90PgoJICA8
dD4KCSAgICBTcGVsbGluZyBhbmQgZ3JhbW1hciBjb3JyZWN0aW9ucy4KCSAgPC90PgogICAgICAg
IDwvbGlzdD4KICAgICAgPC90PgogICAgICA8dD4KICAgICAgICAtMDEKICAgICAgICA8bGlzdCBz
dHlsZT0ic3ltYm9scyI+CiAgICAgICAgICA8dD5BZGRlZCB0aGUgIlNtYWxsIERldmljZXMiIHVz
ZSBjYXNlPC90PgogICAgICAgIDwvbGlzdD4KICAgICAgPC90PgogICAgICA8dD4KICAgICAgICAt
MDAKICAgICAgICA8bGlzdCBzdHlsZT0nc3ltYm9scyc+CiAgICAgICAgICA8dD4KICAgICAgICAg
ICAgQ3JlYXRlZCB0aGUgaW5pdGlhbCBJRVRGIGRyYWZ0IGJhc2VkIHVwb24KICAgICAgICAgICAg
ZHJhZnQtYmFybmVzLWpvc2UtdXNlLWNhc2VzLTAxIHdpdGggc29tZSBhZGRpdGlvbnMuCiAgICAg
ICAgICA8L3Q+CiAgICAgICAgPC9saXN0PgogICAgICA8L3Q+CiAgICA8L3NlY3Rpb24+ICAgICAK
CiAgPC9iYWNrPgo8L3JmYz4K

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: text/plain; name="draft-ietf-jose-use-cases-02+Mike.txt"
Content-Description: draft-ietf-jose-use-cases-02+Mike.txt
Content-Disposition: attachment;
	filename="draft-ietf-jose-use-cases-02+Mike.txt"; size=54300;
	creation-date="Tue, 18 Jun 2013 22:46:24 GMT";
	modification-date="Tue, 18 Jun 2013 22:46:24 GMT"
Content-Transfer-Encoding: base64

CgoKSk9TRSBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgUi4gQmFybmVzCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgQkJOIFRlY2hub2xvZ2llcwpJbnRlbmRlZCBzdGF0dXM6IEluZm9y
bWF0aW9uYWwgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEp1bmUgMTksIDIwMTMKRXhwaXJl
czogRGVjZW1iZXIgMjEsIDIwMTMKCgpVc2UgQ2FzZXMgYW5kIFJlcXVpcmVtZW50cyBmb3IgSlNP
TiBPYmplY3QgU2lnbmluZyBhbmQgRW5jcnlwdGlvbiAoSk9TRSkKICAgICAgICAgICAgICAgICAg
ICAgIGRyYWZ0LWlldGYtam9zZS11c2UtY2FzZXMtMDMKCkFic3RyYWN0CgogICBNYW55IEludGVy
bmV0IGFwcGxpY2F0aW9ucyBoYXZlIGEgbmVlZCBmb3Igb2JqZWN0LWJhc2VkIHNlY3VyaXR5CiAg
IG1lY2hhbmlzbXMgaW4gYWRkaXRpb24gdG8gc2VjdXJpdHkgbWVjaGFuaXNtcyBhdCB0aGUgbmV0
d29yayBsYXllciBvcgogICB0cmFuc3BvcnQgbGF5ZXIuICBJbiB0aGUgcGFzdCwgdGhlIENyeXB0
b2dyYXBoaWMgTWVzc2FnZSBTeW50YXggaGFzCiAgIHByb3ZpZGVkIGEgYmluYXJ5IHNlY3VyZSBv
YmplY3QgZm9ybWF0IGJhc2VkIG9uIEFTTi4xLiAgT3ZlciB0aW1lLAogICB0aGUgdXNlIG9mIGJp
bmFyeSBvYmplY3QgZW5jb2RpbmdzIHN1Y2ggYXMgQVNOLjEgaGFzIGJlZW4gb3ZlcnRha2VuCiAg
IGJ5IHRleHQtYmFzZWQgZW5jb2RpbmdzLCBmb3IgZXhhbXBsZSBKYXZhU2NyaXB0IE9iamVjdCBO
b3RhdGlvbi4KICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgc2V0IG9mIHVzZSBjYXNlcyBhbmQg
cmVxdWlyZW1lbnRzIGZvciBhCiAgIHNlY3VyZSBvYmplY3QgZm9ybWF0IGVuY29kZWQgdXNpbmcg
SmF2YVNjcmlwdCBPYmplY3QgTm90YXRpb24sIGRyYXduCiAgIGZyb20gYSB2YXJpZXR5IG9mIGFw
cGxpY2F0aW9uIHNlY3VyaXR5IG1lY2hhbmlzbXMgY3VycmVudGx5IGluCiAgIGRldmVsb3BtZW50
LgoKU3RhdHVzIG9mIHRoaXMgTWVtbwoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0
ZWQgaW4gZnVsbCBjb25mb3JtYW5jZSB3aXRoIHRoZQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBh
bmQgQkNQIDc5LgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0
aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcKICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQg
b3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUKICAgd29ya2luZyBkb2N1bWVudHMgYXMg
SW50ZXJuZXQtRHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC0KICAgRHJhZnRz
IGlzIGF0IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8uCgogICBJ
bnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9m
IHNpeCBtb250aHMKICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVk
IGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkKICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUg
dG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UKICAgbWF0ZXJpYWwgb3IgdG8gY2l0
ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIgoKICAgVGhpcyBJbnRlcm5l
dC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBEZWNlbWJlciAyMSwgMjAxMy4KCkNvcHlyaWdodCBOb3Rp
Y2UKCiAgIENvcHlyaWdodCAoYykgMjAxMyBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVu
dGlmaWVkIGFzIHRoZQogICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4K
CiAgIFRoaXMgZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0
J3MgTGVnYWwKICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0
cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUg
b2YKICAgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2Ug
ZG9jdW1lbnRzCgoKCkJhcm5lcyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjEs
IDIwMTMgICAgICAgICAgICAgICBbUGFnZSAxXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAg
ICAgSk9TRSBVc2UgQ2FzZXMgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAxMwoKCiAgIGNhcmVm
dWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVzdHJpY3Rpb25zIHdpdGgg
cmVzcGVjdAogICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21wb25lbnRzIGV4dHJhY3RlZCBm
cm9tIHRoaXMgZG9jdW1lbnQgbXVzdAogICBpbmNsdWRlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2Ug
dGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LmUgb2YKICAgdGhlIFRydXN0IExlZ2FsIFBy
b3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0IHdhcnJhbnR5IGFzCiAgIGRlc2NyaWJl
ZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS4KCgpUYWJsZSBvZiBDb250ZW50cwoKICAg
MS4gIEludHJvZHVjdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAzCiAgIDIuICBEZWZpbml0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNAogICAzLiAgQmFzaWMgUmVxdWlyZW1lbnRzIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDUKICAgNC4gIFJlcXVp
cmVtZW50cyBvbiBBcHBsaWNhdGlvbiBQcm90b2NvbHMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICA2CiAgIDUuICBVc2UgQ2FzZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgNwogICAgIDUuMS4gIFNlY3VyaXR5IFRva2VucyAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDcKICAgICA1LjIuICBPQXV0aCAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA3CiAgICAg
NS4zLiAgRmVkZXJhdGlvbiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgOQogICAgIDUuNC4gIFhNUFAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTAKICAgICA1LjUuICBBTFRPIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEyCiAgICAgNS42LiAgRW1l
cmdlbmN5IEFsZXJ0aW5nIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAx
MwogICAgIDUuNy4gIFdlYiBDcnlwdG9ncmFwaHkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gMTQKICAgICA1LjguICBTbWFsbCBEZXZpY2VzICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE1CiAgIDYuICBSZXF1aXJlbWVudHMgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNgogICAgIDYu
MS4gIEZ1bmN0aW9uYWwgUmVxdWlyZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gMTcKICAgICA2LjIuICBTZWN1cml0eSBSZXF1aXJlbWVudHMgIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE4CiAgICAgNi4zLiAgRGVzaWRlcmF0YSAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxOAogICA3LiAgSUFOQSBDb25z
aWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTgK
ICAgOC4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDE5CiAgIDkuICBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxOQogICAgIDkuMS4gIE5vcm1hdGl2ZSBSZWZl
cmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTkKICAgICA5LjIu
ICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDIwCiAgIEFwcGVuZGl4IEEuICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAyMgogICBBcHBlbmRpeCBCLiAgRG9jdW1lbnQgSGlzdG9yeSAg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjMKICAgQXV0aG9yJ3MgQWRkcmVz
cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDIzCgoK
CgoKCgoKCgoKCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAy
MSwgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAg
ICAgICBKT1NFIFVzZSBDYXNlcyAgICAgICAgICAgICAgICAgICAgSnVuZSAyMDEzCgoKMS4gIElu
dHJvZHVjdGlvbgoKICAgSW50ZXJuZXQgYXBwbGljYXRpb25zIHJlc3Qgb24gdGhlIGxheWVyZWQg
YXJjaGl0ZWN0dXJlIG9mIHRoZQogICBJbnRlcm5ldCwgYW5kIHRha2UgYWR2YW50YWdlIG9mIHNl
Y3VyaXR5IG1lY2hhbmlzbXMgYXQgYWxsIGxheWVycy4KICAgTWFueSBhcHBsaWNhdGlvbnMgcmVs
eSBwcmltYXJpbHkgb24gY2hhbm5lbC1iYXNlZCBzZWN1cml0eQogICB0ZWNobm9sb2dpZXMsIHdo
aWNoIGNyZWF0ZSBhIHNlY3VyZSBjaGFubmVsIGF0IHRoZSBJUCBsYXllciBvcgogICB0cmFuc3Bv
cnQgbGF5ZXIgb3ZlciB3aGljaCBhcHBsaWNhdGlvbiBkYXRhIGNhbiBmbG93CiAgIFtSRkM0MzAx
XVtSRkM1MjQ2XS4gIFRoZXNlIG1lY2hhbmlzbXMsIGhvd2V2ZXIsIGNhbm5vdCBwcm92aWRlIGVu
ZC0KICAgdG8tZW5kIHNlY3VyaXR5IGluIHNvbWUgY2FzZXMuICBGb3IgZXhhbXBsZSwgaW4gcHJv
dG9jb2xzIHdpdGgKICAgYXBwbGljYXRpb24tbGF5ZXIgaW50ZXJtZWRpYXJpZXMsIGNoYW5uZWwt
YmFzZWQgc2VjdXJpdHkgcHJvdG9jb2xzCiAgIHdvdWxkIHByb3RlY3QgbWVzc2FnZXMgZnJvbSBh
dHRhY2tlcnMgYmV0d2VlbiBpbnRlcm1lZGlhcmllcywgYnV0IG5vdAogICBmcm9tIHRoZSBpbnRl
cm1lZGlhcmllcyB0aGVtc2VsdmVzLiAgVGhlc2UgY2FzZXMgcmVxdWlyZSBvYmplY3QtYmFzZWQK
ICAgc2VjdXJpdHkgdGVjaG5vbG9naWVzLCB3aGljaCBlbWJlZCBhcHBsaWNhdGlvbiBkYXRhIHdp
dGhpbiBhIHNlY3VyZQogICBvYmplY3QgdGhhdCBjYW4gYmUgc2FmZWx5IGhhbmRsZWQgYnkgdW50
cnVzdGVkIGVudGl0aWVzLgoKICAgVGhlIG1vc3Qgd2VsbC1rbm93biBleGFtcGxlIG9mIHN1Y2gg
YSBwcm90b2NvbCB0b2RheSBpcyB0aGUgdXNlIG9mCiAgIFNlY3VyZS9NdWx0aXB1cnBvc2UgSW50
ZXJuZXQgTWFpbCBFeHRlbnNpb25zIChTL01JTUUpIHByb3RlY3Rpb25zCiAgIHdpdGhpbiB0aGUg
ZW1haWwgc3lzdGVtIFtSRkM1NzUxXVtSRkM1MzIyXS4gIEFuIGVtYWlsIG1lc3NhZ2UKICAgdHlw
aWNhbGx5IHBhc3NlcyB0aHJvdWdoIGEgc2VyaWVzIG9mIGludGVybWVkaWF0ZSBNYWlsIFRyYW5z
ZmVyCiAgIEFnZW50cyAoTVRBcykgZW4gcm91dGUgdG8gaXRzIGRlc3RpbmF0aW9uLiAgV2hpbGUg
dGhlc2UgTVRBcyBvZnRlbgogICBhcHBseSBjaGFubmVsLWJhc2VkIHNlY3VyaXR5IHByb3RlY3Rp
b25zIHRvIHRoZWlyIGludGVyYWN0aW9ucyAoZS5nLiwKICAgW1JGQzMyMDddKSwgdGhlc2UgcHJv
dGVjdGlvbnMgZG8gbm90IHByZXZlbnQgdGhlIE1UQXMgZnJvbQogICBpbnRlcmZlcmluZyB3aXRo
IHRoZSBtZXNzYWdlLiAgSW4gb3JkZXIgdG8gcHJvdmlkZSBlbmQtdG8tZW5kCiAgIHNlY3VyaXR5
IHByb3RlY3Rpb25zIGluIHRoZSBwcmVzZW5jZSBvZiB1bnRydXN0ZWQgTVRBcywgbWFpbCB1c2Vy
cwogICBjYW4gdXNlIFMvTUlNRSB0byBlbWJlZCBtZXNzYWdlIGJvZGllcyBpbiBhIHNlY3VyZSBv
YmplY3QgZm9ybWF0IHRoYXQKICAgY2FuIHByb3ZpZGUgY29uZmlkZW50aWFsaXR5LCBpbnRlZ3Jp
dHksIGFuZCBkYXRhIG9yaWdpbgogICBhdXRoZW50aWNhdGlvbi4KCiAgIFMvTUlNRSBpcyBiYXNl
ZCBvbiB0aGUgQ3J5cHRvZ3JhcGhpYyBNZXNzYWdlIFN5bnRheCBmb3Igc2VjdXJlCiAgIG9iamVj
dHMgKENNUykgW1JGQzU2NTJdLiAgQ01TIGlzIGRlZmluZWQgdXNpbmcgQWJzdHJhY3QgU3ludGF4
CiAgIE5vdGF0aW9uIDEgKEFTTi4xKSBhbmQgdHJhZGl0aW9uYWxseSBlbmNvZGVkIHVzaW5nIHRo
ZSBBU04uMQogICBEaXN0aW5ndWlzaGVkIEVuY29kaW5nIFJ1bGVzIChERVIpLCB3aGljaCBkZWZp
bmUgYSBiaW5hcnkgZW5jb2Rpbmcgb2YKICAgdGhlIHByb3RlY3RlZCBtZXNzYWdlIGFuZCBhc3Nv
Y2lhdGVkIHBhcmFtZXRlcnMgW0lUVS5YNjkwLjE5OTRdLiAgSW4KICAgcmVjZW50IHllYXJzLCB1
c2FnZSBvZiBBU04uMSBoYXMgZGVjcmVhc2VkIChhbG9uZyB3aXRoIG90aGVyIGJpbmFyeQogICBl
bmNvZGluZ3MgZm9yIGdlbmVyYWwgb2JqZWN0cyksIHdoaWxlIG1vcmUgYXBwbGljYXRpb25zIGhh
dmUgY29tZSB0bwogICByZWx5IG9uIHRleHQtYmFzZWQgZm9ybWF0cyBzdWNoIGFzIHRoZSBFeHRl
bnNpYmxlIE1hcmt1cCBMYW5ndWFnZQogICAoWE1MKSBvciB0aGUgSmF2YVNjcmlwdCBPYmplY3Qg
Tm90YXRpb24gKEpTT04pCiAgIFtXM0MuUkVDLXhtbC0xOTk4XVtSRkM0NjI3XS4KCiAgIE1hbnkg
Y3VycmVudCBhcHBsaWNhdGlvbnMgdGh1cyBoYXZlIG11Y2ggbW9yZSByb2J1c3Qgc3VwcG9ydCBm
b3IKICAgcHJvY2Vzc2luZyBvYmplY3RzIGluIHRoZXNlIHRleHQtYmFzZWQgZm9ybWF0cyB0aGFu
IEFTTi4xIG9iamVjdHM7CiAgIGluZGVlZCwgbWFueSBsYWNrIHRoZSBhYmlsaXR5IHRvIHByb2Nl
c3MgQVNOLjEgb2JqZWN0cyBhdCBhbGwuICBUbwogICBzaW1wbGlmeSB0aGUgYWRkaXRpb24gb2Yg
b2JqZWN0LWJhc2VkIHNlY3VyaXR5IGZlYXR1cmVzIHRvIHRoZXNlCiAgIGFwcGxpY2F0aW9ucywg
dGhlIElFVEYgSlNPTiBPYmplY3QgU2lnbmluZyBhbmQgRW5jcnlwdGlvbiAoSk9TRSkKICAgd29y
a2luZyBncm91cCBoYXMgYmVlbiBjaGFydGVyZWQgdG8gZGV2ZWxvcCBhIHNlY3VyZSBvYmplY3Qg
Zm9ybWF0CiAgIGJhc2VkIG9uIEpTT04uICBXaGlsZSB0aGUgYmFzaWMgcmVxdWlyZW1lbnRzIGZv
ciB0aGlzIG9iamVjdCBmb3JtYXQKICAgYXJlIHN0cmFpZ2h0Zm9yd2FyZCAtLSBuYW1lbHksIGNv
bmZpZGVudGlhbGl0eSBhbmQgaW50ZWdyaXR5CiAgIG1lY2hhbmlzbXMsIGVuY29kZWQgaW4gSlNP
TiAtLSBkaXNjdXNzaW9ucyBpbiB0aGUgd29ya2luZyBncm91cAoKCgpCYXJuZXMgICAgICAgICAg
ICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAgICAgW1BhZ2UgM10K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAgICAgICAg
ICAgICAgICBKdW5lIDIwMTMKCgogICBpbmRpY2F0ZWQgdGhhdCBkaWZmZXJlbnQgYXBwbGljYXRp
b25zIGhvcGluZyB0byB1c2UgdGhlIGZvcm1hdHMKICAgZGVmaW5lZCBieSBKT1NFIGhhdmUgZGlm
ZmVyZW50IHJlcXVpcmVtZW50cy4gIFRoaXMgZG9jdW1lbnQKICAgc3VtbWFyaXplcyB0aGUgdXNl
IGNhc2VzIGZvciBKT1NFIGVudmlzaW9uZWQgYnkgdGhvc2UgcG90ZW50aWFsCiAgIGFwcGxpY2F0
aW9ucyBhbmQgdGhlIHJlc3VsdGluZyByZXF1aXJlbWVudHMgZm9yIHNlY3VyaXR5IG1lY2hhbmlz
bXMKICAgYW5kIG9iamVjdCBlbmNvZGluZ3MuCgogICBTb21lIHN5c3RlbXMgdGhhdCB1c2UgWE1M
IGhhdmUgc3BlY2lmaWVkIHRoZSB1c2Ugb2YgWE1MLWJhc2VkCiAgIHNlY3VyaXR5IG1lY2hhbmlz
bXMgZm9yIG9iamVjdCBzZWN1cml0eSwgbmFtZWx5IFhNTCBEaWdpdGFsCiAgIFNpZ25hdHVyZXMg
YW5kIFhNTCBFbmNyeXB0aW9uCiAgIFtXM0MuQ1IteG1sZHNpZy1jb3JlMi0yMDEyMDEyNF1bVzND
LkNSLXhtbGVuYy1jb3JlMS0yMDEyMDMxM10uICBUaGVzZQogICBtZWNoYW5pc21zIGFyZSBkZWZp
bmVkIGZvciB1c2Ugd2l0aCBzZXZlcmFsIHNlY3VyaXR5IHRva2VuIHN5c3RlbXMKICAgKGUuZy4s
IFNBTUwgW09BU0lTLnNhbWwtY29yZS0yLjAtb3NdIGFuZCBXUy1GZWRlcmF0aW9uCiAgIFtXUy1G
ZWRlcmF0aW9uXSkgYW5kIHRoZSBDQVAgZW1lcmdlbmN5IGFsZXJ0aW5nIGZvcm1hdCBbQ0FQXS4g
IEluCiAgIHByYWN0aWNlLCBob3dldmVyLCBYTUwtYmFzZWQgc2VjdXJlIG9iamVjdCBmb3JtYXRz
IGludHJvZHVjZSBzaW1pbGFyCiAgIGxldmVscyBvZiBjb21wbGV4aXR5IHRvIEFTTi4xLCBzbyBk
ZXZlbG9wZXJzIHRoYXQgbGFjayB0aGUgdG9vbHMgb3IKICAgbW90aXZhdGlvbiB0byBoYW5kbGUg
QVNOLjEgYXJlbid0IGxpa2VseSB0byB1c2UgWE1MIHNlY3VyaXR5IGVpdGhlci4KICAgVGhpcyBz
aXR1YXRpb24gbW90aXZhdGVzIHRoZSBjcmVhdGlvbiBvZiBhIEpTT04tYmFzZWQgc2VjdXJlIG9i
amVjdAogICBmb3JtYXQgdGhhdCBpcyBzaW1wbGUgZW5vdWdoIHRvIGltcGxlbWVudCBhbmQgZGVw
bG95IHRoYXQgaXQgY2FuIGJlCiAgIGVhc2lseSBhZG9wdGVkIGJ5IGRldmVsb3BlcnMgd2l0aCBt
aW5pbWFsIGVmZm9ydCBhbmQgdG9vbHMuCgoKMi4gIERlZmluaXRpb25zCgogICBUaGlzIGRvY3Vt
ZW50IG1ha2VzIGV4dGVuc2l2ZSB1c2Ugb2Ygc3RhbmRhcmQgc2VjdXJpdHkgdGVybWlub2xvZ3kK
ICAgW1JGQzQ5NDldLiAgSW4gYWRkaXRpb24sIGJlY2F1c2UgdGhlIHVzZSBjYXNlcyBmb3IgSk9T
RSBhbmQgQ01TIGFyZQogICBzaW1pbGFyLCB3ZSB3aWxsIHNvbWV0aW1lcyBtYWtlIGFuYWxvZ2ll
cyB0byBzb21lIENNUyBjb25jZXB0cwogICBbUkZDNTY1Ml0uCgogICBUaGUgSk9TRSB3b3JraW5n
IGdyb3VwIGNoYXJ0ZXIgY2FsbHMgZm9yIHRoZSBncm91cCB0byBkZWZpbmUgdGhyZWUKICAgYmFz
aWMgSlNPTiBvYmplY3QgZm9ybWF0czoKCiAgIDEuICBDb25maWRlbnRpYWxpdHktcHJvdGVjdGVk
IG9iamVjdCBmb3JtYXQKCiAgIDIuICBJbnRlZ3JpdHktcHJvdGVjdGVkIG9iamVjdCBmb3JtYXQK
CiAgIDMuICBBIGZvcm1hdCBmb3IgZXhwcmVzc2luZyBrZXlzCgogICBJbiB0aGlzIGRvY3VtZW50
LCB3ZSB3aWxsIHJlZmVyIHRvIHRoZXNlIGFzIHRoZSAic2lnbmVkIG9iamVjdAogICBmb3JtYXQi
LCB0aGUgImVuY3J5cHRlZCBvYmplY3QgZm9ybWF0IiwgYW5kIHRoZSAia2V5IGZvcm1hdCIsCiAg
IHJlc3BlY3RpdmVseS4gIFRoZSBKT1NFIHdvcmtpbmcgZ3JvdXAgaXRlbXMgaW50ZW5kZWQgdG8g
ZGVzY3JpYmUKICAgdGhlc2UgZm9ybWF0cyBhcmUgSlNPTiBXZWIgU2lnbmF0dXJlIChKV1MpLCBK
U09OIFdlYiBFbmNyeXB0aW9uCiAgIChKV0UpLCBhbmQgSlNPTiBXZWIgS2V5IChKV0spLCByZXNw
ZWN0aXZlbHkKICAgW0ktRC5pZXRmLWpvc2UtanNvbi13ZWItc2lnbmF0dXJlXSwKICAgW0ktRC5p
ZXRmLWpvc2UtanNvbi13ZWItZW5jcnlwdGlvbl0sIGFuZAogICBbSS1ELmlldGYtam9zZS1qc29u
LXdlYi1rZXldLiAgQWxnb3JpdGhtcyBhbmQgYWxnb3JpdGhtIGlkZW50aWZpZXJzCiAgIHVzZWQg
YnkgSldTLCBKV0UsIGFuZCBKV0sgYXJlIGRlZmluZWQgaW4gSlNPTiBXZWIgQWxnb3JpdGhtcyAo
SldBKQogICBbSS1ELmlldGYtam9zZS1qc29uLXdlYi1hbGdvcml0aG1zXS4KCgoKCkJhcm5lcyAg
ICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjEsIDIwMTMgICAgICAgICAgICAgICBb
UGFnZSA0XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgSk9TRSBVc2UgQ2FzZXMgICAg
ICAgICAgICAgICAgICAgIEp1bmUgMjAxMwoKCiAgIEluIGdlbmVyYWwsIHdoZXJlIHRoZXJlIGlz
IG5vIG5lZWQgdG8gZGlzdGluZ3Vpc2ggYmV0d2VlbiBhc3ltbWV0cmljCiAgIGFuZCBzeW1tZXRy
aWMgb3BlcmF0aW9ucywgd2Ugd2lsbCB1c2UgdGhlIHRlcm1zICJzaWduaW5nIiwKICAgInNpZ25h
dHVyZSIsIGV0Yy4gdG8gZGVub3RlIGJvdGggdHJ1ZSBkaWdpdGFsIHNpZ25hdHVyZXMgaW52b2x2
aW5nCiAgIGFzeW1tZXRyaWMgY3J5cHRvZ3JhcGh5IGFzIHdlbGwgYXMgbWVzc2FnZSBhdXRoZW50
aWNhdGlvbiBjb2RlcyB1c2luZwogICBzeW1tZXRyaWMga2V5cyAoTUFDcykuCgogICBJbiB0aGUg
bGlmZXNwYW4gb2YgYSBzZWN1cmUgb2JqZWN0LCB0aGVyZSBhcmUgdHdvIGJhc2ljIHJvbGVzLCBh
bgogICBlbnRpdHkgdGhhdCBjcmVhdGVzIHRoZSBvYmplY3QgKGUuZy4sIGVuY3J5cHRpbmcgb3Ig
c2lnbmluZyBhCiAgIHBheWxvYWQpLCBhbmQgYW4gZW50aXR5IHRoYXQgdXNlcyB0aGUgb2JqZWN0
IChkZWNyeXB0aW5nLCB2ZXJpZnlpbmcpLgogICBXZSB3aWxsIHJlZmVyIHRvIHRoZXNlIHJvbGVz
IGFzICJzZW5kZXIiIGFuZCAicmVjaXBpZW50IiwKICAgcmVzcGVjdGl2ZWx5LiAgTm90ZSB0aGF0
IHdoaWxlIHNvbWUgcmVxdWlyZW1lbnRzIGFuZCB1c2UgY2FzZXMgbWF5CiAgIHJlZmVyIHRvIHRo
ZXNlIGFzIHNpbmdsZSBlbnRpdGllcywgZWFjaCBvYmplY3QgbWF5IGhhdmUgbXVsdGlwbGUKICAg
ZW50aXRpZXMgaW4gZWFjaCByb2xlLiAgRm9yIGV4YW1wbGUsIGEgbWVzc2FnZSBtYXkgYmUgc2ln
bmVkIGJ5CiAgIG11bHRpcGxlIHNlbmRlcnMsIG9yIGRlY3J5cHRlZCBieSBtdWx0aXBsZSByZWNp
cGllbnRzLgoKCjMuICBCYXNpYyBSZXF1aXJlbWVudHMKCiAgIE9idmlvdXNseSwgZm9yIHRoZSBl
bmNyeXB0ZWQgYW5kIHNpZ25lZCBvYmplY3QgZm9ybWF0cywgdGhlIG5lY2Vzc2FyeQogICBwcm90
ZWN0aW9ucyB3aWxsIGJlIGNyZWF0ZWQgdXNpbmcgYXBwcm9wcmlhdGUgY3J5cHRvZ3JhcGhpYwog
ICBtZWNoYW5pc21zOiBzeW1tZXRyaWMgb3IgYXN5bW1ldHJpYyBlbmNyeXB0aW9uIGZvciBjb25m
aWRlbnRpYWxpdHkKICAgYW5kIE1BQ3Mgb3IgZGlnaXRhbCBzaWduYXR1cmVzIGZvciBpbnRlZ3Jp
dHkgcHJvdGVjdGlvbi4gIEluIGJvdGgKICAgY2FzZXMsIGl0IGlzIG5lY2Vzc2FyeSBmb3IgdGhl
IEpPU0UgZm9ybWF0IHRvIHN1cHBvcnQgYm90aCBzeW1tZXRyaWMKICAgYW5kIGFzeW1tZXRyaWMg
b3BlcmF0aW9ucy4KCiAgIG8gIFRoZSBKT1NFIGVuY3J5cHRlZCBvYmplY3QgZm9ybWF0IG11c3Qg
c3VwcG9ydCBvYmplY3QgZW5jcnlwdGlvbiBpbgogICAgICB0aGUgY2FzZSB3aGVyZSB0aGUgc2Vu
ZGVyIGFuZCByZWNlaXZlciBzaGFyZSBhIHN5bW1ldHJpYyBrZXkuCgogICBvICBUaGUgSk9TRSBl
bmNyeXB0ZWQgb2JqZWN0IGZvcm1hdCBtdXN0IHN1cHBvcnQgb2JqZWN0IGVuY3J5cHRpb24gaW4K
ICAgICAgdGhlIGNhc2Ugd2hlcmUgdGhlIHNlbmRlciBoYXMgb25seSBhIHB1YmxpYyBrZXkgZm9y
IHRoZSByZWNlaXZlci4KCiAgIG8gIFRoZSBKT1NFIHNpZ25lZCBvYmplY3QgZm9ybWF0IG11c3Qg
c3VwcG9ydCBpbnRlZ3JpdHkgcHJvdGVjdGlvbgogICAgICB1c2luZyBNZXNzYWdlIEF1dGhlbnRp
Y2F0aW9uIENvZGVzIChNQUNzKSwgZm9yIHRoZSBjYXNlIHdoZXJlIHRoZQogICAgICBzZW5kZXIg
YW5kIHJlY2VpdmVyIHNoYXJlIG9ubHkgYSBzeW1tZXRyaWMga2V5LgoKICAgbyAgVGhlIEpPU0Ug
c2lnbmVkIG9iamVjdCBmb3JtYXQgbXVzdCBzdXBwb3J0IGludGVncml0eSBwcm90ZWN0aW9uCiAg
ICAgIHVzaW5nIGRpZ2l0YWwgc2lnbmF0dXJlcywgZm9yIHRoZSBjYXNlIHdoZXJlIHRoZSByZWNl
aXZlciBoYXMgb25seQogICAgICBhIHB1YmxpYyBrZXkgZm9yIHRoZSBzZW5kZXIuCgogICBJbiBz
b21lIGFwcGxpY2F0aW9ucywgdGhlIGtleSB1c2VkIHRvIHByb2Nlc3MgYSBKT1NFIG9iamVjdCBp
cwogICBpbmRpY2F0ZWQgYnkgYXBwbGljYXRpb24gY29udGV4dCwgaW5zdGVhZCBvZiBkaXJlY3Rs
eSBpbiB0aGUgSk9TRQogICBvYmplY3QuICBIb3dldmVyLCBpbiBvcmRlciB0byBhdm9pZCBjb25m
dXNpbmcgZW5kcG9pbnRzIHRoYXQgbGFjayB0aGUKICAgbmVjZXNzYXJ5IGNvbnRleHQgbmVlZCB0
byBiZSBhYmxlIHRvIHJlY29nbml6ZSB0aGlzIGFuZCBmYWlsIGNsZWFubHkuCiAgIE90aGVyIHRo
YW4ga2V5cywgSk9TRSBvYmplY3RzIGRvIG5vdCBzdXBwb3J0IHByZS1uZWdvdGlhdGlvbjsgYWxs
CiAgIGNyeXB0b2dyYXBoaWMgcGFyYW1ldGVycyBtdXN0IGJlIGV4cHJlc3NlZCBkaXJlY3RseSBp
biB0aGUgSk9TRQogICBvYmplY3QuCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAgRXhwaXJl
cyBEZWNlbWJlciAyMSwgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDVdCgwKSW50ZXJuZXQtRHJh
ZnQgICAgICAgICAgICAgICBKT1NFIFVzZSBDYXNlcyAgICAgICAgICAgICAgICAgICAgSnVuZSAy
MDEzCgoKICAgbyAgVGhlIEpPU0Ugc2lnbmVkIGFuZCBlbmNyeXB0ZWQgb2JqZWN0IGZvcm1hdHMg
bXVzdCBkZWZpbmUgdGhlCiAgICAgIHByb2Nlc3MgYnkgd2hpY2ggYW4gaW1wbGVtZW50YXRpb24g
cmVjb2duaXplcyB3aGV0aGVyIGl0IGhhcyB0aGUKICAgICAga2V5IHJlcXVpcmVkIHRvIHByb2Nl
c3MgYSBnaXZlbiBvYmplY3QgaW4gdGhlIGNhc2UgdGhhdCB0aGUKICAgICAgYXBwbGljYXRpb24g
ZG9lcyBub3Qgc3BlY2lmeSB0aGUgdXNlIG9mIGFub3RoZXIgbWVhbnMgb3IKICAgICAgY29udmVu
dGlvbiB0byBkZXRlcm1pbmUgdGhlIGtleSB1c2VkLgoKICAgbyAgRWFjaCBhbGdvcml0aG0gdXNl
ZCBmb3IgSk9TRSBtdXN0IGRlZmluZSB3aGljaCBwYXJhbWV0ZXJzIGFyZQogICAgICByZXF1aXJl
ZCB0byBiZSBwcmVzZW50IGluIGEgSk9TRSBvYmplY3QgdXNpbmcgdGhhdCBhbGdvcml0aG0uCgog
ICBJbiBjYXNlcyB3aGVyZSB0d28gZW50aXRpZXMgYXJlIGdvaW5nIHRvIGJlIGV4Y2hhbmdpbmcg
c2V2ZXJhbCBKT1NFCiAgIG9iamVjdHMsIGl0IG1pZ2h0IGJlIGhlbHBmdWwgdG8gcHJlLW5lZ290
aWF0ZSBzb21lIHBhcmFtZXRlcnMgc28gdGhhdAogICB0aGV5IGRvIG5vdCBoYXZlIHRvIGJlIHNp
Z25hbGVkIGluIGV2ZXJ5IEpPU0Ugb2JqZWN0LiAgSG93ZXZlciwgc28gYXMKICAgbm90IHRvIGNv
bmZ1c2UgZW5kcG9pbnRzIHRoYXQgZG8gbm90IHN1cHBvcnQgcHJlLW5lZ290aWF0aW9uLCBpdCBp
cwogICB1c2VmdWwgdG8gc2lnbmFsIHdoZW4gcHJlLW5lZ290aWF0ZWQgcGFyYW1ldGVycyBhcmUg
aW4gdXNlIGluIHRob3NlCiAgIGNhc2VzLgoKICAgbyAgSXQgc2hvdWxkIGJlIHBvc3NpYmxlIHRv
IGV4dGVuZCB0aGUgYmFzZSBKT1NFIHNpZ25lZCBhbmQgZW5jcnlwdGVkCiAgICAgIG9iamVjdCBm
b3JtYXRzIHRvIGluZGljYXRlIHRoYXQgcHJlLW5lZ290aWF0ZWQgcGFyYW1ldGVycyBhcmUgdG8K
ICAgICAgYmUgdXNlZCB0byBwcm9jZXNzIHRoZSBvYmplY3QuICBUaGlzIGV4dGVuc2lvbiBzaG91
bGQgYWxzbyBwcm92aWRlCiAgICAgIGEgbWVhbnMgb2YgaW5kaWNhdGluZyBvZiB3aGljaCBwYXJh
bWV0ZXJzIGFyZSB0byBiZSB1c2VkLgoKICAgVGhlIHB1cnBvc2Ugb2YgdGhlIGtleSBmb3JtYXQg
aXMgdG8gcHJvdmlkZSB0aGUgcmVjaXBpZW50IHdpdGgKICAgc3VmZmljaWVudCBpbmZvcm1hdGlv
biB0byB1c2UgdGhlIGVuY29kZWQga2V5IHRvIHByb2Nlc3MKICAgY3J5cHRvZ3JhcGhpYyBtZXNz
YWdlcy4gIFRodXMgaXQgaXMgc29tZXRpbWVzIG5lY2Vzc2FyeSB0byBpbmNsdWRlCiAgIGFkZGl0
aW9uYWwgcGFyYW1ldGVycyBhbG9uZyB3aXRoIHRoZSBiYXJlIGtleS4KCiAgIG8gIFRoZSBKT1NF
IGtleSBmb3JtYXQgbXVzdCBlbmFibGUgaW5jbHVzaW9uIG9mIGFsbCBhbGdvcml0aG0KICAgICAg
cGFyYW1ldGVycyBuZWNlc3NhcnkgdG8gdXNlIHRoZSBlbmNvZGVkIGtleSwgaW5jbHVkaW5nIGFu
CiAgICAgIGlkZW50aWZpZXIgZm9yIHRoZSBhbGdvcml0aG0gd2l0aCB3aGljaCB0aGUga2V5IGlz
IHVzZWQgYXMgd2VsbCBhcwogICAgICBhbnkgYWRkaXRpb25hbCBwYXJhbWV0ZXJzIHJlcXVpcmVk
IGJ5IHRoZSBhbGdvcml0aG0gKGUuZy4sCiAgICAgIGVsbGlwdGljIGN1cnZlIHBhcmFtZXRlcnMp
LgoKCjQuICBSZXF1aXJlbWVudHMgb24gQXBwbGljYXRpb24gUHJvdG9jb2xzCgogICBUaGUgSk9T
RSBzZWN1cmUgb2JqZWN0IGZvcm1hdHMgZGVzY3JpYmUgaG93IGNyeXB0b2dyYXBoaWMgcHJvY2Vz
c2luZwogICBpcyBkb25lIG9uIHNlY3VyZWQgY29udGVudCwgZW5zdXJpbmcgdGhhdCB0aGUgcmVj
aXBpZW50IGFuIG9iamVjdCBpcwogICBhYmxlIHRvIHByb3Blcmx5IGRlY3J5cHQgYW4gZW5jcnlw
dGVkIG9iamVjdCBvciB2ZXJpZnkgYSBzaWduYXR1cmUuCiAgIEluIG9yZGVyIHRvIG1ha2UgdXNl
IG9mIEpPU0UsIGhvd2V2ZXIsIGFwcGxpY2F0aW9ucyB3aWxsIG5lZWQgdG8KICAgc3BlY2lmeSBz
ZXZlcmFsIGFzcGVjdHMgb2YgaG93IEpPU0UgaXMgdG8gYmUgdXNlZDoKCiAgIG8gIFdoYXQgYXBw
bGljYXRpb24gZGF0YSBpcyB0byBiZSBwcm90ZWN0ZWQKCiAgIG8gIFdoaWNoIGNyeXB0b2dyYXBo
aWMgYWxnb3JpdGhtcyBhcmUgdG8gYmUgdXNlZAoKICAgbyAgSG93IGFwcGxpY2F0aW9uIHByb3Rv
Y29sIGVudGl0aWVzIGVzdGFibGlzaCBrZXlzCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAg
RXhwaXJlcyBEZWNlbWJlciAyMSwgMjAxMyAgICAgICAgICAgICAgIFtQYWdlIDZdCgwKSW50ZXJu
ZXQtRHJhZnQgICAgICAgICAgICAgICBKT1NFIFVzZSBDYXNlcyAgICAgICAgICAgICAgICAgICAg
SnVuZSAyMDEzCgoKICAgbyAgV2hldGhlciBrZXlzIGFyZSB0byBiZSBleHBsaWNpdGx5IGluZGlj
YXRlZCBpbiBKT1NFIG9iamVjdHMsIG9yCiAgICAgIGFzc29jaWF0ZWQgYnkgYXBwbGljYXRpb24g
Y29udGV4dAoKCjUuICBVc2UgQ2FzZXMKCiAgIFNldmVyYWwgd29ya2luZyBncm91cHMgZGV2ZWxv
cGluZyBhcHBsaWNhdGlvbi1sYXllciBwcm90b2NvbHMgaGF2ZQogICBleHByZXNzZWQgYSBkZXNp
cmUgdG8gdXNlIHRoZSBKT1NFIGRhdGEgZm9ybWF0cyBpbiB0aGVpciBkZXNpZ25zIGZvcgogICBl
bmQtdG8tZW5kIHNlY3VyaXR5IGZlYXR1cmVzLiAgSW4gdGhpcyBzZWN0aW9uLCB3ZSBzdW1tYXJp
emUgdGhlIHVzZQogICBjYXNlcyBwcm9wb3NlZCBieSB0aGVzZSBncm91cHMgYW5kIGRpc2N1c3Mg
dGhlIHJlcXVpcmVtZW50cyB0aGF0IHRoZXkKICAgaW1wbHkgZm9yIHRoZSBKT1NFIG9iamVjdCBm
b3JtYXRzLgoKNS4xLiAgU2VjdXJpdHkgVG9rZW5zCgogICBTZWN1cml0eSB0b2tlbnMgYXJlIGEg
Y29tbW9uIHVzZSBjYXNlIGZvciBvYmplY3QtYmFzZWQgc2VjdXJpdHksIGZvcgogICBleGFtcGxl
LCBTQU1MIGFzc2VydGlvbnMgW09BU0lTLnNhbWwtY29yZS0yLjAtb3NdLiAgU2VjdXJpdHkgdG9r
ZW5zCiAgIGFyZSB1c2VkIHRvIGNvbnZleSBpbmZvcm1hdGlvbiBhYm91dCBhIHN1YmplY3QgZW50
aXR5ICgiY2xhaW1zIiBvcgogICAiYXNzZXJ0aW9ucyIpIGZyb20gYW4gaXNzdWVyIHRvIGEgcmVj
aXBpZW50LiAgVGhlIHNlY3VyaXR5IGZlYXR1cmVzCiAgIG9mIGEgdG9rZW4gZm9ybWF0IGVuYWJs
ZSB0aGUgcmVjaXBpZW50IHRvIHZlcmlmeSB0aGF0IHRoZSBjbGFpbXMgY2FtZQogICBmcm9tIHRo
ZSBpc3N1ZXIgYW5kLCBpZiB0aGUgb2JqZWN0IGlzIGNvbmZpZGVudGlhbGl0eS1wcm90ZWN0ZWQs
IHRoYXQKICAgdGhleSB3ZXJlIG5vdCB2aXNpYmxlIHRvIG90aGVyIHBhcnRpZXMuCgogICBTZWN1
cml0eSB0b2tlbnMgYXJlIHVzZWQgaW4gZmVkZXJhdGlvbiBwcm90b2NvbHMgc3VjaCBhcyBTQU1M
IDIuMAogICBbT0FTSVMuc2FtbC1jb3JlLTIuMC1vc10sIFdTLUZlZGVyYXRpb24gW1dTLUZlZGVy
YXRpb25dLCBNb3ppbGxhCiAgIFBlcnNvbmEgW1BlcnNvbmFdLCBhbmQgT3BlbklEIENvbm5lY3Qg
W09wZW5JRC5NZXNzYWdlc10sIGFzIHdlbGwgYXMKICAgaW4gcmVzb3VyY2UgYXV0aG9yaXphdGlv
biBwcm90b2NvbHMgc3VjaCBhcyBPQXV0aCAyLjAgW1JGQzY3NDldLAogICBpbmNsdWRpbmcgZm9y
IE9BdXRoIGJlYXJlciB0b2tlbnMgW1JGQzY3NTBdLiAgSW4gc29tZSBjYXNlcywgc2VjdXJpdHkK
ICAgdG9rZW5zIGFyZSB1c2VkIGZvciBjbGllbnQgYXV0aGVudGljYXRpb24gYW5kIGZvciBhY2Nl
c3MgY29udHJvbAogICBbSS1ELmlldGYtb2F1dGgtand0LWJlYXJlcl1bSS1ELmlldGYtb2F1dGgt
c2FtbDItYmVhcmVyXS4KCiAgIEpTT04gV2ViIFRva2VuIChKV1QpIFtJLUQuaWV0Zi1vYXV0aC1q
c29uLXdlYi10b2tlbl0gaXMgYSBzZWN1cml0eQogICB0b2tlbiBmb3JtYXQgYmFzZWQgb24gSlNP
TiBhbmQgSk9TRS4gIEl0IGlzIHVzZWQgd2l0aCBNb3ppbGxhCiAgIFBlcnNvbmEsIE9wZW5JRCBD
b25uZWN0LCBhbmQgT0F1dGguICBCZWNhdXNlIEpXVHMgYXJlIG9mdGVuIHVzZWQgaW4KICAgY29u
dGV4dHMgd2l0aCBsaW1pdGVkIHNwYWNlIChlLmcuLCBIVFRQIHF1ZXJ5IHBhcmFtZXRlcnMpLCBp
dCBpcyBhCiAgIGNvcmUgcmVxdWlyZW1lbnQgZm9yIEpXVHMsIGFuZCB0aHVzIEpPU0UsIHRvIGhh
dmUgYSBjb21wYWN0LCBVUkwtc2FmZQogICByZXByZXNlbnRhdGlvbi4KCjUuMi4gIE9BdXRoCgog
ICBUaGUgT0F1dGggcHJvdG9jb2wgZGVmaW5lcyBhIG1lY2hhbmlzbSBmb3IgZGlzdHJpYnV0aW5n
IGFuZCB1c2luZwogICBhdXRob3JpemF0aW9uIHRva2VucyB1c2luZyBIVFRQIFtSRkM2NzQ5XS4g
IEEgQ2xpZW50IHRoYXQgd2lzaGVzIHRvCiAgIGFjY2VzcyBhIHByb3RlY3RlZCByZXNvdXJjZSBy
ZXF1ZXN0cyBhdXRob3JpemF0aW9uIGZyb20gdGhlIFJlc291cmNlCiAgIE93bmVyLiAgSWYgdGhl
IFJlc291cmNlIE93bmVyIGFsbG93cyB0aGlzIGFjY2VzcywgaGUgZGlyZWN0cyBhbgogICBBdXRo
b3JpemF0aW9uIFNlcnZlciB0byBpc3N1ZSBhbiBhY2Nlc3MgdG9rZW4gdG8gdGhlIENsaWVudC4g
IFdoZW4KICAgdGhlIENsaWVudCB3aXNoZXMgdG8gYWNjZXNzIHRoZSBwcm90ZWN0ZWQgcmVzb3Vy
Y2UsIGhlIHByZXNlbnRzIHRoZQogICB0b2tlbiB0byB0aGUgcmVsZXZhbnQgUmVzb3VyY2UgU2Vy
dmVyLCB3aGljaCB2ZXJpZmllcyB0aGUgdmFsaWRpdHkgb2YKICAgdGhlIHRva2VuIGJlZm9yZSBw
cm92aWRpbmcgYWNjZXNzIHRvIHRoZSBwcm90ZWN0ZWQgcmVzb3VyY2UuCgoKCgpCYXJuZXMgICAg
ICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAgICAgW1Bh
Z2UgN10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAg
ICAgICAgICAgICAgICBKdW5lIDIwMTMKCgogICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0t
LS0rICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgIHwgICAgICAgICAgfCAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICB8ICAg
UmVzb3VyY2UgICAgfDwuLi4uLi4uLj58IEF1dGhvcml6YXRpb24gfAogICAgICAgICAgICAgICAg
IHwgICAgU2VydmVyICAgICB8ICAgICAgICAgIHwgICAgIFNlcnZlciAgICB8CiAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgIHwgICAgICAgICAgfCAgICAgICAgICAgICAgIHwKICAgICAg
ICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKyAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKwog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeICAgICAgICAgICAgICAgIHwKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAg
ICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLXwtLSsgICAgICAg
ICAgKy0tfC0tLS0tLS0tLS0tLSsKICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLS0tLS0rICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAg
ICB8ICAgICAgICAgIHwgICBSZXNvdXJjZSAgICB8CiAgICAgICAgICAgICAgICAgfCAgICAgQ2xp
ZW50ICAgIHwgICAgICAgICAgfCAgICAgT3duZXIgICAgIHwKICAgICAgICAgICAgICAgICB8ICAg
ICAgICAgICAgICAgfCAgICAgICAgICB8ICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAg
ICstLS0tLS0tLS0tLS0tLS0rICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0rCgogICAgICAgICAg
ICAgICAgICAgICAgICBGaWd1cmUgMTogVGhlIE9BdXRoIHByb2Nlc3MKCiAgIEluIGVmZmVjdCwg
dGhpcyBwcm9jZXNzIG1vdmVzIHRoZSB0b2tlbiBmcm9tIHRoZSBBdXRob3JpemF0aW9uIFNlcnZl
cgogICAoYXMgYSBzZW5kZXIgb2YgdGhlIG9iamVjdCkgdG8gdGhlIFJlc291cmNlIFNlcnZlciAo
cmVjaXBpZW50KSwgdmlhCiAgIHRoZSBDbGllbnQgYXMgd2VsbCBhcyB0aGUgUmVzb3VyY2UgT3du
ZXIgKHRoZSBsYXR0ZXIgYmVjYXVzZSBvZiB0aGUKICAgSFRUUCBtZWNoYW5pY3MgdW5kZXJseWlu
ZyB0aGUgcHJvdG9jb2wpLiAgU28gYWdhaW4gd2UgaGF2ZSBhIGNhc2UKICAgd2hlcmUgYW4gYXBw
bGljYXRpb24gb2JqZWN0IGlzIHRyYW5zcG9ydGVkIHZpYSB1bnRydXN0ZWQKICAgaW50ZXJtZWRp
YXJpZXMuCgogICBUaGlzIGFwcGxpY2F0aW9uIGhhcyB0d28gZXNzZW50aWFsIHNlY3VyaXR5IHJl
cXVpcmVtZW50czogSW50ZWdyaXR5CiAgIGFuZCBkYXRhIG9yaWdpbiBhdXRoZW50aWNhdGlvbi4g
IEludGVncml0eSBwcm90ZWN0aW9uIGlzIHJlcXVpcmVkIHNvCiAgIHRoYXQgdGhlIFJlc291cmNl
IE93bmVyIGFuZCB0aGUgQ2xpZW50IGNhbm5vdCBtb2RpZnkgdGhlIHBlcm1pc3Npb24KICAgZW5j
b2RlZCBpbiB0aGUgdG9rZW4uICBEYXRhIG9yaWdpbiBhdXRoZW50aWNhdGlvbiBpcyByZXF1aXJl
ZCBzbyB0aGF0CiAgIHRoZSBSZXNvdXJjZSBTZXJ2ZXIgY2FuIHZlcmlmeSB0aGF0IHRoZSB0b2tl
biB3YXMgaXNzdWVkIGJ5IGEgdHJ1c3RlZAogICBBdXRob3JpemF0aW9uIFNlcnZlci4gIENvbmZp
ZGVudGlhbGl0eSBwcm90ZWN0aW9uIG1heSBhbHNvIGJlIG5lZWRlZCwKICAgaWYgdGhlIEF1dGhv
cml6YXRpb24gU2VydmVyIGlzIGNvbmNlcm5lZCBhYm91dCB0aGUgdmlzaWJpbGl0eSBvZgogICBw
ZXJtaXNzaW9ucyBpbmZvcm1hdGlvbiB0byB0aGUgUmVzb3VyY2UgT3duZXIgb3IgQ2xpZW50LiAg
Rm9yCiAgIGV4YW1wbGUsIHBlcm1pc3Npb25zIHJlbGF0ZWQgdG8gc29jaWFsIG5ldHdvcmtpbmcg
bWlnaHQgYmUgY29uc2lkZXJlZAogICBwcml2YXRlIGluZm9ybWF0aW9uLiAgTm90ZSwgaG93ZXZl
ciwgdGhhdCBPQXV0aCBhbHJlYWR5IHJlcXVpcmVzIHRoYXQKICAgdGhlIHVuZGVybHlpbmcgSFRU
UCB0cmFuc2FjdGlvbnMgYmUgcHJvdGVjdGVkIGJ5IFRMUywgc28KICAgY29uZmlkZW50aWFsaXR5
IHByb3RlY3Rpb24gaXMgbm90IHN0cmljdGx5IG5lY2Vzc2FyeSBmb3IgdGhpcyB1c2UKICAgY2Fz
ZS4KCiAgIFRoZSBjb25maWRlbnRpYWxpdHkgYW5kIGludGVncml0eSBuZWVkcyBhcmUgbWV0IGJ5
IHRoZSBiYXNpYwogICByZXF1aXJlbWVudHMgZm9yIHNpZ25lZCBhbmQgZW5jcnlwdGVkIG9iamVj
dCBmb3JtYXRzLCB3aGV0aGVyIHRoZQogICBzaWduaW5nIGFuZCBlbmNyeXB0aW9uIGFyZSBwcm92
aWRlZCB1c2luZyBhc3ltbWV0cmljIG9yIHN5bW1ldHJpYwogICBjcnlwdG9ncmFwaHkuICBUaGUg
Y2hvaWNlIG9mIHdoaWNoIG1lY2hhbmlzbSBpcyBhcHBsaWVkIHdpbGwgZGVwZW5kCiAgIG9uIHRo
ZSByZWxhdGlvbnNoaXAgYmV0d2VlbiB0aGUgdHdvIHNlcnZlcnMsIG5hbWVseSB3aGV0aGVyIHRo
ZXkKICAgc2hhcmUgYSBzeW1tZXRyaWMga2V5IG9yIG9ubHkgcHVibGljIGtleXMuCgoKCgpCYXJu
ZXMgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAg
ICAgW1BhZ2UgOF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2Vz
ICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTMKCgogICBBdXRoZW50aWNhdGlvbiByZXF1aXJl
bWVudHMgd2lsbCBhbHNvIGRlcGVuZCBvbiBkZXBsb3ltZW50CiAgIGNoYXJhY3RlcmlzdGljcy4g
IFdoZXJlIHRoZXJlIGlzIGEgcmVsYXRpdmVseSBzdHJvbmcgYmluZGluZyBiZXR3ZWVuCiAgIHRo
ZSByZXNvdXJjZSBzZXJ2ZXIgYW5kIHRoZSBhdXRob3JpemF0aW9uIHNlcnZlciwgaXQgbWF5IHN1
ZmZpY2UgZm9yCiAgIHRoZSBBdXRob3JpemF0aW9uIFNlcnZlciBpc3N1aW5nIGEgdG9rZW4gdG8g
YmUgaWRlbnRpZmllZCBieSB0aGUga2V5CiAgIHVzZWQgdG8gc2lnbiB0aGUgdG9rZW4uICBUaGlz
IHJlcXVpcmVzIHRoYXQgdGhlIHByb3RvY29sIGNhcnJ5IGVpdGhlcgogICB0aGUgcHVibGljIGtl
eSBvZiB0aGUgQXV0aG9yaXphdGlvbiBTZXJ2ZXIgb3IgYW4gaWRlbnRpZmllciBmb3IgdGhlCiAg
IHB1YmxpYyBvciBzeW1tZXRyaWMga2V5LiAgSW4gT0F1dGgsIHRoZSAiY2xpZW50X2lkIiBwYXJh
bWV0ZXIKICAgaWRlbnRpZmllcyB0aGUga2V5IHRvIGJlIHVzZWQuCgogICBUaGVyZSBtYXkgYWxz
byBiZSBtb3JlIGFkdmFuY2VkIGNhc2VzLCB3aGVyZSB0aGUgQXV0aG9yaXphdGlvbgogICBTZXJ2
ZXIncyBrZXkgaXMgbm90IGtub3duIGluIGFkdmFuY2UgdG8gdGhlIFJlc291cmNlIFNlcnZlci4g
IFRoaXMKICAgbWF5IGhhcHBlbiwgZm9yIGluc3RhbmNlLCBpZiBhbiBlbnRpdHkgaW5zdGFudGlh
dGVkIGEgY29sbGVjdGlvbiBvZgogICBBdXRob3JpemF0aW9uIFNlcnZlcnMgKHNheSBmb3IgbG9h
ZCBiYWxhbmNpbmcpLCBlYWNoIG9mIHdoaWNoIGhhcyBhbgogICBpbmRlcGVuZGVudCBrZXkgcGFp
ci4gIEluIHRoZXNlIGNhc2VzLCBpdCBtYXkgYmUgbmVjZXNzYXJ5IHRvIGFsc28KICAgaW5jbHVk
ZSBhIGNlcnRpZmljYXRlIG9yIGNlcnRpZmljYXRlIGNoYWluIGZvciB0aGUgQXV0aG9yaXphdGlv
bgogICBTZXJ2ZXIsIHNvIHRoYXQgdGhlIFJlc291cmNlIFNlcnZlciBjYW4gdmVyaWZ5IHRoYXQg
dGhlIEF1dGhvcml6YXRpb24KICAgU2VydmVyIGlzIGFuIGVudGl0eSB0aGF0IGl0IHRydXN0cy4K
CiAgIFRoZSBIVFRQIHRyYW5zcG9ydCBmb3IgT0F1dGggaW1wb3NlcyBhIHBhcnRpY3VsYXIgY29u
c3RyYWludCBvbiB0aGUKICAgZW5jb2RpbmcuICBJbiB0aGUgT0F1dGggcHJvdG9jb2wsIHRva2Vu
cyBmcmVxdWVudGx5IG5lZWQgdG8gYmUgcGFzc2VkCiAgIGFzIHF1ZXJ5IHBhcmFtZXRlcnMgaW4g
SFRUUCBVUklzIFtSRkMyNjE2XSwgYWZ0ZXIgaGF2aW5nIGJlZW4KICAgYmFzZTY0dXJsIGVuY29k
ZWQgW1JGQzQ2NDhdLiAgV2hpbGUgdGhlcmUgaXMgbm8gc3BlY2lmaWVkIGxpbWl0IG9uCiAgIHRo
ZSBsZW5ndGggb2YgVVJJcyAoYW5kIHRodXMgb2YgcXVlcnkgcGFyYW1ldGVycyksIGluIHByYWN0
aWNlLCBVUklzCiAgIG9mIG1vcmUgdGhhbiAyLDA0OCBjaGFyYWN0ZXJzIGFyZSByZWplY3RlZCBi
eSBzb21lIHVzZXIgYWdlbnRzLiAgRm9yCiAgIHNvbWUgbW9iaWxlIGJyb3dzZXJzLCB0aGlzIGxp
bWl0IGlzIGV2ZW4gc21hbGxlci4gIFNvIHRoaXMgdXNlIGNhc2UKICAgcmVxdWlyZXMgdGhhdCBh
IEpPU0Ugb2JqZWN0IGhhdmUgc3VmZmljaWVudGx5IHNtYWxsIHNpemUgZXZlbiBhZnRlcgogICBz
aWduaW5nLCBwb3NzaWJseSBlbmNyeXB0aW5nLCB3aGlsZSBzdGlsbCBiZWluZyBzaW1wbGUgdG8g
aW5jbHVkZSBpbgogICBhbiBIVFRQIFVSSSBxdWVyeSBwYXJhbWV0ZXIuCgo1LjMuICBGZWRlcmF0
aW9uCgogICBTZWN1cml0eSB0b2tlbnMgYXJlIHVzZWQgaW4gdHdvIGZlZGVyYXRlZCBpZGVudGl0
eSBwcm90b2NvbHM6CgogICBvICBUaGUgT3BlbklEIENvbm5lY3QgcHJvdG9jb2wgW09wZW5JRC5N
ZXNzYWdlc10gaXMgYSBzaW1wbGUsIFJFU1QvCiAgICAgIEpTT04tYmFzZWQgaWRlbnRpdHkgZmVk
ZXJhdGlvbiBwcm90b2NvbCBsYXllcmVkIG9uIE9BdXRoIDIuMC4gIEl0CiAgICAgIHVzZXMgdGhl
IEpXVCBhbmQgSk9TRSBmb3JtYXRzIGJvdGggdG8gcmVwcmVzZW50IHNlY3VyaXR5IHRva2Vucwog
ICAgICBhbmQgdG8gcHJvdmlkZSBzZWN1cml0eSBmb3Igb3RoZXIgcHJvdG9jb2wgbWVzc2FnZXMg
KHBlcmZvcm1pbmcKICAgICAgc2lnbmluZyBhbmQgb3B0aW9uYWxseSBlbmNyeXB0aW9uKS4gIE9w
ZW5JRCBDb25uZWN0IG5lZ290aWF0ZXMgdGhlCiAgICAgIGFsZ29yaXRobXMgdG8gYmUgdXNlZCBh
bmQgZGlzdHJpYnV0ZXMgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGtleXMKICAgICAgdG8gYmUgdXNl
ZCB1c2luZyBwcm90b2NvbCBlbGVtZW50cyB0aGF0IGFyZSBub3QgcGFydCBvZiB0aGUgSldUCiAg
ICAgIGFuZCBKT1NFIGhlYWRlciBwYXJhbWV0ZXJzLgoKICAgbyAgVGhlIE1vemlsbGEgUGVyc29u
YSBbUGVyc29uYV0gc3lzdGVtIGlzIGEgc2ltcGxlIHNpbmdsZS1zaWduLW9uCiAgICAgIChTU08p
IHByb3RvY29sIHRoYXQgdXNlcyBKV1RzIHRoYXQgYXJlIHNpZ25lZCBKT1NFIEpXUyBvYmplY3Rz
IHRvCiAgICAgIHJlcHJlc2VudCBpbmZvcm1hdGlvbiBhYm91dCBpZGVudGl0aWVzLCBhcHBsaWNh
dGlvbnMsIGFuZCBrZXlzIGZvcgogICAgICBwYXJ0aWNpcGF0aW5nIGVudGl0aWVzLiAgUGVyc29u
YSBkaXN0cmlidXRlcyB0aGUga2V5cyB1c2VkIGFzCiAgICAgIGNsYWltcyBpbiBKV1QgbWVzc2Fn
ZXMgYW5kIG5vdCBieSB1c2luZyBKT1NFIGhlYWRlciBwYXJhbWV0ZXJzLgoKCgoKQmFybmVzICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAyMSwgMjAxMyAgICAgICAgICAgICAgIFtQ
YWdlIDldCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICBKT1NFIFVzZSBDYXNlcyAgICAg
ICAgICAgICAgICAgICAgSnVuZSAyMDEzCgoKNS40LiAgWE1QUAoKICAgVGhlIEV4dGVuc2libGUg
TWVzc2FnaW5nIGFuZCBQcmVzZW5jZSBQcm90b2NvbCAoWE1QUCkgcm91dGVzIG1lc3NhZ2VzCiAg
IGZyb20gb25lIGVuZCBjbGllbnQgdG8gYW5vdGhlciBieSB3YXkgb2YgWE1QUCBzZXJ2ZXJzIFtS
RkM2MTIwXS4KICAgVGhlcmUgYXJlIHR5cGljYWxseSB0d28gc2VydmVycyBpbnZvbHZlZCBpbiBk
ZWxpdmVyaW5nIGFueSBnaXZlbgogICBtZXNzYWdlOiBUaGUgZmlyc3QgY2xpZW50IChBbGljZSkg
c2VuZHMgYSBtZXNzYWdlIGZvciBhbm90aGVyIGNsaWVudAogICAoQikgdG8gaGVyIHNlcnZlciAo
QSkuICBTZXJ2ZXIgQSB1c2VzIEJvYidzIGlkZW50aXR5IGFuZCB0aGUgRE5TIHRvCiAgIGxvY2F0
ZSB0aGUgc2VydmVyIGZvciBCb2IncyBkb21haW4gKEIpLCB0aGVuIGRlbGl2ZXJzIHRoZSBtZXNz
YWdlIHRvCiAgIHRoYXQgc2VydmVyLiAgU2VydmVyIEIgdGhlbiByb3V0ZXMgdGhlIG1lc3NhZ2Ug
dG8gQm9iLgoKICAgICAgICAgICAgKy0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0tLS0t
LS0rICAgKy0tLS0tKwogICAgICAgICAgICB8IEFsaWNlIHwtLT58IFNlcnZlciBBIHwtLT58IFNl
cnZlciBCIHwtLT58IEJvYiB8CiAgICAgICAgICAgICstLS0tLS0tKyAgICstLS0tLS0tLS0tKyAg
ICstLS0tLS0tLS0tKyAgICstLS0tLSsKCiAgICAgICAgICAgICAgICAgICBGaWd1cmUgMjogRGVs
aXZlcmluZyBhbiBYTVBQIG1lc3NhZ2UKCiAgIFRoZSB1bnRydXN0ZWQtaW50ZXJtZWRpYXJ5IHBy
b2JsZW1zIGFyZSBlc3BlY2lhbGx5IGFjdXRlIGZvciBYTVBQCiAgIGJlY2F1c2UgaW4gbWFueSBj
dXJyZW50IGRlcGxveW1lbnRzLCB0aGUgaG9sZGVyIG9mIGFuIFhNUFAgZG9tYWluCiAgIG91dHNv
dXJjZXMgdGhlIG9wZXJhdGlvbiBvZiB0aGUgZG9tYWluJ3Mgc2VydmVycyB0byBhIGRpZmZlcmVu
dAogICBlbnRpdHkuICBJbiB0aGlzIGVudmlyb25tZW50LCB0aGVyZSBpcyBhIGNsZWFyIHJpc2sg
b2YgZXhwb3NpbmcgdGhlCiAgIGRvbWFpbiBob2xkZXIncyBwcml2YXRlIGluZm9ybWF0aW9uIHRv
IHRoZSBkb21haW4gb3BlcmF0b3IuICBYTVBQCiAgIGFscmVhZHkgaGFzIGEgZGVmaW5lZCBtZWNo
YW5pc20gZm9yIGVuZC10by1lbmQgc2VjdXJpdHkgdXNpbmcgUy9NSU1FLAogICBidXQgaXQgaGFz
IGZhaWxlZCB0byBnYWluIHdpZGVzcHJlYWQgZGVwbG95bWVudCBbUkZDMzkyM10sIGluIHBhcnQK
ICAgYmVjYXVzZSBvZiBrZXkgbWFuYWdlbWVudCBjaGFsbGVuZ2VzIGFuZCBiZWNhdXNlIG9mIHRo
ZSBkaWZmaWN1bHR5IG9mCiAgIHByb2Nlc3NpbmcgUy9NSU1FIG9iamVjdHMuCgogICBUaGUgWE1Q
UCB3b3JraW5nIGdyb3VwIGlzIGluIHRoZSBwcm9jZXNzIG9mIGRldmVsb3BpbmcgYSBuZXcgZW5k
LXRvLQogICBlbmQgZW5jcnlwdGlvbiBzeXN0ZW0gd2l0aCBhbiBlbmNvZGluZyBiYXNlZCBvbiBK
T1NFIGFuZCBhIGNsZWFyZXIKICAga2V5IG1hbmFnZW1lbnQgc3lzdGVtIFtJLUQubWlsbGVyLXht
cHAtZTJlXS4gIFRoZSBwcm9jZXNzIG9mIHNlbmRpbmcKICAgYW4gZW5jcnlwdGVkIG1lc3NhZ2Ug
aW4gdGhpcyBzeXN0ZW0gaW52b2x2ZXMgdHdvIHN0ZXBzOiBGaXJzdCwgdGhlCiAgIHNlbmRlciBn
ZW5lcmF0ZXMgYSBzeW1tZXRyaWMgQ29udGVudCBFbmNyeXB0aW9uIEtleSAoQ0VLKSwgZW5jcnlw
dHMKICAgdGhlIG1lc3NhZ2UgY29udGVudCwgYW5kIHNlbmRzIHRoZSBlbmNyeXB0ZWQgbWVzc2Fn
ZSB0byB0aGUgZGVzaXJlZAogICBzZXQgb2YgcmVjaXBpZW50cy4gIFNlY29uZCwgZWFjaCByZWNp
cGllbnQgImRpYWxzIGJhY2siIHRvIHRoZQogICBzZW5kZXIsIHByb3ZpZGluZyBoaXMgcHVibGlj
IGtleTsgdGhlIHNlbmRlciB0aGVuIHJlc3BvbmRzIHdpdGggdGhlCiAgIHJlbGV2YW50IENFSywg
d3JhcHBlZCB3aXRoIHRoZSByZWNpcGllbnQncyBwdWJsaWMga2V5LgoKICAgICAgICAgICAgKy0t
LS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0tKwogICAgICAgICAg
ICB8IEFsaWNlIHw8LT58IFNlcnZlciBBIHw8LT58IFNlcnZlciBCIHw8LT58IEJvYiB8CiAgICAg
ICAgICAgICstLS0tLS0tKyAgICstLS0tLS0tLS0tKyAgICstLS0tLS0tLS0tKyAgICstLS0tLSsK
ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgfCAgICAgICAgICAgICAgfCAgICAgICAgICAg
fAogICAgICAgICAgICAgICAgfC0tLS0tLS0tLS0tLUVuY3J5cHRlZC0tbWVzc2FnZS0tLS0tLS0t
LT58CiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgIHwgICAgICAgICAgICAgIHwgICAgICAg
ICAgIHwKICAgICAgICAgICAgICAgIHw8LS0tLS0tLS0tLS0tLS0tUHVibGljLWtleS0tLS0tLS0t
LS0tLS0tfAogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICB8ICAgICAgICAgICAgICB8ICAg
ICAgICAgICB8CiAgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0tV3JhcHBlZCBDRUstLS0t
LS0tLS0tLS0tPnwKICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgfCAgICAgICAgICAgICAg
fCAgICAgICAgICAgfAoKICAgICAgICAgICAgICAgIEZpZ3VyZSAzOiBEZWxpdmVyaW5nIGEgc2Vj
dXJlIFhNUFAgbWVzc2FnZQoKCgpCYXJuZXMgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2Vt
YmVyIDIxLCAyMDEzICAgICAgICAgICAgICBbUGFnZSAxMF0KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTMKCgog
ICBUaGUgbWFpbiB0aGluZyB0aGF0IHRoaXMgc3lzdGVtIHJlcXVpcmVzIGZyb20gdGhlIEpPU0Ug
Zm9ybWF0cyBpcwogICBjb25maWRlbnRpYWxpdHkgcHJvdGVjdGlvbiB2aWEgY29udGVudCBlbmNy
eXB0aW9uLCBwbHVzIGFuIGludGVncml0eQogICBjaGVjayB2aWEgYSBNQUMgZGVyaXZlZCBmcm9t
IHRoZSBzYW1lIHN5bW1ldHJpYyBrZXkuICBUaGUgc2VwYXJhdGlvbgogICBvZiB0aGUga2V5IGV4
Y2hhbmdlIGZyb20gdGhlIHRyYW5zbWlzc2lvbiBvZiB0aGUgZW5jcnlwdGVkIGNvbnRlbnQsCiAg
IGhvd2V2ZXIsIHJlcXVpcmVzIHRoYXQgdGhlIEpPU0UgZW5jcnlwdGVkIG9iamVjdCBmb3JtYXQg
YWxsb3cgd3JhcHBlZAogICBzeW1tZXRyaWMga2V5cyB0byBiZSBjYXJyaWVkIHNlcGFyYXRlbHkg
ZnJvbSB0aGUgZW5jcnlwdGVkIHBheWxvYWQuCiAgIEluIGFkZGl0aW9uLCB0aGUgZW5jcnlwdGVk
IG9iamVjdCB3aWxsIG5lZWQgdG8gaGF2ZSBhIHRhZyBmb3IgdGhlIGtleQogICB0aGF0IHdhcyB1
c2VkIHRvIGVuY3J5cHQgdGhlIGNvbnRlbnQsIHNvIHRoYXQgdGhlIHJlY2lwaWVudCAoQm9iKSBj
YW4KICAgcHJlc2VudCB0aGUgdGFnIHRvIHRoZSBzZW5kZXIgKEFsaWNlKSB3aGVuIHJlcXVlc3Rp
bmcgdGhlIHdyYXBwZWQKICAga2V5LgoKICAgQW5vdGhlciBpbXBvcnRhbnQgZmVhdHVyZSBvZiBY
TVBQIGlzIHRoYXQgaXQgYWxsb3dzIGZvciB0aGUKICAgc2ltdWx0YW5lb3VzIGRlbGl2ZXJ5IG9m
IGEgbWVzc2FnZSB0byBtdWx0aXBsZSByZWNpcGllbnRzLiAgSW4gdGhlCiAgIGRpYWdyYW1zIGFi
b3ZlLCBTZXJ2ZXIgQSBjb3VsZCBkZWxpdmVyIHRoZSBtZXNzYWdlIG5vdCBvbmx5IHRvIFNlcnZl
cgogICBCIChmb3IgQm9iKSBidXQgYWxzbyB0byBTZXJ2ZXJzIEMsIEQsIEUsIGV0Yy4gZm9yIG90
aGVyIHVzZXJzLiAgSW4KICAgc3VjaCBjYXNlcywgdG8gYXZvaWQgdGhlIG11bHRpcGxlICJkaWFs
IGJhY2siIHRyYW5zYWN0aW9ucyBpbXBsaWVkIGJ5CiAgIHRoZSBhYm92ZSBtZWNoYW5pc20sIFhN
UFAgc3lzdGVtcyB3aWxsIGxpa2VseSBjYWNoZSBwdWJsaWMga2V5cyBmb3IKICAgZW5kIHJlY2lw
aWVudHMsIHNvIHRoYXQgd3JhcHBlZCBrZXlzIGNhbiBiZSBzZW50IGFsb25nIHdpdGggY29udGVu
dAogICBvbiBmdXR1cmUgbWVzc2FnZXMuICBUaGlzIGltcGxpZXMgdGhhdCB0aGUgSk9TRSBlbmNy
eXB0ZWQgb2JqZWN0CiAgIGZvcm1hdCBtdXN0IHN1cHBvcnQgdGhlIHByb3Zpc2lvbiBvZiBtdWx0
aXBsZSB2ZXJzaW9ucyBvZiB0aGUgc2FtZQogICB3cmFwcGVkIENFSyAobXVjaCBhcyBhIENNUyBF
bnZlbG9wZWREYXRhIHN0cnVjdHVyZSBjYW4gaW5jbHVkZQogICBtdWx0aXBsZSBSZWNpcGllbnRJ
bmZvIHN0cnVjdHVyZXMpLgoKICAgSW4gdGhlIGN1cnJlbnQgZHJhZnQgb2YgdGhlIFhNUFAgZW5k
LXRvLWVuZCBzZWN1cml0eSBzeXN0ZW0sIGVhY2gKICAgcGFydHkgaXMgYXV0aGVudGljYXRlZCBi
eSB2aXJ0dWUgb2YgdGhlIG90aGVyIHBhcnR5J3MgdHJ1c3QgaW4gdGhlCiAgIFhNUFAgbWVzc2Fn
ZSByb3V0aW5nIHN5c3RlbS4gIFRoZSBzZW5kZXIgaXMgYXV0aGVudGljYXRlZCB0byB0aGUKICAg
cmVjZWl2ZXIgYmVjYXVzZSBoZSBjYW4gcmVjZWl2ZSBtZXNzYWdlcyBmb3IgdGhlIGlkZW50aWZp
ZXIgIkFsaWNlIgogICAoaW4gcGFydGljdWxhciwgdGhlIHJlcXVlc3QgZm9yIHdyYXBwZWQga2V5
cyksIGFuZCBjYW4gb3JpZ2luYXRlCiAgIG1lc3NhZ2VzIGZvciB0aGF0IGlkZW50aWZpZXIgKHRo
ZSB3cmFwcGVkIGtleSkuICBMaWtld2lzZSwgdGhlCiAgIHJlY2VpdmVyIGlzIGF1dGhlbnRpY2F0
ZWQgdG8gdGhlIHNlbmRlciBiZWNhdXNlIGhlIHJlY2VpdmVkIHRoZQogICBvcmlnaW5hbCBlbmNy
eXB0ZWQgbWVzc2FnZSBhbmQgb3JpZ2luYXRlZCB0aGUgcmVxdWVzdCBmb3Igd3JhcHBlZAogICBr
ZXkuICBTbyB0aGUgYXV0aGVudGljYXRpb24gaGVyZSByZXF1aXJlcyBub3Qgb25seSB0aGF0IFhN
UFAgcm91dGluZwogICBiZSBkb25lIHByb3Blcmx5LCBidXQgYWxzbyB0aGF0IFRMUyBiZSB1c2Vk
IG9uIGV2ZXJ5IGhvcC4gIE1vcmVvdmVyLAogICBpdCByZXF1aXJlcyB0aGF0IHRoZSBUTFMgY2hh
bm5lbHMgaGF2ZSBzdHJvbmcgYXV0aGVudGljYXRpb24sIHNpbmNlIGEKICAgbWFuIGluIHRoZSBt
aWRkbGUgb24gYW55IG9mIHRoZSB0aHJlZSBob3BzIGNhbiBtYXNxdWVyYWRlIGFzIEJvYiBhbmQK
ICAgb2J0YWluIHRoZSBrZXkgbWF0ZXJpYWwgZm9yIGFuIGVuY3J5cHRlZCBtZXNzYWdlLgoKICAg
QmVjYXVzZSB0aGlzIGF1dGhlbnRpY2F0aW9uIGlzIHF1aXRlIHdlYWsgKGRlcGVuZGluZyBvbiB0
aGUgdXNlIG9mCiAgIHRyYW5zcG9ydC1sYXllciBzZWN1cml0eSBvbiB0aHJlZSBob3BzKSBhbmQg
dW52ZXJpZmlhYmxlIGJ5IHRoZQogICBlbmRwb2ludHMsIGl0IGlzIHBvc3NpYmxlIHRoYXQgdGhl
IFhNUFAgd29ya2luZyBncm91cCB3aWxsIGludGVncmF0ZQogICBzb21lIHNvcnQgb2YgY3JlZGVu
dGlhbHMgZm9yIGVuZCByZWNpcGllbnRzLCBpbiB3aGljaCBjYXNlIHRoZXJlCiAgIHdvdWxkIG5l
ZWQgdG8gYmUgYSB3YXkgdG8gYXNzb2NpYXRlIHRoZXNlIGNyZWRlbnRpYWxzIHdpdGggSk9TRQog
ICBvYmplY3RzLgoKICAgRmluYWxseSwgaXQncyB3b3J0aCBub3RpbmcgdGhhdCBYTVBQIGlzIGJh
c2VkIG9uIFhNTCwgbm90IEpTT04uICBTbwogICBieSB1c2luZyBKT1NFLCBYTVBQIHdpbGwgYmUg
Y2FycnlpbmcgSlNPTiBvYmplY3RzIHdpdGhpbiBYTUwuICBJdCBpcwogICB0aHVzIGEgZGVzaXJh
YmxlIHByb3BlcnR5IGZvciBKT1NFIG9iamVjdHMgdG8gYmUgZW5jb2RlZCBpbiBzdWNoIGEKICAg
d2F5IGFzIHRvIGJlIHNhZmUgZm9yIGluY2x1c2lvbiBpbiBYTUwuICBPdGhlcndpc2UsIGFuIGV4
cGxpY2l0IENEQVRBCgoKCkJhcm5lcyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIg
MjEsIDIwMTMgICAgICAgICAgICAgIFtQYWdlIDExXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAg
ICAgICAgSk9TRSBVc2UgQ2FzZXMgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAxMwoKCiAgIGlu
ZGljYXRpb24gbXVzdCBiZSBnaXZlbiB0byB0aGUgcGFyc2VyIHRvIGluZGljYXRlIHRoYXQgaXQg
aXMgbm90IHRvCiAgIGJlIHBhcnNlZCBhcyBYTUwuICBPbmUgd2F5IHRvIG1lZXQgdGhpcyByZXF1
aXJlbWVudCB3b3VsZCBiZSB0byBhcHBseQogICBiYXNlNjR1cmwgZW5jb2RpbmcsIGJ1dCBmb3Ig
WE1QUCBtZXNzYWdlcyBvZiBtZWRpdW0tdG8tbGFyZ2Ugc2l6ZSwKICAgdGhpcyBjb3VsZCBpbXBv
c2UgYSBmYWlyIGRlZ3JlZSBvZiBvdmVyaGVhZC4KCjUuNS4gIEFMVE8KCiAgIEFwcGxpY2F0aW9u
LUxheWVyIFRyYWZmaWMgT3B0aW1pemF0aW9uIChBTFRPKSBpcyBhIHN5c3RlbSBmb3IKICAgZGlz
dHJpYnV0aW5nIG5ldHdvcmsgdG9wb2xvZ3kgaW5mb3JtYXRpb24gdG8gZW5kIGRldmljZXMsIHNv
IHRoYXQKICAgdGhvc2UgZGV2aWNlcyBjYW4gbW9kaWZ5IHRoZWlyIGJlaGF2aW9yIHRvIGhhdmUg
YSBsb3dlciBpbXBhY3Qgb24gdGhlCiAgIG5ldHdvcmsgW1JGQzY3MDhdLiAgVGhlIEFMVE8gcHJv
dG9jb2wgZGlzdHJpYnV0ZXMgdG9wb2xvZ3kKICAgaW5mb3JtYXRpb24gaW4gdGhlIGZvcm0gb2Yg
SlNPTiBvYmplY3RzIGNhcnJpZWQgaW4gSFRUUAogICBbUkZDMjYxNl1bSS1ELmlldGYtYWx0by1w
cm90b2NvbF0uICBUaGUgYmFzaWMgdmVyc2lvbiBvZiBBTFRPIGlzCiAgIHNpbXBseSBhIGNsaWVu
dC1zZXJ2ZXIgcHJvdG9jb2wsIHNvIHNpbXBsZSB1c2Ugb2YgSFRUUFMgc3VmZmljZXMgZm9yCiAg
IHRoaXMgY2FzZSBbUkZDMjgxOF0uICBIb3dldmVyLCB0aGVyZSBpcyBiZWdpbm5pbmcgdG8gYmUg
c29tZQogICBkaXNjdXNzaW9uIG9mIHVzZSBjYXNlcyBmb3IgQUxUTyBpbiB3aGljaCB0aGVzZSBK
U09OIG9iamVjdHMgd2lsbCBiZQogICBkaXN0cmlidXRlZCB0aHJvdWdoIGEgY29sbGVjdGlvbiBv
ZiBpbnRlcm1lZGlhdGUgc2VydmVycyBiZWZvcmUKICAgcmVhY2hpbmcgdGhlIGNsaWVudCwgd2hp
bGUgc3RpbGwgcHJlc2VydmluZyB0aGUgYWJpbGl0eSBvZiB0aGUgY2xpZW50CiAgIHRvIGF1dGhl
bnRpY2F0ZSB0aGUgb3JpZ2luYWwgc291cmNlIG9mIHRoZSBvYmplY3QuICBFdmVuIHRoZSBiYXNl
CiAgIEFMVE8gcHJvdG9jb2wgbm90ZXMgdGhhdCAiQUxUTyBjbGllbnRzIG9idGFpbmluZyBBTFRP
IGluZm9ybWF0aW9uCiAgIG11c3QgYmUgYWJsZSB0byB2YWxpZGF0ZSB0aGUgcmVjZWl2ZWQgQUxU
TyBpbmZvcm1hdGlvbiB0byBlbnN1cmUgdGhhdAogICBpdCB3YXMgZ2VuZXJhdGVkIGJ5IGFuIGFw
cHJvcHJpYXRlIEFMVE8gc2VydmVyLiIKCiAgIEluIHRoaXMgY2FzZSwgdGhlIHNlY3VyaXR5IHJl
cXVpcmVtZW50cyBhcmUgc3RyYWlnaHRmb3J3YXJkLiAgSk9TRQogICBvYmplY3RzIGNhcnJ5aW5n
IEFMVE8gcGF5bG9hZHMgd2lsbCBuZWVkIHRvIGJlYXIgZGlnaXRhbCBzaWduYXR1cmVzCiAgIGZy
b20gdGhlIG9yaWdpbmF0aW5nIHNlcnZlcnMsIHdoaWNoIHdpbGwgYmUgYm91bmQgdG8gY2VydGlm
aWNhdGVzCiAgIGF0dGVzdGluZyB0byB0aGUgaWRlbnRpdGllcyBvZiB0aGUgc2VydmVycy4gIFRo
ZXJlIGlzIG5vIHJlcXVpcmVtZW50CiAgIGZvciBjb25maWRlbnRpYWxpdHkgaW4gdGhpcyBjYXNl
LCBzaW5jZSBBTFRPIGluZm9ybWF0aW9uIGlzIGdlbmVyYWxseQogICBwdWJsaWMuCgogICBUaGUg
bW9yZSBpbnRlcmVzdGluZyBxdWVzdGlvbnMgYXJlIGVuY29kaW5nIHF1ZXN0aW9ucy4gIEFMVE8g
b2JqZWN0cwogICBhcmUgbGlrZWx5IHRvIGJlIG11Y2ggbGFyZ2VyIHRoYW4gcGF5bG9hZHMgaW4g
dGhlIHR3byBjYXNlcyBhYm92ZSwKICAgd2l0aCBzaXplcyBvZiB1cCB0byBzZXZlcmFsIG1lZ2Fi
eXRlcy4gIFByb2Nlc3Npbmcgb2Ygc3VjaCBsYXJnZQogICBvYmplY3RzIGNhbiBiZSBkb25lIG1v
cmUgcXVpY2tseSBpZiBpdCBjYW4gYmUgZG9uZSBpbiBhIHNpbmdsZSBwYXNzLAogICB3aGljaCBt
YXkgYmUgcG9zc2libGUgaWYgSk9TRSBvYmplY3RzIHJlcXVpcmUgc3BlY2lmaWMgb3JkZXJpbmdz
IG9mCiAgIGZpZWxkcyB3aXRoaW4gdGhlIEpTT04gc3RydWN0dXJlLgoKICAgSW4gYWRkaXRpb24s
IGJlY2F1c2UgQUxUTyBvYmplY3RzIGFyZSBhbHNvIGVuY29kZWQgYXMgSlNPTiwgdGhleSBhcmUK
ICAgYWxyZWFkeSBzYWZlIGZvciBpbmNsdXNpb24gaW4gYSBKT1NFIG9iamVjdC4gIFNpZ25lZCBK
T1NFIG9iamVjdHMKICAgd2lsbCBsaWtlbHkgY2FycnkgdGhlIHNpZ25lZCBkYXRhIGluIGEgc3Ry
aW5nIGFsb25nc2lkZSB0aGUKICAgc2lnbmF0dXJlLiAgSlNPTiBvYmplY3RzIGhhdmUgdGhlIHBy
b3BlcnR5IHRoYXQgdGhleSBjYW4gYmUgc2FmZWx5CiAgIGVuY29kZWQgaW4gSlNPTiBzdHJpbmdz
LiAgQWxsIHRoZXkgcmVxdWlyZSBpcyB0aGF0IHVubmVjZXNzYXJ5IHdoaXRlCiAgIHNwYWNlIGJl
IHJlbW92ZWQsIGEgbXVjaCBzaW1wbGVyIHRyYW5zZm9ybWF0aW9uIHRoYW4sIHNheSBiYXNlNjR1
cmwKICAgZW5jb2RpbmcuICBUaGlzIHJhaXNlcyB0aGUgcXVlc3Rpb24gb2Ygd2hldGhlciBpdCBt
aWdodCBiZSBwb3NzaWJsZQogICB0byBvcHRpbWl6ZSB0aGUgSk9TRSBlbmNvZGluZyBmb3IgY2Vy
dGFpbiAiSlNPTi1zYWZlIiBjYXNlcy4KCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAgRXhw
aXJlcyBEZWNlbWJlciAyMSwgMjAxMyAgICAgICAgICAgICAgW1BhZ2UgMTJdCgwKSW50ZXJuZXQt
RHJhZnQgICAgICAgICAgICAgICBKT1NFIFVzZSBDYXNlcyAgICAgICAgICAgICAgICAgICAgSnVu
ZSAyMDEzCgoKNS42LiAgRW1lcmdlbmN5IEFsZXJ0aW5nCgogICBFbWVyZ2VuY3kgYWxlcnRpbmcg
aXMgYW4gZW1lcmdpbmcgdXNlIGNhc2UgZm9yIElQIG5ldHdvcmtzCiAgIFtJLUQuaWV0Zi1hdG9j
YS1yZXF1aXJlbWVudHNdLiAgQWxlcnRpbmcgc3lzdGVtcyBhbGxvdyBhdXRob3JpdGllcyB0bwog
ICB3YXJuIHVzZXJzIG9mIGltcGVuZGluZyBkYW5nZXIgYnkgc2VuZGluZyBhbGVydCBtZXNzYWdl
cyB0byBjb25uZWN0ZWQKICAgZGV2aWNlcy4gIEZvciBleGFtcGxlLCBpbiB0aGUgZXZlbnQgb2Yg
aHVycmljYW5lIG9yIHRvcm5hZG8sIGFsZXJ0cwogICBtaWdodCBiZSBzZW50IHRvIGFsbCBkZXZp
Y2VzIGluIHRoZSBwYXRoIG9mIHRoZSBzdG9ybS4KCiAgIFRoZSBtb3N0IGNyaXRpY2FsIHNlY3Vy
aXR5IHJlcXVpcmVtZW50IGZvciBhbGVydGluZyBzeXN0ZW1zIGlzIHRoYXQKICAgaXQgbXVzdCBu
b3QgYmUgcG9zc2libGUgZm9yIGFuIGF0dGFja2VyIHRvIHNlbmQgZmFsc2UgYWxlcnRzIHRvCiAg
IGRldmljZXMuICBTdWNoIGEgY2FwYWJpbGl0eSB3b3VsZCBwb3RlbnRpYWxseSBhbGxvdyBhbiBh
dHRhY2tlciB0bwogICBjcmVhdGUgd2lkZS1zcHJlYWQgcGFuaWMuICBJbiBwcmFjdGljZSwgYWxl
cnQgc3lzdGVtcyBwcmV2ZW50IHRoZXNlCiAgIGF0dGFja3MgYm90aCBieSBjb250cm9scyBvbiBz
ZW5kaW5nIG1lc3NhZ2VzIGF0IHBvaW50cyB3aGVyZSBhbGVydHMKICAgYXJlIG9yaWdpbmF0ZWQs
IGFzIHdlbGwgYXMgYnkgaGF2aW5nIHJlY2lwaWVudHMgb2YgYWxlcnRzIHZlcmlmeSB0aGF0CiAg
IHRoZSBhbGVydCB3YXMgc2VudCBieSBhbiBhdXRob3JpemVkIHNvdXJjZS4gIFRoZSBmb3JtZXIg
dHlwZSBvZgogICBjb250cm9sIGltcGxlbWVudGVkIHdpdGggbG9jYWwgc2VjdXJpdHkgb24gaG9z
dHMgZnJvbSB3aGljaCBhbGVydHMKICAgY2FuIGJlIG9yaWdpbmF0ZWQuICBUaGUgbGF0dGVyIHR5
cGUgaW1wbGVtZW50ZWQgYnkgZGlnaXRhbCBzaWduYXR1cmVzCiAgIG9uIGFsZXJ0IG1lc3NhZ2Vz
ICh1c2luZyBjaGFubmVsLWJhc2VkIG9yIG9iamVjdC1iYXNlZCBtZWNoYW5pc21zKS4KCiAgIEFs
ZXJ0cyB0eXBpY2FsbHkgcmVhY2ggZW5kIHJlY2lwaWVudHMgdmlhIGEgc2VyaWVzIG9mIGludGVy
bWVkaWFyaWVzLgogICBGb3IgZXhhbXBsZSwgd2hpbGUgYSBuYXRpb25hbCB3ZWF0aGVyIHNlcnZp
Y2UgbWlnaHQgb3JpZ2luYXRlIGEKICAgaHVycmljYW5lIGFsZXJ0LCBpdCBtaWdodCBmaXJzdCBi
ZSBkZWxpdmVyZWQgdG8gYSBuYXRpb25hbCBnYXRld2F5LAogICBhbmQgdGhlbiB0byBuZXR3b3Jr
IG9wZXJhdG9ycywgd2hvIGJyb2FkY2FzdCBpdCB0byBlbmQgc3Vic2NyaWJlcnMuCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgpCYXJuZXMgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2Vt
YmVyIDIxLCAyMDEzICAgICAgICAgICAgICBbUGFnZSAxM10KDApJbnRlcm5ldC1EcmFmdCAgICAg
ICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTMKCgog
ICAgICAgICAgICstLS0tLS0tLS0tLS0rICAgICstLS0tLS0tLS0tLS0rICAgICstLS0tLS0tLS0t
LS0rCiAgICAgICAgICAgfCBPcmlnaW5hdG9yIHwgICAgfCBPcmlnaW5hdG9yIHwgICAgfCBPcmln
aW5hdG9yIHwKICAgICAgICAgICArLS0tLS0tLS0tLS0tKyAgICArLS0tLS0tLS0tLS0tKyAgICAr
LS0tLS0tLS0tLS0tKwogICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgIC4gICAgICAg
ICAgICAgICAgIC4KICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLS0rLi4uLi4uLi4u
Li4uLi4uLi4uCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfAogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIFYKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
Ky0tLS0tLS0tLSsKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBHYXRld2F5IHwKICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLSsKICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tKy0t
LS0tLS0tLS0tLSsKICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAg
ICAgfAogICAgICAgICAgICAgICAgICAgICAgViAgICAgICAgICAgICAgICAgICAgICAgICBWCiAg
ICAgICAgICAgICAgICAgKy0tLS0tLS0tLSsgICAgICAgICAgICAgICArLS0tLS0tLS0tKwogICAg
ICAgICAgICAgICAgIHwgTmV0d29yayB8ICAgICAgICAgICAgICAgfCBOZXR3b3JrIHwKICAgICAg
ICAgICAgICAgICArLS0tLS0tLS0tKyAgICAgICAgICAgICAgICstLS0tLS0tLS0rCiAgICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAg
Ky0tLS0tLSstLS0tLSsgICAgICAgICAgICArLS0tLS0tKy0tLS0tKwogICAgICAgICAgICAgICB8
ICAgICAgICAgICAgfCAgICAgICAgICAgIHwgICAgICAgICAgICB8CiAgICAgICAgICAgICAgIFYg
ICAgICAgICAgICBWICAgICAgICAgICAgViAgICAgICAgICAgIFYKICAgICAgICAgICArLS0tLS0t
LS0rICAgKy0tLS0tLS0tKyAgICstLS0tLS0tLSsgICArLS0tLS0tLS0rCiAgICAgICAgICAgfCBE
ZXZpY2UgfCAgIHwgRGV2aWNlIHwgICB8IERldmljZSB8ICAgfCBEZXZpY2UgfAogICAgICAgICAg
ICstLS0tLS0tLSsgICArLS0tLS0tLS0rICAgKy0tLS0tLS0tKyAgICstLS0tLS0tLSsKCgogICAg
ICAgICAgICAgICAgICBGaWd1cmUgNDogRGVsaXZlcmluZyBhbiBlbWVyZ2VuY3kgYWxlcnQKCiAg
IEluIG9yZGVyIHRvIHZlcmlmeSBhbGVydCBzaWduYXR1cmVzLCByZWNpcGllbnRzIG11c3QgYmUg
cHJvdmlzaW9uZWQKICAgd2l0aCB0aGUgcHJvcGVyIHB1YmxpYyBrZXlzIGZvciB0cnVzdGVkIGFs
ZXJ0IGF1dGhvcml0aWVzLiAgVGhpcwogICB0cnVzdCBtYXkgYmUgInBpZWNlLXdpc2UiIGFsb25n
IHRoZSBwYXRoIHRoZSBhbGVydCB0YWtlcy4gIEZvcgogICBleGFtcGxlLCB0aGUgYWxlcnQgcmVs
YXlzIG9wZXJhdGVkIGJ5IG5ldHdvcmtzIG1pZ2h0IGhhdmUgYSBmdWxsIHNldAogICBvZiBjZXJ0
aWZpY2F0ZXMgZm9yIGFsbCBhbGVydCBvcmlnaW5hdG9ycywgd2hpbGUgZW5kIGRldmljZXMgbWF5
IG9ubHkKICAgdHJ1c3QgdGhlaXIgbG9jYWwgYWxlcnQgcmVsYXkuICBPciBkZXZpY2VzIG1pZ2h0
IHJlcXVpcmUgdGhhdCBhCiAgIGRldmljZSBiZSBzaWduZWQgYnkgYW4gYXV0aG9yaXplZCBvcmln
aW5hdG9yIGFuZCBieSBpdHMgbG9jYWwKICAgbmV0d29yaydzIHJlbGF5LgoKICAgVGhpcyBzY2Vu
YXJpbyBjcmVhdGVzIGEgbmVlZCBmb3IgbXVsdGlwbGUgc2lnbmF0dXJlcyBvbiBhbGVydAogICBk
b2N1bWVudHMsIHNvIHRoYXQgYW4gYWxlcnQgY2FuIGJlYXIgc2lnbmF0dXJlcyBmcm9tIGFueSBv
ciBhbGwgb2YKICAgdGhlIGVudGl0aWVzIHRoYXQgcHJvY2Vzc2VkIGl0IGFsb25nIHRoZSBwYXRo
LiAgSW4gb3JkZXIgdG8gbWluaW1pemUKICAgY29tcGxleGl0eSwgdGhlc2Ugc2lnbmF0dXJlcyBz
aG91bGQgYmUgIm1vZHVsYXIiLCBpbiB0aGUgc2Vuc2UgdGhhdCBhCiAgIG5ldyBzaWduYXR1cmUg
Y2FuIGJlIGFkZGVkIHdpdGhvdXQgYSBuZWVkIHRvIGFsdGVyIG9yIHJlY29tcHV0ZQogICBwcmV2
aW91cyBzaWduYXR1cmVzLgoKNS43LiAgV2ViIENyeXB0b2dyYXBoeQoKICAgVGhlIFczQyBXZWIg
Q3J5cHRvZ3JhcGh5IEFQSSBkZWZpbmVzIGEgc3RhbmRhcmQgY3J5cHRvZ3JhcGhpYyBBUEkgZm9y
CiAgIHRoZSBXZWIgW1dlYkNyeXB0b10uICBJZiBhIGJyb3dzZXIgZXhwb3NlcyB0aGlzIEFQSSwg
dGhlbiBKYXZhU2NyaXB0CgoKCkJhcm5lcyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1i
ZXIgMjEsIDIwMTMgICAgICAgICAgICAgIFtQYWdlIDE0XQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICAgICAgSk9TRSBVc2UgQ2FzZXMgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAxMwoKCiAg
IHByb3ZpZGVkIGFzIHBhcnQgb2YgYSBXZWIgcGFnZSBjYW4gYXNrIHRoZSBicm93c2VyIHRvIHBl
cmZvcm0KICAgY3J5cHRvZ3JhcGhpYyBvcGVyYXRpb25zLCBzdWNoIGFzIGRpZ2VzdCwgTUFDLCBl
bmNyeXB0aW9uLCBvciBkaWdpdGFsCiAgIHNpZ25pbmcuCgogICBPbmUgb2YgdGhlIGtleSByZWFz
b25zIHRvIGhhdmUgdGhlIGJyb3dzZXIgcGVyZm9ybSBjcnlwdG9ncmFwaGljCiAgIG9wZXJhdGlv
bnMgaXMgdG8gYXZvaWQgYWxsb3dpbmcgSmF2YVNjcmlwdCBjb2RlIHRvIGFjY2VzcyB0aGUga2V5
aW5nCiAgIG1hdGVyaWFsIHVzZWQgZm9yIHRoZXNlIG9wZXJhdGlvbnMuICBGb3IgZXhhbXBsZSwg
dGhpcyBzZXBhcmF0aW9uCiAgIHdvdWxkIHByZXZlbnQgY29kZSBpbmplY3RlZCB0aHJvdWdoIGEg
Y3Jvc3Mtc2l0ZSBzY3JpcHRpbmcgKFhTUykKICAgYXR0YWNrIGZyb20gcmVhZGluZyBhbmQgZXhm
aWx0cmF0aW5nIGtleXMgc3RvcmVkIHdpdGhpbiBhIGJyb3dzZXIuCiAgIFdoaWxlIHRoZSBtYWxp
Y2lvdXMgY29kZSBjb3VsZCBzdGlsbCB1c2UgdGhlIGtleSB3aGlsZSBydW5uaW5nIGluIHRoZQog
ICBicm93c2VyLCB0aGlzIHZ1bG5lcmFiaWxpdHkgY2FuIG9ubHkgYmUgZXhlcmNpc2VkIHdoaWxl
IHRoZQogICB2dWxuZXJhYmxlIHBhZ2UgaXMgYWN0aXZlIGluIGEgdXNlcidzIGJyb3dzZXIuCgog
ICBIb3dldmVyLCB0aGUgV2ViQ3J5cHRvZ3JhcGh5IEFQSSBhbHNvIHByb3ZpZGVzIGEga2V5IGV4
cG9ydAogICBmdW5jdGlvbmFsaXR5LCB3aGljaCBjYW4gYWxsb3cgSmF2YVNjcmlwdCB0byBleHRy
YWN0IGEga2V5IGZyb20gdGhlCiAgIEFQSSBpbiB3cmFwcGVkIGZvcm0uICBGb3IgZXhhbXBsZSwg
dGhlIEphdmFTY3JpcHQgbWlnaHQgcHJvdmlkZSBhCiAgIHB1YmxpYyBrZXkgZm9yIHdoaWNoIHRo
ZSBjb3JyZXNwb25kaW5nIHByaXZhdGUga2V5IGlzIGhlbGQgYnkgYW5vdGhlcgogICBkZXZpY2Uu
ICBUaGUgd3JhcHBlZCBrZXkgcHJvdmlkZWQgYnkgdGhlIEFQSSBjb3VsZCB0aGVuIGJlIHVzZWQg
dG8KICAgc2FmZWx5IHRyYW5zcG9ydCB0aGUga2V5IHRvIHRoZSBuZXcgZGV2aWNlLiAgV2hpbGUg
dGhpcyBjb3VsZAogICBwb3RlbnRpYWxseSBhbGxvdyBtYWxpY2lvdXMgY29kZSB0byBleHBvcnQg
YSBrZXksIHRoZSBuZWVkIGZvciBhbgogICBleHBsaWNpdCBleHBvcnQgb3BlcmF0aW9uIHByb3Zp
ZGVzIGEgY29udHJvbCBwb2ludCwgYWxsb3dpbmcgZm9yIHVzZXIKICAgbm90aWZpY2F0aW9uIG9y
IGNvbnNlbnQgdmVyaWZpY2F0aW9uLgoKICAgVGhlIFdlYiBDcnlwdG9ncmFwaHkgQVBJIGFsc28g
YWxsb3dzIGJyb3dzZXJzIHRvIGltcG9zZSBsaW1pdGF0aW9ucwogICBvbiB0aGUgdXNhZ2Ugb2Yg
dGhlIGtleXMgaXQgaGFuZGxlcy4gIEZvciBleGFtcGxlLCBhIHN5bW1ldHJpYyBrZXkKICAgbWln
aHQgYmUgbWFya2VkIGFzIHVzYWJsZSBvbmx5IGZvciBlbmNyeXB0aW9uLCBhbmQgbm90IGZvciBN
QUMuICBXaGVuCiAgIGEga2V5IGlzIGV4cG9ydGVkIGluIHdyYXBwZWQgZm9ybSwgdGhlc2UgYXR0
cmlidXRlcyBzaG91bGQgYmUgY2FycmllZAogICBhbG9uZyB3aXRoIGl0LgoKICAgVGhlIFdlYiBD
cnlwdG9ncmFwaHkgQVBJIHRodXMgcmVxdWlyZXMgZm9ybWF0cyB0byBleHByZXNzIHNldmVyYWwK
ICAgZm9ybXMgb2Yga2V5cy4gIE9idmlvdXNseSwgdGhlIHB1YmxpYyBrZXkgZnJvbSBhbiBhc3lt
bWV0cmljIGtleSBwYWlyCiAgIGNhbiBiZSBmcmVlbHkgaW1wb3J0ZWQgdG8gYW5kIGV4cG9ydGVk
IGZyb20gdGhlIGJyb3dzZXIsIHNvIHRoZXJlCiAgIG5lZWRzIHRvIGJlIGEgZm9ybWF0IGZvciBw
dWJsaWMga2V5cy4gIFRoZXJlIGlzIGFsc28gYSBuZWVkIGZvciBhCiAgIGZvcm1hdCB0byBleHBy
ZXNzIHByaXZhdGUga2V5cyBhbmQgc3ltbWV0cmljIGtleXMuICBGb3Igbm9uLXB1YmxpYwogICBr
ZXlzLCB0aGUgcHJpbWFyeSBuZWVkIGlzIGZvciBhIHdyYXBwZWQgZm9ybSwgd2hlcmUgdGhlCiAg
IGNvbmZpZGVudGlhbGl0eSBhbmQgaW50ZWdyaXR5IG9mIHRoZSBrZXkgaXMgYXNzdXJlZAogICBj
cnlwdG9ncmFwaGljYWxseTsgdGhlc2UgcHJvdGVjdGlvbnMgc2hvdWxkIGFsc28gYXBwbHkgdG8g
YW55CiAgIGF0dHJpYnV0ZXMgb2YgdGhlIGtleS4gIEl0IG1heSBhbHNvIGJlIHVzZWZ1bCB0byBk
ZWZpbmUgYSBkaXJlY3QsCiAgIHVud3JhcHBlZCBmb3JtYXQsIGZvciB1c2Ugd2l0aGluIGEgc2Vj
dXJpdHkgYm91bmRhcnkuCgo1LjguICBTbWFsbCBEZXZpY2VzCgogICBBIHNtYWxsLCBsb3cgcG93
ZXIgZGV2aWNlIG1ha2VyIGhhcyBkZWNpZGVkIG9uIHVzaW5nIHRoZSBvdXRwdXQgb2YKICAgdGhl
IEpPU0Ugd29ya2luZyBncm91cCBhcyB0aGVpciBlbmNyeXB0aW9uIGFuZCBhdXRoZW50aWNhdGlv
bgogICBmcmFtZXdvcmsuICBUaGUgZGV2aWNlIG1ha2VyIGhhcyBhIGxpbWl0ZWQgYXZhaWxhYmls
aXR5IG9mIGJvdGggcmVhbAogICBlc3RhdGUgZm9yIGdhdGVzIGFuZCBwb3dlci4gIEZvciB0aGlz
IHJlYXNvbiB0aGVyZSBhcmUgYSBudW1iZXIgb2YKICAgc2hvcnQgY3V0cyBhbmQgZGVzaWduIGRl
Y2lzaW9ucyB0aGF0IGhhdmUgYmVlbiBtYWRlIGluIG9yZGVyIHRvCiAgIG1pbmltaXplIHRoZXNl
IG5lZWRzLgoKCgpCYXJuZXMgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAy
MDEzICAgICAgICAgICAgICBbUGFnZSAxNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAg
IEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTMKCgogICBUaGUgZGVz
aWduIHRlYW0gaGFzIGRldGVybWluZWQgdGhhdCB0aGUgdXNlIG9mIG1lc3NhZ2UgYXV0aGVudGlj
YXRpb24KICAgY29kZXMgKE1BQykgaXMgZ29pbmcgdG8gYmUgc3VmZmljaWVudCB0byBwcm92aWRl
IHRoZSBuZWNlc3NhcnkKICAgYXV0aGVudGljYXRpb24uICBIb3dldmVyLCBhbHRob3VnaCBhIE1B
QyBpcyBnb2luZyB0byBiZSB1c2VkLCB0aGV5IGRvCiAgIG5vdCB3YW50IHRvIHVzZSBhIHNpbmds
ZSBsb25nIHRlcm0gc2hhcmVkIHNlY3JldC4gIEluc3RlYWQgdGhleSBoYXZlCiAgIGFkb3B0ZWQg
dGhlIGZvbGxvd2luZyBwcm9wb3NhbCBmb3IgY29tcHV0aW5nIGEgc2hhcmVkIHNlY3JldCB0aGF0
IGNhbgogICBiZSB2YWxpZGF0ZWQ6CgogICBvICBBbiBFbGxpcHRpYy1DdXJ2ZSBEaWZmaWUtSGVs
bG1hbiAoRUNESCkga2V5IGlzIGdlbmVyYXRlZCBmb3IgdGhlCiAgICAgIGRldmljZSBhdCB0aGUg
dGltZSBvZiBtYW51ZmFjdHVyaW5nLiAgKE9yIGFzIHBhcnQgb2YgdGhlCiAgICAgIGNvbmZpZ3Vy
YXRpb24gcHJvY2VzcyBkdXJpbmcgaW5zdGFsbGF0aW9uLikKCiAgIG8gIEFuIEVDREggcHVibGlj
IGtleSBmb3IgdGhlIGNvbnRyb2xsZXIgaXMgY29uZmlndXJlZCBhdCB0aGUgdGltZSBvZgogICAg
ICBjb25maWd1cmF0aW9uLgoKICAgbyAgVGhlIGNvbmZpZ3VyYXRpb24gc3lzdGVtIHBlcmZvcm1z
IHRoZSBleHBvbmVudGlhdGlvbiBhbmQKICAgICAgY29uZmlndXJlcyB0aGUgZGV2aWNlIHdpdGgg
dGhlIHJlc3VsdGluZyBzaGFyZWQgc2VjcmV0LiAgVGhpcwogICAgICBwcm9jZXNzIGVsaW1pbmF0
ZXMgdGhlIG5lZWQgZm9yIHRoZSBkZXZpY2UgdG8gYmUgYWJsZSB0byBwZXJmb3JtCiAgICAgIHRo
ZSByZXF1aXJlZCBleHBvbmVudGlhdGlvbiBwcm9jZXNzaW5nLiAgVGhlIHNlY3VyaXR5IHJlcXVp
cmVtZW50cwogICAgICBvbiBwcm90ZWN0aW5nIHRoaXMgY29tcHV0ZWQgc2hhcmVkIHNlY3JldCBh
cmUgdGhlIHNhbWUgYXMgdGhlCiAgICAgIHJlcXVpcmVtZW50cyBvbiBwcm90ZWN0aW5nIHRoZSBw
cml2YXRlIEVDREgga2V5LgoKICAgbyAgQSBjb3VudGVyIGFuZCBhbiBpbmNyZW1lbnQgdmFsdWUg
YXJlIGNvbmZpZ3VyZWQgb250byB0aGUgZGV2aWNlLgoKICAgbyAgV2hlbiBhIG1lc3NhZ2UgaXMg
dG8gYmUgc2VudCBieSB0aGUgZGV2aWNlLCB0aGUgY291bnRlciBpcwogICAgICBpbmNyZW1lbnRl
ZCBhbmQgYSBuZXcgTUFDIGtleSBpcyBjb21wdXRlZCBmcm9tIHRoZSBFQ0RIIHNlY3JldCBhbmQK
ICAgICAgdGhlIGNvdW50ZXIgdmFsdWUuICBBIGN1c3RvbSBLZXkgRGVyaXZhdGlvbiBGdW5jdGlv
biAoS0RGKQogICAgICBmdW5jdGlvbiBpcyB1c2VkIHdoZW4gaXMgYmFzZWQgb24gdGhlIEFFUy1D
QkMgaXMgdXNlZCB0byBkZXJpdmUKICAgICAgdGhlIHJlcXVpcmVkIE1BQyBrZXkuICBUaGUgTUFD
IGtleSBpcyB0aGVuIHVzZWQgdG8gY29tcHV0ZSB0aGUgTUFDCiAgICAgIHZhbHVlIGZvciB0aGUg
bWVzc2FnZS4KCiAgIEluIGEgc2ltaWxhciBtYW5uZXIgdGhlIEtERiBmdW5jdGlvbiBjYW4gdXNl
ZCB0byBjb21wdXRlIGFuIEFFQUQKICAgYWxnb3JpdGhtIGtleSB3aGVuIHRoZSBzeXN0ZW0gbmVl
ZHMgdG8gcHJvdmlkZSBjb25maWRlbnRpYWxseSBmb3IgdGhlCiAgIG1lc3NhZ2UuICBUaGUgY29u
dHJvbGxlciwgYmVpbmcgYSBsYXJnZXIgZGV2aWNlIHdpbGwgcGVyZm9ybSB0aGUKICAgZXhwb25l
bnRpYXRpb24gc3RlcCBhbmQgdXNlIGEgcmFuZG9tIG51bWJlciBnZW5lcmF0b3IgdG8gZ2VuZXJh
dGUgdGhlCiAgIHNlbmRlciBub25jZSB2YWx1ZS4KCgo2LiAgUmVxdWlyZW1lbnRzCgogICBUaGlz
IHNlY3Rpb24gc3VtbWFyaXplcyB0aGUgcmVxdWlyZW1lbnRzIGZyb20gdGhlIGFib3ZlIHVzZXMg
Y2FzZXMsCiAgIGFuZCBsaXN0cyBmdXJ0aGVyIHJlcXVpcmVtZW50cyBub3QgZGlyZWN0bHkgZGVy
aXZlZCBmcm9tIHRoZSBhYm92ZQogICB1c2UgY2FzZXMuICBUaGVyZSBhcmUgYWxzbyBzb21lIGNv
bnN0cmFpbnRzIHRoYXQgYXJlIG5vdCBoYXJkCiAgIHJlcXVpcmVtZW50cywgYnV0IHdoaWNoIGFy
ZSBzdGlsbCBkZXNpcmFibGUgcHJvcGVydGllcyBmb3IgdGhlIEpPU0UKICAgc3lzdGVtIHRvIGhh
dmUuCgoKCgoKCgpCYXJuZXMgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAy
MDEzICAgICAgICAgICAgICBbUGFnZSAxNl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAg
IEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAgICAgICBKdW5lIDIwMTMKCgo2LjEuICBGdW5j
dGlvbmFsIFJlcXVpcmVtZW50cwoKICAgRjEgRGVmaW5lIGZvcm1hdHMgZm9yIHNlY3VyZSBvYmpl
Y3RzIHRoYXQgcHJvdmlkZSB0aGUgZm9sbG93aW5nCiAgICAgIHNlY3VyaXR5IHByb3BlcnRpZXM6
CgogICAgICAqICBEaWdpdGFsIHNpZ25hdHVyZSAoaW50ZWdyaXR5L2F1dGhlbnRpY2F0aW9uIHVu
ZGVyIGFuIGFzeW1tZXRyaWMKICAgICAgICAga2V5IHBhaXIpCgogICAgICAqICBNZXNzYWdlIGF1
dGhlbnRpY2F0aW9uIChpbnRlZ3JpdHkvYXV0aGVudGljYXRpb24gdW5kZXIgYQogICAgICAgICBz
eW1tZXRyaWMga2V5KQoKICAgICAgKiAgRW5jcnlwdGlvbgoKICAgICAgKiAgQXV0aGVudGljYXRl
ZCBlbmNyeXB0aW9uCgogICAgICBUaGF0IGlzLCB0aGUgc2VjdXJlIG9iamVjdHMgZGVmaW5lZCBi
eSB0aGlzIHdvcmtpbmcgZ3JvdXAgc2hvdWxkCiAgICAgIHByb3ZpZGUgZXF1aXZhbGVudCBzZWN1
cml0eSBwcm9wZXJ0aWVzIHRvIHRoZSBDTVMgU2lnbmVkRGF0YSwKICAgICAgQXV0aGVudGljYXRl
ZERhdGEsIEVudmVsb3BlZERhdGEsIGFuZCBBdXRoRW52ZWxvcGVkIGRhdGEgb2JqZWN0cwogICAg
ICBbUkZDNTY1Ml0gW1JGQzUwODNdLgoKICAgRjIgRGVmaW5lIGEgZm9ybWF0IGZvciBwdWJsaWMg
a2V5cyBhbmQgcHJpdmF0ZSBrZXlzIGZvciBhc3ltbWV0cmljCiAgICAgIGNyeXB0b2dyYXBoaWMg
YWxnb3JpdGhtcywgd2l0aCBhc3NvY2lhdGVkIGF0dHJpYnV0ZXMsIGluY2x1ZGluZyBhCiAgICAg
IHdyYXBwZWQgZm9ybSBmb3IgcHJpdmF0ZSBrZXlzLgoKICAgRjMgRGVmaW5lIGEgZm9ybWF0IGZv
ciBzeW1tZXRyaWMga2V5cyB3aXRoIGFzc29jaWF0ZWQgYXR0cmlidXRlcywKICAgICAgYWxsb3dp
bmcgZm9yIGJvdGggd3JhcHBlZCBhbmQgdW53cmFwcGVkIGtleXMuCgogICBGNCBEZWZpbmUgSlNP
TiBzZXJpYWxpemF0aW9ucyBmb3IgdGhlIGFib3ZlIG9iamVjdHMuICBBbiBvYmplY3QgaW4KICAg
ICAgdGhpcyBlbmNvZGluZyBtdXN0IGJlIHZhbGlkIGFjY29yZGluZyB0byB0aGUgSlNPTiBBQk5G
IHN5bnRheAogICAgICBbUkZDNDYyN10KCiAgIEY1IERlZmluZSBjb21wYWN0LCBVUkwtc2FmZSB0
ZXh0IHNlcmlhbGl6YXRpb25zIGZvciB0aGUgYWJvdmUKICAgICAgb2JqZWN0cy4KCiAgIEY2IEFs
bG93IGZvciBhdHRyaWJ1dGVzIGFzc29jaWF0ZWQgdG8gd3JhcHBlZCBrZXlzIHRvIGJlIGJvdW5k
IHRvCiAgICAgIHRoZW0gY3J5cHRvZ3JhcGhpY2FsbHkKCiAgIEY3IEFsbG93IGZvciB3cmFwcGVk
IGtleXMgdG8gYmUgc2VwYXJhdGVkIGZyb20gYSBzZWN1cmUgb2JqZWN0IHRoYXQKICAgICAgdXNl
cyBhIHN5bW1ldHJpYyBrZXkuICBJbiBzdWNoIGNhc2VzLCBjcnlwdG9ncmFwaGljIGNvbXBvbmVu
dHMgb2YKICAgICAgdGhlIHNlY3VyZSBvYmplY3Qgb3RoZXIgdGhhbiB0aGUgd3JhcHBlZCBrZXkg
KGUuZy4sIGNpcGhlcnRleHQsCiAgICAgIE1BQyB2YWx1ZXMpIG11c3QgYmUgaW5kZXBlbmRlbnQg
b2YgdGhlIHdyYXBwZWQgZm9ybSBvZiB0aGUga2V5LgogICAgICBGb3IgZXhhbXBsZSwgaWYgYW4g
ZW5jcnlwdGVkIG9iamVjdCBpcyBwcmVwYXJlZCBmb3IgbXVsdGlwbGUKICAgICAgcmVjaXBpZW50
cywgdGhlbiBvbmx5IHRoZSB3cmFwcGVkIGtleSBtYXkgdmFyeSwgbm90IHRoZQogICAgICBjaXBo
ZXJ0ZXh0LgoKCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAy
MSwgMjAxMyAgICAgICAgICAgICAgW1BhZ2UgMTddCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAg
ICAgICBKT1NFIFVzZSBDYXNlcyAgICAgICAgICAgICAgICAgICAgSnVuZSAyMDEzCgoKNi4yLiAg
U2VjdXJpdHkgUmVxdWlyZW1lbnRzCgogICBTMSBQcm92aWRlIGtleSBtYW5hZ2VtZW50IGZ1bmN0
aW9ucyBmb3IgZXBoZW1lcmFsIHN5bW1ldHJpYyBrZXlzLAogICAgICBpbmNsdWRpbmcgZW5jcnlw
dGlvbiBrZXlzIGFuZCBNQUMga2V5cy4gIEl0IHNob3VsZCBiZSBwb3NzaWJsZSB0bwogICAgICB1
c2UgYW55IG9mIHRoZSBrZXkgbWFuYWdlbWVudCB0ZWNobmlxdWVzIHByb3ZpZGVkIGluIENNUwog
ICAgICBbUkZDNTY1Ml06CgogICAgICAqICBLZXkgdHJhbnNwb3J0ICh3cmFwcGluZyBmb3IgYSBw
dWJsaWMga2V5KQoKICAgICAgKiAgS2V5IGVuY2lwaGVybWVudCAod3JhcHBpbmcgZm9yIGEgc3lt
bWV0cmljIGtleSkKCiAgICAgICogIEtleSBhZ3JlZW1lbnQgKHdyYXBwaW5nIGZvciBhIERIIHB1
YmxpYyBrZXkpCgogICAgICAqICBQYXNzd29yZC1iYXNlZCBlbmNyeXB0aW9uICh3cmFwcGluZyB1
bmRlciBhIGtleSBkZXJpdmVkIGZyb20gYQogICAgICAgICBwYXNzd29yZCkKCiAgIFMyIFVzZSBj
cnlwdG9ncmFwaGljIGFsZ29yaXRobXMgaW4gYSBtYW5uZXIgY29tcGF0aWJsZSB3aXRoIG1ham9y
CiAgICAgIHZhbGlkYXRpb24gcHJvY2Vzc2VzLiAgRm9yIGV4YW1wbGUsIGlmIGEgRklQUyBzdGFu
ZGFyZCBhbGxvd3MKICAgICAgYWxnb3JpdGhtIEEgdG8gYmUgdXNlZCBmb3IgcHVycG9zZSBYIGJ1
dCBub3QgcHVycG9zZSBZLCB0aGVuIEpPU0UKICAgICAgc2hvdWxkIG5vdCByZWNvbW1lbmQgdXNp
bmcgYWxnb3JpdGhtIEEgZm9yIHB1cnBvc2UgWS4KCiAgIFMzIFN1cHBvcnQgb3BlcmF0aW9uIHdp
dGggb3Igd2l0aG91dCBwcmUtbmVnb3RpYXRpb24uICBJdCBtdXN0IGJlCiAgICAgIHBvc3NpYmxl
IHRvIGNyZWF0ZSBvciBwcm9jZXNzIHNlY3VyZSBvYmplY3RzIHdpdGhvdXQgYW55CiAgICAgIGNv
bmZpZ3VyYXRpb24gYmV5b25kIGtleSBwcm92aXNpb25pbmcuICBJZiBpdCBpcyBwb3NzaWJsZSBm
b3Iga2V5cwogICAgICB0byBiZSBkZXJpdmVkIGZyb20gYXBwbGljYXRpb24gY29udGV4dCwgaXQg
bXVzdCBiZSBwb3NzaWJsZSBmb3IgYQogICAgICByZWNpcGllbnQgdG8gcmVjb2duaXplIHdoZW4g
aXQgZG9lcyBub3QgaGF2ZSB0aGUgYXBwcm9wcmlhdGUga2V5CiAgICAgIGluIHRoZSBjYXNlIHRo
YXQgdGhlIGFwcGxpY2F0aW9uIGRvZXMgbm90IHNwZWNpZnkgdGhlIHVzZSBvZgogICAgICBhbm90
aGVyIG1lYW5zIG9yIGNvbnZlbnRpb24gdG8gZGV0ZXJtaW5lIHRoZSBrZXkgdXNlZC4KCjYuMy4g
IERlc2lkZXJhdGEKCiAgIEQxIE1heGltaXplIGNvbXBhdGliaWxpdHkgd2l0aCB0aGUgVzNDIFdl
YkNyeXB0byBzcGVjaWZpY2F0aW9ucywKICAgICAgZS5nLiwgYnkgY29vcmRpbmF0aW5nIHdpdGgg
dGhlIFdlYkNyeXB0byB3b3JraW5nIGdyb3VwIHRvCiAgICAgIGVuY291cmFnZSBhbGlnbm1lbnQg
b2YgYWxnb3JpdGhtcyBhbmQgYWxnb3JpdGhtIGlkZW50aWZpZXJzIHRvIHRoZQogICAgICBleHRl
bnQgdGhhdCBpdCBtYWtlcyBzZW5zZSBpbiB0aGUgc29tZXdoYXQgZGlmZmVyZW50IFdlYkNyeXB0
byBhbmQKICAgICAgSk9TRSBhcHBsaWNhdGlvbiBjb250ZXh0cy4KCiAgIEQyIEF2b2lkIEpTT04g
Y2Fub25pY2FsaXphdGlvbiB0byB0aGUgZXh0ZW50IHBvc3NpYmxlLiAgVGhhdCBpcywgYWxsCiAg
ICAgIG90aGVyIHRoaW5ncyBiZWluZyBlcXVhbCwgdGVjaG5pcXVlcyB0aGF0IHJlbHkgb24gZml4
aW5nIGEKICAgICAgc2VyaWFsaXphdGlvbiBvZiBhbiBvYmplY3QgKGUuZy4sIGJ5IGJhc2U2NHVy
bCBlbmNvZGluZyBpdCkgYXJlCiAgICAgIHByZWZlcnJlZCBvdmVyIHRob3NlIHRoYXQgcmVxdWly
ZSBjb252ZXJ0aW5nIGFuIG9iamVjdCB0byBhCiAgICAgIGNhbm9uaWNhbCBmb3JtLgoKCjcuICBJ
QU5BIENvbnNpZGVyYXRpb25zCgogICBUaGlzIGRvY3VtZW50IG1ha2VzIG5vIHJlcXVlc3Qgb2Yg
SUFOQS4KCgoKCkJhcm5lcyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjEsIDIw
MTMgICAgICAgICAgICAgIFtQYWdlIDE4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAg
Sk9TRSBVc2UgQ2FzZXMgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAxMwoKCjguICBTZWN1cml0
eSBDb25zaWRlcmF0aW9ucwoKICAgVGhlIHByaW1hcnkgZm9jdXMgb2YgdGhpcyBkb2N1bWVudCBp
cyB0aGUgcmVxdWlyZW1lbnRzIGZvciBhIEpTT04tCiAgIGJhc2VkIHNlY3VyZSBvYmplY3QgZm9y
bWF0LiAgQXQgdGhlIGxldmVsIG9mIGdlbmVyYWwgc2VjdXJpdHkKICAgY29uc2lkZXJhdGlvbnMg
Zm9yIG9iamVjdC1iYXNlZCBzZWN1cml0eSB0ZWNobm9sb2dpZXMsIHRoZSBzZWN1cml0eQogICBj
b25zaWRlcmF0aW9ucyBmb3IgdGhpcyBmb3JtYXQgYXJlIHRoZSBzYW1lIGFzIGZvciBDTVMgW1JG
QzU2NTJdLgogICBUaGUgcHJpbWFyeSBkaWZmZXJlbmNlIGJldHdlZW4gdGhlIEpPU0UgZm9ybWF0
IGFuZCBDTVMgaXMgdGhhdCBKT1NFCiAgIGlzIGJhc2VkIG9uIEpTT04sIHdoaWNoIGRvZXMgbm90
IGhhdmUgYSBjYW5vbmljYWwgcmVwcmVzZW50YXRpb24uCiAgIFRoZSBsYWNrIG9mIGEgY2Fub25p
Y2FsIGZvcm0gbWVhbnMgdGhhdCBpdCBpcyBkaWZmaWN1bHQgdG8gZGV0ZXJtaW5lCiAgIHdoZXRo
ZXIgdHdvIEpTT04gb2JqZWN0cyByZXByZXNlbnQgdGhlIHNhbWUgaW5mb3JtYXRpb24sIHdoaWNo
IGNvdWxkCiAgIGxlYWQgdG8gdnVsbmVyYWJpbGl0aWVzIGluIHNvbWUgdXNhZ2VzIG9mIEpPU0Uu
CgoKOS4gIFJlZmVyZW5jZXMKCjkuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBbUkZDNDYy
N10gIENyb2NrZm9yZCwgRC4sICJUaGUgYXBwbGljYXRpb24vanNvbiBNZWRpYSBUeXBlIGZvcgog
ICAgICAgICAgICAgIEphdmFTY3JpcHQgT2JqZWN0IE5vdGF0aW9uIChKU09OKSIsIFJGQyA0NjI3
LCBKdWx5IDIwMDYuCgogICBbUkZDNDY0OF0gIEpvc2Vmc3NvbiwgUy4sICJUaGUgQmFzZTE2LCBC
YXNlMzIsIGFuZCBCYXNlNjQgRGF0YQogICAgICAgICAgICAgIEVuY29kaW5ncyIsIFJGQyA0NjQ4
LCBPY3RvYmVyIDIwMDYuCgogICBbUkZDNDk0OV0gIFNoaXJleSwgUi4sICJJbnRlcm5ldCBTZWN1
cml0eSBHbG9zc2FyeSwgVmVyc2lvbiAyIiwKICAgICAgICAgICAgICBSRkMgNDk0OSwgQXVndXN0
IDIwMDcuCgogICBbUkZDNTA4M10gIEhvdXNsZXksIFIuLCAiQ3J5cHRvZ3JhcGhpYyBNZXNzYWdl
IFN5bnRheCAoQ01TKQogICAgICAgICAgICAgIEF1dGhlbnRpY2F0ZWQtRW52ZWxvcGVkLURhdGEg
Q29udGVudCBUeXBlIiwgUkZDIDUwODMsCiAgICAgICAgICAgICAgTm92ZW1iZXIgMjAwNy4KCiAg
IFtSRkM1NjUyXSAgSG91c2xleSwgUi4sICJDcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChD
TVMpIiwgU1REIDcwLAogICAgICAgICAgICAgIFJGQyA1NjUyLCBTZXB0ZW1iZXIgMjAwOS4KCiAg
IFtSRkM2MTIwXSAgU2FpbnQtQW5kcmUsIFAuLCAiRXh0ZW5zaWJsZSBNZXNzYWdpbmcgYW5kIFBy
ZXNlbmNlCiAgICAgICAgICAgICAgUHJvdG9jb2wgKFhNUFApOiBDb3JlIiwgUkZDIDYxMjAsIE1h
cmNoIDIwMTEuCgogICBbUkZDNjcwOF0gIEtpZXNlbCwgUy4sIFByZXZpZGksIFMuLCBTdGllbWVy
bGluZywgTS4sIFdvdW5keSwgUi4sIGFuZAogICAgICAgICAgICAgIFkuIFlhbmcsICJBcHBsaWNh
dGlvbi1MYXllciBUcmFmZmljIE9wdGltaXphdGlvbiAoQUxUTykKICAgICAgICAgICAgICBSZXF1
aXJlbWVudHMiLCBSRkMgNjcwOCwgU2VwdGVtYmVyIDIwMTIuCgogICBbUkZDNjc0OV0gIEhhcmR0
LCBELiwgIlRoZSBPQXV0aCAyLjAgQXV0aG9yaXphdGlvbiBGcmFtZXdvcmsiLAogICAgICAgICAg
ICAgIFJGQyA2NzQ5LCBPY3RvYmVyIDIwMTIuCgogICBbUkZDNjc1MF0gIEpvbmVzLCBNLiBhbmQg
RC4gSGFyZHQsICJUaGUgT0F1dGggMi4wIEF1dGhvcml6YXRpb24KICAgICAgICAgICAgICBGcmFt
ZXdvcms6IEJlYXJlciBUb2tlbiBVc2FnZSIsIFJGQyA2NzUwLCBPY3RvYmVyIDIwMTIuCgogICBb
VzNDLkNSLXhtbGRzaWctY29yZTItMjAxMjAxMjRdCiAgICAgICAgICAgICAgRWFzdGxha2UsIEQu
LCBSZWFnbGUsIEouLCBZaXUsIEsuLCBTb2xvLCBELiwgRGF0dGEsIFAuLAoKCgpCYXJuZXMgICAg
ICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAgICBbUGFn
ZSAxOV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAg
ICAgICAgICAgICAgICBKdW5lIDIwMTMKCgogICAgICAgICAgICAgIEhpcnNjaCwgRi4sIENhbnRv
ciwgUy4sIGFuZCBULiBSb2Vzc2xlciwgIlhNTCBTaWduYXR1cmUKICAgICAgICAgICAgICBTeW50
YXggYW5kIFByb2Nlc3NpbmcgVmVyc2lvbiAyLjAiLCBXb3JsZCBXaWRlIFdlYgogICAgICAgICAg
ICAgIENvbnNvcnRpdW0gQ1IgQ1IteG1sZHNpZy1jb3JlMi0yMDEyMDEyNCwgSmFudWFyeSAyMDEy
LAogICAgICAgICAgICAgIDxodHRwOi8vd3d3LnczLm9yZy9UUi8yMDEyL0NSLXhtbGRzaWctY29y
ZTItMjAxMjAxMjQ+LgoKICAgW1czQy5DUi14bWxlbmMtY29yZTEtMjAxMjAzMTNdCiAgICAgICAg
ICAgICAgRWFzdGxha2UsIEQuLCBSZWFnbGUsIEouLCBSb2Vzc2xlciwgVC4sIGFuZCBGLiBIaXJz
Y2gsCiAgICAgICAgICAgICAgIlhNTCBFbmNyeXB0aW9uIFN5bnRheCBhbmQgUHJvY2Vzc2luZyBW
ZXJzaW9uIDEuMSIsIFdvcmxkCiAgICAgICAgICAgICAgV2lkZSBXZWIgQ29uc29ydGl1bSBDUiBD
Ui14bWxlbmMtY29yZTEtMjAxMjAzMTMsCiAgICAgICAgICAgICAgTWFyY2ggMjAxMiwKICAgICAg
ICAgICAgICA8aHR0cDovL3d3dy53My5vcmcvVFIvMjAxMi9DUi14bWxlbmMtY29yZTEtMjAxMjAz
MTM+LgoKICAgW1czQy5SRUMteG1sLTE5OThdCiAgICAgICAgICAgICAgQnJheSwgVC4sIFBhb2xp
LCBKLiwgYW5kIEMuIFNwZXJiZXJnLU1jUXVlZW4sICJFeHRlbnNpYmxlCiAgICAgICAgICAgICAg
TWFya3VwIExhbmd1YWdlIChYTUwpIDEuMCIsIFczQyBSRUMteG1sLTE5OTgsCiAgICAgICAgICAg
ICAgRmVicnVhcnkgMTk5OCwKICAgICAgICAgICAgICA8aHR0cDovL3d3dy53My5vcmcvVFIvMTk5
OC9SRUMteG1sLTE5OTgwMjEwLz4uCgogICBbV2ViQ3J5cHRvXQogICAgICAgICAgICAgIFNsZWV2
aSwgUi4gYW5kIEQuIERhaGwsICJXZWIgQ3J5cHRvZ3JhcGh5IEFQSSIsCiAgICAgICAgICAgICAg
SmFudWFyeSAyMDEzLgoKOS4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW0NBUF0gICAg
ICBCb3R0ZXJlbGwsIEEuIGFuZCBFLiBKb25lcywgIkNvbW1vbiBBbGVydGluZyBQcm90b2NvbAog
ICAgICAgICAgICAgIHYxLjEiLCBPY3RvYmVyIDIwMDUuCgogICBbSS1ELmlldGYtYWx0by1wcm90
b2NvbF0KICAgICAgICAgICAgICBBbGltaSwgUi4sIFBlbm5vLCBSLiwgYW5kIFkuIFlhbmcsICJB
TFRPIFByb3RvY29sIiwKICAgICAgICAgICAgICBkcmFmdC1pZXRmLWFsdG8tcHJvdG9jb2wtMTYg
KHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXkgMjAxMy4KCiAgIFtJLUQuaWV0Zi1hdG9jYS1yZXF1aXJl
bWVudHNdCiAgICAgICAgICAgICAgU2NodWx6cmlubmUsIEguLCBOb3JyZXlzLCBTLiwgUm9zZW4s
IEIuLCBhbmQgSC4KICAgICAgICAgICAgICBUc2Nob2ZlbmlnLCAiUmVxdWlyZW1lbnRzLCBUZXJt
aW5vbG9neSBhbmQgRnJhbWV3b3JrIGZvcgogICAgICAgICAgICAgIEV4aWdlbnQgQ29tbXVuaWNh
dGlvbnMiLCBkcmFmdC1pZXRmLWF0b2NhLXJlcXVpcmVtZW50cy0wMwogICAgICAgICAgICAgICh3
b3JrIGluIHByb2dyZXNzKSwgTWFyY2ggMjAxMi4KCiAgIFtJLUQuaWV0Zi1qb3NlLWpzb24td2Vi
LWFsZ29yaXRobXNdCiAgICAgICAgICAgICAgSm9uZXMsIE0uLCAiSlNPTiBXZWIgQWxnb3JpdGht
cyAoSldBKSIsCiAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLWFsZ29yaXRo
bXMtMTEgKHdvcmsgaW4gcHJvZ3Jlc3MpLAogICAgICAgICAgICAgIE1heSAyMDEzLgoKICAgW0kt
RC5pZXRmLWpvc2UtanNvbi13ZWItZW5jcnlwdGlvbl0KICAgICAgICAgICAgICBKb25lcywgTS4s
IFJlc2NvcmxhLCBFLiwgYW5kIEouIEhpbGRlYnJhbmQsICJKU09OIFdlYgogICAgICAgICAgICAg
IEVuY3J5cHRpb24gKEpXRSkiLCBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItZW5jcnlwdGlvbi0x
MQogICAgICAgICAgICAgICh3b3JrIGluIHByb2dyZXNzKSwgTWF5IDIwMTMuCgogICBbSS1ELmll
dGYtam9zZS1qc29uLXdlYi1rZXldCgoKCkJhcm5lcyAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
RGVjZW1iZXIgMjEsIDIwMTMgICAgICAgICAgICAgIFtQYWdlIDIwXQoMCkludGVybmV0LURyYWZ0
ICAgICAgICAgICAgICAgSk9TRSBVc2UgQ2FzZXMgICAgICAgICAgICAgICAgICAgIEp1bmUgMjAx
MwoKCiAgICAgICAgICAgICAgSm9uZXMsIE0uLCAiSlNPTiBXZWIgS2V5IChKV0spIiwKICAgICAg
ICAgICAgICBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWIta2V5LTExICh3b3JrIGluIHByb2dyZXNz
KSwKICAgICAgICAgICAgICBNYXkgMjAxMy4KCiAgIFtJLUQuaWV0Zi1qb3NlLWpzb24td2ViLXNp
Z25hdHVyZV0KICAgICAgICAgICAgICBKb25lcywgTS4sIEJyYWRsZXksIEouLCBhbmQgTi4gU2Fr
aW11cmEsICJKU09OIFdlYgogICAgICAgICAgICAgIFNpZ25hdHVyZSAoSldTKSIsIGRyYWZ0LWll
dGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmUtMTEKICAgICAgICAgICAgICAod29yayBpbiBwcm9n
cmVzcyksIE1heSAyMDEzLgoKICAgW0ktRC5pZXRmLW9hdXRoLWpzb24td2ViLXRva2VuXQogICAg
ICAgICAgICAgIEpvbmVzLCBNLiwgQnJhZGxleSwgSi4sIGFuZCBOLiBTYWtpbXVyYSwgIkpTT04g
V2ViIFRva2VuCiAgICAgICAgICAgICAgKEpXVCkiLCBkcmFmdC1pZXRmLW9hdXRoLWpzb24td2Vi
LXRva2VuLTA4ICh3b3JrIGluCiAgICAgICAgICAgICAgcHJvZ3Jlc3MpLCBNYXkgMjAxMy4KCiAg
IFtJLUQuaWV0Zi1vYXV0aC1qd3QtYmVhcmVyXQogICAgICAgICAgICAgIEpvbmVzLCBNLiwgQ2Ft
cGJlbGwsIEIuLCBhbmQgQy4gTW9ydGltb3JlLCAiSlNPTiBXZWIgVG9rZW4KICAgICAgICAgICAg
ICAoSldUKSBQcm9maWxlIGZvciBPQXV0aCAyLjAgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZAog
ICAgICAgICAgICAgIEF1dGhvcml6YXRpb24gR3JhbnRzIiwgZHJhZnQtaWV0Zi1vYXV0aC1qd3Qt
YmVhcmVyLTA1CiAgICAgICAgICAgICAgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJjaCAyMDEzLgoK
ICAgW0ktRC5pZXRmLW9hdXRoLXNhbWwyLWJlYXJlcl0KICAgICAgICAgICAgICBDYW1wYmVsbCwg
Qi4sIE1vcnRpbW9yZSwgQy4sIGFuZCBNLiBKb25lcywgIlNBTUwgMi4wCiAgICAgICAgICAgICAg
UHJvZmlsZSBmb3IgT0F1dGggMi4wIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQKICAgICAgICAg
ICAgICBBdXRob3JpemF0aW9uIEdyYW50cyIsIGRyYWZ0LWlldGYtb2F1dGgtc2FtbDItYmVhcmVy
LTE2CiAgICAgICAgICAgICAgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJjaCAyMDEzLgoKICAgW0kt
RC5taWxsZXIteG1wcC1lMmVdCiAgICAgICAgICAgICAgTWlsbGVyLCBNLiwgIkVuZC10by1FbmQg
T2JqZWN0IEVuY3J5cHRpb24gZm9yIHRoZQogICAgICAgICAgICAgIEV4dGVuc2libGUgTWVzc2Fn
aW5nIGFuZCBQcmVzZW5jZSBQcm90b2NvbCAoWE1QUCkiLAogICAgICAgICAgICAgIGRyYWZ0LW1p
bGxlci14bXBwLWUyZS0wNiAod29yayBpbiBwcm9ncmVzcyksIE1heSAyMDEzLgoKICAgW0lUVS5Y
NjkwLjE5OTRdCiAgICAgICAgICAgICAgSW50ZXJuYXRpb25hbCBUZWxlY29tbXVuaWNhdGlvbnMg
VW5pb24sICJJbmZvcm1hdGlvbgogICAgICAgICAgICAgIFRlY2hub2xvZ3kgLSBBU04uMSBlbmNv
ZGluZyBydWxlczogU3BlY2lmaWNhdGlvbiBvZiBCYXNpYwogICAgICAgICAgICAgIEVuY29kaW5n
IFJ1bGVzIChCRVIpLCBDYW5vbmljYWwgRW5jb2RpbmcgUnVsZXMgKENFUikgYW5kCiAgICAgICAg
ICAgICAgRGlzdGluZ3Vpc2hlZCBFbmNvZGluZyBSdWxlcyAoREVSKSIsIElUVS1UIFJlY29tbWVu
ZGF0aW9uCiAgICAgICAgICAgICAgWC42OTAsIDE5OTQuCgogICBbT0FTSVMuc2FtbC1jb3JlLTIu
MC1vc10KICAgICAgICAgICAgICBDYW50b3IsIFMuLCBLZW1wLCBKLiwgUGhpbHBvdHQsIFIuLCBh
bmQgRS4gTWFsZXIsCiAgICAgICAgICAgICAgIkFzc2VydGlvbnMgYW5kIFByb3RvY29sIGZvciB0
aGUgT0FTSVMgU2VjdXJpdHkgQXNzZXJ0aW9uCiAgICAgICAgICAgICAgTWFya3VwIExhbmd1YWdl
IChTQU1MKSBWMi4wIiwgT0FTSVMgU3RhbmRhcmQgc2FtbC1jb3JlLQogICAgICAgICAgICAgIDIu
MC1vcywgTWFyY2ggMjAwNS4KCiAgIFtPcGVuSUQuTWVzc2FnZXNdCiAgICAgICAgICAgICAgU2Fr
aW11cmEsIE4uLCBCcmFkbGV5LCBKLiwgSm9uZXMsIE0uLCBkZSBNZWRlaXJvcywgQi4sCiAgICAg
ICAgICAgICAgTW9ydGltb3JlLCBDLiwgYW5kIEUuIEpheSwgIk9wZW5JRCBDb25uZWN0IE1lc3Nh
Z2VzIDEuMCIsCiAgICAgICAgICAgICAgSnVuZSAyMDEzLAoKCgpCYXJuZXMgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAgICBbUGFnZSAyMV0KDApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAg
ICAgICBKdW5lIDIwMTMKCgogICAgICAgICAgICAgIDxodHRwOi8vb3BlbmlkLm5ldC9zcGVjcy8K
ICAgICAgICAgICAgICBvcGVuaWQtY29ubmVjdC1tZXNzYWdlcy0xXzAuaHRtbD4uCgogICBbUGVy
c29uYV0gIE1vemlsbGEsICJNb3ppbGxhIFBlcnNvbmEiLCBBcHJpbCAyMDEzLgoKICAgW1JGQzI2
MTZdICBGaWVsZGluZywgUi4sIEdldHR5cywgSi4sIE1vZ3VsLCBKLiwgRnJ5c3R5aywgSC4sCiAg
ICAgICAgICAgICAgTWFzaW50ZXIsIEwuLCBMZWFjaCwgUC4sIGFuZCBULiBCZXJuZXJzLUxlZSwg
Ikh5cGVydGV4dAogICAgICAgICAgICAgIFRyYW5zZmVyIFByb3RvY29sIC0tIEhUVFAvMS4xIiwg
UkZDIDI2MTYsIEp1bmUgMTk5OS4KCiAgIFtSRkMyODE4XSAgUmVzY29ybGEsIEUuLCAiSFRUUCBP
dmVyIFRMUyIsIFJGQyAyODE4LCBNYXkgMjAwMC4KCiAgIFtSRkMzMjA3XSAgSG9mZm1hbiwgUC4s
ICJTTVRQIFNlcnZpY2UgRXh0ZW5zaW9uIGZvciBTZWN1cmUgU01UUCBvdmVyCiAgICAgICAgICAg
ICAgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IiwgUkZDIDMyMDcsIEZlYnJ1YXJ5IDIwMDIuCgog
ICBbUkZDMzkyM10gIFNhaW50LUFuZHJlLCBQLiwgIkVuZC10by1FbmQgU2lnbmluZyBhbmQgT2Jq
ZWN0IEVuY3J5cHRpb24KICAgICAgICAgICAgICBmb3IgdGhlIEV4dGVuc2libGUgTWVzc2FnaW5n
IGFuZCBQcmVzZW5jZSBQcm90b2NvbAogICAgICAgICAgICAgIChYTVBQKSIsIFJGQyAzOTIzLCBP
Y3RvYmVyIDIwMDQuCgogICBbUkZDNDMwMV0gIEtlbnQsIFMuIGFuZCBLLiBTZW8sICJTZWN1cml0
eSBBcmNoaXRlY3R1cmUgZm9yIHRoZQogICAgICAgICAgICAgIEludGVybmV0IFByb3RvY29sIiwg
UkZDIDQzMDEsIERlY2VtYmVyIDIwMDUuCgogICBbUkZDNTI0Nl0gIERpZXJrcywgVC4gYW5kIEUu
IFJlc2NvcmxhLCAiVGhlIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eQogICAgICAgICAgICAgIChU
TFMpIFByb3RvY29sIFZlcnNpb24gMS4yIiwgUkZDIDUyNDYsIEF1Z3VzdCAyMDA4LgoKICAgW1JG
QzUzMjJdICBSZXNuaWNrLCBQLiwgRWQuLCAiSW50ZXJuZXQgTWVzc2FnZSBGb3JtYXQiLCBSRkMg
NTMyMiwKICAgICAgICAgICAgICBPY3RvYmVyIDIwMDguCgogICBbUkZDNTc1MV0gIFJhbXNkZWxs
LCBCLiBhbmQgUy4gVHVybmVyLCAiU2VjdXJlL011bHRpcHVycG9zZSBJbnRlcm5ldAogICAgICAg
ICAgICAgIE1haWwgRXh0ZW5zaW9ucyAoUy9NSU1FKSBWZXJzaW9uIDMuMiBNZXNzYWdlCiAgICAg
ICAgICAgICAgU3BlY2lmaWNhdGlvbiIsIFJGQyA1NzUxLCBKYW51YXJ5IDIwMTAuCgogICBbV1Mt
RmVkZXJhdGlvbl0KICAgICAgICAgICAgICBLYWxlciwgQy4sIE1jSW50b3NoLCBNLiwgR29vZG5l
ciwgTS4sIGFuZCBBLiBOYWRhbGluLCAiV2ViCiAgICAgICAgICAgICAgU2VydmljZXMgRmVkZXJh
dGlvbiBMYW5ndWFnZSAoV1MtRmVkZXJhdGlvbikgVmVyc2lvbiAxLjIiLAogICAgICAgICAgICAg
IE1heSAyMDA5LCA8aHR0cDovL2RvY3Mub2FzaXMtb3Blbi5vcmcvd3NmZWQvZmVkZXJhdGlvbi8K
ICAgICAgICAgICAgICB2MS4yL29zL3dzLWZlZGVyYXRpb24tMS4yLXNwZWMtb3MuaHRtbD4uCgoK
QXBwZW5kaXggQS4gIEFja25vd2xlZGdlbWVudHMKCiAgIFRoYW5rcyB0byBNYXR0IE1pbGxlciBm
b3IgZGlzY3Vzc2lvbnMgcmVsYXRlZCB0byBYTVBQIGVuZC10by1lbmQKICAgc2VjdXJpdHkgbW9k
ZWwsIGFuZCB0byBNaWtlIEpvbmVzIGZvciBjb25zaWRlcmF0aW9ucyByZWxhdGVkIHRvCiAgIHNl
Y3VyaXR5IHRva2VucyBhbmQgWE1MIHNlY3VyaXR5LiAgVGhhbmtzIHRvIE1hcmsgV2F0c29uIGZv
ciByYWlzaW5nCiAgIHRoZSBuZWVkIGZvciByZXByZXNlbnRpbmcgc3ltbWV0cmljIGtleXMgYW5k
IGJpbmRpbmcgYXR0cmlidXRlcyB0bwogICB0aGVtLgoKCgoKCgpCYXJuZXMgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIERlY2VtYmVyIDIxLCAyMDEzICAgICAgICAgICAgICBbUGFnZSAyMl0KDApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgIEpPU0UgVXNlIENhc2VzICAgICAgICAgICAgICAg
ICAgICBKdW5lIDIwMTMKCgpBcHBlbmRpeCBCLiAgRG9jdW1lbnQgSGlzdG9yeQoKICAgW1sgdG8g
YmUgcmVtb3ZlZCBieSB0aGUgUkZDIGVkaXRvciBiZWZvcmUgcHVibGljYXRpb24gYXMgYW4gUkZD
IF1dCgogICAtMDMKCiAgIG8gIEVkaXRvcmlhbCBhbmQgZmFjdHVhbCBjb3JyZWN0aW9ucy4KCiAg
IC0wMgoKICAgbyAgUmVmZXJlbmNlZCB0aGUgSldTLCBKV0UsIEpXSywgYW5kIEpXQSBzcGVjaWZp
Y2F0aW9ucyBtYWtpbmcgdGhlCiAgICAgICJzaWduZWQgb2JqZWN0IGZvcm1hdCIsICJlbmNyeXB0
ZWQgb2JqZWN0IGZvcm1hdCIsICJrZXkgZm9ybWF0IiwKICAgICAgYW5kIGFsZ29yaXRobXMgcmVz
dWx0aW5nIGZyb20gdGhlc2UgdXNlIGNhc2VzIGNvbmNyZXRlLgoKICAgbyAgQWRkZWQgIlJlcXVp
cmVtZW50cyBvbiBBcHBsaWNhdGlvbiBQcm90b2NvbHMiIHNlY3Rpb24uCgogICBvICBCcm9rZSBm
b3JtZXIgaHVnZSAiU2VjdXJpdHkgVG9rZW5zIGFuZCBBdXRob3JpemF0aW9uIiBVc2UgQ2FzZQog
ICAgICBzZWN0aW9uIGludG8gIlNlY3VyaXR5IFRva2VucyIsICJPQXV0aCIsIGFuZCAiRmVkZXJh
dGlvbiIgVXNlIENhc2UKICAgICAgc2VjdGlvbnMuCgogICBvICBDaXRlZCBNb3ppbGxhIFBlcnNv
bmEgYXMgYSBzaW5nbGUtc2lnbi1vbiAoU1NPKSBzeXN0ZW0gdXNpbmcgSldUcwogICAgICBhbmQg
Sk9TRSBkYXRhIGZvcm1hdHMuCgogICBvICBTcGVsbGluZyBhbmQgZ3JhbW1hciBjb3JyZWN0aW9u
cy4KCiAgIC0wMQoKICAgbyAgQWRkZWQgdGhlICJTbWFsbCBEZXZpY2VzIiB1c2UgY2FzZQoKICAg
LTAwCgogICBvICBDcmVhdGVkIHRoZSBpbml0aWFsIElFVEYgZHJhZnQgYmFzZWQgdXBvbgogICAg
ICBkcmFmdC1iYXJuZXMtam9zZS11c2UtY2FzZXMtMDEgd2l0aCBzb21lIGFkZGl0aW9ucy4KCgpB
dXRob3IncyBBZGRyZXNzCgogICBSaWNoYXJkIEJhcm5lcwogICBCQk4gVGVjaG5vbG9naWVzCiAg
IDEzMDAgTiAxN3RoIFN0CiAgIEFybGluZ3RvbiwgVkEgIDIyMjA5CiAgIFVTCgogICBFbWFpbDog
cmxiQGlwdi5zeAoKCgoKCgoKQmFybmVzICAgICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNlbWJl
ciAyMSwgMjAxMyAgICAgICAgICAgICAgW1BhZ2UgMjNdCgwK

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_
Content-Type: text/html; name="draft-ietf-jose-use-cases-02+Mike.html"
Content-Description: draft-ietf-jose-use-cases-02+Mike.html
Content-Disposition: attachment;
	filename="draft-ietf-jose-use-cases-02+Mike.html"; size=88311;
	creation-date="Tue, 18 Jun 2013 22:46:38 GMT";
	modification-date="Tue, 18 Jun 2013 22:46:38 GMT"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlvbmFs
Ly9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL2h0bWw0L2xvb3NlLmR0ZCI+CjxodG1sIGxhbmc9
ImVuIj48aGVhZD48dGl0bGU+VXNlIENhc2VzIGFuZCBSZXF1aXJlbWVudHMgZm9yIEpTT04gT2Jq
ZWN0CiAgICBTaWduaW5nIGFuZCBFbmNyeXB0aW9uIChKT1NFKTwvdGl0bGU+CjxtZXRhIGh0dHAt
ZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4K
PG1ldGEgbmFtZT0iZGVzY3JpcHRpb24iIGNvbnRlbnQ9IlVzZSBDYXNlcyBhbmQgUmVxdWlyZW1l
bnRzIGZvciBKU09OIE9iamVjdAogICAgU2lnbmluZyBhbmQgRW5jcnlwdGlvbiAoSk9TRSkiPgo8
bWV0YSBuYW1lPSJrZXl3b3JkcyIgY29udGVudD0iSldTLCBKV0UsIEpXSywgSldBLCBKV1QsIENN
UywgUy9NSU1FLCBKT1NFLCBYTVBQLCBBTFRPLCBPQXV0aCwgRmVkZXJhdGlvbiwgU2VjdXJpdHkg
VG9rZW4iPgo8bWV0YSBuYW1lPSJnZW5lcmF0b3IiIGNvbnRlbnQ9InhtbDJyZmMgdjEuMzYgKGh0
dHA6Ly94bWwucmVzb3VyY2Uub3JnLykiPgo8c3R5bGUgdHlwZT0ndGV4dC9jc3MnPjwhLS0KICAg
ICAgICBib2R5IHsKICAgICAgICAgICAgICAgIGZvbnQtZmFtaWx5OiB2ZXJkYW5hLCBjaGFyY29h
bCwgaGVsdmV0aWNhLCBhcmlhbCwgc2Fucy1zZXJpZjsKICAgICAgICAgICAgICAgIGZvbnQtc2l6
ZTogc21hbGw7IGNvbG9yOiAjMDAwOyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkZGOwogICAgICAgICAg
ICAgICAgbWFyZ2luOiAyZW07CiAgICAgICAgfQogICAgICAgIGgxLCBoMiwgaDMsIGg0LCBoNSwg
aDYgewogICAgICAgICAgICAgICAgZm9udC1mYW1pbHk6IGhlbHZldGljYSwgbW9uYWNvLCAiTVMg
U2FucyBTZXJpZiIsIGFyaWFsLCBzYW5zLXNlcmlmOwogICAgICAgICAgICAgICAgZm9udC13ZWln
aHQ6IGJvbGQ7IGZvbnQtc3R5bGU6IG5vcm1hbDsKICAgICAgICB9CiAgICAgICAgaDEgeyBjb2xv
cjogIzkwMDsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJlbnQ7IHRleHQtYWxpZ246IHJpZ2h0
OyB9CiAgICAgICAgaDMgeyBjb2xvcjogIzMzMzsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJl
bnQ7IH0KCiAgICAgICAgdGQuUkZDYnVnIHsKICAgICAgICAgICAgICAgIGZvbnQtc2l6ZTogeC1z
bWFsbDsgdGV4dC1kZWNvcmF0aW9uOiBub25lOwogICAgICAgICAgICAgICAgd2lkdGg6IDMwcHg7
IGhlaWdodDogMzBweDsgcGFkZGluZy10b3A6IDJweDsKICAgICAgICAgICAgICAgIHRleHQtYWxp
Z246IGp1c3RpZnk7IHZlcnRpY2FsLWFsaWduOiBtaWRkbGU7CiAgICAgICAgICAgICAgICBiYWNr
Z3JvdW5kLWNvbG9yOiAjMDAwOwogICAgICAgIH0KICAgICAgICB0ZC5SRkNidWcgc3Bhbi5SRkMg
ewogICAgICAgICAgICAgICAgZm9udC1mYW1pbHk6IG1vbmFjbywgY2hhcmNvYWwsIGdlbmV2YSwg
Ik1TIFNhbnMgU2VyaWYiLCBoZWx2ZXRpY2EsIHZlcmRhbmEsIHNhbnMtc2VyaWY7CiAgICAgICAg
ICAgICAgICBmb250LXdlaWdodDogYm9sZDsgY29sb3I6ICM2NjY7CiAgICAgICAgfQogICAgICAg
IHRkLlJGQ2J1ZyBzcGFuLmhvdFRleHQgewogICAgICAgICAgICAgICAgZm9udC1mYW1pbHk6IGNo
YXJjb2FsLCBtb25hY28sIGdlbmV2YSwgIk1TIFNhbnMgU2VyaWYiLCBoZWx2ZXRpY2EsIHZlcmRh
bmEsIHNhbnMtc2VyaWY7CiAgICAgICAgICAgICAgICBmb250LXdlaWdodDogbm9ybWFsOyB0ZXh0
LWFsaWduOiBjZW50ZXI7IGNvbG9yOiAjRkZGOwogICAgICAgIH0KCiAgICAgICAgdGFibGUuVE9D
YnVnIHsgd2lkdGg6IDMwcHg7IGhlaWdodDogMTVweDsgfQogICAgICAgIHRkLlRPQ2J1ZyB7CiAg
ICAgICAgICAgICAgICB0ZXh0LWFsaWduOiBjZW50ZXI7IHdpZHRoOiAzMHB4OyBoZWlnaHQ6IDE1
cHg7CiAgICAgICAgICAgICAgICBjb2xvcjogI0ZGRjsgYmFja2dyb3VuZC1jb2xvcjogIzkwMDsK
ICAgICAgICB9CiAgICAgICAgdGQuVE9DYnVnIGEgewogICAgICAgICAgICAgICAgZm9udC1mYW1p
bHk6IG1vbmFjbywgY2hhcmNvYWwsIGdlbmV2YSwgIk1TIFNhbnMgU2VyaWYiLCBoZWx2ZXRpY2Es
IHNhbnMtc2VyaWY7CiAgICAgICAgICAgICAgICBmb250LXdlaWdodDogYm9sZDsgZm9udC1zaXpl
OiB4LXNtYWxsOyB0ZXh0LWRlY29yYXRpb246IG5vbmU7CiAgICAgICAgICAgICAgICBjb2xvcjog
I0ZGRjsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJlbnQ7CiAgICAgICAgfQoKICAgICAgICB0
ZC5oZWFkZXIgewogICAgICAgICAgICAgICAgZm9udC1mYW1pbHk6IGFyaWFsLCBoZWx2ZXRpY2Es
IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogeC1zbWFsbDsKICAgICAgICAgICAgICAgIHZlcnRpY2Fs
LWFsaWduOiB0b3A7IHdpZHRoOiAzMyU7CiAgICAgICAgICAgICAgICBjb2xvcjogI0ZGRjsgYmFj
a2dyb3VuZC1jb2xvcjogIzY2NjsKICAgICAgICB9CiAgICAgICAgdGQuYXV0aG9yIHsgZm9udC13
ZWlnaHQ6IGJvbGQ7IGZvbnQtc2l6ZTogeC1zbWFsbDsgbWFyZ2luLWxlZnQ6IDRlbTsgfQogICAg
ICAgIHRkLmF1dGhvci10ZXh0IHsgZm9udC1zaXplOiB4LXNtYWxsOyB9CgogICAgICAgIC8qIGlu
Zm8gY29kZSBmcm9tIFNhbnRhS2xhdXNzIGF0IGh0dHA6Ly93d3cubWFkYWJvdXRzdHlsZS5jb20v
dG9vbHRpcDIuaHRtbCAqLwogICAgICAgIGEuaW5mbyB7CiAgICAgICAgICAgICAgICAvKiBUaGlz
IGlzIHRoZSBrZXkuICovCiAgICAgICAgICAgICAgICBwb3NpdGlvbjogcmVsYXRpdmU7CiAgICAg
ICAgICAgICAgICB6LWluZGV4OiAyNDsKICAgICAgICAgICAgICAgIHRleHQtZGVjb3JhdGlvbjog
bm9uZTsKICAgICAgICB9CiAgICAgICAgYS5pbmZvOmhvdmVyIHsKICAgICAgICAgICAgICAgIHot
aW5kZXg6IDI1OwogICAgICAgICAgICAgICAgY29sb3I6ICNGRkY7IGJhY2tncm91bmQtY29sb3I6
ICM5MDA7CiAgICAgICAgfQogICAgICAgIGEuaW5mbyBzcGFuIHsgZGlzcGxheTogbm9uZTsgfQog
ICAgICAgIGEuaW5mbzpob3ZlciBzcGFuLmluZm8gewogICAgICAgICAgICAgICAgLyogVGhlIHNw
YW4gd2lsbCBkaXNwbGF5IGp1c3Qgb24gOmhvdmVyIHN0YXRlLiAqLwogICAgICAgICAgICAgICAg
ZGlzcGxheTogYmxvY2s7CiAgICAgICAgICAgICAgICBwb3NpdGlvbjogYWJzb2x1dGU7CiAgICAg
ICAgICAgICAgICBmb250LXNpemU6IHNtYWxsZXI7CiAgICAgICAgICAgICAgICB0b3A6IDJlbTsg
bGVmdDogLTVlbTsgd2lkdGg6IDE1ZW07CiAgICAgICAgICAgICAgICBwYWRkaW5nOiAycHg7IGJv
cmRlcjogMXB4IHNvbGlkICMzMzM7CiAgICAgICAgICAgICAgICBjb2xvcjogIzkwMDsgYmFja2dy
b3VuZC1jb2xvcjogI0VFRTsKICAgICAgICAgICAgICAgIHRleHQtYWxpZ246IGxlZnQ7CiAgICAg
ICAgfQoKICAgICAgICBhIHsgZm9udC13ZWlnaHQ6IGJvbGQ7IH0KICAgICAgICBhOmxpbmsgICAg
eyBjb2xvcjogIzkwMDsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJlbnQ7IH0KICAgICAgICBh
OnZpc2l0ZWQgeyBjb2xvcjogIzYzMzsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNwYXJlbnQ7IH0K
ICAgICAgICBhOmFjdGl2ZSAgeyBjb2xvcjogIzYzMzsgYmFja2dyb3VuZC1jb2xvcjogdHJhbnNw
YXJlbnQ7IH0KCiAgICAgICAgcCB7IG1hcmdpbi1sZWZ0OiAyZW07IG1hcmdpbi1yaWdodDogMmVt
OyB9CiAgICAgICAgcC5jb3B5cmlnaHQgeyBmb250LXNpemU6IHgtc21hbGw7IH0KICAgICAgICBw
LnRvYyB7IGZvbnQtc2l6ZTogc21hbGw7IGZvbnQtd2VpZ2h0OiBib2xkOyBtYXJnaW4tbGVmdDog
M2VtOyB9CiAgICAgICAgdGFibGUudG9jIHsgbWFyZ2luOiAwIDAgMCAzZW07IHBhZGRpbmc6IDA7
IGJvcmRlcjogMDsgdmVydGljYWwtYWxpZ246IHRleHQtdG9wOyB9CiAgICAgICAgdGQudG9jIHsg
Zm9udC1zaXplOiBzbWFsbDsgZm9udC13ZWlnaHQ6IGJvbGQ7IHZlcnRpY2FsLWFsaWduOiB0ZXh0
LXRvcDsgfQoKICAgICAgICBvbC50ZXh0IHsgbWFyZ2luLWxlZnQ6IDJlbTsgbWFyZ2luLXJpZ2h0
OiAyZW07IH0KICAgICAgICB1bC50ZXh0IHsgbWFyZ2luLWxlZnQ6IDJlbTsgbWFyZ2luLXJpZ2h0
OiAyZW07IH0KICAgICAgICBsaSAgICAgIHsgbWFyZ2luLWxlZnQ6IDNlbTsgfQoKICAgICAgICAv
KiBSRkMtMjYyOSA8c3Bhbng+cyBhbmQgPGFydHdvcms+cy4gKi8KICAgICAgICBlbSAgICAgeyBm
b250LXN0eWxlOiBpdGFsaWM7IH0KICAgICAgICBzdHJvbmcgeyBmb250LXdlaWdodDogYm9sZDsg
fQogICAgICAgIGRmbiAgICB7IGZvbnQtd2VpZ2h0OiBib2xkOyBmb250LXN0eWxlOiBub3JtYWw7
IH0KICAgICAgICBjaXRlICAgeyBmb250LXdlaWdodDogbm9ybWFsOyBmb250LXN0eWxlOiBub3Jt
YWw7IH0KICAgICAgICB0dCAgICAgeyBjb2xvcjogIzAzNjsgfQogICAgICAgIHR0LCBwcmUsIHBy
ZSBkZm4sIHByZSBlbSwgcHJlIGNpdGUsIHByZSBzcGFuIHsKICAgICAgICAgICAgICAgIGZvbnQt
ZmFtaWx5OiAiQ291cmllciBOZXciLCBDb3VyaWVyLCBtb25vc3BhY2U7IGZvbnQtc2l6ZTogc21h
bGw7CiAgICAgICAgfQogICAgICAgIHByZSB7CiAgICAgICAgICAgICAgICB0ZXh0LWFsaWduOiBs
ZWZ0OyBwYWRkaW5nOiA0cHg7CiAgICAgICAgICAgICAgICBjb2xvcjogIzAwMDsgYmFja2dyb3Vu
ZC1jb2xvcjogI0NDQzsKICAgICAgICB9CiAgICAgICAgcHJlIGRmbiAgeyBjb2xvcjogIzkwMDsg
fQogICAgICAgIHByZSBlbSAgIHsgY29sb3I6ICM2NkY7IGJhY2tncm91bmQtY29sb3I6ICNGRkM7
IGZvbnQtd2VpZ2h0OiBub3JtYWw7IH0KICAgICAgICBwcmUgLmtleSB7IGNvbG9yOiAjMzNDOyBm
b250LXdlaWdodDogYm9sZDsgfQogICAgICAgIHByZSAuaWQgIHsgY29sb3I6ICM5MDA7IH0KICAg
ICAgICBwcmUgLnN0ciB7IGNvbG9yOiAjMDAwOyBiYWNrZ3JvdW5kLWNvbG9yOiAjQ0ZGOyB9CiAg
ICAgICAgcHJlIC52YWwgeyBjb2xvcjogIzA2NjsgfQogICAgICAgIHByZSAucmVwIHsgY29sb3I6
ICM5MDk7IH0KICAgICAgICBwcmUgLm90aCB7IGNvbG9yOiAjMDAwOyBiYWNrZ3JvdW5kLWNvbG9y
OiAjRkNGOyB9CiAgICAgICAgcHJlIC5lcnIgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjRkNDOyB9Cgog
ICAgICAgIC8qIFJGQy0yNjI5IDx0ZXh0dGFibGU+cy4gKi8KICAgICAgICB0YWJsZS5hbGwsIHRh
YmxlLmZ1bGwsIHRhYmxlLmhlYWRlcnMsIHRhYmxlLm5vbmUgewogICAgICAgICAgICAgICAgZm9u
dC1zaXplOiBzbWFsbDsgdGV4dC1hbGlnbjogY2VudGVyOyBib3JkZXItd2lkdGg6IDJweDsKICAg
ICAgICAgICAgICAgIHZlcnRpY2FsLWFsaWduOiB0b3A7IGJvcmRlci1jb2xsYXBzZTogY29sbGFw
c2U7CiAgICAgICAgfQogICAgICAgIHRhYmxlLmFsbCwgdGFibGUuZnVsbCB7IGJvcmRlci1zdHls
ZTogc29saWQ7IGJvcmRlci1jb2xvcjogYmxhY2s7IH0KICAgICAgICB0YWJsZS5oZWFkZXJzLCB0
YWJsZS5ub25lIHsgYm9yZGVyLXN0eWxlOiBub25lOyB9CiAgICAgICAgdGggewogICAgICAgICAg
ICAgICAgZm9udC13ZWlnaHQ6IGJvbGQ7IGJvcmRlci1jb2xvcjogYmxhY2s7CiAgICAgICAgICAg
ICAgICBib3JkZXItd2lkdGg6IDJweCAycHggM3B4IDJweDsKICAgICAgICB9CiAgICAgICAgdGFi
bGUuYWxsIHRoLCB0YWJsZS5mdWxsIHRoIHsgYm9yZGVyLXN0eWxlOiBzb2xpZDsgfQogICAgICAg
IHRhYmxlLmhlYWRlcnMgdGggeyBib3JkZXItc3R5bGU6IG5vbmUgbm9uZSBzb2xpZCBub25lOyB9
CiAgICAgICAgdGFibGUubm9uZSB0aCB7IGJvcmRlci1zdHlsZTogbm9uZTsgfQogICAgICAgIHRh
YmxlLmFsbCB0ZCB7CiAgICAgICAgICAgICAgICBib3JkZXItc3R5bGU6IHNvbGlkOyBib3JkZXIt
Y29sb3I6ICMzMzM7CiAgICAgICAgICAgICAgICBib3JkZXItd2lkdGg6IDFweCAycHg7CiAgICAg
ICAgfQogICAgICAgIHRhYmxlLmZ1bGwgdGQsIHRhYmxlLmhlYWRlcnMgdGQsIHRhYmxlLm5vbmUg
dGQgeyBib3JkZXItc3R5bGU6IG5vbmU7IH0KCiAgICAgICAgaHIgeyBoZWlnaHQ6IDFweDsgfQog
ICAgICAgIGhyLmluc2VydCB7CiAgICAgICAgICAgICAgICB3aWR0aDogODAlOyBib3JkZXItc3R5
bGU6IG5vbmU7IGJvcmRlci13aWR0aDogMDsKICAgICAgICAgICAgICAgIGNvbG9yOiAjQ0NDOyBi
YWNrZ3JvdW5kLWNvbG9yOiAjQ0NDOwogICAgICAgIH0KLS0+PC9zdHlsZT4KPC9oZWFkPgo8Ym9k
eT4KPHRhYmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIy
IiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1ZyI+PGEg
aHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8dGFibGUg
c3VtbWFyeT0ibGF5b3V0IiB3aWR0aD0iNjYlIiBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBj
ZWxsc3BhY2luZz0iMCI+PHRyPjx0ZD48dGFibGUgc3VtbWFyeT0ibGF5b3V0IiB3aWR0aD0iMTAw
JSIgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMiIgY2VsbHNwYWNpbmc9IjEiPgo8dHI+PHRkIGNs
YXNzPSJoZWFkZXIiPkpPU0UgV29ya2luZyBHcm91cDwvdGQ+PHRkIGNsYXNzPSJoZWFkZXIiPlIu
IEJhcm5lczwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iaGVhZGVyIj5JbnRlcm5ldC1EcmFmdDwv
dGQ+PHRkIGNsYXNzPSJoZWFkZXIiPkJCTiBUZWNobm9sb2dpZXM8L3RkPjwvdHI+Cjx0cj48dGQg
Y2xhc3M9ImhlYWRlciI+SW50ZW5kZWQgc3RhdHVzOiBJbmZvcm1hdGlvbmFsPC90ZD48dGQgY2xh
c3M9ImhlYWRlciI+SnVuZSAxOSwgMjAxMzwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iaGVhZGVy
Ij5FeHBpcmVzOiBEZWNlbWJlciAyMSwgMjAxMzwvdGQ+PHRkIGNsYXNzPSJoZWFkZXIiPiZuYnNw
OzwvdGQ+PC90cj4KPC90YWJsZT48L3RkPjwvdHI+PC90YWJsZT4KPGgxPjxiciAvPlVzZSBDYXNl
cyBhbmQgUmVxdWlyZW1lbnRzIGZvciBKU09OIE9iamVjdAogICAgU2lnbmluZyBhbmQgRW5jcnlw
dGlvbiAoSk9TRSk8YnIgLz5kcmFmdC1pZXRmLWpvc2UtdXNlLWNhc2VzLTAzPC9oMT4KCjxoMz5B
YnN0cmFjdDwvaDM+Cgo8cD5NYW55IEludGVybmV0IGFwcGxpY2F0aW9ucyBoYXZlIGEgbmVlZCBm
b3Igb2JqZWN0LWJhc2VkIHNlY3VyaXR5CiAgICAgIG1lY2hhbmlzbXMgaW4gYWRkaXRpb24gdG8g
c2VjdXJpdHkgbWVjaGFuaXNtcyBhdCB0aGUgbmV0d29yayBsYXllciBvcgogICAgICB0cmFuc3Bv
cnQgbGF5ZXIuIEluIHRoZSBwYXN0LCB0aGUgQ3J5cHRvZ3JhcGhpYyBNZXNzYWdlIFN5bnRheCBo
YXMKICAgICAgcHJvdmlkZWQgYSBiaW5hcnkgc2VjdXJlIG9iamVjdCBmb3JtYXQgYmFzZWQgb24g
QVNOLjEuIE92ZXIgdGltZSwgdGhlCiAgICAgIHVzZSBvZiBiaW5hcnkgb2JqZWN0IGVuY29kaW5n
cyBzdWNoIGFzIEFTTi4xIGhhcyBiZWVuIG92ZXJ0YWtlbiBieQogICAgICB0ZXh0LWJhc2VkIGVu
Y29kaW5ncywgZm9yIGV4YW1wbGUgSmF2YVNjcmlwdCBPYmplY3QgTm90YXRpb24uIFRoaXMKICAg
ICAgZG9jdW1lbnQgZGVmaW5lcyBhIHNldCBvZiB1c2UgY2FzZXMgYW5kIHJlcXVpcmVtZW50cyBm
b3IgYSBzZWN1cmUgb2JqZWN0CiAgICAgIGZvcm1hdCBlbmNvZGVkIHVzaW5nIEphdmFTY3JpcHQg
T2JqZWN0IE5vdGF0aW9uLCBkcmF3biBmcm9tIGEgdmFyaWV0eSBvZgogICAgICBhcHBsaWNhdGlv
biBzZWN1cml0eSBtZWNoYW5pc21zIGN1cnJlbnRseSBpbiBkZXZlbG9wbWVudC4KPC9wPgo8aDM+
U3RhdHVzIG9mIHRoaXMgTWVtbzwvaDM+CjxwPgpUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1p
dHRlZCAgaW4gZnVsbApjb25mb3JtYW5jZSB3aXRoIHRoZSBwcm92aXNpb25zIG9mIEJDUCZuYnNw
Ozc4IGFuZCBCQ1AmbmJzcDs3OS48L3A+CjxwPgpJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcg
ZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwpUYXNrIEZvcmNlIChJRVRGKS4g
IE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQp3b3JraW5nIGRvY3Vt
ZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJyZW50CkludGVybmV0LURy
YWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJlbnQvLjwv
cD4KPHA+CkludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1h
eGltdW0gb2Ygc2l4IG1vbnRocwphbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNv
bGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueSB0aW1lLgpJdCBpcyBpbmFwcHJvcHJpYXRl
IHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlIG1hdGVyaWFsIG9yIHRvIGNpdGUK
dGhlbSBvdGhlciB0aGFuIGFzICZsZHF1bzt3b3JrIGluIHByb2dyZXNzLiZyZHF1bzs8L3A+Cjxw
PgpUaGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIERlY2VtYmVyIDIxLCAyMDEzLjwv
cD4KCjxoMz5Db3B5cmlnaHQgTm90aWNlPC9oMz4KPHA+CkNvcHlyaWdodCAoYykgMjAxMyBJRVRG
IFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFzIHRoZQpkb2N1bWVudCBhdXRob3Jz
LiAgQWxsIHJpZ2h0cyByZXNlcnZlZC48L3A+CjxwPgpUaGlzIGRvY3VtZW50IGlzIHN1YmplY3Qg
dG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsClByb3Zpc2lvbnMgUmVsYXRpbmcg
dG8gSUVURiBEb2N1bWVudHMKKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykg
aW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mCnB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQ
bGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50cwpjYXJlZnVsbHksIGFzIHRoZXkgZGVzY3JpYmUg
eW91ciByaWdodHMgYW5kIHJlc3RyaWN0aW9ucyB3aXRoIHJlc3BlY3QKdG8gdGhpcyBkb2N1bWVu
dC4gQ29kZSBDb21wb25lbnRzIGV4dHJhY3RlZCBmcm9tIHRoaXMgZG9jdW1lbnQgbXVzdAppbmNs
dWRlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0
LmUgb2YKdGhlIFRydXN0IExlZ2FsIFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0
IHdhcnJhbnR5IGFzCmRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS48L3A+
CjxhIG5hbWU9InRvYyI+PC9hPjxiciAvPjxociAvPgo8aDM+VGFibGUgb2YgQ29udGVudHM8L2gz
Pgo8cCBjbGFzcz0idG9jIj4KPGEgaHJlZj0iI2ludHJvLXNlYyI+MS48L2E+Jm5ic3A7CkludHJv
ZHVjdGlvbjxiciAvPgo8YSBocmVmPSIjZGVmLXNlYyI+Mi48L2E+Jm5ic3A7CkRlZmluaXRpb25z
PGJyIC8+CjxhIGhyZWY9IiNiYXNpYy1zZWMiPjMuPC9hPiZuYnNwOwpCYXNpYyBSZXF1aXJlbWVu
dHM8YnIgLz4KPGEgaHJlZj0iI2FwcC1yZXEtc2VjIj40LjwvYT4mbmJzcDsKUmVxdWlyZW1lbnRz
IG9uIEFwcGxpY2F0aW9uIFByb3RvY29sczxiciAvPgo8YSBocmVmPSIjdXNlLWNhc2VzLXNlYyI+
NS48L2E+Jm5ic3A7ClVzZSBDYXNlczxiciAvPgombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs8YSBo
cmVmPSIjc2VjLXRva2VuLXNlYyI+NS4xLjwvYT4mbmJzcDsKU2VjdXJpdHkgVG9rZW5zPGJyIC8+
CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNvYXV0aC1zZWMiPjUuMi48L2E+Jm5i
c3A7Ck9BdXRoPGJyIC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNmZWQtc2Vj
Ij41LjMuPC9hPiZuYnNwOwpGZWRlcmF0aW9uPGJyIC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OzxhIGhyZWY9IiN4bXBwLXNlYyI+NS40LjwvYT4mbmJzcDsKWE1QUDxiciAvPgombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDs8YSBocmVmPSIjYWx0by1zZWMiPjUuNS48L2E+Jm5ic3A7CkFMVE88YnIg
Lz4KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iI2F0b2NhLXNlYyI+NS42LjwvYT4m
bmJzcDsKRW1lcmdlbmN5IEFsZXJ0aW5nPGJyIC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxh
IGhyZWY9IiN3ZWJjcnlwdG8tc2VjIj41LjcuPC9hPiZuYnNwOwpXZWIgQ3J5cHRvZ3JhcGh5PGJy
IC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNhbmNob3IxIj41LjguPC9hPiZu
YnNwOwpTbWFsbCBEZXZpY2VzPGJyIC8+CjxhIGhyZWY9IiNyZXEtc2VjIj42LjwvYT4mbmJzcDsK
UmVxdWlyZW1lbnRzPGJyIC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNmdW5j
dGlvbmFsLXNlYyI+Ni4xLjwvYT4mbmJzcDsKRnVuY3Rpb25hbCBSZXF1aXJlbWVudHM8YnIgLz4K
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iI3NlYy1yZXEtc2VjIj42LjIuPC9hPiZu
YnNwOwpTZWN1cml0eSBSZXF1aXJlbWVudHM8YnIgLz4KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
PGEgaHJlZj0iI2Rlc2lkZXJhdGEtc2VjIj42LjMuPC9hPiZuYnNwOwpEZXNpZGVyYXRhPGJyIC8+
CjxhIGhyZWY9IiNpYW5hLXNlYyI+Ny48L2E+Jm5ic3A7CklBTkEgQ29uc2lkZXJhdGlvbnM8YnIg
Lz4KPGEgaHJlZj0iI3NlYy1jb25zLXNlYyI+OC48L2E+Jm5ic3A7ClNlY3VyaXR5IENvbnNpZGVy
YXRpb25zPGJyIC8+CjxhIGhyZWY9IiNyZmMucmVmZXJlbmNlczEiPjkuPC9hPiZuYnNwOwpSZWZl
cmVuY2VzPGJyIC8+CiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNyZmMucmVmZXJl
bmNlczEiPjkuMS48L2E+Jm5ic3A7Ck5vcm1hdGl2ZSBSZWZlcmVuY2VzPGJyIC8+CiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9IiNyZmMucmVmZXJlbmNlczIiPjkuMi48L2E+Jm5ic3A7
CkluZm9ybWF0aXZlIFJlZmVyZW5jZXM8YnIgLz4KPGEgaHJlZj0iI2Fjay1zZWMiPkFwcGVuZGl4
Jm5ic3A7QS48L2E+Jm5ic3A7CkFja25vd2xlZGdlbWVudHM8YnIgLz4KPGEgaHJlZj0iI2hpc3Qt
c2VjIj5BcHBlbmRpeCZuYnNwO0IuPC9hPiZuYnNwOwpEb2N1bWVudCBIaXN0b3J5PGJyIC8+Cjxh
IGhyZWY9IiNyZmMuYXV0aG9ycyI+JiMxNjc7PC9hPiZuYnNwOwpBdXRob3IncyBBZGRyZXNzPGJy
IC8+CjwvcD4KPGJyIGNsZWFyPSJhbGwiIC8+Cgo8YSBuYW1lPSJpbnRyby1zZWMiPjwvYT48YnIg
Lz48aHIgLz4KPHRhYmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFj
aW5nPSIyIiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1
ZyI+PGEgaHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8
YSBuYW1lPSJyZmMuc2VjdGlvbi4xIj48L2E+PGgzPjEuJm5ic3A7CkludHJvZHVjdGlvbjwvaDM+
Cgo8cD5JbnRlcm5ldCBhcHBsaWNhdGlvbnMgcmVzdCBvbiB0aGUgbGF5ZXJlZCBhcmNoaXRlY3R1
cmUgb2YgdGhlCiAgICAgIEludGVybmV0LCBhbmQgdGFrZSBhZHZhbnRhZ2Ugb2Ygc2VjdXJpdHkg
bWVjaGFuaXNtcyBhdCBhbGwgbGF5ZXJzLiBNYW55CiAgICAgIGFwcGxpY2F0aW9ucyByZWx5IHBy
aW1hcmlseSBvbiBjaGFubmVsLWJhc2VkIHNlY3VyaXR5IHRlY2hub2xvZ2llcywKICAgICAgd2hp
Y2ggY3JlYXRlIGEgc2VjdXJlIGNoYW5uZWwgYXQgdGhlIElQIGxheWVyIG9yIHRyYW5zcG9ydCBs
YXllciBvdmVyCiAgICAgIHdoaWNoIGFwcGxpY2F0aW9uIGRhdGEgY2FuIGZsb3cgPGEgY2xhc3M9
J2luZm8nIGhyZWY9JyNSRkM0MzAxJz5bUkZDNDMwMV08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFz
cz0naW5mbyc+S2VudCwgUy4gYW5kIEsuIFNlbywgJmxkcXVvO1NlY3VyaXR5IEFyY2hpdGVjdHVy
ZSBmb3IgdGhlIEludGVybmV0IFByb3RvY29sLCZyZHF1bzsgRGVjZW1iZXImbmJzcDsyMDA1Ljwv
c3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT48YSBjbGFzcz0naW5mbycgaHJlZj0nI1JGQzUyNDYnPltS
RkM1MjQ2XTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5EaWVya3MsIFQuIGFuZCBF
LiBSZXNjb3JsYSwgJmxkcXVvO1RoZSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykgUHJv
dG9jb2wgVmVyc2lvbiAxLjIsJnJkcXVvOyBBdWd1c3QmbmJzcDsyMDA4Ljwvc3Bhbj48c3Bhbj4p
PC9zcGFuPjwvYT4uIFRoZXNlIG1lY2hhbmlzbXMsIGhvd2V2ZXIsIGNhbm5vdCBwcm92aWRlIGVu
ZC10by1lbmQKICAgICAgc2VjdXJpdHkgaW4gc29tZSBjYXNlcy4gRm9yIGV4YW1wbGUsIGluIHBy
b3RvY29scyB3aXRoIGFwcGxpY2F0aW9uLWxheWVyCiAgICAgIGludGVybWVkaWFyaWVzLCBjaGFu
bmVsLWJhc2VkIHNlY3VyaXR5IHByb3RvY29scyB3b3VsZCBwcm90ZWN0IG1lc3NhZ2VzCiAgICAg
IGZyb20gYXR0YWNrZXJzIGJldHdlZW4gaW50ZXJtZWRpYXJpZXMsIGJ1dCBub3QgZnJvbSB0aGUg
aW50ZXJtZWRpYXJpZXMKICAgICAgdGhlbXNlbHZlcy4gVGhlc2UgY2FzZXMgcmVxdWlyZSBvYmpl
Y3QtYmFzZWQgc2VjdXJpdHkgdGVjaG5vbG9naWVzLAogICAgICB3aGljaCBlbWJlZCBhcHBsaWNh
dGlvbiBkYXRhIHdpdGhpbiBhIHNlY3VyZSBvYmplY3QgdGhhdCBjYW4gYmUgc2FmZWx5CiAgICAg
IGhhbmRsZWQgYnkgdW50cnVzdGVkIGVudGl0aWVzLgo8L3A+CjxwPlRoZSBtb3N0IHdlbGwta25v
d24gZXhhbXBsZSBvZiBzdWNoIGEgcHJvdG9jb2wgdG9kYXkgaXMgdGhlIHVzZSBvZgogICAgICBT
ZWN1cmUvTXVsdGlwdXJwb3NlIEludGVybmV0IE1haWwgRXh0ZW5zaW9ucyAoUy9NSU1FKSBwcm90
ZWN0aW9ucyB3aXRoaW4KICAgICAgdGhlIGVtYWlsIHN5c3RlbSA8YSBjbGFzcz0naW5mbycgaHJl
Zj0nI1JGQzU3NTEnPltSRkM1NzUxXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5S
YW1zZGVsbCwgQi4gYW5kIFMuIFR1cm5lciwgJmxkcXVvO1NlY3VyZS9NdWx0aXB1cnBvc2UgSW50
ZXJuZXQgTWFpbCBFeHRlbnNpb25zIChTL01JTUUpIFZlcnNpb24gMy4yIE1lc3NhZ2UgU3BlY2lm
aWNhdGlvbiwmcmRxdW87IEphbnVhcnkmbmJzcDsyMDEwLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwv
YT48YSBjbGFzcz0naW5mbycgaHJlZj0nI1JGQzUzMjInPltSRkM1MzIyXTxzcGFuPiAoPC9zcGFu
PjxzcGFuIGNsYXNzPSdpbmZvJz5SZXNuaWNrLCBQLiwgRWQuLCAmbGRxdW87SW50ZXJuZXQgTWVz
c2FnZSBGb3JtYXQsJnJkcXVvOyBPY3RvYmVyJm5ic3A7MjAwOC48L3NwYW4+PHNwYW4+KTwvc3Bh
bj48L2E+LiBBbgogICAgICBlbWFpbCBtZXNzYWdlIHR5cGljYWxseSBwYXNzZXMgdGhyb3VnaCBh
IHNlcmllcyBvZiBpbnRlcm1lZGlhdGUgTWFpbAogICAgICBUcmFuc2ZlciBBZ2VudHMgKE1UQXMp
IGVuIHJvdXRlIHRvIGl0cyBkZXN0aW5hdGlvbi4gV2hpbGUgdGhlc2UgTVRBcwogICAgICBvZnRl
biBhcHBseSBjaGFubmVsLWJhc2VkIHNlY3VyaXR5IHByb3RlY3Rpb25zIHRvIHRoZWlyIGludGVy
YWN0aW9ucwogICAgICAoZS5nLiwgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkMzMjA3Jz5bUkZD
MzIwN108c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+SG9mZm1hbiwgUC4sICZsZHF1
bztTTVRQIFNlcnZpY2UgRXh0ZW5zaW9uIGZvciBTZWN1cmUgU01UUCBvdmVyIFRyYW5zcG9ydCBM
YXllciBTZWN1cml0eSwmcmRxdW87IEZlYnJ1YXJ5Jm5ic3A7MjAwMi48L3NwYW4+PHNwYW4+KTwv
c3Bhbj48L2E+KSwgdGhlc2UgcHJvdGVjdGlvbnMgZG8gbm90IHByZXZlbnQgdGhlCiAgICAgIE1U
QXMgZnJvbSBpbnRlcmZlcmluZyB3aXRoIHRoZSBtZXNzYWdlLiBJbiBvcmRlciB0byBwcm92aWRl
IGVuZC10by1lbmQKICAgICAgc2VjdXJpdHkgcHJvdGVjdGlvbnMgaW4gdGhlIHByZXNlbmNlIG9m
IHVudHJ1c3RlZCBNVEFzLCBtYWlsIHVzZXJzIGNhbgogICAgICB1c2UgUy9NSU1FIHRvIGVtYmVk
IG1lc3NhZ2UgYm9kaWVzIGluIGEgc2VjdXJlIG9iamVjdCBmb3JtYXQgdGhhdCBjYW4KICAgICAg
cHJvdmlkZSBjb25maWRlbnRpYWxpdHksIGludGVncml0eSwgYW5kIGRhdGEgb3JpZ2luIGF1dGhl
bnRpY2F0aW9uLgo8L3A+CjxwPlMvTUlNRSBpcyBiYXNlZCBvbiB0aGUgQ3J5cHRvZ3JhcGhpYyBN
ZXNzYWdlIFN5bnRheCBmb3Igc2VjdXJlCiAgICAgIG9iamVjdHMgKENNUykgPGEgY2xhc3M9J2lu
Zm8nIGhyZWY9JyNSRkM1NjUyJz5bUkZDNTY1Ml08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0n
aW5mbyc+SG91c2xleSwgUi4sICZsZHF1bztDcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChD
TVMpLCZyZHF1bzsgU2VwdGVtYmVyJm5ic3A7MjAwOS48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+
LiBDTVMgaXMgZGVmaW5lZCB1c2luZyBBYnN0cmFjdAogICAgICBTeW50YXggTm90YXRpb24gMSAo
QVNOLjEpIGFuZCB0cmFkaXRpb25hbGx5IGVuY29kZWQgdXNpbmcgdGhlIEFTTi4xCiAgICAgIERp
c3Rpbmd1aXNoZWQgRW5jb2RpbmcgUnVsZXMgKERFUiksIHdoaWNoIGRlZmluZSBhIGJpbmFyeSBl
bmNvZGluZyBvZgogICAgICB0aGUgcHJvdGVjdGVkIG1lc3NhZ2UgYW5kIGFzc29jaWF0ZWQgcGFy
YW1ldGVycyA8YSBjbGFzcz0naW5mbycgaHJlZj0nI0lUVS5YNjkwLjE5OTQnPltJVFUuWDY5MC4x
OTk0XTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5JbnRlcm5hdGlvbmFsIFRlbGVj
b21tdW5pY2F0aW9ucyBVbmlvbiwgJmxkcXVvO0luZm9ybWF0aW9uIFRlY2hub2xvZ3kgLSBBU04u
MSBlbmNvZGluZyBydWxlczogU3BlY2lmaWNhdGlvbiBvZiBCYXNpYyBFbmNvZGluZyBSdWxlcyAo
QkVSKSwgQ2Fub25pY2FsIEVuY29kaW5nIFJ1bGVzIChDRVIpIGFuZCBEaXN0aW5ndWlzaGVkIEVu
Y29kaW5nIFJ1bGVzIChERVIpLCZyZHF1bzsgMTk5NC48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+
LiBJbiByZWNlbnQgeWVhcnMsIHVzYWdlIG9mIEFTTi4xIGhhcyBkZWNyZWFzZWQKICAgICAgKGFs
b25nIHdpdGggb3RoZXIgYmluYXJ5IGVuY29kaW5ncyBmb3IgZ2VuZXJhbCBvYmplY3RzKSwgd2hp
bGUgbW9yZQogICAgICBhcHBsaWNhdGlvbnMgaGF2ZSBjb21lIHRvIHJlbHkgb24gdGV4dC1iYXNl
ZCBmb3JtYXRzIHN1Y2ggYXMgdGhlCiAgICAgIEV4dGVuc2libGUgTWFya3VwIExhbmd1YWdlIChY
TUwpIG9yIHRoZSBKYXZhU2NyaXB0IE9iamVjdCBOb3RhdGlvbgogICAgICAoSlNPTikgPGEgY2xh
c3M9J2luZm8nIGhyZWY9JyNXM0MuUkVDLXhtbC0xOTk4Jz5bVzNDLlJFQyYjODIwOTt4bWwmIzgy
MDk7MTk5OF08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+QnJheSwgVC4sIFBhb2xp
LCBKLiwgYW5kIEMuIFNwZXJiZXJnLU1jUXVlZW4sICZsZHF1bztFeHRlbnNpYmxlIE1hcmt1cCBM
YW5ndWFnZSAoWE1MKSAxLjAsJnJkcXVvOyBGZWJydWFyeSZuYnNwOzE5OTguPC9zcGFuPjxzcGFu
Pik8L3NwYW4+PC9hPjxhIGNsYXNzPSdpbmZvJyBocmVmPScjUkZDNDYyNyc+W1JGQzQ2MjddPHNw
YW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8nPkNyb2NrZm9yZCwgRC4sICZsZHF1bztUaGUg
YXBwbGljYXRpb24vanNvbiBNZWRpYSBUeXBlIGZvciBKYXZhU2NyaXB0IE9iamVjdCBOb3RhdGlv
biAoSlNPTiksJnJkcXVvOyBKdWx5Jm5ic3A7MjAwNi48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+
Lgo8L3A+CjxwPk1hbnkgY3VycmVudCBhcHBsaWNhdGlvbnMgdGh1cyBoYXZlIG11Y2ggbW9yZSBy
b2J1c3Qgc3VwcG9ydCBmb3IKICAgICAgcHJvY2Vzc2luZyBvYmplY3RzIGluIHRoZXNlIHRleHQt
YmFzZWQgZm9ybWF0cyB0aGFuIEFTTi4xIG9iamVjdHM7CiAgICAgIGluZGVlZCwgbWFueSBsYWNr
IHRoZSBhYmlsaXR5IHRvIHByb2Nlc3MgQVNOLjEgb2JqZWN0cyBhdCBhbGwuIFRvCiAgICAgIHNp
bXBsaWZ5IHRoZSBhZGRpdGlvbiBvZiBvYmplY3QtYmFzZWQgc2VjdXJpdHkgZmVhdHVyZXMgdG8g
dGhlc2UKICAgICAgYXBwbGljYXRpb25zLCB0aGUgSUVURiBKU09OIE9iamVjdCBTaWduaW5nIGFu
ZCBFbmNyeXB0aW9uIChKT1NFKSB3b3JraW5nCiAgICAgIGdyb3VwIGhhcyBiZWVuIGNoYXJ0ZXJl
ZCB0byBkZXZlbG9wIGEgc2VjdXJlIG9iamVjdCBmb3JtYXQgYmFzZWQgb24KICAgICAgSlNPTi4g
V2hpbGUgdGhlIGJhc2ljIHJlcXVpcmVtZW50cyBmb3IgdGhpcyBvYmplY3QgZm9ybWF0IGFyZQog
ICAgICBzdHJhaWdodGZvcndhcmQgLS0gbmFtZWx5LCBjb25maWRlbnRpYWxpdHkgYW5kIGludGVn
cml0eSBtZWNoYW5pc21zLAogICAgICBlbmNvZGVkIGluIEpTT04gLS0gZGlzY3Vzc2lvbnMgaW4g
dGhlIHdvcmtpbmcgZ3JvdXAgaW5kaWNhdGVkIHRoYXQKICAgICAgZGlmZmVyZW50IGFwcGxpY2F0
aW9ucyBob3BpbmcgdG8gdXNlIHRoZSBmb3JtYXRzIGRlZmluZWQgYnkgSk9TRSBoYXZlCiAgICAg
IGRpZmZlcmVudCByZXF1aXJlbWVudHMuIFRoaXMgZG9jdW1lbnQgc3VtbWFyaXplcyB0aGUgdXNl
IGNhc2VzIGZvciBKT1NFCiAgICAgIGVudmlzaW9uZWQgYnkgdGhvc2UgcG90ZW50aWFsIGFwcGxp
Y2F0aW9ucyBhbmQgdGhlIHJlc3VsdGluZyByZXF1aXJlbWVudHMgZm9yCiAgICAgIHNlY3VyaXR5
IG1lY2hhbmlzbXMgYW5kIG9iamVjdCBlbmNvZGluZ3MuCjwvcD4KPHA+U29tZSBzeXN0ZW1zIHRo
YXQgdXNlIFhNTCBoYXZlIHNwZWNpZmllZCB0aGUgdXNlIG9mIFhNTC1iYXNlZAogICAgICBzZWN1
cml0eSBtZWNoYW5pc21zIGZvciBvYmplY3Qgc2VjdXJpdHksIG5hbWVseSBYTUwgRGlnaXRhbCBT
aWduYXR1cmVzCiAgICAgIGFuZCBYTUwgRW5jcnlwdGlvbiA8YSBjbGFzcz0naW5mbycgaHJlZj0n
I1czQy5DUi14bWxkc2lnLWNvcmUyLTIwMTIwMTI0Jz5bVzNDLkNSJiM4MjA5O3htbGRzaWcmIzgy
MDk7Y29yZTImIzgyMDk7MjAxMjAxMjRdPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8n
PkVhc3RsYWtlLCBELiwgUmVhZ2xlLCBKLiwgWWl1LCBLLiwgU29sbywgRC4sIERhdHRhLCBQLiwg
SGlyc2NoLCBGLiwgQ2FudG9yLCBTLiwgYW5kIFQuIFJvZXNzbGVyLCAmbGRxdW87WE1MIFNpZ25h
dHVyZSBTeW50YXggYW5kIFByb2Nlc3NpbmcgVmVyc2lvbiAyLjAsJnJkcXVvOyBKYW51YXJ5Jm5i
c3A7MjAxMi48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+PGEgY2xhc3M9J2luZm8nIGhyZWY9JyNX
M0MuQ1IteG1sZW5jLWNvcmUxLTIwMTIwMzEzJz5bVzNDLkNSJiM4MjA5O3htbGVuYyYjODIwOTtj
b3JlMSYjODIwOTsyMDEyMDMxM108c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+RWFz
dGxha2UsIEQuLCBSZWFnbGUsIEouLCBSb2Vzc2xlciwgVC4sIGFuZCBGLiBIaXJzY2gsICZsZHF1
bztYTUwgRW5jcnlwdGlvbiBTeW50YXggYW5kIFByb2Nlc3NpbmcgVmVyc2lvbiAxLjEsJnJkcXVv
OyBNYXJjaCZuYnNwOzIwMTIuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPi4gVGhlc2UgbWVjaGFu
aXNtcyBhcmUgZGVmaW5lZAogICAgICBmb3IgdXNlIHdpdGggc2V2ZXJhbCBzZWN1cml0eSB0b2tl
biBzeXN0ZW1zIChlLmcuLAogICAgICBTQU1MIDxhIGNsYXNzPSdpbmZvJyBocmVmPScjT0FTSVMu
c2FtbC1jb3JlLTIuMC1vcyc+W09BU0lTLnNhbWwmIzgyMDk7Y29yZSYjODIwOTsyLjAmIzgyMDk7
b3NdPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8nPkNhbnRvciwgUy4sIEtlbXAsIEou
LCBQaGlscG90dCwgUi4sIGFuZCBFLiBNYWxlciwgJmxkcXVvO0Fzc2VydGlvbnMgYW5kIFByb3Rv
Y29sIGZvciB0aGUgT0FTSVMgU2VjdXJpdHkgQXNzZXJ0aW9uIE1hcmt1cCBMYW5ndWFnZSAgICAg
ICAgICAgICAoU0FNTCkgVjIuMCwmcmRxdW87IE1hcmNoJm5ic3A7MjAwNS48L3NwYW4+PHNwYW4+
KTwvc3Bhbj48L2E+IGFuZAogICAgICBXUy1GZWRlcmF0aW9uIDxhIGNsYXNzPSdpbmZvJyBocmVm
PScjV1MtRmVkZXJhdGlvbic+W1dTJiM4MjA5O0ZlZGVyYXRpb25dPHNwYW4+ICg8L3NwYW4+PHNw
YW4gY2xhc3M9J2luZm8nPkthbGVyLCBDLiwgTWNJbnRvc2gsIE0uLCBHb29kbmVyLCBNLiwgYW5k
IEEuIE5hZGFsaW4sICZsZHF1bztXZWIgU2VydmljZXMgRmVkZXJhdGlvbiBMYW5ndWFnZSAoV1Mt
RmVkZXJhdGlvbikgVmVyc2lvbiAxLjIsJnJkcXVvOyBNYXkmbmJzcDsyMDA5Ljwvc3Bhbj48c3Bh
bj4pPC9zcGFuPjwvYT4pIGFuZCB0aGUgQ0FQCiAgICAgIGVtZXJnZW5jeSBhbGVydGluZyBmb3Jt
YXQgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNDQVAnPltDQVBdPHNwYW4+ICg8L3NwYW4+PHNwYW4g
Y2xhc3M9J2luZm8nPkJvdHRlcmVsbCwgQS4gYW5kIEUuIEpvbmVzLCAmbGRxdW87Q29tbW9uIEFs
ZXJ0aW5nIFByb3RvY29sIHYxLjEsJnJkcXVvOyBPY3RvYmVyJm5ic3A7MjAwNS48L3NwYW4+PHNw
YW4+KTwvc3Bhbj48L2E+LiBJbiBwcmFjdGljZSwgaG93ZXZlciwKICAgICAgWE1MLWJhc2VkIHNl
Y3VyZSBvYmplY3QgZm9ybWF0cyBpbnRyb2R1Y2Ugc2ltaWxhciBsZXZlbHMgb2YgY29tcGxleGl0
eQogICAgICB0byBBU04uMSwgc28gZGV2ZWxvcGVycyB0aGF0IGxhY2sgdGhlIHRvb2xzIG9yIG1v
dGl2YXRpb24gdG8gaGFuZGxlCiAgICAgIEFTTi4xIGFyZW4ndCBsaWtlbHkgdG8gdXNlIFhNTCBz
ZWN1cml0eSBlaXRoZXIuIFRoaXMgc2l0dWF0aW9uIG1vdGl2YXRlcwogICAgICB0aGUgY3JlYXRp
b24gb2YgYSBKU09OLWJhc2VkIHNlY3VyZSBvYmplY3QgZm9ybWF0IHRoYXQgaXMgc2ltcGxlIGVu
b3VnaAogICAgICB0byBpbXBsZW1lbnQgYW5kIGRlcGxveSB0aGF0IGl0IGNhbiBiZSBlYXNpbHkg
YWRvcHRlZCBieSBkZXZlbG9wZXJzIHdpdGgKICAgICAgbWluaW1hbCBlZmZvcnQgYW5kIHRvb2xz
Lgo8L3A+CjxhIG5hbWU9ImRlZi1zZWMiPjwvYT48YnIgLz48aHIgLz4KPHRhYmxlIHN1bW1hcnk9
ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIyIiBjbGFzcz0iVE9DYnVnIiBh
bGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1ZyI+PGEgaHJlZj0iI3RvYyI+Jm5ic3A7
VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8YSBuYW1lPSJyZmMuc2VjdGlvbi4yIj48
L2E+PGgzPjIuJm5ic3A7CkRlZmluaXRpb25zPC9oMz4KCjxwPlRoaXMgZG9jdW1lbnQgbWFrZXMg
ZXh0ZW5zaXZlIHVzZSBvZiBzdGFuZGFyZCBzZWN1cml0eSB0ZXJtaW5vbG9neQogICAgICA8YSBj
bGFzcz0naW5mbycgaHJlZj0nI1JGQzQ5NDknPltSRkM0OTQ5XTxzcGFuPiAoPC9zcGFuPjxzcGFu
IGNsYXNzPSdpbmZvJz5TaGlyZXksIFIuLCAmbGRxdW87SW50ZXJuZXQgU2VjdXJpdHkgR2xvc3Nh
cnksIFZlcnNpb24gMiwmcmRxdW87IEF1Z3VzdCZuYnNwOzIwMDcuPC9zcGFuPjxzcGFuPik8L3Nw
YW4+PC9hPi4gSW4gYWRkaXRpb24sIGJlY2F1c2UgdGhlIHVzZSBjYXNlcyBmb3IgSk9TRQogICAg
ICBhbmQgQ01TIGFyZSBzaW1pbGFyLCB3ZSB3aWxsIHNvbWV0aW1lcyBtYWtlIGFuYWxvZ2llcyB0
byBzb21lIENNUwogICAgICBjb25jZXB0cyA8YSBjbGFzcz0naW5mbycgaHJlZj0nI1JGQzU2NTIn
PltSRkM1NjUyXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5Ib3VzbGV5LCBSLiwg
JmxkcXVvO0NyeXB0b2dyYXBoaWMgTWVzc2FnZSBTeW50YXggKENNUyksJnJkcXVvOyBTZXB0ZW1i
ZXImbmJzcDsyMDA5Ljwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4uCjwvcD4KPHA+VGhlIEpPU0Ug
d29ya2luZyBncm91cCBjaGFydGVyIGNhbGxzIGZvciB0aGUgZ3JvdXAgdG8gZGVmaW5lIHRocmVl
CiAgICAgIGJhc2ljIEpTT04gb2JqZWN0IGZvcm1hdHM6PC9wPgo8b2wgY2xhc3M9InRleHQiPgo8
bGk+Q29uZmlkZW50aWFsaXR5LXByb3RlY3RlZCBvYmplY3QgZm9ybWF0CjwvbGk+CjxsaT5JbnRl
Z3JpdHktcHJvdGVjdGVkIG9iamVjdCBmb3JtYXQKPC9saT4KPGxpPkEgZm9ybWF0IGZvciBleHBy
ZXNzaW5nIGtleXMKPC9saT4KPC9vbD48cD4KCiAgICAgIEluIHRoaXMgZG9jdW1lbnQsIHdlIHdp
bGwgcmVmZXIgdG8gdGhlc2UgYXMKICAgICAgdGhlICJzaWduZWQgb2JqZWN0IGZvcm1hdCIsCiAg
ICAgIHRoZSAiZW5jcnlwdGVkIG9iamVjdCBmb3JtYXQiLAogICAgICBhbmQgdGhlICJrZXkgZm9y
bWF0IiwgcmVzcGVjdGl2ZWx5LgogICAgICBUaGUgSk9TRSB3b3JraW5nIGdyb3VwIGl0ZW1zIGlu
dGVuZGVkIHRvIGRlc2NyaWJlIHRoZXNlIGZvcm1hdHMgYXJlIAogICAgICBKU09OIFdlYiBTaWdu
YXR1cmUgKEpXUyksIEpTT04gV2ViIEVuY3J5cHRpb24gKEpXRSksIGFuZCBKU09OIFdlYiBLZXkg
KEpXSyksCiAgICAgIHJlc3BlY3RpdmVseSA8YSBjbGFzcz0naW5mbycgaHJlZj0nI0ktRC5pZXRm
LWpvc2UtanNvbi13ZWItc2lnbmF0dXJlJz5bSSYjODIwOTtELmlldGYmIzgyMDk7am9zZSYjODIw
OTtqc29uJiM4MjA5O3dlYiYjODIwOTtzaWduYXR1cmVdPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xh
c3M9J2luZm8nPkpvbmVzLCBNLiwgQnJhZGxleSwgSi4sIGFuZCBOLiBTYWtpbXVyYSwgJmxkcXVv
O0pTT04gV2ViIFNpZ25hdHVyZSAoSldTKSwmcmRxdW87IE1heSZuYnNwOzIwMTMuPC9zcGFuPjxz
cGFuPik8L3NwYW4+PC9hPiwKICAgICAgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNJLUQuaWV0Zi1q
b3NlLWpzb24td2ViLWVuY3J5cHRpb24nPltJJiM4MjA5O0QuaWV0ZiYjODIwOTtqb3NlJiM4MjA5
O2pzb24mIzgyMDk7d2ViJiM4MjA5O2VuY3J5cHRpb25dPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xh
c3M9J2luZm8nPkpvbmVzLCBNLiwgUmVzY29ybGEsIEUuLCBhbmQgSi4gSGlsZGVicmFuZCwgJmxk
cXVvO0pTT04gV2ViIEVuY3J5cHRpb24gKEpXRSksJnJkcXVvOyBNYXkmbmJzcDsyMDEzLjwvc3Bh
bj48c3Bhbj4pPC9zcGFuPjwvYT4sIGFuZAogICAgICA8YSBjbGFzcz0naW5mbycgaHJlZj0nI0kt
RC5pZXRmLWpvc2UtanNvbi13ZWIta2V5Jz5bSSYjODIwOTtELmlldGYmIzgyMDk7am9zZSYjODIw
OTtqc29uJiM4MjA5O3dlYiYjODIwOTtrZXldPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2lu
Zm8nPkpvbmVzLCBNLiwgJmxkcXVvO0pTT04gV2ViIEtleSAoSldLKSwmcmRxdW87IE1heSZuYnNw
OzIwMTMuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPi4KICAgICAgQWxnb3JpdGhtcyBhbmQgYWxn
b3JpdGhtIGlkZW50aWZpZXJzIHVzZWQgYnkgSldTLCBKV0UsIGFuZCBKV0sgYXJlIGRlZmluZWQg
aW4KICAgICAgSlNPTiBXZWIgQWxnb3JpdGhtcyAoSldBKSA8YSBjbGFzcz0naW5mbycgaHJlZj0n
I0ktRC5pZXRmLWpvc2UtanNvbi13ZWItYWxnb3JpdGhtcyc+W0kmIzgyMDk7RC5pZXRmJiM4MjA5
O2pvc2UmIzgyMDk7anNvbiYjODIwOTt3ZWImIzgyMDk7YWxnb3JpdGhtc108c3Bhbj4gKDwvc3Bh
bj48c3BhbiBjbGFzcz0naW5mbyc+Sm9uZXMsIE0uLCAmbGRxdW87SlNPTiBXZWIgQWxnb3JpdGht
cyAoSldBKSwmcmRxdW87IE1heSZuYnNwOzIwMTMuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPi4K
ICAgICAgCjwvcD4KPHA+SW4gZ2VuZXJhbCwgd2hlcmUgdGhlcmUgaXMgbm8gbmVlZCB0byBkaXN0
aW5ndWlzaCBiZXR3ZWVuIGFzeW1tZXRyaWMgYW5kCiAgICAgIHN5bW1ldHJpYyBvcGVyYXRpb25z
LCB3ZSB3aWxsIHVzZSB0aGUgdGVybXMgInNpZ25pbmciLCAic2lnbmF0dXJlIiwgZXRjLgogICAg
ICB0byBkZW5vdGUgYm90aCB0cnVlIGRpZ2l0YWwgc2lnbmF0dXJlcyBpbnZvbHZpbmcgYXN5bW1l
dHJpYyBjcnlwdG9ncmFwaHkKICAgICAgYXMgd2VsbCBhcyBtZXNzYWdlIGF1dGhlbnRpY2F0aW9u
IGNvZGVzIHVzaW5nIHN5bW1ldHJpYyBrZXlzIChNQUNzKS4KPC9wPgo8cD5JbiB0aGUgbGlmZXNw
YW4gb2YgYSBzZWN1cmUgb2JqZWN0LCB0aGVyZSBhcmUgdHdvIGJhc2ljIHJvbGVzLCBhbgogICAg
ICBlbnRpdHkgdGhhdCBjcmVhdGVzIHRoZSBvYmplY3QgKGUuZy4sIGVuY3J5cHRpbmcgb3Igc2ln
bmluZyBhIHBheWxvYWQpLAogICAgICBhbmQgYW4gZW50aXR5IHRoYXQgdXNlcyB0aGUgb2JqZWN0
IChkZWNyeXB0aW5nLCB2ZXJpZnlpbmcpLiBXZSB3aWxsCiAgICAgIHJlZmVyIHRvIHRoZXNlIHJv
bGVzIGFzICJzZW5kZXIiIGFuZCAicmVjaXBpZW50IiwgcmVzcGVjdGl2ZWx5LiBOb3RlCiAgICAg
IHRoYXQgd2hpbGUgc29tZSByZXF1aXJlbWVudHMgYW5kIHVzZSBjYXNlcyBtYXkgcmVmZXIgdG8g
dGhlc2UgYXMgc2luZ2xlCiAgICAgIGVudGl0aWVzLCBlYWNoIG9iamVjdCBtYXkgaGF2ZSBtdWx0
aXBsZSBlbnRpdGllcyBpbiBlYWNoIHJvbGUuIEZvcgogICAgICBleGFtcGxlLCBhIG1lc3NhZ2Ug
bWF5IGJlIHNpZ25lZCBieSBtdWx0aXBsZSBzZW5kZXJzLCBvciBkZWNyeXB0ZWQgYnkKICAgICAg
bXVsdGlwbGUgcmVjaXBpZW50cy4KPC9wPgo8YSBuYW1lPSJiYXNpYy1zZWMiPjwvYT48YnIgLz48
aHIgLz4KPHRhYmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5n
PSIyIiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1ZyI+
PGEgaHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8YSBu
YW1lPSJyZmMuc2VjdGlvbi4zIj48L2E+PGgzPjMuJm5ic3A7CkJhc2ljIFJlcXVpcmVtZW50czwv
aDM+Cgo8cD5PYnZpb3VzbHksIGZvciB0aGUgZW5jcnlwdGVkIGFuZCBzaWduZWQgb2JqZWN0IGZv
cm1hdHMsIHRoZSBuZWNlc3NhcnkKICAgICAgcHJvdGVjdGlvbnMgd2lsbCBiZSBjcmVhdGVkIHVz
aW5nIGFwcHJvcHJpYXRlIGNyeXB0b2dyYXBoaWMgbWVjaGFuaXNtczoKICAgICAgc3ltbWV0cmlj
IG9yIGFzeW1tZXRyaWMgZW5jcnlwdGlvbiBmb3IgY29uZmlkZW50aWFsaXR5IGFuZCBNQUNzIG9y
CiAgICAgIGRpZ2l0YWwgc2lnbmF0dXJlcyBmb3IgaW50ZWdyaXR5IHByb3RlY3Rpb24uIEluIGJv
dGggY2FzZXMsIGl0IGlzCiAgICAgIG5lY2Vzc2FyeSBmb3IgdGhlIEpPU0UgZm9ybWF0IHRvIHN1
cHBvcnQgYm90aCBzeW1tZXRyaWMgYW5kIGFzeW1tZXRyaWMKICAgICAgb3BlcmF0aW9ucy48L3A+
Cjx1bCBjbGFzcz0idGV4dCI+CjxsaT5UaGUgSk9TRSBlbmNyeXB0ZWQgb2JqZWN0IGZvcm1hdCBt
dXN0IHN1cHBvcnQgb2JqZWN0IGVuY3J5cHRpb24KICAgICAgICAgIGluIHRoZSBjYXNlIHdoZXJl
IHRoZSBzZW5kZXIgYW5kIHJlY2VpdmVyIHNoYXJlIGEgc3ltbWV0cmljIGtleS4KPC9saT4KPGxp
PlRoZSBKT1NFIGVuY3J5cHRlZCBvYmplY3QgZm9ybWF0IG11c3Qgc3VwcG9ydCBvYmplY3QgZW5j
cnlwdGlvbgogICAgICAgICAgaW4gdGhlIGNhc2Ugd2hlcmUgdGhlIHNlbmRlciBoYXMgb25seSBh
IHB1YmxpYyBrZXkgZm9yIHRoZQogICAgICAgICAgcmVjZWl2ZXIuCjwvbGk+CjxsaT5UaGUgSk9T
RSBzaWduZWQgb2JqZWN0IGZvcm1hdCBtdXN0IHN1cHBvcnQgaW50ZWdyaXR5IHByb3RlY3Rpb24g
dXNpbmcKICAgICAgICAgIE1lc3NhZ2UgQXV0aGVudGljYXRpb24gQ29kZXMgKE1BQ3MpLCBmb3Ig
dGhlIGNhc2Ugd2hlcmUgdGhlIHNlbmRlcgogICAgICAgICAgYW5kIHJlY2VpdmVyIHNoYXJlIG9u
bHkgYSBzeW1tZXRyaWMga2V5Lgo8L2xpPgo8bGk+VGhlIEpPU0Ugc2lnbmVkIG9iamVjdCBmb3Jt
YXQgbXVzdCBzdXBwb3J0IGludGVncml0eSBwcm90ZWN0aW9uIHVzaW5nCiAgICAgICAgICBkaWdp
dGFsIHNpZ25hdHVyZXMsIGZvciB0aGUgY2FzZSB3aGVyZSB0aGUgcmVjZWl2ZXIgaGFzIG9ubHkg
YQogICAgICAgICAgcHVibGljIGtleSBmb3IgdGhlIHNlbmRlci4KPC9saT4KPC91bD4KCjxwPklu
IHNvbWUgYXBwbGljYXRpb25zLCB0aGUga2V5IHVzZWQgdG8gcHJvY2VzcyBhIEpPU0Ugb2JqZWN0
IGlzIGluZGljYXRlZAogICAgICBieSBhcHBsaWNhdGlvbiBjb250ZXh0LCBpbnN0ZWFkIG9mIGRp
cmVjdGx5IGluIHRoZSBKT1NFIG9iamVjdC4gIEhvd2V2ZXIsCiAgICAgIGluIG9yZGVyIHRvIGF2
b2lkIGNvbmZ1c2luZyBlbmRwb2ludHMgdGhhdCBsYWNrIHRoZSBuZWNlc3NhcnkgY29udGV4dCBu
ZWVkCiAgICAgIHRvIGJlIGFibGUgdG8gcmVjb2duaXplIHRoaXMgYW5kIGZhaWwgY2xlYW5seS4g
IE90aGVyIHRoYW4ga2V5cywgSk9TRSBvYmplY3RzIAogICAgICBkbyBub3Qgc3VwcG9ydCBwcmUt
bmVnb3RpYXRpb247IGFsbCBjcnlwdG9ncmFwaGljIHBhcmFtZXRlcnMgbXVzdCBiZSBleHByZXNz
ZWQKICAgICAgZGlyZWN0bHkgaW4gdGhlIEpPU0Ugb2JqZWN0LgogICAgICAgICAgPC9wPgo8dWwg
Y2xhc3M9InRleHQiPgo8bGk+VGhlIEpPU0Ugc2lnbmVkIGFuZCBlbmNyeXB0ZWQgb2JqZWN0IGZv
cm1hdHMgbXVzdCBkZWZpbmUgdGhlIHByb2Nlc3MKICAgICAgICAgIGJ5IHdoaWNoIGFuIGltcGxl
bWVudGF0aW9uIHJlY29nbml6ZXMgd2hldGhlciBpdCBoYXMgdGhlIGtleSByZXF1aXJlZAogICAg
ICAgICAgdG8gcHJvY2VzcyBhIGdpdmVuIG9iamVjdCBpbiB0aGUgY2FzZSB0aGF0IHRoZSBhcHBs
aWNhdGlvbiBkb2VzIG5vdAoJICBzcGVjaWZ5IHRoZSB1c2Ugb2YgYW5vdGhlciBtZWFucyBvciBj
b252ZW50aW9uIHRvIGRldGVybWluZSB0aGUga2V5IHVzZWQuCjwvbGk+CjxsaT5FYWNoIGFsZ29y
aXRobSB1c2VkIGZvciBKT1NFIG11c3QgZGVmaW5lIHdoaWNoIHBhcmFtZXRlcnMgYXJlIAogICAg
ICAgICAgcmVxdWlyZWQgdG8gYmUgcHJlc2VudCBpbiBhIEpPU0Ugb2JqZWN0IHVzaW5nIHRoYXQg
YWxnb3JpdGhtLgo8L2xpPgo8L3VsPjxwPgogICAgICAKPC9wPgo8cD5JbiBjYXNlcyB3aGVyZSB0
d28gZW50aXRpZXMgYXJlIGdvaW5nIHRvIGJlIGV4Y2hhbmdpbmcgc2V2ZXJhbCBKT1NFCiAgICAg
IG9iamVjdHMsIGl0IG1pZ2h0IGJlIGhlbHBmdWwgdG8gcHJlLW5lZ290aWF0ZSBzb21lIHBhcmFt
ZXRlcnMgc28gdGhhdCAKICAgICAgdGhleSBkbyBub3QgaGF2ZSB0byBiZSBzaWduYWxlZCBpbiBl
dmVyeSBKT1NFIG9iamVjdC4gIEhvd2V2ZXIsCiAgICAgIHNvIGFzIG5vdCB0byBjb25mdXNlIGVu
ZHBvaW50cyB0aGF0IGRvIG5vdCBzdXBwb3J0IHByZS1uZWdvdGlhdGlvbiwKICAgICAgaXQgaXMg
dXNlZnVsIHRvIHNpZ25hbCB3aGVuIHByZS1uZWdvdGlhdGVkIHBhcmFtZXRlcnMgYXJlIGluIHVz
ZSBpbiB0aG9zZSBjYXNlcy4KICAgICAgICAgIDwvcD4KPHVsIGNsYXNzPSJ0ZXh0Ij4KPGxpPkl0
IHNob3VsZCBiZSBwb3NzaWJsZSB0byBleHRlbmQgdGhlIGJhc2UKCSAgSk9TRSBzaWduZWQgYW5k
IGVuY3J5cHRlZCBvYmplY3QgZm9ybWF0cwoJICB0byBpbmRpY2F0ZSB0aGF0IHByZS1uZWdvdGlh
dGVkIHBhcmFtZXRlcnMgYXJlIHRvIGJlIHVzZWQgdG8gCiAgICAgICAgICBwcm9jZXNzIHRoZSBv
YmplY3QuICBUaGlzIGV4dGVuc2lvbiBzaG91bGQgYWxzbyBwcm92aWRlIGEgbWVhbnMgb2YgaW5k
aWNhdGluZyBvZiAKICAgICAgICAgIHdoaWNoIHBhcmFtZXRlcnMgYXJlIHRvIGJlIHVzZWQuCjwv
bGk+CjwvdWw+PHA+CiAgICAgIAo8L3A+CjxwPlRoZSBwdXJwb3NlIG9mIHRoZSBrZXkgZm9ybWF0
IGlzIHRvIHByb3ZpZGUgdGhlIHJlY2lwaWVudCB3aXRoCiAgICAgIHN1ZmZpY2llbnQgaW5mb3Jt
YXRpb24gdG8gdXNlIHRoZSBlbmNvZGVkIGtleSB0byBwcm9jZXNzIGNyeXB0b2dyYXBoaWMKICAg
ICAgbWVzc2FnZXMuIFRodXMgaXQgaXMgc29tZXRpbWVzIG5lY2Vzc2FyeSB0byBpbmNsdWRlIGFk
ZGl0aW9uYWwgcGFyYW1ldGVycyBhbG9uZwogICAgICB3aXRoIHRoZSBiYXJlIGtleS4KPC9wPgo8
cD48L3A+Cjx1bCBjbGFzcz0idGV4dCI+CjxsaT5UaGUgSk9TRSBrZXkgZm9ybWF0IG11c3QgZW5h
YmxlIGluY2x1c2lvbiBvZiBhbGwgYWxnb3JpdGhtIHBhcmFtZXRlcnMKICAgICAgICAgIG5lY2Vz
c2FyeSB0byB1c2UgdGhlIGVuY29kZWQga2V5LCBpbmNsdWRpbmcgYW4gaWRlbnRpZmllciBmb3Ig
dGhlCiAgICAgICAgICBhbGdvcml0aG0gd2l0aCB3aGljaCB0aGUga2V5IGlzIHVzZWQgYXMgd2Vs
bCBhcyBhbnkgYWRkaXRpb25hbAogICAgICAgICAgcGFyYW1ldGVycyByZXF1aXJlZCBieSB0aGUg
YWxnb3JpdGhtIChlLmcuLCBlbGxpcHRpYyBjdXJ2ZQogICAgICAgICAgcGFyYW1ldGVycykuCjwv
bGk+CjwvdWw+Cgo8YSBuYW1lPSJhcHAtcmVxLXNlYyI+PC9hPjxiciAvPjxociAvPgo8dGFibGUg
c3VtbWFyeT0ibGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJU
T0NidWciIGFsaWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9j
Ij4mbmJzcDtUT0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxhIG5hbWU9InJmYy5zZWN0
aW9uLjQiPjwvYT48aDM+NC4mbmJzcDsKUmVxdWlyZW1lbnRzIG9uIEFwcGxpY2F0aW9uIFByb3Rv
Y29sczwvaDM+Cgo8cD4KICAgICAgICBUaGUgSk9TRSBzZWN1cmUgb2JqZWN0IGZvcm1hdHMgZGVz
Y3JpYmUgaG93IGNyeXB0b2dyYXBoaWMgcHJvY2Vzc2luZyBpcyAKICAgICAgICBkb25lIG9uIHNl
Y3VyZWQgY29udGVudCwgZW5zdXJpbmcgdGhhdCB0aGUgcmVjaXBpZW50IGFuIG9iamVjdCBpcyBh
YmxlCiAgICAgICAgdG8gcHJvcGVybHkgZGVjcnlwdCBhbiBlbmNyeXB0ZWQgb2JqZWN0IG9yIHZl
cmlmeSBhIHNpZ25hdHVyZS4gIEluIG9yZGVyCiAgICAgICAgdG8gbWFrZSB1c2Ugb2YgSk9TRSwg
aG93ZXZlciwgYXBwbGljYXRpb25zIHdpbGwgbmVlZCB0byBzcGVjaWZ5IHNldmVyYWwKICAgICAg
ICBhc3BlY3RzIG9mIGhvdyBKT1NFIGlzIHRvIGJlIHVzZWQ6CiAgICAgICAgPC9wPgo8dWwgY2xh
c3M9InRleHQiPgo8bGk+V2hhdCBhcHBsaWNhdGlvbiBkYXRhIGlzIHRvIGJlIHByb3RlY3RlZAo8
L2xpPgo8bGk+V2hpY2ggY3J5cHRvZ3JhcGhpYyBhbGdvcml0aG1zIGFyZSB0byBiZSB1c2VkCjwv
bGk+CjxsaT5Ib3cgYXBwbGljYXRpb24gcHJvdG9jb2wgZW50aXRpZXMgZXN0YWJsaXNoIGtleXMK
PC9saT4KPGxpPldoZXRoZXIga2V5cyBhcmUgdG8gYmUgZXhwbGljaXRseSBpbmRpY2F0ZWQgaW4g
Sk9TRSBvYmplY3RzLCBvciAKICAgICAgICAgICAgIGFzc29jaWF0ZWQgYnkgYXBwbGljYXRpb24g
Y29udGV4dAo8L2xpPgo8L3VsPjxwPgogICAgICAKPC9wPgo8YSBuYW1lPSJ1c2UtY2FzZXMtc2Vj
Ij48L2E+PGJyIC8+PGhyIC8+Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIw
IiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNs
YXNzPSJUT0NidWciPjxhIGhyZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+
PC90YWJsZT4KPGEgbmFtZT0icmZjLnNlY3Rpb24uNSI+PC9hPjxoMz41LiZuYnNwOwpVc2UgQ2Fz
ZXM8L2gzPgoKPHA+U2V2ZXJhbCB3b3JraW5nIGdyb3VwcyBkZXZlbG9waW5nIGFwcGxpY2F0aW9u
LWxheWVyIHByb3RvY29scwogICAgICBoYXZlIGV4cHJlc3NlZCBhIGRlc2lyZSB0byB1c2UgdGhl
IEpPU0UgZGF0YSBmb3JtYXRzIGluIHRoZWlyCiAgICAgIGRlc2lnbnMgZm9yIGVuZC10by1lbmQg
c2VjdXJpdHkgZmVhdHVyZXMuIEluIHRoaXMgc2VjdGlvbiwgd2Ugc3VtbWFyaXplCiAgICAgIHRo
ZSB1c2UgY2FzZXMgcHJvcG9zZWQgYnkgdGhlc2UgZ3JvdXBzIGFuZCBkaXNjdXNzIHRoZSByZXF1
aXJlbWVudHMgdGhhdAogICAgICB0aGV5IGltcGx5IGZvciB0aGUgSk9TRSBvYmplY3QgZm9ybWF0
cy4KPC9wPgo8YSBuYW1lPSJzZWMtdG9rZW4tc2VjIj48L2E+PGJyIC8+PGhyIC8+Cjx0YWJsZSBz
dW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9IlRP
Q2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhyZWY9IiN0b2Mi
PiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0icmZjLnNlY3Rp
b24uNS4xIj48L2E+PGgzPjUuMS4mbmJzcDsKU2VjdXJpdHkgVG9rZW5zPC9oMz4KCjxwPlNlY3Vy
aXR5IHRva2VucyBhcmUgYSBjb21tb24gdXNlIGNhc2UgZm9yIG9iamVjdC1iYXNlZCBzZWN1cml0
eSwKICAgICAgICBmb3IgZXhhbXBsZSwgU0FNTCBhc3NlcnRpb25zIDxhIGNsYXNzPSdpbmZvJyBo
cmVmPScjT0FTSVMuc2FtbC1jb3JlLTIuMC1vcyc+W09BU0lTLnNhbWwmIzgyMDk7Y29yZSYjODIw
OTsyLjAmIzgyMDk7b3NdPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8nPkNhbnRvciwg
Uy4sIEtlbXAsIEouLCBQaGlscG90dCwgUi4sIGFuZCBFLiBNYWxlciwgJmxkcXVvO0Fzc2VydGlv
bnMgYW5kIFByb3RvY29sIGZvciB0aGUgT0FTSVMgU2VjdXJpdHkgQXNzZXJ0aW9uIE1hcmt1cCBM
YW5ndWFnZSAgICAgICAgICAgICAoU0FNTCkgVjIuMCwmcmRxdW87IE1hcmNoJm5ic3A7MjAwNS48
L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+LgogICAgICAgIFNlY3VyaXR5IHRva2VucyBhcmUgdXNl
ZCB0byBjb252ZXkgaW5mb3JtYXRpb24gYWJvdXQgYSBzdWJqZWN0IGVudGl0eQogICAgICAgICgi
Y2xhaW1zIiBvciAiYXNzZXJ0aW9ucyIpIGZyb20gYW4gaXNzdWVyIHRvIGEgcmVjaXBpZW50LiBU
aGUgc2VjdXJpdHkKICAgICAgICBmZWF0dXJlcyBvZiBhIHRva2VuIGZvcm1hdCBlbmFibGUgdGhl
IHJlY2lwaWVudCB0byB2ZXJpZnkgdGhhdCB0aGUKICAgICAgICBjbGFpbXMgY2FtZSBmcm9tIHRo
ZSBpc3N1ZXIgYW5kLCBpZiB0aGUgb2JqZWN0IGlzCiAgICAgICAgY29uZmlkZW50aWFsaXR5LXBy
b3RlY3RlZCwgdGhhdCB0aGV5IHdlcmUgbm90IHZpc2libGUgdG8gb3RoZXIKICAgICAgICBwYXJ0
aWVzLgo8L3A+CjxwPlNlY3VyaXR5IHRva2VucyBhcmUgdXNlZCBpbiBmZWRlcmF0aW9uIHByb3Rv
Y29scyBzdWNoIGFzIFNBTUwgMi4wCgk8YSBjbGFzcz0naW5mbycgaHJlZj0nI09BU0lTLnNhbWwt
Y29yZS0yLjAtb3MnPltPQVNJUy5zYW1sJiM4MjA5O2NvcmUmIzgyMDk7Mi4wJiM4MjA5O29zXTxz
cGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5DYW50b3IsIFMuLCBLZW1wLCBKLiwgUGhp
bHBvdHQsIFIuLCBhbmQgRS4gTWFsZXIsICZsZHF1bztBc3NlcnRpb25zIGFuZCBQcm90b2NvbCBm
b3IgdGhlIE9BU0lTIFNlY3VyaXR5IEFzc2VydGlvbiBNYXJrdXAgTGFuZ3VhZ2UgICAgICAgICAg
ICAgKFNBTUwpIFYyLjAsJnJkcXVvOyBNYXJjaCZuYnNwOzIwMDUuPC9zcGFuPjxzcGFuPik8L3Nw
YW4+PC9hPiwKICAgICAgICBXUy1GZWRlcmF0aW9uIDxhIGNsYXNzPSdpbmZvJyBocmVmPScjV1Mt
RmVkZXJhdGlvbic+W1dTJiM4MjA5O0ZlZGVyYXRpb25dPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xh
c3M9J2luZm8nPkthbGVyLCBDLiwgTWNJbnRvc2gsIE0uLCBHb29kbmVyLCBNLiwgYW5kIEEuIE5h
ZGFsaW4sICZsZHF1bztXZWIgU2VydmljZXMgRmVkZXJhdGlvbiBMYW5ndWFnZSAoV1MtRmVkZXJh
dGlvbikgVmVyc2lvbiAxLjIsJnJkcXVvOyBNYXkmbmJzcDsyMDA5Ljwvc3Bhbj48c3Bhbj4pPC9z
cGFuPjwvYT4sCglNb3ppbGxhIFBlcnNvbmEgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNQZXJzb25h
Jz5bUGVyc29uYV08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+TW96aWxsYSwgJmxk
cXVvO01vemlsbGEgUGVyc29uYSwmcmRxdW87IEFwcmlsJm5ic3A7MjAxMy48L3NwYW4+PHNwYW4+
KTwvc3Bhbj48L2E+LAoJYW5kIE9wZW5JRCBDb25uZWN0IDxhIGNsYXNzPSdpbmZvJyBocmVmPScj
T3BlbklELk1lc3NhZ2VzJz5bT3BlbklELk1lc3NhZ2VzXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNs
YXNzPSdpbmZvJz5TYWtpbXVyYSwgTi4sIEJyYWRsZXksIEouLCBKb25lcywgTS4sIGRlIE1lZGVp
cm9zLCBCLiwgTW9ydGltb3JlLCBDLiwgYW5kIEUuIEpheSwgJmxkcXVvO09wZW5JRCBDb25uZWN0
IE1lc3NhZ2VzIDEuMCwmcmRxdW87IEp1bmUmbmJzcDsyMDEzLjwvc3Bhbj48c3Bhbj4pPC9zcGFu
PjwvYT4sCglhcyB3ZWxsIGFzIGluIHJlc291cmNlIGF1dGhvcml6YXRpb24KICAgICAgICBwcm90
b2NvbHMgc3VjaCBhcyBPQXV0aCAyLjAgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM2NzQ5Jz5b
UkZDNjc0OV08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+SGFyZHQsIEQuLCAmbGRx
dW87VGhlIE9BdXRoIDIuMCBBdXRob3JpemF0aW9uIEZyYW1ld29yaywmcmRxdW87IE9jdG9iZXIm
bmJzcDsyMDEyLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4sCglpbmNsdWRpbmcgZm9yIE9BdXRo
IGJlYXJlciB0b2tlbnMgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM2NzUwJz5bUkZDNjc1MF08
c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+Sm9uZXMsIE0uIGFuZCBELiBIYXJkdCwg
JmxkcXVvO1RoZSBPQXV0aCAyLjAgQXV0aG9yaXphdGlvbiBGcmFtZXdvcms6IEJlYXJlciBUb2tl
biBVc2FnZSwmcmRxdW87IE9jdG9iZXImbmJzcDsyMDEyLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwv
YT4uIEluIHNvbWUgY2FzZXMsCiAgICAgICAgc2VjdXJpdHkgdG9rZW5zIGFyZSB1c2VkIGZvciBj
bGllbnQgYXV0aGVudGljYXRpb24gYW5kIGZvciBhY2Nlc3MKICAgICAgICBjb250cm9sIDxhIGNs
YXNzPSdpbmZvJyBocmVmPScjSS1ELmlldGYtb2F1dGgtand0LWJlYXJlcic+W0kmIzgyMDk7RC5p
ZXRmJiM4MjA5O29hdXRoJiM4MjA5O2p3dCYjODIwOTtiZWFyZXJdPHNwYW4+ICg8L3NwYW4+PHNw
YW4gY2xhc3M9J2luZm8nPkpvbmVzLCBNLiwgQ2FtcGJlbGwsIEIuLCBhbmQgQy4gTW9ydGltb3Jl
LCAmbGRxdW87SlNPTiBXZWIgVG9rZW4gKEpXVCkgUHJvZmlsZSBmb3IgT0F1dGggMi4wIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgQXV0aG9yaXphdGlvbiBHcmFudHMsJnJkcXVvOyBNYXJjaCZu
YnNwOzIwMTMuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPjxhIGNsYXNzPSdpbmZvJyBocmVmPScj
SS1ELmlldGYtb2F1dGgtc2FtbDItYmVhcmVyJz5bSSYjODIwOTtELmlldGYmIzgyMDk7b2F1dGgm
IzgyMDk7c2FtbDImIzgyMDk7YmVhcmVyXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZv
Jz5DYW1wYmVsbCwgQi4sIE1vcnRpbW9yZSwgQy4sIGFuZCBNLiBKb25lcywgJmxkcXVvO1NBTUwg
Mi4wIFByb2ZpbGUgZm9yIE9BdXRoIDIuMCBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEF1dGhv
cml6YXRpb24gR3JhbnRzLCZyZHF1bzsgTWFyY2gmbmJzcDsyMDEzLjwvc3Bhbj48c3Bhbj4pPC9z
cGFuPjwvYT4uCjwvcD4KPHA+SlNPTiBXZWIgVG9rZW4gKEpXVCkgPGEgY2xhc3M9J2luZm8nIGhy
ZWY9JyNJLUQuaWV0Zi1vYXV0aC1qc29uLXdlYi10b2tlbic+W0kmIzgyMDk7RC5pZXRmJiM4MjA5
O29hdXRoJiM4MjA5O2pzb24mIzgyMDk7d2ViJiM4MjA5O3Rva2VuXTxzcGFuPiAoPC9zcGFuPjxz
cGFuIGNsYXNzPSdpbmZvJz5Kb25lcywgTS4sIEJyYWRsZXksIEouLCBhbmQgTi4gU2FraW11cmEs
ICZsZHF1bztKU09OIFdlYiBUb2tlbiAoSldUKSwmcmRxdW87IE1heSZuYnNwOzIwMTMuPC9zcGFu
PjxzcGFuPik8L3NwYW4+PC9hPgoJaXMgYSBzZWN1cml0eSB0b2tlbiBmb3JtYXQKCWJhc2VkIG9u
IEpTT04gYW5kIEpPU0UuIEl0IGlzIHVzZWQgd2l0aCBNb3ppbGxhIFBlcnNvbmEsCglPcGVuSUQg
Q29ubmVjdCwgYW5kIE9BdXRoLiBCZWNhdXNlIEpXVHMgYXJlIG9mdGVuIHVzZWQgaW4gY29udGV4
dHMKCXdpdGggbGltaXRlZCBzcGFjZSAoZS5nLiwgSFRUUCBxdWVyeSBwYXJhbWV0ZXJzKSwgaXQg
aXMgYSBjb3JlCglyZXF1aXJlbWVudCBmb3IgSldUcywgYW5kIHRodXMgSk9TRSwgdG8gaGF2ZSBh
IGNvbXBhY3QsIFVSTC1zYWZlCglyZXByZXNlbnRhdGlvbi4KPC9wPgo8YSBuYW1lPSJvYXV0aC1z
ZWMiPjwvYT48YnIgLz48aHIgLz4KPHRhYmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9
IjAiIGNlbGxzcGFjaW5nPSIyIiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQg
Y2xhc3M9IlRPQ2J1ZyI+PGEgaHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90
cj48L3RhYmxlPgo8YSBuYW1lPSJyZmMuc2VjdGlvbi41LjIiPjwvYT48aDM+NS4yLiZuYnNwOwpP
QXV0aDwvaDM+Cgo8cD5UaGUgT0F1dGggcHJvdG9jb2wgZGVmaW5lcyBhIG1lY2hhbmlzbSBmb3Ig
ZGlzdHJpYnV0aW5nIGFuZCB1c2luZwogICAgICAgIGF1dGhvcml6YXRpb24gdG9rZW5zIHVzaW5n
IEhUVFAgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM2NzQ5Jz5bUkZDNjc0OV08c3Bhbj4gKDwv
c3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+SGFyZHQsIEQuLCAmbGRxdW87VGhlIE9BdXRoIDIuMCBB
dXRob3JpemF0aW9uIEZyYW1ld29yaywmcmRxdW87IE9jdG9iZXImbmJzcDsyMDEyLjwvc3Bhbj48
c3Bhbj4pPC9zcGFuPjwvYT4uIEEgQ2xpZW50CiAgICAgICAgdGhhdCB3aXNoZXMgdG8gYWNjZXNz
IGEgcHJvdGVjdGVkIHJlc291cmNlIHJlcXVlc3RzIGF1dGhvcml6YXRpb24gZnJvbQogICAgICAg
IHRoZSBSZXNvdXJjZSBPd25lci4gSWYgdGhlIFJlc291cmNlIE93bmVyIGFsbG93cyB0aGlzIGFj
Y2VzcywgaGUKICAgICAgICBkaXJlY3RzIGFuIEF1dGhvcml6YXRpb24gU2VydmVyIHRvIGlzc3Vl
IGFuIGFjY2VzcyB0b2tlbiB0byB0aGUKICAgICAgICBDbGllbnQuIFdoZW4gdGhlIENsaWVudCB3
aXNoZXMgdG8gYWNjZXNzIHRoZSBwcm90ZWN0ZWQgcmVzb3VyY2UsIGhlCiAgICAgICAgcHJlc2Vu
dHMgdGhlIHRva2VuIHRvIHRoZSByZWxldmFudCBSZXNvdXJjZSBTZXJ2ZXIsIHdoaWNoIHZlcmlm
aWVzIHRoZQogICAgICAgIHZhbGlkaXR5IG9mIHRoZSB0b2tlbiBiZWZvcmUgcHJvdmlkaW5nIGFj
Y2VzcyB0byB0aGUgcHJvdGVjdGVkCiAgICAgICAgcmVzb3VyY2UuCjwvcD48YnIgLz48aHIgY2xh
c3M9Imluc2VydCIgLz4KPGEgbmFtZT0iZmlnT0F1dGgiPjwvYT4KPGRpdiBzdHlsZT0nZGlzcGxh
eTogdGFibGU7IHdpZHRoOiAwOyBtYXJnaW4tbGVmdDogM2VtOyBtYXJnaW4tcmlnaHQ6IGF1dG8n
PjxwcmU+ICAgICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKyAgICAgICAgICArLS0tLS0tLS0t
LS0tLS0tKwogICAgICAgICAgICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgIHwgICAgICAg
ICAgICAgICB8CiAgICAgICAgICAgICAgfCAgIFJlc291cmNlICAgIHwmbHQ7Li4uLi4uLi4mZ3Q7
fCBBdXRob3JpemF0aW9uIHwKICAgICAgICAgICAgICB8ICAgIFNlcnZlciAgICAgfCAgICAgICAg
ICB8ICAgICBTZXJ2ZXIgICAgfAogICAgICAgICAgICAgIHwgICAgICAgICAgICAgICB8ICAgICAg
ICAgIHwgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLSsgICAg
ICAgICAgKy0tLS0tLS0tLS0tLS0tLSsKICAgICAgICAgICAgICAgICAgICAgICAgICAgXiAgICAg
ICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAg
fAogICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICstLS0tLS0tLS0tLS18LS0r
ICAgICAgICAgICstLXwtLS0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgfCAgICAgICAgICAgICst
LS0tLS0tLS0tLS0tLS0tKyAgICAgICAgICAgIHwKICAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgfCAgICAgICAgICB8ICAgUmVzb3VyY2UgICAgfAogICAgICAgICAgICAgIHwgICAgIENsaWVu
dCAgICB8ICAgICAgICAgIHwgICAgIE93bmVyICAgICB8CiAgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgIHwgICAgICAgICAgfCAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICArLS0tLS0t
LS0tLS0tLS0tKyAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tKzwvcHJlPjwvZGl2Pgo8cD4KPC9w
Pjx0YWJsZSBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgYWxpZ249
ImNlbnRlciI+PHRyPjx0ZCBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJtb25hY28sIE1TIFNh
bnMgU2VyaWYiIHNpemU9IjEiPjxiPiZuYnNwO0ZpZ3VyZSZuYnNwOzE6IFRoZSBPQXV0aCBwcm9j
ZXNzJm5ic3A7PC9iPjwvZm9udD48YnIgLz48L3RkPjwvdHI+PC90YWJsZT48aHIgY2xhc3M9Imlu
c2VydCIgLz4KCjxwPkluIGVmZmVjdCwgdGhpcyBwcm9jZXNzIG1vdmVzIHRoZSB0b2tlbiBmcm9t
IHRoZSBBdXRob3JpemF0aW9uCiAgICAgICAgU2VydmVyIChhcyBhIHNlbmRlciBvZiB0aGUgb2Jq
ZWN0KSB0byB0aGUgUmVzb3VyY2UgU2VydmVyIChyZWNpcGllbnQpLAogICAgICAgIHZpYSB0aGUg
Q2xpZW50IGFzIHdlbGwgYXMgdGhlIFJlc291cmNlIE93bmVyICh0aGUgbGF0dGVyIGJlY2F1c2Ug
b2YKICAgICAgICB0aGUgSFRUUCBtZWNoYW5pY3MgdW5kZXJseWluZyB0aGUgcHJvdG9jb2wpLiBT
byBhZ2FpbiB3ZSBoYXZlIGEgY2FzZQogICAgICAgIHdoZXJlIGFuIGFwcGxpY2F0aW9uIG9iamVj
dCBpcyB0cmFuc3BvcnRlZCB2aWEgdW50cnVzdGVkCiAgICAgICAgaW50ZXJtZWRpYXJpZXMuCjwv
cD4KPHA+VGhpcyBhcHBsaWNhdGlvbiBoYXMgdHdvIGVzc2VudGlhbCBzZWN1cml0eSByZXF1aXJl
bWVudHM6IEludGVncml0eQogICAgICAgIGFuZCBkYXRhIG9yaWdpbiBhdXRoZW50aWNhdGlvbi4g
SW50ZWdyaXR5IHByb3RlY3Rpb24gaXMgcmVxdWlyZWQgc28KICAgICAgICB0aGF0IHRoZSBSZXNv
dXJjZSBPd25lciBhbmQgdGhlIENsaWVudCBjYW5ub3QgbW9kaWZ5IHRoZSBwZXJtaXNzaW9uCiAg
ICAgICAgZW5jb2RlZCBpbiB0aGUgdG9rZW4uIERhdGEgb3JpZ2luIGF1dGhlbnRpY2F0aW9uIGlz
IHJlcXVpcmVkIHNvIHRoYXQKICAgICAgICB0aGUgUmVzb3VyY2UgU2VydmVyIGNhbiB2ZXJpZnkg
dGhhdCB0aGUgdG9rZW4gd2FzIGlzc3VlZCBieSBhIHRydXN0ZWQKICAgICAgICBBdXRob3JpemF0
aW9uIFNlcnZlci4gQ29uZmlkZW50aWFsaXR5IHByb3RlY3Rpb24gbWF5IGFsc28gYmUgbmVlZGVk
LAogICAgICAgIGlmIHRoZSBBdXRob3JpemF0aW9uIFNlcnZlciBpcyBjb25jZXJuZWQgYWJvdXQg
dGhlIHZpc2liaWxpdHkgb2YKICAgICAgICBwZXJtaXNzaW9ucyBpbmZvcm1hdGlvbiB0byB0aGUg
UmVzb3VyY2UgT3duZXIgb3IgQ2xpZW50LiBGb3IgZXhhbXBsZSwKICAgICAgICBwZXJtaXNzaW9u
cyByZWxhdGVkIHRvIHNvY2lhbCBuZXR3b3JraW5nIG1pZ2h0IGJlIGNvbnNpZGVyZWQgcHJpdmF0
ZQogICAgICAgIGluZm9ybWF0aW9uLiBOb3RlLCBob3dldmVyLCB0aGF0IE9BdXRoIGFscmVhZHkg
cmVxdWlyZXMgdGhhdCB0aGUKICAgICAgICB1bmRlcmx5aW5nIEhUVFAgdHJhbnNhY3Rpb25zIGJl
IHByb3RlY3RlZCBieSBUTFMsIHNvIGNvbmZpZGVudGlhbGl0eQogICAgICAgIHByb3RlY3Rpb24g
aXMgbm90IHN0cmljdGx5IG5lY2Vzc2FyeSBmb3IgdGhpcyB1c2UgY2FzZS4KPC9wPgo8cD5UaGUg
Y29uZmlkZW50aWFsaXR5IGFuZCBpbnRlZ3JpdHkgbmVlZHMgYXJlIG1ldCBieSB0aGUgYmFzaWMK
ICAgICAgICByZXF1aXJlbWVudHMgZm9yIHNpZ25lZCBhbmQgZW5jcnlwdGVkIG9iamVjdCBmb3Jt
YXRzLCB3aGV0aGVyIHRoZQogICAgICAgIHNpZ25pbmcgYW5kIGVuY3J5cHRpb24gYXJlIHByb3Zp
ZGVkIHVzaW5nIGFzeW1tZXRyaWMgb3Igc3ltbWV0cmljCiAgICAgICAgY3J5cHRvZ3JhcGh5LiBU
aGUgY2hvaWNlIG9mIHdoaWNoIG1lY2hhbmlzbSBpcyBhcHBsaWVkIHdpbGwgZGVwZW5kIG9uCiAg
ICAgICAgdGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuIHRoZSB0d28gc2VydmVycywgbmFtZWx5IHdo
ZXRoZXIgdGhleSBzaGFyZSBhCiAgICAgICAgc3ltbWV0cmljIGtleSBvciBvbmx5IHB1YmxpYyBr
ZXlzLgo8L3A+CjxwPkF1dGhlbnRpY2F0aW9uIHJlcXVpcmVtZW50cyB3aWxsIGFsc28gZGVwZW5k
IG9uIGRlcGxveW1lbnQKICAgICAgICBjaGFyYWN0ZXJpc3RpY3MuIFdoZXJlIHRoZXJlIGlzIGEg
cmVsYXRpdmVseSBzdHJvbmcgYmluZGluZyBiZXR3ZWVuCiAgICAgICAgdGhlIHJlc291cmNlIHNl
cnZlciBhbmQgdGhlIGF1dGhvcml6YXRpb24gc2VydmVyLCBpdCBtYXkgc3VmZmljZSBmb3IKICAg
ICAgICB0aGUgQXV0aG9yaXphdGlvbiBTZXJ2ZXIgaXNzdWluZyBhIHRva2VuIHRvIGJlIGlkZW50
aWZpZWQgYnkgdGhlIGtleQogICAgICAgIHVzZWQgdG8gc2lnbiB0aGUgdG9rZW4uIFRoaXMgcmVx
dWlyZXMgdGhhdCB0aGUgcHJvdG9jb2wgY2FycnkgZWl0aGVyIHRoZQogICAgICAgIHB1YmxpYyBr
ZXkgb2YgdGhlIEF1dGhvcml6YXRpb24gU2VydmVyIG9yIGFuIGlkZW50aWZpZXIgZm9yIHRoZSBw
dWJsaWMKICAgICAgICBvciBzeW1tZXRyaWMga2V5LiAgSW4gT0F1dGgsIHRoZSA8dHQ+Y2xpZW50
X2lkPC90dD4gCiAgICAgICAgcGFyYW1ldGVyIGlkZW50aWZpZXMgdGhlIGtleSB0byBiZSB1c2Vk
Lgo8L3A+CjxwPlRoZXJlIG1heSBhbHNvIGJlIG1vcmUgYWR2YW5jZWQgY2FzZXMsIHdoZXJlIHRo
ZSBBdXRob3JpemF0aW9uCiAgICAgICAgU2VydmVyJ3Mga2V5IGlzIG5vdCBrbm93biBpbiBhZHZh
bmNlIHRvIHRoZSBSZXNvdXJjZSBTZXJ2ZXIuIFRoaXMgbWF5CiAgICAgICAgaGFwcGVuLCBmb3Ig
aW5zdGFuY2UsIGlmIGFuIGVudGl0eSBpbnN0YW50aWF0ZWQgYSBjb2xsZWN0aW9uIG9mCiAgICAg
ICAgQXV0aG9yaXphdGlvbiBTZXJ2ZXJzIChzYXkgZm9yIGxvYWQgYmFsYW5jaW5nKSwgZWFjaCBv
ZiB3aGljaCBoYXMgYW4KICAgICAgICBpbmRlcGVuZGVudCBrZXkgcGFpci4gSW4gdGhlc2UgY2Fz
ZXMsIGl0IG1heSBiZSBuZWNlc3NhcnkgdG8gYWxzbwogICAgICAgIGluY2x1ZGUgYSBjZXJ0aWZp
Y2F0ZSBvciBjZXJ0aWZpY2F0ZSBjaGFpbiBmb3IgdGhlIEF1dGhvcml6YXRpb24KICAgICAgICBT
ZXJ2ZXIsIHNvIHRoYXQgdGhlIFJlc291cmNlIFNlcnZlciBjYW4gdmVyaWZ5IHRoYXQgdGhlIEF1
dGhvcml6YXRpb24KICAgICAgICBTZXJ2ZXIgaXMgYW4gZW50aXR5IHRoYXQgaXQgdHJ1c3RzLgo8
L3A+CjxwPlRoZSBIVFRQIHRyYW5zcG9ydCBmb3IgT0F1dGggaW1wb3NlcyBhIHBhcnRpY3VsYXIg
Y29uc3RyYWludCBvbiB0aGUKICAgICAgICBlbmNvZGluZy4gSW4gdGhlIE9BdXRoIHByb3RvY29s
LCB0b2tlbnMgZnJlcXVlbnRseSBuZWVkIHRvIGJlIHBhc3NlZAogICAgICAgIGFzIHF1ZXJ5IHBh
cmFtZXRlcnMgaW4gSFRUUCBVUklzIDxhIGNsYXNzPSdpbmZvJyBocmVmPScjUkZDMjYxNic+W1JG
QzI2MTZdPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8nPkZpZWxkaW5nLCBSLiwgR2V0
dHlzLCBKLiwgTW9ndWwsIEouLCBGcnlzdHlrLCBILiwgTWFzaW50ZXIsIEwuLCBMZWFjaCwgUC4s
IGFuZCBULiBCZXJuZXJzLUxlZSwgJmxkcXVvO0h5cGVydGV4dCBUcmFuc2ZlciBQcm90b2NvbCAt
LSBIVFRQLzEuMSwmcmRxdW87IEp1bmUmbmJzcDsxOTk5Ljwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwv
YT4sIGFmdGVyCiAgICAgICAgaGF2aW5nIGJlZW4gYmFzZTY0dXJsIGVuY29kZWQgPGEgY2xhc3M9
J2luZm8nIGhyZWY9JyNSRkM0NjQ4Jz5bUkZDNDY0OF08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFz
cz0naW5mbyc+Sm9zZWZzc29uLCBTLiwgJmxkcXVvO1RoZSBCYXNlMTYsIEJhc2UzMiwgYW5kIEJh
c2U2NCBEYXRhIEVuY29kaW5ncywmcmRxdW87IE9jdG9iZXImbmJzcDsyMDA2Ljwvc3Bhbj48c3Bh
bj4pPC9zcGFuPjwvYT4uIFdoaWxlIHRoZXJlIGlzCiAgICAgICAgbm8gc3BlY2lmaWVkIGxpbWl0
IG9uIHRoZSBsZW5ndGggb2YgVVJJcyAoYW5kIHRodXMgb2YgcXVlcnkKICAgICAgICBwYXJhbWV0
ZXJzKSwgaW4gcHJhY3RpY2UsIFVSSXMgb2YgbW9yZSB0aGFuIDIsMDQ4IGNoYXJhY3RlcnMgYXJl
CiAgICAgICAgcmVqZWN0ZWQgYnkgc29tZSB1c2VyIGFnZW50cy4gIEZvciBzb21lIG1vYmlsZSBi
cm93c2VycywgdGhpcyBsaW1pdCBpcyAKICAgICAgICBldmVuIHNtYWxsZXIuIFNvIHRoaXMgdXNl
IGNhc2UgcmVxdWlyZXMgdGhhdCBhIEpPU0UKICAgICAgICBvYmplY3QgaGF2ZSBzdWZmaWNpZW50
bHkgc21hbGwgc2l6ZSBldmVuIGFmdGVyIHNpZ25pbmcsIHBvc3NpYmx5CiAgICAgICAgZW5jcnlw
dGluZywgd2hpbGUgc3RpbGwgYmVpbmcgc2ltcGxlIHRvIGluY2x1ZGUgaW4gYW4gSFRUUCBVUkkg
cXVlcnkKICAgICAgICBwYXJhbWV0ZXIuCjwvcD4KPGEgbmFtZT0iZmVkLXNlYyI+PC9hPjxiciAv
PjxociAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNp
bmc9IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVn
Ij48YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFibGU+Cjxh
IG5hbWU9InJmYy5zZWN0aW9uLjUuMyI+PC9hPjxoMz41LjMuJm5ic3A7CkZlZGVyYXRpb248L2gz
PgoKPHA+U2VjdXJpdHkgdG9rZW5zIGFyZSB1c2VkIGluIHR3byBmZWRlcmF0ZWQgaWRlbnRpdHkg
cHJvdG9jb2xzOgo8L3A+CjxwPjwvcD4KPHVsIGNsYXNzPSJ0ZXh0Ij4KPGxpPlRoZSBPcGVuSUQg
Q29ubmVjdCBwcm90b2NvbCA8YSBjbGFzcz0naW5mbycgaHJlZj0nI09wZW5JRC5NZXNzYWdlcyc+
W09wZW5JRC5NZXNzYWdlc108c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+U2FraW11
cmEsIE4uLCBCcmFkbGV5LCBKLiwgSm9uZXMsIE0uLCBkZSBNZWRlaXJvcywgQi4sIE1vcnRpbW9y
ZSwgQy4sIGFuZCBFLiBKYXksICZsZHF1bztPcGVuSUQgQ29ubmVjdCBNZXNzYWdlcyAxLjAsJnJk
cXVvOyBKdW5lJm5ic3A7MjAxMy48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+CgkgICAgaXMgYSBz
aW1wbGUsIFJFU1QvSlNPTi1iYXNlZAoJICAgIGlkZW50aXR5IGZlZGVyYXRpb24gcHJvdG9jb2wg
bGF5ZXJlZCBvbiBPQXV0aCAyLjAuCgkgICAgSXQgdXNlcyB0aGUgSldUIGFuZCBKT1NFIGZvcm1h
dHMgYm90aAogICAgICAgICAgICB0byByZXByZXNlbnQgc2VjdXJpdHkgdG9rZW5zIGFuZCB0byBw
cm92aWRlIHNlY3VyaXR5IGZvciBvdGhlcgogICAgICAgICAgICBwcm90b2NvbCBtZXNzYWdlcyAo
cGVyZm9ybWluZyBzaWduaW5nIGFuZCBvcHRpb25hbGx5IGVuY3J5cHRpb24pLgoJICAgIE9wZW5J
RCBDb25uZWN0IG5lZ290aWF0ZXMgdGhlIGFsZ29yaXRobXMgdG8gYmUgdXNlZCBhbmQgZGlzdHJp
YnV0ZXMKCSAgICBpbmZvcm1hdGlvbiBhYm91dCB0aGUga2V5cyB0byBiZSB1c2VkIHVzaW5nIHBy
b3RvY29sIGVsZW1lbnRzCgkgICAgdGhhdCBhcmUgbm90IHBhcnQgb2YgdGhlIEpXVCBhbmQgSk9T
RSBoZWFkZXIgcGFyYW1ldGVycy4KPC9saT4KPGxpPlRoZSBNb3ppbGxhIFBlcnNvbmEgPGEgY2xh
c3M9J2luZm8nIGhyZWY9JyNQZXJzb25hJz5bUGVyc29uYV08c3Bhbj4gKDwvc3Bhbj48c3BhbiBj
bGFzcz0naW5mbyc+TW96aWxsYSwgJmxkcXVvO01vemlsbGEgUGVyc29uYSwmcmRxdW87IEFwcmls
Jm5ic3A7MjAxMy48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+IHN5c3RlbSBpcyBhIHNpbXBsZQoJ
ICAgIHNpbmdsZS1zaWduLW9uIChTU08pIHByb3RvY29sIHRoYXQgdXNlcyBKV1RzIHRoYXQgYXJl
IHNpZ25lZAoJICAgIEpPU0UgSldTIG9iamVjdHMgdG8gcmVwcmVzZW50IGluZm9ybWF0aW9uIGFi
b3V0IGlkZW50aXRpZXMsCgkgICAgYXBwbGljYXRpb25zLCBhbmQga2V5cyBmb3IgcGFydGljaXBh
dGluZyBlbnRpdGllcy4KCSAgICBQZXJzb25hIGRpc3RyaWJ1dGVzIHRoZSBrZXlzIHVzZWQgYXMg
Y2xhaW1zIGluIEpXVCBtZXNzYWdlcwoJICAgIGFuZCBub3QgYnkgdXNpbmcgSk9TRSBoZWFkZXIg
cGFyYW1ldGVycy4KCSAgICAKPC9saT4KPC91bD4KCjxhIG5hbWU9InhtcHAtc2VjIj48L2E+PGJy
IC8+PGhyIC8+Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3Bh
Y2luZz0iMiIgY2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNsYXNzPSJUT0Ni
dWciPjxhIGhyZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+PC90YWJsZT4K
PGEgbmFtZT0icmZjLnNlY3Rpb24uNS40Ij48L2E+PGgzPjUuNC4mbmJzcDsKWE1QUDwvaDM+Cgo8
cD5UaGUgRXh0ZW5zaWJsZSBNZXNzYWdpbmcgYW5kIFByZXNlbmNlIFByb3RvY29sIChYTVBQKSBy
b3V0ZXMKICAgICAgICBtZXNzYWdlcyBmcm9tIG9uZSBlbmQgY2xpZW50IHRvIGFub3RoZXIgYnkg
d2F5IG9mIFhNUFAgc2VydmVycyA8YSBjbGFzcz0naW5mbycgaHJlZj0nI1JGQzYxMjAnPltSRkM2
MTIwXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5TYWludC1BbmRyZSwgUC4sICZs
ZHF1bztFeHRlbnNpYmxlIE1lc3NhZ2luZyBhbmQgUHJlc2VuY2UgUHJvdG9jb2wgKFhNUFApOiBD
b3JlLCZyZHF1bzsgTWFyY2gmbmJzcDsyMDExLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4uIFRo
ZXJlIGFyZSB0eXBpY2FsbHkgdHdvIHNlcnZlcnMgaW52b2x2ZWQgaW4KICAgICAgICBkZWxpdmVy
aW5nIGFueSBnaXZlbiBtZXNzYWdlOiBUaGUgZmlyc3QgY2xpZW50IChBbGljZSkgc2VuZHMgYSBt
ZXNzYWdlCiAgICAgICAgZm9yIGFub3RoZXIgY2xpZW50IChCKSB0byBoZXIgc2VydmVyIChBKS4g
U2VydmVyIEEgdXNlcyBCb2IncyBpZGVudGl0eQogICAgICAgIGFuZCB0aGUgRE5TIHRvIGxvY2F0
ZSB0aGUgc2VydmVyIGZvciBCb2IncyBkb21haW4gKEIpLCB0aGVuIGRlbGl2ZXJzCiAgICAgICAg
dGhlIG1lc3NhZ2UgdG8gdGhhdCBzZXJ2ZXIuIFNlcnZlciBCIHRoZW4gcm91dGVzIHRoZSBtZXNz
YWdlIHRvCiAgICAgICAgQm9iLgo8L3A+PGJyIC8+PGhyIGNsYXNzPSJpbnNlcnQiIC8+CjxhIG5h
bWU9ImZpZy14bXBwIj48L2E+CjxkaXYgc3R5bGU9J2Rpc3BsYXk6IHRhYmxlOyB3aWR0aDogMDsg
bWFyZ2luLWxlZnQ6IDNlbTsgbWFyZ2luLXJpZ2h0OiBhdXRvJz48cHJlPgogICAgICAgICArLS0t
LS0tLSsgICArLS0tLS0tLS0tLSsgICArLS0tLS0tLS0tLSsgICArLS0tLS0rCiAgICAgICAgIHwg
QWxpY2UgfC0tJmd0O3wgU2VydmVyIEEgfC0tJmd0O3wgU2VydmVyIEIgfC0tJmd0O3wgQm9iIHwK
ICAgICAgICAgKy0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0tLS0tLS0rICAgKy0tLS0t
KzwvcHJlPjwvZGl2Pjx0YWJsZSBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2lu
Zz0iMiIgYWxpZ249ImNlbnRlciI+PHRyPjx0ZCBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJt
b25hY28sIE1TIFNhbnMgU2VyaWYiIHNpemU9IjEiPjxiPiZuYnNwO0ZpZ3VyZSZuYnNwOzI6IERl
bGl2ZXJpbmcgYW4gWE1QUCBtZXNzYWdlJm5ic3A7PC9iPjwvZm9udD48YnIgLz48L3RkPjwvdHI+
PC90YWJsZT48aHIgY2xhc3M9Imluc2VydCIgLz4KCjxwPlRoZSB1bnRydXN0ZWQtaW50ZXJtZWRp
YXJ5IHByb2JsZW1zIGFyZSBlc3BlY2lhbGx5IGFjdXRlIGZvciBYTVBQCiAgICAgICAgYmVjYXVz
ZSBpbiBtYW55IGN1cnJlbnQgZGVwbG95bWVudHMsIHRoZSBob2xkZXIgb2YgYW4gWE1QUCBkb21h
aW4KICAgICAgICBvdXRzb3VyY2VzIHRoZSBvcGVyYXRpb24gb2YgdGhlIGRvbWFpbidzIHNlcnZl
cnMgdG8gYSBkaWZmZXJlbnQKICAgICAgICBlbnRpdHkuIEluIHRoaXMgZW52aXJvbm1lbnQsIHRo
ZXJlIGlzIGEgY2xlYXIgcmlzayBvZiBleHBvc2luZyB0aGUKICAgICAgICBkb21haW4gaG9sZGVy
J3MgcHJpdmF0ZSBpbmZvcm1hdGlvbiB0byB0aGUgZG9tYWluIG9wZXJhdG9yLiBYTVBQCiAgICAg
ICAgYWxyZWFkeSBoYXMgYSBkZWZpbmVkIG1lY2hhbmlzbSBmb3IgZW5kLXRvLWVuZCBzZWN1cml0
eSB1c2luZyBTL01JTUUsCiAgICAgICAgYnV0IGl0IGhhcyBmYWlsZWQgdG8gZ2FpbiB3aWRlc3By
ZWFkIGRlcGxveW1lbnQgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkMzOTIzJz5bUkZDMzkyM108
c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+U2FpbnQtQW5kcmUsIFAuLCAmbGRxdW87
RW5kLXRvLUVuZCBTaWduaW5nIGFuZCBPYmplY3QgRW5jcnlwdGlvbiBmb3IgdGhlIEV4dGVuc2li
bGUgTWVzc2FnaW5nIGFuZCBQcmVzZW5jZSBQcm90b2NvbCAoWE1QUCksJnJkcXVvOyBPY3RvYmVy
Jm5ic3A7MjAwNC48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+LCBpbiBwYXJ0IGJlY2F1c2Ugb2Yg
a2V5IG1hbmFnZW1lbnQgY2hhbGxlbmdlcyBhbmQKICAgICAgICBiZWNhdXNlIG9mIHRoZSBkaWZm
aWN1bHR5IG9mIHByb2Nlc3NpbmcgUy9NSU1FIG9iamVjdHMuCjwvcD4KPHA+VGhlIFhNUFAgd29y
a2luZyBncm91cCBpcyBpbiB0aGUgcHJvY2VzcyBvZiBkZXZlbG9waW5nIGEgbmV3CiAgICAgICAg
ZW5kLXRvLWVuZCBlbmNyeXB0aW9uIHN5c3RlbSB3aXRoIGFuIGVuY29kaW5nIGJhc2VkIG9uIEpP
U0UgYW5kIGEKICAgICAgICBjbGVhcmVyIGtleSBtYW5hZ2VtZW50IHN5c3RlbSA8YSBjbGFzcz0n
aW5mbycgaHJlZj0nI0ktRC5taWxsZXIteG1wcC1lMmUnPltJJiM4MjA5O0QubWlsbGVyJiM4MjA5
O3htcHAmIzgyMDk7ZTJlXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5NaWxsZXIs
IE0uLCAmbGRxdW87RW5kLXRvLUVuZCBPYmplY3QgRW5jcnlwdGlvbiBmb3IgdGhlIEV4dGVuc2li
bGUgTWVzc2FnaW5nIGFuZCBQcmVzZW5jZSBQcm90b2NvbCAoWE1QUCksJnJkcXVvOyBNYXkmbmJz
cDsyMDEzLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4uCiAgICAgICAgVGhlIHByb2Nlc3Mgb2Yg
c2VuZGluZyBhbiBlbmNyeXB0ZWQgbWVzc2FnZSBpbiB0aGlzIHN5c3RlbSBpbnZvbHZlcwogICAg
ICAgIHR3byBzdGVwczogRmlyc3QsIHRoZSBzZW5kZXIgZ2VuZXJhdGVzIGEgc3ltbWV0cmljIENv
bnRlbnQgRW5jcnlwdGlvbgogICAgICAgIEtleSAoQ0VLKSwgZW5jcnlwdHMgdGhlIG1lc3NhZ2Ug
Y29udGVudCwgYW5kIHNlbmRzIHRoZSBlbmNyeXB0ZWQKICAgICAgICBtZXNzYWdlIHRvIHRoZSBk
ZXNpcmVkIHNldCBvZiByZWNpcGllbnRzLiBTZWNvbmQsIGVhY2ggcmVjaXBpZW50CiAgICAgICAg
ImRpYWxzIGJhY2siIHRvIHRoZSBzZW5kZXIsIHByb3ZpZGluZyBoaXMgcHVibGljIGtleTsgdGhl
IHNlbmRlciB0aGVuCiAgICAgICAgcmVzcG9uZHMgd2l0aCB0aGUgcmVsZXZhbnQgQ0VLLCB3cmFw
cGVkIHdpdGggdGhlIHJlY2lwaWVudCdzIHB1YmxpYwogICAgICAgIGtleS4KPC9wPjxiciAvPjxo
ciBjbGFzcz0iaW5zZXJ0IiAvPgo8YSBuYW1lPSJmaWcteG1wcC1zZWMiPjwvYT4KPGRpdiBzdHls
ZT0nZGlzcGxheTogdGFibGU7IHdpZHRoOiAwOyBtYXJnaW4tbGVmdDogM2VtOyBtYXJnaW4tcmln
aHQ6IGF1dG8nPjxwcmU+CiAgICAgICAgICstLS0tLS0tKyAgICstLS0tLS0tLS0tKyAgICstLS0t
LS0tLS0tKyAgICstLS0tLSsKICAgICAgICAgfCBBbGljZSB8Jmx0Oy0mZ3Q7fCBTZXJ2ZXIgQSB8
Jmx0Oy0mZ3Q7fCBTZXJ2ZXIgQiB8Jmx0Oy0mZ3Q7fCBCb2IgfAogICAgICAgICArLS0tLS0tLSsg
ICArLS0tLS0tLS0tLSsgICArLS0tLS0tLS0tLSsgICArLS0tLS0rCiAgICAgICAgICAgICB8ICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgIHwgICAgICAgICAgIHwKICAgICAgICAgICAgIHwtLS0t
LS0tLS0tLS1FbmNyeXB0ZWQtLW1lc3NhZ2UtLS0tLS0tLS0mZ3Q7fAogICAgICAgICAgICAgfCAg
ICAgICAgICAgICB8ICAgICAgICAgICAgICB8ICAgICAgICAgICB8CiAgICAgICAgICAgICB8Jmx0
Oy0tLS0tLS0tLS0tLS0tLVB1YmxpYy1rZXktLS0tLS0tLS0tLS0tLXwKICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgfCAgICAgICAgICAgICAgfCAgICAgICAgICAgfAogICAgICAgICAgICAgfC0t
LS0tLS0tLS0tLS0tLVdyYXBwZWQgQ0VLLS0tLS0tLS0tLS0tLSZndDt8CiAgICAgICAgICAgICB8
ICAgICAgICAgICAgIHwgICAgICAgICAgICAgIHwgICAgICAgICAgIHw8L3ByZT48L2Rpdj48dGFi
bGUgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGFsaWduPSJjZW50
ZXIiPjx0cj48dGQgYWxpZ249ImNlbnRlciI+PGZvbnQgZmFjZT0ibW9uYWNvLCBNUyBTYW5zIFNl
cmlmIiBzaXplPSIxIj48Yj4mbmJzcDtGaWd1cmUmbmJzcDszOiBEZWxpdmVyaW5nIGEgc2VjdXJl
IFhNUFAgbWVzc2FnZSZuYnNwOzwvYj48L2ZvbnQ+PGJyIC8+PC90ZD48L3RyPjwvdGFibGU+PGhy
IGNsYXNzPSJpbnNlcnQiIC8+Cgo8cD5UaGUgbWFpbiB0aGluZyB0aGF0IHRoaXMgc3lzdGVtIHJl
cXVpcmVzIGZyb20gdGhlIEpPU0UgZm9ybWF0cyBpcwogICAgICAgIGNvbmZpZGVudGlhbGl0eSBw
cm90ZWN0aW9uIHZpYSBjb250ZW50IGVuY3J5cHRpb24sIHBsdXMgYW4gaW50ZWdyaXR5CiAgICAg
ICAgY2hlY2sgdmlhIGEgTUFDIGRlcml2ZWQgZnJvbSB0aGUgc2FtZSBzeW1tZXRyaWMga2V5LiBU
aGUgc2VwYXJhdGlvbiBvZgogICAgICAgIHRoZSBrZXkgZXhjaGFuZ2UgZnJvbSB0aGUgdHJhbnNt
aXNzaW9uIG9mIHRoZSBlbmNyeXB0ZWQgY29udGVudCwKICAgICAgICBob3dldmVyLCByZXF1aXJl
cyB0aGF0IHRoZSBKT1NFIGVuY3J5cHRlZCBvYmplY3QgZm9ybWF0IGFsbG93IHdyYXBwZWQKICAg
ICAgICBzeW1tZXRyaWMga2V5cyB0byBiZSBjYXJyaWVkIHNlcGFyYXRlbHkgZnJvbSB0aGUgZW5j
cnlwdGVkIHBheWxvYWQuIEluCiAgICAgICAgYWRkaXRpb24sIHRoZSBlbmNyeXB0ZWQgb2JqZWN0
IHdpbGwgbmVlZCB0byBoYXZlIGEgdGFnIGZvciB0aGUga2V5CiAgICAgICAgdGhhdCB3YXMgdXNl
ZCB0byBlbmNyeXB0IHRoZSBjb250ZW50LCBzbyB0aGF0IHRoZSByZWNpcGllbnQgKEJvYikgY2Fu
CiAgICAgICAgcHJlc2VudCB0aGUgdGFnIHRvIHRoZSBzZW5kZXIgKEFsaWNlKSB3aGVuIHJlcXVl
c3RpbmcgdGhlIHdyYXBwZWQKICAgICAgICBrZXkuCjwvcD4KPHA+QW5vdGhlciBpbXBvcnRhbnQg
ZmVhdHVyZSBvZiBYTVBQIGlzIHRoYXQgaXQgYWxsb3dzIGZvciB0aGUKICAgICAgICBzaW11bHRh
bmVvdXMgZGVsaXZlcnkgb2YgYSBtZXNzYWdlIHRvIG11bHRpcGxlIHJlY2lwaWVudHMuIEluIHRo
ZQogICAgICAgIGRpYWdyYW1zIGFib3ZlLCBTZXJ2ZXIgQSBjb3VsZCBkZWxpdmVyIHRoZSBtZXNz
YWdlIG5vdCBvbmx5IHRvIFNlcnZlcgogICAgICAgIEIgKGZvciBCb2IpIGJ1dCBhbHNvIHRvIFNl
cnZlcnMgQywgRCwgRSwgZXRjLiBmb3Igb3RoZXIgdXNlcnMuIEluIHN1Y2gKICAgICAgICBjYXNl
cywgdG8gYXZvaWQgdGhlIG11bHRpcGxlICJkaWFsIGJhY2siIHRyYW5zYWN0aW9ucyBpbXBsaWVk
IGJ5IHRoZQogICAgICAgIGFib3ZlIG1lY2hhbmlzbSwgWE1QUCBzeXN0ZW1zIHdpbGwgbGlrZWx5
IGNhY2hlIHB1YmxpYyBrZXlzIGZvciBlbmQKICAgICAgICByZWNpcGllbnRzLCBzbyB0aGF0IHdy
YXBwZWQga2V5cyBjYW4gYmUgc2VudCBhbG9uZyB3aXRoIGNvbnRlbnQgb24KICAgICAgICBmdXR1
cmUgbWVzc2FnZXMuIFRoaXMgaW1wbGllcyB0aGF0IHRoZSBKT1NFIGVuY3J5cHRlZCBvYmplY3Qg
Zm9ybWF0CiAgICAgICAgbXVzdCBzdXBwb3J0IHRoZSBwcm92aXNpb24gb2YgbXVsdGlwbGUgdmVy
c2lvbnMgb2YgdGhlIHNhbWUgd3JhcHBlZAogICAgICAgIENFSyAobXVjaCBhcyBhIENNUyBFbnZl
bG9wZWREYXRhIHN0cnVjdHVyZSBjYW4gaW5jbHVkZSBtdWx0aXBsZQogICAgICAgIFJlY2lwaWVu
dEluZm8gc3RydWN0dXJlcykuCjwvcD4KPHA+SW4gdGhlIGN1cnJlbnQgZHJhZnQgb2YgdGhlIFhN
UFAgZW5kLXRvLWVuZCBzZWN1cml0eSBzeXN0ZW0sIGVhY2gKICAgICAgICBwYXJ0eSBpcyBhdXRo
ZW50aWNhdGVkIGJ5IHZpcnR1ZSBvZiB0aGUgb3RoZXIgcGFydHkncyB0cnVzdCBpbiB0aGUKICAg
ICAgICBYTVBQIG1lc3NhZ2Ugcm91dGluZyBzeXN0ZW0uIFRoZSBzZW5kZXIgaXMgYXV0aGVudGlj
YXRlZCB0byB0aGUKICAgICAgICByZWNlaXZlciBiZWNhdXNlIGhlIGNhbiByZWNlaXZlIG1lc3Nh
Z2VzIGZvciB0aGUgaWRlbnRpZmllciAiQWxpY2UiCiAgICAgICAgKGluIHBhcnRpY3VsYXIsIHRo
ZSByZXF1ZXN0IGZvciB3cmFwcGVkIGtleXMpLCBhbmQgY2FuIG9yaWdpbmF0ZQogICAgICAgIG1l
c3NhZ2VzIGZvciB0aGF0IGlkZW50aWZpZXIgKHRoZSB3cmFwcGVkIGtleSkuIExpa2V3aXNlLCB0
aGUgcmVjZWl2ZXIKICAgICAgICBpcyBhdXRoZW50aWNhdGVkIHRvIHRoZSBzZW5kZXIgYmVjYXVz
ZSBoZSByZWNlaXZlZCB0aGUgb3JpZ2luYWwKICAgICAgICBlbmNyeXB0ZWQgbWVzc2FnZSBhbmQg
b3JpZ2luYXRlZCB0aGUgcmVxdWVzdCBmb3Igd3JhcHBlZCBrZXkuIFNvIHRoZQogICAgICAgIGF1
dGhlbnRpY2F0aW9uIGhlcmUgcmVxdWlyZXMgbm90IG9ubHkgdGhhdCBYTVBQIHJvdXRpbmcgYmUg
ZG9uZQogICAgICAgIHByb3Blcmx5LCBidXQgYWxzbyB0aGF0IFRMUyBiZSB1c2VkIG9uIGV2ZXJ5
IGhvcC4gTW9yZW92ZXIsIGl0CiAgICAgICAgcmVxdWlyZXMgdGhhdCB0aGUgVExTIGNoYW5uZWxz
IGhhdmUgc3Ryb25nIGF1dGhlbnRpY2F0aW9uLCBzaW5jZSBhIG1hbgogICAgICAgIGluIHRoZSBt
aWRkbGUgb24gYW55IG9mIHRoZSB0aHJlZSBob3BzIGNhbiBtYXNxdWVyYWRlIGFzIEJvYiBhbmQK
ICAgICAgICBvYnRhaW4gdGhlIGtleSBtYXRlcmlhbCBmb3IgYW4gZW5jcnlwdGVkIG1lc3NhZ2Uu
CjwvcD4KPHA+QmVjYXVzZSB0aGlzIGF1dGhlbnRpY2F0aW9uIGlzIHF1aXRlIHdlYWsgKGRlcGVu
ZGluZyBvbiB0aGUgdXNlIG9mCiAgICAgICAgdHJhbnNwb3J0LWxheWVyIHNlY3VyaXR5IG9uIHRo
cmVlIGhvcHMpIGFuZCB1bnZlcmlmaWFibGUgYnkgdGhlCiAgICAgICAgZW5kcG9pbnRzLCBpdCBp
cyBwb3NzaWJsZSB0aGF0IHRoZSBYTVBQIHdvcmtpbmcgZ3JvdXAgd2lsbCBpbnRlZ3JhdGUKICAg
ICAgICBzb21lIHNvcnQgb2YgY3JlZGVudGlhbHMgZm9yIGVuZCByZWNpcGllbnRzLCBpbiB3aGlj
aCBjYXNlIHRoZXJlIHdvdWxkCiAgICAgICAgbmVlZCB0byBiZSBhIHdheSB0byBhc3NvY2lhdGUg
dGhlc2UgY3JlZGVudGlhbHMgd2l0aCBKT1NFIG9iamVjdHMuCjwvcD4KPHA+RmluYWxseSwgaXQn
cyB3b3J0aCBub3RpbmcgdGhhdCBYTVBQIGlzIGJhc2VkIG9uIFhNTCwgbm90IEpTT04uIFNvCiAg
ICAgICAgYnkgdXNpbmcgSk9TRSwgWE1QUCB3aWxsIGJlIGNhcnJ5aW5nIEpTT04gb2JqZWN0cyB3
aXRoaW4gWE1MLiBJdCBpcwogICAgICAgIHRodXMgYSBkZXNpcmFibGUgcHJvcGVydHkgZm9yIEpP
U0Ugb2JqZWN0cyB0byBiZSBlbmNvZGVkIGluIHN1Y2ggYSB3YXkKICAgICAgICBhcyB0byBiZSBz
YWZlIGZvciBpbmNsdXNpb24gaW4gWE1MLiBPdGhlcndpc2UsIGFuIGV4cGxpY2l0IENEQVRBCiAg
ICAgICAgaW5kaWNhdGlvbiBtdXN0IGJlIGdpdmVuIHRvIHRoZSBwYXJzZXIgdG8gaW5kaWNhdGUg
dGhhdCBpdCBpcyBub3QgdG8KICAgICAgICBiZSBwYXJzZWQgYXMgWE1MLiBPbmUgd2F5IHRvIG1l
ZXQgdGhpcyByZXF1aXJlbWVudCB3b3VsZCBiZSB0byBhcHBseQogICAgICAgIGJhc2U2NHVybCBl
bmNvZGluZywgYnV0IGZvciBYTVBQIG1lc3NhZ2VzIG9mIG1lZGl1bS10by1sYXJnZSBzaXplLAog
ICAgICAgIHRoaXMgY291bGQgaW1wb3NlIGEgZmFpciBkZWdyZWUgb2Ygb3ZlcmhlYWQuCjwvcD4K
PGEgbmFtZT0iYWx0by1zZWMiPjwvYT48YnIgLz48aHIgLz4KPHRhYmxlIHN1bW1hcnk9ImxheW91
dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIyIiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0i
cmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1ZyI+PGEgaHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5i
c3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8YSBuYW1lPSJyZmMuc2VjdGlvbi41LjUiPjwvYT48
aDM+NS41LiZuYnNwOwpBTFRPPC9oMz4KCjxwPkFwcGxpY2F0aW9uLUxheWVyIFRyYWZmaWMgT3B0
aW1pemF0aW9uIChBTFRPKSBpcyBhIHN5c3RlbSBmb3IKICAgICAgICBkaXN0cmlidXRpbmcgbmV0
d29yayB0b3BvbG9neSBpbmZvcm1hdGlvbiB0byBlbmQgZGV2aWNlcywgc28gdGhhdAogICAgICAg
IHRob3NlIGRldmljZXMgY2FuIG1vZGlmeSB0aGVpciBiZWhhdmlvciB0byBoYXZlIGEgbG93ZXIg
aW1wYWN0IG9uIHRoZQogICAgICAgIG5ldHdvcmsgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM2
NzA4Jz5bUkZDNjcwOF08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+S2llc2VsLCBT
LiwgUHJldmlkaSwgUy4sIFN0aWVtZXJsaW5nLCBNLiwgV291bmR5LCBSLiwgYW5kIFkuIFlhbmcs
ICZsZHF1bztBcHBsaWNhdGlvbi1MYXllciBUcmFmZmljIE9wdGltaXphdGlvbiAoQUxUTykgUmVx
dWlyZW1lbnRzLCZyZHF1bzsgU2VwdGVtYmVyJm5ic3A7MjAxMi48L3NwYW4+PHNwYW4+KTwvc3Bh
bj48L2E+LiBUaGUgQUxUTyBwcm90b2NvbAogICAgICAgIGRpc3RyaWJ1dGVzIHRvcG9sb2d5IGlu
Zm9ybWF0aW9uIGluIHRoZSBmb3JtIG9mIEpTT04gb2JqZWN0cyBjYXJyaWVkCiAgICAgICAgaW4g
SFRUUCA8YSBjbGFzcz0naW5mbycgaHJlZj0nI1JGQzI2MTYnPltSRkMyNjE2XTxzcGFuPiAoPC9z
cGFuPjxzcGFuIGNsYXNzPSdpbmZvJz5GaWVsZGluZywgUi4sIEdldHR5cywgSi4sIE1vZ3VsLCBK
LiwgRnJ5c3R5aywgSC4sIE1hc2ludGVyLCBMLiwgTGVhY2gsIFAuLCBhbmQgVC4gQmVybmVycy1M
ZWUsICZsZHF1bztIeXBlcnRleHQgVHJhbnNmZXIgUHJvdG9jb2wgLS0gSFRUUC8xLjEsJnJkcXVv
OyBKdW5lJm5ic3A7MTk5OS48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+PGEgY2xhc3M9J2luZm8n
IGhyZWY9JyNJLUQuaWV0Zi1hbHRvLXByb3RvY29sJz5bSSYjODIwOTtELmlldGYmIzgyMDk7YWx0
byYjODIwOTtwcm90b2NvbF08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+QWxpbWks
IFIuLCBQZW5ubywgUi4sIGFuZCBZLiBZYW5nLCAmbGRxdW87QUxUTyBQcm90b2NvbCwmcmRxdW87
IE1heSZuYnNwOzIwMTMuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPi4gVGhlIGJhc2ljIHZlcnNp
b24gb2YgQUxUTyBpcyBzaW1wbHkKICAgICAgICBhIGNsaWVudC1zZXJ2ZXIgcHJvdG9jb2wsIHNv
IHNpbXBsZSB1c2Ugb2YgSFRUUFMgc3VmZmljZXMgZm9yIHRoaXMKICAgICAgICBjYXNlIDxhIGNs
YXNzPSdpbmZvJyBocmVmPScjUkZDMjgxOCc+W1JGQzI4MThdPHNwYW4+ICg8L3NwYW4+PHNwYW4g
Y2xhc3M9J2luZm8nPlJlc2NvcmxhLCBFLiwgJmxkcXVvO0hUVFAgT3ZlciBUTFMsJnJkcXVvOyBN
YXkmbmJzcDsyMDAwLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4uIEhvd2V2ZXIsIHRoZXJlIGlz
IGJlZ2lubmluZyB0byBiZSBzb21lCiAgICAgICAgZGlzY3Vzc2lvbiBvZiB1c2UgY2FzZXMgZm9y
IEFMVE8gaW4gd2hpY2ggdGhlc2UgSlNPTiBvYmplY3RzIHdpbGwgYmUKICAgICAgICBkaXN0cmli
dXRlZCB0aHJvdWdoIGEgY29sbGVjdGlvbiBvZiBpbnRlcm1lZGlhdGUgc2VydmVycyBiZWZvcmUK
ICAgICAgICByZWFjaGluZyB0aGUgY2xpZW50LCB3aGlsZSBzdGlsbCBwcmVzZXJ2aW5nIHRoZSBh
YmlsaXR5IG9mIHRoZSBjbGllbnQKICAgICAgICB0byBhdXRoZW50aWNhdGUgdGhlIG9yaWdpbmFs
IHNvdXJjZSBvZiB0aGUgb2JqZWN0LiBFdmVuIHRoZSBiYXNlIEFMVE8KICAgICAgICBwcm90b2Nv
bCBub3RlcyB0aGF0ICJBTFRPIGNsaWVudHMgb2J0YWluaW5nIEFMVE8gaW5mb3JtYXRpb24gbXVz
dCBiZQogICAgICAgIGFibGUgdG8gdmFsaWRhdGUgdGhlIHJlY2VpdmVkIEFMVE8gaW5mb3JtYXRp
b24gdG8gZW5zdXJlIHRoYXQgaXQgd2FzCiAgICAgICAgZ2VuZXJhdGVkIGJ5IGFuIGFwcHJvcHJp
YXRlIEFMVE8gc2VydmVyLiIKPC9wPgo8cD5JbiB0aGlzIGNhc2UsIHRoZSBzZWN1cml0eSByZXF1
aXJlbWVudHMgYXJlIHN0cmFpZ2h0Zm9yd2FyZC4gSk9TRQogICAgICAgIG9iamVjdHMgY2Fycnlp
bmcgQUxUTyBwYXlsb2FkcyB3aWxsIG5lZWQgdG8gYmVhciBkaWdpdGFsIHNpZ25hdHVyZXMKICAg
ICAgICBmcm9tIHRoZSBvcmlnaW5hdGluZyBzZXJ2ZXJzLCB3aGljaCB3aWxsIGJlIGJvdW5kIHRv
IGNlcnRpZmljYXRlcwogICAgICAgIGF0dGVzdGluZyB0byB0aGUgaWRlbnRpdGllcyBvZiB0aGUg
c2VydmVycy4gVGhlcmUgaXMgbm8gcmVxdWlyZW1lbnQKICAgICAgICBmb3IgY29uZmlkZW50aWFs
aXR5IGluIHRoaXMgY2FzZSwgc2luY2UgQUxUTyBpbmZvcm1hdGlvbiBpcyBnZW5lcmFsbHkKICAg
ICAgICBwdWJsaWMuCjwvcD4KPHA+VGhlIG1vcmUgaW50ZXJlc3RpbmcgcXVlc3Rpb25zIGFyZSBl
bmNvZGluZyBxdWVzdGlvbnMuIEFMVE8gb2JqZWN0cwogICAgICAgIGFyZSBsaWtlbHkgdG8gYmUg
bXVjaCBsYXJnZXIgdGhhbiBwYXlsb2FkcyBpbiB0aGUgdHdvIGNhc2VzIGFib3ZlLAogICAgICAg
IHdpdGggc2l6ZXMgb2YgdXAgdG8gc2V2ZXJhbCBtZWdhYnl0ZXMuIFByb2Nlc3Npbmcgb2Ygc3Vj
aCBsYXJnZQogICAgICAgIG9iamVjdHMgY2FuIGJlIGRvbmUgbW9yZSBxdWlja2x5IGlmIGl0IGNh
biBiZSBkb25lIGluIGEgc2luZ2xlIHBhc3MsCiAgICAgICAgd2hpY2ggbWF5IGJlIHBvc3NpYmxl
IGlmIEpPU0Ugb2JqZWN0cyByZXF1aXJlIHNwZWNpZmljIG9yZGVyaW5ncyBvZgogICAgICAgIGZp
ZWxkcyB3aXRoaW4gdGhlIEpTT04gc3RydWN0dXJlLgo8L3A+CjxwPkluIGFkZGl0aW9uLCBiZWNh
dXNlIEFMVE8gb2JqZWN0cyBhcmUgYWxzbyBlbmNvZGVkIGFzIEpTT04sIHRoZXkKICAgICAgICBh
cmUgYWxyZWFkeSBzYWZlIGZvciBpbmNsdXNpb24gaW4gYSBKT1NFIG9iamVjdC4gU2lnbmVkIEpP
U0Ugb2JqZWN0cwogICAgICAgIHdpbGwgbGlrZWx5IGNhcnJ5IHRoZSBzaWduZWQgZGF0YSBpbiBh
IHN0cmluZyBhbG9uZ3NpZGUgdGhlIHNpZ25hdHVyZS4KICAgICAgICBKU09OIG9iamVjdHMgaGF2
ZSB0aGUgcHJvcGVydHkgdGhhdCB0aGV5IGNhbiBiZSBzYWZlbHkgZW5jb2RlZCBpbiBKU09OCiAg
ICAgICAgc3RyaW5ncy4gQWxsIHRoZXkgcmVxdWlyZSBpcyB0aGF0IHVubmVjZXNzYXJ5IHdoaXRl
IHNwYWNlIGJlIHJlbW92ZWQsCiAgICAgICAgYSBtdWNoIHNpbXBsZXIgdHJhbnNmb3JtYXRpb24g
dGhhbiwgc2F5IGJhc2U2NHVybCBlbmNvZGluZy4gVGhpcwogICAgICAgIHJhaXNlcyB0aGUgcXVl
c3Rpb24gb2Ygd2hldGhlciBpdCBtaWdodCBiZSBwb3NzaWJsZSB0byBvcHRpbWl6ZSB0aGUKICAg
ICAgICBKT1NFIGVuY29kaW5nIGZvciBjZXJ0YWluICJKU09OLXNhZmUiIGNhc2VzLgo8L3A+Cjxh
IG5hbWU9ImF0b2NhLXNlYyI+PC9hPjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0
IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJy
aWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJz
cDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxhIG5hbWU9InJmYy5zZWN0aW9uLjUuNiI+PC9hPjxo
Mz41LjYuJm5ic3A7CkVtZXJnZW5jeSBBbGVydGluZzwvaDM+Cgo8cD5FbWVyZ2VuY3kgYWxlcnRp
bmcgaXMgYW4gZW1lcmdpbmcgdXNlIGNhc2UgZm9yIElQIG5ldHdvcmtzIDxhIGNsYXNzPSdpbmZv
JyBocmVmPScjSS1ELmlldGYtYXRvY2EtcmVxdWlyZW1lbnRzJz5bSSYjODIwOTtELmlldGYmIzgy
MDk7YXRvY2EmIzgyMDk7cmVxdWlyZW1lbnRzXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNzPSdp
bmZvJz5TY2h1bHpyaW5uZSwgSC4sIE5vcnJleXMsIFMuLCBSb3NlbiwgQi4sIGFuZCBILiBUc2No
b2ZlbmlnLCAmbGRxdW87UmVxdWlyZW1lbnRzLCBUZXJtaW5vbG9neSBhbmQgRnJhbWV3b3JrIGZv
ciBFeGlnZW50IENvbW11bmljYXRpb25zLCZyZHF1bzsgTWFyY2gmbmJzcDsyMDEyLjwvc3Bhbj48
c3Bhbj4pPC9zcGFuPjwvYT4uIEFsZXJ0aW5nIHN5c3RlbXMgYWxsb3cKICAgICAgICBhdXRob3Jp
dGllcyB0byB3YXJuIHVzZXJzIG9mIGltcGVuZGluZyBkYW5nZXIgYnkgc2VuZGluZyBhbGVydAog
ICAgICAgIG1lc3NhZ2VzIHRvIGNvbm5lY3RlZCBkZXZpY2VzLiBGb3IgZXhhbXBsZSwgaW4gdGhl
IGV2ZW50IG9mIGh1cnJpY2FuZQogICAgICAgIG9yIHRvcm5hZG8sIGFsZXJ0cyBtaWdodCBiZSBz
ZW50IHRvIGFsbCBkZXZpY2VzIGluIHRoZSBwYXRoIG9mIHRoZQogICAgICAgIHN0b3JtLgo8L3A+
CjxwPlRoZSBtb3N0IGNyaXRpY2FsIHNlY3VyaXR5IHJlcXVpcmVtZW50IGZvciBhbGVydGluZyBz
eXN0ZW1zIGlzIHRoYXQKICAgICAgICBpdCBtdXN0IG5vdCBiZSBwb3NzaWJsZSBmb3IgYW4gYXR0
YWNrZXIgdG8gc2VuZCBmYWxzZSBhbGVydHMgdG8KICAgICAgICBkZXZpY2VzLiBTdWNoIGEgY2Fw
YWJpbGl0eSB3b3VsZCBwb3RlbnRpYWxseSBhbGxvdyBhbiBhdHRhY2tlciB0bwogICAgICAgIGNy
ZWF0ZSB3aWRlLXNwcmVhZCBwYW5pYy4gSW4gcHJhY3RpY2UsIGFsZXJ0IHN5c3RlbXMgcHJldmVu
dCB0aGVzZQogICAgICAgIGF0dGFja3MgYm90aCBieSBjb250cm9scyBvbiBzZW5kaW5nIG1lc3Nh
Z2VzIGF0IHBvaW50cyB3aGVyZSBhbGVydHMKICAgICAgICBhcmUgb3JpZ2luYXRlZCwgYXMgd2Vs
bCBhcyBieSBoYXZpbmcgcmVjaXBpZW50cyBvZiBhbGVydHMgdmVyaWZ5IHRoYXQKICAgICAgICB0
aGUgYWxlcnQgd2FzIHNlbnQgYnkgYW4gYXV0aG9yaXplZCBzb3VyY2UuIFRoZSBmb3JtZXIgdHlw
ZSBvZiBjb250cm9sCiAgICAgICAgaW1wbGVtZW50ZWQgd2l0aCBsb2NhbCBzZWN1cml0eSBvbiBo
b3N0cyBmcm9tIHdoaWNoIGFsZXJ0cyBjYW4gYmUKICAgICAgICBvcmlnaW5hdGVkLiBUaGUgbGF0
dGVyIHR5cGUgaW1wbGVtZW50ZWQgYnkgZGlnaXRhbCBzaWduYXR1cmVzIG9uIGFsZXJ0CiAgICAg
ICAgbWVzc2FnZXMgKHVzaW5nIGNoYW5uZWwtYmFzZWQgb3Igb2JqZWN0LWJhc2VkIG1lY2hhbmlz
bXMpLgo8L3A+CjxwPkFsZXJ0cyB0eXBpY2FsbHkgcmVhY2ggZW5kIHJlY2lwaWVudHMgdmlhIGEg
c2VyaWVzIG9mCiAgICAgICAgaW50ZXJtZWRpYXJpZXMuIEZvciBleGFtcGxlLCB3aGlsZSBhIG5h
dGlvbmFsIHdlYXRoZXIgc2VydmljZSBtaWdodAogICAgICAgIG9yaWdpbmF0ZSBhIGh1cnJpY2Fu
ZSBhbGVydCwgaXQgbWlnaHQgZmlyc3QgYmUgZGVsaXZlcmVkIHRvIGEgbmF0aW9uYWwKICAgICAg
ICBnYXRld2F5LCBhbmQgdGhlbiB0byBuZXR3b3JrIG9wZXJhdG9ycywgd2hvIGJyb2FkY2FzdCBp
dCB0byBlbmQKICAgICAgICBzdWJzY3JpYmVycy4KPC9wPgo8cD48YnIgLz48aHIgY2xhc3M9Imlu
c2VydCIgLz4KPGEgbmFtZT0iZmlnLWF0b2NhLXNlYyI+PC9hPgo8L3A+CjxkaXYgc3R5bGU9J2Rp
c3BsYXk6IHRhYmxlOyB3aWR0aDogMDsgbWFyZ2luLWxlZnQ6IDNlbTsgbWFyZ2luLXJpZ2h0OiBh
dXRvJz48cHJlPiAgICAgICAgKy0tLS0tLS0tLS0tLSsgICAgKy0tLS0tLS0tLS0tLSsgICAgKy0t
LS0tLS0tLS0tLSsKICAgICAgICB8IE9yaWdpbmF0b3IgfCAgICB8IE9yaWdpbmF0b3IgfCAgICB8
IE9yaWdpbmF0b3IgfAogICAgICAgICstLS0tLS0tLS0tLS0rICAgICstLS0tLS0tLS0tLS0rICAg
ICstLS0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgLiAgICAgICAg
ICAgICAgICAgLgogICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLSsuLi4uLi4uLi4uLi4u
Li4uLi4KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgVgogICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0tKwog
ICAgICAgICAgICAgICAgICAgICAgICAgICB8IEdhdGV3YXkgfAogICAgICAgICAgICAgICAgICAg
ICAgICAgICArLS0tLS0tLS0tKwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwKICAg
ICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tKwogICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICAgICAgICAgICAgICBWICAg
ICAgICAgICAgICAgICAgICAgICAgIFYKICAgICAgICAgICAgICArLS0tLS0tLS0tKyAgICAgICAg
ICAgICAgICstLS0tLS0tLS0rCiAgICAgICAgICAgICAgfCBOZXR3b3JrIHwgICAgICAgICAgICAg
ICB8IE5ldHdvcmsgfAogICAgICAgICAgICAgICstLS0tLS0tLS0rICAgICAgICAgICAgICAgKy0t
LS0tLS0tLSsKICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgfAog
ICAgICAgICAgICArLS0tLS0tKy0tLS0tKyAgICAgICAgICAgICstLS0tLS0rLS0tLS0rCiAgICAg
ICAgICAgIHwgICAgICAgICAgICB8ICAgICAgICAgICAgfCAgICAgICAgICAgIHwKICAgICAgICAg
ICAgViAgICAgICAgICAgIFYgICAgICAgICAgICBWICAgICAgICAgICAgVgogICAgICAgICstLS0t
LS0tLSsgICArLS0tLS0tLS0rICAgKy0tLS0tLS0tKyAgICstLS0tLS0tLSsKICAgICAgICB8IERl
dmljZSB8ICAgfCBEZXZpY2UgfCAgIHwgRGV2aWNlIHwgICB8IERldmljZSB8CiAgICAgICAgKy0t
LS0tLS0tKyAgICstLS0tLS0tLSsgICArLS0tLS0tLS0rICAgKy0tLS0tLS0tKwoKPC9wcmU+PC9k
aXY+PHA+Cjx0YWJsZSBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIg
YWxpZ249ImNlbnRlciI+PHRyPjx0ZCBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJtb25hY28s
IE1TIFNhbnMgU2VyaWYiIHNpemU9IjEiPjxiPiZuYnNwO0ZpZ3VyZSZuYnNwOzQ6IERlbGl2ZXJp
bmcgYW4gZW1lcmdlbmN5IGFsZXJ0Jm5ic3A7PC9iPjwvZm9udD48YnIgLz48L3RkPjwvdHI+PC90
YWJsZT48aHIgY2xhc3M9Imluc2VydCIgLz4KCjwvcD4KPHA+SW4gb3JkZXIgdG8gdmVyaWZ5IGFs
ZXJ0IHNpZ25hdHVyZXMsIHJlY2lwaWVudHMgbXVzdCBiZSBwcm92aXNpb25lZAogICAgICAgIHdp
dGggdGhlIHByb3BlciBwdWJsaWMga2V5cyBmb3IgdHJ1c3RlZCBhbGVydCBhdXRob3JpdGllcy4g
VGhpcyB0cnVzdAogICAgICAgIG1heSBiZSAicGllY2Utd2lzZSIgYWxvbmcgdGhlIHBhdGggdGhl
IGFsZXJ0IHRha2VzLiBGb3IgZXhhbXBsZSwgdGhlCiAgICAgICAgYWxlcnQgcmVsYXlzIG9wZXJh
dGVkIGJ5IG5ldHdvcmtzIG1pZ2h0IGhhdmUgYSBmdWxsIHNldCBvZgogICAgICAgIGNlcnRpZmlj
YXRlcyBmb3IgYWxsIGFsZXJ0IG9yaWdpbmF0b3JzLCB3aGlsZSBlbmQgZGV2aWNlcyBtYXkgb25s
eQogICAgICAgIHRydXN0IHRoZWlyIGxvY2FsIGFsZXJ0IHJlbGF5LiBPciBkZXZpY2VzIG1pZ2h0
IHJlcXVpcmUgdGhhdCBhIGRldmljZQogICAgICAgIGJlIHNpZ25lZCBieSBhbiBhdXRob3JpemVk
IG9yaWdpbmF0b3IgYW5kIGJ5IGl0cyBsb2NhbCBuZXR3b3JrJ3MKICAgICAgICByZWxheS4KPC9w
Pgo8cD5UaGlzIHNjZW5hcmlvIGNyZWF0ZXMgYSBuZWVkIGZvciBtdWx0aXBsZSBzaWduYXR1cmVz
IG9uIGFsZXJ0CiAgICAgICAgZG9jdW1lbnRzLCBzbyB0aGF0IGFuIGFsZXJ0IGNhbiBiZWFyIHNp
Z25hdHVyZXMgZnJvbSBhbnkgb3IgYWxsIG9mIHRoZQogICAgICAgIGVudGl0aWVzIHRoYXQgcHJv
Y2Vzc2VkIGl0IGFsb25nIHRoZSBwYXRoLiBJbiBvcmRlciB0byBtaW5pbWl6ZQogICAgICAgIGNv
bXBsZXhpdHksIHRoZXNlIHNpZ25hdHVyZXMgc2hvdWxkIGJlICJtb2R1bGFyIiwgaW4gdGhlIHNl
bnNlIHRoYXQgYQogICAgICAgIG5ldyBzaWduYXR1cmUgY2FuIGJlIGFkZGVkIHdpdGhvdXQgYSBu
ZWVkIHRvIGFsdGVyIG9yIHJlY29tcHV0ZQogICAgICAgIHByZXZpb3VzIHNpZ25hdHVyZXMuCjwv
cD4KPGEgbmFtZT0id2ViY3J5cHRvLXNlYyI+PC9hPjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFy
eT0ibGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWci
IGFsaWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJz
cDtUT0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxhIG5hbWU9InJmYy5zZWN0aW9uLjUu
NyI+PC9hPjxoMz41LjcuJm5ic3A7CldlYiBDcnlwdG9ncmFwaHk8L2gzPgoKPHA+VGhlIFczQyBX
ZWIgQ3J5cHRvZ3JhcGh5IEFQSSBkZWZpbmVzIGEgc3RhbmRhcmQgY3J5cHRvZ3JhcGhpYyBBUEkg
Zm9yIHRoZQogICAgICBXZWIgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNXZWJDcnlwdG8nPltXZWJD
cnlwdG9dPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9J2luZm8nPlNsZWV2aSwgUi4gYW5kIEQu
IERhaGwsICZsZHF1bztXZWIgQ3J5cHRvZ3JhcGh5IEFQSSwmcmRxdW87IEphbnVhcnkmbmJzcDsy
MDEzLjwvc3Bhbj48c3Bhbj4pPC9zcGFuPjwvYT4uICBJZiBhIGJyb3dzZXIgZXhwb3NlcyB0aGlz
IEFQSSwgdGhlbiAKICAgICAgSmF2YVNjcmlwdCBwcm92aWRlZCBhcyBwYXJ0IG9mIGEgV2ViIHBh
Z2UgY2FuIGFzayB0aGUgYnJvd3NlciB0byBwZXJmb3JtIAogICAgICBjcnlwdG9ncmFwaGljIG9w
ZXJhdGlvbnMsIHN1Y2ggYXMgZGlnZXN0LCBNQUMsIGVuY3J5cHRpb24sIG9yIGRpZ2l0YWwgc2ln
bmluZy4KPC9wPgo8cD5PbmUgb2YgdGhlIGtleSByZWFzb25zIHRvIGhhdmUgdGhlIGJyb3dzZXIg
cGVyZm9ybSBjcnlwdG9ncmFwaGljIG9wZXJhdGlvbnMgIAogICAgICBpcyB0byBhdm9pZCBhbGxv
d2luZyBKYXZhU2NyaXB0IGNvZGUgdG8gYWNjZXNzIHRoZSBrZXlpbmcgbWF0ZXJpYWwgdXNlZCBm
b3IgdGhlc2UKICAgICAgb3BlcmF0aW9ucy4gIEZvciBleGFtcGxlLCB0aGlzIHNlcGFyYXRpb24g
d291bGQgcHJldmVudCBjb2RlIGluamVjdGVkIHRocm91Z2ggYQogICAgICBjcm9zcy1zaXRlIHNj
cmlwdGluZyAoWFNTKSBhdHRhY2sgZnJvbSByZWFkaW5nIGFuZCBleGZpbHRyYXRpbmcga2V5cyBz
dG9yZWQgCiAgICAgIHdpdGhpbiBhIGJyb3dzZXIuICBXaGlsZSB0aGUgbWFsaWNpb3VzIGNvZGUg
Y291bGQgc3RpbGwgdXNlIHRoZSBrZXkgd2hpbGUgcnVubmluZwogICAgICBpbiB0aGUgYnJvd3Nl
ciwgdGhpcyB2dWxuZXJhYmlsaXR5IGNhbiBvbmx5IGJlIGV4ZXJjaXNlZCB3aGlsZSB0aGUgdnVs
bmVyYWJsZQogICAgICBwYWdlIGlzIGFjdGl2ZSBpbiBhIHVzZXIncyBicm93c2VyLgo8L3A+Cjxw
Pkhvd2V2ZXIsIHRoZSBXZWJDcnlwdG9ncmFwaHkgQVBJIGFsc28gcHJvdmlkZXMgYSBrZXkgZXhw
b3J0IGZ1bmN0aW9uYWxpdHksIAogICAgICB3aGljaCBjYW4gYWxsb3cgSmF2YVNjcmlwdCB0byBl
eHRyYWN0IGEga2V5IGZyb20gdGhlIEFQSSBpbiB3cmFwcGVkIGZvcm0uICBGb3IKICAgICAgZXhh
bXBsZSwgdGhlIEphdmFTY3JpcHQgbWlnaHQgcHJvdmlkZSBhIHB1YmxpYyBrZXkgZm9yIHdoaWNo
IHRoZSBjb3JyZXNwb25kaW5nCiAgICAgIHByaXZhdGUga2V5IGlzIGhlbGQgYnkgYW5vdGhlciBk
ZXZpY2UuICBUaGUgd3JhcHBlZCBrZXkgcHJvdmlkZWQgYnkgdGhlIEFQSSAKICAgICAgY291bGQg
dGhlbiBiZSB1c2VkIHRvIHNhZmVseSB0cmFuc3BvcnQgdGhlIGtleSB0byB0aGUgbmV3IGRldmlj
ZS4gIFdoaWxlIHRoaXMKICAgICAgY291bGQgcG90ZW50aWFsbHkgYWxsb3cgbWFsaWNpb3VzIGNv
ZGUgdG8gZXhwb3J0IGEga2V5LCB0aGUgbmVlZCBmb3IgYW4gZXhwbGljaXQKICAgICAgZXhwb3J0
IG9wZXJhdGlvbiBwcm92aWRlcyBhIGNvbnRyb2wgcG9pbnQsIGFsbG93aW5nIGZvciB1c2VyIG5v
dGlmaWNhdGlvbiBvcgogICAgICBjb25zZW50IHZlcmlmaWNhdGlvbi4KPC9wPgo8cD5UaGUgV2Vi
IENyeXB0b2dyYXBoeSBBUEkgYWxzbyBhbGxvd3MgYnJvd3NlcnMgdG8gaW1wb3NlIGxpbWl0YXRp
b25zIG9uIHRoZSAKICAgICAgdXNhZ2Ugb2YgdGhlIGtleXMgaXQgaGFuZGxlcy4gIEZvciBleGFt
cGxlLCBhIHN5bW1ldHJpYyBrZXkgbWlnaHQgYmUgbWFya2VkIGFzIAogICAgICB1c2FibGUgb25s
eSBmb3IgZW5jcnlwdGlvbiwgYW5kIG5vdCBmb3IgTUFDLiAgV2hlbiBhIGtleSBpcyBleHBvcnRl
ZCBpbiB3cmFwcGVkIAogICAgICBmb3JtLCB0aGVzZSBhdHRyaWJ1dGVzIHNob3VsZCBiZSBjYXJy
aWVkIGFsb25nIHdpdGggaXQuCjwvcD4KPHA+VGhlIFdlYiBDcnlwdG9ncmFwaHkgQVBJIHRodXMg
cmVxdWlyZXMgZm9ybWF0cyB0byBleHByZXNzIHNldmVyYWwgZm9ybXMgb2YKICAgICAga2V5cy4g
IE9idmlvdXNseSwgdGhlIHB1YmxpYyBrZXkgZnJvbSBhbiBhc3ltbWV0cmljIGtleSBwYWlyIGNh
biBiZSBmcmVlbHkgCiAgICAgIGltcG9ydGVkIHRvIGFuZCBleHBvcnRlZCBmcm9tIHRoZSBicm93
c2VyLCBzbyB0aGVyZSBuZWVkcyB0byBiZSBhIGZvcm1hdCBmb3IKICAgICAgcHVibGljIGtleXMu
ICBUaGVyZSBpcyBhbHNvIGEgbmVlZCBmb3IgYSBmb3JtYXQgdG8gZXhwcmVzcyBwcml2YXRlIGtl
eXMgYW5kCiAgICAgIHN5bW1ldHJpYyBrZXlzLiAgRm9yIG5vbi1wdWJsaWMga2V5cywgdGhlIHBy
aW1hcnkgbmVlZCBpcyBmb3IgYSB3cmFwcGVkIGZvcm0sCiAgICAgIHdoZXJlIHRoZSBjb25maWRl
bnRpYWxpdHkgYW5kIGludGVncml0eSBvZiB0aGUga2V5IGlzIGFzc3VyZWQgY3J5cHRvZ3JhcGhp
Y2FsbHk7CiAgICAgIHRoZXNlIHByb3RlY3Rpb25zIHNob3VsZCBhbHNvIGFwcGx5IHRvIGFueSBh
dHRyaWJ1dGVzIG9mIHRoZSBrZXkuICBJdCBtYXkgYWxzbwogICAgICBiZSB1c2VmdWwgdG8gZGVm
aW5lIGEgZGlyZWN0LCB1bndyYXBwZWQgZm9ybWF0LCBmb3IgdXNlIHdpdGhpbiBhIHNlY3VyaXR5
IAogICAgICBib3VuZGFyeS4KPC9wPgo8YSBuYW1lPSJhbmNob3IxIj48L2E+PGJyIC8+PGhyIC8+
Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIg
Y2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhy
ZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0i
cmZjLnNlY3Rpb24uNS44Ij48L2E+PGgzPjUuOC4mbmJzcDsKU21hbGwgRGV2aWNlczwvaDM+Cgo8
cD4KICAgICAgQSBzbWFsbCwgbG93IHBvd2VyIGRldmljZSBtYWtlciBoYXMgZGVjaWRlZCBvbiB1
c2luZyB0aGUgb3V0cHV0IG9mIHRoZSBKT1NFIHdvcmtpbmcgZ3JvdXAgYXMgdGhlaXIgZW5jcnlw
dGlvbiBhbmQgYXV0aGVudGljYXRpb24gZnJhbWV3b3JrLgogICAgICBUaGUgZGV2aWNlIG1ha2Vy
IGhhcyBhIGxpbWl0ZWQgYXZhaWxhYmlsaXR5IG9mIGJvdGggcmVhbCBlc3RhdGUgZm9yIGdhdGVz
IGFuZCBwb3dlci4KICAgICAgRm9yIHRoaXMgcmVhc29uIHRoZXJlIGFyZSBhIG51bWJlciBvZiBz
aG9ydCBjdXRzIGFuZCBkZXNpZ24gZGVjaXNpb25zIHRoYXQgaGF2ZSBiZWVuIG1hZGUgaW4gb3Jk
ZXIgdG8gbWluaW1pemUgdGhlc2UgbmVlZHMuCiAgICAKPC9wPgo8cD4KICAgICAgVGhlIGRlc2ln
biB0ZWFtIGhhcyBkZXRlcm1pbmVkIHRoYXQgdGhlIHVzZSBvZiBtZXNzYWdlIGF1dGhlbnRpY2F0
aW9uIGNvZGVzIChNQUMpIGlzIGdvaW5nIHRvIGJlIHN1ZmZpY2llbnQgdG8gcHJvdmlkZSB0aGUg
bmVjZXNzYXJ5IGF1dGhlbnRpY2F0aW9uLiAKICAgICAgSG93ZXZlciwgYWx0aG91Z2ggYSBNQUMg
aXMgZ29pbmcgdG8gYmUgdXNlZCwgdGhleSBkbyBub3Qgd2FudCB0byB1c2UgYSBzaW5nbGUgbG9u
ZyB0ZXJtIHNoYXJlZCBzZWNyZXQuCiAgICAgIEluc3RlYWQgdGhleSBoYXZlIGFkb3B0ZWQgdGhl
IGZvbGxvd2luZyBwcm9wb3NhbCBmb3IgY29tcHV0aW5nIGEgc2hhcmVkIHNlY3JldCB0aGF0IGNh
biBiZSB2YWxpZGF0ZWQ6CiAgICAgIDwvcD4KPHVsIGNsYXNzPSJ0ZXh0Ij4KPGxpPgogICAgICAg
ICAgQW4gRWxsaXB0aWMtQ3VydmUgRGlmZmllLUhlbGxtYW4gKEVDREgpIGtleSBpcyBnZW5lcmF0
ZWQgZm9yIHRoZSBkZXZpY2UgYXQgdGhlIHRpbWUgb2YgbWFudWZhY3R1cmluZy4KICAgICAgICAg
IChPciBhcyBwYXJ0IG9mIHRoZSBjb25maWd1cmF0aW9uIHByb2Nlc3MgZHVyaW5nIGluc3RhbGxh
dGlvbi4pCiAgICAgICAgCjwvbGk+CjxsaT4KICAgICAgICAgIEFuIEVDREggcHVibGljIGtleSBm
b3IgdGhlIGNvbnRyb2xsZXIgaXMgY29uZmlndXJlZCBhdCB0aGUgdGltZSBvZiBjb25maWd1cmF0
aW9uLgogICAgICAgIAo8L2xpPgo8bGk+CiAgICAgICAgICBUaGUgY29uZmlndXJhdGlvbiBzeXN0
ZW0gcGVyZm9ybXMgdGhlIGV4cG9uZW50aWF0aW9uIGFuZCBjb25maWd1cmVzIHRoZSBkZXZpY2Ug
d2l0aCB0aGUgcmVzdWx0aW5nIHNoYXJlZCBzZWNyZXQuCiAgICAgICAgICBUaGlzIHByb2Nlc3Mg
ZWxpbWluYXRlcyB0aGUgbmVlZCBmb3IgdGhlIGRldmljZSB0byBiZSBhYmxlIHRvIHBlcmZvcm0g
dGhlIHJlcXVpcmVkIGV4cG9uZW50aWF0aW9uIHByb2Nlc3NpbmcuCiAgICAgICAgICBUaGUgc2Vj
dXJpdHkgcmVxdWlyZW1lbnRzIG9uIHByb3RlY3RpbmcgdGhpcyBjb21wdXRlZCBzaGFyZWQgc2Vj
cmV0IGFyZSB0aGUgc2FtZSBhcyB0aGUgcmVxdWlyZW1lbnRzIG9uIHByb3RlY3RpbmcgdGhlIHBy
aXZhdGUgRUNESCBrZXkuCiAgICAgICAgCjwvbGk+CjxsaT4KICAgICAgICAgIEEgY291bnRlciBh
bmQgYW4gaW5jcmVtZW50IHZhbHVlIGFyZSBjb25maWd1cmVkIG9udG8gdGhlIGRldmljZS4KICAg
ICAgICAKPC9saT4KPGxpPgogICAgICAgICAgV2hlbiBhIG1lc3NhZ2UgaXMgdG8gYmUgc2VudCBi
eSB0aGUgZGV2aWNlLCB0aGUgY291bnRlciBpcyBpbmNyZW1lbnRlZCBhbmQgYSBuZXcgTUFDIGtl
eSBpcyBjb21wdXRlZCBmcm9tIHRoZSBFQ0RIIHNlY3JldCBhbmQgdGhlIGNvdW50ZXIgdmFsdWUu
CiAgICAgICAgICBBIGN1c3RvbSBLZXkgRGVyaXZhdGlvbiBGdW5jdGlvbiAoS0RGKSBmdW5jdGlv
biBpcyB1c2VkIHdoZW4gaXMgYmFzZWQgb24gdGhlIEFFUy1DQkMgaXMgdXNlZCB0byBkZXJpdmUg
dGhlIHJlcXVpcmVkIE1BQyBrZXkuCiAgICAgICAgICBUaGUgTUFDIGtleSBpcyB0aGVuIHVzZWQg
dG8gY29tcHV0ZSB0aGUgTUFDIHZhbHVlIGZvciB0aGUgbWVzc2FnZS4KICAgICAgICAKPC9saT4K
PC91bD48cD4KIAogICAgICBJbiBhIHNpbWlsYXIgbWFubmVyIHRoZSBLREYgZnVuY3Rpb24gY2Fu
IHVzZWQgdG8gY29tcHV0ZSBhbiBBRUFEIGFsZ29yaXRobSBrZXkgd2hlbiB0aGUgc3lzdGVtIG5l
ZWRzIHRvIHByb3ZpZGUgY29uZmlkZW50aWFsbHkgZm9yIHRoZSBtZXNzYWdlLgogICAgICBUaGUg
Y29udHJvbGxlciwgYmVpbmcgYSBsYXJnZXIgZGV2aWNlIHdpbGwgcGVyZm9ybSB0aGUgZXhwb25l
bnRpYXRpb24gc3RlcCBhbmQgdXNlIGEgcmFuZG9tIG51bWJlciBnZW5lcmF0b3IgdG8gZ2VuZXJh
dGUgdGhlIHNlbmRlciBub25jZSB2YWx1ZS4KICAgIAo8L3A+CjxhIG5hbWU9InJlcS1zZWMiPjwv
YT48YnIgLz48aHIgLz4KPHRhYmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNl
bGxzcGFjaW5nPSIyIiBjbGFzcz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9
IlRPQ2J1ZyI+PGEgaHJlZj0iI3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3Rh
YmxlPgo8YSBuYW1lPSJyZmMuc2VjdGlvbi42Ij48L2E+PGgzPjYuJm5ic3A7ClJlcXVpcmVtZW50
czwvaDM+Cgo8cD5UaGlzIHNlY3Rpb24gc3VtbWFyaXplcyB0aGUgcmVxdWlyZW1lbnRzIGZyb20g
dGhlIGFib3ZlIHVzZXMgY2FzZXMsIGFuZAogICAgICBsaXN0cyBmdXJ0aGVyIHJlcXVpcmVtZW50
cyBub3QgZGlyZWN0bHkgZGVyaXZlZCBmcm9tIHRoZSBhYm92ZSB1c2UgY2FzZXMuCiAgICAgIFRo
ZXJlIGFyZSBhbHNvIHNvbWUgY29uc3RyYWludHMgdGhhdCBhcmUgbm90IGhhcmQgcmVxdWlyZW1l
bnRzLCBidXQgd2hpY2gKICAgICAgYXJlIHN0aWxsIGRlc2lyYWJsZSBwcm9wZXJ0aWVzIGZvciB0
aGUgSk9TRSBzeXN0ZW0gdG8gaGF2ZS4KPC9wPgo8YSBuYW1lPSJmdW5jdGlvbmFsLXNlYyI+PC9h
PjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2Vs
bHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0i
VE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFi
bGU+CjxhIG5hbWU9InJmYy5zZWN0aW9uLjYuMSI+PC9hPjxoMz42LjEuJm5ic3A7CkZ1bmN0aW9u
YWwgUmVxdWlyZW1lbnRzPC9oMz4KCjxwPjwvcD4KPGJsb2NrcXVvdGUgY2xhc3M9InRleHQiPjxk
bD4KPGR0PkYxPC9kdD4KPGRkPkRlZmluZSBmb3JtYXRzIGZvciBzZWN1cmUgb2JqZWN0cyB0aGF0
IHByb3ZpZGUgdGhlIGZvbGxvd2luZwogICAgICAgICAgc2VjdXJpdHkgcHJvcGVydGllczoKICAg
ICAgICAgICAgCjx1bCBjbGFzcz0idGV4dCI+CjxsaT5EaWdpdGFsIHNpZ25hdHVyZSAoaW50ZWdy
aXR5L2F1dGhlbnRpY2F0aW9uIHVuZGVyIGFuIGFzeW1tZXRyaWMga2V5IHBhaXIpCjwvbGk+Cjxs
aT5NZXNzYWdlIGF1dGhlbnRpY2F0aW9uIChpbnRlZ3JpdHkvYXV0aGVudGljYXRpb24gdW5kZXIg
YSBzeW1tZXRyaWMga2V5KQo8L2xpPgo8bGk+RW5jcnlwdGlvbgo8L2xpPgo8bGk+QXV0aGVudGlj
YXRlZCBlbmNyeXB0aW9uCjwvbGk+CjwvdWw+CiAgICAgICAgICBUaGF0IGlzLCB0aGUgc2VjdXJl
IG9iamVjdHMgZGVmaW5lZCBieSB0aGlzIHdvcmtpbmcgZ3JvdXAgc2hvdWxkIHByb3ZpZGUgCiAg
ICAgICAgICBlcXVpdmFsZW50IHNlY3VyaXR5IHByb3BlcnRpZXMgdG8gdGhlIENNUyBTaWduZWRE
YXRhLCBBdXRoZW50aWNhdGVkRGF0YSwgCiAgICAgICAgICBFbnZlbG9wZWREYXRhLCBhbmQgQXV0
aEVudmVsb3BlZCBkYXRhIG9iamVjdHMgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM1NjUyJz5b
UkZDNTY1Ml08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+SG91c2xleSwgUi4sICZs
ZHF1bztDcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChDTVMpLCZyZHF1bzsgU2VwdGVtYmVy
Jm5ic3A7MjAwOS48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+CiAgICAgICAgICA8YSBjbGFzcz0n
aW5mbycgaHJlZj0nI1JGQzUwODMnPltSRkM1MDgzXTxzcGFuPiAoPC9zcGFuPjxzcGFuIGNsYXNz
PSdpbmZvJz5Ib3VzbGV5LCBSLiwgJmxkcXVvO0NyeXB0b2dyYXBoaWMgTWVzc2FnZSBTeW50YXgg
KENNUykgQXV0aGVudGljYXRlZC1FbnZlbG9wZWQtRGF0YSBDb250ZW50IFR5cGUsJnJkcXVvOyBO
b3ZlbWJlciZuYnNwOzIwMDcuPC9zcGFuPjxzcGFuPik8L3NwYW4+PC9hPi4KPC9kZD4KPGR0PkYy
PC9kdD4KPGRkPkRlZmluZSBhIGZvcm1hdCBmb3IgcHVibGljIGtleXMgYW5kIHByaXZhdGUga2V5
cyBmb3IgCiAgICAgICAgICBhc3ltbWV0cmljIGNyeXB0b2dyYXBoaWMgYWxnb3JpdGhtcywgd2l0
aCBhc3NvY2lhdGVkIGF0dHJpYnV0ZXMsIGluY2x1ZGluZyBhCiAgICAgICAgICB3cmFwcGVkIGZv
cm0gZm9yIHByaXZhdGUga2V5cy4KPC9kZD4KPGR0PkYzPC9kdD4KPGRkPkRlZmluZSBhIGZvcm1h
dCBmb3Igc3ltbWV0cmljIGtleXMgd2l0aCBhc3NvY2lhdGVkIGF0dHJpYnV0ZXMsCiAgICAgICAg
ICBhbGxvd2luZyBmb3IgYm90aCB3cmFwcGVkIGFuZCB1bndyYXBwZWQga2V5cy4KPC9kZD4KPGR0
PkY0PC9kdD4KPGRkPkRlZmluZSBKU09OIHNlcmlhbGl6YXRpb25zIGZvciB0aGUgYWJvdmUgb2Jq
ZWN0cy4gIEFuIG9iamVjdAogICAgICAgICAgaW4gdGhpcyBlbmNvZGluZyBtdXN0IGJlIHZhbGlk
IGFjY29yZGluZyB0byB0aGUgSlNPTiBBQk5GIHN5bnRheCAKICAgICAgICAgIDxhIGNsYXNzPSdp
bmZvJyBocmVmPScjUkZDNDYyNyc+W1JGQzQ2MjddPHNwYW4+ICg8L3NwYW4+PHNwYW4gY2xhc3M9
J2luZm8nPkNyb2NrZm9yZCwgRC4sICZsZHF1bztUaGUgYXBwbGljYXRpb24vanNvbiBNZWRpYSBU
eXBlIGZvciBKYXZhU2NyaXB0IE9iamVjdCBOb3RhdGlvbiAoSlNPTiksJnJkcXVvOyBKdWx5Jm5i
c3A7MjAwNi48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+CjwvZGQ+CjxkdD5GNTwvZHQ+CjxkZD5E
ZWZpbmUgY29tcGFjdCwgVVJMLXNhZmUgdGV4dCBzZXJpYWxpemF0aW9ucyBmb3IgdGhlIGFib3Zl
IAogICAgICAgICAgb2JqZWN0cy4KPC9kZD4KPGR0PkY2PC9kdD4KPGRkPkFsbG93IGZvciBhdHRy
aWJ1dGVzIGFzc29jaWF0ZWQgdG8gd3JhcHBlZCBrZXlzIHRvIGJlIGJvdW5kIAogICAgICAgICAg
dG8gdGhlbSBjcnlwdG9ncmFwaGljYWxseQo8L2RkPgo8ZHQ+Rjc8L2R0Pgo8ZGQ+QWxsb3cgZm9y
IHdyYXBwZWQga2V5cyB0byBiZSBzZXBhcmF0ZWQgZnJvbSBhIHNlY3VyZSBvYmplY3QgCiAgICAg
ICAgICB0aGF0IHVzZXMgYSBzeW1tZXRyaWMga2V5LiAgSW4gc3VjaCBjYXNlcywgY3J5cHRvZ3Jh
cGhpYyBjb21wb25lbnRzIG9mIHRoZSAKICAgICAgICAgIHNlY3VyZSBvYmplY3Qgb3RoZXIgdGhh
biB0aGUgd3JhcHBlZCBrZXkgKGUuZy4sIGNpcGhlcnRleHQsIE1BQyB2YWx1ZXMpIG11c3QKICAg
ICAgICAgIGJlIGluZGVwZW5kZW50IG9mIHRoZSB3cmFwcGVkIGZvcm0gb2YgdGhlIGtleS4gIEZv
ciBleGFtcGxlLCBpZiBhbiBlbmNyeXB0ZWQKICAgICAgICAgIG9iamVjdCBpcyBwcmVwYXJlZCBm
b3IgbXVsdGlwbGUgcmVjaXBpZW50cywgdGhlbiBvbmx5IHRoZSB3cmFwcGVkIGtleSBtYXkgdmFy
eSwKICAgICAgICAgIG5vdCB0aGUgY2lwaGVydGV4dC4KPC9kZD4KPC9kbD48L2Jsb2NrcXVvdGU+
Cgo8YSBuYW1lPSJzZWMtcmVxLXNlYyI+PC9hPjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFyeT0i
bGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWciIGFs
aWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJzcDtU
T0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxhIG5hbWU9InJmYy5zZWN0aW9uLjYuMiI+
PC9hPjxoMz42LjIuJm5ic3A7ClNlY3VyaXR5IFJlcXVpcmVtZW50czwvaDM+Cgo8cD48L3A+Cjxi
bG9ja3F1b3RlIGNsYXNzPSJ0ZXh0Ij48ZGw+CjxkdD5TMTwvZHQ+CjxkZD5Qcm92aWRlIGtleSBt
YW5hZ2VtZW50IGZ1bmN0aW9ucyBmb3IgZXBoZW1lcmFsIHN5bW1ldHJpYyBrZXlzLAogICAgICAg
IGluY2x1ZGluZyBlbmNyeXB0aW9uIGtleXMgYW5kIE1BQyBrZXlzLiAgSXQgc2hvdWxkIGJlIHBv
c3NpYmxlIHRvIHVzZSBhbnkKICAgICAgICBvZiB0aGUga2V5IG1hbmFnZW1lbnQgdGVjaG5pcXVl
cyBwcm92aWRlZCBpbiBDTVMgPGEgY2xhc3M9J2luZm8nIGhyZWY9JyNSRkM1NjUyJz5bUkZDNTY1
Ml08c3Bhbj4gKDwvc3Bhbj48c3BhbiBjbGFzcz0naW5mbyc+SG91c2xleSwgUi4sICZsZHF1bztD
cnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChDTVMpLCZyZHF1bzsgU2VwdGVtYmVyJm5ic3A7
MjAwOS48L3NwYW4+PHNwYW4+KTwvc3Bhbj48L2E+OgogICAgICAgICAgCjx1bCBjbGFzcz0idGV4
dCI+CjxsaT5LZXkgdHJhbnNwb3J0ICh3cmFwcGluZyBmb3IgYSBwdWJsaWMga2V5KQo8L2xpPgo8
bGk+S2V5IGVuY2lwaGVybWVudCAod3JhcHBpbmcgZm9yIGEgc3ltbWV0cmljIGtleSkKPC9saT4K
PGxpPktleSBhZ3JlZW1lbnQgKHdyYXBwaW5nIGZvciBhIERIIHB1YmxpYyBrZXkpCjwvbGk+Cjxs
aT5QYXNzd29yZC1iYXNlZCBlbmNyeXB0aW9uICh3cmFwcGluZyB1bmRlciBhIGtleSBkZXJpdmVk
IGZyb20gYSBwYXNzd29yZCkKPC9saT4KPC91bD4KICAgICAgICAKPC9kZD4KPGR0PlMyPC9kdD4K
PGRkPlVzZSBjcnlwdG9ncmFwaGljIGFsZ29yaXRobXMgaW4gYSBtYW5uZXIgY29tcGF0aWJsZSB3
aXRoCiAgICAgICAgbWFqb3IgdmFsaWRhdGlvbiBwcm9jZXNzZXMuICBGb3IgZXhhbXBsZSwgaWYg
YSBGSVBTIHN0YW5kYXJkIGFsbG93cyAKICAgICAgICBhbGdvcml0aG0gQSB0byBiZSB1c2VkIGZv
ciBwdXJwb3NlIFggYnV0IG5vdCBwdXJwb3NlIFksIHRoZW4gSk9TRSBzaG91bGQKICAgICAgICBu
b3QgcmVjb21tZW5kIHVzaW5nIGFsZ29yaXRobSBBIGZvciBwdXJwb3NlIFkuCjwvZGQ+CjxkdD5T
MzwvZHQ+CjxkZD5TdXBwb3J0IG9wZXJhdGlvbiB3aXRoIG9yIHdpdGhvdXQgcHJlLW5lZ290aWF0
aW9uLiAgCiAgICAgICAgSXQgbXVzdCBiZSBwb3NzaWJsZSB0byBjcmVhdGUgb3IgcHJvY2VzcyBz
ZWN1cmUgb2JqZWN0cyB3aXRob3V0CiAgICAgICAgYW55IGNvbmZpZ3VyYXRpb24gYmV5b25kIGtl
eSBwcm92aXNpb25pbmcuICBJZiBpdCBpcyBwb3NzaWJsZSBmb3Iga2V5cwogICAgICAgIHRvIGJl
IGRlcml2ZWQgZnJvbSBhcHBsaWNhdGlvbiBjb250ZXh0LCBpdCBtdXN0IGJlIHBvc3NpYmxlIGZv
ciBhIHJlY2lwaWVudAogICAgICAgIHRvIHJlY29nbml6ZSB3aGVuIGl0IGRvZXMgbm90IGhhdmUg
dGhlIGFwcHJvcHJpYXRlIGtleSBpbiB0aGUgY2FzZSB0aGF0IHRoZSBhcHBsaWNhdGlvbiBkb2Vz
IG5vdAoJc3BlY2lmeSB0aGUgdXNlIG9mIGFub3RoZXIgbWVhbnMgb3IgY29udmVudGlvbiB0byBk
ZXRlcm1pbmUgdGhlIGtleSB1c2VkLgo8L2RkPgo8L2RsPjwvYmxvY2txdW90ZT4KCjxhIG5hbWU9
ImRlc2lkZXJhdGEtc2VjIj48L2E+PGJyIC8+PGhyIC8+Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQi
IGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJp
Z2h0Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhyZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNw
OzwvYT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0icmZjLnNlY3Rpb24uNi4zIj48L2E+PGgz
PjYuMy4mbmJzcDsKRGVzaWRlcmF0YTwvaDM+Cgo8cD48L3A+CjxibG9ja3F1b3RlIGNsYXNzPSJ0
ZXh0Ij48ZGw+CjxkdD5EMTwvZHQ+CjxkZD5NYXhpbWl6ZSBjb21wYXRpYmlsaXR5IHdpdGggdGhl
IFczQyBXZWJDcnlwdG8gCiAgICAgICAgICBzcGVjaWZpY2F0aW9ucywgZS5nLiwgYnkgY29vcmRp
bmF0aW5nIHdpdGggdGhlIFdlYkNyeXB0byB3b3JraW5nIGdyb3VwCiAgICAgICAgICB0byBlbmNv
dXJhZ2UgYWxpZ25tZW50IG9mIGFsZ29yaXRobXMgYW5kIGFsZ29yaXRobSBpZGVudGlmaWVycwoJ
ICB0byB0aGUgZXh0ZW50IHRoYXQgaXQgbWFrZXMgc2Vuc2UgaW4gdGhlIHNvbWV3aGF0IGRpZmZl
cmVudCBXZWJDcnlwdG8gYW5kIEpPU0UgYXBwbGljYXRpb24gY29udGV4dHMuCjwvZGQ+CjxkdD5E
MjwvZHQ+CjxkZD5Bdm9pZCBKU09OIGNhbm9uaWNhbGl6YXRpb24gdG8gdGhlIGV4dGVudCBwb3Nz
aWJsZS4KCSAgVGhhdCBpcywgYWxsIG90aGVyIHRoaW5ncyBiZWluZyBlcXVhbCwgdGVjaG5pcXVl
cyB0aGF0IHJlbHkgCiAgICAgICAgICBvbiBmaXhpbmcgYSBzZXJpYWxpemF0aW9uIG9mIGFuIG9i
amVjdCAoZS5nLiwgYnkgYmFzZTY0dXJsIGVuY29kaW5nIGl0KSAKICAgICAgICAgIGFyZSBwcmVm
ZXJyZWQgb3ZlciB0aG9zZSB0aGF0IHJlcXVpcmUgY29udmVydGluZyBhbiBvYmplY3QgdG8gYSAK
ICAgICAgICAgIGNhbm9uaWNhbCBmb3JtLgo8L2RkPgo8L2RsPjwvYmxvY2txdW90ZT4KCjxhIG5h
bWU9ImlhbmEtc2VjIj48L2E+PGJyIC8+PGhyIC8+Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNl
bGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0
Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhyZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwv
YT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0icmZjLnNlY3Rpb24uNyI+PC9hPjxoMz43LiZu
YnNwOwpJQU5BIENvbnNpZGVyYXRpb25zPC9oMz4KCjxwPlRoaXMgZG9jdW1lbnQgbWFrZXMgbm8g
cmVxdWVzdCBvZiBJQU5BLgo8L3A+CjxhIG5hbWU9InNlYy1jb25zLXNlYyI+PC9hPjxiciAvPjxo
ciAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9
IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJyaWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48
YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJzcDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxhIG5h
bWU9InJmYy5zZWN0aW9uLjgiPjwvYT48aDM+OC4mbmJzcDsKU2VjdXJpdHkgQ29uc2lkZXJhdGlv
bnM8L2gzPgoKPHA+VGhlIHByaW1hcnkgZm9jdXMgb2YgdGhpcyBkb2N1bWVudCBpcyB0aGUgcmVx
dWlyZW1lbnRzIGZvciBhCiAgICAgIEpTT04tYmFzZWQgc2VjdXJlIG9iamVjdCBmb3JtYXQuIEF0
IHRoZSBsZXZlbCBvZiBnZW5lcmFsIHNlY3VyaXR5CiAgICAgIGNvbnNpZGVyYXRpb25zIGZvciBv
YmplY3QtYmFzZWQgc2VjdXJpdHkgdGVjaG5vbG9naWVzLCB0aGUgc2VjdXJpdHkKICAgICAgY29u
c2lkZXJhdGlvbnMgZm9yIHRoaXMgZm9ybWF0IGFyZSB0aGUgc2FtZSBhcyBmb3IgQ01TIDxhIGNs
YXNzPSdpbmZvJyBocmVmPScjUkZDNTY1Mic+W1JGQzU2NTJdPHNwYW4+ICg8L3NwYW4+PHNwYW4g
Y2xhc3M9J2luZm8nPkhvdXNsZXksIFIuLCAmbGRxdW87Q3J5cHRvZ3JhcGhpYyBNZXNzYWdlIFN5
bnRheCAoQ01TKSwmcmRxdW87IFNlcHRlbWJlciZuYnNwOzIwMDkuPC9zcGFuPjxzcGFuPik8L3Nw
YW4+PC9hPi4gVGhlIHByaW1hcnkgZGlmZmVyZW5jZSBiZXR3ZWVuIHRoZSBKT1NFIGZvcm1hdCBh
bmQKICAgICAgQ01TIGlzIHRoYXQgSk9TRSBpcyBiYXNlZCBvbiBKU09OLCB3aGljaCBkb2VzIG5v
dCBoYXZlIGEgY2Fub25pY2FsCiAgICAgIHJlcHJlc2VudGF0aW9uLiBUaGUgbGFjayBvZiBhIGNh
bm9uaWNhbCBmb3JtIG1lYW5zIHRoYXQgaXQgaXMgZGlmZmljdWx0CiAgICAgIHRvIGRldGVybWlu
ZSB3aGV0aGVyIHR3byBKU09OIG9iamVjdHMgcmVwcmVzZW50IHRoZSBzYW1lIGluZm9ybWF0aW9u
LAogICAgICB3aGljaCBjb3VsZCBsZWFkIHRvIHZ1bG5lcmFiaWxpdGllcyBpbiBzb21lIHVzYWdl
cyBvZiBKT1NFLgo8L3A+CjxhIG5hbWU9InJmYy5yZWZlcmVuY2VzIj48L2E+PGJyIC8+PGhyIC8+
Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIg
Y2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhy
ZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0i
cmZjLnNlY3Rpb24uOSI+PC9hPjxoMz45LiZuYnNwOwpSZWZlcmVuY2VzPC9oMz4KCjxhIG5hbWU9
InJmYy5yZWZlcmVuY2VzMSI+PC9hPjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0
IiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJy
aWdodCI+PHRyPjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJz
cDs8L2E+PC90ZD48L3RyPjwvdGFibGU+CjxoMz45LjEuJm5ic3A7Tm9ybWF0aXZlIFJlZmVyZW5j
ZXM8L2gzPgo8dGFibGUgd2lkdGg9Ijk5JSIgYm9yZGVyPSIwIj4KPHRyPjx0ZCBjbGFzcz0iYXV0
aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkM0NjI3Ij5bUkZDNDYyN108L2E+PC90
ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+Q3JvY2tmb3JkLCBELiwgJmxkcXVvOzxhIGhyZWY9
Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ2MjciPlRoZSBhcHBsaWNhdGlvbi9qc29u
IE1lZGlhIFR5cGUgZm9yIEphdmFTY3JpcHQgT2JqZWN0IE5vdGF0aW9uIChKU09OKTwvYT4sJnJk
cXVvOyBSRkMmbmJzcDs0NjI3LCBKdWx5Jm5ic3A7MjAwNiAoPGEgaHJlZj0iaHR0cDovL3d3dy5y
ZmMtZWRpdG9yLm9yZy9yZmMvcmZjNDYyNy50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0
ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkM0NjQ4Ij5bUkZD
NDY0OF08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+Sm9zZWZzc29uLCBTLiwgJmxk
cXVvOzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ2NDgiPlRoZSBCYXNl
MTYsIEJhc2UzMiwgYW5kIEJhc2U2NCBEYXRhIEVuY29kaW5nczwvYT4sJnJkcXVvOyBSRkMmbmJz
cDs0NjQ4LCBPY3RvYmVyJm5ic3A7MjAwNiAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9yZmMvcmZjNDY0OC50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0i
YXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkM0OTQ5Ij5bUkZDNDk0OV08L2E+
PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+U2hpcmV5LCBSLiwgJmxkcXVvOzxhIGhyZWY9
Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ5NDkiPkludGVybmV0IFNlY3VyaXR5IEds
b3NzYXJ5LCBWZXJzaW9uIDI8L2E+LCZyZHF1bzsgUkZDJm5ic3A7NDk0OSwgQXVndXN0Jm5ic3A7
MjAwNyAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9yZmMvcmZjNDk0OS50eHQi
PlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGlnbj0i
dG9wIj48YSBuYW1lPSJSRkM1MDgzIj5bUkZDNTA4M108L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRo
b3ItdGV4dCI+SG91c2xleSwgUi4sICZsZHF1bzs8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9yZmM1MDgzIj5DcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChDTVMpIEF1dGhl
bnRpY2F0ZWQtRW52ZWxvcGVkLURhdGEgQ29udGVudCBUeXBlPC9hPiwmcmRxdW87IFJGQyZuYnNw
OzUwODMsIE5vdmVtYmVyJm5ic3A7MjAwNyAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9yZmMvcmZjNTA4My50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0i
YXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkM1NjUyIj5bUkZDNTY1Ml08L2E+
PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+SG91c2xleSwgUi4sICZsZHF1bzs8YSBocmVm
PSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1NjUyIj5DcnlwdG9ncmFwaGljIE1lc3Nh
Z2UgU3ludGF4IChDTVMpPC9hPiwmcmRxdW87IFNURCZuYnNwOzcwLCBSRkMmbmJzcDs1NjUyLCBT
ZXB0ZW1iZXImbmJzcDsyMDA5ICg8YSBocmVmPSJodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3Jm
Yy9yZmM1NjUyLnR4dCI+VFhUPC9hPikuPC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3It
dGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IlJGQzYxMjAiPltSRkM2MTIwXTwvYT48L3RkPgo8
dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5TYWludC1BbmRyZSwgUC4sICZsZHF1bzs8YSBocmVmPSJo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2MTIwIj5FeHRlbnNpYmxlIE1lc3NhZ2luZyBh
bmQgUHJlc2VuY2UgUHJvdG9jb2wgKFhNUFApOiBDb3JlPC9hPiwmcmRxdW87IFJGQyZuYnNwOzYx
MjAsIE1hcmNoJm5ic3A7MjAxMSAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9y
ZmMvcmZjNjEyMC50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9y
LXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkM2NzA4Ij5bUkZDNjcwOF08L2E+PC90ZD4K
PHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+S2llc2VsLCBTLiwgUHJldmlkaSwgUy4sIFN0aWVtZXJs
aW5nLCBNLiwgV291bmR5LCBSLiwgYW5kIFkuIFlhbmcsICZsZHF1bzs8YSBocmVmPSJodHRwOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM2NzA4Ij5BcHBsaWNhdGlvbi1MYXllciBUcmFmZmljIE9w
dGltaXphdGlvbiAoQUxUTykgUmVxdWlyZW1lbnRzPC9hPiwmcmRxdW87IFJGQyZuYnNwOzY3MDgs
IFNlcHRlbWJlciZuYnNwOzIwMTIgKDxhIGhyZWY9Imh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcv
cmZjL3JmYzY3MDgudHh0Ij5UWFQ8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhv
ci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iUkZDNjc0OSI+W1JGQzY3NDldPC9hPjwvdGQ+
Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPkhhcmR0LCBELiwgJmxkcXVvOzxhIGhyZWY9Imh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzY3NDkiPlRoZSBPQXV0aCAyLjAgQXV0aG9yaXphdGlv
biBGcmFtZXdvcms8L2E+LCZyZHF1bzsgUkZDJm5ic3A7Njc0OSwgT2N0b2JlciZuYnNwOzIwMTIg
KDxhIGhyZWY9Imh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvcmZjL3JmYzY3NDkudHh0Ij5UWFQ8
L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2YWxpZ249InRvcCI+
PGEgbmFtZT0iUkZDNjc1MCI+W1JGQzY3NTBdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRl
eHQiPkpvbmVzLCBNLiBhbmQgRC4gSGFyZHQsICZsZHF1bzs8YSBocmVmPSJodHRwOi8vdG9vbHMu
aWV0Zi5vcmcvaHRtbC9yZmM2NzUwIj5UaGUgT0F1dGggMi4wIEF1dGhvcml6YXRpb24gRnJhbWV3
b3JrOiBCZWFyZXIgVG9rZW4gVXNhZ2U8L2E+LCZyZHF1bzsgUkZDJm5ic3A7Njc1MCwgT2N0b2Jl
ciZuYnNwOzIwMTIgKDxhIGhyZWY9Imh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvcmZjL3JmYzY3
NTAudHh0Ij5UWFQ8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2
YWxpZ249InRvcCI+PGEgbmFtZT0iVzNDLkNSLXhtbGRzaWctY29yZTItMjAxMjAxMjQiPltXM0Mu
Q1IteG1sZHNpZy1jb3JlMi0yMDEyMDEyNF08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4
dCI+RWFzdGxha2UsIEQuLCBSZWFnbGUsIEouLCBZaXUsIEsuLCBTb2xvLCBELiwgRGF0dGEsIFAu
LCBIaXJzY2gsIEYuLCBDYW50b3IsIFMuLCBhbmQgVC4gUm9lc3NsZXIsICZsZHF1bzs8YSBocmVm
PSJodHRwOi8vd3d3LnczLm9yZy9UUi8yMDEyL0NSLXhtbGRzaWctY29yZTItMjAxMjAxMjQiPlhN
TCBTaWduYXR1cmUgU3ludGF4IGFuZCBQcm9jZXNzaW5nIFZlcnNpb24gMi4wPC9hPiwmcmRxdW87
IFdvcmxkIFdpZGUgV2ViIENvbnNvcnRpdW0gQ1ImbmJzcDtDUi14bWxkc2lnLWNvcmUyLTIwMTIw
MTI0LCBKYW51YXJ5Jm5ic3A7MjAxMiAoPGEgaHJlZj0iaHR0cDovL3d3dy53My5vcmcvVFIvMjAx
Mi9DUi14bWxkc2lnLWNvcmUyLTIwMTIwMTI0Ij5IVE1MPC9hPikuPC90ZD48L3RyPgo8dHI+PHRk
IGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IlczQy5DUi14bWxlbmMt
Y29yZTEtMjAxMjAzMTMiPltXM0MuQ1IteG1sZW5jLWNvcmUxLTIwMTIwMzEzXTwvYT48L3RkPgo8
dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5FYXN0bGFrZSwgRC4sIFJlYWdsZSwgSi4sIFJvZXNzbGVy
LCBULiwgYW5kIEYuIEhpcnNjaCwgJmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly93d3cudzMub3JnL1RS
LzIwMTIvQ1IteG1sZW5jLWNvcmUxLTIwMTIwMzEzIj5YTUwgRW5jcnlwdGlvbiBTeW50YXggYW5k
IFByb2Nlc3NpbmcgVmVyc2lvbiAxLjE8L2E+LCZyZHF1bzsgV29ybGQgV2lkZSBXZWIgQ29uc29y
dGl1bSBDUiZuYnNwO0NSLXhtbGVuYy1jb3JlMS0yMDEyMDMxMywgTWFyY2gmbmJzcDsyMDEyICg8
YSBocmVmPSJodHRwOi8vd3d3LnczLm9yZy9UUi8yMDEyL0NSLXhtbGVuYy1jb3JlMS0yMDEyMDMx
MyI+SFRNTDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGln
bj0idG9wIj48YSBuYW1lPSJXM0MuUkVDLXhtbC0xOTk4Ij5bVzNDLlJFQy14bWwtMTk5OF08L2E+
PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+QnJheSwgVC4sIFBhb2xpLCBKLiwgYW5kIEMu
IFNwZXJiZXJnLU1jUXVlZW4sICZsZHF1bzs8YSBocmVmPSJodHRwOi8vd3d3LnczLm9yZy9UUi8x
OTk4L1JFQy14bWwtMTk5ODAyMTAvIj5FeHRlbnNpYmxlIE1hcmt1cCBMYW5ndWFnZSAoWE1MKSAx
LjA8L2E+LCZyZHF1bzsgVzNDJm5ic3A7UkVDLXhtbC0xOTk4LCBGZWJydWFyeSZuYnNwOzE5OTgu
PC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5h
bWU9IldlYkNyeXB0byI+W1dlYkNyeXB0b108L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4
dCI+U2xlZXZpLCBSLiBhbmQgRC4gRGFobCwgJmxkcXVvO1dlYiBDcnlwdG9ncmFwaHkgQVBJLCZy
ZHF1bzsgSmFudWFyeSZuYnNwOzIwMTMuPC90ZD48L3RyPgo8L3RhYmxlPgoKPGEgbmFtZT0icmZj
LnJlZmVyZW5jZXMyIj48L2E+PGJyIC8+PGhyIC8+Cjx0YWJsZSBzdW1tYXJ5PSJsYXlvdXQiIGNl
bGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9IlRPQ2J1ZyIgYWxpZ249InJpZ2h0
Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhyZWY9IiN0b2MiPiZuYnNwO1RPQyZuYnNwOzwv
YT48L3RkPjwvdHI+PC90YWJsZT4KPGgzPjkuMi4mbmJzcDtJbmZvcm1hdGl2ZSBSZWZlcmVuY2Vz
PC9oMz4KPHRhYmxlIHdpZHRoPSI5OSUiIGJvcmRlcj0iMCI+Cjx0cj48dGQgY2xhc3M9ImF1dGhv
ci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iQ0FQIj5bQ0FQXTwvYT48L3RkPgo8dGQgY2xh
c3M9ImF1dGhvci10ZXh0Ij5Cb3R0ZXJlbGwsIEEuIGFuZCBFLiBKb25lcywgJmxkcXVvO0NvbW1v
biBBbGVydGluZyBQcm90b2NvbCB2MS4xLCZyZHF1bzsgT2N0b2JlciZuYnNwOzIwMDUuPC90ZD48
L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9Ikkt
RC5pZXRmLWFsdG8tcHJvdG9jb2wiPltJLUQuaWV0Zi1hbHRvLXByb3RvY29sXTwvYT48L3RkPgo8
dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5BbGltaSwgUi4sIFBlbm5vLCBSLiwgYW5kIFkuIFlhbmcs
ICZsZHF1bzs8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWFs
dG8tcHJvdG9jb2wtMTYiPkFMVE8gUHJvdG9jb2w8L2E+LCZyZHF1bzsgZHJhZnQtaWV0Zi1hbHRv
LXByb3RvY29sLTE2ICh3b3JrIGluIHByb2dyZXNzKSwgTWF5Jm5ic3A7MjAxMyAoPGEgaHJlZj0i
aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1hbHRvLXByb3Rv
Y29sLTE2LnR4dCI+VFhUPC9hPikuPC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4
dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IkktRC5pZXRmLWF0b2NhLXJlcXVpcmVtZW50cyI+W0kt
RC5pZXRmLWF0b2NhLXJlcXVpcmVtZW50c108L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4
dCI+U2NodWx6cmlubmUsIEguLCBOb3JyZXlzLCBTLiwgUm9zZW4sIEIuLCBhbmQgSC4gVHNjaG9m
ZW5pZywgJmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtYXRvY2EtcmVxdWlyZW1lbnRzLTAzIj5SZXF1aXJlbWVudHMsIFRlcm1pbm9sb2d5IGFuZCBG
cmFtZXdvcmsgZm9yIEV4aWdlbnQgQ29tbXVuaWNhdGlvbnM8L2E+LCZyZHF1bzsgZHJhZnQtaWV0
Zi1hdG9jYS1yZXF1aXJlbWVudHMtMDMgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJjaCZuYnNwOzIw
MTIgKDxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWll
dGYtYXRvY2EtcmVxdWlyZW1lbnRzLTAzLnR4dCI+VFhUPC9hPikuPC90ZD48L3RyPgo8dHI+PHRk
IGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IkktRC5pZXRmLWpvc2Ut
anNvbi13ZWItYWxnb3JpdGhtcyI+W0ktRC5pZXRmLWpvc2UtanNvbi13ZWItYWxnb3JpdGhtc108
L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+Sm9uZXMsIE0uLCAmbGRxdW87PGEgaHJl
Zj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLWFs
Z29yaXRobXMtMTEiPkpTT04gV2ViIEFsZ29yaXRobXMgKEpXQSk8L2E+LCZyZHF1bzsgZHJhZnQt
aWV0Zi1qb3NlLWpzb24td2ViLWFsZ29yaXRobXMtMTEgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXkm
bmJzcDsyMDEzICg8YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1pZXRmLWpvc2UtanNvbi13ZWItYWxnb3JpdGhtcy0xMS50eHQiPlRYVDwvYT4sIDxhIGhy
ZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtam9zZS1q
c29uLXdlYi1hbGdvcml0aG1zLTExLnBkZiI+UERGPC9hPikuPC90ZD48L3RyPgo8dHI+PHRkIGNs
YXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IkktRC5pZXRmLWpvc2UtanNv
bi13ZWItZW5jcnlwdGlvbiI+W0ktRC5pZXRmLWpvc2UtanNvbi13ZWItZW5jcnlwdGlvbl08L2E+
PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+Sm9uZXMsIE0uLCBSZXNjb3JsYSwgRS4sIGFu
ZCBKLiBIaWxkZWJyYW5kLCAmbGRxdW87PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLWVuY3J5cHRpb24tMTEiPkpTT04gV2ViIEVuY3J5
cHRpb24gKEpXRSk8L2E+LCZyZHF1bzsgZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLWVuY3J5cHRp
b24tMTEgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXkmbmJzcDsyMDEzICg8YSBocmVmPSJodHRwOi8v
d3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItZW5j
cnlwdGlvbi0xMS50eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1lbmNyeXB0aW9uLTExLnBkZiI+
UERGPC9hPikuPC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0
b3AiPjxhIG5hbWU9IkktRC5pZXRmLWpvc2UtanNvbi13ZWIta2V5Ij5bSS1ELmlldGYtam9zZS1q
c29uLXdlYi1rZXldPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPkpvbmVzLCBNLiwg
JmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtam9z
ZS1qc29uLXdlYi1rZXktMTEiPkpTT04gV2ViIEtleSAoSldLKTwvYT4sJnJkcXVvOyBkcmFmdC1p
ZXRmLWpvc2UtanNvbi13ZWIta2V5LTExICh3b3JrIGluIHByb2dyZXNzKSwgTWF5Jm5ic3A7MjAx
MyAoPGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0
Zi1qb3NlLWpzb24td2ViLWtleS0xMS50eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0dHA6Ly93d3cu
aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1rZXktMTEu
cGRmIj5QREY8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2YWxp
Z249InRvcCI+PGEgbmFtZT0iSS1ELmlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmUiPltJLUQu
aWV0Zi1qb3NlLWpzb24td2ViLXNpZ25hdHVyZV08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3It
dGV4dCI+Sm9uZXMsIE0uLCBCcmFkbGV5LCBKLiwgYW5kIE4uIFNha2ltdXJhLCAmbGRxdW87PGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1qb3NlLWpzb24td2Vi
LXNpZ25hdHVyZS0xMSI+SlNPTiBXZWIgU2lnbmF0dXJlIChKV1MpPC9hPiwmcmRxdW87IGRyYWZ0
LWlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmUtMTEgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXkm
bmJzcDsyMDEzICg8YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k
cmFmdC1pZXRmLWpvc2UtanNvbi13ZWItc2lnbmF0dXJlLTExLnR4dCI+VFhUPC9hPiwgPGEgaHJl
Zj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1qb3NlLWpz
b24td2ViLXNpZ25hdHVyZS0xMS5wZGYiPlBERjwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFz
cz0iYXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJJLUQuaWV0Zi1vYXV0aC1qc29u
LXdlYi10b2tlbiI+W0ktRC5pZXRmLW9hdXRoLWpzb24td2ViLXRva2VuXTwvYT48L3RkPgo8dGQg
Y2xhc3M9ImF1dGhvci10ZXh0Ij5Kb25lcywgTS4sIEJyYWRsZXksIEouLCBhbmQgTi4gU2FraW11
cmEsICZsZHF1bzs8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LW9hdXRoLWpzb24td2ViLXRva2VuLTA4Ij5KU09OIFdlYiBUb2tlbiAoSldUKTwvYT4sJnJkcXVv
OyBkcmFmdC1pZXRmLW9hdXRoLWpzb24td2ViLXRva2VuLTA4ICh3b3JrIGluIHByb2dyZXNzKSwg
TWF5Jm5ic3A7MjAxMyAoPGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtaWV0Zi1vYXV0aC1qc29uLXdlYi10b2tlbi0wOC50eHQiPlRYVDwvYT4sIDxhIGhy
ZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtb2F1dGgt
anNvbi13ZWItdG9rZW4tMDgucGRmIj5QREY8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9
ImF1dGhvci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iSS1ELmlldGYtb2F1dGgtand0LWJl
YXJlciI+W0ktRC5pZXRmLW9hdXRoLWp3dC1iZWFyZXJdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0
aG9yLXRleHQiPkpvbmVzLCBNLiwgQ2FtcGJlbGwsIEIuLCBhbmQgQy4gTW9ydGltb3JlLCAmbGRx
dW87PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1vYXV0aC1q
d3QtYmVhcmVyLTA1Ij5KU09OIFdlYiBUb2tlbiAoSldUKSBQcm9maWxlIGZvciBPQXV0aCAyLjAg
Q2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBBdXRob3JpemF0aW9uIEdyYW50czwvYT4sJnJkcXVv
OyBkcmFmdC1pZXRmLW9hdXRoLWp3dC1iZWFyZXItMDUgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJj
aCZuYnNwOzIwMTMgKDxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LWlldGYtb2F1dGgtand0LWJlYXJlci0wNS50eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0
dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtb2F1dGgtand0LWJl
YXJlci0wNS5wZGYiPlBERjwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRl
eHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJJLUQuaWV0Zi1vYXV0aC1zYW1sMi1iZWFyZXIiPltJ
LUQuaWV0Zi1vYXV0aC1zYW1sMi1iZWFyZXJdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRl
eHQiPkNhbXBiZWxsLCBCLiwgTW9ydGltb3JlLCBDLiwgYW5kIE0uIEpvbmVzLCAmbGRxdW87PGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1vYXV0aC1zYW1sMi1i
ZWFyZXItMTYiPlNBTUwgMi4wIFByb2ZpbGUgZm9yIE9BdXRoIDIuMCBDbGllbnQgQXV0aGVudGlj
YXRpb24gYW5kIEF1dGhvcml6YXRpb24gR3JhbnRzPC9hPiwmcmRxdW87IGRyYWZ0LWlldGYtb2F1
dGgtc2FtbDItYmVhcmVyLTE2ICh3b3JrIGluIHByb2dyZXNzKSwgTWFyY2gmbmJzcDsyMDEzICg8
YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLW9h
dXRoLXNhbWwyLWJlYXJlci0xNi50eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0
Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtb2F1dGgtc2FtbDItYmVhcmVyLTE2LnBk
ZiI+UERGPC9hPikuPC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWdu
PSJ0b3AiPjxhIG5hbWU9IkktRC5taWxsZXIteG1wcC1lMmUiPltJLUQubWlsbGVyLXhtcHAtZTJl
XTwvYT48L3RkPgo8dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5NaWxsZXIsIE0uLCAmbGRxdW87PGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbWlsbGVyLXhtcHAtZTJlLTA2
Ij5FbmQtdG8tRW5kIE9iamVjdCBFbmNyeXB0aW9uIGZvciB0aGUgRXh0ZW5zaWJsZSBNZXNzYWdp
bmcgYW5kIFByZXNlbmNlIFByb3RvY29sIChYTVBQKTwvYT4sJnJkcXVvOyBkcmFmdC1taWxsZXIt
eG1wcC1lMmUtMDYgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXkmbmJzcDsyMDEzICg8YSBocmVmPSJo
dHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1taWxsZXIteG1wcC1lMmUt
MDYudHh0Ij5UWFQ8L2E+LCA8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1taWxsZXIteG1wcC1lMmUtMDYiPkhUTUw8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9
ImF1dGhvci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iSVRVLlg2OTAuMTk5NCI+W0lUVS5Y
NjkwLjE5OTRdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPkludGVybmF0aW9uYWwg
VGVsZWNvbW11bmljYXRpb25zIFVuaW9uLCAmbGRxdW87SW5mb3JtYXRpb24gVGVjaG5vbG9neSAt
IEFTTi4xIGVuY29kaW5nIHJ1bGVzOiBTcGVjaWZpY2F0aW9uIG9mIEJhc2ljIEVuY29kaW5nIFJ1
bGVzIChCRVIpLCBDYW5vbmljYWwgRW5jb2RpbmcgUnVsZXMgKENFUikgYW5kIERpc3Rpbmd1aXNo
ZWQgRW5jb2RpbmcgUnVsZXMgKERFUiksJnJkcXVvOyBJVFUtVCZuYnNwO1JlY29tbWVuZGF0aW9u
IFguNjkwLCAxOTk0LjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGln
bj0idG9wIj48YSBuYW1lPSJPQVNJUy5zYW1sLWNvcmUtMi4wLW9zIj5bT0FTSVMuc2FtbC1jb3Jl
LTIuMC1vc108L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+PGEgaHJlZj0ibWFpbHRv
OmNhbnRvci4yQG9zdS5lZHUiPkNhbnRvciwgUy48L2E+LCA8YSBocmVmPSJtYWlsdG86Sm9obi5L
ZW1wQG5va2lhLmNvbSI+S2VtcCwgSi48L2E+LCA8YSBocmVmPSJtYWlsdG86cnBoaWxwb3R0QHJz
YXNlY3VyaXR5LmNvbSI+UGhpbHBvdHQsIFIuPC9hPiwgYW5kIDxhIGhyZWY9Im1haWx0bzpldmUu
bWFsZXJAc3VuLmNvbSI+RS4gTWFsZXI8L2E+LCAmbGRxdW87PGEgaHJlZj0iaHR0cDovL2RvY3Mu
b2FzaXMtb3Blbi5vcmcvc2VjdXJpdHkvc2FtbC92Mi4wL3NhbWwtY29yZS0yLjAtb3MucGRmIj5B
c3NlcnRpb25zIGFuZCBQcm90b2NvbCBmb3IgdGhlIE9BU0lTIFNlY3VyaXR5IEFzc2VydGlvbiBN
YXJrdXAgTGFuZ3VhZ2UKICAgICAgICAgICAgKFNBTUwpIFYyLjA8L2E+LCZyZHF1bzsgT0FTSVMg
U3RhbmRhcmQmbmJzcDtzYW1sLWNvcmUtMi4wLW9zLCBNYXJjaCZuYnNwOzIwMDUuPC90ZD48L3Ry
Pgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9Ik9wZW5J
RC5NZXNzYWdlcyI+W09wZW5JRC5NZXNzYWdlc108L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3It
dGV4dCI+U2FraW11cmEsIE4uLCBCcmFkbGV5LCBKLiwgSm9uZXMsIE0uLCBkZSBNZWRlaXJvcywg
Qi4sIE1vcnRpbW9yZSwgQy4sIGFuZCBFLiBKYXksICZsZHF1bzs8YSBocmVmPSJodHRwOi8vb3Bl
bmlkLm5ldC9zcGVjcy9vcGVuaWQtY29ubmVjdC1tZXNzYWdlcy0xXzAuaHRtbCI+T3BlbklEIENv
bm5lY3QgTWVzc2FnZXMgMS4wPC9hPiwmcmRxdW87IEp1bmUmbmJzcDsyMDEzLjwvdGQ+PC90cj4K
PHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJQZXJzb25h
Ij5bUGVyc29uYV08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+TW96aWxsYSwgJmxk
cXVvOzxhIGhyZWY9Imh0dHBzOi8vZGV2ZWxvcGVyLm1vemlsbGEub3JnL2VuLVVTL2RvY3MvUGVy
c29uYSI+TW96aWxsYSBQZXJzb25hPC9hPiwmcmRxdW87IEFwcmlsJm5ic3A7MjAxMy48L3RkPjwv
dHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iUkZD
MjYxNiI+W1JGQzI2MTZdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPjxhIGhyZWY9
Im1haWx0bzpmaWVsZGluZ0BpY3MudWNpLmVkdSI+RmllbGRpbmcsIFIuPC9hPiwgPGEgaHJlZj0i
bWFpbHRvOmpnQHczLm9yZyI+R2V0dHlzLCBKLjwvYT4sIDxhIGhyZWY9Im1haWx0bzptb2d1bEB3
cmwuZGVjLmNvbSI+TW9ndWwsIEouPC9hPiwgPGEgaHJlZj0ibWFpbHRvOmZyeXN0eWtAdzMub3Jn
Ij5GcnlzdHlrLCBILjwvYT4sIDxhIGhyZWY9Im1haWx0bzptYXNpbnRlckBwYXJjLnhlcm94LmNv
bSI+TWFzaW50ZXIsIEwuPC9hPiwgPGEgaHJlZj0ibWFpbHRvOnBhdWxsZUBtaWNyb3NvZnQuY29t
Ij5MZWFjaCwgUC48L2E+LCBhbmQgPGEgaHJlZj0ibWFpbHRvOnRpbWJsQHczLm9yZyI+VC4gQmVy
bmVycy1MZWU8L2E+LCAmbGRxdW87PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
cmZjMjYxNiI+SHlwZXJ0ZXh0IFRyYW5zZmVyIFByb3RvY29sIC0tIEhUVFAvMS4xPC9hPiwmcmRx
dW87IFJGQyZuYnNwOzI2MTYsIEp1bmUmbmJzcDsxOTk5ICg8YSBocmVmPSJodHRwOi8vd3d3LnJm
Yy1lZGl0b3Iub3JnL3JmYy9yZmMyNjE2LnR4dCI+VFhUPC9hPiwgPGEgaHJlZj0iaHR0cDovL3d3
dy5yZmMtZWRpdG9yLm9yZy9yZmMvcmZjMjYxNi5wcyI+UFM8L2E+LCA8YSBocmVmPSJodHRwOi8v
d3d3LnJmYy1lZGl0b3Iub3JnL3JmYy9yZmMyNjE2LnBkZiI+UERGPC9hPiwgPGEgaHJlZj0iaHR0
cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGljL3JmYy9odG1sL3JmYzI2MTYuaHRtbCI+SFRNTDwv
YT4sIDxhIGhyZWY9Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMveG1sL3JmYzI2
MTYueG1sIj5YTUw8L2E+KS48L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2
YWxpZ249InRvcCI+PGEgbmFtZT0iUkZDMjgxOCI+W1JGQzI4MThdPC9hPjwvdGQ+Cjx0ZCBjbGFz
cz0iYXV0aG9yLXRleHQiPlJlc2NvcmxhLCBFLiwgJmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly90b29s
cy5pZXRmLm9yZy9odG1sL3JmYzI4MTgiPkhUVFAgT3ZlciBUTFM8L2E+LCZyZHF1bzsgUkZDJm5i
c3A7MjgxOCwgTWF5Jm5ic3A7MjAwMCAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9y
Zy9yZmMvcmZjMjgxOC50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0
aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJSRkMzMjA3Ij5bUkZDMzIwN108L2E+PC90
ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+SG9mZm1hbiwgUC4sICZsZHF1bzs8YSBocmVmPSJo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMzMjA3Ij5TTVRQIFNlcnZpY2UgRXh0ZW5zaW9u
IGZvciBTZWN1cmUgU01UUCBvdmVyIFRyYW5zcG9ydCBMYXllciBTZWN1cml0eTwvYT4sJnJkcXVv
OyBSRkMmbmJzcDszMjA3LCBGZWJydWFyeSZuYnNwOzIwMDIgKDxhIGhyZWY9Imh0dHA6Ly93d3cu
cmZjLWVkaXRvci5vcmcvcmZjL3JmYzMyMDcudHh0Ij5UWFQ8L2E+KS48L3RkPjwvdHI+Cjx0cj48
dGQgY2xhc3M9ImF1dGhvci10ZXh0IiB2YWxpZ249InRvcCI+PGEgbmFtZT0iUkZDMzkyMyI+W1JG
QzM5MjNdPC9hPjwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPjxhIGhyZWY9Im1haWx0bzpz
dHBldGVyQGphYmJlci5vcmciPlNhaW50LUFuZHJlLCBQLjwvYT4sICZsZHF1bzs8YSBocmVmPSJo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMzOTIzIj5FbmQtdG8tRW5kIFNpZ25pbmcgYW5k
IE9iamVjdCBFbmNyeXB0aW9uIGZvciB0aGUgRXh0ZW5zaWJsZSBNZXNzYWdpbmcgYW5kIFByZXNl
bmNlIFByb3RvY29sIChYTVBQKTwvYT4sJnJkcXVvOyBSRkMmbmJzcDszOTIzLCBPY3RvYmVyJm5i
c3A7MjAwNCAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9yZmMvcmZjMzkyMy50
eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMv
aHRtbC9yZmMzOTIzLmh0bWwiPkhUTUw8L2E+LCA8YSBocmVmPSJodHRwOi8veG1sLnJlc291cmNl
Lm9yZy9wdWJsaWMvcmZjL3htbC9yZmMzOTIzLnhtbCI+WE1MPC9hPikuPC90ZD48L3RyPgo8dHI+
PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IlJGQzQzMDEiPltS
RkM0MzAxXTwvYT48L3RkPgo8dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5LZW50LCBTLiBhbmQgSy4g
U2VvLCAmbGRxdW87PGEgaHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDMwMSI+
U2VjdXJpdHkgQXJjaGl0ZWN0dXJlIGZvciB0aGUgSW50ZXJuZXQgUHJvdG9jb2w8L2E+LCZyZHF1
bzsgUkZDJm5ic3A7NDMwMSwgRGVjZW1iZXImbmJzcDsyMDA1ICg8YSBocmVmPSJodHRwOi8vd3d3
LnJmYy1lZGl0b3Iub3JnL3JmYy9yZmM0MzAxLnR4dCI+VFhUPC9hPikuPC90ZD48L3RyPgo8dHI+
PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IlJGQzUyNDYiPltS
RkM1MjQ2XTwvYT48L3RkPgo8dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5EaWVya3MsIFQuIGFuZCBF
LiBSZXNjb3JsYSwgJmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3Jm
YzUyNDYiPlRoZSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykgUHJvdG9jb2wgVmVyc2lv
biAxLjI8L2E+LCZyZHF1bzsgUkZDJm5ic3A7NTI0NiwgQXVndXN0Jm5ic3A7MjAwOCAoPGEgaHJl
Zj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9yZmMvcmZjNTI0Ni50eHQiPlRYVDwvYT4pLjwv
dGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1l
PSJSRkM1MzIyIj5bUkZDNTMyMl08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+PGEg
aHJlZj0ibWFpbHRvOnByZXNuaWNrQHF1YWxjb21tLmNvbSI+UmVzbmljaywgUC4sIEVkLjwvYT4s
ICZsZHF1bzs8YSBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1MzIyIj5JbnRl
cm5ldCBNZXNzYWdlIEZvcm1hdDwvYT4sJnJkcXVvOyBSRkMmbmJzcDs1MzIyLCBPY3RvYmVyJm5i
c3A7MjAwOCAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9yZmMvcmZjNTMyMi50
eHQiPlRYVDwvYT4sIDxhIGhyZWY9Imh0dHA6Ly94bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMv
aHRtbC9yZmM1MzIyLmh0bWwiPkhUTUw8L2E+LCA8YSBocmVmPSJodHRwOi8veG1sLnJlc291cmNl
Lm9yZy9wdWJsaWMvcmZjL3htbC9yZmM1MzIyLnhtbCI+WE1MPC9hPikuPC90ZD48L3RyPgo8dHI+
PHRkIGNsYXNzPSJhdXRob3ItdGV4dCIgdmFsaWduPSJ0b3AiPjxhIG5hbWU9IlJGQzU3NTEiPltS
RkM1NzUxXTwvYT48L3RkPgo8dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij5SYW1zZGVsbCwgQi4gYW5k
IFMuIFR1cm5lciwgJmxkcXVvOzxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL3Jm
YzU3NTEiPlNlY3VyZS9NdWx0aXB1cnBvc2UgSW50ZXJuZXQgTWFpbCBFeHRlbnNpb25zIChTL01J
TUUpIFZlcnNpb24gMy4yIE1lc3NhZ2UgU3BlY2lmaWNhdGlvbjwvYT4sJnJkcXVvOyBSRkMmbmJz
cDs1NzUxLCBKYW51YXJ5Jm5ic3A7MjAxMCAoPGEgaHJlZj0iaHR0cDovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9yZmMvcmZjNTc1MS50eHQiPlRYVDwvYT4pLjwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0i
YXV0aG9yLXRleHQiIHZhbGlnbj0idG9wIj48YSBuYW1lPSJXUy1GZWRlcmF0aW9uIj5bV1MtRmVk
ZXJhdGlvbl08L2E+PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+S2FsZXIsIEMuLCBNY0lu
dG9zaCwgTS4sIEdvb2RuZXIsIE0uLCBhbmQgQS4gTmFkYWxpbiwgJmxkcXVvOzxhIGhyZWY9Imh0
dHA6Ly9kb2NzLm9hc2lzLW9wZW4ub3JnL3dzZmVkL2ZlZGVyYXRpb24vdjEuMi9vcy93cy1mZWRl
cmF0aW9uLTEuMi1zcGVjLW9zLmh0bWwiPldlYiBTZXJ2aWNlcyBGZWRlcmF0aW9uIExhbmd1YWdl
IChXUy1GZWRlcmF0aW9uKSBWZXJzaW9uIDEuMjwvYT4sJnJkcXVvOyBNYXkmbmJzcDsyMDA5Ljwv
dGQ+PC90cj4KPC90YWJsZT4KCjxhIG5hbWU9ImFjay1zZWMiPjwvYT48YnIgLz48aHIgLz4KPHRh
YmxlIHN1bW1hcnk9ImxheW91dCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIyIiBjbGFz
cz0iVE9DYnVnIiBhbGlnbj0icmlnaHQiPjx0cj48dGQgY2xhc3M9IlRPQ2J1ZyI+PGEgaHJlZj0i
I3RvYyI+Jm5ic3A7VE9DJm5ic3A7PC9hPjwvdGQ+PC90cj48L3RhYmxlPgo8YSBuYW1lPSJyZmMu
c2VjdGlvbi5BIj48L2E+PGgzPkFwcGVuZGl4IEEuJm5ic3A7CkFja25vd2xlZGdlbWVudHM8L2gz
PgoKPHA+VGhhbmtzIHRvIE1hdHQgTWlsbGVyIGZvciBkaXNjdXNzaW9ucyByZWxhdGVkIHRvIFhN
UFAgZW5kLXRvLWVuZAogICAgICBzZWN1cml0eSBtb2RlbCwgYW5kIHRvIE1pa2UgSm9uZXMgZm9y
IGNvbnNpZGVyYXRpb25zIHJlbGF0ZWQgdG8gc2VjdXJpdHkKICAgICAgdG9rZW5zIGFuZCBYTUwg
c2VjdXJpdHkuICBUaGFua3MgdG8gTWFyayBXYXRzb24gZm9yIHJhaXNpbmcgdGhlIG5lZWQgZm9y
IAogICAgICByZXByZXNlbnRpbmcgc3ltbWV0cmljIGtleXMgYW5kIGJpbmRpbmcgYXR0cmlidXRl
cyB0byB0aGVtLgo8L3A+CjxhIG5hbWU9Imhpc3Qtc2VjIj48L2E+PGJyIC8+PGhyIC8+Cjx0YWJs
ZSBzdW1tYXJ5PSJsYXlvdXQiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMiIgY2xhc3M9
IlRPQ2J1ZyIgYWxpZ249InJpZ2h0Ij48dHI+PHRkIGNsYXNzPSJUT0NidWciPjxhIGhyZWY9IiN0
b2MiPiZuYnNwO1RPQyZuYnNwOzwvYT48L3RkPjwvdHI+PC90YWJsZT4KPGEgbmFtZT0icmZjLnNl
Y3Rpb24uQiI+PC9hPjxoMz5BcHBlbmRpeCBCLiZuYnNwOwpEb2N1bWVudCBIaXN0b3J5PC9oMz4K
CjxwPgoJW1sgdG8gYmUgcmVtb3ZlZCBieSB0aGUgUkZDIGVkaXRvciBiZWZvcmUgcHVibGljYXRp
b24gYXMgYW4gUkZDIF1dCiAgICAgIAo8L3A+CjxwPgogICAgICAgIC0wMwogICAgICAgIDwvcD4K
PHVsIGNsYXNzPSJ0ZXh0Ij4KPGxpPgogICAgICAgICAgICBFZGl0b3JpYWwgYW5kIGZhY3R1YWwg
Y29ycmVjdGlvbnMuCgkgIAo8L2xpPgo8L3VsPjxwPgogICAgICAKPC9wPgo8cD4KICAgICAgICAt
MDIKICAgICAgICA8L3A+Cjx1bCBjbGFzcz0idGV4dCI+CjxsaT4KICAgICAgICAgICAgUmVmZXJl
bmNlZCB0aGUgSldTLCBKV0UsIEpXSywgYW5kIEpXQSBzcGVjaWZpY2F0aW9ucwoJICAgIG1ha2lu
ZyB0aGUgInNpZ25lZCBvYmplY3QgZm9ybWF0IiwgImVuY3J5cHRlZCBvYmplY3QgZm9ybWF0IiwK
CSAgICAia2V5IGZvcm1hdCIsIGFuZCBhbGdvcml0aG1zIHJlc3VsdGluZyBmcm9tIHRoZXNlIHVz
ZSBjYXNlcyBjb25jcmV0ZS4KICAgICAgICAgIAo8L2xpPgo8bGk+CgkgICAgQWRkZWQgIlJlcXVp
cmVtZW50cyBvbiBBcHBsaWNhdGlvbiBQcm90b2NvbHMiIHNlY3Rpb24uCgkgIAo8L2xpPgo8bGk+
CgkgICAgQnJva2UgZm9ybWVyIGh1Z2UgIlNlY3VyaXR5IFRva2VucyBhbmQgQXV0aG9yaXphdGlv
biIgVXNlIENhc2Ugc2VjdGlvbgoJICAgIGludG8gIlNlY3VyaXR5IFRva2VucyIsICJPQXV0aCIs
IGFuZCAiRmVkZXJhdGlvbiIgVXNlIENhc2Ugc2VjdGlvbnMuCgkgIAo8L2xpPgo8bGk+CgkgICAg
Q2l0ZWQgTW96aWxsYSBQZXJzb25hIGFzIGEgc2luZ2xlLXNpZ24tb24gKFNTTykgc3lzdGVtIHVz
aW5nIEpXVHMKCSAgICBhbmQgSk9TRSBkYXRhIGZvcm1hdHMuCgkgIAo8L2xpPgo8bGk+CgkgICAg
U3BlbGxpbmcgYW5kIGdyYW1tYXIgY29ycmVjdGlvbnMuCgkgIAo8L2xpPgo8L3VsPjxwPgogICAg
ICAKPC9wPgo8cD4KICAgICAgICAtMDEKICAgICAgICA8L3A+Cjx1bCBjbGFzcz0idGV4dCI+Cjxs
aT5BZGRlZCB0aGUgIlNtYWxsIERldmljZXMiIHVzZSBjYXNlCjwvbGk+CjwvdWw+PHA+CiAgICAg
IAo8L3A+CjxwPgogICAgICAgIC0wMAogICAgICAgIDwvcD4KPHVsIGNsYXNzPSJ0ZXh0Ij4KPGxp
PgogICAgICAgICAgICBDcmVhdGVkIHRoZSBpbml0aWFsIElFVEYgZHJhZnQgYmFzZWQgdXBvbgog
ICAgICAgICAgICBkcmFmdC1iYXJuZXMtam9zZS11c2UtY2FzZXMtMDEgd2l0aCBzb21lIGFkZGl0
aW9ucy4KICAgICAgICAgIAo8L2xpPgo8L3VsPjxwPgogICAgICAKPC9wPgo8YSBuYW1lPSJyZmMu
YXV0aG9ycyI+PC9hPjxiciAvPjxociAvPgo8dGFibGUgc3VtbWFyeT0ibGF5b3V0IiBjZWxscGFk
ZGluZz0iMCIgY2VsbHNwYWNpbmc9IjIiIGNsYXNzPSJUT0NidWciIGFsaWduPSJyaWdodCI+PHRy
Pjx0ZCBjbGFzcz0iVE9DYnVnIj48YSBocmVmPSIjdG9jIj4mbmJzcDtUT0MmbmJzcDs8L2E+PC90
ZD48L3RyPjwvdGFibGU+CjxoMz5BdXRob3IncyBBZGRyZXNzPC9oMz4KPHRhYmxlIHdpZHRoPSI5
OSUiIGJvcmRlcj0iMCIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIwIj4KPHRyPjx0ZCBj
bGFzcz0iYXV0aG9yLXRleHQiPiZuYnNwOzwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPlJp
Y2hhcmQgQmFybmVzPC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+Jm5ic3A7
PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+QkJOIFRlY2hub2xvZ2llczwvdGQ+PC90cj4K
PHRyPjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPiZuYnNwOzwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9y
LXRleHQiPjEzMDAgTiAxN3RoIFN0PC90ZD48L3RyPgo8dHI+PHRkIGNsYXNzPSJhdXRob3ItdGV4
dCI+Jm5ic3A7PC90ZD4KPHRkIGNsYXNzPSJhdXRob3ItdGV4dCI+QXJsaW5ndG9uLCBWQSAgMjIy
MDk8L3RkPjwvdHI+Cjx0cj48dGQgY2xhc3M9ImF1dGhvci10ZXh0Ij4mbmJzcDs8L3RkPgo8dGQg
Y2xhc3M9ImF1dGhvci10ZXh0Ij5VUzwvdGQ+PC90cj4KPHRyPjx0ZCBjbGFzcz0iYXV0aG9yIiBh
bGlnbj0icmlnaHQiPkVtYWlsOiZuYnNwOzwvdGQ+Cjx0ZCBjbGFzcz0iYXV0aG9yLXRleHQiPjxh
IGhyZWY9Im1haWx0bzpybGJAaXB2LnN4Ij5ybGJAaXB2LnN4PC9hPjwvdGQ+PC90cj4KPC90YWJs
ZT4KPC9ib2R5PjwvaHRtbD4K

--_007_4E1F6AAD24975D4BA5B168042967394367872E2ATK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Tue Jun 18 18:42:11 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D61821F9B1B for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 18:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8io83zVmrol for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 18:42:05 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id DAFDA21F9B1A for <jose@ietf.org>; Tue, 18 Jun 2013 18:42:04 -0700 (PDT)
Received: from BN1BFFO11FD009.protection.gbl (10.58.52.203) by BN1BFFO11HUB006.protection.gbl (10.58.53.116) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 19 Jun 2013 01:26:06 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD009.mail.protection.outlook.com (10.58.53.69) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 19 Jun 2013 01:26:06 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Wed, 19 Jun 2013 01:26:05 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQ==
Date: Wed, 19 Jun 2013 01:26:04 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678735D4TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(51444003)(189002)(54356001)(31966008)(74366001)(77096001)(512954002)(81342001)(66066001)(81542001)(76786001)(69226001)(74706001)(74502001)(63696002)(49866001)(74662001)(47446002)(46102001)(56776001)(51856001)(65816001)(74876001)(55846006)(15202345002)(50986001)(76796001)(77982001)(76482001)(33656001)(47976001)(79102001)(56816003)(16406001)(6806003)(54316002)(20776003)(53806001)(4396001)(80022001)(71186001)(59766001)(16236675002)(47736001)(76176001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB006; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08828D20BC
Subject: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Jun 2013 01:42:12 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678735D4TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The JWS and JWE documents currently define these MIME types for the conveni=
ence of applications that may want to use them:
                application/jws
                application/jws+json
                application/jwe
                application/jwe+json

That being said, I'm not aware of any uses of these by applications at pres=
ent.  Thus, I think that makes it fair game to ask whether we want to keep =
them or remove them - in which case, if applications ever needed them, they=
 could define them later.

Another dimension of this question for JWS and JWE is that it's not clear t=
hat the four types application/jws, application/jws+json, application/jwe, =
and application/jwe+json are even the right ones.  It might be more useful =
to have generic application/jose and application/jose+json types, which cou=
ld hold either JWS or JWE objects respectively using the compact or JSON se=
rializations (although I'm not advocating adding them at this time).

Having different JWS versus JWE MIME types apparently did contribute to at =
least Dick's confusion about the purpose of the "typ" field, so deleting th=
em could help eliminate this possibility of confusion in the future.  Thus,=
 I'm increasingly convinced we should get rid of the JWS and JWE types and =
leave it up to applications to define the types they need, when they need t=
hem.

Do people have use cases for these four MIME types now or should we leave t=
hem to future specs to define, if needed?

                                                                -- Mike

P.S.  For completeness, I'll add that the JWK document also defines these M=
IME types:
                application/jwk+json
                application/jwk-set+json

There are already clear use cases for these types, so I'm not advocating de=
leting them, but wanted to call that out explicitly.  For instance, when re=
trieving a JWK Set document referenced by a "jku" header parameter, I belie=
ve that the result should use the application/jwk-set+json type.  (In fact,=
 I'll add this to the specs, unless there are any objections.)  Likewise, d=
raft-miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.  B=
oth could also be as "cty" values when encrypting JWKs and JWK Sets, in con=
texts where that that would be useful.


--_000_4E1F6AAD24975D4BA5B1680429673943678735D4TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:<o:p>=
</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json<o:p></o:p><=
/p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">That being said, I&#8217;m not aware of any uses of =
these by applications at present.&nbsp; Thus, I think that makes it fair ga=
me to ask whether we want to keep them or remove them &#8211; in which case=
, if applications ever needed them, they could define
 them later.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it&#8217;s not clear that the four types application/jws, applicatio=
n/jws&#43;json, application/jwe, and application/jwe&#43;json are even the =
right ones.&nbsp; It might be more useful to have generic
 application/jose and application/jose&#43;json types, which could hold eit=
her JWS or JWE objects respectively using the compact or JSON serialization=
s (although I&#8217;m not advocating adding them at this time).<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick&#8217;s confusion about the purpose of th=
e &#8220;typ&#8221; field, so deleting them could help eliminate this possi=
bility of confusion in the future.&nbsp; Thus, I&#8217;m increasingly
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">P.S.&nbsp; For completeness, I&#8217;ll add that the=
 JWK document also defines these MIME types:<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json<o:p></o:p><=
/p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;json<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I&#8217;m not advocating deleting them, but wanted to call that out expli=
citly.&nbsp; For instance, when retrieving a JWK Set document referenced by=
 a &#8220;jku&#8221; header parameter, I believe that the
 result should use the application/jwk-set&#43;json type.&nbsp; (In fact, I=
&#8217;ll add this to the specs, unless there are any objections.)&nbsp; Li=
kewise, draft-miller-jose-jwe-protected-jwk-02 already uses application/jwk=
&#43;json.&nbsp; Both could also be as &#8220;cty&#8221; values when encryp=
ting
 JWKs and JWK Sets, in contexts where that that would be useful.<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678735D4TK5EX14MBXC283r_--

From James.H.Manger@team.telstra.com  Tue Jun 18 20:52:40 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA0921F99EC for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 20:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.644
X-Spam-Level: 
X-Spam-Status: No, score=-0.644 tagged_above=-999 required=5 tests=[AWL=0.257,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KrwmchtN4m5t for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 20:52:34 -0700 (PDT)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by ietfa.amsl.com (Postfix) with ESMTP id BB5D221F99E2 for <jose@ietf.org>; Tue, 18 Jun 2013 20:52:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,894,1363093200"; d="scan'208";a="136092060"
Received: from unknown (HELO ipcdni.tcif.telstra.com.au) ([10.97.216.212]) by ipocni.tcif.telstra.com.au with ESMTP; 19 Jun 2013 13:52:30 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7110"; a="104158992"
Received: from wsmsg3704.srv.dir.telstra.com ([172.49.40.197]) by ipcdni.tcif.telstra.com.au with ESMTP; 19 Jun 2013 13:52:31 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3704.srv.dir.telstra.com ([172.49.40.197]) with mapi; Wed, 19 Jun 2013 13:52:30 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Date: Wed, 19 Jun 2013 13:52:29 +1000
Thread-Topic: Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQAAxHXw
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Jun 2013 03:52:40 -0000

R29vZCBxdWVzdGlvbnMsIE1pa2UuIE15IChiYWNrd2FyZCBjb21wYXRpYmxlKSBzdWdnZXN0aW9u
cyBiZWxvdy4NCg0KPiBUaGUgSldTIGFuZCBKV0UgZG9jdW1lbnRzIGN1cnJlbnRseSBkZWZpbmUg
dGhlc2UgTUlNRSB0eXBlcyBmb3IgdGhlDQo+IGNvbnZlbmllbmNlIG9mIGFwcGxpY2F0aW9ucyB0
aGF0IG1heSB3YW50IHRvIHVzZSB0aGVtOg0KPiDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
wqAgYXBwbGljYXRpb24vandzDQo+IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBs
aWNhdGlvbi9qd3MranNvbg0KPiDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgYXBwbGlj
YXRpb24vandlDQo+IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBsaWNhdGlvbi9q
d2UranNvbg0KDQpEcm9wIHRoZXNlLg0KRGVmaW5lIGFwcGxpY2F0aW9uL2pvc2UgYW5kIGFwcGxp
Y2F0aW9uL2pvc2UranNvbi4NCg0KQWxsb3cgdHdvIG9wdGlvbmFsIHBhcmFtZXRlcnMgb24gdGhl
c2UgbWVkaWEgdHlwZXM6DQoNCiAgaW5uZXIgLS0gaW5kaWNhdGVzIHRoZSBtZWRpYSB0eXBlIG9m
IHRoZSBjb250ZW50IG9mIHRoZSBKT1NFIG1lc3NhZ2UsIGFmdGVyIHJlbW92aW5nIDEgb3IgbW9y
ZSBsYXllcnMgb2YgSk9TRSBwcm90ZWN0aW9uLiBGb3IgaW5zdGFuY2UsIGlmIGEgSlBFRyBpbWFn
ZSBpcyBzaWduZWQgd2l0aCBhbiBSU0Ega2V5LCB0aGVuIGVuY3J5cHRlZCB3aXRoIEFFUy1HQ00s
IGlubmVyIHdvdWxkIGJlIGltYWdlL2pwZWcuDQoNCiAgbW9kZSAtLSBpbmRpY2F0ZXMgdGhlIHNv
cnQgb2YgcHJvdGVjdGlvbiBhcHBsaWVkIChlZyBzaWduZWQsIGVuY3J5cHRlZCwgdW5wcm90ZWN0
ZWQuLi4pLiBJZiBtdWx0aXBsZSBtb2RlcyBvZiBwcm90ZWN0aW9uIGFyZSBhcHBsaWVkIGluIHR1
cm4gKGVnIHNpZ25lZCB0aGVuIGVuY3J5cHRlZCkgdGhleSBjYW4gYWxsIGJlIGxpc3RlZDogZnJv
bSB0aGUgb3V0ZXItbW9zdCBtb2RlIHRvIHRoZSBpbm5lci1tb3N0OyBzZXBhcmF0ZWQgYnkgYSBw
bHVzIChlZyBtb2RlPSJlbmMrc2lnIikuDQoNCg0KQSAibW9kZSIgbWVkaWEgdHlwZSBwYXJhbWV0
ZXIgd291bGQgYmUgZWFzeSB0byBzcGVjaWZ5IGlmIEpPU0UgbWVzc2FnZXMgaGFkIGEgY29ycmVz
cG9uZGluZyBoZWFkZXIgZmllbGQsIGluc3RlYWQgb2YgaW5mZXJyaW5nIHRoZSBzb3J0IG9mIHBy
b2Nlc3NpbmcgZnJvbSB0aGUgImFsZyIgdmFsdWUuIDotKA0KDQoNClN1Z2dlc3Rpb246DQoNCjEu
IERlZmluZSBhIGhlYWRlciBwYXJhbWV0ZXIgdGhhdCBpbmRpY2F0ZXMgdGhlIHNvcnQgb2YgcHJv
Y2Vzc2luZy4gSXRzIG5hbWUgY291bGQgYmUgIlQiLCBvciAibW9kZSIgKGp1c3Qgbm90ICJ0eXAi
IGFzIHRoYXQgaXMgdG9vIGNvbmZ1c2VkKS4NCltJIGxpa2UgIlQiIChzaG9ydDsgc3RhbmRzIG91
dCBhcyBUSEUgcHJpbWFyeSBmaWVsZCBpbiBhIEpPU0UgbWVzc2FnZSksIGJ1dCBJIHVzZSAibW9k
ZSIgYmVsb3cgdG8gYmUgYSBsaXR0bGUgbGVzcyBjb250cm92ZXJzaWFsLl0NCg0KMi4gQ3JlYXRl
IGEgcmVnaXN0cnkgZm9yICJtb2RlIiB2YWx1ZXMuDQoNCjMuIERlZmluZSBzb21lIGluaXRpYWwg
Im1vZGUiIHZhbHVlcywgYWxvbmdzaWRlIHRoZSBzcGVjIGZvciB0aGF0IHByb2Nlc3Npbmc6DQog
ICJzaWcxIiBmb3IgZGlnaXRhbGx5IHNpZ25pbmcgQjY0KGhlYWRlcikuQjY0KGNvbnRlbnQpOw0K
ICAibWFjMSIgZm9yIE1BQyBvdmVyIEI2NChoZWFkZXIpLkI2NChjb250ZW50KTsNCiAgImVuYzEi
IGZvciBBRUFELCB3aGVyZSBBQUQgaXMgQjY0KGhlYWRlcikNCiAgIm5vbmUiIGZvciB1bnByb2Nl
c3NlZCBjb250ZW50DQogICJjbXAiIGZvciBjb21wcmVzc2VkIChidXQgbm90IHByb3RlY3RlZCkg
Y29udGVudA0KICAiZW5jMiIgZm9yIEFFQUQgYXBwbGllZCBkaWZmZXJlbnRseSAoYXMgcGVyIHRo
ZSBKU09OIHJlcHJlc2VudGF0aW9uKQ0KICAuLi4NCg0KNC4gQWxsb3cgdGhlICJtb2RlIiBwYXJh
bWV0ZXIgdG8gYmUgYWJzZW50IGlmIGFuICJhbGciIHZhbHVlIGlzIHByZXNlbnQgYW5kIGhhcyBh
IGRlZmF1bHQgIm1vZGUiLiBUaGlzIG1haW50YWlucyBjb21wYXRpYmlsaXR5IHdpdGggSk9TRSBt
ZXNzYWdlcyBiYXNlZCBvbiBwcmV2aW91cyBkcmFmdHMuDQoNCjUuIERlZmluZSB0aGUgZGVmYXVs
dCAibW9kZSIgZm9yIGV4aXN0aW5nICJhbGciIHZhbHVlcy4gRm9yIGluc3RhbmNlLCBmb3IgImFs
ZyI6IkhTMjU2IiB0aGUgZGVmYXVsdCBpcyAibW9kZSI6Im1hYzEiLiBUaGUgcmVnaXN0cnkgb2Yg
YWxnIHZhbHVlcyB3b3VsZCBoYXZlIGEgY29sdW1uIGZvciB0aGUgZGVmYXVsdCBtb2RlICh0aG91
Z2ggbmV3IGFsZ3MgY2FuIGxlYXZlIHRoYXQgY29sdW1uIGJsYW5rKS4NCg0KNi4gRHJvcCB0aGUg
ImNyaXQiIGZpZWxkLiBJZiB5b3UgYXJlIGNyZWF0aW5nIGEgSk9TRSBtZXNzYWdlIHdpdGggbmV3
IHNlbWFudGljcyB0aGF0IE1VU1QgYmUgdW5kZXJzdG9vZCwganVzdCBkZWZpbmUgYSBuZXcgIm1v
ZGUiIHZhbHVlLiBGb3IgZXhhbXBsZSwgdG8gYXZvaWQgc29tZSBiYXNlNjQgb3ZlcmhlYWQgeW91
IGNvdWxkIGRlZmluZSAibW9kZSI6InNpZzIiIHRvIG1lYW4gZGlnaXRhbGx5IHNpZ24gaGVhZGVy
fHxjb250ZW50fHxsZW4oaGVhZGVyKS4NCg0KNy4gQWxsb3cgYSBsaXN0IG9mICJtb2RlIiB2YWx1
ZXMgdG8gYmUgc3BlY2lmaWVkIGFzIGEgcGFyYW1ldGVyIG9uIGEgSk9TRSBtZWRpYSB0eXBlLg0K
DQoNCltwcm9iYWJseV0NCjguIEEgcGx1cyBzaWduICIrIiBjYW4gYmUgYXBwZW5kZWQgdG8gYW55
ICJtb2RlIiB2YWx1ZSB0byBpbmRpY2F0ZSB0aGF0IHRoZSBjb250ZW50IG9mIHRoaXMgSk9TRSBs
YXllciBpcyBhbm90aGVyIEpPU0UgbGF5ZXIuIFRoYXQgaXMsIHByb2Nlc3MgdGhpcyBtZXNzYWdl
IGFzIHBlciB0aGUgIm1vZGUiIHdpdGhvdXQgdGhlICIrIiwgdGhlbiBwcm9jZXNzIHRoZSBjb250
ZW50IGFzIGFub3RoZXIgSk9TRSBtZXNzYWdlLg0KW0FwcGVuZGluZyAiKyIgaXMgc2ltcGxlciB0
aGFuICJjdHkiOiJqd3MiIG9yICJtb3JlIjp0cnVlLCBidXQgYXNzdW1lcyB0aGUgaW5uZXIgSk9T
RSBtZXNzYWdlIHVzZXMgdGhlIHNhbWUgc2VyaWFsaXphdGlvbiBhcyB0aGUgb3V0ZXIgb25lLl0N
Cg0KDQpFbmQgcmVzdWx0OiBzaW1wbGVyLCBtb3JlIGVhc2lseSB1bmRlcnN0b29kIGJ5IHBlb3Bs
ZTsgb25lIGZpZWxkIHRoYXQgaXMgc3VpdGFibGUgZm9yIGFuIGltcGxlbWVudGF0aW9uIHRvIHVz
ZSB0byBzd2l0Y2ggdG8gdGhlIGFwcHJvcHJpYXRlIHByb2Nlc3NpbmcgY29kZTsgYmFja3dhcmQg
Y29tcGF0aWJsZSB3aXRoIGVhcmxpZXIgZHJhZnRzOyBjbGVhciBtZWNoYW5pc20gZm9yIG1ha2lu
ZyBjaGFuZ2VzIHRoYXQgTVVTVC1iZS11bmRlcnN0b29kICh0aGF0IHdlIGNhbiBiZSBjb25maWRl
bnQgY29kZSB3aWxsIG5vdGljZSkuDQoNCg0KDQo+IFRoYXQgYmVpbmcgc2FpZCwgSeKAmW0gbm90
IGF3YXJlIG9mIGFueSB1c2VzIG9mIHRoZXNlIGJ5IGFwcGxpY2F0aW9ucyBhdA0KPiBwcmVzZW50
Lg0KDQpBcHBzIHN1Y2ggYXMgT3BlbklEIENvbm5lY3QgY291bGQgdXNlOg0KICBhcHBsaWNhdGlv
bi9qb3NlO2lubmVyPWFwcGxpY2F0aW9uL2p3dCtqc29uDQoNCkFwcHMgY2FuIHN0aWxsIGRlZmlu
ZSB0aGVpciBvd24gbWVkaWEgdHlwZXMgZm9yIEpPU0UgbWVzc2FnZXMgKGVnIGFwcGxpY2F0aW9u
L2p3dCkgdGhvdWdoIHRoYXQgc2hvdWxkIG5vdCBiZSBuZWNlc3NhcnkuDQoNCg0KPsKgIFRodXMs
IEkgdGhpbmsgdGhhdCBtYWtlcyBpdCBmYWlyIGdhbWUgdG8gYXNrIHdoZXRoZXIgd2Ugd2FudA0K
PiB0byBrZWVwIHRoZW0gb3IgcmVtb3ZlIHRoZW0g4oCTIGluIHdoaWNoIGNhc2UsIGlmIGFwcGxp
Y2F0aW9ucyBldmVyDQo+IG5lZWRlZCB0aGVtLCB0aGV5IGNvdWxkIGRlZmluZSB0aGVtIGxhdGVy
Lg0KPiANCj4gQW5vdGhlciBkaW1lbnNpb24gb2YgdGhpcyBxdWVzdGlvbiBmb3IgSldTIGFuZCBK
V0UgaXMgdGhhdCBpdOKAmXMgbm90DQo+IGNsZWFyIHRoYXQgdGhlIGZvdXIgdHlwZXMgYXBwbGlj
YXRpb24vandzLCBhcHBsaWNhdGlvbi9qd3MranNvbiwNCj4gYXBwbGljYXRpb24vandlLCBhbmQg
YXBwbGljYXRpb24vandlK2pzb24gYXJlIGV2ZW4gdGhlIHJpZ2h0IG9uZXMuwqAgSXQNCj4gbWln
aHQgYmUgbW9yZSB1c2VmdWwgdG8gaGF2ZSBnZW5lcmljIGFwcGxpY2F0aW9uL2pvc2UgYW5kDQo+
IGFwcGxpY2F0aW9uL2pvc2UranNvbiB0eXBlcywgd2hpY2ggY291bGQgaG9sZCBlaXRoZXIgSldT
IG9yIEpXRSBvYmplY3RzDQo+IHJlc3BlY3RpdmVseSB1c2luZyB0aGUgY29tcGFjdCBvciBKU09O
IHNlcmlhbGl6YXRpb25zIChhbHRob3VnaCBJ4oCZbSBub3QNCj4gYWR2b2NhdGluZyBhZGRpbmcg
dGhlbSBhdCB0aGlzIHRpbWUpLg0KPiANCj4gSGF2aW5nIGRpZmZlcmVudCBKV1MgdmVyc3VzIEpX
RSBNSU1FIHR5cGVzIGFwcGFyZW50bHkgZGlkIGNvbnRyaWJ1dGUgdG8NCj4gYXQgbGVhc3QgRGlj
a+KAmXMgY29uZnVzaW9uIGFib3V0IHRoZSBwdXJwb3NlIG9mIHRoZSDigJx0eXDigJ0gZmllbGQs
IHNvDQo+IGRlbGV0aW5nIHRoZW0gY291bGQgaGVscCBlbGltaW5hdGUgdGhpcyBwb3NzaWJpbGl0
eSBvZiBjb25mdXNpb24gaW4gdGhlDQo+IGZ1dHVyZS7CoCBUaHVzLCBJ4oCZbSBpbmNyZWFzaW5n
bHkgY29udmluY2VkIHdlIHNob3VsZCBnZXQgcmlkIG9mIHRoZSBKV1MNCj4gYW5kIEpXRSB0eXBl
cyBhbmQgbGVhdmUgaXQgdXAgdG8gYXBwbGljYXRpb25zIHRvIGRlZmluZSB0aGUgdHlwZXMgdGhl
eQ0KPiBuZWVkLCB3aGVuIHRoZXkgbmVlZCB0aGVtLg0KPiANCj4gRG8gcGVvcGxlIGhhdmUgdXNl
IGNhc2VzIGZvciB0aGVzZSBmb3VyIE1JTUUgdHlwZXMgbm93IG9yIHNob3VsZCB3ZQ0KPiBsZWF2
ZSB0aGVtIHRvIGZ1dHVyZSBzcGVjcyB0byBkZWZpbmUsIGlmIG5lZWRlZD8NCg0KV2UgYXJlIGRl
ZmluaW5nIGEgZm9ybWF0IGZvciB1c2Ugb24gdGhlIHdlYi4gVGhlIHdlYiBpZGVudGlmaWVzIGZv
cm1hdHMgdmlhIG1lZGlhIHR5cGVzLiBTbyBKT1NFIG5lZWRzIHRvIGRlZmluZSBtZWRpYSB0eXBl
cy4NCg0KLS0NCkphbWVzIE1hbmdlcg0K

From ietf@augustcellars.com  Tue Jun 18 21:48:48 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D679221F9BA6 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 21:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.546
X-Spam-Level: 
X-Spam-Status: No, score=-3.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 031HGXTFi6s9 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 21:48:44 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 224B421F9BA3 for <jose@ietf.org>; Tue, 18 Jun 2013 21:48:44 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 9291D38F1B; Tue, 18 Jun 2013 21:48:43 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Manger, James H'" <James.H.Manger@team.telstra.com>, "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.com>
Date: Tue, 18 Jun 2013 21:47:48 -0700
Message-ID: <03a201ce6ca8$267c50f0$7374f2d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQJdUfWtdvWfIayb6axdJ1IllIJd1wIYXLYBmA3pO1A=
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Jun 2013 04:48:49 -0000

One possible way to do this can be seen in this document  =
http://www.ietf.org/internet-drafts/draft-turner-application-cms-media-ty=
pe-04.txt that is doing much the same thing for CMS.

Jim


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
> Manger, James H
> Sent: Tuesday, June 18, 2013 8:52 PM
> To: Mike Jones; jose@ietf.org
> Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?
>=20
> Good questions, Mike. My (backward compatible) suggestions below.
>=20
> > The JWS and JWE documents currently define these MIME types for the
> > convenience of applications that may want to use them:
> >                 application/jws
> >                 application/jws+json
> >                 application/jwe
> >                 application/jwe+json
>=20
> Drop these.
> Define application/jose and application/jose+json.
>=20
> Allow two optional parameters on these media types:
>=20
>   inner -- indicates the media type of the content of the JOSE =
message, after
> removing 1 or more layers of JOSE protection. For instance, if a JPEG =
image is
> signed with an RSA key, then encrypted with AES-GCM, inner would be
> image/jpeg.
>=20
>   mode -- indicates the sort of protection applied (eg signed, =
encrypted,
> unprotected...). If multiple modes of protection are applied in turn =
(eg
> signed then encrypted) they can all be listed: from the outer-most =
mode to
> the inner-most; separated by a plus (eg mode=3D"enc+sig").
>=20
>=20
> A "mode" media type parameter would be easy to specify if JOSE =
messages
> had a corresponding header field, instead of inferring the sort of =
processing
> from the "alg" value. :-(
>=20
>=20
> Suggestion:
>=20
> 1. Define a header parameter that indicates the sort of processing. =
Its name
> could be "T", or "mode" (just not "typ" as that is too confused).
> [I like "T" (short; stands out as THE primary field in a JOSE =
message), but I use
> "mode" below to be a little less controversial.]
>=20
> 2. Create a registry for "mode" values.
>=20
> 3. Define some initial "mode" values, alongside the spec for that =
processing:
>   "sig1" for digitally signing B64(header).B64(content);
>   "mac1" for MAC over B64(header).B64(content);
>   "enc1" for AEAD, where AAD is B64(header)
>   "none" for unprocessed content
>   "cmp" for compressed (but not protected) content
>   "enc2" for AEAD applied differently (as per the JSON representation)
>   ...
>=20
> 4. Allow the "mode" parameter to be absent if an "alg" value is =
present and
> has a default "mode". This maintains compatibility with JOSE messages =
based
> on previous drafts.
>=20
> 5. Define the default "mode" for existing "alg" values. For instance, =
for
> "alg":"HS256" the default is "mode":"mac1". The registry of alg values =
would
> have a column for the default mode (though new algs can leave that =
column
> blank).
>=20
> 6. Drop the "crit" field. If you are creating a JOSE message with new
> semantics that MUST be understood, just define a new "mode" value. For
> example, to avoid some base64 overhead you could define "mode":"sig2" =
to
> mean digitally sign header||content||len(header).
>=20
> 7. Allow a list of "mode" values to be specified as a parameter on a =
JOSE
> media type.
>=20
>=20
> [probably]
> 8. A plus sign "+" can be appended to any "mode" value to indicate =
that the
> content of this JOSE layer is another JOSE layer. That is, process =
this message
> as per the "mode" without the "+", then process the content as another
> JOSE message.
> [Appending "+" is simpler than "cty":"jws" or "more":true, but assumes =
the
> inner JOSE message uses the same serialization as the outer one.]
>=20
>=20
> End result: simpler, more easily understood by people; one field that =
is
> suitable for an implementation to use to switch to the appropriate =
processing
> code; backward compatible with earlier drafts; clear mechanism for =
making
> changes that MUST-be-understood (that we can be confident code will
> notice).
>=20
>=20
>=20
> > That being said, I m not aware of any uses of these by applications =
at
> > present.
>=20
> Apps such as OpenID Connect could use:
>   application/jose;inner=3Dapplication/jwt+json
>=20
> Apps can still define their own media types for JOSE messages (eg
> application/jwt) though that should not be necessary.
>=20
>=20
> >  Thus, I think that makes it fair game to ask whether we want  to =
keep
> >them or remove them   in which case, if applications ever  needed =
them,
> >they could define them later.
> >
> > Another dimension of this question for JWS and JWE is that it s not
> > clear that the four types application/jws, application/jws+json,
> > application/jwe, and application/jwe+json are even the right ones.  =
It
> > might be more useful to have generic application/jose and
> > application/jose+json types, which could hold either JWS or JWE
> > objects respectively using the compact or JSON serializations
> > (although I m not advocating adding them at this time).
> >
> > Having different JWS versus JWE MIME types apparently did contribute
> > to at least Dick s confusion about the purpose of the  typ  field, =
so
> > deleting them could help eliminate this possibility of confusion in
> > the future.  Thus, I m increasingly convinced we should get rid of =
the
> > JWS and JWE types and leave it up to applications to define the =
types
> > they need, when they need them.
> >
> > Do people have use cases for these four MIME types now or should we
> > leave them to future specs to define, if needed?
>=20
> We are defining a format for use on the web. The web identifies =
formats via
> media types. So JOSE needs to define media types.
>=20
> --
> James Manger
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From Michael.Jones@microsoft.com  Tue Jun 18 22:29:38 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F3D21F9ED6 for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 22:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bz-dpt4RWbiO for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 22:29:33 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id F260E21F9EBC for <jose@ietf.org>; Tue, 18 Jun 2013 22:29:32 -0700 (PDT)
Received: from BN1BFFO11FD010.protection.gbl (10.58.52.200) by BN1AFFO11HUB018.protection.gbl (10.58.52.128) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 19 Jun 2013 05:29:31 +0000
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD010.mail.protection.outlook.com (10.58.53.70) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 19 Jun 2013 05:29:30 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC105.redmond.corp.microsoft.com ([157.54.80.48]) with mapi id 14.03.0136.001; Wed, 19 Jun 2013 05:29:16 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQAAxHXwAAc8BoA=
Date: Wed, 19 Jun 2013 05:29:16 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678738FD@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51704005)(199002)(13464003)(189002)(51444003)(377454003)(50466002)(50986001)(54316002)(56816003)(76786001)(47976001)(74502001)(54356001)(69226001)(47736001)(33656001)(74366001)(55846006)(74706001)(561944002)(53806001)(6806003)(65816001)(76796001)(49866001)(77096001)(47776003)(47446002)(66066001)(46102001)(74662001)(80022001)(79102001)(51856001)(4396001)(31966008)(59766001)(63696002)(81342001)(20776003)(16406001)(81542001)(23676002)(74876001)(76482001)(77982001)(56776001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB018; H:TK5EX14HUBC105.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08828D20BC
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Jun 2013 05:29:38 -0000

U28gd2UgYWdyZWUgdGhhdCBkcm9wcGluZyB0aGUgSldTIGFuZCBKV0UgbWVkaWEgdHlwZXMgaXMg
YSByZWFzb25hYmxlIHRoaW5nIHRvIGRvLg0KDQpBcyBmYXIgYXMgYWRkaW5nIGEgY29tcGxpY2F0
ZWQgbmV3IG1lZGlhIHR5cGUgd2l0aG91dCBhIGNsZWFyIHVzZSBjYXNlIHRvIGRvIHNvLCB3ZSBk
b24ndCBhZ3JlZS4gIFdlJ3JlIG5vdCB0cnlpbmcgdG8gYm9pbCB0aGUgb2NlYW4gaGVyZS4gIFRo
aXMgdGhyZWFkIHdhcyBpbnRlbmRlZCB0byBiZSBhYm91dCBzaW1wbGlmeWluZyB0aGluZ3MgYnkg
cmVtb3ZpbmcgdGhpbmdzIHRoYXQgYXJlbid0IGFjdHVhbGx5IGJlaW5nIHVzZWQgLSBub3QgYWRk
aW5nIG5ldyBjb21wbGljYXRlZCB0aGluZ3MgdGhhdCBhbHNvIGFyZW4ndCBiZWluZyB1c2VkLg0K
DQpGb3IgY29udGV4dCBvbiB5b3VyIHByb3Bvc2FsIGJlbG93LCB5b3UndmUgcHJvcG9zZWQgc2V2
ZXJhbCB0aW1lcyBpbiBzZXZlcmFsIHdheXMgdG8gY29tcGxldGVseSByZXN0cnVjdHVyZSB0aGUg
cHJvY2Vzc2luZyBydWxlcyBmb3IgSldTIGFuZCBKV0UuICBOb25lIG9mIHRob3NlIGhhdmUgZ2Fp
bmVkIHRyYWN0aW9uIHdpdGggdGhlIHdvcmtpbmcgZ3JvdXAgdG8gZGF0ZS4gIFlvdXIgcHJvcG9z
YWwgYmVsb3cgc2VlbXMgdG8gYmUgbW9yZSBvZiB0aGUgc2FtZSAtIGF0IGxlYXN0IHRvIG1lLg0K
DQpPbmUgb2YgdGhlIHByb2JsZW1zIHRoaXMgd291bGQgY3JlYXRlIHdvdWxkIGJlIGhhdmluZyBt
dWx0aXBsZSB3YXlzIG9mIGluZGljYXRpbmcgd2hldGhlciB0aGUgb2JqZWN0IGlzIGEgSldTIG9y
IEpXRSAtIGJvdGggdGhlICJhbGciIHZhbHVlIGFuZCB0aGUgYWRkaXRpb25hbCB2YWx1ZXMgeW91
IHByb3Bvc2UuICBBIHByb2JsZW0gd2l0aCBzdWNoIGR1cGxpY2F0aW9uIGlzIHRoYXQgaXQgY3Jl
YXRlcyBuZXcgZXJyb3IgY29uZGl0aW9ucyB0byBoYW5kbGUuICBGb3IgaW5zdGFuY2UsIHdoYXQg
aWYgeW91ciBuZXcgcGFyYW1ldGVycyBzYWlkIHRoYXQgdGhlIGNvbnRlbnQgd2FzIGEgSldTIGJ1
dCB0aGUgY29udGVudCB3YXMgYWN0dWFsbHkgYSBKV0U/ICBUaGF0J3MgYSBuZXcgZXJyb3IgY29u
ZGl0aW9uIHRoYXQgcnVsZXMgd291bGQgaGF2ZSB0byBiZSBzcGVjaWZpZWQgdG8gaGFuZGxlLiAg
SXQgc2VlbXMgYmV0dGVyIHRvIGhhdmUgb25lIHdheSBvZiBkZXRlcm1pbmluZyB0aGlzLCByYXRo
ZXIgbXVsdGlwbGUgd2F5cyB0aGF0IG1pZ2h0IGNvbmZsaWN0Lg0KDQpXaXRob3V0IGEgY2xlYXIg
dXNlIGNhc2UgZm9yIGFkZGluZyB0aGUgY29tcGxpY2F0ZWQgbWVkaWEgdHlwZSB5b3UgZGVzY3Jp
YmUgYmVsb3cgd2hpY2ggc2VlbXMgZmFyIGZyb20gbWluaW1hbCwgaW5jbHVkaW5nIHNheWluZyB3
aHkgaXRzIGdvYWxzIGNhbid0IGJlIGFjY29tcGxpc2hlZCB3aXRoIHdoYXQgYWxyZWFkeSBleGlz
dHMsIEkgZG9uJ3QgdGhpbmsgaXQgbWFrZXMgc2Vuc2UuICBNeSB2aWV3LCBhbnl3YXkuLi4NCg0K
CQkJCS0tIE1pa2UNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGpvc2UtYm91
bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m
IE1hbmdlciwgSmFtZXMgSA0KU2VudDogVHVlc2RheSwgSnVuZSAxOCwgMjAxMyA4OjUyIFBNDQpU
bzogTWlrZSBKb25lczsgam9zZUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtqb3NlXSBTaG91bGQg
d2Uga2VlcCBvciByZW1vdmUgdGhlIEpPU0UgSldTIGFuZCBKV0UgTUlNRSB0eXBlcz8NCg0KR29v
ZCBxdWVzdGlvbnMsIE1pa2UuIE15IChiYWNrd2FyZCBjb21wYXRpYmxlKSBzdWdnZXN0aW9ucyBi
ZWxvdy4NCg0KPiBUaGUgSldTIGFuZCBKV0UgZG9jdW1lbnRzIGN1cnJlbnRseSBkZWZpbmUgdGhl
c2UgTUlNRSB0eXBlcyBmb3IgdGhlIA0KPiBjb252ZW5pZW5jZSBvZiBhcHBsaWNhdGlvbnMgdGhh
dCBtYXkgd2FudCB0byB1c2UgdGhlbToNCj4gwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
IGFwcGxpY2F0aW9uL2p3cw0KPiDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgYXBwbGlj
YXRpb24vandzK2pzb24NCj4gwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIGFwcGxpY2F0
aW9uL2p3ZQ0KPiDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgYXBwbGljYXRpb24vandl
K2pzb24NCg0KRHJvcCB0aGVzZS4NCkRlZmluZSBhcHBsaWNhdGlvbi9qb3NlIGFuZCBhcHBsaWNh
dGlvbi9qb3NlK2pzb24uDQoNCkFsbG93IHR3byBvcHRpb25hbCBwYXJhbWV0ZXJzIG9uIHRoZXNl
IG1lZGlhIHR5cGVzOg0KDQogIGlubmVyIC0tIGluZGljYXRlcyB0aGUgbWVkaWEgdHlwZSBvZiB0
aGUgY29udGVudCBvZiB0aGUgSk9TRSBtZXNzYWdlLCBhZnRlciByZW1vdmluZyAxIG9yIG1vcmUg
bGF5ZXJzIG9mIEpPU0UgcHJvdGVjdGlvbi4gRm9yIGluc3RhbmNlLCBpZiBhIEpQRUcgaW1hZ2Ug
aXMgc2lnbmVkIHdpdGggYW4gUlNBIGtleSwgdGhlbiBlbmNyeXB0ZWQgd2l0aCBBRVMtR0NNLCBp
bm5lciB3b3VsZCBiZSBpbWFnZS9qcGVnLg0KDQogIG1vZGUgLS0gaW5kaWNhdGVzIHRoZSBzb3J0
IG9mIHByb3RlY3Rpb24gYXBwbGllZCAoZWcgc2lnbmVkLCBlbmNyeXB0ZWQsIHVucHJvdGVjdGVk
Li4uKS4gSWYgbXVsdGlwbGUgbW9kZXMgb2YgcHJvdGVjdGlvbiBhcmUgYXBwbGllZCBpbiB0dXJu
IChlZyBzaWduZWQgdGhlbiBlbmNyeXB0ZWQpIHRoZXkgY2FuIGFsbCBiZSBsaXN0ZWQ6IGZyb20g
dGhlIG91dGVyLW1vc3QgbW9kZSB0byB0aGUgaW5uZXItbW9zdDsgc2VwYXJhdGVkIGJ5IGEgcGx1
cyAoZWcgbW9kZT0iZW5jK3NpZyIpLg0KDQoNCkEgIm1vZGUiIG1lZGlhIHR5cGUgcGFyYW1ldGVy
IHdvdWxkIGJlIGVhc3kgdG8gc3BlY2lmeSBpZiBKT1NFIG1lc3NhZ2VzIGhhZCBhIGNvcnJlc3Bv
bmRpbmcgaGVhZGVyIGZpZWxkLCBpbnN0ZWFkIG9mIGluZmVycmluZyB0aGUgc29ydCBvZiBwcm9j
ZXNzaW5nIGZyb20gdGhlICJhbGciIHZhbHVlLiA6LSgNCg0KDQpTdWdnZXN0aW9uOg0KDQoxLiBE
ZWZpbmUgYSBoZWFkZXIgcGFyYW1ldGVyIHRoYXQgaW5kaWNhdGVzIHRoZSBzb3J0IG9mIHByb2Nl
c3NpbmcuIEl0cyBuYW1lIGNvdWxkIGJlICJUIiwgb3IgIm1vZGUiIChqdXN0IG5vdCAidHlwIiBh
cyB0aGF0IGlzIHRvbyBjb25mdXNlZCkuDQpbSSBsaWtlICJUIiAoc2hvcnQ7IHN0YW5kcyBvdXQg
YXMgVEhFIHByaW1hcnkgZmllbGQgaW4gYSBKT1NFIG1lc3NhZ2UpLCBidXQgSSB1c2UgIm1vZGUi
IGJlbG93IHRvIGJlIGEgbGl0dGxlIGxlc3MgY29udHJvdmVyc2lhbC5dDQoNCjIuIENyZWF0ZSBh
IHJlZ2lzdHJ5IGZvciAibW9kZSIgdmFsdWVzLg0KDQozLiBEZWZpbmUgc29tZSBpbml0aWFsICJt
b2RlIiB2YWx1ZXMsIGFsb25nc2lkZSB0aGUgc3BlYyBmb3IgdGhhdCBwcm9jZXNzaW5nOg0KICAi
c2lnMSIgZm9yIGRpZ2l0YWxseSBzaWduaW5nIEI2NChoZWFkZXIpLkI2NChjb250ZW50KTsNCiAg
Im1hYzEiIGZvciBNQUMgb3ZlciBCNjQoaGVhZGVyKS5CNjQoY29udGVudCk7DQogICJlbmMxIiBm
b3IgQUVBRCwgd2hlcmUgQUFEIGlzIEI2NChoZWFkZXIpDQogICJub25lIiBmb3IgdW5wcm9jZXNz
ZWQgY29udGVudA0KICAiY21wIiBmb3IgY29tcHJlc3NlZCAoYnV0IG5vdCBwcm90ZWN0ZWQpIGNv
bnRlbnQNCiAgImVuYzIiIGZvciBBRUFEIGFwcGxpZWQgZGlmZmVyZW50bHkgKGFzIHBlciB0aGUg
SlNPTiByZXByZXNlbnRhdGlvbikNCiAgLi4uDQoNCjQuIEFsbG93IHRoZSAibW9kZSIgcGFyYW1l
dGVyIHRvIGJlIGFic2VudCBpZiBhbiAiYWxnIiB2YWx1ZSBpcyBwcmVzZW50IGFuZCBoYXMgYSBk
ZWZhdWx0ICJtb2RlIi4gVGhpcyBtYWludGFpbnMgY29tcGF0aWJpbGl0eSB3aXRoIEpPU0UgbWVz
c2FnZXMgYmFzZWQgb24gcHJldmlvdXMgZHJhZnRzLg0KDQo1LiBEZWZpbmUgdGhlIGRlZmF1bHQg
Im1vZGUiIGZvciBleGlzdGluZyAiYWxnIiB2YWx1ZXMuIEZvciBpbnN0YW5jZSwgZm9yICJhbGci
OiJIUzI1NiIgdGhlIGRlZmF1bHQgaXMgIm1vZGUiOiJtYWMxIi4gVGhlIHJlZ2lzdHJ5IG9mIGFs
ZyB2YWx1ZXMgd291bGQgaGF2ZSBhIGNvbHVtbiBmb3IgdGhlIGRlZmF1bHQgbW9kZSAodGhvdWdo
IG5ldyBhbGdzIGNhbiBsZWF2ZSB0aGF0IGNvbHVtbiBibGFuaykuDQoNCjYuIERyb3AgdGhlICJj
cml0IiBmaWVsZC4gSWYgeW91IGFyZSBjcmVhdGluZyBhIEpPU0UgbWVzc2FnZSB3aXRoIG5ldyBz
ZW1hbnRpY3MgdGhhdCBNVVNUIGJlIHVuZGVyc3Rvb2QsIGp1c3QgZGVmaW5lIGEgbmV3ICJtb2Rl
IiB2YWx1ZS4gRm9yIGV4YW1wbGUsIHRvIGF2b2lkIHNvbWUgYmFzZTY0IG92ZXJoZWFkIHlvdSBj
b3VsZCBkZWZpbmUgIm1vZGUiOiJzaWcyIiB0byBtZWFuIGRpZ2l0YWxseSBzaWduIGhlYWRlcnx8
Y29udGVudHx8bGVuKGhlYWRlcikuDQoNCjcuIEFsbG93IGEgbGlzdCBvZiAibW9kZSIgdmFsdWVz
IHRvIGJlIHNwZWNpZmllZCBhcyBhIHBhcmFtZXRlciBvbiBhIEpPU0UgbWVkaWEgdHlwZS4NCg0K
DQpbcHJvYmFibHldDQo4LiBBIHBsdXMgc2lnbiAiKyIgY2FuIGJlIGFwcGVuZGVkIHRvIGFueSAi
bW9kZSIgdmFsdWUgdG8gaW5kaWNhdGUgdGhhdCB0aGUgY29udGVudCBvZiB0aGlzIEpPU0UgbGF5
ZXIgaXMgYW5vdGhlciBKT1NFIGxheWVyLiBUaGF0IGlzLCBwcm9jZXNzIHRoaXMgbWVzc2FnZSBh
cyBwZXIgdGhlICJtb2RlIiB3aXRob3V0IHRoZSAiKyIsIHRoZW4gcHJvY2VzcyB0aGUgY29udGVu
dCBhcyBhbm90aGVyIEpPU0UgbWVzc2FnZS4NCltBcHBlbmRpbmcgIisiIGlzIHNpbXBsZXIgdGhh
biAiY3R5IjoiandzIiBvciAibW9yZSI6dHJ1ZSwgYnV0IGFzc3VtZXMgdGhlIGlubmVyIEpPU0Ug
bWVzc2FnZSB1c2VzIHRoZSBzYW1lIHNlcmlhbGl6YXRpb24gYXMgdGhlIG91dGVyIG9uZS5dDQoN
Cg0KRW5kIHJlc3VsdDogc2ltcGxlciwgbW9yZSBlYXNpbHkgdW5kZXJzdG9vZCBieSBwZW9wbGU7
IG9uZSBmaWVsZCB0aGF0IGlzIHN1aXRhYmxlIGZvciBhbiBpbXBsZW1lbnRhdGlvbiB0byB1c2Ug
dG8gc3dpdGNoIHRvIHRoZSBhcHByb3ByaWF0ZSBwcm9jZXNzaW5nIGNvZGU7IGJhY2t3YXJkIGNv
bXBhdGlibGUgd2l0aCBlYXJsaWVyIGRyYWZ0czsgY2xlYXIgbWVjaGFuaXNtIGZvciBtYWtpbmcg
Y2hhbmdlcyB0aGF0IE1VU1QtYmUtdW5kZXJzdG9vZCAodGhhdCB3ZSBjYW4gYmUgY29uZmlkZW50
IGNvZGUgd2lsbCBub3RpY2UpLg0KDQoNCg0KPiBUaGF0IGJlaW5nIHNhaWQsIEnigJltIG5vdCBh
d2FyZSBvZiBhbnkgdXNlcyBvZiB0aGVzZSBieSBhcHBsaWNhdGlvbnMgYXQgDQo+IHByZXNlbnQu
DQoNCkFwcHMgc3VjaCBhcyBPcGVuSUQgQ29ubmVjdCBjb3VsZCB1c2U6DQogIGFwcGxpY2F0aW9u
L2pvc2U7aW5uZXI9YXBwbGljYXRpb24vand0K2pzb24NCg0KQXBwcyBjYW4gc3RpbGwgZGVmaW5l
IHRoZWlyIG93biBtZWRpYSB0eXBlcyBmb3IgSk9TRSBtZXNzYWdlcyAoZWcgYXBwbGljYXRpb24v
and0KSB0aG91Z2ggdGhhdCBzaG91bGQgbm90IGJlIG5lY2Vzc2FyeS4NCg0KDQo+wqAgVGh1cywg
SSB0aGluayB0aGF0IG1ha2VzIGl0IGZhaXIgZ2FtZSB0byBhc2sgd2hldGhlciB3ZSB3YW50ICB0
byBrZWVwIA0KPnRoZW0gb3IgcmVtb3ZlIHRoZW0g4oCTIGluIHdoaWNoIGNhc2UsIGlmIGFwcGxp
Y2F0aW9ucyBldmVyICBuZWVkZWQgdGhlbSwgDQo+dGhleSBjb3VsZCBkZWZpbmUgdGhlbSBsYXRl
ci4NCj4gDQo+IEFub3RoZXIgZGltZW5zaW9uIG9mIHRoaXMgcXVlc3Rpb24gZm9yIEpXUyBhbmQg
SldFIGlzIHRoYXQgaXTigJlzIG5vdCANCj4gY2xlYXIgdGhhdCB0aGUgZm91ciB0eXBlcyBhcHBs
aWNhdGlvbi9qd3MsIGFwcGxpY2F0aW9uL2p3cytqc29uLCANCj4gYXBwbGljYXRpb24vandlLCBh
bmQgYXBwbGljYXRpb24vandlK2pzb24gYXJlIGV2ZW4gdGhlIHJpZ2h0IG9uZXMuwqAgSXQgDQo+
IG1pZ2h0IGJlIG1vcmUgdXNlZnVsIHRvIGhhdmUgZ2VuZXJpYyBhcHBsaWNhdGlvbi9qb3NlIGFu
ZCANCj4gYXBwbGljYXRpb24vam9zZStqc29uIHR5cGVzLCB3aGljaCBjb3VsZCBob2xkIGVpdGhl
ciBKV1Mgb3IgSldFIA0KPiBvYmplY3RzIHJlc3BlY3RpdmVseSB1c2luZyB0aGUgY29tcGFjdCBv
ciBKU09OIHNlcmlhbGl6YXRpb25zIA0KPiAoYWx0aG91Z2ggSeKAmW0gbm90IGFkdm9jYXRpbmcg
YWRkaW5nIHRoZW0gYXQgdGhpcyB0aW1lKS4NCj4gDQo+IEhhdmluZyBkaWZmZXJlbnQgSldTIHZl
cnN1cyBKV0UgTUlNRSB0eXBlcyBhcHBhcmVudGx5IGRpZCBjb250cmlidXRlIA0KPiB0byBhdCBs
ZWFzdCBEaWNr4oCZcyBjb25mdXNpb24gYWJvdXQgdGhlIHB1cnBvc2Ugb2YgdGhlIOKAnHR5cOKA
nSBmaWVsZCwgc28gDQo+IGRlbGV0aW5nIHRoZW0gY291bGQgaGVscCBlbGltaW5hdGUgdGhpcyBw
b3NzaWJpbGl0eSBvZiBjb25mdXNpb24gaW4gDQo+IHRoZSBmdXR1cmUuwqAgVGh1cywgSeKAmW0g
aW5jcmVhc2luZ2x5IGNvbnZpbmNlZCB3ZSBzaG91bGQgZ2V0IHJpZCBvZiB0aGUgDQo+IEpXUyBh
bmQgSldFIHR5cGVzIGFuZCBsZWF2ZSBpdCB1cCB0byBhcHBsaWNhdGlvbnMgdG8gZGVmaW5lIHRo
ZSB0eXBlcyANCj4gdGhleSBuZWVkLCB3aGVuIHRoZXkgbmVlZCB0aGVtLg0KPiANCj4gRG8gcGVv
cGxlIGhhdmUgdXNlIGNhc2VzIGZvciB0aGVzZSBmb3VyIE1JTUUgdHlwZXMgbm93IG9yIHNob3Vs
ZCB3ZSANCj4gbGVhdmUgdGhlbSB0byBmdXR1cmUgc3BlY3MgdG8gZGVmaW5lLCBpZiBuZWVkZWQ/
DQoNCldlIGFyZSBkZWZpbmluZyBhIGZvcm1hdCBmb3IgdXNlIG9uIHRoZSB3ZWIuIFRoZSB3ZWIg
aWRlbnRpZmllcyBmb3JtYXRzIHZpYSBtZWRpYSB0eXBlcy4gU28gSk9TRSBuZWVkcyB0byBkZWZp
bmUgbWVkaWEgdHlwZXMuDQoNCi0tDQpKYW1lcyBNYW5nZXINCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQpqb3NlIG1haWxpbmcgbGlzdA0Kam9zZUBpZXRm
Lm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9qb3NlDQo=

From James.H.Manger@team.telstra.com  Tue Jun 18 23:20:58 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2757521F972C for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 23:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.654
X-Spam-Level: 
X-Spam-Status: No, score=-0.654 tagged_above=-999 required=5 tests=[AWL=0.247,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eV-5ehlPfPOb for <jose@ietfa.amsl.com>; Tue, 18 Jun 2013 23:20:52 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 1792B21F9928 for <jose@ietf.org>; Tue, 18 Jun 2013 23:20:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,895,1363093200"; d="scan'208";a="142397451"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipocvi.tcif.telstra.com.au with ESMTP; 19 Jun 2013 16:20:47 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7110"; a="139774339"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipccvi.tcif.telstra.com.au with ESMTP; 19 Jun 2013 16:20:47 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Wed, 19 Jun 2013 16:20:46 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Date: Wed, 19 Jun 2013 16:20:45 +1000
Thread-Topic: Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQAAxHXwAAc8BoAAAJhEYA==
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BA6ABB8@WSMSG3153V.srv.dir.telstra.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E1151BA6A75E@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678738FD@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678738FD@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Jun 2013 06:20:58 -0000

PiBTbyB3ZSBhZ3JlZSB0aGF0IGRyb3BwaW5nIHRoZSBKV1MgYW5kIEpXRSBtZWRpYSB0eXBlcyBp
cyBhIHJlYXNvbmFibGUNCj4gdGhpbmcgdG8gZG8uDQoNCipSZXBsYWNpbmcqIHRoZW0gd2l0aCBh
IEpPU0UgbWVkaWEgdHlwZSBpcyBhIHJlYXNvbmFibGUgdGhpbmcgdG8gZG8uDQoNCj4gQXMgZmFy
IGFzIGFkZGluZyBhIGNvbXBsaWNhdGVkIG5ldyBtZWRpYSB0eXBlIHdpdGhvdXQgYSBjbGVhciB1
c2UgY2FzZQ0KPiB0byBkbyBzbywgd2UgZG9uJ3QgYWdyZWUuICBXZSdyZSBub3QgdHJ5aW5nIHRv
IGJvaWwgdGhlIG9jZWFuIGhlcmUuDQoNClRoZSB3ZWIgd29ya3MgYnkgbGFiZWxsaW5nIGVhY2gg
ZGF0YSBmb3JtYXQgd2l0aCBhIG1lZGlhIHR5cGUuDQpJIGRvbid0IHdhbnQgdG8gYm9pbCB0aGUg
b2NlYW4uIEkgd2FudCB0byB3b3JrIHdpdGggdGhlIHdlYi4NCg0KPiBUaGlzIHRocmVhZCB3YXMg
aW50ZW5kZWQgdG8gYmUgYWJvdXQgc2ltcGxpZnlpbmcgdGhpbmdzIGJ5IHJlbW92aW5nDQo+IHRo
aW5ncyB0aGF0IGFyZW4ndCBhY3R1YWxseSBiZWluZyB1c2VkIC0gbm90IGFkZGluZyBuZXcgY29t
cGxpY2F0ZWQNCj4gdGhpbmdzIHRoYXQgYWxzbyBhcmVuJ3QgYmVpbmcgdXNlZC4NCg0KVGhlIG9u
bHkgcmVhc29uIGEgSk9TRSBtZWRpYSB0eXBlIGlzIG5vdCBiZWluZyB1c2VkIGlzIHRoYXQgSldU
IGRlZmluZWQgaXRzIG93biBtZWRpYSB0eXBlLCBwcm9iYWJseSBiZWNhdXNlIG5vIHN1aXRhYmxl
IEpPU0UgbWVkaWEgdHlwZSBleGlzdGVkLg0KDQpBcyBhbiBhbmFsb2d5LCBpZiBhcHBsaWNhdGlv
bi9qc29uIHdhcyBub3QgZGVmaW5lZCBldmVyeSBhcHAgdXNpbmcgSlNPTiB3b3VsZCBuZWVkIHRv
IGRlZmluZSBhbiBhcHAtc3BlY2lmaWMgbWVkaWEgdHlwZS4gSW4gcHJhY3RpY2UsIGFwcGxpY2F0
aW9uL2pzb24gaXMgY29udmVuaWVudCBpbiBtYW55IHNpdHVhdGlvbnMuDQoNCj4gRm9yIGNvbnRl
eHQgb24geW91ciBwcm9wb3NhbCBiZWxvdywgeW91J3ZlIHByb3Bvc2VkIHNldmVyYWwgdGltZXMg
aW4NCj4gc2V2ZXJhbCB3YXlzIHRvIGNvbXBsZXRlbHkgcmVzdHJ1Y3R1cmUgdGhlIHByb2Nlc3Np
bmcgcnVsZXMgZm9yIEpXUyBhbmQNCj4gSldFLiAgTm9uZSBvZiB0aG9zZSBoYXZlIGdhaW5lZCB0
cmFjdGlvbiB3aXRoIHRoZSB3b3JraW5nIGdyb3VwIHRvDQo+IGRhdGUuICBZb3VyIHByb3Bvc2Fs
IGJlbG93IHNlZW1zIHRvIGJlIG1vcmUgb2YgdGhlIHNhbWUgLSBhdCBsZWFzdCB0bw0KPiBtZS4N
Cg0KVGhlICJ0eXAiIGZpYXNjbyBzaG93ZWQgbWFueSBvdGhlcnMgYWxzbyB3YW50IGEgd2F5IHRv
IGluZGljYXRlIHRoZSAibW9kZSIgb2YgYSBKT1NFIG1lc3NhZ2UuDQoNCj4gT25lIG9mIHRoZSBw
cm9ibGVtcyB0aGlzIHdvdWxkIGNyZWF0ZSB3b3VsZCBiZSBoYXZpbmcgbXVsdGlwbGUgd2F5cyBv
Zg0KPiBpbmRpY2F0aW5nIHdoZXRoZXIgdGhlIG9iamVjdCBpcyBhIEpXUyBvciBKV0UgLSBib3Ro
IHRoZSAiYWxnIiB2YWx1ZQ0KPiBhbmQgdGhlIGFkZGl0aW9uYWwgdmFsdWVzIHlvdSBwcm9wb3Nl
Lg0KDQpBcyBvcHBvc2VkIHRvIHRoZSBtdWx0aXBsZSB3YXlzIHRvZGF5IC0gYm90aCB0aGUgImFs
ZyIgdmFsdWUgYW5kIHRoZSBwcmVzZW5jZS9hYnNlbmNlIG9mICJlbmMiLg0KDQpNeSBwcm9wb3Nh
bCBkZWZpbmVzIDEgZGV0ZXJtaW5pc3RpYyB3YXkgKGllICJtb2RlIiB0YWtlcyBwcmVjZWRlbmNl
KToNCg0KICBNb2RlID0gaGVhZGVyLmdldCgibW9kZSkNCiAgSWYgbW9kZSA9PT0gdW5kZWZpbmVk
IHRoZW4NCiAgICBBbGcgPSBoZWFkZXIuZ2V0KCJhbGciKQ0KICAgIE1vZGUgPSBUQUJMRV9PRl9B
TEdTLmdldChhbGcpLmdldCgibW9kZSIpDQogIEVuZElmDQogIFN3aXRjaCAobW9kZSkNCiAgICBD
YXNlICJzaWcxIiAuLi52ZXJpZnkgc2lnbmF0dXJlLi4uDQogICAgQ2FzZSAiZW5jMSIgLi4uZGVj
cnlwdC4uLg0KICAgIERlZmF1bHQgLi4uRVJST1I6IHVuc3VwcG9ydGVkIG1lc3NhZ2UuLi4NCiAg
RW5kU3dpdGNoDQoNCj4gIEEgcHJvYmxlbSB3aXRoIHN1Y2ggZHVwbGljYXRpb24NCj4gaXMgdGhh
dCBpdCBjcmVhdGVzIG5ldyBlcnJvciBjb25kaXRpb25zIHRvIGhhbmRsZS4gIEZvciBpbnN0YW5j
ZSwgd2hhdA0KPiBpZiB5b3VyIG5ldyBwYXJhbWV0ZXJzIHNhaWQgdGhhdCB0aGUgY29udGVudCB3
YXMgYSBKV1MgYnV0IHRoZSBjb250ZW50DQo+IHdhcyBhY3R1YWxseSBhIEpXRT8NCg0KeyJtb2Rl
Ijoic2lnMSIsICJhbGciOiJFQ0RILUVTIn0NCiJtb2RlIiBpcyAic2lnMSIgc28gdGhlIHJlY2lw
aWVudCB0cmllcyB0byB2ZXJpZnkgYSBzaWduYXR1cmUsIGJ1dCBmYWlscyBiZWNhdXNlIHRoZSAi
YWxnIiB2YWx1ZSBpc24ndCBhIHNpZ25hdHVyZSBhbGdvcml0aG0uIFRyaXZpYWwuDQoNCk5vdCBt
dWNoIGRpZmZlcmVudCBmcm9tIGEgZHJhZnQtMTEgbWVzc2FnZSB0aGF0IGhhcyB7ImFsZyI6IkhT
MjU2IiwgImVuYyI6IkEyNTZHQ00ifS4NCg0KQWN0dWFsbHksIG15IHByb3Bvc2FsIGlzIG11Y2gg
YmV0dGVyLiBXaXRoIGRyYWZ0LTExLCBoYWxmIHRoZSByZWNpcGllbnRzIHdpbGwgcHJvY2VzcyB0
aGlzIGFzIGEgSldTIChiYXNlZCBvbiAiYWxnIiksIHRoZSBvdGhlciBoYWxmIHdpbGwgcHJvY2Vz
cyB0aGlzIGFzIGEgSldFIChiYXNlZCBvbiAiZW5jIikgc28gd2hvIGtub3dzIHdoYXQgd2lsbCBo
YXBwZW4uDQoNCj4gIFRoYXQncyBhIG5ldyBlcnJvciBjb25kaXRpb24gdGhhdCBydWxlcyB3b3Vs
ZCBoYXZlDQo+IHRvIGJlIHNwZWNpZmllZCB0byBoYW5kbGUuDQoNCkRyYWZ0LTExIGRvZXNuJ3Qg
c3BlY2lmeSBydWxlcyBmb3IgaGFuZGxpbmcgeyJhbGciOiJIUzI1NiIsICJlbmMiOiJBMjU2R0NN
In0uIEl0IG1lcmVseSBpbXBsaWVzIGl0IGNhbm5vdCBvY2N1ciBmb3IgbGVnYWwgaW5wdXQgdmFs
dWVzIC0tIG5vIGRpZmZlcmVudCB0aGFuICJtb2RlIiBhbmQgImFsZyIgY29udHJhZGljdGluZyBl
YWNoIG90aGVyLg0KDQo+IEl0IHNlZW1zIGJldHRlciB0byBoYXZlIG9uZSB3YXkgb2YNCj4gZGV0
ZXJtaW5pbmcgdGhpcywgcmF0aGVyIG11bHRpcGxlIHdheXMgdGhhdCBtaWdodCBjb25mbGljdC4N
Cg0KQWdyZWUuIE15IHByb3Bvc2FsIGdpdmVzIDEgd2F5ICh0aGF0IGludm9sdmVzIDIgc3RlcHMg
dG8gYWlkIGJhY2t3YXJkIGNvbXBhdGliaWxpdHkpLg0KDQo+IFdpdGhvdXQgYSBjbGVhciB1c2Ug
Y2FzZSBmb3IgYWRkaW5nIHRoZSBjb21wbGljYXRlZCBtZWRpYSB0eXBlIHlvdQ0KPiBkZXNjcmli
ZSBiZWxvdyB3aGljaCBzZWVtcyBmYXIgZnJvbSBtaW5pbWFsLCBpbmNsdWRpbmcgc2F5aW5nIHdo
eSBpdHMNCj4gZ29hbHMgY2FuJ3QgYmUgYWNjb21wbGlzaGVkIHdpdGggd2hhdCBhbHJlYWR5IGV4
aXN0cywgSSBkb24ndCB0aGluayBpdA0KPiBtYWtlcyBzZW5zZS4gIE15IHZpZXcsIGFueXdheS4u
Lg0KDQpJZiB0aGUgSk9TRSBncm91cCBkZWNpZGVzIG1lZGlhIHR5cGUgcGFyYW1ldGVycyBhcmUg
dG9vIGNvbXBsaWNhdGVkIEkgY291bGQgbGl2ZSB3aXRoIGp1c3QgYXBwbGljYXRpb24vam9zZSBh
bmQgYXBwbGljYXRpb24vam9zZStqc29uLiBFdmVuIHRoYXQgd291bGQgYmUgbXVjaCBiZXR0ZXIg
dGhhbiB0aGUgY3VycmVudCBKV0UvSldTL0pXVCBtZWRpYSB0eXBlcy4gSSB0aGluayAiaW5uZXIi
IGFuZCAibW9kZSIgbWVkaWEgdHlwZSBwYXJhbWV0ZXJzIGFkZCB2YWx1ZS4NCg0KLS0NCkphbWVz
IE1hbmdlcg0KDQoNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBqb3Nl
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZg0KPiBNYW5nZXIsIEphbWVzIEgNCj4gU2VudDogVHVlc2RheSwgSnVuZSAxOCwgMjAxMyA4
OjUyIFBNDQo+IFRvOiBNaWtlIEpvbmVzOyBqb3NlQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBb
am9zZV0gU2hvdWxkIHdlIGtlZXAgb3IgcmVtb3ZlIHRoZSBKT1NFIEpXUyBhbmQgSldFIE1JTUUN
Cj4gdHlwZXM/DQo+IA0KPiBHb29kIHF1ZXN0aW9ucywgTWlrZS4gTXkgKGJhY2t3YXJkIGNvbXBh
dGlibGUpIHN1Z2dlc3Rpb25zIGJlbG93Lg0KPiANCj4gPiBUaGUgSldTIGFuZCBKV0UgZG9jdW1l
bnRzIGN1cnJlbnRseSBkZWZpbmUgdGhlc2UgTUlNRSB0eXBlcyBmb3IgdGhlDQo+ID4gY29udmVu
aWVuY2Ugb2YgYXBwbGljYXRpb25zIHRoYXQgbWF5IHdhbnQgdG8gdXNlIHRoZW06DQo+ID4gwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIGFwcGxpY2F0aW9uL2p3cw0KPiA+IMKgwqDCoMKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBsaWNhdGlvbi9qd3MranNvbg0KPiA+IMKgwqDCoMKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBsaWNhdGlvbi9qd2UNCj4gPiDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqAgYXBwbGljYXRpb24vandlK2pzb24NCj4gDQo+IERyb3AgdGhlc2Uu
DQo+IERlZmluZSBhcHBsaWNhdGlvbi9qb3NlIGFuZCBhcHBsaWNhdGlvbi9qb3NlK2pzb24uDQo+
IA0KPiBBbGxvdyB0d28gb3B0aW9uYWwgcGFyYW1ldGVycyBvbiB0aGVzZSBtZWRpYSB0eXBlczoN
Cj4gDQo+ICAgaW5uZXIgLS0gaW5kaWNhdGVzIHRoZSBtZWRpYSB0eXBlIG9mIHRoZSBjb250ZW50
IG9mIHRoZSBKT1NFIG1lc3NhZ2UsDQo+IGFmdGVyIHJlbW92aW5nIDEgb3IgbW9yZSBsYXllcnMg
b2YgSk9TRSBwcm90ZWN0aW9uLiBGb3IgaW5zdGFuY2UsIGlmIGENCj4gSlBFRyBpbWFnZSBpcyBz
aWduZWQgd2l0aCBhbiBSU0Ega2V5LCB0aGVuIGVuY3J5cHRlZCB3aXRoIEFFUy1HQ00sDQo+IGlu
bmVyIHdvdWxkIGJlIGltYWdlL2pwZWcuDQo+IA0KPiAgIG1vZGUgLS0gaW5kaWNhdGVzIHRoZSBz
b3J0IG9mIHByb3RlY3Rpb24gYXBwbGllZCAoZWcgc2lnbmVkLA0KPiBlbmNyeXB0ZWQsIHVucHJv
dGVjdGVkLi4uKS4gSWYgbXVsdGlwbGUgbW9kZXMgb2YgcHJvdGVjdGlvbiBhcmUgYXBwbGllZA0K
PiBpbiB0dXJuIChlZyBzaWduZWQgdGhlbiBlbmNyeXB0ZWQpIHRoZXkgY2FuIGFsbCBiZSBsaXN0
ZWQ6IGZyb20gdGhlDQo+IG91dGVyLW1vc3QgbW9kZSB0byB0aGUgaW5uZXItbW9zdDsgc2VwYXJh
dGVkIGJ5IGEgcGx1cyAoZWcNCj4gbW9kZT0iZW5jK3NpZyIpLg0KPiANCj4gDQo+IEEgIm1vZGUi
IG1lZGlhIHR5cGUgcGFyYW1ldGVyIHdvdWxkIGJlIGVhc3kgdG8gc3BlY2lmeSBpZiBKT1NFIG1l
c3NhZ2VzDQo+IGhhZCBhIGNvcnJlc3BvbmRpbmcgaGVhZGVyIGZpZWxkLCBpbnN0ZWFkIG9mIGlu
ZmVycmluZyB0aGUgc29ydCBvZg0KPiBwcm9jZXNzaW5nIGZyb20gdGhlICJhbGciIHZhbHVlLiA6
LSgNCj4gDQo+IA0KPiBTdWdnZXN0aW9uOg0KPiANCj4gMS4gRGVmaW5lIGEgaGVhZGVyIHBhcmFt
ZXRlciB0aGF0IGluZGljYXRlcyB0aGUgc29ydCBvZiBwcm9jZXNzaW5nLiBJdHMNCj4gbmFtZSBj
b3VsZCBiZSAiVCIsIG9yICJtb2RlIiAoanVzdCBub3QgInR5cCIgYXMgdGhhdCBpcyB0b28gY29u
ZnVzZWQpLg0KPiBbSSBsaWtlICJUIiAoc2hvcnQ7IHN0YW5kcyBvdXQgYXMgVEhFIHByaW1hcnkg
ZmllbGQgaW4gYSBKT1NFIG1lc3NhZ2UpLA0KPiBidXQgSSB1c2UgIm1vZGUiIGJlbG93IHRvIGJl
IGEgbGl0dGxlIGxlc3MgY29udHJvdmVyc2lhbC5dDQo+IA0KPiAyLiBDcmVhdGUgYSByZWdpc3Ry
eSBmb3IgIm1vZGUiIHZhbHVlcy4NCj4gDQo+IDMuIERlZmluZSBzb21lIGluaXRpYWwgIm1vZGUi
IHZhbHVlcywgYWxvbmdzaWRlIHRoZSBzcGVjIGZvciB0aGF0DQo+IHByb2Nlc3Npbmc6DQo+ICAg
InNpZzEiIGZvciBkaWdpdGFsbHkgc2lnbmluZyBCNjQoaGVhZGVyKS5CNjQoY29udGVudCk7DQo+
ICAgIm1hYzEiIGZvciBNQUMgb3ZlciBCNjQoaGVhZGVyKS5CNjQoY29udGVudCk7DQo+ICAgImVu
YzEiIGZvciBBRUFELCB3aGVyZSBBQUQgaXMgQjY0KGhlYWRlcikNCj4gICAibm9uZSIgZm9yIHVu
cHJvY2Vzc2VkIGNvbnRlbnQNCj4gICAiY21wIiBmb3IgY29tcHJlc3NlZCAoYnV0IG5vdCBwcm90
ZWN0ZWQpIGNvbnRlbnQNCj4gICAiZW5jMiIgZm9yIEFFQUQgYXBwbGllZCBkaWZmZXJlbnRseSAo
YXMgcGVyIHRoZSBKU09OIHJlcHJlc2VudGF0aW9uKQ0KPiAgIC4uLg0KPiANCj4gNC4gQWxsb3cg
dGhlICJtb2RlIiBwYXJhbWV0ZXIgdG8gYmUgYWJzZW50IGlmIGFuICJhbGciIHZhbHVlIGlzIHBy
ZXNlbnQNCj4gYW5kIGhhcyBhIGRlZmF1bHQgIm1vZGUiLiBUaGlzIG1haW50YWlucyBjb21wYXRp
YmlsaXR5IHdpdGggSk9TRQ0KPiBtZXNzYWdlcyBiYXNlZCBvbiBwcmV2aW91cyBkcmFmdHMuDQo+
IA0KPiA1LiBEZWZpbmUgdGhlIGRlZmF1bHQgIm1vZGUiIGZvciBleGlzdGluZyAiYWxnIiB2YWx1
ZXMuIEZvciBpbnN0YW5jZSwNCj4gZm9yICJhbGciOiJIUzI1NiIgdGhlIGRlZmF1bHQgaXMgIm1v
ZGUiOiJtYWMxIi4gVGhlIHJlZ2lzdHJ5IG9mIGFsZw0KPiB2YWx1ZXMgd291bGQgaGF2ZSBhIGNv
bHVtbiBmb3IgdGhlIGRlZmF1bHQgbW9kZSAodGhvdWdoIG5ldyBhbGdzIGNhbg0KPiBsZWF2ZSB0
aGF0IGNvbHVtbiBibGFuaykuDQo+IA0KPiA2LiBEcm9wIHRoZSAiY3JpdCIgZmllbGQuIElmIHlv
dSBhcmUgY3JlYXRpbmcgYSBKT1NFIG1lc3NhZ2Ugd2l0aCBuZXcNCj4gc2VtYW50aWNzIHRoYXQg
TVVTVCBiZSB1bmRlcnN0b29kLCBqdXN0IGRlZmluZSBhIG5ldyAibW9kZSIgdmFsdWUuIEZvcg0K
PiBleGFtcGxlLCB0byBhdm9pZCBzb21lIGJhc2U2NCBvdmVyaGVhZCB5b3UgY291bGQgZGVmaW5l
ICJtb2RlIjoic2lnMiINCj4gdG8gbWVhbiBkaWdpdGFsbHkgc2lnbiBoZWFkZXJ8fGNvbnRlbnR8
fGxlbihoZWFkZXIpLg0KPiANCj4gNy4gQWxsb3cgYSBsaXN0IG9mICJtb2RlIiB2YWx1ZXMgdG8g
YmUgc3BlY2lmaWVkIGFzIGEgcGFyYW1ldGVyIG9uIGENCj4gSk9TRSBtZWRpYSB0eXBlLg0KPiAN
Cj4gDQo+IFtwcm9iYWJseV0NCj4gOC4gQSBwbHVzIHNpZ24gIisiIGNhbiBiZSBhcHBlbmRlZCB0
byBhbnkgIm1vZGUiIHZhbHVlIHRvIGluZGljYXRlIHRoYXQNCj4gdGhlIGNvbnRlbnQgb2YgdGhp
cyBKT1NFIGxheWVyIGlzIGFub3RoZXIgSk9TRSBsYXllci4gVGhhdCBpcywgcHJvY2Vzcw0KPiB0
aGlzIG1lc3NhZ2UgYXMgcGVyIHRoZSAibW9kZSIgd2l0aG91dCB0aGUgIisiLCB0aGVuIHByb2Nl
c3MgdGhlDQo+IGNvbnRlbnQgYXMgYW5vdGhlciBKT1NFIG1lc3NhZ2UuDQo+IFtBcHBlbmRpbmcg
IisiIGlzIHNpbXBsZXIgdGhhbiAiY3R5IjoiandzIiBvciAibW9yZSI6dHJ1ZSwgYnV0IGFzc3Vt
ZXMNCj4gdGhlIGlubmVyIEpPU0UgbWVzc2FnZSB1c2VzIHRoZSBzYW1lIHNlcmlhbGl6YXRpb24g
YXMgdGhlIG91dGVyIG9uZS5dDQo+IA0KPiANCj4gRW5kIHJlc3VsdDogc2ltcGxlciwgbW9yZSBl
YXNpbHkgdW5kZXJzdG9vZCBieSBwZW9wbGU7IG9uZSBmaWVsZCB0aGF0DQo+IGlzIHN1aXRhYmxl
IGZvciBhbiBpbXBsZW1lbnRhdGlvbiB0byB1c2UgdG8gc3dpdGNoIHRvIHRoZSBhcHByb3ByaWF0
ZQ0KPiBwcm9jZXNzaW5nIGNvZGU7IGJhY2t3YXJkIGNvbXBhdGlibGUgd2l0aCBlYXJsaWVyIGRy
YWZ0czsgY2xlYXINCj4gbWVjaGFuaXNtIGZvciBtYWtpbmcgY2hhbmdlcyB0aGF0IE1VU1QtYmUt
dW5kZXJzdG9vZCAodGhhdCB3ZSBjYW4gYmUNCj4gY29uZmlkZW50IGNvZGUgd2lsbCBub3RpY2Up
Lg0KPiANCj4gDQo+IA0KPiA+IFRoYXQgYmVpbmcgc2FpZCwgSeKAmW0gbm90IGF3YXJlIG9mIGFu
eSB1c2VzIG9mIHRoZXNlIGJ5IGFwcGxpY2F0aW9ucw0KPiBhdA0KPiA+IHByZXNlbnQuDQo+IA0K
PiBBcHBzIHN1Y2ggYXMgT3BlbklEIENvbm5lY3QgY291bGQgdXNlOg0KPiAgIGFwcGxpY2F0aW9u
L2pvc2U7aW5uZXI9YXBwbGljYXRpb24vand0K2pzb24NCj4gDQo+IEFwcHMgY2FuIHN0aWxsIGRl
ZmluZSB0aGVpciBvd24gbWVkaWEgdHlwZXMgZm9yIEpPU0UgbWVzc2FnZXMgKGVnDQo+IGFwcGxp
Y2F0aW9uL2p3dCkgdGhvdWdoIHRoYXQgc2hvdWxkIG5vdCBiZSBuZWNlc3NhcnkuDQo+IA0KPiAN
Cj4gPsKgIFRodXMsIEkgdGhpbmsgdGhhdCBtYWtlcyBpdCBmYWlyIGdhbWUgdG8gYXNrIHdoZXRo
ZXIgd2Ugd2FudCAgdG8NCj4ga2VlcA0KPiA+dGhlbSBvciByZW1vdmUgdGhlbSDigJMgaW4gd2hp
Y2ggY2FzZSwgaWYgYXBwbGljYXRpb25zIGV2ZXIgIG5lZWRlZA0KPiB0aGVtLA0KPiA+dGhleSBj
b3VsZCBkZWZpbmUgdGhlbSBsYXRlci4NCj4gPg0KPiA+IEFub3RoZXIgZGltZW5zaW9uIG9mIHRo
aXMgcXVlc3Rpb24gZm9yIEpXUyBhbmQgSldFIGlzIHRoYXQgaXTigJlzIG5vdA0KPiA+IGNsZWFy
IHRoYXQgdGhlIGZvdXIgdHlwZXMgYXBwbGljYXRpb24vandzLCBhcHBsaWNhdGlvbi9qd3MranNv
biwNCj4gPiBhcHBsaWNhdGlvbi9qd2UsIGFuZCBhcHBsaWNhdGlvbi9qd2UranNvbiBhcmUgZXZl
biB0aGUgcmlnaHQgb25lcy4NCj4gSXQNCj4gPiBtaWdodCBiZSBtb3JlIHVzZWZ1bCB0byBoYXZl
IGdlbmVyaWMgYXBwbGljYXRpb24vam9zZSBhbmQNCj4gPiBhcHBsaWNhdGlvbi9qb3NlK2pzb24g
dHlwZXMsIHdoaWNoIGNvdWxkIGhvbGQgZWl0aGVyIEpXUyBvciBKV0UNCj4gPiBvYmplY3RzIHJl
c3BlY3RpdmVseSB1c2luZyB0aGUgY29tcGFjdCBvciBKU09OIHNlcmlhbGl6YXRpb25zDQo+ID4g
KGFsdGhvdWdoIEnigJltIG5vdCBhZHZvY2F0aW5nIGFkZGluZyB0aGVtIGF0IHRoaXMgdGltZSku
DQo+ID4NCj4gPiBIYXZpbmcgZGlmZmVyZW50IEpXUyB2ZXJzdXMgSldFIE1JTUUgdHlwZXMgYXBw
YXJlbnRseSBkaWQgY29udHJpYnV0ZQ0KPiA+IHRvIGF0IGxlYXN0IERpY2vigJlzIGNvbmZ1c2lv
biBhYm91dCB0aGUgcHVycG9zZSBvZiB0aGUg4oCcdHlw4oCdIGZpZWxkLCBzbw0KPiA+IGRlbGV0
aW5nIHRoZW0gY291bGQgaGVscCBlbGltaW5hdGUgdGhpcyBwb3NzaWJpbGl0eSBvZiBjb25mdXNp
b24gaW4NCj4gPiB0aGUgZnV0dXJlLsKgIFRodXMsIEnigJltIGluY3JlYXNpbmdseSBjb252aW5j
ZWQgd2Ugc2hvdWxkIGdldCByaWQgb2YNCj4gdGhlDQo+ID4gSldTIGFuZCBKV0UgdHlwZXMgYW5k
IGxlYXZlIGl0IHVwIHRvIGFwcGxpY2F0aW9ucyB0byBkZWZpbmUgdGhlIHR5cGVzDQo+ID4gdGhl
eSBuZWVkLCB3aGVuIHRoZXkgbmVlZCB0aGVtLg0KPiA+DQo+ID4gRG8gcGVvcGxlIGhhdmUgdXNl
IGNhc2VzIGZvciB0aGVzZSBmb3VyIE1JTUUgdHlwZXMgbm93IG9yIHNob3VsZCB3ZQ0KPiA+IGxl
YXZlIHRoZW0gdG8gZnV0dXJlIHNwZWNzIHRvIGRlZmluZSwgaWYgbmVlZGVkPw0KPiANCj4gV2Ug
YXJlIGRlZmluaW5nIGEgZm9ybWF0IGZvciB1c2Ugb24gdGhlIHdlYi4gVGhlIHdlYiBpZGVudGlm
aWVzIGZvcm1hdHMNCj4gdmlhIG1lZGlhIHR5cGVzLiBTbyBKT1NFIG5lZWRzIHRvIGRlZmluZSBt
ZWRpYSB0eXBlcy4NCj4gDQo+IC0tDQo+IEphbWVzIE1hbmdlcg0KDQo=

From turners@ieca.com  Thu Jun 20 06:46:19 2013
Return-Path: <turners@ieca.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55D4B21F9990 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 06:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.489
X-Spam-Level: 
X-Spam-Status: No, score=-101.489 tagged_above=-999 required=5 tests=[AWL=-0.713, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pLz-tA3C80B for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 06:46:14 -0700 (PDT)
Received: from gateway14.websitewelcome.com (gateway14.websitewelcome.com [67.18.7.4]) by ietfa.amsl.com (Postfix) with ESMTP id BB8CE21F91BC for <jose@ietf.org>; Thu, 20 Jun 2013 06:46:10 -0700 (PDT)
Received: by gateway14.websitewelcome.com (Postfix, from userid 5007) id E3D1B65FC6294; Thu, 20 Jun 2013 08:46:04 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway14.websitewelcome.com (Postfix) with ESMTP id ACF2565FC61DC for <jose@ietf.org>; Thu, 20 Jun 2013 08:46:04 -0500 (CDT)
Received: from [147.28.0.178] (port=57955 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UpfBh-0000ct-Py; Thu, 20 Jun 2013 08:46:09 -0500
Message-ID: <51C307A0.70704@ieca.com>
Date: Thu, 20 Jun 2013 22:46:08 +0900
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: jose@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [147.28.0.178]:57955
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: ietf@ietf.org
Subject: [jose] JOSE Virtual Interim 6/17 mixup
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 13:46:19 -0000

There was an intent to have a virtual meeting of the JOSE WG on 
2013-06-17.  The announcement never made it to the IETF announce list. 
Because of this that virtual meeting is considered a design team meeting 
and not an official virtual interim meeting.  As such, all output is 
subject to approval, rejection or modification by the WG as a whole. 
The minutes of that design team have been posted here:

http://www.ietf.org/proceedings/interim/2013/06/17/jose/minutes/minutes-interim-2013-jose-2

Note that the next virtual interim was properly announced:
http://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=12075&tid=1371735805

spt

From rlb@ipv.sx  Thu Jun 20 08:15:52 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E7721F8F5C for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.321
X-Spam-Level: 
X-Spam-Status: No, score=-0.321 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g06Wyj+Pqpfs for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:15:48 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA4921F99AE for <jose@ietf.org>; Thu, 20 Jun 2013 08:15:35 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id ta17so7209524obb.8 for <jose@ietf.org>; Thu, 20 Jun 2013 08:15:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=y8DUXGJJnVsjnGjPoIjtZiTrrTTLbOudSWvaObrj2t4=; b=VcqQ3cdUWqqraUryRPYDmMN4fPvIUM0fy1UPRwZBVY9UkEgu616vy4AxxkX92SUH2R VCOIiIadrXfJU+sYVaqyai7cyQ8SDugcZjnrnSFsVHdmFXzBAFI3Ma3V7mJNQVXtw4Q0 gvBLAvsZlq9ONkMBTUgQ6wc5rH+pSmSWhkyHgLhgtEuO9vVxh6RpOtoTLLSX3mxIRxBu ITQ6l6Bpv+5skxyv582GT10RNHZD0vCD4qQ7ry6KyZD0W/43EYjq1tvtOSFTUOL7TeI9 T7be4SwYjT2GsvzqC1QpN2ajkHIIBLw10MrvJZH5FpjGtJHqpmQiMrdsNFd8PNxh1pFJ Ex6w==
MIME-Version: 1.0
X-Received: by 10.182.237.77 with SMTP id va13mr1748478obc.65.1371741326047; Thu, 20 Jun 2013 08:15:26 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 08:15:25 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 11:15:25 -0400
Message-ID: <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cdcc7690a704df976adf
X-Gm-Message-State: ALoCoQnJMJw2ZkiU1WhRv7m7irLUEmiHUWRCtPAUglJQQ8UEaho7TEU4dHGMq644JoiEy50OK2gU
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 15:15:52 -0000

--e89a8ff1cdcc7690a704df976adf
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Multiplexing JWE and JWS under a single JOSE media type only makes sense if
there's a defined algorithm to demux them.  So if you want to do this, you
would need to write down the algorithm.

Personally, it seems simpler and clearer to me to just have the four
current types, so that you know which type of object you're dealing with,
and in what serialization, without having to do content sniffing.


On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  The JWS and JWE documents currently define these MIME types for the
> convenience of applications that may want to use them:****
>
>                 application/jws****
>
>                 application/jws+json****
>
>                 application/jwe****
>
>                 application/jwe+json****
>
> ** **
>
> That being said, I=92m not aware of any uses of these by applications at
> present.  Thus, I think that makes it fair game to ask whether we want to
> keep them or remove them =96 in which case, if applications ever needed t=
hem,
> they could define them later.****
>
> ** **
>
> Another dimension of this question for JWS and JWE is that it=92s not cle=
ar
> that the four types application/jws, application/jws+json, application/jw=
e,
> and application/jwe+json are even the right ones.  It might be more usefu=
l
> to have generic application/jose and application/jose+json types, which
> could hold either JWS or JWE objects respectively using the compact or JS=
ON
> serializations (although I=92m not advocating adding them at this time).*=
***
>
> ** **
>
> Having different JWS versus JWE MIME types apparently did contribute to a=
t
> least Dick=92s confusion about the purpose of the =93typ=94 field, so del=
eting
> them could help eliminate this possibility of confusion in the future.
> Thus, I=92m increasingly convinced we should get rid of the JWS and JWE t=
ypes
> and leave it up to applications to define the types they need, when they
> need them.****
>
> ** **
>
> Do people have use cases for these four MIME types now or should we leave
> them to future specs to define, if needed?****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> P.S.  For completeness, I=92ll add that the JWK document also defines the=
se
> MIME types:****
>
>                 application/jwk+json****
>
>                 application/jwk-set+json****
>
> ** **
>
> There are already clear use cases for these types, so I=92m not advocatin=
g
> deleting them, but wanted to call that out explicitly.  For instance, whe=
n
> retrieving a JWK Set document referenced by a =93jku=94 header parameter,=
 I
> believe that the result should use the application/jwk-set+json type.  (I=
n
> fact, I=92ll add this to the specs, unless there are any objections.)
> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
> application/jwk+json.  Both could also be as =93cty=94 values when encryp=
ting
> JWKs and JWK Sets, in contexts where that that would be useful.****
>
> ** **
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--e89a8ff1cdcc7690a704df976adf
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Multiplexing JWE and JWS under a single JOSE media type on=
ly makes sense if there&#39;s a defined algorithm to demux them. =A0So if y=
ou want to do this, you would need to write down the algorithm.<div><br></d=
iv>
<div>Personally, it seems simpler and clearer to me to just have the four c=
urrent types, so that you know which type of object you&#39;re dealing with=
, and in what serialization, without having to do content sniffing.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
 Jun 18, 2013 at 9:26 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:<u></=
u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe+json<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">That being said, I=92m not aware of any uses of thes=
e by applications at present.=A0 Thus, I think that makes it fair game to a=
sk whether we want to keep them or remove them =96 in which case, if applic=
ations ever needed them, they could define
 them later.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it=92s not clear that the four types application/jws, application/jw=
s+json, application/jwe, and application/jwe+json are even the right ones.=
=A0 It might be more useful to have generic
 application/jose and application/jose+json types, which could hold either =
JWS or JWE objects respectively using the compact or JSON serializations (a=
lthough I=92m not advocating adding them at this time).<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick=92s confusion about the purpose of the =
=93typ=94 field, so deleting them could help eliminate this possibility of =
confusion in the future.=A0 Thus, I=92m increasingly
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.<u></u><u></u=
></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?<u></u><u><=
/u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u><=
/u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">P.S.=A0 For completeness, I=92ll add that the JWK do=
cument also defines these MIME types:<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk-set+json<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I=92m not advocating deleting them, but wanted to call that out explicitl=
y.=A0 For instance, when retrieving a JWK Set document referenced by a =93j=
ku=94 header parameter, I believe that the
 result should use the application/jwk-set+json type.=A0 (In fact, I=92ll a=
dd this to the specs, unless there are any objections.)=A0 Likewise, draft-=
miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.=A0 Both=
 could also be as =93cty=94 values when encrypting
 JWKs and JWK Sets, in contexts where that that would be useful.<u></u><u><=
/u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--e89a8ff1cdcc7690a704df976adf--

From Michael.Jones@microsoft.com  Thu Jun 20 08:19:59 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5988921F8F6D for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1Kq9dkf8gPQ for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:19:54 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id C0F7221F9D82 for <jose@ietf.org>; Thu, 20 Jun 2013 08:19:52 -0700 (PDT)
Received: from BN1AFFO11FD008.protection.gbl (10.58.52.204) by BN1BFFO11HUB027.protection.gbl (10.58.53.137) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 15:19:49 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD008.mail.protection.outlook.com (10.58.52.68) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 15:19:49 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 15:19:39 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQBPRl+AAAAPBOA=
Date: Thu, 20 Jun 2013 15:19:38 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com>
In-Reply-To: <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.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_4E1F6AAD24975D4BA5B1680429673943678794EFTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51444003)(189002)(199002)(24454002)(377454003)(50986001)(77982001)(66066001)(55846006)(76796001)(31966008)(16236675002)(51856001)(512954002)(74366001)(63696002)(81342001)(4396001)(49866001)(74706001)(46102001)(16406001)(79102001)(65816001)(69226001)(81542001)(54356001)(53806001)(47446002)(56776001)(74502001)(74662001)(33656001)(71186001)(20776003)(54316002)(76786001)(59766001)(77096001)(6806003)(47736001)(80022001)(56816003)(19300405003)(74876001)(16297215004)(15202345003)(76482001)(47976001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB027; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 15:19:59 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678794EFTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There is a defined algorithm to distinguish between the JWS and JWE objects=
 in the third paragraph of http://tools.ietf.org/html/draft-ietf-jose-json-=
web-encryption-11#section-4.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 20, 2013 8:15 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?

Multiplexing JWE and JWS under a single JOSE media type only makes sense if=
 there's a defined algorithm to demux them.  So if you want to do this, you=
 would need to write down the algorithm.

Personally, it seems simpler and clearer to me to just have the four curren=
t types, so that you know which type of object you're dealing with, and in =
what serialization, without having to do content sniffing.

On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
The JWS and JWE documents currently define these MIME types for the conveni=
ence of applications that may want to use them:
                application/jws
                application/jws+json
                application/jwe
                application/jwe+json

That being said, I'm not aware of any uses of these by applications at pres=
ent.  Thus, I think that makes it fair game to ask whether we want to keep =
them or remove them - in which case, if applications ever needed them, they=
 could define them later.

Another dimension of this question for JWS and JWE is that it's not clear t=
hat the four types application/jws, application/jws+json, application/jwe, =
and application/jwe+json are even the right ones.  It might be more useful =
to have generic application/jose and application/jose+json types, which cou=
ld hold either JWS or JWE objects respectively using the compact or JSON se=
rializations (although I'm not advocating adding them at this time).

Having different JWS versus JWE MIME types apparently did contribute to at =
least Dick's confusion about the purpose of the "typ" field, so deleting th=
em could help eliminate this possibility of confusion in the future.  Thus,=
 I'm increasingly convinced we should get rid of the JWS and JWE types and =
leave it up to applications to define the types they need, when they need t=
hem.

Do people have use cases for these four MIME types now or should we leave t=
hem to future specs to define, if needed?

                                                                -- Mike

P.S.  For completeness, I'll add that the JWK document also defines these M=
IME types:
                application/jwk+json
                application/jwk-set+json

There are already clear use cases for these types, so I'm not advocating de=
leting them, but wanted to call that out explicitly.  For instance, when re=
trieving a JWK Set document referenced by a "jku" header parameter, I belie=
ve that the result should use the application/jwk-set+json type.  (In fact,=
 I'll add this to the specs, unless there are any objections.)  Likewise, d=
raft-miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.  B=
oth could also be as "cty" values when encrypting JWKs and JWK Sets, in con=
texts where that that would be useful.


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B1680429673943678794EFTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There is a defined algori=
thm to distinguish between the JWS and JWE objects in the third paragraph o=
f
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-1=
1#section-4">
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4=
</a>.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Multiplexing JWE and JWS under a single JOSE media t=
ype only makes sense if there's a defined algorithm to demux them. &nbsp;So=
 if you want to do this, you would need to write down the algorithm.<o:p></=
o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Personally, it seems simpler and clearer to me to ju=
st have the four current types, so that you know which type of object you'r=
e dealing with, and in what serialization, without having to do content sni=
ffing.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The JWS and JWE documents currently define these MIME types for th=
e convenience of applications that may want to use them:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jws<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwe<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">That being said, I&#8217;m not aware of any uses of these by appli=
cations at present.&nbsp; Thus, I think that makes it fair game to ask whet=
her we want to keep them or remove them &#8211; in which
 case, if applications ever needed them, they could define them later.<o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Another dimension of this question for JWS and JWE is that it&#821=
7;s not clear that the four types application/jws, application/jws&#43;json=
, application/jwe, and application/jwe&#43;json are
 even the right ones.&nbsp; It might be more useful to have generic applica=
tion/jose and application/jose&#43;json types, which could hold either JWS =
or JWE objects respectively using the compact or JSON serializations (altho=
ugh I&#8217;m not advocating adding them at this
 time).<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Having different JWS versus JWE MIME types apparently did contribu=
te to at least Dick&#8217;s confusion about the purpose of the &#8220;typ&#=
8221; field, so deleting them could help eliminate this
 possibility of confusion in the future.&nbsp; Thus, I&#8217;m increasingly=
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.<o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Do people have use cases for these four MIME types now or should w=
e leave them to future specs to define, if needed?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; -- Mike<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">P.S.&nbsp; For completeness, I&#8217;ll add that the JWK document =
also defines these MIME types:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">There are already clear use cases for these types, so I&#8217;m no=
t advocating deleting them, but wanted to call that out explicitly.&nbsp; F=
or instance, when retrieving a JWK Set document
 referenced by a &#8220;jku&#8221; header parameter, I believe that the res=
ult should use the application/jwk-set&#43;json type.&nbsp; (In fact, I&#82=
17;ll add this to the specs, unless there are any objections.)&nbsp; Likewi=
se, draft-miller-jose-jwe-protected-jwk-02 already uses application/jwk&#43=
;json.&nbsp;
 Both could also be as &#8220;cty&#8221; values when encrypting JWKs and JW=
K Sets, in contexts where that that would be useful.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678794EFTK5EX14MBXC283r_--

From jricher@mitre.org  Thu Jun 20 08:22:14 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5DE021F9D6F for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MXeR7FUrFnKN for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:21:54 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 4FABD21F9D2F for <jose@ietf.org>; Thu, 20 Jun 2013 08:21:53 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 87F131F0BD7; Thu, 20 Jun 2013 11:21:52 -0400 (EDT)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 477C41F0BC9; Thu, 20 Jun 2013 11:21:52 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS03.MITRE.ORG (129.83.29.80) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 20 Jun 2013 11:21:51 -0400
Message-ID: <51C31DCE.8080309@mitre.org>
Date: Thu, 20 Jun 2013 11:20:46 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>
Content-Type: multipart/alternative; boundary="------------060309090501090506080604"
X-Originating-IP: [129.83.31.56]
Cc: Richard Barnes <rlb@ipv.sx>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 15:22:15 -0000

--------------060309090501090506080604
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

And I'd like to point out that we need this method anyway because you 
won't always have a mimetype along with the JOSE object -- they can be 
sent as HTTP headers, query parameters, any number of things really.

  -- Justin

On 06/20/2013 11:19 AM, Mike Jones wrote:
>
> There is a defined algorithm to distinguish between the JWS and JWE 
> objects in the third paragraph of 
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4.
>
> -- Mike
>
> *From:*Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 20, 2013 8:15 AM
> *To:* Mike Jones
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE 
> MIME types?
>
> Multiplexing JWE and JWS under a single JOSE media type only makes 
> sense if there's a defined algorithm to demux them.  So if you want to 
> do this, you would need to write down the algorithm.
>
> Personally, it seems simpler and clearer to me to just have the four 
> current types, so that you know which type of object you're dealing 
> with, and in what serialization, without having to do content sniffing.
>
> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones 
> <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> wrote:
>
> The JWS and JWE documents currently define these MIME types for the 
> convenience of applications that may want to use them:
>
> application/jws
>
> application/jws+json
>
> application/jwe
>
> application/jwe+json
>
> That being said, I'm not aware of any uses of these by applications at 
> present.  Thus, I think that makes it fair game to ask whether we want 
> to keep them or remove them -- in which case, if applications ever 
> needed them, they could define them later.
>
> Another dimension of this question for JWS and JWE is that it's not 
> clear that the four types application/jws, application/jws+json, 
> application/jwe, and application/jwe+json are even the right ones.  It 
> might be more useful to have generic application/jose and 
> application/jose+json types, which could hold either JWS or JWE 
> objects respectively using the compact or JSON serializations 
> (although I'm not advocating adding them at this time).
>
> Having different JWS versus JWE MIME types apparently did contribute 
> to at least Dick's confusion about the purpose of the "typ" field, so 
> deleting them could help eliminate this possibility of confusion in 
> the future.  Thus, I'm increasingly convinced we should get rid of the 
> JWS and JWE types and leave it up to applications to define the types 
> they need, when they need them.
>
> Do people have use cases for these four MIME types now or should we 
> leave them to future specs to define, if needed?
>
> -- Mike
>
> P.S. For completeness, I'll add that the JWK document also defines 
> these MIME types:
>
> application/jwk+json
>
> application/jwk-set+json
>
> There are already clear use cases for these types, so I'm not 
> advocating deleting them, but wanted to call that out explicitly.  For 
> instance, when retrieving a JWK Set document referenced by a "jku" 
> header parameter, I believe that the result should use the 
> application/jwk-set+json type.  (In fact, I'll add this to the specs, 
> unless there are any objections.) Likewise, 
> draft-miller-jose-jwe-protected-jwk-02 already uses 
> application/jwk+json.  Both could also be as "cty" values when 
> encrypting JWKs and JWK Sets, in contexts where that that would be useful.
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org <mailto:jose@ietf.org>
> https://www.ietf.org/mailman/listinfo/jose
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------060309090501090506080604
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    And I'd like to point out that we need this method anyway because
    you won't always have a mimetype along with the JOSE object -- they
    can be sent as HTTP headers, query parameters, any number of things
    really. <br>
    <br>
    &nbsp;-- Justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/20/2013 11:19 AM, Mike Jones
      wrote:<br>
    </div>
    <blockquote
cite="mid:4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">There
            is a defined algorithm to distinguish between the JWS and
            JWE objects in the third paragraph of
            <a moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4</a>.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
            -- Mike<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
            Richard Barnes [<a class="moz-txt-link-freetext" href="mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
            <br>
            <b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
            <b>To:</b> Mike Jones<br>
            <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a><br>
            <b>Subject:</b> Re: [jose] Should we keep or remove the JOSE
            JWS and JWE MIME types?<o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <div>
          <p class="MsoNormal">Multiplexing JWE and JWS under a single
            JOSE media type only makes sense if there's a defined
            algorithm to demux them. &nbsp;So if you want to do this, you
            would need to write down the algorithm.<o:p></o:p></p>
          <div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
          <div>
            <p class="MsoNormal">Personally, it seems simpler and
              clearer to me to just have the four current types, so that
              you know which type of object you're dealing with, and in
              what serialization, without having to do content sniffing.<o:p></o:p></p>
          </div>
        </div>
        <div>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
          <div>
            <p class="MsoNormal">On Tue, Jun 18, 2013 at 9:26 PM, Mike
              Jones &lt;<a moz-do-not-send="true"
                href="mailto:Michael.Jones@microsoft.com"
                target="_blank">Michael.Jones@microsoft.com</a>&gt;
              wrote:<o:p></o:p></p>
            <div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The
                  JWS and JWE documents currently define these MIME
                  types for the convenience of applications that may
                  want to use them:<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jws<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jws+json<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jwe<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jwe+json<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">That
                  being said, I&#8217;m not aware of any uses of these by
                  applications at present.&nbsp; Thus, I think that makes it
                  fair game to ask whether we want to keep them or
                  remove them &#8211; in which case, if applications ever
                  needed them, they could define them later.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Another
                  dimension of this question for JWS and JWE is that
                  it&#8217;s not clear that the four types application/jws,
                  application/jws+json, application/jwe, and
                  application/jwe+json are even the right ones.&nbsp; It
                  might be more useful to have generic application/jose
                  and application/jose+json types, which could hold
                  either JWS or JWE objects respectively using the
                  compact or JSON serializations (although I&#8217;m not
                  advocating adding them at this time).<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Having
                  different JWS versus JWE MIME types apparently did
                  contribute to at least Dick&#8217;s confusion about the
                  purpose of the &#8220;typ&#8221; field, so deleting them could
                  help eliminate this possibility of confusion in the
                  future.&nbsp; Thus, I&#8217;m increasingly convinced we should
                  get rid of the JWS and JWE types and leave it up to
                  applications to define the types they need, when they
                  need them.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Do
                  people have use cases for these four MIME types now or
                  should we leave them to future specs to define, if
                  needed?<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  -- Mike<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">P.S.&nbsp;
                  For completeness, I&#8217;ll add that the JWK document also
                  defines these MIME types:<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jwk+json<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                  application/jwk-set+json<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There
                  are already clear use cases for these types, so I&#8217;m
                  not advocating deleting them, but wanted to call that
                  out explicitly.&nbsp; For instance, when retrieving a JWK
                  Set document referenced by a &#8220;jku&#8221; header parameter, I
                  believe that the result should use the
                  application/jwk-set+json type.&nbsp; (In fact, I&#8217;ll add
                  this to the specs, unless there are any objections.)&nbsp;
                  Likewise, draft-miller-jose-jwe-protected-jwk-02
                  already uses application/jwk+json.&nbsp; Both could also be
                  as &#8220;cty&#8221; values when encrypting JWKs and JWK Sets, in
                  contexts where that that would be useful.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
              _______________________________________________<br>
              jose mailing list<br>
              <a moz-do-not-send="true" href="mailto:jose@ietf.org">jose@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/jose"
                target="_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060309090501090506080604--

From jricher@mitre.org  Thu Jun 20 08:50:29 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA8C21F9E16 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBjH3mvRWsfs for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 08:50:23 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id B58FE21F9E1F for <jose@ietf.org>; Thu, 20 Jun 2013 08:50:22 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 3FC11226010C; Thu, 20 Jun 2013 11:50:22 -0400 (EDT)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 2CA292260102; Thu, 20 Jun 2013 11:50:22 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS04.MITRE.ORG (129.83.29.81) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 20 Jun 2013 11:50:21 -0400
Message-ID: <51C3247C.1060901@mitre.org>
Date: Thu, 20 Jun 2013 11:49:16 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <MLQM-20130620113038269-3554@mlite.mitre.org>
In-Reply-To: <MLQM-20130620113038269-3554@mlite.mitre.org>
Content-Type: multipart/alternative; boundary="------------000603060406070103080200"
X-Originating-IP: [129.83.31.56]
Cc: Richard Barnes <rlb@ipv.sx>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 15:50:29 -0000

--------------000603060406070103080200
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Which is to say, if what I said wasn't exactly clear, that the different 
mimetypes don't necessarily add anything. If we're going to define a 
mimetype we might as well just have the one, application/jose for the 
compact encoding.

For the JSON-based encodings, the same argument applies. However, 
personally, I've never been a fan of the plus-style mimetypes like 
application/jose+json, since in most dev frameworks that I've worked in 
you get "application/json" for free when you start spitting out JSON 
objects. It raises the question: is it valid to put a JSON-encoded JOSE 
object out as just application/json? I'd think you'd want it to be. I'd 
predict that that's what you're going to have developers doing in general.

  -- justin

On 06/20/2013 11:20 AM, Justin Richer wrote:
> And I'd like to point out that we need this method anyway because you 
> won't always have a mimetype along with the JOSE object -- they can be 
> sent as HTTP headers, query parameters, any number of things really.
>
>  -- Justin
>
> On 06/20/2013 11:19 AM, Mike Jones wrote:
>>
>> There is a defined algorithm to distinguish between the JWS and JWE 
>> objects in the third paragraph of 
>> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4.
>>
>> -- Mike
>>
>> *From:*Richard Barnes [mailto:rlb@ipv.sx]
>> *Sent:* Thursday, June 20, 2013 8:15 AM
>> *To:* Mike Jones
>> *Cc:* jose@ietf.org
>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE 
>> MIME types?
>>
>> Multiplexing JWE and JWS under a single JOSE media type only makes 
>> sense if there's a defined algorithm to demux them.  So if you want 
>> to do this, you would need to write down the algorithm.
>>
>> Personally, it seems simpler and clearer to me to just have the four 
>> current types, so that you know which type of object you're dealing 
>> with, and in what serialization, without having to do content sniffing.
>>
>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones 
>> <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> wrote:
>>
>> The JWS and JWE documents currently define these MIME types for the 
>> convenience of applications that may want to use them:
>>
>> application/jws
>>
>> application/jws+json
>>
>> application/jwe
>>
>> application/jwe+json
>>
>> That being said, I'm not aware of any uses of these by applications 
>> at present.  Thus, I think that makes it fair game to ask whether we 
>> want to keep them or remove them -- in which case, if applications 
>> ever needed them, they could define them later.
>>
>> Another dimension of this question for JWS and JWE is that it's not 
>> clear that the four types application/jws, application/jws+json, 
>> application/jwe, and application/jwe+json are even the right ones.  
>> It might be more useful to have generic application/jose and 
>> application/jose+json types, which could hold either JWS or JWE 
>> objects respectively using the compact or JSON serializations 
>> (although I'm not advocating adding them at this time).
>>
>> Having different JWS versus JWE MIME types apparently did contribute 
>> to at least Dick's confusion about the purpose of the "typ" field, so 
>> deleting them could help eliminate this possibility of confusion in 
>> the future.  Thus, I'm increasingly convinced we should get rid of 
>> the JWS and JWE types and leave it up to applications to define the 
>> types they need, when they need them.
>>
>> Do people have use cases for these four MIME types now or should we 
>> leave them to future specs to define, if needed?
>>
>> -- Mike
>>
>> P.S. For completeness, I'll add that the JWK document also defines 
>> these MIME types:
>>
>> application/jwk+json
>>
>> application/jwk-set+json
>>
>> There are already clear use cases for these types, so I'm not 
>> advocating deleting them, but wanted to call that out explicitly.  
>> For instance, when retrieving a JWK Set document referenced by a 
>> "jku" header parameter, I believe that the result should use the 
>> application/jwk-set+json type.  (In fact, I'll add this to the specs, 
>> unless there are any objections.)  Likewise, 
>> draft-miller-jose-jwe-protected-jwk-02 already uses 
>> application/jwk+json.  Both could also be as "cty" values when 
>> encrypting JWKs and JWK Sets, in contexts where that that would be 
>> useful.
>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org <mailto:jose@ietf.org>
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------000603060406070103080200
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Which is to say, if what I said wasn't exactly clear, that the
    different mimetypes don't necessarily add anything. If we're going
    to define a mimetype we might as well just have the one,
    application/jose for the compact encoding. <br>
    <br>
    For the JSON-based encodings, the same argument applies. However,
    personally, I've never been a fan of the plus-style mimetypes like
    application/jose+json, since in most dev frameworks that I've worked
    in you get "application/json" for free when you start spitting out
    JSON objects. It raises the question: is it valid to put a
    JSON-encoded JOSE object out as just application/json? I'd think
    you'd want it to be. I'd predict that that's what you're going to
    have developers doing in general. <br>
    <br>
    &nbsp;-- justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/20/2013 11:20 AM, Justin Richer
      wrote:<br>
    </div>
    <blockquote cite="mid:MLQM-20130620113038269-3554@mlite.mitre.org"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      And I'd like to point out that we need this method anyway because
      you won't always have a mimetype along with the JOSE object --
      they can be sent as HTTP headers, query parameters, any number of
      things really. <br>
      <br>
      &nbsp;-- Justin<br>
      <br>
      <div class="moz-cite-prefix">On 06/20/2013 11:19 AM, Mike Jones
        wrote:<br>
      </div>
      <blockquote
cite="mid:4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com"
        type="cite">
        <meta name="Generator" content="Microsoft Word 14 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
        <div class="WordSection1">
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">There

              is a defined algorithm to distinguish between the JWS and
              JWE objects in the third paragraph of <a
                moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4</a>.<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

              -- Mike<o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
              Richard Barnes [<a moz-do-not-send="true"
                class="moz-txt-link-freetext" href="mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
              <br>
              <b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
              <b>To:</b> Mike Jones<br>
              <b>Cc:</b> <a moz-do-not-send="true"
                class="moz-txt-link-abbreviated"
                href="mailto:jose@ietf.org">jose@ietf.org</a><br>
              <b>Subject:</b> Re: [jose] Should we keep or remove the
              JOSE JWS and JWE MIME types?<o:p></o:p></span></p>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <div>
            <p class="MsoNormal">Multiplexing JWE and JWS under a single
              JOSE media type only makes sense if there's a defined
              algorithm to demux them. &nbsp;So if you want to do this, you
              would need to write down the algorithm.<o:p></o:p></p>
            <div>
              <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
            </div>
            <div>
              <p class="MsoNormal">Personally, it seems simpler and
                clearer to me to just have the four current types, so
                that you know which type of object you're dealing with,
                and in what serialization, without having to do content
                sniffing.<o:p></o:p></p>
            </div>
          </div>
          <div>
            <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
            <div>
              <p class="MsoNormal">On Tue, Jun 18, 2013 at 9:26 PM, Mike
                Jones &lt;<a moz-do-not-send="true"
                  href="mailto:Michael.Jones@microsoft.com"
                  target="_blank">Michael.Jones@microsoft.com</a>&gt;
                wrote:<o:p></o:p></p>
              <div>
                <div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The

                    JWS and JWE documents currently define these MIME
                    types for the convenience of applications that may
                    want to use them:<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jws<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jws+json<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jwe<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jwe+json<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">That

                    being said, I&#8217;m not aware of any uses of these by
                    applications at present.&nbsp; Thus, I think that makes
                    it fair game to ask whether we want to keep them or
                    remove them &#8211; in which case, if applications ever
                    needed them, they could define them later.<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Another

                    dimension of this question for JWS and JWE is that
                    it&#8217;s not clear that the four types application/jws,
                    application/jws+json, application/jwe, and
                    application/jwe+json are even the right ones.&nbsp; It
                    might be more useful to have generic
                    application/jose and application/jose+json types,
                    which could hold either JWS or JWE objects
                    respectively using the compact or JSON
                    serializations (although I&#8217;m not advocating adding
                    them at this time).<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Having

                    different JWS versus JWE MIME types apparently did
                    contribute to at least Dick&#8217;s confusion about the
                    purpose of the &#8220;typ&#8221; field, so deleting them could
                    help eliminate this possibility of confusion in the
                    future.&nbsp; Thus, I&#8217;m increasingly convinced we should
                    get rid of the JWS and JWE types and leave it up to
                    applications to define the types they need, when
                    they need them.<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Do

                    people have use cases for these four MIME types now
                    or should we leave them to future specs to define,
                    if needed?<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    -- Mike<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">P.S.&nbsp;

                    For completeness, I&#8217;ll add that the JWK document
                    also defines these MIME types:<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jwk+json<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

                    application/jwk-set+json<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There

                    are already clear use cases for these types, so I&#8217;m
                    not advocating deleting them, but wanted to call
                    that out explicitly.&nbsp; For instance, when retrieving
                    a JWK Set document referenced by a &#8220;jku&#8221; header
                    parameter, I believe that the result should use the
                    application/jwk-set+json type.&nbsp; (In fact, I&#8217;ll add
                    this to the specs, unless there are any
                    objections.)&nbsp; Likewise,
                    draft-miller-jose-jwe-protected-jwk-02 already uses
                    application/jwk+json.&nbsp; Both could also be as &#8220;cty&#8221;
                    values when encrypting JWKs and JWK Sets, in
                    contexts where that that would be useful.<o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">&nbsp;<o:p></o:p></p>
                </div>
              </div>
              <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
                _______________________________________________<br>
                jose mailing list<br>
                <a moz-do-not-send="true" href="mailto:jose@ietf.org">jose@ietf.org</a><br>
                <a moz-do-not-send="true"
                  href="https://www.ietf.org/mailman/listinfo/jose"
                  target="_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
            </div>
            <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
jose mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000603060406070103080200--

From rlb@ipv.sx  Thu Jun 20 09:49:10 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0424021F9D64 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 09:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.024
X-Spam-Level: 
X-Spam-Status: No, score=-0.024 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPrIJZpBBABd for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 09:49:05 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id C03EB21F9CEB for <jose@ietf.org>; Thu, 20 Jun 2013 09:49:05 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so7313156obc.23 for <jose@ietf.org>; Thu, 20 Jun 2013 09:49:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=NN8l6I1OKfI94Xfp503esd8NuidcXkx0Y1RVsodEZp8=; b=mM/D4E8gPBCTj7vxvO7vBZra1wY0p64lMSxbZtIVWnyd2SUKmWhnh/pHzvsgEmcihz iZOBCoD5NfSdbpYSBEy9hsdgBgpHkOkMPF6gQ4xPL+fH8FyVppXrehXf6AiCU9MakwRZ Q+4j1rw03uAlWJq+auKwa/uYPE3MrGKjMEC8y8Ja3z3yakF3JjMmljNsLMAJabSwcnQt UlFaOw8oPpe0ctE9PW9CWC9sjGVzFA+zi7Pe5lCWR9XvnQx1LrHijGaSFJXemW8LtF5E itumqTC4mzBGvE9R8ZgNXtqZxzR+HlNsRWtM0R2QyYT3KkI2Xrpra06yP6ULOyirF3Gm bfBA==
MIME-Version: 1.0
X-Received: by 10.182.232.225 with SMTP id tr1mr1893264obc.69.1371746945312; Thu, 20 Jun 2013 09:49:05 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 09:49:05 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 12:49:05 -0400
Message-ID: <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c3124265ba3504df98b9aa
X-Gm-Message-State: ALoCoQnD74fLzUdUHsg0ugikeXwnYiol/0/bSsk9jEdKUxIIfI+yGQt5XEL0ztW+jTyh6CAe1kYO
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 16:49:10 -0000

--001a11c3124265ba3504df98b9aa
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

That algorithm is part of the story, but it's incomplete.  What we need is
an algorithm that starts with an arbitrary octet string and sorts by
JWS/JWE and serialization.  An outline of the flow chart:

1. If content parses as valid JSON
1.*. Parse JSON
1.1. Iontains a "ciphertext" field -> JWE + JSON
1.2. Contains a "payload" field -> JWS + JSON
1.3. Else fail
2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
2.*. Split on "."
2.1. If 5 components -> JWE + compact
2.2. If 3 components -> JWS + compact
2.3. Else fail
3. Else fail

There's also the question of which document this goes in.  It would be a
natural thing for a combined JWS+JWE document, but we don't have one of
those :(




On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com>w=
rote:

>  There is a defined algorithm to distinguish between the JWS and JWE
> objects in the third paragraph of
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section=
-4
> .****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 20, 2013 8:15 AM
> *To:* Mike Jones
> *Cc:* jose@ietf.org
>
> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
> ** **
>
> Multiplexing JWE and JWS under a single JOSE media type only makes sense
> if there's a defined algorithm to demux them.  So if you want to do this,
> you would need to write down the algorithm.****
>
> ** **
>
> Personally, it seems simpler and clearer to me to just have the four
> current types, so that you know which type of object you're dealing with,
> and in what serialization, without having to do content sniffing.****
>
> ** **
>
> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> The JWS and JWE documents currently define these MIME types for the
> convenience of applications that may want to use them:****
>
>                 application/jws****
>
>                 application/jws+json****
>
>                 application/jwe****
>
>                 application/jwe+json****
>
>  ****
>
> That being said, I=92m not aware of any uses of these by applications at
> present.  Thus, I think that makes it fair game to ask whether we want to
> keep them or remove them =96 in which case, if applications ever needed t=
hem,
> they could define them later.****
>
>  ****
>
> Another dimension of this question for JWS and JWE is that it=92s not cle=
ar
> that the four types application/jws, application/jws+json, application/jw=
e,
> and application/jwe+json are even the right ones.  It might be more usefu=
l
> to have generic application/jose and application/jose+json types, which
> could hold either JWS or JWE objects respectively using the compact or JS=
ON
> serializations (although I=92m not advocating adding them at this time).*=
***
>
>  ****
>
> Having different JWS versus JWE MIME types apparently did contribute to a=
t
> least Dick=92s confusion about the purpose of the =93typ=94 field, so del=
eting
> them could help eliminate this possibility of confusion in the future.
> Thus, I=92m increasingly convinced we should get rid of the JWS and JWE t=
ypes
> and leave it up to applications to define the types they need, when they
> need them.****
>
>  ****
>
> Do people have use cases for these four MIME types now or should we leave
> them to future specs to define, if needed?****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> P.S.  For completeness, I=92ll add that the JWK document also defines the=
se
> MIME types:****
>
>                 application/jwk+json****
>
>                 application/jwk-set+json****
>
>  ****
>
> There are already clear use cases for these types, so I=92m not advocatin=
g
> deleting them, but wanted to call that out explicitly.  For instance, whe=
n
> retrieving a JWK Set document referenced by a =93jku=94 header parameter,=
 I
> believe that the result should use the application/jwk-set+json type.  (I=
n
> fact, I=92ll add this to the specs, unless there are any objections.)
> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
> application/jwk+json.  Both could also be as =93cty=94 values when encryp=
ting
> JWKs and JWK Sets, in contexts where that that would be useful.****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>

--001a11c3124265ba3504df98b9aa
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">That algorithm is part of the story, but it&#39;s incomple=
te. =A0What we need is an algorithm that starts with an arbitrary octet str=
ing and sorts by JWS/JWE and serialization. =A0An outline of the flow chart=
:<div>
<br></div><div>1. If content parses as valid JSON</div><div>1.*. Parse JSON=
</div><div>1.1. Iontains a &quot;ciphertext&quot; field -&gt; JWE + JSON</d=
iv><div>1.2. Contains a &quot;payload&quot; field -&gt; JWS + JSON</div>
<div>1.3. Else fail</div><div>2. Else if content matches the regex &quot;^[=
a-zA-Z0-9_.-]*$&quot;</div><div>2.*. Split on &quot;.&quot;</div><div>2.1. =
If 5 components -&gt; JWE + compact</div><div>2.2. If 3 components -&gt; JW=
S + compact</div>
<div>2.3. Else fail</div><div>3. Else fail</div><div><br></div><div>There&#=
39;s also the question of which document this goes in. =A0It would be a nat=
ural thing for a combined JWS+JWE document, but we don&#39;t have one of th=
ose :(</div>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_bl=
ank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a defined algori=
thm to distinguish between the JWS and JWE objects in the third paragraph o=
f
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-1=
1#section-4" target=3D"_blank">
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4=
</a>.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span></p><div class=3D"im"><br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<u></u><u></u></div><p></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Multiplexing JWE and JWS under a single JOSE media t=
ype only makes sense if there&#39;s a defined algorithm to demux them. =A0S=
o if you want to do this, you would need to write down the algorithm.<u></u=
><u></u></p>
<div><div class=3D"h5">
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Personally, it seems simpler and clearer to me to ju=
st have the four current types, so that you know which type of object you&#=
39;re dealing with, and in what serialization, without having to do content=
 sniffing.<u></u><u></u></p>

</div>
</div></div></div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:<u></=
u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">That being said, I=92m not aware of any uses of thes=
e by applications at present.=A0 Thus, I think that makes it fair game to a=
sk whether we want to keep them or remove them =96 in which
 case, if applications ever needed them, they could define them later.<u></=
u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it=92s not clear that the four types application/jws, application/jw=
s+json, application/jwe, and application/jwe+json are
 even the right ones.=A0 It might be more useful to have generic applicatio=
n/jose and application/jose+json types, which could hold either JWS or JWE =
objects respectively using the compact or JSON serializations (although I=
=92m not advocating adding them at this
 time).<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick=92s confusion about the purpose of the =
=93typ=94 field, so deleting them could help eliminate this
 possibility of confusion in the future.=A0 Thus, I=92m increasingly convin=
ced we should get rid of the JWS and JWE types and leave it up to applicati=
ons to define the types they need, when they need them.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?<u></u><u><=
/u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u><=
/u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">P.S.=A0 For completeness, I=92ll add that the JWK do=
cument also defines these MIME types:<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk-set+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I=92m not advocating deleting them, but wanted to call that out explicitl=
y.=A0 For instance, when retrieving a JWK Set document
 referenced by a =93jku=94 header parameter, I believe that the result shou=
ld use the application/jwk-set+json type.=A0 (In fact, I=92ll add this to t=
he specs, unless there are any objections.)=A0 Likewise, draft-miller-jose-=
jwe-protected-jwk-02 already uses application/jwk+json.=A0
 Both could also be as =93cty=94 values when encrypting JWKs and JWK Sets, =
in contexts where that that would be useful.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c3124265ba3504df98b9aa--

From mamille2@cisco.com  Thu Jun 20 10:32:46 2013
Return-Path: <mamille2@cisco.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD9E21F9E88 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XILr5NUGYXQ3 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:32:41 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 1A38821F9E74 for <jose@ietf.org>; Thu, 20 Jun 2013 10:32:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12285; q=dns/txt; s=iport; t=1371749561; x=1372959161; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=VFNnsgBFaU0ynD+yeSn2oKr8d7wDUTPCGwLdVj4JhMU=; b=GCaUSFS2G5x0hXvEtDwlE9iaq99mnfT6cNZuzA2CpQlblUeJjadMqNm4 GIXddLiLOFIvgm52QztxcKPAWuMDzZ8HFp1J4N1kRGEtkXfNY8Hr/u/EQ ZCbU2IirII39fhvtE45ffuRAwQfx7D6AgD2xTx7qAOaXIvkCdG8jeTbwg g=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAAQ7w1GtJV2a/2dsb2JhbABbgwkxSb82fBZ0giMBAQEDAQEBASRHCwULAgEIDgMEAQELHQcCJQsUCQgBAQQOBQgGh3oGDLwjjxgxBwSCfGEDkAOBLIc9kBuDD4Io
X-IronPort-AV: E=Sophos;i="4.87,906,1363132800";  d="p7s'?scan'208";a="222449264"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 20 Jun 2013 17:32:40 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r5KHWeX0029398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Jun 2013 17:32:40 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Thu, 20 Jun 2013 12:32:40 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQBZwJSAAAAltAAAAx++gAABhYWA
Date: Thu, 20 Jun 2013 17:32:39 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com>
In-Reply-To: <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.129.24.59]
Content-Type: multipart/signed; boundary="Apple-Mail=_47B6FCFC-03C8-414A-B2DF-778204E264D8"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 17:32:46 -0000

--Apple-Mail=_47B6FCFC-03C8-414A-B2DF-778204E264D8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I just want to say that I think having a media type is important and =
useful.  It might not be important and useful for JWT or OAuth or =
OpenID-Connect, but I can think of many applications that would make use =
of them if at all possible.

I personally don't care if it's a generic media type or individual =
application/jwe and application/jws.  However, I think a generic media =
type would require a separate document; trying to fit this into the one =
shared document (JWA) seems wrong.


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

PS: I've found +json useful for other things, because I do have =
applications that present in different formats (right now that's usually =
+xml).  While there's not a simple corollary with XML-based concepts, I =
think there will be corollaries in the future (e.g., CBOR).  Having them =
now means we're not painted into a corner if (when) we look at JOSE2 and =
support for binary representations.

On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx>
 wrote:

> That algorithm is part of the story, but it's incomplete.  What we =
need is
> an algorithm that starts with an arbitrary octet string and sorts by
> JWS/JWE and serialization.  An outline of the flow chart:
>=20
> 1. If content parses as valid JSON
> 1.*. Parse JSON
> 1.1. Iontains a "ciphertext" field -> JWE + JSON
> 1.2. Contains a "payload" field -> JWS + JSON
> 1.3. Else fail
> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
> 2.*. Split on "."
> 2.1. If 5 components -> JWE + compact
> 2.2. If 3 components -> JWS + compact
> 2.3. Else fail
> 3. Else fail
>=20
> There's also the question of which document this goes in.  It would be =
a
> natural thing for a combined JWS+JWE document, but we don't have one =
of
> those :(
>=20
>=20
>=20
>=20
> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones =
<Michael.Jones@microsoft.com>wrote:
>=20
>> There is a defined algorithm to distinguish between the JWS and JWE
>> objects in the third paragraph of
>> =
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-=
4
>> .****
>>=20
>> ** **
>>=20
>>                                                            -- =
Mike****
>>=20
>> ** **
>>=20
>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>> *Sent:* Thursday, June 20, 2013 8:15 AM
>> *To:* Mike Jones
>> *Cc:* jose@ietf.org
>>=20
>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE =
MIME
>> types?****
>>=20
>> ** **
>>=20
>> Multiplexing JWE and JWS under a single JOSE media type only makes =
sense
>> if there's a defined algorithm to demux them.  So if you want to do =
this,
>> you would need to write down the algorithm.****
>>=20
>> ** **
>>=20
>> Personally, it seems simpler and clearer to me to just have the four
>> current types, so that you know which type of object you're dealing =
with,
>> and in what serialization, without having to do content sniffing.****
>>=20
>> ** **
>>=20
>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones =
<Michael.Jones@microsoft.com>
>> wrote:****
>>=20
>> The JWS and JWE documents currently define these MIME types for the
>> convenience of applications that may want to use them:****
>>=20
>>                application/jws****
>>=20
>>                application/jws+json****
>>=20
>>                application/jwe****
>>=20
>>                application/jwe+json****
>>=20
>> ****
>>=20
>> That being said, I=92m not aware of any uses of these by applications =
at
>> present.  Thus, I think that makes it fair game to ask whether we =
want to
>> keep them or remove them =96 in which case, if applications ever =
needed them,
>> they could define them later.****
>>=20
>> ****
>>=20
>> Another dimension of this question for JWS and JWE is that it=92s not =
clear
>> that the four types application/jws, application/jws+json, =
application/jwe,
>> and application/jwe+json are even the right ones.  It might be more =
useful
>> to have generic application/jose and application/jose+json types, =
which
>> could hold either JWS or JWE objects respectively using the compact =
or JSON
>> serializations (although I=92m not advocating adding them at this =
time).****
>>=20
>> ****
>>=20
>> Having different JWS versus JWE MIME types apparently did contribute =
to at
>> least Dick=92s confusion about the purpose of the =93typ=94 field, so =
deleting
>> them could help eliminate this possibility of confusion in the =
future.
>> Thus, I=92m increasingly convinced we should get rid of the JWS and =
JWE types
>> and leave it up to applications to define the types they need, when =
they
>> need them.****
>>=20
>> ****
>>=20
>> Do people have use cases for these four MIME types now or should we =
leave
>> them to future specs to define, if needed?****
>>=20
>> ****
>>=20
>>                                                                -- =
Mike***
>> *
>>=20
>> ****
>>=20
>> P.S.  For completeness, I=92ll add that the JWK document also defines =
these
>> MIME types:****
>>=20
>>                application/jwk+json****
>>=20
>>                application/jwk-set+json****
>>=20
>> ****
>>=20
>> There are already clear use cases for these types, so I=92m not =
advocating
>> deleting them, but wanted to call that out explicitly.  For instance, =
when
>> retrieving a JWK Set document referenced by a =93jku=94 header =
parameter, I
>> believe that the result should use the application/jwk-set+json type. =
 (In
>> fact, I=92ll add this to the specs, unless there are any objections.)
>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
>> application/jwk+json.  Both could also be as =93cty=94 values when =
encrypting
>> JWKs and JWK Sets, in contexts where that that would be useful.****
>>=20
>> ****
>>=20
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose****
>>=20
>> ** **
>>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_47B6FCFC-03C8-414A-B2DF-778204E264D8
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMezCCBjQw
ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX
DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK
75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC
+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD
z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr
/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc
fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG
XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt
UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R
HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv
sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq
+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT
zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq
Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1
9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPzCCBSeg
AwIBAgIDBoRIMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN
MTMwNDMwMjE1NDQyWhcNMTQwNTAyMDUzOTA0WjBbMRkwFwYDVQQNExBiN2F6NndOY0t0R3JtMEpF
MRswGQYDVQQDDBJtYW1pbGxlMkBjaXNjby5jb20xITAfBgkqhkiG9w0BCQEWEm1hbWlsbGUyQGNp
c2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJbKBMsG+9UFTx9uq/bhhXgu
vJvO8z7cwKaqqwZhVf5z/kHFyCNijtmTOE+YXjA8mWR4aoBwB5SvGypI/cJUofJ+AlBTC4g+RMx/
K0Ab4/jQqTQz9CDzMOB+Wm+rt8ZJ7A8ZzOJmNDAsf/VvB8l2A1SQz1UsAixgH16NTr8SlblAXEKk
4hwpCudUiNjjQokqJ0H686UBKVorcZSgXaza8XMqGtJF/8mNhR9GQYi7Xht1ky+9LFOrto2daZto
KJRwMeVusVdHUeKEQSu7jztw8HchH3KEb7Q+r5X+hhDZoddfKE8d5eyPuhiZdrzv7OlNZ0fSLdx7
3AE3nx9/R5YlXucCAwEAAaOCAtgwggLUMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQW
MBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUxGd+/qrdVudHrIKkw5xOMY7eaLUwHwYD
VR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWFtaWxsZTJAY2lzY28u
Y29tMIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9m
IHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBw
dXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYG
A1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4G
CCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy
dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAlDhXbGEI7lbqUcu5r2JHZaMsbRZda/99ZqODzWGX
0llou9jGccsAWDPPwRRe2+ROpXfH4cuJZElTcLDeZSp/qpXKhjYieFSX8+Ml9sKEj5UOSqQLyoLk
PtrIJV12Jk3nuG2Jc0UeEnGwK/aqtzy7+bfEVI0ziyVM2gChHh0RH74KyiwYWknbOTRIkZcz/ulE
DVFQp63uj6wfmDNvAUHBAdhKVqA1S/rfP1KcDZpf1NfvwXJibiqTRA6K1EOxTJOP41n/XdvHqHXL
RWL2xrOUI9/URANr/ok3OrsuZEMFnAAGefS1bWS/hFtUGVkHGiKEBbyDW7da2ULXbuC7umrQnzGC
A28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDAJBgUrDgMCGgUA
oIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MjAxNzMy
MzlaMCMGCSqGSIb3DQEJBDEWBBSsgiO2toISgDS9LFKEPO46n0GFxTCBpQYJKwYBBAGCNxAEMYGX
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3Mg
MSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDCBpwYLKoZIhvcNAQkQAgsxgZeg
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBoRIMA0GCSqGSIb3DQEBAQUABIIBAEGv
qO494/0ccRwIZOVhjeSzPJw2wAJrUfw3w+H2QwDgUdjoE04s54UvyplYQxUgVPUm6et5ekkPL+Wu
/Yqm8PXP9MfYTiLnCQAnLhfIPbqrclH2nPLu4YIxoUQhgQbeOkav4jL0NCZ+dnufLjaEXOstV983
oeyo5y9eA3Dw36Kf2UMei364fSxj9AcYQiLtRftylxxi3pcEmFiv9IlCdhiCc6gx0NqhIG96xJMv
7Iztt2xzclrlG76QQAcWzgsjZs7H0PilWmCDB+WaSrCbPE014eej4yUUcYGlRWKmN57YWUFS6FiB
zkXKdbLXE2rglP3sIyIGeFSewAn6hiuxjh4AAAAAAAA=

--Apple-Mail=_47B6FCFC-03C8-414A-B2DF-778204E264D8--

From jricher@mitre.org  Thu Jun 20 10:34:52 2013
Return-Path: <jricher@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1AE821F9F40 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level: 
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgLokNWUuywg for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:34:42 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2345621F9F42 for <jose@ietf.org>; Thu, 20 Jun 2013 10:34:41 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 79ECE1F0BC5; Thu, 20 Jun 2013 13:34:40 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 5DFC61F0352; Thu, 20 Jun 2013 13:34:40 -0400 (EDT)
Received: from [10.146.15.13] (129.83.31.56) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server (TLS) id 14.2.342.3; Thu, 20 Jun 2013 13:34:40 -0400
Message-ID: <51C33CEE.4040802@mitre.org>
Date: Thu, 20 Jun 2013 13:33:34 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com>
Content-Type: multipart/alternative; boundary="------------080903050101090301090209"
X-Originating-IP: [129.83.31.56]
Cc: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 17:34:52 -0000

--------------080903050101090301090209
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

It seems like JWA is quickly becoming the document with all the actual 
concrete content in it.

  -- Justin

On 06/20/2013 01:32 PM, Matt Miller (mamille2) wrote:
> I just want to say that I think having a media type is important and useful.  It might not be important and useful for JWT or OAuth or OpenID-Connect, but I can think of many applications that would make use of them if at all possible.
>
> I personally don't care if it's a generic media type or individual application/jwe and application/jws.  However, I think a generic media type would require a separate document; trying to fit this into the one shared document (JWA) seems wrong.
>
>
> - m&m
>
> Matt Miller < mamille2@cisco.com >
> Cisco Systems, Inc.
>
> PS: I've found +json useful for other things, because I do have applications that present in different formats (right now that's usually +xml).  While there's not a simple corollary with XML-based concepts, I think there will be corollaries in the future (e.g., CBOR).  Having them now means we're not painted into a corner if (when) we look at JOSE2 and support for binary representations.
>
> On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx>
>   wrote:
>
>> That algorithm is part of the story, but it's incomplete.  What we need is
>> an algorithm that starts with an arbitrary octet string and sorts by
>> JWS/JWE and serialization.  An outline of the flow chart:
>>
>> 1. If content parses as valid JSON
>> 1.*. Parse JSON
>> 1.1. Iontains a "ciphertext" field -> JWE + JSON
>> 1.2. Contains a "payload" field -> JWS + JSON
>> 1.3. Else fail
>> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
>> 2.*. Split on "."
>> 2.1. If 5 components -> JWE + compact
>> 2.2. If 3 components -> JWS + compact
>> 2.3. Else fail
>> 3. Else fail
>>
>> There's also the question of which document this goes in.  It would be a
>> natural thing for a combined JWS+JWE document, but we don't have one of
>> those :(
>>
>>
>>
>>
>> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com>wrote:
>>
>>> There is a defined algorithm to distinguish between the JWS and JWE
>>> objects in the third paragraph of
>>> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4
>>> .****
>>>
>>> ** **
>>>
>>>                                                             -- Mike****
>>>
>>> ** **
>>>
>>> *From:* Richard Barnes [mailto:rlb@ipv.sx]
>>> *Sent:* Thursday, June 20, 2013 8:15 AM
>>> *To:* Mike Jones
>>> *Cc:* jose@ietf.org
>>>
>>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
>>> types?****
>>>
>>> ** **
>>>
>>> Multiplexing JWE and JWS under a single JOSE media type only makes sense
>>> if there's a defined algorithm to demux them.  So if you want to do this,
>>> you would need to write down the algorithm.****
>>>
>>> ** **
>>>
>>> Personally, it seems simpler and clearer to me to just have the four
>>> current types, so that you know which type of object you're dealing with,
>>> and in what serialization, without having to do content sniffing.****
>>>
>>> ** **
>>>
>>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com>
>>> wrote:****
>>>
>>> The JWS and JWE documents currently define these MIME types for the
>>> convenience of applications that may want to use them:****
>>>
>>>                 application/jws****
>>>
>>>                 application/jws+json****
>>>
>>>                 application/jwe****
>>>
>>>                 application/jwe+json****
>>>
>>> ****
>>>
>>> That being said, I'm not aware of any uses of these by applications at
>>> present.  Thus, I think that makes it fair game to ask whether we want to
>>> keep them or remove them -- in which case, if applications ever needed them,
>>> they could define them later.****
>>>
>>> ****
>>>
>>> Another dimension of this question for JWS and JWE is that it's not clear
>>> that the four types application/jws, application/jws+json, application/jwe,
>>> and application/jwe+json are even the right ones.  It might be more useful
>>> to have generic application/jose and application/jose+json types, which
>>> could hold either JWS or JWE objects respectively using the compact or JSON
>>> serializations (although I'm not advocating adding them at this time).****
>>>
>>> ****
>>>
>>> Having different JWS versus JWE MIME types apparently did contribute to at
>>> least Dick's confusion about the purpose of the "typ" field, so deleting
>>> them could help eliminate this possibility of confusion in the future.
>>> Thus, I'm increasingly convinced we should get rid of the JWS and JWE types
>>> and leave it up to applications to define the types they need, when they
>>> need them.****
>>>
>>> ****
>>>
>>> Do people have use cases for these four MIME types now or should we leave
>>> them to future specs to define, if needed?****
>>>
>>> ****
>>>
>>>                                                                 -- Mike***
>>> *
>>>
>>> ****
>>>
>>> P.S.  For completeness, I'll add that the JWK document also defines these
>>> MIME types:****
>>>
>>>                 application/jwk+json****
>>>
>>>                 application/jwk-set+json****
>>>
>>> ****
>>>
>>> There are already clear use cases for these types, so I'm not advocating
>>> deleting them, but wanted to call that out explicitly.  For instance, when
>>> retrieving a JWK Set document referenced by a "jku" header parameter, I
>>> believe that the result should use the application/jwk-set+json type.  (In
>>> fact, I'll add this to the specs, unless there are any objections.)
>>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
>>> application/jwk+json.  Both could also be as "cty" values when encrypting
>>> JWKs and JWK Sets, in contexts where that that would be useful.****
>>>
>>> ****
>>>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose****
>>>
>>> ** **
>>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------080903050101090301090209
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    It seems like JWA is quickly becoming the document with all the
    actual concrete content in it. <br>
    <br>
    &nbsp;-- Justin<br>
    <br>
    <div class="moz-cite-prefix">On 06/20/2013 01:32 PM, Matt Miller
      (mamille2) wrote:<br>
    </div>
    <blockquote
cite="mid:BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com"
      type="cite">
      <pre wrap="">I just want to say that I think having a media type is important and useful.  It might not be important and useful for JWT or OAuth or OpenID-Connect, but I can think of many applications that would make use of them if at all possible.

I personally don't care if it's a generic media type or individual application/jwe and application/jws.  However, I think a generic media type would require a separate document; trying to fit this into the one shared document (JWA) seems wrong.


- m&amp;m

Matt Miller &lt; <a class="moz-txt-link-abbreviated" href="mailto:mamille2@cisco.com">mamille2@cisco.com</a> &gt;
Cisco Systems, Inc.

PS: I've found +json useful for other things, because I do have applications that present in different formats (right now that's usually +xml).  While there's not a simple corollary with XML-based concepts, I think there will be corollaries in the future (e.g., CBOR).  Having them now means we're not painted into a corner if (when) we look at JOSE2 and support for binary representations.

On Jun 20, 2013, at 10:49 AM, Richard Barnes <a class="moz-txt-link-rfc2396E" href="mailto:rlb@ipv.sx">&lt;rlb@ipv.sx&gt;</a>
 wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">That algorithm is part of the story, but it's incomplete.  What we need is
an algorithm that starts with an arbitrary octet string and sorts by
JWS/JWE and serialization.  An outline of the flow chart:

1. If content parses as valid JSON
1.*. Parse JSON
1.1. Iontains a "ciphertext" field -&gt; JWE + JSON
1.2. Contains a "payload" field -&gt; JWS + JSON
1.3. Else fail
2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
2.*. Split on "."
2.1. If 5 components -&gt; JWE + compact
2.2. If 3 components -&gt; JWS + compact
2.3. Else fail
3. Else fail

There's also the question of which document this goes in.  It would be a
natural thing for a combined JWS+JWE document, but we don't have one of
those :(




On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <a class="moz-txt-link-rfc2396E" href="mailto:Michael.Jones@microsoft.com">&lt;Michael.Jones@microsoft.com&gt;</a>wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">There is a defined algorithm to distinguish between the JWS and JWE
objects in the third paragraph of
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4">http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4</a>
.****

** **

                                                           -- Mike****

** **

*From:* Richard Barnes [<a class="moz-txt-link-freetext" href="mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
*Sent:* Thursday, June 20, 2013 8:15 AM
*To:* Mike Jones
*Cc:* <a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>

*Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
types?****

** **

Multiplexing JWE and JWS under a single JOSE media type only makes sense
if there's a defined algorithm to demux them.  So if you want to do this,
you would need to write down the algorithm.****

** **

Personally, it seems simpler and clearer to me to just have the four
current types, so that you know which type of object you're dealing with,
and in what serialization, without having to do content sniffing.****

** **

On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <a class="moz-txt-link-rfc2396E" href="mailto:Michael.Jones@microsoft.com">&lt;Michael.Jones@microsoft.com&gt;</a>
wrote:****

The JWS and JWE documents currently define these MIME types for the
convenience of applications that may want to use them:****

               application/jws****

               application/jws+json****

               application/jwe****

               application/jwe+json****

****

That being said, I&#8217;m not aware of any uses of these by applications at
present.  Thus, I think that makes it fair game to ask whether we want to
keep them or remove them &#8211; in which case, if applications ever needed them,
they could define them later.****

****

Another dimension of this question for JWS and JWE is that it&#8217;s not clear
that the four types application/jws, application/jws+json, application/jwe,
and application/jwe+json are even the right ones.  It might be more useful
to have generic application/jose and application/jose+json types, which
could hold either JWS or JWE objects respectively using the compact or JSON
serializations (although I&#8217;m not advocating adding them at this time).****

****

Having different JWS versus JWE MIME types apparently did contribute to at
least Dick&#8217;s confusion about the purpose of the &#8220;typ&#8221; field, so deleting
them could help eliminate this possibility of confusion in the future.
Thus, I&#8217;m increasingly convinced we should get rid of the JWS and JWE types
and leave it up to applications to define the types they need, when they
need them.****

****

Do people have use cases for these four MIME types now or should we leave
them to future specs to define, if needed?****

****

                                                               -- Mike***
*

****

P.S.  For completeness, I&#8217;ll add that the JWK document also defines these
MIME types:****

               application/jwk+json****

               application/jwk-set+json****

****

There are already clear use cases for these types, so I&#8217;m not advocating
deleting them, but wanted to call that out explicitly.  For instance, when
retrieving a JWK Set document referenced by a &#8220;jku&#8221; header parameter, I
believe that the result should use the application/jwk-set+json type.  (In
fact, I&#8217;ll add this to the specs, unless there are any objections.)
Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
application/jwk+json.  Both could also be as &#8220;cty&#8221; values when encrypting
JWKs and JWK Sets, in contexts where that that would be useful.****

****


_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose****">https://www.ietf.org/mailman/listinfo/jose****</a>

** **

</pre>
        </blockquote>
        <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
      </blockquote>
      <pre wrap="">
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080903050101090301090209--

From Michael.Jones@microsoft.com  Thu Jun 20 10:41:40 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08BBD21F9E14 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level: 
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=-0.212,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5o7jJYAEqph for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 10:41:34 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id B388B21F9DFB for <jose@ietf.org>; Thu, 20 Jun 2013 10:41:34 -0700 (PDT)
Received: from BL2FFO11FD006.protection.gbl (10.173.161.203) by BL2FFO11HUB026.protection.gbl (10.173.161.50) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 17:41:20 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD006.mail.protection.outlook.com (10.173.161.2) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 17:41:20 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 17:41:08 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQBPRl+AAAAPBOAAAzZugAAByUwg
Date: Thu, 20 Jun 2013 17:41:07 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678798E6@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com>
In-Reply-To: <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.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_4E1F6AAD24975D4BA5B1680429673943678798E6TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(199002)(189002)(51444003)(24454002)(49866001)(50986001)(54356001)(19300405003)(46102001)(44976003)(76796001)(53806001)(33656001)(74366001)(47736001)(81542001)(47446002)(77982001)(81342001)(51856001)(4396001)(77096001)(76786001)(16297215004)(79102001)(512954002)(15202345003)(6806003)(16406001)(76482001)(71186001)(54316002)(74502001)(16236675002)(47976001)(69226001)(66066001)(80022001)(65816001)(56816003)(74706001)(74662001)(55846006)(59766001)(31966008)(56776001)(20776003)(74876001)(63696002)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB026; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 17:41:40 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678798E6TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I know of no use cases where the application won't know whether it's using =
the Compact Serialization or the JSON Serialization.

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 20, 2013 9:49 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?

That algorithm is part of the story, but it's incomplete.  What we need is =
an algorithm that starts with an arbitrary octet string and sorts by JWS/JW=
E and serialization.  An outline of the flow chart:

1. If content parses as valid JSON
1.*. Parse JSON
1.1. Iontains a "ciphertext" field -> JWE + JSON
1.2. Contains a "payload" field -> JWS + JSON
1.3. Else fail
2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
2.*. Split on "."
2.1. If 5 components -> JWE + compact
2.2. If 3 components -> JWS + compact
2.3. Else fail
3. Else fail

There's also the question of which document this goes in.  It would be a na=
tural thing for a combined JWS+JWE document, but we don't have one of those=
 :(



On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
There is a defined algorithm to distinguish between the JWS and JWE objects=
 in the third paragraph of http://tools.ietf.org/html/draft-ietf-jose-json-=
web-encryption-11#section-4.

                                                            -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, June 20, 2013 8:15 AM
To: Mike Jones
Cc: jose@ietf.org<mailto:jose@ietf.org>

Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?

Multiplexing JWE and JWS under a single JOSE media type only makes sense if=
 there's a defined algorithm to demux them.  So if you want to do this, you=
 would need to write down the algorithm.

Personally, it seems simpler and clearer to me to just have the four curren=
t types, so that you know which type of object you're dealing with, and in =
what serialization, without having to do content sniffing.

On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
The JWS and JWE documents currently define these MIME types for the conveni=
ence of applications that may want to use them:
                application/jws
                application/jws+json
                application/jwe
                application/jwe+json

That being said, I'm not aware of any uses of these by applications at pres=
ent.  Thus, I think that makes it fair game to ask whether we want to keep =
them or remove them - in which case, if applications ever needed them, they=
 could define them later.

Another dimension of this question for JWS and JWE is that it's not clear t=
hat the four types application/jws, application/jws+json, application/jwe, =
and application/jwe+json are even the right ones.  It might be more useful =
to have generic application/jose and application/jose+json types, which cou=
ld hold either JWS or JWE objects respectively using the compact or JSON se=
rializations (although I'm not advocating adding them at this time).

Having different JWS versus JWE MIME types apparently did contribute to at =
least Dick's confusion about the purpose of the "typ" field, so deleting th=
em could help eliminate this possibility of confusion in the future.  Thus,=
 I'm increasingly convinced we should get rid of the JWS and JWE types and =
leave it up to applications to define the types they need, when they need t=
hem.

Do people have use cases for these four MIME types now or should we leave t=
hem to future specs to define, if needed?

                                                                -- Mike

P.S.  For completeness, I'll add that the JWK document also defines these M=
IME types:
                application/jwk+json
                application/jwk-set+json

There are already clear use cases for these types, so I'm not advocating de=
leting them, but wanted to call that out explicitly.  For instance, when re=
trieving a JWK Set document referenced by a "jku" header parameter, I belie=
ve that the result should use the application/jwk-set+json type.  (In fact,=
 I'll add this to the specs, unless there are any objections.)  Likewise, d=
raft-miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.  B=
oth could also be as "cty" values when encrypting JWKs and JWK Sets, in con=
texts where that that would be useful.


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B1680429673943678798E6TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I know of no use cases wh=
ere the application won&#8217;t know whether it&#8217;s using the Compact S=
erialization or the JSON Serialization.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 20, 2013 9:49 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">That algorithm is part of the story, but it's incomp=
lete. &nbsp;What we need is an algorithm that starts with an arbitrary octe=
t string and sorts by JWS/JWE and serialization. &nbsp;An outline of the fl=
ow chart:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1. If content parses as valid JSON<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1.*. Parse JSON<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1.1. Iontains a &quot;ciphertext&quot; field -&gt; J=
WE &#43; JSON<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1.2. Contains a &quot;payload&quot; field -&gt; JWS =
&#43; JSON<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1.3. Else fail<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2. Else if content matches the regex &quot;^[a-zA-Z0=
-9_.-]*$&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2.*. Split on &quot;.&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2.1. If 5 components -&gt; JWE &#43; compact<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal">2.2. If 3 components -&gt; JWS &#43; compact<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal">2.3. Else fail<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">3. Else fail<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There's also the question of which document this goe=
s in. &nbsp;It would be a natural thing for a combined JWS&#43;JWE document=
, but we don't have one of those :(<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">There is a defined algorithm to disting=
uish between the JWS and JWE objects in the third paragraph
 of <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encrypti=
on-11#section-4" target=3D"_blank">
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4=
</a>.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [mailto=
:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Multiplexing JWE and JWS under a single JOSE media type only makes=
 sense if there's a defined algorithm to demux them. &nbsp;So if you want t=
o do this, you would need to write down the
 algorithm.<o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Personally, it seems simpler and clearer to me to just have the fo=
ur current types, so that you know which type of object you're dealing with=
, and in what serialization, without
 having to do content sniffing.<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The JWS and JWE documents currently define these MIME types for th=
e convenience of applications that may want to use them:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jws<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwe<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">That being said, I&#8217;m not aware of any uses of these by appli=
cations at present.&nbsp; Thus, I think that makes it fair game to ask whet=
her we want to keep them or remove them &#8211; in which
 case, if applications ever needed them, they could define them later.<o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Another dimension of this question for JWS and JWE is that it&#821=
7;s not clear that the four types application/jws, application/jws&#43;json=
, application/jwe, and application/jwe&#43;json are
 even the right ones.&nbsp; It might be more useful to have generic applica=
tion/jose and application/jose&#43;json types, which could hold either JWS =
or JWE objects respectively using the compact or JSON serializations (altho=
ugh I&#8217;m not advocating adding them at this
 time).<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Having different JWS versus JWE MIME types apparently did contribu=
te to at least Dick&#8217;s confusion about the purpose of the &#8220;typ&#=
8221; field, so deleting them could help eliminate this
 possibility of confusion in the future.&nbsp; Thus, I&#8217;m increasingly=
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.<o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Do people have use cases for these four MIME types now or should w=
e leave them to future specs to define, if needed?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; -- Mike<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">P.S.&nbsp; For completeness, I&#8217;ll add that the JWK document =
also defines these MIME types:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;json<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">There are already clear use cases for these types, so I&#8217;m no=
t advocating deleting them, but wanted to call that out explicitly.&nbsp; F=
or instance, when retrieving a JWK Set document
 referenced by a &#8220;jku&#8221; header parameter, I believe that the res=
ult should use the application/jwk-set&#43;json type.&nbsp; (In fact, I&#82=
17;ll add this to the specs, unless there are any objections.)&nbsp; Likewi=
se, draft-miller-jose-jwe-protected-jwk-02 already uses application/jwk&#43=
;json.&nbsp;
 Both could also be as &#8220;cty&#8221; values when encrypting JWKs and JW=
K Sets, in contexts where that that would be useful.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678798E6TK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Thu Jun 20 11:17:33 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7A121F9C12 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.136
X-Spam-Level: 
X-Spam-Status: No, score=-2.136 tagged_above=-999 required=5 tests=[AWL=-0.269, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vK03Pb3w8kpB for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:17:28 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id 0FBCE21F9C0C for <jose@ietf.org>; Thu, 20 Jun 2013 11:17:27 -0700 (PDT)
Received: from BN1BFFO11FD012.protection.gbl (10.58.52.203) by BN1AFFO11HUB039.protection.gbl (10.58.52.150) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 17:47:11 +0000
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD012.mail.protection.outlook.com (10.58.53.72) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 17:47:11 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC105.redmond.corp.microsoft.com ([157.54.80.48]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 17:47:05 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQBPRl+AAAAPBOAAAzZugAABhYSAAABQGPA=
Date: Thu, 20 Jun 2013 17:47:04 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436787993E@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.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_4E1F6AAD24975D4BA5B16804296739436787993ETK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51704005)(189002)(199002)(51444003)(13464003)(24454002)(377454003)(66066001)(6806003)(65816001)(76786001)(74876001)(19300405003)(74706001)(33656001)(16406001)(4396001)(74366001)(71186001)(81342001)(69226001)(54356001)(51856001)(63696002)(77982001)(59766001)(79102001)(55846006)(47446002)(50986001)(80022001)(512954002)(47976001)(20776003)(74502001)(54316002)(46102001)(56776001)(77096001)(31966008)(56816003)(47736001)(49866001)(74662001)(81542001)(53806001)(76482001)(76796001)(15202345003)(16236675002)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB039; H:TK5EX14HUBC105.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:17:33 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436787993ETK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Editorially, if we do decide to add application/jose and application/jose+j=
son MIME types, I would register them in draft-ietf-jose-json-web-signature=
, just like other registry content shared between JWS and JWE, such as the =
JSON Web Signature and Encryption Header Parameters Registry<http://tools.i=
etf.org/html/draft-ietf-jose-json-web-signature-11#page-18>.

                                                            -- Mike



-----Original Message-----
From: Matt Miller (mamille2) [mailto:mamille2@cisco.com]
Sent: Thursday, June 20, 2013 10:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?



I just want to say that I think having a media type is important and useful=
.  It might not be important and useful for JWT or OAuth or OpenID-Connect,=
 but I can think of many applications that would make use of them if at all=
 possible.



I personally don't care if it's a generic media type or individual applicat=
ion/jwe and application/jws.  However, I think a generic media type would r=
equire a separate document; trying to fit this into the one shared document=
 (JWA) seems wrong.





- m&m



Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >

Cisco Systems, Inc.



PS: I've found +json useful for other things, because I do have application=
s that present in different formats (right now that's usually +xml).  While=
 there's not a simple corollary with XML-based concepts, I think there will=
 be corollaries in the future (e.g., CBOR).  Having them now means we're no=
t painted into a corner if (when) we look at JOSE2 and support for binary r=
epresentations.



On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>=
>

wrote:



> That algorithm is part of the story, but it's incomplete.  What we need i=
s

> an algorithm that starts with an arbitrary octet string and sorts by

> JWS/JWE and serialization.  An outline of the flow chart:

>

> 1. If content parses as valid JSON

> 1.*. Parse JSON

> 1.1. Iontains a "ciphertext" field -> JWE + JSON

> 1.2. Contains a "payload" field -> JWS + JSON

> 1.3. Else fail

> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"

> 2.*. Split on "."

> 2.1. If 5 components -> JWE + compact

> 2.2. If 3 components -> JWS + compact

> 2.3. Else fail

> 3. Else fail

>

> There's also the question of which document this goes in.  It would be a

> natural thing for a combined JWS+JWE document, but we don't have one of

> those :(

>

>

>

>

> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>wrote:

>

>> There is a defined algorithm to distinguish between the JWS and JWE

>> objects in the third paragraph of

>> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#sectio=
n-4

>> .****

>>

>> ** **

>>

>>                                                            -- Mike****

>>

>> ** **

>>

>> *From:* Richard Barnes [mailto:rlb@ipv.sx]

>> *Sent:* Thursday, June 20, 2013 8:15 AM

>> *To:* Mike Jones

>> *Cc:* jose@ietf.org<mailto:jose@ietf.org>

>>

>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME

>> types?****

>>

>> ** **

>>

>> Multiplexing JWE and JWS under a single JOSE media type only makes sense

>> if there's a defined algorithm to demux them.  So if you want to do this=
,

>> you would need to write down the algorithm.****

>>

>> ** **

>>

>> Personally, it seems simpler and clearer to me to just have the four

>> current types, so that you know which type of object you're dealing with=
,

>> and in what serialization, without having to do content sniffing.****

>>

>> ** **

>>

>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>

>> wrote:****

>>

>> The JWS and JWE documents currently define these MIME types for the

>> convenience of applications that may want to use them:****

>>

>>                application/jws****

>>

>>                application/jws+json****

>>

>>                application/jwe****

>>

>>                application/jwe+json****

>>

>> ****

>>

>> That being said, I'm not aware of any uses of these by applications at

>> present.  Thus, I think that makes it fair game to ask whether we want t=
o

>> keep them or remove them - in which case, if applications ever needed th=
em,

>> they could define them later.****

>>

>> ****

>>

>> Another dimension of this question for JWS and JWE is that it's not clea=
r

>> that the four types application/jws, application/jws+json, application/j=
we,

>> and application/jwe+json are even the right ones.  It might be more usef=
ul

>> to have generic application/jose and application/jose+json types, which

>> could hold either JWS or JWE objects respectively using the compact or J=
SON

>> serializations (although I'm not advocating adding them at this time).**=
**

>>

>> ****

>>

>> Having different JWS versus JWE MIME types apparently did contribute to =
at

>> least Dick's confusion about the purpose of the "typ" field, so deleting

>> them could help eliminate this possibility of confusion in the future.

>> Thus, I'm increasingly convinced we should get rid of the JWS and JWE ty=
pes

>> and leave it up to applications to define the types they need, when they

>> need them.****

>>

>> ****

>>

>> Do people have use cases for these four MIME types now or should we leav=
e

>> them to future specs to define, if needed?****

>>

>> ****

>>

>>                                                                -- Mike**=
*

>> *

>>

>> ****

>>

>> P.S.  For completeness, I'll add that the JWK document also defines thes=
e

>> MIME types:****

>>

>>                application/jwk+json****

>>

>>                application/jwk-set+json****

>>

>> ****

>>

>> There are already clear use cases for these types, so I'm not advocating

>> deleting them, but wanted to call that out explicitly.  For instance, wh=
en

>> retrieving a JWK Set document referenced by a "jku" header parameter, I

>> believe that the result should use the application/jwk-set+json type.  (=
In

>> fact, I'll add this to the specs, unless there are any objections.)

>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses

>> application/jwk+json.  Both could also be as "cty" values when encryptin=
g

>> JWKs and JWK Sets, in contexts where that that would be useful.****

>>

>> ****

>>

>>

>> _______________________________________________

>> jose mailing list

>> jose@ietf.org<mailto:jose@ietf.org>

>> https://www.ietf.org/mailman/listinfo/jose****

>>

>> ** **

>>

> _______________________________________________

> jose mailing list

> jose@ietf.org<mailto:jose@ietf.org>

> https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B16804296739436787993ETK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Editorially, if we do decide to add application/jose=
 and application/jose&#43;json MIME types, I would register them in draft-i=
etf-jose-json-web-signature, just like other registry content shared betwee=
n JWS and JWE, such as the
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11=
#page-18">
JSON Web Signature and Encryption Header Parameters Registry</a>.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; -- Mike<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: Matt Miller (mamille2) [mailto:mamille2@cisco.com] <br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; jose@ietf.org<br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I just want to say that I think having a media ty=
pe is important and useful.&nbsp; It might not be important and useful for =
JWT or OAuth or OpenID-Connect, but I can think of many applications that w=
ould make use of them if at all possible.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I personally don't care if it's a generic media t=
ype or individual application/jwe and application/jws.&nbsp; However, I thi=
nk a generic media type would require a separate document; trying to fit th=
is into the one shared document (JWA) seems
 wrong.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- m&amp;m<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Matt Miller &lt; <a href=3D"mailto:mamille2@cisco=
.com"><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.=
com</span></a> &gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Cisco Systems, Inc.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">PS: I've found &#43;json useful for other things,=
 because I do have applications that present in different formats (right no=
w that's usually &#43;xml).&nbsp; While there's not a simple corollary with=
 XML-based concepts, I think there will be corollaries
 in the future (e.g., CBOR).&nbsp; Having them now means we're not painted =
into a corner if (when) we look at JOSE2 and support for binary representat=
ions.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx"><span style=3D"color:windowtext;text-decorati=
on:none">rlb@ipv.sx</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; That algorithm is part of the story, but it'=
s incomplete.&nbsp; What we need is<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; an algorithm that starts with an arbitrary o=
ctet string and sorts by<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; JWS/JWE and serialization.&nbsp; An outline =
of the flow chart:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1. If content parses as valid JSON<o:p></o:p=
></p>
<p class=3D"MsoPlainText">&gt; 1.*. Parse JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.1. Iontains a &quot;ciphertext&quot; field=
 -&gt; JWE &#43; JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.2. Contains a &quot;payload&quot; field -&=
gt; JWS &#43; JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2. Else if content matches the regex &quot;^=
[a-zA-Z0-9_.-]*$&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.*. Split on &quot;.&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.1. If 5 components -&gt; JWE &#43; compact=
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.2. If 3 components -&gt; JWS &#43; compact=
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; There's also the question of which document =
this goes in.&nbsp; It would be a<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; natural thing for a combined JWS&#43;JWE doc=
ument, but we don't have one of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; those :(<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones=
 &lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span style=3D"color:wi=
ndowtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wr=
ote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; There is a defined algorithm to distingu=
ish between the JWS and JWE<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; objects in the third paragraph of<o:p></=
o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"http://tools.ietf.org/html/dr=
aft-ietf-jose-json-web-encryption-11#section-4">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><o:p></o:p=
></p>
<p class=3D"MsoPlainText">&gt;&gt; .****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; -- Mike****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *From:* Richard Barnes [<a href=3D"mailt=
o:rlb@ipv.sx"><span style=3D"color:windowtext;text-decoration:none">mailto:=
rlb@ipv.sx</span></a>]<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *To:* Mike Jones<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org"><=
span style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></=
a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Subject:* Re: [jose] Should we keep or =
remove the JOSE JWS and JWE MIME<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; types?****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Multiplexing JWE and JWS under a single =
JOSE media type only makes sense<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; if there's a defined algorithm to demux =
them.&nbsp; So if you want to do this,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; you would need to write down the algorit=
hm.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Personally, it seems simpler and clearer=
 to me to just have the four<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; current types, so that you know which ty=
pe of object you're dealing with,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and in what serialization, without havin=
g to do content sniffing.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jo=
nes &lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span style=3D"color=
:windowtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt=
;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; wrote:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; The JWS and JWE documents currently defi=
ne these MIME types for the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; convenience of applications that may wan=
t to use them:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws****<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe****<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; That being said, I&#8217;m not aware of =
any uses of these by applications at<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; present.&nbsp; Thus, I think that makes =
it fair game to ask whether we want to<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; keep them or remove them &#8211; in whic=
h case, if applications ever needed them,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; they could define them later.****<o:p></=
o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Another dimension of this question for J=
WS and JWE is that it&#8217;s not clear<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; that the four types application/jws, app=
lication/jws&#43;json, application/jwe,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and application/jwe&#43;json are even th=
e right ones.&nbsp; It might be more useful<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; to have generic application/jose and app=
lication/jose&#43;json types, which<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; could hold either JWS or JWE objects res=
pectively using the compact or JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; serializations (although I&#8217;m not a=
dvocating adding them at this time).****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Having different JWS versus JWE MIME typ=
es apparently did contribute to at<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; least Dick&#8217;s confusion about the p=
urpose of the &#8220;typ&#8221; field, so deleting<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; them could help eliminate this possibili=
ty of confusion in the future.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Thus, I&#8217;m increasingly convinced w=
e should get rid of the JWS and JWE types<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and leave it up to applications to defin=
e the types they need, when they<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; need them.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Do people have use cases for these four =
MIME types now or should we leave<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; them to future specs to define, if neede=
d?****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; P.S.&nbsp; For completeness, I&#8217;ll =
add that the JWK document also defines these<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; MIME types:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;j=
son****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; There are already clear use cases for th=
ese types, so I&#8217;m not advocating<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; deleting them, but wanted to call that o=
ut explicitly.&nbsp; For instance, when<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; retrieving a JWK Set document referenced=
 by a &#8220;jku&#8221; header parameter, I<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; believe that the result should use the a=
pplication/jwk-set&#43;json type.&nbsp; (In<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; fact, I&#8217;ll add this to the specs, =
unless there are any objections.)<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Likewise, draft-miller-jose-jwe-protecte=
d-jwk-02 already uses<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; application/jwk&#43;json.&nbsp; Both cou=
ld also be as &#8220;cty&#8221; values when encrypting<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; JWKs and JWK Sets, in contexts where tha=
t that would be useful.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ________________________________________=
_______<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"mailto:jose@ietf.org"><span s=
tyle=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"https://www.ietf.org/mailman/=
listinfo/jose****">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/jose****</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; ____________________________________________=
___<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <a href=3D"mailto:jose@ietf.org"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o=
:p></p>
<p class=3D"MsoPlainText">&gt; <a href=3D"https://www.ietf.org/mailman/list=
info/jose"><span style=3D"color:windowtext;text-decoration:none">https://ww=
w.ietf.org/mailman/listinfo/jose</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436787993ETK5EX14MBXC283r_--

From rlb@ipv.sx  Thu Jun 20 11:39:09 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6E4B21F9F35 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.024
X-Spam-Level: 
X-Spam-Status: No, score=-0.024 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hb8NNXrU7LzI for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:39:04 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4270221F9EBC for <jose@ietf.org>; Thu, 20 Jun 2013 11:39:02 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id g12so8188716oah.39 for <jose@ietf.org>; Thu, 20 Jun 2013 11:39:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ubd5qb45cgjQ9jYgdQRtDTjshuDcJjwfa/E17KWtLMQ=; b=NAOG6UB7fdJn1LBc6yyVHTQH8O6V2EZ4crtVLI344YnPcOf4H6Z0Vyls5INfQFWCMU kwQ1HXfQgswPDjfcg7FjPDOcMhJK8joSjRWd+6f19kTjMGu8BCdjTkNqVYR3OGbs+p6d S1N7yE6tr1ADefmpjjeggYkN8OF7nB++O7SAoMB4vPHYPabN18b+1e7Y7jtvIGBm80FF S8YD88RFDO+Iat9wrwAAhnUKuiYxDzUNXVBbgvmWPGheBC7DIyu/p70VmQl79z1R4+W7 9DQHcS90FethS6RNy/TM3WAcDTSMugi9s1S5LItU/VjkHcGHMU36Dmh+vTH8KNNcE942 y0Qw==
MIME-Version: 1.0
X-Received: by 10.182.237.77 with SMTP id va13mr2126786obc.65.1371753541771; Thu, 20 Jun 2013 11:39:01 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 11:39:01 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678798E6@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678798E6@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 14:39:01 -0400
Message-ID: <CAL02cgTf6-kbQmkOxgJX-aSDtLmcNPifPLVVwei9naBuELQ3OA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cdcc93b6bc04df9a4280
X-Gm-Message-State: ALoCoQl/sxvMgaDJfwKN4KSNsvMXeb69fEosy18A1k3kIxYTBwNQwgrEuGgCKA4NFk27SyIjeqoe
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:39:09 -0000

--e89a8ff1cdcc93b6bc04df9a4280
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

What you mean to say is that there are really two algorithms here,
depending on the media type:

application/jose
-> If 3 components, JWS
-> If 5 components, JWE

application/jose+json
-> If 'payloaod', JWS
-> If 'ciphertext', JWE




On Thu, Jun 20, 2013 at 1:41 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  I know of no use cases where the application won=92t know whether it=92s
> using the Compact Serialization or the JSON Serialization.****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 20, 2013 9:49 AM
>
> *To:* Mike Jones
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
> ** **
>
> That algorithm is part of the story, but it's incomplete.  What we need i=
s
> an algorithm that starts with an arbitrary octet string and sorts by
> JWS/JWE and serialization.  An outline of the flow chart:****
>
> ** **
>
> 1. If content parses as valid JSON****
>
> 1.*. Parse JSON****
>
> 1.1. Iontains a "ciphertext" field -> JWE + JSON****
>
> 1.2. Contains a "payload" field -> JWS + JSON****
>
> 1.3. Else fail****
>
> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"****
>
> 2.*. Split on "."****
>
> 2.1. If 5 components -> JWE + compact****
>
> 2.2. If 3 components -> JWS + compact****
>
> 2.3. Else fail****
>
> 3. Else fail****
>
> ** **
>
> There's also the question of which document this goes in.  It would be a
> natural thing for a combined JWS+JWE document, but we don't have one of
> those :(****
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
> There is a defined algorithm to distinguish between the JWS and JWE
> objects in the third paragraph of
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section=
-4
> .****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 20, 2013 8:15 AM
> *To:* Mike Jones
> *Cc:* jose@ietf.org****
>
>
> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
>  ****
>
> Multiplexing JWE and JWS under a single JOSE media type only makes sense
> if there's a defined algorithm to demux them.  So if you want to do this,
> you would need to write down the algorithm.****
>
>  ****
>
> Personally, it seems simpler and clearer to me to just have the four
> current types, so that you know which type of object you're dealing with,
> and in what serialization, without having to do content sniffing.****
>
>  ****
>
> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> The JWS and JWE documents currently define these MIME types for the
> convenience of applications that may want to use them:****
>
>                 application/jws****
>
>                 application/jws+json****
>
>                 application/jwe****
>
>                 application/jwe+json****
>
>  ****
>
> That being said, I=92m not aware of any uses of these by applications at
> present.  Thus, I think that makes it fair game to ask whether we want to
> keep them or remove them =96 in which case, if applications ever needed t=
hem,
> they could define them later.****
>
>  ****
>
> Another dimension of this question for JWS and JWE is that it=92s not cle=
ar
> that the four types application/jws, application/jws+json, application/jw=
e,
> and application/jwe+json are even the right ones.  It might be more usefu=
l
> to have generic application/jose and application/jose+json types, which
> could hold either JWS or JWE objects respectively using the compact or JS=
ON
> serializations (although I=92m not advocating adding them at this time).*=
***
>
>  ****
>
> Having different JWS versus JWE MIME types apparently did contribute to a=
t
> least Dick=92s confusion about the purpose of the =93typ=94 field, so del=
eting
> them could help eliminate this possibility of confusion in the future.
> Thus, I=92m increasingly convinced we should get rid of the JWS and JWE t=
ypes
> and leave it up to applications to define the types they need, when they
> need them.****
>
>  ****
>
> Do people have use cases for these four MIME types now or should we leave
> them to future specs to define, if needed?****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> P.S.  For completeness, I=92ll add that the JWK document also defines the=
se
> MIME types:****
>
>                 application/jwk+json****
>
>                 application/jwk-set+json****
>
>  ****
>
> There are already clear use cases for these types, so I=92m not advocatin=
g
> deleting them, but wanted to call that out explicitly.  For instance, whe=
n
> retrieving a JWK Set document referenced by a =93jku=94 header parameter,=
 I
> believe that the result should use the application/jwk-set+json type.  (I=
n
> fact, I=92ll add this to the specs, unless there are any objections.)
> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
> application/jwk+json.  Both could also be as =93cty=94 values when encryp=
ting
> JWKs and JWK Sets, in contexts where that that would be useful.****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
> ** **
>

--e89a8ff1cdcc93b6bc04df9a4280
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What you mean to say is that there are really two algorith=
ms here, depending on the media type:<div><br></div><div>application/jose</=
div><div>-&gt; If 3 components, JWS</div><div>-&gt; If 5 components, JWE</d=
iv>
<div><br></div><div>application/jose+json</div><div>-&gt; If &#39;payloaod&=
#39;, JWS</div><div>-&gt; If &#39;ciphertext&#39;, JWE</div><div><br></div>=
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">
On Thu, Jun 20, 2013 at 1:41 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=
=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@mic=
rosoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">






<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I know of no use cases wh=
ere the application won=92t know whether it=92s using the Compact Serializa=
tion or the JSON Serialization.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 9:49 AM</span></p><div><div class=3D"h=
5"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<u></u><u></u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">That algorithm is part of the story, but it&#39;s in=
complete. =A0What we need is an algorithm that starts with an arbitrary oct=
et string and sorts by JWS/JWE and serialization. =A0An outline of the flow=
 chart:<u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1. If content parses as valid JSON<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1.*. Parse JSON<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1.1. Iontains a &quot;ciphertext&quot; field -&gt; J=
WE + JSON<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1.2. Contains a &quot;payload&quot; field -&gt; JWS =
+ JSON<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1.3. Else fail<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. Else if content matches the regex &quot;^[a-zA-Z0=
-9_.-]*$&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2.*. Split on &quot;.&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2.1. If 5 components -&gt; JWE + compact<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">2.2. If 3 components -&gt; JWS + compact<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">2.3. Else fail<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">3. Else fail<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">There&#39;s also the question of which document this=
 goes in. =A0It would be a natural thing for a combined JWS+JWE document, b=
ut we don&#39;t have one of those :(<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a defined algori=
thm to distinguish between the JWS and JWE objects in the third paragraph
 of <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encrypti=
on-11#section-4" target=3D"_blank">
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4=
</a>.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 8:15 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a></span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Multiplexing JWE and JWS under a single JOSE media t=
ype only makes sense if there&#39;s a defined algorithm to demux them. =A0S=
o if you want to do this, you would need to write down the
 algorithm.<u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Personally, it seems simpler and clearer to me to ju=
st have the four current types, so that you know which type of object you&#=
39;re dealing with, and in what serialization, without
 having to do content sniffing.<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:<u></=
u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">That being said, I=92m not aware of any uses of thes=
e by applications at present.=A0 Thus, I think that makes it fair game to a=
sk whether we want to keep them or remove them =96 in which
 case, if applications ever needed them, they could define them later.<u></=
u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it=92s not clear that the four types application/jws, application/jw=
s+json, application/jwe, and application/jwe+json are
 even the right ones.=A0 It might be more useful to have generic applicatio=
n/jose and application/jose+json types, which could hold either JWS or JWE =
objects respectively using the compact or JSON serializations (although I=
=92m not advocating adding them at this
 time).<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick=92s confusion about the purpose of the =
=93typ=94 field, so deleting them could help eliminate this
 possibility of confusion in the future.=A0 Thus, I=92m increasingly convin=
ced we should get rid of the JWS and JWE types and leave it up to applicati=
ons to define the types they need, when they need them.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?<u></u><u><=
/u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u><=
/u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">P.S.=A0 For completeness, I=92ll add that the JWK do=
cument also defines these MIME types:<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk-set+json<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I=92m not advocating deleting them, but wanted to call that out explicitl=
y.=A0 For instance, when retrieving a JWK Set document
 referenced by a =93jku=94 header parameter, I believe that the result shou=
ld use the application/jwk-set+json type.=A0 (In fact, I=92ll add this to t=
he specs, unless there are any objections.)=A0 Likewise, draft-miller-jose-=
jwe-protected-jwk-02 already uses application/jwk+json.=A0
 Both could also be as =93cty=94 values when encrypting JWKs and JWK Sets, =
in contexts where that that would be useful.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--e89a8ff1cdcc93b6bc04df9a4280--

From rlb@ipv.sx  Thu Jun 20 11:41:19 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E2321F9EF6 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.046
X-Spam-Level: 
X-Spam-Status: No, score=0.046 tagged_above=-999 required=5 tests=[AWL=-0.260,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RDNS_NONE=0.1, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdp-3xVZylW9 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:41:15 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 837A921F9DBE for <jose@ietf.org>; Thu, 20 Jun 2013 11:41:15 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so8382861oah.10 for <jose@ietf.org>; Thu, 20 Jun 2013 11:41:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=vyEiOKI9nBupjEcDnF3qLFtSkyk4FaWv+XLfRAomPSA=; b=ITGUYvTCbjA81cu3OQZVZ2G2VXMu0MlzhH4tugT41HA32sjL7AVStewV3q66dWqG2A PfZJGvmKTPu6OlnorGkFA11ow6IyWDf5TL6meMmajnFOm83MbHU1a9X1X1GNnzsArlP1 7+cOCR+nKx17v/WFjDrSlRbmeIGWJQYwX2UmvI7umvAO071Ns9AJQGeJ3cpeXlX1N8pO XMcAMr/ABuTmybl4PhPWdqOapYawcJiEQP2LagqQfiu9TPzdooif1NUvsaEUaWay4A07 WR/t8wJbYbX2ZBKM3n2EGunHv7oGdWaylAObx281nkJZFjE4idpRxBDvgI395CkJ5E3u /awA==
MIME-Version: 1.0
X-Received: by 10.182.61.105 with SMTP id o9mr2065419obr.54.1371753675026; Thu, 20 Jun 2013 11:41:15 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 11:41:14 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
Date: Thu, 20 Jun 2013 14:41:14 -0400
Message-ID: <CAL02cgThKXYYmKpB+_XVCE3cBPDsX=cKnNaEYdKOEqz1cy8aLw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8fb1ea3085050004df9a4ac6
X-Gm-Message-State: ALoCoQlxVkZv+eIU/bXB/mbHA84MGbimzMWGFaRh6zCp7a7JAyUMdVI+Wj/aqbNTyhT0QxXLHXpa
Cc: "jose@ietf.org" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: [jose] Common elements (was: Re: Should we keep or remove the JOSE JWS and JWE MIME types?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:41:20 -0000

--e89a8fb1ea3085050004df9a4ac6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

While we're at it, you could move over the header parameters that are
shared between the two.  Namely all but "enc" and "zip".  ("epk", and "apu"
should move to JWA.)

And once you do that, it seems more and more like JWE is becoming the
little brother to JWS, in which case we might as well combine them.


On Thu, Jun 20, 2013 at 1:47 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Editorially, if we do decide to add application/jose and
> application/jose+json MIME types, I would register them in
> draft-ietf-jose-json-web-signature, just like other registry content shar=
ed
> between JWS and JWE, such as the JSON Web Signature and Encryption Header
> Parameters Registry<http://tools.ietf.org/html/draft-ietf-jose-json-web-s=
ignature-11#page-18>
> .****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> -----Original Message-----
> From: Matt Miller (mamille2) [mailto:mamille2@cisco.com]
> Sent: Thursday, June 20, 2013 10:33 AM
> To: Richard Barnes
> Cc: Mike Jones; jose@ietf.org
> Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?
>
> ** **
>
> I just want to say that I think having a media type is important and
> useful.  It might not be important and useful for JWT or OAuth or
> OpenID-Connect, but I can think of many applications that would make use =
of
> them if at all possible.****
>
> ** **
>
> I personally don't care if it's a generic media type or individual
> application/jwe and application/jws.  However, I think a generic media ty=
pe
> would require a separate document; trying to fit this into the one shared
> document (JWA) seems wrong.****
>
> ** **
>
> ** **
>
> - m&m****
>
> ** **
>
> Matt Miller < mamille2@cisco.com >****
>
> Cisco Systems, Inc.****
>
> ** **
>
> PS: I've found +json useful for other things, because I do have
> applications that present in different formats (right now that's usually
> +xml).  While there's not a simple corollary with XML-based concepts, I
> think there will be corollaries in the future (e.g., CBOR).  Having them
> now means we're not painted into a corner if (when) we look at JOSE2 and
> support for binary representations.****
>
> ** **
>
> On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx>****
>
> wrote:****
>
> ** **
>
> > That algorithm is part of the story, but it's incomplete.  What we need
> is****
>
> > an algorithm that starts with an arbitrary octet string and sorts by***=
*
>
> > JWS/JWE and serialization.  An outline of the flow chart:****
>
> > ****
>
> > 1. If content parses as valid JSON****
>
> > 1.*. Parse JSON****
>
> > 1.1. Iontains a "ciphertext" field -> JWE + JSON****
>
> > 1.2. Contains a "payload" field -> JWS + JSON****
>
> > 1.3. Else fail****
>
> > 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"****
>
> > 2.*. Split on "."****
>
> > 2.1. If 5 components -> JWE + compact****
>
> > 2.2. If 3 components -> JWS + compact****
>
> > 2.3. Else fail****
>
> > 3. Else fail****
>
> > ****
>
> > There's also the question of which document this goes in.  It would be =
a
> ****
>
> > natural thing for a combined JWS+JWE document, but we don't have one of=
*
> ***
>
> > those :(****
>
> > ****
>
> > ****
>
> > ****
>
> > ****
>
> > On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <
> Michael.Jones@microsoft.com>wrote:****
>
> > ****
>
> >> There is a defined algorithm to distinguish between the JWS and JWE***=
*
>
> >> objects in the third paragraph of****
>
> >>
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section=
-4
> ****
>
> >> .********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >>                                                            -- Mike****=
*
> ***
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]****
>
> >> *Sent:* Thursday, June 20, 2013 8:15 AM****
>
> >> *To:* Mike Jones****
>
> >> *Cc:* jose@ietf.org****
>
> >> ****
>
> >> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME
> ****
>
> >> types?********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Multiplexing JWE and JWS under a single JOSE media type only makes sen=
se
> ****
>
> >> if there's a defined algorithm to demux them.  So if you want to do
> this,****
>
> >> you would need to write down the algorithm.********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Personally, it seems simpler and clearer to me to just have the four**=
*
> *
>
> >> current types, so that you know which type of object you're dealing
> with,****
>
> >> and in what serialization, without having to do content sniffing.*****=
*
> **
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <
> Michael.Jones@microsoft.com>****
>
> >> wrote:********
>
> >> ****
>
> >> The JWS and JWE documents currently define these MIME types for the***=
*
>
> >> convenience of applications that may want to use them:********
>
> >> ****
>
> >>                application/jws********
>
> >> ****
>
> >>                application/jws+json********
>
> >> ****
>
> >>                application/jwe********
>
> >> ****
>
> >>                application/jwe+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> That being said, I=92m not aware of any uses of these by applications =
at*
> ***
>
> >> present.  Thus, I think that makes it fair game to ask whether we want
> to****
>
> >> keep them or remove them =96 in which case, if applications ever neede=
d
> them,****
>
> >> they could define them later.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Another dimension of this question for JWS and JWE is that it=92s not
> clear****
>
> >> that the four types application/jws, application/jws+json,
> application/jwe,****
>
> >> and application/jwe+json are even the right ones.  It might be more
> useful****
>
> >> to have generic application/jose and application/jose+json types, whic=
h
> ****
>
> >> could hold either JWS or JWE objects respectively using the compact or
> JSON****
>
> >> serializations (although I=92m not advocating adding them at this
> time).********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Having different JWS versus JWE MIME types apparently did contribute t=
o
> at****
>
> >> least Dick=92s confusion about the purpose of the =93typ=94 field, so =
deleting
> ****
>
> >> them could help eliminate this possibility of confusion in the future.=
*
> ***
>
> >> Thus, I=92m increasingly convinced we should get rid of the JWS and JW=
E
> types****
>
> >> and leave it up to applications to define the types they need, when th=
ey
> ****
>
> >> need them.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Do people have use cases for these four MIME types now or should we
> leave****
>
> >> them to future specs to define, if needed?********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >>                                                                --
> Mike*******
>
> >> *****
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> P.S.  For completeness, I=92ll add that the JWK document also defines
> these****
>
> >> MIME types:********
>
> >> ****
>
> >>                application/jwk+json********
>
> >> ****
>
> >>                application/jwk-set+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> There are already clear use cases for these types, so I=92m not advoca=
ting
> ****
>
> >> deleting them, but wanted to call that out explicitly.  For instance,
> when****
>
> >> retrieving a JWK Set document referenced by a =93jku=94 header paramet=
er, I
> ****
>
> >> believe that the result should use the application/jwk-set+json type.
> (In****
>
> >> fact, I=92ll add this to the specs, unless there are any objections.)*=
***
>
> >> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses****
>
> >> application/jwk+json.  Both could also be as =93cty=94 values when
> encrypting****
>
> >> JWKs and JWK Sets, in contexts where that that would be useful.*******=
*
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> ****
>
> >> _______________________________________________****
>
> >> jose mailing list****
>
> >> jose@ietf.org****
>
> >> https://www.ietf.org/mailman/listinfo/jose********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> > _______________________________________________****
>
> > jose mailing list****
>
> > jose@ietf.org****
>
> > https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>

--e89a8fb1ea3085050004df9a4ac6
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>While we&#39;re at it, you could move over the header=
 parameters that are shared between the two. =A0Namely all but &quot;enc&qu=
ot; and &quot;zip&quot;. =A0(&quot;epk&quot;, and &quot;apu&quot; should mo=
ve to JWA.)</div>
<div><br></div>And once you do that, it seems more and more like JWE is bec=
oming the little brother to JWS, in which case we might as well combine the=
m.<br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Jun 20, 2013 at 1:47 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">Editorially, if we do decide to add application/jose=
 and application/jose+json MIME types, I would register them in draft-ietf-=
jose-json-web-signature, just like other registry content shared between JW=
S and JWE, such as the
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11=
#page-18" target=3D"_blank">
JSON Web Signature and Encryption Header Parameters Registry</a>.<span clas=
s=3D"HOEnZb"><font color=3D"#888888"><u></u><u></u></font></span></p><span =
class=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></=
p></font></span><div><div class=3D"h5">
<p><u></u>=A0<u></u></p>
<p>-----Original Message-----<br>
From: Matt Miller (mamille2) [mailto:<a href=3D"mailto:mamille2@cisco.com" =
target=3D"_blank">mamille2@cisco.com</a>] <br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@iet=
f.org</a><br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?</p>
<p><u></u>=A0<u></u></p>
<p>I just want to say that I think having a media type is important and use=
ful.=A0 It might not be important and useful for JWT or OAuth or OpenID-Con=
nect, but I can think of many applications that would make use of them if a=
t all possible.<u></u><u></u></p>

<p><u></u>=A0<u></u></p>
<p>I personally don&#39;t care if it&#39;s a generic media type or individu=
al application/jwe and application/jws.=A0 However, I think a generic media=
 type would require a separate document; trying to fit this into the one sh=
ared document (JWA) seems
 wrong.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p><u></u>=A0<u></u></p>
<p>- m&amp;m<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.com</=
span></a> &gt;<u></u><u></u></p>
<p>Cisco Systems, Inc.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>PS: I&#39;ve found +json useful for other things, because I do have appl=
ications that present in different formats (right now that&#39;s usually +x=
ml).=A0 While there&#39;s not a simple corollary with XML-based concepts, I=
 think there will be corollaries
 in the future (e.g., CBOR).=A0 Having them now means we&#39;re not painted=
 into a corner if (when) we look at JOSE2 and support for binary representa=
tions.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;<a href=3D"mailto:rlb@i=
pv.sx" target=3D"_blank"><span style=3D"color:windowtext;text-decoration:no=
ne">rlb@ipv.sx</span></a>&gt;<u></u><u></u></p>
<p>wrote:<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; That algorithm is part of the story, but it&#39;s incomplete.=A0 Wh=
at we need is<u></u><u></u></p>
<p>&gt; an algorithm that starts with an arbitrary octet string and sorts b=
y<u></u><u></u></p>
<p>&gt; JWS/JWE and serialization.=A0 An outline of the flow chart:<u></u><=
u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; 1. If content parses as valid JSON<u></u><u></u></p>
<p>&gt; 1.*. Parse JSON<u></u><u></u></p>
<p>&gt; 1.1. Iontains a &quot;ciphertext&quot; field -&gt; JWE + JSON<u></u=
><u></u></p>
<p>&gt; 1.2. Contains a &quot;payload&quot; field -&gt; JWS + JSON<u></u><u=
></u></p>
<p>&gt; 1.3. Else fail<u></u><u></u></p>
<p>&gt; 2. Else if content matches the regex &quot;^[a-zA-Z0-9_.-]*$&quot;<=
u></u><u></u></p>
<p>&gt; 2.*. Split on &quot;.&quot;<u></u><u></u></p>
<p>&gt; 2.1. If 5 components -&gt; JWE + compact<u></u><u></u></p>
<p>&gt; 2.2. If 3 components -&gt; JWS + compact<u></u><u></u></p>
<p>&gt; 2.3. Else fail<u></u><u></u></p>
<p>&gt; 3. Else fail<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; There&#39;s also the question of which document this goes in.=A0 It=
 would be a<u></u><u></u></p>
<p>&gt; natural thing for a combined JWS+JWE document, but we don&#39;t hav=
e one of<u></u><u></u></p>
<p>&gt; those :(<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:windowt=
ext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wrote:<=
u></u><u></u></p>

<p>&gt; <u></u><u></u></p>
<p>&gt;&gt; There is a defined algorithm to distinguish between the JWS and=
 JWE<u></u><u></u></p>
<p>&gt;&gt; objects in the third paragraph of<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-=
encryption-11#section-4" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><u></u><u>=
</u></p>
<p>&gt;&gt; .****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *From:* Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D=
"_blank"><span style=3D"color:windowtext;text-decoration:none">mailto:rlb@i=
pv.sx</span></a>]<u></u><u></u></p>
<p>&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<u></u><u></u></p>
<p>&gt;&gt; *To:* Mike Jones<u></u><u></u></p>
<p>&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span =
style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u>=
</u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and=
 JWE MIME<u></u><u></u></p>
<p>&gt;&gt; types?****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Multiplexing JWE and JWS under a single JOSE media type only ma=
kes sense<u></u><u></u></p>
<p>&gt;&gt; if there&#39;s a defined algorithm to demux them.=A0 So if you =
want to do this,<u></u><u></u></p>
<p>&gt;&gt; you would need to write down the algorithm.****<u></u><u></u></=
p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Personally, it seems simpler and clearer to me to just have the=
 four<u></u><u></u></p>
<p>&gt;&gt; current types, so that you know which type of object you&#39;re=
 dealing with,<u></u><u></u></p>
<p>&gt;&gt; and in what serialization, without having to do content sniffin=
g.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a href=3D"mail=
to:Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:wind=
owtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;<u><=
/u><u></u></p>

<p>&gt;&gt; wrote:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; The JWS and JWE documents currently define these MIME types for=
 the<u></u><u></u></p>
<p>&gt;&gt; convenience of applications that may want to use them:****<u></=
u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; That being said, I=92m not aware of any uses of these by applic=
ations at<u></u><u></u></p>
<p>&gt;&gt; present.=A0 Thus, I think that makes it fair game to ask whethe=
r we want to<u></u><u></u></p>
<p>&gt;&gt; keep them or remove them =96 in which case, if applications eve=
r needed them,<u></u><u></u></p>
<p>&gt;&gt; they could define them later.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Another dimension of this question for JWS and JWE is that it=
=92s not clear<u></u><u></u></p>
<p>&gt;&gt; that the four types application/jws, application/jws+json, appl=
ication/jwe,<u></u><u></u></p>
<p>&gt;&gt; and application/jwe+json are even the right ones.=A0 It might b=
e more useful<u></u><u></u></p>
<p>&gt;&gt; to have generic application/jose and application/jose+json type=
s, which<u></u><u></u></p>
<p>&gt;&gt; could hold either JWS or JWE objects respectively using the com=
pact or JSON<u></u><u></u></p>
<p>&gt;&gt; serializations (although I=92m not advocating adding them at th=
is time).****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Having different JWS versus JWE MIME types apparently did contr=
ibute to at<u></u><u></u></p>
<p>&gt;&gt; least Dick=92s confusion about the purpose of the =93typ=94 fie=
ld, so deleting<u></u><u></u></p>
<p>&gt;&gt; them could help eliminate this possibility of confusion in the =
future.<u></u><u></u></p>
<p>&gt;&gt; Thus, I=92m increasingly convinced we should get rid of the JWS=
 and JWE types<u></u><u></u></p>
<p>&gt;&gt; and leave it up to applications to define the types they need, =
when they<u></u><u></u></p>
<p>&gt;&gt; need them.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Do people have use cases for these four MIME types now or shoul=
d we leave<u></u><u></u></p>
<p>&gt;&gt; them to future specs to define, if needed?****<u></u><u></u></p=
>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike***<u></u><u></u=
></p>
<p>&gt;&gt; *<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; P.S.=A0 For completeness, I=92ll add that the JWK document also=
 defines these<u></u><u></u></p>
<p>&gt;&gt; MIME types:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk-se=
t+json****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; There are already clear use cases for these types, so I=92m not=
 advocating<u></u><u></u></p>
<p>&gt;&gt; deleting them, but wanted to call that out explicitly.=A0 For i=
nstance, when<u></u><u></u></p>
<p>&gt;&gt; retrieving a JWK Set document referenced by a =93jku=94 header =
parameter, I<u></u><u></u></p>
<p>&gt;&gt; believe that the result should use the application/jwk-set+json=
 type.=A0 (In<u></u><u></u></p>
<p>&gt;&gt; fact, I=92ll add this to the specs, unless there are any object=
ions.)<u></u><u></u></p>
<p>&gt;&gt; Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses<u=
></u><u></u></p>
<p>&gt;&gt; application/jwk+json.=A0 Both could also be as =93cty=94 values=
 when encrypting<u></u><u></u></p>
<p>&gt;&gt; JWKs and JWK Sets, in contexts where that that would be useful.=
****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; _______________________________________________<u></u><u></u></=
p>
<p>&gt;&gt; jose mailing list<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><=
u></u></p>
<p>&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose****" targ=
et=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/jose****</span></a><u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt; _______________________________________________<u></u><u></u></p>
<p>&gt; jose mailing list<u></u><u></u></p>
<p>&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u=
></p>
<p>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_b=
lank"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><u></u><u></u></p>
<p><u></u>=A0<u></u></p>
</div></div></div>
</div>

</blockquote></div><br></div></div>

--e89a8fb1ea3085050004df9a4ac6--

From ietf@augustcellars.com  Thu Jun 20 11:50:26 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600EC21E808F for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.184
X-Spam-Level: 
X-Spam-Status: No, score=-3.184 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjWw5BJsQhFh for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:50:21 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id CF95E21E80A8 for <jose@ietf.org>; Thu, 20 Jun 2013 11:50:20 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id DEE1F38EED; Thu, 20 Jun 2013 11:50:19 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Matt Miller \(mamille2\)'" <mamille2@cisco.com>, "'Richard Barnes'" <rlb@ipv.sx>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com>	<4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com>	<BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com> <4E1F6AAD24975D4BA5B16804296739436787993E@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436787993E@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 11:49:24 -0700
Message-ID: <053a01ce6de6$e34775e0$a9d661a0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_053B_01CE6DAC.36EB5D00"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQJdUfWtdvWfIayb6axdJ1IllIJd1wKlu52JAfTxSWECb9SNjAENpF9HAVxiwOKX1YV2MA==
Cc: jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:50:26 -0000

This is a multipart message in MIME format.

------=_NextPart_000_053B_01CE6DAC.36EB5D00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I have a question, why is there both an application/jose and and
application/jose+json.  Why not have just one of them?

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Thursday, June 20, 2013 10:47 AM
To: Matt Miller (mamille2); Richard Barnes
Cc: jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
types?

 

Editorially, if we do decide to add application/jose and
application/jose+json MIME types, I would register them in
draft-ietf-jose-json-web-signature, just like other registry content shared
between JWS and JWE, such as the JSON Web Signature and Encryption Header
Parameters Registry
<http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#page-18> .

 

                                                            -- Mike

 

-----Original Message-----
From: Matt Miller (mamille2) [mailto:mamille2@cisco.com] 
Sent: Thursday, June 20, 2013 10:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
types?

 

I just want to say that I think having a media type is important and useful.
It might not be important and useful for JWT or OAuth or OpenID-Connect, but
I can think of many applications that would make use of them if at all
possible.

 

I personally don't care if it's a generic media type or individual
application/jwe and application/jws.  However, I think a generic media type
would require a separate document; trying to fit this into the one shared
document (JWA) seems wrong.

 

 

- m&m

 

Matt Miller <  <mailto:mamille2@cisco.com> mamille2@cisco.com >

Cisco Systems, Inc.

 

PS: I've found +json useful for other things, because I do have applications
that present in different formats (right now that's usually +xml).  While
there's not a simple corollary with XML-based concepts, I think there will
be corollaries in the future (e.g., CBOR).  Having them now means we're not
painted into a corner if (when) we look at JOSE2 and support for binary
representations.

 

On Jun 20, 2013, at 10:49 AM, Richard Barnes < <mailto:rlb@ipv.sx>
rlb@ipv.sx>

wrote:

 

> That algorithm is part of the story, but it's incomplete.  What we need is

> an algorithm that starts with an arbitrary octet string and sorts by

> JWS/JWE and serialization.  An outline of the flow chart:

> 

> 1. If content parses as valid JSON

> 1.*. Parse JSON

> 1.1. Iontains a "ciphertext" field -> JWE + JSON

> 1.2. Contains a "payload" field -> JWS + JSON

> 1.3. Else fail

> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"

> 2.*. Split on "."

> 2.1. If 5 components -> JWE + compact

> 2.2. If 3 components -> JWS + compact

> 2.3. Else fail

> 3. Else fail

> 

> There's also the question of which document this goes in.  It would be a

> natural thing for a combined JWS+JWE document, but we don't have one of

> those :(

> 

> 

> 

> 

> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <
<mailto:Michael.Jones@microsoft.com> Michael.Jones@microsoft.com>wrote:

> 

>> There is a defined algorithm to distinguish between the JWS and JWE

>> objects in the third paragraph of

>>
<http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4
>
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4

>> .****

>> 

>> ** **

>> 

>>                                                            -- Mike****

>> 

>> ** **

>> 

>> *From:* Richard Barnes [ <mailto:rlb@ipv.sx> mailto:rlb@ipv.sx]

>> *Sent:* Thursday, June 20, 2013 8:15 AM

>> *To:* Mike Jones

>> *Cc:*  <mailto:jose@ietf.org> jose@ietf.org

>> 

>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME

>> types?****

>> 

>> ** **

>> 

>> Multiplexing JWE and JWS under a single JOSE media type only makes sense

>> if there's a defined algorithm to demux them.  So if you want to do this,

>> you would need to write down the algorithm.****

>> 

>> ** **

>> 

>> Personally, it seems simpler and clearer to me to just have the four

>> current types, so that you know which type of object you're dealing with,

>> and in what serialization, without having to do content sniffing.****

>> 

>> ** **

>> 

>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <
<mailto:Michael.Jones@microsoft.com> Michael.Jones@microsoft.com>

>> wrote:****

>> 

>> The JWS and JWE documents currently define these MIME types for the

>> convenience of applications that may want to use them:****

>> 

>>                application/jws****

>> 

>>                application/jws+json****

>> 

>>                application/jwe****

>> 

>>                application/jwe+json****

>> 

>> ****

>> 

>> That being said, I'm not aware of any uses of these by applications at

>> present.  Thus, I think that makes it fair game to ask whether we want to

>> keep them or remove them - in which case, if applications ever needed
them,

>> they could define them later.****

>> 

>> ****

>> 

>> Another dimension of this question for JWS and JWE is that it's not clear

>> that the four types application/jws, application/jws+json,
application/jwe,

>> and application/jwe+json are even the right ones.  It might be more
useful

>> to have generic application/jose and application/jose+json types, which

>> could hold either JWS or JWE objects respectively using the compact or
JSON

>> serializations (although I'm not advocating adding them at this
time).****

>> 

>> ****

>> 

>> Having different JWS versus JWE MIME types apparently did contribute to
at

>> least Dick's confusion about the purpose of the "typ" field, so deleting

>> them could help eliminate this possibility of confusion in the future.

>> Thus, I'm increasingly convinced we should get rid of the JWS and JWE
types

>> and leave it up to applications to define the types they need, when they

>> need them.****

>> 

>> ****

>> 

>> Do people have use cases for these four MIME types now or should we leave

>> them to future specs to define, if needed?****

>> 

>> ****

>> 

>>                                                                -- Mike***

>> *

>> 

>> ****

>> 

>> P.S.  For completeness, I'll add that the JWK document also defines these

>> MIME types:****

>> 

>>                application/jwk+json****

>> 

>>                application/jwk-set+json****

>> 

>> ****

>> 

>> There are already clear use cases for these types, so I'm not advocating

>> deleting them, but wanted to call that out explicitly.  For instance,
when

>> retrieving a JWK Set document referenced by a "jku" header parameter, I

>> believe that the result should use the application/jwk-set+json type.
(In

>> fact, I'll add this to the specs, unless there are any objections.)

>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses

>> application/jwk+json.  Both could also be as "cty" values when encrypting

>> JWKs and JWK Sets, in contexts where that that would be useful.****

>> 

>> ****

>> 

>> 

>> _______________________________________________

>> jose mailing list

>>  <mailto:jose@ietf.org> jose@ietf.org

>>  <https://www.ietf.org/mailman/listinfo/jose****>
https://www.ietf.org/mailman/listinfo/jose****

>> 

>> ** **

>> 

> _______________________________________________

> jose mailing list

>  <mailto:jose@ietf.org> jose@ietf.org

>  <https://www.ietf.org/mailman/listinfo/jose>
https://www.ietf.org/mailman/listinfo/jose

 


------=_NextPart_000_053B_01CE6DAC.36EB5D00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I have a question, why is there both an =
application/jose and and application/jose+json.&nbsp; Why not have just =
one of them?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of =
</b>Mike Jones<br><b>Sent:</b> Thursday, June 20, 2013 10:47 =
AM<br><b>To:</b> Matt Miller (mamille2); Richard Barnes<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: [jose] Should we keep or remove the =
JOSE JWS and JWE MIME types?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Editorially, =
if we do decide to add application/jose and application/jose+json MIME =
types, I would register them in draft-ietf-jose-json-web-signature, just =
like other registry content shared between JWS and JWE, such as the <a =
href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11#=
page-18">JSON Web Signature and Encryption Header Parameters =
Registry</a>.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; -- Mike<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: Matt Miller =
(mamille2) [<a =
href=3D"mailto:mamille2@cisco.com">mailto:mamille2@cisco.com</a>] =
<br>Sent: Thursday, June 20, 2013 10:33 AM<br>To: Richard Barnes<br>Cc: =
Mike Jones; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>Subject: Re: [jose] =
Should we keep or remove the JOSE JWS and JWE MIME =
types?<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>I just want to say that I think having a media type =
is important and useful.&nbsp; It might not be important and useful for =
JWT or OAuth or OpenID-Connect, but I can think of many applications =
that would make use of them if at all possible.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I =
personally don't care if it's a generic media type or individual =
application/jwe and application/jws.&nbsp; However, I think a generic =
media type would require a separate document; trying to fit this into =
the one shared document (JWA) seems wrong.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>- =
m&amp;m<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Matt Miller &lt; <a =
href=3D"mailto:mamille2@cisco.com"><span =
style=3D'color:windowtext;text-decoration:none'>mamille2@cisco.com</span>=
</a> &gt;<o:p></o:p></p><p class=3DMsoPlainText>Cisco Systems, =
Inc.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>PS: I've found +json useful for other things, =
because I do have applications that present in different formats (right =
now that's usually +xml).&nbsp; While there's not a simple corollary =
with XML-based concepts, I think there will be corollaries in the future =
(e.g., CBOR).&nbsp; Having them now means we're not painted into a =
corner if (when) we look at JOSE2 and support for binary =
representations.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>On Jun =
20, 2013, at 10:49 AM, Richard Barnes &lt;<a =
href=3D"mailto:rlb@ipv.sx"><span =
style=3D'color:windowtext;text-decoration:none'>rlb@ipv.sx</span></a>&gt;=
<o:p></o:p></p><p class=3DMsoPlainText>wrote:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&gt; =
That algorithm is part of the story, but it's incomplete.&nbsp; What we =
need is<o:p></o:p></p><p class=3DMsoPlainText>&gt; an algorithm that =
starts with an arbitrary octet string and sorts by<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; JWS/JWE and serialization.&nbsp; An outline of =
the flow chart:<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; 1. If content parses as =
valid JSON<o:p></o:p></p><p class=3DMsoPlainText>&gt; 1.*. Parse =
JSON<o:p></o:p></p><p class=3DMsoPlainText>&gt; 1.1. Iontains a =
&quot;ciphertext&quot; field -&gt; JWE + JSON<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; 1.2. Contains a &quot;payload&quot; field =
-&gt; JWS + JSON<o:p></o:p></p><p class=3DMsoPlainText>&gt; 1.3. Else =
fail<o:p></o:p></p><p class=3DMsoPlainText>&gt; 2. Else if content =
matches the regex &quot;^[a-zA-Z0-9_.-]*$&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; 2.*. Split on &quot;.&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; 2.1. If 5 components -&gt; JWE + =
compact<o:p></o:p></p><p class=3DMsoPlainText>&gt; 2.2. If 3 components =
-&gt; JWS + compact<o:p></o:p></p><p class=3DMsoPlainText>&gt; 2.3. Else =
fail<o:p></o:p></p><p class=3DMsoPlainText>&gt; 3. Else =
fail<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; There's also the question of which document =
this goes in.&nbsp; It would be a<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; natural thing for a combined JWS+JWE document, =
but we don't have one of<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
those :(<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones =
&lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span =
style=3D'color:windowtext;text-decoration:none'>Michael.Jones@microsoft.c=
om</span></a>&gt;wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; There is a defined =
algorithm to distinguish between the JWS and JWE<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; objects in the third paragraph =
of<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11=
#section-4"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-ietf-jose-json-web-encryption-11#section-4</span></a><o:p></o:p><=
/p><p class=3DMsoPlainText>&gt;&gt; .****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; -- Mike****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; *From:* Richard Barnes [<a =
href=3D"mailto:rlb@ipv.sx"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:rlb@ipv.sx</span><=
/a>]<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; *Sent:* Thursday, =
June 20, 2013 8:15 AM<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
*To:* Mike Jones<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; *Cc:* <a =
href=3D"mailto:jose@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; *Subject:* Re: [jose] Should we keep or =
remove the JOSE JWS and JWE MIME<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; types?****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Multiplexing JWE and JWS under a single =
JOSE media type only makes sense<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; if there's a defined algorithm to demux =
them.&nbsp; So if you want to do this,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; you would need to write down the =
algorithm.****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Personally, it seems simpler and clearer =
to me to just have the four<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; current types, so that you know which type =
of object you're dealing with,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; and in what serialization, without having =
to do content sniffing.****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike =
Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span =
style=3D'color:windowtext;text-decoration:none'>Michael.Jones@microsoft.c=
om</span></a>&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
wrote:****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; The JWS and JWE =
documents currently define these MIME types for the<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; convenience of applications that may want =
to use them:****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jws****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jws+json****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jwe****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jwe+json****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; That being said, I&#8217;m not aware of =
any uses of these by applications at<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; present.&nbsp; Thus, I think that makes it =
fair game to ask whether we want to<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; keep them or remove them &#8211; in which =
case, if applications ever needed them,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; they could define them =
later.****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Another dimension of this question for JWS =
and JWE is that it&#8217;s not clear<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; that the four types application/jws, =
application/jws+json, application/jwe,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; and application/jwe+json are even the =
right ones.&nbsp; It might be more useful<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; to have generic application/jose and =
application/jose+json types, which<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; could hold either JWS or JWE objects =
respectively using the compact or JSON<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; serializations (although I&#8217;m not =
advocating adding them at this time).****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Having different JWS versus JWE MIME types =
apparently did contribute to at<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; least Dick&#8217;s confusion about the =
purpose of the &#8220;typ&#8221; field, so deleting<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; them could help eliminate this possibility =
of confusion in the future.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Thus, I&#8217;m increasingly convinced we =
should get rid of the JWS and JWE types<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; and leave it up to applications to define =
the types they need, when they<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; need them.****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Do people have use cases for these four =
MIME types now or should we leave<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; them to future specs to define, if =
needed?****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike***<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; *<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; P.S.&nbsp; For completeness, I&#8217;ll =
add that the JWK document also defines these<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; MIME types:****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jwk+json****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jwk-set+json****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; There are already clear use cases for =
these types, so I&#8217;m not advocating<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; deleting them, but wanted to call that out =
explicitly.&nbsp; For instance, when<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; retrieving a JWK Set document referenced =
by a &#8220;jku&#8221; header parameter, I<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; believe that the result should use the =
application/jwk-set+json type.&nbsp; (In<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; fact, I&#8217;ll add this to the specs, =
unless there are any objections.)<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Likewise, =
draft-miller-jose-jwe-protected-jwk-02 already uses<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; application/jwk+json.&nbsp; Both could =
also be as &#8220;cty&#8221; values when encrypting<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; JWKs and JWK Sets, in contexts where that =
that would be useful.****<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; ****<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; jose mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <a href=3D"mailto:jose@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/jose****"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/jose****</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ** **<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; jose mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a href=3D"mailto:jose@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/jose"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/jose</span></a><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_053B_01CE6DAC.36EB5D00--


From ietf@augustcellars.com  Thu Jun 20 11:55:20 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AB611E80F5 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.538
X-Spam-Level: 
X-Spam-Status: No, score=-3.538 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Bl+d04YDyY7 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:55:12 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6755D11E80BA for <jose@ietf.org>; Thu, 20 Jun 2013 11:55:12 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id EEA242CA40; Thu, 20 Jun 2013 11:55:07 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "Richard Barnes" <rlb@ipv.sx>
Date: Thu, 20 Jun 2013 11:54:13 -0700
Message-ID: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0540_01CE6DAC.E2734250"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5t5xRPeyoH6vXbTWe6CTWcVqhYoA==
Cc: jose@ietf.org
Subject: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:55:20 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0540_01CE6DAC.E2734250
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<no hat>

 

Having just started looking at a design implementation, I am now more than
ever interested in seeing this matrix of fields.  At the present time I
think the following columns are probably of interest:

 

Name, must understand, use required, common vs specific, protection required

 

I was just looking at the alg and enc fields for JWE and realized that one
was specific - so it should be one location - and one was common - so it
should be in a different location.  And then I needed to start thinking
about where it goes in terms of compacted vs one recipient vs two
recipients.

 

Do you have an idea of when this matrix might show up?

 

Jim

 


------=_NextPart_000_0540_01CE6DAC.E2734250
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>&lt;no =
hat&gt;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Having just started looking at a design =
implementation, I am now more than ever interested in seeing this matrix =
of fields.&nbsp; At the present time I think the following columns are =
probably of interest:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Name, must =
understand, use required, common vs specific, protection =
required<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I was just looking at the alg and enc fields for JWE =
and realized that one was specific &#8211; so it should be one location =
&#8211; and one was common &#8211; so it should be in a different =
location.&nbsp; And then I needed to start thinking about where it goes =
in terms of compacted vs one recipient vs two =
recipients.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Do you have an idea of when this matrix might show =
up?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0540_01CE6DAC.E2734250--


From Michael.Jones@microsoft.com  Thu Jun 20 11:57:42 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFF921E80B3 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.126
X-Spam-Level: 
X-Spam-Status: No, score=-2.126 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4W6JvTkdWwnq for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 11:57:32 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id 40D6F11E80F5 for <jose@ietf.org>; Thu, 20 Jun 2013 11:56:40 -0700 (PDT)
Received: from BY2FFO11FD027.protection.gbl (10.1.15.203) by BY2FFO11HUB011.protection.gbl (10.1.14.82) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 18:56:37 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD027.mail.protection.outlook.com (10.1.15.216) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 18:56:37 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 18:56:25 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "'Matt Miller (mamille2)'" <mamille2@cisco.com>, 'Richard Barnes' <rlb@ipv.sx>
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5si+PCJyNtJjwFQ3SCQ8Y9W8ChrQBPRl+AAAAPBOAAAzZugAABhYSAAABQGPAAAl4bAAAAOJZw
Date: Thu, 20 Jun 2013 18:56:25 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367879D67@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com> <4E1F6AAD24975D4BA5B16804296739436787993E@TK5EX14MBXC283.redmond.corp.microsoft.com> <053a01ce6de6$e34775e0$a9d661a0$@augustcellars.com>
In-Reply-To: <053a01ce6de6$e34775e0$a9d661a0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367879D67TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(24454002)(51444003)(51704005)(199002)(189002)(13464003)(377454003)(56816003)(54316002)(66066001)(79102001)(55846006)(4396001)(81342001)(71186001)(54356001)(65816001)(74662001)(74502001)(16236675002)(74366001)(16406001)(19300405004)(46102001)(512954002)(53806001)(51856001)(77982001)(31966008)(76482001)(76786001)(20776003)(77096001)(44976003)(74876001)(50986001)(74706001)(81542001)(69226001)(80022001)(63696002)(76796001)(47446002)(47976001)(15202345003)(49866001)(56776001)(47736001)(33656001)(6806003)(59766001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB011; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 18:57:42 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367879D67TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Because the syntax is completely different.  One is period-separated base64=
url encoded fields.  The other is JSON.

                                                                -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Thursday, June 20, 2013 11:49 AM
To: Mike Jones; 'Matt Miller (mamille2)'; 'Richard Barnes'
Cc: jose@ietf.org
Subject: RE: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?

I have a question, why is there both an application/jose and and applicatio=
n/jose+json.  Why not have just one of them?

Jim


From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mik=
e Jones
Sent: Thursday, June 20, 2013 10:47 AM
To: Matt Miller (mamille2); Richard Barnes
Cc: jose@ietf.org
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?

Editorially, if we do decide to add application/jose and application/jose+j=
son MIME types, I would register them in draft-ietf-jose-json-web-signature=
, just like other registry content shared between JWS and JWE, such as the =
JSON Web Signature and Encryption Header Parameters Registry<http://tools.i=
etf.org/html/draft-ietf-jose-json-web-signature-11#page-18>.

                                                            -- Mike



-----Original Message-----
From: Matt Miller (mamille2) [mailto:mamille2@cisco.com]
Sent: Thursday, June 20, 2013 10:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?



I just want to say that I think having a media type is important and useful=
.  It might not be important and useful for JWT or OAuth or OpenID-Connect,=
 but I can think of many applications that would make use of them if at all=
 possible.



I personally don't care if it's a generic media type or individual applicat=
ion/jwe and application/jws.  However, I think a generic media type would r=
equire a separate document; trying to fit this into the one shared document=
 (JWA) seems wrong.





- m&m



Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >

Cisco Systems, Inc.



PS: I've found +json useful for other things, because I do have application=
s that present in different formats (right now that's usually +xml).  While=
 there's not a simple corollary with XML-based concepts, I think there will=
 be corollaries in the future (e.g., CBOR).  Having them now means we're no=
t painted into a corner if (when) we look at JOSE2 and support for binary r=
epresentations.



On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>=
>

wrote:



> That algorithm is part of the story, but it's incomplete.  What we need i=
s

> an algorithm that starts with an arbitrary octet string and sorts by

> JWS/JWE and serialization.  An outline of the flow chart:

>

> 1. If content parses as valid JSON

> 1.*. Parse JSON

> 1.1. Iontains a "ciphertext" field -> JWE + JSON

> 1.2. Contains a "payload" field -> JWS + JSON

> 1.3. Else fail

> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"

> 2.*. Split on "."

> 2.1. If 5 components -> JWE + compact

> 2.2. If 3 components -> JWS + compact

> 2.3. Else fail

> 3. Else fail

>

> There's also the question of which document this goes in.  It would be a

> natural thing for a combined JWS+JWE document, but we don't have one of

> those :(

>

>

>

>

> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>wrote:

>

>> There is a defined algorithm to distinguish between the JWS and JWE

>> objects in the third paragraph of

>> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#sectio=
n-4

>> .****

>>

>> ** **

>>

>>                                                            -- Mike****

>>

>> ** **

>>

>> *From:* Richard Barnes [mailto:rlb@ipv.sx]

>> *Sent:* Thursday, June 20, 2013 8:15 AM

>> *To:* Mike Jones

>> *Cc:* jose@ietf.org<mailto:jose@ietf.org>

>>

>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME

>> types?****

>>

>> ** **

>>

>> Multiplexing JWE and JWS under a single JOSE media type only makes sense

>> if there's a defined algorithm to demux them.  So if you want to do this=
,

>> you would need to write down the algorithm.****

>>

>> ** **

>>

>> Personally, it seems simpler and clearer to me to just have the four

>> current types, so that you know which type of object you're dealing with=
,

>> and in what serialization, without having to do content sniffing.****

>>

>> ** **

>>

>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>

>> wrote:****

>>

>> The JWS and JWE documents currently define these MIME types for the

>> convenience of applications that may want to use them:****

>>

>>                application/jws****

>>

>>                application/jws+json****

>>

>>                application/jwe****

>>

>>                application/jwe+json****

>>

>> ****

>>

>> That being said, I'm not aware of any uses of these by applications at

>> present.  Thus, I think that makes it fair game to ask whether we want t=
o

>> keep them or remove them - in which case, if applications ever needed th=
em,

>> they could define them later.****

>>

>> ****

>>

>> Another dimension of this question for JWS and JWE is that it's not clea=
r

>> that the four types application/jws, application/jws+json, application/j=
we,

>> and application/jwe+json are even the right ones.  It might be more usef=
ul

>> to have generic application/jose and application/jose+json types, which

>> could hold either JWS or JWE objects respectively using the compact or J=
SON

>> serializations (although I'm not advocating adding them at this time).**=
**

>>

>> ****

>>

>> Having different JWS versus JWE MIME types apparently did contribute to =
at

>> least Dick's confusion about the purpose of the "typ" field, so deleting

>> them could help eliminate this possibility of confusion in the future.

>> Thus, I'm increasingly convinced we should get rid of the JWS and JWE ty=
pes

>> and leave it up to applications to define the types they need, when they

>> need them.****

>>

>> ****

>>

>> Do people have use cases for these four MIME types now or should we leav=
e

>> them to future specs to define, if needed?****

>>

>> ****

>>

>>                                                                -- Mike**=
*

>> *

>>

>> ****

>>

>> P.S.  For completeness, I'll add that the JWK document also defines thes=
e

>> MIME types:****

>>

>>                application/jwk+json****

>>

>>                application/jwk-set+json****

>>

>> ****

>>

>> There are already clear use cases for these types, so I'm not advocating

>> deleting them, but wanted to call that out explicitly.  For instance, wh=
en

>> retrieving a JWK Set document referenced by a "jku" header parameter, I

>> believe that the result should use the application/jwk-set+json type.  (=
In

>> fact, I'll add this to the specs, unless there are any objections.)

>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses

>> application/jwk+json.  Both could also be as "cty" values when encryptin=
g

>> JWKs and JWK Sets, in contexts where that that would be useful.****

>>

>> ****

>>

>>

>> _______________________________________________

>> jose mailing list

>> jose@ietf.org<mailto:jose@ietf.org>

>> https://www.ietf.org/mailman/listinfo/jose****

>>

>> ** **

>>

> _______________________________________________

> jose mailing list

> jose@ietf.org<mailto:jose@ietf.org>

> https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B168042967394367879D67TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Because the syntax is =
completely different.&nbsp; One is period-separated base64url encoded field=
s.&nbsp; The other is JSON.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Thursday, June 20, 2013 11:49 AM<br>
<b>To:</b> Mike Jones; 'Matt Miller (mamille2)'; 'Richard Barnes'<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have a question, why=
 is there both an application/jose and and application/jose&#43;json.&nbsp;=
 Why not have just one of them?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Thursday, June 20, 2013 10:47 AM<br>
<b>To:</b> Matt Miller (mamille2); Richard Barnes<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Editorially, if we do decide to add application/jose=
 and application/jose&#43;json MIME types, I would register them in draft-i=
etf-jose-json-web-signature, just like other registry content shared betwee=
n JWS and JWE, such as the
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11=
#page-18">
JSON Web Signature and Encryption Header Parameters Registry</a>.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; -- Mike<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: Matt Miller (mamille2) [<a href=3D"mailto:mamille2@cisco.com">mailto:=
mamille2@cisco.com</a>]
<br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I just want to say that I think having a media ty=
pe is important and useful.&nbsp; It might not be important and useful for =
JWT or OAuth or OpenID-Connect, but I can think of many applications that w=
ould make use of them if at all possible.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I personally don't care if it's a generic media t=
ype or individual application/jwe and application/jws.&nbsp; However, I thi=
nk a generic media type would require a separate document; trying to fit th=
is into the one shared document (JWA) seems
 wrong.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">- m&amp;m<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Matt Miller &lt; <a href=3D"mailto:mamille2@cisco=
.com"><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.=
com</span></a> &gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Cisco Systems, Inc.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">PS: I've found &#43;json useful for other things,=
 because I do have applications that present in different formats (right no=
w that's usually &#43;xml).&nbsp; While there's not a simple corollary with=
 XML-based concepts, I think there will be corollaries
 in the future (e.g., CBOR).&nbsp; Having them now means we're not painted =
into a corner if (when) we look at JOSE2 and support for binary representat=
ions.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx"><span style=3D"color:windowtext;text-decorati=
on:none">rlb@ipv.sx</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; That algorithm is part of the story, but it'=
s incomplete.&nbsp; What we need is<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; an algorithm that starts with an arbitrary o=
ctet string and sorts by<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; JWS/JWE and serialization.&nbsp; An outline =
of the flow chart:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1. If content parses as valid JSON<o:p></o:p=
></p>
<p class=3D"MsoPlainText">&gt; 1.*. Parse JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.1. Iontains a &quot;ciphertext&quot; field=
 -&gt; JWE &#43; JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.2. Contains a &quot;payload&quot; field -&=
gt; JWS &#43; JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 1.3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2. Else if content matches the regex &quot;^=
[a-zA-Z0-9_.-]*$&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.*. Split on &quot;.&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.1. If 5 components -&gt; JWE &#43; compact=
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.2. If 3 components -&gt; JWS &#43; compact=
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 2.3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; 3. Else fail<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; There's also the question of which document =
this goes in.&nbsp; It would be a<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; natural thing for a combined JWS&#43;JWE doc=
ument, but we don't have one of<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; those :(<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones=
 &lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span style=3D"color:wi=
ndowtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wr=
ote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; There is a defined algorithm to distingu=
ish between the JWS and JWE<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; objects in the third paragraph of<o:p></=
o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"http://tools.ietf.org/html/dr=
aft-ietf-jose-json-web-encryption-11#section-4">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><o:p></o:p=
></p>
<p class=3D"MsoPlainText">&gt;&gt; .****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; -- Mike****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *From:* Richard Barnes [<a href=3D"mailt=
o:rlb@ipv.sx"><span style=3D"color:windowtext;text-decoration:none">mailto:=
rlb@ipv.sx</span></a>]<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *To:* Mike Jones<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org"><=
span style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></=
a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *Subject:* Re: [jose] Should we keep or =
remove the JOSE JWS and JWE MIME<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; types?****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Multiplexing JWE and JWS under a single =
JOSE media type only makes sense<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; if there's a defined algorithm to demux =
them.&nbsp; So if you want to do this,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; you would need to write down the algorit=
hm.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Personally, it seems simpler and clearer=
 to me to just have the four<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; current types, so that you know which ty=
pe of object you're dealing with,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and in what serialization, without havin=
g to do content sniffing.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jo=
nes &lt;<a href=3D"mailto:Michael.Jones@microsoft.com"><span style=3D"color=
:windowtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt=
;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; wrote:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; The JWS and JWE documents currently defi=
ne these MIME types for the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; convenience of applications that may wan=
t to use them:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws****<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe****<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; That being said, I&#8217;m not aware of =
any uses of these by applications at<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; present.&nbsp; Thus, I think that makes =
it fair game to ask whether we want to<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; keep them or remove them &#8211; in whic=
h case, if applications ever needed them,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; they could define them later.****<o:p></=
o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Another dimension of this question for J=
WS and JWE is that it&#8217;s not clear<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; that the four types application/jws, app=
lication/jws&#43;json, application/jwe,<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and application/jwe&#43;json are even th=
e right ones.&nbsp; It might be more useful<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; to have generic application/jose and app=
lication/jose&#43;json types, which<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; could hold either JWS or JWE objects res=
pectively using the compact or JSON<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; serializations (although I&#8217;m not a=
dvocating adding them at this time).****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Having different JWS versus JWE MIME typ=
es apparently did contribute to at<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; least Dick&#8217;s confusion about the p=
urpose of the &#8220;typ&#8221; field, so deleting<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; them could help eliminate this possibili=
ty of confusion in the future.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Thus, I&#8217;m increasingly convinced w=
e should get rid of the JWS and JWE types<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; and leave it up to applications to defin=
e the types they need, when they<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; need them.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Do people have use cases for these four =
MIME types now or should we leave<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; them to future specs to define, if neede=
d?****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; *<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; P.S.&nbsp; For completeness, I&#8217;ll =
add that the JWK document also defines these<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; MIME types:****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json*=
***<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;j=
son****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; There are already clear use cases for th=
ese types, so I&#8217;m not advocating<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; deleting them, but wanted to call that o=
ut explicitly.&nbsp; For instance, when<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; retrieving a JWK Set document referenced=
 by a &#8220;jku&#8221; header parameter, I<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; believe that the result should use the a=
pplication/jwk-set&#43;json type.&nbsp; (In<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; fact, I&#8217;ll add this to the specs, =
unless there are any objections.)<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Likewise, draft-miller-jose-jwe-protecte=
d-jwk-02 already uses<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; application/jwk&#43;json.&nbsp; Both cou=
ld also be as &#8220;cty&#8221; values when encrypting<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; JWKs and JWK Sets, in contexts where tha=
t that would be useful.****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ****<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ________________________________________=
_______<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"mailto:jose@ietf.org"><span s=
tyle=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"https://www.ietf.org/mailman/=
listinfo/jose****">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/jose****</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ** **<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; ____________________________________________=
___<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; <a href=3D"mailto:jose@ietf.org"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o=
:p></p>
<p class=3D"MsoPlainText">&gt; <a href=3D"https://www.ietf.org/mailman/list=
info/jose"><span style=3D"color:windowtext;text-decoration:none">https://ww=
w.ietf.org/mailman/listinfo/jose</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367879D67TK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Thu Jun 20 12:05:02 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A7A21F9AF0 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 12:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfj18ZcUfvWz for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 12:04:55 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) by ietfa.amsl.com (Postfix) with ESMTP id 947E321F867B for <jose@ietf.org>; Thu, 20 Jun 2013 12:04:24 -0700 (PDT)
Received: from BL2FFO11FD006.protection.gbl (10.173.161.202) by BL2FFO11HUB021.protection.gbl (10.173.161.45) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 19:04:22 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD006.mail.protection.outlook.com (10.173.161.2) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 19:04:21 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 19:04:06 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: Common elements (was: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?)
Thread-Index: AQHObeXN1GY2mXm1UkS/cH+IeFF5Vpk+9RbQ
Date: Thu, 20 Jun 2013 19:04:06 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367879E91@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgThKXYYmKpB+_XVCE3cBPDsX=cKnNaEYdKOEqz1cy8aLw@mail.gmail.com>
In-Reply-To: <CAL02cgThKXYYmKpB+_XVCE3cBPDsX=cKnNaEYdKOEqz1cy8aLw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367879E91TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51704005)(24454002)(51444003)(13464003)(377454003)(74502001)(74706001)(51856001)(63696002)(512954002)(56776001)(53806001)(74662001)(74876001)(65816001)(59766001)(46102001)(47446002)(55846006)(47736001)(71186001)(19300405004)(66066001)(77982001)(50986001)(49866001)(44976003)(4396001)(76786001)(31966008)(54316002)(81342001)(69226001)(76796001)(77096001)(20776003)(54356001)(6806003)(33656001)(80022001)(79102001)(81542001)(47976001)(56816003)(76482001)(16236675002)(15202345003)(16406001)(74366001)(217873001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB021; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] Common elements (was: Re: Should we keep or remove the JOSE JWS and JWE MIME types?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 19:05:02 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367879E91TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As you know from our private conversation about your review comments, while=
 closely related, the key selection header parameter definitions are, by de=
sign, not identical between the JWS and JWE spec.  In JWS they refer to the=
 key that is used to check the signature/MAC.  In JWE they refer to the key=
 to which the JWE was encrypted.  Trying to coalesce them would only make t=
he text unnecessarily muddier in both cases.

                                                                           =
     -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 20, 2013 11:41 AM
To: Mike Jones
Cc: Matt Miller (mamille2); jose@ietf.org
Subject: Common elements (was: Re: [jose] Should we keep or remove the JOSE=
 JWS and JWE MIME types?)

While we're at it, you could move over the header parameters that are share=
d between the two.  Namely all but "enc" and "zip".  ("epk", and "apu" shou=
ld move to JWA.)

And once you do that, it seems more and more like JWE is becoming the littl=
e brother to JWS, in which case we might as well combine them.

On Thu, Jun 20, 2013 at 1:47 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
Editorially, if we do decide to add application/jose and application/jose+j=
son MIME types, I would register them in draft-ietf-jose-json-web-signature=
, just like other registry content shared between JWS and JWE, such as the =
JSON Web Signature and Encryption Header Parameters Registry<http://tools.i=
etf.org/html/draft-ietf-jose-json-web-signature-11#page-18>.

                                                            -- Mike



-----Original Message-----
From: Matt Miller (mamille2) [mailto:mamille2@cisco.com<mailto:mamille2@cis=
co.com>]
Sent: Thursday, June 20, 2013 10:33 AM
To: Richard Barnes
Cc: Mike Jones; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?



I just want to say that I think having a media type is important and useful=
.  It might not be important and useful for JWT or OAuth or OpenID-Connect,=
 but I can think of many applications that would make use of them if at all=
 possible.



I personally don't care if it's a generic media type or individual applicat=
ion/jwe and application/jws.  However, I think a generic media type would r=
equire a separate document; trying to fit this into the one shared document=
 (JWA) seems wrong.





- m&m



Matt Miller < mamille2@cisco.com<mailto:mamille2@cisco.com> >

Cisco Systems, Inc.



PS: I've found +json useful for other things, because I do have application=
s that present in different formats (right now that's usually +xml).  While=
 there's not a simple corollary with XML-based concepts, I think there will=
 be corollaries in the future (e.g., CBOR).  Having them now means we're no=
t painted into a corner if (when) we look at JOSE2 and support for binary r=
epresentations.



On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>=
>

wrote:



> That algorithm is part of the story, but it's incomplete.  What we need i=
s

> an algorithm that starts with an arbitrary octet string and sorts by

> JWS/JWE and serialization.  An outline of the flow chart:

>

> 1. If content parses as valid JSON

> 1.*. Parse JSON

> 1.1. Iontains a "ciphertext" field -> JWE + JSON

> 1.2. Contains a "payload" field -> JWS + JSON

> 1.3. Else fail

> 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"

> 2.*. Split on "."

> 2.1. If 5 components -> JWE + compact

> 2.2. If 3 components -> JWS + compact

> 2.3. Else fail

> 3. Else fail

>

> There's also the question of which document this goes in.  It would be a

> natural thing for a combined JWS+JWE document, but we don't have one of

> those :(

>

>

>

>

> On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>wrote:

>

>> There is a defined algorithm to distinguish between the JWS and JWE

>> objects in the third paragraph of

>> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#sectio=
n-4

>> .****

>>

>> ** **

>>

>>                                                            -- Mike****

>>

>> ** **

>>

>> *From:* Richard Barnes [mailto:rlb@ipv.sx]

>> *Sent:* Thursday, June 20, 2013 8:15 AM

>> *To:* Mike Jones

>> *Cc:* jose@ietf.org<mailto:jose@ietf.org>

>>

>> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME

>> types?****

>>

>> ** **

>>

>> Multiplexing JWE and JWS under a single JOSE media type only makes sense

>> if there's a defined algorithm to demux them.  So if you want to do this=
,

>> you would need to write down the algorithm.****

>>

>> ** **

>>

>> Personally, it seems simpler and clearer to me to just have the four

>> current types, so that you know which type of object you're dealing with=
,

>> and in what serialization, without having to do content sniffing.****

>>

>> ** **

>>

>> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <Michael.Jones@microsoft.com=
<mailto:Michael.Jones@microsoft.com>>

>> wrote:****

>>

>> The JWS and JWE documents currently define these MIME types for the

>> convenience of applications that may want to use them:****

>>

>>                application/jws****

>>

>>                application/jws+json****

>>

>>                application/jwe****

>>

>>                application/jwe+json****

>>

>> ****

>>

>> That being said, I'm not aware of any uses of these by applications at

>> present.  Thus, I think that makes it fair game to ask whether we want t=
o

>> keep them or remove them - in which case, if applications ever needed th=
em,

>> they could define them later.****

>>

>> ****

>>

>> Another dimension of this question for JWS and JWE is that it's not clea=
r

>> that the four types application/jws, application/jws+json, application/j=
we,

>> and application/jwe+json are even the right ones.  It might be more usef=
ul

>> to have generic application/jose and application/jose+json types, which

>> could hold either JWS or JWE objects respectively using the compact or J=
SON

>> serializations (although I'm not advocating adding them at this time).**=
**

>>

>> ****

>>

>> Having different JWS versus JWE MIME types apparently did contribute to =
at

>> least Dick's confusion about the purpose of the "typ" field, so deleting

>> them could help eliminate this possibility of confusion in the future.

>> Thus, I'm increasingly convinced we should get rid of the JWS and JWE ty=
pes

>> and leave it up to applications to define the types they need, when they

>> need them.****

>>

>> ****

>>

>> Do people have use cases for these four MIME types now or should we leav=
e

>> them to future specs to define, if needed?****

>>

>> ****

>>

>>                                                                -- Mike**=
*

>> *

>>

>> ****

>>

>> P.S.  For completeness, I'll add that the JWK document also defines thes=
e

>> MIME types:****

>>

>>                application/jwk+json****

>>

>>                application/jwk-set+json****

>>

>> ****

>>

>> There are already clear use cases for these types, so I'm not advocating

>> deleting them, but wanted to call that out explicitly.  For instance, wh=
en

>> retrieving a JWK Set document referenced by a "jku" header parameter, I

>> believe that the result should use the application/jwk-set+json type.  (=
In

>> fact, I'll add this to the specs, unless there are any objections.)

>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses

>> application/jwk+json.  Both could also be as "cty" values when encryptin=
g

>> JWKs and JWK Sets, in contexts where that that would be useful.****

>>

>> ****

>>

>>

>> _______________________________________________

>> jose mailing list

>> jose@ietf.org<mailto:jose@ietf.org>

>> https://www.ietf.org/mailman/listinfo/jose****

>>

>> ** **

>>

> _______________________________________________

> jose mailing list

> jose@ietf.org<mailto:jose@ietf.org>

> https://www.ietf.org/mailman/listinfo/jose




--_000_4E1F6AAD24975D4BA5B168042967394367879E91TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As you know from our priv=
ate conversation about your review comments, while closely related, the key=
 selection header parameter definitions are, by design,
 not identical between the JWS and JWE spec.&nbsp; In JWS they refer to the=
 key that is used to check the signature/MAC.&nbsp; In JWE they refer to th=
e key to which the JWE was encrypted.&nbsp; Trying to coalesce them would o=
nly make the text unnecessarily muddier in both
 cases.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 20, 2013 11:41 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Matt Miller (mamille2); jose@ietf.org<br>
<b>Subject:</b> Common elements (was: Re: [jose] Should we keep or remove t=
he JOSE JWS and JWE MIME types?)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">While we're at it, you could move over the header pa=
rameters that are shared between the two. &nbsp;Namely all but &quot;enc&qu=
ot; and &quot;zip&quot;. &nbsp;(&quot;epk&quot;, and &quot;apu&quot; should=
 move to JWA.)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">And once you do that, it seems more and more like JW=
E is becoming the little brother to JWS, in which case we might as well com=
bine them.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 1:47 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Editorially, if we do decide to add application/jose and applicati=
on/jose&#43;json MIME types, I would register them in draft-ietf-jose-json-=
web-signature, just like other registry
 content shared between JWS and JWE, such as the <a href=3D"http://tools.ie=
tf.org/html/draft-ietf-jose-json-web-signature-11#page-18" target=3D"_blank=
">
JSON Web Signature and Encryption Header Parameters Registry</a>.<o:p></o:p=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<div>
<div>
<p>&nbsp;<o:p></o:p></p>
<p>-----Original Message-----<br>
From: Matt Miller (mamille2) [mailto:<a href=3D"mailto:mamille2@cisco.com" =
target=3D"_blank">mamille2@cisco.com</a>]
<br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@iet=
f.org</a><br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>I just want to say that I think having a media type is important and use=
ful.&nbsp; It might not be important and useful for JWT or OAuth or OpenID-=
Connect, but I can think of many applications that would make use of them i=
f at all possible.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>I personally don't care if it's a generic media type or individual appli=
cation/jwe and application/jws.&nbsp; However, I think a generic media type=
 would require a separate document; trying to fit this into the one shared =
document (JWA) seems wrong.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>- m&amp;m<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.com</=
span></a> &gt;<o:p></o:p></p>
<p>Cisco Systems, Inc.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>PS: I've found &#43;json useful for other things, because I do have appl=
ications that present in different formats (right now that's usually &#43;x=
ml).&nbsp; While there's not a simple corollary with XML-based concepts, I =
think there will be corollaries in the future
 (e.g., CBOR).&nbsp; Having them now means we're not painted into a corner =
if (when) we look at JOSE2 and support for binary representations.<o:p></o:=
p></p>
<p>&nbsp;<o:p></o:p></p>
<p>On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;<a href=3D"mailto:rlb@i=
pv.sx" target=3D"_blank"><span style=3D"color:windowtext;text-decoration:no=
ne">rlb@ipv.sx</span></a>&gt;<o:p></o:p></p>
<p>wrote:<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; That algorithm is part of the story, but it's incomplete.&nbsp; Wha=
t we need is<o:p></o:p></p>
<p>&gt; an algorithm that starts with an arbitrary octet string and sorts b=
y<o:p></o:p></p>
<p>&gt; JWS/JWE and serialization.&nbsp; An outline of the flow chart:<o:p>=
</o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; 1. If content parses as valid JSON<o:p></o:p></p>
<p>&gt; 1.*. Parse JSON<o:p></o:p></p>
<p>&gt; 1.1. Iontains a &quot;ciphertext&quot; field -&gt; JWE &#43; JSON<o=
:p></o:p></p>
<p>&gt; 1.2. Contains a &quot;payload&quot; field -&gt; JWS &#43; JSON<o:p>=
</o:p></p>
<p>&gt; 1.3. Else fail<o:p></o:p></p>
<p>&gt; 2. Else if content matches the regex &quot;^[a-zA-Z0-9_.-]*$&quot;<=
o:p></o:p></p>
<p>&gt; 2.*. Split on &quot;.&quot;<o:p></o:p></p>
<p>&gt; 2.1. If 5 components -&gt; JWE &#43; compact<o:p></o:p></p>
<p>&gt; 2.2. If 3 components -&gt; JWS &#43; compact<o:p></o:p></p>
<p>&gt; 2.3. Else fail<o:p></o:p></p>
<p>&gt; 3. Else fail<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; There's also the question of which document this goes in.&nbsp; It =
would be a<o:p></o:p></p>
<p>&gt; natural thing for a combined JWS&#43;JWE document, but we don't hav=
e one of<o:p></o:p></p>
<p>&gt; those :(<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:windowt=
ext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wrote:<=
o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt;&gt; There is a defined algorithm to distinguish between the JWS and=
 JWE<o:p></o:p></p>
<p>&gt;&gt; objects in the third paragraph of<o:p></o:p></p>
<p>&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-=
encryption-11#section-4" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><o:p></o:p=
></p>
<p>&gt;&gt; .****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike**=
**<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; *From:* Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D=
"_blank"><span style=3D"color:windowtext;text-decoration:none">mailto:rlb@i=
pv.sx</span></a>]<o:p></o:p></p>
<p>&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<o:p></o:p></p>
<p>&gt;&gt; *To:* Mike Jones<o:p></o:p></p>
<p>&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span =
style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:=
p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and=
 JWE MIME<o:p></o:p></p>
<p>&gt;&gt; types?****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; Multiplexing JWE and JWS under a single JOSE media type only ma=
kes sense<o:p></o:p></p>
<p>&gt;&gt; if there's a defined algorithm to demux them.&nbsp; So if you w=
ant to do this,<o:p></o:p></p>
<p>&gt;&gt; you would need to write down the algorithm.****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; Personally, it seems simpler and clearer to me to just have the=
 four<o:p></o:p></p>
<p>&gt;&gt; current types, so that you know which type of object you're dea=
ling with,<o:p></o:p></p>
<p>&gt;&gt; and in what serialization, without having to do content sniffin=
g.****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a href=3D"mail=
to:Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:wind=
owtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;<o:p=
></o:p></p>
<p>&gt;&gt; wrote:****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; The JWS and JWE documents currently define these MIME types for=
 the<o:p></o:p></p>
<p>&gt;&gt; convenience of applications that may want to use them:****<o:p>=
</o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jws****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jws&#43;json****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe&#43;json****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; That being said, I&#8217;m not aware of any uses of these by ap=
plications at<o:p></o:p></p>
<p>&gt;&gt; present.&nbsp; Thus, I think that makes it fair game to ask whe=
ther we want to<o:p></o:p></p>
<p>&gt;&gt; keep them or remove them &#8211; in which case, if applications=
 ever needed them,<o:p></o:p></p>
<p>&gt;&gt; they could define them later.****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; Another dimension of this question for JWS and JWE is that it&#=
8217;s not clear<o:p></o:p></p>
<p>&gt;&gt; that the four types application/jws, application/jws&#43;json, =
application/jwe,<o:p></o:p></p>
<p>&gt;&gt; and application/jwe&#43;json are even the right ones.&nbsp; It =
might be more useful<o:p></o:p></p>
<p>&gt;&gt; to have generic application/jose and application/jose&#43;json =
types, which<o:p></o:p></p>
<p>&gt;&gt; could hold either JWS or JWE objects respectively using the com=
pact or JSON<o:p></o:p></p>
<p>&gt;&gt; serializations (although I&#8217;m not advocating adding them a=
t this time).****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; Having different JWS versus JWE MIME types apparently did contr=
ibute to at<o:p></o:p></p>
<p>&gt;&gt; least Dick&#8217;s confusion about the purpose of the &#8220;ty=
p&#8221; field, so deleting<o:p></o:p></p>
<p>&gt;&gt; them could help eliminate this possibility of confusion in the =
future.<o:p></o:p></p>
<p>&gt;&gt; Thus, I&#8217;m increasingly convinced we should get rid of the=
 JWS and JWE types<o:p></o:p></p>
<p>&gt;&gt; and leave it up to applications to define the types they need, =
when they<o:p></o:p></p>
<p>&gt;&gt; need them.****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; Do people have use cases for these four MIME types now or shoul=
d we leave<o:p></o:p></p>
<p>&gt;&gt; them to future specs to define, if needed?****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; -- Mike***<o:p></o:p></p>
<p>&gt;&gt; *<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; P.S.&nbsp; For completeness, I&#8217;ll add that the JWK docume=
nt also defines these<o:p></o:p></p>
<p>&gt;&gt; MIME types:****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk&#43;json****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set&#43;json****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; There are already clear use cases for these types, so I&#8217;m=
 not advocating<o:p></o:p></p>
<p>&gt;&gt; deleting them, but wanted to call that out explicitly.&nbsp; Fo=
r instance, when<o:p></o:p></p>
<p>&gt;&gt; retrieving a JWK Set document referenced by a &#8220;jku&#8221;=
 header parameter, I<o:p></o:p></p>
<p>&gt;&gt; believe that the result should use the application/jwk-set&#43;=
json type.&nbsp; (In<o:p></o:p></p>
<p>&gt;&gt; fact, I&#8217;ll add this to the specs, unless there are any ob=
jections.)<o:p></o:p></p>
<p>&gt;&gt; Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses<o=
:p></o:p></p>
<p>&gt;&gt; application/jwk&#43;json.&nbsp; Both could also be as &#8220;ct=
y&#8221; values when encrypting<o:p></o:p></p>
<p>&gt;&gt; JWKs and JWK Sets, in contexts where that that would be useful.=
****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ****<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; _______________________________________________<o:p></o:p></p>
<p>&gt;&gt; jose mailing list<o:p></o:p></p>
<p>&gt;&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o=
:p></p>
<p>&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose****" targ=
et=3D"_blank"><span style=3D"color:windowtext;text-decoration:none">https:/=
/www.ietf.org/mailman/listinfo/jose****</span></a><o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt;&gt; ** **<o:p></o:p></p>
<p>&gt;&gt; <o:p></o:p></p>
<p>&gt; _______________________________________________<o:p></o:p></p>
<p>&gt; jose mailing list<o:p></o:p></p>
<p>&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></=
p>
<p>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_b=
lank"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367879E91TK5EX14MBXC283r_--

From rlb@ipv.sx  Thu Jun 20 13:36:14 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C30221F9452 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.823
X-Spam-Level: *
X-Spam-Status: No, score=1.823 tagged_above=-999 required=5 tests=[AWL=-0.265,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWJpd3T+bDMm for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:36:09 -0700 (PDT)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id BE3E421F9433 for <jose@ietf.org>; Thu, 20 Jun 2013 13:36:08 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id o6so8541256oag.13 for <jose@ietf.org>; Thu, 20 Jun 2013 13:36:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=V/sPsUtjKyB/ZREiFXMxSAWkLWLdumK8LMQGlOxVDOA=; b=lhxbBSOWMZ7didlLLKDHstUB3zv+X+eMBjE/+OYKMKh/zdr6bnTUHnwDdPZFG2/g4p 0/JcgKngFuRx2grvq4NL+DPJRhvg2BENTS5ujp8CPQPHGikkDDOlDwoKs7hTsZ2Mwfin LFryqkvTjwjA2/+h+hLDqEhZrpsVp8uoBF+9uJ/1gCG3ODiOaMxB3lr03tdUTZH8XoRb 1F3GqhGHPa3VAit9i7RqZiaF4phnaoKbSWSm+rW76jlvEQ1gedKnt3YckPosSws5WSaH zYh++AAeYFQ5WjUpIA6UIzN0bwRG7AzPX+AFGPUQ2X5DqHcuk++ovwr3UKq3JVg4tDte Fncw==
MIME-Version: 1.0
X-Received: by 10.182.237.77 with SMTP id va13mr2304318obc.65.1371760567970; Thu, 20 Jun 2013 13:36:07 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 13:36:07 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367879E91@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <CAL02cgThKXYYmKpB+_XVCE3cBPDsX=cKnNaEYdKOEqz1cy8aLw@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394367879E91@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 16:36:07 -0400
Message-ID: <CAL02cgQgui-DYFgzYaXG+GSxs1SqGZ5YH25RgaL_akXnkDF=pw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cdcc5efda604df9be5ba
X-Gm-Message-State: ALoCoQlYR5nxGM1NiLCm7hapnASU9MkEQnj/g+xDYkgtxQ+l+BLuwIUF1oMv3t6qdbi/g3i7utLH
Cc: "jose@ietf.org" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] Common elements (was: Re: Should we keep or remove the JOSE JWS and JWE MIME types?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:36:15 -0000

--e89a8ff1cdcc5efda604df9be5ba
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

And as I said in that conversation, it seems like you could have those two
sentences instead of 12 sections of duplicative text.


On Thu, Jun 20, 2013 at 3:04 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  As you know from our private conversation about your review comments,
> while closely related, the key selection header parameter definitions are=
,
> by design, not identical between the JWS and JWE spec.  In JWS they refer
> to the key that is used to check the signature/MAC.  In JWE they refer to
> the key to which the JWE was encrypted.  Trying to coalesce them would on=
ly
> make the text unnecessarily muddier in both cases.****
>
> ** **
>
>
> -- Mike****
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 20, 2013 11:41 AM
> *To:* Mike Jones
> *Cc:* Matt Miller (mamille2); jose@ietf.org
> *Subject:* Common elements (was: Re: [jose] Should we keep or remove the
> JOSE JWS and JWE MIME types?)****
>
> ** **
>
> While we're at it, you could move over the header parameters that are
> shared between the two.  Namely all but "enc" and "zip".  ("epk", and "ap=
u"
> should move to JWA.)****
>
> ** **
>
> And once you do that, it seems more and more like JWE is becoming the
> little brother to JWS, in which case we might as well combine them.****
>
> ** **
>
> On Thu, Jun 20, 2013 at 1:47 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> Editorially, if we do decide to add application/jose and
> application/jose+json MIME types, I would register them in
> draft-ietf-jose-json-web-signature, just like other registry content shar=
ed
> between JWS and JWE, such as the JSON Web Signature and Encryption Header
> Parameters Registry<http://tools.ietf.org/html/draft-ietf-jose-json-web-s=
ignature-11#page-18>
> .****
>
>  ****
>
>                                                             -- Mike****
>
>  ****
>
> -----Original Message-----
> From: Matt Miller (mamille2) [mailto:mamille2@cisco.com]
> Sent: Thursday, June 20, 2013 10:33 AM
> To: Richard Barnes
> Cc: Mike Jones; jose@ietf.org
> Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
>  ****
>
> I just want to say that I think having a media type is important and
> useful.  It might not be important and useful for JWT or OAuth or
> OpenID-Connect, but I can think of many applications that would make use =
of
> them if at all possible.****
>
>  ****
>
> I personally don't care if it's a generic media type or individual
> application/jwe and application/jws.  However, I think a generic media ty=
pe
> would require a separate document; trying to fit this into the one shared
> document (JWA) seems wrong.****
>
>  ****
>
>  ****
>
> - m&m****
>
>  ****
>
> Matt Miller < mamille2@cisco.com >****
>
> Cisco Systems, Inc.****
>
>  ****
>
> PS: I've found +json useful for other things, because I do have
> applications that present in different formats (right now that's usually
> +xml).  While there's not a simple corollary with XML-based concepts, I
> think there will be corollaries in the future (e.g., CBOR).  Having them
> now means we're not painted into a corner if (when) we look at JOSE2 and
> support for binary representations.****
>
>  ****
>
> On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx>****
>
> wrote:****
>
>  ****
>
> > That algorithm is part of the story, but it's incomplete.  What we need
> is****
>
> > an algorithm that starts with an arbitrary octet string and sorts by***=
*
>
> > JWS/JWE and serialization.  An outline of the flow chart:****
>
> > ****
>
> > 1. If content parses as valid JSON****
>
> > 1.*. Parse JSON****
>
> > 1.1. Iontains a "ciphertext" field -> JWE + JSON****
>
> > 1.2. Contains a "payload" field -> JWS + JSON****
>
> > 1.3. Else fail****
>
> > 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"****
>
> > 2.*. Split on "."****
>
> > 2.1. If 5 components -> JWE + compact****
>
> > 2.2. If 3 components -> JWS + compact****
>
> > 2.3. Else fail****
>
> > 3. Else fail****
>
> > ****
>
> > There's also the question of which document this goes in.  It would be =
a
> ****
>
> > natural thing for a combined JWS+JWE document, but we don't have one of=
*
> ***
>
> > those :(****
>
> > ****
>
> > ****
>
> > ****
>
> > ****
>
> > On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <
> Michael.Jones@microsoft.com>wrote:****
>
> > ****
>
> >> There is a defined algorithm to distinguish between the JWS and JWE***=
*
>
> >> objects in the third paragraph of****
>
> >>
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section=
-4
> ****
>
> >> .********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >>                                                            -- Mike****=
*
> ***
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]****
>
> >> *Sent:* Thursday, June 20, 2013 8:15 AM****
>
> >> *To:* Mike Jones****
>
> >> *Cc:* jose@ietf.org****
>
> >> ****
>
> >> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME
> ****
>
> >> types?********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Multiplexing JWE and JWS under a single JOSE media type only makes sen=
se
> ****
>
> >> if there's a defined algorithm to demux them.  So if you want to do
> this,****
>
> >> you would need to write down the algorithm.********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Personally, it seems simpler and clearer to me to just have the four**=
*
> *
>
> >> current types, so that you know which type of object you're dealing
> with,****
>
> >> and in what serialization, without having to do content sniffing.*****=
*
> **
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <
> Michael.Jones@microsoft.com>****
>
> >> wrote:********
>
> >> ****
>
> >> The JWS and JWE documents currently define these MIME types for the***=
*
>
> >> convenience of applications that may want to use them:********
>
> >> ****
>
> >>                application/jws********
>
> >> ****
>
> >>                application/jws+json********
>
> >> ****
>
> >>                application/jwe********
>
> >> ****
>
> >>                application/jwe+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> That being said, I=92m not aware of any uses of these by applications =
at*
> ***
>
> >> present.  Thus, I think that makes it fair game to ask whether we want
> to****
>
> >> keep them or remove them =96 in which case, if applications ever neede=
d
> them,****
>
> >> they could define them later.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Another dimension of this question for JWS and JWE is that it=92s not
> clear****
>
> >> that the four types application/jws, application/jws+json,
> application/jwe,****
>
> >> and application/jwe+json are even the right ones.  It might be more
> useful****
>
> >> to have generic application/jose and application/jose+json types, whic=
h
> ****
>
> >> could hold either JWS or JWE objects respectively using the compact or
> JSON****
>
> >> serializations (although I=92m not advocating adding them at this
> time).********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Having different JWS versus JWE MIME types apparently did contribute t=
o
> at****
>
> >> least Dick=92s confusion about the purpose of the =93typ=94 field, so =
deleting
> ****
>
> >> them could help eliminate this possibility of confusion in the future.=
*
> ***
>
> >> Thus, I=92m increasingly convinced we should get rid of the JWS and JW=
E
> types****
>
> >> and leave it up to applications to define the types they need, when th=
ey
> ****
>
> >> need them.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Do people have use cases for these four MIME types now or should we
> leave****
>
> >> them to future specs to define, if needed?********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >>                                                                --
> Mike*******
>
> >> *****
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> P.S.  For completeness, I=92ll add that the JWK document also defines
> these****
>
> >> MIME types:********
>
> >> ****
>
> >>                application/jwk+json********
>
> >> ****
>
> >>                application/jwk-set+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> There are already clear use cases for these types, so I=92m not advoca=
ting
> ****
>
> >> deleting them, but wanted to call that out explicitly.  For instance,
> when****
>
> >> retrieving a JWK Set document referenced by a =93jku=94 header paramet=
er, I
> ****
>
> >> believe that the result should use the application/jwk-set+json type.
> (In****
>
> >> fact, I=92ll add this to the specs, unless there are any objections.)*=
***
>
> >> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses****
>
> >> application/jwk+json.  Both could also be as =93cty=94 values when
> encrypting****
>
> >> JWKs and JWK Sets, in contexts where that that would be useful.*******=
*
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> ****
>
> >> _______________________________________________****
>
> >> jose mailing list****
>
> >> jose@ietf.org****
>
> >> https://www.ietf.org/mailman/listinfo/jose********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> > _______________________________________________****
>
> > jose mailing list****
>
> > jose@ietf.org****
>
> > https://www.ietf.org/mailman/listinfo/jose****
>
>  ****
>
> ** **
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--e89a8ff1cdcc5efda604df9be5ba
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">And as I said in that conversation, it seems like you coul=
d have those two sentences instead of 12 sections of duplicative text.</div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun =
20, 2013 at 3:04 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Mic=
hael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">As you know from our priv=
ate conversation about your review comments, while closely related, the key=
 selection header parameter definitions are, by design,
 not identical between the JWS and JWE spec.=A0 In JWS they refer to the ke=
y that is used to check the signature/MAC.=A0 In JWE they refer to the key =
to which the JWE was encrypted.=A0 Trying to coalesce them would only make =
the text unnecessarily muddier in both
 cases.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u><=
/u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 11:41 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Matt Miller (mamille2); <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a><br>
<b>Subject:</b> Common elements (was: Re: [jose] Should we keep or remove t=
he JOSE JWS and JWE MIME types?)<u></u><u></u></span></p><div><div class=3D=
"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">While we&#39;re at it, you could move over the heade=
r parameters that are shared between the two. =A0Namely all but &quot;enc&q=
uot; and &quot;zip&quot;. =A0(&quot;epk&quot;, and &quot;apu&quot; should m=
ove to JWA.)<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">And once you do that, it seems more and more like JW=
E is becoming the little brother to JWS, in which case we might as well com=
bine them.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 1:47 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Editorially, if we do decide to add application/jose=
 and application/jose+json MIME types, I would register them in draft-ietf-=
jose-json-web-signature, just like other registry
 content shared between JWS and JWE, such as the <a href=3D"http://tools.ie=
tf.org/html/draft-ietf-jose-json-web-signature-11#page-18" target=3D"_blank=
">
JSON Web Signature and Encryption Header Parameters Registry</a>.<u></u><u>=
</u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 -- Mike<u></u><u></u></span></p>
<div>
<div>
<p>=A0<u></u><u></u></p>
<p>-----Original Message-----<br>
From: Matt Miller (mamille2) [mailto:<a href=3D"mailto:mamille2@cisco.com" =
target=3D"_blank">mamille2@cisco.com</a>]
<br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@iet=
f.org</a><br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?<u></u><u></u></p>
<p>=A0<u></u><u></u></p>
<p>I just want to say that I think having a media type is important and use=
ful.=A0 It might not be important and useful for JWT or OAuth or OpenID-Con=
nect, but I can think of many applications that would make use of them if a=
t all possible.<u></u><u></u></p>

<p>=A0<u></u><u></u></p>
<p>I personally don&#39;t care if it&#39;s a generic media type or individu=
al application/jwe and application/jws.=A0 However, I think a generic media=
 type would require a separate document; trying to fit this into the one sh=
ared document (JWA) seems wrong.<u></u><u></u></p>

<p>=A0<u></u><u></u></p>
<p>=A0<u></u><u></u></p>
<p>- m&amp;m<u></u><u></u></p>
<p>=A0<u></u><u></u></p>
<p>Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.com</=
span></a> &gt;<u></u><u></u></p>
<p>Cisco Systems, Inc.<u></u><u></u></p>
<p>=A0<u></u><u></u></p>
<p>PS: I&#39;ve found +json useful for other things, because I do have appl=
ications that present in different formats (right now that&#39;s usually +x=
ml).=A0 While there&#39;s not a simple corollary with XML-based concepts, I=
 think there will be corollaries in the future
 (e.g., CBOR).=A0 Having them now means we&#39;re not painted into a corner=
 if (when) we look at JOSE2 and support for binary representations.<u></u><=
u></u></p>
<p>=A0<u></u><u></u></p>
<p>On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;<a href=3D"mailto:rlb@i=
pv.sx" target=3D"_blank"><span style=3D"color:windowtext;text-decoration:no=
ne">rlb@ipv.sx</span></a>&gt;<u></u><u></u></p>
<p>wrote:<u></u><u></u></p>
<p>=A0<u></u><u></u></p>
<p>&gt; That algorithm is part of the story, but it&#39;s incomplete.=A0 Wh=
at we need is<u></u><u></u></p>
<p>&gt; an algorithm that starts with an arbitrary octet string and sorts b=
y<u></u><u></u></p>
<p>&gt; JWS/JWE and serialization.=A0 An outline of the flow chart:<u></u><=
u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; 1. If content parses as valid JSON<u></u><u></u></p>
<p>&gt; 1.*. Parse JSON<u></u><u></u></p>
<p>&gt; 1.1. Iontains a &quot;ciphertext&quot; field -&gt; JWE + JSON<u></u=
><u></u></p>
<p>&gt; 1.2. Contains a &quot;payload&quot; field -&gt; JWS + JSON<u></u><u=
></u></p>
<p>&gt; 1.3. Else fail<u></u><u></u></p>
<p>&gt; 2. Else if content matches the regex &quot;^[a-zA-Z0-9_.-]*$&quot;<=
u></u><u></u></p>
<p>&gt; 2.*. Split on &quot;.&quot;<u></u><u></u></p>
<p>&gt; 2.1. If 5 components -&gt; JWE + compact<u></u><u></u></p>
<p>&gt; 2.2. If 3 components -&gt; JWS + compact<u></u><u></u></p>
<p>&gt; 2.3. Else fail<u></u><u></u></p>
<p>&gt; 3. Else fail<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; There&#39;s also the question of which document this goes in.=A0 It=
 would be a<u></u><u></u></p>
<p>&gt; natural thing for a combined JWS+JWE document, but we don&#39;t hav=
e one of<u></u><u></u></p>
<p>&gt; those :(<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:windowt=
ext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wrote:<=
u></u><u></u></p>

<p>&gt; <u></u><u></u></p>
<p>&gt;&gt; There is a defined algorithm to distinguish between the JWS and=
 JWE<u></u><u></u></p>
<p>&gt;&gt; objects in the third paragraph of<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-=
encryption-11#section-4" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><u></u><u>=
</u></p>
<p>&gt;&gt; .****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *From:* Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D=
"_blank"><span style=3D"color:windowtext;text-decoration:none">mailto:rlb@i=
pv.sx</span></a>]<u></u><u></u></p>
<p>&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<u></u><u></u></p>
<p>&gt;&gt; *To:* Mike Jones<u></u><u></u></p>
<p>&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span =
style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u>=
</u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and=
 JWE MIME<u></u><u></u></p>
<p>&gt;&gt; types?****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Multiplexing JWE and JWS under a single JOSE media type only ma=
kes sense<u></u><u></u></p>
<p>&gt;&gt; if there&#39;s a defined algorithm to demux them.=A0 So if you =
want to do this,<u></u><u></u></p>
<p>&gt;&gt; you would need to write down the algorithm.****<u></u><u></u></=
p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Personally, it seems simpler and clearer to me to just have the=
 four<u></u><u></u></p>
<p>&gt;&gt; current types, so that you know which type of object you&#39;re=
 dealing with,<u></u><u></u></p>
<p>&gt;&gt; and in what serialization, without having to do content sniffin=
g.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a href=3D"mail=
to:Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:wind=
owtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;<u><=
/u><u></u></p>

<p>&gt;&gt; wrote:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; The JWS and JWE documents currently define these MIME types for=
 the<u></u><u></u></p>
<p>&gt;&gt; convenience of applications that may want to use them:****<u></=
u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; That being said, I=92m not aware of any uses of these by applic=
ations at<u></u><u></u></p>
<p>&gt;&gt; present.=A0 Thus, I think that makes it fair game to ask whethe=
r we want to<u></u><u></u></p>
<p>&gt;&gt; keep them or remove them =96 in which case, if applications eve=
r needed them,<u></u><u></u></p>
<p>&gt;&gt; they could define them later.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Another dimension of this question for JWS and JWE is that it=
=92s not clear<u></u><u></u></p>
<p>&gt;&gt; that the four types application/jws, application/jws+json, appl=
ication/jwe,<u></u><u></u></p>
<p>&gt;&gt; and application/jwe+json are even the right ones.=A0 It might b=
e more useful<u></u><u></u></p>
<p>&gt;&gt; to have generic application/jose and application/jose+json type=
s, which<u></u><u></u></p>
<p>&gt;&gt; could hold either JWS or JWE objects respectively using the com=
pact or JSON<u></u><u></u></p>
<p>&gt;&gt; serializations (although I=92m not advocating adding them at th=
is time).****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Having different JWS versus JWE MIME types apparently did contr=
ibute to at<u></u><u></u></p>
<p>&gt;&gt; least Dick=92s confusion about the purpose of the =93typ=94 fie=
ld, so deleting<u></u><u></u></p>
<p>&gt;&gt; them could help eliminate this possibility of confusion in the =
future.<u></u><u></u></p>
<p>&gt;&gt; Thus, I=92m increasingly convinced we should get rid of the JWS=
 and JWE types<u></u><u></u></p>
<p>&gt;&gt; and leave it up to applications to define the types they need, =
when they<u></u><u></u></p>
<p>&gt;&gt; need them.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Do people have use cases for these four MIME types now or shoul=
d we leave<u></u><u></u></p>
<p>&gt;&gt; them to future specs to define, if needed?****<u></u><u></u></p=
>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike***<u></u><u></u=
></p>
<p>&gt;&gt; *<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; P.S.=A0 For completeness, I=92ll add that the JWK document also=
 defines these<u></u><u></u></p>
<p>&gt;&gt; MIME types:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk-se=
t+json****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; There are already clear use cases for these types, so I=92m not=
 advocating<u></u><u></u></p>
<p>&gt;&gt; deleting them, but wanted to call that out explicitly.=A0 For i=
nstance, when<u></u><u></u></p>
<p>&gt;&gt; retrieving a JWK Set document referenced by a =93jku=94 header =
parameter, I<u></u><u></u></p>
<p>&gt;&gt; believe that the result should use the application/jwk-set+json=
 type.=A0 (In<u></u><u></u></p>
<p>&gt;&gt; fact, I=92ll add this to the specs, unless there are any object=
ions.)<u></u><u></u></p>
<p>&gt;&gt; Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses<u=
></u><u></u></p>
<p>&gt;&gt; application/jwk+json.=A0 Both could also be as =93cty=94 values=
 when encrypting<u></u><u></u></p>
<p>&gt;&gt; JWKs and JWK Sets, in contexts where that that would be useful.=
****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; _______________________________________________<u></u><u></u></=
p>
<p>&gt;&gt; jose mailing list<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><=
u></u></p>
<p>&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose****" targ=
et=3D"_blank"><span style=3D"color:windowtext;text-decoration:none">https:/=
/www.ietf.org/mailman/listinfo/jose****</span></a><u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt; _______________________________________________<u></u><u></u></p>
<p>&gt; jose mailing list<u></u><u></u></p>
<p>&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u=
></p>
<p>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_b=
lank"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><u></u><u></u></p>
<p>=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--e89a8ff1cdcc5efda604df9be5ba--

From edmundjay@sbcglobal.net  Thu Jun 20 13:39:46 2013
Return-Path: <edmundjay@sbcglobal.net>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B995021F9EEB for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ra70WV9s0VjZ for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:39:31 -0700 (PDT)
Received: from nm26-vm0.access.bullet.mail.mud.yahoo.com (nm26-vm0.access.bullet.mail.mud.yahoo.com [66.94.236.225]) by ietfa.amsl.com (Postfix) with ESMTP id CC60C21F9E62 for <jose@ietf.org>; Thu, 20 Jun 2013 13:39:30 -0700 (PDT)
Received: from [66.94.237.193] by nm26.access.bullet.mail.mud.yahoo.com with NNFMP; 20 Jun 2013 20:39:30 -0000
Received: from [66.94.237.110] by tm4.access.bullet.mail.mud.yahoo.com with NNFMP; 20 Jun 2013 20:39:29 -0000
Received: from [127.0.0.1] by omp1015.access.mail.mud.yahoo.com with NNFMP; 20 Jun 2013 20:39:29 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 778444.55901.bm@omp1015.access.mail.mud.yahoo.com
Received: (qmail 22991 invoked by uid 60001); 20 Jun 2013 20:39:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1371760769; bh=kErX6aK2rZ0KsVm5vfVxQpwwJgl+BdCW2XG6XG+nD+k=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=B3GavcWu4dJ9J8AKEle1gvn8aw8API2f30ddDm60j8cASPBVLsGzImNlFyR3+dOLpgAv7Y1Cdvr9srVF49Vs7xv8ADnQHG6jb5P7ftRdXvsBMh2UQIipVXYa2nCIwFiU1yKix03B8l7k5eqd3FqOaGoNErKPNb2mYWOqRgOPzWA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=C60Zf4JsSSSIIbpB5zzSEhg8na2wMpRQO7eiL4UNTV6w6VGE92KTAxR3VovT4Iqgff1nt1/2LFpvMbWCow383glHw/ryRjGP4N1eSMOxiK2aH7Zv8m0m7/Mc+QLWBLhiZHssVKJNozh29dv1TB23WGd0TMawtXvtRl34F4BOGqo=;
X-YMail-OSG: i5pvf18VM1n417sNFVxPEfWDjbK0q4WIwn0vYRmVha61G_1 AV3mxzn.mF_RN1mNS0NiM3_Wh7Q9m86QJOiN_ZQDBI7O7o9rWZHbiuWQhPTF qKBEfr93mzUQEjWBSmTwQIzjnY8G1BVEeVI7ugFQsgYgBtYdyjmiEPvO1d4g HkCx.HJgMXTFwsbipPY8PMjQMYVcjjdxOH6XdqZnu8Fi8NQtjuF_b4t32d2_ O35uzkICf3FsC1EgHx2KOBlXZObXO__ahY9vx0OJacEy8PvvwMDOagjp7Flh RNpbWskygZEoPkh5oqfhy5CccU2SBQvQ_NH7Q_o4oC8nm75HAN1OyZkiDt9f nZXZ9kbu2FVfZ_fekfrIgV2pA2h4OzSma4zIOcbzhNsEpPg54DNbVZJyJDld dKlxd.E.tmFiAhsp57of3PpB7MGUHXAG4k2FRSVMMBzDUuvp8JesPuqG9SHL .3q7OPvs_CGzisVu0Ep7LRW.XYymEC0k7R3IT1k2qTTDl8TpbXD_UcTotg4I tLkkspdTymxEkPAmN_tELLYzrx8FkWrV5vy6wgAVhi6hqljRCViM2rCk-
Received: from [70.36.254.42] by web184402.mail.bf1.yahoo.com via HTTP; Thu, 20 Jun 2013 13:39:29 PDT
X-Rocket-MIMEInfo: 002.001, KzEgaW4gZmF2b3Igb2YgZHJvcHBpbmcKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KRnJvbTogTWlrZSBKb25lcyA8TWljaGFlbC5Kb25lc0BtaWNyb3NvZnQuY29tPgpUbzogImpvc2VAaWV0Zi5vcmciIDxqb3NlQGlldGYub3JnPgpTZW50OiBUdWUsIEp1bmUgMTgsIDIwMTMgNjo0MjoxNSBQTQpTdWJqZWN0OiBbam9zZV0gU2hvdWxkIHdlIGtlZXAgb3IgcmVtb3ZlIHRoZSBKT1NFIEpXUyBhbmQgSldFIE1JTUUgdHlwZXM_CgogClRoZSBKV1MgYW5kIEpXRSBkb2N1bWVudHMgY3VycmVudGwBMAEBAQE-
X-RocketYMMF: edmundjay@sbcglobal.net
X-Mailer: YahooMailRC/729 YahooMailWebService/0.8.148.554
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
Message-ID: <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com>
Date: Thu, 20 Jun 2013 13:39:29 -0700 (PDT)
From: Edmund Jay <ejay@mgi1.com>
To: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-334495122-293771357-1371760769=:7926"
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:39:46 -0000

---334495122-293771357-1371760769=:7926
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

+1 in favor of dropping=0A=0A=0A=0A________________________________=0AFrom:=
 Mike Jones <Michael.Jones@microsoft.com>=0ATo: "jose@ietf.org" <jose@ietf.=
org>=0ASent: Tue, June 18, 2013 6:42:15 PM=0ASubject: [jose] Should we keep=
 or remove the JOSE JWS and JWE MIME types?=0A=0A =0AThe JWS and JWE docume=
nts currently define these MIME types for the convenience =0Aof application=
s that may want to use them:=0A                application/jws=0A          =
      application/jws+json=0A                application/jwe=0A            =
    application/jwe+json=0A =0AThat being said, I=E2=80=99m not aware of an=
y uses of these by applications at present.  =0AThus, I think that makes it=
 fair game to ask whether we want to keep them or =0Aremove them =E2=80=93 =
in which case, if applications ever needed them, they could define  =0Athem=
 later.=0A =0AAnother dimension of this question for JWS and JWE is that it=
=E2=80=99s not clear that =0Athe four types application/jws, application/jw=
s+json, application/jwe, and =0Aapplication/jwe+json are even the right one=
s.  It might be more useful to have =0Ageneric  application/jose and applic=
ation/jose+json types, which could hold =0Aeither JWS or JWE objects respec=
tively using the compact or JSON serializations =0A(although I=E2=80=99m no=
t advocating adding them at this time).=0A =0AHaving different JWS versus J=
WE MIME types apparently did contribute to at least =0ADick=E2=80=99s confu=
sion about the purpose of the =E2=80=9Ctyp=E2=80=9D field, so deleting them=
 could =0Ahelp eliminate this possibility of confusion in the future.  Thus=
, I=E2=80=99m =0Aincreasingly  convinced we should get rid of the JWS and J=
WE types and leave it =0Aup to applications to define the types they need, =
when they need them.=0A =0ADo people have use cases for these four MIME typ=
es now or should we leave them =0Ato future specs to define, if needed?=0A =
=0A                                                                -- Mike=
=0A =0AP.S.  For completeness, I=E2=80=99ll add that the JWK document also =
defines these MIME =0Atypes:=0A                application/jwk+json=0A     =
           application/jwk-set+json=0A =0AThere are already clear use cases=
 for these types, so I=E2=80=99m not advocating =0Adeleting them, but wante=
d to call that out explicitly.  For instance, when =0Aretrieving a JWK Set =
document referenced by a =E2=80=9Cjku=E2=80=9D header parameter, I believe =
=0Athat the  result should use the application/jwk-set+json type.  (In fact=
, I=E2=80=99ll =0Aadd this to the specs, unless there are any objections.) =
 Likewise, =0Adraft-miller-jose-jwe-protected-jwk-02 already uses applicati=
on/jwk+json.  Both =0Acould also be as =E2=80=9Ccty=E2=80=9D values when en=
crypting  JWKs and JWK Sets, in contexts =0Awhere that that would be useful=
.
---334495122-293771357-1371760769=:7926
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:tahoma, 'new york', times, serif;font-si=
ze:10pt"><div>+1 in favor of dropping</div><div style=3D"font-family:tahoma=
, new york, times, serif;font-size:10pt"><br><div style=3D"font-family:time=
s new roman, new york, times, serif;font-size:12pt"><font size=3D"2" face=
=3D"Tahoma"><hr size=3D"1"><b><span style=3D"font-weight: bold;">From:</spa=
n></b> Mike Jones &lt;Michael.Jones@microsoft.com&gt;<br><b><span style=3D"=
font-weight: bold;">To:</span></b> "jose@ietf.org" &lt;jose@ietf.org&gt;<br=
><b><span style=3D"font-weight: bold;">Sent:</span></b> Tue, June 18, 2013 =
6:42:15 PM<br><b><span style=3D"font-weight: bold;">Subject:</span></b> [jo=
se] Should we keep or remove the JOSE JWS and JWE MIME types?<br></font><br=
>=0A=0A =0A =0A<style><!--=0A =0A _filtered {font-family:Calibri;panose-1:2=
 15 5 2 2 2 4 3 2 4;}=0A =0Ap.MsoNormal, li.MsoNormal, div.MsoNormal=0A=09{=
margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "s=
ans-serif";}=0Aa:link, span.MsoHyperlink=0A=09{color:blue;text-decoration:u=
nderline;}=0Aa:visited, span.MsoHyperlinkFollowed=0A=09{color:purple;text-d=
ecoration:underline;}=0Aspan.EmailStyle17=0A=09{font-family:"Calibri", "san=
s-serif";color:windowtext;}=0A.MsoChpDefault=0A=09{font-family:"Calibri", "=
sans-serif";}=0A _filtered {margin:1.0in 1.0in 1.0in 1.0in;}=0Adiv.WordSect=
ion1=0A=09{}=0A--></style>=0A=0A=0A<div class=3D"WordSection1">=0A<p class=
=3D"MsoNormal">The JWS and JWE documents currently define these MIME types =
for the convenience of applications that may want to use them:</p> =0A<p cl=
ass=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws</p> =0A<p class=3D"MsoNor=
mal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; application/jws+json</p> =0A<p class=3D"MsoNormal">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; application/jwe</p> =0A<p class=3D"MsoNormal">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
application/jwe+json</p> =0A<p class=3D"MsoNormal"> &nbsp;</p> =0A<p class=
=3D"MsoNormal">That being said, I=E2=80=99m not aware of any uses of these =
by applications at present.&nbsp; Thus, I think that makes it fair game to =
ask whether we want to keep them or remove them =E2=80=93 in which case, if=
 applications ever needed them, they could define=0A them later.</p> =0A<p =
class=3D"MsoNormal"> &nbsp;</p> =0A<p class=3D"MsoNormal">Another dimension=
 of this question for JWS and JWE is that it=E2=80=99s not clear that the f=
our types application/jws, application/jws+json, application/jwe, and appli=
cation/jwe+json are even the right ones.&nbsp; It might be more useful to h=
ave generic=0A application/jose and application/jose+json types, which coul=
d hold either JWS or JWE objects respectively using the compact or JSON ser=
ializations (although I=E2=80=99m not advocating adding them at this time).=
</p> =0A<p class=3D"MsoNormal"> &nbsp;</p> =0A<p class=3D"MsoNormal">Having=
 different JWS versus JWE MIME types apparently did contribute to at least =
Dick=E2=80=99s confusion about the purpose of the =E2=80=9Ctyp=E2=80=9D fie=
ld, so deleting them could help eliminate this possibility of confusion in =
the future.&nbsp; Thus, I=E2=80=99m increasingly=0A convinced we should get=
 rid of the JWS and JWE types and leave it up to applications to define the=
 types they need, when they need them.</p> =0A<p class=3D"MsoNormal"> &nbsp=
;</p> =0A<p class=3D"MsoNormal">Do people have use cases for these four MIM=
E types now or should we leave them to future specs to define, if needed?</=
p> =0A<p class=3D"MsoNormal"> &nbsp;</p> =0A<p class=3D"MsoNormal">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- M=
ike</p> =0A<p class=3D"MsoNormal"> &nbsp;</p> =0A<p class=3D"MsoNormal">P.S=
.&nbsp; For completeness, I=E2=80=99ll add that the JWK document also defin=
es these MIME types:</p> =0A<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; applicat=
ion/jwk+json</p> =0A<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-=
set+json</p> =0A<p class=3D"MsoNormal"> &nbsp;</p> =0A<p class=3D"MsoNormal=
">There are already clear use cases for these types, so I=E2=80=99m not adv=
ocating deleting them, but wanted to call that out explicitly.&nbsp; For in=
stance, when retrieving a JWK Set document referenced by a =E2=80=9Cjku=E2=
=80=9D header parameter, I believe that the=0A result should use the applic=
ation/jwk-set+json type.&nbsp; (In fact, I=E2=80=99ll add this to the specs=
, unless there are any objections.)&nbsp; Likewise, draft-miller-jose-jwe-p=
rotected-jwk-02 already uses application/jwk+json.&nbsp; Both could also be=
 as =E2=80=9Ccty=E2=80=9D values when encrypting=0A JWKs and JWK Sets, in c=
ontexts where that that would be useful.</p> =0A<p class=3D"MsoNormal"> &nb=
sp;</p> =0A</div>=0A=0A=0A</div></div><div style=3D"position:fixed"></div>=
=0A=0A=0A</div></body></html>
---334495122-293771357-1371760769=:7926--

From rlb@ipv.sx  Thu Jun 20 13:44:53 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 221D421F9A37 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.889
X-Spam-Level: *
X-Spam-Status: No, score=1.889 tagged_above=-999 required=5 tests=[AWL=-0.199,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1, SARE_UNSUB18=0.131]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xULAg7h9Qjuc for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:44:48 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AA3E921F9A0C for <jose@ietf.org>; Thu, 20 Jun 2013 13:44:48 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l10so8552571oag.3 for <jose@ietf.org>; Thu, 20 Jun 2013 13:44:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Efc7CeGQ0v9GbTG4kFNMhOAhpML1SKYjARXAkqWs35I=; b=FGmVP/TjhLOuWSj3cXHq0fgEfCL+ocknv/XE07uuoOVlXHGhEB9Ft5VAoy7uFf4ihQ f6OqpJRDV8EyHNnWBtxfv3NyhCoqJLGUYPtSrecUl1NdNU7n47H+8MSxd3aor3JqXqYw cm8XJmYCjgvsc2WaDZuIzWCLgswfHT7kaAnwVMtg3ZZcLKkl/lN2h26DDl8xx5182lg0 3Cv3ECiUl+UEtumGkKgNjLfDt0NonJEyEYOY03Qg0vCWthrXyAkecWI3jEyOQYgiXcFX kXYv5RGulG0trbJX/fi82qGFJFEudQ6RHqXYlMt4Gb7dKIJTaK2m2KIGTxmdmBzRtmLQ WEtg==
MIME-Version: 1.0
X-Received: by 10.182.74.131 with SMTP id t3mr2298719obv.87.1371761088122; Thu, 20 Jun 2013 13:44:48 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 13:44:48 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367879D67@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411528DA68@xmb-aln-x11.cisco.com> <4E1F6AAD24975D4BA5B16804296739436787993E@TK5EX14MBXC283.redmond.corp.microsoft.com> <053a01ce6de6$e34775e0$a9d661a0$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367879D67@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 16:44:48 -0400
Message-ID: <CAL02cgQO_ncK=c6kAQwBBT_b_RaXxeEdjbR-cRPLyiHiLEEwog@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c1be065fd53404df9c0417
X-Gm-Message-State: ALoCoQmMU97OmYzs9jzauUZ+Jg6EorF9dJVnTJ1SIaeBBq0WbxGxATOW46enKN/G1hx5/SZtpJ/U
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:44:53 -0000

--001a11c1be065fd53404df9c0417
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Also: http://tools.ietf.org/html/rfc6839


On Thu, Jun 20, 2013 at 2:56 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Because the syntax is completely different.  One is period-separated
> base64url encoded fields.  The other is JSON.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Jim Schaad [mailto:ietf@augustcellars.com]
> *Sent:* Thursday, June 20, 2013 11:49 AM
> *To:* Mike Jones; 'Matt Miller (mamille2)'; 'Richard Barnes'
> *Cc:* jose@ietf.org
> *Subject:* RE: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
> ** **
>
> I have a question, why is there both an application/jose and and
> application/jose+json.  Why not have just one of them?****
>
> ** **
>
> Jim****
>
> ** **
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Mike Jones
> *Sent:* Thursday, June 20, 2013 10:47 AM
> *To:* Matt Miller (mamille2); Richard Barnes
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
> ** **
>
> Editorially, if we do decide to add application/jose and
> application/jose+json MIME types, I would register them in
> draft-ietf-jose-json-web-signature, just like other registry content shar=
ed
> between JWS and JWE, such as the JSON Web Signature and Encryption Header
> Parameters Registry<http://tools.ietf.org/html/draft-ietf-jose-json-web-s=
ignature-11#page-18>
> .****
>
> ** **
>
>                                                             -- Mike****
>
> ** **
>
> -----Original Message-----
> From: Matt Miller (mamille2) [mailto:mamille2@cisco.com<mamille2@cisco.co=
m>]
>
> Sent: Thursday, June 20, 2013 10:33 AM
> To: Richard Barnes
> Cc: Mike Jones; jose@ietf.org
> Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?****
>
> ** **
>
> I just want to say that I think having a media type is important and
> useful.  It might not be important and useful for JWT or OAuth or
> OpenID-Connect, but I can think of many applications that would make use =
of
> them if at all possible.****
>
> ** **
>
> I personally don't care if it's a generic media type or individual
> application/jwe and application/jws.  However, I think a generic media ty=
pe
> would require a separate document; trying to fit this into the one shared
> document (JWA) seems wrong.****
>
> ** **
>
> ** **
>
> - m&m****
>
> ** **
>
> Matt Miller < mamille2@cisco.com >****
>
> Cisco Systems, Inc.****
>
> ** **
>
> PS: I've found +json useful for other things, because I do have
> applications that present in different formats (right now that's usually
> +xml).  While there's not a simple corollary with XML-based concepts, I
> think there will be corollaries in the future (e.g., CBOR).  Having them
> now means we're not painted into a corner if (when) we look at JOSE2 and
> support for binary representations.****
>
> ** **
>
> On Jun 20, 2013, at 10:49 AM, Richard Barnes <rlb@ipv.sx>****
>
> wrote:****
>
> ** **
>
> > That algorithm is part of the story, but it's incomplete.  What we need
> is****
>
> > an algorithm that starts with an arbitrary octet string and sorts by***=
*
>
> > JWS/JWE and serialization.  An outline of the flow chart:****
>
> > ****
>
> > 1. If content parses as valid JSON****
>
> > 1.*. Parse JSON****
>
> > 1.1. Iontains a "ciphertext" field -> JWE + JSON****
>
> > 1.2. Contains a "payload" field -> JWS + JSON****
>
> > 1.3. Else fail****
>
> > 2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"****
>
> > 2.*. Split on "."****
>
> > 2.1. If 5 components -> JWE + compact****
>
> > 2.2. If 3 components -> JWS + compact****
>
> > 2.3. Else fail****
>
> > 3. Else fail****
>
> > ****
>
> > There's also the question of which document this goes in.  It would be =
a
> ****
>
> > natural thing for a combined JWS+JWE document, but we don't have one of=
*
> ***
>
> > those :(****
>
> > ****
>
> > ****
>
> > ****
>
> > ****
>
> > On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones <
> Michael.Jones@microsoft.com>wrote:****
>
> > ****
>
> >> There is a defined algorithm to distinguish between the JWS and JWE***=
*
>
> >> objects in the third paragraph of****
>
> >>
> http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section=
-4
> ****
>
> >> .********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >>                                                            -- Mike****=
*
> ***
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> *From:* Richard Barnes [mailto:rlb@ipv.sx <rlb@ipv.sx>]****
>
> >> *Sent:* Thursday, June 20, 2013 8:15 AM****
>
> >> *To:* Mike Jones****
>
> >> *Cc:* jose@ietf.org****
>
> >> ****
>
> >> *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME
> ****
>
> >> types?********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Multiplexing JWE and JWS under a single JOSE media type only makes sen=
se
> ****
>
> >> if there's a defined algorithm to demux them.  So if you want to do
> this,****
>
> >> you would need to write down the algorithm.********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> Personally, it seems simpler and clearer to me to just have the four**=
*
> *
>
> >> current types, so that you know which type of object you're dealing
> with,****
>
> >> and in what serialization, without having to do content sniffing.*****=
*
> **
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> >> On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones <
> Michael.Jones@microsoft.com>****
>
> >> wrote:********
>
> >> ****
>
> >> The JWS and JWE documents currently define these MIME types for the***=
*
>
> >> convenience of applications that may want to use them:********
>
> >> ****
>
> >>                application/jws********
>
> >> ****
>
> >>                application/jws+json********
>
> >> ****
>
> >>                application/jwe********
>
> >> ****
>
> >>                application/jwe+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> That being said, I=92m not aware of any uses of these by applications =
at*
> ***
>
> >> present.  Thus, I think that makes it fair game to ask whether we want
> to****
>
> >> keep them or remove them =96 in which case, if applications ever neede=
d
> them,****
>
> >> they could define them later.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Another dimension of this question for JWS and JWE is that it=92s not
> clear****
>
> >> that the four types application/jws, application/jws+json,
> application/jwe,****
>
> >> and application/jwe+json are even the right ones.  It might be more
> useful****
>
> >> to have generic application/jose and application/jose+json types, whic=
h
> ****
>
> >> could hold either JWS or JWE objects respectively using the compact or
> JSON****
>
> >> serializations (although I=92m not advocating adding them at this
> time).********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Having different JWS versus JWE MIME types apparently did contribute t=
o
> at****
>
> >> least Dick=92s confusion about the purpose of the =93typ=94 field, so =
deleting
> ****
>
> >> them could help eliminate this possibility of confusion in the future.=
*
> ***
>
> >> Thus, I=92m increasingly convinced we should get rid of the JWS and JW=
E
> types****
>
> >> and leave it up to applications to define the types they need, when th=
ey
> ****
>
> >> need them.********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> Do people have use cases for these four MIME types now or should we
> leave****
>
> >> them to future specs to define, if needed?********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >>                                                                --
> Mike*******
>
> >> *****
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> P.S.  For completeness, I=92ll add that the JWK document also defines
> these****
>
> >> MIME types:********
>
> >> ****
>
> >>                application/jwk+json********
>
> >> ****
>
> >>                application/jwk-set+json********
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> There are already clear use cases for these types, so I=92m not advoca=
ting
> ****
>
> >> deleting them, but wanted to call that out explicitly.  For instance,
> when****
>
> >> retrieving a JWK Set document referenced by a =93jku=94 header paramet=
er, I
> ****
>
> >> believe that the result should use the application/jwk-set+json type.
> (In****
>
> >> fact, I=92ll add this to the specs, unless there are any objections.)*=
***
>
> >> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses****
>
> >> application/jwk+json.  Both could also be as =93cty=94 values when
> encrypting****
>
> >> JWKs and JWK Sets, in contexts where that that would be useful.*******=
*
>
> >> ****
>
> >> ********
>
> >> ****
>
> >> ****
>
> >> _______________________________________________****
>
> >> jose mailing list****
>
> >> jose@ietf.org****
>
> >> https://www.ietf.org/mailman/listinfo/jose********
>
> >> ****
>
> >> ** ******
>
> >> ****
>
> > _______________________________________________****
>
> > jose mailing list****
>
> > jose@ietf.org****
>
> > https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>

--001a11c1be065fd53404df9c0417
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Also:=A0<a href=3D"http://tools.ietf.org/html/rfc6839">htt=
p://tools.ietf.org/html/rfc6839</a></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">On Thu, Jun 20, 2013 at 2:56 PM, Mike Jones <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D=
"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Because the syntax is =
completely different.=A0 One is period-separated base64url encoded fields.=
=A0 The other is JSON.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf=
@augustcellars.com</a>]
<br>
<b>Sent:</b> Thursday, June 20, 2013 11:49 AM<br>
<b>To:</b> Mike Jones; &#39;Matt Miller (mamille2)&#39;; &#39;Richard Barne=
s&#39;<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> RE: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<u></u><u></u></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">I have a question, why=
 is there both an application/jose and and application/jose+json.=A0 Why no=
t have just one of them?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Jim<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Thursday, June 20, 2013 10:47 AM<br>
<b>To:</b> Matt Miller (mamille2); Richard Barnes<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Should we keep or remove the JOSE JWS and JWE MI=
ME types?<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">Editorially, if we do decide to add application/jose=
 and application/jose+json MIME types, I would register them in draft-ietf-=
jose-json-web-signature, just like other registry content shared between JW=
S and JWE, such as the
<a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-signature-11=
#page-18" target=3D"_blank">
JSON Web Signature and Encryption Header Parameters Registry</a>.<u></u><u>=
</u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></=
p>
<p><u></u>=A0<u></u></p>
<p>-----Original Message-----<br>
From: Matt Miller (mamille2) [<a href=3D"mailto:mamille2@cisco.com" target=
=3D"_blank">mailto:mamille2@cisco.com</a>]
<br>
Sent: Thursday, June 20, 2013 10:33 AM<br>
To: Richard Barnes<br>
Cc: Mike Jones; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@iet=
f.org</a><br>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME type=
s?<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>I just want to say that I think having a media type is important and use=
ful.=A0 It might not be important and useful for JWT or OAuth or OpenID-Con=
nect, but I can think of many applications that would make use of them if a=
t all possible.<u></u><u></u></p>

<p><u></u>=A0<u></u></p>
<p>I personally don&#39;t care if it&#39;s a generic media type or individu=
al application/jwe and application/jws.=A0 However, I think a generic media=
 type would require a separate document; trying to fit this into the one sh=
ared document (JWA) seems
 wrong.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p><u></u>=A0<u></u></p>
<p>- m&amp;m<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Matt Miller &lt; <a href=3D"mailto:mamille2@cisco.com" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">mamille2@cisco.com</=
span></a> &gt;<u></u><u></u></p>
<p>Cisco Systems, Inc.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>PS: I&#39;ve found +json useful for other things, because I do have appl=
ications that present in different formats (right now that&#39;s usually +x=
ml).=A0 While there&#39;s not a simple corollary with XML-based concepts, I=
 think there will be corollaries
 in the future (e.g., CBOR).=A0 Having them now means we&#39;re not painted=
 into a corner if (when) we look at JOSE2 and support for binary representa=
tions.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>On Jun 20, 2013, at 10:49 AM, Richard Barnes &lt;<a href=3D"mailto:rlb@i=
pv.sx" target=3D"_blank"><span style=3D"color:windowtext;text-decoration:no=
ne">rlb@ipv.sx</span></a>&gt;<u></u><u></u></p>
<p>wrote:<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; That algorithm is part of the story, but it&#39;s incomplete.=A0 Wh=
at we need is<u></u><u></u></p>
<p>&gt; an algorithm that starts with an arbitrary octet string and sorts b=
y<u></u><u></u></p>
<p>&gt; JWS/JWE and serialization.=A0 An outline of the flow chart:<u></u><=
u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; 1. If content parses as valid JSON<u></u><u></u></p>
<p>&gt; 1.*. Parse JSON<u></u><u></u></p>
<p>&gt; 1.1. Iontains a &quot;ciphertext&quot; field -&gt; JWE + JSON<u></u=
><u></u></p>
<p>&gt; 1.2. Contains a &quot;payload&quot; field -&gt; JWS + JSON<u></u><u=
></u></p>
<p>&gt; 1.3. Else fail<u></u><u></u></p>
<p>&gt; 2. Else if content matches the regex &quot;^[a-zA-Z0-9_.-]*$&quot;<=
u></u><u></u></p>
<p>&gt; 2.*. Split on &quot;.&quot;<u></u><u></u></p>
<p>&gt; 2.1. If 5 components -&gt; JWE + compact<u></u><u></u></p>
<p>&gt; 2.2. If 3 components -&gt; JWS + compact<u></u><u></u></p>
<p>&gt; 2.3. Else fail<u></u><u></u></p>
<p>&gt; 3. Else fail<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; There&#39;s also the question of which document this goes in.=A0 It=
 would be a<u></u><u></u></p>
<p>&gt; natural thing for a combined JWS+JWE document, but we don&#39;t hav=
e one of<u></u><u></u></p>
<p>&gt; those :(<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:windowt=
ext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;wrote:<=
u></u><u></u></p>

<p>&gt; <u></u><u></u></p>
<p>&gt;&gt; There is a defined algorithm to distinguish between the JWS and=
 JWE<u></u><u></u></p>
<p>&gt;&gt; objects in the third paragraph of<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-jose-json-web-=
encryption-11#section-4" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://tools.ietf.org=
/html/draft-ietf-jose-json-web-encryption-11#section-4</span></a><u></u><u>=
</u></p>
<p>&gt;&gt; .****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *From:* Richard Barnes [<a href=3D"mailto:rlb@ipv.sx" target=3D=
"_blank"><span style=3D"color:windowtext;text-decoration:none">mailto:rlb@i=
pv.sx</span></a>]<u></u><u></u></p>
<p>&gt;&gt; *Sent:* Thursday, June 20, 2013 8:15 AM<u></u><u></u></p>
<p>&gt;&gt; *To:* Mike Jones<u></u><u></u></p>
<p>&gt;&gt; *Cc:* <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span =
style=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u>=
</u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and=
 JWE MIME<u></u><u></u></p>
<p>&gt;&gt; types?****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Multiplexing JWE and JWS under a single JOSE media type only ma=
kes sense<u></u><u></u></p>
<p>&gt;&gt; if there&#39;s a defined algorithm to demux them.=A0 So if you =
want to do this,<u></u><u></u></p>
<p>&gt;&gt; you would need to write down the algorithm.****<u></u><u></u></=
p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Personally, it seems simpler and clearer to me to just have the=
 four<u></u><u></u></p>
<p>&gt;&gt; current types, so that you know which type of object you&#39;re=
 dealing with,<u></u><u></u></p>
<p>&gt;&gt; and in what serialization, without having to do content sniffin=
g.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones &lt;<a href=3D"mail=
to:Michael.Jones@microsoft.com" target=3D"_blank"><span style=3D"color:wind=
owtext;text-decoration:none">Michael.Jones@microsoft.com</span></a>&gt;<u><=
/u><u></u></p>

<p>&gt;&gt; wrote:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; The JWS and JWE documents currently define these MIME types for=
 the<u></u><u></u></p>
<p>&gt;&gt; convenience of applications that may want to use them:****<u></=
u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jws+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe***=
*<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwe+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; That being said, I=92m not aware of any uses of these by applic=
ations at<u></u><u></u></p>
<p>&gt;&gt; present.=A0 Thus, I think that makes it fair game to ask whethe=
r we want to<u></u><u></u></p>
<p>&gt;&gt; keep them or remove them =96 in which case, if applications eve=
r needed them,<u></u><u></u></p>
<p>&gt;&gt; they could define them later.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Another dimension of this question for JWS and JWE is that it=
=92s not clear<u></u><u></u></p>
<p>&gt;&gt; that the four types application/jws, application/jws+json, appl=
ication/jwe,<u></u><u></u></p>
<p>&gt;&gt; and application/jwe+json are even the right ones.=A0 It might b=
e more useful<u></u><u></u></p>
<p>&gt;&gt; to have generic application/jose and application/jose+json type=
s, which<u></u><u></u></p>
<p>&gt;&gt; could hold either JWS or JWE objects respectively using the com=
pact or JSON<u></u><u></u></p>
<p>&gt;&gt; serializations (although I=92m not advocating adding them at th=
is time).****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Having different JWS versus JWE MIME types apparently did contr=
ibute to at<u></u><u></u></p>
<p>&gt;&gt; least Dick=92s confusion about the purpose of the =93typ=94 fie=
ld, so deleting<u></u><u></u></p>
<p>&gt;&gt; them could help eliminate this possibility of confusion in the =
future.<u></u><u></u></p>
<p>&gt;&gt; Thus, I=92m increasingly convinced we should get rid of the JWS=
 and JWE types<u></u><u></u></p>
<p>&gt;&gt; and leave it up to applications to define the types they need, =
when they<u></u><u></u></p>
<p>&gt;&gt; need them.****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; Do people have use cases for these four MIME types now or shoul=
d we leave<u></u><u></u></p>
<p>&gt;&gt; them to future specs to define, if needed?****<u></u><u></u></p=
>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike***<u></u><u></u=
></p>
<p>&gt;&gt; *<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; P.S.=A0 For completeness, I=92ll add that the JWK document also=
 defines these<u></u><u></u></p>
<p>&gt;&gt; MIME types:****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk+js=
on****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt;=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 application/jwk-se=
t+json****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; There are already clear use cases for these types, so I=92m not=
 advocating<u></u><u></u></p>
<p>&gt;&gt; deleting them, but wanted to call that out explicitly.=A0 For i=
nstance, when<u></u><u></u></p>
<p>&gt;&gt; retrieving a JWK Set document referenced by a =93jku=94 header =
parameter, I<u></u><u></u></p>
<p>&gt;&gt; believe that the result should use the application/jwk-set+json=
 type.=A0 (In<u></u><u></u></p>
<p>&gt;&gt; fact, I=92ll add this to the specs, unless there are any object=
ions.)<u></u><u></u></p>
<p>&gt;&gt; Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses<u=
></u><u></u></p>
<p>&gt;&gt; application/jwk+json.=A0 Both could also be as =93cty=94 values=
 when encrypting<u></u><u></u></p>
<p>&gt;&gt; JWKs and JWK Sets, in contexts where that that would be useful.=
****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ****<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; _______________________________________________<u></u><u></u></=
p>
<p>&gt;&gt; jose mailing list<u></u><u></u></p>
<p>&gt;&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=
=3D"color:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><=
u></u></p>
<p>&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose****" targ=
et=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org/=
mailman/listinfo/jose****</span></a><u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt;&gt; ** **<u></u><u></u></p>
<p>&gt;&gt; <u></u><u></u></p>
<p>&gt; _______________________________________________<u></u><u></u></p>
<p>&gt; jose mailing list<u></u><u></u></p>
<p>&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u=
></p>
<p>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_b=
lank"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><u></u><u></u></p>
<p><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c1be065fd53404df9c0417--

From bcampbell@pingidentity.com  Thu Jun 20 13:48:22 2013
Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 725B121F9F05 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level: 
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJVYc5adHJBC for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:48:17 -0700 (PDT)
Received: from na3sys009aog118.obsmtp.com (na3sys009aog118.obsmtp.com [74.125.149.244]) by ietfa.amsl.com (Postfix) with ESMTP id 22B2321F9EF7 for <jose@ietf.org>; Thu, 20 Jun 2013 13:48:17 -0700 (PDT)
Received: from mail-ie0-f171.google.com ([209.85.223.171]) (using TLSv1) by na3sys009aob118.postini.com ([74.125.148.12]) with SMTP ID DSNKUcNqkKQlZaSAzgI7mRoR3dh6zWUKwXrW@postini.com; Thu, 20 Jun 2013 13:48:17 PDT
Received: by mail-ie0-f171.google.com with SMTP id qd12so17734986ieb.2 for <jose@ietf.org>; Thu, 20 Jun 2013 13:48:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=qNM8TEQ8yCN3PHZku6bhCyHDcsZHnZ2YZQECJ1YTqi8=; b=bx08IH6M1bju2B0B+cjk/xLooqTpy1+WTvkdTjNqBlSVd/N5wtIsu7RgLhHayHuQQi Ffz85Xv/ntuCRNpUa5EDIG1Q7WlOTmUpbLzywYfVmddFoOh9u8PuBvTAX8t2xcg1jPST ddBaEAWW5WrGtIJkGBLrLHjgk3Y819XCauGKnzGkFNFGWM/7yQ626nR0+x/P1SKwnlgE Oni0SqtuyP6NoF8nqVkWx8bsxJnXwt7RfFNp3uhn7YqEXDLq+w4sE4A0wF1UAgVn04zG iFb976KhbLZC7AJfNJz1r/bwJ++qs2gUV09OaQQQUBf7rSxmUhfoVrGe19xywGzP85Zd 0Xdw==
X-Received: by 10.50.55.42 with SMTP id o10mr748927igp.28.1371761296488; Thu, 20 Jun 2013 13:48:16 -0700 (PDT)
X-Received: by 10.50.55.42 with SMTP id o10mr748921igp.28.1371761296370; Thu, 20 Jun 2013 13:48:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.41.34 with HTTP; Thu, 20 Jun 2013 13:47:46 -0700 (PDT)
In-Reply-To: <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 20 Jun 2013 14:47:46 -0600
Message-ID: <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com>
To: Edmund Jay <ejay@mgi1.com>
Content-Type: multipart/alternative; boundary=047d7b111981c980c304df9c1085
X-Gm-Message-State: ALoCoQmTkR7xB5LDWG+DwravH5imol3kYzTpJj14v2VuIrQb/RFX8fNE9GrPwQX6r84arrsTAhCVh1Z4WqzXjw2uu7Cyrqjz2/n0cjV6PHo5uWAvH0vHf7UJrVke3+HgeOqa1uLv87BQ
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:48:22 -0000

--047d7b111981c980c304df9c1085
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I'm okay dropping them.


On Thu, Jun 20, 2013 at 2:39 PM, Edmund Jay <ejay@mgi1.com> wrote:

> +1 in favor of dropping
>
> ------------------------------
> *From:* Mike Jones <Michael.Jones@microsoft.com>
> *To:* "jose@ietf.org" <jose@ietf.org>
> *Sent:* Tue, June 18, 2013 6:42:15 PM
> *Subject:* [jose] Should we keep or remove the JOSE JWS and JWE MIME
> types?
>
>  The JWS and JWE documents currently define these MIME types for the
> convenience of applications that may want to use them:
>
>                 application/jws
>
>                 application/jws+json
>
>                 application/jwe
>
>                 application/jwe+json
>
>
>
> That being said, I=92m not aware of any uses of these by applications at
> present.  Thus, I think that makes it fair game to ask whether we want to
> keep them or remove them =96 in which case, if applications ever needed t=
hem,
> they could define them later.
>
>
>
> Another dimension of this question for JWS and JWE is that it=92s not cle=
ar
> that the four types application/jws, application/jws+json, application/jw=
e,
> and application/jwe+json are even the right ones.  It might be more usefu=
l
> to have generic application/jose and application/jose+json types, which
> could hold either JWS or JWE objects respectively using the compact or JS=
ON
> serializations (although I=92m not advocating adding them at this time).
>
>
>
> Having different JWS versus JWE MIME types apparently did contribute to a=
t
> least Dick=92s confusion about the purpose of the =93typ=94 field, so del=
eting
> them could help eliminate this possibility of confusion in the future.
> Thus, I=92m increasingly convinced we should get rid of the JWS and JWE t=
ypes
> and leave it up to applications to define the types they need, when they
> need them.
>
>
>
> Do people have use cases for these four MIME types now or should we leave
> them to future specs to define, if needed?
>
>
>
>                                                                 -- Mike
>
>
>
> P.S.  For completeness, I=92ll add that the JWK document also defines the=
se
> MIME types:
>
>                 application/jwk+json
>
>                 application/jwk-set+json
>
>
>
> There are already clear use cases for these types, so I=92m not advocatin=
g
> deleting them, but wanted to call that out explicitly.  For instance, whe=
n
> retrieving a JWK Set document referenced by a =93jku=94 header parameter,=
 I
> believe that the result should use the application/jwk-set+json type.  (I=
n
> fact, I=92ll add this to the specs, unless there are any objections.)
> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
> application/jwk+json.  Both could also be as =93cty=94 values when encryp=
ting
> JWKs and JWK Sets, in contexts where that that would be useful.
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--047d7b111981c980c304df9c1085
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m okay dropping them.<br></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Thu, Jun 20, 2013 at 2:39 PM, E=
dmund Jay <span dir=3D"ltr">&lt;<a href=3D"mailto:ejay@mgi1.com" target=3D"=
_blank">ejay@mgi1.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div style=3D"font-family:tahoma,&#39;n=
ew york&#39;,times,serif;font-size:10pt"><div>+1 in favor of dropping</div>=
<div style=3D"font-family:tahoma,new york,times,serif;font-size:10pt">

<br><div style=3D"font-family:times new roman,new york,times,serif;font-siz=
e:12pt"><font face=3D"Tahoma"><hr size=3D"1"><b><span style=3D"font-weight:=
bold">From:</span></b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@micro=
soft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;<br>

<b><span style=3D"font-weight:bold">To:</span></b> &quot;<a href=3D"mailto:=
jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&quot; &lt;<a href=3D"mai=
lto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&gt;<br><b><span styl=
e=3D"font-weight:bold">Sent:</span></b> Tue, June 18, 2013 6:42:15 PM<br>

<b><span style=3D"font-weight:bold">Subject:</span></b> [jose] Should we ke=
ep or remove the JOSE JWS and JWE MIME types?<br></font><div><div class=3D"=
h5"><br>

=20
=20



<div>
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:</p>=
=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws+json</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe+json</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">That being said, I=92m not aware of any uses of thes=
e by applications at present.=A0 Thus, I think that makes it fair game to a=
sk whether we want to keep them or remove them =96 in which case, if applic=
ations ever needed them, they could define
 them later.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it=92s not clear that the four types application/jws, application/jw=
s+json, application/jwe, and application/jwe+json are even the right ones.=
=A0 It might be more useful to have generic
 application/jose and application/jose+json types, which could hold either =
JWS or JWE objects respectively using the compact or JSON serializations (a=
lthough I=92m not advocating adding them at this time).</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick=92s confusion about the purpose of the =
=93typ=94 field, so deleting them could help eliminate this possibility of =
confusion in the future.=A0 Thus, I=92m increasingly
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</p>=
=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">P.S.=A0 For completeness, I=92ll add that the JWK do=
cument also defines these MIME types:</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk+json</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk-set+json</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I=92m not advocating deleting them, but wanted to call that out explicitl=
y.=A0 For instance, when retrieving a JWK Set document referenced by a =93j=
ku=94 header parameter, I believe that the
 result should use the application/jwk-set+json type.=A0 (In fact, I=92ll a=
dd this to the specs, unless there are any objections.)=A0 Likewise, draft-=
miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.=A0 Both=
 could also be as =93cty=94 values when encrypting
 JWKs and JWK Sets, in contexts where that that would be useful.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
</div>


</div></div></div></div><div></div>


</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--047d7b111981c980c304df9c1085--

From rlb@ipv.sx  Thu Jun 20 13:52:25 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA2D21F9FDC for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.563
X-Spam-Level: *
X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwA+HKF-bI3w for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:52:01 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0E21F9E5C for <jose@ietf.org>; Thu, 20 Jun 2013 13:51:44 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so7686718obc.38 for <jose@ietf.org>; Thu, 20 Jun 2013 13:51:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=h17woPSJ3jph/jzVv4fwd7GLs0QYvIULjUrgeB+GTLU=; b=o2H3ub2GbfnCq+QC3etX/+Xaoh13JKUp4PYJeabzDubwd7xqijrHNTafWNd8rAoW8p lUUpM2RmD2p2RNO5XQqYg/GVwWKIskQ+mevSzdZAL/hyZEEkqeBGPiSSPwo5PLjSl/1g qJkqX5zk2udOrhpjHWE6d9T1oLok3oktfcBfOYr2Y3wDlRpJU3z9STY6TFRJVEg2+/ap o6Xir8dEzvk7Rm8EbfW0G8q8x9AxeZ1SDJ86Tyv53Xd1lLkMOu6LAflqmwcS1FmybP/q 1CgCc41USQ4u+HVi1KWNDwJGKRMcA6i9O5OvhrSc/yDIw2o/jBWxtEVgC12xktfHauxQ v0Tg==
MIME-Version: 1.0
X-Received: by 10.60.161.206 with SMTP id xu14mr5067838oeb.109.1371761504405;  Thu, 20 Jun 2013 13:51:44 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 13:51:44 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com>
References: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com>
Date: Thu, 20 Jun 2013 16:51:44 -0400
Message-ID: <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e01176a6d2fd91304df9c1dcc
X-Gm-Message-State: ALoCoQl5xUjhzU+OuG/EKd0y8PzJjaPcHE7WAnW3MJ6Q+6/8YfdZ4dRzipHdxrchWDA1Zgw8TEfe
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:52:26 -0000

--089e01176a6d2fd91304df9c1dcc
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

You can eliminate the "protection required" field, because there aren't any
of those.

Or there shouldn't be: The only security case we have is algorithm
dependent ("alg" must be protected if "alg" =3D=3D "PS256", "PS512").  The =
only
fields for which the specs currently require integrity protection are "zip"
and "crit".  Neither of these have the property that changing them would
cause a security violation, except in some application-dependent sense.  So
the choice of integrity protection should be left to applications, not
fixed in the spec.

--Richard


On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> <no hat>****
>
> ** **
>
> Having just started looking at a design implementation, I am now more tha=
n
> ever interested in seeing this matrix of fields.  At the present time I
> think the following columns are probably of interest:****
>
> ** **
>
> Name, must understand, use required, common vs specific, protection
> required****
>
> ** **
>
> I was just looking at the alg and enc fields for JWE and realized that on=
e
> was specific =96 so it should be one location =96 and one was common =96 =
so it
> should be in a different location.  And then I needed to start thinking
> about where it goes in terms of compacted vs one recipient vs two
> recipients.****
>
> ** **
>
> Do you have an idea of when this matrix might show up?****
>
> ** **
>
> Jim****
>
> ** **
>

--089e01176a6d2fd91304df9c1dcc
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You can eliminate the &quot;protection required&quot; fiel=
d, because there aren&#39;t any of those. =A0<div><br></div><div>Or there s=
houldn&#39;t be: The only security case we have is algorithm dependent (&qu=
ot;alg&quot; must be protected if &quot;alg&quot; =3D=3D &quot;PS256&quot;,=
 &quot;PS512&quot;). =A0The only fields for which the specs currently requi=
re integrity protection are &quot;zip&quot; and &quot;crit&quot;. =A0Neithe=
r of these have the property that changing them would cause a security viol=
ation, except in some application-dependent sense. =A0So the choice of inte=
grity protection should be left to applications, not fixed in the spec.<div=
>
<br></div><div>--Richard</div></div></div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_bl=
ank">ietf@augustcellars.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal">&lt;no hat&gt;<u></u><u></u></p><p class=
=3D"MsoNormal">
<u></u>=A0<u></u></p><p class=3D"MsoNormal">Having just started looking at =
a design implementation, I am now more than ever interested in seeing this =
matrix of fields.=A0 At the present time I think the following columns are =
probably of interest:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">Name, mu=
st understand, use required, common vs specific, protection required<u></u>=
<u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNorma=
l">I was just looking at the alg and enc fields for JWE and realized that o=
ne was specific =96 so it should be one location =96 and one was common =96=
 so it should be in a different location.=A0 And then I needed to start thi=
nking about where it goes in terms of compacted vs one recipient vs two rec=
ipients.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">Do you h=
ave an idea of when this matrix might show up?<span class=3D"HOEnZb"><font =
color=3D"#888888"><u></u><u></u></font></span></p><span class=3D"HOEnZb"><f=
ont color=3D"#888888"><p class=3D"MsoNormal">
<u></u>=A0<u></u></p><p class=3D"MsoNormal">Jim<u></u><u></u></p><p class=
=3D"MsoNormal"><u></u>=A0<u></u></p></font></span></div></div></blockquote>=
</div><br></div>

--089e01176a6d2fd91304df9c1dcc--

From rlb@ipv.sx  Thu Jun 20 13:52:47 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC5A21F9FFD for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.529
X-Spam-Level: *
X-Spam-Status: No, score=1.529 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHGXb9cHJ9+a for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 13:52:43 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id EF23F11E80D3 for <jose@ietf.org>; Thu, 20 Jun 2013 13:52:40 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id f4so8486855oah.35 for <jose@ietf.org>; Thu, 20 Jun 2013 13:52:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=n0PldZvzEDFvcbr2PimFdBrTwrojrr98EA0NAph1ClQ=; b=Ez/gBqBKP9BZKByUqqt4qWlVPSRPf9LtpWEb8lE2/CvHlXhHnnyyLiEVmKrU7TrwnW nWUYg3yrwJKj+BYcaHldZtIapKgJfFOKmMB2d4Wp3MybveW5qp50CenpHuj+qAO9wGGp 9uL3CV38Fy8Z6S5QY9MupZWtQrmZygwY22+YcGlZOtmzCPDVr6FzfKtwCdezGTCF8Drk DEBDW5W1ajlV/I32lK1wbuQmse3un1+q9i08dTluKHvBdl+uQ7ONIEpB6QkPEXJpM+KM ru0pSh+SyCQTKK5/0j/fZXF8YCDzxjGQnGNzcQejdMu+CHlFgrsDkEloy3B3xX3p2rWB k3mA==
MIME-Version: 1.0
X-Received: by 10.60.144.233 with SMTP id sp9mr5213246oeb.53.1371761560330; Thu, 20 Jun 2013 13:52:40 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 13:52:40 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com> <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com>
Date: Thu, 20 Jun 2013 16:52:40 -0400
Message-ID: <CAL02cgRkQEkuvLJqmZ-NQKE6ET4J1zN2FUT018+FgLjEsa8aFg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Brian Campbell <bcampbell@pingidentity.com>
Content-Type: multipart/alternative; boundary=047d7b3a8b6685333404df9c20ca
X-Gm-Message-State: ALoCoQmHn/Ktng5pTJdq/GxpTh3GRWcvSYuKt1vaj8ht7HqavOPFFYCC+6B+f5wIyZ5hwYIAHP/l
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>, Edmund Jay <ejay@mgi1.com>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 20:52:47 -0000

--047d7b3a8b6685333404df9c20ca
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

To be clear, when people say "dropping them", you mean "changing from four
MIME types to two", right?

Dropping the MIME types altogether is not an option, as Matt noted.

--Richard


On Thu, Jun 20, 2013 at 4:47 PM, Brian Campbell
<bcampbell@pingidentity.com>wrote:

> I'm okay dropping them.
>
>
> On Thu, Jun 20, 2013 at 2:39 PM, Edmund Jay <ejay@mgi1.com> wrote:
>
>> +1 in favor of dropping
>>
>> ------------------------------
>> *From:* Mike Jones <Michael.Jones@microsoft.com>
>> *To:* "jose@ietf.org" <jose@ietf.org>
>> *Sent:* Tue, June 18, 2013 6:42:15 PM
>> *Subject:* [jose] Should we keep or remove the JOSE JWS and JWE MIME
>> types?
>>
>>  The JWS and JWE documents currently define these MIME types for the
>> convenience of applications that may want to use them:
>>
>>                 application/jws
>>
>>                 application/jws+json
>>
>>                 application/jwe
>>
>>                 application/jwe+json
>>
>>
>>
>> That being said, I=92m not aware of any uses of these by applications at
>> present.  Thus, I think that makes it fair game to ask whether we want t=
o
>> keep them or remove them =96 in which case, if applications ever needed =
them,
>> they could define them later.
>>
>>
>>
>> Another dimension of this question for JWS and JWE is that it=92s not cl=
ear
>> that the four types application/jws, application/jws+json, application/j=
we,
>> and application/jwe+json are even the right ones.  It might be more usef=
ul
>> to have generic application/jose and application/jose+json types, which
>> could hold either JWS or JWE objects respectively using the compact or J=
SON
>> serializations (although I=92m not advocating adding them at this time).
>>
>>
>>
>> Having different JWS versus JWE MIME types apparently did contribute to
>> at least Dick=92s confusion about the purpose of the =93typ=94 field, so=
 deleting
>> them could help eliminate this possibility of confusion in the future.
>> Thus, I=92m increasingly convinced we should get rid of the JWS and JWE =
types
>> and leave it up to applications to define the types they need, when they
>> need them.
>>
>>
>>
>> Do people have use cases for these four MIME types now or should we leav=
e
>> them to future specs to define, if needed?
>>
>>
>>
>>                                                                 -- Mike
>>
>>
>>
>> P.S.  For completeness, I=92ll add that the JWK document also defines th=
ese
>> MIME types:
>>
>>                 application/jwk+json
>>
>>                 application/jwk-set+json
>>
>>
>>
>> There are already clear use cases for these types, so I=92m not advocati=
ng
>> deleting them, but wanted to call that out explicitly.  For instance, wh=
en
>> retrieving a JWK Set document referenced by a =93jku=94 header parameter=
, I
>> believe that the result should use the application/jwk-set+json type.  (=
In
>> fact, I=92ll add this to the specs, unless there are any objections.)
>> Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses
>> application/jwk+json.  Both could also be as =93cty=94 values when encry=
pting
>> JWKs and JWK Sets, in contexts where that that would be useful.
>>
>>
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--047d7b3a8b6685333404df9c20ca
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">To be clear, when people say &quot;dropping them&quot;, yo=
u mean &quot;changing from four MIME types to two&quot;, right?<div><br></d=
iv><div>Dropping the MIME types altogether is not an option, as Matt noted.=
</div>
<div><br></div><div>--Richard</div></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">On Thu, Jun 20, 2013 at 4:47 PM, Brian Campbell=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:bcampbell@pingidentity.com" target=
=3D"_blank">bcampbell@pingidentity.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I&#39;m okay dropping them.=
<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"><di=
v><div class=3D"h5">
On Thu, Jun 20, 2013 at 2:39 PM, Edmund Jay <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ejay@mgi1.com" target=3D"_blank">ejay@mgi1.com</a>&gt;</span> wr=
ote:<br>

</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5"><div><div=
 style=3D"font-family:tahoma,&#39;new york&#39;,times,serif;font-size:10pt"=
><div>
+1 in favor of dropping</div><div style=3D"font-family:tahoma,new york,time=
s,serif;font-size:10pt">

<br><div style=3D"font-family:times new roman,new york,times,serif;font-siz=
e:12pt"><font face=3D"Tahoma"><hr size=3D"1"><b><span style=3D"font-weight:=
bold">From:</span></b> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@micro=
soft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;<br>


<b><span style=3D"font-weight:bold">To:</span></b> &quot;<a href=3D"mailto:=
jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&quot; &lt;<a href=3D"mai=
lto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>&gt;<br><b><span styl=
e=3D"font-weight:bold">Sent:</span></b> Tue, June 18, 2013 6:42:15 PM<br>


<b><span style=3D"font-weight:bold">Subject:</span></b> [jose] Should we ke=
ep or remove the JOSE JWS and JWE MIME types?<br></font><div><div><br>

=20
=20



<div>
<p class=3D"MsoNormal">The JWS and JWE documents currently define these MIM=
E types for the convenience of applications that may want to use them:</p>=
=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jws+json</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwe+json</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">That being said, I=92m not aware of any uses of thes=
e by applications at present.=A0 Thus, I think that makes it fair game to a=
sk whether we want to keep them or remove them =96 in which case, if applic=
ations ever needed them, they could define
 them later.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Another dimension of this question for JWS and JWE i=
s that it=92s not clear that the four types application/jws, application/jw=
s+json, application/jwe, and application/jwe+json are even the right ones.=
=A0 It might be more useful to have generic
 application/jose and application/jose+json types, which could hold either =
JWS or JWE objects respectively using the compact or JSON serializations (a=
lthough I=92m not advocating adding them at this time).</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Having different JWS versus JWE MIME types apparentl=
y did contribute to at least Dick=92s confusion about the purpose of the =
=93typ=94 field, so deleting them could help eliminate this possibility of =
confusion in the future.=A0 Thus, I=92m increasingly
 convinced we should get rid of the JWS and JWE types and leave it up to ap=
plications to define the types they need, when they need them.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">Do people have use cases for these four MIME types n=
ow or should we leave them to future specs to define, if needed?</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</p>=
=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">P.S.=A0 For completeness, I=92ll add that the JWK do=
cument also defines these MIME types:</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk+json</p>=20
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 applic=
ation/jwk-set+json</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
<p class=3D"MsoNormal">There are already clear use cases for these types, s=
o I=92m not advocating deleting them, but wanted to call that out explicitl=
y.=A0 For instance, when retrieving a JWK Set document referenced by a =93j=
ku=94 header parameter, I believe that the
 result should use the application/jwk-set+json type.=A0 (In fact, I=92ll a=
dd this to the specs, unless there are any objections.)=A0 Likewise, draft-=
miller-jose-jwe-protected-jwk-02 already uses application/jwk+json.=A0 Both=
 could also be as =93cty=94 values when encrypting
 JWKs and JWK Sets, in contexts where that that would be useful.</p>=20
<p class=3D"MsoNormal"> =A0</p>=20
</div>


</div></div></div></div><div></div>


</div></div><br></div></div><div class=3D"im">_____________________________=
__________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--047d7b3a8b6685333404df9c20ca--

From Michael.Jones@microsoft.com  Thu Jun 20 14:03:31 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F4121E804E for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 14:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0COtQnrVZ2eW for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 14:03:25 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0211.outbound.protection.outlook.com [207.46.163.211]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2A821E8093 for <jose@ietf.org>; Thu, 20 Jun 2013 14:03:24 -0700 (PDT)
Received: from BY2FFO11FD025.protection.gbl (10.1.15.204) by BY2FFO11HUB028.protection.gbl (10.1.14.139) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 20 Jun 2013 21:02:12 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD025.mail.protection.outlook.com (10.1.15.214) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 20 Jun 2013 21:02:12 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Thu, 20 Jun 2013 21:01:40 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] Field Matrix
Thread-Index: Ac5t5xRPeyoH6vXbTWe6CTWcVqhYoAAEOSMAAAAwarA=
Date: Thu, 20 Jun 2013 21:01:40 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436787AC69@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com> <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com>
In-Reply-To: <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.79]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436787AC69TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(24454002)(199002)(189002)(377454003)(54316002)(56816003)(66066001)(79102001)(55846006)(19300405004)(81342001)(4396001)(71186001)(65816001)(54356001)(74662001)(74502001)(74366001)(16236675002)(46102001)(44976004)(16406001)(512954002)(53806001)(51856001)(76482001)(77982001)(31966008)(76786001)(20776003)(77096001)(74876001)(50986001)(74706001)(81542001)(69226001)(80022001)(63696002)(76796001)(47446002)(47976001)(15202345003)(47736001)(49866001)(56776001)(33656001)(6806003)(59766001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB028; H:TK5EX14HUBC106.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08831F51DC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 21:03:32 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436787AC69TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There was a working group decision at the Denver meeting that "crit" must b=
e integrity protected.  The reason for this is straightforward.

If not integrity protected, an attacker could strip the "crit" field, defea=
ting the semantic requirement that implementations must reject the input if=
 a "crit" value is used that is not understood.  Thus, the spec requires th=
at this field be integrity protected whenever used.

                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Thursday, June 20, 2013 1:52 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Field Matrix

You can eliminate the "protection required" field, because there aren't any=
 of those.

Or there shouldn't be: The only security case we have is algorithm dependen=
t ("alg" must be protected if "alg" =3D=3D "PS256", "PS512").  The only fie=
lds for which the specs currently require integrity protection are "zip" an=
d "crit".  Neither of these have the property that changing them would caus=
e a security violation, except in some application-dependent sense.  So the=
 choice of integrity protection should be left to applications, not fixed i=
n the spec.

--Richard

On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

Having just started looking at a design implementation, I am now more than =
ever interested in seeing this matrix of fields.  At the present time I thi=
nk the following columns are probably of interest:

Name, must understand, use required, common vs specific, protection require=
d

I was just looking at the alg and enc fields for JWE and realized that one =
was specific - so it should be one location - and one was common - so it sh=
ould be in a different location.  And then I needed to start thinking about=
 where it goes in terms of compacted vs one recipient vs two recipients.

Do you have an idea of when this matrix might show up?

Jim



--_000_4E1F6AAD24975D4BA5B16804296739436787AC69TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There was a working group=
 decision at the Denver meeting that &#8220;crit&#8221; must be integrity p=
rotected.&nbsp; The reason for this is straightforward.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If not integrity protecte=
d, an attacker could strip the &#8220;crit&#8221; field, defeating the sema=
ntic requirement that implementations must reject the input if a &#8220;cri=
t&#8221;
 value is used that is not understood.&nbsp; Thus, the spec requires that t=
his field be integrity protected whenever used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 1:52 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Field Matrix<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">You can eliminate the &quot;protection required&quot=
; field, because there aren't any of those. &nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Or there shouldn't be: The only security case we hav=
e is algorithm dependent (&quot;alg&quot; must be protected if &quot;alg&qu=
ot; =3D=3D &quot;PS256&quot;, &quot;PS512&quot;). &nbsp;The only fields for=
 which the specs currently require integrity protection are &quot;zip&quot;=
 and &quot;crit&quot;. &nbsp;Neither
 of these have the property that changing them would cause a security viola=
tion, except in some application-dependent sense. &nbsp;So the choice of in=
tegrity protection should be left to applications, not fixed in the spec.<o=
:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Having just started looking at a design implementation, I am now m=
ore than ever interested in seeing this matrix of fields.&nbsp; At the pres=
ent time I think the following columns are
 probably of interest:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Name, must understand, use required, common vs specific, protectio=
n required<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was just looking at the alg and enc fields for JWE and realized =
that one was specific &#8211; so it should be one location &#8211; and one =
was common &#8211; so it should be in a different location.&nbsp;
 And then I needed to start thinking about where it goes in terms of compac=
ted vs one recipient vs two recipients.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Do you have an idea of when this matrix might show up?<o:p></o:p><=
/p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436787AC69TK5EX14MBXC283r_--

From rlb@ipv.sx  Thu Jun 20 14:52:18 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC2D411E80E1 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 14:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.504
X-Spam-Level: 
X-Spam-Status: No, score=0.504 tagged_above=-999 required=5 tests=[AWL=1.147,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nP9+OFtgNgjs for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 14:52:14 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E583221F942B for <jose@ietf.org>; Thu, 20 Jun 2013 14:52:11 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id ef5so7795120obb.1 for <jose@ietf.org>; Thu, 20 Jun 2013 14:52:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=nEZOSJmp75N5MPTCRHm3Fh2HM3a55/ERQItpMPZGS4o=; b=DjzkftDkjtj5zWiRnZLHBWTjrzhE6BGFNVfF5MOCvON1tv0cjmJ8BbmUir5fESHwvb 5R0aSkHAecSWwy02xR36wnHbGAKpFqr1V0SRufUWD1aLX2jY+aFdJ+t29DrGpMe7XoRR Bu/y/V9dLHdeg+IQczZl6y8rZbFQjL896p+bhNrwWUilAcYBQ80JYMh01+dxvzWV8Puh 1etxyhHFh5lPyfrH8oOvDSjX3/qARBrx0kikrlfOvlHuATh1w5SAS5XlsKbS7iI7myo5 uA/7zz4eqabyowcuwctBtiBXV1gko1U+3lrgxNYTJ/nVGDWkwDATJIE6bhWbWTJovgIb IwaA==
MIME-Version: 1.0
X-Received: by 10.182.125.1 with SMTP id mm1mr2386944obb.47.1371765131366; Thu, 20 Jun 2013 14:52:11 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 14:52:11 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>
Date: Thu, 20 Jun 2013 17:52:11 -0400
Message-ID: <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e0122ac505f343c04df9cf5ba
X-Gm-Message-State: ALoCoQnNA756rQVJTrGfAaRe3LiuE5wLXRN5xofMunGX6ON+6TvOzc4iJ9MFrBiugB6pIWqKJpaR
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 21:52:18 -0000

--089e0122ac505f343c04df9cf5ba
Content-Type: text/plain; charset=ISO-8859-1

## Summary

For those playing along at home, the document in question is NIST SP800-56A:
<http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar2.pdf>

That document calls for the following required inputs to the KDF:
1. AlgorithmID: an identifier for the algorithm that the derived keys will
be used for
2. PartyUInfo: Not null, including at least ID_U
3. PartyVInfo: Not null, including at least ID_V

The relevant text for JOSE is in JWA:
<
http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-11#section-4.7.1
>


## Commentary

Right now, the spec seems to me to be mostly compliant with the letter of
SP800-56A.  It seems like a few small tweaks would bring it to full
compliance.

AlgorithmID is almost right, but it needs to distinguish between the direct
and wrapped cases.  In the case of "ECDH-ES+A128KW", the AlgorithmID should
be set to the "alg" value, as it is now.  In the case of "ECDH-ES", the
AlgorithmID should be value of the "enc" parameter.

PartyUInfo seems compliant with the letter of the SP800-56A.  SP800-56A
doesn't place any constraints on the form or duration of the identifier
ID_U, so the 512-bit value provided seems sufficient if you regard that as
ID_U.

PartyVInfo is clearly non-compliant, because SP800-56A requires it to be
non-null.  It seems like there are a few possible ways to resolve this:
1. Use a random string, as in PartyUInfo.  Possibly split the 512 bits
currently in PartyUInfo into two 256-bit halves, one for PartyUInfo and one
in PartyVInfo.
2. Use another identifier, e.g., the value of the "kid" parameter


## Counterproposal

Of course, this all seems pretty abusive and not in the spirit of
SP800-56A.  The fact that this question is still unresolved makes me wonder
how existing implementations are populating these fields.  There are three
possible cases:
1. Current JOSE ECDH code populates the concat fields correctly according
to SP800-56A
2. Current JOSE ECDH code popluates the concat fields incorrectly
3. No current JOSE code actually implements ECDH

In case (1), the spec should just require what the code is doing.
In case (2), the implementations are going to have to change anyway, to
have correct behavior.

I suspect the real situation is case (3), based on a cursory survey of
implementations, or at best (2), based on the current state of the spec.
 In either of those cases, our work here need not be constrained by
existing code (since it will have to change anyway), so we could do
something crazy like use a KDF that we don't have to abuse.  PBKDF2 would
be one option.

The better option would be to use the same KDF that CMS uses
[RFC3278][SEC1].  It's simpler, and also complies with USG mandates (Suite
B [RFC5008]).  If we use the RFC 5008 variant, it also takes as input
exactly what the current JWS spec provides:

KM = Hash ( Z || Counter || ECC-CMS-SharedInfo )

ECC-CMS-SharedInfo = {
    keyInfo, // The algorithm with which the key will be used, currently in
AlgorithmID
    entityUInfo, // The entropy source we're currently putting in PartyUInfo
    suppPubInfo // The derived key length, currently in SuppPubInfo
}

In other words, CMS does exactly what JWS wants to do now.  Let's just do
it for real.  Proposed text for Section 4.7.1 of JWA:

"""
The key derivation process derives the agreed upon key from the shared
secret Z established through the ECDH algorithm using the single-pass KDF
defined in [SEC1].  The inputs to the key derivation process are as follows:

Z This is set to the representation of the shared secret Z as an octet
sequence.

SharedInfo This is set to the concatenation of the following octet strings,
in order:
   1. The algorithm with which the derived key is to be used.  If the "alg"
value is "ECDH", then this field contains the value of the "alg" parameter.
 Otherwise, it contains the value of the "enc" parameter.
   2. The length of the value of the "apu" parameter, as a 32-bit big
endian integer.  If the "apu" parameter is not present, then this field is
set to all zeros (0x00000000).
   3. The value of the "apu" parameter, if present.  If provided, this
value MUST contain at least 512 bits and a unique value SHOULD be used for
each recipient.  The "apu" parameter MAY be omitted only if a different
ephemeral key is used for each key agreement transaction.
   4. The length of the derived key, as a 32-bit big endian integer.  For
"ECDH-ES", this is length of the key used by the "enc" algorithm.  For
"ECDH-ES+A128KW" or "ECDH-ES+A256KW", it is 128 (0x00000080) or 256
(0x00000100), respectively.
"""

Two side notes:
1. We need hash agility here (as in RFC 5008) to be able to meet higher
levels of security for which SHA-256 is unacceptable.  Suggest adding hash
algorithms to the ECDH algorithm identifiers, e.g., "ECDH256", "ECDH284+KW".
2. The "-ES" is unnecessary, since the entropy added in entityUInfo is
sufficient to address both ES and SS cases.

--Richard






On Tue, Jun 18, 2013 at 5:39 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> I have gone back a re-read the NIST document from the top, and there are
> going to be some problems with trying to comply with them in some cases.
>
> Let's look at the fields from top to bottom
>
> AlgorithmID - I would agree that this should be alg in the case of doing a
> key wrap key and enc in the case of doing a CEK.
>
> Identities of PartyU and PartyV - these are well known as PartyU is always
> the initiator and PartyV is always the acceptor.  In a store and forward
> environment where we are doing static-ephemeral the ephemeral is always
> associated with PartyU.  I do not believe that this needs to be made
> explicit in the document but that can be addressed later.
>
> IDs - there is a problem with what to use for identifiers in for the JOSE
> work.  In many cases there is just a key and not necessarily a well-defined
> identifier that both parties are going to agree on.  This is something that
> we cannot really do at present because there is no name component of a JWK
> and any other name is going to be based on the application and not on what
> is known to the JOSE library.  It is even harder because the sender can,
> with an ephemeral key, want to remain anonymous and therefore the recipient
> has no agreed upon identifier with the sender.
>
> In theory, the names used should not need to be transmitted as part of the
> message as it is assumed that both parties will understand what the
> identifiers are (or they will have exchanged them in an online protocol).
> One possible course is to say that by default the names "Sender" and
> "Receiver" will be used as the identifiers unless other names are provided
> by the application protocol.  In this case they would not need to be
> transmitted as they are known to each entity.
>
> There is also a requirement for a nonce to be sent for a simple
> static-static case, this is not a current requirement and would be defined
> for the case of a static-static algorithm.  I don't believe that we need to
> define the 'nonce' field to carry this value at this time.
>
> Jim
>
>
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> > Manger, James H
> > Sent: Sunday, June 16, 2013 6:20 PM
> > To: jose@ietf.org
> > Subject: [jose] Concat KDF
> >
> > The use of the Concat KDF still does not look right.
> >
> > JWA [draft-ietf-jose-json-web-algorithms-11] section 4.7 says "ECDH-ES"
> > uses Concat KDF from NIST 800-56A section 5.8.1. NIST defines 5 fields
> that
> > go into the key derivation: AlgorithmID, PartyUInfo, PartyVInfo,
> > SuppPubInfo, and SuppPrivInfo.
> >
> > NIST says AlgorithmID indicates the algorithm that will use the derived
> key.
> > JWA says to use the "alg" value (eg "ECDH-ES") as the AlgorithmID.
> > AlgorithmID should actually be the "enc" value when the derived key is
> used
> > directly as a CEK. When the derived key unwraps the CEK, AlgorithmID
> should
> > be the name of the key wrap algorithm (eg "A128KW"). Perhaps the "alg"
> > value can be used in this case as it identifies the key wrap algorithm
> along
> > with the key establishment algorithm (eg "ECDH-ES+A128KW").
> >
> > NIST says PartyUInfo includes an identifier for party U. The first
> problem
> is
> > that JWA does not indicate if the sender or receiver is party U (nor does
> > JWE). The second problem is that JWA says PartyUInfo is random -- which
> > seems to totally defeat the purpose of being an identifier for a party.
> JWA
> > says PartyUInfo should vary for each recipient, which suggests PartyUInfo
> > cannot be an id of the sender. Does that suggest the receiver is party U?
> >
> > NIST says PartyVInfo is required and includes an identifier for party V.
> JWA
> > says PartyVInfo is empty, which obviously cannot meet the NIST
> definition.
> >
> > The JWA values for SuppPubInfo (length of derived key in bits) and
> > SuppPrivInfo (empty) are in line with the NIST definitions.
> >
> >
> > It appears the Concat KDF text in JWA has been rewritten based on RFC2631
> > "Diffie-Hellman Key Agreement Method". RFC2631 is not referenced by JWA,
> > but it is mentioned in the "document history" section (which will
> eventually
> > be deleted). RFC2631 has items such as partyAInfo and suppPubInfo whose
> > names are similar to NIST items. However, RFC2631 was published 7 years
> > before NIST 800-56A (and 13 years before the current version of NIST 800-
> > 56A) so RFC2631 cannot be used as a example of how to use Concat KDF.
> >
> > --
> > James Manger
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--089e0122ac505f343c04df9cf5ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>## Summary</div><div><br></div>For those playing alon=
g at home, the document in question is NIST SP800-56A:<div>&lt;<a href=3D"h=
ttp://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar2.pdf">=
http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar2.pdf<=
/a>&gt;</div>
<div><br></div><div>That document calls for the following required inputs t=
o the KDF:</div><div>1. AlgorithmID: an identifier for the algorithm that t=
he derived keys will be used for</div><div>2. PartyUInfo: Not null, includi=
ng at least ID_U</div>
<div>3. PartyVInfo: Not null, including at least ID_V</div><div><br></div><=
div>The relevant text for JOSE is in JWA:<br>&lt;<a href=3D"http://tools.ie=
tf.org/html/draft-ietf-jose-json-web-algorithms-11#section-4.7.1">http://to=
ols.ietf.org/html/draft-ietf-jose-json-web-algorithms-11#section-4.7.1</a>&=
gt;</div>
<div><br></div><div><br></div><div>## Commentary</div><div><br></div><div>R=
ight now, the spec seems to me to be mostly compliant with the letter of SP=
800-56A. =A0It seems like a few small tweaks would bring it to full complia=
nce.</div>
<div><br></div><div>AlgorithmID is almost right, but it needs to distinguis=
h between the direct and wrapped cases. =A0In the case of &quot;ECDH-ES+A12=
8KW&quot;, the AlgorithmID should be set to the &quot;alg&quot; value, as i=
t is now. =A0In the case of &quot;ECDH-ES&quot;, the AlgorithmID should be =
value of the &quot;enc&quot; parameter.</div>
<div><br></div><div>PartyUInfo seems compliant with the letter of the SP800=
-56A. =A0SP800-56A doesn&#39;t place any constraints on the form or duratio=
n of the identifier ID_U, so the 512-bit value provided seems sufficient if=
 you regard that as ID_U.</div>
<div><br></div><div>PartyVInfo is clearly non-compliant, because SP800-56A =
requires it to be non-null. =A0It seems like there are a few possible ways =
to resolve this:</div><div>1. Use a random string, as in PartyUInfo. =A0Pos=
sibly split the 512 bits currently in PartyUInfo into two 256-bit halves, o=
ne for PartyUInfo and one in PartyVInfo.</div>
<div>2. Use another identifier, e.g., the value of the &quot;kid&quot; para=
meter</div><div><br></div><div><br></div><div>## Counterproposal</div><div>=
<br></div><div>Of course, this all seems pretty abusive and not in the spir=
it of SP800-56A. =A0The fact that this question is still unresolved makes m=
e wonder how existing implementations are populating these fields. =A0There=
 are three possible cases:</div>
<div>1. Current JOSE ECDH code populates the concat fields correctly accord=
ing to SP800-56A<br></div><div>2. Current JOSE ECDH code popluates the conc=
at fields incorrectly</div><div>3. No current JOSE code actually implements=
 ECDH</div>
<div><br></div><div>In case (1), the spec should just require what the code=
 is doing.</div><div>In case (2), the implementations are going to have to =
change anyway, to have correct behavior.<br></div><div><br></div><div>I sus=
pect the real situation is case (3), based on a cursory survey of implement=
ations, or at best (2), based on the current state of the spec. =A0In eithe=
r of those cases, our work here need not be constrained by existing code (s=
ince it will have to change anyway), so we could do something crazy like us=
e a KDF that we don&#39;t have to abuse. =A0PBKDF2 would be one option.</di=
v>
<div><br></div><div>The better option would be to use the same KDF that CMS=
 uses [RFC3278][SEC1]. =A0It&#39;s simpler, and also complies with USG mand=
ates (Suite B [RFC5008]). =A0If we use the RFC 5008 variant, it also takes =
as input exactly what the current JWS spec provides:</div>
<div><br></div><div>KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo )<br><=
/div><div><br></div><div>ECC-CMS-SharedInfo =3D {</div><div>=A0 =A0 keyInfo=
, // The algorithm with which the key will be used, currently in AlgorithmI=
D</div>
<div>=A0 =A0 entityUInfo, // The entropy source we&#39;re currently putting=
 in PartyUInfo</div><div>=A0 =A0 suppPubInfo // The derived key length, cur=
rently in=A0<span style=3D"color:rgb(0,0,0);font-size:1em">SuppPubInfo</spa=
n></div>
<div>}</div><div><br></div><div>In other words, CMS does exactly what JWS w=
ants to do now. =A0Let&#39;s just do it for real. =A0Proposed text for Sect=
ion 4.7.1 of JWA:</div><div><br></div><div>&quot;&quot;&quot;</div><div>The=
 key derivation process derives the agreed upon key from the shared secret =
Z established through the ECDH algorithm using the single-pass KDF defined =
in [SEC1]. =A0The inputs to the key derivation process are as follows:</div=
>
<div><br></div><div>Z This is set to the representation of the shared secre=
t Z as an octet sequence.</div><div><br></div><div>SharedInfo This is set t=
o the concatenation of the following octet strings, in order:</div><div>
=A0 =A01. The algorithm with which the derived key is to be used. =A0If the=
 &quot;alg&quot; value is &quot;ECDH&quot;, then this field contains the va=
lue of the &quot;alg&quot; parameter. =A0Otherwise, it contains the value o=
f the &quot;enc&quot; parameter.</div>
<div>=A0 =A02. The length of the value of the &quot;apu&quot; parameter, as=
 a 32-bit big endian integer. =A0If the &quot;apu&quot; parameter is not pr=
esent, then this field is set to all zeros (0x00000000).</div><div>=A0 =A03=
. The value of the &quot;apu&quot; parameter, if present. =A0If provided, t=
his value MUST contain at least 512 bits and a unique value SHOULD be used =
for each recipient. =A0The &quot;apu&quot; parameter MAY be omitted only if=
 a different ephemeral key is used for each key agreement transaction.</div=
>
<div>=A0 =A04. The length of the derived key, as a 32-bit big endian intege=
r. =A0For &quot;ECDH-ES&quot;, this is length of the key used by the &quot;=
enc&quot; algorithm. =A0For &quot;ECDH-ES+A128KW&quot; or &quot;ECDH-ES+A25=
6KW&quot;, it is 128 (0x00000080) or 256 (0x00000100), respectively.</div>
<div>&quot;&quot;&quot;</div><div><br></div><div>Two side notes:</div><div>=
1. We need hash agility here (as in RFC 5008) to be able to meet higher lev=
els of security for which SHA-256 is unacceptable. =A0Suggest adding hash a=
lgorithms to the ECDH algorithm identifiers, e.g., &quot;ECDH256&quot;, &qu=
ot;ECDH284+KW&quot;.<br>
</div><div>2. The &quot;-ES&quot; is unnecessary, since the entropy added i=
n entityUInfo is sufficient to address both ES and SS cases.</div><div><br>=
</div><div>--Richard</div><div><br></div><div><br></div><div><br></div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 18, 2013 at 5:39 PM, Jim Schaad <span dir=3D"ltr">&lt;<=
a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcella=
rs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I have gone back a re-read the NIST document=
 from the top, and there are<br>
going to be some problems with trying to comply with them in some cases.<br=
>
<br>
Let&#39;s look at the fields from top to bottom<br>
<br>
AlgorithmID - I would agree that this should be alg in the case of doing a<=
br>
key wrap key and enc in the case of doing a CEK.<br>
<br>
Identities of PartyU and PartyV - these are well known as PartyU is always<=
br>
the initiator and PartyV is always the acceptor. =A0In a store and forward<=
br>
environment where we are doing static-ephemeral the ephemeral is always<br>
associated with PartyU. =A0I do not believe that this needs to be made<br>
explicit in the document but that can be addressed later.<br>
<br>
IDs - there is a problem with what to use for identifiers in for the JOSE<b=
r>
work. =A0In many cases there is just a key and not necessarily a well-defin=
ed<br>
identifier that both parties are going to agree on. =A0This is something th=
at<br>
we cannot really do at present because there is no name component of a JWK<=
br>
and any other name is going to be based on the application and not on what<=
br>
is known to the JOSE library. =A0It is even harder because the sender can,<=
br>
with an ephemeral key, want to remain anonymous and therefore the recipient=
<br>
has no agreed upon identifier with the sender.<br>
<br>
In theory, the names used should not need to be transmitted as part of the<=
br>
message as it is assumed that both parties will understand what the<br>
identifiers are (or they will have exchanged them in an online protocol).<b=
r>
One possible course is to say that by default the names &quot;Sender&quot; =
and<br>
&quot;Receiver&quot; will be used as the identifiers unless other names are=
 provided<br>
by the application protocol. =A0In this case they would not need to be<br>
transmitted as they are known to each entity.<br>
<br>
There is also a requirement for a nonce to be sent for a simple<br>
static-static case, this is not a current requirement and would be defined<=
br>
for the case of a static-static algorithm. =A0I don&#39;t believe that we n=
eed to<br>
define the &#39;nonce&#39; field to carry this value at this time.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jim<br>
</font></span><div class=3D"im HOEnZb"><br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</=
a>] On Behalf Of<br>
&gt; Manger, James H<br>
&gt; Sent: Sunday, June 16, 2013 6:20 PM<br>
&gt; To: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: [jose] Concat KDF<br>
&gt;<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">&gt; The use of the Concat KD=
F still does not look right.<br>
&gt;<br>
&gt; JWA [draft-ietf-jose-json-web-algorithms-11] section 4.7 says &quot;EC=
DH-ES&quot;<br>
&gt; uses Concat KDF from NIST 800-56A section 5.8.1. NIST defines 5 fields=
<br>
that<br>
&gt; go into the key derivation: AlgorithmID, PartyUInfo, PartyVInfo,<br>
&gt; SuppPubInfo, and SuppPrivInfo.<br>
&gt;<br>
&gt; NIST says AlgorithmID indicates the algorithm that will use the derive=
d<br>
key.<br>
&gt; JWA says to use the &quot;alg&quot; value (eg &quot;ECDH-ES&quot;) as =
the AlgorithmID.<br>
&gt; AlgorithmID should actually be the &quot;enc&quot; value when the deri=
ved key is<br>
used<br>
&gt; directly as a CEK. When the derived key unwraps the CEK, AlgorithmID<b=
r>
should<br>
&gt; be the name of the key wrap algorithm (eg &quot;A128KW&quot;). Perhaps=
 the &quot;alg&quot;<br>
&gt; value can be used in this case as it identifies the key wrap algorithm=
<br>
along<br>
&gt; with the key establishment algorithm (eg &quot;ECDH-ES+A128KW&quot;).<=
br>
&gt;<br>
&gt; NIST says PartyUInfo includes an identifier for party U. The first pro=
blem<br>
is<br>
&gt; that JWA does not indicate if the sender or receiver is party U (nor d=
oes<br>
&gt; JWE). The second problem is that JWA says PartyUInfo is random -- whic=
h<br>
&gt; seems to totally defeat the purpose of being an identifier for a party=
.<br>
JWA<br>
&gt; says PartyUInfo should vary for each recipient, which suggests PartyUI=
nfo<br>
&gt; cannot be an id of the sender. Does that suggest the receiver is party=
 U?<br>
&gt;<br>
&gt; NIST says PartyVInfo is required and includes an identifier for party =
V.<br>
JWA<br>
&gt; says PartyVInfo is empty, which obviously cannot meet the NIST definit=
ion.<br>
&gt;<br>
&gt; The JWA values for SuppPubInfo (length of derived key in bits) and<br>
&gt; SuppPrivInfo (empty) are in line with the NIST definitions.<br>
&gt;<br>
&gt;<br>
&gt; It appears the Concat KDF text in JWA has been rewritten based on RFC2=
631<br>
&gt; &quot;Diffie-Hellman Key Agreement Method&quot;. RFC2631 is not refere=
nced by JWA,<br>
&gt; but it is mentioned in the &quot;document history&quot; section (which=
 will<br>
eventually<br>
&gt; be deleted). RFC2631 has items such as partyAInfo and suppPubInfo whos=
e<br>
&gt; names are similar to NIST items. However, RFC2631 was published 7 year=
s<br>
&gt; before NIST 800-56A (and 13 years before the current version of NIST 8=
00-<br>
&gt; 56A) so RFC2631 cannot be used as a example of how to use Concat KDF.<=
br>
&gt;<br>
&gt; --<br>
&gt; James Manger<br>
&gt; _______________________________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</div></div></blockquote></div><br></div>

--089e0122ac505f343c04df9cf5ba--

From rlb@ipv.sx  Thu Jun 20 15:00:45 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9505A21F9EBC for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 15:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.361
X-Spam-Level: *
X-Spam-Status: No, score=1.361 tagged_above=-999 required=5 tests=[AWL=0.004,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+tqRILqBraY for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 15:00:40 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE6021F9E9E for <jose@ietf.org>; Thu, 20 Jun 2013 15:00:40 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id v19so7734303obq.35 for <jose@ietf.org>; Thu, 20 Jun 2013 15:00:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rojKG7yfpA4t06wZiTguh4lJtOW0mTIveAWn2FTzaxo=; b=dgy/uKqDNCtbKY0SGJ4WMhS2NxXfTri/+tKOVU+EUOGuqctlyH4JYezAV/zAU4cj8I 1TAJnbfUihqpj37lx8xQ7z5RQQ69Sco82QwwEopxdx4DFF2d330y9aTCuXbkxT7MxaWT BjxwSzz0/lL0aQcavvpBOkqeusyDPagHGts/6eruVch7rdImWiUyE8U6sywPkTDS9MfN /BZ2zD6NaGHuYfd/MB0yKvj+BhmeQCA7N3uhFIpqGdD0M9LshfvmCjUa5XPqunFVrM0X D04UJtslx0vxwOueOGpf1IhsW1pQD3Ej1cQck9UfoIIoTpuk5V+cCoY1zOo76m1SV+pa 14jQ==
MIME-Version: 1.0
X-Received: by 10.182.61.105 with SMTP id o9mr2347823obr.54.1371765639896; Thu, 20 Jun 2013 15:00:39 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 15:00:39 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436787AC69@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com> <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436787AC69@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 20 Jun 2013 18:00:39 -0400
Message-ID: <CAL02cgTu=LMdH5VEdCsUAs0Ro3qeu_4MZ6viY5QF7axpQmYkZQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=e89a8fb1ea30ae745b04df9d13f3
X-Gm-Message-State: ALoCoQkghD9k+mQNNGM0W61b0gFScGMYiWNoi1ord4hJ/uKOk6C0ymPP7+tSJWEXZms9Co6WS0Vy
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 22:00:45 -0000

--e89a8fb1ea30ae745b04df9d13f3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

There was no such decision.  Quoting directly from the minutes:
"""
**  Crit Text

Two questions were raised for dealing with the cirt field.  Does the crit
field need to be signed and do the members listed in the crit field need to
be signed.

There was no consensus in the group at this time as we adjourned for the da=
y
"""

In order for the attack you describe to be an actual security risk, it
would need to be the case that the parameters in "crit" were
security-critical, as opposed to things that would simply cause incorrect
processing.  One can certainly imagine parameters that would fall in the
latter bin; my current favorite example is a "part" parameter that would
allow fragmentation / reassembly.  Because such parameters exist, it's
possible to use "crit" safely without integrity protection.

Can we at least agree that integrity protecting "zip" is unnecessary?  The
only thing that stripping / changing "zip" causes is a processing failure,
not a security compromise.

--Richard



On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  There was a working group decision at the Denver meeting that =93crit=94
> must be integrity protected.  The reason for this is straightforward.****
>
> ** **
>
> If not integrity protected, an attacker could strip the =93crit=94 field,
> defeating the semantic requirement that implementations must reject the
> input if a =93crit=94 value is used that is not understood.  Thus, the sp=
ec
> requires that this field be integrity protected whenever used.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 20, 2013 1:52 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Field Matrix****
>
> ** **
>
> You can eliminate the "protection required" field, because there aren't
> any of those.  ****
>
> ** **
>
> Or there shouldn't be: The only security case we have is algorithm
> dependent ("alg" must be protected if "alg" =3D=3D "PS256", "PS512").  Th=
e only
> fields for which the specs currently require integrity protection are "zi=
p"
> and "crit".  Neither of these have the property that changing them would
> cause a security violation, except in some application-dependent sense.  =
So
> the choice of integrity protection should be left to applications, not
> fixed in the spec.****
>
> ** **
>
> --Richard****
>
> ** **
>
> On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> Having just started looking at a design implementation, I am now more tha=
n
> ever interested in seeing this matrix of fields.  At the present time I
> think the following columns are probably of interest:****
>
>  ****
>
> Name, must understand, use required, common vs specific, protection
> required****
>
>  ****
>
> I was just looking at the alg and enc fields for JWE and realized that on=
e
> was specific =96 so it should be one location =96 and one was common =96 =
so it
> should be in a different location.  And then I needed to start thinking
> about where it goes in terms of compacted vs one recipient vs two
> recipients.****
>
>  ****
>
> Do you have an idea of when this matrix might show up?****
>
>  ****
>
> Jim****
>
>  ****
>
> ** **
>

--e89a8fb1ea30ae745b04df9d13f3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>There was no such decision. =A0Quoting directly from =
the minutes:</div><div>&quot;&quot;&quot;</div><div><div>** =A0Crit Text</d=
iv><div><br></div><div>Two questions were raised for dealing with the cirt =
field. =A0Does the crit field need to be signed and do the members listed i=
n the crit field need to be signed.</div>
<div><br></div><div>There was no consensus in the group at this time as we =
adjourned for the day</div></div><div>&quot;&quot;&quot;</div><div><br></di=
v>In order for the attack you describe to be an actual security risk, it wo=
uld need to be the case that the parameters in &quot;crit&quot; were securi=
ty-critical, as opposed to things that would simply cause incorrect process=
ing. =A0One can certainly imagine parameters that would fall in the latter =
bin; my current favorite example is a &quot;part&quot; parameter that would=
 allow fragmentation / reassembly. =A0Because such parameters exist, it&#39=
;s possible to use &quot;crit&quot; safely without integrity protection.<di=
v>
<br></div><div>Can we at least agree that integrity protecting &quot;zip&qu=
ot; is unnecessary? =A0The only thing that stripping / changing &quot;zip&q=
uot; causes is a processing failure, not a security compromise.</div><div>
<br></div><div>--Richard</div><div><br><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_=
blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">There was a working group decision at the Denver meet=
ing that =93crit=94 must be integrity protected.=A0 The reason for this is =
straightforward.<u></u><u></u></span></p>


<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">If not integrity protected, an attacker could strip t=
he =93crit=94 field, defeating the semantic requirement that implementation=
s must reject the input if a =93crit=94
 value is used that is not understood.=A0 Thus, the spec requires that this=
 field be integrity protected whenever used.<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u>=
<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"=
_blank">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 1:52 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Field Matrix<u></u><u></u></span></p><div><div>
<p class=3D""><u></u>=A0<u></u></p>
<div>
<p class=3D"">You can eliminate the &quot;protection required&quot; field, =
because there aren&#39;t any of those. =A0<u></u><u></u></p>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">Or there shouldn&#39;t be: The only security case we have is =
algorithm dependent (&quot;alg&quot; must be protected if &quot;alg&quot; =
=3D=3D &quot;PS256&quot;, &quot;PS512&quot;). =A0The only fields for which =
the specs currently require integrity protection are &quot;zip&quot; and &q=
uot;crit&quot;. =A0Neither
 of these have the property that changing them would cause a security viola=
tion, except in some application-dependent sense. =A0So the choice of integ=
rity protection should be left to applications, not fixed in the spec.<u></=
u><u></u></p>


<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">--Richard<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"">On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad &lt;<a href=3D"ma=
ilto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&g=
t; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">Having just started looking at a design implementation, I am =
now more than ever interested in seeing this matrix of fields.=A0 At the pr=
esent time I think the following columns are
 probably of interest:<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">Name, must understand, use required, common vs specific, prot=
ection required<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">I was just looking at the alg and enc fields for JWE and real=
ized that one was specific =96 so it should be one location =96 and one was=
 common =96 so it should be in a different location.=A0
 And then I needed to start thinking about where it goes in terms of compac=
ted vs one recipient vs two recipients.<u></u><u></u></p>
<p class=3D"">=A0<u></u><u></u></p>
<p class=3D"">Do you have an idea of when this matrix might show up?<u></u>=
<u></u></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">=A0<u></u><u></u></spa=
n></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">Jim<u></u><u></u></spa=
n></p>
<p class=3D""><span style=3D"color:rgb(136,136,136)">=A0<u></u><u></u></spa=
n></p>
</div>
</div>
</div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div></div></div>

--e89a8fb1ea30ae745b04df9d13f3--

From James.H.Manger@team.telstra.com  Thu Jun 20 16:57:43 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7607121E80C9 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 16:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.664
X-Spam-Level: 
X-Spam-Status: No, score=-0.664 tagged_above=-999 required=5 tests=[AWL=0.237,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5dQs4bYj6XX for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 16:57:36 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id 025CA21E80AD for <jose@ietf.org>; Thu, 20 Jun 2013 16:57:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,908,1363093200"; d="scan'208";a="142523382"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipobvi.tcif.telstra.com.au with ESMTP; 21 Jun 2013 09:57:33 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7112"; a="139525082"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipcdvi.tcif.telstra.com.au with ESMTP; 21 Jun 2013 09:57:33 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Fri, 21 Jun 2013 09:57:33 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Mike Jones <Michael.Jones@microsoft.com>, Richard Barnes <rlb@ipv.sx>
Date: Fri, 21 Jun 2013 09:57:32 +1000
Thread-Topic: [jose] Common elements (was: Re: Should we keep or remove the JOSE JWS and JWE MIME types?)
Thread-Index: AQHObeXN1GY2mXm1UkS/cH+IeFF5Vpk+9RbQgABLqwA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BB8F653@WSMSG3153V.srv.dir.telstra.com>
References: <CAL02cgThKXYYmKpB+_XVCE3cBPDsX=cKnNaEYdKOEqz1cy8aLw@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394367879E91@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367879E91@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>
Subject: Re: [jose] Common elements (was: Re: Should we keep or remove the JOSE JWS and JWE MIME types?)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 20 Jun 2013 23:57:43 -0000

PiBFZGl0b3JpYWxseSwgaWYgd2UgZG8gZGVjaWRlIHRvIGFkZCBhcHBsaWNhdGlvbi9qb3NlIGFu
ZCBhcHBsaWNhdGlvbi9qb3NlK2pzb24gTUlNRSB0eXBlcywgSSB3b3VsZCByZWdpc3RlciB0aGVt
IGluIGRyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmUsIGp1c3QgbGlrZSBvdGhlciBy
ZWdpc3RyeSBjb250ZW50IHNoYXJlZCBiZXR3ZWVuIEpXUyBhbmQgSldFLCBzdWNoIGFzIHRoZSBK
U09OIFdlYiBTaWduYXR1cmUgYW5kIEVuY3J5cHRpb24gSGVhZGVyIFBhcmFtZXRlcnMgUmVnaXN0
cnkuDQoNCj4+IFdoaWxlIHdlJ3JlIGF0IGl0LCB5b3UgY291bGQgbW92ZSBvdmVyIHRoZSBoZWFk
ZXIgcGFyYW1ldGVycyB0aGF0IGFyZSBzaGFyZWQgYmV0d2VlbiB0aGUgdHdvLiAgTmFtZWx5IGFs
bCBidXQgImVuYyIgYW5kICJ6aXAiLiAgKCJlcGsiLCBhbmQgImFwdSIgc2hvdWxkIG1vdmUgdG8g
SldBLikNCg0KKzENCg0KPj4gQW5kIG9uY2UgeW91IGRvIHRoYXQsIGl0IHNlZW1zIG1vcmUgYW5k
IG1vcmUgbGlrZSBKV0UgaXMgYmVjb21pbmcgdGhlIGxpdHRsZSBicm90aGVyIHRvIEpXUywgaW4g
d2hpY2ggY2FzZSB3ZSBtaWdodCBhcyB3ZWxsIGNvbWJpbmUgdGhlbS4NCg0KKzAuNQ0KV2UgZG8g
bmVlZCBhICpzaW5nbGUqIGRlc2NyaXB0aW9uIG9mIHRoZSBiYXNpYyBzdHJ1Y3R1cmUgb2YgYW55
IEpPU0Ugb2JqZWN0LiBDYWxsaW5nIHN1Y2ggYSBzcGVjICJKV1MiIGlzIG5vdCBpZGVhbC4gV2l0
aCBhIHNlbnNpYmxlIHNlcGFyYXRpb24gb2YgdGhlIHNwZWMgaW50byBzZWN0aW9ucyBvbiB0aGUg
YmFzaWMgc3RydWN0dXJlLCBhIHNlY3Rpb24gb2Ygc2lnbmluZywgYSBzZWN0aW9uIG9uIE1BQ2lu
ZywgYSBzZWN0aW9uIG9uIGF1dGhlbnRpY2F0ZWQgZW5jcnlwdGlvbiwgc2VjdGlvbnMgb24ga2V5
IGV4Y2hhbmdlLi4uIC0tIGl0IHdvdWxkbid0IG1hdHRlciBxdWl0ZSBzbyBtdWNoIGlmLCBzYXks
IHRoZSBlbmNyeXB0aW9uIHNlY3Rpb24gd2FzIGluIGEgc2VwYXJhdGUgZG9jdW1lbnQgYXMgbG9u
ZyBhcyBpdCBkaWRuJ3QgaGF2ZSB0byBkdXBsaWNhdGUgc28gbXVjaCB0ZXh0IHRoZSB3YXkgSldF
IGRvZXMuDQoNCj4gQXMgeW91IGtub3cgZnJvbSBvdXIgcHJpdmF0ZSBjb252ZXJzYXRpb24gYWJv
dXQgeW91ciByZXZpZXcgY29tbWVudHMsIHdoaWxlIGNsb3NlbHkgcmVsYXRlZCwgdGhlIGtleSBz
ZWxlY3Rpb24gaGVhZGVyIHBhcmFtZXRlciBkZWZpbml0aW9ucyBhcmUsIGJ5IGRlc2lnbiwgbm90
IGlkZW50aWNhbCBiZXR3ZWVuIHRoZSBKV1MgYW5kIEpXRSBzcGVjLiAgSW4gSldTIHRoZXkgcmVm
ZXIgdG8gdGhlIGtleSB0aGF0IGlzIHVzZWQgdG8gY2hlY2sgdGhlIHNpZ25hdHVyZS9NQUMuICBJ
biBKV0UgdGhleSByZWZlciB0byB0aGUga2V5IHRvIHdoaWNoIHRoZSBKV0Ugd2FzIGVuY3J5cHRl
ZC4gIFRyeWluZyB0byBjb2FsZXNjZSB0aGVtIHdvdWxkIG9ubHkgbWFrZSB0aGUgdGV4dCB1bm5l
Y2Vzc2FyaWx5IG11ZGRpZXIgaW4gYm90aCBjYXNlcy4NCg0KQ29hbGVzY2luZyB0aGUgdGV4dCB3
b3VsZCBoaWdobGlnaHQgdGhlIGRlc2lnbiBmbGF3IHRoYXQgdGhlIHNhbWUgZmllbGQgKGVnICJr
aWQiKSBpbiB0aGUgc2FtZSBwbGFjZSAoSk9TRSBoZWFkZXIpIGhhcyBkaWZmZXJlbnQgbWVhbmlu
Z3MgKGVnIGlkZW50aWZ5aW5nIGEgcmVjaXBpZW50IGtleSBvciBpZGVudGlmeWluZyBhbiBvcmln
aW5hdG9yIGtleSkuIEl0IG1pZ2h0IGhlbHAgdXMgZml4IHRoYXQgZGVzaWduIGZsYXcuDQoNCi0t
DQpKYW1lcyBNYW5nZXINCg==

From ietf@augustcellars.com  Thu Jun 20 18:29:37 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98BF311E8142 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.54
X-Spam-Level: 
X-Spam-Status: No, score=-3.54 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ruRqEa8EYbmd for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:29:31 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5C911E8143 for <jose@ietf.org>; Thu, 20 Jun 2013 18:29:30 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 2CD222CA40; Thu, 20 Jun 2013 18:29:30 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-json-web-encryption@tools.ietf.org>
Date: Thu, 20 Jun 2013 18:28:35 -0700
Message-ID: <05ca01ce6e1e$a663ddc0$f32b9940$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05CB_01CE6DE3.FA0553E0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac5uHoEIhUHF1bDIRb+g9Dwvv0NexQ==
Cc: jose@ietf.org
Subject: [jose] Keys in the documents
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 01:29:37 -0000

This is a multipart message in MIME format.

------=_NextPart_000_05CB_01CE6DE3.FA0553E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Is there any reason not to provide the public and private keys in the
appendixes as JWK objects?  This would make them easier to understand and
put them into a format that one expects to be understood by JOSE systems.

 

Jim

 


------=_NextPart_000_05CB_01CE6DE3.FA0553E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Is there =
any reason not to provide the public and private keys in the appendixes =
as JWK objects? &nbsp;This would make them easier to understand and put =
them into a format that one expects to be understood by JOSE =
systems.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_05CB_01CE6DE3.FA0553E0--


From mamille2@cisco.com  Thu Jun 20 18:36:04 2013
Return-Path: <mamille2@cisco.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E670221F9458 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deMu53EeR4P2 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:36:00 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id F289E21F92C2 for <jose@ietf.org>; Thu, 20 Jun 2013 18:35:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6837; q=dns/txt; s=iport; t=1371778560; x=1372988160; h=from:to:cc:subject:date:message-id:mime-version; bh=rJ3P7ZGKjGWV+EnAM/g6mjuXDZQ9UwNamfU/7mNGTc0=; b=KSLMMBInDdXaSJ6DdOJ3tdYsJCEzdqTYL/S4A257Ij8bGtyTDYo+cJet XAQKQGTvmLPLFjjyu5iJMnZTzfxC8OAsk2FnJyn/N69VBbOzI9zDnRNWF JDmS9ondxkBmIXYA9jMbCCjEMJgefaY7jsWjNI6GiSIg8jiDSEG3HoABp Y=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsFAH6sw1GtJV2a/2dsb2JhbABbgwkxSYI8vHqBARZtB4IlAQR5EgEqJjAPGAQOBQgGDYdzDLwqjxgxgwdhA5ADgSyHPZAbgw+CKA
X-IronPort-AV: E=Sophos;i="4.87,908,1363132800";  d="p7s'?scan'208";a="225593979"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP; 21 Jun 2013 01:35:59 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r5L1Zx5S006861 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Jun 2013 01:35:59 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Thu, 20 Jun 2013 20:35:58 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: About POSH
Thread-Index: AQHObh+umQVbfFv2HUWCkWB31tIuLQ==
Date: Fri, 21 Jun 2013 01:35:58 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411528E538@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.93.120]
Content-Type: multipart/signed; boundary="Apple-Mail=_C05E032C-B5FD-4118-9FAD-B7B5D2445F28"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Peter Saint-Andre <stpeter@stpeter.im>
Subject: [jose] About POSH
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 01:36:05 -0000

--Apple-Mail=_C05E032C-B5FD-4118-9FAD-B7B5D2445F28
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello all,

As has been indirectly discussed previously, Peter Saint-Andre and I =
have been working on secure delegation; how a source domain (e.g., =
example.com) can prove it has delegated some non-HTTP service to another =
domain (e.g., hosting.example.net), without handing over things like =
private keys.  One of the possible solutions we've developed is [POSH].

Of direct interest for JOSE is that POSH (ab)uses JWK Set objects as the =
content format.

Any feedback this group can provide would be greatly appreciated.  The =
discussion forum is < posh@ietf.org >.


Thanks!

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

[POSH] :: PKIX over Secure HTTP (POSH) < =
http://tools.ietf.org/html/draft-miller-posh-00 >=

--Apple-Mail=_C05E032C-B5FD-4118-9FAD-B7B5D2445F28
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMezCCBjQw
ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX
DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK
75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC
+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD
z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr
/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc
fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG
XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt
UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R
HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv
sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq
+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT
zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq
Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1
9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPzCCBSeg
AwIBAgIDBoRIMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN
MTMwNDMwMjE1NDQyWhcNMTQwNTAyMDUzOTA0WjBbMRkwFwYDVQQNExBiN2F6NndOY0t0R3JtMEpF
MRswGQYDVQQDDBJtYW1pbGxlMkBjaXNjby5jb20xITAfBgkqhkiG9w0BCQEWEm1hbWlsbGUyQGNp
c2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJbKBMsG+9UFTx9uq/bhhXgu
vJvO8z7cwKaqqwZhVf5z/kHFyCNijtmTOE+YXjA8mWR4aoBwB5SvGypI/cJUofJ+AlBTC4g+RMx/
K0Ab4/jQqTQz9CDzMOB+Wm+rt8ZJ7A8ZzOJmNDAsf/VvB8l2A1SQz1UsAixgH16NTr8SlblAXEKk
4hwpCudUiNjjQokqJ0H686UBKVorcZSgXaza8XMqGtJF/8mNhR9GQYi7Xht1ky+9LFOrto2daZto
KJRwMeVusVdHUeKEQSu7jztw8HchH3KEb7Q+r5X+hhDZoddfKE8d5eyPuhiZdrzv7OlNZ0fSLdx7
3AE3nx9/R5YlXucCAwEAAaOCAtgwggLUMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQW
MBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUxGd+/qrdVudHrIKkw5xOMY7eaLUwHwYD
VR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWFtaWxsZTJAY2lzY28u
Y29tMIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9m
IHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBw
dXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYG
A1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4G
CCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy
dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAlDhXbGEI7lbqUcu5r2JHZaMsbRZda/99ZqODzWGX
0llou9jGccsAWDPPwRRe2+ROpXfH4cuJZElTcLDeZSp/qpXKhjYieFSX8+Ml9sKEj5UOSqQLyoLk
PtrIJV12Jk3nuG2Jc0UeEnGwK/aqtzy7+bfEVI0ziyVM2gChHh0RH74KyiwYWknbOTRIkZcz/ulE
DVFQp63uj6wfmDNvAUHBAdhKVqA1S/rfP1KcDZpf1NfvwXJibiqTRA6K1EOxTJOP41n/XdvHqHXL
RWL2xrOUI9/URANr/ok3OrsuZEMFnAAGefS1bWS/hFtUGVkHGiKEBbyDW7da2ULXbuC7umrQnzGC
A28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDAJBgUrDgMCGgUA
oIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MjEwMTM1
NTdaMCMGCSqGSIb3DQEJBDEWBBSCio5TdWyUYGmNE4TsZBosJLiV7zCBpQYJKwYBBAGCNxAEMYGX
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3Mg
MSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDCBpwYLKoZIhvcNAQkQAgsxgZeg
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBoRIMA0GCSqGSIb3DQEBAQUABIIBAIgj
dDan4KED7o2cXCegTp9m18syf3YWIPCywJTs/PnR39o8xRFouge4P3sub9VrVJcXynUSKLuvmzjI
pwpgJ7voN+3EgFswExQ/U4nZDCGBpw0hzs4O0zs7VP20v6sONa1wt3NSC4ZtubFjUt0kReHNwPDM
2lQKQALDx+84FQwQH0jCtK02/6fyyrkJDFyNHfAHb2DaJt223PY/QvfmgWu29Z0SVuQdEZ8ts/06
ircgQf6G6UtuOZ86Yj8/SeRRPFoPrAwsw1+BvT5TXxHu+NYgO2iMyWrtuU4a6b1E/otDin/m/nyv
/X4saqBbmbletiTBpSjOIr35vT1TXrlDfPIAAAAAAAA=

--Apple-Mail=_C05E032C-B5FD-4118-9FAD-B7B5D2445F28--

From James.H.Manger@team.telstra.com  Thu Jun 20 18:50:28 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62F2321E80F8 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.672
X-Spam-Level: 
X-Spam-Status: No, score=-1.672 tagged_above=-999 required=5 tests=[AWL=1.229,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aguQMZ2ALwKX for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 18:50:02 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id A7FB611E8144 for <jose@ietf.org>; Thu, 20 Jun 2013 18:50:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,909,1363093200"; d="scan'208";a="142740154"
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipocvi.tcif.telstra.com.au with ESMTP; 21 Jun 2013 11:49:59 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7112"; a="140249358"
Received: from wsmsg3702.srv.dir.telstra.com ([172.49.40.170]) by ipcbvi.tcif.telstra.com.au with ESMTP; 21 Jun 2013 11:49:59 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3702.srv.dir.telstra.com ([172.49.40.170]) with mapi; Fri, 21 Jun 2013 11:49:49 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
Date: Fri, 21 Jun 2013 11:49:43 +1000
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5uAG20UjuawbqlQIaVY1C52sOChQAE6v5Q
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>
In-Reply-To: <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 01:50:28 -0000

PiBQYXJ0eVVJbmZvIHNlZW1zIGNvbXBsaWFudCB3aXRoIHRoZSBsZXR0ZXIgb2YgdGhlIFNQODAw
LTU2QS4gwqBTUDgwMC01NkENCj4gZG9lc24ndCBwbGFjZSBhbnkgY29uc3RyYWludHMgb24gdGhl
IGZvcm0gb3IgZHVyYXRpb24gb2YgdGhlIGlkZW50aWZpZXINCj4gSURfVSwgc28gdGhlIDUxMi1i
aXQgdmFsdWUgcHJvdmlkZWQgc2VlbXMgc3VmZmljaWVudCBpZiB5b3UgcmVnYXJkIHRoYXQNCj4g
YXMgSURfVS4NCg0KT25lIGFzcGVjdCB0aGF0IGhhcyBiZWVuIGNvbmZ1c2luZyBtZSBpcyB3aGV0
aGVyIHRoZSByZWNpcGllbnQgaXMgZXhwZWN0ZWQgdG8gcmVjb2duaXplIElEX1UgYXMgYSBrbm93
biBpZGVudGlmaWVyIGZvciB0aGUgb3JpZ2luYXRvciwgYW5kIElEX1YgYXMgaXRzIG93biBuYW1l
Pw0KDQpBbHRlcm5hdGl2ZWx5LCBkbyByZXF1aXJlbWVudHMgb24gdGhlc2UgaXRlbXMgb25seSBh
cHBseSB0byB0aGUgb3JpZ2luYXRvcj8gSXMgaXQgY29tcGxldGVseSBzYWZlIGZvciBhIHJlY2lw
aWVudCB0byB0cmVhdCBJRF9VIGFuZCBJRF9WIGFzIG9wYXF1ZSBieXRlcyB0byBiZSBoYXNoZWQg
YXMgcGFydCBvZiB0aGUgS0RGLCBidXQgd2l0aCBubyBvdGhlciBwcm9jZXNzaW5nPyBJcyBpdCwg
aW4gZmFjdCwgc2FmZSBmb3IgYSByZWNpcGllbnQgdG8gdHJlYXQgT3RoZXJJbmZvIChBbGdvcml0
aG1JRCArIFBhcnR5VUluZm8gKy4uLikgYXMgYW4gb3BhcXVlIGJsb2IsIG9yIGV2ZW4gT3RoZXJJ
bnB1dCAoa2V5ZGF0YWxlbiArIE90aGVySW5mbykgYXMgYW4gb3BhcXVlIGJsb2I/IEluIHdoaWNo
IGNhc2UsIHdlIGNvdWxkIHNpbXBseSBpbmNsdWRlIEI2NChPdGhlcklucHV0KSBpbiBhIEpPU0Ug
bWVzc2FnZSwgcGVyaGFwcyB3aXRoIGEgc3VnZ2VzdGVkIHdheSBhbiBvcmlnaW5hdG9yIGNvdWxk
IGNvbnN0cnVjdCBPdGhlcklucHV0IChlZyBmcm9tIGFsZywgZW5jLCBraWQvamt1LCBub25jZSku
DQoNCg0KPiBUaGUgYmV0dGVyIG9wdGlvbiB3b3VsZCBiZSB0byB1c2UgdGhlIHNhbWUgS0RGIHRo
YXQgQ01TIHVzZXMNCj4gW1JGQzMyNzhdW1NFQzFdLiDCoEl0J3Mgc2ltcGxlciwgYW5kIGFsc28g
Y29tcGxpZXMgd2l0aCBVU0cgbWFuZGF0ZXMNCj4gKFN1aXRlIEIgW1JGQzUwMDhdKS4gwqBJZiB3
ZSB1c2UgdGhlIFJGQyA1MDA4IHZhcmlhbnQsIGl0IGFsc28gdGFrZXMgYXMNCj4gaW5wdXQgZXhh
Y3RseSB3aGF0IHRoZSBjdXJyZW50IEpXUyBzcGVjIHByb3ZpZGVzOg0KPiANCj4gS00gPSBIYXNo
ICggWiB8fCBDb3VudGVyIHx8IEVDQy1DTVMtU2hhcmVkSW5mbyApDQo+IA0KPiBFQ0MtQ01TLVNo
YXJlZEluZm8gPSB7DQo+IMKgIMKgIGtleUluZm8sIC8vIFRoZSBhbGdvcml0aG0gd2l0aCB3aGlj
aCB0aGUga2V5IHdpbGwgYmUgdXNlZCwNCj4gY3VycmVudGx5IGluIEFsZ29yaXRobUlEDQo+IMKg
IMKgIGVudGl0eVVJbmZvLCAvLyBUaGUgZW50cm9weSBzb3VyY2Ugd2UncmUgY3VycmVudGx5IHB1
dHRpbmcgaW4NCj4gUGFydHlVSW5mbw0KPiDCoCDCoCBzdXBwUHViSW5mbyAvLyBUaGUgZGVyaXZl
ZCBrZXkgbGVuZ3RoLCBjdXJyZW50bHkgaW7CoFN1cHBQdWJJbmZvDQo+IH0NCj4gDQo+IEluIG90
aGVyIHdvcmRzLCBDTVMgZG9lcyBleGFjdGx5IHdoYXQgSldTIHdhbnRzIHRvIGRvIG5vdy4gwqBM
ZXQncyBqdXN0DQo+IGRvIGl0IGZvciByZWFsLiDCoFByb3Bvc2VkIHRleHQgZm9yIFNlY3Rpb24g
NC43LjEgb2YgSldBOg0KDQpZb3VyIHByb3Bvc2FsIGlzICJsb2dpY2FsbHkiIHRoZSBzYW1lIGFz
IENNUyAoc28gc2FtZSBzZWN1cml0eSBwcm9wZXJ0aWVzKSwgYnV0IHRoZSBwcmVjaXNlIGNhbGN1
bGF0aW9uIGlzIGluY29tcGF0aWJsZSBhcyB5b3UgZG9uJ3QgdXNlIGEgREVSLWVuY29kaW5nIG9m
IEVDQy1DTVMtU2hhcmVkSW5mby4gSnVzdCB3YW50ZWQgdG8gY2xhcmlmeSB0aGlzIGludGVudGlv
bi4NCg0KPiAiIiINCj4gVGhlIGtleSBkZXJpdmF0aW9uIHByb2Nlc3MgZGVyaXZlcyB0aGUgYWdy
ZWVkIHVwb24ga2V5IGZyb20gdGhlIHNoYXJlZA0KPiBzZWNyZXQgWiBlc3RhYmxpc2hlZCB0aHJv
dWdoIHRoZSBFQ0RIIGFsZ29yaXRobSB1c2luZyB0aGUgc2luZ2xlLXBhc3MNCj4gS0RGIGRlZmlu
ZWQgaW4gW1NFQzFdLiDCoFRoZSBpbnB1dHMgdG8gdGhlIGtleSBkZXJpdmF0aW9uIHByb2Nlc3Mg
YXJlIGFzDQo+IGZvbGxvd3M6DQo+IA0KPiBaIFRoaXMgaXMgc2V0IHRvIHRoZSByZXByZXNlbnRh
dGlvbiBvZiB0aGUgc2hhcmVkIHNlY3JldCBaIGFzIGFuIG9jdGV0DQo+IHNlcXVlbmNlLg0KPiAN
Cj4gU2hhcmVkSW5mbyBUaGlzIGlzIHNldCB0byB0aGUgY29uY2F0ZW5hdGlvbiBvZiB0aGUgZm9s
bG93aW5nIG9jdGV0DQo+IHN0cmluZ3MsIGluIG9yZGVyOg0KPiDCoCDCoDEuIFRoZSBhbGdvcml0
aG0gd2l0aCB3aGljaCB0aGUgZGVyaXZlZCBrZXkgaXMgdG8gYmUgdXNlZC4gwqBJZiB0aGUNCj4g
ImFsZyIgdmFsdWUgaXMgIkVDREgiLCB0aGVuIHRoaXMgZmllbGQgY29udGFpbnMgdGhlIHZhbHVl
IG9mIHRoZSAiYWxnIg0KPiBwYXJhbWV0ZXIuIMKgT3RoZXJ3aXNlLCBpdCBjb250YWlucyB0aGUg
dmFsdWUgb2YgdGhlICJlbmMiIHBhcmFtZXRlci4NCg0KV3Jvbmcgd2F5IGFyb3VuZC4gSWYgImFs
ZyIgaXMgIkVDREgiIHVzZSAiZW5jIiB2YWx1ZSwgb3RoZXJ3aXNlIHVzZSAiYWxnIiB2YWx1ZS4N
Cg0KWW91IGFsc28gbmVlZCB0byBzZXBhcmF0ZSB0aGlzIGZpZWxkIGZyb20gdGhlIG5leHQ6IHdp
dGggYSBsZW5ndGggcHJlZml4LCBvciBzZXBhcmF0b3IgY2hhci9ieXRlLg0KV2l0aCAyIHZhcmlh
YmxlLXNpemVkIGZpZWxkcyAoYWxnb3JpdGhtIGFuZCBhcHUpIHlvdSBvbmx5IHRoZW9yZXRpY2Fs
bHkgbmVlZCAxIGxlbmd0aCBmaWVsZCB0byBiZSB1bmFtYmlndW91cywgYnV0IGl0IG5lZWRzIHRv
IGJlIGF0IHRoZSBzdGFydCBvciBlbmQsIG5vdCBpbiBiZXR3ZWVuIHRoZSAyIGZpZWxkcy4NCg0K
PiDCoCDCoDIuIFRoZSBsZW5ndGggb2YgdGhlIHZhbHVlIG9mIHRoZSAiYXB1IiBwYXJhbWV0ZXIs
IGFzIGEgMzItYml0IGJpZw0KPiBlbmRpYW4gaW50ZWdlci4gwqBJZiB0aGUgImFwdSIgcGFyYW1l
dGVyIGlzIG5vdCBwcmVzZW50LCB0aGVuIHRoaXMgZmllbGQNCj4gaXMgc2V0IHRvIGFsbCB6ZXJv
cyAoMHgwMDAwMDAwMCkuDQo+IMKgIMKgMy4gVGhlIHZhbHVlIG9mIHRoZSAiYXB1IiBwYXJhbWV0
ZXIsIGlmIHByZXNlbnQuIMKgSWYgcHJvdmlkZWQsIHRoaXMNCj4gdmFsdWUgTVVTVCBjb250YWlu
IGF0IGxlYXN0IDUxMiBiaXRzIGFuZCBhIHVuaXF1ZSB2YWx1ZSBTSE9VTEQgYmUgdXNlZA0KPiBm
b3IgZWFjaCByZWNpcGllbnQuIMKgVGhlICJhcHUiIHBhcmFtZXRlciBNQVkgYmUgb21pdHRlZCBv
bmx5IGlmIGENCj4gZGlmZmVyZW50IGVwaGVtZXJhbCBrZXkgaXMgdXNlZCBmb3IgZWFjaCBrZXkg
YWdyZWVtZW50IHRyYW5zYWN0aW9uLg0KPiDCoCDCoDQuIFRoZSBsZW5ndGggb2YgdGhlIGRlcml2
ZWQga2V5LCBhcyBhIDMyLWJpdCBiaWcgZW5kaWFuIGludGVnZXIuDQo+IMKgRm9yICJFQ0RILUVT
IiwgdGhpcyBpcyBsZW5ndGggb2YgdGhlIGtleSB1c2VkIGJ5IHRoZSAiZW5jIiBhbGdvcml0aG0u
DQo+IMKgRm9yICJFQ0RILUVTK0ExMjhLVyIgb3IgIkVDREgtRVMrQTI1NktXIiwgaXQgaXMgMTI4
ICgweDAwMDAwMDgwKSBvcg0KPiAyNTYgKDB4MDAwMDAxMDApLCByZXNwZWN0aXZlbHkuDQoNClN5
bW1ldHJpYyBrZXkgbGVuZ3RocyBhcmUgaGFyZHdpcmVkIGludG8gImFsZyIgYW5kICJlbmMiIHZh
bHVlcyBpbiBKT1NFIChlZyAiQTI1NktXIiwgIkExMjhDR00iKSBzbyB3ZSBkb24ndCBhY3R1YWxs
eSBuZWVkIGEgc2VwYXJhdGUgZmllbGQuDQoNCj4gIiIiDQo+IA0KPiBUd28gc2lkZSBub3RlczoN
Cj4gMS4gV2UgbmVlZCBoYXNoIGFnaWxpdHkgaGVyZSAoYXMgaW4gUkZDIDUwMDgpIHRvIGJlIGFi
bGUgdG8gbWVldCBoaWdoZXINCj4gbGV2ZWxzIG9mIHNlY3VyaXR5IGZvciB3aGljaCBTSEEtMjU2
IGlzIHVuYWNjZXB0YWJsZS4gwqBTdWdnZXN0IGFkZGluZw0KPiBoYXNoIGFsZ29yaXRobXMgdG8g
dGhlIEVDREggYWxnb3JpdGhtIGlkZW50aWZpZXJzLCBlLmcuLCAiRUNESDI1NiIsDQo+ICJFQ0RI
Mjg0K0tXIi4NCg0KIkVDREgyNTYiLCAiRUNESDI1NitBMTI4S1ciLCAiRUNESDM4NCIsICJFQ0gz
ODQrQTE5MktXIj8JDQoNCj4gMi4gVGhlICItRVMiIGlzIHVubmVjZXNzYXJ5LCBzaW5jZSB0aGUg
ZW50cm9weSBhZGRlZCBpbiBlbnRpdHlVSW5mbyBpcw0KPiBzdWZmaWNpZW50IHRvIGFkZHJlc3Mg
Ym90aCBFUyBhbmQgU1MgY2FzZXMuDQoNCg0KLS0NCkphbWVzIE1hbmdlcg0K

From rlb@ipv.sx  Thu Jun 20 19:49:11 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B8321E80F3 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 19:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.37
X-Spam-Level: *
X-Spam-Status: No, score=1.37 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LRpWzacV82Y8 for <jose@ietfa.amsl.com>; Thu, 20 Jun 2013 19:48:59 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7F16921E80DF for <jose@ietf.org>; Thu, 20 Jun 2013 19:48:58 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so8671640oag.4 for <jose@ietf.org>; Thu, 20 Jun 2013 19:48:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=kIbl5eAQYlJKXnwzmrvt7Nwttpjp9Kn39GaVEvq+5eE=; b=hSNKdvh7WfsW/gB1mV02lztcg6tVgMLT+1Z+WXdS0Sc1KsLa0LysxG7fmaGhUWyO0O u4YbR+gEbZw/hDHGDHMCSYh6eSeCeipWmRzKqt1yMONQLSYBMWIx7k/UCfJhYRxGXqOY BG69pK+Mhy0ZlfHQZTs8InWszpd/mF4sBAM5DPbPq1AAnoTLthVWZnjB6uEVQqI9uJHg XC/pbCxFw6QsE+XBOFsX7stx92wGJQMAmtGoXIER1b+sWPlZ889/xvoYcDVF4YD1t/QX iACAG6CV8w1+7rcPUNvg2t6WcBASwUL8WZP63PW+nNuuKOlbWp55mZkmTts8H7XZjPkn z8Bw==
MIME-Version: 1.0
X-Received: by 10.60.144.233 with SMTP id sp9mr5636991oeb.53.1371782938286; Thu, 20 Jun 2013 19:48:58 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 20 Jun 2013 19:48:58 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <05ca01ce6e1e$a663ddc0$f32b9940$@augustcellars.com>
References: <05ca01ce6e1e$a663ddc0$f32b9940$@augustcellars.com>
Date: Thu, 20 Jun 2013 22:48:58 -0400
Message-ID: <CAL02cgRS_v1rrj8Xs6bYFg5OHjKG1Gq0rc4xcoMED9j-3aTjHQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=047d7b3a8b66bef02f04dfa11a67
X-Gm-Message-State: ALoCoQnaH+Mu3tVJVCFHpbslNTcPpv4xGW35JfJeaYVyzHH7h13TOuz43+pUreXOPiQRgpj1N4hQ
Cc: "draft-ietf-jose-json-web-encryption@tools.ietf.org" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Keys in the documents
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 02:49:11 -0000

--047d7b3a8b66bef02f04dfa11a67
Content-Type: text/plain; charset=ISO-8859-1

+1

On Thursday, June 20, 2013, Jim Schaad wrote:

> Is there any reason not to provide the public and private keys in the
> appendixes as JWK objects?  This would make them easier to understand and
> put them into a format that one expects to be understood by JOSE systems.*
> ***
>
> ** **
>
> Jim****
>
> ** **
>

--047d7b3a8b66bef02f04dfa11a67
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1<span></span><br><br>On Thursday, June 20, 2013, Jim Schaad  wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"pur=
ple"><div>
<p class=3D"MsoNormal">Is there any reason not to provide the public and pr=
ivate keys in the appendixes as JWK objects? =A0This would make them easier=
 to understand and put them into a format that one expects to be understood=
 by JOSE systems.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoNormal">Jim<u></=
u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></bloc=
kquote>

--047d7b3a8b66bef02f04dfa11a67--

From mamille2@cisco.com  Fri Jun 21 06:05:36 2013
Return-Path: <mamille2@cisco.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210C821E8121 for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 06:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVl2LqCh81Fl for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 06:05:30 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4264421E811F for <jose@ietf.org>; Fri, 21 Jun 2013 06:05:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6559; q=dns/txt; s=iport; t=1371819930; x=1373029530; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=39hRFmS/LjBGVfnGVZ09uKgQXBgRrEgj7Hfotm/AXRY=; b=GNVr8p39/vb8N46paBX8GlfgkkewKR3dr0VsVRgGU/30MfUK7mWkL0bL 692l7m67j5271Yc5hOa5rYbvnOunW6GgXZ9wUDOjsVcu9bg6GjXRtGRzT 3buyvAx0TU2iNN++F3PFXDUIvxw6ce2yL1QcfNJEt7byv/+8qsdi2RZSc 8=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAA9PxFGtJXG9/2dsb2JhbABbgwl6gjy8eIECFnSCIwEBAQR5EAIBCA4KCiQCMCUBAQQOBQgGiAC8aI8YMQeDAGEDkAOBLJdYgw+CKA
X-IronPort-AV: E=Sophos;i="4.87,913,1363132800";  d="p7s'?scan'208";a="222811940"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 21 Jun 2013 13:05:26 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5LD5PnA031236 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Jun 2013 13:05:25 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Fri, 21 Jun 2013 08:05:25 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Keys in the documents
Thread-Index: Ac5uHoEIhUHF1bDIRb+g9Dwvv0NexQANUhUAABWHfoA=
Date: Fri, 21 Jun 2013 13:05:25 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411528E965@xmb-aln-x11.cisco.com>
References: <05ca01ce6e1e$a663ddc0$f32b9940$@augustcellars.com> <CAL02cgRS_v1rrj8Xs6bYFg5OHjKG1Gq0rc4xcoMED9j-3aTjHQ@mail.gmail.com>
In-Reply-To: <CAL02cgRS_v1rrj8Xs6bYFg5OHjKG1Gq0rc4xcoMED9j-3aTjHQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.129.24.59]
Content-Type: multipart/signed; boundary="Apple-Mail=_D601E30C-59A3-454F-A38F-4281A6F21AB8"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "draft-ietf-jose-json-web-encryption@tools.ietf.org" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Keys in the documents
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 13:05:36 -0000

--Apple-Mail=_D601E30C-59A3-454F-A38F-4281A6F21AB8
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1

+1

On Jun 20, 2013, at 8:48 PM, Richard Barnes <rlb@ipv.sx>
 wrote:

> +1
> 
> On Thursday, June 20, 2013, Jim Schaad wrote:
> 
>> Is there any reason not to provide the public and private keys in the
>> appendixes as JWK objects?  This would make them easier to understand and
>> put them into a format that one expects to be understood by JOSE systems.*
>> ***
>> 
>> ** **
>> 
>> Jim****
>> 
>> ** **
>> 

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.


--Apple-Mail=_D601E30C-59A3-454F-A38F-4281A6F21AB8
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMezCCBjQw
ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX
DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK
75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC
+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD
z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr
/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc
fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG
XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt
UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R
HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv
sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq
+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT
zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq
Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1
9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGPzCCBSeg
AwIBAgIDBoRIMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD
b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN
MTMwNDMwMjE1NDQyWhcNMTQwNTAyMDUzOTA0WjBbMRkwFwYDVQQNExBiN2F6NndOY0t0R3JtMEpF
MRswGQYDVQQDDBJtYW1pbGxlMkBjaXNjby5jb20xITAfBgkqhkiG9w0BCQEWEm1hbWlsbGUyQGNp
c2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJbKBMsG+9UFTx9uq/bhhXgu
vJvO8z7cwKaqqwZhVf5z/kHFyCNijtmTOE+YXjA8mWR4aoBwB5SvGypI/cJUofJ+AlBTC4g+RMx/
K0Ab4/jQqTQz9CDzMOB+Wm+rt8ZJ7A8ZzOJmNDAsf/VvB8l2A1SQz1UsAixgH16NTr8SlblAXEKk
4hwpCudUiNjjQokqJ0H686UBKVorcZSgXaza8XMqGtJF/8mNhR9GQYi7Xht1ky+9LFOrto2daZto
KJRwMeVusVdHUeKEQSu7jztw8HchH3KEb7Q+r5X+hhDZoddfKE8d5eyPuhiZdrzv7OlNZ0fSLdx7
3AE3nx9/R5YlXucCAwEAAaOCAtgwggLUMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQW
MBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUxGd+/qrdVudHrIKkw5xOMY7eaLUwHwYD
VR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWFtaWxsZTJAY2lzY28u
Y29tMIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9m
IHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBw
dXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYG
A1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4G
CCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2Vy
dHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRz
c2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAlDhXbGEI7lbqUcu5r2JHZaMsbRZda/99ZqODzWGX
0llou9jGccsAWDPPwRRe2+ROpXfH4cuJZElTcLDeZSp/qpXKhjYieFSX8+Ml9sKEj5UOSqQLyoLk
PtrIJV12Jk3nuG2Jc0UeEnGwK/aqtzy7+bfEVI0ziyVM2gChHh0RH74KyiwYWknbOTRIkZcz/ulE
DVFQp63uj6wfmDNvAUHBAdhKVqA1S/rfP1KcDZpf1NfvwXJibiqTRA6K1EOxTJOP41n/XdvHqHXL
RWL2xrOUI9/URANr/ok3OrsuZEMFnAAGefS1bWS/hFtUGVkHGiKEBbyDW7da2ULXbuC7umrQnzGC
A28wggNrAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDAJBgUrDgMCGgUA
oIIBrzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MjExMzA1
MjZaMCMGCSqGSIb3DQEJBDEWBBQQcAQHHMkq880OvUgHjlpVAnHfOzCBpQYJKwYBBAGCNxAEMYGX
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3Mg
MSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwaESDCBpwYLKoZIhvcNAQkQAgsxgZeg
gZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx
IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBoRIMA0GCSqGSIb3DQEBAQUABIIBADbN
OcFsAh+k4Iby4LvKPVQPonDHcZ2PCsbNl12h2/WA81d0TMqtuS4Lz75UBcIR2KX3IJON/ZRdLWlT
OO9lyfNQJ1Ruo39WMeNapiGK8u3RsM0ZhXDMstz/N/Nt7h2wBoUa1pvNfjG8kSyg9QyBLLviwnhX
lfVwWUNrIzbrulAzOvKbRQVbyeAHk/IHSfriraQIqkd1rSWDIMasZs3VyS3exuuPQhrBFbm8sxjU
MGPW8I+PdRlfsHtTAIYER67V3lcjJQbC9tSiDGjQXV5LgaC+qu7H7Rn2C4UOcBbQOO4Fd9asCINf
QiPn7O93HMwlq0lnAf4WiV6L1zAt/D+H2NYAAAAAAAA=

--Apple-Mail=_D601E30C-59A3-454F-A38F-4281A6F21AB8--

From Michael.Jones@microsoft.com  Fri Jun 21 08:58:42 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D18F21E8130 for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 08:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vE71aNbp9-xM for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 08:58:36 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 4E29B21E812F for <jose@ietf.org>; Fri, 21 Jun 2013 08:58:33 -0700 (PDT)
Received: from BL2FFO11FD019.protection.gbl (10.173.161.203) by BL2FFO11HUB036.protection.gbl (10.173.161.116) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 21 Jun 2013 15:58:26 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD019.mail.protection.outlook.com (10.173.161.37) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 21 Jun 2013 15:58:25 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Fri, 21 Jun 2013 15:57:57 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Keys in the documents
Thread-Index: Ac5umBcQhUHF1bDIRb+g9Dwvv0NexQ==
Content-Class: urn:content-classes:message
Date: Fri, 21 Jun 2013 15:57:57 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436787EB2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436787EB2ATK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(479174003)(199002)(189002)(51704005)(24454002)(63696002)(44976004)(79102001)(16236675002)(74366001)(31966008)(47446002)(16406001)(512934002)(74502001)(6806003)(74662001)(20776003)(46102001)(51856001)(33656001)(49866001)(59766001)(77982001)(47976001)(76786001)(80022001)(56816003)(47736001)(76796001)(54356001)(50986001)(55846006)(56776001)(53806001)(81542001)(69226001)(54316002)(4396001)(76176001)(74706001)(81342001)(65816001)(71186001)(74876001)(76482001)(77096001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB036; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0884AAA693
Cc: "draft-ietf-jose-json-web-encryption@tools.ietf.org" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Keys in the documents
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 15:58:42 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436787EB2ATK5EX14MBXC283r_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Will do.

________________________________
From: Matt Miller (mamille2)
Sent: 6/21/2013 6:06 AM
To: Richard Barnes
Cc: Jim Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org; jose@ie=
tf.org
Subject: Re: [jose] Keys in the documents

+1

On Jun 20, 2013, at 8:48 PM, Richard Barnes <rlb@ipv.sx>
wrote:

> +1
>
> On Thursday, June 20, 2013, Jim Schaad wrote:
>
>> Is there any reason not to provide the public and private keys in the
>> appendixes as JWK objects?  This would make them easier to understand an=
d
>> put them into a format that one expects to be understood by JOSE systems=
.*
>> ***
>>
>> ** **
>>
>> Jim****
>>
>> ** **
>>

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.


--_000_4E1F6AAD24975D4BA5B16804296739436787EB2ATK5EX14MBXC283r_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <AF8ED36AC3BB9A4698FC7FF9282E2F86@microsoft.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<div>
<div style=3D"font-family: Calibri,sans-serif; font-size: 11pt;">Will do.<b=
r>
<br>
</div>
</div>
<hr>
<span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-weight=
: bold;">From:
</span><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">Mat=
t Miller (mamille2)</span><br>
<span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-weight=
: bold;">Sent:
</span><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">6/2=
1/2013 6:06 AM</span><br>
<span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-weight=
: bold;">To:
</span><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">Ric=
hard Barnes</span><br>
<span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-weight=
: bold;">Cc:
</span><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">Jim=
 Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org; jose@ietf.org<=
/span><br>
<span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-weight=
: bold;">Subject:
</span><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">Re:=
 [jose] Keys in the documents</span><br>
<br>
&#43;1<br>
<br>
On Jun 20, 2013, at 8:48 PM, Richard Barnes &lt;rlb@ipv.sx&gt;<br>
wrote:<br>
<br>
&gt; &#43;1<br>
&gt; <br>
&gt; On Thursday, June 20, 2013, Jim Schaad wrote:<br>
&gt; <br>
&gt;&gt; Is there any reason not to provide the public and private keys in =
the<br>
&gt;&gt; appendixes as JWK objects?&nbsp; This would make them easier to un=
derstand and<br>
&gt;&gt; put them into a format that one expects to be understood by JOSE s=
ystems.*<br>
&gt;&gt; ***<br>
&gt;&gt; <br>
&gt;&gt; ** **<br>
&gt;&gt; <br>
&gt;&gt; Jim****<br>
&gt;&gt; <br>
&gt;&gt; ** **<br>
&gt;&gt; <br>
<br>
- m&amp;m<br>
<br>
Matt Miller &lt; mamille2@cisco.com &gt;<br>
Cisco Systems, Inc.<br>
<br>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436787EB2ATK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Fri Jun 21 16:37:12 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D6321F9DF0 for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 16:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.18
X-Spam-Level: 
X-Spam-Status: No, score=-3.18 tagged_above=-999 required=5 tests=[AWL=0.819,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_17=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wn8+vY3vyl9k for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 16:37:07 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) by ietfa.amsl.com (Postfix) with ESMTP id 80A9021F9B8E for <jose@ietf.org>; Fri, 21 Jun 2013 16:37:07 -0700 (PDT)
Received: from BN1AFFO11FD027.protection.gbl (10.58.52.203) by BN1AFFO11HUB034.protection.gbl (10.58.52.145) with Microsoft SMTP Server (TLS) id 15.0.707.0; Fri, 21 Jun 2013 23:22:02 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD027.mail.protection.outlook.com (10.58.52.87) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 21 Jun 2013 23:22:01 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Fri, 21 Jun 2013 23:21:58 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkg
Date: Fri, 21 Jun 2013 23:21:58 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.74]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51444003)(51704005)(51694002)(13464003)(51914003)(377454003)(23676002)(6806003)(74662001)(66066001)(74706001)(63696002)(33656001)(47776003)(76786001)(16406001)(76796001)(561944002)(74876001)(69226001)(20776003)(65816001)(81542001)(551934002)(53806001)(76482001)(51856001)(77096001)(47736001)(54316002)(79102001)(50466002)(46102001)(77982001)(56816003)(47976001)(47446002)(50986001)(74502001)(4396001)(56776001)(31966008)(49866001)(55846006)(59766001)(74366001)(81342001)(15202345003)(80022001)(54356001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB034; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0884AAA693
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 21 Jun 2013 23:37:13 -0000

VGhhbmtzIGZvciB0aGUgc3VnZ2VzdGlvbiBvZiB1c2luZyB0aGUgUkZDIDUwMDggS0RGLiAgSSBk
aWQgc29tZSByZXNlYXJjaCBpbnRvIHRoaXMsIGhvcGluZyB0byBmaW5kIHRoYXQgaXQgd2FzIGVx
dWl2YWxlbnQgdG8gdGhlIENvbmNhdCBLREYgd2l0aCBhIHN1aXRhYmxlIE90aGVySW5mbyB2YWx1
ZSwgYW5kIHVuZm9ydHVuYXRlbHksIGZvdW5kIHRoYXQgdGhlIHR3byBhcmUgaW5jb21wYXRpYmxl
LiAgVGhlIHJlYXNvbiB0aGV5J3JlIGluY29tcGF0aWJsZSBpcyB0aGF0IFJGQyA1MDA4IGNvbXB1
dGVzIHRoaXMgaGFzaDoNCglLTSA9IEhhc2ggKCBaIHx8IENvdW50ZXIgfHwgRUNDLUNNUy1TaGFy
ZWRJbmZvICkNCndoZXJlYXMgQ29uY2F0IGNvbXB1dGVzIHRoaXMgaGFzaDoNCglLKGkpID0gSChj
b3VudGVyIHx8IFogfHwgT3RoZXJJbmZvKQ0KDQpJZiB0aGUgb3JkZXIgb2YgImNvdW50ZXIiIGFu
ZCAiWiIgd2VyZSB0aGlzIHNhbWUsIGFuIGltcGxlbWVudGF0aW9uIG9mIENvbmNhdCBjb3VsZCBi
ZSB1c2VkIHRvIGRvIHRoZSBSRkMgNTAwOCBjb21wdXRhdGlvbiwgYnV0IGJlY2F1c2UgdGhlIG9y
ZGVyIGlzIGRpZmZlcmVudCwgdW5mb3J0dW5hdGVseSBpdCBjYW4ndC4NCg0KVGhlIHJlYXNvbiB0
aGF0IHRoaXMgbWF0dGVycyBpcyB3ZSBuZWVkIHRvIHVzZSBhIHdpZGVseS1zdXBwb3J0ZWQgS0RG
IHRvIGFjaGlldmUgdGhlIEpPU0UgZGVwbG95YWJpbGl0eSBhbmQgaW50ZXJvcGVyYWJpbGl0eSBn
b2Fscy4gIFdoZW4gdGhlIG9yaWdpbmFsIGNob2ljZSB3YXMgbWFkZSB0byB1c2UgQ29uY2F0LCBp
dCB3YXMgYmFzZWQgdXBvbiBsb29raW5nIGludG8gd2hhdCBLREZzIHdlcmUgYWxyZWFkeSB3aWRl
bHkgc3VwcG9ydGVkIGluIGxpYnJhcmllcywgYW5kIENvbmNhdCBsb29rZWQgbGlrZSB0aGUgYmVz
dCBjaG9pY2UuDQoNClVzaW5nIFdpbmRvd3MgYXMgYW4gZXhhbXBsZSwgaWYgeW91IGxvb2sgYXQg
dGhlIEJDcnlwdERlcml2ZUtleSBmdW5jdGlvbiBhdCBodHRwOi8vbXNkbi5taWNyb3NvZnQuY29t
L2VuLXVzL2xpYnJhcnkvd2luZG93cy9kZXNrdG9wL2FhMzc1MzkzKHY9dnMuODUpLmFzcHgsIHlv
dSdsbCBzZWUgdGhhdCBCQ1JZUFRfS0RGX1NQODAwNTZBX0NPTkNBVCBpcyBvbmUgb2YgdGhlIHN1
cHBvcnRlZCBLREYgZnVuY3Rpb25zIGJ1dCB0aGF0IHRoZSBSRkMgNTAwOCBmdW5jdGlvbiBpc24n
dC4gIChZZXMsIGZvciBrZXkgbGVuZ3RocyBvbmx5IHJlcXVpcmluZyBhIHNpbmdsZSBoYXMgY29t
cHV0YXRpb24sIHlvdSBjb3VsZCBwcm9iYWJseSBmYWtlIGl0IHdpdGggQkNSWVBUX0tERl9IQVNI
LCBidXQgdGhpcyB3b3VsZG4ndCB3b3JrIGZvciBrZXkgbGVuZ3RocyByZXF1aXJpbmcgbXVsdGlw
bGUgaGFzaCBjb21wdXRhdGlvbnMuKSAgVGhlIHNhbWUgcHJvYmxlbSBpcyBsaWtlbHkgdG8gYXBw
ZWFyIG9uIG90aGVyIHBsYXRmb3Jtcy4NCg0KVXNpbmcgWE1MIEVuY3J5cHRpb24gYXMgYSBsaXRt
dXMgdGVzdCBmb3Igd2hhdCBLREYgYWxnb3JpdGhtcyBhcmUgbGlrZWx5IHRvIGJlIHdpZGVseSBz
dXBwb3J0ZWQgZ2l2ZXMgdGhlIHNhbWUgY29uY2x1c2lvbiAtIGh0dHA6Ly93d3cudzMub3JnL1RS
L3htbGVuYy1jb3JlMS8jc2VjLUFsZy1LZXlEZXJpdmF0aW9uIGRlc2NyaWJlcyBzdXBwb3J0IG9u
bHkgZm9yIENvbmNhdCBhbmQgUEJLREYyLg0KDQpUaHVzLCB3aGlsZSBJIGFwcHJlY2lhdGUgdGhl
IHN1Z2dlc3Rpb24sIGFuZCBJIGRpZCBzZXJpb3VzbHkgaW52ZXN0aWdhdGUgaXQsIEkgZG9uJ3Qg
dGhpbmsgaXQncyBwcmFjdGljYWwgdG8gbW92ZSBhd2F5IGZyb20gdXNpbmcgdGhlIFNQIDgwMC01
NkEgQ29uY2F0IEtERi4gIFRoYXQgdGhlbiBlc3RhYmxpc2hlZCwgSSB0aGluayB0aGF0IHRoZSB0
YXNrIHRoZW4gYmVmb3JlIHVzIGlzIHRvIGRlY2lkZSBleGFjdGx5IGhvdyB0byB1c2UgaXQuICBU
aGF0IHdpbGwgYmUgdGhlIHN1YmplY3Qgb2YgYSBzdWJzZXF1ZW50IG1lc3NhZ2UuDQoNCgkJCQkt
LSBNaWtlDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBqb3NlLWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYW5n
ZXIsIEphbWVzIEgNClNlbnQ6IFRodXJzZGF5LCBKdW5lIDIwLCAyMDEzIDY6NTAgUE0NClRvOiBS
aWNoYXJkIEJhcm5lczsgSmltIFNjaGFhZA0KQ2M6IGpvc2VAaWV0Zi5vcmcNClN1YmplY3Q6IFJl
OiBbam9zZV0gQ29uY2F0IEtERg0KDQo+IFBhcnR5VUluZm8gc2VlbXMgY29tcGxpYW50IHdpdGgg
dGhlIGxldHRlciBvZiB0aGUgU1A4MDAtNTZBLiDCoA0KPiBTUDgwMC01NkEgZG9lc24ndCBwbGFj
ZSBhbnkgY29uc3RyYWludHMgb24gdGhlIGZvcm0gb3IgZHVyYXRpb24gb2YgdGhlIA0KPiBpZGVu
dGlmaWVyIElEX1UsIHNvIHRoZSA1MTItYml0IHZhbHVlIHByb3ZpZGVkIHNlZW1zIHN1ZmZpY2ll
bnQgaWYgeW91IA0KPiByZWdhcmQgdGhhdCBhcyBJRF9VLg0KDQpPbmUgYXNwZWN0IHRoYXQgaGFz
IGJlZW4gY29uZnVzaW5nIG1lIGlzIHdoZXRoZXIgdGhlIHJlY2lwaWVudCBpcyBleHBlY3RlZCB0
byByZWNvZ25pemUgSURfVSBhcyBhIGtub3duIGlkZW50aWZpZXIgZm9yIHRoZSBvcmlnaW5hdG9y
LCBhbmQgSURfViBhcyBpdHMgb3duIG5hbWU/DQoNCkFsdGVybmF0aXZlbHksIGRvIHJlcXVpcmVt
ZW50cyBvbiB0aGVzZSBpdGVtcyBvbmx5IGFwcGx5IHRvIHRoZSBvcmlnaW5hdG9yPyBJcyBpdCBj
b21wbGV0ZWx5IHNhZmUgZm9yIGEgcmVjaXBpZW50IHRvIHRyZWF0IElEX1UgYW5kIElEX1YgYXMg
b3BhcXVlIGJ5dGVzIHRvIGJlIGhhc2hlZCBhcyBwYXJ0IG9mIHRoZSBLREYsIGJ1dCB3aXRoIG5v
IG90aGVyIHByb2Nlc3Npbmc/IElzIGl0LCBpbiBmYWN0LCBzYWZlIGZvciBhIHJlY2lwaWVudCB0
byB0cmVhdCBPdGhlckluZm8gKEFsZ29yaXRobUlEICsgUGFydHlVSW5mbyArLi4uKSBhcyBhbiBv
cGFxdWUgYmxvYiwgb3IgZXZlbiBPdGhlcklucHV0IChrZXlkYXRhbGVuICsgT3RoZXJJbmZvKSBh
cyBhbiBvcGFxdWUgYmxvYj8gSW4gd2hpY2ggY2FzZSwgd2UgY291bGQgc2ltcGx5IGluY2x1ZGUg
QjY0KE90aGVySW5wdXQpIGluIGEgSk9TRSBtZXNzYWdlLCBwZXJoYXBzIHdpdGggYSBzdWdnZXN0
ZWQgd2F5IGFuIG9yaWdpbmF0b3IgY291bGQgY29uc3RydWN0IE90aGVySW5wdXQgKGVnIGZyb20g
YWxnLCBlbmMsIGtpZC9qa3UsIG5vbmNlKS4NCg0KDQo+IFRoZSBiZXR0ZXIgb3B0aW9uIHdvdWxk
IGJlIHRvIHVzZSB0aGUgc2FtZSBLREYgdGhhdCBDTVMgdXNlcyANCj4gW1JGQzMyNzhdW1NFQzFd
LiDCoEl0J3Mgc2ltcGxlciwgYW5kIGFsc28gY29tcGxpZXMgd2l0aCBVU0cgbWFuZGF0ZXMgDQo+
IChTdWl0ZSBCIFtSRkM1MDA4XSkuIMKgSWYgd2UgdXNlIHRoZSBSRkMgNTAwOCB2YXJpYW50LCBp
dCBhbHNvIHRha2VzIGFzIA0KPiBpbnB1dCBleGFjdGx5IHdoYXQgdGhlIGN1cnJlbnQgSldTIHNw
ZWMgcHJvdmlkZXM6DQo+IA0KPiBLTSA9IEhhc2ggKCBaIHx8IENvdW50ZXIgfHwgRUNDLUNNUy1T
aGFyZWRJbmZvICkNCj4gDQo+IEVDQy1DTVMtU2hhcmVkSW5mbyA9IHsNCj4gwqAgwqAga2V5SW5m
bywgLy8gVGhlIGFsZ29yaXRobSB3aXRoIHdoaWNoIHRoZSBrZXkgd2lsbCBiZSB1c2VkLCANCj4g
Y3VycmVudGx5IGluIEFsZ29yaXRobUlEDQo+IMKgIMKgIGVudGl0eVVJbmZvLCAvLyBUaGUgZW50
cm9weSBzb3VyY2Ugd2UncmUgY3VycmVudGx5IHB1dHRpbmcgaW4gDQo+IFBhcnR5VUluZm8NCj4g
wqAgwqAgc3VwcFB1YkluZm8gLy8gVGhlIGRlcml2ZWQga2V5IGxlbmd0aCwgY3VycmVudGx5IGlu
wqBTdXBwUHViSW5mbyB9DQo+IA0KPiBJbiBvdGhlciB3b3JkcywgQ01TIGRvZXMgZXhhY3RseSB3
aGF0IEpXUyB3YW50cyB0byBkbyBub3cuIMKgTGV0J3MganVzdCANCj4gZG8gaXQgZm9yIHJlYWwu
IMKgUHJvcG9zZWQgdGV4dCBmb3IgU2VjdGlvbiA0LjcuMSBvZiBKV0E6DQoNCllvdXIgcHJvcG9z
YWwgaXMgImxvZ2ljYWxseSIgdGhlIHNhbWUgYXMgQ01TIChzbyBzYW1lIHNlY3VyaXR5IHByb3Bl
cnRpZXMpLCBidXQgdGhlIHByZWNpc2UgY2FsY3VsYXRpb24gaXMgaW5jb21wYXRpYmxlIGFzIHlv
dSBkb24ndCB1c2UgYSBERVItZW5jb2Rpbmcgb2YgRUNDLUNNUy1TaGFyZWRJbmZvLiBKdXN0IHdh
bnRlZCB0byBjbGFyaWZ5IHRoaXMgaW50ZW50aW9uLg0KDQo+ICIiIg0KPiBUaGUga2V5IGRlcml2
YXRpb24gcHJvY2VzcyBkZXJpdmVzIHRoZSBhZ3JlZWQgdXBvbiBrZXkgZnJvbSB0aGUgc2hhcmVk
IA0KPiBzZWNyZXQgWiBlc3RhYmxpc2hlZCB0aHJvdWdoIHRoZSBFQ0RIIGFsZ29yaXRobSB1c2lu
ZyB0aGUgc2luZ2xlLXBhc3MgDQo+IEtERiBkZWZpbmVkIGluIFtTRUMxXS4gwqBUaGUgaW5wdXRz
IHRvIHRoZSBrZXkgZGVyaXZhdGlvbiBwcm9jZXNzIGFyZSANCj4gYXMNCj4gZm9sbG93czoNCj4g
DQo+IFogVGhpcyBpcyBzZXQgdG8gdGhlIHJlcHJlc2VudGF0aW9uIG9mIHRoZSBzaGFyZWQgc2Vj
cmV0IFogYXMgYW4gb2N0ZXQgDQo+IHNlcXVlbmNlLg0KPiANCj4gU2hhcmVkSW5mbyBUaGlzIGlz
IHNldCB0byB0aGUgY29uY2F0ZW5hdGlvbiBvZiB0aGUgZm9sbG93aW5nIG9jdGV0IA0KPiBzdHJp
bmdzLCBpbiBvcmRlcjoNCj4gwqAgwqAxLiBUaGUgYWxnb3JpdGhtIHdpdGggd2hpY2ggdGhlIGRl
cml2ZWQga2V5IGlzIHRvIGJlIHVzZWQuIMKgSWYgdGhlIA0KPiAiYWxnIiB2YWx1ZSBpcyAiRUNE
SCIsIHRoZW4gdGhpcyBmaWVsZCBjb250YWlucyB0aGUgdmFsdWUgb2YgdGhlICJhbGciDQo+IHBh
cmFtZXRlci4gwqBPdGhlcndpc2UsIGl0IGNvbnRhaW5zIHRoZSB2YWx1ZSBvZiB0aGUgImVuYyIg
cGFyYW1ldGVyLg0KDQpXcm9uZyB3YXkgYXJvdW5kLiBJZiAiYWxnIiBpcyAiRUNESCIgdXNlICJl
bmMiIHZhbHVlLCBvdGhlcndpc2UgdXNlICJhbGciIHZhbHVlLg0KDQpZb3UgYWxzbyBuZWVkIHRv
IHNlcGFyYXRlIHRoaXMgZmllbGQgZnJvbSB0aGUgbmV4dDogd2l0aCBhIGxlbmd0aCBwcmVmaXgs
IG9yIHNlcGFyYXRvciBjaGFyL2J5dGUuDQpXaXRoIDIgdmFyaWFibGUtc2l6ZWQgZmllbGRzIChh
bGdvcml0aG0gYW5kIGFwdSkgeW91IG9ubHkgdGhlb3JldGljYWxseSBuZWVkIDEgbGVuZ3RoIGZp
ZWxkIHRvIGJlIHVuYW1iaWd1b3VzLCBidXQgaXQgbmVlZHMgdG8gYmUgYXQgdGhlIHN0YXJ0IG9y
IGVuZCwgbm90IGluIGJldHdlZW4gdGhlIDIgZmllbGRzLg0KDQo+IMKgIMKgMi4gVGhlIGxlbmd0
aCBvZiB0aGUgdmFsdWUgb2YgdGhlICJhcHUiIHBhcmFtZXRlciwgYXMgYSAzMi1iaXQgYmlnIA0K
PiBlbmRpYW4gaW50ZWdlci4gwqBJZiB0aGUgImFwdSIgcGFyYW1ldGVyIGlzIG5vdCBwcmVzZW50
LCB0aGVuIHRoaXMgDQo+IGZpZWxkIGlzIHNldCB0byBhbGwgemVyb3MgKDB4MDAwMDAwMDApLg0K
PiDCoCDCoDMuIFRoZSB2YWx1ZSBvZiB0aGUgImFwdSIgcGFyYW1ldGVyLCBpZiBwcmVzZW50LiDC
oElmIHByb3ZpZGVkLCB0aGlzIA0KPiB2YWx1ZSBNVVNUIGNvbnRhaW4gYXQgbGVhc3QgNTEyIGJp
dHMgYW5kIGEgdW5pcXVlIHZhbHVlIFNIT1VMRCBiZSB1c2VkIA0KPiBmb3IgZWFjaCByZWNpcGll
bnQuIMKgVGhlICJhcHUiIHBhcmFtZXRlciBNQVkgYmUgb21pdHRlZCBvbmx5IGlmIGEgDQo+IGRp
ZmZlcmVudCBlcGhlbWVyYWwga2V5IGlzIHVzZWQgZm9yIGVhY2gga2V5IGFncmVlbWVudCB0cmFu
c2FjdGlvbi4NCj4gwqAgwqA0LiBUaGUgbGVuZ3RoIG9mIHRoZSBkZXJpdmVkIGtleSwgYXMgYSAz
Mi1iaXQgYmlnIGVuZGlhbiBpbnRlZ2VyLg0KPiDCoEZvciAiRUNESC1FUyIsIHRoaXMgaXMgbGVu
Z3RoIG9mIHRoZSBrZXkgdXNlZCBieSB0aGUgImVuYyIgYWxnb3JpdGhtLg0KPiDCoEZvciAiRUNE
SC1FUytBMTI4S1ciIG9yICJFQ0RILUVTK0EyNTZLVyIsIGl0IGlzIDEyOCAoMHgwMDAwMDA4MCkg
b3INCj4gMjU2ICgweDAwMDAwMTAwKSwgcmVzcGVjdGl2ZWx5Lg0KDQpTeW1tZXRyaWMga2V5IGxl
bmd0aHMgYXJlIGhhcmR3aXJlZCBpbnRvICJhbGciIGFuZCAiZW5jIiB2YWx1ZXMgaW4gSk9TRSAo
ZWcgIkEyNTZLVyIsICJBMTI4Q0dNIikgc28gd2UgZG9uJ3QgYWN0dWFsbHkgbmVlZCBhIHNlcGFy
YXRlIGZpZWxkLg0KDQo+ICIiIg0KPiANCj4gVHdvIHNpZGUgbm90ZXM6DQo+IDEuIFdlIG5lZWQg
aGFzaCBhZ2lsaXR5IGhlcmUgKGFzIGluIFJGQyA1MDA4KSB0byBiZSBhYmxlIHRvIG1lZXQgDQo+
IGhpZ2hlciBsZXZlbHMgb2Ygc2VjdXJpdHkgZm9yIHdoaWNoIFNIQS0yNTYgaXMgdW5hY2NlcHRh
YmxlLiDCoFN1Z2dlc3QgDQo+IGFkZGluZyBoYXNoIGFsZ29yaXRobXMgdG8gdGhlIEVDREggYWxn
b3JpdGhtIGlkZW50aWZpZXJzLCBlLmcuLCANCj4gIkVDREgyNTYiLCAiRUNESDI4NCtLVyIuDQoN
CiJFQ0RIMjU2IiwgIkVDREgyNTYrQTEyOEtXIiwgIkVDREgzODQiLCAiRUNIMzg0K0ExOTJLVyI/
CQ0KDQo+IDIuIFRoZSAiLUVTIiBpcyB1bm5lY2Vzc2FyeSwgc2luY2UgdGhlIGVudHJvcHkgYWRk
ZWQgaW4gZW50aXR5VUluZm8gaXMgDQo+IHN1ZmZpY2llbnQgdG8gYWRkcmVzcyBib3RoIEVTIGFu
ZCBTUyBjYXNlcy4NCg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0Kam9zZSBtYWlsaW5nIGxpc3QNCmpvc2VAaWV0Zi5v
cmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vam9zZQ0K

From Michael.Jones@microsoft.com  Fri Jun 21 17:46:57 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A47021F9B30 for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 17:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.204
X-Spam-Level: 
X-Spam-Status: No, score=-3.204 tagged_above=-999 required=5 tests=[AWL=0.794,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VabsyhAGYuSN for <jose@ietfa.amsl.com>; Fri, 21 Jun 2013 17:46:51 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7C81321F9A78 for <jose@ietf.org>; Fri, 21 Jun 2013 17:46:51 -0700 (PDT)
Received: from BN1AFFO11FD026.protection.gbl (10.58.52.200) by BN1BFFO11HUB029.protection.gbl (10.58.53.139) with Microsoft SMTP Server (TLS) id 15.0.707.0; Sat, 22 Jun 2013 00:46:48 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD026.mail.protection.outlook.com (10.58.52.86) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Sat, 22 Jun 2013 00:46:47 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Sat, 22 Jun 2013 00:45:55 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, Russ Housley <housley@vigilsec.com>,  "Manger, James H" <James.H.Manger@team.telstra.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkgAALrZmA=
Date: Sat, 22 Jun 2013 00:45:55 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.74]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367880BB1TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(51914003)(377454003)(189002)(51704005)(51694002)(51444003)(199002)(13464003)(74502001)(4396001)(53806001)(76796001)(56816003)(76482001)(55846006)(79102001)(54316002)(63696002)(51856001)(512874002)(6806003)(74366001)(81342001)(77096001)(15202345003)(47446002)(46102001)(49866001)(47736001)(47976001)(33656001)(54356001)(76786001)(20776003)(77982001)(50986001)(16236675002)(561944002)(19300405004)(59766001)(56776001)(81542001)(66066001)(69226001)(16406001)(74876001)(551934002)(74662001)(65816001)(31966008)(71186001)(80022001)(74706001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB029; H:TK5EX14HUBC106.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 088552DE73
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 00:46:57 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367880BB1TK5EX14MBXC283r_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBhZ3JlZSB3aXRoIEphbWVzJyBjb25jbHVzaW9uIHRoYXQgdGhlIC0xMSB1c2Ugb2YgdGhlIENv
bmNhdCBLREYgZG9lc24ndCBjb25mb3JtIHRvIFNQIDgwMC01NkEgYmVjYXVzZSBpdCBkb2Vzbid0
IHN1cHBvcnQgdGhlIFBhcnR5VkluZm8gcGFyYW1ldGVyLiAgSSBiZWxpZXZlIHRoYXQgRElTQ1VT
UyBjb21tZW50cyB3aWxsIHJlc3VsdCBpZiB3ZSBkb24ndCBlbmFibGUgY29uZm9ybWluZyB1c2Vz
IG9mIENvbmNhdC4gIFRoZXJlZm9yZSwgSSBwcm9wb3NlIHRvIG1ha2UgdGhlc2Ugc3BlY2lmaWMg
Y2hhbmdlcyByZWxhdGl2ZSB0byAtMTEuDQoNCg0KDQoxLiAgUmV2ZXJ0IHRoZSBQYXJ0eVVJbmZv
IGFuZCBQYXJ0eVZJbmZvIGxhbmd1YWdlIHRvIHRoZSAtMTAgdGV4dCwgd2hpY2ggd2FzOg0KUGFy
dHlVSW5mbw0KVGhlIFBhcnR5VUluZm8gdmFsdWUgaXMgb2YgdGhlIGZvcm0gRGF0YWxlbiB8fCBE
YXRhLCB3aGVyZSBEYXRhIGlzIGEgdmFyaWFibGUtbGVuZ3RoIHN0cmluZyBvZiB6ZXJvIG9yIG1v
cmUgb2N0ZXRzLCBhbmQgRGF0YWxlbiBpcyBhIGZpeGVkLWxlbmd0aCwgYmlnIGVuZGlhbiAzMiBi
aXQgY291bnRlciB0aGF0IGluZGljYXRlcyB0aGUgbGVuZ3RoIChpbiBvY3RldHMpIG9mIERhdGEs
IHdpdGggfHwgYmVpbmcgY29uY2F0ZW5hdGlvbi4gSWYgYW4gYXB1IChhZ3JlZW1lbnQgUGFydHlV
SW5mbykgaGVhZGVyIHBhcmFtZXRlciBpcyBwcmVzZW50LCBEYXRhIGlzIHNldCB0byB0aGUgcmVz
dWx0IG9mIGJhc2U2NHVybCBkZWNvZGluZyB0aGUgYXB1IHZhbHVlIGFuZCBEYXRhbGVuIGlzIHNl
dCB0byB0aGUgbnVtYmVyIG9mIG9jdGV0cyBpbiBEYXRhLiBPdGhlcndpc2UsIERhdGFsZW4gaXMg
c2V0IHRvIDAgYW5kIERhdGEgaXMgc2V0IHRvIHRoZSBlbXB0eSBvY3RldCBzZXF1ZW5jZS4NClBh
cnR5VkluZm8NClRoZSBQYXJ0eVZJbmZvIHZhbHVlIGlzIG9mIHRoZSBmb3JtIERhdGFsZW4gfHwg
RGF0YSwgd2hlcmUgRGF0YSBpcyBhIHZhcmlhYmxlLWxlbmd0aCBzdHJpbmcgb2YgemVybyBvciBt
b3JlIG9jdGV0cywgYW5kIERhdGFsZW4gaXMgYSBmaXhlZC1sZW5ndGgsIGJpZyBlbmRpYW4gMzIg
Yml0IGNvdW50ZXIgdGhhdCBpbmRpY2F0ZXMgdGhlIGxlbmd0aCAoaW4gb2N0ZXRzKSBvZiBEYXRh
LCB3aXRoIHx8IGJlaW5nIGNvbmNhdGVuYXRpb24uIElmIGFuIGFwdiAoYWdyZWVtZW50IFBhcnR5
VkluZm8pIGhlYWRlciBwYXJhbWV0ZXIgaXMgcHJlc2VudCwgRGF0YSBpcyBzZXQgdG8gdGhlIHJl
c3VsdCBvZiBiYXNlNjR1cmwgZGVjb2RpbmcgdGhlIGFwdiB2YWx1ZSBhbmQgRGF0YWxlbiBpcyBz
ZXQgdG8gdGhlIG51bWJlciBvZiBvY3RldHMgaW4gRGF0YS4gT3RoZXJ3aXNlLCBEYXRhbGVuIGlz
IHNldCB0byAwIGFuZCBEYXRhIGlzIHNldCB0byB0aGUgZW1wdHkgb2N0ZXQgc2VxdWVuY2UuDQoN
Cg0KDQoyLiAgQ2hhbmdlIHRoZSBBbGdvcml0aG1JRCBsYW5ndWFnZSB0bzoNCkFsZ29yaXRobUlE
DQpUaGlzIGlzIHNldCB0byB0aGUgb2N0ZXRzIG9mIHRoZSBVVEYtOCByZXByZXNlbnRhdGlvbiBv
ZiB0aGUgYWxnIGhlYWRlciBwYXJhbWV0ZXIgdmFsdWUgd2hlbiBpbiB0aGUgS2V5IEFncmVlbWVu
dCB3aXRoIEtleSBXcmFwcGluZyBtb2RlIGFuZCB0byB0aGUgb2N0ZXRzIG9mIHRoZSBVVEYtOCBy
ZXByZXNlbnRhdGlvbiBvZiB0aGUgZW5jIGhlYWRlciBwYXJhbWV0ZXIgdmFsdWUgd2hlbiBpbiB0
aGUgRGlyZWN0IEtleSBBZ3JlZW1lbnQgbW9kZS4NCg0KDQoNCjMuICBBdHRlbXB0aW5nIHRvIGFj
Y29tbW9kYXRlIHdoYXQgSSBiZWxpZXZlIGFyZSBKaW3igJlzIGFuZCBSaWNoYXJk4oCZcyBkZXNp
cmUgdG8gYWxpZ24gd2l0aCBDTVPigJlzIGtleSBkZXJpdmF0aW9uIHByYWN0aWNlcywgSSB3b3Vs
ZCBhZGQgdGhlIGZvbGxvd2luZyBwYXJhZ3JhcGg6DQoNCg0KVGhlIERpZmZpZS1IZWxsbWFuIEtl
eSBBZ3JlZW1lbnQgTWV0aG9kIFtSRkMgMjYzMV0gdXNlcyBhIGtleSBkZXJpdmF0aW9uIGZ1bmN0
aW9uIHNpbWlsYXIgdG8gdGhlIENvbmNhdCBLREYsIGJ1dCB3aXRoIGZld2VyIHBhcmFtZXRlcnMu
ICBSYXRoZXIgdGhhbiBoYXZpbmcgc2VwYXJhdGUgUGFydHlVSW5mbyBhbmQgUGFydHlWSW5mbyBw
YXJhbWV0ZXJzLCBpdCB1c2VzIGEgc2luZ2xlIFBhcnR5QUluZm8gcGFyYW1ldGVyLCB3aGljaCBp
cyBhIHJhbmRvbSBzdHJpbmcgcHJvdmlkZWQgYnkgdGhlIHNlbmRlciwgdGhhdCBjb250YWlucyA1
MTIgYml0cyBvZiBpbmZvcm1hdGlvbiwgd2hlbiBwcm92aWRlZC4gIEl0IGhhcyBubyBzdXBwUHJp
dkluZm8gcGFyYW1ldGVyLiAgS2V5IGFncmVlbWVudCBjYW4gYmUgcGVyZm9ybWVkIGluIGEgbWFu
bmVyIGFraW4gdG8gUkZDIDI2MzEgYnkgdXNpbmcgdGhlIFBhcnR5QUluZm8gdmFsdWUgYXMgdGhl
IOKAnGFwdeKAnSAoQWdyZWVtZW50IFBhcnR5VUluZm8pIGhlYWRlciBwYXJhbWV0ZXIgdmFsdWUs
IHdoZW4gcHJvdmlkZWQsIGFuZCBieSB1c2luZyBubyDigJxhcHbigJ0gKEFncmVlbWVudCBQYXJ0
eVZJbmZvKSBoZWFkZXIgcGFyYW1ldGVyLg0KDQoNCg0KV2lsbCB0aG9zZSBjaGFuZ2VzLCBjb2xs
ZWN0aXZlbHksIHNhdGlzZnkgYWxsIHRob3NlIHdobyBoYXZlIGJlZW4gY29tbWVudGluZyBvbiB0
aGlzIHRocmVhZD8gIElmIHRoZXkgd2lsbCBub3QsIHBsZWFzZSBzdXBwbHkgc3BlY2lmaWMgYWx0
ZXJuYXRpdmUgdGV4dC4gIEppbSwgUnVzcywgSmFtZXMsIGFuZCBSaWNoYXJkIOKAkyB3aGF0IHNh
eSB5ZT8NCg0KDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAtLSBNaWtlDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogam9zZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86am9zZS1ib3VuY2VzQGll
dGYub3JnXSBPbiBCZWhhbGYgT2YgTWlrZSBKb25lcw0KU2VudDogRnJpZGF5LCBKdW5lIDIxLCAy
MDEzIDQ6MjIgUE0NClRvOiBNYW5nZXIsIEphbWVzIEg7IFJpY2hhcmQgQmFybmVzOyBKaW0gU2No
YWFkDQpDYzogam9zZUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtqb3NlXSBDb25jYXQgS0RGDQoN
Cg0KDQpUaGFua3MgZm9yIHRoZSBzdWdnZXN0aW9uIG9mIHVzaW5nIHRoZSBSRkMgNTAwOCBLREYu
ICBJIGRpZCBzb21lIHJlc2VhcmNoIGludG8gdGhpcywgaG9waW5nIHRvIGZpbmQgdGhhdCBpdCB3
YXMgZXF1aXZhbGVudCB0byB0aGUgQ29uY2F0IEtERiB3aXRoIGEgc3VpdGFibGUgT3RoZXJJbmZv
IHZhbHVlLCBhbmQgdW5mb3J0dW5hdGVseSwgZm91bmQgdGhhdCB0aGUgdHdvIGFyZSBpbmNvbXBh
dGlibGUuICBUaGUgcmVhc29uIHRoZXkncmUgaW5jb21wYXRpYmxlIGlzIHRoYXQgUkZDIDUwMDgg
Y29tcHV0ZXMgdGhpcyBoYXNoOg0KDQogICAgICAgICAgICAgICAgS00gPSBIYXNoICggWiB8fCBD
b3VudGVyIHx8IEVDQy1DTVMtU2hhcmVkSW5mbyApIHdoZXJlYXMgQ29uY2F0IGNvbXB1dGVzIHRo
aXMgaGFzaDoNCg0KICAgICAgICAgICAgICAgIEsoaSkgPSBIKGNvdW50ZXIgfHwgWiB8fCBPdGhl
ckluZm8pDQoNCg0KDQpJZiB0aGUgb3JkZXIgb2YgImNvdW50ZXIiIGFuZCAiWiIgd2VyZSB0aGlz
IHNhbWUsIGFuIGltcGxlbWVudGF0aW9uIG9mIENvbmNhdCBjb3VsZCBiZSB1c2VkIHRvIGRvIHRo
ZSBSRkMgNTAwOCBjb21wdXRhdGlvbiwgYnV0IGJlY2F1c2UgdGhlIG9yZGVyIGlzIGRpZmZlcmVu
dCwgdW5mb3J0dW5hdGVseSBpdCBjYW4ndC4NCg0KDQoNClRoZSByZWFzb24gdGhhdCB0aGlzIG1h
dHRlcnMgaXMgd2UgbmVlZCB0byB1c2UgYSB3aWRlbHktc3VwcG9ydGVkIEtERiB0byBhY2hpZXZl
IHRoZSBKT1NFIGRlcGxveWFiaWxpdHkgYW5kIGludGVyb3BlcmFiaWxpdHkgZ29hbHMuICBXaGVu
IHRoZSBvcmlnaW5hbCBjaG9pY2Ugd2FzIG1hZGUgdG8gdXNlIENvbmNhdCwgaXQgd2FzIGJhc2Vk
IHVwb24gbG9va2luZyBpbnRvIHdoYXQgS0RGcyB3ZXJlIGFscmVhZHkgd2lkZWx5IHN1cHBvcnRl
ZCBpbiBsaWJyYXJpZXMsIGFuZCBDb25jYXQgbG9va2VkIGxpa2UgdGhlIGJlc3QgY2hvaWNlLg0K
DQoNCg0KVXNpbmcgV2luZG93cyBhcyBhbiBleGFtcGxlLCBpZiB5b3UgbG9vayBhdCB0aGUgQkNy
eXB0RGVyaXZlS2V5IGZ1bmN0aW9uIGF0IGh0dHA6Ly9tc2RuLm1pY3Jvc29mdC5jb20vZW4tdXMv
bGlicmFyeS93aW5kb3dzL2Rlc2t0b3AvYWEzNzUzOTModj12cy44NSkuYXNweCwgeW91J2xsIHNl
ZSB0aGF0IEJDUllQVF9LREZfU1A4MDA1NkFfQ09OQ0FUIGlzIG9uZSBvZiB0aGUgc3VwcG9ydGVk
IEtERiBmdW5jdGlvbnMgYnV0IHRoYXQgdGhlIFJGQyA1MDA4IGZ1bmN0aW9uIGlzbid0LiAgKFll
cywgZm9yIGtleSBsZW5ndGhzIG9ubHkgcmVxdWlyaW5nIGEgc2luZ2xlIGhhcyBjb21wdXRhdGlv
biwgeW91IGNvdWxkIHByb2JhYmx5IGZha2UgaXQgd2l0aCBCQ1JZUFRfS0RGX0hBU0gsIGJ1dCB0
aGlzIHdvdWxkbid0IHdvcmsgZm9yIGtleSBsZW5ndGhzIHJlcXVpcmluZyBtdWx0aXBsZSBoYXNo
IGNvbXB1dGF0aW9ucy4pICBUaGUgc2FtZSBwcm9ibGVtIGlzIGxpa2VseSB0byBhcHBlYXIgb24g
b3RoZXIgcGxhdGZvcm1zLg0KDQoNCg0KVXNpbmcgWE1MIEVuY3J5cHRpb24gYXMgYSBsaXRtdXMg
dGVzdCBmb3Igd2hhdCBLREYgYWxnb3JpdGhtcyBhcmUgbGlrZWx5IHRvIGJlIHdpZGVseSBzdXBw
b3J0ZWQgZ2l2ZXMgdGhlIHNhbWUgY29uY2x1c2lvbiAtIGh0dHA6Ly93d3cudzMub3JnL1RSL3ht
bGVuYy1jb3JlMS8jc2VjLUFsZy1LZXlEZXJpdmF0aW9uIGRlc2NyaWJlcyBzdXBwb3J0IG9ubHkg
Zm9yIENvbmNhdCBhbmQgUEJLREYyLg0KDQoNCg0KVGh1cywgd2hpbGUgSSBhcHByZWNpYXRlIHRo
ZSBzdWdnZXN0aW9uLCBhbmQgSSBkaWQgc2VyaW91c2x5IGludmVzdGlnYXRlIGl0LCBJIGRvbid0
IHRoaW5rIGl0J3MgcHJhY3RpY2FsIHRvIG1vdmUgYXdheSBmcm9tIHVzaW5nIHRoZSBTUCA4MDAt
NTZBIENvbmNhdCBLREYuICBUaGF0IHRoZW4gZXN0YWJsaXNoZWQsIEkgdGhpbmsgdGhhdCB0aGUg
dGFzayB0aGVuIGJlZm9yZSB1cyBpcyB0byBkZWNpZGUgZXhhY3RseSBob3cgdG8gdXNlIGl0LiAg
VGhhdCB3aWxsIGJlIHRoZSBzdWJqZWN0IG9mIGEgc3Vic2VxdWVudCBtZXNzYWdlLg0KDQoNCg0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIC0tIE1pa2UNCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQoNCkZyb206
IGpvc2UtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86am9zZS1ib3VuY2VzQGlldGYub3JnPiBbbWFp
bHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1hbmdlciwgSmFtZXMgSA0K
DQpTZW50OiBUaHVyc2RheSwgSnVuZSAyMCwgMjAxMyA2OjUwIFBNDQoNClRvOiBSaWNoYXJkIEJh
cm5lczsgSmltIFNjaGFhZA0KDQpDYzogam9zZUBpZXRmLm9yZzxtYWlsdG86am9zZUBpZXRmLm9y
Zz4NCg0KU3ViamVjdDogUmU6IFtqb3NlXSBDb25jYXQgS0RGDQoNCg0KDQo+IFBhcnR5VUluZm8g
c2VlbXMgY29tcGxpYW50IHdpdGggdGhlIGxldHRlciBvZiB0aGUgU1A4MDAtNTZBLiBTUDgwMC01
NkENCg0KPiBkb2Vzbid0IHBsYWNlIGFueSBjb25zdHJhaW50cyBvbiB0aGUgZm9ybSBvciBkdXJh
dGlvbiBvZiB0aGUNCg0KPiBpZGVudGlmaWVyIElEX1UsIHNvIHRoZSA1MTItYml0IHZhbHVlIHBy
b3ZpZGVkIHNlZW1zIHN1ZmZpY2llbnQgaWYgeW91DQoNCj4gcmVnYXJkIHRoYXQgYXMgSURfVS4N
Cg0KDQoNCk9uZSBhc3BlY3QgdGhhdCBoYXMgYmVlbiBjb25mdXNpbmcgbWUgaXMgd2hldGhlciB0
aGUgcmVjaXBpZW50IGlzIGV4cGVjdGVkIHRvIHJlY29nbml6ZSBJRF9VIGFzIGEga25vd24gaWRl
bnRpZmllciBmb3IgdGhlIG9yaWdpbmF0b3IsIGFuZCBJRF9WIGFzIGl0cyBvd24gbmFtZT8NCg0K
DQoNCkFsdGVybmF0aXZlbHksIGRvIHJlcXVpcmVtZW50cyBvbiB0aGVzZSBpdGVtcyBvbmx5IGFw
cGx5IHRvIHRoZSBvcmlnaW5hdG9yPyBJcyBpdCBjb21wbGV0ZWx5IHNhZmUgZm9yIGEgcmVjaXBp
ZW50IHRvIHRyZWF0IElEX1UgYW5kIElEX1YgYXMgb3BhcXVlIGJ5dGVzIHRvIGJlIGhhc2hlZCBh
cyBwYXJ0IG9mIHRoZSBLREYsIGJ1dCB3aXRoIG5vIG90aGVyIHByb2Nlc3Npbmc/IElzIGl0LCBp
biBmYWN0LCBzYWZlIGZvciBhIHJlY2lwaWVudCB0byB0cmVhdCBPdGhlckluZm8gKEFsZ29yaXRo
bUlEICsgUGFydHlVSW5mbyArLi4uKSBhcyBhbiBvcGFxdWUgYmxvYiwgb3IgZXZlbiBPdGhlcklu
cHV0IChrZXlkYXRhbGVuICsgT3RoZXJJbmZvKSBhcyBhbiBvcGFxdWUgYmxvYj8gSW4gd2hpY2gg
Y2FzZSwgd2UgY291bGQgc2ltcGx5IGluY2x1ZGUgQjY0KE90aGVySW5wdXQpIGluIGEgSk9TRSBt
ZXNzYWdlLCBwZXJoYXBzIHdpdGggYSBzdWdnZXN0ZWQgd2F5IGFuIG9yaWdpbmF0b3IgY291bGQg
Y29uc3RydWN0IE90aGVySW5wdXQgKGVnIGZyb20gYWxnLCBlbmMsIGtpZC9qa3UsIG5vbmNlKS4N
Cg0KDQoNCg0KDQo+IFRoZSBiZXR0ZXIgb3B0aW9uIHdvdWxkIGJlIHRvIHVzZSB0aGUgc2FtZSBL
REYgdGhhdCBDTVMgdXNlcw0KDQo+IFtSRkMzMjc4XVtTRUMxXS4gIEl0J3Mgc2ltcGxlciwgYW5k
IGFsc28gY29tcGxpZXMgd2l0aCBVU0cgbWFuZGF0ZXMNCg0KPiAoU3VpdGUgQiBbUkZDNTAwOF0p
LiAgSWYgd2UgdXNlIHRoZSBSRkMgNTAwOCB2YXJpYW50LCBpdCBhbHNvIHRha2VzIGFzDQoNCj4g
aW5wdXQgZXhhY3RseSB3aGF0IHRoZSBjdXJyZW50IEpXUyBzcGVjIHByb3ZpZGVzOg0KDQo+DQoN
Cj4gS00gPSBIYXNoICggWiB8fCBDb3VudGVyIHx8IEVDQy1DTVMtU2hhcmVkSW5mbyApDQoNCj4N
Cg0KPiBFQ0MtQ01TLVNoYXJlZEluZm8gPSB7DQoNCj4gICAgIGtleUluZm8sIC8vIFRoZSBhbGdv
cml0aG0gd2l0aCB3aGljaCB0aGUga2V5IHdpbGwgYmUgdXNlZCwNCg0KPiBjdXJyZW50bHkgaW4g
QWxnb3JpdGhtSUQNCg0KPiAgICAgZW50aXR5VUluZm8sIC8vIFRoZSBlbnRyb3B5IHNvdXJjZSB3
ZSdyZSBjdXJyZW50bHkgcHV0dGluZyBpbg0KDQo+IFBhcnR5VUluZm8NCg0KPiAgICAgc3VwcFB1
YkluZm8gLy8gVGhlIGRlcml2ZWQga2V5IGxlbmd0aCwgY3VycmVudGx5IGluIFN1cHBQdWJJbmZv
IH0NCg0KPg0KDQo+IEluIG90aGVyIHdvcmRzLCBDTVMgZG9lcyBleGFjdGx5IHdoYXQgSldTIHdh
bnRzIHRvIGRvIG5vdy4gIExldCdzIGp1c3QNCg0KPiBkbyBpdCBmb3IgcmVhbC4gIFByb3Bvc2Vk
IHRleHQgZm9yIFNlY3Rpb24gNC43LjEgb2YgSldBOg0KDQoNCg0KWW91ciBwcm9wb3NhbCBpcyAi
bG9naWNhbGx5IiB0aGUgc2FtZSBhcyBDTVMgKHNvIHNhbWUgc2VjdXJpdHkgcHJvcGVydGllcyks
IGJ1dCB0aGUgcHJlY2lzZSBjYWxjdWxhdGlvbiBpcyBpbmNvbXBhdGlibGUgYXMgeW91IGRvbid0
IHVzZSBhIERFUi1lbmNvZGluZyBvZiBFQ0MtQ01TLVNoYXJlZEluZm8uIEp1c3Qgd2FudGVkIHRv
IGNsYXJpZnkgdGhpcyBpbnRlbnRpb24uDQoNCg0KDQo+ICIiIg0KDQo+IFRoZSBrZXkgZGVyaXZh
dGlvbiBwcm9jZXNzIGRlcml2ZXMgdGhlIGFncmVlZCB1cG9uIGtleSBmcm9tIHRoZSBzaGFyZWQN
Cg0KPiBzZWNyZXQgWiBlc3RhYmxpc2hlZCB0aHJvdWdoIHRoZSBFQ0RIIGFsZ29yaXRobSB1c2lu
ZyB0aGUgc2luZ2xlLXBhc3MNCg0KPiBLREYgZGVmaW5lZCBpbiBbU0VDMV0uICBUaGUgaW5wdXRz
IHRvIHRoZSBrZXkgZGVyaXZhdGlvbiBwcm9jZXNzIGFyZQ0KDQo+IGFzDQoNCj4gZm9sbG93czoN
Cg0KPg0KDQo+IFogVGhpcyBpcyBzZXQgdG8gdGhlIHJlcHJlc2VudGF0aW9uIG9mIHRoZSBzaGFy
ZWQgc2VjcmV0IFogYXMgYW4gb2N0ZXQNCg0KPiBzZXF1ZW5jZS4NCg0KPg0KDQo+IFNoYXJlZElu
Zm8gVGhpcyBpcyBzZXQgdG8gdGhlIGNvbmNhdGVuYXRpb24gb2YgdGhlIGZvbGxvd2luZyBvY3Rl
dA0KDQo+IHN0cmluZ3MsIGluIG9yZGVyOg0KDQo+ICAgIDEuIFRoZSBhbGdvcml0aG0gd2l0aCB3
aGljaCB0aGUgZGVyaXZlZCBrZXkgaXMgdG8gYmUgdXNlZC4gIElmIHRoZQ0KDQo+ICJhbGciIHZh
bHVlIGlzICJFQ0RIIiwgdGhlbiB0aGlzIGZpZWxkIGNvbnRhaW5zIHRoZSB2YWx1ZSBvZiB0aGUg
ImFsZyINCg0KPiBwYXJhbWV0ZXIuICBPdGhlcndpc2UsIGl0IGNvbnRhaW5zIHRoZSB2YWx1ZSBv
ZiB0aGUgImVuYyIgcGFyYW1ldGVyLg0KDQoNCg0KV3Jvbmcgd2F5IGFyb3VuZC4gSWYgImFsZyIg
aXMgIkVDREgiIHVzZSAiZW5jIiB2YWx1ZSwgb3RoZXJ3aXNlIHVzZSAiYWxnIiB2YWx1ZS4NCg0K
DQoNCllvdSBhbHNvIG5lZWQgdG8gc2VwYXJhdGUgdGhpcyBmaWVsZCBmcm9tIHRoZSBuZXh0OiB3
aXRoIGEgbGVuZ3RoIHByZWZpeCwgb3Igc2VwYXJhdG9yIGNoYXIvYnl0ZS4NCg0KV2l0aCAyIHZh
cmlhYmxlLXNpemVkIGZpZWxkcyAoYWxnb3JpdGhtIGFuZCBhcHUpIHlvdSBvbmx5IHRoZW9yZXRp
Y2FsbHkgbmVlZCAxIGxlbmd0aCBmaWVsZCB0byBiZSB1bmFtYmlndW91cywgYnV0IGl0IG5lZWRz
IHRvIGJlIGF0IHRoZSBzdGFydCBvciBlbmQsIG5vdCBpbiBiZXR3ZWVuIHRoZSAyIGZpZWxkcy4N
Cg0KDQoNCj4gICAgMi4gVGhlIGxlbmd0aCBvZiB0aGUgdmFsdWUgb2YgdGhlICJhcHUiIHBhcmFt
ZXRlciwgYXMgYSAzMi1iaXQgYmlnDQoNCj4gZW5kaWFuIGludGVnZXIuICBJZiB0aGUgImFwdSIg
cGFyYW1ldGVyIGlzIG5vdCBwcmVzZW50LCB0aGVuIHRoaXMNCg0KPiBmaWVsZCBpcyBzZXQgdG8g
YWxsIHplcm9zICgweDAwMDAwMDAwKS4NCg0KPiAgICAzLiBUaGUgdmFsdWUgb2YgdGhlICJhcHUi
IHBhcmFtZXRlciwgaWYgcHJlc2VudC4gIElmIHByb3ZpZGVkLCB0aGlzDQoNCj4gdmFsdWUgTVVT
VCBjb250YWluIGF0IGxlYXN0IDUxMiBiaXRzIGFuZCBhIHVuaXF1ZSB2YWx1ZSBTSE9VTEQgYmUg
dXNlZA0KDQo+IGZvciBlYWNoIHJlY2lwaWVudC4gIFRoZSAiYXB1IiBwYXJhbWV0ZXIgTUFZIGJl
IG9taXR0ZWQgb25seSBpZiBhDQoNCj4gZGlmZmVyZW50IGVwaGVtZXJhbCBrZXkgaXMgdXNlZCBm
b3IgZWFjaCBrZXkgYWdyZWVtZW50IHRyYW5zYWN0aW9uLg0KDQo+ICAgIDQuIFRoZSBsZW5ndGgg
b2YgdGhlIGRlcml2ZWQga2V5LCBhcyBhIDMyLWJpdCBiaWcgZW5kaWFuIGludGVnZXIuDQoNCj4g
IEZvciAiRUNESC1FUyIsIHRoaXMgaXMgbGVuZ3RoIG9mIHRoZSBrZXkgdXNlZCBieSB0aGUgImVu
YyIgYWxnb3JpdGhtLg0KDQo+ICBGb3IgIkVDREgtRVMrQTEyOEtXIiBvciAiRUNESC1FUytBMjU2
S1ciLCBpdCBpcyAxMjggKDB4MDAwMDAwODApIG9yDQoNCj4gMjU2ICgweDAwMDAwMTAwKSwgcmVz
cGVjdGl2ZWx5Lg0KDQoNCg0KU3ltbWV0cmljIGtleSBsZW5ndGhzIGFyZSBoYXJkd2lyZWQgaW50
byAiYWxnIiBhbmQgImVuYyIgdmFsdWVzIGluIEpPU0UgKGVnICJBMjU2S1ciLCAiQTEyOENHTSIp
IHNvIHdlIGRvbid0IGFjdHVhbGx5IG5lZWQgYSBzZXBhcmF0ZSBmaWVsZC4NCg0KDQoNCj4gIiIi
DQoNCj4NCg0KPiBUd28gc2lkZSBub3RlczoNCg0KPiAxLiBXZSBuZWVkIGhhc2ggYWdpbGl0eSBo
ZXJlIChhcyBpbiBSRkMgNTAwOCkgdG8gYmUgYWJsZSB0byBtZWV0DQoNCj4gaGlnaGVyIGxldmVs
cyBvZiBzZWN1cml0eSBmb3Igd2hpY2ggU0hBLTI1NiBpcyB1bmFjY2VwdGFibGUuICBTdWdnZXN0
DQoNCj4gYWRkaW5nIGhhc2ggYWxnb3JpdGhtcyB0byB0aGUgRUNESCBhbGdvcml0aG0gaWRlbnRp
ZmllcnMsIGUuZy4sDQoNCj4gIkVDREgyNTYiLCAiRUNESDI4NCtLVyIuDQoNCg0KDQoiRUNESDI1
NiIsICJFQ0RIMjU2K0ExMjhLVyIsICJFQ0RIMzg0IiwgIkVDSDM4NCtBMTkyS1ciPw0KDQoNCg0K
PiAyLiBUaGUgIi1FUyIgaXMgdW5uZWNlc3NhcnksIHNpbmNlIHRoZSBlbnRyb3B5IGFkZGVkIGlu
IGVudGl0eVVJbmZvIGlzDQoNCj4gc3VmZmljaWVudCB0byBhZGRyZXNzIGJvdGggRVMgYW5kIFNT
IGNhc2VzLg0KDQoNCg0KDQoNCi0tDQoNCkphbWVzIE1hbmdlcg0KDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpqb3NlIG1haWxpbmcgbGlzdA0KDQpq
b3NlQGlldGYub3JnPG1haWx0bzpqb3NlQGlldGYub3JnPg0KDQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2pvc2UNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCg0Kam9zZSBtYWlsaW5nIGxpc3QNCg0Kam9zZUBpZXRmLm9yZzxt
YWlsdG86am9zZUBpZXRmLm9yZz4NCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9qb3NlDQo=

--_000_4E1F6AAD24975D4BA5B168042967394367880BB1TK5EX14MBXC283r_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZlcmRhbmE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1
IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29O
b3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAx
cHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQs
IHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNv
bG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0
LCBsaS5Nc29QbGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQp0dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgljb2xvcjojMDAzMzY2O30NCnAuTXNvQWNldGF0
ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCglt
YXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJU
YWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5h
bWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHls
ZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi
O30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQg
Q2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29u
IFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkkgYWdyZWUgd2l0aCBKYW1l
cycgY29uY2x1c2lvbiB0aGF0IHRoZSAtMTEgdXNlIG9mIHRoZSBDb25jYXQgS0RGIGRvZXNuJ3Qg
Y29uZm9ybSB0byBTUCA4MDAtNTZBIGJlY2F1c2UgaXQgZG9lc24ndCBzdXBwb3J0IHRoZSBQYXJ0
eVZJbmZvIHBhcmFtZXRlci4mbmJzcDsgSSBiZWxpZXZlIHRoYXQgRElTQ1VTUyBjb21tZW50cyB3
aWxsIHJlc3VsdCBpZiB3ZSBkb24ndCBlbmFibGUgY29uZm9ybWluZyB1c2VzIG9mIENvbmNhdC4m
bmJzcDsNCiBUaGVyZWZvcmUsIEkgcHJvcG9zZSB0byBtYWtlIHRoZXNlIHNwZWNpZmljIGNoYW5n
ZXMgcmVsYXRpdmUgdG8gLTExLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4xLiZuYnNw
OyBSZXZlcnQgdGhlIFBhcnR5VUluZm8gYW5kIFBhcnR5VkluZm8gbGFuZ3VhZ2UgdG8gdGhlIC0x
MCB0ZXh0LCB3aGljaCB3YXM6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gbGFuZz0iRU4iIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2si
PlBhcnR5VUluZm88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWxlZnQ6OTYuMHB0Ij48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+VGhlIFBhcnR5VUluZm8gdmFsdWUgaXMgb2YgdGhlIGZvcm0gRGF0YWxlbiB8fCBEYXRhLCB3
aGVyZSBEYXRhIGlzIGEgdmFyaWFibGUtbGVuZ3RoIHN0cmluZyBvZiB6ZXJvIG9yIG1vcmUgb2N0
ZXRzLCBhbmQgRGF0YWxlbiBpcyBhIGZpeGVkLWxlbmd0aCwNCiBiaWcgZW5kaWFuIDMyIGJpdCBj
b3VudGVyIHRoYXQgaW5kaWNhdGVzIHRoZSBsZW5ndGggKGluIG9jdGV0cykgb2YgRGF0YSwgd2l0
aCB8fCBiZWluZyBjb25jYXRlbmF0aW9uLiBJZiBhbg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOIiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6IzAwMzM2NiI+
YXB1PC9zcGFuPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFu
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4gKGFncmVlbWVudCBQ
YXJ0eVVJbmZvKSBoZWFkZXIgcGFyYW1ldGVyIGlzIHByZXNlbnQsIERhdGEgaXMgc2V0IHRvIHRo
ZSByZXN1bHQgb2YgYmFzZTY0dXJsIGRlY29kaW5nIHRoZQ0KPC9zcGFuPjxzcGFuIGxhbmc9IkVO
IiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6IzAwMzM2
NiI+YXB1PC9zcGFuPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVy
ZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj4gdmFsdWUgYW5k
IERhdGFsZW4gaXMgc2V0IHRvIHRoZSBudW1iZXIgb2Ygb2N0ZXRzIGluIERhdGEuIE90aGVyd2lz
ZSwgRGF0YWxlbiBpcyBzZXQgdG8gMCBhbmQgRGF0YSBpcyBzZXQNCiB0byB0aGUgZW1wdHkgb2N0
ZXQgc2VxdWVuY2UuIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+UGFydHlWSW5mbzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tbGVmdDo5Ni4wcHQiPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJs
YWNrIj5UaGUgUGFydHlWSW5mbyB2YWx1ZSBpcyBvZiB0aGUgZm9ybSBEYXRhbGVuIHx8IERhdGEs
IHdoZXJlIERhdGEgaXMgYSB2YXJpYWJsZS1sZW5ndGggc3RyaW5nIG9mIHplcm8gb3IgbW9yZSBv
Y3RldHMsIGFuZCBEYXRhbGVuIGlzIGEgZml4ZWQtbGVuZ3RoLA0KIGJpZyBlbmRpYW4gMzIgYml0
IGNvdW50ZXIgdGhhdCBpbmRpY2F0ZXMgdGhlIGxlbmd0aCAoaW4gb2N0ZXRzKSBvZiBEYXRhLCB3
aXRoIHx8IGJlaW5nIGNvbmNhdGVuYXRpb24uIElmIGFuDQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4i
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMDAzMzY2
Ij5hcHY8L3NwYW4+PHNwYW4gbGFuZz0iRU4iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJk
YW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPiAoYWdyZWVtZW50
IFBhcnR5VkluZm8pIGhlYWRlciBwYXJhbWV0ZXIgaXMgcHJlc2VudCwgRGF0YSBpcyBzZXQgdG8g
dGhlIHJlc3VsdCBvZiBiYXNlNjR1cmwgZGVjb2RpbmcgdGhlDQo8L3NwYW4+PHNwYW4gbGFuZz0i
RU4iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMDAz
MzY2Ij5hcHY8L3NwYW4+PHNwYW4gbGFuZz0iRU4iIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtW
ZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPiB2YWx1ZSBh
bmQgRGF0YWxlbiBpcyBzZXQgdG8gdGhlIG51bWJlciBvZiBvY3RldHMgaW4gRGF0YS4gT3RoZXJ3
aXNlLCBEYXRhbGVuIGlzIHNldCB0byAwIGFuZCBEYXRhIGlzIHNldA0KIHRvIHRoZSBlbXB0eSBv
Y3RldCBzZXF1ZW5jZS4gPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4yLiZu
YnNwOyBDaGFuZ2UgdGhlIEFsZ29yaXRobUlEIGxhbmd1YWdlIHRvOjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxzcGFuIGxhbmc9
IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5BbGdvcml0aG1JRDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDo5Ni4wcHQiPjxzcGFuIGxh
bmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGlzIGlzIHNldCB0byB0aGUgb2N0ZXRzIG9mIHRo
ZSBVVEYtOCByZXByZXNlbnRhdGlvbiBvZiB0aGUNCjwvc3Bhbj48c3BhbiBsYW5nPSJFTiIgc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMwMDMzNjYiPmFs
Zzwvc3Bhbj48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+IGhlYWRlciBwYXJhbWV0
ZXIgdmFsdWUgd2hlbg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5p
biB0aGUgS2V5IEFncmVlbWVudCB3aXRoIEtleSBXcmFwcGluZyBtb2RlIGFuZA0KPC9zcGFuPjxz
cGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj50byB0aGUgb2N0ZXRzIG9mIHRoZSBVVEYt
OCByZXByZXNlbnRhdGlvbiBvZiB0aGUNCjwvc3Bhbj48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMwMDMzNjYiPmVuYzwvc3Bh
bj48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjpibGFjayI+IGhlYWRlciBwYXJhbWV0ZXIgdmFs
dWUgd2hlbg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5pbiB0aGUg
RGlyZWN0IEtleSBBZ3JlZW1lbnQgbW9kZTwvc3Bhbj48c3BhbiBsYW5nPSJFTiIgc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjpibGFjayI+LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+My4mbmJzcDsg
QXR0ZW1wdGluZyB0byBhY2NvbW1vZGF0ZSB3aGF0IEkgYmVsaWV2ZSBhcmUgSmlt4oCZcyBhbmQg
UmljaGFyZOKAmXMgZGVzaXJlIHRvIGFsaWduIHdpdGggQ01T4oCZcyBrZXkgZGVyaXZhdGlvbiBw
cmFjdGljZXMsIEkgd291bGQgYWRkIHRoZSBmb2xsb3dpbmcgcGFyYWdyYXBoOjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PHNwYW4gbGFuZz0iRU4i
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6YmxhY2siPlRoZSBEaWZmaWUtSGVsbG1hbiBLZXkgQWdyZWVtZW50IE1ldGhv
ZCBbUkZDIDI2MzFdIHVzZXMgYSBrZXkgZGVyaXZhdGlvbiBmdW5jdGlvbiBzaW1pbGFyIHRvIHRo
ZSBDb25jYXQgS0RGLCBidXQgd2l0aCBmZXdlciBwYXJhbWV0ZXJzLiZuYnNwOyBSYXRoZXINCiB0
aGFuIGhhdmluZyBzZXBhcmF0ZSBQYXJ0eVVJbmZvIGFuZCBQYXJ0eVZJbmZvIHBhcmFtZXRlcnMs
IGl0IHVzZXMgYSBzaW5nbGUgUGFydHlBSW5mbyBwYXJhbWV0ZXIsIHdoaWNoIGlzIGEgcmFuZG9t
IHN0cmluZyBwcm92aWRlZCBieSB0aGUgc2VuZGVyLCB0aGF0IGNvbnRhaW5zIDUxMiBiaXRzIG9m
IGluZm9ybWF0aW9uLCB3aGVuIHByb3ZpZGVkLiZuYnNwOyBJdCBoYXMgbm8gc3VwcFByaXZJbmZv
IHBhcmFtZXRlci4mbmJzcDsgS2V5IGFncmVlbWVudCBjYW4gYmUNCiBwZXJmb3JtZWQgaW4gYSBt
YW5uZXIgYWtpbiB0byBSRkMgMjYzMSBieSB1c2luZyB0aGUgUGFydHlBSW5mbyB2YWx1ZSBhcyB0
aGUg4oCcYXB14oCdIChBZ3JlZW1lbnQgUGFydHlVSW5mbykgaGVhZGVyIHBhcmFtZXRlciB2YWx1
ZSwgd2hlbiBwcm92aWRlZCwgYW5kIGJ5IHVzaW5nIG5vIOKAnGFwduKAnSAoQWdyZWVtZW50IFBh
cnR5VkluZm8pIGhlYWRlciBwYXJhbWV0ZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5XaWxsIHRob3NlIGNoYW5nZXMsIGNvbGxlY3RpdmVseSwgc2F0aXNmeSBhbGwgdGhv
c2Ugd2hvIGhhdmUgYmVlbiBjb21tZW50aW5nIG9uIHRoaXMgdGhyZWFkPyZuYnNwOyBJZiB0aGV5
IHdpbGwgbm90LCBwbGVhc2Ugc3VwcGx5IHNwZWNpZmljIGFsdGVybmF0aXZlIHRleHQuJm5ic3A7
DQo8c3BhbiBzdHlsZT0iY29sb3I6cmVkIj5KaW0sIFJ1c3MsIEphbWVzLCBhbmQgUmljaGFyZDwv
c3Bhbj4g4oCTIHdoYXQgc2F5IHllPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLS0gTWlrZTxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IGpvc2Ut
Ym91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxm
IE9mIE1pa2UgSm9uZXM8YnI+DQpTZW50OiBGcmlkYXksIEp1bmUgMjEsIDIwMTMgNDoyMiBQTTxi
cj4NClRvOiBNYW5nZXIsIEphbWVzIEg7IFJpY2hhcmQgQmFybmVzOyBKaW0gU2NoYWFkPGJyPg0K
Q2M6IGpvc2VAaWV0Zi5vcmc8YnI+DQpTdWJqZWN0OiBSZTogW2pvc2VdIENvbmNhdCBLREY8L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPlRoYW5rcyBmb3IgdGhlIHN1Z2dlc3Rpb24gb2YgdXNpbmcgdGhlIFJG
QyA1MDA4IEtERi4mbmJzcDsgSSBkaWQgc29tZSByZXNlYXJjaCBpbnRvIHRoaXMsIGhvcGluZyB0
byBmaW5kIHRoYXQgaXQgd2FzIGVxdWl2YWxlbnQgdG8gdGhlIENvbmNhdCBLREYgd2l0aCBhIHN1
aXRhYmxlIE90aGVySW5mbyB2YWx1ZSwgYW5kIHVuZm9ydHVuYXRlbHksIGZvdW5kIHRoYXQgdGhl
IHR3byBhcmUgaW5jb21wYXRpYmxlLiZuYnNwOyBUaGUNCiByZWFzb24gdGhleSdyZSBpbmNvbXBh
dGlibGUgaXMgdGhhdCBSRkMgNTAwOCBjb21wdXRlcyB0aGlzIGhhc2g6PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgS00gPSBIYXNoICggWiB8fCBDb3VudGVyIHx8IEVDQy1DTVMtU2hhcmVkSW5mbyApIHdoZXJl
YXMgQ29uY2F0IGNvbXB1dGVzIHRoaXMgaGFzaDo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBLKGkpID0gSChj
b3VudGVyIHx8IFogfHwgT3RoZXJJbmZvKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5J
ZiB0aGUgb3JkZXIgb2YgJnF1b3Q7Y291bnRlciZxdW90OyBhbmQgJnF1b3Q7WiZxdW90OyB3ZXJl
IHRoaXMgc2FtZSwgYW4gaW1wbGVtZW50YXRpb24gb2YgQ29uY2F0IGNvdWxkIGJlIHVzZWQgdG8g
ZG8gdGhlIFJGQyA1MDA4IGNvbXB1dGF0aW9uLCBidXQgYmVjYXVzZSB0aGUgb3JkZXIgaXMgZGlm
ZmVyZW50LCB1bmZvcnR1bmF0ZWx5IGl0IGNhbid0LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij5UaGUgcmVhc29uIHRoYXQgdGhpcyBtYXR0ZXJzIGlzIHdlIG5lZWQgdG8gdXNlIGEgd2lk
ZWx5LXN1cHBvcnRlZCBLREYgdG8gYWNoaWV2ZSB0aGUgSk9TRSBkZXBsb3lhYmlsaXR5IGFuZCBp
bnRlcm9wZXJhYmlsaXR5IGdvYWxzLiZuYnNwOyBXaGVuIHRoZSBvcmlnaW5hbCBjaG9pY2Ugd2Fz
IG1hZGUgdG8gdXNlIENvbmNhdCwgaXQgd2FzIGJhc2VkIHVwb24gbG9va2luZyBpbnRvIHdoYXQg
S0RGcyB3ZXJlIGFscmVhZHkNCiB3aWRlbHkgc3VwcG9ydGVkIGluIGxpYnJhcmllcywgYW5kIENv
bmNhdCBsb29rZWQgbGlrZSB0aGUgYmVzdCBjaG9pY2UuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPlVzaW5nIFdpbmRvd3MgYXMgYW4gZXhhbXBsZSwgaWYgeW91IGxvb2sgYXQgdGhlIEJD
cnlwdERlcml2ZUtleSBmdW5jdGlvbiBhdA0KPGEgaHJlZj0iaHR0cDovL21zZG4ubWljcm9zb2Z0
LmNvbS9lbi11cy9saWJyYXJ5L3dpbmRvd3MvZGVza3RvcC9hYTM3NTM5Myh2PXZzLjg1KS5hc3B4
Ij4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5o
dHRwOi8vbXNkbi5taWNyb3NvZnQuY29tL2VuLXVzL2xpYnJhcnkvd2luZG93cy9kZXNrdG9wL2Fh
Mzc1MzkzKHY9dnMuODUpLmFzcHg8L3NwYW4+PC9hPiwgeW91J2xsIHNlZSB0aGF0IEJDUllQVF9L
REZfU1A4MDA1NkFfQ09OQ0FUIGlzIG9uZSBvZiB0aGUgc3VwcG9ydGVkIEtERiBmdW5jdGlvbnMg
YnV0IHRoYXQgdGhlIFJGQyA1MDA4IGZ1bmN0aW9uIGlzbid0LiZuYnNwOw0KIChZZXMsIGZvciBr
ZXkgbGVuZ3RocyBvbmx5IHJlcXVpcmluZyBhIHNpbmdsZSBoYXMgY29tcHV0YXRpb24sIHlvdSBj
b3VsZCBwcm9iYWJseSBmYWtlIGl0IHdpdGggQkNSWVBUX0tERl9IQVNILCBidXQgdGhpcyB3b3Vs
ZG4ndCB3b3JrIGZvciBrZXkgbGVuZ3RocyByZXF1aXJpbmcgbXVsdGlwbGUgaGFzaCBjb21wdXRh
dGlvbnMuKSZuYnNwOyBUaGUgc2FtZSBwcm9ibGVtIGlzIGxpa2VseSB0byBhcHBlYXIgb24gb3Ro
ZXIgcGxhdGZvcm1zLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5Vc2luZyBYTUwgRW5j
cnlwdGlvbiBhcyBhIGxpdG11cyB0ZXN0IGZvciB3aGF0IEtERiBhbGdvcml0aG1zIGFyZSBsaWtl
bHkgdG8gYmUgd2lkZWx5IHN1cHBvcnRlZCBnaXZlcyB0aGUgc2FtZSBjb25jbHVzaW9uIC0NCjxh
IGhyZWY9Imh0dHA6Ly93d3cudzMub3JnL1RSL3htbGVuYy1jb3JlMS8jc2VjLUFsZy1LZXlEZXJp
dmF0aW9uIj48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9u
ZSI+aHR0cDovL3d3dy53My5vcmcvVFIveG1sZW5jLWNvcmUxLyNzZWMtQWxnLUtleURlcml2YXRp
b248L3NwYW4+PC9hPiBkZXNjcmliZXMgc3VwcG9ydCBvbmx5IGZvciBDb25jYXQgYW5kIFBCS0RG
Mi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+VGh1cywgd2hpbGUgSSBhcHByZWNpYXRl
IHRoZSBzdWdnZXN0aW9uLCBhbmQgSSBkaWQgc2VyaW91c2x5IGludmVzdGlnYXRlIGl0LCBJIGRv
bid0IHRoaW5rIGl0J3MgcHJhY3RpY2FsIHRvIG1vdmUgYXdheSBmcm9tIHVzaW5nIHRoZSBTUCA4
MDAtNTZBIENvbmNhdCBLREYuJm5ic3A7IFRoYXQgdGhlbiBlc3RhYmxpc2hlZCwgSSB0aGluayB0
aGF0IHRoZSB0YXNrIHRoZW4gYmVmb3JlIHVzIGlzIHRvIGRlY2lkZSBleGFjdGx5DQogaG93IHRv
IHVzZSBpdC4mbmJzcDsgVGhhdCB3aWxsIGJlIHRoZSBzdWJqZWN0IG9mIGEgc3Vic2VxdWVudCBt
ZXNzYWdlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgLS0gTWlrZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+RnJvbTogPGEgaHJlZj0ibWFpbHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZyI+PHNw
YW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmpvc2UtYm91
bmNlc0BpZXRmLm9yZzwvc3Bhbj48L2E+IFs8YSBocmVmPSJtYWlsdG86am9zZS1ib3VuY2VzQGll
dGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9u
ZSI+bWFpbHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZzwvc3Bhbj48L2E+XQ0KIE9uIEJlaGFsZiBP
ZiBNYW5nZXIsIEphbWVzIEg8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PlNlbnQ6IFRodXJzZGF5LCBKdW5lIDIwLCAyMDEzIDY6NTAgUE08bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPlRvOiBSaWNoYXJkIEJhcm5lczsgSmltIFNjaGFhZDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Q2M6IDxhIGhyZWY9Im1haWx0bzpq
b3NlQGlldGYub3JnIj48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRp
b246bm9uZSI+am9zZUBpZXRmLm9yZzwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5TdWJqZWN0OiBSZTogW2pvc2VdIENvbmNhdCBLREY8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBQYXJ0eVVJbmZvIHNlZW1zIGNvbXBsaWFudCB3aXRo
IHRoZSBsZXR0ZXIgb2YgdGhlIFNQODAwLTU2QS4gU1A4MDAtNTZBDQo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgZG9lc24ndCBwbGFjZSBhbnkgY29uc3RyYWlu
dHMgb24gdGhlIGZvcm0gb3IgZHVyYXRpb24gb2YgdGhlDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZndDsgaWRlbnRpZmllciBJRF9VLCBzbyB0aGUgNTEyLWJpdCB2
YWx1ZSBwcm92aWRlZCBzZWVtcyBzdWZmaWNpZW50IGlmIHlvdQ0KPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IHJlZ2FyZCB0aGF0IGFzIElEX1UuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPk9uZSBhc3BlY3QgdGhhdCBoYXMgYmVlbiBjb25mdXNpbmcg
bWUgaXMgd2hldGhlciB0aGUgcmVjaXBpZW50IGlzIGV4cGVjdGVkIHRvIHJlY29nbml6ZSBJRF9V
IGFzIGEga25vd24gaWRlbnRpZmllciBmb3IgdGhlIG9yaWdpbmF0b3IsIGFuZCBJRF9WIGFzIGl0
cyBvd24gbmFtZT88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+QWx0ZXJuYXRpdmVseSwg
ZG8gcmVxdWlyZW1lbnRzIG9uIHRoZXNlIGl0ZW1zIG9ubHkgYXBwbHkgdG8gdGhlIG9yaWdpbmF0
b3I/IElzIGl0IGNvbXBsZXRlbHkgc2FmZSBmb3IgYSByZWNpcGllbnQgdG8gdHJlYXQgSURfVSBh
bmQgSURfViBhcyBvcGFxdWUgYnl0ZXMgdG8gYmUgaGFzaGVkIGFzIHBhcnQgb2YgdGhlIEtERiwg
YnV0IHdpdGggbm8gb3RoZXIgcHJvY2Vzc2luZz8gSXMgaXQsIGluIGZhY3QsIHNhZmUNCiBmb3Ig
YSByZWNpcGllbnQgdG8gdHJlYXQgT3RoZXJJbmZvIChBbGdvcml0aG1JRCAmIzQzOyBQYXJ0eVVJ
bmZvICYjNDM7Li4uKSBhcyBhbiBvcGFxdWUgYmxvYiwgb3IgZXZlbiBPdGhlcklucHV0IChrZXlk
YXRhbGVuICYjNDM7IE90aGVySW5mbykgYXMgYW4gb3BhcXVlIGJsb2I/IEluIHdoaWNoIGNhc2Us
IHdlIGNvdWxkIHNpbXBseSBpbmNsdWRlIEI2NChPdGhlcklucHV0KSBpbiBhIEpPU0UgbWVzc2Fn
ZSwgcGVyaGFwcyB3aXRoIGEgc3VnZ2VzdGVkIHdheSBhbiBvcmlnaW5hdG9yDQogY291bGQgY29u
c3RydWN0IE90aGVySW5wdXQgKGVnIGZyb20gYWxnLCBlbmMsIGtpZC9qa3UsIG5vbmNlKS48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IFRoZSBiZXR0ZXIgb3B0aW9uIHdvdWxkIGJlIHRvIHVzZSB0
aGUgc2FtZSBLREYgdGhhdCBDTVMgdXNlcw0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mZ3Q7IFtSRkMzMjc4XVtTRUMxXS4gJm5ic3A7SXQncyBzaW1wbGVyLCBhbmQg
YWxzbyBjb21wbGllcyB3aXRoIFVTRyBtYW5kYXRlcw0KPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IChTdWl0ZSBCIFtSRkM1MDA4XSkuICZuYnNwO0lmIHdlIHVz
ZSB0aGUgUkZDIDUwMDggdmFyaWFudCwgaXQgYWxzbyB0YWtlcyBhcw0KPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGlucHV0IGV4YWN0bHkgd2hhdCB0aGUgY3Vy
cmVudCBKV1Mgc3BlYyBwcm92aWRlczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZndDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7
IEtNID0gSGFzaCAoIFogfHwgQ291bnRlciB8fCBFQ0MtQ01TLVNoYXJlZEluZm8gKTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyA8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgRUNDLUNNUy1TaGFyZWRJbmZvID0gezxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyAmbmJzcDsgJm5ic3A7IGtleUlu
Zm8sIC8vIFRoZSBhbGdvcml0aG0gd2l0aCB3aGljaCB0aGUga2V5IHdpbGwgYmUgdXNlZCwNCjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBjdXJyZW50bHkgaW4g
QWxnb3JpdGhtSUQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsg
Jm5ic3A7ICZuYnNwOyBlbnRpdHlVSW5mbywgLy8gVGhlIGVudHJvcHkgc291cmNlIHdlJ3JlIGN1
cnJlbnRseSBwdXR0aW5nIGluDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPiZndDsgUGFydHlVSW5mbzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+Jmd0OyAmbmJzcDsgJm5ic3A7IHN1cHBQdWJJbmZvIC8vIFRoZSBkZXJpdmVkIGtleSBsZW5n
dGgsIGN1cnJlbnRseSBpbiZuYnNwO1N1cHBQdWJJbmZvIH08bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZndDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mZ3Q7IEluIG90aGVyIHdvcmRzLCBDTVMgZG9lcyBleGFjdGx5IHdoYXQgSldTIHdh
bnRzIHRvIGRvIG5vdy4gJm5ic3A7TGV0J3MganVzdA0KPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGRvIGl0IGZvciByZWFsLiAmbmJzcDtQcm9wb3NlZCB0ZXh0
IGZvciBTZWN0aW9uIDQuNy4xIG9mIEpXQTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
WW91ciBwcm9wb3NhbCBpcyAmcXVvdDtsb2dpY2FsbHkmcXVvdDsgdGhlIHNhbWUgYXMgQ01TIChz
byBzYW1lIHNlY3VyaXR5IHByb3BlcnRpZXMpLCBidXQgdGhlIHByZWNpc2UgY2FsY3VsYXRpb24g
aXMgaW5jb21wYXRpYmxlIGFzIHlvdSBkb24ndCB1c2UgYSBERVItZW5jb2Rpbmcgb2YgRUNDLUNN
Uy1TaGFyZWRJbmZvLiBKdXN0IHdhbnRlZCB0byBjbGFyaWZ5IHRoaXMgaW50ZW50aW9uLjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7ICZxdW90OyZxdW90OyZxdW90OzxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBUaGUga2V5IGRlcml2YXRpb24g
cHJvY2VzcyBkZXJpdmVzIHRoZSBhZ3JlZWQgdXBvbiBrZXkgZnJvbSB0aGUgc2hhcmVkDQo8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgc2VjcmV0IFogZXN0YWJs
aXNoZWQgdGhyb3VnaCB0aGUgRUNESCBhbGdvcml0aG0gdXNpbmcgdGhlIHNpbmdsZS1wYXNzDQo8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgS0RGIGRlZmluZWQg
aW4gW1NFQzFdLiAmbmJzcDtUaGUgaW5wdXRzIHRvIHRoZSBrZXkgZGVyaXZhdGlvbiBwcm9jZXNz
IGFyZQ0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGFzPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGZvbGxvd3M6PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBaIFRoaXMgaXMgc2V0IHRvIHRoZSByZXByZXNl
bnRhdGlvbiBvZiB0aGUgc2hhcmVkIHNlY3JldCBaIGFzIGFuIG9jdGV0DQo8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgc2VxdWVuY2UuPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyBTaGFyZWRJbmZvIFRoaXMgaXMgc2V0IHRvIHRoZSBjb25jYXRl
bmF0aW9uIG9mIHRoZSBmb2xsb3dpbmcgb2N0ZXQNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyBzdHJpbmdzLCBpbiBvcmRlcjo8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgJm5ic3A7ICZuYnNwOzEuIFRoZSBhbGdvcml0aG0g
d2l0aCB3aGljaCB0aGUgZGVyaXZlZCBrZXkgaXMgdG8gYmUgdXNlZC4gJm5ic3A7SWYgdGhlDQo8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgJnF1b3Q7YWxnJnF1
b3Q7IHZhbHVlIGlzICZxdW90O0VDREgmcXVvdDssIHRoZW4gdGhpcyBmaWVsZCBjb250YWlucyB0
aGUgdmFsdWUgb2YgdGhlICZxdW90O2FsZyZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyBwYXJhbWV0ZXIuICZuYnNwO090aGVyd2lzZSwgaXQgY29udGFp
bnMgdGhlIHZhbHVlIG9mIHRoZSAmcXVvdDtlbmMmcXVvdDsgcGFyYW1ldGVyLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij5Xcm9uZyB3YXkgYXJvdW5kLiBJZiAmcXVvdDthbGcmcXVvdDsg
aXMgJnF1b3Q7RUNESCZxdW90OyB1c2UgJnF1b3Q7ZW5jJnF1b3Q7IHZhbHVlLCBvdGhlcndpc2Ug
dXNlICZxdW90O2FsZyZxdW90OyB2YWx1ZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
WW91IGFsc28gbmVlZCB0byBzZXBhcmF0ZSB0aGlzIGZpZWxkIGZyb20gdGhlIG5leHQ6IHdpdGgg
YSBsZW5ndGggcHJlZml4LCBvciBzZXBhcmF0b3IgY2hhci9ieXRlLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+V2l0aCAyIHZhcmlhYmxlLXNpemVkIGZpZWxkcyAoYWxn
b3JpdGhtIGFuZCBhcHUpIHlvdSBvbmx5IHRoZW9yZXRpY2FsbHkgbmVlZCAxIGxlbmd0aCBmaWVs
ZCB0byBiZSB1bmFtYmlndW91cywgYnV0IGl0IG5lZWRzIHRvIGJlIGF0IHRoZSBzdGFydCBvciBl
bmQsIG5vdCBpbiBiZXR3ZWVuIHRoZSAyIGZpZWxkcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jmd0OyAmbmJzcDsgJm5ic3A7Mi4gVGhlIGxlbmd0aCBvZiB0aGUgdmFsdWUgb2YgdGhl
ICZxdW90O2FwdSZxdW90OyBwYXJhbWV0ZXIsIGFzIGEgMzItYml0IGJpZw0KPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGVuZGlhbiBpbnRlZ2VyLiAmbmJzcDtJ
ZiB0aGUgJnF1b3Q7YXB1JnF1b3Q7IHBhcmFtZXRlciBpcyBub3QgcHJlc2VudCwgdGhlbiB0aGlz
DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgZmllbGQgaXMg
c2V0IHRvIGFsbCB6ZXJvcyAoMHgwMDAwMDAwMCkuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mZ3Q7ICZuYnNwOyAmbmJzcDszLiBUaGUgdmFsdWUgb2YgdGhlICZxdW90
O2FwdSZxdW90OyBwYXJhbWV0ZXIsIGlmIHByZXNlbnQuICZuYnNwO0lmIHByb3ZpZGVkLCB0aGlz
DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgdmFsdWUgTVVT
VCBjb250YWluIGF0IGxlYXN0IDUxMiBiaXRzIGFuZCBhIHVuaXF1ZSB2YWx1ZSBTSE9VTEQgYmUg
dXNlZA0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IGZvciBl
YWNoIHJlY2lwaWVudC4gJm5ic3A7VGhlICZxdW90O2FwdSZxdW90OyBwYXJhbWV0ZXIgTUFZIGJl
IG9taXR0ZWQgb25seSBpZiBhDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPiZndDsgZGlmZmVyZW50IGVwaGVtZXJhbCBrZXkgaXMgdXNlZCBmb3IgZWFjaCBrZXkgYWdy
ZWVtZW50IHRyYW5zYWN0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+Jmd0OyAmbmJzcDsgJm5ic3A7NC4gVGhlIGxlbmd0aCBvZiB0aGUgZGVyaXZlZCBrZXksIGFz
IGEgMzItYml0IGJpZyBlbmRpYW4gaW50ZWdlci48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZndDsgJm5ic3A7Rm9yICZxdW90O0VDREgtRVMmcXVvdDssIHRoaXMgaXMg
bGVuZ3RoIG9mIHRoZSBrZXkgdXNlZCBieSB0aGUgJnF1b3Q7ZW5jJnF1b3Q7IGFsZ29yaXRobS48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgJm5ic3A7Rm9yICZx
dW90O0VDREgtRVMmIzQzO0ExMjhLVyZxdW90OyBvciAmcXVvdDtFQ0RILUVTJiM0MztBMjU2S1cm
cXVvdDssIGl0IGlzIDEyOCAoMHgwMDAwMDA4MCkgb3I8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZndDsgMjU2ICgweDAwMDAwMTAwKSwgcmVzcGVjdGl2ZWx5LjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5TeW1tZXRyaWMga2V5IGxlbmd0aHMgYXJlIGhhcmR3
aXJlZCBpbnRvICZxdW90O2FsZyZxdW90OyBhbmQgJnF1b3Q7ZW5jJnF1b3Q7IHZhbHVlcyBpbiBK
T1NFIChlZyAmcXVvdDtBMjU2S1cmcXVvdDssICZxdW90O0ExMjhDR00mcXVvdDspIHNvIHdlIGRv
bid0IGFjdHVhbGx5IG5lZWQgYSBzZXBhcmF0ZSBmaWVsZC48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jmd0OyAmcXVvdDsmcXVvdDsmcXVvdDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZndDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij4mZ3Q7IFR3byBzaWRlIG5vdGVzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jmd0OyAxLiBXZSBuZWVkIGhhc2ggYWdpbGl0eSBoZXJlIChhcyBpbiBSRkMgNTAw
OCkgdG8gYmUgYWJsZSB0byBtZWV0DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZndDsgaGlnaGVyIGxldmVscyBvZiBzZWN1cml0eSBmb3Igd2hpY2ggU0hBLTI1NiBp
cyB1bmFjY2VwdGFibGUuICZuYnNwO1N1Z2dlc3QNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jmd0OyBhZGRpbmcgaGFzaCBhbGdvcml0aG1zIHRvIHRoZSBFQ0RIIGFs
Z29yaXRobSBpZGVudGlmaWVycywgZS5nLiwNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jmd0OyAmcXVvdDtFQ0RIMjU2JnF1b3Q7LCAmcXVvdDtFQ0RIMjg0JiM0MztL
VyZxdW90Oy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+JnF1b3Q7RUNESDI1NiZxdW90
OywgJnF1b3Q7RUNESDI1NiYjNDM7QTEyOEtXJnF1b3Q7LCAmcXVvdDtFQ0RIMzg0JnF1b3Q7LCAm
cXVvdDtFQ0gzODQmIzQzO0ExOTJLVyZxdW90Oz8mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mZ3Q7IDIuIFRoZSAmcXVvdDstRVMmcXVvdDsgaXMgdW5uZWNlc3NhcnksIHNpbmNlIHRoZSBl
bnRyb3B5IGFkZGVkIGluIGVudGl0eVVJbmZvIGlzDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZndDsgc3VmZmljaWVudCB0byBhZGRyZXNzIGJvdGggRVMgYW5kIFNT
IGNhc2VzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPi0tPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij5KYW1lcyBNYW5nZXI8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5qb3NlIG1haWxpbmcgbGlz
dDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PGEgaHJlZj0ibWFpbHRv
Ompvc2VAaWV0Zi5vcmciPjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3Jh
dGlvbjpub25lIj5qb3NlQGlldGYub3JnPC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vam9zZSI+PHNwYW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0
aW9uOm5vbmUiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vam9zZTwvc3Bh
bj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+am9zZSBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxhIGhyZWY9Im1haWx0bzpqb3NlQGlldGYub3JnIj48c3Bh
biBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+am9zZUBpZXRm
Lm9yZzwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2pvc2UiPjxzcGFu
IHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5odHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2pvc2U8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_4E1F6AAD24975D4BA5B168042967394367880BB1TK5EX14MBXC283r_--

From rlb@ipv.sx  Sat Jun 22 12:26:58 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB9A421F9E7A for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 12:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Level: 
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[AWL=0.712,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUde177tNn+j for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 12:26:54 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A2C2D21F9E55 for <jose@ietf.org>; Sat, 22 Jun 2013 12:26:54 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so9513790obc.20 for <jose@ietf.org>; Sat, 22 Jun 2013 12:26:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=QFt5zxCCUVpTDtoW3aiEoQSoPkMp5ZZPL1YstI9nZn4=; b=Bvnf21c9dBiMYvWw2mhkJFzN12Soi5NsaHcJDg4QrEpufME2K7/Ylm3LukIg1KWGke +hd3YmC+nqGq7EIoNn5DcT9kQiy2ecO2g50cZPLLlMY1iLic/kG/ktC1ZEwI31iPVTvY ypkdfsYXo63wdNkHzta3Sa1mnwc07eedEYtveDfVT6DTg5tU5pwaR87jxpMx4156d4vr LKFb/5knMdsm96CJMZWhRVRROgcsTI9tAZLa83xK941kPfvstbkutGO0GEdHZeUHGvLD mgNusxuR/t0mUxlEymokOVxTlkFcBcXnGMELTFrS5l4o2YrTvKpiJrj7ltGm3j5C9dNL ECxg==
MIME-Version: 1.0
X-Received: by 10.60.144.233 with SMTP id sp9mr8553012oeb.53.1371929212884; Sat, 22 Jun 2013 12:26:52 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Sat, 22 Jun 2013 12:26:52 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sat, 22 Jun 2013 15:26:52 -0400
Message-ID: <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=047d7b3a8b66641d3204dfc329bb
X-Gm-Message-State: ALoCoQlPlt+V9GML4sYN/P4Ck76ecalK7qNCo6d2RO/KT4nB6vPwH9cU/XwIswzea1eq26POoO+G
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, Jim Schaad <ietf@augustcellars.com>, Russ Housley <housley@vigilsec.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 19:26:58 -0000

--047d7b3a8b66641d3204dfc329bb
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Don't think that quite answers the mail.  The algorithm text is correct.
 However, SP800-56A still says that both PartyUInfo and PartyVInfo MUST NOT
be empty.  So setting them to zero-length octet strings is non-compliant.
 There needs to be something there in any case.  And this still seems
abusive of SP800-56A.

I also think your assertion that Concat is a "widely supported KDF" is
rather thinly supported.  IIRC, your algorithm support spreadsheet from
earlier showed that BCryptDeriveKey was the *only* known implementation of
Concat.  StackOverflow seems to agree, and NIST has a special "800-56A
EXCEPT KDF" category because that's apparently what everything does.
<
http://stackoverflow.com/questions/10879658/existing-implementations-for-ni=
st-sp-800-56a-concatenation-key-derivation-functi
>
<http://csrc.nist.gov/groups/STM/cavp/documents/components/componentval.htm=
l
>

So I don't think support is really a reason to prefer Concat.  Pretty much
everyone is going to have to implement either KDF from scratch anyway
(using concatenation and a hash function), so we might as well choose one
that (1) has some history in the IETF (so there's at least some code in CMS
libraries), and (2) doesn't have to be used with inappropriate semantics.

--Richard







On Fri, Jun 21, 2013 at 8:45 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  I agree with James' conclusion that the -11 use of the Concat KDF
> doesn't conform to SP 800-56A because it doesn't support the PartyVInfo
> parameter.  I believe that DISCUSS comments will result if we don't enabl=
e
> conforming uses of Concat.  Therefore, I propose to make these specific
> changes relative to -11.****
>
> ** **
>
> 1.  Revert the PartyUInfo and PartyVInfo language to the -10 text, which
> was:****
>
> PartyUInfo****
>
> The PartyUInfo value is of the form Datalen || Data, where Data is a
> variable-length string of zero or more octets, and Datalen is a
> fixed-length, big endian 32 bit counter that indicates the length (in
> octets) of Data, with || being concatenation. If an apu (agreement
> PartyUInfo) header parameter is present, Data is set to the result of
> base64url decoding the apu value and Datalen is set to the number of
> octets in Data. Otherwise, Datalen is set to 0 and Data is set to the emp=
ty
> octet sequence. ****
>
> PartyVInfo****
>
> The PartyVInfo value is of the form Datalen || Data, where Data is a
> variable-length string of zero or more octets, and Datalen is a
> fixed-length, big endian 32 bit counter that indicates the length (in
> octets) of Data, with || being concatenation. If an apv (agreement
> PartyVInfo) header parameter is present, Data is set to the result of
> base64url decoding the apv value and Datalen is set to the number of
> octets in Data. Otherwise, Datalen is set to 0 and Data is set to the emp=
ty
> octet sequence. ****
>
> ** **
>
> 2.  Change the AlgorithmID language to:****
>
> AlgorithmID****
>
> This is set to the octets of the UTF-8 representation of the alg header
> parameter value when in the Key Agreement with Key Wrapping mode and to
> the octets of the UTF-8 representation of the enc header parameter value
> when in the Direct Key Agreement mode.****
>
> ** **
>
> 3.  Attempting to accommodate what I believe are Jim=92s and Richard=92s
> desire to align with CMS=92s key derivation practices, I would add the
> following paragraph:****
>
> ** **
>
> The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation
> function similar to the Concat KDF, but with fewer parameters.  Rather th=
an
> having separate PartyUInfo and PartyVInfo parameters, it uses a single
> PartyAInfo parameter, which is a random string provided by the sender, th=
at
> contains 512 bits of information, when provided.  It has no suppPrivInfo
> parameter.  Key agreement can be performed in a manner akin to RFC 2631 b=
y
> using the PartyAInfo value as the =93apu=94 (Agreement PartyUInfo) header
> parameter value, when provided, and by using no =93apv=94 (Agreement
> PartyVInfo) header parameter.****
>
> ** **
>
> Will those changes, collectively, satisfy all those who have been
> commenting on this thread?  If they will not, please supply specific
> alternative text.  Jim, Russ, James, and Richard =96 what say ye?****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> Mike Jones
> Sent: Friday, June 21, 2013 4:22 PM
> To: Manger, James H; Richard Barnes; Jim Schaad
> Cc: jose@ietf.org
> Subject: Re: [jose] Concat KDF
>
> ** **
>
> Thanks for the suggestion of using the RFC 5008 KDF.  I did some research
> into this, hoping to find that it was equivalent to the Concat KDF with a
> suitable OtherInfo value, and unfortunately, found that the two are
> incompatible.  The reason they're incompatible is that RFC 5008 computes
> this hash:****
>
>                 KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo ) wherea=
s
> Concat computes this hash:****
>
>                 K(i) =3D H(counter || Z || OtherInfo)****
>
> ** **
>
> If the order of "counter" and "Z" were this same, an implementation of
> Concat could be used to do the RFC 5008 computation, but because the orde=
r
> is different, unfortunately it can't.****
>
> ** **
>
> The reason that this matters is we need to use a widely-supported KDF to
> achieve the JOSE deployability and interoperability goals.  When the
> original choice was made to use Concat, it was based upon looking into wh=
at
> KDFs were already widely supported in libraries, and Concat looked like t=
he
> best choice.****
>
> ** **
>
> Using Windows as an example, if you look at the BCryptDeriveKey function
> at
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393(v=3Dvs.8=
5).aspx,
> you'll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported KDF
> functions but that the RFC 5008 function isn't.  (Yes, for key lengths on=
ly
> requiring a single has computation, you could probably fake it with
> BCRYPT_KDF_HASH, but this wouldn't work for key lengths requiring multipl=
e
> hash computations.)  The same problem is likely to appear on other
> platforms.****
>
> ** **
>
> Using XML Encryption as a litmus test for what KDF algorithms are likely
> to be widely supported gives the same conclusion -
> http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation describes
> support only for Concat and PBKDF2.****
>
> ** **
>
> Thus, while I appreciate the suggestion, and I did seriously investigate
> it, I don't think it's practical to move away from using the SP 800-56A
> Concat KDF.  That then established, I think that the task then before us =
is
> to decide exactly how to use it.  That will be the subject of a subsequen=
t
> message.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> -----Original Message-----****
>
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org<jose-bounces@ie=
tf.org>]
> On Behalf Of Manger, James H****
>
> Sent: Thursday, June 20, 2013 6:50 PM****
>
> To: Richard Barnes; Jim Schaad****
>
> Cc: jose@ietf.org****
>
> Subject: Re: [jose] Concat KDF****
>
> ** **
>
> > PartyUInfo seems compliant with the letter of the SP800-56A. SP800-56A =
*
> ***
>
> > doesn't place any constraints on the form or duration of the ****
>
> > identifier ID_U, so the 512-bit value provided seems sufficient if you =
*
> ***
>
> > regard that as ID_U.****
>
> ** **
>
> One aspect that has been confusing me is whether the recipient is expecte=
d
> to recognize ID_U as a known identifier for the originator, and ID_V as i=
ts
> own name?****
>
> ** **
>
> Alternatively, do requirements on these items only apply to the
> originator? Is it completely safe for a recipient to treat ID_U and ID_V =
as
> opaque bytes to be hashed as part of the KDF, but with no other processin=
g?
> Is it, in fact, safe for a recipient to treat OtherInfo (AlgorithmID +
> PartyUInfo +...) as an opaque blob, or even OtherInput (keydatalen +
> OtherInfo) as an opaque blob? In which case, we could simply include
> B64(OtherInput) in a JOSE message, perhaps with a suggested way an
> originator could construct OtherInput (eg from alg, enc, kid/jku, nonce).=
*
> ***
>
> ** **
>
> ** **
>
> > The better option would be to use the same KDF that CMS uses ****
>
> > [RFC3278][SEC1].  It's simpler, and also complies with USG mandates ***=
*
>
> > (Suite B [RFC5008]).  If we use the RFC 5008 variant, it also takes as =
*
> ***
>
> > input exactly what the current JWS spec provides:****
>
> > ****
>
> > KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo )****
>
> > ****
>
> > ECC-CMS-SharedInfo =3D {****
>
> >     keyInfo, // The algorithm with which the key will be used, ****
>
> > currently in AlgorithmID****
>
> >     entityUInfo, // The entropy source we're currently putting in ****
>
> > PartyUInfo****
>
> >     suppPubInfo // The derived key length, currently in SuppPubInfo }**=
*
> *
>
> > ****
>
> > In other words, CMS does exactly what JWS wants to do now.  Let's just =
*
> ***
>
> > do it for real.  Proposed text for Section 4.7.1 of JWA:****
>
> ** **
>
> Your proposal is "logically" the same as CMS (so same security
> properties), but the precise calculation is incompatible as you don't use=
 a
> DER-encoding of ECC-CMS-SharedInfo. Just wanted to clarify this intention=
.
> ****
>
> ** **
>
> > """****
>
> > The key derivation process derives the agreed upon key from the shared =
*
> ***
>
> > secret Z established through the ECDH algorithm using the single-pass *=
*
> **
>
> > KDF defined in [SEC1].  The inputs to the key derivation process are **=
*
> *
>
> > as****
>
> > follows:****
>
> > ****
>
> > Z This is set to the representation of the shared secret Z as an octet =
*
> ***
>
> > sequence.****
>
> > ****
>
> > SharedInfo This is set to the concatenation of the following octet ****
>
> > strings, in order:****
>
> >    1. The algorithm with which the derived key is to be used.  If the *=
*
> **
>
> > "alg" value is "ECDH", then this field contains the value of the "alg"*=
*
> **
>
> > parameter.  Otherwise, it contains the value of the "enc" parameter.***=
*
>
> ** **
>
> Wrong way around. If "alg" is "ECDH" use "enc" value, otherwise use "alg"
> value.****
>
> ** **
>
> You also need to separate this field from the next: with a length prefix,
> or separator char/byte.****
>
> With 2 variable-sized fields (algorithm and apu) you only theoretically
> need 1 length field to be unambiguous, but it needs to be at the start or
> end, not in between the 2 fields.****
>
> ** **
>
> >    2. The length of the value of the "apu" parameter, as a 32-bit big *=
*
> **
>
> > endian integer.  If the "apu" parameter is not present, then this ****
>
> > field is set to all zeros (0x00000000).****
>
> >    3. The value of the "apu" parameter, if present.  If provided, this =
*
> ***
>
> > value MUST contain at least 512 bits and a unique value SHOULD be used =
*
> ***
>
> > for each recipient.  The "apu" parameter MAY be omitted only if a ****
>
> > different ephemeral key is used for each key agreement transaction.****
>
> >    4. The length of the derived key, as a 32-bit big endian integer.***=
*
>
> >  For "ECDH-ES", this is length of the key used by the "enc" algorithm.*=
*
> **
>
> >  For "ECDH-ES+A128KW" or "ECDH-ES+A256KW", it is 128 (0x00000080) or***=
*
>
> > 256 (0x00000100), respectively.****
>
> ** **
>
> Symmetric key lengths are hardwired into "alg" and "enc" values in JOSE
> (eg "A256KW", "A128CGM") so we don't actually need a separate field.****
>
> ** **
>
> > """****
>
> > ****
>
> > Two side notes:****
>
> > 1. We need hash agility here (as in RFC 5008) to be able to meet ****
>
> > higher levels of security for which SHA-256 is unacceptable.  Suggest *=
*
> **
>
> > adding hash algorithms to the ECDH algorithm identifiers, e.g., ****
>
> > "ECDH256", "ECDH284+KW".****
>
> ** **
>
> "ECDH256", "ECDH256+A128KW", "ECDH384", "ECH384+A192KW"?          ****
>
> ** **
>
> > 2. The "-ES" is unnecessary, since the entropy added in entityUInfo is =
*
> ***
>
> > sufficient to address both ES and SS cases.****
>
> ** **
>
> ** **
>
> --****
>
> James Manger****
>
> _______________________________________________****
>
> jose mailing list****
>
> jose@ietf.org****
>
> https://www.ietf.org/mailman/listinfo/jose****
>
> _______________________________________________****
>
> jose mailing list****
>
> jose@ietf.org****
>
> https://www.ietf.org/mailman/listinfo/jose****
>

--047d7b3a8b66641d3204dfc329bb
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Don&#39;t think that quite answers the mail. =A0The algori=
thm text is correct. =A0However, SP800-56A still says that both PartyUInfo =
and PartyVInfo MUST NOT be empty. =A0So setting them to zero-length octet s=
trings is non-compliant. =A0There needs to be something there in any case. =
=A0And this still seems abusive of SP800-56A.=A0<div>
<br></div><div>I also think your assertion that Concat is a &quot;widely su=
pported KDF&quot; is rather thinly supported. =A0IIRC, your algorithm suppo=
rt spreadsheet from earlier showed that BCryptDeriveKey was the *only* know=
n implementation of Concat. =A0StackOverflow seems to agree, and NIST has a=
 special &quot;800-56A EXCEPT KDF&quot; category because that&#39;s apparen=
tly what everything does.</div>
<div>&lt;<a href=3D"http://stackoverflow.com/questions/10879658/existing-im=
plementations-for-nist-sp-800-56a-concatenation-key-derivation-functi">http=
://stackoverflow.com/questions/10879658/existing-implementations-for-nist-s=
p-800-56a-concatenation-key-derivation-functi</a>&gt;</div>
<div>&lt;<a href=3D"http://csrc.nist.gov/groups/STM/cavp/documents/componen=
ts/componentval.html">http://csrc.nist.gov/groups/STM/cavp/documents/compon=
ents/componentval.html</a>&gt;</div><div><br></div><div>So I don&#39;t thin=
k support is really a reason to prefer Concat. =A0Pretty much everyone is g=
oing to have to implement either KDF from scratch anyway (using concatenati=
on and a hash function), so we might as well choose one that (1) has some h=
istory in the IETF (so there&#39;s at least some code in CMS libraries), an=
d (2) doesn&#39;t have to be used with inappropriate semantics.<br>
</div><div><br></div><div>--Richard</div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><=
br><br><div class=3D"gmail_quote">On Fri, Jun 21, 2013 at 8:45 PM, Mike Jon=
es <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" tar=
get=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p>I agree with James&#39; conclusion that the -11 use of the Concat KDF do=
esn&#39;t conform to SP 800-56A because it doesn&#39;t support the PartyVIn=
fo parameter.=A0 I believe that DISCUSS comments will result if we don&#39;=
t enable conforming uses of Concat.=A0
 Therefore, I propose to make these specific changes relative to -11.<u></u=
><u></u></p>
<p><u></u>=A0<u></u></p>
<p>1.=A0 Revert the PartyUInfo and PartyVInfo language to the -10 text, whi=
ch was:<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">PartyUInfo<u></=
u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:96.0pt"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">The PartyUInfo =
value is of the form Datalen || Data, where Data is a variable-length strin=
g of zero or more octets, and Datalen is a fixed-length,
 big endian 32 bit counter that indicates the length (in octets) of Data, w=
ith || being concatenation. If an
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">apu</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> (agreement PartyUInfo) header parameter is pre=
sent, Data is set to the result of base64url decoding the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">apu</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> value and Datalen is set to the number of octe=
ts in Data. Otherwise, Datalen is set to 0 and Data is set
 to the empty octet sequence. <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">PartyVInfo<u></=
u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:96.0pt"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">The PartyVInfo =
value is of the form Datalen || Data, where Data is a variable-length strin=
g of zero or more octets, and Datalen is a fixed-length,
 big endian 32 bit counter that indicates the length (in octets) of Data, w=
ith || being concatenation. If an
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">apv</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> (agreement PartyVInfo) header parameter is pre=
sent, Data is set to the result of base64url decoding the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">apv</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> value and Datalen is set to the number of octe=
ts in Data. Otherwise, Datalen is set to 0 and Data is set
 to the empty octet sequence. <u></u><u></u></span></p>
<p><u></u>=A0<u></u></p>
<p>2.=A0 Change the AlgorithmID language to:<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">AlgorithmID<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:96.0pt"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">This is set to =
the octets of the UTF-8 representation of the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">alg</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> header parameter value when
</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;san=
s-serif&quot;">in the Key Agreement with Key Wrapping mode and
</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;san=
s-serif&quot;">to the octets of the UTF-8 representation of the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">enc</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> header parameter value when
</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;san=
s-serif&quot;">in the Direct Key Agreement mode</span><span lang=3D"EN" sty=
le=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">.<u></u><u></=
u></span></p>

<p><u></u>=A0<u></u></p>
<p>3.=A0 Attempting to accommodate what I believe are Jim=92s and Richard=
=92s desire to align with CMS=92s key derivation practices, I would add the=
 following paragraph:<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN" style=
=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;">The Diffie-Hell=
man Key Agreement Method [RFC 2631] uses a key derivation function similar =
to the Concat KDF, but with fewer parameters.=A0 Rather
 than having separate PartyUInfo and PartyVInfo parameters, it uses a singl=
e PartyAInfo parameter, which is a random string provided by the sender, th=
at contains 512 bits of information, when provided.=A0 It has no suppPrivIn=
fo parameter.=A0 Key agreement can be
 performed in a manner akin to RFC 2631 by using the PartyAInfo value as th=
e =93apu=94 (Agreement PartyUInfo) header parameter value, when provided, a=
nd by using no =93apv=94 (Agreement PartyVInfo) header parameter.<u></u><u>=
</u></span></p>

<p><u></u>=A0<u></u></p>
<p>Will those changes, collectively, satisfy all those who have been commen=
ting on this thread?=A0 If they will not, please supply specific alternativ=
e text.=A0
<span style=3D"color:red">Jim, Russ, James, and Richard</span> =96 what say=
 ye?<span class=3D"HOEnZb"><font color=3D"#888888"><u></u><u></u></font></s=
pan></p><span class=3D"HOEnZb"><font color=3D"#888888">
<p><u></u>=A0<u></u></p>
<p>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></p></font>=
</span><div><div class=3D"h5">
<p><u></u>=A0<u></u></p>
<p>-----Original Message-----<br>
From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"=
_blank">jose-bounces@ietf.org</a>] On Behalf Of Mike Jones<br>
Sent: Friday, June 21, 2013 4:22 PM<br>
To: Manger, James H; Richard Barnes; Jim Schaad<br>
Cc: <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br=
>
Subject: Re: [jose] Concat KDF</p>
<p><u></u>=A0<u></u></p>
<p>Thanks for the suggestion of using the RFC 5008 KDF.=A0 I did some resea=
rch into this, hoping to find that it was equivalent to the Concat KDF with=
 a suitable OtherInfo value, and unfortunately, found that the two are inco=
mpatible.=A0 The
 reason they&#39;re incompatible is that RFC 5008 computes this hash:<u></u=
><u></u></p>
<p>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 KM =3D Hash ( Z || Counter=
 || ECC-CMS-SharedInfo ) whereas Concat computes this hash:<u></u><u></u></=
p>
<p>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 K(i) =3D H(counter || Z ||=
 OtherInfo)<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>If the order of &quot;counter&quot; and &quot;Z&quot; were this same, an=
 implementation of Concat could be used to do the RFC 5008 computation, but=
 because the order is different, unfortunately it can&#39;t.<u></u><u></u><=
/p>

<p><u></u>=A0<u></u></p>
<p>The reason that this matters is we need to use a widely-supported KDF to=
 achieve the JOSE deployability and interoperability goals.=A0 When the ori=
ginal choice was made to use Concat, it was based upon looking into what KD=
Fs were already
 widely supported in libraries, and Concat looked like the best choice.<u><=
/u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Using Windows as an example, if you look at the BCryptDeriveKey function=
 at
<a href=3D"http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393=
(v=3Dvs.85).aspx" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://msdn.microsoft=
.com/en-us/library/windows/desktop/aa375393(v=3Dvs.85).aspx</span></a>, you=
&#39;ll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported KDF fun=
ctions but that the RFC 5008 function isn&#39;t.=A0
 (Yes, for key lengths only requiring a single has computation, you could p=
robably fake it with BCRYPT_KDF_HASH, but this wouldn&#39;t work for key le=
ngths requiring multiple hash computations.)=A0 The same problem is likely =
to appear on other platforms.<u></u><u></u></p>

<p><u></u>=A0<u></u></p>
<p>Using XML Encryption as a litmus test for what KDF algorithms are likely=
 to be widely supported gives the same conclusion -
<a href=3D"http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation" target=
=3D"_blank"><span style=3D"color:windowtext;text-decoration:none">http://ww=
w.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation</span></a> describes suppor=
t only for Concat and PBKDF2.<u></u><u></u></p>

<p><u></u>=A0<u></u></p>
<p>Thus, while I appreciate the suggestion, and I did seriously investigate=
 it, I don&#39;t think it&#39;s practical to move away from using the SP 80=
0-56A Concat KDF.=A0 That then established, I think that the task then befo=
re us is to decide exactly
 how to use it.=A0 That will be the subject of a subsequent message.<u></u>=
<u></u></p>
<p><u></u>=A0<u></u></p>
<p>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>-----Original Message-----<u></u><u></u></p>
<p>From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank"><span s=
tyle=3D"color:windowtext;text-decoration:none">jose-bounces@ietf.org</span>=
</a> [<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank"><span styl=
e=3D"color:windowtext;text-decoration:none">mailto:jose-bounces@ietf.org</s=
pan></a>]
 On Behalf Of Manger, James H<u></u><u></u></p>
<p>Sent: Thursday, June 20, 2013 6:50 PM<u></u><u></u></p>
<p>To: Richard Barnes; Jim Schaad<u></u><u></u></p>
<p>Cc: <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"co=
lor:windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u>=
</p>
<p>Subject: Re: [jose] Concat KDF<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; PartyUInfo seems compliant with the letter of the SP800-56A. SP800-=
56A
<u></u><u></u></p>
<p>&gt; doesn&#39;t place any constraints on the form or duration of the
<u></u><u></u></p>
<p>&gt; identifier ID_U, so the 512-bit value provided seems sufficient if =
you
<u></u><u></u></p>
<p>&gt; regard that as ID_U.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>One aspect that has been confusing me is whether the recipient is expect=
ed to recognize ID_U as a known identifier for the originator, and ID_V as =
its own name?<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Alternatively, do requirements on these items only apply to the originat=
or? Is it completely safe for a recipient to treat ID_U and ID_V as opaque =
bytes to be hashed as part of the KDF, but with no other processing? Is it,=
 in fact, safe
 for a recipient to treat OtherInfo (AlgorithmID + PartyUInfo +...) as an o=
paque blob, or even OtherInput (keydatalen + OtherInfo) as an opaque blob? =
In which case, we could simply include B64(OtherInput) in a JOSE message, p=
erhaps with a suggested way an originator
 could construct OtherInput (eg from alg, enc, kid/jku, nonce).<u></u><u></=
u></p>
<p><u></u>=A0<u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; The better option would be to use the same KDF that CMS uses
<u></u><u></u></p>
<p>&gt; [RFC3278][SEC1]. =A0It&#39;s simpler, and also complies with USG ma=
ndates
<u></u><u></u></p>
<p>&gt; (Suite B [RFC5008]). =A0If we use the RFC 5008 variant, it also tak=
es as
<u></u><u></u></p>
<p>&gt; input exactly what the current JWS spec provides:<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo )<u></u><u></u></p=
>
<p>&gt; <u></u><u></u></p>
<p>&gt; ECC-CMS-SharedInfo =3D {<u></u><u></u></p>
<p>&gt; =A0 =A0 keyInfo, // The algorithm with which the key will be used,
<u></u><u></u></p>
<p>&gt; currently in AlgorithmID<u></u><u></u></p>
<p>&gt; =A0 =A0 entityUInfo, // The entropy source we&#39;re currently putt=
ing in
<u></u><u></u></p>
<p>&gt; PartyUInfo<u></u><u></u></p>
<p>&gt; =A0 =A0 suppPubInfo // The derived key length, currently in=A0SuppP=
ubInfo }<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; In other words, CMS does exactly what JWS wants to do now. =A0Let&#=
39;s just
<u></u><u></u></p>
<p>&gt; do it for real. =A0Proposed text for Section 4.7.1 of JWA:<u></u><u=
></u></p>
<p><u></u>=A0<u></u></p>
<p>Your proposal is &quot;logically&quot; the same as CMS (so same security=
 properties), but the precise calculation is incompatible as you don&#39;t =
use a DER-encoding of ECC-CMS-SharedInfo. Just wanted to clarify this inten=
tion.<u></u><u></u></p>

<p><u></u>=A0<u></u></p>
<p>&gt; &quot;&quot;&quot;<u></u><u></u></p>
<p>&gt; The key derivation process derives the agreed upon key from the sha=
red
<u></u><u></u></p>
<p>&gt; secret Z established through the ECDH algorithm using the single-pa=
ss
<u></u><u></u></p>
<p>&gt; KDF defined in [SEC1]. =A0The inputs to the key derivation process =
are
<u></u><u></u></p>
<p>&gt; as<u></u><u></u></p>
<p>&gt; follows:<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; Z This is set to the representation of the shared secret Z as an oc=
tet
<u></u><u></u></p>
<p>&gt; sequence.<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; SharedInfo This is set to the concatenation of the following octet
<u></u><u></u></p>
<p>&gt; strings, in order:<u></u><u></u></p>
<p>&gt; =A0 =A01. The algorithm with which the derived key is to be used. =
=A0If the
<u></u><u></u></p>
<p>&gt; &quot;alg&quot; value is &quot;ECDH&quot;, then this field contains=
 the value of the &quot;alg&quot;<u></u><u></u></p>
<p>&gt; parameter. =A0Otherwise, it contains the value of the &quot;enc&quo=
t; parameter.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Wrong way around. If &quot;alg&quot; is &quot;ECDH&quot; use &quot;enc&q=
uot; value, otherwise use &quot;alg&quot; value.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>You also need to separate this field from the next: with a length prefix=
, or separator char/byte.<u></u><u></u></p>
<p>With 2 variable-sized fields (algorithm and apu) you only theoretically =
need 1 length field to be unambiguous, but it needs to be at the start or e=
nd, not in between the 2 fields.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; =A0 =A02. The length of the value of the &quot;apu&quot; parameter,=
 as a 32-bit big
<u></u><u></u></p>
<p>&gt; endian integer. =A0If the &quot;apu&quot; parameter is not present,=
 then this
<u></u><u></u></p>
<p>&gt; field is set to all zeros (0x00000000).<u></u><u></u></p>
<p>&gt; =A0 =A03. The value of the &quot;apu&quot; parameter, if present. =
=A0If provided, this
<u></u><u></u></p>
<p>&gt; value MUST contain at least 512 bits and a unique value SHOULD be u=
sed
<u></u><u></u></p>
<p>&gt; for each recipient. =A0The &quot;apu&quot; parameter MAY be omitted=
 only if a
<u></u><u></u></p>
<p>&gt; different ephemeral key is used for each key agreement transaction.=
<u></u><u></u></p>
<p>&gt; =A0 =A04. The length of the derived key, as a 32-bit big endian int=
eger.<u></u><u></u></p>
<p>&gt; =A0For &quot;ECDH-ES&quot;, this is length of the key used by the &=
quot;enc&quot; algorithm.<u></u><u></u></p>
<p>&gt; =A0For &quot;ECDH-ES+A128KW&quot; or &quot;ECDH-ES+A256KW&quot;, it=
 is 128 (0x00000080) or<u></u><u></u></p>
<p>&gt; 256 (0x00000100), respectively.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>Symmetric key lengths are hardwired into &quot;alg&quot; and &quot;enc&q=
uot; values in JOSE (eg &quot;A256KW&quot;, &quot;A128CGM&quot;) so we don&=
#39;t actually need a separate field.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; &quot;&quot;&quot;<u></u><u></u></p>
<p>&gt; <u></u><u></u></p>
<p>&gt; Two side notes:<u></u><u></u></p>
<p>&gt; 1. We need hash agility here (as in RFC 5008) to be able to meet
<u></u><u></u></p>
<p>&gt; higher levels of security for which SHA-256 is unacceptable. =A0Sug=
gest
<u></u><u></u></p>
<p>&gt; adding hash algorithms to the ECDH algorithm identifiers, e.g.,
<u></u><u></u></p>
<p>&gt; &quot;ECDH256&quot;, &quot;ECDH284+KW&quot;.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&quot;ECDH256&quot;, &quot;ECDH256+A128KW&quot;, &quot;ECDH384&quot;, &q=
uot;ECH384+A192KW&quot;?=A0=A0=A0=A0=A0=A0=A0=A0=A0
<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p>&gt; 2. The &quot;-ES&quot; is unnecessary, since the entropy added in e=
ntityUInfo is
<u></u><u></u></p>
<p>&gt; sufficient to address both ES and SS cases.<u></u><u></u></p>
<p><u></u>=A0<u></u></p>
<p><u></u>=A0<u></u></p>
<p>--<u></u><u></u></p>
<p>James Manger<u></u><u></u></p>
<p>_______________________________________________<u></u><u></u></p>
<p>jose mailing list<u></u><u></u></p>
<p><a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"color:=
windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u></p>
<p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/jose</span></a><u></u><u></u></p>
<p>_______________________________________________<u></u><u></u></p>
<p>jose mailing list<u></u><u></u></p>
<p><a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"color:=
windowtext;text-decoration:none">jose@ietf.org</span></a><u></u><u></u></p>
<p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/jose</span></a><u></u><u></u></p>
</div></div></div>
</div>

</blockquote></div><br></div>

--047d7b3a8b66641d3204dfc329bb--

From ietf@augustcellars.com  Sat Jun 22 14:29:52 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BEA721F9E67 for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 14:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.242
X-Spam-Level: 
X-Spam-Status: No, score=-4.242 tagged_above=-999 required=5 tests=[AWL=0.756,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwCUPZWJ5msW for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 14:29:45 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 56CF221F9E85 for <jose@ietf.org>; Sat, 22 Jun 2013 14:29:45 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 89A622CA28; Sat, 22 Jun 2013 14:29:42 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Richard Barnes'" <rlb@ipv.sx>, "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>	<033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>	<CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>	<4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>	<4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>
In-Reply-To: <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>
Date: Sat, 22 Jun 2013 14:28:45 -0700
Message-ID: <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004B_01CE6F54.CF33FD70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwQJlRGK8ApvD+k8A6jOEoAH71aeeAt8ahgUCiwG8iJgIc3YQ
Content-Language: en-us
Cc: "'Manger, James H'" <James.H.Manger@team.telstra.com>, 'Russ Housley' <housley@vigilsec.com>, jose@ietf.org
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 21:29:52 -0000

This is a multipart message in MIME format.

------=_NextPart_000_004B_01CE6F54.CF33FD70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This does not also answer the question of how entities are going to be named
in JOSE.  It is easy to do in TLS and for PKIX because there are always
names for them.  This is not a feature of JOSE, we don't name people that is
left for applications.  Also if one looks at it, then we should not need to
send this information in the message because each party would know the names
of both entities.

 

Having read the rational for using identifiers, it is not clear that there
is anything in the rational that applies to JOSE in any case.  Given that we
are doing ephemeral-static dh, there is no way for a shared key attack to
occur in the case of a store and forward message.  

 

There is a possibility that it could occur for the case of XMPP where one is
separating the key management from the key usage, but it is not a general
case problem.

 

If we are going to be in a situation where we don't know the names of the
entities - unless the application somehow finds them out, makes them common
and then tells the application what they are there is no reason not to use
fixed constants.  I don't know what the benefit is going to be for saying,
in the message, that for the purposes of this message "Your name is Fred".

 

Jim

 

 

From: Richard Barnes [mailto:rlb@ipv.sx] 
Sent: Saturday, June 22, 2013 12:27 PM
To: Mike Jones
Cc: Jim Schaad; Russ Housley; Manger, James H; jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Don't think that quite answers the mail.  The algorithm text is correct.
However, SP800-56A still says that both PartyUInfo and PartyVInfo MUST NOT
be empty.  So setting them to zero-length octet strings is non-compliant.
There needs to be something there in any case.  And this still seems abusive
of SP800-56A. 

 

I also think your assertion that Concat is a "widely supported KDF" is
rather thinly supported.  IIRC, your algorithm support spreadsheet from
earlier showed that BCryptDeriveKey was the *only* known implementation of
Concat.  StackOverflow seems to agree, and NIST has a special "800-56A
EXCEPT KDF" category because that's apparently what everything does.

<http://stackoverflow.com/questions/10879658/existing-implementations-for-ni
st-sp-800-56a-concatenation-key-derivation-functi>

<http://csrc.nist.gov/groups/STM/cavp/documents/components/componentval.html
>

 

So I don't think support is really a reason to prefer Concat.  Pretty much
everyone is going to have to implement either KDF from scratch anyway (using
concatenation and a hash function), so we might as well choose one that (1)
has some history in the IETF (so there's at least some code in CMS
libraries), and (2) doesn't have to be used with inappropriate semantics.

 

--Richard

 

 

 

 

 

 

On Fri, Jun 21, 2013 at 8:45 PM, Mike Jones <Michael.Jones@microsoft.com>
wrote:

I agree with James' conclusion that the -11 use of the Concat KDF doesn't
conform to SP 800-56A because it doesn't support the PartyVInfo parameter.
I believe that DISCUSS comments will result if we don't enable conforming
uses of Concat.  Therefore, I propose to make these specific changes
relative to -11.

 

1.  Revert the PartyUInfo and PartyVInfo language to the -10 text, which
was:

PartyUInfo

The PartyUInfo value is of the form Datalen || Data, where Data is a
variable-length string of zero or more octets, and Datalen is a
fixed-length, big endian 32 bit counter that indicates the length (in
octets) of Data, with || being concatenation. If an apu (agreement
PartyUInfo) header parameter is present, Data is set to the result of
base64url decoding the apu value and Datalen is set to the number of octets
in Data. Otherwise, Datalen is set to 0 and Data is set to the empty octet
sequence. 

PartyVInfo

The PartyVInfo value is of the form Datalen || Data, where Data is a
variable-length string of zero or more octets, and Datalen is a
fixed-length, big endian 32 bit counter that indicates the length (in
octets) of Data, with || being concatenation. If an apv (agreement
PartyVInfo) header parameter is present, Data is set to the result of
base64url decoding the apv value and Datalen is set to the number of octets
in Data. Otherwise, Datalen is set to 0 and Data is set to the empty octet
sequence. 

 

2.  Change the AlgorithmID language to:

AlgorithmID

This is set to the octets of the UTF-8 representation of the alg header
parameter value when in the Key Agreement with Key Wrapping mode and to the
octets of the UTF-8 representation of the enc header parameter value when in
the Direct Key Agreement mode.

 

3.  Attempting to accommodate what I believe are Jim's and Richard's desire
to align with CMS's key derivation practices, I would add the following
paragraph:

 

The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation
function similar to the Concat KDF, but with fewer parameters.  Rather than
having separate PartyUInfo and PartyVInfo parameters, it uses a single
PartyAInfo parameter, which is a random string provided by the sender, that
contains 512 bits of information, when provided.  It has no suppPrivInfo
parameter.  Key agreement can be performed in a manner akin to RFC 2631 by
using the PartyAInfo value as the "apu" (Agreement PartyUInfo) header
parameter value, when provided, and by using no "apv" (Agreement PartyVInfo)
header parameter.

 

Will those changes, collectively, satisfy all those who have been commenting
on this thread?  If they will not, please supply specific alternative text.
Jim, Russ, James, and Richard - what say ye?

 

                                                                -- Mike

 

-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Friday, June 21, 2013 4:22 PM
To: Manger, James H; Richard Barnes; Jim Schaad
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Thanks for the suggestion of using the RFC 5008 KDF.  I did some research
into this, hoping to find that it was equivalent to the Concat KDF with a
suitable OtherInfo value, and unfortunately, found that the two are
incompatible.  The reason they're incompatible is that RFC 5008 computes
this hash:

                KM = Hash ( Z || Counter || ECC-CMS-SharedInfo ) whereas
Concat computes this hash:

                K(i) = H(counter || Z || OtherInfo)

 

If the order of "counter" and "Z" were this same, an implementation of
Concat could be used to do the RFC 5008 computation, but because the order
is different, unfortunately it can't.

 

The reason that this matters is we need to use a widely-supported KDF to
achieve the JOSE deployability and interoperability goals.  When the
original choice was made to use Concat, it was based upon looking into what
KDFs were already widely supported in libraries, and Concat looked like the
best choice.

 

Using Windows as an example, if you look at the BCryptDeriveKey function at
<http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393(v=vs.85).a
spx>
http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393(v=vs.85).as
px, you'll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported KDF
functions but that the RFC 5008 function isn't.  (Yes, for key lengths only
requiring a single has computation, you could probably fake it with
BCRYPT_KDF_HASH, but this wouldn't work for key lengths requiring multiple
hash computations.)  The same problem is likely to appear on other
platforms.

 

Using XML Encryption as a litmus test for what KDF algorithms are likely to
be widely supported gives the same conclusion -
<http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation>
http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation describes support
only for Concat and PBKDF2.

 

Thus, while I appreciate the suggestion, and I did seriously investigate it,
I don't think it's practical to move away from using the SP 800-56A Concat
KDF.  That then established, I think that the task then before us is to
decide exactly how to use it.  That will be the subject of a subsequent
message.

 

                                                                -- Mike

 

-----Original Message-----

From:  <mailto:jose-bounces@ietf.org> jose-bounces@ietf.org [
<mailto:jose-bounces@ietf.org> mailto:jose-bounces@ietf.org] On Behalf Of
Manger, James H

Sent: Thursday, June 20, 2013 6:50 PM

To: Richard Barnes; Jim Schaad

Cc:  <mailto:jose@ietf.org> jose@ietf.org

Subject: Re: [jose] Concat KDF

 

> PartyUInfo seems compliant with the letter of the SP800-56A. SP800-56A 

> doesn't place any constraints on the form or duration of the 

> identifier ID_U, so the 512-bit value provided seems sufficient if you 

> regard that as ID_U.

 

One aspect that has been confusing me is whether the recipient is expected
to recognize ID_U as a known identifier for the originator, and ID_V as its
own name?

 

Alternatively, do requirements on these items only apply to the originator?
Is it completely safe for a recipient to treat ID_U and ID_V as opaque bytes
to be hashed as part of the KDF, but with no other processing? Is it, in
fact, safe for a recipient to treat OtherInfo (AlgorithmID + PartyUInfo
+...) as an opaque blob, or even OtherInput (keydatalen + OtherInfo) as an
opaque blob? In which case, we could simply include B64(OtherInput) in a
JOSE message, perhaps with a suggested way an originator could construct
OtherInput (eg from alg, enc, kid/jku, nonce).

 

 

> The better option would be to use the same KDF that CMS uses 

> [RFC3278][SEC1].  It's simpler, and also complies with USG mandates 

> (Suite B [RFC5008]).  If we use the RFC 5008 variant, it also takes as 

> input exactly what the current JWS spec provides:

> 

> KM = Hash ( Z || Counter || ECC-CMS-SharedInfo )

> 

> ECC-CMS-SharedInfo = {

>     keyInfo, // The algorithm with which the key will be used, 

> currently in AlgorithmID

>     entityUInfo, // The entropy source we're currently putting in 

> PartyUInfo

>     suppPubInfo // The derived key length, currently in SuppPubInfo }

> 

> In other words, CMS does exactly what JWS wants to do now.  Let's just 

> do it for real.  Proposed text for Section 4.7.1 of JWA:

 

Your proposal is "logically" the same as CMS (so same security properties),
but the precise calculation is incompatible as you don't use a DER-encoding
of ECC-CMS-SharedInfo. Just wanted to clarify this intention.

 

> """

> The key derivation process derives the agreed upon key from the shared 

> secret Z established through the ECDH algorithm using the single-pass 

> KDF defined in [SEC1].  The inputs to the key derivation process are 

> as

> follows:

> 

> Z This is set to the representation of the shared secret Z as an octet 

> sequence.

> 

> SharedInfo This is set to the concatenation of the following octet 

> strings, in order:

>    1. The algorithm with which the derived key is to be used.  If the 

> "alg" value is "ECDH", then this field contains the value of the "alg"

> parameter.  Otherwise, it contains the value of the "enc" parameter.

 

Wrong way around. If "alg" is "ECDH" use "enc" value, otherwise use "alg"
value.

 

You also need to separate this field from the next: with a length prefix, or
separator char/byte.

With 2 variable-sized fields (algorithm and apu) you only theoretically need
1 length field to be unambiguous, but it needs to be at the start or end,
not in between the 2 fields.

 

>    2. The length of the value of the "apu" parameter, as a 32-bit big 

> endian integer.  If the "apu" parameter is not present, then this 

> field is set to all zeros (0x00000000).

>    3. The value of the "apu" parameter, if present.  If provided, this 

> value MUST contain at least 512 bits and a unique value SHOULD be used 

> for each recipient.  The "apu" parameter MAY be omitted only if a 

> different ephemeral key is used for each key agreement transaction.

>    4. The length of the derived key, as a 32-bit big endian integer.

>  For "ECDH-ES", this is length of the key used by the "enc" algorithm.

>  For "ECDH-ES+A128KW" or "ECDH-ES+A256KW", it is 128 (0x00000080) or

> 256 (0x00000100), respectively.

 

Symmetric key lengths are hardwired into "alg" and "enc" values in JOSE (eg
"A256KW", "A128CGM") so we don't actually need a separate field.

 

> """

> 

> Two side notes:

> 1. We need hash agility here (as in RFC 5008) to be able to meet 

> higher levels of security for which SHA-256 is unacceptable.  Suggest 

> adding hash algorithms to the ECDH algorithm identifiers, e.g., 

> "ECDH256", "ECDH284+KW".

 

"ECDH256", "ECDH256+A128KW", "ECDH384", "ECH384+A192KW"?          

 

> 2. The "-ES" is unnecessary, since the entropy added in entityUInfo is 

> sufficient to address both ES and SS cases.

 

 

--

James Manger

_______________________________________________

jose mailing list

 <mailto:jose@ietf.org> jose@ietf.org

 <https://www.ietf.org/mailman/listinfo/jose>
https://www.ietf.org/mailman/listinfo/jose

_______________________________________________

jose mailing list

 <mailto:jose@ietf.org> jose@ietf.org

 <https://www.ietf.org/mailman/listinfo/jose>
https://www.ietf.org/mailman/listinfo/jose

 


------=_NextPart_000_004B_01CE6F54.CF33FD70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This does not also answer the question of how entities are going to =
be named in JOSE.&nbsp; It is easy to do in TLS and for PKIX because =
there are always names for them.&nbsp; This is not a feature of JOSE, we =
don&#8217;t name people that is left for applications.&nbsp; Also if one =
looks at it, then we should not need to send this information in the =
message because each party would know the names of both =
entities.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Having read the rational for using identifiers, it is not clear that =
there is anything in the rational that applies to JOSE in any case. =
&nbsp;Given that we are doing ephemeral-static dh, there is no way for a =
shared key attack to occur in the case of a store and forward =
message.&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There is a possibility that it could occur for the case of XMPP where =
one is separating the key management from the key usage, but it is not a =
general case problem.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If we are going to be in a situation where we don&#8217;t know the =
names of the entities &#8211; unless the application somehow finds them =
out, makes them common&nbsp; and then tells the application what they =
are there is no reason not to use fixed constants.&nbsp; I don&#8217;t =
know what the benefit is going to be for saying, in the message, that =
for the purposes of this message &#8220;Your name is =
Fred&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Richard Barnes [mailto:rlb@ipv.sx] <br><b>Sent:</b> Saturday, June 22, =
2013 12:27 PM<br><b>To:</b> Mike Jones<br><b>Cc:</b> Jim Schaad; Russ =
Housley; Manger, James H; jose@ietf.org<br><b>Subject:</b> Re: [jose] =
Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Don't =
think that quite answers the mail. &nbsp;The algorithm text is correct. =
&nbsp;However, SP800-56A still says that both PartyUInfo and PartyVInfo =
MUST NOT be empty. &nbsp;So setting them to zero-length octet strings is =
non-compliant. &nbsp;There needs to be something there in any case. =
&nbsp;And this still seems abusive of =
SP800-56A.&nbsp;<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
also think your assertion that Concat is a &quot;widely supported =
KDF&quot; is rather thinly supported. &nbsp;IIRC, your algorithm support =
spreadsheet from earlier showed that BCryptDeriveKey was the *only* =
known implementation of Concat. &nbsp;StackOverflow seems to agree, and =
NIST has a special &quot;800-56A EXCEPT KDF&quot; category because =
that's apparently what everything does.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&lt;<a =
href=3D"http://stackoverflow.com/questions/10879658/existing-implementati=
ons-for-nist-sp-800-56a-concatenation-key-derivation-functi">http://stack=
overflow.com/questions/10879658/existing-implementations-for-nist-sp-800-=
56a-concatenation-key-derivation-functi</a>&gt;<o:p></o:p></p></div><div>=
<p class=3DMsoNormal>&lt;<a =
href=3D"http://csrc.nist.gov/groups/STM/cavp/documents/components/compone=
ntval.html">http://csrc.nist.gov/groups/STM/cavp/documents/components/com=
ponentval.html</a>&gt;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>So I don't think support is really a reason to prefer =
Concat. &nbsp;Pretty much everyone is going to have to implement either =
KDF from scratch anyway (using concatenation and a hash function), so we =
might as well choose one that (1) has some history in the IETF (so =
there's at least some code in CMS libraries), and (2) doesn't have to be =
used with inappropriate semantics.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>--Richard<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Fri, Jun 21, 2013 at 8:45 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p>I agree with James' conclusion that =
the -11 use of the Concat KDF doesn't conform to SP 800-56A because it =
doesn't support the PartyVInfo parameter.&nbsp; I believe that DISCUSS =
comments will result if we don't enable conforming uses of Concat.&nbsp; =
Therefore, I propose to make these specific changes relative to =
-11.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>1.&nbsp; Revert the =
PartyUInfo and PartyVInfo language to the -10 text, which =
was:<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.=
5in'><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'>PartyUInfo</span><o:p></o:p>=
</p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:9=
6.0pt'><span lang=3DEN style=3D'font-family:"Verdana","sans-serif"'>The =
PartyUInfo value is of the form Datalen || Data, where Data is a =
variable-length string of zero or more octets, and Datalen is a =
fixed-length, big endian 32 bit counter that indicates the length (in =
octets) of Data, with || being concatenation. If an </span><span =
lang=3DEN style=3D'font-family:"Courier =
New";color:#003366'>apu</span><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'> (agreement PartyUInfo) =
header parameter is present, Data is set to the result of base64url =
decoding the </span><span lang=3DEN style=3D'font-family:"Courier =
New";color:#003366'>apu</span><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'> value and Datalen is set =
to the number of octets in Data. Otherwise, Datalen is set to 0 and Data =
is set to the empty octet sequence. </span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.=
5in'><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'>PartyVInfo</span><o:p></o:p>=
</p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:9=
6.0pt'><span lang=3DEN style=3D'font-family:"Verdana","sans-serif"'>The =
PartyVInfo value is of the form Datalen || Data, where Data is a =
variable-length string of zero or more octets, and Datalen is a =
fixed-length, big endian 32 bit counter that indicates the length (in =
octets) of Data, with || being concatenation. If an </span><span =
lang=3DEN style=3D'font-family:"Courier =
New";color:#003366'>apv</span><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'> (agreement PartyVInfo) =
header parameter is present, Data is set to the result of base64url =
decoding the </span><span lang=3DEN style=3D'font-family:"Courier =
New";color:#003366'>apv</span><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'> value and Datalen is set =
to the number of octets in Data. Otherwise, Datalen is set to 0 and Data =
is set to the empty octet sequence. =
</span><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>2.&nbsp; Change the =
AlgorithmID language to:<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.=
5in'><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'>AlgorithmID</span><o:p></o:p=
></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:9=
6.0pt'><span lang=3DEN style=3D'font-family:"Verdana","sans-serif"'>This =
is set to the octets of the UTF-8 representation of the </span><span =
lang=3DEN style=3D'font-family:"Courier =
New";color:#003366'>alg</span><span lang=3DEN =
style=3D'font-family:"Verdana","sans-serif"'> header parameter value =
when in the Key Agreement with Key Wrapping mode and to the octets of =
the UTF-8 representation of the </span><span lang=3DEN =
style=3D'font-family:"Courier New";color:#003366'>enc</span><span =
lang=3DEN style=3D'font-family:"Verdana","sans-serif"'> header parameter =
value when in the Direct Key Agreement =
mode.</span><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>3.&nbsp; =
Attempting to accommodate what I believe are Jim&#8217;s and =
Richard&#8217;s desire to align with CMS&#8217;s key derivation =
practices, I would add the following =
paragraph:<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.=
5in'><span lang=3DEN style=3D'font-family:"Verdana","sans-serif"'>The =
Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation =
function similar to the Concat KDF, but with fewer parameters.&nbsp; =
Rather than having separate PartyUInfo and PartyVInfo parameters, it =
uses a single PartyAInfo parameter, which is a random string provided by =
the sender, that contains 512 bits of information, when provided.&nbsp; =
It has no suppPrivInfo parameter.&nbsp; Key agreement can be performed =
in a manner akin to RFC 2631 by using the PartyAInfo value as the =
&#8220;apu&#8221; (Agreement PartyUInfo) header parameter value, when =
provided, and by using no &#8220;apv&#8221; (Agreement PartyVInfo) =
header parameter.</span><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Will =
those changes, collectively, satisfy all those who have been commenting =
on this thread?&nbsp; If they will not, please supply specific =
alternative text.&nbsp; <span style=3D'color:red'>Jim, Russ, James, and =
Richard</span> &#8211; what say ye?<o:p></o:p></p><p><span =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p><p><span =
style=3D'color:#888888'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><div><div><p>&nbsp;<o:p></o:p></p><p>-----Origi=
nal Message-----<br>From: <a href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank">jose-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank">jose-bounces@ietf.org</a>] On Behalf Of Mike =
Jones<br>Sent: Friday, June 21, 2013 4:22 PM<br>To: Manger, James H; =
Richard Barnes; Jim Schaad<br>Cc: <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a><br>Subject: Re: [jose] Concat =
KDF<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Thanks for the suggestion =
of using the RFC 5008 KDF.&nbsp; I did some research into this, hoping =
to find that it was equivalent to the Concat KDF with a suitable =
OtherInfo value, and unfortunately, found that the two are =
incompatible.&nbsp; The reason they're incompatible is that RFC 5008 =
computes this =
hash:<o:p></o:p></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; KM =3D Hash ( Z || Counter || =
ECC-CMS-SharedInfo ) whereas Concat computes this =
hash:<o:p></o:p></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; K(i) =3D H(counter || Z || =
OtherInfo)<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>If the order of =
&quot;counter&quot; and &quot;Z&quot; were this same, an implementation =
of Concat could be used to do the RFC 5008 computation, but because the =
order is different, unfortunately it =
can't.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>The reason that this =
matters is we need to use a widely-supported KDF to achieve the JOSE =
deployability and interoperability goals.&nbsp; When the original choice =
was made to use Concat, it was based upon looking into what KDFs were =
already widely supported in libraries, and Concat looked like the best =
choice.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Using Windows as an =
example, if you look at the BCryptDeriveKey function at <a =
href=3D"http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393(=
v=3Dvs.85).aspx" target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>http://msdn.microsoft.com=
/en-us/library/windows/desktop/aa375393(v=3Dvs.85).aspx</span></a>, =
you'll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported KDF =
functions but that the RFC 5008 function isn't.&nbsp; (Yes, for key =
lengths only requiring a single has computation, you could probably fake =
it with BCRYPT_KDF_HASH, but this wouldn't work for key lengths =
requiring multiple hash computations.)&nbsp; The same problem is likely =
to appear on other =
platforms.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Using XML Encryption =
as a litmus test for what KDF algorithms are likely to be widely =
supported gives the same conclusion - <a =
href=3D"http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>http://www.w3.org/TR/xmle=
nc-core1/#sec-Alg-KeyDerivation</span></a> describes support only for =
Concat and PBKDF2.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Thus, while =
I appreciate the suggestion, and I did seriously investigate it, I don't =
think it's practical to move away from using the SP 800-56A Concat =
KDF.&nbsp; That then established, I think that the task then before us =
is to decide exactly how to use it.&nbsp; That will be the subject of a =
subsequent =
message.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>-----Original =
Message-----<o:p></o:p></p><p>From: <a =
href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>jose-bounces@ietf.org</sp=
an></a> [<a href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:jose-bounces@ietf.=
org</span></a>] On Behalf Of Manger, James H<o:p></o:p></p><p>Sent: =
Thursday, June 20, 2013 6:50 PM<o:p></o:p></p><p>To: Richard Barnes; Jim =
Schaad<o:p></o:p></p><p>Cc: <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p>Subject: Re: [jose] Concat =
KDF<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&gt; PartyUInfo seems =
compliant with the letter of the SP800-56A. SP800-56A =
<o:p></o:p></p><p>&gt; doesn't place any constraints on the form or =
duration of the <o:p></o:p></p><p>&gt; identifier ID_U, so the 512-bit =
value provided seems sufficient if you <o:p></o:p></p><p>&gt; regard =
that as ID_U.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>One aspect that =
has been confusing me is whether the recipient is expected to recognize =
ID_U as a known identifier for the originator, and ID_V as its own =
name?<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Alternatively, do =
requirements on these items only apply to the originator? Is it =
completely safe for a recipient to treat ID_U and ID_V as opaque bytes =
to be hashed as part of the KDF, but with no other processing? Is it, in =
fact, safe for a recipient to treat OtherInfo (AlgorithmID + PartyUInfo =
+...) as an opaque blob, or even OtherInput (keydatalen + OtherInfo) as =
an opaque blob? In which case, we could simply include B64(OtherInput) =
in a JOSE message, perhaps with a suggested way an originator could =
construct OtherInput (eg from alg, enc, kid/jku, =
nonce).<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>=
&gt; The better option would be to use the same KDF that CMS uses =
<o:p></o:p></p><p>&gt; [RFC3278][SEC1]. &nbsp;It's simpler, and also =
complies with USG mandates <o:p></o:p></p><p>&gt; (Suite B [RFC5008]). =
&nbsp;If we use the RFC 5008 variant, it also takes as =
<o:p></o:p></p><p>&gt; input exactly what the current JWS spec =
provides:<o:p></o:p></p><p>&gt; <o:p></o:p></p><p>&gt; KM =3D Hash ( Z =
|| Counter || ECC-CMS-SharedInfo )<o:p></o:p></p><p>&gt; =
<o:p></o:p></p><p>&gt; ECC-CMS-SharedInfo =3D {<o:p></o:p></p><p>&gt; =
&nbsp; &nbsp; keyInfo, // The algorithm with which the key will be used, =
<o:p></o:p></p><p>&gt; currently in AlgorithmID<o:p></o:p></p><p>&gt; =
&nbsp; &nbsp; entityUInfo, // The entropy source we're currently putting =
in <o:p></o:p></p><p>&gt; PartyUInfo<o:p></o:p></p><p>&gt; &nbsp; &nbsp; =
suppPubInfo // The derived key length, currently in&nbsp;SuppPubInfo =
}<o:p></o:p></p><p>&gt; <o:p></o:p></p><p>&gt; In other words, CMS does =
exactly what JWS wants to do now. &nbsp;Let's just =
<o:p></o:p></p><p>&gt; do it for real. &nbsp;Proposed text for Section =
4.7.1 of JWA:<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Your proposal is =
&quot;logically&quot; the same as CMS (so same security properties), but =
the precise calculation is incompatible as you don't use a DER-encoding =
of ECC-CMS-SharedInfo. Just wanted to clarify this =
intention.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&gt; =
&quot;&quot;&quot;<o:p></o:p></p><p>&gt; The key derivation process =
derives the agreed upon key from the shared <o:p></o:p></p><p>&gt; =
secret Z established through the ECDH algorithm using the single-pass =
<o:p></o:p></p><p>&gt; KDF defined in [SEC1]. &nbsp;The inputs to the =
key derivation process are <o:p></o:p></p><p>&gt; =
as<o:p></o:p></p><p>&gt; follows:<o:p></o:p></p><p>&gt; =
<o:p></o:p></p><p>&gt; Z This is set to the representation of the shared =
secret Z as an octet <o:p></o:p></p><p>&gt; =
sequence.<o:p></o:p></p><p>&gt; <o:p></o:p></p><p>&gt; SharedInfo This =
is set to the concatenation of the following octet =
<o:p></o:p></p><p>&gt; strings, in order:<o:p></o:p></p><p>&gt; &nbsp; =
&nbsp;1. The algorithm with which the derived key is to be used. =
&nbsp;If the <o:p></o:p></p><p>&gt; &quot;alg&quot; value is =
&quot;ECDH&quot;, then this field contains the value of the =
&quot;alg&quot;<o:p></o:p></p><p>&gt; parameter. &nbsp;Otherwise, it =
contains the value of the &quot;enc&quot; =
parameter.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Wrong way around. If =
&quot;alg&quot; is &quot;ECDH&quot; use &quot;enc&quot; value, otherwise =
use &quot;alg&quot; value.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>You =
also need to separate this field from the next: with a length prefix, or =
separator char/byte.<o:p></o:p></p><p>With 2 variable-sized fields =
(algorithm and apu) you only theoretically need 1 length field to be =
unambiguous, but it needs to be at the start or end, not in between the =
2 fields.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&gt; &nbsp; &nbsp;2. =
The length of the value of the &quot;apu&quot; parameter, as a 32-bit =
big <o:p></o:p></p><p>&gt; endian integer. &nbsp;If the &quot;apu&quot; =
parameter is not present, then this <o:p></o:p></p><p>&gt; field is set =
to all zeros (0x00000000).<o:p></o:p></p><p>&gt; &nbsp; &nbsp;3. The =
value of the &quot;apu&quot; parameter, if present. &nbsp;If provided, =
this <o:p></o:p></p><p>&gt; value MUST contain at least 512 bits and a =
unique value SHOULD be used <o:p></o:p></p><p>&gt; for each recipient. =
&nbsp;The &quot;apu&quot; parameter MAY be omitted only if a =
<o:p></o:p></p><p>&gt; different ephemeral key is used for each key =
agreement transaction.<o:p></o:p></p><p>&gt; &nbsp; &nbsp;4. The length =
of the derived key, as a 32-bit big endian =
integer.<o:p></o:p></p><p>&gt; &nbsp;For &quot;ECDH-ES&quot;, this is =
length of the key used by the &quot;enc&quot; =
algorithm.<o:p></o:p></p><p>&gt; &nbsp;For &quot;ECDH-ES+A128KW&quot; or =
&quot;ECDH-ES+A256KW&quot;, it is 128 (0x00000080) =
or<o:p></o:p></p><p>&gt; 256 (0x00000100), =
respectively.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>Symmetric key =
lengths are hardwired into &quot;alg&quot; and &quot;enc&quot; values in =
JOSE (eg &quot;A256KW&quot;, &quot;A128CGM&quot;) so we don't actually =
need a separate field.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&gt; =
&quot;&quot;&quot;<o:p></o:p></p><p>&gt; <o:p></o:p></p><p>&gt; Two side =
notes:<o:p></o:p></p><p>&gt; 1. We need hash agility here (as in RFC =
5008) to be able to meet <o:p></o:p></p><p>&gt; higher levels of =
security for which SHA-256 is unacceptable. &nbsp;Suggest =
<o:p></o:p></p><p>&gt; adding hash algorithms to the ECDH algorithm =
identifiers, e.g., <o:p></o:p></p><p>&gt; &quot;ECDH256&quot;, =
&quot;ECDH284+KW&quot;.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&quot;EC=
DH256&quot;, &quot;ECDH256+A128KW&quot;, &quot;ECDH384&quot;, =
&quot;ECH384+A192KW&quot;?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; <o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&gt; 2. The =
&quot;-ES&quot; is unnecessary, since the entropy added in entityUInfo =
is <o:p></o:p></p><p>&gt; sufficient to address both ES and SS =
cases.<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p>-=
-<o:p></o:p></p><p>James =
Manger<o:p></o:p></p><p>_______________________________________________<o=
:p></o:p></p><p>jose mailing list<o:p></o:p></p><p><a =
href=3D"mailto:jose@ietf.org" target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/jose</span></a><o:p></o:p></p><p>___________________________=
____________________<o:p></o:p></p><p>jose mailing =
list<o:p></o:p></p><p><a href=3D"mailto:jose@ietf.org" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/jose</span></a><o:p></o:p></p></div></div></div></div></div>=
<p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_004B_01CE6F54.CF33FD70--


From Michael.Jones@microsoft.com  Sat Jun 22 15:18:33 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7308F21F9D6B for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 15:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.228
X-Spam-Level: 
X-Spam-Status: No, score=-3.228 tagged_above=-999 required=5 tests=[AWL=0.770,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndRDkEqkiXjv for <jose@ietfa.amsl.com>; Sat, 22 Jun 2013 15:18:25 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 811E521F9CED for <jose@ietf.org>; Sat, 22 Jun 2013 15:18:25 -0700 (PDT)
Received: from BN1BFFO11FD018.protection.gbl (10.58.52.204) by BN1BFFO11HUB020.protection.gbl (10.58.53.130) with Microsoft SMTP Server (TLS) id 15.0.707.0; Sat, 22 Jun 2013 22:18:22 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD018.mail.protection.outlook.com (10.58.53.78) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Sat, 22 Jun 2013 22:18:22 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Sat, 22 Jun 2013 22:17:16 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Richard Barnes' <rlb@ipv.sx>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkgAALrZmAAKEYUAAAEQbmAAAFAjDA=
Date: Sat, 22 Jun 2013 22:17:15 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>
In-Reply-To: <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367888C47TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(51704005)(51914003)(51444003)(377454003)(189002)(51694002)(13464003)(124975003)(24454002)(6806003)(16236675002)(19300405004)(4396001)(47446002)(512954002)(55846006)(56776001)(65816001)(49866001)(76796001)(59766001)(79102001)(81542001)(551934002)(74876001)(71186001)(63696002)(15202345003)(50986001)(76482001)(56816003)(77096001)(77982001)(20776003)(74502001)(54356001)(46102001)(47736001)(76786001)(16406001)(74662001)(51856001)(561944002)(31966008)(66066001)(81342001)(74706001)(15395725003)(54316002)(53806001)(47976001)(69226001)(74366001)(80022001)(33656001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB020; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 088552DE73
Cc: "'Manger, James H'" <James.H.Manger@team.telstra.com>, 'Russ Housley' <housley@vigilsec.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 22:18:33 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367888C47TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I can add a sentence along the lines of the following to make Jim's points =
below clearer to non-expert readers:

"The specific identifiers used to tie the key derivation to the sender (Par=
ty U) and the receiver (Party V) are application specific and beyond the sc=
ope of this specification."

                                                            -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Saturday, June 22, 2013 2:29 PM
To: 'Richard Barnes'; Mike Jones
Cc: 'Russ Housley'; 'Manger, James H'; jose@ietf.org
Subject: RE: [jose] Concat KDF

This does not also answer the question of how entities are going to be name=
d in JOSE.  It is easy to do in TLS and for PKIX because there are always n=
ames for them.  This is not a feature of JOSE, we don't name people that is=
 left for applications.  Also if one looks at it, then we should not need t=
o send this information in the message because each party would know the na=
mes of both entities.

Having read the rational for using identifiers, it is not clear that there =
is anything in the rational that applies to JOSE in any case.  Given that w=
e are doing ephemeral-static dh, there is no way for a shared key attack to=
 occur in the case of a store and forward message.

There is a possibility that it could occur for the case of XMPP where one i=
s separating the key management from the key usage, but it is not a general=
 case problem.

If we are going to be in a situation where we don't know the names of the e=
ntities - unless the application somehow finds them out, makes them common =
 and then tells the application what they are there is no reason not to use=
 fixed constants.  I don't know what the benefit is going to be for saying,=
 in the message, that for the purposes of this message "Your name is Fred".

Jim


From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Saturday, June 22, 2013 12:27 PM
To: Mike Jones
Cc: Jim Schaad; Russ Housley; Manger, James H; jose@ietf.org<mailto:jose@ie=
tf.org>
Subject: Re: [jose] Concat KDF

Don't think that quite answers the mail.  The algorithm text is correct.  H=
owever, SP800-56A still says that both PartyUInfo and PartyVInfo MUST NOT b=
e empty.  So setting them to zero-length octet strings is non-compliant.  T=
here needs to be something there in any case.  And this still seems abusive=
 of SP800-56A.

I also think your assertion that Concat is a "widely supported KDF" is rath=
er thinly supported.  IIRC, your algorithm support spreadsheet from earlier=
 showed that BCryptDeriveKey was the *only* known implementation of Concat.=
  StackOverflow seems to agree, and NIST has a special "800-56A EXCEPT KDF"=
 category because that's apparently what everything does.
<http://stackoverflow.com/questions/10879658/existing-implementations-for-n=
ist-sp-800-56a-concatenation-key-derivation-functi>
<http://csrc.nist.gov/groups/STM/cavp/documents/components/componentval.htm=
l>

So I don't think support is really a reason to prefer Concat.  Pretty much =
everyone is going to have to implement either KDF from scratch anyway (usin=
g concatenation and a hash function), so we might as well choose one that (=
1) has some history in the IETF (so there's at least some code in CMS libra=
ries), and (2) doesn't have to be used with inappropriate semantics.

--Richard






On Fri, Jun 21, 2013 at 8:45 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:

I agree with James' conclusion that the -11 use of the Concat KDF doesn't c=
onform to SP 800-56A because it doesn't support the PartyVInfo parameter.  =
I believe that DISCUSS comments will result if we don't enable conforming u=
ses of Concat.  Therefore, I propose to make these specific changes relativ=
e to -11.



1.  Revert the PartyUInfo and PartyVInfo language to the -10 text, which wa=
s:
PartyUInfo
The PartyUInfo value is of the form Datalen || Data, where Data is a variab=
le-length string of zero or more octets, and Datalen is a fixed-length, big=
 endian 32 bit counter that indicates the length (in octets) of Data, with =
|| being concatenation. If an apu (agreement PartyUInfo) header parameter i=
s present, Data is set to the result of base64url decoding the apu value an=
d Datalen is set to the number of octets in Data. Otherwise, Datalen is set=
 to 0 and Data is set to the empty octet sequence.
PartyVInfo
The PartyVInfo value is of the form Datalen || Data, where Data is a variab=
le-length string of zero or more octets, and Datalen is a fixed-length, big=
 endian 32 bit counter that indicates the length (in octets) of Data, with =
|| being concatenation. If an apv (agreement PartyVInfo) header parameter i=
s present, Data is set to the result of base64url decoding the apv value an=
d Datalen is set to the number of octets in Data. Otherwise, Datalen is set=
 to 0 and Data is set to the empty octet sequence.



2.  Change the AlgorithmID language to:
AlgorithmID
This is set to the octets of the UTF-8 representation of the alg header par=
ameter value when in the Key Agreement with Key Wrapping mode and to the oc=
tets of the UTF-8 representation of the enc header parameter value when in =
the Direct Key Agreement mode.



3.  Attempting to accommodate what I believe are Jim's and Richard's desire=
 to align with CMS's key derivation practices, I would add the following pa=
ragraph:


The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation fu=
nction similar to the Concat KDF, but with fewer parameters.  Rather than h=
aving separate PartyUInfo and PartyVInfo parameters, it uses a single Party=
AInfo parameter, which is a random string provided by the sender, that cont=
ains 512 bits of information, when provided.  It has no suppPrivInfo parame=
ter.  Key agreement can be performed in a manner akin to RFC 2631 by using =
the PartyAInfo value as the "apu" (Agreement PartyUInfo) header parameter v=
alue, when provided, and by using no "apv" (Agreement PartyVInfo) header pa=
rameter.



Will those changes, collectively, satisfy all those who have been commentin=
g on this thread?  If they will not, please supply specific alternative tex=
t.  Jim, Russ, James, and Richard - what say ye?



                                                                -- Mike



-----Original Message-----
From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Mike Jones
Sent: Friday, June 21, 2013 4:22 PM
To: Manger, James H; Richard Barnes; Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Concat KDF



Thanks for the suggestion of using the RFC 5008 KDF.  I did some research i=
nto this, hoping to find that it was equivalent to the Concat KDF with a su=
itable OtherInfo value, and unfortunately, found that the two are incompati=
ble.  The reason they're incompatible is that RFC 5008 computes this hash:

                KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo ) whereas =
Concat computes this hash:

                K(i) =3D H(counter || Z || OtherInfo)



If the order of "counter" and "Z" were this same, an implementation of Conc=
at could be used to do the RFC 5008 computation, but because the order is d=
ifferent, unfortunately it can't.



The reason that this matters is we need to use a widely-supported KDF to ac=
hieve the JOSE deployability and interoperability goals.  When the original=
 choice was made to use Concat, it was based upon looking into what KDFs we=
re already widely supported in libraries, and Concat looked like the best c=
hoice.



Using Windows as an example, if you look at the BCryptDeriveKey function at=
 http://msdn.microsoft.com/en-us/library/windows/desktop/aa375393(v=3Dvs.85=
).aspx, you'll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported =
KDF functions but that the RFC 5008 function isn't.  (Yes, for key lengths =
only requiring a single has computation, you could probably fake it with BC=
RYPT_KDF_HASH, but this wouldn't work for key lengths requiring multiple ha=
sh computations.)  The same problem is likely to appear on other platforms.



Using XML Encryption as a litmus test for what KDF algorithms are likely to=
 be widely supported gives the same conclusion - http://www.w3.org/TR/xmlen=
c-core1/#sec-Alg-KeyDerivation describes support only for Concat and PBKDF2=
.



Thus, while I appreciate the suggestion, and I did seriously investigate it=
, I don't think it's practical to move away from using the SP 800-56A Conca=
t KDF.  That then established, I think that the task then before us is to d=
ecide exactly how to use it.  That will be the subject of a subsequent mess=
age.



                                                                -- Mike



-----Original Message-----

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Manger, James H

Sent: Thursday, June 20, 2013 6:50 PM

To: Richard Barnes; Jim Schaad

Cc: jose@ietf.org<mailto:jose@ietf.org>

Subject: Re: [jose] Concat KDF



> PartyUInfo seems compliant with the letter of the SP800-56A. SP800-56A

> doesn't place any constraints on the form or duration of the

> identifier ID_U, so the 512-bit value provided seems sufficient if you

> regard that as ID_U.



One aspect that has been confusing me is whether the recipient is expected =
to recognize ID_U as a known identifier for the originator, and ID_V as its=
 own name?



Alternatively, do requirements on these items only apply to the originator?=
 Is it completely safe for a recipient to treat ID_U and ID_V as opaque byt=
es to be hashed as part of the KDF, but with no other processing? Is it, in=
 fact, safe for a recipient to treat OtherInfo (AlgorithmID + PartyUInfo +.=
..) as an opaque blob, or even OtherInput (keydatalen + OtherInfo) as an op=
aque blob? In which case, we could simply include B64(OtherInput) in a JOSE=
 message, perhaps with a suggested way an originator could construct OtherI=
nput (eg from alg, enc, kid/jku, nonce).





> The better option would be to use the same KDF that CMS uses

> [RFC3278][SEC1].  It's simpler, and also complies with USG mandates

> (Suite B [RFC5008]).  If we use the RFC 5008 variant, it also takes as

> input exactly what the current JWS spec provides:

>

> KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo )

>

> ECC-CMS-SharedInfo =3D {

>     keyInfo, // The algorithm with which the key will be used,

> currently in AlgorithmID

>     entityUInfo, // The entropy source we're currently putting in

> PartyUInfo

>     suppPubInfo // The derived key length, currently in SuppPubInfo }

>

> In other words, CMS does exactly what JWS wants to do now.  Let's just

> do it for real.  Proposed text for Section 4.7.1 of JWA:



Your proposal is "logically" the same as CMS (so same security properties),=
 but the precise calculation is incompatible as you don't use a DER-encodin=
g of ECC-CMS-SharedInfo. Just wanted to clarify this intention.



> """

> The key derivation process derives the agreed upon key from the shared

> secret Z established through the ECDH algorithm using the single-pass

> KDF defined in [SEC1].  The inputs to the key derivation process are

> as

> follows:

>

> Z This is set to the representation of the shared secret Z as an octet

> sequence.

>

> SharedInfo This is set to the concatenation of the following octet

> strings, in order:

>    1. The algorithm with which the derived key is to be used.  If the

> "alg" value is "ECDH", then this field contains the value of the "alg"

> parameter.  Otherwise, it contains the value of the "enc" parameter.



Wrong way around. If "alg" is "ECDH" use "enc" value, otherwise use "alg" v=
alue.



You also need to separate this field from the next: with a length prefix, o=
r separator char/byte.

With 2 variable-sized fields (algorithm and apu) you only theoretically nee=
d 1 length field to be unambiguous, but it needs to be at the start or end,=
 not in between the 2 fields.



>    2. The length of the value of the "apu" parameter, as a 32-bit big

> endian integer.  If the "apu" parameter is not present, then this

> field is set to all zeros (0x00000000).

>    3. The value of the "apu" parameter, if present.  If provided, this

> value MUST contain at least 512 bits and a unique value SHOULD be used

> for each recipient.  The "apu" parameter MAY be omitted only if a

> different ephemeral key is used for each key agreement transaction.

>    4. The length of the derived key, as a 32-bit big endian integer.

>  For "ECDH-ES", this is length of the key used by the "enc" algorithm.

>  For "ECDH-ES+A128KW" or "ECDH-ES+A256KW", it is 128 (0x00000080) or

> 256 (0x00000100), respectively.



Symmetric key lengths are hardwired into "alg" and "enc" values in JOSE (eg=
 "A256KW", "A128CGM") so we don't actually need a separate field.



> """

>

> Two side notes:

> 1. We need hash agility here (as in RFC 5008) to be able to meet

> higher levels of security for which SHA-256 is unacceptable.  Suggest

> adding hash algorithms to the ECDH algorithm identifiers, e.g.,

> "ECDH256", "ECDH284+KW".



"ECDH256", "ECDH256+A128KW", "ECDH384", "ECH384+A192KW"?



> 2. The "-ES" is unnecessary, since the entropy added in entityUInfo is

> sufficient to address both ES and SS cases.





--

James Manger

_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose

_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B168042967394367888C47TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I can add a sentence alon=
g the lines of the following to make Jim&#8217;s points below clearer to no=
n-expert readers:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;The specific ident=
ifiers used to tie the key derivation to the sender (Party U) and the recei=
ver (Party V) are application specific and beyond the scope of
 this specification.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Saturday, June 22, 2013 2:29 PM<br>
<b>To:</b> 'Richard Barnes'; Mike Jones<br>
<b>Cc:</b> 'Russ Housley'; 'Manger, James H'; jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This does not also answer=
 the question of how entities are going to be named in JOSE.&nbsp; It is ea=
sy to do in TLS and for PKIX because there are always names for
 them.&nbsp; This is not a feature of JOSE, we don&#8217;t name people that=
 is left for applications.&nbsp; Also if one looks at it, then we should no=
t need to send this information in the message because each party would kno=
w the names of both entities.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Having read the rational =
for using identifiers, it is not clear that there is anything in the ration=
al that applies to JOSE in any case. &nbsp;Given that we are
 doing ephemeral-static dh, there is no way for a shared key attack to occu=
r in the case of a store and forward message.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There is a possibility th=
at it could occur for the case of XMPP where one is separating the key mana=
gement from the key usage, but it is not a general case
 problem.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If we are going to be in =
a situation where we don&#8217;t know the names of the entities &#8211; unl=
ess the application somehow finds them out, makes them common&nbsp; and the=
n
 tells the application what they are there is no reason not to use fixed co=
nstants.&nbsp; I don&#8217;t know what the benefit is going to be for sayin=
g, in the message, that for the purposes of this message &#8220;Your name i=
s Fred&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [<a href=3D"mailto:rlb@ipv.sx">mailto:rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Saturday, June 22, 2013 12:27 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; Russ Housley; Manger, James H; <a href=3D"mailto:jos=
e@ietf.org">
jose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Don't think that quite answers the mail. &nbsp;The a=
lgorithm text is correct. &nbsp;However, SP800-56A still says that both Par=
tyUInfo and PartyVInfo MUST NOT be empty. &nbsp;So setting them to zero-len=
gth octet strings is non-compliant. &nbsp;There needs
 to be something there in any case. &nbsp;And this still seems abusive of S=
P800-56A.&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I also think your assertion that Concat is a &quot;w=
idely supported KDF&quot; is rather thinly supported. &nbsp;IIRC, your algo=
rithm support spreadsheet from earlier showed that BCryptDeriveKey was the =
*only* known implementation of Concat. &nbsp;StackOverflow
 seems to agree, and NIST has a special &quot;800-56A EXCEPT KDF&quot; cate=
gory because that's apparently what everything does.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://stackoverflow.com/questions/10=
879658/existing-implementations-for-nist-sp-800-56a-concatenation-key-deriv=
ation-functi">http://stackoverflow.com/questions/10879658/existing-implemen=
tations-for-nist-sp-800-56a-concatenation-key-derivation-functi</a>&gt;<o:p=
></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&lt;<a href=3D"http://csrc.nist.gov/groups/STM/cavp/=
documents/components/componentval.html">http://csrc.nist.gov/groups/STM/cav=
p/documents/components/componentval.html</a>&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">So I don't think support is really a reason to prefe=
r Concat. &nbsp;Pretty much everyone is going to have to implement either K=
DF from scratch anyway (using concatenation and a hash function), so we mig=
ht as well choose one that (1) has some
 history in the IETF (so there's at least some code in CMS libraries), and =
(2) doesn't have to be used with inappropriate semantics.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 21, 2013 at 8:45 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p>I agree with James' conclusion that the -11 use of the Concat KDF doesn'=
t conform to SP 800-56A because it doesn't support the PartyVInfo parameter=
.&nbsp; I believe that DISCUSS comments will result if we don't enable conf=
orming uses of Concat.&nbsp; Therefore, I
 propose to make these specific changes relative to -11.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>1.&nbsp; Revert the PartyUInfo and PartyVInfo language to the -10 text, =
which was:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">PartyUInfo</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:96.0pt">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">The PartyUInfo value is of the form Datalen || Data, where Data is =
a variable-length string of zero or more octets, and Datalen is a fixed-len=
gth, big endian 32 bit counter that indicates the length
 (in octets) of Data, with || being concatenation. If an </span><span lang=
=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color:#003366">apu</sp=
an><span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-se=
rif&quot;"> (agreement PartyUInfo) header parameter is present, Data is
 set to the result of base64url decoding the </span><span lang=3D"EN" style=
=3D"font-family:&quot;Courier New&quot;;color:#003366">apu</span><span lang=
=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;"> v=
alue and Datalen is set to the number of octets in Data. Otherwise, Datalen
 is set to 0 and Data is set to the empty octet sequence. </span><o:p></o:p=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">PartyVInfo</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:96.0pt">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">The PartyVInfo value is of the form Datalen || Data, where Data is =
a variable-length string of zero or more octets, and Datalen is a fixed-len=
gth, big endian 32 bit counter that indicates the length
 (in octets) of Data, with || being concatenation. If an </span><span lang=
=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color:#003366">apv</sp=
an><span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-se=
rif&quot;"> (agreement PartyVInfo) header parameter is present, Data is
 set to the result of base64url decoding the </span><span lang=3D"EN" style=
=3D"font-family:&quot;Courier New&quot;;color:#003366">apv</span><span lang=
=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;"> v=
alue and Datalen is set to the number of octets in Data. Otherwise, Datalen
 is set to 0 and Data is set to the empty octet sequence. </span><o:p></o:p=
></p>
<p>&nbsp;<o:p></o:p></p>
<p>2.&nbsp; Change the AlgorithmID language to:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">AlgorithmID</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:96.0pt">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">This is set to the octets of the UTF-8 representation of the
</span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quot;;color=
:#003366">alg</span><span lang=3D"EN" style=3D"font-family:&quot;Verdana&qu=
ot;,&quot;sans-serif&quot;"> header parameter value when in the Key Agreeme=
nt with Key Wrapping mode and to the octets of the UTF-8 representation
 of the </span><span lang=3D"EN" style=3D"font-family:&quot;Courier New&quo=
t;;color:#003366">enc</span><span lang=3D"EN" style=3D"font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;"> header parameter value when in the Dir=
ect Key Agreement mode.</span><o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>3.&nbsp; Attempting to accommodate what I believe are Jim&#8217;s and Ri=
chard&#8217;s desire to align with CMS&#8217;s key derivation practices, I =
would add the following paragraph:<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span lang=3D"EN" style=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif=
&quot;">The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key deriv=
ation function similar to the Concat KDF, but with fewer parameters.&nbsp; =
Rather than having separate PartyUInfo and PartyVInfo parameters,
 it uses a single PartyAInfo parameter, which is a random string provided b=
y the sender, that contains 512 bits of information, when provided.&nbsp; I=
t has no suppPrivInfo parameter.&nbsp; Key agreement can be performed in a =
manner akin to RFC 2631 by using the PartyAInfo
 value as the &#8220;apu&#8221; (Agreement PartyUInfo) header parameter val=
ue, when provided, and by using no &#8220;apv&#8221; (Agreement PartyVInfo)=
 header parameter.</span><o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Will those changes, collectively, satisfy all those who have been commen=
ting on this thread?&nbsp; If they will not, please supply specific alterna=
tive text.&nbsp;
<span style=3D"color:red">Jim, Russ, James, and Richard</span> &#8211; what=
 say ye?<o:p></o:p></p>
<p><span style=3D"color:#888888">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"color:#888888">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<div>
<div>
<p>&nbsp;<o:p></o:p></p>
<p>-----Original Message-----<br>
From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"=
_blank">jose-bounces@ietf.org</a>] On Behalf Of Mike Jones<br>
Sent: Friday, June 21, 2013 4:22 PM<br>
To: Manger, James H; Richard Barnes; Jim Schaad<br>
Cc: <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br=
>
Subject: Re: [jose] Concat KDF<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Thanks for the suggestion of using the RFC 5008 KDF.&nbsp; I did some re=
search into this, hoping to find that it was equivalent to the Concat KDF w=
ith a suitable OtherInfo value, and unfortunately, found that the two are i=
ncompatible.&nbsp; The reason they're incompatible
 is that RFC 5008 computes this hash:<o:p></o:p></p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo ) where=
as Concat computes this hash:<o:p></o:p></p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; K(i) =3D H(counter || Z || OtherInfo)<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>If the order of &quot;counter&quot; and &quot;Z&quot; were this same, an=
 implementation of Concat could be used to do the RFC 5008 computation, but=
 because the order is different, unfortunately it can't.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>The reason that this matters is we need to use a widely-supported KDF to=
 achieve the JOSE deployability and interoperability goals.&nbsp; When the =
original choice was made to use Concat, it was based upon looking into what=
 KDFs were already widely supported in
 libraries, and Concat looked like the best choice.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Using Windows as an example, if you look at the BCryptDeriveKey function=
 at <a href=3D"http://msdn.microsoft.com/en-us/library/windows/desktop/aa37=
5393(v=3Dvs.85).aspx" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://msdn.microsoft=
.com/en-us/library/windows/desktop/aa375393(v=3Dvs.85).aspx</span></a>, you=
'll see that BCRYPT_KDF_SP80056A_CONCAT is one of the supported KDF functio=
ns but that the RFC 5008 function isn't.&nbsp;
 (Yes, for key lengths only requiring a single has computation, you could p=
robably fake it with BCRYPT_KDF_HASH, but this wouldn't work for key length=
s requiring multiple hash computations.)&nbsp; The same problem is likely t=
o appear on other platforms.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Using XML Encryption as a litmus test for what KDF algorithms are likely=
 to be widely supported gives the same conclusion -
<a href=3D"http://www.w3.org/TR/xmlenc-core1/#sec-Alg-KeyDerivation" target=
=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">http://www.w3.org/TR/=
xmlenc-core1/#sec-Alg-KeyDerivation</span></a> describes support only for C=
oncat and PBKDF2.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Thus, while I appreciate the suggestion, and I did seriously investigate=
 it, I don't think it's practical to move away from using the SP 800-56A Co=
ncat KDF.&nbsp; That then established, I think that the task then before us=
 is to decide exactly how to use it.&nbsp;
 That will be the subject of a subsequent message.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; -- Mike<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>-----Original Message-----<o:p></o:p></p>
<p>From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank"><span s=
tyle=3D"color:windowtext;text-decoration:none">jose-bounces@ietf.org</span>=
</a> [<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank"><span styl=
e=3D"color:windowtext;text-decoration:none">mailto:jose-bounces@ietf.org</s=
pan></a>]
 On Behalf Of Manger, James H<o:p></o:p></p>
<p>Sent: Thursday, June 20, 2013 6:50 PM<o:p></o:p></p>
<p>To: Richard Barnes; Jim Schaad<o:p></o:p></p>
<p>Cc: <a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"co=
lor:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></p=
>
<p>Subject: Re: [jose] Concat KDF<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; PartyUInfo seems compliant with the letter of the SP800-56A. SP800-=
56A <o:p>
</o:p></p>
<p>&gt; doesn't place any constraints on the form or duration of the <o:p><=
/o:p></p>
<p>&gt; identifier ID_U, so the 512-bit value provided seems sufficient if =
you <o:p>
</o:p></p>
<p>&gt; regard that as ID_U.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>One aspect that has been confusing me is whether the recipient is expect=
ed to recognize ID_U as a known identifier for the originator, and ID_V as =
its own name?<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Alternatively, do requirements on these items only apply to the originat=
or? Is it completely safe for a recipient to treat ID_U and ID_V as opaque =
bytes to be hashed as part of the KDF, but with no other processing? Is it,=
 in fact, safe for a recipient to
 treat OtherInfo (AlgorithmID &#43; PartyUInfo &#43;...) as an opaque blob,=
 or even OtherInput (keydatalen &#43; OtherInfo) as an opaque blob? In whic=
h case, we could simply include B64(OtherInput) in a JOSE message, perhaps =
with a suggested way an originator could construct
 OtherInput (eg from alg, enc, kid/jku, nonce).<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; The better option would be to use the same KDF that CMS uses <o:p><=
/o:p></p>
<p>&gt; [RFC3278][SEC1]. &nbsp;It's simpler, and also complies with USG man=
dates <o:p></o:p></p>
<p>&gt; (Suite B [RFC5008]). &nbsp;If we use the RFC 5008 variant, it also =
takes as <o:p>
</o:p></p>
<p>&gt; input exactly what the current JWS spec provides:<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; KM =3D Hash ( Z || Counter || ECC-CMS-SharedInfo )<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; ECC-CMS-SharedInfo =3D {<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp; keyInfo, // The algorithm with which the key will be =
used, <o:p></o:p></p>
<p>&gt; currently in AlgorithmID<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp; entityUInfo, // The entropy source we're currently pu=
tting in <o:p></o:p></p>
<p>&gt; PartyUInfo<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp; suppPubInfo // The derived key length, currently in&n=
bsp;SuppPubInfo }<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; In other words, CMS does exactly what JWS wants to do now. &nbsp;Le=
t's just <o:p>
</o:p></p>
<p>&gt; do it for real. &nbsp;Proposed text for Section 4.7.1 of JWA:<o:p><=
/o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Your proposal is &quot;logically&quot; the same as CMS (so same security=
 properties), but the precise calculation is incompatible as you don't use =
a DER-encoding of ECC-CMS-SharedInfo. Just wanted to clarify this intention=
.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; &quot;&quot;&quot;<o:p></o:p></p>
<p>&gt; The key derivation process derives the agreed upon key from the sha=
red <o:p>
</o:p></p>
<p>&gt; secret Z established through the ECDH algorithm using the single-pa=
ss <o:p></o:p></p>
<p>&gt; KDF defined in [SEC1]. &nbsp;The inputs to the key derivation proce=
ss are <o:p></o:p></p>
<p>&gt; as<o:p></o:p></p>
<p>&gt; follows:<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; Z This is set to the representation of the shared secret Z as an oc=
tet <o:p>
</o:p></p>
<p>&gt; sequence.<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; SharedInfo This is set to the concatenation of the following octet =
<o:p></o:p></p>
<p>&gt; strings, in order:<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp;1. The algorithm with which the derived key is to be u=
sed. &nbsp;If the <o:p></o:p></p>
<p>&gt; &quot;alg&quot; value is &quot;ECDH&quot;, then this field contains=
 the value of the &quot;alg&quot;<o:p></o:p></p>
<p>&gt; parameter. &nbsp;Otherwise, it contains the value of the &quot;enc&=
quot; parameter.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Wrong way around. If &quot;alg&quot; is &quot;ECDH&quot; use &quot;enc&q=
uot; value, otherwise use &quot;alg&quot; value.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>You also need to separate this field from the next: with a length prefix=
, or separator char/byte.<o:p></o:p></p>
<p>With 2 variable-sized fields (algorithm and apu) you only theoretically =
need 1 length field to be unambiguous, but it needs to be at the start or e=
nd, not in between the 2 fields.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp;2. The length of the value of the &quot;apu&quot; para=
meter, as a 32-bit big <o:p></o:p></p>
<p>&gt; endian integer. &nbsp;If the &quot;apu&quot; parameter is not prese=
nt, then this <o:p></o:p></p>
<p>&gt; field is set to all zeros (0x00000000).<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp;3. The value of the &quot;apu&quot; parameter, if pres=
ent. &nbsp;If provided, this <o:p>
</o:p></p>
<p>&gt; value MUST contain at least 512 bits and a unique value SHOULD be u=
sed <o:p>
</o:p></p>
<p>&gt; for each recipient. &nbsp;The &quot;apu&quot; parameter MAY be omit=
ted only if a <o:p></o:p></p>
<p>&gt; different ephemeral key is used for each key agreement transaction.=
<o:p></o:p></p>
<p>&gt; &nbsp; &nbsp;4. The length of the derived key, as a 32-bit big endi=
an integer.<o:p></o:p></p>
<p>&gt; &nbsp;For &quot;ECDH-ES&quot;, this is length of the key used by th=
e &quot;enc&quot; algorithm.<o:p></o:p></p>
<p>&gt; &nbsp;For &quot;ECDH-ES&#43;A128KW&quot; or &quot;ECDH-ES&#43;A256K=
W&quot;, it is 128 (0x00000080) or<o:p></o:p></p>
<p>&gt; 256 (0x00000100), respectively.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>Symmetric key lengths are hardwired into &quot;alg&quot; and &quot;enc&q=
uot; values in JOSE (eg &quot;A256KW&quot;, &quot;A128CGM&quot;) so we don'=
t actually need a separate field.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; &quot;&quot;&quot;<o:p></o:p></p>
<p>&gt; <o:p></o:p></p>
<p>&gt; Two side notes:<o:p></o:p></p>
<p>&gt; 1. We need hash agility here (as in RFC 5008) to be able to meet <o=
:p></o:p></p>
<p>&gt; higher levels of security for which SHA-256 is unacceptable. &nbsp;=
Suggest <o:p></o:p></p>
<p>&gt; adding hash algorithms to the ECDH algorithm identifiers, e.g., <o:=
p></o:p></p>
<p>&gt; &quot;ECDH256&quot;, &quot;ECDH284&#43;KW&quot;.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&quot;ECDH256&quot;, &quot;ECDH256&#43;A128KW&quot;, &quot;ECDH384&quot;=
, &quot;ECH384&#43;A192KW&quot;?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; <o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&gt; 2. The &quot;-ES&quot; is unnecessary, since the entropy added in e=
ntityUInfo is <o:p>
</o:p></p>
<p>&gt; sufficient to address both ES and SS cases.<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
<p>--<o:p></o:p></p>
<p>James Manger<o:p></o:p></p>
<p>_______________________________________________<o:p></o:p></p>
<p>jose mailing list<o:p></o:p></p>
<p><a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"color:=
windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></p>
<p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/jose</span></a><o:p></o:p></p>
<p>_______________________________________________<o:p></o:p></p>
<p>jose mailing list<o:p></o:p></p>
<p><a href=3D"mailto:jose@ietf.org" target=3D"_blank"><span style=3D"color:=
windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></p>
<p><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://www.ietf.org=
/mailman/listinfo/jose</span></a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367888C47TK5EX14MBXC283r_--

From housley@vigilsec.com  Sun Jun 23 07:43:28 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E953021F9D84 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 07:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krioYykFSYKn for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 07:43:22 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 81A2F21F9C1E for <jose@ietf.org>; Sun, 23 Jun 2013 07:43:22 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 0E6A0F24072; Sun, 23 Jun 2013 10:43:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id anDMKV22ZKXE; Sun, 23 Jun 2013 10:43:19 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 318B8F24070; Sun, 23 Jun 2013 10:43:28 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-13-701891147
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sun, 23 Jun 2013 10:43:18 -0400
Message-Id: <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1085)
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 23 Jun 2013 14:43:29 -0000

--Apple-Mail-13-701891147
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Mike:

> I can add a sentence along the lines of the following to make Jim=92s =
points below clearer to non-expert readers:
> =20
> =93The specific identifiers used to tie the key derivation to the =
sender (Party U) and the receiver (Party V) are application specific and =
beyond the scope of this specification.=94

I see the attraction of this approach, but I wonder if it would be =
possible to also include some advice to applications that make use of =
JOSE.

If the parties that are trying to form a pairwise key make different =
assumptions, then we do not get interoperability.  I am just trying to =
improve the likelihood of interoperability.

Russ


--Apple-Mail-13-701891147
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>Mike:</div><br class=3D"Apple-interchange-newline"><blockquote=
 type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-right: 0in; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; margin-top: 0in; =
margin-bottom: 0.0001pt; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">I can add a sentence =
along the lines of the following to make Jim=92s points below clearer to =
non-expert readers:<o:p></o:p></span></div><div style=3D"margin-right: =
0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-right: 0in; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; margin-top: 0in; margin-bottom: =
0.0001pt; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">=93The specific identifiers used =
to tie the key derivation to the sender (Party U) and the receiver =
(Party V) are application specific and beyond the scope of this =
specification.=94</span></div></div></div></span></blockquote><br></div><d=
iv>I see the attraction of this approach, but I wonder if it would be =
possible to also include some advice to applications that make use of =
JOSE.</div><div><br></div><div>If the parties that are trying to form a =
pairwise key make different assumptions, then we do not get =
interoperability. &nbsp;I am just trying to improve the likelihood of =
interoperability.</div><div><br></div><div>Russ</div><div><br></div></body=
></html>=

--Apple-Mail-13-701891147--

From Michael.Jones@microsoft.com  Sun Jun 23 14:56:58 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C59421F9EF0 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 14:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2R-TYCldnlx for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 14:56:52 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2CF21F924A for <jose@ietf.org>; Sun, 23 Jun 2013 14:56:51 -0700 (PDT)
Received: from BY2FFO11FD015.protection.gbl (10.1.15.204) by BY2FFO11HUB023.protection.gbl (10.1.14.110) with Microsoft SMTP Server (TLS) id 15.0.707.0; Sun, 23 Jun 2013 21:56:46 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD015.mail.protection.outlook.com (10.1.14.131) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Sun, 23 Jun 2013 21:56:46 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Sun, 23 Jun 2013 21:56:44 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Russ Housley <housley@vigilsec.com>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkgAALrZmAAKEYUAAAEQbmAAAFAjDAAIuENAAAPAwIw
Date: Sun, 23 Jun 2013 21:56:43 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com> <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com>
In-Reply-To: <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436788B908TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(54094003)(377454003)(189002)(44976004)(54356001)(76482001)(50986001)(53806001)(59766001)(65816001)(19300405004)(81342001)(20776003)(56776001)(47446002)(47736001)(4396001)(55846006)(6806003)(66066001)(16236675002)(71186001)(79102001)(51856001)(16406001)(74706001)(76796001)(74502001)(46102001)(47976001)(31966008)(74662001)(33656001)(512954002)(49866001)(63696002)(69226001)(54316002)(15202345003)(77096001)(80022001)(81542001)(56816003)(74366001)(77982001)(76786001)(74876001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB023; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08864C38AC
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 23 Jun 2013 21:56:58 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436788B908TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Good idea, Russ.  How about this?

"In the general case, the specific identifiers used to tie the key derivati=
on to the sender (Party U) and the receiver (Party V) are application speci=
fic and beyond the scope of this specification.  As an illustration of one =
possible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications =
might specify that the "iss" (issuer) value be used as the "apu" value and =
the primary "aud" (audience) value be used as the "apv' value."

                                                            -- Mike

From: Russ Housley [mailto:housley@vigilsec.com]
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

Mike:


I can add a sentence along the lines of the following to make Jim's points =
below clearer to non-expert readers:

"The specific identifiers used to tie the key derivation to the sender (Par=
ty U) and the receiver (Party V) are application specific and beyond the sc=
ope of this specification."

I see the attraction of this approach, but I wonder if it would be possible=
 to also include some advice to applications that make use of JOSE.

If the parties that are trying to form a pairwise key make different assump=
tions, then we do not get interoperability.  I am just trying to improve th=
e likelihood of interoperability.

Russ


--_000_4E1F6AAD24975D4BA5B16804296739436788B908TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Good idea, Russ.&nbsp; Ho=
w about this?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;In the general cas=
e, the specific identifiers used to tie the key derivation to the sender (P=
arty U) and the receiver (Party V) are application specific and
 beyond the scope of this specification.&nbsp; As an illustration of one po=
ssible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications mi=
ght specify that the &#8220;iss&#8221; (issuer) value be used as the &#8220=
;apu&#8221; value and the primary &#8220;aud&#8221; (audience) value be use=
d
 as the &#8220;apv&#8217; value.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><span style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Russ Hou=
sley [mailto:housley@vigilsec.com]
<br>
<b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Mike:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I can add a sentence alon=
g the lines of the following to make Jim&#8217;s points below clearer to no=
n-expert readers:</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;The specific ident=
ifiers used to tie the key derivation to the sender (Party U) and the recei=
ver (Party V) are application specific and beyond the scope of
 this specification.&#8221;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I see the attraction of this approach, but I wonder =
if it would be possible to also include some advice to applications that ma=
ke use of JOSE.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the parties that are trying to form a pairwise ke=
y make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of interoperability.<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Russ<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436788B908TK5EX14MBXC283r_--

From ietf@augustcellars.com  Sun Jun 23 16:11:45 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4997221F934C for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 16:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.568
X-Spam-Level: 
X-Spam-Status: No, score=-3.568 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9GUjjfLhWME for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 16:11:39 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 632F521F9360 for <jose@ietf.org>; Sun, 23 Jun 2013 16:11:39 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id BF86138EF2; Sun, 23 Jun 2013 16:11:36 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Russ Housley'" <housley@vigilsec.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>	<033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>	<CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>	<4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>	<4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>	<004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>	<4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>	<EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com> <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sun, 23 Jun 2013 16:10:40 -0700
Message-ID: <003901ce7066$e19f9470$a4debd50$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003A_01CE702C.3543F0C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwQJlRGK8ApvD+k8A6jOEoAH71aeeAt8ahgUCiwG8iAGlt3KlAsFOBucCSOBDEAJqvEIyl8FTy5A=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 23 Jun 2013 23:11:45 -0000

This is a multipart message in MIME format.

------=_NextPart_000_003A_01CE702C.3543F0C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I have been thinking about this and I am going to make a different proposal.

 

 

The proposal is as follows:

 

1.        We eliminate the two partyX fields from the specification

2.       We define a new "ID" field which MUST be present for ECDH keys.

3.       We say that you take the ID field from the sender/recipient
respectively and use them in the PartyX fields when doing the KDC.

 

The only down side of this, is that if one has a certificate then we should
use the DER encoded subject name of the certificate but I am not sure how
this would be encoded in the case you have a JWK which contains an x5c
member.  It might be that we will need to defined an ID and an IDb64 field
to allow for a binary ID to be used.

 

There would still need to be a requirement that the ID field be length
prefixed in the discussion.

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Sunday, June 23, 2013 2:57 PM
To: Russ Housley
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Good idea, Russ.  How about this?

 

"In the general case, the specific identifiers used to tie the key
derivation to the sender (Party U) and the receiver (Party V) are
application specific and beyond the scope of this specification.  As an
illustration of one possible usage, when the JWE is a JSON Web Token (JWT)
[JWT], applications might specify that the "iss" (issuer) value be used as
the "apu" value and the primary "aud" (audience) value be used as the "apv'
value."

 

                                                            -- Mike

 

From: Russ Housley [mailto:housley@vigilsec.com] 
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Mike:

 

I can add a sentence along the lines of the following to make Jim's points
below clearer to non-expert readers:

 

"The specific identifiers used to tie the key derivation to the sender
(Party U) and the receiver (Party V) are application specific and beyond the
scope of this specification."

 

I see the attraction of this approach, but I wonder if it would be possible
to also include some advice to applications that make use of JOSE.

 

If the parties that are trying to form a pairwise key make different
assumptions, then we do not get interoperability.  I am just trying to
improve the likelihood of interoperability.

 

Russ

 


------=_NextPart_000_003A_01CE702C.3543F0C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1981686151;
	mso-list-type:hybrid;
	mso-list-template-ids:-266444574 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have been thinking about this and I am going to make a different =
proposal.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The proposal is as follows:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;We eliminate the two partyX fields from the =
specification<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We define a new &#8220;ID&#8221; field which MUST be present for ECDH =
keys.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We say that you take the ID field from the sender/recipient =
respectively and use them in the PartyX fields when doing the =
KDC.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The only down side of this, is that if one has a certificate then we =
should use the DER encoded subject name of the certificate but I am not =
sure how this would be encoded in the case you have a JWK which contains =
an x5c member. &nbsp;It might be that we will need to defined an ID and =
an IDb64 field to allow for a binary ID to be =
used.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There would still need to be a requirement that the ID field be =
length prefixed in the discussion.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of =
</b>Mike Jones<br><b>Sent:</b> Sunday, June 23, 2013 2:57 =
PM<br><b>To:</b> Russ Housley<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: [jose] Concat =
KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Good idea, Russ.&nbsp; How about this?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;In the general case, the specific identifiers used to tie the =
key derivation to the sender (Party U) and the receiver (Party V) are =
application specific and beyond the scope of this specification.&nbsp; =
As an illustration of one possible usage, when the JWE is a JSON Web =
Token (JWT) [JWT], applications might specify that the &#8220;iss&#8221; =
(issuer) value be used as the &#8220;apu&#8221; value and the primary =
&#8220;aud&#8221; (audience) value be used as the &#8220;apv&#8217; =
value.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Russ Housley [<a =
href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</a>] =
<br><b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br><b>To:</b> Mike =
Jones<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>Mike:<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I can add a sentence along the lines of the following to make =
Jim&#8217;s points below clearer to non-expert =
readers:</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;The specific identifiers used to tie the key derivation to the =
sender (Party U) and the receiver (Party V) are application specific and =
beyond the scope of this =
specification.&#8221;</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
see the attraction of this approach, but I wonder if it would be =
possible to also include some advice to applications that make use of =
JOSE.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If the parties that are trying to form a pairwise key =
make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of =
interoperability.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Russ<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_003A_01CE702C.3543F0C0--


From Michael.Jones@microsoft.com  Sun Jun 23 17:25:19 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C617021F9A90 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 17:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N96xvZGqUd7W for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 17:25:13 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id 137E321F9D36 for <jose@ietf.org>; Sun, 23 Jun 2013 17:25:11 -0700 (PDT)
Received: from BY2FFO11FD001.protection.gbl (10.1.15.204) by BY2FFO11HUB034.protection.gbl (10.1.14.118) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 24 Jun 2013 00:25:03 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD001.mail.protection.outlook.com (10.1.14.123) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 24 Jun 2013 00:25:03 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Mon, 24 Jun 2013 00:24:46 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Russ Housley' <housley@vigilsec.com>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkgAALrZmAAKEYUAAAEQbmAAAFAjDAAIuENAAAPAwIwAAK1NAAAAnBasA==
Date: Mon, 24 Jun 2013 00:24:45 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com> <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com> <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com> <003901ce7066$e19f9470$a4debd50$@augustcellars.com>
In-Reply-To: <003901ce7066$e19f9470$a4debd50$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436788BAC9TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(54094003)(199002)(189002)(377454003)(54356001)(46102001)(4396001)(63696002)(59766001)(6806003)(77096001)(49866001)(50986001)(47976001)(66066001)(561944002)(20776003)(512954002)(69226001)(44976004)(74366001)(56816003)(55846006)(74502001)(74706001)(74662001)(65816001)(31966008)(33656001)(80022001)(47446002)(53806001)(79102001)(16406001)(19300405004)(76482001)(16236675002)(74876001)(54316002)(56776001)(76786001)(81342001)(81542001)(76796001)(47736001)(15202345003)(51856001)(71186001)(77982001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB034; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 088751B4D4
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 00:25:19 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436788BAC9TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The problem with that is that we're inventing our own KDF at that point.  T=
he upsides of Concat are that it is known to work, is known to be implement=
ed, and is known to meet NIST and other existing security criteria.  At lea=
st as I see it, we shouldn't give up those advantages without a compelling =
reason to do so.

                                                            -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Sunday, June 23, 2013 4:11 PM
To: Mike Jones; 'Russ Housley'
Cc: jose@ietf.org
Subject: RE: [jose] Concat KDF

I have been thinking about this and I am going to make a different proposal=
.


The proposal is as follows:


1.       We eliminate the two partyX fields from the specification

2.      We define a new "ID" field which MUST be present for ECDH keys.

3.      We say that you take the ID field from the sender/recipient respect=
ively and use them in the PartyX fields when doing the KDC.

The only down side of this, is that if one has a certificate then we should=
 use the DER encoded subject name of the certificate but I am not sure how =
this would be encoded in the case you have a JWK which contains an x5c memb=
er.  It might be that we will need to defined an ID and an IDb64 field to a=
llow for a binary ID to be used.

There would still need to be a requirement that the ID field be length pref=
ixed in the discussion.

Jim


From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Mike Jones
Sent: Sunday, June 23, 2013 2:57 PM
To: Russ Housley
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Concat KDF

Good idea, Russ.  How about this?

"In the general case, the specific identifiers used to tie the key derivati=
on to the sender (Party U) and the receiver (Party V) are application speci=
fic and beyond the scope of this specification.  As an illustration of one =
possible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications =
might specify that the "iss" (issuer) value be used as the "apu" value and =
the primary "aud" (audience) value be used as the "apv' value."

                                                            -- Mike

From: Russ Housley [mailto:housley@vigilsec.com]
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Concat KDF

Mike:

I can add a sentence along the lines of the following to make Jim's points =
below clearer to non-expert readers:

"The specific identifiers used to tie the key derivation to the sender (Par=
ty U) and the receiver (Party V) are application specific and beyond the sc=
ope of this specification."

I see the attraction of this approach, but I wonder if it would be possible=
 to also include some advice to applications that make use of JOSE.

If the parties that are trying to form a pairwise key make different assump=
tions, then we do not get interoperability.  I am just trying to improve th=
e likelihood of interoperability.

Russ


--_000_4E1F6AAD24975D4BA5B16804296739436788BAC9TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1981686151;
	mso-list-type:hybrid;
	mso-list-template-ids:-266444574 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The problem with that is =
that we&#8217;re inventing our own KDF at that point.&nbsp; The upsides of =
Concat are that it is known to work, is known to be implemented, and
 is known to meet NIST and other existing security criteria.&nbsp; At least=
 as I see it, we shouldn&#8217;t give up those advantages without a compell=
ing reason to do so.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Sunday, June 23, 2013 4:11 PM<br>
<b>To:</b> Mike Jones; 'Russ Housley'<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I have been thinking abou=
t this and I am going to make a different proposal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The proposal is as follow=
s:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;We eliminat=
e the two partyX fields from the specification<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We define a new &=
#8220;ID&#8221; field which MUST be present for ECDH keys.<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We say that you t=
ake the ID field from the sender/recipient respectively and use them in the=
 PartyX fields when doing the KDC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The only down side of thi=
s, is that if one has a certificate then we should use the DER encoded subj=
ect name of the certificate but I am not sure how this would
 be encoded in the case you have a JWK which contains an x5c member. &nbsp;=
It might be that we will need to defined an ID and an IDb64 field to allow =
for a binary ID to be used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There would still need to=
 be a requirement that the ID field be length prefixed in the discussion.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Sunday, June 23, 2013 2:57 PM<br>
<b>To:</b> Russ Housley<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Good idea, Russ.&nbsp; Ho=
w about this?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;In the general cas=
e, the specific identifiers used to tie the key derivation to the sender (P=
arty U) and the receiver (Party V) are application specific and
 beyond the scope of this specification.&nbsp; As an illustration of one po=
ssible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications mi=
ght specify that the &#8220;iss&#8221; (issuer) value be used as the &#8220=
;apu&#8221; value and the primary &#8220;aud&#8221; (audience) value be use=
d
 as the &#8220;apv&#8217; value.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Russ Hou=
sley [<a href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</=
a>]
<br>
<b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Mike:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I can add a sentence alon=
g the lines of the following to make Jim&#8217;s points below clearer to no=
n-expert readers:</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;The specific ident=
ifiers used to tie the key derivation to the sender (Party U) and the recei=
ver (Party V) are application specific and beyond the scope of
 this specification.&#8221;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I see the attraction of this approach, but I wonder =
if it would be possible to also include some advice to applications that ma=
ke use of JOSE.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the parties that are trying to form a pairwise ke=
y make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of interoperability.<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Russ<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436788BAC9TK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Sun Jun 23 18:18:28 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A52911E80F3 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 18:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LouRYi6N8KfK for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 18:18:21 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id A252E11E80F0 for <jose@ietf.org>; Sun, 23 Jun 2013 18:18:21 -0700 (PDT)
Received: from BY2FFO11FD020.protection.gbl (10.1.15.201) by BY2FFO11HUB012.protection.gbl (10.1.14.83) with Microsoft SMTP Server (TLS) id 15.0.707.0; Mon, 24 Jun 2013 01:18:20 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD020.mail.protection.outlook.com (10.1.14.137) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Mon, 24 Jun 2013 01:18:20 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Mon, 24 Jun 2013 01:18:20 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Russ Housley' <housley@vigilsec.com>
Thread-Topic: [jose] Concat KDF
Thread-Index: Ac5q+NhbtqGMiV/SQhaOAzsJ13w6TQBc3A2AAGUIioAACEu3gAAsBMkgAALrZmAAKEYUAAAEQbmAAAFAjDAAIuENAAAPAwIwAAK1NAAAAnBasAAB4V2A
Date: Mon, 24 Jun 2013 01:18:19 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436788BBCB@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com> <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com> <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com> <003901ce7066$e19f9470$a4debd50$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436788BBCBTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(377454003)(54094003)(164054003)(66066001)(55846006)(16236675002)(44976004)(77982001)(79102001)(19300405004)(54316002)(20776003)(512954002)(74366001)(71186001)(76482001)(53806001)(16406001)(77096001)(15202345003)(76786001)(56776001)(6806003)(59766001)(47976001)(69226001)(74876001)(47736001)(56816003)(4396001)(31966008)(74706001)(33656001)(63696002)(51856001)(80022001)(47446002)(74662001)(65816001)(81542001)(54356001)(49866001)(81342001)(46102001)(74502001)(76796001)(561944002)(50986001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB012; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 088751B4D4
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 01:18:28 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436788BBCBTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jim - permit me to ask a pair of follow-up questions.  First, what goal are=
 you trying to accomplish in your suggestion below?  I'm wondering if there=
's a way to meet the needs of the use case you have in mind with particular=
 parameter choices with the Concat KDF.

Second, does the proposed text below meet the needs of the use case you hav=
e in mind?

The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation fu=
nction similar to the Concat KDF, but with fewer parameters.  Rather than h=
aving separate PartyUInfo and PartyVInfo parameters, it uses a single Party=
AInfo parameter, which is a random string provided by the sender, that cont=
ains 512 bits of information, when provided.  It has no suppPrivInfo parame=
ter.  Key agreement can be performed in a manner akin to RFC 2631 by using =
the PartyAInfo value as the "apu" (Agreement PartyUInfo) header parameter v=
alue, when provided, and by using no "apv" (Agreement PartyVInfo) header pa=
rameter.

                                                            Thanks,
                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mik=
e Jones
Sent: Sunday, June 23, 2013 5:25 PM
To: Jim Schaad; 'Russ Housley'
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

The problem with that is that we're inventing our own KDF at that point.  T=
he upsides of Concat are that it is known to work, is known to be implement=
ed, and is known to meet NIST and other existing security criteria.  At lea=
st as I see it, we shouldn't give up those advantages without a compelling =
reason to do so.

                                                            -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Sunday, June 23, 2013 4:11 PM
To: Mike Jones; 'Russ Housley'
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Concat KDF

I have been thinking about this and I am going to make a different proposal=
.


The proposal is as follows:


1.       We eliminate the two partyX fields from the specification

2.      We define a new "ID" field which MUST be present for ECDH keys.

3.      We say that you take the ID field from the sender/recipient respect=
ively and use them in the PartyX fields when doing the KDC.

The only down side of this, is that if one has a certificate then we should=
 use the DER encoded subject name of the certificate but I am not sure how =
this would be encoded in the case you have a JWK which contains an x5c memb=
er.  It might be that we will need to defined an ID and an IDb64 field to a=
llow for a binary ID to be used.

There would still need to be a requirement that the ID field be length pref=
ixed in the discussion.

Jim


From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Mike Jones
Sent: Sunday, June 23, 2013 2:57 PM
To: Russ Housley
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Concat KDF

Good idea, Russ.  How about this?

"In the general case, the specific identifiers used to tie the key derivati=
on to the sender (Party U) and the receiver (Party V) are application speci=
fic and beyond the scope of this specification.  As an illustration of one =
possible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications =
might specify that the "iss" (issuer) value be used as the "apu" value and =
the primary "aud" (audience) value be used as the "apv' value."

                                                            -- Mike

From: Russ Housley [mailto:housley@vigilsec.com]
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Concat KDF

Mike:

I can add a sentence along the lines of the following to make Jim's points =
below clearer to non-expert readers:

"The specific identifiers used to tie the key derivation to the sender (Par=
ty U) and the receiver (Party V) are application specific and beyond the sc=
ope of this specification."

I see the attraction of this approach, but I wonder if it would be possible=
 to also include some advice to applications that make use of JOSE.

If the parties that are trying to form a pairwise key make different assump=
tions, then we do not get interoperability.  I am just trying to improve th=
e likelihood of interoperability.

Russ


--_000_4E1F6AAD24975D4BA5B16804296739436788BBCBTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1981686151;
	mso-list-type:hybrid;
	mso-list-template-ids:-266444574 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim &#8211; permit me to =
ask a pair of follow-up questions.&nbsp; First, what goal are you trying to=
 accomplish in your suggestion below?&nbsp; I&#8217;m wondering if there&#8=
217;s a way
 to meet the needs of the use case you have in mind with particular paramet=
er choices with the Concat KDF.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Second, does the proposed=
 text below meet the needs of the use case you have in mind?<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span lang=3D"EN" style=
=3D"font-size:11.0pt;font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;=
;color:black">The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key=
 derivation function similar to the Concat KDF, but with fewer
 parameters.&nbsp; Rather than having separate PartyUInfo and PartyVInfo pa=
rameters, it uses a single PartyAInfo parameter, which is a random string p=
rovided by the sender, that contains 512 bits of information, when provided=
.&nbsp; It has no suppPrivInfo parameter.&nbsp;
 Key agreement can be performed in a manner akin to RFC 2631 by using the P=
artyAInfo value as the &#8220;apu&#8221; (Agreement PartyUInfo) header para=
meter value, when provided, and by using no &#8220;apv&#8221; (Agreement Pa=
rtyVInfo) header parameter.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Sunday, June 23, 2013 5:25 PM<br>
<b>To:</b> Jim Schaad; 'Russ Housley'<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The problem with that is =
that we&#8217;re inventing our own KDF at that point.&nbsp; The upsides of =
Concat are that it is known to work, is known to be implemented, and
 is known to meet NIST and other existing security criteria.&nbsp; At least=
 as I see it, we shouldn&#8217;t give up those advantages without a compell=
ing reason to do so.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [<a href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com=
</a>]
<br>
<b>Sent:</b> Sunday, June 23, 2013 4:11 PM<br>
<b>To:</b> Mike Jones; 'Russ Housley'<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> RE: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I have been thinking abou=
t this and I am going to make a different proposal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The proposal is as follow=
s:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;We eliminat=
e the two partyX fields from the specification<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We define a new &=
#8220;ID&#8221; field which MUST be present for ECDH keys.<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">We say that you t=
ake the ID field from the sender/recipient respectively and use them in the=
 PartyX fields when doing the KDC.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">The only down side of thi=
s, is that if one has a certificate then we should use the DER encoded subj=
ect name of the certificate but I am not sure how this would
 be encoded in the case you have a JWK which contains an x5c member. &nbsp;=
It might be that we will need to defined an ID and an IDb64 field to allow =
for a binary ID to be used.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">There would still need to=
 be a requirement that the ID field be length prefixed in the discussion.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Jim<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Mike Jones<br>
<b>Sent:</b> Sunday, June 23, 2013 2:57 PM<br>
<b>To:</b> Russ Housley<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Good idea, Russ.&nbsp; Ho=
w about this?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;In the general cas=
e, the specific identifiers used to tie the key derivation to the sender (P=
arty U) and the receiver (Party V) are application specific and
 beyond the scope of this specification.&nbsp; As an illustration of one po=
ssible usage, when the JWE is a JSON Web Token (JWT) [JWT], applications mi=
ght specify that the &#8220;iss&#8221; (issuer) value be used as the &#8220=
;apu&#8221; value and the primary &#8220;aud&#8221; (audience) value be use=
d
 as the &#8220;apv&#8217; value.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Russ Hou=
sley [<a href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</=
a>]
<br>
<b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> Re: [jose] Concat KDF<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Mike:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I can add a sentence alon=
g the lines of the following to make Jim&#8217;s points below clearer to no=
n-expert readers:</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;The specific ident=
ifiers used to tie the key derivation to the sender (Party U) and the recei=
ver (Party V) are application specific and beyond the scope of
 this specification.&#8221;</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I see the attraction of this approach, but I wonder =
if it would be possible to also include some advice to applications that ma=
ke use of JOSE.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the parties that are trying to form a pairwise ke=
y make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of interoperability.<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Russ<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436788BBCBTK5EX14MBXC283r_--

From ietf@augustcellars.com  Sun Jun 23 21:08:47 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0770711E8115 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 21:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6nobwf4t0W4 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 21:08:41 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACD711E80A2 for <jose@ietf.org>; Sun, 23 Jun 2013 21:08:40 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id E04A92CA06; Sun, 23 Jun 2013 21:08:39 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Russ Housley'" <housley@vigilsec.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>	<033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>	<CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>	<4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>	<4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>	<004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>	<4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>	<EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com>	<4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com>	<003901ce7066$e19f9470$a4debd50$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B16804296739436788BBCB@TK5EX14MBXC28 3.redmond.corp.microso ft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436788BBCB@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sun, 23 Jun 2013 21:07:43 -0700
Message-ID: <007e01ce7090$60e7d250$22b776f0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007F_01CE7055.B48E7890"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwQJlRGK8ApvD+k8A6jOEoAH71aeeAt8ahgUCiwG8iAGlt3KlAsFOBucCSOBDEAJqvEIyAf1Fom8CzGDghQL0H7ugl4O5llA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 04:08:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_007F_01CE7055.B48E7890
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The goal is simple - meet the requirements of the NIST document.

 

No the text below does not meet the requirements stated above.

 

The text does not contain sufficient information to fully document what is
required to define the KDF function needed.  However, I will be happy using
the 2531 KDF function rather than a NIST one since, as I have previously
stated, the reasons in the NIST document for having the party identifiers is
not one that is required for the store and forward use cases.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Sunday, June 23, 2013 6:18 PM
To: Jim Schaad; 'Russ Housley'
Cc: jose@ietf.org
Subject: RE: [jose] Concat KDF

 

Jim - permit me to ask a pair of follow-up questions.  First, what goal are
you trying to accomplish in your suggestion below?  I'm wondering if there's
a way to meet the needs of the use case you have in mind with particular
parameter choices with the Concat KDF.

 

Second, does the proposed text below meet the needs of the use case you have
in mind?

 

The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key derivation
function similar to the Concat KDF, but with fewer parameters.  Rather than
having separate PartyUInfo and PartyVInfo parameters, it uses a single
PartyAInfo parameter, which is a random string provided by the sender, that
contains 512 bits of information, when provided.  It has no suppPrivInfo
parameter.  Key agreement can be performed in a manner akin to RFC 2631 by
using the PartyAInfo value as the "apu" (Agreement PartyUInfo) header
parameter value, when provided, and by using no "apv" (Agreement PartyVInfo)
header parameter.

 

                                                            Thanks,

                                                            -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Sunday, June 23, 2013 5:25 PM
To: Jim Schaad; 'Russ Housley'
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

The problem with that is that we're inventing our own KDF at that point.
The upsides of Concat are that it is known to work, is known to be
implemented, and is known to meet NIST and other existing security criteria.
At least as I see it, we shouldn't give up those advantages without a
compelling reason to do so.

 

                                                            -- Mike

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Sunday, June 23, 2013 4:11 PM
To: Mike Jones; 'Russ Housley'
Cc: jose@ietf.org
Subject: RE: [jose] Concat KDF

 

I have been thinking about this and I am going to make a different proposal.

 

 

The proposal is as follows:

 

1.        We eliminate the two partyX fields from the specification

2.       We define a new "ID" field which MUST be present for ECDH keys.

3.       We say that you take the ID field from the sender/recipient
respectively and use them in the PartyX fields when doing the KDC.

 

The only down side of this, is that if one has a certificate then we should
use the DER encoded subject name of the certificate but I am not sure how
this would be encoded in the case you have a JWK which contains an x5c
member.  It might be that we will need to defined an ID and an IDb64 field
to allow for a binary ID to be used.

 

There would still need to be a requirement that the ID field be length
prefixed in the discussion.

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Sunday, June 23, 2013 2:57 PM
To: Russ Housley
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Good idea, Russ.  How about this?

 

"In the general case, the specific identifiers used to tie the key
derivation to the sender (Party U) and the receiver (Party V) are
application specific and beyond the scope of this specification.  As an
illustration of one possible usage, when the JWE is a JSON Web Token (JWT)
[JWT], applications might specify that the "iss" (issuer) value be used as
the "apu" value and the primary "aud" (audience) value be used as the "apv'
value."

 

                                                            -- Mike

 

From: Russ Housley [mailto:housley@vigilsec.com] 
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Mike:

 

I can add a sentence along the lines of the following to make Jim's points
below clearer to non-expert readers:

 

"The specific identifiers used to tie the key derivation to the sender
(Party U) and the receiver (Party V) are application specific and beyond the
scope of this specification."

 

I see the attraction of this approach, but I wonder if it would be possible
to also include some advice to applications that make use of JOSE.

 

If the parties that are trying to form a pairwise key make different
assumptions, then we do not get interoperability.  I am just trying to
improve the likelihood of interoperability.

 

Russ

 


------=_NextPart_000_007F_01CE7055.B48E7890
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1981686151;
	mso-list-type:hybrid;
	mso-list-template-ids:-266444574 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The goal is simple &#8211; meet the requirements of the NIST =
document.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>No the text below does not meet the requirements stated =
above.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The text does not contain sufficient information to fully document =
what is required to define the KDF function needed.&nbsp; However, I =
will be happy using the 2531 KDF function rather than a NIST one since, =
as I have previously stated, the reasons in the NIST document for having =
the party identifiers is not one that is required for the store and =
forward use cases.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Sunday, =
June 23, 2013 6:18 PM<br><b>To:</b> Jim Schaad; 'Russ =
Housley'<br><b>Cc:</b> jose@ietf.org<br><b>Subject:</b> RE: [jose] =
Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim &#8211; permit me to ask a pair of follow-up questions.&nbsp; =
First, what goal are you trying to accomplish in your suggestion =
below?&nbsp; I&#8217;m wondering if there&#8217;s a way to meet the =
needs of the use case you have in mind with particular parameter choices =
with the Concat KDF.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Second, does the proposed text below meet the needs of the use case =
you have in mind?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Verdana","sans-serif";color:black'=
>The Diffie-Hellman Key Agreement Method [RFC 2631] uses a key =
derivation function similar to the Concat KDF, but with fewer =
parameters.&nbsp; Rather than having separate PartyUInfo and PartyVInfo =
parameters, it uses a single PartyAInfo parameter, which is a random =
string provided by the sender, that contains 512 bits of information, =
when provided.&nbsp; It has no suppPrivInfo parameter.&nbsp; Key =
agreement can be performed in a manner akin to RFC 2631 by using the =
PartyAInfo value as the &#8220;apu&#8221; (Agreement PartyUInfo) header =
parameter value, when provided, and by using no &#8220;apv&#8221; =
(Agreement PartyVInfo) header parameter.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Mike Jones<br><b>Sent:</b> Sunday, June 23, 2013 =
5:25 PM<br><b>To:</b> Jim Schaad; 'Russ Housley'<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The problem with that is that we&#8217;re inventing our own KDF at =
that point.&nbsp; The upsides of Concat are that it is known to work, is =
known to be implemented, and is known to meet NIST and other existing =
security criteria.&nbsp; At least as I see it, we shouldn&#8217;t give =
up those advantages without a compelling reason to do =
so.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Sunday, June 23, 2013 4:11 PM<br><b>To:</b> Mike =
Jones; 'Russ Housley'<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have been thinking about this and I am going to make a different =
proposal.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The proposal is as follows:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;We eliminate the two partyX fields from the =
specification<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We define a new &#8220;ID&#8221; field which MUST be present for ECDH =
keys.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We say that you take the ID field from the sender/recipient =
respectively and use them in the PartyX fields when doing the =
KDC.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The only down side of this, is that if one has a certificate then we =
should use the DER encoded subject name of the certificate but I am not =
sure how this would be encoded in the case you have a JWK which contains =
an x5c member. &nbsp;It might be that we will need to defined an ID and =
an IDb64 field to allow for a binary ID to be =
used.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There would still need to be a requirement that the ID field be =
length prefixed in the discussion.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Mike Jones<br><b>Sent:</b> Sunday, June 23, 2013 =
2:57 PM<br><b>To:</b> Russ Housley<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Good idea, Russ.&nbsp; How about this?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;In the general case, the specific identifiers used to tie the =
key derivation to the sender (Party U) and the receiver (Party V) are =
application specific and beyond the scope of this specification.&nbsp; =
As an illustration of one possible usage, when the JWE is a JSON Web =
Token (JWT) [JWT], applications might specify that the &#8220;iss&#8221; =
(issuer) value be used as the &#8220;apu&#8221; value and the primary =
&#8220;aud&#8221; (audience) value be used as the &#8220;apv&#8217; =
value.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Russ Housley [<a =
href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</a>] =
<br><b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br><b>To:</b> Mike =
Jones<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>Mike:<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I can add a sentence along the lines of the following to make =
Jim&#8217;s points below clearer to non-expert =
readers:</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;The specific identifiers used to tie the key derivation to the =
sender (Party U) and the receiver (Party V) are application specific and =
beyond the scope of this =
specification.&#8221;</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
see the attraction of this approach, but I wonder if it would be =
possible to also include some advice to applications that make use of =
JOSE.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If the parties that are trying to form a pairwise key =
make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of =
interoperability.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Russ<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_007F_01CE7055.B48E7890--


From ietf@augustcellars.com  Sun Jun 23 21:11:43 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47E2C21F9798 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 21:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level: 
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCuQdAoAv7n4 for <jose@ietfa.amsl.com>; Sun, 23 Jun 2013 21:11:37 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 52C4521F9385 for <jose@ietf.org>; Sun, 23 Jun 2013 21:11:37 -0700 (PDT)
Received: from Philemon (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id C511B2CA06; Sun, 23 Jun 2013 21:11:36 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'Russ Housley'" <housley@vigilsec.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com>	<033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com>	<CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com>	<255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com>	<4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com>	<4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com>	<CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com>	<004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com>	<4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com>	<EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com>	<4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com>	<003901ce7066$e19f9470$a4debd50$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436788BAC9@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sun, 23 Jun 2013 21:10:40 -0700
Message-ID: <008301ce7090$ca547fe0$5efd7fa0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0084_01CE7056.1DF9EDA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwQJlRGK8ApvD+k8A6jOEoAH71aeeAt8ahgUCiwG8iAGlt3KlAsFOBucCSOBDEAJqvEIyAf1Fom8CzGDghZebXGhQ
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 04:11:43 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0084_01CE7056.1DF9EDA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is not implementing a new KDF in any way shape or form.  This is
defining a way to know what the IDs that are to be included in the NIST KDF
function are supposed to be.

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Sunday, June 23, 2013 5:25 PM
To: Jim Schaad; 'Russ Housley'
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

The problem with that is that we're inventing our own KDF at that point.
The upsides of Concat are that it is known to work, is known to be
implemented, and is known to meet NIST and other existing security criteria.
At least as I see it, we shouldn't give up those advantages without a
compelling reason to do so.

 

                                                            -- Mike

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Sunday, June 23, 2013 4:11 PM
To: Mike Jones; 'Russ Housley'
Cc: jose@ietf.org
Subject: RE: [jose] Concat KDF

 

I have been thinking about this and I am going to make a different proposal.

 

 

The proposal is as follows:

 

1.        We eliminate the two partyX fields from the specification

2.       We define a new "ID" field which MUST be present for ECDH keys.

3.       We say that you take the ID field from the sender/recipient
respectively and use them in the PartyX fields when doing the KDC.

 

The only down side of this, is that if one has a certificate then we should
use the DER encoded subject name of the certificate but I am not sure how
this would be encoded in the case you have a JWK which contains an x5c
member.  It might be that we will need to defined an ID and an IDb64 field
to allow for a binary ID to be used.

 

There would still need to be a requirement that the ID field be length
prefixed in the discussion.

 

Jim

 

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Mike
Jones
Sent: Sunday, June 23, 2013 2:57 PM
To: Russ Housley
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Good idea, Russ.  How about this?

 

"In the general case, the specific identifiers used to tie the key
derivation to the sender (Party U) and the receiver (Party V) are
application specific and beyond the scope of this specification.  As an
illustration of one possible usage, when the JWE is a JSON Web Token (JWT)
[JWT], applications might specify that the "iss" (issuer) value be used as
the "apu" value and the primary "aud" (audience) value be used as the "apv'
value."

 

                                                            -- Mike

 

From: Russ Housley [mailto:housley@vigilsec.com] 
Sent: Sunday, June 23, 2013 7:43 AM
To: Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] Concat KDF

 

Mike:

 

I can add a sentence along the lines of the following to make Jim's points
below clearer to non-expert readers:

 

"The specific identifiers used to tie the key derivation to the sender
(Party U) and the receiver (Party V) are application specific and beyond the
scope of this specification."

 

I see the attraction of this approach, but I wonder if it would be possible
to also include some advice to applications that make use of JOSE.

 

If the parties that are trying to form a pairwise key make different
assumptions, then we do not get interoperability.  I am just trying to
improve the likelihood of interoperability.

 

Russ

 


------=_NextPart_000_0084_01CE7056.1DF9EDA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1981686151;
	mso-list-type:hybrid;
	mso-list-template-ids:-266444574 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This is not implementing a new KDF in any way shape or form. =
&nbsp;This is defining a way to know what the IDs that are to be =
included in the NIST KDF function are supposed to =
be.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] <b>On Behalf Of =
</b>Mike Jones<br><b>Sent:</b> Sunday, June 23, 2013 5:25 =
PM<br><b>To:</b> Jim Schaad; 'Russ Housley'<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> Re: [jose] Concat =
KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The problem with that is that we&#8217;re inventing our own KDF at =
that point.&nbsp; The upsides of Concat are that it is known to work, is =
known to be implemented, and is known to meet NIST and other existing =
security criteria.&nbsp; At least as I see it, we shouldn&#8217;t give =
up those advantages without a compelling reason to do =
so.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Sunday, June 23, 2013 4:11 PM<br><b>To:</b> Mike =
Jones; 'Russ Housley'<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have been thinking about this and I am going to make a different =
proposal.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The proposal is as follows:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;We eliminate the two partyX fields from the =
specification<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We define a new &#8220;ID&#8221; field which MUST be present for ECDH =
keys.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We say that you take the ID field from the sender/recipient =
respectively and use them in the PartyX fields when doing the =
KDC.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The only down side of this, is that if one has a certificate then we =
should use the DER encoded subject name of the certificate but I am not =
sure how this would be encoded in the case you have a JWK which contains =
an x5c member. &nbsp;It might be that we will need to defined an ID and =
an IDb64 field to allow for a binary ID to be =
used.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There would still need to be a requirement that the ID field be =
length prefixed in the discussion.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Mike Jones<br><b>Sent:</b> Sunday, June 23, 2013 =
2:57 PM<br><b>To:</b> Russ Housley<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Good idea, Russ.&nbsp; How about this?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;In the general case, the specific identifiers used to tie the =
key derivation to the sender (Party U) and the receiver (Party V) are =
application specific and beyond the scope of this specification.&nbsp; =
As an illustration of one possible usage, when the JWE is a JSON Web =
Token (JWT) [JWT], applications might specify that the &#8220;iss&#8221; =
(issuer) value be used as the &#8220;apu&#8221; value and the primary =
&#8220;aud&#8221; (audience) value be used as the &#8220;apv&#8217; =
value.&#8221;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Russ Housley [<a =
href=3D"mailto:housley@vigilsec.com">mailto:housley@vigilsec.com</a>] =
<br><b>Sent:</b> Sunday, June 23, 2013 7:43 AM<br><b>To:</b> Mike =
Jones<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Concat KDF<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>Mike:<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I can add a sentence along the lines of the following to make =
Jim&#8217;s points below clearer to non-expert =
readers:</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8220;The specific identifiers used to tie the key derivation to the =
sender (Party U) and the receiver (Party V) are application specific and =
beyond the scope of this =
specification.&#8221;</span><o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
see the attraction of this approach, but I wonder if it would be =
possible to also include some advice to applications that make use of =
JOSE.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If the parties that are trying to form a pairwise key =
make different assumptions, then we do not get interoperability. &nbsp;I =
am just trying to improve the likelihood of =
interoperability.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Russ<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_0084_01CE7056.1DF9EDA0--


From iesg-secretary@ietf.org  Mon Jun 24 15:03:19 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638B911E819D; Mon, 24 Jun 2013 15:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level: 
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Taygzpg7R9nF; Mon, 24 Jun 2013 15:03:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F171D11E818C; Mon, 24 Jun 2013 15:03:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130624220318.4670.98039.idtracker@ietfa.amsl.com>
Date: Mon, 24 Jun 2013 15:03:18 -0700
Cc: jose@ietf.org
Subject: [jose] JOSE WG Virtual Interim Meeting, July 15, 2013
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 22:03:19 -0000

The JOSE Working Group will hold a virtual interim meeting on Monday,
July 15, 2013 at 10:00 AM PDT.

Additional information will be announced on the JOSE WG mailing list:
http://www.ietf.org/mail-archive/web/jose/current/maillist.html

From ve7jtb@ve7jtb.com  Mon Jun 24 16:50:20 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAF521F9F2A for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 16:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4f-KH3LihW9L for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 16:50:18 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A480821F9F03 for <jose@ietf.org>; Mon, 24 Jun 2013 16:50:18 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id e11so27003531iej.29 for <jose@ietf.org>; Mon, 24 Jun 2013 16:50:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=2OFjEHG/xHBYyZhE8leZx6xo6SNHxqghAl2cRixfZfQ=; b=QHYwJaibypLqgiObDi4j9i5ynOjvRbbQ7AewlEBNDIRHVUSjAAcm6h7lRtkG705Cw2 oZVkgAve6eARHlckfX3u7dJNGcxljraiQtXTo1Eb0cRYjxofX/zTzrvI31W0xhxn/Had loaC/ENG5G5S/aerVrCoz61qO7oAOY2YCt3+0mfIa0XMUafVfpIFgjxEmP39pNGrnHx3 6N+v4//5H5kl944zBg8Fxotr7ob+nDjKq3RNaFfK2W+vfkkIhHbJcQxV5+s9GAZOWNqw odqjtae/jstZ6Uv7aBOaMIGDCgn7F/S2Wwa5bSbxKVIZ/kZutr/8Sd1692NJ1whcwKRK z8PA==
X-Received: by 10.50.110.100 with SMTP id hz4mr6983660igb.46.1372117811536; Mon, 24 Jun 2013 16:50:11 -0700 (PDT)
Received: from [192.168.1.35] (190-20-31-145.baf.movistar.cl. [190.20.31.145]) by mx.google.com with ESMTPSA id z6sm664731igw.8.2013.06.24.16.50.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Jun 2013 16:50:10 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C736AA10-E1B7-48E5-9DF8-24E9FE11C55F"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com>
Date: Mon, 24 Jun 2013 19:49:41 -0400
Message-Id: <6C8CCB64-095A-42A2-A986-D38D86A37E34@ve7jtb.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com> <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com>
To: Brian Campbell <bcampbell@pingidentity.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkJE+LW7OicgjY5bRNZuS+SuE1QLK40X+rgrdRCvX34TChIGcxTYIg1a6zhdTPmohHB9wiT
Cc: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>, Edmund Jay <ejay@mgi1.com>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 24 Jun 2013 23:50:20 -0000

--Apple-Mail=_C736AA10-E1B7-48E5-9DF8-24E9FE11C55F
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_013EC9A5-1A26-41A3-9008-7F8C0D541FB7"


--Apple-Mail=_013EC9A5-1A26-41A3-9008-7F8C0D541FB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

+1 I am OK with dropping those 4 Mime types.=20

I think a single generic media type for JOSE is the correct thing.=20

John B.

On 2013-06-20, at 4:47 PM, Brian Campbell <bcampbell@pingidentity.com> =
wrote:

> I'm okay dropping them.
>=20
>=20
> On Thu, Jun 20, 2013 at 2:39 PM, Edmund Jay <ejay@mgi1.com> wrote:
> +1 in favor of dropping
>=20
> From: Mike Jones <Michael.Jones@microsoft.com>
> To: "jose@ietf.org" <jose@ietf.org>
> Sent: Tue, June 18, 2013 6:42:15 PM
> Subject: [jose] Should we keep or remove the JOSE JWS and JWE MIME =
types?
>=20
> The JWS and JWE documents currently define these MIME types for the =
convenience of applications that may want to use them:
>=20
>                 application/jws
>=20
>                 application/jws+json
>=20
>                 application/jwe
>=20
>                 application/jwe+json
>=20
> =20
> That being said, I=92m not aware of any uses of these by applications =
at present.  Thus, I think that makes it fair game to ask whether we =
want to keep them or remove them =96 in which case, if applications ever =
needed them, they could define them later.
>=20
> =20
> Another dimension of this question for JWS and JWE is that it=92s not =
clear that the four types application/jws, application/jws+json, =
application/jwe, and application/jwe+json are even the right ones.  It =
might be more useful to have generic application/jose and =
application/jose+json types, which could hold either JWS or JWE objects =
respectively using the compact or JSON serializations (although I=92m =
not advocating adding them at this time).
>=20
> =20
> Having different JWS versus JWE MIME types apparently did contribute =
to at least Dick=92s confusion about the purpose of the =93typ=94 field, =
so deleting them could help eliminate this possibility of confusion in =
the future.  Thus, I=92m increasingly convinced we should get rid of the =
JWS and JWE types and leave it up to applications to define the types =
they need, when they need them.
>=20
> =20
> Do people have use cases for these four MIME types now or should we =
leave them to future specs to define, if needed?
>=20
> =20
>                                                                 -- =
Mike
>=20
> =20
> P.S.  For completeness, I=92ll add that the JWK document also defines =
these MIME types:
>=20
>                 application/jwk+json
>=20
>                 application/jwk-set+json
>=20
> =20
> There are already clear use cases for these types, so I=92m not =
advocating deleting them, but wanted to call that out explicitly.  For =
instance, when retrieving a JWK Set document referenced by a =93jku=94 =
header parameter, I believe that the result should use the =
application/jwk-set+json type.  (In fact, I=92ll add this to the specs, =
unless there are any objections.)  Likewise, =
draft-miller-jose-jwe-protected-jwk-02 already uses =
application/jwk+json.  Both could also be as =93cty=94 values when =
encrypting JWKs and JWK Sets, in contexts where that that would be =
useful.
>=20
> =20
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>=20
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_013EC9A5-1A26-41A3-9008-7F8C0D541FB7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1 I =
am OK with dropping those 4 Mime types.&nbsp;<div><br></div><div>I think =
a single generic media type for JOSE is the correct =
thing.&nbsp;</div><div><br></div><div>John B.</div><div><br><div><div>On =
2013-06-20, at 4:47 PM, Brian Campbell &lt;<a =
href=3D"mailto:bcampbell@pingidentity.com">bcampbell@pingidentity.com</a>&=
gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">I'm okay dropping them.<br></div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 20, =
2013 at 2:39 PM, Edmund Jay <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ejay@mgi1.com" =
target=3D"_blank">ejay@mgi1.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div =
style=3D"font-family:tahoma,'new =
york',times,serif;font-size:10pt"><div>+1 in favor of dropping</div><div =
style=3D"font-family:tahoma,new york,times,serif;font-size:10pt">

<br><div style=3D"font-family:times new roman,new =
york,times,serif;font-size:12pt"><font face=3D"Tahoma"><hr =
size=3D"1"><b><span style=3D"font-weight:bold">From:</span></b> Mike =
Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;<br>

<b><span style=3D"font-weight:bold">To:</span></b> "<a =
href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>" =
&lt;<a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a>&gt;<br><b><span =
style=3D"font-weight:bold">Sent:</span></b> Tue, June 18, 2013 6:42:15 =
PM<br>

<b><span style=3D"font-weight:bold">Subject:</span></b> [jose] Should we =
keep or remove the JOSE JWS and JWE MIME types?<br></font><div><div =
class=3D"h5"><br>

=20
=20



<div><p class=3D"MsoNormal">The JWS and JWE documents currently define =
these MIME types for the convenience of applications that may want to =
use them:</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jws+json</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwe+json</p><div> =
&nbsp;<br class=3D"webkit-block-placeholder"></div><p =
class=3D"MsoNormal">That being said, I=92m not aware of any uses of =
these by applications at present.&nbsp; Thus, I think that makes it fair =
game to ask whether we want to keep them or remove them =96 in which =
case, if applications ever needed them, they could define
 them later.</p><div> &nbsp;<br =
class=3D"webkit-block-placeholder"></div><p class=3D"MsoNormal">Another =
dimension of this question for JWS and JWE is that it=92s not clear that =
the four types application/jws, application/jws+json, application/jwe, =
and application/jwe+json are even the right ones.&nbsp; It might be more =
useful to have generic
 application/jose and application/jose+json types, which could hold =
either JWS or JWE objects respectively using the compact or JSON =
serializations (although I=92m not advocating adding them at this =
time).</p><div> &nbsp;<br class=3D"webkit-block-placeholder"></div><p =
class=3D"MsoNormal">Having different JWS versus JWE MIME types =
apparently did contribute to at least Dick=92s confusion about the =
purpose of the =93typ=94 field, so deleting them could help eliminate =
this possibility of confusion in the future.&nbsp; Thus, I=92m =
increasingly
 convinced we should get rid of the JWS and JWE types and leave it up to =
applications to define the types they need, when they need =
them.</p><div> &nbsp;<br class=3D"webkit-block-placeholder"></div><p =
class=3D"MsoNormal">Do people have use cases for these four MIME types =
now or should we leave them to future specs to define, if =
needed?</p><div> &nbsp;<br class=3D"webkit-block-placeholder"></div><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</p><div> &nbsp;<br =
class=3D"webkit-block-placeholder"></div><p class=3D"MsoNormal">P.S.&nbsp;=
 For completeness, I=92ll add that the JWK document also defines these =
MIME types:</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk+json</p><p =
class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; application/jwk-set+json</p><div> =
&nbsp;<br class=3D"webkit-block-placeholder"></div><p =
class=3D"MsoNormal">There are already clear use cases for these types, =
so I=92m not advocating deleting them, but wanted to call that out =
explicitly.&nbsp; For instance, when retrieving a JWK Set document =
referenced by a =93jku=94 header parameter, I believe that the
 result should use the application/jwk-set+json type.&nbsp; (In fact, =
I=92ll add this to the specs, unless there are any objections.)&nbsp; =
Likewise, draft-miller-jose-jwe-protected-jwk-02 already uses =
application/jwk+json.&nbsp; Both could also be as =93cty=94 values when =
encrypting
 JWKs and JWK Sets, in contexts where that that would be =
useful.</p><div> &nbsp;<br class=3D"webkit-block-placeholder"></div>=20
</div>


</div></div></div></div><div></div>


</div></div><br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>jose mailing =
list<br><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/jose<br></blockquote></div><br></div></body></html>=

--Apple-Mail=_013EC9A5-1A26-41A3-9008-7F8C0D541FB7--

--Apple-Mail=_C736AA10-E1B7-48E5-9DF8-24E9FE11C55F
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI0MjM0OTQxWjAjBgkqhkiG9w0BCQQxFgQUUFCbgfxg
GhaRv+g1NZF7zCRzyVswgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAZ9Y8cKZwnn0ySCHGQSfLvOPpk3CLML7+hKDy+Ttz
jvJE4JU6DZM9zXfCj1D/0SnhryGIt/RGfp5Uk1lJtJSh6GboSOVL5HApxw5GaEpN83L/Lvceup0F
b7cIfRNWNbFqlefV7AlQUe/z1e6ZZI7EBpXw+rQQj3/xwInBFa6xj28zLXay+cey3saYxtYBrwrc
cBpYcMpReQY/5ln2BQrrcjUz0x5VZarqrqYYofxMl72zdzlqf0PmL7jqc2+f2+ZNQD+wQw6ewrao
AlpCyh6HrrhvfOovgbmKD56nxOGlBBY5ETRkU+fMhUX9KzrD3VCGPY19Yekj42RV0CHsZMovuQAA
AAAAAA==

--Apple-Mail=_C736AA10-E1B7-48E5-9DF8-24E9FE11C55F--

From James.H.Manger@team.telstra.com  Mon Jun 24 19:44:36 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 923D321E8089 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 19:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.716
X-Spam-Level: 
X-Spam-Status: No, score=-0.716 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwXPn9D+Y3dk for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 19:44:30 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfa.amsl.com (Postfix) with ESMTP id 1A05921E8087 for <jose@ietf.org>; Mon, 24 Jun 2013 19:44:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,933,1363093200"; d="scan'208";a="142822309"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipoavi.tcif.telstra.com.au with ESMTP; 25 Jun 2013 12:44:29 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7116"; a="140587517"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipccvi.tcif.telstra.com.au with ESMTP; 25 Jun 2013 12:44:28 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Tue, 25 Jun 2013 12:44:28 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: John Bradley <ve7jtb@ve7jtb.com>
Date: Tue, 25 Jun 2013 12:44:27 +1000
Thread-Topic: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
Thread-Index: Ac5xNZqZ4/FAkz9ZTtCC+3vk/PglswAF66Pw
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BD1CF5B@WSMSG3153V.srv.dir.telstra.com>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <1371760769.7926.YahooMailRC@web184402.mail.bf1.yahoo.com> <CA+k3eCRS1Fri_fW310UKdvwBMXA1+wdxtdBBc2cnUPypQs7zBQ@mail.gmail.com> <6C8CCB64-095A-42A2-A986-D38D86A37E34@ve7jtb.com>
In-Reply-To: <6C8CCB64-095A-42A2-A986-D38D86A37E34@ve7jtb.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 02:44:36 -0000

PiArMSBJIGFtIE9LIHdpdGggZHJvcHBpbmcgdGhvc2UgNCBNaW1lIHR5cGVzLg0KPiANCj4gSSB0
aGluayBhIHNpbmdsZSBnZW5lcmljIG1lZGlhIHR5cGUgZm9yIEpPU0UgaXMgdGhlIGNvcnJlY3Qg
dGhpbmcuDQoNCkpvaG4sDQpBcmUgeW91IHNheWluZyB5b3Ugd2FudCB0byByZXBsYWNlIHRob3Nl
IDQgd2l0aCAxPw0KU28gMSBtZWRpYSB0eXBlIHdvdWxkIGNvdmVyIDIgc2VyaWFsaXphdGlvbnM/
DQoNCi0tDQpKYW1lcyBNYW5nZXINCg0KDQogDQo+IE9uIDIwMTMtMDYtMjAsIGF0IDQ6NDcgUE0s
IEJyaWFuIENhbXBiZWxsIDxiY2FtcGJlbGxAcGluZ2lkZW50aXR5LmNvbT4NCj4gd3JvdGU6DQo+
IA0KPiANCj4gSSdtIG9rYXkgZHJvcHBpbmcgdGhlbS4NCj4gDQo+IE9uIFRodSwgSnVuIDIwLCAy
MDEzIGF0IDI6MzkgUE0sIEVkbXVuZCBKYXkgPGVqYXlAbWdpMS5jb20+IHdyb3RlOg0KPiArMSBp
biBmYXZvciBvZiBkcm9wcGluZw0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPiBGcm9tOiBNaWtlIEpvbmVzIDxNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5j
b20+DQo+IFRvOiAiam9zZUBpZXRmLm9yZyIgPGpvc2VAaWV0Zi5vcmc+DQo+IFNlbnQ6IFR1ZSwg
SnVuZSAxOCwgMjAxMyA2OjQyOjE1IFBNDQo+IFN1YmplY3Q6IFtqb3NlXSBTaG91bGQgd2Uga2Vl
cCBvciByZW1vdmUgdGhlIEpPU0UgSldTIGFuZCBKV0UgTUlNRQ0KPiB0eXBlcz8NCj4gDQo+IFRo
ZSBKV1MgYW5kIEpXRSBkb2N1bWVudHMgY3VycmVudGx5IGRlZmluZSB0aGVzZSBNSU1FIHR5cGVz
IGZvciB0aGUNCj4gY29udmVuaWVuY2Ugb2YgYXBwbGljYXRpb25zIHRoYXQgbWF5IHdhbnQgdG8g
dXNlIHRoZW06DQo+IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBsaWNhdGlvbi9q
d3MNCj4gwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIGFwcGxpY2F0aW9uL2p3cytqc29u
DQo+IMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBhcHBsaWNhdGlvbi9qd2UNCj4gwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIGFwcGxpY2F0aW9uL2p3ZStqc29uDQo+IC4uLg0K

From tony@att.com  Mon Jun 24 20:14:38 2013
Return-Path: <tony@att.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9906B21F9CEC for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 20:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.698
X-Spam-Level: 
X-Spam-Status: No, score=-105.698 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkUXlIq1QD8L for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 20:14:32 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 164CB21F9CF1 for <jose@ietf.org>; Mon, 24 Jun 2013 20:14:32 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 71b09c15.0.3778248.00-272.10484624.nbfkord-smmo06.seg.att.com (envelope-from <tony@att.com>);  Tue, 25 Jun 2013 03:14:32 +0000 (UTC)
X-MXL-Hash: 51c90b181f32a38a-3c8e392f72758a1ac6e2de7d3b7b9ce7b46b7afe
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5P3EVHU020456 for <jose@ietf.org>; Mon, 24 Jun 2013 23:14:31 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5P3EOVW020387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <jose@ietf.org>; Mon, 24 Jun 2013 23:14:29 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor) for <jose@ietf.org>; Tue, 25 Jun 2013 03:14:16 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5P3EGfw018400 for <jose@ietf.org>; Mon, 24 Jun 2013 23:14:16 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r5P3EDGG018384 for <jose@ietf.org>; Mon, 24 Jun 2013 23:14:13 -0400
Received: from [135.70.3.126] (vpn-135-70-3-126.vpn.west.att.com[135.70.3.126]) by maillennium.att.com (mailgw1) with ESMTP id <20130625031410gw100bhhbge> (Authid: tony); Tue, 25 Jun 2013 03:14:11 +0000
X-Originating-IP: [135.70.3.126]
Message-ID: <51C90B09.9050305@att.com>
Date: Mon, 24 Jun 2013 23:14:17 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "jose@ietf.org" <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B1680429673943678735D4@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgQUpbYLatgiaXa8T9oMMi+sA5KxEiocETLTEDXskTtqDQ@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678794EF@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgSui3q4co4sCRBZCsA_wEgSNUFx8v0jsx+H_2z761VN=Q@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678798E6@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTf6-kbQmkOxgJX-aSDtLmcNPifPLVVwei9naBuELQ3OA@mail.gmail.com>
In-Reply-To: <CAL02cgTf6-kbQmkOxgJX-aSDtLmcNPifPLVVwei9naBuELQ3OA@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------010202050803050008070405"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=VapAyiV9 c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=ejDPqqJihJkA:10 a=bfzWQn4VrGAA:10 a=Youw7J1VjLsA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=GxhHSBoc]
X-AnalysisOut: [HF4A:10 a=yMhMjlubAAAA:8 a=48vgC7mUAAAA:8 a=Vt_-PteriqkSKN]
X-AnalysisOut: [erh98A:9 a=wPNLvfGTeEIA:10 a=-AOE9ft50oIA:10 a=lZB815dzVvQ]
X-AnalysisOut: [A:10 a=pGLkceISAAAA:8 a=Khvs_yYRcUdzI71M3zcA:9 a=_W_S_7Vec]
X-AnalysisOut: [oQA:10 a=tXsnliwV7b4A:10 a=dnEh7ZtaC97qqMXY:21]
Subject: Re: [jose] Should we keep or remove the JOSE JWS and JWE MIME types?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 03:14:38 -0000

This is a multi-part message in MIME format.
--------------010202050803050008070405
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Of all of the suggestions I've seen so far on this topic, I think this
one gives the best way to proceed on the media type.

To paraphrase, it

    1) replaces application/jws and application/jwe with application/jose
and
    2) replaces application/jws+json and application/jwe+json with
application/jose+json

And there is a simple algorithm that can be applied to determine whether
it's jwe or jws.

    Tony Hansen

On 6/20/2013 2:39 PM, Richard Barnes wrote:
> What you mean to say is that there are really two algorithms here,
> depending on the media type:
>
> application/jose
> -> If 3 components, JWS
> -> If 5 components, JWE
>
> application/jose+json
> -> If 'payloaod', JWS
> -> If 'ciphertext', JWE
>
> On Thu, Jun 20, 2013 at 1:41 PM, Mike Jones
> <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>> wrote:
>
>     I know of no use cases where the application won't know whether
>     it's using the Compact Serialization or the JSON Serialization.
>
>      
>
>     *From:*Richard Barnes [mailto:rlb@ipv.sx <mailto:rlb@ipv.sx>]
>     *Sent:* Thursday, June 20, 2013 9:49 AM
>
>
>     *To:* Mike Jones
>     *Cc:* jose@ietf.org <mailto:jose@ietf.org>
>     *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and
>     JWE MIME types?
>
>      
>
>     That algorithm is part of the story, but it's incomplete.  What we
>     need is an algorithm that starts with an arbitrary octet string
>     and sorts by JWS/JWE and serialization.  An outline of the flow chart:
>
>      
>
>     1. If content parses as valid JSON
>
>     1.*. Parse JSON
>
>     1.1. Iontains a "ciphertext" field -> JWE + JSON
>
>     1.2. Contains a "payload" field -> JWS + JSON
>
>     1.3. Else fail
>
>     2. Else if content matches the regex "^[a-zA-Z0-9_.-]*$"
>
>     2.*. Split on "."
>
>     2.1. If 5 components -> JWE + compact
>
>     2.2. If 3 components -> JWS + compact
>
>     2.3. Else fail
>
>     3. Else fail
>
>      
>
>     There's also the question of which document this goes in.  It
>     would be a natural thing for a combined JWS+JWE document, but we
>     don't have one of those :(
>
>      
>
>      
>
>      
>
>     On Thu, Jun 20, 2013 at 11:19 AM, Mike Jones
>     <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>>
>     wrote:
>
>     There is a defined algorithm to distinguish between the JWS and
>     JWE objects in the third paragraph of
>     http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4.
>
>      
>
>                                                                 -- Mike
>
>      
>
>     *From:*Richard Barnes [mailto:rlb@ipv.sx <mailto:rlb@ipv.sx>]
>     *Sent:* Thursday, June 20, 2013 8:15 AM
>     *To:* Mike Jones
>     *Cc:* jose@ietf.org <mailto:jose@ietf.org>
>
>
>     *Subject:* Re: [jose] Should we keep or remove the JOSE JWS and
>     JWE MIME types?
>
>      
>
>     Multiplexing JWE and JWS under a single JOSE media type only makes
>     sense if there's a defined algorithm to demux them.  So if you
>     want to do this, you would need to write down the algorithm.
>
>      
>
>     Personally, it seems simpler and clearer to me to just have the
>     four current types, so that you know which type of object you're
>     dealing with, and in what serialization, without having to do
>     content sniffing.
>
>      
>
>     On Tue, Jun 18, 2013 at 9:26 PM, Mike Jones
>     <Michael.Jones@microsoft.com <mailto:Michael.Jones@microsoft.com>>
>     wrote:
>
>     The JWS and JWE documents currently define these MIME types for
>     the convenience of applications that may want to use them:
>
>                     application/jws
>
>                     application/jws+json
>
>                     application/jwe
>
>                     application/jwe+json
>
>      
>
>     That being said, I'm not aware of any uses of these by
>     applications at present.  Thus, I think that makes it fair game to
>     ask whether we want to keep them or remove them -- in which case,
>     if applications ever needed them, they could define them later.
>
>      
>
>     Another dimension of this question for JWS and JWE is that it's
>     not clear that the four types application/jws,
>     application/jws+json, application/jwe, and application/jwe+json
>     are even the right ones.  It might be more useful to have generic
>     application/jose and application/jose+json types, which could hold
>     either JWS or JWE objects respectively using the compact or JSON
>     serializations (although I'm not advocating adding them at this time).
>
>      
>
>     Having different JWS versus JWE MIME types apparently did
>     contribute to at least Dick's confusion about the purpose of the
>     "typ" field, so deleting them could help eliminate this
>     possibility of confusion in the future.  Thus, I'm increasingly
>     convinced we should get rid of the JWS and JWE types and leave it
>     up to applications to define the types they need, when they need them.
>
>      
>
>     Do people have use cases for these four MIME types now or should
>     we leave them to future specs to define, if needed?
>
>      
>
>                                                                     --
>     Mike
>
>      
>
>     P.S.  For completeness, I'll add that the JWK document also
>     defines these MIME types:
>
>                     application/jwk+json
>
>                     application/jwk-set+json
>
>      
>
>     There are already clear use cases for these types, so I'm not
>     advocating deleting them, but wanted to call that out explicitly. 
>     For instance, when retrieving a JWK Set document referenced by a
>     "jku" header parameter, I believe that the result should use the
>     application/jwk-set+json type.  (In fact, I'll add this to the
>     specs, unless there are any objections.)  Likewise,
>     draft-miller-jose-jwe-protected-jwk-02 already uses
>     application/jwk+json.  Both could also be as "cty" values when
>     encrypting JWKs and JWK Sets, in contexts where that that would be
>     useful.
>
>      
>
>
>     _______________________________________________
>     jose mailing list
>     jose@ietf.org <mailto:jose@ietf.org>
>     https://www.ietf.org/mailman/listinfo/jose
>
>      
>
>      
>
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--------------010202050803050008070405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Of all of the suggestions I've seen so far on this topic, I think
    this one gives the best way to proceed on the media type.<br>
    <br>
    To paraphrase, it <br>
    <br>
    &nbsp;&nbsp;&nbsp; 1) replaces application/jws and application/jwe with
    application/jose<br>
    and<br>
    &nbsp;&nbsp;&nbsp; 2) replaces application/jws+json and application/jwe+json with
    application/jose+json<br>
    <br>
    And there is a simple algorithm that can be applied to determine
    whether it's jwe or jws.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony Hansen<br>
    <br>
    <div class="moz-cite-prefix">On 6/20/2013 2:39 PM, Richard Barnes
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAL02cgTf6-kbQmkOxgJX-aSDtLmcNPifPLVVwei9naBuELQ3OA@mail.gmail.com"
      type="cite">
      <div dir="ltr">What you mean to say is that there are really two
        algorithms here, depending on the media type:
        <div><br>
        </div>
        <div>application/jose</div>
        <div>-&gt; If 3 components, JWS</div>
        <div>-&gt; If 5 components, JWE</div>
        <div><br>
        </div>
        <div>application/jose+json</div>
        <div>-&gt; If 'payloaod', JWS</div>
        <div>-&gt; If 'ciphertext', JWE</div>
        <div><br>
        </div>
        <div class="gmail_extra">On Thu, Jun 20, 2013 at 1:41 PM, Mike
          Jones <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:Michael.Jones@microsoft.com" target="_blank">Michael.Jones@microsoft.com</a>&gt;</span>
          wrote:<br>
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div link="blue" vlink="purple" lang="EN-US">
                <div>
                  <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I
                      know of no use cases where the application won&#8217;t
                      know whether it&#8217;s using the Compact Serialization
                      or the JSON Serialization.</span></p>
                  <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                  <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                      Richard Barnes [mailto:<a moz-do-not-send="true"
                        href="mailto:rlb@ipv.sx" target="_blank">rlb@ipv.sx</a>]
                      <br>
                      <b>Sent:</b> Thursday, June 20, 2013 9:49 AM</span></p>
                  <div>
                    <div class="h5"><br>
                      <b>To:</b> Mike Jones<br>
                      <b>Cc:</b> <a moz-do-not-send="true"
                        href="mailto:jose@ietf.org" target="_blank">jose@ietf.org</a><br>
                      <b>Subject:</b> Re: [jose] Should we keep or
                      remove the JOSE JWS and JWE MIME types?</div>
                  </div>
                  <div>
                    <div class="h5">
                      <p class="MsoNormal">&nbsp;</p>
                      <div>
                        <p class="MsoNormal">That algorithm is part of
                          the story, but it's incomplete. &nbsp;What we need
                          is an algorithm that starts with an arbitrary
                          octet string and sorts by JWS/JWE and
                          serialization. &nbsp;An outline of the flow chart:</p>
                        <div>
                          <p class="MsoNormal">&nbsp;</p>
                        </div>
                        <div>
                          <p class="MsoNormal">1. If content parses as
                            valid JSON</p>
                        </div>
                        <div>
                          <p class="MsoNormal">1.*. Parse JSON</p>
                        </div>
                        <div>
                          <p class="MsoNormal">1.1. Iontains a
                            "ciphertext" field -&gt; JWE + JSON</p>
                        </div>
                        <div>
                          <p class="MsoNormal">1.2. Contains a "payload"
                            field -&gt; JWS + JSON</p>
                        </div>
                        <div>
                          <p class="MsoNormal">1.3. Else fail</p>
                        </div>
                        <div>
                          <p class="MsoNormal">2. Else if content
                            matches the regex "^[a-zA-Z0-9_.-]*$"</p>
                        </div>
                        <div>
                          <p class="MsoNormal">2.*. Split on "."</p>
                        </div>
                        <div>
                          <p class="MsoNormal">2.1. If 5 components
                            -&gt; JWE + compact</p>
                        </div>
                        <div>
                          <p class="MsoNormal">2.2. If 3 components
                            -&gt; JWS + compact</p>
                        </div>
                        <div>
                          <p class="MsoNormal">2.3. Else fail</p>
                        </div>
                        <div>
                          <p class="MsoNormal">3. Else fail</p>
                        </div>
                        <div>
                          <p class="MsoNormal">&nbsp;</p>
                        </div>
                        <div>
                          <p class="MsoNormal">There's also the question
                            of which document this goes in. &nbsp;It would be
                            a natural thing for a combined JWS+JWE
                            document, but we don't have one of those :(</p>
                        </div>
                        <div>
                          <p class="MsoNormal">&nbsp;</p>
                        </div>
                        <div>
                          <p class="MsoNormal">&nbsp;</p>
                        </div>
                      </div>
                      <div>
                        <p class="MsoNormal"
                          style="margin-bottom:12.0pt">&nbsp;</p>
                        <div>
                          <p class="MsoNormal">On Thu, Jun 20, 2013 at
                            11:19 AM, Mike Jones &lt;<a
                              moz-do-not-send="true"
                              href="mailto:Michael.Jones@microsoft.com"
                              target="_blank">Michael.Jones@microsoft.com</a>&gt;
                            wrote:</p>
                          <div>
                            <div>
                              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">There
                                  is a defined algorithm to distinguish
                                  between the JWS and JWE objects in the
                                  third paragraph of <a
                                    moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4"
                                    target="_blank">
http://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-11#section-4</a>.</span></p>
                              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                  -- Mike</span></p>
                              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span></p>
                              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                                  Richard Barnes [mailto:<a
                                    moz-do-not-send="true"
                                    href="mailto:rlb@ipv.sx"
                                    target="_blank">rlb@ipv.sx</a>]
                                  <br>
                                  <b>Sent:</b> Thursday, June 20, 2013
                                  8:15 AM<br>
                                  <b>To:</b> Mike Jones<br>
                                  <b>Cc:</b> <a moz-do-not-send="true"
                                    href="mailto:jose@ietf.org"
                                    target="_blank">jose@ietf.org</a></span></p>
                              <div>
                                <p class="MsoNormal"><br>
                                  <b>Subject:</b> Re: [jose] Should we
                                  keep or remove the JOSE JWS and JWE
                                  MIME types?</p>
                              </div>
                              <p class="MsoNormal">&nbsp;</p>
                              <div>
                                <p class="MsoNormal">Multiplexing JWE
                                  and JWS under a single JOSE media type
                                  only makes sense if there's a defined
                                  algorithm to demux them. &nbsp;So if you
                                  want to do this, you would need to
                                  write down the algorithm.</p>
                                <div>
                                  <div>
                                    <div>
                                      <p class="MsoNormal">&nbsp;</p>
                                    </div>
                                    <div>
                                      <p class="MsoNormal">Personally,
                                        it seems simpler and clearer to
                                        me to just have the four current
                                        types, so that you know which
                                        type of object you're dealing
                                        with, and in what serialization,
                                        without having to do content
                                        sniffing.</p>
                                    </div>
                                  </div>
                                </div>
                              </div>
                              <div>
                                <div>
                                  <div>
                                    <p class="MsoNormal"
                                      style="margin-bottom:12.0pt">&nbsp;</p>
                                    <div>
                                      <p class="MsoNormal">On Tue, Jun
                                        18, 2013 at 9:26 PM, Mike Jones
                                        &lt;<a moz-do-not-send="true"
                                          href="mailto:Michael.Jones@microsoft.com"
                                          target="_blank">Michael.Jones@microsoft.com</a>&gt;
                                        wrote:</p>
                                      <div>
                                        <div>
                                          <p class="MsoNormal">The JWS
                                            and JWE documents currently
                                            define these MIME types for
                                            the convenience of
                                            applications that may want
                                            to use them:</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jws</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jws+json</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jwe</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jwe+json</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">That
                                            being said, I&#8217;m not aware of
                                            any uses of these by
                                            applications at present.&nbsp;
                                            Thus, I think that makes it
                                            fair game to ask whether we
                                            want to keep them or remove
                                            them &#8211; in which case, if
                                            applications ever needed
                                            them, they could define them
                                            later.</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">Another
                                            dimension of this question
                                            for JWS and JWE is that it&#8217;s
                                            not clear that the four
                                            types application/jws,
                                            application/jws+json,
                                            application/jwe, and
                                            application/jwe+json are
                                            even the right ones.&nbsp; It
                                            might be more useful to have
                                            generic application/jose and
                                            application/jose+json types,
                                            which could hold either JWS
                                            or JWE objects respectively
                                            using the compact or JSON
                                            serializations (although I&#8217;m
                                            not advocating adding them
                                            at this time).</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">Having
                                            different JWS versus JWE
                                            MIME types apparently did
                                            contribute to at least
                                            Dick&#8217;s confusion about the
                                            purpose of the &#8220;typ&#8221; field,
                                            so deleting them could help
                                            eliminate this possibility
                                            of confusion in the future.&nbsp;
                                            Thus, I&#8217;m increasingly
                                            convinced we should get rid
                                            of the JWS and JWE types and
                                            leave it up to applications
                                            to define the types they
                                            need, when they need them.</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">Do people
                                            have use cases for these
                                            four MIME types now or
                                            should we leave them to
                                            future specs to define, if
                                            needed?</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            -- Mike</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">P.S.&nbsp; For
                                            completeness, I&#8217;ll add that
                                            the JWK document also
                                            defines these MIME types:</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jwk+json</p>
                                          <p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
                                            application/jwk-set+json</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                          <p class="MsoNormal">There are
                                            already clear use cases for
                                            these types, so I&#8217;m not
                                            advocating deleting them,
                                            but wanted to call that out
                                            explicitly.&nbsp; For instance,
                                            when retrieving a JWK Set
                                            document referenced by a
                                            &#8220;jku&#8221; header parameter, I
                                            believe that the result
                                            should use the
                                            application/jwk-set+json
                                            type.&nbsp; (In fact, I&#8217;ll add
                                            this to the specs, unless
                                            there are any objections.)&nbsp;
                                            Likewise,
                                            draft-miller-jose-jwe-protected-jwk-02
                                            already uses
                                            application/jwk+json.&nbsp; Both
                                            could also be as &#8220;cty&#8221;
                                            values when encrypting JWKs
                                            and JWK Sets, in contexts
                                            where that that would be
                                            useful.</p>
                                          <p class="MsoNormal">&nbsp;</p>
                                        </div>
                                      </div>
                                      <p class="MsoNormal"
                                        style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
                                        jose mailing list<br>
                                        <a moz-do-not-send="true"
                                          href="mailto:jose@ietf.org"
                                          target="_blank">jose@ietf.org</a><br>
                                        <a moz-do-not-send="true"
                                          href="https://www.ietf.org/mailman/listinfo/jose"
                                          target="_blank">https://www.ietf.org/mailman/listinfo/jose</a></p>
                                    </div>
                                    <p class="MsoNormal">&nbsp;</p>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </div>
                        <p class="MsoNormal">&nbsp;</p>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
jose mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jose@ietf.org">jose@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/jose">https://www.ietf.org/mailman/listinfo/jose</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010202050803050008070405--

From James.H.Manger@team.telstra.com  Mon Jun 24 21:21:57 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C225A21F9302 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 21:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.722
X-Spam-Level: 
X-Spam-Status: No, score=-0.722 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkCvO6sx3Lom for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 21:21:51 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id AD5DB21F930C for <jose@ietf.org>; Mon, 24 Jun 2013 21:21:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,933,1363093200";  d="scan'208,217";a="143164251"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipobvi.tcif.telstra.com.au with ESMTP; 25 Jun 2013 14:21:32 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7116"; a="140603663"
Received: from wsmsg3702.srv.dir.telstra.com ([172.49.40.170]) by ipccvi.tcif.telstra.com.au with ESMTP; 25 Jun 2013 14:21:32 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3702.srv.dir.telstra.com ([172.49.40.170]) with mapi; Tue, 25 Jun 2013 14:21:31 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Mike Jones' <Michael.Jones@microsoft.com>, 'Russ Housley' <housley@vigilsec.com>
Date: Tue, 25 Jun 2013 14:21:30 +1000
Thread-Topic: [jose] Concat KDF
Thread-Index: AQI2DKIeuNf4zKTggqGJ0eM46TKvwQJlRGK8ApvD+k8A6jOEoAH71aeeAt8ahgUCiwG8iAGlt3KlAsFOBucCSOBDEAJqvEIyl8FTy5CAAHPBIA==
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BD1D219@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B930A31@WSMSG3153V.srv.dir.telstra.com> <033601ce6c6c$492fa4d0$db8eee70$@augustcellars.com> <CAL02cgQCquK9KVdnXWoeK5HJLBrU_TFaw9wNPydFRA9t1wS5jw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BB8F972@WSMSG3153V.srv.dir.telstra.com> <4E1F6AAD24975D4BA5B1680429673943678805A6@TK5EX14MBXC283.redmond.corp.microsoft.com> <4E1F6AAD24975D4BA5B168042967394367880BB1@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgRn5SA=WQDGsQUHQPRu8W+Fw0Xau0uyWXfFSn9ppe+cUQ@mail.gmail.com> <004a01ce6f8f$7b8df370$72a9da50$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367888C47@TK5EX14MBXC283.redmond.corp.microsoft.com> <EE17904F-1717-4015-B998-899C5E42F1D9@vigilsec.com> <4E1F6AAD24975D4BA5B16804296739436788B908@TK5EX14MBXC283.redmond.corp.microsoft.com> <003901ce7066$e19f9470$a4debd50$@augustcellars.com>
In-Reply-To: <003901ce7066$e19f9470$a4debd50$@augustcellars.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E1151BD1D219WSMSG3153Vsrv_"
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Concat KDF
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 04:21:57 -0000

--_000_255B9BB34FB7D647A506DC292726F6E1151BD1D219WSMSG3153Vsrv_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QSBmZXcgbW9yZSBvYnNlcnZhdGlvbnMgb24gQ29uY2F0S0RG4oCmDQoNClJldmlzaW9uIDIgb2Yg
TklTVCA4MDAtNTZBIGhhcyBqdXN0IGJlZW4gcHVibGlzaGVkLiBKT1NFIHNob3VsZCBwcm9iYWJs
eSByZWZlcmVuY2UgdGhpcyB1cGRhdGUuIFRoZSB0ZXh0IGFib3V0IGlkZW50aWZpZXJzIGZvciBw
YXJ0aWVzIGlzIHNsaWdodGx5IGJldHRlciAoc2VjdGlvbiA0LjEg4oCcS2V5IGVzdGFibGlzaG1l
bnQgUHJlcGFyYXRpb25z4oCdKSwgYnV0IGl0IHN0aWxsIGlzbuKAmXQgZXhwbGljaXQgYWJvdXQg
d2hldGhlciBzZW5kZXJzIGFuZC9vciByZWNlaXZlcnMgYXJlIHJlc3BvbnNpYmxlIGZvciB2YWxp
ZGF0aW5nIEFsZ29yaXRobUlEL1BhcnR5VUluZm8vUGFydHlWSW5mby9TdXBwUHViSW5mby9TdXBw
UHJpdkluZm8uDQoNCkluY2x1ZGluZyBhIGtleSBvd25lcuKAmXMgbmFtZSBpbiBhIEtERiBjYWxj
dWxhdGlvbiBpcyBnb2luZyB0byBiZSBhd2t3YXJkIGZvciBKT1NFIGdpdmVuIGl0IHJlYWxseSBs
ZWF2ZXMgdGhvc2UgZGV0YWlscyB0byBoaWdoZXIgbGF5ZXJzLCBidXQgaXQgaXMgbmVjZXNzYXJ5
IGZvciBpbnRlcm9wZXJhYmlsaXR5IGlmIHdlIHVzZSBDb25jYXRLREYuDQoNCkppbeKAmXMgc2No
ZW1lIG1pZ2h0IHdvcmsuIFRoZSByZWNpcGllbnTigJlzIHN0YXRpYyBFQ0RIIGtleSBpcyBhc3N1
bWVkIHRvIGNvbWUgZnJvbSBhIEpXSyB0aGF0IGhhcyBhbiDigJxJROKAnSBmaWVsZC4NCkV4YW1w
bGU6IHsia3R5IjoiRUMiLCJjcnYiOiJQLTUyMSIsImtpZCI6IjUzNzM1MiIsIklEIjoiYWxpY2Ui
LCJ4Ijoi4oCmIiwieSI6IuKApiJ9DQoNCklmIHRoZSDigJxJROKAnSBmaWVsZCBpcyBhYnNlbnQg
YnV0IGEg4oCceDVj4oCdIGZpZWxkIGlzIHByZXNlbnQsIGl0IG1pZ2h0IGJlIGVhc2llciB0byB1
c2UgdGhlIHdob2xlIGNlcnRpZmljYXRlIChpbnN0ZWFkIG9mIHRoZSBERVItZW5jb2RlZCBzdWJq
ZWN0IG5hbWUpIGFzIFBhcnR5VkluZm8uIEl0IG1lYW5zIHRoZSBjb2RlIGRvaW5nIHRoZSBDb25j
YXRLREYgY2FsY3VsYXRpb24gZG9lc27igJl0IG5lZWQgdG8gZGVjb2RlIERFUi4gSXQgZG9lcyBt
ZWFuIHRoYXQgYSByZWNpcGllbnTigJlzIGtleSBNVVNUIGJlIGFzc29jaWF0ZWQgd2l0aCBhbiDi
gJxJROKAnSBvciDigJx4NWPigJ0gZmllbGQgdG8gdXNlIENvbmNhdEtERi4NCg0K4oCcSUTigJ0g
bWlnaHQgbm90IGJlIHN1Y2ggYSBnb29kIG5hbWUgYXMgaXQgaXMgdG9vIGVhc3kgdG8gY29uZnVz
ZSB3aXRoIOKAnGtpZOKAnS4gUGVyaGFwcyDigJxvd25lcuKAnT8NCg0KVGhlIG9yaWdpbmF0b3Ig
b2YgYSBKT1NFIEVDREggbWVzc2FnZSBjb250cmlidXRlcyBhbiBlcGhlbWVyYWwga2V5IGFuZCBp
cyBub3QgYXV0aGVudGljYXRlZCBzbyBnaXZpbmcgdGhlbSBhIG5hbWUgZmVlbHMgdW5uZWNlc3Nh
cnkgKG9yIGFjdGl2ZWx5IG1pc2xlYWRpbmcpLiBIb3cgYWJvdXQgZml4aW5nIFBhcnR5VUluZm8g
dG8gYmUg4oCcYW5vbnltb3Vz4oCdIGZvciB0aGUgRUNESCBFcGhlbWVyYWwtU3RhdGljIGFsZ29y
aXRobXM/DQoNCltJdOKAmXMgYSBwaXR5IHdlIGRvbuKAmXQgaGF2ZSBhIGNhbm9uaWNhbCBmb3Jt
IG9mIEpTT04gc28gd2UgY291bGQgZGVzY3JpYmUgdGhlIENvbmNhdEtERiBPdGhlcklucHV0IGZp
ZWxkIGFzIGEgSlNPTiBvYmplY3Qg4oCUIGluc3RlYWQgb2YgbmVlZGluZyB0byBtYWtlIHVwIGFu
IGFkIGhvYyBiaW5hcnkgZm9ybWF0Ll0NCg0KDQpDb25jYXRLREYgaW4gdGhlIFhNTCBlbmNyeXB0
aW9uIHN0YW5kYXJkIFtodHRwOi8vd3d3LnczLm9yZy9UUi94bWxlbmMtY29yZTEvI3NlYy1Db25j
YXRLREZdIGhhcyBzZXBhcmF0ZSBYTUwgYXR0cmlidXRlcyBmb3IgQWxnb3JpdGhtSUQsIFBhcnR5
VUluZm8sIFBhcnR5VkluZm8sIFN1cHBQdWJJbmZvLCBhbmQgU3VwcFByaXZJbmZvLiBVbmZvcnR1
bmF0ZWx5IHRoZSBmaWVsZHMgYXJlIGNvbmNhdGVuYXRlZCB0b2dldGhlciB3aXRob3V0IHByZXNl
cnZpbmcgdGhlaXIgYm91bmRhcmllcy4gSGVuY2UgaXQgbG9va3MgYnJva2VuIHRvIG1lLiBUaGVy
ZSB3ZXJlIHNvbWUgcmVjZW50IGludGVyb3AgdGVzdCBjYXNlcyBmcm9tIE1pY3Jvc29mdCBhbmQg
SUJNIGZvciBDb25jYXRLREYgaW4gWE1MIGVuY3J5cHRpb24uIFRoZSBLREYgcGFydHMgd29yaywg
YnV0IHRoZSBhc3NvY2lhdGVkIENCQyBlbmNyeXB0aW9uIGxvb2tzIHdyb25nIGFzIGl0IGlzIG1p
c3Npbmcgc29tZSBwYWRkaW5nLiBJdCBkb2VzbuKAmXQgZ2l2ZSBtdWNoIGNvbmZpZGVuY2UgdGhh
dCBDb25jYXRLREYgaXMgdXNlZCBtdWNoLiBbaHR0cDovL2xpc3RzLnczLm9yZy9BcmNoaXZlcy9Q
dWJsaWMvcHVibGljLXhtbHNlYy8yMDEzSnVuLzAwMDUuaHRtbF0NCg0KLS0NCkphbWVzIE1hbmdl
cg0KDQpGcm9tOiBqb3NlLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBKaW0gU2NoYWFkDQpTZW50OiBNb25kYXksIDI0IEp1bmUgMjAx
MyA5OjExIEFNDQpUbzogJ01pa2UgSm9uZXMnOyAnUnVzcyBIb3VzbGV5Jw0KQ2M6IGpvc2VAaWV0
Zi5vcmcNClN1YmplY3Q6IFJlOiBbam9zZV0gQ29uY2F0IEtERg0KDQpJIGhhdmUgYmVlbiB0aGlu
a2luZyBhYm91dCB0aGlzIGFuZCBJIGFtIGdvaW5nIHRvIG1ha2UgYSBkaWZmZXJlbnQgcHJvcG9z
YWwuDQoNCg0KVGhlIHByb3Bvc2FsIGlzIGFzIGZvbGxvd3M6DQoNCg0KMS4gICAgICAgIFdlIGVs
aW1pbmF0ZSB0aGUgdHdvIHBhcnR5WCBmaWVsZHMgZnJvbSB0aGUgc3BlY2lmaWNhdGlvbg0KDQoy
LiAgICAgICBXZSBkZWZpbmUgYSBuZXcg4oCcSUTigJ0gZmllbGQgd2hpY2ggTVVTVCBiZSBwcmVz
ZW50IGZvciBFQ0RIIGtleXMuDQoNCjMuICAgICAgIFdlIHNheSB0aGF0IHlvdSB0YWtlIHRoZSBJ
RCBmaWVsZCBmcm9tIHRoZSBzZW5kZXIvcmVjaXBpZW50IHJlc3BlY3RpdmVseSBhbmQgdXNlIHRo
ZW0gaW4gdGhlIFBhcnR5WCBmaWVsZHMgd2hlbiBkb2luZyB0aGUgS0RDLg0KDQpUaGUgb25seSBk
b3duIHNpZGUgb2YgdGhpcywgaXMgdGhhdCBpZiBvbmUgaGFzIGEgY2VydGlmaWNhdGUgdGhlbiB3
ZSBzaG91bGQgdXNlIHRoZSBERVIgZW5jb2RlZCBzdWJqZWN0IG5hbWUgb2YgdGhlIGNlcnRpZmlj
YXRlIGJ1dCBJIGFtIG5vdCBzdXJlIGhvdyB0aGlzIHdvdWxkIGJlIGVuY29kZWQgaW4gdGhlIGNh
c2UgeW91IGhhdmUgYSBKV0sgd2hpY2ggY29udGFpbnMgYW4geDVjIG1lbWJlci4gIEl0IG1pZ2h0
IGJlIHRoYXQgd2Ugd2lsbCBuZWVkIHRvIGRlZmluZWQgYW4gSUQgYW5kIGFuIElEYjY0IGZpZWxk
IHRvIGFsbG93IGZvciBhIGJpbmFyeSBJRCB0byBiZSB1c2VkLg0KDQpUaGVyZSB3b3VsZCBzdGls
bCBuZWVkIHRvIGJlIGEgcmVxdWlyZW1lbnQgdGhhdCB0aGUgSUQgZmllbGQgYmUgbGVuZ3RoIHBy
ZWZpeGVkIGluIHRoZSBkaXNjdXNzaW9uLg0KDQpKaW0NCg0KDQpGcm9tOiBqb3NlLWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNaWtl
IEpvbmVzDQpTZW50OiBTdW5kYXksIEp1bmUgMjMsIDIwMTMgMjo1NyBQTQ0KVG86IFJ1c3MgSG91
c2xleQ0KQ2M6IGpvc2VAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbam9zZV0gQ29uY2F0IEtERg0K
DQpHb29kIGlkZWEsIFJ1c3MuICBIb3cgYWJvdXQgdGhpcz8NCg0K4oCcSW4gdGhlIGdlbmVyYWwg
Y2FzZSwgdGhlIHNwZWNpZmljIGlkZW50aWZpZXJzIHVzZWQgdG8gdGllIHRoZSBrZXkgZGVyaXZh
dGlvbiB0byB0aGUgc2VuZGVyIChQYXJ0eSBVKSBhbmQgdGhlIHJlY2VpdmVyIChQYXJ0eSBWKSBh
cmUgYXBwbGljYXRpb24gc3BlY2lmaWMgYW5kIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhpcyBzcGVj
aWZpY2F0aW9uLiAgQXMgYW4gaWxsdXN0cmF0aW9uIG9mIG9uZSBwb3NzaWJsZSB1c2FnZSwgd2hl
biB0aGUgSldFIGlzIGEgSlNPTiBXZWIgVG9rZW4gKEpXVCkgW0pXVF0sIGFwcGxpY2F0aW9ucyBt
aWdodCBzcGVjaWZ5IHRoYXQgdGhlIOKAnGlzc+KAnSAoaXNzdWVyKSB2YWx1ZSBiZSB1c2VkIGFz
IHRoZSDigJxhcHXigJ0gdmFsdWUgYW5kIHRoZSBwcmltYXJ5IOKAnGF1ZOKAnSAoYXVkaWVuY2Up
IHZhbHVlIGJlIHVzZWQgYXMgdGhlIOKAnGFwduKAmSB2YWx1ZS7igJ0NCg0KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0gTWlrZQ0K
DQpGcm9tOiBSdXNzIEhvdXNsZXkgW21haWx0bzpob3VzbGV5QHZpZ2lsc2VjLmNvbV0NClNlbnQ6
IFN1bmRheSwgSnVuZSAyMywgMjAxMyA3OjQzIEFNDQpUbzogTWlrZSBKb25lcw0KQ2M6IGpvc2VA
aWV0Zi5vcmc8bWFpbHRvOmpvc2VAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW2pvc2VdIENvbmNh
dCBLREYNCg0KTWlrZToNCg0KSSBjYW4gYWRkIGEgc2VudGVuY2UgYWxvbmcgdGhlIGxpbmVzIG9m
IHRoZSBmb2xsb3dpbmcgdG8gbWFrZSBKaW3igJlzIHBvaW50cyBiZWxvdyBjbGVhcmVyIHRvIG5v
bi1leHBlcnQgcmVhZGVyczoNCg0K4oCcVGhlIHNwZWNpZmljIGlkZW50aWZpZXJzIHVzZWQgdG8g
dGllIHRoZSBrZXkgZGVyaXZhdGlvbiB0byB0aGUgc2VuZGVyIChQYXJ0eSBVKSBhbmQgdGhlIHJl
Y2VpdmVyIChQYXJ0eSBWKSBhcmUgYXBwbGljYXRpb24gc3BlY2lmaWMgYW5kIGJleW9uZCB0aGUg
c2NvcGUgb2YgdGhpcyBzcGVjaWZpY2F0aW9uLuKAnQ0KDQpJIHNlZSB0aGUgYXR0cmFjdGlvbiBv
ZiB0aGlzIGFwcHJvYWNoLCBidXQgSSB3b25kZXIgaWYgaXQgd291bGQgYmUgcG9zc2libGUgdG8g
YWxzbyBpbmNsdWRlIHNvbWUgYWR2aWNlIHRvIGFwcGxpY2F0aW9ucyB0aGF0IG1ha2UgdXNlIG9m
IEpPU0UuDQoNCklmIHRoZSBwYXJ0aWVzIHRoYXQgYXJlIHRyeWluZyB0byBmb3JtIGEgcGFpcndp
c2Uga2V5IG1ha2UgZGlmZmVyZW50IGFzc3VtcHRpb25zLCB0aGVuIHdlIGRvIG5vdCBnZXQgaW50
ZXJvcGVyYWJpbGl0eS4gIEkgYW0ganVzdCB0cnlpbmcgdG8gaW1wcm92ZSB0aGUgbGlrZWxpaG9v
ZCBvZiBpbnRlcm9wZXJhYmlsaXR5Lg0KDQpSdXNzDQoNCg==

--_000_255B9BB34FB7D647A506DC292726F6E1151BD1D219WSMSG3153Vsrv_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYi
O30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNw
YW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvQWNldGF0ZSwgbGku
TXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5OiJUYWhvbWEi
LCJzYW5zLXNlcmlmIjt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgs
IGRpdi5Nc29MaXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4t
dG9wOjBjbTsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1hcmdpbi1ib3R0b206MGNtOw0KCW1hcmdp
bi1sZWZ0OjM2LjBwdDsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBw
dDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uQmFsbG9v
blRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZvbnQt
ZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLmFwcGxlLXN0eWxlLXNwYW4NCgl7
bXNvLXN0eWxlLW5hbWU6YXBwbGUtc3R5bGUtc3Bhbjt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXtt
c28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xv
cjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTIzDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFG
NDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglm
b250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzky
LjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0KQGxp
c3QgbDANCgl7bXNvLWxpc3QtaWQ6MTk4MTY4NjE1MTsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsN
Cgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6LTI2NjQ0NDU3NCA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5
ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcx
NTt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3Qg
bDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1s
ZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0
ZXh0LWluZGVudDotMTguMHB0O30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBs
MDpsZXZlbDQNCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
MTguMHB0O30NCkBsaXN0IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21h
bi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOnJpZ2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0O30NCkBs
aXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0
Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0K
CXttYXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpl
eHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVs
YXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+PC9oZWFkPjxib2R5IGxhbmc9RU4tQVUgbGluaz1ibHVl
IHZsaW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjtjb2xvcjojMUY0OTdEJz5BIGZldyBtb3JlIG9ic2VydmF0aW9ucyBvbiBDb25jYXRL
REbigKY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxl
PSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29s
b3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlJldmlzaW9uIDIgb2YgTklTVCA4MDAtNTZBIGhhcyBq
dXN0IGJlZW4gcHVibGlzaGVkLiBKT1NFIHNob3VsZCBwcm9iYWJseSByZWZlcmVuY2UgdGhpcyB1
cGRhdGUuIFRoZSB0ZXh0IGFib3V0IGlkZW50aWZpZXJzIGZvciBwYXJ0aWVzIGlzIHNsaWdodGx5
IGJldHRlciAoc2VjdGlvbiA0LjEg4oCcS2V5IGVzdGFibGlzaG1lbnQgUHJlcGFyYXRpb25z4oCd
KSwgYnV0IGl0IHN0aWxsIGlzbuKAmXQgZXhwbGljaXQgYWJvdXQgd2hldGhlciBzZW5kZXJzIGFu
ZC9vciByZWNlaXZlcnMgYXJlIHJlc3BvbnNpYmxlIGZvciB2YWxpZGF0aW5nIEFsZ29yaXRobUlE
L1BhcnR5VUluZm8vUGFydHlWSW5mby9TdXBwUHViSW5mby9TdXBwUHJpdkluZm8uPG86cD48L286
cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv
cjojMUY0OTdEJz5JbmNsdWRpbmcgYSBrZXkgb3duZXLigJlzIG5hbWUgaW4gYSBLREYgY2FsY3Vs
YXRpb24gaXMgZ29pbmcgdG8gYmUgYXdrd2FyZCBmb3IgSk9TRSBnaXZlbiBpdCByZWFsbHkgbGVh
dmVzIHRob3NlIGRldGFpbHMgdG8gaGlnaGVyIGxheWVycywgYnV0IGl0IGlzIG5lY2Vzc2FyeSBm
b3IgaW50ZXJvcGVyYWJpbGl0eSBpZiB3ZSB1c2UgQ29uY2F0S0RGLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3
RCc+Smlt4oCZcyBzY2hlbWUgbWlnaHQgd29yay4gVGhlIHJlY2lwaWVudOKAmXMgc3RhdGljIEVD
REgga2V5IGlzIGFzc3VtZWQgdG8gY29tZSBmcm9tIGEgSldLIHRoYXQgaGFzIGFuIOKAnElE4oCd
IGZpZWxkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj
b2xvcjojMUY0OTdEJz5FeGFtcGxlOiB7JnF1b3Q7a3R5JnF1b3Q7OiZxdW90O0VDJnF1b3Q7LCZx
dW90O2NydiZxdW90OzomcXVvdDtQLTUyMSZxdW90OywmcXVvdDtraWQmcXVvdDs6JnF1b3Q7NTM3
MzUyJnF1b3Q7LCZxdW90O0lEJnF1b3Q7OiZxdW90O2FsaWNlJnF1b3Q7LCZxdW90O3gmcXVvdDs6
JnF1b3Q74oCmJnF1b3Q7LCZxdW90O3kmcXVvdDs6JnF1b3Q74oCmJnF1b3Q7fTxvOnA+PC9vOnA+
PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6
IzFGNDk3RCc+SWYgdGhlIOKAnElE4oCdIGZpZWxkIGlzIGFic2VudCBidXQgYSDigJx4NWPigJ0g
ZmllbGQgaXMgcHJlc2VudCwgaXQgbWlnaHQgYmUgZWFzaWVyIHRvIHVzZSB0aGUgd2hvbGUgY2Vy
dGlmaWNhdGUgKGluc3RlYWQgb2YgdGhlIERFUi1lbmNvZGVkIHN1YmplY3QgbmFtZSkgYXMgUGFy
dHlWSW5mby4gSXQgbWVhbnMgdGhlIGNvZGUgZG9pbmcgdGhlIENvbmNhdEtERiBjYWxjdWxhdGlv
biBkb2VzbuKAmXQgbmVlZCB0byBkZWNvZGUgREVSLiBJdCBkb2VzIG1lYW4gdGhhdCBhIHJlY2lw
aWVudOKAmXMga2V5IE1VU1QgYmUgYXNzb2NpYXRlZCB3aXRoIGFuIOKAnElE4oCdIG9yIOKAnHg1
Y+KAnSBmaWVsZCB0byB1c2UgQ29uY2F0S0RGLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+4oCcSUTigJ0g
bWlnaHQgbm90IGJlIHN1Y2ggYSBnb29kIG5hbWUgYXMgaXQgaXMgdG9vIGVhc3kgdG8gY29uZnVz
ZSB3aXRoIOKAnGtpZOKAnS4gUGVyaGFwcyDigJxvd25lcuKAnT88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0Qn
PlRoZSBvcmlnaW5hdG9yIG9mIGEgSk9TRSBFQ0RIIG1lc3NhZ2UgY29udHJpYnV0ZXMgYW4gZXBo
ZW1lcmFsIGtleSBhbmQgaXMgbm90IGF1dGhlbnRpY2F0ZWQgc28gZ2l2aW5nIHRoZW0gYSBuYW1l
IGZlZWxzIHVubmVjZXNzYXJ5IChvciBhY3RpdmVseSBtaXNsZWFkaW5nKS4gSG93IGFib3V0IGZp
eGluZyBQYXJ0eVVJbmZvIHRvIGJlIOKAnGFub255bW91c+KAnSBmb3IgdGhlIEVDREggRXBoZW1l
cmFsLVN0YXRpYyBhbGdvcml0aG1zPzxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+W0l04oCZcyBhIHBpdHkg
d2UgZG9u4oCZdCBoYXZlIGEgY2Fub25pY2FsIGZvcm0gb2YgSlNPTiBzbyB3ZSBjb3VsZCBkZXNj
cmliZSB0aGUgQ29uY2F0S0RGIE90aGVySW5wdXQgZmllbGQgYXMgYSBKU09OIG9iamVjdCDigJQg
aW5zdGVhZCBvZiBuZWVkaW5nIHRvIG1ha2UgdXAgYW4gYWQgaG9jIGJpbmFyeSBmb3JtYXQuXTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJp
ZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJy
aSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkNvbmNhdEtERiBpbiB0aGUgWE1MIGVuY3J5
cHRpb24gc3RhbmRhcmQgWzxhIGhyZWY9Imh0dHA6Ly93d3cudzMub3JnL1RSL3htbGVuYy1jb3Jl
MS8jc2VjLUNvbmNhdEtERiI+aHR0cDovL3d3dy53My5vcmcvVFIveG1sZW5jLWNvcmUxLyNzZWMt
Q29uY2F0S0RGPC9hPl0gaGFzIHNlcGFyYXRlIFhNTCBhdHRyaWJ1dGVzIGZvciBBbGdvcml0aG1J
RCwgUGFydHlVSW5mbywgUGFydHlWSW5mbywgU3VwcFB1YkluZm8sIGFuZCBTdXBwUHJpdkluZm8u
IFVuZm9ydHVuYXRlbHkgdGhlIGZpZWxkcyBhcmUgY29uY2F0ZW5hdGVkIHRvZ2V0aGVyIHdpdGhv
dXQgcHJlc2VydmluZyB0aGVpciBib3VuZGFyaWVzLiBIZW5jZSBpdCBsb29rcyBicm9rZW4gdG8g
bWUuIFRoZXJlIHdlcmUgc29tZSByZWNlbnQgaW50ZXJvcCB0ZXN0IGNhc2VzIGZyb20gTWljcm9z
b2Z0IGFuZCBJQk0gZm9yIENvbmNhdEtERiBpbiBYTUwgZW5jcnlwdGlvbi4gVGhlIEtERiBwYXJ0
cyB3b3JrLCBidXQgdGhlIGFzc29jaWF0ZWQgQ0JDIGVuY3J5cHRpb24gbG9va3Mgd3JvbmcgYXMg
aXQgaXMgbWlzc2luZyBzb21lIHBhZGRpbmcuIEl0IGRvZXNu4oCZdCBnaXZlIG11Y2ggY29uZmlk
ZW5jZSB0aGF0IENvbmNhdEtERiBpcyB1c2VkIG11Y2guIFs8L3NwYW4+PGEgaHJlZj0iaHR0cDov
L2xpc3RzLnczLm9yZy9BcmNoaXZlcy9QdWJsaWMvcHVibGljLXhtbHNlYy8yMDEzSnVuLzAwMDUu
aHRtbCI+aHR0cDovL2xpc3RzLnczLm9yZy9BcmNoaXZlcy9QdWJsaWMvcHVibGljLXhtbHNlYy8y
MDEzSnVuLzAwMDUuaHRtbDwvYT5dPHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxl
PSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29s
b3I6IzFGNDk3RCc+LS08bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7Y29sb3I6IzFGNDk3RCc+SmFtZXMgTWFuZ2VyPG86cD48L286cD48L3NwYW4+PC9wPjwv
ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD48ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQnPjxkaXY+PGRpdiBzdHlsZT0n
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGNtIDBjbSAwY20nPjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBsYW5nPUVOLVVTIHN0eWxl
PSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiJz4gam9zZS1ib3VuY2VzQGlldGYub3JnIFtt
YWlsdG86am9zZS1ib3VuY2VzQGlldGYub3JnXSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkppbSBTY2hh
YWQ8YnI+PGI+U2VudDo8L2I+IE1vbmRheSwgMjQgSnVuZSAyMDEzIDk6MTEgQU08YnI+PGI+VG86
PC9iPiAnTWlrZSBKb25lcyc7ICdSdXNzIEhvdXNsZXknPGJyPjxiPkNjOjwvYj4gam9zZUBpZXRm
Lm9yZzxicj48Yj5TdWJqZWN0OjwvYj4gUmU6IFtqb3NlXSBDb25jYXQgS0RGPG86cD48L286cD48
L3NwYW4+PC9wPjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwvbzpw
PjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0Qn
PkkgaGF2ZSBiZWVuIHRoaW5raW5nIGFib3V0IHRoaXMgYW5kIEkgYW0gZ29pbmcgdG8gbWFrZSBh
IGRpZmZlcmVudCBwcm9wb3NhbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5UaGUgcHJvcG9zYWwgaXMgYXMgZm9sbG93czo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMg
c3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv
TGlzdFBhcmFncmFwaCBzdHlsZT0ndGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZl
bDEgbGZvMic+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMx
RjQ5N0QnPjxzcGFuIHN0eWxlPSdtc28tbGlzdDpJZ25vcmUnPjEuPHNwYW4gc3R5bGU9J2ZvbnQ6
Ny4wcHQgIlRpbWVzIE5ldyBSb21hbiInPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyA8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gbGFuZz1FTi1VUyBzdHls
ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv
bG9yOiMxRjQ5N0QnPiZuYnNwO1dlIGVsaW1pbmF0ZSB0aGUgdHdvIHBhcnR5WCBmaWVsZHMgZnJv
bSB0aGUgc3BlY2lmaWNhdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0
UGFyYWdyYXBoIHN0eWxlPSd0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBs
Zm8yJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3
RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+Mi48c3BhbiBzdHlsZT0nZm9udDo3LjBw
dCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6
IzFGNDk3RCc+V2UgZGVmaW5lIGEgbmV3IOKAnElE4oCdIGZpZWxkIHdoaWNoIE1VU1QgYmUgcHJl
c2VudCBmb3IgRUNESCBrZXlzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29MaXN0
UGFyYWdyYXBoIHN0eWxlPSd0ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBs
Zm8yJz48IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3
RCc+PHNwYW4gc3R5bGU9J21zby1saXN0Oklnbm9yZSc+My48c3BhbiBzdHlsZT0nZm9udDo3LjBw
dCAiVGltZXMgTmV3IFJvbWFuIic+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IDwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6
IzFGNDk3RCc+V2Ugc2F5IHRoYXQgeW91IHRha2UgdGhlIElEIGZpZWxkIGZyb20gdGhlIHNlbmRl
ci9yZWNpcGllbnQgcmVzcGVjdGl2ZWx5IGFuZCB1c2UgdGhlbSBpbiB0aGUgUGFydHlYIGZpZWxk
cyB3aGVuIGRvaW5nIHRoZSBLREMuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+VGhlIG9ubHkgZG93biBzaWRlIG9mIHRoaXMsIGlzIHRoYXQgaWYgb25lIGhhcyBhIGNl
cnRpZmljYXRlIHRoZW4gd2Ugc2hvdWxkIHVzZSB0aGUgREVSIGVuY29kZWQgc3ViamVjdCBuYW1l
IG9mIHRoZSBjZXJ0aWZpY2F0ZSBidXQgSSBhbSBub3Qgc3VyZSBob3cgdGhpcyB3b3VsZCBiZSBl
bmNvZGVkIGluIHRoZSBjYXNlIHlvdSBoYXZlIGEgSldLIHdoaWNoIGNvbnRhaW5zIGFuIHg1YyBt
ZW1iZXIuICZuYnNwO0l0IG1pZ2h0IGJlIHRoYXQgd2Ugd2lsbCBuZWVkIHRvIGRlZmluZWQgYW4g
SUQgYW5kIGFuIElEYjY0IGZpZWxkIHRvIGFsbG93IGZvciBhIGJpbmFyeSBJRCB0byBiZSB1c2Vk
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1V
UyBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N
c29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPlRoZXJlIHdvdWxkIHN0
aWxsIG5lZWQgdG8gYmUgYSByZXF1aXJlbWVudCB0aGF0IHRoZSBJRCBmaWVsZCBiZSBsZW5ndGgg
cHJlZml4ZWQgaW4gdGhlIGRpc2N1c3Npb24uPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxl
PSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29s
b3I6IzFGNDk3RCc+SmltPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCc+PGRpdj48
ZGl2IHN0eWxlPSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFk
ZGluZzozLjBwdCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9
RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiJz5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiBqb3NlLWJvdW5jZXNA
aWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0Zi5vcmddIDxiPk9uIEJlaGFsZiBPZiA8
L2I+TWlrZSBKb25lczxicj48Yj5TZW50OjwvYj4gU3VuZGF5LCBKdW5lIDIzLCAyMDEzIDI6NTcg
UE08YnI+PGI+VG86PC9iPiBSdXNzIEhvdXNsZXk8YnI+PGI+Q2M6PC9iPiBqb3NlQGlldGYub3Jn
PGJyPjxiPlN1YmplY3Q6PC9iPiBSZTogW2pvc2VdIENvbmNhdCBLREY8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVO
LVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1z
ZXJpZiI7Y29sb3I6IzFGNDk3RCc+R29vZCBpZGVhLCBSdXNzLiZuYnNwOyBIb3cgYWJvdXQgdGhp
cz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4t
VVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNl
cmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz7igJxJbiB0aGUgZ2Vu
ZXJhbCBjYXNlLCB0aGUgc3BlY2lmaWMgaWRlbnRpZmllcnMgdXNlZCB0byB0aWUgdGhlIGtleSBk
ZXJpdmF0aW9uIHRvIHRoZSBzZW5kZXIgKFBhcnR5IFUpIGFuZCB0aGUgcmVjZWl2ZXIgKFBhcnR5
IFYpIGFyZSBhcHBsaWNhdGlvbiBzcGVjaWZpYyBhbmQgYmV5b25kIHRoZSBzY29wZSBvZiB0aGlz
IHNwZWNpZmljYXRpb24uJm5ic3A7IEFzIGFuIGlsbHVzdHJhdGlvbiBvZiBvbmUgcG9zc2libGUg
dXNhZ2UsIHdoZW4gdGhlIEpXRSBpcyBhIEpTT04gV2ViIFRva2VuIChKV1QpIFtKV1RdLCBhcHBs
aWNhdGlvbnMgbWlnaHQgc3BlY2lmeSB0aGF0IHRoZSDigJxpc3PigJ0gKGlzc3VlcikgdmFsdWUg
YmUgdXNlZCBhcyB0aGUg4oCcYXB14oCdIHZhbHVlIGFuZCB0aGUgcHJpbWFyeSDigJxhdWTigJ0g
KGF1ZGllbmNlKSB2YWx1ZSBiZSB1c2VkIGFzIHRoZSDigJxhcHbigJkgdmFsdWUu4oCdPG86cD48
L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTIHN0eWxl
PSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29s
b3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJD
YWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0tIE1pa2U8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMg
c3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdj48ZGl2IHN0
eWxlPSdib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwY20gMGNtIDBjbSc+PHAgY2xhc3M9TXNvTm9ybWFsPjxiPjxzcGFuIGxhbmc9RU4tVVMg
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYi
Jz5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiInPiBSdXNzIEhvdXNsZXkgWzxhIGhy
ZWY9Im1haWx0bzpob3VzbGV5QHZpZ2lsc2VjLmNvbSI+bWFpbHRvOmhvdXNsZXlAdmlnaWxzZWMu
Y29tPC9hPl0gPGJyPjxiPlNlbnQ6PC9iPiBTdW5kYXksIEp1bmUgMjMsIDIwMTMgNzo0MyBBTTxi
cj48Yj5Ubzo8L2I+IE1pa2UgSm9uZXM8YnI+PGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86am9z
ZUBpZXRmLm9yZyI+am9zZUBpZXRmLm9yZzwvYT48YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBbam9z
ZV0gQ29uY2F0IEtERjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48cCBjbGFzcz1N
c29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRp
dj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTPk1pa2U6PG86cD48L286
cD48L3NwYW4+PC9wPjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRv
bToxMi4wcHQnPjxzcGFuIGxhbmc9RU4tVVM+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxk
aXY+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5
N0QnPkkgY2FuIGFkZCBhIHNlbnRlbmNlIGFsb25nIHRoZSBsaW5lcyBvZiB0aGUgZm9sbG93aW5n
IHRvIG1ha2UgSmlt4oCZcyBwb2ludHMgYmVsb3cgY2xlYXJlciB0byBub24tZXhwZXJ0IHJlYWRl
cnM6PC9zcGFuPjxzcGFuIGxhbmc9RU4tVVM+PG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2Pjxk
aXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4m
bmJzcDs8L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+
PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0Qn
PuKAnFRoZSBzcGVjaWZpYyBpZGVudGlmaWVycyB1c2VkIHRvIHRpZSB0aGUga2V5IGRlcml2YXRp
b24gdG8gdGhlIHNlbmRlciAoUGFydHkgVSkgYW5kIHRoZSByZWNlaXZlciAoUGFydHkgVikgYXJl
IGFwcGxpY2F0aW9uIHNwZWNpZmljIGFuZCBiZXlvbmQgdGhlIHNjb3BlIG9mIHRoaXMgc3BlY2lm
aWNhdGlvbi7igJ08L3NwYW4+PHNwYW4gbGFuZz1FTi1VUz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
PC9kaXY+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxh
bmc9RU4tVVM+SSBzZWUgdGhlIGF0dHJhY3Rpb24gb2YgdGhpcyBhcHByb2FjaCwgYnV0IEkgd29u
ZGVyIGlmIGl0IHdvdWxkIGJlIHBvc3NpYmxlIHRvIGFsc28gaW5jbHVkZSBzb21lIGFkdmljZSB0
byBhcHBsaWNhdGlvbnMgdGhhdCBtYWtlIHVzZSBvZiBKT1NFLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBsYW5nPUVOLVVTPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBs
YW5nPUVOLVVTPklmIHRoZSBwYXJ0aWVzIHRoYXQgYXJlIHRyeWluZyB0byBmb3JtIGEgcGFpcndp
c2Uga2V5IG1ha2UgZGlmZmVyZW50IGFzc3VtcHRpb25zLCB0aGVuIHdlIGRvIG5vdCBnZXQgaW50
ZXJvcGVyYWJpbGl0eS4gJm5ic3A7SSBhbSBqdXN0IHRyeWluZyB0byBpbXByb3ZlIHRoZSBsaWtl
bGlob29kIG9mIGludGVyb3BlcmFiaWxpdHkuPG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2Pjxk
aXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPjwvZGl2PjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIGxhbmc9RU4tVVM+
UnVzczxvOnA+PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBsYW5nPUVOLVVTPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48
L2Rpdj48L2Rpdj48L2JvZHk+PC9odG1sPg==

--_000_255B9BB34FB7D647A506DC292726F6E1151BD1D219WSMSG3153Vsrv_--

From trac+jose@trac.tools.ietf.org  Mon Jun 24 22:57:09 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE97721F9A1E for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 22:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnYWmrR628rM for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 22:57:09 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 58FD321F99C7 for <jose@ietf.org>; Mon, 24 Jun 2013 22:57:08 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52873 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrMFN-00020V-KS; Tue, 25 Jun 2013 07:56:57 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 25 Jun 2013 05:56:57 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/24#comment:2
Message-ID: <064.9c6aec3e9813fc2933f6082d75e8e239@trac.tools.ietf.org>
References: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 24
In-Reply-To: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130625055709.58FD321F99C7@ietfa.amsl.com>
Resent-Date: Mon, 24 Jun 2013 22:57:08 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #24: Move JWS headers into signature block
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 05:57:10 -0000

#24: Move JWS headers into signature block

Changes (by ietf@augustcellars.com):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Closing per the discussion on the teleconference.

 We currently do not have a strong use case for per user items.   It will
 be possible in future versions to add a protected field to the per signer
 item and include both in the integrity protection in the event that a use
 case appears.

 There was no strong recommendation from the CFRG list if a hash
 substitution attack is either probable or possible.

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  signature@tools.ietf.org
 Priority:  major        |      Status:  closed
Component:  json-web-    |   Milestone:
  signature              |     Version:
 Severity:  -            |  Resolution:  wontfix
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/24#comment:2>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Mon Jun 24 23:00:54 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9A221E8086 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVkLlyqQwvFI for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:00:53 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 80CFB21F9EFB for <jose@ietf.org>; Mon, 24 Jun 2013 23:00:52 -0700 (PDT)
Received: from localhost ([127.0.0.1]:53322 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrMJ5-0008Ed-Tg; Tue, 25 Jun 2013 08:00:47 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 25 Jun 2013 06:00:47 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/25
Message-ID: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org>
X-Trac-Ticket-ID: 25
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130625060052.80CFB21F9EFB@ietfa.amsl.com>
Resent-Date: Mon, 24 Jun 2013 23:00:52 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 06:00:54 -0000

#25: Detached content for the ALTO use case

 When the ALTO use case was originally presented to the JOSE WG, it was
 does as a detached content signature.  The content would be carried in the
 HTTP body while the signature would be carried in the header.  This
 permits a roll out of the signature into current ALTO systems in a way
 that is backwards compatible.

 The current JWS documents do not have any way of doing a detached content
 signature encoding.  The following decisions need to be made:

 1.  Does the JOSE document support this use case or not?
 2.  If it does support this, does it do it by direct or indirect inclusion
 of the content?

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  signature              |   Keywords:
 Severity:  -            |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/25>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Mon Jun 24 23:09:37 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CA321F9FB2 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01Sy4blba+PR for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:09:36 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id AB12121F9E96 for <jose@ietf.org>; Mon, 24 Jun 2013 23:09:36 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54253 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrMRT-0006pX-18; Tue, 25 Jun 2013 08:09:27 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 25 Jun 2013 06:09:27 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/26
Message-ID: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org>
X-Trac-Ticket-ID: 26
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130625060936.AB12121F9E96@ietfa.amsl.com>
Resent-Date: Mon, 24 Jun 2013 23:09:36 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 06:09:37 -0000

#26: Allow for signature payload to not be base64 encoded

 Ticket #23 was closed because for signature computation, the header
 information must be base64 encoded due to security considerations.  This
 is not true for the payload.

 Payload does need to be restricted to the base64URL character set for the
 compact encoding, however it does not need to be restricted for the JSON
 encoding, it is the responsibility of JSON parsers/serializers not to
 change the encoding of a string field.

 For detached content, the payload can be binary without any transport
 problems.  For text the content needs to be UTF8 encoded (maybe) but not
 base64url encoded.  For compact messages it might need to be base64url
 encoded.

 Applications can and should (when necessary) specify that there is one
 encoding that needs to be used.  However for the general purpose library
 all that is needed is to say that we are passing in an octet string to be
 used.  A flag/function name choice can easily be used to determine if the
 passed in value needs to be utf8 encoded or utf8 and base64url encoded.  I
 have put this into my implementation with almost zero effort and it is
 still very easy to understand for callers.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  signature              |   Keywords:
 Severity:  -            |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/26>
jose <http://tools.ietf.org/jose/>


From ietf@augustcellars.com  Mon Jun 24 23:19:14 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDC021F9F60 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O443bqIE1vzH for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:19:08 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 2C73621F8B33 for <jose@ietf.org>; Mon, 24 Jun 2013 23:19:07 -0700 (PDT)
Received: from Philemon (ip-64-134-138-86.public.wayport.net [64.134.138.86]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id F2CBF38EE8; Mon, 24 Jun 2013 23:19:05 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739436787EB2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436787EB2A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 24 Jun 2013 23:18:07 -0700
Message-ID: <019f01ce716b$c40e6480$4c2b2d80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01CE7131.17B24BA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFu1YhbhvKKzJg8MhN51L4B2pAQtJoFK2Dw
Content-Language: en-us
Cc: draft-ietf-jose-json-web-encryption@tools.ietf.org, jose@ietf.org
Subject: Re: [jose] Keys in the documents
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 06:19:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01A0_01CE7131.17B24BA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I have gone through the process of trying to use this, and I have also sat
down to think about how I would like to use the examples and I would suggest
the following:

 

There be one or two JWK sets that are defined at the start of appendix A.  

 

.         All of the keys (public, private and secret) be included in the
JWK sets

.         We assign, for testing purposes, a URL to each of the JWK sets
defined

.         Each example then either has the necessary data to find the key
from the correct JWK Set (and possibly the correct JWK Set via a jku) or the
text defines which of the keys is to be used.

.         There should be examples of many (most? All?) of the key location
methods between the JWS and JWE drafts.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Friday, June 21, 2013 8:58 AM
To: Matt Miller (mamille2); Richard Barnes
Cc: Jim Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org;
jose@ietf.org
Subject: RE: [jose] Keys in the documents

 

Will do.

  _____  

From: Matt Miller (mamille2)
Sent: 6/21/2013 6:06 AM
To: Richard Barnes
Cc: Jim Schaad; draft-ietf-jose-json-web-encryption@tools.ietf.org;
jose@ietf.org
Subject: Re: [jose] Keys in the documents

+1

On Jun 20, 2013, at 8:48 PM, Richard Barnes <rlb@ipv.sx>
wrote:

> +1
> 
> On Thursday, June 20, 2013, Jim Schaad wrote:
> 
>> Is there any reason not to provide the public and private keys in the
>> appendixes as JWK objects?  This would make them easier to understand and
>> put them into a format that one expects to be understood by JOSE
systems.*
>> ***
>> 
>> ** **
>> 
>> Jim****
>> 
>> ** **
>> 

- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.


------=_NextPart_000_01A0_01CE7131.17B24BA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:318583253;
	mso-list-type:hybrid;
	mso-list-template-ids:-1075810210 1758485650 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I have gone through the process of trying to use this, and I have =
also sat down to think about how I would like to use the examples and I =
would suggest the following:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There be one or two JWK sets that are defined at the start of =
appendix A.&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>All of the keys (public, private and secret) be included in the JWK =
sets<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We assign, for testing purposes, a URL to each of the JWK sets =
defined<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Each example then either has the necessary data to find the key from =
the correct JWK Set (and possibly the correct JWK Set via a jku) or the =
text defines which of the keys is to be used.<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There should be examples of many (most? All?) of the key location =
methods between the JWS and JWE drafts.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Jim<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Friday, =
June 21, 2013 8:58 AM<br><b>To:</b> Matt Miller (mamille2); Richard =
Barnes<br><b>Cc:</b> Jim Schaad; =
draft-ietf-jose-json-web-encryption@tools.ietf.org; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Keys in the =
documents<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Will =
do.<o:p></o:p></span></p></div></div><div class=3DMsoNormal =
align=3Dcenter style=3D'text-align:center'><hr size=3D2 width=3D"100%" =
align=3Dcenter></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From: =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Matt Miller =
(mamille2)</span><br><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Sent: =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>6/21/2013 =
6:06 AM</span><br><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>To: =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Richard =
Barnes</span><br><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Cc: =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Jim Schaad; =
<a =
href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">draft-=
ietf-jose-json-web-encryption@tools.ietf.org</a>; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a></span><br><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Subject: =
</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Re: [jose] =
Keys in the documents</span><br><br>+1<br><br>On Jun 20, 2013, at 8:48 =
PM, Richard Barnes &lt;<a =
href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt;<br>wrote:<br><br>&gt; =
+1<br>&gt; <br>&gt; On Thursday, June 20, 2013, Jim Schaad =
wrote:<br>&gt; <br>&gt;&gt; Is there any reason not to provide the =
public and private keys in the<br>&gt;&gt; appendixes as JWK =
objects?&nbsp; This would make them easier to understand and<br>&gt;&gt; =
put them into a format that one expects to be understood by JOSE =
systems.*<br>&gt;&gt; ***<br>&gt;&gt; <br>&gt;&gt; ** **<br>&gt;&gt; =
<br>&gt;&gt; Jim****<br>&gt;&gt; <br>&gt;&gt; ** **<br>&gt;&gt; =
<br><br>- m&amp;m<br><br>Matt Miller &lt; <a =
href=3D"mailto:mamille2@cisco.com">mamille2@cisco.com</a> &gt;<br>Cisco =
Systems, Inc.<o:p></o:p></p></div></div></body></html>
------=_NextPart_000_01A0_01CE7131.17B24BA0--


From trac+jose@trac.tools.ietf.org  Mon Jun 24 23:30:19 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0680D21F9FD8 for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOzRqbU1ua+L for <jose@ietfa.amsl.com>; Mon, 24 Jun 2013 23:30:18 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 60AF521F9FCB for <jose@ietf.org>; Mon, 24 Jun 2013 23:30:18 -0700 (PDT)
Received: from localhost ([127.0.0.1]:56203 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrMlQ-0004Mx-FC; Tue, 25 Jun 2013 08:30:04 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Tue, 25 Jun 2013 06:30:04 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/27
Message-ID: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org>
X-Trac-Ticket-ID: 27
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130625063018.60AF521F9FCB@ietfa.amsl.com>
Resent-Date: Mon, 24 Jun 2013 23:30:18 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 06:30:19 -0000

#27: member names MUST be unique needs additional text

 Based on the discussions on the JSON mailing list, it is clear that there
 will never be a requirement on parsers that member names at a lexical
 scope need to be unique.

 Based on the discussions on the JSON mailing list, it is clear that if
 there are two members with the same name, it is not predictable if you
 will get an error, both elements the first element or the last element.
 It will be highly parser dependent.

 From this we need to include additional text on why names need to be
 unique and how to go about checking that they are.  We will also need to
 include advice about what to do if a system is unable to provide the
 uniqueness requirement.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  signature              |   Keywords:
 Severity:  -            |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/27>
jose <http://tools.ietf.org/jose/>


From ietf@augustcellars.com  Tue Jun 25 09:51:51 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859D721E80A1 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 09:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPLTw7sVaYLb for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 09:51:41 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2C821E8099 for <jose@ietf.org>; Tue, 25 Jun 2013 09:51:38 -0700 (PDT)
Received: from Philemon (ip-64-134-138-86.public.wayport.net [64.134.138.86]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 8EA342CA23 for <jose@ietf.org>; Tue, 25 Jun 2013 09:51:36 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Tue, 25 Jun 2013 09:50:40 -0700
Message-ID: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_020B_01CE7189.73EEA140"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5xxBwfJ6lb4g6/QO2bDRCHQ9LMhg==
Content-Language: en-us
Subject: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 16:51:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_020B_01CE7189.73EEA140
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Agenda has been posted
http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interi
m-2013-jose-3

 


------=_NextPart_000_020B_01CE7189.73EEA140
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Agenda has =
been posted <a =
href=3D"http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/ag=
enda-interim-2013-jose-3">http://www.ietf.org/proceedings/interim/2013/07=
/01/jose/agenda/agenda-interim-2013-jose-3</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_020B_01CE7189.73EEA140--


From ietf@augustcellars.com  Tue Jun 25 09:54:26 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3033011E8114 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 09:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TV3NI1sQLJbn for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 09:54:20 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 9A85111E811E for <jose@ietf.org>; Tue, 25 Jun 2013 09:54:18 -0700 (PDT)
Received: from Philemon (ip-64-134-138-86.public.wayport.net [64.134.138.86]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 6D32738EFE for <jose@ietf.org>; Tue, 25 Jun 2013 09:54:18 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>
Date: Tue, 25 Jun 2013 09:53:22 -0700
Message-ID: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0210_01CE7189.D45AC5E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5xxGXFBxC1FARbRReYSyWIKtodvA==
Content-Language: en-us
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 16:54:26 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0210_01CE7189.D45AC5E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

We now have two documents - one from Richard and one from Mike - which
provide the two different ways that have been proposed for doing key
wrapping with an AEAD algorithm.

 

Please review the two documents and provide comments to the list.

 

Jim

 


------=_NextPart_000_0210_01CE7189.D45AC5E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>We now =
have two documents &#8211; one from Richard and one from Mike &#8211; =
which provide the two different ways that have been proposed for doing =
key wrapping with an AEAD algorithm.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the two documents and provide comments to the =
list.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0210_01CE7189.D45AC5E0--


From Michael.Jones@microsoft.com  Tue Jun 25 16:18:33 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9172021E80A9 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 16:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQGMFWqeuFo3 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 16:18:28 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0235.outbound.protection.outlook.com [207.46.163.235]) by ietfa.amsl.com (Postfix) with ESMTP id 23BA811E80FB for <jose@ietf.org>; Tue, 25 Jun 2013 16:18:27 -0700 (PDT)
Received: from BN1BFFO11FD005.protection.gbl (10.58.52.200) by BN1AFFO11HUB033.protection.gbl (10.58.52.144) with Microsoft SMTP Server (TLS) id 15.0.707.0; Tue, 25 Jun 2013 23:18:19 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD005.mail.protection.outlook.com (10.58.53.65) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Tue, 25 Jun 2013 23:18:18 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Tue, 25 Jun 2013 23:18:17 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: 'Jim Schaad' <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5x+kWA5ynNruFyScOmFXp2dnVQrA==
Date: Tue, 25 Jun 2013 23:18:16 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367898761TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(5383001)(377454003)(16236675002)(6806003)(79102001)(33656001)(76176001)(74662001)(15202345003)(47446002)(63696002)(56816003)(74502001)(76786001)(74366001)(46102001)(76796001)(51856001)(77096001)(20776003)(74876001)(74706001)(65816001)(81542001)(53806001)(69226001)(80022001)(31966008)(19300405004)(66066001)(512954002)(77982001)(59766001)(47736001)(76482001)(54316002)(55846006)(16406001)(49866001)(47976001)(50986001)(4396001)(54356001)(71186001)(56776001)(81342001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB033; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0888B1D284
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 23:18:33 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367898761TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like =
a substantially simpler approach than http://tools.ietf.org/html/draft-barn=
es-jose-key-wrapping-01.  This is evident by several metrics:

*         Number of proposed changes:  The Jones draft proposes no changes =
to any of the current specs.  It simply defines an encoding for GCM and add=
s registry entries for it.  Whereas the Barnes draft proposes a major restr=
ucturing - listing 4 major changes in the introduction and 4 smaller change=
s.

*         Normative text size:  The Jones GCM key wrap approach requires on=
ly 7 normative sentences in 1/2 page of text.  The Barnes draft has four pa=
ges of normative text, along with an extensive introduction describing the =
proposed complete restructuring of JWS and JWE.

We don't need to boil the ocean with a total redesign to enable AEAD key wr=
apping.  It can already easily be done with the current specs simply by def=
ining new algorithms.  The approach taken in http://tools.ietf.org/html/dra=
ft-jones-jose-aes-gcm-key-wrap-00 would work for any AEAD algorithm.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

We now have two documents - one from Richard and one from Mike - which prov=
ide the two different ways that have been proposed for doing key wrapping w=
ith an AEAD algorithm.

Please review the two documents and provide comments to the list.

Jim


--_000_4E1F6AAD24975D4BA5B168042967394367898761TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"http://tool=
s.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">http://tools.ietf.org=
/html/draft-jones-jose-aes-gcm-key-wrap-00</a> seems like a substantially s=
impler approach than
<a href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">ht=
tp://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; This =
is evident by several metrics:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Number of prop=
osed changes:&nbsp; The Jones draft proposes no changes to any of the curre=
nt specs.&nbsp; It simply defines an encoding for GCM and adds registry ent=
ries for it.&nbsp; Whereas the Barnes draft proposes
 a major restructuring &#8211; listing 4 major changes in the introduction =
and 4 smaller changes.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Normative text=
 size:&nbsp; The Jones GCM key wrap approach requires only 7 normative sent=
ences in 1/2 page of text.&nbsp; The Barnes draft has four pages of normati=
ve text, along with an extensive introduction
 describing the proposed complete restructuring of JWS and JWE.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We don&#8217;t need to=
 boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; It=
 can already easily be done with the current specs simply by defining new a=
lgorithms.&nbsp; The approach taken in
<a href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00"=
>http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> would =
work for any AEAD algorithm.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 25, 2013 9:53 AM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We now have two documents &#8211; one from Richard a=
nd one from Mike &#8211; which provide the two different ways that have bee=
n proposed for doing key wrapping with an AEAD algorithm.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the two documents and provide comments=
 to the list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367898761TK5EX14MBXC283r_--

From ve7jtb@ve7jtb.com  Tue Jun 25 16:29:29 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D15D21E80BE for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 16:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzYUtZQZnhAT for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 16:29:28 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 501F821E80B8 for <jose@ietf.org>; Tue, 25 Jun 2013 16:29:28 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id aq17so27461437iec.8 for <jose@ietf.org>; Tue, 25 Jun 2013 16:29:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=iabpXwmBCgEAjU6PtXj8CCd6GA6ZiXUJx6y0UJ32b0k=; b=J3CG3tcV98TdPYGg05USj2hi8NlJ51wDxC7/Th6fDggxkyNHkwDjuB5G2kStaEw7/G vlzO34wRBL6Ve4bTnoSMfWePL0aUt8Ei//6NbJF3Ilp4zZR/Ifjvwx8Rg41ABt12c48L 9Ss9R033usgcEP3pp6Y8pdaDoO3LPs4Ad98gKd5sjewtefTIzWQsaN7IqNjCXTDPgTYG +lO/mW1V6/t1LPF3JJzRymvd4vjiC0o4HmkAEHwpGLgMRhq1uEKtfDN1HaO4wlk5GlsK jZ4scz1zTLLgZFQYpL4wqW/QwsXw17iHxfj+Q3JLe13uHpdhgpCmCLPOzcF2HPFLmVJN eonw==
X-Received: by 10.42.68.145 with SMTP id x17mr622701ici.110.1372202967792; Tue, 25 Jun 2013 16:29:27 -0700 (PDT)
Received: from [192.168.1.216] (190-20-31-145.baf.movistar.cl. [190.20.31.145]) by mx.google.com with ESMTPSA id j3sm5516285igv.4.2013.06.25.16.29.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Jun 2013 16:29:26 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_62C35973-1FD6-4CD1-A0F6-82A2BC0DDC97"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Tue, 25 Jun 2013 19:28:55 -0400
Message-Id: <AB09929C-35FA-4185-94BD-DBE6F57083DF@ve7jtb.com>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQn2dNqlH6ZLFK+1o690wLXwZ2rIJgG1sunh8/vVuImEUp/e40aEaIdelDbs2MstrUVJR9a7
Cc: 'Jim Schaad' <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 25 Jun 2013 23:29:29 -0000

--Apple-Mail=_62C35973-1FD6-4CD1-A0F6-82A2BC0DDC97
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DD7A1A4A-5435-43AE-9427-4C27ABF71DED"


--Apple-Mail=_DD7A1A4A-5435-43AE-9427-4C27ABF71DED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I prefer the approach Mike is proposing.   It is overall simper and less =
restructuring.

John B.
On 2013-06-25, at 7:18 PM, Mike Jones <Michael.Jones@microsoft.com> =
wrote:

> http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems =
like a substantially simpler approach =
thanhttp://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01.  This =
is evident by several metrics:
> =B7         Number of proposed changes:  The Jones draft proposes no =
changes to any of the current specs.  It simply defines an encoding for =
GCM and adds registry entries for it.  Whereas the Barnes draft proposes =
a major restructuring =96 listing 4 major changes in the introduction =
and 4 smaller changes.
> =B7         Normative text size:  The Jones GCM key wrap approach =
requires only 7 normative sentences in 1/2 page of text.  The Barnes =
draft has four pages of normative text, along with an extensive =
introduction describing the proposed complete restructuring of JWS and =
JWE.
> =20
> We don=92t need to boil the ocean with a total redesign to enable AEAD =
key wrapping.  It can already easily be done with the current specs =
simply by defining new algorithms.  The approach taken in =
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would =
work for any AEAD algorithm.
> =20
>                                                                 -- =
Mike
> =20
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of Jim Schaad
> Sent: Tuesday, June 25, 2013 9:53 AM
> To: jose@ietf.org
> Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
> =20
> We now have two documents =96 one from Richard and one from Mike =96 =
which provide the two different ways that have been proposed for doing =
key wrapping with an AEAD algorithm.
> =20
> Please review the two documents and provide comments to the list.
> =20
> Jim
> =20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_DD7A1A4A-5435-43AE-9427-4C27ABF71DED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><base href=3D"x-msg://42/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">I prefer the approach Mike is =
proposing. &nbsp; It is overall simper and less =
restructuring.<div><br></div><div>John B.<br><div><div>On 2013-06-25, at =
7:18 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a=
>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"color: rgb(31, 73, 125); "><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00" =
style=3D"color: purple; text-decoration: underline; =
">http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a><span=
 class=3D"Apple-converted-space">&nbsp;</span>seems like a substantially =
simpler approach than<a =
href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01" =
style=3D"color: purple; text-decoration: underline; =
">http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; =
This is evident by several metrics:<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -0.25in; "><span style=3D"font-family: =
Symbol; color: rgb(31, 73, 125); "><span>=B7<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; =
line-height: normal; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"color: rgb(31, 73, 125); ">Number of proposed changes:&nbsp; =
The Jones draft proposes no changes to any of the current specs.&nbsp; =
It simply defines an encoding for GCM and adds registry entries for =
it.&nbsp; Whereas the Barnes draft proposes a major restructuring =96 =
listing 4 major changes in the introduction and 4 smaller =
changes.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt =
0.5in; font-size: 11pt; font-family: Calibri, sans-serif; text-indent: =
-0.25in; "><span style=3D"font-family: Symbol; color: rgb(31, 73, 125); =
"><span>=B7<span style=3D"font-style: normal; font-variant: normal; =
font-weight: normal; font-size: 7pt; line-height: normal; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"color: rgb(31, 73, 125); ">Normative text size:&nbsp; The Jones =
GCM key wrap approach requires only 7 normative sentences in 1/2 page of =
text.&nbsp; The Barnes draft has four pages of normative text, along =
with an extensive introduction describing the proposed complete =
restructuring of JWS and JWE.<o:p></o:p></span></div><div style=3D"margin:=
 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"color: rgb(31, 73, 125); ">We =
don=92t need to boil the ocean with a total redesign to enable AEAD key =
wrapping.&nbsp; It can already easily be done with the current specs =
simply by defining new algorithms.&nbsp; The approach taken in<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00" =
style=3D"color: purple; text-decoration: underline; =
">http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a><span=
 class=3D"Apple-converted-space">&nbsp;</span>would work for any AEAD =
algorithm.<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"color: rgb(31, 73, 125); =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; -- Mike<o:p></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"color: rgb(31, 73, 125); ">&nbsp;</span></div><div><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in; "><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><b><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jose-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">jose-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:jose-bounces@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">mailto:jose-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Jim =
Schaad<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, June 25, 2013 9:53 =
AM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:jose@ietf.org" style=3D"color: purple; text-decoration: =
underline; ">jose@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[jose] Issue #13 - use =
AES-GCM for Key Wrapping<o:p></o:p></span></div></div></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">We =
now have two documents =96 one from Richard and one from Mike =96 which =
provide the two different ways that have been proposed for doing key =
wrapping with an AEAD algorithm.<o:p></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Please review the =
two documents and provide comments to the list.<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Jim<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div>___________________________________________=
____<br>jose mailing list<br><a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/jose</div></blockquote></div><br></div></body></html>=

--Apple-Mail=_DD7A1A4A-5435-43AE-9427-4C27ABF71DED--

--Apple-Mail=_62C35973-1FD6-4CD1-A0F6-82A2BC0DDC97
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI1MjMyODU1WjAjBgkqhkiG9w0BCQQxFgQUNgJgbrZW
RvzE6LOuljYWneQYO3kwgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEABhUIrguWLUx9kVOO05a+wTOyBpN6HL2YIwTnabdo
s9yTCOqVmG/aSLrWvs3eXB/aG8IORvgdfBIldtEve4nUrTAMKPSE2c7jy7sI9SjXgy5JC71KXfLz
XlOrN6h6/72Nx8no2ptius1iy81cUNBA2zhN6JCLH1KCfiD44yeKA6Lam8aPQtIhJaI0TQOrU9Zx
4xVXxYfaNux0srEfuoO2ezXSSGJJkZM2ek7wfCgFJYxSeHBaVsS/CgfVYANu/O90gTON6uvqLTAS
rEo7CtxEVOnVDmOz6lY0ijdGJ2BM6TvfeJhr2XQmYgaFf4NkYfGsVUSoWQIbkZp+CwoNBmZilAAA
AAAAAA==

--Apple-Mail=_62C35973-1FD6-4CD1-A0F6-82A2BC0DDC97--

From trac+jose@trac.tools.ietf.org  Tue Jun 25 17:08:18 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86FCD21E80EC for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VMmYYLx3f1t for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:08:17 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B4B6D21E80F7 for <jose@ietf.org>; Tue, 25 Jun 2013 17:08:17 -0700 (PDT)
Received: from localhost ([127.0.0.1]:32869 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrdHN-0006Mr-Dl; Wed, 26 Jun 2013 02:08:09 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Wed, 26 Jun 2013 00:08:09 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1
Message-ID: <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org>
X-Trac-Ticket-ID: 25
In-Reply-To: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130626000817.B4B6D21E80F7@ietfa.amsl.com>
Resent-Date: Tue, 25 Jun 2013 17:08:17 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 00:08:18 -0000

#25: Detached content for the ALTO use case


Comment (by michael.jones@microsoft.com):

 Detached signatures was one of the complicated features of XMLDSIG that
 caused substantial interop problems.  Iâ€™d thought that there was already
 substantial sentiment in the working group not to do this because of the
 high complexity/benefit ratio.

 The good news, however, is that a form of detached signatures is EASY to
 build one layer up the stack by signing a hash of the detached content.
 ALTO could easily do this.

 Thereâ€™s already a deployed example of this, in fact.  OpenID Connect
 includes a hash of the OAuth Access Token as a claim in the ID Token
 issued with it.  This allows the holder of the ID Token to verify that
 token substitution of a different Access Token value has not been
 performed by an attacker.  This works with JWS as it is today.

 I therefore suggest that we recommend this technique to ALTO and add a
 description of it in the ALTO section of the Use Cases document and close
 this issue as â€œwonâ€™t fixâ€�.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  signature              |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Tue Jun 25 17:22:54 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22BC711E8160 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMYk5DFxDYrb for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:22:52 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id EA4D521F9D64 for <jose@ietf.org>; Tue, 25 Jun 2013 17:22:51 -0700 (PDT)
Received: from localhost ([127.0.0.1]:33712 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrdVV-0000Hd-4J; Wed, 26 Jun 2013 02:22:45 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Wed, 26 Jun 2013 00:22:45 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1
Message-ID: <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org>
X-Trac-Ticket-ID: 26
In-Reply-To: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130626002251.EA4D521F9D64@ietfa.amsl.com>
Resent-Date: Tue, 25 Jun 2013 17:22:51 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 00:22:54 -0000

#26: Allow for signature payload to not be base64 encoded


Comment (by michael.jones@microsoft.com):

 Having multiple ways to do something is one of the classic pitfalls to
 avoid in standards.  They tend to generate interop problems because
 developers will often only build the way that they think they need, never
 getting around to the others.   I donâ€™t think the potential benefits of
 having multiple ways to encode the payload outweigh this cost.

 Next, this feature would only work with the JSON serialization; it would
 not work for the Compact Serialization because the payload must be URL
 safe.  The base64url encoding accomplishes that, and so is a necessary
 part of the encoding.  Having the two serializations diverge in this
 manner seems suboptimal.

 Third, I am concerned that the payload will sometimes change during
 transmission if not encoded in some manner.  Tabs can change to spaces.
 LFs can change to CRLFs.  HTML is notorious for adding a blank at the end
 of each line.  Two spaces can change to a space and a non-breaking space.
 Etc.  Not encoding the payload would open us up to all of these potential
 modification-during-transmission problems â€“ all of which would render the
 JWS useless by breaking the signature.

 Finally, this feature seems to be motivated by detached signatures, which
 per my comment on Ticket #25, can be accomplished at the application layer
 without adding general-purpose support for detached signatures.  Thus, I
 donâ€™t think this related feature is needed either.

 For all these reasons, I believe that this issue should be closed as
 â€œwonâ€™t fixâ€�.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  signature              |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1>
jose <http://tools.ietf.org/jose/>


From Michael.Jones@microsoft.com  Tue Jun 25 17:32:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5DB21E80CA for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XSDYu2buxlC for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:32:20 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC3411E816B for <jose@ietf.org>; Tue, 25 Jun 2013 17:32:20 -0700 (PDT)
Received: from BN1BFFO11FD009.protection.gbl (10.58.52.200) by BN1BFFO11HUB025.protection.gbl (10.58.53.135) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 26 Jun 2013 00:32:18 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD009.mail.protection.outlook.com (10.58.53.69) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 26 Jun 2013 00:32:18 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Wed, 26 Jun 2013 00:31:36 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Teleconference July 1 Agenda
Thread-Index: Ac5xxBwfJ6lb4g6/QO2bDRCHQ9LMhgAP3tNA
Date: Wed, 26 Jun 2013 00:31:36 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394367899098@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com>
In-Reply-To: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B168042967394367899098TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(164054003)(30513003)(497574002)(189002)(199002)(377454003)(76796001)(46102001)(77096001)(33656001)(76786001)(76482001)(74366001)(56816003)(53806001)(31966008)(55846006)(81542001)(51856001)(65816001)(20776003)(81342001)(54356001)(71186001)(74662001)(6806003)(56776001)(80022001)(512954002)(74876001)(63696002)(77982001)(15202345003)(47976001)(59766001)(16406001)(69226001)(74706001)(79102001)(16236675002)(49866001)(19300405004)(54316002)(47446002)(50986001)(66066001)(16297215004)(4396001)(74502001)(47736001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB025; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08897B549D
Subject: Re: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 00:32:26 -0000

--_000_4E1F6AAD24975D4BA5B168042967394367899098TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please add these issues to the agenda:  #5, #14, and #15.  Suggested agenda=
 text follows.

Issue #5 - Unclear instructions for key management
                Discuss closing this issue as "fixed", as text addressing i=
t was added in the -09 drafts

Issue #14 - Support longer wrapped keys than OAEP allows
                Discuss closing this issue as "won't fix", as it will not o=
ccur in practice

Issue #15 - At least one key indicator should be mandatory
                Discuss closing this issue as "fixed", as text addressing i=
t was added in -11, as proposed by the WG in Denver

                                                                Thanks,
                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Tuesday, June 25, 2013 9:51 AM
To: jose@ietf.org
Subject: [jose] Teleconference July 1 Agenda

Agenda has been posted http://www.ietf.org/proceedings/interim/2013/07/01/j=
ose/agenda/agenda-interim-2013-jose-3


--_000_4E1F6AAD24975D4BA5B168042967394367899098TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please add these issue=
s to the agenda:&nbsp; #5, #14, and #15.&nbsp; Suggested agenda text follow=
s.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #5 - Unclear ins=
tructions for key management<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;fixed&#8221;, as text addressing it was adde=
d in the -09 drafts<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #14 - Support lo=
nger wrapped keys than OAEP allows<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;won&#8217;t fix&#8221;, as it will not occur=
 in practice<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #15 - At least o=
ne key indicator should be mandatory<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;fixed&#8221;, as text addressing it was adde=
d in -11, as proposed by the WG in Denver<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 25, 2013 9:51 AM<br>
<b>To:</b> jose@ietf.org<br>
<b>Subject:</b> [jose] Teleconference July 1 Agenda<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Agenda has been posted <a href=3D"http://www.ietf.or=
g/proceedings/interim/2013/07/01/jose/agenda/agenda-interim-2013-jose-3">
http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-inter=
im-2013-jose-3</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B168042967394367899098TK5EX14MBXC283r_--

From trac+jose@trac.tools.ietf.org  Tue Jun 25 17:41:21 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B8521F9AD1 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDR7AtxvclLn for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 17:41:21 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id C878921F9A69 for <jose@ietf.org>; Tue, 25 Jun 2013 17:41:20 -0700 (PDT)
Received: from localhost ([127.0.0.1]:34889 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UrdnM-0006qz-RV; Wed, 26 Jun 2013 02:41:12 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Wed, 26 Jun 2013 00:41:12 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1
Message-ID: <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org>
X-Trac-Ticket-ID: 27
In-Reply-To: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-signature@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com, n-sakimura@nri.co.jp, ve7jtb@ve7jtb.com
Resent-Message-Id: <20130626004120.C878921F9A69@ietfa.amsl.com>
Resent-Date: Tue, 25 Jun 2013 17:41:20 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 00:41:21 -0000

#27: member names MUST be unique needs additional text


Comment (by michael.jones@microsoft.com):

 The JWS draft currently says:

         The Header Parameter Names within the JWS Header MUST be unique;
         JWSs with duplicate Header Parameter Names MUST be rejected.

 How about changing this to:

         The Header Parameter Names within the JWS Header MUST be unique;
         JWSs with duplicate Header Parameter Names MUST be rejected.
         This is necessary to prevent attacks in which the same JWS might
 be interpreted
         in different ways by different implementations and to prevent
 attackers
         from hiding extra content in duplicate member values.
         If the platformâ€™s JSON parser does not reject input with duplicate
 member names,
         the input will first need to be separately parsed to reject these
 invalid inputs
         before using the platformâ€™s parser.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  signature@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  signature              |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
jose <http://tools.ietf.org/jose/>


From odonoghue@isoc.org  Tue Jun 25 21:04:42 2013
Return-Path: <odonoghue@isoc.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFF811E8193 for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 21:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sn2zVN8cfvjF for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 21:04:38 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id A713611E8199 for <jose@ietf.org>; Tue, 25 Jun 2013 21:04:37 -0700 (PDT)
Received: from BLUPR06MB180.namprd06.prod.outlook.com (10.242.190.27) by BLUPR06MB177.namprd06.prod.outlook.com (10.242.190.22) with Microsoft SMTP Server (TLS) id 15.0.702.21; Wed, 26 Jun 2013 04:04:29 +0000
Received: from BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.30]) by BLUPR06MB180.namprd06.prod.outlook.com ([169.254.7.137]) with mapi id 15.00.0702.005; Wed, 26 Jun 2013 04:04:29 +0000
From: Karen O'Donoghue <odonoghue@isoc.org>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: status of WGLC on - draft-ietf-jose-use-cases
Thread-Index: AQHOciJBy56K2M8QVEGKfFZZru/Lug==
Date: Wed, 26 Jun 2013 04:04:28 +0000
Message-ID: <A13981F3-83DF-4519-8173-6A10FA00E71F@isoc.org>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com> <06f001ce663d$75b3d100$611b7300$@augustcellars.com>
In-Reply-To: <06f001ce663d$75b3d100$611b7300$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.245.107.12]
x-forefront-prvs: 08897B549D
x-forefront-antispam-report: SFV:NSPM; SFS:(189002)(199002)(69224002)(377454003)(24454002)(74366001)(16406001)(81342001)(81542001)(79102001)(47446002)(56816003)(53806001)(74662001)(74502001)(76786001)(77096001)(76796001)(74706001)(31966008)(33656001)(77982001)(74876001)(69226001)(16236675002)(54356001)(59766001)(47976001)(4396001)(50986001)(80022001)(51856001)(49866001)(47736001)(66066001)(65816001)(36756003)(63696002)(54316002)(76482001)(56776001)(46102001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR06MB177; H:BLUPR06MB180.namprd06.prod.outlook.com; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_A13981F383DF451981736A10FA00E71Fisocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
Subject: [jose] status of WGLC on - draft-ietf-jose-use-cases
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 04:04:42 -0000

--_000_A13981F383DF451981736A10FA00E71Fisocorg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

The WGLC on draft-ietf-jose-use-cases has closed. As a result of the WGLC, =
the chairs request the editor to update the document to add the additional =
use case and to address the additional comments posted on the list. Upon su=
ccessful completion of the revision, the document will be forwarded to the =
IESG.

Thanks for all who reviewed the document.

Regards,
Karen


On Jun 10, 2013, at 8:48 PM, Jim Schaad wrote:

This is a reminder to do this in the next week.  We need both positive and =
negative reviews to judge consensus.

Jim


From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Thursday, May 30, 2013 9:16 AM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Working Group Last Call - draft-ietf-jose-use-cases
Importance: High

<chair>

This message starts the Working Group Last Call on the Use Cases document.

Minor issues should be sent to the list

Major issues (those that should block the document from proceeding to the I=
ESG) should be sent to the list and an issue created in the tracker.

The final day for Last Call comments is June 16, 2013


Jim

_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose


--_000_A13981F383DF451981736A10FA00E71Fisocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <3D3509EC976BB24882A2AAE82EB1B821@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<base href=3D"x-msg://987/">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Folks,
<div><br>
</div>
<div>The WGLC on draft-ietf-jose-use-cases has closed. As a result of the W=
GLC, the chairs request the editor to update the document to add the additi=
onal use case and to address the additional comments posted on the list. Up=
on successful completion of the
 revision, the document will be forwarded to the IESG.</div>
<div><br>
</div>
<div>Thanks for all who reviewed the document.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Karen</div>
<div><br>
</div>
<div><br>
<div>
<div>On Jun 10, 2013, at 8:48 PM, Jim Schaad wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style=3D"color: rgb(31, 73, 125); ">This is a reminder to do this in =
the next week.&nbsp; We need both positive and negative reviews to judge co=
nsensus.<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style=3D"color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style=3D"color: rgb(31, 73, 125); ">Jim<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style=3D"color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<span style=3D"color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"border-top-style: none; border-right-style: none; border-bott=
om-style: none; border-width: initial; border-color: initial; border-left-s=
tyle: solid; border-left-color: blue; border-left-width: 1.5pt; padding-top=
: 0in; padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; ">
<div>
<div style=3D"border-right-style: none; border-bottom-style: none; border-l=
eft-style: none; border-width: initial; border-color: initial; border-top-s=
tyle: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; p=
adding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in=
; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">From:=
</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;=
 "><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:jos=
e-bounces@ietf.org" style=3D"color: blue; text-decoration: underline; ">jos=
e-bounces@ietf.org</a><span class=3D"Apple-converted-space">&nbsp;</span>[m=
ailto:jose-bounces@ietf.org]<span class=3D"Apple-converted-space">&nbsp;</s=
pan><b>On
 Behalf Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Jim Schaad=
<br>
<b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>Thursday, Ma=
y 30, 2013 9:16 AM<br>
<b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mai=
lto:jose@ietf.org" style=3D"color: blue; text-decoration: underline; ">jose=
@ietf.org</a><br>
<b>Subject:</b><span class=3D"Apple-converted-space">&nbsp;</span>[jose] Wo=
rking Group Last Call - draft-ietf-jose-use-cases<br>
<b>Importance:</b><span class=3D"Apple-converted-space">&nbsp;</span>High<o=
:p></o:p></span></div>
</div>
</div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
&lt;chair&gt;<o:p></o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
This message starts the Working Group Last Call on the Use Cases document.<=
o:p></o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Minor issues should be sent to the list<o:p></o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Major issues (those that should block the document from proceeding to the I=
ESG) should be sent to the list and an issue created in the tracker.<o:p></=
o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
The final day for Last Call comments is June 16, 2013<o:p></o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
Jim<o:p></o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<o:p>&nbsp;</o:p></div>
</div>
</div>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" style=3D"color: blue; text-decoration: und=
erline; ">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" style=3D"color: blue=
; text-decoration: underline; ">https://www.ietf.org/mailman/listinfo/jose<=
/a></div>
</span></blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_A13981F383DF451981736A10FA00E71Fisocorg_--

From roland.hedberg@adm.umu.se  Tue Jun 25 23:52:27 2013
Return-Path: <roland.hedberg@adm.umu.se>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD84521E808E for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 23:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58IhsEdpsy7A for <jose@ietfa.amsl.com>; Tue, 25 Jun 2013 23:52:23 -0700 (PDT)
Received: from mail.ad.umu.se (umdac-ch2.ad.umu.se [130.239.1.247]) by ietfa.amsl.com (Postfix) with ESMTP id 2015D21F9EB8 for <jose@ietf.org>; Tue, 25 Jun 2013 23:52:22 -0700 (PDT)
Received: from UMDAC-CCR1.ad.umu.se ([169.254.1.56]) by UMDAC-CH2.ad.umu.se ([130.239.1.247]) with mapi; Wed, 26 Jun 2013 08:52:07 +0200
From: Roland Hedberg <roland.hedberg@adm.umu.se>
To: "jose@ietf.org" <jose@ietf.org>
Date: Wed, 26 Jun 2013 08:52:09 +0200
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5yOaxqqBEt5GvYQvW1Aubs4WGOUg==
Message-ID: <6036825F-6F06-412E-89B1-523BC10D1AA9@adm.umu.se>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <AB09929C-35FA-4185-94BD-DBE6F57083DF@ve7jtb.com>
In-Reply-To: <AB09929C-35FA-4185-94BD-DBE6F57083DF@ve7jtb.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, sv-SE
Content-Type: multipart/mixed; boundary="_003_6036825F6F06412E89B1523BC10D1AA9admumuse_"
MIME-Version: 1.0
Cc: John Bradley <ve7jtb@ve7jtb.com>, Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 06:52:28 -0000

--_003_6036825F6F06412E89B1523BC10D1AA9admumuse_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Likewise, I also prefer Mike's proposal.

26 jun 2013 kl. 01:28 skrev John Bradley <ve7jtb@ve7jtb.com>:

> I prefer the approach Mike is proposing.   It is overall simper and less =
restructuring.
>=20
> John B.
> On 2013-06-25, at 7:18 PM, Mike Jones <Michael.Jones@microsoft.com> wrote=
:
>=20
>> http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems li=
ke a substantially simpler approach thanhttp://tools.ietf.org/html/draft-ba=
rnes-jose-key-wrapping-01.  This is evident by several metrics:
>> =B7         Number of proposed changes:  The Jones draft proposes no cha=
nges to any of the current specs.  It simply defines an encoding for GCM an=
d adds registry entries for it.  Whereas the Barnes draft proposes a major =
restructuring =96 listing 4 major changes in the introduction and 4 smaller=
 changes.
>> =B7         Normative text size:  The Jones GCM key wrap approach requir=
es only 7 normative sentences in 1/2 page of text.  The Barnes draft has fo=
ur pages of normative text, along with an extensive introduction describing=
 the proposed complete restructuring of JWS and JWE.
>> =20
>> We don=92t need to boil the ocean with a total redesign to enable AEAD k=
ey wrapping.  It can already easily be done with the current specs simply b=
y defining new algorithms.  The approach taken in http://tools.ietf.org/htm=
l/draft-jones-jose-aes-gcm-key-wrap-00 would work for any AEAD algorithm.
>> =20
>>                                                                 -- Mike
>> =20
>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of =
Jim Schaad
>> Sent: Tuesday, June 25, 2013 9:53 AM
>> To: jose@ietf.org
>> Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
>> =20
>> We now have two documents =96 one from Richard and one from Mike =96 whi=
ch provide the two different ways that have been proposed for doing key wra=
pping with an AEAD algorithm.
>> =20
>> Please review the two documents and provide comments to the list.
>> =20
>> Jim
>> =20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>=20

--_003_6036825F6F06412E89B1523BC10D1AA9admumuse_
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Description: smime.p7s
Content-Disposition: attachment; filename="smime.p7s"; size=4507;
	creation-date="Wed, 26 Jun 2013 06:52:07 GMT";
	modification-date="Wed, 26 Jun 2013 06:52:07 GMT"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI1MjMyODU1WjAjBgkqhkiG9w0BCQQxFgQUNgJgbrZW
RvzE6LOuljYWneQYO3kwgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEABhUIrguWLUx9kVOO05a+wTOyBpN6HL2YIwTnabdo
s9yTCOqVmG/aSLrWvs3eXB/aG8IORvgdfBIldtEve4nUrTAMKPSE2c7jy7sI9SjXgy5JC71KXfLz
XlOrN6h6/72Nx8no2ptius1iy81cUNBA2zhN6JCLH1KCfiD44yeKA6Lam8aPQtIhJaI0TQOrU9Zx
4xVXxYfaNux0srEfuoO2ezXSSGJJkZM2ek7wfCgFJYxSeHBaVsS/CgfVYANu/O90gTON6uvqLTAS
rEo7CtxEVOnVDmOz6lY0ijdGJ2BM6TvfeJhr2XQmYgaFf4NkYfGsVUSoWQIbkZp+CwoNBmZilAAA
AAAAAA==

--_003_6036825F6F06412E89B1523BC10D1AA9admumuse_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=241;
	creation-date="Wed, 26 Jun 2013 06:52:07 GMT";
	modification-date="Wed, 26 Jun 2013 06:52:07 GMT"
Content-Transfer-Encoding: base64

PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBqb3Nl
IG1haWxpbmcgbGlzdA0KPiBqb3NlQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vam9zZQ0KDQotLSBSb2xhbmQNCiJFZHVjYXRpb24gaXMgdGhlIHBhdGgg
ZnJvbSBjb2NreSBpZ25vcmFuY2UgdG8gbWlzZXJhYmxlIHVuY2VydGFpbnR5LpQgLSBNYXJrIFR3
YWluDQoNCg0KDQoNCg==

--_003_6036825F6F06412E89B1523BC10D1AA9admumuse_--

From edmundjay@sbcglobal.net  Wed Jun 26 00:12:43 2013
Return-Path: <edmundjay@sbcglobal.net>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349D221E8119 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 00:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7g5ygDPYTIx for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 00:12:37 -0700 (PDT)
Received: from nm7-vm0.access.bullet.mail.mud.yahoo.com (nm7-vm0.access.bullet.mail.mud.yahoo.com [66.94.237.189]) by ietfa.amsl.com (Postfix) with ESMTP id 6633021E808E for <jose@ietf.org>; Wed, 26 Jun 2013 00:12:37 -0700 (PDT)
Received: from [66.94.237.193] by nm7.access.bullet.mail.mud.yahoo.com with NNFMP; 26 Jun 2013 07:12:36 -0000
Received: from [66.196.81.125] by tm4.access.bullet.mail.mud.yahoo.com with NNFMP; 26 Jun 2013 07:12:36 -0000
Received: from [127.0.0.1] by omp1001.access.mail.bf1.yahoo.com with NNFMP; 26 Jun 2013 07:12:36 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 640952.38709.bm@omp1001.access.mail.bf1.yahoo.com
Received: (qmail 53228 invoked by uid 60001); 26 Jun 2013 07:12:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1372230756; bh=BeJlbg4W6kcOtMX21rRDhIo5aQzYyKlInfuqErxdSAM=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=TjiiRt0UkorLvE175P3CfQpKY/PglFlPSwTr9pH9tqtxKppMJaaVo38h86gQteV8+lvs7vDnUWPD63upULNUgQGHeChTsfKVKt/OlSzYM97I+M7iNZMi2PPz0BJnCl+pOO5DCyXdYybBmMXSN/zp/+1378942o/vA+Aas2n2bxg=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ceqaSRhFuiC9JvqWkqNDaRRcYHjQDBKxv/QrGrEAvTMqYOdDrRo/tZYdXI/hC67TVoXSRjWHR9PRuFC9Y1n1oo0776GLwcb0qWkj5dsRKa2S3CPLCdxibdBp4O4PPVI9cGw34xadtQdeTFEeCVrysm5F1tueFrdrUlMOm0NUxrw=;
X-YMail-OSG: ZFgHR_YVM1kAV_qXb_70xFlpftYV2jT.ziSXRKxykizill3 PEfEYaoH22_aggvT3u17y1KKV_D1P3kHSLpQxvM6Rkp0B4jz19FxXeWzCUIV AgEXEXCcvJlnqEMok2eKK.Pcfn6_NG_3n2x3g0PJbO31Oi4Q2rrCVNnowbvE x34OkYlF8xVC7kqjWZM9sh5ntVqJeDxOxfBdFW.5HYjllv0M7CgTDb6uPStF DMhNjI50D6tLw6JmjrBBoSNm81sQ07xaKeblLfer8SYHvwp_2R8_CrriZTgr HDKweBq.aIr.MdfyIEh2VJb7.09PDL3mkuBPCWBEY3op3h0Cgx8gO4tIJ_qG MW7mt_3UIC6cBx_0hayuhp_uQRELcrokSds9i.oJXvvGGilNwDf4DxPmaety OSTr76XswgDZReEy766UGNykYYinzzygPnGH95we4wxBpjkTGVWgfOJM9Fbf HvNRBbvlliWcEEECBvuuLQ7VgX24joaPYwpzBc0C5rnp5e1DGYzO.INHCtRd m68LvkdShvYHFKx9itL20uqLtFslgzeFMfxVp.1LrqpWEFVZDc9413TbXsNL hAB4MLDPlCnwumn0zdg--
Received: from [70.36.254.42] by web184405.mail.bf1.yahoo.com via HTTP; Wed, 26 Jun 2013 00:12:35 PDT
X-Rocket-MIMEInfo: 002.001, SSdtIGluIGZhdm9yIG9mIHN1cHBvcnRpbmcgTWlrZSdzIHByb3Bvc2FsIGR1ZSB0byBzaW1wbGljaXR5LgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCiBGcm9tOiBSb2xhbmQgSGVkYmVyZyA8cm9sYW5kLmhlZGJlcmdAYWRtLnVtdS5zZT4KVG86ICJqb3NlQGlldGYub3JnIiA8am9zZUBpZXRmLm9yZz4gCkNjOiBKb2huIEJyYWRsZXkgPHZlN2p0YkB2ZTdqdGIuY29tPjsgTWlrZSBKb25lcyA8TWljaGFlbC5Kb25lc0BtaWNyb3NvZnQuY29tPjsgSmltIFNjaGFhZCA8aWV0ZkBhdWd1c3RjZWwBMAEBAQE-
X-RocketYMMF: edmundjay@sbcglobal.net
X-Mailer: YahooMailWebService/0.8.148.554
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <AB09929C-35FA-4185-94BD-DBE6F57083DF@ve7jtb.com> <6036825F-6F06-412E-89B1-523BC10D1AA9@adm.umu.se>
Message-ID: <1372230755.52922.YahooMailNeo@web184405.mail.bf1.yahoo.com>
Date: Wed, 26 Jun 2013 00:12:35 -0700 (PDT)
From: Edmund Jay <ejay@mgi1.com>
To: Roland Hedberg <roland.hedberg@adm.umu.se>, "jose@ietf.org" <jose@ietf.org>
In-Reply-To: <6036825F-6F06-412E-89B1-523BC10D1AA9@adm.umu.se>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1412092350-1960711502-1372230755=:52922"
Cc: John Bradley <ve7jtb@ve7jtb.com>, Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Edmund Jay <ejay@mgi1.com>
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, 26 Jun 2013 07:12:43 -0000

---1412092350-1960711502-1372230755=:52922
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I'm in favor of supporting Mike's proposal due to simplicity.=0A=0A=0A_____=
___________________________=0A From: Roland Hedberg <roland.hedberg@adm.umu=
.se>=0ATo: "jose@ietf.org" <jose@ietf.org> =0ACc: John Bradley <ve7jtb@ve7j=
tb.com>; Mike Jones <Michael.Jones@microsoft.com>; Jim Schaad <ietf@augustc=
ellars.com> =0ASent: Tuesday, June 25, 2013 11:52 PM=0ASubject: Re: [jose] =
Issue #13 - use AES-GCM for Key Wrapping=0A =0A=0ALikewise, I also prefer M=
ike's proposal.=0A=0A26 jun 2013 kl. 01:28 skrev John Bradley <ve7jtb@ve7jt=
b.com>:=0A=0A> I prefer the approach Mike is proposing.=C2=A0  It is overal=
l simper and less restructuring.=0A> =0A> John B.=0A> On 2013-06-25, at 7:1=
8 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:=0A> =0A>> http://tool=
s.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like a substanti=
ally simpler approach thanhttp://tools.ietf.org/html/draft-barnes-jose-key-=
wrapping-01.=C2=A0 This is evident by several metrics:=0A>> =C2=B7=C2=A0 =
=C2=A0 =C2=A0 =C2=A0  Number of proposed changes:=C2=A0 The Jones draft pro=
poses no changes to any of the current specs.=C2=A0 It simply defines an en=
coding for GCM and adds registry entries for it.=C2=A0 Whereas the Barnes d=
raft proposes a major restructuring =E2=80=93 listing 4 major changes in th=
e introduction and 4 smaller changes.=0A>> =C2=B7=C2=A0 =C2=A0 =C2=A0 =C2=
=A0  Normative text size:=C2=A0 The Jones GCM key wrap approach requires on=
ly 7 normative sentences in 1/2 page of text.=C2=A0 The Barnes draft has fo=
ur pages of normative text, along with an extensive introduction describing=
 the proposed complete restructuring of JWS and JWE.=0A>>=C2=A0 =0A>> We do=
n=E2=80=99t need to boil the ocean with a total redesign to enable AEAD key=
 wrapping.=C2=A0 It can already easily be done with the current specs simpl=
y by defining new algorithms.=C2=A0 The approach taken in http://tools.ietf=
.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would work for any AEAD algo=
rithm.=0A>>=C2=A0 =0A>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0  -- Mike=0A>>=C2=A0 =0A>> From: jose-bounces@ietf.=
org [mailto:jose-bounces@ietf.org] On Behalf Of Jim Schaad=0A>> Sent: Tuesd=
ay, June 25, 2013 9:53 AM=0A>> To: jose@ietf.org=0A>> Subject: [jose] Issue=
 #13 - use AES-GCM for Key Wrapping=0A>>=C2=A0 =0A>> We now have two docume=
nts =E2=80=93 one from Richard and one from Mike =E2=80=93 which provide th=
e two different ways that have been proposed for doing key wrapping with an=
 AEAD algorithm.=0A>>=C2=A0 =0A>> Please review the two documents and provi=
de comments to the list.=0A>>=C2=A0 =0A>> Jim=0A>>=C2=A0 =0A>> ____________=
___________________________________=0A>> jose mailing list=0A>> jose@ietf.o=
rg=0A>> https://www.ietf.org/mailman/listinfo/jose=0A> =0A=0A______________=
_________________________________=0Ajose mailing list=0Ajose@ietf.org=0Ahtt=
ps://www.ietf.org/mailman/listinfo/jose
---1412092350-1960711502-1372230755=:52922
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ta=
homa, new york, times, serif;font-size:10pt"><div><span>I'm in favor of sup=
porting Mike's proposal due to simplicity.</span></div><div><br></div>  <di=
v style=3D"font-family: tahoma, 'new york', times, serif; font-size: 10pt; =
"> <div style=3D"font-family: 'times new roman', 'new york', times, serif; =
font-size: 12pt; "> <div dir=3D"ltr"> <hr size=3D"1">  <font size=3D"2" fac=
e=3D"Arial"> <b><span style=3D"font-weight:bold;">From:</span></b> Roland H=
edberg &lt;roland.hedberg@adm.umu.se&gt;<br> <b><span style=3D"font-weight:=
 bold;">To:</span></b> "jose@ietf.org" &lt;jose@ietf.org&gt; <br><b><span s=
tyle=3D"font-weight: bold;">Cc:</span></b> John Bradley &lt;ve7jtb@ve7jtb.c=
om&gt;; Mike Jones &lt;Michael.Jones@microsoft.com&gt;; Jim Schaad &lt;ietf=
@augustcellars.com&gt; <br> <b><span style=3D"font-weight: bold;">Sent:</sp=
an></b> Tuesday, June 25, 2013 11:52 PM<br> <b><span style=3D"font-weight:
 bold;">Subject:</span></b> Re: [jose] Issue #13 - use AES-GCM for Key Wrap=
ping<br> </font> </div> <div class=3D"y_msg_container"><br>=0ALikewise, I a=
lso prefer Mike's proposal.<br><br>26 jun 2013 kl. 01:28 skrev John Bradley=
 &lt;<a ymailto=3D"mailto:ve7jtb@ve7jtb.com" href=3D"mailto:ve7jtb@ve7jtb.c=
om">ve7jtb@ve7jtb.com</a>&gt;:<br><br>&gt; I prefer the approach Mike is pr=
oposing.&nbsp;  It is overall simper and less restructuring.<br>&gt; <br>&g=
t; John B.<br>&gt; On 2013-06-25, at 7:18 PM, Mike Jones &lt;<a ymailto=3D"=
mailto:Michael.Jones@microsoft.com" href=3D"mailto:Michael.Jones@microsoft.=
com">Michael.Jones@microsoft.com</a>&gt; wrote:<br>&gt; <br>&gt;&gt; http:/=
/tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like a subs=
tantially simpler approach thanhttp://tools.ietf.org/html/draft-barnes-jose=
-key-wrapping-01.&nbsp; This is evident by several metrics:<br>&gt;&gt; =C2=
=B7&nbsp; &nbsp; &nbsp; &nbsp;  Number of proposed changes:&nbsp; The Jones=
 draft proposes no changes to any of the current specs.&nbsp; It simply def=
ines an encoding for GCM and adds registry entries for it.&nbsp;
 Whereas the Barnes draft proposes a major restructuring =E2=80=93 listing =
4 major changes in the introduction and 4 smaller changes.<br>&gt;&gt; =C2=
=B7&nbsp; &nbsp; &nbsp; &nbsp;  Normative text size:&nbsp; The Jones GCM ke=
y wrap approach requires only 7 normative sentences in 1/2 page of text.&nb=
sp; The Barnes draft has four pages of normative text, along with an extens=
ive introduction describing the proposed complete restructuring of JWS and =
JWE.<br>&gt;&gt;&nbsp; <br>&gt;&gt; We don=E2=80=99t need to boil the ocean=
 with a total redesign to enable AEAD key wrapping.&nbsp; It can already ea=
sily be done with the current specs simply by defining new algorithms.&nbsp=
; The approach taken in <a href=3D"http://tools.ietf.org/html/draft-jones-j=
ose-aes-gcm-key-wrap-00" target=3D"_blank">http://tools.ietf.org/html/draft=
-jones-jose-aes-gcm-key-wrap-00</a> would work for any AEAD algorithm.<br>&=
gt;&gt;&nbsp; <br>&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp;  -- Mike<br>&gt;&gt;&nbsp; <br>&gt;&gt; From: <a ymailto=3D"mai=
lto:jose-bounces@ietf.org" href=3D"mailto:jose-bounces@ietf.org">jose-bounc=
es@ietf.org</a> [mailto:<a ymailto=3D"mailto:jose-bounces@ietf.org" href=3D=
"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a>] On Behalf Of Jim =
Schaad<br>&gt;&gt; Sent: Tuesday, June 25, 2013 9:53 AM<br>&gt;&gt; To: <a =
ymailto=3D"mailto:jose@ietf.org" href=3D"mailto:jose@ietf.org">jose@ietf.or=
g</a><br>&gt;&gt; Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping<=
br>&gt;&gt;&nbsp; <br>&gt;&gt; We now have two documents =E2=80=93 one from=
 Richard and one from Mike =E2=80=93 which provide the two different ways t=
hat have been proposed for doing key wrapping with an AEAD algorithm.<br>&g=
t;&gt;&nbsp; <br>&gt;&gt; Please review the two documents and provide comme=
nts to the
 list.<br>&gt;&gt;&nbsp; <br>&gt;&gt; Jim<br>&gt;&gt;&nbsp; <br>&gt;&gt; __=
_____________________________________________<br>&gt;&gt; jose mailing list=
<br>&gt;&gt; <a ymailto=3D"mailto:jose@ietf.org" href=3D"mailto:jose@ietf.o=
rg">jose@ietf.org</a><br>&gt;&gt; <a href=3D"https://www.ietf.org/mailman/l=
istinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose<=
/a><br>&gt; <br><br>_______________________________________________<br>jose=
 mailing list<br><a ymailto=3D"mailto:jose@ietf.org" href=3D"mailto:jose@ie=
tf.org">jose@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listin=
fo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><b=
r><br><br></div> </div> </div>  </div></body></html>
---1412092350-1960711502-1372230755=:52922--

From ietf@augustcellars.com  Wed Jun 26 11:30:54 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695FE11E8125 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qEj2JKJprtuR for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id B985211E811F for <jose@ietf.org>; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 6915D38F36; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'jose issue tracker'" <trac+jose@trac.tools.ietf.org>, <draft-ietf-jose-json-web-signature@tools.ietf.org>, <michael.jones@microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org>
In-Reply-To: <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org>
Date: Wed, 26 Jun 2013 11:29:52 -0700
Message-ID: <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvmX0JYbA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 18:30:54 -0000

<no hat>

I consider myself to be reasonably competent in both English and =
Technical English.  I have no idea what I am supposed to be doing to =
deal with the text below.  Does this mean that I need to write an =
independent parser?  What about cases where it is coming in on a stream =
and I don't get to see the data before the parse occurs?  How are they =
interpreted differently?  What exactly is this supposed to be =
addressing.  Much of this could be skipped when we said don't do it.  =
Since this is no longer a viable statement due to the state of parsers, =
we need to be more explicit and say what is going on.

No I don't consider the suggested text to be adequate.

> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
> jose issue tracker
> Sent: Tuesday, June 25, 2013 5:41 PM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> michael.jones@microsoft.com
> Cc: jose@ietf.org
> Subject: Re: [jose] #27: member names MUST be unique needs additional =
text
>=20
> #27: member names MUST be unique needs additional text
>=20
>=20
> Comment (by michael.jones@microsoft.com):
>=20
>  The JWS draft currently says:
>=20
>          The Header Parameter Names within the JWS Header MUST be =
unique;
>          JWSs with duplicate Header Parameter Names MUST be rejected.
>=20
>  How about changing this to:
>=20
>          The Header Parameter Names within the JWS Header MUST be =
unique;
>          JWSs with duplicate Header Parameter Names MUST be rejected.
>          This is necessary to prevent attacks in which the same JWS =
might  be
> interpreted
>          in different ways by different implementations and to prevent =
 attackers
>          from hiding extra content in duplicate member values.
>          If the platform s JSON parser does not reject input with =
duplicate
> member names,
>          the input will first need to be separately parsed to reject =
these  invalid
> inputs
>          before using the platform s parser.
>=20
> --
> =
-------------------------+----------------------------------------------
> -------------------------+---
>  Reporter:               |       Owner:  draft-ietf-jose-json-web-
>   ietf@augustcellars.com |  signature@tools.ietf.org
>      Type:  defect       |      Status:  new
>  Priority:  major        |   Milestone:
> Component:  json-web-    |     Version:
>   signature              |  Resolution:
>  Severity:  -            |
>  Keywords:               |
> =
-------------------------+----------------------------------------------
> -------------------------+---
>=20
> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From ietf@augustcellars.com  Wed Jun 26 11:30:54 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E56611E811F for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oi9rfXKc+5oI for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id B712D11E811D for <jose@ietf.org>; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 21FA638F35; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-json-web-signature@tools.ietf.org>, <michael.jones@microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org>
In-Reply-To: <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org>
Date: Wed, 26 Jun 2013 11:29:52 -0700
Message-ID: <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbtMM0AVMbmndwUUG6vntocHGkoALWvDclmhcGO3A=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 18:30:54 -0000

Having multiple ways to do something can frequently buy you a great deal =
of benefit.  However, in this case it is my library that is doing this =
and not the standard.

The client gives the library an 8-bit string.  The library signs that =
string.  The library puts that string into the payload field.

The client needs to make the 8-bit string URL safe if it wants to use =
compact encoding.

Where is there two ways of doing something?

Jim


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
> jose issue tracker
> Sent: Tuesday, June 25, 2013 5:23 PM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> michael.jones@microsoft.com
> Cc: jose@ietf.org
> Subject: Re: [jose] #26: Allow for signature payload to not be base64 =
encoded
>=20
> #26: Allow for signature payload to not be base64 encoded
>=20
>=20
> Comment (by michael.jones@microsoft.com):
>=20
>  Having multiple ways to do something is one of the classic pitfalls =
to  avoid in
> standards.  They tend to generate interop problems because  developers =
will
> often only build the way that they think they need, never
>  getting around to the others.   I don t think the potential benefits =
of
>  having multiple ways to encode the payload outweigh this cost.
>=20
>  Next, this feature would only work with the JSON serialization; it =
would  not
> work for the Compact Serialization because the payload must be URL  =
safe.
> The base64url encoding accomplishes that, and so is a necessary  part =
of the
> encoding.  Having the two serializations diverge in this  manner seems
> suboptimal.
>=20
>  Third, I am concerned that the payload will sometimes change during
> transmission if not encoded in some manner.  Tabs can change to =
spaces.
>  LFs can change to CRLFs.  HTML is notorious for adding a blank at the =
end  of
> each line.  Two spaces can change to a space and a non-breaking space.
>  Etc.  Not encoding the payload would open us up to all of these =
potential
> modification-during-transmission problems   all of which would render =
the
> JWS useless by breaking the signature.
>=20
>  Finally, this feature seems to be motivated by detached signatures, =
which  per
> my comment on Ticket #25, can be accomplished at the application layer
> without adding general-purpose support for detached signatures.  Thus, =
I  don
> t think this related feature is needed either.
>=20
>  For all these reasons, I believe that this issue should be closed as  =
 won t fix .
>=20
> --
> =
-------------------------+----------------------------------------------
> -------------------------+---
>  Reporter:               |       Owner:  draft-ietf-jose-json-web-
>   ietf@augustcellars.com |  signature@tools.ietf.org
>      Type:  defect       |      Status:  new
>  Priority:  major        |   Milestone:
> Component:  json-web-    |     Version:
>   signature              |  Resolution:
>  Severity:  -            |
>  Keywords:               |
> =
-------------------------+----------------------------------------------
> -------------------------+---
>=20
> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From ietf@augustcellars.com  Wed Jun 26 11:30:59 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3C311E81D0 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xkiUbUSgJOOy for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:54 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 01DC811E8120 for <jose@ietf.org>; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id D65AD38F38; Wed, 26 Jun 2013 11:30:49 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367899098@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367899098@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 11:29:52 -0700
Message-ID: <033c01ce729b$272470c0$756d5240$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_033D_01CE7260.7AC6AA30"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGcpZW0SYDqCTp0n8LDt7OsdLmuBgJzXos9mZg+KnA=
Content-Language: en-us
Subject: Re: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 18:30:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_033D_01CE7260.7AC6AA30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

#5 is blocked on getting information from Richard

#14 is blocked on issue #13

#15 still needs to get review.  I have sent you a number of comments about
this which need to be addressed.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Tuesday, June 25, 2013 5:32 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Teleconference July 1 Agenda

 

Please add these issues to the agenda:  #5, #14, and #15.  Suggested agenda
text follows.

 

Issue #5 - Unclear instructions for key management

                Discuss closing this issue as "fixed", as text addressing it
was added in the -09 drafts

 

Issue #14 - Support longer wrapped keys than OAEP allows

                Discuss closing this issue as "won't fix", as it will not
occur in practice

 

Issue #15 - At least one key indicator should be mandatory

                Discuss closing this issue as "fixed", as text addressing it
was added in -11, as proposed by the WG in Denver

 

                                                                Thanks,

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 25, 2013 9:51 AM
To: jose@ietf.org
Subject: [jose] Teleconference July 1 Agenda

 

Agenda has been posted
http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interi
m-2013-jose-3

 


------=_NextPart_000_033D_01CE7260.7AC6AA30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#5 is blocked on getting information from =
Richard<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#14 is blocked on issue =
#13<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#15 still needs to get review. &nbsp;I have sent =
you a number of comments about this which need to be =
addressed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Tuesday, June 25, 2013 5:32 PM<br><b>To:</b> Jim Schaad; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Teleconference July 1 =
Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Please add these issues to the agenda:&nbsp; #5, =
#14, and #15.&nbsp; Suggested agenda text =
follows.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #5 - Unclear =
instructions for key management<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;fixed&#8221;, as text addressing it was added in the -09 =
drafts<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #14 - Support =
longer wrapped keys than OAEP allows<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;won&#8217;t fix&#8221;, as it will not occur in =
practice<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #15 - At least one =
key indicator should be mandatory<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;fixed&#8221;, as text addressing it was added in -11, as proposed =
by the WG in Denver<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Tuesday, June 25, 2013 =
9:51 AM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] Teleconference July 1 Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Agenda has =
been posted <a =
href=3D"http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/ag=
enda-interim-2013-jose-3">http://www.ietf.org/proceedings/interim/2013/07=
/01/jose/agenda/agenda-interim-2013-jose-3</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_033D_01CE7260.7AC6AA30--


From ietf@augustcellars.com  Wed Jun 26 11:30:59 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4742811E8120 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3P8GiyIlkRmh for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 11:30:54 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 42AF511E8122 for <jose@ietf.org>; Wed, 26 Jun 2013 11:30:50 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 1B91D38F3A; Wed, 26 Jun 2013 11:30:50 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 11:29:52 -0700
Message-ID: <034101ce729b$27473b00$75d5b100$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0342_01CE7260.7AEAD400"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH9pEpqg6SA+ykRJHySAR3RzJ5mhJjptffw
Content-Language: en-us
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 18:30:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0342_01CE7260.7AEAD400
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

<no hat>

<sarcasm level="heavy">

 

I am shocked that you would possibly support this proposal.  It provides for
two ways of dealing with something.  It is my understanding that you never
support anything that has two ways of doing something.

 

How the AEAD algorithm parameters is handled completely differently for this
proposal and for the same algorithms being used in a CEK context.  This is
going to lead to confusion.

 

</sarcasm>

 

Your specification is missing some items that still need to be registered
Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined
in your document as well.

 

Your document ends up with a registration complexity that needs to be
thought about and dealt with as well.  For every new key wrap algorithm
added, you will need to register not only it alone but also it with every
different key agreement algorithm that is supported.  Thus adding a single
key wrap algorithm becomes a slight issue in terms of adding in all of the
different ways that it might be used.  This is a complexity issue that is
not discussed in the current draft.

 

I have not necessarily found that document size equals code size.  I have
implemented some very simple documents that were very difficult to code and
implemented some very long documents that were very easy to code.  So I
would not use that fact as a deciding factor.

 

(Once again I regret the fact that the group did not go with an object
descriptor for algorithms as this would have made all of this much simpler.
I actually immediately map from the string to an object description in my
JOSE implementation for simplicity reasons.  Not to mention that this is way
it needs to be done for the WebCrypto specficiation.)

 

Jim

 

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Tuesday, June 25, 2013 4:18 PM
To: 'Jim Schaad'; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like a
substantially simpler approach than
http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01.  This is
evident by several metrics:

.         Number of proposed changes:  The Jones draft proposes no changes
to any of the current specs.  It simply defines an encoding for GCM and adds
registry entries for it.  Whereas the Barnes draft proposes a major
restructuring - listing 4 major changes in the introduction and 4 smaller
changes.

.         Normative text size:  The Jones GCM key wrap approach requires
only 7 normative sentences in 1/2 page of text.  The Barnes draft has four
pages of normative text, along with an extensive introduction describing the
proposed complete restructuring of JWS and JWE.

 

We don't need to boil the ocean with a total redesign to enable AEAD key
wrapping.  It can already easily be done with the current specs simply by
defining new algorithms.  The approach taken in
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would work
for any AEAD algorithm.

 

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

We now have two documents - one from Richard and one from Mike - which
provide the two different ways that have been proposed for doing key
wrapping with an AEAD algorithm.

 

Please review the two documents and provide comments to the list.

 

Jim

 


------=_NextPart_000_0342_01CE7260.7AEAD400
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;no hat&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>&lt;sarcasm =
level=3D&#8221;heavy&#8221;&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am shocked that you =
would possibly support this proposal.&nbsp; It provides for two ways of =
dealing with something.&nbsp; It is my understanding that you never =
support anything that has two ways of doing =
something.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>How the AEAD algorithm =
parameters is handled completely differently for this proposal and for =
the same algorithms being used in a CEK context. &nbsp;This is going to =
lead to confusion.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;/sarcasm&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your specification is =
missing some items that still need to be registered&nbsp; Thus you also =
need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined in your =
document as well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your document ends up =
with a registration complexity that needs to be thought about and dealt =
with as well.&nbsp; For every new key wrap algorithm added, you will =
need to register not only it alone but also it with every different key =
agreement algorithm that is supported. &nbsp;Thus adding a single key =
wrap algorithm becomes a slight issue in terms of adding in all of the =
different ways that it might be used.&nbsp; This is a complexity issue =
that is not discussed in the current draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I have not necessarily =
found that document size equals code size.&nbsp; I have implemented some =
very simple documents that were very difficult to code and implemented =
some very long documents that were very easy to code.&nbsp; So I would =
not use that fact as a deciding factor.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>(Once again I regret the =
fact that the group did not go with an object descriptor for algorithms =
as this would have made all of this much simpler.&nbsp; I actually =
immediately map from the string to an object description in my JOSE =
implementation for simplicity reasons.&nbsp; Not to mention that this is =
way it needs to be done for the WebCrypto =
specficiation.)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Tuesday, June 25, 2013 4:18 PM<br><b>To:</b> 'Jim Schaad'; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for =
Key Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
seems like a substantially simpler approach than <a =
href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">htt=
p://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; =
This is evident by several metrics:<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Number of =
proposed changes:&nbsp; The Jones draft proposes no changes to any of =
the current specs.&nbsp; It simply defines an encoding for GCM and adds =
registry entries for it.&nbsp; Whereas the Barnes draft proposes a major =
restructuring &#8211; listing 4 major changes in the introduction and 4 =
smaller changes.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Normative =
text size:&nbsp; The Jones GCM key wrap approach requires only 7 =
normative sentences in 1/2 page of text.&nbsp; The Barnes draft has four =
pages of normative text, along with an extensive introduction describing =
the proposed complete restructuring of JWS and =
JWE.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>We don&#8217;t need to =
boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; =
It can already easily be done with the current specs simply by defining =
new algorithms.&nbsp; The approach taken in <a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
would work for any AEAD algorithm.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Tuesday, June 25, 2013 =
9:53 AM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We now have =
two documents &#8211; one from Richard and one from Mike &#8211; which =
provide the two different ways that have been proposed for doing key =
wrapping with an AEAD algorithm.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the two documents and provide comments to the =
list.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0342_01CE7260.7AEAD400--


From Michael.Jones@microsoft.com  Wed Jun 26 12:10:51 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233F011E81DC for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vgk+ecgVkKCq for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:10:46 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id 9732B11E812E for <jose@ietf.org>; Wed, 26 Jun 2013 12:10:45 -0700 (PDT)
Received: from BY2FFO11FD007.protection.gbl (10.1.15.202) by BY2FFO11HUB025.protection.gbl (10.1.14.111) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 26 Jun 2013 19:10:36 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD007.mail.protection.outlook.com (10.1.14.128) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 26 Jun 2013 19:10:36 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Wed, 26 Jun 2013 19:09:31 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] #26: Allow for signature payload to not be base64 encoded
Thread-Index: AQHOcgNOsVoAPXc/s02k5Wh9HChUEZlIUkQAgAAIucA=
Date: Wed, 26 Jun 2013 19:09:31 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789B3BC@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
In-Reply-To: <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(13464003)(51704005)(189002)(199002)(377454003)(69226001)(74706001)(77096001)(76482001)(76786001)(74662001)(74366001)(81342001)(31966008)(56816003)(46406003)(46102001)(53806001)(55846006)(76796001)(81542001)(80022001)(56776001)(4396001)(77982001)(74876001)(54356001)(51856001)(6806003)(47776003)(54316002)(63696002)(65816001)(20776003)(23726002)(561944002)(50466002)(47976001)(59766001)(16406001)(33656001)(49866001)(47736001)(79102001)(74502001)(47446002)(44976004)(66066001)(50986001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB025; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08897B549D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 19:10:51 -0000

Maybe I'm confused about what you were proposing.  These are the two ways o=
f doing something that I thought you were describing:

1.  Have the signature payload be base64url encoded (the status quo)
2.  Have the signature payload be unencoded in the JSON Serialization if a =
flag is set in the header

If you're proposing that the default be unencoded for the JSON Serializatio=
n, that has the pitfall that a simple syntactic transformation is no longer=
 possible between the Compact Serialization and the JSON Serialization.  Th=
e two would have unnecessarily diverged.

If I misunderstood your proposal, maybe you could describe it in closer to =
normative language - for instance, defining the flag you propose to say tha=
t the payload is not base64url encoded and saying what its semantics would =
be for the JSON Serialization and the Compact Serialization.

BTW, your response didn't address the point that a primary purpose of the b=
ase64url encoding is to harden the payload against changes that might other=
wise occur during transmission.  Not hardening the payload will almost cert=
ainly lead to hard-to-debug interop problems in practice.

				-- Mike

-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Wednesday, June 26, 2013 11:30 AM
To: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones
Cc: jose@ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encod=
ed

Having multiple ways to do something can frequently buy you a great deal of=
 benefit.  However, in this case it is my library that is doing this and no=
t the standard.

The client gives the library an 8-bit string.  The library signs that strin=
g.  The library puts that string into the payload field.

The client needs to make the 8-bit string URL safe if it wants to use compa=
ct encoding.

Where is there two ways of doing something?

Jim


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf=20
> Of jose issue tracker
> Sent: Tuesday, June 25, 2013 5:23 PM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> michael.jones@microsoft.com
> Cc: jose@ietf.org
> Subject: Re: [jose] #26: Allow for signature payload to not be base64=20
> encoded
>=20
> #26: Allow for signature payload to not be base64 encoded
>=20
>=20
> Comment (by michael.jones@microsoft.com):
>=20
>  Having multiple ways to do something is one of the classic pitfalls=20
> to  avoid in standards.  They tend to generate interop problems=20
> because  developers will often only build the way that they think they ne=
ed, never
>  getting around to the others.   I don t think the potential benefits of
>  having multiple ways to encode the payload outweigh this cost.
>=20
>  Next, this feature would only work with the JSON serialization; it=20
> would  not work for the Compact Serialization because the payload must be=
 URL  safe.
> The base64url encoding accomplishes that, and so is a necessary  part=20
> of the encoding.  Having the two serializations diverge in this =20
> manner seems suboptimal.
>=20
>  Third, I am concerned that the payload will sometimes change during=20
> transmission if not encoded in some manner.  Tabs can change to spaces.
>  LFs can change to CRLFs.  HTML is notorious for adding a blank at the=20
> end  of each line.  Two spaces can change to a space and a non-breaking s=
pace.
>  Etc.  Not encoding the payload would open us up to all of these potentia=
l
> modification-during-transmission problems   all of which would render the
> JWS useless by breaking the signature.
>=20
>  Finally, this feature seems to be motivated by detached signatures,=20
> which  per my comment on Ticket #25, can be accomplished at the=20
> application layer without adding general-purpose support for detached=20
> signatures.  Thus, I  don t think this related feature is needed either.
>=20
>  For all these reasons, I believe that this issue should be closed as   w=
on t fix .
>=20
> --
> -------------------------+--------------------------------------------
> -------------------------+--
> -------------------------+---
>  Reporter:               |       Owner:  draft-ietf-jose-json-web-
>   ietf@augustcellars.com |  signature@tools.ietf.org
>      Type:  defect       |      Status:  new
>  Priority:  major        |   Milestone:
> Component:  json-web-    |     Version:
>   signature              |  Resolution:
>  Severity:  -            |
>  Keywords:               |
> -------------------------+--------------------------------------------
> -------------------------+--
> -------------------------+---
>=20
> Ticket URL:=20
> <http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

From Michael.Jones@microsoft.com  Wed Jun 26 12:30:24 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D61411E8129 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhDKp4NPszVL for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:30:19 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id B8BB611E81D0 for <jose@ietf.org>; Wed, 26 Jun 2013 12:30:18 -0700 (PDT)
Received: from BL2FFO11FD017.protection.gbl (10.173.161.204) by BL2FFO11HUB042.protection.gbl (10.173.161.0) with Microsoft SMTP Server (TLS) id 15.0.717.3; Wed, 26 Jun 2013 19:30:11 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD017.mail.protection.outlook.com (10.173.161.35) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 26 Jun 2013 19:30:11 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Wed, 26 Jun 2013 19:30:00 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkA==
Date: Wed, 26 Jun 2013 19:29:59 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com>
In-Reply-To: <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(377454003)(51704005)(13464003)(4396001)(47976001)(54316002)(74662001)(47446002)(54356001)(69226001)(56776001)(47736001)(74366001)(44976004)(56816003)(55846006)(16406001)(59766001)(77982001)(23676002)(50986001)(79102001)(66066001)(51856001)(63696002)(31966008)(50466002)(76796001)(81342001)(76482001)(49866001)(74706001)(6806003)(81542001)(65816001)(47776003)(46102001)(53806001)(74502001)(80022001)(74876001)(33656001)(76786001)(77096001)(20776003); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB042; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08897B549D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 19:30:24 -0000

VGhlIG9wZXJhYmxlIHNlbnRlbmNlIGluIG15IHN1Z2dlc3RlZCB0ZXh0IGJlbG93IGlzIHRoaXMg
b25lOiAiSWYgdGhlIHBsYXRmb3JtJ3MgSlNPTiBwYXJzZXIgZG9lcyBub3QgcmVqZWN0IGlucHV0
IHdpdGggZHVwbGljYXRlIG1lbWJlciBuYW1lcywgdGhlIGlucHV0IHdpbGwgZmlyc3QgbmVlZCB0
byBiZSBzZXBhcmF0ZWx5IHBhcnNlZCB0byByZWplY3QgdGhlc2UgaW52YWxpZCBpbnB1dHMgYmVm
b3JlIHVzaW5nIHRoZSBwbGF0Zm9ybSdzIHBhcnNlciIuICBJbiBvdGhlciB3b3JkcywgaWYgdGhl
IEpTT04gcGFyc2VyIGluIHRoZSBkZXZlbG9wbWVudCBwbGF0Zm9ybSB5b3UgYXJlIHVzaW5nIGRv
ZXMgbm90IHJlamVjdCBpbnB1dHMgd2l0aCBkdXBsaWNhdGUgbWVtYmVyIG5hbWVzLCB5b3Ugd2ls
bCBuZWVkIHRvIHdyaXRlIGEgc2VwYXJhdGUgSlNPTiBwYXJzZXIgdGhhdCBkZXRlY3RzIHRoaXMg
aW52YWxpZCBpbnB1dCBhbmQgcmVqZWN0cyBpdC4NCg0KVGhpcyBwYXJzZXIgY291bGQgZWl0aGVy
IGp1c3QgYmUgYSB2YWxpZGF0b3IsIHJldHVybmluZyBUUlVFIG9yIEZBTFNFIGZvciB3aGV0aGVy
IHRoZSBKU09OIGlzIHZhbGlkIGZvciBKT1NFIC0gaW4gd2hpY2ggY2FzZSB5b3UnZCB0aGVuIHBh
c3MgYW55IGlucHV0cyB2YWxpZGF0aW5nIGFzIFRSVUUgdG8gdGhlIHBsYXRmb3JtJ3MgSlNPTiBw
YXJzZXIsIG9yIGl0IGNvdWxkIGJlIGEgcmVwbGFjZW1lbnQgcGFyc2VyLCBpbiB3aGljaCBjYXNl
IHlvdXIgY29kZSB3b3VsZCBub3QgdXNlIHRoZSBkZXZlbG9wbWVudCBwbGF0Zm9ybSdzIEpTT04g
cGFyc2VyIGF0IGFsbC4gIEkgc3VzcGVjdCBwZW9wbGUgd291bGQgYmUgbW9yZSBsaWtlbHkgdG8g
ZG8gdGhlIGZvcm1lciB0aGFuIHRoZSBsYXR0ZXIsIGJ1dCBib3RoIGFwcHJvYWNoZXMgYXJlIGVx
dWl2YWxlbnQuDQoNCkJUVywgaWYgaXQncyB5b3VyIHNlbnNlIHRoYXQgdGhlcmUncyBhIHByb2Js
ZW0gb2NjdXJyaW5nIGluIHRoZSBKU09OIHdvcmtpbmcgZ3JvdXAgd2l0aCByZXNwZWN0IHRvIGVu
YWJsaW5nIHN0cmljdCBKU09OIHBhcnNpbmcsIHdlIHByb2JhYmx5IG5lZWQgdG8gYmVjb21lIGFj
dGl2ZSB0aGVyZS4gIEZvciBpbnN0YW5jZSwgZXZlbiBpZiB0aGUgc3BlYyBhbGxvd3MgZHVwbGlj
YXRlIG1lbWJlciBuYW1lcyBsaWtlIHRoZSBFQ01BIHNwZWMgZG9lcywgdGhlIFJGQyBjb3VsZCBy
ZWNvbW1lbmQgb3IgcmVxdWlyZSB0aGF0IHBhcnNlcnMgc3VwcG9ydCBhICJzdHJpY3QiIG1vZGUs
IHdoaWNoIHJlamVjdHMgdGhlc2UgdW5uZWNlc3NhcmlseSBsYXggaW5wdXRzLiAgVGhlbiBKT1NF
IGltcGxlbWVudGF0aW9ucyBjb3VsZCB1c2UgdGhhdC4NCg0KCQkJCS0tIE1pa2UNCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEppbSBTY2hhYWQgW21haWx0bzppZXRmQGF1Z3Vz
dGNlbGxhcnMuY29tXSANClNlbnQ6IFdlZG5lc2RheSwgSnVuZSAyNiwgMjAxMyAxMTozMCBBTQ0K
VG86ICdqb3NlIGlzc3VlIHRyYWNrZXInOyBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItc2lnbmF0
dXJlQHRvb2xzLmlldGYub3JnOyBNaWtlIEpvbmVzDQpDYzogam9zZUBpZXRmLm9yZw0KU3ViamVj
dDogUkU6IFtqb3NlXSAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVkcyBhZGRp
dGlvbmFsIHRleHQNCg0KPG5vIGhhdD4NCg0KSSBjb25zaWRlciBteXNlbGYgdG8gYmUgcmVhc29u
YWJseSBjb21wZXRlbnQgaW4gYm90aCBFbmdsaXNoIGFuZCBUZWNobmljYWwgRW5nbGlzaC4gIEkg
aGF2ZSBubyBpZGVhIHdoYXQgSSBhbSBzdXBwb3NlZCB0byBiZSBkb2luZyB0byBkZWFsIHdpdGgg
dGhlIHRleHQgYmVsb3cuICBEb2VzIHRoaXMgbWVhbiB0aGF0IEkgbmVlZCB0byB3cml0ZSBhbiBp
bmRlcGVuZGVudCBwYXJzZXI/ICBXaGF0IGFib3V0IGNhc2VzIHdoZXJlIGl0IGlzIGNvbWluZyBp
biBvbiBhIHN0cmVhbSBhbmQgSSBkb24ndCBnZXQgdG8gc2VlIHRoZSBkYXRhIGJlZm9yZSB0aGUg
cGFyc2Ugb2NjdXJzPyAgSG93IGFyZSB0aGV5IGludGVycHJldGVkIGRpZmZlcmVudGx5PyAgV2hh
dCBleGFjdGx5IGlzIHRoaXMgc3VwcG9zZWQgdG8gYmUgYWRkcmVzc2luZy4gIE11Y2ggb2YgdGhp
cyBjb3VsZCBiZSBza2lwcGVkIHdoZW4gd2Ugc2FpZCBkb24ndCBkbyBpdC4gIFNpbmNlIHRoaXMg
aXMgbm8gbG9uZ2VyIGEgdmlhYmxlIHN0YXRlbWVudCBkdWUgdG8gdGhlIHN0YXRlIG9mIHBhcnNl
cnMsIHdlIG5lZWQgdG8gYmUgbW9yZSBleHBsaWNpdCBhbmQgc2F5IHdoYXQgaXMgZ29pbmcgb24u
DQoNCk5vIEkgZG9uJ3QgY29uc2lkZXIgdGhlIHN1Z2dlc3RlZCB0ZXh0IHRvIGJlIGFkZXF1YXRl
Lg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGpvc2UtYm91bmNlc0Bp
ZXRmLm9yZyBbbWFpbHRvOmpvc2UtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIA0KPiBPZiBq
b3NlIGlzc3VlIHRyYWNrZXINCj4gU2VudDogVHVlc2RheSwgSnVuZSAyNSwgMjAxMyA1OjQxIFBN
DQo+IFRvOiBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItc2lnbmF0dXJlQHRvb2xzLmlldGYub3Jn
Ow0KPiBtaWNoYWVsLmpvbmVzQG1pY3Jvc29mdC5jb20NCj4gQ2M6IGpvc2VAaWV0Zi5vcmcNCj4g
U3ViamVjdDogUmU6IFtqb3NlXSAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVk
cyBhZGRpdGlvbmFsIA0KPiB0ZXh0DQo+IA0KPiAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVu
aXF1ZSBuZWVkcyBhZGRpdGlvbmFsIHRleHQNCj4gDQo+IA0KPiBDb21tZW50IChieSBtaWNoYWVs
LmpvbmVzQG1pY3Jvc29mdC5jb20pOg0KPiANCj4gIFRoZSBKV1MgZHJhZnQgY3VycmVudGx5IHNh
eXM6DQo+IA0KPiAgICAgICAgICBUaGUgSGVhZGVyIFBhcmFtZXRlciBOYW1lcyB3aXRoaW4gdGhl
IEpXUyBIZWFkZXIgTVVTVCBiZSB1bmlxdWU7DQo+ICAgICAgICAgIEpXU3Mgd2l0aCBkdXBsaWNh
dGUgSGVhZGVyIFBhcmFtZXRlciBOYW1lcyBNVVNUIGJlIHJlamVjdGVkLg0KPiANCj4gIEhvdyBh
Ym91dCBjaGFuZ2luZyB0aGlzIHRvOg0KPiANCj4gICAgICAgICAgVGhlIEhlYWRlciBQYXJhbWV0
ZXIgTmFtZXMgd2l0aGluIHRoZSBKV1MgSGVhZGVyIE1VU1QgYmUgdW5pcXVlOw0KPiAgICAgICAg
ICBKV1NzIHdpdGggZHVwbGljYXRlIEhlYWRlciBQYXJhbWV0ZXIgTmFtZXMgTVVTVCBiZSByZWpl
Y3RlZC4NCj4gICAgICAgICAgVGhpcyBpcyBuZWNlc3NhcnkgdG8gcHJldmVudCBhdHRhY2tzIGlu
IHdoaWNoIHRoZSBzYW1lIEpXUyANCj4gbWlnaHQgIGJlIGludGVycHJldGVkDQo+ICAgICAgICAg
IGluIGRpZmZlcmVudCB3YXlzIGJ5IGRpZmZlcmVudCBpbXBsZW1lbnRhdGlvbnMgYW5kIHRvIHBy
ZXZlbnQgIGF0dGFja2Vycw0KPiAgICAgICAgICBmcm9tIGhpZGluZyBleHRyYSBjb250ZW50IGlu
IGR1cGxpY2F0ZSBtZW1iZXIgdmFsdWVzLg0KPiAgICAgICAgICBJZiB0aGUgcGxhdGZvcm0gcyBK
U09OIHBhcnNlciBkb2VzIG5vdCByZWplY3QgaW5wdXQgd2l0aCANCj4gZHVwbGljYXRlIG1lbWJl
ciBuYW1lcywNCj4gICAgICAgICAgdGhlIGlucHV0IHdpbGwgZmlyc3QgbmVlZCB0byBiZSBzZXBh
cmF0ZWx5IHBhcnNlZCB0byByZWplY3QgDQo+IHRoZXNlICBpbnZhbGlkIGlucHV0cw0KPiAgICAg
ICAgICBiZWZvcmUgdXNpbmcgdGhlIHBsYXRmb3JtIHMgcGFyc2VyLg0KPiANCj4gLS0NCj4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tDQo+IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0rLS0tDQo+ICBSZXBvcnRlcjogICAgICAgICAgICAgICB8ICAgICAgIE93
bmVyOiAgZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLQ0KPiAgIGlldGZAYXVndXN0Y2VsbGFycy5j
b20gfCAgc2lnbmF0dXJlQHRvb2xzLmlldGYub3JnDQo+ICAgICAgVHlwZTogIGRlZmVjdCAgICAg
ICB8ICAgICAgU3RhdHVzOiAgbmV3DQo+ICBQcmlvcml0eTogIG1ham9yICAgICAgICB8ICAgTWls
ZXN0b25lOg0KPiBDb21wb25lbnQ6ICBqc29uLXdlYi0gICAgfCAgICAgVmVyc2lvbjoNCj4gICBz
aWduYXR1cmUgICAgICAgICAgICAgIHwgIFJlc29sdXRpb246DQo+ICBTZXZlcml0eTogIC0gICAg
ICAgICAgICB8DQo+ICBLZXl3b3JkczogICAgICAgICAgICAgICB8DQo+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tKy0tLQ0KPiANCj4gVGlja2V0IFVSTDogDQo+IDxodHRwOi8vdHJhYy50b29scy5pZXRmLm9y
Zy93Zy9qb3NlL3RyYWMvdGlja2V0LzI3I2NvbW1lbnQ6MT4NCj4gam9zZSA8aHR0cDovL3Rvb2xz
LmlldGYub3JnL2pvc2UvPg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4gam9zZSBtYWlsaW5nIGxpc3QNCj4gam9zZUBpZXRmLm9yZw0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2pvc2UNCg0K

From Michael.Jones@microsoft.com  Wed Jun 26 12:36:45 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BC211E81EB for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixWEMwFv9GDO for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:36:40 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id B096E11E8127 for <jose@ietf.org>; Wed, 26 Jun 2013 12:36:40 -0700 (PDT)
Received: from BY2FFO11FD025.protection.gbl (10.1.15.200) by BY2FFO11HUB032.protection.gbl (10.1.14.177) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 26 Jun 2013 19:35:34 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD025.mail.protection.outlook.com (10.1.15.214) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 26 Jun 2013 19:35:34 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Wed, 26 Jun 2013 19:35:29 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Teleconference July 1 Agenda
Thread-Index: Ac5xxBwfJ6lb4g6/QO2bDRCHQ9LMhgAP3tNAACXjmAAAAhp/kA==
Date: Wed, 26 Jun 2013 19:35:28 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789B518@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367899098@TK5EX14MBXC283.redmond.corp.microsoft.com> <033c01ce729b$272470c0$756d5240$@augustcellars.com>
In-Reply-To: <033c01ce729b$272470c0$756d5240$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436789B518TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(164054003)(30513003)(497574002)(189002)(199002)(377454003)(69226001)(77096001)(74706001)(76482001)(76786001)(74662001)(74366001)(81342001)(31966008)(56816003)(46102001)(55846006)(53806001)(76796001)(81542001)(71186001)(512954002)(80022001)(56776001)(4396001)(77982001)(74876001)(15202345003)(51856001)(54356001)(6806003)(54316002)(63696002)(20776003)(65816001)(19300405004)(47976001)(59766001)(16406001)(16236675002)(49866001)(33656001)(47736001)(79102001)(74502001)(47446002)(44976004)(66066001)(16297215004)(50986001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB032; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08897B549D
Subject: Re: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 19:36:46 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436789B518TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Can we please set a time limit on #5, after which we will close the issue i=
f Richard hasn't produced the table he suggested?  This issue was addressed=
 two months and three drafts ago, which is ample time for the working group=
 to have reviewed the text.  At least to my way of thinking, it's not reaso=
nable to hold an issue open indefinitely due to inactivity of a potential c=
ontributor.

I'll look at your comments on #15 and try to respond before Monday's call.

                                                                Thanks,
                                                                -- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org
Subject: RE: [jose] Teleconference July 1 Agenda

#5 is blocked on getting information from Richard
#14 is blocked on issue #13
#15 still needs to get review.  I have sent you a number of comments about =
this which need to be addressed.

Jim


From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Tuesday, June 25, 2013 5:32 PM
To: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Teleconference July 1 Agenda

Please add these issues to the agenda:  #5, #14, and #15.  Suggested agenda=
 text follows.

Issue #5 - Unclear instructions for key management
                Discuss closing this issue as "fixed", as text addressing i=
t was added in the -09 drafts

Issue #14 - Support longer wrapped keys than OAEP allows
                Discuss closing this issue as "won't fix", as it will not o=
ccur in practice

Issue #15 - At least one key indicator should be mandatory
                Discuss closing this issue as "fixed", as text addressing i=
t was added in -11, as proposed by the WG in Denver

                                                                Thanks,
                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Tuesday, June 25, 2013 9:51 AM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Teleconference July 1 Agenda

Agenda has been posted http://www.ietf.org/proceedings/interim/2013/07/01/j=
ose/agenda/agenda-interim-2013-jose-3


--_000_4E1F6AAD24975D4BA5B16804296739436789B518TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Can we please set a ti=
me limit on #5, after which we will close the issue if Richard hasn&#8217;t=
 produced the table he suggested?&nbsp; This issue was addressed two months=
 and three drafts ago, which is ample time for
 the working group to have reviewed the text.&nbsp; At least to my way of t=
hinking, it&#8217;s not reasonable to hold an issue open indefinitely due t=
o inactivity of a potential contributor.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;ll look at you=
r comments on #15 and try to respond before Monday&#8217;s call.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Wednesday, June 26, 2013 11:30 AM<br>
<b>To:</b> Mike Jones; jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Teleconference July 1 Agenda<o:p></o:p></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">#5 is blocked on getti=
ng information from Richard<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">#14 is blocked on issu=
e #13<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">#15 still needs to get=
 review. &nbsp;I have sent you a number of comments about this which need t=
o be addressed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Tuesday, June 25, 2013 5:32 PM<br>
<b>To:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><b=
r>
<b>Subject:</b> RE: [jose] Teleconference July 1 Agenda<o:p></o:p></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please add these issue=
s to the agenda:&nbsp; #5, #14, and #15.&nbsp; Suggested agenda text follow=
s.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #5 - Unclear ins=
tructions for key management<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;fixed&#8221;, as text addressing it was adde=
d in the -09 drafts<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #14 - Support lo=
nger wrapped keys than OAEP allows<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;won&#8217;t fix&#8221;, as it will not occur=
 in practice<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Issue #15 - At least o=
ne key indicator should be mandatory<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discus=
s closing this issue as &#8220;fixed&#8221;, as text addressing it was adde=
d in -11, as proposed by the WG in Denver<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 25, 2013 9:51 AM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> [jose] Teleconference July 1 Agenda<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Agenda has been posted <a href=3D"http://www.ietf.or=
g/proceedings/interim/2013/07/01/jose/agenda/agenda-interim-2013-jose-3">
http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-inter=
im-2013-jose-3</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436789B518TK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Wed Jun 26 12:37:19 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCAE11E81F3 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9eJq9eSaIxbh for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 12:37:13 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 99D6411E812B for <jose@ietf.org>; Wed, 26 Jun 2013 12:37:13 -0700 (PDT)
Received: from BL2FFO11FD028.protection.gbl (10.173.161.200) by BL2FFO11HUB039.protection.gbl (10.173.160.245) with Microsoft SMTP Server (TLS) id 15.0.707.0; Wed, 26 Jun 2013 19:21:50 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD028.mail.protection.outlook.com (10.173.161.107) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Wed, 26 Jun 2013 19:21:50 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0136.001; Wed, 26 Jun 2013 19:21:39 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5x+kWA5ynNruFyScOmFXp2dnVQrAAoOBMAAAFzy1A=
Date: Wed, 26 Jun 2013 19:21:38 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <034101ce729b$27473b00$75d5b100$@augustcellars.com>
In-Reply-To: <034101ce729b$27473b00$75d5b100$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436789B458TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(5383001)(199002)(189002)(50986001)(47736001)(4396001)(51856001)(54356001)(49866001)(59766001)(47976001)(74876001)(76482001)(65816001)(69226001)(71186001)(19300405004)(81342001)(66066001)(55846006)(54316002)(512954002)(77982001)(44976004)(80022001)(16236675002)(56776001)(33656001)(561944002)(77096001)(81542001)(6806003)(56816003)(46102001)(74366001)(74706001)(76786001)(76796001)(74662001)(15202345003)(20776003)(16406001)(74502001)(47446002)(53806001)(63696002)(31966008)(79102001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB039; H:TK5EX14MLTC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08897B549D
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 19:37:19 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436789B458TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, we could also propose algorithm combinations for key agreement followe=
d GCM key wrapping but I didn't think that was an ask from the working grou=
p.  The Denver minutes just recorded my action item as "key wrap draft for =
AES-GCM-keywrap", so that's what I did.  We could have a discussion on Mond=
ay's call and on the list about whether the working group is also intereste=
d in other algorithms.

Remember, the beauty of having the algorithms registry is that algorithms c=
an be added "just in time" - as actual need for them is demonstrated.  We d=
on't have to register all conceivable algorithm combinations up front for t=
he JWE/JWA specs to be complete.

As for how the AEAD parameters are handled I used a parameter encoding that=
 doesn't result in double base64url encoding anything.  I could have instea=
d introduced separate "iv" and "tag" header parameter values, but didn't do=
 so for that reason.  But if people would prefer that approach because it's=
 more parallel to the use of GCM for plaintext encryption, I have no proble=
m with that.

I do believe that the objective of my draft was met - demonstrating that AE=
AD key wrapping can be easily done with the current drafts.  The details of=
 how the algorithm parameters are encoded is secondary to that and algorith=
m-specific; several reasonable choices are possible within the current JWE =
framework - one of which was described in my draft.

                                                                -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping

<no hat>
<sarcasm level=3D"heavy">

I am shocked that you would possibly support this proposal.  It provides fo=
r two ways of dealing with something.  It is my understanding that you neve=
r support anything that has two ways of doing something.

How the AEAD algorithm parameters is handled completely differently for thi=
s proposal and for the same algorithms being used in a CEK context.  This i=
s going to lead to confusion.

</sarcasm>

Your specification is missing some items that still need to be registered  =
Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined =
in your document as well.

Your document ends up with a registration complexity that needs to be thoug=
ht about and dealt with as well.  For every new key wrap algorithm added, y=
ou will need to register not only it alone but also it with every different=
 key agreement algorithm that is supported.  Thus adding a single key wrap =
algorithm becomes a slight issue in terms of adding in all of the different=
 ways that it might be used.  This is a complexity issue that is not discus=
sed in the current draft.

I have not necessarily found that document size equals code size.  I have i=
mplemented some very simple documents that were very difficult to code and =
implemented some very long documents that were very easy to code.  So I wou=
ld not use that fact as a deciding factor.

(Once again I regret the fact that the group did not go with an object desc=
riptor for algorithms as this would have made all of this much simpler.  I =
actually immediately map from the string to an object description in my JOS=
E implementation for simplicity reasons.  Not to mention that this is way i=
t needs to be done for the WebCrypto specficiation.)

Jim



From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Tuesday, June 25, 2013 4:18 PM
To: 'Jim Schaad'; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like =
a substantially simpler approach than http://tools.ietf.org/html/draft-barn=
es-jose-key-wrapping-01.  This is evident by several metrics:

*         Number of proposed changes:  The Jones draft proposes no changes =
to any of the current specs.  It simply defines an encoding for GCM and add=
s registry entries for it.  Whereas the Barnes draft proposes a major restr=
ucturing - listing 4 major changes in the introduction and 4 smaller change=
s.

*         Normative text size:  The Jones GCM key wrap approach requires on=
ly 7 normative sentences in 1/2 page of text.  The Barnes draft has four pa=
ges of normative text, along with an extensive introduction describing the =
proposed complete restructuring of JWS and JWE.

We don't need to boil the ocean with a total redesign to enable AEAD key wr=
apping.  It can already easily be done with the current specs simply by def=
ining new algorithms.  The approach taken in http://tools.ietf.org/html/dra=
ft-jones-jose-aes-gcm-key-wrap-00 would work for any AEAD algorithm.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

We now have two documents - one from Richard and one from Mike - which prov=
ide the two different ways that have been proposed for doing key wrapping w=
ith an AEAD algorithm.

Please review the two documents and provide comments to the list.

Jim


--_000_4E1F6AAD24975D4BA5B16804296739436789B458TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Yes, we could also pro=
pose algorithm combinations for key agreement followed GCM key wrapping but=
 I didn&#8217;t think that was an ask from the working group.&nbsp; The Den=
ver minutes just recorded my action item as &#8220;key
 wrap draft for AES-GCM-keywrap&#8221;, so that&#8217;s what I did.&nbsp; W=
e could have a discussion on Monday&#8217;s call and on the list about whet=
her the working group is also interested in other algorithms.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Remember, the beauty o=
f having the algorithms registry is that algorithms can be added &#8220;jus=
t in time&#8221; &#8211; as actual need for them is demonstrated.&nbsp; We =
don&#8217;t have to register all conceivable algorithm combinations
 up front for the JWE/JWA specs to be complete.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As for how the AEAD pa=
rameters are handled I used a parameter encoding that doesn&#8217;t result =
in double base64url encoding anything.&nbsp; I could have instead introduce=
d separate &#8220;iv&#8221; and &#8220;tag&#8221; header parameter values,
 but didn&#8217;t do so for that reason.&nbsp; But if people would prefer t=
hat approach because it&#8217;s more parallel to the use of GCM for plainte=
xt encryption, I have no problem with that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I do believe that the =
objective of my draft was met &#8211; demonstrating that AEAD key wrapping =
can be easily done with the current drafts.&nbsp; The details of how the al=
gorithm parameters are encoded is secondary to
 that and algorithm-specific; several reasonable choices are possible withi=
n the current JWE framework &#8211; one of which was described in my draft.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Wednesday, June 26, 2013 11:30 AM<br>
<b>To:</b> Mike Jones; jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;no hat&gt;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;sarcasm level=3D&#=
8221;heavy&#8221;&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I am shocked that you =
would possibly support this proposal.&nbsp; It provides for two ways of dea=
ling with something.&nbsp; It is my understanding that you never support an=
ything that has two ways of doing something.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">How the AEAD algorithm=
 parameters is handled completely differently for this proposal and for the=
 same algorithms being used in a CEK context. &nbsp;This is going to lead t=
o confusion.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;/sarcasm&gt;<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Your specification is =
missing some items that still need to be registered&nbsp; Thus you also nee=
d to have ECDH-ES&#43;A128GCMKW and ECDH-ES&#43;A256GCMKW defined in your d=
ocument as well.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Your document ends up =
with a registration complexity that needs to be thought about and dealt wit=
h as well.&nbsp; For every new key wrap algorithm added, you will need to r=
egister not only it alone but also it with
 every different key agreement algorithm that is supported. &nbsp;Thus addi=
ng a single key wrap algorithm becomes a slight issue in terms of adding in=
 all of the different ways that it might be used.&nbsp; This is a complexit=
y issue that is not discussed in the current
 draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have not necessarily=
 found that document size equals code size.&nbsp; I have implemented some v=
ery simple documents that were very difficult to code and implemented some =
very long documents that were very easy to
 code.&nbsp; So I would not use that fact as a deciding factor.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">(Once again I regret t=
he fact that the group did not go with an object descriptor for algorithms =
as this would have made all of this much simpler.&nbsp; I actually immediat=
ely map from the string to an object description
 in my JOSE implementation for simplicity reasons.&nbsp; Not to mention tha=
t this is way it needs to be done for the WebCrypto specficiation.)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Tuesday, June 25, 2013 4:18 PM<br>
<b>To:</b> 'Jim Schaad'; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a>=
<br>
<b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"http://tool=
s.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">http://tools.ietf.org=
/html/draft-jones-jose-aes-gcm-key-wrap-00</a> seems like a substantially s=
impler approach than
<a href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">ht=
tp://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; This =
is evident by several metrics:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Number of prop=
osed changes:&nbsp; The Jones draft proposes no changes to any of the curre=
nt specs.&nbsp; It simply defines an encoding for GCM and adds registry ent=
ries for it.&nbsp; Whereas the Barnes draft proposes
 a major restructuring &#8211; listing 4 major changes in the introduction =
and 4 smaller changes.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Normative text=
 size:&nbsp; The Jones GCM key wrap approach requires only 7 normative sent=
ences in 1/2 page of text.&nbsp; The Barnes draft has four pages of normati=
ve text, along with an extensive introduction
 describing the proposed complete restructuring of JWS and JWE.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We don&#8217;t need to=
 boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; It=
 can already easily be done with the current specs simply by defining new a=
lgorithms.&nbsp; The approach taken in
<a href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00"=
>http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> would =
work for any AEAD algorithm.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 25, 2013 9:53 AM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We now have two documents &#8211; one from Richard a=
nd one from Mike &#8211; which provide the two different ways that have bee=
n proposed for doing key wrapping with an AEAD algorithm.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the two documents and provide comments=
 to the list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436789B458TK5EX14MBXC283r_--

From ve7jtb@ve7jtb.com  Wed Jun 26 13:03:23 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577C011E8201 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 13:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yuAtHuBDwHW7 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 13:03:22 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7C58011E8142 for <jose@ietf.org>; Wed, 26 Jun 2013 13:03:22 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id e11so8433085qcx.24 for <jose@ietf.org>; Wed, 26 Jun 2013 13:03:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=bQBa6AlzQ+GfkvmWwQMY7bEhrIjzxScCwSb5npt3GlQ=; b=QotnuwCPr/NnUPxDeQ4uXBZJSxNXvqGaT1IPqgeltT5mNLmNHni7FpJ5xpad3S/oJ7 JP/NWxfIX/55TT/+u7XDdDlrqz9lUpDUW+nh7mUJF2IpBbKjkHkasfBhoKd68LC1XDhi jRptC35IOryUKtXGTqFbKEib5LTKlPJu427qixE1HATNR9wZgEh16cj+wjkzPUtYv8zz j2bL+f1mly+aNx92FWliiS2GXSUvXTiadOqobz2VRnpf0bl/0nHxjLTZrQdfzBg/MoQ6 dPUc16a+tD85RgjH2YOjJWinQTvA0DpUjHWs6n2JSr5vv/LHgXx4uWkXUWlS6tGnt4lF lhBg==
X-Received: by 10.224.74.72 with SMTP id t8mr7565078qaj.74.1372277001709; Wed, 26 Jun 2013 13:03:21 -0700 (PDT)
Received: from [192.168.1.216] (190-20-19-12.baf.movistar.cl. [190.20.19.12]) by mx.google.com with ESMTPSA id l4sm125725qay.0.2013.06.26.13.03.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 13:03:20 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_C4CF314B-E2A2-42A9-ACFF-9436CA5DBDB8"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
Date: Wed, 26 Jun 2013 16:02:57 -0400
Message-Id: <1AE58166-F5E3-4631-90C9-32EC5EE2DF07@ve7jtb.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
To: "Jim Schaad" <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQnlMdO+UjaCPwtvpBmobvHS6hJlH6f2g5gqnekSIxWpLmVuCfNnFljtky4jjewppgJoz5AV
Cc: michael.jones@microsoft.com, jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 20:03:23 -0000

--Apple-Mail=_C4CF314B-E2A2-42A9-ACFF-9436CA5DBDB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

At the moment the signature is calculated over the base64url encoded =
representation of the payload and not the binary string. =20

Having two different ways to calculate the signature seems like the =
wrong thing. =20

If we were talking about always calculating the signature over the =
binary string and then dealing with encoding as a later step I would =
understand your point better but the flag is changing the processing as =
well as the representation.

However that would render the compact and JSON forms incompatible =
without recalculating the signature.

What are the issues with including a 8-bit string in a JSON sting?

What you are proposing seems like a large fundamental change, that would =
require a matching change in compact, that complicates that format.

Perhaps I am not understanding your proposal.

John B.

On 2013-06-26, at 2:29 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:

> Having multiple ways to do something can frequently buy you a great =
deal of benefit.  However, in this case it is my library that is doing =
this and not the standard.
>=20
> The client gives the library an 8-bit string.  The library signs that =
string.  The library puts that string into the payload field.
>=20
> The client needs to make the 8-bit string URL safe if it wants to use =
compact encoding.
>=20
> Where is there two ways of doing something?
>=20
> Jim
>=20
>=20
>> -----Original Message-----
>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
>> jose issue tracker
>> Sent: Tuesday, June 25, 2013 5:23 PM
>> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
>> michael.jones@microsoft.com
>> Cc: jose@ietf.org
>> Subject: Re: [jose] #26: Allow for signature payload to not be base64 =
encoded
>>=20
>> #26: Allow for signature payload to not be base64 encoded
>>=20
>>=20
>> Comment (by michael.jones@microsoft.com):
>>=20
>> Having multiple ways to do something is one of the classic pitfalls =
to  avoid in
>> standards.  They tend to generate interop problems because  =
developers will
>> often only build the way that they think they need, never
>> getting around to the others.   I don t think the potential benefits =
of
>> having multiple ways to encode the payload outweigh this cost.
>>=20
>> Next, this feature would only work with the JSON serialization; it =
would  not
>> work for the Compact Serialization because the payload must be URL  =
safe.
>> The base64url encoding accomplishes that, and so is a necessary  part =
of the
>> encoding.  Having the two serializations diverge in this  manner =
seems
>> suboptimal.
>>=20
>> Third, I am concerned that the payload will sometimes change during
>> transmission if not encoded in some manner.  Tabs can change to =
spaces.
>> LFs can change to CRLFs.  HTML is notorious for adding a blank at the =
end  of
>> each line.  Two spaces can change to a space and a non-breaking =
space.
>> Etc.  Not encoding the payload would open us up to all of these =
potential
>> modification-during-transmission problems   all of which would render =
the
>> JWS useless by breaking the signature.
>>=20
>> Finally, this feature seems to be motivated by detached signatures, =
which  per
>> my comment on Ticket #25, can be accomplished at the application =
layer
>> without adding general-purpose support for detached signatures.  =
Thus, I  don
>> t think this related feature is needed either.
>>=20
>> For all these reasons, I believe that this issue should be closed as  =
 won t fix .
>>=20
>> --
>> =
-------------------------+----------------------------------------------
>> -------------------------+---
>> Reporter:               |       Owner:  draft-ietf-jose-json-web-
>>  ietf@augustcellars.com |  signature@tools.ietf.org
>>     Type:  defect       |      Status:  new
>> Priority:  major        |   Milestone:
>> Component:  json-web-    |     Version:
>>  signature              |  Resolution:
>> Severity:  -            |
>> Keywords:               |
>> =
-------------------------+----------------------------------------------
>> -------------------------+---
>>=20
>> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1>
>> jose <http://tools.ietf.org/jose/>
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_C4CF314B-E2A2-42A9-ACFF-9436CA5DBDB8
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI2MjAwMjU4WjAjBgkqhkiG9w0BCQQxFgQUA9iA6SS1
es9FkJuZcTYccMjqT34wgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAjAFgdwsavLRqZOXEXnOaQZZeEiaMG2HY5yKuUjWs
JihrY/QbP3QvpPCTdliBYByviYqLbd3St/lK7KZMQDI+5nmCMFaUQDmOW0gifnPJdRVJO2sdNzUU
KaUA9CW3ZgqkqUPHozITJSbQItCwZHLRyNjNzDsSKnk1B5SIaDYPq2N2OAgVfOGZGTspKo8tLr1b
tfUXJOU1wJvh7Snm/4yPWKZvokeyPhBWTVyu3sz74F+VK2xUS3pFkVFEUiJt4lUZeBX8BmVU+uR2
VktUw5jinYDZg7GX1Gc64biJv9HPic78oytyj3PxVNo0xZrAr0P0X0t4W0qARKl2zRQqe0IypQAA
AAAAAA==

--Apple-Mail=_C4CF314B-E2A2-42A9-ACFF-9436CA5DBDB8--

From ietf@augustcellars.com  Wed Jun 26 16:47:56 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF7611E8155 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 16:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqANTb-B-EoZ for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 16:47:50 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 65E1B11E814D for <jose@ietf.org>; Wed, 26 Jun 2013 16:47:49 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id B942D2CA23; Wed, 26 Jun 2013 16:47:47 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <draft-ietf-jose-json-web-signature@tools.ietf.org>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org> <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org>
In-Reply-To: <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org>
Date: Wed, 26 Jun 2013 16:46:51 -0700
Message-ID: <03a601ce72c7$6eb58010$4c208030$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHKld+pXydVGMxINHz+GIm2S6VogAHtViClmUD2iRA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 26 Jun 2013 23:47:56 -0000

I completely disagree with your characterization that detached =
signatures was either a complicated feature or that it caused interop =
problems.  The problems that I always had with XMLDSig were XML problems =
and had nothing to do with the question of detached or non-detached, =
canonizied or non-canonicized.  The problem was always that XML itself =
was not a good thing to try and produce a usable and reproducible octet =
stream for the purposes of hashing.  If you just processed it as a =
binary stream in a disk file then there were no problems (assuming that =
you had not re-written it in some way).

I also disagree that it would be any easier to do a detached signature =
using an indirect rather than direct form.  If you are worried about =
having things change because it is a detached content, then it makes no =
difference if that detached content is either directly or indirectly =
reference.  I don't think that going to an indirect form fixes this =
problem in any way.

Finally, if we are going to say this is the way to do things, we need to =
define a way to do this in the JOSE drafts themselves.  This would =
expected to be a standard technique that is used by a number of =
different systems.  It should therefore be a common method for doing it =
because otherwise you get many different ways of doing it that are =
designed by non-security people and therefore prone to error.


> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
> jose issue tracker
> Sent: Tuesday, June 25, 2013 5:08 PM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> michael.jones@microsoft.com
> Cc: jose@ietf.org
> Subject: Re: [jose] #25: Detached content for the ALTO use case
>=20
> #25: Detached content for the ALTO use case
>=20
>=20
> Comment (by michael.jones@microsoft.com):
>=20
>  Detached signatures was one of the complicated features of XMLDSIG =
that
> caused substantial interop problems.  I d thought that there was =
already
> substantial sentiment in the working group not to do this because of =
the  high
> complexity/benefit ratio.
>=20
>  The good news, however, is that a form of detached signatures is EASY =
to
> build one layer up the stack by signing a hash of the detached =
content.
>  ALTO could easily do this.
>=20
>  There s already a deployed example of this, in fact.  OpenID Connect
> includes a hash of the OAuth Access Token as a claim in the ID Token  =
issued
> with it.  This allows the holder of the ID Token to verify that  token =
substitution
> of a different Access Token value has not been  performed by an =
attacker.
> This works with JWS as it is today.
>=20
>  I therefore suggest that we recommend this technique to ALTO and add =
a
> description of it in the ALTO section of the Use Cases document and =
close  this
> issue as  won t fix .
>=20
> --
> =
-------------------------+----------------------------------------------
> -------------------------+---
>  Reporter:               |       Owner:  draft-ietf-jose-json-web-
>   ietf@augustcellars.com |  signature@tools.ietf.org
>      Type:  defect       |      Status:  new
>  Priority:  major        |   Milestone:
> Component:  json-web-    |     Version:
>   signature              |  Resolution:
>  Severity:  -            |
>  Keywords:               |
> =
-------------------------+----------------------------------------------
> -------------------------+---
>=20
> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
> jose <http://tools.ietf.org/jose/>
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From rlb@ipv.sx  Wed Jun 26 17:08:54 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D6821F9AC2 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 17:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.882
X-Spam-Level: 
X-Spam-Status: No, score=-2.882 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNBXpTBVHH6J for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 17:08:49 -0700 (PDT)
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) by ietfa.amsl.com (Postfix) with ESMTP id 69E2921F9AAF for <jose@ietf.org>; Wed, 26 Jun 2013 17:08:49 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so86711obc.37 for <jose@ietf.org>; Wed, 26 Jun 2013 17:08:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=0C+V4hK3PPxuWdsiY9QVfjJ9M7USIgrn8Ec2Yz4isnw=; b=b7uJo9Gj1VX60Eu6VOTOYNASUwKy0vSEzMGshVg21NvN+uyUYsDe6O++h6qCZyPP5o WnKxSKNYEnuuqGDKLth/O8Ci65PvhPCdg1/5wMuAJ+eh/IC6dv11d0e5Esnu8B826mlR NowOLOiU4KmPqDY/4IjehnaJqIcevrL9fZb1I+b2J0PC6RtYv8I7yEyaZOT8ls1iFlE3 qptUJG+Rnuf0AI9ng0BsjDfoPabGTf58cQWXpCmv/UdK5m4/Jzpjr6UbqkAO0Y4eTo5m 1/iwpRoGxJ1i9Ex0WLcRDV3Sq/KoaYmTTzuA8VQ2BqX6HMITbqoreV1GksSR0Z8h5WKR 6WQw==
MIME-Version: 1.0
X-Received: by 10.60.43.226 with SMTP id z2mr1712396oel.76.1372291728628; Wed, 26 Jun 2013 17:08:48 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Wed, 26 Jun 2013 17:08:48 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <A13981F3-83DF-4519-8173-6A10FA00E71F@isoc.org>
References: <046e01ce5d51$0732ffc0$1598ff40$@augustcellars.com> <06f001ce663d$75b3d100$611b7300$@augustcellars.com> <A13981F3-83DF-4519-8173-6A10FA00E71F@isoc.org>
Date: Wed, 26 Jun 2013 20:08:48 -0400
Message-ID: <CAL02cgTfTJe3tkfk=5pJf78tzKoucJvBL4r34WcdSVL4F+wtAw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Karen O'Donoghue" <odonoghue@isoc.org>
Content-Type: multipart/alternative; boundary=001a11333dce0370f604e0179183
X-Gm-Message-State: ALoCoQnpIV1VijSyEli6czXEhHS1LbxupsWmW+mjXaeIJwDyXsQ5E0gFmeK3K4s0sQqUHjcQDe74
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] status of WGLC on - draft-ietf-jose-use-cases
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 00:08:54 -0000

--001a11333dce0370f604e0179183
Content-Type: text/plain; charset=ISO-8859-1

Request acknowledged.
Thanks,
The Editor


On Wed, Jun 26, 2013 at 12:04 AM, Karen O'Donoghue <odonoghue@isoc.org>wrote:

>  Folks,
>
>  The WGLC on draft-ietf-jose-use-cases has closed. As a result of the
> WGLC, the chairs request the editor to update the document to add the
> additional use case and to address the additional comments posted on the
> list. Upon successful completion of the revision, the document will be
> forwarded to the IESG.
>
>  Thanks for all who reviewed the document.
>
>  Regards,
> Karen
>
>
>  On Jun 10, 2013, at 8:48 PM, Jim Schaad wrote:
>
>   This is a reminder to do this in the next week.  We need both positive
> and negative reviews to judge consensus.****
>  ** **
>  Jim****
>  ** **
>  ** **
>   *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Jim Schaad
> *Sent:* Thursday, May 30, 2013 9:16 AM
> *To:* jose@ietf.org
> *Subject:* [jose] Working Group Last Call - draft-ietf-jose-use-cases
> *Importance:* High****
>   ** **
>  <chair>****
>  ** **
>  This message starts the Working Group Last Call on the Use Cases document.
> ****
>  ** **
>  Minor issues should be sent to the list****
>  ** **
>  Major issues (those that should block the document from proceeding to the
> IESG) should be sent to the list and an issue created in the tracker.****
>  ** **
>  The final day for Last Call comments is June 16, 2013****
>  ** **
>  ** **
>  Jim****
>  ** **
>  _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--001a11333dce0370f604e0179183
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Request acknowledged. =A0<div>Thanks,</div><div>The Editor=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Wed, Jun 26, 2013 at 12:04 AM, Karen O&#39;Donoghue <span dir=3D"ltr">&lt=
;<a href=3D"mailto:odonoghue@isoc.org" target=3D"_blank">odonoghue@isoc.org=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">




<div style=3D"word-wrap:break-word">
Folks,
<div><br>
</div>
<div>The WGLC on draft-ietf-jose-use-cases has closed. As a result of the W=
GLC, the chairs request the editor to update the document to add the additi=
onal use case and to address the additional comments posted on the list. Up=
on successful completion of the
 revision, the document will be forwarded to the IESG.</div>
<div><br>
</div>
<div>Thanks for all who reviewed the document.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Karen</div>
<div><br>
</div>
<div><br>
<div>
<div>On Jun 10, 2013, at 8:48 PM, Jim Schaad wrote:</div>
<br>
<blockquote type=3D"cite"><span style=3D"border-collapse:separate;font-fami=
ly:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;lette=
r-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px=
;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<span style=3D"color:rgb(31,73,125)">This is a reminder to do this in the n=
ext week.=A0 We need both positive and negative reviews to judge consensus.=
<u></u><u></u></span></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<span style=3D"color:rgb(31,73,125)"><u></u>=A0<u></u></span></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<span style=3D"color:rgb(31,73,125)">Jim<u></u><u></u></span></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<span style=3D"color:rgb(31,73,125)"><u></u>=A0<u></u></span></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<span style=3D"color:rgb(31,73,125)"><u></u>=A0<u></u></span></div>
<div style=3D"border-top-style:none;border-right-style:none;border-bottom-s=
tyle:none;border-width:initial;border-color:initial;border-left-style:solid=
;border-left-color:blue;border-left-width:1.5pt;padding-top:0in;padding-rig=
ht:0in;padding-bottom:0in;padding-left:4pt">

<div>
<div style=3D"border-right-style:none;border-bottom-style:none;border-left-=
style:none;border-width:initial;border-color:initial;border-top-style:solid=
;border-top-color:rgb(181,196,223);border-top-width:1pt;padding-top:3pt;pad=
ding-right:0in;padding-bottom:0in;padding-left:0in">

<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif">From:</span=
></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif"><span>=A0=
</span><a href=3D"mailto:jose-bounces@ietf.org" style=3D"color:blue;text-de=
coration:underline" target=3D"_blank">jose-bounces@ietf.org</a><span>=A0</s=
pan>[mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose=
-bounces@ietf.org</a>]<span>=A0</span><b>On
 Behalf Of<span>=A0</span></b>Jim Schaad<br>
<b>Sent:</b><span>=A0</span>Thursday, May 30, 2013 9:16 AM<br>
<b>To:</b><span>=A0</span><a href=3D"mailto:jose@ietf.org" style=3D"color:b=
lue;text-decoration:underline" target=3D"_blank">jose@ietf.org</a><br>
<b>Subject:</b><span>=A0</span>[jose] Working Group Last Call - draft-ietf-=
jose-use-cases<br>
<b>Importance:</b><span>=A0</span>High<u></u><u></u></span></div>
</div>
</div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
&lt;chair&gt;<u></u><u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
This message starts the Working Group Last Call on the Use Cases document.<=
u></u><u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Minor issues should be sent to the list<u></u><u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Major issues (those that should block the document from proceeding to the I=
ESG) should be sent to the list and an issue created in the tracker.<u></u>=
<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
The final day for Last Call comments is June 16, 2013<u></u><u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
Jim<u></u><u></u></div>
<div style=3D"margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom=
:0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">
<u></u>=A0<u></u></div>
</div>
</div>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" style=3D"color:blue;text-decoration:underl=
ine" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" style=3D"color:blue;=
text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/jose</a></div>
</span></blockquote>
</div>
<br>
</div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--001a11333dce0370f604e0179183--

From ve7jtb@ve7jtb.com  Wed Jun 26 18:22:36 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32ACE11E8184 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 18:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6780ASQGiMFB for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 18:22:29 -0700 (PDT)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id A81D211E8177 for <jose@ietf.org>; Wed, 26 Jun 2013 18:22:27 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id a13so354941iee.6 for <jose@ietf.org>; Wed, 26 Jun 2013 18:22:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=T/RlZPCkp8Ebla6dCU+Ti4vy3JTCaWbjSIHxDHRGzS0=; b=nhQ+vZugc2rB6HcbyZ7/Q2T1e8X6T6PPApKoxPhrt9B+PbuNM2MsAcX3j0uuzVVgBQ C6NMfMTMhPbQtPEDzFKC7Q97PNPE1XGDF2qZzchkcVE9UH3RZl3SGl6OfzyqOd2Zrfox 6nTEkU+CWfbApPdCdFRNCOEsFTZbjjn13uJ5Jj/6EBT4VuXg/7m+LwP3FA2j8H0GFWWs nmBs6Omn7/CPt2cKaunOBKuTcnxfZbFY/GzzFl0e2MuHdoLZXQ5U4P5lwwMaI2XxA58I aBI8EaboWQyft1+VvwDVwrQqknbsYEjN9jgQrSUdduoIIQujktEBBrijFD3FVXU+abeA VvfQ==
X-Received: by 10.43.53.211 with SMTP id vr19mr3602704icb.33.1372296142572; Wed, 26 Jun 2013 18:22:22 -0700 (PDT)
Received: from [192.168.1.216] (190-20-19-12.baf.movistar.cl. [190.20.19.12]) by mx.google.com with ESMTPSA id ff19sm720748igb.0.2013.06.26.18.22.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 18:22:21 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_2BE571F5-822D-454B-A1B2-28493AC475C5"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <03a601ce72c7$6eb58010$4c208030$@augustcellars.com>
Date: Wed, 26 Jun 2013 21:19:41 -0400
Message-Id: <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org> <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org> <03a601ce72c7$6eb58010$4c208030$@augustcellars.com>
To: "Jim Schaad" <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmDTin8UawA5HGbFfU0jz6W53IWxMwqF5EGaiWoOyNpCWKOzEezQtE7pEq9E/a7vC51KIDF
Cc: jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 01:22:36 -0000

--Apple-Mail=_2BE571F5-822D-454B-A1B2-28493AC475C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

The problem is describing the detached thing in a way that will allow =
for correct verification.=20
SOAP has a number of interesting things that can happen by getting the =
receiver to verify one header part but use another for processing.
XMLdsig wrapping attacks exist and are to some minds related to detached =
signatures.

In Connect the claim defines exactly how to find the detached body.

Leaving it to the application layer to define where the detached body is =
to be located is not unreasonable.

How are you thinking of doing that in a generic and secure enough way to =
be useful in JWS itself?

The signature itself is not really the hard part.

As an example of a detached body that might be useful to look at is =
signing a HTTP request for OAuth and including the JWS in a header.  How =
in a generic JWS way would you describe how to assemble the body to be =
hashed?=20

In principal I see lats of uses at the application layer for sending a =
hash of something in a JWS where the application layer describes how to =
assemble some custom content for hashing, but I have a hard time seeing =
that happen in a interoperable way in JWS.   I could be wrong and am =
interested in concrete proposals.

John B.

On 2013-06-26, at 7:46 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:

> I completely disagree with your characterization that detached =
signatures was either a complicated feature or that it caused interop =
problems.  The problems that I always had with XMLDSig were XML problems =
and had nothing to do with the question of detached or non-detached, =
canonizied or non-canonicized.  The problem was always that XML itself =
was not a good thing to try and produce a usable and reproducible octet =
stream for the purposes of hashing.  If you just processed it as a =
binary stream in a disk file then there were no problems (assuming that =
you had not re-written it in some way).
>=20
> I also disagree that it would be any easier to do a detached signature =
using an indirect rather than direct form.  If you are worried about =
having things change because it is a detached content, then it makes no =
difference if that detached content is either directly or indirectly =
reference.  I don't think that going to an indirect form fixes this =
problem in any way.
>=20
> Finally, if we are going to say this is the way to do things, we need =
to define a way to do this in the JOSE drafts themselves.  This would =
expected to be a standard technique that is used by a number of =
different systems.  It should therefore be a common method for doing it =
because otherwise you get many different ways of doing it that are =
designed by non-security people and therefore prone to error.
>=20
>=20
>> -----Original Message-----
>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
>> jose issue tracker
>> Sent: Tuesday, June 25, 2013 5:08 PM
>> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
>> michael.jones@microsoft.com
>> Cc: jose@ietf.org
>> Subject: Re: [jose] #25: Detached content for the ALTO use case
>>=20
>> #25: Detached content for the ALTO use case
>>=20
>>=20
>> Comment (by michael.jones@microsoft.com):
>>=20
>> Detached signatures was one of the complicated features of XMLDSIG =
that
>> caused substantial interop problems.  I d thought that there was =
already
>> substantial sentiment in the working group not to do this because of =
the  high
>> complexity/benefit ratio.
>>=20
>> The good news, however, is that a form of detached signatures is EASY =
to
>> build one layer up the stack by signing a hash of the detached =
content.
>> ALTO could easily do this.
>>=20
>> There s already a deployed example of this, in fact.  OpenID Connect
>> includes a hash of the OAuth Access Token as a claim in the ID Token  =
issued
>> with it.  This allows the holder of the ID Token to verify that  =
token substitution
>> of a different Access Token value has not been  performed by an =
attacker.
>> This works with JWS as it is today.
>>=20
>> I therefore suggest that we recommend this technique to ALTO and add =
a
>> description of it in the ALTO section of the Use Cases document and =
close  this
>> issue as  won t fix .
>>=20
>> --
>> =
-------------------------+----------------------------------------------
>> -------------------------+---
>> Reporter:               |       Owner:  draft-ietf-jose-json-web-
>> ietf@augustcellars.com |  signature@tools.ietf.org
>>    Type:  defect       |      Status:  new
>> Priority:  major        |   Milestone:
>> Component:  json-web-    |     Version:
>> signature              |  Resolution:
>> Severity:  -            |
>> Keywords:               |
>> =
-------------------------+----------------------------------------------
>> -------------------------+---
>>=20
>> Ticket URL: =
<http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
>> jose <http://tools.ietf.org/jose/>
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


--Apple-Mail=_2BE571F5-822D-454B-A1B2-28493AC475C5
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI3MDExOTQxWjAjBgkqhkiG9w0BCQQxFgQURrfQQdsJ
c4SV1mvTvd4q2stvXL8wgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAMFK8lKBjOStxz+CGFqVESKS64XfdGeOzYI+85Edu
mYYThrbeu7pYzz8+r1U2/kkpn9Da4nU45r4TxA//7wxYHr6v6fcNOPvF7Rfejvj+Hfq8tXihza4i
7Zcd5L5u40GBtSMOi4cVc62mz/dgQY6IslOSJ23ukCKnF4o8rPm4L1dcjiQf4W3tVZ4nw96mSTg3
42mOwlqKJB5DzWHhEDCvJjj2EPCqR/8sqpjIAJFrlBfc61L2SQ8J7vVXmOimbv81yp68WbWGlLqG
baVd2H6pHuFMhJ4qQW3il0ls+BCtVw7Xx0lk0D/rU67G0ZAkrTJOxcedzIa6bez4xCSgDp0ohgAA
AAAAAA==

--Apple-Mail=_2BE571F5-822D-454B-A1B2-28493AC475C5--

From sakimura@gmail.com  Wed Jun 26 19:27:13 2013
Return-Path: <sakimura@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E1111E817F for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwfXdCTHk9dZ for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:27:09 -0700 (PDT)
Received: from tonescape.net (sv0808.marimba.org [210.227.115.218]) by ietfa.amsl.com (Postfix) with ESMTP id 8381111E80F9 for <jose@ietf.org>; Wed, 26 Jun 2013 19:27:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) (uid 33) by tonescape.net with local; Thu, 27 Jun 2013 11:27:07 +0900 id 00388E88.51CBA2FB.000020C4
To: John Bradley <ve7jtb@ve7jtb.com>
X-PHP-Originating-Script: 0:func.inc
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Date: Thu, 27 Jun 2013 11:27:07 +0900
From: sakimura <sakimura@gmail.com>
In-Reply-To: <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org> <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org> <03a601ce72c7$6eb58010$4c208030$@augustcellars.com> <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com>
Message-ID: <dbd7c98a00fe3b8fd47bc4c4435f5c64@imap.gmail.com>
X-Sender: sakimura@gmail.com
User-Agent: RoundCube Webmail/0.3.1
X-Mime-Autoconverted: from 8bit to 7bit by courier 0.65
Cc: Jim Schaad <ietf@augustcellars.com>, jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 02:27:14 -0000

I was writing almost exactly the same thing. 

I am interested to hear why it would not work by defining how to hash 
whatever the content and sign it with JWS and include the compact
serialization in 
a HTTP header like 'x-alto-signature'.  

Nat

On Wed, 26 Jun 2013 21:19:41 -0400, John Bradley <ve7jtb@ve7jtb.com>
wrote:
> The problem is describing the detached thing in a way that will allow
for
> correct verification. 
> SOAP has a number of interesting things that can happen by getting the
> receiver to verify one header part but use another for processing.
> XMLdsig wrapping attacks exist and are to some minds related to detached
> signatures.
> 
> In Connect the claim defines exactly how to find the detached body.
> 
> Leaving it to the application layer to define where the detached body is
> to be located is not unreasonable.
> 
> How are you thinking of doing that in a generic and secure enough way to
> be useful in JWS itself?
> 
> The signature itself is not really the hard part.
> 
> As an example of a detached body that might be useful to look at is
> signing a HTTP request for OAuth and including the JWS in a header.  How
in
> a generic JWS way would you describe how to assemble the body to be
hashed?
> 
> 
> In principal I see lats of uses at the application layer for sending a
> hash of something in a JWS where the application layer describes how to
> assemble some custom content for hashing, but I have a hard time seeing
> that happen in a interoperable way in JWS.   I could be wrong and am
> interested in concrete proposals.
> 
> John B.
> 
> On 2013-06-26, at 7:46 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:
> 
>> I completely disagree with your characterization that detached
>> signatures was either a complicated feature or that it caused interop
>> problems.  The problems that I always had with XMLDSig were XML
problems
>> and had nothing to do with the question of detached or non-detached,
>> canonizied or non-canonicized.  The problem was always that XML itself
>> was not a good thing to try and produce a usable and reproducible octet
>> stream for the purposes of hashing.  If you just processed it as a
binary
>> stream in a disk file then there were no problems (assuming that you
had
>> not re-written it in some way).
>> 
>> I also disagree that it would be any easier to do a detached signature
>> using an indirect rather than direct form.  If you are worried about
>> having things change because it is a detached content, then it makes no
>> difference if that detached content is either directly or indirectly
>> reference.  I don't think that going to an indirect form fixes this
>> problem in any way.
>> 
>> Finally, if we are going to say this is the way to do things, we need
to
>> define a way to do this in the JOSE drafts themselves.  This would
>> expected to be a standard technique that is used by a number of
different
>> systems.  It should therefore be a common method for doing it because
>> otherwise you get many different ways of doing it that are designed by
>> non-security people and therefore prone to error.
>> 
>> 
>>> -----Original Message-----
>>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
Of
>>> jose issue tracker
>>> Sent: Tuesday, June 25, 2013 5:08 PM
>>> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
>>> michael.jones@microsoft.com
>>> Cc: jose@ietf.org
>>> Subject: Re: [jose] #25: Detached content for the ALTO use case
>>> 
>>> #25: Detached content for the ALTO use case
>>> 
>>> 
>>> Comment (by michael.jones@microsoft.com):
>>> 
>>> Detached signatures was one of the complicated features of XMLDSIG
that
>>> caused substantial interop problems.  I d thought that there was
already
>>> substantial sentiment in the working group not to do this because of
>>> the  high
>>> complexity/benefit ratio.
>>> 
>>> The good news, however, is that a form of detached signatures is EASY
to
>>> build one layer up the stack by signing a hash of the detached
content.
>>> ALTO could easily do this.
>>> 
>>> There s already a deployed example of this, in fact.  OpenID Connect
>>> includes a hash of the OAuth Access Token as a claim in the ID Token 
>>> issued
>>> with it.  This allows the holder of the ID Token to verify that  token
>>> substitution
>>> of a different Access Token value has not been  performed by an
>>> attacker.
>>> This works with JWS as it is today.
>>> 
>>> I therefore suggest that we recommend this technique to ALTO and add a
>>> description of it in the ALTO section of the Use Cases document and
>>> close  this
>>> issue as  won t fix .
>>> 
>>> --
>>>
-------------------------+----------------------------------------------
>>> -------------------------+---
>>> Reporter:               |       Owner:  draft-ietf-jose-json-web-
>>> ietf@augustcellars.com |  signature@tools.ietf.org
>>>    Type:  defect       |      Status:  new
>>> Priority:  major        |   Milestone:
>>> Component:  json-web-    |     Version:
>>> signature              |  Resolution:
>>> Severity:  -            |
>>> Keywords:               |
>>>
-------------------------+----------------------------------------------
>>> -------------------------+---
>>> 
>>> Ticket URL:
>>> <http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
>>> jose <http://tools.ietf.org/jose/>
>>> 
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>> 
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose

From James.H.Manger@team.telstra.com  Wed Jun 26 19:40:28 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45D3F11E80F9 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level: 
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YpOa-ZMyjNUR for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:40:11 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfa.amsl.com (Postfix) with ESMTP id C02AB11E80ED for <jose@ietf.org>; Wed, 26 Jun 2013 19:40:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,949,1363093200"; d="scan'208";a="143357070"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipoavi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 12:40:07 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7118"; a="140979844"
Received: from wsmsg3704.srv.dir.telstra.com ([172.49.40.197]) by ipccvi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 12:40:08 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3704.srv.dir.telstra.com ([172.49.40.197]) with mapi; Thu, 27 Jun 2013 12:40:07 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "jose@ietf.org" <jose@ietf.org>
Date: Thu, 27 Jun 2013 12:40:05 +1000
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5xxGXFBxC1FARbRReYSyWIKtodvABC/E+g
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com>
References: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com>
In-Reply-To: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 02:40:28 -0000

SSBkb24ndCB0aGluayB3ZSBzaG91bGQgc3RhbmRhcmRpemUgZHJhZnQtam9uZXMtam9zZS1hZXMt
Z2NtLWtleS13cmFwLTAwLiBObyByYXRpb25hbGUgaXMgYXBwYXJlbnQuIFdlIGFscmVhZHkgaGF2
ZSBhbiBBRVMtYmFzZWQga2V5IHdyYXAgYWxnb3JpdGhtIChBMTI4S1csIEEyNTZLVyksIHdoaWNo
IGhhcyBhIDY0LWJpdCBzaXplIG92ZXJoZWFkLiBUaGUgQUVTLUdDTSBrZXkgd3JhcCBhbGdvcml0
aG0gaW4gdGhpcyBkcmFmdCBhZGQgYWxtb3N0IG5vIHVzZWZ1bCBwcm9wZXJ0aWVzLCBidXQgaGFz
IGEgMjI0LWJpdCBzaXplIG92ZXJoZWFkLg0KDQpJIGxpa2UgdGhlIGNvbmNhdGVuYXRpb24gb2Yg
dGhlIElWLCBjaXBoZXJ0ZXh0LCBhbmQgdGFnIGJ5dGUgYXJyYXlzLiBCdXQgZG9pbmcgdGhpcyBo
ZXJlIHdoaWxlIGNvbnRlbnQgZW5jcnlwdGlvbiBzZXJpYWxpemVzIHRoZSBzYW1lIHZhbHVlcyBh
cyBkb3Qtc2VwYXJhdGVkIEI2NCBibG9icyBkb2VzIHNtZWxsIG9mIHBvb3IgYWQgaG9jIGRlc2ln
bi4gSXQgaXMgbmljZSB0byBoaWdobGlnaHQgaG93IGEgcHJldmlvdXMgY2hvaWNlIGNvbXBsaWNh
dGVzIGV4dGVuZGluZyBKT1NFIHRvIG90aGVyIGFsZ29yaXRobXMsIGJ1dCBvbmx5IGlmIHdlIHRo
ZW4gZml4IHRoYXQgcHJldmlvdXMgY2hvaWNlLg0KDQpJZiB0aGUgYWRkaXRpb25hbCBhdXRoZW50
aWNhdGVkIGRhdGEgKEFBRCkgd2FzIHVzZWQgdG8gYmluZCB0aGUgQ0VLIGFsZ29yaXRobSBpZCAo
b3Igb3RoZXIgY29udGV4dCBpbmZvLCBhcyBDb25jYXRLREYgZG9lcykgdG8gdGhlIHdyYXBwZWQg
a2V5LCB0aGVuIHRoZXJlIHdvdWxkIGF0IGxlYXN0IGJlIGFuIGV4dHJhIHNlY3VyaXR5IHByb3Bl
cnR5IHRoYXQgd291bGQgbWFrZSB0aGlzIGtleSB3cmFwIGFsZ29yaXRobSB3b3J0aCBjb25zaWRl
cmluZy4gRm9yIGluc3RhbmNlLCBpbnN0ZWFkIG9mIEFBRCBiZWluZyBlbXB0eSwgQUFEIGNvdWxk
IGJlIHRoZSAia2V5IHdyYXA6ICIgKyAiZW5jIiB2YWx1ZS4NCg0KQnkgcmV1c2luZyBhIENFSyBh
bGdvcml0aG0gYXMgYSBLRUsgYWxnb3JpdGhtLCBhbmQgc3VwcG9ydGluZyBkaXJlY3QgZW5jcnlw
dGlvbiwgd2Ugc3Vic3RhbnRpYWxseSBpbmNyZWFzZSB0aGUgcmlzayB0aGF0IGFuIGF0dGFja2Vy
IGNhbiByZWFycmFuZ2Ugc29tZSBlbmNyeXB0ZWQgY29udGVudCBzbyBhIGxlZ2l0aW1hdGUgcmVj
aXBpZW50IHRyZWF0cyBpdCBhcyBhbiBlbmNyeXB0ZWQga2V5IGxlYWRpbmcgdG8gc2VjdXJpdHkg
Zmxhd3MuDQoNCkZvciBleGFtcGxlLCBBbGljZSBzZW5kcyAiU3RhcnQgb2YgUElOID0gOCIgY29u
ZmlkZW50aWFsbHkgdG8gQm9iOg0KICB7YWxnOmRpcixlbmM6QTEyOEdDTSxraWQ6MX0uLml2LmNp
cGhlcnRleHQudGFnDQpBbiBhdHRhY2tlciBzZWVpbmcgdGhpcyBKT1NFIG1lc3NhZ2UgbGVhcm5z
IG5vdGhpbmcgYWJvdXQgdGhlIDFzdCBkaWdpdCBvZiB0aGUgUElOLg0KQnV0IGlmIHRoZSBhdHRh
Y2tlciBzZW5kcyAxMCBtZXNzYWdlcyB0byBCb2IgZm9yIDEwIGd1ZXNzIG9mIHRoYXQgZGlnaXQ6
DQogIHthbGc6QTEyOEdDTUtXLGVuYzpBMTI4R0NNLGtpZDoxfS5pdnxjaXBoZXJ0ZXh0fHRhZy5p
dk4uY2lwaGVydGV4dE4udGFnTg0Kd2hlcmUgaXZOLmNpcGhlcnRleHROLnRhZ04gYXJlIGNhbGN1
bGF0ZWQgdXNpbmcgYW4gQUVTIGtleSBvZiAiU3RhcnQgb2YgUElOID0gPE4+IiwgdGhlbiA5IG1l
c3NhZ2VzIHdpbGwgY2F1c2UgZXJyb3JzLCB3aGlsZSAxIG1lc3NhZ2Ugd2lsbCBiZSBhY2NlcHRl
ZCAtLSByZXZlYWxpbmcgdGhlIHN1cHBvc2VkbHkgY29uZmlkZW50aWFsIGluZm9ybWF0aW9uIGlu
IDEwIGd1ZXNzZXMgaW5zdGVhZCBvZiAyXjEyOC4NCg0KQWN0dWFsbHkgdGhlIGFib3ZlIGF0dGFj
ayBkb2VzIG5vdCBxdWl0ZSB3b3JrIGZvciB0aGUgY29tcGFjdCBlbmNvZGluZyBhcyBBQUQgaXMg
bmV2ZXIgZW1wdHkgZm9yIGNvbnRlbnQgZW5jcnlwdGlvbi4gSSBub3QgY2VydGFpbiBmb3IgdGhl
IEpTT04gZW5jb2RpbmcuIEluIGFueSBjYXNlLCBhbiBleHBsaWNpdCBhbmQgdW5hbWJpZ3VvdXMg
QUFEIHZhbHVlIGZvciBrZXkgd3JhcHBpbmcgd291bGQgYmUgZ29vZC4NCg0KRmluYWxseSwgYSBr
ZXkgd3JhcCBhbGdvcml0aG0gbGlrZSB0aGlzIHNob3VsZCBnbyB0byB0aGUgSUVURiBjcnlwdG8g
Z3JvdXAgKENSRkcpIGluc3RlYWQgb2YgYmVpbmcgaW52ZW50ZWQgaW4gSk9TRS4gV2UgaGF2ZSBh
bHJlYWR5IHNwZW50IGEgeWVhciB1bnBpY2tpbmcgYSBKT1NFLXNwZWNpYWwgQUVBRCBhbGdvcml0
aG0uDQoNCi0tDQpKYW1lcyBNYW5nZXINCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+IEZyb206IGpvc2UtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmpvc2UtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mDQo+IEppbSBTY2hhYWQNCj4gU2VudDogV2VkbmVzZGF5LCAyNiBK
dW5lIDIwMTMgMjo1MyBBTQ0KPiBUbzogam9zZUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBbam9zZV0g
SXNzdWUgIzEzIC0gdXNlIEFFUy1HQ00gZm9yIEtleSBXcmFwcGluZw0KPiANCj4gV2Ugbm93IGhh
dmUgdHdvIGRvY3VtZW50cyDigJMgb25lIGZyb20gUmljaGFyZCBhbmQgb25lIGZyb20gTWlrZSDi
gJMgd2hpY2gNCj4gcHJvdmlkZSB0aGUgdHdvIGRpZmZlcmVudCB3YXlzIHRoYXQgaGF2ZSBiZWVu
IHByb3Bvc2VkIGZvciBkb2luZyBrZXkNCj4gd3JhcHBpbmcgd2l0aCBhbiBBRUFEIGFsZ29yaXRo
bS4NCj4gDQo+IFBsZWFzZSByZXZpZXcgdGhlIHR3byBkb2N1bWVudHMgYW5kIHByb3ZpZGUgY29t
bWVudHMgdG8gdGhlIGxpc3QuDQo+IA0KPiBKaW0NCg0K

From n-sakimura@nri.co.jp  Wed Jun 26 19:55:20 2013
Return-Path: <n-sakimura@nri.co.jp>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B6EA11E8169 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhfnOe8TrooI for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 19:55:13 -0700 (PDT)
Received: from nrifs02.index.or.jp (nrigw01.index.or.jp [133.250.250.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD26011E80BA for <jose@ietf.org>; Wed, 26 Jun 2013 19:55:12 -0700 (PDT)
Received: from nriea02.index.or.jp (unknown [172.19.246.37]) by nrifs02.index.or.jp (Postfix) with SMTP id AE6E2196882; Thu, 27 Jun 2013 11:55:11 +0900 (JST)
Received: from nrims00a.nri.co.jp ([192.50.135.11]) by nriea02.index.or.jp (unknown) with ESMTP id r5R2tBfY019783; Thu, 27 Jun 2013 11:55:11 +0900
Received: from nrims00a.nri.co.jp (localhost.localdomain [127.0.0.1]) by nrims00a.nri.co.jp (Switch-3.3.3/Switch-3.3.3) with ESMTP id r5R2tBCO013313; Thu, 27 Jun 2013 11:55:11 +0900
Received: (from mailnull@localhost) by nrims00a.nri.co.jp (Switch-3.3.3/Switch-3.3.0/Submit) id r5R2tBhd013311; Thu, 27 Jun 2013 11:55:11 +0900
X-Authentication-Warning: nrims00a.nri.co.jp: mailnull set sender to n-sakimura@nri.co.jp using -f
Received: from nrizmf21b.index.or.jp ([172.100.25.20]) by nrims00a.nri.co.jp (Switch-3.3.3/Switch-3.3.3) with ESMTP id r5R2tB1i013305; Thu, 27 Jun 2013 11:55:11 +0900
Received: from 127.0.0.1 (127.0.0.1) by m-FILTER with ESMTP; Thu, 27 Jun 2013 11:55:11 +0900
Message-ID: <51CBA981.4050006@nri.co.jp>
Date: Thu, 27 Jun 2013 11:54:57 +0900
From: n-sakimura <n-sakimura@nri.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.12) Gecko/20130105 Thunderbird/10.0.12
MIME-Version: 1.0
To: Jim Schaad <ietf@augustcellars.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
In-Reply-To: <033a01ce729b$26bc3910$7434ab30$@augustcellars.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-MailAdviser: Ver1.3.3
Cc: michael.jones@microsoft.com, jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 02:55:20 -0000

Let me understand the problem.

Are you suggesting that we should be able to do something like:

Case 1:

      {"protected":<integrity-protected shared header contents>",
       "unprotected":<non-integrity-protected shared header contents>",
       "payload":"this is a multi\nline text payload of which a line can 
be very very very long and wrapped during transmission. "
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "signature":"<signature N contents>"}],
      }

or even

Case 2:

      {"protected":<integrity-protected shared header contents>",
       "unprotected":<non-integrity-protected shared header contents>",
       "payload":{
	"this":"is a json",
	"payload":"which is not base64url encoded"
       }
       "signatures":[
        {"header":"<per-signature unprotected header 1 contents>",
         "signature":"<signature 1 contents>"},
        ...
        {"header":"<per-signature unprotected header N contents>",
         "signature":"<signature N contents>"}],
      }

Then, I am worried about allowing them because in general we would not 
know what would a transmission mechanism and user agents (including text 
editors) would do to them, like Mike mentioned. I do not think we should 
assume the property of the transmission mechanism in JOSE level. 
Assuming that would cause brittleness in the implementations.

For detached signature, I do not understand why you would want 
non-base64url encoded payload. The application should define how to hash 
the octet stream that it wants to calculate signature over it, and we 
can just include the base64url encoded hash in the "payload".
Why would you like to do other encoding for the hash?

-- 
Nat Sakimura (n-sakimura@nri.co.jp)
Nomura Research Institute

PLEASE READ:
The information contained in this e-mail is confidential and intended 
for the named recipient(s) only.
If you are not an intended recipient of this e-mail, you are hereby 
notified that any review, dissemination, distribution or duplication of 
this message is strictly prohibited. If you have received this message 
in error, please notify the sender immediately and delete your copy from 
your system.

From ietf@augustcellars.com  Wed Jun 26 20:19:32 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6107F21F961F for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTt2ZM8BEXLH for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:27 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id A3A0D21F94FA for <jose@ietf.org>; Wed, 26 Jun 2013 20:19:27 -0700 (PDT)
Received: from Philemon (ip-64-134-233-240.public.wayport.net [64.134.233.240]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 6EF1F2CA0C; Wed, 26 Jun 2013 20:19:26 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <draft-ietf-jose-json-web-signature@tools.ietf.org>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 20:18:29 -0700
Message-ID: <03b401ce72e5$002c65f0$008531d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvAtXnsooCfmP1+5lS3btg
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 03:19:32 -0000

I would strongly encourage everyone in the JOSE list to join the JSON =
list and read what was is there and participate.

That being said there are situations where you might not be able to do =
an independent parser.  And in fact what you have stated is that there =
is now a requirement that a JOSE library supply a JSON parser.  Is that =
really what we want to say?  How far from creating a set of generator =
and parser requirements that are non standard and requiring a =
parser/generator are we from that?

> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Wednesday, June 26, 2013 12:30 PM
> To: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional =
text
>=20
> The operable sentence in my suggested text below is this one: "If the
> platform's JSON parser does not reject input with duplicate member =
names,
> the input will first need to be separately parsed to reject these =
invalid inputs
> before using the platform's parser".  In other words, if the JSON =
parser in the
> development platform you are using does not reject inputs with =
duplicate
> member names, you will need to write a separate JSON parser that =
detects
> this invalid input and rejects it.
>=20
> This parser could either just be a validator, returning TRUE or FALSE =
for
> whether the JSON is valid for JOSE - in which case you'd then pass any =
inputs
> validating as TRUE to the platform's JSON parser, or it could be a =
replacement
> parser, in which case your code would not use the development =
platform's
> JSON parser at all.  I suspect people would be more likely to do the =
former
> than the latter, but both approaches are equivalent.
>=20
> BTW, if it's your sense that there's a problem occurring in the JSON =
working
> group with respect to enabling strict JSON parsing, we probably need =
to
> become active there.  For instance, even if the spec allows duplicate =
member
> names like the ECMA spec does, the RFC could recommend or require that
> parsers support a "strict" mode, which rejects these unnecessarily lax =
inputs.
> Then JOSE implementations could use that.
>=20
> 				-- Mike
>=20
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Wednesday, June 26, 2013 11:30 AM
> To: 'jose issue tracker'; =
draft-ietf-jose-json-web-signature@tools.ietf.org;
> Mike Jones
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional =
text
>=20
> <no hat>
>=20
> I consider myself to be reasonably competent in both English and =
Technical
> English.  I have no idea what I am supposed to be doing to deal with =
the text
> below.  Does this mean that I need to write an independent parser?  =
What
> about cases where it is coming in on a stream and I don't get to see =
the data
> before the parse occurs?  How are they interpreted differently?  What
> exactly is this supposed to be addressing.  Much of this could be =
skipped
> when we said don't do it.  Since this is no longer a viable statement =
due to the
> state of parsers, we need to be more explicit and say what is going =
on.
>=20
> No I don't consider the suggested text to be adequate.
>=20
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > Of jose issue tracker
> > Sent: Tuesday, June 25, 2013 5:41 PM
> > To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > michael.jones@microsoft.com
> > Cc: jose@ietf.org
> > Subject: Re: [jose] #27: member names MUST be unique needs =
additional
> > text
> >
> > #27: member names MUST be unique needs additional text
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> >  The JWS draft currently says:
> >
> >          The Header Parameter Names within the JWS Header MUST be =
unique;
> >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> >
> >  How about changing this to:
> >
> >          The Header Parameter Names within the JWS Header MUST be =
unique;
> >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> >          This is necessary to prevent attacks in which the same JWS
> > might  be interpreted
> >          in different ways by different implementations and to =
prevent
> attackers
> >          from hiding extra content in duplicate member values.
> >          If the platform s JSON parser does not reject input with
> > duplicate member names,
> >          the input will first need to be separately parsed to reject
> > these  invalid inputs
> >          before using the platform s parser.
> >
> > --
> > =
-------------------------+--------------------------------------------
> > -------------------------+--
> > -------------------------+---
> >  Reporter:               |       Owner:  draft-ietf-jose-json-web-
> >   ietf@augustcellars.com |  signature@tools.ietf.org
> >      Type:  defect       |      Status:  new
> >  Priority:  major        |   Milestone:
> > Component:  json-web-    |     Version:
> >   signature              |  Resolution:
> >  Severity:  -            |
> >  Keywords:               |
> > =
-------------------------+--------------------------------------------
> > -------------------------+--
> > -------------------------+---
> >
> > Ticket URL:
> > <http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
> > jose <http://tools.ietf.org/jose/>
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose



From ietf@augustcellars.com  Wed Jun 26 20:19:32 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7728921F94FA for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.732
X-Spam-Level: 
X-Spam-Status: No, score=-2.732 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSxmFTfZjqHn for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:27 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id A3C9D21F94FF for <jose@ietf.org>; Wed, 26 Jun 2013 20:19:27 -0700 (PDT)
Received: from Philemon (ip-64-134-233-240.public.wayport.net [64.134.233.240]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id C4AD82C9F5; Wed, 26 Jun 2013 20:19:25 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com> <4E1F6AAD24975D4BA5B168042967394367899098@TK5EX14MBXC283.redmond.corp.microsoft.com> <033c01ce729b$272470c0$756d5240$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B518@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789B518@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 20:18:29 -0700
Message-ID: <03ab01ce72e4$ff693d00$fe3bb700$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03AC_01CE72AA.530BC490"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGcpZW0SYDqCTp0n8LDt7OsdLmuBgJzXos9AQY8OhEDTET/xpl2Idpg
Content-Language: en-us
Subject: Re: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 03:19:32 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03AC_01CE72AA.530BC490
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Sure, the time limit would be when we finish the WG last call.  We can go
into last call with open issues if we do not believe that are blocking in
any way.

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Wednesday, June 26, 2013 12:35 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Teleconference July 1 Agenda

 

Can we please set a time limit on #5, after which we will close the issue if
Richard hasn't produced the table he suggested?  This issue was addressed
two months and three drafts ago, which is ample time for the working group
to have reviewed the text.  At least to my way of thinking, it's not
reasonable to hold an issue open indefinitely due to inactivity of a
potential contributor.

 

I'll look at your comments on #15 and try to respond before Monday's call.

 

                                                                Thanks,

                                                                -- Mike

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org
Subject: RE: [jose] Teleconference July 1 Agenda

 

#5 is blocked on getting information from Richard

#14 is blocked on issue #13

#15 still needs to get review.  I have sent you a number of comments about
this which need to be addressed.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Tuesday, June 25, 2013 5:32 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Teleconference July 1 Agenda

 

Please add these issues to the agenda:  #5, #14, and #15.  Suggested agenda
text follows.

 

Issue #5 - Unclear instructions for key management

                Discuss closing this issue as "fixed", as text addressing it
was added in the -09 drafts

 

Issue #14 - Support longer wrapped keys than OAEP allows

                Discuss closing this issue as "won't fix", as it will not
occur in practice

 

Issue #15 - At least one key indicator should be mandatory

                Discuss closing this issue as "fixed", as text addressing it
was added in -11, as proposed by the WG in Denver

 

                                                                Thanks,

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 25, 2013 9:51 AM
To: jose@ietf.org
Subject: [jose] Teleconference July 1 Agenda

 

Agenda has been posted
http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interi
m-2013-jose-3

 


------=_NextPart_000_03AC_01CE72AA.530BC490
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Sure, the time limit would be when we finish the =
WG last call.&nbsp; We can go into last call with open issues if we do =
not believe that are blocking in any way.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Wednesday, June 26, 2013 12:35 PM<br><b>To:</b> Jim Schaad; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Teleconference July 1 =
Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Can we please set a time limit on #5, after =
which we will close the issue if Richard hasn&#8217;t produced the table =
he suggested?&nbsp; This issue was addressed two months and three drafts =
ago, which is ample time for the working group to have reviewed the =
text.&nbsp; At least to my way of thinking, it&#8217;s not reasonable to =
hold an issue open indefinitely due to inactivity of a potential =
contributor.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I&#8217;ll look at your =
comments on #15 and try to respond before Monday&#8217;s =
call.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Wednesday, June 26, 2013 11:30 AM<br><b>To:</b> Mike =
Jones; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Teleconference July 1 Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#5 is blocked on getting information from =
Richard<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#14 is blocked on issue =
#13<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>#15 still needs to get review. &nbsp;I have sent =
you a number of comments about this which need to be =
addressed.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [<a =
href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsof=
t.com</a>] <br><b>Sent:</b> Tuesday, June 25, 2013 5:32 PM<br><b>To:</b> =
Jim Schaad; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Teleconference July 1 Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Please add these issues to the agenda:&nbsp; #5, =
#14, and #15.&nbsp; Suggested agenda text =
follows.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #5 - Unclear =
instructions for key management<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;fixed&#8221;, as text addressing it was added in the -09 =
drafts<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #14 - Support =
longer wrapped keys than OAEP allows<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;won&#8217;t fix&#8221;, as it will not occur in =
practice<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Issue #15 - At least one =
key indicator should be mandatory<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Discuss closing this issue as =
&#8220;fixed&#8221;, as text addressing it was added in -11, as proposed =
by the WG in Denver<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Tuesday, June 25, 2013 =
9:51 AM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] Teleconference July 1 Agenda<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Agenda has =
been posted <a =
href=3D"http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/ag=
enda-interim-2013-jose-3">http://www.ietf.org/proceedings/interim/2013/07=
/01/jose/agenda/agenda-interim-2013-jose-3</a><o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_03AC_01CE72AA.530BC490--


From ietf@augustcellars.com  Wed Jun 26 20:19:38 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0786E21F964C for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.948
X-Spam-Level: 
X-Spam-Status: No, score=-2.948 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4jjLm4LRP-c for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:32 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6466A21F94DC for <jose@ietf.org>; Wed, 26 Jun 2013 20:19:29 -0700 (PDT)
Received: from Philemon (ip-64-134-233-240.public.wayport.net [64.134.233.240]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id D1E892CA15; Wed, 26 Jun 2013 20:19:27 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <034101ce729b$27473b00$75d5b100$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 20:18:29 -0700
Message-ID: <03b901ce72e5$01248190$036d84b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03BA_01CE72AA.54F767F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH9pEpqg6SA+ykRJHySAR3RzJ5mhAI1BH/RAavUVGWYy0uIcA==
Content-Language: en-us
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 03:19:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_03BA_01CE72AA.54F767F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

My point was that there were some issues that your draft did not fully
address that need to be evaluated as part of your proposal not that these
algorithms would need to be added.  The n x m addition of algorithms to the
registry is an issue that is there for your draft that is not present for
Richard's draft and therefore needs to be considered in the arguments.

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Wednesday, June 26, 2013 12:22 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

Yes, we could also propose algorithm combinations for key agreement followed
GCM key wrapping but I didn't think that was an ask from the working group.
The Denver minutes just recorded my action item as "key wrap draft for
AES-GCM-keywrap", so that's what I did.  We could have a discussion on
Monday's call and on the list about whether the working group is also
interested in other algorithms.

 

Remember, the beauty of having the algorithms registry is that algorithms
can be added "just in time" - as actual need for them is demonstrated.  We
don't have to register all conceivable algorithm combinations up front for
the JWE/JWA specs to be complete.

 

As for how the AEAD parameters are handled I used a parameter encoding that
doesn't result in double base64url encoding anything.  I could have instead
introduced separate "iv" and "tag" header parameter values, but didn't do so
for that reason.  But if people would prefer that approach because it's more
parallel to the use of GCM for plaintext encryption, I have no problem with
that.

 

I do believe that the objective of my draft was met - demonstrating that
AEAD key wrapping can be easily done with the current drafts.  The details
of how the algorithm parameters are encoded is secondary to that and
algorithm-specific; several reasonable choices are possible within the
current JWE framework - one of which was described in my draft.

 

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

<no hat>

<sarcasm level="heavy">

 

I am shocked that you would possibly support this proposal.  It provides for
two ways of dealing with something.  It is my understanding that you never
support anything that has two ways of doing something.

 

How the AEAD algorithm parameters is handled completely differently for this
proposal and for the same algorithms being used in a CEK context.  This is
going to lead to confusion.

 

</sarcasm>

 

Your specification is missing some items that still need to be registered
Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined
in your document as well.

 

Your document ends up with a registration complexity that needs to be
thought about and dealt with as well.  For every new key wrap algorithm
added, you will need to register not only it alone but also it with every
different key agreement algorithm that is supported.  Thus adding a single
key wrap algorithm becomes a slight issue in terms of adding in all of the
different ways that it might be used.  This is a complexity issue that is
not discussed in the current draft.

 

I have not necessarily found that document size equals code size.  I have
implemented some very simple documents that were very difficult to code and
implemented some very long documents that were very easy to code.  So I
would not use that fact as a deciding factor.

 

(Once again I regret the fact that the group did not go with an object
descriptor for algorithms as this would have made all of this much simpler.
I actually immediately map from the string to an object description in my
JOSE implementation for simplicity reasons.  Not to mention that this is way
it needs to be done for the WebCrypto specficiation.)

 

Jim

 

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Tuesday, June 25, 2013 4:18 PM
To: 'Jim Schaad'; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like a
substantially simpler approach than
http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01.  This is
evident by several metrics:

.         Number of proposed changes:  The Jones draft proposes no changes
to any of the current specs.  It simply defines an encoding for GCM and adds
registry entries for it.  Whereas the Barnes draft proposes a major
restructuring - listing 4 major changes in the introduction and 4 smaller
changes.

.         Normative text size:  The Jones GCM key wrap approach requires
only 7 normative sentences in 1/2 page of text.  The Barnes draft has four
pages of normative text, along with an extensive introduction describing the
proposed complete restructuring of JWS and JWE.

 

We don't need to boil the ocean with a total redesign to enable AEAD key
wrapping.  It can already easily be done with the current specs simply by
defining new algorithms.  The approach taken in
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would work
for any AEAD algorithm.

 

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

We now have two documents - one from Richard and one from Mike - which
provide the two different ways that have been proposed for doing key
wrapping with an AEAD algorithm.

 

Please review the two documents and provide comments to the list.

 

Jim

 


------=_NextPart_000_03BA_01CE72AA.54F767F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>My point was that there were some issues that =
your draft did not fully address that need to be evaluated as part of =
your proposal not that these algorithms would need to be added. =
&nbsp;The n x m addition of algorithms to the registry is an issue that =
is there for your draft that is not present for Richard&#8217;s draft =
and therefore needs to be considered in the =
arguments.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Wednesday, June 26, 2013 12:22 PM<br><b>To:</b> Jim Schaad; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for =
Key Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Yes, we could also propose algorithm =
combinations for key agreement followed GCM key wrapping but I =
didn&#8217;t think that was an ask from the working group.&nbsp; The =
Denver minutes just recorded my action item as &#8220;key wrap draft for =
AES-GCM-keywrap&#8221;, so that&#8217;s what I did.&nbsp; We could have =
a discussion on Monday&#8217;s call and on the list about whether the =
working group is also interested in other =
algorithms.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Remember, the beauty of =
having the algorithms registry is that algorithms can be added =
&#8220;just in time&#8221; &#8211; as actual need for them is =
demonstrated.&nbsp; We don&#8217;t have to register all conceivable =
algorithm combinations up front for the JWE/JWA specs to be =
complete.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>As for how the AEAD =
parameters are handled I used a parameter encoding that doesn&#8217;t =
result in double base64url encoding anything.&nbsp; I could have instead =
introduced separate &#8220;iv&#8221; and &#8220;tag&#8221; header =
parameter values, but didn&#8217;t do so for that reason.&nbsp; But if =
people would prefer that approach because it&#8217;s more parallel to =
the use of GCM for plaintext encryption, I have no problem with =
that.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I do believe that the =
objective of my draft was met &#8211; demonstrating that AEAD key =
wrapping can be easily done with the current drafts.&nbsp; The details =
of how the algorithm parameters are encoded is secondary to that and =
algorithm-specific; several reasonable choices are possible within the =
current JWE framework &#8211; one of which was described in my =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Wednesday, June 26, 2013 =
11:30 AM<br><b>To:</b> Mike Jones; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;no hat&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>&lt;sarcasm =
level=3D&#8221;heavy&#8221;&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am shocked that you =
would possibly support this proposal.&nbsp; It provides for two ways of =
dealing with something.&nbsp; It is my understanding that you never =
support anything that has two ways of doing =
something.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>How the AEAD algorithm =
parameters is handled completely differently for this proposal and for =
the same algorithms being used in a CEK context. &nbsp;This is going to =
lead to confusion.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;/sarcasm&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your specification is =
missing some items that still need to be registered&nbsp; Thus you also =
need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined in your =
document as well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your document ends up =
with a registration complexity that needs to be thought about and dealt =
with as well.&nbsp; For every new key wrap algorithm added, you will =
need to register not only it alone but also it with every different key =
agreement algorithm that is supported. &nbsp;Thus adding a single key =
wrap algorithm becomes a slight issue in terms of adding in all of the =
different ways that it might be used.&nbsp; This is a complexity issue =
that is not discussed in the current draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I have not necessarily =
found that document size equals code size.&nbsp; I have implemented some =
very simple documents that were very difficult to code and implemented =
some very long documents that were very easy to code.&nbsp; So I would =
not use that fact as a deciding factor.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>(Once again I regret the =
fact that the group did not go with an object descriptor for algorithms =
as this would have made all of this much simpler.&nbsp; I actually =
immediately map from the string to an object description in my JOSE =
implementation for simplicity reasons.&nbsp; Not to mention that this is =
way it needs to be done for the WebCrypto =
specficiation.)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [<a =
href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsof=
t.com</a>] <br><b>Sent:</b> Tuesday, June 25, 2013 4:18 PM<br><b>To:</b> =
'Jim Schaad'; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
seems like a substantially simpler approach than <a =
href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">htt=
p://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; =
This is evident by several metrics:<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Number of =
proposed changes:&nbsp; The Jones draft proposes no changes to any of =
the current specs.&nbsp; It simply defines an encoding for GCM and adds =
registry entries for it.&nbsp; Whereas the Barnes draft proposes a major =
restructuring &#8211; listing 4 major changes in the introduction and 4 =
smaller changes.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Normative =
text size:&nbsp; The Jones GCM key wrap approach requires only 7 =
normative sentences in 1/2 page of text.&nbsp; The Barnes draft has four =
pages of normative text, along with an extensive introduction describing =
the proposed complete restructuring of JWS and =
JWE.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>We don&#8217;t need to =
boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; =
It can already easily be done with the current specs simply by defining =
new algorithms.&nbsp; The approach taken in <a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
would work for any AEAD algorithm.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Tuesday, June 25, 2013 =
9:53 AM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We now have =
two documents &#8211; one from Richard and one from Mike &#8211; which =
provide the two different ways that have been proposed for doing key =
wrapping with an AEAD algorithm.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the two documents and provide comments to the =
list.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_03BA_01CE72AA.54F767F0--


From ietf@augustcellars.com  Wed Jun 26 20:19:38 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF3F21F9649 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.079
X-Spam-Level: 
X-Spam-Status: No, score=-3.079 tagged_above=-999 required=5 tests=[AWL=0.520,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OhK6lKpFK1qU for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 20:19:32 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id D266821F957B for <jose@ietf.org>; Wed, 26 Jun 2013 20:19:29 -0700 (PDT)
Received: from Philemon (ip-64-134-233-240.public.wayport.net [64.134.233.240]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id AD60C2C9F5; Wed, 26 Jun 2013 20:19:29 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org>	<076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B3BC@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789B3BC@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 20:18:29 -0700
Message-ID: <03c101ce72e5$01bffe40$053ffac0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbtMM0AVMbmndwUUG6vntocHGkoALWvDclApUnp/sBskfd3Jn1Pj6Q
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 03:19:38 -0000

What I am proposing is that it is an option to "harden" the content, but is
not required.  What is signed and what is transported are the same, but what
is signed may or may not be suitable for the compact encoding.

One would always be able to switch from the compact to the JSON
serialization, however the reverse transformation may not always be
possible.  This would be one more reason why it would not be possible, but
there are many others.

What I originally described would by how I would approach it from a library
basis.  However, there are many things that applications can do that are not
doable by a library and a library would only give some additional options to
what was doable.  This means that while I said that the application would be
required to base64url encode the content, it could do this by passing an
indicator to the library that this was the desired behavior (for example by
calling the SignForCompactEncoding function).

The primary purpose of base64 encoding is not to harden the content to
protect from changes, it is to allow you to do the compact encoding and
transport it in a URL.   If you are worried about things which are going to
muck with the content, they are going to be happy to parse it up, unbase64
encode it, muck with it and write it back out.  This does not prevent a
determined entity from doing the mucking.   If I pass the content as a
string field in a JSON encoded object, then nobody is going to much with it
by default.  They are going to need to know that the need to muck with it
before they start.

> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Wednesday, June 26, 2013 12:10 PM
> To: Jim Schaad
> Cc: jose@ietf.org
> Subject: RE: [jose] #26: Allow for signature payload to not be base64
encoded
> 
> Maybe I'm confused about what you were proposing.  These are the two ways
> of doing something that I thought you were describing:
> 
> 1.  Have the signature payload be base64url encoded (the status quo) 2.
Have
> the signature payload be unencoded in the JSON Serialization if a flag is
set in
> the header
> 
> If you're proposing that the default be unencoded for the JSON
Serialization,
> that has the pitfall that a simple syntactic transformation is no longer
possible
> between the Compact Serialization and the JSON Serialization.  The two
would
> have unnecessarily diverged.
> 
> If I misunderstood your proposal, maybe you could describe it in closer to
> normative language - for instance, defining the flag you propose to say
that
> the payload is not base64url encoded and saying what its semantics would
be
> for the JSON Serialization and the Compact Serialization.
> 
> BTW, your response didn't address the point that a primary purpose of the
> base64url encoding is to harden the payload against changes that might
> otherwise occur during transmission.  Not hardening the payload will
almost
> certainly lead to hard-to-debug interop problems in practice.
> 
> 				-- Mike
> 
> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
Jim
> Schaad
> Sent: Wednesday, June 26, 2013 11:30 AM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones
> Cc: jose@ietf.org
> Subject: Re: [jose] #26: Allow for signature payload to not be base64
encoded
> 
> Having multiple ways to do something can frequently buy you a great deal
of
> benefit.  However, in this case it is my library that is doing this and
not the
> standard.
> 
> The client gives the library an 8-bit string.  The library signs that
string.  The
> library puts that string into the payload field.
> 
> The client needs to make the 8-bit string URL safe if it wants to use
compact
> encoding.
> 
> Where is there two ways of doing something?
> 
> Jim
> 
> 
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > Of jose issue tracker
> > Sent: Tuesday, June 25, 2013 5:23 PM
> > To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > michael.jones@microsoft.com
> > Cc: jose@ietf.org
> > Subject: Re: [jose] #26: Allow for signature payload to not be base64
> > encoded
> >
> > #26: Allow for signature payload to not be base64 encoded
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> >  Having multiple ways to do something is one of the classic pitfalls
> > to  avoid in standards.  They tend to generate interop problems
> > because  developers will often only build the way that they think they
need,
> never
> >  getting around to the others.   I don t think the potential benefits of
> >  having multiple ways to encode the payload outweigh this cost.
> >
> >  Next, this feature would only work with the JSON serialization; it
> > would  not work for the Compact Serialization because the payload must
be
> URL  safe.
> > The base64url encoding accomplishes that, and so is a necessary  part
> > of the encoding.  Having the two serializations diverge in this manner
> > seems suboptimal.
> >
> >  Third, I am concerned that the payload will sometimes change during
> > transmission if not encoded in some manner.  Tabs can change to spaces.
> >  LFs can change to CRLFs.  HTML is notorious for adding a blank at the
> > end  of each line.  Two spaces can change to a space and a non-breaking
> space.
> >  Etc.  Not encoding the payload would open us up to all of these
potential
> > modification-during-transmission problems   all of which would render
the
> > JWS useless by breaking the signature.
> >
> >  Finally, this feature seems to be motivated by detached signatures,
> > which  per my comment on Ticket #25, can be accomplished at the
> > application layer without adding general-purpose support for detached
> > signatures.  Thus, I  don t think this related feature is needed either.
> >
> >  For all these reasons, I believe that this issue should be closed as
won t fix .
> >
> > --
> > -------------------------+--------------------------------------------
> > -------------------------+--
> > -------------------------+---
> >  Reporter:               |       Owner:  draft-ietf-jose-json-web-
> >   ietf@augustcellars.com |  signature@tools.ietf.org
> >      Type:  defect       |      Status:  new
> >  Priority:  major        |   Milestone:
> > Component:  json-web-    |     Version:
> >   signature              |  Resolution:
> >  Severity:  -            |
> >  Keywords:               |
> > -------------------------+--------------------------------------------
> > -------------------------+--
> > -------------------------+---
> >
> > Ticket URL:
> > <http://trac.tools.ietf.org/wg/jose/trac/ticket/26#comment:1>
> > jose <http://tools.ietf.org/jose/>
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
> 
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From Michael.Jones@microsoft.com  Wed Jun 26 21:16:48 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DABFF11E8101 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ox1ObfJhu-ca for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:16:43 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id 09A8811E80FA for <jose@ietf.org>; Wed, 26 Jun 2013 21:16:42 -0700 (PDT)
Received: from BL2FFO11FD005.protection.gbl (10.173.161.201) by BL2FFO11HUB036.protection.gbl (10.173.161.116) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 27 Jun 2013 04:01:32 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD005.mail.protection.outlook.com (10.173.161.1) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Thu, 27 Jun 2013 04:01:32 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 04:01:15 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5x+kWA5ynNruFyScOmFXp2dnVQrAAoOBMAAAFzy1AAEQJogAABTLoQ
Date: Thu, 27 Jun 2013 04:01:14 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789D481@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <034101ce729b$27473b00$75d5b100$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b901ce72e5$01248190$036d84b0$@augustcellars.com>
In-Reply-To: <03b901ce72e5$01248190$036d84b0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739436789D481TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(5383001)(199002)(189002)(377454003)(19300405004)(44976004)(51856001)(561944002)(16236675002)(63696002)(50986001)(69226001)(6806003)(47976001)(4396001)(20776003)(49866001)(47736001)(74502001)(56776001)(74662001)(47446002)(54356001)(74366001)(33656001)(71186001)(66066001)(74706001)(74876001)(81542001)(56816003)(76482001)(77096001)(77982001)(16406001)(59766001)(55846006)(80022001)(512954002)(46102001)(54316002)(79102001)(53806001)(76786001)(31966008)(81342001)(15202345003)(76796001)(65816001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB036; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 04:16:49 -0000

--_000_4E1F6AAD24975D4BA5B16804296739436789D481TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

For my part, I consider the fact that people will need to register specific=
 algorithm combinations that they actually need to be a feature - not a bug=
.  The smaller the set of algorithm combinations registered, the more likel=
y that they will be implemented and will interoperate.  Trying to claim tha=
t we support the combinatorial explosion of mask generation functions, hash=
 functions, key derivation functions, key wrapping functions, etc. that are=
 possible will almost certainly result in less interoperability and more de=
veloper confusion than a small set of registered choices, carefully conside=
red.  I'm glad to have people consider these criteria in their evaluation o=
f the two choices.

                                                                           =
-- Mike

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Wednesday, June 26, 2013 8:18 PM
To: Mike Jones; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

My point was that there were some issues that your draft did not fully addr=
ess that need to be evaluated as part of your proposal not that these algor=
ithms would need to be added.  The n x m addition of algorithms to the regi=
stry is an issue that is there for your draft that is not present for Richa=
rd's draft and therefore needs to be considered in the arguments.

From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Wednesday, June 26, 2013 12:22 PM
To: Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

Yes, we could also propose algorithm combinations for key agreement followe=
d GCM key wrapping but I didn't think that was an ask from the working grou=
p.  The Denver minutes just recorded my action item as "key wrap draft for =
AES-GCM-keywrap", so that's what I did.  We could have a discussion on Mond=
ay's call and on the list about whether the working group is also intereste=
d in other algorithms.

Remember, the beauty of having the algorithms registry is that algorithms c=
an be added "just in time" - as actual need for them is demonstrated.  We d=
on't have to register all conceivable algorithm combinations up front for t=
he JWE/JWA specs to be complete.

As for how the AEAD parameters are handled I used a parameter encoding that=
 doesn't result in double base64url encoding anything.  I could have instea=
d introduced separate "iv" and "tag" header parameter values, but didn't do=
 so for that reason.  But if people would prefer that approach because it's=
 more parallel to the use of GCM for plaintext encryption, I have no proble=
m with that.

I do believe that the objective of my draft was met - demonstrating that AE=
AD key wrapping can be easily done with the current drafts.  The details of=
 how the algorithm parameters are encoded is secondary to that and algorith=
m-specific; several reasonable choices are possible within the current JWE =
framework - one of which was described in my draft.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping

<no hat>
<sarcasm level=3D"heavy">

I am shocked that you would possibly support this proposal.  It provides fo=
r two ways of dealing with something.  It is my understanding that you neve=
r support anything that has two ways of doing something.

How the AEAD algorithm parameters is handled completely differently for thi=
s proposal and for the same algorithms being used in a CEK context.  This i=
s going to lead to confusion.

</sarcasm>

Your specification is missing some items that still need to be registered  =
Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined =
in your document as well.

Your document ends up with a registration complexity that needs to be thoug=
ht about and dealt with as well.  For every new key wrap algorithm added, y=
ou will need to register not only it alone but also it with every different=
 key agreement algorithm that is supported.  Thus adding a single key wrap =
algorithm becomes a slight issue in terms of adding in all of the different=
 ways that it might be used.  This is a complexity issue that is not discus=
sed in the current draft.

I have not necessarily found that document size equals code size.  I have i=
mplemented some very simple documents that were very difficult to code and =
implemented some very long documents that were very easy to code.  So I wou=
ld not use that fact as a deciding factor.

(Once again I regret the fact that the group did not go with an object desc=
riptor for algorithms as this would have made all of this much simpler.  I =
actually immediately map from the string to an object description in my JOS=
E implementation for simplicity reasons.  Not to mention that this is way i=
t needs to be done for the WebCrypto specficiation.)

Jim



From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Tuesday, June 25, 2013 4:18 PM
To: 'Jim Schaad'; jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like =
a substantially simpler approach than http://tools.ietf.org/html/draft-barn=
es-jose-key-wrapping-01.  This is evident by several metrics:

*        Number of proposed changes:  The Jones draft proposes no changes t=
o any of the current specs.  It simply defines an encoding for GCM and adds=
 registry entries for it.  Whereas the Barnes draft proposes a major restru=
cturing - listing 4 major changes in the introduction and 4 smaller changes=
.

*        Normative text size:  The Jones GCM key wrap approach requires onl=
y 7 normative sentences in 1/2 page of text.  The Barnes draft has four pag=
es of normative text, along with an extensive introduction describing the p=
roposed complete restructuring of JWS and JWE.

We don't need to boil the ocean with a total redesign to enable AEAD key wr=
apping.  It can already easily be done with the current specs simply by def=
ining new algorithms.  The approach taken in http://tools.ietf.org/html/dra=
ft-jones-jose-aes-gcm-key-wrap-00 would work for any AEAD algorithm.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org] On Behalf Of Jim Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org<mailto:jose@ietf.org>
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

We now have two documents - one from Richard and one from Mike - which prov=
ide the two different ways that have been proposed for doing key wrapping w=
ith an AEAD algorithm.

Please review the two documents and provide comments to the list.

Jim


--_000_4E1F6AAD24975D4BA5B16804296739436789D481TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">For my part, I conside=
r the fact that people will need to register specific algorithm combination=
s that they actually need to be a feature &#8211; not a bug.&nbsp; The smal=
ler the set of algorithm combinations registered,
 the more likely that they will be implemented and will interoperate.&nbsp;=
 Trying to claim that we support the combinatorial explosion of mask genera=
tion functions, hash functions, key derivation functions, key wrapping func=
tions, etc. that are possible will almost
 certainly result in less interoperability and more developer confusion tha=
n a small set of registered choices, carefully considered.&nbsp; I&#8217;m =
glad to have people consider these criteria in their evaluation of the two =
choices.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Wednesday, June 26, 2013 8:18 PM<br>
<b>To:</b> Mike Jones; jose@ietf.org<br>
<b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">My point was that ther=
e were some issues that your draft did not fully address that need to be ev=
aluated as part of your proposal not that these algorithms would need to be=
 added. &nbsp;The n x m addition of algorithms
 to the registry is an issue that is there for your draft that is not prese=
nt for Richard&#8217;s draft and therefore needs to be considered in the ar=
guments.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Wednesday, June 26, 2013 12:22 PM<br>
<b>To:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><b=
r>
<b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Yes, we could also pro=
pose algorithm combinations for key agreement followed GCM key wrapping but=
 I didn&#8217;t think that was an ask from the working group.&nbsp; The Den=
ver minutes just recorded my action item as &#8220;key
 wrap draft for AES-GCM-keywrap&#8221;, so that&#8217;s what I did.&nbsp; W=
e could have a discussion on Monday&#8217;s call and on the list about whet=
her the working group is also interested in other algorithms.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Remember, the beauty o=
f having the algorithms registry is that algorithms can be added &#8220;jus=
t in time&#8221; &#8211; as actual need for them is demonstrated.&nbsp; We =
don&#8217;t have to register all conceivable algorithm combinations
 up front for the JWE/JWA specs to be complete.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As for how the AEAD pa=
rameters are handled I used a parameter encoding that doesn&#8217;t result =
in double base64url encoding anything.&nbsp; I could have instead introduce=
d separate &#8220;iv&#8221; and &#8220;tag&#8221; header parameter values,
 but didn&#8217;t do so for that reason.&nbsp; But if people would prefer t=
hat approach because it&#8217;s more parallel to the use of GCM for plainte=
xt encryption, I have no problem with that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I do believe that the =
objective of my draft was met &#8211; demonstrating that AEAD key wrapping =
can be easily done with the current drafts.&nbsp; The details of how the al=
gorithm parameters are encoded is secondary to
 that and algorithm-specific; several reasonable choices are possible withi=
n the current JWE framework &#8211; one of which was described in my draft.=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Wednesday, June 26, 2013 11:30 AM<br>
<b>To:</b> Mike Jones; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><b=
r>
<b>Subject:</b> Re: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;no hat&gt;<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;sarcasm level=3D&#=
8221;heavy&#8221;&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I am shocked that you =
would possibly support this proposal.&nbsp; It provides for two ways of dea=
ling with something.&nbsp; It is my understanding that you never support an=
ything that has two ways of doing something.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">How the AEAD algorithm=
 parameters is handled completely differently for this proposal and for the=
 same algorithms being used in a CEK context. &nbsp;This is going to lead t=
o confusion.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&lt;/sarcasm&gt;<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Your specification is =
missing some items that still need to be registered&nbsp; Thus you also nee=
d to have ECDH-ES&#43;A128GCMKW and ECDH-ES&#43;A256GCMKW defined in your d=
ocument as well.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Your document ends up =
with a registration complexity that needs to be thought about and dealt wit=
h as well.&nbsp; For every new key wrap algorithm added, you will need to r=
egister not only it alone but also it with
 every different key agreement algorithm that is supported. &nbsp;Thus addi=
ng a single key wrap algorithm becomes a slight issue in terms of adding in=
 all of the different ways that it might be used.&nbsp; This is a complexit=
y issue that is not discussed in the current
 draft.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have not necessarily=
 found that document size equals code size.&nbsp; I have implemented some v=
ery simple documents that were very difficult to code and implemented some =
very long documents that were very easy to
 code.&nbsp; So I would not use that fact as a deciding factor.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">(Once again I regret t=
he fact that the group did not go with an object descriptor for algorithms =
as this would have made all of this much simpler.&nbsp; I actually immediat=
ely map from the string to an object description
 in my JOSE implementation for simplicity reasons.&nbsp; Not to mention tha=
t this is way it needs to be done for the WebCrypto specficiation.)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jim<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Tuesday, June 25, 2013 4:18 PM<br>
<b>To:</b> 'Jim Schaad'; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a>=
<br>
<b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><a href=3D"http://tool=
s.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">http://tools.ietf.org=
/html/draft-jones-jose-aes-gcm-key-wrap-00</a> seems like a substantially s=
impler approach than
<a href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">ht=
tp://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; This =
is evident by several metrics:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Number of prop=
osed changes:&nbsp; The Jones draft proposes no changes to any of the curre=
nt specs.&nbsp; It simply defines an encoding for GCM and adds registry ent=
ries for it.&nbsp; Whereas the Barnes draft proposes
 a major restructuring &#8211; listing 4 major changes in the introduction =
and 4 smaller changes.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-family:Symbol;color:#1F497=
D"><span style=3D"mso-list:Ignore">&middot;<span style=3D"font:7.0pt &quot;=
Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Normative text=
 size:&nbsp; The Jones GCM key wrap approach requires only 7 normative sent=
ences in 1/2 page of text.&nbsp; The Barnes draft has four pages of normati=
ve text, along with an extensive introduction
 describing the proposed complete restructuring of JWS and JWE.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We don&#8217;t need to=
 boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; It=
 can already easily be done with the current specs simply by defining new a=
lgorithms.&nbsp; The approach taken in
<a href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00"=
>http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> would =
work for any AEAD algorithm.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a href=
=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Tuesday, June 25, 2013 9:53 AM<br>
<b>To:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> [jose] Issue #13 - use AES-GCM for Key Wrapping<o:p></o:p><=
/span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We now have two documents &#8211; one from Richard a=
nd one from Mike &#8211; which provide the two different ways that have bee=
n proposed for doing key wrapping with an AEAD algorithm.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please review the two documents and provide comments=
 to the list.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B16804296739436789D481TK5EX14MBXC283r_--

From breno@google.com  Wed Jun 26 21:21:56 2013
Return-Path: <breno@google.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 195F221F9133 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B77vqTwA84BZ for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:21:54 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E3BC021F859A for <jose@ietf.org>; Wed, 26 Jun 2013 21:21:47 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id m46so169144wev.16 for <jose@ietf.org>; Wed, 26 Jun 2013 21:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vlDPrQXOM0CAm0gVsV3Cn2G0Rln57/HSKp9mtDxj6EE=; b=VKbKOhiHxs6XuE2C3bQo5GtAByWFbf+DFyCuaITytFlEQTLXIPhpoJ9RPUmMVKHBZC res5rhAw9ryeqaRzg9DEEnKJ2OlIgAuOy1MbZFrz+aa3o1zn+KeoBlWstiCsCjg8kf/I ESI9eKuH1yljXPQSpYsuibQGVxtMkiRQTxZOFkuYxmojlUfQFqGWmvWez/trSj4pf5LX anPnm8P70B8qzPagV9guevPobqAq8Q60PpQYEeU+4FgqeaYBCeqG68U0ee/Vwf11+9M9 vGoahBxAunRidsk0ZX9desqPJDN5ZAV5t8a2yaop9PnaUiyptcH96RrB8YA3gMIYHJs2 RKBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=vlDPrQXOM0CAm0gVsV3Cn2G0Rln57/HSKp9mtDxj6EE=; b=CMKdFShXobTbqegZvnY2YsnLVgFmVSocvB47hQXOABTmJ/RyT1cPojIi5zY7wILjbZ klAVfjPee2UZ7dsND5q/mXt70qk4VFkOHm4oiBraLUIqueczk5FLWZbOrdVZ21saXfcj buo73fwZioZO7mRfJK0PE3ygeBZE8Ge1T60awiVXceMdWFA8qWDZe4hjeK/ESUcEaVM6 fsv8hsWQh7PIqMTR2WyJq5qbih3bSnehHx6yXpWXjvp/pV+5FcVHwX3UR32fxZRtJUzW PdeiYodARKK/ku6JGmKQuBHLT83t31mnYrp6OaANwXRtq2t5aGqCXuIeb3sCDk0PTuxb Z9ag==
MIME-Version: 1.0
X-Received: by 10.180.188.97 with SMTP id fz1mr4638132wic.34.1372306906985; Wed, 26 Jun 2013 21:21:46 -0700 (PDT)
Received: by 10.194.151.72 with HTTP; Wed, 26 Jun 2013 21:21:46 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789D481@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <034101ce729b$27473b00$75d5b100$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b901ce72e5$01248190$036d84b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D481@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 21:21:46 -0700
Message-ID: <CAAJ++qGUTLrqT9JmDDw0LJUusYzqorKCH6EpzriLnOeBTs7EuA@mail.gmail.com>
From: Breno de Medeiros <breno@google.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkqYAMxb1+G0kZshncXQ2lh8ju0M7VT+iPXMDgW80alQInivE34/Ht8LYoT5xAJnVdcqQRorA++10c2J3jU7Q1J/ZGaichd7W5KIICWdon0tN3OVkQgyBaSfnohFGi7FarKQyQ2iKo50jZut+zqKuNPNdIE9pgYebOYiytW5DGJlGze1Dcknzx2CSCcxCLuc0IV/sjb
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 04:21:56 -0000

I also don't believe that supporting the matrix of possible
algorithmic combinations satisfies any business need.

On Wed, Jun 26, 2013 at 9:01 PM, Mike Jones <Michael.Jones@microsoft.com> w=
rote:
> For my part, I consider the fact that people will need to register specif=
ic
> algorithm combinations that they actually need to be a feature =96 not a =
bug.
> The smaller the set of algorithm combinations registered, the more likely
> that they will be implemented and will interoperate.  Trying to claim tha=
t
> we support the combinatorial explosion of mask generation functions, hash
> functions, key derivation functions, key wrapping functions, etc. that ar=
e
> possible will almost certainly result in less interoperability and more
> developer confusion than a small set of registered choices, carefully
> considered.  I=92m glad to have people consider these criteria in their
> evaluation of the two choices.
>
>
>
>
> -- Mike
>
>
>
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Wednesday, June 26, 2013 8:18 PM
> To: Mike Jones; jose@ietf.org
>
>
> Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>
>
> My point was that there were some issues that your draft did not fully
> address that need to be evaluated as part of your proposal not that these
> algorithms would need to be added.  The n x m addition of algorithms to t=
he
> registry is an issue that is there for your draft that is not present for
> Richard=92s draft and therefore needs to be considered in the arguments.
>
>
>
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Wednesday, June 26, 2013 12:22 PM
> To: Jim Schaad; jose@ietf.org
> Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>
>
> Yes, we could also propose algorithm combinations for key agreement follo=
wed
> GCM key wrapping but I didn=92t think that was an ask from the working gr=
oup.
> The Denver minutes just recorded my action item as =93key wrap draft for
> AES-GCM-keywrap=94, so that=92s what I did.  We could have a discussion o=
n
> Monday=92s call and on the list about whether the working group is also
> interested in other algorithms.
>
>
>
> Remember, the beauty of having the algorithms registry is that algorithms
> can be added =93just in time=94 =96 as actual need for them is demonstrat=
ed.  We
> don=92t have to register all conceivable algorithm combinations up front =
for
> the JWE/JWA specs to be complete.
>
>
>
> As for how the AEAD parameters are handled I used a parameter encoding th=
at
> doesn=92t result in double base64url encoding anything.  I could have ins=
tead
> introduced separate =93iv=94 and =93tag=94 header parameter values, but d=
idn=92t do so
> for that reason.  But if people would prefer that approach because it=92s=
 more
> parallel to the use of GCM for plaintext encryption, I have no problem wi=
th
> that.
>
>
>
> I do believe that the objective of my draft was met =96 demonstrating tha=
t
> AEAD key wrapping can be easily done with the current drafts.  The detail=
s
> of how the algorithm parameters are encoded is secondary to that and
> algorithm-specific; several reasonable choices are possible within the
> current JWE framework =96 one of which was described in my draft.
>
>
>
>                                                                 -- Mike
>
>
>
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of J=
im
> Schaad
> Sent: Wednesday, June 26, 2013 11:30 AM
> To: Mike Jones; jose@ietf.org
> Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>
>
> <no hat>
>
> <sarcasm level=3D=94heavy=94>
>
>
>
> I am shocked that you would possibly support this proposal.  It provides =
for
> two ways of dealing with something.  It is my understanding that you neve=
r
> support anything that has two ways of doing something.
>
>
>
> How the AEAD algorithm parameters is handled completely differently for t=
his
> proposal and for the same algorithms being used in a CEK context.  This i=
s
> going to lead to confusion.
>
>
>
> </sarcasm>
>
>
>
> Your specification is missing some items that still need to be registered
> Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW define=
d
> in your document as well.
>
>
>
> Your document ends up with a registration complexity that needs to be
> thought about and dealt with as well.  For every new key wrap algorithm
> added, you will need to register not only it alone but also it with every
> different key agreement algorithm that is supported.  Thus adding a singl=
e
> key wrap algorithm becomes a slight issue in terms of adding in all of th=
e
> different ways that it might be used.  This is a complexity issue that is
> not discussed in the current draft.
>
>
>
> I have not necessarily found that document size equals code size.  I have
> implemented some very simple documents that were very difficult to code a=
nd
> implemented some very long documents that were very easy to code.  So I
> would not use that fact as a deciding factor.
>
>
>
> (Once again I regret the fact that the group did not go with an object
> descriptor for algorithms as this would have made all of this much simple=
r.
> I actually immediately map from the string to an object description in my
> JOSE implementation for simplicity reasons.  Not to mention that this is =
way
> it needs to be done for the WebCrypto specficiation.)
>
>
>
> Jim
>
>
>
>
>
>
>
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Tuesday, June 25, 2013 4:18 PM
> To: 'Jim Schaad'; jose@ietf.org
> Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>
>
> http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems lik=
e a
> substantially simpler approach than
> http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01.  This is
> evident by several metrics:
>
> =B7        Number of proposed changes:  The Jones draft proposes no chang=
es to
> any of the current specs.  It simply defines an encoding for GCM and adds
> registry entries for it.  Whereas the Barnes draft proposes a major
> restructuring =96 listing 4 major changes in the introduction and 4 small=
er
> changes.
>
> =B7        Normative text size:  The Jones GCM key wrap approach requires=
 only
> 7 normative sentences in 1/2 page of text.  The Barnes draft has four pag=
es
> of normative text, along with an extensive introduction describing the
> proposed complete restructuring of JWS and JWE.
>
>
>
> We don=92t need to boil the ocean with a total redesign to enable AEAD ke=
y
> wrapping.  It can already easily be done with the current specs simply by
> defining new algorithms.  The approach taken in
> http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would wor=
k
> for any AEAD algorithm.
>
>
>
>                                                                 -- Mike
>
>
>
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of J=
im
> Schaad
> Sent: Tuesday, June 25, 2013 9:53 AM
> To: jose@ietf.org
> Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>
>
> We now have two documents =96 one from Richard and one from Mike =96 whic=
h
> provide the two different ways that have been proposed for doing key
> wrapping with an AEAD algorithm.
>
>
>
> Please review the two documents and provide comments to the list.
>
>
>
> Jim
>
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>



--=20
--Breno

From Michael.Jones@microsoft.com  Wed Jun 26 21:52:36 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE6C21F9A86 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level: 
X-Spam-Status: No, score=-3.161 tagged_above=-999 required=5 tests=[AWL=0.438,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oo8iRIrWsHuy for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 21:52:31 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id B191B21F9A7E for <jose@ietf.org>; Wed, 26 Jun 2013 21:52:30 -0700 (PDT)
Received: from BL2FFO11FD025.protection.gbl (10.173.161.201) by BL2FFO11HUB045.protection.gbl (10.173.161.121) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 04:07:16 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD025.mail.protection.outlook.com (10.173.161.104) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 04:07:16 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 04:07:15 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkIAAhRqAgAAMGPA=
Date: Thu, 27 Jun 2013 04:07:15 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com>
In-Reply-To: <03b401ce72e5$002c65f0$008531d0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(189002)(199002)(13464003)(51704005)(69226001)(74706001)(74662001)(76796001)(74876001)(31966008)(74502001)(16406001)(81542001)(81342001)(46102001)(47446002)(50466002)(77096001)(74366001)(76786001)(56816003)(44976004)(79102001)(51856001)(59766001)(77982001)(56776001)(54356001)(54316002)(55846006)(53806001)(76482001)(47736001)(47976001)(50986001)(33656001)(49866001)(23676002)(4396001)(20776003)(47776003)(63696002)(6806003)(66066001)(65816001)(80022001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB045; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 04:52:36 -0000

VGhlIGFsdGVybmF0aXZlIGlzIHRvIHNheSB0aGF0IHByb2R1Y2VycyBNVVNUIE5PVCBwcm9kdWNl
IEpTT04gd2l0aCBkdXBsaWNhdGUgbWVtYmVyIG5hbWVzIGFuZCB0aGF0IGNvbnN1bWVycyBhcmUg
c3Ryb25nbHkgUkVDT01NRU5ERUQgdG8gcmVqZWN0IGlucHV0IHdpdGggZHVwbGljYXRlIG1lbWJl
ciBuYW1lcyBhbmQgbGVhdmUgaXQgYXQgdGhhdC4NCg0KSSB1bmRlcnN0YW5kIG5vdCB3YW50aW5n
IHRvIHJlcXVpcmUgY3VzdG9tZXIgcGFyc2VycyBpZiB0aGUgdW5kZXJseWluZyBwbGF0Zm9ybSBw
YXJzZXJzIGFyZSBkZWZpY2llbnQuICBCdXQgSSByZWFsbHkgaG9wZSB0aGF0IHRoZSBKU09OIFdH
IHdpbGwgaGF2ZSBtb3JlIHNlbnNlIHRoYW4gdG8gYWxsb3cgdGhlIGN1cnJlbnQgbWFkbmVzcyB0
byBjb250aW51ZS4gIEFzIEkgdW5kZXJzdG9vZCBpdCwgdGhlIHByaW1hcnkgbW90aXZhdGlvbiBm
b3IgdGhlIEpTT04gV0cgaW4gdGhlIGZpcnN0IHBsYWNlIHdhcyB0byBjaGFuZ2UgdGhlIFNIT1VM
RCB0byBhIE1VU1QuICBJZiB0aGV5IGRvbid0IGRvIHRoYXQsIEknbSByZWFsbHkgbm90IHN1cmUg
d2hhdCB0aGUgcG9pbnQgb2YgaXQgaXMuDQoNCgkJCQktLSBNaWtlDQoNClAuUy4gIEkgYW0gYSBz
dWJzY3JpYmVyIHRvIHRoZSBKU09OIG1haWxpbmcgbGlzdCwgYnV0IHVuZm9ydHVuYXRlbHksIHRo
ZSB2b2x1bWUgZ290IHNvIGhpZ2ggYSBmZXcgd2Vla3MgYWdvIHRoYXQgdHJ5aW5nIHRvIGtlZXAg
dXAgd2l0aCBpdCBiZWNhbWUgYW4gaW1wZWRpbWVudCB0byBnZXR0aW5nIHJlYWwgd29yayBkb25l
LiAgQXQgdGhhdCBwb2ludCBJIGNyZWF0ZWQgYSBydWxlIHRvIGZpbGUgdGhvc2UgbWVzc2FnZXMg
aW50byBhIGZvbGRlciwgd2hpY2ggSSBvbmx5IHJhcmVseSBsb29rIGF0LiAgSGFzIHRoYXQgc2l0
dWF0aW9uIGltcHJvdmVkPw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSmlt
IFNjaGFhZCBbbWFpbHRvOmlldGZAYXVndXN0Y2VsbGFycy5jb21dIA0KU2VudDogV2VkbmVzZGF5
LCBKdW5lIDI2LCAyMDEzIDg6MTggUE0NClRvOiBNaWtlIEpvbmVzOyBkcmFmdC1pZXRmLWpvc2Ut
anNvbi13ZWItc2lnbmF0dXJlQHRvb2xzLmlldGYub3JnDQpDYzogam9zZUBpZXRmLm9yZw0KU3Vi
amVjdDogUkU6IFtqb3NlXSAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVkcyBh
ZGRpdGlvbmFsIHRleHQNCg0KSSB3b3VsZCBzdHJvbmdseSBlbmNvdXJhZ2UgZXZlcnlvbmUgaW4g
dGhlIEpPU0UgbGlzdCB0byBqb2luIHRoZSBKU09OIGxpc3QgYW5kIHJlYWQgd2hhdCB3YXMgaXMg
dGhlcmUgYW5kIHBhcnRpY2lwYXRlLg0KDQpUaGF0IGJlaW5nIHNhaWQgdGhlcmUgYXJlIHNpdHVh
dGlvbnMgd2hlcmUgeW91IG1pZ2h0IG5vdCBiZSBhYmxlIHRvIGRvIGFuIGluZGVwZW5kZW50IHBh
cnNlci4gIEFuZCBpbiBmYWN0IHdoYXQgeW91IGhhdmUgc3RhdGVkIGlzIHRoYXQgdGhlcmUgaXMg
bm93IGEgcmVxdWlyZW1lbnQgdGhhdCBhIEpPU0UgbGlicmFyeSBzdXBwbHkgYSBKU09OIHBhcnNl
ci4gIElzIHRoYXQgcmVhbGx5IHdoYXQgd2Ugd2FudCB0byBzYXk/ICBIb3cgZmFyIGZyb20gY3Jl
YXRpbmcgYSBzZXQgb2YgZ2VuZXJhdG9yIGFuZCBwYXJzZXIgcmVxdWlyZW1lbnRzIHRoYXQgYXJl
IG5vbiBzdGFuZGFyZCBhbmQgcmVxdWlyaW5nIGEgcGFyc2VyL2dlbmVyYXRvciBhcmUgd2UgZnJv
bSB0aGF0Pw0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE1pa2UgSm9u
ZXMgW21haWx0bzpNaWNoYWVsLkpvbmVzQG1pY3Jvc29mdC5jb21dDQo+IFNlbnQ6IFdlZG5lc2Rh
eSwgSnVuZSAyNiwgMjAxMyAxMjozMCBQTQ0KPiBUbzogSmltIFNjaGFhZDsgZHJhZnQtaWV0Zi1q
b3NlLWpzb24td2ViLXNpZ25hdHVyZUB0b29scy5pZXRmLm9yZw0KPiBDYzogam9zZUBpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBSRTogW2pvc2VdICMyNzogbWVtYmVyIG5hbWVzIE1VU1QgYmUgdW5pcXVl
IG5lZWRzIGFkZGl0aW9uYWwgDQo+IHRleHQNCj4gDQo+IFRoZSBvcGVyYWJsZSBzZW50ZW5jZSBp
biBteSBzdWdnZXN0ZWQgdGV4dCBiZWxvdyBpcyB0aGlzIG9uZTogIklmIHRoZSANCj4gcGxhdGZv
cm0ncyBKU09OIHBhcnNlciBkb2VzIG5vdCByZWplY3QgaW5wdXQgd2l0aCBkdXBsaWNhdGUgbWVt
YmVyIA0KPiBuYW1lcywgdGhlIGlucHV0IHdpbGwgZmlyc3QgbmVlZCB0byBiZSBzZXBhcmF0ZWx5
IHBhcnNlZCB0byByZWplY3QgDQo+IHRoZXNlIGludmFsaWQgaW5wdXRzIGJlZm9yZSB1c2luZyB0
aGUgcGxhdGZvcm0ncyBwYXJzZXIiLiAgSW4gb3RoZXIgDQo+IHdvcmRzLCBpZiB0aGUgSlNPTiBw
YXJzZXIgaW4gdGhlIGRldmVsb3BtZW50IHBsYXRmb3JtIHlvdSBhcmUgdXNpbmcgDQo+IGRvZXMg
bm90IHJlamVjdCBpbnB1dHMgd2l0aCBkdXBsaWNhdGUgbWVtYmVyIG5hbWVzLCB5b3Ugd2lsbCBu
ZWVkIHRvIA0KPiB3cml0ZSBhIHNlcGFyYXRlIEpTT04gcGFyc2VyIHRoYXQgZGV0ZWN0cyB0aGlz
IGludmFsaWQgaW5wdXQgYW5kIHJlamVjdHMgaXQuDQo+IA0KPiBUaGlzIHBhcnNlciBjb3VsZCBl
aXRoZXIganVzdCBiZSBhIHZhbGlkYXRvciwgcmV0dXJuaW5nIFRSVUUgb3IgRkFMU0UgDQo+IGZv
ciB3aGV0aGVyIHRoZSBKU09OIGlzIHZhbGlkIGZvciBKT1NFIC0gaW4gd2hpY2ggY2FzZSB5b3Un
ZCB0aGVuIHBhc3MgDQo+IGFueSBpbnB1dHMgdmFsaWRhdGluZyBhcyBUUlVFIHRvIHRoZSBwbGF0
Zm9ybSdzIEpTT04gcGFyc2VyLCBvciBpdCANCj4gY291bGQgYmUgYSByZXBsYWNlbWVudCBwYXJz
ZXIsIGluIHdoaWNoIGNhc2UgeW91ciBjb2RlIHdvdWxkIG5vdCB1c2UgDQo+IHRoZSBkZXZlbG9w
bWVudCBwbGF0Zm9ybSdzIEpTT04gcGFyc2VyIGF0IGFsbC4gIEkgc3VzcGVjdCBwZW9wbGUgd291
bGQgDQo+IGJlIG1vcmUgbGlrZWx5IHRvIGRvIHRoZSBmb3JtZXIgdGhhbiB0aGUgbGF0dGVyLCBi
dXQgYm90aCBhcHByb2FjaGVzIGFyZSBlcXVpdmFsZW50Lg0KPiANCj4gQlRXLCBpZiBpdCdzIHlv
dXIgc2Vuc2UgdGhhdCB0aGVyZSdzIGEgcHJvYmxlbSBvY2N1cnJpbmcgaW4gdGhlIEpTT04gDQo+
IHdvcmtpbmcgZ3JvdXAgd2l0aCByZXNwZWN0IHRvIGVuYWJsaW5nIHN0cmljdCBKU09OIHBhcnNp
bmcsIHdlIA0KPiBwcm9iYWJseSBuZWVkIHRvIGJlY29tZSBhY3RpdmUgdGhlcmUuICBGb3IgaW5z
dGFuY2UsIGV2ZW4gaWYgdGhlIHNwZWMgDQo+IGFsbG93cyBkdXBsaWNhdGUgbWVtYmVyIG5hbWVz
IGxpa2UgdGhlIEVDTUEgc3BlYyBkb2VzLCB0aGUgUkZDIGNvdWxkIA0KPiByZWNvbW1lbmQgb3Ig
cmVxdWlyZSB0aGF0IHBhcnNlcnMgc3VwcG9ydCBhICJzdHJpY3QiIG1vZGUsIHdoaWNoIHJlamVj
dHMgdGhlc2UgdW5uZWNlc3NhcmlseSBsYXggaW5wdXRzLg0KPiBUaGVuIEpPU0UgaW1wbGVtZW50
YXRpb25zIGNvdWxkIHVzZSB0aGF0Lg0KPiANCj4gCQkJCS0tIE1pa2UNCj4gDQo+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEppbSBTY2hhYWQgW21haWx0bzppZXRmQGF1Z3Vz
dGNlbGxhcnMuY29tXQ0KPiBTZW50OiBXZWRuZXNkYXksIEp1bmUgMjYsIDIwMTMgMTE6MzAgQU0N
Cj4gVG86ICdqb3NlIGlzc3VlIHRyYWNrZXInOyANCj4gZHJhZnQtaWV0Zi1qb3NlLWpzb24td2Vi
LXNpZ25hdHVyZUB0b29scy5pZXRmLm9yZzsNCj4gTWlrZSBKb25lcw0KPiBDYzogam9zZUBpZXRm
Lm9yZw0KPiBTdWJqZWN0OiBSRTogW2pvc2VdICMyNzogbWVtYmVyIG5hbWVzIE1VU1QgYmUgdW5p
cXVlIG5lZWRzIGFkZGl0aW9uYWwgDQo+IHRleHQNCj4gDQo+IDxubyBoYXQ+DQo+IA0KPiBJIGNv
bnNpZGVyIG15c2VsZiB0byBiZSByZWFzb25hYmx5IGNvbXBldGVudCBpbiBib3RoIEVuZ2xpc2gg
YW5kIA0KPiBUZWNobmljYWwgRW5nbGlzaC4gIEkgaGF2ZSBubyBpZGVhIHdoYXQgSSBhbSBzdXBw
b3NlZCB0byBiZSBkb2luZyB0byANCj4gZGVhbCB3aXRoIHRoZSB0ZXh0IGJlbG93LiAgRG9lcyB0
aGlzIG1lYW4gdGhhdCBJIG5lZWQgdG8gd3JpdGUgYW4gDQo+IGluZGVwZW5kZW50IHBhcnNlcj8g
IFdoYXQgYWJvdXQgY2FzZXMgd2hlcmUgaXQgaXMgY29taW5nIGluIG9uIGEgDQo+IHN0cmVhbSBh
bmQgSSBkb24ndCBnZXQgdG8gc2VlIHRoZSBkYXRhIGJlZm9yZSB0aGUgcGFyc2Ugb2NjdXJzPyAg
SG93IA0KPiBhcmUgdGhleSBpbnRlcnByZXRlZCBkaWZmZXJlbnRseT8gIFdoYXQgZXhhY3RseSBp
cyB0aGlzIHN1cHBvc2VkIHRvIGJlIA0KPiBhZGRyZXNzaW5nLiAgTXVjaCBvZiB0aGlzIGNvdWxk
IGJlIHNraXBwZWQgd2hlbiB3ZSBzYWlkIGRvbid0IGRvIGl0LiAgDQo+IFNpbmNlIHRoaXMgaXMg
bm8gbG9uZ2VyIGEgdmlhYmxlIHN0YXRlbWVudCBkdWUgdG8gdGhlIHN0YXRlIG9mIHBhcnNlcnMs
IHdlIG5lZWQgdG8gYmUgbW9yZSBleHBsaWNpdCBhbmQgc2F5IHdoYXQgaXMgZ29pbmcgb24uDQo+
IA0KPiBObyBJIGRvbid0IGNvbnNpZGVyIHRoZSBzdWdnZXN0ZWQgdGV4dCB0byBiZSBhZGVxdWF0
ZS4NCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBqb3NlLWJv
dW5jZXNAaWV0Zi5vcmcgW21haWx0bzpqb3NlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiAN
Cj4gPiBPZiBqb3NlIGlzc3VlIHRyYWNrZXINCj4gPiBTZW50OiBUdWVzZGF5LCBKdW5lIDI1LCAy
MDEzIDU6NDEgUE0NCj4gPiBUbzogZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLXNpZ25hdHVyZUB0
b29scy5pZXRmLm9yZzsNCj4gPiBtaWNoYWVsLmpvbmVzQG1pY3Jvc29mdC5jb20NCj4gPiBDYzog
am9zZUBpZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFJlOiBbam9zZV0gIzI3OiBtZW1iZXIgbmFtZXMg
TVVTVCBiZSB1bmlxdWUgbmVlZHMgDQo+ID4gYWRkaXRpb25hbCB0ZXh0DQo+ID4NCj4gPiAjMjc6
IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVkcyBhZGRpdGlvbmFsIHRleHQNCj4gPg0K
PiA+DQo+ID4gQ29tbWVudCAoYnkgbWljaGFlbC5qb25lc0BtaWNyb3NvZnQuY29tKToNCj4gPg0K
PiA+ICBUaGUgSldTIGRyYWZ0IGN1cnJlbnRseSBzYXlzOg0KPiA+DQo+ID4gICAgICAgICAgVGhl
IEhlYWRlciBQYXJhbWV0ZXIgTmFtZXMgd2l0aGluIHRoZSBKV1MgSGVhZGVyIE1VU1QgYmUgdW5p
cXVlOw0KPiA+ICAgICAgICAgIEpXU3Mgd2l0aCBkdXBsaWNhdGUgSGVhZGVyIFBhcmFtZXRlciBO
YW1lcyBNVVNUIGJlIHJlamVjdGVkLg0KPiA+DQo+ID4gIEhvdyBhYm91dCBjaGFuZ2luZyB0aGlz
IHRvOg0KPiA+DQo+ID4gICAgICAgICAgVGhlIEhlYWRlciBQYXJhbWV0ZXIgTmFtZXMgd2l0aGlu
IHRoZSBKV1MgSGVhZGVyIE1VU1QgYmUgdW5pcXVlOw0KPiA+ICAgICAgICAgIEpXU3Mgd2l0aCBk
dXBsaWNhdGUgSGVhZGVyIFBhcmFtZXRlciBOYW1lcyBNVVNUIGJlIHJlamVjdGVkLg0KPiA+ICAg
ICAgICAgIFRoaXMgaXMgbmVjZXNzYXJ5IHRvIHByZXZlbnQgYXR0YWNrcyBpbiB3aGljaCB0aGUg
c2FtZSBKV1MgDQo+ID4gbWlnaHQgIGJlIGludGVycHJldGVkDQo+ID4gICAgICAgICAgaW4gZGlm
ZmVyZW50IHdheXMgYnkgZGlmZmVyZW50IGltcGxlbWVudGF0aW9ucyBhbmQgdG8gDQo+ID4gcHJl
dmVudA0KPiBhdHRhY2tlcnMNCj4gPiAgICAgICAgICBmcm9tIGhpZGluZyBleHRyYSBjb250ZW50
IGluIGR1cGxpY2F0ZSBtZW1iZXIgdmFsdWVzLg0KPiA+ICAgICAgICAgIElmIHRoZSBwbGF0Zm9y
bSBzIEpTT04gcGFyc2VyIGRvZXMgbm90IHJlamVjdCBpbnB1dCB3aXRoIA0KPiA+IGR1cGxpY2F0
ZSBtZW1iZXIgbmFtZXMsDQo+ID4gICAgICAgICAgdGhlIGlucHV0IHdpbGwgZmlyc3QgbmVlZCB0
byBiZSBzZXBhcmF0ZWx5IHBhcnNlZCB0byByZWplY3QgDQo+ID4gdGhlc2UgIGludmFsaWQgaW5w
dXRzDQo+ID4gICAgICAgICAgYmVmb3JlIHVzaW5nIHRoZSBwbGF0Zm9ybSBzIHBhcnNlci4NCj4g
Pg0KPiA+IC0tDQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
Ky0tDQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLQ0KPiA+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0rLS0tDQo+ID4gIFJlcG9ydGVyOiAgICAgICAgICAgICAgIHwgICAgICAgT3du
ZXI6ICBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItDQo+ID4gICBpZXRmQGF1Z3VzdGNlbGxhcnMu
Y29tIHwgIHNpZ25hdHVyZUB0b29scy5pZXRmLm9yZw0KPiA+ICAgICAgVHlwZTogIGRlZmVjdCAg
ICAgICB8ICAgICAgU3RhdHVzOiAgbmV3DQo+ID4gIFByaW9yaXR5OiAgbWFqb3IgICAgICAgIHwg
ICBNaWxlc3RvbmU6DQo+ID4gQ29tcG9uZW50OiAganNvbi13ZWItICAgIHwgICAgIFZlcnNpb246
DQo+ID4gICBzaWduYXR1cmUgICAgICAgICAgICAgIHwgIFJlc29sdXRpb246DQo+ID4gIFNldmVy
aXR5OiAgLSAgICAgICAgICAgIHwNCj4gPiAgS2V5d29yZHM6ICAgICAgICAgICAgICAgfA0KPiA+
IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLQ0KPiA+IC0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0NCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0t
LQ0KPiA+DQo+ID4gVGlja2V0IFVSTDoNCj4gPiA8aHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcv
d2cvam9zZS90cmFjL3RpY2tldC8yNyNjb21tZW50OjE+DQo+ID4gam9zZSA8aHR0cDovL3Rvb2xz
LmlldGYub3JnL2pvc2UvPg0KPiA+DQo+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gPiBqb3NlIG1haWxpbmcgbGlzdA0KPiA+IGpvc2VAaWV0Zi5v
cmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2pvc2UNCg0KDQo=

From tbray@textuality.com  Wed Jun 26 22:23:51 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873F821F9B0E for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyqoJcXsNBZg for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:23:46 -0700 (PDT)
Received: from mail-vb0-f42.google.com (mail-vb0-f42.google.com [209.85.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id 4459621F9BF2 for <jose@ietf.org>; Wed, 26 Jun 2013 22:23:46 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id i3so257328vbh.15 for <jose@ietf.org>; Wed, 26 Jun 2013 22:23:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=OcTG+YKucbchd8Uh+rTW1kXKyCmGjUGOt/X8HaCJmDc=; b=KFQbEyuN3gTzIHho6iBukudNLWwhw+2Fm9uDODgxAXVsRKzm0/XuT0m2iCHwLMPunw nf2nLf+2jj+G4r05PfBcMR3c7g708N352Fub+RVFh8ZjqSGAeoJQtI0xPoBKS4SQ6OCe tkuVNxjWnsqtmcx7PJ0LKpH3W2w2OLJf5jzHqH6WFrLEYdarewiOM5iwWKIz7UUDlCks En4IUB+mJSRnnbllTUz4pwuk5C0S22s25cAJhFAB4DruipHg4nLevcEfxLQaWbJlrAxe p8oniz+dOAlmb0cryya7HuPemoY82SitK9M8K6GVn8eQpegQO5rh4t2bGKqsAzigzl60 LkIA==
MIME-Version: 1.0
X-Received: by 10.220.91.75 with SMTP id l11mr2883278vcm.82.1372310625624; Wed, 26 Jun 2013 22:23:45 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Wed, 26 Jun 2013 22:23:45 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Wed, 26 Jun 2013 22:23:45 -0700
Message-ID: <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=047d7b3440885cb06704e01bf78b
X-Gm-Message-State: ALoCoQkY74U5Omt3FKGCxJwVPiGMNGxuFVxJd64bYeXNBQ2O/hDGulJieQ5PncUMOWi0zGM3ndQ7
Cc: Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 05:23:51 -0000

--047d7b3440885cb06704e01bf78b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think it=E2=80=99s a nice clean minimal solution to say that producers MU=
ST NOT
generate dupes, end of story.  I don=E2=80=99t think saying anything beyond=
 that
adds value. -T


On Wed, Jun 26, 2013 at 9:07 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

> The alternative is to say that producers MUST NOT produce JSON with
> duplicate member names and that consumers are strongly RECOMMENDED to
> reject input with duplicate member names and leave it at that.
>
> I understand not wanting to require customer parsers if the underlying
> platform parsers are deficient.  But I really hope that the JSON WG will
> have more sense than to allow the current madness to continue.  As I
> understood it, the primary motivation for the JSON WG in the first place
> was to change the SHOULD to a MUST.  If they don't do that, I'm really no=
t
> sure what the point of it is.
>
>                                 -- Mike
>
> P.S.  I am a subscriber to the JSON mailing list, but unfortunately, the
> volume got so high a few weeks ago that trying to keep up with it became =
an
> impediment to getting real work done.  At that point I created a rule to
> file those messages into a folder, which I only rarely look at.  Has that
> situation improved?
>
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Wednesday, June 26, 2013 8:18 PM
> To: Mike Jones; draft-ietf-jose-json-web-signature@tools.ietf.org
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional tex=
t
>
> I would strongly encourage everyone in the JOSE list to join the JSON lis=
t
> and read what was is there and participate.
>
> That being said there are situations where you might not be able to do an
> independent parser.  And in fact what you have stated is that there is no=
w
> a requirement that a JOSE library supply a JSON parser.  Is that really
> what we want to say?  How far from creating a set of generator and parser
> requirements that are non standard and requiring a parser/generator are w=
e
> from that?
>
> > -----Original Message-----
> > From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> > Sent: Wednesday, June 26, 2013 12:30 PM
> > To: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org
> > Cc: jose@ietf.org
> > Subject: RE: [jose] #27: member names MUST be unique needs additional
> > text
> >
> > The operable sentence in my suggested text below is this one: "If the
> > platform's JSON parser does not reject input with duplicate member
> > names, the input will first need to be separately parsed to reject
> > these invalid inputs before using the platform's parser".  In other
> > words, if the JSON parser in the development platform you are using
> > does not reject inputs with duplicate member names, you will need to
> > write a separate JSON parser that detects this invalid input and reject=
s
> it.
> >
> > This parser could either just be a validator, returning TRUE or FALSE
> > for whether the JSON is valid for JOSE - in which case you'd then pass
> > any inputs validating as TRUE to the platform's JSON parser, or it
> > could be a replacement parser, in which case your code would not use
> > the development platform's JSON parser at all.  I suspect people would
> > be more likely to do the former than the latter, but both approaches ar=
e
> equivalent.
> >
> > BTW, if it's your sense that there's a problem occurring in the JSON
> > working group with respect to enabling strict JSON parsing, we
> > probably need to become active there.  For instance, even if the spec
> > allows duplicate member names like the ECMA spec does, the RFC could
> > recommend or require that parsers support a "strict" mode, which reject=
s
> these unnecessarily lax inputs.
> > Then JOSE implementations could use that.
> >
> >                               -- Mike
> >
> > -----Original Message-----
> > From: Jim Schaad [mailto:ietf@augustcellars.com]
> > Sent: Wednesday, June 26, 2013 11:30 AM
> > To: 'jose issue tracker';
> > draft-ietf-jose-json-web-signature@tools.ietf.org;
> > Mike Jones
> > Cc: jose@ietf.org
> > Subject: RE: [jose] #27: member names MUST be unique needs additional
> > text
> >
> > <no hat>
> >
> > I consider myself to be reasonably competent in both English and
> > Technical English.  I have no idea what I am supposed to be doing to
> > deal with the text below.  Does this mean that I need to write an
> > independent parser?  What about cases where it is coming in on a
> > stream and I don't get to see the data before the parse occurs?  How
> > are they interpreted differently?  What exactly is this supposed to be
> > addressing.  Much of this could be skipped when we said don't do it.
> > Since this is no longer a viable statement due to the state of parsers,
> we need to be more explicit and say what is going on.
> >
> > No I don't consider the suggested text to be adequate.
> >
> > > -----Original Message-----
> > > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > > Of jose issue tracker
> > > Sent: Tuesday, June 25, 2013 5:41 PM
> > > To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > > michael.jones@microsoft.com
> > > Cc: jose@ietf.org
> > > Subject: Re: [jose] #27: member names MUST be unique needs
> > > additional text
> > >
> > > #27: member names MUST be unique needs additional text
> > >
> > >
> > > Comment (by michael.jones@microsoft.com):
> > >
> > >  The JWS draft currently says:
> > >
> > >          The Header Parameter Names within the JWS Header MUST be
> unique;
> > >          JWSs with duplicate Header Parameter Names MUST be rejected.
> > >
> > >  How about changing this to:
> > >
> > >          The Header Parameter Names within the JWS Header MUST be
> unique;
> > >          JWSs with duplicate Header Parameter Names MUST be rejected.
> > >          This is necessary to prevent attacks in which the same JWS
> > > might  be interpreted
> > >          in different ways by different implementations and to
> > > prevent
> > attackers
> > >          from hiding extra content in duplicate member values.
> > >          If the platform s JSON parser does not reject input with
> > > duplicate member names,
> > >          the input will first need to be separately parsed to reject
> > > these  invalid inputs
> > >          before using the platform s parser.
> > >
> > > --
> > > -------------------------+------------------------------------------
> > > -------------------------+--
> > > -------------------------+--
> > > -------------------------+---
> > >  Reporter:               |       Owner:  draft-ietf-jose-json-web-
> > >   ietf@augustcellars.com |  signature@tools.ietf.org
> > >      Type:  defect       |      Status:  new
> > >  Priority:  major        |   Milestone:
> > > Component:  json-web-    |     Version:
> > >   signature              |  Resolution:
> > >  Severity:  -            |
> > >  Keywords:               |
> > > -------------------------+------------------------------------------
> > > -------------------------+--
> > > -------------------------+--
> > > -------------------------+---
> > >
> > > Ticket URL:
> > > <http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
> > > jose <http://tools.ietf.org/jose/>
> > >
> > > _______________________________________________
> > > jose mailing list
> > > jose@ietf.org
> > > https://www.ietf.org/mailman/listinfo/jose
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--047d7b3440885cb06704e01bf78b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think it=E2=80=99s a nice clean minimal solution to say =
that producers MUST NOT generate dupes, end of story.=C2=A0 I don=E2=80=99t=
 think saying anything beyond that adds value. -T<br></div><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">
On Wed, Jun 26, 2013 at 9:07 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=
=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@mic=
rosoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The alternative is to say that producers MUST NOT produce JSON with duplica=
te member names and that consumers are strongly RECOMMENDED to reject input=
 with duplicate member names and leave it at that.<br>
<br>
I understand not wanting to require customer parsers if the underlying plat=
form parsers are deficient. =C2=A0But I really hope that the JSON WG will h=
ave more sense than to allow the current madness to continue. =C2=A0As I un=
derstood it, the primary motivation for the JSON WG in the first place was =
to change the SHOULD to a MUST. =C2=A0If they don&#39;t do that, I&#39;m re=
ally not sure what the point of it is.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -- Mike<br>
</font></span><br>
P.S. =C2=A0I am a subscriber to the JSON mailing list, but unfortunately, t=
he volume got so high a few weeks ago that trying to keep up with it became=
 an impediment to getting real work done. =C2=A0At that point I created a r=
ule to file those messages into a folder, which I only rarely look at. =C2=
=A0Has that situation improved?<br>

<div class=3D"im"><br>
-----Original Message-----<br>
From: Jim Schaad [mailto:<a href=3D"mailto:ietf@augustcellars.com">ietf@aug=
ustcellars.com</a>]<br>
</div><div><div class=3D"h5">Sent: Wednesday, June 26, 2013 8:18 PM<br>
To: Mike Jones; <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.=
ietf.org">draft-ietf-jose-json-web-signature@tools.ietf.org</a><br>
Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
Subject: RE: [jose] #27: member names MUST be unique needs additional text<=
br>
<br>
I would strongly encourage everyone in the JOSE list to join the JSON list =
and read what was is there and participate.<br>
<br>
That being said there are situations where you might not be able to do an i=
ndependent parser. =C2=A0And in fact what you have stated is that there is =
now a requirement that a JOSE library supply a JSON parser. =C2=A0Is that r=
eally what we want to say? =C2=A0How far from creating a set of generator a=
nd parser requirements that are non standard and requiring a parser/generat=
or are we from that?<br>

<br>
&gt; -----Original Message-----<br>
&gt; From: Mike Jones [mailto:<a href=3D"mailto:Michael.Jones@microsoft.com=
">Michael.Jones@microsoft.com</a>]<br>
&gt; Sent: Wednesday, June 26, 2013 12:30 PM<br>
&gt; To: Jim Schaad; <a href=3D"mailto:draft-ietf-jose-json-web-signature@t=
ools.ietf.org">draft-ietf-jose-json-web-signature@tools.ietf.org</a><br>
&gt; Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #27: member names MUST be unique needs additional<=
br>
&gt; text<br>
&gt;<br>
&gt; The operable sentence in my suggested text below is this one: &quot;If=
 the<br>
&gt; platform&#39;s JSON parser does not reject input with duplicate member=
<br>
&gt; names, the input will first need to be separately parsed to reject<br>
&gt; these invalid inputs before using the platform&#39;s parser&quot;. =C2=
=A0In other<br>
&gt; words, if the JSON parser in the development platform you are using<br=
>
&gt; does not reject inputs with duplicate member names, you will need to<b=
r>
&gt; write a separate JSON parser that detects this invalid input and rejec=
ts it.<br>
&gt;<br>
&gt; This parser could either just be a validator, returning TRUE or FALSE<=
br>
&gt; for whether the JSON is valid for JOSE - in which case you&#39;d then =
pass<br>
&gt; any inputs validating as TRUE to the platform&#39;s JSON parser, or it=
<br>
&gt; could be a replacement parser, in which case your code would not use<b=
r>
&gt; the development platform&#39;s JSON parser at all. =C2=A0I suspect peo=
ple would<br>
&gt; be more likely to do the former than the latter, but both approaches a=
re equivalent.<br>
&gt;<br>
&gt; BTW, if it&#39;s your sense that there&#39;s a problem occurring in th=
e JSON<br>
&gt; working group with respect to enabling strict JSON parsing, we<br>
&gt; probably need to become active there. =C2=A0For instance, even if the =
spec<br>
&gt; allows duplicate member names like the ECMA spec does, the RFC could<b=
r>
&gt; recommend or require that parsers support a &quot;strict&quot; mode, w=
hich rejects these unnecessarily lax inputs.<br>
&gt; Then JOSE implementations could use that.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -- Mike<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Jim Schaad [mailto:<a href=3D"mailto:ietf@augustcellars.com">iet=
f@augustcellars.com</a>]<br>
&gt; Sent: Wednesday, June 26, 2013 11:30 AM<br>
&gt; To: &#39;jose issue tracker&#39;;<br>
&gt; <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">d=
raft-ietf-jose-json-web-signature@tools.ietf.org</a>;<br>
&gt; Mike Jones<br>
&gt; Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #27: member names MUST be unique needs additional<=
br>
&gt; text<br>
&gt;<br>
&gt; &lt;no hat&gt;<br>
&gt;<br>
&gt; I consider myself to be reasonably competent in both English and<br>
&gt; Technical English. =C2=A0I have no idea what I am supposed to be doing=
 to<br>
&gt; deal with the text below. =C2=A0Does this mean that I need to write an=
<br>
&gt; independent parser? =C2=A0What about cases where it is coming in on a<=
br>
&gt; stream and I don&#39;t get to see the data before the parse occurs? =
=C2=A0How<br>
&gt; are they interpreted differently? =C2=A0What exactly is this supposed =
to be<br>
&gt; addressing. =C2=A0Much of this could be skipped when we said don&#39;t=
 do it.<br>
&gt; Since this is no longer a viable statement due to the state of parsers=
, we need to be more explicit and say what is going on.<br>
&gt;<br>
&gt; No I don&#39;t consider the suggested text to be adequate.<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.=
org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.=
org</a>] On Behalf<br>
&gt; &gt; Of jose issue tracker<br>
&gt; &gt; Sent: Tuesday, June 25, 2013 5:41 PM<br>
&gt; &gt; To: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ie=
tf.org">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;<br>
&gt; &gt; <a href=3D"mailto:michael.jones@microsoft.com">michael.jones@micr=
osoft.com</a><br>
&gt; &gt; Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; &gt; Subject: Re: [jose] #27: member names MUST be unique needs<br>
&gt; &gt; additional text<br>
&gt; &gt;<br>
&gt; &gt; #27: member names MUST be unique needs additional text<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Comment (by <a href=3D"mailto:michael.jones@microsoft.com">michae=
l.jones@microsoft.com</a>):<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0The JWS draft currently says:<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Header Parameter Names with=
in the JWS Header MUST be unique;<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0JWSs with duplicate Header Para=
meter Names MUST be rejected.<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0How about changing this to:<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Header Parameter Names with=
in the JWS Header MUST be unique;<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0JWSs with duplicate Header Para=
meter Names MUST be rejected.<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This is necessary to prevent at=
tacks in which the same JWS<br>
&gt; &gt; might =C2=A0be interpreted<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0in different ways by different =
implementations and to<br>
&gt; &gt; prevent<br>
&gt; attackers<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0from hiding extra content in du=
plicate member values.<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0If the platform s JSON parser d=
oes not reject input with<br>
&gt; &gt; duplicate member names,<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the input will first need to be=
 separately parsed to reject<br>
&gt; &gt; these =C2=A0invalid inputs<br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0before using the platform s par=
ser.<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; -------------------------+---------------------------------------=
---<br>
</div></div>&gt; &gt; -------------------------+--<br>
<div class=3D"im">&gt; &gt; -------------------------+--<br>
&gt; &gt; -------------------------+---<br>
&gt; &gt; =C2=A0Reporter: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
| =C2=A0 =C2=A0 =C2=A0 Owner: =C2=A0draft-ietf-jose-json-web-<br>
&gt; &gt; =C2=A0 <a href=3D"mailto:ietf@augustcellars.com">ietf@augustcella=
rs.com</a> | =C2=A0<a href=3D"mailto:signature@tools.ietf.org">signature@to=
ols.ietf.org</a><br>
&gt; &gt; =C2=A0 =C2=A0 =C2=A0Type: =C2=A0defect =C2=A0 =C2=A0 =C2=A0 | =C2=
=A0 =C2=A0 =C2=A0Status: =C2=A0new<br>
&gt; &gt; =C2=A0Priority: =C2=A0major =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 M=
ilestone:<br>
&gt; &gt; Component: =C2=A0json-web- =C2=A0 =C2=A0| =C2=A0 =C2=A0 Version:<=
br>
&gt; &gt; =C2=A0 signature =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
| =C2=A0Resolution:<br>
&gt; &gt; =C2=A0Severity: =C2=A0- =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
|<br>
&gt; &gt; =C2=A0Keywords: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
|<br>
&gt; &gt; -------------------------+---------------------------------------=
---<br>
</div>&gt; &gt; -------------------------+--<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt; &gt; -------------------------=
+--<br>
&gt; &gt; -------------------------+---<br>
&gt; &gt;<br>
&gt; &gt; Ticket URL:<br>
&gt; &gt; &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/27#=
comment:1" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket=
/27#comment:1</a>&gt;<br>
&gt; &gt; jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank=
">http://tools.ietf.org/jose/</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; jose mailing list<br>
&gt; &gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"=
_blank">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</div></div></blockquote></div><br></div>

--047d7b3440885cb06704e01bf78b--

From James.H.Manger@team.telstra.com  Wed Jun 26 22:26:22 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A13121F8FBE for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level: 
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6uHtn0BdsJS for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:26:17 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) by ietfa.amsl.com (Postfix) with ESMTP id 1B97521F9016 for <jose@ietf.org>; Wed, 26 Jun 2013 22:26:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,949,1363093200"; d="scan'208";a="143940480"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipocvi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 15:26:14 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7118"; a="141024484"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipccvi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 15:26:14 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Thu, 27 Jun 2013 15:26:13 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Mike Jones' <Michael.Jones@microsoft.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Date: Thu, 27 Jun 2013 15:26:12 +1000
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvAtXnsooCfmP1+5lS3btggAA1HjA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BE456D2@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com>
In-Reply-To: <03b401ce72e5$002c65f0$008531d0$@augustcellars.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 05:26:22 -0000

SlNPTiBwYXJzZXJzIHRoYXQgYWNjZXB0IGR1cGxpY2F0ZSBuYW1lcywgYnV0IGlnbm9yZSBhbGwg
YnV0IHRoZSBsYXN0LCBhcmUgdG9vIGNvbW1vbiB0byBiZWxpZXZlIEpPU0Ugd2lsbCBub3QgYmUg
aW1wbGVtZW50ZWQgdXNpbmcgdGhvc2UgcGFyc2Vycy4gU2VlICJbSnNvbl0gQ2FsbCBmb3IgcmVh
bC13b3JsZCBleGFtcGxlcyBvZiBob3cgcGFyc2VycyBkZWFsIHdpdGggZHVwbGljYXRlIGtleXMi
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9qc29uL2N1cnJlbnQvbXNnMDA0
NzEuaHRtbC4NCg0KSSBzdXNwZWN0IHRoZSBiZXN0IHdlIGNhbiBkbyBpcyBzYXk6DQoNCiAgQSBj
cmVhdG9yIG9mIGEgSk9TRSBtZXNzYWdlIE1VU1QgTk9UIHB1dCBkdXBsaWNhdGUgbmFtZXMgaW4g
YW55IEpTT04gb2JqZWN0IGluIGEgSk9TRSBoZWFkZXIuDQogIFRvIHByZXZlbnQgYXR0YWNrcyB3
aGVyZSBhIEpPU0UgbWVzc2FnZSBpcyBpbnRlcnByZXRlZCBhcyBkaWZmZXJlbnQgdmFsaWQgbWVz
c2FnZXMgYnkgZGlmZmVyZW50IHJlY2lwaWVudHMsIGVhY2ggcmVjaXBpZW50IE1VU1QgZWl0aGVy
IHJlamVjdCBtZXNzYWdlcyB3aXRoIGR1cGxpY2F0ZSBuYW1lcyBvciBhY2NlcHQgb25seSB0aGUg
bGFzdCBuYW1lLg0KDQpQbHVzIGFnaXRhdGUgaW4gdGhlIEpTT04gZ3JvdXAgdG8gYWRkIHJlbGF0
ZWQgdGV4dCB0byB0aGUgbmV4dCB2ZXJzaW9uIG9mIHRoZSBKU09OIHNwZWMuDQoNCg0KLS0NCkph
bWVzIE1hbmdlcg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogam9z
ZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86am9zZS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YNCj4gSmltIFNjaGFhZA0KPiBTZW50OiBUaHVyc2RheSwgMjcgSnVuZSAyMDEzIDE6MTgg
UE0NCj4gVG86ICdNaWtlIEpvbmVzJzsgZHJhZnQtaWV0Zi1qb3NlLWpzb24td2ViLXNpZ25hdHVy
ZUB0b29scy5pZXRmLm9yZw0KPiBDYzogam9zZUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW2pv
c2VdICMyNzogbWVtYmVyIG5hbWVzIE1VU1QgYmUgdW5pcXVlIG5lZWRzIGFkZGl0aW9uYWwNCj4g
dGV4dA0KPiANCj4gSSB3b3VsZCBzdHJvbmdseSBlbmNvdXJhZ2UgZXZlcnlvbmUgaW4gdGhlIEpP
U0UgbGlzdCB0byBqb2luIHRoZSBKU09ODQo+IGxpc3QgYW5kIHJlYWQgd2hhdCB3YXMgaXMgdGhl
cmUgYW5kIHBhcnRpY2lwYXRlLg0KPiANCj4gVGhhdCBiZWluZyBzYWlkIHRoZXJlIGFyZSBzaXR1
YXRpb25zIHdoZXJlIHlvdSBtaWdodCBub3QgYmUgYWJsZSB0byBkbw0KPiBhbiBpbmRlcGVuZGVu
dCBwYXJzZXIuICBBbmQgaW4gZmFjdCB3aGF0IHlvdSBoYXZlIHN0YXRlZCBpcyB0aGF0IHRoZXJl
DQo+IGlzIG5vdyBhIHJlcXVpcmVtZW50IHRoYXQgYSBKT1NFIGxpYnJhcnkgc3VwcGx5IGEgSlNP
TiBwYXJzZXIuICBJcyB0aGF0DQo+IHJlYWxseSB3aGF0IHdlIHdhbnQgdG8gc2F5PyAgSG93IGZh
ciBmcm9tIGNyZWF0aW5nIGEgc2V0IG9mIGdlbmVyYXRvcg0KPiBhbmQgcGFyc2VyIHJlcXVpcmVt
ZW50cyB0aGF0IGFyZSBub24gc3RhbmRhcmQgYW5kIHJlcXVpcmluZyBhDQo+IHBhcnNlci9nZW5l
cmF0b3IgYXJlIHdlIGZyb20gdGhhdD8NCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gPiBGcm9tOiBNaWtlIEpvbmVzIFttYWlsdG86TWljaGFlbC5Kb25lc0BtaWNyb3NvZnQu
Y29tXQ0KPiA+IFNlbnQ6IFdlZG5lc2RheSwgSnVuZSAyNiwgMjAxMyAxMjozMCBQTQ0KPiA+IFRv
OiBKaW0gU2NoYWFkOyBkcmFmdC1pZXRmLWpvc2UtanNvbi13ZWItc2lnbmF0dXJlQHRvb2xzLmll
dGYub3JnDQo+ID4gQ2M6IGpvc2VAaWV0Zi5vcmcNCj4gPiBTdWJqZWN0OiBSRTogW2pvc2VdICMy
NzogbWVtYmVyIG5hbWVzIE1VU1QgYmUgdW5pcXVlIG5lZWRzIGFkZGl0aW9uYWwNCj4gPiB0ZXh0
DQo+ID4NCj4gPiBUaGUgb3BlcmFibGUgc2VudGVuY2UgaW4gbXkgc3VnZ2VzdGVkIHRleHQgYmVs
b3cgaXMgdGhpcyBvbmU6ICJJZiB0aGUNCj4gPiBwbGF0Zm9ybSdzIEpTT04gcGFyc2VyIGRvZXMg
bm90IHJlamVjdCBpbnB1dCB3aXRoIGR1cGxpY2F0ZSBtZW1iZXINCj4gPiBuYW1lcywgdGhlIGlu
cHV0IHdpbGwgZmlyc3QgbmVlZCB0byBiZSBzZXBhcmF0ZWx5IHBhcnNlZCB0byByZWplY3QNCj4g
PiB0aGVzZSBpbnZhbGlkIGlucHV0cyBiZWZvcmUgdXNpbmcgdGhlIHBsYXRmb3JtJ3MgcGFyc2Vy
Ii4gIEluIG90aGVyDQo+ID4gd29yZHMsIGlmIHRoZSBKU09OIHBhcnNlciBpbiB0aGUgZGV2ZWxv
cG1lbnQgcGxhdGZvcm0geW91IGFyZSB1c2luZw0KPiA+IGRvZXMgbm90IHJlamVjdCBpbnB1dHMg
d2l0aCBkdXBsaWNhdGUgbWVtYmVyIG5hbWVzLCB5b3Ugd2lsbCBuZWVkIHRvDQo+ID4gd3JpdGUg
YSBzZXBhcmF0ZSBKU09OIHBhcnNlciB0aGF0IGRldGVjdHMgdGhpcyBpbnZhbGlkIGlucHV0IGFu
ZA0KPiByZWplY3RzIGl0Lg0KPiA+DQo+ID4gVGhpcyBwYXJzZXIgY291bGQgZWl0aGVyIGp1c3Qg
YmUgYSB2YWxpZGF0b3IsIHJldHVybmluZyBUUlVFIG9yIEZBTFNFDQo+ID4gZm9yIHdoZXRoZXIg
dGhlIEpTT04gaXMgdmFsaWQgZm9yIEpPU0UgLSBpbiB3aGljaCBjYXNlIHlvdSdkIHRoZW4NCj4g
cGFzcw0KPiA+IGFueSBpbnB1dHMgdmFsaWRhdGluZyBhcyBUUlVFIHRvIHRoZSBwbGF0Zm9ybSdz
IEpTT04gcGFyc2VyLCBvciBpdA0KPiA+IGNvdWxkIGJlIGEgcmVwbGFjZW1lbnQgcGFyc2VyLCBp
biB3aGljaCBjYXNlIHlvdXIgY29kZSB3b3VsZCBub3QgdXNlDQo+ID4gdGhlIGRldmVsb3BtZW50
IHBsYXRmb3JtJ3MgSlNPTiBwYXJzZXIgYXQgYWxsLiAgSSBzdXNwZWN0IHBlb3BsZQ0KPiB3b3Vs
ZA0KPiA+IGJlIG1vcmUgbGlrZWx5IHRvIGRvIHRoZSBmb3JtZXIgdGhhbiB0aGUgbGF0dGVyLCBi
dXQgYm90aCBhcHByb2FjaGVzDQo+IGFyZSBlcXVpdmFsZW50Lg0KPiA+DQo+ID4gQlRXLCBpZiBp
dCdzIHlvdXIgc2Vuc2UgdGhhdCB0aGVyZSdzIGEgcHJvYmxlbSBvY2N1cnJpbmcgaW4gdGhlIEpT
T04NCj4gPiB3b3JraW5nIGdyb3VwIHdpdGggcmVzcGVjdCB0byBlbmFibGluZyBzdHJpY3QgSlNP
TiBwYXJzaW5nLCB3ZQ0KPiA+IHByb2JhYmx5IG5lZWQgdG8gYmVjb21lIGFjdGl2ZSB0aGVyZS4g
IEZvciBpbnN0YW5jZSwgZXZlbiBpZiB0aGUgc3BlYw0KPiA+IGFsbG93cyBkdXBsaWNhdGUgbWVt
YmVyIG5hbWVzIGxpa2UgdGhlIEVDTUEgc3BlYyBkb2VzLCB0aGUgUkZDIGNvdWxkDQo+ID4gcmVj
b21tZW5kIG9yIHJlcXVpcmUgdGhhdCBwYXJzZXJzIHN1cHBvcnQgYSAic3RyaWN0IiBtb2RlLCB3
aGljaA0KPiByZWplY3RzIHRoZXNlIHVubmVjZXNzYXJpbHkgbGF4IGlucHV0cy4NCj4gPiBUaGVu
IEpPU0UgaW1wbGVtZW50YXRpb25zIGNvdWxkIHVzZSB0aGF0Lg0KPiA+DQo+ID4gCQkJCS0tIE1p
a2UNCj4gPg0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4gRnJvbTogSmltIFNj
aGFhZCBbbWFpbHRvOmlldGZAYXVndXN0Y2VsbGFycy5jb21dDQo+ID4gU2VudDogV2VkbmVzZGF5
LCBKdW5lIDI2LCAyMDEzIDExOjMwIEFNDQo+ID4gVG86ICdqb3NlIGlzc3VlIHRyYWNrZXInOw0K
PiA+IGRyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmVAdG9vbHMuaWV0Zi5vcmc7DQo+
ID4gTWlrZSBKb25lcw0KPiA+IENjOiBqb3NlQGlldGYub3JnDQo+ID4gU3ViamVjdDogUkU6IFtq
b3NlXSAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVkcyBhZGRpdGlvbmFsDQo+
ID4gdGV4dA0KPiA+DQo+ID4gPG5vIGhhdD4NCj4gPg0KPiA+IEkgY29uc2lkZXIgbXlzZWxmIHRv
IGJlIHJlYXNvbmFibHkgY29tcGV0ZW50IGluIGJvdGggRW5nbGlzaCBhbmQNCj4gPiBUZWNobmlj
YWwgRW5nbGlzaC4gIEkgaGF2ZSBubyBpZGVhIHdoYXQgSSBhbSBzdXBwb3NlZCB0byBiZSBkb2lu
ZyB0bw0KPiA+IGRlYWwgd2l0aCB0aGUgdGV4dCBiZWxvdy4gIERvZXMgdGhpcyBtZWFuIHRoYXQg
SSBuZWVkIHRvIHdyaXRlIGFuDQo+ID4gaW5kZXBlbmRlbnQgcGFyc2VyPyAgV2hhdCBhYm91dCBj
YXNlcyB3aGVyZSBpdCBpcyBjb21pbmcgaW4gb24gYQ0KPiA+IHN0cmVhbSBhbmQgSSBkb24ndCBn
ZXQgdG8gc2VlIHRoZSBkYXRhIGJlZm9yZSB0aGUgcGFyc2Ugb2NjdXJzPyAgSG93DQo+ID4gYXJl
IHRoZXkgaW50ZXJwcmV0ZWQgZGlmZmVyZW50bHk/ICBXaGF0IGV4YWN0bHkgaXMgdGhpcyBzdXBw
b3NlZCB0bw0KPiBiZQ0KPiA+IGFkZHJlc3NpbmcuICBNdWNoIG9mIHRoaXMgY291bGQgYmUgc2tp
cHBlZCB3aGVuIHdlIHNhaWQgZG9uJ3QgZG8gaXQuDQo+ID4gU2luY2UgdGhpcyBpcyBubyBsb25n
ZXIgYSB2aWFibGUgc3RhdGVtZW50IGR1ZSB0byB0aGUgc3RhdGUgb2YNCj4gcGFyc2Vycywgd2Ug
bmVlZCB0byBiZSBtb3JlIGV4cGxpY2l0IGFuZCBzYXkgd2hhdCBpcyBnb2luZyBvbi4NCj4gPg0K
PiA+IE5vIEkgZG9uJ3QgY29uc2lkZXIgdGhlIHN1Z2dlc3RlZCB0ZXh0IHRvIGJlIGFkZXF1YXRl
Lg0KPiA+DQo+ID4gPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+ID4gRnJvbTogam9z
ZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86am9zZS1ib3VuY2VzQGlldGYub3JnXSBPbg0KPiBC
ZWhhbGYNCj4gPiA+IE9mIGpvc2UgaXNzdWUgdHJhY2tlcg0KPiA+ID4gU2VudDogVHVlc2RheSwg
SnVuZSAyNSwgMjAxMyA1OjQxIFBNDQo+ID4gPiBUbzogZHJhZnQtaWV0Zi1qb3NlLWpzb24td2Vi
LXNpZ25hdHVyZUB0b29scy5pZXRmLm9yZzsNCj4gPiA+IG1pY2hhZWwuam9uZXNAbWljcm9zb2Z0
LmNvbQ0KPiA+ID4gQ2M6IGpvc2VAaWV0Zi5vcmcNCj4gPiA+IFN1YmplY3Q6IFJlOiBbam9zZV0g
IzI3OiBtZW1iZXIgbmFtZXMgTVVTVCBiZSB1bmlxdWUgbmVlZHMNCj4gPiA+IGFkZGl0aW9uYWwg
dGV4dA0KPiA+ID4NCj4gPiA+ICMyNzogbWVtYmVyIG5hbWVzIE1VU1QgYmUgdW5pcXVlIG5lZWRz
IGFkZGl0aW9uYWwgdGV4dA0KPiA+ID4NCj4gPiA+DQo+ID4gPiBDb21tZW50IChieSBtaWNoYWVs
LmpvbmVzQG1pY3Jvc29mdC5jb20pOg0KPiA+ID4NCj4gPiA+ICBUaGUgSldTIGRyYWZ0IGN1cnJl
bnRseSBzYXlzOg0KPiA+ID4NCj4gPiA+ICAgICAgICAgIFRoZSBIZWFkZXIgUGFyYW1ldGVyIE5h
bWVzIHdpdGhpbiB0aGUgSldTIEhlYWRlciBNVVNUIGJlDQo+IHVuaXF1ZTsNCj4gPiA+ICAgICAg
ICAgIEpXU3Mgd2l0aCBkdXBsaWNhdGUgSGVhZGVyIFBhcmFtZXRlciBOYW1lcyBNVVNUIGJlDQo+
IHJlamVjdGVkLg0KPiA+ID4NCj4gPiA+ICBIb3cgYWJvdXQgY2hhbmdpbmcgdGhpcyB0bzoNCj4g
PiA+DQo+ID4gPiAgICAgICAgICBUaGUgSGVhZGVyIFBhcmFtZXRlciBOYW1lcyB3aXRoaW4gdGhl
IEpXUyBIZWFkZXIgTVVTVCBiZQ0KPiB1bmlxdWU7DQo+ID4gPiAgICAgICAgICBKV1NzIHdpdGgg
ZHVwbGljYXRlIEhlYWRlciBQYXJhbWV0ZXIgTmFtZXMgTVVTVCBiZQ0KPiByZWplY3RlZC4NCj4g
PiA+ICAgICAgICAgIFRoaXMgaXMgbmVjZXNzYXJ5IHRvIHByZXZlbnQgYXR0YWNrcyBpbiB3aGlj
aCB0aGUgc2FtZSBKV1MNCj4gPiA+IG1pZ2h0ICBiZSBpbnRlcnByZXRlZA0KPiA+ID4gICAgICAg
ICAgaW4gZGlmZmVyZW50IHdheXMgYnkgZGlmZmVyZW50IGltcGxlbWVudGF0aW9ucyBhbmQgdG8N
Cj4gPiA+IHByZXZlbnQNCj4gPiBhdHRhY2tlcnMNCj4gPiA+ICAgICAgICAgIGZyb20gaGlkaW5n
IGV4dHJhIGNvbnRlbnQgaW4gZHVwbGljYXRlIG1lbWJlciB2YWx1ZXMuDQo+ID4gPiAgICAgICAg
ICBJZiB0aGUgcGxhdGZvcm0gcyBKU09OIHBhcnNlciBkb2VzIG5vdCByZWplY3QgaW5wdXQgd2l0
aA0KPiA+ID4gZHVwbGljYXRlIG1lbWJlciBuYW1lcywNCj4gPiA+ICAgICAgICAgIHRoZSBpbnB1
dCB3aWxsIGZpcnN0IG5lZWQgdG8gYmUgc2VwYXJhdGVseSBwYXJzZWQgdG8NCj4gcmVqZWN0DQo+
ID4gPiB0aGVzZSAgaW52YWxpZCBpbnB1dHMNCj4gPiA+ICAgICAgICAgIGJlZm9yZSB1c2luZyB0
aGUgcGxhdGZvcm0gcyBwYXJzZXIuDQo+ID4gPg0K

From James.H.Manger@team.telstra.com  Wed Jun 26 22:39:17 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCC421F9B8A for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level: 
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFYf6fyJXjF9 for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 22:39:11 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5975621F9BF1 for <jose@ietf.org>; Wed, 26 Jun 2013 22:39:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,949,1363093200"; d="scan'208";a="144888987"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipoani.tcif.telstra.com.au with ESMTP; 27 Jun 2013 15:39:06 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7118"; a="146846229"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipccni.tcif.telstra.com.au with ESMTP; 27 Jun 2013 15:39:06 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Thu, 27 Jun 2013 15:39:05 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Tim Bray <tbray@textuality.com>, Mike Jones <Michael.Jones@microsoft.com>
Date: Thu, 27 Jun 2013 15:39:05 +1000
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: Ac5y9omnN2qpgs6iQLe4JDlwlLM0cgAAK0zw
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com>
In-Reply-To: <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 05:39:17 -0000

PiBJIHRoaW5rIGl04oCZcyBhIG5pY2UgY2xlYW4gbWluaW1hbCBzb2x1dGlvbiB0byBzYXkgdGhh
dCBwcm9kdWNlcnMgTVVTVA0KPiBOT1QgZ2VuZXJhdGUgZHVwZXMsIGVuZCBvZiBzdG9yeS7CoCBJ
IGRvbuKAmXQgdGhpbmsgc2F5aW5nIGFueXRoaW5nIGJleW9uZA0KPiB0aGF0IGFkZHMgdmFsdWUu
IC1UDQoNCkNsZWFuIGFuZCBtaW5pbWFsIHRoYXQgbWF5IGJlLCBidXQgaXQgaWdub3JlcyB0aGUg
c2VjdXJpdHkgaXNzdWUuIFdlIGRvbid0IHdhbnQgYSBtYWxpY2lvdXMgcHJvZHVjZXIgKHdobyBp
cyBzbyBtYWxpY2lvdXMgdGhleSBpZ25vcmUgYSBNVVNUKSB0byBjcmVhdGUgSk9TRSBtZXNzYWdl
cyB0aGF0IGEgSk9TRS1jb21wbGlhbnQgc2VjdXJpdHkgbGF5ZXIgYWNjZXB0cyBhcyAiYmVuaWdu
IGludGVycHJldGF0aW9uICMxIiBzbyBpdCBwYXNzZXMgdGhlIG1lc3NhZ2Ugb24gdG8gdGhlIEpP
U0UtY29tcGxpYW50IGJhY2tlbmQgYXBwIHRoYXQgYWN0cyBvbiAibmFzdHkgaW50ZXJwcmV0YXRp
b24gIzIiLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQo=

From tbray@textuality.com  Wed Jun 26 23:16:02 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5D8321F9C3D for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 23:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmZBz998WVpw for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 23:15:57 -0700 (PDT)
Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by ietfa.amsl.com (Postfix) with ESMTP id DD89E21F9C46 for <jose@ietf.org>; Wed, 26 Jun 2013 23:15:46 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id b10so296602vea.16 for <jose@ietf.org>; Wed, 26 Jun 2013 23:15:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=mIrNH5XJvcv2hP0vJgLsZorYpTeD8EdAz+3a0/gmKJ8=; b=JFeM+sUYf6YxfY79lW5JoUm09wQuUmr+l4k+yAWSwhybxdtsxXwE3e8m3Blgjrxhze URcYsLMPR/MPxsNB66vmWutGuU3w63TD5QNUX8I3L4ciQkNhk7uZ5W/qhst/fcscwmyP dzN+9V3/SCIYZ56EszQpjrUGcuwFTYERiDbOEXOP6UvnvUyvUmX0Svn0FnPzo8qRCPxO KSbua53S1Dxi5/yPXtN77iXQxQj+mP9bFBwNb9NcZOWkjGwd1TKtoXc47Dy46BcYMZZ1 ZbFRawYnr3vFuoElhOsDN4kZjfhV3uawfPA+rT/O0rna+KklaGJU/CCR87XzLjte/pzw CesA==
MIME-Version: 1.0
X-Received: by 10.58.54.70 with SMTP id h6mr2965254vep.36.1372313745035; Wed, 26 Jun 2013 23:15:45 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Wed, 26 Jun 2013 23:15:44 -0700 (PDT)
X-Originating-IP: [172.26.52.9]
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 26 Jun 2013 23:15:44 -0700
Message-ID: <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=089e0122ad064b299004e01cb1d0
X-Gm-Message-State: ALoCoQmWs9P9LO6uh1ywGY23rg34DMe2U9nX1ICM5CIiPkVS0UE/nmZzGZfZRPdKjQ2aX0up7MmQ
Cc: Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 06:16:02 -0000

--089e0122ad064b299004e01cb1d0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Well, you have a practical problem in that most implementers will want to
use a standard JSON library, which is good practice because it will be
well-debugged, and most libraries [sob] silently take care of dupe keys and
don=E2=80=99t have a way to tell the client software what happened. So if y=
ou want
truly predictable behavior, you=E2=80=99re forcing the use of hand-construc=
ted JSON
parsers. And that sucks, because getting good performance in JSON parsing
is surprisingly hard, with dramatic performance differences between
implementations. So you=E2=80=99re forcing receiving software which wants t=
o be
conformant to use a hand-rolled parser which will probably have lousy
performance and have other bugs which in fact may compromise security more
than dupe-key tricks could.  -T


On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> > I think it=E2=80=99s a nice clean minimal solution to say that producer=
s MUST
> > NOT generate dupes, end of story.  I don=E2=80=99t think saying anythin=
g beyond
> > that adds value. -T
>
> Clean and minimal that may be, but it ignores the security issue. We don'=
t
> want a malicious producer (who is so malicious they ignore a MUST) to
> create JOSE messages that a JOSE-compliant security layer accepts as
> "benign interpretation #1" so it passes the message on to the
> JOSE-compliant backend app that acts on "nasty interpretation #2".
>
> --
> James Manger
>

--089e0122ad064b299004e01cb1d0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well, you have a practical problem in that most implemente=
rs will want to use a standard JSON library, which is good practice because=
 it will be well-debugged, and most libraries [sob] silently take care of d=
upe keys and don=E2=80=99t have a way to tell the client software what happ=
ened. So if you want truly predictable behavior, you=E2=80=99re forcing the=
 use of hand-constructed JSON parsers. And that sucks, because getting good=
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you=E2=80=99re forcing receiving =
software which wants to be conformant to use a hand-rolled parser which wil=
l probably have lousy performance and have other bugs which in fact may com=
promise security more than dupe-key tricks could.=C2=A0 -T<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Jun 26, 2013 at 10:39 PM, Manger, James H <span dir=3D"ltr">&lt;<a href=3D=
"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Manger@t=
eam.telstra.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; I think it=E2=80=99s =
a nice clean minimal solution to say that producers MUST<br>
&gt; NOT generate dupes, end of story.=C2=A0 I don=E2=80=99t think saying a=
nything beyond<br>
&gt; that adds value. -T<br>
<br>
</div>Clean and minimal that may be, but it ignores the security issue. We =
don&#39;t want a malicious producer (who is so malicious they ignore a MUST=
) to create JOSE messages that a JOSE-compliant security layer accepts as &=
quot;benign interpretation #1&quot; so it passes the message on to the JOSE=
-compliant backend app that acts on &quot;nasty interpretation #2&quot;.<br=
>

<br>
--<br>
James Manger<br>
</blockquote></div><br></div>

--089e0122ad064b299004e01cb1d0--

From James.H.Manger@team.telstra.com  Wed Jun 26 23:30:08 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2ABC21F9C5B for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 23:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level: 
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RehNFaFs-XCf for <jose@ietfa.amsl.com>; Wed, 26 Jun 2013 23:30:02 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id DD15D21F9C60 for <jose@ietf.org>; Wed, 26 Jun 2013 23:30:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,950,1363093200";  d="scan'208,217";a="136441261"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipobni.tcif.telstra.com.au with ESMTP; 27 Jun 2013 16:29:59 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7118"; a="91005249"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipcani.tcif.telstra.com.au with ESMTP; 27 Jun 2013 16:29:59 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Thu, 27 Jun 2013 16:29:59 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Tim Bray <tbray@textuality.com>
Date: Thu, 27 Jun 2013 16:29:58 +1000
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: Ac5y/csF1c6qnG6VTGGz8Tyy5Pl0wgAABhBQ
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com>
In-Reply-To: <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E1151BEDDD3CWSMSG3153Vsrv_"
MIME-Version: 1.0
Cc: Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 06:30:08 -0000

--_000_255B9BB34FB7D647A506DC292726F6E1151BEDDD3CWSMSG3153Vsrv_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TW9zdCBKU09OIGxpYnJhcmllcyB0aGF0IHNpbGVudGx5IGFjY2VwdCBbc29iXSBkdXBlIGtleXMg
YXQgbGVhc3QgY29uc2lzdGVudGx5IHVzZSB0aGUgbGFzdCBrZXkuIEFsbG93aW5nIGp1c3QgdGhh
dCBiZWhhdmlvdXIgKG9yIHJlamVjdGluZyBkdXBlcyksIHdoaWxlIGZvcmJpZGRpbmcgYWNjZXB0
YW5jZSBvZiBhIG5vbi1sYXN0IGR1cGUgKGVnIGZpcnN0IGtleSksIGlzIHNhZmUgYW5kIGFsbG93
cyBtb3N0IEpTT04gbGlicmFyaWVzIHRvIGJlIHVzZWQuIFNpbmNlIHRoaXMgYWNjZXB0cyBtb3N0
IGxpYnJhcmllcyBJIHRoaW5rIGl0IGlzIHByYWN0aWNhbC4NCg0KSGVuY2UgSSBzdWdnZXN0Og0K
DQoNCj4gICBBIGNyZWF0b3Igb2YgYSBKT1NFIG1lc3NhZ2UgTVVTVCBOT1QgcHV0IGR1cGxpY2F0
ZSBuYW1lcyBpbiBhbnkgSlNPTg0KDQo+IG9iamVjdCBpbiBhIEpPU0UgaGVhZGVyLg0KDQo+ICAg
VG8gcHJldmVudCBhdHRhY2tzIHdoZXJlIGEgSk9TRSBtZXNzYWdlIGlzIGludGVycHJldGVkIGFz
IGRpZmZlcmVudA0KDQo+IHZhbGlkIG1lc3NhZ2VzIGJ5IGRpZmZlcmVudCByZWNpcGllbnRzLCBl
YWNoIHJlY2lwaWVudCBNVVNUIGVpdGhlcg0KDQo+IHJlamVjdCBtZXNzYWdlcyB3aXRoIGR1cGxp
Y2F0ZSBuYW1lcyBvciBhY2NlcHQgb25seSB0aGUgbGFzdCBuYW1lLg0KDQpUaGlzIGlzbuKAmXQg
4oCcdHJ1bHkgcHJlZGljdGFibGXigJ0gYXMgYSBtZXNzYWdlIHdpdGggZHVwZXMgbWlnaHQgYmUg
YWNjZXB0ZWQgb3IgcmVqZWN0ZWQuIFRoZSBjcnVjaWFsIHBvaW50IGlzIHRoYXQgaWYgYSBtZXNz
YWdlIGlzIGFjY2VwdGVkIGl0IGlzIHByZWRpY3RhYmxlLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQoN
CkZyb206IFRpbSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5jb21dDQpTZW50OiBUaHVy
c2RheSwgMjcgSnVuZSAyMDEzIDQ6MTYgUE0NClRvOiBNYW5nZXIsIEphbWVzIEgNCkNjOiBNaWtl
IEpvbmVzOyBKaW0gU2NoYWFkOyBqb3NlQGlldGYub3JnOyBkcmFmdC1pZXRmLWpvc2UtanNvbi13
ZWItc2lnbmF0dXJlQHRvb2xzLmlldGYub3JnDQpTdWJqZWN0OiBSZTogW2pvc2VdICMyNzogbWVt
YmVyIG5hbWVzIE1VU1QgYmUgdW5pcXVlIG5lZWRzIGFkZGl0aW9uYWwgdGV4dA0KDQpXZWxsLCB5
b3UgaGF2ZSBhIHByYWN0aWNhbCBwcm9ibGVtIGluIHRoYXQgbW9zdCBpbXBsZW1lbnRlcnMgd2ls
bCB3YW50IHRvIHVzZSBhIHN0YW5kYXJkIEpTT04gbGlicmFyeSwgd2hpY2ggaXMgZ29vZCBwcmFj
dGljZSBiZWNhdXNlIGl0IHdpbGwgYmUgd2VsbC1kZWJ1Z2dlZCwgYW5kIG1vc3QgbGlicmFyaWVz
IFtzb2JdIHNpbGVudGx5IHRha2UgY2FyZSBvZiBkdXBlIGtleXMgYW5kIGRvbuKAmXQgaGF2ZSBh
IHdheSB0byB0ZWxsIHRoZSBjbGllbnQgc29mdHdhcmUgd2hhdCBoYXBwZW5lZC4gU28gaWYgeW91
IHdhbnQgdHJ1bHkgcHJlZGljdGFibGUgYmVoYXZpb3IsIHlvdeKAmXJlIGZvcmNpbmcgdGhlIHVz
ZSBvZiBoYW5kLWNvbnN0cnVjdGVkIEpTT04gcGFyc2Vycy4gQW5kIHRoYXQgc3Vja3MsIGJlY2F1
c2UgZ2V0dGluZyBnb29kIHBlcmZvcm1hbmNlIGluIEpTT04gcGFyc2luZyBpcyBzdXJwcmlzaW5n
bHkgaGFyZCwgd2l0aCBkcmFtYXRpYyBwZXJmb3JtYW5jZSBkaWZmZXJlbmNlcyBiZXR3ZWVuIGlt
cGxlbWVudGF0aW9ucy4gU28geW914oCZcmUgZm9yY2luZyByZWNlaXZpbmcgc29mdHdhcmUgd2hp
Y2ggd2FudHMgdG8gYmUgY29uZm9ybWFudCB0byB1c2UgYSBoYW5kLXJvbGxlZCBwYXJzZXIgd2hp
Y2ggd2lsbCBwcm9iYWJseSBoYXZlIGxvdXN5IHBlcmZvcm1hbmNlIGFuZCBoYXZlIG90aGVyIGJ1
Z3Mgd2hpY2ggaW4gZmFjdCBtYXkgY29tcHJvbWlzZSBzZWN1cml0eSBtb3JlIHRoYW4gZHVwZS1r
ZXkgdHJpY2tzIGNvdWxkLiAgLVQNCg0KT24gV2VkLCBKdW4gMjYsIDIwMTMgYXQgMTA6MzkgUE0s
IE1hbmdlciwgSmFtZXMgSCA8SmFtZXMuSC5NYW5nZXJAdGVhbS50ZWxzdHJhLmNvbTxtYWlsdG86
SmFtZXMuSC5NYW5nZXJAdGVhbS50ZWxzdHJhLmNvbT4+IHdyb3RlOg0KPiBJIHRoaW5rIGl04oCZ
cyBhIG5pY2UgY2xlYW4gbWluaW1hbCBzb2x1dGlvbiB0byBzYXkgdGhhdCBwcm9kdWNlcnMgTVVT
VA0KPiBOT1QgZ2VuZXJhdGUgZHVwZXMsIGVuZCBvZiBzdG9yeS4gIEkgZG9u4oCZdCB0aGluayBz
YXlpbmcgYW55dGhpbmcgYmV5b25kDQo+IHRoYXQgYWRkcyB2YWx1ZS4gLVQNCkNsZWFuIGFuZCBt
aW5pbWFsIHRoYXQgbWF5IGJlLCBidXQgaXQgaWdub3JlcyB0aGUgc2VjdXJpdHkgaXNzdWUuIFdl
IGRvbid0IHdhbnQgYSBtYWxpY2lvdXMgcHJvZHVjZXIgKHdobyBpcyBzbyBtYWxpY2lvdXMgdGhl
eSBpZ25vcmUgYSBNVVNUKSB0byBjcmVhdGUgSk9TRSBtZXNzYWdlcyB0aGF0IGEgSk9TRS1jb21w
bGlhbnQgc2VjdXJpdHkgbGF5ZXIgYWNjZXB0cyBhcyAiYmVuaWduIGludGVycHJldGF0aW9uICMx
IiBzbyBpdCBwYXNzZXMgdGhlIG1lc3NhZ2Ugb24gdG8gdGhlIEpPU0UtY29tcGxpYW50IGJhY2tl
bmQgYXBwIHRoYXQgYWN0cyBvbiAibmFzdHkgaW50ZXJwcmV0YXRpb24gIzIiLg0KDQotLQ0KSmFt
ZXMgTWFuZ2VyDQoNCg==

--_000_255B9BB34FB7D647A506DC292726F6E1151BEDDD3CWSMSG3153Vsrv_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N
CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5N
c29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFy
Z2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjVwdDsNCglm
b250LWZhbWlseTpDb25zb2xhczt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlw
ZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0K
CWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5QbGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQ
bGFpbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu
azoiUGxhaW4gVGV4dCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7fQ0KLk1zb0NocERlZmF1bHQN
Cgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7
fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwh
LS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3Bp
ZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRh
dGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+PC9oZWFkPjxib2R5
IGxhbmc9RU4tQVUgbGluaz1ibHVlIHZsaW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdvcmRTZWN0aW9u
MT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5Nb3N0IEpTT04gbGli
cmFyaWVzIHRoYXQgc2lsZW50bHkgYWNjZXB0IFtzb2JdIGR1cGUga2V5cyBhdCBsZWFzdCBjb25z
aXN0ZW50bHkgdXNlIHRoZSBsYXN0IGtleS4gQWxsb3dpbmcganVzdCB0aGF0IGJlaGF2aW91ciAo
b3IgcmVqZWN0aW5nIGR1cGVzKSwgd2hpbGUgZm9yYmlkZGluZyBhY2NlcHRhbmNlIG9mIGEgbm9u
LWxhc3QgZHVwZSAoZWcgZmlyc3Qga2V5KSwgaXMgc2FmZSBhbmQgYWxsb3dzIG1vc3QgSlNPTiBs
aWJyYXJpZXMgdG8gYmUgdXNlZC4gU2luY2UgdGhpcyBhY2NlcHRzIG1vc3QgbGlicmFyaWVzIEkg
dGhpbmsgaXQgaXMgcHJhY3RpY2FsLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29O
b3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+SGVuY2UgSSBzdWdnZXN0
OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjoj
MUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgwqDCoEEgY3JlYXRvciBvZiBhIEpPU0UgbWVzc2FnZSBNVVNUIE5PVCBwdXQgZHVwbGlj
YXRlIG5hbWVzIGluIGFueSBKU09OPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNvUGxhaW5UZXh0
PiZndDsgb2JqZWN0IGluIGEgSk9TRSBoZWFkZXIuPG86cD48L286cD48L3A+PHAgY2xhc3M9TXNv
UGxhaW5UZXh0PiZndDsgwqDCoFRvIHByZXZlbnQgYXR0YWNrcyB3aGVyZSBhIEpPU0UgbWVzc2Fn
ZSBpcyBpbnRlcnByZXRlZCBhcyBkaWZmZXJlbnQ8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Q
bGFpblRleHQ+Jmd0OyB2YWxpZCBtZXNzYWdlcyBieSBkaWZmZXJlbnQgcmVjaXBpZW50cywgZWFj
aCByZWNpcGllbnQgTVVTVCBlaXRoZXI8bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29QbGFpblRl
eHQ+Jmd0OyByZWplY3QgbWVzc2FnZXMgd2l0aCBkdXBsaWNhdGUgbmFtZXMgb3IgYWNjZXB0IG9u
bHkgdGhlIGxhc3QgbmFtZS48bzpwPjwvbzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+VGhpcyBpc27igJl0IOKAnHRydWx5IHByZWRp
Y3RhYmxl4oCdIGFzIGEgbWVzc2FnZSB3aXRoIGR1cGVzIG1pZ2h0IGJlIGFjY2VwdGVkIG9yIHJl
amVjdGVkLiBUaGUgY3J1Y2lhbCBwb2ludCBpcyB0aGF0IGlmIGEgbWVzc2FnZSBpcyBhY2NlcHRl
ZCBpdCBpcyBwcmVkaWN0YWJsZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi
c2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPi0tPG86cD48L286cD48L3Nw
YW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPkphbWVzIE1h
bmdlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv
cjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRpdiBzdHlsZT0nYm9yZGVy
Om5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQu
MHB0Jz48ZGl2PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtJz48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+
PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFo
b21hIiwic2Fucy1zZXJpZiInPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPUVOLVVTIHN0eWxl
PSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJUYWhvbWEiLCJzYW5zLXNlcmlmIic+IFRp
bSBCcmF5IFttYWlsdG86dGJyYXlAdGV4dHVhbGl0eS5jb21dIDxicj48Yj5TZW50OjwvYj4gVGh1
cnNkYXksIDI3IEp1bmUgMjAxMyA0OjE2IFBNPGJyPjxiPlRvOjwvYj4gTWFuZ2VyLCBKYW1lcyBI
PGJyPjxiPkNjOjwvYj4gTWlrZSBKb25lczsgSmltIFNjaGFhZDsgam9zZUBpZXRmLm9yZzsgZHJh
ZnQtaWV0Zi1qb3NlLWpzb24td2ViLXNpZ25hdHVyZUB0b29scy5pZXRmLm9yZzxicj48Yj5TdWJq
ZWN0OjwvYj4gUmU6IFtqb3NlXSAjMjc6IG1lbWJlciBuYW1lcyBNVVNUIGJlIHVuaXF1ZSBuZWVk
cyBhZGRpdGlvbmFsIHRleHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9kaXY+PHAgY2xh
c3M9TXNvTm9ybWFsPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPjxkaXY+PHAgY2xhc3M9TXNvTm9ybWFs
PldlbGwsIHlvdSBoYXZlIGEgcHJhY3RpY2FsIHByb2JsZW0gaW4gdGhhdCBtb3N0IGltcGxlbWVu
dGVycyB3aWxsIHdhbnQgdG8gdXNlIGEgc3RhbmRhcmQgSlNPTiBsaWJyYXJ5LCB3aGljaCBpcyBn
b29kIHByYWN0aWNlIGJlY2F1c2UgaXQgd2lsbCBiZSB3ZWxsLWRlYnVnZ2VkLCBhbmQgbW9zdCBs
aWJyYXJpZXMgW3NvYl0gc2lsZW50bHkgdGFrZSBjYXJlIG9mIGR1cGUga2V5cyBhbmQgZG9u4oCZ
dCBoYXZlIGEgd2F5IHRvIHRlbGwgdGhlIGNsaWVudCBzb2Z0d2FyZSB3aGF0IGhhcHBlbmVkLiBT
byBpZiB5b3Ugd2FudCB0cnVseSBwcmVkaWN0YWJsZSBiZWhhdmlvciwgeW914oCZcmUgZm9yY2lu
ZyB0aGUgdXNlIG9mIGhhbmQtY29uc3RydWN0ZWQgSlNPTiBwYXJzZXJzLiBBbmQgdGhhdCBzdWNr
cywgYmVjYXVzZSBnZXR0aW5nIGdvb2QgcGVyZm9ybWFuY2UgaW4gSlNPTiBwYXJzaW5nIGlzIHN1
cnByaXNpbmdseSBoYXJkLCB3aXRoIGRyYW1hdGljIHBlcmZvcm1hbmNlIGRpZmZlcmVuY2VzIGJl
dHdlZW4gaW1wbGVtZW50YXRpb25zLiBTbyB5b3XigJlyZSBmb3JjaW5nIHJlY2VpdmluZyBzb2Z0
d2FyZSB3aGljaCB3YW50cyB0byBiZSBjb25mb3JtYW50IHRvIHVzZSBhIGhhbmQtcm9sbGVkIHBh
cnNlciB3aGljaCB3aWxsIHByb2JhYmx5IGhhdmUgbG91c3kgcGVyZm9ybWFuY2UgYW5kIGhhdmUg
b3RoZXIgYnVncyB3aGljaCBpbiBmYWN0IG1heSBjb21wcm9taXNlIHNlY3VyaXR5IG1vcmUgdGhh
biBkdXBlLWtleSB0cmlja3MgY291bGQuJm5ic3A7IC1UPG86cD48L286cD48L3A+PC9kaXY+PGRp
dj48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21hcmdpbi1ib3R0b206MTIuMHB0Jz48bzpwPiZu
YnNwOzwvbzpwPjwvcD48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbD5PbiBXZWQsIEp1biAyNiwgMjAx
MyBhdCAxMDozOSBQTSwgTWFuZ2VyLCBKYW1lcyBIICZsdDs8YSBocmVmPSJtYWlsdG86SmFtZXMu
SC5NYW5nZXJAdGVhbS50ZWxzdHJhLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPkphbWVzLkguTWFuZ2Vy
QHRlYW0udGVsc3RyYS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD48ZGl2PjxwIGNs
YXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbToxMi4wcHQnPiZndDsgSSB0aGluayBp
dOKAmXMgYSBuaWNlIGNsZWFuIG1pbmltYWwgc29sdXRpb24gdG8gc2F5IHRoYXQgcHJvZHVjZXJz
IE1VU1Q8YnI+Jmd0OyBOT1QgZ2VuZXJhdGUgZHVwZXMsIGVuZCBvZiBzdG9yeS4mbmJzcDsgSSBk
b27igJl0IHRoaW5rIHNheWluZyBhbnl0aGluZyBiZXlvbmQ8YnI+Jmd0OyB0aGF0IGFkZHMgdmFs
dWUuIC1UPG86cD48L286cD48L3A+PC9kaXY+PHAgY2xhc3M9TXNvTm9ybWFsPkNsZWFuIGFuZCBt
aW5pbWFsIHRoYXQgbWF5IGJlLCBidXQgaXQgaWdub3JlcyB0aGUgc2VjdXJpdHkgaXNzdWUuIFdl
IGRvbid0IHdhbnQgYSBtYWxpY2lvdXMgcHJvZHVjZXIgKHdobyBpcyBzbyBtYWxpY2lvdXMgdGhl
eSBpZ25vcmUgYSBNVVNUKSB0byBjcmVhdGUgSk9TRSBtZXNzYWdlcyB0aGF0IGEgSk9TRS1jb21w
bGlhbnQgc2VjdXJpdHkgbGF5ZXIgYWNjZXB0cyBhcyAmcXVvdDtiZW5pZ24gaW50ZXJwcmV0YXRp
b24gIzEmcXVvdDsgc28gaXQgcGFzc2VzIHRoZSBtZXNzYWdlIG9uIHRvIHRoZSBKT1NFLWNvbXBs
aWFudCBiYWNrZW5kIGFwcCB0aGF0IGFjdHMgb24gJnF1b3Q7bmFzdHkgaW50ZXJwcmV0YXRpb24g
IzImcXVvdDsuPGJyPjxicj4tLTxicj5KYW1lcyBNYW5nZXI8bzpwPjwvbzpwPjwvcD48L2Rpdj48
cCBjbGFzcz1Nc29Ob3JtYWw+PG86cD4mbmJzcDs8L286cD48L3A+PC9kaXY+PC9kaXY+PC9kaXY+
PC9ib2R5PjwvaHRtbD4=

--_000_255B9BB34FB7D647A506DC292726F6E1151BEDDD3CWSMSG3153Vsrv_--

From cabo@tzi.org  Thu Jun 27 00:16:43 2013
Return-Path: <cabo@tzi.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B7411E80D3 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 00:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atdFpSA6GBCz for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 00:16:39 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id C20A321F9A8B for <jose@ietf.org>; Thu, 27 Jun 2013 00:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5R7GAUC019075; Thu, 27 Jun 2013 09:16:11 +0200 (CEST)
Received: from [134.102.116.224] (unknown [134.102.116.224]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CC1283373; Thu, 27 Jun 2013 09:16:10 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BE456D2@WSMSG3153V.srv.dir.telstra.com>
Date: Thu, 27 Jun 2013 09:16:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE290511-7365-4815-A99A-481F8699CC37@tzi.org>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE456D2@WSMSG3153V.srv.dir.telstra.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
X-Mailer: Apple Mail (2.1508)
Cc: Jim Schaad <ietf@augustcellars.com>, 'Mike Jones' <Michael.Jones@microsoft.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 07:16:43 -0000

On Jun 27, 2013, at 07:26, "Manger, James H" =
<James.H.Manger@team.telstra.com> wrote:

> each recipient MUST either reject messages with duplicate names or =
accept only the last name.

Maybe only gatekeeper functions need validating parsers?

gatekeeper function: A processing step that derives (makes/validates)
an assertion from a JOSE object and then moves forward that JOSE
object unchanged to the next processing step (e.g., to preserve a
signature)

validating parser: A JSON parser that rejects JSON that might be
interpreted differently by another JSON parser

Are we sure that the duplicate key issue is the only one that needs to
be checked by a validating parser?  A number of candidate issues:

http://www.ietf.org/mail-archive/web/json/current/msg01068.html

E.g., what about issue 3.8?  If a gatekeeper function derives an
asssertion about a JOSE object mentioning twitter ID
10765432100123456789, but the next step thinks it is about
10765432100123458000?

https://dev.twitter.com/docs/twitter-ids-json-and-snowflake

The list in msg01068 also is not complete for our purposes, e.g., it
mentions normalization issues only in passing.  A validating parser
sure wants to reject anything that isn't already normalized Unicode.

Maybe gatekeeper functions are not such a bright idea?

Gr=FC=DFe, Carsten


From James.H.Manger@team.telstra.com  Thu Jun 27 01:09:07 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDF421F9BB4 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 01:09:07 -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=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UqXvtPsCei8e for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 01:09:03 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfa.amsl.com (Postfix) with ESMTP id C916121F9BB7 for <jose@ietf.org>; Thu, 27 Jun 2013 01:09:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,950,1363093200"; d="scan'208";a="143463213"
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipoavi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 18:08:57 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7118"; a="141235152"
Received: from wsmsg3753.srv.dir.telstra.com ([172.49.40.174]) by ipcbvi.tcif.telstra.com.au with ESMTP; 27 Jun 2013 18:08:57 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3753.srv.dir.telstra.com ([172.49.40.174]) with mapi; Thu, 27 Jun 2013 18:08:57 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Carsten Bormann <cabo@tzi.org>
Date: Thu, 27 Jun 2013 18:08:55 +1000
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: Ac5zBkoe9YPcCT6+Q/uqZxl6igm5pwAAGOQA
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151BEDDEB6@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE456D2@WSMSG3153V.srv.dir.telstra.com> <EE290511-7365-4815-A99A-481F8699CC37@tzi.org>
In-Reply-To: <EE290511-7365-4815-A99A-481F8699CC37@tzi.org>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Jim Schaad <ietf@augustcellars.com>, 'Mike Jones' <Michael.Jones@microsoft.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 08:09:07 -0000

PiA+IGVhY2ggcmVjaXBpZW50IE1VU1QgZWl0aGVyIHJlamVjdCBtZXNzYWdlcyB3aXRoIGR1cGxp
Y2F0ZSBuYW1lcyBvcg0KPiBhY2NlcHQgb25seSB0aGUgbGFzdCBuYW1lLg0KPiANCj4gTWF5YmUg
b25seSBnYXRla2VlcGVyIGZ1bmN0aW9ucyBuZWVkIHZhbGlkYXRpbmcgcGFyc2Vycz8NCg0KRG91
YnQgaXQuIEhvdyBjYW4gYSBKT1NFIGxpYnJhcnkgdGVsbCBpZiBpdCB3aWxsIGV2ZXIgYmUgdXNl
ZCBieSBhIGdhdGV3YXkuLi4gYmV0dGVyIHRyZWF0IGFsbCBsaWJyYXJpZXMgYXMgcG90ZW50aWFs
IGdhdGV3YXlzLg0KDQo+IGdhdGVrZWVwZXIgZnVuY3Rpb246IEEgcHJvY2Vzc2luZyBzdGVwIHRo
YXQgZGVyaXZlcyAobWFrZXMvdmFsaWRhdGVzKQ0KPiBhbiBhc3NlcnRpb24gZnJvbSBhIEpPU0Ug
b2JqZWN0IGFuZCB0aGVuIG1vdmVzIGZvcndhcmQgdGhhdCBKT1NFIG9iamVjdA0KPiB1bmNoYW5n
ZWQgdG8gdGhlIG5leHQgcHJvY2Vzc2luZyBzdGVwIChlLmcuLCB0byBwcmVzZXJ2ZSBhDQo+IHNp
Z25hdHVyZSkNCj4gDQo+IHZhbGlkYXRpbmcgcGFyc2VyOiBBIEpTT04gcGFyc2VyIHRoYXQgcmVq
ZWN0cyBKU09OIHRoYXQgbWlnaHQgYmUNCj4gaW50ZXJwcmV0ZWQgZGlmZmVyZW50bHkgYnkgYW5v
dGhlciBKU09OIHBhcnNlcg0KDQpCdXQgbm93IGEgdmFsaWRhdGluZyBwYXJzZXIgTVVTVCByZWpl
Y3QgZHVwZXMsIGFzIG90aGVycyBtaWdodCBpbnRlcnByZXQgdGhlbSBkaWZmZXJlbnRseSwgc28g
dGhlIHZhbGlkYXRpbmcgcGFyc2VyIGNhbm5vdCBiZSBidWlsdCBmcm9tIG1hbnkgc3RhbmRhcmQg
SlNPTiBsaWJyYXJpZXMuDQoNCj4gQXJlIHdlIHN1cmUgdGhhdCB0aGUgZHVwbGljYXRlIGtleSBp
c3N1ZSBpcyB0aGUgb25seSBvbmUgdGhhdCBuZWVkcyB0bw0KPiBiZSBjaGVja2VkIGJ5IGEgdmFs
aWRhdGluZyBwYXJzZXI/ICBBIG51bWJlciBvZiBjYW5kaWRhdGUgaXNzdWVzOg0KPiANCj4gaHR0
cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2pzb24vY3VycmVudC9tc2cwMTA2OC5o
dG1sDQo+IA0KPiBFLmcuLCB3aGF0IGFib3V0IGlzc3VlIDMuOD8gIElmIGEgZ2F0ZWtlZXBlciBm
dW5jdGlvbiBkZXJpdmVzIGFuDQo+IGFzc3NlcnRpb24gYWJvdXQgYSBKT1NFIG9iamVjdCBtZW50
aW9uaW5nIHR3aXR0ZXIgSUQNCj4gMTA3NjU0MzIxMDAxMjM0NTY3ODksIGJ1dCB0aGUgbmV4dCBz
dGVwIHRoaW5rcyBpdCBpcyBhYm91dA0KPiAxMDc2NTQzMjEwMDEyMzQ1ODAwMD8NCj4NCj4gaHR0
cHM6Ly9kZXYudHdpdHRlci5jb20vZG9jcy90d2l0dGVyLWlkcy1qc29uLWFuZC1zbm93Zmxha2UN
Cg0KVGhhdCB3b3VsZCBiZSBhIHByb2JsZW0sIGJ1dCBvbmUgZm9yIHRoZSBhcHAgdXNpbmcgSk9T
RSB0byBmaXgsIG5vdCBKT1NFIGl0c2VsZi4gSSBkb24ndCB0aGluayBhbnkgSk9TRSBmaWVsZHMg
dXNlIEpTT04gbnVtYmVycyBhcyBpbnRlZ2VyczsgYW5kIGlmIHRoZXkgZGlkIHRoZSBKT1NFIHNw
ZWMgc2hvdWxkIGFkZCBhICJNVVNUIGJlIHVuZGVyIDJeNTMiIHJ1bGUuIEF0IGxlYXN0IGluIHRo
aXMgY2FzZSBpdCBpcyBjbGVhcmVyIHdoYXQgaXMgYXQgZmF1bHQuDQoNCj4gVGhlIGxpc3QgaW4g
bXNnMDEwNjggYWxzbyBpcyBub3QgY29tcGxldGUgZm9yIG91ciBwdXJwb3NlcywgZS5nLiwgaXQN
Cj4gbWVudGlvbnMgbm9ybWFsaXphdGlvbiBpc3N1ZXMgb25seSBpbiBwYXNzaW5nLiAgQSB2YWxp
ZGF0aW5nIHBhcnNlcg0KPiBzdXJlIHdhbnRzIHRvIHJlamVjdCBhbnl0aGluZyB0aGF0IGlzbid0
IGFscmVhZHkgbm9ybWFsaXplZCBVbmljb2RlLg0KDQpOb3Qgc3VyZSBpZiB0aGF0IGlzIGEgcHJv
YmxlbS4gSk9TRSBtaWdodCBhdm9pZCB0aG9zZSBpc3N1ZXMgKGFsbW9zdCBieSBhY2NpZGVudCkg
Ynkgb25seSBkZWZpbmluZyBmaWVsZCBuYW1lcyB0aGF0IHVzZSBBU0NJSSBsZXR0ZXJzLiBJZiBp
dCB0dXJucyBvdXQgdGhhdCBhIGJ1bmNoIG9mIEpTT04gcGFyc2VycyAibGVnaXRpbWF0ZWx5IiBh
Y2NlcHQgeyJhbGciOiJBQkMiLCJcdTI0RDBcdTI0REJcdTI0RDYiOiJYWVoifSBhcyBoYXZpbmcg
YW4gImFsZyIgdmFsdWUgb2YgWFlaIChkdWUgdG8gc29tZSBub3JtYWxpemF0aW9uKSB3ZSB3b3Vs
ZCBuZWVkIHRvIGFtZW5kIEpPU0UgdG8gZXhwbGljaXRseSBmb3JiaWQgaXQuIEkgZG91YnQgdGhh
dCBpc24ndCBuZWNlc3NhcnkuDQoNClsiXHUyNEQwXHUyNERCXHUyNEQ2IiA9ICLik5Dik5vik5Yi
XQ0KDQo+IE1heWJlIGdhdGVrZWVwZXIgZnVuY3Rpb25zIGFyZSBub3Qgc3VjaCBhIGJyaWdodCBp
ZGVhPw0KDQpUaGV5IGFyZSBldmVyeXdoZXJlLiBGaXJld2FsbHMsIHByb3hpZXMsIFdBRnMsIGdh
dGV3YXlzOyBhbnkgdGllcmVkIGFyY2hpdGVjdHVyZS4uLiANCkdhdGV3YXlzIGFyZSBmaW5lLiBQ
b3RlbnRpYWxseSBhbWJpZ3VvdXMgbWVzc2FnZXMgYXJlIHRoZSBpZGVhIHRoYXQgaXMgbm90IHNv
IGJyaWdodC4gDQoNCkl0IGlzIG5vdCBqdXN0ICJpbmxpbmUiIGdhdGV3YXlzLiBZb3UgZG9uJ3Qg
d2FudCB5b3VyIGF1ZGl0IHRvb2wsIG9yIHN1cHBvcnQgdG9vbCwgdGhhdCBtaWdodCBsb29rIGF0
IG1lc3NhZ2VzIGFmdGVyIHRoZXkgaGF2ZSBiZWVuIHByb2Nlc3NlZCB0byBzZWUgYSBkaWZmZXJl
bnQgaW50ZXJwcmV0YXRpb24uIFlvdSBkb24ndCB3YW50IGEgY291cnQgZGlzYWdyZWVpbmcgYWJv
dXQgYSBtZXNzYWdlIHllYXJzIGxhdGVyLg0KDQotLQ0KSmFtZXMgTWFuZ2VyDQo=

From trac+jose@trac.tools.ietf.org  Thu Jun 27 08:25:51 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDD411E80E2 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tahHIXiZZEQP for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:25:50 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 7C51F11E810A for <jose@ietf.org>; Thu, 27 Jun 2013 08:25:46 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48756 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UsE4s-0004zy-Rv; Thu, 27 Jun 2013 17:25:42 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-algorithms@tools.ietf.org, michael.jones@microsoft.com
X-Trac-Project: jose
Date: Thu, 27 Jun 2013 15:25:42 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/jose/trac/ticket/28#comment:1
Message-ID: <069.dc8e817f3443ca8137d8048db4905647@trac.tools.ietf.org>
References: <054.7c33f2d20d536f291cb1402eed2d1710@trac.tools.ietf.org>
X-Trac-Ticket-ID: 28
In-Reply-To: <054.7c33f2d20d536f291cb1402eed2d1710@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-algorithms@tools.ietf.org, michael.jones@microsoft.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20130627152549.7C51F11E810A@ietfa.amsl.com>
Resent-Date: Thu, 27 Jun 2013 08:25:46 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #28: AES-GCM should not be allowed for content encryption in combination with Direct Encryption key management mode
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:25:51 -0000

#28: AES-GCM should not be allowed for content encryption in combination with
Direct Encryption key management mode


Comment (by michael.jones@microsoft.com):

 Thanks for pointing out the NIST text.  Rather than prohibiting the use of
 GCM, a less heavy-handed means of handling this issue would be to include
 text such as the following:

 "NIST SP 800-38D section 8.3 states 'The total number of invocations of
 the authenticated encryption function shall not exceed 2^32, including all
 IV lengths and all instances of the authenticated encryption function with
 the given key.'  In accordance with this rule, AES GCM MUST NOT be used
 with the same direct encryption key more than 2^32 times."

 No we canâ€™t guarantee that applications will always follow this
 requirement, but we canâ€™t guarantee that many other requirements are
 followed either â€“ such as the requirement to use a unique ephemeral key
 when doing key agreement.  Just because incorrect uses are possible
 doesnâ€™t mean that we shouldnâ€™t enable correct uses.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  mpeck@mitre.org        |  algorithms@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  algorithms             |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://tools.ietf.org/wg/jose/trac/ticket/28#comment:1>
jose <http://tools.ietf.org/jose/>


From trac+jose@trac.tools.ietf.org  Thu Jun 27 08:28:49 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB2A21F9DB2 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aZYCXWQSzx4 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:28:48 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A9FD921F9E31 for <jose@ietf.org>; Thu, 27 Jun 2013 08:13:18 -0700 (PDT)
Received: from localhost ([127.0.0.1]:47715 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UsDsm-0000Gg-Ih; Thu, 27 Jun 2013 17:13:12 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-algorithms@tools.ietf.org, mpeck@mitre.org
X-Trac-Project: jose
Date: Thu, 27 Jun 2013 15:13:12 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/jose/trac/ticket/28
Message-ID: <054.7c33f2d20d536f291cb1402eed2d1710@trac.tools.ietf.org>
X-Trac-Ticket-ID: 28
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-algorithms@tools.ietf.org, mpeck@mitre.org, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20130627151321.A9FD921F9E31@ietfa.amsl.com>
Resent-Date: Thu, 27 Jun 2013 08:13:18 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose] #28: AES-GCM should not be allowed for content encryption in combination with Direct Encryption key management mode
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:28:49 -0000

#28: AES-GCM should not be allowed for content encryption in combination with
Direct Encryption key management mode

 Section 4.9 of draft-ietf-jose-json-web-algorithms should prohibit use of
 the A128GCM and A256GCM "enc" content encryption algorithms in combination
 with the Direct Encryption key management mode (when the value of "alg" is
 "dir").

 NIST SP 800-38D section 8.3 states "The total number of invocations of the
 authenticated encryption function shall not exceed 2^32 ,  including all
 IV lengths and all instances of the authenticated encryption function with
 the given key."  There is no way to guarantee compliance with this using
 the Direct Encryption mode.  All of the other modes are OK because they
 generate or derive a fresh CEK for each message.

 Existing RFCs using GCM include requirements for "automated key
 management", for example RFC 4106 Section 2 and RFC 5084.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-jose-json-web-
  mpeck@mitre.org        |  algorithms@tools.ietf.org
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  json-web-    |    Version:
  algorithms             |   Keywords:
 Severity:  -            |
-------------------------+-------------------------------------------------

Ticket URL: <http://tools.ietf.org/wg/jose/trac/ticket/28>
jose <http://tools.ietf.org/jose/>


From tbray@textuality.com  Thu Jun 27 08:33:47 2013
Return-Path: <tbray@textuality.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D43F21F9D9C for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmKE5BroBpsr for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:33:41 -0700 (PDT)
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACB811E80E7 for <jose@ietf.org>; Thu, 27 Jun 2013 08:20:24 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id w15so758598vbf.7 for <jose@ietf.org>; Thu, 27 Jun 2013 08:20:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=z8CuBphhCW+WXFtw8jYuE0WzoLjVIive8ro8UjZEX+k=; b=F+cW/5+zQuFv1ioNYslUahQZpA5WJl4u3KDkydW5EM2BrOyIdhoK/TgwzAFi64lt9O I5bFrNBiRkhuwlQy7ErvZlmlNh9hEAsNuTIMPImyxU6s6XnWrI4RNnyOyl8QENDs6b+Q FWUHeM2jVrmoseOf9L+eGwBc+3dxhhpbfcmR5v/KhAkU1OG+Z84e9jy3gBSJqnEw7NqI UWLgOreUVZM/7NJA1T5KTjw0xiyj5XYy58aVn/fJ97SfSTU3r7IJl6Il1C/C+5zZAKOM ixJkYekqDI6Kz70jX1PsC29cHfkkysWbqWMuY1TLkUkN2OQNTnWXpJ7Fryt5aavvZ2Ne PorQ==
MIME-Version: 1.0
X-Received: by 10.52.69.207 with SMTP id g15mr3022517vdu.108.1372346411693; Thu, 27 Jun 2013 08:20:11 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Thu, 27 Jun 2013 08:20:11 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com>
Date: Thu, 27 Jun 2013 08:20:11 -0700
Message-ID: <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=20cf307f392060cee504e0244cc0
X-Gm-Message-State: ALoCoQlbV8nGu1lj5rirPbpFXousdOQXhqbaWeM47DSq4iIwkUNZNxsNyyWK51vPw/wEje+TQfKT
Cc: Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:33:47 -0000

--20cf307f392060cee504e0244cc0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The approach just seems wrong.  If we require that conforming
implementations MUST NOT emit dupes, then authors of receiving software can
just pick the best-performing parser with the nicest API, because they
*all* perform correctly when there are no dupes.

Who=E2=80=99s going to own the responsibility for making the authoritative =
finding
that of the many JSON parsers in the Java ecosystem, these ones, but not
those ones, are usable in JOSE applications?  And suppose one that has been
previously OK is quietly optimized on GitHub to run 30% faster and as a
side-effect silently ignores dupes?

The benefit of using JSON is that there is widely deployed software to
handle it.  It is a known problem that sloppy spec drafting has allowed
various kinds of problems to occur when dupe keys are received. =E2=80=9CDo=
ctor, it
hurts when I do this.=E2=80=9D =E2=80=9CSo... don=E2=80=99t do that.=E2=80=
=9D

Are we also going to specify the behavior of receiving software when the
JSON has a misplaced quotation mark?  A missing trailing =E2=80=9C}=E2=80=
=9D?

 -T



On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> Most JSON libraries that silently accept [sob] dupe keys at least
> consistently use the last key. Allowing just that behaviour (or rejecting
> dupes), while forbidding acceptance of a non-last dupe (eg first key), is
> safe and allows most JSON libraries to be used. Since this accepts most
> libraries I think it is practical.****
>
> ** **
>
> Hence I suggest:****
>
> ** **
>
> >   A creator of a JOSE message MUST NOT put duplicate names in any JSON*=
*
> **
>
> > object in a JOSE header.****
>
> >   To prevent attacks where a JOSE message is interpreted as different**=
*
> *
>
> > valid messages by different recipients, each recipient MUST either****
>
> > reject messages with duplicate names or accept only the last name.****
>
> ** **
>
> This isn=E2=80=99t =E2=80=9Ctruly predictable=E2=80=9D as a message with =
dupes might be accepted
> or rejected. The crucial point is that if a message is accepted it is
> predictable.****
>
> ** **
>
> --****
>
> James Manger****
>
> ** **
>
> *From:* Tim Bray [mailto:tbray@textuality.com]
> *Sent:* Thursday, 27 June 2013 4:16 PM
> *To:* Manger, James H
> *Cc:* Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
> ** **
>
> Well, you have a practical problem in that most implementers will want to
> use a standard JSON library, which is good practice because it will be
> well-debugged, and most libraries [sob] silently take care of dupe keys a=
nd
> don=E2=80=99t have a way to tell the client software what happened. So if=
 you want
> truly predictable behavior, you=E2=80=99re forcing the use of hand-constr=
ucted JSON
> parsers. And that sucks, because getting good performance in JSON parsing
> is surprisingly hard, with dramatic performance differences between
> implementations. So you=E2=80=99re forcing receiving software which wants=
 to be
> conformant to use a hand-rolled parser which will probably have lousy
> performance and have other bugs which in fact may compromise security mor=
e
> than dupe-key tricks could.  -T****
>
> ** **
>
> On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> > I think it=E2=80=99s a nice clean minimal solution to say that producer=
s MUST
> > NOT generate dupes, end of story.  I don=E2=80=99t think saying anythin=
g beyond
> > that adds value. -T****
>
> Clean and minimal that may be, but it ignores the security issue. We don'=
t
> want a malicious producer (who is so malicious they ignore a MUST) to
> create JOSE messages that a JOSE-compliant security layer accepts as
> "benign interpretation #1" so it passes the message on to the
> JOSE-compliant backend app that acts on "nasty interpretation #2".
>
> --
> James Manger****
>
> ** **
>

--20cf307f392060cee504e0244cc0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>The approach just seems wrong.=C2=A0 If we requi=
re that conforming implementations MUST NOT emit dupes, then authors of rec=
eiving software can just pick the best-performing parser with the nicest AP=
I, because they *all* perform correctly when there are no dupes.=C2=A0 <br>
<br>Who=E2=80=99s going to own the responsibility for making the authoritat=
ive finding that of the many JSON parsers in the Java ecosystem, these ones=
, but not those ones, are usable in JOSE applications?=C2=A0 And suppose on=
e that has been previously OK is quietly optimized on GitHub to run 30% fas=
ter and as a side-effect silently ignores dupes?=C2=A0 <br>
<br></div>The benefit of using JSON is that there is widely deployed softwa=
re to handle it.=C2=A0 It is a known problem that sloppy spec drafting has =
allowed various kinds of problems to occur when dupe keys are received. =E2=
=80=9CDoctor, it hurts when I do this.=E2=80=9D =E2=80=9CSo... don=E2=80=99=
t do that.=E2=80=9D<br>
<br></div><div>Are we also going to specify the behavior of receiving softw=
are when the JSON has a misplaced quotation mark?=C2=A0 A missing trailing =
=E2=80=9C}=E2=80=9D?<br><br></div><div>=C2=A0-T<br></div><div><div><div><di=
v><div><div><br></div>
</div></div></div></div></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" targ=
et=3D"_blank">James.H.Manger@team.telstra.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"=
EN-AU"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Most JSON lib=
raries that silently accept [sob] dupe keys at least consistently use the l=
ast key. Allowing just that behaviour (or rejecting dupes), while forbiddin=
g acceptance of a non-last dupe (eg first key), is safe and allows most JSO=
N libraries to be used. Since this accepts most libraries I think it is pra=
ctical.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hence I suggest:<u>=
</u><u></u></span></p>
<div class=3D"im"><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=
=C2=A0<u></u></span></p><p>&gt; =C2=A0=C2=A0A creator of a JOSE message MUS=
T NOT put duplicate names in any JSON<u></u><u></u></p>
<p>&gt; object in a JOSE header.<u></u><u></u></p><p>&gt; =C2=A0=C2=A0To pr=
event attacks where a JOSE message is interpreted as different<u></u><u></u=
></p><p>&gt; valid messages by different recipients, each recipient MUST ei=
ther<u></u><u></u></p>
<p>&gt; reject messages with duplicate names or accept only the last name.<=
u></u><u></u></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=
=C2=A0<u></u></span></p>
</div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">This isn=E2=80=99t =
=E2=80=9Ctruly predictable=E2=80=9D as a message with dupes might be accept=
ed or rejected. The crucial point is that if a message is accepted it is pr=
edictable.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">--<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">James Manger<u></u><u></u=
></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0=
<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;paddin=
g:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.=
0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">F=
rom:</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;" lang=3D"EN-US"> Tim Bray [mailto:<a href=3D"mail=
to:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</a>] <br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br><b>To:</b> Manger, James H<b=
r><b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" targe=
t=3D"_blank">jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-=
signature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signat=
ure@tools.ietf.org</a></span></p>
<div class=3D"im"><br><b>Subject:</b> Re: [jose] #27: member names MUST be =
unique needs additional text<u></u><u></u></div><p></p></div></div><p class=
=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal">Well, yo=
u have a practical problem in that most implementers will want to use a sta=
ndard JSON library, which is good practice because it will be well-debugged=
, and most libraries [sob] silently take care of dupe keys and don=E2=80=99=
t have a way to tell the client software what happened. So if you want trul=
y predictable behavior, you=E2=80=99re forcing the use of hand-constructed =
JSON parsers. And that sucks, because getting good performance in JSON pars=
ing is surprisingly hard, with dramatic performance differences between imp=
lementations. So you=E2=80=99re forcing receiving software which wants to b=
e conformant to use a hand-rolled parser which will probably have lousy per=
formance and have other bugs which in fact may compromise security more tha=
n dupe-key tricks could.=C2=A0 -T<u></u><u></u></p>
</div><div><div class=3D"h5"><div><p class=3D"MsoNormal" style=3D"margin-bo=
ttom:12.0pt"><u></u>=C2=A0<u></u></p><div><p class=3D"MsoNormal">On Wed, Ju=
n 26, 2013 at 10:39 PM, Manger, James H &lt;<a href=3D"mailto:James.H.Mange=
r@team.telstra.com" target=3D"_blank">James.H.Manger@team.telstra.com</a>&g=
t; wrote:<u></u><u></u></p>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; I think it=
=E2=80=99s a nice clean minimal solution to say that producers MUST<br>&gt;=
 NOT generate dupes, end of story.=C2=A0 I don=E2=80=99t think saying anyth=
ing beyond<br>&gt; that adds value. -T<u></u><u></u></p>
</div><p class=3D"MsoNormal">Clean and minimal that may be, but it ignores =
the security issue. We don&#39;t want a malicious producer (who is so malic=
ious they ignore a MUST) to create JOSE messages that a JOSE-compliant secu=
rity layer accepts as &quot;benign interpretation #1&quot; so it passes the=
 message on to the JOSE-compliant backend app that acts on &quot;nasty inte=
rpretation #2&quot;.<br>
<br>--<br>James Manger<u></u><u></u></p></div><p class=3D"MsoNormal"><u></u=
>=C2=A0<u></u></p></div></div></div></div></div></div></blockquote></div><b=
r></div>

--20cf307f392060cee504e0244cc0--

From mpeck@mitre.org  Thu Jun 27 08:44:13 2013
Return-Path: <mpeck@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346A821F9DC7 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKslHEhlyPsQ for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:43:56 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id DF26B21F9AF1 for <jose@ietf.org>; Thu, 27 Jun 2013 08:43:55 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 918C01F03A7; Thu, 27 Jun 2013 11:43:54 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 7A344226009E; Thu, 27 Jun 2013 11:43:54 -0400 (EDT)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.162]) by IMCCAS01.MITRE.ORG ([129.83.29.68]) with mapi id 14.02.0342.003; Thu, 27 Jun 2013 11:43:54 -0400
From: "Peck, Michael A" <mpeck@mitre.org>
To: Richard Barnes <rlb@ipv.sx>, Mike Jones <Michael.Jones@microsoft.com>
Thread-Topic: [jose] Field Matrix
Thread-Index: Ac5t5xRPeyoH6vXbTWe6CTWcVqhYoAAMmugAAABYzwAAAg9agAFKH59g
Date: Thu, 27 Jun 2013 15:43:53 +0000
Message-ID: <8B4C063947CD794BB6FF90C78BAE9B321F064434@IMCMBX04.MITRE.ORG>
References: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com> <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436787AC69@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTu=LMdH5VEdCsUAs0Ro3qeu_4MZ6viY5QF7axpQmYkZQ@mail.gmail.com>
In-Reply-To: <CAL02cgTu=LMdH5VEdCsUAs0Ro3qeu_4MZ6viY5QF7axpQmYkZQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.83.31.54]
Content-Type: multipart/alternative; boundary="_000_8B4C063947CD794BB6FF90C78BAE9B321F064434IMCMBX04MITREOR_"
MIME-Version: 1.0
Cc: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:44:13 -0000

--_000_8B4C063947CD794BB6FF90C78BAE9B321F064434IMCMBX04MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

"zip" indicates whether the authenticated encryption is applied to Plaintex=
t vs Compress(Plaintext).

By stripping "zip" an attacker could make the message appear to successfull=
y decrypt to Compress(Plaintext) rather than Plaintext?

I suppose whether that could lead to something bad would be implementation =
dependent, but anything that can lead to ambiguity about the contents of th=
e original plaintext doesn't seem like a good idea.

Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Ric=
hard Barnes
Sent: Thursday, June 20, 2013 6:01 PM
To: Mike Jones
Cc: Jim Schaad; jose@ietf.org
Subject: Re: [jose] Field Matrix

There was no such decision.  Quoting directly from the minutes:
"""
**  Crit Text

Two questions were raised for dealing with the cirt field.  Does the crit f=
ield need to be signed and do the members listed in the crit field need to =
be signed.

There was no consensus in the group at this time as we adjourned for the da=
y
"""

In order for the attack you describe to be an actual security risk, it woul=
d need to be the case that the parameters in "crit" were security-critical,=
 as opposed to things that would simply cause incorrect processing.  One ca=
n certainly imagine parameters that would fall in the latter bin; my curren=
t favorite example is a "part" parameter that would allow fragmentation / r=
eassembly.  Because such parameters exist, it's possible to use "crit" safe=
ly without integrity protection.

Can we at least agree that integrity protecting "zip" is unnecessary?  The =
only thing that stripping / changing "zip" causes is a processing failure, =
not a security compromise.

--Richard


On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
There was a working group decision at the Denver meeting that "crit" must b=
e integrity protected.  The reason for this is straightforward.

If not integrity protected, an attacker could strip the "crit" field, defea=
ting the semantic requirement that implementations must reject the input if=
 a "crit" value is used that is not understood.  Thus, the spec requires th=
at this field be integrity protected whenever used.

                                                                -- Mike

From: jose-bounces@ietf.org<mailto:jose-bounces@ietf.org> [mailto:jose-boun=
ces@ietf.org<mailto:jose-bounces@ietf.org>] On Behalf Of Richard Barnes
Sent: Thursday, June 20, 2013 1:52 PM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] Field Matrix

You can eliminate the "protection required" field, because there aren't any=
 of those.

Or there shouldn't be: The only security case we have is algorithm dependen=
t ("alg" must be protected if "alg" =3D=3D "PS256", "PS512").  The only fie=
lds for which the specs currently require integrity protection are "zip" an=
d "crit".  Neither of these have the property that changing them would caus=
e a security violation, except in some application-dependent sense.  So the=
 choice of integrity protection should be left to applications, not fixed i=
n the spec.

--Richard

On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
<no hat>

Having just started looking at a design implementation, I am now more than =
ever interested in seeing this matrix of fields.  At the present time I thi=
nk the following columns are probably of interest:

Name, must understand, use required, common vs specific, protection require=
d

I was just looking at the alg and enc fields for JWE and realized that one =
was specific - so it should be one location - and one was common - so it sh=
ould be in a different location.  And then I needed to start thinking about=
 where it goes in terms of compacted vs one recipient vs two recipients.

Do you have an idea of when this matrix might show up?

Jim




--_000_8B4C063947CD794BB6FF90C78BAE9B321F064434IMCMBX04MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8220;zip&#8221; indicat=
es whether the authenticated encryption is applied to Plaintext vs Compress=
(Plaintext).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">By stripping &#8220;zip&#=
8221; an attacker could make the message appear to successfully decrypt to =
Compress(Plaintext) rather than Plaintext?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I suppose whether that co=
uld lead to something bad would be implementation dependent, but anything t=
hat can lead to ambiguity about the contents of the original
 plaintext doesn&#8217;t seem like a good idea.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Mike<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 6:01 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; jose@ietf.org<br>
<b>Subject:</b> Re: [jose] Field Matrix<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">There was no such decision. &nbsp;Quoting directly f=
rom the minutes:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">** &nbsp;Crit Text<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Two questions were raised for dealing with the cirt =
field. &nbsp;Does the crit field need to be signed and do the members liste=
d in the crit field need to be signed.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There was no consensus in the group at this time as =
we adjourned for the day<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">In order for the attack you describe to be an actual=
 security risk, it would need to be the case that the parameters in &quot;c=
rit&quot; were security-critical, as opposed to things that would simply ca=
use incorrect processing. &nbsp;One can certainly
 imagine parameters that would fall in the latter bin; my current favorite =
example is a &quot;part&quot; parameter that would allow fragmentation / re=
assembly. &nbsp;Because such parameters exist, it's possible to use &quot;c=
rit&quot; safely without integrity protection.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Can we at least agree that integrity protecting &quo=
t;zip&quot; is unnecessary? &nbsp;The only thing that stripping / changing =
&quot;zip&quot; causes is a processing failure, not a security compromise.<=
o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">There was a working group decision at t=
he Denver meeting that &#8220;crit&#8221; must be integrity protected.&nbsp=
;
 The reason for this is straightforward.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If not integrity protected, an attacker=
 could strip the &#8220;crit&#8221; field, defeating the semantic requireme=
nt
 that implementations must reject the input if a &#8220;crit&#8221; value i=
s used that is not understood.&nbsp; Thus, the spec requires that this fiel=
d be integrity protected whenever used.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 1:52 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Field Matrix</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">You can eliminate the &quot;protection required&quot; field, becau=
se there aren't any of those. &nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Or there shouldn't be: The only security case we have is algorithm=
 dependent (&quot;alg&quot; must be protected if &quot;alg&quot; =3D=3D &qu=
ot;PS256&quot;, &quot;PS512&quot;). &nbsp;The only fields for which the spe=
cs currently
 require integrity protection are &quot;zip&quot; and &quot;crit&quot;. &nb=
sp;Neither of these have the property that changing them would cause a secu=
rity violation, except in some application-dependent sense. &nbsp;So the ch=
oice of integrity protection should be left to applications, not
 fixed in the spec.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad &lt;<a href=3D"mailto:=
ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt; wr=
ote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&lt;no hat&gt;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Having just started looking at a design implementation, I am now m=
ore than ever interested in seeing this matrix of fields.&nbsp; At the pres=
ent time I think the following columns are
 probably of interest:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Name, must understand, use required, common vs specific, protectio=
n required<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I was just looking at the alg and enc fields for JWE and realized =
that one was specific &#8211; so it should be one location &#8211; and one =
was common &#8211; so it should be in a different location.&nbsp;
 And then I needed to start thinking about where it goes in terms of compac=
ted vs one recipient vs two recipients.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Do you have an idea of when this matrix might show up?<o:p></o:p><=
/p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">Jim</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#888888">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_8B4C063947CD794BB6FF90C78BAE9B321F064434IMCMBX04MITREOR_--

From ve7jtb@ve7jtb.com  Thu Jun 27 08:49:44 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2105D21F9DEE for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8hdgCHSGQ6o for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 08:49:38 -0700 (PDT)
Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by ietfa.amsl.com (Postfix) with ESMTP id E6BA921F9D92 for <jose@ietf.org>; Thu, 27 Jun 2013 08:49:37 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ci6so2570818qab.18 for <jose@ietf.org>; Thu, 27 Jun 2013 08:49:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=hPSRqvmUkQFxFqly9SGSU8ivXUQQzdmsN2nI+cYQnF8=; b=Rw7gvL5N6TbPy7VHP0uPuxlxKe2rTDP352FNU/puYfYpSzm7lFyPTFF93EIHFjEDkt lCoRFJ82UcdVoBqgTp2vkDj8VmHdB4Yd7M5rEIqch4QE9EpTmclO+hBmfAwJI3NCUzfF XXAEd+mX5aolxB4ilnbE/MO4KJ5I7FR6oGIdzT1K2liw1byQEBcOB+dFeV396QUV7kkS 28h4CSwNN2RT4ALlXKlCLDVXv5AkSFdNYyQO8OGToqG2jU0+LsT7fToygIKWgp7b46d1 ayZsai7rJfjmelt3D9iHiHXXEXYVWDdZOLFHN5p0LguMsDm5X97rdk2RHDAKhB1dZObk fumQ==
X-Received: by 10.224.79.209 with SMTP id q17mr12437043qak.88.1372348177156; Thu, 27 Jun 2013 08:49:37 -0700 (PDT)
Received: from [192.168.1.216] (190-20-7-218.baf.movistar.cl. [190.20.7.218]) by mx.google.com with ESMTPSA id ff5sm4498067qeb.6.2013.06.27.08.49.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 08:49:35 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_17FACC13-7E73-42D9-8A16-9E12D9F82161"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com>
Date: Thu, 27 Jun 2013 11:49:03 -0400
Message-Id: <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQkgg5fPvrCZ1xqz9ih9OUd5I7VnnP1yKdEF/OfaXHsvdDe1VZ7WqhlEmIRVruZBY0RA7MJE
Cc: Mike Jones <Michael.Jones@microsoft.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, Jim Schaad <ietf@augustcellars.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 15:49:44 -0000

--Apple-Mail=_17FACC13-7E73-42D9-8A16-9E12D9F82161
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_ED07A3C7-87CC-41F4-A556-670610EEDB66"


--Apple-Mail=_ED07A3C7-87CC-41F4-A556-670610EEDB66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

The problem is not wanting to leave a hole for malicious signers to =
create JWT that may be misinterpreted by the receiver.  Accidental =
interop problems from bad signers are not a big concern for me and are =
covered by MUST NOT emit dups.

Accepting malformed JSON as the envelope may lead to real security =
issues.

This may be more of an issue for the JSON encoding than the compact as =
there you need to be careful the body you process for the signature is =
the body that the application uses.

What happens if you receive.

{"protected":<integrity-protected shared header contents>",
      "unprotected":<non-integrity-protected shared header contents>",
      "payload":"<original payload contents>",
      "payload":"<bad payload contents inserted by attacker>"
      "signatures":[
       {"header":"<per-signature unprotected header 1 contents>",
        "signature":"<signature 1 contents>"},
       ...
       {"header":"<per-signature unprotected header N contents>",
        "signature":"<signature N contents>"}],
     }

If the JOSE library validates on the first version of "payload" and the =
application using a different JSON parser only sees the second "payload" =
we have a wrapping attack similar to xmldsig.

I can't off the top of my head think of what you could do in the compact =
serialization that would lead to a successful attack given that the =
signature is over the base64url encoded segments, that prevents =
attackers from modifying the JSON while maintaining integrity.

It is a real issue for the JSON serialization though.

John B.

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com> wrote:

> The approach just seems wrong.  If we require that conforming =
implementations MUST NOT emit dupes, then authors of receiving software =
can just pick the best-performing parser with the nicest API, because =
they *all* perform correctly when there are no dupes. =20
>=20
> Who=92s going to own the responsibility for making the authoritative =
finding that of the many JSON parsers in the Java ecosystem, these ones, =
but not those ones, are usable in JOSE applications?  And suppose one =
that has been previously OK is quietly optimized on GitHub to run 30% =
faster and as a side-effect silently ignores dupes? =20
>=20
> The benefit of using JSON is that there is widely deployed software to =
handle it.  It is a known problem that sloppy spec drafting has allowed =
various kinds of problems to occur when dupe keys are received. =93Doctor,=
 it hurts when I do this.=94 =93So... don=92t do that.=94
>=20
> Are we also going to specify the behavior of receiving software when =
the JSON has a misplaced quotation mark?  A missing trailing =93}=94?
>=20
>  -T
>=20
>=20
>=20
> On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H =
<James.H.Manger@team.telstra.com> wrote:
> Most JSON libraries that silently accept [sob] dupe keys at least =
consistently use the last key. Allowing just that behaviour (or =
rejecting dupes), while forbidding acceptance of a non-last dupe (eg =
first key), is safe and allows most JSON libraries to be used. Since =
this accepts most libraries I think it is practical.
>=20
> =20
>=20
> Hence I suggest:
>=20
> =20
>=20
> >   A creator of a JOSE message MUST NOT put duplicate names in any =
JSON
>=20
> > object in a JOSE header.
>=20
> >   To prevent attacks where a JOSE message is interpreted as =
different
>=20
> > valid messages by different recipients, each recipient MUST either
>=20
> > reject messages with duplicate names or accept only the last name.
>=20
> =20
>=20
> This isn=92t =93truly predictable=94 as a message with dupes might be =
accepted or rejected. The crucial point is that if a message is accepted =
it is predictable.
>=20
> =20
>=20
> --
>=20
> James Manger
>=20
> =20
>=20
> From: Tim Bray [mailto:tbray@textuality.com]=20
> Sent: Thursday, 27 June 2013 4:16 PM
> To: Manger, James H
> Cc: Mike Jones; Jim Schaad; jose@ietf.org; =
draft-ietf-jose-json-web-signature@tools.ietf.org
>=20
>=20
> Subject: Re: [jose] #27: member names MUST be unique needs additional =
text
>=20
> =20
>=20
> Well, you have a practical problem in that most implementers will want =
to use a standard JSON library, which is good practice because it will =
be well-debugged, and most libraries [sob] silently take care of dupe =
keys and don=92t have a way to tell the client software what happened. =
So if you want truly predictable behavior, you=92re forcing the use of =
hand-constructed JSON parsers. And that sucks, because getting good =
performance in JSON parsing is surprisingly hard, with dramatic =
performance differences between implementations. So you=92re forcing =
receiving software which wants to be conformant to use a hand-rolled =
parser which will probably have lousy performance and have other bugs =
which in fact may compromise security more than dupe-key tricks could.  =
-T
>=20
> =20
>=20
> On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H =
<James.H.Manger@team.telstra.com> wrote:
>=20
> > I think it=92s a nice clean minimal solution to say that producers =
MUST
> > NOT generate dupes, end of story.  I don=92t think saying anything =
beyond
> > that adds value. -T
>=20
> Clean and minimal that may be, but it ignores the security issue. We =
don't want a malicious producer (who is so malicious they ignore a MUST) =
to create JOSE messages that a JOSE-compliant security layer accepts as =
"benign interpretation #1" so it passes the message on to the =
JOSE-compliant backend app that acts on "nasty interpretation #2".
>=20
> --
> James Manger
>=20
> =20
>=20
>=20


--Apple-Mail=_ED07A3C7-87CC-41F4-A556-670610EEDB66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The =
problem is not wanting to leave a hole for malicious signers to create =
JWT that may be misinterpreted by the receiver. &nbsp;Accidental interop =
problems from bad signers are not a big concern for me and are covered =
by MUST NOT emit dups.<div><br></div><div>Accepting malformed JSON as =
the envelope may lead to real security =
issues.</div><div><br></div><div>This may be more of an issue for the =
JSON encoding than the compact as there you need to be careful the body =
you process for the signature is the body that the application =
uses.</div><div><br></div><div>What happens if you =
receive.</div><div><br></div><div><pre class=3D"newpage" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; =
page-break-before: always; ">{"protected":&lt;integrity-protected shared =
header contents&gt;",
      "unprotected":&lt;non-integrity-protected shared header =
contents&gt;",
      "payload":"&lt;original payload contents&gt;",</pre><pre =
class=3D"newpage" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always; "><pre class=3D"newpage" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; =
page-break-before: always; ">      "payload":"&lt;bad payload contents =
inserted by attacker&gt;"</pre>      "signatures":[
       {"header":"&lt;per-signature unprotected header 1 contents&gt;",
        "signature":"&lt;signature 1 contents&gt;"},
       ...
       {"header":"&lt;per-signature unprotected header N contents&gt;",
        "signature":"&lt;signature N contents&gt;"}],
     }</pre><div><br></div><div>If the JOSE library validates on the =
first version of "payload" and the application using a different JSON =
parser only sees the second "payload" we have a wrapping attack similar =
to xmldsig.</div><div><br></div><div>I can't off the top of my head =
think of what you could do in the compact serialization that would lead =
to a successful attack given that the signature is over the base64url =
encoded segments, that prevents attackers from modifying the JSON while =
maintaining integrity.</div><div><br></div><div>It is a real issue for =
the JSON serialization though.</div><div><br></div><div>John =
B.</div><div><br></div><div><div>On 2013-06-27, at 11:20 AM, Tim Bray =
&lt;<a href=3D"mailto:tbray@textuality.com">tbray@textuality.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div><div>The approach just seems =
wrong.&nbsp; If we require that conforming implementations MUST NOT emit =
dupes, then authors of receiving software can just pick the =
best-performing parser with the nicest API, because they *all* perform =
correctly when there are no dupes.&nbsp; <br>
<br>Who=92s going to own the responsibility for making the authoritative =
finding that of the many JSON parsers in the Java ecosystem, these ones, =
but not those ones, are usable in JOSE applications?&nbsp; And suppose =
one that has been previously OK is quietly optimized on GitHub to run =
30% faster and as a side-effect silently ignores dupes?&nbsp; <br>
<br></div>The benefit of using JSON is that there is widely deployed =
software to handle it.&nbsp; It is a known problem that sloppy spec =
drafting has allowed various kinds of problems to occur when dupe keys =
are received. =93Doctor, it hurts when I do this.=94 =93So... don=92t do =
that.=94<br>
<br></div><div>Are we also going to specify the behavior of receiving =
software when the JSON has a misplaced quotation mark?&nbsp; A missing =
trailing =93}=94?<br><br></div><div>&nbsp;-T<br></div><div><div><br></div>=

</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H =
<span dir=3D"ltr">&lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" =
vlink=3D"purple" lang=3D"EN-AU"><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">Most JSON libraries that silently accept [sob] =
dupe keys at least consistently use the last key. Allowing just that =
behaviour (or rejecting dupes), while forbidding acceptance of a =
non-last dupe (eg first key), is safe and allows most JSON libraries to =
be used. Since this accepts most libraries I think it is =
practical.<u></u><u></u></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">Hence I suggest:<u></u><u></u></span></p>
<div class=3D"im"><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p>&gt; =
&nbsp;&nbsp;A creator of a JOSE message MUST NOT put duplicate names in =
any JSON<u></u><u></u></p><p>&gt; object in a JOSE =
header.<u></u><u></u></p><p>&gt; &nbsp;&nbsp;To prevent attacks where a =
JOSE message is interpreted as different<u></u><u></u></p><p>&gt; valid =
messages by different recipients, each recipient MUST =
either<u></u><u></u></p><p>&gt; reject messages with duplicate names or =
accept only the last name.<u></u><u></u></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">This isn=92t =93truly predictable=94 as a message =
with dupes might be accepted or rejected. The crucial point is that if a =
message is accepted it is predictable.<u></u><u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">--<u></u><u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d">James Manger<u></u><u></u></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:#1f497d"><u></u>&nbsp;<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm =
0cm 4.0pt"><div><div style=3D"border:none;border-top:solid #b5c4df =
1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;" lang=3D"EN-US">From:</span></b><span =
style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&=
quot;" lang=3D"EN-US"> Tim Bray [mailto:<a =
href=3D"mailto:tbray@textuality.com" =
target=3D"_blank">tbray@textuality.com</a>] <br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br><b>To:</b> Manger, James =
H<br><b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-signature@tools.ietf.org</a></s=
pan></p>
<div class=3D"im"><br><b>Subject:</b> Re: [jose] #27: member names MUST =
be unique needs additional text<u></u><u></u></div><div><br =
class=3D"webkit-block-placeholder"></div></div></div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p><div><p =
class=3D"MsoNormal">Well, you have a practical problem in that most =
implementers will want to use a standard JSON library, which is good =
practice because it will be well-debugged, and most libraries [sob] =
silently take care of dupe keys and don=92t have a way to tell the =
client software what happened. So if you want truly predictable =
behavior, you=92re forcing the use of hand-constructed JSON parsers. And =
that sucks, because getting good performance in JSON parsing is =
surprisingly hard, with dramatic performance differences between =
implementations. So you=92re forcing receiving software which wants to =
be conformant to use a hand-rolled parser which will probably have lousy =
performance and have other bugs which in fact may compromise security =
more than dupe-key tricks could.&nbsp; -T<u></u><u></u></p>
</div><div><div class=3D"h5"><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><u></u>&nbsp;<u></u></p><div><p =
class=3D"MsoNormal">On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H =
&lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; =
wrote:<u></u><u></u></p>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt; I think =
it=92s a nice clean minimal solution to say that producers MUST<br>&gt; =
NOT generate dupes, end of story.&nbsp; I don=92t think saying anything =
beyond<br>&gt; that adds value. -T<u></u><u></u></p>
</div><p class=3D"MsoNormal">Clean and minimal that may be, but it =
ignores the security issue. We don't want a malicious producer (who is =
so malicious they ignore a MUST) to create JOSE messages that a =
JOSE-compliant security layer accepts as "benign interpretation #1" so =
it passes the message on to the JOSE-compliant backend app that acts on =
"nasty interpretation #2".<br>
<br>--<br>James Manger<u></u><u></u></p></div><p =
class=3D"MsoNormal"><u></u>&nbsp;<u></u></p></div></div></div></div></bloc=
kquote></div><br></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail=_ED07A3C7-87CC-41F4-A556-670610EEDB66--

--Apple-Mail=_17FACC13-7E73-42D9-8A16-9E12D9F82161
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI3MTU0OTA1WjAjBgkqhkiG9w0BCQQxFgQU/dav0Qs7
Uubue4FnK+NB5wBlXrgwgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAaBzb+MGCBBPveXktC+ueHC2c2dijZgkqb/5ukVlQ
mQ37WP8isSBvQJX3EFN65BmnKlgLrjugw5Z1baFNmADW+b0CW6Syg2rz2TK+GVCJUEhe86KaJWvl
VUgCrLSLucrZzSVfIRO2DmIUTXfU+5Ogs0d3FvfJ+RkPWft3+goItBnhnX60QHKnmqJgIEl25WNH
mSsDDNZqS9laIeBqz+J6yMriEyMqnwi8zmKYShuVBoJ1SkIkTDjHfcpPy/1OuUhorngs4274iDwx
dLzn0ptMxBkCzKd5sd7pmYi0kkJs0e/DXVL+giRFI9FbK0BTAn56kK0Be1WLH84i4wOVlUAWSAAA
AAAAAA==

--Apple-Mail=_17FACC13-7E73-42D9-8A16-9E12D9F82161--

From ietf@augustcellars.com  Thu Jun 27 09:34:19 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF11521F9E28 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8cD6UTRmcGoc for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:34:15 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 0100921F9E15 for <jose@ietf.org>; Thu, 27 Jun 2013 09:34:14 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 3F5E338F20; Thu, 27 Jun 2013 09:34:13 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'John Bradley'" <ve7jtb@ve7jtb.com>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org> <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org> <03a601ce72c7$6eb58010$4c208030$@augustcellars.com> <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com>
In-Reply-To: <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com>
Date: Thu, 27 Jun 2013 09:33:17 -0700
Message-ID: <048e01ce7354$07537480$15fa5d80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHKld+pXydVGMxINHz+GIm2S6VogAHtViClAgJhV54COfI4kJkgJ9yg
Content-Language: en-us
Cc: jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:34:19 -0000

I agree that forcing the application layer to figure out where and what the
detached content is makes compete sense.  This would be true if we did
detached signatures or indirect content hashing.

For indirect content hashing I think we would need to define the following:

1.  An object structure
2. A media type for that structure
3. How to do an array of references (it is possible that we would just only
allow one but I don't know that this makes sense)
4. A member for a hash value
5. A member for a hash algorithm
6. A set of hash functions with the appropriate registration
7. A member name for a content identifier in the event that we allow
multiple references (optional element)

I also think it would make sense to evaluate two sets of rules for
evaluation that an application can just reference

All or nothing - all of the contents need to be found and evaluated for the
signature to be considered to be valid
Optional checking - the contents are checked independently from the
signature processing.  Hash values are checked when and as needed.



> -----Original Message-----
> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
> Sent: Wednesday, June 26, 2013 6:20 PM
> To: Jim Schaad
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
> Subject: Re: [jose] #25: Detached content for the ALTO use case
> 
> The problem is describing the detached thing in a way that will allow for
> correct verification.
> SOAP has a number of interesting things that can happen by getting the
> receiver to verify one header part but use another for processing.
> XMLdsig wrapping attacks exist and are to some minds related to detached
> signatures.
> 
> In Connect the claim defines exactly how to find the detached body.
> 
> Leaving it to the application layer to define where the detached body is
to be
> located is not unreasonable.
> 
> How are you thinking of doing that in a generic and secure enough way to
be
> useful in JWS itself?
> 
> The signature itself is not really the hard part.
> 
> As an example of a detached body that might be useful to look at is
signing a
> HTTP request for OAuth and including the JWS in a header.  How in a
generic
> JWS way would you describe how to assemble the body to be hashed?
> 
> In principal I see lats of uses at the application layer for sending a
hash of
> something in a JWS where the application layer describes how to assemble
> some custom content for hashing, but I have a hard time seeing that happen
in
> a interoperable way in JWS.   I could be wrong and am interested in
concrete
> proposals.
> 
> John B.
> 
> On 2013-06-26, at 7:46 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:
> 
> > I completely disagree with your characterization that detached
signatures
> was either a complicated feature or that it caused interop problems.  The
> problems that I always had with XMLDSig were XML problems and had nothing
> to do with the question of detached or non-detached, canonizied or non-
> canonicized.  The problem was always that XML itself was not a good thing
to
> try and produce a usable and reproducible octet stream for the purposes of
> hashing.  If you just processed it as a binary stream in a disk file then
there
> were no problems (assuming that you had not re-written it in some way).
> >
> > I also disagree that it would be any easier to do a detached signature
using
> an indirect rather than direct form.  If you are worried about having
things
> change because it is a detached content, then it makes no difference if
that
> detached content is either directly or indirectly reference.  I don't
think that
> going to an indirect form fixes this problem in any way.
> >
> > Finally, if we are going to say this is the way to do things, we need to
define a
> way to do this in the JOSE drafts themselves.  This would expected to be a
> standard technique that is used by a number of different systems.  It
should
> therefore be a common method for doing it because otherwise you get many
> different ways of doing it that are designed by non-security people and
> therefore prone to error.
> >
> >
> >> -----Original Message-----
> >> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> >> jose issue tracker
> >> Sent: Tuesday, June 25, 2013 5:08 PM
> >> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> >> michael.jones@microsoft.com
> >> Cc: jose@ietf.org
> >> Subject: Re: [jose] #25: Detached content for the ALTO use case
> >>
> >> #25: Detached content for the ALTO use case
> >>
> >>
> >> Comment (by michael.jones@microsoft.com):
> >>
> >> Detached signatures was one of the complicated features of XMLDSIG that
> >> caused substantial interop problems.  I d thought that there was
already
> >> substantial sentiment in the working group not to do this because of
the
> high
> >> complexity/benefit ratio.
> >>
> >> The good news, however, is that a form of detached signatures is EASY
to
> >> build one layer up the stack by signing a hash of the detached content.
> >> ALTO could easily do this.
> >>
> >> There s already a deployed example of this, in fact.  OpenID Connect
> >> includes a hash of the OAuth Access Token as a claim in the ID Token
> issued
> >> with it.  This allows the holder of the ID Token to verify that  token
> substitution
> >> of a different Access Token value has not been  performed by an
attacker.
> >> This works with JWS as it is today.
> >>
> >> I therefore suggest that we recommend this technique to ALTO and add a
> >> description of it in the ALTO section of the Use Cases document and
close
> this
> >> issue as  won t fix .
> >>
> >> --
> >>
-------------------------+----------------------------------------------
> >> -------------------------+---
> >> Reporter:               |       Owner:  draft-ietf-jose-json-web-
> >> ietf@augustcellars.com |  signature@tools.ietf.org
> >>    Type:  defect       |      Status:  new
> >> Priority:  major        |   Milestone:
> >> Component:  json-web-    |     Version:
> >> signature              |  Resolution:
> >> Severity:  -            |
> >> Keywords:               |
> >>
-------------------------+----------------------------------------------
> >> -------------------------+---
> >>
> >> Ticket URL:
<http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
> >> jose <http://tools.ietf.org/jose/>
> >>
> >> _______________________________________________
> >> jose mailing list
> >> jose@ietf.org
> >> https://www.ietf.org/mailman/listinfo/jose
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose



From ietf@augustcellars.com  Thu Jun 27 09:42:00 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0145B21F9E52 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2DVxOSy+DEr4 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:41:54 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1F18621F9E4B for <jose@ietf.org>; Thu, 27 Jun 2013 09:41:54 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id E96AB2C9E7; Thu, 27 Jun 2013 09:41:53 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'n-sakimura'" <n-sakimura@nri.co.jp>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp>
In-Reply-To: <51CBA981.4050006@nri.co.jp>
Date: Thu, 27 Jun 2013 09:40:57 -0700
Message-ID: <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbtMM0AVMbmndwUUG6vntocHGkoALWvDclApUnp/sBuDIBRpn2Hglg
Content-Language: en-us
Cc: michael.jones@microsoft.com, jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:42:00 -0000

Nat,

The only thing that can be signed or encrypted is an octet string. (A =
slight over generalization. GOST for example hashes an integer, tree =
hashes can do strange things but a sufficiently true statement for our =
purposes.)

A that being said - yes case 1 would be something you can do.  Case #2 =
would not be something that you can do because it is not an octet =
string.

If you are looking at JavaScript, in order to hash something as an octet =
string it can be one of three things.  A UInt8Array, an Int8Array and, =
due to convention, a string where the top byte of all of the code points =
in the string is zero.

We currently don't have an efficient way to encode the Uint8Array case, =
although that might not be true if we are looking at new ECMA =
specifications which apparently are adding more defined types and =
serialization methods for those types.

> -----Original Message-----
> From: n-sakimura [mailto:n-sakimura@nri.co.jp]
> Sent: Wednesday, June 26, 2013 7:55 PM
> To: Jim Schaad
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org;
> michael.jones@microsoft.com; jose@ietf.org
> Subject: Re: [jose] #26: Allow for signature payload to not be base64 =
encoded
>=20
> Let me understand the problem.
>=20
> Are you suggesting that we should be able to do something like:
>=20
> Case 1:
>=20
>       {"protected":<integrity-protected shared header contents>",
>        "unprotected":<non-integrity-protected shared header =
contents>",
>        "payload":"this is a multi\nline text payload of which a line =
can be very
> very very long and wrapped during transmission. "
>        "signatures":[
>         {"header":"<per-signature unprotected header 1 contents>",
>          "signature":"<signature 1 contents>"},
>         ...
>         {"header":"<per-signature unprotected header N contents>",
>          "signature":"<signature N contents>"}],
>       }
>=20
> or even
>=20
> Case 2:
>=20
>       {"protected":<integrity-protected shared header contents>",
>        "unprotected":<non-integrity-protected shared header =
contents>",
>        "payload":{
> 	"this":"is a json",
> 	"payload":"which is not base64url encoded"
>        }
>        "signatures":[
>         {"header":"<per-signature unprotected header 1 contents>",
>          "signature":"<signature 1 contents>"},
>         ...
>         {"header":"<per-signature unprotected header N contents>",
>          "signature":"<signature N contents>"}],
>       }
>=20
> Then, I am worried about allowing them because in general we would not
> know what would a transmission mechanism and user agents (including =
text
> editors) would do to them, like Mike mentioned. I do not think we =
should
> assume the property of the transmission mechanism in JOSE level.
> Assuming that would cause brittleness in the implementations.
>=20
> For detached signature, I do not understand why you would want non-
> base64url encoded payload. The application should define how to hash =
the
> octet stream that it wants to calculate signature over it, and we can =
just
> include the base64url encoded hash in the "payload".
> Why would you like to do other encoding for the hash?

If I am not transporting the base64url encoded content, because it is =
not in the "payload" field, then why should I need to base64 encode it =
just to validate the signature.  This is the alto case.

Jim

>=20
> --
> Nat Sakimura (n-sakimura@nri.co.jp)
> Nomura Research Institute
>=20
> PLEASE READ:
> The information contained in this e-mail is confidential and intended =
for the
> named recipient(s) only.
> If you are not an intended recipient of this e-mail, you are hereby =
notified
> that any review, dissemination, distribution or duplication of this =
message is
> strictly prohibited. If you have received this message in error, =
please notify
> the sender immediately and delete your copy from your system.


From Michael.Jones@microsoft.com  Thu Jun 27 09:43:13 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E5321F9D2B for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kJrG6Ej09hC for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:43:04 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]) by ietfa.amsl.com (Postfix) with ESMTP id 1876B21F9A7E for <jose@ietf.org>; Thu, 27 Jun 2013 09:42:51 -0700 (PDT)
Received: from BY2FFO11FD019.protection.gbl (10.1.15.201) by BY2FFO11HUB037.protection.gbl (10.1.14.120) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 27 Jun 2013 16:42:42 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD019.mail.protection.outlook.com (10.1.14.107) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 16:42:42 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 16:42:33 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: John Bradley <ve7jtb@ve7jtb.com>, Tim Bray <tbray@textuality.com>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkIAAhRqAgAAMGPCAABbogIAABEiAgAAKPgCAAAP6AIAAlCSAgAAIEICAAAw40A==
Date: Thu, 27 Jun 2013 16:42:33 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com>
In-Reply-To: <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A009CTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(377424004)(24454002)(43544003)(199002)(189002)(15202345003)(59766001)(74876001)(69226001)(50986001)(512954002)(54316002)(49866001)(63696002)(6806003)(74706001)(56816003)(71186001)(76786001)(80022001)(81542001)(74366001)(56776001)(54356001)(74502001)(77982001)(81342001)(20776003)(55846006)(19300405004)(76482001)(79102001)(76796001)(51856001)(31966008)(74662001)(47446002)(77096001)(46102001)(47976001)(33656001)(47736001)(44976004)(65816001)(66066001)(16236675002)(16406001)(4396001)(53806001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB037; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: Jim Schaad <ietf@augustcellars.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "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] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:43:13 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A009CTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've come to believe that James' proposed language does a good job of makin=
g security-appropriate restrictions while allowing the use of existing pars=
ers.  It was:

A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST ei=
ther reject messages with duplicate names or accept only the last name.

I might change "or accept only the last name" to "or use a parser that alwa=
ys uses the lexically last name for any duplicate member names, per [ECMASc=
ript]" for clarity, but the intent is the same.

Would that work for people?

                                                            -- Mike

From: John Bradley [mailto:ve7jtb@ve7jtb.com]
Sent: Thursday, June 27, 2013 8:49 AM
To: Tim Bray
Cc: Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org; draft-ietf-jose=
-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text

The problem is not wanting to leave a hole for malicious signers to create =
JWT that may be misinterpreted by the receiver.  Accidental interop problem=
s from bad signers are not a big concern for me and are covered by MUST NOT=
 emit dups.

Accepting malformed JSON as the envelope may lead to real security issues.

This may be more of an issue for the JSON encoding than the compact as ther=
e you need to be careful the body you process for the signature is the body=
 that the application uses.

What happens if you receive.


{"protected":<integrity-protected shared header contents>",

      "unprotected":<non-integrity-protected shared header contents>",

      "payload":"<original payload contents>",

      "payload":"<bad payload contents inserted by attacker>"

      "signatures":[

       {"header":"<per-signature unprotected header 1 contents>",

        "signature":"<signature 1 contents>"},

       ...

       {"header":"<per-signature unprotected header N contents>",

        "signature":"<signature N contents>"}],

     }

If the JOSE library validates on the first version of "payload" and the app=
lication using a different JSON parser only sees the second "payload" we ha=
ve a wrapping attack similar to xmldsig.

I can't off the top of my head think of what you could do in the compact se=
rialization that would lead to a successful attack given that the signature=
 is over the base64url encoded segments, that prevents attackers from modif=
ying the JSON while maintaining integrity.

It is a real issue for the JSON serialization though.

John B.

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com<mailto:tbray@tex=
tuality.com>> wrote:


The approach just seems wrong.  If we require that conforming implementatio=
ns MUST NOT emit dupes, then authors of receiving software can just pick th=
e best-performing parser with the nicest API, because they *all* perform co=
rrectly when there are no dupes.

Who's going to own the responsibility for making the authoritative finding =
that of the many JSON parsers in the Java ecosystem, these ones, but not th=
ose ones, are usable in JOSE applications?  And suppose one that has been p=
reviously OK is quietly optimized on GitHub to run 30% faster and as a side=
-effect silently ignores dupes?
The benefit of using JSON is that there is widely deployed software to hand=
le it.  It is a known problem that sloppy spec drafting has allowed various=
 kinds of problems to occur when dupe keys are received. "Doctor, it hurts =
when I do this." "So... don't do that."
Are we also going to specify the behavior of receiving software when the JS=
ON has a misplaced quotation mark?  A missing trailing "}"?
 -T


On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
Most JSON libraries that silently accept [sob] dupe keys at least consisten=
tly use the last key. Allowing just that behaviour (or rejecting dupes), wh=
ile forbidding acceptance of a non-last dupe (eg first key), is safe and al=
lows most JSON libraries to be used. Since this accepts most libraries I th=
ink it is practical.

Hence I suggest:


>   A creator of a JOSE message MUST NOT put duplicate names in any JSON

> object in a JOSE header.

>   To prevent attacks where a JOSE message is interpreted as different

> valid messages by different recipients, each recipient MUST either

> reject messages with duplicate names or accept only the last name.

This isn't "truly predictable" as a message with dupes might be accepted or=
 rejected. The crucial point is that if a message is accepted it is predict=
able.

--
James Manger

From: Tim Bray [mailto:tbray@textuality.com<mailto:tbray@textuality.com>]
Sent: Thursday, 27 June 2013 4:16 PM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; draft-ietf=
-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-jose-json-web-sig=
nature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text


Well, you have a practical problem in that most implementers will want to u=
se a standard JSON library, which is good practice because it will be well-=
debugged, and most libraries [sob] silently take care of dupe keys and don'=
t have a way to tell the client software what happened. So if you want trul=
y predictable behavior, you're forcing the use of hand-constructed JSON par=
sers. And that sucks, because getting good performance in JSON parsing is s=
urprisingly hard, with dramatic performance differences between implementat=
ions. So you're forcing receiving software which wants to be conformant to =
use a hand-rolled parser which will probably have lousy performance and hav=
e other bugs which in fact may compromise security more than dupe-key trick=
s could.  -T

On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
> I think it's a nice clean minimal solution to say that producers MUST
> NOT generate dupes, end of story.  I don't think saying anything beyond
> that adds value. -T
Clean and minimal that may be, but it ignores the security issue. We don't =
want a malicious producer (who is so malicious they ignore a MUST) to creat=
e JOSE messages that a JOSE-compliant security layer accepts as "benign int=
erpretation #1" so it passes the message on to the JOSE-compliant backend a=
pp that acts on "nasty interpretation #2".

--
James Manger




--_000_4E1F6AAD24975D4BA5B1680429673943678A009CTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;ve come to believ=
e that James&#8217; proposed language does a good job of making security-ap=
propriate restrictions while allowing the use of existing parsers.&nbsp;
 It was:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><span style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D=
">A creator of a JOSE message MUST NOT put duplicate names in any JSON obje=
ct in a JOSE header.&nbsp; To prevent attacks where a JOSE message
 is interpreted as different valid messages by different recipients, each r=
ecipient MUST either reject messages with duplicate names or accept only th=
e last name.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I might change &#8220;or =
accept only the last name&#8221; to &#8220;or use a parser that always uses=
 the lexically last name for any duplicate member names, per [ECMAScript]&#=
8221;
 for clarity, but the intent is the same.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Would that work for peopl=
e?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bra=
dley [mailto:ve7jtb@ve7jtb.com]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org; draft-ie=
tf-jose-json-web-signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The problem is not wanting to leave a hole for malic=
ious signers to create JWT that may be misinterpreted by the receiver. &nbs=
p;Accidental interop problems from bad signers are not a big concern for me=
 and are covered by MUST NOT emit dups.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Accepting malformed JSON as the envelope may lead to=
 real security issues.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This may be more of an issue for the JSON encoding t=
han the compact as there you need to be careful the body you process for th=
e signature is the body that the application uses.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">What happens if you receive.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">{&=
quot;protected&quot;:&lt;integrity-protected shared header contents&gt;&quo=
t;,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;unprotected&quot;:&lt;non-integrity-prot=
ected shared header contents&gt;&quot;,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;payload&quot;:&quot;&lt;original payload=
 contents&gt;&quot;,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;payload&quot;:&quot;&lt;bad payload cont=
ents inserted by attacker&gt;&quot;<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;signatures&quot;:[<o:p></o:p></span></pr=
e>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {&quot;header&quot;:&quot;&lt;per-signat=
ure unprotected header 1 contents&gt;&quot;,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;signature&quot;:&quot;&lt;si=
gnature 1 contents&gt;&quot;},<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {&quot;header&quot;:&quot;&lt;per-signat=
ure unprotected header N contents&gt;&quot;,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;signature&quot;:&quot;&lt;si=
gnature N contents&gt;&quot;}],<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt">&n=
bsp;&nbsp;&nbsp;&nbsp; }<o:p></o:p></span></pre>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the JOSE library validates on the first version o=
f &quot;payload&quot; and the application using a different JSON parser onl=
y sees the second &quot;payload&quot; we have a wrapping attack similar to =
xmldsig.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I can't off the top of my head think of what you cou=
ld do in the compact serialization that would lead to a successful attack g=
iven that the signature is over the base64url encoded segments, that preven=
ts attackers from modifying the JSON
 while maintaining integrity.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">It is a real issue for the JSON serialization though=
.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">John B.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"=
mailto:tbray@textuality.com">tbray@textuality.com</a>&gt; wrote:<o:p></o:p>=
</p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The approach just see=
ms wrong.&nbsp; If we require that conforming implementations MUST NOT emit=
 dupes, then authors of receiving software can just pick the best-performin=
g parser with the nicest API, because they
 *all* perform correctly when there are no dupes.&nbsp; <br>
<br>
Who&#8217;s going to own the responsibility for making the authoritative fi=
nding that of the many JSON parsers in the Java ecosystem, these ones, but =
not those ones, are usable in JOSE applications?&nbsp; And suppose one that=
 has been previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?&n=
bsp; <o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The benefit of using =
JSON is that there is widely deployed software to handle it.&nbsp; It is a =
known problem that sloppy spec drafting has allowed various kinds of proble=
ms to occur when dupe keys are received.
 &#8220;Doctor, it hurts when I do this.&#8221; &#8220;So... don&#8217;t do=
 that.&#8221;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Are we also going to =
specify the behavior of receiving software when the JSON has a misplaced qu=
otation mark?&nbsp; A missing trailing &#8220;}&#8221;?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;-T<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &l=
t;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">Jame=
s.H.Manger@team.telstra.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Most JSON libraries that=
 silently accept [sob] dupe keys at least consistently use the
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><span lang=3D"EN-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"EN-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hence I suggest:</span><=
span lang=3D"EN-AU"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"EN-AU"><o:p></o:p></span></p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;A creator of a JOSE message MUST N=
OT put duplicate names in any JSON<o:p></o:p></span></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.<o:p></o:p></span></p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;To prevent attacks where a JOSE me=
ssage is interpreted as different<o:p></o:p></span></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either<o:p></o:p></span></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"EN-AU"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">This isn&#8217;t &#8220;=
truly predictable&#8221; as a message with dupes might be accepted or rejec=
ted.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><span lang=3D"EN-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"EN-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">--</span><span lang=3D"E=
N-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">James Manger</span><span=
 lang=3D"EN-AU"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span lang=
=3D"EN-AU"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray [mailto:<a hr=
ef=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</=
a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><span lang=3D"E=
N-AU"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Well, you have a practical problem in that mo=
st implementers will want to use a standard JSON library, which is good pra=
ctice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don&#8217;t h=
ave a way to tell the client software what happened. So if you want truly p=
redictable behavior, you&#8217;re forcing the use of hand-constructed JSON =
parsers. And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you&#8217;re forcing receiving so=
ftware which wants to be conformant to use a hand-rolled parser which will =
probably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.&nbsp; -T<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&nbsp;<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 PM, Manger, Jam=
es H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blan=
k">James.H.Manger@team.telstra.com</a>&gt; wrote:<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&gt; I think it&#8217;s a nice clean minimal soluti=
on to say that producers MUST<br>
&gt; NOT generate dupes, end of story.&nbsp; I don&#8217;t think saying any=
thing beyond<br>
&gt; that adds value. -T<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Clean and minimal that may be, but it ignores=
 the security issue. We don't want a malicious producer (who is so maliciou=
s they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A009CTK5EX14MBXC283r_--

From ietf@augustcellars.com  Thu Jun 27 09:43:31 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B35F21F9E4C for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[AWL=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tN3ZPw0ywKm for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:43:26 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id EDDF221F9E02 for <jose@ietf.org>; Thu, 27 Jun 2013 09:43:25 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 765A02CA36; Thu, 27 Jun 2013 09:43:25 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <4E1F6AAD24975D4BA5B168042967394367898761@TK5EX14MBXC283.redmond.corp.microsoft.com> <034101ce729b$27473b00$75d5b100$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B458@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b901ce72e5$01248190$036d84b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D481@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789D481@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 09:42:27 -0700
Message-ID: <049001ce7355$50859830$f190c890$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0491_01CE731A.A42A42A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH9pEpqg6SA+ykRJHySAR3RzJ5mhAI1BH/RAavUVGUCJpyCOQN1jVsImJ95yjA=
Content-Language: en-us
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:43:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0491_01CE731A.A42A42A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

That is not the experience that we have seen with TLS.  In this case people
want to constantly register the entire matrix of items.  I would not expect
that desire to change.

 

Jim

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Wednesday, June 26, 2013 9:01 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

For my part, I consider the fact that people will need to register specific
algorithm combinations that they actually need to be a feature - not a bug.
The smaller the set of algorithm combinations registered, the more likely
that they will be implemented and will interoperate.  Trying to claim that
we support the combinatorial explosion of mask generation functions, hash
functions, key derivation functions, key wrapping functions, etc. that are
possible will almost certainly result in less interoperability and more
developer confusion than a small set of registered choices, carefully
considered.  I'm glad to have people consider these criteria in their
evaluation of the two choices.

 

 
-- Mike

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Wednesday, June 26, 2013 8:18 PM
To: Mike Jones; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

My point was that there were some issues that your draft did not fully
address that need to be evaluated as part of your proposal not that these
algorithms would need to be added.  The n x m addition of algorithms to the
registry is an issue that is there for your draft that is not present for
Richard's draft and therefore needs to be considered in the arguments.

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Wednesday, June 26, 2013 12:22 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

Yes, we could also propose algorithm combinations for key agreement followed
GCM key wrapping but I didn't think that was an ask from the working group.
The Denver minutes just recorded my action item as "key wrap draft for
AES-GCM-keywrap", so that's what I did.  We could have a discussion on
Monday's call and on the list about whether the working group is also
interested in other algorithms.

 

Remember, the beauty of having the algorithms registry is that algorithms
can be added "just in time" - as actual need for them is demonstrated.  We
don't have to register all conceivable algorithm combinations up front for
the JWE/JWA specs to be complete.

 

As for how the AEAD parameters are handled I used a parameter encoding that
doesn't result in double base64url encoding anything.  I could have instead
introduced separate "iv" and "tag" header parameter values, but didn't do so
for that reason.  But if people would prefer that approach because it's more
parallel to the use of GCM for plaintext encryption, I have no problem with
that.

 

I do believe that the objective of my draft was met - demonstrating that
AEAD key wrapping can be easily done with the current drafts.  The details
of how the algorithm parameters are encoded is secondary to that and
algorithm-specific; several reasonable choices are possible within the
current JWE framework - one of which was described in my draft.

 

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Wednesday, June 26, 2013 11:30 AM
To: Mike Jones; jose@ietf.org
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

<no hat>

<sarcasm level="heavy">

 

I am shocked that you would possibly support this proposal.  It provides for
two ways of dealing with something.  It is my understanding that you never
support anything that has two ways of doing something.

 

How the AEAD algorithm parameters is handled completely differently for this
proposal and for the same algorithms being used in a CEK context.  This is
going to lead to confusion.

 

</sarcasm>

 

Your specification is missing some items that still need to be registered
Thus you also need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined
in your document as well.

 

Your document ends up with a registration complexity that needs to be
thought about and dealt with as well.  For every new key wrap algorithm
added, you will need to register not only it alone but also it with every
different key agreement algorithm that is supported.  Thus adding a single
key wrap algorithm becomes a slight issue in terms of adding in all of the
different ways that it might be used.  This is a complexity issue that is
not discussed in the current draft.

 

I have not necessarily found that document size equals code size.  I have
implemented some very simple documents that were very difficult to code and
implemented some very long documents that were very easy to code.  So I
would not use that fact as a deciding factor.

 

(Once again I regret the fact that the group did not go with an object
descriptor for algorithms as this would have made all of this much simpler.
I actually immediately map from the string to an object description in my
JOSE implementation for simplicity reasons.  Not to mention that this is way
it needs to be done for the WebCrypto specficiation.)

 

Jim

 

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Tuesday, June 25, 2013 4:18 PM
To: 'Jim Schaad'; jose@ietf.org
Subject: RE: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 seems like a
substantially simpler approach than
http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01.  This is
evident by several metrics:

.         Number of proposed changes:  The Jones draft proposes no changes
to any of the current specs.  It simply defines an encoding for GCM and adds
registry entries for it.  Whereas the Barnes draft proposes a major
restructuring - listing 4 major changes in the introduction and 4 smaller
changes.

.         Normative text size:  The Jones GCM key wrap approach requires
only 7 normative sentences in 1/2 page of text.  The Barnes draft has four
pages of normative text, along with an extensive introduction describing the
proposed complete restructuring of JWS and JWE.

 

We don't need to boil the ocean with a total redesign to enable AEAD key
wrapping.  It can already easily be done with the current specs simply by
defining new algorithms.  The approach taken in
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00 would work
for any AEAD algorithm.

 

                                                                -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Tuesday, June 25, 2013 9:53 AM
To: jose@ietf.org
Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping

 

We now have two documents - one from Richard and one from Mike - which
provide the two different ways that have been proposed for doing key
wrapping with an AEAD algorithm.

 

Please review the two documents and provide comments to the list.

 

Jim

 


------=_NextPart_000_0491_01CE731A.A42A42A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1592155778;
	mso-list-type:hybrid;
	mso-list-template-ids:-1500624704 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>That is not the experience that we have seen =
with TLS.&nbsp; In this case people want to constantly register the =
entire matrix of items.&nbsp; I would not expect that desire to =
change.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Wednesday, June 26, 2013 9:01 PM<br><b>To:</b> Jim Schaad; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Issue #13 - use AES-GCM for =
Key Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>For my part, I consider the fact that people =
will need to register specific algorithm combinations that they actually =
need to be a feature &#8211; not a bug.&nbsp; The smaller the set of =
algorithm combinations registered, the more likely that they will be =
implemented and will interoperate.&nbsp; Trying to claim that we support =
the combinatorial explosion of mask generation functions, hash =
functions, key derivation functions, key wrapping functions, etc. that =
are possible will almost certainly result in less interoperability and =
more developer confusion than a small set of registered choices, =
carefully considered.&nbsp; I&#8217;m glad to have people consider these =
criteria in their evaluation of the two choices.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Wednesday, June 26, 2013 8:18 PM<br><b>To:</b> Mike =
Jones; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>My point was that there were some issues that =
your draft did not fully address that need to be evaluated as part of =
your proposal not that these algorithms would need to be added. =
&nbsp;The n x m addition of algorithms to the registry is an issue that =
is there for your draft that is not present for Richard&#8217;s draft =
and therefore needs to be considered in the =
arguments.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [<a =
href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsof=
t.com</a>] <br><b>Sent:</b> Wednesday, June 26, 2013 12:22 =
PM<br><b>To:</b> Jim Schaad; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Yes, we could also propose algorithm =
combinations for key agreement followed GCM key wrapping but I =
didn&#8217;t think that was an ask from the working group.&nbsp; The =
Denver minutes just recorded my action item as &#8220;key wrap draft for =
AES-GCM-keywrap&#8221;, so that&#8217;s what I did.&nbsp; We could have =
a discussion on Monday&#8217;s call and on the list about whether the =
working group is also interested in other =
algorithms.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Remember, the beauty of =
having the algorithms registry is that algorithms can be added =
&#8220;just in time&#8221; &#8211; as actual need for them is =
demonstrated.&nbsp; We don&#8217;t have to register all conceivable =
algorithm combinations up front for the JWE/JWA specs to be =
complete.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>As for how the AEAD =
parameters are handled I used a parameter encoding that doesn&#8217;t =
result in double base64url encoding anything.&nbsp; I could have instead =
introduced separate &#8220;iv&#8221; and &#8220;tag&#8221; header =
parameter values, but didn&#8217;t do so for that reason.&nbsp; But if =
people would prefer that approach because it&#8217;s more parallel to =
the use of GCM for plaintext encryption, I have no problem with =
that.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I do believe that the =
objective of my draft was met &#8211; demonstrating that AEAD key =
wrapping can be easily done with the current drafts.&nbsp; The details =
of how the algorithm parameters are encoded is secondary to that and =
algorithm-specific; several reasonable choices are possible within the =
current JWE framework &#8211; one of which was described in my =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Wednesday, June 26, 2013 =
11:30 AM<br><b>To:</b> Mike Jones; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> Re: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;no hat&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>&lt;sarcasm =
level=3D&#8221;heavy&#8221;&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am shocked that you =
would possibly support this proposal.&nbsp; It provides for two ways of =
dealing with something.&nbsp; It is my understanding that you never =
support anything that has two ways of doing =
something.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>How the AEAD algorithm =
parameters is handled completely differently for this proposal and for =
the same algorithms being used in a CEK context. &nbsp;This is going to =
lead to confusion.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&lt;/sarcasm&gt;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your specification is =
missing some items that still need to be registered&nbsp; Thus you also =
need to have ECDH-ES+A128GCMKW and ECDH-ES+A256GCMKW defined in your =
document as well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Your document ends up =
with a registration complexity that needs to be thought about and dealt =
with as well.&nbsp; For every new key wrap algorithm added, you will =
need to register not only it alone but also it with every different key =
agreement algorithm that is supported. &nbsp;Thus adding a single key =
wrap algorithm becomes a slight issue in terms of adding in all of the =
different ways that it might be used.&nbsp; This is a complexity issue =
that is not discussed in the current draft.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I have not necessarily =
found that document size equals code size.&nbsp; I have implemented some =
very simple documents that were very difficult to code and implemented =
some very long documents that were very easy to code.&nbsp; So I would =
not use that fact as a deciding factor.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>(Once again I regret the =
fact that the group did not go with an object descriptor for algorithms =
as this would have made all of this much simpler.&nbsp; I actually =
immediately map from the string to an object description in my JOSE =
implementation for simplicity reasons.&nbsp; Not to mention that this is =
way it needs to be done for the WebCrypto =
specficiation.)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Jim<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [<a =
href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsof=
t.com</a>] <br><b>Sent:</b> Tuesday, June 25, 2013 4:18 PM<br><b>To:</b> =
'Jim Schaad'; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
seems like a substantially simpler approach than <a =
href=3D"http://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01">htt=
p://tools.ietf.org/html/draft-barnes-jose-key-wrapping-01</a>.&nbsp; =
This is evident by several metrics:<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Number of =
proposed changes:&nbsp; The Jones draft proposes no changes to any of =
the current specs.&nbsp; It simply defines an encoding for GCM and adds =
registry entries for it.&nbsp; Whereas the Barnes draft proposes a major =
restructuring &#8211; listing 4 major changes in the introduction and 4 =
smaller changes.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>Normative =
text size:&nbsp; The Jones GCM key wrap approach requires only 7 =
normative sentences in 1/2 page of text.&nbsp; The Barnes draft has four =
pages of normative text, along with an extensive introduction describing =
the proposed complete restructuring of JWS and =
JWE.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>We don&#8217;t need to =
boil the ocean with a total redesign to enable AEAD key wrapping.&nbsp; =
It can already easily be done with the current specs simply by defining =
new algorithms.&nbsp; The approach taken in <a =
href=3D"http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00">=
http://tools.ietf.org/html/draft-jones-jose-aes-gcm-key-wrap-00</a> =
would work for any AEAD algorithm.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Tuesday, June 25, 2013 =
9:53 AM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> =
[jose] Issue #13 - use AES-GCM for Key =
Wrapping<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We now have =
two documents &#8211; one from Richard and one from Mike &#8211; which =
provide the two different ways that have been proposed for doing key =
wrapping with an AEAD algorithm.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the two documents and provide comments to the =
list.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------=_NextPart_000_0491_01CE731A.A42A42A0--


From Michael.Jones@microsoft.com  Thu Jun 27 09:49:34 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBFF21F9DD4 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saMMvT3zjdGs for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:49:20 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7A81021F8793 for <jose@ietf.org>; Thu, 27 Jun 2013 09:49:20 -0700 (PDT)
Received: from BY2FFO11FD012.protection.gbl (10.1.15.204) by BY2FFO11HUB017.protection.gbl (10.1.14.91) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 27 Jun 2013 16:49:19 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD012.mail.protection.outlook.com (10.1.14.130) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 16:49:19 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 16:49:13 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'n-sakimura' <n-sakimura@nri.co.jp>
Thread-Topic: [jose] #26: Allow for signature payload to not be base64 encoded
Thread-Index: AQHOcgNOsVoAPXc/s02k5Wh9HChUEZlIUkQAgACNH4CAAObIgIAAAUow
Date: Thu, 27 Jun 2013 16:49:12 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com>
In-Reply-To: <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(51704005)(13464003)(50084003)(374574003)(377454003)(365934002)(20776003)(47776003)(33656001)(51856001)(76786001)(81542001)(53806001)(76796001)(44976004)(50466002)(31966008)(77096001)(79102001)(47446002)(76482001)(56776001)(46102001)(16406001)(59766001)(54316002)(74366001)(6806003)(81342001)(77982001)(54356001)(56816003)(74502001)(65816001)(47736001)(63696002)(74662001)(50986001)(23676002)(4396001)(49866001)(74706001)(66066001)(74876001)(69226001)(55846006)(47976001)(80022001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB017; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:49:34 -0000

SmltLCB5b3Ugd3JvdGUgIklmIEkgYW0gbm90IHRyYW5zcG9ydGluZyB0aGUgYmFzZTY0dXJsIGVu
Y29kZWQgY29udGVudCwgYmVjYXVzZSBpdCBpcyBub3QgaW4gdGhlICJwYXlsb2FkIiBmaWVsZCwg
dGhlbiB3aHkgc2hvdWxkIEkgbmVlZCB0byBiYXNlNjQgZW5jb2RlIGl0IGp1c3QgdG8gdmFsaWRh
dGUgdGhlIHNpZ25hdHVyZS4gIFRoaXMgaXMgdGhlIGFsdG8gY2FzZS4iDQoNClNvIGFtIEkgY29y
cmVjdCB0aGVuLCBpbiB0aGlua2luZyB0aGF0IHlvdXIgbW90aXZhdGlvbiBmb3IgIzI2IGlzIGFj
dHVhbGx5ICMyNSAtIERldGFjaGVkIGNvbnRlbnQgZm9yIHRoZSBBTFRPIHVzZSBjYXNlPyAgQXMg
Sm9obiBhbmQgTmF0IGhhZCB3cml0dGVuLCB0aGlzIGNvdWxkIGJlIGhhbmRsZWQgYnkgdGhlIHNw
ZWNzIGFzIHRoZXkgYXJlIHRvZGF5IGJ5IHNpZ25pbmcgYSBoYXNoIG9mIHRoZSBkZXRhY2hlZCBj
b250ZW50IGFuZCBpbmNsdWRpbmcgYSBjb21wYWN0IEpXUyByZXByZXNlbnRpbmcgdGhhdCBzaWdu
YXR1cmUgYXMgYW4geC1hbHRvLXNpZ25hdHVyZSBoZWFkZXIuICBUaGF0IGRvZXNuJ3QgcmVxdWly
ZSBjaGFuZ2luZyB0aGUgc2lnbmF0dXJlIGNhbGN1bGF0aW9uLg0KDQoJCQkJLS0gTWlrZQ0KDQot
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSmltIFNjaGFhZCBbbWFpbHRvOmlldGZA
YXVndXN0Y2VsbGFycy5jb21dIA0KU2VudDogVGh1cnNkYXksIEp1bmUgMjcsIDIwMTMgOTo0MSBB
TQ0KVG86ICduLXNha2ltdXJhJw0KQ2M6IGRyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1
cmVAdG9vbHMuaWV0Zi5vcmc7IE1pa2UgSm9uZXM7IGpvc2VAaWV0Zi5vcmcNClN1YmplY3Q6IFJF
OiBbam9zZV0gIzI2OiBBbGxvdyBmb3Igc2lnbmF0dXJlIHBheWxvYWQgdG8gbm90IGJlIGJhc2U2
NCBlbmNvZGVkDQoNCk5hdCwNCg0KVGhlIG9ubHkgdGhpbmcgdGhhdCBjYW4gYmUgc2lnbmVkIG9y
IGVuY3J5cHRlZCBpcyBhbiBvY3RldCBzdHJpbmcuIChBIHNsaWdodCBvdmVyIGdlbmVyYWxpemF0
aW9uLiBHT1NUIGZvciBleGFtcGxlIGhhc2hlcyBhbiBpbnRlZ2VyLCB0cmVlIGhhc2hlcyBjYW4g
ZG8gc3RyYW5nZSB0aGluZ3MgYnV0IGEgc3VmZmljaWVudGx5IHRydWUgc3RhdGVtZW50IGZvciBv
dXIgcHVycG9zZXMuKQ0KDQpBIHRoYXQgYmVpbmcgc2FpZCAtIHllcyBjYXNlIDEgd291bGQgYmUg
c29tZXRoaW5nIHlvdSBjYW4gZG8uICBDYXNlICMyIHdvdWxkIG5vdCBiZSBzb21ldGhpbmcgdGhh
dCB5b3UgY2FuIGRvIGJlY2F1c2UgaXQgaXMgbm90IGFuIG9jdGV0IHN0cmluZy4NCg0KSWYgeW91
IGFyZSBsb29raW5nIGF0IEphdmFTY3JpcHQsIGluIG9yZGVyIHRvIGhhc2ggc29tZXRoaW5nIGFz
IGFuIG9jdGV0IHN0cmluZyBpdCBjYW4gYmUgb25lIG9mIHRocmVlIHRoaW5ncy4gIEEgVUludDhB
cnJheSwgYW4gSW50OEFycmF5IGFuZCwgZHVlIHRvIGNvbnZlbnRpb24sIGEgc3RyaW5nIHdoZXJl
IHRoZSB0b3AgYnl0ZSBvZiBhbGwgb2YgdGhlIGNvZGUgcG9pbnRzIGluIHRoZSBzdHJpbmcgaXMg
emVyby4NCg0KV2UgY3VycmVudGx5IGRvbid0IGhhdmUgYW4gZWZmaWNpZW50IHdheSB0byBlbmNv
ZGUgdGhlIFVpbnQ4QXJyYXkgY2FzZSwgYWx0aG91Z2ggdGhhdCBtaWdodCBub3QgYmUgdHJ1ZSBp
ZiB3ZSBhcmUgbG9va2luZyBhdCBuZXcgRUNNQSBzcGVjaWZpY2F0aW9ucyB3aGljaCBhcHBhcmVu
dGx5IGFyZSBhZGRpbmcgbW9yZSBkZWZpbmVkIHR5cGVzIGFuZCBzZXJpYWxpemF0aW9uIG1ldGhv
ZHMgZm9yIHRob3NlIHR5cGVzLg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZy
b206IG4tc2FraW11cmEgW21haWx0bzpuLXNha2ltdXJhQG5yaS5jby5qcF0NCj4gU2VudDogV2Vk
bmVzZGF5LCBKdW5lIDI2LCAyMDEzIDc6NTUgUE0NCj4gVG86IEppbSBTY2hhYWQNCj4gQ2M6IGRy
YWZ0LWlldGYtam9zZS1qc29uLXdlYi1zaWduYXR1cmVAdG9vbHMuaWV0Zi5vcmc7DQo+IG1pY2hh
ZWwuam9uZXNAbWljcm9zb2Z0LmNvbTsgam9zZUBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW2pv
c2VdICMyNjogQWxsb3cgZm9yIHNpZ25hdHVyZSBwYXlsb2FkIHRvIG5vdCBiZSBiYXNlNjQgDQo+
IGVuY29kZWQNCj4gDQo+IExldCBtZSB1bmRlcnN0YW5kIHRoZSBwcm9ibGVtLg0KPiANCj4gQXJl
IHlvdSBzdWdnZXN0aW5nIHRoYXQgd2Ugc2hvdWxkIGJlIGFibGUgdG8gZG8gc29tZXRoaW5nIGxp
a2U6DQo+IA0KPiBDYXNlIDE6DQo+IA0KPiAgICAgICB7InByb3RlY3RlZCI6PGludGVncml0eS1w
cm90ZWN0ZWQgc2hhcmVkIGhlYWRlciBjb250ZW50cz4iLA0KPiAgICAgICAgInVucHJvdGVjdGVk
Ijo8bm9uLWludGVncml0eS1wcm90ZWN0ZWQgc2hhcmVkIGhlYWRlciBjb250ZW50cz4iLA0KPiAg
ICAgICAgInBheWxvYWQiOiJ0aGlzIGlzIGEgbXVsdGlcbmxpbmUgdGV4dCBwYXlsb2FkIG9mIHdo
aWNoIGEgbGluZSANCj4gY2FuIGJlIHZlcnkgdmVyeSB2ZXJ5IGxvbmcgYW5kIHdyYXBwZWQgZHVy
aW5nIHRyYW5zbWlzc2lvbi4gIg0KPiAgICAgICAgInNpZ25hdHVyZXMiOlsNCj4gICAgICAgICB7
ImhlYWRlciI6IjxwZXItc2lnbmF0dXJlIHVucHJvdGVjdGVkIGhlYWRlciAxIGNvbnRlbnRzPiIs
DQo+ICAgICAgICAgICJzaWduYXR1cmUiOiI8c2lnbmF0dXJlIDEgY29udGVudHM+In0sDQo+ICAg
ICAgICAgLi4uDQo+ICAgICAgICAgeyJoZWFkZXIiOiI8cGVyLXNpZ25hdHVyZSB1bnByb3RlY3Rl
ZCBoZWFkZXIgTiBjb250ZW50cz4iLA0KPiAgICAgICAgICAic2lnbmF0dXJlIjoiPHNpZ25hdHVy
ZSBOIGNvbnRlbnRzPiJ9XSwNCj4gICAgICAgfQ0KPiANCj4gb3IgZXZlbg0KPiANCj4gQ2FzZSAy
Og0KPiANCj4gICAgICAgeyJwcm90ZWN0ZWQiOjxpbnRlZ3JpdHktcHJvdGVjdGVkIHNoYXJlZCBo
ZWFkZXIgY29udGVudHM+IiwNCj4gICAgICAgICJ1bnByb3RlY3RlZCI6PG5vbi1pbnRlZ3JpdHkt
cHJvdGVjdGVkIHNoYXJlZCBoZWFkZXIgY29udGVudHM+IiwNCj4gICAgICAgICJwYXlsb2FkIjp7
DQo+IAkidGhpcyI6ImlzIGEganNvbiIsDQo+IAkicGF5bG9hZCI6IndoaWNoIGlzIG5vdCBiYXNl
NjR1cmwgZW5jb2RlZCINCj4gICAgICAgIH0NCj4gICAgICAgICJzaWduYXR1cmVzIjpbDQo+ICAg
ICAgICAgeyJoZWFkZXIiOiI8cGVyLXNpZ25hdHVyZSB1bnByb3RlY3RlZCBoZWFkZXIgMSBjb250
ZW50cz4iLA0KPiAgICAgICAgICAic2lnbmF0dXJlIjoiPHNpZ25hdHVyZSAxIGNvbnRlbnRzPiJ9
LA0KPiAgICAgICAgIC4uLg0KPiAgICAgICAgIHsiaGVhZGVyIjoiPHBlci1zaWduYXR1cmUgdW5w
cm90ZWN0ZWQgaGVhZGVyIE4gY29udGVudHM+IiwNCj4gICAgICAgICAgInNpZ25hdHVyZSI6Ijxz
aWduYXR1cmUgTiBjb250ZW50cz4ifV0sDQo+ICAgICAgIH0NCj4gDQo+IFRoZW4sIEkgYW0gd29y
cmllZCBhYm91dCBhbGxvd2luZyB0aGVtIGJlY2F1c2UgaW4gZ2VuZXJhbCB3ZSB3b3VsZCBub3Qg
DQo+IGtub3cgd2hhdCB3b3VsZCBhIHRyYW5zbWlzc2lvbiBtZWNoYW5pc20gYW5kIHVzZXIgYWdl
bnRzIChpbmNsdWRpbmcgDQo+IHRleHQNCj4gZWRpdG9ycykgd291bGQgZG8gdG8gdGhlbSwgbGlr
ZSBNaWtlIG1lbnRpb25lZC4gSSBkbyBub3QgdGhpbmsgd2UgDQo+IHNob3VsZCBhc3N1bWUgdGhl
IHByb3BlcnR5IG9mIHRoZSB0cmFuc21pc3Npb24gbWVjaGFuaXNtIGluIEpPU0UgbGV2ZWwuDQo+
IEFzc3VtaW5nIHRoYXQgd291bGQgY2F1c2UgYnJpdHRsZW5lc3MgaW4gdGhlIGltcGxlbWVudGF0
aW9ucy4NCj4gDQo+IEZvciBkZXRhY2hlZCBzaWduYXR1cmUsIEkgZG8gbm90IHVuZGVyc3RhbmQg
d2h5IHlvdSB3b3VsZCB3YW50IG5vbi0gDQo+IGJhc2U2NHVybCBlbmNvZGVkIHBheWxvYWQuIFRo
ZSBhcHBsaWNhdGlvbiBzaG91bGQgZGVmaW5lIGhvdyB0byBoYXNoIA0KPiB0aGUgb2N0ZXQgc3Ry
ZWFtIHRoYXQgaXQgd2FudHMgdG8gY2FsY3VsYXRlIHNpZ25hdHVyZSBvdmVyIGl0LCBhbmQgd2Ug
DQo+IGNhbiBqdXN0IGluY2x1ZGUgdGhlIGJhc2U2NHVybCBlbmNvZGVkIGhhc2ggaW4gdGhlICJw
YXlsb2FkIi4NCj4gV2h5IHdvdWxkIHlvdSBsaWtlIHRvIGRvIG90aGVyIGVuY29kaW5nIGZvciB0
aGUgaGFzaD8NCg0KSWYgSSBhbSBub3QgdHJhbnNwb3J0aW5nIHRoZSBiYXNlNjR1cmwgZW5jb2Rl
ZCBjb250ZW50LCBiZWNhdXNlIGl0IGlzIG5vdCBpbiB0aGUgInBheWxvYWQiIGZpZWxkLCB0aGVu
IHdoeSBzaG91bGQgSSBuZWVkIHRvIGJhc2U2NCBlbmNvZGUgaXQganVzdCB0byB2YWxpZGF0ZSB0
aGUgc2lnbmF0dXJlLiAgVGhpcyBpcyB0aGUgYWx0byBjYXNlLg0KDQpKaW0NCg0KPiANCj4gLS0N
Cj4gTmF0IFNha2ltdXJhIChuLXNha2ltdXJhQG5yaS5jby5qcCkNCj4gTm9tdXJhIFJlc2VhcmNo
IEluc3RpdHV0ZQ0KPiANCj4gUExFQVNFIFJFQUQ6DQo+IFRoZSBpbmZvcm1hdGlvbiBjb250YWlu
ZWQgaW4gdGhpcyBlLW1haWwgaXMgY29uZmlkZW50aWFsIGFuZCBpbnRlbmRlZCANCj4gZm9yIHRo
ZSBuYW1lZCByZWNpcGllbnQocykgb25seS4NCj4gSWYgeW91IGFyZSBub3QgYW4gaW50ZW5kZWQg
cmVjaXBpZW50IG9mIHRoaXMgZS1tYWlsLCB5b3UgYXJlIGhlcmVieSANCj4gbm90aWZpZWQgdGhh
dCBhbnkgcmV2aWV3LCBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24gb3IgZHVwbGljYXRpb24g
DQo+IG9mIHRoaXMgbWVzc2FnZSBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSBy
ZWNlaXZlZCB0aGlzIA0KPiBtZXNzYWdlIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5k
ZXIgaW1tZWRpYXRlbHkgYW5kIGRlbGV0ZSB5b3VyIGNvcHkgZnJvbSB5b3VyIHN5c3RlbS4NCg0K

From ietf@augustcellars.com  Thu Jun 27 09:49:47 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B697321F9E28 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YFrULl9XCg2u for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:49:43 -0700 (PDT)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) by ietfa.amsl.com (Postfix) with ESMTP id 00D9E21F8793 for <jose@ietf.org>; Thu, 27 Jun 2013 09:49:43 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id C760638F23; Thu, 27 Jun 2013 09:49:42 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Manger, James H'" <James.H.Manger@team.telstra.com>, <jose@ietf.org>
References: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com>
Date: Thu, 27 Jun 2013 09:48:46 -0700
Message-ID: <049501ce7356$31644680$942cd380$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKtGl93YDlEnjAj5/fvpBd7x0XS6QKImkgOl3gyfqA=
Content-Language: en-us
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:49:47 -0000

James,

The small devices use case does present a reason for wanting to use =
AES-GCM rather than AESKW for this case.  Specifically, there is no need =
to have silicon devoted to doing AES decrypt.  All operations can be =
done just with AES encrypt.

jim

> -----Original Message-----
> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf =
Of
> Manger, James H
> Sent: Wednesday, June 26, 2013 7:40 PM
> To: jose@ietf.org
> Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
>=20
> I don't think we should standardize =
draft-jones-jose-aes-gcm-key-wrap-00. No
> rationale is apparent. We already have an AES-based key wrap algorithm
> (A128KW, A256KW), which has a 64-bit size overhead. The AES-GCM key
> wrap algorithm in this draft add almost no useful properties, but has =
a 224-bit
> size overhead.
>=20
> I like the concatenation of the IV, ciphertext, and tag byte arrays. =
But doing
> this here while content encryption serializes the same values as =
dot-separated
> B64 blobs does smell of poor ad hoc design. It is nice to highlight =
how a
> previous choice complicates extending JOSE to other algorithms, but =
only if
> we then fix that previous choice.
>=20
> If the additional authenticated data (AAD) was used to bind the CEK =
algorithm
> id (or other context info, as ConcatKDF does) to the wrapped key, then =
there
> would at least be an extra security property that would make this key =
wrap
> algorithm worth considering. For instance, instead of AAD being empty, =
AAD
> could be the "key wrap: " + "enc" value.
>=20
> By reusing a CEK algorithm as a KEK algorithm, and supporting direct
> encryption, we substantially increase the risk that an attacker can =
rearrange
> some encrypted content so a legitimate recipient treats it as an =
encrypted key
> leading to security flaws.
>=20
> For example, Alice sends "Start of PIN =3D 8" confidentially to Bob:
>   {alg:dir,enc:A128GCM,kid:1}..iv.ciphertext.tag
> An attacker seeing this JOSE message learns nothing about the 1st =
digit of the
> PIN.
> But if the attacker sends 10 messages to Bob for 10 guess of that =
digit:
>=20
> =
{alg:A128GCMKW,enc:A128GCM,kid:1}.iv|ciphertext|tag.ivN.ciphertextN.tag
> N
> where ivN.ciphertextN.tagN are calculated using an AES key of "Start =
of PIN =3D
> <N>", then 9 messages will cause errors, while 1 message will be =
accepted --
> revealing the supposedly confidential information in 10 guesses =
instead of
> 2^128.
>=20
> Actually the above attack does not quite work for the compact encoding =
as
> AAD is never empty for content encryption. I not certain for the JSON
> encoding. In any case, an explicit and unambiguous AAD value for key
> wrapping would be good.
>=20
> Finally, a key wrap algorithm like this should go to the IETF crypto =
group
> (CRFG) instead of being invented in JOSE. We have already spent a year
> unpicking a JOSE-special AEAD algorithm.
>=20
> --
> James Manger
>=20
>=20
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > Of Jim Schaad
> > Sent: Wednesday, 26 June 2013 2:53 AM
> > To: jose@ietf.org
> > Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
> >
> > We now have two documents   one from Richard and one from Mike   =
which
> > provide the two different ways that have been proposed for doing key
> > wrapping with an AEAD algorithm.
> >
> > Please review the two documents and provide comments to the list.
> >
> > Jim
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose


From ietf@augustcellars.com  Thu Jun 27 09:50:43 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67E221F9E44 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=0.974,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35FToDMgI+Fc for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:50:38 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1C05321F9DD4 for <jose@ietf.org>; Thu, 27 Jun 2013 09:50:35 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 7D5FD38F00; Thu, 27 Jun 2013 09:50:34 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Tim Bray'" <tbray@textuality.com>, "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org>	<076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org>	<033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com>	<4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com>	<03b401ce72e5$002c65f0$008531d0$@augustcellars.com>	<4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com>
In-Reply-To: <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com>
Date: Thu, 27 Jun 2013 09:49:38 -0700
Message-ID: <049601ce7356$504a9590$f0dfc0b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0497_01CE731B.A3EDB960"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvAtXnsooCfmP1+wE/Pt+eAksevJwBgJ6Q/JkrlwwA
Content-Language: en-us
Cc: jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:50:43 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0497_01CE731B.A3EDB960
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am attacking you.  Why would I care about what the restrictions on =
producers are?

=20

From: Tim Bray [mailto:tbray@textuality.com]=20
Sent: Wednesday, June 26, 2013 10:24 PM
To: Mike Jones
Cc: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org; =
jose@ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional =
text

=20

I think it=E2=80=99s a nice clean minimal solution to say that producers =
MUST NOT generate dupes, end of story.  I don=E2=80=99t think saying =
anything beyond that adds value. -T

=20

On Wed, Jun 26, 2013 at 9:07 PM, Mike Jones =
<Michael.Jones@microsoft.com> wrote:

The alternative is to say that producers MUST NOT produce JSON with =
duplicate member names and that consumers are strongly RECOMMENDED to =
reject input with duplicate member names and leave it at that.

I understand not wanting to require customer parsers if the underlying =
platform parsers are deficient.  But I really hope that the JSON WG will =
have more sense than to allow the current madness to continue.  As I =
understood it, the primary motivation for the JSON WG in the first place =
was to change the SHOULD to a MUST.  If they don't do that, I'm really =
not sure what the point of it is.

                                -- Mike

P.S.  I am a subscriber to the JSON mailing list, but unfortunately, the =
volume got so high a few weeks ago that trying to keep up with it became =
an impediment to getting real work done.  At that point I created a rule =
to file those messages into a folder, which I only rarely look at.  Has =
that situation improved?


-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com]

Sent: Wednesday, June 26, 2013 8:18 PM
To: Mike Jones; draft-ietf-jose-json-web-signature@tools.ietf.org
Cc: jose@ietf.org
Subject: RE: [jose] #27: member names MUST be unique needs additional =
text

I would strongly encourage everyone in the JOSE list to join the JSON =
list and read what was is there and participate.

That being said there are situations where you might not be able to do =
an independent parser.  And in fact what you have stated is that there =
is now a requirement that a JOSE library supply a JSON parser.  Is that =
really what we want to say?  How far from creating a set of generator =
and parser requirements that are non standard and requiring a =
parser/generator are we from that?

> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Wednesday, June 26, 2013 12:30 PM
> To: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional
> text
>
> The operable sentence in my suggested text below is this one: "If the
> platform's JSON parser does not reject input with duplicate member
> names, the input will first need to be separately parsed to reject
> these invalid inputs before using the platform's parser".  In other
> words, if the JSON parser in the development platform you are using
> does not reject inputs with duplicate member names, you will need to
> write a separate JSON parser that detects this invalid input and =
rejects it.
>
> This parser could either just be a validator, returning TRUE or FALSE
> for whether the JSON is valid for JOSE - in which case you'd then pass
> any inputs validating as TRUE to the platform's JSON parser, or it
> could be a replacement parser, in which case your code would not use
> the development platform's JSON parser at all.  I suspect people would
> be more likely to do the former than the latter, but both approaches =
are equivalent.
>
> BTW, if it's your sense that there's a problem occurring in the JSON
> working group with respect to enabling strict JSON parsing, we
> probably need to become active there.  For instance, even if the spec
> allows duplicate member names like the ECMA spec does, the RFC could
> recommend or require that parsers support a "strict" mode, which =
rejects these unnecessarily lax inputs.
> Then JOSE implementations could use that.
>
>                               -- Mike
>
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Wednesday, June 26, 2013 11:30 AM
> To: 'jose issue tracker';
> draft-ietf-jose-json-web-signature@tools.ietf.org;
> Mike Jones
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional
> text
>
> <no hat>
>
> I consider myself to be reasonably competent in both English and
> Technical English.  I have no idea what I am supposed to be doing to
> deal with the text below.  Does this mean that I need to write an
> independent parser?  What about cases where it is coming in on a
> stream and I don't get to see the data before the parse occurs?  How
> are they interpreted differently?  What exactly is this supposed to be
> addressing.  Much of this could be skipped when we said don't do it.
> Since this is no longer a viable statement due to the state of =
parsers, we need to be more explicit and say what is going on.
>
> No I don't consider the suggested text to be adequate.
>
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > Of jose issue tracker
> > Sent: Tuesday, June 25, 2013 5:41 PM
> > To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > michael.jones@microsoft.com
> > Cc: jose@ietf.org
> > Subject: Re: [jose] #27: member names MUST be unique needs
> > additional text
> >
> > #27: member names MUST be unique needs additional text
> >
> >
> > Comment (by michael.jones@microsoft.com):
> >
> >  The JWS draft currently says:
> >
> >          The Header Parameter Names within the JWS Header MUST be =
unique;
> >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> >
> >  How about changing this to:
> >
> >          The Header Parameter Names within the JWS Header MUST be =
unique;
> >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> >          This is necessary to prevent attacks in which the same JWS
> > might  be interpreted
> >          in different ways by different implementations and to
> > prevent
> attackers
> >          from hiding extra content in duplicate member values.
> >          If the platform s JSON parser does not reject input with
> > duplicate member names,
> >          the input will first need to be separately parsed to reject
> > these  invalid inputs
> >          before using the platform s parser.
> >
> > --
> > -------------------------+------------------------------------------

> > -------------------------+--

> > -------------------------+--
> > -------------------------+---
> >  Reporter:               |       Owner:  draft-ietf-jose-json-web-
> >   ietf@augustcellars.com |  signature@tools.ietf.org
> >      Type:  defect       |      Status:  new
> >  Priority:  major        |   Milestone:
> > Component:  json-web-    |     Version:
> >   signature              |  Resolution:
> >  Severity:  -            |
> >  Keywords:               |
> > -------------------------+------------------------------------------

> > -------------------------+--

> > -------------------------+--
> > -------------------------+---
> >
> > Ticket URL:
> > <http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
> > jose <http://tools.ietf.org/jose/>
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose


_______________________________________________
jose mailing list
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose

=20


------=_NextPart_000_0497_01CE731B.A3EDB960
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I am attacking you.=C2=A0 Why would I care about what the =
restrictions on producers are?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Tim Bray [mailto:tbray@textuality.com] <br><b>Sent:</b> Wednesday, June =
26, 2013 10:24 PM<br><b>To:</b> Mike Jones<br><b>Cc:</b> Jim Schaad; =
draft-ietf-jose-json-web-signature@tools.ietf.org; =
jose@ietf.org<br><b>Subject:</b> Re: [jose] #27: member names MUST be =
unique needs additional text<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
it=E2=80=99s a nice clean minimal solution to say that producers MUST =
NOT generate dupes, end of story.&nbsp; I don=E2=80=99t think saying =
anything beyond that adds value. -T<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Wed, Jun 26, 2013 at 9:07 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" =
target=3D"_blank">Michael.Jones@microsoft.com</a>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoNormal>The alternative is to say that =
producers MUST NOT produce JSON with duplicate member names and that =
consumers are strongly RECOMMENDED to reject input with duplicate member =
names and leave it at that.<br><br>I understand not wanting to require =
customer parsers if the underlying platform parsers are deficient. =
&nbsp;But I really hope that the JSON WG will have more sense than to =
allow the current madness to continue. &nbsp;As I understood it, the =
primary motivation for the JSON WG in the first place was to change the =
SHOULD to a MUST. &nbsp;If they don't do that, I'm really not sure what =
the point of it is.<br><span style=3D'color:#888888'><br><span =
class=3Dhoenzb>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -- =
Mike</span><br></span><br>P.S. &nbsp;I am a subscriber to the JSON =
mailing list, but unfortunately, the volume got so high a few weeks ago =
that trying to keep up with it became an impediment to getting real work =
done. &nbsp;At that point I created a rule to file those messages into a =
folder, which I only rarely look at. &nbsp;Has that situation =
improved?<o:p></o:p></p><div><p class=3DMsoNormal><br>-----Original =
Message-----<br>From: Jim Schaad [mailto:<a =
href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a>]<o:p></=
o:p></p></div><div><div><p class=3DMsoNormal>Sent: Wednesday, June 26, =
2013 8:18 PM<br>To: Mike Jones; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">draft-i=
etf-jose-json-web-signature@tools.ietf.org</a><br>Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>Subject: RE: [jose] =
#27: member names MUST be unique needs additional text<br><br>I would =
strongly encourage everyone in the JOSE list to join the JSON list and =
read what was is there and participate.<br><br>That being said there are =
situations where you might not be able to do an independent parser. =
&nbsp;And in fact what you have stated is that there is now a =
requirement that a JOSE library supply a JSON parser. &nbsp;Is that =
really what we want to say? &nbsp;How far from creating a set of =
generator and parser requirements that are non standard and requiring a =
parser/generator are we from that?<br><br>&gt; -----Original =
Message-----<br>&gt; From: Mike Jones [mailto:<a =
href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</=
a>]<br>&gt; Sent: Wednesday, June 26, 2013 12:30 PM<br>&gt; To: Jim =
Schaad; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">draft-i=
etf-jose-json-web-signature@tools.ietf.org</a><br>&gt; Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>&gt; Subject: RE: =
[jose] #27: member names MUST be unique needs additional<br>&gt; =
text<br>&gt;<br>&gt; The operable sentence in my suggested text below is =
this one: &quot;If the<br>&gt; platform's JSON parser does not reject =
input with duplicate member<br>&gt; names, the input will first need to =
be separately parsed to reject<br>&gt; these invalid inputs before using =
the platform's parser&quot;. &nbsp;In other<br>&gt; words, if the JSON =
parser in the development platform you are using<br>&gt; does not reject =
inputs with duplicate member names, you will need to<br>&gt; write a =
separate JSON parser that detects this invalid input and rejects =
it.<br>&gt;<br>&gt; This parser could either just be a validator, =
returning TRUE or FALSE<br>&gt; for whether the JSON is valid for JOSE - =
in which case you'd then pass<br>&gt; any inputs validating as TRUE to =
the platform's JSON parser, or it<br>&gt; could be a replacement parser, =
in which case your code would not use<br>&gt; the development platform's =
JSON parser at all. &nbsp;I suspect people would<br>&gt; be more likely =
to do the former than the latter, but both approaches are =
equivalent.<br>&gt;<br>&gt; BTW, if it's your sense that there's a =
problem occurring in the JSON<br>&gt; working group with respect to =
enabling strict JSON parsing, we<br>&gt; probably need to become active =
there. &nbsp;For instance, even if the spec<br>&gt; allows duplicate =
member names like the ECMA spec does, the RFC could<br>&gt; recommend or =
require that parsers support a &quot;strict&quot; mode, which rejects =
these unnecessarily lax inputs.<br>&gt; Then JOSE implementations could =
use that.<br>&gt;<br>&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -- =
Mike<br>&gt;<br>&gt; -----Original Message-----<br>&gt; From: Jim Schaad =
[mailto:<a =
href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a>]<br>&gt=
; Sent: Wednesday, June 26, 2013 11:30 AM<br>&gt; To: 'jose issue =
tracker';<br>&gt; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">draft-i=
etf-jose-json-web-signature@tools.ietf.org</a>;<br>&gt; Mike =
Jones<br>&gt; Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>&gt; Subject: RE: =
[jose] #27: member names MUST be unique needs additional<br>&gt; =
text<br>&gt;<br>&gt; &lt;no hat&gt;<br>&gt;<br>&gt; I consider myself to =
be reasonably competent in both English and<br>&gt; Technical English. =
&nbsp;I have no idea what I am supposed to be doing to<br>&gt; deal with =
the text below. &nbsp;Does this mean that I need to write an<br>&gt; =
independent parser? &nbsp;What about cases where it is coming in on =
a<br>&gt; stream and I don't get to see the data before the parse =
occurs? &nbsp;How<br>&gt; are they interpreted differently? &nbsp;What =
exactly is this supposed to be<br>&gt; addressing. &nbsp;Much of this =
could be skipped when we said don't do it.<br>&gt; Since this is no =
longer a viable statement due to the state of parsers, we need to be =
more explicit and say what is going on.<br>&gt;<br>&gt; No I don't =
consider the suggested text to be adequate.<br>&gt;<br>&gt; &gt; =
-----Original Message-----<br>&gt; &gt; From: <a =
href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> =
[mailto:<a =
href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a>] On =
Behalf<br>&gt; &gt; Of jose issue tracker<br>&gt; &gt; Sent: Tuesday, =
June 25, 2013 5:41 PM<br>&gt; &gt; To: <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">draft-i=
etf-jose-json-web-signature@tools.ietf.org</a>;<br>&gt; &gt; <a =
href=3D"mailto:michael.jones@microsoft.com">michael.jones@microsoft.com</=
a><br>&gt; &gt; Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>&gt; &gt; Subject: =
Re: [jose] #27: member names MUST be unique needs<br>&gt; &gt; =
additional text<br>&gt; &gt;<br>&gt; &gt; #27: member names MUST be =
unique needs additional text<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt; =
Comment (by <a =
href=3D"mailto:michael.jones@microsoft.com">michael.jones@microsoft.com</=
a>):<br>&gt; &gt;<br>&gt; &gt; &nbsp;The JWS draft currently =
says:<br>&gt; &gt;<br>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;The =
Header Parameter Names within the JWS Header MUST be unique;<br>&gt; =
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;JWSs with duplicate Header =
Parameter Names MUST be rejected.<br>&gt; &gt;<br>&gt; &gt; &nbsp;How =
about changing this to:<br>&gt; &gt;<br>&gt; &gt; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;The Header Parameter Names within the JWS Header MUST be =
unique;<br>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;JWSs with =
duplicate Header Parameter Names MUST be rejected.<br>&gt; &gt; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;This is necessary to prevent attacks in which =
the same JWS<br>&gt; &gt; might &nbsp;be interpreted<br>&gt; &gt; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;in different ways by different =
implementations and to<br>&gt; &gt; prevent<br>&gt; attackers<br>&gt; =
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;from hiding extra content in =
duplicate member values.<br>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;If the platform s JSON parser does not reject input with<br>&gt; =
&gt; duplicate member names,<br>&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;the input will first need to be separately parsed to =
reject<br>&gt; &gt; these &nbsp;invalid inputs<br>&gt; &gt; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;before using the platform s parser.<br>&gt; =
&gt;<br>&gt; &gt; --<br>&gt; &gt; =
-------------------------+------------------------------------------<o:p>=
</o:p></p></div></div><p class=3DMsoNormal>&gt; &gt; =
-------------------------+--<o:p></o:p></p><div><p =
class=3DMsoNormal>&gt; &gt; -------------------------+--<br>&gt; &gt; =
-------------------------+---<br>&gt; &gt; &nbsp;Reporter: &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; Owner: =
&nbsp;draft-ietf-jose-json-web-<br>&gt; &gt; &nbsp; <a =
href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a> | =
&nbsp;<a =
href=3D"mailto:signature@tools.ietf.org">signature@tools.ietf.org</a><br>=
&gt; &gt; &nbsp; &nbsp; &nbsp;Type: &nbsp;defect &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp;Status: &nbsp;new<br>&gt; &gt; &nbsp;Priority: =
&nbsp;major &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; Milestone:<br>&gt; &gt; =
Component: &nbsp;json-web- &nbsp; &nbsp;| &nbsp; &nbsp; Version:<br>&gt; =
&gt; &nbsp; signature &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp;Resolution:<br>&gt; &gt; &nbsp;Severity: &nbsp;- &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;|<br>&gt; &gt; &nbsp;Keywords: &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<br>&gt; &gt; =
-------------------------+------------------------------------------<o:p>=
</o:p></p></div><p class=3DMsoNormal>&gt; &gt; =
-------------------------+--<o:p></o:p></p><div><div><p =
class=3DMsoNormal>&gt; &gt; -------------------------+--<br>&gt; &gt; =
-------------------------+---<br>&gt; &gt;<br>&gt; &gt; Ticket =
URL:<br>&gt; &gt; &lt;<a =
href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1" =
target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comme=
nt:1</a>&gt;<br>&gt; &gt; jose &lt;<a =
href=3D"http://tools.ietf.org/jose/" =
target=3D"_blank">http://tools.ietf.org/jose/</a>&gt;<br>&gt; =
&gt;<br>&gt; &gt; =
_______________________________________________<br>&gt; &gt; jose =
mailing list<br>&gt; &gt; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>&gt; &gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><br><br><=
br>_______________________________________________<br>jose mailing =
list<br><a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a><o:p></o:=
p></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_0497_01CE731B.A3EDB960--


From ve7jtb@ve7jtb.com  Thu Jun 27 09:52:18 2013
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2062321F9E30 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yFZSNQwzNBl0 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 09:52:13 -0700 (PDT)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id 07D3221F9DD4 for <jose@ietf.org>; Thu, 27 Jun 2013 09:52:12 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id u12so660889qcx.12 for <jose@ietf.org>; Thu, 27 Jun 2013 09:52:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=v6/ulOtwH51EIMOxwBEiMJrhNMae7WArhBBxvUgU5g8=; b=bs2UnUxSTH/TcsHLQd3A+1hq7pkO2zq3C4Ovom2ia4AdA2DztSshCnoj0mh6+XsQrr 6Xq8jRY/xC31OWT4tn+TO5pWoHm3+0TBrhKyYPEBv6gLb6HiXNj/6LmLbQZDN5QV8XEB vvUrgVD/Ewr+oDGTJGgRopqgwrbf6plyJt1f6JiCX9TsZ60FRkdM7bszl4lHVXW4nSIF r5g0THcdCncQz0o8Vlu2jJvcmexzOQ5bFUZ+cgx6jDSDNgs02pEcTK71ujpbJDHVxWfW 4jPER6H3W8ywM8U2dgmXgXRGYyBz5JHAc5y5dgH2/ThOnIdlAY5Q4JwyzihYcMo9+/8n WdTQ==
X-Received: by 10.49.101.74 with SMTP id fe10mr12245109qeb.11.1372351931361; Thu, 27 Jun 2013 09:52:11 -0700 (PDT)
Received: from [192.168.1.216] (190-20-7-218.baf.movistar.cl. [190.20.7.218]) by mx.google.com with ESMTPSA id 15sm5656386qaa.9.2013.06.27.09.52.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Jun 2013 09:52:09 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_F2A02399-2847-44C3-AC1E-A7A43A2B6155"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <048e01ce7354$07537480$15fa5d80$@augustcellars.com>
Date: Thu, 27 Jun 2013 12:51:46 -0400
Message-Id: <6459A8AE-A016-449B-A9B8-D691DFB8750B@ve7jtb.com>
References: <061.ff0b5e5ec612118e22556dfc646e603e@trac.tools.ietf.org> <076.edb3925c8fcf46207d36414fcad4b5e6@trac.tools.ietf.org> <03a601ce72c7$6eb58010$4c208030$@augustcellars.com> <C18B2753-41A6-4C47-BB22-A139896C44A0@ve7jtb.com> <048e01ce7354$07537480$15fa5d80$@augustcellars.com>
To: "Jim Schaad" <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQnQe6lQlgs/OmzTdYl3iAOReKW4p2CTbOTn7aBBL1E4Gcn4U1a5a9bQN/zFGU7nKz+TMlGO
Cc: jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #25: Detached content for the ALTO use case
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 16:52:18 -0000

--Apple-Mail=_F2A02399-2847-44C3-AC1E-A7A43A2B6155
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Having a OPTIONAL defined set of claims for a JSON body to point to =
external objects and there hashes is fine.

We need to consider how that may interact with the JWT spec over in =
OAuth that defines the claims for a JWT token.

I think that can be done without impacting the core of JWS.

John B.


On 2013-06-27, at 12:33 PM, "Jim Schaad" <ietf@augustcellars.com> wrote:

> I agree that forcing the application layer to figure out where and =
what the
> detached content is makes compete sense.  This would be true if we did
> detached signatures or indirect content hashing.
>=20
> For indirect content hashing I think we would need to define the =
following:
>=20
> 1.  An object structure
> 2. A media type for that structure
> 3. How to do an array of references (it is possible that we would just =
only
> allow one but I don't know that this makes sense)
> 4. A member for a hash value
> 5. A member for a hash algorithm
> 6. A set of hash functions with the appropriate registration
> 7. A member name for a content identifier in the event that we allow
> multiple references (optional element)
>=20
> I also think it would make sense to evaluate two sets of rules for
> evaluation that an application can just reference
>=20
> All or nothing - all of the contents need to be found and evaluated =
for the
> signature to be considered to be valid
> Optional checking - the contents are checked independently from the
> signature processing.  Hash values are checked when and as needed.
>=20
>=20
>=20
>> -----Original Message-----
>> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
>> Sent: Wednesday, June 26, 2013 6:20 PM
>> To: Jim Schaad
>> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
>> Subject: Re: [jose] #25: Detached content for the ALTO use case
>>=20
>> The problem is describing the detached thing in a way that will allow =
for
>> correct verification.
>> SOAP has a number of interesting things that can happen by getting =
the
>> receiver to verify one header part but use another for processing.
>> XMLdsig wrapping attacks exist and are to some minds related to =
detached
>> signatures.
>>=20
>> In Connect the claim defines exactly how to find the detached body.
>>=20
>> Leaving it to the application layer to define where the detached body =
is
> to be
>> located is not unreasonable.
>>=20
>> How are you thinking of doing that in a generic and secure enough way =
to
> be
>> useful in JWS itself?
>>=20
>> The signature itself is not really the hard part.
>>=20
>> As an example of a detached body that might be useful to look at is
> signing a
>> HTTP request for OAuth and including the JWS in a header.  How in a
> generic
>> JWS way would you describe how to assemble the body to be hashed?
>>=20
>> In principal I see lats of uses at the application layer for sending =
a
> hash of
>> something in a JWS where the application layer describes how to =
assemble
>> some custom content for hashing, but I have a hard time seeing that =
happen
> in
>> a interoperable way in JWS.   I could be wrong and am interested in
> concrete
>> proposals.
>>=20
>> John B.
>>=20
>> On 2013-06-26, at 7:46 PM, "Jim Schaad" <ietf@augustcellars.com> =
wrote:
>>=20
>>> I completely disagree with your characterization that detached
> signatures
>> was either a complicated feature or that it caused interop problems.  =
The
>> problems that I always had with XMLDSig were XML problems and had =
nothing
>> to do with the question of detached or non-detached, canonizied or =
non-
>> canonicized.  The problem was always that XML itself was not a good =
thing
> to
>> try and produce a usable and reproducible octet stream for the =
purposes of
>> hashing.  If you just processed it as a binary stream in a disk file =
then
> there
>> were no problems (assuming that you had not re-written it in some =
way).
>>>=20
>>> I also disagree that it would be any easier to do a detached =
signature
> using
>> an indirect rather than direct form.  If you are worried about having
> things
>> change because it is a detached content, then it makes no difference =
if
> that
>> detached content is either directly or indirectly reference.  I don't
> think that
>> going to an indirect form fixes this problem in any way.
>>>=20
>>> Finally, if we are going to say this is the way to do things, we =
need to
> define a
>> way to do this in the JOSE drafts themselves.  This would expected to =
be a
>> standard technique that is used by a number of different systems.  It
> should
>> therefore be a common method for doing it because otherwise you get =
many
>> different ways of doing it that are designed by non-security people =
and
>> therefore prone to error.
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On =
Behalf Of
>>>> jose issue tracker
>>>> Sent: Tuesday, June 25, 2013 5:08 PM
>>>> To: draft-ietf-jose-json-web-signature@tools.ietf.org;
>>>> michael.jones@microsoft.com
>>>> Cc: jose@ietf.org
>>>> Subject: Re: [jose] #25: Detached content for the ALTO use case
>>>>=20
>>>> #25: Detached content for the ALTO use case
>>>>=20
>>>>=20
>>>> Comment (by michael.jones@microsoft.com):
>>>>=20
>>>> Detached signatures was one of the complicated features of XMLDSIG =
that
>>>> caused substantial interop problems.  I d thought that there was
> already
>>>> substantial sentiment in the working group not to do this because =
of
> the
>> high
>>>> complexity/benefit ratio.
>>>>=20
>>>> The good news, however, is that a form of detached signatures is =
EASY
> to
>>>> build one layer up the stack by signing a hash of the detached =
content.
>>>> ALTO could easily do this.
>>>>=20
>>>> There s already a deployed example of this, in fact.  OpenID =
Connect
>>>> includes a hash of the OAuth Access Token as a claim in the ID =
Token
>> issued
>>>> with it.  This allows the holder of the ID Token to verify that  =
token
>> substitution
>>>> of a different Access Token value has not been  performed by an
> attacker.
>>>> This works with JWS as it is today.
>>>>=20
>>>> I therefore suggest that we recommend this technique to ALTO and =
add a
>>>> description of it in the ALTO section of the Use Cases document and
> close
>> this
>>>> issue as  won t fix .
>>>>=20
>>>> --
>>>>=20
> =
-------------------------+----------------------------------------------
>>>> -------------------------+---
>>>> Reporter:               |       Owner:  draft-ietf-jose-json-web-
>>>> ietf@augustcellars.com |  signature@tools.ietf.org
>>>>   Type:  defect       |      Status:  new
>>>> Priority:  major        |   Milestone:
>>>> Component:  json-web-    |     Version:
>>>> signature              |  Resolution:
>>>> Severity:  -            |
>>>> Keywords:               |
>>>>=20
> =
-------------------------+----------------------------------------------
>>>> -------------------------+---
>>>>=20
>>>> Ticket URL:
> <http://trac.tools.ietf.org/wg/jose/trac/ticket/25#comment:1>
>>>> jose <http://tools.ietf.org/jose/>
>>>>=20
>>>> _______________________________________________
>>>> jose mailing list
>>>> jose@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jose
>>>=20
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>=20
>=20


--Apple-Mail=_F2A02399-2847-44C3-AC1E-A7A43A2B6155
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIN8TCCBjQw
ggQcoAMCAQICASAwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDI1NVoX
DTE3MTAyNDIxMDI1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAMsohUWcASz7GfKrpTOMKqANy9BV7V0igWdGxA8IU77L3aTxErQ+
fcxtDYZ36Z6GH0YFn7fq5RADteP0AYzrCA+EQTfi8q1+kA3m0nwtwXG94M5sIqsvs7lRP1aycBke
/s5g9hJHryZ2acScnzczjBCAo7X1v5G3yw8MDP2m2RCye0KfgZ4nODerZJVzhAlOD9YejvAXZqHk
sw56HzElVIoYSZ3q4+RJuPXXfIoyby+Y2m1E+YzX5iCZXBx05gk6MKAW1vaw4/v2OOLy6FZH3XHH
tOkzUreG//CsFnB9+uaYSlR65cdGzTsmoIK8WH1ygoXhRBm98SD7Hf/r3FELNvUCAwEAAaOCAa0w
ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBSuVYNv7DHKufcd
+q9rMfPIHeOsuzAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa
MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6
Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j
b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBADqpJw3I07QW
ke9plNBpxUxcffc7nUrIQpJHDci91DFG7fVhHRkMZ1J+BKg5UNUxIFJ2Z9B90Micc/NXcs7kPBRd
n6XGO/vPc87Y6R+cWS9Nc9+fp3Enmsm94OxOwI9wn8qnr/6o3mD4noP9JphwUPTXwHovjavRnhUQ
HLfo/i2NG0XXgTHXS2Xm0kVUozXqpYpAdumMiB/vezj1QHQJDmUdPYMcp+reg9901zkyT3fDW/iv
JVv6pWtkh6Pw2ytZT7mvg7YhX3V50Nv860cV11mocUVcqBLv0gcT+HBDYtbuvexNftwNQKD5193A
7zN4vG7CTYkXxytSjKuXrpEatEiFPxWgb84nVj25SU5q/r1Xhwby6mLhkbaXslkVtwEWT3Van49r
KjlK4XrUKYYWtnfzq6aSak5u0Vpxd1rY79tWhD3EdCvOhNz/QplNa+VkIsrcp7+8ZhP1l1b2U6Ma
xIVteuVMD3X0vziIwr7jxYae9FZjbxlpUemqXjcC0QaFfN7qI0JsQMALL7iGRBg7K0CoOBzECdD3
fuZil5kU/LP9cr1BK31U0Uy651bFnAMMMkqhAChIbn0ei72VnbpSsrrSdF0BAGYQ8vyHae5aCg+H
75dVCV33K6FuxZrf09yTz+Vx/PkdRUYkXmZz/OTfyJXsUOUXrym6KvI2rYpccSk5MIIHtTCCBp2g
AwIBAgICHlwwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENv
bSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0x
MjAzMTgwNDMyNDhaFw0xNDAzMTkxMTA3MzJaMIGbMRkwFwYDVQQNExBHclRNNkxTN1gzNTc3OHM5
MQswCQYDVQQGEwJDTDEiMCAGA1UECBMZTWV0cm9wb2xpdGFuYSBkZSBTYW50aWFnbzEWMBQGA1UE
BxMNSXNsYSBkZSBNYWlwbzEVMBMGA1UEAxMMSm9obiBCcmFkbGV5MR4wHAYJKoZIhvcNAQkBFg9q
YnJhZGxleUBtZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCySuUEj3esFMs5
AZLAhPpyjp0DD+vAM+tFeXr8XahzgoOf5A3oJ0V4ejTwfzjpUlL0IOMsq+cr2NvHGzjBip6cp09v
eODO3yhztv1le1aQ6CzGAx/p0Fn8g+biVYGkJtKvex4MYNcSmITaVNleejtzbk6C5HgTpBqFykcA
FmN4RYrrmYwfbmCahF/kxjWTeq67nL4UJgIcTaLBTmPOr6YjceYbn35QwUvHV+NX7NOyVHDbpxAM
L+56nCN5hKnxLbqF9aKlVbBCPiOz8LtGg+2+3aLJ5T4tIfzWMbjCUBae2I4bVa2hdS5dZJwTGFyI
p4pYKd6bL2qqbFF8moFE54aVAgMBAAGjggQOMIIECjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFD8Dv8LEoSfOmqZmUvP2JpAz
Lbh5MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MH4GA1UdEQR3MHWBD2picmFkbGV5
QG1lLmNvbYEPamJyYWRsZXlAbWUuY29tgRBqYnJhZGxleUBtYWMuY29tgRF2ZTdqdGJAdmU3anRi
LmNvbYETamJyYWRsZXlAd2luZ2FhLmNvbYEXam9obi5icmFkbGV5QHdpbmdhYS5jb20wggIhBgNV
HSAEggIYMIICFDCCAhAGCysGAQQBgbU3AQICMIIB/zAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5z
dGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5j
b20vaW50ZXJtZWRpYXRlLnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRp
bmcgdG8gdGhlIENsYXNzIDIgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29t
cGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wgZwGCCsGAQUFBwICMIGP
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQIaZExpYWJpbGl0eSBhbmQg
d2FycmFudGllcyBhcmUgbGltaXRlZCEgU2VlIHNlY3Rpb24gIkxlZ2FsIGFuZCBMaW1pdGF0aW9u
cyIgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeS4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2Ny
bC5zdGFydHNzbC5jb20vY3J0dTItY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcw
AYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczIvY2xpZW50L2NhMEIGCCsGAQUF
BzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MyLmNsaWVudC5jYS5j
cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IB
AQARx8Pg+Yetf5bfNo/8qxHiDAsAvRRNozPXhIieDpr0XeRvxkNtNSd5L25uCmp4lA/YgVzRTmBC
cndd4Ifqn0jzya+bU2opDDxa9+CVLRohLX29+lOBclI90g7Ykk9GpoG1d/fOR1cnByRf3900yssZ
4a9oVP19Q11B0dTgEjWlVSmAqvv3pPstNz8RF8fyIWnX4KZ1WQnpjaIl1ZSniHXteZvFshPQJ1Lh
JKT9VbwsWyf+ZXPqEHvdW2HCMawiS7nhanilG6rUpf6kBOdGTekdFrXPebEkyars4RcQ1wJWb5sC
fJSthtSKU1L1RVNhLz/d1WwqI26kFo5k7686AmpUMYIDbDCCA2gCAQEwgZMwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0
aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJt
ZWRpYXRlIENsaWVudCBDQQICHlwwCQYFKw4DAhoFAKCCAa0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNjI3MTY1MTQ2WjAjBgkqhkiG9w0BCQQxFgQUxAnv6+Rj
najoSSVxR3cI6p1v73IwgaQGCSsGAQQBgjcQBDGBljCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNV
BAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xp
ZW50IENBAgIeXDCBpgYLKoZIhvcNAQkQAgsxgZaggZMwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK
Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAyIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQICHlwwDQYJKoZIhvcNAQEBBQAEggEAcqeZVv0KAjN1x3zoeXLhkWa5Pyd2YtzwxPYRifsN
zgIzk4zxtZxtlHiQFQzncBwGSN1EKaN/4/enDVyDaUc2N+EB3NV4lgEXyckvleG3mmBrP5F+i+Ai
p86PbqTPi7pQWx/UEWT2DqrCONTf+8qglClDhFSqUtqG1C/sUGIhsATdMba+MSqATsw+1N0tORFG
MIpcp6j4m6Rl9NEwO8F2D7hjhOZNagvtn0tvhMF4uAY5ZbNm2YzWaj3CLNEXUA7mVIHe9LY6TU/u
r3gsQSxLmb9xls2UylNmQssWYa/9Cn6LHQ485Vy8gYALGWQehQSvDd9jc4WfvIg7qr3pAAkWawAA
AAAAAA==

--Apple-Mail=_F2A02399-2847-44C3-AC1E-A7A43A2B6155--

From ietf@augustcellars.com  Thu Jun 27 10:08:08 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF7421F9A3C for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.819
X-Spam-Level: 
X-Spam-Status: No, score=-2.819 tagged_above=-999 required=5 tests=[AWL=0.780,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzxfcYdcUJPk for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:08:03 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 84A6721F99A0 for <jose@ietf.org>; Thu, 27 Jun 2013 10:08:01 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id A28AC38F22; Thu, 27 Jun 2013 10:08:01 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <draft-ietf-jose-json-web-signature@tools.ietf.org>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 10:07:04 -0700
Message-ID: <04a601ce7358$bfeade80$3fc09b80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvAtXnsooCfmP1+wE/Pt+eAksevJyZN6A8cA==
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 17:08:08 -0000

When the volume is high is when one needs to keep track of the what is =
going on.  If the volume is low then you can ignore it.

There have not been any recent discussions on parsers but I don't know =
what you mean by improved so I cannot make a statement one way or the =
other on that.  I have always had the mail moved into a folder and go in =
and read it in one big shot once or twice a day unless I am currently =
involved in a discussion.  I find that technique works well.

Jim


> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Wednesday, June 26, 2013 9:07 PM
> To: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional =
text
>=20
> The alternative is to say that producers MUST NOT produce JSON with
> duplicate member names and that consumers are strongly RECOMMENDED to
> reject input with duplicate member names and leave it at that.
>=20
> I understand not wanting to require customer parsers if the underlying
> platform parsers are deficient.  But I really hope that the JSON WG =
will have
> more sense than to allow the current madness to continue.  As I =
understood
> it, the primary motivation for the JSON WG in the first place was to =
change the
> SHOULD to a MUST.  If they don't do that, I'm really not sure what the =
point of
> it is.
>=20
> 				-- Mike
>=20
> P.S.  I am a subscriber to the JSON mailing list, but unfortunately, =
the volume
> got so high a few weeks ago that trying to keep up with it became an
> impediment to getting real work done.  At that point I created a rule =
to file
> those messages into a folder, which I only rarely look at.  Has that =
situation
> improved?
>=20
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Wednesday, June 26, 2013 8:18 PM
> To: Mike Jones; draft-ietf-jose-json-web-signature@tools.ietf.org
> Cc: jose@ietf.org
> Subject: RE: [jose] #27: member names MUST be unique needs additional =
text
>=20
> I would strongly encourage everyone in the JOSE list to join the JSON =
list and
> read what was is there and participate.
>=20
> That being said there are situations where you might not be able to do =
an
> independent parser.  And in fact what you have stated is that there is =
now a
> requirement that a JOSE library supply a JSON parser.  Is that really =
what we
> want to say?  How far from creating a set of generator and parser
> requirements that are non standard and requiring a parser/generator =
are we
> from that?
>=20
> > -----Original Message-----
> > From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> > Sent: Wednesday, June 26, 2013 12:30 PM
> > To: Jim Schaad; draft-ietf-jose-json-web-signature@tools.ietf.org
> > Cc: jose@ietf.org
> > Subject: RE: [jose] #27: member names MUST be unique needs =
additional
> > text
> >
> > The operable sentence in my suggested text below is this one: "If =
the
> > platform's JSON parser does not reject input with duplicate member
> > names, the input will first need to be separately parsed to reject
> > these invalid inputs before using the platform's parser".  In other
> > words, if the JSON parser in the development platform you are using
> > does not reject inputs with duplicate member names, you will need to
> > write a separate JSON parser that detects this invalid input and =
rejects it.
> >
> > This parser could either just be a validator, returning TRUE or =
FALSE
> > for whether the JSON is valid for JOSE - in which case you'd then =
pass
> > any inputs validating as TRUE to the platform's JSON parser, or it
> > could be a replacement parser, in which case your code would not use
> > the development platform's JSON parser at all.  I suspect people =
would
> > be more likely to do the former than the latter, but both approaches =
are
> equivalent.
> >
> > BTW, if it's your sense that there's a problem occurring in the JSON
> > working group with respect to enabling strict JSON parsing, we
> > probably need to become active there.  For instance, even if the =
spec
> > allows duplicate member names like the ECMA spec does, the RFC could
> > recommend or require that parsers support a "strict" mode, which =
rejects
> these unnecessarily lax inputs.
> > Then JOSE implementations could use that.
> >
> > 				-- Mike
> >
> > -----Original Message-----
> > From: Jim Schaad [mailto:ietf@augustcellars.com]
> > Sent: Wednesday, June 26, 2013 11:30 AM
> > To: 'jose issue tracker';
> > draft-ietf-jose-json-web-signature@tools.ietf.org;
> > Mike Jones
> > Cc: jose@ietf.org
> > Subject: RE: [jose] #27: member names MUST be unique needs =
additional
> > text
> >
> > <no hat>
> >
> > I consider myself to be reasonably competent in both English and
> > Technical English.  I have no idea what I am supposed to be doing to
> > deal with the text below.  Does this mean that I need to write an
> > independent parser?  What about cases where it is coming in on a
> > stream and I don't get to see the data before the parse occurs?  How
> > are they interpreted differently?  What exactly is this supposed to =
be
> > addressing.  Much of this could be skipped when we said don't do it.
> > Since this is no longer a viable statement due to the state of =
parsers, we
> need to be more explicit and say what is going on.
> >
> > No I don't consider the suggested text to be adequate.
> >
> > > -----Original Message-----
> > > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On =
Behalf
> > > Of jose issue tracker
> > > Sent: Tuesday, June 25, 2013 5:41 PM
> > > To: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > > michael.jones@microsoft.com
> > > Cc: jose@ietf.org
> > > Subject: Re: [jose] #27: member names MUST be unique needs
> > > additional text
> > >
> > > #27: member names MUST be unique needs additional text
> > >
> > >
> > > Comment (by michael.jones@microsoft.com):
> > >
> > >  The JWS draft currently says:
> > >
> > >          The Header Parameter Names within the JWS Header MUST be
> unique;
> > >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> > >
> > >  How about changing this to:
> > >
> > >          The Header Parameter Names within the JWS Header MUST be
> unique;
> > >          JWSs with duplicate Header Parameter Names MUST be =
rejected.
> > >          This is necessary to prevent attacks in which the same =
JWS
> > > might  be interpreted
> > >          in different ways by different implementations and to
> > > prevent
> > attackers
> > >          from hiding extra content in duplicate member values.
> > >          If the platform s JSON parser does not reject input with
> > > duplicate member names,
> > >          the input will first need to be separately parsed to =
reject
> > > these  invalid inputs
> > >          before using the platform s parser.
> > >
> > > --
> > > =
-------------------------+------------------------------------------
> > > -------------------------+--
> > > -------------------------+--
> > > -------------------------+---
> > >  Reporter:               |       Owner:  draft-ietf-jose-json-web-
> > >   ietf@augustcellars.com |  signature@tools.ietf.org
> > >      Type:  defect       |      Status:  new
> > >  Priority:  major        |   Milestone:
> > > Component:  json-web-    |     Version:
> > >   signature              |  Resolution:
> > >  Severity:  -            |
> > >  Keywords:               |
> > > =
-------------------------+------------------------------------------
> > > -------------------------+--
> > > -------------------------+--
> > > -------------------------+---
> > >
> > > Ticket URL:
> > > <http://trac.tools.ietf.org/wg/jose/trac/ticket/27#comment:1>
> > > jose <http://tools.ietf.org/jose/>
> > >
> > > _______________________________________________
> > > jose mailing list
> > > jose@ietf.org
> > > https://www.ietf.org/mailman/listinfo/jose
>=20



From ietf@augustcellars.com  Thu Jun 27 10:11:15 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9815821F9E77 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.649,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKVpAIJYcJ5D for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:11:09 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7E56721F9E75 for <jose@ietf.org>; Thu, 27 Jun 2013 10:11:09 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id DB4D52C9FE; Thu, 27 Jun 2013 10:11:08 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'John Bradley'" <ve7jtb@ve7jtb.com>, "'Tim Bray'" <tbray@textuality.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 10:10:12 -0700
Message-ID: <04ba01ce7359$2f946120$8ebd2360$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04BB_01CE731E.8337FA20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGqOaFgm5bSrTowyJkuz8ggVcVAJQJ0/9dvAtXnsooCfmP1+wE/Pt+eAksevJwBgJ6Q/AKiJ4UHAcTplCQBWG5bvQLZ0+mqAXMi1n4BLTjXupjRzw7Q
Content-Language: en-us
Cc: "'Manger, James H'" <James.H.Manger@team.telstra.com>, jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 17:11:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04BB_01CE731E.8337FA20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Except for the parsers which only return the nth name (according to the JSON
list they exist) it at least provides a degree of predictability.

 

The JSON list would point out that you want to allow duplicate field names
for the purposes of putting comments into output using the name "//".

 

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Thursday, June 27, 2013 9:43 AM
To: John Bradley; Tim Bray
Cc: Manger, James H; Jim Schaad; jose@ietf.org;
draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: RE: [jose] #27: member names MUST be unique needs additional text

 

I've come to believe that James' proposed language does a good job of making
security-appropriate restrictions while allowing the use of existing
parsers.  It was:

 

A creator of a JOSE message MUST NOT put duplicate names in any JSON object
in a JOSE header.  To prevent attacks where a JOSE message is interpreted as
different valid messages by different recipients, each recipient MUST either
reject messages with duplicate names or accept only the last name.

 

I might change "or accept only the last name" to "or use a parser that
always uses the lexically last name for any duplicate member names, per
[ECMAScript]" for clarity, but the intent is the same.

 

Would that work for people?

 

                                                            -- Mike

 

From: John Bradley [mailto:ve7jtb@ve7jtb.com] 
Sent: Thursday, June 27, 2013 8:49 AM
To: Tim Bray
Cc: Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org;
draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text

 

The problem is not wanting to leave a hole for malicious signers to create
JWT that may be misinterpreted by the receiver.  Accidental interop problems
from bad signers are not a big concern for me and are covered by MUST NOT
emit dups.

 

Accepting malformed JSON as the envelope may lead to real security issues.

 

This may be more of an issue for the JSON encoding than the compact as there
you need to be careful the body you process for the signature is the body
that the application uses.

 

What happens if you receive.

 

{"protected":<integrity-protected shared header contents>",
      "unprotected":<non-integrity-protected shared header contents>",
      "payload":"<original payload contents>",
      "payload":"<bad payload contents inserted by attacker>"
      "signatures":[
       {"header":"<per-signature unprotected header 1 contents>",
        "signature":"<signature 1 contents>"},
       ...
       {"header":"<per-signature unprotected header N contents>",
        "signature":"<signature N contents>"}],
     }

 

If the JOSE library validates on the first version of "payload" and the
application using a different JSON parser only sees the second "payload" we
have a wrapping attack similar to xmldsig.

 

I can't off the top of my head think of what you could do in the compact
serialization that would lead to a successful attack given that the
signature is over the base64url encoded segments, that prevents attackers
from modifying the JSON while maintaining integrity.

 

It is a real issue for the JSON serialization though.

 

John B.

 

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com> wrote:

 

The approach just seems wrong.  If we require that conforming
implementations MUST NOT emit dupes, then authors of receiving software can
just pick the best-performing parser with the nicest API, because they *all*
perform correctly when there are no dupes.  

Who's going to own the responsibility for making the authoritative finding
that of the many JSON parsers in the Java ecosystem, these ones, but not
those ones, are usable in JOSE applications?  And suppose one that has been
previously OK is quietly optimized on GitHub to run 30% faster and as a
side-effect silently ignores dupes?  

The benefit of using JSON is that there is widely deployed software to
handle it.  It is a known problem that sloppy spec drafting has allowed
various kinds of problems to occur when dupe keys are received. "Doctor, it
hurts when I do this." "So... don't do that."

Are we also going to specify the behavior of receiving software when the
JSON has a misplaced quotation mark?  A missing trailing "}"?

 -T

 

 

On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:

Most JSON libraries that silently accept [sob] dupe keys at least
consistently use the last key. Allowing just that behaviour (or rejecting
dupes), while forbidding acceptance of a non-last dupe (eg first key), is
safe and allows most JSON libraries to be used. Since this accepts most
libraries I think it is practical.

 

Hence I suggest:

 

>   A creator of a JOSE message MUST NOT put duplicate names in any JSON

> object in a JOSE header.

>   To prevent attacks where a JOSE message is interpreted as different

> valid messages by different recipients, each recipient MUST either

> reject messages with duplicate names or accept only the last name.

 

This isn't "truly predictable" as a message with dupes might be accepted or
rejected. The crucial point is that if a message is accepted it is
predictable.

 

--

James Manger

 

From: Tim Bray [mailto:tbray@textuality.com] 
Sent: Thursday, 27 June 2013 4:16 PM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org;
draft-ietf-jose-json-web-signature@tools.ietf.org


Subject: Re: [jose] #27: member names MUST be unique needs additional text

 

 

Well, you have a practical problem in that most implementers will want to
use a standard JSON library, which is good practice because it will be
well-debugged, and most libraries [sob] silently take care of dupe keys and
don't have a way to tell the client software what happened. So if you want
truly predictable behavior, you're forcing the use of hand-constructed JSON
parsers. And that sucks, because getting good performance in JSON parsing is
surprisingly hard, with dramatic performance differences between
implementations. So you're forcing receiving software which wants to be
conformant to use a hand-rolled parser which will probably have lousy
performance and have other bugs which in fact may compromise security more
than dupe-key tricks could.  -T

 

On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:

> I think it's a nice clean minimal solution to say that producers MUST
> NOT generate dupes, end of story.  I don't think saying anything beyond
> that adds value. -T

Clean and minimal that may be, but it ignores the security issue. We don't
want a malicious producer (who is so malicious they ignore a MUST) to create
JOSE messages that a JOSE-compliant security layer accepts as "benign
interpretation #1" so it passes the message on to the JOSE-compliant backend
app that acts on "nasty interpretation #2".

--
James Manger

 

 

 


------=_NextPart_000_04BB_01CE731E.8337FA20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Except for the parsers which only return the nth name (according to =
the JSON list they exist) it at least provides a degree of =
predictability.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The JSON list would point out that you want to allow duplicate field =
names for the purposes of putting comments into output using the name =
&#8220;//&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Thursday, June 27, 2013 9:43 AM<br><b>To:</b> John Bradley; Tim =
Bray<br><b>Cc:</b> Manger, James H; Jim Schaad; jose@ietf.org; =
draft-ietf-jose-json-web-signature@tools.ietf.org<br><b>Subject:</b> RE: =
[jose] #27: member names MUST be unique needs additional =
text<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I&#8217;ve come to believe that James&#8217; proposed language does a =
good job of making security-appropriate restrictions while allowing the =
use of existing parsers.&nbsp; It was:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>A creator of a JOSE message MUST NOT put duplicate names in any JSON =
object in a JOSE header.&nbsp; To prevent attacks where a JOSE message =
is interpreted as different valid messages by different recipients, each =
recipient MUST either reject messages with duplicate names or accept =
only the last name.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I might change &#8220;or accept only the last name&#8221; to =
&#8220;or use a parser that always uses the lexically last name for any =
duplicate member names, per [ECMAScript]&#8221; for clarity, but the =
intent is the same.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Would that work for people?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- =
Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
John Bradley [<a =
href=3D"mailto:ve7jtb@ve7jtb.com">mailto:ve7jtb@ve7jtb.com</a>] =
<br><b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br><b>To:</b> Tim =
Bray<br><b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">draft-i=
etf-jose-json-web-signature@tools.ietf.org</a><br><b>Subject:</b> Re: =
[jose] #27: member names MUST be unique needs additional =
text<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The problem =
is not wanting to leave a hole for malicious signers to create JWT that =
may be misinterpreted by the receiver. &nbsp;Accidental interop problems =
from bad signers are not a big concern for me and are covered by MUST =
NOT emit dups.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Accepting malformed JSON as the envelope may lead to =
real security issues.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>This may be more of an issue for the JSON encoding =
than the compact as there you need to be careful the body you process =
for the signature is the body that the application =
uses.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>What happens if you =
receive.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>{&quot;protected&quot;:&lt;integrity-protected=
 shared header contents&gt;&quot;,<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;unprotected&quot;:&lt;non-integrity-protected shared header =
contents&gt;&quot;,<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;payload&quot;:&quot;&lt;original payload =
contents&gt;&quot;,<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;payload&quot;:&quot;&lt;bad payload contents inserted by =
attacker&gt;&quot;<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;signatures&quot;:[<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header 1 =
contents&gt;&quot;,<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;signature&quot;:&quot;&lt;signature 1 =
contents&gt;&quot;},<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
...<o:p></o:p></span></pre><pre style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header N =
contents&gt;&quot;,<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;signature&quot;:&quot;&lt;signature N =
contents&gt;&quot;}],<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; =
}<o:p></o:p></span></pre><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If the JOSE library validates on the first version of =
&quot;payload&quot; and the application using a different JSON parser =
only sees the second &quot;payload&quot; we have a wrapping attack =
similar to xmldsig.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
can't off the top of my head think of what you could do in the compact =
serialization that would lead to a successful attack given that the =
signature is over the base64url encoded segments, that prevents =
attackers from modifying the JSON while maintaining =
integrity.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>It is a real issue for the JSON serialization =
though.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>John B.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><div><p =
class=3DMsoNormal>On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a =
href=3D"mailto:tbray@textuality.com">tbray@textuality.com</a>&gt; =
wrote:<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>The approach just seems =
wrong.&nbsp; If we require that conforming implementations MUST NOT emit =
dupes, then authors of receiving software can just pick the =
best-performing parser with the nicest API, because they *all* perform =
correctly when there are no dupes.&nbsp; <br><br>Who&#8217;s going to =
own the responsibility for making the authoritative finding that of the =
many JSON parsers in the Java ecosystem, these ones, but not those ones, =
are usable in JOSE applications?&nbsp; And suppose one that has been =
previously OK is quietly optimized on GitHub to run 30% faster and as a =
side-effect silently ignores dupes?&nbsp; <o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>The benefit of using =
JSON is that there is widely deployed software to handle it.&nbsp; It is =
a known problem that sloppy spec drafting has allowed various kinds of =
problems to occur when dupe keys are received. &#8220;Doctor, it hurts =
when I do this.&#8221; &#8220;So... don&#8217;t do =
that.&#8221;<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Are we also going to specify the behavior =
of receiving software when the JSON has a misplaced quotation =
mark?&nbsp; A missing trailing =
&#8220;}&#8221;?<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;-T<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H =
&lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; =
wrote:<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Most JSON libraries that silently accept [sob] dupe keys at least =
consistently use the last key. Allowing just that behaviour (or =
rejecting dupes), while forbidding acceptance of a non-last dupe (eg =
first key), is safe and allows most JSON libraries to be used. Since =
this accepts most libraries I think it is practical.</span><span =
lang=3DEN-AU><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-AU><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hence I suggest:</span><span =
lang=3DEN-AU><o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-AU><o:p></o:p></span></p><p><span =
lang=3DEN-AU>&gt; &nbsp;&nbsp;A creator of a JOSE message MUST NOT put =
duplicate names in any JSON<o:p></o:p></span></p><p><span =
lang=3DEN-AU>&gt; object in a JOSE header.<o:p></o:p></span></p><p><span =
lang=3DEN-AU>&gt; &nbsp;&nbsp;To prevent attacks where a JOSE message is =
interpreted as different<o:p></o:p></span></p><p><span lang=3DEN-AU>&gt; =
valid messages by different recipients, each recipient MUST =
either<o:p></o:p></span></p><p><span lang=3DEN-AU>&gt; reject messages =
with duplicate names or accept only the last =
name.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-AU><o:p></o:p></span></p></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This isn&#8217;t &#8220;truly predictable&#8221; as a message with =
dupes might be accepted or rejected. The crucial point is that if a =
message is accepted it is predictable.</span><span =
lang=3DEN-AU><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-AU><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>--</span><span lang=3DEN-AU><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>James Manger</span><span lang=3DEN-AU><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><span lang=3DEN-AU><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Tim Bray [mailto:<a href=3D"mailto:tbray@textuality.com" =
target=3D"_blank">tbray@textuality.com</a>] <br><b>Sent:</b> Thursday, =
27 June 2013 4:16 PM<br><b>To:</b> Manger, James H<br><b>Cc:</b> Mike =
Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" =
target=3D"_blank">jose@ietf.org</a>; <a =
href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org" =
target=3D"_blank">draft-ietf-jose-json-web-signature@tools.ietf.org</a></=
span><span lang=3DEN-AU><o:p></o:p></span></p><div><p =
class=3DMsoNormal><span lang=3DEN-AU><br><b>Subject:</b> Re: [jose] #27: =
member names MUST be unique needs additional =
text<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
lang=3DEN-AU><o:p>&nbsp;</o:p></span></p></div></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU>&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU>Well, you have a practical problem in that most =
implementers will want to use a standard JSON library, which is good =
practice because it will be well-debugged, and most libraries [sob] =
silently take care of dupe keys and don&#8217;t have a way to tell the =
client software what happened. So if you want truly predictable =
behavior, you&#8217;re forcing the use of hand-constructed JSON parsers. =
And that sucks, because getting good performance in JSON parsing is =
surprisingly hard, with dramatic performance differences between =
implementations. So you&#8217;re forcing receiving software which wants =
to be conformant to use a hand-rolled parser which will probably have =
lousy performance and have other bugs which in fact may compromise =
security more than dupe-key tricks could.&nbsp; =
-T<o:p></o:p></span></p></div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
lang=3DEN-AU>&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU>On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H &lt;<a =
href=3D"mailto:James.H.Manger@team.telstra.com" =
target=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; =
wrote:<o:p></o:p></span></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
lang=3DEN-AU>&gt; I think it&#8217;s a nice clean minimal solution to =
say that producers MUST<br>&gt; NOT generate dupes, end of story.&nbsp; =
I don&#8217;t think saying anything beyond<br>&gt; that adds value. =
-T<o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU>Clean and minimal that may be, but it ignores the security =
issue. We don't want a malicious producer (who is so malicious they =
ignore a MUST) to create JOSE messages that a JOSE-compliant security =
layer accepts as &quot;benign interpretation #1&quot; so it passes the =
message on to the JOSE-compliant backend app that acts on &quot;nasty =
interpretation #2&quot;.<br><br>--<br>James =
Manger<o:p></o:p></span></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-AU>&nbsp;<o:p></o:p></span></p></div></div></div></div></div><p=
 class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_04BB_01CE731E.8337FA20--


From ietf@augustcellars.com  Thu Jun 27 10:12:29 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE83721F9D69 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.042
X-Spam-Level: 
X-Spam-Status: No, score=-3.042 tagged_above=-999 required=5 tests=[AWL=0.557,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5OWYN5TOcaP for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 10:12:24 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 88FB221F9E76 for <jose@ietf.org>; Thu, 27 Jun 2013 10:12:21 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 3D42838F00; Thu, 27 Jun 2013 10:12:21 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, "'n-sakimura'" <n-sakimura@nri.co.jp>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 10:11:24 -0700
Message-ID: <04bf01ce7359$5ab862c0$10292840$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFbtMM0AVMbmndwUUG6vntocHGkoALWvDclApUnp/sBuDIBRgE/jA4aApzLX2SZ10WFIA==
Content-Language: en-us
Cc: jose@ietf.org, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 17:12:29 -0000

No, my motivation is to allow for a smaller version of the payload =
string.  In some cases quoting it will generate a smaller string than =
doing the base64 conversion on the string.



> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> Sent: Thursday, June 27, 2013 9:49 AM
> To: Jim Schaad; 'n-sakimura'
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
> Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded
>=20
> Jim, you wrote "If I am not transporting the base64url encoded =
content,
> because it is not in the "payload" field, then why should I need to =
base64
> encode it just to validate the signature.  This is the alto case."
>=20
> So am I correct then, in thinking that your motivation for #26 is =
actually #25 -
> Detached content for the ALTO use case?  As John and Nat had written, =
this
> could be handled by the specs as they are today by signing a hash of =
the
> detached content and including a compact JWS representing that =
signature as
> an x-alto-signature header.  That doesn't require changing the =
signature
> calculation.
>=20
> 				-- Mike
>=20
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com]
> Sent: Thursday, June 27, 2013 9:41 AM
> To: 'n-sakimura'
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones;
> jose@ietf.org
> Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded
>=20
> Nat,
>=20
> The only thing that can be signed or encrypted is an octet string. (A =
slight over
> generalization. GOST for example hashes an integer, tree hashes can do
> strange things but a sufficiently true statement for our purposes.)
>=20
> A that being said - yes case 1 would be something you can do.  Case #2 =
would
> not be something that you can do because it is not an octet string.
>=20
> If you are looking at JavaScript, in order to hash something as an =
octet string it
> can be one of three things.  A UInt8Array, an Int8Array and, due to
> convention, a string where the top byte of all of the code points in =
the string is
> zero.
>=20
> We currently don't have an efficient way to encode the Uint8Array =
case,
> although that might not be true if we are looking at new ECMA =
specifications
> which apparently are adding more defined types and serialization =
methods for
> those types.
>=20
> > -----Original Message-----
> > From: n-sakimura [mailto:n-sakimura@nri.co.jp]
> > Sent: Wednesday, June 26, 2013 7:55 PM
> > To: Jim Schaad
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > michael.jones@microsoft.com; jose@ietf.org
> > Subject: Re: [jose] #26: Allow for signature payload to not be =
base64
> > encoded
> >
> > Let me understand the problem.
> >
> > Are you suggesting that we should be able to do something like:
> >
> > Case 1:
> >
> >       {"protected":<integrity-protected shared header contents>",
> >        "unprotected":<non-integrity-protected shared header =
contents>",
> >        "payload":"this is a multi\nline text payload of which a line
> > can be very very very long and wrapped during transmission. "
> >        "signatures":[
> >         {"header":"<per-signature unprotected header 1 contents>",
> >          "signature":"<signature 1 contents>"},
> >         ...
> >         {"header":"<per-signature unprotected header N contents>",
> >          "signature":"<signature N contents>"}],
> >       }
> >
> > or even
> >
> > Case 2:
> >
> >       {"protected":<integrity-protected shared header contents>",
> >        "unprotected":<non-integrity-protected shared header =
contents>",
> >        "payload":{
> > 	"this":"is a json",
> > 	"payload":"which is not base64url encoded"
> >        }
> >        "signatures":[
> >         {"header":"<per-signature unprotected header 1 contents>",
> >          "signature":"<signature 1 contents>"},
> >         ...
> >         {"header":"<per-signature unprotected header N contents>",
> >          "signature":"<signature N contents>"}],
> >       }
> >
> > Then, I am worried about allowing them because in general we would =
not
> > know what would a transmission mechanism and user agents (including
> > text
> > editors) would do to them, like Mike mentioned. I do not think we
> > should assume the property of the transmission mechanism in JOSE =
level.
> > Assuming that would cause brittleness in the implementations.
> >
> > For detached signature, I do not understand why you would want non-
> > base64url encoded payload. The application should define how to hash
> > the octet stream that it wants to calculate signature over it, and =
we
> > can just include the base64url encoded hash in the "payload".
> > Why would you like to do other encoding for the hash?
>=20
> If I am not transporting the base64url encoded content, because it is =
not in
> the "payload" field, then why should I need to base64 encode it just =
to
> validate the signature.  This is the alto case.
>=20
> Jim
>=20
> >
> > --
> > Nat Sakimura (n-sakimura@nri.co.jp)
> > Nomura Research Institute
> >
> > PLEASE READ:
> > The information contained in this e-mail is confidential and =
intended
> > for the named recipient(s) only.
> > If you are not an intended recipient of this e-mail, you are hereby
> > notified that any review, dissemination, distribution or duplication
> > of this message is strictly prohibited. If you have received this
> > message in error, please notify the sender immediately and delete =
your
> copy from your system.



From rlb@ipv.sx  Thu Jun 27 15:24:19 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C144F11E8108 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.976
X-Spam-Level: 
X-Spam-Status: No, score=-4.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xZv7RW78Qkn for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:24:15 -0700 (PDT)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id C9EC511E80F2 for <jose@ietf.org>; Thu, 27 Jun 2013 15:24:14 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id o6so1557613oag.27 for <jose@ietf.org>; Thu, 27 Jun 2013 15:24:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+Ps6iTM0X+lWATMD5I8avej0RduouZf6DpvNuyQhFME=; b=lSt0bgfs07xh70E/4O/hULRLyiGcWlJEgCTJAhVCLSPg5DjQlDhhCehhsNSLAph9OF mc0w6cABgrA5F5+wWVkPvRbfQ5XAG+ajSiH7j52Xamgim/Ovrb5Hs0kM0dJyUVKrNJ61 21+pg/WBvfCjx4tYAUmrvo1fyTENML+i+ZArDDutADF4oP6LJqU74GfcWOrD6ROI+S+v YNZRz8rERJuyxjdmn1PYUjDhHTOUL3ANaMR9NvVp3dhA1NN2AcTVjbeqlBAerU6NMR6m W3b9HMhURLE3tDs6x3AEdDIqB62P9HkHQzXheiR32VNzSbPH0lVGETVsH/A7xsU5ISsN SVTQ==
MIME-Version: 1.0
X-Received: by 10.60.43.226 with SMTP id z2mr3981799oel.76.1372371846728; Thu, 27 Jun 2013 15:24:06 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 27 Jun 2013 15:24:06 -0700 (PDT)
X-Originating-IP: [192.1.51.93]
In-Reply-To: <04bf01ce7359$5ab862c0$10292840$@augustcellars.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com>
Date: Thu, 27 Jun 2013 18:24:06 -0400
Message-ID: <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a11333dce6ca1fd04e02a38c2
X-Gm-Message-State: ALoCoQnPcpOIA5s3ln9p/9Uz0l9lEVY+IAUFdhJfgJbuSwcM78EhtTiwLZABti2IgxMRB4Qbl1R/
Cc: Mike Jones <Michael.Jones@microsoft.com>, n-sakimura <n-sakimura@nri.co.jp>, "jose@ietf.org" <jose@ietf.org>, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:24:19 -0000

--001a11333dce6ca1fd04e02a38c2
Content-Type: text/plain; charset=ISO-8859-1

I think there are two separable issues here, both of which Mike and I
probably have divergent opinions on :)
1. Syntax: Should it be possible for the "payload" field JWS to be a JSON
string (instead of base64) when the payload is simply a UTF-8 string?
2. Crypto: Must the JWS Signing Input be base64url encoded.

The current answers to these questions are:
1. It is not possible.  Payload is always base64url encoded.
2. It is always base64url encoded.

The answers should be:
1. The payload should not be base64url encoded unless it cannot be
represented as a JSON string.
2. The JWS Signing Input should not be base64url encoded unless there is a
JWS Protected Header

Neither of these are complicated changes:
1. Add a "b64" header parameter that indicates that the payload is
base64url-encoded binary, as opposed to a UTF-8 string.  Specify that this
parameter is on by default in compact-formatted JWS objects.
2. Modify the signing/verification instructions to switch based on the
presence of a JWS Protected Header: "If the JWS Protected Header is absent
or empty, then the JWS Signing Input is simply the JWS Payload (not
encoded).  If the JWS Protected Header has a non-empty value, then the the
JWS Signing Input is the concatenation of the Encoded JWS Header, a period
('.') character, and the Encoded JWS Payload"

There are two reasons for these, both of which are important to make sure
that this spec is applicable to a broad variety of use cases:
1. Compactness.  As Jim notes, quoted strings are shorter than
base64url-encoded strings
2. Crypto-compatibility: Avoiding base64-encoding means that there's
nothing JWS-specific about the signature value.  So for example, you could
translate a JWS with no protected attributes to a CMS SignedData object
with no protected attributes.

This email brought to you by the number 2 and the letters J, W, and S :)

--Richard

[1] Note that the default value for this header must be false, or else you
lose the compactness advantage!
[2] You could also do this as a "Content-Encoding" equivalent, "cenc":
"b64".  That would give you "base64 agility", as some folks have asked for,
since you could have "b64" and "b64u" values.
[3] You could also do this like CMS, and have the JWS Signing Input in the
latter case be "the concatenation of the Encoded JWS Header, a period ('.')
character, and the Encoded JWS Payload Hash".  Where the Encoded JWS
Payload Hash is the base64url-encoded version of the hash you would
otherwise be signing.  This seems simpler to code, since you just digest
the body, then if there's a protected header, you digest again.  But it
also breaks with existing code.





On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> No, my motivation is to allow for a smaller version of the payload string.
>  In some cases quoting it will generate a smaller string than doing the
> base64 conversion on the string.
>
>
>
> > -----Original Message-----
> > From: Mike Jones [mailto:Michael.Jones@microsoft.com]
> > Sent: Thursday, June 27, 2013 9:49 AM
> > To: Jim Schaad; 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Jim, you wrote "If I am not transporting the base64url encoded content,
> > because it is not in the "payload" field, then why should I need to
> base64
> > encode it just to validate the signature.  This is the alto case."
> >
> > So am I correct then, in thinking that your motivation for #26 is
> actually #25 -
> > Detached content for the ALTO use case?  As John and Nat had written,
> this
> > could be handled by the specs as they are today by signing a hash of the
> > detached content and including a compact JWS representing that signature
> as
> > an x-alto-signature header.  That doesn't require changing the signature
> > calculation.
> >
> >                               -- Mike
> >
> > -----Original Message-----
> > From: Jim Schaad [mailto:ietf@augustcellars.com]
> > Sent: Thursday, June 27, 2013 9:41 AM
> > To: 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones;
> > jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Nat,
> >
> > The only thing that can be signed or encrypted is an octet string. (A
> slight over
> > generalization. GOST for example hashes an integer, tree hashes can do
> > strange things but a sufficiently true statement for our purposes.)
> >
> > A that being said - yes case 1 would be something you can do.  Case #2
> would
> > not be something that you can do because it is not an octet string.
> >
> > If you are looking at JavaScript, in order to hash something as an octet
> string it
> > can be one of three things.  A UInt8Array, an Int8Array and, due to
> > convention, a string where the top byte of all of the code points in the
> string is
> > zero.
> >
> > We currently don't have an efficient way to encode the Uint8Array case,
> > although that might not be true if we are looking at new ECMA
> specifications
> > which apparently are adding more defined types and serialization methods
> for
> > those types.
> >
> > > -----Original Message-----
> > > From: n-sakimura [mailto:n-sakimura@nri.co.jp]
> > > Sent: Wednesday, June 26, 2013 7:55 PM
> > > To: Jim Schaad
> > > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > > michael.jones@microsoft.com; jose@ietf.org
> > > Subject: Re: [jose] #26: Allow for signature payload to not be base64
> > > encoded
> > >
> > > Let me understand the problem.
> > >
> > > Are you suggesting that we should be able to do something like:
> > >
> > > Case 1:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>",
> > >        "payload":"this is a multi\nline text payload of which a line
> > > can be very very very long and wrapped during transmission. "
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > or even
> > >
> > > Case 2:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>",
> > >        "payload":{
> > >     "this":"is a json",
> > >     "payload":"which is not base64url encoded"
> > >        }
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > Then, I am worried about allowing them because in general we would not
> > > know what would a transmission mechanism and user agents (including
> > > text
> > > editors) would do to them, like Mike mentioned. I do not think we
> > > should assume the property of the transmission mechanism in JOSE level.
> > > Assuming that would cause brittleness in the implementations.
> > >
> > > For detached signature, I do not understand why you would want non-
> > > base64url encoded payload. The application should define how to hash
> > > the octet stream that it wants to calculate signature over it, and we
> > > can just include the base64url encoded hash in the "payload".
> > > Why would you like to do other encoding for the hash?
> >
> > If I am not transporting the base64url encoded content, because it is
> not in
> > the "payload" field, then why should I need to base64 encode it just to
> > validate the signature.  This is the alto case.
> >
> > Jim
> >
> > >
> > > --
> > > Nat Sakimura (n-sakimura@nri.co.jp)
> > > Nomura Research Institute
> > >
> > > PLEASE READ:
> > > The information contained in this e-mail is confidential and intended
> > > for the named recipient(s) only.
> > > If you are not an intended recipient of this e-mail, you are hereby
> > > notified that any review, dissemination, distribution or duplication
> > > of this message is strictly prohibited. If you have received this
> > > message in error, please notify the sender immediately and delete your
> > copy from your system.
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--001a11333dce6ca1fd04e02a38c2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think there are two separable issues here, both of which=
 Mike and I probably have divergent opinions on :)<div>1. Syntax: Should it=
 be possible for the &quot;payload&quot; field JWS to be a JSON string (ins=
tead of base64) when the payload is simply a UTF-8 string?</div>
<div>2. Crypto: Must the JWS Signing Input be base64url encoded.</div><div>=
<br></div><div>The current answers to these questions are:</div><div>1. It =
is not possible. =A0Payload is always base64url encoded.</div><div><div>2. =
It is always base64url encoded.</div>
<div><br></div><div>The answers should be:</div><div>1. The payload should =
not be base64url encoded unless it cannot be represented as a JSON string.<=
/div><div>2. The JWS Signing Input should not be base64url encoded unless t=
here is a JWS Protected Header</div>
<div><br></div><div>Neither of these are complicated changes:<br></div><div=
>1. Add a &quot;b64&quot; header parameter that indicates that the payload =
is base64url-encoded binary, as opposed to a UTF-8 string. =A0Specify that =
this parameter is on by default in compact-formatted JWS objects.</div>
<div>2. Modify the signing/verification instructions to switch based on the=
 presence of a JWS Protected Header: &quot;If the JWS Protected Header is a=
bsent or empty, then the JWS Signing Input is simply the JWS Payload (not e=
ncoded). =A0If the JWS Protected Header has a non-empty value, then the the=
 JWS Signing Input is the concatenation of the Encoded JWS Header, a period=
 (&#39;.&#39;) character, and the Encoded JWS Payload&quot;</div>
<div><br></div><div>There are two reasons for these, both of which are impo=
rtant to make sure that this spec is applicable to a broad variety of use c=
ases:</div><div>1. Compactness. =A0As Jim notes, quoted strings are shorter=
 than base64url-encoded strings</div>
<div>2. Crypto-compatibility: Avoiding base64-encoding means that there&#39=
;s nothing JWS-specific about the signature value. =A0So for example, you c=
ould translate a JWS with no protected attributes to a CMS SignedData objec=
t with no protected attributes.</div>
<div><br></div><div>This email brought to you by the number 2 and the lette=
rs J, W, and S :)<br></div><div><br></div><div>--Richard</div><div><br></di=
v><div>[1] Note that the default value for this header must be false, or el=
se you lose the compactness advantage!</div>
<div>[2] You could also do this as a &quot;Content-Encoding&quot; equivalen=
t, &quot;cenc&quot;: &quot;b64&quot;. =A0That would give you &quot;base64 a=
gility&quot;, as some folks have asked for, since you could have &quot;b64&=
quot; and &quot;b64u&quot; values. =A0</div>
<div>[3] You could also do this like CMS, and have the JWS Signing Input in=
 the latter case be &quot;the concatenation of the Encoded JWS Header, a pe=
riod (&#39;.&#39;) character, and the Encoded JWS Payload Hash&quot;. =A0Wh=
ere the Encoded JWS Payload Hash is the base64url-encoded version of the ha=
sh you would otherwise be signing. =A0This seems simpler to code, since you=
 just digest the body, then if there&#39;s a protected header, you digest a=
gain. =A0But it also breaks with existing code. =A0=A0</div>
<div><br></div><div><br></div><div><br></div></div></div><div class=3D"gmai=
l_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 27, 2013 at 1:11 PM=
, Jim Schaad <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcellars.com=
" target=3D"_blank">ietf@augustcellars.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">No, my motivation is to allow for a smaller =
version of the payload string. =A0In some cases quoting it will generate a =
smaller string than doing the base64 conversion on the string.<br>

<div class=3D"im HOEnZb"><br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Mike Jones [mailto:<a href=3D"mailto:Michael.Jones@microsoft.com=
">Michael.Jones@microsoft.com</a>]<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">&gt; Sent: Thursday, June 27,=
 2013 9:49 AM<br>
&gt; To: Jim Schaad; &#39;n-sakimura&#39;<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g">draft-ietf-jose-json-web-signature@tools.ietf.org</a>; <a href=3D"mailto=
:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Jim, you wrote &quot;If I am not transporting the base64url encoded co=
ntent,<br>
&gt; because it is not in the &quot;payload&quot; field, then why should I =
need to base64<br>
&gt; encode it just to validate the signature. =A0This is the alto case.&qu=
ot;<br>
&gt;<br>
&gt; So am I correct then, in thinking that your motivation for #26 is actu=
ally #25 -<br>
&gt; Detached content for the ALTO use case? =A0As John and Nat had written=
, this<br>
&gt; could be handled by the specs as they are today by signing a hash of t=
he<br>
&gt; detached content and including a compact JWS representing that signatu=
re as<br>
&gt; an x-alto-signature header. =A0That doesn&#39;t require changing the s=
ignature<br>
&gt; calculation.<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Mike<br=
>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Jim Schaad [mailto:<a href=3D"mailto:ietf@augustcellars.com">iet=
f@augustcellars.com</a>]<br>
&gt; Sent: Thursday, June 27, 2013 9:41 AM<br>
&gt; To: &#39;n-sakimura&#39;<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g">draft-ietf-jose-json-web-signature@tools.ietf.org</a>; Mike Jones;<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Nat,<br>
&gt;<br>
&gt; The only thing that can be signed or encrypted is an octet string. (A =
slight over<br>
&gt; generalization. GOST for example hashes an integer, tree hashes can do=
<br>
&gt; strange things but a sufficiently true statement for our purposes.)<br=
>
&gt;<br>
&gt; A that being said - yes case 1 would be something you can do. =A0Case =
#2 would<br>
&gt; not be something that you can do because it is not an octet string.<br=
>
&gt;<br>
&gt; If you are looking at JavaScript, in order to hash something as an oct=
et string it<br>
&gt; can be one of three things. =A0A UInt8Array, an Int8Array and, due to<=
br>
&gt; convention, a string where the top byte of all of the code points in t=
he string is<br>
&gt; zero.<br>
&gt;<br>
&gt; We currently don&#39;t have an efficient way to encode the Uint8Array =
case,<br>
&gt; although that might not be true if we are looking at new ECMA specific=
ations<br>
&gt; which apparently are adding more defined types and serialization metho=
ds for<br>
&gt; those types.<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: n-sakimura [mailto:<a href=3D"mailto:n-sakimura@nri.co.jp">=
n-sakimura@nri.co.jp</a>]<br>
&gt; &gt; Sent: Wednesday, June 26, 2013 7:55 PM<br>
&gt; &gt; To: Jim Schaad<br>
&gt; &gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ie=
tf.org">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;<br>
&gt; &gt; <a href=3D"mailto:michael.jones@microsoft.com">michael.jones@micr=
osoft.com</a>; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; &gt; Subject: Re: [jose] #26: Allow for signature payload to not be ba=
se64<br>
&gt; &gt; encoded<br>
&gt; &gt;<br>
&gt; &gt; Let me understand the problem.<br>
&gt; &gt;<br>
&gt; &gt; Are you suggesting that we should be able to do something like:<b=
r>
&gt; &gt;<br>
&gt; &gt; Case 1:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:&quot;this is a multi\nline te=
xt payload of which a line<br>
&gt; &gt; can be very very very long and wrapped during transmission. &quot=
;<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; or even<br>
&gt; &gt;<br>
&gt; &gt; Case 2:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:{<br>
&gt; &gt; =A0 =A0 &quot;this&quot;:&quot;is a json&quot;,<br>
&gt; &gt; =A0 =A0 &quot;payload&quot;:&quot;which is not base64url encoded&=
quot;<br>
&gt; &gt; =A0 =A0 =A0 =A0}<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; Then, I am worried about allowing them because in general we woul=
d not<br>
&gt; &gt; know what would a transmission mechanism and user agents (includi=
ng<br>
&gt; &gt; text<br>
&gt; &gt; editors) would do to them, like Mike mentioned. I do not think we=
<br>
&gt; &gt; should assume the property of the transmission mechanism in JOSE =
level.<br>
&gt; &gt; Assuming that would cause brittleness in the implementations.<br>
&gt; &gt;<br>
&gt; &gt; For detached signature, I do not understand why you would want no=
n-<br>
&gt; &gt; base64url encoded payload. The application should define how to h=
ash<br>
&gt; &gt; the octet stream that it wants to calculate signature over it, an=
d we<br>
&gt; &gt; can just include the base64url encoded hash in the &quot;payload&=
quot;.<br>
&gt; &gt; Why would you like to do other encoding for the hash?<br>
&gt;<br>
&gt; If I am not transporting the base64url encoded content, because it is =
not in<br>
&gt; the &quot;payload&quot; field, then why should I need to base64 encode=
 it just to<br>
&gt; validate the signature. =A0This is the alto case.<br>
&gt;<br>
&gt; Jim<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Nat Sakimura (<a href=3D"mailto:n-sakimura@nri.co.jp">n-sakimura@=
nri.co.jp</a>)<br>
&gt; &gt; Nomura Research Institute<br>
&gt; &gt;<br>
&gt; &gt; PLEASE READ:<br>
&gt; &gt; The information contained in this e-mail is confidential and inte=
nded<br>
&gt; &gt; for the named recipient(s) only.<br>
&gt; &gt; If you are not an intended recipient of this e-mail, you are here=
by<br>
&gt; &gt; notified that any review, dissemination, distribution or duplicat=
ion<br>
&gt; &gt; of this message is strictly prohibited. If you have received this=
<br>
&gt; &gt; message in error, please notify the sender immediately and delete=
 your<br>
&gt; copy from your system.<br>
<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</div></div></blockquote></div><br></div>

--001a11333dce6ca1fd04e02a38c2--

From rlb@ipv.sx  Thu Jun 27 15:25:54 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7868311E8118 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.976
X-Spam-Level: 
X-Spam-Status: No, score=-3.976 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZmkv2ARyOZ4 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:25:45 -0700 (PDT)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id EFC7C11E8116 for <jose@ietf.org>; Thu, 27 Jun 2013 15:25:44 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k14so1566196oag.12 for <jose@ietf.org>; Thu, 27 Jun 2013 15:25:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=dVkJesszGIccZBhf9yiJrZCFyFkFAENQ6rCPmJWVTDE=; b=ppw//6i4cmer1n9z6cVxzmsBpkgToMIHRjnFrcQ4p5MzEjH/wywTvvCTqiN0b8QrD/ O/FlXY+k6xd9UvXZDBgBNGTdQSQDu+hYry13s8J4wZQdRY8Vc0vpi89m1Yy1owEnCQsj nIGBlO/+6dSDeS//9GGSliHKw5Eba2ce+shHvWIRde48J9r7fcAM0sPuaHfSWtiD30Bt vzeW9SK0/zzyAv5bFk4k+LLzntIFsBsL4hX0lWobtmYtub8rvp6idEBbpnnkJNDI/l96 Q73/9GjMywf/mKp4HNnSMdZaeolOF3f1uDOGF9nBXIcNaqySGrWMRtvYNucq9VEaGB+9 A5Rw==
MIME-Version: 1.0
X-Received: by 10.182.105.99 with SMTP id gl3mr5148154obb.94.1372371944524; Thu, 27 Jun 2013 15:25:44 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 27 Jun 2013 15:25:44 -0700 (PDT)
X-Originating-IP: [192.1.51.93]
In-Reply-To: <8B4C063947CD794BB6FF90C78BAE9B321F064434@IMCMBX04.MITRE.ORG>
References: <053f01ce6de7$8ed108e0$ac731aa0$@augustcellars.com> <CAL02cgTVfWU_Ly1txm_k6s+omX8ZzUHTbp58HK03_EZ0qg_7cA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739436787AC69@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTu=LMdH5VEdCsUAs0Ro3qeu_4MZ6viY5QF7axpQmYkZQ@mail.gmail.com> <8B4C063947CD794BB6FF90C78BAE9B321F064434@IMCMBX04.MITRE.ORG>
Date: Thu, 27 Jun 2013 18:25:44 -0400
Message-ID: <CAL02cgTASNKkc_fOzj2+CF0O0S1YSkBta+57TiRqKsJiROGc_Q@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "Peck, Michael A" <mpeck@mitre.org>
Content-Type: multipart/alternative; boundary=e89a8ff2545c40dfd404e02a3e88
X-Gm-Message-State: ALoCoQngHrv18BTCABL9iMpUsKFvVWEbE8KCW8vnckSUSYjAW4oNw5hOS9Dd/lvroyuVCHKM2ye4
Cc: Mike Jones <Michael.Jones@microsoft.com>, Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Field Matrix
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:25:54 -0000

--e89a8ff2545c40dfd404e02a3e88
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Compress(plaintext) and Plaintext have the same information content.  So
the attacker hasn't revealed anything.  Still not a security risk.

--Richard


On Thu, Jun 27, 2013 at 11:43 AM, Peck, Michael A <mpeck@mitre.org> wrote:

>  =93zip=94 indicates whether the authenticated encryption is applied to
> Plaintext vs Compress(Plaintext).****
>
> ** **
>
> By stripping =93zip=94 an attacker could make the message appear to
> successfully decrypt to Compress(Plaintext) rather than Plaintext?****
>
> ** **
>
> I suppose whether that could lead to something bad would be implementatio=
n
> dependent, but anything that can lead to ambiguity about the contents of
> the original plaintext doesn=92t seem like a good idea.****
>
> ** **
>
> Mike****
>
> ** **
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 20, 2013 6:01 PM
> *To:* Mike Jones
> *Cc:* Jim Schaad; jose@ietf.org
>
> *Subject:* Re: [jose] Field Matrix****
>
>  ** **
>
> There was no such decision.  Quoting directly from the minutes:****
>
> """****
>
> **  Crit Text****
>
> ** **
>
> Two questions were raised for dealing with the cirt field.  Does the crit
> field need to be signed and do the members listed in the crit field need =
to
> be signed.****
>
> ** **
>
> There was no consensus in the group at this time as we adjourned for the
> day****
>
> """****
>
> ** **
>
> In order for the attack you describe to be an actual security risk, it
> would need to be the case that the parameters in "crit" were
> security-critical, as opposed to things that would simply cause incorrect
> processing.  One can certainly imagine parameters that would fall in the
> latter bin; my current favorite example is a "part" parameter that would
> allow fragmentation / reassembly.  Because such parameters exist, it's
> possible to use "crit" safely without integrity protection.****
>
> ** **
>
> Can we at least agree that integrity protecting "zip" is unnecessary?  Th=
e
> only thing that stripping / changing "zip" causes is a processing failure=
,
> not a security compromise.****
>
> ** **
>
> --Richard****
>
> ** **
>
> ** **
>
> On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> There was a working group decision at the Denver meeting that =93crit=94 =
must
> be integrity protected.  The reason for this is straightforward.****
>
>  ****
>
> If not integrity protected, an attacker could strip the =93crit=94 field,
> defeating the semantic requirement that implementations must reject the
> input if a =93crit=94 value is used that is not understood.  Thus, the sp=
ec
> requires that this field be integrity protected whenever used.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf
> Of *Richard Barnes
> *Sent:* Thursday, June 20, 2013 1:52 PM
> *To:* Jim Schaad
> *Cc:* jose@ietf.org
> *Subject:* Re: [jose] Field Matrix****
>
>  ****
>
> You can eliminate the "protection required" field, because there aren't
> any of those.  ****
>
>  ****
>
> Or there shouldn't be: The only security case we have is algorithm
> dependent ("alg" must be protected if "alg" =3D=3D "PS256", "PS512").  Th=
e only
> fields for which the specs currently require integrity protection are "zi=
p"
> and "crit".  Neither of these have the property that changing them would
> cause a security violation, except in some application-dependent sense.  =
So
> the choice of integrity protection should be left to applications, not
> fixed in the spec.****
>
>  ****
>
> --Richard****
>
>  ****
>
> On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> <no hat>****
>
>  ****
>
> Having just started looking at a design implementation, I am now more tha=
n
> ever interested in seeing this matrix of fields.  At the present time I
> think the following columns are probably of interest:****
>
>  ****
>
> Name, must understand, use required, common vs specific, protection
> required****
>
>  ****
>
> I was just looking at the alg and enc fields for JWE and realized that on=
e
> was specific =96 so it should be one location =96 and one was common =96 =
so it
> should be in a different location.  And then I needed to start thinking
> about where it goes in terms of compacted vs one recipient vs two
> recipients.****
>
>  ****
>
> Do you have an idea of when this matrix might show up?****
>
>  ****
>
> Jim****
>
>  ****
>
>  ****
>
> ** **
>

--e89a8ff2545c40dfd404e02a3e88
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Compress(plaintext) and Plaintext have the same informatio=
n content. =A0So the attacker hasn&#39;t revealed anything. =A0Still not a =
security risk.<div><br></div><div>--Richard</div></div><div class=3D"gmail_=
extra">
<br><br><div class=3D"gmail_quote">On Thu, Jun 27, 2013 at 11:43 AM, Peck, =
Michael A <span dir=3D"ltr">&lt;<a href=3D"mailto:mpeck@mitre.org" target=
=3D"_blank">mpeck@mitre.org</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">






<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=93zip=94 indicates wheth=
er the authenticated encryption is applied to Plaintext vs Compress(Plainte=
xt).<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">By stripping =93zip=94 an=
 attacker could make the message appear to successfully decrypt to Compress=
(Plaintext) rather than Plaintext?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I suppose whether that co=
uld lead to something bad would be implementation dependent, but anything t=
hat can lead to ambiguity about the contents of the original
 plaintext doesn=92t seem like a good idea.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Mike<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 6:01 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">j=
ose@ietf.org</a></span></p><div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] Field Matrix<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">There was no such decision. =A0Quoting directly from=
 the minutes:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">** =A0Crit Text<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Two questions were raised for dealing with the cirt =
field. =A0Does the crit field need to be signed and do the members listed i=
n the crit field need to be signed.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">There was no consensus in the group at this time as =
we adjourned for the day<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">In order for the attack you describe to be an actual=
 security risk, it would need to be the case that the parameters in &quot;c=
rit&quot; were security-critical, as opposed to things that would simply ca=
use incorrect processing. =A0One can certainly
 imagine parameters that would fall in the latter bin; my current favorite =
example is a &quot;part&quot; parameter that would allow fragmentation / re=
assembly. =A0Because such parameters exist, it&#39;s possible to use &quot;=
crit&quot; safely without integrity protection.<u></u><u></u></p>

<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Can we at least agree that integrity protecting &quo=
t;zip&quot; is unnecessary? =A0The only thing that stripping / changing &qu=
ot;zip&quot; causes is a processing failure, not a security compromise.<u><=
/u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 5:01 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There was a working group=
 decision at the Denver meeting that =93crit=94 must be integrity protected=
.=A0
 The reason for this is straightforward.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If not integrity protecte=
d, an attacker could strip the =93crit=94 field, defeating the semantic req=
uirement
 that implementations must reject the input if a =93crit=94 value is used t=
hat is not understood.=A0 Thus, the spec requires that this field be integr=
ity protected whenever used.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank=
">jose-bounces@ietf.org</a>]
<b>On Behalf Of </b>Richard Barnes<br>
<b>Sent:</b> Thursday, June 20, 2013 1:52 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org=
</a><br>
<b>Subject:</b> Re: [jose] Field Matrix</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">You can eliminate the &quot;protection required&quot=
; field, because there aren&#39;t any of those. =A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Or there shouldn&#39;t be: The only security case we=
 have is algorithm dependent (&quot;alg&quot; must be protected if &quot;al=
g&quot; =3D=3D &quot;PS256&quot;, &quot;PS512&quot;). =A0The only fields fo=
r which the specs currently
 require integrity protection are &quot;zip&quot; and &quot;crit&quot;. =A0=
Neither of these have the property that changing them would cause a securit=
y violation, except in some application-dependent sense. =A0So the choice o=
f integrity protection should be left to applications, not
 fixed in the spec.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 20, 2013 at 2:54 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">&lt;no hat&gt;<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Having just started looking at a design implementati=
on, I am now more than ever interested in seeing this matrix of fields.=A0 =
At the present time I think the following columns are
 probably of interest:<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Name, must understand, use required, common vs speci=
fic, protection required<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I was just looking at the alg and enc fields for JWE=
 and realized that one was specific =96 so it should be one location =96 an=
d one was common =96 so it should be in a different location.=A0
 And then I needed to start thinking about where it goes in terms of compac=
ted vs one recipient vs two recipients.<u></u><u></u></p>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Do you have an idea of when this matrix might show u=
p?<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">Jim</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"color:#888888">=A0</span><u></u><u></=
u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--e89a8ff2545c40dfd404e02a3e88--

From rlb@ipv.sx  Thu Jun 27 15:48:00 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CA011E80A5 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.476
X-Spam-Level: 
X-Spam-Status: No, score=-3.476 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktSsLgMIGbda for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:47:55 -0700 (PDT)
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by ietfa.amsl.com (Postfix) with ESMTP id 65E7121F9B2E for <jose@ietf.org>; Thu, 27 Jun 2013 15:47:54 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id up14so1330436obb.0 for <jose@ietf.org>; Thu, 27 Jun 2013 15:47:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=BOyqGRUfVb2a2ADzB6EELxgC/VcjST3xlfoum45xknY=; b=CDpo2RcCISI4NhdIAxO6IBTd16QADF9md9dnjWFvRwnLXQafOdQWOE4bxrzh4loCc1 YI6t0Do6EXYWPgChBuiQO5e0ZX1RATE+uYUoQSelBZKxGu66Iyr6JGv4HEszImqaTkrC 3RFoRMDRHTBrnfhYvpjOdDARK8L3EcYCfqPHfuOGEssT4sFKMRVIQix08V9lMoexZK4N 9y0mXm3xUHvr2Jgiq7GgmKM7P8gOtUqbs/AMPE2GYLNibirnJR279+ss1lrQQWM7WX+I Fyu/LvbsySuO9NTsCvzV5NN4QQ1Ahf9AYK/VXIi/oJiLjnC0o939J5nhctjE72Y09D/0 nFPA==
MIME-Version: 1.0
X-Received: by 10.182.142.104 with SMTP id rv8mr5244002obb.3.1372373256407; Thu, 27 Jun 2013 15:47:36 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 27 Jun 2013 15:47:36 -0700 (PDT)
X-Originating-IP: [192.1.51.93]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 18:47:36 -0400
Message-ID: <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2eaae729e0904e02a8c11
X-Gm-Message-State: ALoCoQk6Ow6kTDOHHknG26SmZD66MevUuEDcXzU6UrleLIygekvL544DYYPECsEJgMLs1PM2IpAB
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:48:00 -0000

--001a11c2eaae729e0904e02a8c11
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com>w=
rote:

>  I=92ve come to believe that James=92 proposed language does a good job o=
f
> making security-appropriate restrictions while allowing the use of existi=
ng
> parsers.  It was:****
>
> ** **
>
> A creator of a JOSE message MUST NOT put duplicate names in any JSON
> object in a JOSE header.  To prevent attacks where a JOSE message is
> interpreted as different valid messages by different recipients, each
> recipient MUST either reject messages with duplicate names or accept only
> the last name.****
>
> ** **
>
> I might change =93or accept only the last name=94 to =93or use a parser t=
hat
> always uses the lexically last name for any duplicate member names, per
> [ECMAScript]=94 for clarity, but the intent is the same.****
>
> ** **
>
> Would that work for people?****
>
> ** **
>
>                                                             -- Mike
>


That's close.  I don't think we can allow the "lexically last" because
elements in a JSON dictionary can be re-ordered.  Suppose there a helpful
intermediary that sorts a JSON dictionary in descending alphabetical order
of values.
When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }
It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }

The only way to avoid the ambiguity is to reject objects with duplicate
keys.


I realize that this renders most JSON parsers incompatible.  Implementors
will need to add a secondary check.  I feel your pain.  But hopefully this
pain will be temporary; the ambiguity will be fixed by the JSON WG and
ECMA, and parsers will be updated.  Even in the short run, it doesn't seem
like it would be that hard to mod existing parsers to have a "strict" flag.

"""
A creator of a JOSE message MUST NOT put duplicate names in any JSON object
in a JOSE header.  To prevent attacks where a JOSE message is interpreted
as different valid messages by different recipients, each recipient MUST
reject messages.  Implementations MUST NOT select the lexically last name,
as required by [ECMAScript], since this could lead them to select the
incorrect value if an intermediary re-orders the fields in a dictionary.
 If an implementation uses a JSON parser that does not reject objects with
duplicate fields, then it MUST verify that there are no dictionaries with
duplicate fields in the JSON object.
"""

--Richard






> ****
>
> ** **
>
> *From:* John Bradley [mailto:ve7jtb@ve7jtb.com]
> *Sent:* Thursday, June 27, 2013 8:49 AM
> *To:* Tim Bray
> *Cc:* Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ** **
>
> The problem is not wanting to leave a hole for malicious signers to creat=
e
> JWT that may be misinterpreted by the receiver.  Accidental interop
> problems from bad signers are not a big concern for me and are covered by
> MUST NOT emit dups.****
>
> ** **
>
> Accepting malformed JSON as the envelope may lead to real security issues=
.
> ****
>
> ** **
>
> This may be more of an issue for the JSON encoding than the compact as
> there you need to be careful the body you process for the signature is th=
e
> body that the application uses.****
>
> ** **
>
> What happens if you receive.****
>
> ** **
>
> {"protected":<integrity-protected shared header contents>",****
>
>       "unprotected":<non-integrity-protected shared header contents>",***=
*
>
>       "payload":"<original payload contents>",****
>
>       "payload":"<bad payload contents inserted by attacker>"****
>
>       "signatures":[****
>
>        {"header":"<per-signature unprotected header 1 contents>",****
>
>         "signature":"<signature 1 contents>"},****
>
>        ...****
>
>        {"header":"<per-signature unprotected header N contents>",****
>
>         "signature":"<signature N contents>"}],****
>
>      }****
>
>  ** **
>
> If the JOSE library validates on the first version of "payload" and the
> application using a different JSON parser only sees the second "payload" =
we
> have a wrapping attack similar to xmldsig.****
>
> ** **
>
> I can't off the top of my head think of what you could do in the compact
> serialization that would lead to a successful attack given that the
> signature is over the base64url encoded segments, that prevents attackers
> from modifying the JSON while maintaining integrity.****
>
> ** **
>
> It is a real issue for the JSON serialization though.****
>
> ** **
>
> John B.****
>
> ** **
>
> On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com> wrote:****
>
>
>
> ****
>
> The approach just seems wrong.  If we require that conforming
> implementations MUST NOT emit dupes, then authors of receiving software c=
an
> just pick the best-performing parser with the nicest API, because they
> *all* perform correctly when there are no dupes.
>
> Who=92s going to own the responsibility for making the authoritative find=
ing
> that of the many JSON parsers in the Java ecosystem, these ones, but not
> those ones, are usable in JOSE applications?  And suppose one that has be=
en
> previously OK is quietly optimized on GitHub to run 30% faster and as a
> side-effect silently ignores dupes?  ****
>
> The benefit of using JSON is that there is widely deployed software to
> handle it.  It is a known problem that sloppy spec drafting has allowed
> various kinds of problems to occur when dupe keys are received. =93Doctor=
, it
> hurts when I do this.=94 =93So... don=92t do that.=94****
>
> Are we also going to specify the behavior of receiving software when the
> JSON has a misplaced quotation mark?  A missing trailing =93}=94?****
>
>  -T****
>
> ** **
>
> ** **
>
> On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> Most JSON libraries that silently accept [sob] dupe keys at least
> consistently use the last key. Allowing just that behaviour (or rejecting
> dupes), while forbidding acceptance of a non-last dupe (eg first key), is
> safe and allows most JSON libraries to be used. Since this accepts most
> libraries I think it is practical.****
>
>  ****
>
> Hence I suggest:****
>
>  ****
>
> >   A creator of a JOSE message MUST NOT put duplicate names in any JSON*=
*
> **
>
> > object in a JOSE header.****
>
> >   To prevent attacks where a JOSE message is interpreted as different**=
*
> *
>
> > valid messages by different recipients, each recipient MUST either****
>
> > reject messages with duplicate names or accept only the last name.****
>
>  ****
>
> This isn=92t =93truly predictable=94 as a message with dupes might be acc=
epted
> or rejected. The crucial point is that if a message is accepted it is
> predictable.****
>
>  ****
>
> --****
>
> James Manger****
>
>  ****
>
> *From:* Tim Bray [mailto:tbray@textuality.com]
> *Sent:* Thursday, 27 June 2013 4:16 PM
> *To:* Manger, James H
> *Cc:* Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
> ** **
>
>  ****
>
> Well, you have a practical problem in that most implementers will want to
> use a standard JSON library, which is good practice because it will be
> well-debugged, and most libraries [sob] silently take care of dupe keys a=
nd
> don=92t have a way to tell the client software what happened. So if you w=
ant
> truly predictable behavior, you=92re forcing the use of hand-constructed =
JSON
> parsers. And that sucks, because getting good performance in JSON parsing
> is surprisingly hard, with dramatic performance differences between
> implementations. So you=92re forcing receiving software which wants to be
> conformant to use a hand-rolled parser which will probably have lousy
> performance and have other bugs which in fact may compromise security mor=
e
> than dupe-key tricks could.  -T****
>
>  ****
>
> On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> > I think it=92s a nice clean minimal solution to say that producers MUST
> > NOT generate dupes, end of story.  I don=92t think saying anything beyo=
nd
> > that adds value. -T****
>
> Clean and minimal that may be, but it ignores the security issue. We don'=
t
> want a malicious producer (who is so malicious they ignore a MUST) to
> create JOSE messages that a JOSE-compliant security layer accepts as
> "benign interpretation #1" so it passes the message on to the
> JOSE-compliant backend app that acts on "nasty interpretation #2".
>
> --
> James Manger****
>
>  ****
>
> ** **
>
> ** **
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--001a11c2eaae729e0904e02a8c11
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <span dir=3D"=
ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">M=
ichael.Jones@microsoft.com</a>&gt;</span> wrote:<br><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">I=92ve come to believe that James=92 proposed languag=
e does a good job of making security-appropriate restrictions while allowin=
g the use of existing parsers.=A0
 It was:<u></u><u></u></span></p><div class=3D"im">
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D"" style=3D"margin-left:0.5in"><span style=3D"font-size:11pt;fon=
t-family:Calibri,sans-serif;color:rgb(31,73,125)">A creator of a JOSE messa=
ge MUST NOT put duplicate names in any JSON object in a JOSE header.=A0 To =
prevent attacks where a JOSE message
 is interpreted as different valid messages by different recipients, each r=
ecipient MUST either reject messages with duplicate names or accept only th=
e last name.<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
</div><p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-=
serif;color:rgb(31,73,125)">I might change =93or accept only the last name=
=94 to =93or use a parser that always uses the lexically last name for any =
duplicate member names, per [ECMAScript]=94
 for clarity, but the intent is the same.<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">Would that work for people?<u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</span></p></div=
></div></blockquote><div><br></div><div><br>
</div><div>That&#39;s close. =A0I don&#39;t think we can allow the &quot;le=
xically last&quot; because elements in a JSON dictionary can be re-ordered.=
 =A0Suppose there a helpful intermediary that sorts a JSON dictionary in de=
scending alphabetical order of values.=A0</div>
<div>When it gets: {=A0&quot;payload&quot;: &quot;bad stuff&quot;,=A0=A0&qu=
ot;payload&quot;: &quot;good stuff&quot;, ... }</div><div>It emits: {=A0&qu=
ot;payload&quot;: &quot;good stuff&quot;,=A0=A0&quot;payload&quot;: &quot;b=
ad=A0stuff&quot;, ... }</div>
<div><br></div><div>The only way to avoid the ambiguity is to reject object=
s with duplicate keys.</div><div><br></div><div><br class=3D"">I realize th=
at this renders most JSON parsers incompatible. =A0Implementors will need t=
o add a secondary check. =A0I feel your pain. =A0But hopefully this pain wi=
ll be temporary; the ambiguity will be fixed by the JSON WG and ECMA, and p=
arsers will be updated. =A0Even in the short run, it doesn&#39;t seem like =
it would be that hard to mod existing parsers to have a &quot;strict&quot; =
flag.<br>
</div><div><br></div><div>&quot;&quot;&quot;</div><div>A creator of a JOSE =
message MUST NOT put duplicate names in any JSON object in a JOSE header. =
=A0To prevent attacks where a JOSE message is interpreted as different vali=
d messages by different recipients, each recipient MUST reject messages. =
=A0Implementations MUST NOT select the lexically last name, as required by =
[ECMAScript], since this could lead them to select the incorrect value if a=
n intermediary re-orders the fields in a dictionary. =A0If an implementatio=
n uses a JSON parser that does not reject objects with duplicate fields, th=
en it MUST verify that there are no dictionaries with duplicate fields in t=
he JSON object.<br>
</div><div>&quot;&quot;&quot;</div><div><br></div><div>--Richard=A0<br></di=
v><div><br></div><div><br></div><div><br></div><div><br></div><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D""><span=
 style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125=
)"><u></u><u></u></span></p>
<p class=3D""><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u>=A0<u></u></span></p>
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0in 0in">
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> John Bradley [mailto:<a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_=
blank">ve7jtb@ve7jtb.com</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">jose@ietf.org</a>; <a href=3D"mailto:draft-ietf=
-jose-json-web-signature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-=
json-web-signature@tools.ietf.org</a></span></p>
<div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">The problem is not wanting to leave a hole for malicious sign=
ers to create JWT that may be misinterpreted by the receiver. =A0Accidental=
 interop problems from bad signers are not a big concern for me and are cov=
ered by MUST NOT emit dups.<u></u><u></u></p>

<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">Accepting malformed JSON as the envelope may lead to real sec=
urity issues.<u></u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">This may be more of an issue for the JSON encoding than the c=
ompact as there you need to be careful the body you process for the signatu=
re is the body that the application uses.<u></u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">What happens if you receive.<u></u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<pre><span style=3D"font-size:12pt">{&quot;protected&quot;:&lt;integrity-pr=
otected shared header contents&gt;&quot;,<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0 &quot;unprotected&quot;=
:&lt;non-integrity-protected shared header contents&gt;&quot;,<u></u><u></u=
></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&qu=
ot;&lt;original payload contents&gt;&quot;,<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&qu=
ot;&lt;bad payload contents inserted by attacker&gt;&quot;<u></u><u></u></s=
pan></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0 &quot;signatures&quot;:=
[<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot;:=
&quot;&lt;per-signature unprotected header 1 contents&gt;&quot;,<u></u><u><=
/u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature&q=
uot;:&quot;&lt;signature 1 contents&gt;&quot;},<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0=A0 ...<u></u><u></u></s=
pan></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot;:=
&quot;&lt;per-signature unprotected header N contents&gt;&quot;,<u></u><u><=
/u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature&q=
uot;:&quot;&lt;signature N contents&gt;&quot;}],<u></u><u></u></span></pre>
<pre><span style=3D"font-size:12pt">=A0=A0=A0=A0 }<u></u><u></u></span></pr=
e>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">If the JOSE library validates on the first version of &quot;p=
ayload&quot; and the application using a different JSON parser only sees th=
e second &quot;payload&quot; we have a wrapping attack similar to xmldsig.<=
u></u><u></u></p>

</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">I can&#39;t off the top of my head think of what you could do=
 in the compact serialization that would lead to a successful attack given =
that the signature is over the base64url encoded segments, that prevents at=
tackers from modifying the JSON
 while maintaining integrity.<u></u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">It is a real issue for the JSON serialization though.<u></u><=
u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"">John B.<u></u><u></u></p>
</div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"mailto:tb=
ray@textuality.com" target=3D"_blank">tbray@textuality.com</a>&gt; wrote:<u=
></u><u></u></p>
</div>
<p class=3D""><br>
<br>
<u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt">The approach just seems wrong.=
=A0 If we require that conforming implementations MUST NOT emit dupes, then=
 authors of receiving software can just pick the best-performing parser wit=
h the nicest API, because they
 *all* perform correctly when there are no dupes.=A0 <br>
<br>
Who=92s going to own the responsibility for making the authoritative findin=
g that of the many JSON parsers in the Java ecosystem, these ones, but not =
those ones, are usable in JOSE applications?=A0 And suppose one that has be=
en previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?=
=A0 <u></u><u></u></p>
</div>
<p class=3D"" style=3D"margin-bottom:12pt">The benefit of using JSON is tha=
t there is widely deployed software to handle it.=A0 It is a known problem =
that sloppy spec drafting has allowed various kinds of problems to occur wh=
en dupe keys are received.
 =93Doctor, it hurts when I do this.=94 =93So... don=92t do that.=94<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt">Are we also going to specify the=
 behavior of receiving software when the JSON has a misplaced quotation mar=
k?=A0 A missing trailing =93}=94?<u></u><u></u></p>
</div>
<div>
<p class=3D"">=A0-T<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &lt;<a href=
=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Mange=
r@team.telstra.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">Most JSON libraries that silently acce=
pt [sob] dupe keys at least consistently use the
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><span lang=3D"EN-AU"><u></u><u></u></span></p>

<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=3D"EN-AU"><u></u>=
<u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">Hence I suggest:</span><span lang=3D"E=
N-AU"><u></u><u></u></span></p>
<div>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=3D"EN-AU"><u></u>=
<u></u></span></p>
<p><span lang=3D"EN-AU">&gt; =A0=A0A creator of a JOSE message MUST NOT put=
 duplicate names in any JSON<u></u><u></u></span></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.<u></u><u></u></span><=
/p>
<p><span lang=3D"EN-AU">&gt; =A0=A0To prevent attacks where a JOSE message =
is interpreted as different<u></u><u></u></span></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either<u></u><u></u></span></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.<u></u><u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=3D"EN-AU"><u></u>=
<u></u></span></p>
</div>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">This isn=92t =93truly predictable=94 a=
s a message with dupes might be accepted or rejected.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><span lang=3D"EN-AU"><u></u><u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=3D"EN-AU"><u></u>=
<u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">--</span><span lang=3D"EN-AU"><u></u><=
u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">James Manger</span><span lang=3D"EN-AU=
"><u></u><u></u></span></p>
<p class=3D""><span lang=3D"EN-AU" style=3D"font-size:11pt;font-family:Cali=
bri,sans-serif;color:rgb(31,73,125)">=A0</span><span lang=3D"EN-AU"><u></u>=
<u></u></span></p>
<div style=3D"border-style:none none none solid;border-left-color:blue;bord=
er-left-width:1.5pt;padding:0in 0in 0in 4pt">
<div>
<div style=3D"border-style:solid none none;border-top-color:rgb(181,196,223=
);border-top-width:1pt;padding:3pt 0in 0in">
<p class=3D""><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-seri=
f">From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-se=
rif"> Tim Bray [mailto:<a href=3D"mailto:tbray@textuality.com" target=3D"_b=
lank">tbray@textuality.com</a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><span lang=3D"E=
N-AU"><u></u><u></u></span></p>
<div>
<p class=3D""><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></span></p>
</div>
<div>
<p class=3D""><span lang=3D"EN-AU"><u></u>=A0<u></u></span></p>
</div>
</div>
</div>
<p class=3D""><span lang=3D"EN-AU">=A0<u></u><u></u></span></p>
<div>
<p class=3D""><span lang=3D"EN-AU">Well, you have a practical problem in th=
at most implementers will want to use a standard JSON library, which is goo=
d practice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don=92t have =
a way to tell the client software what happened. So if you want truly predi=
ctable behavior, you=92re forcing the use of hand-constructed JSON parsers.=
 And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you=92re forcing receiving softwa=
re which wants to be conformant to use a hand-rolled parser which will prob=
ably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.=A0 -T<u></u><u></u></span></p>
</div>
<div>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><span lang=3D"EN-AU">=A0<u></u><=
u></u></span></p>
<div>
<p class=3D""><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 PM, Manger=
, James H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"=
_blank">James.H.Manger@team.telstra.com</a>&gt; wrote:<u></u><u></u></span>=
</p>

<div>
<p class=3D"" style=3D"margin-bottom:12pt"><span lang=3D"EN-AU">&gt; I thin=
k it=92s a nice clean minimal solution to say that producers MUST<br>
&gt; NOT generate dupes, end of story.=A0 I don=92t think saying anything b=
eyond<br>
&gt; that adds value. -T<u></u><u></u></span></p>
</div>
<p class=3D""><span lang=3D"EN-AU">Clean and minimal that may be, but it ig=
nores the security issue. We don&#39;t want a malicious producer (who is so=
 malicious they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger<u></u><u></u></span></p>
</div>
<p class=3D""><span lang=3D"EN-AU">=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div></div>

--001a11c2eaae729e0904e02a8c11--

From Michael.Jones@microsoft.com  Thu Jun 27 15:48:45 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A4311E810B for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.649,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rm6khScYJ54J for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:48:37 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id ACD6B11E80F2 for <jose@ietf.org>; Thu, 27 Jun 2013 15:48:36 -0700 (PDT)
Received: from BL2FFO11FD002.protection.gbl (10.173.161.202) by BL2FFO11HUB016.protection.gbl (10.173.160.108) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 22:48:28 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD002.mail.protection.outlook.com (10.173.160.102) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Thu, 27 Jun 2013 22:48:28 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 22:48:28 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "draft-ietf-jose-json-signature@tools.ietf.org" <draft-ietf-jose-json-signature@tools.ietf.org>
Thread-Topic: [jose] Comments on the web signature draft version 11
Thread-Index: Ac5nqFuZTYR8wZ0pRs+tqSZ/RDYb+wLsbzoA
Date: Thu, 27 Jun 2013 22:48:27 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1A4A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <00f901ce6a04$d0e7d1f0$72b775d0$@augustcellars.com>
In-Reply-To: <00f901ce6a04$d0e7d1f0$72b775d0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.76]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1A4ATK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(377454003)(199002)(52604005)(51444003)(69224002)(13464003)(51914003)(51856001)(74662001)(79102001)(31966008)(81542001)(55846006)(56776001)(54356001)(33656001)(81342001)(47446002)(74366001)(74502001)(77096001)(56816003)(76796001)(16406001)(15202345003)(76786001)(19300405004)(59766001)(512954002)(76482001)(71186001)(54316002)(53806001)(44976004)(6806003)(46102001)(77982001)(16236675002)(74876001)(74706001)(49866001)(4396001)(65816001)(66066001)(69226001)(80022001)(50986001)(47976001)(47736001)(20776003)(63696002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB016; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Comments on the web signature draft version 11
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:48:45 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1A4ATK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the useful review comments, Jim.  Replies inline prefixed by "Mi=
ke>"...



-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Saturday, June 15, 2013 1:14 PM
To: draft-ietf-jose-json-signature@tools.ietf.org
Cc: jose@ietf.org
Subject: [jose] Comments on the web signature draft version 11



1.   Going from the string to the UTF8 encoding followed by the base64

encoding in section 3.1 is difficult given that it is not really possible t=
o

figure out where the spaces, returns and new-lines are.   It would be easie=
r

if you included the half-way step or better yet make the header be a single=
 line.



Mike> OK - I'll copy this intermediate step forward from the appendix where=
 it's already present.



2.  In section 3.1 rather than saying you are using ASCII, it might be bett=
er to omit the character set entirely.  IMHO, having ASCII in there confuse=
s the issue rather than clarifies it.



Mike> Disagree.  EBCDIC still exists, could represent this string, and uses=
 a different encoding.  The computation is dependent up the encoding, so it=
 needs to be specified.



3.  In section 3.1  s/Header.Payload.Signature/Header, Payload, Signature/ =
you are listing the items and the 'with' clause describes how to put in the=
 separation character.



Mike> OK



4.  In section 4 para #1 - I am having an issue with the first sentence.

               a) Using "object(s)" to describe the possible hierarchy is m=
essy as it might be possible to interpret this as interdependent rather tha=
n nested.



Mike> "JSON object" is a term from RFC 4627 - not a statement about possibl=
e hierarchy.  I could change the words "represented by" to "representing", =
as I think that would be clearer.  Would that address the issue for you?



               b) 'optionally additional properties' is difficult for me to=
 parse.

I think that "and, optionally, additional properties" would be better



Mike> OK



5.  In section 4 para #2 - Two items, this does not talk about header param=
eter not defined in this document and I think it might be more understandab=
le if this was done as a series of bullet points rather than just text.



Mike> Actually, the paragraph does talk about header parameters not defined=
 in this document: "Unless listed as a critical header parameter, per Secti=
on 4.1.10, all other header parameters MUST be ignored when not understood.=
"  Editorially, I don't think that bullets would be the best choice, becaus=
e the points being made in the different sentences are not grammatically pa=
rallel.



6.  In section 4.1.1 - I think the current text for rejection on alg is wri=
tten on the assumption that there is only one signature/MAC on the object. =
 If there are two and there is both an implementation and a key for one sig=
nature but the second either does not have an implementation or a key

- is this still a MUST reject situation?



Mike> About the multi-signature case, we could say something like: "If ther=
e are multiple signatures and/or MACs over the payload, then at least one "=
alg" value must be supported and have an associated key as described above,=
 or the JWS must be rejected".  Does that describe the semantics you had in=
 mind?  What does CMS do in this case?



7.  In section 4.1.2 - Are you going to impose a minimum version TLS - spec=
ifically are SSL and TLS v1.0 allowed?



Mike> I propose that we add this security considerations subsection, which =
is derived from that used in OAuth.  (This language resulted from the resol=
ution of a DISCUSS, if I recall correctly.)



TLS Requirements



Implementations MUST support TLS. Which version(s) ought to be implemented =
will vary over time, and depend on the widespread deployment and known secu=
rity vulnerabilities at the time of implementation. At the time of this wri=
ting, TLS version 1.2 [RFC5246] is the most recent version, but has very li=
mited actual deployment, and might not be readily available in implementati=
on toolkits. TLS version 1.0 [RFC2246] is the most widely deployed version,=
 and will give the broadest interoperability.



To protect against information disclosure and tampering, confidentiality pr=
otection MUST be applied using TLS with a ciphersuite that provides confide=
ntiality and integrity protection.



Whenever TLS is used, a TLS server certificate check MUST be performed, per=
 RFC 6125 [RFC6125].



8.  In section 4.1.2 - Is implementation of this parameter required?



Mike> Only in the sense described in the second paragraph of section 4:  "A=
ll other header parameters defined by this specification that are not so de=
signated MUST be ignored when not understood."  This was part of the "MUST =
understand" resolution proposed by Eric Rescorla, Nat Sakimura, and others =
and confirmed by the working group.  Incomplete implementations are OK - ju=
st not fully functional.



9.  In section 4.1.3 - see comment 8



Mike> Same answer as 8



10.  In section 4.1.3 - Should we make a note that the private portions of =
a key MUST NOT be included?



Mike> OK



11.  In section 4.1.4 - Other than consistency - what is the requirement he=
re for doing HTTPS - are you expecting self-signed certificates to be commo=
n and trying to get around trust anchor issues?



Mike> Yes



12. In section 4.1.4 - see comment 8  -- ok - and lots of other sections



Mike> Same answer as 8

13.  In section 4.1.6 - There is a verification statement on X.509 certific=
ates.  There is not a similar statement for x5t or x5u.  Should there be?



Mike> Thanks for pointing this out.  I think there should be.



14. In section 4.1.9 - This section gives why I thought that JWT was a cty =
value.  It explicitly says so.  Mike has said this is not true.



Mike> I can see why the example is misleading.  "cty": "JWT" is only used w=
hen the JWT representation signs or encrypts another JWT in a nested fashio=
n - not when a set of claims are directly signed or encrypted.  I'll remove=
 it (and clarify the intent of "cty" and "typ" using language supplied by R=
ichard).



15.  In section 4.1.9 - The last paragraph states that ctyp and typ values =
come from the same values space.  Mike has said this is not true.



Mike> It is true.  If it appeared that I contradicted this, I misspoke or w=
as misunderstood.



16. In section 4.1.10 - I think there is an interesting discussion point on=
 the use of 'crit' in the following case.  I want to ensure that you implem=
ent a feature in the base specification that the base specification has sai=
d you do not need to implement.  I am not sure based on the current documen=
t language if this is an empty set or not.



Mike> There's a distinction that Eric Rescorla made when designing the "MUS=
T understand" solution between fields that would result in security bugs if=
 not fully supported versus fields that would result in the inability to pr=
ocess the content if not supported.  For instance, the key selection fields=
 are in the latter category.  If someone doesn't support "x5t" you might no=
t know what certificate to use and so you couldn't process the JWS, but tha=
t would just be functionality deficiency - not a security bug.  "crit" is t=
here to be able to dynamically designate new fields as being in the former =
category.



17.  In section 5.1 step 3 - I don't know if there is a reason to make a st=
atement about suggesting that whitespace be removed when you are planning o=
n doing a compact representation.  This is one of those things that would l=
ead to a smaller encoding.



Mike> The statement is that whitespace is permitted and no canonicalization=
 need be performed.  It doesn't say that you can't remove whitespace or per=
form canonicalization if you choose.



18.  In section 5.1, step 4 - the phrase "If the JWS protected header is no=
t present..." leaves me lost.  I don't understand what this term is coming =
from as you have not yet introduced it in terms of how to build a signed me=
ssage.  Specifically, there has been nothing at this point which tells me h=
ow to decide what goes where.  I strongly feel that section 8 needs to move=
 before this section.



Mike> The JWS Protected Header was already defined in the Terminology secti=
on.  We could make this more explicit by saying that the base64url encoding=
 of the JWS Protected Header is the value of the "protected" member in the =
JSON Serialization, if present.



19.  In section 5.1, Step 11 - I think this should be moved forward to say =
- repeat the steps X to Y for each signature to be processed.  I also don't=
 think this needs to say anything about the serialization method being used=
.

It is not relevant.



Mike> I will add the language about "steps X to Y" as you suggest.  Saying =
that this only applies for the JSON Serialization is important, since this =
step is inapplicable to the Compact Serialization.



20.  In section 5.1, step 5 - the last sentence in this step would appear t=
o be out of place.  This is not a requirement of computing the signature, b=
ut one of building the JWS header which is step 2.  This MUST is just a re-=
iteration of one someplace else so it does not add anything.



Mike> Agreed - I'll delete this sentence.



21. In section 5.1, step 9 - I believe that the compact serialization shoul=
d be moved to its own section.  There should not be any apparent preference=
 in the document for one of the serialization methods.



Mike> I will create a Compact Serialization section paralleling the JSON Se=
rialization section, but I disagree about removing the concatenation langua=
ge here.  One of the beautiful things about the Compact Serialization is th=
at it *can* be described in a single sentence, as is step 9.  It will be ea=
sier for most developers to continue having this single sentence in-line, r=
ather than making them jump to another section when a single sentence in pl=
ace already does the job nicely.



22. In Section 5 - I am going to make a suggestion that I would like you to=
 consider, although I think that it might not be to your liking.  My person=
al view of the world has been one of: There is a JSON serialization that is=
 the object.  There is a way to map from the JSON serialization to the comp=
act serialization.  The mapping requires a set of constraints on the origin=
al serialization.  Thus in my world, I build the internal JSON object repre=
sentation, run the computations on that internal representation and then ei=
ther run the mapping to the compact serialization or serialize the JSON obj=
ect representation to get the output.  Using this as the method would mean =
that section 5 would be an object representation for JSON, section 6 would =
be how to do the mappings to and from the compact form, section 7 would be =
the how to do this.



Mike> What you're doing is functionally equivalent to what's in the spec no=
w, but pretty inefficient and unnecessary if you're only using the Compact =
Serialization, which will be a common model for many use cases.  I think a =
better model is that the Compact Serialization and JSON Serialization are p=
eers - sharing 95%+ of the processing rules and then applying a particular =
serialization for the data values manipulated by those processing rules.  T=
hat's why the specs describe things in terms of abstract fields and binding=
s of those fields to elements of serializations - rather than describing th=
ings only in terms of the serialized representations.



23.  In section 5.3 - Are steps #1 and #2 not the requirement of the JSON p=
arser and not my application?  I would suggest reading some of the updated =
text on member name string comparison from the JSON mailing list for a clea=
ner way to write this section.

Mike> Specific text suggestions welcomed.



24.  Section 6 appears to be extraneous and could be deleted.  What is the =
purpose that this is supposed to serve?  Why is that purpose not covered in=
 the description of the alg member?



Mike> I agree.  FWIW, Richard privately made the same suggestion about the =
parallel section in JWE, which I also agree with.



25.  Section 7 would appear to be better served by making it section 4.1.2 =
and making section on jku, jwk, x5u, x5t, x5c and kid as subjections of it.



Mike> The problem with this suggestion is that it would make the list of re=
served header parameters no longer syntactically parallel.  And I do believ=
e there's value in having a paragraph that talks about the semantics of key=
 identification all-up, rather than trying to do it in a manner that's scat=
tered in bits and pieces into the individual parameter definitions.



26.  Section 8 - I found the presentation confusing.  I would have expected=
 that it would be made in the normal manner - that is you have an object an=
d a list of members each with its own section - and those members may have =
sub members which are listed.  There would then be references back to the m=
embers defined in section 4



Mike> I agree that an object-centered approach will be easier to follow.  T=
hanks for suggesting it.  Some of that content is now in prose.  I'll restr=
ucture to use lists/tables instead as you suggest.



27.  Section 9 - I would dispute the content of this section vigorously.


Mike> Hannes and Derek and Stephen and Sean, at least to the OAuth WG, have=
 made it VERY CLEAR that the IESG requires MTI features to be defined.  Of =
the JSON and Compact serializations, the latter is the only one in widespre=
ad use, therefore it makes sense for it to be the MTI serialization.  Parti=
cularly since JWTs mandate that only the Compact Serialization be used, it =
would make no sense from a working group coordination point of view to try =
to mandate that the JSON serialization also be MTI - especially since it's =
more complicated.



I stopped reviewing after section 9.



Mike> Thanks for all the useful comments.



                                                            -- Mike

Jim





_______________________________________________

jose mailing list

jose@ietf.org<mailto:jose@ietf.org>

https://www.ietf.org/mailman/listinfo/jose

--_000_4E1F6AAD24975D4BA5B1680429673943678A1A4ATK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Thanks for the useful review comments, Jim.&nbsp;=
 Replies inline prefixed by &#8220;<span style=3D"color:#0070C0">Mike&gt;</=
span>&#8221;...<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad<br>
Sent: Saturday, June 15, 2013 1:14 PM<br>
To: draft-ietf-jose-json-signature@tools.ietf.org<br>
Cc: jose@ietf.org<br>
Subject: [jose] Comments on the web signature draft version 11</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1.&nbsp;&nbsp; Going from the string to the UTF8 =
encoding followed by the base64<o:p></o:p></p>
<p class=3D"MsoPlainText">encoding in section 3.1 is difficult given that i=
t is not really possible to<o:p></o:p></p>
<p class=3D"MsoPlainText">figure out where the spaces, returns and new-line=
s are.&nbsp;&nbsp; It would be easier<o:p></o:p></p>
<p class=3D"MsoPlainText">if you included the half-way step or better yet m=
ake the header be a single line.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; OK &#8211;=
 I&#8217;ll copy this intermediate step forward from the appendix where it&=
#8217;s already present.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">2.&nbsp; In section 3.1 rather than saying you ar=
e using ASCII, it might be better to omit the character set entirely.&nbsp;=
 IMHO, having ASCII in there confuses the issue rather than clarifies it.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Disagree.&=
nbsp; EBCDIC still exists, could represent this string, and uses a differen=
t encoding.&nbsp; The computation is dependent up the encoding, so it needs=
 to be specified.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">3.&nbsp; In section 3.1&nbsp; s/Header.Payload.Si=
gnature/Header, Payload, Signature/ you are listing the items and the 'with=
' clause describes how to put in the separation character.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; OK<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">4.&nbsp; In section 4 para #1 - I am having an is=
sue with the first sentence.<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Using &quot;object(s)&quot; to descr=
ibe the possible hierarchy is messy as it might be possible to interpret th=
is as interdependent rather than nested.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; &quot;JSON=
 object&quot; is a term from RFC 4627 - not a statement about possible hier=
archy.&nbsp; I could change the words &quot;represented by&quot; to &quot;r=
epresenting&quot;, as I think that would be clearer.&nbsp; Would that addre=
ss the
 issue for you?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; b) 'optionally additional properties' i=
s difficult for me to parse.<o:p></o:p></p>
<p class=3D"MsoPlainText">I think that &quot;and, optionally, additional pr=
operties&quot; would be better<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; OK<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">5.&nbsp; In section 4 para #2 - Two items, this d=
oes not talk about header parameter not defined in this document and I thin=
k it might be more understandable if this was done as a series of bullet po=
ints rather than just text.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Actually, =
the paragraph does talk about header parameters not defined in this documen=
t: &quot;Unless listed as a critical header parameter, per Section 4.1.10, =
all other header parameters MUST be ignored
 when not understood.&quot;&nbsp; Editorially, I don't think that bullets w=
ould be the best choice, because the points being made in the different sen=
tences are not grammatically parallel.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">6.&nbsp; In section 4.1.1 - I think the current t=
ext for rejection on alg is written on the assumption that there is only on=
e signature/MAC on the object.&nbsp; If there are two and there is both an =
implementation and a key for one signature but
 the second either does not have an implementation or a key<o:p></o:p></p>
<p class=3D"MsoPlainText">- is this still a MUST reject situation?<o:p></o:=
p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; About the =
multi-signature case, we could say something like: &quot;If there are multi=
ple signatures and/or MACs over the payload, then at least one &quot;alg&qu=
ot; value must be supported and have an associated key
 as described above, or the JWS must be rejected&quot;.&nbsp; Does that des=
cribe the semantics you had in mind?&nbsp; What does CMS do in this case?<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">7.&nbsp; In section 4.1.2 - Are you going to impo=
se a minimum version TLS - specifically are SSL and TLS v1.0 allowed?<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I propose =
that we add this security considerations subsection, which is derived from =
that used in OAuth.&nbsp; (This language resulted from the resolution of a =
DISCUSS, if I recall correctly.)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0">TLS Requirements<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0">Implementations MUST support TLS. Which version(s) ought to be impl=
emented will vary over time, and depend on the widespread deployment and kn=
own security vulnerabilities at the time
 of implementation. At the time of this writing, TLS version 1.2 [RFC5246] =
is the most recent version, but has very limited actual deployment, and mig=
ht not be readily available in implementation toolkits. TLS version 1.0 [RF=
C2246] is the most widely deployed
 version, and will give the broadest interoperability. <o:p></o:p></span></=
p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0">To protect against information disclosure and tampering, confidenti=
ality protection MUST be applied using TLS with a ciphersuite that provides=
 confidentiality and integrity protection.
<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in"><span style=3D"color:#=
0070C0">Whenever TLS is used, a TLS server certificate check MUST be perfor=
med, per RFC 6125 [RFC6125].<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">8.&nbsp; In section 4.1.2 - Is implementation of =
this parameter required?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Only in th=
e sense described in the second paragraph of section 4:&nbsp; &#8220;All ot=
her header parameters defined by this specification that are not so designa=
ted MUST be ignored when not understood.&#8221;&nbsp; This was
 part of the &#8220;MUST understand&#8221; resolution proposed by Eric Resc=
orla, Nat Sakimura, and others and confirmed by the working group.&nbsp; In=
complete implementations are OK &#8211; just not fully functional.<o:p></o:=
p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">9.&nbsp; In section 4.1.3 - see comment 8<o:p></o=
:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Same answe=
r as 8<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">10.&nbsp; In section 4.1.3 - Should we make a not=
e that the private portions of a key MUST NOT be included?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; OK<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">11.&nbsp; In section 4.1.4 - Other than consisten=
cy - what is the requirement here for doing HTTPS - are you expecting self-=
signed certificates to be common and trying to get around trust anchor issu=
es?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Yes<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">12. In section 4.1.4 - see comment 8&nbsp; -- ok =
- and lots of other sections<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Same answe=
r as 8<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText">13.&nbsp; In section 4.1.6 - There is a verificat=
ion statement on X.509 certificates.&nbsp; There is not a similar statement=
 for x5t or x5u.&nbsp; Should there be?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Thanks for=
 pointing this out.&nbsp; I think there should be.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">14. In section 4.1.9 - This section gives why I t=
hought that JWT was a cty value.&nbsp; It explicitly says so.&nbsp; Mike ha=
s said this is not true.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I can see =
why the example is misleading.&nbsp; &#8220;cty&#8221;: &#8220;JWT&#8221; i=
s only used when the JWT representation signs or encrypts another JWT in a =
nested fashion &#8211; not when a set of claims are directly signed or encr=
ypted.&nbsp;
 I&#8217;ll remove it (and clarify the intent of &#8220;cty&#8221; and &#82=
20;typ&#8221; using language supplied by Richard).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">15.&nbsp; In section 4.1.9 - The last paragraph s=
tates that ctyp and typ values come from the same values space.&nbsp; Mike =
has said this is not true.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; It is true=
.&nbsp; If it appeared that I contradicted this, I misspoke or was misunder=
stood.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">16. In section 4.1.10 - I think there is an inter=
esting discussion point on the use of 'crit' in the following case.&nbsp; I=
 want to ensure that you implement a feature in the base specification that=
 the base specification has said you do
 not need to implement.&nbsp; I am not sure based on the current document l=
anguage if this is an empty set or not.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; There&#821=
7;s a distinction that Eric Rescorla made when designing the &#8220;MUST un=
derstand&#8221; solution between fields that would result in security bugs =
if not fully supported versus fields that would result in
 the inability to process the content if not supported.&nbsp; For instance,=
 the key selection fields are in the latter category.&nbsp; If someone does=
n&#8217;t support &#8220;x5t&#8221; you might not know what certificate to =
use and so you couldn&#8217;t process the JWS, but that would just
 be functionality deficiency &#8211; not a security bug.&nbsp; &#8220;crit&=
#8221; is there to be able to dynamically designate new fields as being in =
the former category.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">17.&nbsp; In section 5.1 step 3 - I don't know if=
 there is a reason to make a statement about suggesting that whitespace be =
removed when you are planning on doing a compact representation.&nbsp; This=
 is one of those things that would lead to a
 smaller encoding.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; The statem=
ent is that whitespace is permitted and no canonicalization need be perform=
ed.&nbsp; It doesn&#8217;t say that you can&#8217;t remove whitespace or pe=
rform canonicalization if you choose.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">18.&nbsp; In section 5.1, step 4 - the phrase &qu=
ot;If the JWS protected header is not present...&quot; leaves me lost.&nbsp=
; I don't understand what this term is coming from as you have not yet intr=
oduced it in terms of how to build a signed message.&nbsp;
 Specifically, there has been nothing at this point which tells me how to d=
ecide what goes where.&nbsp; I strongly feel that section 8 needs to move b=
efore this section.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; The JWS Pr=
otected Header was already defined in the Terminology section.&nbsp; We cou=
ld make this more explicit by saying that the base64url encoding of the JWS=
 Protected Header is the value of the &#8220;protected&#8221;
 member in the JSON Serialization, if present.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">19.&nbsp; In section 5.1, Step 11 - I think this =
should be moved forward to say - repeat the steps X to Y for each signature=
 to be processed.&nbsp; I also don't think this needs to say anything about=
 the serialization method being used.<o:p></o:p></p>
<p class=3D"MsoPlainText">It is not relevant.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I will add=
 the language about &#8220;steps X to Y&#8221; as you suggest.&nbsp; Saying=
 that this only applies for the JSON Serialization is important, since this=
 step is inapplicable to the Compact Serialization.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">20.&nbsp; In section 5.1, step 5 - the last sente=
nce in this step would appear to be out of place.&nbsp; This is not a requi=
rement of computing the signature, but one of building the JWS header which=
 is step 2.&nbsp; This MUST is just a re-iteration
 of one someplace else so it does not add anything.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Agreed &#8=
211; I&#8217;ll delete this sentence.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">21. In section 5.1, step 9 - I believe that the c=
ompact serialization should be moved to its own section.&nbsp; There should=
 not be any apparent preference in the document for one of the serializatio=
n methods.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I will cre=
ate a Compact Serialization section paralleling the JSON Serialization sect=
ion, but I disagree about removing the concatenation language here.&nbsp; O=
ne of the beautiful things about the Compact
 Serialization is that it *<b>can</b>* be described in a single sentence, a=
s is step 9.&nbsp; It will be easier for most developers to continue having=
 this single sentence in-line, rather than making them jump to another sect=
ion when a single sentence in place already
 does the job nicely.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">22. In Section 5 - I am going to make a suggestio=
n that I would like you to consider, although I think that it might not be =
to your liking.&nbsp; My personal view of the world has been one of: There =
is a JSON serialization that is the object.&nbsp;
 There is a way to map from the JSON serialization to the compact serializa=
tion.&nbsp; The mapping requires a set of constraints on the original seria=
lization.&nbsp; Thus in my world, I build the internal JSON object represen=
tation, run the computations on that internal
 representation and then either run the mapping to the compact serializatio=
n or serialize the JSON object representation to get the output.&nbsp; Usin=
g this as the method would mean that section 5 would be an object represent=
ation for JSON, section 6 would be how
 to do the mappings to and from the compact form, section 7 would be the ho=
w to do this.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; What you&#=
8217;re doing is functionally equivalent to what&#8217;s in the spec now, b=
ut pretty inefficient and unnecessary if you&#8217;re only using the Compac=
t Serialization, which will be a common model for many use
 cases.&nbsp; I think a better model is that the Compact Serialization and =
JSON Serialization are peers &#8211; sharing 95%&#43; of the processing rul=
es and then applying a particular serialization for the data values manipul=
ated by those processing rules.&nbsp; That&#8217;s why the
 specs describe things in terms of abstract fields and bindings of those fi=
elds to elements of serializations &#8211; rather than describing things on=
ly in terms of the serialized representations.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">23.&nbsp; In section 5.3 - Are steps #1 and #2 no=
t the requirement of the JSON parser and not my application?&nbsp; I would =
suggest reading some of the updated text on member name string comparison f=
rom the JSON mailing list for a cleaner way
 to write this section.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Specific t=
ext suggestions welcomed.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">24.&nbsp; Section 6 appears to be extraneous and =
could be deleted.&nbsp; What is the purpose that this is supposed to serve?=
&nbsp; Why is that purpose not covered in the description of the alg member=
?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I agree.&n=
bsp; FWIW, Richard privately made the same suggestion about the parallel se=
ction in JWE, which I also agree with.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">25.&nbsp; Section 7 would appear to be better ser=
ved by making it section 4.1.2 and making section on jku, jwk, x5u, x5t, x5=
c and kid as subjections of it.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; The proble=
m with this suggestion is that it would make the list of reserved header pa=
rameters no longer syntactically parallel.&nbsp; And I do believe there&#82=
17;s value in having a paragraph that talks about
 the semantics of key identification all-up, rather than trying to do it in=
 a manner that&#8217;s scattered in bits and pieces into the individual par=
ameter definitions.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">26.&nbsp; Section 8 - I found the presentation co=
nfusing.&nbsp; I would have expected that it would be made in the normal ma=
nner - that is you have an object and a list of members each with its own s=
ection - and those members may have sub members
 which are listed.&nbsp; There would then be references back to the members=
 defined in section 4<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I agree th=
at an object-centered approach will be easier to follow.&nbsp; Thanks for s=
uggesting it.&nbsp; Some of that content is now in prose.&nbsp; I&#8217;ll =
restructure to use lists/tables instead as you suggest.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">27.&nbsp; Section 9 - I would dispute the content=
 of this section vigorously.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#0070C0">Mike&gt; Hannes and De=
rek and Stephen and Sean, at least to the OAuth WG, have made it VERY CLEAR=
 that the IESG requires MTI features to be defined.&nbsp; Of the JSON and C=
ompact serializations, the latter is the only
 one in widespread use, therefore it makes sense for it to be the MTI seria=
lization.&nbsp; Particularly since JWTs mandate that only the Compact Seria=
lization be used, it would make no sense from a working group coordination =
point of view to try to mandate that
 the JSON serialization also be MTI &#8211; especially since it&#8217;s mor=
e complicated.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">I stopped reviewing after section 9.<o:p></o:p></=
p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Thanks for=
 all the useful comments.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoPlainText">Jim<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">_______________________________________________<o=
:p></o:p></p>
<p class=3D"MsoPlainText">jose mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"mailto:jose@ietf.org"><span style=3D"c=
olor:windowtext;text-decoration:none">jose@ietf.org</span></a><o:p></o:p></=
p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
jose"><span style=3D"color:windowtext;text-decoration:none">https://www.iet=
f.org/mailman/listinfo/jose</span></a><o:p></o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1A4ATK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Thu Jun 27 15:51:00 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F38E11E80F2 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.165
X-Spam-Level: 
X-Spam-Status: No, score=-3.165 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NysfeDMqtO6B for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:50:51 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5BC11E80A5 for <jose@ietf.org>; Thu, 27 Jun 2013 15:50:51 -0700 (PDT)
Received: from BY2FFO11FD013.protection.gbl (10.1.15.203) by BY2FFO11HUB012.protection.gbl (10.1.14.83) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 22:50:50 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD013.mail.protection.outlook.com (10.1.14.75) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 22:50:50 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 22:50:02 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>
Thread-Topic: Comments on version 11 of draft-ietf-jose-json-web-encryption
Thread-Index: Ac5qBROwQiVllCE1TESnJHctXErySQJdAyhQ
Date: Thu, 27 Jun 2013 22:50:01 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1AFC@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com>
In-Reply-To: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1AFCTK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(43784003)(377454003)(51914003)(189002)(199002)(13464003)(69226001)(46102001)(81542001)(81342001)(77982001)(51856001)(59766001)(74876001)(71186001)(56776001)(55846006)(77096001)(54316002)(74662001)(31966008)(74502001)(54356001)(76482001)(53806001)(47446002)(56816003)(76796001)(76786001)(44976004)(19300405004)(74366001)(79102001)(15202345003)(74706001)(47736001)(49866001)(50986001)(47976001)(16236675002)(512954002)(65816001)(20776003)(63696002)(6806003)(33656001)(16406001)(4396001)(66066001)(80022001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB012; H:TK5EX14HUBC107.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Comments on version 11 of draft-ietf-jose-json-web-encryption
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:51:00 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1AFCTK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the useful review comments, Jim.  Replies inline prefixed by "Mi=
ke>"...



-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Saturday, June 15, 2013 2:08 PM
To: draft-ietf-jose-json-web-encryption@tools.ietf.org
Cc: jose@ietf.org
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption



Gentlemen,



Here are a few comments for consideration.  Note that some of the comments =
from the JWS review are also applicable to this document as much of the lan=
guage in places is the same.



1.  In Section 4.1.2 - You probably want to say an AEAD algorithm not an AE=
 algorithm



Mike> The problem with the "AEAD" terminology is that it implies both algor=
ithm and encoding properties.  We want the algorithm properties but not the=
 encoding properties defined by RFC 5116.  Thus, a conscious terminology ch=
ange was made in -08 to longer use the term "AEAD".



2  In section 4.1.3 - I would suggest changing the text to "This parameter =
MUST be omitted unless required by the algorithm in the "alg" member.  This=
 header parameter MUST be understood if an algorithm is supported that requ=
ires it."



Mike> OK



3.  In section 4.1.4 - Does the group agree that compression is a required =
feature to implement?



Mike> This feature was discussed at IETF 83 and has been in place in the cu=
rrent form ever since -02.  I'd be shocked if people didn't believe this fe=
ature was necessary.



4.  Why not reference sections 4.1.5 - 10 by reference with a comment that =
these refer to the key that was used to encrypt the content?  Is there a be=
nefit of having them listed here?  Is there a difference in the way they ar=
e interpreted other than the recipient/originator thing?



Mike> I assume you mean reference them in JWS?  There's a complete list her=
e so that it's clear to JWE implementers what the reserved header parameter=
s are without having to reference other specs.  And yes, the JWS and JWE ke=
y selection parameters are the same other than the JWS sender/JWE receiver =
difference.



5.  Why not reference sections 4.1.11-12 from the JWS document?  Is there a=
 difference in the way they are interpreted?



Mike> (Apparently I didn't understand what you were suggesting in 4, having=
 seen this next question.)  In any event, in JWS they reference the key tha=
t is used to verify the signature.  In JWE they reference the key to which =
the content was encrypted.  That's the difference in all these parameters.



6.  If we are not going with an alphabetic order of names, the I would sugg=
est that apu should be next to exp as they are used in the same context and=
 therefore having them adjacent makes sense.



Mike> Actually, Richard had suggested moving "apu" to the key agreement sec=
tion in JWA, since its use is algorithm-specific.  I think I agree with him=
.



7.  Is there a reason not to reference 4.1.14 from JWS?  Is there a differe=
nce in interpretation?



Mike> Stylistically, it seems easier for implementers of JWE to have a comp=
lete list of general-purpose parameter definitions than to have some here a=
nd some there.  The example is also different, because one is a JWS header =
and the other is a JWE header.



                                                                Thanks agai=
n,

                                                                -- Mike



Jim





--_000_4E1F6AAD24975D4BA5B1680429673943678A1AFCTK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Thanks for the useful review comments, Jim.&nbsp;=
 Replies inline prefixed by &#8220;<span style=3D"color:#0070C0">Mike&gt;</=
span>&#8221;&#8230;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: Jim Schaad [mailto:ietf@augustcellars.com] <br>
Sent: Saturday, June 15, 2013 2:08 PM<br>
To: draft-ietf-jose-json-web-encryption@tools.ietf.org<br>
Cc: jose@ietf.org<br>
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Gentlemen,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Here are a few comments for consideration.&nbsp; =
Note that some of the comments from the JWS review are also applicable to t=
his document as much of the language in places is the same.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1.&nbsp; In Section 4.1.2 - You probably want to =
say an AEAD algorithm not an AE algorithm<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; The proble=
m with the &#8220;AEAD&#8221; terminology is that it implies both algorithm=
 and encoding properties.&nbsp; We want the algorithm properties but not th=
e encoding properties defined by RFC 5116.&nbsp; Thus, a conscious
 terminology change was made in -08 to longer use the term &#8220;AEAD&#822=
1;.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">2&nbsp; In section 4.1.3 - I would suggest changi=
ng the text to &quot;This parameter MUST be omitted unless required by the =
algorithm in the &quot;alg&quot; member.&nbsp; This header parameter MUST b=
e understood if an algorithm is supported that requires it.&quot;<o:p></o:p=
></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; OK<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">3.&nbsp; In section 4.1.4 - Does the group agree =
that compression is a required feature to implement?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; This featu=
re was discussed at IETF 83 and has been in place in the current form ever =
since -02.&nbsp; I&#8217;d be shocked if people didn&#8217;t believe this f=
eature was necessary.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">4.&nbsp; Why not reference sections 4.1.5 - 10 by=
 reference with a comment that these refer to the key that was used to encr=
ypt the content?&nbsp; Is there a benefit of having them listed here?&nbsp;=
 Is there a difference in the way they are interpreted
 other than the recipient/originator thing?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I assume y=
ou mean reference them in JWS?&nbsp; There&#8217;s a complete list here so =
that it&#8217;s clear to JWE implementers what the reserved header paramete=
rs are without having to reference other specs.&nbsp; And yes,
 the JWS and JWE key selection parameters are the same other than the JWS s=
ender/JWE receiver difference.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">5.&nbsp; Why not reference sections 4.1.11-12 fro=
m the JWS document?&nbsp; Is there a difference in the way they are interpr=
eted?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; (Apparentl=
y I didn&#8217;t understand what you were suggesting in 4, having seen this=
 next question.)&nbsp; In any event, in JWS they reference the key that is =
used to verify the signature.&nbsp; In JWE they reference
 the key to which the content was encrypted.&nbsp; That&#8217;s the differe=
nce in all these parameters.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">6.&nbsp; If we are not going with an alphabetic o=
rder of names, the I would suggest that apu should be next to exp as they a=
re used in the same context and therefore having them adjacent makes sense.=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Actually, =
Richard had suggested moving &#8220;apu&#8221; to the key agreement section=
 in JWA, since its use is algorithm-specific.&nbsp; I think I agree with hi=
m.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">7.&nbsp; Is there a reason not to reference 4.1.1=
4 from JWS?&nbsp; Is there a difference in interpretation?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Stylistica=
lly, it seems easier for implementers of JWE to have a complete list of gen=
eral-purpose parameter definitions than to have some here and some there.&n=
bsp; The example is also different, because
 one is a JWS header and the other is a JWE header.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks again,<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Jim<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1AFCTK5EX14MBXC283r_--

From rlb@ipv.sx  Thu Jun 27 15:56:02 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E75811E8115 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level: 
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KsKSEvzOGrr for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 15:55:57 -0700 (PDT)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by ietfa.amsl.com (Postfix) with ESMTP id 8560A11E8108 for <jose@ietf.org>; Thu, 27 Jun 2013 15:55:57 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so1318845obb.5 for <jose@ietf.org>; Thu, 27 Jun 2013 15:55:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=tI8KHhPRap8NwdGF0BVLCt9EiKg5vezOjYFXg7dZv2E=; b=Pwv3srsmpg1tWeWsmyouKauJeNMDy7M8NE3zniEmb+Ckqb935EdmVYPYQC+ABWgJqp i5Xkh4ydpmdn+IlSJFoYYys3Cu0GZibBpIdIfihDK/CziP+wBi79AnKK/I1bnIqbbXcY smebFdtSnQmzHpQ5zGWxagTw/QMDEd9BbUA079pwhGgwv8FYA1U62sYzBj2vOULgiQuk Fvh8QwfqjuH3KbaJM62UwWm6HTzzunDTKQgs3fP00geBnnm1WzLrOjRpGYXIN+yZ/hD6 BdLr59IjiWaDgZpqZTWRQTOnmDsHbhVMbYr3gt4aOMrtPXHqudn7HrnplD20fn/AlI3c yM/w==
MIME-Version: 1.0
X-Received: by 10.182.142.104 with SMTP id rv8mr5255123obb.3.1372373757052; Thu, 27 Jun 2013 15:55:57 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 27 Jun 2013 15:55:56 -0700 (PDT)
X-Originating-IP: [192.1.51.93]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 18:55:56 -0400
Message-ID: <CAL02cgS3Hq2EGH9=+UH9wssfnsB9=Ns43jbTjhzqX9cMrhwtvw@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2eaae49ce5e04e02aaae9
X-Gm-Message-State: ALoCoQmqr9qxYYS305ZO/70E2PlZZjqXrgcqMRwWUd/rw0Typb3k9vo1ALQSA+yl4olNUul6QC/Z
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 22:56:02 -0000

--001a11c2eaae49ce5e04e02aaae9
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

In a JSON-formatted JWS, the top-level JSON fields are not covered by the
signature (only the protected header).  See the examples in my previous
mail and in John's.
--Richard


On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  If an intermediary reorders the fields the signature validation will
> fail, so I=92m not worried about that.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 27, 2013 3:48 PM
> *To:* Mike Jones
> *Cc:* John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
> ** **
>
> On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
>  I=92ve come to believe that James=92 proposed language does a good job o=
f
> making security-appropriate restrictions while allowing the use of existi=
ng
> parsers.  It was:****
>
>  ****
>
> A creator of a JOSE message MUST NOT put duplicate names in any JSON
> object in a JOSE header.  To prevent attacks where a JOSE message is
> interpreted as different valid messages by different recipients, each
> recipient MUST either reject messages with duplicate names or accept only
> the last name.****
>
>  ****
>
> I might change =93or accept only the last name=94 to =93or use a parser t=
hat
> always uses the lexically last name for any duplicate member names, per
> [ECMAScript]=94 for clarity, but the intent is the same.****
>
>  ****
>
> Would that work for people?****
>
>  ****
>
>                                                             -- Mike****
>
>  ** **
>
> ** **
>
> That's close.  I don't think we can allow the "lexically last" because
> elements in a JSON dictionary can be re-ordered.  Suppose there a helpful
> intermediary that sorts a JSON dictionary in descending alphabetical orde=
r
> of values. ****
>
> When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }**=
*
> *
>
> It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }****
>
> ** **
>
> The only way to avoid the ambiguity is to reject objects with duplicate
> keys.****
>
> ** **
>
>
> I realize that this renders most JSON parsers incompatible.  Implementors
> will need to add a secondary check.  I feel your pain.  But hopefully thi=
s
> pain will be temporary; the ambiguity will be fixed by the JSON WG and
> ECMA, and parsers will be updated.  Even in the short run, it doesn't see=
m
> like it would be that hard to mod existing parsers to have a "strict" fla=
g.
> ****
>
> ** **
>
> """****
>
> A creator of a JOSE message MUST NOT put duplicate names in any JSON
> object in a JOSE header.  To prevent attacks where a JOSE message is
> interpreted as different valid messages by different recipients, each
> recipient MUST reject messages.  Implementations MUST NOT select the
> lexically last name, as required by [ECMAScript], since this could lead
> them to select the incorrect value if an intermediary re-orders the field=
s
> in a dictionary.  If an implementation uses a JSON parser that does not
> reject objects with duplicate fields, then it MUST verify that there are =
no
> dictionaries with duplicate fields in the JSON object.****
>
> """****
>
> ** **
>
> --Richard ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
>  ****
>
>   ****
>
> *From:* John Bradley [mailto:ve7jtb@ve7jtb.com]
> *Sent:* Thursday, June 27, 2013 8:49 AM
> *To:* Tim Bray
> *Cc:* Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ****
>
> The problem is not wanting to leave a hole for malicious signers to creat=
e
> JWT that may be misinterpreted by the receiver.  Accidental interop
> problems from bad signers are not a big concern for me and are covered by
> MUST NOT emit dups.****
>
>  ****
>
> Accepting malformed JSON as the envelope may lead to real security issues=
.
> ****
>
>  ****
>
> This may be more of an issue for the JSON encoding than the compact as
> there you need to be careful the body you process for the signature is th=
e
> body that the application uses.****
>
>  ****
>
> What happens if you receive.****
>
>  ****
>
> {"protected":<integrity-protected shared header contents>",****
>
>       "unprotected":<non-integrity-protected shared header contents>",***=
*
>
>       "payload":"<original payload contents>",****
>
>       "payload":"<bad payload contents inserted by attacker>"****
>
>       "signatures":[****
>
>        {"header":"<per-signature unprotected header 1 contents>",****
>
>         "signature":"<signature 1 contents>"},****
>
>        ...****
>
>        {"header":"<per-signature unprotected header N contents>",****
>
>         "signature":"<signature N contents>"}],****
>
>      }****
>
>   ****
>
> If the JOSE library validates on the first version of "payload" and the
> application using a different JSON parser only sees the second "payload" =
we
> have a wrapping attack similar to xmldsig.****
>
>  ****
>
> I can't off the top of my head think of what you could do in the compact
> serialization that would lead to a successful attack given that the
> signature is over the base64url encoded segments, that prevents attackers
> from modifying the JSON while maintaining integrity.****
>
>  ****
>
> It is a real issue for the JSON serialization though.****
>
>  ****
>
> John B.****
>
>  ****
>
> On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com> wrote:****
>
> ** **
>
> The approach just seems wrong.  If we require that conforming
> implementations MUST NOT emit dupes, then authors of receiving software c=
an
> just pick the best-performing parser with the nicest API, because they
> *all* perform correctly when there are no dupes.
>
> Who=92s going to own the responsibility for making the authoritative find=
ing
> that of the many JSON parsers in the Java ecosystem, these ones, but not
> those ones, are usable in JOSE applications?  And suppose one that has be=
en
> previously OK is quietly optimized on GitHub to run 30% faster and as a
> side-effect silently ignores dupes?  ****
>
> The benefit of using JSON is that there is widely deployed software to
> handle it.  It is a known problem that sloppy spec drafting has allowed
> various kinds of problems to occur when dupe keys are received. =93Doctor=
, it
> hurts when I do this.=94 =93So... don=92t do that.=94****
>
> Are we also going to specify the behavior of receiving software when the
> JSON has a misplaced quotation mark?  A missing trailing =93}=94?****
>
>  -T****
>
>  ****
>
>  ****
>
> On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> Most JSON libraries that silently accept [sob] dupe keys at least
> consistently use the last key. Allowing just that behaviour (or rejecting
> dupes), while forbidding acceptance of a non-last dupe (eg first key), is
> safe and allows most JSON libraries to be used. Since this accepts most
> libraries I think it is practical.****
>
>  ****
>
> Hence I suggest:****
>
>  ****
>
> >   A creator of a JOSE message MUST NOT put duplicate names in any JSON*=
*
> **
>
> > object in a JOSE header.****
>
> >   To prevent attacks where a JOSE message is interpreted as different**=
*
> *
>
> > valid messages by different recipients, each recipient MUST either****
>
> > reject messages with duplicate names or accept only the last name.****
>
>  ****
>
> This isn=92t =93truly predictable=94 as a message with dupes might be acc=
epted
> or rejected. The crucial point is that if a message is accepted it is
> predictable.****
>
>  ****
>
> --****
>
> James Manger****
>
>  ****
>
> *From:* Tim Bray [mailto:tbray@textuality.com]
> *Sent:* Thursday, 27 June 2013 4:16 PM
> *To:* Manger, James H
> *Cc:* Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ****
>
>  ****
>
> Well, you have a practical problem in that most implementers will want to
> use a standard JSON library, which is good practice because it will be
> well-debugged, and most libraries [sob] silently take care of dupe keys a=
nd
> don=92t have a way to tell the client software what happened. So if you w=
ant
> truly predictable behavior, you=92re forcing the use of hand-constructed =
JSON
> parsers. And that sucks, because getting good performance in JSON parsing
> is surprisingly hard, with dramatic performance differences between
> implementations. So you=92re forcing receiving software which wants to be
> conformant to use a hand-rolled parser which will probably have lousy
> performance and have other bugs which in fact may compromise security mor=
e
> than dupe-key tricks could.  -T****
>
>  ****
>
> On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> > I think it=92s a nice clean minimal solution to say that producers MUST
> > NOT generate dupes, end of story.  I don=92t think saying anything beyo=
nd
> > that adds value. -T****
>
> Clean and minimal that may be, but it ignores the security issue. We don'=
t
> want a malicious producer (who is so malicious they ignore a MUST) to
> create JOSE messages that a JOSE-compliant security layer accepts as
> "benign interpretation #1" so it passes the message on to the
> JOSE-compliant backend app that acts on "nasty interpretation #2".
>
> --
> James Manger****
>
>  ****
>
>  ****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>  ** **
>

--001a11c2eaae49ce5e04e02aaae9
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In a JSON-formatted JWS, the top-level JSON fields are not=
 covered by the signature (only the protected header). =A0See the examples =
in my previous mail and in John&#39;s.<div>--Richard</div></div><div class=
=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Jun 27, 2013 at 6:51 PM, Mike Jo=
nes <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@microsoft.com" ta=
rget=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">






<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If an intermediary reorde=
rs the fields the signature validation will fail, so I=92m not worried abou=
t that.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:48 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-jose-json-web-signature@tools.ietf.org" target=3D"_blank">draf=
t-ietf-jose-json-web-signature@tools.ietf.org</a></span></p>
<div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I=92ve come to believe th=
at James=92 proposed language does a good job of making security-appropriat=
e
 restrictions while allowing the use of existing parsers.=A0 It was:</span>=
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">A creator of a JOSE message MUST NOT put duplica=
te names in any JSON object in a JOSE header.=A0 To prevent attacks where a=
 JOSE message is interpreted as different valid messages
 by different recipients, each recipient MUST either reject messages with d=
uplicate names or accept only the last name.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I might change =93or acce=
pt only the last name=94 to =93or use a parser that always uses the lexical=
ly
 last name for any duplicate member names, per [ECMAScript]=94 for clarity,=
 but the intent is the same.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Would that work for peopl=
e?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That&#39;s close. =A0I don&#39;t think we can allow =
the &quot;lexically last&quot; because elements in a JSON dictionary can be=
 re-ordered. =A0Suppose there a helpful intermediary that sorts a JSON dict=
ionary in descending alphabetical order of values.=A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">When it gets: {=A0&quot;payload&quot;: &quot;bad stu=
ff&quot;,=A0=A0&quot;payload&quot;: &quot;good stuff&quot;, ... }<u></u><u>=
</u></p>
</div>
<div>
<p class=3D"MsoNormal">It emits: {=A0&quot;payload&quot;: &quot;good stuff&=
quot;,=A0=A0&quot;payload&quot;: &quot;bad=A0stuff&quot;, ... }<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The only way to avoid the ambiguity is to reject obj=
ects with duplicate keys.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
I realize that this renders most JSON parsers incompatible. =A0Implementors=
 will need to add a secondary check. =A0I feel your pain. =A0But hopefully =
this pain will be temporary; the ambiguity will be fixed by the JSON WG and=
 ECMA, and parsers will be updated. =A0Even
 in the short run, it doesn&#39;t seem like it would be that hard to mod ex=
isting parsers to have a &quot;strict&quot; flag.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">A creator of a JOSE message MUST NOT put duplicate n=
ames in any JSON object in a JOSE header. =A0To prevent attacks where a JOS=
E message is interpreted as different valid messages by different recipient=
s, each recipient MUST reject messages.
 =A0Implementations MUST NOT select the lexically last name, as required by=
 [ECMAScript], since this could lead them to select the incorrect value if =
an intermediary re-orders the fields in a dictionary. =A0If an implementati=
on uses a JSON parser that does not
 reject objects with duplicate fields, then it MUST verify that there are n=
o dictionaries with duplicate fields in the JSON object.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bra=
dley [mailto:<a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_blank">ve7jtb@=
ve7jtb.com</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><u></u><u></u><=
/p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The problem is not wanting to leave a hole for malic=
ious signers to create JWT that may be misinterpreted by the receiver. =A0A=
ccidental interop problems from bad signers are not
 a big concern for me and are covered by MUST NOT emit dups.<u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Accepting malformed JSON as the envelope may lead to=
 real security issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This may be more of an issue for the JSON encoding t=
han the compact as there you need to be careful the body you process for th=
e signature is the body that the application uses.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">What happens if you receive.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<pre><span style=3D"font-size:12.0pt">{&quot;protected&quot;:&lt;integrity-=
protected shared header contents&gt;&quot;,</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;unprotected&quo=
t;:&lt;non-integrity-protected shared header contents&gt;&quot;,</span><u><=
/u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&=
quot;&lt;original payload contents&gt;&quot;,</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&=
quot;&lt;bad payload contents inserted by attacker&gt;&quot;</span><u></u><=
u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;signatures&quot=
;:[</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot=
;:&quot;&lt;per-signature unprotected header 1 contents&gt;&quot;,</span><u=
></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature=
&quot;:&quot;&lt;signature 1 contents&gt;&quot;},</span><u></u><u></u></pre=
>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 ...</span><u></u><=
u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot=
;:&quot;&lt;per-signature unprotected header N contents&gt;&quot;,</span><u=
></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature=
&quot;:&quot;&lt;signature N contents&gt;&quot;}],</span><u></u><u></u></pr=
e>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0 }</span><u></u><u></u></=
pre>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If the JOSE library validates on the first version o=
f &quot;payload&quot; and the application using a different JSON parser onl=
y sees the second &quot;payload&quot; we have a wrapping attack similar
 to xmldsig.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I can&#39;t off the top of my head think of what you=
 could do in the compact serialization that would lead to a successful atta=
ck given that the signature is over the base64url encoded
 segments, that prevents attackers from modifying the JSON while maintainin=
g integrity.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It is a real issue for the JSON serialization though=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">John B.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"=
mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</a>&gt;=
 wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The approach just see=
ms wrong.=A0 If we require that conforming implementations MUST NOT emit du=
pes, then authors of receiving software can just pick the best-performing p=
arser with the
 nicest API, because they *all* perform correctly when there are no dupes.=
=A0 <br>
<br>
Who=92s going to own the responsibility for making the authoritative findin=
g that of the many JSON parsers in the Java ecosystem, these ones, but not =
those ones, are usable in JOSE applications?=A0 And suppose one that has be=
en previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?=
=A0 <u></u><u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The benefit of using =
JSON is that there is widely deployed software to handle it.=A0 It is a kno=
wn problem that sloppy spec drafting has allowed various kinds of problems =
to occur when
 dupe keys are received. =93Doctor, it hurts when I do this.=94 =93So... do=
n=92t do that.=94<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Are we also going to =
specify the behavior of receiving software when the JSON has a misplaced qu=
otation mark?=A0 A missing trailing =93}=94?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0-T<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &l=
t;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">Jame=
s.H.Manger@team.telstra.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Most JSON =
libraries that silently accept [sob] dupe keys at least consistently use th=
e
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hence I su=
ggest:</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; =A0=A0A creator of a JOSE message MUST NOT put=
 duplicate names in any JSON</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.</span><u></u><u></u><=
/p>
<p><span lang=3D"EN-AU">&gt; =A0=A0To prevent attacks where a JOSE message =
is interpreted as different</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">This isn=
=92t =93truly predictable=94 as a message with dupes might be accepted or r=
ejected.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">--</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">James Mang=
er</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray=
 [mailto:<a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@te=
xtuality.com</a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">Well, you have a practical prob=
lem in that most implementers will want to use a standard JSON library, whi=
ch is good practice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don=92t have =
a way to tell the client software what happened. So if you want truly predi=
ctable behavior, you=92re forcing the use of hand-constructed JSON parsers.=
 And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you=92re forcing receiving softwa=
re which wants to be conformant to use a hand-rolled parser which will prob=
ably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.=A0 -T</span><u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-AU">=
=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 P=
M, Manger, James H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" t=
arget=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; wrote:</span><u></=
u><u></u></p>

<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-AU">=
&gt; I think it=92s a nice clean minimal solution to say that producers MUS=
T<br>
&gt; NOT generate dupes, end of story.=A0 I don=92t think saying anything b=
eyond<br>
&gt; that adds value. -T</span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">Clean and minimal that may be, =
but it ignores the security issue. We don&#39;t want a malicious producer (=
who is so malicious they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger</span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c2eaae49ce5e04e02aaae9--

From Michael.Jones@microsoft.com  Thu Jun 27 16:00:33 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C9511E8118 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ij8o1ITkc-YG for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:00:27 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id 184AB21F9DCB for <jose@ietf.org>; Thu, 27 Jun 2013 16:00:26 -0700 (PDT)
Received: from BY2FFO11FD012.protection.gbl (10.1.15.202) by BY2FFO11HUB039.protection.gbl (10.1.14.122) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 27 Jun 2013 23:00:19 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD012.mail.protection.outlook.com (10.1.14.130) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 23:00:18 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 23:00:17 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkIAAhRqAgAAMGPCAABbogIAABEiAgAAKPgCAAAP6AIAAlCSAgAAIEICAAAw40IAAaLoAgAABBaCAAAFPAIAAACRA
Date: Thu, 27 Jun 2013 23:00:17 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1CF7@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgS3Hq2EGH9=+UH9wssfnsB9=Ns43jbTjhzqX9cMrhwtvw@mail.gmail.com>
In-Reply-To: <CAL02cgS3Hq2EGH9=+UH9wssfnsB9=Ns43jbTjhzqX9cMrhwtvw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1CF7TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(43544003)(377424004)(24454002)(377454003)(76796001)(31966008)(66066001)(69226001)(55846006)(76786001)(74662001)(47736001)(4396001)(6806003)(19300405004)(16406001)(76482001)(47446002)(74876001)(15202345003)(47976001)(54356001)(49866001)(51856001)(65816001)(50986001)(74706001)(53806001)(77982001)(44976004)(81542001)(59766001)(56816003)(33656001)(512954002)(80022001)(56776001)(20776003)(46102001)(74502001)(71186001)(77096001)(74366001)(16236675002)(81342001)(63696002)(54316002)(79102001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB039; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:00:33 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1CF7TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes - but this is only a problem for the JSON Serialization - and then, onl=
y for fields that are not integrity protected.

If you don't care enough about the content of the header fields to integrit=
y protect them, you clearly don't care whether an intermediary can tamper w=
ith them.  Reordering duplicate member names is the only the tip of the ice=
berg of the tampering that not integrity protecting header fields enables. =
 The intermediary could delete them or completely rewrite them!

Defending only against field reordering is like putting your finger in a ho=
le in the dike when the floodgates next door are already wide open.  Your f=
ield will definitely flood when the sea rises.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 27, 2013 3:56 PM
To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org; dra=
ft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text

In a JSON-formatted JWS, the top-level JSON fields are not covered by the s=
ignature (only the protected header).  See the examples in my previous mail=
 and in John's.
--Richard

On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
If an intermediary reorders the fields the signature validation will fail, =
so I'm not worried about that.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, June 27, 2013 3:48 PM
To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org<mail=
to:jose@ietf.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto=
:draft-ietf-jose-json-web-signature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text

On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
I've come to believe that James' proposed language does a good job of makin=
g security-appropriate restrictions while allowing the use of existing pars=
ers.  It was:

A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST ei=
ther reject messages with duplicate names or accept only the last name.

I might change "or accept only the last name" to "or use a parser that alwa=
ys uses the lexically last name for any duplicate member names, per [ECMASc=
ript]" for clarity, but the intent is the same.

Would that work for people?

                                                            -- Mike


That's close.  I don't think we can allow the "lexically last" because elem=
ents in a JSON dictionary can be re-ordered.  Suppose there a helpful inter=
mediary that sorts a JSON dictionary in descending alphabetical order of va=
lues.
When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }
It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }

The only way to avoid the ambiguity is to reject objects with duplicate key=
s.


I realize that this renders most JSON parsers incompatible.  Implementors w=
ill need to add a secondary check.  I feel your pain.  But hopefully this p=
ain will be temporary; the ambiguity will be fixed by the JSON WG and ECMA,=
 and parsers will be updated.  Even in the short run, it doesn't seem like =
it would be that hard to mod existing parsers to have a "strict" flag.

"""
A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST re=
ject messages.  Implementations MUST NOT select the lexically last name, as=
 required by [ECMAScript], since this could lead them to select the incorre=
ct value if an intermediary re-orders the fields in a dictionary.  If an im=
plementation uses a JSON parser that does not reject objects with duplicate=
 fields, then it MUST verify that there are no dictionaries with duplicate =
fields in the JSON object.
"""

--Richard






From: John Bradley [mailto:ve7jtb@ve7jtb.com<mailto:ve7jtb@ve7jtb.com>]
Sent: Thursday, June 27, 2013 8:49 AM
To: Tim Bray
Cc: Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf=
.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-=
jose-json-web-signature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text

The problem is not wanting to leave a hole for malicious signers to create =
JWT that may be misinterpreted by the receiver.  Accidental interop problem=
s from bad signers are not a big concern for me and are covered by MUST NOT=
 emit dups.

Accepting malformed JSON as the envelope may lead to real security issues.

This may be more of an issue for the JSON encoding than the compact as ther=
e you need to be careful the body you process for the signature is the body=
 that the application uses.

What happens if you receive.


{"protected":<integrity-protected shared header contents>",

      "unprotected":<non-integrity-protected shared header contents>",

      "payload":"<original payload contents>",

      "payload":"<bad payload contents inserted by attacker>"

      "signatures":[

       {"header":"<per-signature unprotected header 1 contents>",

        "signature":"<signature 1 contents>"},

       ...

       {"header":"<per-signature unprotected header N contents>",

        "signature":"<signature N contents>"}],

     }

If the JOSE library validates on the first version of "payload" and the app=
lication using a different JSON parser only sees the second "payload" we ha=
ve a wrapping attack similar to xmldsig.

I can't off the top of my head think of what you could do in the compact se=
rialization that would lead to a successful attack given that the signature=
 is over the base64url encoded segments, that prevents attackers from modif=
ying the JSON while maintaining integrity.

It is a real issue for the JSON serialization though.

John B.

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com<mailto:tbray@tex=
tuality.com>> wrote:

The approach just seems wrong.  If we require that conforming implementatio=
ns MUST NOT emit dupes, then authors of receiving software can just pick th=
e best-performing parser with the nicest API, because they *all* perform co=
rrectly when there are no dupes.

Who's going to own the responsibility for making the authoritative finding =
that of the many JSON parsers in the Java ecosystem, these ones, but not th=
ose ones, are usable in JOSE applications?  And suppose one that has been p=
reviously OK is quietly optimized on GitHub to run 30% faster and as a side=
-effect silently ignores dupes?
The benefit of using JSON is that there is widely deployed software to hand=
le it.  It is a known problem that sloppy spec drafting has allowed various=
 kinds of problems to occur when dupe keys are received. "Doctor, it hurts =
when I do this." "So... don't do that."
Are we also going to specify the behavior of receiving software when the JS=
ON has a misplaced quotation mark?  A missing trailing "}"?
 -T


On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
Most JSON libraries that silently accept [sob] dupe keys at least consisten=
tly use the last key. Allowing just that behaviour (or rejecting dupes), wh=
ile forbidding acceptance of a non-last dupe (eg first key), is safe and al=
lows most JSON libraries to be used. Since this accepts most libraries I th=
ink it is practical.

Hence I suggest:


>   A creator of a JOSE message MUST NOT put duplicate names in any JSON

> object in a JOSE header.

>   To prevent attacks where a JOSE message is interpreted as different

> valid messages by different recipients, each recipient MUST either

> reject messages with duplicate names or accept only the last name.

This isn't "truly predictable" as a message with dupes might be accepted or=
 rejected. The crucial point is that if a message is accepted it is predict=
able.

--
James Manger

From: Tim Bray [mailto:tbray@textuality.com<mailto:tbray@textuality.com>]
Sent: Thursday, 27 June 2013 4:16 PM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; draft-ietf=
-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-jose-json-web-sig=
nature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text


Well, you have a practical problem in that most implementers will want to u=
se a standard JSON library, which is good practice because it will be well-=
debugged, and most libraries [sob] silently take care of dupe keys and don'=
t have a way to tell the client software what happened. So if you want trul=
y predictable behavior, you're forcing the use of hand-constructed JSON par=
sers. And that sucks, because getting good performance in JSON parsing is s=
urprisingly hard, with dramatic performance differences between implementat=
ions. So you're forcing receiving software which wants to be conformant to =
use a hand-rolled parser which will probably have lousy performance and hav=
e other bugs which in fact may compromise security more than dupe-key trick=
s could.  -T

On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
> I think it's a nice clean minimal solution to say that producers MUST
> NOT generate dupes, end of story.  I don't think saying anything beyond
> that adds value. -T
Clean and minimal that may be, but it ignores the security issue. We don't =
want a malicious producer (who is so malicious they ignore a MUST) to creat=
e JOSE messages that a JOSE-compliant security layer accepts as "benign int=
erpretation #1" so it passes the message on to the JOSE-compliant backend a=
pp that acts on "nasty interpretation #2".

--
James Manger




_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose



--_000_4E1F6AAD24975D4BA5B1680429673943678A1CF7TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yes &#8211; but this is o=
nly a problem for the JSON Serialization &#8211; and then, only for fields =
that are not integrity protected.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If you don&#8217;t care e=
nough about the content of the header fields to integrity protect them, you=
 clearly don&#8217;t care whether an intermediary can tamper with them.&nbs=
p;
 Reordering duplicate member names is the only the tip of the iceberg of th=
e tampering that not integrity protecting header fields enables.&nbsp; The =
intermediary could delete them or completely rewrite them!<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Defending only against fi=
eld reordering is like putting your finger in a hole in the dike when the f=
loodgates next door are already wide open.&nbsp; Your field will
 definitely flood when the sea rises.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:56 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.o=
rg; draft-ietf-jose-json-web-signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">In a JSON-formatted JWS, the top-level JSON fields a=
re not covered by the signature (only the protected header). &nbsp;See the =
examples in my previous mail and in John's.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If an intermediary reorders the fields =
the signature validation will fail, so I&#8217;m not worried about
 that.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [mailto=
:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:48 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones &lt;<a href=3D"mailto=
:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I&#8217;ve come to believe that James&#=
8217; proposed language does a good job of making security-appropriate
 restrictions while allowing the use of existing parsers.&nbsp; It was:</sp=
an><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">A creator of a JOSE message MUST NOT put duplica=
te names in any JSON object in a JOSE header.&nbsp; To prevent attacks wher=
e a JOSE message is interpreted as different valid messages
 by different recipients, each recipient MUST either reject messages with d=
uplicate names or accept only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I might change &#8220;or accept only th=
e last name&#8221; to &#8220;or use a parser that always uses the lexically
 last name for any duplicate member names, per [ECMAScript]&#8221; for clar=
ity, but the intent is the same.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Would that work for people?</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">That's close. &nbsp;I don't think we can allow the &quot;lexically=
 last&quot; because elements in a JSON dictionary can be re-ordered. &nbsp;=
Suppose there a helpful intermediary that sorts a JSON dictionary
 in descending alphabetical order of values.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">When it gets: {&nbsp;&quot;payload&quot;: &quot;bad stuff&quot;,&n=
bsp;&nbsp;&quot;payload&quot;: &quot;good stuff&quot;, ... }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">It emits: {&nbsp;&quot;payload&quot;: &quot;good stuff&quot;,&nbsp=
;&nbsp;&quot;payload&quot;: &quot;bad&nbsp;stuff&quot;, ... }<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The only way to avoid the ambiguity is to reject objects with dupl=
icate keys.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
I realize that this renders most JSON parsers incompatible. &nbsp;Implement=
ors will need to add a secondary check. &nbsp;I feel your pain. &nbsp;But h=
opefully this pain will be temporary; the ambiguity will be fixed by the JS=
ON WG and ECMA, and parsers will be updated. &nbsp;Even
 in the short run, it doesn't seem like it would be that hard to mod existi=
ng parsers to have a &quot;strict&quot; flag.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">A creator of a JOSE message MUST NOT put duplicate names in any JS=
ON object in a JOSE header. &nbsp;To prevent attacks where a JOSE message i=
s interpreted as different valid messages
 by different recipients, each recipient MUST reject messages. &nbsp;Implem=
entations MUST NOT select the lexically last name, as required by [ECMAScri=
pt], since this could lead them to select the incorrect value if an interme=
diary re-orders the fields in a dictionary.
 &nbsp;If an implementation uses a JSON parser that does not reject objects=
 with duplicate fields, then it MUST verify that there are no dictionaries =
with duplicate fields in the JSON object.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bradley [mailto:<=
a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_blank">ve7jtb@ve7jtb.com</a>=
]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The problem is not wanting to leave a hole for malicious signers t=
o create JWT that may be misinterpreted by the receiver. &nbsp;Accidental i=
nterop problems from bad signers are not
 a big concern for me and are covered by MUST NOT emit dups.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Accepting malformed JSON as the envelope may lead to real security=
 issues.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This may be more of an issue for the JSON encoding than the compac=
t as there you need to be careful the body you process for the signature is=
 the body that the application uses.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">What happens if you receive.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<pre><span style=3D"font-size:12.0pt">{&quot;protected&quot;:&lt;integrity-=
protected shared header contents&gt;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
unprotected&quot;:&lt;non-integrity-protected shared header contents&gt;&qu=
ot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;original payload contents&gt;&quot;,</span><o:p></o=
:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;bad payload contents inserted by attacker&gt;&quot;=
</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
signatures&quot;:[</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header 1 contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature 1 contents&gt;&quot;},</spa=
n><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
...</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header N contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature N contents&gt;&quot;}],</sp=
an><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp; }</span><o:p=
></o:p></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">If the JOSE library validates on the first version of &quot;payloa=
d&quot; and the application using a different JSON parser only sees the sec=
ond &quot;payload&quot; we have a wrapping attack similar
 to xmldsig.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I can't off the top of my head think of what you could do in the c=
ompact serialization that would lead to a successful attack given that the =
signature is over the base64url encoded
 segments, that prevents attackers from modifying the JSON while maintainin=
g integrity.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">It is a real issue for the JSON serialization though.<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">John B.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"mailto:tbray@t=
extuality.com" target=3D"_blank">tbray@textuality.com</a>&gt; wrote:<o:p></=
o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The approach just seems wrong.&nbsp; If we require that conforming imple=
mentations MUST NOT emit dupes, then authors of receiving software can just=
 pick the best-performing parser with the
 nicest API, because they *all* perform correctly when there are no dupes.&=
nbsp; <br>
<br>
Who&#8217;s going to own the responsibility for making the authoritative fi=
nding that of the many JSON parsers in the Java ecosystem, these ones, but =
not those ones, are usable in JOSE applications?&nbsp; And suppose one that=
 has been previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?&n=
bsp; <o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The benefit of using JSON is that there is widely deployed software to h=
andle it.&nbsp; It is a known problem that sloppy spec drafting has allowed=
 various kinds of problems to occur when
 dupe keys are received. &#8220;Doctor, it hurts when I do this.&#8221; &#8=
220;So... don&#8217;t do that.&#8221;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Are we also going to specify the behavior of receiving software when the=
 JSON has a misplaced quotation mark?&nbsp; A missing trailing &#8220;}&#82=
21;?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;-T<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &lt;<a href=3D"m=
ailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Manger@tea=
m.telstra.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Most JSON libraries that=
 silently accept [sob] dupe keys at least consistently use the
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hence I suggest:</span><=
o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;A creator of a JOSE message MUST N=
OT put duplicate names in any JSON</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;To prevent attacks where a JOSE me=
ssage is interpreted as different</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">This isn&#8217;t &#8220;=
truly predictable&#8221; as a message with dupes might be accepted or rejec=
ted.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">--</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">James Manger</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray [mailto:<a hr=
ef=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</=
a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Well, you have a practical problem in that mo=
st implementers will want to use a standard JSON library, which is good pra=
ctice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don&#8217;t h=
ave a way to tell the client software what happened. So if you want truly p=
redictable behavior, you&#8217;re forcing the use of hand-constructed JSON =
parsers. And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you&#8217;re forcing receiving so=
ftware which wants to be conformant to use a hand-rolled parser which will =
probably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.&nbsp; -T</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 PM, Manger, Jam=
es H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blan=
k">James.H.Manger@team.telstra.com</a>&gt; wrote:</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&gt; I think it&#8217;s a nice clean minimal soluti=
on to say that producers MUST<br>
&gt; NOT generate dupes, end of story.&nbsp; I don&#8217;t think saying any=
thing beyond<br>
&gt; that adds value. -T</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Clean and minimal that may be, but it ignores=
 the security issue. We don't want a malicious producer (who is so maliciou=
s they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1CF7TK5EX14MBXC283r_--

From trac+jose@trac.tools.ietf.org  Thu Jun 27 16:05:14 2013
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E273021F9D9A for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6JdwnL1Bk5g for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:05:14 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 3748C21F9D0F for <jose@ietf.org>; Thu, 27 Jun 2013 16:05:13 -0700 (PDT)
Received: from localhost ([127.0.0.1]:34280 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1UsLFQ-0002zp-HM; Fri, 28 Jun 2013 01:05:05 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "jose issue tracker" <trac+jose@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx
X-Trac-Project: jose
Date: Thu, 27 Jun 2013 23:05:03 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/jose/trac/ticket/29
Message-ID: <049.2f6c2e28d610320d40f8f4307cd0bf6b@trac.tools.ietf.org>
X-Trac-Ticket-ID: 29
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@tools.ietf.org, rlb@ipv.sx, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20130627230514.3748C21F9D0F@ietfa.amsl.com>
Resent-Date: Thu, 27 Jun 2013 16:05:13 -0700 (PDT)
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose]  #29: Add an explicit "aad" field to JWE
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:05:15 -0000

#29: Add an explicit "aad" field to JWE

 Let's start from the design principle that the crypto operations in JWE
 should not be JWE-specific if they don't have to be.  Right now, the only
 way for an application to provide AAD to a JWE algorithm is in the
 protected header.  So it's impossible to use JOSE to implement any
 protocol that uses AAD to protect non-JSON data.  (Or if not impossible,
 it's costly, since it will end up getting double-base64 encoded.)

 Instead, JWE should have an explicit "aad" field that contains a
 base64-encoded octet string that is input as Additional Authenticated Data
 to the AEAD algorithm.  If there is a protected header present then the
 overall AAD is the concatenation of the header and the "aad" field.

 In the compact format, this field is always empty.

 OLD:
 """
 Let the Additional Authenticated Data encryption parameter be the octets
 of the ASCII representation of the Encoded JWE Header value.
 """
 NEW:
 """
 Let the Additional Authenticated Data encryption parameter be the octets
 of the ASCII representation of the Encoded JWE Header value.  If an "aad"
 parameter is present, set the Additional Authenticated Data to the
 concatenation of the Encoded JWE Header, a period ('.') character, and the
 ASCII representation of the "aad" field value.
 """

-- 
-------------------------+-------------------------------------------------
 Reporter:  rlb@ipv.sx   |      Owner:  draft-ietf-jose-json-web-
     Type:  defect       |  encryption@tools.ietf.org
 Priority:  major        |     Status:  new
Component:  json-web-    |  Milestone:
  encryption             |    Version:
 Severity:  -            |   Keywords:
-------------------------+-------------------------------------------------

Ticket URL: <http://tools.ietf.org/wg/jose/trac/ticket/29>
jose <http://tools.ietf.org/jose/>


From Michael.Jones@microsoft.com  Thu Jun 27 16:07:15 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE29C21F9D2F for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.338
X-Spam-Level: 
X-Spam-Status: No, score=-3.338 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXga1MnM+Gyt for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:07:10 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5078621F9DD3 for <jose@ietf.org>; Thu, 27 Jun 2013 16:07:10 -0700 (PDT)
Received: from BL2FFO11FD026.protection.gbl (10.173.161.204) by BL2FFO11HUB052.protection.gbl (10.173.161.128) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 22:52:03 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD026.mail.protection.outlook.com (10.173.161.105) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 22:52:03 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 22:51:47 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkIAAhRqAgAAMGPCAABbogIAABEiAgAAKPgCAAAP6AIAAlCSAgAAIEICAAAw40IAAaLoAgAABBaA=
Date: Thu, 27 Jun 2013 22:51:47 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com>
In-Reply-To: <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1B91TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(199002)(189002)(377424004)(43544003)(24454002)(19300405004)(81542001)(74662001)(71186001)(74366001)(77982001)(81342001)(74706001)(74502001)(69226001)(31966008)(55846006)(16406001)(76482001)(47446002)(51856001)(79102001)(53806001)(54356001)(76786001)(74876001)(56816003)(15202345003)(54316002)(59766001)(46102001)(56776001)(76796001)(77096001)(44976004)(47976001)(6806003)(4396001)(63696002)(512954002)(20776003)(50986001)(47736001)(33656001)(16236675002)(49866001)(80022001)(65816001)(66066001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB052; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:07:16 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1B91TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If an intermediary reorders the fields the signature validation will fail, =
so I'm not worried about that.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 27, 2013 3:48 PM
To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org; dra=
ft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text

On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
I've come to believe that James' proposed language does a good job of makin=
g security-appropriate restrictions while allowing the use of existing pars=
ers.  It was:

A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST ei=
ther reject messages with duplicate names or accept only the last name.

I might change "or accept only the last name" to "or use a parser that alwa=
ys uses the lexically last name for any duplicate member names, per [ECMASc=
ript]" for clarity, but the intent is the same.

Would that work for people?

                                                            -- Mike


That's close.  I don't think we can allow the "lexically last" because elem=
ents in a JSON dictionary can be re-ordered.  Suppose there a helpful inter=
mediary that sorts a JSON dictionary in descending alphabetical order of va=
lues.
When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }
It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }

The only way to avoid the ambiguity is to reject objects with duplicate key=
s.


I realize that this renders most JSON parsers incompatible.  Implementors w=
ill need to add a secondary check.  I feel your pain.  But hopefully this p=
ain will be temporary; the ambiguity will be fixed by the JSON WG and ECMA,=
 and parsers will be updated.  Even in the short run, it doesn't seem like =
it would be that hard to mod existing parsers to have a "strict" flag.

"""
A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST re=
ject messages.  Implementations MUST NOT select the lexically last name, as=
 required by [ECMAScript], since this could lead them to select the incorre=
ct value if an intermediary re-orders the fields in a dictionary.  If an im=
plementation uses a JSON parser that does not reject objects with duplicate=
 fields, then it MUST verify that there are no dictionaries with duplicate =
fields in the JSON object.
"""

--Richard






From: John Bradley [mailto:ve7jtb@ve7jtb.com<mailto:ve7jtb@ve7jtb.com>]
Sent: Thursday, June 27, 2013 8:49 AM
To: Tim Bray
Cc: Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf=
.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-=
jose-json-web-signature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text

The problem is not wanting to leave a hole for malicious signers to create =
JWT that may be misinterpreted by the receiver.  Accidental interop problem=
s from bad signers are not a big concern for me and are covered by MUST NOT=
 emit dups.

Accepting malformed JSON as the envelope may lead to real security issues.

This may be more of an issue for the JSON encoding than the compact as ther=
e you need to be careful the body you process for the signature is the body=
 that the application uses.

What happens if you receive.


{"protected":<integrity-protected shared header contents>",

      "unprotected":<non-integrity-protected shared header contents>",

      "payload":"<original payload contents>",

      "payload":"<bad payload contents inserted by attacker>"

      "signatures":[

       {"header":"<per-signature unprotected header 1 contents>",

        "signature":"<signature 1 contents>"},

       ...

       {"header":"<per-signature unprotected header N contents>",

        "signature":"<signature N contents>"}],

     }

If the JOSE library validates on the first version of "payload" and the app=
lication using a different JSON parser only sees the second "payload" we ha=
ve a wrapping attack similar to xmldsig.

I can't off the top of my head think of what you could do in the compact se=
rialization that would lead to a successful attack given that the signature=
 is over the base64url encoded segments, that prevents attackers from modif=
ying the JSON while maintaining integrity.

It is a real issue for the JSON serialization though.

John B.

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com<mailto:tbray@tex=
tuality.com>> wrote:

The approach just seems wrong.  If we require that conforming implementatio=
ns MUST NOT emit dupes, then authors of receiving software can just pick th=
e best-performing parser with the nicest API, because they *all* perform co=
rrectly when there are no dupes.

Who's going to own the responsibility for making the authoritative finding =
that of the many JSON parsers in the Java ecosystem, these ones, but not th=
ose ones, are usable in JOSE applications?  And suppose one that has been p=
reviously OK is quietly optimized on GitHub to run 30% faster and as a side=
-effect silently ignores dupes?
The benefit of using JSON is that there is widely deployed software to hand=
le it.  It is a known problem that sloppy spec drafting has allowed various=
 kinds of problems to occur when dupe keys are received. "Doctor, it hurts =
when I do this." "So... don't do that."
Are we also going to specify the behavior of receiving software when the JS=
ON has a misplaced quotation mark?  A missing trailing "}"?
 -T


On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
Most JSON libraries that silently accept [sob] dupe keys at least consisten=
tly use the last key. Allowing just that behaviour (or rejecting dupes), wh=
ile forbidding acceptance of a non-last dupe (eg first key), is safe and al=
lows most JSON libraries to be used. Since this accepts most libraries I th=
ink it is practical.

Hence I suggest:


>   A creator of a JOSE message MUST NOT put duplicate names in any JSON

> object in a JOSE header.

>   To prevent attacks where a JOSE message is interpreted as different

> valid messages by different recipients, each recipient MUST either

> reject messages with duplicate names or accept only the last name.

This isn't "truly predictable" as a message with dupes might be accepted or=
 rejected. The crucial point is that if a message is accepted it is predict=
able.

--
James Manger

From: Tim Bray [mailto:tbray@textuality.com<mailto:tbray@textuality.com>]
Sent: Thursday, 27 June 2013 4:16 PM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; draft-ietf=
-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-jose-json-web-sig=
nature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text


Well, you have a practical problem in that most implementers will want to u=
se a standard JSON library, which is good practice because it will be well-=
debugged, and most libraries [sob] silently take care of dupe keys and don'=
t have a way to tell the client software what happened. So if you want trul=
y predictable behavior, you're forcing the use of hand-constructed JSON par=
sers. And that sucks, because getting good performance in JSON parsing is s=
urprisingly hard, with dramatic performance differences between implementat=
ions. So you're forcing receiving software which wants to be conformant to =
use a hand-rolled parser which will probably have lousy performance and hav=
e other bugs which in fact may compromise security more than dupe-key trick=
s could.  -T

On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
> I think it's a nice clean minimal solution to say that producers MUST
> NOT generate dupes, end of story.  I don't think saying anything beyond
> that adds value. -T
Clean and minimal that may be, but it ignores the security issue. We don't =
want a malicious producer (who is so malicious they ignore a MUST) to creat=
e JOSE messages that a JOSE-compliant security layer accepts as "benign int=
erpretation #1" so it passes the message on to the JOSE-compliant backend a=
pp that acts on "nasty interpretation #2".

--
James Manger




_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B1680429673943678A1B91TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If an intermediary reorde=
rs the fields the signature validation will fail, so I&#8217;m not worried =
about that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:48 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.o=
rg; draft-ietf-jose-json-web-signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I&#8217;ve come to believe that James&#=
8217; proposed language does a good job of making security-appropriate
 restrictions while allowing the use of existing parsers.&nbsp; It was:</sp=
an><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">A creator of a JOSE message MUST NOT put duplica=
te names in any JSON object in a JOSE header.&nbsp; To prevent attacks wher=
e a JOSE message is interpreted as different valid messages
 by different recipients, each recipient MUST either reject messages with d=
uplicate names or accept only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I might change &#8220;or accept only th=
e last name&#8221; to &#8220;or use a parser that always uses the lexically
 last name for any duplicate member names, per [ECMAScript]&#8221; for clar=
ity, but the intent is the same.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Would that work for people?</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">That's close. &nbsp;I don't think we can allow the &=
quot;lexically last&quot; because elements in a JSON dictionary can be re-o=
rdered. &nbsp;Suppose there a helpful intermediary that sorts a JSON dictio=
nary in descending alphabetical order of values.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">When it gets: {&nbsp;&quot;payload&quot;: &quot;bad =
stuff&quot;,&nbsp;&nbsp;&quot;payload&quot;: &quot;good stuff&quot;, ... }<=
o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">It emits: {&nbsp;&quot;payload&quot;: &quot;good stu=
ff&quot;,&nbsp;&nbsp;&quot;payload&quot;: &quot;bad&nbsp;stuff&quot;, ... }=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The only way to avoid the ambiguity is to reject obj=
ects with duplicate keys.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
I realize that this renders most JSON parsers incompatible. &nbsp;Implement=
ors will need to add a secondary check. &nbsp;I feel your pain. &nbsp;But h=
opefully this pain will be temporary; the ambiguity will be fixed by the JS=
ON WG and ECMA, and parsers will be updated. &nbsp;Even
 in the short run, it doesn't seem like it would be that hard to mod existi=
ng parsers to have a &quot;strict&quot; flag.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">A creator of a JOSE message MUST NOT put duplicate n=
ames in any JSON object in a JOSE header. &nbsp;To prevent attacks where a =
JOSE message is interpreted as different valid messages by different recipi=
ents, each recipient MUST reject messages.
 &nbsp;Implementations MUST NOT select the lexically last name, as required=
 by [ECMAScript], since this could lead them to select the incorrect value =
if an intermediary re-orders the fields in a dictionary. &nbsp;If an implem=
entation uses a JSON parser that does not
 reject objects with duplicate fields, then it MUST verify that there are n=
o dictionaries with duplicate fields in the JSON object.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bradley [mailto:<=
a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_blank">ve7jtb@ve7jtb.com</a>=
]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The problem is not wanting to leave a hole for malicious signers t=
o create JWT that may be misinterpreted by the receiver. &nbsp;Accidental i=
nterop problems from bad signers are not
 a big concern for me and are covered by MUST NOT emit dups.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Accepting malformed JSON as the envelope may lead to real security=
 issues.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This may be more of an issue for the JSON encoding than the compac=
t as there you need to be careful the body you process for the signature is=
 the body that the application uses.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">What happens if you receive.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<pre><span style=3D"font-size:12.0pt">{&quot;protected&quot;:&lt;integrity-=
protected shared header contents&gt;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
unprotected&quot;:&lt;non-integrity-protected shared header contents&gt;&qu=
ot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;original payload contents&gt;&quot;,</span><o:p></o=
:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;bad payload contents inserted by attacker&gt;&quot;=
</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
signatures&quot;:[</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header 1 contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature 1 contents&gt;&quot;},</spa=
n><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
...</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header N contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature N contents&gt;&quot;}],</sp=
an><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp; }</span><o:p=
></o:p></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">If the JOSE library validates on the first version of &quot;payloa=
d&quot; and the application using a different JSON parser only sees the sec=
ond &quot;payload&quot; we have a wrapping attack similar
 to xmldsig.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I can't off the top of my head think of what you could do in the c=
ompact serialization that would lead to a successful attack given that the =
signature is over the base64url encoded
 segments, that prevents attackers from modifying the JSON while maintainin=
g integrity.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">It is a real issue for the JSON serialization though.<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">John B.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"mailto:tbray@t=
extuality.com" target=3D"_blank">tbray@textuality.com</a>&gt; wrote:<o:p></=
o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The approach just seems wrong.&nbsp; If we require that conforming imple=
mentations MUST NOT emit dupes, then authors of receiving software can just=
 pick the best-performing parser with the
 nicest API, because they *all* perform correctly when there are no dupes.&=
nbsp; <br>
<br>
Who&#8217;s going to own the responsibility for making the authoritative fi=
nding that of the many JSON parsers in the Java ecosystem, these ones, but =
not those ones, are usable in JOSE applications?&nbsp; And suppose one that=
 has been previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?&n=
bsp; <o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The benefit of using JSON is that there is widely deployed software to h=
andle it.&nbsp; It is a known problem that sloppy spec drafting has allowed=
 various kinds of problems to occur when
 dupe keys are received. &#8220;Doctor, it hurts when I do this.&#8221; &#8=
220;So... don&#8217;t do that.&#8221;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Are we also going to specify the behavior of receiving software when the=
 JSON has a misplaced quotation mark?&nbsp; A missing trailing &#8220;}&#82=
21;?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;-T<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &lt;<a href=3D"m=
ailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Manger@tea=
m.telstra.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Most JSON libraries that=
 silently accept [sob] dupe keys at least consistently use the
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hence I suggest:</span><=
o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;A creator of a JOSE message MUST N=
OT put duplicate names in any JSON</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;To prevent attacks where a JOSE me=
ssage is interpreted as different</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">This isn&#8217;t &#8220;=
truly predictable&#8221; as a message with dupes might be accepted or rejec=
ted.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">--</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">James Manger</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray [mailto:<a hr=
ef=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</=
a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Well, you have a practical problem in that mo=
st implementers will want to use a standard JSON library, which is good pra=
ctice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don&#8217;t h=
ave a way to tell the client software what happened. So if you want truly p=
redictable behavior, you&#8217;re forcing the use of hand-constructed JSON =
parsers. And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you&#8217;re forcing receiving so=
ftware which wants to be conformant to use a hand-rolled parser which will =
probably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.&nbsp; -T</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 PM, Manger, Jam=
es H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blan=
k">James.H.Manger@team.telstra.com</a>&gt; wrote:</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&gt; I think it&#8217;s a nice clean minimal soluti=
on to say that producers MUST<br>
&gt; NOT generate dupes, end of story.&nbsp; I don&#8217;t think saying any=
thing beyond<br>
&gt; that adds value. -T</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Clean and minimal that may be, but it ignores=
 the security issue. We don't want a malicious producer (who is so maliciou=
s they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1B91TK5EX14MBXC283r_--

From rlb@ipv.sx  Thu Jun 27 16:10:40 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A857711E810B for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.226
X-Spam-Level: 
X-Spam-Status: No, score=-3.226 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8vI-WWn3OkN for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:10:35 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7E58211E80DF for <jose@ietf.org>; Thu, 27 Jun 2013 16:10:35 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so1572130oag.18 for <jose@ietf.org>; Thu, 27 Jun 2013 16:10:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=/e7b5Ps4cHlnKcwdaLPfVcOq+nhbz6t4BTHcDL2vSok=; b=EyUlNTAPG8h/qhWxhtIfQw/z7A1uWNHjnw8js2QH6q5Z9CmQlGlAZzpOWaWdZobGQi NwiA0ITiLFfhWQX4RUIZeA1VJv9b7wf1T/cHgX16G69kGy5YK+i8Ri+iKRtpHYe4OqrG z9x/AbjVjV/grH9dzzRDaZlu1jZn94LefAV7fa/EQ9Y7LhAMwTYTyhERGAin7NhoIPV4 N00BEh1FWSiOF2dx0THdpUT7SznSsKW13qd2OW4ngfH9FKDrx+o5adR6GvCJeemFEKXZ wwJvqbgQZk5QtqCFW2NecTq3YgiCAyuM7iMQRrTU4EWoF6gqWfY/dqZAnliONX4fx0lq O9ww==
MIME-Version: 1.0
X-Received: by 10.60.97.74 with SMTP id dy10mr3941798oeb.27.1372374635017; Thu, 27 Jun 2013 16:10:35 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Thu, 27 Jun 2013 16:10:34 -0700 (PDT)
X-Originating-IP: [192.1.51.93]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1CF7@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgS3Hq2EGH9=+UH9wssfnsB9=Ns43jbTjhzqX9cMrhwtvw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1CF7@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Thu, 27 Jun 2013 19:10:34 -0400
Message-ID: <CAL02cgTYqyUpARxYZYupNMxQvE_WH4JgsQXGX1G_kkHdNxUpTQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e0115e9fa9e8c8804e02ade52
X-Gm-Message-State: ALoCoQmlfWIrSSdZ13z5yA5dZwFkWMAj3WuQXSl5OM5JDSsJ6RmiCfSCpCPsHu3cJrpbi4XBAZ4+
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:10:40 -0000

--089e0115e9fa9e8c8804e02ade52
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The goal here is not to defend against attackers.  It's to prevent benign
intermediaries from causing breakage.

The point here is that a JOSE implementation needs to get the same
understanding of a JOSE object regardless of which of the multiple
equivalent forms of the JSON form it gets.  This is about having a
well-specified protocol, for which transformations that produce equivalent
JSON objects should produce equivalent JOSE objects.  That is, the
following process should be lossless:
JOSE --stringify--> JSON --reorder-fields--> JSON --parse--> JOSE

If that's not the case, then we've built a broken protocol.

--Richard








On Thu, Jun 27, 2013 at 7:00 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Yes =96 but this is only a problem for the JSON Serialization =96 and th=
en,
> only for fields that are not integrity protected.****
>
> ** **
>
> If you don=92t care enough about the content of the header fields to
> integrity protect them, you clearly don=92t care whether an intermediary =
can
> tamper with them.  Reordering duplicate member names is the only the tip =
of
> the iceberg of the tampering that not integrity protecting header fields
> enables.  The intermediary could delete them or completely rewrite them!*=
*
> **
>
> ** **
>
> Defending only against field reordering is like putting your finger in a
> hole in the dike when the floodgates next door are already wide open.  Yo=
ur
> field will definitely flood when the sea rises.****
>
> ** **
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 27, 2013 3:56 PM
>
> *To:* Mike Jones
> *Cc:* John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
> ** **
>
> In a JSON-formatted JWS, the top-level JSON fields are not covered by the
> signature (only the protected header).  See the examples in my previous
> mail and in John's.****
>
> --Richard****
>
> ** **
>
> On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:****
>
> If an intermediary reorders the fields the signature validation will fail=
,
> so I=92m not worried about that.****
>
>  ****
>
>                                                                 -- Mike**=
*
> *
>
>  ****
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 27, 2013 3:48 PM
> *To:* Mike Jones
> *Cc:* John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ****
>
> On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com=
>
> wrote:****
>
>  I=92ve come to believe that James=92 proposed language does a good job o=
f
> making security-appropriate restrictions while allowing the use of existi=
ng
> parsers.  It was:****
>
>  ****
>
> A creator of a JOSE message MUST NOT put duplicate names in any JSON
> object in a JOSE header.  To prevent attacks where a JOSE message is
> interpreted as different valid messages by different recipients, each
> recipient MUST either reject messages with duplicate names or accept only
> the last name.****
>
>  ****
>
> I might change =93or accept only the last name=94 to =93or use a parser t=
hat
> always uses the lexically last name for any duplicate member names, per
> [ECMAScript]=94 for clarity, but the intent is the same.****
>
>  ****
>
> Would that work for people?****
>
>  ****
>
>                                                             -- Mike****
>
>   ****
>
>  ****
>
> That's close.  I don't think we can allow the "lexically last" because
> elements in a JSON dictionary can be re-ordered.  Suppose there a helpful
> intermediary that sorts a JSON dictionary in descending alphabetical orde=
r
> of values. ****
>
> When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }**=
*
> *
>
> It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }****
>
>  ****
>
> The only way to avoid the ambiguity is to reject objects with duplicate
> keys.****
>
>  ****
>
>
> I realize that this renders most JSON parsers incompatible.  Implementors
> will need to add a secondary check.  I feel your pain.  But hopefully thi=
s
> pain will be temporary; the ambiguity will be fixed by the JSON WG and
> ECMA, and parsers will be updated.  Even in the short run, it doesn't see=
m
> like it would be that hard to mod existing parsers to have a "strict" fla=
g.
> ****
>
>  ****
>
> """****
>
> A creator of a JOSE message MUST NOT put duplicate names in any JSON
> object in a JOSE header.  To prevent attacks where a JOSE message is
> interpreted as different valid messages by different recipients, each
> recipient MUST reject messages.  Implementations MUST NOT select the
> lexically last name, as required by [ECMAScript], since this could lead
> them to select the incorrect value if an intermediary re-orders the field=
s
> in a dictionary.  If an implementation uses a JSON parser that does not
> reject objects with duplicate fields, then it MUST verify that there are =
no
> dictionaries with duplicate fields in the JSON object.****
>
> """****
>
>  ****
>
> --Richard ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>   ****
>
> *From:* John Bradley [mailto:ve7jtb@ve7jtb.com]
> *Sent:* Thursday, June 27, 2013 8:49 AM
> *To:* Tim Bray
> *Cc:* Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ****
>
> The problem is not wanting to leave a hole for malicious signers to creat=
e
> JWT that may be misinterpreted by the receiver.  Accidental interop
> problems from bad signers are not a big concern for me and are covered by
> MUST NOT emit dups.****
>
>  ****
>
> Accepting malformed JSON as the envelope may lead to real security issues=
.
> ****
>
>  ****
>
> This may be more of an issue for the JSON encoding than the compact as
> there you need to be careful the body you process for the signature is th=
e
> body that the application uses.****
>
>  ****
>
> What happens if you receive.****
>
>  ****
>
> {"protected":<integrity-protected shared header contents>",****
>
>       "unprotected":<non-integrity-protected shared header contents>",***=
*
>
>       "payload":"<original payload contents>",****
>
>       "payload":"<bad payload contents inserted by attacker>"****
>
>       "signatures":[****
>
>        {"header":"<per-signature unprotected header 1 contents>",****
>
>         "signature":"<signature 1 contents>"},****
>
>        ...****
>
>        {"header":"<per-signature unprotected header N contents>",****
>
>         "signature":"<signature N contents>"}],****
>
>      }****
>
>   ****
>
> If the JOSE library validates on the first version of "payload" and the
> application using a different JSON parser only sees the second "payload" =
we
> have a wrapping attack similar to xmldsig.****
>
>  ****
>
> I can't off the top of my head think of what you could do in the compact
> serialization that would lead to a successful attack given that the
> signature is over the base64url encoded segments, that prevents attackers
> from modifying the JSON while maintaining integrity.****
>
>  ****
>
> It is a real issue for the JSON serialization though.****
>
>  ****
>
> John B.****
>
>  ****
>
> On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com> wrote:****
>
>  ****
>
> The approach just seems wrong.  If we require that conforming
> implementations MUST NOT emit dupes, then authors of receiving software c=
an
> just pick the best-performing parser with the nicest API, because they
> *all* perform correctly when there are no dupes.
>
> Who=92s going to own the responsibility for making the authoritative find=
ing
> that of the many JSON parsers in the Java ecosystem, these ones, but not
> those ones, are usable in JOSE applications?  And suppose one that has be=
en
> previously OK is quietly optimized on GitHub to run 30% faster and as a
> side-effect silently ignores dupes?  ****
>
> The benefit of using JSON is that there is widely deployed software to
> handle it.  It is a known problem that sloppy spec drafting has allowed
> various kinds of problems to occur when dupe keys are received. =93Doctor=
, it
> hurts when I do this.=94 =93So... don=92t do that.=94****
>
> Are we also going to specify the behavior of receiving software when the
> JSON has a misplaced quotation mark?  A missing trailing =93}=94?****
>
>  -T****
>
>  ****
>
>  ****
>
> On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> Most JSON libraries that silently accept [sob] dupe keys at least
> consistently use the last key. Allowing just that behaviour (or rejecting
> dupes), while forbidding acceptance of a non-last dupe (eg first key), is
> safe and allows most JSON libraries to be used. Since this accepts most
> libraries I think it is practical.****
>
>  ****
>
> Hence I suggest:****
>
>  ****
>
> >   A creator of a JOSE message MUST NOT put duplicate names in any JSON*=
*
> **
>
> > object in a JOSE header.****
>
> >   To prevent attacks where a JOSE message is interpreted as different**=
*
> *
>
> > valid messages by different recipients, each recipient MUST either****
>
> > reject messages with duplicate names or accept only the last name.****
>
>  ****
>
> This isn=92t =93truly predictable=94 as a message with dupes might be acc=
epted
> or rejected. The crucial point is that if a message is accepted it is
> predictable.****
>
>  ****
>
> --****
>
> James Manger****
>
>  ****
>
> *From:* Tim Bray [mailto:tbray@textuality.com]
> *Sent:* Thursday, 27 June 2013 4:16 PM
> *To:* Manger, James H
> *Cc:* Mike Jones; Jim Schaad; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org****
>
>
> *Subject:* Re: [jose] #27: member names MUST be unique needs additional
> text****
>
>  ****
>
>  ****
>
> Well, you have a practical problem in that most implementers will want to
> use a standard JSON library, which is good practice because it will be
> well-debugged, and most libraries [sob] silently take care of dupe keys a=
nd
> don=92t have a way to tell the client software what happened. So if you w=
ant
> truly predictable behavior, you=92re forcing the use of hand-constructed =
JSON
> parsers. And that sucks, because getting good performance in JSON parsing
> is surprisingly hard, with dramatic performance differences between
> implementations. So you=92re forcing receiving software which wants to be
> conformant to use a hand-rolled parser which will probably have lousy
> performance and have other bugs which in fact may compromise security mor=
e
> than dupe-key tricks could.  -T****
>
>  ****
>
> On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:****
>
> > I think it=92s a nice clean minimal solution to say that producers MUST
> > NOT generate dupes, end of story.  I don=92t think saying anything beyo=
nd
> > that adds value. -T****
>
> Clean and minimal that may be, but it ignores the security issue. We don'=
t
> want a malicious producer (who is so malicious they ignore a MUST) to
> create JOSE messages that a JOSE-compliant security layer accepts as
> "benign interpretation #1" so it passes the message on to the
> JOSE-compliant backend app that acts on "nasty interpretation #2".
>
> --
> James Manger****
>
>  ****
>
>  ****
>
>  ****
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
>   ****
>
> ** **
>

--089e0115e9fa9e8c8804e02ade52
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The goal here is not to defend against attackers. =A0It&#3=
9;s to prevent benign intermediaries from causing breakage.<div><br></div><=
div>The point here is that a JOSE implementation needs to get the same unde=
rstanding of a JOSE object regardless of which of the multiple equivalent f=
orms of the JSON form it gets. =A0This is about having a well-specified pro=
tocol, for which transformations that produce equivalent JSON objects shoul=
d produce equivalent JOSE objects. =A0That is, the following process should=
 be lossless:</div>
<div>JOSE --stringify--&gt; JSON --reorder-fields--&gt; JSON --parse--&gt; =
JOSE</div><div><br></div><div>If that&#39;s not the case, then we&#39;ve bu=
ilt a broken protocol.</div><div><br></div><div>--Richard</div><div><br>
</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br>=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Thu, Jun 27, 2013 at 7:00 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D=
"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@micros=
oft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Yes =96 but this is only =
a problem for the JSON Serialization =96 and then, only for fields that are=
 not integrity protected.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If you don=92t care enoug=
h about the content of the header fields to integrity protect them, you cle=
arly don=92t care whether an intermediary can tamper with them.=A0
 Reordering duplicate member names is the only the tip of the iceberg of th=
e tampering that not integrity protecting header fields enables.=A0 The int=
ermediary could delete them or completely rewrite them!<u></u><u></u></span=
></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Defending only against fi=
eld reordering is like putting your finger in a hole in the dike when the f=
loodgates next door are already wide open.=A0 Your field will
 definitely flood when the sea rises.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:56 PM</span></p><div><div class=3D"h=
5"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-jose-json-web-signature@tools.ietf.org" target=3D"_blank">draf=
t-ietf-jose-json-web-signature@tools.ietf.org</a><br>

<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">In a JSON-formatted JWS, the top-level JSON fields a=
re not covered by the signature (only the protected header). =A0See the exa=
mples in my previous mail and in John&#39;s.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If an intermediary reorde=
rs the fields the signature validation will fail, so I=92m not worried abou=
t
 that.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:48 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><u></u><u></u><=
/p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones &lt;<a =
href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones=
@microsoft.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I=92ve come to believe th=
at James=92 proposed language does a good job of making security-appropriat=
e
 restrictions while allowing the use of existing parsers.=A0 It was:</span>=
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">A creator of a JOSE message MUST NOT put duplica=
te names in any JSON object in a JOSE header.=A0 To prevent attacks where a=
 JOSE message is interpreted as different valid messages
 by different recipients, each recipient MUST either reject messages with d=
uplicate names or accept only the last name.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I might change =93or acce=
pt only the last name=94 to =93or use a parser that always uses the lexical=
ly
 last name for any duplicate member names, per [ECMAScript]=94 for clarity,=
 but the intent is the same.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Would that work for peopl=
e?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 -- Mike</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That&#39;s close. =A0I don&#39;t think we can allow =
the &quot;lexically last&quot; because elements in a JSON dictionary can be=
 re-ordered. =A0Suppose there a helpful intermediary that sorts a JSON dict=
ionary
 in descending alphabetical order of values.=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">When it gets: {=A0&quot;payload&quot;: &quot;bad stu=
ff&quot;,=A0=A0&quot;payload&quot;: &quot;good stuff&quot;, ... }<u></u><u>=
</u></p>
</div>
<div>
<p class=3D"MsoNormal">It emits: {=A0&quot;payload&quot;: &quot;good stuff&=
quot;,=A0=A0&quot;payload&quot;: &quot;bad=A0stuff&quot;, ... }<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The only way to avoid the ambiguity is to reject obj=
ects with duplicate keys.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
I realize that this renders most JSON parsers incompatible. =A0Implementors=
 will need to add a secondary check. =A0I feel your pain. =A0But hopefully =
this pain will be temporary; the ambiguity will be fixed by the JSON WG and=
 ECMA, and parsers will be updated. =A0Even
 in the short run, it doesn&#39;t seem like it would be that hard to mod ex=
isting parsers to have a &quot;strict&quot; flag.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">A creator of a JOSE message MUST NOT put duplicate n=
ames in any JSON object in a JOSE header. =A0To prevent attacks where a JOS=
E message is interpreted as different valid messages
 by different recipients, each recipient MUST reject messages. =A0Implement=
ations MUST NOT select the lexically last name, as required by [ECMAScript]=
, since this could lead them to select the incorrect value if an intermedia=
ry re-orders the fields in a dictionary.
 =A0If an implementation uses a JSON parser that does not reject objects wi=
th duplicate fields, then it MUST verify that there are no dictionaries wit=
h duplicate fields in the JSON object.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;&quot;&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span><u></u><u></u><=
/p>
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bra=
dley [mailto:<a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_blank">ve7jtb@=
ve7jtb.com</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><u></u><u></u><=
/p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
<p class=3D"MsoNormal">The problem is not wanting to leave a hole for malic=
ious signers to create JWT that may be misinterpreted by the receiver. =A0A=
ccidental interop problems from bad signers are not
 a big concern for me and are covered by MUST NOT emit dups.<u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Accepting malformed JSON as the envelope may lead to=
 real security issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This may be more of an issue for the JSON encoding t=
han the compact as there you need to be careful the body you process for th=
e signature is the body that the application uses.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">What happens if you receive.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<pre><span style=3D"font-size:12.0pt">{&quot;protected&quot;:&lt;integrity-=
protected shared header contents&gt;&quot;,</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;unprotected&quo=
t;:&lt;non-integrity-protected shared header contents&gt;&quot;,</span><u><=
/u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&=
quot;&lt;original payload contents&gt;&quot;,</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;payload&quot;:&=
quot;&lt;bad payload contents inserted by attacker&gt;&quot;</span><u></u><=
u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0 &quot;signatures&quot=
;:[</span><u></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot=
;:&quot;&lt;per-signature unprotected header 1 contents&gt;&quot;,</span><u=
></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature=
&quot;:&quot;&lt;signature 1 contents&gt;&quot;},</span><u></u><u></u></pre=
>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 ...</span><u></u><=
u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0 {&quot;header&quot=
;:&quot;&lt;per-signature unprotected header N contents&gt;&quot;,</span><u=
></u><u></u></pre>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0=A0=A0=A0 &quot;signature=
&quot;:&quot;&lt;signature N contents&gt;&quot;}],</span><u></u><u></u></pr=
e>
<pre><span style=3D"font-size:12.0pt">=A0=A0=A0=A0 }</span><u></u><u></u></=
pre>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If the JOSE library validates on the first version o=
f &quot;payload&quot; and the application using a different JSON parser onl=
y sees the second &quot;payload&quot; we have a wrapping attack similar
 to xmldsig.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I can&#39;t off the top of my head think of what you=
 could do in the compact serialization that would lead to a successful atta=
ck given that the signature is over the base64url encoded
 segments, that prevents attackers from modifying the JSON while maintainin=
g integrity.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It is a real issue for the JSON serialization though=
.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">John B.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"=
mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</a>&gt;=
 wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The approach just see=
ms wrong.=A0 If we require that conforming implementations MUST NOT emit du=
pes, then authors of receiving software can just pick the best-performing p=
arser with the
 nicest API, because they *all* perform correctly when there are no dupes.=
=A0 <br>
<br>
Who=92s going to own the responsibility for making the authoritative findin=
g that of the many JSON parsers in the Java ecosystem, these ones, but not =
those ones, are usable in JOSE applications?=A0 And suppose one that has be=
en previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?=
=A0 <u></u><u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The benefit of using =
JSON is that there is widely deployed software to handle it.=A0 It is a kno=
wn problem that sloppy spec drafting has allowed various kinds of problems =
to occur when
 dupe keys are received. =93Doctor, it hurts when I do this.=94 =93So... do=
n=92t do that.=94<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Are we also going to =
specify the behavior of receiving software when the JSON has a misplaced qu=
otation mark?=A0 A missing trailing =93}=94?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0-T<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &l=
t;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">Jame=
s.H.Manger@team.telstra.com</a>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Most JSON =
libraries that silently accept [sob] dupe keys at least consistently use th=
e
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><u></u><u></u></p>

<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hence I su=
ggest:</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; =A0=A0A creator of a JOSE message MUST NOT put=
 duplicate names in any JSON</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.</span><u></u><u></u><=
/p>
<p><span lang=3D"EN-AU">&gt; =A0=A0To prevent attacks where a JOSE message =
is interpreted as different</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either</span><u></u><u></u></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">This isn=
=92t =93truly predictable=94 as a message with dupes might be accepted or r=
ejected.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">--</span><=
u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">James Mang=
er</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0</span>=
<u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray=
 [mailto:<a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@te=
xtuality.com</a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><u></u><u></u><=
/p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">Well, you have a practical prob=
lem in that most implementers will want to use a standard JSON library, whi=
ch is good practice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don=92t have =
a way to tell the client software what happened. So if you want truly predi=
ctable behavior, you=92re forcing the use of hand-constructed JSON parsers.=
 And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you=92re forcing receiving softwa=
re which wants to be conformant to use a hand-rolled parser which will prob=
ably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.=A0 -T</span><u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-AU">=
=A0</span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 P=
M, Manger, James H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" t=
arget=3D"_blank">James.H.Manger@team.telstra.com</a>&gt; wrote:</span><u></=
u><u></u></p>

<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-AU">=
&gt; I think it=92s a nice clean minimal solution to say that producers MUS=
T<br>
&gt; NOT generate dupes, end of story.=A0 I don=92t think saying anything b=
eyond<br>
&gt; that adds value. -T</span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">Clean and minimal that may be, =
but it ignores the security issue. We don&#39;t want a malicious producer (=
who is so malicious they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger</span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-AU">=A0</span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--089e0115e9fa9e8c8804e02ade52--

From Michael.Jones@microsoft.com  Thu Jun 27 16:16:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEAAF21F9B16 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.382
X-Spam-Level: 
X-Spam-Status: No, score=-4.382 tagged_above=-999 required=5 tests=[AWL=1.217,  BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McjyIsKAUC-3 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:16:20 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 8A35D21F9B15 for <jose@ietf.org>; Thu, 27 Jun 2013 16:16:20 -0700 (PDT)
Received: from BY2FFO11FD027.protection.gbl (10.1.15.202) by BY2FFO11HUB010.protection.gbl (10.1.14.80) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 23:16:19 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD027.mail.protection.outlook.com (10.1.15.216) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 23:16:19 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 23:16:15 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] #26: Allow for signature payload to not be base64 encoded
Thread-Index: AQHOcgNOsVoAPXc/s02k5Wh9HChUEZlIUkQAgACNH4CAAObIgIAAAUowgAAHOACAAFdeAIAACIkw
Date: Thu, 27 Jun 2013 23:16:14 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com>
In-Reply-To: <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1F0ATK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(13464003)(189002)(199002)(30844003)(50084003)(374574003)(24454002)(377454003)(365934002)(51704005)(47976001)(50986001)(16236675002)(47736001)(49866001)(4396001)(16406001)(6806003)(33656001)(66066001)(80022001)(20776003)(63696002)(65816001)(512954002)(81542001)(81342001)(69226001)(46102001)(76786001)(79102001)(74366001)(19300405004)(44976004)(76796001)(56816003)(47446002)(74706001)(15202345003)(55846006)(56776001)(77096001)(51856001)(77982001)(71186001)(74876001)(59766001)(54356001)(76482001)(53806001)(74502001)(54316002)(31966008)(74662001)(380704003); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB010; H:TK5EX14MLTC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: n-sakimura <n-sakimura@nri.co.jp>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:16:26 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1F0ATK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Even if we chose to support an unencoded payload representation as an optio=
n for the JSON Serialization (which I'm not advocating), having this be the=
 default would be the wrong thing for two reasons:

1.  It won't work for the Compact Serialization, since it doesn't ensure th=
at the representation is URL-safe.  The default should work for both serial=
izations.

2.  It assumes a special case (a payload that can be represented as a trans=
port-invariant JSON string), which will often not work.  The default should=
 be the general case, which always works.

As for your suggestion to not use the base64url encoded payload in the sign=
ature computation, this seems to me like an attempt to reopen http://trac.t=
ools.ietf.org/wg/jose/trac/ticket/23 (Make crypto independent of binary enc=
oding (base64)) by another means, despite it already being resolved as "Won=
't Fix".  I don't believe that constantly trying to revisit closed issues i=
s a productive activity, nor respectful of the working group's time, so I t=
herefore request that you let that one go.

                                                                Sincerely,
                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 27, 2013 3:24 PM
To: Jim Schaad
Cc: Mike Jones; n-sakimura; jose@ietf.org; draft-ietf-jose-json-web-signatu=
re@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encod=
ed

I think there are two separable issues here, both of which Mike and I proba=
bly have divergent opinions on :)
1. Syntax: Should it be possible for the "payload" field JWS to be a JSON s=
tring (instead of base64) when the payload is simply a UTF-8 string?
2. Crypto: Must the JWS Signing Input be base64url encoded.

The current answers to these questions are:
1. It is not possible.  Payload is always base64url encoded.
2. It is always base64url encoded.

The answers should be:
1. The payload should not be base64url encoded unless it cannot be represen=
ted as a JSON string.
2. The JWS Signing Input should not be base64url encoded unless there is a =
JWS Protected Header

Neither of these are complicated changes:
1. Add a "b64" header parameter that indicates that the payload is base64ur=
l-encoded binary, as opposed to a UTF-8 string.  Specify that this paramete=
r is on by default in compact-formatted JWS objects.
2. Modify the signing/verification instructions to switch based on the pres=
ence of a JWS Protected Header: "If the JWS Protected Header is absent or e=
mpty, then the JWS Signing Input is simply the JWS Payload (not encoded).  =
If the JWS Protected Header has a non-empty value, then the the JWS Signing=
 Input is the concatenation of the Encoded JWS Header, a period ('.') chara=
cter, and the Encoded JWS Payload"

There are two reasons for these, both of which are important to make sure t=
hat this spec is applicable to a broad variety of use cases:
1. Compactness.  As Jim notes, quoted strings are shorter than base64url-en=
coded strings
2. Crypto-compatibility: Avoiding base64-encoding means that there's nothin=
g JWS-specific about the signature value.  So for example, you could transl=
ate a JWS with no protected attributes to a CMS SignedData object with no p=
rotected attributes.

This email brought to you by the number 2 and the letters J, W, and S :)

--Richard

[1] Note that the default value for this header must be false, or else you =
lose the compactness advantage!
[2] You could also do this as a "Content-Encoding" equivalent, "cenc": "b64=
".  That would give you "base64 agility", as some folks have asked for, sin=
ce you could have "b64" and "b64u" values.
[3] You could also do this like CMS, and have the JWS Signing Input in the =
latter case be "the concatenation of the Encoded JWS Header, a period ('.')=
 character, and the Encoded JWS Payload Hash".  Where the Encoded JWS Paylo=
ad Hash is the base64url-encoded version of the hash you would otherwise be=
 signing.  This seems simpler to code, since you just digest the body, then=
 if there's a protected header, you digest again.  But it also breaks with =
existing code.




On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad <ietf@augustcellars.com<mailto:=
ietf@augustcellars.com>> wrote:
No, my motivation is to allow for a smaller version of the payload string. =
 In some cases quoting it will generate a smaller string than doing the bas=
e64 conversion on the string.



> -----Original Message-----
> From: Mike Jones [mailto:Michael.Jones@microsoft.com<mailto:Michael.Jones=
@microsoft.com>]
> Sent: Thursday, June 27, 2013 9:49 AM
> To: Jim Schaad; 'n-sakimura'
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-j=
ose-json-web-signature@tools.ietf.org>; jose@ietf.org<mailto:jose@ietf.org>
> Subject: RE: [jose] #26: Allow for signature payload to not be base64 enc=
oded
>
> Jim, you wrote "If I am not transporting the base64url encoded content,
> because it is not in the "payload" field, then why should I need to base6=
4
> encode it just to validate the signature.  This is the alto case."
>
> So am I correct then, in thinking that your motivation for #26 is actuall=
y #25 -
> Detached content for the ALTO use case?  As John and Nat had written, thi=
s
> could be handled by the specs as they are today by signing a hash of the
> detached content and including a compact JWS representing that signature =
as
> an x-alto-signature header.  That doesn't require changing the signature
> calculation.
>
>                               -- Mike
>
> -----Original Message-----
> From: Jim Schaad [mailto:ietf@augustcellars.com<mailto:ietf@augustcellars=
.com>]
> Sent: Thursday, June 27, 2013 9:41 AM
> To: 'n-sakimura'
> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-j=
ose-json-web-signature@tools.ietf.org>; Mike Jones;
> jose@ietf.org<mailto:jose@ietf.org>
> Subject: RE: [jose] #26: Allow for signature payload to not be base64 enc=
oded
>
> Nat,
>
> The only thing that can be signed or encrypted is an octet string. (A sli=
ght over
> generalization. GOST for example hashes an integer, tree hashes can do
> strange things but a sufficiently true statement for our purposes.)
>
> A that being said - yes case 1 would be something you can do.  Case #2 wo=
uld
> not be something that you can do because it is not an octet string.
>
> If you are looking at JavaScript, in order to hash something as an octet =
string it
> can be one of three things.  A UInt8Array, an Int8Array and, due to
> convention, a string where the top byte of all of the code points in the =
string is
> zero.
>
> We currently don't have an efficient way to encode the Uint8Array case,
> although that might not be true if we are looking at new ECMA specificati=
ons
> which apparently are adding more defined types and serialization methods =
for
> those types.
>
> > -----Original Message-----
> > From: n-sakimura [mailto:n-sakimura@nri.co.jp<mailto:n-sakimura@nri.co.=
jp>]
> > Sent: Wednesday, June 26, 2013 7:55 PM
> > To: Jim Schaad
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf=
-jose-json-web-signature@tools.ietf.org>;
> > michael.jones@microsoft.com<mailto:michael.jones@microsoft.com>; jose@i=
etf.org<mailto:jose@ietf.org>
> > Subject: Re: [jose] #26: Allow for signature payload to not be base64
> > encoded
> >
> > Let me understand the problem.
> >
> > Are you suggesting that we should be able to do something like:
> >
> > Case 1:
> >
> >       {"protected":<integrity-protected shared header contents>",
> >        "unprotected":<non-integrity-protected shared header contents>",
> >        "payload":"this is a multi\nline text payload of which a line
> > can be very very very long and wrapped during transmission. "
> >        "signatures":[
> >         {"header":"<per-signature unprotected header 1 contents>",
> >          "signature":"<signature 1 contents>"},
> >         ...
> >         {"header":"<per-signature unprotected header N contents>",
> >          "signature":"<signature N contents>"}],
> >       }
> >
> > or even
> >
> > Case 2:
> >
> >       {"protected":<integrity-protected shared header contents>",
> >        "unprotected":<non-integrity-protected shared header contents>",
> >        "payload":{
> >     "this":"is a json",
> >     "payload":"which is not base64url encoded"
> >        }
> >        "signatures":[
> >         {"header":"<per-signature unprotected header 1 contents>",
> >          "signature":"<signature 1 contents>"},
> >         ...
> >         {"header":"<per-signature unprotected header N contents>",
> >          "signature":"<signature N contents>"}],
> >       }
> >
> > Then, I am worried about allowing them because in general we would not
> > know what would a transmission mechanism and user agents (including
> > text
> > editors) would do to them, like Mike mentioned. I do not think we
> > should assume the property of the transmission mechanism in JOSE level.
> > Assuming that would cause brittleness in the implementations.
> >
> > For detached signature, I do not understand why you would want non-
> > base64url encoded payload. The application should define how to hash
> > the octet stream that it wants to calculate signature over it, and we
> > can just include the base64url encoded hash in the "payload".
> > Why would you like to do other encoding for the hash?
>
> If I am not transporting the base64url encoded content, because it is not=
 in
> the "payload" field, then why should I need to base64 encode it just to
> validate the signature.  This is the alto case.
>
> Jim
>
> >
> > --
> > Nat Sakimura (n-sakimura@nri.co.jp<mailto:n-sakimura@nri.co.jp>)
> > Nomura Research Institute
> >
> > PLEASE READ:
> > The information contained in this e-mail is confidential and intended
> > for the named recipient(s) only.
> > If you are not an intended recipient of this e-mail, you are hereby
> > notified that any review, dissemination, distribution or duplication
> > of this message is strictly prohibited. If you have received this
> > message in error, please notify the sender immediately and delete your
> copy from your system.


_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose


--_000_4E1F6AAD24975D4BA5B1680429673943678A1F0ATK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Even if we chose to suppo=
rt an unencoded payload representation as an option for the JSON Serializat=
ion (which I&#8217;m not advocating), having this be the default
 would be the wrong thing for two reasons:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">1.&nbsp; It won&#8217;t w=
ork for the Compact Serialization, since it doesn&#8217;t ensure that the r=
epresentation is URL-safe.&nbsp; The default should work for both serializa=
tions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">2.&nbsp; It assumes a spe=
cial case (a payload that can be represented as a transport-invariant JSON =
string), which will often not work.&nbsp; The default should be the
 general case, which always works.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As for your suggestion to=
 not use the base64url encoded payload in the signature computation, this s=
eems to me like an attempt to reopen
<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/23">http://trac.t=
ools.ietf.org/wg/jose/trac/ticket/23</a> (Make crypto independent of binary=
 encoding (base64)) by another means, despite it already being resolved as =
&#8220;Won&#8217;t Fix&#8221;.&nbsp; I don&#8217;t believe that
 constantly trying to revisit closed issues is a productive activity, nor r=
espectful of the working group&#8217;s time, so I therefore request that yo=
u let that one go.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sincerely,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:24 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> Mike Jones; n-sakimura; jose@ietf.org; draft-ietf-jose-json-web-=
signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #26: Allow for signature payload to not be base6=
4 encoded<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">I think there are two separable issues here, both of=
 which Mike and I probably have divergent opinions on :)<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">1. Syntax: Should it be possible for the &quot;paylo=
ad&quot; field JWS to be a JSON string (instead of base64) when the payload=
 is simply a UTF-8 string?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2. Crypto: Must the JWS Signing Input be base64url e=
ncoded.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The current answers to these questions are:<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal">1. It is not possible. &nbsp;Payload is always base6=
4url encoded.<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">2. It is always base64url encoded.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The answers should be:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1. The payload should not be base64url encoded unles=
s it cannot be represented as a JSON string.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2. The JWS Signing Input should not be base64url enc=
oded unless there is a JWS Protected Header<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Neither of these are complicated changes:<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal">1. Add a &quot;b64&quot; header parameter that indic=
ates that the payload is base64url-encoded binary, as opposed to a UTF-8 st=
ring. &nbsp;Specify that this parameter is on by default in compact-formatt=
ed JWS objects.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2. Modify the signing/verification instructions to s=
witch based on the presence of a JWS Protected Header: &quot;If the JWS Pro=
tected Header is absent or empty, then the JWS Signing Input is simply the =
JWS Payload (not encoded). &nbsp;If the JWS
 Protected Header has a non-empty value, then the the JWS Signing Input is =
the concatenation of the Encoded JWS Header, a period ('.') character, and =
the Encoded JWS Payload&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are two reasons for these, both of which are i=
mportant to make sure that this spec is applicable to a broad variety of us=
e cases:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1. Compactness. &nbsp;As Jim notes, quoted strings a=
re shorter than base64url-encoded strings<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">2. Crypto-compatibility: Avoiding base64-encoding me=
ans that there's nothing JWS-specific about the signature value. &nbsp;So f=
or example, you could translate a JWS with no protected attributes to a CMS=
 SignedData object with no protected attributes.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">This email brought to you by the number 2 and the le=
tters J, W, and S :)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[1] Note that the default value for this header must=
 be false, or else you lose the compactness advantage!<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[2] You could also do this as a &quot;Content-Encodi=
ng&quot; equivalent, &quot;cenc&quot;: &quot;b64&quot;. &nbsp;That would gi=
ve you &quot;base64 agility&quot;, as some folks have asked for, since you =
could have &quot;b64&quot; and &quot;b64u&quot; values. &nbsp;<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal">[3] You could also do this like CMS, and have the JW=
S Signing Input in the latter case be &quot;the concatenation of the Encode=
d JWS Header, a period ('.') character, and the Encoded JWS Payload Hash&qu=
ot;. &nbsp;Where the Encoded JWS Payload Hash is
 the base64url-encoded version of the hash you would otherwise be signing. =
&nbsp;This seems simpler to code, since you just digest the body, then if t=
here's a protected header, you digest again. &nbsp;But it also breaks with =
existing code. &nbsp;&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">No, my motivation is to allow for a smaller version =
of the payload string. &nbsp;In some cases quoting it will generate a small=
er string than doing the base64 conversion on the string.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Mike Jones [mailto:<a href=3D"mailto:Michael.Jones@microsoft.com=
">Michael.Jones@microsoft.com</a>]<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&gt; Sent: Thursday, June 27, 2013 9:49 AM<br>
&gt; To: Jim Schaad; 'n-sakimura'<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Jim, you wrote &quot;If I am not transporting the base64url encoded co=
ntent,<br>
&gt; because it is not in the &quot;payload&quot; field, then why should I =
need to base64<br>
&gt; encode it just to validate the signature. &nbsp;This is the alto case.=
&quot;<br>
&gt;<br>
&gt; So am I correct then, in thinking that your motivation for #26 is actu=
ally #25 -<br>
&gt; Detached content for the ALTO use case? &nbsp;As John and Nat had writ=
ten, this<br>
&gt; could be handled by the specs as they are today by signing a hash of t=
he<br>
&gt; detached content and including a compact JWS representing that signatu=
re as<br>
&gt; an x-alto-signature header. &nbsp;That doesn't require changing the si=
gnature<br>
&gt; calculation.<br>
&gt;<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -- Mike<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Jim Schaad [mailto:<a href=3D"mailto:ietf@augustcellars.com">iet=
f@augustcellars.com</a>]<br>
&gt; Sent: Thursday, June 27, 2013 9:41 AM<br>
&gt; To: 'n-sakimura'<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g">draft-ietf-jose-json-web-signature@tools.ietf.org</a>; Mike Jones;<br>
&gt; <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Nat,<br>
&gt;<br>
&gt; The only thing that can be signed or encrypted is an octet string. (A =
slight over<br>
&gt; generalization. GOST for example hashes an integer, tree hashes can do=
<br>
&gt; strange things but a sufficiently true statement for our purposes.)<br=
>
&gt;<br>
&gt; A that being said - yes case 1 would be something you can do. &nbsp;Ca=
se #2 would<br>
&gt; not be something that you can do because it is not an octet string.<br=
>
&gt;<br>
&gt; If you are looking at JavaScript, in order to hash something as an oct=
et string it<br>
&gt; can be one of three things. &nbsp;A UInt8Array, an Int8Array and, due =
to<br>
&gt; convention, a string where the top byte of all of the code points in t=
he string is<br>
&gt; zero.<br>
&gt;<br>
&gt; We currently don't have an efficient way to encode the Uint8Array case=
,<br>
&gt; although that might not be true if we are looking at new ECMA specific=
ations<br>
&gt; which apparently are adding more defined types and serialization metho=
ds for<br>
&gt; those types.<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: n-sakimura [mailto:<a href=3D"mailto:n-sakimura@nri.co.jp">=
n-sakimura@nri.co.jp</a>]<br>
&gt; &gt; Sent: Wednesday, June 26, 2013 7:55 PM<br>
&gt; &gt; To: Jim Schaad<br>
&gt; &gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ie=
tf.org">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;<br>
&gt; &gt; <a href=3D"mailto:michael.jones@microsoft.com">michael.jones@micr=
osoft.com</a>;
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
&gt; &gt; Subject: Re: [jose] #26: Allow for signature payload to not be ba=
se64<br>
&gt; &gt; encoded<br>
&gt; &gt;<br>
&gt; &gt; Let me understand the problem.<br>
&gt; &gt;<br>
&gt; &gt; Are you suggesting that we should be able to do something like:<b=
r>
&gt; &gt;<br>
&gt; &gt; Case 1:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; {&quot;protected&quot;:&lt;integrity-protect=
ed shared header contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;unprotected&quot;:&lt;non-integr=
ity-protected shared header contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;payload&quot;:&quot;this is a mu=
lti\nline text payload of which a line<br>
&gt; &gt; can be very very very long and wrapped during transmission. &quot=
;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signatures&quot;:[<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {&quot;header&quot;:&quot;&lt;per-sig=
nature unprotected header 1 contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signature&quot;:&quot;&lt=
;signature 1 contents&gt;&quot;},<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; ...<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {&quot;header&quot;:&quot;&lt;per-sig=
nature unprotected header N contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signature&quot;:&quot;&lt=
;signature N contents&gt;&quot;}],<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; }<br>
&gt; &gt;<br>
&gt; &gt; or even<br>
&gt; &gt;<br>
&gt; &gt; Case 2:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; {&quot;protected&quot;:&lt;integrity-protect=
ed shared header contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;unprotected&quot;:&lt;non-integr=
ity-protected shared header contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;payload&quot;:{<br>
&gt; &gt; &nbsp; &nbsp; &quot;this&quot;:&quot;is a json&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &quot;payload&quot;:&quot;which is not base64url en=
coded&quot;<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;}<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signatures&quot;:[<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {&quot;header&quot;:&quot;&lt;per-sig=
nature unprotected header 1 contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signature&quot;:&quot;&lt=
;signature 1 contents&gt;&quot;},<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; ...<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {&quot;header&quot;:&quot;&lt;per-sig=
nature unprotected header N contents&gt;&quot;,<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;signature&quot;:&quot;&lt=
;signature N contents&gt;&quot;}],<br>
&gt; &gt; &nbsp; &nbsp; &nbsp; }<br>
&gt; &gt;<br>
&gt; &gt; Then, I am worried about allowing them because in general we woul=
d not<br>
&gt; &gt; know what would a transmission mechanism and user agents (includi=
ng<br>
&gt; &gt; text<br>
&gt; &gt; editors) would do to them, like Mike mentioned. I do not think we=
<br>
&gt; &gt; should assume the property of the transmission mechanism in JOSE =
level.<br>
&gt; &gt; Assuming that would cause brittleness in the implementations.<br>
&gt; &gt;<br>
&gt; &gt; For detached signature, I do not understand why you would want no=
n-<br>
&gt; &gt; base64url encoded payload. The application should define how to h=
ash<br>
&gt; &gt; the octet stream that it wants to calculate signature over it, an=
d we<br>
&gt; &gt; can just include the base64url encoded hash in the &quot;payload&=
quot;.<br>
&gt; &gt; Why would you like to do other encoding for the hash?<br>
&gt;<br>
&gt; If I am not transporting the base64url encoded content, because it is =
not in<br>
&gt; the &quot;payload&quot; field, then why should I need to base64 encode=
 it just to<br>
&gt; validate the signature. &nbsp;This is the alto case.<br>
&gt;<br>
&gt; Jim<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Nat Sakimura (<a href=3D"mailto:n-sakimura@nri.co.jp">n-sakimura@=
nri.co.jp</a>)<br>
&gt; &gt; Nomura Research Institute<br>
&gt; &gt;<br>
&gt; &gt; PLEASE READ:<br>
&gt; &gt; The information contained in this e-mail is confidential and inte=
nded<br>
&gt; &gt; for the named recipient(s) only.<br>
&gt; &gt; If you are not an intended recipient of this e-mail, you are here=
by<br>
&gt; &gt; notified that any review, dissemination, distribution or duplicat=
ion<br>
&gt; &gt; of this message is strictly prohibited. If you have received this=
<br>
&gt; &gt; message in error, please notify the sender immediately and delete=
 your<br>
&gt; copy from your system.<br>
<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1F0ATK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Thu Jun 27 16:19:25 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8E3321F9BAF for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.555
X-Spam-Level: 
X-Spam-Status: No, score=-3.555 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WmDWdyWJI5ZJ for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:19:18 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id C911621F9982 for <jose@ietf.org>; Thu, 27 Jun 2013 16:19:17 -0700 (PDT)
Received: from BN1AFFO11FD018.protection.gbl (10.58.52.201) by BN1AFFO11HUB049.protection.gbl (10.58.52.160) with Microsoft SMTP Server (TLS) id 15.0.717.3; Thu, 27 Jun 2013 23:19:14 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD018.mail.protection.outlook.com (10.58.52.78) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Thu, 27 Jun 2013 23:19:14 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Thu, 27 Jun 2013 23:18:35 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] #27: member names MUST be unique needs additional text
Thread-Index: AQHOcW13mt9O8ZWU/EKeLtDRf+ylY5lHKNsAgAEqlQCAAA6YkIAAhRqAgAAMGPCAABbogIAABEiAgAAKPgCAAAP6AIAAlCSAgAAIEICAAAw40IAAaLoAgAABBaCAAAFPAIAAACRAgAAD8gCAAAH24A==
Date: Thu, 27 Jun 2013 23:18:34 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A1F90@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.bb7bbe0b618ec6b74904f48bdb9bb312@trac.tools.ietf.org> <076.a597050ecb4fb25084cec65f7174dc7e@trac.tools.ietf.org> <033b01ce729b$26ff5c90$74fe15b0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789B4CC@TK5EX14MBXC283.redmond.corp.microsoft.com> <03b401ce72e5$002c65f0$008531d0$@augustcellars.com> <4E1F6AAD24975D4BA5B16804296739436789D4EA@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAHBU6ivNow2xhDvRj7gG2gmHQ+C-ejEHCQubK=LwUtrXxdW6MA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BE45737@WSMSG3153V.srv.dir.telstra.com> <CAHBU6itHZ4NvGLyRqfDFaC9gkWD1_6dxhY=uVmwpyL+5Ay+j2w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1151BEDDD3C@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iss5JbmHAue_2-AFDYSMVjAEnMLeLcESei3xTGTWP8_jQ@mail.gmail.com> <16F5858A-B77F-498B-9296-A42F84D5244D@ve7jtb.com> <4E1F6AAD24975D4BA5B1680429673943678A009C@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgT4y4_zMC67ZKD5b=8JQHLVzuZSDP9ThiBF2Y_HYzMi5A@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1B91@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgS3Hq2EGH9=+UH9wssfnsB9=Ns43jbTjhzqX9cMrhwtvw@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1CF7@TK5EX14MBXC283.redmond.corp.microsoft.com> <CAL02cgTYqyUpARxYZYupNMxQvE_WH4JgsQXGX1G_kkHdNxUpTQ@mail.gmail.com>
In-Reply-To: <CAL02cgTYqyUpARxYZYupNMxQvE_WH4JgsQXGX1G_kkHdNxUpTQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A1F90TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(377454003)(24454002)(43544003)(377424004)(16236675002)(65816001)(50986001)(47976001)(6806003)(4396001)(49866001)(33656001)(512954002)(80022001)(47736001)(66066001)(63696002)(20776003)(16406001)(81542001)(31966008)(77096001)(71186001)(81342001)(69226001)(74502001)(74706001)(47446002)(54316002)(74662001)(19300405004)(15202345003)(56776001)(51856001)(76482001)(76786001)(53806001)(54356001)(79102001)(74366001)(76796001)(59766001)(77982001)(56816003)(46102001)(55846006)(74876001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB049; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 08902E536D
Cc: Jim Schaad <ietf@augustcellars.com>, Tim Bray <tbray@textuality.com>, "jose@ietf.org" <jose@ietf.org>, John Bradley <ve7jtb@ve7jtb.com>, "Manger, James H" <James.H.Manger@team.telstra.com>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:19:25 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A1F90TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It's not lossless only for illegal inputs - those with duplicate members.  =
If your goal isn't to defend against attackers, then it's safe to assume th=
at the producer produced a legal input - hence no problem in practice.

From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: Thursday, June 27, 2013 4:11 PM
To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org; dra=
ft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #27: member names MUST be unique needs additional text

The goal here is not to defend against attackers.  It's to prevent benign i=
ntermediaries from causing breakage.

The point here is that a JOSE implementation needs to get the same understa=
nding of a JOSE object regardless of which of the multiple equivalent forms=
 of the JSON form it gets.  This is about having a well-specified protocol,=
 for which transformations that produce equivalent JSON objects should prod=
uce equivalent JOSE objects.  That is, the following process should be loss=
less:
JOSE --stringify--> JSON --reorder-fields--> JSON --parse--> JOSE

If that's not the case, then we've built a broken protocol.

--Richard







On Thu, Jun 27, 2013 at 7:00 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
Yes - but this is only a problem for the JSON Serialization - and then, onl=
y for fields that are not integrity protected.

If you don't care enough about the content of the header fields to integrit=
y protect them, you clearly don't care whether an intermediary can tamper w=
ith them.  Reordering duplicate member names is the only the tip of the ice=
berg of the tampering that not integrity protecting header fields enables. =
 The intermediary could delete them or completely rewrite them!

Defending only against field reordering is like putting your finger in a ho=
le in the dike when the floodgates next door are already wide open.  Your f=
ield will definitely flood when the sea rises.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, June 27, 2013 3:56 PM

To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org<mail=
to:jose@ietf.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto=
:draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #27: member names MUST be unique needs additional text

In a JSON-formatted JWS, the top-level JSON fields are not covered by the s=
ignature (only the protected header).  See the examples in my previous mail=
 and in John's.
--Richard

On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
If an intermediary reorders the fields the signature validation will fail, =
so I'm not worried about that.

                                                                -- Mike

From: Richard Barnes [mailto:rlb@ipv.sx<mailto:rlb@ipv.sx>]
Sent: Thursday, June 27, 2013 3:48 PM
To: Mike Jones
Cc: John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.org<mail=
to:jose@ietf.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto=
:draft-ietf-jose-json-web-signature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text

On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones <Michael.Jones@microsoft.com<m=
ailto:Michael.Jones@microsoft.com>> wrote:
I've come to believe that James' proposed language does a good job of makin=
g security-appropriate restrictions while allowing the use of existing pars=
ers.  It was:

A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST ei=
ther reject messages with duplicate names or accept only the last name.

I might change "or accept only the last name" to "or use a parser that alwa=
ys uses the lexically last name for any duplicate member names, per [ECMASc=
ript]" for clarity, but the intent is the same.

Would that work for people?

                                                            -- Mike


That's close.  I don't think we can allow the "lexically last" because elem=
ents in a JSON dictionary can be re-ordered.  Suppose there a helpful inter=
mediary that sorts a JSON dictionary in descending alphabetical order of va=
lues.
When it gets: { "payload": "bad stuff",  "payload": "good stuff", ... }
It emits: { "payload": "good stuff",  "payload": "bad stuff", ... }

The only way to avoid the ambiguity is to reject objects with duplicate key=
s.


I realize that this renders most JSON parsers incompatible.  Implementors w=
ill need to add a secondary check.  I feel your pain.  But hopefully this p=
ain will be temporary; the ambiguity will be fixed by the JSON WG and ECMA,=
 and parsers will be updated.  Even in the short run, it doesn't seem like =
it would be that hard to mod existing parsers to have a "strict" flag.

"""
A creator of a JOSE message MUST NOT put duplicate names in any JSON object=
 in a JOSE header.  To prevent attacks where a JOSE message is interpreted =
as different valid messages by different recipients, each recipient MUST re=
ject messages.  Implementations MUST NOT select the lexically last name, as=
 required by [ECMAScript], since this could lead them to select the incorre=
ct value if an intermediary re-orders the fields in a dictionary.  If an im=
plementation uses a JSON parser that does not reject objects with duplicate=
 fields, then it MUST verify that there are no dictionaries with duplicate =
fields in the JSON object.
"""

--Richard






From: John Bradley [mailto:ve7jtb@ve7jtb.com<mailto:ve7jtb@ve7jtb.com>]
Sent: Thursday, June 27, 2013 8:49 AM
To: Tim Bray
Cc: Manger, James H; Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf=
.org>; draft-ietf-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-=
jose-json-web-signature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text

The problem is not wanting to leave a hole for malicious signers to create =
JWT that may be misinterpreted by the receiver.  Accidental interop problem=
s from bad signers are not a big concern for me and are covered by MUST NOT=
 emit dups.

Accepting malformed JSON as the envelope may lead to real security issues.

This may be more of an issue for the JSON encoding than the compact as ther=
e you need to be careful the body you process for the signature is the body=
 that the application uses.

What happens if you receive.


{"protected":<integrity-protected shared header contents>",

      "unprotected":<non-integrity-protected shared header contents>",

      "payload":"<original payload contents>",

      "payload":"<bad payload contents inserted by attacker>"

      "signatures":[

       {"header":"<per-signature unprotected header 1 contents>",

        "signature":"<signature 1 contents>"},

       ...

       {"header":"<per-signature unprotected header N contents>",

        "signature":"<signature N contents>"}],

     }

If the JOSE library validates on the first version of "payload" and the app=
lication using a different JSON parser only sees the second "payload" we ha=
ve a wrapping attack similar to xmldsig.

I can't off the top of my head think of what you could do in the compact se=
rialization that would lead to a successful attack given that the signature=
 is over the base64url encoded segments, that prevents attackers from modif=
ying the JSON while maintaining integrity.

It is a real issue for the JSON serialization though.

John B.

On 2013-06-27, at 11:20 AM, Tim Bray <tbray@textuality.com<mailto:tbray@tex=
tuality.com>> wrote:

The approach just seems wrong.  If we require that conforming implementatio=
ns MUST NOT emit dupes, then authors of receiving software can just pick th=
e best-performing parser with the nicest API, because they *all* perform co=
rrectly when there are no dupes.

Who's going to own the responsibility for making the authoritative finding =
that of the many JSON parsers in the Java ecosystem, these ones, but not th=
ose ones, are usable in JOSE applications?  And suppose one that has been p=
reviously OK is quietly optimized on GitHub to run 30% faster and as a side=
-effect silently ignores dupes?
The benefit of using JSON is that there is widely deployed software to hand=
le it.  It is a known problem that sloppy spec drafting has allowed various=
 kinds of problems to occur when dupe keys are received. "Doctor, it hurts =
when I do this." "So... don't do that."
Are we also going to specify the behavior of receiving software when the JS=
ON has a misplaced quotation mark?  A missing trailing "}"?
 -T


On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
Most JSON libraries that silently accept [sob] dupe keys at least consisten=
tly use the last key. Allowing just that behaviour (or rejecting dupes), wh=
ile forbidding acceptance of a non-last dupe (eg first key), is safe and al=
lows most JSON libraries to be used. Since this accepts most libraries I th=
ink it is practical.

Hence I suggest:


>   A creator of a JOSE message MUST NOT put duplicate names in any JSON

> object in a JOSE header.

>   To prevent attacks where a JOSE message is interpreted as different

> valid messages by different recipients, each recipient MUST either

> reject messages with duplicate names or accept only the last name.

This isn't "truly predictable" as a message with dupes might be accepted or=
 rejected. The crucial point is that if a message is accepted it is predict=
able.

--
James Manger

From: Tim Bray [mailto:tbray@textuality.com<mailto:tbray@textuality.com>]
Sent: Thursday, 27 June 2013 4:16 PM
To: Manger, James H
Cc: Mike Jones; Jim Schaad; jose@ietf.org<mailto:jose@ietf.org>; draft-ietf=
-jose-json-web-signature@tools.ietf.org<mailto:draft-ietf-jose-json-web-sig=
nature@tools.ietf.org>

Subject: Re: [jose] #27: member names MUST be unique needs additional text


Well, you have a practical problem in that most implementers will want to u=
se a standard JSON library, which is good practice because it will be well-=
debugged, and most libraries [sob] silently take care of dupe keys and don'=
t have a way to tell the client software what happened. So if you want trul=
y predictable behavior, you're forcing the use of hand-constructed JSON par=
sers. And that sucks, because getting good performance in JSON parsing is s=
urprisingly hard, with dramatic performance differences between implementat=
ions. So you're forcing receiving software which wants to be conformant to =
use a hand-rolled parser which will probably have lousy performance and hav=
e other bugs which in fact may compromise security more than dupe-key trick=
s could.  -T

On Wed, Jun 26, 2013 at 10:39 PM, Manger, James H <James.H.Manger@team.tels=
tra.com<mailto:James.H.Manger@team.telstra.com>> wrote:
> I think it's a nice clean minimal solution to say that producers MUST
> NOT generate dupes, end of story.  I don't think saying anything beyond
> that adds value. -T
Clean and minimal that may be, but it ignores the security issue. We don't =
want a malicious producer (who is so malicious they ignore a MUST) to creat=
e JOSE messages that a JOSE-compliant security layer accepts as "benign int=
erpretation #1" so it passes the message on to the JOSE-compliant backend a=
pp that acts on "nasty interpretation #2".

--
James Manger




_______________________________________________
jose mailing list
jose@ietf.org<mailto:jose@ietf.org>
https://www.ietf.org/mailman/listinfo/jose




--_000_4E1F6AAD24975D4BA5B1680429673943678A1F90TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It&#8217;s not lossless o=
nly for illegal inputs &#8211; those with duplicate members.&nbsp; If your =
goal isn&#8217;t to defend against attackers, then it&#8217;s safe to assum=
e that the
 producer produced a legal input &#8211; hence no problem in practice.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:rlb@ipv.sx]
<br>
<b>Sent:</b> Thursday, June 27, 2013 4:11 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; jose@ietf.o=
rg; draft-ietf-jose-json-web-signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">The goal here is not to defend against attackers. &n=
bsp;It's to prevent benign intermediaries from causing breakage.<o:p></o:p>=
</p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The point here is that a JOSE implementation needs t=
o get the same understanding of a JOSE object regardless of which of the mu=
ltiple equivalent forms of the JSON form it gets. &nbsp;This is about havin=
g a well-specified protocol, for which
 transformations that produce equivalent JSON objects should produce equiva=
lent JOSE objects. &nbsp;That is, the following process should be lossless:=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">JOSE --stringify--&gt; JSON --reorder-fields--&gt; J=
SON --parse--&gt; JOSE<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If that's not the case, then we've built a broken pr=
otocol.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 7:00 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Yes &#8211; but this is only a problem =
for the JSON Serialization &#8211; and then, only for fields that are
 not integrity protected.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If you don&#8217;t care enough about th=
e content of the header fields to integrity protect them, you clearly
 don&#8217;t care whether an intermediary can tamper with them.&nbsp; Reord=
ering duplicate member names is the only the tip of the iceberg of the tamp=
ering that not integrity protecting header fields enables.&nbsp; The interm=
ediary could delete them or completely rewrite them!</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Defending only against field reordering=
 is like putting your finger in a hole in the dike when the
 floodgates next door are already wide open.&nbsp; Your field will definite=
ly flood when the sea rises.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [mailto=
:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:56 PM</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">In a JSON-formatted JWS, the top-level JSON fields are not covered=
 by the signature (only the protected header). &nbsp;See the examples in my=
 previous mail and in John's.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, Jun 27, 2013 at 6:51 PM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If an intermediary reorders the fields =
the signature validation will fail, so I&#8217;m not worried about
 that.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard Barnes [mailto=
:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:48 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> John Bradley; Tim Bray; Jim Schaad; Manger, James H; <a href=3D"=
mailto:jose@ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Thu, Jun 27, 2013 at 12:42 PM, Mike Jones &lt;<a href=3D"mailto=
:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I&#8217;ve come to believe that James&#=
8217; proposed language does a good job of making security-appropriate
 restrictions while allowing the use of existing parsers.&nbsp; It was:</sp=
an><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:.5in">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D">A creator of a JOSE message MUST NOT put duplica=
te names in any JSON object in a JOSE header.&nbsp; To prevent attacks wher=
e a JOSE message is interpreted as different valid messages
 by different recipients, each recipient MUST either reject messages with d=
uplicate names or accept only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">I might change &#8220;or accept only th=
e last name&#8221; to &#8220;or use a parser that always uses the lexically
 last name for any duplicate member names, per [ECMAScript]&#8221; for clar=
ity, but the intent is the same.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Would that work for people?</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">That's close. &nbsp;I don't think we can allow the &quot;lexically=
 last&quot; because elements in a JSON dictionary can be re-ordered. &nbsp;=
Suppose there a helpful intermediary that sorts a JSON dictionary
 in descending alphabetical order of values.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">When it gets: {&nbsp;&quot;payload&quot;: &quot;bad stuff&quot;,&n=
bsp;&nbsp;&quot;payload&quot;: &quot;good stuff&quot;, ... }<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">It emits: {&nbsp;&quot;payload&quot;: &quot;good stuff&quot;,&nbsp=
;&nbsp;&quot;payload&quot;: &quot;bad&nbsp;stuff&quot;, ... }<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The only way to avoid the ambiguity is to reject objects with dupl=
icate keys.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
I realize that this renders most JSON parsers incompatible. &nbsp;Implement=
ors will need to add a secondary check. &nbsp;I feel your pain. &nbsp;But h=
opefully this pain will be temporary; the ambiguity will be fixed by the JS=
ON WG and ECMA, and parsers will be updated. &nbsp;Even
 in the short run, it doesn't seem like it would be that hard to mod existi=
ng parsers to have a &quot;strict&quot; flag.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">A creator of a JOSE message MUST NOT put duplicate names in any JS=
ON object in a JOSE header. &nbsp;To prevent attacks where a JOSE message i=
s interpreted as different valid messages
 by different recipients, each recipient MUST reject messages. &nbsp;Implem=
entations MUST NOT select the lexically last name, as required by [ECMAScri=
pt], since this could lead them to select the incorrect value if an interme=
diary re-orders the fields in a dictionary.
 &nbsp;If an implementation uses a JSON parser that does not reject objects=
 with duplicate fields, then it MUST verify that there are no dictionaries =
with duplicate fields in the JSON object.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;&quot;&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">--Richard&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> John Bradley [mailto:<=
a href=3D"mailto:ve7jtb@ve7jtb.com" target=3D"_blank">ve7jtb@ve7jtb.com</a>=
]
<br>
<b>Sent:</b> Thursday, June 27, 2013 8:49 AM<br>
<b>To:</b> Tim Bray<br>
<b>Cc:</b> Manger, James H; Mike Jones; Jim Schaad; <a href=3D"mailto:jose@=
ietf.org" target=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The problem is not wanting to leave a hole for malicious signers t=
o create JWT that may be misinterpreted by the receiver. &nbsp;Accidental i=
nterop problems from bad signers are not
 a big concern for me and are covered by MUST NOT emit dups.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Accepting malformed JSON as the envelope may lead to real security=
 issues.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This may be more of an issue for the JSON encoding than the compac=
t as there you need to be careful the body you process for the signature is=
 the body that the application uses.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">What happens if you receive.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<pre><span style=3D"font-size:12.0pt">{&quot;protected&quot;:&lt;integrity-=
protected shared header contents&gt;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
unprotected&quot;:&lt;non-integrity-protected shared header contents&gt;&qu=
ot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;original payload contents&gt;&quot;,</span><o:p></o=
:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;:&quot;&lt;bad payload contents inserted by attacker&gt;&quot;=
</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;=
signatures&quot;:[</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header 1 contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature 1 contents&gt;&quot;},</spa=
n><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
...</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
{&quot;header&quot;:&quot;&lt;per-signature unprotected header N contents&g=
t;&quot;,</span><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; &quot;signature&quot;:&quot;&lt;signature N contents&gt;&quot;}],</sp=
an><o:p></o:p></pre>
<pre><span style=3D"font-size:12.0pt">&nbsp;&nbsp;&nbsp;&nbsp; }</span><o:p=
></o:p></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">If the JOSE library validates on the first version of &quot;payloa=
d&quot; and the application using a different JSON parser only sees the sec=
ond &quot;payload&quot; we have a wrapping attack similar
 to xmldsig.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I can't off the top of my head think of what you could do in the c=
ompact serialization that would lead to a successful attack given that the =
signature is over the base64url encoded
 segments, that prevents attackers from modifying the JSON while maintainin=
g integrity.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">It is a real issue for the JSON serialization though.<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">John B.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On 2013-06-27, at 11:20 AM, Tim Bray &lt;<a href=3D"mailto:tbray@t=
extuality.com" target=3D"_blank">tbray@textuality.com</a>&gt; wrote:<o:p></=
o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The approach just seems wrong.&nbsp; If we require that conforming imple=
mentations MUST NOT emit dupes, then authors of receiving software can just=
 pick the best-performing parser with the
 nicest API, because they *all* perform correctly when there are no dupes.&=
nbsp; <br>
<br>
Who&#8217;s going to own the responsibility for making the authoritative fi=
nding that of the many JSON parsers in the Java ecosystem, these ones, but =
not those ones, are usable in JOSE applications?&nbsp; And suppose one that=
 has been previously OK is quietly optimized
 on GitHub to run 30% faster and as a side-effect silently ignores dupes?&n=
bsp; <o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">The benefit of using JSON is that there is widely deployed software to h=
andle it.&nbsp; It is a known problem that sloppy spec drafting has allowed=
 various kinds of problems to occur when
 dupe keys are received. &#8220;Doctor, it hurts when I do this.&#8221; &#8=
220;So... don&#8217;t do that.&#8221;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">Are we also going to specify the behavior of receiving software when the=
 JSON has a misplaced quotation mark?&nbsp; A missing trailing &#8220;}&#82=
21;?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;-T<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Jun 26, 2013 at 11:29 PM, Manger, James H &lt;<a href=3D"m=
ailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Manger@tea=
m.telstra.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Most JSON libraries that=
 silently accept [sob] dupe keys at least consistently use the
 last key. Allowing just that behaviour (or rejecting dupes), while forbidd=
ing acceptance of a non-last dupe (eg first key), is safe and allows most J=
SON libraries to be used. Since this accepts most libraries I think it is p=
ractical.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hence I suggest:</span><=
o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;A creator of a JOSE message MUST N=
OT put duplicate names in any JSON</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; object in a JOSE header.</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; &nbsp;&nbsp;To prevent attacks where a JOSE me=
ssage is interpreted as different</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; valid messages by different recipients, each r=
ecipient MUST either</span><o:p></o:p></p>
<p><span lang=3D"EN-AU">&gt; reject messages with duplicate names or accept=
 only the last name.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">This isn&#8217;t &#8220;=
truly predictable&#8221; as a message with dupes might be accepted or rejec=
ted.
 The crucial point is that if a message is accepted it is predictable.</spa=
n><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">--</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">James Manger</span><o:p>=
</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU" style=3D"font-size:11.0pt;font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tim Bray [mailto:<a hr=
ef=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.com</=
a>]
<br>
<b>Sent:</b> Thursday, 27 June 2013 4:16 PM<br>
<b>To:</b> Manger, James H<br>
<b>Cc:</b> Mike Jones; Jim Schaad; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">
jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-signature@too=
ls.ietf.org" target=3D"_blank">
draft-ietf-jose-json-web-signature@tools.ietf.org</a></span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU"><br>
<b>Subject:</b> Re: [jose] #27: member names MUST be unique needs additiona=
l text</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Well, you have a practical problem in that mo=
st implementers will want to use a standard JSON library, which is good pra=
ctice because it will be well-debugged,
 and most libraries [sob] silently take care of dupe keys and don&#8217;t h=
ave a way to tell the client software what happened. So if you want truly p=
redictable behavior, you&#8217;re forcing the use of hand-constructed JSON =
parsers. And that sucks, because getting good
 performance in JSON parsing is surprisingly hard, with dramatic performanc=
e differences between implementations. So you&#8217;re forcing receiving so=
ftware which wants to be conformant to use a hand-rolled parser which will =
probably have lousy performance and have
 other bugs which in fact may compromise security more than dupe-key tricks=
 could.&nbsp; -T</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">On Wed, Jun 26, 2013 at 10:39 PM, Manger, Jam=
es H &lt;<a href=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blan=
k">James.H.Manger@team.telstra.com</a>&gt; wrote:</span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span lang=3D"EN-AU">&gt; I think it&#8217;s a nice clean minimal soluti=
on to say that producers MUST<br>
&gt; NOT generate dupes, end of story.&nbsp; I don&#8217;t think saying any=
thing beyond<br>
&gt; that adds value. -T</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">Clean and minimal that may be, but it ignores=
 the security issue. We don't want a malicious producer (who is so maliciou=
s they ignore a MUST) to create JOSE messages
 that a JOSE-compliant security layer accepts as &quot;benign interpretatio=
n #1&quot; so it passes the message on to the JOSE-compliant backend app th=
at acts on &quot;nasty interpretation #2&quot;.<br>
<br>
--<br>
James Manger</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span lang=3D"EN-AU">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A1F90TK5EX14MBXC283r_--

From dick.hardt@gmail.com  Thu Jun 27 16:56:54 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720D611E8170 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Cm+vxGTRyVl for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 16:56:53 -0700 (PDT)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4E06F11E8163 for <jose@ietf.org>; Thu, 27 Jun 2013 16:56:51 -0700 (PDT)
Received: by mail-bk0-f51.google.com with SMTP id ji1so548541bkc.10 for <jose@ietf.org>; Thu, 27 Jun 2013 16:56:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GJmnH02OUWfs+PFtzcrCAvX1UD3360Ko51m6gm1s+Ak=; b=irxgr6V2DDxwyQbkGForaG7RTkf8DFylZCmTFupfI48G6XtfV5pRjz2jUcSuDtzaHT VrgkOgOd79SpXo9wJ0puVYks5ynV9bw67LggkP6STtaGTTOeZAQ6RUsDim2Gf8hRK9tU j6bIaB6Rg3b6Mp2EpQ9uUCMDDqM+lD03AH2avsiw722+oUlnR3nOPD1eD6My4Kig/Jnx OIjT3crHc64xrFfUpOUhNYoiQQVH+7q5/hmYVORIFyAtJs4JLTka8/aJYXlvz9RLxs+b uRGprgtcKWp4BkzZ0Y/68uTTuCkGKP6M9chB/xgVucIgJIQXBsPQ2FeoBe12aDCaALOp oCNw==
X-Received: by 10.205.36.194 with SMTP id tb2mr1492073bkb.174.1372377409368; Thu, 27 Jun 2013 16:56:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.205.133.75 with HTTP; Thu, 27 Jun 2013 16:56:29 -0700 (PDT)
In-Reply-To: <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 27 Jun 2013 16:56:29 -0700
Message-ID: <CAD9ie-sZ+w_HADMTnnkTC8XRJmjZvwYOmA+AhvJGTNPhhK=Z4g@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=bcaec52996ebfbea9004e02b8329
Cc: Jim Schaad <ietf@augustcellars.com>, n-sakimura <n-sakimura@nri.co.jp>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>, draft-ietf-jose-json-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Jun 2013 23:56:54 -0000

--bcaec52996ebfbea9004e02b8329
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes <rlb@ipv.sx> wrote:

> I think there are two separable issues here, both of which Mike and I
> probably have divergent opinions on :)
> 1. Syntax: Should it be possible for the "payload" field JWS to be a JSON
> string (instead of base64) when the payload is simply a UTF-8 string?
>

One of the goals of the token was that it not require encoding for it to be
transported in a request. IE that it be safe and SIMPLE to include in an
HTTP header or in a URL


> 2. Crypto: Must the JWS Signing Input be base64url encoded.
>
> The current answers to these questions are:
> 1. It is not possible.  Payload is always base64url encoded.
> 2. It is always base64url encoded.
>
> The answers should be:
> 1. The payload should not be base64url encoded unless it cannot be
> represented as a JSON string.
>

How does an implementation determine which parts are separated? Are '.'
escaped? Does the implementation need to parse the JSON to determine a
valid separator? How does it know the end of the JSON? That sounds really
hard to implement, or I am misunderstanding what you are proposing.



> 2. The JWS Signing Input should not be base64url encoded unless there is a
> JWS Protected Header
>
> Neither of these are complicated changes:
> 1. Add a "b64" header parameter that indicates that the payload is
> base64url-encoded binary, as opposed to a UTF-8 string.  Specify that this
> parameter is on by default in compact-formatted JWS objects.
>

And how is the header separated from the payload?


>  2. Modify the signing/verification instructions to switch based on the
> presence of a JWS Protected Header: "If the JWS Protected Header is absent
> or empty, then the JWS Signing Input is simply the JWS Payload (not
> encoded).  If the JWS Protected Header has a non-empty value, then the the
> JWS Signing Input is the concatenation of the Encoded JWS Header, a period
> ('.') character, and the Encoded JWS Payload"
>
> There are two reasons for these, both of which are important to make sure
> that this spec is applicable to a broad variety of use cases:
> 1. Compactness.  As Jim notes, quoted strings are shorter than
> base64url-encoded strings
>

The tokens are already compact enough.


>  2. Crypto-compatibility: Avoiding base64-encoding means that there's
> nothing JWS-specific about the signature value.  So for example, you could
> translate a JWS with no protected attributes to a CMS SignedData object
> with no protected attributes.
>

Not a useful feature from my point of view.

-- Dick

--bcaec52996ebfbea9004e02b8329
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes <span dir=3D"ltr">&=
lt;<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span=
> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I think there are two separ=
able issues here, both of which Mike and I probably have divergent opinions=
 on :)<div>

1. Syntax: Should it be possible for the &quot;payload&quot; field JWS to b=
e a JSON string (instead of base64) when the payload is simply a UTF-8 stri=
ng?</div></div></blockquote><div><br></div><div style>One of the goals of t=
he token was that it not require encoding for it to be transported in a req=
uest. IE that it be safe and SIMPLE to include in an HTTP header or in a UR=
L</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">
<div>2. Crypto: Must the JWS Signing Input be base64url encoded.</div><div>=
<br></div><div>The current answers to these questions are:</div><div>1. It =
is not possible. =A0Payload is always base64url encoded.</div><div><div>

2. It is always base64url encoded.</div>
<div><br></div><div>The answers should be:</div><div>1. The payload should =
not be base64url encoded unless it cannot be represented as a JSON string.<=
/div></div></div></blockquote><div><br></div><div style>How does an impleme=
ntation determine which parts are separated? Are &#39;.&#39; escaped? Does =
the implementation need to parse the JSON to determine a valid separator? H=
ow does it know the end of the JSON? That sounds really hard to implement, =
or I am misunderstanding what you are proposing.</div>

<div style><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><div>2. The JWS Signing Input should not be base64url encoded=
 unless there is a JWS Protected Header</div>


<div><br></div><div>Neither of these are complicated changes:<br></div><div=
>1. Add a &quot;b64&quot; header parameter that indicates that the payload =
is base64url-encoded binary, as opposed to a UTF-8 string. =A0Specify that =
this parameter is on by default in compact-formatted JWS objects.</div>

</div></div></blockquote><div><br></div><div style>And how is the header se=
parated from the payload?</div><div>=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<div dir=3D"ltr">
<div>
<div>2. Modify the signing/verification instructions to switch based on the=
 presence of a JWS Protected Header: &quot;If the JWS Protected Header is a=
bsent or empty, then the JWS Signing Input is simply the JWS Payload (not e=
ncoded). =A0If the JWS Protected Header has a non-empty value, then the the=
 JWS Signing Input is the concatenation of the Encoded JWS Header, a period=
 (&#39;.&#39;) character, and the Encoded JWS Payload&quot;</div>


<div><br></div><div>There are two reasons for these, both of which are impo=
rtant to make sure that this spec is applicable to a broad variety of use c=
ases:</div><div>1. Compactness. =A0As Jim notes, quoted strings are shorter=
 than base64url-encoded strings</div>

</div></div></blockquote><div><br></div><div style>The tokens are already c=
ompact enough.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr">

<div>
<div>2. Crypto-compatibility: Avoiding base64-encoding means that there&#39=
;s nothing JWS-specific about the signature value. =A0So for example, you c=
ould translate a JWS with no protected attributes to a CMS SignedData objec=
t with no protected attributes.</div>

</div></div></blockquote><div><br></div><div style>Not a useful feature fro=
m my point of view.</div><div style><br></div><div style>-- Dick</div></div=
></div></div>

--bcaec52996ebfbea9004e02b8329--

From edmundjay@sbcglobal.net  Thu Jun 27 17:01:44 2013
Return-Path: <edmundjay@sbcglobal.net>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EF911E8142 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ul8x3zyCNHIh for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:01:36 -0700 (PDT)
Received: from nm21-vm10.access.bullet.mail.bf1.yahoo.com (nm21-vm10.access.bullet.mail.bf1.yahoo.com [216.109.115.137]) by ietfa.amsl.com (Postfix) with ESMTP id 447A411E815A for <jose@ietf.org>; Thu, 27 Jun 2013 17:01:36 -0700 (PDT)
Received: from [66.196.81.165] by nm21.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 00:01:35 -0000
Received: from [66.196.81.139] by tm11.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 00:01:35 -0000
Received: from [127.0.0.1] by omp1015.access.mail.bf1.yahoo.com with NNFMP; 28 Jun 2013 00:01:35 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 588387.65727.bm@omp1015.access.mail.bf1.yahoo.com
Received: (qmail 15896 invoked by uid 60001); 28 Jun 2013 00:01:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1372377695; bh=7m5STR+yJl/Pgno5hXYc4mQSII8I5mmKkTTIRjsBryU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=DhYzi8KyMt9G3uSp4jxrCn7s5nfv2a7s5A3V20G7XhGG3/Itm00m7ToQC7Ie/sOJ2Yt/jzgQwqh3HUtxn/Ka5moS+3M9bdq4IMmbf9Mby3C787F6DUeTluT96GDN/gH04UXN+u9G56d4HKO841TrXj+F9tNgq7iJjPCXuaU2cnU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=nlvoRbef00s4VgfkP9TZEOjobz89M3W9Dr1tr/4R3f4tCGBB6NiVIpKC6nhJ47/hYF869Y1PSuAYsrR9u5SVH8C2FSGUvIqHgnFEWWMBmF1os1buRM2k9iFYoykf5ttDE+/FNdF51C2OoJ7jPJhpD5owZb1BsAzkUmnNn2FsQek=;
X-YMail-OSG: 3NEs6gsVM1ll3pT3SOZoDd0zdI02MfouN8tiL8SAn..gUe7 DKXC6pM3VhcBshAOB2p08_jp_4NXw4vCkW6nVUpgp1q_efb6WRxAnWucKvbv x5h8DMdH.HhNMprXi8ll8bLciTwDM3f.ogUMH9oA7m5uoQTLeJeQqgxhDR6m v_LuIvmcmrwSeGQi.LnJWgbqIB9K65gvtM5u0vkBRbz4N2ZIhtiCbM1mfaZr f0ipgfM57Ds60_mDT65CV6ZYaKV9V0atZMAwe3EByE_uuWkqRNDGpUruoO0t ZliYKBUSN3LGgIM.mo8z3fq5sX8Ly4P.EXLmlBiB.V0GTRgn2LyKkQhwdWOi aacMQ4jk7.6If1QYkno1ITzgXPVdphcapBZASI.Ee.ynxvpBoFh_bzlV2F4H 74gGNhF1GCTgijksZX94GzJ1b8YiwX204_963reh8YxalDoPC7nJFMN27kho YlFHyOn9DlYS9z69BYFdd.Qg7rvjnk8pZ4GrSt.DrGaBWxqmjz0BqEpY3fac WrE4Ps7ZeoOcoHo4XxnwxZ5tjQm3_7ZxwJNEmsthSYu20yfwEu3TDJOz9oPt XAVjvgBokdM6ojzVkhYlMPTPN6GkYs9HWVqXF
Received: from [70.36.254.42] by web184406.mail.bf1.yahoo.com via HTTP; Thu, 27 Jun 2013 17:01:35 PDT
X-Rocket-MIMEInfo: 002.001, SSBwcmVmZXIga2VlcGluZyB0aGUgYmFzZTY0dXJsIGVuY29kZWQgcGF5bG9hZCBhcyB0aGF0IHdpbGwgcmVzdWx0IGluIHNpbXBsZXIgY29kZSBwYXRocyBhbmQgYmV0dGVyIGludGVyb3BlcmFiaWxpdHkuCkFzIE1pa2UgcG9pbnRlZCBvdXQsIHRoZXJlIGNvdWxkIGJlIHByb2JsZW1zIHdpdGggY29tcGFjdCBzZXJpYWxpemF0aW9uIGlmIHlvdSB0dXJuIGI2NCBvZmYuCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KIEZyb206IE1pa2UgSm9uZXMgPE1pY2hhZWwuSm9uZXNAbWljcm9zb2Z0LmMBMAEBAQE-
X-RocketYMMF: edmundjay@sbcglobal.net
X-Mailer: YahooMailWebService/0.8.148.557
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Message-ID: <1372377695.85310.YahooMailNeo@web184406.mail.bf1.yahoo.com>
Date: Thu, 27 Jun 2013 17:01:35 -0700 (PDT)
From: Edmund Jay <ejay@mgi1.com>
To: Mike Jones <Michael.Jones@microsoft.com>, Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1789658926-599191483-1372377695=:85310"
Cc: n-sakimura <n-sakimura@nri.co.jp>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Edmund Jay <ejay@mgi1.com>
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: Fri, 28 Jun 2013 00:01:44 -0000

--1789658926-599191483-1372377695=:85310
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I prefer keeping the base64url encoded payload as that will result in simpl=
er code paths and better interoperability.=0AAs Mike pointed out, there cou=
ld be problems with compact serialization if you turn b64 off.=0A=0A=0A____=
____________________________=0A From: Mike Jones <Michael.Jones@microsoft.c=
om>=0ATo: Richard Barnes <rlb@ipv.sx>; Jim Schaad <ietf@augustcellars.com> =
=0ACc: n-sakimura <n-sakimura@nri.co.jp>; "jose@ietf.org" <jose@ietf.org>; =
"draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-w=
eb-signature@tools.ietf.org> =0ASent: Thursday, June 27, 2013 4:16 PM=0ASub=
ject: Re: [jose] #26: Allow for signature payload to not be base64 encoded=
=0A =0A=0A=0A =0AEven if we chose to support an unencoded payload represent=
ation as an option for the JSON Serialization (which I=E2=80=99m not advoca=
ting), having this be the default would be the wrong thing for two reasons:=
=0A=C2=A0=0A1.=C2=A0 It won=E2=80=99t work for the Compact Serialization, s=
ince it doesn=E2=80=99t ensure that the representation is URL-safe.=C2=A0 T=
he default should work for both serializations.=0A=C2=A0=0A2.=C2=A0 It assu=
mes a special case (a payload that can be represented as a transport-invari=
ant JSON string), which will often not work.=C2=A0 The default should be th=
e general case, which always works.=0A=C2=A0=0AAs for your suggestion to no=
t use the base64url encoded payload in the signature computation, this seem=
s to me like an attempt to reopen http://trac.tools.ietf.org/wg/jose/trac/t=
icket/23 (Make crypto independent of binary encoding (base64)) by another m=
eans, despite it already being resolved as =E2=80=9CWon=E2=80=99t Fix=E2=80=
=9D.=C2=A0 I don=E2=80=99t believe that constantly trying to revisit closed=
 issues is a productive activity, nor respectful of the working group=E2=80=
=99s time, so I therefore request that you let that one go.=0A=C2=A0=0A=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 Sincerely,=0A=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 -- Mike=0A=C2=A0=0AFrom:Richard Barnes [mailto:rlb@ipv.s=
x] =0ASent: Thursday, June 27, 2013 3:24 PM=0ATo: Jim Schaad=0ACc: Mike Jon=
es; n-sakimura; jose@ietf.org; draft-ietf-jose-json-web-signature@tools.iet=
f.org=0ASubject: Re: [jose] #26: Allow for signature payload to not be base=
64 encoded=0A=C2=A0=0AI think there are two separable issues here, both of =
which Mike and I probably have divergent opinions on :)=0A1. Syntax: Should=
 it be possible for the "payload" field JWS to be a JSON string (instead of=
 base64) when the payload is simply a UTF-8 string?=0A2. Crypto: Must the J=
WS Signing Input be base64url encoded.=0A=C2=A0=0AThe current answers to th=
ese questions are:=0A1. It is not possible. =C2=A0Payload is always base64u=
rl encoded.=0A2. It is always base64url encoded.=0A=C2=A0=0AThe answers sho=
uld be:=0A1. The payload should not be base64url encoded unless it cannot b=
e represented as a JSON string.=0A2. The JWS Signing Input should not be ba=
se64url encoded unless there is a JWS Protected Header=0A=C2=A0=0ANeither o=
f these are complicated changes:=0A1. Add a "b64" header parameter that ind=
icates that the payload is base64url-encoded binary, as opposed to a UTF-8 =
string. =C2=A0Specify that this parameter is on by default in compact-forma=
tted JWS objects.=0A2. Modify the signing/verification instructions to swit=
ch based on the presence of a JWS Protected Header: "If the JWS Protected H=
eader is absent or empty, then the JWS Signing Input is simply the JWS Payl=
oad (not encoded). =C2=A0If the JWS Protected Header has a non-empty value,=
 then the the JWS Signing Input is the concatenation of the Encoded JWS Hea=
der, a period ('.') character, and the Encoded JWS Payload"=0A=C2=A0=0ATher=
e are two reasons for these, both of which are important to make sure that =
this spec is applicable to a broad variety of use cases:=0A1. Compactness. =
=C2=A0As Jim notes, quoted strings are shorter than base64url-encoded strin=
gs=0A2. Crypto-compatibility: Avoiding base64-encoding means that there's n=
othing JWS-specific about the signature value. =C2=A0So for example, you co=
uld translate a JWS with no protected attributes to a CMS SignedData object=
 with no protected attributes.=0A=C2=A0=0AThis email brought to you by the =
number 2 and the letters J, W, and S :)=0A=C2=A0=0A--Richard=0A=C2=A0=0A[1]=
 Note that the default value for this header must be false, or else you los=
e the compactness advantage!=0A[2] You could also do this as a "Content-Enc=
oding" equivalent, "cenc": "b64". =C2=A0That would give you "base64 agility=
", as some folks have asked for, since you could have "b64" and "b64u" valu=
es. =C2=A0=0A[3] You could also do this like CMS, and have the JWS Signing =
Input in the latter case be "the concatenation of the Encoded JWS Header, a=
 period ('.') character, and the Encoded JWS Payload Hash". =C2=A0Where the=
 Encoded JWS Payload Hash is the base64url-encoded version of the hash you =
would otherwise be signing. =C2=A0This seems simpler to code, since you jus=
t digest the body, then if there's a protected header, you digest again. =
=C2=A0But it also breaks with existing code. =C2=A0=C2=A0=0A=C2=A0=0A=C2=A0=
=0A=C2=A0=0A=C2=A0=0AOn Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad <ietf@augu=
stcellars.com> wrote:=0ANo, my motivation is to allow for a smaller version=
 of the payload string. =C2=A0In some cases quoting it will generate a smal=
ler string than doing the base64 conversion on the string.=0A=0A=0A=0A> ---=
--Original Message-----=0A> From: Mike Jones [mailto:Michael.Jones@microsof=
t.com]=0A> Sent: Thursday, June 27, 2013 9:49 AM=0A> To: Jim Schaad; 'n-sak=
imura'=0A> Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf=
.org=0A> Subject: RE: [jose] #26: Allow for signature payload to not be bas=
e64 encoded=0A>=0A> Jim, you wrote "If I am not transporting the base64url =
encoded content,=0A> because it is not in the "payload" field, then why sho=
uld I need to base64=0A> encode it just to validate the signature. =C2=A0Th=
is is the alto case."=0A>=0A> So am I correct then, in thinking that your m=
otivation for #26 is actually #25 -=0A> Detached content for the ALTO use c=
ase? =C2=A0As John and Nat had written, this=0A> could be handled by the sp=
ecs as they are today by signing a hash of the=0A> detached content and inc=
luding a compact JWS representing that signature as=0A> an x-alto-signature=
 header. =C2=A0That doesn't require changing the signature=0A> calculation.=
=0A>=0A> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -- Mike=0A>=0A> -----Original Messag=
e-----=0A> From: Jim Schaad [mailto:ietf@augustcellars.com]=0A> Sent: Thurs=
day, June 27, 2013 9:41 AM=0A> To: 'n-sakimura'=0A> Cc: draft-ietf-jose-jso=
n-web-signature@tools.ietf.org; Mike Jones;=0A> jose@ietf.org=0A> Subject: =
RE: [jose] #26: Allow for signature payload to not be base64 encoded=0A>=0A=
> Nat,=0A>=0A> The only thing that can be signed or encrypted is an octet s=
tring. (A slight over=0A> generalization. GOST for example hashes an intege=
r, tree hashes can do=0A> strange things but a sufficiently true statement =
for our purposes.)=0A>=0A> A that being said - yes case 1 would be somethin=
g you can do. =C2=A0Case #2 would=0A> not be something that you can do beca=
use it is not an octet string.=0A>=0A> If you are looking at JavaScript, in=
 order to hash something as an octet string it=0A> can be one of three thin=
gs. =C2=A0A UInt8Array, an Int8Array and, due to=0A> convention, a string w=
here the top byte of all of the code points in the string is=0A> zero.=0A>=
=0A> We currently don't have an efficient way to encode the Uint8Array case=
,=0A> although that might not be true if we are looking at new ECMA specifi=
cations=0A> which apparently are adding more defined types and serializatio=
n methods for=0A> those types.=0A>=0A> > -----Original Message-----=0A> > F=
rom: n-sakimura [mailto:n-sakimura@nri.co.jp]=0A> > Sent: Wednesday, June 2=
6, 2013 7:55 PM=0A> > To: Jim Schaad=0A> > Cc: draft-ietf-jose-json-web-sig=
nature@tools.ietf.org;=0A> > michael.jones@microsoft.com; jose@ietf.org=0A>=
 > Subject: Re: [jose] #26: Allow for signature payload to not be base64=0A=
> > encoded=0A> >=0A> > Let me understand the problem.=0A> >=0A> > Are you =
suggesting that we should be able to do something like:=0A> >=0A> > Case 1:=
=0A> >=0A> > =C2=A0 =C2=A0 =C2=A0 {"protected":<integrity-protected shared =
header contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0"unprotected":<non-inte=
grity-protected shared header contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0=
"payload":"this is a multi\nline text payload of which a line=0A> > can be =
very very very long and wrapped during transmission. "=0A> > =C2=A0 =C2=A0 =
=C2=A0 =C2=A0"signatures":[=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 {"header":"<p=
er-signature unprotected header 1 contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0"signature":"<signature 1 contents>"},=0A> > =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 ...=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 {"header":"<per-signature =
unprotected header N contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"s=
ignature":"<signature N contents>"}],=0A> > =C2=A0 =C2=A0 =C2=A0 }=0A> >=0A=
> > or even=0A> >=0A> > Case 2:=0A> >=0A> > =C2=A0 =C2=A0 =C2=A0 {"protecte=
d":<integrity-protected shared header contents>",=0A> > =C2=A0 =C2=A0 =C2=
=A0 =C2=A0"unprotected":<non-integrity-protected shared header contents>",=
=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0"payload":{=0A> > =C2=A0 =C2=A0 "this":"i=
s a json",=0A> > =C2=A0 =C2=A0 "payload":"which is not base64url encoded"=
=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0}=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0"signa=
tures":[=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 {"header":"<per-signature unprot=
ected header 1 contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"signatu=
re":"<signature 1 contents>"},=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 ...=0A> > =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 {"header":"<per-signature unprotected header N =
contents>",=0A> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"signature":"<signature=
 N contents>"}],=0A> > =C2=A0 =C2=A0 =C2=A0 }=0A> >=0A> > Then, I am worrie=
d about allowing them because in general we would not=0A> > know what would=
 a transmission mechanism and user agents (including=0A> > text=0A> > edito=
rs) would do to them, like Mike mentioned. I do not think we=0A> > should a=
ssume the property of the transmission mechanism in JOSE level.=0A> > Assum=
ing that would cause brittleness in the implementations.=0A> >=0A> > For de=
tached signature, I do not understand why you would want non-=0A> > base64u=
rl encoded payload. The application should define how to hash=0A> > the oct=
et stream that it wants to calculate signature over it, and we=0A> > can ju=
st include the base64url encoded hash in the "payload".=0A> > Why would you=
 like to do other encoding for the hash?=0A>=0A> If I am not transporting t=
he base64url encoded content, because it is not in=0A> the "payload" field,=
 then why should I need to base64 encode it just to=0A> validate the signat=
ure. =C2=A0This is the alto case.=0A>=0A> Jim=0A>=0A> >=0A> > --=0A> > Nat =
Sakimura (n-sakimura@nri.co.jp)=0A> > Nomura Research Institute=0A> >=0A> >=
 PLEASE READ:=0A> > The information contained in this e-mail is confidentia=
l and intended=0A> > for the named recipient(s) only.=0A> > If you are not =
an intended recipient of this e-mail, you are hereby=0A> > notified that an=
y review, dissemination, distribution or duplication=0A> > of this message =
is strictly prohibited. If you have received this=0A> > message in error, p=
lease notify the sender immediately and delete your=0A> copy from your syst=
em.=0A=0A=0A_______________________________________________=0Ajose mailing =
list=0Ajose@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/jose=0A=C2=A0=
=0A_______________________________________________=0Ajose mailing list=0Ajo=
se@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo/jose
--1789658926-599191483-1372377695=:85310
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ta=
homa, new york, times, serif;font-size:10pt"><div><span>I prefer keeping th=
e base64url encoded payload as that will result in simpler code paths and b=
etter interoperability.</span></div><div style=3D"color: rgb(0, 0, 0); font=
-size: 13px; font-family: tahoma, 'new york', times, serif; background-colo=
r: transparent; font-style: normal; "><span>As Mike pointed out, there coul=
d be problems with compact serialization if you turn b64 off.</span></div><=
div><br></div>  <div style=3D"font-family: tahoma, 'new york', times, serif=
; font-size: 10pt; "> <div style=3D"font-family: 'times new roman', 'new yo=
rk', times, serif; font-size: 12pt; "> <div dir=3D"ltr"> <hr size=3D"1">  <=
font size=3D"2" face=3D"Arial"> <b><span style=3D"font-weight:bold;">From:<=
/span></b> Mike Jones &lt;Michael.Jones@microsoft.com&gt;<br> <b><span styl=
e=3D"font-weight: bold;">To:</span></b> Richard Barnes &lt;rlb@ipv.sx&gt;; =
Jim Schaad
 &lt;ietf@augustcellars.com&gt; <br><b><span style=3D"font-weight: bold;">C=
c:</span></b> n-sakimura &lt;n-sakimura@nri.co.jp&gt;; "jose@ietf.org" &lt;=
jose@ietf.org&gt;; "draft-ietf-jose-json-web-signature@tools.ietf.org" &lt;=
draft-ietf-jose-json-web-signature@tools.ietf.org&gt; <br> <b><span style=
=3D"font-weight: bold;">Sent:</span></b> Thursday, June 27, 2013 4:16 PM<br=
> <b><span style=3D"font-weight: bold;">Subject:</span></b> Re: [jose] #26:=
 Allow for signature payload to not be base64 encoded<br> </font> </div> <d=
iv class=3D"y_msg_container"><br><div id=3D"yiv221984933">=0A=0A =0A =0A<st=
yle><!--=0A#yiv221984933  =0A _filtered #yiv221984933 {font-family:Calibri;=
panose-1:2 15 5 2 2 2 4 3 2 4;}=0A _filtered #yiv221984933 {font-family:Tah=
oma;panose-1:2 11 6 4 3 5 4 4 2 4;}=0A#yiv221984933  =0A#yiv221984933 p.yiv=
221984933MsoNormal, #yiv221984933 li.yiv221984933MsoNormal, #yiv221984933 d=
iv.yiv221984933MsoNormal=0A=09{margin:0in;margin-bottom:.0001pt;font-size:1=
2.0pt;font-family:"Times New Roman", "serif";}=0A#yiv221984933 a:link, #yiv=
221984933 span.yiv221984933MsoHyperlink=0A=09{color:blue;text-decoration:un=
derline;}=0A#yiv221984933 a:visited, #yiv221984933 span.yiv221984933MsoHype=
rlinkFollowed=0A=09{color:purple;text-decoration:underline;}=0A#yiv22198493=
3 span.yiv221984933EmailStyle17=0A=09{font-family:"Calibri", "sans-serif";c=
olor:#1F497D;}=0A#yiv221984933 .yiv221984933MsoChpDefault=0A=09{}=0A _filte=
red #yiv221984933 {margin:1.0in 1.0in 1.0in 1.0in;}=0A#yiv221984933 div.yiv=
221984933WordSection1=0A=09{}=0A--></style>=0A=0A<div>=0A<div class=3D"yiv2=
21984933WordSection1">=0A<div class=3D"yiv221984933MsoNormal"><span style=
=3D"font-size:11.0pt;color:#1F497D;">Even if we chose to support an unencod=
ed payload representation as an option for the JSON Serialization (which I=
=E2=80=99m not advocating), having this be the default=0A would be the wron=
g thing for two reasons:</span></div> =0A<div class=3D"yiv221984933MsoNorma=
l"><span style=3D"font-size:11.0pt;color:#1F497D;"> &nbsp;</span></div> =0A=
<div class=3D"yiv221984933MsoNormal"><span style=3D"font-size:11.0pt;color:=
#1F497D;">1.&nbsp; It won=E2=80=99t work for the Compact Serialization, sin=
ce it doesn=E2=80=99t ensure that the representation is URL-safe.&nbsp; The=
 default should work for both serializations.</span></div> =0A<div class=3D=
"yiv221984933MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D;"> &n=
bsp;</span></div> =0A<div class=3D"yiv221984933MsoNormal"><span style=3D"fo=
nt-size:11.0pt;color:#1F497D;">2.&nbsp; It assumes a special case (a payloa=
d that can be represented as a transport-invariant JSON string), which will=
 often not work.&nbsp; The default should be the=0A general case, which alw=
ays works.</span></div> =0A<div class=3D"yiv221984933MsoNormal"><span style=
=3D"font-size:11.0pt;color:#1F497D;"> &nbsp;</span></div> =0A<div class=3D"=
yiv221984933MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D;">As f=
or your suggestion to not use the base64url encoded payload in the signatur=
e computation, this seems to me like an attempt to reopen=0A<a rel=3D"nofol=
low" target=3D"_blank" href=3D"http://trac.tools.ietf.org/wg/jose/trac/tick=
et/23">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a> (Make crypto i=
ndependent of binary encoding (base64)) by another means, despite it alread=
y being resolved as =E2=80=9CWon=E2=80=99t Fix=E2=80=9D.&nbsp; I don=E2=80=
=99t believe that=0A constantly trying to revisit closed issues is a produc=
tive activity, nor respectful of the working group=E2=80=99s time, so I the=
refore request that you let that one go.</span></div> =0A<div class=3D"yiv2=
21984933MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D;"> &nbsp;<=
/span></div> =0A<div class=3D"yiv221984933MsoNormal"><span style=3D"font-si=
ze:11.0pt;color:#1F497D;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sincerely,</span></div> =0A<div class=3D"yiv2=
21984933MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D;">&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- M=
ike</span></div> =0A<div class=3D"yiv221984933MsoNormal"><span style=3D"fon=
t-size:11.0pt;color:#1F497D;"> &nbsp;</span></div> =0A<div class=3D"yiv2219=
84933MsoNormal"><b><span style=3D"font-size:10.0pt;">From:</span></b><span =
style=3D"font-size:10.0pt;"> Richard Barnes [mailto:rlb@ipv.sx]=0A<br>=0A<b=
>Sent:</b> Thursday, June 27, 2013 3:24 PM<br>=0A<b>To:</b> Jim Schaad<br>=
=0A<b>Cc:</b> Mike Jones; n-sakimura; jose@ietf.org; draft-ietf-jose-json-w=
eb-signature@tools.ietf.org<br>=0A<b>Subject:</b> Re: [jose] #26: Allow for=
 signature payload to not be base64 encoded</span></div> =0A<div class=3D"y=
iv221984933MsoNormal"> &nbsp;</div> =0A<div>=0A<div class=3D"yiv221984933Ms=
oNormal">I think there are two separable issues here, both of which Mike an=
d I probably have divergent opinions on :)</div> =0A<div>=0A<div class=3D"y=
iv221984933MsoNormal">1. Syntax: Should it be possible for the "payload" fi=
eld JWS to be a JSON string (instead of base64) when the payload is simply =
a UTF-8 string?</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNorm=
al">2. Crypto: Must the JWS Signing Input be base64url encoded.</div> =0A</=
div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div>=
=0A<div>=0A<div class=3D"yiv221984933MsoNormal">The current answers to thes=
e questions are:</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNor=
mal">1. It is not possible. &nbsp;Payload is always base64url encoded.</div=
> =0A</div>=0A<div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">2. It is=
 always base64url encoded.</div> =0A</div>=0A<div>=0A<div class=3D"yiv22198=
4933MsoNormal"> &nbsp;</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933=
MsoNormal">The answers should be:</div> =0A</div>=0A<div>=0A<div class=3D"y=
iv221984933MsoNormal">1. The payload should not be base64url encoded unless=
 it cannot be represented as a JSON string.</div> =0A</div>=0A<div>=0A<div =
class=3D"yiv221984933MsoNormal">2. The JWS Signing Input should not be base=
64url encoded unless there is a JWS Protected Header</div> =0A</div>=0A<div=
>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div>=0A<div>=0A=
<div class=3D"yiv221984933MsoNormal">Neither of these are complicated chang=
es:</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">1. Add a=
 "b64" header parameter that indicates that the payload is base64url-encode=
d binary, as opposed to a UTF-8 string. &nbsp;Specify that this parameter i=
s on by default in compact-formatted JWS objects.</div> =0A</div>=0A<div>=
=0A<div class=3D"yiv221984933MsoNormal">2. Modify the signing/verification =
instructions to switch based on the presence of a JWS Protected Header: "If=
 the JWS Protected Header is absent or empty, then the JWS Signing Input is=
 simply the JWS Payload (not encoded). &nbsp;If the JWS=0A Protected Header=
 has a non-empty value, then the the JWS Signing Input is the concatenation=
 of the Encoded JWS Header, a period ('.') character, and the Encoded JWS P=
ayload"</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nb=
sp;</div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">There ar=
e two reasons for these, both of which are important to make sure that this=
 spec is applicable to a broad variety of use cases:</div> =0A</div>=0A<div=
>=0A<div class=3D"yiv221984933MsoNormal">1. Compactness. &nbsp;As Jim notes=
, quoted strings are shorter than base64url-encoded strings</div> =0A</div>=
=0A<div>=0A<div class=3D"yiv221984933MsoNormal">2. Crypto-compatibility: Av=
oiding base64-encoding means that there's nothing JWS-specific about the si=
gnature value. &nbsp;So for example, you could translate a JWS with no prot=
ected attributes to a CMS SignedData object with no protected attributes.</=
div> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div>=
 =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">This email brough=
t to you by the number 2 and the letters J, W, and S :)</div> =0A</div>=0A<=
div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div>=0A<div>=
=0A<div class=3D"yiv221984933MsoNormal">--Richard</div> =0A</div>=0A<div>=
=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div>=0A<div>=0A<=
div class=3D"yiv221984933MsoNormal">[1] Note that the default value for thi=
s header must be false, or else you lose the compactness advantage!</div> =
=0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">[2] You could also=
 do this as a "Content-Encoding" equivalent, "cenc": "b64". &nbsp;That woul=
d give you "base64 agility", as some folks have asked for, since you could =
have "b64" and "b64u" values. &nbsp;</div> =0A</div>=0A<div>=0A<div class=
=3D"yiv221984933MsoNormal">[3] You could also do this like CMS, and have th=
e JWS Signing Input in the latter case be "the concatenation of the Encoded=
 JWS Header, a period ('.') character, and the Encoded JWS Payload Hash". &=
nbsp;Where the Encoded JWS Payload Hash is=0A the base64url-encoded version=
 of the hash you would otherwise be signing. &nbsp;This seems simpler to co=
de, since you just digest the body, then if there's a protected header, you=
 digest again. &nbsp;But it also breaks with existing code. &nbsp;&nbsp;</d=
iv> =0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =
=0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A<=
/div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div=
>=0A</div>=0A</div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal" style=3D=
"margin-bottom:12.0pt;"> &nbsp;</div> =0A<div>=0A<div class=3D"yiv221984933=
MsoNormal">On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad &lt;<a rel=3D"nofoll=
ow" ymailto=3D"mailto:ietf@augustcellars.com" target=3D"_blank" href=3D"mai=
lto:ietf@augustcellars.com">ietf@augustcellars.com</a>&gt; wrote:</div> =0A=
<div class=3D"yiv221984933MsoNormal">No, my motivation is to allow for a sm=
aller version of the payload string. &nbsp;In some cases quoting it will ge=
nerate a smaller string than doing the base64 conversion on the string.</di=
v> =0A<div>=0A<div class=3D"yiv221984933MsoNormal"><br>=0A<br>=0A<br>=0A&gt=
; -----Original Message-----<br>=0A&gt; From: Mike Jones [mailto:<a rel=3D"=
nofollow" ymailto=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank" =
href=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>=
]</div> =0A</div>=0A<div>=0A<div>=0A<div class=3D"yiv221984933MsoNormal">&g=
t; Sent: Thursday, June 27, 2013 9:49 AM<br>=0A&gt; To: Jim Schaad; 'n-saki=
mura'<br>=0A&gt; Cc: <a rel=3D"nofollow" ymailto=3D"mailto:draft-ietf-jose-=
json-web-signature@tools.ietf.org" target=3D"_blank" href=3D"mailto:draft-i=
etf-jose-json-web-signature@tools.ietf.org">draft-ietf-jose-json-web-signat=
ure@tools.ietf.org</a>;=0A<a rel=3D"nofollow" ymailto=3D"mailto:jose@ietf.o=
rg" target=3D"_blank" href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>=
=0A&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base=
64 encoded<br>=0A&gt;<br>=0A&gt; Jim, you wrote "If I am not transporting t=
he base64url encoded content,<br>=0A&gt; because it is not in the "payload"=
 field, then why should I need to base64<br>=0A&gt; encode it just to valid=
ate the signature. &nbsp;This is the alto case."<br>=0A&gt;<br>=0A&gt; So a=
m I correct then, in thinking that your motivation for #26 is actually #25 =
-<br>=0A&gt; Detached content for the ALTO use case? &nbsp;As John and Nat =
had written, this<br>=0A&gt; could be handled by the specs as they are toda=
y by signing a hash of the<br>=0A&gt; detached content and including a comp=
act JWS representing that signature as<br>=0A&gt; an x-alto-signature heade=
r. &nbsp;That doesn't require changing the signature<br>=0A&gt; calculation=
.<br>=0A&gt;<br>=0A&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -- Mike<br>=0A&gt;<br=
>=0A&gt; -----Original Message-----<br>=0A&gt; From: Jim Schaad [mailto:<a =
rel=3D"nofollow" ymailto=3D"mailto:ietf@augustcellars.com" target=3D"_blank=
" href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a>]<br>=0A=
&gt; Sent: Thursday, June 27, 2013 9:41 AM<br>=0A&gt; To: 'n-sakimura'<br>=
=0A&gt; Cc: <a rel=3D"nofollow" ymailto=3D"mailto:draft-ietf-jose-json-web-=
signature@tools.ietf.org" target=3D"_blank" href=3D"mailto:draft-ietf-jose-=
json-web-signature@tools.ietf.org">draft-ietf-jose-json-web-signature@tools=
.ietf.org</a>; Mike Jones;<br>=0A&gt; <a rel=3D"nofollow" ymailto=3D"mailto=
:jose@ietf.org" target=3D"_blank" href=3D"mailto:jose@ietf.org">jose@ietf.o=
rg</a><br>=0A&gt; Subject: RE: [jose] #26: Allow for signature payload to n=
ot be base64 encoded<br>=0A&gt;<br>=0A&gt; Nat,<br>=0A&gt;<br>=0A&gt; The o=
nly thing that can be signed or encrypted is an octet string. (A slight ove=
r<br>=0A&gt; generalization. GOST for example hashes an integer, tree hashe=
s can do<br>=0A&gt; strange things but a sufficiently true statement for ou=
r purposes.)<br>=0A&gt;<br>=0A&gt; A that being said - yes case 1 would be =
something you can do. &nbsp;Case #2 would<br>=0A&gt; not be something that =
you can do because it is not an octet string.<br>=0A&gt;<br>=0A&gt; If you =
are looking at JavaScript, in order to hash something as an octet string it=
<br>=0A&gt; can be one of three things. &nbsp;A UInt8Array, an Int8Array an=
d, due to<br>=0A&gt; convention, a string where the top byte of all of the =
code points in the string is<br>=0A&gt; zero.<br>=0A&gt;<br>=0A&gt; We curr=
ently don't have an efficient way to encode the Uint8Array case,<br>=0A&gt;=
 although that might not be true if we are looking at new ECMA specificatio=
ns<br>=0A&gt; which apparently are adding more defined types and serializat=
ion methods for<br>=0A&gt; those types.<br>=0A&gt;<br>=0A&gt; &gt; -----Ori=
ginal Message-----<br>=0A&gt; &gt; From: n-sakimura [mailto:<a rel=3D"nofol=
low" ymailto=3D"mailto:n-sakimura@nri.co.jp" target=3D"_blank" href=3D"mail=
to:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>]<br>=0A&gt; &gt; Sent: We=
dnesday, June 26, 2013 7:55 PM<br>=0A&gt; &gt; To: Jim Schaad<br>=0A&gt; &g=
t; Cc: <a rel=3D"nofollow" ymailto=3D"mailto:draft-ietf-jose-json-web-signa=
ture@tools.ietf.org" target=3D"_blank" href=3D"mailto:draft-ietf-jose-json-=
web-signature@tools.ietf.org">draft-ietf-jose-json-web-signature@tools.ietf=
.org</a>;<br>=0A&gt; &gt; <a rel=3D"nofollow" ymailto=3D"mailto:michael.jon=
es@microsoft.com" target=3D"_blank" href=3D"mailto:michael.jones@microsoft.=
com">michael.jones@microsoft.com</a>;=0A<a rel=3D"nofollow" ymailto=3D"mail=
to:jose@ietf.org" target=3D"_blank" href=3D"mailto:jose@ietf.org">jose@ietf=
.org</a><br>=0A&gt; &gt; Subject: Re: [jose] #26: Allow for signature paylo=
ad to not be base64<br>=0A&gt; &gt; encoded<br>=0A&gt; &gt;<br>=0A&gt; &gt;=
 Let me understand the problem.<br>=0A&gt; &gt;<br>=0A&gt; &gt; Are you sug=
gesting that we should be able to do something like:<br>=0A&gt; &gt;<br>=0A=
&gt; &gt; Case 1:<br>=0A&gt; &gt;<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; {"pr=
otected":&lt;integrity-protected shared header contents&gt;",<br>=0A&gt; &g=
t; &nbsp; &nbsp; &nbsp; &nbsp;"unprotected":&lt;non-integrity-protected sha=
red header contents&gt;",<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;"paylo=
ad":"this is a multi\nline text payload of which a line<br>=0A&gt; &gt; can=
 be very very very long and wrapped during transmission. "<br>=0A&gt; &gt; =
&nbsp; &nbsp; &nbsp; &nbsp;"signatures":[<br>=0A&gt; &gt; &nbsp; &nbsp; &nb=
sp; &nbsp; {"header":"&lt;per-signature unprotected header 1 contents&gt;",=
<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"signature":"&lt;signatu=
re 1 contents&gt;"},<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; ...<br>=0A=
&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {"header":"&lt;per-signature unprotec=
ted header N contents&gt;",<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp;"signature":"&lt;signature N contents&gt;"}],<br>=0A&gt; &gt; &nbsp; &nb=
sp; &nbsp; }<br>=0A&gt; &gt;<br>=0A&gt; &gt; or even<br>=0A&gt; &gt;<br>=0A=
&gt; &gt; Case 2:<br>=0A&gt; &gt;<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; {"pr=
otected":&lt;integrity-protected shared header contents&gt;",<br>=0A&gt; &g=
t; &nbsp; &nbsp; &nbsp; &nbsp;"unprotected":&lt;non-integrity-protected sha=
red header contents&gt;",<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;"paylo=
ad":{<br>=0A&gt; &gt; &nbsp; &nbsp; "this":"is a json",<br>=0A&gt; &gt; &nb=
sp; &nbsp; "payload":"which is not base64url encoded"<br>=0A&gt; &gt; &nbsp=
; &nbsp; &nbsp; &nbsp;}<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp;"signatu=
res":[<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; {"header":"&lt;per-signa=
ture unprotected header 1 contents&gt;",<br>=0A&gt; &gt; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp;"signature":"&lt;signature 1 contents&gt;"},<br>=0A&gt; &gt=
; &nbsp; &nbsp; &nbsp; &nbsp; ...<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; &nbs=
p; {"header":"&lt;per-signature unprotected header N contents&gt;",<br>=0A&=
gt; &gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"signature":"&lt;signature N con=
tents&gt;"}],<br>=0A&gt; &gt; &nbsp; &nbsp; &nbsp; }<br>=0A&gt; &gt;<br>=0A=
&gt; &gt; Then, I am worried about allowing them because in general we woul=
d not<br>=0A&gt; &gt; know what would a transmission mechanism and user age=
nts (including<br>=0A&gt; &gt; text<br>=0A&gt; &gt; editors) would do to th=
em, like Mike mentioned. I do not think we<br>=0A&gt; &gt; should assume th=
e property of the transmission mechanism in JOSE level.<br>=0A&gt; &gt; Ass=
uming that would cause brittleness in the implementations.<br>=0A&gt; &gt;<=
br>=0A&gt; &gt; For detached signature, I do not understand why you would w=
ant non-<br>=0A&gt; &gt; base64url encoded payload. The application should =
define how to hash<br>=0A&gt; &gt; the octet stream that it wants to calcul=
ate signature over it, and we<br>=0A&gt; &gt; can just include the base64ur=
l encoded hash in the "payload".<br>=0A&gt; &gt; Why would you like to do o=
ther encoding for the hash?<br>=0A&gt;<br>=0A&gt; If I am not transporting =
the base64url encoded content, because it is not in<br>=0A&gt; the "payload=
" field, then why should I need to base64 encode it just to<br>=0A&gt; vali=
date the signature. &nbsp;This is the alto case.<br>=0A&gt;<br>=0A&gt; Jim<=
br>=0A&gt;<br>=0A&gt; &gt;<br>=0A&gt; &gt; --<br>=0A&gt; &gt; Nat Sakimura =
(<a rel=3D"nofollow" ymailto=3D"mailto:n-sakimura@nri.co.jp" target=3D"_bla=
nk" href=3D"mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>)<br>=0A&g=
t; &gt; Nomura Research Institute<br>=0A&gt; &gt;<br>=0A&gt; &gt; PLEASE RE=
AD:<br>=0A&gt; &gt; The information contained in this e-mail is confidentia=
l and intended<br>=0A&gt; &gt; for the named recipient(s) only.<br>=0A&gt; =
&gt; If you are not an intended recipient of this e-mail, you are hereby<br=
>=0A&gt; &gt; notified that any review, dissemination, distribution or dupl=
ication<br>=0A&gt; &gt; of this message is strictly prohibited. If you have=
 received this<br>=0A&gt; &gt; message in error, please notify the sender i=
mmediately and delete your<br>=0A&gt; copy from your system.<br>=0A<br>=0A<=
br>=0A_______________________________________________<br>=0Ajose mailing li=
st<br>=0A<a rel=3D"nofollow" ymailto=3D"mailto:jose@ietf.org" target=3D"_bl=
ank" href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>=0A<a rel=3D"nofoll=
ow" target=3D"_blank" href=3D"https://www.ietf.org/mailman/listinfo/jose">h=
ttps://www.ietf.org/mailman/listinfo/jose</a></div> =0A</div>=0A</div>=0A</=
div>=0A<div class=3D"yiv221984933MsoNormal"> &nbsp;</div> =0A</div>=0A</div=
>=0A</div>=0A=0A</div><br>_______________________________________________<b=
r>jose mailing list<br><a ymailto=3D"mailto:jose@ietf.org" href=3D"mailto:j=
ose@ietf.org">jose@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/=
listinfo/jose" target=3D"_blank">https://www.ietf.org/mailman/listinfo/jose=
</a><br><br><br></div> </div> </div>  </div></body></html>
--1789658926-599191483-1372377695=:85310--

From matiasw@gmail.com  Thu Jun 27 17:21:29 2013
Return-Path: <matiasw@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD4C21F940D for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YtMeDNIiLv1u for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:21:27 -0700 (PDT)
Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 18D6E21F9406 for <jose@ietf.org>; Thu, 27 Jun 2013 17:21:26 -0700 (PDT)
Received: by mail-ee0-f46.google.com with SMTP id d41so708367eek.5 for <jose@ietf.org>; Thu, 27 Jun 2013 17:21:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aw9P7ZCQ+QoHFH46RlmpyFeMYaXAbxbLOp64LBsukLQ=; b=C8s/3Jhr4FGUMVGBR2QTLJBW21G8SWhbVJqZ8+tDNHuFciU37/TKqrXJl6p6nj4c2w ZYqLpStn+Z6FnzUN4YNhinyP4hXgy6u2undZzvplzIa/LAmDPlvuMP6+mFB7ScuCGwYd UzKQFYn1TQQoMbuT4twbgdbu8HIVsc+4EcdActGjgpqpii/7y90Ft1O61xB/lLYQVmr8 F0jeJRhY5W536kHqvn4o3u0fEq2iJSW2UK7IAp958iCUdjkut0DSAVqh5Aw6zJwoxUvt lnSBG38JXIWA0TUCuiDaahq6kcP18ehXN8z1/DAlNKiLxjXqz8RkzE2bW5tFvI9MZw/u SfwQ==
X-Received: by 10.15.102.68 with SMTP id bq44mr11228796eeb.89.1372378886169; Thu, 27 Jun 2013 17:21:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.191.79 with HTTP; Thu, 27 Jun 2013 17:21:05 -0700 (PDT)
In-Reply-To: <1372377695.85310.YahooMailNeo@web184406.mail.bf1.yahoo.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com> <1372377695.85310.YahooMailNeo@web184406.mail.bf1.yahoo.com>
From: Matias Woloski <matiasw@gmail.com>
Date: Thu, 27 Jun 2013 21:21:05 -0300
Message-ID: <CAK+KdNVPF63M5L+g=+Zn9KJvN+kkxsU1xvbWEvLnVNVK+ySubg@mail.gmail.com>
To: Edmund Jay <ejay@mgi1.com>
Content-Type: multipart/alternative; boundary=089e01634fa402164704e02bdc78
Cc: Richard Barnes <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>, n-sakimura <n-sakimura@nri.co.jp>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 00:21:29 -0000

--089e01634fa402164704e02bdc78
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

+1. KISS.


On Thu, Jun 27, 2013 at 9:01 PM, Edmund Jay <ejay@mgi1.com> wrote:

> I prefer keeping the base64url encoded payload as that will result in
> simpler code paths and better interoperability.
> As Mike pointed out, there could be problems with compact serialization i=
f
> you turn b64 off.
>
>   ------------------------------
>  *From:* Mike Jones <Michael.Jones@microsoft.com>
> *To:* Richard Barnes <rlb@ipv.sx>; Jim Schaad <ietf@augustcellars.com>
> *Cc:* n-sakimura <n-sakimura@nri.co.jp>; "jose@ietf.org" <jose@ietf.org>;
> "draft-ietf-jose-json-web-signature@tools.ietf.org" <
> draft-ietf-jose-json-web-signature@tools.ietf.org>
> *Sent:* Thursday, June 27, 2013 4:16 PM
>
> *Subject:* Re: [jose] #26: Allow for signature payload to not be base64
> encoded
>
>  Even if we chose to support an unencoded payload representation as an
> option for the JSON Serialization (which I=92m not advocating), having th=
is
> be the default would be the wrong thing for two reasons:
>
> 1.  It won=92t work for the Compact Serialization, since it doesn=92t ens=
ure
> that the representation is URL-safe.  The default should work for both
> serializations.
>
> 2.  It assumes a special case (a payload that can be represented as a
> transport-invariant JSON string), which will often not work.  The default
> should be the general case, which always works.
>
> As for your suggestion to not use the base64url encoded payload in the
> signature computation, this seems to me like an attempt to reopen
> http://trac.tools.ietf.org/wg/jose/trac/ticket/23 (Make crypto
> independent of binary encoding (base64)) by another means, despite it
> already being resolved as =93Won=92t Fix=94.  I don=92t believe that cons=
tantly
> trying to revisit closed issues is a productive activity, nor respectful =
of
> the working group=92s time, so I therefore request that you let that one =
go.
>
>                                                                 Sincerely=
,
>                                                                 -- Mike
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 27, 2013 3:24 PM
> *To:* Jim Schaad
> *Cc:* Mike Jones; n-sakimura; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
> *Subject:* Re: [jose] #26: Allow for signature payload to not be base64
> encoded
>
>  I think there are two separable issues here, both of which Mike and I
> probably have divergent opinions on :)
>  1. Syntax: Should it be possible for the "payload" field JWS to be a
> JSON string (instead of base64) when the payload is simply a UTF-8 string=
?
>  2. Crypto: Must the JWS Signing Input be base64url encoded.
>
>  The current answers to these questions are:
>  1. It is not possible.  Payload is always base64url encoded.
>   2. It is always base64url encoded.
>
>  The answers should be:
>  1. The payload should not be base64url encoded unless it cannot be
> represented as a JSON string.
>  2. The JWS Signing Input should not be base64url encoded unless there is
> a JWS Protected Header
>
>  Neither of these are complicated changes:
>  1. Add a "b64" header parameter that indicates that the payload is
> base64url-encoded binary, as opposed to a UTF-8 string.  Specify that thi=
s
> parameter is on by default in compact-formatted JWS objects.
>  2. Modify the signing/verification instructions to switch based on the
> presence of a JWS Protected Header: "If the JWS Protected Header is absen=
t
> or empty, then the JWS Signing Input is simply the JWS Payload (not
> encoded).  If the JWS Protected Header has a non-empty value, then the th=
e
> JWS Signing Input is the concatenation of the Encoded JWS Header, a perio=
d
> ('.') character, and the Encoded JWS Payload"
>
>  There are two reasons for these, both of which are important to make
> sure that this spec is applicable to a broad variety of use cases:
>  1. Compactness.  As Jim notes, quoted strings are shorter than
> base64url-encoded strings
>  2. Crypto-compatibility: Avoiding base64-encoding means that there's
> nothing JWS-specific about the signature value.  So for example, you coul=
d
> translate a JWS with no protected attributes to a CMS SignedData object
> with no protected attributes.
>
>  This email brought to you by the number 2 and the letters J, W, and S :)
>
>  --Richard
>
>  [1] Note that the default value for this header must be false, or else
> you lose the compactness advantage!
>  [2] You could also do this as a "Content-Encoding" equivalent, "cenc":
> "b64".  That would give you "base64 agility", as some folks have asked fo=
r,
> since you could have "b64" and "b64u" values.
>  [3] You could also do this like CMS, and have the JWS Signing Input in
> the latter case be "the concatenation of the Encoded JWS Header, a period
> ('.') character, and the Encoded JWS Payload Hash".  Where the Encoded JW=
S
> Payload Hash is the base64url-encoded version of the hash you would
> otherwise be signing.  This seems simpler to code, since you just digest
> the body, then if there's a protected header, you digest again.  But it
> also breaks with existing code.
>
>
>
>
>  On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:
> No, my motivation is to allow for a smaller version of the payload string=
.
>  In some cases quoting it will generate a smaller string than doing the
> base64 conversion on the string.
>
>
>
> > -----Original Message-----
> > From: Mike Jones [mailto:Michael.Jones@microsoft.com]
>   > Sent: Thursday, June 27, 2013 9:49 AM
> > To: Jim Schaad; 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Jim, you wrote "If I am not transporting the base64url encoded content,
> > because it is not in the "payload" field, then why should I need to
> base64
> > encode it just to validate the signature.  This is the alto case."
> >
> > So am I correct then, in thinking that your motivation for #26 is
> actually #25 -
> > Detached content for the ALTO use case?  As John and Nat had written,
> this
> > could be handled by the specs as they are today by signing a hash of th=
e
> > detached content and including a compact JWS representing that signatur=
e
> as
> > an x-alto-signature header.  That doesn't require changing the signatur=
e
> > calculation.
> >
> >                               -- Mike
> >
> > -----Original Message-----
> > From: Jim Schaad [mailto:ietf@augustcellars.com]
> > Sent: Thursday, June 27, 2013 9:41 AM
> > To: 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones;
> > jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Nat,
> >
> > The only thing that can be signed or encrypted is an octet string. (A
> slight over
> > generalization. GOST for example hashes an integer, tree hashes can do
> > strange things but a sufficiently true statement for our purposes.)
> >
> > A that being said - yes case 1 would be something you can do.  Case #2
> would
> > not be something that you can do because it is not an octet string.
> >
> > If you are looking at JavaScript, in order to hash something as an octe=
t
> string it
> > can be one of three things.  A UInt8Array, an Int8Array and, due to
> > convention, a string where the top byte of all of the code points in th=
e
> string is
> > zero.
> >
> > We currently don't have an efficient way to encode the Uint8Array case,
> > although that might not be true if we are looking at new ECMA
> specifications
> > which apparently are adding more defined types and serialization method=
s
> for
> > those types.
> >
> > > -----Original Message-----
> > > From: n-sakimura [mailto:n-sakimura@nri.co.jp]
> > > Sent: Wednesday, June 26, 2013 7:55 PM
> > > To: Jim Schaad
> > > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > > michael.jones@microsoft.com; jose@ietf.org
> > > Subject: Re: [jose] #26: Allow for signature payload to not be base64
> > > encoded
> > >
> > > Let me understand the problem.
> > >
> > > Are you suggesting that we should be able to do something like:
> > >
> > > Case 1:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>=
",
> > >        "payload":"this is a multi\nline text payload of which a line
> > > can be very very very long and wrapped during transmission. "
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > or even
> > >
> > > Case 2:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>=
",
> > >        "payload":{
> > >     "this":"is a json",
> > >     "payload":"which is not base64url encoded"
> > >        }
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > Then, I am worried about allowing them because in general we would no=
t
> > > know what would a transmission mechanism and user agents (including
> > > text
> > > editors) would do to them, like Mike mentioned. I do not think we
> > > should assume the property of the transmission mechanism in JOSE leve=
l.
> > > Assuming that would cause brittleness in the implementations.
> > >
> > > For detached signature, I do not understand why you would want non-
> > > base64url encoded payload. The application should define how to hash
> > > the octet stream that it wants to calculate signature over it, and we
> > > can just include the base64url encoded hash in the "payload".
> > > Why would you like to do other encoding for the hash?
> >
> > If I am not transporting the base64url encoded content, because it is
> not in
> > the "payload" field, then why should I need to base64 encode it just to
> > validate the signature.  This is the alto case.
> >
> > Jim
> >
> > >
> > > --
> > > Nat Sakimura (n-sakimura@nri.co.jp)
> > > Nomura Research Institute
> > >
> > > PLEASE READ:
> > > The information contained in this e-mail is confidential and intended
> > > for the named recipient(s) only.
> > > If you are not an intended recipient of this e-mail, you are hereby
> > > notified that any review, dissemination, distribution or duplication
> > > of this message is strictly prohibited. If you have received this
> > > message in error, please notify the sender immediately and delete you=
r
> > copy from your system.
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--089e01634fa402164704e02bdc78
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1. KISS.</div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Thu, Jun 27, 2013 at 9:01 PM, Edmund Jay <span dir=3D=
"ltr">&lt;<a href=3D"mailto:ejay@mgi1.com" target=3D"_blank">ejay@mgi1.com<=
/a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div style=3D"font-size:10pt;font-famil=
y:tahoma,new york,times,serif"><div><span>I prefer keeping the base64url en=
coded payload as that will result in simpler code paths and better interope=
rability.</span></div>

<div style=3D"font-style:normal;font-size:13px;background-color:transparent=
;font-family:tahoma,&#39;new york&#39;,times,serif"><span>As Mike pointed o=
ut, there could be problems with compact serialization if you turn b64 off.=
</span></div>

<div><br></div>  <div style=3D"font-family:tahoma,&#39;new york&#39;,times,=
serif;font-size:10pt"> <div style=3D"font-family:&#39;times new roman&#39;,=
&#39;new york&#39;,times,serif;font-size:12pt"> <div dir=3D"ltr"> <hr size=
=3D"1">

  <font face=3D"Arial"> <b><span style=3D"font-weight:bold">From:</span></b=
> Mike Jones &lt;<a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_=
blank">Michael.Jones@microsoft.com</a>&gt;<br> <b><span style=3D"font-weigh=
t:bold">To:</span></b> Richard Barnes &lt;rlb@ipv.sx&gt;; Jim Schaad
 &lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augus=
tcellars.com</a>&gt; <br><b><span style=3D"font-weight:bold">Cc:</span></b>=
 n-sakimura &lt;<a href=3D"mailto:n-sakimura@nri.co.jp" target=3D"_blank">n=
-sakimura@nri.co.jp</a>&gt;; &quot;<a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>&quot; &lt;<a href=3D"mailto:jose@ietf.org" ta=
rget=3D"_blank">jose@ietf.org</a>&gt;; &quot;<a href=3D"mailto:draft-ietf-j=
ose-json-web-signature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-js=
on-web-signature@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-=
jose-json-web-signature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-j=
son-web-signature@tools.ietf.org</a>&gt; <br>

 <b><span style=3D"font-weight:bold">Sent:</span></b> Thursday, June 27, 20=
13 4:16 PM<div><div class=3D"h5"><br> <b><span style=3D"font-weight:bold">S=
ubject:</span></b> Re: [jose] #26: Allow for signature payload to not be ba=
se64 encoded<br>

 </div></div></font> </div><div><div class=3D"h5"> <div><br><div>

=20
=20


<div>
<div>
<div><span style=3D"font-size:11.0pt;color:#1f497d">Even if we chose to sup=
port an unencoded payload representation as an option for the JSON Serializ=
ation (which I=92m not advocating), having this be the default
 would be the wrong thing for two reasons:</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d"> =A0</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d">1.=A0 It won=92t work f=
or the Compact Serialization, since it doesn=92t ensure that the representa=
tion is URL-safe.=A0 The default should work for both serializations.</span=
></div>

=20
<div><span style=3D"font-size:11.0pt;color:#1f497d"> =A0</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d">2.=A0 It assumes a spec=
ial case (a payload that can be represented as a transport-invariant JSON s=
tring), which will often not work.=A0 The default should be the
 general case, which always works.</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d"> =A0</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d">As for your suggestion =
to not use the base64url encoded payload in the signature computation, this=
 seems to me like an attempt to reopen
<a rel=3D"nofollow" href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/=
23" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a>=
 (Make crypto independent of binary encoding (base64)) by another means, de=
spite it already being resolved as =93Won=92t Fix=94.=A0 I don=92t believe =
that
 constantly trying to revisit closed issues is a productive activity, nor r=
espectful of the working group=92s time, so I therefore request that you le=
t that one go.</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d"> =A0</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 Sincerely,</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 -- Mike</span></div>=20
<div><span style=3D"font-size:11.0pt;color:#1f497d"> =A0</span></div>=20
<div><b><span style=3D"font-size:10.0pt">From:</span></b><span style=3D"fon=
t-size:10.0pt"> Richard Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:24 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> Mike Jones; n-sakimura; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-s=
ignature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signatu=
re@tools.ietf.org</a><br>


<b>Subject:</b> Re: [jose] #26: Allow for signature payload to not be base6=
4 encoded</span></div>=20
<div> =A0</div>=20
<div>
<div>I think there are two separable issues here, both of which Mike and I =
probably have divergent opinions on :)</div>=20
<div>
<div>1. Syntax: Should it be possible for the &quot;payload&quot; field JWS=
 to be a JSON string (instead of base64) when the payload is simply a UTF-8=
 string?</div>=20
</div>
<div>
<div>2. Crypto: Must the JWS Signing Input be base64url encoded.</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>The current answers to these questions are:</div>=20
</div>
<div>
<div>1. It is not possible. =A0Payload is always base64url encoded.</div>=
=20
</div>
<div>
<div>
<div>2. It is always base64url encoded.</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>The answers should be:</div>=20
</div>
<div>
<div>1. The payload should not be base64url encoded unless it cannot be rep=
resented as a JSON string.</div>=20
</div>
<div>
<div>2. The JWS Signing Input should not be base64url encoded unless there =
is a JWS Protected Header</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>Neither of these are complicated changes:</div>=20
</div>
<div>
<div>1. Add a &quot;b64&quot; header parameter that indicates that the payl=
oad is base64url-encoded binary, as opposed to a UTF-8 string. =A0Specify t=
hat this parameter is on by default in compact-formatted JWS objects.</div>

=20
</div>
<div>
<div>2. Modify the signing/verification instructions to switch based on the=
 presence of a JWS Protected Header: &quot;If the JWS Protected Header is a=
bsent or empty, then the JWS Signing Input is simply the JWS Payload (not e=
ncoded). =A0If the JWS
 Protected Header has a non-empty value, then the the JWS Signing Input is =
the concatenation of the Encoded JWS Header, a period (&#39;.&#39;) charact=
er, and the Encoded JWS Payload&quot;</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>There are two reasons for these, both of which are important to make s=
ure that this spec is applicable to a broad variety of use cases:</div>=20
</div>
<div>
<div>1. Compactness. =A0As Jim notes, quoted strings are shorter than base6=
4url-encoded strings</div>=20
</div>
<div>
<div>2. Crypto-compatibility: Avoiding base64-encoding means that there&#39=
;s nothing JWS-specific about the signature value. =A0So for example, you c=
ould translate a JWS with no protected attributes to a CMS SignedData objec=
t with no protected attributes.</div>

=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>This email brought to you by the number 2 and the letters J, W, and S =
:)</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>--Richard</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div>[1] Note that the default value for this header must be false, or else=
 you lose the compactness advantage!</div>=20
</div>
<div>
<div>[2] You could also do this as a &quot;Content-Encoding&quot; equivalen=
t, &quot;cenc&quot;: &quot;b64&quot;. =A0That would give you &quot;base64 a=
gility&quot;, as some folks have asked for, since you could have &quot;b64&=
quot; and &quot;b64u&quot; values. =A0</div>

=20
</div>
<div>
<div>[3] You could also do this like CMS, and have the JWS Signing Input in=
 the latter case be &quot;the concatenation of the Encoded JWS Header, a pe=
riod (&#39;.&#39;) character, and the Encoded JWS Payload Hash&quot;. =A0Wh=
ere the Encoded JWS Payload Hash is
 the base64url-encoded version of the hash you would otherwise be signing. =
=A0This seems simpler to code, since you just digest the body, then if ther=
e&#39;s a protected header, you digest again. =A0But it also breaks with ex=
isting code. =A0=A0</div>

=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
<div>
<div> =A0</div>=20
</div>
</div>
</div>
<div>
<div style=3D"margin-bottom:12.0pt"> =A0</div>=20
<div>
<div>On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad &lt;<a rel=3D"nofollow" hr=
ef=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.c=
om</a>&gt; wrote:</div>=20
<div>No, my motivation is to allow for a smaller version of the payload str=
ing. =A0In some cases quoting it will generate a smaller string than doing =
the base64 conversion on the string.</div>=20
<div>
<div><br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Mike Jones [mailto:<a rel=3D"nofollow" href=3D"mailto:Michael.Jo=
nes@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>]</div>=
=20
</div>
<div>
<div>
<div>&gt; Sent: Thursday, June 27, 2013 9:49 AM<br>
&gt; To: Jim Schaad; &#39;n-sakimura&#39;<br>
&gt; Cc: <a rel=3D"nofollow" href=3D"mailto:draft-ietf-jose-json-web-signat=
ure@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signature@to=
ols.ietf.org</a>;
<a rel=3D"nofollow" href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ie=
tf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Jim, you wrote &quot;If I am not transporting the base64url encoded co=
ntent,<br>
&gt; because it is not in the &quot;payload&quot; field, then why should I =
need to base64<br>
&gt; encode it just to validate the signature. =A0This is the alto case.&qu=
ot;<br>
&gt;<br>
&gt; So am I correct then, in thinking that your motivation for #26 is actu=
ally #25 -<br>
&gt; Detached content for the ALTO use case? =A0As John and Nat had written=
, this<br>
&gt; could be handled by the specs as they are today by signing a hash of t=
he<br>
&gt; detached content and including a compact JWS representing that signatu=
re as<br>
&gt; an x-alto-signature header. =A0That doesn&#39;t require changing the s=
ignature<br>
&gt; calculation.<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Mike<br=
>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Jim Schaad [mailto:<a rel=3D"nofollow" href=3D"mailto:ietf@augus=
tcellars.com" target=3D"_blank">ietf@augustcellars.com</a>]<br>
&gt; Sent: Thursday, June 27, 2013 9:41 AM<br>
&gt; To: &#39;n-sakimura&#39;<br>
&gt; Cc: <a rel=3D"nofollow" href=3D"mailto:draft-ietf-jose-json-web-signat=
ure@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signature@to=
ols.ietf.org</a>; Mike Jones;<br>
&gt; <a rel=3D"nofollow" href=3D"mailto:jose@ietf.org" target=3D"_blank">jo=
se@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Nat,<br>
&gt;<br>
&gt; The only thing that can be signed or encrypted is an octet string. (A =
slight over<br>
&gt; generalization. GOST for example hashes an integer, tree hashes can do=
<br>
&gt; strange things but a sufficiently true statement for our purposes.)<br=
>
&gt;<br>
&gt; A that being said - yes case 1 would be something you can do. =A0Case =
#2 would<br>
&gt; not be something that you can do because it is not an octet string.<br=
>
&gt;<br>
&gt; If you are looking at JavaScript, in order to hash something as an oct=
et string it<br>
&gt; can be one of three things. =A0A UInt8Array, an Int8Array and, due to<=
br>
&gt; convention, a string where the top byte of all of the code points in t=
he string is<br>
&gt; zero.<br>
&gt;<br>
&gt; We currently don&#39;t have an efficient way to encode the Uint8Array =
case,<br>
&gt; although that might not be true if we are looking at new ECMA specific=
ations<br>
&gt; which apparently are adding more defined types and serialization metho=
ds for<br>
&gt; those types.<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: n-sakimura [mailto:<a rel=3D"nofollow" href=3D"mailto:n-sak=
imura@nri.co.jp" target=3D"_blank">n-sakimura@nri.co.jp</a>]<br>
&gt; &gt; Sent: Wednesday, June 26, 2013 7:55 PM<br>
&gt; &gt; To: Jim Schaad<br>
&gt; &gt; Cc: <a rel=3D"nofollow" href=3D"mailto:draft-ietf-jose-json-web-s=
ignature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signatu=
re@tools.ietf.org</a>;<br>
&gt; &gt; <a rel=3D"nofollow" href=3D"mailto:michael.jones@microsoft.com" t=
arget=3D"_blank">michael.jones@microsoft.com</a>;
<a rel=3D"nofollow" href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ie=
tf.org</a><br>
&gt; &gt; Subject: Re: [jose] #26: Allow for signature payload to not be ba=
se64<br>
&gt; &gt; encoded<br>
&gt; &gt;<br>
&gt; &gt; Let me understand the problem.<br>
&gt; &gt;<br>
&gt; &gt; Are you suggesting that we should be able to do something like:<b=
r>
&gt; &gt;<br>
&gt; &gt; Case 1:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:&quot;this is a multi\nline te=
xt payload of which a line<br>
&gt; &gt; can be very very very long and wrapped during transmission. &quot=
;<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; or even<br>
&gt; &gt;<br>
&gt; &gt; Case 2:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:{<br>
&gt; &gt; =A0 =A0 &quot;this&quot;:&quot;is a json&quot;,<br>
&gt; &gt; =A0 =A0 &quot;payload&quot;:&quot;which is not base64url encoded&=
quot;<br>
&gt; &gt; =A0 =A0 =A0 =A0}<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; Then, I am worried about allowing them because in general we woul=
d not<br>
&gt; &gt; know what would a transmission mechanism and user agents (includi=
ng<br>
&gt; &gt; text<br>
&gt; &gt; editors) would do to them, like Mike mentioned. I do not think we=
<br>
&gt; &gt; should assume the property of the transmission mechanism in JOSE =
level.<br>
&gt; &gt; Assuming that would cause brittleness in the implementations.<br>
&gt; &gt;<br>
&gt; &gt; For detached signature, I do not understand why you would want no=
n-<br>
&gt; &gt; base64url encoded payload. The application should define how to h=
ash<br>
&gt; &gt; the octet stream that it wants to calculate signature over it, an=
d we<br>
&gt; &gt; can just include the base64url encoded hash in the &quot;payload&=
quot;.<br>
&gt; &gt; Why would you like to do other encoding for the hash?<br>
&gt;<br>
&gt; If I am not transporting the base64url encoded content, because it is =
not in<br>
&gt; the &quot;payload&quot; field, then why should I need to base64 encode=
 it just to<br>
&gt; validate the signature. =A0This is the alto case.<br>
&gt;<br>
&gt; Jim<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Nat Sakimura (<a rel=3D"nofollow" href=3D"mailto:n-sakimura@nri.c=
o.jp" target=3D"_blank">n-sakimura@nri.co.jp</a>)<br>
&gt; &gt; Nomura Research Institute<br>
&gt; &gt;<br>
&gt; &gt; PLEASE READ:<br>
&gt; &gt; The information contained in this e-mail is confidential and inte=
nded<br>
&gt; &gt; for the named recipient(s) only.<br>
&gt; &gt; If you are not an intended recipient of this e-mail, you are here=
by<br>
&gt; &gt; notified that any review, dissemination, distribution or duplicat=
ion<br>
&gt; &gt; of this message is strictly prohibited. If you have received this=
<br>
&gt; &gt; message in error, please notify the sender immediately and delete=
 your<br>
&gt; copy from your system.<br>
<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a rel=3D"nofollow" href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ie=
tf.org</a><br>
<a rel=3D"nofollow" href=3D"https://www.ietf.org/mailman/listinfo/jose" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/jose</a></div>=20
</div>
</div>
</div>
<div> =A0</div>=20
</div>
</div>
</div>

</div><br>_______________________________________________<br>jose mailing l=
ist<br><a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a>=
<br><a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/jose</a><br>

<br><br></div> </div></div></div> </div>  </div></div><br>_________________=
______________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--089e01634fa402164704e02bdc78--

From matiasw@gmail.com  Thu Jun 27 17:37:33 2013
Return-Path: <matiasw@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8953611E8130 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T7DZt5b16FP0 for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 17:37:32 -0700 (PDT)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id EEFE821F9AB3 for <jose@ietf.org>; Thu, 27 Jun 2013 17:37:31 -0700 (PDT)
Received: by mail-ee0-f52.google.com with SMTP id c50so719523eek.39 for <jose@ietf.org>; Thu, 27 Jun 2013 17:37:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mhWAErnJ9Tuz273VK1V6cANb1SOCx8rO8EHizhIpiCE=; b=UNum6ClFwIXrHhocEef1LukqeFbwQCdBg3iZFHc/BoN1nR1edyzj4qGyedHZ3ZSRcW jBcfc7xHMsoQ+UPNRYfANMWAJ0TeKsMNWhXdYvnYStxAVumj7yrezzYCYfGFjJMPFzWn BmJC8Q2uyUy5+CuhW59VEpJ6VIiNlFawvm92C0P4hPAcRDA/X/huY0cf52SRp6IZVkeI PrbkEftGf+S/FfMe3kveDWO206e0fSvGJtozTnj6Zv8kOmeMVZrV4SuOZ3+jax7Xwyq5 4GtCIjnw66fjXrVk9WtqFD3FAfD37QBr8Rr7/lTWqAbEpuBh2KQqafTTFQAyMGt+Rusa 3V1w==
X-Received: by 10.15.102.68 with SMTP id bq44mr11265394eeb.89.1372379849924; Thu, 27 Jun 2013 17:37:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.191.79 with HTTP; Thu, 27 Jun 2013 17:37:09 -0700 (PDT)
In-Reply-To: <049501ce7356$31644680$942cd380$@augustcellars.com>
References: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com> <049501ce7356$31644680$942cd380$@augustcellars.com>
From: Matias Woloski <matiasw@gmail.com>
Date: Thu, 27 Jun 2013 21:37:09 -0300
Message-ID: <CAK+KdNWr-KBkO6_Z_iodcq-R_KBPFvFaU2i+ak5xLbLB=Vg9pw@mail.gmail.com>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=089e01634fa473cdae04e02c15fe
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 00:37:33 -0000

--089e01634fa473cdae04e02c15fe
Content-Type: text/plain; charset=ISO-8859-1

While I like the detailed examples of barnes draft. I have to agree, that
the explosion of combinations is not good for implementers. It's
overwhelming and doesn't foster interop on the open web. Look at XMLEnc and
all the options you have, imho that's why standards don't end up being
adopted wildly in every language (only some of those algos end up being
implemented in each language creating an interop nightmare). Jones draft is
simple enough (although it would be good to add some examples).


On Thu, Jun 27, 2013 at 1:48 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> James,
>
> The small devices use case does present a reason for wanting to use
> AES-GCM rather than AESKW for this case.  Specifically, there is no need to
> have silicon devoted to doing AES decrypt.  All operations can be done just
> with AES encrypt.
>
> jim
>
> > -----Original Message-----
> > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
> > Manger, James H
> > Sent: Wednesday, June 26, 2013 7:40 PM
> > To: jose@ietf.org
> > Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
> >
> > I don't think we should standardize
> draft-jones-jose-aes-gcm-key-wrap-00. No
> > rationale is apparent. We already have an AES-based key wrap algorithm
> > (A128KW, A256KW), which has a 64-bit size overhead. The AES-GCM key
> > wrap algorithm in this draft add almost no useful properties, but has a
> 224-bit
> > size overhead.
> >
> > I like the concatenation of the IV, ciphertext, and tag byte arrays. But
> doing
> > this here while content encryption serializes the same values as
> dot-separated
> > B64 blobs does smell of poor ad hoc design. It is nice to highlight how a
> > previous choice complicates extending JOSE to other algorithms, but only
> if
> > we then fix that previous choice.
> >
> > If the additional authenticated data (AAD) was used to bind the CEK
> algorithm
> > id (or other context info, as ConcatKDF does) to the wrapped key, then
> there
> > would at least be an extra security property that would make this key
> wrap
> > algorithm worth considering. For instance, instead of AAD being empty,
> AAD
> > could be the "key wrap: " + "enc" value.
> >
> > By reusing a CEK algorithm as a KEK algorithm, and supporting direct
> > encryption, we substantially increase the risk that an attacker can
> rearrange
> > some encrypted content so a legitimate recipient treats it as an
> encrypted key
> > leading to security flaws.
> >
> > For example, Alice sends "Start of PIN = 8" confidentially to Bob:
> >   {alg:dir,enc:A128GCM,kid:1}..iv.ciphertext.tag
> > An attacker seeing this JOSE message learns nothing about the 1st digit
> of the
> > PIN.
> > But if the attacker sends 10 messages to Bob for 10 guess of that digit:
> >
> > {alg:A128GCMKW,enc:A128GCM,kid:1}.iv|ciphertext|tag.ivN.ciphertextN.tag
> > N
> > where ivN.ciphertextN.tagN are calculated using an AES key of "Start of
> PIN =
> > <N>", then 9 messages will cause errors, while 1 message will be
> accepted --
> > revealing the supposedly confidential information in 10 guesses instead
> of
> > 2^128.
> >
> > Actually the above attack does not quite work for the compact encoding as
> > AAD is never empty for content encryption. I not certain for the JSON
> > encoding. In any case, an explicit and unambiguous AAD value for key
> > wrapping would be good.
> >
> > Finally, a key wrap algorithm like this should go to the IETF crypto
> group
> > (CRFG) instead of being invented in JOSE. We have already spent a year
> > unpicking a JOSE-special AEAD algorithm.
> >
> > --
> > James Manger
> >
> >
> > > -----Original Message-----
> > > From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
> > > Of Jim Schaad
> > > Sent: Wednesday, 26 June 2013 2:53 AM
> > > To: jose@ietf.org
> > > Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
> > >
> > > We now have two documents   one from Richard and one from Mike   which
> > > provide the two different ways that have been proposed for doing key
> > > wrapping with an AEAD algorithm.
> > >
> > > Please review the two documents and provide comments to the list.
> > >
> > > Jim
> >
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--089e01634fa473cdae04e02c15fe
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">While I like the detailed examples of barnes draft. I have=
 to agree, that the explosion of combinations is not good for implementers.=
 It&#39;s overwhelming and doesn&#39;t foster interop on the open web. Look=
 at XMLEnc and all the options you have, imho that&#39;s why standards don&=
#39;t end up being adopted wildly in every language (only some of those alg=
os end up being implemented in each language creating an interop nightmare)=
. Jones draft is simple enough (although it would be good to add some examp=
les).
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 2=
7, 2013 at 1:48 PM, Jim Schaad <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf=
@augustcellars.com" target=3D"_blank">ietf@augustcellars.com</a>&gt;</span>=
 wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">James,<br>
<br>
The small devices use case does present a reason for wanting to use AES-GCM=
 rather than AESKW for this case. =A0Specifically, there is no need to have=
 silicon devoted to doing AES decrypt. =A0All operations can be done just w=
ith AES encrypt.<br>



<span><font color=3D"#888888"><br>
jim<br>
</font></span><div><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">jose-=
bounces@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" targe=
t=3D"_blank">jose-bounces@ietf.org</a>] On Behalf Of<br>
</div><div><div>&gt; Manger, James H<br>
&gt; Sent: Wednesday, June 26, 2013 7:40 PM<br>
&gt; To: <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</=
a><br>
&gt; Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping<br>
&gt;<br>
&gt; I don&#39;t think we should standardize draft-jones-jose-aes-gcm-key-w=
rap-00. No<br>
&gt; rationale is apparent. We already have an AES-based key wrap algorithm=
<br>
&gt; (A128KW, A256KW), which has a 64-bit size overhead. The AES-GCM key<br=
>
&gt; wrap algorithm in this draft add almost no useful properties, but has =
a 224-bit<br>
&gt; size overhead.<br>
&gt;<br>
&gt; I like the concatenation of the IV, ciphertext, and tag byte arrays. B=
ut doing<br>
&gt; this here while content encryption serializes the same values as dot-s=
eparated<br>
&gt; B64 blobs does smell of poor ad hoc design. It is nice to highlight ho=
w a<br>
&gt; previous choice complicates extending JOSE to other algorithms, but on=
ly if<br>
&gt; we then fix that previous choice.<br>
&gt;<br>
&gt; If the additional authenticated data (AAD) was used to bind the CEK al=
gorithm<br>
&gt; id (or other context info, as ConcatKDF does) to the wrapped key, then=
 there<br>
&gt; would at least be an extra security property that would make this key =
wrap<br>
&gt; algorithm worth considering. For instance, instead of AAD being empty,=
 AAD<br>
&gt; could be the &quot;key wrap: &quot; + &quot;enc&quot; value.<br>
&gt;<br>
&gt; By reusing a CEK algorithm as a KEK algorithm, and supporting direct<b=
r>
&gt; encryption, we substantially increase the risk that an attacker can re=
arrange<br>
&gt; some encrypted content so a legitimate recipient treats it as an encry=
pted key<br>
&gt; leading to security flaws.<br>
&gt;<br>
&gt; For example, Alice sends &quot;Start of PIN =3D 8&quot; confidentially=
 to Bob:<br>
&gt; =A0 {alg:dir,enc:A128GCM,kid:1}..iv.ciphertext.tag<br>
&gt; An attacker seeing this JOSE message learns nothing about the 1st digi=
t of the<br>
&gt; PIN.<br>
&gt; But if the attacker sends 10 messages to Bob for 10 guess of that digi=
t:<br>
&gt;<br>
&gt; {alg:A128GCMKW,enc:A128GCM,kid:1}.iv|ciphertext|tag.ivN.ciphertextN.ta=
g<br>
&gt; N<br>
&gt; where ivN.ciphertextN.tagN are calculated using an AES key of &quot;St=
art of PIN =3D<br>
&gt; &lt;N&gt;&quot;, then 9 messages will cause errors, while 1 message wi=
ll be accepted --<br>
&gt; revealing the supposedly confidential information in 10 guesses instea=
d of<br>
&gt; 2^128.<br>
&gt;<br>
&gt; Actually the above attack does not quite work for the compact encoding=
 as<br>
&gt; AAD is never empty for content encryption. I not certain for the JSON<=
br>
&gt; encoding. In any case, an explicit and unambiguous AAD value for key<b=
r>
&gt; wrapping would be good.<br>
&gt;<br>
&gt; Finally, a key wrap algorithm like this should go to the IETF crypto g=
roup<br>
&gt; (CRFG) instead of being invented in JOSE. We have already spent a year=
<br>
&gt; unpicking a JOSE-special AEAD algorithm.<br>
&gt;<br>
&gt; --<br>
&gt; James Manger<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:jose-bounces@ietf.org" target=3D"_blank">=
jose-bounces@ietf.org</a> [mailto:<a href=3D"mailto:jose-bounces@ietf.org" =
target=3D"_blank">jose-bounces@ietf.org</a>] On Behalf<br>
&gt; &gt; Of Jim Schaad<br>
&gt; &gt; Sent: Wednesday, 26 June 2013 2:53 AM<br>
&gt; &gt; To: <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.=
org</a><br>
&gt; &gt; Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping<br>
&gt; &gt;<br>
&gt; &gt; We now have two documents =A0 one from Richard and one from Mike =
=A0 which<br>
&gt; &gt; provide the two different ways that have been proposed for doing =
key<br>
&gt; &gt; wrapping with an AEAD algorithm.<br>
&gt; &gt;<br>
&gt; &gt; Please review the two documents and provide comments to the list.=
<br>
&gt; &gt;<br>
&gt; &gt; Jim<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; jose mailing list<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/jose</a><br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</div></div></blockquote></div><br></div></div>

--089e01634fa473cdae04e02c15fe--

From cabo@tzi.org  Thu Jun 27 23:15:52 2013
Return-Path: <cabo@tzi.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 266DE21F9D8E for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 23:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.635
X-Spam-Level: 
X-Spam-Status: No, score=-98.635 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, MIME_QP_LONG_LINE=1.819, RCVD_ILLEGAL_IP=3.196, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NziguVYFBVRl for <jose@ietfa.amsl.com>; Thu, 27 Jun 2013 23:15:42 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBCA21F9C2B for <jose@ietf.org>; Thu, 27 Jun 2013 23:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5S6EkkT016292; Fri, 28 Jun 2013 08:14:46 +0200 (CEST)
Received: from [2.203.68.83] (ip-2-203-68-83.web.vodafone.de [2.203.68.83]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id DE6373B9F; Fri, 28 Jun 2013 08:14:42 +0200 (CEST)
References: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com> <049501ce7356$31644680$942cd380$@augustcellars.com>
In-Reply-To: <049501ce7356$31644680$942cd380$@augustcellars.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <DEE3F4FD-0B7D-49CA-95FC-40741D9C8BED@tzi.org>
X-Mailer: iPad Mail (10B329)
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 28 Jun 2013 08:14:21 +0200
To: Jim Schaad <ietf@augustcellars.com>
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 06:15:52 -0000

Well, we actually like to use AES-CCM in the small devices.
Not having to do AES decrypt is a good thing, indeed.

Sent from my mobile device

On 27.06.2013, at 18:48, "Jim Schaad" <ietf@augustcellars.com> wrote:

> James,
>=20
> The small devices use case does present a reason for wanting to use AES-GC=
M rather than AESKW for this case.  Specifically, there is no need to have s=
ilicon devoted to doing AES decrypt.  All operations can be done just with A=
ES encrypt.
>=20
> jim
>=20
>> -----Original Message-----
>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
>> Manger, James H
>> Sent: Wednesday, June 26, 2013 7:40 PM
>> To: jose@ietf.org
>> Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
>>=20
>> I don't think we should standardize draft-jones-jose-aes-gcm-key-wrap-00.=
 No
>> rationale is apparent. We already have an AES-based key wrap algorithm
>> (A128KW, A256KW), which has a 64-bit size overhead. The AES-GCM key
>> wrap algorithm in this draft add almost no useful properties, but has a 2=
24-bit
>> size overhead.
>>=20
>> I like the concatenation of the IV, ciphertext, and tag byte arrays. But d=
oing
>> this here while content encryption serializes the same values as dot-sepa=
rated
>> B64 blobs does smell of poor ad hoc design. It is nice to highlight how a=

>> previous choice complicates extending JOSE to other algorithms, but only i=
f
>> we then fix that previous choice.
>>=20
>> If the additional authenticated data (AAD) was used to bind the CEK algor=
ithm
>> id (or other context info, as ConcatKDF does) to the wrapped key, then th=
ere
>> would at least be an extra security property that would make this key wra=
p
>> algorithm worth considering. For instance, instead of AAD being empty, AA=
D
>> could be the "key wrap: " + "enc" value.
>>=20
>> By reusing a CEK algorithm as a KEK algorithm, and supporting direct
>> encryption, we substantially increase the risk that an attacker can rearr=
ange
>> some encrypted content so a legitimate recipient treats it as an encrypte=
d key
>> leading to security flaws.
>>=20
>> For example, Alice sends "Start of PIN =3D 8" confidentially to Bob:
>>  {alg:dir,enc:A128GCM,kid:1}..iv.ciphertext.tag
>> An attacker seeing this JOSE message learns nothing about the 1st digit o=
f the
>> PIN.
>> But if the attacker sends 10 messages to Bob for 10 guess of that digit:
>>=20
>> {alg:A128GCMKW,enc:A128GCM,kid:1}.iv|ciphertext|tag.ivN.ciphertextN.tag
>> N
>> where ivN.ciphertextN.tagN are calculated using an AES key of "Start of P=
IN =3D
>> <N>", then 9 messages will cause errors, while 1 message will be accepted=
 --
>> revealing the supposedly confidential information in 10 guesses instead o=
f
>> 2^128.
>>=20
>> Actually the above attack does not quite work for the compact encoding as=

>> AAD is never empty for content encryption. I not certain for the JSON
>> encoding. In any case, an explicit and unambiguous AAD value for key
>> wrapping would be good.
>>=20
>> Finally, a key wrap algorithm like this should go to the IETF crypto grou=
p
>> (CRFG) instead of being invented in JOSE. We have already spent a year
>> unpicking a JOSE-special AEAD algorithm.
>>=20
>> --
>> James Manger
>>=20
>>=20
>>> -----Original Message-----
>>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
>>> Of Jim Schaad
>>> Sent: Wednesday, 26 June 2013 2:53 AM
>>> To: jose@ietf.org
>>> Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
>>>=20
>>> We now have two documents   one from Richard and one from Mike   which
>>> provide the two different ways that have been proposed for doing key
>>> wrapping with an AEAD algorithm.
>>>=20
>>> Please review the two documents and provide comments to the list.
>>>=20
>>> Jim
>>=20
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>=20
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>=20

From ietf@augustcellars.com  Fri Jun 28 12:40:23 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCF521F9BAD for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 12:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oG-JaBxXqpof for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 12:40:17 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 98E2621F9BCF for <jose@ietf.org>; Fri, 28 Jun 2013 12:40:17 -0700 (PDT)
Received: from Philemon (mccpool-66-89.ci.monterey.ca.us [205.155.66.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 84AD638EEA; Fri, 28 Jun 2013 12:40:16 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A1AFC@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1AFC@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 28 Jun 2013 12:39:19 -0700
Message-ID: <05e901ce7437$2f02f7b0$8d08e710$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05EA_01CE73FC.82A7C930"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFaf58+YZiiYzWVV6ccWMZjKm95PQJNBX9KmiEE/HA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Comments on version 11 of draft-ietf-jose-json-web-encryption
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 19:40:23 -0000

This is a multipart message in MIME format.

------=_NextPart_000_05EA_01CE73FC.82A7C930
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Thursday, June 27, 2013 3:50 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

Thanks for the useful review comments, Jim.  Replies inline prefixed by
"Mike>".

 

-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Saturday, June 15, 2013 2:08 PM
To: draft-ietf-jose-json-web-encryption@tools.ietf.org
Cc: jose@ietf.org
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

Gentlemen,

 

Here are a few comments for consideration.  Note that some of the comments
from the JWS review are also applicable to this document as much of the
language in places is the same.

 

1.  In Section 4.1.2 - You probably want to say an AEAD algorithm not an AE
algorithm

 

Mike> The problem with the "AEAD" terminology is that it implies both
algorithm and encoding properties.  We want the algorithm properties but not
the encoding properties defined by RFC 5116.  Thus, a conscious terminology
change was made in -08 to longer use the term "AEAD".

 

[JLS] The term AEAD has nothing to do with the encoding properties defined
in RFC 5116.  AE and AEAD algorithms are very distinct.  One offers only
authenticated encryption and the other adds the associated data.  They are
not to be confused.

 

 

3.  In section 4.1.4 - Does the group agree that compression is a required
feature to implement?

 

Mike> This feature was discussed at IETF 83 and has been in place in the
current form ever since -02.  I'd be shocked if people didn't believe this
feature was necessary.

 

[JLS]  So in your opinion, it is an absolute requirement that my code
implement zip, but not that it implement jwk.  This makes absolutely no
sense to me.  I am not asking if there is a requirement that it be present
in the document.  I am asking if it is a required to implement feature.

 

4.  Why not reference sections 4.1.5 - 10 by reference with a comment that
these refer to the key that was used to encrypt the content?  Is there a
benefit of having them listed here?  Is there a difference in the way they
are interpreted other than the recipient/originator thing?

 

Mike> I assume you mean reference them in JWS?  There's a complete list here
so that it's clear to JWE implementers what the reserved header parameters
are without having to reference other specs.  And yes, the JWS and JWE key
selection parameters are the same other than the JWS sender/JWE receiver
difference.

 

[JLS] That does not make sense to me.  There are lots of times that
referencing other specifications makes a lot of sense.  You certainly be
that this is true when it comes to security considerations.  I believe that
it is equally true here.  I did not say don't list time, I said that you
should reference the sections in the signature draft.

 

5.  Why not reference sections 4.1.11-12 from the JWS document?  Is there a
difference in the way they are interpreted?

 

Mike> (Apparently I didn't understand what you were suggesting in 4, having
seen this next question.)  In any event, in JWS they reference the key that
is used to verify the signature.  In JWE they reference the key to which the
content was encrypted.  That's the difference in all these parameters.

 

6.  If we are not going with an alphabetic order of names, the I would
suggest that apu should be next to exp as they are used in the same context
and therefore having them adjacent makes sense.

 

Mike> Actually, Richard had suggested moving "apu" to the key agreement
section in JWA, since its use is algorithm-specific.  I think I agree with
him.

 

[JLS] that's a fine approach as well.

 

7.  Is there a reason not to reference 4.1.14 from JWS?  Is there a
difference in interpretation?

 

Mike> Stylistically, it seems easier for implementers of JWE to have a
complete list of general-purpose parameter definitions than to have some
here and some there.  The example is also different, because one is a JWS
header and the other is a JWE header.

 

 

                                                                Thanks
again,

                                                                -- Mike

 

Jim

 

 


------=_NextPart_000_05EA_01CE73FC.82A7C930
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Thursday, June 27, 2013 3:50 PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> RE: Comments on version 11 of =
draft-ietf-jose-json-web-encryption<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Thanks =
for the useful review comments, Jim.&nbsp; Replies inline prefixed by =
&#8220;<span =
style=3D'color:#0070C0'>Mike&gt;</span>&#8221;&#8230;<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br>Sent: Saturday, June 15, 2013 2:08 PM<br>To: <a =
href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">draft-=
ietf-jose-json-web-encryption@tools.ietf.org</a><br>Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>Subject: Comments on =
version 11 of draft-ietf-jose-json-web-encryption<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Gentlemen,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Here =
are a few comments for consideration.&nbsp; Note that some of the =
comments from the JWS review are also applicable to this document as =
much of the language in places is the same.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>1.&nbsp; In Section 4.1.2 - You probably want to =
say an AEAD algorithm not an AE algorithm<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; The problem =
with the &#8220;AEAD&#8221; terminology is that it implies both =
algorithm and encoding properties.&nbsp; We want the algorithm =
properties but not the encoding properties defined by RFC 5116.&nbsp; =
Thus, a conscious terminology change was made in -08 to longer use the =
term &#8220;AEAD&#8221;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] The term AEAD =
has nothing to do with the encoding properties defined in RFC =
5116.&nbsp; AE and AEAD algorithms are very distinct.&nbsp; One offers =
only authenticated encryption and the other adds the associated data. =
&nbsp;They are not to be confused.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>3.&nbsp; In section 4.1.4 - Does the group agree =
that compression is a required feature to implement?<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; This feature =
was discussed at IETF 83 and has been in place in the current form ever =
since -02.&nbsp; I&#8217;d be shocked if people didn&#8217;t believe =
this feature was necessary.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] &nbsp;So in =
your opinion, it is an absolute requirement that my code implement zip, =
but not that it implement jwk.&nbsp; This makes absolutely no sense to =
me.&nbsp; I am not asking if there is a requirement that it be present =
in the document.&nbsp; I am asking if it is a required to implement =
feature.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>4.&nbsp; Why not reference sections 4.1.5 - 10 by =
reference with a comment that these refer to the key that was used to =
encrypt the content?&nbsp; Is there a benefit of having them listed =
here?&nbsp; Is there a difference in the way they are interpreted other =
than the recipient/originator thing?<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I assume you =
mean reference them in JWS?&nbsp; There&#8217;s a complete list here so =
that it&#8217;s clear to JWE implementers what the reserved header =
parameters are without having to reference other specs.&nbsp; And yes, =
the JWS and JWE key selection parameters are the same other than the JWS =
sender/JWE receiver difference.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] That does not =
make sense to me.&nbsp; There are lots of times that referencing other =
specifications makes a lot of sense. &nbsp;You certainly be that this is =
true when it comes to security considerations.&nbsp; I believe that it =
is equally true here.&nbsp; I did not say don&#8217;t list time, I said =
that you should reference the sections in the signature =
draft.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>5.&nbsp; Why not reference sections 4.1.11-12 from =
the JWS document?&nbsp; Is there a difference in the way they are =
interpreted?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; (Apparently =
I didn&#8217;t understand what you were suggesting in 4, having seen =
this next question.)&nbsp; In any event, in JWS they reference the key =
that is used to verify the signature.&nbsp; In JWE they reference the =
key to which the content was encrypted.&nbsp; That&#8217;s the =
difference in all these parameters.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>6.&nbsp; If we are not going with an alphabetic =
order of names, the I would suggest that apu should be next to exp as =
they are used in the same context and therefore having them adjacent =
makes sense.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Actually, =
Richard had suggested moving &#8220;apu&#8221; to the key agreement =
section in JWA, since its use is algorithm-specific.&nbsp; I think I =
agree with him.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] that&#8217;s a =
fine approach as well.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>7.&nbsp; Is there a reason not to reference 4.1.14 =
from JWS?&nbsp; Is there a difference in =
interpretation?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; =
Stylistically, it seems easier for implementers of JWE to have a =
complete list of general-purpose parameter definitions than to have some =
here and some there.&nbsp; The example is also different, because one is =
a JWS header and the other is a JWE header.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks =
again,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Jim<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_05EA_01CE73FC.82A7C930--


From rlb@ipv.sx  Fri Jun 28 15:53:11 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8595E21F9CE3 for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 15:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.976
X-Spam-Level: 
X-Spam-Status: No, score=-4.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxO+eenknR1d for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 15:53:03 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1224021F9CBC for <jose@ietf.org>; Fri, 28 Jun 2013 15:53:02 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wo10so2519751obc.3 for <jose@ietf.org>; Fri, 28 Jun 2013 15:52:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=6IcN61G/G6stwl42tfJPd7N4Y9STq3zOprttubnfmOY=; b=TArF4SN6tmXdPjy2WpdXGPhgyQeK51W0sMoR0/tMitY3vC0OCHbUJQeNYe4uthBtrF 8LzJzJpKxTi3Ttw48Xlyaj2YCc/qbttk0ohUeK3PnX5H7bK0GfmaxUI2fWCJfcFNZ+38 trrf1ummJ9jKJnfgb6d8caD6bFYZRo6/R9coI/NePeGcRc3ClwAGjDycLeJUv7pBvCYZ 1YSUjkEbWSmH/4J7Eri+uqHtYIG/ANa0dLdn6GDySfA0b1K384cWRiQLt/0BtDq4tnFk /4GrCAIf1h0NiqOkUJ5fLRqOQIHHzKH+DN0Qp2vPXfTVEFa6HTUosDlBysFXmY3yPKwQ pISg==
MIME-Version: 1.0
X-Received: by 10.60.103.211 with SMTP id fy19mr6033923oeb.103.1372459975185;  Fri, 28 Jun 2013 15:52:55 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Fri, 28 Jun 2013 15:52:55 -0700 (PDT)
X-Originating-IP: [128.89.255.96]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943678A1F0A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 28 Jun 2013 18:52:55 -0400
Message-ID: <CAL02cgRJYB23OwFMT84wZuH+ddjtSh2x0+wXQMfz_+aZ8dtLYg@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e0115e85e4a27dc04e03ebd87
X-Gm-Message-State: ALoCoQnydFfkxFOcoXkaJC+YMTI4oUhGXzMXY8IQNaVomschBRy1YCr6Jin354TQ02gUuYxgBn3w
Cc: Jim Schaad <ietf@augustcellars.com>, n-sakimura <n-sakimura@nri.co.jp>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 22:53:11 -0000

--089e0115e85e4a27dc04e03ebd87
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 27, 2013 at 7:16 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Even if we chose to support an unencoded payload representation as an
> option for the JSON Serialization (which I=92m not advocating), having th=
is
> be the default would be the wrong thing for two reasons:****
>
> ** **
>
> 1.  It won=92t work for the Compact Serialization, since it doesn=92t ens=
ure
> that the representation is URL-safe.  The default should work for both
> serializations.
>

It does work for the compact serialization; you just declare that the
default for the compact serialization is "b64": true.  That is, you declare
the compact serialization equivalent to the following JSON object:

{
  "unprotected": { "b64": true },
  "protected": /* JWS Protected Header */,
  "payload": /* JWS Payload */,
  "signature": /* JWS Signature */
}



> 2.  It assumes a special case (a payload that can be represented as a
> transport-invariant JSON string), which will often not work.  The default
> should be the general case, which always works.
>

It assumes that the protected content can be represented as a UTF-8 string.
 Which is true of some large fraction of the traffic on the Internet.


> As for your suggestion to not use the base64url encoded payload in the
> signature computation, this seems to me like an attempt to reopen
> http://trac.tools.ietf.org/wg/jose/trac/ticket/23 (Make crypto
> independent of binary encoding (base64)) by another means, despite it
> already being resolved as =93Won=92t Fix=94.  I don=92t believe that cons=
tantly
> trying to revisit closed issues is a productive activity, nor respectful =
of
> the working group=92s time, so I therefore request that you let that one =
go.
>

That was closed because the proposed solution would have broken legacy
code.  The current proposal does not, because it only changes the process
when there is no protected header, which can only happen in the JSON
serialization.  You're trying to inflict the limitations of the compact
format on the JSON format.

--Richard



> ****
>
> ** **
>
>                                                                 Sincerely=
,
> ****
>
>                                                                 -- Mike**=
*
> *
>
> ** **
>
> *From:* Richard Barnes [mailto:rlb@ipv.sx]
> *Sent:* Thursday, June 27, 2013 3:24 PM
> *To:* Jim Schaad
> *Cc:* Mike Jones; n-sakimura; jose@ietf.org;
> draft-ietf-jose-json-web-signature@tools.ietf.org
>
> *Subject:* Re: [jose] #26: Allow for signature payload to not be base64
> encoded****
>
> ** **
>
> I think there are two separable issues here, both of which Mike and I
> probably have divergent opinions on :)****
>
> 1. Syntax: Should it be possible for the "payload" field JWS to be a JSON
> string (instead of base64) when the payload is simply a UTF-8 string?****
>
> 2. Crypto: Must the JWS Signing Input be base64url encoded.****
>
> ** **
>
> The current answers to these questions are:****
>
> 1. It is not possible.  Payload is always base64url encoded.****
>
> 2. It is always base64url encoded.****
>
> ** **
>
> The answers should be:****
>
> 1. The payload should not be base64url encoded unless it cannot be
> represented as a JSON string.****
>
> 2. The JWS Signing Input should not be base64url encoded unless there is =
a
> JWS Protected Header****
>
> ** **
>
> Neither of these are complicated changes:****
>
> 1. Add a "b64" header parameter that indicates that the payload is
> base64url-encoded binary, as opposed to a UTF-8 string.  Specify that thi=
s
> parameter is on by default in compact-formatted JWS objects.****
>
> 2. Modify the signing/verification instructions to switch based on the
> presence of a JWS Protected Header: "If the JWS Protected Header is absen=
t
> or empty, then the JWS Signing Input is simply the JWS Payload (not
> encoded).  If the JWS Protected Header has a non-empty value, then the th=
e
> JWS Signing Input is the concatenation of the Encoded JWS Header, a perio=
d
> ('.') character, and the Encoded JWS Payload"****
>
> ** **
>
> There are two reasons for these, both of which are important to make sure
> that this spec is applicable to a broad variety of use cases:****
>
> 1. Compactness.  As Jim notes, quoted strings are shorter than
> base64url-encoded strings****
>
> 2. Crypto-compatibility: Avoiding base64-encoding means that there's
> nothing JWS-specific about the signature value.  So for example, you coul=
d
> translate a JWS with no protected attributes to a CMS SignedData object
> with no protected attributes.****
>
> ** **
>
> This email brought to you by the number 2 and the letters J, W, and S :)*=
*
> **
>
> ** **
>
> --Richard****
>
> ** **
>
> [1] Note that the default value for this header must be false, or else yo=
u
> lose the compactness advantage!****
>
> [2] You could also do this as a "Content-Encoding" equivalent, "cenc":
> "b64".  That would give you "base64 agility", as some folks have asked fo=
r,
> since you could have "b64" and "b64u" values.  ****
>
> [3] You could also do this like CMS, and have the JWS Signing Input in th=
e
> latter case be "the concatenation of the Encoded JWS Header, a period ('.=
')
> character, and the Encoded JWS Payload Hash".  Where the Encoded JWS
> Payload Hash is the base64url-encoded version of the hash you would
> otherwise be signing.  This seems simpler to code, since you just digest
> the body, then if there's a protected header, you digest again.  But it
> also breaks with existing code.   ****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad <ietf@augustcellars.com>
> wrote:****
>
> No, my motivation is to allow for a smaller version of the payload string=
.
>  In some cases quoting it will generate a smaller string than doing the
> base64 conversion on the string.****
>
>
>
>
> > -----Original Message-----
> > From: Mike Jones [mailto:Michael.Jones@microsoft.com]****
>
> > Sent: Thursday, June 27, 2013 9:49 AM
> > To: Jim Schaad; 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Jim, you wrote "If I am not transporting the base64url encoded content,
> > because it is not in the "payload" field, then why should I need to
> base64
> > encode it just to validate the signature.  This is the alto case."
> >
> > So am I correct then, in thinking that your motivation for #26 is
> actually #25 -
> > Detached content for the ALTO use case?  As John and Nat had written,
> this
> > could be handled by the specs as they are today by signing a hash of th=
e
> > detached content and including a compact JWS representing that signatur=
e
> as
> > an x-alto-signature header.  That doesn't require changing the signatur=
e
> > calculation.
> >
> >                               -- Mike
> >
> > -----Original Message-----
> > From: Jim Schaad [mailto:ietf@augustcellars.com]
> > Sent: Thursday, June 27, 2013 9:41 AM
> > To: 'n-sakimura'
> > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones;
> > jose@ietf.org
> > Subject: RE: [jose] #26: Allow for signature payload to not be base64
> encoded
> >
> > Nat,
> >
> > The only thing that can be signed or encrypted is an octet string. (A
> slight over
> > generalization. GOST for example hashes an integer, tree hashes can do
> > strange things but a sufficiently true statement for our purposes.)
> >
> > A that being said - yes case 1 would be something you can do.  Case #2
> would
> > not be something that you can do because it is not an octet string.
> >
> > If you are looking at JavaScript, in order to hash something as an octe=
t
> string it
> > can be one of three things.  A UInt8Array, an Int8Array and, due to
> > convention, a string where the top byte of all of the code points in th=
e
> string is
> > zero.
> >
> > We currently don't have an efficient way to encode the Uint8Array case,
> > although that might not be true if we are looking at new ECMA
> specifications
> > which apparently are adding more defined types and serialization method=
s
> for
> > those types.
> >
> > > -----Original Message-----
> > > From: n-sakimura [mailto:n-sakimura@nri.co.jp]
> > > Sent: Wednesday, June 26, 2013 7:55 PM
> > > To: Jim Schaad
> > > Cc: draft-ietf-jose-json-web-signature@tools.ietf.org;
> > > michael.jones@microsoft.com; jose@ietf.org
> > > Subject: Re: [jose] #26: Allow for signature payload to not be base64
> > > encoded
> > >
> > > Let me understand the problem.
> > >
> > > Are you suggesting that we should be able to do something like:
> > >
> > > Case 1:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>=
",
> > >        "payload":"this is a multi\nline text payload of which a line
> > > can be very very very long and wrapped during transmission. "
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > or even
> > >
> > > Case 2:
> > >
> > >       {"protected":<integrity-protected shared header contents>",
> > >        "unprotected":<non-integrity-protected shared header contents>=
",
> > >        "payload":{
> > >     "this":"is a json",
> > >     "payload":"which is not base64url encoded"
> > >        }
> > >        "signatures":[
> > >         {"header":"<per-signature unprotected header 1 contents>",
> > >          "signature":"<signature 1 contents>"},
> > >         ...
> > >         {"header":"<per-signature unprotected header N contents>",
> > >          "signature":"<signature N contents>"}],
> > >       }
> > >
> > > Then, I am worried about allowing them because in general we would no=
t
> > > know what would a transmission mechanism and user agents (including
> > > text
> > > editors) would do to them, like Mike mentioned. I do not think we
> > > should assume the property of the transmission mechanism in JOSE leve=
l.
> > > Assuming that would cause brittleness in the implementations.
> > >
> > > For detached signature, I do not understand why you would want non-
> > > base64url encoded payload. The application should define how to hash
> > > the octet stream that it wants to calculate signature over it, and we
> > > can just include the base64url encoded hash in the "payload".
> > > Why would you like to do other encoding for the hash?
> >
> > If I am not transporting the base64url encoded content, because it is
> not in
> > the "payload" field, then why should I need to base64 encode it just to
> > validate the signature.  This is the alto case.
> >
> > Jim
> >
> > >
> > > --
> > > Nat Sakimura (n-sakimura@nri.co.jp)
> > > Nomura Research Institute
> > >
> > > PLEASE READ:
> > > The information contained in this e-mail is confidential and intended
> > > for the named recipient(s) only.
> > > If you are not an intended recipient of this e-mail, you are hereby
> > > notified that any review, dissemination, distribution or duplication
> > > of this message is strictly prohibited. If you have received this
> > > message in error, please notify the sender immediately and delete you=
r
> > copy from your system.
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose****
>
> ** **
>

--089e0115e85e4a27dc04e03ebd87
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jun 27, 2013 at 7:16 PM, Mike Jones <span dir=3D"ltr">&lt;<=
a href=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jon=
es@microsoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Even if we chose to suppo=
rt an unencoded payload representation as an option for the JSON Serializat=
ion (which I=92m not advocating), having this be the default
 would be the wrong thing for two reasons:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">1.=A0 It won=92t work for=
 the Compact Serialization, since it doesn=92t ensure that the representati=
on is URL-safe.=A0 The default should work for both serializations.</span><=
/p>
</div></div></blockquote><div><br></div><div>It does work for the compact s=
erialization; you just declare that the default for the compact serializati=
on is &quot;b64&quot;: true. =A0That is, you declare the compact serializat=
ion equivalent to the following JSON object:</div>
<div><br></div><div>{</div><div>=A0 &quot;unprotected&quot;: { &quot;b64&qu=
ot;: true },</div><div>=A0 &quot;protected&quot;: /* JWS Protected Header *=
/,</div><div>=A0 &quot;payload&quot;: /* JWS Payload */,</div><div>=A0 &quo=
t;signature&quot;: /* JWS Signature */</div>
<div>}</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">2.=A0 It assumes a specia=
l case (a payload that can be represented as a transport-invariant JSON str=
ing), which will often not work.=A0 The default should be the
 general case, which always works.</span></p></div></div></blockquote><div>=
<br></div><div>It assumes that the protected content can be represented as =
a UTF-8 string. =A0Which is true of some large fraction of the traffic on t=
he Internet.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"bl=
ue" vlink=3D"purple"><div><p class=3D"MsoNormal"></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">As for your suggestion to=
 not use the base64url encoded payload in the signature computation, this s=
eems to me like an attempt to reopen
<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/23" target=3D"_bl=
ank">http://trac.tools.ietf.org/wg/jose/trac/ticket/23</a> (Make crypto ind=
ependent of binary encoding (base64)) by another means, despite it already =
being resolved as =93Won=92t Fix=94.=A0 I don=92t believe that
 constantly trying to revisit closed issues is a productive activity, nor r=
espectful of the working group=92s time, so I therefore request that you le=
t that one go.</span></p></div></div></blockquote><div><br></div><div>That =
was closed because the proposed solution would have broken legacy code. =A0=
The current proposal does not, because it only changes the process when the=
re is no protected header, which can only happen in the JSON serialization.=
 =A0You&#39;re trying to inflict the limitations of the compact format on t=
he JSON format.</div>
<div><br></div><div>--Richard</div><div><br></div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div=
><p class=3D"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 Sincerely,<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 -- Mike<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Richard =
Barnes [mailto:<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</=
a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:24 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> Mike Jones; n-sakimura; <a href=3D"mailto:jose@ietf.org" target=
=3D"_blank">jose@ietf.org</a>; <a href=3D"mailto:draft-ietf-jose-json-web-s=
ignature@tools.ietf.org" target=3D"_blank">draft-ietf-jose-json-web-signatu=
re@tools.ietf.org</a></span></p>
<div><div class=3D"h5"><br>
<b>Subject:</b> Re: [jose] #26: Allow for signature payload to not be base6=
4 encoded<u></u><u></u></div></div><p></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I think there are two separable issues here, both of=
 which Mike and I probably have divergent opinions on :)<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">1. Syntax: Should it be possible for the &quot;paylo=
ad&quot; field JWS to be a JSON string (instead of base64) when the payload=
 is simply a UTF-8 string?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. Crypto: Must the JWS Signing Input be base64url e=
ncoded.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The current answers to these questions are:<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal">1. It is not possible. =A0Payload is always base64ur=
l encoded.<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">2. It is always base64url encoded.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The answers should be:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1. The payload should not be base64url encoded unles=
s it cannot be represented as a JSON string.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. The JWS Signing Input should not be base64url enc=
oded unless there is a JWS Protected Header<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Neither of these are complicated changes:<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">1. Add a &quot;b64&quot; header parameter that indic=
ates that the payload is base64url-encoded binary, as opposed to a UTF-8 st=
ring. =A0Specify that this parameter is on by default in compact-formatted =
JWS objects.<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">2. Modify the signing/verification instructions to s=
witch based on the presence of a JWS Protected Header: &quot;If the JWS Pro=
tected Header is absent or empty, then the JWS Signing Input is simply the =
JWS Payload (not encoded). =A0If the JWS
 Protected Header has a non-empty value, then the the JWS Signing Input is =
the concatenation of the Encoded JWS Header, a period (&#39;.&#39;) charact=
er, and the Encoded JWS Payload&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">There are two reasons for these, both of which are i=
mportant to make sure that this spec is applicable to a broad variety of us=
e cases:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1. Compactness. =A0As Jim notes, quoted strings are =
shorter than base64url-encoded strings<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. Crypto-compatibility: Avoiding base64-encoding me=
ans that there&#39;s nothing JWS-specific about the signature value. =A0So =
for example, you could translate a JWS with no protected attributes to a CM=
S SignedData object with no protected attributes.<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This email brought to you by the number 2 and the le=
tters J, W, and S :)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--Richard<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[1] Note that the default value for this header must=
 be false, or else you lose the compactness advantage!<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[2] You could also do this as a &quot;Content-Encodi=
ng&quot; equivalent, &quot;cenc&quot;: &quot;b64&quot;. =A0That would give =
you &quot;base64 agility&quot;, as some folks have asked for, since you cou=
ld have &quot;b64&quot; and &quot;b64u&quot; values. =A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal">[3] You could also do this like CMS, and have the JW=
S Signing Input in the latter case be &quot;the concatenation of the Encode=
d JWS Header, a period (&#39;.&#39;) character, and the Encoded JWS Payload=
 Hash&quot;. =A0Where the Encoded JWS Payload Hash is
 the base64url-encoded version of the hash you would otherwise be signing. =
=A0This seems simpler to code, since you just digest the body, then if ther=
e&#39;s a protected header, you digest again. =A0But it also breaks with ex=
isting code. =A0=A0<u></u><u></u></p>

</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 1:11 PM, Jim Schaad &lt;<a h=
ref=3D"mailto:ietf@augustcellars.com" target=3D"_blank">ietf@augustcellars.=
com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">No, my motivation is to allow for a smaller version =
of the payload string. =A0In some cases quoting it will generate a smaller =
string than doing the base64 conversion on the string.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Mike Jones [mailto:<a href=3D"mailto:Michael.Jones@microsoft.com=
" target=3D"_blank">Michael.Jones@microsoft.com</a>]<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&gt; Sent: Thursday, June 27, 2013 9:49 AM<br>
&gt; To: Jim Schaad; &#39;n-sakimura&#39;<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g" target=3D"_blank">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Jim, you wrote &quot;If I am not transporting the base64url encoded co=
ntent,<br>
&gt; because it is not in the &quot;payload&quot; field, then why should I =
need to base64<br>
&gt; encode it just to validate the signature. =A0This is the alto case.&qu=
ot;<br>
&gt;<br>
&gt; So am I correct then, in thinking that your motivation for #26 is actu=
ally #25 -<br>
&gt; Detached content for the ALTO use case? =A0As John and Nat had written=
, this<br>
&gt; could be handled by the specs as they are today by signing a hash of t=
he<br>
&gt; detached content and including a compact JWS representing that signatu=
re as<br>
&gt; an x-alto-signature header. =A0That doesn&#39;t require changing the s=
ignature<br>
&gt; calculation.<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Mike<br=
>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: Jim Schaad [mailto:<a href=3D"mailto:ietf@augustcellars.com" tar=
get=3D"_blank">ietf@augustcellars.com</a>]<br>
&gt; Sent: Thursday, June 27, 2013 9:41 AM<br>
&gt; To: &#39;n-sakimura&#39;<br>
&gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.or=
g" target=3D"_blank">draft-ietf-jose-json-web-signature@tools.ietf.org</a>;=
 Mike Jones;<br>
&gt; <a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><b=
r>
&gt; Subject: RE: [jose] #26: Allow for signature payload to not be base64 =
encoded<br>
&gt;<br>
&gt; Nat,<br>
&gt;<br>
&gt; The only thing that can be signed or encrypted is an octet string. (A =
slight over<br>
&gt; generalization. GOST for example hashes an integer, tree hashes can do=
<br>
&gt; strange things but a sufficiently true statement for our purposes.)<br=
>
&gt;<br>
&gt; A that being said - yes case 1 would be something you can do. =A0Case =
#2 would<br>
&gt; not be something that you can do because it is not an octet string.<br=
>
&gt;<br>
&gt; If you are looking at JavaScript, in order to hash something as an oct=
et string it<br>
&gt; can be one of three things. =A0A UInt8Array, an Int8Array and, due to<=
br>
&gt; convention, a string where the top byte of all of the code points in t=
he string is<br>
&gt; zero.<br>
&gt;<br>
&gt; We currently don&#39;t have an efficient way to encode the Uint8Array =
case,<br>
&gt; although that might not be true if we are looking at new ECMA specific=
ations<br>
&gt; which apparently are adding more defined types and serialization metho=
ds for<br>
&gt; those types.<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: n-sakimura [mailto:<a href=3D"mailto:n-sakimura@nri.co.jp" =
target=3D"_blank">n-sakimura@nri.co.jp</a>]<br>
&gt; &gt; Sent: Wednesday, June 26, 2013 7:55 PM<br>
&gt; &gt; To: Jim Schaad<br>
&gt; &gt; Cc: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ie=
tf.org" target=3D"_blank">draft-ietf-jose-json-web-signature@tools.ietf.org=
</a>;<br>
&gt; &gt; <a href=3D"mailto:michael.jones@microsoft.com" target=3D"_blank">=
michael.jones@microsoft.com</a>;
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
&gt; &gt; Subject: Re: [jose] #26: Allow for signature payload to not be ba=
se64<br>
&gt; &gt; encoded<br>
&gt; &gt;<br>
&gt; &gt; Let me understand the problem.<br>
&gt; &gt;<br>
&gt; &gt; Are you suggesting that we should be able to do something like:<b=
r>
&gt; &gt;<br>
&gt; &gt; Case 1:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:&quot;this is a multi\nline te=
xt payload of which a line<br>
&gt; &gt; can be very very very long and wrapped during transmission. &quot=
;<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; or even<br>
&gt; &gt;<br>
&gt; &gt; Case 2:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 {&quot;protected&quot;:&lt;integrity-protected shared=
 header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;unprotected&quot;:&lt;non-integrity-protecte=
d shared header contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;payload&quot;:{<br>
&gt; &gt; =A0 =A0 &quot;this&quot;:&quot;is a json&quot;,<br>
&gt; &gt; =A0 =A0 &quot;payload&quot;:&quot;which is not base64url encoded&=
quot;<br>
&gt; &gt; =A0 =A0 =A0 =A0}<br>
&gt; &gt; =A0 =A0 =A0 =A0&quot;signatures&quot;:[<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header 1 contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature 1 co=
ntents&gt;&quot;},<br>
&gt; &gt; =A0 =A0 =A0 =A0 ...<br>
&gt; &gt; =A0 =A0 =A0 =A0 {&quot;header&quot;:&quot;&lt;per-signature unpro=
tected header N contents&gt;&quot;,<br>
&gt; &gt; =A0 =A0 =A0 =A0 =A0&quot;signature&quot;:&quot;&lt;signature N co=
ntents&gt;&quot;}],<br>
&gt; &gt; =A0 =A0 =A0 }<br>
&gt; &gt;<br>
&gt; &gt; Then, I am worried about allowing them because in general we woul=
d not<br>
&gt; &gt; know what would a transmission mechanism and user agents (includi=
ng<br>
&gt; &gt; text<br>
&gt; &gt; editors) would do to them, like Mike mentioned. I do not think we=
<br>
&gt; &gt; should assume the property of the transmission mechanism in JOSE =
level.<br>
&gt; &gt; Assuming that would cause brittleness in the implementations.<br>
&gt; &gt;<br>
&gt; &gt; For detached signature, I do not understand why you would want no=
n-<br>
&gt; &gt; base64url encoded payload. The application should define how to h=
ash<br>
&gt; &gt; the octet stream that it wants to calculate signature over it, an=
d we<br>
&gt; &gt; can just include the base64url encoded hash in the &quot;payload&=
quot;.<br>
&gt; &gt; Why would you like to do other encoding for the hash?<br>
&gt;<br>
&gt; If I am not transporting the base64url encoded content, because it is =
not in<br>
&gt; the &quot;payload&quot; field, then why should I need to base64 encode=
 it just to<br>
&gt; validate the signature. =A0This is the alto case.<br>
&gt;<br>
&gt; Jim<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Nat Sakimura (<a href=3D"mailto:n-sakimura@nri.co.jp" target=3D"_=
blank">n-sakimura@nri.co.jp</a>)<br>
&gt; &gt; Nomura Research Institute<br>
&gt; &gt;<br>
&gt; &gt; PLEASE READ:<br>
&gt; &gt; The information contained in this e-mail is confidential and inte=
nded<br>
&gt; &gt; for the named recipient(s) only.<br>
&gt; &gt; If you are not an intended recipient of this e-mail, you are here=
by<br>
&gt; &gt; notified that any review, dissemination, distribution or duplicat=
ion<br>
&gt; &gt; of this message is strictly prohibited. If you have received this=
<br>
&gt; &gt; message in error, please notify the sender immediately and delete=
 your<br>
&gt; copy from your system.<br>
<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org" target=3D"_blank">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div></div>

--089e0115e85e4a27dc04e03ebd87--

From rlb@ipv.sx  Fri Jun 28 15:57:54 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C6221F9D55 for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 15:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.976
X-Spam-Level: 
X-Spam-Status: No, score=-3.976 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVXodb4a18Os for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 15:57:48 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id AFD1721F9D41 for <jose@ietf.org>; Fri, 28 Jun 2013 15:57:48 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j1so2943885oag.32 for <jose@ietf.org>; Fri, 28 Jun 2013 15:57:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=FgKQ3kUD1oUgB9TzOrdWfKATcz4Ey0+X8aaZQeUNPyE=; b=MqOnO04V4tArV1ohr391EwEdFgpo5I3oevq2H+ANVOCHYDMgae4gst0aqKveOIuBhO qOLvCVRop+ynQblxddYeGursmrofewuVmdpGVn4yNzb7plOXRFIHEdjPEgRxBpRO9ogv FLHdw4vk1DWrIbUXKeK5xycwuKbmAP9iuNsUMFXLU+5gHoyqcZiVwKdGkwVHS8gGGYgP krO5b5WKMZyrw3xoPrNhADMYWmioNnQZ4R6C3BHpQ0EsNodLFCRN35MIRAhD8zyR0Ltn mhOGndpZj5uDWMmibHNZJh7mo96V7YOsv+i35no4MYixatRHxt5U5dUrmjP0H0bDdbGX 8XKg==
MIME-Version: 1.0
X-Received: by 10.182.142.104 with SMTP id rv8mr7344965obb.3.1372460268234; Fri, 28 Jun 2013 15:57:48 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Fri, 28 Jun 2013 15:57:48 -0700 (PDT)
X-Originating-IP: [128.89.255.96]
In-Reply-To: <CAD9ie-sZ+w_HADMTnnkTC8XRJmjZvwYOmA+AhvJGTNPhhK=Z4g@mail.gmail.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <CAD9ie-sZ+w_HADMTnnkTC8XRJmjZvwYOmA+AhvJGTNPhhK=Z4g@mail.gmail.com>
Date: Fri, 28 Jun 2013 18:57:48 -0400
Message-ID: <CAL02cgQbAQ8zhumdR_uvXjhbZM0iXpfPnmgcJrMUuh4+bj11NA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Dick Hardt <dick.hardt@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2eaaec1bf2d04e03ece82
X-Gm-Message-State: ALoCoQmY7Mckp464EFiFIpfgHw3d/hOtwA2H2wZpn6Qcmew/4pgV9zqxqmau/ZEsHA7xYl2taRDC
Cc: Jim Schaad <ietf@augustcellars.com>, n-sakimura <n-sakimura@nri.co.jp>, Mike Jones <Michael.Jones@microsoft.com>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 22:57:54 -0000

--001a11c2eaaec1bf2d04e03ece82
Content-Type: text/plain; charset=ISO-8859-1

Hey Dick,

I guess I should have been clearer that I was only talking about the JSON
serialization.  My proposed change would have no impact on the compact
serialization.  Hopefully that answers your questions about separators,
etc.; they payload would just be a normal JSON string.

--Richard


On Thu, Jun 27, 2013 at 7:56 PM, Dick Hardt <dick.hardt@gmail.com> wrote:

>
>
>
> On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> I think there are two separable issues here, both of which Mike and I
>> probably have divergent opinions on :)
>> 1. Syntax: Should it be possible for the "payload" field JWS to be a JSON
>> string (instead of base64) when the payload is simply a UTF-8 string?
>>
>
> One of the goals of the token was that it not require encoding for it to
> be transported in a request. IE that it be safe and SIMPLE to include in an
> HTTP header or in a URL
>
>
>> 2. Crypto: Must the JWS Signing Input be base64url encoded.
>>
>> The current answers to these questions are:
>> 1. It is not possible.  Payload is always base64url encoded.
>> 2. It is always base64url encoded.
>>
>> The answers should be:
>> 1. The payload should not be base64url encoded unless it cannot be
>> represented as a JSON string.
>>
>
> How does an implementation determine which parts are separated? Are '.'
> escaped? Does the implementation need to parse the JSON to determine a
> valid separator? How does it know the end of the JSON? That sounds really
> hard to implement, or I am misunderstanding what you are proposing.
>
>
>
>> 2. The JWS Signing Input should not be base64url encoded unless there is
>> a JWS Protected Header
>>
>> Neither of these are complicated changes:
>> 1. Add a "b64" header parameter that indicates that the payload is
>> base64url-encoded binary, as opposed to a UTF-8 string.  Specify that this
>> parameter is on by default in compact-formatted JWS objects.
>>
>
> And how is the header separated from the payload?
>
>
>>  2. Modify the signing/verification instructions to switch based on the
>> presence of a JWS Protected Header: "If the JWS Protected Header is absent
>> or empty, then the JWS Signing Input is simply the JWS Payload (not
>> encoded).  If the JWS Protected Header has a non-empty value, then the the
>> JWS Signing Input is the concatenation of the Encoded JWS Header, a period
>> ('.') character, and the Encoded JWS Payload"
>>
>> There are two reasons for these, both of which are important to make sure
>> that this spec is applicable to a broad variety of use cases:
>> 1. Compactness.  As Jim notes, quoted strings are shorter than
>> base64url-encoded strings
>>
>
> The tokens are already compact enough.
>
>
>>  2. Crypto-compatibility: Avoiding base64-encoding means that there's
>> nothing JWS-specific about the signature value.  So for example, you could
>> translate a JWS with no protected attributes to a CMS SignedData object
>> with no protected attributes.
>>
>
> Not a useful feature from my point of view.
>
> -- Dick
>

--001a11c2eaaec1bf2d04e03ece82
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Dick,<div><br></div><div>I guess I should have been cl=
earer that I was only talking about the JSON serialization. =A0My proposed =
change would have no impact on the compact serialization. =A0Hopefully that=
 answers your questions about separators, etc.; they payload would just be =
a normal JSON string.</div>
<div><br></div><div>--Richard</div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Thu, Jun 27, 2013 at 7:56 PM, Dick Hardt <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick=
.hardt@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote"><div class=3D"im">On Thu, Jun 27, 20=
13 at 3:24 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@i=
pv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I think there are two separ=
able issues here, both of which Mike and I probably have divergent opinions=
 on :)<div>


1. Syntax: Should it be possible for the &quot;payload&quot; field JWS to b=
e a JSON string (instead of base64) when the payload is simply a UTF-8 stri=
ng?</div></div></blockquote><div><br></div></div><div>One of the goals of t=
he token was that it not require encoding for it to be transported in a req=
uest. IE that it be safe and SIMPLE to include in an HTTP header or in a UR=
L</div>
<div class=3D"im">

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">
<div>2. Crypto: Must the JWS Signing Input be base64url encoded.</div><div>=
<br></div><div>The current answers to these questions are:</div><div>1. It =
is not possible. =A0Payload is always base64url encoded.</div><div><div>


2. It is always base64url encoded.</div>
<div><br></div><div>The answers should be:</div><div>1. The payload should =
not be base64url encoded unless it cannot be represented as a JSON string.<=
/div></div></div></blockquote><div><br></div></div><div>How does an impleme=
ntation determine which parts are separated? Are &#39;.&#39; escaped? Does =
the implementation need to parse the JSON to determine a valid separator? H=
ow does it know the end of the JSON? That sounds really hard to implement, =
or I am misunderstanding what you are proposing.</div>
<div class=3D"im">

<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div><div>2. The JWS Signing Input should not be base64url encoded unless=
 there is a JWS Protected Header</div>



<div><br></div><div>Neither of these are complicated changes:<br></div><div=
>1. Add a &quot;b64&quot; header parameter that indicates that the payload =
is base64url-encoded binary, as opposed to a UTF-8 string. =A0Specify that =
this parameter is on by default in compact-formatted JWS objects.</div>


</div></div></blockquote><div><br></div></div><div>And how is the header se=
parated from the payload?</div><div class=3D"im"><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">

<div dir=3D"ltr">
<div>
<div>2. Modify the signing/verification instructions to switch based on the=
 presence of a JWS Protected Header: &quot;If the JWS Protected Header is a=
bsent or empty, then the JWS Signing Input is simply the JWS Payload (not e=
ncoded). =A0If the JWS Protected Header has a non-empty value, then the the=
 JWS Signing Input is the concatenation of the Encoded JWS Header, a period=
 (&#39;.&#39;) character, and the Encoded JWS Payload&quot;</div>



<div><br></div><div>There are two reasons for these, both of which are impo=
rtant to make sure that this spec is applicable to a broad variety of use c=
ases:</div><div>1. Compactness. =A0As Jim notes, quoted strings are shorter=
 than base64url-encoded strings</div>


</div></div></blockquote><div><br></div></div><div>The tokens are already c=
ompact enough.</div><div class=3D"im"><div>=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<div dir=3D"ltr">

<div>
<div>2. Crypto-compatibility: Avoiding base64-encoding means that there&#39=
;s nothing JWS-specific about the signature value. =A0So for example, you c=
ould translate a JWS with no protected attributes to a CMS SignedData objec=
t with no protected attributes.</div>


</div></div></blockquote><div><br></div></div><div>Not a useful feature fro=
m my point of view.</div><span class=3D"HOEnZb"><font color=3D"#888888"><di=
v><br></div><div>-- Dick</div></font></span></div></div></div>
</blockquote></div><br></div></div>

--001a11c2eaaec1bf2d04e03ece82--

From dick.hardt@gmail.com  Fri Jun 28 16:04:48 2013
Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10EE21F9D27 for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 16:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SOHu4FHW-1K for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 16:04:48 -0700 (PDT)
Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE0921F9D23 for <jose@ietf.org>; Fri, 28 Jun 2013 16:04:47 -0700 (PDT)
Received: by mail-bk0-f41.google.com with SMTP id jc3so982736bkc.0 for <jose@ietf.org>; Fri, 28 Jun 2013 16:04:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+44SwIopOA7nqvlWn01dlhE6VgLfCaiuF3fDsSxELKY=; b=nYkBDKGnTT/P6BYFqWWOOssL0NRsQnhAPxIwrczbfchrXKmKKZVKt+iAsKreEEBK5c V41j54BuwYVrPAT9hU3DLHXdZ8kRk4HIwbfx369hrdTpUuc2MIU/7wcOUURT7G2Laocl 8IZXE5zndCbdchyBUvYe1HZSicYY82Yd1vhLZPW6mKNdc0oMt1ehHA0oGjbChJzTRXXz vViQFH6ABU4bboDl+jnB9CyXvP7wkpkjp8YMT0Zm76Qt7PkRVTPvUu5jFzOiae0DEiPx 6TnDUL83VdIxyilvrZWlIU0rFh/cV3PgZOHnZmzA7mYruPseFS6QldfB16qLD5HuroaF WB6Q==
X-Received: by 10.204.77.72 with SMTP id f8mr2039618bkk.28.1372460686525; Fri, 28 Jun 2013 16:04:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.205.133.75 with HTTP; Fri, 28 Jun 2013 16:04:26 -0700 (PDT)
In-Reply-To: <CAL02cgQbAQ8zhumdR_uvXjhbZM0iXpfPnmgcJrMUuh4+bj11NA@mail.gmail.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <CAD9ie-sZ+w_HADMTnnkTC8XRJmjZvwYOmA+AhvJGTNPhhK=Z4g@mail.gmail.com> <CAL02cgQbAQ8zhumdR_uvXjhbZM0iXpfPnmgcJrMUuh4+bj11NA@mail.gmail.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Fri, 28 Jun 2013 16:04:26 -0700
Message-ID: <CAD9ie-sBGnv5QbjFeQiXiMJ0Git06LPsAkoNeN7KZxRNqukv3w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=047d7bb70b60b07d1404e03ee7df
Cc: Jim Schaad <ietf@augustcellars.com>, n-sakimura <n-sakimura@nri.co.jp>, Mike Jones <Michael.Jones@microsoft.com>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 23:04:48 -0000

--047d7bb70b60b07d1404e03ee7df
Content-Type: text/plain; charset=ISO-8859-1

Hi Richard, that helps.

Our you looking at a way of effectively signing a JSON payload? A complete,
real world example would help alot.


On Fri, Jun 28, 2013 at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:

> Hey Dick,
>
> I guess I should have been clearer that I was only talking about the JSON
> serialization.  My proposed change would have no impact on the compact
> serialization.  Hopefully that answers your questions about separators,
> etc.; they payload would just be a normal JSON string.
>
> --Richard
>
>
> On Thu, Jun 27, 2013 at 7:56 PM, Dick Hardt <dick.hardt@gmail.com> wrote:
>
>>
>>
>>
>> On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes <rlb@ipv.sx> wrote:
>>
>>> I think there are two separable issues here, both of which Mike and I
>>> probably have divergent opinions on :)
>>> 1. Syntax: Should it be possible for the "payload" field JWS to be a
>>> JSON string (instead of base64) when the payload is simply a UTF-8 string?
>>>
>>
>> One of the goals of the token was that it not require encoding for it to
>> be transported in a request. IE that it be safe and SIMPLE to include in an
>> HTTP header or in a URL
>>
>>
>>> 2. Crypto: Must the JWS Signing Input be base64url encoded.
>>>
>>> The current answers to these questions are:
>>> 1. It is not possible.  Payload is always base64url encoded.
>>> 2. It is always base64url encoded.
>>>
>>> The answers should be:
>>> 1. The payload should not be base64url encoded unless it cannot be
>>> represented as a JSON string.
>>>
>>
>> How does an implementation determine which parts are separated? Are '.'
>> escaped? Does the implementation need to parse the JSON to determine a
>> valid separator? How does it know the end of the JSON? That sounds really
>> hard to implement, or I am misunderstanding what you are proposing.
>>
>>
>>
>>> 2. The JWS Signing Input should not be base64url encoded unless there is
>>> a JWS Protected Header
>>>
>>> Neither of these are complicated changes:
>>> 1. Add a "b64" header parameter that indicates that the payload is
>>> base64url-encoded binary, as opposed to a UTF-8 string.  Specify that this
>>> parameter is on by default in compact-formatted JWS objects.
>>>
>>
>> And how is the header separated from the payload?
>>
>>
>>>  2. Modify the signing/verification instructions to switch based on the
>>> presence of a JWS Protected Header: "If the JWS Protected Header is absent
>>> or empty, then the JWS Signing Input is simply the JWS Payload (not
>>> encoded).  If the JWS Protected Header has a non-empty value, then the the
>>> JWS Signing Input is the concatenation of the Encoded JWS Header, a period
>>> ('.') character, and the Encoded JWS Payload"
>>>
>>> There are two reasons for these, both of which are important to make
>>> sure that this spec is applicable to a broad variety of use cases:
>>> 1. Compactness.  As Jim notes, quoted strings are shorter than
>>> base64url-encoded strings
>>>
>>
>> The tokens are already compact enough.
>>
>>
>>>  2. Crypto-compatibility: Avoiding base64-encoding means that there's
>>> nothing JWS-specific about the signature value.  So for example, you could
>>> translate a JWS with no protected attributes to a CMS SignedData object
>>> with no protected attributes.
>>>
>>
>> Not a useful feature from my point of view.
>>
>> -- Dick
>>
>
>

--047d7bb70b60b07d1404e03ee7df
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Richard, that helps.=A0<div><br></div><div>Our you look=
ing at a way of effectively signing a JSON payload? A complete, real world =
example would help alot.</div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">

On Fri, Jun 28, 2013 at 3:57 PM, Richard Barnes <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr">Hey Dick,<div><br></div><div>I guess I should have been cl=
earer that I was only talking about the JSON serialization. =A0My proposed =
change would have no impact on the compact serialization. =A0Hopefully that=
 answers your questions about separators, etc.; they payload would just be =
a normal JSON string.</div>

<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>--Richard</div></font></span><div><div class=3D"h5"><di=
v class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Jun 27, =
2013 at 7:56 PM, Dick Hardt <span dir=3D"ltr">&lt;<a href=3D"mailto:dick.ha=
rdt@gmail.com" target=3D"_blank">dick.hardt@gmail.com</a>&gt;</span> wrote:=
<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote"><div>On Thu, Jun 27, 2013 at 3:24 PM=
, Richard Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<br>




<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I think there are two separ=
able issues here, both of which Mike and I probably have divergent opinions=
 on :)<div>




1. Syntax: Should it be possible for the &quot;payload&quot; field JWS to b=
e a JSON string (instead of base64) when the payload is simply a UTF-8 stri=
ng?</div></div></blockquote><div><br></div></div><div>One of the goals of t=
he token was that it not require encoding for it to be transported in a req=
uest. IE that it be safe and SIMPLE to include in an HTTP header or in a UR=
L</div>


<div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">
<div>2. Crypto: Must the JWS Signing Input be base64url encoded.</div><div>=
<br></div><div>The current answers to these questions are:</div><div>1. It =
is not possible. =A0Payload is always base64url encoded.</div><div><div>




2. It is always base64url encoded.</div>
<div><br></div><div>The answers should be:</div><div>1. The payload should =
not be base64url encoded unless it cannot be represented as a JSON string.<=
/div></div></div></blockquote><div><br></div></div><div>How does an impleme=
ntation determine which parts are separated? Are &#39;.&#39; escaped? Does =
the implementation need to parse the JSON to determine a valid separator? H=
ow does it know the end of the JSON? That sounds really hard to implement, =
or I am misunderstanding what you are proposing.</div>


<div>

<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div><div>2. The JWS Signing Input should not be base64url encoded unless=
 there is a JWS Protected Header</div>





<div><br></div><div>Neither of these are complicated changes:<br></div><div=
>1. Add a &quot;b64&quot; header parameter that indicates that the payload =
is base64url-encoded binary, as opposed to a UTF-8 string. =A0Specify that =
this parameter is on by default in compact-formatted JWS objects.</div>




</div></div></blockquote><div><br></div></div><div>And how is the header se=
parated from the payload?</div><div><div>=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">



<div dir=3D"ltr">
<div>
<div>2. Modify the signing/verification instructions to switch based on the=
 presence of a JWS Protected Header: &quot;If the JWS Protected Header is a=
bsent or empty, then the JWS Signing Input is simply the JWS Payload (not e=
ncoded). =A0If the JWS Protected Header has a non-empty value, then the the=
 JWS Signing Input is the concatenation of the Encoded JWS Header, a period=
 (&#39;.&#39;) character, and the Encoded JWS Payload&quot;</div>





<div><br></div><div>There are two reasons for these, both of which are impo=
rtant to make sure that this spec is applicable to a broad variety of use c=
ases:</div><div>1. Compactness. =A0As Jim notes, quoted strings are shorter=
 than base64url-encoded strings</div>




</div></div></blockquote><div><br></div></div><div>The tokens are already c=
ompact enough.</div><div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">

<div>
<div>2. Crypto-compatibility: Avoiding base64-encoding means that there&#39=
;s nothing JWS-specific about the signature value. =A0So for example, you c=
ould translate a JWS with no protected attributes to a CMS SignedData objec=
t with no protected attributes.</div>




</div></div></blockquote><div><br></div></div><div>Not a useful feature fro=
m my point of view.</div><span><font color=3D"#888888"><div><br></div><div>=
-- Dick</div></font></span></div></div></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>

--047d7bb70b60b07d1404e03ee7df--

From Michael.Jones@microsoft.com  Fri Jun 28 16:46:21 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 548B821F9DB7 for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 16:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcaRQ-I3x0IY for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 16:46:15 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id C43AD21F9DBB for <jose@ietf.org>; Fri, 28 Jun 2013 16:46:14 -0700 (PDT)
Received: from BN1BFFO11FD007.protection.gbl (10.58.52.204) by BN1AFFO11HUB015.protection.gbl (10.58.52.125) with Microsoft SMTP Server (TLS) id 15.0.717.3; Fri, 28 Jun 2013 23:46:12 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD007.mail.protection.outlook.com (10.58.53.67) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Fri, 28 Jun 2013 23:46:12 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Fri, 28 Jun 2013 23:45:22 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>
Thread-Topic: Comments on version 11 of draft-ietf-jose-json-web-encryption
Thread-Index: Ac5qBROwQiVllCE1TESnJHctXErySQJdAyhQAC+DgoAAA443gA==
Date: Fri, 28 Jun 2013 23:45:22 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A83C1@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A1AFC@TK5EX14MBXC283.redmond.corp.microsoft.com> <05e901ce7437$2f02f7b0$8d08e710$@augustcellars.com>
In-Reply-To: <05e901ce7437$2f02f7b0$8d08e710$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.75]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A83C1TK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(377454003)(199002)(51914003)(43784003)(13464003)(76796001)(56776001)(16406001)(81342001)(74366001)(74662001)(79102001)(51856001)(77096001)(512954002)(76786001)(59766001)(55846006)(54356001)(15202345003)(54316002)(6806003)(74502001)(53806001)(46102001)(71186001)(56816003)(19300405004)(77982001)(76482001)(16236675002)(81542001)(31966008)(74876001)(74706001)(47446002)(47736001)(33656001)(4396001)(20776003)(49866001)(83072001)(65816001)(69226001)(66066001)(80022001)(50986001)(63696002)(47976001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB015; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0891BC3F3D
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Comments on version 11 of draft-ietf-jose-json-web-encryption
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 28 Jun 2013 23:46:21 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A83C1TK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Responses inline...

From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Friday, June 28, 2013 12:39 PM
To: Mike Jones
Cc: jose@ietf.org
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption



From: Mike Jones [mailto:Michael.Jones@microsoft.com]
Sent: Thursday, June 27, 2013 3:50 PM
To: Jim Schaad
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption


Thanks for the useful review comments, Jim.  Replies inline prefixed by "Mi=
ke>"...



-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com]
Sent: Saturday, June 15, 2013 2:08 PM
To: draft-ietf-jose-json-web-encryption@tools.ietf.org<mailto:draft-ietf-jo=
se-json-web-encryption@tools.ietf.org>
Cc: jose@ietf.org<mailto:jose@ietf.org>
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption



Gentlemen,



Here are a few comments for consideration.  Note that some of the comments =
from the JWS review are also applicable to this document as much of the lan=
guage in places is the same.



1.  In Section 4.1.2 - You probably want to say an AEAD algorithm not an AE=
 algorithm



Mike> The problem with the "AEAD" terminology is that it implies both algor=
ithm and encoding properties.  We want the algorithm properties but not the=
 encoding properties defined by RFC 5116.  Thus, a conscious terminology ch=
ange was made in -08 to longer use the term "AEAD".



[JLS] The term AEAD has nothing to do with the encoding properties defined =
in RFC 5116.  AE and AEAD algorithms are very distinct.  One offers only au=
thenticated encryption and the other adds the associated data.  They are no=
t to be confused.

Mike> OK - What's a good reference for the term that's not RFC 5116?


3.  In section 4.1.4 - Does the group agree that compression is a required =
feature to implement?



Mike> This feature was discussed at IETF 83 and has been in place in the cu=
rrent form ever since -02.  I'd be shocked if people didn't believe this fe=
ature was necessary.



[JLS]  So in your opinion, it is an absolute requirement that my code imple=
ment zip, but not that it implement jwk.  This makes absolutely no sense to=
 me.  I am not asking if there is a requirement that it be present in the d=
ocument.  I am asking if it is a required to implement feature.



Mike> The rationale for this is that people (Eric Rescorla, I think) though=
t that since "zip" processing changes the ciphertext, that not supporting i=
t would give a weapon to attackers, enabling them to substitute one ciphert=
ext for another.  Since there are security implications in not implementing=
 it, it's MTI.



4.  Why not reference sections 4.1.5 - 10 by reference with a comment that =
these refer to the key that was used to encrypt the content?  Is there a be=
nefit of having them listed here?  Is there a difference in the way they ar=
e interpreted other than the recipient/originator thing?



Mike> I assume you mean reference them in JWS?  There's a complete list her=
e so that it's clear to JWE implementers what the reserved header parameter=
s are without having to reference other specs.  And yes, the JWS and JWE ke=
y selection parameters are the same other than the JWS sender/JWE receiver =
difference.



[JLS] That does not make sense to me.  There are lots of times that referen=
cing other specifications makes a lot of sense.  You certainly be that this=
 is true when it comes to security considerations.  I believe that it is eq=
ually true here.  I did not say don't list time, I said that you should ref=
erence the sections in the signature draft.



Mike> I have no objection to adding a reference saying that related paramet=
er definitions are also contained in JWS 4.1.2 - 4.1.5.



5.  Why not reference sections 4.1.11-12 from the JWS document?  Is there a=
 difference in the way they are interpreted?



Mike> (Apparently I didn't understand what you were suggesting in 4, having=
 seen this next question.)  In any event, in JWS they reference the key tha=
t is used to verify the signature.  In JWE they reference the key to which =
the content was encrypted.  That's the difference in all these parameters.



Mike> I have no objection to adding a reference saying that the related par=
ameter definitions are also contained in JWS 4.1.8 - 4.1.9.



6.  If we are not going with an alphabetic order of names, the I would sugg=
est that apu should be next to exp as they are used in the same context and=
 therefore having them adjacent makes sense.



Mike> Actually, Richard had suggested moving "apu" to the key agreement sec=
tion in JWA, since its use is algorithm-specific.  I think I agree with him=
.



[JLS] that's a fine approach as well.



7.  Is there a reason not to reference 4.1.14 from JWS?  Is there a differe=
nce in interpretation?



Mike> Stylistically, it seems easier for implementers of JWE to have a comp=
lete list of general-purpose parameter definitions than to have some here a=
nd some there.  The example is also different, because one is a JWS header =
and the other is a JWE header.



Mike> I have no objection to adding a reference saying that the related par=
ameter definition is also contained in JWS 4.1.10.







                                                                Thanks agai=
n,

                                                                -- Mike



Jim





--_000_4E1F6AAD24975D4BA5B1680429673943678A83C1TK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Responses inline&#8230=
;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Jim Scha=
ad [mailto:ietf@augustcellars.com]
<br>
<b>Sent:</b> Friday, June 28, 2013 12:39 PM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> jose@ietf.org<br>
<b>Subject:</b> RE: Comments on version 11 of draft-ietf-jose-json-web-encr=
yption<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Mike Jon=
es [<a href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@mic=
rosoft.com</a>]
<br>
<b>Sent:</b> Thursday, June 27, 2013 3:50 PM<br>
<b>To:</b> Jim Schaad<br>
<b>Cc:</b> <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<b>Subject:</b> RE: Comments on version 11 of draft-ietf-jose-json-web-encr=
yption<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks for the useful review comments, Jim.&nbsp;=
 Replies inline prefixed by &#8220;<span style=3D"color:#0070C0">Mike&gt;</=
span>&#8221;&#8230;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: Jim Schaad [<a href=3D"mailto:ietf@augustcellars.com">mailto:ietf@aug=
ustcellars.com</a>]
<br>
Sent: Saturday, June 15, 2013 2:08 PM<br>
To: <a href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">d=
raft-ietf-jose-json-web-encryption@tools.ietf.org</a><br>
Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption<o:p>=
</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Gentlemen,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Here are a few comments for consideration.&nbsp; =
Note that some of the comments from the JWS review are also applicable to t=
his document as much of the language in places is the same.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1.&nbsp; In Section 4.1.2 - You probably want to =
say an AEAD algorithm not an AE algorithm<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; The proble=
m with the &#8220;AEAD&#8221; terminology is that it implies both algorithm=
 and encoding properties.&nbsp; We want the algorithm properties but not th=
e encoding properties defined by RFC 5116.&nbsp; Thus, a conscious
 terminology change was made in -08 to longer use the term &#8220;AEAD&#822=
1;.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D">[JLS] The term AEAD=
 has nothing to do with the encoding properties defined in RFC 5116.&nbsp; =
AE and AEAD algorithms are very distinct.&nbsp; One offers only authenticat=
ed encryption and the other adds the associated
 data. &nbsp;They are not to be confused.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050">Mike&gt; OK &#8211; Wh=
at&#8217;s a good reference for the term that&#8217;s not RFC 5116?<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText">3.&nbsp; In section 4.1.4 - Does the group agree =
that compression is a required feature to implement?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; This featu=
re was discussed at IETF 83 and has been in place in the current form ever =
since -02.&nbsp; I&#8217;d be shocked if people didn&#8217;t believe this f=
eature was necessary.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D">[JLS] &nbsp;So in y=
our opinion, it is an absolute requirement that my code implement zip, but =
not that it implement jwk.&nbsp; This makes absolutely no sense to me.&nbsp=
; I am not asking if there is a requirement that it
 be present in the document.&nbsp; I am asking if it is a required to imple=
ment feature.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050">Mike&gt; The ration=
ale for this is that people (Eric Rescorla, I think) thought that since &#8=
220;zip&#8221; processing changes the ciphertext, that not supporting it wo=
uld give a weapon to attackers, enabling them to substitute
 one ciphertext for another.&nbsp; Since there are security implications in=
 not implementing it, it&#8217;s MTI.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">4.&nbsp; Why not reference sections 4.1.5 - 10 by=
 reference with a comment that these refer to the key that was used to encr=
ypt the content?&nbsp; Is there a benefit of having them listed here?&nbsp;=
 Is there a difference in the way they are interpreted
 other than the recipient/originator thing?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; I assume y=
ou mean reference them in JWS?&nbsp; There&#8217;s a complete list here so =
that it&#8217;s clear to JWE implementers what the reserved header paramete=
rs are without having to reference other specs.&nbsp; And yes,
 the JWS and JWE key selection parameters are the same other than the JWS s=
ender/JWE receiver difference.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D">[JLS] That does not=
 make sense to me.&nbsp; There are lots of times that referencing other spe=
cifications makes a lot of sense. &nbsp;You certainly be that this is true =
when it comes to security considerations.&nbsp; I believe
 that it is equally true here.&nbsp; I did not say don&#8217;t list time, I=
 said that you should reference the sections in the signature draft.<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050">Mike&gt; I have no =
objection to adding a reference saying that related parameter definitions a=
re also contained in JWS 4.1.2 &#8211; 4.1.5.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">5.&nbsp; Why not reference sections 4.1.11-12 fro=
m the JWS document?&nbsp; Is there a difference in the way they are interpr=
eted?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; (Apparentl=
y I didn&#8217;t understand what you were suggesting in 4, having seen this=
 next question.)&nbsp; In any event, in JWS they reference the key that is =
used to verify the signature.&nbsp; In JWE they reference
 the key to which the content was encrypted.&nbsp; That&#8217;s the differe=
nce in all these parameters.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050">Mike&gt; I have no =
objection to adding a reference saying that the related parameter definitio=
ns are also contained in JWS 4.1.8 &#8211; 4.1.9.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">6.&nbsp; If we are not going with an alphabetic o=
rder of names, the I would suggest that apu should be next to exp as they a=
re used in the same context and therefore having them adjacent makes sense.=
<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Actually, =
Richard had suggested moving &#8220;apu&#8221; to the key agreement section=
 in JWA, since its use is algorithm-specific.&nbsp; I think I agree with hi=
m.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D">[JLS] that&#8217;s =
a fine approach as well.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText">7.&nbsp; Is there a reason not to reference 4.1.1=
4 from JWS?&nbsp; Is there a difference in interpretation?<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">Mike&gt; Stylistica=
lly, it seems easier for implementers of JWE to have a complete list of gen=
eral-purpose parameter definitions than to have some here and some there.&n=
bsp; The example is also different, because
 one is a JWS header and the other is a JWE header.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#00B050">Mike&gt; I have no =
objection to adding a reference saying that the related parameter definitio=
n is also contained in JWS 4.1.10.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks again,<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"color:#0070C0">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Jim<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A83C1TK5EX14MBXC283r_--

From ietf@augustcellars.com  Fri Jun 28 20:39:59 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD9E21F9DE4 for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 20:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.979
X-Spam-Level: 
X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYfq+xvD2Y3c for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 20:39:53 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 5160521F9DBA for <jose@ietf.org>; Fri, 28 Jun 2013 20:39:53 -0700 (PDT)
Received: from Philemon (unknown [207.239.114.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id ECC8838EEA; Fri, 28 Jun 2013 20:39:50 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>
References: <010601ce6a0c$6cabe700$4603b500$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A1AFC@TK5EX14MBXC283.redmond.corp.microsoft.com> <05e901ce7437$2f02f7b0$8d08e710$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A83C1@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A83C1@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 28 Jun 2013 20:38:50 -0700
Message-ID: <062201ce747a$2dd02190$897064b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0623_01CE743F.8175B660"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFaf58+YZiiYzWVV6ccWMZjKm95PQJNBX9KAvb5Tw0C4zyt0JnyulfA
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Comments on version 11 of draft-ietf-jose-json-web-encryption
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 03:39:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0623_01CE743F.8175B660
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Friday, June 28, 2013 4:45 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

Responses inline.

 

From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Friday, June 28, 2013 12:39 PM
To: Mike Jones
Cc: jose@ietf.org
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Thursday, June 27, 2013 3:50 PM
To: Jim Schaad
Cc: jose@ietf.org
Subject: RE: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

Thanks for the useful review comments, Jim.  Replies inline prefixed by
"Mike>".

 

-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Saturday, June 15, 2013 2:08 PM
To: draft-ietf-jose-json-web-encryption@tools.ietf.org
Cc: jose@ietf.org
Subject: Comments on version 11 of draft-ietf-jose-json-web-encryption

 

Gentlemen,

 

Here are a few comments for consideration.  Note that some of the comments
from the JWS review are also applicable to this document as much of the
language in places is the same.

 

1.  In Section 4.1.2 - You probably want to say an AEAD algorithm not an AE
algorithm

 

Mike> The problem with the "AEAD" terminology is that it implies both
algorithm and encoding properties.  We want the algorithm properties but not
the encoding properties defined by RFC 5116.  Thus, a conscious terminology
change was made in -08 to longer use the term "AEAD".

 

[JLS] The term AEAD has nothing to do with the encoding properties defined
in RFC 5116.  AE and AEAD algorithms are very distinct.  One offers only
authenticated encryption and the other adds the associated data.  They are
not to be confused.

 

Mike> OK - What's a good reference for the term that's not RFC 5116?

 

[JLS] You don't need one - if you are worried about it rather than just
doing an inline abbrev (i.e. Authenticated Encryption with Associated Data
(AEAD)) then define it in the terms.

 

3.  In section 4.1.4 - Does the group agree that compression is a required
feature to implement?

 

Mike> This feature was discussed at IETF 83 and has been in place in the
current form ever since -02.  I'd be shocked if people didn't believe this
feature was necessary.

 

[JLS]  So in your opinion, it is an absolute requirement that my code
implement zip, but not that it implement jwk.  This makes absolutely no
sense to me.  I am not asking if there is a requirement that it be present
in the document.  I am asking if it is a required to implement feature.

 

Mike> The rationale for this is that people (Eric Rescorla, I think) thought
that since "zip" processing changes the ciphertext, that not supporting it
would give a weapon to attackers, enabling them to substitute one ciphertext
for another.  Since there are security implications in not implementing it,
it's MTI.

 

[JLS] I would have to talk to EKR about this.  Given that you compress
before you encrypt and we are authenticating either the post encrypted
stream or the post compressed stream I don't see where this is a real
security issue.

 

4.  Why not reference sections 4.1.5 - 10 by reference with a comment that
these refer to the key that was used to encrypt the content?  Is there a
benefit of having them listed here?  Is there a difference in the way they
are interpreted other than the recipient/originator thing?

 

Mike> I assume you mean reference them in JWS?  There's a complete list here
so that it's clear to JWE implementers what the reserved header parameters
are without having to reference other specs.  And yes, the JWS and JWE key
selection parameters are the same other than the JWS sender/JWE receiver
difference.

 

[JLS] That does not make sense to me.  There are lots of times that
referencing other specifications makes a lot of sense.  You certainly be
that this is true when it comes to security considerations.  I believe that
it is equally true here.  I did not say don't list time, I said that you
should reference the sections in the signature draft.

 

Mike> I have no objection to adding a reference saying that related
parameter definitions are also contained in JWS 4.1.2 - 4.1.5.

 

[JLS] I have no objection to saying the complete definition is in JWS as the
entire text of the section.

 

5.  Why not reference sections 4.1.11-12 from the JWS document?  Is there a
difference in the way they are interpreted?

 

Mike> (Apparently I didn't understand what you were suggesting in 4, having
seen this next question.)  In any event, in JWS they reference the key that
is used to verify the signature.  In JWE they reference the key to which the
content was encrypted.  That's the difference in all these parameters.

 

Mike> I have no objection to adding a reference saying that the related
parameter definitions are also contained in JWS 4.1.8 - 4.1.9.

 

6.  If we are not going with an alphabetic order of names, the I would
suggest that apu should be next to exp as they are used in the same context
and therefore having them adjacent makes sense.

 

Mike> Actually, Richard had suggested moving "apu" to the key agreement
section in JWA, since its use is algorithm-specific.  I think I agree with
him.

 

[JLS] that's a fine approach as well.

 

7.  Is there a reason not to reference 4.1.14 from JWS?  Is there a
difference in interpretation?

 

Mike> Stylistically, it seems easier for implementers of JWE to have a
complete list of general-purpose parameter definitions than to have some
here and some there.  The example is also different, because one is a JWS
header and the other is a JWE header.

 

Mike> I have no objection to adding a reference saying that the related
parameter definition is also contained in JWS 4.1.10.

 

 

 

                                                                Thanks
again,

                                                                -- Mike

 

Jim

 

 


------=_NextPart_000_0623_01CE743F.8175B660
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Friday, =
June 28, 2013 4:45 PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> RE: Comments on version 11 of =
draft-ietf-jose-json-web-encryption<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#00B050'>Responses inline&#8230;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br><b>Sent:</b> Friday, June 28, 2013 12:39 PM<br><b>To:</b> Mike =
Jones<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
Comments on version 11 of =
draft-ietf-jose-json-web-encryption<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [<a =
href=3D"mailto:Michael.Jones@microsoft.com">mailto:Michael.Jones@microsof=
t.com</a>] <br><b>Sent:</b> Thursday, June 27, 2013 3:50 =
PM<br><b>To:</b> Jim Schaad<br><b>Cc:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br><b>Subject:</b> RE: =
Comments on version 11 of =
draft-ietf-jose-json-web-encryption<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Thanks =
for the useful review comments, Jim.&nbsp; Replies inline prefixed by =
&#8220;<span =
style=3D'color:#0070C0'>Mike&gt;</span>&#8221;&#8230;<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: Jim Schaad [<a =
href=3D"mailto:ietf@augustcellars.com">mailto:ietf@augustcellars.com</a>]=
 <br>Sent: Saturday, June 15, 2013 2:08 PM<br>To: <a =
href=3D"mailto:draft-ietf-jose-json-web-encryption@tools.ietf.org">draft-=
ietf-jose-json-web-encryption@tools.ietf.org</a><br>Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>Subject: Comments on =
version 11 of draft-ietf-jose-json-web-encryption<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Gentlemen,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Here =
are a few comments for consideration.&nbsp; Note that some of the =
comments from the JWS review are also applicable to this document as =
much of the language in places is the same.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>1.&nbsp; In Section 4.1.2 - You probably want to =
say an AEAD algorithm not an AE algorithm<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; The problem =
with the &#8220;AEAD&#8221; terminology is that it implies both =
algorithm and encoding properties.&nbsp; We want the algorithm =
properties but not the encoding properties defined by RFC 5116.&nbsp; =
Thus, a conscious terminology change was made in -08 to longer use the =
term &#8220;AEAD&#8221;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] The term AEAD =
has nothing to do with the encoding properties defined in RFC =
5116.&nbsp; AE and AEAD algorithms are very distinct.&nbsp; One offers =
only authenticated encryption and the other adds the associated data. =
&nbsp;They are not to be confused.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#00B050'>Mike&gt; OK &#8211; =
What&#8217;s a good reference for the term that&#8217;s not RFC =
5116?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>[JLS] You don&#8217;t =
need one &#8211; if you are worried about it rather than just doing an =
inline abbrev (i.e. Authenticated Encryption with Associated Data =
(AEAD)) then define it in the terms.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>3.&nbsp; In section 4.1.4 - Does the group agree =
that compression is a required feature to implement?<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; This feature =
was discussed at IETF 83 and has been in place in the current form ever =
since -02.&nbsp; I&#8217;d be shocked if people didn&#8217;t believe =
this feature was necessary.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] &nbsp;So in =
your opinion, it is an absolute requirement that my code implement zip, =
but not that it implement jwk.&nbsp; This makes absolutely no sense to =
me.&nbsp; I am not asking if there is a requirement that it be present =
in the document.&nbsp; I am asking if it is a required to implement =
feature.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#00B050'>Mike&gt; The =
rationale for this is that people (Eric Rescorla, I think) thought that =
since &#8220;zip&#8221; processing changes the ciphertext, that not =
supporting it would give a weapon to attackers, enabling them to =
substitute one ciphertext for another.&nbsp; Since there are security =
implications in not implementing it, it&#8217;s =
MTI.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] I would have to =
talk to EKR about this.&nbsp; Given that you compress before you encrypt =
and we are authenticating either the post encrypted stream or the post =
compressed stream I don&#8217;t see where this is a real security =
issue.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>4.&nbsp; Why not reference sections 4.1.5 - 10 by =
reference with a comment that these refer to the key that was used to =
encrypt the content?&nbsp; Is there a benefit of having them listed =
here?&nbsp; Is there a difference in the way they are interpreted other =
than the recipient/originator thing?<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I assume you =
mean reference them in JWS?&nbsp; There&#8217;s a complete list here so =
that it&#8217;s clear to JWE implementers what the reserved header =
parameters are without having to reference other specs.&nbsp; And yes, =
the JWS and JWE key selection parameters are the same other than the JWS =
sender/JWE receiver difference.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] That does not =
make sense to me.&nbsp; There are lots of times that referencing other =
specifications makes a lot of sense. &nbsp;You certainly be that this is =
true when it comes to security considerations.&nbsp; I believe that it =
is equally true here.&nbsp; I did not say don&#8217;t list time, I said =
that you should reference the sections in the signature =
draft.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#00B050'>Mike&gt; I have no =
objection to adding a reference saying that related parameter =
definitions are also contained in JWS 4.1.2 &#8211; =
4.1.5.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] I have no =
objection to saying the complete definition is in JWS as the entire text =
of the section.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>5.&nbsp; Why not reference sections 4.1.11-12 from =
the JWS document?&nbsp; Is there a difference in the way they are =
interpreted?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; (Apparently =
I didn&#8217;t understand what you were suggesting in 4, having seen =
this next question.)&nbsp; In any event, in JWS they reference the key =
that is used to verify the signature.&nbsp; In JWE they reference the =
key to which the content was encrypted.&nbsp; That&#8217;s the =
difference in all these parameters.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#00B050'>Mike&gt; I have no =
objection to adding a reference saying that the related parameter =
definitions are also contained in JWS 4.1.8 &#8211; =
4.1.9.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>6.&nbsp; If we are not going with an alphabetic =
order of names, the I would suggest that apu should be next to exp as =
they are used in the same context and therefore having them adjacent =
makes sense.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Actually, =
Richard had suggested moving &#8220;apu&#8221; to the key agreement =
section in JWA, since its use is algorithm-specific.&nbsp; I think I =
agree with him.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] that&#8217;s a =
fine approach as well.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>7.&nbsp; Is there a reason not to reference 4.1.14 =
from JWS?&nbsp; Is there a difference in =
interpretation?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; =
Stylistically, it seems easier for implementers of JWE to have a =
complete list of general-purpose parameter definitions than to have some =
here and some there.&nbsp; The example is also different, because one is =
a JWS header and the other is a JWE header.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#00B050'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#00B050'>Mike&gt; I have no =
objection to adding a reference saying that the related parameter =
definition is also contained in JWS 4.1.10.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks =
again,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Jim<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p></div></div></div></body></html=
>
------=_NextPart_000_0623_01CE743F.8175B660--


From ietf@augustcellars.com  Fri Jun 28 20:46:47 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2AB21F9E2B for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 20:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.979
X-Spam-Level: 
X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wlfdypdFrPS for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 20:46:37 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED3421F9E29 for <jose@ietf.org>; Fri, 28 Jun 2013 20:46:37 -0700 (PDT)
Received: from Philemon (unknown [207.239.114.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 2C10B2CA3C; Fri, 28 Jun 2013 20:46:37 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <draft-ietf-jose-json-signature@tools.ietf.org>
References: <00f901ce6a04$d0e7d1f0$72b775d0$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A1A4A@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A1A4A@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Fri, 28 Jun 2013 20:45:39 -0700
Message-ID: <062701ce747b$1fd56040$5f8020c0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0628_01CE7440.737C2D90"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQBtu0vFP8h3IMrkFf2vW6MKEq5RDQIupFQfm/uCrWA=
Content-Language: en-us
Cc: jose@ietf.org
Subject: Re: [jose] Comments on the web signature draft version 11
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 03:46:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0628_01CE7440.737C2D90
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Thursday, June 27, 2013 3:48 PM
To: Jim Schaad; draft-ietf-jose-json-signature@tools.ietf.org
Cc: jose@ietf.org
Subject: RE: [jose] Comments on the web signature draft version 11

 

Thanks for the useful review comments, Jim.  Replies inline prefixed by
"Mike>"...

 

-----Original Message-----
From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Saturday, June 15, 2013 1:14 PM
To: draft-ietf-jose-json-signature@tools.ietf.org
Cc: jose@ietf.org
Subject: [jose] Comments on the web signature draft version 11

 

1.   Going from the string to the UTF8 encoding followed by the base64

encoding in section 3.1 is difficult given that it is not really possible to

figure out where the spaces, returns and new-lines are.   It would be easier

if you included the half-way step or better yet make the header be a single
line.

 

Mike> OK - I'll copy this intermediate step forward from the appendix where
it's already present.

 

[JLS}  I would strongly prefer the better yet approach.  In fact having
started to try and do am implementation I am going to suggest something that
is even a stricter suggestion.  It is difficult for me to match the same
protected header fields if I don't have a set of rules to follow that are
simple to program into my system.  As an example the mail on the list
earlier about the difference between line endings in your example and those
on other systems.

 

For the purpose of the examples I suggest the following rules be applied to
the protected content:

a)      There is no whitespace permitted outside of strings (which I think
means none)

b)      That all members of an object are emitted in alphabetical order
according to standard ASCII

 

This convention should be documented at the start of the example appendix
and then strictly followed.  This means that for checking the test vectors I
can have a specialized generator and use my normal generator in production
code but still be able to produce the examples from my library without
having to hand code exceptions into it.

 

2.  In section 3.1 rather than saying you are using ASCII, it might be
better to omit the character set entirely.  IMHO, having ASCII in there
confuses the issue rather than clarifies it.

 

Mike> Disagree.  EBCDIC still exists, could represent this string, and uses
a different encoding.  The computation is dependent up the encoding, so it
needs to be specified.

 

[JLS] I will worry about that issue when and if somebody does a base64url
that produces EBCIDIC.

 

4.  In section 4 para #1 - I am having an issue with the first sentence.

               a) Using "object(s)" to describe the possible hierarchy is
messy as it might be possible to interpret this as interdependent rather
than nested.

 

Mike> "JSON object" is a term from RFC 4627 - not a statement about possible
hierarchy.  I could change the words "represented by" to "representing", as
I think that would be clearer.  Would that address the issue for you?

 

[JLS] Not really - you could remove the "(s)"

 

5.  In section 4 para #2 - Two items, this does not talk about header
parameter not defined in this document and I think it might be more
understandable if this was done as a series of bullet points rather than
just text.

 

Mike> Actually, the paragraph does talk about header parameters not defined
in this document: "Unless listed as a critical header parameter, per Section
4.1.10, all other header parameters MUST be ignored when not understood."
Editorially, I don't think that bullets would be the best choice, because
the points being made in the different sentences are not grammatically
parallel.

 

[JLS] That is not the way  that I interpreted the phrase so I would
disagree.  TO me this is unclear text.  A change in the text should make it
clearer and doing bullet points would be one way to change the text.

 

6.  In section 4.1.1 - I think the current text for rejection on alg is
written on the assumption that there is only one signature/MAC on the
object.  If there are two and there is both an implementation and a key for
one signature but the second either does not have an implementation or a key

- is this still a MUST reject situation?

 

Mike> About the multi-signature case, we could say something like: "If there
are multiple signatures and/or MACs over the payload, then at least one
"alg" value must be supported and have an associated key as described above,
or the JWS must be rejected".  Does that describe the semantics you had in
mind?  What does CMS do in this case?

 

[JLS] CMS is silent on the topic.  There are applications that say that all
signatures must validate and some that say that any signature can validate.
It depends on the application.  If it said anything it would say that the
current signature would fail to validate and would say nothing about the
state of the JWS object.

 

7.  In section 4.1.2 - Are you going to impose a minimum version TLS -
specifically are SSL and TLS v1.0 allowed?

 

Mike> I propose that we add this security considerations subsection, which
is derived from that used in OAuth.  (This language resulted from the
resolution of a DISCUSS, if I recall correctly.)

 

TLS Requirements

 

Implementations MUST support TLS. Which version(s) ought to be implemented
will vary over time, and depend on the widespread deployment and known
security vulnerabilities at the time of implementation. At the time of this
writing, TLS version 1.2 [RFC5246] is the most recent version, but has very
limited actual deployment, and might not be readily available in
implementation toolkits. TLS version 1.0 [RFC2246] is the most widely
deployed version, and will give the broadest interoperability. 

 

To protect against information disclosure and tampering, confidentiality
protection MUST be applied using TLS with a ciphersuite that provides
confidentiality and integrity protection. 

 

Whenever TLS is used, a TLS server certificate check MUST be performed, per
RFC 6125 [RFC6125].

 

[JLS] while the text makes sense, it does not address the question I asked.

 

8.  In section 4.1.2 - Is implementation of this parameter required?

 

Mike> Only in the sense described in the second paragraph of section 4:
"All other header parameters defined by this specification that are not so
designated MUST be ignored when not understood."  This was part of the "MUST
understand" resolution proposed by Eric Rescorla, Nat Sakimura, and others
and confirmed by the working group.  Incomplete implementations are OK -
just not fully functional.

 

[JLS] In that case is there any reason why I should not be able to put these
items into a crit?  That is to say if you don't support this then you fail
validation on this signature.

 

9.  In section 4.1.3 - see comment 8

 

Mike> Same answer as 8

 

 

11.  In section 4.1.4 - Other than consistency - what is the requirement
here for doing HTTPS - are you expecting self-signed certificates to be
common and trying to get around trust anchor issues?

 

Mike> Yes

 

[JLS] Then you need to say so.

 

12. In section 4.1.4 - see comment 8  -- ok - and lots of other sections

 

Mike> Same answer as 8

 

14. In section 4.1.9 - This section gives why I thought that JWT was a cty
value.  It explicitly says so.  Mike has said this is not true.

 

Mike> I can see why the example is misleading.  "cty": "JWT" is only used
when the JWT representation signs or encrypts another JWT in a nested
fashion - not when a set of claims are directly signed or encrypted.  I'll
remove it (and clarify the intent of "cty" and "typ" using language supplied
by Richard).

 

15.  In section 4.1.9 - The last paragraph states that ctyp and typ values
come from the same values space.  Mike has said this is not true.

 

Mike> It is true.  If it appeared that I contradicted this, I misspoke or
was misunderstood.

 

[JLS] Ok - so now I have a question about what happens if the same value is
used in both a typ and a ctyp field.  They may have different meanings in
this case.  How is this clarified - please find the message that I mailed to
the list earlier on this issue and respond to it.  Also please look at your
prior responses to see if they need to be clarified.

 

16. In section 4.1.10 - I think there is an interesting discussion point on
the use of 'crit' in the following case.  I want to ensure that you
implement a feature in the base specification that the base specification
has said you do not need to implement.  I am not sure based on the current
document language if this is an empty set or not.

 

Mike> There's a distinction that Eric Rescorla made when designing the "MUST
understand" solution between fields that would result in security bugs if
not fully supported versus fields that would result in the inability to
process the content if not supported.  For instance, the key selection
fields are in the latter category.  If someone doesn't support "x5t" you
might not know what certificate to use and so you couldn't process the JWS,
but that would just be functionality deficiency - not a security bug.
"crit" is there to be able to dynamically designate new fields as being in
the former category.

 

[JLS] You might not support x5t and still be able to guess what the
certificate is based on it happened to work.  But it might be the wrong
certificate.  That would be a security bug.

 

17.  In section 5.1 step 3 - I don't know if there is a reason to make a
statement about suggesting that whitespace be removed when you are planning
on doing a compact representation.  This is one of those things that would
lead to a smaller encoding.

 

Mike> The statement is that whitespace is permitted and no canonicalization
need be performed.  It doesn't say that you can't remove whitespace or
perform canonicalization if you choose.

 

[JLS] there is a big difference between suggesting something be done in
practice and requiring it.  If you want to say that size matters then you
should be consistent about it.  I think that as a good practice the
suggestion makes sense.

 

18.  In section 5.1, step 4 - the phrase "If the JWS protected header is not
present..." leaves me lost.  I don't understand what this term is coming
from as you have not yet introduced it in terms of how to build a signed
message.  Specifically, there has been nothing at this point which tells me
how to decide what goes where.  I strongly feel that section 8 needs to move
before this section.

 

Mike> The JWS Protected Header was already defined in the Terminology
section.  We could make this more explicit by saying that the base64url
encoding of the JWS Protected Header is the value of the "protected" member
in the JSON Serialization, if present.

 

19.  In section 5.1, Step 11 - I think this should be moved forward to say -
repeat the steps X to Y for each signature to be processed.  I also don't
think this needs to say anything about the serialization method being used.

It is not relevant.

 

Mike> I will add the language about "steps X to Y" as you suggest.  Saying
that this only applies for the JSON Serialization is important, since this
step is inapplicable to the Compact Serialization.

 

[JLS] No,, the important thing to say for compact serialization is that in
that section it needs to say that you can only have one signer - that is not
the same as saying it is needed here.

 

21. In section 5.1, step 9 - I believe that the compact serialization should
be moved to its own section.  There should not be any apparent preference in
the document for one of the serialization methods.

 

Mike> I will create a Compact Serialization section paralleling the JSON
Serialization section, but I disagree about removing the concatenation
language here.  One of the beautiful things about the Compact Serialization
is that it *can* be described in a single sentence, as is step 9.  It will
be easier for most developers to continue having this single sentence
in-line, rather than making them jump to another section when a single
sentence in place already does the job nicely.

 

[JLS] again - that is a good optimization to put into the section on compact
serialization.  Otherwise it is getting in the way of reading and
understanding this section.

 

22. In Section 5 - I am going to make a suggestion that I would like you to
consider, although I think that it might not be to your liking.  My personal
view of the world has been one of: There is a JSON serialization that is the
object.  There is a way to map from the JSON serialization to the compact
serialization.  The mapping requires a set of constraints on the original
serialization.  Thus in my world, I build the internal JSON object
representation, run the computations on that internal representation and
then either run the mapping to the compact serialization or serialize the
JSON object representation to get the output.  Using this as the method
would mean that section 5 would be an object representation for JSON,
section 6 would be how to do the mappings to and from the compact form,
section 7 would be the how to do this.

 

Mike> What you're doing is functionally equivalent to what's in the spec
now, but pretty inefficient and unnecessary if you're only using the Compact
Serialization, which will be a common model for many use cases.  I think a
better model is that the Compact Serialization and JSON Serialization are
peers - sharing 95%+ of the processing rules and then applying a particular
serialization for the data values manipulated by those processing rules.
That's why the specs describe things in terms of abstract fields and
bindings of those fields to elements of serializations - rather than
describing things only in terms of the serialized representations.

 

[JLS] Neither of us can make a statement about which is going to be the most
implemented version.  Indeed if the mandatories are changed then you are
wrong and they would both be equally implemented.  I think that making
things clear is always better and I don't think the current text is very
clear at all.

 

23.  In section 5.3 - Are steps #1 and #2 not the requirement of the JSON
parser and not my application?  I would suggest reading some of the updated
text on member name string comparison from the JSON mailing list for a
cleaner way to write this section.

 

Mike> Specific text suggestions welcomed.

 

25.  Section 7 would appear to be better served by making it section 4.1.2
and making section on jku, jwk, x5u, x5t, x5c and kid as subjections of it.

 

Mike> The problem with this suggestion is that it would make the list of
reserved header parameters no longer syntactically parallel.  And I do
believe there's value in having a paragraph that talks about the semantics
of key identification all-up, rather than trying to do it in a manner that's
scattered in bits and pieces into the individual parameter definitions.

 

[JLS} I don't think that this changes the syntax of the output in anyway
shape or form.  I think it makes the fact that these things are common and
apply to the sub sections clear and does not interfere with reading the
document in any way.

 

26.  Section 8 - I found the presentation confusing.  I would have expected
that it would be made in the normal manner - that is you have an object and
a list of members each with its own section - and those members may have sub
members which are listed.  There would then be references back to the
members defined in section 4

 

Mike> I agree that an object-centered approach will be easier to follow.
Thanks for suggesting it.  Some of that content is now in prose.  I'll
restructure to use lists/tables instead as you suggest.

 

27.  Section 9 - I would dispute the content of this section vigorously.

 

Mike> Hannes and Derek and Stephen and Sean, at least to the OAuth WG, have
made it VERY CLEAR that the IESG requires MTI features to be defined.  Of
the JSON and Compact serializations, the latter is the only one in
widespread use, therefore it makes sense for it to be the MTI serialization.
Particularly since JWTs mandate that only the Compact Serialization be used,
it would make no sense from a working group coordination point of view to
try to mandate that the JSON serialization also be MTI - especially since
it's more complicated.

 

[JLS} Great - the mandatory to implement is now the JSON serialization with
one signer as well as the compact serialization.

 

I stopped reviewing after section 9.

 

Mike> Thanks for all the useful comments.

 

                                                            -- Mike

Jim

 

 

_______________________________________________

jose mailing list

 <mailto:jose@ietf.org> jose@ietf.org

 <https://www.ietf.org/mailman/listinfo/jose>
https://www.ietf.org/mailman/listinfo/jose


------=_NextPart_000_0628_01CE7440.737C2D90
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:47075939;
	mso-list-type:hybrid;
	mso-list-template-ids:-1591684556 67698711 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> =
Thursday, June 27, 2013 3:48 PM<br><b>To:</b> Jim Schaad; =
draft-ietf-jose-json-signature@tools.ietf.org<br><b>Cc:</b> =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Comments on the web =
signature draft version 11<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Thanks =
for the useful review comments, Jim.&nbsp; Replies inline prefixed by =
&#8220;<span =
style=3D'color:#0070C0'>Mike&gt;</span>&#8221;...<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: <a =
href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
On Behalf Of Jim Schaad<br>Sent: Saturday, June 15, 2013 1:14 PM<br>To: =
<a =
href=3D"mailto:draft-ietf-jose-json-signature@tools.ietf.org">draft-ietf-=
jose-json-signature@tools.ietf.org</a><br>Cc: <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>Subject: [jose] =
Comments on the web signature draft version 11<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>1.&nbsp;&nbsp; Going from the string to the UTF8 =
encoding followed by the base64<o:p></o:p></p><p =
class=3DMsoPlainText>encoding in section 3.1 is difficult given that it =
is not really possible to<o:p></o:p></p><p class=3DMsoPlainText>figure =
out where the spaces, returns and new-lines are.&nbsp;&nbsp; It would be =
easier<o:p></o:p></p><p class=3DMsoPlainText>if you included the =
half-way step or better yet make the header be a single =
line.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; OK &#8211; =
I&#8217;ll copy this intermediate step forward from the appendix where =
it&#8217;s already present.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS}&nbsp; I would =
strongly prefer the better yet approach.&nbsp; In fact having started to =
try and do am implementation I am going to suggest something that is =
even a stricter suggestion.&nbsp; It is difficult for me to match the =
same protected header fields if I don&#8217;t have a set of rules to =
follow that are simple to program into my system.&nbsp; As an example =
the mail on the list earlier about the difference between line endings =
in your example and those on other systems.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>For the purpose of =
the examples I suggest the following rules be applied to the protected =
content:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>a)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>There is no =
whitespace permitted outside of strings (which I think means =
none)<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:41.25pt;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>b)<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span style=3D'color:#1F497D'>That all =
members of an object are emitted in alphabetical order according to =
standard ASCII<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>This convention =
should be documented at the start of the example appendix and then =
strictly followed. &nbsp;This means that for checking the test vectors I =
can have a specialized generator and use my normal generator in =
production code but still be able to produce the examples from my =
library without having to hand code exceptions into =
it.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>2.&nbsp; In section 3.1 rather than saying you are =
using ASCII, it might be better to omit the character set =
entirely.&nbsp; IMHO, having ASCII in there confuses the issue rather =
than clarifies it.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; =
Disagree.&nbsp; EBCDIC still exists, could represent this string, and =
uses a different encoding.&nbsp; The computation is dependent up the =
encoding, so it needs to be specified.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] I will worry =
about that issue when and if somebody does a base64url that produces =
EBCIDIC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>4.&nbsp; In section 4 para #1 - I am having an =
issue with the first sentence.<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a) Using &quot;object(s)&quot; to =
describe the possible hierarchy is messy as it might be possible to =
interpret this as interdependent rather than nested.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; &quot;JSON =
object&quot; is a term from RFC 4627 - not a statement about possible =
hierarchy.&nbsp; I could change the words &quot;represented by&quot; to =
&quot;representing&quot;, as I think that would be clearer.&nbsp; Would =
that address the issue for you?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] Not really =
&#8211; you could remove the &#8220;(s)&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>5.&nbsp; In section 4 para #2 - Two items, this =
does not talk about header parameter not defined in this document and I =
think it might be more understandable if this was done as a series of =
bullet points rather than just text.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Actually, =
the paragraph does talk about header parameters not defined in this =
document: &quot;Unless listed as a critical header parameter, per =
Section 4.1.10, all other header parameters MUST be ignored when not =
understood.&quot;&nbsp; Editorially, I don't think that bullets would be =
the best choice, because the points being made in the different =
sentences are not grammatically parallel.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] That is not the =
way&nbsp; that I interpreted the phrase so I would disagree. &nbsp;TO me =
this is unclear text.&nbsp; A change in the text should make it clearer =
and doing bullet points would be one way to change the =
text.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>6.&nbsp; In section 4.1.1 - I think the current =
text for rejection on alg is written on the assumption that there is =
only one signature/MAC on the object.&nbsp; If there are two and there =
is both an implementation and a key for one signature but the second =
either does not have an implementation or a key<o:p></o:p></p><p =
class=3DMsoPlainText>- is this still a MUST reject =
situation?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; About the =
multi-signature case, we could say something like: &quot;If there are =
multiple signatures and/or MACs over the payload, then at least one =
&quot;alg&quot; value must be supported and have an associated key as =
described above, or the JWS must be rejected&quot;.&nbsp; Does that =
describe the semantics you had in mind?&nbsp; What does CMS do in this =
case?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] CMS is silent =
on the topic.&nbsp; There are applications that say that all signatures =
must validate and some that say that any signature can validate.&nbsp; =
It depends on the application.&nbsp; If it said anything it would say =
that the current signature would fail to validate and would say nothing =
about the state of the JWS object.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>7.&nbsp; In section 4.1.2 - Are you going to impose =
a minimum version TLS - specifically are SSL and TLS v1.0 =
allowed?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I propose =
that we add this security considerations subsection, which is derived =
from that used in OAuth.&nbsp; (This language resulted from the =
resolution of a DISCUSS, if I recall correctly.)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'>TLS Requirements<o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'>Implementations MUST support TLS. Which =
version(s) ought to be implemented will vary over time, and depend on =
the widespread deployment and known security vulnerabilities at the time =
of implementation. At the time of this writing, TLS version 1.2 =
[RFC5246] is the most recent version, but has very limited actual =
deployment, and might not be readily available in implementation =
toolkits. TLS version 1.0 [RFC2246] is the most widely deployed version, =
and will give the broadest interoperability. <o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'>To protect against information disclosure and =
tampering, confidentiality protection MUST be applied using TLS with a =
ciphersuite that provides confidentiality and integrity protection. =
<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:#0070C0'>Whenever TLS is used, a TLS server certificate =
check MUST be performed, per RFC 6125 [RFC6125].<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] while the text =
makes sense, it does not address the question I =
asked.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>8.&nbsp; In section 4.1.2 - Is implementation of =
this parameter required?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Only in the =
sense described in the second paragraph of section 4:&nbsp; &#8220;All =
other header parameters defined by this specification that are not so =
designated MUST be ignored when not understood.&#8221;&nbsp; This was =
part of the &#8220;MUST understand&#8221; resolution proposed by Eric =
Rescorla, Nat Sakimura, and others and confirmed by the working =
group.&nbsp; Incomplete implementations are OK &#8211; just not fully =
functional.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] In that case is =
there any reason why I should not be able to put these items into a =
crit?&nbsp; That is to say if you don&#8217;t support this then you fail =
validation on this signature.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>9.&nbsp; In section 4.1.3 - see comment =
8<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Same answer =
as 8<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>11.&nbsp; In section 4.1.4 - Other than consistency =
- what is the requirement here for doing HTTPS - are you expecting =
self-signed certificates to be common and trying to get around trust =
anchor issues?<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; =
Yes<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] Then you need =
to say so.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>12. In section 4.1.4 - see comment 8&nbsp; -- ok - =
and lots of other sections<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Same answer =
as 8<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>14. In section 4.1.9 - This section gives why I =
thought that JWT was a cty value.&nbsp; It explicitly says so.&nbsp; =
Mike has said this is not true.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I can see =
why the example is misleading.&nbsp; &#8220;cty&#8221;: =
&#8220;JWT&#8221; is only used when the JWT representation signs or =
encrypts another JWT in a nested fashion &#8211; not when a set of =
claims are directly signed or encrypted.&nbsp; I&#8217;ll remove it (and =
clarify the intent of &#8220;cty&#8221; and &#8220;typ&#8221; using =
language supplied by Richard).<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>15.&nbsp; In section 4.1.9 - The last paragraph =
states that ctyp and typ values come from the same values space.&nbsp; =
Mike has said this is not true.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; It is =
true.&nbsp; If it appeared that I contradicted this, I misspoke or was =
misunderstood.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] Ok &#8211; so =
now I have a question about what happens if the same value is used in =
both a typ and a ctyp field.&nbsp; They may have different meanings in =
this case.&nbsp; How is this clarified &#8211; please find the message =
that I mailed to the list earlier on this issue and respond to it.&nbsp; =
Also please look at your prior responses to see if they need to be =
clarified.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>16. In section 4.1.10 - I think there is an =
interesting discussion point on the use of 'crit' in the following =
case.&nbsp; I want to ensure that you implement a feature in the base =
specification that the base specification has said you do not need to =
implement.&nbsp; I am not sure based on the current document language if =
this is an empty set or not.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; =
There&#8217;s a distinction that Eric Rescorla made when designing the =
&#8220;MUST understand&#8221; solution between fields that would result =
in security bugs if not fully supported versus fields that would result =
in the inability to process the content if not supported.&nbsp; For =
instance, the key selection fields are in the latter category.&nbsp; If =
someone doesn&#8217;t support &#8220;x5t&#8221; you might not know what =
certificate to use and so you couldn&#8217;t process the JWS, but that =
would just be functionality deficiency &#8211; not a security bug.&nbsp; =
&#8220;crit&#8221; is there to be able to dynamically designate new =
fields as being in the former category.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] You might not =
support x5t and still be able to guess what the certificate is based on =
it happened to work.&nbsp; But it might be the wrong certificate.&nbsp; =
That would be a security bug.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>17.&nbsp; In section 5.1 step 3 - I don't know if =
there is a reason to make a statement about suggesting that whitespace =
be removed when you are planning on doing a compact =
representation.&nbsp; This is one of those things that would lead to a =
smaller encoding.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; The =
statement is that whitespace is permitted and no canonicalization need =
be performed.&nbsp; It doesn&#8217;t say that you can&#8217;t remove =
whitespace or perform canonicalization if you =
choose.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] there is a big =
difference between suggesting something be done in practice and =
requiring it.&nbsp; If you want to say that size matters then you should =
be consistent about it.&nbsp; I think that as a good practice the =
suggestion makes sense.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>18.&nbsp; In section 5.1, step 4 - the phrase =
&quot;If the JWS protected header is not present...&quot; leaves me =
lost.&nbsp; I don't understand what this term is coming from as you have =
not yet introduced it in terms of how to build a signed message.&nbsp; =
Specifically, there has been nothing at this point which tells me how to =
decide what goes where.&nbsp; I strongly feel that section 8 needs to =
move before this section.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; The JWS =
Protected Header was already defined in the Terminology section.&nbsp; =
We could make this more explicit by saying that the base64url encoding =
of the JWS Protected Header is the value of the &#8220;protected&#8221; =
member in the JSON Serialization, if present.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>19.&nbsp; In section 5.1, Step 11 - I think this =
should be moved forward to say - repeat the steps X to Y for each =
signature to be processed.&nbsp; I also don't think this needs to say =
anything about the serialization method being used.<o:p></o:p></p><p =
class=3DMsoPlainText>It is not relevant.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I will add =
the language about &#8220;steps X to Y&#8221; as you suggest.&nbsp; =
Saying that this only applies for the JSON Serialization is important, =
since this step is inapplicable to the Compact =
Serialization.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] No,, the =
important thing to say for compact serialization is that in that section =
it needs to say that you can only have one signer &#8211; that is not =
the same as saying it is needed here.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>21. In section 5.1, step 9 - I believe that the =
compact serialization should be moved to its own section.&nbsp; There =
should not be any apparent preference in the document for one of the =
serialization methods.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I will =
create a Compact Serialization section paralleling the JSON =
Serialization section, but I disagree about removing the concatenation =
language here.&nbsp; One of the beautiful things about the Compact =
Serialization is that it *<b>can</b>* be described in a single sentence, =
as is step 9.&nbsp; It will be easier for most developers to continue =
having this single sentence in-line, rather than making them jump to =
another section when a single sentence in place already does the job =
nicely.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] again &#8211; =
that is a good optimization to put into the section on compact =
serialization.&nbsp; Otherwise it is getting in the way of reading and =
understanding this section.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>22. In Section 5 - I am going to make a suggestion =
that I would like you to consider, although I think that it might not be =
to your liking.&nbsp; My personal view of the world has been one of: =
There is a JSON serialization that is the object.&nbsp; There is a way =
to map from the JSON serialization to the compact serialization.&nbsp; =
The mapping requires a set of constraints on the original =
serialization.&nbsp; Thus in my world, I build the internal JSON object =
representation, run the computations on that internal representation and =
then either run the mapping to the compact serialization or serialize =
the JSON object representation to get the output.&nbsp; Using this as =
the method would mean that section 5 would be an object representation =
for JSON, section 6 would be how to do the mappings to and from the =
compact form, section 7 would be the how to do this.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; What =
you&#8217;re doing is functionally equivalent to what&#8217;s in the =
spec now, but pretty inefficient and unnecessary if you&#8217;re only =
using the Compact Serialization, which will be a common model for many =
use cases.&nbsp; I think a better model is that the Compact =
Serialization and JSON Serialization are peers &#8211; sharing 95%+ of =
the processing rules and then applying a particular serialization for =
the data values manipulated by those processing rules.&nbsp; =
That&#8217;s why the specs describe things in terms of abstract fields =
and bindings of those fields to elements of serializations &#8211; =
rather than describing things only in terms of the serialized =
representations.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS] Neither of us =
can make a statement about which is going to be the most implemented =
version.&nbsp; Indeed if the mandatories are changed then you are wrong =
and they would both be equally implemented.&nbsp; I think that making =
things clear is always better and I don&#8217;t think the current text =
is very clear at all.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>23.&nbsp; In section 5.3 - Are steps #1 and #2 not =
the requirement of the JSON parser and not my application?&nbsp; I would =
suggest reading some of the updated text on member name string =
comparison from the JSON mailing list for a cleaner way to write this =
section.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Specific =
text suggestions welcomed.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>25.&nbsp; Section 7 would appear to be better =
served by making it section 4.1.2 and making section on jku, jwk, x5u, =
x5t, x5c and kid as subjections of it.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; The problem =
with this suggestion is that it would make the list of reserved header =
parameters no longer syntactically parallel.&nbsp; And I do believe =
there&#8217;s value in having a paragraph that talks about the semantics =
of key identification all-up, rather than trying to do it in a manner =
that&#8217;s scattered in bits and pieces into the individual parameter =
definitions.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#1F497D'>[JLS} I don&#8217;t =
think that this changes the syntax of the output in anyway shape or =
form.&nbsp; I think it makes the fact that these things are common and =
apply to the sub sections clear and does not interfere with reading the =
document in any way.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>26.&nbsp; Section 8 - I found the presentation =
confusing.&nbsp; I would have expected that it would be made in the =
normal manner - that is you have an object and a list of members each =
with its own section - and those members may have sub members which are =
listed.&nbsp; There would then be references back to the members defined =
in section 4<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; I agree that =
an object-centered approach will be easier to follow.&nbsp; Thanks for =
suggesting it.&nbsp; Some of that content is now in prose.&nbsp; =
I&#8217;ll restructure to use lists/tables instead as you =
suggest.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>27.&nbsp; Section 9 - I would dispute the content =
of this section vigorously.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0070C0'>Mike&gt; Hannes and =
Derek and Stephen and Sean, at least to the OAuth WG, have made it VERY =
CLEAR that the IESG requires MTI features to be defined.&nbsp; Of the =
JSON and Compact serializations, the latter is the only one in =
widespread use, therefore it makes sense for it to be the MTI =
serialization.&nbsp; Particularly since JWTs mandate that only the =
Compact Serialization be used, it would make no sense from a working =
group coordination point of view to try to mandate that the JSON =
serialization also be MTI &#8211; especially since it&#8217;s more =
complicated.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>[JLS} Great &#8211; the =
mandatory to implement is now the JSON serialization with one signer as =
well as the compact serialization.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText>I stopped reviewing after section =
9.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:#0070C0'>Mike&gt; Thanks for =
all the useful comments.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:#0070C0'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p =
class=3DMsoPlainText>Jim<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>jose mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a href=3D"mailto:jose@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>jose@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/jose"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/jose</span></a><o:p></o:p></p></div></div></body></html>
------=_NextPart_000_0628_01CE7440.737C2D90--


From ietf@augustcellars.com  Fri Jun 28 21:10:30 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53F521F9CAC for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 21:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.979
X-Spam-Level: 
X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtK7wZ3fbBJY for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 21:10:24 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id DA4E321F9CAF for <jose@ietf.org>; Fri, 28 Jun 2013 21:10:24 -0700 (PDT)
Received: from Philemon (unknown [207.239.114.206]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id CAB5738EEA; Fri, 28 Jun 2013 21:08:46 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: <jose@ietf.org>, "Mike Jones" <Michael.Jones@microsoft.com>
Date: Fri, 28 Jun 2013 21:07:19 -0700
Message-ID: <063101ce747e$425dd4f0$c7197ed0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0632_01CE7443.9600AAA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac50fElxmCSb5LZPRZybsBfpsl+Msg==
Content-Language: en-us
Subject: [jose] Propsoed Signing Procedure
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 04:10:30 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0632_01CE7443.9600AAA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I would suggest something along the following lines.  It is still missing
some of the descriptive text that is required, but not a great deal of it.

 

Jim

 

 

 

5.1 Message signing or MACing

 

To create a JWS, on performs the following steps.  The order of the steps is
information, however the result of performing the steps is prescriptive.

 

1.        Verify the content to be used as the JWS Payload is an octet
stream.  If it is not then the fail.

2.        If a common signature header field exists, then serialize the
object describing the header using UTF-8 and then base64 URL that result.
This is now the Encoded JWS Header.

3.       For each signature to be created perform the following steps:

a.       Obtain the algorithm to be used for the signature operation.  This
may be in the common signature protected header, the common signature
unprotected header or the signature header objects.  If this is not a legal
and supported signature algorithm then fail.

b.      Verify that the key to be used for the signature operation is
compatible with the signature algorithm.

c.       Concatenate the following values for the octet stream to be signed:

                                                               i.      The
Encoded JWS header if it exists,

                                                             ii.      One
period character ('.')

                                                            iii.      The
JWS payload

d.      Compute the signature value using the key, the signature algorithm
and the octet stream to be signed.

e.      Base64url encode the signature value, this is the Encoded JWS
signature.

 

Section 8.1  Compact serialization

 

In order for a compact serialization to be created, the following conditions
must be met:

1.       There must be exactly one signer

2.       There must not be a common unprotected header field or a signer
header field.  These can be combined before the signature is created to form
the common protected header field.

3.       The JWS payload MUST conform to the character set which is used for
base64url encoding.  This is A-Za-z0-9 (and whatever the rest of them are)

 

The compact serialization is formed by concatenating the following items:

1.       The Encoded JWS Header,

2.       One period character ('.')

3.       The JWS Payload

4.       One period character ('.')

5.       The Encoded JWS signature

 

Section 8.2  JSON Serialization

 

The JSON serialization is an object with the following members:

Protected            - a string containing the Encoded JWS Header (OPTIONAL)

Unprotected      - an object containing any common unprotected header values
(OPTINAL)

Payload                - a string containing the JWS Payload (REQUIRED)

Signatures           - an array containing one element for each signature
created.  Each array element consists of an object with the following
members:

                Header - an object containing any signer specific
unprotected header values (OPTINAL)

                Signature - a string containing the Encoded JWS Signature
for that signer.

 

 

 

 


------=_NextPart_000_0632_01CE7443.9600AAA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1080374493;
	mso-list-type:hybrid;
	mso-list-template-ids:-895184064 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1246306417;
	mso-list-type:hybrid;
	mso-list-template-ids:319712564 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1782797315;
	mso-list-type:hybrid;
	mso-list-template-ids:-3501958 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I would =
suggest something along the following lines.&nbsp; It is still missing =
some of the descriptive text that is required, but not a great deal of =
it.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>5.1 Message =
signing or MACing<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>To create a =
JWS, on performs the following steps.&nbsp; The order of the steps is =
information, however the result of performing the steps is =
prescriptive.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&nbsp;Verify the content to be used as the JWS =
Payload is an octet stream.&nbsp; If it is not then the =
fail.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&nbsp;If a common signature header field exists, =
then serialize the object describing the header using UTF-8 and then =
base64 URL that result.&nbsp; This is now the Encoded JWS =
Header.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>For =
each signature to be created perform the following =
steps:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>a.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Obtain the algorithm to be used for the =
signature operation.&nbsp; This may be in the common signature protected =
header, the common signature unprotected header or the signature header =
objects.&nbsp; If this is not a legal and supported signature algorithm =
then fail.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>b.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Verify that the key to be used for the signature =
operation is compatible with the signature algorithm.<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>c.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Concatenate the following values for the octet =
stream to be signed:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo1'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span>i.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
Encoded JWS header if it exists,<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo1'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; </span>ii.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo1'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span>iii.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The JWS =
payload<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>d.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Compute the signature value using the key, the =
signature algorithm and the octet stream to be signed.<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>e.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Base64url encode the signature value, this is =
the Encoded JWS signature.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section =
8.1&nbsp; Compact serialization<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In order for =
a compact serialization to be created, the following conditions must be =
met:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>There must be exactly one =
signer<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>There must not be a common unprotected header =
field or a signer header field.&nbsp; These can be combined before the =
signature is created to form the common protected header =
field.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
JWS payload MUST conform to the character set which is used for =
base64url encoding.&nbsp; This is A-Za-z0-9 (and whatever the rest of =
them are)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The compact serialization is formed by concatenating =
the following items:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo3'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
Encoded JWS Header,<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo3'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l2 level1 =
lfo3'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
JWS Payload<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo3'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>4.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l2 level1 =
lfo3'><![if !supportLists]><span style=3D'mso-list:Ignore'>5.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
Encoded JWS signature<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section =
8.2&nbsp; JSON Serialization<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The JSON =
serialization is an object with the following members:<o:p></o:p></p><p =
class=3DMsoNormal>Protected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; - a string containing the Encoded JWS Header =
(OPTIONAL)<o:p></o:p></p><p =
class=3DMsoNormal>Unprotected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - an object =
containing any common unprotected header values =
(OPTINAL)<o:p></o:p></p><p =
class=3DMsoNormal>Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - a string containing the JWS =
Payload (REQUIRED)<o:p></o:p></p><p =
class=3DMsoNormal>Signatures&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; - an array containing one element for each signature =
created.&nbsp; Each array element consists of an object with the =
following members:<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Header &#8211; an object containing =
any signer specific unprotected header values (OPTINAL)<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signature &#8211; a string =
containing the Encoded JWS Signature for that signer.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.5in'><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0632_01CE7443.9600AAA0--


From Michael.Jones@microsoft.com  Fri Jun 28 21:37:45 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC54A21F99EB for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 21:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQvXlgq7IwWz for <jose@ietfa.amsl.com>; Fri, 28 Jun 2013 21:37:39 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 4468421F99A1 for <jose@ietf.org>; Fri, 28 Jun 2013 21:37:39 -0700 (PDT)
Received: from BL2FFO11FD011.protection.gbl (10.173.161.201) by BL2FFO11HUB021.protection.gbl (10.173.161.45) with Microsoft SMTP Server (TLS) id 15.0.717.3; Sat, 29 Jun 2013 04:37:37 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD011.mail.protection.outlook.com (10.173.161.17) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Sat, 29 Jun 2013 04:37:37 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Sat, 29 Jun 2013 04:37:36 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] Propsoed Signing Procedure
Thread-Index: Ac50fElxmCSb5LZPRZybsBfpsl+MsgABLACA
Date: Sat, 29 Jun 2013 04:37:35 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A8DDE@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <063101ce747e$425dd4f0$c7197ed0$@augustcellars.com>
In-Reply-To: <063101ce747e$425dd4f0$c7197ed0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A8DDETK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(199002)(189002)(164054003)(44976004)(69226001)(51856001)(55846006)(56776001)(81542001)(46102001)(77982001)(19300405004)(81342001)(74876001)(59766001)(54316002)(76482001)(77096001)(54356001)(79102001)(47446002)(74662001)(74502001)(71186001)(15202345003)(56816003)(83072001)(31966008)(53806001)(74366001)(74706001)(33656001)(4396001)(76796001)(49866001)(80022001)(76786001)(47736001)(16406001)(65816001)(561944002)(63696002)(20776003)(6806003)(47976001)(50986001)(66066001)(512954002)(16236675002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB021; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0892FA9A88
Subject: Re: [jose] Propsoed Signing Procedure
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 04:37:45 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A8DDETK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Your description below confuses the JWS Payload (which can be any octet seq=
uence) and the Encoded JWS Payload (which is the base64url encoded represen=
tation of the JWS Payload).  For instance, you made a typo in your point 3.=
c.iii below by writing "JWS Payload" when you meant "Encoded JWS Payload".

Likewise, your first point 3 in your proposed 8.1 should be referring to th=
e Encoded JWS Payload - not the JWS Payload.  Similarly, you left off the "=
Encoded" in the second point 3 of your proposed 8.1.

Likewise, you are confusing the Encoded Payload and the Payload in your pro=
posed 8.2 text.  The payload has to be able to represent any octet stream, =
which your text doesn't enable.  That's why we have the Encoded Payload in =
the first place.

Do you want to revise your proposal to eliminate this confusion, differenti=
ating between the JWS Payload - which can represent any octet sequence, and=
 the JWS Encoded Payload, which is a URL-safe, JSON-string-safe representat=
ion of that octet stream?

I understand that editorially you're trying to restructure the signing and =
verification sections to be more agnostic to whether there are multiple sig=
natures.  I don't have any issue with that.

                                                            Thanks,
                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim=
 Schaad
Sent: Friday, June 28, 2013 9:07 PM
To: jose@ietf.org; Mike Jones
Subject: [jose] Propsoed Signing Procedure

I would suggest something along the following lines.  It is still missing s=
ome of the descriptive text that is required, but not a great deal of it.

Jim



5.1 Message signing or MACing

To create a JWS, on performs the following steps.  The order of the steps i=
s information, however the result of performing the steps is prescriptive.


1.       Verify the content to be used as the JWS Payload is an octet strea=
m.  If it is not then the fail.

2.       If a common signature header field exists, then serialize the obje=
ct describing the header using UTF-8 and then base64 URL that result.  This=
 is now the Encoded JWS Header.

3.      For each signature to be created perform the following steps:

a.      Obtain the algorithm to be used for the signature operation.  This =
may be in the common signature protected header, the common signature unpro=
tected header or the signature header objects.  If this is not a legal and =
supported signature algorithm then fail.

b.      Verify that the key to be used for the signature operation is compa=
tible with the signature algorithm.

c.      Concatenate the following values for the octet stream to be signed:

                                                    i.     The Encoded JWS =
header if it exists,

                                                   ii.     One period chara=
cter ('.')

                                                  iii.     The JWS payload

d.      Compute the signature value using the key, the signature algorithm =
and the octet stream to be signed.

e.      Base64url encode the signature value, this is the Encoded JWS signa=
ture.

Section 8.1  Compact serialization

In order for a compact serialization to be created, the following condition=
s must be met:

1.      There must be exactly one signer

2.      There must not be a common unprotected header field or a signer hea=
der field.  These can be combined before the signature is created to form t=
he common protected header field.

3.      The JWS payload MUST conform to the character set which is used for=
 base64url encoding.  This is A-Za-z0-9 (and whatever the rest of them are)

The compact serialization is formed by concatenating the following items:

1.      The Encoded JWS Header,

2.      One period character ('.')

3.      The JWS Payload

4.      One period character ('.')

5.      The Encoded JWS signature

Section 8.2  JSON Serialization

The JSON serialization is an object with the following members:
Protected            - a string containing the Encoded JWS Header (OPTIONAL=
)
Unprotected      - an object containing any common unprotected header value=
s (OPTINAL)
Payload                - a string containing the JWS Payload (REQUIRED)
Signatures           - an array containing one element for each signature c=
reated.  Each array element consists of an object with the following member=
s:
                Header - an object containing any signer specific unprotect=
ed header values (OPTINAL)
                Signature - a string containing the Encoded JWS Signature f=
or that signer.







--_000_4E1F6AAD24975D4BA5B1680429673943678A8DDETK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1080374493;
	mso-list-type:hybrid;
	mso-list-template-ids:-895184064 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1246306417;
	mso-list-type:hybrid;
	mso-list-template-ids:319712564 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1782797315;
	mso-list-type:hybrid;
	mso-list-template-ids:-3501958 67698703 67698713 67698715 67698703 6769871=
3 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Your description below=
 confuses the JWS Payload (which can be any octet sequence) and the Encoded=
 JWS Payload (which is the base64url encoded representation of the JWS Payl=
oad).&nbsp; For instance, you made a typo
 in your point 3.c.iii below by writing &#8220;JWS Payload&#8221; when you =
meant &#8220;Encoded JWS Payload&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Likewise, your first p=
oint 3 in your proposed 8.1 should be referring to the Encoded JWS Payload =
&#8211; not the JWS Payload.&nbsp; Similarly, you left off the &#8220;Encod=
ed&#8221; in
<i>the</i> second point 3 of your proposed 8.1.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Likewise, you are conf=
using the Encoded Payload and the Payload in your proposed 8.2 text.&nbsp; =
The payload has to be able to represent any octet stream, which your text d=
oesn&#8217;t enable.&nbsp; That&#8217;s why we have the Encoded
 Payload in the first place.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Do you want to revise =
your proposal to eliminate this confusion, differentiating between the JWS =
Payload &#8211; which can represent any octet sequence, and the JWS Encoded=
 Payload, which is a URL-safe, JSON-string-safe
 representation of that octet stream?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I understand that edit=
orially you&#8217;re trying to restructure the signing and verification sec=
tions to be more agnostic to whether there are multiple signatures.&nbsp; I=
 don&#8217;t have any issue with that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Jim Schaad<br>
<b>Sent:</b> Friday, June 28, 2013 9:07 PM<br>
<b>To:</b> jose@ietf.org; Mike Jones<br>
<b>Subject:</b> [jose] Propsoed Signing Procedure<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would suggest something along the following lines.=
&nbsp; It is still missing some of the descriptive text that is required, b=
ut not a great deal of it.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Jim<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">5.1 Message signing or MACing<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">To create a JWS, on performs the following steps.&nb=
sp; The order of the steps is information, however the result of performing=
 the steps is prescriptive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>&nbsp;Verify the content to be used as the JWS Payl=
oad is an octet stream.&nbsp; If it is not then the fail.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>&nbsp;If a common signature header field exists, th=
en serialize the object describing the header using UTF-8 and then base64 U=
RL that result.&nbsp; This is now the Encoded JWS Header.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>For each signature to be created perform the follow=
ing steps:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">a.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Obtain the algorithm to be used for the signature o=
peration.&nbsp; This may be in the common signature protected header, the c=
ommon signature unprotected header or the signature header objects.&nbsp; I=
f this is not a legal and supported signature
 algorithm then fail.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">b.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Verify that the key to be used for the signature op=
eration is compatible with the signature algorithm.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">c.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Concatenate the following values for the octet stre=
am to be signed:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.5in;text-indent:-1.5in=
;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore"><span style=3D"font:7.=
0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>i.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp; </span></span><![endif]>The Encoded JWS header if it exists,<=
o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.5in;text-indent:-1.5in=
;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore"><span style=3D"font:7.=
0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>ii.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp; </span></span><![endif]>One period character (&#8216;.&#8217=
;)<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.5in;text-indent:-1.5in=
;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore"><span style=3D"font:7.=
0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>iii.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nb=
sp;&nbsp;&nbsp; </span></span><![endif]>The JWS payload<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">d.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Compute the signature value using the key, the sign=
ature algorithm and the octet stream to be signed.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">e.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Base64url encode the signature value, this is the E=
ncoded JWS signature.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.1&nbsp; Compact serialization<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order for a compact serialization to be created, =
the following conditions must be met:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>There must be exactly one signer<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>There must not be a common unprotected header field=
 or a signer header field.&nbsp; These can be combined before the signature=
 is created to form the common protected header field.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo4"><![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The JWS payload MUST conform to the character set w=
hich is used for base64url encoding.&nbsp; This is A-Za-z0-9 (and whatever =
the rest of them are)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The compact serialization is formed by concatenating=
 the following items:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo6"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The Encoded JWS Header,<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo6"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>One period character (&#8216;.&#8217;)<o:p></o:p></=
p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo6"><![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The JWS Payload<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo6"><![if !supportLists]><span style=3D"mso-list:Ignore">4.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>One period character (&#8216;.&#8217;)<o:p></o:p></=
p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo6"><![if !supportLists]><span style=3D"mso-list:Ignore">5.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>The Encoded JWS signature<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.2&nbsp; JSON Serialization<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The JSON serialization is an object with the followi=
ng members:<o:p></o:p></p>
<p class=3D"MsoNormal">Protected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; - a string containing the Encoded JWS Header (OPTIO=
NAL)<o:p></o:p></p>
<p class=3D"MsoNormal">Unprotected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - an objec=
t containing any common unprotected header values (OPTINAL)<o:p></o:p></p>
<p class=3D"MsoNormal">Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - a string containing the JWS=
 Payload (REQUIRED)<o:p></o:p></p>
<p class=3D"MsoNormal">Signatures&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; - an array containing one element for each signature cre=
ated.&nbsp; Each array element consists of an object with the following mem=
bers:<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Header &#8211; an object containing =
any signer specific unprotected header values (OPTINAL)<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signature &#8211; a string containin=
g the Encoded JWS Signature for that signer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.5in"><o:p>&nbsp;</o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.5in"><o:p>&nbsp;</o:p>=
</p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A8DDETK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Sat Jun 29 03:19:02 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D8421F9EC3 for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDiDoGMaORo3 for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:18:55 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id 3941521F9EC1 for <jose@ietf.org>; Sat, 29 Jun 2013 03:18:55 -0700 (PDT)
Received: from BY2FFO11FD022.protection.gbl (10.1.15.200) by BY2FFO11HUB029.protection.gbl (10.1.14.114) with Microsoft SMTP Server (TLS) id 15.0.717.3; Sat, 29 Jun 2013 10:15:34 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD022.mail.protection.outlook.com (10.1.15.211) with Microsoft SMTP Server (TLS) id 15.0.707.0 via Frontend Transport; Sat, 29 Jun 2013 10:15:34 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Sat, 29 Jun 2013 10:14:47 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Dick Hardt <dick.hardt@gmail.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [jose] #26: Allow for signature payload to not be base64 encoded
Thread-Index: AQHOcgNOsVoAPXc/s02k5Wh9HChUEZlIUkQAgACNH4CAAObIgIAAAUowgAAHOACAAFdeAIAAGdCAgAGB7wCAAAHbAIAAtFIw
Date: Sat, 29 Jun 2013 10:14:47 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A92EE@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <061.c2fcfec0a75d48eb8b194991ce56157e@trac.tools.ietf.org> <076.3f5d1244c042cd87bfb07814924fcbc9@trac.tools.ietf.org> <033a01ce729b$26bc3910$7434ab30$@augustcellars.com> <51CBA981.4050006@nri.co.jp> <048f01ce7355$19f05bc0$4dd11340$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A0114@TK5EX14MBXC283.redmond.corp.microsoft.com> <04bf01ce7359$5ab862c0$10292840$@augustcellars.com> <CAL02cgTkUrQptGqOfQyhCembS1e3Qxw3peRFnO5QjswUW=XR-w@mail.gmail.com> <CAD9ie-sZ+w_HADMTnnkTC8XRJmjZvwYOmA+AhvJGTNPhhK=Z4g@mail.gmail.com> <CAL02cgQbAQ8zhumdR_uvXjhbZM0iXpfPnmgcJrMUuh4+bj11NA@mail.gmail.com> <CAD9ie-sBGnv5QbjFeQiXiMJ0Git06LPsAkoNeN7KZxRNqukv3w@mail.gmail.com>
In-Reply-To: <CAD9ie-sBGnv5QbjFeQiXiMJ0Git06LPsAkoNeN7KZxRNqukv3w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943678A92EETK5EX14MBXC283r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(51444003)(377454003)(24454002)(6806003)(56776001)(19300405004)(33656001)(16406001)(74502001)(76482001)(74366001)(74662001)(47446002)(76796001)(74706001)(16236675002)(15202345003)(83072001)(56816003)(77096001)(79102001)(31966008)(20776003)(44976004)(66066001)(80022001)(77982001)(54316002)(59766001)(51856001)(49866001)(4396001)(47736001)(76786001)(63696002)(47976001)(50986001)(46102001)(81542001)(54356001)(55846006)(74876001)(71186001)(65816001)(69226001)(81342001)(512954002)(53806001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB029; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0892FA9A88
Cc: Jim Schaad <ietf@augustcellars.com>, n-sakimura <n-sakimura@nri.co.jp>, "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] #26: Allow for signature payload to not be base64 encoded
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 10:19:02 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943678A92EETK5EX14MBXC283r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In the spirit of compromise, and to help further the discussion on this top=
ic, I thought I'd suggest a possible syntax for the JWS JSON Serialization =
for representing an unencoded payload as a JSON string.  One way of allowin=
g either encoded or unencoded payloads would be to use different JSON membe=
r names for them.  For instance, one could allow either of these names, but=
 not both, in any particular JWS using the JSON Serialization:

    "payload" - Contains base64url encoded JWS Payload representation
    "verbatim" - Contains unencoded JWS Payload representation

So then, for instance, these three alternative representations would all re=
present the same JWS Payload:
    "payload": "SGVsbG8gd29ybGQ"
    "verbatim": "Hello world"
    "verbatim": "Hello\u0020world"

As for the signature computation, in the "payload", case there would be no =
change from the present.  In the "verbatim" case, I assume that the logical=
 thing to do would be to use the octets of the UTF8 representation of the p=
ayload string in the signing input - in this example, 72 101 108 108 111 32=
 119 111 114 108 100.

This approach would avoid the problem I had discussed earlier of there bein=
g a default that is different than the Compact Serialization.  There would =
be no default.  Those encoding the content would choose either the "payload=
" or "verbatim" member name.

This does not avoid the problem of there being two different ways to do the=
 same thing in the standard, with the interoperability problems that can re=
sult.

I am still not advocating that we support two ways of representing payloads=
.  But if the working group does decide that it's important to do so, I thi=
nk that this would be a credible approach for doing so.  I think it would a=
ccomplish what Jim is after here.

Thoughts?

                                                            -- Mike

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Dic=
k Hardt
Sent: Friday, June 28, 2013 4:04 PM
To: Richard Barnes
Cc: Jim Schaad; n-sakimura; Mike Jones; jose@ietf.org; draft-ietf-jose-json=
-web-signature@tools.ietf.org
Subject: Re: [jose] #26: Allow for signature payload to not be base64 encod=
ed

Hi Richard, that helps.

Our you looking at a way of effectively signing a JSON payload? A complete,=
 real world example would help alot.

On Fri, Jun 28, 2013 at 3:57 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
Hey Dick,

I guess I should have been clearer that I was only talking about the JSON s=
erialization.  My proposed change would have no impact on the compact seria=
lization.  Hopefully that answers your questions about separators, etc.; th=
ey payload would just be a normal JSON string.

--Richard

On Thu, Jun 27, 2013 at 7:56 PM, Dick Hardt <dick.hardt@gmail.com<mailto:di=
ck.hardt@gmail.com>> wrote:


On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.=
sx>> wrote:
I think there are two separable issues here, both of which Mike and I proba=
bly have divergent opinions on :)
1. Syntax: Should it be possible for the "payload" field JWS to be a JSON s=
tring (instead of base64) when the payload is simply a UTF-8 string?

One of the goals of the token was that it not require encoding for it to be=
 transported in a request. IE that it be safe and SIMPLE to include in an H=
TTP header or in a URL

2. Crypto: Must the JWS Signing Input be base64url encoded.

The current answers to these questions are:
1. It is not possible.  Payload is always base64url encoded.
2. It is always base64url encoded.

The answers should be:
1. The payload should not be base64url encoded unless it cannot be represen=
ted as a JSON string.

How does an implementation determine which parts are separated? Are '.' esc=
aped? Does the implementation need to parse the JSON to determine a valid s=
eparator? How does it know the end of the JSON? That sounds really hard to =
implement, or I am misunderstanding what you are proposing.


2. The JWS Signing Input should not be base64url encoded unless there is a =
JWS Protected Header

Neither of these are complicated changes:
1. Add a "b64" header parameter that indicates that the payload is base64ur=
l-encoded binary, as opposed to a UTF-8 string.  Specify that this paramete=
r is on by default in compact-formatted JWS objects.

And how is the header separated from the payload?

2. Modify the signing/verification instructions to switch based on the pres=
ence of a JWS Protected Header: "If the JWS Protected Header is absent or e=
mpty, then the JWS Signing Input is simply the JWS Payload (not encoded).  =
If the JWS Protected Header has a non-empty value, then the the JWS Signing=
 Input is the concatenation of the Encoded JWS Header, a period ('.') chara=
cter, and the Encoded JWS Payload"

There are two reasons for these, both of which are important to make sure t=
hat this spec is applicable to a broad variety of use cases:
1. Compactness.  As Jim notes, quoted strings are shorter than base64url-en=
coded strings

The tokens are already compact enough.

2. Crypto-compatibility: Avoiding base64-encoding means that there's nothin=
g JWS-specific about the signature value.  So for example, you could transl=
ate a JWS with no protected attributes to a CMS SignedData object with no p=
rotected attributes.

Not a useful feature from my point of view.

-- Dick



--_000_4E1F6AAD24975D4BA5B1680429673943678A92EETK5EX14MBXC283r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In the spirit of compromi=
se, and to help further the discussion on this topic, I thought I&#8217;d s=
uggest a possible syntax for the JWS JSON Serialization for representing
 an unencoded payload as a JSON string.&nbsp; One way of allowing either en=
coded or unencoded payloads would be to use different JSON member names for=
 them.&nbsp; For instance, one could allow either of these names, but not b=
oth, in any particular JWS using the JSON
 Serialization:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &#8220=
;payload&#8221; &#8211; Contains base64url encoded JWS Payload representati=
on<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &#8220=
;verbatim&#8221; &#8211; Contains unencoded JWS Payload representation<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So then, for instance, th=
ese three alternative representations would all represent the same JWS Payl=
oad:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &quot;=
payload&quot;: &quot;SGVsbG8gd29ybGQ&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &quot;=
verbatim&quot;: &quot;Hello world&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp; &quot;=
verbatim&quot;: &quot;Hello\u0020world&quot;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As for the signature comp=
utation, in the &#8220;payload&#8221;, case there would be no change from t=
he present.&nbsp; In the &#8220;verbatim&#8221; case, I assume that the log=
ical thing
 to do would be to use the octets of the UTF8 representation of the payload=
 string in the signing input &#8211; in this example, 72 101 108 108 111 32=
 119 111 114 108 100.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This approach would avoid=
 the problem I had discussed earlier of there being a default that is diffe=
rent than the Compact Serialization.&nbsp; There would be no
 default.&nbsp; Those encoding the content would choose either the &#8220;p=
ayload&#8221; or &#8220;verbatim&#8221; member name.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">This does not avoid the p=
roblem of there being two different ways to do the same thing in the standa=
rd, with the interoperability problems that can result.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I am still not advocating=
 that we support two ways of representing payloads.&nbsp; But if the workin=
g group does decide that it&#8217;s important to do so, I think that
 this would be a credible approach for doing so. &nbsp;I think it would acc=
omplish what Jim is after here.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thoughts?<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> jose-bou=
nces@ietf.org [mailto:jose-bounces@ietf.org]
<b>On Behalf Of </b>Dick Hardt<br>
<b>Sent:</b> Friday, June 28, 2013 4:04 PM<br>
<b>To:</b> Richard Barnes<br>
<b>Cc:</b> Jim Schaad; n-sakimura; Mike Jones; jose@ietf.org; draft-ietf-jo=
se-json-web-signature@tools.ietf.org<br>
<b>Subject:</b> Re: [jose] #26: Allow for signature payload to not be base6=
4 encoded<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hi Richard, that helps.&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Our you looking at a way of effectively signing a JS=
ON payload? A complete, real world example would help alot.<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Jun 28, 2013 at 3:57 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o=
:p></o:p></p>
<div>
<p class=3D"MsoNormal">Hey Dick,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I guess I should have been clearer that I was only t=
alking about the JSON serialization. &nbsp;My proposed change would have no=
 impact on the compact serialization. &nbsp;Hopefully that answers your que=
stions about separators, etc.; they payload
 would just be a normal JSON string.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">--Richard<o:p></o:p></=
span></p>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 7:56 PM, Dick Hardt &lt;<a h=
ref=3D"mailto:dick.hardt@gmail.com" target=3D"_blank">dick.hardt@gmail.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Jun 27, 2013 at 3:24 PM, Richard Barnes &lt;=
<a href=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:<o=
:p></o:p></p>
<div>
<p class=3D"MsoNormal">I think there are two separable issues here, both of=
 which Mike and I probably have divergent opinions on :)<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">1. Syntax: Should it be possible for the &quot;paylo=
ad&quot; field JWS to be a JSON string (instead of base64) when the payload=
 is simply a UTF-8 string?<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">One of the goals of the token was that it not requir=
e encoding for it to be transported in a request. IE that it be safe and SI=
MPLE to include in an HTTP header or in a URL<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">2. Crypto: Must the JWS Signing Input be base64url e=
ncoded.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The current answers to these questions are:<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal">1. It is not possible. &nbsp;Payload is always base6=
4url encoded.<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">2. It is always base64url encoded.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The answers should be:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1. The payload should not be base64url encoded unles=
s it cannot be represented as a JSON string.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">How does an implementation determine which parts are=
 separated? Are '.' escaped? Does the implementation need to parse the JSON=
 to determine a valid separator? How does it know the end of the JSON? That=
 sounds really hard to implement,
 or I am misunderstanding what you are proposing.<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class=3D"MsoNormal">2. The JWS Signing Input should not be base64url enc=
oded unless there is a JWS Protected Header<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Neither of these are complicated changes:<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal">1. Add a &quot;b64&quot; header parameter that indic=
ates that the payload is base64url-encoded binary, as opposed to a UTF-8 st=
ring. &nbsp;Specify that this parameter is on by default in compact-formatt=
ed JWS objects.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">And how is the header separated from the payload?<o:=
p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class=3D"MsoNormal">2. Modify the signing/verification instructions to s=
witch based on the presence of a JWS Protected Header: &quot;If the JWS Pro=
tected Header is absent or empty, then the JWS Signing Input is simply the =
JWS Payload (not encoded). &nbsp;If the JWS
 Protected Header has a non-empty value, then the the JWS Signing Input is =
the concatenation of the Encoded JWS Header, a period ('.') character, and =
the Encoded JWS Payload&quot;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">There are two reasons for these, both of which are i=
mportant to make sure that this spec is applicable to a broad variety of us=
e cases:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">1. Compactness. &nbsp;As Jim notes, quoted strings a=
re shorter than base64url-encoded strings<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">The tokens are already compact enough.<o:p></o:p></p=
>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class=3D"MsoNormal">2. Crypto-compatibility: Avoiding base64-encoding me=
ans that there's nothing JWS-specific about the signature value. &nbsp;So f=
or example, you could translate a JWS with no protected attributes to a CMS=
 SignedData object with no protected attributes.<o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">Not a useful feature from my point of view.<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#888888">-- Dick<o:p></o:p></sp=
an></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943678A92EETK5EX14MBXC283r_--

From Michael.Jones@microsoft.com  Sat Jun 29 03:36:22 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24AFF21F9F1F for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uip8WYMU1EdN for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:36:17 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7A421F9F16 for <jose@ietf.org>; Sat, 29 Jun 2013 03:36:15 -0700 (PDT)
Received: from BL2FFO11FD017.protection.gbl (10.173.161.203) by BL2FFO11HUB037.protection.gbl (10.173.160.241) with Microsoft SMTP Server (TLS) id 15.0.717.3; Sat, 29 Jun 2013 10:21:09 +0000
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD017.mail.protection.outlook.com (10.173.161.35) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Sat, 29 Jun 2013 10:21:09 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0136.001; Sat, 29 Jun 2013 10:20:39 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: jose issue tracker <trac+jose@trac.tools.ietf.org>, "draft-ietf-jose-json-web-encryption@tools.ietf.org" <draft-ietf-jose-json-web-encryption@tools.ietf.org>, "rlb@ipv.sx" <rlb@ipv.sx>
Thread-Topic: [jose] #29: Add an explicit "aad" field to JWE
Thread-Index: AQHOc4rImU7RZeqPmUqN4QOCR8PjxplMfE8A
Date: Sat, 29 Jun 2013 10:20:39 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A932C@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <049.2f6c2e28d610320d40f8f4307cd0bf6b@trac.tools.ietf.org>
In-Reply-To: <049.2f6c2e28d610320d40f8f4307cd0bf6b@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(13464003)(199002)(189002)(377454003)(53806001)(47976001)(50986001)(49866001)(47736001)(16406001)(4396001)(23676002)(6806003)(46102001)(65816001)(33656001)(80022001)(83072001)(63696002)(47776003)(20776003)(74366001)(81542001)(54356001)(561944002)(81342001)(66066001)(55846006)(74706001)(56776001)(31966008)(77096001)(74502001)(74876001)(74662001)(50466002)(47446002)(76786001)(59766001)(51856001)(76482001)(69226001)(76796001)(54316002)(44976004)(77982001)(56816003)(79102001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB037; H:TK5EX14HUBC101.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0892FA9A88
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #29: Add an explicit "aad" field to JWE
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 10:36:22 -0000

SSBjYW4gc2VlIG1lcml0IGluIHRoaXMgcHJvcG9zYWwuDQoNCk9uIHRoZSBuZWdhdGl2ZSBzaWRl
LCBpdCdzIG9uZSBtb3JlIGZlYXR1cmUgZm9yIGltcGxlbWVudGF0aW9ucyBvZiB0aGUgSldFIEpT
T04gU2VyaWFsaXphdGlvbiB0byBzdXBwb3J0IGFuZCBvbmUgbW9yZSB3YXkgdGhhdCB0aGUgSlNP
TiBTZXJpYWxpemF0aW9uIGlzIGEgc3VwZXJzZXQgb2Ygd2hhdCdzIHBvc3NpYmxlIGluIHRoZSBD
b21wYWN0IFNlcmlhbGl6YXRpb24uDQoNCk9uIHRoZSBwb3NpdGl2ZSBzaWRlLCBpdCB3b3VsZCBs
ZXQgdGhlIEpXUyBKU09OIFNlcmlhbGl6YXRpb24gYmUgZGlyZWN0bHkgdXNlZCBmb3IgdXNlIGNh
c2VzIHdoZXJlIGhhdmluZyBBZGRpdGlvbmFsIEF1dGhlbnRpY2F0ZWQgRGF0YSAoQUFEKSBpcyB1
c2VmdWwuDQoNCkknbSBjdXJpb3VzIHdoYXQgb3RoZXJzIHRoaW5rLg0KDQoJCQkJLS0gTWlrZQ0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogam9zZSBpc3N1ZSB0cmFja2VyIFtt
YWlsdG86dHJhYytqb3NlQHRyYWMudG9vbHMuaWV0Zi5vcmddIA0KU2VudDogVGh1cnNkYXksIEp1
bmUgMjcsIDIwMTMgNDowNSBQTQ0KVG86IGRyYWZ0LWlldGYtam9zZS1qc29uLXdlYi1lbmNyeXB0
aW9uQHRvb2xzLmlldGYub3JnOyBybGJAaXB2LnN4DQpDYzogam9zZUBpZXRmLm9yZw0KU3ViamVj
dDogW2pvc2VdICMyOTogQWRkIGFuIGV4cGxpY2l0ICJhYWQiIGZpZWxkIHRvIEpXRQ0KDQojMjk6
IEFkZCBhbiBleHBsaWNpdCAiYWFkIiBmaWVsZCB0byBKV0UNCg0KIExldCdzIHN0YXJ0IGZyb20g
dGhlIGRlc2lnbiBwcmluY2lwbGUgdGhhdCB0aGUgY3J5cHRvIG9wZXJhdGlvbnMgaW4gSldFICBz
aG91bGQgbm90IGJlIEpXRS1zcGVjaWZpYyBpZiB0aGV5IGRvbid0IGhhdmUgdG8gYmUuICBSaWdo
dCBub3csIHRoZSBvbmx5ICB3YXkgZm9yIGFuIGFwcGxpY2F0aW9uIHRvIHByb3ZpZGUgQUFEIHRv
IGEgSldFIGFsZ29yaXRobSBpcyBpbiB0aGUgIHByb3RlY3RlZCBoZWFkZXIuICBTbyBpdCdzIGlt
cG9zc2libGUgdG8gdXNlIEpPU0UgdG8gaW1wbGVtZW50IGFueSAgcHJvdG9jb2wgdGhhdCB1c2Vz
IEFBRCB0byBwcm90ZWN0IG5vbi1KU09OIGRhdGEuICAoT3IgaWYgbm90IGltcG9zc2libGUsICBp
dCdzIGNvc3RseSwgc2luY2UgaXQgd2lsbCBlbmQgdXAgZ2V0dGluZyBkb3VibGUtYmFzZTY0IGVu
Y29kZWQuKQ0KDQogSW5zdGVhZCwgSldFIHNob3VsZCBoYXZlIGFuIGV4cGxpY2l0ICJhYWQiIGZp
ZWxkIHRoYXQgY29udGFpbnMgYSAgYmFzZTY0LWVuY29kZWQgb2N0ZXQgc3RyaW5nIHRoYXQgaXMg
aW5wdXQgYXMgQWRkaXRpb25hbCBBdXRoZW50aWNhdGVkIERhdGEgIHRvIHRoZSBBRUFEIGFsZ29y
aXRobS4gIElmIHRoZXJlIGlzIGEgcHJvdGVjdGVkIGhlYWRlciBwcmVzZW50IHRoZW4gdGhlICBv
dmVyYWxsIEFBRCBpcyB0aGUgY29uY2F0ZW5hdGlvbiBvZiB0aGUgaGVhZGVyIGFuZCB0aGUgImFh
ZCIgZmllbGQuDQoNCiBJbiB0aGUgY29tcGFjdCBmb3JtYXQsIHRoaXMgZmllbGQgaXMgYWx3YXlz
IGVtcHR5Lg0KDQogT0xEOg0KICIiIg0KIExldCB0aGUgQWRkaXRpb25hbCBBdXRoZW50aWNhdGVk
IERhdGEgZW5jcnlwdGlvbiBwYXJhbWV0ZXIgYmUgdGhlIG9jdGV0cyAgb2YgdGhlIEFTQ0lJIHJl
cHJlc2VudGF0aW9uIG9mIHRoZSBFbmNvZGVkIEpXRSBIZWFkZXIgdmFsdWUuDQogIiIiDQogTkVX
Og0KICIiIg0KIExldCB0aGUgQWRkaXRpb25hbCBBdXRoZW50aWNhdGVkIERhdGEgZW5jcnlwdGlv
biBwYXJhbWV0ZXIgYmUgdGhlIG9jdGV0cyAgb2YgdGhlIEFTQ0lJIHJlcHJlc2VudGF0aW9uIG9m
IHRoZSBFbmNvZGVkIEpXRSBIZWFkZXIgdmFsdWUuICBJZiBhbiAiYWFkIg0KIHBhcmFtZXRlciBp
cyBwcmVzZW50LCBzZXQgdGhlIEFkZGl0aW9uYWwgQXV0aGVudGljYXRlZCBEYXRhIHRvIHRoZSAg
Y29uY2F0ZW5hdGlvbiBvZiB0aGUgRW5jb2RlZCBKV0UgSGVhZGVyLCBhIHBlcmlvZCAoJy4nKSBj
aGFyYWN0ZXIsIGFuZCB0aGUgIEFTQ0lJIHJlcHJlc2VudGF0aW9uIG9mIHRoZSAiYWFkIiBmaWVs
ZCB2YWx1ZS4NCiAiIiINCg0KLS0gDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0rLS0tDQogUmVwb3J0ZXI6ICBybGJAaXB2LnN4ICAgfCAgICAgIE93bmVyOiAgZHJh
ZnQtaWV0Zi1qb3NlLWpzb24td2ViLQ0KICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIGVuY3J5
cHRpb25AdG9vbHMuaWV0Zi5vcmcNCiBQcmlvcml0eTogIG1ham9yICAgICAgICB8ICAgICBTdGF0
dXM6ICBuZXcNCkNvbXBvbmVudDogIGpzb24td2ViLSAgICB8ICBNaWxlc3RvbmU6DQogIGVuY3J5
cHRpb24gICAgICAgICAgICAgfCAgICBWZXJzaW9uOg0KIFNldmVyaXR5OiAgLSAgICAgICAgICAg
IHwgICBLZXl3b3JkczoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LSstLS0NCg0KVGlja2V0IFVSTDogPGh0dHA6Ly90b29scy5pZXRmLm9yZy93Zy9qb3NlL3RyYWMv
dGlja2V0LzI5Pg0Kam9zZSA8aHR0cDovL3Rvb2xzLmlldGYub3JnL2pvc2UvPg0KDQo=

From Michael.Jones@microsoft.com  Sat Jun 29 03:58:10 2013
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4817421F9F6B for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnxnPVNqsuJb for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 03:58:05 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id C9C4621F9F63 for <jose@ietf.org>; Sat, 29 Jun 2013 03:58:04 -0700 (PDT)
Received: from BN1AFFO11FD017.protection.gbl (10.58.52.203) by BN1AFFO11HUB006.protection.gbl (10.58.52.116) with Microsoft SMTP Server (TLS) id 15.0.717.3; Sat, 29 Jun 2013 10:42:54 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD017.mail.protection.outlook.com (10.58.52.77) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Sat, 29 Jun 2013 10:42:54 +0000
Received: from TK5EX14MBXC283.redmond.corp.microsoft.com ([169.254.2.25]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Sat, 29 Jun 2013 10:42:53 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] #24: Move JWS headers into signature block
Thread-Index: AQHOZuGREcSF6P64R0Gww4KERWq9uplGA9aAgAaUYvA=
Date: Sat, 29 Jun 2013 10:42:52 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943678A937E@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org> <064.9c6aec3e9813fc2933f6082d75e8e239@trac.tools.ietf.org>
In-Reply-To: <064.9c6aec3e9813fc2933f6082d75e8e239@trac.tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454003)(199002)(189002)(13464003)(20776003)(65816001)(69226001)(50466002)(79102001)(80022001)(16406001)(55846006)(83072001)(66066001)(54356001)(46102001)(47976001)(47776003)(51856001)(47736001)(74706001)(63696002)(31966008)(53806001)(4396001)(50986001)(49866001)(74876001)(33656001)(74502001)(76482001)(74662001)(81542001)(47446002)(74366001)(77982001)(59766001)(6806003)(81342001)(54316002)(56776001)(23676002)(76786001)(76796001)(77096001)(56816003); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB006; H:TK5EX14MLTC104.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0892FA9A88
Subject: Re: [jose] #24: Move JWS headers into signature block
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 10:58:10 -0000

UGVyaGFwcyBJJ20gaW4gYW4gb2RkIGZyYW1lIG9mIG1pbmQgdG9uaWdodCwgYmVjYXVzZSBJIHdv
dWxkbid0IG5vcm1hbGx5IGV2ZW4gY29uc2lkZXIgcmUtcmFpc2luZyBhIGNsb3NlZCBpc3N1ZSwg
YnV0IEJlbiBMYXVyaWUncyBhZHZpY2UgIndoeSBub3QganVzdCBwcm90ZWN0IGV2ZXJ5dGhpbmci
IGtlcHQgcnVubmluZyBteSBtaW5kIGFuZCBJIHJlYWxpemVkIHRoYXQgdGhlIGN1cnJlbnQgSldT
IEpTT04gU2VyaWFsaXphdGlvbiBkb2Vzbid0IGFsbG93IHVzIHRvIGRvIHRoYXQgaW4gdGhlIGdl
bmVyYWwgY2FzZS4gIFNwZWNpZmljYWxseSwgd2UgZG9uJ3QgYWxsb3cgYSBwZXItc2lnbmF0dXJl
ICJwcm90ZWN0ZWQiIGhlYWRlcnMgZmllbGQsIHdoaWNoIHdvdWxkIGJlIG5lY2Vzc2FyeSB0byBw
cm90ZWN0IHRoZSBjcnlwdG9ncmFwaGljIHBhcmFtZXRlcnMgaWYgZGlmZmVyZW50IHNpZ25hdHVy
ZXMgdXNlIGRpZmZlcmVudCBhbGdvcml0aG1zLg0KDQpTbyBJJ2QgYXQgbGVhc3QgbGlrZSBvdGhl
cnMnIHRob3VnaHRzIG9uIHdoZXRoZXIgd2Ugd2FudCB0byAiZmlsbCBpbiB0aGUgbWF0cml4IiBm
b3IgdGhlIEpXUyBKU09OIFNlcmlhbGl6YXRpb24gYW5kIGFsbG93IGhlYWRlciBwYXJhbWV0ZXJz
IHRvIGJlIHNwZWNpZmllZCBib3RoIGluIHByb3RlY3RlZCBhbmQgdW5wcm90ZWN0ZWQgZm9ybXMs
IGJvdGggb24gYSBzaGFyZWQgYW5kIHBlci1zaWduYXR1cmUgYmFzaXMuICBXZSBjdXJyZW50bHkg
c3VwcG9ydCAzIG9mIHRoZXNlIDQgaGVhZGVyIHBhcmFtZXRlciBsb2NhdGlvbnMuDQoNCk5vdGUg
dGhhdCB3ZSB3b3VsZCBub3QgZG8gdGhpcyBmb3IgSldFLCBzaW5jZSAoYXMgZXh0ZW5zaXZlbHkg
ZGlzY3Vzc2VkKSBwZXItcmVjaXBpZW50IHByb3RlY3RlZCBjb250ZW50IGlzIHByb2JsZW1hdGlj
Lg0KDQpGb3IgdGhlIHNpZ25hdHVyZSBpbnB1dCwgaWYgYm90aCBzaGFyZWQgYW5kIHBlci1zaWdu
YXR1cmUgcHJvdGVjdGVkIGhlYWRlcnMgd2VyZSBwcmVzZW50LCB3ZSdkIG5lZWQgdG8gY29uY2F0
ZW5hdGUgdGhlIHR3byBiYXNlNjR1cmwgZW5jb2RlZCByZXByZXNlbnRhdGlvbnMgdG9nZXRoZXIg
d2l0aCBhIHNlcGFyYXRvciBjaGFyYWN0ZXIgYmV0d2VlbiAoSSdtIHRoaW5raW5nIGNvbW1hICgn
LCcpIGJlY2F1c2UgaXQgaXMgZGlzdGluY3QgZnJvbSBwZXJpb2QgKCcuJyksIHdoaWNoIGlzIGFs
c28gdXNlZCBhcyBhIHNlcGFyYXRvciBpbiB0aGUgc2lnbmF0dXJlIGlucHV0KS4NCg0KSSdtIGZp
bmUgd2l0aCB0aGlzIGlzc3VlIHJlbWFpbmluZyBjbG9zZWQsIGJ1dCBJIHdhbnRlZCB0byBhdCBs
ZWFzdCBydW4gdGhpcyBwb3NzaWJpbGl0eSBieSB0aGUgd29ya2luZyBncm91cCBmb3IgdGhlaXIg
aW5wdXQsIHNpbmNlIGl0IGhhZG4ndCBiZWVuIGRpc2N1c3NlZCBwcmV2aW91c2x5Lg0KDQoJCQkJ
Q2hlZXJzLA0KCQkJCS0tIE1pa2UNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IGpvc2UgaXNzdWUgdHJhY2tlciBbbWFpbHRvOnRyYWMram9zZUB0cmFjLnRvb2xzLmlldGYub3Jn
XSANClNlbnQ6IE1vbmRheSwgSnVuZSAyNCwgMjAxMyAxMDo1NyBQTQ0KVG86IGRyYWZ0LWlldGYt
am9zZS1qc29uLXdlYi1zaWduYXR1cmVAdG9vbHMuaWV0Zi5vcmc7IE1pa2UgSm9uZXM7IGlldGZA
YXVndXN0Y2VsbGFycy5jb20NCkNjOiBqb3NlQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2pvc2Vd
ICMyNDogTW92ZSBKV1MgaGVhZGVycyBpbnRvIHNpZ25hdHVyZSBibG9jaw0KDQojMjQ6IE1vdmUg
SldTIGhlYWRlcnMgaW50byBzaWduYXR1cmUgYmxvY2sNCg0KQ2hhbmdlcyAoYnkgaWV0ZkBhdWd1
c3RjZWxsYXJzLmNvbSk6DQoNCiAqIHN0YXR1czogIG5ldyA9PiBjbG9zZWQNCiAqIHJlc29sdXRp
b246ICAgPT4gd29udGZpeA0KDQoNCkNvbW1lbnQ6DQoNCiBDbG9zaW5nIHBlciB0aGUgZGlzY3Vz
c2lvbiBvbiB0aGUgdGVsZWNvbmZlcmVuY2UuDQoNCiBXZSBjdXJyZW50bHkgZG8gbm90IGhhdmUg
YSBzdHJvbmcgdXNlIGNhc2UgZm9yIHBlciB1c2VyIGl0ZW1zLiAgIEl0IHdpbGwNCiBiZSBwb3Nz
aWJsZSBpbiBmdXR1cmUgdmVyc2lvbnMgdG8gYWRkIGEgcHJvdGVjdGVkIGZpZWxkIHRvIHRoZSBw
ZXIgc2lnbmVyICBpdGVtIGFuZCBpbmNsdWRlIGJvdGggaW4gdGhlIGludGVncml0eSBwcm90ZWN0
aW9uIGluIHRoZSBldmVudCB0aGF0IGEgdXNlICBjYXNlIGFwcGVhcnMuDQoNCiBUaGVyZSB3YXMg
bm8gc3Ryb25nIHJlY29tbWVuZGF0aW9uIGZyb20gdGhlIENGUkcgbGlzdCBpZiBhIGhhc2ggIHN1
YnN0aXR1dGlvbiBhdHRhY2sgaXMgZWl0aGVyIHByb2JhYmxlIG9yIHBvc3NpYmxlLg0KDQotLSAN
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0NCiBSZXBvcnRl
cjogIHJsYkBpcHYuc3ggICB8ICAgICAgIE93bmVyOiAgZHJhZnQtaWV0Zi1qb3NlLWpzb24td2Vi
LQ0KICAgICBUeXBlOiAgZGVmZWN0ICAgICAgIHwgIHNpZ25hdHVyZUB0b29scy5pZXRmLm9yZw0K
IFByaW9yaXR5OiAgbWFqb3IgICAgICAgIHwgICAgICBTdGF0dXM6ICBjbG9zZWQNCkNvbXBvbmVu
dDogIGpzb24td2ViLSAgICB8ICAgTWlsZXN0b25lOg0KICBzaWduYXR1cmUgICAgICAgICAgICAg
IHwgICAgIFZlcnNpb246DQogU2V2ZXJpdHk6ICAtICAgICAgICAgICAgfCAgUmVzb2x1dGlvbjog
IHdvbnRmaXgNCiBLZXl3b3JkczogICAgICAgICAgICAgICB8DQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCi0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tDQoNClRpY2tldCBVUkw6IDxodHRwOi8vdHJhYy50
b29scy5pZXRmLm9yZy93Zy9qb3NlL3RyYWMvdGlja2V0LzI0I2NvbW1lbnQ6Mj4NCmpvc2UgPGh0
dHA6Ly90b29scy5pZXRmLm9yZy9qb3NlLz4NCg0K

From ietf@augustcellars.com  Sat Jun 29 13:23:22 2013
Return-Path: <ietf@augustcellars.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E3B21F9AAE for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 13:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpeS-zJSkqxF for <jose@ietfa.amsl.com>; Sat, 29 Jun 2013 13:23:16 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD04321F9AEC for <jose@ietf.org>; Sat, 29 Jun 2013 13:23:15 -0700 (PDT)
Received: from Philemon (winery.augustcellars.com [206.212.239.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id CBE952C9F4; Sat, 29 Jun 2013 13:23:13 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Mike Jones'" <Michael.Jones@microsoft.com>, <jose@ietf.org>
References: <063101ce747e$425dd4f0$c7197ed0$@augustcellars.com> <4E1F6AAD24975D4BA5B1680429673943678A8DDE@TK5EX14MBXC283.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A8DDE@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sat, 29 Jun 2013 13:22:16 -0700
Message-ID: <067301ce7506$59c24300$0d46c900$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0674_01CE74CB.AD698580"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ0ZpASfqhOiWpDoSxBqh+0BS1yoALr+1MWl+mye2A=
Content-Language: en-us
Subject: Re: [jose] Propsoed Signing Procedure
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 29 Jun 2013 20:23:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0674_01CE74CB.AD698580
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

You are making an assumption which is incorrect.

 

This text is in response to a request by you to outline the procedures for
not base64 encoding the content.  Thus it is completely correct that there
no difference between the JWS payload and the JWS encoded payload because
under that proposal there isn't any difference.

 

The problem with doing things piecemeal over time is that one forgets
things.  I was going to add a new section to the document as well

 

X.  Content Preparation requirements on the Application

 

Applications need to do a certain amount of preparation of the content
before it can be signed.   The only content that can be signed is a stream
of octet values.  How the stream of octet values is represented is specific
to the language and, potentially, library being used for the implementation
of JWS.  

 

Some libraries will provide helper functions that can do the preparation for
the application, however the capabilities will vary from library to library
and are not covered by this specification.

 

The compact serialization method requires that the content be placed in the
base64url character set prior to being signed.  This can be done either by
the application doing the base64url encoding on the content, or by the
application constraining the set of possible values to be signed to those in
the base64url character set.  Again this is a feature that some libraries
will provide helper functions for but how it is done will be library
specific.

 

From: Mike Jones [mailto:Michael.Jones@microsoft.com] 
Sent: Friday, June 28, 2013 9:38 PM
To: Jim Schaad; jose@ietf.org
Subject: RE: [jose] Propsoed Signing Procedure

 

Your description below confuses the JWS Payload (which can be any octet
sequence) and the Encoded JWS Payload (which is the base64url encoded
representation of the JWS Payload).  For instance, you made a typo in your
point 3.c.iii below by writing "JWS Payload" when you meant "Encoded JWS
Payload".

 

Likewise, your first point 3 in your proposed 8.1 should be referring to the
Encoded JWS Payload - not the JWS Payload.  Similarly, you left off the
"Encoded" in the second point 3 of your proposed 8.1.

 

Likewise, you are confusing the Encoded Payload and the Payload in your
proposed 8.2 text.  The payload has to be able to represent any octet
stream, which your text doesn't enable.  That's why we have the Encoded
Payload in the first place.

 

Do you want to revise your proposal to eliminate this confusion,
differentiating between the JWS Payload - which can represent any octet
sequence, and the JWS Encoded Payload, which is a URL-safe, JSON-string-safe
representation of that octet stream?

 

I understand that editorially you're trying to restructure the signing and
verification sections to be more agnostic to whether there are multiple
signatures.  I don't have any issue with that.

 

                                                            Thanks,

                                                            -- Mike

 

From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Jim
Schaad
Sent: Friday, June 28, 2013 9:07 PM
To: jose@ietf.org; Mike Jones
Subject: [jose] Propsoed Signing Procedure

 

I would suggest something along the following lines.  It is still missing
some of the descriptive text that is required, but not a great deal of it.

 

Jim

 

 

 

5.1 Message signing or MACing

 

To create a JWS, on performs the following steps.  The order of the steps is
information, however the result of performing the steps is prescriptive.

 

1.        Verify the content to be used as the JWS Payload is an octet
stream.  If it is not then the fail.

2.        If a common signature header field exists, then serialize the
object describing the header using UTF-8 and then base64 URL that result.
This is now the Encoded JWS Header.

3.       For each signature to be created perform the following steps:

a.       Obtain the algorithm to be used for the signature operation.  This
may be in the common signature protected header, the common signature
unprotected header or the signature header objects.  If this is not a legal
and supported signature algorithm then fail.

b.      Verify that the key to be used for the signature operation is
compatible with the signature algorithm.

c.       Concatenate the following values for the octet stream to be signed:

                                                                  i.
The Encoded JWS header if it exists,

                                                                 ii.
One period character ('.')

                                                               iii.      The
JWS payload

d.      Compute the signature value using the key, the signature algorithm
and the octet stream to be signed.

e.      Base64url encode the signature value, this is the Encoded JWS
signature.

 

Section 8.1  Compact serialization

 

In order for a compact serialization to be created, the following conditions
must be met:

1.       There must be exactly one signer

2.       There must not be a common unprotected header field or a signer
header field.  These can be combined before the signature is created to form
the common protected header field.

3.       The JWS payload MUST conform to the character set which is used for
base64url encoding.  This is A-Za-z0-9 (and whatever the rest of them are)

 

The compact serialization is formed by concatenating the following items:

1.       The Encoded JWS Header,

2.       One period character ('.')

3.       The JWS Payload

4.       One period character ('.')

5.       The Encoded JWS signature

 

Section 8.2  JSON Serialization

 

The JSON serialization is an object with the following members:

Protected            - a string containing the Encoded JWS Header (OPTIONAL)

Unprotected      - an object containing any common unprotected header values
(OPTINAL)

Payload                - a string containing the JWS Payload (REQUIRED)

Signatures           - an array containing one element for each signature
created.  Each array element consists of an object with the following
members:

                Header - an object containing any signer specific
unprotected header values (OPTINAL)

                Signature - a string containing the Encoded JWS Signature
for that signer.

 

 

 

 


------=_NextPart_000_0674_01CE74CB.AD698580
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1080374493;
	mso-list-type:hybrid;
	mso-list-template-ids:-895184064 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1246306417;
	mso-list-type:hybrid;
	mso-list-template-ids:319712564 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1782797315;
	mso-list-type:hybrid;
	mso-list-template-ids:-3501958 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>You are making an assumption which is =
incorrect.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This text is in response =
to a request by you to outline the procedures for not base64 encoding =
the content.&nbsp; Thus it is completely correct that there no =
difference between the JWS payload and the JWS encoded payload because =
under that proposal there isn&#8217;t any =
difference.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>The problem with doing =
things piecemeal over time is that one forgets things.&nbsp; I was going =
to add a new section to the document as well<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>X.&nbsp; Content =
Preparation requirements on the Application<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Applications need to do =
a certain amount of preparation of the content before it can be =
signed.&nbsp; &nbsp;The only content that can be signed is a stream of =
octet values.&nbsp; How the stream of octet values is represented is =
specific to the language and, potentially, library being used for the =
implementation of JWS. &nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Some libraries will =
provide helper functions that can do the preparation for the =
application, however the capabilities will vary from library to library =
and are not covered by this specification.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>The compact =
serialization method requires that the content be placed in the =
base64url character set prior to being signed.&nbsp; This can be done =
either by the application doing the base64url encoding on the content, =
or by the application constraining the set of possible values to be =
signed to those in the base64url character set.&nbsp; Again this is a =
feature that some libraries will provide helper functions for but how it =
is done will be library specific.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Mike Jones [mailto:Michael.Jones@microsoft.com] <br><b>Sent:</b> Friday, =
June 28, 2013 9:38 PM<br><b>To:</b> Jim Schaad; =
jose@ietf.org<br><b>Subject:</b> RE: [jose] Propsoed Signing =
Procedure<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Your description below confuses the JWS Payload =
(which can be any octet sequence) and the Encoded JWS Payload (which is =
the base64url encoded representation of the JWS Payload).&nbsp; For =
instance, you made a typo in your point 3.c.iii below by writing =
&#8220;JWS Payload&#8221; when you meant &#8220;Encoded JWS =
Payload&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Likewise, your first =
point 3 in your proposed 8.1 should be referring to the Encoded JWS =
Payload &#8211; not the JWS Payload.&nbsp; Similarly, you left off the =
&#8220;Encoded&#8221; in <i>the</i> second point 3 of your proposed =
8.1.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Likewise, you are =
confusing the Encoded Payload and the Payload in your proposed 8.2 =
text.&nbsp; The payload has to be able to represent any octet stream, =
which your text doesn&#8217;t enable.&nbsp; That&#8217;s why we have the =
Encoded Payload in the first place.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Do you want to revise =
your proposal to eliminate this confusion, differentiating between the =
JWS Payload &#8211; which can represent any octet sequence, and the JWS =
Encoded Payload, which is a URL-safe, JSON-string-safe representation of =
that octet stream?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I understand that =
editorially you&#8217;re trying to restructure the signing and =
verification sections to be more agnostic to whether there are multiple =
signatures.&nbsp; I don&#8217;t have any issue with =
that.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:jose-bounces@ietf.org">jose-bounces@ietf.org</a> [<a =
href=3D"mailto:jose-bounces@ietf.org">mailto:jose-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Jim Schaad<br><b>Sent:</b> Friday, June 28, 2013 =
9:07 PM<br><b>To:</b> <a =
href=3D"mailto:jose@ietf.org">jose@ietf.org</a>; Mike =
Jones<br><b>Subject:</b> [jose] Propsoed Signing =
Procedure<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would =
suggest something along the following lines.&nbsp; It is still missing =
some of the descriptive text that is required, but not a great deal of =
it.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jim<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>5.1 Message =
signing or MACing<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>To create a =
JWS, on performs the following steps.&nbsp; The order of the steps is =
information, however the result of performing the steps is =
prescriptive.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&nbsp;Verify the content to be used as the JWS =
Payload is an octet stream.&nbsp; If it is not then the =
fail.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&nbsp;If a common signature header field exists, =
then serialize the object describing the header using UTF-8 and then =
base64 URL that result.&nbsp; This is now the Encoded JWS =
Header.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>For =
each signature to be created perform the following =
steps:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>a.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Obtain the algorithm to be used for the =
signature operation.&nbsp; This may be in the common signature protected =
header, the common signature unprotected header or the signature header =
objects.&nbsp; If this is not a legal and supported signature algorithm =
then fail.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>b.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Verify that the key to be used for the signature =
operation is compatible with the signature algorithm.<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>c.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Concatenate the following values for the octet =
stream to be signed:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>i.<span style=3D'font:7.0pt =
"Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>The Encoded JWS header if it =
exists,<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; </span>ii.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;=
mso-list:l0 level3 lfo2'><![if !supportLists]><span =
style=3D'mso-list:Ignore'><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; </span>iii.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The JWS =
payload<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>d.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Compute the signature value using the key, the =
signature algorithm and the octet stream to be signed.<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>e.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Base64url encode the signature value, this is =
the Encoded JWS signature.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section =
8.1&nbsp; Compact serialization<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In order for =
a compact serialization to be created, the following conditions must be =
met:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo4'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>There must be exactly one =
signer<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo4'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>There must not be a common unprotected header =
field or a signer header field.&nbsp; These can be combined before the =
signature is created to form the common protected header =
field.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo4'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
JWS payload MUST conform to the character set which is used for =
base64url encoding.&nbsp; This is A-Za-z0-9 (and whatever the rest of =
them are)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The compact serialization is formed by concatenating =
the following items:<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo6'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
Encoded JWS Header,<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo6'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l2 level1 =
lfo6'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
JWS Payload<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l2 level1 lfo6'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>4.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>One =
period character (&#8216;.&#8217;)<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l2 level1 =
lfo6'><![if !supportLists]><span style=3D'mso-list:Ignore'>5.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>The =
Encoded JWS signature<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Section =
8.2&nbsp; JSON Serialization<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The JSON =
serialization is an object with the following members:<o:p></o:p></p><p =
class=3DMsoNormal>Protected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; - a string containing the Encoded JWS Header =
(OPTIONAL)<o:p></o:p></p><p =
class=3DMsoNormal>Unprotected&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - an object =
containing any common unprotected header values =
(OPTINAL)<o:p></o:p></p><p =
class=3DMsoNormal>Payload&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - a string containing the JWS =
Payload (REQUIRED)<o:p></o:p></p><p =
class=3DMsoNormal>Signatures&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; - an array containing one element for each signature =
created.&nbsp; Each array element consists of an object with the =
following members:<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Header &#8211; an object containing =
any signer specific unprotected header values (OPTINAL)<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signature &#8211; a string =
containing the Encoded JWS Signature for that signer.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.5in'><o:p>&nbsp;</o:p></p></div></div></body></htm=
l>
------=_NextPart_000_0674_01CE74CB.AD698580--


From rlb@ipv.sx  Sun Jun 30 15:19:15 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCE721F9BF7 for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 15:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.476
X-Spam-Level: 
X-Spam-Status: No, score=-3.476 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Qd-nZEbvchu for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 15:19:11 -0700 (PDT)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id CFB3021F9BF6 for <jose@ietf.org>; Sun, 30 Jun 2013 15:19:10 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n10so4166036oag.0 for <jose@ietf.org>; Sun, 30 Jun 2013 15:19:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=nII0Kigyw5PEIjA8hyWyLIoPWxd110Req8N7RuZ+Tx0=; b=nUalZcrZlY5qmRuB8b8pexLrn9yl5L9zIZoGaww01DVPgWkieyLLxC2BpJR+SFZ84a ohKckMfvh7/Uu6itQrTkVvjNN7WLsiBoozeGW2UfMtwOM/ozJXiN8A6k+zC3PDHDwate YgRFV4uKP/SGZOcrfa3bDUw2iF0PdDuKWjSWRofAu5RaAyfVlVuHhb0/RItFcALUiiUs Z8jXRxoE7p9zSWsl3rn92TqzppQQhG0BHQJF1oOhsf8817k/p5f3wJHE+CcdyPdBwTjI v6aCgfzGCX0cs/wtuqsFm6mvWos/7wKOYw1QsSeF0NV9zQV+DDTOCQ4VcdzyV3K660Bk KEbw==
MIME-Version: 1.0
X-Received: by 10.60.97.74 with SMTP id dy10mr8538117oeb.27.1372630750242; Sun, 30 Jun 2013 15:19:10 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Sun, 30 Jun 2013 15:19:10 -0700 (PDT)
X-Originating-IP: [128.89.255.182]
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943678A937E@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <049.3a20609eab4b4c08a7e01f21f6d6565d@trac.tools.ietf.org> <064.9c6aec3e9813fc2933f6082d75e8e239@trac.tools.ietf.org> <4E1F6AAD24975D4BA5B1680429673943678A937E@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Sun, 30 Jun 2013 18:19:10 -0400
Message-ID: <CAL02cgR0R2bc_d_mmXKovPe0Gzt=-GDiUU-A6cL8UShO=SJgmQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e0115e9fa46b55204e0668002
X-Gm-Message-State: ALoCoQlEK5ry5UJqdkxweNLIB/VUe8kGj6sUr8i0dh9YpvW/k1M6nPRPZurbMeyLNEiOAVnOe/0+
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] #24: Move JWS headers into signature block
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 30 Jun 2013 22:19:15 -0000

--089e0115e9fa46b55204e0668002
Content-Type: text/plain; charset=ISO-8859-1

I was not on the call.  Sorry.

I also disagree with closing this issue.  This is not a crypto question,
it's just syntax cleanliness.  As Mike points out, the proposed syntax
allows the JSON serialization to have the same security properties as the
compact serialization.  The only cost is that protected items have to be
repeated for each signer.

I will definitely be on the call tomorrow.  Happy to discuss then.

--Richard


On Sat, Jun 29, 2013 at 6:42 AM, Mike Jones <Michael.Jones@microsoft.com>wrote:

> Perhaps I'm in an odd frame of mind tonight, because I wouldn't normally
> even consider re-raising a closed issue, but Ben Laurie's advice "why not
> just protect everything" kept running my mind and I realized that the
> current JWS JSON Serialization doesn't allow us to do that in the general
> case.  Specifically, we don't allow a per-signature "protected" headers
> field, which would be necessary to protect the cryptographic parameters if
> different signatures use different algorithms.
>
> So I'd at least like others' thoughts on whether we want to "fill in the
> matrix" for the JWS JSON Serialization and allow header parameters to be
> specified both in protected and unprotected forms, both on a shared and
> per-signature basis.  We currently support 3 of these 4 header parameter
> locations.
>
> Note that we would not do this for JWE, since (as extensively discussed)
> per-recipient protected content is problematic.
>
> For the signature input, if both shared and per-signature protected
> headers were present, we'd need to concatenate the two base64url encoded
> representations together with a separator character between (I'm thinking
> comma (',') because it is distinct from period ('.'), which is also used as
> a separator in the signature input).
>
> I'm fine with this issue remaining closed, but I wanted to at least run
> this possibility by the working group for their input, since it hadn't been
> discussed previously.
>
>                                 Cheers,
>                                 -- Mike
>
> -----Original Message-----
> From: jose issue tracker [mailto:trac+jose@trac.tools.ietf.org]
> Sent: Monday, June 24, 2013 10:57 PM
> To: draft-ietf-jose-json-web-signature@tools.ietf.org; Mike Jones;
> ietf@augustcellars.com
> Cc: jose@ietf.org
> Subject: Re: [jose] #24: Move JWS headers into signature block
>
> #24: Move JWS headers into signature block
>
> Changes (by ietf@augustcellars.com):
>
>  * status:  new => closed
>  * resolution:   => wontfix
>
>
> Comment:
>
>  Closing per the discussion on the teleconference.
>
>  We currently do not have a strong use case for per user items.   It will
>  be possible in future versions to add a protected field to the per signer
>  item and include both in the integrity protection in the event that a use
>  case appears.
>
>  There was no strong recommendation from the CFRG list if a hash
>  substitution attack is either probable or possible.
>
> --
> -------------------------+----------------------------------------------
> -------------------------+---
>  Reporter:  rlb@ipv.sx   |       Owner:  draft-ietf-jose-json-web-
>      Type:  defect       |  signature@tools.ietf.org
>  Priority:  major        |      Status:  closed
> Component:  json-web-    |   Milestone:
>   signature              |     Version:
>  Severity:  -            |  Resolution:  wontfix
>  Keywords:               |
> -------------------------+----------------------------------------------
> -------------------------+---
>
> Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/24#comment:2>
> jose <http://tools.ietf.org/jose/>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

--089e0115e9fa46b55204e0668002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I was not on the call. =A0Sorry.<div><br></div><div>I also=
 disagree with closing this issue. =A0This is not a crypto question, it&#39=
;s just syntax cleanliness. =A0As Mike points out, the proposed syntax allo=
ws the JSON serialization to have the same security properties as the compa=
ct serialization. =A0The only cost is that protected items have to be repea=
ted for each signer.</div>
<div><br></div><div>I will definitely be on the call tomorrow. =A0Happy to =
discuss then.</div><div><br></div><div>--Richard</div></div><div class=3D"g=
mail_extra"><br><br><div class=3D"gmail_quote">On Sat, Jun 29, 2013 at 6:42=
 AM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.Jones@micro=
soft.com" target=3D"_blank">Michael.Jones@microsoft.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Perhaps I&#39;m in an odd frame of mind toni=
ght, because I wouldn&#39;t normally even consider re-raising a closed issu=
e, but Ben Laurie&#39;s advice &quot;why not just protect everything&quot; =
kept running my mind and I realized that the current JWS JSON Serialization=
 doesn&#39;t allow us to do that in the general case. =A0Specifically, we d=
on&#39;t allow a per-signature &quot;protected&quot; headers field, which w=
ould be necessary to protect the cryptographic parameters if different sign=
atures use different algorithms.<br>

<br>
So I&#39;d at least like others&#39; thoughts on whether we want to &quot;f=
ill in the matrix&quot; for the JWS JSON Serialization and allow header par=
ameters to be specified both in protected and unprotected forms, both on a =
shared and per-signature basis. =A0We currently support 3 of these 4 header=
 parameter locations.<br>

<br>
Note that we would not do this for JWE, since (as extensively discussed) pe=
r-recipient protected content is problematic.<br>
<br>
For the signature input, if both shared and per-signature protected headers=
 were present, we&#39;d need to concatenate the two base64url encoded repre=
sentations together with a separator character between (I&#39;m thinking co=
mma (&#39;,&#39;) because it is distinct from period (&#39;.&#39;), which i=
s also used as a separator in the signature input).<br>

<br>
I&#39;m fine with this issue remaining closed, but I wanted to at least run=
 this possibility by the working group for their input, since it hadn&#39;t=
 been discussed previously.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Cheers,<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Mike<br>
<div class=3D"im"><br>
-----Original Message-----<br>
From: jose issue tracker [mailto:<a href=3D"mailto:trac%2Bjose@trac.tools.i=
etf.org">trac+jose@trac.tools.ietf.org</a>]<br>
Sent: Monday, June 24, 2013 10:57 PM<br>
To: <a href=3D"mailto:draft-ietf-jose-json-web-signature@tools.ietf.org">dr=
aft-ietf-jose-json-web-signature@tools.ietf.org</a>; Mike Jones; <a href=3D=
"mailto:ietf@augustcellars.com">ietf@augustcellars.com</a><br>
Cc: <a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
Subject: Re: [jose] #24: Move JWS headers into signature block<br>
<br>
#24: Move JWS headers into signature block<br>
<br>
Changes (by <a href=3D"mailto:ietf@augustcellars.com">ietf@augustcellars.co=
m</a>):<br>
<br>
=A0* status: =A0new =3D&gt; closed<br>
=A0* resolution: =A0 =3D&gt; wontfix<br>
<br>
<br>
Comment:<br>
<br>
=A0Closing per the discussion on the teleconference.<br>
<br>
=A0We currently do not have a strong use case for per user items. =A0 It wi=
ll<br>
=A0be possible in future versions to add a protected field to the per signe=
r =A0item and include both in the integrity protection in the event that a =
use =A0case appears.<br>
<br>
=A0There was no strong recommendation from the CFRG list if a hash =A0subst=
itution attack is either probable or possible.<br>
<br>
--<br>
-------------------------+----------------------------------------------<br=
>
</div>-------------------------+---<br>
<div class=3D"im">=A0Reporter: =A0rlb@ipv.sx =A0 | =A0 =A0 =A0 Owner: =A0dr=
aft-ietf-jose-json-web-<br>
=A0 =A0 =A0Type: =A0defect =A0 =A0 =A0 | =A0<a href=3D"mailto:signature@too=
ls.ietf.org">signature@tools.ietf.org</a><br>
=A0Priority: =A0major =A0 =A0 =A0 =A0| =A0 =A0 =A0Status: =A0closed<br>
Component: =A0json-web- =A0 =A0| =A0 Milestone:<br>
=A0 signature =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 Version:<br>
=A0Severity: =A0- =A0 =A0 =A0 =A0 =A0 =A0| =A0Resolution: =A0wontfix<br>
=A0Keywords: =A0 =A0 =A0 =A0 =A0 =A0 =A0 |<br>
-------------------------+----------------------------------------------<br=
>
</div>-------------------------+---<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
Ticket URL: &lt;<a href=3D"http://trac.tools.ietf.org/wg/jose/trac/ticket/2=
4#comment:2" target=3D"_blank">http://trac.tools.ietf.org/wg/jose/trac/tick=
et/24#comment:2</a>&gt;<br>
jose &lt;<a href=3D"http://tools.ietf.org/jose/" target=3D"_blank">http://t=
ools.ietf.org/jose/</a>&gt;<br>
<br>
_______________________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
</div></div></blockquote></div><br></div>

--089e0115e9fa46b55204e0668002--

From rlb@ipv.sx  Sun Jun 30 15:41:07 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB9721F9BA2 for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 15:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level: 
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDJgQ8mueLua for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 15:41:02 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC3721F9B21 for <jose@ietf.org>; Sun, 30 Jun 2013 15:41:02 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wo10so3639081obc.31 for <jose@ietf.org>; Sun, 30 Jun 2013 15:41:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=AAvs5AheMSMZqEMVeBCzoTdkcRbuaLH/kPnqB3QGE9U=; b=azlF1Ui3g3hzMmBbzVWy+Wkt/T4SscYdrVuqiO6da6wVNAmQk4vULpItQ7hT+5PQfw z0sY2jM+4gz5/wbbnrMtxWkqi1w2q68HO0QulUMETaZGHnep1KcXd8BkkYdYiU12XzrJ Pa+j4gxNaFFfnda6VX089svifVtNkrUGpw1OLOLKXpHUZwHy1Eva4Rxq0rvMWJhhPUk8 uW2Xy8ek2p4lHNFhSHSC6euSTuDMYmNPNRYNod5HKtGVw1MaequANsJifAQurvILPPeR rQp8R9T8BTb1Zs0+nTVIMMHvQ0zQ3I/1eMSTMqtXe0y7Bm2OX2VQCovqmw4DTtnlx7kT r6eQ==
MIME-Version: 1.0
X-Received: by 10.182.165.133 with SMTP id yy5mr3749881obb.89.1372632061148; Sun, 30 Jun 2013 15:41:01 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Sun, 30 Jun 2013 15:41:01 -0700 (PDT)
X-Originating-IP: [128.89.255.182]
In-Reply-To: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com>
References: <020a01ce71c4$204cb5f0$60e621d0$@augustcellars.com>
Date: Sun, 30 Jun 2013 18:41:01 -0400
Message-ID: <CAL02cgSo7ab5RkfCjTjhWvqw_oeNpsMr7QP8Lxu+Kmb+fka0yQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Jim Schaad <ietf@augustcellars.com>
Content-Type: multipart/alternative; boundary=001a11c2e76a698fb504e066cef6
X-Gm-Message-State: ALoCoQkMNoe8iGnuZ6XbGGXPeA/Hu6aqsqgwthoDeviDGZv5MCy51Zc/NL+1xUpc11/bdhUkgyoi
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Teleconference July 1 Agenda
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 30 Jun 2013 22:41:07 -0000

--001a11c2e76a698fb504e066cef6
Content-Type: text/plain; charset=ISO-8859-1

For my open actions under ISSUE-6:

Create algorithm table reflecting meember requirement levels before 1 June:

alg/enc         Required fields
============================================
RSA1_5          encrypted_key
RSA-OAEP        encrypted_key
A128KW          encrypted_key
A256KW          encrypted_key
dir
ECDH-ES         epk, apu
ECDH-ES+A128KW  encrypted_key, epk, apu
ECDH-ES+A256KW  encrypted_key, epk, apu
--------------------------------------------
A128CBC-HS256   iv, tag
A256CBC-HS512   iv, tag
A128GCM         iv, tag
A256GCM         iv, tag


Add evaluation for protection to table of all fields:
-- There are no parameters where protection is REQUIRED for security
purposes.
-- If one of the PSS algorithms is used ("PS256"/"PS512"), then the "alg"
field MUST be protected, in order to protect the hash algorithm used.




On Tue, Jun 25, 2013 at 12:50 PM, Jim Schaad <ietf@augustcellars.com> wrote:

> Agenda has been posted
> http://www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interim-2013-jose-3
> ****
>
> ** **
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

--001a11c2e76a698fb504e066cef6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">For my open actions under ISSUE-6:<div><br></div><div>Crea=
te algorithm table reflecting meember requirement levels before 1 June:<br>=
</div><div><br></div><div><div>alg/enc =A0 =A0 =A0 =A0 Required fields</div=
><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
<div>RSA1_5 =A0 =A0 =A0 =A0 =A0encrypted_key</div><div>RSA-OAEP =A0 =A0 =A0=
 =A0encrypted_key</div><div>A128KW =A0 =A0 =A0 =A0 =A0encrypted_key</div><d=
iv>A256KW =A0 =A0 =A0 =A0 =A0encrypted_key</div><div>dir</div><div>ECDH-ES =
=A0 =A0 =A0 =A0 epk, apu</div><div>ECDH-ES+A128KW =A0encrypted_key, epk, ap=
u</div>
<div>ECDH-ES+A256KW =A0encrypted_key, epk, apu</div><div>------------------=
--------------------------</div><div>A128CBC-HS256 =A0 iv, tag</div><div>A2=
56CBC-HS512 =A0 iv, tag</div><div>A128GCM =A0 =A0 =A0 =A0 iv, tag</div><div=
>A256GCM =A0 =A0 =A0 =A0 iv, tag</div>
</div><div><br></div><div><br></div><div>Add evaluation for protection to t=
able of all fields:<br></div><div>-- There are no parameters where protecti=
on is REQUIRED for security purposes.</div><div>-- If one of the PSS algori=
thms is used (&quot;PS256&quot;/&quot;PS512&quot;), then the &quot;alg&quot=
; field MUST be protected, in order to protect the hash algorithm used.</di=
v>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Tue, Jun 25, 2013 at 12:50 PM, Jim Schaad <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:ietf@augustcellars.com" target=3D"_blank">=
ietf@augustcellars.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal">Agenda has been posted <a href=3D"http:/=
/www.ietf.org/proceedings/interim/2013/07/01/jose/agenda/agenda-interim-201=
3-jose-3" target=3D"_blank">http://www.ietf.org/proceedings/interim/2013/07=
/01/jose/agenda/agenda-interim-2013-jose-3</a><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div><br>_______________=
________________________________<br>
jose mailing list<br>
<a href=3D"mailto:jose@ietf.org">jose@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/jose" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/jose</a><br>
<br></blockquote></div><br></div>

--001a11c2e76a698fb504e066cef6--

From mpeck@mitre.org  Sun Jun 30 21:49:17 2013
Return-Path: <mpeck@mitre.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD26321F9F06 for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 21:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6rG1dN3D6Hk for <jose@ietfa.amsl.com>; Sun, 30 Jun 2013 21:49:10 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFC321F9EC3 for <jose@ietf.org>; Sun, 30 Jun 2013 21:49:10 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id DAA441F02EA; Mon,  1 Jul 2013 00:49:09 -0400 (EDT)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id BD3391F02B5; Mon,  1 Jul 2013 00:49:09 -0400 (EDT)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.162]) by IMCCAS02.MITRE.ORG ([129.83.29.69]) with mapi id 14.02.0342.003; Mon, 1 Jul 2013 00:49:09 -0400
From: "Peck, Michael A" <mpeck@mitre.org>
To: Carsten Bormann <cabo@tzi.org>, Jim Schaad <ietf@augustcellars.com>
Thread-Topic: [jose] Issue #13 - use AES-GCM for Key Wrapping
Thread-Index: Ac5xxGXFBxC1FARbRReYSyWIKtodvABC/E+gACnYKgAAHCJ6gACK81fg
Date: Mon, 1 Jul 2013 04:49:08 +0000
Message-ID: <8B4C063947CD794BB6FF90C78BAE9B321F066C96@IMCMBX04.MITRE.ORG>
References: <020f01ce71c4$80b8da90$822a8fb0$@augustcellars.com> <255B9BB34FB7D647A506DC292726F6E1151BE45229@WSMSG3153V.srv.dir.telstra.com> <049501ce7356$31644680$942cd380$@augustcellars.com> <DEE3F4FD-0B7D-49CA-95FC-40741D9C8BED@tzi.org>
In-Reply-To: <DEE3F4FD-0B7D-49CA-95FC-40741D9C8BED@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.83.31.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "<jose@ietf.org>" <jose@ietf.org>
Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Jul 2013 04:49:18 -0000

The concerns I raised in issue #28 also apply here, though the potential co=
nsequences may be worse here since it's keys that are being encrypted. =20
GCM is not safe to use without automated key management. =20

ECDH-ES+AES128GCMKW / ECDH-ES+AES256GCMKW seem OK, but AES-GCM Key Wrap dir=
ectly using a pre-shared key is unsafe. =20

I don't think adding Security Considerations text is sufficient, because it=
's not practical to expect implementations will be able to keep track of ho=
w many times the same pre-shared key has been used.

As there appears to be a use case for AES-GCM Key Wrapping, could we explor=
e options to try to ensure a new key is used for each AES-GCM Key Wrap oper=
ation?  For example, run the pre-shared key through the Counter Mode KDF (N=
IST SP 800-108 Section 5.1) to get the AES-GCM Key Wrap Key -- the KDF coul=
d mix in information like algorithm identifiers (might help prevent the iss=
ue James Manger pointed out of mixing up AES-GCM Content Encryption with AE=
S-GCM Key Wrap, though I still think direct encryption should be prohibited=
 with AES-GCM Content Encryption) and  a sender-provided random value (to m=
ake sure a new key is used each time).
Section 2 of SP 800-108 says its KDFs can be used to derive keys from a pre=
-shared key.

Mike

>-----Original Message-----
>From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
>Carsten Bormann
>Sent: Friday, June 28, 2013 2:14 AM
>To: Jim Schaad
>Cc: Manger, James H; <jose@ietf.org>
>Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
>
>Well, we actually like to use AES-CCM in the small devices.
>Not having to do AES decrypt is a good thing, indeed.
>
>Sent from my mobile device
>
>On 27.06.2013, at 18:48, "Jim Schaad" <ietf@augustcellars.com> wrote:
>
>> James,
>>
>> The small devices use case does present a reason for wanting to use AES-
>GCM rather than AESKW for this case.  Specifically, there is no need to ha=
ve
>silicon devoted to doing AES decrypt.  All operations can be done just wit=
h AES
>encrypt.
>>
>> jim
>>
>>> -----Original Message-----
>>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of
>>> Manger, James H
>>> Sent: Wednesday, June 26, 2013 7:40 PM
>>> To: jose@ietf.org
>>> Subject: Re: [jose] Issue #13 - use AES-GCM for Key Wrapping
>>>
>>> I don't think we should standardize draft-jones-jose-aes-gcm-key-wrap-0=
0.
>No
>>> rationale is apparent. We already have an AES-based key wrap algorithm
>>> (A128KW, A256KW), which has a 64-bit size overhead. The AES-GCM key
>>> wrap algorithm in this draft add almost no useful properties, but has a=
 224-
>bit
>>> size overhead.
>>>
>>> I like the concatenation of the IV, ciphertext, and tag byte arrays. Bu=
t
>doing
>>> this here while content encryption serializes the same values as dot-
>separated
>>> B64 blobs does smell of poor ad hoc design. It is nice to highlight how=
 a
>>> previous choice complicates extending JOSE to other algorithms, but onl=
y if
>>> we then fix that previous choice.
>>>
>>> If the additional authenticated data (AAD) was used to bind the CEK
>algorithm
>>> id (or other context info, as ConcatKDF does) to the wrapped key, then
>there
>>> would at least be an extra security property that would make this key w=
rap
>>> algorithm worth considering. For instance, instead of AAD being empty,
>AAD
>>> could be the "key wrap: " + "enc" value.
>>>
>>> By reusing a CEK algorithm as a KEK algorithm, and supporting direct
>>> encryption, we substantially increase the risk that an attacker can
>rearrange
>>> some encrypted content so a legitimate recipient treats it as an encryp=
ted
>key
>>> leading to security flaws.
>>>
>>> For example, Alice sends "Start of PIN =3D 8" confidentially to Bob:
>>>  {alg:dir,enc:A128GCM,kid:1}..iv.ciphertext.tag
>>> An attacker seeing this JOSE message learns nothing about the 1st digit=
 of
>the
>>> PIN.
>>> But if the attacker sends 10 messages to Bob for 10 guess of that digit=
:
>>>
>>>
>{alg:A128GCMKW,enc:A128GCM,kid:1}.iv|ciphertext|tag.ivN.ciphertextN.tag
>>> N
>>> where ivN.ciphertextN.tagN are calculated using an AES key of "Start of
>PIN =3D
>>> <N>", then 9 messages will cause errors, while 1 message will be accept=
ed
>--
>>> revealing the supposedly confidential information in 10 guesses instead=
 of
>>> 2^128.
>>>
>>> Actually the above attack does not quite work for the compact encoding =
as
>>> AAD is never empty for content encryption. I not certain for the JSON
>>> encoding. In any case, an explicit and unambiguous AAD value for key
>>> wrapping would be good.
>>>
>>> Finally, a key wrap algorithm like this should go to the IETF crypto gr=
oup
>>> (CRFG) instead of being invented in JOSE. We have already spent a year
>>> unpicking a JOSE-special AEAD algorithm.
>>>
>>> --
>>> James Manger
>>>
>>>
>>>> -----Original Message-----
>>>> From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf
>>>> Of Jim Schaad
>>>> Sent: Wednesday, 26 June 2013 2:53 AM
>>>> To: jose@ietf.org
>>>> Subject: [jose] Issue #13 - use AES-GCM for Key Wrapping
>>>>
>>>> We now have two documents   one from Richard and one from Mike
>which
>>>> provide the two different ways that have been proposed for doing key
>>>> wrapping with an AEAD algorithm.
>>>>
>>>> Please review the two documents and provide comments to the list.
>>>>
>>>> Jim
>>>=20

