<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<style type="text/css">
<!--
body {
font-family: "sans-serif";
font-weight: normal;
color: #555555;
margin: 1.25cm;
max-width: 50em;
counter-reset: chapter;
text-align: justify;
}
h1 {
color: #00A6A6;
}
h1.title {
text-align: center;
}
h2, h3, h4, h5, h6 {
color: #146A68;
}
a {
text-decoration: none;
}
/* The following a: pseudo-class order is necessary in
* order to be effective.
*/
a:link {
color: #009999;
}
a:visited {
color: #006699;
}
a:hover {
color: #00CCCC;
}
a:active {
color: #0000FF;
}
code.code {
white-space: nowrap;
}
div.footnote {
font-size: small;
}
div.legalnotice {
font-size: x-small;
}
table {
border-collapse: separate;
border-spacing: 0;
border-style: ridge;
}
caption {
background-color: #146A68;
color: #FFFF33;
}
td {
padding: 0.3em;
}
th {
padding: 0.3em;
/* background-color: #FFDEAD; */
background-color: #EBD8AF;
}
th:first-child {
/* background-color: #EFEFEF; */
background-color: #EBE57B;
}
.informalexample {
background-color: #F7F9F9;
border: thin dashed #146A68;
}
.footnote {
font-size: x-small;
border-top: thin solid #146A68;
border-right: thin none #146A68;
border-bottom: thin none #146A68;
border-left: thin none #146A68;
}
code {
font-family: "Courier New", Courier, mono;
white-space: pre;
}
-->
</style>
</head>
<body>
<p>Hi Ned,<br>
</p>
<p>Thank you for the useful information buried in the unnecessary
lecture.<br>
</p>
<p>I am well aware that IANA != IESG. I began my search there
because they have documents and instructions related to MIME type
registration. I did search more widely without result.<br>
</p>
<p>I was not looking for a license to not follow current rules,
merely an explanation of your request related to security and a
major image file format seemed like a good place to start.<br>
</p>
<p>I read RFC4288 as I was preparing the registration template but I
did not fully understand the import of the *fifth* bullet in
Section 4.6. I will revise the section on security then submit my
registration to the IESG.<br>
</p>
<p>Regards</p>
<blockquote>
<p>-Mark</p>
</blockquote>
<br>
<br>
<br>
<br>
On 07/09/2010 09:24, Ned Freed wrote:
<blockquote id="mid_01NRKUEAP0LE000CVY_mauve_mrochek_com"
cite="mid:01NRKUEAP0LE000CVY@mauve.mrochek.com" type="cite">
<blockquote id="StationeryCiteGenerated_36" type="cite">
<pre wrap="">I could find no information on the IANA web site that provides a
definitive definition of "recognized" in this context.
</pre>
</blockquote>
<pre wrap="">
Um, exactly what part of "the IESG makes the determination" did you fail to
understand? IANA != IESG. It would be frankly astonishing if the rules for how
the IESG determines standards body status could be found on the IANA site.
Having served on the IESG in the past, I also doubt very much the IESG has
bothered to create formalized rules for what consistitutes a recognized
standards body - maybe they should, but I doubt they have. So IMO it's also
pretty unlikely you'll find such rules on the IESG's site either, but at least
you'd be looking in the right place...
</pre>
<blockquote id="StationeryCiteGenerated_37" type="cite">
<pre wrap="">However I believe
Khronos should qualify as it is a widely supported industry consortium
with responsibility for several well known standards.
</pre>
</blockquote>
<pre wrap="">
That's my reading as well, but again, this is up to the IESG to determine.
</pre>
....</blockquote>
</body>
</html>