attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
@font-face
{font-family:"Andale Mono";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:16.0pt;
font-family:"Calibri Light","sans-serif";
color:#2E74B5;
font-weight:normal;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri Light","sans-serif";
color:#2E74B5;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Making printer-xxx-date-time & printer-current-time REQUIRED for consistency across the 3 primary specifications will be fine as long as devices that do not
have a notion of calendar time can provide “no-value” as RFC 2911 allows for “printer-current-time” (and attributes whose value is derived from that). But, that is effectively making it STRONGLY RECOMMENDED, in principle, isn’t it?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Personally, I feel that making something REQUIRED typically sets an expectation on the validity/accuracy of the data that the attribute provides although there
is no explicit claim/requirement on the validity/accuracy made in the underlying specification.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks and Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Somasundaram.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Michael Sweet [mailto:msweet@apple.com]
<br>
<b>Sent:</b> Wednesday, May 21, 2014 8:54 PM<br>
<b>To:</b> Soma Meiyappan<br>
<b>Cc:</b> Ira McDonald; Peter Zehler; IPP@pwg.org<br>
<b>Subject:</b> Re: [IPP] WG Last Call of IPP Scan Service specification<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Soma,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This is indeed something that needs to be documented in the implementor's guide, but in most cases the client just needs to see whether the date/time (or simply the up time in seconds) is different than last reported, and not if the change
is newer.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But given that the printer-xxx-change-date-time attributes are required in IPP Everywhere, I think we still want them required for IPP Scan.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On May 20, 2014, at 11:09 PM, Soma Meiyappan <<a href="mailto:Soma.Meiyappan@conexant.com">Soma.Meiyappan@conexant.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Ira,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you very much for the summary from the F2F discussions on this topic.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My question on the topic for FaxOut stems from the imaginable ways an IPP client may have been written to be dependent on printer-config-change-date-time for
caching printer confifuation and if it is a value that may be treated as trusted enough for that purpose. I am aware that ‘no-value’ is valid for these attributes (incl printer-current-time); but I am concerned about other valid (but inaccurate) dateTime
values and the implications.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If ‘printer-config-change-date-time’ is used purely for informational purposes (as a value to display in a report or a web-page and not necessarily in caching
the printer configuration), I’ll not be too concerned. However, could it be used to determine if cached information about the printer needs to be refreshed? If yes, we may want to add a note targeted at IPP client writers, in the implementer’s guide, that
this information MUST not be used for caching printer capabilities without other precautions including protection against the possibility of the printer reported time being inaccurate [RFC 2911 does not place any accuracy requirements] and printer-current-time
(and derived attribute values) going back to the past for a number of reasons. </span>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Looking forward to hearing the forum’s thoughts on the topic.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks and Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Somasundaram.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Ira McDonald [</span><a href="mailto:blueroofmusic@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">mailto:blueroofmusic@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">]
<br>
<b>Sent:</b> Monday, May 19, 2014 11:23 PM<br>
<b>To:</b> Soma Meiyappan; Ira McDonald; Peter Zehler<br>
<b>Cc:</b> </span><a href="mailto:IPP@pwg.org"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">IPP@pwg.org</span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><br>
<b>Subject:</b> Re: [IPP] WG Last Call of IPP Scan Service specification</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Soma,<br>
<br>
Thanks for your careful reading of these IPP specs.<o:p></o:p></p>
</div>
<p class="MsoNormal">We discussed this comment during the Thursday IPP WG session
<o:p></o:p></p>
</div>
<p class="MsoNormal">at the PWG F2F meeting last week, when looking at IPP Scan with<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Pete Zehler.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">The IPP F2F minutes state that this issue should be resolved on the
<br>
IPP mailing list, but there was unanimous consensus in the meeting:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">(1) IPP FaxOut - these date-time attributes should remain REQUIRED<o:p></o:p></p>
</div>
<p class="MsoNormal">(because they satisfy regulatory requirements for a Fax service).<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
(2) IPP Scan - these date-time attributes should be changed to either<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">RECOMMENDED (i.e., best practice) or simply OPTIONAL.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Please note that in IPP Everywhere (PWG 5100.14), the attributes<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">printer-config-change-date-time and printer-state-change-date-time<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">attributes are REQUIRED in Table 6 for conformance (see notes 2<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and 3 below the table).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Obviously, the underlying printer-date-time attribute should have<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">the same conformance level as the change-xxx attributes in IPP
<br>
Everywhere, IPP FaxOut, and IPP Scan. This appears to me to<br>
be an oversight in these specs.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Please comment further on this thread, to clarify your thoughts.<o:p></o:p></p>
</div>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">- Ira (co-chair of IPP WG)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Ira McDonald (Musician / Software Architect)<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music / High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333FF">http://sites.google.com/site/blueroofmusic</span></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></a><br>
mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Tue, May 13, 2014 at 10:34 PM, Soma Meiyappan <<a href="mailto:Soma.Meiyappan@conexant.com" target="_blank">Soma.Meiyappan@conexant.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Hi Pete et al,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">I have a concern about</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">printer-config-change-date-time </span><o:p></o:p></p>
<p><span style="font-size:11.0pt">printer-state-change-date-time </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">These attributes figure in the REQUIRED table in section 4.3. The above attributes require the scan device to have a notion of wall clock time (whether
it is accurate or not to the global wall clock time). To increase the chances of making use of that effectively & correctly, all clients would be required to use this somehow in reference to printer-current-time and not to the wall-clock time that the client
might know through other sources. That makes me wonder if it is sufficient to have printer-state-change-time and printer-config-change-time as required and make xxxx-date-time as optional.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">I have a similar question on FaxOut; but at least on FaxOut, the devices are expected to have a notion of wall-clock time although the point about how
clients should use that information with reference to printer-current-time still seems applicable.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Somasundaram.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b>
<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a> [mailto:<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>]
<b>On Behalf Of </b>Zehler, Peter<br>
<b>Sent:</b> Friday, May 09, 2014 10:35 PM<br>
<b>To:</b> <a href="mailto:IPP@pwg.org" target="_blank">IPP@pwg.org</a><br>
<b>Subject:</b> [IPP] WG Last Call of IPP Scan Service specification<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">All,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This message initiates the IPP Working Group last call of the IPP Scan Service<span style="color:#1F497D">
</span>specification updated per prototype experience and subsequent discussions.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140509.pdf" target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140509.pdf</a> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140509.pdf" target="_blank">http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippscan10-20140509.pdf</a><span style="color:#1F497D">
</span> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Please send all feedback to the IPP mailing list (reply-all works fine for this) and it will be collected and processed as quickly as possible.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Our intent is to move IPP Scan Service<span style="color:#1F497D">
</span>to PWG Formal Vote before the August 2014 F2F.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Impact","sans-serif";color:navy">Peter Zehler</span><span style="color:#1F497D"><br>
<br>
</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy">Xerox Research Center Webster<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Email:
</span><a href="mailto:Peter.Zehler@Xerox.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Peter.Zehler@Xerox.com</span></a><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Voice:
</span><a href="tel:%28585%29%20265-8755" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(585) 265-8755</span></a><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX:
</span><a href="tel:%28585%29%20265-7441" target="_blank"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">(585) 265-7441</span></a><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">US Mail: Peter Zehler</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Xerox Corp.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">M/S 128-25E</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Webster NY, 14580-9701</span><span style="color:#1F497D">
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Andale Mono","serif";color:black">_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>