[IPP] Minutes posted for today's IPP WG meeting

[IPP] Minutes posted for today's IPP WG meeting

[IPP] Minutes posted for today's IPP WG meeting

Michael Sweet msweet at apple.com
Fri Oct 9 13:30:52 UTC 2015


> On Oct 6, 2015, at 5:16 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com> wrote:
> Hi there,
> A couple of questions about the changes we agreed that I should make to the "job-password-repertoire" whitepaper:
> 1. There was this discussion of what to do about managing the set of possible values the device supports, vs. what the printer is configured to use:
> Q: Do we need multiple values?
> Original purpose was to tell client the 1 password format that is acceptable for job-password values
> Important to convey capabilities (only have a numeric keypad)
> Impossible to validate values when job-password is encrypted
> A: Want a separate job-password-repertoire-configured Printer attribute that specifies the repertoire to use at the client end, job-password-repertoire-supported Printer attributes lists all of the (currently) available repertoire (for use by admin to configure the -configured value)
> My worry about this is that this seems to break the "xxx" / "xxx-default" / "xxx-supported" design pattern that has been used thus far, because with this what would have been "xxx-supported" is now called "xxx-configured", and then the "xxx-supported" becomes an attribute that is considered by a tool engaging with the Printer via, for instance, a System Control Service.

Not exactly.  The consensus from the concall was to define two attributes:

    job-password-repertoire-configured (type2 keyword | name(MAX))

        The configured password repertoire that a client uses to limit and validate
        the values entered into the print UI.

    job-password-repertoire-supported (1setOf (type2 keyword | name(MAX)))

        The list of printer-supported repertoire that can be configured by the
        administrator in the job-password-repertoire-configured attribute.

This is consistent with how we handle printer settings for other things like natural language support - see the generated-natural-language-supported and natural-language-configured attributes from RFC 2911.

For printer/service settings (that are not part of the job ticket), the xxx-supported attribute lists the supported values while the xxx-configured attribute specifies the configured value.

For job tickets/settings we use xxx-default attributes to fill in values for missing Job Template xxx attributes.

> 2. The Section 5.1 recommendation that we use the IANA registry for "Hash Function Textual Names" seems woefully out-of-date (last updated in August of 2006!):
> https://www.iana.org/assignments/hash-function-text-names/hash-function-text-names.xml <https://www.iana.org/assignments/hash-function-text-names/hash-function-text-names.xml>
> I think it is pretty clear how the new values will be encoded, but wanted to point this out and see if there were any follow-up recommendations.  There seem to be a bunch of RFCs that didn't register new strings with IANA...

I don't think a SHA-3 RFC has come through yet, and sometimes registrations do get missed during document review.  Anyways, I'll be posting the registration template for the SHA-3 hashes to the IPP list today, which will take care of our needs...

> 3. Referencing NIST specs for deprecation recommendations - if someone can provide me with links to NIST deprecation recommendations, and to the SHA-2 specifications, I would appreciate it.  I seem to be having issues finding anything but the SHA-3 specs (already referenced).


Michael Sweet, Senior Printing System Engineer, PWG Chair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20151009/a73b2549/attachment.html>

More information about the ipp mailing list