IETF Logo Mail Archive

[Ace] [IANA #1303039] expert review for draft-ietf-ace-wg-coap-eap (core-parameters, CoAP Content-Formats)

David Dong via RT <drafts-expert-review-comment@iana.org> Fri, 26 January 2024 18:27 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 072AAC14F68D for <ace@ietfa.amsl.com>; Fri, 26 Jan 2024 10:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.636
X-Spam-Level:
X-Spam-Status: No, score=-5.636 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, 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
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 aCsa5eGLyDo6 for <ace@ietfa.amsl.com>; Fri, 26 Jan 2024 10:27:32 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (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 E0412C14F681 for <ace@ietf.org>; Fri, 26 Jan 2024 10:27:32 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id C3C0AE142D; Fri, 26 Jan 2024 18:27:32 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id C0DC24AF4F; Fri, 26 Jan 2024 18:27:32 +0000 (UTC)
RT-Owner: david.dong
From: David Dong via RT <drafts-expert-review-comment@iana.org>
Reply-To: drafts-expert-review-comment@iana.org
In-Reply-To: <rt-5.0.3-114668-1705702877-950.1303039-9-0@icann.org>
References: <RT-Ticket-1303039@icann.org> <rt-5.0.3-872909-1705020114-1329.1303039-9-0@icann.org> <rt-5.0.3-872909-1705021772-1730.1303039-9-0@icann.org> <DU0P190MB19786D09779887659E5C8B2DFD6F2@DU0P190MB1978.EURP190.PROD.OUTLOOK.COM> <rt-5.0.3-928320-1705053337-826.1303039-9-0@icann.org> <rt-5.0.3-969786-1705080457-1375.1303039-9-0@icann.org> <rt-5.0.3-114668-1705702877-950.1303039-9-0@icann.org>
Message-ID: <rt-5.0.3-351702-1706293652-1075.1303039-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1303039
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: david.dong@iana.org
CC: rafa@um.es, garciadan@uniovi.es, loganaden@gmail.com, tim.hollebeek@digicert.com, rdd@cert.org, paul.wouters@aiven.io, ace@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Fri, 26 Jan 2024 18:27:32 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/EFGUgphctqsYi5bKQaFyxXzM3h4>
Subject: [Ace] [IANA #1303039] expert review for draft-ietf-ace-wg-coap-eap (core-parameters, CoAP Content-Formats)
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2024 18:27:37 -0000

Dear Authors/Chairs/ADs,

Following up on this; please see below for comments from the expert. Please let us know how you would like to respond.

--

I believe the draft would need a few updates to clarify the new media type and the precise request.

* application/coap-eap is registered but never used (i.e. referred to by name) from any other section.
* I couldn't find an explicit format/syntax definition for this new media type.
* Is it equal to the CBOR data format defined in Section 4? If so, then section 4 should mention at least the name of the new media type and section 8.5 ideally should give a quick pointer to section 4 for the format definition.
* the text in 8.6 should better refer to Section 12.3 of [RFC 7252] for the registry; link to [RFC 6690] is not so useful here.
The text says "Expert Review" but that's only for the 0-255 range. For this range some additional motivation is required why it needs to be there, and this is missing.
For the 256-9999 range the procedure is "IETF review" -> did you mean to select this range?

It would be ok to continue the registration with the current draft, if the authors want to make text clarifications later on and not now.
A number in the 256-9999 is for sure ok (if that's intended), for example 260, but for 0-255 range some reason/rationale needs to be provided.

--

Best regards,

David Dong
IANA Services Sr. Specialist


On Fri Jan 19 22:21:17 2024, david.dong wrote:
> Dear Authors/Chairs/ADs,
> 
> Following up on this; please see below for comments from the expert.
> 
> --
> 
> I believe the draft would need a few updates to clarify the new media
> type and the precise request.
> 
> * application/coap-eap is registered but never used (i.e. referred to
> by name) from any other section.
> * I couldn't find an explicit format/syntax definition for this new
> media type.
> * Is it equal to the CBOR data format defined in Section 4? If so,
> then section 4 should mention at least the name of the new media type
> and section 8.5 ideally should give a quick pointer to section 4 for
> the format definition.
> * the text in 8.6 should better refer to Section 12.3 of [RFC 7252]
> for the registry; link to [RFC 6690] is not so useful here.
> The text says "Expert Review" but that's only for the 0-255 range. For
> this range some additional motivation is required why it needs to be
> there, and this is missing.
> For the 256-9999 range the procedure is "IETF review" -> did you mean
> to select this range?
> 
> It would be ok to continue the registration with the current draft, if
> the authors want to make text clarifications later on and not now.
> A number in the 256-9999 is for sure ok (if that's intended), for
> example 260, but for 0-255 range some reason/rationale needs to be
> provided.
> 
> --
> 
> Best regards,
> 
> David Dong
> IANA Services Sr. Specialist
> 
> On Fri Jan 12 17:27:37 2024, david.dong wrote:
> > Dear Authors/Chairs/ADs,
> >
> > Please see below for comments from the expert.
> >
> > --
> >
> > I believe the draft would need a few updates to clarify the new media
> > type and the precise request.
> >
> > * application/coap-eap is registered but never used (i.e. referred to
> > by name) from any other section.
> > * I couldn't find an explicit format/syntax definition for this new
> > media type.
> > * Is it equal to the CBOR data format defined in Section 4? If so,
> > then section 4 should mention at least the name of the new media type
> > and section 8.5 ideally should give a quick pointer to section 4 for
> > the format definition.
> > * the text in 8.6 should better refer to Section 12.3 of [RFC 7252]
> > for the registry; link to [RFC 6690] is not so useful here.
> > The text says "Expert Review" but that's only for the 0-255 range.
> > For
> > this range some additional motivation is required why it needs to be
> > there, and this is missing.
> > For the 256-9999 range the procedure is "IETF review" -> did you mean
> > to select this range?
> >
> > It would be ok to continue the registration with the current draft,
> > if
> > the authors want to make text clarifications later on and not now.
> > A number in the 256-9999 is for sure ok (if that's intended), for
> > example 260, but for 0-255 range some reason/rationale needs to be
> > provided.
> >
> > --
> >
> > Best regards,
> >
> > David Dong
> > IANA Services Sr. Specialist
> >
> > On Fri Jan 12 09:55:37 2024, esko.dijk@iotconsultancy.nl wrote:
> > > Hello,
> > >
> > > I believe the draft would need a few updates to clarify the new
> > > media
> > > type and the precise request.
> > >
> > > * application/coap-eap is registered but never used (i.e. referred
> > > to
> > > by name) from any other section.
> > > * I couldn't find an explicit format/syntax definition for this new
> > > media type.
> > > * Is it equal to the CBOR data format defined in Section 4? If so,
> > > then section 4 should mention at least the name of the new media
> > > type
> > > and section 8.5 ideally should give a quick pointer to section 4
> > > for
> > > the format definition.
> > > * the text in 8.6 should better refer to Section 12.3 of [RFC 7252]
> > > for the registry; link to [RFC 6690] is not so useful here.
> > >    The text says "Expert Review" but that's only for the 0-255
> > > range.
> > > For this range some additional motivation is required why it needs
> > > to
> > > be there, and this is missing.
> > >    For the 256-9999 range the procedure is "IETF review" -> did you
> > > mean to select this range?
> > >
> > > It would be ok to continue the registration with the current draft,
> > > if
> > > the authors want to make text clarifications later on and not now.
> > > A number in the 256-9999 is for sure ok (if that's intended), for
> > > example 260, but for 0-255 range some reason/rationale needs to be
> > > provided.
> > >
> > > Regards
> > > Esko
> > >
> > >
> > > -----Original Message-----
> > >  From: David Dong via RT <drafts-expert-review-comment@iana.org>
> > > Sent: Friday, January 12, 2024 02:10
> > > Cc: Esko Dijk <esko.dijk@iotconsultancy.nl>; hartke@projectcool.de;
> > > cabo@tzi.org; jaime@iki.fi; jaime.jimenez@ericsson.com;
> > > alexander@ackl.io; ace@ietf.org
> > > Subject: [IANA #1303039] expert review for draft-ietf-ace-wg-coap-
> > > eap
> > > (core-parameters, CoAP Content-Formats)
> > >
> > > Dear Esko Dijk (cc: ace WG),
> > >
> > > As the designated expert for the CoAP Content-Formats registry, can
> > > you review the proposed registration in draft-ietf-ace-wg-coap-eap-
> > > 09
> > > for us? Please see:
> > >
> > > https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap/
> > >
> > > The due date is January 25.
> > >
> > > 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/
> > >
> > > With thanks,
> > >
> > > David Dong
> > > IANA Services Sr. Specialist

v2.23.0 | Report a Bug | By Email