IETF Logo Mail Archive

Re: [IPP] Update registration for "printer-current-time" Printer Description attribute in IANA Registry; was Re: Minutes posted from today's concall

Michael Sweet via ipp <ipp@pwg.org> Tue, 27 October 2020 01:09 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 2486D3A1149 for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 26 Oct 2020 18:09:20 -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 zh0sR23dYs7n for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 26 Oct 2020 18:09:18 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id E34D93A1147 for <ipp-archive2@ietf.org>; Mon, 26 Oct 2020 18:09:18 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 95BC5E904; Tue, 27 Oct 2020 01:09:18 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id CFB1DE8F0; Tue, 27 Oct 2020 01:09:16 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 215BB36C; Tue, 27 Oct 2020 01:09:16 +0000 (UTC)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by mail.pwg.org (Postfix) with ESMTP id B723036C for <ipp@pwg.org>; Tue, 27 Oct 2020 01:09:15 +0000 (UTC)
Received: from [10.0.1.64] (host-148-170-144-200.public.eastlink.ca [148.170.144.200]) by mail.msweet.org (Postfix) with ESMTPSA id 64EDA8258F; Tue, 27 Oct 2020 01:09:14 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
In-Reply-To: <CAN40gSv=v_c6UCTAmUjaDGfHnPGxoGkpGmQztH-V2Fs=gZzpmQ@mail.gmail.com>
Date: Mon, 26 Oct 2020 21:09:13 -0400
Message-Id: <4ADB2699-8F17-4FFF-A7A8-50BA57B96443@msweet.org>
References: <5C7BC033-7981-4447-B6DE-BF882003EBA7@msweet.org> <0BF17E9B-ED0B-4BE6-86D6-0A75DE13B28B@hp.com> <C59D87DE-3830-46BC-9076-8CBC4B30CD38@msweet.org> <CAN40gSv=v_c6UCTAmUjaDGfHnPGxoGkpGmQztH-V2Fs=gZzpmQ@mail.gmail.com>
To: Ira McDonald <blueroofmusic@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] Update registration for "printer-current-time" Printer Description attribute in IANA Registry; was Re: Minutes posted from today's concall
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>

Ira,

> On Oct 26, 2020, at 8:34 PM, Ira McDonald <blueroofmusic@gmail.com> wrote:
> 
> Hi,
> 
> The lack of REQUIRED "printer-current-time" to populate "date-time-at-xxx"
> attributes is an *old* problem - noticed in the first draft of IPP 2.0.  In RFC
> 8011, it's still (incorrectly) RECOMMENDED, which breaks the preferred
> "date-time-at-xxx" attributes (the only useful ones in a Job Log) - and RFC
> 8011 is the authoritative source definition in the IANA IPP Registry, so this
> can't simply be fixed in a PWG 5100.x spec (I think?).

So dateTime attributes were all optional in IPP/1.1 and IPP/2.0.  And we updated the definition of printer-current-time to include the 'unknown' syntax since it was already explicitly allowed in RFC 2911, just not included in the syntax definition for printer-current-time...

The issue for the registry is that when I updated the registrations for RFC 8011 I didn't update the printer-current-time syntax to match the document.  I'll include a fix for that in my next dump for IANA.

The issue for IPP Everywhere is that 1.0 didn't explicitly require it but *did* require date-time-at-xxx - clearly the intent was to require printer-current-time but we missed it.  IPP Everywhere 1.1 makes it RECOMMENDED and notes that the omission from 1.0 was an error since we *did* require date-time-at-xxx.  IPP Everywhere 2.0 will be able to make it REQUIRED.

Anyways...

________________________
Michael Sweet



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

v2.23.0 | Report a Bug | By Email