IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 24 October 2023 14:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0A2D3C14F749 for <core@ietfa.amsl.com>; Tue, 24 Oct 2023 07:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, 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, 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 (2048-bit key) header.d=sandelman.ca
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 k0zzPK4kZxmo for <core@ietfa.amsl.com>; Tue, 24 Oct 2023 07:16:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7470C14CE3B for <core@ietf.org>; Tue, 24 Oct 2023 07:16:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 474641800D for <core@ietf.org>; Tue, 24 Oct 2023 10:16:22 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wLYU-yS5jINi for <core@ietf.org>; Tue, 24 Oct 2023 10:16:21 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 9DE811800C for <core@ietf.org>; Tue, 24 Oct 2023 10:16:21 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1698156981; bh=ZXts90XqzTPNBBcg6xUPsQjYwxeTrxj6PDCPnH4zrgM=; h=From:To:Subject:In-Reply-To:References:Date:From; b=dj3mIXU1hTNHfI7ofl5+y/bMVAj+AuINXbMGCwT4iENLq+7XEdaZwxGDL9qwh4NoK jsQ9t8WS/ABkIEuyaFHS7UmIZMMJWRsqto07ChJ6j3NOdamsFgpfcFfnZqNwK2zv7Y iGAGiC/5kn4nTPHce8hxtLuXpLraxjN2hfncHQwPHgKTyh4E6EuEnbKmOtLeXNsbV5 ffpRR8/2TphpbReDQH0+hjiaWwb0uNJoGos1DRuClqE9kF0Egqezs7BEMmj5Rxl+Ry BSRq5RiqpoeXb5OMjqoqtsxwIyNngDIGKu+zrsI9MvUkFgcnNdhWqWOeAMe7zix0um F1hwcW7t4dZ/g==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 576991C9 for <core@ietf.org>; Tue, 24 Oct 2023 10:16:21 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: core@ietf.org
In-Reply-To: <core-wg/yang-cbor/pull/159/review/1693455422@github.com>
References: <core-wg/yang-cbor/pull/159@github.com> <core-wg/yang-cbor/pull/159/review/1693455422@github.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 24 Oct 2023 10:16:21 -0400
Message-ID: <29493.1698156981@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/V47irX3XU9HwwXyr6KXZO4ymo-E>
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:16:28 -0000

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 don't think the document should discuss procedural steps of the RPC such as AUTH48.
    > It is clear that the RFC editor needs to do "something", so we don't
    > need to go into that level of (brittle) detail.

I don't care how we write it.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email