Forwarded,
Carl-Uno
Carl-Uno Manros
Keller Williams Realty - The Marketplace
2230 Corporate Circle, Suite 250
Henderson, NV 89074
Tel Office (702) 939-0000
Tel Mobile (702) 525-0727
Email carl@manros.com
Website www.manros.com
-----Original Message-----
To: IETF-Announce: ;
Subject: RFC 3510 on Internet Printing Protocol/1.1: IPP URL Scheme
Cc: rfc-editor@rfc-editor.org, ipp@pwg.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 02 Apr 2003 14:40:33 -0800
Sender: rfc-ed@ISI.EDU
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 3510
Title: Internet Printing Protocol/1.1:
IPP URL Scheme
Author(s): R. Herriot, I. McDonald
Status: Standards Track
Date: April 2003
Mailbox: bob@herriot.com, imcdonald@sharplabs.com
Pages: 16
Characters: 22009
Updates: 2910
I-D Tag: draft-ietf-ipp-url-scheme-05.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3510.txt
This memo defines the "ipp" URL (Uniform Resource Locator) scheme.
This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by
expanding and clarifying Section 5, "IPP URL Scheme", of RFC 2910. An
"ipp" URL is used to specify the network location of a print service
that supports the IPP Protocol (RFC 2910), or of a network resource
(for example, a print job) managed by such a print service.
This document is a product of the Internet Printing Protocol Working
Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <030402143902.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc3510
--OtherAccess
Content-Type: Message/External-body;
name="rfc3510.txt";
site="ftp.isi.edu";
access-type="anon-ftp";
directory="in-notes"
Content-Type: text/plain
Content-ID: <030402143902.RFC@RFC-EDITOR.ORG>
--OtherAccess--
--NextPart--
This archive was generated by hypermail 2b29 : Wed Apr 02 2003 - 22:48:16 EST