All,
It recently came to my attention that a vendor had used, without registration, some enum values in the standards-track range.
It is very important that all IPP implementations follow the registration process defined in RFC 2911. Operation codes from 0 to 0x3FFF are reserved for standards-track work. Operation codes from 0x4000 to 0x8FFF are reserved for vendor extensions. You can request a block of vendor extension operations by sending an email to me (or whoever the current IPP WG secretary happens to be); details are at:
http://pwg.org/ipp/opcodes/ippopcodes.html
For other enum values (like "finishings", etc.) and new value tags, all values from 0 to 0x3FFFFFFF are standards-track and values from 0x4000000 to 0x7FFFFFFF are reserved for vendor extensions. In most cases you can register standards-track values by sending an email to the IPP WG list with your registration template. If you do not want have this information publicly available, use the vendor extension range. (and if there is interest I can setup a vendor enum page like the opcode page above...)
Thank you!
(PS - If you *have* been using standards-track enum values for your own vendor extensions, please let me know so that we can minimize further damage in the future...)
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4798 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20141112/5b0d9bd3/attachment.p7s>