Hi Rick,
In IPP Job and Printer Set Operations (RFC 3380, September 2002),
'xxx-supported'
attributes are settable, because that's the ONLY way the administrator has
to restrict
by policy the use of capabilities that are built-in by the manufacturer but
should NOT
be used at the particular site. That approach comes from IPP/1.0 (RFC 2566)
and IPP/1.1
(RFC 2911) - which assumed the actual setting of 'xxx-supported' was done
out-of-band.
This goes all the way back to ISO DPA, where 'xxx-supported' had these same
semantics
and behavior - they are policy attributes, NOT fixed manufacturer capability
attributes.
RFC 3380 defines a new operation 'Get-Printer-Supported-Values' that allows
an
administrator to discover the existence of a manufacturer built-in
capability that has
been previously disabled by policy (and to restore it by setting the
appropriate
'xxx-supported' attribute).
Hope this helps the discussion.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: Richard_Landau@Dell.com [mailto:Richard_Landau@Dell.com]
Sent: Monday, August 22, 2005 3:27 PM
To: imcdonald@sharplabs.com; cwhittle@sharplabs.com; wims@pwg.org
Subject: RE: WIMS> CIM: August 18, 2005 minutes posted
Craig,
Good minutes, thanks. And I agree with all of them except the statement
that "xxx-supported attributes (policy administrator may restrict features
available to users) should be writable." I agree that Default, Current,
Max, and Available are reasonable writable properties for setup and policy
control, but I think that "Supported" is *generally* a statement of the
physical (or software) capabilities of the device, as specified by the
manufacturer, rather than policy, as set by the local manager.
For instance, the CIM_Printer.PaperSizesSupported property contains a list
of physical sizes that can pass thru the printer. I think that list comes
from the manufacturer and is not writable. Similarly for
LanguagesSupported, CharSetsSupported, NaturalLanguagesSupported, etc. On
the other side, I think that MaxSizeSupported (in Kbytes, remember) seems to
be a sensible policy control. Are there cases in the gray area?
Hate to say it, but I think we will have to review these one by one, both
the ones already in CIM_Printer and the ones that we will probably add from
Printer MIB and IPP. I just don't know enough about IPP to understand the
distinctions in the specs.
In any case, I think the blanket statement that xxx-supported should be
writable goes a little too far. I might have agreed with it during the
phone call. If so, I apologize for being misleading.
rick
_____
From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of McDonald,
Ira
Sent: Thursday, August 18, 2005 17:05
To: Whittle, Craig; 'wims@pwg.org'
Subject: RE: WIMS> CIM: August 18, 2005 minutes posted
Hi Craig,
Good minutes - thanks.
All - please look at Printer and _other_ object classes in CIM Printing.
Overall,
a very small number of the Printer MIB and IPP attributes are presently
defined
in CIM Printing. This affects the size of the eventual alignment work
(nearterm
it's smaller, longterm it's a much bigger job than I had anticipated).
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
-----Original Message-----
From: owner-wims@pwg.org [mailto:owner-wims@pwg.org]On Behalf Of Whittle,
Craig
Sent: Thursday, August 18, 2005 4:36 PM
To: 'wims@pwg.org'
Subject: WIMS> CIM: August 18, 2005 minutes posted
All:
Minutes from the PWG-CIM Alignment Working Group teleconference call have
been posted. See ftp://ftp.pwg.org/pub/pwg/wims/cim/minutes/cim_050818.pdf
<ftp://ftp.pwg.org/pub/pwg/wims/cim/minutes/cim_050818.pdf> .
Best regards,
**CW
This archive was generated by hypermail 2b29 : Tue Aug 23 2005 - 10:31:53 EDT