Re: [IPP] pwg-5100.13 section 5.6.39 printer-supply encoding

Michael Sweet via ipp <ipp@pwg.org> Thu, 07 May 2020 23:27 UTC

Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC0443A0B32 for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 7 May 2020 16:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAL07isKGraC for <ietfarch-ipp-archive@ietfa.amsl.com>; Thu, 7 May 2020 16:27:31 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 42DB43A0A43 for <ipp-archive2@ietf.org>; Thu, 7 May 2020 16:27:31 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id B2F9E34E8; Thu, 7 May 2020 23:27:30 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id AE2B626F0; Thu, 7 May 2020 23:27:27 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id BA50D28D9; Thu, 7 May 2020 23:27:26 +0000 (UTC)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTP id 4C2681E49 for <ipp@pwg.org>; Thu, 7 May 2020 23:27:26 +0000 (UTC)
Received: from mbp16.lan (host-148-170-144-200.public.eastlink.ca [148.170.144.200]) by mail.msweet.org (Postfix) with ESMTPSA id 99214808BB; Thu, 7 May 2020 23:27:22 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <0A928404-13DF-4D11-A68F-064210FC90A4@xerox.com>
Date: Thu, 07 May 2020 19:27:19 -0400
Message-Id: <A1AE1F3F-36EC-4E87-A538-20218D48574D@msweet.org>
References: <0A928404-13DF-4D11-A68F-064210FC90A4@xerox.com>
To: "Rizzo, Christopher" <Christopher.Rizzo@xerox.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] pwg-5100.13 section 5.6.39 printer-supply encoding
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Michael Sweet via ipp <ipp@pwg.org>
Reply-To: Michael Sweet <msweet@msweet.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Chris,

Only list the properties that are present in the MIB entries - thus the non-colorant supplies don't have the colorantxxx properties.

The colorantname only required for supplies with associated colorants, and the ABNF lists it as OPTIONAL (and so the IPP Everywhere tests don't require it...) but I do see it listed as REQUIRED in Table 9 (which is an error - the intent was for note 3 to apply to all of the colorant properties...)


> On May 7, 2020, at 6:27 PM, Rizzo, Christopher via ipp <ipp@pwg.org> wrote:
> 
> Table 9 has optional printer-supply (1setOf octetString(MAX)) keywords.
>  
> Some supplies have colorants, others have colorantIndex = 0 ("this supply does not depend on a single specified colorant").
>  
> Must each entry in the set of octetStrings contain the same SNMP Supply Objects (matching cardinality), or can colorant objects be present in an octetString for those supplies that have a colorant, but not present in an octetString for those supplies that do not have a colorant?
>  
> For example, must we do this:
>  
> // Black toner.
> printer-supply[1] =
> type=toner;maxcapacity=100;level=75;index=1;markerindex=1;
> class=supplyThatIsConsumed;unit=percent;
> colorantindex=1;colorantrole=process;colorantname=black;
> coloranttonality=256;
>  
> // Fuser does not have concept of colorant.
> printer-supply[2] =
> type=fuser;maxcapacity=100;level=96;index=2;markerindex=1;
> class=supplyThatIsConsumed;unit=percent;
> colorantindex=0;colorantrole=???;colorantname=???;
> coloranttonality=???;
>  
> Or should we do this (is it legal to have colorant entries for some supplies, but not have colorant entries for others in the set (non-matching cardinality)?):
>  
> // Black toner.
> printer-supply[1] =
> type=toner;maxcapacity=100;level=75;index=1;markerindex=1;
> class=supplyThatIsConsumed;unit=percent;
> colorantindex=1;colorantrole=process;colorantname=black;
> coloranttonality=256;
>  
> // Fuser does not have concept of colorant.
> printer-supply[2] =
> type=fuser;maxcapacity=100;level=96;index=2;markerindex=1;
> class=supplyThatIsConsumed;unit=percent;colorantname=unknown;
>  
>  
> And since colorantname is REQUIRED, what value should it have for a supply that is not associated with any colorant (unknown or other appear to be the only available values in RFC3805)?
>  
> Thanks,
> Chris
>  
> Christopher Rizzo
> Xerox Corporation
> GDG/Discovery/Advance Technology
> 26600 SW Parkway Ave.
> Wilsonville, OR 97070-9251
> Phone: (585) 314-6936
> Email: Christopher.Rizzo@xerox.com
>  
> "The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs."
> -Maurice Wilkes, Memoirs of a Computer Pioneer
> _______________________________________________
> ipp mailing list
> ipp@pwg.org
> https://www.pwg.org/mailman/listinfo/ipp

________________________
Michael Sweet



_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp