[OAUTH-WG] Proposed RFC Editor's note for draft-ietf-oauth-json-web-token

Mike Jones <Michael.Jones@microsoft.com> Thu, 15 January 2015 20:13 UTC

Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4327D1B32C3 for <oauth@ietfa.amsl.com>; Thu, 15 Jan 2015 12:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0qt_Dw-fMUs for <oauth@ietfa.amsl.com>; Thu, 15 Jan 2015 12:13:02 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0139.outbound.protection.outlook.com [65.55.169.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A941B3264 for <oauth@ietf.org>; Thu, 15 Jan 2015 12:13:02 -0800 (PST)
Received: from BLUPR03MB152.namprd03.prod.outlook.com (10.255.212.28) by BLUPR03MB002.namprd03.prod.outlook.com (10.255.208.36) with Microsoft SMTP Server (TLS) id 15.1.65.13; Thu, 15 Jan 2015 20:13:00 +0000
Received: from CH1PR03CA011.namprd03.prod.outlook.com (10.255.156.156) by BLUPR03MB152.namprd03.prod.outlook.com (10.255.212.28) with Microsoft SMTP Server (TLS) id 15.1.53.17; Thu, 15 Jan 2015 20:12:59 +0000
Received: from BN1AFFO11FD059.protection.gbl (10.255.156.132) by CH1PR03CA011.outlook.office365.com (10.255.156.156) with Microsoft SMTP Server (TLS) id 15.1.59.20 via Frontend Transport; Thu, 15 Jan 2015 20:12:58 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD059.mail.protection.outlook.com (10.58.53.74) with Microsoft SMTP Server (TLS) id 15.1.49.13 via Frontend Transport; Thu, 15 Jan 2015 20:12:58 +0000
Received: from TK5EX14MBXC291.redmond.corp.microsoft.com ([169.254.2.131]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0210.003; Thu, 15 Jan 2015 20:12:47 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: Proposed RFC Editor's note for draft-ietf-oauth-json-web-token
Thread-Index: AdAw/598kpzhHacHQXyPC17umOvrvQ==
Date: Thu, 15 Jan 2015 20:12:45 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739439E650F2C@TK5EX14MBXC291.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.34]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739439E650F2CTK5EX14MBXC291r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
Received-SPF: Pass (protection.outlook.com: domain of microsoft.com designates 131.107.125.37 as permitted sender) receiver=protection.outlook.com; client-ip=131.107.125.37; helo=mail.microsoft.com;
Authentication-Results: spf=pass (sender IP is 131.107.125.37) smtp.mailfrom=Michael.Jones@microsoft.com;
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(438002)(288314003)(199003)(65554003)(105444003)(189002)(229853001)(84326002)(106466001)(6806004)(19580395003)(97736003)(86612001)(81156004)(46102003)(19300405004)(86362001)(110136001)(69596002)(230783001)(54356999)(55846006)(512954002)(102836002)(15975445007)(64706001)(26826002)(62966003)(104016003)(66066001)(2656002)(33656002)(87936001)(50986999)(19619215002)(19625215002)(16236675004)(92566002)(2900100001)(2920100001)(77156002)(68736005)(2930100002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB152; H:mail.microsoft.com; FPR:; SPF:Pass; MLV:ovrnspm; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-DmarcStatus-Test: Passed
X-DmarcAction-Test: None
X-Microsoft-Antispam: UriScan:;UriScan:;
X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(3003004)(3005004); SRVR:BLUPR03MB152;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:BLUPR03MB152;
X-Forefront-PRVS: 0457F11EAF
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB152;
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 15 Jan 2015 20:12:58.7796 (UTC)
X-MS-Exchange-CrossTenant-Id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=72f988bf-86f1-41af-91ab-2d7cd011db47; Ip=[131.107.125.37]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB152
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB002;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/DResyQqckOn2NKUrqaQFt1rI_Wc>
Cc: Derek Atkins <derek@ihtfp.com>, "oauth@ietf.org" <oauth@ietf.org>
Subject: [OAUTH-WG] Proposed RFC Editor's note for draft-ietf-oauth-json-web-token
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 20:13:05 -0000

Hi Kathleen,

After you approved the JWT spec, while editing the JOSE specs, I found a missing reference to the Unicode spec that was also missing in the JWT spec, which had already been approved by that point.  Per our conversation, I propose that you send this editor's note:

==== RFC Editor's Note for draft-ietf-oauth-json-web-token ====

A reference to the Unicode specification is missing.  Please make these changes to the XML source:

OLD:
                 algorithm is, the Unicode string encoding
NEW:
                 algorithm is, the Unicode <xref target="UNICODE"/> string encoding

After the reference to RFC 20, ADD:

      <reference anchor="UNICODE" target="http://www.unicode.org/versions/latest/">
               <front>
                 <title abbrev="Unicode">The Unicode Standard</title>
                 <author>
                   <organization>The Unicode Consortium</organization>
                   <address />
                 </author>
                 <date year="1991-"/>
               </front>
               <!--
               <annotation>
                 Note that this reference is to the latest version of Unicode,
                 rather than to a specific release.  It is not expected that future changes in
                 the UNICODE specification will impact the syntax of JSON or the UTF-8 encoding.
               </annotation>
               -->
      </reference>

                                                            Thank you,
                                                            -- Mike