IETF Logo Mail Archive

[Cbor] CBOR-YANG representation of common types

Maria Matejka <maria.matejka@nic.cz> Tue, 14 November 2023 16:54 UTC

Return-Path: <maria.matejka@nic.cz>
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 DDE6CC1519A6 for <cbor@ietfa.amsl.com>; Tue, 14 Nov 2023 08:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=nic.cz
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 t5308PtByy7H for <cbor@ietfa.amsl.com>; Tue, 14 Nov 2023 08:54:04 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 9B181C15198C for <cbor@ietf.org>; Tue, 14 Nov 2023 08:54:04 -0800 (PST)
Received: from [IPV6:2001:1488:fffe:6:ffff:ffff:fffe:4] (unknown [IPv6:2001:1488:fffe:6:ffff:ffff:fffe:4]) by mail.nic.cz (Postfix) with ESMTPSA id A2A771C192D; Tue, 14 Nov 2023 17:54:00 +0100 (CET)
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=maria.matejka@nic.cz smtp.mailfrom=maria.matejka@nic.cz
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1699980840; bh=V4rC+TBF1JwL9oJre0c/uvvyOuqK8E4yQxia82sfxsM=; h=Date:To:Cc:From:Subject:From:Reply-To:Subject:To:Cc; b=F15/J0psh80FMl9BrLKPAPltMmZi9cLcZORtXwVHswcY1NjeTDZhL9wy+M0NltTx4 KMZRH2fSYWMoKTi29x5p5VUaEfVhZdTnaFOjhDG3EQUnzqb3nXvsIMpj0F6VrJIFVY quy5R9zwzmjTkKGO1JT2ZFRhaCVz4WvW+OYL1Ggs=
Content-Type: multipart/alternative; boundary="------------JoN9Nd3qc9ySSIIE2atH5PfQ"
Message-ID: <77159997-0cc1-4b5d-9a1d-cc61f3d0be73@nic.cz>
Date: Tue, 14 Nov 2023 17:54:00 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US, cs
To: cbor@ietf.org
Cc: Kateřina Kubecová <katerina.kubecova@nic.cz>, vojtech.vilimek@nic.cz
From: Maria Matejka <maria.matejka@nic.cz>
X-Virus-Scanned: clamav-milter 0.103.7 at mail
X-Virus-Status: Clean
X-Rspamd-Server: mail
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP
X-Rspamd-Queue-Id: A2A771C192D
X-Spamd-Bar: /
X-Spamd-Result: default: False [-0.10 / 20.00]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FUZZY_BLOCKED(0.00)[rspamd.com]; WHITELISTED_IP(0.00)[2001:1488:fffe:6:ffff:ffff:fffe:4]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]
X-Rspamd-Action: no action
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1yoTIQ2hmItAZbQFadqeJj212q0>
Subject: [Cbor] CBOR-YANG representation of common types
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: Tue, 14 Nov 2023 16:54:09 -0000

Dear CBOR WG,

we're currently trying to embrace the CBOR described by YANG in BIRD 
interface and we're struggling with the representation of certain types 
like date, time, IP address or prefix. We would assume that if there is 
RFC 9164 or RFC 8943, we shall then encode dates or IP addresses in 
these defined formats in CBOR and they shall get converted between CBOR 
and JSON/XML appropriately. But I can't find any RFC on this, nor any 
implementation of CBOR-JSON convertor.

Thus, these questions arise:

  * Is there any discussion on this topic, regarding interoperability
    between CBOR and JSON/XML?
  * Is there any RFC on draft on this? If not, we're probably gonna
    create one. We need it
  * Is there any implementation of YANG-ed converter between CBOR and
    JSON? If not, we're probably gonna create one. We need it.

Thank you for considering our questions.
Maria and the BIRD Team

-- 
Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

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