Hi Michael,
Wait - the IETF _will not_ allow 'ippget:' (with nothing following or
with nonsense that isn't a protocol target address following) as a
URL scheme. It violates all the rules of URLs usage.
The idea is that the EMPTY string (not the 'ippget' value) is
unambiguous. BECAUSE it's empty there is NOT a protocol target for
the IPP Printer object to send notifications to. The IPP client
must retrieve the notifications in-band via IPP.
OK?
Cheers,
- Ira McDonald
-----Original Message-----
From: Michael Sweet [mailto:mike@easysw.com]
Sent: Tuesday, October 23, 2001 10:13 AM
To: Hastings, Tom N
Cc: ipp (E-mail); IPP FAX DL (E-mail)
Subject: Re: IPP> NOT - IPPGET Delivery Method - ISSUE 02 'ippget' URI
"Hastings, Tom N" wrote:
>
> Or maybe it would be simpler just to include 'ippget' as if it were a URL
> scheme in "notify-schemes-supported", but with the definition that when
> using this "scheme", the URL in "notify-recipient-uri" is actually a
> zero-length string.
> ...
Assuming that the IETF allows "ippget" as a scheme name, then
allowing "ippget" as the only allowed notify-recipient-uri should
also be OK (and perhaps less confusing than passing in a 0-length
string which might trigger other parsing errors since some IPP
implementations might validate URI values as valid URIs... :)
-- ______________________________________________________________________ Michael Sweet, Easy Software Products mike@easysw.com Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Wed Oct 24 2001 - 21:43:57 EDT