idnits 2.17.1 draft-lutz-print-types-00.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-19) 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 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 an Authors' Addresses Section. ** There are 2 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 72 has weird spacing: '...tration metho...' -- 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 (January 6, 1997) is 9965 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) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group R. Lutz 2 Internet-Draft: draft-lutz-print-types-00.txt MFPA 3 January 6, 1997 5 MIME media-types for Print Formats 7 Status of this Memo 9 This document is an Internet-Draft. Internet-Drafts are 10 working documents of the Internet Engineering Task Force 11 (IETF), its areas, and its working groups. Note that 12 other groups may also distribute working documents as 13 Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum 16 of six months and may be updated, replaced, or obsoleted 17 by other documents at any time. It is inappropriate to 18 use Internet- Drafts as reference material or to cite 19 them other than as "work in progress." 21 To learn the current status of any Internet-Draft, please 22 check the "1id-abstracts.txt" listing contained in the 23 Internet- Drafts Shadow Directories on ftp.is.co.za 24 (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific 25 Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US 26 West Coast). 28 Abstract 30 This memo defines media-type designators for various 31 printer control file formats which are popularly used in 32 the industry, and proposes a means to correlate the 33 printer interpreter types as specified in the Printer MIB 34 (RFC-1759). 36 1. Overview 38 MIME media-types describe the format of MIME objects, 39 which are used in internet email (SMTP), web applications 40 (HTTP), and others. MIME media types such as 41 application/postscript and text/plain are examples of 42 print formats which are interpreted by many printers. 43 However, there are many other file formats whice are 44 frequently used with printers which are not supported by 45 MIME media-type designations. This document proposes a 46 set of MIME media-type designations for these popular 47 print file formats. The result of this work should 48 support transport of these printer formats to enable 49 internet printing scenarios. 51 2. Definition Method 53 The printer MIB (RFC-1759) is used as a source of much of 54 the information in this document. Each section of this 55 document is formatted according to the MIME media-type 57 draft-lutz-print-types-00.txt January, 97 59 registration procedure (RFC-1590). 61 RFC 1759 (_Printer MIB_) contains a group, 62 PrtInterpreterLang, with objects that identify various 63 file formats and protocols which are used to submit jobs 64 and interact with print equipment. The purpose for this 65 list is to allow a network administrator to garner 66 information regarding the capabilities or view and set 67 current settings of a printer peripheral. 69 MIME (Multimedia Internet Mail Extensions) contain a 70 registration method and registry for defining various 71 media-types (or _data formats_). The purpose of this 72 registration method and registry is to allow transfer of 73 file data via email MIME body parts and allow the 74 receiver to handle each part in a graceful manner. 76 The ability to reference file formats is important in the 77 Multifunction product area as we are submitting jobs to 78 dial-up or email-remote printers. The lack of a single 79 registry has been a key problem in this area. 81 2.1 OBSERVATIONS 83 The MIME registry is targeted at _data formats_ and does 84 not specify protocols which would not be transportable 85 using internet store-and-forward mail technology. 86 Therefore, some of the objects contained in 87 prtInterpreterLang group would probably not be 88 appropriate for the MIME registry. For example, TIPSI 89 (IEEE-1284.1) is a good candidate for this characteristic 90 since TIPSI requires bidirectional communication to 91 operate. Such formats may be compatible with certain 92 limitations. This is they way that Postscript is treated. 93 This document will not attempt to sanatize any formats 94 that require a special protocol. 96 RFC-1759 does not specify exact versions as a part of the 97 prtInterpreterLang group, especially when the language 98 can self-identify or gracefully handle various 99 generations of the same format. In some cases, a given 100 interpreter will not gracefully handle the various 101 generations, and yet the version is not specified. 103 There may be some need to refine RFC-1759 or other 104 documents as a result of completing this work. 106 3. Method to handle Vendor-specific formats 108 It is generally the case that the Interpreter Languages 109 as defined by RFC-1759 are vendor-specific and are not 110 ietf or public standards. The MIME designation will be 111 generated using a standard "recipe" to allow easy 112 correlation with RFC-1759, without unduly burdening the 114 draft-lutz-print-types-00.txt January, 97 116 MIB or the MIME media-types with absolute 117 synchronization. The general recipe is to form the MIME 118 media type as follows (Angle brackets are to group 119 syntactical elements and do not occur in the string; 120 square brackets indicates optional): 122 vnd.-[;Version=] 126 For example, for LangPCL, Level 3, the resulting string 127 is: 129 application/vnd.hp-pcl;version=3 131 4. Prior Generations also accepted by the media-type 133 If a given device claims that it can handle a given 134 printer media-type by examining the MIB 135 prtInterpreterLang object, it may also be able to handle 136 other media-types of prior generations. A maker of a MIME 137 object should designate the minimum media-type 138 designation possible. A device should claim support in 139 the device MIB of the latest generation of a given media- 140 type which has several generations. 142 This document includes a profile which defines the exact 143 MIB field contents and their relation to the proposed 144 MIME types. The use of the recipe to form the MIME media- 145 type designation will allow the vendor that is actually 146 responsible for the given format to enhance the format 147 without revision of this profile. 149 4. Summary of the printer media-types 151 In the table below, the term "Also Accepted" indicates 152 that the device would also accept another generation of 153 the format or another format by inspecting the object. 154 There is usually no use in referencing more than a single 155 prior generation since it can also reference other 156 generations, however, in some cases, more than one 157 language is lumped together with some form of automatic 158 sensing. 160 In the table below, the columns are defined as follows: 161 "Family" prtInterpreterLangFamily string 162 "Code" numeric entry of Printer MIB 163 "Level" prtInterpreterLangLevel string 165 If a media-type string is defined, a prior generation or 166 other format which is also parsed and interpreted by this 167 interpreter if the printer MIB indicates this format is 168 supported. 170 draft-lutz-print-types-00.txt January, 97 172 Family Code Level media-type Notes 173 (Prior Generation) 174 =============== ==== ===== ===================== ====== 175 other 1 x NOTE 1 176 langPCL 3 3 vnd.hp-pcl;version=3 177 langPCL 3 4 vnd.hp-pcl;version=4 178 (vnd.hp-pcl;version=3) 179 langPCL 3 5 vnd.hp-pcl;version=5 180 (vnd.hp-pcl;version=4) 181 (vnd.hp-hpgl;version=2) 182 langPCL 3 5e vnd.hp-pcl;version=5e 183 (vnd.hp-pcl;version=5) 184 langHPGL 4 2 vnd.hp-hpgl;version=2 185 langPJL 5 1 vnd.hp-pjl;version=1 186 langPS 6 1 postscript;version=1 187 langPS 6 2 postscript;version=2 188 (postscript;version=1) 189 langPS 6 3 postscript;version=3 190 (postscript;version=2) 191 langPSPrinter 42 vnd.adobe-PSPrinter NOTE 2 192 langIPDS 7 vnd.ibm-ipds NOTE 2 193 langPPDS 8 vnd.lexmark-ppds 194 langEscapeP 9 vnd.epson-escapep 195 langEpson 10 80 vnd.epson-fx;version=80 NOTE 3 196 langEpson 10 100 vnd.epson-fx;version=100 NOTE 3 197 langDDIF 11 vnd.dec-dx 198 langInterpress 12 NOTE 1 199 langISO6429 13 text/iso6429 200 langLineData 14 text/linedata 201 langMODCA 15 vnd.ibm-modca NOTE 2 202 langREGIS 16 vnd.dec-regis 203 langSCS 17 NOTE 1 204 langSPDL 18 iso10180 205 langTEK4014 19 vnd.tek-4014 206 langPDS 20 NOTE 1 207 langIGP 21 NOTE 1 208 langCodeV 22 vnd.qms-codev 209 langDSCDSE 23 NOTE 1 210 langWPS 24 NOTE 1 211 langLN03 25 vnd.dec-ln03 212 langCCITT 26 image/g3fax 213 langQUIC 27 vnd.qms-quic 214 langCPAP 28 vnd.dec-cpap 215 langDecPPL 29 vnd.dec-ppl 216 langSimpleText 30 text/plain NOTE 4 217 langNPAP 31 NOTE 1 218 langDOC 32 vnd.qms-doc NOTE 2 219 langimPress 33 vnd.qms-impress 220 langPinwriter 34 vnd.nec-pinwriter 221 langNEC201PL 36 vnd.nec-201pl 222 langAutomatic 37 NOTE 5 223 langPages 38 vnd.ibm-pages 225 draft-lutz-print-types-00.txt January, 97 227 langLIPS 39 vnd.cie-lips 228 langTIFF 40 image/tiff 229 langDiagnostic 41 octet-stream 230 langCaPSL 43 vnd.canon-psl 231 langEXCL 44 vnd.talaris-excl 232 langLCDS 45 vnd.xerox-lcds 233 langXES 46 vnd.xerox-xes 234 =============== ==== ===== ===================== ====== 236 NOTES 237 1: No media-type definable. 238 2: Is this really mappable? 239 3: Level is just a guess. 240 4: Need charset 241 5: automatic will need to list the media-types accepted. 243 draft-lutz-print-types-00.txt January, 97 245 APPENDIX 1: Media-Type Registrations 247 The following are proposed registrations of media-types 248 required for those printer interpreters listed in RFC- 249 1759. Not all of these types may be worthwhile additions 250 as MIME media-types. At this time, there are many missing 251 published specifications and contact names. 253 ====================================================== 255 Media Type name: application 256 Media subtype name: vnd.hp-pcl 257 Required parameters: none 258 Optional parameters: 259 version=3 indicates HP PCL-3 (default) 260 version=4 indicates HP PCL-4 261 version=5 indicates HP PCL-5 262 version=5e indicates HP PCL-5e 263 Encoding considerations: 264 base-64 preferred 265 (is quoted-printable a good choice?) 266 Security considerations: 267 Delivery of this format to a printer which is not 268 capable of parsing the format may result in poor printer 269 behavior. 270 Published specification: 271 HP-PCL5: PCL5 Printer Language Technical Reference 272 Manual, HP Manual Part No. 5961-0888. 273 Contact: 275 ====================================================== 277 Media Type name: application 278 Media subtype name: vnd.hp-pgl 279 Required parameters: none 280 Optional parameters: 281 version=2 indicates HPGL/2 282 Encoding considerations: 283 base-64 284 Security considerations: 285 Delivery of this format to a printer which is not 286 capable of parsing the format may result in poor printer 287 behavior. 288 Published specification: 289 HPGL manual .... 290 Contact: 292 ====================================================== 294 NOTE the following is an amendment of an existing media- 295 type since the "version=#" parameter is added as an 296 optional parameter. 298 Media Type name: application 300 draft-lutz-print-types-00.txt January, 97 302 Media subtype name: postscript 303 Required parameters: none 304 Optional parameters: 305 version=1 indicates Postscript Level 1 (default) 306 version=2 indicates Postscript Level 2 307 version=3 indicates Postscript Level 3 308 Encoding considerations: 309 base-64 310 Security considerations: 311 Delivery of this format to a printer which is not 312 capable of parsing the format may result in poor printer 313 behavior. See RFC ???? for cautionary statements with 314 regard to the use of Postscript. 315 Published specification: 316 Postscript Language Reference Manual, Adobe Systems Inc., 317 ISBN 0-201-10174-2 318 Postscript Language Level - 2 Reference Manual, Adobe 319 Systems Inc. 320 Contact: 322 ====================================================== 324 Media Type name: application 325 Media subtype name: vnd.adobe-PSPrinter 326 Required parameters: none 327 Optional parameters: none 328 Encoding considerations: 329 base-64 330 Security considerations: 331 Delivery of this format to a printer which is not 332 capable of parsing the format may result in poor printer 333 behavior. 334 Published specification: 335 Contact: 337 ====================================================== 339 Media Type name: application 340 Media subtype name: ibm-ipds 341 Required parameters: none 342 Optional parameters: none 343 Encoding considerations: 344 base-64 345 Security considerations: 346 Delivery of this format to a printer which is not 347 capable of parsing the format may result in poor printer 348 behavior. 349 Published specification: 350 Contact: 352 ====================================================== 354 Media Type name: application 355 Media subtype name: vnd.lexmark-ppds 357 draft-lutz-print-types-00.txt January, 97 359 Required parameters: none 360 Optional parameters: none 361 Encoding considerations: 362 base-64 363 Security considerations: 364 Delivery of this format to a printer which is not 365 capable of parsing the format may result in poor printer 366 behavior. 367 Published specification: 368 Contact: 370 ====================================================== 372 Media Type name: application 373 Media subtype name: epson-escapep 374 Required parameters: none 375 Optional parameters: none 376 Encoding considerations: 377 base-64 378 Security considerations: 379 Delivery of this format to a printer which is not 380 capable of parsing the format may result in poor printer 381 behavior. 382 Published specification: 383 Contact: 385 ====================================================== 387 Media Type name: application 388 Media subtype name: lexmark-ppds 389 Required parameters: none 390 Optional parameters: none 391 Encoding considerations: 392 base-64 393 Security considerations: 394 Delivery of this format to a printer which is not 395 capable of parsing the format may result in poor printer 396 behavior. 397 Published specification: 398 Contact: 400 ====================================================== 402 Media Type name: application 403 Media subtype name: epson-fx 404 Required parameters: none 405 Optional parameters: 406 version=80 indicates fx-80 407 version=100 indicates fx-100 408 Encoding considerations: 409 base-64 preferred 410 (is quoted-printable a good choice?) 412 draft-lutz-print-types-00.txt January, 97 414 Security considerations: 415 Delivery of this format to a printer which is not 416 capable of parsing the format may result in poor printer 417 behavior. 418 Published specification: 419 Contact: 421 ====================================================== 423 Media Type name: application 424 Media subtype name: vnd.dec-dx 425 Required parameters: none 426 Optional parameters: none 427 Encoding considerations: 428 base-64 429 Security considerations: 430 Delivery of this format to a printer which is not 431 capable of parsing the format may result in poor printer 432 behavior. 433 Published specification: 434 Contact: 436 ====================================================== 438 Media Type name: text 439 Media subtype name: iso6429 440 Required parameters: none 441 Optional parameters: none 442 Encoding considerations: 443 quoted printable 444 Security considerations: 445 Delivery of this format to a printer which is not 446 capable of parsing the format may result in poor printer 447 behavior. 448 Published specification: 449 ISO-6429 450 Contact: 452 ====================================================== 454 Media Type name: text 455 Media subtype name: linedata 456 Required parameters: none 457 Optional parameters: none 458 Encoding considerations: 459 quoted printable 460 Security considerations: 461 Delivery of this format to a printer which is not 462 capable of parsing the format may result in poor printer 463 behavior. 464 Published specification: 465 Contact: 467 ====================================================== 469 draft-lutz-print-types-00.txt January, 97 471 Media Type name: application 472 Media subtype name: vnd.ibm-modca 473 Required parameters: none 474 Optional parameters: none 475 Encoding considerations: 476 base-64 477 Security considerations: 478 Delivery of this format to a printer which is not 479 capable of parsing the format may result in poor printer 480 behavior. 481 Published specification: 482 Contact: 484 ====================================================== 486 Media Type name: application 487 Media subtype name: vnd.dec-regis 488 Required parameters: none 489 Optional parameters: none 490 Encoding considerations: 491 base-64 492 Security considerations: 493 Delivery of this format to a printer which is not 494 capable of parsing the format may result in poor printer 495 behavior. 496 Published specification: 497 Contact: 499 ====================================================== 501 Media Type name: application 502 Media subtype name: iso10180 503 Required parameters: none 504 Optional parameters: none 505 Encoding considerations: 506 base-64 507 Security considerations: 508 Delivery of this format to a printer which is not 509 capable of parsing the format may result in poor printer 510 behavior. 511 Published specification: 512 ISO-10180 513 Contact: 515 ====================================================== 517 Media Type name: application 518 Media subtype name: vnd.tek-4014 519 Required parameters: none 520 Optional parameters: none 521 Encoding considerations: 522 base-64 524 draft-lutz-print-types-00.txt January, 97 526 Security considerations: 527 Delivery of this format to a printer which is not 528 capable of parsing the format may result in poor printer 529 behavior. 530 Published specification: 531 Contact: 533 ====================================================== 535 Media Type name: application 536 Media subtype name: vnd.qms-codev 537 Required parameters: none 538 Optional parameters: none 539 Encoding considerations: 540 base-64 541 Security considerations: 542 Delivery of this format to a printer which is not 543 capable of parsing the format may result in poor printer 544 behavior. 545 Published specification: 546 Contact: 548 ====================================================== 550 Media Type name: application 551 Media subtype name: dec-ln03 552 Required parameters: none 553 Optional parameters: none 554 Encoding considerations: 555 base-64 556 Security considerations: 557 Delivery of this format to a printer which is not 558 capable of parsing the format may result in poor printer 559 behavior. 560 Published specification: 561 Contact: 563 ====================================================== 565 Media Type name: application 566 Media subtype name: vnd.qms-quic 567 Required parameters: none 568 Optional parameters: none 569 Encoding considerations: 570 base-64 571 Security considerations: 572 Delivery of this format to a printer which is not 573 capable of parsing the format may result in poor printer 574 behavior. 575 Published specification: 576 Contact: 578 ====================================================== 580 draft-lutz-print-types-00.txt January, 97 582 Media Type name: application 583 Media subtype name: vnd.dec-cpap 584 Required parameters: none 585 Optional parameters: none 586 Encoding considerations: 587 base-64 588 Security considerations: 589 Delivery of this format to a printer which is not 590 capable of parsing the format may result in poor printer 591 behavior. 592 Published specification: 593 Contact: 595 ====================================================== 597 Media Type name: application 598 Media subtype name: vnd.dec-ppl 599 Required parameters: none 600 Optional parameters: none 601 Encoding considerations: 602 base-64 603 Security considerations: 604 Delivery of this format to a printer which is not 605 capable of parsing the format may result in poor printer 606 behavior. 607 Published specification: 608 Contact: 610 ====================================================== 612 Media Type name: application 613 Media subtype name: vnd.qms-doc 614 Required parameters: none 615 Optional parameters: none 616 Encoding considerations: 617 base-64 618 Security considerations: 619 Delivery of this format to a printer which is not 620 capable of parsing the format may result in poor printer 621 behavior. 622 Published specification: 623 Contact: 625 ====================================================== 627 Media Type name: application 628 Media subtype name: vnd.qms-impress 629 Required parameters: none 630 Optional parameters: none 631 Encoding considerations: 632 base-64 634 draft-lutz-print-types-00.txt January, 97 636 Security considerations: 637 Delivery of this format to a printer which is not 638 capable of parsing the format may result in poor printer 639 behavior. 640 Published specification: 641 Contact: 643 ====================================================== 645 Media Type name: application 646 Media subtype name: vnd.nec-pinwriter 647 Required parameters: none 648 Optional parameters: none 649 Encoding considerations: 650 base-64 651 Security considerations: 652 Delivery of this format to a printer which is not 653 capable of parsing the format may result in poor printer 654 behavior. 655 Published specification: 656 Contact: 658 ====================================================== 660 Media Type name: application 661 Media subtype name: vnd.nec-201pl 662 Required parameters: none 663 Optional parameters: none 664 Encoding considerations: 665 base-64 666 Security considerations: 667 Delivery of this format to a printer which is not 668 capable of parsing the format may result in poor printer 669 behavior. 670 Published specification: 671 Contact: 673 ====================================================== 675 Media Type name: application 676 Media subtype name: vnd.ibm-pages 677 Required parameters: none 678 Optional parameters: none 679 Encoding considerations: 680 base-64 681 Security considerations: 682 Delivery of this format to a printer which is not 683 capable of parsing the format may result in poor printer 684 behavior. 685 Published specification: 686 Contact: 688 ====================================================== 690 draft-lutz-print-types-00.txt January, 97 692 Media Type name: application 693 Media subtype name: vnd.cie-lips 694 Required parameters: none 695 Optional parameters: none 696 Encoding considerations: 697 base-64 698 Security considerations: 699 Delivery of this format to a printer which is not 700 capable of parsing the format may result in poor printer 701 behavior. 702 Published specification: 703 Contact: 705 ====================================================== 707 Media Type name: application 708 Media subtype name: vnd.canon-psl 709 Required parameters: none 710 Optional parameters: none 711 Encoding considerations: 712 base-64 713 Security considerations: 714 Delivery of this format to a printer which is not 715 capable of parsing the format may result in poor printer 716 behavior. 717 Published specification: 718 Contact: 720 ====================================================== 722 Media Type name: application 723 Media subtype name: vnd.talaris-excl 724 Required parameters: none 725 Optional parameters: none 726 Encoding considerations: 727 base-64 728 Security considerations: 729 Delivery of this format to a printer which is not 730 capable of parsing the format may result in poor printer 731 behavior. 732 Published specification: 733 Contact: 735 ====================================================== 737 Media Type name: application 738 Media subtype name: vnd.xerox-lcds 739 Required parameters: none 740 Optional parameters: none 741 Encoding considerations: 742 base-64 744 draft-lutz-print-types-00.txt January, 97 746 Security considerations: 747 Delivery of this format to a printer which is not 748 capable of parsing the format may result in poor printer 749 behavior. 750 Published specification: 751 Contact: 753 ====================================================== 755 Media Type name: application 756 Media subtype name: vnd.xerox-xes 757 Required parameters: none 758 Optional parameters: none 759 Encoding considerations: 760 base-64 761 Security considerations: 762 Delivery of this format to a printer which is not 763 capable of parsing the format may result in poor printer 764 behavior. 765 Published specification: 766 Contact: 768