Re: [dispatch] draft-devault-bare-07 to be discussed during IETF 114

Jiri Vlasak <jiri.hubacek@gmail.com> Thu, 28 July 2022 07:41 UTC

Return-Path: <jiri.hubacek@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA71C14CF15 for <dispatch@ietfa.amsl.com>; Thu, 28 Jul 2022 00:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (2048-bit key) header.d=gmail.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 qSx4MjhzMnz6 for <dispatch@ietfa.amsl.com>; Thu, 28 Jul 2022 00:40:56 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 C0D13C13CCF0 for <dispatch@ietf.org>; Thu, 28 Jul 2022 00:40:56 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id i13so1086062edj.11 for <dispatch@ietf.org>; Thu, 28 Jul 2022 00:40:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=hnI7m3W86/w3qUWoVX2YrXnktW0sp+0A46ccw8eQLVI=; b=MS8WcMENqu1hhAnvBvtwT0rkBIKzSu0jr5sqPsCwDnbwWi/dx+g1F7t6RN3MnESCUs B/oJ3i06nHjcbggmF1mZvxjPayoPV5WgNh7g1YMOaBwFM75VY1eb4Ohukee0Lzwygn0v nj4IhB8vGd4N+VUCJQZ1CBKkgeV/M5cwKlXmt6Lxi4sfg6au9xw2ShubO116SlLTwUcP DMua493iUwDjAToHoJ8UsSqjcNRgnTCYo9N+mXc/OKZofET7pETVvOxc61ipkliY+RjI oLjn+fFBKsVUgXvXKY9T3UD80+nwr4xZP417bvcFAPAHoH20KRwVKhRcz1XqKkQ68e5Z 29Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=hnI7m3W86/w3qUWoVX2YrXnktW0sp+0A46ccw8eQLVI=; b=h5V/l8QabUjfFpf4y6kVX2Q753mqahx9ksCLgu+ZMiviy2HCRZf7dp+31n//Vv8axi 615nPOhWwO9I+bHS8T+ita1K/69iw12Zlb/NTvJFdL0RKjl2482ahnuyrHRDuD32gYCf l0FC+AmLO46YmEf5WdriSi51wdWuHOnbntPXPPA/C0gEB2Zi8img/pujVk73JEfZuiQ2 uzRXGZoyTbB29QhE4GbKVlqD2ajSN6646/Mqcu7P8iBDZVYIjUqTn/VjwjvXpdAPma5d xajygXGZcDuzQGdNheAQ6VlpQUz/Hr1MmrQ8TMnkh9C2a7pZxYjcUleET0tkDDIuXzLW KRJg==
X-Gm-Message-State: AJIora/L5CJrxzd9BSGySBIcR3w/K3pc4FzFC4XMuqgppC3Fq3HpD/HU DgQXZ0lZ/7n8clvrAJ4QmtgXpF9/vyM=
X-Google-Smtp-Source: AGRyM1twjZu5EZBxjVmZr0LUiqy+eA/U+FK7Iy0Y7bK3eCc2x22vkSk//100obgwe4TzQ8gyyEY9dA==
X-Received: by 2002:a05:6402:2552:b0:43c:a3e:5be7 with SMTP id l18-20020a056402255200b0043c0a3e5be7mr17428975edb.426.1658994054869; Thu, 28 Jul 2022 00:40:54 -0700 (PDT)
Received: from cvut.cz (fw3.ciirc.cvut.cz. [147.32.71.8]) by smtp.gmail.com with ESMTPSA id qc10-20020a170906d8aa00b0072eddc468absm92862ejb.134.2022.07.28.00.40.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Jul 2022 00:40:54 -0700 (PDT)
Date: Thu, 28 Jul 2022 09:40:52 +0200
From: Jiri Vlasak <jiri.hubacek@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: sir@cmpwn.com, dispatch@ietf.org
Message-ID: <YuI9hC33bHV2H84M@cvut.cz>
Mail-Followup-To: Anders Rundgren <anders.rundgren.net@gmail.com>, sir@cmpwn.com, dispatch@ietf.org
References: <YqC0MHD7MPpcFEuc@cvut.cz> <CAL02cgRVtSdkJxNe50ZLVQgF=3OWaBOC56X_wSdDgEgxovSCng@mail.gmail.com> <YuDxASssK9VtXO05@cvut.cz> <d60e3aad-221a-a7d1-9b34-7bd8b39d6a0c@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <d60e3aad-221a-a7d1-9b34-7bd8b39d6a0c@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/WEyHdktVGY-UjAA6Mwxl1rcJVLE>
Subject: Re: [dispatch] draft-devault-bare-07 to be discussed during IETF 114
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2022 07:41:00 -0000

Please, note that I re-added the dispatch@ietf.org to CC.

> As an author of https://www.rfc-editor.org/rfc/rfc8785.html I would
> REQUIRE keys to be sorted.  The cost isn't for real.

With all the respect, it is not good idea in my opinion. These are the
reasons:

- there is no wide support for ordered maps in programming environments
- there are situations when ordering is not important
- we would need to decide how to order
- there is alternative, explicit solution (list of pairs) with no
  difference in overhead

Please, note that BARE can not achieve full canonicity -- we need full
compliance to IEEE 754 (e.g. NaN values from sensors or infinity in
mathematical computations).

> For IEEE floating point data, I would consider adapting the CBOR
> encoding scheme so the re-serialization becomes fully compatible.

I am sorry but I do not understand. Both, BARE and CBOR use IEEE 754
binary formats.