draft-ietf-ipp-install-02.txt   draft-ietf-ipp-install-03.txt 
INTERNET-DRAFT INTERNET-DRAFT
<draft-ietf-ipp-install-02.txt> <draft-ietf-ipp-install-03.txt>
[Target category: standards track] Hugo Parra [Target category: standards track] Hugo Parra
Novell, Inc. Novell, Inc.
Ted Tronson Ted Tronson
Novell, Inc. Novell, Inc.
Tom Hastings Tom Hastings
Xerox Corp. Xerox Corp.
February 28, 2001 April 5, 2001
Internet Printing Protocol (IPP): Internet Printing Protocol (IPP):
Printer Installation Extension Printer Installation Extension
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [RFC2026]. Internet-Drafts are all provisions of Section 10 of [RFC2026]. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
skipping to change at page 1, line 38 skipping to change at page 1, line 38
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed as The list of Internet-Draft Shadow Directories can be accessed as
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document describes an extension to the Internet Printing
Protocol/1.0 (IPP) [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910].
Various client platforms require that some setting up take place at Various client platforms require that some setting up take place at
the workstation before the client can properly submit jobs to a the workstation before the client can properly submit jobs to a
specific printer. This setup process is sometimes referred to as specific printer. This setup process is sometimes referred to as
printer installation. Most clients need some information about the printer installation. Most clients need some information about the
printer being installed as well as support files to complete the printer being installed as well as support files to complete the
printer installation. The nature of the support files varies printer installation. The nature of these "Client Print Support
depending on the specific client platform, from simple configuration Files" varies depending on the specific client platform, from simple
files to highly sophisticated printer drivers. This document refers configuration files to highly sophisticated printer drivers. The
to these support files as "Client Print Support Files". selection and installation process can be simplified and even
Traditionally, the selection and installation of the correct Client automated if the workstation can learn some key information about the
Print Support Files has been error prone. The selection and printer and which sets of Client Print Support Files are available.
installation process can be simplified and even automated if the Such key information includes: operating system type, CPU type,
workstation can learn some key information about the printer and document-format (PDL), natural language, compression mechanism, file
which sets of Client Print Support Files are available. Such key type, client file name, policy for automatic loading, file size, file
information includes: operating system type, CPU type, document-
format (PDL), natural language, compression mechanism, file type,
client file name, policy for automatic loading, file size, file
version, file date and time, file information description, and version, file date and time, file information description, and
digital signature. This document describes the IPP extensions that digital signature.
enable workstations to obtain the information needed to perform a
proper printer driver installation using IPP, including security for
downloading executable code and data.
The full set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
Mapping between LPD and IPP Protocols [RFC2569]
The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that
are satisfied in IPP/1.0. A few OPTIONAL operator operations have
been added to IPP/1.1.
The "Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol" document describes IPP from a high level
view, defines a roadmap for the various documents that form the suite
of IPP specification documents, and gives background and rationale
for the IETF working group's major decisions.
The "Internet Printing Protocol/1.1: Encoding and Transport" document
is a formal mapping of the abstract operations and attributes defined
in the model document onto HTTP/1.1 [RFC2616]. It defines the
encoding rules for a new Internet MIME media type called
"application/ipp". This document also defines the rules for
transporting a message body over HTTP whose Content-Type is
"application/ipp". This document defines a new scheme named 'ipp'
for identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document
gives insight and advice to implementers of IPP clients and IPP
objects. It is intended to help them understand IPP/1.1 and some of
the considerations that may assist them in the design of their client
and/or IPP object implementations. For example, a typical order of
processing requests is given, including error checking. Motivation
for some of the specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some
advice to implementers of gateways between IPP and LPD (Line Printer
Daemon) implementations.
Table of Contents Table of Contents
1 Introduction....................................................6 1 Introduction....................................................5
2 Terminology.....................................................6 2 Terminology.....................................................5
3 Model Extensions................................................7 3 Model Extensions................................................6
3.1 client-print-support-files-supported (1setOf octetString(MAX)) 3.1 client-print-support-files-supported (1setOf octetString(MAX))
..........................................................7 ..........................................................6
3.1.1 Use of Keyword Values in fields.............................12 3.1.1 Use of Keyword Values in fields.............................11
3.1.2 Use of the Special Keyword Value: 'unknown'.................12 3.1.2 Use of the Special Keyword Value: 'unknown'.................11
3.1.3 Examples of "client-print-support-files-supported" attribute 3.1.3 Examples of "client-print-support-files-supported" attribute
values.................................................12 values.................................................11
3.2 Get-Printer-Attributes Operation Extension..................13 3.2 Get-Printer-Attributes Operation Extension..................12
3.2.1 Get-Printer-Attributes Request..............................13 3.2.1 Get-Printer-Attributes Request..............................12
3.2.1.1 client-print-support-files-filter (octetString(MAX)) 3.2.1.1 client-print-support-files-filter (octetString(MAX))
operation attribute..................................13 operation attribute..................................12
3.2.1.1.1 Filter matching rules.................................15 3.2.1.1.1 Filter matching rules.................................14
3.2.2 Get-Printer-Attributes Response.............................16 3.2.2 Get-Printer-Attributes Response.............................15
3.3 Get-Client-Print-Support-Files..............................17 3.3 Get-Client-Print-Support-Files..............................16
3.3.1 Get-Client-Print-Support-Files Request......................17 3.3.1 Get-Client-Print-Support-Files Request......................16
3.3.2 Get-Client-Print-Support-Files Response.....................18 3.3.2 Get-Client-Print-Support-Files Response.....................17
4 Conformance....................................................19 4 Conformance....................................................18
5 Encoding of the Operation Layer................................20 4.1 Printer Conformane Requirements.............................18
6 Encoding of Transport Layer....................................20 4.2 Client Conformance Requirements.............................18
7 IANA Considerations............................................20 5 Encoding of the Operation Layer................................19
7.1 Attribute Registrations.....................................21 6 Encoding of Transport Layer....................................19
7.2 Operation Registrations.....................................22 7 IANA Considerations............................................19
8 Internationalization Considerations............................22 7.1 Attribute Registrations.....................................20
9 Security Considerations........................................22 7.2 Operation Registrations.....................................21
10 References.....................................................23 8 Internationalization Considerations............................21
9 Security Considerations........................................21
10 References.....................................................22
11 Author's Addresses.............................................24 11 Author's Addresses.............................................24
12 Full Copyright Statement.......................................25 12 Description of the Base IPP Documents..........................24
13 Full Copyright Statement.......................................25
Tables Tables
Table 1 - "client-print-support-files-supported" attribute fields..9 Table 1 - "client-print-support-files-supported" attribute fields..8
Table 2 - "client-print-support-files-filter" attribute fields....14 Table 2 - "client-print-support-files-filter" attribute fields....13
Table 3 - REQUIRED "client-print-support-files-filter" fields.....14 Table 3 - REQUIRED "client-print-support-files-filter" fields.....13
1 Introduction 1 Introduction
A common configuration for printing from a workstation requires that A common configuration for printing from a workstation requires that
some Client Print Support Files (e.g., PPD, printer driver files) some Client Print Support Files (e.g., PPD, printer driver files)
specific to the target printer be installed on that workstation. specific to the target printer be installed on that workstation.
Selection and configuration of the appropriate Client Print Support Selection and configuration of the appropriate Client Print Support
Files can be simplified and even automated if the workstation can Files can be simplified and even automated if the workstation can
obtain some key information about the printer and which sets of obtain some key information about the printer and which sets of
Client Print Support Files are available. Such key information Client Print Support Files are available. Such key information
includes: operating system type, CPU type, document-format (PDL), includes: operating system type, CPU type, document-format (PDL),
natural language, compression mechanism, file type, client file name, natural language, compression mechanism, file type, client file name,
policy for automatic loading, file size, file version, file date and policy for automatic loading, file size, file version, file date and
time, file information description, and digital signature. With a time, file information description, and digital signature. The IPP
few extensions, IPP provides a simple and reliable vehicle for extension defined in this document provides a simple and reliable
printers to convey this information to interested workstations. The vehicle for printers to convey this information to interested
IPP extensions described in this document enable a flexible solution workstations. This extension enables a flexible solution for
for installing Client Print Support Files on workstations running installing Client Print Support Files on workstations running
different operating systems and for printers of all makes and models. different operating systems and for printers of all makes and models.
It allows Client Print Support Files to be downloaded from It allows Client Print Support Files to be downloaded from
repositories of different sorts. A possible repository for the files repositories of different sorts. A possible repository for the files
is the printer itself. The extensions necessary for getting Client is the printer itself. The extensions necessary for getting Client
Print Support Files from the printer are included in this document, Print Support Files from the printer are included in this document,
including security for downloading executable code and data. including security for downloading executable code and data.
2 Terminology 2 Terminology
Client Print Support Files - a set of files, such as a printer Client Print Support Files - a set of files, such as a printer
skipping to change at page 7, line 38 skipping to change at page 6, line 38
Files. Files.
3.1 client-print-support-files-supported (1setOf octetString(MAX)) 3.1 client-print-support-files-supported (1setOf octetString(MAX))
An IPP Printer uses the REQUIRED Printer Description attribute An IPP Printer uses the REQUIRED Printer Description attribute
"client-print-support-files-supported" to represent relevant "client-print-support-files-supported" to represent relevant
information about all of the Client Print Support Files it supports. information about all of the Client Print Support Files it supports.
Each value is a composite UTF-8 string with well-defined fields (see Each value is a composite UTF-8 string with well-defined fields (see
Table 1). Each value string MUST be formatted as follows: Table 1). Each value string MUST be formatted as follows:
"uri=val1< field-name2=val21,_,val2p< _ < field-namen=valn1,_,valnq<" "uri=val1< field-name2=val21,...,val2p< ... < field-
namen=valn1,...,valnq<"
The first field MUST be the "uri" field. The remaining fields MAY be The first field MUST be the "uri" field. The remaining fields MAY be
in any order. in any order.
The string MUST NOT include any control characters (hex 00 to 1F), The string MUST NOT include any control characters (hex 00 to 1F),
even the so-called white space control characters (TAB, CR, and LF) even the so-called white space control characters (TAB, CR, and LF)
anywhere. Only zero or more UTF-8 SPACE characters (hex 20) can be anywhere. Only zero or more UTF-8 SPACE characters (hex 20) can be
included and they can be included only IMMEDIATELY AFTER the included and they can be included only IMMEDIATELY AFTER the
delimiter character: "<", but NOT anywhere else, including after "=" delimiter character: "<", but NOT anywhere else, including after "="
and ",". However, if the UTF-8 SPACE character is needed in a and ",". However, if the UTF-8 SPACE character is needed in a
skipping to change at page 8, line 17 skipping to change at page 7, line 19
support-files-supported" (1setOf octetString(MAX)) Printer support-files-supported" (1setOf octetString(MAX)) Printer
Description attribute. A Printer implementation MAY support Description attribute. A Printer implementation MAY support
additional fields using the same syntax. Values are defined to be additional fields using the same syntax. Values are defined to be
either CASE-SENSITIVE or ALL-LOWER-CASE according to the definitions either CASE-SENSITIVE or ALL-LOWER-CASE according to the definitions
for the attribute syntaxes from [RFC2911] (set off by single quotes for the attribute syntaxes from [RFC2911] (set off by single quotes
in the table). The CASE-SENSITIVE values MAY have upper and lower in the table). The CASE-SENSITIVE values MAY have upper and lower
case letters as for the corresponding attribute syntaxes in case letters as for the corresponding attribute syntaxes in
[RFC2911]. The LOWER-CASE values MUST have all lower case alphabetic [RFC2911]. The LOWER-CASE values MUST have all lower case alphabetic
letters. Additional characters, such as digits, hyphen-minus (-), letters. Additional characters, such as digits, hyphen-minus (-),
period (.), and slash (/) are according to the corresponding period (.), and slash (/) are according to the corresponding
attribute syntaxes in [RFC2911]. attribute syntaxes in [RFC2911]. Additional values for these fields
can be registered with IANA according to the procedures in [RFC2911]
for registering additional values of attributes. Additional fields
can be registered with IANA according to the procedures defined in
[RFC2911] for registering attributes. See section 7.
Clients SHOULD ignore fields they don't recognize in a given value. Clients SHOULD ignore fields they don't recognize in a given value.
This allows for future extensions to the format of the string without This allows for future extensions to the format of the string without
breaking compatibility with earlier clients. breaking compatibility with earlier clients.
Table 1 - "client-print-support-files-supported" attribute fields Table 1 - "client-print-support-files-supported" attribute fields
Field Field value Field Field value
name name
skipping to change at page 9, line 49 skipping to change at page 8, line 49
lower case in this field (plus hyphen-minus (-), period lower case in this field (plus hyphen-minus (-), period
(.), and slash (/)). Examples: 'linux', 'linux-2.2', (.), and slash (/)). Examples: 'linux', 'linux-2.2',
'os/2', 'sun-os-4.0', 'unix', 'unix-bsd', 'win32', 'os/2', 'sun-os-4.0', 'unix', 'unix-bsd', 'win32',
'windows-95', 'windows-98', 'windows-ce', 'windows-nt', 'windows-95', 'windows-98', 'windows-ce', 'windows-nt',
'windows-nt-4', 'windows-nt-5', 'unknown'. 'windows-nt-4', 'windows-nt-5', 'unknown'.
"cpu- One or more REQUIRED comma-separated LOWER-CASE "cpu- One or more REQUIRED comma-separated LOWER-CASE
type" 'keyword' strings identifying the CPU types supported by type" 'keyword' strings identifying the CPU types supported by
this set of Client Print Support Files. The values this set of Client Print Support Files. The values
indicate the CPU family independent of the CPU indicate the CPU family independent of the CPU
manufacturer. Valid keyword values are: 'x86-16', manufacturer. Standard keyword values are: 'x86-16',
'x86-32', 'x86-64', 'dec-vax', 'alpha', 'power-pc', 'm- 'x86-32', 'x86-64', 'dec-vax', 'alpha', 'power-pc', 'm-
68000, 'sparc', 'itantium', 'mips', 'arm' and will be 68000, 'sparc', 'itantium', 'mips', 'arm' and will be
Field Field value Field Field value
name name
used as the initial value for the "cpu-type" IANA used as the initial value for the "cpu-type" IANA
registry. In addition, the special keyword value: registry. In addition, the special keyword value:
'unknown' is valid. 'unknown' is valid.
"document One or more REQUIRED comma-separated CASE-SENSITIVE "document One or more REQUIRED comma-separated CASE-SENSITIVE
skipping to change at page 10, line 44 skipping to change at page 9, line 44
See [RFC2911] section 4.4.32), for example 'gzip'. The See [RFC2911] section 4.4.32), for example 'gzip'. The
'none' value limits the uncompressed Client Print 'none' value limits the uncompressed Client Print
Support File to a single file. The values for the Support File to a single file. The values for the
"compression" field that a Printer supports NEED NOT be "compression" field that a Printer supports NEED NOT be
the same values that the Printer is configured to the same values that the Printer is configured to
support in Job Creation operations as indicated in the support in Job Creation operations as indicated in the
Printer's "compressions-supported" attribute. Printer's "compressions-supported" attribute.
"file- One or more REQUIRED comma-separated LOWER-CASE "file- One or more REQUIRED comma-separated LOWER-CASE
type" 'keyword' strings identifying the type of the Client type" 'keyword' strings identifying the type of the Client
Print Support Files. Valid keyword values are: Print Support Files. Standard keyword values are:
'printer-driver', 'ppd', 'updf', 'gpd'. 'printer-driver', 'ppd', 'updf', 'gpd'.
"client- One REQUIRED CASE-SENSITIVE string identifying the name "client- One REQUIRED CASE-SENSITIVE string identifying the name
file- by which the Client Print Support Files will be file- by which the Client Print Support Files will be
name" installed on the workstation. For Client Print Support name" installed on the workstation. For Client Print Support
Files of type 'printer-driver', this is also the name Files of type 'printer-driver', this is also the name
Field Field value Field Field value
name name
that identifies this printer driver in an .inf file. that identifies this printer driver in an .inf file.
"policy" One OPTIONAL LOWER-CASE 'keyword' string indicating the "policy" One OPTIONAL LOWER-CASE 'keyword' string indicating the
policy for automatic loading. Valid keyword values are: policy for automatic loading. Standard keyword values
'manufacturer-recommended', 'administrator-recommended', are: 'manufacturer-recommended', 'administrator-
'manufacturer-experimental, 'administrator- recommended', 'manufacturer-experimental,
experimental'. The experimental values are for beta 'administrator-experimental'. The experimental values
test. are for beta test.
"file- One OPTIONAL file size in octets represented as ASCII "file- One OPTIONAL file size in octets represented as ASCII
size" decimal digits. size" decimal digits.
"file- One OPTIONAL LOWER-CASE version number. Recommended to "file- One OPTIONAL LOWER-CASE version number. Recommended to
version" be of the form "Major.minor[.revision]" where "Major" is version" be of the form "Major.minor[.revision]" where "Major" is
the major version number, "minor" is the minor version the major version number, "minor" is the minor version
number and "revision" is an optional revision number. number and "revision" is an optional revision number.
"file- One OPTIONAL File CASE-SENSITIVE creation date and time "file- One OPTIONAL File CASE-SENSITIVE creation date and time
skipping to change at page 11, line 41 skipping to change at page 10, line 41
info" describing this set of Client Print Support Files. The info" describing this set of Client Print Support Files. The
natural language for this value MUST be the natural natural language for this value MUST be the natural
language indicated by the Printer's "natural-language- language indicated by the Printer's "natural-language-
configured" attribute. To avoid exceeding the maximum configured" attribute. To avoid exceeding the maximum
limit imposed on IPP attributes and to increase limit imposed on IPP attributes and to increase
interoperability with other systems, the length of this interoperability with other systems, the length of this
field value MUST not exceed 127 characters. field value MUST not exceed 127 characters.
"digital- One REQUIRED LOWER-CASE 'keyword' string identifying the "digital- One REQUIRED LOWER-CASE 'keyword' string identifying the
signature mechanism used to ensure the integrity and authenticity signature mechanism used to ensure the integrity and authenticity
" of this set of Client Print Support Files. Valid values " of this set of Client Print Support Files. Standard
are: 'smime', 'pgp', 'dss', and 'xmldsig' which are values are: 'smime', 'pgp', 'dss', and 'xmldsig' which
defined in [RFC2634], [RFC1991], [dss], and [xmldsig], are defined in [RFC2634], [RFC1991], [dss], and
respectively. In addition, the special keyword value: [xmldsig], respectively. In addition, the special
'none' is valid. keyword value: 'none' is valid.
Each value MUST refer to one and only one set of Client Print Support Each value MUST refer to one and only one set of Client Print Support
Files, even if the files are downloadable from various repositories Files, even if the files are downloadable from various repositories
(i.e., even if they are associated with multiple URIs). (i.e., even if they are associated with multiple URIs).
3.1.1 Use of Keyword Values in fields 3.1.1 Use of Keyword Values in fields
A number of the fields in Table 1 use keyword strings as values. The A number of the fields in Table 1 use keyword strings as values. The
syntax of these keywords is the same as in [RFC2911], including the syntax of these keywords is the same as in [RFC2911], including the
use of private keywords. See [RFC2911] sections 4.1.3 and 6.1. use of private keywords. See [RFC2911] sections 4.1.3 and 6.1.
skipping to change at page 17, line 48 skipping to change at page 16, line 48
The "attributes-charset" and "attributes-natural-language" The "attributes-charset" and "attributes-natural-language"
attributes as described in [RFC2911], section 3.1.4.1. attributes as described in [RFC2911], section 3.1.4.1.
Target: Target:
The "printer-uri" (uri) operation attribute which is the target The "printer-uri" (uri) operation attribute which is the target
for this operation as described in [RFC2911], section 3.1.5. for this operation as described in [RFC2911], section 3.1.5.
The client MUST use the URI value as the target of this The client MUST use the URI value as the target of this
operation that the Printer returns in the "uri" field (see Table operation that the Printer returns in the "uri" field (see Table
1) in the Get-Printer-Attributes response. Furthermore, the 1) in the Get-Printer-Attributes response. Furthermore, the
client MUST use the appropriate authorization and security client MUST use the appropriate authorization and security
regime for this URI as indicated by the Printer's "printer-uri- mechanism for this URI as indicated by the Printer's "printer-
supported", "uri-authentication-supported" and "uri-security- uri-supported", "uri-authentication-supported" and "uri-
supported" attributes (see [RFC2911] sections 4.4.1, 4.4.2, and security-supported" attributes (see [RFC2911] sections 4.4.1,
4.4.3). Only if the URI returned in the "uri" field matches the 4.4.2, and 4.4.3). Only if the URI returned in the "uri" field
URI that the client used for the Get-Printer-Attributes request matches the URI that the client used for the Get-Printer-
MAY the client use the same HTTP connection. The 'ipp' URL Attributes request MAY the client use the same HTTP connection.
matching rules are defined in [ipp-url] and do not include the The 'ipp' URL matching rules are defined in [ipp-url] and do not
query part. include the query part.
Requesting User Name: Requesting User Name:
The "requesting-user-name" (name(MAX)) attribute SHOULD be The "requesting-user-name" (name(MAX)) attribute SHOULD be
supplied by the client as described in [RFC2911], section 8.3. supplied by the client as described in [RFC2911], section 8.3.
"client-print-support-files-query" (text(127)): "client-print-support-files-query" (text(127)):
The client MUST supply this attribute specifying the query part The client MUST supply this attribute specifying the query part
[RFC2396] of the ipp uri for the desired Client Print Support [RFC2396] of the ipp uri for the desired Client Print Support
Files not including the "?" character that starts the query Files not including the "?" character that starts the query
part, i.e., the value of the "uri" field following the "?" part, i.e., the value of the "uri" field following the "?"
skipping to change at page 19, line 15 skipping to change at page 18, line 15
Printer MUST return all configured fields for the selected Printer MUST return all configured fields for the selected
Client Print Support Files in the format shown in section 3.1. Client Print Support Files in the format shown in section 3.1.
Group 4: Client Print Support Files Group 4: Client Print Support Files
The printer MUST supply the Client Print Support Files that match The printer MUST supply the Client Print Support Files that match
the client's criteria following the "end-of-attributes" tag. All the client's criteria following the "end-of-attributes" tag. All
necessary files MUST be compressed into a single transferred file. necessary files MUST be compressed into a single transferred file.
4 Conformance 4 Conformance
4.1 Printer Conformane Requirements
A Printer conforming to this specification: A Printer conforming to this specification:
1.MUST support the "client-print-support-files-supported" Printer 1.MUST support the "client-print-support-files-supported" Printer
Description attribute as defined in section 3.1, including all Description attribute as defined in section 3.1, including all
of the REQUIRED fields defined in Table 1 and MAY support the of the REQUIRED fields defined in Table 1 and MAY support the
OPTIONAL fields defined in Table 1. OPTIONAL fields defined in Table 1.
2.MUST support the "client-print-support-files-filter" operation 2.MUST support the "client-print-support-files-filter" operation
attribute in the Get-Printer-Attributes request as defined in attribute in the Get-Printer-Attributes request as defined in
section 3.2, including all of the fields listed in Table 3 and section 3.2, including all of the fields listed in Table 3 and
skipping to change at page 19, line 37 skipping to change at page 18, line 39
3.MUST support at least one of the following URI schemes that 3.MUST support at least one of the following URI schemes that
identify the support files: 'ftp', 'http', or 'ipp', of which identify the support files: 'ftp', 'http', or 'ipp', of which
the 'ipp' scheme is the RECOMMENDED one. the 'ipp' scheme is the RECOMMENDED one.
4.SHOULD support the Get-Client-Print-Support-Files operation as 4.SHOULD support the Get-Client-Print-Support-Files operation as
described in section 3.3. If this operation is supported, then described in section 3.3. If this operation is supported, then
one of the supported schemes MUST be 'ipp'. one of the supported schemes MUST be 'ipp'.
5.SHOULD support TLS as described in section 9. 5.SHOULD support TLS as described in section 9.
6.SHOULD support the downloading of Client Print Support Files 6.SHOULD support at least one method for the downloading of Client
that have been digitally signed as described in section 9. Print Support Files that have been digitally signed as described
in section 9.
4.2 Client Conformance Requirements
A client conforming to this specification: A client conforming to this specification:
1.MUST ignore any fields returned by the Printer in the "client- 1.MUST ignore any fields returned by the Printer in the "client-
print-support-files-supported" Printer Description attribute print-support-files-supported" Printer Description attribute
that the client does not recognize or support. that the client does not recognize or support.
2.SHOULD be able to retrieve Client Print Support Files by either 2.SHOULD be able to retrieve Client Print Support Files by either
FTP Get or HTTP Get operations. FTP Get or HTTP Get operations.
skipping to change at page 20, line 46 skipping to change at page 20, line 5
(see Table 1). (see Table 1).
Table 1 of this document defines possible 'keyword' values for the Table 1 of this document defines possible 'keyword' values for the
"cpu-type" field. However, the existing IANA machine registration "cpu-type" field. However, the existing IANA machine registration
[cpu-names] is inadequate for two reasons: a) it is really a machine [cpu-names] is inadequate for two reasons: a) it is really a machine
model number, not a CPU type, and b) it doesn't express whether a model number, not a CPU type, and b) it doesn't express whether a
CPU is 16-bit, 32-bit, or 64-bit which needs to be indicated in the CPU is 16-bit, 32-bit, or 64-bit which needs to be indicated in the
keyword value. Therefore, the "os-type" field will be a new keyword value. Therefore, the "os-type" field will be a new
registration with initial values assigned. registration with initial values assigned.
Implementers may register additional values for the fields defined in
Table 1 with IANA according to the procedures in [RFC2911] for
registering additional values of attributes. Implementers may
register additional fields with IANA according to the procedures
defined in [RFC2911] for registering attributes.
The rest of this section contains the exact information for IANA to The rest of this section contains the exact information for IANA to
add to the IPP Registries according to the procedures defined in RFC add to the IPP Registries according to the procedures defined in RFC
2911 [RFC2911] section 6. 2911 [RFC2911] section 6.
Note to RFC Editors: Replace RFC NNNN below with the RFC number Note to RFC Editors: Replace RFC NNNN below with the RFC number
for this document, so that it accurately reflects the content of for this document, so that it accurately reflects the content of
the information for the IANA Registry. the information for the IANA Registry.
7.1 Attribute Registrations 7.1 Attribute Registrations
skipping to change at page 24, line 13 skipping to change at page 23, line 21
2026, October 1996. 2026, October 1996.
[RFC2396] [RFC2396]
Berners-Lee, T., Fielding, R., Masinter, L., "Uniform Resource Berners-Lee, T., Fielding, R., Masinter, L., "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998. Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2518] [RFC2518]
Goland, Y., et al, "HTTP Extensions for Distributed Authoring -- Goland, Y., et al, "HTTP Extensions for Distributed Authoring --
WEBDAV", RFC 2518, February 1999. WEBDAV", RFC 2518, February 1999.
[RFC2565]
Herriot, R., Butler, S., Moore, P., and R. Turner, "Internet
Printing Protocol/1.0: Encoding and Transport", RFC 2565, April
1999.
[RFC2566]
R. deBry, T. Hastings, R. Herriot, S. Isaacson, and P. Powell,
"Internet Printing Protocol/1.0: Model and Semantics", RFC 2566,
April 1999.
[RFC2567]
Wright, D., "Design Goals for an Internet Printing Protocol", RFC
2567, April 1999.
[RFC2568]
Zilles, S., "Rationale for the Structure and Model and Protocol for
the Internet Printing Protocol", RFC 2568, April 1999.
[RFC2569]
Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between
LPD and IPP Protocols", RFC 2569, April 1999.
[RFC2616] [RFC2616]
R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1",
RFC 2616, June 1999. RFC 2616, June 1999.
[RFC2634] [RFC2634]
P. Hoffman, "Enhanced Security Services for S/MIME", RFC 2634, June P. Hoffman, "Enhanced Security Services for S/MIME", RFC 2634, June
1999. 1999.
[RFC2910] [RFC2910]
skipping to change at page 25, line 4 skipping to change at page 24, line 33
e-mail: hparra@novell.com e-mail: hparra@novell.com
Ted Tronson Ted Tronson
Novell, Inc. Novell, Inc.
1800 South Novell Place 1800 South Novell Place
Provo, UT 84606 Provo, UT 84606
Phone: 801-861-3338 Phone: 801-861-3338
Fax: 801-861-4025 Fax: 801-861-4025
e-mail: ttronson@novell.com e-mail: ttronson@novell.com
Thomas N. Hastings Thomas N. Hastings
Xerox Corp. Xerox Corp.
737 Hawaii St. ESAE 231 737 Hawaii St. ESAE 231
El Segundo, CA 90245 El Segundo, CA 90245
Phone: 310-333-6413 Phone: 310-333-6413
Fax: 310-333-5514 Fax: 310-333-5514
e-mail: hastings@cp10.es.xerox.com e-mail: hastings@cp10.es.xerox.com
12 Full Copyright Statement 12 Description of the Base IPP Documents
The base set of IPP documents includes:
Design Goals for an Internet Printing Protocol [RFC2567]
Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol [RFC2568]
Internet Printing Protocol/1.1: Model and Semantics [RFC2911]
Internet Printing Protocol/1.1: Encoding and Transport [RFC2910]
Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig]
Mapping between LPD and IPP Protocols [RFC2569]
The "Design Goals for an Internet Printing Protocol" document takes a
broad look at distributed printing functionality, and it enumerates
real-life scenarios that help to clarify the features that need to be
included in a printing protocol for the Internet. It identifies
requirements for three types of users: end users, operators, and
administrators. It calls out a subset of end user requirements that
are satisfied in IPP/1.0 [RFC2566, RFC2565]. A few OPTIONAL operator
operations have been added to IPP/1.1 [RFC2911, RFC2910].
The "Rationale for the Structure and Model and Protocol for the
Internet Printing Protocol" document describes IPP from a high level
view, defines a roadmap for the various documents that form the suite
of IPP specification documents, and gives background and rationale
for the IETF working group's major decisions.
The "Internet Printing Protocol/1.1: Encoding and Transport" document
is a formal mapping of the abstract operations and attributes defined
in the model document onto HTTP/1.1 [RFC2616]. It defines the
encoding rules for a new Internet MIME media type called
"application/ipp". This document also defines the rules for
transporting a message body over HTTP whose Content-Type is
"application/ipp". This document defines the 'ipp' scheme for
identifying IPP printers and jobs.
The "Internet Printing Protocol/1.1: Implementer's Guide" document
gives insight and advice to implementers of IPP clients and IPP
objects. It is intended to help them understand IPP/1.1 and some of
the considerations that may assist them in the design of their client
and/or IPP object implementations. For example, a typical order of
processing requests is given, including error checking. Motivation
for some of the specification decisions is also included.
The "Mapping between LPD and IPP Protocols" document gives some
advice to implementers of gateways between IPP and LPD (Line Printer
Daemon) implementations.
13 Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at line 1068 skipping to change at page 26, line 26
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Trade Marks
Trademarks within this document are the property of their owners.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/