rfc3998.Internet Printing Protocol (IPP) Job and Printer Administrative Operations

合集下载

计算机网络端口0-9090及作用

1tcpmux TCP Port Service Multiplexer传输控制协议端口服务多路开关选择器2compressnet Management Utility compressnet 管理实用程序3compressnet Compression Process压缩进程5rje Remote Job Entry远程作业登录7echo Echo回显9discard Discard丢弃11systat Active Users在线用户13daytime Daytime时间17qotd Quote of the Day每日引用18msp Message Send Protocol消息发送协议19chargen Character Generator字符发生器20ftp-data File Transfer[Default Data]文件传输协议(默认数据口)21ftp File Transfer[Control]文件传输协议(控制)22ssh SSH Remote Login Protocol SSH远程登录协议---SSH23telnet Telnet终端仿真协议---telnet24?any private mail system预留给个人用邮件系统25smtp Simple Mail Transfer简单邮件发送协议---smtp27nsw-fe NSW User System FE NSW 用户系统现场工程师29msg-icp MSG ICP MSG ICP31msg-auth MSG Authentication MSG验证33dsp Display Support Protocol显示支持协议35?any private printer server预留给个人打印机服务37time Time时间38rap Route Access Protocol路由访问协议---rap39rlp Resource Location Protocol资源定位协议41graphics Graphics图形42nameserver WINS Host Name Server WINS 主机名服务---wins43nicname Who Is"绰号" who is服务44mpm-flags MPM FLAGS Protocol MPM(消息处理模块)标志协议45mpm Message Processing Module [recv]消息处理模块46mpm-snd MPM [default send]消息处理模块(默认发送口)47ni-ftp NI FTP NI FTP48auditd Digital Audit Daemon数码音频后台服务49tacacs Login Host Protocol (TACACS)TACACS登录主机协议50re-mail-ck Remote Mail Checking Protocol远程邮件检查协议51la-maint IMP Logical Address Maintenance IMP(接口信息处理机)逻辑地址维护52xns-time XNS Time Protocol施乐网络服务系统时间协议53domain Domain Name Server域名服务器---dns54xns-ch XNS Clearinghouse施乐网络服务系统票据交换55isi-gl ISI Graphics Language ISI图形语言56xns-auth XNS Authentication施乐网络服务系统验证57?any private terminal access预留个人用终端访问58xns-mail XNS Mail施乐网络服务系统邮件59?any private file service预留个人文件服务60?Unassigned未定义61ni-mail NI MAIL NI邮件?62acas ACA Services异步通讯适配器服务63whois+ whois+WHOIS+64covia Communications Integrator (CI)通讯接口65tacacs-ds TACACS-Database Service TACACS数据库服务66sql*net Oracle SQL*NET Oracle SQL*NET67bootps Bootstrap Protocol Server引导程序协议服务端68bootpc Bootstrap Protocol Client引导程序协议客户端69tftp Trivial File Transfer小型文件传输协议70gopher Gopher信息检索协议71netrjs-1Remote Job Service远程作业服务72netrjs-2Remote Job Service远程作业服务73netrjs-3Remote Job Service远程作业服务74netrjs-4Remote Job Service远程作业服务75?any private dial out service预留给个人拨出服务76deos Distributed External Object Store 分布式外部对象存储77?any private RJE service预留给个人远程作业输入服务78vettcp vettcp修正TCP?79finger Finger查询远程主机在线用户等信息---finger 80http World Wide Web HTTP全球信息网超文本传输协议81hosts2-ns HOSTS2 Name Server HOST2名称服务82xfer XFER Utility传输实用程序83mit-ml-dev MIT ML Device模块化智能终端ML设备84ctf Common Trace Facility公用追踪设备85mit-ml-dev MIT ML Device模块化智能终端ML设备86mfcobol Micro Focus Cobol Micro Focus Cobol编程语言87?any private terminal link预留给个人终端连接88kerberos Kerberos Kerberros安全认证系统89su-mit-tg SU/MIT Telnet Gateway SU/MIT终端仿真网关90dnsix DNSIX Securit Attribute Token Map DNSIX 安全属性标记图91mit-dov MIT Dover Spooler MIT Dover假脱机92npp Network Printing Protocol网络打印协议93dcp Device Control Protocol设备控制协议94objcall Tivoli Object Dispatcher Tivoli对象调度95supdup SUPDUP96dixie DIXIE Protocol Specification DIXIE协议规范97ft-rvfft Remote Virtural File Protocol）快速远程虚拟文件协议98tacnews TAC News TAC新闻协议99metagram Metagram Relay100newacct[unauthorized use]101/tcp hostname NIC Host Name Server102/tcp iso-tsap ISO-TSAP Class 0103/tcp gppitnp Genesis Point-to-Point Trans Net104/tcp acr-nema ACR-NEMA Digital Imag. & Comm. 300105/tcp cso CCSO name server protocol105/tcp csnet-ns Mailbox Name Nameserver106/tcp 3com-tsmux 3COM-TSMUX107/tcp rtelnet Remote Telnet Service108/tcp snagas SNA Gateway Access Server109/tcp pop2 Post Office Protocol - Version 2110 pop3 默认端口111 端口：111 端口是SUN 公司的RPC（Remote Procedure Call，远程过程调用）服务所开放的端口，主要用于分布式系统中不同计算机的内部进程通信，RPC 在多种网络服务中都是很重要的组件112/tcp mcidas McIDAS Data Transmission Protocol113 端口：113 端口主要用于Windows 的“Authentication Service”（验证服务）114/tcp audionews Audio News Multicast115/tcp sftp Simple File Transfer Protocol116/tcp ansanotify ANSA REX Notify117/tcp uucp-path UUCP Path Service118/tcp sqlserv SQL Services119 端口：119 端口是为“Network News Transfer Protocol”（网络新闻组传输协议，简称NNTP）开放的120/tcp cfdptkt CFDPTKT121/tcp erpc Encore Expedited Remote Pro.Call122/tcp smakynet SMAKYNET123/tcp ntp Network Time Protocol124/tcp ansatrader ANSA REX Trader125/tcp locus-map Locus PC-Interface Net Map Ser126/tcp unitary Unisys Unitary Login127/tcp locus-con Locus PC-Interface Conn Server128/tcp gss-xlicen GSS X License Verification129/tcp pwdgen Password Generator Protocol130/tcp cisco-fna cisco FNATIVE131/tcp cisco-tna cisco TNATIVE132/tcp cisco-sys cisco SYSMAINT133/tcp statsrv Statistics Service134/tcp ingres-net INGRES-NET Service135 端口：135 端口主要用于使用RPC（Remote Procedure Call，远程过程调用）协议并提供DCOM （分布式组件对象模型）服务136/tcp profile PROFILE Naming System137 端口：137 端口主要用于“NetBIOS Name Service”（NetBIOS名称服务）138/tcp netbios-dgm NETBIOS Datagram Service139 端口：139 端口是为“NetBIOS Session Service”提供的，主要用于提供Windows 文件和打印机共享以及Unix 中的Samba 服务140/tcp emfis-data EMFIS Data Service141/tcp emfis-cntl EMFIS Control Service142/tcp bl-idm Britton-Lee IDM143 端口：143 端口主要是用于“Internet Message Access Protocol”v2（Internet 消息访问协议，简称IMAP）144/tcp uma Universal Management Architecture145/tcp uaac UAAC Protocol146/tcp iso-tp0 ISO-IP0161 端口：161 端口是用于“Simple Network Management Protocol”（简单网络管理协议，简称SNMP）443 端口：43 端口即网页浏览端口，主要是用于HTTPS 服务，是提供加密和通过安全端口传输的另一种HTTP554 端口：554 端口默认情况下用于“Real Time Streaming Protocol”（实时流协议，简称RTSP）1024 端口：1024 端口一般不固定分配给某个服务，在英文中的解释是“Reserved”（保留）1080 端口：1080 端口是Socks 代理服务使用的端口，大家平时上网使用的WWW 服务使用的是HTTP 协议的代理服务1433 端口：MS SQL*SERVER数据库server，默认的端口号为1433/tcp 1433/udp1434 端口：MS SQL*SERVER数据库monitor，默认的端口号为1434/tcp 1434/udp1755 端口：1755 端口默认情况下用于“Microsoft Media Server”（微软媒体服务器，简称MMS）3306 端口：mysql 的默认端口3389 端口：WIN2003远程登陆，默认的端口号为33894000 端口：4000 端口是用于大家经常使用的QQ 聊天工具的，再细说就是为QQ 客户端开放的端口，QQ 服务端使用的端口是8000。

IP RFC中文摘要材料

[RFC中文翻译]在串行线路上传输IP数据报的非标准协议TCP/IP协议组运行在各种各样的网络媒介上：IEEE802.3（以太网）和802.5（令牌环）局域网（LAN）、X.25线路、卫星链路以及串行线路。

其中许多网络已经有IP分组的标准封装格式，但没有用于串行线路的标准。

SLIP（串行线路IP）目前已成为事实上的标准，广泛地用于在点对点串行连接上运行TCP/IP。

这并不是一个Internet标准，本备忘录的发布不受限制。

历史（HISTORY）SLIP源于80年代初期的3COMUNETTCP/IP实现。

SLIP只是一个分组分帧协议，仅仅定义了一系列在串行线路上构造IP分组的字符。

它没有提供地址、分组类型标识、错误检查/修正或者压缩机制。

因为这个协议所作的工作这么少，通常很容易实现。

大约在1984年，RickAdam为4.2BerkeleyUnix和SunMicrosystem工作站实现了SLIP并公之于众，并作为一种使用串行线路连接TCP/IP主机和路由器的简单可靠的方法很快流行起来。

SLIP通常专门用于串行连接，有时候也用于拨号网络，使用的线路速率一般介于1200bps 和19.2Kbps之间。

SLIP允许主机和路由器混合连接（主机-主机、主机-路由器、路由器-路由器都是SLIP网络通用的配置），因而非常有用。

可用性（A V AILABILITY）SLIP可用于大多数基于BerkeleyUNIX的系统，并且被包括进了Berkeley的4.3BSD标准版。

SLIP可用于Ultrix、SunUNIX和大多数派生自Berkeley的UNIX系统。

一些终端集线器和IBMPC的实现也支持该协议。

BerkeleyUNIX的SLIP可以使用匿名FTP从上的pub/sl.shar.Z中获得。

确保传输的是二进制文件，并使用UNIX解压程序打开它，然后把解开的文件作为UNIX/bin/sh（如/bin/shsl.shar）的SHELL命令使用协议（PROTOCOL）SLIP定义了两个特殊字符：END和ESC。

使用CUPS打印管理器管理打印机

来源：/cd/E37934_01/html/E36604/preface-4.html#scrolltoc非常详细！！！使用CUPS 设置和管理打印机第 1 章概述本章介绍有关使用通用UNIX 打印系统(Common UNIX Printing System, CUPS) 管理打印环境的概要信息，其中包括如何转换到使用CUPS 管理打印机（如果以前使用LP 打印服务管理打印机）。

本章中介绍的界面包括CUPS 命令行实用程序、CUPS Web 浏览器界面以及CUPS 打印管理器（该打印管理器是可以在桌面中访问的GUI）。

CUPS 简介CUPS 是一种模块化开源打印系统，使用Internet 打印协议(Internet Printing Protocol, IPP) 作为基础来管理打印机、打印请求和打印队列。

CUPS 支持网络打印机浏览和基于PostScript 打印机描述的打印选项。

CUPS 还在本地网络中提供公用打印接口。

IPP 是网络打印的标准协议。

与其他基于IP 的协议类似，可以在本地或通过Internet 使用IPP 与远程打印机进行通信。

但与其他协议不同的是，IPP 还支持访问控制、验证和加密，从而使其成为比其他协议强大且安全许多的打印解决方案。

IPP 位于超文本传输协议(Hypertext Transfer Protocol, HTTP) 的顶层。

HTTP 是Internet 中的Web 服务器的基础协议。

使用IPP 时，您可以验证打印机或服务器的状态信息、管理打印机以及通过浏览器打印作业。

CUPS 是基于IPP/1.1 的完整打印系统，它提供基本的摘要本地证书验证，以及基于用户、域或IP 的访问控制。

CUPS 包括对动态打印机检测和分组的支持。

CUPS 会将lpr命令替换为自己的命令，将LPD 打印机驱动程序替换为自己的打印驱动程序。

CUPS 与LP 打印服务的相似之处在于，它也使用PostScript 格式作为其页面说明底层语言。

常用端口列表

79/TCP Finger协议官方80/TCP HTTP（超文本传输协议）- 用于传输网页官方81/TCP HTTP预备（超文本传输协议）官方81/TCP Torpark - Onion routing ORport非官方82/UDP Torpark - 控制端口非官方88/TCP Kerberos - 认证代理官方101/TCP主机名102/TCP ISO-TSAP 协议107/TCP远程Telnet协议109/TCP POP（Post Office Protocol），“邮局协议”，第2版110/TCP POP3（“邮局协议”，第3版）- 用于接收电子邮件官方111/TCP,UDP Sun协议官方官方113/TCP ident - old server identification system, 仍然被IRC 服务器用来认证它的用户115/TCP SFTP, 简单文件传输协议117/TCP UUCP-PATH118/TCP,UDP SQL 服务官方119/TCP NNTP (Network News Transfer Protocol) - 用来收取新闻组的消息官方123/UDP NTP (Network Time Protocol) - used for time synchronization官方135/TCP,UDP EPMAP (End Point Mapper) / Microsoft RPC Locator Service官方137/TCP,UDP NetBIOS NetBIOS Name Service官方138/TCP,UDP NetBIOS NetBIOS Datagram Service官方139/TCP,UDP NetBIOS NetBIOS Session Service官方官方143/TCP,UDP IMAP4 (Internet Message Access Protocol 4) - used for retrievingE-mails152/TCP,UDP BFTP, Background File Transfer Program153/TCP,UDP SGMP, Simple Gateway Monitoring Protocol156/TCP,UDP SQL Service官方158/TCP,UDP DMSP, Distributed Mail Service Protocol161/TCP,UDP SNMP (Simple Network Management Protocol)官方162/TCP,UDP SNMPTRAP官方170/TCP Print-srv179/TCP BGP (Border Gateway Protocol)官方194/TCP IRC (Internet Relay Chat)官方201/TCP,UDP AppleTalk Routing Maintenance209/TCP,UDP The Quick Mail Transfer Protocol213/TCP,UDP IPX官方218/TCP,UDP MPP, Message Posting Protocol220/TCP,UDP IMAP, Interactive Mail Access Protocol, version 3259/TCP,UDP ESRO, Efficient Short Remote Operations264/TCP,UDP BGMP，Border Gateway Multicast Protocol308/TCP Novastor Online Backup官方311/TCP Apple Server-Admin-Tool, Workgroup-Manager-Tool318/TCP,UDP TSP, Time Stamp Protocol323/TCP,UDP IMMP, Internet Message Mapping Protocol383/TCP,UDP HP OpenView HTTPs Operations Agent366/TCP,UDP SMTP, Simple Mail Transfer Protocol. ODMR, On-Demand Mail Relay369/TCP,UDP Rpc2portmap官方371/TCP,UDP ClearCase albd官方384/TCP,UDP A Remote Network Server System387/TCP,UDP AURP, AppleTalk Update-based Routing Protocol389/TCP,UDP LDAP (Lightweight Directory Access Protocol)官方401/TCP,UDP UPS Uninterruptible Power Supply官方411/TCP Direct Connect Hub port非官方412/TCP Direct Connect Client-To-Client port非官方427/TCP,UDP SLP (Service Location Protocol)官方443/TCP HTTPS - HTTP Protocol over TLS/SSL (encrypted transmission)官方444/TCP,UDP SNPP，Simple Network Paging Protocol官方445/TCP Microsoft-DS (Active Directory，Windows shares, Sasser worm，Agobot, Zobotworm)445/UDP Microsoft-DS SMB file sharing官方464/TCP,UDP Kerberos Change/Set password官方465/TCP Cisco protocol Official 465/TCP SMTP over SSL Unofficial 475/TCP tcpnethaspsrv (Hasp services, TCP/IP version)官方497/TCP dantz backup service官方500/TCP,UDP ISAKMP，IKE-Internet Key Exchange官方502/TCP,UDP Modbus，Protocol512/TCP exec, Remote Process Execution512/UDP comsat, together with biff：notifies users of new c.q. yet unreade-mail513/TCP Login513/UDP Who514/TCP rsh protocol - used to execute non-interactive commandlinecommands on a remote system and see the screen return514/UDP syslog protocol - used for system logging官方515/TCP Line Printer Daemon protocol - used in LPD printer servers517/UDP Talk518/UDP NTalk520/TCP efs520/UDP Routing - RIP官方513/UDP Router官方524/TCP,UDP NCP (NetWare Core Protocol) is used for a variety things such asaccess to primary NetWare server resources, Time Synchronization,525/UDP Timed, Timeserver530/TCP,UDP RPC官方531/TCP,UDP AOL Instant Messenger, IRC非官方532/TCP netnews533/UDP netwall, For Emergency Broadcasts540/TCP UUCP (Unix-to-Unix Copy Protocol)官方542/TCP,UDP commerce (Commerce Applications)官方543/TCP klogin, Kerberos login544/TCP kshell, Kerberos Remote shell546/TCP,UDP DHCPv6 client547/TCP,UDP DHCPv6 server548/TCP AFP（Apple Filing Protocol）550/UDP new-rwho, new-who554/TCP,UDP RTSP (Real Time Streaming Protocol)官方556/TCP Remotefs, rfs, rfs_server560/UDP rmonitor, Remote Monitor561/UDP monitor563/TCP,UDP NNTP protocol over TLS/SSL (NNTPS)官方587/TCP email message submission（SMTP） (RFC 2476)Official官方591/TCP FileMaker 6.0 (and later) Web Sharing (HTTP Alternate, see port80)官方593/TCP,UDP HTTP RPC Ep Map（RPC over HTTP, often used by DCOM services andMicrosoft Exchange Server）604/TCP TUNNEL631/TCP,UDP IPP，Internet Printing Protocol636/TCP,UDP LDAP over SSL (encrypted transmission, also known as LDAPS)官方639/TCP,UDP MSDP, Multicast Source Discovery Protocol646/TCP LDP, Label Distribution Protocol647/TCP DHCP Failover Protocol648/TCP RRP, Registry Registrar Protocol652/TCP DTCP, Dynamic Tunnel Configuration Protocol654/TCP AODV, Ad hoc On-Demand Distance Vector665/TCP sun-dr, Remote Dynamic Reconfiguration非官方666/UDP毁灭战士，电脑平台上的一系列第一人称射击游戏。

TCP和UP端口列表

TCP/UDP端口列表计算机之间依照互联网传输层TCP/IP协议不同的协定通信，都有不同的对应端口。

所以，利用短信（datagram）的UDP，所采用的端口号码不一定和采用TCP 的端口号码一样。

以下为两种通信协定的端口列表连结：目录[隐藏]▪ 1 端口状态颜色图例▪ 2 0到1023号端口▪ 3 1024到49151号端口▪ 4 49152到65535号端口▪ 5 参考文献▪ 6 外部链接[编辑]端口状态颜色图例以下方块，以如下颜色和标签，标明了端口的状态：▪官方应用与端口组合记录在IANA的端口分配列表中；▪非官方应用与端口组合不在IANA的端口分配列表中；以及[编辑]0到1023号端口以下列表仅列出常用端口，详细的列表请参阅IANA网站。

端口描述状态0/TCP,UDP 保留端口；不使用（若发送过程不准备接受回复消息，则可以作为源端口）官方1/TCP,UDP TCPMUX（传输控制协议端口服务多路开关选择器）官方5/TCP,UDP RJE（远程作业登录）官方7/TCP,UDP ECHO（回显）协议官方9/TCP,UDP DISCARD（丢弃）协议官方11/TCP,UDP SYSTAT协议官方13/TCP,UDP DAYTIME协议官方15/TCP,UDP NETSTAT协议官方17/TCP,UDP QOTD（Quote of the Day，每日引用）协议官方18/TCP,UDP 消息发送协议官方19/TCP,UDP CHARGEN（字符发生器）协议官方20/TCP,UDP 文件传输协议- 默认数据端口官方21/TCP,UDP 文件传输协议- 控制端口官方22/TCP,UDP SSH (Secure Shell) - 远程登录协议，用于安全登录文件传输（SCP，SFTP）及端口重新定向官方23/TCP,UDP Telnet终端仿真协议- 未加密文本通信官方25/TCP,UDP SMTP（简单邮件传输协议）- 用于邮件服务器间的电子邮件传递官方26/TCP,UDP RSFTP - 一个简单的类似FTP的协议非官方35/TCP,UDP QMS Magicolor 2 printer非官方37/TCP,UDP TIME时间协议官方39/TCP,UDP Resource Location Protocol（资源定位协议）官方41/TCP,UDP 图形官方42/TCP,UDP Host Name Server（主机名服务）官方42/TCP,UDP WINS（WINS主机名服务）非官方43/TCP WHOIS协议官方49/TCP,UDP TACACS登录主机协议官方53/TCP,UDP DNS（域名服务系统）官方56/TCP,UDP 远程访问协议官方57/TCP MTP，邮件传输协议67/UDP BOOTP（BootStrap协议）服务；同时用于DHCP（动态主机设定协议）官方68/UDP BOOTP客户端；同时用于DHCP（动态主机设定协议）官方69/UDP TFTP（小型文件传输协议）官方70/TCP Gopher信息检索协议官方79/TCP Finger协议官方80/TCP HTTP（超文本传输协议）- 用于传输网页官方81/TCP HTTP预备（超文本传输协议）官方81/TCP Torpark - Onion routing ORport 非官方82/UDP Torpark - 控制端口非官方88/TCP Kerberos - 认证代理官方101/TCP 主机名102/TCP ISO-TSAP 协议107/TCP 远程Telnet协议109/TCP POP（Post Office Protocol），“邮局协议”，第2版110/TCP POP3（“邮局协议”，第3版）- 用于接收电子邮件官方111/TCP,UDP Sun协议官方113/TCP ident - old server identification system, 仍然被IRC服务器用来认证它的用户官方115/TCP SFTP, 简单文件传输协议117/TCP UUCP-PATH118/TCP,UDP SQL服务官方119/TCP NNTP (Network News Transfer Protocol) - 用来收取新闻组的消息官方123/UDP NTP (Network Time Protocol) - used for time synchronization 官方135/TCP,UDP EPMAP (End Point Mapper) / Microsoft RPC Locator Service 官方137/TCP,UDP NetBIOS NetBIOS Name Service 官方138/TCP,UDP NetBIOS NetBIOS Datagram Service 官方139/TCP,UDP NetBIOS NetBIOS Session Service 官方143/TCP,UDP IMAP4 (Internet Message Access Protocol 4) - used for retrieving E-mail s 官方152/TCP,UDP BFTP, Background File Transfer Program153/TCP,UDP SGMP, Simple Gateway Monitoring Protocol156/TCP,UDP SQL Service 官方158/TCP,UDP DMSP, Distributed Mail Service Protocol161/TCP,UDP SNMP (Simple Network Management Protocol) 官方162/TCP,UDP SNMPTRAP 官方170/TCP Print-srv179/TCP BGP (Border Gateway Protocol) 官方194/TCP IRC (Internet Relay Chat) 官方201/TCP,UDP AppleTalk Routing Maintenance209/TCP,UDP The Quick Mail Transfer Protocol213/TCP,UDP IPX官方218/TCP,UDP MPP, Message Posting Protocol220/TCP,UDP IMAP, Interactive Mail Access Protocol, version 3259/TCP,UDP ESRO, Efficient Short Remote Operations264/TCP,UDP BGMP，Border Gateway Multicast Protocol308/TCP Novastor Online Backup 官方311/TCP Apple Server-Admin-Tool, Workgroup-Manager-Tool318/TCP,UDP TSP, Time Stamp Protocol323/TCP,UDP IMMP, Internet Message Mapping Protocol383/TCP,UDP HP OpenView HTTPs Operations Agent366/TCP,UDP SMTP, Simple Mail Transfer Protocol. ODMR, On-Demand Mail Relay369/TCP,UDP Rpc2portmap 官方371/TCP,UDP ClearCase albd 官方384/TCP,UDP A Remote Network Server System387/TCP,UDP AURP, AppleTalk Update-based Routing Protocol389/TCP,UDP LDAP (Lightweight Directory Access Protocol) 官方401/TCP,UDP UPS Uninterruptible Power Supply 官方411/TCP Direct Connect Hub port 非官方412/TCP Direct Connect Client-To-Client port 非官方427/TCP,UDP SLP (Service Location Protocol) 官方443/TCP HTTPS - HTTP Protocol over TLS/SSL (encrypted transmission) 官方444/TCP,UDP SNPP，Simple Network Paging Protocol445/TCP Microsoft-DS (Active Directory，Windows shares, Sasser worm，Agobot, Zobotworm) 官方445/UDP Microsoft-DS SMB file sharing 官方464/TCP,UDP Kerberos Change/Set password 官方465/TCP Cisco protocol 官方465/TCP SMTP over SSL非官方475/TCP tcpnethaspsrv (Hasp services, TCP/IP version) 官方497/TCP dantz backup service 官方500/TCP,UDP ISAKMP，IKE-Internet Key Exchange 官方502/TCP,UDP Modbus，Protocol512/TCP exec, Remote Process Execution512/UDP comsat, together with biff：notifies users of new c.q. yet unread e-mail513/TCP Login513/UDP Whorsh protocol - used to execute non-interactive commandline commands on a remote system and see the screen 514/TCPreturn514/UDP syslog protocol - used for system logging 官方515/TCP Line Printer Daemon protocol - used in LPD printer servers517/UDP Talk518/UDP NTalk520/TCP efs520/UDP Routing - RIP官方513/UDP Router524/TCP,UDP NCP (NetWare Core Protocol) is used for a variety things such as access to primary NetWare server resources, Time 官方Synchronization, etc.525/UDP Timed, Timeserver530/TCP,UDP RPC官方531/TCP,UDP AOL Instant Messenger, IRC 非官方532/TCP netnews533/UDP netwall, For Emergency Broadcasts540/TCP UUCP (Unix-to-Unix Copy Protocol) 官方542/TCP,UDP commerce (Commerce Applications) 官方543/TCP klogin, Kerberos login544/TCP kshell, Kerberos Remote shell546/TCP,UDP DHCPv6 client547/TCP,UDP DHCPv6 server548/TCP AFP（Apple Filing Protocol）550/UDP new-rwho, new-who554/TCP,UDP RTSP (Real Time Streaming Protocol) 官方556/TCP Remotefs, rfs, rfs_server560/UDP rmonitor, Remote Monitor561/UDP monitor563/TCP,UDP NNTP protocol over TLS/SSL (NNTPS) 官方587/TCP email message submission（SMTP）(RFC 2476) Official 591/TCP FileMaker 6.0 (and later) Web Sharing (HTTP Alternate, see port 80)官方593/TCP,UDP HTTP RPC Ep Map（RPC over HTTP, often used by DCOM services and Microsoft Exchange Server）官方604/TCP TUNNEL631/TCP,UDP IPP，Internet Printing Protocol636/TCP,UDP LDAP over SSL (encrypted transmission, also known as LDAPS) 官方639/TCP,UDP MSDP, Multicast Source Discovery Protocol646/TCP LDP, Label Distribution Protocol647/TCP DHCP Failover Protocol648/TCP RRP, Registry Registrar Protocol652/TCP DTCP, Dynamic Tunnel Configuration Protocol654/UDP AODV, Ad hoc On-Demand Distance Vector665/TCP sun-dr, Remote Dynamic Reconfiguration 非官方666/UDP 毁灭战士，电脑平台上的一系列第一人称射击游戏。

TP-LINK TL-PS110U 打印服务器配置指南

不得以任何形式或任何方式（电子、机械、影印、录制或其他可能的方式）进行商品传播或用于任何商业、赢利目的。

为深圳市普联技术有限公司注册商标。

本文档提及的其他所有商标或注册商标，由各自的所有人拥有。

本手册所提到的产品规格和资讯仅供参考，如有内容更新，恕不另行通知。

除非有特殊约定，本手册仅作为使用指导，本手册中的所有陈述、信息等均不构成任何形式的担保。

目录1产品说明 (1)2产品规格 (1)2.1硬件规格 (1)2.2软件规格 (1)2.2.1Windows 95/98/ME (1)2.2.2Windows NT/2000/XP/2003/Vista (1)2.2.3NetWare (2)2.2.4UNIX/LINUX/FreeBSD (2)2.2.5MAC OS (2)2.3产品功能 (2)2.4指示灯规则 (3)3硬件安装 (3)3.1产品清单 (3)3.2安装之前 (3)3.3硬件安装步骤： (4)3.4注意事项 (4)3.5TL-PS110U网络架构 (4)4TL-PS110U打印服务器配置 (5)4.1开始之前 (5)4.2TL-PS110U支持配置方式 (5)4.3WEB浏览器配置 (5)4.4TP-LINK 管理工具 (7)4.4.1安装光盘 (7)4.4.1.1设置向导 (7)4.4.1.2手动安装 (8)4.4.1.3相关文件 (9)4.4.1.4离开 (9)4.4.2设置向导（PSWizard）配置 (9)4.4.3PSAdmin 配置 (18)4.4.3.1常规配置 (18)4.4.3.2向导配置 (21)4.5Telnet 配置 (22)4.6TFTP 配置 (26)5打印机配置 (28)5.1开始之前 (28)5.2支持打印方式 (29)5.3Standard TCP/IP Port (29)使用RAW 网络协议打印方式 (33)使用LPR 网络协议打印方式 (34)5.4NETWORK Print Port (37)使用TCP/IP网络协议创建端口 (39)使用IPX/SPX网络协议创建端口 (40)使用NetBEUI网络协议创建端口 (40)5.5IPP （Internet Printing Protocol） (43)5.6SMB (46)5.7SCO UNIX 8.0.0 （Caldera Open Unix 8.0.0） (50)5.8System V Release 4 Unix (51)6软件升级 (51)6.1透过WEB浏览器升级 (51)6.2透过PSAdmin升级 (52)6.3透过TFTP升级 (53)6.4UNIX升级 (54)7FAQ (54)1 产品说明TP-LINK TL-PS110U高速单USB口打印服务器（以下简称TL-PS110U），是一款可以支持一个USB2.0/1.1端口打印机的单端口打印服务器。

网络安全——网络安全性协议 ln

网络安全——网络安全性协议
6.4.1 应用层安全协议
安全外壳协议SSH
用密码算法提供安全可靠的远程登录、文件传输和远程复制等网络应用程序。
安全超文本传输协议S-HTTP
S-HTTP提供了文件级的安全机制，用作加密及签名的算法可以由参与通信的收发双方协商。
2020/5/30
信息安全案例教程：技术与应用
SSL提供的面向连接的安全性具有以下三个基本性质：
连接是秘密的。
连接是可认证的。
连接是可靠的。
2020/5/30
信息安全案例教程：技术与应用
6.4.2 传输层安全协议SSL
2. SSL使用的安全机制以及提供的安全服务
SSL中使用的安全机制有：
加密机制数据签名机制数据完整性机制交换鉴别机制公证机制
1. IPsec基本概念
IPSec定义了一种标准、健壮的以及包容广泛的机制，可用它为IP及其上层协议(如TCP和 UDP)提供安全保证。
IPSec的目标是为IPv4和IPv6提供具有较强的互操作能力、高质量和基于密码的安全功能，在IP层实现多种安全服务，包括访问控制、数据完整性、数据源验证、抗重播、机密性等。 IPSec通过支持一系列加密算法如DES、三重 DES、IDEA、AES等确保通信双方的机密性。
SSL可以用于任何面向连接的安全通信，但通常用于安全Web应用的HTTP协议。
2020/5/30
信息安全案例教程：技术与应用
6.4.2 传输层安全协议SSL
2. SSL使用的安全机制以及提供的安全服务
SSL使用公钥密码系统和技术进行客户机和服务器通信实体身份的认证和会话密钥的协商，使用对称密码算法对SSL连接上传输的敏感数据进行加密。

rfc3995.Internet Printing Protocol (IPP) Event Notifications and Subscriptions

Network Working Group R. Herriot Request for Comments: 3995 Global Workflow Solutions Category: Standards Track T. Hastings Updates: 2911, 2910 Xerox Corporation March 2005 Internet Printing Protocol (IPP):Event Notifications and SubscriptionsStatus of This MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "InternetOfficial Protocol Standards" (STD 1) for the standardization stateand status of this protocol. Distribution of this memo is unlimited. Copyright NoticeCopyright (C) The Internet Society (2005).AbstractThis document describes an OPTIONAL extension to the InternetPrinting Protocol/1.1: Model and Semantics (RFC 2911, RFC 2910).This extension allows a client to subscribe to printing relatedEvents. Subscriptions are modeled as Subscription Objects. TheSubscription Object specifies that when one of the specified Eventsoccurs, the Printer delivers an asynchronous Event Notification tothe specified Notification Recipient via the specified Push or PullDelivery Method (i.e., protocol).A client associates Subscription Objects with a particular Job byperforming the Create-Job-Subscriptions operation or by submitting a Job with subscription information. A client associates Subscription Objects with the Printer by performing a Create-Printer-Subscriptions operation. Four other operations are defined for SubscriptionObjects: Get-Subscriptions-Attributes, Get-Subscriptions, Renew-Subscription, and Cancel-Subscription.Herriot & Hastings Standards Track [Page 1]Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 51.1. Notification Overview. . . . . . . . . . . . . . . . . . 52. Models for Notification. . . . . . . . . . . . . . . . . . . . 8 2.1. Model for Simple Notification (Normative). . . . . . . . 82.2. Additional Models for Notification (Informative) . . . . 93. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . 9 3.1. Conformance Terminology. . . . . . . . . . . . . . . . . 93.2. Other Terminology. . . . . . . . . . . . . . . . . . . . 104. Object Relationships . . . . . . . . . . . . . . . . . . . . . 12 4.1. Printer and Per-Printer Subscription Objects . . . . . . 134.2. Printer, Job and Per-Job Subscription Objects. . . . . . 135. Subscription Object. . . . . . . . . . . . . . . . . . . . . . 13 5.1. Rules for Support of Subscription Template Attributes. . 14 5.2. Rules for Processing Subscription Template Attributes. . 15 5.3. Subscription Template Attributes . . . . . . . . . . . . 18 5.3.1. notify-recipient-uri (uri) . . . . . . . . . . . 20 5.3.2. notify-pull-method (type2 keyword) . . . . . . . 21 5.3.3. notify-events (1setOf type2 keyword) . . . . . . 22 5.3.4. notify-attributes (1setOf type2 keyword) . . . . 29 5.3.5. notify-user-data (octetString(63)) . . . . . . . 30 5.3.6. notify-charset (charset) . . . . . . . . . . . . 31 5.3.7. notify-natural-language (naturalLanguage). . . . 31 5.3.8. notify-lease-duration (integer(0:67108863)). . . 32 5.3.9. notify-time-interval (integer(0:MAX)). . . . . . 33 5.4. Subscription Description Attributes. . . . . . . . . . . 34 5.4.1. notify-subscription-id (integer (1:MAX)). . . . 35 5.4.2. notify-sequence-number (integer (0:MAX)) . . . . 35 5.4.3. notify-lease-expiration-time (integer(0:MAX)). . 36 5.4.4. notify-printer-up-time (integer(1:MAX)). . . . . 37 5.4.5. notify-printer-uri (uri) . . . . . . . . . . . . 37 5.4.6. notify-job-id (integer(1:MAX)) . . . . . . . . . 375.4.7. notify-subscriber-user-name (name(MAX)). . . . . 386. Printer Description Attributes Related to Notification . . . . 38 6.1. printer-state-change-time (integer(1:MAX)) . . . . . . . 396.2. printer-state-change-date-time (dateTime). . . . . . . . 397. New Values for Existing Printer Description Attributes . . . . 397.1. operations-supported (1setOf type2 enum) . . . . . . . . 408. Attributes Only in Event Notifications . . . . . . . . . . . . 40 8.1. notify-subscribed-event (type2 keyword). . . . . . . . . 408.2. notify-text (text(MAX)). . . . . . . . . . . . . . . . . 419. Event Notification Content . . . . . . . . . . . . . . . . . . 41 9.1. Content of Machine Consumable Event Notifications. . . . 44 9.1.1. Event Notification Content Common to All Events. 44 9.1.2. Additional Event Notification Content for JobEvents . . . . . . . . . . . . . . . . . . . . . 45 Herriot & Hastings Standards Track [Page 2]9.1.3. Additional Event Notification Content forPrinter Events . . . . . . . . . . . . . . . . . 46 9.2. Content of Human Consumable Event Notification . . . . . 46 9.2.1. Event Notification Content Common to All Events. 47 9.2.2. Additional Event Notification Content for JobEvents . . . . . . . . . . . . . . . . . . . . . 49 9.2.3. Additional Event Notification Content forPrinter Events . . . . . . . . . . . . . . . . . 4910. Delivery Methods . . . . . . . . . . . . . . . . . . . . . . . 5011. Operations for Notification. . . . . . . . . . . . . . . . . . 52 11.1. Subscription Creation Operations . . . . . . . . . . . . 52 11.1.1. Create-Job-Subscriptions Operation . . . . . . . 52 11.1.2. Create-Printer-Subscriptions operation . . . . . 55 11.1.3. Job Creation Operations - Extensions forNotification . . . . . . . . . . . . . . . . . . 56 11.2 Other Operations. . . . . . . . . . . . . . . . . . . . . 58 11.2.1. Restart-Job Operation - Extensions forNotification . . . . . . . . . . . . . . . . . . 58 11.2.2. Validate-Job Operation - Extensions forNotification . . . . . . . . . . . . . . . . . . 59 11.2.3. Get-Printer-Attributes - Extensions forNotification . . . . . . . . . . . . . . . . . . 59 11.2.4. Get-Subscription-Attributes operation. . . . . . 60 11.2.5. Get-Subscriptions operation. . . . . . . . . . . 63 11.2.6. Renew-Subscription operation . . . . . . . . . . 6611.2.7. Cancel-Subscription operation. . . . . . . . . . 6812. Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . 70 12.1. successful-ok-ignored-subscriptions (0x0003) . . . . . . 7012.2. client-error-ignored-all-subscriptions (0x0414). . . . . 7113. Status Codes in Subscription Attributes Groups . . . . . . . . 71 13.1. client-error-uri-scheme-not-supported (0x040C) . . . . . 71 13.2. client-error-attributes-or-values-not-supported (0x040B) 71 13.3. client-error-too-many-subscriptions (0x0415) . . . . . . 72 13.4. successful-ok-too-many-events (0x0005) . . . . . . . . . 7213.5. successful-ok-ignored-or-substituted-attributes (0x0001) 7214. Encodings of Additional Attribute Tags . . . . . . . . . . . . 7215. Conformance Requirements . . . . . . . . . . . . . . . . . . . 72 15.1. Conformance requirements for clients . . . . . . . . . . 7315.2. Conformance requirements for Printers. . . . . . . . . . 7316. Model for Notification with Cascading Printers (Informative) . 7417. Distributed Model for Notification (Informative) . . . . . . . 7518. Extended Notification Recipient (Informative). . . . . . . . . 7619. Object Model for Notification (Normative). . . . . . . . . . . 77 19.1. Object relationships . . . . . . . . . . . . . . . . . . 78 19.2. Printer Object and Per-Printer Subscription Objects. . . 7919.3. Job Object and Per-Job Subscription Objects. . . . . . . 7920. Per-Job versus Per-Printer Subscription Objects (Normative). . 7921. Normative References . . . . . . . . . . . . . . . . . . . . . 80 Herriot & Hastings Standards Track [Page 3]22. Informative References . . . . . . . . . . . . . . . . . . . . 8023. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 81 23.1. Attribute Registrations. . . . . . . . . . . . . . . . . 82 23.2. Additional Enum Attribute Value Registrations withinthe IPP registry . . . . . . . . . . . . . . . . . . . . 83 23.3. Operation Registrations. . . . . . . . . . . . . . . . . 83 23.4. Status code Registrations. . . . . . . . . . . . . . . . 83 23.5. Attribute Group tag Registrations. . . . . . . . . . . . 84 23.6. Registration of Events . . . . . . . . . . . . . . . . . 84 23.7. Registration of Event Notification Delivery Methods. . . 85 23.7.1. Requirements for Registration of EventNotification Delivery Methods. . . . . . . . . . 85 23.7.2. Registration Procedure . . . . . . . . . . . . . 86 23.7.3. Delivery Method Document Registrations . . . . . 8723.7.4. Registration Template. . . . . . . . . . . . . . 8824. Internationalization Considerations. . . . . . . . . . . . . . 8925. Security Considerations. . . . . . . . . . . . . . . . . . . . 89 25.1. Client access rights . . . . . . . . . . . . . . . . . . 89 25.2. Printer security threats . . . . . . . . . . . . . . . . 9125.3. Notification Recipient security threats. . . . . . . . . 9126. Description of the base IPP documents (Informative). . . . . . 9227. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 93 Authors’ Addresses . . . . . . . . . . . . . . . . . . . . . . . . 94 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 95TablesTable 1 - Subscription Template Attributes. . . . . . . . . . . . 20 Table 2 - Subscription Description Attributes . . . . . . . . . . 35 Table 3 - Printer Description Attributes Associated withNotification. . . . . . . . . . . . . . . . . . . . . . 39 Table 4 - Operation-id assignments. . . . . . . . . . . . . . . . 40 Table 5 - Attributes in Event Notification Content. . . . . . . . 45 Table 6 - Additional Event Notification Content for Job Events. . 46 Table 7 - Combinations of Events and Subscribed Events for"job-impressions-completed" . . . . . . . . . . . . . . 46 Table 8 - Additional Event Notification Content for PrinterEvents. . . . . . . . . . . . . . . . . . . . . . . . . 46 Table 9 - Printer Name in Event Notification Content. . . . . . . 48 Table 10 - Event Name in Event Notification Content. . . . . . . . 48 Table 11 - Event Time in Event Notification Content. . . . . . . . 48 Table 12 - Job Name in Event Notification Content. . . . . . . . . 49 Table 13 - Job State in Event Notification Content . . . . . . . . 49 Table 14 - Printer State in Event Notification Content . . . . . . 50 Table 15 - Information about the Delivery Method . . . . . . . . . 51 Table 16 - Printer Conformance Requirements for Operations . . . . 74 Herriot & Hastings Standards Track [Page 4]FiguresFigure 1 - Model for Notification. . . . . . . . . . . . . . . . . 9 Figure 2 - Model for Notification with Cascading Printers. . . . . 75 Figure 3 - Opaque Use of a Notification Server Transparent to theClient. . . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 4 - Use of an Extended Notification Recipient transparentto the Printer. . . . . . . . . . . . . . . . . . . . . 77 Figure 5 - Object Model for Notification . . . . . . . . . . . . . 78 1. IntroductionThis IPP notification specification is an OPTIONAL extension toInternet Printing Protocol/1.1: Model and Semantics [RFC2911,RFC2910]. See Appendix 29 for a description of the base IPPdocuments. This document in combination with the following documents is intended to meet the most important notification requirementsdescribed in [RFC3997]:Internet Printing Protocol (IPP): "Job Progress Attributes"[RFC3381]Internet Printing Protocol (IPP): "The ’ippget’ Delivery Methodfor Event Notifications" [RFC3996]This specification REQUIRES that clients and Printers support the’ippget’ Pull Delivery Method [RFC3996]. Conforming client andPrinter implementations MAY support additional Push or Pull Delivery Methods as well. Note: this document does not define any DeliveryMethods itself, but it does define the rules for conformance forDelivery Method Documents and their registration with IANA (seesection 23.7.3).Refer to the Table of Contents for the layout of this document.1.1. Notification OverviewThis document defines operations that a client can perform in orderto create Subscription Objects in a Printer and carry out otheroperations on them. A Subscription Object represents a Subscription abstraction. The Subscription Object specifies that when one of the specified Events occurs, the Printer delivers an asynchronous EventNotification to the specified Notification Recipient via thespecified Delivery Method (i.e., protocol).When a client (called a Subscribing Client) performs an operationthat creates a Subscription Object, the operation contains one ormore Subscription Template Attributes Groups. Each such group holds Herriot & Hastings Standards Track [Page 5]information used by the Printer to initialize a newly createdSubscription Object. The Printer creates one Subscription Object for each Subscription Template Attributes Group in the operation. Thisgroup is like the Job Template Attributes group defined in [RFC2911]. The following is an example of the information included in aSubscription Template Attributes Group (see section 5 for details on the Subscription Object attributes):1. The names of Subscribed Events that are of interest to theNotification Recipient.2. The address (URL) of one Notification Recipient for a PushDelivery Method or the method for a Pull Delivery Method.3. The Delivery Method (i.e., the protocol) which the Printer uses to deliver the Event Notification.4. Some opaque data that the Printer delivers to the NotificationRecipient in the Event Notification. For example, theNotification Recipient might use this opaque data as a forwarding address for the Event Notification.5. The charset to use in text fields within an Event Notification6. The natural language to use in the text fields of the EventNotification7. The requested lease time in seconds for the Subscription ObjectAn operation that creates a Subscription Object is called aSubscription Creation Operation. These operations include thefollowing operations (see section 11.1 for further details):- Job Creation operation: When a client performs such anoperation (Print-Job, Print-URI, and Create-Job), a client can include zero or more Subscription Template Attributes Groups in the request. The Printer creates one Subscription Object foreach Subscription Template Attributes Group in the request, and the Printer associates each such Subscription Object with thenewly created Job. This document extends these operations’definitions in [RFC2911] by adding Subscription TemplateAttributes Groups in the request and Subscription AttributesGroups in the response.- Create-Job-Subscriptions operation: A client can include one or more Subscription Template Attributes Groups in the request.The Printer creates one Subscription Object for eachHerriot & Hastings Standards Track [Page 6]Subscription Template Attributes Group and associates each with the job that is the target of this operation.- Create-Printer-Subscriptions operation: A client can includeone or more Subscription Template Attributes Groups in therequest. The Printer creates one Subscription Object for each Subscription Template Attributes Group and associates each with the Printer that is the target of this operation.For each of the above operations:- the Printer associates a Subscription Object with the Printeror a specific Job. When a Subscription Object is associatedwith a Job Object, it is called a Per-Job Subscription Object. When a Subscription Object is associated with a Printer Object, it is called a Per-Printer Subscription Object.- the response contains one Subscription Attributes Group foreach Subscription Template Attributes Group in the request and in the same order. When the Printer successfully creates aSubscription Object, its corresponding Subscription Attributes Group contains the "notify-subscription-id" attribute. Thisattribute uniquely identifies the Subscription Object and isanalogous to a "job-id" for a Job object. Some operationsdescribed below use the "notify-subscription-id" to identifythe target Subscription Object.This document defines the following additional operations (seesection 11.2 for further details):- Restart-Job operation: When a client performs the Restart-Joboperation [RFC2911], the Printer re-uses the same Job and itsSubscription Objects.- Validate-Job operation: When a client performs this operation, aclient can include zero or more Subscription Template AttributesGroups in the request. The Printer determines if it could create one Subscription Object for each Subscription Template Attributes Group in the request. This document extends this operation’sdefinition in [RFC2911] by adding Subscription Template Attributes Groups in the request and Subscription Attributes Groups in theresponse.- Get-Subscription-Attributes operation: This operation allows aclient to obtain the specified attributes of a target Subscription Object.Herriot & Hastings Standards Track [Page 7]- Get-Subscriptions operation: This operation allows a client toobtain the specified attributes of all Subscription Objectsassociated with the Printer or a specified Job.- Renew-Subscription operation: This operation renews the lease onthe target Per-Printer Subscription Object before it expires. Anewly created Per-Printer Subscription Object receives an initial lease. It is the duty of the client to use this operationfrequently enough to preserve a Per-Printer Subscription Object.The Printer deletes a Per-Printer Subscription Object when itslease expires. A Per-Job Subscription Object last exactly as long as its associated Job Object and thus doesn’t have a lease.- Cancel-Subscription operation: This operation (1) cancels thelease on the specified Per-Printer Subscription Object and thereby deletes the Per-Printer Subscription Object or (2) deletes thePer-Job Subscription Object.When an Event occurs, the Printer finds all Subscription Objectslistening for the Event (see section 9 for details on finding suchSubscription Objects). For each such Subscription Object, thePrinter:a) generates an Event Notification with information specified insection 9, ANDb) either:i) If the Delivery Method is a Push Delivery Method as indicated by the presence of the Subscription Object’s "notify-recipient-uri" attribute, delivers the Event Notificationusing the Delivery Method and target address identified in the Subscription Object’s "notify-recipient-uri" attribute, ORii) If the Delivery Method is a Pull Delivery Method as indicated by the presence of the Subscription Object’s "notify-pull-method" attribute, saves Event Notification for a time period called the Event Life defined by the Delivery Method, i.e.,the Notification Recipient is expected to fetch the EventNotifications.2. Models for Notification2.1. Model for Simple Notification (Normative)As part of a Subscription Creation Operation, an IPP Printer (i.e.,located in an output device or a server) creates one or moreSubscription Objects. In a Subscription Creation Operation, the Herriot & Hastings Standards Track [Page 8]client specifies the Notification Recipient to which the Printer isto deliver Event Notifications. A Notification Recipient can be the Subscribing Client or a third party.Figure 1 shows the Notification model for a simple Client-Printerrelationship.embedded printer:output device or serverPDA, desktop, or server +---------------++--------+ | ########### || client |-----Subscription ---------># Printer # |+--------+ Creation Operation | # Object # |+------------+ | #####|##### ||Notification| +-------|-------+|Recipient |<----IPP Event Notifications----++------------+ (Job and/or Printer Events)Figure 1 - Model for Notification2.2. Additional Models for Notification (Informative)Additional models have been proposed (see Appendices 16, 17, and 18).3. TerminologyThis section defines terminology used throughout this document.Other terminology is defined in [RFC2911].3.1. Conformance TerminologyCapitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULDNOT, MAY, NEED NOT, and OPTIONAL, have special meaning relating toconformance as defined in RFC 2119 [RFC2119] and [RFC2911] section12.1. If an implementation supports the extension defined in thisdocument, then these terms apply; otherwise, they do not. Theseterms define conformance to this document only; they do not affectconformance to other documents, unless explicitly stated otherwise.Note: a feature that is OPTIONAL in this document becomes REQUIRED if the Printer implements a Delivery Method that REQUIRES the feature.READ-ONLY - an adjective used in an attribute definition to indicate that an IPP Printer MUST NOT allow the attribute’s value to bemodified.Herriot & Hastings Standards Track [Page 9]3.2. Other TerminologyThis document uses the same terminology as [RFC2911], such as"client", "Printer", "attribute", "attribute value", "keyword","operation", "request", "response", "administrator", "operator", and "support". In addition, the following terms are defined for use inthis document and the Delivery Method Documents:Compound Event Notification - two or more Event Notifications that a Printer delivers together as a single request or response. TheDelivery Method Document specifies whether the Delivery Methodsupports Compound Event Notifications.Delivery Method - the mechanism by which the Printer delivers anEvent Notification.Delivery Method Document - a document, separate from this document,that defines a Delivery Method.Event - some occurrence (either expected or unexpected) within theprinting system of a change of state, condition, or configuration of a Job or Printer object. An Event occurs only at one instant in time and does not span the time the physical Event takes place. Forexample, jam-occurred and jam-cleared are two distinct, instantaneous Events, even though the jam may last for a while.Event Life - For a Pull Delivery Method, the length of time inseconds after an Event occurs during which the Printer will retainthat Event for delivery in an Event Notification. After the EventLife expires, the Printer will no longer deliver an EventNotification for that Event in such a response.Event Notification - the information about an Event that the Printer delivers when an Event occurs.Event Notification Attributes Group - The attributes group which isused to deliver an Event Notification in a request (Push DeliveryMethods) or a response (Pull Delivery Methods).Human Consumable Event Notification - localized text for humanconsumption only. There is no standardized format and thus programs should not try to parse this text.Job Creation operation - One of the operations that creates a Jobobject: Print-Job, Print-URI and Create-Job. The Restart-Joboperation [RFC2911] is not considered a Job Creation operation, since the Printer re-uses the existing Job object. The Validate-Joboperation is not considered a Job Creation operation because no Job Herriot & Hastings Standards Track [Page 10]object is created. Therefore, when a statement also applies toeither the Restart-Job and/or the Validate-Job operation, they arementioned explicitly.Job Event - an Event caused by some change in a particular job on the Printer, e.g., ’job-completed’.Machine Consumable Event Notification - bytes for programconsumption. The bytes are formatted according to the DeliveryMethod document.Notification - when not in the phrases ’Event Notification’ and’Notification Recipient’ - the concepts of this specification, i.e., Events, Subscription Objects, and Event Notifications.Notification Recipient - the entity to which the Printer delivers an Event Notification. For Push Delivery Methods, the IPP Printer sends the Notifications to a Notification Recipient. For Pull DeliveryMethods, the Notification Recipient is acting in the role of an IPPclient and requests Event Notifications and so the terms "client" and "Notification Recipient" are used interchangeably with such Delivery Methods. For example, see [RFC3996].Per-Job Subscription Object - A Subscription Object that isassociated with a single Job. The Create-Job-Subscriptions operation and Job Creation operations create such an object.Per-Printer Subscription Object - A Subscription Object that isassociated with the Printer as a whole. The Create-Printer-Subscriptions operation creates such an object.Printer Event - an Event caused by some change in the Printer that is not specific to a job, e.g., ’printer-state-changed’.Pull Delivery Method - The Printer saves Event Notifications for some event life time and expects the Notification Recipient to requestEvent Notifications. The Printer delivers the Event Notifications in a response to such a request.Push Delivery Method -The Printer delivers the Event Notificationshortly after an Event occurs.Subscribed Event - an Event that the Subscribing Client expressesinterest in by making it a value of the "notify-events" attribute on a Subscription Object.Subscribed Job Event - a Subscribed Event that is a Job Event.Herriot & Hastings Standards Track [Page 11]Subscribed Printer Event - a Subscribed Event that is a PrinterEvent.Subscribing Client - The client that creates the Subscription Object. Subscription Attributes Group - The attributes group in a responsethat contains Subscription Object attributes.Subscription Creation Operation - An operation that creates aSubscription Object: Job Creation operations, Create-Job-Subscriptions operation, Create-Printer-Subscriptions operation. In the context of a Job Creation operation, a Subscription CreationOperation is the part of the Job Creation operation that creates one or more Subscription objects. The Restart-Job operation [RFC2911] is not considered a Subscription Creation Operation, since the Printerre-uses the Job’s existing Subscription Objects, rather than creating any new Subscription Objects.Subscription Creation Request - The request portion of a Subscription Creation Operation.Subscription Description Attributes - Subscription Object attributes that a Printer supplies during a Subscription Creation Operation.Subscription Object - An object containing a set of attributes thatindicate: the Notification Recipient (for Push Delivery Methodonly), the Delivery Method, the Subscribed Events that cause thePrinter to deliver an Event Notification, and the information toinclude in an Event Notification.Subscription Template Attributes - Subscription Object attributesthat a client can supply in a Subscription Creation Operation andassociated Printer Object attributes that specify supported anddefault values for the Subscription Object attributes.Subscription Template Attributes Group - The attributes group in arequest that contains Subscription Object attributes that areSubscription Template Attributes.4. Object RelationshipsThis section defines the object relationships between the Printer,Job, and Subscription Objects. It does not define theimplementation. For an illustration of these relationships, seeAppendix 19.Herriot & Hastings Standards Track [Page 12]。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

Network Working Group C. Kugler Request for Comments: 3998 H. Lewis Category: Standards Track IBM Corporation T. Hastings, Ed. Xerox Corporation March 2005 Internet Printing Protocol (IPP):Job and Printer Administrative OperationsStatus of This MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "InternetOfficial Protocol Standards" (STD 1) for the standardization stateand status of this protocol. Distribution of this memo is unlimited. Copyright NoticeCopyright (C) The Internet Society (2005).AbstractThis document specifies the following 16 additional OPTIONAL systemadministration operations for use with the Internet PrintingProtocol/1.1 (IPP), plus a few associated attributes, values, andstatus codes, and using the IPP Printer object to manage printerfan-out and fan-in.Printer operations: Job operations:Enable-Printer and Disable-Printer Reprocess-JobPause-Printer-After-Current-Job Cancel-Current-JobHold-New-Jobs and Release-Held-New-Jobs Suspend-Current-JobDeactivate-Printer and Activate-Printer Resume-JobRestart-Printer Promote-JobShutdown-Printer and Startup-Printer Schedule-Job-After Kugler, et al. Standards Track [Page 1]Table of Contents1. Introduction (4)2. Terminology (4)2.1. Conformance Terminology (4)2.2. Other Terminology (5)3. Definition of the Printer Operations (6)3.1. The Disable and Enable Printer Operations (7)3.1.1. Disable-Printer Operation (7)3.1.2. Enable-Printer Operation (8)3.2. The Pause and Resume Printer Operations (8)3.2.1. Pause-Printer-After-Current-Job Operation (9)3.3. Hold and Release New Jobs Operations (11)3.3.1. Hold-New-Jobs Operation (11)3.3.2. Release-Held-New-Jobs Operation (12)3.4. Deactivate and Activate Printer Operations (12)3.4.1. Deactivate-Printer Operation (13)3.4.2. Activate-Printer Operation (13)3.5. Restart-Printer, Shutdown-Printer,and Startup-Printer Operations (14)3.5.1. Restart-Printer Operation (14)3.5.2. Shutdown-Printer Operation (14)3.5.3. Startup-Printer Operation (15)4. Definition of the Job Operations (16)4.1. Reprocess-Job Operation (17)4.2. Cancel-Current-Job Operation (17)4.3. Suspend and Resume Job Operations (18)4.3.1. Suspend-Current-Job Operation (19)4.3.2. Resume-Job Operation (20)4.4. Job Scheduling Operations (20)4.4.1. Promote-Job Operation (20)4.4.2. Schedule-Job-After Operation (21)5. Additional Status Codes (23)5.1. ’server-error-printer-is-deactivated’ (0x050A) (23)6. Use of Operation AttributesThat Are Messages from the Operator (23)7. New Printer Description Attributes (26)7.1. subordinate-printers-supported (1setOf uri) (26)7.2. parent-printers-supported (1setOf uri) (26)8. Additional Values forthe "printer-state-reasons" Printer Description Attribute (26)8.1. ’hold-new-jobs’ Value (27)8.2. ’deactivated’ Value (27)9. Additional Values forthe "job-state-reasons" Job Description attribute (27)9.1. ’job-suspended’ Value (27)10. Use of the Printer Object to RepresentIPP Printer Fan-Out and IPP Printer Fan-In (27)Kugler, et al. Standards Track [Page 2]10.1. IPP Printer Fan-Out (28)10.2. IPP Printer Fan-In (28)10.3. Printer Object Attributes Usedto Represent Printer Fan-Out and Printer Fan-In (29)10.4. Subordinate Printer URI (29)10.5. Printer Object Attributes Usedto Represent Output Device Fan-Out (30)10.6. Figures to Show All Possible Configurations (30)10.7. Forwarding Requests (33)10.7.1. Forwarding Requeststhat Affect Printer Objects (33)10.7.2. Forwarding Requests that Affect Jobs (35)10.8. Additional Attributes to Help with Fan-Out (37)10.8.1. output-device-assigned (name(127))Job Description Attribute - from [RFC2911] (37)10.8.2. original-requesting-user-name (name(MAX))Operation and Job Description Attribute (37)10.8.3. requesting-user-name (name(MAX))Operation Attribute - Additional Semantics (38)10.8.4. job-originating-user-name (name(MAX))Job Description Attribute -Additional Semantics (38)11. Conformance Requirements (38)12. Normative References (39)13. Informative References (40)14. IANA Considerations (40)14.1. Attribute Registrations (41)14.2. Attribute Value Registrations (41)14.3. Additional Enum Attribute Value Registrations (41)14.4. Operation Registrations (42)14.5. Status Code Registrations (43)15. Internationalization Considerations (43)16. Security Considerations (43)17. Summary of Base IPP Documents (44)Authors’ Addresses (45)Full Copyright Statement (46)List of TablesTable 1. Printer Operation Operation-Id Assignments (6)Table 2. Pause and Resume Printer Operations (9)Table 3. State Transition Table forPause-Printer-After-Current-Job Operation (10)Table 4. Job Operation Operation-Id Assignments (16)Table 5. Operation Attribute Support for Printer Operations (24)Table 6. Operation Attribute Support for Job Operations (25)Table 7. Forwarding Operations that Affect Printer Objects (34)Table 8. Forwarding Operations that Affect Jobs Objects (36)Kugler, et al. Standards Track [Page 3]Table 9. Conformance Requirement Dependencies for Operations (38)Table 10. Conformance Requirement Dependenciesfor "printer-state-reasons" Values (39)Table 11. Conformance Requirement Dependenciesfor "job-state-reasons" Values (39)List of FiguresFigure 1. Embedded Printer Object (31)Figure 2. Hosted Printer Object (31)Figure 3. Output Device Fan-Out (31)Figure 4. Chained IPP Printer Objects (32)Figure 5. IPP Printer Object Fan-Out (32)Figure 6. IPP Printer Object Fan-In (33)1. IntroductionThe Internet Printing Protocol (IPP) is an application level protocol that can be used for distributed printing using Internet tools andtechnologies. IPP version 1.1 ([RFC2911, RFC2910]) focuses on end-user functionality, with a few administrative operations included.This document defines additional OPTIONAL end user, operator, andadministrator operations used to control Jobs and Printers. Inaddition, this document extends the semantic model of the Printerobject by allowing them to be configured into trees and/or invertedtrees that represent Printer object Fan-Out and Printer object Fan-In, respectively. The special case of a tree with only a singleSubordinate node represents Chained Printers. This document is aregistration proposal for an extension to IPP/1.0 and IPP/1.1following the registration procedures in those documents.The requirements and use cases for this document are defined in[RFC3239].2. TerminologyThis section defines the terminology used throughout this document. 2.1. Conformance TerminologyCapitalized terms such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULDNOT, MAY, NEED NOT, and OPTIONAL have special meaning relating toconformance as defined in RFC 2119 [RFC2119] and [RFC2911], section12.1. If an implementation supports the extension defined in thisdocument, then these terms apply; otherwise, they do not. Theseterms define conformance to this document only; they do not affectconformance to other documents, unless explicitly stated otherwise. Kugler, et al. Standards Track [Page 4]2.2. Other TerminologyThis document uses terms such as "client", "Printer", "Job","attributes", "keywords", "operation", and "support". These termshave special meaning and are defined in the model terminology([RFC2911], section 12.2).In addition, the following capitalized terms are defined:IPP Printer object (or Printer for short) - A software abstractiondefined by [RFC2911].Printer Operation - An operation whose target is an IPP Printerobject and whose effect is on the Printer object.Output Device - The physical imaging mechanism that an IPP Printercontrols. Note: although this term is capitalized in thisspecification (but not in [RFC2911]), there is no formal objectcalled an Output Device defined in this document (or in [RFC2911]).Output Device Fan-Out - A configuration in which an IPP Printercontrols more than one Output Device.Printer Fan-Out - A configuration in which an IPP Printer objectcontrols more than one Subordinate IPP Printer object.Printer Fan-In - A configuration in which an IPP Printer object iscontrolled by more than one IPP Printer object.Subordinate Printer - An IPP Printer object that is controlled byanother IPP Printer object. Such a Subordinate Printer MAY have zero or more Subordinate Printers.Leaf Printer - An IPP Printer object that has no SubordinatePrinters.Non-Leaf Printer - An IPP Printer object that has one or moreSubordinate Printers. A Non-Leaf Printer is also called a ParentPrinter.Chained Printer - a Non-Leaf Printer that has exactly one Subordinate Printer.Job Creation operations - IPP operations that create a Job object:Print-Job, Print-URI, and Create-Job.Kugler, et al. Standards Track [Page 5]3. Definition of the Printer OperationsAll Printer Operations are directed at Printer objects. A clientMUST always supply the "printer-uri" operation attribute in order to identify the correct target of the operation. These descriptionsassume all of the common semantics of the IPP/1.1 Model and Semantics document ([RFC2911], section 3.1).The Printer Operations defined in this document are summarized inTable 1.Table 1. Printer Operation Operation-Id AssignmentsOperation Name Operation-Id Brief Description-------------------------------------------------------------------- Enable-Printer 0x22 Allows the target Printer to acceptJob Creation operations.Disable-Printer 0x23 Prevents the target Printer fromaccepting Job Creation operations.Pause-Printer- 0x24 Pauses the Printer after the currentAfter-Current- job has been sent to the OutputJob Device.Hold-New-Jobs 0x25 Finishes processing all currentlypending jobs. Any new jobs areplaced in the ’pending-held’ state.Release-Held- 0x26 Releases all jobs to the ’pending’New-Jobs state that had been held by theeffect of a previous Hold-New-Jobsoperation and condition the Printerso that it no longer holds new jobs.Deactivate- 0x27 Puts the Printer into a read-onlyPrinter deactivated state.Activate- 0x28 Restores the Printer to normalPrinter activity.Restart-Printer 0x29 Restarts the target Printer and re-initializes the software.Shutdown- 0x2A Shuts down the target Printer so thatPrinter it cannot be restarted or queried. Kugler, et al. Standards Track [Page 6]Startup-Printer 0x2B Starts up the instance of the Printerobject.All of the operations in this document are OPTIONAL for an IPP object to support. Unless the specification of an OPTIONAL operationrequires support of another OPTIONAL operation, conformingimplementations may support any combination of these operations.Many of the operations come in pairs, so both are REQUIRED if either one is implemented.3.1. The Disable and Enable Printer OperationsThis section defines the OPTIONAL Disable-Printer and Enable-Printer operations that stop and start the IPP Printer object from accepting new IPP jobs. If either of these operations are supported, both MUST be supported.These operations allow the operator to control whether the Printerwill accept new Job Creation (Print-Job, Print-URI, and Create-Job)operations. These operations have no other effect on the Printer, so the Printer continues to accept all other operations and continues to schedule and process jobs normally. In other words, these operations control the "input of new jobs" to the IPP Printer, and the Pause and Resume operations (see section 3.2) independently control the "output of new jobs" from the IPP Printer to the Output Device.3.1.1. Disable-Printer OperationThis OPTIONAL operation allows a client to stop the Printer objectfrom accepting new jobs; i.e., it causes the Printer to rejectsubsequent Job Creation operations and return the ’server-error-not- accepting-jobs’ status code. The Printer still accepts all otheroperations, including Validate-Job, Send-Document, and Send-URIoperations. Thus a Disable-Printer operation allows a client tocontinue submitting multiple documents of a multiple document job if the Create-Job operation had already been accepted. All previouslycreated or submitted Jobs and all Jobs currently processing continue unaffected.The IPP Printer MUST accept the request in any state. The Printersets the value of its "printer-is-accepting-jobs" READ-ONLY PrinterDescription attribute to ’false’ (see [RFC2911], section 4.4.20), no matter what the previous value was. This operation has no immediate or direct effect on the Printer’s "printer-state" and "printer-state-reasons" attributes.Kugler, et al. Standards Track [Page 7]Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911] sections 1 and 8.5).The Disable-Printer Request and Disable-Printer Response have thesame attribute groups and attributes as do the Pause-Printeroperation (see [RFC2911], sections 3.2.7.1 and 3.2.7.2), includingthe new "printer-message-from-operator" operation attribute (seesection 6).3.1.2. Enable-Printer OperationThis OPTIONAL operation allows a client to start the Printer objectaccepting jobs; i.e., it causes the Printer to accept subsequent Job Creation operations. The Printer still accepts all other operations. All previously submitted and currently processing Jobs continueunaffected.The IPP Printer MUST accept the request in any state. The Printersets the value of its "printer-is-accepting-jobs" READ-ONLY PrinterDescription attribute to ’true’ (see [RFC2911], section 4.4.20), nomatter what the previous value was. This operation has no immediate or direct effect on the Printer’s "printer-state" and "printer-state-reasons" attributes.Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911] sections 1 and 8.5).The Enable-Printer Request and Enable-Printer Response have the same attribute groups and attributes as does the Pause-Printer operation(see [RFC2911], sections 3.2.8.1 and 3.2.8.2), including the new"printer-message-from-operator" operation attribute (see section 6).3.2. The Pause and Resume Printer OperationsThis section leaves the OPTIONAL IPP/1.1 Pause-Printer (see[RFC2911], sections 3.2.7) ambiguous as to whether it stops thePrinter immediately or after the current job. It also defines theOPTIONAL Pause-Printer-After-Current-Job operation as following thecurrent job. These operations affect the scheduling of IPP jobs. If either of these Pause Printer operations are supported, then theResume-Printer operation MUST be supported.These operations allow the operator to control whether the Printerwill send new IPP jobs to the associated Output Device(s) that theIPP Printer object represents. These operations have no other effect on the Printer, so the Printer continues to accept all operations. Kugler, et al. Standards Track [Page 8]In other words, these operations control the "output of new jobs" to the Output Device(s), and the Disable and Enable Printer Operations(see section 3.1) independently control the "input of new jobs" tothe IPP Printer.Table 2. Pause and Resume Printer OperationsPause and Resume Printers Description-------------------------------------------------------------------- IPP/1.1 Pause Printer Stops the IPP Printer from sendingnew IPP Jobs to the Output Device(s)either immediately or after thecurrent job completes, depending onimplementation, as defined in[RFC2911].Pause-Printer-After- Stops the IPP Printer from sendingCurrent-Job new IPP Jobs to the Output Device(s)after the current jobs finish.Resume-Printer Starts the IPP Printer sending IPPJobs to the Output Device again.3.2.1. Pause-Printer-After-Current-Job OperationThis OPTIONAL operation allows a client to stop the Printer objectfrom sending IPP jobs to any of its Output Devices or SubordinatePrinters. If the IPP Printer is in the middle of sending an IPP job to an Output Device or Subordinate Printer, the IPP Printer MUSTcomplete sending that Job. However, after receiving this operation, the IPP Printer MUST NOT send any additional IPP jobs to any of itsOutput Devices or Subordinate Printers. In addition, after havingreceived this operation, the IPP Printer MUST NOT start processingany more jobs, so additional jobs MUST NOT enter the ’processing’state.If the IPP Printer is not sending an IPP Job to the Output Device or Subordinate Printer (whether or not the Output Device or Subordinate Printer is busy processing any jobs), the IPP Printer objecttransitions immediately to the ’stopped’ state by setting its"printer-state" attribute to ’stopped’, removing the ’moving-to-paused’ value, if present, from its "printer-state-reasons"attribute, and adding the ’paused’ value to its "printer-state-reasons" attribute.If the implementation will take appreciable time to complete sending an IPP job that it has started sending to an Output Device orSubordinate Printer, the IPP Printer adds the ’moving-to-paused’Kugler, et al. Standards Track [Page 9]value to the Printer object’s "printer-state-reasons" attribute (see section [RFC2911], 4.4.12). When the IPP Printer has completedsending IPP jobs that it was in the process of sending, the Printerobject transitions to the ’stopped’ state by setting its "printer-state" attribute to ’stopped’, removing the ’moving-to-paused’ value, if present, from its "printer-state-reasons" attribute, and addingthe ’paused’ value to its "printer-state-reasons" attribute.This operation MUST NOT affect the acceptance of Job Creationrequests (see Disable-Printer Operation, section 3.1.1).For any jobs that are ’pending’ or ’pending-held’, the ’printer-stopped’ values of the jobs’ "job-state-reasons" attribute alsoapply. However, the IPP Printer NEED NOT update those jobs’ "job-state-reasons" attributes and only have to return the ’printer-stopped’ value when those jobs are queried by using the Get-Job-Attributes or Get-Jobs operations (so-called "lazy evaluation").The IPP Printer MUST accept the request in any state and transitionthe Printer to the indicated new "printer-state", and it MUST add the indicated value to "printer-state-reasons" attribute before returning as follows:Table 3. State Transition Table for Pause-Printer-After-Current-Job OperationCurrent New "printer IPP Printer’s response status"printer- "printer- -state- code and action (REQUIRED/state" state" reasons" OPTIONAL state transition fora Printer to support):--------------------------------------------------------------------’idle’ ’stopped’ ’paused’ REQUIRED: ’successful-ok’’processing’ ’processing’ ’moving- OPTIONAL: ’successful-ok’;to- Later, when the IPP Printerpaused’ has finished sending IPP jobsto an Output Device, the"printer-state" becomes’stopped’, and the ’paused’value replaces the ’moving-to-paused’ value in the "printer-state-reasons" attribute’processing’ ’stopped’ ’paused’ REQUIRED: ’successful-ok’;the IPP Printer wasn’t in themiddle of sending an IPP jobto an Output DeviceKugler, et al. Standards Track [Page 10]’stopped’ ’stopped’ ’paused’ REQUIRED: ’successful-ok’Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).The Pause-Printer-After-Current-Job Request and Pause-Printer-After- Current-Job Response have the same attribute groups and attributes as does the Pause-Printer operation (see [RFC2911], sections 3.2.7.1 and 3.2.7.2), including the new "printer-message-from-operator" operation attribute (see section 6).3.3. Hold and Release New Jobs OperationsThis section defines operations to condition the Printer to hold any new jobs and to release them.3.3.1. Hold-New-Jobs OperationThis OPTIONAL operation allows a client to condition the Printer tocomplete the current ’pending’ and ’processing’ IPP Jobs but not tostart processing any subsequently created IPP Jobs. If the IPPPrinter is in the middle of sending an IPP job to an Output Device or Subordinate Printer, the IPP Printer MUST complete sending that Job. Furthermore, the IPP Printer MUST send all of the current ’pending’IPP Jobs to the Output Device(s) or Subordinate IPP Printerobject(s). Any subsequently received Job Creation operations willcause the IPP Printer to put the Job into the ’pending-held’ state,with the ’job-held-on-create’ value being added to the job’s "job-state-reasons" attribute. Thus all newly accepted jobs will beautomatically held by the Printer.When the Printer completes all the ’pending’ and ’processing’ jobs,it enters the ’idle’ state as usual. An operator monitoring Printer state changes will know when the Printer has completed all currentjobs because the Printer enters the ’idle’ state.This operation MUST NOT affect the acceptance of Job Creationrequests (see Disable-Printer Operation, section 3.1.1), except toput the Jobs into the ’pending-held’ state, instead of the ’pending’ or ’processing’ state.The IPP Printer MUST accept the request in any state, MUST NOTtransition the Printer to any other "printer-state", and MUST add the ’hold-new-jobs’ value to the Printer’s "printer-state-reasons"attribute (whether the value was present or not).Kugler, et al. Standards Track [Page 11]Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).The Hold-New-Jobs Request and Hold-New-Jobs Response have the sameattribute groups and attributes as does the Pause-Printer operation(see [RFC2911], sections 3.2.7.1 and 3.2.7.2), including the new"printer-message-from-operator" operation attribute (see section 6).3.3.2. Release-Held-New-Jobs OperationThis OPTIONAL operation allows a client to undo the effect of aprevious Hold-New-Jobs operation. In particular, the Printerreleases all the jobs that it held as a consequence of a Hold-New-Jobs operations; i.e., while the ’hold-new-jobs’ value was present in the Printer’s "printer-state-reasons" attribute. In addition, thePrinter MUST accept this request in any state, MUST NOT transitionthe Printer to any other "printer-state", and MUST remove the ’hold- new-jobs’ value from its "printer-state-reasons" attribute (whetherthe value was present or not) so that the Printer no longer holdsnewly created jobs.Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).The Release-Held-New-Jobs Request and Release-Held-New-Jobs Response have the same attribute groups and attributes as the Pause-Printeroperation (see [RFC2911], sections 3.2.7.1 and 3.2.7.2), includingthe new "printer-message-from-operator" operation attribute (seesection 6).3.4. Deactivate and Activate Printer OperationsThis section defines the OPTIONAL Deactivate-Printer and Activate-Printer operations that stop and start the IPP Printer object fromaccepting all requests except queries and performing work. If either of these operations are supported, both MUST be supported.These operations allow the operator to put the Printer into a dormant read-only condition and to take it out of this condition.Kugler, et al. Standards Track [Page 12]3.4.1. Deactivate-Printer OperationThis OPTIONAL operation allows a client to stop the Printer objectfrom sending IPP jobs to any of its Output Devices or SubordinatePrinters (Pause-Printer-After-Current-Job) and to stop the Printerobject from accepting any requests but query requests. The Printerperforms a Disable-Printer and a Pause-Printer-After-Current-Joboperation immediately. If these two operations cannot be completedimmediately, it includes use of all of the "printer-state-reasons".In addition, the Printer MUST immediately reject all requests, except for Activate-Printer, queries (Get-Printer-Attributes, Get-Job-Attributes, Get-Jobs, etc.), Send-Document, and Send-URI (so thatpartial job submission can be completed, see section 3.1.1). ThePrinter MUST then return the ’server-error-service-unavailable’status code.The IPP Printer MUST accept the request in any state. Immediately,the Printer MUST set the ’deactivated’ value in its "printer-state-reasons" attribute. Note: neither the Disable-Printer nor thePause-Printer-After-Current-Job set the ’deactivated’ value.Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).The Deactivate-Printer Request and Deactivate-Printer Response havethe same attribute groups and attributes as does the Pause-Printeroperation (see [RFC2911], sections 3.2.7.1 and 3.2.7.2), includingthe new "printer-message-from-operator" operation attribute (seesection 6).3.4.2. Activate-Printer OperationThis OPTIONAL operation allows a client to undo the effects of theDeactivate-Printer; i.e., it allows the Printer object to startsending IPP jobs to any of its Output Devices or Subordinate Printers (Pause-Printer-After-Current-Job) and starts the Printer object from accepting any requests. The Printer performs an Enable-Printer and a Resume-Printer operation immediately. In addition, the Printer MUST immediately start accepting all requests.The IPP Printer MUST accept the request in any state. The PrinterMUST immediately remove the ’deactivated’ value from its "printer-state-reasons" attribute (whether it is present or not).Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).Kugler, et al. Standards Track [Page 13]The Activate-Printer Request and Activate-Printer Response have thesame attribute groups and attributes as the Pause-Printer operation(see [RFC2911], sections 3.2.7.1 and 3.2.7.2), including the new"printer-message-from-operator" operation attribute (see section 6).3.5. Restart-Printer, Shutdown-Printer, and Startup-Printer Operations This section defines the OPTIONAL Restart-Printer, Shutdown-Printer, and Startup-Printer operations that initialize, shutdown, and startup the Printer object, respectively. Each of these operations isOPTIONAL, and any combination MAY be supported.3.5.1. Restart-Printer OperationThis OPTIONAL operation allows a client to restart a Printer objectwhose operation is in need of initialization because of incorrect or erratic behavior; i.e., perform the effect of a software re-boot.The implementation MUST attempt to save any information about Jobsand the Printer object before re-initializing. However, thisoperation MAY have drastic consequences on the running system, so the client SHOULD first try the Deactivate-Printer operation to minimize the effect on the current state of the system. The effects ofprevious Disable-Printer, Pause Printer, and Deactivate-Printeroperations are lost.The IPP Printer MUST accept the request in any state. The Printerobject MUST initialize its Printer’s "printer-state" to ’idle’,remove the state reasons from its "printer-state-reasons" attribute, and change its "printer-is-accepting-jobs" attribute to ’true’.Access Rights: The authenticated user (see [RFC2911], section 8.3)performing this operation must be an operator or administrator of the Printer object (see [RFC2911], sections 1 and 8.5).The Restart-Printer Request and Restart-Printer Response have thesame attribute groups and attributes as does the Pause-Printeroperation (see [RFC2911], sections 3.2.8.1 and 3.2.8.2), includingthe new "printer-message-from-operator" operation attribute (seesection 6).3.5.2. Shutdown-Printer OperationThis OPTIONAL operation allows a client to shutdown a Printer; i.e., to stop processing jobs without losing any jobs and to make thePrinter object unavailable for any operations using the IPP protocol. There is no way to bring the instance of the Printer object back tobeing used, except for the Startup-Printer (see section 3.5.3), which starts up a new instance of the Printer object for hostedKugler, et al. Standards Track [Page 14]。