Hello Dan, Thanks - as soon as the proposed updates are included the registration can be approved. @David It will be a number from the 256-999 subset (e.g. 261) of the 256-9999 range.
Esko -----Original Message----- From: Dan Garcia Carrillo <[email protected]> Sent: Monday, January 29, 2024 10:16 To: Esko Dijk <[email protected]> Cc: [email protected]; [email protected] Subject: Re: [Ace] [IANA #1303039] expert review for draft-ietf-ace-wg-coap-eap (core-parameters, CoAP Content-Formats) Dear Esko, Thank you for your comments. Please, see responses inline. El 12/1/24 a las 10:55, Esko Dijk escribió: > 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. We will update the figures and text to show the usage of the media type. > * 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. Yes, the format is the EAP packet, followed by the CoAP_Information elements described in Section 4. We will update the text as suggested. > * 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. Thank you, we will follow these suggestions. > 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. The "256-9999" range is ok for us. We will change the text to “IETF review”. Thank you. Best regards. > > Regards > Esko > > > -----Original Message----- > From: David Dong via RT <[email protected]> > Sent: Friday, January 12, 2024 02:10 > Cc: Esko Dijk <[email protected]>; [email protected]; > [email protected]; [email protected]; [email protected]; [email protected]; > [email protected] > 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://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap/__;!!D9dNQwwGXtA!X-2HqHkXNgi4f08VyivJJDBTCBQ2LDf3_mHRSZywqNh3FLf6SkB5RRDROAs1sw1qJ-PEFH7NcEG_EJgsmzrCHjtHZGuy$ > > 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://urldefense.com/v3/__https://www.iana.org/assignments/core-parameters/__;!!D9dNQwwGXtA!X-2HqHkXNgi4f08VyivJJDBTCBQ2LDf3_mHRSZywqNh3FLf6SkB5RRDROAs1sw1qJ-PEFH7NcEG_EJgsmzrCHihUlDpD$ > > With thanks, > > David Dong > IANA Services Sr. Specialist > _______________________________________________ > Ace mailing list > [email protected] > https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ace__;!!D9dNQwwGXtA!X-2HqHkXNgi4f08VyivJJDBTCBQ2LDf3_mHRSZywqNh3FLf6SkB5RRDROAs1sw1qJ-PEFH7NcEG_EJgsmzrCHvRavnve$ _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
