[media-types] Re: [IANA #1418198] application/vnd.an gel.evidence-package registration request

"Murray S. Kucherawy" <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <CAL0qLwYOA836DjghcyVbHoDR2fMWb9nJMZvYPy0xnHsfDt-=pA@mail.gmail.com>
On Tue, Jun 3, 2025 at 7:06 PM Amanda Baber via RT <
[email protected]> wrote:

> The standards tree media type registration we made through RFCs were in
> accordance with instructions from Ned Freed. More info inline:
>
> [...]

This is the text from RFC 6838, Section 3.1:
>
> Registrations published in non-IETF RFC streams are also allowed and
>    require IESG approval.  A registration can be either in a stand-alone
>    "registration only" RFC or incorporated into a more general
>    specification of some sort.
>

Also from 3.1 (Standards Tree registrations), above what you cited:

   1.  in the case of registrations associated with IETF specifications,
       approved directly by the IESG, or

Far as I'm aware, an ISE document is not an "IETF specification", which
disqualifies ISE documents from this path.  I think they even say in their
boilerplate that this is not a product of the IETF, or something close to
that.  So this path doesn't apply even if the IESG approves it.  Thus, I
think what was done previously involving Ned and Nevil was probably the
closest thing possible to the "right" thing, but I don't see a path in 6838
that actually allows this.  We can ask the IESG for an opinion if you
like.  (I'll probably do that separately anyway.)

So now it's a question of whether we follow that same improper process
again here (and probably make sure IANABIS fixes it in their chartered
work) on the basis of precedent, or force it through the correct process.

Would you recommend that the submitters pursue standards tree registration
> through the ISE?
>

I think our choices at this point are:

(1) Attempt to invoke the previous (but as far as I can tell, improper)
process to get it onto the standards tree by just having the IESG approve
it either as a direct submission to the reviewers or an ISE publication;

(2) Shop for an AD willing to sponsor it onto the IETF stream; or

(3) Present it in DISPATCH and see if they have any other suggestions, like
taking it on directly or chartering a WG to do it.

-MSK

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.