Also odd would be to have two IPP implmentations on TCP/IP - HTTP and direct
TCP/IP.
In retrospect the correct thing to have done was to produce a mapping of
TIP/SI onto HTTP. Ie. HTTP is just another transport layer.
> -----Original Message-----
> From: Gordon, Charles [SMTP:CGordon@wal.osicom.com]
> Sent: Friday, April 03, 1998 1:57 PM
> To: 'don@lexmark.com'; rturner@sharplabs.com
> Cc: Rdebry@Us.Ibm.Com; Ipp@pwg.org
> Subject: RE: IPP> Host to device
>
> Given that IPP is the Internet Printing Protocol, do we really need to
> support anything else besides TCP/IP? Is the IPP working group even
> mandated to worry about non TCP/IP environments?
>
> --- Charles
>
> > -----Original Message-----
> > From: don@lexmark.com [SMTP:don@lexmark.com]
> > Sent: Friday, April 03, 1998 4:22 PM
> > To: rturner@sharplabs.com
> > Cc: Rdebry@Us.Ibm.Com; Ipp@pwg.org
> > Subject: RE: IPP> Host to device
> >
> >
> > Randy:
> >
> > My biggest concern is that your proposal is TCP/IP only. Is does not
> > solve
> > the problem for printers connected to servers via:
> >
> > - Parallel
> > - Serial
> > - USB
> > - 1394
> > - IPX/SPX
> > - AppleTalk
> > - DLC/LLC
> > - etc., etc., etc.
> >
> > If I'm going to use TCP/IP then I might as well go ahead with the HTTP
> > based implementation. You don't provide more status and control or
> > anything else that really buys me anything other than a slightly
> > lighter
> > transport. It's just not work the trouble for the return on
> > investment.
> >
> > Don
> >
> > **********************************************
> > * Don Wright don@lexmark.com *
> > * Product Manager, Strategic Alliances *
> > * Lexmark International *
> > * 740 New Circle Rd *
> > * Lexington, Ky 40550 *
> > * 606-232-4808 (phone) 606-232-6740 (fax) *
> > **********************************************
> >