Re: [IPP] RFC: Rename JPS3?
"Kennedy, Smith \(Wireless & IPP Standards\) via ipp" <ipp@pwg.org> Mon, 04 November 2019 04:41 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 BD5071200C7 for <ietfarch-ipp-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 20:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 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, MIME_HTML_MOSTLY=0.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 (1024-bit key) reason="fail (message has been altered)" header.d=hp.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 UQapcEf5kigD for <ietfarch-ipp-archive@ietfa.amsl.com>; Sun, 3 Nov 2019 20:41:07 -0800 (PST)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7E4120125 for <ipp-archive2@ietf.org>; Sun, 3 Nov 2019 20:41:07 -0800 (PST)
Received: by mail.pwg.org (Postfix, from userid 1002) id 10AB21C9E; Mon, 4 Nov 2019 04:41:06 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id 2E0BA80F; Mon, 4 Nov 2019 04:40:59 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id D33313A63; Mon, 4 Nov 2019 04:40:57 +0000 (UTC)
Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by mail.pwg.org (Postfix) with ESMTPS id 3725F1C9E for <ipp@pwg.org>; Mon, 4 Nov 2019 04:40:56 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1572842455; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=45AGPNAkBZ+D45zpWNBFIt6oiQtCzGPhfOk3cdhK3SI=; b=Wdkno0VJF3Shn+XIT4BWWa67mnZNygNsjP0Do5hdrULxa8/CXOuLZsACNZrGGETdev7XIs EfCEJ+2gq3M2tD6xUaDQP/0dKTcQ9ERKlCmcRuhn8gyNjkOfLxRFzXqNVZnxiwuXYpy3KS Gsd/35lqr7iHDHbxxTM0WUH3McdG6bQ=
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2058.outbound.protection.outlook.com [104.47.44.58]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-268-TNbOHaqhMwurQf_RW627fQ-1; Sun, 03 Nov 2019 23:40:53 -0500
X-MC-Unique: TNbOHaqhMwurQf_RW627fQ-1
Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0887.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Mon, 4 Nov 2019 04:40:49 +0000
Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::ec8b:9d00:2a51:8d21]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::ec8b:9d00:2a51:8d21%7]) with mapi id 15.20.2408.024; Mon, 4 Nov 2019 04:40:49 +0000
To: "Kennedy, Smith (Wireless & IPP Standards)" <smith.kennedy@hp.com>
Thread-Topic: [IPP] RFC: Rename JPS3?
Thread-Index: AQHVg4GAmYve/TkL80qKnzeEWCEnOadcAvWAgARhHwCAABwxAIAAKdyAgAAX+YCAAAuEAIAAFxOAgADyCICAAEuhAIAYarCA
Date: Mon, 04 Nov 2019 04:40:49 +0000
Message-ID: <AD415C1E-0E41-402E-BD2A-5EFCEA915575@hp.com>
References: <CAN40gSsfmpcogHxwgq31bSeR0V88ZEGoVDWLiHkNBjvJQB7V1Q@mail.gmail.com> <599AA411-FF44-4D0E-8CEA-21A25158D405@msweet.org> <289A83B7-7273-487A-9FF5-A8656F39937A@hp.com>
In-Reply-To: <289A83B7-7273-487A-9FF5-A8656F39937A@hp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=smith.kennedy@hp.com;
x-originating-ip: [75.174.24.180]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d62ba844-096b-45d4-5317-08d760e12a9b
x-ms-traffictypediagnostic: CS1PR8401MB0887:|CS1PR8401MB0887:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <CS1PR8401MB08877380664C5AAD3A9EB1899E7F0@CS1PR8401MB0887.NAMPRD84.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(346002)(376002)(39860400002)(396003)(199900001)(199004)(189003)(6602003)(71200400001)(76176011)(6512007)(6306002)(54896002)(606006)(66616009)(2616005)(476003)(6436002)(66476007)(6246003)(37006003)(26005)(229853002)(53546011)(6506007)(66066001)(54906003)(316002)(102836004)(6486002)(99286004)(5660300002)(36756003)(76116006)(8676002)(8936002)(6862004)(91956017)(66946007)(81156014)(186003)(81166006)(4326008)(33656002)(3846002)(6116002)(478600001)(966005)(99936001)(66556008)(64756008)(66446008)(486006)(2906002)(256004)(14454004)(7736002)(6200100001)(19273905006)(236005)(86362001)(446003)(11346002)(66574012)(25786009)(14444005)(71190400001)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0887; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jUYHPv0WjvhscZw4yQl3a036wb5zEJWfn3G5RVnlA4AbsEm384PaL4cr76++0UmJJjJktnyAt+WMfJuc2v4i7oTjDpl55AWQCk3gM8FQKNXgjwJZAFiD2LTPgbn9Rz7TM4Gkx8N+D90mcdi16eiowCBQGivaPwR1WM6ZTr2VPl6BjpAqidzbaaajfw/sIgZ73w6O42N5aPv5ufHBfuvZ8wxLBhRwQeYYY0KebIQl1Hqs3q0lWBkJesiWOyviVHbN881EWxUaeh/28EaYcPn7nXOXCt4Tl5bIOzoXdXsIGYrrCfa1piKjGIRtB3TAFfgwDzIZTzKDhCYfH88ArM6zNJGOvzHY/iFUij15l4/OXZDiotdI6ifztc17R+B+V08R2PHQosYlXjRLLfE8nLINq1rmaHNOym4Vd6C7T8x+V1tsS4tRJJF6sitp6uBsfnC6
MIME-Version: 1.0
X-OriginatorOrg: hp.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d62ba844-096b-45d4-5317-08d760e12a9b
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 04:40:49.3835 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 6jsih40oxwRFCoEoarTbAR3GNgC9KHld4rCnhrMcZ8cdUghr79DohpZfmOyjKdF29SvdQpYwGIjIlkqVC79DGA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CS1PR8401MB0887
X-Mimecast-Spam-Score: 0
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] RFC: Rename JPS3?
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: "Kennedy, Smith (Wireless & IPP Standards) via ipp" <ipp@pwg.org>
Reply-To: "Kennedy, Smith (Wireless & IPP Standards)" <smith.kennedy@hp.com>
Content-Type: multipart/mixed; boundary="===============2497114323427043348=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
So if it is now named "IPP Driverless Printing Extensions (NODRIVER)", what version number, since it is a renamed / rebranded JPS3? > On Oct 19, 2019, at 9:48 AM, Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote: > > Signed PGP part > +1. Will go with that. > > Smith > > /** > Smith Kennedy > HP Inc. > */ > >> On Oct 19, 2019, at 1:18 AM, Michael Sweet <msweet@msweet.org <mailto:msweet@msweet.org>> wrote: >> >> Ira, >> >> NODRIVER works for me as well. >> >> ____________________ >> Michael Sweet >> >>> On Oct 18, 2019, at 4:52 PM, Ira McDonald <blueroofmusic@gmail.com <mailto:blueroofmusic@gmail.com>> wrote: >>> >>> >>> Hi Mike, >>> >>> See my reply to Uli just now. >>> >>> For simplicity, how about "nodriver"? >>> >>> I never visually parse things like "DRVR" and I doubt others do. >>> >>> Cheers, >>> - Ira >>> >>> Ira McDonald (Musician / Software Architect) >>> 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@gmail.com <mailto:blueroofmusic@gmail.com> >>> PO Box 221 Grand Marais, MI 49839 906-494-2434 >>> >>> >>> >>> On Fri, Oct 18, 2019 at 3:29 PM Michael Sweet <msweet@msweet.org <mailto:msweet@msweet.org>> wrote: >>> Ira, >>> >>> It doesn't roll off the tongue quite as easily as "NODRVR", and I think the "ipp" that comes before it should hint at the focus on printing, but I don't have a strong objection to it. >>> >>> >>> > On Oct 18, 2019, at 2:47 PM, Ira McDonald <blueroofmusic@gmail.com <mailto:blueroofmusic@gmail.com>> wrote: >>> > >>> > Hi Mike, >>> > >>> > I hadn't thought about "DLP". >>> > >>> > How about "nodprt" (No Driver Printing) to preserve the printing aspect. >>> > >>> > Cheers, >>> > - Ira >>> > >>> > Ira McDonald (Musician / Software Architect) >>> > 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@gmail.com <mailto:blueroofmusic@gmail.com> >>> > PO Box 221 Grand Marais, MI 49839 906-494-2434 >>> > >>> > >>> > >>> > On Fri, Oct 18, 2019 at 1:22 PM Michael Sweet <msweet@msweet.org <mailto:msweet@msweet.org>> wrote: >>> > Ira, >>> > >>> > How about "DRVRLS" or "NODRVR" as the acronym? DLPX makes me think of a super version of DLP projectors... :) >>> > >>> > >>> > > On Oct 18, 2019, at 10:52 AM, Ira McDonald <blueroofmusic@gmail.com <mailto:blueroofmusic@gmail.com>> wrote: >>> > > >>> > > Hi, >>> > > >>> > > To avoid the growing collection of three-letter acronyms ending in 'x', >>> > > I suggest 'ippdlpx' (DLPX) to emphasize that it's about *not* needing >>> > > special drivers. >>> > > >>> > > Cheers, >>> > > - Ira >>> > > >>> > > Ira McDonald (Musician / Software Architect) >>> > > 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@gmail.com <mailto:blueroofmusic@gmail.com> >>> > > PO Box 221 Grand Marais, MI 49839 906-494-2434 >>> > > >>> > > >>> > > >>> > > On Fri, Oct 18, 2019 at 9:12 AM Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com <mailto:smith.kennedy@hp.com>> wrote: >>> > > I'm fine with renaming it to be "Driverless Printing Extensions" - will change it in the next draft once the current one has been reviewed. >>> > > >>> > > Smith >>> > > >>> > > /** >>> > > Smith Kennedy >>> > > HP Inc. >>> > > */ >>> > > >>> > >> On Oct 15, 2019, at 8:18 AM, Ira McDonald via ipp <ipp@pwg.org <mailto:ipp@pwg.org>> wrote: >>> > >> >>> > >> Hi Mike, >>> > >> >>> > >> Thank you! >>> > >> >>> > >> +1 >>> > >> >>> > >> I like "IPP Driverless Printing Extensions" best of your suggestions >>> > >> (because "Mobile" is too narrow and "Universal" is too ambiguous). >>> > >> >>> > >> JPS3 is a meaningless name. >>> > >> >>> > >> Cheers, >>> > >> - Ira >>> > >> >>> > >> Ira McDonald (Musician / Software Architect) >>> > >> 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@gmail.com <mailto:blueroofmusic@gmail.com> >>> > >> PO Box 221 Grand Marais, MI 49839 906-494-2434 >>> > >> >>> > >> >>> > >> >>> > >> On Tue, Oct 15, 2019 at 1:53 PM Michael Sweet via ipp <ipp@pwg.org <mailto:ipp@pwg.org>> wrote: >>> > >> All, >>> > >> >>> > >> As I start to prepare the slides for the November F2F, it occurs to me that we have made some useful name changes to historical specifications: >>> > >> >>> > >> - PWG 5100.3 ("IPP Production Printing Attributes - Set 1") renamed to "IPP Production Printing Extensions" >>> > >> - PWG 5100.11 ("IPP Job and Printer Extensions - Set 2") renamed to "IPP Enterprise Printing Extensions" >>> > >> >>> > >> That just leaves PWG 5100.13 ("IPP Job and Printer Extensions - Set 3"), which has a strong focus on "driverless" printing. I suggest we rename JPS3 to something that indicates its focus, for example: >>> > >> >>> > >> "IPP Driverless Printing Extensions" >>> > >> >>> > >> "IPP Driver Equivalence Extensions" >>> > >> >>> > >> "IPP Mobile Printing Extensions" >>> > >> >>> > >> "IPP Universal Printing Extensions" >>> > >> >>> > >> Thoughts? >>> > >> >>> > >> ________________________ >>> > >> Michael Sweet >>> > >> >>> > >> >>> > >> >>> > >> _______________________________________________ >>> > >> ipp mailing list >>> > >> ipp@pwg.org <mailto:ipp@pwg.org> >>> > >> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp> >>> > >> _______________________________________________ >>> > >> ipp mailing list >>> > >> ipp@pwg.org <mailto:ipp@pwg.org> >>> > >> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp> >>> > > >>> > >>> > ________________________ >>> > Michael Sweet >>> > >>> > >>> > >>> >>> ________________________ >>> Michael Sweet >>> >>> >>> > >
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] RFC: Rename JPS3? Michael Sweet via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp
- Re: [IPP] RFC: Rename JPS3? Kennedy, Smith (Wireless & Standards Architect) via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp
- Re: [IPP] RFC: Rename JPS3? Michael Sweet via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp
- Re: [IPP] RFC: Rename JPS3? Michael Sweet via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp
- Re: [IPP] RFC: Rename JPS3? Michael Sweet via ipp
- Re: [IPP] RFC: Rename JPS3? Kennedy, Smith (Wireless & Standards Architect) via ipp
- Re: [IPP] RFC: Rename JPS3? Kennedy, Smith (Wireless & IPP Standards) via ipp
- Re: [IPP] RFC: Rename JPS3? Michael Sweet via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp
- Re: [IPP] RFC: Rename JPS3? Ira McDonald via ipp