IPP Mail Archive: Re: IPP> RE^4: IPP over TCP

Re: IPP> RE^4: IPP over TCP

Alex Bochannek (abochann@cisco.com)
Wed, 11 Dec 96 22:17:17 PST

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Peter_Zehler@wb.xerox.com: "IPP> RE: Printer Instance Creation/Installation"
Previous message: Hiroyuki Sato: "IPP> RE^4: IPP over TCP"
Maybe in reply to: Hiroyuki Sato: "IPP> RE^4: IPP over TCP"

> Internet Printing requires client sides bundle a print command with some
> attributes, e.g. copy count, finishing, etc. and issue the data package,
> also requires server sides receive/analyze the data and respond it.
>
> TCP offers only bi-directional bit stream. So we need a protocol on TCP
> to handle the sequence anyway. Salutation picks ONC/RPC as this
> mechanism, defining calls, Open, Close and DataTransfer. DataTransfer
> carries BER-encoded print commands, attributes and print data.

I agree. This protocol you describe is called IPP.

> If there are many choices, it confuses end users and manufacturers.
> Ya, we need only a one protocol spec.

That is arguable and hopefully can be discussed tomorrow.

> Today's BOF sounds exciting. I miss the one.

Too bad that you'll miss it, but I am sure someone will post notes.

Alex.

Next message: Peter_Zehler@wb.xerox.com: "IPP> RE: Printer Instance Creation/Installation"
Previous message: Hiroyuki Sato: "IPP> RE^4: IPP over TCP"
Maybe in reply to: Hiroyuki Sato: "IPP> RE^4: IPP over TCP"