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

From: Mike Jones <[email-masked]>
Date: Thu, 15 Jan 2015 20:12:45 +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