Re: [core] [core-wg/yang-cbor] Describe publication process (addressing Rob Wilton's DISCUSS) (PR #159)

Carsten Bormann <cabo@tzi.org> Tue, 24 October 2023 14:23 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 5A7ADC151548 for <core@ietfa.amsl.com>; Tue, 24 Oct 2023 07:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 SRUxNMidMDqr for <core@ietfa.amsl.com>; Tue, 24 Oct 2023 07:23:24 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 DFEB0C14CE3B for <core@ietf.org>; Tue, 24 Oct 2023 07:23:22 -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 4SFDn42VwrzDCdZ; Tue, 24 Oct 2023 16:23:20 +0200 (CEST)
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: <29493.1698156981@localhost>
Date: Tue, 24 Oct 2023 16:23:19 +0200
Cc: core@ietf.org
X-Mao-Original-Outgoing-Id: 719850199.7752891-f0a1eba6645749e248d09ec320feb2cd
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BB3BD97-0669-4487-96C1-B634A1BD0D0B@tzi.org>
References: <core-wg/yang-cbor/pull/159@github.com> <core-wg/yang-cbor/pull/159/review/1693455422@github.com> <29493.1698156981@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/e8Le1Dqa8FtdzZ5joZ-u2eDL90A>
Subject: Re: [core] [core-wg/yang-cbor] Describe publication process (addressing Rob Wilton's DISCUSS) (PR #159)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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, 24 Oct 2023 14:23:27 -0000


> On 2023-10-24, at 16:16, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> In a github pull request, already merged, at:
> https://github.com/core-wg/yang-cbor/pull/159#discussion_r1369223213
> 
> cabo <notifications@github.com> wrote:
>>> +RFCs that need SIDs assigned to their new modules for use in the text
>> +of the document, e.g., for examples, need to alert the RFC editor in
>> +the draft text that this is the case.
> 
>> I'm not sure the SIDTBDXX approach works too well, but it clearly is
>> one way of alerting the RFC editor.
>> In the CBOR context, we like the examples to actually parse, and
>> SIDTBDXX often won't.
> 
> Yes, this is the struggle.  We need real allocations to do the CBOR, and we
> can't really expect the RPC to renegerate that, so we need a step where the
> authors do that work after IANA allocation, but before publication.
> I think that if there isn't an early allocation, that the authors wind up
> using experimental values, and then putting SIDTBDXX in the comment.

I would expect drafts like the constrained voucher draft to go for early allocation and type-1 processing, which should solve this problem neatly.

Grüße, Carsten