RFC 3510: Internet Printing Protocol/1.1: IPP URL Scheme 中文翻译

URL : https://datatracker.ietf.org/doc/html/rfc3510
标题 : RFC 3510
翻译类型 : 自动生成

Network Working Group                                         R. Herriot
Request for Comments: 3510                                   I. McDonald
Updates: 2910                                            High North Inc.
Category: Standards Track                                     April 2003

Network Working Group                                         R. Herriot
Request for Comments: 3510                                   I. McDonald
Updates: 2910                                            High North Inc.
Category: Standards Track                                     April 2003

Internet Printing Protocol/1.1: IPP URL Scheme

Internet打印协议/1.1:IPP URL方案

Status of this Memo

本备忘录的状况

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。

版权公告

Abstract

摘要

This memo defines the "ipp" URL (Uniform Resource Locator) scheme. This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910. An "ipp" URL is used to specify the network location of a print service that supports the IPP Protocol (RFC 2910), or of a network resource (for example, a print job) managed by such a print service.

本备忘录定义了“ipp”URL（统一资源定位器）方案。本备忘录通过扩展和澄清RFC 2910第5节“IPP URL方案”，更新了IPP/1.1：编码和传输（RFC 2910）。“ipp”URL用于指定支持ipp协议（RFC 2910）的打印服务或由此类打印服务管理的网络资源（例如打印作业）的网络位置。

Table of Contents

   1.  Introduction ...............................................  2
   2.  Terminology ................................................  3
       2.1.  Conformance Terminology ..............................  3
       2.2.  Model Terminology ....................................  3
   3.  IPP Model for Printers and Jobs ............................  3
   4.  IPP URL Scheme .............................................  4
       4.1.  IPP URL Scheme Applicability .........................  4
       4.2.  IPP URL Scheme Associated Port .......................  4
       4.3.  IPP URL Scheme Associated MIME Type ..................  5
       4.4.  IPP URL Scheme Character Encoding ....................  5
       4.5.  IPP URL Scheme Syntax ................................  5
       4.6.  IPP URL Examples .....................................  6
             4.6.1.  IPP Printer URL Examples .....................  6
             4.6.2.  IPP Job URL Examples .........................  6
       4.7.  IPP URL Comparisons ..................................  7

   1.  Introduction ...............................................  2
   2.  Terminology ................................................  3
       2.1.  Conformance Terminology ..............................  3
       2.2.  Model Terminology ....................................  3
   3.  IPP Model for Printers and Jobs ............................  3
   4.  IPP URL Scheme .............................................  4
       4.1.  IPP URL Scheme Applicability .........................  4
       4.2.  IPP URL Scheme Associated Port .......................  4
       4.3.  IPP URL Scheme Associated MIME Type ..................  5
       4.4.  IPP URL Scheme Character Encoding ....................  5
       4.5.  IPP URL Scheme Syntax ................................  5
       4.6.  IPP URL Examples .....................................  6
             4.6.1.  IPP Printer URL Examples .....................  6
             4.6.2.  IPP Job URL Examples .........................  6
       4.7.  IPP URL Comparisons ..................................  7

   5.  Conformance Requirements ...................................  8
       5.1.  IPP Client Conformance Requirements ..................  8
       5.2.  IPP Printer Conformance Requirements .................  8
   6.  IANA Considerations ........................................  9
   7.  Internationalization Considerations ........................  9
   8.  Security Considerations ....................................  9
   9.  Intellectual Property Rights ............................... 10
   10. Normative References ....................................... 11
   11. Informative References ..................................... 11
   12. Acknowledgments ............................................ 12
   Appendix A - Registration of "ipp" URL Scheme .................. 13
   Authors' Addresses ............................................. 15
   Full Copyright Statement ....................................... 16

   5.  Conformance Requirements ...................................  8
       5.1.  IPP Client Conformance Requirements ..................  8
       5.2.  IPP Printer Conformance Requirements .................  8
   6.  IANA Considerations ........................................  9
   7.  Internationalization Considerations ........................  9
   8.  Security Considerations ....................................  9
   9.  Intellectual Property Rights ............................... 10
   10. Normative References ....................................... 11
   11. Informative References ..................................... 11
   12. Acknowledgments ............................................ 12
   Appendix A - Registration of "ipp" URL Scheme .................. 13
   Authors' Addresses ............................................. 15
   Full Copyright Statement ....................................... 16

1. Introduction

1. 介绍

This memo conforms to all of the requirements in Registration Procedures for URL Scheme Names [RFC2717]. This memo also follows all of the recommendations in Guidelines for new URL Schemes [RFC2718].

本备忘录符合URL方案名称注册程序[RFC2717]中的所有要求。本备忘录还遵循了新URL方案指南[RFC2718]中的所有建议。

See section 1, "Introduction", of [RFC2911] and section 1, "Introduction", of [RFC3196] for overview information about IPP. See section 10, "Description of the Base IPP Documents", of [RFC3196] for a full description of the IPP document set.

有关IPP的概述信息，请参见[RFC2911]第1节“简介”和[RFC3196]第1节“简介”。有关IPP文件集的完整说明，请参见[RFC3196]第10节“基本IPP文件的说明”。

This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910, but does not define any new parameters or other new extensions to the syntax of IPP URLs.

本备忘录通过扩展和澄清RFC 2910第5节“IPP URL方案”，更新了IPP/1.1：编码和传输（RFC 2910），但未定义任何新参数或IPP URL语法的其他新扩展。

The IPP URL scheme defined in this document is based on the ABNF for the HTTP URL scheme defined in HTTP [RFC2616], which in turn is derived from the URI Generic Syntax [RFC2396] and further updated for IPv6 by [RFC2732]. An IPP URL is transformed into an HTTP URL according to the rules specified in section 5 of IPP Protocol [RFC2910].

本文档中定义的IPP URL方案基于HTTP[RFC2616]中定义的HTTP URL方案的ABNF，该方案又源自URI通用语法[RFC2396]，并由[RFC2732]针对IPv6进一步更新。根据IPP协议[RFC2910]第5节规定的规则，将IPP URL转换为HTTP URL。

This document defines IPP URL scheme applicability, associated port (631), associated MIME type ("application/ipp"), character encoding, and syntax.

本文档定义了IPP URL方案的适用性、相关端口（631）、相关MIME类型（“应用程序/IPP”）、字符编码和语法。

This document is laid out as follows:

本文件的内容如下：

- Section 2 defines the terminology used throughout the document.

- 第2节定义了整个文件中使用的术语。

- Section 3 supplies references to the IPP Printer and IPP Job object model defined in IPP Model [RFC2911].

- 第3节提供了IPP模型[RFC2911]中定义的IPP打印机和IPP作业对象模型的参考。

- Section 4 specifies the IPP URL scheme.

- 第4节规定了IPP URL方案。

- Section 5 specifies the conformance requirements for IPP Clients and IPP Printers that claim conformance to this document.

- 第5节规定了声称符合本文件要求的IPP客户和IPP打印机的一致性要求。

- Sections 6, 7, and 8 specify IANA, internationalization, and security considerations.

- 第6、7和8节规定了IANA、国际化和安全注意事项。

- Sections 9, 10, 11, 12, and 13 specify normative references, informative references, acknowledgements, authors' addresses, and full IETF copyright statement.

- Section 14 (Appendix A) is a completed registration template for the IPP URL Scheme (see section 6.0 of [RFC2717]).

- 第14节（附录A）是IPP URL方案的完整注册模板（见[RFC2717]第6.0节）。

2. Terminology

2. 术语

This specification document uses the terminology defined in this section.

本规范文件使用本节中定义的术语。

2.1. Conformance Terminology

2.1. 一致性术语

The uppercase terms "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT" "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. These terms are used to specify conformance requirements for all implementations (both print clients and print services) of this specification.

本文件中大写术语“必须”、“不得”、“必需”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。这些术语用于指定本规范所有实现（打印客户端和打印服务）的一致性要求。

2.2. Model Terminology

2.2. 模型术语

See section 12.2, "Model Terminology", in IPP Model [RFC2911].

参见IPP型号[RFC2911]中的第12.2节“型号术语”。

3. IPP Model for Printers and Jobs

3. 打印机和作业的IPP模型

See section 2, "IPP Objects", section 2.1, "Printer Object", and section 2.2, "Job Object", in [RFC2911] for a full description of the IPP object model and terminology.

有关IPP对象模型和术语的完整说明，请参见[RFC2911]中的第2节“IPP对象”、第2.1节“打印机对象”和第2.2节“作业对象”。

In this document, "IPP Client" means the software (on some hardware platform) that submits, monitors, and/or manages print jobs via the IPP Protocol [RFC2910] to a print spooler, print gateway, or physical printing device.

在本文档中，“IPP客户端”是指（在某些硬件平台上）通过IPP协议[RFC2910]向后台打印程序、打印网关或物理打印设备提交、监控和/或管理打印作业的软件。

In this document, "IPP Printer object" means the software (on some hardware platform) that receives print jobs and/or printer/job operations via the IPP Protocol [RFC2910] from an "IPP Client".

在本文档中，“IPP打印机对象”是指（在某些硬件平台上）通过IPP协议[RFC2910]从“IPP客户端”接收打印作业和/或打印机/作业操作的软件。

In this document, "IPP Printer" is a synonym for "IPP Printer object".

在本文档中，“IPP打印机”是“IPP打印机对象”的同义词。

In this document, "IPP Job object" means the set of attributes and documents for one print job instantiated on an "IPP Printer".

在本文档中，“IPP作业对象”是指在“IPP打印机”上实例化的一个打印作业的一组属性和文档。

In this document, "IPP Job" is a synonym for "IPP Job object".

在本文档中，“IPP作业”是“IPP作业对象”的同义词。

In this document, "IPP URL" means a URL with the "ipp" scheme.

在本文件中，“IPP URL”指带有“IPP”方案的URL。

Note: In this document, "IPP URL" is a synonym for "ipp-URL" (in section 4, "IPP URL Scheme", of this document) and "ipp-URL" (in section 5, "IPP URL Scheme", of [RFC2910]).

注：在本文件中，“IPP URL”是[RFC2910]第4节“IPP URL方案”和第5节“IPP URL方案”的同义词。

4. IPP URL Scheme

4. IPP URL方案

4.1. IPP URL Scheme Applicability

4.1. IPP URL方案的适用性

The "ipp" URL scheme MUST only be used to specify absolute URLs (relative IPP URLs are not allowed) for IPP print services and their associated network resources. The "ipp" URL scheme MUST only be used to specify the use of the abstract protocol defined in IPP Model [RFC2911] over an HTTP [RFC2616] transport, as defined in IPP Protocol [RFC2910]. Any other transport binding for the abstract protocol defined in IPP Model [RFC2911] would require a different URL scheme.

“ipp”URL方案只能用于指定ipp打印服务及其相关网络资源的绝对URL（不允许使用相对ipp URL）。“ipp”URL方案只能用于指定ipp模型[RFC2911]中定义的抽象协议在HTTP[RFC2616]传输上的使用，如ipp协议[RFC2910]中所定义。IPP模型[RFC2911]中定义的抽象协议的任何其他传输绑定都需要不同的URL方案。

The "ipp" URL scheme allows an IPP client to choose an appropriate IPP print service (for example, from a directory). The IPP client can establish an HTTP connection to the specified IPP print service. The IPP client can send IPP protocol requests (for example, a "Print-Job" request) and receive IPP protocol responses over that HTTP connection.

“ipp”URL方案允许ipp客户端选择适当的ipp打印服务（例如，从目录）。IPP客户端可以建立到指定IPP打印服务的HTTP连接。IPP客户端可以发送IPP协议请求（例如，“打印作业”请求）并通过该HTTP连接接收IPP协议响应。

4.2. IPP URL Scheme Associated Port

4.2. IPP URL方案关联端口

All IPP URLs which do NOT explicitly specify a port MUST be resolved to IANA-assigned well-known port 631, as registered in [IANA-PORTREG].

所有未明确指定端口的IPP URL必须解析为IANA分配的已知端口631，如在[IANA-PORTREG]中注册的那样。

See: IANA Port Numbers Registry [IANA-PORTREG]. See: IPP Protocol [RFC2910].

请参阅：IANA端口号注册表[IANA-PORTREG]。见：IPP协议[RFC2910]。

4.3. IPP URL Scheme Associated MIME Type

4.3. IPP URL方案关联的MIME类型

All IPP URLs MUST be used to specify network print services which support the "application/ipp" MIME media type as registered in [IANA-MIMEREG] for IPP protocol requests and responses.

所有IPP URL必须用于指定支持[IANA-MIMEREG]中注册的IPP协议请求和响应的“应用程序/IPP”MIME媒体类型的网络打印服务。

See: IANA MIME Media Types Registry [IANA-MIMEREG]. See: IPP Protocol [RFC2910].

请参阅：IANA MIME媒体类型注册表[IANA-MIMEREG]。见：IPP协议[RFC2910]。

4.4. IPP URL Scheme Character Encoding

4.4. IPP URL方案字符编码

IPP URLs MUST use [RFC2396] encoding, as do their equivalent HTTP URLs. Characters other than those in the "reserved" and "unsafe" sets [RFC2396] are equivalent to their ""%" HEX HEX" encoding.

IPP URL必须使用[RFC2396]编码，其等效HTTP URL也是如此。“保留”和“不安全”集合[RFC2396]中的字符以外的字符等效于其“%”十六进制编码。

4.5. IPP URL Scheme Syntax

4.5. IPP URL方案语法

The abstract protocol defined in IPP Model [RFC2911] places a limit of 1023 octets (NOT characters) on the length of a URI (see section 4.1.5, "uri", in [RFC2911]).

IPP模型[RFC2911]中定义的抽象协议对URI的长度限制为1023个八位字节（非字符）（参见[RFC2911]中的第4.1.5节“URI”）。

Note: IPP Printers ought to be cautious about depending on URI lengths above 255 bytes, because some older client implementations might not properly support these lengths.

注意：IPP打印机在依赖超过255字节的URI长度时应该谨慎，因为一些旧的客户端实现可能无法正确支持这些长度。

IPP URLs MUST be represented in absolute form. Absolute URLs MUST always begin with a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics" [RFC2396]. This specification adopts the definitions of "host", "port", "abs_path", and "query" from [RFC2396], as updated for IPv6 by [RFC2732].

IPP URL必须以绝对形式表示。绝对URL必须始终以方案名称开头，后跟冒号。有关URL语法和语义的详细信息，请参阅“统一资源标识符（URI）：通用语法和语义”[RFC2396]。本规范采用[RFC2396]中“主机”、“端口”、“abs_路径”和“查询”的定义，并由[RFC2732]针对IPv6进行了更新。

The IPP URL scheme syntax in ABNF is as follows:

ABNF中的IPP URL方案语法如下：

   ipp-URL = "ipp:" "//" host [ ":" port ] [ abs_path [ "?" query ]]

   ipp-URL = "ipp:" "//" host [ ":" port ] [ abs_path [ "?" query ]]

If the port is empty or not given, port 631 is assumed. The semantics are that the identified resource (see section 5.1.2 of [RFC2616]) is located at the IPP print service listening for HTTP connections on that port of that host, and the Request-URI for the identified resource is 'abs_path'.

如果端口为空或未给定，则假定端口631。语义是标识的资源（参见[RFC2616]第5.1.2节）位于IPP打印服务上，侦听该主机端口上的HTTP连接，标识的资源的请求URI为“abs_path”。

If the 'abs_path' is not present in the URL, it MUST be given as "/" when used as a Request-URI for a resource (see section 5.1.2 of [RFC2616]).

如果URL中不存在“abs_path”，则当用作资源的请求URI时，必须将其指定为“/”（请参见[RFC2616]第5.1.2节）。

4.6. IPP URL Examples

4.6. IPP URL示例

Note: Literal IPv4 or IPv6 addresses SHOULD NOT be used in IPP URLs.

注意：IPP URL中不应使用文字IPv4或IPv6地址。

4.6.1. IPP Printer URL Examples

4.6.1. IPP打印机URL示例

The following are examples of well-formed IPP URLs for IPP Printers (for example, to be used as protocol elements in 'printer-uri' operation attributes of 'Print-Job' request messages):

以下是IPP打印机格式良好的IPP URL示例（例如，用作“打印作业”请求消息的“打印机uri”操作属性中的协议元素）：

      ipp://example.com
      ipp://example.com/printer
      ipp://example.com/printer/tiger
      ipp://example.com/printer/fox
      ipp://example.com/printer/tiger/bob
      ipp://example.com/printer/tiger/ira

      ipp://example.com
      ipp://example.com/printer
      ipp://example.com/printer/tiger
      ipp://example.com/printer/fox
      ipp://example.com/printer/tiger/bob
      ipp://example.com/printer/tiger/ira

Each of the above URLs are well-formed URLs for IPP Printers and each would reference a logically different IPP Printer, even though some of those IPP Printers might share the same host system. The 'bob' or 'ira' last path components might represent two different physical printer devices, while 'tiger' might represent some grouping of IPP Printers (for example, a load-balancing spooler). Or the 'bob' and 'ira' last path components might represent separate human recipients on the same physical printer device (for example, a physical printer supporting two job queues). In either case, both 'bob' and 'ira' would behave as different and independent IPP Printers.

以上每个URL都是IPP打印机的格式良好的URL，每个URL都引用逻辑上不同的IPP打印机，即使其中一些IPP打印机可能共享同一主机系统。“bob”或“ira”最后路径组件可能表示两个不同的物理打印机设备，而“tiger”可能表示IPP打印机的某些分组（例如，负载平衡后台处理程序）。或者，“bob”和“ira”最后路径组件可能表示同一物理打印机设备上的不同人工收件人（例如，支持两个作业队列的物理打印机）。在任何一种情况下，“bob”和“ira”都将表现为不同的独立IPP打印机。

The following are examples of well-formed IPP URLs for IPP Printers with (optional) ports and paths:

以下是具有（可选）端口和路径的IPP打印机的格式良好的IPP URL示例：

      ipp://example.com
      ipp://example.com/~smith/printer
      ipp://example.com:631/~smith/printer

      ipp://example.com
      ipp://example.com/~smith/printer
      ipp://example.com:631/~smith/printer

The first and second IPP URLs above MUST be resolved to port 631 (IANA assigned well-known port for IPP). The second and third IPP URLs above are equivalent (see section 4.7 below).

以上第一个和第二个IPP URL必须解析为端口631（IANA为IPP分配的已知端口）。上述第二个和第三个IPP URL是等效的（见下文第4.7节）。

4.6.2. IPP Job URL Examples

4.6.2. IPP作业URL示例

The following are examples of well-formed IPP URLs for IPP Jobs (for example, to be used as protocol elements in 'job-uri' attributes of 'Print-Job' response messages):

以下是IPP作业的格式良好的IPP URL示例（例如，用作“打印作业”响应消息的“作业uri”属性中的协议元素）：

      ipp://example.com/printer/123
      ipp://example.com/printer/tiger/job123

      ipp://example.com/printer/123
      ipp://example.com/printer/tiger/job123

IPP Job URLs are valid and meaningful only until Job completion and possibly an implementation defined optional period of persistence after Job completion (see IPP Model [RFC2911]).

IPP作业URL仅在作业完成之前有效且有意义，并且可能在作业完成后有一个实现定义的可选持久期（请参阅IPP模型[RFC2911]）。

Ambiguously, section 4.3.1 'job-uri' of IPP Model [RFC2911] states that:

IPP模型[RFC2911]第4.3.1节“作业uri”含糊不清地指出：

"the precise format of a Job URI is implementation dependent."

“作业URI的精确格式取决于实现。”

Thus, the relationship between the value of the "printer-uri" operation attribute used in a 'Print-Job' request and the value of the "job-uri" attribute returned in the corresponding 'Print-Job' response is implementation dependent. Also, section 4.3.3 'job-printer-uri' of IPP Model [RFC2911] states that the 'job-printer-uri' attribute of a Job object:

因此，“打印作业”请求中使用的“打印机uri”操作属性的值与相应的“打印作业”响应中返回的“作业uri”属性的值之间的关系取决于实现。此外，IPP型号[RFC2911]第4.3.3节“作业打印机uri”规定作业对象的“作业打印机uri”属性：

"permits a client to identify the Printer object that created this Job object when only the Job object's URI is available to the client."

“当客户端只有作业对象的URI可用时，允许客户端识别创建此作业对象的打印机对象。”

However, the above statement is false, because the transform from an IPP Job URL to the corresponding IPP Printer URL is unspecified in either IPP Model [RFC2911] or IPP Protocol [RFC2910].

但是，上述陈述是错误的，因为IPP型号[RFC2911]或IPP协议[RFC2910]中未指定从IPP作业URL到相应IPP打印机URL的转换。

IPP Printers that conform to this specification SHOULD only generate IPP Job URLs (for example, in the "job-uri" attribute in a 'Print-Job' response) by appending exactly one path component to the corresponding IPP Printer URL (for interoperability).

符合此规范的IPP打印机应仅通过将一个路径组件添加到相应的IPP打印机URL（用于互操作性）来生成IPP作业URL（例如，在“打印作业”响应的“作业uri”属性中）。

4.7. IPP URL Comparisons

4.7. IPP URL比较

When comparing two IPP URLs to decide if they match or not, an IPP Client MUST use the same rules as those defined for HTTP URI comparisons in [RFC2616], with the sole following exception:

当比较两个IPP URL以确定它们是否匹配时，IPP客户端必须使用与[RFC2616]中为HTTP URI比较定义的规则相同的规则，唯一的例外是：

- A port that is empty or not given MUST be treated as equivalent to the well-known port for that IPP URL (port 631);

- 空的或未给定的端口必须被视为与该IPP URL的已知端口（端口631）等效；

See: Section 3.2.3, "URI Comparison", in [RFC2616].

参见[RFC2616]中的第3.2.3节“URI比较”。

5. Conformance Requirements

5. 一致性要求

5.1. IPP Client Conformance Requirements

5.1. IPP客户一致性要求

IPP Clients that conform to this specification:

符合本规范的IPP客户机：

a) MUST only send IPP protocol connections to the port specified in each given IPP URL (if present) or otherwise to IANA assigned well-known port 631;

a) 必须仅将IPP协议连接发送到每个给定IPP URL（如果存在）中指定的端口，或以其他方式发送到IANA分配的已知端口631；

b) MUST only send IPP URLs used as protocol elements in outgoing IPP protocol request messages (for example, in the "printer-uri" operation attribute in a 'Print-Job' request) that conform to the ABNF specified in section 4.5, "IPP URL Scheme Syntax, of this document;

b) 必须仅发送符合本文件第4.5节“IPP URL方案语法”中规定的ABNF的IPP URL，作为传出IPP协议请求消息中的协议元素（例如，“打印作业”请求中的“打印机uri”操作属性）；

c) MUST only convert IPP URLs to their corresponding HTTP URL forms according to the rules in section 5, "IPP URL Scheme", in [RFC2910].

c) 只能根据[RFC2910]第5节“IPP URL方案”中的规则将IPP URL转换为相应的HTTP URL格式。

5.2. IPP Printer Conformance Requirements

5.2. IPP打印机一致性要求

IPP Printers that conform to this specification:

符合本规范的IPP打印机：

a) MUST listen for incoming IPP protocol connections on IANA-assigned well-known port 631, unless explicitly configured by system administrators or site policies;

a) 除非系统管理员或站点策略明确配置，否则必须侦听IANA分配的已知端口631上的传入IPP协议连接；

b) SHOULD NOT listen for incoming IPP protocol connections on any other port, unless explicitly configured by system administrators or site policies;

b) 除非系统管理员或站点策略明确配置，否则不应侦听任何其他端口上的传入IPP协议连接；

c) SHOULD only accept IPP URLs used as protocol elements in incoming IPP protocol request messages (for example, in the "printer-uri" operation attribute in a 'Print-Job' request) that conform to the ABNF specified in section 4.5, "IPP URL Scheme Syntax", of this document;

c) 应仅接受IPP URL作为传入IPP协议请求消息（例如，“打印作业”请求中的“打印机uri”操作属性）中的协议元素，并符合本文件第4.5节“IPP URL方案语法”中规定的ABNF；

d) SHOULD only send IPP URLs used as protocol elements in outgoing IPP protocol response messages (for example, in the "job-uri" attribute in a 'Print-Job' response) that conform to the ABNF specified in section 4.5, "IPP URL Scheme Syntax", of this document;

d) 应仅发送符合本文件第4.5节“IPP URL方案语法”中规定的ABNF的IPP URL作为传出IPP协议响应消息中的协议元素（例如，“打印作业”响应中的“作业uri”属性）；

e) SHOULD only generate IPP Job URLs (for example, in the "job-uri" attribute in a 'Print-Job' response) by appending exactly one path component to the corresponding IPP Printer URL (for interoperability);

e) 应仅通过将一个路径组件添加到相应的IPP打印机URL（用于互操作性）来生成IPP作业URL（例如，“打印作业”响应中的“作业uri”属性）；

f) SHOULD NOT use literal IPv6 or IPv4 addresses in configured or locally generated IPP URLs.

f) 在配置的或本地生成的IPP URL中不应使用文字IPv6或IPv4地址。

6. IANA Considerations

6. IANA考虑

This IPP URL Scheme specification does not introduce any additional IANA considerations, beyond those described in [RFC2910] and [RFC2911].

除[RFC2910]和[RFC2911]中所述内容外，本IPP URL方案规范未引入任何其他IANA注意事项。

See: Section 6, "IANA Considerations" in [RFC2910] See: Section 6, "IANA Considerations" in [RFC2911].

参见[RFC2910]中的第6节“IANA注意事项”，参见[RFC2911]中的第6节“IANA注意事项”。

7. Internationalization Considerations

7. 国际化考虑

This IPP URL Scheme specification does not introduce any additional internationalization considerations, beyond those described in [RFC2910] and [RFC2911].

除了[RFC2910]和[RFC2911]中所述的国际化注意事项外，本IPP URL方案规范未引入任何其他国际化注意事项。

See: Section 7, "Internationalization Considerations", in [RFC2910]. See: Section 7, "Internationalization Considerations", in [RFC2911].

参见[RFC2910]中的第7节“国际化注意事项”。参见[RFC2911]中的第7节“国际化注意事项”。

8. Security Considerations

8. 安全考虑

This IPP URL Scheme specification does not introduce any additional security considerations, beyond those described in [RFC2910] and [RFC2911], except the following:

除[RFC2910]和[RFC2911]中所述的安全注意事项外，本IPP URL方案规范未引入任何其他安全注意事项，以下情况除外：

a) An IPP URL might be faked to point to a rogue IPP print service, thus collecting confidential document contents from IPP clients. Server authentication mechanisms and security mechanisms specified in the IPP Protocol [RFC2910] are sufficient to address this threat.

a) IPP URL可能被伪造为指向恶意IPP打印服务，从而从IPP客户端收集机密文档内容。IPP协议[RFC2910]中指定的服务器身份验证机制和安全机制足以解决此威胁。

b) An IPP URL might be used to access an IPP print service by an unauthorized IPP client. Client authentication mechanisms and security mechanisms specified in the IPP Protocol [RFC2910] are sufficient to address this threat.

b) 未经授权的IPP客户端可能会使用IPP URL访问IPP打印服务。IPP协议[RFC2910]中规定的客户端身份验证机制和安全机制足以解决此威胁。

c) An IPP URL might be used to access an IPP print service at a print protocol application layer gateway (for example, an IPP to LPD gateway [RFC2569]) causing silent compromise of IPP security mechanisms. There is no practical defense against this threat by a client system. System administrators should avoid such compromising configurations.

c) IPP URL可用于访问打印协议应用层网关（例如，IPP到LPD网关[RFC2569]）上的IPP打印服务，从而导致IPP安全机制的无声泄漏。客户端系统没有针对这种威胁的实际防御措施。系统管理员应避免此类破坏性配置。

d) An IPP URL does not have parameters to specify the required client authentication mechanism (for example, 'certificate' as defined in section 4.4.2, "uri-authentication-supported", of IPP Model

d) IPP URL没有参数来指定所需的客户端身份验证机制（例如，IPP模型第4.4.2节“支持的uri身份验证”中定义的“证书”）

[RFC2911]) and required security mechanism (for example, 'tls' as defined in section 4.4.3, "uri-security-supported", of IPP Model [RFC2911]). Service discovery or directory protocols might be used to discover the required client authentication and security mechanisms associated with given IPP URLs.

[RFC2911]）和所需的安全机制（例如，IPP型号[RFC2911]第4.4.3节“支持的uri安全性”中定义的“tls”）。服务发现或目录协议可用于发现与给定IPP URL关联的所需客户端身份验证和安全机制。

Historical Note: During the development of this document, consideration was given to the addition of standard IPP URL parameters for the client authentication and security mechanisms. However, based on a strong IETF IPP Working Group consensus, no parameters were added to the "ipp" URL scheme as originally defined in IPP Protocol [RFC2910] in September 2000, for reasons of backwards compatibility with the many currently shipping implementations of IPP/1.1.

历史注释：在本文档的开发过程中，考虑了为客户端身份验证和安全机制添加标准IPP URL参数。然而，基于IETF IPP工作组的强烈共识，2000年9月，IPP协议[RFC2910]中最初定义的“IPP”URL方案未添加任何参数，原因是与IPP/1.1的许多当前装运实现向后兼容。

See: Section 8, "Security Considerations", in [RFC2910]. See: Section 8, "Security Considerations", in [RFC2911].

见[RFC2910]第8节“安全注意事项”。参见[RFC2911]中的第8节“安全注意事项”。

9. Intellectual Property Rights

9. 知识产权

The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.

IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。

10. Normative References

10. 规范性引用文件

[RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.

[RFC2234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。

[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

[RFC2396]Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。

[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。

[RFC2732] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal IPv6 Addresses in URL's", RFC 2732, December 1999.

[RFC2732]Hinden，R.，Carpenter，B.和L.Masinter，“URL中文字IPv6地址的格式”，RFC 2732，1999年12月。

[RFC2910] Herriot, R., Butler, S., Moore, P., Turner, R. and J. Wenn, "IPP/1.1 Encoding and Transport [IPP Protocol]", RFC 2910, September 2000.

[RFC2910]Herriot，R.，Butler，S.，Moore，P.，Turner，R.和J.Wenn，“IPP/1.1编码和传输[IPP协议]”，RFC 29102000年9月。

[RFC2911] Hastings, T., Herriot, R., deBry, R., Isaacson, S. and P. Powell, "IPP/1.1 Model and Semantics [IPP Model]", RFC 2911, September 2000.

[RFC2911]黑斯廷斯，T.，赫里奥特，R.，德布雷，R.，艾萨克森，S.和P.鲍威尔，“IPP/1.1模型和语义[IPP模型]”，RFC 29112000年9月。

[US-ASCII] Coded Character Set -- 7-bit American Standard Code for Information Interchange, ANSI X3.4-1986.

[US-ASCII]编码字符集——信息交换用7位美国标准代码，ANSI X3.4-1986。

11. Informative References

11. 资料性引用

[IANA-MIMEREG] IANA MIME Media Types Registry. ftp://ftp.iana.org/in-notes/iana/assignments/media-types/...

[IANA-MIMEREG]IANA MIME媒体类型注册表。ftp://ftp.iana.org/in-notes/iana/assignments/media-types/...

   [IANA-PORTREG] IANA Port Numbers Registry. ftp://ftp.iana.org/in-
                  notes/iana/assignments/port-numbers

   [IANA-PORTREG] IANA Port Numbers Registry. ftp://ftp.iana.org/in-
                  notes/iana/assignments/port-numbers

[RFC2569] Herriot, R., Hastings, T., Jacobs, N. and J. Martin, "Mapping between LPD and IPP Protocols", RFC 2569, April 1999.

[RFC2569]Herriot，R.，Hastings，T.，Jacobs，N.和J.Martin，“LPD和IPP协议之间的映射”，RFC 2569，1999年4月。

[RFC2717] Petke, R. and I. King, "Registration Procedures for URL Scheme Names", RFC 2717, November 1999.

[RFC2717]Petke，R.和I.King，“URL方案名称的注册程序”，RFC 2717，1999年11月。

[RFC2718] Masinter, L., Alvestrand, H., Zigmond, D. and R. Petke, "Guidelines for new URL Schemes", RFC 2718, November 1999.

[RFC2718]Masinter，L.，Alvestrand，H.，Zigmond，D.和R.Petke，“新URL方案指南”，RFC 27181999年11月。

[RFC3196] Hastings, T., Manros, C., Zehler, P., Kugler, C. and H. Holst, "Internet Printing Protocol/1.1: Implementor's Guide", RFC 3196, November 2001.

[RFC3196]Hastings，T.，Manros，C.，Zehler，P.，Kugler，C.和H.Holst，“互联网打印协议/1.1：实施者指南”，RFC 31962001年11月。

12. Acknowledgments

12. 致谢

This document is a product of the Internet Printing Protocol Working Group of the Internet Engineering Task Force (IETF).

本文件是互联网工程任务组（IETF）互联网打印协议工作组的产品。

Thanks to Pat Fleming (IBM), Tom Hastings (Xerox), Harry Lewis (IBM), Hugo Parra (Novell), Don Wright (Lexmark), and all the members of the IETF IPP WG.

感谢Pat Fleming（IBM）、Tom Hastings（Xerox）、Harry Lewis（IBM）、Hugo Parra（Novell）、Don Wright（Lexmark）和IETF IPP工作组的所有成员。

Section 5, "IPP URL Scheme", in IPP Protocol [RFC2910] was the primary input to this IPP URL Scheme specification.

IPP协议[RFC2910]中的第5节“IPP URL方案”是本IPP URL方案规范的主要输入。

Appendix A - Registration of "ipp" URL Scheme

附录A-注册“ipp”URL方案

Note: The following registration obsoletes section 5, "IPP URL Scheme", of IPP Protocol [RFC2911].

注：以下注册废除IPP协议[RFC2911]第5节“IPP URL方案”。

URL Scheme Name: ipp

URL方案名称：ipp

URL Scheme Syntax:

URL方案语法：

      ipp-URL = "ipp:" "//" host [ ":" port ] [ abs_path [ "?" query ]]

      ipp-URL = "ipp:" "//" host [ ":" port ] [ abs_path [ "?" query ]]

Character Encoding Considerations:

字符编码注意事项：

IPP URLs MUST use [RFC2396] encoding, as do their equivalent HTTP URLs. Characters other than those in the "reserved" and "unsafe" sets [RFC2396] are equivalent to their ""%" HEX HEX" encoding.

IPP URL必须使用[RFC2396]编码，其等效HTTP URL也是如此。“保留”和“不安全”集合[RFC2396]中的字符以外的字符等效于其“%”十六进制编码。

Intended Usage:

预期用途：

The intended usage of the "ipp" URL scheme is COMMON.

“ipp”URL方案的预期用途很常见。

An "ipp" URL is used to specify the network location of a print service that supports the IPP Protocol [RFC2910], or of a network resource (for example, a print job) managed by such a print service. An IPP client can choose to establish an HTTP connection to the specified print service for transmission of IPP protocol requests (for example, IPP print job submission requests).

“ipp”URL用于指定支持ipp协议[RFC2910]的打印服务或由此类打印服务管理的网络资源（例如打印作业）的网络位置。IPP客户端可以选择建立到指定打印服务的HTTP连接，以传输IPP协议请求（例如，IPP打印作业提交请求）。

Applications or Protocols which use this URL scheme:

使用此URL方案的应用程序或协议：

See: Section 5, "IPP URL Scheme", in IPP Protocol [RFC2910].

参见IPP协议[RFC2910]第5节“IPP URL方案”。

Interoperability Considerations:

互操作性注意事项：

See: Section 9, "Interoperability with IPP/1.0 Implementations", in IPP Protocol [RFC2910].

参见IPP协议[RFC2910]第9节“与IPP/1.0实现的互操作性”。

Security Considerations:

安全考虑：

See: Section 8, "Security Considerations", in IPP Protocol [RFC2910].

见：IPP协议[RFC2910]第8节“安全注意事项”。

Relevant Publications: