TA Triumph-Adler CX 8036 - Manual (Page 257)

1
Connectivity - Appendix D
KIP IPS - Technical Detail
Version 1.1
Introduction
The following document contains technical detail and description related to the
networkability of KIP printers, functionality of KIP printers in various network
typologies, and concepts relating to client-server printing architecture. This
document is intended for an audience familiar with core networking fundamentals
and concepts, and an understanding of general network typologies and practices.
KIP Printers are considered to be hardware network-connected devices in the
sense that participation within a given network typology requires a physical RJ-45
type connection in order to communicate with other network devices such as
computer workstations, dedicated-servers, switching equipment, hubs, bridges,
office printers, routers, and a variety of other network capable hardware.
KIP Printers are TCP/IP devices. TCP/IP is short for Transmission Control
Protocol / Internet Protocol. TCP/IP is a widely adopted networking protocol
standard that is common place in many environments requiring network capable
equipment, and network connectivity to company intranets, the larger internet, e-
mail, wireless communications, shared printing devices, IP-telephony, and many
other applications
Many other networking protocols exist at the same OSI level as TCP/IP (.e.
IPX/SPX AppleTalk, NetBEUI) and at lower levels of the OSI model (BGP, RIP,
OSPF, IGRP / EIGRP). TCP/IP can be traced to it’s origin in 1969 to a research
project funded by the United States Defense Advanced Research Projects
Agency (DARPA). In 1983 TCP/IP was adopted as a standard by the DARPA as
the primary vehicle for network connected devices, or hosts, and was considered
a requirement for connected device implementation. Many companies have now
built corporate TCP/IP networks that have grown to a point at which it could
almost be considered a mainstream consumer technology.
TCP/IP has several different fundamental concepts and inner working that are
well beyond the scope of this document. An excellent resource of TCP/IP study
can be found at
http://www.faqs.org/rfcs/rfc1180.html .