CUPS & IPP_TAG_EXTENSION
Alexander Pevzner <[email protected]> Fri, 22 Mar 2024 12:06:26 +0300
| Newsgroups | dev.linux.lists.printing-architecture |
|---|---|
| Message-ID | <[email protected]> |
Hi Everybody, yet another question regarding IPP. In RFC8010, it is stated that IPP_TAG_EXTENSION is encoded similarly to any other tag: starting with 1 byte of tag (0x7f), followed by the attribute name, and then the attribute value. However, the RFC specifies that the first 4 bytes of the value should be reserved to encode 4 bytes of an extended tag. On the other hand, the CUPS implementation encodes 0x7f, followed by 4 bytes of the extended tag, and then the attribute name and value. So, the question arises: which approach is correct, CUPS or the RFC? -- Wishes, Alexander Pevzner ([email protected])