[media-types] Re: [IANA #1418198] application/vnd.an gel.evidence-package registration request
"Murray S. Kucherawy" <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <CAL0qLwZjMmX0AX0J2hCaZRux1Yf6tH0v3cBwusgwWakOeRQyxg@mail.gmail.com> |
On Tue, Jun 10, 2025 at 2:51 PM Murray S. Kucherawy <[email protected]> wrote: > 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 > I guess on review, my problem is that I see these two things as being in conflict. It's weird that the bullet says "IETF specifications" (a precise definition), but then the paragraph below it calls out this exception, rather than just including "non-IETF streams with IESG approval" as its own bullet. So this: (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; > ...becomes less opinionated: (1) Invoke the previous 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]