Re: [OAUTH-WG] Question for encrypted POP Key

Jim Schaad <ietf@augustcellars.com> Mon, 20 January 2020 18:58 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79738120875 for <oauth@ietfa.amsl.com>; Mon, 20 Jan 2020 10:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLLu6HZxj4f3 for <oauth@ietfa.amsl.com>; Mon, 20 Jan 2020 10:58:24 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2835120945 for <oauth@ietf.org>; Mon, 20 Jan 2020 10:58:23 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 20 Jan 2020 10:58:19 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: <draft-ietf-oauth-proof-of-possession@ietf.org>
CC: 'oauth' <oauth@ietf.org>
References:
In-Reply-To:
Date: Mon, 20 Jan 2020 10:58:15 -0800
Message-ID: <002601d5cfc3$942e43d0$bc8acb70$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdXPwu8/l3HG9L7fRL2eLS+vwxL9CgAAJ62g
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/imIxQoItBCCl42lZZ8cE7pygtjo>
Subject: Re: [OAUTH-WG] Question for encrypted POP Key
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 18:58:32 -0000

Never mind, I just saw the answer.

-----Original Message-----
From: Jim Schaad <ietf@augustcellars.com> 
Sent: Monday, January 20, 2020 10:57 AM
To: 'draft-ietf-oauth-proof-of-possession@ietf.org'
<draft-ietf-oauth-proof-of-possession@ietf.org>
Cc: 'oauth' <oauth@ietf.org>
Subject: Question for encrypted POP Key

I am trying to deal with some of the various confirmation methods for a  POP
token.  The question that I have is about the format of the JOSE Encrypted
value to be used.  The document has an example of a compact serialization
for this concept, it does not have an example of a JSON serialization.  The
document appears to be silent about the legal serialization formats except
for this example.  

Is only the compact serialization format allowed or are all three
serialization formats allowed?

Jim