[core] CoAP Options for CRI (and URI scheme number) use in CoAP
Carsten Bormann <cabo@tzi.org> Wed, 22 November 2023 12:30 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 773C6C151082 for <core@ietfa.amsl.com>; Wed, 22 Nov 2023 04:30:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 3CMdnqJtIvh6 for <core@ietfa.amsl.com>; Wed, 22 Nov 2023 04:30:09 -0800 (PST)
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 A9CE8C151070 for <core@ietf.org>; Wed, 22 Nov 2023 04:30:08 -0800 (PST)
Received: from smtpclient.apple (p548dcbf2.dip0.t-ipconnect.de [84.141.203.242]) (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 4Sb0v15k4TzDCdG; Wed, 22 Nov 2023 13:30:05 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Date: Wed, 22 Nov 2023 13:29:54 +0100
Message-Id: <675475E0-1845-4E28-BD35-B9C1CDD75BD5@tzi.org>
To: core <core@ietf.org>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/n3tLtYVud1OEZ74J6uRsuFqluwQ>
Subject: [core] CoAP Options for CRI (and URI scheme number) use in CoAP
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: Wed, 22 Nov 2023 12:30:13 -0000
As an input for today’s CoRE interim, I have created a pull request that defines CoAP Options for CRI (and URI scheme number) use in CoAP: https://github.com/core-wg/href/pull/81 (In formatted form:) https://core-wg.github.io/href/coap-integration/draft-ietf-core-href.html#name-coap-options-for-forward-pr (It also has a placeholder for the procedures of converting between CoAP Options and CRIs; to be filled in later.) Comments welcome here, in GitHub, and/or in the interim meeting in 2.5 hours. Grüße, Carsten
- [core] CoAP Options for CRI (and URI scheme numbe… Carsten Bormann