<!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>In my reply to your original message I wrote the following on
8/31.<br>
</p>
<blockquote type="cite">
<p>On 27/08/2010 05:27, Ned Freed wrote: </p>
<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>
<br>
I no clearer to understanding your request. Please answer my
question so I can proceed with the registration.<br>
<br>
Regards<br>
<br>
-Mark<br>
<br>
</body>
</html>