IPP Mail Archive: IPP> Fwd: Definition of 'printer:raw-tcp:' URLs for SLP

IPP Mail Archive: IPP> Fwd: Definition of 'printer:raw-tcp:' URLs for SLP

IPP> Fwd: Definition of 'printer:raw-tcp:' URLs for SLP

Ira McDonald (imcdonal@sdsp.mc.xerox.com)
Wed, 11 Aug 1999 10:58:59 -0400

[New version from Michael Pahmp at Axis - I haven't reviewed
it yet - Ira McDonald]

To: IETF-Announce: ;
Cc: srvloc@srvloc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-svrloc-rawtcp-printer-scheme-01.txt
Date: Wed, 11 Aug 1999 07:10:33 -0400
Sender: owner-srvloc@srvloc.org
Status: R


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Service Location Protocol Working Group of the IETF.

Title : Definition of printer:raw-tcp: URLs for use with
Service Location
Author(s) : M. Pahmp
Filename : draft-ietf-svrloc-rawtcp-printer-scheme-01.txt
Pages : 3
Date : 10-Aug-99

This document defines the 'printer:raw-tcp' service type and the
attributes associated with it. It is a concrete service type of the
abstract printer service type defined in [1] for the Service Location
Procotocol, Version 2 [2].

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-ietf-svrloc-rawtcp-printer-scheme-01.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
"FILE /internet-drafts/draft-ietf-svrloc-rawtcp-printer-scheme-01.txt".

NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type: Message/External-body;

Content-Type: text/plain
Content-ID: <19990810094747.I-D@ietf.org>

FILE /internet-drafts/draft-ietf-svrloc-rawtcp-printer-scheme-01.txt

Content-Type: Message/External-body;

Content-Type: text/plain
Content-ID: <19990810094747.I-D@ietf.org>