idnits 2.17.1 draft-hallambaker-joseunencoded-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 25, 2015) is 3320 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force (IETF) Phillip Hallam-Baker 2 INTERNET-DRAFT Comodo Group Inc. 3 Intended Status: Standards Track March 25, 2015 4 Expires: September 26, 2015 6 JOSE Direct Compact Serialization 7 draft-hallambaker-joseunencoded-01 9 Abstract 11 An alternative serialization for JOSE signatures is presented in 12 which the headers, signature and payload are encoded directly, 13 without Base64 encoding. Use of this format requires the use of a 14 binary transport that does not 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 Copyright Notice 33 Copyright (c) 2015 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 50 2. Serialization . . . . . . . . . . . . . . . . . . . . . . . . 3 51 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 53 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Definitions 60 1.1. Requirements Language 62 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 63 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 64 document are to be interpreted as described in RFC 2119 [RFC2119]. 66 2. Serialization 68 In the JWS Direct Serialization, no JWS Unprotected Header is used. 69 In this case, the JOSE Header and the JWS Protected Header are the 70 same. 72 In the JWS Direct Serialization, a JWS is represented as the 73 concatenation: 75 UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.' || 77 (JWS Signature) 79 The calculation of the signature is performed over the octet sequence 80 that corresponds to the concatenation: 82 UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.' 84 3. Acknowledgements 86 Mike Jones provided advice on an early version of this proposal. 88 4. Security Considerations 90 The security considerations presented in [I-D.ietf-jose-json-web- 91 signature] apply. 93 5. IANA Considerations 95 Type name: application 97 Subtype name: jose+direct 99 Required parameters: n/a 101 Optional parameters: n/a 103 Encoding considerations: 8bit; application/jose+direct values are 104 represented as a JSON Object; UTF-8 encoding SHOULD be employed for 105 the JSON object. 107 Security considerations: See the Security Considerations section of 108 [I-D.ietf-jose-json-web-signature] 110 Interoperability considerations: n/a 112 Published specification: [I-D.ietf-jose-json-web-signature] 114 Applications that use this media type: TBD 116 Fragment identifier considerations: n/a 118 Additional information: Magic number(s): n/a, File extension(s): n/a, 119 Macintosh file type code(s): n/a 121 Person & email address to contact for further information: Phillip 122 Hallam-Baker (phill@hallambaker.com) 124 Intended usage: COMMON 126 Restrictions on usage: none 128 Author: Phillip Hallam-Baker (phill@hallambaker.com) 130 Change Controller: IESG 132 Provisional registration? No 134 6. References 136 6.1. Normative References 138 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 139 Requirement Levels", BCP 14, RFC 2119, March 1997. 141 [I-D.ietf-jose-json-web-signature] Jones, M,Bradley, J,Sakimura, N, 142 "JSON Web Signature (JWS)", Internet-Draft draft-ietf- 143 jose-json-web-signature-41, 16 January 2015. 145 Author's Address 147 Phillip Hallam-Baker 148 Comodo Group Inc. 150 philliph@comodo.com