I've made a .pdf with line numbers and down-loaded it to:
ftp://ftp.pwg.org/pub/pwg/ipp/new_URL/draft-ietf-ipp-url-scheme-05.pdf
where the .txt version is already:
ftp://ftp.pwg.org/pub/pwg/ipp/new_URL/draft-ietf-ipp-url-scheme-05.txt
Tom
-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Monday, May 20, 2002 13:04
To: 'ipp at pwg.org'; 'carl at manros.com'; 'ned.freed at mrochek.com'
Subject: IPP> New I-D for IPP URL Scheme (20 May 2002)
Copies: Carl-Uno Manros <carl at manros.com>
IPP WG <ipp at pwg.org>
Hi folks, Monday (20 May 2002)
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 file:
draft-ietf-ipp-url-scheme-05.txt (20 May 2002)
All of the changes in this version are clarifications and expansions
requested by our IETF Applications Area Director, Ned Freed, during the
IESG 'last call' on the previous version (draft-04). Carl-Uno Manros
(IETF IPP WG chair) plans to send this final version to the IESG for
publication as a Proposed Standard RFC.
Cheers,
- Ira McDonald (IPP WG member, co-editor of IPP URL scheme)
High North Inc
imcdonald at sharplabs.com
------------------------------------------------------------------------
Appendix X - Change History
[To be deleted before RFC publication]
20 May 2002 - draft-ietf-ipp-url-scheme-05.txt
- expanded IPP in title of document, per RFC Editor;
- revised 'References' section, separating into 'Normative
References' and 'Informative References' sections, per RFC Editor;
- revised 'Abstract' section, to emphasize that this document updates
RFC 2910, per Ned Freed;
- revised several sections, deleting repeated paragraphs and
references to RFC 2373 "IPv6 Addressing Architecture", per Ned
Freed;
- revised 'IPP URL Examples' section, adding examples of IPP URLs
used to uniquely identify IPP Jobs, per Ned Freed;
- revised 'IPP URL Examples' section, deleting both IPv4 and IPv6
literal address examples, per Ned Freed;
- revised 'Conformance Requirements' section, to specify requirements
both for IPP URLs used for the network location of IPP print
services and for IPP URLs used as protocol elements in IPP protocol
requests and responses, per Ned Freed;
- revised 'Security Considerations' section, to discuss security
threats associated with the use of IPP URLs (see section 2.4 of
[RFC2718]), per Ned Freed;
- added 'Appendix A - Registration of "ipp" URL Scheme' with
completed form (see section 6.0 'Registration Template' of
[RFC2717]).
------------------------------------------------------------------------
Copies: "Internet Drafts Editor" <internet-drafts at ietf.org>
"Carl-Uno Manros" <carl at manros.com>
"Tom Hastings" <hastings at cp10.es.xerox.com>
"Bob Herriot" <bob at herriot.com>
"Ira McDonald" <imcdonald at sharplabs.com>
I-D Editor, Monday (20 May 2002)
IETF IPP WG:
Please place this document in the Internet-Drafts repository named:
<draft-ietf-ipp-url-scheme-05.txt> (20 May 2002)
It replaces the previous:
<draft-ietf-ipp-url-scheme-04.txt> (10 January 2002)
Thanks very much,
- Ira McDonald (IPP WG member, co-editor of IPP URL scheme)
High North Inc
imcdonald at sharplabs.com
--------------------
Abstract
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.