Also the Notification Requirements I-D has expired its 6 months (and is no
longer available at):
http://www.ietf.org/internet-drafts/draft-ietf-ipp-not-03.txt
So I added it to the meeting directory
ftp://ftp.pwg.org/pub/pwg/ipp/meeting-txt-000404/
and the .zip that is there.
Its full URL is:
ftp://ftp.pwg.org/pub/pwg/ipp/meeting-txt-000404/draft-ietf-ipp-not-03.txt
and the URL of the updated .zip is:
ftp://ftp.pwg.org/pub/pwg/ipp/meeting-txt-000404/meeting-txt-000404.zip
Tom
-----Original Message-----
From: Hastings, Tom N
Sent: Monday, March 27, 2000 14:31
To: ipp
Subject: RE: IPP> ADM - Internet-Drafts for March IETF and IPP WG
meeting put into new directory
BTW,
I didn't include the draft-ietf-ipp-not-http-delivery-00.txt (October 1999)
since it has been superseded by draft-ietf-ipp-indp-method-00.txt
I also chopped off the FTP date stuff from the directory listing to make it
more readable in the attached mail message.
Tom
-----Original Message-----
From: Hastings, Tom N [mailto:hastings at cp10.es.xerox.com]
Sent: Monday, March 27, 2000 12:04
To: ipp
Subject: IPP> ADM - Internet-Drafts for March IETF and IPP WG meeting
put into new directory
I've copied the relevant IPP I-Ds to the directory as indicated in Ira's
mail.
I've also put all of the files into a .zip so you can copy all of them at
once compressed.
Note: The snmp-02 document is written as an I-D, but has not been send to
the IETF, since it was produced after the cutoff. So the directory has both
the -01 (October 99) and -02 versions.
ftp://ftp.pwg.org/pub/pwg/ipp/meeting-txt-000404/
draft-ietf-ipp-collection-02.txt
draft-ietf-ipp-finishings-fold-trim-bale-00.txt
draft-ietf-ipp-implementers-guide-v11-00.txt
draft-ietf-ipp-indp-00.txt
draft-ietf-ipp-indp-method-00.txt
draft-ietf-ipp-job-printer-set-ops-01.txt
draft-ietf-ipp-ldap-printer-schema-00.txt
draft-ietf-ipp-model-v11-06.txt
draft-ietf-ipp-notify-mailto-00.txt
draft-ietf-ipp-notify-poll-00.txt
draft-ietf-ipp-not-over-snmp-01.txt
draft-ietf-ipp-not-over-snmp-02.txt
draft-ietf-ipp-not-spec-02.txt
draft-ietf-ipp-ops-set2-00.txt
draft-ietf-ipp-output-bin-attr-00.txt
draft-ietf-ipp-protocol-v11-05.txt
draft-ietf-svrloc-printer-scheme-06.txt
list-of-txt-file-for-000404-meeting.txt
meeting-txt-000404.zip
I'm working on doing the same for the .pdf files for the PWG meeting. I'll
also make a single .zip file as well in that directory. The .pdf directory
will have the .pdf for all of these Internet-Drafts, plus some PWG specs,
and any later specs that come out this week.
Tom
-----Original Message-----
From: McDonald, Ira [mailto:imcdonald at sharplabs.com]
Sent: Wednesday, March 22, 2000 12:51
To: 'Hugo Parra'; Robert.Herriot at pahv.xerox.com; ipp at pwg.org
Subject: RE: IPP>NOT IETF talk on notification
Hi Hugo,
We spent our entire IPP Telecon (2 1/2 hours) discussing these
slides. Carl-Uno, Tom Hastings, Bob Herriot and I cleaned them
up and we agee that 'acts like an IPP Printer' was inaccurate
and confusing.
Bob will get new copies out for review ASAP. He will also try
to export HTML versions for better accessibility to IETF 47
participants (in addition to the PowerPoint base slides for
those with MS Windows tools).
Also, Tom Hastings will build two new directories under
'ftp://ftp.pwg.org/pub/pwg/ipp' for the convenience of PWG
Tokyo attendees:
meeting-txt-mmddyy - IETF I-D text formatted documents
meeting-pdf-mmddyy - PDF of original MS Word documents
These directories will contain ONLY the latest versions of each
current IETF or PWG working document - so meeting attendees can
browse them easily with low-bandwidth (dial-up) connections and
download the documents they want to view or print locally.
-----Original Message-----
From: Hugo Parra [mailto:HPARRA at novell.com]
Sent: Wednesday, March 22, 2000 9:43 AM
To: Robert.Herriot at pahv.xerox.com; ipp at pwg.org
Subject: Re: IPP>NOT IETF talk on notification
Bob,
It looks like you're going to engage the IESG in a good discussion.
Excellent. I have a comment on the "indp:" slide. I think saying that the
notify recipient "acts like a Printer" is inaccurate and can create a lot of
confusion. I don't think that everything that implements an HTTP server
stack and accepts requests formatted with the "application/ipp" encoding
needs to be described as acting like a printer. I would rather say it
behaves as an http server.
-Hugo
>>> "Herriot, Robert" <Robert.Herriot at pahv.xerox.com> 03/21/00 08:00PM >>>
I have downloaded a powerpoint presentation on notification for the IETF
meeting next week.
We plan to look at it for tomorrow's teleconference.
It is at:
ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/talkNotify000321.ppt