attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE>@font-face {
        font-family: AGaramond;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: AGaramond
}
LI.MsoNormal {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: AGaramond
}
DIV.MsoNormal {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: AGaramond
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
P.MsoAutoSig {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoAutoSig {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoAutoSig {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
SPAN.EmailStyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003>Gail,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>I
suspect that the reason that the IPPFAX spec says that the Receiver MUST support
"media-ready" was because the spec says that the IPPFAX Sender SHOULD query the
"media-ready" Printer attribute. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>I also
think that the mind set of IPPFAX had been a single Device, so that the fan-out
to multiple devices wasn't even a consideration in being difficult to reflect
the "media-ready" value(s) correctly. For example, the statement in the
Introduction:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=425180720-30052003><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">"The
target market for an IPPFAX receiver is a midrange imaging device that can
support the minimum memory requirements that are required by the data format
PDF/is, but the image format is structured in such a way that the Receiver is
not required to include a disk or other permanent
storage."</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>On the
other hand, the definition of Receiver is:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>
<P class=MsoNormal style="MARGIN: 0in 0in 12pt"><FONT
face="Times New Roman"><FONT color=#000000><FONT size=3><B><SPAN
class=425180720-30052003>"</SPAN>Receiver</B><SPAN
style="mso-spacerun: yes"> </SPAN>The Printer object that accepts IPPFAX
protocol operations and receives the Document sent by the Sender.<SPAN
style="mso-spacerun: yes"> </SPAN>A Receiver offers the IPPFAX Print
Service (by definition).<SPAN
class=425180720-30052003>"</SPAN></FONT></FONT></FONT></P></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>So the
real question is:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>OK
that the IPPFAX Sender not bother with querying "media-ready", but should send
the IPPFAX PDF/is document whether the media is ready or not?
</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>If the
Sender doesn't query "media-ready", then the IPPFAX protocol is an
Electronic Document Transfer Protocol, i.e., get the bits from the Sender to the
Receiver, rather than get the Quality Document Successfully Printed onto Paper
Service. The mind set of the WG does shift from one paradigm to the other
from time to time (and from place to place within the IPPFAX Protocol spec
itself).</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=425180720-30052003>As
another example of this vacilation between defining a Device Protocol versus an
Electronic Document Exchange Service, is the idea that the IPPGET notification
is going to indicate whether the paper got printed OK. To me that means we
are talking about getting the document successfully transferred to paper.
Therefore, with that mind set, having the Sender query the "media-ready" makes a
lot of sense if the Sending User cares about knowing for certain that the
document was correctly imaged onto paper.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=425180720-30052003>Tom</SPAN></FONT></DIV><FONT face=Arial
color=#0000ff><SPAN class=425180720-30052003></SPAN></FONT><FONT face=Tahoma>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT size=2><SPAN class=425180720-30052003> </SPAN>-----Original
Message-----<BR><B>From:</B> Gail Songer
[mailto:gail.songer@peerless.com]<BR><B>Sent:</B> Friday, May 30, 2003
06:32<BR><B>To:</B> ifx@pwg.org<BR><B>Subject:</B> IFX>
Media-Ready<BR><BR></DIV></FONT></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">At Wednesday’s telecom, we
discovered that Media-Ready was Required in one spot and optional in
another. Ira was of the opinion that it should be
PROHIBIED.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does anyone else have opinion (or
remember why it was “Required”?)</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoAutoSig><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Gail Songer</SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Peerless Systems Corp</SPAN></FONT></P>
<P class=MsoAutoSig><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">gsonger@peerless.com</SPAN></FONT></P>
<P class=MsoNormal><FONT face=AGaramond size=2><SPAN
style="FONT-SIZE: 10pt"></SPAN></FONT> </P></DIV></BLOCKQUOTE></BODY></HTML>