attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content='"MSHTML 4.72.3110.7"' name=GENERATOR> </HEAD> <BODY bgColor=#ffffff style="FONT: 10pt Arial; MARGIN-LEFT: 2px; MARGIN-TOP: 2px"> <DIV>Thank you Ira.  We'll consider your suggestion in the meeting.</DIV> <DIV>-Hugo >>> "McDonald, Ira" <<A href="mailto:imcdonald@sharplabs.com">imcdonald@sharplabs.com</A>> 02/09/00 11:13AM >>> Hi Hugo, I prefer the scheme name 'ipp-notify-http' - because it states the functionality (ipp-notify) and the transport (http). Yes, the IESG has considerable influence over scheme names. They are supposed to be IDENTICAL to the standard acronym for the protocol associated with the scheme - for example, 'http:' and 'ipp:'. In the case of IPP notifications asynchronously over HTTP by server push, the protocol is arguably a new protocol (and not merely a mapping like 'mailto:' for email notifications), so I think the IESG will want a unique scheme name. But they're also fond of short, sweet scheme names, so 'ippnh:' (IPP Notify over HTTP) or some such is probably likely to be better received. The relevant IETF standards are: RFC 2717 - Registration Procedures for URL Scheme Names (November 1999) RFC 2718 - Guidelines for new URL Schemes (November 1999) Cheers, - Ira McDonald, consulting architect at Sharp Labs America High North Inc -----Original Message----- From: Hugo Parra [mailto:HPARRA@novell.com] Sent: Tuesday, February 08, 2000 5:40 PM To: ipp@pwg.org Subject: Re: IPP> ADM - Agenda Points for the IEEE-ISTO IPP WG Meeting in New Orleans February 9-10, 2000 In order to expedite our discussion of the ipp-ntfy-send protocol and to hopefully resolve the remaining issues, I'd like to follow the attached discussion outline when I'm up. If you've taken a few minutes to review the outline, the discussion should be a bit smoother. Cheers, -Hugo >>> "Manros, Carl-Uno B" <cmanros@cp10.es.xerox.com> 02/02/00 02:24PM >>> Please see the proposed agenda topics and document references for our upcoming meeting in New Orleans. We will discuss the exact order and the time allocation for these points at the beginning of the meeting. Agenda Points for the IEEE-ISTO IPP WG Meeting in New Orleans February 9-10, 2000 ====================================== === - Introduction informing about the proposed charter for the IETF IPPEXT WG, and the latest organizational changes in IETF. Discussion about how to organize the IETF vs. PWG parts of the IPP work. (Carl-Uno Manros) - Main Topics: - Discussion of new IPP operations: "IPP/1.1: Job and Printer Set Operations" (Tom Hastings, Bob Herriot) ftp://ftp.pwg.org/pub/pwg/ipp/new_OPS/ipp-job-printer-set-ops-000130.pdf The plan is to send this document out for IETF WG Last Call, after any final edits, following the New Orleans meeting. - Discuss how to proceed with our earlier drafts on remaining new operations: Set 2 and Set 3 Operations: "IPP/1.1: Set2 Operations" ftp://ftp.pwg.org/pub/pwg/ipp/new_OPS/ipp-ops-set2-991208.pdf (or newer version) "IPP/1.1: Set3 Operations" ftp://ftp.pwg.org/pub/pwg/ipp/new_OPS/ipp-ops-set3-991208.pdf - IPP Notifications, see the latest drafts on the documented delivery methods and the Collection syntax (Tom Hastings) "Internet Printing Protocol/1.1: Requirements for IPP Notifications" ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notification-requirements-990811.p df http://www.ietf.org/internet-drafts/draft-ietf-ipp-not-03.txt "IPP/1.1: IPP Event Notification Specification" ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-spec-991014.pdf (or newer version) "IPP/1.1: Notifications over SNMP" (Ira Mcdonald) ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/draft-ietf-ipp-not-over-snmp-01.pdf "IPP/1.1: The 'ipp-get' Notification Delivery Method" (Carl-Uno Manros, Harry Lewis) ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-get-delivery-991207.pdf "IPP/1.1: The 'ipp-ntfy' Notification Delivery Method and Protocol (Hugo Parra) ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-not-ntfy-delivery-991209.pdf "IPP/1.1: Notifications over SMTP" (look for new draft from Henrik Holst) "IPP/1.1: Job Progress Attributes" (Harry Lewis, Tom Hastings) ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-job-prog-attr-990913.pdf "IPP/1.1: attribute syntax for Collection" (Bob Herriot) ftp://ftp.pwg.org/pub/pwg/ipp/new_COL/ipp-collection-attr-syntax-991208.pdf http://www.ietf.org/internet-drafts/draft-ietf-ipp-collection-00.txt - Additional Topics: - Look at questions and answers from the IPP DL and determine which ones should be documented in the IPP Implementer's Guide (Carl-Uno) Possible Input for IPP/1.1: IIG - PWG - Production Printing: Internet Printing Protocol: Exception Attributes for Documents and Pages ftp://ftp.pwg.org/pub/pwg/ipp/new_EXC/pwg-ipp-exceptions-model-000131.pdf Internet Printing Protocol: Production Printing Attributes - Set1 ftp://ftp.pwg.org/pub/pwg/ipp/new_PPE/pwg-ipp-prod-print-set1-000131.pdf ---------------- Carl-Uno Manros Principal Engineer - Xerox Architecture Center - Xerox Corporation 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 Phone +1-310-333 8273, Fax +1-310-333 5514 Email: manros@cp10.es.xerox.com </DIV></BODY></HTML>