[media-types] [IANA #1418198] application/vnd.angel. evidence-package registration request

Hi Murray,

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

On Mon Jun 02 23:58:20 2025, [email protected] wrote:
> 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.

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.

The registrations I've been able to locate were made in cooperation with Ned, who did give them preliminary reviews. I mentioned Nevil in this context because I don't know whether subsequent ISEs have been in favor of publishing documents solely to register standards-tree media types, since I'm not sure anyone else has used this process. 

One example is application/pkcs8-encrypted, from RFC 8351. Looking at our correspondence related to that registration request, which was sent to the IESG for the same telechat as the conflict review, for that type, Ned wrote, "fine from a tecnical perspective, but I note that the issue Barry raised last time of who is the change controller and contact (which are both currently Sean) for a standards tree type remains. Not that my opinion is relevant, but I see no major problem with having it point to Sean." Sean also registered types via the independent submission RFC 7903. 

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

thanks,
Amanda

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