Hi Renzo, Thanks again for your review and the interesting follow-ups on the issue tracker. We should have addressed all but one of your points in the newly published -08. Focusing on the outstanding comment: On Fri, 18 Apr 2025 at 18:08, Renzo Navas via Datatracker <noreply@xxxxxxxx> wrote: > Section 3.3, How do we determine if a parameter’s value is valid ? (given an > existing media type parameter)? (We have to track the values on the “Reference” > column on the Media Type register? E.g., for “cose;cose-type=”, I could not > find it on IANA https://www.iana.org/assignments/media-types/application/cose , > but have to read RFC9052). OK after reading the document, all these cases > (invalid or unknown stuff) will need an “Expert Review” . SUGGESTION: maybe put > a small disclaimer at the beginning of the section? For example: "Unknown or > Invalid values will be detected by a Expert Review". §3.3 illustrates the difficulty in discerning whether a parameter is acceptable, which may require digging into some RFC, or worse. IANA personnel's job description doesn’t include that - I think - which justifies moving to Expert Review. What constitutes an "invalid request" is decided by IANA and/or the DE. They will inform the requester if their request was accepted and actively engage with them to find an acceptable solution if the original request can't go through. Note that the DEs have a whole back office team at their disposal, the "core-parameters mailing list" [1]. cheers! Thomas & Esko [1] https://mailarchive.ietf.org/arch/browse/core-parameters/ -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
