idnits 2.17.1 draft-ietf-ipp-dir-schema-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-20) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 79 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 160: '...ATORY attributes MUST be defined in ea...' RFC 2119 keyword, line 161: '...other attributes SHOULD be defined in ...' RFC 2119 keyword, line 163: '...r an IPP Printer SHOULD be an instance...' RFC 2119 keyword, line 165: '... for an IPP Printer SHOULD reflect the...' RFC 2119 keyword, line 173: '...of a printer URI SHALL be implementati...' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 12, 1997) is 9809 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 295, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 297, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 299, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' Summary: 9 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT 3 K. Carter 4 IBM 5 S. Isaacson 6 Novell, Inc. 7 June 12, 1997 9 Internet Printing Protocol/1.0: Directory Schema 10 draft-ietf-ipp-dir-schema-01.txt 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 To learn the current status of any Internet-Draft, please check the 25 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 26 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 27 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 28 ftp.isi.edu (US West Coast). 30 Abstract 32 This document is one of a set of documents which together describe 33 all aspects of a new Internet Printing Protocol (IPP). IPP is an 34 application level protocol that can be used for distributed printing 35 using Internet tools and technology. The protocol is heavily 36 influenced by the printing model introduced in the Document Printing 37 Application (ISO/IEC 10175 DPA) standard. Although DPA specifies 38 both end user and administrative features, IPP version 1.0 is focused 39 on end user functionality. Although DPA specifies both end user and 40 administrative features, IPP version 1.0 is focused only on end user 41 functionality. 43 The full set of IPP documents includes: 45 June 12, 1997, Expires December 12, 1997 46 Internet Printing Protocol : Requirements 47 Internet Printing Protocol/1.0: Model and Semantics 48 Internet Printing Protocol/1.0: Security 49 Internet Printing Protocol/1.0: Protocol Specification 50 Internet Printing Protocol/1.0: Directory Schema 52 The requirements document takes a broad look at distributed printing 53 functionality, and it enumerates real-life scenarios that help to 54 clarify the features that need to be included in a printing protocol 55 for the Internet. It identifies requirements for three types of 56 users: end users, operators, and administrators. The requirements 57 document calls out a subset of end user requirements that must be 58 satisfied in the first version of IPP. Operator and administrator 59 requirements are out of scope for v1.0. The model and semantics 60 document describes a simplified model with abstract objects, their 61 attributes, and their operations. The security document covers 62 potential threats and proposed counters to those threats. The 63 protocol specification incorporates the ideas in all the other 64 documents into a concrete mapping using clearly defined data 65 representations and transport protocol mappings that real 66 implementers can use to develop interoperable client and server side 67 components. Finally, the directory schema document shows a generic 68 schema for directory service entries that represent instances of IPP 69 Printers. 71 This document is the "Internet Printing Protocol/1.0: Directory 72 Schema" document. 74 June 12, 1997, Expires December 12, 1997 75 Table of Contents 77 1. Introduction ..........................................4 78 2. Directory Entry Schema ................................5 79 2.1 printer-URI (uri, MANDATORY) ........................5 80 2.2 printer-name (name, MANDATORY) ......................5 81 2.3 printer-location (text) .............................5 82 2.4 printer-description (text) ..........................6 83 2.5 printer-more-info-site (uri) ........................6 84 2.6 printer-make-and-model (text) .......................6 85 2.7 printer-more-info-manf (uri) ........................6 86 2.8 media-supported (1setOftype4 keyword) ...............6 87 2.9 number-up-supported (1setOftype3 keyword) ...........6 88 2.10 sides-supported (1setOftype2 keyword) ...............7 89 2.11 printer-resolution-supported (1setOftype2 keyword) ..7 90 2.12 maximum-printer-speed-supported (integerUnits) ......7 91 2.13 print-quality-supported (1setOftype2 keyword) .......7 92 2.14 color-supported (boolean) ...........................7 93 2.15 finishings-supported (setOftype2 keyword) ...........7 94 2.16 document-formats-supported (1setOftype2 keyword) ....7 95 2.17 printer-locales-supported 96 (1setOflocale keyword, MANDATORY) ...................7 97 3. Security Considerations ...............................7 98 4. References ............................................8 99 5. Author's Address ......................................8 101 June 12, 1997, Expires December 12, 1997 102 1. Introduction 104 A Directory Service is a means by which service users can locate 105 service providers. The directory contains entries for each type of 106 object within the system: entries for users, file systems, servers, 107 applications, printers, other devices, etc. End users use a 108 Directory Service to locate objects based on naming and 109 organizational contexts. For example, find all servers in the "Local 110 Department" context. Authentication and authorization are also often 111 part of a directory service. Users are only allowed to find objects 112 to which they have certain access rights. Each service provider 113 registers with the directory (either automatically or with the help 114 of an administrator) as an entry of a certain type. For example, an 115 IPP Printer can be registered in the directory as a Printer object 116 with certain registration attributes (name, address, static 117 characteristics, etc.). Given a Directory Service provides this type 118 of interaction for both service providers and service users, it is 119 possible for end users to locate an IPP Printer using either a simple 120 name lookup or a filtered attribute search. 122 After an end user locates one or more IPP Printers, the end user 123 selects a Printer. Certain attributes in the directory entry for a 124 Printer provide additional information to the end user, such as the 125 cost to print jobs on this Printer, that assist the end user in 126 selecting a Printer. 128 After an end user selects an IPP Printer, the end user performs an 129 IPP print operation on that Printer. IPP provides the protocol that 130 communicates this print operation to the IPP Printer in the network. 131 An IPP client addresses an IPP Printer using a URI. This URI is a 132 required attribute in the directory entry for an IPP Printer. Thus, 133 the Printer's URI _links_ the directory entry for an IPP Printer to 134 the corresponding IPP Printer in the network. 136 IPP does not require any specific Directory Service provider. 137 However, this specification does define a generic schema that can be 138 used to implement directory entries for Printers using a specific 139 Directory Service. 141 Section 2 introduces the generic schema for entries in a directory 142 that represent IPP Printer objects. 144 Sections 3-5 cover security, technical references, and author contact 145 information. 147 June 12, 1997, Expires December 12, 1997 148 2. Directory Entry Schema 150 The following attributes define the generic directory entry schema 151 for an IPP Printer. The conformance terminology, the syntax 152 definitions of the attributes and the values of the attributes are 153 defined in the _Internet Printing Protocol/1.0 Model and Semantics_ 154 document and are not repeated in this document. The attribute 155 definitions in this schema match the corresponding attribute 156 definitions in the model to facilitate manual and/or automatic 157 mechanisms of mapping an IPP Printer to its corresponding directory 158 entry. 160 All MANDATORY attributes MUST be defined in each directory entry for 161 an IPP Printer. All other attributes SHOULD be defined in each 162 directory entry for an IPP Printer. Furthermore, a directory entry 163 for an IPP Printer SHOULD be an instance of a Printer object class 164 defined by the Directory Service to scope searches for Printers. 165 Finally, a directory entry for an IPP Printer SHOULD reflect the 166 current attribute values for an IPP Printer in the network at any 167 point in time. 169 2.1 printer-URI (uri, MANDATORY) 171 This attribute contains the URI for the Printer. An administrator 172 shall determine a printer's URI and shall set this attribute to that 173 URI. The precise format of a printer URI SHALL be implementation 174 dependent. 176 2.2 printer-name (name, MANDATORY) 178 This attribute contains the name of the Printer. It is a name that is 179 more user friendly than the printer-URI. An administrator shall 180 determine a Printer's name and shall set this attribute to that name. 181 This name may be the last part of the printer's URI or it may be 182 unrelated. In non-US-English locales, a name may contain characters 183 that are not allowed in a URI. 185 2.3 printer-location (text) 187 This attribute identifies the location of this Printer. 189 In order for filtered searches to be more effective, a given site may 190 use some regular structuring within the attribute value such as 191 "SITE:USA-San Jose,BUILDING:A1,FLOOR:2,ROOM:555" or "department5- 192 2ndFloor-A5-IndianHills-Chicago-IL-USA". 194 June 12, 1997, Expires December 12, 1997 195 2.4 printer-description (text) 197 This attribute identifies the descriptive information about this 198 Printer. This could include things like: "This printer can be used 199 for printing color transparencies for HR presentations", or "Out of 200 courtesy for others, please print only small (1-5 page) jobs at this 201 printer", or even "this printer is going away on July 1, 1997, please 202 find a new printer". 204 2.5 printer-more-info-site (uri) 206 This attribute contains a URI used to obtain more information about 207 this specific Printer. The information obtained from this URI is 208 intended for end user consumption. Features outside the scope of IPP 209 can be accessed from this URI. The information is intended to be 210 specific to this Printer and site services (e.g. job pricing, 211 services offered, end user assistance). The manufacturer may 212 initially populate this attribute. 214 2.6 printer-make-and-model (text) 216 This attribute identifies the make and model of the printer. 218 2.7 printer-more-info-manf (uri) 220 This attribute contains a URI used to obtain more information about 221 this type of printer. The information obtained from this URI is 222 intended for end user consumption. Features outside the scope of IPP 223 can be accessed from this URI. (e.g. latest firmware, upgrades, 224 print drivers, optional features available). The information is 225 intended to be germane to this printer without regard to site 226 specific modifications or services. 228 2.8 media-supported (1setOftype4 keyword) 230 This attribute identifies the media supported by the Printer. This 231 directory attribute SHOULD only be updated with values that are 232 relatively static values, not values which are constantly being 233 updated by the Printer. 235 2.9 number-up-supported (1setOftype3 keyword) 237 This attribute specifies the number of source page-images to impose 238 upon a single side of an instance of a selected medium. 240 June 12, 1997, Expires December 12, 1997 241 2.10 sides-supported (1setOftype2 keyword) 243 This attribute specifies how source page-images are to be imposed 244 upon the sides of an instance of a selected medium. 246 2.11 printer-resolution-supported (1setOftype2 keyword) 248 This attribute specifies the printer resolutions supported by this 249 printer. 251 2.12 maximum-printer-speed-supported (integerUnits) 253 This attribute specifies the maximum printer speed of the Printer. 255 2.13 print-quality-supported (1setOftype2 keyword) 257 This attribute specifies the print qualities supported by the 258 Printer. 260 2.14 color-supported (boolean) 262 This attribute specifies whether the Printer supports color or not. 264 2.15 finishings-supported (setOftype2 keyword) 266 This attribute identifies the finishing operations that the Printer 267 can apply to each copy of each printed document in a job. 269 2.16 document-formats-supported (1setOftype2 keyword) 271 This attribute specifies a list of the document formats that the 272 Printer supports. 274 2.17 printer-locales-supported (1setOflocale keyword, MANDATORY) 276 This attribute specifies the locales that the Printer operates in. 278 3. Security Considerations 280 An end user's access to a directory entry for an IPP Printer is 281 controlled by the Directory Service. An end user's access to an IPP 282 Printer in the network is controlled by the service provider for that 283 IPP Printer. 285 NOTE: There is another Internet-Draft called "Internet Printing 286 Protocol/1.0: Security." That document is being drafted and reviewed 287 in parallel with this document. Before this document can become a 289 June 12, 1997, Expires December 12, 1997 290 formal RFC, any relevant issues from that document will be rolled 291 into this one. 293 4. References 295 [1] Internet Printing Protocol: Requirements. 297 [2] Internet Printing Protocol/1.0: Model and Semantics. 299 [3] Internet Printing Protocol/1.0: Security. 301 5. Author's Address 303 Scott A. Isaacson 304 Novell, Inc. 305 122 E 1700 S 306 Provo, UT 84606 308 Phone: 801-861-7366 309 Fax: 801-861-4025 310 EMail: scott_isaacson@novell.com 312 Keith Carter 313 IBM Corporation 314 11400 Burnet Road 315 Internal Zip 9372 316 Austin, Texas 78758 318 Phone: (512) 838-2155 319 Fax: (512) 838-2611 320 Email: carterk@us.ibm.com 322 IPP Mailing List: ipp@pwg.org 323 IPP Mailing List Subscription Information: ipp-request@pwg.org 324 IPP Home Page: http://www.pwg.org/ipp/ 326 Other Participants: 328 June 12, 1997, Expires December 12, 1997