
From nobody Fri Feb 13 09:52:28 2015
Return-Path: <dev+ietf@seantek.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914571A0161 for <media-types@ietfa.amsl.com>; Fri, 13 Feb 2015 09:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6lSZtkN_c3Al for <media-types@ietfa.amsl.com>; Fri, 13 Feb 2015 09:52:22 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1C021A0046 for <media-types@ietf.org>; Fri, 13 Feb 2015 09:52:22 -0800 (PST)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 86FF422E263 for <media-types@ietf.org>; Fri, 13 Feb 2015 12:52:18 -0500 (EST)
Message-ID: <54DE39B1.8000104@seantek.com>
Date: Fri, 13 Feb 2015 09:51:45 -0800
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: media-types@ietf.org
References: <20141230000544.65052.qmail@ary.lan>
In-Reply-To: <20141230000544.65052.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/PjnjoWA7u3v95IUxAtD_DSqedgA>
Subject: Re: [media-types] Going to register - Internet media type application/pkcs12; request review
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2015 17:52:25 -0000

Hello media-types:

Just following up on this thread. I intend to register=20
application/pkcs12 next week unless there are further revisions.

Best regards,

Sean

************
Registration Template [DRAFT prefinal]

Type name: application

Subtype name: pkcs12

Required parameters: N/A

Optional parameters: N/A

Encoding considerations: binary

Security considerations:
PKCS #12 data typically contains one or more private keys encrypted with =

a password using a key derivation function. Poor password choices, weak=20
algorithms, or improper parameter selections (e.g., insufficient salting =

rounds) will make the confidential payloads much easier to compromise.=20
Additionally, PFX was subject to criticism for being too obtuse and=20
cumbersome to implement (see Gutmann, P., PFX - How Not to Design a=20
Crypto Protocol/Standard,=20
<https://www.cs.auckland.ac.nz/~pgut001/pubs/pfx.html>). Many of these=20
(editorial) shortcomings have been addressed in the latest publications=20
of PKCS #12.

Interoperability considerations:
PKCS #12 (formerly PFX, Personal Information Exchange) is a widely=20
recognized format for exchange of secret (personal identity) information =

on all modern cryptographic stacks. The format is primarily used for the =

exchange of private keys and certificates, but can also be used to=20
exchange symmetric keys, miscellaneous secrets, attributed objects, and=20
extensions.

Published specification:
PKCS #12 v1.0, June 1999; PKCS #12 v1.1 (RFC 7292), July 2014

Applications that use this media type:

Machines, applications, browsers, Internet kiosks, and so on, that=20
support this standard allow a user to import, export, and exercise a=20
single set of personal identity information.


Fragment identifier considerations: N/A

Additional information:

  Deprecated alias names for this type: N/A
  Magic number(s): None.
  File extension(s): .p12, .pfx
  Macintosh file type code(s): N/A

Person & email address to contact for further information:
  Sean Leonard <dev+ietf@seantek.com>

Intended usage: COMMON

Restrictions on usage: None.

Author:
RSA, EMC, IETF

Change controller: The IESG

Provisional registration? (standards tree only): No


From nobody Tue Feb 17 20:50:14 2015
Return-Path: <mike@w3.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5691A9110 for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 20:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.512
X-Spam-Level: 
X-Spam-Status: No, score=-5.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvrFD2PaWStD for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 20:50:10 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA85E1A9101 for <media-types@ietf.org>; Tue, 17 Feb 2015 20:50:10 -0800 (PST)
Received: from mike by jay.w3.org with local (Exim 4.72) (envelope-from <mike@w3.org>) id 1YNwaP-0006o6-Cl; Tue, 17 Feb 2015 23:50:09 -0500
Date: Wed, 18 Feb 2015 13:50:09 +0900
From: "Michael[tm] Smith" <mike@w3.org>
To: media-types@ietf.org
Message-ID: <20150218045009.GU28032@jay.w3.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="OelmujB7rQAg+yu0"
Content-Disposition: inline
User-Agent: Mutt/1.5.23+34 (compatible; MSIE 6.0; Windows 98)
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/hGqtItfITpIKz97rSskP3XEbZc8>
Subject: [media-types] View pending media-type applications?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 04:50:12 -0000

--OelmujB7rQAg+yu0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Is there still no public Web=E2=80=90based interface to view details of med=
ia=E2=80=90type
applications that have been submitted via http://www.iana.org/form/media-ty=
pes
but not approved yet?

  =E3=83=BCMike

--=20
Michael[tm] Smith https://people.w3.org/mike

--OelmujB7rQAg+yu0
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJU5BoBAAoJEIfRdHe8OkuVsFoP/1ISfGCReuJN/3AbOsNO9nYR
B2JKoMS7c7mJxFAgivgMIeA7yvBAUgjye8bRu3SeB7t/0v4au+IhAhtIVSdnfuYD
Pg+bDBBX2AqyJBxqTXQC0KoPSNsaLN3D155kkEIEL6XgM8bmVWzzJDhpjTm7mH7Y
qTEGTvIG8Xqn54ZeF2wgqCL61IquOms/Lsufz87VXqFu4eMju5GM43EupfzfxXaS
4fYi1DWaI3BMwuxz8uBHQw2OYpQCnWm/h0HbW7giF7+qmXjjjHgiwzSXSkwglvO5
vYDmqB6E0V032t3JPth2X0o2w1TiihTMvNQDZsdZc3tp4GCVZzESAu4qOkUh5wVY
HtCsZkDoR1j8qf9gk7QBReYmsmUwjMIsvjCgAZBeT64FBOIs/3/79mZkVqanSDdl
Y5R4ySbuE4n0iwt9oq0lTaQA2fljbSB3FNVh9tRScZzvXkW9wRjX4/u1dtFjBqOM
eABhkoROJ5/l3lycVZc7KYw4fCWop8l0lmVEiFK9yi1Qp3aMU9HZVxZY+xJrOMdL
yJhpZXZdpRyTAXZhlDnIpBeOZZf+xnMoZ1ZGdC61Yo2PYLI9xFN0BWf70OBNYAI1
NJFhV0xTt7coFVv1H3xPVTgwL3cOvQfp7pRTaRnxsouUjnJV18IREULrPocQn+4p
yTS5BIjU8kSrOJ9oMWl+
=bTlD
-----END PGP SIGNATURE-----

--OelmujB7rQAg+yu0--


From nobody Tue Feb 17 22:36:17 2015
Return-Path: <ned.freed@mrochek.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFBB01A8713 for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 22:36:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.113
X-Spam-Level: 
X-Spam-Status: No, score=-0.113 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAVIP969uhph for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 22:36:11 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 70F4E1A6FF6 for <media-types@ietf.org>; Tue, 17 Feb 2015 22:36:11 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIN6GROQ7K0055R6@mauve.mrochek.com> for media-types@ietf.org; Tue, 17 Feb 2015 22:31:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1424241070; bh=sNWSZ3FtI2Kk04rd8NiPusEpAKsytUcAFW9Rd9tT1UA=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=BZMZPiY9cJu5OljPnGbLCKExtRNfxpocb62Wngu5mA55e+iQf2XUhbLJBDF7b3wiS NK3Ay0ejFkZYdXZ471bvKpndm+An/6Jl2DiYQ3C9pFoTQ7y0nOwp/fOYIs/7HfCFIM Uj0ikdOFbWFeUYoOwqNIv0tEqmNSOxQKwSCBGMpk=
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=utf-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIDH7P70SW0000AQ@mauve.mrochek.com>; Tue, 17 Feb 2015 22:31:06 -0800 (PST)
Message-id: <01PIN6GQ6S4W0000AQ@mauve.mrochek.com>
Date: Tue, 17 Feb 2015 22:20:22 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 18 Feb 2015 13:50:09 +0900" <20150218045009.GU28032@jay.w3.org>
References: <20150218045009.GU28032@jay.w3.org>
To: "Michael[tm] Smith" <mike@w3.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/VwQUpEOwWyrZSiXO6nirX1U4io0>
Cc: media-types@ietf.org
Subject: Re: [media-types] View pending media-type applications?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 06:36:16 -0000

> Is there still no public Web‐based interface to view details of media‐type
> applications that have been submitted via http://www.iana.org/form/media-types
> but not approved yet?

No, and there's no "still" about it - AFAIK there is no plan to offer such  a
thing, and I would object if there were. The goal is always to get things
registered, and exposing initial attempts, warts and all, to public scrutiny
doesn't seem like a good way to further that goal.

There is a provisional registry to expose the names of in-progress standards
tree registrations, but not the details. That's available here:

    http://www.iana.org/assignments/provisional-standard-media-types/provisional-standard-media-types.xhtml

I note in passing that the review queue is presently empty. So there are no
media types waiting for IANA action, if that's what you're interesting in
finding out.

				Ned


From nobody Tue Feb 17 22:59:20 2015
Return-Path: <mike@w3.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B887A1A871B for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 22:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level: 
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Asijwg02emDR for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 22:59:17 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FF2C1A8713 for <media-types@ietf.org>; Tue, 17 Feb 2015 22:59:17 -0800 (PST)
Received: from mike by jay.w3.org with local (Exim 4.72) (envelope-from <mike@w3.org>) id 1YNybL-0007AB-RU; Wed, 18 Feb 2015 01:59:15 -0500
Date: Wed, 18 Feb 2015 15:59:15 +0900
From: "Michael[tm] Smith" <mike@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Message-ID: <20150218065915.GW28032@jay.w3.org>
References: <20150218045009.GU28032@jay.w3.org> <01PIN6GQ6S4W0000AQ@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qRqofxetdBO9L27H"
Content-Disposition: inline
In-Reply-To: <01PIN6GQ6S4W0000AQ@mauve.mrochek.com>
User-Agent: Mutt/1.5.23+34 (compatible; MSIE 6.0; Windows 98)
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/9Bn5i6FURS-oV1QGKt7th36Lfxs>
Cc: media-types@ietf.org
Subject: Re: [media-types] View pending media-type applications?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 06:59:19 -0000

--qRqofxetdBO9L27H
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Ned,

Ned Freed <ned.freed@mrochek.com>, 2015-02-17 22:20 -0800:
> Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/VwQUpEOwWy=
rZSiXO6nirX1U4io0>
>=20
> > Is there still no public Web-based interface to view details of media-t=
ype
> > applications that have been submitted via http://www.iana.org/form/medi=
a-types
> > but not approved yet?
>=20
> No, and there's no "still" about it - AFAIK there is no plan to offer suc=
h  a
> thing, and I would object if there were. The goal is always to get things
> registered, and exposing initial attempts, warts and all, to public scrut=
iny
> doesn't seem like a good way to further that goal.

That seems like a reasonable position to take, though I can't say I
personally agree with it. Is there some consensus about that position
documented somewhere (and the rationale)?

IMHO the goal of getting things registered isn't hindered much by having
greater transparency and more opportunities for wider review and scrutiny.

But also IMHO it is actually probably hindered some by the fact that
submitters don't have any means to check themselves on the status of their
applications, or to point others at the pending application so they examine
the details, or to confirm that somebody else hasn't already submitted an
application for the same media type that's still pending, etc.

> There is a provisional registry to expose the names of in-progress standa=
rds
> tree registrations, but not the details. That's available here:
>=20
>     http://www.iana.org/assignments/provisional-standard-media-types/prov=
isional-standard-media-types.xhtml

Thanks for the heads-up about that. That would be an improvement, I think.

Is there a discussion archived somewhere about how the decision was arrived
at to only expose the names but not the details?

> I note in passing that the review queue is presently empty. So there are =
no
> media types waiting for IANA action, if that's what you're interesting in
> finding out.

I was actually specifically interested in finding out the details for an
application for the `application/vnd.citationstyles.style+xml` media type,
which per https://github.com/validator/validator/issues/30#issuecomment-740=
62123
I believe were submitted a few days ago.

  =E3=83=BCMike

--=20
Michael[tm] Smith https://people.w3.org/mike

--qRqofxetdBO9L27H
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJU5DhDAAoJEIfRdHe8OkuVejMP/20OH4lS0SKIZXIjxXgJnnkZ
GpGtyrdX7bGXsBofXIDZCJsjFwp3EpiUDq6ByRJUgrXqtZ98+iwf2Fs+eZYeNY3w
OgaT7RUdzHlUAluKA0O3g+9mSd1e+YhcTexcmtdxcut+NO+R4kaMY5bu+0w/lOwJ
LD3Pml+++LLjQI1SSiLVwdiIL4tHjb2ashJeZtnLMiBMgrPHANpjFk3hjZfy5/7b
Btf8O2yGBgBZJEMUD+S4prhLwAUqzJ1zJ1+O94lGREz4H+EYs68XXSS/3I5+SVr0
YHDdReeJaDM17UKj98eoJ9xGjI/l5f7HwvHc607o4lOS820VaM8SlgYIjus67l+F
4c8Ny4kYED7vZNVcN5W2bLDsgwt83vjOUr/Auj1nMt095YcWVXSZjxldX9xb3hmF
/ehe/v3xSucDDup/g1p6W32UfQ7EhSaiuuwUraQmG4PFHjfkXGaJegMMR8cgnXco
j8RLqoQ37rCTmwhQa0I8v6Un7DrZ+RDb77/dzf+An/zPRJ8KvLF4JWqV8ThCHf4p
X3RUoV3KHPnJuvIyicDO8R/gO1nmpO3ypSw/QAnp9zoBHJZ4AulvmcrcSDhNaY9P
koZ31FbbacbZYeQjFcSwOtIr9X0msBsIwlYilYmdXlkEVRnM+x21Iit3zj3Q9ylb
KiVpE93AyJexCIgSbc/v
=LQCc
-----END PGP SIGNATURE-----

--qRqofxetdBO9L27H--


From nobody Tue Feb 17 23:36:53 2015
Return-Path: <ned.freed@mrochek.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC0A1A9105 for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 23:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level: 
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05ohnlqMXat5 for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 23:36:50 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id D02C11A8743 for <media-types@ietf.org>; Tue, 17 Feb 2015 23:36:50 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIN8KYNXJ4004YWG@mauve.mrochek.com> for media-types@ietf.org; Tue, 17 Feb 2015 23:31:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1424244709; bh=JjG8si02bs5o2YkHtJi8jYdNALOQgnKSmltv4IBjgRQ=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=SxBl9DQeFjvbq75qYTwamy0nA9mQHQRFsicjkfFcHC/lPIOllnMIo70MbMCcY+q2u NE9NNaBToarPeG/To/bebvB4HKsP1t1v/hOgHxjyfWF9Icu4MLX6oHsGMvzl1Qzrhp C4SRb+CrblQARvAYTCRnazDZJAq0B8Nmo38B5JoA=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PIDH7P70SW0000AQ@mauve.mrochek.com>; Tue, 17 Feb 2015 23:31:45 -0800 (PST)
Message-id: <01PIN8KWJXHW0000AQ@mauve.mrochek.com>
Date: Tue, 17 Feb 2015 23:04:49 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 18 Feb 2015 15:59:15 +0900" <20150218065915.GW28032@jay.w3.org>
References: <20150218045009.GU28032@jay.w3.org> <01PIN6GQ6S4W0000AQ@mauve.mrochek.com> <20150218065915.GW28032@jay.w3.org>
To: "Michael[tm] Smith" <mike@w3.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/w1sWHeTG8sFEt3aPi9ollwX5QcA>
Cc: media-types@ietf.org, Ned Freed <ned.freed@mrochek.com>
Subject: Re: [media-types] View pending media-type applications?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 07:36:52 -0000

> Hi Ned,

> Ned Freed <ned.freed@mrochek.com>, 2015-02-17 22:20 -0800:
> > Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/VwQUpEOwWyrZSiXO6nirX1U4io0>
> >
> > > Is there still no public Web-based interface to view details of media-type
> > > applications that have been submitted via http://www.iana.org/form/media-types
> > > but not approved yet?
> >
> > No, and there's no "still" about it - AFAIK there is no plan to offer such  a
> > thing, and I would object if there were. The goal is always to get things
> > registered, and exposing initial attempts, warts and all, to public scrutiny
> > doesn't seem like a good way to further that goal.

> That seems like a reasonable position to take, though I can't say I
> personally agree with it. Is there some consensus about that position
> documented somewhere (and the rationale)?

Well, I can't say for sure that the issue of making such material public was
never suggested - there have been thousands of messages on many different
lists, many F2F meetings, lunch discussions, phone calls, and who knows what
else over the past 20 years or so. But I'm pretty sure there was never any
concrete proposal made to do it. And it should be obvious that documenting
decisions on proposals that nobody made is an absurdity.

> IMHO the goal of getting things registered isn't hindered much by having
> greater transparency and more opportunities for wider review and scrutiny.

Actually, there is evidence that says it does. When the process was originally
designed public review was required for all registrations. And registration
rates were low to nonexistent. Things improved considerably once the
requirement was removed.

> But also IMHO it is actually probably hindered some by the fact that
> submitters don't have any means to check themselves on the status of their
> applications, or to point others at the pending application so they examine
> the details, or to confirm that somebody else hasn't already submitted an
> application for the same media type that's still pending, etc.

Checking on the status of your own submissions is another matter entirely. I
think that would be a fine thing, but that's a matter for IANA, as it would
have to be integrated into their ticket system.

> > There is a provisional registry to expose the names of in-progress standards
> > tree registrations, but not the details. That's available here:
> >
> >     http://www.iana.org/assignments/provisional-standard-media-types/provisional-standard-media-types.xhtml

> Thanks for the heads-up about that. That would be an improvement, I think.

> Is there a discussion archived somewhere about how the decision was arrived
> at to only expose the names but not the details?

What is now RFC 6838 was discussed at length on the apps area list back in
2012. I have no idea if that particular issue ever came up though.

> > I note in passing that the review queue is presently empty. So there are no
> > media types waiting for IANA action, if that's what you're interesting in
> > finding out.

> I was actually specifically interested in finding out the details for an
> application for the `application/vnd.citationstyles.style+xml` media type,
> which per https://github.com/validator/validator/issues/30#issuecomment-74062123
> I believe were submitted a few days ago.

The review request was sent to me yesterday and completed the same day. That's
all I can say.

				Ned


From nobody Tue Feb 17 23:51:40 2015
Return-Path: <mike@w3.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D2BE1A9105 for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 23:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level: 
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWb9xWdN3QaN for <media-types@ietfa.amsl.com>; Tue, 17 Feb 2015 23:51:35 -0800 (PST)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE7E61A874B for <media-types@ietf.org>; Tue, 17 Feb 2015 23:51:35 -0800 (PST)
Received: from mike by jay.w3.org with local (Exim 4.72) (envelope-from <mike@w3.org>) id 1YNzPy-00027w-BZ; Wed, 18 Feb 2015 02:51:34 -0500
Date: Wed, 18 Feb 2015 16:51:34 +0900
From: "Michael[tm] Smith" <mike@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Message-ID: <20150218075134.GX28032@jay.w3.org>
References: <20150218045009.GU28032@jay.w3.org> <01PIN6GQ6S4W0000AQ@mauve.mrochek.com> <20150218065915.GW28032@jay.w3.org> <01PIN8KWJXHW0000AQ@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7uidztUHYC105IRM"
Content-Disposition: inline
In-Reply-To: <01PIN8KWJXHW0000AQ@mauve.mrochek.com>
User-Agent: Mutt/1.5.23+34 (compatible; MSIE 6.0; Windows 98)
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/wdqGbZkN_6ckyZPozHpOfwgW5pw>
Cc: media-types@ietf.org
Subject: Re: [media-types] View pending media-type applications?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 07:51:38 -0000

--7uidztUHYC105IRM
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Ned,

Ned Freed <ned.freed@mrochek.com>, 2015-02-17 23:04 -0800:
> Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/w1sWHeTG8s=
FEt3aPi9ollwX5QcA>
> > Ned Freed <ned.freed@mrochek.com>, 2015-02-17 22:20 -0800:
> > > Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/VwQUpE=
OwWyrZSiXO6nirX1U4io0>
> > >
> > > > Is there still no public Web-based interface to view details of med=
ia-type
> > > > applications that have been submitted via http://www.iana.org/form/=
media-types
> > > > but not approved yet?
> > >
> > > No, and there's no "still" about it - AFAIK there is no plan to offer=
 such  a
> > > thing, and I would object if there were. The goal is always to get th=
ings
> > > registered, and exposing initial attempts, warts and all, to public s=
crutiny
> > > doesn't seem like a good way to further that goal.
>=20
> > That seems like a reasonable position to take, though I can't say I
> > personally agree with it. Is there some consensus about that position
> > documented somewhere (and the rationale)?
>=20
> Well, I can't say for sure that the issue of making such material public =
was
> never suggested - there have been thousands of messages on many different
> lists, many F2F meetings, lunch discussions, phone calls, and who knows w=
hat
> else over the past 20 years or so. But I'm pretty sure there was never any
> concrete proposal made to do it. And it should be obvious that documenting
> decisions on proposals that nobody made is an absurdity.

Fair enough. I don't personally feel strongly enough about it being a real
problem that I care to take time to write a proposal for changing anything.

> > IMHO the goal of getting things registered isn't hindered much by having
> > greater transparency and more opportunities for wider review and scruti=
ny.
>=20
> Actually, there is evidence that says it does. When the process was origi=
nally
> designed public review was required for all registrations.

Understood but I wasn't suggesting to have a requirement for public review
of pending applications. I was just suggesting to have the information be
made publicly available, with no new requirements on submitters themselves.

> And registration rates were low to nonexistent. Things improved
> considerably once the requirement was removed.

OK but another data point I can provide to counter that is that as somebody
who has actually taken time to submit applications in the past, I personally
found the current process to pretty unfriendly and I found the lack of
ability to check on the status of my own applications to be a disincentive.
But I suppose others might see it differently.

> > But also IMHO it is actually probably hindered some by the fact that
> > submitters don't have any means to check themselves on the status of th=
eir
> > applications, or to point others at the pending application so they exa=
mine
> > the details, or to confirm that somebody else hasn't already submitted =
an
> > application for the same media type that's still pending, etc.
>=20
> Checking on the status of your own submissions is another matter entirely=
=2E I
> think that would be a fine thing, but that's a matter for IANA, as it wou=
ld
> have to be integrated into their ticket system.

OK. Well I think that'd be an improvement at least. I don't feel strongly
enough about it to be commit to writing a proposal and taking through the
rounds on my own, but if it it's just a logistical change that can be
deployed without needing an RFC or something to be created, I'd otherwise
be happy to put time into helping make it happen.

> > > There is a provisional registry to expose the names of in-progress st=
andards
> > > tree registrations, but not the details. That's available here:
> > >
> > >     http://www.iana.org/assignments/provisional-standard-media-types/=
provisional-standard-media-types.xhtml
>=20
> > Thanks for the heads-up about that. That would be an improvement, I thi=
nk.
>=20
> > Is there a discussion archived somewhere about how the decision was arr=
ived
> > at to only expose the names but not the details?
>=20
> What is now RFC 6838 was discussed at length on the apps area list back in
> 2012. I have no idea if that particular issue ever came up though.
>=20
> > > I note in passing that the review queue is presently empty. So there =
are no
> > > media types waiting for IANA action, if that's what you're interestin=
g in
> > > finding out.
>=20
> > I was actually specifically interested in finding out the details for an
> > application for the `application/vnd.citationstyles.style+xml` media ty=
pe,
> > which per https://github.com/validator/validator/issues/30#issuecomment=
-74062123
> > I believe were submitted a few days ago.
>=20
> The review request was sent to me yesterday and completed the same day. T=
hat's
> all I can say.

OK, that's good to know at least=E3=83=BCthanks

  =E3=83=BCMike

--=20
Michael[tm] Smith https://people.w3.org/mike

--7uidztUHYC105IRM
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCgAGBQJU5ESGAAoJEIfRdHe8OkuVw8gQAKGHTsQnn6aY4SjCouNNIWiw
IifQ0+Usqx5PZK1vZWhLWUWxn8CPDrOzFWiu9PlYywzAcCy6z6KjECikKDHGOyOs
jEAtQAv5WSenhrCF4em5QBKEG01QVfx7JwO2P+kqKvsYHRUNgQVOF5VbzeEh1D3d
49dkmZ8WE8nxLJQoMMSsxAOUYHgL8yLoC8LP6H5vx6nJSatLP+2ZB+cH7TpatAkq
pxIqTAMawBblqJ/J/yQ6X2Fzty37gVVfKFkN4Es+uTiljuapvSAoQbgq7K8fUiMt
ulKZgl74xCYhB/9scuRMEZGIPMO8apkhAIT5573O+PDwD1xTLt+jt7kf05Towfho
VWM20o9SDQkCPRH96COE7ZQqjeY5yK2dJGNQ5hqugh4EUCBIFZB7nrv24CTw4HSS
I1KTyQmiRt/W6Q34+Eg0jUaUcuL4rV1h/UoGk4ElFYZ9Ib7TrDGHzFphg9y8YDiZ
Nok3JljEznU5MVByyWemP3oQlNtgmvq3qFbBw7x7jhg0IDuMBSD38aUnUypNL0Fq
X6aREh8abhYLeff+ir9hzjV4y0w+WMc2Pe/5YVcMvp2GgqSUo88fOGPR529otP3b
t3wMFS6k4H/joP1wUHOwOrUd+F7IlMXudiauT6FkLU5Ut8exK7x2Z/G3dZonVmQH
eKYAHbiL+3mOGFkqsTKw
=AzXI
-----END PGP SIGNATURE-----

--7uidztUHYC105IRM--

