[media-types] Re: [IANA #1453872] application/vnd.ju pyter registration request

"Murray S. Kucherawy" <[email protected]> Mon, 20 Jul 2026 17:45:47 +0200
Newsgroups gmane.ietf.types
Message-ID <CAL0qLwYk+oaK7icA9Z8SYpY-b+KVAeLVfN66bi819BHtAWg3wg@mail.gmail.com>
--===============6653150917468185183==
Content-Type: multipart/alternative; boundary="00000000000091ab5506570ccdc6"

--00000000000091ab5506570ccdc6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 16, 2026 at 6:26=E2=80=AFAM Amanda Baber via RT <
[email protected]> wrote:

> Hi Murray,
>
> > > > I am not involved directly in the project, although I know who the
> > > > current project lead is, I am not willing to say that it is ok to p=
ut
> > > > them down as direct contact for this.
> > >
> >
> > Could we ask that person?
> >
> >
> > > > The reason I want this registered, is that I am writing an RFC wher=
e
> I
> > > > want to reference this specific mime type, and I noticed that it wa=
s
> > > > possible to register mime types without direct involvement in the
> > > > project.
> > >
> >
> > The RFC could do the registration instead, if you like, but you'll face
> the
> > same question there if the contact offered is a URI rather than a singl=
e
> > contact address.
> >
> >
> > > > But if it doesn't work in this specific case, as they do not publis=
h
> > > > email addresses for direct contact that I could find despite
> > > > considerable effort to find one, maybe the registration request nee=
ds
> > > > to fail?
> > >
> >
> > Amanda, what would IANA do here, or what guidance should we provide?
> Given
> > a slate of people, would you try to contact all of them?  Pick one at
> > random?  Pick the first one?  What if you get multiple answers that don=
't
> > agree?  I'm inclined to say it should be a single email address, but
> maybe
> > there are other precedents here we should observe.
>
> This is unusual, and I don't know that we've run into it. For the contact=
,
> at least, we really want an email address, whether it's for a person or a
> role ("Example Administrator, [email protected]") or a group of people.
> Their address will be obscured slightly in the registry (@ symbol
> automatically replaced with an ampersand), if that's a concern.
>
> If this were to state that any single member of that group could verify a
> change to the registration, that could work, although it's not ideal.
>

I'm inclined to say this needs to be a single email address then (and is it
too late to make sure 6838bis says so?) rather than a URI from which you're
expected to select the right thing and hope you guessed correctly.

-MSK

--00000000000091ab5506570ccdc6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><span style=3D"background-color:transpare=
nt">On Thu, Jul 16, 2026 at 6:26=E2=80=AFAM Amanda Baber via RT &lt;<a href=
=3D"mailto:[email protected]">[email protected]</a>&gt; w=
rote:</span></div><div class=3D"gmail_quote gmail_quote_container"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">Hi Murray,<br>
<br>
&gt; &gt; &gt; I am not involved directly in the project, although I know w=
ho the<br>
&gt; &gt; &gt; current project lead is, I am not willing to say that it is =
ok to put<br>
&gt; &gt; &gt; them down as direct contact for this.<br>
&gt; &gt;<br>
&gt; <br>
&gt; Could we ask that person?<br>
&gt; <br>
&gt; <br>
&gt; &gt; &gt; The reason I want this registered, is that I am writing an R=
FC where I<br>
&gt; &gt; &gt; want to reference this specific mime type, and I noticed tha=
t it was<br>
&gt; &gt; &gt; possible to register mime types without direct involvement i=
n the<br>
&gt; &gt; &gt; project.<br>
&gt; &gt;<br>
&gt; <br>
&gt; The RFC could do the registration instead, if you like, but you&#39;ll=
 face the<br>
&gt; same question there if the contact offered is a URI rather than a sing=
le<br>
&gt; contact address.<br>
&gt; <br>
&gt; <br>
&gt; &gt; &gt; But if it doesn&#39;t work in this specific case, as they do=
 not publish<br>
&gt; &gt; &gt; email addresses for direct contact that I could find despite=
<br>
&gt; &gt; &gt; considerable effort to find one, maybe the registration requ=
est needs<br>
&gt; &gt; &gt; to fail?<br>
&gt; &gt;<br>
&gt; <br>
&gt; Amanda, what would IANA do here, or what guidance should we provide?=
=C2=A0 Given<br>
&gt; a slate of people, would you try to contact all of them?=C2=A0 Pick on=
e at<br>
&gt; random?=C2=A0 Pick the first one?=C2=A0 What if you get multiple answe=
rs that don&#39;t<br>
&gt; agree?=C2=A0 I&#39;m inclined to say it should be a single email addre=
ss, but maybe<br>
&gt; there are other precedents here we should observe.<br>
<br>
This is unusual, and I don&#39;t know that we&#39;ve run into it. For the c=
ontact, at least, we really want an email address, whether it&#39;s for a p=
erson or a role (&quot;Example Administrator, <a href=3D"mailto:admin@examp=
le.com" target=3D"_blank">[email protected]</a>&quot;) or a group of people=
. Their address will be obscured slightly in the registry (@ symbol automat=
ically replaced with an ampersand), if that&#39;s a concern. <br>
<br>
If this were to state that any single member of that group could verify a c=
hange to the registration, that could work, although it&#39;s not ideal.<br=
></blockquote><div><br></div><div>I&#39;m inclined to say this needs to be =
a single email address then (and is it too late to make sure 6838bis says s=
o?) rather than a URI from which you&#39;re expected to select the right th=
ing and hope you guessed correctly.</div><div><br></div><div>-MSK=C2=A0</di=
v></div></div>

--00000000000091ab5506570ccdc6--


--===============6653150917468185183==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWVkaWEtdHlw
ZXMgbWFpbGluZyBsaXN0IC0tIG1lZGlhLXR5cGVzQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNl
bmQgYW4gZW1haWwgdG8gbWVkaWEtdHlwZXMtbGVhdmVAaWV0Zi5vcmcK

--===============6653150917468185183==--