idnits 2.17.1 draft-ietf-ipp-indp-method-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 Shadow Directories -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC2565,RFC2910], [RFC2911,RFC2910], [RFC2566,RFC2565]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 2 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. ** 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 41: '... RECOMMENDED Delivery Methods for Pr...' RFC 2119 keyword, line 144: '... defines an OPTIONAL extension to In...' RFC 2119 keyword, line 166: '...his document is one of the RECOMMENDED...' RFC 2119 keyword, line 193: '...d terms, such as MUST, MUST NOT, REQUI...' RFC 2119 keyword, line 194: '... SHOULD NOT, MAY, NEED NOT, and O...' (79 more instances...) == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document updates RFC2910, but the abstract doesn't seem to directly say this. It does mention RFC2910 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 174 has weird spacing: '...ions to the N...' == Line 281 has weird spacing: '...me name ind...' == Line 290 has weird spacing: '...ter use compl...' == Line 336 has weird spacing: '...ansport itse...' == Line 349 has weird spacing: '...on that attri...' == (1 more instance...) == Unrecognized Status in '[Target Category: standards track]', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) (Using the creation date from RFC2910, updated by this document, for RFC5378 checks: 1999-02-22) -- 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 (July 17, 2001) is 8319 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) == Missing Reference: 'RFC2119' is mentioned on line 195, but not defined == Missing Reference: 'US-ASCII' is mentioned on line 904, but not defined == Missing Reference: 'RFC2246' is mentioned on line 1120, but not defined ** Obsolete undefined reference: RFC 2246 (Obsoleted by RFC 4346) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-MIMEREG' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANA-PORTREG' ** Downref: Normative reference to an Informational RFC: RFC 1900 ** Obsolete normative reference: RFC 2373 (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2565 (Obsoleted by RFC 2910) ** Obsolete normative reference: RFC 2566 (Obsoleted by RFC 2911) ** Downref: Normative reference to an Experimental RFC: RFC 2567 ** Downref: Normative reference to an Experimental RFC: RFC 2568 ** Downref: Normative reference to an Experimental RFC: RFC 2569 ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617) ** Obsolete normative reference: RFC 2717 (Obsoleted by RFC 4395) ** Obsolete normative reference: RFC 2732 (Obsoleted by RFC 3986) ** Obsolete normative reference: RFC 2910 (Obsoleted by RFC 8010) ** Obsolete normative reference: RFC 2911 (Obsoleted by RFC 8011) Summary: 21 errors (**), 0 flaws (~~), 14 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Printing Protocol WG Hugo Parra 3 INTERNET-DRAFT Novell, Inc. 4 Tom Hastings 5 Updates: RFC 2910 and 2911 Xerox Corp. 6 [Target Category: standards track] July 17, 2001 7 Expires: January 17, 2002 9 Internet Printing Protocol (IPP): 10 The 'indp' Delivery Method for Event Notifications and Protocol/1.0 12 Copyright (C) The Internet Society (2001). All Rights Reserved. 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of [RFC2026]. Internet-Drafts are 18 working documents of the Internet Engineering Task Force (IETF), its 19 areas, and its working groups. Note that other groups may also 20 distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed as 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This document describes an extension to the Internet Printing 36 Protocol/1.0 (IPP) [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910]. 37 This document specifies the 'indp' Delivery Method and Protocol/1.0 38 for use with the "IPP Event Notifications and Subscriptions" 39 specification [ipp-ntfy]. When IPP Notification [ipp-ntfy] is 40 supported, the Delivery Method defined in this document is one of the 41 RECOMMENDED Delivery Methods for Printers to support. 43 This Delivery Method is a simple protocol consisting of a single 44 operation: the Send-Notifications operation which uses the same 45 encoding and transport as IPP [RFC2565, RFC2910]. For this Delivery 46 Method, when an Event occurs, the Printer immediately sends (pushes) 47 an Event Notification via the Send-Notifications operation to the 48 Notification Recipient specified in the Subscription Object. The 49 Event Notification content consists of Machine Consumable attributes 50 and a Human Consumable "notify-text" attribute. The Notification 51 Recipient returns a response to the Printer. 53 Table of Contents 55 1 Introduction.....................................................5 57 2 Terminology......................................................6 59 3 Model and Operation..............................................6 61 4 General Information..............................................7 63 5 Subscription object attributes..................................10 64 5.1 Subscription Template Attribute Conformance...................10 65 5.2 Additional Information about Subscription Template Attributes.10 66 5.2.1 notify-recipient-uri (uri)..................................10 67 5.3 Subscription Description Attribute Conformance................10 69 6 New Values for Existing Printer Description Attributes..........11 70 6.1 notify-schemes-supported (1setOf uriScheme)...................11 71 6.2 operations-supported (1setOf type2 enum)......................11 73 7 Attributes Only in Event Notifications..........................11 75 8 Operations for Notification.....................................12 76 8.1 Send-Notifications operation..................................12 77 8.1.1 Send-Notifications Request..................................12 78 8.1.2 Send-Notifications Response.................................17 80 9 Status Codes....................................................18 81 9.1 Additional Status Codes.......................................18 82 9.1.1 successful-ok-ignored-notifications (0x0004)................19 83 9.1.2 client-error-ignored-all-notifications (0x0416).............19 84 9.2 Status Codes returned in Event Notification Attributes Groups.19 85 9.2.1 client-error-not-found (0x0406).............................19 86 9.2.2 successful-ok-but-cancel-subscription (0x0006)..............20 88 10 Encoding and Transport.........................................20 89 10.1 Encoding of the Operation Layer..............................20 90 10.2 Encoding of Transport Layer..................................20 92 11 Conformance Requirements.......................................20 93 11.1 Conformance Requirements for Printers........................21 94 11.2 Conformance Requirements for INDP Notification Recipients....21 96 12 INDP URL Scheme................................................22 97 12.1 INDP URL Scheme Applicability and Intended Usage.............22 98 12.2 INDP URL Scheme Associated INDP Port.........................22 99 12.3 INDP URL Scheme Associated MIME Type.........................22 100 12.4 INDP URL Scheme Character Encoding...........................22 101 12.5 INDP URL Scheme Syntax in ABNF...............................23 102 12.5.1 INDP URL Examples..........................................23 103 12.5.2 INDP URL Comparisons.......................................24 105 13 IANA Considerations............................................24 106 13.1 Operation Registrations......................................25 107 13.2 Additional attribute value registrations for existing attributes 108 25 109 13.2.1 Additional values for the "notify-schemes-supported" Printer 110 attribute..............................................25 111 13.2.2 Additional values for the "operations-supported" Printer 112 attribute..............................................26 113 13.3 Status code Registrations....................................26 115 14 Internationalization Considerations............................26 117 15 Security Considerations........................................27 118 15.1 Security Conformance.........................................27 120 16 References.....................................................28 122 17 Author's Addresses.............................................29 124 18 Summary of Base IPP documents..................................30 126 19 Full Copyright Statement.......................................32 128 Tables 130 Table 1 - Information about the Delivery Method....................8 131 Table 2 - Operation-id assignments................................11 132 Table 3 - Attributes in Event Notification Content................15 133 Table 4 - Additional Attributes in Event Notification Content for Job 134 Events ........................................................16 135 Table 5 - Combinations of Events and Subscribed Events for "job- 136 impressions-completed" ........................................16 137 Table 6 - Additional Attributes in Event Notification Content for 138 Printer Events ................................................17 139 Table 7 - The "event-notification-attributes-tag" value...........20 141 1 Introduction 143 The "IPP Event Notifications and Subscriptions" document [ipp-ntfy] 144 defines an OPTIONAL extension to Internet Printing Protocol/1.0 (IPP) 145 [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910] (for a description 146 of the base IPP documents, see section 18). That extension defines 147 operations that a client can perform in order to create Subscription 148 Objects in a Printer and carry out other operations on them. A 149 Subscription Object represents a Subscription abstraction. A client 150 associates Subscription Objects with a particular Job by performing 151 the Create-Job-Subscriptions operation or by submitting a Job with 152 subscription information. A client associates Subscription Objects 153 with the Printer by performing a Create-Printer-Subscriptions 154 operation. Four other operations are defined for Subscription 155 Objects: Get-Subscriptions-Attributes, Get-Subscriptions, Renew- 156 Subscription, and Cancel-Subscription. The Subscription Object 157 specifies that when one of the specified Events occurs, the Printer 158 sends an asynchronous Event Notification to the specified 159 Notification Recipient via the specified Delivery Method (i.e., 160 protocol). 162 The "IPP Event Notifications and Subscriptions" document [ipp-ntfy] 163 specifies that each Delivery Method is defined in another document. 164 This document is one such document, and it specifies the 'indp' 165 Delivery Method. When IPP Notification [ipp-ntfy] is supported, the 166 Delivery Method defined in this document is one of the RECOMMENDED 167 Delivery Methods for Printers to support. This Delivery Method is a 168 simple protocol consisting of a single operation: the Send- 169 Notifications operation which uses the same encoding and transport as 170 IPP. This document defines version '1.0' of the protocol. 172 For the 'indp' Delivery Method, an IPP Printer sends (pushes) a Send- 173 Notifications operation request containing one or more Event 174 Notifications to the Notification Recipient specified in the 175 Subscription Object. The Event Notification content consists of 176 Machine Consumable attributes and a Human Consumable "notify-text" 177 attribute. 179 The Notification Recipient receives the Event Notification as a Send- 180 Notifications operation, in the same way as an IPP Printer receives 181 IPP operations. The Notification Recipient returns a response to the 182 Printer. 184 2 Terminology 186 This section defines the following terms that are used throughout 187 this document: 189 This document uses the same terminology as [RFC2911], such as 190 "client", "Printer", "attribute", "attribute value", "keyword", 191 "operation", "request", "response", and "support". 193 Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, 194 SHOULD NOT, MAY, NEED NOT, and OPTIONAL, have special meaning 195 relating to conformance as defined in RFC 2119 [RFC2119] and 196 [RFC2911] section 12.1. If an implementation supports the 197 extension defined in this document, then these terms apply; 198 otherwise, they do not. These terms define conformance to this 199 document only; they do not affect conformance to other documents, 200 unless explicitly stated otherwise. 202 Event Notification Attributes Group - The attributes group in a 203 request that contains Event Notification Attributes in a 204 request or response. 206 Other capitalized terms, such as Notification Recipient, Event 207 Notification, Compound Event Notification, Printer, etc., are 208 defined in [ipp-ntfy], have the same meanings, and are not 209 reproduced here. 211 3 Model and Operation 213 See [ipp-ntfy] for the description of the Event Notification Model 214 and Operation. This Delivery Method takes advantage of combining 215 several Event Notifications into a single Compound Event Notification 216 that is delivery by a single Send-Notification operation to a single 217 Notification Recipient. 219 When creating each Subscription object, the client supplies the 220 "notify-recipient" (uri) Subscription Template attribute. The 221 "notify-recipient" attribute specifies both a single Notification 222 Recipient that is to receive the Notifications when subsequent events 223 occur and the method for notification delivery that the IPP Printer 224 is to use. For the Notification Delivery Method defined in this 225 document, the notification method is 'indp' and the rest of the URI 226 is the address of the Notification Recipient to which the IPP Printer 227 will send the Send-Notifications operation. 229 The 'indp' Notification Delivery Method defined in this document uses 230 a client/server protocol paradigm. The "client" in this relationship 231 is the Printer described in [ipp-ntfy] while the "server" is the 232 Notification Recipient. The Printer invokes the Send-Notifications 233 operation to communicate IPP Event Notification contents to the 234 Notification Recipient. The Notification Recipient only conveys 235 information to the Printer in the form of responses to the operations 236 initiated by the Printer. 238 Printers that implement the 'indp' Notification Delivery Method will 239 need to include an HTTP client stack while Notification Recipients 240 that implement this Delivery Method will need to support an HTTP 241 server stack. See section 10.2 for more details. 243 If the client wants the Printer to send Event Notifications via the 244 'indp' Delivery Method, the client MUST choose a value for "notify- 245 recipient-uri" attribute which conforms to the rules of section 246 5.2.1. 248 When an Event occurs, the Printer MUST immediately: 250 1.Find all pertinent Subscription Objects P according to the rules of 251 section 9 of [ipp-ntfy], AND 253 2.Find the subset M of these Subscription Objects P whose "notify- 254 recipient-uri" attribute has a scheme value of 'indp', AND 256 3.For each Subscription Object in M, the Printer MUST 258 a)generate a Send-Notifications request as specified in section 259 8.1.1 AND 261 b)send the Send-Notifications request to the Notification 262 Recipient specified by the address part of the "notify- 263 recipient-uri" attribute value (see section 5.2.1). 265 If several events occur sufficiently close to one another for the 266 same or different Subscription objects, but with the same 267 Notification Recipient, the Printer MAY combine them into a single 268 Send-Notifications request using a separate Event Notification 269 Attributes group for each event (see section 8.1.1). 271 4 General Information 273 If a client or Printer supports this Delivery Method, Table 1 lists 274 its characteristics. 276 Table 1 - Information about the Delivery Method 278 Document Method conformance 'indp' realization 279 requirement 281 1. What is the URL scheme name indp 282 for the Delivery Method? 284 2. Is the Delivery Method is 285 REQUIRED, RECOMMENDED, or 286 OPTIONAL for an IPP Printer to 287 support? RECOMMENDED 289 3. What transport and delivery 290 protocol does the Printer use complete HTTP/1.1 stack 291 to deliver the Event [RFC2616] 292 Notification content, i.e., 293 what is the entire network 294 stack? A Printer MUST support a 296 4. Can several Event A Printer implementation MAY 297 Notifications be combined into combine several Event 298 a Compound Event Notification? Notifications into a single 299 Event Notifications request as 300 separate Event Notification 301 Attributes Groups, see section 302 8.1.1 304 5. Is the Delivery Method This Delivery Method is a push. 305 initiated by the Notification 306 Recipient (pull), or by the 307 Printer (push)? 309 6. Is the Event Notification Machine Consumable with the 310 content Machine Consumable or "notify-text" attribute being 311 Human Consumable? Human Consumable 313 7. What section in this document The representation and encoding 314 answers the following is the same as IPP. See 315 question? For a Machine section 8.1.1 316 Consumable Event Notification, 317 what is the representation and 318 encoding of values defined in 319 section 9.1 of [ipp-ntfy] and 320 the conformance requirements 321 thereof? For a Human 323 Document Method conformance 'indp' realization 324 requirement 326 thereof? For a Human 327 Consumable Event Notification, 328 what is the representation and 329 encoding of pieces of 330 information defined in section 331 9.2 of [ipp-ntfy] and the 332 conformance requirements 333 thereof? 335 8. What are the latency and 336 reliability of the transport itself (see [RFC2911]). 337 and delivery protocol? Same as for IPP/1.0 or IPP/1.1 339 9. What are the security aspects See section 15 340 of the transport and delivery 341 protocol, e.g., how it is 342 handled in firewalls? 344 10. What are the content length They are the same as for 345 restrictions? IPP/1.0 and IPP/1.1 itself (see 346 [RFC2911]). 348 11. What are the additional values A new Event Notifications 349 or pieces of information that attribute group (see section 350 a Printer sends in an Event 10.1) and additional status 351 Notification and the codes for use in the response 352 conformance requirements (see section 9) 353 thereof? 355 12. What are the additional None 356 Subscription Template and/or 357 Subscription Description 358 attributes and the conformance 359 requirements thereof? 361 13. What are the additional None 362 Printer Description attributes 363 and the conformance 364 requirements thereof? 366 The remaining sections of this document parallel the sections of 367 [ipp-ntfy]. 369 5 Subscription object attributes 371 This section defines the Subscription object conformance requirements 372 for Printers. 374 5.1 Subscription Template Attribute Conformance 376 The 'indp' Delivery Method has the same conformance requirements for 377 Subscription Template attributes as defined in [ipp-ntfy]. The 378 'indp' Delivery Method does not define any addition Subscription 379 Template attributes. 381 5.2 Additional Information about Subscription Template Attributes 383 This section defines additional information about Subscription 384 Template attributes defined in [ipp-ntfy]. 386 5.2.1 notify-recipient-uri (uri) 388 This section describes the syntax of the value of this attribute for 389 the 'indp' Delivery Method. The syntax for values of this attribute 390 for other Delivery Method is defined in other Delivery Method 391 Documents. 393 In order to support the 'indp' Delivery Method and Protocol, the 394 Printer MUST support the following syntax: 396 The 'indp://' URI scheme. The remainder of the URI indicates 397 the host name or host address (and optional path) of the 398 Notification Recipient that is to receive the Send- 399 Notification operation. See section 12 for a complete 400 definition of the syntax of the INDP URL. 402 5.3 Subscription Description Attribute Conformance 404 The 'indp' Delivery Method has the same conformance requirements for 405 Subscription Description attributes as defined in [ipp-ntfy]. The 406 'indp' Delivery Method does not define any addition Subscription 407 Description attributes. 409 6 New Values for Existing Printer Description Attributes 411 This Delivery Method does not define any additional Printer 412 Description attribute from those defined in [ipp-ntfy]. However, it 413 does define additional values for existing Printer Description 414 attributes defined in [ipp-ntfy]. This section defines those 415 additional values. 417 6.1 notify-schemes-supported (1setOf uriScheme) 419 The following value of the "notify-schemes-supported" Printer 420 attribute (see [ipp-ntfy] section 5.3.1) is added in order to support 421 the new Delivery Method defined in this document: 423 'indp' - The IPP Notification Delivery Method defined in this 424 document. 426 6.2 operations-supported (1setOf type2 enum) 428 Table 2 lists the value of the "operation-id" operation parameter 429 (see [RFC2911]) and the value of the "operations-supported" Printer 430 Description attribute (see [RFC2911]) added in order to support the 431 new operation defined in this document. The operation-id is assigned 432 in the same name space as other operations that a Printer supports. 433 However, a Printer MUST NOT include this value in its "operations- 434 supported" attribute unless it can accept the Send-Notifications 435 request. 437 Table 2 - Operation-id assignments 439 Value Operation Name 441 0x001D Send-Notifications 443 7 Attributes Only in Event Notifications 445 No additional attributes are defined only for use in Event 446 Notifications besides those defined in [ipp-ntfy]. 448 8 Operations for Notification 450 This section defines the operation for Event Notification using the 451 'indp' Delivery Method. 453 There is only one operation defined: Send-Notifications. Section 454 6.2 assigns of the "operation-id" for the Send-Notifications 455 operation and the following section defined the operation. 457 8.1 Send-Notifications operation 459 This REQUIRED operation allows a Printer to send one or more Event 460 Notifications to a Notification Recipient using HTTP. 462 The Printer composes the information defined for an IPP Notification 463 [ipp-ntfy] and sends it using the Send-Notifications operation to the 464 Notification Recipient supplied in the Subscription object. The 465 ordering of separate Send-Notifications operations that a Printer 466 sends MUST follow the "Event Notification Ordering" requirements in 467 [ipp-ntfy] section 9. 469 The Send-Notifications operation uses the operations model defined by 470 IPP [RFC2566]. This includes, the use of a URI as the identifier for 471 the target of each operation, the inclusion of a version number, 472 operation-id, and request-id in each request, and the definition of 473 attribute groups. The Send-Notifications operation uses the Operation 474 Attributes group, but currently has no need for the Unsupported 475 Attributes, Printer Object Attributes, and Job-Object Attributes 476 groups. However, it uses a new attribute group, the Event 477 Notification Attributes group. 479 The Notification Recipient MUST accept the request in any state. 480 There is no state defined for the Notification Recipient for this 481 Delivery Method. 483 Access Rights: Notification Recipient MAY enforce access rights. If 484 the Printer receives a rejection with these status codes: 'client- 485 error-forbidden', 'client-error-not-authenticated', or 'client-error- 486 not-authorized' status code , the Printer SHOULD cancel the 487 subscription. 489 8.1.1 Send-Notifications Request 491 Every operation request MUST contains the following parameters (see 492 [RFC2911] section 3.1.1): 494 - a "version-number" '1.0' - the version of the 'indp' 495 protocol is '1.0'. 496 - an "operation-id" - the value defined in Table 2 497 - a "request-id" - the request id (see [RFC2911] section 3.1.2). 499 The following groups of attributes MUST be part of the Send- 500 Notifications Request: 502 Group 1: Operation Attributes 503 Natural Language and Character Set: 504 The "attributes-charset" and "attributes-natural-language" 505 attributes as defined in [RFC2911] section 3.1.4.1. 507 The Printer MUST use the values of "notify-charset" and 508 "notify-natural-language", respectively, from one Subscription 509 Object associated with the Event Notifications in this request. 511 Normally, there is only one matched Subscription Object, or the 512 value of the "notify-charset" and "notify-natural-language" 513 attributes is the same in all Subscription Objects. If not, the 514 Printer MUST pick one Subscription Object from which to obtain 515 the value of these attributes. The algorithm for picking the 516 Subscription Object is implementation dependent. The choice of 517 natural language is not critical because 'text' and 'name' 518 values can override the "attributes-natural-language" Operation 519 attribute. The Printer's choice of charset is critical because 520 a bad choice may leave it unable to send some 'text' and 'name' 521 values accurately. 523 Target: 524 A copy of the Subscription object's "notify-recipient-uri" 525 (uri) attribute which is the target of this operation as 526 described in [RFC2911] section 3.1.5, i.e., the URI of the 527 'indp' Notification Recipient (see section 5.2.1). 529 Group 2 to N: Event Notification Attributes 531 In each group 2 to N, each attribute is encoded using the IPP 532 rules for encoding attributes [RFC2910] and the attributes 533 within a group MAY be encoded in any order. Note: the Get-Jobs 534 response in [RFC2911] acts as a model for encoding multiple 535 groups of attributes. The entire request is considered a 536 single Compound Event Notification and MUST follow the "Event 537 Notification Ordering" requirements for Event Notifications 538 within a Compound Event Notification specified in [ipp-ntfy] 539 section 9. 541 Each Event Notification Group MUST contain all of attributes 542 specified in [ipp-ntfy] section 9.1 ("Content of Machine 543 Consumable Event Notifications") with exceptions denoted by 544 asterisks in the tables below. 546 The tables below are copies of the tables in [ipp-ntfy] section 547 9.1 ("Content of Machine Consumable Event Notifications") 548 except that each cell in the "Sends" column is a "MUST". 550 For an Event Notification for all Events, the Printer sends the 551 following attributes. 553 Table 3 - Attributes in Event Notification Content 555 Source Value Sends Source Object 557 notify-subscription-id (integer(1:MAX)) MUST Subscription 559 notify-printer-uri (uri) MUST Subscription 561 notify-subscribed-event (type2 keyword) MUST Event 562 Notification 564 printer-up-time (integer(MIN:MAX)) MUST Printer 566 printer-current-time (dateTime) MUST * Printer 568 notify-sequence-number (integer (0:MAX)) MUST Subscription 570 notify-charset (charset) MUST Subscription 572 notify-natural-language (naturalLanguage) MUST Subscription 574 notify-user-data (octetString(63)) MUST ** Subscription 576 notify-text (text (MAX)) MUST Event 577 Notification 579 attributes from the "notify-attributes" MUST *** Printer 580 attribute, if any 582 attributes from the "notify-attributes" MUST *** Job 583 attribute, if any 585 attributes from the "notify-attributes" MUST *** Subscription 586 attribute, if any 588 * The Printer MUST send "printer-current-time" if and only if 589 it supports the "printer-current-time" attribute on the Printer 590 object. 592 ** If the associated Subscription Object does not contain a 593 "notify-user-data" attribute, the Printer MUST send an octet- 594 string of length 0. 596 *** If the "notify-attributes" attribute is present on the 597 Subscription Object, the Printer MUST send all attributes 598 specified by the "notify-attributes" attribute. Note: if the 599 Printer doesn't support the "notify-attributes" attribute, it 600 is not present on the associated Subscription Object and the 601 Printer does not send any client-requested attributes. 603 For Event Notifications for Job Events, the Printer sends the 604 following additional attributes shown in Table 4. 606 Table 4 - Additional Attributes in Event Notification Content for 607 Job Events 609 Source Value Sends Source 610 Object 612 job-id (integer(1:MAX)) MUST Job 614 job-state (type1 enum) MUST Job 616 job-state-reasons (1setOf type2 keyword) MUST Job 618 job-impressions-completed (integer(0:MAX)) MUST * Job 620 * The Printer MUST send the "job-impressions-completed" 621 attribute in an Event Notification only for the combinations of 622 Events and Subscribed Events shown in Table 5. 624 Table 5 - Combinations of Events and Subscribed Events for "job- 625 impressions-completed" 627 Job Event Subscribed Job Event 629 'job-progress' 'job-progress' 631 'job-completed' 'job-completed' 633 'job-completed' 'job-state-changed' 635 For Event Notification for Printer Events, the Printer sends 636 the following additional attributes shown in Table 6. 638 Table 6 - Additional Attributes in Event Notification Content for 639 Printer Events 641 Source Value Sends Source Object 643 printer-state (type1 enum) MUST Printer 645 printer-state-reasons (1setOf type2 keyword) MUST Printer 647 printer-is-accepting-jobs (boolean) MUST Printer 649 8.1.2 Send-Notifications Response 651 The Notification Recipient MUST return (to the client which is the 652 Printer) the following sets of attributes as part of a Send- 653 Notifications response: 655 Every operation response contains the following REQUIRED parameters 656 (see [RFC2911] section 3.1.1}: 658 - a "version-number" 659 - a "status-code" 660 - the "request-id" that was supplied in the corresponding request 662 Group 1: Operation Attributes 664 Status Message: 665 As defined in [RFC2911]. 667 The Notification Recipient can return any status codes defined 668 in [RFC2911] and section 9.1 that applies to all of the Event 669 Notification Attribute groups. The following is a description 670 of the important status codes: 672 'successful-ok': the Notification Recipient received all of 673 the Event Notification Attribute Groups and was expecting 674 each of them. 676 'successful-ok-ignored-notifications': the Notification 677 Recipient was able to consume some, but not all of the 678 Event Notification Attributes Groups sent. The Event 679 Notification Attributes Groups with a "notify-status- 680 code" attribute are the ones that were ignored or are to 681 be canceled. 683 'client-error-ignored-all-notifications': the Notification 684 Recipient was unable to consume any of the Event 685 Notification Attributes Groups sent. The Event 686 Notification Attributes Groups with a "notify-status- 687 code" attribute are the ones that were ignored or are to 688 be canceled. 690 Natural Language and Character Set: 691 The "attributes-charset" and "attributes-natural-language" 692 attributes as defined in [RFC2911] section 3.1.4.1. 694 Group 2 to N: Notification Attributes 696 These groups MUST be returned if and only if the "status-code" 697 parameter returned in Group 1 is anything but the 'successful-ok' 698 status code. 700 "notify-status-code" (type2 enum) 701 Indicates whether the Notification Recipient was able to 702 consume the n-th Notification Report as follows: 704 'successful-ok' - this Event Notification Attribute Group 705 was consumed 706 'client-error-not-found' - this Event Notification 707 Attribute Group was not able to be consumed. The Printer 708 MUST cancel the Subscription and MUST NOT attempt to send 709 any further Event Notifications from the associated 710 Subscription object. 711 'successful-ok-but-cancel-subscription' - the Event 712 Notification Attribute Group was consumed, but the 713 Notification Recipient wishes to cancel the Subscription 714 object. The Printer MUST cancel the Subscription and 715 MUST NOT attempt to send any further Event Notifications 716 from the associated Subscription object. 718 9 Status Codes 720 This section lists status codes whose meaning have been extended 721 and/or defined for returning in Event Notification Attribute Groups 722 as the value of the "notify-status-code" operation attribute. The 723 code values are allocated in the same space as the status codes in 724 [RFC2911]. 726 9.1 Additional Status Codes 728 The following status codes are defined as extensions for Notification 729 and are returned as the value of the "status-code" parameter in the 730 Operation Attributes Group of a response (see [RFC2911] section 731 3.1.6.1). Operations in this document can also return the status 732 codes defined in section 13 of [RFC2911]. The 'successful-ok' status 733 code is an example of such a status code. 735 9.1.1 successful-ok-ignored-notifications (0x0004) 737 The Notification Recipient was able to consume some, but not all, of 738 the Event Notifications Attributes Groups sent by the Printer in the 739 Send-Notifications request. See section 8.1.2 for further details. 741 9.1.2 client-error-ignored-all-notifications (0x0416) 743 The Notification Recipient was unable to consume any of the Event 744 Notification Attributes Groups sent by the Printer. The Event 745 Notification Attributes Groups with a "notify-status-code" attribute 746 are the ones that were ignored or are to be canceled. The Printer 747 MAY remove subscriptions for future events which this client was 748 unable to consume. 750 9.2 Status Codes returned in Event Notification Attributes Groups 752 This section contains values of the "notify-status-code" attribute 753 that the Notification Recipient returns in a Event Notification 754 Attributes Group in a response when the corresponding Event 755 Notification Attributes Group in the request: 757 1.was not consumed OR 759 2.was consumed, but the Notification Recipient wants to cancel the 760 corresponding Subscription object 762 The following sections are ordered in decreasing order of importance 763 of the status-codes. 765 9.2.1 client-error-not-found (0x0406) 767 This status code is defined in [RFC2911]. This document extends its 768 meaning and allows it to be returned in an Event Notification 769 Attributes Group of a response. 771 The Notification Recipient was unable to consume this Event 772 Notification Attributes Group because it was not expected. See 773 section 8.1.2 for further details. 775 9.2.2 successful-ok-but-cancel-subscription (0x0006) 777 The Notification Recipient was able to consume this Event 778 Notification Attributes Group that the Printer sent, but wants the 779 corresponding Subscription object to be canceled none-the-less. See 780 section 8.1.2 for further details. 782 10 Encoding and Transport 784 This section defines the encoding and transport used by the 'indp' 785 Delivery Method. 787 10.1 Encoding of the Operation Layer 789 The 'indp' Delivery Method uses the IPP operation layer encoding 790 described in [RFC2910] and the Event Notification Attributes Group 791 tag allocated by [ipp-ntfy] as shown in Table 7: 793 Table 7 - The "event-notification-attributes-tag" value 795 Tag Value (Hex) Meaning 797 0x07 "event-notification-attributes-tag" 799 10.2 Encoding of Transport Layer 801 The 'indp' Notification Delivery Method uses the IPP transport layer 802 encoding described in [RFC2910]. 804 It is REQUIRED that an 'indp' Notification Recipient implementation 805 support HTTP over the IANA-assigned well known system port assigned 806 to the 'indp' Delivery Method as its default port by IANA (see 807 section 13), though a Notification Recipient implementation MAY 808 support HTTP over some other port as well. 810 11 Conformance Requirements 812 This section defines conformance requirements for Printers and 813 Notification Recipients. 815 11.1 Conformance Requirements for Printers 817 The 'indp' Delivery Method is RECOMMENDED for a Printer to support. 819 IPP Printers that conform to this specification: 821 1.MUST meet the conformance requirements defined in [ipp-ntfy]. 823 2.MUST support the conformance requirements for Subscription object 824 attributes defined in section 5, including the syntax for the 825 "notify-recipient-uri" Subscription Object attribute defined in 826 section 5.2.1. 828 3.MUST support the conformance requirements for Printer Description 829 object attributes defined in section 6. 831 4.MUST support the 'indp' protocol by sending Event Notifications 832 using the Send-Notifications operation defined in section 8.1. 834 5.MUST send INDP URLs (e.g., in the "notify-recipient-uri" attribute 835 in 'Send-Notifications') that conform to the ABNF specified in 836 section 12.5 of this document; 838 6.MUST send the Send-Notifications operation via the port specified 839 in the INDP URL (if present) or otherwise via the IANA-assigned 840 well-known system port xxx [TBA by IANA]; 842 7.MUST convert INDP URLs for use in the Send-Notifications operation 843 to their corresponding HTTP URL forms for use in the HTTP layer by 844 the same rules used to convert IPP URLs to their corresponding 845 HTTP URL forms (see section 5 'IPP URL Scheme' in [RFC2910]). 847 11.2 Conformance Requirements for INDP Notification Recipients 849 INDP Notification Recipients that conform to this specification: 851 1.MUST accept Send-Notifications requests and return Send- 852 Notifications responses as defined in sections 8 and 9. 854 2.SHOULD reject received INDP URLs in "application/ipp" request 855 bodies (e.g., in the "notify-recipient-uri" attribute in 'Send- 856 Notifications') that do not conform to the ABNF for INDP URLs 857 specified in section 12.5 of this document; 859 3.MUST listen for INDP operations on IANA-assigned well-known system 860 port xxx [TBA by IANA], unless explicitly configured by system 861 administrators or site policies; 863 4.SHOULD NOT listen for INDP operations on any other port, unless 864 explicitly configured by system administrators or site policies. 866 12 INDP URL Scheme 868 12.1 INDP URL Scheme Applicability and Intended Usage 870 This section is intended for use in registering the "indp" URL scheme 871 with IANA and fully conforms to the requirements in [RFC2717]. This 872 document defines the "indp" URL (Uniform Resource Locator) scheme for 873 specifying the location of an INDP Notification Recipient object 874 which implements IPP Notification Delivery Protocol (INDP) specified 875 in this document. 877 The intended usage of the "indp" URL scheme is COMMON. 879 12.2 INDP URL Scheme Associated INDP Port 881 All INDP URLs which do NOT explicitly specify a port MUST be used 882 over IANA-assigned well-known system port xxx [TBA by IANA] for the 883 INDP protocol. 885 See: IANA Port Numbers Registry [IANA-PORTREG]. 887 12.3 INDP URL Scheme Associated MIME Type 889 All INDP protocol operations (requests and responses) MUST be 890 conveyed in an "application/ipp" MIME media type as registered in 891 [IANA-MIMEREG]. INDP URLs MUST refer to INDP Notification Recipient 892 objects which support this "application/ipp" MIME media type. 894 See: IANA MIME Media Types Registry [IANA-MIMEREG]. 896 12.4 INDP URL Scheme Character Encoding 898 The INDP URL scheme defined in this document is based on the ABNF for 899 the HTTP URL scheme defined in HTTP/1.1 [RFC2616], which is derived 900 from the URI Generic Syntax [RFC2396] and further updated by 901 [RFC2732] and [RFC2373] (for IPv6 addresses in URLs). The INDP URL 902 scheme is case-insensitive in the 'scheme' and 'host' (host name or 903 host address) part; however the 'abs_path' part is case-sensitive, as 904 in [RFC2396]. Code points outside [US-ASCII] MUST be hex escaped by 905 the mechanism specified in [RFC2396]. 907 12.5 INDP URL Scheme Syntax in ABNF 909 The IPP protocol places a limit of 1023 octets (NOT characters) on 910 the length of a URI (see section 4.1.5 'uri' in [RFC2911]). An INDP 911 Notification Recipient MUST return 'client-error-request-value-too- 912 long' (see section 13.1.4.10 in [RFC2911]) when a URI received in a 913 request is too long. 915 Note: INDP Notification Recipients ought to be cautious about 916 depending on URI lengths above 255 bytes, because some older client 917 or proxy implementations might not properly support these lengths. 919 INDP URLs MUST be represented in absolute form. Absolute URLs always 920 begin with a scheme name followed by a colon. For definitive 921 information on URL syntax and semantics, see "Uniform Resource 922 Identifiers (URI): Generic Syntax and Semantics" [RFC2396]. This 923 specification adopts the definitions of "port", "host", "abs_path", 924 and "query" from [RFC2396], as updated by [RFC2732] and [RFC2373] 925 (for IPv6 addresses in URLs). 927 The INDP URL scheme syntax in ABNF is as follows: 929 indp_URL = "indp:" "//" host [ ":" port ] [ abs_path [ "?" query ]] 931 If the port is empty or not given, IANA-assigned well-known system 932 port xxx [TBA by IANA] is assumed. The semantics are that the 933 identified resource (see section 5.1.2 of [RFC2616]) is located at 934 the INDP Notification Recipient listening for HTTP connections on 935 that port of that host, and the Request-URI for the identified 936 resource is 'abs_path'. 938 Note: The use of IP addresses in URLs SHOULD be avoided whenever 939 possible (see [RFC1900]). 941 If the 'abs_path' is not present in the URL, it MUST be given as "/" 942 when used as a Request-URI for a resource (see section 5.1.2 of 943 [RFC2616]). If a proxy receives a host name which is not a fully 944 qualified domain name, it MAY add its domain to the host name it 945 received. If a proxy receives a fully qualified domain name, the 946 proxy MUST NOT change the host name. 948 12.5.1 INDP URL Examples 950 The following are examples of valid INDP URLs for Notification 951 Recipient objects (using DNS host names): 953 indp://abc.com 954 indp://abc.com/listener 956 Note: The use of IP addresses in URLs SHOULD be avoided whenever 957 possible (see [RFC1900]). 959 The following literal IPv4 addresses: 961 192.9.5.5 ; IPv4 address in IPv4 style 962 186.7.8.9 ; IPv4 address in IPv4 style 964 are represented in the following example INDP URLs: 966 indp://192.9.5.5/listener 967 indp://186.7.8.9/listeners/tom 969 The following literal IPv6 addresses (conformant to [RFC2373]): 971 ::192.9.5.5 ; IPv4 address in IPv6 style 972 ::FFFF:129.144.52.38 ; IPv4 address in IPv6 style 973 2010:836B:4179::836B:4179 ; IPv6 address per RFC 2373 975 are represented in the following example INDP URLs: 977 indp://[::192.9.5.5]/listener 978 indp://[::FFFF:129.144.52.38]/listener 979 indp://[2010:836B:4179::836B:4179]/listeners/tom 981 12.5.2 INDP URL Comparisons 983 When comparing two INDP URLs to decide if they match or not, the 984 comparer MUST use the same rules as those defined for HTTP URI 985 comparisons in [RFC2616], with the sole following exception: 987 ? A port that is empty or not given MUST be treated as equivalent 988 to the well-known system port xxx [TBA by IANA] for that INDP 989 URL; 991 13 IANA Considerations 993 IANA shall register the indp URL scheme as defined in section 12 994 according to the procedures of [RFC2717] and assign a well-known 995 system port. 997 The rest of this section contains the exact information for IANA to 998 add to the IPP Registries according to the procedures defined in RFC 999 2911 [RFC2911] section 6. 1001 Note to RFC Editors: Replace RFC NNNN below with the RFC number 1002 for this document, so that it accurately reflects the content of 1003 the information for the IANA Registry. 1005 13.1 Operation Registrations 1007 The following table lists the operation defined in this document. 1008 This is to be registered according to the procedures in RFC 2911 1009 [RFC2911] section 6.4. 1011 Operations: Ref. 1012 Section: 1013 Send-Notifications operation RFC NNNN 8.1 1015 The resulting operation registration will be published in the 1016 ftp://ftp.iana.org/in-notes/iana/assignments/ipp/operations/ 1017 area. 1019 13.2 Additional attribute value registrations for existing attributes 1021 This section lists additional attribute value registrations for use 1022 with existing attributes defined in other documents. 1024 13.2.1 Additional values for the "notify-schemes-supported" Printer 1025 attribute 1027 The following table lists the uriScheme value defined in this 1028 document as an additional uriScheme value for use with the "notify- 1029 schemes-supported" Printer attribute defined in [ipp-ntfy]. This is 1030 to be registered according to the procedures in RFC 2911 [RFC2911] 1031 section 6.1. 1033 uriScheme Attribute Values: Ref. Section: 1034 indp RFC NNNN 6.1 1036 The resulting URI scheme attribute value registration will be 1037 published in the 1038 ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute- 1040 values/notify-schemes-supported/ 1041 area. 1043 13.2.2 Additional values for the "operations-supported" Printer 1044 attribute 1046 The following table lists the enum attribute value defined in this 1047 document as an additional type2 enum value for use with the 1048 "operations-supported" Printer attribute defined in [RFC2911]. This 1049 is to be registered according to the procedures in RFC 2911 [RFC2911] 1050 section 6.1. 1052 type2 enum Attribute Values: Value Ref. Section: 1053 Send-Notifications 0x001D RFC NNNN 6.2 1055 The resulting enum attribute value registration will be published in 1056 the 1057 ftp://ftp.iana.org/in-notes/iana/assignments/ipp/attribute- 1058 values/operations-supported/ 1059 area. 1061 13.3 Status code Registrations 1063 The following table lists all the status codes defined in this 1064 document. These are to be registered according to the procedures in 1065 RFC 2911 [RFC2911] section 6.6. 1067 Status codes: Ref. Section: 1068 successful-ok-ignored-notifications (0x0004) RFC NNNN 9.1.1 1069 client-error-ignored-all-notifications (0x0416) RFC NNNN 9.1.2 1071 Status Codes in Event Notification Attributes Groups: 1072 client-error-not-found (0x0406) RFC NNNN 9.2.1 1073 successful-ok-but-cancel-subscription (0x0006) RFC NNNN 9.2.2 1075 The resulting status code registrations will be published in the 1076 ftp://ftp.iana.org/in-notes/iana/assignments/ipp/status-codes/ 1077 area. 1079 14 Internationalization Considerations 1081 When the client requests Human Consumable form by supplying the 1082 "notify-text-format" operation attribute (see [ipp-ntfy]), the IPP 1083 Printer (or any Notification Service that the IPP Printer might be 1084 configured to use) supplies and localizes the text value of the 1085 "human-readable-report" attribute in the Notification according to 1086 the charset and natural language requested in the notification 1087 subscription. 1089 15 Security Considerations 1091 The IPP Model and Semantics document [RFC2911] discusses high level 1092 security requirements (Client Authentication, Server Authentication 1093 and Operation Privacy). Client Authentication is the mechanism by 1094 which the client proves its identity to the server in a secure 1095 manner. Server Authentication is the mechanism by which the server 1096 proves its identity to the client in a secure manner. Operation 1097 Privacy is defined as a mechanism for protecting operations from 1098 eavesdropping. 1100 The Notification Recipient can cancel unwanted Subscriptions created 1101 by other parties without having to be the owner of the subscription 1102 by returning the 'successful-ok-but-cancel-subscription' status code 1103 in the Send-Notifications response returned to the Printer. 1105 15.1 Security Conformance 1107 Printers (client) MAY support Digest Authentication [RFC2617]. If 1108 Digest Authentication is supported, then MD5 and MD5-sess MUST be 1109 supported, but the Message Integrity feature NEED NOT be supported. 1111 Notification Recipient (server) MAY support Digest Authentication 1112 [RFC2617]. If Digest Authentication is supported, then MD5 and MD5- 1113 sess MUST be supported, but the Message Integrity feature NEED NOT be 1114 supported. 1116 Notification Recipients MAY support TLS for client authentication, 1117 server authentication and operation privacy. If a Notification 1118 Recipient supports TLS, it MUST support the 1119 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA cipher suite as mandated by RFC 1120 2246 [RFC2246]. All other cipher suites are OPTIONAL. Notification 1121 recipients MAY support Basic Authentication (described in HTTP/1.1 1122 [RFC2616]) for client authentication if the channel is secure. TLS 1123 with the above mandated cipher suite can provide such a secure 1124 channel. 1126 16 References 1128 [ipp-iig] 1129 Hastings, T., Manros, C., Kugler, K, Holst H., Zehler, P., 1130 "Internet Printing Protocol/1.1: draft-ietf-ipp-implementers- 1131 guide-v11-03.txt, work in progress, July 17, 2001 1133 [ipp-ntfy] 1134 Isaacson, S., Martin, J., deBry, R., Hastings, T., Shepherd, M., 1135 Bergman, R., "Internet Printing Protocol/1.1: IPP Event 1136 Notifications and Subscriptions", , 1137 July 17, 2001. 1139 [IANA-MIMEREG] 1140 IANA MIME Media Types Registry. ftp://ftp.iana.org/in- 1142 notes/iana/assignments/media-types/ 1144 [IANA-PORTREG] 1145 IANA Port Numbers Registry. ftp://ftp.iana.org/in- 1147 notes/iana/assignments/port-numbers 1149 [RFC1900] 1150 B. Carpenter, Y. Rekhter. Renumbering Needs Work, RFC 1900, 1151 February 1996. 1153 [RFC2026] 1154 S. Bradner, "The Internet Standards Process -- Revision 3", RFC 1155 2026, October 1996. 1157 [RFC2373] 1158 R. Hinden, S. Deering. IP Version 6 Addressing Architecture, RFC 1159 2373, July 1998. 1161 [RFC2396] 1162 Berners-Lee, T. et al. Uniform Resource Identifiers (URI): Generic 1163 Syntax, RFC 2396, August 1998 1165 [RFC2565] 1166 Herriot, R., Butler, S., Moore, P., and R. Turner, "Internet 1167 Printing Protocol/1.0: Encoding and Transport", RFC 2565, April 1168 1999. 1170 [RFC2566] 1171 R. deBry, T. Hastings, R. Herriot, S. Isaacson, and P. Powell, 1172 "Internet Printing Protocol/1.0: Model and Semantics", RFC 2566, 1173 April 1999. 1175 [RFC2567] 1176 Wright, D., "Design Goals for an Internet Printing Protocol", RFC 1177 2567, April 1999. 1179 [RFC2568] 1180 Zilles, S., "Rationale for the Structure and Model and Protocol for 1181 the Internet Printing Protocol", RFC 2568, April 1999. 1183 [RFC2569] 1184 Herriot, R., Hastings, T., Jacobs, N., Martin, J., "Mapping between 1185 LPD and IPP Protocols", RFC 2569, April 1999. 1187 [RFC2616] 1188 R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. 1189 Leach, T. Berners-Lee, "Hypertext Transfer Protocol - HTTP/1.1", 1190 RFC 2616, June 1999. 1192 [RFC2617] 1193 J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. 1194 Luotonen, L. Stewart, "HTTP Authentication: Basic and Digest Access 1195 Authentication", RFC 2617, June 1999. 1197 [RFC2717] 1198 R. Petke and I. King, "Registration Procedures for URL Scheme 1199 Names", RFC 2717, November 1999. 1201 [RFC2732] 1202 R. Hinden, B. Carpenter, L. Masinter. Format for Literal IPv6 1203 Addresses in URL's, RFC 2732, December 1999. 1205 [RFC2910] 1206 Herriot, R., Butler, S., Moore, P., Tuner, R., "Internet Printing 1207 Protocol/1.1: Encoding and Transport", RFC 2910, September 2001. 1209 [RFC2911] 1210 R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell, 1211 "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, 1212 September 2001. 1214 17 Author's Addresses 1216 Hugo Parra 1217 Novell, Inc. 1218 1800 South Novell Place 1220 Provo, UT 84606 1222 Phone: 801-861-3307 1223 Fax: 801-861-2517 1224 e-mail: hparra@novell.com 1226 Tom Hastings 1227 Xerox Corporation 1228 737 Hawaii St. ESAE 231 1229 El Segundo, CA 90245 1231 Phone: 310-333-6413 1232 Fax: 310-333-5514 1233 e-mail: hastings@cp10.es.xerox.com 1235 IPP Web Page: http://www.pwg.org/ipp/ 1236 IPP Mailing List: ipp@pwg.org 1238 To subscribe to the ipp mailing list, send the following email: 1239 1) send it to majordomo@pwg.org 1240 2) leave the subject line blank 1241 3) put the following two lines in the message body: 1242 subscribe ipp 1243 end 1245 Implementers of this specification document are encouraged to join 1246 the IPP Mailing List in order to participate in any discussions of 1247 clarification issues and review of registration proposals for 1248 additional attributes and values. In order to reduce spam the 1249 mailing list rejects mail from non-subscribers, so you must subscribe 1250 to the mailing list in order to send a question or comment to the 1251 mailing list. 1253 18 Summary of Base IPP documents 1255 The base IPP documents includes: 1257 Design Goals for an Internet Printing Protocol [RFC2567] 1258 Rationale for the Structure and Model and Protocol for the 1259 Internet Printing Protocol [RFC2568] 1260 Internet Printing Protocol/1.1: Model and Semantics [RFC2911] 1261 Internet Printing Protocol/1.1: Encoding and Transport [RFC2910] 1262 Internet Printing Protocol/1.1: Implementer's Guide [ipp-iig] 1263 Mapping between LPD and IPP Protocols [RFC2569] 1264 Internet Printing Protocol (IPP): IPP Event Notifications and 1265 Subscriptions [ipp-ntfy] 1267 The "Design Goals for an Internet Printing Protocol" document takes a 1268 broad look at distributed printing functionality, and it enumerates 1269 real-life scenarios that help to clarify the features that need to be 1270 included in a printing protocol for the Internet. It identifies 1271 requirements for three types of users: end users, operators, and 1272 administrators. It calls out a subset of end user requirements that 1273 are satisfied in IPP/1.0 [RFC2566, RFC2565]. A few OPTIONAL operator 1274 operations have been added to IPP/1.1 [RFC2911, RFC2910]. 1276 The "Rationale for the Structure and Model and Protocol for the 1277 Internet Printing Protocol" document describes IPP from a high level 1278 view, defines a roadmap for the various documents that form the suite 1279 of IPP specification documents, and gives background and rationale 1280 for the IETF working group's major decisions. 1282 The "Internet Printing Protocol/1.1: Model and Semantics" document 1283 describes a simplified model with abstract objects, their attributes, 1284 and their operations that are independent of encoding and transport. 1285 It introduces a Printer and a Job object. The Job object optionally 1286 supports multiple documents per Job. It also addresses security, 1287 internationalization, and directory issues. 1289 The "Internet Printing Protocol/1.1: Encoding and Transport" document 1290 is a formal mapping of the abstract operations and attributes defined 1291 in the model document onto HTTP/1.1 [RFC2616]. It defines the 1292 encoding rules for a new Internet MIME media type called 1293 "application/ipp". This document also defines the rules for 1294 transporting a message body over HTTP whose Content-Type is 1295 "application/ipp". This document defines the 'ipp' scheme for 1296 identifying IPP printers and jobs. 1298 The "Internet Printing Protocol/1.1: Implementer's Guide" document 1299 gives insight and advice to implementers of IPP clients and IPP 1300 objects. It is intended to help them understand IPP/1.1 and some of 1301 the considerations that may assist them in the design of their client 1302 and/or IPP object implementations. For example, a typical order of 1303 processing requests is given, including error checking. Motivation 1304 for some of the specification decisions is also included. 1306 The "Mapping between LPD and IPP Protocols" document gives some 1307 advice to implementers of gateways between IPP and LPD (Line Printer 1308 Daemon) implementations. 1310 The "Internet Printing Protocol (IPP): IPP Event Notifications and 1311 Subscriptions" document defines an extension to IPP/1.0 [RFC2566, 1312 RFC2565] and IPP/1.1 [RFC2911, RFC2910]. This extension allows a 1313 client to subscribe to printing related Events by creating a 1314 Subscription Object and defines the semantics for delivering 1315 asynchronous Event Notifications to the specified Notification 1316 Recipient via a specified Delivery Method (i.e., protocols) defined 1317 in (separate) Delivery Method documents. 1319 19 Full Copyright Statement 1321 Copyright (C) The Internet Society (2001). All Rights Reserved. 1323 This document and translations of it may be copied and furnished to 1324 others, and derivative works that comment on or otherwise explain it 1325 or assist in its implementation may be prepared, copied, published 1326 and distributed, in whole or in part, without restriction of any 1327 kind, provided that the above copyright notice and this paragraph are 1328 included on all such copies and derivative works. However, this 1329 document itself may not be modified in any way, such as by removing 1330 the copyright notice or references to the Internet Society or other 1331 Internet organizations, except as needed for the purpose of 1332 developing Internet standards in which case the procedures for 1333 copyrights defined in the Internet Standards process must be 1334 followed, or as required to translate it into languages other than 1335 English. 1337 The limited permissions granted above are perpetual and will not be 1338 revoked by the Internet Society or its successors or assigns. 1340 This document and the information contained herein is provided on an 1341 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1342 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1343 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1344 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1345 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1347 Acknowledgement 1349 Funding for the RFC Editor function is currently provided by the 1350 Internet Society.