Re: [core-parameters] Content-Format registration review request for application/yang-sid+json
Carsten Bormann <cabo@tzi.org> Tue, 31 October 2023 14:20 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: core-parameters@ietfa.amsl.com
Delivered-To: core-parameters@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF09EC16F3EF for <core-parameters@ietfa.amsl.com>; Tue, 31 Oct 2023 07:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 yAOFra52wv6n for <core-parameters@ietfa.amsl.com>; Tue, 31 Oct 2023 07:20:54 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 1D040C16F3F6 for <core-parameters@ietf.org>; Tue, 31 Oct 2023 07:20:26 -0700 (PDT)
Received: from eduroam-pool10-182.wlan.uni-bremen.de (eduroam-pool10-182.wlan.uni-bremen.de [134.102.90.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4SKXNR3JBFzDCg4; Tue, 31 Oct 2023 15:20:23 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DU0P190MB197852C2B4396E9CCFB85466FDA0A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
Date: Tue, 31 Oct 2023 15:20:20 +0100
Cc: "core-parameters@ietf.org" <core-parameters@ietf.org>
X-Mao-Original-Outgoing-Id: 720454820.91919-2df6067822cf17f8df6547f0ce7b81bc
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3B680EF-5B3E-43EF-BD8B-E6D514AF9249@tzi.org>
References: <C555167D-4471-4148-A4C2-ADFA215A4673@tzi.org> <DU0P190MB197872DE7E0B5DA5181217C1FDA0A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <D96F361E-60DF-48EE-B9E6-EE10E6692ECC@tzi.org> <DU0P190MB197852C2B4396E9CCFB85466FDA0A@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM>
To: Esko Dijk <esko.dijk@iotconsultancy.nl>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/Qiu3c9QbTMmlkK-XSf-ICZllwQE>
Subject: Re: [core-parameters] Content-Format registration review request for application/yang-sid+json
X-BeenThere: core-parameters@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Expert review of CoAP parameters." <core-parameters.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core-parameters/>
List-Post: <mailto:core-parameters@ietf.org>
List-Help: <mailto:core-parameters-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Oct 2023 14:20:56 -0000
> I recall once discussing this at a CoRE meeting - but do we have a draft or other documentation for this experiment? We didn’t write this up, in part because we didn’t know what IANA would be willing to do. With target-attr we now have a model for simultaneous registrations. > Currently any existing media types can be registered in the FCFS section of the registry, >= 10000, without any expert consultation (i.e. no email on this list). There are already a few of these registered. > And it cannot be traced who registered it. > > Once the content-format is registered, it's not clear if a duplicate other number for the same media type should be allowed or not. Probably not. IANA could check this (making the media-type-name a unique key). > RFC 7252 doesn't say anything about that. Not really; up to now this was in the heads of the DEs. Grüße, Carsten
- [core-parameters] Content-Format registration rev… Carsten Bormann
- Re: [core-parameters] Content-Format registration… Esko Dijk
- Re: [core-parameters] Content-Format registration… Carsten Bormann
- Re: [core-parameters] Content-Format registration… Esko Dijk
- Re: [core-parameters] Content-Format registration… Carsten Bormann