idnits 2.17.1 draft-ietf-svrloc-rawtcp-printer-scheme-00.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: ---------------------------------------------------------------------------- ** 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 abstract seems to contain references ([2], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (2 December 1998) is 9277 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 section? '1' on line 139 looks like a reference -- Missing reference section? '2' on line 41 looks like a reference -- Missing reference section? '3' on line 151 looks like a reference -- Missing reference section? '4' on line 94 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Service Location Working Group Mikael Pahmp 2 INTERNET DRAFT Axis Communications 4 2 December 1998 6 Definition of printer:raw-tcp: URLs for use with Service Location 7 draft-ietf-svrloc-rawtcp-printer-scheme-00.txt 9 Status of This Memo 11 This document is a submission by the Service Location Working Group 12 of the Internet Engineering Task Force (IETF). Comments should be 13 submitted to the srvloc@srvloc.org mailing list. 15 Distribution of this memo is unlimited. 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 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 24 any time. It is inappropriate to use Internet- Drafts as reference 25 material or to cite them other than as ``work in progress.'' 27 To view the entire list of current Internet-Drafts, please check 28 the ``1id-abstracts.txt'' listing contained in the Internet-Drafts 29 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 30 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 31 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 33 Distribution of this memo is unlimited. 35 Abstract 37 This document defines the raw-tcp service type which is a concrete 38 service type of the abstract printer service type defined in [1]. 40 This template is designed to be used in conjuction with the Service 41 Location Protocol, version 2 defined in [2]. 43 Contents 45 Status of This Memo i 47 Abstract i 49 1. Introduction 1 51 2. Raw TCP printing 1 52 2.1. Service Attributes. . . . . . . . . . . . . . . . . . . . 1 54 3. Printer Service Template 2 56 A. References 3 58 1. Introduction 60 Service Type templates are used to describe in a standard way those 61 services which use the service: URL. The template described in this 62 document extends the abstract service type described in [1], called 63 printer, with another concrete printer type, called raw-tcp. 65 2. Raw TCP printing 67 Printing using TCP for transparent communication between a client 68 and a print service is common today. How print data, status, 69 messages, etc is formatted when exchanged across the TCP connection 70 varies. It is up to the printing client to determine how data should 71 be formatted and interpreted. This may be determined based on the 72 information available in the service attributes. 74 2.1. Service Attributes 76 Attributes of the Raw TCP printing service includes those 77 defined in [1]. The following additional semantics applies. 79 The 'concrete-protocols' attribute value should always be 'tcp'. 81 The 'abstract-protocols' attribute is optional in [1] and should 82 not be advertised with the Raw TCP printing service since data 83 exchanged across the TCP connection isn't defined by the service. 85 A new optional attribute 'device-id' is defined for the Raw TCP 86 printing service. This attribute is the Device ID string defined in 87 IEEE 1284 [3] which may be used to uniqely identify a printer and 88 match it with a software driver on the printing client. 90 3. Printer Service Template 92 The service template defined below, conforms to the grammar 93 described in "Service Templates and service: Schemes". Please refer 94 to [4] for detailed explaination of the syntax. 96 Name of submitter: Mikael Pahmp 97 Language of service template: en 98 Security Considerations: 99 This service neither adds nor detracts from the security of the 100 opaque data stream itself. The service could be used to obfuscate 101 or lie about the service endpoint's characteristics if SLP 102 authentication blocks are not used. 103 Template Text: 104 -------------------------template begins here----------------------- 105 template-type=service:printer:raw-tcp: 107 template-version=0.0 109 template-description= 110 The printer:raw-tcp: URL describes a transparent bidirectional 111 communication channel for printing. Print data, status, messages, 112 etc is written or read by opening a TCP connection to the port in 113 the service URL. How data is formatted and sent across the 114 connection is decided by the printing client and the print service 115 and is not defined in this document. 117 template-url-syntax= 118 url-path = ; 120 concrete-protocols = STRING L M 121 # The names of the concrete protocol types supported 122 # by the printer abstract service type. Example values 123 # include http and lpr. 124 # Is always 'tcp' for this concrete service. 126 abstract-protocol = STRING L O 127 # The name of the abstract protocol which may be run over 128 # any concrete types listed. For example, the abstract 129 # protocol 'ipp' may be run over the concrete types of http 130 # or 'mailto'. 131 # Should not be advertised with this concrete service. 133 device-id= STRING L O 134 # The Device ID string defined in IEEE 1284 which uniqely identifies 135 # a printer type and model. 137 --------------------------template ends here------------------------ 138 Note: The 'concrete-protocols' and 'abstract-protocol' attributes is 139 defined in [1] but is given a more narrow definition here when used 140 with the Raw TCP printing service. The 'device-id' attribute is a new 141 attribute defined for this concrete service type. 143 A. References 145 [1]P. St. Pierre, S. Isaccson. "Definition of printer: URLs for 146 use with Service Location", Work in Progress, March 1998. 148 [2]E. Guttman, C. Perkins, J. Veizades and M. Day. "Service 149 Location Protocol, Version 2", Work in Progress, November 1998. 151 [3] "IEEE Std.1284-1994 Standard Signaling Method for a 152 Bi-directional Parallel Peripheral Interface for Personal 153 Computers", 1994. 155 [4]E. Guttman, C. Perkins, J. Kempf, "Service Templates and service: 156 Schemes", Work in Progress, November, 1998 158 Full Copyright Statement 160 Copyright (C) The Internet Society (1997). All Rights Reserved. 162 This document and translations of it may be copied and furnished to 163 others, and derivative works that comment on or otherwise explain it 164 or assist in its implementation may be prepared, copied, published 165 and distributed, in whole or in part, without restriction of any 166 kind, provided that the above copyright notice and this paragraph 167 are included on all such copies and derivative works. However, 168 this document itself may not be modified in any way, such as by 169 removing the copyright notice or references to the Internet Society 170 or other Internet organizations, except as needed for the purpose 171 of developing Internet standards in which case the procedures 172 for copyrights defined in the Internet Standards process must be 173 followed, or as required to translate it into languages other than 174 English. 176 The limited permissions granted above are perpetual and will not be 177 revoked by the Internet Society or its successors or assigns. 179 This document and the information contained herein is provided on an 180 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 181 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 182 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 183 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 184 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 186 Authors' Address 188 Questions about this memo can be directed to: 190 Mikael Pahmp 191 Axis Communications 192 Scheelev. 16 193 S - 223 70 Lund 194 Sweden 195 Phone: +46 46 270 18 00 196 email: Mikael.Pahmp@axis.com