Internet DRAFT - draft-hallambaker-joseunencoded
draft-hallambaker-joseunencoded
Internet Engineering Task Force (IETF) Phillip Hallam-Baker
INTERNET-DRAFT Comodo Group Inc.
Intended Status: Standards Track March 25, 2015
Expires: September 26, 2015
JOSE Direct Compact Serialization
draft-hallambaker-joseunencoded-01
Abstract
An alternative serialization for JOSE signatures is presented in
which the headers, signature and payload are encoded directly,
without Base64 encoding. Use of this format requires the use of a
binary transport that does not
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Hallam-Baker September 26, 2015 [Page 1]
Internet-Draft JOSE Unencoded Serialization March 2015
Table of Contents
1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Serialization . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4
Hallam-Baker September 26, 2015 [Page 2]
Internet-Draft JOSE Unencoded Serialization March 2015
1. Definitions
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Serialization
In the JWS Direct Serialization, no JWS Unprotected Header is used.
In this case, the JOSE Header and the JWS Protected Header are the
same.
In the JWS Direct Serialization, a JWS is represented as the
concatenation:
UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.' ||
(JWS Signature)
The calculation of the signature is performed over the octet sequence
that corresponds to the concatenation:
UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.'
3. Acknowledgements
Mike Jones provided advice on an early version of this proposal.
4. Security Considerations
The security considerations presented in [I-D.ietf-jose-json-web-
signature] apply.
5. IANA Considerations
Type name: application
Subtype name: jose+direct
Required parameters: n/a
Optional parameters: n/a
Encoding considerations: 8bit; application/jose+direct values are
represented as a JSON Object; UTF-8 encoding SHOULD be employed for
the JSON object.
Hallam-Baker September 26, 2015 [Page 3]
Internet-Draft JOSE Unencoded Serialization March 2015
Security considerations: See the Security Considerations section of
[I-D.ietf-jose-json-web-signature]
Interoperability considerations: n/a
Published specification: [I-D.ietf-jose-json-web-signature]
Applications that use this media type: TBD
Fragment identifier considerations: n/a
Additional information: Magic number(s): n/a, File extension(s): n/a,
Macintosh file type code(s): n/a
Person & email address to contact for further information: Phillip
Hallam-Baker (phill@hallambaker.com)
Intended usage: COMMON
Restrictions on usage: none
Author: Phillip Hallam-Baker (phill@hallambaker.com)
Change Controller: IESG
Provisional registration? No
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[I-D.ietf-jose-json-web-signature] Jones, M,Bradley, J,Sakimura, N,
"JSON Web Signature (JWS)", Internet-Draft draft-ietf-
jose-json-web-signature-41, 16 January 2015.
Author's Address
Phillip Hallam-Baker
Comodo Group Inc.
philliph@comodo.com
Hallam-Baker September 26, 2015 [Page 4]