You're right. Lost my mind.
Handle them w/ new values for existing attributes (same way
we handle Printer MIB TC updates for existing datatypes).
So we need to work out that process (I agree with you that a
durable pointer into the PWG email archives is sufficient).
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
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 Mon, Dec 9, 2013 at 4:17 PM, Michael Sweet <msweet at apple.com> wrote:
>> On Dec 9, 2013, at 3:04 PM, Ira McDonald <blueroofmusic at gmail.com> wrote:
>> Hi Mike,
>> I like your clarifications as suggested.
>> Are you suggesting a *tiny* document that updates JPS3 and extends
>>> No, I really don't want to open up that can of worms.
>> It seems like it would be nice to handle this as a minor release update
> to JPS3 (so that everyone sees it). I know, process...process. But this
> seems like the cleaner fix to me.
>>> I know I don't have the cycles or the energy to update JPS3 right now.
> Given our recent move to start accepting value registrations on the
> mailing list (with the mailing list serving as the durable source of
> information), I was hoping we could simply treat these as new value
> registrations for existing attributes and do the registration. Both
> attributes are type2 and permit extension without full standards backing
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>-------------- next part --------------
An HTML attachment was scrubbed...