[core] Content-Format size for yang-cbor
Carsten Bormann <cabo@tzi.org> Tue, 16 March 2021 20:10 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F523A043E for <core@ietfa.amsl.com>; Tue, 16 Mar 2021 13:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 GvVhWxDP6Gpy for <core@ietfa.amsl.com>; Tue, 16 Mar 2021 13:10:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 728F83A0A86 for <core@ietf.org>; Tue, 16 Mar 2021 13:10:39 -0700 (PDT)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F0PY9337CzyVc; Tue, 16 Mar 2021 21:10:37 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 637618236.17892-fad51877ce2bf7a07925a14667a3bebe
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 16 Mar 2021 21:10:36 +0100
Message-Id: <299C6908-F83E-42D3-87B1-883C12075780@tzi.org>
To: "core@ietf.org WG (core@ietf.org)" <core@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/vK5bt9YW1bFRYkKZ7tB218DGssM>
Subject: [core] Content-Format size for yang-cbor
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Mar 2021 20:10:43 -0000
In the IANA review of draft-ietf-core-yang-cbor, the question was raised what allocation range should be used for the content-format number for application/yang-data+cbor;id=name I believe this content-type will be used mostly for less size-sensitive applications, as a name is used for YANG identifiers and not a YANG SID. So I think we are fine in the range: 256-9999 IETF Review or IESG Approval e.g., 260. Any disagreement (or support)? Grüße, Carsten
- [core] Content-Format size for yang-cbor Carsten Bormann
- Re: [core] Content-Format size for yang-cbor Alexander Pelov
- Re: [core] Content-Format size for yang-cbor (and… Carsten Bormann
- Re: [core] Content-Format size for yang-cbor (and… Alexander Pelov