Re: [OAUTH-WG] Type Metadata for SD-JWT VC

Jacob Ward <jacob.ward@spruceid.com> Wed, 03 April 2024 18:08 UTC

Return-Path: <jacob.ward@spruceid.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 F192FC14F6B7 for <oauth@ietfa.amsl.com>; Wed, 3 Apr 2024 11:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=spruceid.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-JMSe1jLtAy for <oauth@ietfa.amsl.com>; Wed, 3 Apr 2024 11:08:17 -0700 (PDT)
Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2E9C14F684 for <oauth@ietf.org>; Wed, 3 Apr 2024 11:08:17 -0700 (PDT)
Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-611248b4805so1603777b3.0 for <oauth@ietf.org>; Wed, 03 Apr 2024 11:08:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spruceid.com; s=google; t=1712167696; x=1712772496; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nqv3C1BVtGg/wUFoW1PjnMhIDdPmbl6aF0ea0xK8aGA=; b=qYF+HIG2d/JZNoLq8iNKOisaxdByflp50GeoWTsZ8bes8frQfiekccY3/O77ISTw9Q 9VM7wKwPkHi6LCzcTr1IrtdOVR6YJNDaokpWfDO9dy5kXQ7A4qgHIuvuJZibeodOVke8 ByEQnw8ZCMh7Ucwz9HiwJLPk1+w7YhpWwMF0sEs+JIMip5HKUiufPVdmdx7/hMPs6yuv XLnt44u+HyaTuqXBrTEdQIs4AwAwO3bvw7XU5Q2/e9nO8Nxh6aXyCNzXpDCtYH4q52aM 36UHWnv5I00TArvyHv8ZbF/Xp43q/aiZa9WNuXdkYJxolP6E5ThKH/jtX+R/4ClizW0l SwLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712167696; x=1712772496; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nqv3C1BVtGg/wUFoW1PjnMhIDdPmbl6aF0ea0xK8aGA=; b=MTH6nx3Jj1oqD+hXdnc/jKfU0LncHPe1vIjrX7WUlXDc1pA9y1R7Jw3IU03Di6m268 48tNTzJxhlxZL4C657SKXjfbkR3gIF97mV2By6G6GCzDSgUAIP5CuoQ9/+bzd58HLGRJ y+K4h1g8EFIDvbHfcr0fdAmku4w3nKxJuJG7XYmFSGtOdoPFQ/5yiulOxSSZQ3Oqnj/l O6g6qJhUK20wUB4wHKe4FJh+ycvu103nHXUJWh0BaKKsCusSm43tJvtYW8T4/ZJu+li8 HZYjIsX3fnqG+VeDbdXwGChKJXlWuo1grijC98pVbrJcBrtxZahvJhzhh12M2l4YW2QP +j4Q==
X-Gm-Message-State: AOJu0Yz20CbkAUgfueHTJRawfkWnB0FG9jrPcB6+7K5WFZGdHkXGuKpt YWwUAESQ3fvDTaFPDXYULjsjapzltr/v5xdsnYIaB9mQzWcwfn4c8PPMDhCF6pu/fmxuV9SVTE+ iBTlMwtmDs1QSa+8L1vH8Xl8YPs8FsTq8TpZ5cojN1TQVa4l/
X-Google-Smtp-Source: AGHT+IE8EsLg9q63XiZvvP5geYPkRAI5CGptgw4leS/RoXrWWke9F4IsmYHrYgABks4fgCqBP9SMb/IHR5jSb4Bc3/U=
X-Received: by 2002:a0d:e6ca:0:b0:615:5b0:7e60 with SMTP id p193-20020a0de6ca000000b0061505b07e60mr175907ywe.35.1712167696347; Wed, 03 Apr 2024 11:08:16 -0700 (PDT)
MIME-Version: 1.0
References: <680b1aac-3845-461d-a063-09f7a7db9dd9@danielfett.de>
In-Reply-To: <680b1aac-3845-461d-a063-09f7a7db9dd9@danielfett.de>
From: Jacob Ward <jacob.ward@spruceid.com>
Date: Wed, 03 Apr 2024 18:08:05 +0000
Message-ID: <CAGDGPRZy3vP2J=YUExqGr4_gcMZuD9-6ytWHdihHsyAJNdAgfA@mail.gmail.com>
To: Daniel Fett <mail=40danielfett.de@dmarc.ietf.org>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000564bf40615351b66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/H34Fr1gOo8ObRH25-ovyVORaQpA>
Subject: Re: [OAUTH-WG] Type Metadata for SD-JWT VC
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 03 Apr 2024 18:08:22 -0000

Hi Daniel,

I'm not sure anyone has published a draft yet, but given that there is a
draft for SD-CWT I wouldn't be surprised if SD-CWT VC appears at some
point. With that in mind, has there been any discussion on having an
encoding-agnostic specification of this metadata, rather than JSON specific?

Thanks, Jacob

On Wed, Apr 3, 2024 at 8:22 AM Daniel Fett <mail=
40danielfett.de@dmarc.ietf.org> wrote:

> Hi all,
>
> as discussed during IETF 119, we would like to introduce what we call Type
> Metadata to SD-JWT VC.
>
> For a bit of context, the intention is to provide a mechanism to provide
> information about credential types (e.g., a JSON schema, display/rendering
> information, a name and description to be used by developers, etc.). Type
> Metadata can be organized in a hierarchical structure using "extends"
> relationships.
>
> The need for such a mechanism developed from discussions around the 'vct'
> (Verifiable Credentials Type) identifier
> <https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/181> in SD-JWT VC and
> again in the context of the EUDI Wallet
> <https://github.com/danielfett/sd-jwt-vc-dm>.
>
> I drafted a first tentative design in this specification
> <https://vcstuff.github.io/sd-jwt-vc-types/draft-fett-oauth-sd-jwt-vc-types.html>
> and we now want to revisit that and start moving pieces of that over to
> SD-JWT VC.
>
> The first PR <https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/220>
> introduces the basic Type Metadata structures including the extension and
> integrity protection mechanisms. It lacks many of the features we would
> like to see in an MVP, so we plan to release a new draft only after
> introducing a few more features
> <https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/224> in follow-on PRs.
>
> We would like to invite you to review the PR and let us know if there is
> any feedback! I also plan to discuss this in more detail at an unconference
> session at the OAuth Security Workshop.
>
> -Daniel, Brian, Oliver
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>