IETF Logo Mail Archive

[core] Re: [IANA #1456214] Early review: draft-ietf-anima-constrained-join-proxy-20 (IETF 126)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 18 July 2026 14:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: core@mail2.ietf.org
Delivered-To: core@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 57044118E9F83; Sat, 18 Jul 2026 07:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784386507; bh=Ur3G/XUsjvaPMQUtZaR+brbRJkYCNCNkJPoX3wVXOe0=; h=From:To:CC:Subject:In-Reply-To:References:Date; b=pIbb62LOrFqYG/L6OSY7vg1OJSwEPguC15znS+1iwI8gSw1qRXkTxZnWo3k7rEGVZ cmI9JCvWiNskuZ0alKAh3eoEEIpMXP66UOOGx10PO1dqAJHOJYd6Wznz1ihVjVTwtZ bD8AQ045QlmrfnAnTHl/d0SsaRWQVqEt82hJaIUY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SVUN9urp16Cm; Sat, 18 Jul 2026 07:55:06 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CB4AF118E9F7A; Sat, 18 Jul 2026 07:55:03 -0700 (PDT)
Received: from dyas.sandelman.ca (nat64-44.users.meeting.ietf.org [31.130.238.68]) by relay.sandelman.ca (Postfix) with ESMTPS id 172041F46D; Sat, 18 Jul 2026 14:55:03 +0000 (UTC)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id B5EEDA014D; Sat, 18 Jul 2026 10:55:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iana-issues@iana.org, draft-ietf-anima-constrained-join-proxy.all@ietf.org, anima@ietf.org
In-Reply-To: <rt-5.0.3-797414-1784297396-1715.1456214-37-0@icann.org>
References: <RT-Ticket-1456214@icann.org> <rt-5.0.3-797414-1784297343-1382.1456214-37-0@icann.org> <rt-5.0.3-797414-1784297396-1715.1456214-37-0@icann.org>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 29.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 18 Jul 2026 16:55:01 +0200
Message-ID: <768915.1784386501@dyas>
Message-ID-Hash: R6TM3HZCIGKU6XH45OYOH4EEXAOECQCH
X-Message-ID-Hash: R6TM3HZCIGKU6XH45OYOH4EEXAOECQCH
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-core.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: core@ietf.org, core-parameters@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [core] Re: [IANA #1456214] Early review: draft-ietf-anima-constrained-join-proxy-20 (IETF 126)
List-Id: "Constrained RESTful Environments (CoRE) Working Group list" <core.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/8ZqWKsGyXpGBlc7vifnC3nOBFcM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Owner: <mailto:core-owner@ietf.org>
List-Post: <mailto:core@ietf.org>
List-Subscribe: <mailto:core-join@ietf.org>
List-Unsubscribe: <mailto:core-leave@ietf.org>

https://github.com/anima-wg/constrained-join-proxy/commit/ae753b1d9bdfda9bd92633c6270e73af1ae33590

Amanda Baber via RT <iana-issues@iana.org> wrote:
    > https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-join-proxy-20

    > Section 8.3: draft-ietf-core-href (currently in the RFC Ed Queue) added
    > a field called "CRI Scheme Number" to the URI Schemes registry. Please
    > add one of the following lines to the URI scheme registration template:

    > CRI Scheme Number: TBA from the Expert Review range
    > CRI Scheme Number: TBA from the First Come First Served range

okay...

But, href-30 says:

   |  Identifier (URI) Schemes Registry may indicate that there are
   |  special requirements on the CRI scheme number to be assigned for
   |  the new URI Scheme.
   |  If that is not the case, IANA will assign a value autonomously.

As we *DO NOT* have special requirements, it would be fine:

   If no requirement is specified in the registration, IANA will
   autonomously assign a number in the range 1000 to 20000, inclusive,
   that has not yet been used.


(As far as I know, we can not use the CRI in the core?rt= reply)

    > Section 8.4: According to RFC 6335, Section 8.1.1, the contact for the
    > port registrations should be the IETF Chair <chair@ietf.org> rather
    > than the IESG.

Okay.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.46.0 | Report a Bug | By Email | System Status