[kitten] Re: Update about DID-based SASL mechanism ("DID-CHALLENGE")

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 01 April 2026 12:21 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: kitten@mail2.ietf.org
Delivered-To: kitten@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5A97DD4BFF14 for <kitten@mail2.ietf.org>; Wed, 1 Apr 2026 05:21:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775046083; bh=N1lLaGdkjUNBVKfLgI7bPZUSCZRz6RR41flOeOjUZN8=; h=Date:Subject:To:References:From:Cc:In-Reply-To; b=xSKGPnzzyGC8qmkv+34ZmF6eumhsigjMyBWjDfcbgub1TNDanen3QCfv6u8APvMYD QfElabqxO2dDWoL+lbbDcp1UKPyw2vy4q2KaqWmfzqzOHyoR+0SP76nCNJPwiH66TI B1VHtJx10NsD6bxieBn/jHZgbT0l9/MfLagCKygQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E16htFeNxP1h for <kitten@mail2.ietf.org>; Wed, 1 Apr 2026 05:21:22 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [195.21.82.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 36F0ED4BFCEA for <kitten@ietf.org>; Wed, 1 Apr 2026 05:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1775046067; d=isode.com; s=june2016; i=@isode.com; bh=N1lLaGdkjUNBVKfLgI7bPZUSCZRz6RR41flOeOjUZN8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=F6BblcBvBCGE6s+ip3dSQTsXdSMDi9oeMkX5RNJuwoEnQ/F10fGv8rtlPM3HjOpB24MRXj Z7PBHypRCBbQbRLp5FErKUS0ihTUzLkLVv4CctrUukrFqa/+diJwxhR2+k6BlMr+9cH7fM ZxX6FjYg+IP6gfKjXNHrzyc9hzGxcvo=;
Received: from [192.168.0.72] ((unknown) [90.199.8.130]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <ac0Nsi5MZp3J@waldorf.isode.com>; Wed, 1 Apr 2026 13:21:06 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <035542b3-1ff4-4dda-9a17-01829b34d14d@isode.com>
Date: Wed, 01 Apr 2026 13:21:06 +0100
User-Agent: Mozilla Thunderbird
To: Markus Sabadello <markus@danubetech.com>
References: <0571d458-6541-4282-abd7-ee62a86818f9@danubetech.com> <abx1ZeG2Op+6Q7XR@ubby> <1ccdddbf-2af3-42d3-9918-b79e0ad30d61@danubetech.com> <d1e009bc-a9e4-488e-90a2-0eab5ec7f862@danubetech.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <d1e009bc-a9e4-488e-90a2-0eab5ec7f862@danubetech.com>
MIME-Version: 1.0
Content-Language: en-US
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Message-ID-Hash: SGGVE5RVKJWV4GBT6NE3O236OIEAG2N5
X-Message-ID-Hash: SGGVE5RVKJWV4GBT6NE3O236OIEAG2N5
X-MailFrom: alexey.melnikov@isode.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-kitten.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: kitten@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [kitten] Re: Update about DID-based SASL mechanism ("DID-CHALLENGE")
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/s2s_vc4f61p4ogmDhSjKygNgNPM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Owner: <mailto:kitten-owner@ietf.org>
List-Post: <mailto:kitten@ietf.org>
List-Subscribe: <mailto:kitten-join@ietf.org>
List-Unsubscribe: <mailto:kitten-leave@ietf.org>

Hi Markus,

On 26/03/2026 10:35, Markus Sabadello wrote:
> All,
>
> I am also wondering if it would be possible to publish my work on the 
> DID-CHALLENGE mechanism here in the list of documents of this WG?
> https://datatracker.ietf.org/wg/kitten/documents/

For a draft to be listed as an official work item of the KITTEN WG, it 
needs to go through adoption call. Basically this would confirm that 
enough people are interested in working on your document. Once adopted, 
your draft can have "draft-ietf-kitten-XXX" name.

It is possible for your draft to be listed as a related work without 
going through the adoption process. For KITTEN WG you should have 
"kitten" somewhere in your draft name.

> I'm sorry, I am not yet so familiar with IETF processes.
> Would this require approval of the WG, or can I just upload my draft 
> here?
> https://datatracker.ietf.org/submit/

If your draft is named draft-ietf-kitten-XXX, it would require WG 
chairs' approval and a successful adoption call.

If your draft is named draft-<yourlastname>-..., then it's submission 
doesn't require any approval.


I hope the above answers your questions.


Best Regards,

Alexey

>
> all the best,
> Markus
>
> On 3/21/26 3:55 PM, Markus Sabadello wrote:
>> Thanks for your question!
>>
>> As Benjamin replied, a DID is a Decentralized Identifier as defined 
>> in a W3C standard:
>> https://www.w3.org/TR/did-1.0/
>>
>> A DID has resolvable public keys, which can be rotated without 
>> changing the DID itself.
>> For SASL, this means you can have a persistent identity string that 
>> doesn't change over time.
>>
>> Please let me know if you have other questions or feedback!
>>
>> all the best,
>> Markus
>>
>> On 3/19/26 11:15 PM, Nico Williams wrote:
>>> On Thu, Mar 19, 2026 at 11:02:07PM +0100, Markus Sabadello wrote:
>>>> The idea is that you authenticate by signing a challenge, using 
>>>> private keys
>>>> that control the DID.
>>> Where is the terminology from?  If it's brand new it will help if you
>>> harmonize it with terminology that we're all familiar with, if 
>>> possible.
>>>
>>> Nico
>
> _______________________________________________
> Kitten mailing list -- kitten@ietf.org
> To unsubscribe send an email to kitten-leave@ietf.org