I've been doing that as I go through the new-and-improved IPP conformance tests; this is the only one I saw for the required IPP/1.1, 2.0, 2.1, or 2.2 printer attributes.
On Sep 14, 2011, at 3:25 PM, Ira McDonald wrote:
> Hi Mike,
>> Yes - it looks like a bug to me too.
>> We should look through RFC 2911 to see if there are other
> complex "xxx-supported" capabilities attributes that didn't
> get originally registered correctly in IANA IPP Registry.
> - Ira
>> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Co-Chair - IEEE-ISTO PWG IPP WG
> Chair - TCG Embedded Systems Hardcopy SWG
> 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> Christmas through April:
> 579 Park Place Saline, MI 48176
> May to Christmas:
> PO Box 221 Grand Marais, MI 49839
>>>> On Wed, Sep 14, 2011 at 3:53 PM, Michael Sweet <msweet at apple.com> wrote:
> All (particularly Ira... :),
>> Looks like the IANA registration for number-up-supported is messed up. It currently just says:
>> Job Template number-up-supported integer(1:MAX) [RFC2911]
> but it should be:
>> Job Template number-up-supported 1setOf (integer(1:MAX) | rangeOfInteger(1:MAX)) [RFC2911]
> 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.
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>>
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...