[Cbor] Considerations for converting from other serializations formats like Protocol Buffers and FlatBuffers
Jonathan Beri <jmberi@gmail.com> Fri, 10 April 2020 15:34 UTC
Return-Path: <jmberi@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 6BD1F3A0C52 for <cbor@ietfa.amsl.com>; Fri, 10 Apr 2020 08:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctZ3OlBUt7VI for <cbor@ietfa.amsl.com>; Fri, 10 Apr 2020 08:34:50 -0700 (PDT)
Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3A933A0C4C for <cbor@ietf.org>; Fri, 10 Apr 2020 08:34:49 -0700 (PDT)
Received: by mail-vk1-xa31.google.com with SMTP id f195so626494vka.4 for <cbor@ietf.org>; Fri, 10 Apr 2020 08:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=o1kCGmMCbGwlQ+WOMayoCn279AJ8CYi32vZxA/CBCVU=; b=IAJtvlM7UT7TeZobehhKr+XbotqNdcwbPoW7RoquuE91KUvs16BuCT2TVVDHWOTE5J 9QprntVfmju6kguvBwys2M6o5YvZfeNUeWhF1PgQbMkhXzA6hu4acjGYQnvHSThTK5/B sGCZHbsyLVUq7ADKKYjaAVgfNq7ACym88p8cD1YInZ88RGOs8hzByRoIdVTIM8kAnpL2 LDcUJeTBQQdMShse/XmV30G/a4Iu3YK29cBM4DaLwtMshNvFcBXETVFv3poC457Tdyrd mQfh6X92SXGHvei84++9Vjs1cBNTueKx3+/75PQyMjAXzCLdPCXSUUvRp0UI4NcsPLVY vAgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=o1kCGmMCbGwlQ+WOMayoCn279AJ8CYi32vZxA/CBCVU=; b=jefHeViYa8tuRoeYN66OCL6oYdaNfspO3oQECsBZqljDXt7ma+eGdsamQ9CxnCOJeb Wi6445g0mszNCY6tV6Jm7Fd+IBVxmqz3dByKpHnG0cj4B9fwC+idHtE4mVKpSXBW6aiq qdtzFK8Z4A6/o5mBM+udPlE5wy3yn9GWv/EpTfirpdNm8eOXmN5TQgpaaLkzvIeo2l9X kI8uacVsrcQ06kfKI5pfPaPkXkZSpP5yeYZyS54UKd0MuEvQRglZvfqWHmv9q9abSNSc WerYiCgLZsXwwh0veDQlnRHJ1chy+m/+r0NT1ouxlQ2n/2NF2cbnSWjHcwGa00MJMLiE cm8w==
X-Gm-Message-State: AGi0PuZ7YiEuAlXJo776IGALTK39fUR0SZhNp1t2jGruiGJ0zLN0CM7I JbWBd9ATdtjdi2S+XPwtCubvfuLYdE5njreD+r2jnt9i
X-Google-Smtp-Source: APiQypKfrAd07C2KippMpZLN0gTl9DxgST8V9CMKKramo0G8ENVcTHLtHPs3EjZs2jodJPCvy7QuZB8I4Wwjtz628Kw=
X-Received: by 2002:a1f:93d4:: with SMTP id v203mr3706226vkd.78.1586532888325; Fri, 10 Apr 2020 08:34:48 -0700 (PDT)
MIME-Version: 1.0
From: Jonathan Beri <jmberi@gmail.com>
Date: Fri, 10 Apr 2020 08:34:12 -0700
Message-ID: <CANcmUPHvT+o4uckLOTH54h=ZS3pubhyeQ4guxbmdRcVkC91mWA@mail.gmail.com>
To: cbor@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003bb51705a2f17930"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/acIUx_PPHd5Vu8QHtNFt0quPdeo>
Subject: [Cbor] Considerations for converting from other serializations formats like Protocol Buffers and FlatBuffers
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Apr 2020 15:34:51 -0000
Hello, I'm looking into a use case that would require converting data from existing systems that output in well-defined serialization formats (specifically Protocol Buffers <https://developers.google.com/protocol-buffers/> and FlatBuffers <https://google.github.io/flatbuffers/>) to CBOR. The goal is in part to use other specifications like CoAP with this data as as well an existing implementation of CoAP. Has there been any investigation into converting to these formats? Any lessons or points to consider? I've been reading up on CDDL - might that help in implementing a conversion process? Many thanks. -- Jonathan Beri linkedin.com/in/jonathanberi <https://www.linkedin.com/in/jonathanberi/>
- [Cbor] Considerations for converting from other s… Jonathan Beri
- Re: [Cbor] Considerations for converting from oth… Carsten Bormann
- Re: [Cbor] Considerations for converting from oth… Jonathan Beri