idnits 2.17.1 draft-ietf-svrloc-rawtcp-printer-scheme-01.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. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** 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 (28 June 1999) is 9068 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '3' Summary: 6 errors (**), 0 flaws (~~), 2 warnings (==), 5 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 3 28 June 1999 5 Definition of printer:raw-tcp: URLs for use with Service Location 6 draft-ietf-svrloc-rawtcp-printer-scheme-01.txt 8 Status of This Memo 10 This document is a submission by the Service Location Working Group 11 of the Internet Engineering Task Force (IETF). Comments should be 12 submitted to the srvloc@srvloc.org mailing list. 14 Distribution of this memo is unlimited. 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 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 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 at: 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This document defines the 'printer:raw-tcp' service type and the 36 attributes associated with it. It is a concrete service type of the 37 abstract printer service type defined in [1] for the Service Location 38 Procotocol, Version 2 [2]. 40 1. Introduction 42 Service Type templates are used to describe in a standard way those 43 services which use the service: URL. The template described in this 44 document extends the abstract service type described in [1], called 45 printer, with another concrete service type, called raw-tcp. 47 2. Raw TCP printing 49 Printing using TCP for transparent communication between a client 50 and a print service is common today. How print data, status, 51 messages, etc is formatted when exchanged across the TCP connection 52 varies. It is up to the printing client to determine how data should 53 be formatted and interpreted. This may be determined based on the 54 information available in the service attributes. 56 For example, a client without any prior configuration may 57 use the 'ieee-1284-device-id' attribute, described below, to select a 58 printer driver for the advertised printer. The client can then let 59 the printer driver communicate transparently with the printer service 60 by opening a TCP connection to the host and port indicated by the 61 advertised URL. 63 2.1. Service Attributes 65 Attributes of the raw-tcp print service includes those defined 66 in [1] and a new optional attribute 'ieee-1284-device-id' defined 67 in this service template. This attribute is the Device ID string 68 of the advertised printer as defined in IEEE 1284 [3]. 70 3. 'printer:raw-tcp' Service Template 72 The service template defined below, conforms to the grammar 73 described in "Service Templates and service: Schemes". Please refer 74 to [4] for detailed explaination of the syntax. 76 Name of submitter: Mikael Pahmp 78 Language of service template: en 80 Security Considerations: 81 This service neither adds nor detracts from the security of the 82 opaque raw-tcp data stream itself. See also the security 83 considerations of the 'printer:' template [1]. 85 Template Text: 86 -------------------------template begins here----------------------- 87 template-type = printer:raw-tcp 89 template-version = 0.1 91 template-description = 92 The printer:raw-tcp: URL describes a transparent bidirectional 93 communication channel for printing. Print data, status, messages, 94 etc is written or read by opening a TCP connection to the port in 95 the service URL. How data is formatted and sent across the 96 connection is decided by the printing client and the printer 97 service and is not defined by this template. 99 template-url-syntax= 100 url-path = ippurl / lprurl / raw-tcp-url 101 ; This template adds 'raw-tcp-url' to the url-path 102 ; definition in [1]. 103 ; 'ippurl' and 'lprurl' as defined in [1]. 104 raw-tcp-url = "raw-tcp://" hostport 105 ; raw-tcp URLs don't have a path section. 106 hostport = host ":" port 107 ; raw-tcp doesn't have a well-known port assigned by 108 ; IANA. The port must therefor be specified in all 109 ; raw-tcp URLs. 110 ; 'host' and 'port' as defined in [1]. 112 ieee-1284-device-id = STRING L O 113 # The Device ID string of this printer as defined in IEEE 1284 [3] 114 # which identifies the printer type, model, etc. 116 --------------------------template ends here------------------------ 118 4. References 120 [1] St. Pierre, P., Isaccson., S. and I. McDonald, 121 "Definition of printer: URLs for use with Service Location", 122 (work in progress), 123 February 1999. 125 [2] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service 126 Location Protocol Version 2", RFC 2608, June 1999. 128 [3] "IEEE Std.1284-1994 Standard Signaling Method for a 129 Bi-directional Parallel Peripheral Interface for Personal 130 Computers", 1994. 132 [4] Guttman, E., Perkins, C. and J. Kempf, "Service Templates and 133 service: Schemes", RFC 2609, June 1999. 135 5. Full Copyright Statement 137 Copyright (C) The Internet Society (1999). All Rights Reserved. 139 This document and translations of it may be copied and furnished to 140 others, and derivative works that comment on or otherwise explain it 141 or assist in its implementation may be prepared, copied, published 142 and distributed, in whole or in part, without restriction of any 143 kind, provided that the above copyright notice and this paragraph are 144 included on all such copies and derivative works. However, this 145 document itself may not be modified in any way, such as by removing 146 the copyright notice or references to the Internet Society or other 147 Internet organizations, except as needed for the purpose of 148 developing Internet standards in which case the procedures for 149 copyrights defined in the Internet Standards process must be 150 followed, or as required to translate it into languages other than 151 English. 153 The limited permissions granted above are perpetual and will not be 154 revoked by the Internet Society or its successors or assigns. 156 This document and the information contained herein is provided on an 157 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 158 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 159 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 160 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 161 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 163 6. Author's Address 165 Questions about this memo can be directed to: 167 Mikael Pahmp 168 Axis Communications 169 Scheelev. 16 170 S - 223 70 Lund 171 Sweden 172 Phone: +46 46 270 1881 173 email: Mikael.Pahmp@axis.com