Last Call: <draft-ietf-ace-cwt-proof-of-possession-07.txt> (Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)) to Proposed Standard

The IESG <> Wed, 25 September 2019 13:09 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id E6DCC12022C; Wed, 25 Sep 2019 06:09:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-ace-cwt-proof-of-possession-07.txt> (Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Wed, 25 Sep 2019 06:09:34 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Sep 2019 13:09:35 -0000

The IESG has received a request from the Authentication and Authorization for
Constrained Environments WG (ace) to consider the following document: -
'Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)'
  <draft-ietf-ace-cwt-proof-of-possession-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2019-10-09. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   This specification describes how to declare in a CBOR Web Token (CWT)
   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 CBOR and
   CWTs rather than JSON and JWTs.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.