IETF Logo Mail Archive

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

Jiri Vlasak <jiri.hubacek@gmail.com> Mon, 27 June 2022 20:53 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 C50CEC15AD34 for <dispatch@ietfa.amsl.com>; Mon, 27 Jun 2022 13:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 hPHjIIO2Dac9 for <dispatch@ietfa.amsl.com>; Mon, 27 Jun 2022 13:53:27 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 6C19AC159480 for <dispatch@ietf.org>; Mon, 27 Jun 2022 13:53:27 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id bx13so3828563ljb.1 for <dispatch@ietf.org>; Mon, 27 Jun 2022 13:53:27 -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:references:mime-version :content-disposition:in-reply-to; bh=Fm0RBQxwVAkuOQz7ktCh1NDG0Xon04nk7W6tFx70e3g=; b=qXCBlKytmmsDUogt7WqXPKTGYEZKZUC2OdE2aKIKbJ2wNNjymvhs/E55PHKwuorepW fkyIflQOTZLUpKUEXKNJ91pSiisoulc+92F3/pCHmPpJ7EI0ihBNW1mmpGf/b8XHM63f 6UKrrtMD7j3MX3JVxWoUSvD3xYTFhS+CyefXopj11aAPuZhvAe+DCc/nAaQKrtKfnjRO CB0LGn3ij/kzG7XhH+tSpJMBD687qn7FQnKde4rJeElan1KVXQAC47YFcCRRo7BzHypk 6EeQuoisU4u+6+8p3uLU84MsQ++RaITd9o+4IZF/Q6uxbhXZsEgG0PgJzhHqp58iRKLy +GBQ==
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:references :mime-version:content-disposition:in-reply-to; bh=Fm0RBQxwVAkuOQz7ktCh1NDG0Xon04nk7W6tFx70e3g=; b=0ENQbl1j5u6VSTgIVp6N6rMCgVt9b9lP4wc92djkFeiOdzrH0voPP0q+GPIgcS481s 6oF/TY/m9sCIpYX/m6QLyoYna7osgnN+/appP7EZN64vOPgeoFTrja63RKBmRrwGRcC6 FEa0pPfwzPXt/RY+/h0tXB3SC4XZuCUb2FZERhHtrm5o6XD338FiVdY3ASttq+36tesF 7Uubho2mp5Ll19K/ljlqEM/XijxPlggq67xTaqj9uFmTf+9ikQjdw1+ruSAkerm0rcD7 OYWMvrcSdkLUAtC3AeYiZ6ctZO/ABDHinPPCnSMNhNp5lEvrNz+ZcOjfi3WLfEf2ndXp qhcA==
X-Gm-Message-State: AJIora890c+TjiHhZalXdE9+8X+Zw+jNgUeYkuQ2Wlx4+iYzVDwPXQuk KWvhG+J0UXfdSfg9513AcSOc4ykBPC3EmA==
X-Google-Smtp-Source: AGRyM1twaUkgom8vYjq2umqKrtw8ZRxqn/CE6we5lsXRrCjE6a0nnJCY/iT0fgGnrv181WTTxGIC6g==
X-Received: by 2002:a05:651c:1544:b0:25a:8e6f:a1b6 with SMTP id y4-20020a05651c154400b0025a8e6fa1b6mr7858938ljp.314.1656363205237; Mon, 27 Jun 2022 13:53:25 -0700 (PDT)
Received: from gmail.com (185-170-195-217.cust.centrio.cz. [217.195.170.185]) by smtp.gmail.com with ESMTPSA id 17-20020a2eb951000000b00253bc47c202sm1541800ljs.59.2022.06.27.13.53.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jun 2022 13:53:24 -0700 (PDT)
Date: Mon, 27 Jun 2022 22:53:22 +0200
From: Jiri Vlasak <jiri.hubacek@gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: DISPATCH <dispatch@ietf.org>
Message-ID: <YroYwrOk6M/oflox@gmail.com>
References: <YqC0MHD7MPpcFEuc@cvut.cz> <20220608210551.72EB94341C93@ary.qy> <YqH16YukCzEbLBF3@cvut.cz> <CABcZeBNBSt0z7ur7_JwhBs30s05wT9n4jsDZA1wre991fkvS8w@mail.gmail.com> <YqJUjF8W3Dw/XgKB@gmail.com> <CABcZeBPRkW1iHVDVG4fLTdGzigfFtNLQDu_UkRHE1-V7jXgKrA@mail.gmail.com> <CAHBU6isB2-u5TUUMz76ZHF=FcRW9rokEPGtNZzeM2a6NjFxHNA@mail.gmail.com> <7053DA78-703A-420C-A474-C7310251F4F1@iii.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7053DA78-703A-420C-A474-C7310251F4F1@iii.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/mVp9mkNpIyPHwVwkwaADJ_BqZk4>
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: Mon, 27 Jun 2022 20:53:29 -0000

> I think there are a bunch of ways this could be improved to help with
> things like:
> * schema syntax for future extensions points, 

For backwards- and forwards-compatible schema, BARE suggests in section
"4. Application Considerations" the following:

	type Message union {MessageV1 | MessageV2 | MessageV3}

	type MessageV1 ...

	type MessageV2 ...

	type MessageV3 ...

And the later deprecation of the messages:

	type Message union {MessageV2 = 1 | MessageV3}

> * some pre defined thing for common data such as time 

To cite from the "Appendix D. Design Decisions" of the BARE I-D:

> There is no date/time type
>    Use u64 for timestamp or str.

Where "str" is used for example in section "B.1. Message Schema":

	type Time str # ISO 8601

In my opinion, it is better to let a date/time be parsed by the library
function of a language than to complicate the protocol. However, I may
be missing something, and I am happy to discuss it.

v2.23.0 | Report a Bug | By Email