IETF Logo Mail Archive

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

Jiri Vlasak <jiri.hubacek@gmail.com> Thu, 09 June 2022 13:30 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 41EFBC14CF11 for <dispatch@ietfa.amsl.com>; Thu, 9 Jun 2022 06:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMFLpJU_FPSv for <dispatch@ietfa.amsl.com>; Thu, 9 Jun 2022 06:30:22 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 A809CC14F739 for <dispatch@ietf.org>; Thu, 9 Jun 2022 06:30:22 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id n10so47518295ejk.5 for <dispatch@ietf.org>; Thu, 09 Jun 2022 06:30:22 -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=HlJq0ChAIkQCzFUqQFZnQiZ7siCV0W2yRA+OWr973mY=; b=K3XLK5u7utsrsHGi2WGwmm25kRgWeaXitlVaAa+t69E9hG+2ZtiU1gEugds7Ds3cK1 RYvJxJCrC+mR9NQFHczDs3+3ZHWlpzCEgluDoN+T8RYbQNfpHMXxQ+Q3+v7BxTT7oj2f i7s1BAlL3392WLNgz1XnNQ5frJjo953IsYEqivlIznhMgnHMTyqRJxZhMPaILhjVFivH bsnVWEieovGHEvekG2nIRb57RE/UG+v/B52F+HivU7blJVrhWWoDEiOOtD+0/zRLFvEo eFUlEEpfuGrM0f5m3uvPbGp0+wsKzASK/zgUlR7cddEVtYPs8M4sJt8gloBrzIKQ2dwX UP/A==
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=HlJq0ChAIkQCzFUqQFZnQiZ7siCV0W2yRA+OWr973mY=; b=ZjESjuQJlB4DNyUhsyjYD4xWvVD0e6CL1d7eV67Vk+QfCGc3Ym/FJRDgdgBU/y8wjV uA5bi7pXWDHLx98OeEsYXkfFXjFdXjsmk29ncIJWKurW/1KqnTQ0ei+FLPEEHgy7D7oO S3kKaUbDnjfHLudC3JT6cqbHlYUU2LbDCzhHEyYMqqy1Spdj83LOdRiJH2FE93Pe6bwO PUZO1tBqVoQI6tuU1+RoT+hD2NEG3aEhECyDILcy1dj/9vUldiz31fZQSiycQWWgjezr CN0oswgJFUCpDf49zw48L6yC55ibcCcj6GiKJlEKFC5FxTR/B2NPzZUHAzBKeBR24L7a QXaQ==
X-Gm-Message-State: AOAM533IUQ7d+XzCaBibgukCDn/GLkpoZIB+oDoDdyXZPxCfeNwMGaQe wsi4JYEIYXpklZc/IoHNOXQ=
X-Google-Smtp-Source: ABdhPJyD0oOi17194kaMPEy10kK+0KeMaT/aaw2+m++wH2eqVxUZZ1YRG1Hhvv2YAnjmSnnGJGf9sg==
X-Received: by 2002:a17:907:ea7:b0:70f:a27a:dac0 with SMTP id ho39-20020a1709070ea700b0070fa27adac0mr28660506ejc.25.1654781419374; Thu, 09 Jun 2022 06:30:19 -0700 (PDT)
Received: from cvut.cz (fw3.ciirc.cvut.cz. [147.32.71.8]) by smtp.gmail.com with ESMTPSA id a22-20020aa7d916000000b0042dd4f9c464sm14179448edr.84.2022.06.09.06.30.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jun 2022 06:30:18 -0700 (PDT)
Date: Thu, 09 Jun 2022 15:30:17 +0200
From: Jiri Vlasak <jiri.hubacek@gmail.com>
To: John Levine <johnl@taugh.com>
Cc: dispatch@ietf.org
Message-ID: <YqH16YukCzEbLBF3@cvut.cz>
Mail-Followup-To: John Levine <johnl@taugh.com>, dispatch@ietf.org
References: <YqC0MHD7MPpcFEuc@cvut.cz> <20220608210551.72EB94341C93@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20220608210551.72EB94341C93@ary.qy>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/eW8WIQ6k6Mcl-8AKyqm1Nq01CEg>
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, 09 Jun 2022 13:30:26 -0000

> An obvious question is why one would use BARE rather than CBOR which
> appears at first glance to do the largely the same thing. See RFCs
> 8949, 8152, 8392, 8610, 8742, 8746, and 8812.

An obvious answer is that because BARE spec [1] is short. It has about
17 pages (depends on the format), that include schema language and many
examples.

Moreover, BARE needs the schema available prior to the communication,
which is not needed in CBOR [2] as stated in the objectives. In this
manner, BARE better compares to XDR [3].

> If you can join the session remotely, I expect we can have a useful
> discussion about this and related topics.

I will try to save the time and do my best in the discussion.

[1]: https://datatracker.ietf.org/doc/draft-devault-bare/
[2]: https://www.rfc-editor.org/rfc/rfc8949.html
[3]: https://datatracker.ietf.org/doc/html/rfc4506.html

v2.23.0 | Report a Bug | By Email