Re: [IPP] IPP Everywhere tests
Michael Sweet via ipp <ipp@pwg.org> Fri, 01 May 2020 19:00 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 E3DA93A1A49 for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 1 May 2020 12:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level:
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 zDNZ4fKqNrLT for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 1 May 2020 12:00:29 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 645563A1A61 for <ipp-archive2@ietf.org>; Fri, 1 May 2020 12:00:28 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id DFE96C847; Fri, 1 May 2020 19:00:27 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id B15962660; Fri, 1 May 2020 19:00:24 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id ACB8B3A57; Fri, 1 May 2020 19:00:23 +0000 (UTC)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTP id 39D4F26ED for <ipp@pwg.org>; Fri, 1 May 2020 19:00:23 +0000 (UTC)
Received: from imacpro.lan (host-148-170-144-200.public.eastlink.ca [148.170.144.200]) by mail.msweet.org (Postfix) with ESMTPSA id 3E42F82117; Fri, 1 May 2020 19:00:22 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <20AD20E7-421D-46B9-92C2-387081DB47F6@xerox.com>
Date: Fri, 01 May 2020 15:00:20 -0400
Message-Id: <E5C7E25D-3F10-4A59-B88A-2D55B6DC8301@msweet.org>
References: <20AD20E7-421D-46B9-92C2-387081DB47F6@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] IPP Everywhere tests
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: multipart/mixed; boundary="===============1765601500259588954=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Chris, > On May 1, 2020, at 1:35 PM, Rizzo, Christopher via ipp <ipp@pwg.org> wrote: > > Mike, > > Apologies for not raising this sooner, I have not been able to get to running all these tests because of other work, and because I need to make fixes for failed tests where needed. I am continuing to run IPP everywhere tests, but while doing so I am modifying code to get the failing tests to pass, so testing for me is not just testing alone... As I continue to get the code written to pass the tests, I could run into other issues. > > 1. document-password-supported IPP Everywhere test fails: > > I-10. Get-Printer-Attributes Operation (default) [FAIL] > RECEIVED: 15326 bytes in response > status-code = successful-ok (successful-ok) > EXPECTED: document-password-supported > > PWG 5100.13 document-password or document-password-supported are OPTIONAL. Test should not fail based on EXPECT document-password-supported. Correct? IPP Everywhere makes it CONDITIONALLY REQUIRED for printers that support PDF files (which can have passwords to decrypt the contents...) > 2. job-ids-supported - PWG-5100.11, Section 10.2 - 1st sentence should be "... the Printer supports the "job-ids" attribute for the following Operations: Purge-Jobs and Get-Jobs.", the 1st sentence implies that "job-ids" is an operation? Section 6.5 2nd sentence implies job-ids is an operation, but I believe it is just an attribute to an operation. Look to PWG 5100.7 for that now - from 5100.7-2019: 5.5.20 job-ids-supported (boolean) This REQUIRED attribute specifies whether the "job-ids" operation attribute (section 5.1.3) is supported. > 3. Should the following be job-preferred-attributes-supported? IPP everywhere spec table 6 lists job-preferred-attributes-supported, but PWG 5100.13 5.6.19 lists preferrred-attributes-supported, and section 6.12 paragraph 2 refers to job-preferred-attributes-supported. Are preferred-attributes-supported and job-preferred-attributes-supported different attributes? > > I-10. Get-Printer-Attributes Operation (default) [FAIL] > RECEIVED: 15349 bytes in response > status-code = successful-ok (successful-ok) > EXPECTED: preferred-attributes-supported It should be "preferred-attributes-supported", which is what the current draft of IPP Everywhere 1.1 lists... :) https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20200417.pdf <https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20200417.pdf> ________________________ Michael Sweet
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] IPP Everywhere tests Rizzo, Christopher via ipp
- Re: [IPP] IPP Everywhere tests Michael Sweet via ipp