Re: [IPP] Update registration for "printer-current-time" Printer Description attribute in IANA Registry; was Re: Minutes posted from today's concall
Ira McDonald via ipp <ipp@pwg.org> Tue, 27 October 2020 19:15 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 4084A3A1517 for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 27 Oct 2020 12:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 Z3nm2gukGIfE for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 27 Oct 2020 12:15:12 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 686593A0E23 for <ipp-archive2@ietf.org>; Tue, 27 Oct 2020 12:15:12 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id A875EE8E9; Tue, 27 Oct 2020 19:15:10 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 0DC651C7C; Tue, 27 Oct 2020 19:15:06 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id F05932635; Tue, 27 Oct 2020 19:15:04 +0000 (UTC)
Received: from mail-vk1-xa36.google.com (mail-vk1-xa36.google.com [IPv6:2607:f8b0:4864:20::a36]) by mail.pwg.org (Postfix) with ESMTPS id 99D9E1C7C for <ipp@pwg.org>; Tue, 27 Oct 2020 19:15:03 +0000 (UTC)
Received: by mail-vk1-xa36.google.com with SMTP id u202so633479vkb.4 for <ipp@pwg.org>; Tue, 27 Oct 2020 12:15:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/vNs1M0JrynkJAdCa1hIM+rg2UkF8iteDIn36dABUxs=; b=ZvfBuPT5G4UkhZnvyfZRk324cRAgy1bmcw7kcSaC5nEhIUggH7t25s/fZovcKiogjh pLAQ7cLE8fdzY5Cth89yvEKWCRWqcdzk3qL6MrXwMrqNPn3h32Ez/s/F7N+Bj9gZUjMM ri6i+CCFs1pD10otUJB+1BnYMUCVz/jElYQx3PrE+ktP/PER6HRoLHr4iB90+9DNkPIo e17lSbsC2LW2JMLDb4yv/xd1A7UtXg00GqeHVyhJwdWXmIu+I9ZUMrZ9UrCNzg7Uph+1 j3bzK4LdG37wN0JaBPKeMB+fjq7elpsG4Q/Bp80rjGapFpAfL6mZS6roI0bklGoqJ1m8 k2Ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/vNs1M0JrynkJAdCa1hIM+rg2UkF8iteDIn36dABUxs=; b=tz6+ANZeTBaagBVx4UbDNFh5mgasbL7G8uEhsqq1PXeCTQmX2ZJng9ZZZbZzmpmSjR m38257kJ34XHQyds8MsfO1GrpXcFdtDFjfZ7YukvSRjVfOIluOnl3GKe7OhEbdx1Zdkm aOoey9q1OEh5UbasG8AgYqG27mRfGwNJwCH4mOGCilzLS9W5Xs+boArT24Aa3/ra59xL WzmcTqvDDin7ATg7PA9nsmi36KVo4+TxnW/wGo10ei2OQf7ApyJ0whUN+3eAyF+I5CxO Uhi98UFMqLNNwHFFjJMboqw04YEvFvcZusTEiAJZ8N/xKfiUaDxpZzFG28gF6CYYgdzM U2yg==
X-Gm-Message-State: AOAM532a13qYESqgIhOvgPVn0+v+trUiOaV+GbSpBpnBBCgMmPM1zWAG 7eHwbzmFAnWlUlLNgFqL8S2GC4KsGNw10FkBboY=
X-Google-Smtp-Source: ABdhPJxqod1OjeDHjmve68JbUzIUUnR8OGGqgRIejObYULWf5cqKehna5rjEJfwftvSw+pjb8KSIeuP7DxRfVbW9apA=
X-Received: by 2002:a1f:a94c:: with SMTP id s73mr2813358vke.19.1603826102039; Tue, 27 Oct 2020 12:15:02 -0700 (PDT)
MIME-Version: 1.0
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> <4ADB2699-8F17-4FFF-A7A8-50BA57B96443@msweet.org> <CAN40gStQ2UUzYO5B-4b3OyqKDpBaQN886nrd1U_-NTaaHsaLAQ@mail.gmail.com> <BCDED9E1-EF02-4F65-BDDA-1ED0922B7C45@hp.com> <E5DA61D3-122F-40D5-A38A-B6CFD229491E@msweet.org> <07C45F47-E887-4862-AFDF-474451CF3365@hp.com>
In-Reply-To: <07C45F47-E887-4862-AFDF-474451CF3365@hp.com>
Date: Tue, 27 Oct 2020 15:14:46 -0400
Message-ID: <CAN40gSv224nBu1y7T3zecM+Fwzx1R-pgegqnB_ObWbXE+2nPiQ@mail.gmail.com>
To: "Kennedy, Smith (Wireless & IPP Standards)" <smith.kennedy@hp.com>, Ira McDonald <blueroofmusic@gmail.com>
Cc: PWG IPP WG Reflector <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: Ira McDonald via ipp <ipp@pwg.org>
Reply-To: Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/mixed; boundary="===============7385930510105026118=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Hi Smith, Thanks for the clarification. Mike has been suggesting for some time that we should never create any more numbered versions of IPP. Instead, we should use "ipp-features-supported" and "[format]-features-supported" for better clarity. I agree with Mike. 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 WGSecretary - IEEE-ISTO Printer Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF Designated Expert - IPP & Printer MIBBlue Roof Music / High North Inchttp://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@gmail.com <blueroofmusic@gmail.com>(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434* On Tue, Oct 27, 2020 at 3:09 PM Kennedy, Smith (Wireless & IPP Standards) < smith.kennedy@hp.com> wrote: > Sorry, I should have been more clear that I was suggesting we should > update the normative requirements to make all levels (if we have levels) > REQUIRE the "date-time-at-xxx" and "printer-current-time" whenever we > decide to create an "IPP/3". > > > On Oct 27, 2020, at 11:31 AM, Michael Sweet <msweet@msweet.org> wrote: > > Smith, > > IPP 2.1 and 2.2 require the dateTime attributes. IPP 2.0 doesn't, and we > can't really change that for IPP 2.0 since the versioning is pretty well > hardcoded (a good reason never to do that again... :) > > > > On Oct 27, 2020, at 11:52 AM, Kennedy, Smith (Wireless & IPP Standards) < > smith.kennedy@hp.com> wrote: > > > > Hi Ira, > > > > I think all 2.x levels should REQUIRE the "date-time-at-xxx" and > "printer-current-time", since any printers that have an un-initialized > clock can always use the 'unknown' out-of-band value, to reduce the > variability between levels. Even basic printers ought to be able to do that > at this point if they are implementing IPP, don't you think? > > > > Smith > > > > /** > > Smith Kennedy > > HP Inc. > > */ > > > >> On Oct 27, 2020, at 9:22 AM, Ira McDonald <blueroofmusic@gmail.com> > wrote: > >> > >> Hi Mike, > >> > >> About where we RECOMMEND or REQUIRE the "date-time" attributes: > >> > >> In eventual IPP/2.x update, I suggest that IPP/2.1 (Enterprise) and > >> IPP/2.2 (Production) should REQUIRE the "date-time" attributes (since > >> this will after all be a major update to the previous PWG Standard of > >> IPP/2.x). > >> > >> Rick Landau (Dell) and I ran up against this issue way back when we > >> were doing mappings to DMTF CIM classes (where real date-time was > >> already ubiquitous). > >> > >> WDYT? > >> > >> 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/highnorthinc > >> mailto: blueroofmusic@gmail.com > >> (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434 > >> > >> > >> On Mon, Oct 26, 2020 at 9:09 PM Michael Sweet <msweet@msweet.org> > wrote: > >> 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 > >> > >> > >> > > > > ________________________ > Michael Sweet > > > >
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] Minutes posted from today's concall Michael Sweet via ipp
- [IPP] Update registration for "printer-current-ti… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Update registration for "printer-curren… Michael Sweet via ipp
- Re: [IPP] Update registration for "printer-curren… Ira McDonald via ipp
- Re: [IPP] Update registration for "printer-curren… Michael Sweet via ipp
- Re: [IPP] Update registration for "printer-curren… Ira McDonald via ipp
- Re: [IPP] Update registration for "printer-curren… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Update registration for "printer-curren… Michael Sweet via ipp
- Re: [IPP] Update registration for "printer-curren… Ira McDonald via ipp
- Re: [IPP] Update registration for "printer-curren… Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] Update registration for "printer-curren… Ira McDonald via ipp
- Re: [IPP] Update registration for "printer-curren… Michael Sweet via ipp
- Re: [IPP] Update registration for "printer-curren… Ira McDonald via ipp
- Re: [IPP] Update registration for "printer-curren… Michael Sweet via ipp