W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 17682] Clear Key: Document how keys and key IDs are associated

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Oct 2013 20:33:38 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-17682-2486-kZ5gdPOW2N@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17682

--- Comment #15 from David Dorwin <ddorwin@google.com> ---
The first draft defines "Base64url Encoding" [1], and the second draft says the
"k" value " is represented as the base64url encoding of the octet sequence..."

We should use "base64url encoding" in EME for consistency. This includes for my
proposed additional restrictions on "kid" since it will be easiser for everyone
if "k" and "kid" follow similar rules.

The definition also addresses the character set issue, making the
"ASCII-compatible character encoding" discussion obsolete.

The "Base64url Encoding" also says that "all trailing '=' characters [are]
omitted." This means that for "k" and any other fields we specify "base64url
encoding", padding is disallowed (rather than required, as I had proposed).
While UAs will need to add padding, at least there is no need to support both
cases.

[1] http://tools.ietf.org/html/draft-ietf-jose-json-web-key-16#section-2
[2]
http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-16#section-5.4.1

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 2 October 2013 20:33:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:44 UTC