[T2TRG] Considerations for converting from other serializations formats like Protocol Buffers and FlatBuffers
Jonathan Beri <jmberi@gmail.com> Mon, 13 April 2020 15:09 UTC
Return-Path: <jmberi@gmail.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D99C3A1778 for <t2trg@ietfa.amsl.com>; Mon, 13 Apr 2020 08:09:56 -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 9cwfRRGEInDr for <t2trg@ietfa.amsl.com>; Mon, 13 Apr 2020 08:09:55 -0700 (PDT)
Received: from mail-ua1-x936.google.com (mail-ua1-x936.google.com [IPv6:2607:f8b0:4864:20::936]) (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 D76D93A1752 for <t2trg@irtf.org>; Mon, 13 Apr 2020 08:09:54 -0700 (PDT)
Received: by mail-ua1-x936.google.com with SMTP id x18so2496605uap.8 for <t2trg@irtf.org>; Mon, 13 Apr 2020 08:09:54 -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=+s0FNyZPEDma6b39HD0Msez8K9qKsBgpuNwKIFva//M=; b=BPfnAqt0yXgjYkoOBQvQ07BOhw+5xcMsrNOlPXTbxfaTZbGE9TpXzku2lqhg7UdVbK eIR6DrJ96ziZdZXNHi9+XlVB2aOw/dppSzHCKMDDwvYCeDjjEpMyK2KmCXitbPlBbbrD FRbH1jY4QWKYktpAqYBJXJEg48m/XUVWAMRy2Ex/XKZf7e0aQBWQ/gR46Y0zvh9xS2Ki vw3WqwW1EvBO4Pp7xWM7Y+/L9IjVUsfFazmrfNGJbnfxS8T3UfnGgjID5ZWyms/Rtg/y cog1VGv8IAfJYj5FaSNxTj1l2M3458C05vJEsRsyKreQsIzKUhBiSyAfD+e6SDpS+ZfH gM3Q==
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=+s0FNyZPEDma6b39HD0Msez8K9qKsBgpuNwKIFva//M=; b=jOfroZjd/5Xz2xmRbTdUmJaPfhYLaNmhwaRp1DfqdAX14PCdoQECLU8S65eXmXNpU5 zxKVtL2zrHMk0GwtHJqHsLg3RSvzc8qNPgkKdJ9DnicAK3JqRd0kwA7gQcpYTjq++3Su g2FEQ9PyFKMcJeEx8nFRpYwt9ce8NqPhXhuv0i6CxZFyUrOt5ifjQyiMr2vkw5lr5KqP CrykFRdtW9Rr/XbMz1qGCVVjbQTOr/RqoN7+Jaw5pnco95MG2rTf2TvVHjAlWe67yNvm lMd4RGIFZ3yZI0SdjYxoSxKAG8tAECbVjPoPd+QtfcqTq2aHgKH2s9ChgCmyLQE1RYAn CKUA==
X-Gm-Message-State: AGi0PuYAXQdxEfq5+o1Y5Wvi4P2ST/rMvziLgDzojbFo0oiibRV8mp1b Yu08pTWlKk+eb2ZJlTy8dy+n3b/wKVfNN1/BR8WCKMflHX4=
X-Google-Smtp-Source: APiQypLtxrwrCis80dhgOWwJYATOvWSL6lrp+Jez5VLktmEwm49LO+3haN/VTDde0F8zFEYNnrJ3To6bxRsCl6+Xh/Y=
X-Received: by 2002:ab0:29da:: with SMTP id i26mr11531407uaq.29.1586790593405; Mon, 13 Apr 2020 08:09:53 -0700 (PDT)
MIME-Version: 1.0
From: Jonathan Beri <jmberi@gmail.com>
Date: Mon, 13 Apr 2020 08:09:17 -0700
Message-ID: <CANcmUPE58vG-AFLh_Y2Vsdbx2M36=6nJDLXqzO_fhzoUNm_=ug@mail.gmail.com>
To: t2trg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000a7286d05a32d799b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/yrnsl7WaIIfYyTcbHyTWx_EOI9Q>
X-Mailman-Approved-At: Mon, 13 Apr 2020 13:25:27 -0700
Subject: [T2TRG] Considerations for converting from other serializations formats like Protocol Buffers and FlatBuffers
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2020 15:09:56 -0000
[x-post from cbor@: https://mailarchive.ietf.org/arch/msg/cbor/acIUx_PPHd5Vu8QHtNFt0quPdeo/] 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/>
- [T2TRG] Considerations for converting from other … Jonathan Beri