IPP>PRO - posted white paper and foils

IPP>PRO - posted white paper and foils

IPP>PRO - posted white paper and foils

Alex Bochannek abochann at cisco.com
Wed Jan 29 10:13:03 EST 1997


Seems like some people have missed this:


> Obviously, I would prefer another mapping like so:
> 
> 6. Mapping to TCP socket.
> 
> To use a TCP connection to transport IPP messages a new port number
> has to be defined. The suggested number to be registered with the IANA
> is NNN. When using this method, an IPP server opens the socket in
> LISTEN mode and a client connects to it with an unused source port in
> the unrestricted range. This socket pair is the unique identifier for
> the connection. Once the connection reaches ESTABLISHED state, it
> transports at least one complete IPP message exchange. One complete
> IPP message exchange is defined by one Request-Message followed by one
> Response-Message. A multi-segment print message is treated as one
> request.  After the exchange the TCP connection can be disconnected by
> the server but should stay up to support further transactions. An idle
> timer of NN minutes must be used to terminate the connection if the
> option of keeping it up is used.



--
Alex Bochannek                 Phone & Fax : +1 408 526 51 91
Senior Network Analyst         Pager       : +1 408 485 90 92
Engineering Services           Alpha Pager : (800) 225-0256 PIN 104536
Cisco Systems, Inc.            Email       : abochannek at cisco.com
170 West Tasman Drive, Bldg. E Pager Email : abochannek at beeper.cisco.com
San Jose, CA 95134-1706, USA




More information about the Ipp mailing list