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

"Murray S. Kucherawy" <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <CAL0qLwbHPhKJL5tA=T0XjGpLU=0gKi0NutXdLy88gCgkFEagtA@mail.gmail.com>
On Thu, May 22, 2025 at 12:02 PM Amanda Baber via RT <
[email protected]> wrote:

> "I'm still getting my head around the I-D process -- I'm currently
> submitting the draft for the independent stream (which seemed to make sense
> to me as I have no affiliation with any larger organisation that might have
> some power to influence!). If the media type can be assigned to the
> standards tree based on this, as far as I am concerned this is the best
> option, after all Eden and I designed the format to be as useful as
> possible for a wider audience! I wonder, if this is the case, something
> like application/evidence-package might be more suitable (i.e. also
> dropping the "angel." which is the name of the suite of tools containing an
> implementation of the format)."


> They also asked for information about how to submit the I-D for inclusion
> in the IETF stream. Should they be directed to a particular working group?
>
> In the past, a few standards-tree media type registrations were made via
> independent stream RFCs. Nevil, I think, coordinated the separate IESG
> approval process (for the type itself) with us around the time of the
> conflict review. It's been several years since we've seen one of those,
> though.


As I read RFC 6838 Section 3.1, the independent stream is not eligible for
publishing standards tree media type registrations, as IETF consensus is
required but that's not something developed as part of the independent
stream.  I don't know how Nevil did it before.  We'd have to publish this
in the IETF stream, which means (a) a working group, or (b) Area Director
sponsorship.  You could try asking for (b) but that is at the discretion of
the Area Directors, who then become responsible for demonstrating that
consensus exists to proceed.

The other alternative is to make the claim that the applicant is a
legitimate SDO, and then pursue the second route described in that same
section of RFC 6838.

I don't have a working group to suggest.  My best recommendation would be
to make the case to DISPATCH that this is work that should be supported by
the IETF and see what they recommend.

The path of least resistance is a registration on the vendor tree, once we
have an actual specification to look at.  An independent stream publication
would meet this requirement.

-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.