[core-parameters] [IANA #1229125] expert review for draft-ietf-anima-constrained-join-proxy (core-parameters)
Amanda Baber via RT <drafts-expert-review-comment@iana.org> Fri, 19 August 2022 00:27 UTC
Return-Path: <iana-shared@icann.org>
X-Original-To: core-parameters@ietfa.amsl.com
Delivered-To: core-parameters@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E48C1524D2 for <core-parameters@ietfa.amsl.com>; Thu, 18 Aug 2022 17:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.636
X-Spam-Level:
X-Spam-Status: No, score=-0.636 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, 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=no 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 vMVvRqOdeaZ3 for <core-parameters@ietfa.amsl.com>; Thu, 18 Aug 2022 17:27:02 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35C8EC1524D1 for <core-parameters@ietf.org>; Thu, 18 Aug 2022 17:27:02 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id F217DEDBA3; Fri, 19 Aug 2022 00:27:01 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id EFDC920FAF; Fri, 19 Aug 2022 00:27:01 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <drafts-expert-review-comment@iana.org>
Reply-To: drafts-expert-review-comment@iana.org
In-Reply-To: <rt-4.4.3-25544-1649176784-236.1229125-9-0@icann.org>
References: <RT-Ticket-1229125@icann.org> <rt-4.4.3-25544-1649176784-236.1229125-9-0@icann.org>
Message-ID: <rt-4.4.3-16093-1660868821-930.1229125-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1229125
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: jaime.jimenez@ericsson.com, cabo@tzi.org, core-parameters@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 19 Aug 2022 00:27:01 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/core-parameters/ceZKGokSMDHb63WWnJnM8k0suRA>
Subject: [core-parameters] [IANA #1229125] expert review for draft-ietf-anima-constrained-join-proxy (core-parameters)
X-BeenThere: core-parameters@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Expert review of CoAP parameters." <core-parameters.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core-parameters/>
List-Post: <mailto:core-parameters@ietf.org>
List-Help: <mailto:core-parameters-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core-parameters>, <mailto:core-parameters-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2022 00:27:06 -0000
Hi Carsten, Has this been resolved? Is it possible to approve the current version of these registrations (pending IESG approval for publication)? thanks, Amanda On Tue Jul 12 21:25:30 2022, amanda.baber wrote: > Hi Carsten, Jaime (cc: anima), > > Can you approve the Resource Type (rt=) Link Target Attribute Values > registrations in version -11 of this document? > > https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained- > join-proxy > > thanks, > Amanda > > On Thu Apr 07 21:44:01 2022, sabrina.tanamal wrote: > > Hi Carsten, > > > > We have a response from the author: > > > > Thanks for your reaction. > > Suggestion for new readable titles are below. I will insert them in > > the coming version 10 of the draft. > > > > __________________________________________________________________ > > OLD > > Attribute Value: brski.jp > > Description: This BRSKI resource type is used to query and return > > the > > supported BRSKI (CoAP over DTLS) port of the > > constrained > > Join Proxy. > > Reference: [this document] > > > > Attribute Value: brski.rjp > > Description: This BRSKI resource type is used to query and return the > > supported BRSKI JPY protocol port of the Registrar. > > Reference: [this document] > > > > NEW > > > > Attribute Value: brski.jp > > Description: This BRSKI resource type is used to query and return the > > supported BRSKI resources of the constrained Join Proxy. > > Reference: [this document] > > > > Attribute Value: brski.rjp > > Description: This BRSKI resource type is used for the constrained > > Join > > Proxy > > to query and return Join Proxy specific BRSKI resources > > of a Registrar. > > Reference: [this document] > > > > ___________________________________________________________ > > Hope this is understandable enough, > > > > ==== > > > > Best regards, > > > > Sabrina Tanamal > > Lead IANA Services Specialist > > > > On Tue Apr 05 20:30:05 2022, cabo@tzi.org wrote: > > > Hi Sabrina, > > > > > > I looked at the registration requests in the draft. > > > They use somewhat unusual language about discovering ports - > > > resource > > > discovery is understood to discover resources. For brski.jp, this > > > appears to be about discovering a CoAP or CoAPs entry point > > > (without > > > describing how exactly that is then used, e.g., what happens if > > > that > > > has a different IP address in the authority than the request > > > address). > > > For brski.rjp, this appears to be about discovering an entry point > > > for > > > a protocol that I don’t seem to fully understand the description > > > for. > > > > > > I didn’t try to obtain a deep understanding of the protocol before > > > writing this, but I would prefer if the language used for the > > > description were understandable for other registrants in this > > > registry, i.e., discussing resources, not ports (port numbers?). > > > > > > All the other criteria for a registration appear to be fulfilled. > > > > > > I don’t think we need to reach a consensus between the designated > > > experts before proceeding. > > > > > > Grüße, Carsten > > > > > > > > > > On 2022-04-05, at 18:43, Sabrina Tanamal via RT <drafts-expert- > > > > review-comment@iana.org> wrote: > > > > > > > > Carsten and Jaime (cc: anima WG), > > > > > > > > As the designated experts for the Resource Type (rt=) Link Target > > > > Attribute Values registry, can you review the proposed > > > > registrations > > > > in draft-ietf-anima-constrained-join-proxy for us? Please see > > > > > > > > https://datatracker.ietf.org/doc/draft-ietf-anima-constrained- > > > > join- > > > > proxy/ > > > > > > > > If this is OK, when the IESG approves the document for > > > > publication, > > > > we'll make the registration at > > > > > > > > https://www.iana.org/assignments/core-parameters > > > > > > > > If you're the first expert to submit a review, please let us know > > > > whether you want us to wait for both reviewers to respond before > > > > we > > > > mark the document "IANA OK" (or send your comments to the > > > > authors, > > > > if > > > > the registrations aren't OK). > > > > > > > > The IESG has asked us to set a two-week deadline for registration > > > > reviews. The due date for this request is 19 April 2022. > > > > > > > > thanks, > > > > > > > > Sabrina Tanamal > > > > Lead IANA Services Specialist > > > >
- [core-parameters] [IANA #1229125] expert review f… Amanda Baber via RT
- Re: [core-parameters] [IANA #1229125] expert revi… Esko Dijk