In case you missed these announcements from February, the updated IPP URL
scheme document is available on the PWG FTP site and is in the IPP WG agenda
.zip files for next week's IPP WG meeting:
ftp://ftp.pwg.org/pub/pwg/ipp/new_URL/draft-ietf-ipp-url-scheme-02.pdfftp://ftp.pwg.org/pub/pwg/ipp/new_URL/draft-ietf-ipp-url-scheme-02.doc
This document is needed in order to register the 'ipp' scheme for use with
the IPP protocol. We think it is ready for IPP WG Last Call. Do others
agree? Please verify that it is ready for IPP WG Last Call at the IPP WG
meeting.
Send any comments to the mailing list.
Thanks,
Tom
-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Tuesday, February 13, 2001 17:39
To: 'ipp at pwg.org'
Subject: IPP> URL - draft-ietf-ipp-url-scheme-02.txt (13 Feb 2001)
Copies: Carl-Uno Manros <cmanros at cp10.es.xerox.com>
IPP WG <ipp at pwg.org>
SVRLOC WG <srvloc at srvloc.org>
Hi folks, Tuesday (13 February 2001)
I've just sent a new version of 'IPP: IPP URL Scheme' to the
Internet-Drafts editor and posted a copy on the PWG server in the
directory 'ftp://ftp.pwg.org/pub/pwg/ipp/new_URL/' in the files:
draft-ietf-ipp-url-scheme-02.txt (13 February 2001)
draft-ietf-ipp-url-scheme-02.pdf (PDF w/ line numbers of '.txt')
The substance of this document is in five pages, starting at page 5 (see
the change log below). Carl-Uno Manros (IETF IPP WG chair) plans to
discuss this document at the IETF 50 Plenary in Minneapolis in March.
The most important change is the correction of the typographical error
stating "http:" rather than "ipp:" in the one-line ABNF (which was cut
and pasted from HTTP/1.1, RFC 2616, into the previous '-01' version).
Comments?
Cheers,
- Ira McDonald, consulting architect at Xerox and Sharp
High North Inc
imcdonald at sharplabs.comimcdonald at crt.xerox.com
------------------------------------------------------------------------
Appendix X - Change History
[To be deleted before RFC publication]
13 February 2001 - draft-ietf-ipp-url-scheme-02.txt
- revised section 3 'IPP Model for Printers and Jobs' and section 4.5
'IPP URL Scheme Syntax in ABNF' to add notes stating that "IPP URL"
(in this document) is a synonym for "ipp-URL" in [RFC-2910], per
request of Bob Herriot;
- revised section 4.5 'IPP URL Scheme Syntax in ABNF' to correct typo
that showed "http:" rather than "ipp:" in the one-line ABNF, per
request of Tom Hastings;
- revised section 4.5.1 'IPP URL Examples' to add a note discouraging
the use of literal IP addresses in URLs, per [RFC-2616] and
[RFC-1900];
------------------------------------------------------------------------
Copies: "Internet Drafts Editor" <internet-drafts at ietf.org>
"Carl-Uno Manros" <cmanros at cp10.es.xerox.com>
"Bob Herriot" <robert.herriot at pahv.xerox.com>
"Ira McDonald" <imcdonald at sharplabs.com>
"Ira McDonald" <imcdonald at crt.xerox.com>
I-D Editor, Tuesday (13 February 2001)
IETF IPP WG:
Please place this document in the Internet-Drafts repository named:
<draft-ietf-ipp-url-scheme-02.txt> (13 February 2001)
It replaces the previous:
<draft-ietf-ipp-url-scheme-01.txt> (5 February 2001)
Thanks very much,
- Ira McDonald (IPP WG member, co-editor of IPP URL scheme)
High North Inc
imcdonald at sharplabs.comimcdonald at crt.xerox.com
--------------------
Abstract
This document is a product of the Internet Printing Protocol Working
Group of the Internet Engineering Task Force (IETF). Comments should
be submitted to the ipp at pwg.org mailing list.
This document is intended for use in registering the "ipp" URL scheme
with IANA and fully conforms to the requirements in [RFC-2717]. This
document defines the "ipp" URL (Uniform Resource Locator) scheme for
specifying the location of an IPP Printer, IPP Job, or other IPP
object (defined in some future version of IPP) which implements the
IPP/1.1 Model [RFC-2911] and the IPP/1.1 Protocol encoding over HTTP
[RFC-2910] or any later version of IPP. The intended usage of the
"ipp" URL scheme is COMMON.
The IPP URL scheme defined in this document is based on the ABNF for
the HTTP URL scheme defined in HTTP/1.1 [RFC-2616], which is derived
from the URI Generic Syntax [RFC-2396] and further updated by
[RFC-2732] and [RFC-2373] (for IPv6 addresses in URLs). An IPP URL
is transformed into an HTTP URL according to the rules specified in
section 5 of the IPP/1.1 Protocol [RFC-2910].
------------------------------------------------------------------------
-----Original Message-----
From: Internet-Drafts at ietf.org [mailto:Internet-Drafts at ietf.org]
Sent: Thursday, February 15, 2001 03:48
Cc: ipp at pwg.org
Subject: IPP> I-D ACTION:draft-ietf-ipp-url-scheme-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Internet Printing Protocol Working Group of
the IETF.
Title : Internet Printing Protocol (IPP): IPP URL Scheme
Author(s) : R. Herriot, I. McDonald
Filename : draft-ietf-ipp-url-scheme-02.txt
Pages : 16
Date : 14-Feb-01
This document is a product of the Internet Printing Protocol Working
Group of the Internet Engineering Task Force (IETF). Comments should
be submitted to the ipp at pwg.org mailing list.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipp-url-scheme-02.txt
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-ipp-url-scheme-02.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv at ietf.org.
In the body type:
"FILE /internet-drafts/draft-ietf-ipp-url-scheme-02.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
Internet-Draft.