draft-ietf-svrloc-rawtcp-printer-scheme-00.txt		draft-ietf-svrloc-rawtcp-printer-scheme-01.txt
	Service Location Working Group Mikael Pahmp		Service Location Working Group Mikael Pahmp
	INTERNET DRAFT Axis Communications		INTERNET DRAFT Axis Communications
	2 December 1998
	Definition of printer:raw-tcp: URLs for use with Service Location		Definition of printer:raw-tcp: URLs for use with Service Location
	draft-ietf-svrloc-rawtcp-printer-scheme-00.txt		draft-ietf-svrloc-rawtcp-printer-scheme-01.txt
	Status of This Memo		Status of This Memo
	This document is a submission by the Service Location Working Group		This document is a submission by the Service Location Working Group
	of the Internet Engineering Task Force (IETF). Comments should be		of the Internet Engineering Task Force (IETF). Comments should be
	submitted to the srvloc@srvloc.org mailing list.		submitted to the srvloc@srvloc.org mailing list.
	Distribution of this memo is unlimited.		Distribution of this memo is unlimited.
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft and is in full conformance with
			all provisions of Section 10 of RFC2026. Internet-Drafts are working
	documents of the Internet Engineering Task Force (IETF), its areas,		documents of the Internet Engineering Task Force (IETF), its areas,
	and its working groups. Note that other groups may also distribute		and its working groups. Note that other groups may also distribute
	working documents as Internet-Drafts.		working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at		and may be updated, replaced, or obsoleted by other documents at
	any time. It is inappropriate to use Internet- Drafts as reference		any time. It is inappropriate to use Internet- Drafts as reference
	material or to cite them other than as ``work in progress.''		material or to cite them other than as "work in progress."
	To view the entire list of current Internet-Drafts, please check		The list of current Internet-Drafts can be accessed at:
	the ``1id-abstracts.txt'' listing contained in the Internet-Drafts		http://www.ietf.org/ietf/1id-abstracts.txt
	Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
	Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
	Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
	Distribution of this memo is unlimited.		The list of Internet-Draft Shadow Directories can be accessed at:
			http://www.ietf.org/shadow.html.
	Abstract		Abstract
	This document defines the raw-tcp service type which is a concrete		This document defines the 'printer:raw-tcp' service type and the
	service type of the abstract printer service type defined in [1].		attributes associated with it. It is a concrete service type of the
			abstract printer service type defined in [1] for the Service Location
	This template is designed to be used in conjuction with the Service		Procotocol, Version 2 [2].
	Location Protocol, version 2 defined in [2].
	Contents
	Status of This Memo i
	Abstract i
	1. Introduction 1
	2. Raw TCP printing 1
	2.1. Service Attributes. . . . . . . . . . . . . . . . . . . . 1
	3. Printer Service Template 2
	A. References 3
	1. Introduction		1. Introduction
	Service Type templates are used to describe in a standard way those		Service Type templates are used to describe in a standard way those
	services which use the service: URL. The template described in this		services which use the service: URL. The template described in this
	document extends the abstract service type described in [1], called		document extends the abstract service type described in [1], called
	printer, with another concrete printer type, called raw-tcp.		printer, with another concrete service type, called raw-tcp.
	2. Raw TCP printing		2. Raw TCP printing
	Printing using TCP for transparent communication between a client		Printing using TCP for transparent communication between a client
	and a print service is common today. How print data, status,		and a print service is common today. How print data, status,
	messages, etc is formatted when exchanged across the TCP connection		messages, etc is formatted when exchanged across the TCP connection
	varies. It is up to the printing client to determine how data should		varies. It is up to the printing client to determine how data should
	be formatted and interpreted. This may be determined based on the		be formatted and interpreted. This may be determined based on the
	information available in the service attributes.		information available in the service attributes.
	2.1. Service Attributes		For example, a client without any prior configuration may
			use the 'ieee-1284-device-id' attribute, described below, to select a
	Attributes of the Raw TCP printing service includes those		printer driver for the advertised printer. The client can then let
	defined in [1]. The following additional semantics applies.		the printer driver communicate transparently with the printer service
			by opening a TCP connection to the host and port indicated by the
	The 'concrete-protocols' attribute value should always be 'tcp'.		advertised URL.
	The 'abstract-protocols' attribute is optional in [1] and should		2.1. Service Attributes
	not be advertised with the Raw TCP printing service since data
	exchanged across the TCP connection isn't defined by the service.
	A new optional attribute 'device-id' is defined for the Raw TCP		Attributes of the raw-tcp print service includes those defined
	printing service. This attribute is the Device ID string defined in		in [1] and a new optional attribute 'ieee-1284-device-id' defined
	IEEE 1284 [3] which may be used to uniqely identify a printer and		in this service template. This attribute is the Device ID string
	match it with a software driver on the printing client.		of the advertised printer as defined in IEEE 1284 [3].
	3. Printer Service Template		3. 'printer:raw-tcp' Service Template
	The service template defined below, conforms to the grammar		The service template defined below, conforms to the grammar
	described in "Service Templates and service: Schemes". Please refer		described in "Service Templates and service: Schemes". Please refer
	to [4] for detailed explaination of the syntax.		to [4] for detailed explaination of the syntax.
	Name of submitter: Mikael Pahmp		Name of submitter: Mikael Pahmp <Mikael.Pahmp@axis.com>
	Language of service template: en		Language of service template: en
	Security Considerations:		Security Considerations:
	This service neither adds nor detracts from the security of the		This service neither adds nor detracts from the security of the
	opaque data stream itself. The service could be used to obfuscate		opaque raw-tcp data stream itself. See also the security
	or lie about the service endpoint's characteristics if SLP		considerations of the 'printer:' template [1].
	authentication blocks are not used.
	Template Text:		Template Text:
	-------------------------template begins here-----------------------		-------------------------template begins here-----------------------
	template-type=service:printer:raw-tcp:		template-type = printer:raw-tcp
	template-version=0.0		template-version = 0.1
	template-description=		template-description=
	The printer:raw-tcp: URL describes a transparent bidirectional		The printer:raw-tcp: URL describes a transparent bidirectional
	communication channel for printing. Print data, status, messages,		communication channel for printing. Print data, status, messages,
	etc is written or read by opening a TCP connection to the port in		etc is written or read by opening a TCP connection to the port in
	the service URL. How data is formatted and sent across the		the service URL. How data is formatted and sent across the
	connection is decided by the printing client and the print service		connection is decided by the printing client and the printer
	and is not defined in this document.		service and is not defined by this template.
	template-url-syntax=		template-url-syntax=
	url-path = ;		url-path = ippurl / lprurl / raw-tcp-url
			; This template adds 'raw-tcp-url' to the url-path
	concrete-protocols = STRING L M		; definition in [1].
	# The names of the concrete protocol types supported		; 'ippurl' and 'lprurl' as defined in [1].
	# by the printer abstract service type. Example values		raw-tcp-url = "raw-tcp://" hostport
	# include http and lpr.		; raw-tcp URLs don't have a path section.
	# Is always 'tcp' for this concrete service.		hostport = host ":" port
			; raw-tcp doesn't have a well-known port assigned by
	abstract-protocol = STRING L O		; IANA. The port must therefor be specified in all
	# The name of the abstract protocol which may be run over		; raw-tcp URLs.
	# any concrete types listed. For example, the abstract		; 'host' and 'port' as defined in [1].
	# protocol 'ipp' may be run over the concrete types of http
	# or 'mailto'.
	# Should not be advertised with this concrete service.
	device-id= STRING L O		ieee-1284-device-id = STRING L O
	# The Device ID string defined in IEEE 1284 which uniqely identifies		# The Device ID string of this printer as defined in IEEE 1284 [3]
	# a printer type and model.		# which identifies the printer type, model, etc.
	--------------------------template ends here------------------------		--------------------------template ends here------------------------
	Note: The 'concrete-protocols' and 'abstract-protocol' attributes is
	defined in [1] but is given a more narrow definition here when used
	with the Raw TCP printing service. The 'device-id' attribute is a new
	attribute defined for this concrete service type.
	A. References		4. References
	[1]P. St. Pierre, S. Isaccson. "Definition of printer: URLs for		[1] St. Pierre, P., Isaccson., S. and I. McDonald,
	use with Service Location", Work in Progress, March 1998.		"Definition of printer: URLs for use with Service Location",
			<draft-ietf-svrloc-printer-scheme-03.txt> (work in progress),
			February 1999.
	[2]E. Guttman, C. Perkins, J. Veizades and M. Day. "Service		[2] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service
	Location Protocol, Version 2", Work in Progress, November 1998.		Location Protocol Version 2", RFC 2608, June 1999.
	[3] "IEEE Std.1284-1994 Standard Signaling Method for a		[3] "IEEE Std.1284-1994 Standard Signaling Method for a
	Bi-directional Parallel Peripheral Interface for Personal		Bi-directional Parallel Peripheral Interface for Personal
	Computers", 1994.		Computers", 1994.
	[4]E. Guttman, C. Perkins, J. Kempf, "Service Templates and service:		[4] Guttman, E., Perkins, C. and J. Kempf, "Service Templates and
	Schemes", Work in Progress, November, 1998		service: Schemes", RFC 2609, June 1999.
	Full Copyright Statement		5. Full Copyright Statement
	Copyright (C) The Internet Society (1997). All Rights Reserved.		Copyright (C) The Internet Society (1999). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph		kind, provided that the above copyright notice and this paragraph are
	are included on all such copies and derivative works. However,		included on all such copies and derivative works. However, this
	this document itself may not be modified in any way, such as by		document itself may not be modified in any way, such as by removing
	removing the copyright notice or references to the Internet Society		the copyright notice or references to the Internet Society or other
	or other Internet organizations, except as needed for the purpose		Internet organizations, except as needed for the purpose of
	of developing Internet standards in which case the procedures		developing Internet standards in which case the procedures for
	for copyrights defined in the Internet Standards process must be		copyrights defined in the Internet Standards process must be
	followed, or as required to translate it into languages other than		followed, or as required to translate it into languages other than
	English.		English.
	The limited permissions granted above are perpetual and will not be		The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assigns.		revoked by the Internet Society or its successors or assigns.
	This document and the information contained herein is provided on an		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
	Authors' Address		6. Author's Address
	Questions about this memo can be directed to:		Questions about this memo can be directed to:
	Mikael Pahmp		Mikael Pahmp
	Axis Communications		Axis Communications
	Scheelev. 16		Scheelev. 16
	S - 223 70 Lund		S - 223 70 Lund
	Sweden		Sweden
	Phone: +46 46 270 18 00		Phone: +46 46 270 1881
	email: Mikael.Pahmp@axis.com		email: Mikael.Pahmp@axis.com
End of changes. 31 change blocks.
	95 lines changed or deleted		69 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/