I think I start agreeing with you on this one. My recollection is that we
got this as part of our discussion to use a MIME part for the encoding.
MIME purists have stated that all MIME types MUST be transport independent.
I think that having an object that can be mapped to another transport has
its virtues, but I was never convinced that it would ever make sense to
actually send the "application/ipp" object over email. Alternative
transports that make sense to me are things like the emerging HTTP-NG
protocol, and that is most likely able to handle URLs the same way as HTTP
If somebody REALLY wants to send "application/ipp" over email, then they
would need to have an email address in the place where we are using the
HTTP URIs anyway, and I expect that such a mailbox would be dedicated to
the IPP printer and know what to do with messages it receives. In short,
new transport, new addressing scheme.
In summary, I think we should remove any redundant URI information in the
"application/ipp", it seems to cause more confusion than what it is worth.
Principal Engineer - Advanced Printing Standards - Xerox Corporation
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
Phone +1-310-333 8273, Fax +1-310-333 5514