[ltans] implementations of RFC4998 and JOSE/JSON versions
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 11 August 2021 15:29 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ltans@ietfa.amsl.com
Delivered-To: ltans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D33113A0DF6 for <ltans@ietfa.amsl.com>; Wed, 11 Aug 2021 08:29:55 -0700 (PDT)
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, 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 vTS4ZxurLzRd for <ltans@ietfa.amsl.com>; Wed, 11 Aug 2021 08:29:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3A733A1A42 for <ltans@ietf.org>; Wed, 11 Aug 2021 08:29:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 92E193899F for <ltans@ietf.org>; Wed, 11 Aug 2021 11:34:28 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cVe42JjiTYbv for <ltans@ietf.org>; Wed, 11 Aug 2021 11:34:25 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1BE01389A4 for <ltans@ietf.org>; Wed, 11 Aug 2021 11:34:25 -0400 (EDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AA791899 for <ltans@ietf.org>; Wed, 11 Aug 2021 11:29:43 -0400 (EDT)
To: ltans@ietf.org
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <7a6eb814-6af3-96a6-1e54-e62b8510e386@sandelman.ca>
Date: Wed, 11 Aug 2021 11:29:43 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ltans/ru21AXjqYNClZjb1oYB2nBqHNXY>
Subject: [ltans] implementations of RFC4998 and JOSE/JSON versions
X-BeenThere: ltans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: LTANS Working Group <ltans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ltans>, <mailto:ltans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ltans/>
List-Post: <mailto:ltans@ietf.org>
List-Help: <mailto:ltans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltans>, <mailto:ltans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2021 15:29:56 -0000
Hi, a question based upon reading/reviewing of (not yet released) OPC UA provisioning specification. a) are there RFC4998 implementations out there in field? b) how to do with with JOSE signed JSON objects. We can treat this as opaque bytes, but it feels a bit wrong.
- [ltans] implementations of RFC4998 and JOSE/JSON … Michael Richardson