[IPP] Updated JPS3 draft posted

[IPP] Updated JPS3 draft posted

Yousey, Marc marc.yousey at hp.com
Mon Mar 7 21:53:21 UTC 2011


That will teach me to write an email when I'm walking out the door on Friday.

You're right Mike that I was talking about job-uuid and not job-uri.  I'm just making sure we're not adding another job specifier to the uri/id mess we have now.

Thanks,
M.


From: Ira McDonald [mailto:blueroofmusic at gmail.com]
Sent: Saturday, March 05, 2011 6:14 AM
To: Michael Sweet; Ira McDonald
Cc: Yousey, Marc; ipp at pwg.org
Subject: Re: [IPP] Updated JPS3 draft posted

Hi Mike and Mark,

True, RFC 2911 allows "job-uri" alone to be specified
for *some* Job operations.

But RFC 2911/2910 do not specify the relationship
between "job-uri" and "printer-uri" (which is a bug).

So the later RFC 3510 ('ipp' URI Scheme) was unable
to specify any such relationship.

Which is why I've seen quite a few IPP implementations
that do NOT accept a "job-uri" value as HTTP request-URI
(i.e., as a protocol endpoint) - since it's implementation
dependent anyway, they simply refuse to honor stand-alone
"job-uri".  I have always advised my clients to avoid the
assumption that "job-uri" is a safe protocol endpoint.

IPP Everywhere cannot really fix this ambiguity.  And
just saying that "job-uri" should work won't help any.

OTOH - "printer-uri" plus "job-id" is safe and reliable.

My two cents.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com<mailto:blueroofmusic at gmail.com>
Christmas through April:
  579 Park Place  Saline, MI  48176
  734-944-0094
May to Christmas:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


On Sat, Mar 5, 2011 at 4:21 AM, Michael Sweet <msweet at apple.com<mailto:msweet at apple.com>> wrote:

On Mar 5, 2011, at 12:06 AM, Ira McDonald wrote:
> ...
> Note that our DMTF CIM_PrintInputTray class has the
> element "MediaSizeName" which we used to map from
> the Printer MIB's "prtInputMediaDimFeedDirDeclared"
> and "prtInputMediaDimFeedDirDeclared" objects.
media-size-name it is, then...

> Also note that either "job-uri" or "job-id" can be used in
> job operations, but either MUST be accompanied by the
> enclosing "printer-uri" that specifies the over-the-wire
> protocol target of the IPP over HTTP request.
Actually, only job-id needs the printer-uri. job-uri can stand alone, per 2911...

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20110307/92bdec61/attachment-0001.html>


More information about the ipp mailing list