<!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 your reply.<br>
</p>
<p>First let me apologize for a typo in the registration request.
The URL of the spec. was incorrect. A corrected registration
template is attached. Other changes to this version are:<br>
</p>
<ul>
<li>Added URL of the main Khronos Group web site under "Change
Controller."</li>
<li>Added the name of an application that uses (reads) this file
format.</li>
<li>Added additional info. to Security Considerations.</li>
<li>Fixed some typos.</li>
</ul>
See below for other comments.<br>
<br>
On 27/08/2010 05:27, Ned Freed wrote:
<blockquote id="mid_01NR578A6WVI000CVY_mauve_mrochek_com"
cite="mid:01NR578A6WVI000CVY@mauve.mrochek.com" type="cite">...<br>
<pre wrap="">As for your actual registration:
...</pre>
<pre wrap="">
Given that this is a standards tree registration, the IESG is going to ask if
this comes from a recognized standards body. It sounds to me like The Khronos
Group qualifies, but this will be for the IESG to determine.
</pre>
</blockquote>
I could find no information on the IANA web site that provides a
definitive definition of "recognized" in this context. However I
believe Khronos should qualify as it is a widely supported industry
consortium with responsibility for several well known standards.<br>
<blockquote id="mid_01NR578A6WVI000CVY_mauve_mrochek_com"
cite="mid:01NR578A6WVI000CVY@mauve.mrochek.com" type="cite">...
<blockquote id="StationeryCiteGenerated_21" type="cite">
<pre wrap="">The ktx type is a binary data stream which contains no executable code that
could disrupt a client processor. There is no provision in the type
specification that would allow authors to insert executable code that would
present any security risk to a client machine.
</pre>
</blockquote>
<pre wrap="">
IMO these security considerations are nowhere near sufficient for a standards
tree type. At an absolute minimum you need to add a discussion of possible
integrity/confidentiality concerns: Does data of this type require such
protection, and if it does, does the type provide it internally (and if so,
how) or must it be provided externally (and again, how)?
</pre>
</blockquote>
It is not clear to me exactly what you are asking for. I looked at
Security Considerations (Section 8.5) in the image/png registration
(<a href="http://tools.ietf.org/html/rfc2083">RFC 2083</a>) and
could see nothing along the lines you seem to be suggesting. Since
this is an image format, naturally any image could be sent including
images which one may wish to keep confidential. There is no
encryption in the format so users wishing to keep their images
confidential should overlay their own encryption. Is this the kind
of discussion you are requesting?<br>
<blockquote id="mid_01NR578A6WVI000CVY_mauve_mrochek_com"
cite="mid:01NR578A6WVI000CVY@mauve.mrochek.com" type="cite">...
<blockquote id="StationeryCiteGenerated_25" type="cite">
<pre wrap="">The KTX file format specification can be found at
</pre>
</blockquote>
<blockquote id="StationeryCiteGenerated_26" type="cite">
<pre wrap=""> <a class="moz-txt-link-freetext" href="http://www.khronos.org/opengles/sdk/sdk/tools/KTX">http://www.khronos.org/opengles/sdk/sdk/tools/KTX</a>.
</pre>
</blockquote>
<blockquote id="StationeryCiteGenerated_27" type="cite">
<pre wrap="">This is a temporary location. The spec. will be announced next week 7/28
and the permanent location will settled then.
</pre>
</blockquote>
<pre wrap="">
A stable specification location is very important for types in the standards
tree. This will need to be updated once a permanent location is decided on.
</pre>
</blockquote>
It is stable. The specification was ratified and a permanent home
created during the more than a month that has passed since I wrote
the above for my initial message to ietf-types. The permanent home
is<br>
<blockquote><a class="moz-txt-link-freetext" href="http://www.khronos.org/opengles/sdk/tools/KTX/file_format_spec/">http://www.khronos.org/opengles/sdk/tools/KTX/file_format_spec/</a><br>
</blockquote>
as noted in the revised registration that I have attached.<br>
<br>
Regards<br>
<br>
-Mark<br>
</body>
</html>