--- 1/draft-ietf-ace-cwt-proof-of-possession-09.txt 2019-10-30 18:13:09.524268410 -0700 +++ 2/draft-ietf-ace-cwt-proof-of-possession-10.txt 2019-10-30 18:13:09.560269324 -0700 @@ -1,25 +1,25 @@ ACE M. Jones Internet-Draft Microsoft Intended status: Standards Track L. Seitz -Expires: April 20, 2020 RISE SICS +Expires: May 2, 2020 RISE SICS G. Selander Ericsson AB S. Erdtman Spotify H. Tschofenig Arm Ltd. - October 18, 2019 + October 30, 2019 Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs) - draft-ietf-ace-cwt-proof-of-possession-09 + draft-ietf-ace-cwt-proof-of-possession-10 Abstract This specification describes how to declare in a CBOR Web Token (CWT) (which is defined by RFC 8392) that the presenter of the CWT possesses a particular proof-of-possession key. Being able to prove possession of a key is also sometimes described as being the holder- of-key. This specification provides equivalent functionality to "Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)" (RFC 7800) but using Concise Binary Object Representation (CBOR) and CWTs @@ -34,21 +34,21 @@ 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 https://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." - This Internet-Draft will expire on April 20, 2020. + This Internet-Draft will expire on May 2, 2020. Copyright Notice Copyright (c) 2019 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 (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -137,27 +137,28 @@ By including a "cnf" (confirmation) claim in a CWT, the issuer of the CWT declares that the presenter possesses a particular key and that the recipient can cryptographically confirm that the presenter has possession of that key. The value of the "cnf" claim is a CBOR map (which is defined in Section 2.1 of [RFC7049]) and the members of that map identify the proof-of-possession key. The presenter can be identified in one of several ways by the CWT, depending upon the application requirements. For instance, some applications may use the CWT "sub" (subject) claim [RFC8392], to - identify the presenter. Other applications may use the "iss" claim - to identify the presenter. In some applications, the subject - identifier might be relative to the issuer identified by the "iss" - (issuer) claim [RFC8392]. The actual mechanism used is dependent - upon the application. The case in which the presenter is the subject - of the CWT is analogous to Security Assertion Markup Language (SAML) - 2.0 [OASIS.saml-core-2.0-os] SubjectConfirmation usage. + identify the presenter. Other applications may use the "iss" + (issuer) claim [RFC8392] to identify the presenter. In some + applications, the subject identifier might be relative to the issuer + identified by the "iss" claim. The actual mechanism used is + dependent upon the application. The case in which the presenter is + the subject of the CWT is analogous to Security Assertion Markup + Language (SAML) 2.0 [OASIS.saml-core-2.0-os] SubjectConfirmation + usage. 3.1. Confirmation Claim The "cnf" claim in the CWT is used to carry confirmation methods. Some of them use proof-of-possession keys while others do not. This design is analogous to the SAML 2.0 [OASIS.saml-core-2.0-os] SubjectConfirmation element in which a number of different subject confirmation methods can be included (including proof-of-possession key information). @@ -237,21 +238,21 @@ When the key held by the presenter is a symmetric key, the "Encrypted_COSE_Key" member is an encrypted COSE_Key [RFC8152] representing the symmetric key encrypted to a key known to the recipient using COSE_Encrypt or COSE_Encrypt0. The following example illustrates a symmetric key that could subsequently be encrypted for use in the "Encrypted_COSE_Key" member: { /kty/ 1 : /Symmetric/ 4, - /alg/ 3 : /HMAC256//256/ 5, + /alg/ 3 : /HMAC 256-256/ 5, /k/ -1 : h'6684523ab17337f173500e5728c628547cb37df e68449c65f885d1b73b49eae1' } The COSE_Key representation is used as the plaintext when encrypting the key. The following example CWT Claims Set of a CWT illustrates the use of an encrypted symmetric key as the "Encrypted_COSE_Key" member value: @@ -619,31 +620,36 @@ [RFC8610] Birkholz, H., Vigano, C., and C. Bormann, "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures", RFC 8610, DOI 10.17487/RFC8610, June 2019, . Acknowledgements Thanks to the following people for their reviews of the - specification: Roman Danyliw, Christer Holmberg, Benjamin Kaduk, Yoav - Nir, Michael Richardson, and Jim Schaad. + specification: Roman Danyliw, Christer Holmberg, Benjamin Kaduk, + Mirja Kuehlewind, Yoav Nir, Michael Richardson, Adam Roach, Eric + Vyncke, and Jim Schaad. Ludwig Seitz and Goeran Selander worked on this document as part of the CelticPlus projects CyberWI and CRITISEC, with funding from Vinnova. Document History [[ to be removed by the RFC Editor before publication as an RFC ]] + -10 + + o Addressed IESG review comments by Adam Roach and Eric Vyncke. + -09 o Addressed Gen-ART review comments by Christer Holmberg and SecDir review comments by Yoav Nir. -08 o Addressed remaining Area Director review comments by Benjamin Kaduk.