IETF Logo Mail Archive

Re: [Cbor] Status of CBOR CRS Specification

Chris Lemmons <alficles@gmail.com> Fri, 03 March 2023 18:40 UTC

Return-Path: <alficles@gmail.com>
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 0D4CBC14F72F for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 10:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.com
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 jq_-Jyc3wcBn for <cbor@ietfa.amsl.com>; Fri, 3 Mar 2023 10:40:03 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4F1A0C1516E9 for <cbor@ietf.org>; Fri, 3 Mar 2023 10:40:03 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id i34so14007650eda.7 for <cbor@ietf.org>; Fri, 03 Mar 2023 10:40:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677868802; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Lr6M1XaB8MioIFMctsBHaSI3WGSf5mr6uZIacdoM7wA=; b=AiZhMVTfXX5fCC2ByF6Wk7dWcsa0ibj7SEDfgdaaHMm/wfCjPb5Y2P4EKFK13R+9af h9HeHuCRyzuvWOFJYhDMt7NudlMO0MTPlqSCY+N6hHQrSAXi4/yjbMTZS9p7IlMLm52F bZY5vZ4ryQhTxhwKOHIpG2FUjCW4UOF33S38aZNPgeKqYtKrWqvqN/YcP1Q+CwAL1qEg NV9Z9/MkVgQDYC98n2KysZ/xO3PuZ+xsOkUUPYJc53+uB9JBW5StT2Fb+K+p7zV9k+Tm 0PzHtcjkh9kYRNeuuJjvB7Zkkap2p5m+sSUAgKjOFr+sT0tzIVoqlzWE7XOzIT19o3HL VmPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677868802; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Lr6M1XaB8MioIFMctsBHaSI3WGSf5mr6uZIacdoM7wA=; b=cUL+jqBO+uOKgtMgxmBABNSO/Mz+Uc1Vx9kjzO57cXOSpssVqkUJ3PLggQaogX1CJn DHp3FPD+aZAle4YIIQZQHIP2afzMBe4e22qQp9shWL/ZNkDsSDc4VRaI6oas9mtn3JYW 6nULWPC0FWxRxvjcmbxijU55QIz9UShG9lWuKCWufiim3rn2uQaWV3oZIgv/7ruryeRk aNTYrB+5hhg2snRB8JyBPgFga1A+nmm+gzQrIEEaHqJmKU52oi9j2WZmeYHOrK7hZHH7 AvGgelWW720x5lSF7M1kFMhEIek+ZdhOHG88Xg9RxfKE64Bo8kJGOJrZUZ7tw6HDA1H3 G/UQ==
X-Gm-Message-State: AO0yUKUO5nYeHSv1Smz9XO6nuE7wQExvBHZqbc/gwIHmWn4uJGtcobrK Eik718uWqoxyDpAoDcwlQZpEZ0xLzevfHHSNVtP5MIrD
X-Google-Smtp-Source: AK7set97c1cZgg8kGDZXMEuU41eCp2pQ2IU0ktyPJ87DMruOrdvTlmaR/ABfwRmIVoGjpXdVZi3D9gJNAtMiKxoNQnE=
X-Received: by 2002:a17:906:6b1a:b0:877:747d:4a85 with SMTP id q26-20020a1709066b1a00b00877747d4a85mr1364023ejr.3.1677868801633; Fri, 03 Mar 2023 10:40:01 -0800 (PST)
MIME-Version: 1.0
References: <CAJEGKNtpnxr14yn0gcta+7uia4KW=8KdJUs9z7ykUhghv7fwpg@mail.gmail.com> <1797252.1677847990@dyas> <CE76A0CA-C060-412B-85FE-23CFAD3282A1@tzi.org>
In-Reply-To: <CE76A0CA-C060-412B-85FE-23CFAD3282A1@tzi.org>
From: Chris Lemmons <alficles@gmail.com>
Date: Fri, 03 Mar 2023 11:39:49 -0700
Message-ID: <CAJEGKNuzqYBc_cjeEv81PRG3u8a+sQTkU62M8d4jA9piabEcHA@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cbor@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Z5sGeVJlSK8U5cG6h_hXa1FUyyU>
Subject: Re: [Cbor] Status of CBOR CRS Specification
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: Fri, 03 Mar 2023 18:40:07 -0000

I emailed the author directly about it a month ago, but didn't get a
response. It's quite possible that they've got more pressing things to
attend to or just missed my message.

As for whether it's useful to have an RFC, that's an interesting
question. I'd probably have done a mere registration for this one, but
it's already three-quarters done as a draft. It's not a ton of work to
just get it over the finish line.

On Fri, Mar 3, 2023 at 6:09 AM Carsten Bormann <cabo@tzi.org> wrote:
>
>
>
> > On 2023-03-03, at 13:53, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> >
> > Signed PGP part
> >
> > Chris Lemmons <alficles@gmail.com> wrote:
> >> This leaves me with two options: define a new tag fit for precisely the
> >> purpose I need, or see if there's interest in finishing the work that
> >> was started with Tag 104. It does seem like having two tags, especially
> >> with one in the low-numbered space, is not ideal.
> >
> >> The draft is here:
> >> https://datatracker.ietf.org/doc/draft-clarke-cbor-crs/
> >
> >> For context, I need a CRS tag that can "wrap" other content to describe
> >> the CRS for that which it encloses. I can define it as necessary, but
> >> reuse is usually better. Is there any interest in picking up the work
> >> of Tag 104? Is this even an appropriate venue for that?
> >
> > I think that CBOR is the right place for this.
> > Try reaching out to the author, T.Clarke @ Ball.  If he doesn't have time to
> > pursue this document and make you a co-author, then we have the XML for it,
> > and could just take it over.  Once adopted, document authors serve at the
> > pleasure of the wg chairs, so changing authors isn't a problem.
> > (just have to give credit where it is due)
> >
> > It's possible to do new tags in ~1 year as evidenced by RFC9164 and 9277.
> > (Actually, I think they could have happened even faster)
>
> If it is useful to have an RFC, this is correct; a mere registration can be done much more quickly.
>
> Grüße, Carsten
>
>
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

v2.23.0 | Report a Bug | By Email