Hi Tom,
Sorry this is so obscure.
The real reason is quite simple.
RFC 3805 defined two SEPARATE MIB modules:
IANA-PRINTER-MIB
- enums that can be changed and are IANA managed
(so-called "Type 2" enums)
Printer-MIB
- enums that CANNOT be changed because IANA doesn't have them
(so-called "Type 1" enums)
- also all the objects in the main body of the MIB (also can't be changed)
Your prtMarkerSuppliesSupplyUnitTC is in the second module.
It's just a physical impossiblity to change it without an entire
new RFC, because IANA does NOT have the source file to
this second MIB module.
Do you see?
This is very badly explained in section 2.4.1 of RFC 3805 - using the
Type 1 and Type 2 language of IPP/1.1 (RFC 2911).
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Tue, Nov 15, 2011 at 3:32 PM, Silver, Thomas <Thomas.Silver at xerox.com>wrote:
> Hi folks,****
>> ** **
>> Sorry for the delayed response. Thank you for considering my proposal
> during your WIMS WG meeting. I do appreciate that time that was spent
> discussing this request. However, I still do NOT understand why our
> proposal to add ‘hundredthsOfInkSticks(20)’ to
> ‘PrtMarkerSuppliesSupplyUnitTC’ was rejected. Why does a new enum for this
> optional object require a new RFC in order to extend the enum definitions?
> The only rationale that I can loosely apply to your position is that the
> enums for the ‘prtMarkerSuppliesSupplyUnit’ object may be defined as Type 1
> enums. Unfortunately, I cannot find anything within RFC 3805 which defines
> the optional ‘prtMarkerSuppliesSupplyUnit’ object as requiring type 1
> enums. Therefore, can you please help me understand where this is defined
> and why? Until then, I will remain confused about your decision…****
>> ** **
>> Thanks,****
>> Tom****
>> ** **
>> * ** ***
>> *Thomas Silver*
>> *Mgr, Device Compliance*
>> *Global Remote Services*
>> *Xerox Information Management*
>> *Xerox Corporation*
>> 800 Phillips Road, MS 111-04A, Webster, NY 14580****
>> Office 4420
>thomas.silver at xerox.com> 585-422-7219 / 8*702-7219****
>> ** **
>> ** **
>> *From:* Ira McDonald [mailto:blueroofmusic at gmail.com]
> *Sent:* Friday, October 28, 2011 5:48 PM
> *To:* Silver, Thomas; Michael R Sweet; pmp at pwg.org; wims at pwg.org; Ira
> McDonald
> *Subject:* Response to Xerox request for IANA Printer MIB enumerations****
>> ** **
>> Hi Thomas,
>> The WIMS WG discussed your request at our teleconference yesterday
> and reached the following consensus:
>>> (1) add ‘hundredthsOfInkSticks(20)’ to ‘PrtMarkerSuppliesSupplyUnitTC’
> - rejected - rationale: TC in Printer MIB module - requires new RFC
> - but PWG Steering Committee has asked WIMS WG to consider a
> Printer MIB v3 (moving TCs to IANA Printer MIB) at December F2F
> (this would require several years given IETF process delays)
> - recommendation - use 'percent' for now
>> (2) add ‘standardToner(35)’ to ‘PrtMarkerSuppliesTypeTC’
> - rejected - rationale: 'standard' is the default of any supply type
> (Mike S)
> - recommendation - treat any unmodified supply type as 'standard'
>> (3) add ‘matteToner(35)’ to ‘PrtMarkerSuppliesTypeTC’
> - accepted - rationale: widely used distinct toner type (Mike S)
>> Also:
> (4) add 'matteInk(36)' ‘PrtMarkerSuppliesTypeTC’
> - rationale: widely used distinct toner type (Mike S)
>> I will send these registrations to IANA shortly.
>> Cheers,
> - Ira (one of IETF Designated Experts for Printer MIB, along w/ Mike Sweet)
>>> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Secretary - IEEE-ISTO Printer Working Group
> Co-Chair - IEEE-ISTO PWG IPP WG
> Chair - TCG Embedded Systems Hardcopy SG
> 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> Winter 579 Park Place Saline, MI 48176 734-944-0094
> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434****
>> ** **
>
--
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/wims/attachments/20111115/5fb222a1/attachment-0001.html>