[kitten] Small question about token in draft-schmaus-kitten-sasl-ht-09

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 13 January 2023 17:29 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D540FC14CF05 for <kitten@ietfa.amsl.com>; Fri, 13 Jan 2023 09:29:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 LZrjDBajp8GW for <kitten@ietfa.amsl.com>; Fri, 13 Jan 2023 09:29:12 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id EDB34C14CE4C for <kitten@ietf.org>; Fri, 13 Jan 2023 09:29:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1673630950; d=isode.com; s=june2016; i=@isode.com; bh=pjw9hHCbN6X/lsJApHUZWZwnARzbmPBHYjj0m5A+/fg=; 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=iuHhQfelevadcp8sKM0pL4E7tLz10Ym6WI5vPbiP+b3/l/PFNC8Zfsue4a4xlTkBEK4ytj dYcrthzstlRD1b17YmCAiGcHVse78LyyYTvCQTMaSwQ5THlQhQWgZgtDOCW85duxvt/TZU mkidMIyw5Sx0PDxEy2un0NFTTp3wzOE=;
Received: from [192.168.1.222] (host31-49-219-81.range31-49.btcentralplus.com [31.49.219.81]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <Y8GU5QAPgTSy@statler.isode.com>; Fri, 13 Jan 2023 17:29:09 +0000
Message-ID: <e6f1e531-16a4-08d5-d947-b80484bc4969@isode.com>
Date: Fri, 13 Jan 2023 17:29:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Florian Schmaus <flow@cs.fau.de>, Christoph Egger <egger@cs.fau.de>
Cc: "kitten@ietf.org" <kitten@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------kvuttht4VHsFFohzOTfyQSM0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/Zcr6IefSQ9IsLfzzx5us_awWMWA>
Subject: [kitten] Small question about token in draft-schmaus-kitten-sasl-ht-09
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jan 2023 17:29:15 -0000

Hi Florian/Christoph,

I am reading the description of token in your draft:

    HMAC() is the function defined in [RFC2104] with H being the selected
    HT hash algorithm, 'cb-data' represents the data provided by the
    selected channel binding type, and 'token' are the UTF-8 encoded
    octets of the SASL-HT token string which acts as a shared secret
    between initiator and responder.

This made me wonder why is the token defined as UTF-8 string and not just as binary data?

Thank you,
Alexey