attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">All,<div class=""><br class=""></div><div class="">FYI... I will take care of supplying the updates they have requested...</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Amanda Baber via RT <<a href="mailto:iana-mime@iana.org" class="">iana-mime@iana.org</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[IANA #955632] Request for media type text/strings</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">April 13, 2017 at 12:59:03 PM EDT<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:msweet@apple.com" class="">msweet@apple.com</a><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Reply-To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:iana-mime@iana.org" class="">iana-mime@iana.org</a><br class=""></span></div><br class=""><div class=""><div class="">Hi Michael,<br class=""><br class="">The designated experts have returned a review for this request (see inline comments below). Your other request is still in their queue. I'll send them a reminder now.<br class=""><br class="">Please send a revised security considerations section with your reply.<br class=""><br class="">Best regards,<br class=""><br class="">Amanda Baber<br class="">Lead IANA Services Specialist<br class=""><br class="">===<br class=""><br class=""><blockquote type="cite" class="">Name: Michael Sweet<br class="">Email: <a href="mailto:msweet@apple.com" class="">msweet@apple.com</a><br class=""></blockquote><br class=""><blockquote type="cite" class="">Media type name: text<br class="">Media subtype name: strings<br class=""></blockquote><br class="">This name is acceptable, although I have to at least suggest that a more<br class="">specific name, e.g., application/printer-message-catalog might be<br class="">something to consider. (My personal preference would be the leave the name<br class="">alone, but as reviewer I am obligated to make the suggestion.)<br class=""><br class="">The fact that this essentially a registration of Apple's .strings<br class="">file format, the more general name is OK, but does place a bit more<br class="">of a requirement on the registration to cover all the issues.<br class=""><br class=""><blockquote type="cite" class="">Required parameters: NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Optional parameters:<br class="">NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Encoding considerations: 8bit<br class=""></blockquote><br class=""><blockquote type="cite" class="">UTF-8 encoded Unicode text.<br class=""></blockquote><br class=""><blockquote type="cite" class="">Security considerations:<br class=""></blockquote><br class=""><blockquote type="cite" class="">Localized strings may be arbitrarily large and could potentially cause a<br class="">denial-of-service.<br class=""></blockquote><br class=""><blockquote type="cite" class="">Localized strings may contain printf-style format characters that could cause<br class="">a program to display unintended information or crash.<br class=""></blockquote><br class="">This is useful information but not sufficient. All media types must:<br class=""><br class="">(1) State whether or not the media type contains active or executable<br class=""> content. If the media type does contain executable content explain<br class=""> what measures have been taken to insure that it can be executed<br class=""> safely, e.g. a sandbox, safe operation set, signed content, etc.<br class=""><br class="">(2) State whether or not the information contained in the media type<br class=""> needs privacy or integrity services.<br class=""><br class="">(3) If the answer to (2) is yes, elaborate on any privacy or integrity<br class=""> services the media type itself provides, or if it doesn't provide such<br class=""> services, explain how they should be provided externally, e.g., through<br class=""> the use of SSL/TLS.<br class=""><br class="">The answer to (1) is pretty clearly "no", but that needs to be stated. As for<br class="">(2) and (3), the format clearly doesn't provide integrity or privacy<br class="">protections. I don't think privacy is an issue - and you should say that if<br class="">it's true - but integrity clearly is, so there needs to be something about how<br class="">this kind of protection is achieved in the wild.<br class=""><br class=""><blockquote type="cite" class="">Interoperability considerations:<br class="">NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Published specification:<br class=""><a href="http://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf" class="">http://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf</a><br class=""></blockquote><br class="">Is the candidate URL going to change to something else at some point?<br class=""><br class=""><blockquote type="cite" class="">Applications which use this media:<br class="">All Cocoa, NeXTStep, and OpenStep applications<br class="">CUPS<br class="">IPP Everywhere<br class=""></blockquote><br class=""><blockquote type="cite" class="">Fragment identifier considerations:<br class="">NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Restrictions on usage:<br class="">NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Provisional registration? (standards tree only):<br class="">NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">Additional information:<br class=""></blockquote><br class=""><blockquote type="cite" class="">1. Deprecated alias names for this type: NONE<br class="">2. Magic number(s): NONE<br class="">3. File extension(s): NONE<br class="">4. Macintosh file type code: NONE<br class="">5. Object Identifiers: NONE<br class=""></blockquote><br class=""><blockquote type="cite" class="">General Comments:<br class=""></blockquote><br class=""><br class=""><blockquote type="cite" class="">Person to contact for further information:<br class=""></blockquote><br class=""><blockquote type="cite" class="">1. Name: ISTO-PWG Internet Printing Protocol Workgroup<br class="">2. Email: <a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class=""></blockquote><br class=""><blockquote type="cite" class="">Intended usage: Common<br class="">Used for providing localizations of English keywords and numeric values.<br class=""></blockquote><br class=""><br class=""><blockquote type="cite" class="">Author/Change controller: The Printer Working Group<br class="">c/o The IEEE Industry Standards and Technology Organization<br class="">445 Hoes Lane<br class="">Piscataway, NJ 08854<br class="">USA<br class=""></blockquote><br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></body></html>