IETF Logo Mail Archive

Re: [COSE] tstr values for kty, alg, crv, etc.

AJITOMI Daisuke <ajitomi@gmail.com> Sun, 08 August 2021 13:49 UTC

Return-Path: <ajitomi@gmail.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 194243A2BAB for <cose@ietfa.amsl.com>; Sun, 8 Aug 2021 06:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 35DcNRM9of9A for <cose@ietfa.amsl.com>; Sun, 8 Aug 2021 06:49:46 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3D773A2BAA for <cose@ietf.org>; Sun, 8 Aug 2021 06:49:45 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id d22so23003436ioy.11 for <cose@ietf.org>; Sun, 08 Aug 2021 06:49:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9x/HwebwbfxMLzzgcrmihp5OGpg4eLO/YPa8riVK3JE=; b=uAKonL4z8x6ydO3kHCCgPXhvz4slQzSwdU5dmFQ+eKpO8eiE8EKEUArskoCx2Pi+1R 4JgpzDf3+hmdCrbGepL5cFTf1q7knUlH9lFk5/QnWtTzjk3NnQRUDi6gni/sxEoanDij 6Vr6weL4LgERAsU8mt4z4cZIBIAdKigZ1++y/JWR4uUQ2B0OJZ8gwY8CYDqVg9DbWQAU uZZ8PHesADwBsos7dIr+Ln/VoidlJdga7l+S9drvPZmAbnIr+GP6giXe0xavCZscjt3R exNpPBu5lTLOXEFOuo2COtlJunUlJtu5U5dgHsFuV/MGIkVHOtU5Ydhrmr8x8kXjReGa 9/Mw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9x/HwebwbfxMLzzgcrmihp5OGpg4eLO/YPa8riVK3JE=; b=XYizysHvrKJfjJ1qarLLgNfU/pyvy0PDCjiRHjgZZRwVVe1EIiztHN2B6cz7NecJLq r7zAk47Ldh8ofx6eIfNX6oPhARgfoMUt3ak2gmFvUqKw6a2omPGRR3LjGHA6j0larrD7 DM5zWvZ8vzFTXMPC6FUTCczoR8rR8U14UKlAyWLUgmNYNUyuqE5m71t1rkIZgMEv4LZe SO8NU0mkvAdookDWJ0lPK5N7BEIcAzYypc3OukPN6r9exMGBVxOSVoMQxas5SjKLgEa3 T4DUDvv8MAVQhkroHt/BRSAZVkbYU4UtTSmN1posz8Hkn99rS4DHZLfO4hw42VbxC4N9 Or1g==
X-Gm-Message-State: AOAM530alO6lEYQxmQ+VDnzb2FUFN/Q9625AbqVjJUAx5ytDENq3L+xR TLbAQjJQOi/UBcG0FFWcvQr22jLiWGVAiQziLg==
X-Google-Smtp-Source: ABdhPJy4AOjBRjWxNFUtsFjVdC1MBw93tifh/QTJqwQNGuMMuveJ5Ic/tDw3HCV+cy1aK0zNETIsY9zVoJsD396CcTo=
X-Received: by 2002:a92:d3d1:: with SMTP id c17mr203610ilh.86.1628430584341; Sun, 08 Aug 2021 06:49:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAFWvErXkR1vVNQFjn+rVCe8jaJ7DspBUq5kVJdGzonBU98Ctbw@mail.gmail.com> <78EB5028-71BD-4034-A9B3-340E206F1F90@tzi.org>
In-Reply-To: <78EB5028-71BD-4034-A9B3-340E206F1F90@tzi.org>
From: AJITOMI Daisuke <ajitomi@gmail.com>
Date: Sun, 08 Aug 2021 22:49:32 +0900
Message-ID: <CAFWvErXw=0OwR3J1u6m6=LcHQen_ngtGnW_7cvR=EKEhbtPjUQ@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cose@ietf.org, Laurence Lundblade <lgl@island-resort.com>
Content-Type: multipart/alternative; boundary="00000000000085677105c90c8ab9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/70_3xcgLYLH7itbbiv5fB7uvnNo>
Subject: Re: [COSE] tstr values for kty, alg, crv, etc.
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Aug 2021 13:49:51 -0000

> What’s the rush on disabling these?

You may indeed be right.
At least, I think there may be no need to rush to apply the change
to 8152bis (Maybe that's impossible in the first place though).

Maybe we should discuss this more. I would be happy if you would consider
this matter as the next step after 8152bis.

Regards,
Daisuke

2021年8月8日(日) 20:48 Carsten Bormann <cabo@tzi.org>:

> This discussion is all a bit short sighted to me. Sure, we can advise
> against registering text labels now. But COSE has a long life with many
> applications before it, some of which may be outside what you are thinking
> about now. What’s the rush on disabling these?
>
> Sent from mobile, sorry for terse
>
> On 8. Aug 2021, at 10:15, AJITOMI Daisuke <ajitomi@gmail.com> wrote:
>
> 
> > We can deprecate tstr as key.
> > We can say that no signer MUST NEVER emit this again.
> > We can say that a verifier MAY accept tstr as a key.
>
> This sounds reasonable to me.
>
> Since any tstr labels are not registered in the IANA registry for now and
> there are no implementations that support the tstr labels as far as I know,
>
> I think there is room to make the tstr labels deprecated.
>
> Thanks,
> Daisuke
>
> 2021年8月8日(日) 8:22 Michael Richardson <mcr+ietf@sandelman.ca>:
>
>>
>> Laurence Lundblade <lgl@island-resort.com> wrote:
>>     > I don’t think tstr can be removed from the standard. That would
>> break
>>     > backwards compatibility. Maybe a strong recommendation could be
>> added
>>     > with the comment that many implementations don’t support tstr.
>>
>> Any system built upon COSE that does not support tstr as a key is already
>> broken if many implementations don't support it.
>>
>> We can deprecate tstr as key.
>> We can say that no signer MUST NEVER emit this again.
>> We can say that a verifier MAY accept tstr as a key.
>>
>>     > There is a revision of 8152 in process right now called 8152bis.
>> That
>>     > seems like the place to do it.
>>
>> It is pretty late to do this.  8152bis is in AUTH48, we need the
>> proxy-author
>> and WG chairs to agree to this immediately.
>>
>> I agree that having two ways things is not a good thing.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting
>> )
>>            Sandelman Software Works Inc, Ottawa and Worldwide
>>
>

v2.23.0 | Report a Bug | By Email