attachment-0001

<!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; } @font-face { font-family: Tahoma; } @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 } SPAN.EmailStyle19 { COLOR: navy; FONT-FAMILY: Arial } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV>Gail,</DIV> <DIV> </DIV> <DIV>Sounds like there is growing consensus to get rid of the "media-ready" Receiver attribute in IPPFAX and get rid of the RECOMMENDATION that the Sender query it.  This makes IPPFAX even simpler.</DIV> <DIV> </DIV> <DIV>Also with the choice media type, there is yet another reason for the Sender not to query the Receiver's "media-ready" attribute.  The Sender can assume that the choice a4 or letter is supported for IPPFAX and doesn't even have to query the Receiver's "media-supported" attribute.  </DIV> <DIV> </DIV> <DIV>Tom</DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Gail Songer [mailto:gail.songer@peerless.com] Sent: Thursday, June 05, 2003 08:12 To: Hastings, Tom N Cc: ifx@pwg.org Subject: RE: IFX> Media-Ready [and is IPPFAX a Device Protocol or an Electronic Document Exchange Protocol?] </DIV> <DIV class=Section1> Hi Tom,   I’ve been mulling this topic and I believe that media-ready was required because we were going to require the client to format the job based on the size of the paper that could be printed (sender makes right).   However, now that we allow scaling and that we are focusing repositories, maybe this requirement can be lifted.   <DIV> Gail Songer Peerless Systems Corp gsonger@peerless.com</DIV>   -----Original Message----- From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com] Sent: Friday, May 30, 2003 3:06 PM To: Gail Songer Cc: ifx@pwg.org Subject: RE: IFX> Media-Ready [and is IPPFAX a Device Protocol or an Electronic Document Exchange Protocol?]   <DIV> Gail,</DIV> <DIV>  </DIV> <DIV> 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.  </DIV> <DIV>  </DIV> <DIV> 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:</DIV> <DIV>  </DIV> <DIV> "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."</DIV> <DIV>  </DIV> <DIV> On the other hand, the definition of Receiver is:</DIV> <DIV>  </DIV> <DIV> "Receiver  The Printer object that accepts IPPFAX protocol operations and receives the Document sent by the Sender.  A Receiver offers the IPPFAX Print Service (by definition)."</DIV> <DIV>  </DIV> <DIV> So the real question is:</DIV> <DIV>  </DIV> <DIV> 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?  </DIV> <DIV>  </DIV> <DIV> 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).</DIV> <DIV>  </DIV> <DIV> 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.</DIV> <DIV>  </DIV> <DIV> Tom</DIV> <DIV>  </DIV> <DIV>  -----Original Message----- From: Gail Songer [mailto:gail.songer@peerless.com] Sent: Friday, May 30, 2003 06:32 To: ifx@pwg.org Subject: IFX> Media-Ready</DIV> <BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in"> 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.   Does anyone else have opinion (or remember why it was “Required”?)       Gail Songer Peerless Systems Corp gsonger@peerless.com  </BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>