[IPP] Update IANA registry in advance of errata resolution for Issue #113?

[IPP] Update IANA registry in advance of errata resolution for Issue #113?

Kennedy, Smith (Wireless & IPP Standards) smith.kennedy at hp.com
Mon Jun 27 15:22:25 UTC 2022



> On Jun 27, 2022, at 8:52 AM, Ira McDonald <blueroofmusic at gmail.com> wrote:
> 
> Hi Smith,
> 
> I agree with your suggestion.  I also agree with Mike that we should explicitly document
> our rationale for the range starting at 0.

Agree as well!

> 
> We don't have an IPP WG call until 7 July (10 days from now).  We can certainly discuss
> this proposal first on that call, if that suits everyone?

Works for me!

> 
> Cheers,
> - Ira
> 
> Ira McDonald (Musician / Software Architect)
> Chair - SAE Trust Anchors and Authentication TF
> Co-Chair - TCG Trusted Mobility Solutions WG
> Co-Chair - TCG Metadata Access Protocol SG
> 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
> http://sites.google.com/site/blueroofmusic <http://sites.google.com/site/blueroofmusic>
> http://sites.google.com/site/highnorthinc <http://sites.google.com/site/highnorthinc>
> mailto: blueroofmusic at gmail.com <mailto:blueroofmusic at gmail.com>
> (permanent) PO Box 221  Grand Marais, MI 49839  906-494-2434
> 
> 
> On Mon, Jun 27, 2022 at 9:40 AM Michael Sweet via ipp <ipp at pwg.org <mailto:ipp at pwg.org>> wrote:
> Smith,
> 
> I'm generally in favor of this, although I want to do a bit more research to determine why the current registration has the rangeOfInteger(0,MAX) syntax - I have a vague feeling there was a reason for this (tied to MSN's roll limits) but we should be consistent and document the reasons for the range so there is no confusion going forward.
> 
> 
> > On Jun 23, 2022, at 4:50 PM, Kennedy, Smith (Wireless & IPP Standards) via ipp <ipp at pwg.org <mailto:ipp at pwg.org>> wrote:
> >
> > Signed PGP part
> > Greetings,
> >
> > In advance of an erratum resolution in PWG 5100.7 for Issue #113 (https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q <https://www.pwg.org/dynamo/issues.php?L113+P-1+S-2+I0+E0+Z67+Q>), HP Inc. is requesting updating the registration of the "media-size" members of "media-col-database" and "media-col-ready" to also list the "rangeOfInteger" syntax in addition to the current "integer" syntax. HP Inc. is also requesting that the definitions specify a lower bounds of 0 instead of 1 for the "x-dimension" and "y-dimension" members of "media-col-database" and "media-col-ready" to match the member definitions in the "media-col" Job Template attribute.
> >
> > The current registration listed on pages 58 and 60 of PWG 5100.7-2019 are:
> >
> > media-col-database (1setOf collection)
> >   <Any "media-col" member attribute>
> >   media-source-properties (collection)
> >     media-source-feed-direction (type2 keyword)
> >     media-source-feed-orientation (type2 enum)
> >
> > media-col-ready (1setOf collection)
> >   <Any "media-col" member attribute>
> >   media-source-properties (collection)
> >     media-source-feed-direction (type2 keyword)
> >     media-source-feed-orientation (type2 enum)
> >
> > media-size-supported (1setOf collection)
> >   x-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))
> >   y-dimension (integer(1:MAX) | rangeOfInteger(1:MAX))
> >
> > If HP Inc.'s requests are followed, the IANA IPP Registry would be updated like so (changes in red if you can see color):
> >
> > media-col-database (1setOf collection)
> >   <Any "media-col" member attribute>
> >   media-size (collection)
> >     x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >     y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >   media-source-properties (collection)
> >     media-source-feed-direction (type2 keyword)
> >     media-source-feed-orientation (type2 enum)
> >
> > media-col-ready (1setOf collection)
> >   <Any "media-col" member attribute>
> >   media-size (collection)
> >     x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >     y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >   media-source-properties (collection)
> >     media-source-feed-direction (type2 keyword)
> >     media-source-feed-orientation (type2 enum)
> >
> > media-size-supported (1setOf collection)
> >   x-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >   y-dimension (integer(0:MAX) | rangeOfInteger(0:MAX))
> >
> >
> > Doing this registration sooner rather than later will help systems that generate code from the IANA IPP Registry, such as "jipp".
> >
> > Let me know if there are any objections to this registration via email or we can discuss at the next IPP Workgroup call.
> >
> > Cheers,
> >
> > Smith
> >
> > /**
> >     Smith Kennedy
> >     HP Inc.
> > */
> >
> >
> >
> 
> ________________________
> Michael Sweet
> 
> _______________________________________________
> ipp mailing list
> ipp at pwg.org <mailto:ipp at pwg.org>
> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20220627/4c6d3242/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20220627/4c6d3242/attachment.sig>


More information about the ipp mailing list