IETF Logo Mail Archive

Re: [Cbor] Reminder and call for agenda: CBOR WG Virtual Meeting on 2023-05-31

Anders Rundgren <anders.rundgren.net@gmail.com> Fri, 26 May 2023 04:35 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B54C137382 for <cbor@ietfa.amsl.com>; Thu, 25 May 2023 21:35:09 -0700 (PDT)
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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 zCfkFqr-vWMS for <cbor@ietfa.amsl.com>; Thu, 25 May 2023 21:35:05 -0700 (PDT)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 DB455C151B22 for <cbor@ietf.org>; Thu, 25 May 2023 21:35:05 -0700 (PDT)
Received: by mail-wr1-x42f.google.com with SMTP id ffacd0b85a97d-3078a3f3b5fso220797f8f.0 for <cbor@ietf.org>; Thu, 25 May 2023 21:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685075704; x=1687667704; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=3LT0bLq2bLEeQdJ77GZPyRhCVwO3syJBWIG1LRu2sbw=; b=PdEvGMOrvtUfJHO1oGp8YeNVf0wExcqufHMsOK4Wq8Ag0K+eqLUUCcQnc24OtQvXmD TBjtNpvKlBIMJro+73efTRUgM2ID4SaNbka3YnILdhRIMHxkM6PNt43/sca5wE4OW1bs R6ljyFp7/DCLuus8GSjOQGpSvfWxZAW1IgAqFH6C9Jwk0yOEqxYQnJPA7fm955QJgvGk jC5nYI3MdgniSw4htXSMH50aFZ5EfhhR6njddR5636mGT/aFNKBWpV/hm/k0jI7ywysg bYFB4yALLAzGFVPIe65eeljPxjLNWTUCHuSRv9DaKRPs6HpdjnR556FFC6g1Wz1/YUio W2qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685075704; x=1687667704; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3LT0bLq2bLEeQdJ77GZPyRhCVwO3syJBWIG1LRu2sbw=; b=RL+pd7FNz0t7kRzyGbjEDZhbiyLSecbRvewDZbBcf7T2ELHQEr/sKSW0qECIqjZyFY YZFq/7zGkGnXBTAHQ64MWZcxyzeE72vw27DQzdsai53c0B8KaVs2R7YzZB8SMG6xHmkY Q8lZGOAKC/9Ln7WcuQhu5o+A7PGXvYY2RbYDdqm9GIX5lRWYrWspmm32r7f8Wm8Nxb7V 4CiV35BG2wFVO5uiUbqOGp3bqI/HdXjs1yZND8wdrhfS81uG8JQXI2pu3xyIZ3XScmCS p9TrylImOYSFFK1hDFbXcoKv3VloS9qBu8ttDI3QtNLcCJgI1fxA14nbPCAybFe9fWAO s+Xw==
X-Gm-Message-State: AC+VfDxUGZVol+Ewo7gXrOCzU7Tz0S1qTp3GYBT4eAi5rUOXgdEZDdJw YqkIW1b0WJT1yuluivTqiZR/aekY/XUzzcFx
X-Google-Smtp-Source: ACHHUZ594kg9HUX7lOnm5ZTkSjbZMFt6anf9tJ280E+l7Ir4IzKq7pR2BG14VigxIrXt+J3781rP7Q==
X-Received: by 2002:a05:6000:9:b0:304:79c1:725d with SMTP id h9-20020a056000000900b0030479c1725dmr373829wrx.45.1685075704097; Thu, 25 May 2023 21:35:04 -0700 (PDT)
Received: from ?IPV6:2a01:e34:ec4e:5670:4d3c:7af7:dc9e:6058? ([2a01:e34:ec4e:5670:4d3c:7af7:dc9e:6058]) by smtp.googlemail.com with ESMTPSA id b4-20020a5d5504000000b003062b6a522bsm3644902wrv.96.2023.05.25.21.35.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 May 2023 21:35:03 -0700 (PDT)
Message-ID: <118bed90-9c98-0da9-eefb-906e5b714369@gmail.com>
Date: Fri, 26 May 2023 06:35:01 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: Barry Leiba <barryleiba@computer.org>, cbor@ietf.org
References: <CALaySJJ8kwtR8y9us4Qi49KFAYwus0uBoRi49rMsEO4smwfKSA@mail.gmail.com> <CALaySJJqusJ=6X06Ee4UrhQp236h079Ng3MLbTgEzEd4=9EUhQ@mail.gmail.com> <CALaySJLGk9Ztg_kMmvk=PW+=2SLf1Bkb-kmQyPz=Dbs8=DuXMA@mail.gmail.com> <CALaySJLfJqcdy+GbpC0U44t1wi4p+zf7ObogAJFZuVheZ1UC0w@mail.gmail.com> <CALaySJ+eHZ5EeRM8wrO3o7b3UVzMwwAn+6Kuq_wMDLBxtOQmiw@mail.gmail.com> <CALaySJKOqZ0wp6ZBUTo=z6_pLKbQfekfZwJapOzRLWBvAjDiCA@mail.gmail.com> <CALaySJJR0ouauKKsy2uyYVtT2nsuawXGL_JKa0jLFNbxQCHLAw@mail.gmail.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
In-Reply-To: <CALaySJJR0ouauKKsy2uyYVtT2nsuawXGL_JKa0jLFNbxQCHLAw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/0gfX1z1-Nc3I8c2_EMdn9RTKVdY>
Subject: Re: [Cbor] Reminder and call for agenda: CBOR WG Virtual Meeting on 2023-05-31
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2023 04:35:09 -0000

Hi Barry & CBOR WG,

Although the stuff I'm working with may superficially appear similar to dCBOR, these efforts are in fact entirely different.

My project (coined "CBOR everywhere"), is about creating a "baseline" CBOR encoding profile for implementation by platform vendors in order to avoid the situation we got with JSON where for example Microsoft/C# and Oracle/Java interpreted the JSON RFC differently.

Based on recent postings on the mailing list, the CBOR WG seems to rather be drifting towards the opposite goal; creating sector- or/and application-specific encoding profiles like dCBOR, "fintech", or breaking away from the crippling past (C/C++). Since I have no interests in such ventures, I won't attend the meeting.

FWIW, I'm currently in the early phase of defining a CBOR JavaScript API for potential submission to the ECMA TC39 committee:
https://github.com/cyberphone/cbor-js-api/blob/main/README.md#cbor-javascript-api [*]
Whatever CBOR encoding scheme that eventually becomes a part of JavaScript, may very well emerge as the de-facto standard for platforms.  It is not great but it is certainly better than nothing :|

Best Regards,
Anders

*] My JavaScript competence is fairly shallow so feel free suggesting improvements :)

On 2023-05-25 19:34, Barry Leiba wrote:
> Reminder:
> CBOR one-hour Wednesday meeting on 31 May, at 14:00 UTC (16:00 CET).
> 
> Information for this meeting is here:
> Datatracker: hhttps://datatracker.ietf.org/meeting/interim-2023-cbor-09/session/cbor <http://datatracker.ietf.org/meeting/interim-2023-cbor-08/session/cbor>
> Notes: https://notes.ietf.org/notes-ietf-interim-2023-cbor-09-cbor <https://notes.ietf.org/notes-ietf-interim-2023-cbor-08-cbor>
> Meetecho: https://meetings.conf.meetecho.com/interim/?short=872f9f0d-9c33-408e-ba89-65d4e83980e3 <https://meetings.conf.meetecho.com/interim/?short=872f9f0d-9c33-408e-ba89-65d4e83980e3>
> 
> Please go to the notes and add to / adjust the agenda.
> Please go to the notes and add your name to volunteer to help take notes.
> 
> We already have the dCBOR discussion on the agenda, so this meeting WILL happen.
> 
> Barry
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.40.4 | Report a Bug | By Email | System Status