From ipp-bounces@pwg.org Fri Mar 1 07:49:53 2019 Return-Path: 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 0D26C127287 for ; Fri, 1 Mar 2019 07:49:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 KTbynx09N0wL for ; Fri, 1 Mar 2019 07:49:48 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 21811124C04 for ; Fri, 1 Mar 2019 07:49:47 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 5E0923F49; Fri, 1 Mar 2019 15:49:46 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 12EB22667; Fri, 1 Mar 2019 15:49:39 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 9C72B24D3; Fri, 1 Mar 2019 15:49:38 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 620B824D3 for ; Fri, 1 Mar 2019 15:49:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551455375; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=F6GbF2Q+WACCaJSfxFB8DJGJH/J68UTPevxZWoupnp8=; b=BJ/WhO+9T3f/YoEVmMvz1CQKXDbr4+STCOZeB0BCu7CkK4D3Uz1vmuWGYILPoulIBKZ3vOL9sGVAZOOvaBrbusplqUUcubG+SywbS2onX+efKObsCqOakZCyfIaiHOOqELXWaeT5f1BlhXGKpyV8+nbz60FNUoa6kH4EBa1/Ch4= Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-co1nam04lp2053.outbound.protection.outlook.com [104.47.45.53]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-305-BcEK2IdmPOCIJ48jcbODcg-1; Fri, 01 Mar 2019 10:49:33 -0500 X-MC-Unique: BcEK2IdmPOCIJ48jcbODcg-1 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM (10.169.49.22) by TU4PR8401MB0592.NAMPRD84.PROD.OUTLOOK.COM (10.169.44.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Fri, 1 Mar 2019 15:49:30 +0000 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908]) by TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908%4]) with mapi id 15.20.1643.022; Fri, 1 Mar 2019 15:49:30 +0000 To: Michael Sweet Thread-Topic: [IPP] WG Last Call: IPP Authentication Methods Thread-Index: AQHUz8NLomFBNpPp9Em5uDLz5UhCS6X27S6A Date: Fri, 1 Mar 2019 15:49:30 +0000 Message-ID: <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> References: <20190228225026.88CE53F41@www.pwg.org> <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> In-Reply-To: <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: dc817c71-0ce5-4fd4-b8f7-08d69e5d7e4d x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:TU4PR8401MB0592; x-ms-traffictypediagnostic: TU4PR8401MB0592: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtUVTRQUjg0MDFNQjA1OTI7MjM6RzhMVVRsZ3ZuTGZTWnVnRHFZMVppdUpF?= =?utf-8?B?QmRsZ3R6dTc2L3JKNUNQd2EvM3RSMmVJSU1hanRJZ08vWnJuaG5FdlNKNnEy?= =?utf-8?B?U2tMQW1xSWlZZktOS0NTTEFPRWxJWUczSTBSc3lTWnhJVFpFa3V6N3l1RDI1?= =?utf-8?B?aUFOc1kxWlBXY3VObHh0a1EvdUV0cjFXVVk3NEM5REtkVTdnYU1SWWt4bU9I?= =?utf-8?B?NmRyVzA2SG0zckZYMklXak5tNlpHZXVNRGlmazRPVlBjMUs5dnJpSHd0M3NG?= =?utf-8?B?eUZvcThNN1MrR0JNWUYwUDUzQXkyL08xVjRoeVFUTDdaNmJKRVBGTk1QZVZU?= =?utf-8?B?VDFMbUsza0hMYjJObkZFTm1hWm5HTUQyZ1M4VFowbGsweVlLTHNxQXRtTUJu?= =?utf-8?B?MHB1RFhFQW1XQVRpL2Nhc1hMNlh3RFBtOVRMSjV0N2g1Z1gvZzhZQ0ZVV0xa?= =?utf-8?B?c0I2b2pVdkl2RWVPdWk5dTBjWGFyZjNSYysxQXVRdFV6TEIxRmJIVk14WFcr?= =?utf-8?B?YXErbUN3aHh6QkI0anJ0RldETVpSRnB3ZFBDUnpGNnN6cm80NTEzZWZFWkgy?= =?utf-8?B?NzRzN1JXa1hiRmY5MGhBNzcvNkpYb0ZMMWtjem5IRkJ1Wm8yYUs2WGxyOVZE?= =?utf-8?B?Zmw5dXczUGlXM3NTendwUlp4U0F0bnN5M0cyTWdITkZydmtibnlRWHRJZDJL?= =?utf-8?B?N04yZ25VMlJzdjhYZnFKOVg5VC8yZEVUMlhRYzBab0dqU0ZVeHpQRW13MzlZ?= =?utf-8?B?K3Y1UmJsV2NvRW1RWHFRZ3VvbFNaVHp4OUkwS3JOcVQwNW8yS3VEMTdBQnVB?= =?utf-8?B?RW93MTVMbklZWjlCS0ZRZk1TbHpLN2dUbnIwSHI3UUVMTUo2WkM0bG5qSktH?= =?utf-8?B?UHM2d0RxeGNicGhKRjhYOHJVVHM3L2hpOEt5ZkRCY1RYRlZmWmtSWERUN1NR?= =?utf-8?B?V2hzeWN4QnVEcUxBeDY4UmpyNDk4bkhWZ005ZXA3VVhnWldIdEQ3b2huV2Zx?= =?utf-8?B?c09rOXVuSmlOMFN3b2RaaUNnMFNXWEg2eDZ5cERJWWpSanAraWRmQ3dnWWV5?= =?utf-8?B?WDRxSjc1Q1VpNlpUdnllUTNHME1zWElQTXAvdmtOaDFZRm9VVGVDNno0RXdY?= =?utf-8?B?VmpSWUtwbjVvaGxLRVFya0JyT3ZpbnFVSVRKWE01Qnk3ZUhpUTg5eG1sT1BX?= =?utf-8?B?VjlmSXYrN0tZNnF5TVRUYnF1SU16WUJCTktmeHJiMDhodUt1Q1EyY1I4T0No?= =?utf-8?B?Z0FhZE0zMW44aG1YVFY2ckJiVTNiR05LOThObXhFV2dBR0xWaTlUMWsxTE1z?= =?utf-8?B?N0lpQzNJTFc3TC96S085UDI5N2k1cDFCTE9XYTFqZ1ViRzdxc1hScXp4ODhC?= =?utf-8?B?eUl2K3NrYkJTNlNkazRJZ25XQWRyMjh3OUt4eEczbm5EelQyOEpYWkxRNTJM?= =?utf-8?B?L1BiNkZJL0l4b3Y2RmM2WTJuZEY0T2pnN0o0ZlQyem1STGFrRWRyWWd1ck13?= =?utf-8?B?Wit6MVBOeTBYRjk1dExBTW9tb2lzNnBmclRHUzc1Tzgxay9MSm0xV0tFNDc4?= =?utf-8?B?SHZ4eWdhRVBqVzdISzBZZnpxSUZKbEtyMi9uS3kyVWt1THpXWEJPS1hYSTMr?= =?utf-8?B?blVQb3hsSkFLcGJuMnVsRUFNZEo1dnFDSmt0WHl6K1pKLzJkRGQvTXYxOWtn?= =?utf-8?B?LzU4enhwZWdGWnkrTzNzUVJwVFRHSUthMjg2VE5uc2ZjZDluNEtoUzdvZU1a?= =?utf-8?B?L09HVUdaQ21odjJKU1ZJSzd5cVJOaW1NbzVkR3A1NVZ3T1JvZ2tMWG1tbGc0?= =?utf-8?B?K1p4QWhrblJqTzhlNWhkaUtLdVFVN1JHazhOak5LbHNEZFhyY0g4U1dhZ0Nx?= =?utf-8?B?L1dMdFdPc2VXL2FKc256N0w5SGRRaTdVWHEvS00rWEs1emM5WHhJVWxwaEE3?= =?utf-8?Q?hDYAhAjY+KliBdt3UOkyYdl6eE8LS3s0=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(346002)(376002)(39860400002)(189003)(199004)(6602003)(51914003)(8676002)(2906002)(606006)(99936001)(14454004)(26005)(186003)(68736007)(8936002)(99286004)(86362001)(102836004)(966005)(478600001)(76176011)(53546011)(6506007)(36756003)(6116002)(6916009)(82746002)(3846002)(106356001)(105586002)(66066001)(33656002)(71200400001)(71190400001)(54906003)(93886005)(316002)(4326008)(25786009)(66574012)(83716004)(97736004)(7736002)(256004)(14444005)(6436002)(229853002)(6486002)(6246003)(53936002)(236005)(6512007)(6306002)(54896002)(5660300002)(11346002)(476003)(2616005)(486006)(446003)(81156014)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB0592; H:TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: akfXIT6X8EUbbCqRVRl1yj7beFyE4gCdOeL/YG63pIl9tXhsm91d1AcaNMmVqAAJAw5dp4Xn2KJo7mM4ClLItnA/cwdETKs8NkZz/+xarypZKWIhCECHhXTx9+VxPSS8u+6//pV9xFN50vvuy+y20jsNkvGZpiUdYlfjrRZHAKFdTogiIUWA43bwSL4PvAEDb3DJg47hOfEjnyPfGAe7icCOTkinIJJ/0O8zxmFghFUuU2JRaS2s80BXe+tDDNhGEWDj89JMT+oRznEr4Q/R91VQ5X9MPDCKeQ/TYpGvww4T5pIrUNRHkN1snNw4RGVoqM9P7cyjVDRlTIDOnuCTFhINhfcV9xROZ5ymos+3z0yFaHdeiTw4L/V6EVocdL7SiGjS3Hrgu4soARPX/EFAemPgQAFBbLxHcknT7fzNf+k= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: dc817c71-0ce5-4fd4-b8f7-08d69e5d7e4d X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2019 15:49:30.6362 (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-Transport-CrossTenantHeadersStamped: TU4PR8401MB0592 Cc: PWG IPP Workgroup Subject: Re: [IPP] WG Last Call: IPP Authentication Methods X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============0205986496904196896==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0205986496904196896== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_AE623C82-E5C8-4EA6-8F01-77B646C28A90"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_AE623C82-E5C8-4EA6-8F01-77B646C28A90 Content-Type: multipart/alternative; boundary="Apple-Mail=_7BDA7DE8-9F98-46FC-925B-3F8250B63DF2" --Apple-Mail=_7BDA7DE8-9F98-46FC-925B-3F8250B63DF2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 How about this: 3.4. Out of Scope The following are considered out of scope for this document: Definition of new HTTP authentication methods Definition of how specific authorization mechanisms are used by an IPP = Printer. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer or an authorization mechanism maps those = roles to authenticated users. > On Feb 28, 2019, at 5:00 PM, Michael Sweet wrote: >=20 > Bill, >=20 > I think you make a good point. >=20 > Smith, >=20 > I think you can make a general statement about authorization, = something along the lines of: >=20 > "Specific authorization mechanisms are outside the scope of this = document. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer maps those roles to authenticated users." >=20 >=20 > > On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp = wrote: > > > > Smith, > > > > Sorry, my confusion continues. Your new Authorization example may be = valid, but it seems odd to me that someone would have an account in a = printer but not have authority to print at all. Conditional authority, = restricting use to certain times or restricting color, or quantity, etc. = would be more realistic, but that is at the IPP level and does not = appear to be addressed in this specification. > > > > The title is Authentication Methods, and although I may have missed = it, I do not think that it does much with authorization (at least not by = the printer), which would occur after successful Authentication. Perhaps = the Authorization use case should be put in the out of scope section? > > Thanks, Bill W. > > > > > > > > From: Rizzo, Christopher via ipp > > Sent: Thursday, February 28, 2019 4:12 PM > > To: Kennedy, Smith (Wireless & Standards Architect); Rick Yardumian > > Cc: PWG IPP WG Reflector > > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods > > > > This update looks good to me. > > > > 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 > > > > From: "Kennedy, Smith (Wireless & Standards Architect)" = > > Date: Thursday, February 28, 2019 at 12:36 PM > > To: Christopher Rizzo , Rick Yardumian = > > Cc: PWG Workgroup > > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods > > > > Thanks for the feedback Chris! I also received this feedback from = Canon's Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this = issue by rewriting 3.3.2 to more meaningfully describe an authorization = failure. > > > > Here's the rewrite. Any objections or suggestions? > > > > Harry is also visiting Andy's office and wants to print from his = laptop. He uses his laptop to discover available printers, and selects = one listed. The printer is configured to limit access to only authorized = users. > > > > The printer challenges the laptop for authentication, and the laptop = presents an authentication dialog to Harry. Harry has an account, and = enters the account's username and password. The printer accepts these = credentials, but that account is not authorized to access that printer. = Harry's laptop shows a notification dialog expressing this to Harry. = Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil. > > > > Smith > > > > > > > > On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher = wrote: > > > > Just curious, but section 3.3 Exceptions of this document has = sections 3.3.1 and 3.3.2 which are pretty much exact duplicates of each = other, exception being Lisa vs. Harry. Was this intentional? > > > > 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 > > > > =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith = (Wireless & Standards Architect)" wrote: > > > > Greetings, > > > > This message begins the IPP workgroup Last Call of the IPP = Authentication Methods best practice draft, available at: > > > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt = > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf = > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf = > > > > Please respond with any feedback or comments by doing a "reply all" = to this message. > > > > This last call will end on January 31, 2019 at 10pm PT. > > > > Cheers, > > Smith > > > > /** > > Smith Kennedy > > HP Inc. > > */ > > > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://www.pwg.org/mailman/listinfo/ipp = > > > > > > > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://www.pwg.org/mailman/listinfo/ipp = >=20 > ________________________ > Michael Sweet >=20 >=20 --Apple-Mail=_7BDA7DE8-9F98-46FC-925B-3F8250B63DF2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 How = about this:

3.4. Out of = Scope

The following are = considered out of scope for this document:
  • Definition of new HTTP authentication methods
  • Definition of how = specific authorization mechanisms are used by an IPP Printer. The = Internet Printing Protocol/1.1 [STD92] defines authorization roles for = end users, operators, and administrators, but does not define how a = Printer or an authorization mechanism maps those roles to authenticated = users.



    • On Feb 28, 2019, at 5:00 PM, Michael Sweet <msweet@msweet.org> = wrote:

    Bill,

    I think you make a good point.

    Smith,

    I think you can make a general statement about authorization, something = along the lines of:

    "Specific authorization mechanisms are outside the scope of this = document. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer maps those roles to authenticated = users."


    > On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp <ipp@pwg.org> wrote:
    >
    > Smith,
    >
    > Sorry, my confusion continues. Your new Authorization example may = be valid, but it seems odd to me that someone would have an account in a = printer but not have authority to print at all. Conditional authority, = restricting use to certain times or restricting color, or quantity, etc. = would be more realistic, but that is at the IPP level and does not = appear to be addressed in this specification.
    >
    > The title is Authentication Methods, and although I may have = missed it, I do not think that it does much with authorization (at least = not by the printer), which would occur after successful Authentication. = Perhaps the Authorization use case should be put in the out of scope = section?
    > Thanks, Bill W.
    >
    >
    >
    > From: Rizzo, Christopher via ipp
    > Sent: Thursday, February 28, 2019 4:12 PM
    > To: Kennedy, Smith (Wireless & Standards Architect); Rick = Yardumian
    > Cc: PWG IPP WG Reflector
    > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods
    >
    > This update looks good to me.
    >
    > 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
    >
    > From: "Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>
    > Date: Thursday, February 28, 2019 at 12:36 PM
    > To: Christopher Rizzo <Christopher.Rizzo@xerox.com>, Rick Yardumian <RYardumian@ciis.canon.com>
    > Cc: PWG Workgroup <ipp@pwg.org>
    > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods
    >
    > Thanks for the feedback Chris! I also received this feedback from = Canon's Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this = issue by rewriting 3.3.2 to more meaningfully describe an authorization = failure.
    >
    > Here's the rewrite. Any objections or suggestions?
    >
    > Harry is also visiting Andy's office and wants to print from his = laptop. He uses his laptop to discover available printers, and selects = one listed. The printer is configured to limit access to only authorized = users.
    >
    > The printer challenges the laptop for authentication, and the = laptop presents an authentication dialog to Harry. Harry has an account, = and enters the account's username and password. The printer accepts = these credentials, but that account is not authorized to access that = printer. Harry's laptop shows a notification dialog expressing this to = Harry. Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil.
    >
    > Smith
    >
    >
    >
    > On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher <Christopher.Rizzo@xerox.com> wrote:
    >
    > Just curious, but section 3.3 Exceptions of this document has = sections 3.3.1 and 3.3.2 which are pretty much exact duplicates of each = other, exception being Lisa vs. Harry. Was this intentional?
    >
    > 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
    >
    > =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith = (Wireless & Standards Architect)" <ipp-bounces@pwg.org = on behalf of smith.kennedy@hp.com> wrote:
    >
    > Greetings,
    >
    > This message begins the IPP workgroup Last Call of the IPP = Authentication Methods best practice draft, available at:
    >
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt<= br class=3D""> > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf<= br class=3D""> > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf<= /a>
    >
    > Please respond with any feedback or comments by doing a "reply all" = to this message.
    >
    > This last call will end on January 31, 2019 at 10pm PT.
    >
    > Cheers,
    > Smith
    >
    > /**
    > Smith Kennedy
    > HP Inc.
    > */
    >
    > _______________________________________________
    > ipp mailing list
    >     ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp
    >
    >
    >
    > _______________________________________________
    > ipp mailing list
    > ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp

    ________________________
    Michael Sweet



    = --Apple-Mail=_7BDA7DE8-9F98-46FC-925B-3F8250B63DF2-- --Apple-Mail=_AE623C82-E5C8-4EA6-8F01-77B646C28A90 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx5VIkACgkQqskbKLDW 1N3VnQ/+IvrEeczqEptVWkny0m6M8o6QXsdMzyW93hb94LJMEXDskt0IXp2zu9kP VsXsSLo+JppQBQZE1GYme8mwz9h0kL5oOa743B93/qxPeryd2addlxo8TV4sF4th wSO65m1fyIO961azJ9TKKxPL3YKV9Yk71Jzth+OSMTYthk7Dbrx66T8JJC4y1xk7 NldLvB9+tF6sse76uVlqTEzWAedf4av+uI/4lC8ecNj/LZEQAFDAVpekjz5vF1Rq Nseib3g2SoyogJGH2coZvYDxyvr088TCy7sgbjzd8iqSQi1NPl1fG7lBYcl5+s6y 3Ar4YNxtCqCCcEdlsG3npyHlz+K3SnwOH91RmlRaKbMyHdafQS+yHcqOB2+9tG2L bvAb7CcdWNExcI5kK80UAiBY67oOYisXKEbJnmLd87FglxF0K+ZWpdx2AH0Zukfo lMLBnZyZNqfW6HKAJMUpDmkaVrcTzXzZGJZ5LMQOtRkPuD6NPscSt9aZg4HncR8J 4nbnR5T2wlBhBZ10S6amw9YKh1a9rW7c43OAEteuOxW6PcT8KgMpbor1vnLQbAFU OGhgFz/2fSpVe4A2c0CKtzfSXC8DbZ2tPvS5Iwx3k+P8OQsFZcOwRxo4H41zeOzF 2ciQkFyOqtlBIakE//qw0pGhaVDWcDhlLP5zERWoAIPCsnEvLDk= =lS2o -----END PGP SIGNATURE----- --Apple-Mail=_AE623C82-E5C8-4EA6-8F01-77B646C28A90-- --===============0205986496904196896== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0205986496904196896==-- From ipp-bounces@pwg.org Fri Mar 1 11:22:09 2019 Return-Path: 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 653F2130ED9 for ; Fri, 1 Mar 2019 11:22:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.282 X-Spam-Level: X-Spam-Status: No, score=-0.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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=comcast.net 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 Y0wCYIHOoWMD for ; Fri, 1 Mar 2019 11:22:05 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id EFE79130EBE for ; Fri, 1 Mar 2019 11:22:04 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 232A23F49; Fri, 1 Mar 2019 19:22:04 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 7BAB32667; Fri, 1 Mar 2019 19:21:54 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 0707B3F41; Fri, 1 Mar 2019 19:21:53 +0000 (UTC) Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) by www.pwg.org (Postfix) with ESMTPS id 84C0124D3 for ; Fri, 1 Mar 2019 19:21:50 +0000 (UTC) Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id zmQ1gubj1pFrSznjBgDXDY; Fri, 01 Mar 2019 19:21:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1551468109; bh=v92lWKZ/elPZqmstOm+K/cVgMUlx4A5ftI4mSoTqH5g=; h=Received:Received:MIME-Version:To:From:Subject:Date:Content-Type; b=S3V2My20AD+JXyNEbiRDF4TqKunSVpfXxv5T2kSAmu3r/4WU17DWb2Yr7pgOUW+4b 9KyhW4NJ+rd2/PKr1S/5Xd+3Bqnwe44H62ea+YBTa15XFb0SkCInfQCscu3COOQ/nZ EIz7AqrQTvSk3x41DOpBj0YY+sVYGlzcr+B+Ns8S8NOHQWLu3gkuW0mt9opLOy0KFP 7mZ7h77r+BYTq15hmWKVeyKNrEx3+YJPQSpSA81NmYYtG2Y4Y+Pe7csx1DH720HInl 906sDqGsbwGGMsj2kuEZoVsMcKeHvjahxMiwpAY1JiiFJ73pAoyByTWCZ5ML8IbUKJ IKRzTfMeSOYTQ== Received: from [IPv6:::ffff:192.168.1.9] ([73.61.211.249]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id znj9g4oA4l0TEznjAguHUq; Fri, 01 Mar 2019 19:21:48 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedutddrvdehgdduvdegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegopfhokfffucdluddtmdenucfjughrpeggvffhufffkgfrjghftgesrgdttdertddtjeenucfhrhhomhepoeifrghmfigrghhnvghrsegtohhmtggrshhtrdhnvghtqeenucffohhmrghinhepmhhimhgvtggrshhtrdgtohhmpdhpfihgrdhorhhgnecukfhppeejfedriedurddvuddurddvgeelnecurfgrrhgrmhephhgvlhhopeglkffrvheimeemmehffhhffhemudelvddrudeikedruddrlegnpdhinhgvthepjeefrdeiuddrvdduuddrvdegledpmhgrihhlfhhrohhmpeifrghmfigrghhnvghrsegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepshhmihhthhdrkhgvnhhnvgguhieshhhprdgtohhmpdhrtghpthhtohepmhhsfigvvghtsehmshifvggvthdrohhrghdprhgtphhtthhopegthhhrihhsthhophhhvghrrdhrihiiiihoseigvghrohigrdgtohhmpdhrtghpthhtoheprhihrghrughumhhirghnsegtihhishdrtggrnhhonhdrtghomhdprhgtphhtthhopehiphhpsehpfihgrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-Xfinity-VMeta: sc=-90;st=legit MIME-Version: 1.0 To: "Kennedy, Smith (Wireless & Standards Architect)" , Michael Sweet Date: Fri, 1 Mar 2019 14:21:48 -0500 Importance: normal X-Priority: 3 Thread-Topic: [IPP] WG Last Call: IPP Authentication Methods In-Reply-To: <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> References: <20190228225026.88CE53F41@www.pwg.org> <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> Message-Id: <20190301192153.0707B3F41@www.pwg.org> Cc: PWG IPP Workgroup Subject: Re: [IPP] WG Last Call: IPP Authentication Methods X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: wamwagner--- via ipp Reply-To: wamwagner@comcast.net Content-Type: multipart/mixed; boundary="===============2622460338163877962==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2622460338163877962== Content-Type: multipart/alternative; boundary="_491537AD-3230-4897-BF6F-ADBD4681A3D1_" --_491537AD-3230-4897-BF6F-ADBD4681A3D1_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Both Michael and Smith make good points, and I think it is mainly a questio= n of how far Smith wants to extend the scope of the document. From his earl= ier message, it appears that he has=C2=A0 added more information on Authori= zation. However, his comment that the purpose of Authentication=C2=A0 in a = printer is primarily to support Authorization features is quite to the poin= t. Indeed,=C2=A0 the text might point out that the extended authentication = mechanisms discussed relate to obtaining the value of the IPP attribute job= -originating-user-name, which is used by the printer for authorization chec= ks. That is,=20 =C2=A0=C2=A0 The Printer sets this attribute to the most =C2=A0=C2=A0 authenticated printable name that it can obtain from the =C2=A0=C2=A0 authentication service over which the IPP operation was receiv= ed. =C2=A0=C2=A0 Only if such a name is not available does the Printer use the = value =C2=A0=C2=A0 supplied by the Client in the "requesting-user-name" operation =C2=A0=C2=A0 attribute of the Job Creation request. Of course, from Michael=E2=80=99s point, discussion of printer-implemented = authorization in this document is probably limited to restating what is i= n STD92: using the most authenticated printable name for authorization and= IPP responses to authentication failures.=20 Thanks,=20 Bill Wagner From: Kennedy, Smith (Wireless & Standards Architect) Sent: Friday, March 1, 2019 10:49 AM To: Michael Sweet Cc: William A Wagner; Rizzo, Christopher; Rick Yardumian; PWG IPP Workgroup Subject: Re: [IPP] WG Last Call: IPP Authentication Methods How about this: 3.4. Out of Scope The following are considered out of scope for this document: 1. Definition of new HTTP authentication methods 2. Definition of how specific authorization mechanisms are used by an IPP P= rinter. The Internet Printing Protocol/1.1 [STD92] defines authorization ro= les for end users, operators, and administrators, but does not define how a= Printer or an authorization mechanism maps those roles to authenticated us= ers. On Feb 28, 2019, at 5:00 PM, Michael Sweet wrote: Bill, I think you make a good point. Smith, I think you can make a general statement about authorization, something alo= ng the lines of: "Specific authorization mechanisms are outside the scope of this document. = The Internet Printing Protocol/1.1 [STD92] defines authorization roles for = end users, operators, and administrators, but does not define how a Printer= maps those roles to authenticated users." > On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp wrote: >=20 > Smith, >=20 > Sorry, my confusion continues. Your new Authorization example may be vali= d, but it seems odd to me that someone would have an account in a printer b= ut not have authority to print at all. Conditional authority, restricting u= se to certain times or restricting color, or quantity, etc. would be more r= ealistic, but that is at the IPP level and does not appear to be addressed = in this specification.=20 >=20 > The title is Authentication Methods, and although I may have missed it, I= do not think that it does much with authorization (at least not by the pri= nter), which would occur after successful Authentication. Perhaps the Autho= rization use case should be put in the out of scope section? > Thanks, Bill W. >=20 >=20 >=20 > From: Rizzo, Christopher via ipp > Sent: Thursday, February 28, 2019 4:12 PM > To: Kennedy, Smith (Wireless & Standards Architect); Rick Yardumian > Cc: PWG IPP WG Reflector > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >=20 > This update looks good to me. >=20 > Thanks, > Chris >=20 > 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 >=20 > "The realization came over me with full force that a good part of the rem= ainder of my life was going to be spent in finding errors in my own program= s." > -Maurice Wilkes, Memoirs of a Computer Pioneer >=20 > From: "Kennedy, Smith (Wireless & Standards Architect)" > Date: Thursday, February 28, 2019 at 12:36 PM > To: Christopher Rizzo , Rick Yardumian > Cc: PWG Workgroup > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >=20 > Thanks for the feedback Chris! I also received this feedback from Canon's= Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this issue by rewr= iting 3.3.2 to more meaningfully describe an authorization failure.=20 >=20 > Here's the rewrite. Any objections or suggestions? >=20 > Harry is also visiting Andy's office and wants to print from his laptop. = He uses his laptop to discover available printers, and selects one listed. = The printer is configured to limit access to only authorized users.=20 >=20 > The printer challenges the laptop for authentication, and the laptop pres= ents an authentication dialog to Harry. Harry has an account, and enters th= e account's username and password. The printer accepts these credentials, b= ut that account is not authorized to access that printer. Harry's laptop sh= ows a notification dialog expressing this to Harry. Harry clicks =E2=80=9CO= K=E2=80=9D and looks for a pencil. >=20 > Smith >=20 >=20 >=20 > On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher wrote: >=20 > Just curious, but section 3.3 Exceptions of this document has sections 3.= 3.1 and 3.3.2 which are pretty much exact duplicates of each other, excepti= on being Lisa vs. Harry. Was this intentional? >=20 > Thanks, > Chris >=20 >=20 > Christopher Rizzo > Xerox Corporation >=20 > GDG/Discovery/Advance Technology >=20 > 26600 SW Parkway Ave. >=20 > Wilsonville, OR 97070-9251 >=20 > Phone: (585) 314-6936 >=20 > Email: Christopher.Rizzo@xerox.com >=20 > "The realization came over me with full force that a good part of the rem= ainder of my life was going to be spent in finding errors in my own program= s." > -Maurice Wilkes, Memoirs of a Computer Pioneer >=20 > =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wireless = & Standards Architect)" wrote: >=20 > Greetings, >=20 > This message begins the IPP workgroup Last Call of the IPP Authentication= Methods best practice draft, available at: >=20 > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf >=20 > Please respond with any feedback or comments by doing a "reply all" to th= is message. >=20 > This last call will end on January 31, 2019 at 10pm PT. >=20 > Cheers, > Smith >=20 > /** > Smith Kennedy > HP Inc. > */ >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp >=20 >=20 >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp ________________________ Michael Sweet --_491537AD-3230-4897-BF6F-ADBD4681A3D1_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

    Both Michael and Smith make good = points, and I think it is mainly a question of how far Smith wants to exten= d the scope of the document. From his earlier message, it appears that he h= as  added more information on Authorization. However, his comment that= the purpose of Authentication  in a printer is primarily to support A= uthorization features is quite to the point. Indeed,  the text might p= oint out that the extended authentication mechanisms discussed relate to ob= taining the value of the IPP attribute job-originating-user-name, which is = used by the printer for authorization checks. That is,

       The Printer sets this attribute to t= he most

       authenticated printable name that it can obtain= from the

       authentication service over which the IPP ope= ration was received.

       Only if such a name is not availab= le does the Printer use the value

       supplied by the Clien= t in the "requesting-user-name" operation

       att= ribute of the Job Creation request.

     

    Of course, from Michael=E2=80= =99s point, discussion of printer-implemented authorization=C2=A0 in this d= ocument is probably limited to =C2=A0restating what is in STD92: using =C2= =A0the most authenticated printable na= me for authorization and IPP responses to authentication failures. <= /p>

     

    Thanks, <= o:p>

    Bill Wagner

     

     

    From: Kennedy, S= mith (Wireless & Standards Architect)
    Sent: Friday, March= 1, 2019 10:49 AM
    To: Michae= l Sweet
    Cc: William = A Wagner; Rizzo, Christo= pher; Rick Yardumian; = PWG IPP Workgroup
    Subject: Re:= [IPP] WG Last Call: IPP Authentication Methods

     

    How about this:

    =

     

    3.4. Out of Scope

     

    The following are considered out of scope= for this document:

      =
    1. Definition= of new HTTP authentication methods
    2. Definition of how specific = authorization mechanisms are used by an IPP Printer. The Internet Printing = Protocol/1.1 [STD92] defines authorization roles for end users, operators, = and administrators, but does not define how a Printer or an authorization m= echanism maps those roles to authenticated users.

     

    <= div>

     


    On Feb 28, 2019, at 5:00 PM, Michael Sweet &l= t;msweet@msweet.org> wrote:

     

    Bill,

    I think you make= a good point.

    Smith,

    I think you can make a general statemen= t about authorization, something along the lines of:

    "Specific = authorization mechanisms are outside the scope of this document. The Intern= et Printing Protocol/1.1 [STD92] defines authorization roles for end users,= operators, and administrators, but does not define how a Printer maps thos= e roles to authenticated users."


    > On Feb 28, 2019, at 5= :50 PM, wamwagner--- via ipp <ipp@pwg.org= > wrote:
    >
    > Smith,
    >
    > Sorry, my confusio= n continues. Your new Authorization example may be valid, but it seems odd = to me that someone would have an account in a printer but not have authorit= y to print at all. Conditional authority, restricting use to certain times = or restricting color, or quantity, etc. would be more realistic, but that i= s at the IPP level and does not appear to be addressed in this specificatio= n.
    >
    > The title is Authentication Methods, and although I ma= y have missed it, I do not think that it does much with authorization (at l= east not by the printer), which would occur after successful Authentication= . Perhaps the Authorization use case should be put in the out of scope sect= ion?
    > Thanks, Bill W.
    >
    >
    >
    > From: Rizzo= , Christopher via ipp
    > Sent: Thursday, February 28, 2019 4:12 PM
    = > To: Kennedy, Smith (Wireless & Standards Architect); Rick Yardumia= n
    > Cc: PWG IPP WG Reflector
    > Subject: Re: [IPP] WG Last Call:= IPP Authentication Methods
    >
    > This update looks good to me.<= br>>
    > Thanks,
    > Chris
    >
    > Christopher Rizzo> Xerox Corporation
    > GDG/Discovery/Advance Technology
    > 2= 6600 SW Parkway Ave.
    > Wilsonville, OR 97070-9251
    > Phone: (585= ) 314-6936
    > Email: Ch= ristopher.Rizzo@xerox.com
    >
    > "The realization came o= ver me with full force that a good part of the remainder of my life was goi= ng to be spent in finding errors in my own programs."
    > -Maurice= Wilkes, Memoirs of a Computer Pioneer
    >
    > From: "Kennedy= , Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>
    > Date: Thursday, Fe= bruary 28, 2019 at 12:36 PM
    > To: Christopher Rizzo <Christopher.Rizzo@xerox.com>, Rick= Yardumian <RYardumian@ciis= .canon.com>
    > Cc: PWG Workgroup <ipp@pwg.org>
    > Subject: Re: [IPP] WG Last Call: IPP Authe= ntication Methods
    >
    > Thanks for the feedback Chris! I also re= ceived this feedback from Canon's Rick Yardumian (CC'ed). In my LCRC draft,= I've resolved this issue by rewriting 3.3.2 to more meaningfully describe = an authorization failure.
    >
    > Here's the rewrite. Any objecti= ons or suggestions?
    >
    > Harry is also visiting Andy's office a= nd wants to print from his laptop. He uses his laptop to discover available= printers, and selects one listed. The printer is configured to limit acces= s to only authorized users.
    >
    > The printer challenges the la= ptop for authentication, and the laptop presents an authentication dialog t= o Harry. Harry has an account, and enters the account's username and passwo= rd. The printer accepts these credentials, but that account is not authoriz= ed to access that printer. Harry's laptop shows a notification dialog expre= ssing this to Harry. Harry clicks =E2=80=9COK=E2=80=9D and looks for a penc= il.
    >
    > Smith
    >
    >
    >
    > On Feb 28, 20= 19, at 12:33 PM, Rizzo, Christopher <Christopher.Rizzo@xerox.com> wrote:
    >
    > Jus= t curious, but section 3.3 Exceptions of this document has sections 3.3.1 a= nd 3.3.2 which are pretty much exact duplicates of each other, exception be= ing Lisa vs. Harry. Was this intentional?
    >
    > Thanks,
    > = Chris
    >
    >
    > Christopher Rizzo
    > Xerox Corporation=
    >
    > GDG/Discovery/Advance Technology
    >
    > 26600 S= W Parkway Ave.
    >
    > Wilsonville, OR 97070-9251
    >
    >= Phone: (585) 314-6936
    >
    > Email: Christopher.Rizzo@xerox.com
    >
    > "T= he realization came over me with full force that a good part of the remaind= er of my life was going to be spent in finding errors in my own programs.&q= uot;
    > -Maurice Wilkes, Memoirs of a Computer Pioneer
    >
    >= ; =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wire= less & Standards Architect)" <ipp-bounces@pwg.org on behalf of smith.kennedy@hp.com> wrote:
    >
    > Greetings,
    = >
    > This message begins the IPP workgroup Last Call of the IPP Au= thentication Methods best practice draft, available at:
    >
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt=
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190= 117.pdf
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ip= pauth-20190117-rev.pdf
    >
    > Please respond with any feedbac= k or comments by doing a "reply all" to this message.
    > > This last call will end on January 31, 2019 at 10pm PT.
    >
    &= gt; Cheers,
    > Smith
    >
    > /**
    > Smith Kennedy
    >= ; HP Inc.
    > */
    >
    > _____________________________________= __________
    > ipp mailing list
    > = ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp=
    >
    >
    >
    > ___________________________________= ____________
    > ipp mailing list
    > ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/i= pp

    ________________________
    Michael Sweet

    <= /p>

     

     

    = --_491537AD-3230-4897-BF6F-ADBD4681A3D1_-- --===============2622460338163877962== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2622460338163877962==-- From ipp-bounces@pwg.org Fri Mar 1 12:05:43 2019 Return-Path: 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 15573130EB4 for ; Fri, 1 Mar 2019 12:05:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.282 X-Spam-Level: X-Spam-Status: No, score=-0.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 6ARAJjaZ9EWI for ; Fri, 1 Mar 2019 12:05:40 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id E71741200ED for ; Fri, 1 Mar 2019 12:05:39 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 460C83F51; Fri, 1 Mar 2019 20:05:39 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id A50E52667; Fri, 1 Mar 2019 20:05:27 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 5CF8124D3; Fri, 1 Mar 2019 20:05:26 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id BB33C24D3 for ; Fri, 1 Mar 2019 20:05:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551470722; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AGAGlxe5sa4wWKjZ7sKz1GznwEND/QhJNLrJZyQsojY=; b=LGMt/kkkFTUxfsHOAmNT89YDvL5/SI0IGTXWax9yZYuzT/C6GvOnQzqf4xowVJrV4nIUUDemazaSUVmYYRNu9XzulyBLCTbO9WLuBUGp2UBJJA4qLngTWxc+Jw0Aw7mkHaWPiHUQpCnNTk5k1kJ3Qx8PObk6RHou8Bpm+MXh0cI= Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02lp2057.outbound.protection.outlook.com [104.47.37.57]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-29-KPmSLEbFPBm6bUGNl4aZkQ-1; Fri, 01 Mar 2019 15:05:18 -0500 X-MC-Unique: KPmSLEbFPBm6bUGNl4aZkQ-1 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM (10.169.49.22) by TU4PR8401MB1088.NAMPRD84.PROD.OUTLOOK.COM (10.169.48.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.21; Fri, 1 Mar 2019 20:05:16 +0000 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908]) by TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908%4]) with mapi id 15.20.1643.022; Fri, 1 Mar 2019 20:05:16 +0000 To: William A Wagner Thread-Topic: [IPP] WG Last Call: IPP Authentication Methods Thread-Index: AQHUz8NLomFBNpPp9Em5uDLz5UhCS6X27S6AgAA7UwCAAAwjgA== Date: Fri, 1 Mar 2019 20:05:16 +0000 Message-ID: References: <20190228225026.88CE53F41@www.pwg.org> <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> <91959.119030114214901401@us-mta-207.us.mimecast.lan> In-Reply-To: <91959.119030114214901401@us-mta-207.us.mimecast.lan> 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 69ce2910-eab7-4e56-3c8f-08d69e81392e x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:TU4PR8401MB1088; x-ms-traffictypediagnostic: TU4PR8401MB1088: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtUVTRQUjg0MDFNQjEwODg7MjM6cENEQmNzSzJucm0wbTB0M2ZmOS9IZkps?= =?utf-8?B?aHo1TmpPWU5jU3F3YVhTYTZ5VWIwYWxMcGZjcFZkS0tCNlg4dXhoRXVUbFk1?= =?utf-8?B?SEpiU1BHeHJHN2ZCNXJSdnVjUkNBT0FWNEpCbVZNbDhzdDBSYWNxbUNNYXRw?= =?utf-8?B?U2dBRmlwKy9XbXdUaklxazZ0S0FaTmJpZTV6TUZjK2hkRUZIVjhSdnY4WHQx?= =?utf-8?B?UDB4cU53Vm9iNzRnK3czd3Q5QmlOMGJTZUVTYStRb1lXb1o1NkZkZW1jeUNo?= =?utf-8?B?NE1vS1VSclZhRXZOVDcyMWo4bGwxUXZUNk5jWHYzcmxhY1luODVhSUlKRzB6?= =?utf-8?B?ejdBeWdBVUY0L3czaVBWdXc3Q2JzWHpYSjJ3Y2VDQ2tIVXBRcVRQZ25EYThN?= =?utf-8?B?eVNUYzdGcHhVR2hXb2xXOTlpdHVkYXZLWXJYRHFFVzE5NXhnZVN6cUVVVzRD?= =?utf-8?B?RDhmN0Rid29UQjJSc3Qvak5Fc0hyOWdob043MHlvS1FVUFdwRE00VUtveDY0?= =?utf-8?B?Q2dXdVBydnBUSVNzUlV3ZXRYZUZPeXRXWDFRRnpJZE9SOWhEL1VQS2liZWI2?= =?utf-8?B?cjN2cHo2ZXM0Q3JOVDg4VFN4eGZKY1pLVmlTczdyc1lPdzY1Q3VZbnNXQ2JJ?= =?utf-8?B?ZnVKOVhHOFBYV1pCT0U0TXRLbkNTdFJTdVNQRUpjR1Bud2ZaZ091aXJHUGUw?= =?utf-8?B?NFVTM1YzVzh4VDUvajRSWTk0cXVLYjdoSXBja0w1aTZOUGQxY2FreGZ1bkxj?= =?utf-8?B?VmUvMU53dWlkZXA0ZVdyOFNmU056Ynp6VFBpQ1JGRTZNZzRkMEJZQjNWd3cy?= =?utf-8?B?L0JxeXA3VVdnczB3aUpTV3VMOFhTVVpVWGtEQm1tdFN0OWgrTDY3OEdRL1B5?= =?utf-8?B?Ty82YXN3a21RdHp2MkF4eWRJdHZjbWQ5THhXQlRBSngveE9FeXFhOHFmYmFB?= =?utf-8?B?cE9ZMU9hUEo2UzBCcnZrQXpqRzlRQmlPNGd6NXJKeFFqMWNoNW91amMzRCtD?= =?utf-8?B?MW1LMG1hUFVZekxRNnJpN1VKMFFWVVNDWWxxMzJHdWJWQ1Y2T0NTWm01Rnd6?= =?utf-8?B?dlZ3WjhwSm4yMUdQcjBYRVlseTdoc1NWQm1oYW51UU4xNlNXNExFRTkvMWVW?= =?utf-8?B?aVl6ZzJZaWNaTTdRbGV6clBBdjhxQmJWeTQvRk5hTEUvNlpzenhKUEpUSURx?= =?utf-8?B?TEVxejg2Y0xvU1U2ZGY5bkVoVjlEK1o5WFhZczNXV29TNk9qdkRrWVc0Vnc5?= =?utf-8?B?N1NJQUIxMDFhVXo3dU9RaHlVb0J1aHVMRk1UYWtoaGlta0UvcVFrWXM0cWF0?= =?utf-8?B?RHBJbWowTy85VXpHRXNXOGJhR05BNXZMbzNIVG5iT1p5K2ord2xJQTc3VDF4?= =?utf-8?B?dm1qeFJESFFRL1loOWFuTjFveW5KbmVZRjNwTG95b3dacEVydjJta0VFWGNS?= =?utf-8?B?NmFSOXBLciszRGR2aFM1REZ1ZVVSWlZhV0taMkp1cU1KZkFlaTZQZlplb29I?= =?utf-8?B?SG1NUk9YeTcybDZIcm81QXBJU3BCamk1aWpYT3JSMEpzT0Q0dHZGZnJOU3Vw?= =?utf-8?B?ckNIWHJJbDlxMTZEVWdGMW4vVW5SbEJOU3JlaWdaMm11bkM1WGdBaVpJM3hS?= =?utf-8?B?SVFvbFI3MUQ2VlhJQ09jSzM4cFdzQ2Fwb09nQmF0dUJIV3Fsd1pCaSttZXh1?= =?utf-8?B?RzdFRDRPUkh2bmtSam5jeE9ML0VpSzNQR1pDbXlEMkE1MFYweFdzYjhkbEFO?= =?utf-8?B?T0hGV01WVnA2Q1RjK2UxNGI5eXRlUWdQeUdURnQzVmVlT0xjQThhZ3o2ZVh3?= =?utf-8?B?TXZwQk5nRGs1VENuMnpkam94ejQ5b29Sb3o1czN2ZFhuWUpScGNxdTR0c3kx?= =?utf-8?B?ckhXMFVpbXA4SE5qZU5DYmkxb1pVRUpFRHJ0SjdxR2ZFYXk3UnFGVDB3V2Rp?= =?utf-8?Q?L8hvvosNIuSxjqRbUmP8d98WNNxS/QXU=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(39860400002)(366004)(376002)(346002)(6602003)(51914003)(189003)(199004)(316002)(2906002)(7736002)(82746002)(4326008)(102836004)(478600001)(71190400001)(446003)(71200400001)(8676002)(11346002)(86362001)(256004)(99286004)(14444005)(8936002)(83716004)(68736007)(25786009)(93886005)(229853002)(54906003)(66066001)(2616005)(66574012)(6246003)(5660300002)(606006)(97736004)(476003)(26005)(236005)(6512007)(54896002)(14454004)(6306002)(81166006)(6916009)(6116002)(6506007)(186003)(486006)(33656002)(36756003)(966005)(53936002)(3846002)(53546011)(81156014)(6436002)(106356001)(6486002)(76176011)(99936001)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB1088; H:TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: q7irGfJRyGfr0pSlEo3RDHEdcNJFu0KP0V6kHKzAeWQytjtcMdxggiOx+1IuhfMPhtoUmphfQlNUIB6hPDws8au1rnjlW4aWGnI6LSBYYU6qpcNIKlewkodrk5uKccVlDfVh2xKx8T3N00QL9Pjg69a3lDeMcPCc+LRuFfzOlTcHf/xzq/+K04e/qRpmA4P9W7TWxwNSFof4JJ0KSgROExTu1CzjrRljO4Nj07jjTGVSmz+f1fjU5O0B49QKm4gOsfrOHbFXa9YxyG5L128fav90wz+BrsLoIgPNtxXgGkqm+AD4YN+KjP+DgsQ4xfr+lxXu77qy59jHpoMlhfow3yTKDzVuCbfj0ULvaNxhuzf4+f1eC0yoOf3iXII76Z5ErKnsRT7RWb+5AwpA3ySUa/yl9GePyTzCKAaJXo8kRhE= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 69ce2910-eab7-4e56-3c8f-08d69e81392e X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2019 20:05:16.6314 (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-Transport-CrossTenantHeadersStamped: TU4PR8401MB1088 Cc: PWG IPP Workgroup , Michael Sweet Subject: Re: [IPP] WG Last Call: IPP Authentication Methods X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============1768828976006340786==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============1768828976006340786== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_3D09FA5F-891C-4949-840A-593162238488"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_3D09FA5F-891C-4949-840A-593162238488 Content-Type: multipart/alternative; boundary="Apple-Mail=_D63F6A59-811D-4356-B8E2-5974D50F9BA4" --Apple-Mail=_D63F6A59-811D-4356-B8E2-5974D50F9BA4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Thanks for mentioning this detail, Bill! I am fine with adding that the = purpose of authentication is to acquire a token to be used for access = authorization. But after re-reading the definition of = "job-originating-user-name" from RFC 8011, I'm not sure I agree that the = value of the "job-originating-user-name" attribute itself is necessarily = the token to be used. Notice the second paragraph, which talks about the = Printer maintaining an "internal originating user ID of some form", = which is "used for authorization checks" but isn't publicly visible: 5.3.6. job-originating-user-name (name(MAX)) This REQUIRED attribute contains the name of the End User that submitted the Print Job. The Printer sets this attribute to the most authenticated printable name that it can obtain from the authentication service over which the IPP operation was received. Only if such a name is not available does the Printer use the value supplied by the Client in the "requesting-user-name" operation attribute of the Job Creation request (see Sections 5.4.2, 5.4.3, and 9). Note: The Printer needs to keep an internal originating user ID of some form, typically as a credential of a principal, with the Job. Since such an internal attribute is implementation dependent and not of interest to Clients, it is not specified as a Job attribute. This originating user ID is used for authorization checks (if any) on all subsequent operations. So the value of "job-originating-user-name" could be some printable name = string, but that value isn't itself necessarily the token that would be = used by the Printer's "backend" implementation to engage with a = particular authentication service. And that token has no IPP Job Status = attribute and is considered by IPP to be an internal implementation = detail. Smith > On Mar 1, 2019, at 12:21 PM, wamwagner@comcast.net wrote: >=20 > Both Michael and Smith make good points, and I think it is mainly a = question of how far Smith wants to extend the scope of the document. = =46rom his earlier message, it appears that he has added more = information on Authorization. However, his comment that the purpose of = Authentication in a printer is primarily to support Authorization = features is quite to the point. Indeed, the text might point out that = the extended authentication mechanisms discussed relate to obtaining the = value of the IPP attribute job-originating-user-name, which is used by = the printer for authorization checks. That is, > The Printer sets this attribute to the most > authenticated printable name that it can obtain from the > authentication service over which the IPP operation was received. > Only if such a name is not available does the Printer use the value > supplied by the Client in the "requesting-user-name" operation > attribute of the Job Creation request. >=20 > Of course, from Michael=E2=80=99s point, discussion of = printer-implemented authorization in this document is probably limited = to restating what is in STD92: using the most authenticated printable = name for authorization and IPP responses to authentication failures. >=20 > Thanks, > Bill Wagner >=20 >=20 > From: Kennedy, Smith (Wireless & Standards Architect) = > Sent: Friday, March 1, 2019 10:49 AM > To: Michael Sweet > Cc: William A Wagner ; Rizzo, = Christopher ; Rick Yardumian = ; PWG IPP Workgroup = > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >=20 > How about this: >=20 > 3.4. Out of Scope >=20 > The following are considered out of scope for this document: > Definition of new HTTP authentication methods > Definition of how specific authorization mechanisms are used by an IPP = Printer. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer or an authorization mechanism maps those = roles to authenticated users. >=20 >=20 >=20 >=20 > On Feb 28, 2019, at 5:00 PM, Michael Sweet > wrote: >=20 > Bill, >=20 > I think you make a good point. >=20 > Smith, >=20 > I think you can make a general statement about authorization, = something along the lines of: >=20 > "Specific authorization mechanisms are outside the scope of this = document. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer maps those roles to authenticated users." >=20 >=20 > > On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp > wrote: > > > > Smith, > > > > Sorry, my confusion continues. Your new Authorization example may be = valid, but it seems odd to me that someone would have an account in a = printer but not have authority to print at all. Conditional authority, = restricting use to certain times or restricting color, or quantity, etc. = would be more realistic, but that is at the IPP level and does not = appear to be addressed in this specification. > > > > The title is Authentication Methods, and although I may have missed = it, I do not think that it does much with authorization (at least not by = the printer), which would occur after successful Authentication. Perhaps = the Authorization use case should be put in the out of scope section? > > Thanks, Bill W. > > > > > > > > From: Rizzo, Christopher via ipp > > Sent: Thursday, February 28, 2019 4:12 PM > > To: Kennedy, Smith (Wireless & Standards Architect); Rick Yardumian > > Cc: PWG IPP WG Reflector > > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods > > > > This update looks good to me. > > > > 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 > > > > From: "Kennedy, Smith (Wireless & Standards Architect)" = > > > Date: Thursday, February 28, 2019 at 12:36 PM > > To: Christopher Rizzo >, Rick Yardumian = > > > Cc: PWG Workgroup > > > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods > > > > Thanks for the feedback Chris! I also received this feedback from = Canon's Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this = issue by rewriting 3.3.2 to more meaningfully describe an authorization = failure. > > > > Here's the rewrite. Any objections or suggestions? > > > > Harry is also visiting Andy's office and wants to print from his = laptop. He uses his laptop to discover available printers, and selects = one listed. The printer is configured to limit access to only authorized = users. > > > > The printer challenges the laptop for authentication, and the laptop = presents an authentication dialog to Harry. Harry has an account, and = enters the account's username and password. The printer accepts these = credentials, but that account is not authorized to access that printer. = Harry's laptop shows a notification dialog expressing this to Harry. = Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil. > > > > Smith > > > > > > > > On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher = > = wrote: > > > > Just curious, but section 3.3 Exceptions of this document has = sections 3.3.1 and 3.3.2 which are pretty much exact duplicates of each = other, exception being Lisa vs. Harry. Was this intentional? > > > > 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 > > > > =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith = (Wireless & Standards Architect)" on behalf of smith.kennedy@hp.com = > wrote: > > > > Greetings, > > > > This message begins the IPP workgroup Last Call of the IPP = Authentication Methods best practice draft, available at: > > > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt = > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf = > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf = > > > > Please respond with any feedback or comments by doing a "reply all" = to this message. > > > > This last call will end on January 31, 2019 at 10pm PT. > > > > Cheers, > > Smith > > > > /** > > Smith Kennedy > > HP Inc. > > */ > > > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://www.pwg.org/mailman/listinfo/ipp = > > > > > > > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://www.pwg.org/mailman/listinfo/ipp = >=20 > ________________________ > Michael Sweet >=20 --Apple-Mail=_D63F6A59-811D-4356-B8E2-5974D50F9BA4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Thanks for mentioning this detail, Bill! I am fine with = adding that the purpose of authentication is to acquire a token to be = used for access authorization. But after re-reading the definition of = "job-originating-user-name" from RFC 8011, I'm not sure I agree that the = value of the "job-originating-user-name" attribute itself is necessarily = the token to be used. Notice the second paragraph, which talks = about the Printer maintaining an "internal originating user ID of some = form", which is "used for authorization checks" but isn't publicly = visible:

    5.3.6. =  job-originating-user-name (name(MAX))
       This REQUIRED = attribute contains the name of the End User that
       submitted the = Print Job.  The Printer sets this attribute to the = most
      =  authenticated printable name that it can obtain from = the
      =  authentication service over which the IPP operation was = received.
       Only if such a name is not available does the = Printer use the value
       supplied by the Client in the = "requesting-user-name" operation
       attribute of the Job Creation = request (see Sections 5.4.2, 5.4.3,
       and 9).

       Note: The Printer needs to keep an internal = originating user ID of
       some form, typically as a credential of a = principal, with the Job.
       Since such an internal = attribute is implementation dependent and not
       of interest to = Clients, it is not specified as a Job attribute. =  This
       originating user ID is used for authorization = checks (if any) on all
       subsequent = operations.

    So the value of = "job-originating-user-name" could be some printable name string, but = that value isn't itself necessarily the token that would be used by the = Printer's "backend" implementation to engage with a particular = authentication service. And that token has no IPP Job Status attribute = and is considered by IPP to be an internal implementation = detail. 

    Smith



    On Mar 1, 2019, at 12:21 PM, wamwagner@comcast.net= wrote:

    Both = Michael and Smith make good points, and I think it is mainly a question = of how far Smith wants to extend the scope of the document. =46rom his = earlier message, it appears that he has  added more information on = Authorization. However, his comment that the purpose of = Authentication  in a printer is primarily to support Authorization = features is quite to the point. Indeed,  the text might point out = that the extended authentication mechanisms discussed relate to = obtaining the value of the IPP attribute job-originating-user-name, = which is used by the printer for authorization checks. That is, 
       The Printer sets this attribute to the most
       authenticated = printable name that it can obtain from the
       authentication = service over which the IPP operation was received.
       Only if such a = name is not available does the Printer use the value
       supplied by the = Client in the "requesting-user-name" operation
       attribute of = the Job Creation request.
     
    Of course, from Michael=E2=80=99s = point, discussion of printer-implemented authorization  in this = document is probably limited to  restating what is in STD92: using =  the most authenticated printable = name for authorization and IPP responses to authentication = failures. 
     
    Thanks, 
    Bill = Wagner
     
     
    From: Kennedy, Smith (Wireless & = Standards Architect)
    Sent: Friday, March 1, 2019 = 10:49 AM
    To: Michael Sweet
    Cc: William A Wagner; Rizzo, = Christopher; Rick Yardumian; PWG IPP Workgroup
    Subject: Re: [IPP] WG Last Call: = IPP Authentication Methods
     
    How about this:
     
    3.4. Out of Scope
     
    The following are considered out of scope for this = document:
    1. Definition of new HTTP authentication methods
    2. Definition of how specific = authorization mechanisms are used by an IPP Printer. The Internet = Printing Protocol/1.1 [STD92] defines authorization roles for end users, = operators, and administrators, but does not define how a Printer or an = authorization mechanism maps those roles to authenticated = users.
     
     


    On Feb 28, 2019, at 5:00 PM, Michael Sweet <msweet@msweet.org> = wrote:
     

    Bill,

    I think you make a good point.
    Smith,

    I think you can make a = general statement about authorization, something along the lines of:

    "Specific authorization mechanisms are outside = the scope of this document. The Internet Printing Protocol/1.1 [STD92] = defines authorization roles for end users, operators, and = administrators, but does not define how a Printer maps those roles to = authenticated users."


    > = On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp <ipp@pwg.org> wrote:
    > 
    > Smith,
    > 
    > Sorry, = my confusion continues. Your new Authorization example may be valid, but = it seems odd to me that someone would have an account in a printer but = not have authority to print at all. Conditional authority, restricting = use to certain times or restricting color, or quantity, etc. would be = more realistic, but that is at the IPP level and does not appear to be = addressed in this specification. 
    > 
    > The = title is Authentication Methods, and although I may have missed it, I do = not think that it does much with authorization (at least not by the = printer), which would occur after successful Authentication. Perhaps the = Authorization use case should be put in the out of scope section?
    > Thanks, Bill W.
    > 
    > 
    > 
    > From: = Rizzo, Christopher via ipp
    > Sent: Thursday, February = 28, 2019 4:12 PM
    > To: Kennedy, Smith (Wireless & = Standards Architect); Rick Yardumian
    > Cc: PWG IPP WG = Reflector
    > Subject: Re: [IPP] WG Last Call: IPP = Authentication Methods
    > 
    > This = update looks good to me.
    > 
    > = 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
    > 
    > From: = "Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>
    > Date: Thursday, February 28, 2019 at 12:36 PM
    > To: Christopher Rizzo <Christopher.Rizzo@xerox.com>, Rick Yardumian <RYardumian@ciis.canon.com>
    > Cc: PWG = Workgroup <ipp@pwg.org>
    > Subject: Re: [IPP] WG Last Call: IPP Authentication = Methods
    > 
    > Thanks = for the feedback Chris! I also received this feedback from Canon's Rick = Yardumian (CC'ed). In my LCRC draft, I've resolved this issue by = rewriting 3.3.2 to more meaningfully describe an authorization = failure. 
    > 
    > Here's the rewrite. Any objections or suggestions?
    > 
    > Harry is also visiting Andy's office and wants to print = from his laptop. He uses his laptop to discover available printers, and = selects one listed. The printer is configured to limit access to only = authorized users. 
    > 
    > The printer challenges the laptop for authentication, = and the laptop presents an authentication dialog to Harry. Harry has an = account, and enters the account's username and password. The printer = accepts these credentials, but that account is not authorized to access = that printer. Harry's laptop shows a notification dialog expressing this = to Harry. Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil.
    > 
    > Smith
    > 
    > 
    > 
    > On Feb = 28, 2019, at 12:33 PM, Rizzo, Christopher <Christopher.Rizzo@xerox.com> wrote:
    > 
    > Just curious, but section 3.3 Exceptions of this = document has sections 3.3.1 and 3.3.2 which are pretty much exact = duplicates of each other, exception being Lisa vs. Harry. Was this = intentional?
    > 
    > = 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
    > 
    > =EF=BB=BF= On 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wireless & = Standards Architect)" <ipp-bounces@pwg.org on behalf of smith.kennedy@hp.com> = wrote:
    > 
    > = Greetings,
    > 
    > This = message begins the IPP workgroup Last Call of the IPP Authentication = Methods best practice draft, available at:
    > 
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt<= br class=3D"">> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf<= br class=3D"">> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf<= /a>
    > 
    > Please = respond with any feedback or comments by doing a "reply all" to this = message.
    > 
    > This = last call will end on January 31, 2019 at 10pm PT.
    > 
    > = Cheers,
    > Smith
    > 
    > /**
    > Smith Kennedy
    > HP Inc.
    > */
    > 
    > = _______________________________________________
    > ipp = mailing list
    >     ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp
    > 
    > 
    > 
    > _______________________________________________
    > ipp mailing list
    > ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp

    ________________________
    Michael = Sweet


    = --Apple-Mail=_D63F6A59-811D-4356-B8E2-5974D50F9BA4-- --Apple-Mail=_3D09FA5F-891C-4949-840A-593162238488 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx5kHsACgkQqskbKLDW 1N3NvA//fEKiBcktZZSpWH0ymtZFdRkAhSFLQKvLgGLqIPkD5k7hpxu5joxJtDPk 2Toml/1fgCD5Rlbuy3BA4BHof/IAoYdxP7KG7Rvm1Tbte7g/YN6GweVJwjANq27w VnXkKPSmq56b1x1VOP+3kpOgj55rKYIyfMR+OIBAkjoyDIoDtijYBDmQw7AYv+OK jZaTG7ZIHUS4EJ4Sj3YlQyHYVjIoiFZ0gUlz+oCXGnYXfTUQXkxheo28NiNKUTlG 5Lc6JPoaib7Oy2jTfdyEi/lfohrgmbUvTjsq7XA8x+VCTg99f/Ia/BgT6fGWKoDK 7UMr6xKYEUvG1s56bb/uZgmlgVrZfdSG52a/lTyHCBR+HEBAm4Km1GsQ21JXndxg mtjq7fxVNcc813A0SSbt+uhpKWdpIVVl23Qxp0/MOeDNCnwBVSeS0VUd+auk0fAb nzzjYwwwpdha3R07UCqYmyu7pgBtHpAbzML+I5wiRmhOg73qQmPnPKV1syQ/m79s FO8rQl8rgSqYAu30591vq4dJ+0mSpI4uGWYkvqr7BKZD31iUbCgRXTR6b8RDv/9c GrRd1EUvI2WzlRRMJRt50tYAc+lny8mSUOiIZ+9x+K7GUsmWyw6aUoCfUfpLY+YW drUqmSZzGR8wopG2PgWP0LzhP55esb4zn2s06lcwX13Us4T3Ekg= =NZDg -----END PGP SIGNATURE----- --Apple-Mail=_3D09FA5F-891C-4949-840A-593162238488-- --===============1768828976006340786== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1768828976006340786==-- From ipp-bounces@pwg.org Fri Mar 1 12:38:49 2019 Return-Path: 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 AF41E1200B3 for ; Fri, 1 Mar 2019 12:38:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.282 X-Spam-Level: X-Spam-Status: No, score=-0.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 X0ohsJfwUH3o for ; Fri, 1 Mar 2019 12:38:46 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id D19E512D4F2 for ; Fri, 1 Mar 2019 12:38:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 1B7A33F42; Fri, 1 Mar 2019 20:38:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 195402667; Fri, 1 Mar 2019 20:38:31 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 999DC2667; Fri, 1 Mar 2019 20:38:29 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 2E09D315 for ; Fri, 1 Mar 2019 20:38:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551472706; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZxKtABA1un8puKCu19ykIfuAixmT8baNobzvuJna1Fw=; b=RxmMyDUPzFwQLqjbOdORZECixnnCJbKGnqgJYFFmJnllHEx8NVllqJ7lwm5bVTZULaLwfhk30C/BJHotxLsWzU8ytcXCDHQUgx7ywnAf3M6qiZYO/b56HGGSoT03UciiumDkGV23jRq0PrQ8Vw7M1pnZFgvwibU5g8TZdPpvg6U= Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-by2nam05lp2057.outbound.protection.outlook.com [104.47.50.57]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-316-g7PjOyUhNRqX58TEBv9DMA-1; Fri, 01 Mar 2019 15:38:23 -0500 X-MC-Unique: g7PjOyUhNRqX58TEBv9DMA-1 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM (10.169.49.22) by TU4PR8401MB1246.NAMPRD84.PROD.OUTLOOK.COM (10.169.49.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Fri, 1 Mar 2019 20:38:21 +0000 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908]) by TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908%4]) with mapi id 15.20.1643.022; Fri, 1 Mar 2019 20:38:21 +0000 To: William A Wagner Thread-Topic: [IPP] WG Last Call: IPP Authentication Methods Thread-Index: AQHUz8NLomFBNpPp9Em5uDLz5UhCS6X27S6AgAA7UwCAAAwjgIAACT2A Date: Fri, 1 Mar 2019 20:38:20 +0000 Message-ID: References: <20190228225026.88CE53F41@www.pwg.org> <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> <91959.119030114214901401@us-mta-207.us.mimecast.lan> In-Reply-To: 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b859552b-d530-4a9d-f28c-08d69e85d7fa x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:TU4PR8401MB1246; x-ms-traffictypediagnostic: TU4PR8401MB1246: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtUVTRQUjg0MDFNQjEyNDY7MjM6MlZGcHAzTmptR1VtbWdhazNoR3NTYzRz?= =?utf-8?B?QXZzeG5oL0cydjIyYkt1Rnc2UjhyMGJhclVRTHRMR1BRZ0ZpN3R2VWNPWWhx?= =?utf-8?B?N1AyaHRMb1dXS2UvVGlzdldON0lKQjFnQ0FaUVR4VGh6YVJUODNPVEhHaHFU?= =?utf-8?B?dnZGNHlONEI3OWVWNm9wVUxQdzRiTGpjL0pVNmtZK0JkRnJPMC9TVzhNYVVC?= =?utf-8?B?UlJOS3BWWEl3Q3JOanA2NmVCNWNZR3JWaUlqWU52OHJJK1N0cmRGU2dtUkoy?= =?utf-8?B?Y1lTU1BQeGlaK0tTZ0krSDJ3SzRvM09xZyswWVRjMXJIYXhHV0dobGZvVG1R?= =?utf-8?B?KytwZ3UxNXVaUi9QajFtZ09uNDZXQlNrUFh0ZWU5UFhrd2JlU1dycEo0aTgw?= =?utf-8?B?NUFXQnVvaS9uakVwV0l6V3ZXZWZxYmlqemRUbEFwVVVtdGxqcmkzN0VWUzk4?= =?utf-8?B?NzkzSC9VUlZEUjBTYWplbE1ieUpsN3ozdFJvRkZzWGhTbmNBNjhCdGRIL09H?= =?utf-8?B?S1ZRdTNxZHIrTmttZklWQ293a2dqcC9aRUpTd1Z3Y0k2d0JMeGlpenNLTHhw?= =?utf-8?B?a3JFdDdzeVJUNmpaazBsWE04SzVSNlhVTVRtcWUreEVrN2VCSHN3ZjdkK0Ru?= =?utf-8?B?VU9JNkx6RURQa0VaUzQyQjRlbXVaRjg4MHdleVZGTE9KQmNSWHdibDJOS1Bo?= =?utf-8?B?S3c4VVQ1endlUDJDaHYvK2NGR1RHMUx6RmhOdzdBemFuczVKZWlhZm5RNDE4?= =?utf-8?B?Um8zciszdTR1NVlmaHc5NEh0Mzd4dkdLalFkOENnSVZLOTdiSWZ2ZHhmbCtj?= =?utf-8?B?TzhIbzdCRTF0WW9jai9IZnhINmhZakd0NDV6bkIvMUc5VmtzdnhhWEhqSWlX?= =?utf-8?B?RmRoK0pMa1RUckFUcnZuRXRjWE5ZYWx0UzZOUFRuaUNKYzkwalk4Ui9MblFr?= =?utf-8?B?YjlUNUt6d1VQQVF6Wk5iSk1DZ3ozYmxWVDZIcWJSZktiT25Zd3lITExaQyta?= =?utf-8?B?UWw2S1ZrQitjTlkzY0RhK2E2RDlCQ3ByWHEvcXpaTUswbm9yYVZzRXdTTkRq?= =?utf-8?B?aHphUndXcFExYW1YZnU4M0g3TnZHQThUejFUUUpWU1NpSHFFU3JSN1gvUnkw?= =?utf-8?B?SmV0UWF4bFh4LzdzUjdGVDVVbHU3aHBYRXFHS2k0eVZTcldFeFQ5b245WkhZ?= =?utf-8?B?ODEwSWNON052cDV2NWd5M1dKK0NDNDA4dWZXVWFFMlEydmUzeDBFUThZNTdL?= =?utf-8?B?YWRsVWlmYjZ6SnBPZ3JNUVpJanBjaE44NkF2eTVJTHRGZXpER0h2L3BXakpE?= =?utf-8?B?TXFaWnV2Wkp3TXp5MWJFOGRoWEpEeHY5NENaK1hvRW1UcHllcEFYN1BGT25q?= =?utf-8?B?M0pwRmplR0VOcU82cll5Vnc0SWVCd0pBVVBxaDJVR21hVkRPY2ZEV0d6ZDVh?= =?utf-8?B?c0hFcTl5WWpOTi9TYmQrajQ0RldySVZSQ1dJc0ZYWkhZMkh1YUtnS2VXU1ll?= =?utf-8?B?WUtkVFdWWUJ4N0JwSktXeUNpOCtVVlpNU2FBWGNOVFpkcmJDUC9YbSsrZUxv?= =?utf-8?B?aVZEOTYrV0NBb1JoVU5DSU9XVEN1eDNtc0dFZittMHVkR0hOWllPQmt1WlNr?= =?utf-8?B?NU84Q1VWdXB5LzZsbGJHWnkrSzhIYW04d0VVM09XUjZPWmRtMERpcmVrTlFJ?= =?utf-8?B?M0RlK3lqTk9ZcGJmVFpPNVFLZXRXcWk0WmdZQWcxRGhnVVhZTTdKMnZCN1cv?= =?utf-8?B?U3dDOU5Wajg1U2kxS2hyV2lMOXBweGRxUzkrZEJWbEhDK3NDMzZCR0pSNCtm?= =?utf-8?B?aEdQRWUwNk8rWjdFYnBycURsZEVqdjMrOFVKMW9EL3BRZWZ0ZXdmNnM2TVhz?= =?utf-8?B?a09rcmpCMmp2MTd4cENja0VKdEpHQ1RCaUdNYUdQWGZIcWFJUzYxeXVablF1?= =?utf-8?B?U2dHZHcyZkZ1emR5MmordEl1ejZEVUJMdVRzNm15cGRxVmluMXRTd3BmVFl6?= =?utf-8?B?Zml3UkE5ZUdUNllldHZ2dndiMUZXM2VoWlVBcjJ3PT0=?= x-microsoft-antispam-prvs: x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(136003)(366004)(346002)(39860400002)(199900001)(189003)(6602003)(199004)(51914003)(53936002)(6246003)(236005)(7736002)(6306002)(54896002)(81166006)(81156014)(966005)(105586002)(316002)(68736007)(99936001)(6512007)(606006)(66574012)(2906002)(99286004)(14444005)(66066001)(256004)(14454004)(6916009)(5660300002)(186003)(82746002)(54906003)(4326008)(26005)(102836004)(6436002)(476003)(2616005)(11346002)(86362001)(97736004)(83716004)(6486002)(6116002)(8676002)(446003)(30864003)(71190400001)(33656002)(71200400001)(53546011)(25786009)(6506007)(8936002)(36756003)(93886005)(229853002)(478600001)(106356001)(76176011)(3846002)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB1246; H:TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: kaDIhEJ0uzUAHTDYfO80LW7oK39wu9aIZqFBNF7Thyf+qUE9mwCeseXr4mU7oRSyZWNOwAjGpU2yJngszTk0ozSkpYUWHvNMhquYxNC67DeluPmpQyMD2QL8dYLycSyoa2x+LGdMFgL3PPtBrGJ5RjNoSHQznRWuSDZ13BLZaX0Z2+t8ImllNH2SQ9j02G8E+QOOPRJ4HWYR0oKGhKL66TkDD9pvvqnZh1zE9fUUSJ5HjObA2HZo9kT0ZSp2f5S9NCgNrWovnadUTPg1IzEIlT63vkTfqPOp3gG8QaM9EFa0M966AzjPIoBje4ylKRgcHtYgouWhOodRral2DHQ9xnmDCPFMO+CvbgKGLLeUQAPy5r8FMF5LHKKRq4fvrR3smhA/yySyRZyON83aCPtzMJLsjo5j2wLfk+L7ri7xZS0= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: b859552b-d530-4a9d-f28c-08d69e85d7fa X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2019 20:38:20.9439 (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-Transport-CrossTenantHeadersStamped: TU4PR8401MB1246 Cc: PWG IPP Workgroup , Michael Sweet Subject: Re: [IPP] WG Last Call: IPP Authentication Methods X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============0821111432087134236==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0821111432087134236== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_60A6C162-A721-4C58-8B78-E9A8107C78E9"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_60A6C162-A721-4C58-8B78-E9A8107C78E9 Content-Type: multipart/alternative; boundary="Apple-Mail=_1C8EC656-C9C0-4210-A52C-DDBB31C604F8" --Apple-Mail=_1C8EC656-C9C0-4210-A52C-DDBB31C604F8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I've updated Section 4 like so - thoughts? 4. Client Authentication Methods Authentication is the process of establishing some level of trust that = an entity is who or what they are claiming to be. A Printer uses the = =E2=80=9Cauthenticated identity=E2=80=9D or the =E2=80=9Cmost = authenticated user=E2=80=9D [RFC8011] to determine whether to allow the = requesting Client access to capabilities such as operations, resources, = and attributes. A Printer specifies its supported authentication methods = via several IPP attributes. The =E2=80=9Curi-authentication-supported=E2=80= =9D attribute [RFC8011] indicates the authentication method used for a = corresponding URI in =E2=80=9Cprinter-uri-supported=E2=80=9D [RFC8011]. = The =E2=80=9Cxri-authentication=E2=80=9D member attribute of = =E2=80=9Cprinter-xri-supported=E2=80=9D [RFC3380] specifies the same = corresponding values, if the Printer implements the = =E2=80=9Cprinter-xri-supported=E2=80=9D attribute. Each of the = authentication method keywords currently registered for = =E2=80=9Curi-authentication-supported=E2=80=9D is described in its own = subsection below. In cases where the Printer is not directly involved in the = authentication process, such as when OAuth2 is used, or when the Printer = depends on an external authentication service, the Printer might not be = directly aware of the User's identity following authentication. In these = cases, the Printer could still need to acquire the User's identity in = order to accurately document the User's identity in the Job Object's Job = Status attributes, or to support IPP operations such as = Get-User-Printer-Attributes [IPPGUPA] that depend on the User's identity = to provide meaningfully filtered operation responses. When handing an IPP Job Creation request, the Printer will need to = populate the Job's =E2=80=9Cjob-originating-user-name=E2=80=9D Job = Status attribute. In cases where the Printer relies upon an external = authentication service, it will need to acquire a meaningfully printable = value from the authentication service. The Printer or the Job might also need to store a token or identifier = (UUID, JWT, etc.) that represents the User's authenticated identity or = authentication session, in cases where the Printer depends on an = external authorization service for print policy evaluation. This token = is considered by IPP to be an internal implementation detail, and is not = available to Clients via IPP, as discussed in [RFC8011] section 5.3.6. One authentication system not described below is SAML (Security = Assertion Markup Language)[SAMLCORE]. As of this writing, none of the = standard SAML bindings to HTTP directly support IPP. SAML can indirectly = support OAuth2 via a SAML / OAuth2 gateway. The bridge typically uses = the SAML 2.0 assertion as an OAuth 2.0 Bearer token. Specific = instructions for how to configure this depends on the SAML and OAuth2 = system implementations, and is beyond the scope of this document. > On Mar 1, 2019, at 1:05 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp wrote: >=20 > Signed PGP part > Thanks for mentioning this detail, Bill! I am fine with adding that = the purpose of authentication is to acquire a token to be used for = access authorization. But after re-reading the definition of = "job-originating-user-name" from RFC 8011, I'm not sure I agree that the = value of the "job-originating-user-name" attribute itself is necessarily = the token to be used. Notice the second paragraph, which talks about the = Printer maintaining an "internal originating user ID of some form", = which is "used for authorization checks" but isn't publicly visible: >=20 > 5.3.6. job-originating-user-name (name(MAX)) > This REQUIRED attribute contains the name of the End User that > submitted the Print Job. The Printer sets this attribute to the = most > authenticated printable name that it can obtain from the > authentication service over which the IPP operation was received. > Only if such a name is not available does the Printer use the value > supplied by the Client in the "requesting-user-name" operation > attribute of the Job Creation request (see Sections 5.4.2, 5.4.3, > and 9). >=20 > Note: The Printer needs to keep an internal originating user ID of > some form, typically as a credential of a principal, with the Job. > Since such an internal attribute is implementation dependent and = not > of interest to Clients, it is not specified as a Job attribute. = This > originating user ID is used for authorization checks (if any) on = all > subsequent operations. >=20 > So the value of "job-originating-user-name" could be some printable = name string, but that value isn't itself necessarily the token that = would be used by the Printer's "backend" implementation to engage with a = particular authentication service. And that token has no IPP Job Status = attribute and is considered by IPP to be an internal implementation = detail. >=20 > Smith >=20 >=20 >=20 >> On Mar 1, 2019, at 12:21 PM, wamwagner@comcast.net = wrote: >>=20 >> Both Michael and Smith make good points, and I think it is mainly a = question of how far Smith wants to extend the scope of the document. = =46rom his earlier message, it appears that he has added more = information on Authorization. However, his comment that the purpose of = Authentication in a printer is primarily to support Authorization = features is quite to the point. Indeed, the text might point out that = the extended authentication mechanisms discussed relate to obtaining the = value of the IPP attribute job-originating-user-name, which is used by = the printer for authorization checks. That is, >> The Printer sets this attribute to the most >> authenticated printable name that it can obtain from the >> authentication service over which the IPP operation was received. >> Only if such a name is not available does the Printer use the = value >> supplied by the Client in the "requesting-user-name" operation >> attribute of the Job Creation request. >>=20 >> Of course, from Michael=E2=80=99s point, discussion of = printer-implemented authorization in this document is probably limited = to restating what is in STD92: using the most authenticated printable = name for authorization and IPP responses to authentication failures. >>=20 >> Thanks, >> Bill Wagner >>=20 >>=20 >> From: Kennedy, Smith (Wireless & Standards Architect) = >> Sent: Friday, March 1, 2019 10:49 AM >> To: Michael Sweet >> Cc: William A Wagner ; Rizzo, = Christopher ; Rick Yardumian = ; PWG IPP Workgroup = >> Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >>=20 >> How about this: >>=20 >> 3.4. Out of Scope >>=20 >> The following are considered out of scope for this document: >> Definition of new HTTP authentication methods >> Definition of how specific authorization mechanisms are used by an = IPP Printer. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer or an authorization mechanism maps those = roles to authenticated users. >>=20 >>=20 >>=20 >>=20 >> On Feb 28, 2019, at 5:00 PM, Michael Sweet > wrote: >>=20 >> Bill, >>=20 >> I think you make a good point. >>=20 >> Smith, >>=20 >> I think you can make a general statement about authorization, = something along the lines of: >>=20 >> "Specific authorization mechanisms are outside the scope of this = document. The Internet Printing Protocol/1.1 [STD92] defines = authorization roles for end users, operators, and administrators, but = does not define how a Printer maps those roles to authenticated users." >>=20 >>=20 >> > On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp > wrote: >> > >> > Smith, >> > >> > Sorry, my confusion continues. Your new Authorization example may = be valid, but it seems odd to me that someone would have an account in a = printer but not have authority to print at all. Conditional authority, = restricting use to certain times or restricting color, or quantity, etc. = would be more realistic, but that is at the IPP level and does not = appear to be addressed in this specification. >> > >> > The title is Authentication Methods, and although I may have missed = it, I do not think that it does much with authorization (at least not by = the printer), which would occur after successful Authentication. Perhaps = the Authorization use case should be put in the out of scope section? >> > Thanks, Bill W. >> > >> > >> > >> > From: Rizzo, Christopher via ipp >> > Sent: Thursday, February 28, 2019 4:12 PM >> > To: Kennedy, Smith (Wireless & Standards Architect); Rick Yardumian >> > Cc: PWG IPP WG Reflector >> > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >> > >> > This update looks good to me. >> > >> > 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 >> > >> > From: "Kennedy, Smith (Wireless & Standards Architect)" = > >> > Date: Thursday, February 28, 2019 at 12:36 PM >> > To: Christopher Rizzo >, Rick Yardumian = > >> > Cc: PWG Workgroup > >> > Subject: Re: [IPP] WG Last Call: IPP Authentication Methods >> > >> > Thanks for the feedback Chris! I also received this feedback from = Canon's Rick Yardumian (CC'ed). In my LCRC draft, I've resolved this = issue by rewriting 3.3.2 to more meaningfully describe an authorization = failure. >> > >> > Here's the rewrite. Any objections or suggestions? >> > >> > Harry is also visiting Andy's office and wants to print from his = laptop. He uses his laptop to discover available printers, and selects = one listed. The printer is configured to limit access to only authorized = users. >> > >> > The printer challenges the laptop for authentication, and the = laptop presents an authentication dialog to Harry. Harry has an account, = and enters the account's username and password. The printer accepts = these credentials, but that account is not authorized to access that = printer. Harry's laptop shows a notification dialog expressing this to = Harry. Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil. >> > >> > Smith >> > >> > >> > >> > On Feb 28, 2019, at 12:33 PM, Rizzo, Christopher = > = wrote: >> > >> > Just curious, but section 3.3 Exceptions of this document has = sections 3.3.1 and 3.3.2 which are pretty much exact duplicates of each = other, exception being Lisa vs. Harry. Was this intentional? >> > >> > 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 >> > >> > =EF=BB=BFOn 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith = (Wireless & Standards Architect)" on behalf of smith.kennedy@hp.com = > wrote: >> > >> > Greetings, >> > >> > This message begins the IPP workgroup Last Call of the IPP = Authentication Methods best practice draft, available at: >> > >> > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt = >> > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf = >> > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf = >> > >> > Please respond with any feedback or comments by doing a "reply all" = to this message. >> > >> > This last call will end on January 31, 2019 at 10pm PT. >> > >> > Cheers, >> > Smith >> > >> > /** >> > Smith Kennedy >> > HP Inc. >> > */ >> > >> > _______________________________________________ >> > ipp mailing list >> > ipp@pwg.org >> > https://www.pwg.org/mailman/listinfo/ipp = >> > >> > >> > >> > _______________________________________________ >> > ipp mailing list >> > ipp@pwg.org >> > https://www.pwg.org/mailman/listinfo/ipp = >>=20 >> ________________________ >> Michael Sweet >>=20 >=20 >=20 --Apple-Mail=_1C8EC656-C9C0-4210-A52C-DDBB31C604F8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I've = updated Section 4 like so - thoughts?

    4. Client Authentication Methods
    Authentication is = the process of establishing some level of trust that an entity is who or = what they are claiming to be. A Printer uses the =E2=80=9Cauthenticated = identity=E2=80=9D or the =E2=80=9Cmost authenticated user=E2=80=9D = [RFC8011] to determine whether to allow the requesting Client access to = capabilities such as operations, resources, and attributes. A Printer = specifies its supported authentication methods via several IPP = attributes. The =E2=80=9Curi-authentication-supported=E2=80=9D attribute = [RFC8011] indicates the authentication method used for a corresponding = URI in =E2=80=9Cprinter-uri-supported=E2=80=9D [RFC8011]. The = =E2=80=9Cxri-authentication=E2=80=9D member attribute of = =E2=80=9Cprinter-xri-supported=E2=80=9D [RFC3380] specifies the same = corresponding values, if the Printer implements the = =E2=80=9Cprinter-xri-supported=E2=80=9D attribute. Each of the = authentication method keywords currently registered for = =E2=80=9Curi-authentication-supported=E2=80=9D is described in its own = subsection below.

    In cases where the Printer is not directly involved in the = authentication process, such as when OAuth2 is used, or when the Printer depends on an = external authentication service, the Printer might not be directly aware of the User's = identity following authentication. In these cases, the Printer could = still need to acquire the User's identity in order to = accurately document the User's identity in the Job Object's Job Status = attributes, or to support IPP operations such as Get-User-Printer-Attributes = [IPPGUPA] that depend on the User's identity to provide meaningfully filtered operation = responses.

    When handing an IPP Job Creation = request, the Printer will need to populate the Job's = =E2=80=9Cjob-originating-user-name=E2=80=9D Job Status attribute. In = cases where the Printer relies upon an external authentication service, = it will need to acquire a meaningfully printable value from the = authentication service.

    The Printer or = the Job might also need to store a token or identifier (UUID, JWT, etc.) = that represents the User's authenticated identity or authentication = session, in cases where the Printer depends on an external authorization = service for print policy evaluation. This token is considered by IPP to = be an internal implementation detail, and is not available to Clients = via IPP, as discussed in [RFC8011] section 5.3.6.

    One authentication system not described below is SAML = (Security Assertion Markup Language)[SAMLCORE]. As of this writing, none = of the standard SAML bindings to HTTP directly support IPP. SAML can = indirectly support OAuth2 via a SAML / OAuth2 gateway. The bridge = typically uses the SAML 2.0 assertion as an OAuth 2.0 Bearer token. = Specific instructions for how to configure this depends on the SAML and = OAuth2 system implementations, and is beyond the scope of this = document.



    On Mar 1, 2019, at 1:05 PM, Kennedy, Smith (Wireless & = Standards Architect) via ipp <ipp@pwg.org> wrote:

    Signed PGP = part
    Thanks for mentioning = this detail, Bill! I am fine with adding that the purpose of = authentication is to acquire a token to be used for access = authorization. But after re-reading the definition of = "job-originating-user-name" from RFC 8011, I'm not sure I agree that the = value of the "job-originating-user-name" attribute itself is necessarily = the token to be used. Notice the second paragraph, which talks = about the Printer maintaining an "internal originating user ID of some = form", which is "used for authorization checks" but isn't publicly = visible:

    5.3.6. =  job-originating-user-name (name(MAX))
       This REQUIRED = attribute contains the name of the End User that
       submitted the = Print Job.  The Printer sets this attribute to the = most
      =  authenticated printable name that it can obtain from = the
      =  authentication service over which the IPP operation was = received.
       Only if such a name is not available does the = Printer use the value
       supplied by the Client in the = "requesting-user-name" operation
       attribute of the Job Creation = request (see Sections 5.4.2, 5.4.3,
       and 9).

       Note: The Printer needs to keep an internal = originating user ID of
       some form, typically as a credential of a = principal, with the Job.
       Since such an internal = attribute is implementation dependent and not
       of interest to = Clients, it is not specified as a Job attribute. =  This
       originating user ID is used for authorization = checks (if any) on all
       subsequent = operations.

    So the value of = "job-originating-user-name" could be some printable name string, but = that value isn't itself necessarily the token that would be used by the = Printer's "backend" implementation to engage with a particular = authentication service. And that token has no IPP Job Status attribute = and is considered by IPP to be an internal implementation = detail. 

    Smith



    On Mar 1, 2019, at 12:21 PM, wamwagner@comcast.net= wrote:

    Both = Michael and Smith make good points, and I think it is mainly a question = of how far Smith wants to extend the scope of the document. =46rom his = earlier message, it appears that he has  added more information on = Authorization. However, his comment that the purpose of = Authentication  in a printer is primarily to support Authorization = features is quite to the point. Indeed,  the text might point out = that the extended authentication mechanisms discussed relate to = obtaining the value of the IPP attribute job-originating-user-name, = which is used by the printer for authorization checks. That is, 
       The Printer sets this attribute to the most
       authenticated = printable name that it can obtain from the
       authentication = service over which the IPP operation was received.
       Only if such a = name is not available does the Printer use the value
       supplied by the = Client in the "requesting-user-name" operation
       attribute of = the Job Creation request.
     
    Of course, from Michael=E2=80=99s = point, discussion of printer-implemented authorization  in this = document is probably limited to  restating what is in STD92: using =  the most authenticated printable = name for authorization and IPP responses to authentication = failures. 
     
    Thanks, 
    Bill = Wagner
     
     
    From: Kennedy, Smith (Wireless & = Standards Architect)
    Sent: Friday, March 1, 2019 = 10:49 AM
    To: Michael Sweet
    Cc: William A Wagner; Rizzo, = Christopher; Rick Yardumian; PWG IPP Workgroup
    Subject: Re: [IPP] WG Last Call: = IPP Authentication Methods
     
    How about this:
     
    3.4. Out of Scope
     
    The following are considered out of scope for this = document:
    1. Definition of new HTTP authentication methods
    2. Definition of how specific = authorization mechanisms are used by an IPP Printer. The Internet = Printing Protocol/1.1 [STD92] defines authorization roles for end users, = operators, and administrators, but does not define how a Printer or an = authorization mechanism maps those roles to authenticated = users.
     
     


    On Feb 28, 2019, at 5:00 PM, Michael Sweet <msweet@msweet.org> = wrote:
     

    Bill,

    I think you make a good point.
    Smith,

    I think you can make a = general statement about authorization, something along the lines of:

    "Specific authorization mechanisms are outside = the scope of this document. The Internet Printing Protocol/1.1 [STD92] = defines authorization roles for end users, operators, and = administrators, but does not define how a Printer maps those roles to = authenticated users."


    > = On Feb 28, 2019, at 5:50 PM, wamwagner--- via ipp <ipp@pwg.org> wrote:
    > 
    > Smith,
    > 
    > Sorry, = my confusion continues. Your new Authorization example may be valid, but = it seems odd to me that someone would have an account in a printer but = not have authority to print at all. Conditional authority, restricting = use to certain times or restricting color, or quantity, etc. would be = more realistic, but that is at the IPP level and does not appear to be = addressed in this specification. 
    > 
    > The = title is Authentication Methods, and although I may have missed it, I do = not think that it does much with authorization (at least not by the = printer), which would occur after successful Authentication. Perhaps the = Authorization use case should be put in the out of scope section?
    > Thanks, Bill W.
    > 
    > 
    > 
    > From: = Rizzo, Christopher via ipp
    > Sent: Thursday, February = 28, 2019 4:12 PM
    > To: Kennedy, Smith (Wireless & = Standards Architect); Rick Yardumian
    > Cc: PWG IPP WG = Reflector
    > Subject: Re: [IPP] WG Last Call: IPP = Authentication Methods
    > 
    > This = update looks good to me.
    > 
    > = 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
    > 
    > From: = "Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>
    > Date: Thursday, February 28, 2019 at 12:36 PM
    > To: Christopher Rizzo <Christopher.Rizzo@xerox.com>, Rick Yardumian <RYardumian@ciis.canon.com>
    > Cc: PWG = Workgroup <ipp@pwg.org>
    > Subject: Re: [IPP] WG Last Call: IPP Authentication = Methods
    > 
    > Thanks = for the feedback Chris! I also received this feedback from Canon's Rick = Yardumian (CC'ed). In my LCRC draft, I've resolved this issue by = rewriting 3.3.2 to more meaningfully describe an authorization = failure. 
    > 
    > Here's the rewrite. Any objections or suggestions?
    > 
    > Harry is also visiting Andy's office and wants to print = from his laptop. He uses his laptop to discover available printers, and = selects one listed. The printer is configured to limit access to only = authorized users. 
    > 
    > The printer challenges the laptop for authentication, = and the laptop presents an authentication dialog to Harry. Harry has an = account, and enters the account's username and password. The printer = accepts these credentials, but that account is not authorized to access = that printer. Harry's laptop shows a notification dialog expressing this = to Harry. Harry clicks =E2=80=9COK=E2=80=9D and looks for a pencil.
    > 
    > Smith
    > 
    > 
    > 
    > On Feb = 28, 2019, at 12:33 PM, Rizzo, Christopher <Christopher.Rizzo@xerox.com> wrote:
    > 
    > Just curious, but section 3.3 Exceptions of this = document has sections 3.3.1 and 3.3.2 which are pretty much exact = duplicates of each other, exception being Lisa vs. Harry. Was this = intentional?
    > 
    > = 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
    > 
    > =EF=BB=BF= On 1/17/19, 4:00 PM, "ipp on behalf of Kennedy, Smith (Wireless & = Standards Architect)" <ipp-bounces@pwg.org on behalf of smith.kennedy@hp.com> = wrote:
    > 
    > = Greetings,
    > 
    > This = message begins the IPP workgroup Last Call of the IPP Authentication = Methods best practice draft, available at:
    > 
    > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.odt<= br class=3D"">> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117.pdf<= br class=3D"">> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190117-rev.pdf<= /a>
    > 
    > Please = respond with any feedback or comments by doing a "reply all" to this = message.
    > 
    > This = last call will end on January 31, 2019 at 10pm PT.
    > 
    > = Cheers,
    > Smith
    > 
    > /**
    > Smith Kennedy
    > HP Inc.
    > */
    > 
    > = _______________________________________________
    > ipp = mailing list
    >     ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp
    > 
    > 
    > 
    > _______________________________________________
    > ipp mailing list
    > ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp

    ________________________
    Michael = Sweet




    = --Apple-Mail=_1C8EC656-C9C0-4210-A52C-DDBB31C604F8-- --Apple-Mail=_60A6C162-A721-4C58-8B78-E9A8107C78E9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx5mDsACgkQqskbKLDW 1N3XXg/9Hqp4B3HyUbEQUnDXd1cpOHPIqyArJBpKI2HkdI++99lrb8l39HM3Pz5Z 14EVtk/4BFWPbK0u7ctMOnGH5Wv1hzshA0w0LjjIXiDxVKPfVQK1cLdCE2Uiyrzj CSKquyfrHnwRmP93w0lckzSODl2JygTn4v9JBpexyeJhYky3X5pFWE8HLzdkoV5k ocKGonpdClmNpwWDJGlMkyS/ttjN8oF7YgIyqQzBQphnucYFW6+SOW06Xs5O7SW2 UsTQ1K0ta48SXaQ+GSwCECt1swGIzWyc+2RDBmCg/skBP7z2syxKnFFvtkkMLCv7 FQuv/m3SJzlJAu3mmoUmd+oJGmcIPmw9awA0IH11IwEEUXuRFhC3iXg2tm++GeG8 TdnKP7Fr7NCi3Ub22f7zzL41NWEWndt19IfGBkZh/CA3k+U5KJi25IeuWJTb1XaY kmlHlbOK6FgP85TsInTkFUJa32D40JdULf10IgcPIavwUuCktzV18gIqbtGMwVlO rd3j9vwCql0MYQZB0pU9fDDOHZ3o04+PlyTcgxE4O3Qp6gnNjtJfIpSlUfTKsVpO toPqVVbeitrGceb35li83buBpgFi3dWC0DSLDpO9jk7cqxU9ddaa/5tlqgoC9rmb 7Z3JHn/rt3gHotVPVwhCII/qSpf+zTMyHuFxCDsTSRln0VddulE= =kv4F -----END PGP SIGNATURE----- --Apple-Mail=_60A6C162-A721-4C58-8B78-E9A8107C78E9-- --===============0821111432087134236== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0821111432087134236==-- From ipp-bounces@pwg.org Fri Mar 1 12:45:02 2019 Return-Path: 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 B764C12D4F2 for ; Fri, 1 Mar 2019 12:45:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 yzqNr8ybl7Z6 for ; Fri, 1 Mar 2019 12:45:00 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id F1AC11200B3 for ; Fri, 1 Mar 2019 12:44:59 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id B87EE3F48; Fri, 1 Mar 2019 20:44:58 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id B576D2667; Fri, 1 Mar 2019 20:44:53 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 183673F41; Fri, 1 Mar 2019 20:44:52 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 909CB24D3 for ; Fri, 1 Mar 2019 20:44:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551473089; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8dEoPnMLfkOlNOuVnJ8BwkJkprmBRaHAvPu9ZWfTJU0=; b=LUJiGioq7B10/Zna8jgVfbhU1npDUwSXkS7l2emLCZsw9B/W1zWrH+6Y8OZuZT/az2AwixSGi+5jla2jkn6m6cr63cL3si8yUDchhlzyhzEfBM4vOWtN6tKPvUsrKJ3xYpQUgS4eJh3CsoR29fwuFNSMEfoz5awxTwLJOdk3NAk= Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01lp2050.outbound.protection.outlook.com [104.47.32.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-154-tsweyJ55M9SX_hmgWfz5aw-1; Fri, 01 Mar 2019 15:44:47 -0500 X-MC-Unique: tsweyJ55M9SX_hmgWfz5aw-1 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM (10.169.49.22) by TU4PR8401MB0591.NAMPRD84.PROD.OUTLOOK.COM (10.169.44.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Fri, 1 Mar 2019 20:44:46 +0000 Received: from TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908]) by TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM ([fe80::bc4e:2f58:40ea:8908%4]) with mapi id 15.20.1643.022; Fri, 1 Mar 2019 20:44:46 +0000 To: Michael Sweet Thread-Topic: [IPP] WG Last Call: IPP Authentication Methods Thread-Index: AQHUz8NLomFBNpPp9Em5uDLz5UhCS6X27S6AgAACFICAAFBsgA== Date: Fri, 1 Mar 2019 20:44:46 +0000 Message-ID: References: <20190228225026.88CE53F41@www.pwg.org> <6C483769-3037-4F9C-802D-DBE52CF7F7BD@msweet.org> <36E506A2-38FD-45C1-90B4-677F4BDB2DAA@hp.com> <164F1C04-2526-4F58-A3BD-A6C5461A82DB@msweet.org> In-Reply-To: <164F1C04-2526-4F58-A3BD-A6C5461A82DB@msweet.org> 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 96b8ac09-c9a6-45c2-2ffc-08d69e86bdb4 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:TU4PR8401MB0591; x-ms-traffictypediagnostic: TU4PR8401MB0591: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtUVTRQUjg0MDFNQjA1OTE7MjM6aXdpcXUzTk5POXZBUis4ZDVHWmpsUG05?= =?utf-8?B?czd4Mzg4cE8wZHJObUt6WE9aako4UVVrVEN2WWptaElkemFOdnRBbGVjc2hO?= =?utf-8?B?UlJIY04xQTM0bnd2aDN1YWROZDBaOTdveUhlZFFWenlvWkhzTG5UdzZNb2lF?= =?utf-8?B?bng1U1pKaDVLOU9TNDYvcnZ1NnAwUHdWMDh2S04wMEZwYnZ6SmJZajdReFY1?= =?utf-8?B?dnRBdGtGUzY2c1A3Y3ZMalQwVDNqS00ycHRrV1U1ektrRUJEMnpRR2JTT2RK?= =?utf-8?B?ZnNPR3QxRTVGMmEyRVVqZHgzSzVMRzBTOUlXRGJDZnNzWWRndFNSZjhnL1R4?= =?utf-8?B?WjFkZzBJUHd5bDI4elZSRXpoMlQ0UFBrZEpNVjhGV1ArZVk3SEthU0ZDajN3?= =?utf-8?B?b2hDQ2x5dS9SR3lJQ05hZWhXNWh2dUdZa000UXY0VmdaaUNyUU50anFhNTFE?= =?utf-8?B?TklkWEp1dGJQSVZRZERqNXBsekVFcVdNL3luSUg4MVhOQk5rVjNKVXpsSWxh?= =?utf-8?B?MjViWlVvZHZEVzVNQy9qREVXeE45Wlc0cUtoRGNJT3NMeUNKNlVIUHBjSGlS?= =?utf-8?B?bTYrM1hEa20rUHBleTk3U2kzS2dlalJWMmNJdWxFTzVlckNZdHU4Ty9rUlpT?= =?utf-8?B?UUF5bDk4KzNFVE9LbUdyMnhsOUhobnpLK3pXdlVNQ0NzV0FET2VrdHo5Vmw3?= =?utf-8?B?aWpHSW40R1ZHaWQrS2tKYW5ZVUc0YUpSU2FxS2IyNDJrMm1WMitRa2p3NXBB?= =?utf-8?B?cVV3Z1plL2tjekpWdE80ZUEzOGRWWDRPOFdNZHpCSnVpcTR2ODdDOVNDSTlm?= =?utf-8?B?T3lMTDRxZ09nSy9aREpRNkVha2tPcDBRU1hBV2Q1SjBTZjM4YVY0czNhNldV?= =?utf-8?B?VWtFbDdkVmppMzdxQUlWenJmZjgzanBxQTZVNnYvNDQrQlljOHYvQmFRaTNk?= =?utf-8?B?SS9rRVZzeGR3R2RMbGxUWlFUb1kvekU1TCtnYTZzODY2aDAwY3A1bTVhZFl4?= =?utf-8?B?VndSazVqeW1kRklqSHJYaUx5VWhOU2c1UlJyVFM3Z1VyQWZNMEN4SStGb3d1?= =?utf-8?B?NjRrRFdIVkhIL3NseGUrLzRlQ1JjTk1Gb25JVHRUajhJeVZ2cmQ1N1JpOEZw?= =?utf-8?B?U1RJR0V4dFoyWWZoNHJvQ2Q4OVRRZUN3Z05NdlRkVHlwbEtJdW1WTlUrbmFM?= =?utf-8?B?RWQ3U3BnNHJBUi9Od2xRVC9rV3c1NzhSWDd6cURUazFjL2Z0Smh6cW1ETm5N?= =?utf-8?B?YUk5VDJzV3R6Nm1JRjB4ZGpFcGQzNnR1TEZja1dQTjN0WmFwN1BXcTRMT0Q3?= =?utf-8?B?dVJtVVpOL0ZYMTBubnBaWmtsRWRNVU83WWxnT3ZuSlFVaWZSN3MxY3VmQjZZ?= =?utf-8?B?VFNUL1NYSkw4UTJ5dml2UkNQenZLVjVOU0ZQNmNqalFEOHJKV1Z6ZkZJZFAv?= =?utf-8?B?RDlDelQvUzd4K0FUVElQbnRsVWVaVHViMjZTbXVNU1lpNWNOc1RKeTY2NHp6?= =?utf-8?B?VTkyQzNQa2dnSlZUNFBacWE2U3NFbGNVZ1U4UlF1bFhhRDVBS3cra0tWQUhx?= =?utf-8?B?VmRybGZMaXpGMXVpdnNERzVReGVFZUV6ZVZqMTBReE9iT0FRNkxKYlVsRDZG?= =?utf-8?B?aHh2ak1PdjRKVFo1MG5STFlPbWdvcjBGY045VWpXWVVlYjNSdWlyZWlXUFRD?= =?utf-8?B?SVNON1I2ZkxJaGk0aUNzUHllVmxNZmVqNDJweDNqaW9NR1gyRjRpV0k5UGNE?= =?utf-8?B?VnVQbXFLa3VwK0c4TWdSTVUvMHhTRmxSN201dklmOTlXT25TYStmM3NwMHdh?= =?utf-8?B?WlZicDFQWDN3USt6Y2VCZnVoWVp2ZEQ3ckJndzZvK1BmNXFXZz09?= x-microsoft-antispam-prvs: x-forefront-prvs: 09634B1196 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(39860400002)(396003)(136003)(376002)(199004)(189003)(6602003)(186003)(8676002)(68736007)(66574012)(81166006)(4326008)(316002)(6246003)(71200400001)(5660300002)(81156014)(2906002)(99936001)(7736002)(446003)(11346002)(6436002)(54896002)(66066001)(6512007)(36756003)(486006)(6116002)(82746002)(476003)(2616005)(105586002)(53936002)(3846002)(236005)(33656002)(97736004)(6916009)(14454004)(256004)(6486002)(99286004)(229853002)(102836004)(26005)(25786009)(93886005)(6506007)(53546011)(8936002)(106356001)(76176011)(83716004)(71190400001)(86362001)(14444005)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB0591; H:TU4PR8401MB1277.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 0hfZ6ini6DOyhBnjngV6OfCyd5wqy+YACPKYFd0F98VdGbWs3Ye4Px+O6F702gX9IQjJ9PPxDvrkRQlA64NpFJIbaUFCAK2Ol5kFqAAUO6h8EcAwkt/Ac2b8/lhoUa4R1K2u2oOT1CPP35uieFNUVtohHVp4SZlyA8D7FKIfrbHlsizPJSQC/VuXeE48voK9qeNiZ+sE6u9diz6KC0LMfZNth08lgB2cgs4n2faKLuaR+tMcF9Dl4CwxCfjqezk561uiLSkPHBVuOZr5JwuW2Fhiy4rr3NC5ruwYQ00XZbigu3MITVtBMTmkHpFpkx3N9tlShfPU+YjF0GvnKEjm+9n3aNTNy5DBkSb43j8U3dU3BEKGNtRMwEyyq1ZKf11krtqRAPJrmKbXlpPp8EHD3sApT8BvudgZOTG4IrG0ovs= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 96b8ac09-c9a6-45c2-2ffc-08d69e86bdb4 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2019 20:44:46.4132 (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-Transport-CrossTenantHeadersStamped: TU4PR8401MB0591 Cc: PWG IPP Workgroup Subject: Re: [IPP] WG Last Call: IPP Authentication Methods X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============1087566648327174539==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============1087566648327174539== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_5D849DBB-38BE-4D06-819F-16D827F6AC63"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_5D849DBB-38BE-4D06-819F-16D827F6AC63 Content-Type: multipart/alternative; boundary="Apple-Mail=_EDD3AB1D-E69A-4CDC-BF82-908920DD7A0E" --Apple-Mail=_EDD3AB1D-E69A-4CDC-BF82-908920DD7A0E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 1, 2019, at 8:56 AM, Michael Sweet wrote: >=20 > Smith, >=20 > I don't think the second sentence belongs there, but maybe in the = introduction to make it clear that this document talks about = authentication methods, not authorization? >=20 Hopefully my edits to section 4 provide that clarification? Either way, = I'll just ditch the second sentence from section 3.4 item 2. I've merged = the second sentence into the top of the third paragraph of Section 4: 4. Client Authentication Methods Authentication is the process of establishing some level of trust that = an entity is who or what they are claiming to be. A Printer uses the = =E2=80=9Cauthenticated identity=E2=80=9D or the =E2=80=9Cmost = authenticated user=E2=80=9D [RFC8011] to determine whether to allow the = requesting Client access to capabilities such as operations, resources, = and attributes. A Printer specifies its supported authentication methods = via several IPP attributes. The =E2=80=9Curi-authentication-supported=E2=80= =9D attribute [RFC8011] indicates the authentication method used for a = corresponding URI in =E2=80=9Cprinter-uri-supported=E2=80=9D [RFC8011]. = The =E2=80=9Cxri-authentication=E2=80=9D member attribute of = =E2=80=9Cprinter-xri-supported=E2=80=9D [RFC3380] specifies the same = corresponding values, if the Printer implements the = =E2=80=9Cprinter-xri-supported=E2=80=9D attribute. Each of the = authentication method keywords currently registered for = =E2=80=9Curi-authentication-supported=E2=80=9D is described in its own = subsection below. When handing an IPP Job Creation request, the Printer will need to = populate the Job's =E2=80=9Cjob-originating-user-name=E2=80=9D Job = Status attribute. In cases where the Printer relies upon an external = authentication service, it will need to acquire a meaningfully printable = value from the authentication service. The Internet Printing Protocol/1.1 [RFC8011] defines authorization roles = for end users, operators, and administrators, but does not define how a = Printer or an authorization mechanism maps those roles to authenticated = users. The Printer or the Job might also need to store a token or = identifier (UUID, JWT, etc.) that represents the User's authenticated = identity or authentication session, in cases where the Printer depends = on an external authorization service for print policy evaluation. This = token is considered by IPP to be an internal implementation detail, and = is not available to Clients via IPP, as discussed in [RFC8011] section = 5.3.6. One authentication system not described below is SAML (Security = Assertion Markup Language)[SAMLCORE]. As of this writing, none of the = standard SAML bindings to HTTP directly support IPP. SAML can indirectly = support OAuth2 via a SAML / OAuth2 gateway. The bridge typically uses = the SAML 2.0 assertion as an OAuth 2.0 Bearer token. Specific = instructions for how to configure this depends on the SAML and OAuth2 = system implementations, and is beyond the scope of this document. --Apple-Mail=_EDD3AB1D-E69A-4CDC-BF82-908920DD7A0E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

    On Mar 1, 2019, at 8:56 AM, Michael Sweet <msweet@msweet.org> = wrote:

    Smith,

    I don't think the second = sentence belongs there, but maybe in the introduction to make it clear = that this document talks about authentication methods, not = authorization?


    Hopefully my edits to section 4 provide that = clarification? Either way, I'll just ditch the second sentence from = section 3.4 item 2. I've merged the second sentence into the top of the = third paragraph of Section 4:


    4. = Client Authentication Methods

    Authentication is = the process of establishing some level of trust that an entity is who or = what they are claiming to be. A Printer uses the =E2=80=9Cauthenticated = identity=E2=80=9D or the =E2=80=9Cmost authenticated user=E2=80=9D = [RFC8011] to determine whether to allow the requesting Client access to = capabilities such as operations, resources, and attributes. A Printer = specifies its supported authentication methods via several IPP = attributes. The =E2=80=9Curi-authentication-supported=E2=80=9D attribute = [RFC8011] indicates the authentication method used for a corresponding = URI in =E2=80=9Cprinter-uri-supported=E2=80=9D [RFC8011]. The = =E2=80=9Cxri-authentication=E2=80=9D member attribute of = =E2=80=9Cprinter-xri-supported=E2=80=9D [RFC3380] specifies the same = corresponding values, if the Printer implements the = =E2=80=9Cprinter-xri-supported=E2=80=9D attribute. Each of the = authentication method keywords currently registered for = =E2=80=9Curi-authentication-supported=E2=80=9D is described in its own = subsection below.

    When handing an IPP Job Creation = request, the Printer will need to populate the Job's = =E2=80=9Cjob-originating-user-name=E2=80=9D Job Status attribute. In = cases where the Printer relies upon an external authentication service, = it will need to acquire a meaningfully printable value from the = authentication service.

    The Internet = Printing Protocol/1.1 [RFC8011] defines authorization roles for end = users, operators, and administrators, but does not define how a Printer = or an authorization mechanism maps those roles to authenticated users. = The Printer or the Job might also need to store a token or identifier = (UUID, JWT, etc.) that represents the User's authenticated identity or = authentication session, in cases where the Printer depends on an = external authorization service for print policy evaluation. This token = is considered by IPP to be an internal implementation detail, and is not = available to Clients via IPP, as discussed in [RFC8011] section = 5.3.6.

    One authentication system not = described below is SAML (Security Assertion Markup Language)[SAMLCORE]. = As of this writing, none of the standard SAML bindings to HTTP directly = support IPP. SAML can indirectly support OAuth2 via a SAML / OAuth2 = gateway. The bridge typically uses the SAML 2.0 assertion as an OAuth = 2.0 Bearer token. Specific instructions for how to configure this = depends on the SAML and OAuth2 system implementations, and is beyond the = scope of this document.
    = --Apple-Mail=_EDD3AB1D-E69A-4CDC-BF82-908920DD7A0E-- --Apple-Mail=_5D849DBB-38BE-4D06-819F-16D827F6AC63 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx5mb0ACgkQqskbKLDW 1N2XhQ//QXWHjr7/XP/7NNKORDDvx46Za5hJQy5vp5TCtiLobQkxFaLlXuBflbVp Av/Xav7UkYm9KQ8GmXS3NOib2pnIEUPoi7xt5pJUJA+ROF7dEXW+kGyysYReUZ4f cN1IxC3r5b7RL2ADEWQ0dBG2ZAhpYd8SZx8QsUxDstlgdvDrngRrZsyn0nht3psp uyABNCiz0TmdkSjeOCuNG2U4MugybtaFByb7JWtveLFwtSJ198do7s0aD6ELIfMu 8DyIAI/ampQ231wo0JkasmoiGLBESZwCvx/gc3hEnKmCExIo0FpcDer42yP2okXR zxwkPT1l7SUXytCyhPHKm39lglZoW70LKcxLEVN4xHiiUFwy1CLe/CkfZ4YcQXcC 5kCFIwccWvaCW9XTnCUlL+FLawY5J9aZlFc9x7eJUYbJi8xmPBT8vqw0eHnYgX6q A2l8pRXlfZOX+aXLJGUyoKKJEOk9Tz0SjekDiIxbX76XpDpMfIibhS/SJEiwvPa9 IOCJa1V521BGfYXUZb3GxqAC7ArSpLW7vQbGdylvJY2XLgqVcDC9b1UW6Y+UapLZ QB9BzrhoIiYhl8YVqdBAVIHAC+jDqo9I7K4t9EC8zkokHe7lJ4qVI8s0hvfo/4TV qKq0jE+amz//TLiyV9aQKSo7QAIVSlZbjoJaeF6lN8w6nN2Cc8Q= =0c5C -----END PGP SIGNATURE----- --Apple-Mail=_5D849DBB-38BE-4D06-819F-16D827F6AC63-- --===============1087566648327174539== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1087566648327174539==-- From ipp-bounces@pwg.org Mon Mar 4 06:29:55 2019 Return-Path: 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 B798E1310DB for ; Mon, 4 Mar 2019 06:29:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 T2rACnCX9E_z for ; Mon, 4 Mar 2019 06:29:54 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7CC13104B for ; Mon, 4 Mar 2019 06:29:54 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 930D83F9C; Mon, 4 Mar 2019 14:29:53 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id A2D482618; Mon, 4 Mar 2019 14:29:50 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 167E83F45; Mon, 4 Mar 2019 14:29:49 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id 90CE7315 for ; Mon, 4 Mar 2019 14:29:48 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x24EQtum011365 for ; Mon, 4 Mar 2019 06:29:47 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=L3BRImx1tOPKYx/NBR1REsTinCwrk777BOdTuT8N44U=; b=fK02rZclG+n0gZa0sqgM9xIqvjuj2B2MB687q6Y8BtmDhj5A+b761O4myQYj8jOSPAzF Bh5gZ9YlNnFIqK1/z9lrZxpCR/9GmmJM+yePCCLbkUMcMRRku0xmt0aMuMIzYnh7Kua2 6DLU87ACSRA4f5YCpX/jrJYT9Uq6zQDAb6qNfmQikTg5+6qddZitgPGlvvD3zpx40tvH j7dh27pflVdbRwWf4X9p2YgejC2sut7AsZ2JEtlPP6cNVfBB4M6cK9rdSKIue/VSlfGW Z3GAQ5i0f4uWXBjQC3KkdKp5NjzRCPpqasd7QNj+ugNtufuPITswIYFFwGLh4Dkibf7X Mw== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2qyscan6ts-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 04 Mar 2019 06:29:47 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNU0022WIXN1220@mr2-mtap-s01.rno.apple.com> for ipp@pwg.org; Mon, 04 Mar 2019 06:29:47 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNU00F00IUKI100@nwk-mmpp-sz13.apple.com>; Mon, 04 Mar 2019 06:29:47 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: e3d11cfbdce7e89273d7628e8a48ffd3 X-Va-R-CD: 2b64549f9e6640535569a744b296c349 X-Va-CD: 0 X-Va-ID: 1a79bff9-92d8-4606-89a4-c78b2c22fb9a X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: e3d11cfbdce7e89273d7628e8a48ffd3 X-V-R-CD: 2b64549f9e6640535569a744b296c349 X-V-CD: 0 X-V-ID: a020a96d-80f3-4590-a601-bf5c84d881df X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_06:,, signatures=0 Received: from [17.235.55.24] (unknown [17.235.55.24]) by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNU000FPIX6M040@nwk-mmpp-sz13.apple.com>; Mon, 04 Mar 2019 06:29:31 -0800 (PST) Date: Mon, 04 Mar 2019 09:29:27 -0500 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_06:, , signatures=0 Subject: [IPP] WG Last Call: MFD Alerts v1.1 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" [Resending this since I don't see it in the IPP mailing list archives] All, This message begins the IPP workgroup Last Call of the MFD Alerts v1.1 specification available at: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190216.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190216.pdf Please respond with any feedback or comments by doing a "reply all" to this message. This last call will end on March 14, 2019 at 10pm PT. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Mar 4 09:23:03 2019 Return-Path: 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 DABB21310D2 for ; Mon, 4 Mar 2019 09:23:03 -0800 (PST) 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=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 HJllVgVXiZdX for ; Mon, 4 Mar 2019 09:23:02 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id E721F1310C2 for ; Mon, 4 Mar 2019 09:23:01 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id B2E784072; Mon, 4 Mar 2019 17:23:00 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id F2DF6315; Mon, 4 Mar 2019 17:22:56 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 4A1D93F45; Mon, 4 Mar 2019 17:22:56 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id C3AE0315 for ; Mon, 4 Mar 2019 17:22:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551720173; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=ZD5wx7NrjOwY8/ZrhHO5sBIZB1tn2GC/nxo0iJZ3YO0=; b=ZKXUiEiQjp5r389WOtUG1TQw9aRReDSgXFl3PMuv4ZhiWepnekaLiqdPdMPFKBHHfesY3pgDRDKKnn/8KYrgF+91gbgCvd88wpnQn4GnlAXhzSDFP9eVTUsSGXJf1312xeb54PnuDYPW8qmv4RPf+eWZIGGOMEiycrm0nR2HVuY= Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01lp2058.outbound.protection.outlook.com [104.47.34.58]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-126-9CQBAKUDOwWExxbPVO3y1Q-1; Mon, 04 Mar 2019 12:22:52 -0500 X-MC-Unique: 9CQBAKUDOwWExxbPVO3y1Q-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0407.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Mon, 4 Mar 2019 17:22:51 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Mon, 4 Mar 2019 17:22:51 +0000 To: PWG IPP WG Reflector Thread-Topic: Updated stable draft of IPP Authentication Methods posted Thread-Index: AQHU0q7lkznSZJhIDEGZy/F9O9DjYQ== Date: Mon, 4 Mar 2019 17:22:50 +0000 Message-ID: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 86db06e7-a4b5-4b5c-14c7-08d6a0c6079a x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0407; x-ms-traffictypediagnostic: CS1PR8401MB0407: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0407; 23:V5B8nQnVwi0weYyV942vJIP1d6Auhmz9FcOP806?= =?us-ascii?Q?Bfc8c/n1ruQEDDjY6pw1KXS3OZLNPWdmkf6Ja8T8rgO+dVg2qQ9v2j0C8uCv?= =?us-ascii?Q?1SNhP8nZS3zqR7MAB3dh9IJU46Swv/KZj3C8IlvdHFxmi2H4MxGwrpYuFIGw?= =?us-ascii?Q?r+oqvZ3vX7hrpjDBvJ16ffgkwjNMVvzxwlMkc4LfH63/n7sj/ffzOwPdcGVD?= =?us-ascii?Q?AIeXNLrzX/hSiKP3EjS21+PRuEvKBMw1S8EICjeFZfPrnXUNo3Fr5bHZA2z2?= =?us-ascii?Q?Y6gljjZw2FeAC4LDqUrcTC3GE4tp6NErDtCr9Hm+gFH1R/DPFZ91Or3XqgLf?= =?us-ascii?Q?H/ClyykIbpe+R1ye8DoWaEADExfgA1QNmU2g6z60cYMX7YYLXtDyz1pDtbRc?= =?us-ascii?Q?lRvVlhhA71582NEUHLAhpFFnlxXh4k0+bpZREEe+/0/v54AQS+oe+0s8D+Nb?= =?us-ascii?Q?6ytesKuxlWrFRcx1cWuSnyf/0T+ppP1CT+f2aP4HIxuREZymMES0zm0LsDQw?= =?us-ascii?Q?peYKawjCvp+OJKUvvorORSIKeNuMxDQKr2XAC5cdI7zDpe9GaEVozq5eTG9B?= =?us-ascii?Q?w9Ng6cKNOxfmP/s/uyplbDwfAH8VHPmk508vzSIF1OgNxb0nuI7eiR41xyAH?= =?us-ascii?Q?6nQXkxFfyqQJmGtTv27K/K+HLz0q0GIlDyUelh8f5FiTzk37b+nKZL7oG9m4?= =?us-ascii?Q?lMQGCdugqkQSBH3gjBY1+6i4KNzKD+4nj3UWifY4hk5sBMiiXb6ynnSZbicD?= =?us-ascii?Q?pP0GlXczqpyxkB2XtCgonsoMkEQKvacWMTcRlOhqmR5WRxWyO4eu7Pemmby6?= =?us-ascii?Q?aHrh9ASfgKRkHpy2ttbloWdz6QWKAjqw/ECdZY3y0CRcItjQSdnQeqm2CZJY?= =?us-ascii?Q?dmbkltgRJFZc8gvPKR8Vdm9IwHleJKinSbWFrnJ4IYnKcyFsLs0kJiDvEF7L?= =?us-ascii?Q?hvm0xOJzHCsebjL6By5ph+xekD8jEhI0TaVbf2VY+eodclW5ywLK8nhShQlX?= =?us-ascii?Q?yCqR5ZBOLG9slakDeQ027o0XjDjYJ4qZvXm8YGQvLF2O9FyCtcOpCvTeglxA?= =?us-ascii?Q?/Xk70uz3gb28G3/ZWd31H5yFC9iGPzQ1/Cdietx/YbSvaMoLW3PS14i4ypBS?= =?us-ascii?Q?EZVm8JJSDXEHaIsoiNlO0/R6r2Oamxur+AsopgLKFOjrXSnvW2+KV9LwtLj2?= =?us-ascii?Q?OEwEVCV2e49DvCnGa5g1XcBkWxa58NBVDns1Ky/8x3XV+3lcNEBPgtXVKxAS?= =?us-ascii?Q?JP5MwWqVKnjynldcy0DA=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09669DB681 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(346002)(39860400002)(136003)(396003)(54164003)(189003)(199004)(6602003)(6512007)(54896002)(236005)(6306002)(53936002)(25786009)(8936002)(82746002)(81156014)(81166006)(7736002)(4744005)(102836004)(86362001)(71190400001)(71200400001)(186003)(476003)(5660300002)(36756003)(486006)(2616005)(316002)(6506007)(83716004)(99286004)(26005)(66066001)(14454004)(97736004)(3846002)(6116002)(33656002)(6486002)(966005)(6916009)(6436002)(99936001)(478600001)(2906002)(256004)(106356001)(105586002)(606006)(8676002)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0407; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: kJ//l2F51emhnu9KHurdxw/WzQybKjWiFKDCDL40YCsKGKZpzqBzTj41tf1G9e3VOEQJkZtY84IwU2NHedHcYgpG83NgZFuDJlgV2mERtOm4naLVZUXq/iARSHB4+kEMHjDjzeFK52foXroxjNLFHRACCiA4g9PIN6Izi2qRbAclov1LOThZGHNV+mhEAnh/Fn5K5QS5c2+A07VEod5xCHT/UYaz9zStuGONv0xglC4iWf14MuXq3+gkNGqJizjVJzJdGrmsTNtavjfN3Y8FqxNItEtDpf04lpmKnWDaQmIGdPcqeurWzVH+ZyVbxpP8uyLnN8bm6jtuqYaHOzMcR+V9J9tZpD0YGXDjFYL6rDxUkHGO3udXM98sqh169QiIJLL819tBBZCnbELHaiA8O2FzWg/7N1qPy+SDQwXUi60= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 86db06e7-a4b5-4b5c-14c7-08d6a0c6079a X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2019 17:22:50.9940 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0407 Subject: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============6368614916521729699==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6368614916521729699== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_A8395E3E-5786-4A34-9530-ACD2F02A87B7"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_A8395E3E-5786-4A34-9530-ACD2F02A87B7 Content-Type: multipart/alternative; boundary="Apple-Mail=_F0797B67-D250-4839-B1BC-8BC781C10D33" --Apple-Mail=_F0797B67-D250-4839-B1BC-8BC781C10D33 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings, Thanks to all who provided feedback on the 20190117 draft of IPP = Authentication Methods. Since I received valuable non-editorial feedback = in addition to editorial feedback on the draft from the PWG Last Call, I = have produced a new revision that hopefully resolves all the issues and = can be used in a second last call. The new draft is here: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf = I included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it. Smith /** Smith Kennedy HP Inc. */ --Apple-Mail=_F0797B67-D250-4839-B1BC-8BC781C10D33 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Greetings,

    Thanks to all who provided feedback on the 20190117 draft of = IPP Authentication Methods. Since I received valuable non-editorial = feedback in addition to editorial feedback on the draft from the PWG = Last Call, I have produced a new revision that hopefully resolves all = the issues and can be used in a second last call. The new draft is = here:

      =  https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt<= /a> 
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf<= /a> 

    I = included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it.

    Smith

    /**
        Smith = Kennedy
        HP Inc.
    */

    = --Apple-Mail=_F0797B67-D250-4839-B1BC-8BC781C10D33-- --Apple-Mail=_A8395E3E-5786-4A34-9530-ACD2F02A87B7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx9XukACgkQqskbKLDW 1N1NYA//fgoRyVLq4LrRF3VIhdGP3c7BfQOLEZssZgal+paSnzFAM/WDX02ebvAG ydBhY9XSaGvwtjBNVRHfbBSIXCDu3EiV4gak258wUIUUexYJ3y/fUumfib4FTqjA ut8F17bo+DDGLPm2GQ65duWrway9GM0Ks62A+8hfF9tqWIu05DhSY0UwxcnaJMju ZX2pKU7YXoX2/Fow2BMyKxHs1cnHsm0ep3J1lcKM3J7w7FHSu4SK8ZHOtq0hu+MN fG1GQnmqFlr+/SPoLCVyTwrVQFgB0DQJzoNOaHY6sMGF0j7O988HZXeY+uPZtzds dJEAsdZTdwC43gjK1nnuqXG1DV1rtkV+JFKfk37Uxxar4gI7dnfFmyFNNb6xGghu fJ2N8P/L+KCqPH+JohjRSsIFpYEVvjCmTU9RoQwV1eL8SytX6iEKB75ijlSKn9Sj lSHNF58H7r47FnXhPu3DtIgtWxoTlwRqX18TCB8mhnJlZUlqiThwuisbfX8vMCNK PqxEJrU7upBHKY1IhEkWtncrbz+jS3JnUWS0slEy2U2VNiRvaH8HBZurwzVq9Dy+ DraHrpwa3vR5/cyAHm+64Z2h5BRadXu8BwNT3M1BoCXBtIsJZhcfpyMGvKwVXSy/ 03sDJmKaL1NtJ4N81ydip4+Rjea3u1opa6hy/Mna57vkzrE6Pnw= =XFvW -----END PGP SIGNATURE----- --Apple-Mail=_A8395E3E-5786-4A34-9530-ACD2F02A87B7-- --===============6368614916521729699== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6368614916521729699==-- From ipp-bounces@pwg.org Mon Mar 4 09:43:56 2019 Return-Path: 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 A49201311AA for ; Mon, 4 Mar 2019 09:43:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 HH898t-LH93d for ; Mon, 4 Mar 2019 09:43:54 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id CD17813115B for ; Mon, 4 Mar 2019 09:43:54 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 52E6B3FCB; Mon, 4 Mar 2019 17:43:54 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 44AAD1C98; Mon, 4 Mar 2019 17:43:51 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 78A70315; Mon, 4 Mar 2019 17:43:49 +0000 (UTC) Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) by www.pwg.org (Postfix) with ESMTPS id 1B57F315 for ; Mon, 4 Mar 2019 17:43:49 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x24Hfs7e028034 for ; Mon, 4 Mar 2019 09:43:48 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=C/nX+AmAHDa3hPef94NZ81i4yPD3dDnypkH79nbY+co=; b=GCzGmUowI3bgL9e5Tic4dv4PjgGu5PHuCt+pamUXWTnoXaZtdXjsnRKR3uCyUfMSyOkk 7d5kEUzouq/RkH/+i0nVxPI8N45Tlk8i83tZVvKvkZDDGJLGZ9PCyyJ6/qr/uHG34ufw tBkgTK4148wwKeKjFnGXwMln7Xz5iO41jITaJpSIPiJxGcLv5MWjb9oLxEMYYB0Svev+ 4/lfc3xYsKLs0HsBf7N9A6kGFsJRBX3SE7FV4ICQgj5nJnok8tLsrpyz6WGkt6BVbTPc scDIGfCvaqbJCiH0kHqlLiPkmrYF+SSnmESfTBUsJS6J7BeanMpqamtIGK/jxza4sR8d tQ== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2qyq9srqew-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 04 Mar 2019 09:43:48 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNU00F2FRWT5X20@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Mon, 04 Mar 2019 09:43:47 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNU00700RSYMU00@nwk-mmpp-sz10.apple.com>; Mon, 04 Mar 2019 09:43:46 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: 21487fab9f27c70747bf06f8128b8d00 X-Va-R-CD: 99ada51efcfde35b7fc1ecce711e13c4 X-Va-CD: 0 X-Va-ID: 087ee97e-fdac-458a-9165-705f61475eff X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 21487fab9f27c70747bf06f8128b8d00 X-V-R-CD: 99ada51efcfde35b7fc1ecce711e13c4 X-V-CD: 0 X-V-ID: 1b9a18a5-71d2-4df5-a6bb-f59730ec35da X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_08:,, signatures=0 Received: from [17.235.3.21] by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNU00MQFRWVX480@nwk-mmpp-sz10.apple.com>; Mon, 04 Mar 2019 09:43:46 -0800 (PST) Date: Mon, 04 Mar 2019 12:43:42 -0500 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_08:, , signatures=0 Subject: [IPP] W3C Approves WebAuthn X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, Haven't had a chance to see if this could at all be used with IPP, but WebAuthn is a new standard for authenticating without traditional passwords: https://www.w3.org/2019/03/pressrelease-webauthn-rec.html https://www.w3.org/TR/webauthn/ See also the related FIDO2 project information: https://fidoalliance.org/fido2/ _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Mar 4 10:14:34 2019 Return-Path: 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 C2123130DEA for ; Mon, 4 Mar 2019 10:14:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 YJKeOlj0XcS7 for ; Mon, 4 Mar 2019 10:14:32 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 40DC6128B14 for ; Mon, 4 Mar 2019 10:14:32 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 9C7013F4B; Mon, 4 Mar 2019 18:14:31 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 89B2E2618; Mon, 4 Mar 2019 18:14:27 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A95C43F45; Mon, 4 Mar 2019 18:14:25 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id F378F1C98 for ; Mon, 4 Mar 2019 18:14:24 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x24I1dVm008323; Mon, 4 Mar 2019 10:14:21 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=/D5qdzIrl6QNqpPWcxdwllsim9Yd/X86Fvjv7Z/25vA=; b=l1wExS9vxa3YreYIldcIJwKyX9hOkUsDPLXKmWiDTpNmtpWiwnuDJ9dMt4k3t3xElQ22 DpeN6p6vzjgR1FlxohEUVmbPpb1ZvPEi5xiWB852Nw4xbbyhLIPtsd8hdJQXCyGpDJq6 X69FlGd2CWpz6EJGMxDnFCww6f89LNjOPl8SJmQNhIXBdJ01ZsQ3FZy3yVnQOOuLmO6S /ACo8/RtBwsKuG4ZpbUg+MLAZbsENzeVHZpld/m+33klJB1/wr0ytd0Bd1VsnCDVfM0R wZR1BFk/S+sf0t6F6tVJcKpnK0WLxJ0kdAS1OQZwpprIi8lNBpKY7sfch9kRJhDp5dgO sw== Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2qyscasa4w-14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 04 Mar 2019 10:14:21 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNU005PKTBQFY21@mr2-mtap-s03.rno.apple.com>; Mon, 04 Mar 2019 10:14:14 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNU00300SYR4Z00@nwk-mmpp-sz10.apple.com>; Mon, 04 Mar 2019 10:14:14 -0800 (PST) X-Va-A: X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-Va-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-Va-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-Va-CD: 0 X-Va-ID: b2cdefca-a7cb-4c0c-b71f-e9b7563a745f X-V-A: X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-V-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-V-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-V-CD: 0 X-V-ID: 32b19b82-67aa-468e-adaf-38e94962c49d X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_08:,, signatures=0 Received: from [17.235.3.21] by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNU00BIKTBN41A0@nwk-mmpp-sz10.apple.com>; Mon, 04 Mar 2019 10:14:13 -0800 (PST) In-reply-to: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> Date: Mon, 04 Mar 2019 13:14:11 -0500 Message-id: <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> To: "Kennedy, Smith (Wireless & Standards Architect)" X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_08:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============4162026187217977946==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4162026187217977946== Content-type: multipart/alternative; boundary="Boundary_(ID_ftxaCtYDOgsWfLkhAvxDcQ)" --Boundary_(ID_ftxaCtYDOgsWfLkhAvxDcQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Smith, > On Mar 4, 2019, at 12:22 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp wrote: > > Greetings, > > Thanks to all who provided feedback on the 20190117 draft of IPP Authentication Methods. Since I received valuable non-editorial feedback in addition to editorial feedback on the draft from the PWG Last Call, I have produced a new revision that hopefully resolves all the issues and can be used in a second last call. The new draft is here: > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf > > I included the contents of my LCRC document in the "Change History" section. If those that submitted comments could review this draft offline and evaluate whether my changes have fixed their issues, I'd appreciate it. The -rev version is (as usual) a bit hard to follow, but I like the changes. We normally do the LCRC comments in a separate txt file, but I'm fine with it being in the changes section for now. Process/3.0 doesn't require a particular format or filename, just that all comments and their resolutions be listed for review. Feedback: One addition I'd like to see to see for the "requesting-user-name" method is a note that some Clients use a constant identity as a privacy defense (e.g., "mobile" from iOS Clients) when sending requests, so from a Printer's perspective this method is basically useless. In the context of GDPR, this falls under a need for explicit consent - a password challenge or Client UI requesting permission to provide the real user name is required. At Apple we decided to always hide the requesting user on iOS for basic privacy reasons, relying on authentication where such information is genuinely needed. In the general client recommendations (section 14.2?), you say: Client security considerations (section 18.2) should also be followed. Since we have a lowercase "should" here, perhaps reword this as: Also see section 18.2 for Client security considerations and recommendations. There is a similar statement in the general printer recommendation (section 14.4?), which should probably read "Also see section 18.4 for Printer security considerations and recommendations." (right now it says Client...) _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_ftxaCtYDOgsWfLkhAvxDcQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Smith,

    On Mar 4, 2019, at 12:22 PM, = Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> = wrote:

    Greetings,

    Thanks to all who = provided feedback on the 20190117 draft of IPP Authentication Methods. = Since I received valuable non-editorial feedback in addition to = editorial feedback on the draft from the PWG Last Call, I have produced = a new revision that hopefully resolves all the issues and can be used in = a second last call. The new draft is here:

       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt<= /a> 
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf<= /a> 

    I = included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it.

    The -rev version is (as usual) a bit hard to follow, = but I like the changes.  We normally do the LCRC comments in a = separate txt file, but I'm fine with it being in the changes section for = now.  Process/3.0 doesn't require a particular format or filename, = just that all comments and their resolutions be listed for = review.

    Feedback:

    One addition I'd like to see to see for the = "requesting-user-name" method is a note that some Clients use a constant = identity as a privacy defense (e.g., "mobile" from iOS Clients) when = sending requests, so from a Printer's perspective this method is = basically useless.  In the context of GDPR, this falls under a need = for explicit consent - a password challenge or Client UI requesting = permission to provide the real user name is required.  At Apple we = decided to always hide the requesting user on iOS for basic privacy = reasons, relying on authentication where such information is genuinely = needed.

    In the = general client recommendations (section 14.2?), you say:

      =   Client security considerations (section 18.2) should also be = followed.

    Since = we have a lowercase "should" here, perhaps reword this as:

        Also see = section 18.2 for Client security considerations and recommendations.

    There is = a similar statement in the general printer recommendation (section = 14.4?), which should probably read "Also see section 18.4 for Printer = security considerations and recommendations." (right now it says = Client...)

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_ftxaCtYDOgsWfLkhAvxDcQ)-- --===============4162026187217977946== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4162026187217977946==-- From ipp-bounces@pwg.org Mon Mar 4 11:49:21 2019 Return-Path: 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 3A069128CF3 for ; Mon, 4 Mar 2019 11:49:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.281 X-Spam-Level: X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 xHSAqB-8o32g for ; Mon, 4 Mar 2019 11:49:18 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id AC624124D68 for ; Mon, 4 Mar 2019 11:49:18 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 08FF73F4E; Mon, 4 Mar 2019 19:49:18 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 265152618; Mon, 4 Mar 2019 19:49:12 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 888833F45; Mon, 4 Mar 2019 19:49:10 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id A5F1D1C98 for ; Mon, 4 Mar 2019 19:49:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551728947; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=a+dBWaqtE+GBFPMzsHsBa7QdKfoh7CxOOnPLQUfOzGA=; b=ChGEE4bNoE310K5DWOCBDnoSioWw1sA2T4qr9Ri3jSwdd6YUH7tZPSOfFh9qbVsHNG75tmTPYJspPfoHUXHCkZUlWez6slCOFIgghQ97TkWMQT6NYkcNPlZ5d3gfOWh4iYq7HcO7XTvA4lVIybCDLJdiaByy4LSXJRWJRHYKUUk= Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2050.outbound.protection.outlook.com [104.47.44.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-226-78KViuyrP-e1G9GwHs9bSw-1; Mon, 04 Mar 2019 14:49:05 -0500 X-MC-Unique: 78KViuyrP-e1G9GwHs9bSw-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0869.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Mon, 4 Mar 2019 19:49:04 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Mon, 4 Mar 2019 19:49:04 +0000 To: Michael Sweet Thread-Topic: [IPP] Updated stable draft of IPP Authentication Methods posted Thread-Index: AQHU0q7lBItiZ+reqEynp8Y9tft7qqX7xsSAgAAagYA= Date: Mon, 4 Mar 2019 19:49:04 +0000 Message-ID: References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> In-Reply-To: <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: fefbb016-035b-4f4a-0291-08d6a0da74cd x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0869; x-ms-traffictypediagnostic: CS1PR8401MB0869: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0869; 23:Xki/tpee70cq7WGTpvu3bQuRWLAYIQf95S/8GcU?= =?us-ascii?Q?swPnJ0qKK8UuYP5w9BrKQoufzVEp7oVzgSVZYOtoFof44xaeCXnpLdEg+tKR?= =?us-ascii?Q?3RnlAO+3ir7dCFuqIMHvlLYvhf3W/Kw7Wb06zuH8QoleaH3CciJTqLg6L6aa?= =?us-ascii?Q?3o2VJbEw8g+lNv4p6JEFWtTD5wQiv/AHrB8GDtu2/IBIfZZn4XfPN0dqc4W5?= =?us-ascii?Q?2RHLLWjEpdpwHQGhougSDK5hGPIOGYtUWSYkjq9L+uufAdU/BkcRH76CwVGk?= =?us-ascii?Q?41/0v6JSC2AlgzABiEsiZu3y+ojCS3utV6ROw2z/lxeiKhflBFBneNaxwbli?= =?us-ascii?Q?ggfj4sLhZAil/qrPfFZJrK+Fr/2KgEZ2TK/sujJC0zPV19DgjliN9piABkaY?= =?us-ascii?Q?Nn9wG9Y5YtdUdeGElxut7nuM6tedBip1axCr7rTCDmFpKIGVgtfHf15WrYcu?= =?us-ascii?Q?fowpsbTN4Mnc2ET0QBXvRNwT+PgEd2EA0mu94r8ml4/ZT4HvCm6vpfW8w9D2?= =?us-ascii?Q?hL1Mtqjs4CTDJUMwBYDIcqE12O7Atx6Cm2Nov8bhXXT7QMO/5uk9x7ibRepf?= =?us-ascii?Q?Aeb/Ml+8Yt9LeeA+zSiS2gCOHkHOi7ejFcjiU1vRhhwzrdIpCvltYVwVpqJJ?= =?us-ascii?Q?zSFG1OMT++mfrGREBGRrVNjbW0L47LBTJ/4fStvADUrz93QXDLhOUL9MO/DR?= =?us-ascii?Q?Iek7sjHZ92c3Uc71lr6tT0AVhu4miJn38ql2G8PxuznaNZF6L4lL15McUinB?= =?us-ascii?Q?tw2JuEeOOFFcho7gACyaiNczj+dpuRelEYVOAyrhVGCZLeKSilhSJguPOoI3?= =?us-ascii?Q?qbiWJ3V/Q9dAF/PJkGXl9HCiEPrlowA/cvv/5qMqIdMekabQVhx6hQQbBxCN?= =?us-ascii?Q?ka2txNdIRZpZm6NsCKgL2tCCwbpD8FScxeh/gqJpq0QcMI/sP7sToTxZSHGR?= =?us-ascii?Q?S+JFrR3e2BfV5F3EfwuP0IFm/lXRZl4JExQZQv71R76b3F63cee9WLA1KBRc?= =?us-ascii?Q?PzRuvgCgKYp2/ZOm0nUXW7mzqoZyQewYyz0yViREvFTIWcUdcPWnGZuDIAcZ?= =?us-ascii?Q?1K57p+B6E4zIlpUQIgtdD1sSJljWBklOic5DCDvtb0kAkOOln8P0/4IAeoBQ?= =?us-ascii?Q?VKW8+krIJh9WI7ZsJbZI2j0QWYK+251wRk19MNTBcKA6WBSS8CGcTi0oFcwr?= =?us-ascii?Q?jsqFUUyc88Lt+2WpLQRiwYAJSu8Q6mu54vojP/4e4yQPJcI5M09sj1sfRUOa?= =?us-ascii?Q?QsrDSB4bRelj0vDnBY3FjkM+yWmeCovRd+bkQIAD25P9us/66dE8SiCGxZvU?= =?us-ascii?Q?ZY4XAFhFcu42Bt3ZSTKQRzhVVgJR/49bpsOOvXfvia0uBwAYa7wNKqwTV/w0?= =?us-ascii?Q?MUoJ1VYuUXJILsJXIKB+mc1do3qE7UsUz1214os6zRspIoljE?= x-microsoft-antispam-prvs: x-forefront-prvs: 09669DB681 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(396003)(366004)(346002)(376002)(54164003)(6602003)(199004)(189003)(66066001)(68736007)(6506007)(6512007)(4326008)(236005)(446003)(53936002)(11346002)(2906002)(106356001)(54896002)(6306002)(229853002)(25786009)(316002)(82746002)(8936002)(99286004)(15650500001)(81166006)(81156014)(105586002)(33656002)(53546011)(8676002)(6246003)(36756003)(476003)(97736004)(2616005)(6436002)(6916009)(606006)(76176011)(6486002)(486006)(102836004)(14444005)(83716004)(7736002)(99936001)(6116002)(186003)(3846002)(256004)(14454004)(71200400001)(71190400001)(26005)(86362001)(478600001)(966005)(5660300002); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0869; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: hscphiDR82QOS5kP5xU9FmOA7HpCjdOcbwEpCRB999ULsABria+GxOknulUvMLaKb2TF7hYiloPxrUdcv5f9lYEJBy5Mam73dYrww6wTL3nAkn+MZ4Cg86tremjYuO5ihWSu2t9jpPnDYW3EpY6CbDh0TvWgypFW/Q6bx/l4RSsXWvb8qooIJ47J9mEcHoQPnFgw9FgAPDMbeKD8v+UBvxeKqa7YimmDu3gKo8jpxWz+ibHeqKK6dN5jI3U4qDka99gu2qGJ63A4Ecfw8KwSrO0UVwSPc70V4E21WYYc63hiBPGe8yjkFNbN6jQZwoqDqNQ4f2QYmcEg/sTTohNnj3y0zv36ngvqBexDG0JUvu/EpHujkDPXAHZ94W0HgpsLrJzvu3HGPPuHGoWCejGKJOKNmm6CCNkfPmAqCTg8iMo= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: fefbb016-035b-4f4a-0291-08d6a0da74cd X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2019 19:49:04.2030 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0869 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8559223361554995123==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8559223361554995123== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_6BB692D0-01EB-45DE-947B-A7A33A19346F"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_6BB692D0-01EB-45DE-947B-A7A33A19346F Content-Type: multipart/alternative; boundary="Apple-Mail=_E301C985-14EF-4FBB-A5F7-A6CA165C2663" --Apple-Mail=_E301C985-14EF-4FBB-A5F7-A6CA165C2663 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 4, 2019, at 11:14 AM, Michael Sweet wrote: >=20 > Smith, >=20 >> On Mar 4, 2019, at 12:22 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >>=20 >> Greetings, >>=20 >> Thanks to all who provided feedback on the 20190117 draft of IPP = Authentication Methods. Since I received valuable non-editorial feedback = in addition to editorial feedback on the draft from the PWG Last Call, I = have produced a new revision that hopefully resolves all the issues and = can be used in a second last call. The new draft is here: >>=20 >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt = >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf = >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt = >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf = >>=20 >> I included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it. >=20 >=20 > The -rev version is (as usual) a bit hard to follow, but I like the = changes. Totally agree! https://bugs.documentfoundation.org/show_bug.cgi?id=3D123848 = > We normally do the LCRC comments in a separate txt file, but I'm fine = with it being in the changes section for now. Process/3.0 doesn't = require a particular format or filename, just that all comments and = their resolutions be listed for review. >=20 > Feedback: >=20 > One addition I'd like to see to see for the "requesting-user-name" = method is a note that some Clients use a constant identity as a privacy = defense (e.g., "mobile" from iOS Clients) when sending requests, so from = a Printer's perspective this method is basically useless. In the = context of GDPR, this falls under a need for explicit consent - a = password challenge or Client UI requesting permission to provide the = real user name is required. At Apple we decided to always hide the = requesting user on iOS for basic privacy reasons, relying on = authentication where such information is genuinely needed. Do you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. "Client = Security Considerations"? There seems to be two different statements: = what is done in the field, and what a Client or Printer ought to do. >=20 > In the general client recommendations (section 14.2?), you say: >=20 > Client security considerations (section 18.2) should also be = followed. >=20 > Since we have a lowercase "should" here, perhaps reword this as: >=20 > Also see section 18.2 for Client security considerations and = recommendations. OK. Will fix that now and re-post once I am clear about what to do about = the "anonymized 'requesting-user-name'" issue above and where it should = live. >=20 > There is a similar statement in the general printer recommendation = (section 14.4?), which should probably read "Also see section 18.4 for = Printer security considerations and recommendations." (right now it says = Client...) Will fix that one too. >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer --Apple-Mail=_E301C985-14EF-4FBB-A5F7-A6CA165C2663 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

    On Mar 4, 2019, at 11:14 AM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    On Mar 4, 2019, at 12:22 PM, Kennedy, Smith (Wireless & = Standards Architect) via ipp <ipp@pwg.org> wrote:

    Greetings,

    Thanks to all who provided feedback on the 20190117 draft of = IPP Authentication Methods. Since I received valuable non-editorial = feedback in addition to editorial feedback on the draft from the PWG = Last Call, I have produced a new revision that hopefully resolves all = the issues and can be used in a second last call. The new draft is = here:

      =  https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt<= /a> 
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf<= /a> 

    I = included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it.

    The -rev version is (as usual) a bit hard to follow, = but I like the changes.




     We normally do the LCRC comments in a = separate txt file, but I'm fine with it being in the changes section for = now.  Process/3.0 doesn't require a particular format or filename, = just that all comments and their resolutions be listed for = review.

    Feedback:

    One addition I'd = like to see to see for the "requesting-user-name" method is a note that = some Clients use a constant identity as a privacy defense (e.g., = "mobile" from iOS Clients) when sending requests, so from a Printer's = perspective this method is basically useless.  In the context of = GDPR, this falls under a need for explicit consent - a password = challenge or Client UI requesting permission to provide the real user = name is required.  At Apple we decided to always hide the = requesting user on iOS for basic privacy reasons, relying on = authentication where such information is genuinely = needed.

    Do you want = this in section 4.2 "The 'requesting-user-name' IPP Authentication = Method" (using numbering from the non-rev documents), or in 5.1.1. = "General Recommendations" (for Clients), or 7.2. "Client Security = Considerations"? There seems to be two different statements: what is = done in the field, and what a Client or Printer ought to = do.

    = --Apple-Mail=_E301C985-14EF-4FBB-A5F7-A6CA165C2663-- --Apple-Mail=_6BB692D0-01EB-45DE-947B-A7A33A19346F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx9gS8ACgkQqskbKLDW 1N1kLA//VMcZQFVBNxNc5RajHjVBkpB0qubcldZE/5tShqAzugkhQSgPPzrpuWBc YUHtu5BekUVaWQLADO1d6q1cwBVEmnRh/u31w31XpMEs06bpcMwOOz59+uTrXHtT jzqnCdVS9V4vIu0lXQze7d8gy5uZZ9bIGPuG6ipfFDgmSWnzzT1BnM305o1Z46Qa w71k7BTcZuUmPtr4unbJg7cL46/K1/P8lNbIhoB8gI4oz8FjYWEv3tynigWX5INK NNX+kK7w0eCW+avJBvG1LbuIQQGmFKMTPawXZYKMk8cPWpLiKH/wocav5qLY4Fyv J/5ztNelYl7BLTnoCxazIJhyjxI34SRSZiT6Gd6h9wb2R7pAhWA69cDe/rkYk9Bp 6VbcUhh67yif5JpiKE3Hq16B//Dszj0YluLpCs6fV1XphGtj2Qj1apePTFWd6Wey VCfkmaqk9TMHw9rYbEHxfkG67u4fPa7vVhjtoaXEUNDBxljVckrszgMJ6+w4p/5E MHloht8kovzIflZDi4/+yaZ+HKaEY3rFY8tQbv/S6j6CFNw6UWzrk9KjxgijEqSc V6m1NqRD1tDL39kOhetaO16fDGK7amqso/DfY2BPBTM+rk2uKzbZUuxqwk2sMm8R JJgVf9wE2OoaMMYmXfX3ClZJtP+lmi7agucZ7nrVg7F1ncHqHjc= =EAll -----END PGP SIGNATURE----- --Apple-Mail=_6BB692D0-01EB-45DE-947B-A7A33A19346F-- --===============8559223361554995123== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8559223361554995123==-- From ipp-bounces@pwg.org Mon Mar 4 12:27:03 2019 Return-Path: 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 1EE28130F96 for ; Mon, 4 Mar 2019 12:27:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=chromium.org 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 qzJ77q4HUvYb for ; Mon, 4 Mar 2019 12:27:01 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5CC12D4ED for ; Mon, 4 Mar 2019 12:27:01 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 453D53F9C; Mon, 4 Mar 2019 20:27:00 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id D55F72618; Mon, 4 Mar 2019 20:26:57 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 2FFC4315; Mon, 4 Mar 2019 20:26:56 +0000 (UTC) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) by www.pwg.org (Postfix) with ESMTPS id 6F13B315 for ; Mon, 4 Mar 2019 20:26:55 +0000 (UTC) Received: by mail-io1-xd2b.google.com with SMTP id k21so5034945ior.13 for ; Mon, 04 Mar 2019 12:26:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=4onOxTZsmnBlabI8S2+liZJI26r5kCZj+Nvy31MUIZQ=; b=eZjkHWrh+kdUd8M55yTAGmn+tfHQ+LjzKJR2VUukRc4VpkwtCYuxbxwsft6wwOyf7j rAJVl8JeJR6w07H/hV88rYeG7/3tlBnQIV9z4U//r9kaIisPN/MBekb2F5XOY0UtA2V4 xISdRbeXRnDbe/gcvSF5mX4fvKtz/lBDIvH/o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4onOxTZsmnBlabI8S2+liZJI26r5kCZj+Nvy31MUIZQ=; b=C11BykA76izuDYwBSgcJ7pLvFdLBWESYDDZsHoa/PURyAUnz28T2aHyTEhPb/D/irP 1uqvf841wMsbbmOvbifQq7zuDbZjdOEeY/fHDQnxG0tpNvm/M7ubucS3p/PPL9KCuR39 CWYDviAqyYeZpu1hoGD7rSDs69g67bjDXoDX+tw/JpL0NtW5Dy/+QJhd1IhT8vjbMYSW H1uIO68pl3adBsDNC5sdZr+8kwB/lpYPQzjcAVIGDRPkeci09u6yAxHuXnUvf4KZ7Mbm 7llhjFNc/vs4Vn+1IZjwi6F4feC87RIlQFusNwMAcjUzxn7HJm+vYcQ03x/6zuB/QJ72 tMEg== X-Gm-Message-State: APjAAAU8nE7Ge9kyOOj1Vss7x1CY3YufJmeFk/q52WzcdKxurT0o/BpS ANRdWumXyyNc2xBhY6sTigljcwZu2X5SmJVzDQ/Xap8GUsI= X-Google-Smtp-Source: APXvYqwZawUZi/LZMbmw6MOeRPeTU4HEIIoKc649rdslGBzlbKisdi0FG1XivC3HxdMkKKzgUWioeEZ7nKiiU0bcbU8= X-Received: by 2002:a6b:f60e:: with SMTP id n14mr11902ioh.289.1551731214226; Mon, 04 Mar 2019 12:26:54 -0800 (PST) MIME-Version: 1.0 Date: Mon, 4 Mar 2019 12:26:43 -0800 Message-ID: To: ipp@pwg.org Subject: [IPP] IPP Everywhere PWG-Raster AND PDF Requirement X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Sean Kau via ipp Reply-To: Sean Kau Content-Type: multipart/mixed; boundary="===============6553976323297558115==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6553976323297558115== Content-Type: multipart/alternative; boundary="000000000000cfb1d605834a9324" --000000000000cfb1d605834a9324 Content-Type: text/plain; charset="UTF-8" Question about the IPP Everywhere specification: Why do we require that printers support PWG-Raster if it can accept PDF? Is this to improve compatibility with clients? I tried to look through the archives and couldn't find any commentary. -- Sean Kau --000000000000cfb1d605834a9324 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Question about the IPP Everywhere specification:

    <= /div>
    Why do we require that printers support PWG-Raster if it can acce= pt PDF?=C2=A0 Is this to improve compatibility with clients?=C2=A0 I tried = to look through the archives and couldn't find any commentary.

    --
    Sean Kau
    --000000000000cfb1d605834a9324-- --===============6553976323297558115== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6553976323297558115==-- From ipp-bounces@pwg.org Mon Mar 4 12:51:14 2019 Return-Path: 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 0E9221294FA for ; Mon, 4 Mar 2019 12:51:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 VymJc_XVF7uk for ; Mon, 4 Mar 2019 12:51:12 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id EAD2612D4ED for ; Mon, 4 Mar 2019 12:51:11 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 796533F9B; Mon, 4 Mar 2019 20:51:11 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 7FDB22618; Mon, 4 Mar 2019 20:51:08 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 21EDA3F45; Mon, 4 Mar 2019 20:51:07 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id C63DB1C98 for ; Mon, 4 Mar 2019 20:51:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551732663; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=M7pORvZWf2rCNoqXSEF4OQLcXrXNy9jY2H3iVv85/Ds=; b=hZsw3sxJba356ADJ6ayUN1c0l37uERnu7605s2itxAQePpL6vI/jJCuX2ucrp6QAkM63+mc9YplvKzQrSKSlbWzJlnxZnKwNUgXbJcGFupEF1YbXClzbnkXGInXmX2lKnW0JJ+/v7CQNm0XxhEQS34LuNXfnYExzzTaceaBVmAg= Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-bn3nam04lp2059.outbound.protection.outlook.com [104.47.46.59]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-267-iKBhIUq7OhGwmY5G1bINdg-1; Mon, 04 Mar 2019 15:51:02 -0500 X-MC-Unique: iKBhIUq7OhGwmY5G1bINdg-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0518.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Mon, 4 Mar 2019 20:51:01 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Mon, 4 Mar 2019 20:51:01 +0000 To: Sean Kau Thread-Topic: [IPP] IPP Everywhere PWG-Raster AND PDF Requirement Thread-Index: AQHU0sizziZHw324WkaQ8uOPCZ6b46X78l+A Date: Mon, 4 Mar 2019 20:51:01 +0000 Message-ID: <188BC820-B4B4-49EA-946A-AE336B413F9E@hp.com> References: In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e51c562d-5382-4714-eeef-08d6a0e31c37 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0518; x-ms-traffictypediagnostic: CS1PR8401MB0518: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0518; 23:NXqBr3BHz3JSUJbkHSs04HiM2I7oWPGzzrHCfqb?= =?us-ascii?Q?6jdxybmgTj89EMtgQurHvLgwdMeyHSyTZK3MdduZWgrEjBmaAdY6oXoRZenG?= =?us-ascii?Q?fcFIWD1lOlfWg0Olyjb1k2ayXaxYnkda2d6AJbuiiwN2eqx7CPrLiVSnqwYR?= =?us-ascii?Q?sipdZdLdjhrvLiO0gXKlfdE8vV2c7e2EzWfcMBg2KWhE0D7A5RYA+t9xPkRJ?= =?us-ascii?Q?ooQWNdxL6EGriniIBM5Pqnkq4Dz/12k3C4uWwaW+Heo6lg7JhZO8HXOfJPUx?= =?us-ascii?Q?Hp9SUyJ+VK7WN4WrNRcAS+FrDAUvJPdeCmZux+1MZgIVcxbtQy0LSSZ4Uamf?= =?us-ascii?Q?qOIjWXZ3t8p4Tmx4katdBEwWc9Eys+I+S8JzXt4nIDOWL0OJGMvH2IcAhSrj?= =?us-ascii?Q?QeeXn9QKoRzEXkNPVjIgQPrq9/g/HxnwqMtygo0AAarw5pKRa2hxdUo/x/fi?= =?us-ascii?Q?uGzHBsjk/nKGCtYJoz4gdkzydysXPYnKPDoBjEZcNDTWBP6T36hzu65dXUO+?= =?us-ascii?Q?nioKBtV5FidGaq66p2Tqe1Toq3TpvXkFR3oqRDwJfr2gVvYtiImOENfw6PFa?= =?us-ascii?Q?hgKTgjBksEM6epuZ2ql954CQfK6oDLuA35lYEWNrywmm8lb4y36TTV0EUe42?= =?us-ascii?Q?V86+JUeuM+ALbzh54c5FwdMzQBep3X4u+IOT/cptPydE2JfaP//JpwPUmCgq?= =?us-ascii?Q?a+a8r344K2ldTChSrh2vj0WGKdFKVT2x4xgF/l0CMMDxd+QjiiDzAkL0Glpl?= =?us-ascii?Q?Bnhau7DX/omY+05ettf5H9gWVg/shtNjdEQ0ZxqvpY5mnLBUVhdyMD3uZGEb?= =?us-ascii?Q?9f4XpylaUtAG3wDO0isaeQbdVmuFhmrgu/X+V4PNopGT8qSZ9hd5Mc8wfBBY?= =?us-ascii?Q?i6ktBJ4ZT3UH2ZSkLEUs4mulGhfJcR1C9Ijfu/y3fTXBoT0+iQ5bNJdge22m?= =?us-ascii?Q?FwBViqJCiqAoP+u+s0kVcWBM9r7X63Br3ODeH2jykj7MLFDWWp1niZ5rIGW3?= =?us-ascii?Q?ieApjb75aZ1PhTXKSASAlwLyWtY8LaURkdzI6Zk7RkzT0FXy0nDsbNKRCo0b?= =?us-ascii?Q?Qp9dhNWBNwcJBLH3d0f9k/Ns413+ytDRByc77ms1h4epMuoJjClrRah92/4Q?= =?us-ascii?Q?laH2NFC9DIgmhlhOrUKc6JgNSzy8DvJviySyH55tj6nyVoIs7BMyySpp0krg?= =?us-ascii?Q?mew1XRWAovBQ5eldsvczIYIWS4mZcpfilvf9MtC+CcelVyPyjKU6lIfAIzdZ?= =?us-ascii?Q?iIaMoP3hbVdV+vDVrWmZUKdUfDVKi9HZUy6FPFQdZgVqfdnIms/4PBkxLgVE?= =?us-ascii?Q?ObZ22Huehqyrvm6ryQfeW+qhlpvkTuMO4b7kkrL5szDvvoZobcdJzkqcTcMT?= =?us-ascii?Q?WPOR7YMyDsFd9lwEQLafsqP+rUV61hw1Ct7SE8WL+gKnkwuWqsJvMuUrkw0+?= =?us-ascii?Q?3LcsW0LYDTw=3D=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09669DB681 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(346002)(376002)(136003)(396003)(39860400002)(366004)(189003)(199004)(6602003)(71190400001)(4744005)(76176011)(966005)(71200400001)(305945005)(26005)(6916009)(8936002)(105586002)(25786009)(86362001)(486006)(5660300002)(316002)(478600001)(83716004)(14454004)(99286004)(256004)(53936002)(6506007)(3846002)(446003)(229853002)(11346002)(6116002)(33656002)(82746002)(102836004)(2616005)(476003)(6436002)(2906002)(66066001)(106356001)(6486002)(186003)(36756003)(4326008)(81156014)(6306002)(81166006)(68736007)(8676002)(6246003)(99936001)(6512007)(97736004)(7736002)(53546011)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0518; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: S7GLPrHkajmbGjaAJr3V732z+HCI34Q8yDUM0oK5VHxxf2TlRrhjSBUFz9GEgSmhSi29n1A0FfqYYOFn66IShWVVxBpNrR0z4vegGJotZJUNIgkNaFBIATcWfwSUgLx+GNxfDPFqYkTZ/gr69kQqkXDICkrj8COzWkS312nisk7/J6LZbEcwQp916EubU1qb73pm3/kuRpEU2ECekddowQTMPCrz9f5vsd39+tZVGoDlFZxD3fTI3gHfQrEiiDghUgLgu0icrFx7QaEtXsyjAIeORoM7bC0sSULGyh66gan26EbgnGS0hyL9IDtvltuwONbZo++WcvVdus8P2V9AEIHQgbMfEqFXM4675vjb1WuzKb287sPrHoGdL2LlQnTY+0ldG9D1vv6LdHfDQka+a2bRGW5eI87UVMoMH5XEtiY= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: e51c562d-5382-4714-eeef-08d6a0e31c37 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2019 20:51:01.0601 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0518 Cc: "ipp@pwg.org" Subject: Re: [IPP] IPP Everywhere PWG-Raster AND PDF Requirement X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8341619857056813897==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8341619857056813897== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_002D02E2-5C59-4063-A41C-D17605071509"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_002D02E2-5C59-4063-A41C-D17605071509 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Good question, Sean. The reason for this is to set a baseline for = interoperability. Some clients may not support PDF. So all Clients and = Printers are required to support PWG Raster as a bare minimum. That way, = there will always be some common document format that both can fall back = to. Smith > On Mar 4, 2019, at 1:26 PM, Sean Kau via ipp wrote: >=20 > Question about the IPP Everywhere specification: >=20 > Why do we require that printers support PWG-Raster if it can accept = PDF? Is this to improve compatibility with clients? I tried to look = through the archives and couldn't find any commentary. >=20 > -- > Sean Kau > _______________________________________________ > ipp mailing list > ipp@pwg.org > = https://protect-us.mimecast.com/s/OLVKCXDwEwTKJv3Bh6nyay?domain=3Dpwg.org --Apple-Mail=_002D02E2-5C59-4063-A41C-D17605071509 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx9j7MACgkQqskbKLDW 1N1aOw//SQ/cH30t/zyaISysBApvaK3UwhHB9xQQ5AB1aLkZ0ii7qoRvYZU0zBsB 8Wfr6tm570Vjeehh5B0oo0GJIlfWUFcIS/sAggu7T/A+TiEBUwZBH5YugjprbfLp Pxkgt4vk8Ys9kgx/m2SFZ8Nl5ND04swcct0B/HVkTW3g+gJVvp6uGv51bxzZA0Gb C2w6c4LDLdKYVTy4mrECKD0yeQ0nmanTzKH12uLIVsAkFPRlOLWtbBeCs0uDnvuG UZLmk4i5l0sZMofyQu/Fj8yV83WgWLIp4SJ2/iZymkZOnzdg6xCZkheWF7ssfeX/ NOOC6WIbWXE1mfCYZL8qtooH8Ef7MVWJOM9tzaDqA372wq7lICxt+POOq+ySJpAq F9PlKgZWJbaarwzaLGYkGLN85jREbuDTK/vUlP26FJTo0EYSW9B75iSyQzOY0GLW lAgK/R5lhzTD4lfYjJpvTblmFdePLUPy05tZ8VnTmztMvPkxQ50/aCrueJAWoJr8 PULH3tDVHNZ9BNPqPjrU7YPY2KZAkEy2hS9paujSZljYQPcD6pizrIqxH92FjTQ5 PCiWuhgvzesBGOSgdOe39NWvFdo4kBcvdIl6KDbDoXyuGgVx0SDbCKGNzjY4uM0m 45XLfVPPyQeojAkoOLU0mQn8Tt/PIjhRPvYbxjdwZbAoXjbRohA= =gle1 -----END PGP SIGNATURE----- --Apple-Mail=_002D02E2-5C59-4063-A41C-D17605071509-- --===============8341619857056813897== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8341619857056813897==-- From ipp-bounces@pwg.org Mon Mar 4 13:10:41 2019 Return-Path: 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 92B4B1294FA for ; Mon, 4 Mar 2019 13:10:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.282 X-Spam-Level: X-Spam-Status: No, score=-0.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 trQFzpdQWpbY for ; Mon, 4 Mar 2019 13:10:39 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8E612008A for ; Mon, 4 Mar 2019 13:10:38 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 26D8A3F51; Mon, 4 Mar 2019 21:10:38 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 93D8124D3; Mon, 4 Mar 2019 21:10:31 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 4F1A53F45; Mon, 4 Mar 2019 21:10:30 +0000 (UTC) Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) by www.pwg.org (Postfix) with ESMTPS id 55DFF24D3 for ; Mon, 4 Mar 2019 21:10:29 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x24L6apZ043470; Mon, 4 Mar 2019 13:10:27 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=n0TAN3AEubonFEHEV5ckSphnWKB7PYHO582vhPspeJw=; b=FX8h0BKZ/FPuZXswF11hg4OxuhVCYlOCvZiqsYQ3RKpY3erO/qlXNqP3mp1bXjb0g1tp w80LL120RcnYKIjas5aFfE1z8vLjZhkoNWosZG9zIo6/UpGTuD3Kh2011cj3EJt7QdLN BfgUNXNXXLmrGkxli26KSsOYHPOsOa66RiGBJa9jU1uhe1yzlElPWiuD+YcsCCPVF+vo 8xUpRUgNVohOG4lvdFv3x0PSHP7cxKHZv0mSNBfEzuynun4HAU3HspWseodSdxZcanIF OuzXXVd1JKJmUx+8gt+fPE/JsSAUBnVkSEyoXCFySoBW4iu8Hg+iVGkM6hr3PeezwkXT OQ== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2qyq9sv9q4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 04 Mar 2019 13:10:27 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNV003SW1HEI000@mr2-mtap-s01.rno.apple.com>; Mon, 04 Mar 2019 13:10:27 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNV009000MPPM00@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 13:10:26 -0800 (PST) X-Va-A: X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-Va-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-Va-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-Va-CD: 0 X-Va-ID: a587556e-e2cf-4bdc-931a-a4bce6ded07b X-V-A: X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-V-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-V-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-V-CD: 0 X-V-ID: b13a080b-14a9-4557-9082-0c60a5760690 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_11:,, signatures=0 Received: from [17.235.3.21] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNV004BH1H9LF80@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 13:10:23 -0800 (PST) In-reply-to: Date: Mon, 04 Mar 2019 16:10:21 -0500 Message-id: <46698615-D1A6-413D-9E83-9B38ED84A89B@apple.com> References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> To: "Kennedy, Smith (Wireless & Standards Architect)" X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_11:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============6484670792595682584==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6484670792595682584== Content-type: multipart/alternative; boundary="Boundary_(ID_YqHDoHSYNOFal1Cdt9PsXQ)" --Boundary_(ID_YqHDoHSYNOFal1Cdt9PsXQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Smith, > On Mar 4, 2019, at 2:49 PM, Kennedy, Smith (Wireless & Standards Architect) wrote: > > > >> On Mar 4, 2019, at 11:14 AM, Michael Sweet > wrote: >> >> Smith, >> >>> On Mar 4, 2019, at 12:22 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp > wrote: >>> >>> Greetings, >>> >>> Thanks to all who provided feedback on the 20190117 draft of IPP Authentication Methods. Since I received valuable non-editorial feedback in addition to editorial feedback on the draft from the PWG Last Call, I have produced a new revision that hopefully resolves all the issues and can be used in a second last call. The new draft is here: >>> >>> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt >>> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf >>> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt >>> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf >>> >>> I included the contents of my LCRC document in the "Change History" section. If those that submitted comments could review this draft offline and evaluate whether my changes have fixed their issues, I'd appreciate it. >> >> >> The -rev version is (as usual) a bit hard to follow, but I like the changes. > > Totally agree! > > https://bugs.documentfoundation.org/show_bug.cgi?id=123848 > > >> We normally do the LCRC comments in a separate txt file, but I'm fine with it being in the changes section for now. Process/3.0 doesn't require a particular format or filename, just that all comments and their resolutions be listed for review. >> >> Feedback: >> >> One addition I'd like to see to see for the "requesting-user-name" method is a note that some Clients use a constant identity as a privacy defense (e.g., "mobile" from iOS Clients) when sending requests, so from a Printer's perspective this method is basically useless. In the context of GDPR, this falls under a need for explicit consent - a password challenge or Client UI requesting permission to provide the real user name is required. At Apple we decided to always hide the requesting user on iOS for basic privacy reasons, relying on authentication where such information is genuinely needed. > > Do you want this in section 4.2 "The 'requesting-user-name' IPP Authentication Method" (using numbering from the non-rev documents), or in 5.1.1. "General Recommendations" (for Clients), or 7.2. "Client Security Considerations"? There seems to be two different statements: what is done in the field, and what a Client or Printer ought to do. I was thinking of this being in section 4.2. As far as the general recommendations for clients, I think we need to make a note of privacy concerns, .i.e., recommend that Clients don't just throw the current username in there without getting explicit permission from the User. >> In the general client recommendations (section 14.2?), you say: >> >> Client security considerations (section 18.2) should also be followed. >> >> Since we have a lowercase "should" here, perhaps reword this as: >> >> Also see section 18.2 for Client security considerations and recommendations. > > OK. Will fix that now and re-post once I am clear about what to do about the "anonymized 'requesting-user-name'" issue above and where it should live. > >> >> There is a similar statement in the general printer recommendation (section 14.4?), which should probably read "Also see section 18.4 for Printer security considerations and recommendations." (right now it says Client...) > > Will fix that one too. > >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_YqHDoHSYNOFal1Cdt9PsXQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Smith,

    On Mar 4, 2019, at 2:49 PM, = Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:



    On Mar = 4, 2019, at 11:14 AM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    On Mar 4, 2019, at 12:22 PM, Kennedy, Smith = (Wireless & Standards Architect) via ipp <ipp@pwg.org> = wrote:

    Greetings,

    Thanks to all who provided feedback on = the 20190117 draft of IPP Authentication Methods. Since I received = valuable non-editorial feedback in addition to editorial feedback on the = draft from the PWG Last Call, I have produced a new revision that = hopefully resolves all the issues and can be used in a second last call. = The new draft is here:

       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.odt&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304.pdf&= nbsp;
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.odt<= /a> 
       https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf<= /a> 

    I = included the contents of my LCRC document in the "Change History" = section. If those that submitted comments could review this draft = offline and evaluate whether my changes have fixed their issues, I'd = appreciate it.

    The -rev version is (as usual) a bit hard to follow, = but I like the changes.

    Totally agree!

    https://bugs.documentfoundation.org/show_bug.cgi?id=3D123848


     We = normally do the LCRC comments in a separate txt file, but I'm fine with = it being in the changes section for now.  Process/3.0 doesn't = require a particular format or filename, just that all comments and = their resolutions be listed for review.

    Feedback:

    One addition I'd like to see to see for the = "requesting-user-name" method is a note that some Clients use a constant = identity as a privacy defense (e.g., "mobile" from iOS Clients) when = sending requests, so from a Printer's perspective this method is = basically useless.  In the context of GDPR, this falls under a need = for explicit consent - a password challenge or Client UI requesting = permission to provide the real user name is required.  At Apple we = decided to always hide the requesting user on iOS for basic privacy = reasons, relying on authentication where such information is genuinely = needed.

    Do = you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. = "Client Security Considerations"? There seems to be two different = statements: what is done in the field, and what a Client or Printer = ought to do.

    I was = thinking of this being in section 4.2.  As far as the general = recommendations for clients, I think we need to make a note of privacy = concerns, .i.e., recommend that Clients don't just throw the current = username in there without getting explicit permission from the = User.

    In the general client recommendations (section = 14.2?), you say:

      =   Client security considerations (section 18.2) should also be = followed.

    Since we have a = lowercase "should" here, perhaps reword this as:

        Also see section 18.2 for Client = security considerations and recommendations.

    OK. Will fix that now and re-post once I am clear about = what to do about the "anonymized 'requesting-user-name'" issue above and = where it should live.


    There is a similar = statement in the general printer recommendation (section 14.4?), which = should probably read "Also see section 18.4 for Printer security = considerations and recommendations." (right now it says = Client...)

    Will fix that one too.


    ______________________________________________________= ___
    Michael Sweet, Senior Printing = System Engineer

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_YqHDoHSYNOFal1Cdt9PsXQ)-- --===============6484670792595682584== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6484670792595682584==-- From ipp-bounces@pwg.org Mon Mar 4 13:25:35 2019 Return-Path: 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 B8A29130EA8 for ; Mon, 4 Mar 2019 13:25:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 Y4jdoZ6Xn1u5 for ; Mon, 4 Mar 2019 13:25:33 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 43A6F12008A for ; Mon, 4 Mar 2019 13:25:33 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id CB88C3F9B; Mon, 4 Mar 2019 21:25:32 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 22EAD2618; Mon, 4 Mar 2019 21:25:28 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 9401B3F45; Mon, 4 Mar 2019 21:25:26 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id A5D581C98 for ; Mon, 4 Mar 2019 21:25:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551734723; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YVbUcygxrUpQRFp7w21TXPW6c5/kZJ5vBfvehMwZHdc=; b=YeuiLLzjBEPBEutJTZvAZQgOTdh66hqloF3L8LA4LPLyG6aDz9kCTYCzrSrSS2XrHzUBMd91lx+HrR/aXqxwm6AGT8VSCSZmaKR57dh1cG6dIXEaS3OQKM9bZSkzzmT2vL0mwumX9gGHz0qcJPqllNKx07gTNc6xIdkl4QBrPZA= Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01lp2056.outbound.protection.outlook.com [104.47.32.56]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-128-IZvEwTPDMNGMj1q5eBMINw-1; Mon, 04 Mar 2019 16:25:22 -0500 X-MC-Unique: IZvEwTPDMNGMj1q5eBMINw-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0950.NAMPRD84.PROD.OUTLOOK.COM (10.169.14.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.15; Mon, 4 Mar 2019 21:25:20 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Mon, 4 Mar 2019 21:25:20 +0000 To: Michael Sweet Thread-Topic: [IPP] Updated stable draft of IPP Authentication Methods posted Thread-Index: AQHU0q7lBItiZ+reqEynp8Y9tft7qqX7xsSAgAAagYCAABa3gIAABC0A Date: Mon, 4 Mar 2019 21:25:20 +0000 Message-ID: <8FF54F79-03FE-469B-8102-04790B0AB755@hp.com> References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> <46698615-D1A6-413D-9E83-9B38ED84A89B@apple.com> In-Reply-To: <46698615-D1A6-413D-9E83-9B38ED84A89B@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d2b66a48-41ee-4af7-60ae-08d6a0e7e7d1 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0950; x-ms-traffictypediagnostic: CS1PR8401MB0950: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtDUzFQUjg0MDFNQjA5NTA7MjM6a1lRQnBqVURtY2hPRUtuMjFOSm4zcC84?= =?utf-8?B?S2hOVW1Iazh4Q0hacS9ZenhqU21mV1VqVkdBT1MwWEU0ekJ4NDFIcnNQWUZD?= =?utf-8?B?TDFpTW11dmk1WHJ3bzljckRpc0FHVlpRd05oampTMThMeGJHTWdidkRQNHJS?= =?utf-8?B?eFhsanlJOTd0cTl1OEh4aWVaMEM3SUtLN0dBTUNMSGZEdlVSWDUzTUhHVmwx?= =?utf-8?B?Ykk0Q2ltWnR2VW5tblQ0Z2NRcWFUSW9qekNORFNDMlRxUk44aThUdS9NMzU4?= =?utf-8?B?VHErU1hSckxZYWUvMGV5RWpHN2Fyc0RYSmh5ZCt6SnhBRktQSEVrcmVGQnYw?= =?utf-8?B?WmlYV25Ib3lKS3Y1UXRCMGpvU3NwTFFwTHVGeGoxOWhkTTdBNHlROUVCaEdn?= =?utf-8?B?dE9hRFlLK24xaW9ua0lkSHdkVW5sNDNST1pOT1ZoSTdaQUV1MDZhb0UzRGt6?= =?utf-8?B?cisrTkRtcUhnM0lkRWJsVlZaRlBrLzRtUnk0SWpaT0QwRE53dGFmTHRkaDl2?= =?utf-8?B?SjVkSHRVYXFIaW44cFVEd1BlNlhlcWplU3FGMUJpczFBdVVJWUJjRWZxTkRB?= =?utf-8?B?Q1ZYaU1OY0tWaWJyUU5SWWhpandmekUraVJ6K1RsUTB1cThyRkJYSDFIUitS?= =?utf-8?B?S2lGcmRYS2J1SmJYMUFYVTk3OWRpRHhhTjlPRHR6NXdEUXhUajU1dmVubTFD?= =?utf-8?B?eklDWEJBYUZlOFBjS1hqNGYyTEg5ZjR1ajlZeDFqYitLeXJpOE5iVC9hWFhB?= =?utf-8?B?SXJpRTZHZ05ra1JBV1VTUGtTZ0VaaktMMlp3ZnBpQW5Pb2hXUnNJcVNoMzg0?= =?utf-8?B?RnJXaTdXYS81d1F3dFlxNTBXeDEwR0x4aEtZS01DU2xkN0NUQnZRR3BmQzln?= =?utf-8?B?UDhaSVkzN0tEbTRGSk81bHdxT2NyNVhueFFnZzJFeXBpeXppTVR6ZURZS0dD?= =?utf-8?B?VVBNNW1jNXk3N0htL25uUVM1dzRzblZ5WUhlNm1STGVwMzZndWFnUHFEWmlt?= =?utf-8?B?ZlR5M0U1Sk11WTFPSVlGNnM2NVpZRFRoQWVFOHgzV2dvV3NmeXpOV1YzNVFm?= =?utf-8?B?cDJZUmxPQmNFdDVkN3JNUmh3SVZleStaY0lsWlpEWFpYNHRwUGJPa2pabC9j?= =?utf-8?B?L1lacDd2TmhYVHBOWjlZc0JTYmdVVlhablIrNnRtaDNMcGM3QW50QXVKOCtQ?= =?utf-8?B?UUZEOUxlTXBLZmlkbkRaRVlwcDc3bCtrbVlkR3pFY1JFbXIyUWE2TlUvTTg5?= =?utf-8?B?NnhxYnhneFpaOUJMM2hybUZYOTVZbU1xdkh1bEtpb29uaFplbVVnTzQzNXJk?= =?utf-8?B?U0ZHU0Y3UWpXN21QNjF5V3ZsMWhlQTVmZVdjbTJDUDVCTElNVitZYzRuc0hZ?= =?utf-8?B?dUNXUjEyMlgyRmVxcm5pd0VJOEhOTERTZjlMbFVUTUFjZnZLamQ3Z29nMTZl?= =?utf-8?B?VzZyR2lEdVUxZXZnUGx5TExIYkt2OFdTUlMwWU53clpubHk5eXFKM0ZEWExV?= =?utf-8?B?ZkEwcHZjcWdOQUFndm41SENEckdic2VYTlExa0tyZnFZSW55K0FtRVp0cFhD?= =?utf-8?B?QjYzdU1rOUppUXd4MTFMOE5LMmtVSVVhTDRmbGg2Wk5pK3grQ0g2OGE4bmJW?= =?utf-8?B?SnRGc1VWdHhCc2dabHJsdmN4VUhCL3NxVDNmbDlYVWdiWnJOSXFMUE9sbE9W?= =?utf-8?B?cTQ4cEhLTWtUTUl5WTBBWWt6NjRtRjYxVUZ4dzVGdWhJOEExZWdvMVpJUmxh?= =?utf-8?B?L3JCREtGWkdoVWZqaTBMUGxhQW5YR2h0bU1oUlh0akJ3bVA2am02djlkY3dy?= =?utf-8?B?UVBGVUNSanp1dmVKcHg2NmoyemQ2L2VpeFpONEZYUTUzSkhEWlo2NXFjT3Jk?= =?utf-8?Q?fFV7WEvaT4iC4=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09669DB681 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(136003)(396003)(376002)(39860400002)(189003)(199004)(6602003)(54094003)(5660300002)(53936002)(106356001)(99936001)(93886005)(15650500001)(71190400001)(478600001)(14454004)(33656002)(97736004)(71200400001)(68736007)(81166006)(76176011)(186003)(105586002)(6116002)(36756003)(83716004)(26005)(3846002)(54896002)(8936002)(14444005)(2616005)(11346002)(6246003)(6512007)(316002)(66066001)(6436002)(6506007)(53546011)(6916009)(82746002)(256004)(81156014)(102836004)(99286004)(25786009)(2906002)(8676002)(476003)(6486002)(7736002)(446003)(486006)(229853002)(86362001)(4326008)(236005); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0950; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: TrDXNoOuw03rNA3ChNPdEPrCiCW9YUHk7SLPgS2I3rzwFFKaFiKuv11b6O9g+xlPcLwLlssknV3CUm7xfQR4YdcOByqQqnsKGARZsGyKR2Z53uEXr+44wsTl6G3YFoR3p4R233JnPP6yhWPYABn4XLNwJd8LX2VTxkN0zN2V1frNI1r4LJ36ia/EyQryPomw2LUKoCMiyMN3V5G9Bf/fzWnZ+8RO7HcL1ql17VX+7mR0QQ4NuzoxzZn3vFOdp4Itir8i7nVXblWftvO9BqxkyRuJO1UDiURnGDe7JG3XJS1+Fo7uNEf/YAOWgWZooLkQjXAyJXkI8mISrJz0rpHj0+ev+QPTbSRifaTOF9tFfNBXwyacv0lrxl3nhD6iHI4I6nyazlkr9tc8QAFcbVtjNmDtIGtRBGR/+NrhVMWJQQg= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: d2b66a48-41ee-4af7-60ae-08d6a0e7e7d1 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2019 21:25:20.6041 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0950 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============0803813712242183756==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0803813712242183756== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F7B6445E-AA95-4171-9322-2640BCA5CA7F"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_F7B6445E-AA95-4171-9322-2640BCA5CA7F Content-Type: multipart/alternative; boundary="Apple-Mail=_4071EB6A-CE47-4144-8EE1-FD3286E97C47" --Apple-Mail=_4071EB6A-CE47-4144-8EE1-FD3286E97C47 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 4, 2019, at 2:10 PM, Michael Sweet wrote: >=20 >>> One addition I'd like to see to see for the "requesting-user-name" = method is a note that some Clients use a constant identity as a privacy = defense (e.g., "mobile" from iOS Clients) when sending requests, so from = a Printer's perspective this method is basically useless. In the = context of GDPR, this falls under a need for explicit consent - a = password challenge or Client UI requesting permission to provide the = real user name is required. At Apple we decided to always hide the = requesting user on iOS for basic privacy reasons, relying on = authentication where such information is genuinely needed. >>=20 >> Do you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. "Client = Security Considerations"? There seems to be two different statements: = what is done in the field, and what a Client or Printer ought to do. >=20 > I was thinking of this being in section 4.2. As far as the general = recommendations for clients, I think we need to make a note of privacy = concerns, .i.e., recommend that Clients don't just throw the current = username in there without getting explicit permission from the User. I am fine with that - how's this for an updated section 4.2: 4.2. The 'requesting-user-name' IPP Authentication Method The 'requesting-user-name' IPP Authentication Method [RFC8011] indicates = that the Client is to provide the =E2=80=9Crequesting-user-name=E2=80=9D = operation attribute [RFC8011] in its IPP operation request. The Printer = uses this unauthenticated name as the identity of the User operating the = Client. This method is not recommended if job accounting or access = authorization is important, since the Printer does not challenge the = Client to prove the identity claimed in the =E2=80=9Crequesting-user-name=E2= =80=9D. Some Clients always send a fixed identity name (e.g. = =E2=80=9Cmobile=E2=80=9D) as a privacy defense when sending requests. As = such, from a Printer's perspective, this method is increasingly = undependable. I wonder if we need to call out the notion of authentication as a form = of explicit consent to share information, especially within the context = of privacy concerns such as GDPR compliance? Where might we put that? = The start of Section 4 "Client Authentication Methods"? Or down in = Security Considerations? --Apple-Mail=_4071EB6A-CE47-4144-8EE1-FD3286E97C47 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

    On Mar 4, 2019, at 2:10 PM, Michael Sweet <msweet@apple.com> = wrote:

    One addition I'd like to see to see for the = "requesting-user-name" method is a note that some Clients use a constant = identity as a privacy defense (e.g., "mobile" from iOS Clients) when = sending requests, so from a Printer's perspective this method is = basically useless.  In the context of GDPR, this falls under a need = for explicit consent - a password challenge or Client UI requesting = permission to provide the real user name is required.  At Apple we = decided to always hide the requesting user on iOS for basic privacy = reasons, relying on authentication where such information is genuinely = needed.

    Do = you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. = "Client Security Considerations"? There seems to be two different = statements: what is done in the field, and what a Client or Printer = ought to do.

    I was thinking of this being in = section 4.2.  As far as the general recommendations for clients, I = think we need to make a note of privacy concerns, .i.e., recommend that = Clients don't just throw the current username in there without getting = explicit permission from the = User.

    I am fine with that - how's this for an updated section = 4.2:

    4.2. = The 'requesting-user-name' IPP Authentication = Method

    The 'requesting-user-name' IPP Authentication Method = [RFC8011] indicates that the Client is to provide the = =E2=80=9Crequesting-user-name=E2=80=9D operation attribute [RFC8011] in = its IPP operation request. The Printer uses this unauthenticated name as = the identity of the User operating the Client. This method is not = recommended if job accounting or access authorization is important, = since the Printer does not challenge the Client to prove the identity = claimed in the =E2=80=9Crequesting-user-name=E2=80=9D. Some Clients = always send a fixed identity name (e.g. =E2=80=9Cmobile=E2=80=9D) as a = privacy defense when sending requests. As such, from a Printer's = perspective, this method is increasingly = undependable. 

    I wonder if we need to call out the = notion of authentication as a form of explicit consent to share = information, especially within the context of privacy concerns such as = GDPR compliance? Where might we put that? The start of Section 4 "Client = Authentication Methods"? Or down in Security Considerations?


    = --Apple-Mail=_4071EB6A-CE47-4144-8EE1-FD3286E97C47-- --Apple-Mail=_F7B6445E-AA95-4171-9322-2640BCA5CA7F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx9l74ACgkQqskbKLDW 1N3cyg//SyYBuWRQ5EvJTlCU3TdTkv8ZjL0Q6b3b2ooD3Ly4shQhebkkWkSnVYuO wH+RsGMtWUBfCuCSrGeU92BFqKWyXAFPMb6USI0ZteD4fNHrV134lk00WQQyFuEs S2lyzK3kxD77dwn5WOFD0eDa5fcWBA3XijZYcVm+gat4phuN6557vrIhUv0ImuXo b2rBtKciNFeI/WVv1AKjHWwFZLhSYofse8nWO1TIZNsV/UmTOzSA+yAt4uCyAi4j 0TtImMetvrIvyAHfH6Re/G5rVvkUBxWCF+5vyC0+KCBmKxtrZM5wR1F1Vrje0orB QUctKSg7qF8r/IzIXYxABq6I/0tUNueKxfsp9NMRDpuS70OFStaTzCJsykqqPgGa WBpPiMlqdCYCcLVW599RxHy5agez6oY2hAF5/n3yuoxZ5kHEbJIqSISlFQo3G1Gt 81bSICYW3S6B7CV0WupMHUFs5JVXt7wzHqfEsIXzVxZG+QaCHlvToXTafsxnGA+U /WUNqGrYyyh/6X853gNho8JTBLfMd/HkEkOf8k9kmAli6cUuBpvYGYqThBF6tRe4 suoAto1+dqFibpADSjsHBFbV4fQOb7OrLPQJf4PR/byG2p5/6hLNi5v0oa/VmLAc ckA4509mAOrG2h6jDxLQTuVcLDtRNefkx3I13rNoG/aaTEN7B6k= =QyLp -----END PGP SIGNATURE----- --Apple-Mail=_F7B6445E-AA95-4171-9322-2640BCA5CA7F-- --===============0803813712242183756== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0803813712242183756==-- From ipp-bounces@pwg.org Mon Mar 4 13:35:10 2019 Return-Path: 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 AF9CD131119 for ; Mon, 4 Mar 2019 13:35:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=chromium.org 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 ztctb0ouXamu for ; Mon, 4 Mar 2019 13:35:08 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id D991B131154 for ; Mon, 4 Mar 2019 13:35:07 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id EFF803F4E; Mon, 4 Mar 2019 21:35:06 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1F2921C98; Mon, 4 Mar 2019 21:35:03 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 9C8883F45; Mon, 4 Mar 2019 21:35:00 +0000 (UTC) Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) by www.pwg.org (Postfix) with ESMTPS id B66E624D3 for ; Mon, 4 Mar 2019 21:34:59 +0000 (UTC) Received: by mail-io1-xd30.google.com with SMTP id k21so5195217ior.13 for ; Mon, 04 Mar 2019 13:34:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DdxXAbVdRvqe19h4LTElaKFt+AklAxGHc6DzYuk4h5Q=; b=CcQaq2N9EioXnLx6ArZ04+zDsJHqZqF9KA88M67iTW5/B5li2box3eDZkmOFT2gwjg reClW1q4sbNKblnrmWJR6hfsKv+8zefVLN+Jd7tNlb7jx5aTrsQezt3/nqU/dfhmQRGB HZLeetGpKQn5XdTgg1cz11CzwQ0BSWwC+kuU0= 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=DdxXAbVdRvqe19h4LTElaKFt+AklAxGHc6DzYuk4h5Q=; b=HjQXkVKE4KfJn2nUNCLV3JEkmZKQraJf28cMjo9cX6wkzAFsRO4mcMpzNP7rbKo7Me dIcaCkNQvmzcxERdfXOCl65LAPYsJBYMMSQWqx7NStnUjUsodZyZn5ilnmIy+vLCnuJr CiDhWCXDJAA0NhHt0T6zbt0ff+9ywDLMCHCumFqLSbRE1HvKJVKLeOVIsjeEYh6sdvJZ 1l23hhFrkqcXSO8XjP36fjLRsaYjA0gDvb/XD9m38oSyLKvZpnzEyVntkbnGzVUJz5Pg YV9U7FDrzWo6N80TgFykej6ETmFl9zVg04Z4pS74NGSmMLLzA1+Y2/ytz99TZPyNCQ1B b+KA== X-Gm-Message-State: APjAAAVjlUUHH5Loao2A+Ianh3NnyJYsK838yxKBJYsgIK9gbiTCSILc 6d+uL+oWNISBkKvWOHbj54MfqbXWAs/sNIGs4igS2Q== X-Google-Smtp-Source: APXvYqwPLdI8vj4Y73Wl2fn1j44YOM+DD7kdce1PQKnxcNVjs/BywfeZmMiG70W9k3ES38xJmQi/ZoUkrwH0fu7SGg8= X-Received: by 2002:a6b:8e04:: with SMTP id q4mr11022069iod.287.1551735298716; Mon, 04 Mar 2019 13:34:58 -0800 (PST) MIME-Version: 1.0 References: <188BC820-B4B4-49EA-946A-AE336B413F9E@hp.com> In-Reply-To: <188BC820-B4B4-49EA-946A-AE336B413F9E@hp.com> Date: Mon, 4 Mar 2019 13:34:46 -0800 Message-ID: To: "Kennedy, Smith (Wireless & Standards Architect)" Cc: "ipp@pwg.org" Subject: Re: [IPP] IPP Everywhere PWG-Raster AND PDF Requirement X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Sean Kau via ipp Reply-To: Sean Kau Content-Type: multipart/mixed; boundary="===============1937573021279853537==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============1937573021279853537== Content-Type: multipart/alternative; boundary="000000000000441a1a05834b8729" --000000000000441a1a05834b8729 Content-Type: text/plain; charset="UTF-8" That's sensible behavior for the standard as applicable to printers. Is there a recommendation for client behavior? It seems like clients should prefer PDF since that should be smaller on the wire, On Mon, Mar 4, 2019 at 12:51 PM Kennedy, Smith (Wireless & Standards Architect) wrote: > Good question, Sean. The reason for this is to set a baseline for > interoperability. Some clients may not support PDF. So all Clients and > Printers are required to support PWG Raster as a bare minimum. That way, > there will always be some common document format that both can fall back to. > > Smith > > > > > On Mar 4, 2019, at 1:26 PM, Sean Kau via ipp wrote: > > > > Question about the IPP Everywhere specification: > > > > Why do we require that printers support PWG-Raster if it can accept > PDF? Is this to improve compatibility with clients? I tried to look > through the archives and couldn't find any commentary. > > > > -- > > Sean Kau > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://protect-us.mimecast.com/s/OLVKCXDwEwTKJv3Bh6nyay?domain=pwg.org > > -- Sean Kau --000000000000441a1a05834b8729 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    That's sensible behavior for the standard as applicabl= e to printers.=C2=A0 Is there a recommendation for client behavior?=C2=A0 I= t seems like clients should prefer PDF since that should be smaller on the = wire,

    On Mon, Mar 4, 2019 at 12:51 PM Kennedy, Smith (Wireless & Standa= rds Architect) <smith.kennedy@hp= .com> wrote:
    Good question, Sean. The reason for this is to set a baseline for inter= operability. Some clients may not support PDF. So all Clients and Printers = are required to support PWG Raster as a bare minimum. That way, there will = always be some common document format that both can fall back to.

    Smith



    > On Mar 4, 2019, at 1:26 PM, Sean Kau via ipp <ipp@pwg.org> wrote:
    >
    > Question about the IPP Everywhere specification:
    >
    > Why do we require that printers support PWG-Raster if it can accept PD= F?=C2=A0 Is this to improve compatibility with clients?=C2=A0 I tried to lo= ok through the archives and couldn't find any commentary.
    >
    > --
    > Sean Kau
    > _______________________________________________
    > ipp mailing list
    > ipp@pwg.org
    > https://protect-us.mim= ecast.com/s/OLVKCXDwEwTKJv3Bh6nyay?domain=3Dpwg.org



    --
    Sean Kau
    --000000000000441a1a05834b8729-- --===============1937573021279853537== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1937573021279853537==-- From ipp-bounces@pwg.org Mon Mar 4 16:30:20 2019 Return-Path: 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 AD675131179 for ; Mon, 4 Mar 2019 16:30:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 RTDU75JgZoUQ for ; Mon, 4 Mar 2019 16:30:17 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 5606A130DC2 for ; Mon, 4 Mar 2019 16:30:17 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id BDC663F9B; Tue, 5 Mar 2019 00:30:16 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 4F650315; Tue, 5 Mar 2019 00:30:11 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 377173F45; Tue, 5 Mar 2019 00:30:10 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id 371DD315 for ; Tue, 5 Mar 2019 00:30:09 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x250MGi5065486; Mon, 4 Mar 2019 16:30:06 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=kulk7weStIl/mfs/lbUn1+HZRy6UIQ5E9gRa5ZTIoGs=; b=SGIxTlUi0wO3+oS6yHUDaDJSt7kpa1gJXtr+yfg+MR276DNrsogxgrg2uvsg2X8qfM0q PgL3NRcMbeSOZ6PY0rZcMPmYeGeG1Gn2ottX4wEwbDhjCEQScCNWq25emBenaWfPh4Yv cGZUXGFTYcvCsl52oHEQYn3DRdjKCW3OpFd8iXScTb25OPj2Cm16b61Y1/XptLKZagLY oSbdEfTD3bfTqTWo99fmmYwMji7zDn0Uf6DnHznbWWbVr5nmn23DZ285NBDDVjv45u40 4sDkbbQhBYrwSwql/QthZJwpcZm8U7PeVQl4m9eGgLuRSh8SVH3qqL2iBN5N1W+qDYmh Ww== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2qyscayk9d-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 04 Mar 2019 16:30:06 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNV00CX3APY5QB0@ma1-mtap-s03.corp.apple.com>; Mon, 04 Mar 2019 16:30:04 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNV00C009N8GS00@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 16:30:04 -0800 (PST) X-Va-A: X-Va-T-CD: 943928c10ba20a309aa72d547dc77650 X-Va-E-CD: ba95cf33ea6f603e0c310aa6c7fa7d63 X-Va-R-CD: be124565f6d8738eb05185d150b08263 X-Va-CD: 0 X-Va-ID: 0c691aae-c52b-4df2-963b-e3e633736f18 X-V-A: X-V-T-CD: 943928c10ba20a309aa72d547dc77650 X-V-E-CD: ba95cf33ea6f603e0c310aa6c7fa7d63 X-V-R-CD: be124565f6d8738eb05185d150b08263 X-V-CD: 0 X-V-ID: 0bac77b2-219a-4a38-950c-ac588ba34be5 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_13:,, signatures=0 Received: from [17.235.50.128] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNV002SXAQ2RV80@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 16:30:03 -0800 (PST) In-reply-to: Date: Mon, 04 Mar 2019 19:30:01 -0500 Message-id: <0EACD046-EF4F-4B87-B656-A11203CE721D@apple.com> References: <188BC820-B4B4-49EA-946A-AE336B413F9E@hp.com> To: Sean Kau X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] IPP Everywhere PWG-Raster AND PDF Requirement X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============5812655176845525790==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5812655176845525790== Content-type: multipart/alternative; boundary="Boundary_(ID_4+pzm7DHcwunrOvHVZsiSQ)" --Boundary_(ID_4+pzm7DHcwunrOvHVZsiSQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sean, > On Mar 4, 2019, at 4:34 PM, Sean Kau via ipp wrote: > > That's sensible behavior for the standard as applicable to printers. Is there a recommendation for client behavior? It seems like clients should prefer PDF since that should be smaller on the wire, Generally speaking, if the Client can produce PDF then it should use it. However, if the Client is printing a JPEG image (without special layout) and the Printer accepts JPEG, it should send the JPEG and not try wrapping it in a PDF or rendering as PWG Raster. That said, a Client should also handle the document-unprintable-error case and retry as raster if the PDF (or JPEG) fails. You can see this behavior in the CUPS ipp backend (where it tells cupsd to retry the job and use raster...) > > On Mon, Mar 4, 2019 at 12:51 PM Kennedy, Smith (Wireless & Standards Architect) > wrote: > Good question, Sean. The reason for this is to set a baseline for interoperability. Some clients may not support PDF. So all Clients and Printers are required to support PWG Raster as a bare minimum. That way, there will always be some common document format that both can fall back to. > > Smith > > > > > On Mar 4, 2019, at 1:26 PM, Sean Kau via ipp > wrote: > > > > Question about the IPP Everywhere specification: > > > > Why do we require that printers support PWG-Raster if it can accept PDF? Is this to improve compatibility with clients? I tried to look through the archives and couldn't find any commentary. > > > > -- > > Sean Kau > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://protect-us.mimecast.com/s/OLVKCXDwEwTKJv3Bh6nyay?domain=pwg.org > > > > -- > Sean Kau > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_4+pzm7DHcwunrOvHVZsiSQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Sean,

    On Mar 4, 2019, at 4:34 PM, = Sean Kau via ipp <ipp@pwg.org> wrote:

    That's sensible behavior for the standard as = applicable to printers.  Is there a recommendation for client = behavior?  It seems like clients should prefer PDF since that = should be smaller on the wire,

    Generally speaking, if the Client can produce PDF then = it should use it.  However, if the Client is printing a JPEG image = (without special layout) and the Printer accepts JPEG, it should send = the JPEG and not try wrapping it in a PDF or rendering as PWG = Raster.

    That said, a Client should = also handle the document-unprintable-error case and retry as raster if = the PDF (or JPEG) fails.  You can see this behavior in the CUPS ipp = backend (where it tells cupsd to retry the job and use = raster...)


    On Mon, Mar 4, 2019 at = 12:51 PM Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    Good = question, Sean. The reason for this is to set a baseline for = interoperability. Some clients may not support PDF. So all Clients and = Printers are required to support PWG Raster as a bare minimum. That way, = there will always be some common document format that both can fall back = to.

    Smith



    > On Mar 4, 2019, at 1:26 PM, Sean Kau via = ipp <ipp@pwg.org> wrote:
    > 
    > = Question about the IPP Everywhere specification:
    > 
    > Why do = we require that printers support PWG-Raster if it can accept PDF?  = Is this to improve compatibility with clients?  I tried to look = through the archives and couldn't find any commentary.
    > 
    > --
    > Sean Kau
    > = _______________________________________________
    > ipp = mailing list
    > ipp@pwg.org
    > https://protect-us.mimecast.com/s/OLVKCXDwEwTKJv3Bh6nyay?domain= =3Dpwg.org



    -- 
    Sean Kau
    _______________________________________________
    ipp mailing = list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    =

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_4+pzm7DHcwunrOvHVZsiSQ)-- --===============5812655176845525790== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5812655176845525790==-- From ipp-bounces@pwg.org Mon Mar 4 16:38:21 2019 Return-Path: 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 CDDF213123B for ; Mon, 4 Mar 2019 16:38:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 eAsjYUSZ6ItM for ; Mon, 4 Mar 2019 16:38:18 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 9077F13122D for ; Mon, 4 Mar 2019 16:38:18 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 8E3583F4D; Tue, 5 Mar 2019 00:38:16 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id E793124D3; Tue, 5 Mar 2019 00:38:07 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 3DA5E315; Tue, 5 Mar 2019 00:38:07 +0000 (UTC) Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) by www.pwg.org (Postfix) with ESMTPS id 6F2D2315 for ; Tue, 5 Mar 2019 00:38:06 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x250ash9020277; Mon, 4 Mar 2019 16:38:04 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=d13nwhN6tr/riSEr+Bep4H6BGxmaae2XGAhIbGW43WA=; b=DvjzaB3tuPC22vHcnYndC/KE+iOs2ctrLWzkoAl9NO4fvkl8HfUy/iAF4cjk0mkv89o4 ZBFwHVPihuX42eCw6ikfDIlms6JGv8chz1MdXR8ZMl1ezvECOvg+RgCY+OuJpV0Ug7q4 A+QUN/qQsNCpXjoPJpf9gZgBZ0JheA9vJL6EjQ5yAZI/Tfp8PDQQCjn/v0/gzomgAoRt Xl3Yq07V8+el5sc8yAx8DqPQujv3j/jQX5f8ZmJAXWwC4TucXto3GatejlqnWx48kycw BZ2dklDAzMz0yv03OtPFrkpDEb4phEU2RSg3mIiDVauMVse2qN4/9J+xbbm6z56b+yOb Eg== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2qyq9syfst-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 04 Mar 2019 16:38:04 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNV003CEB3DHW20@ma1-mtap-s03.corp.apple.com>; Mon, 04 Mar 2019 16:38:02 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNV00800ARZDD00@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 16:38:02 -0800 (PST) X-Va-A: X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-Va-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-Va-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-Va-CD: 0 X-Va-ID: cdcf6a0a-6886-4e2b-913d-84f0c86dfe73 X-V-A: X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-V-E-CD: 9834e30e54db3bd9672d95edc6326d24 X-V-R-CD: a96f0fe8e640c559970af8f2afbaef0b X-V-CD: 0 X-V-ID: aa21e032-e348-4836-8ee7-fa4ea87a1e5f X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-04_13:,, signatures=0 Received: from [17.235.50.128] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNV0079SB3B2V20@nwk-mmpp-sz09.apple.com>; Mon, 04 Mar 2019 16:38:02 -0800 (PST) In-reply-to: <8FF54F79-03FE-469B-8102-04790B0AB755@hp.com> Date: Mon, 04 Mar 2019 19:37:59 -0500 Message-id: <20025728-8AD2-4473-B0A8-CBCC2AB3ECF2@apple.com> References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> <46698615-D1A6-413D-9E83-9B38ED84A89B@apple.com> <8FF54F79-03FE-469B-8102-04790B0AB755@hp.com> To: "Kennedy, Smith (Wireless & Standards Architect)" X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-04_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============8733028673556055728==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8733028673556055728== Content-type: multipart/alternative; boundary="Boundary_(ID_8Q6tOHqmq2OgQ3QCC7yuVQ)" --Boundary_(ID_8Q6tOHqmq2OgQ3QCC7yuVQ) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable Smith, > On Mar 4, 2019, at 4:25 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp wrote: >=20 >=20 >=20 >> On Mar 4, 2019, at 2:10 PM, Michael Sweet > wrote: >>=20 >>>> One addition I'd like to see to see for the "requesting-user-name" = method is a note that some Clients use a constant identity as a privacy = defense (e.g., "mobile" from iOS Clients) when sending requests, so from = a Printer's perspective this method is basically useless. In the = context of GDPR, this falls under a need for explicit consent - a = password challenge or Client UI requesting permission to provide the = real user name is required. At Apple we decided to always hide the = requesting user on iOS for basic privacy reasons, relying on = authentication where such information is genuinely needed. >>>=20 >>> Do you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. "Client = Security Considerations"? There seems to be two different statements: = what is done in the field, and what a Client or Printer ought to do. >>=20 >> I was thinking of this being in section 4.2. As far as the general = recommendations for clients, I think we need to make a note of privacy = concerns, .i.e., recommend that Clients don't just throw the current = username in there without getting explicit permission from the User. >=20 > I am fine with that - how's this for an updated section 4.2: >=20 > 4.2. The 'requesting-user-name' IPP Authentication Method >=20 > The 'requesting-user-name' IPP Authentication Method [RFC8011] = indicates that the Client is to provide the =E2=80=9Crequesting-user-name=E2= =80=9D operation attribute [RFC8011] in its IPP operation request. The = Printer uses this unauthenticated name as the identity of the User = operating the Client. This method is not recommended if job accounting = or access authorization is important, since the Printer does not = challenge the Client to prove the identity claimed in the = =E2=80=9Crequesting-user-name=E2=80=9D. Some Clients always send a fixed = identity name (e.g. =E2=80=9Cmobile=E2=80=9D) as a privacy defense when = sending requests. As such, from a Printer's perspective, this method is = increasingly undependable.=20 I would add "also" to the sentence, e.g., "Also, some Clients always = send ..." > I wonder if we need to call out the notion of authentication as a form = of explicit consent to share information, especially within the context = of privacy concerns such as GDPR compliance? Where might we put that? = The start of Section 4 "Client Authentication Methods"? Or down in = Security Considerations? Right now I hesitate to put that wording in this document. If IDS is = going to tackle the privacy/information gathering problem, I think we = are probably better off deferring that discussion to their work since = there isn't a lot we can say in a few sentences here. But FWIW, I think an authentication challenge and the subsequent = providing of credentials does constitute explicit consent WRT the = username and password; there is still the issue of *informed consent* to = deal with - how does the user know why they are being asked for a = username and password? (I also feel like we may end up with an update to my IPP Privacy = Attributes document at some point...) _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_8Q6tOHqmq2OgQ3QCC7yuVQ) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable Smith,

    On Mar 4, 2019, at 4:25 PM, = Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> = wrote:



    On Mar 4, 2019, at 2:10 PM, Michael Sweet <msweet@apple.com> = wrote:

    One addition I'd like to see to see for the = "requesting-user-name" method is a note that some Clients use a constant = identity as a privacy defense (e.g., "mobile" from iOS Clients) when = sending requests, so from a Printer's perspective this method is = basically useless.  In the context of GDPR, this falls under a need = for explicit consent - a password challenge or Client UI requesting = permission to provide the real user name is required.  At Apple we = decided to always hide the requesting user on iOS for basic privacy = reasons, relying on authentication where such information is genuinely = needed.

    Do = you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. = "Client Security Considerations"? There seems to be two different = statements: what is done in the field, and what a Client or Printer = ought to do.

    I was thinking of this being in = section 4.2.  As far as the general recommendations for clients, I = think we need to make a note of privacy concerns, .i.e., recommend that = Clients don't just throw the current username in there without getting = explicit permission from the = User.

    I am fine with that - how's this for an updated section = 4.2:

    4.2. = The 'requesting-user-name' IPP Authentication = Method

    The 'requesting-user-name' IPP Authentication Method = [RFC8011] indicates that the Client is to provide the = =E2=80=9Crequesting-user-name=E2=80=9D operation attribute [RFC8011] in = its IPP operation request. The Printer uses this unauthenticated name as = the identity of the User operating the Client. This method is not = recommended if job accounting or access authorization is important, = since the Printer does not challenge the Client to prove the identity = claimed in the =E2=80=9Crequesting-user-name=E2=80=9D. Some Clients = always send a fixed identity name (e.g. =E2=80=9Cmobile=E2=80=9D) as a = privacy defense when sending requests. As such, from a Printer's = perspective, this method is increasingly = undependable. 
    =
    I would add "also" to the sentence, e.g., "Also, = some Clients always send ..."

    I = wonder if we need to call out the notion of authentication as a form of = explicit consent to share information, especially within the context of = privacy concerns such as GDPR compliance? Where might we put that? The = start of Section 4 "Client Authentication Methods"? Or down in Security = Considerations?

    Right now I hesitate to put that wording in this = document.  If IDS is going to tackle the privacy/information = gathering problem, I think we are probably better off deferring that = discussion to their work since there isn't a lot we can say in a few = sentences here.

    But FWIW, I think an = authentication challenge and the subsequent providing of credentials = does constitute explicit consent WRT the username and password; there is = still the issue of *informed consent* to deal with - how does the user = know why they are being asked for a username and password?

    (I also feel like we may end up with an update to = my IPP Privacy Attributes document at some point...)

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_8Q6tOHqmq2OgQ3QCC7yuVQ)-- --===============8733028673556055728== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8733028673556055728==-- From ipp-bounces@pwg.org Tue Mar 5 07:52:33 2019 Return-Path: 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 CE29F1200D8 for ; Tue, 5 Mar 2019 07:52:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 9JvpkpX00lWy for ; Tue, 5 Mar 2019 07:52:29 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 6F095124B0C for ; Tue, 5 Mar 2019 07:52:29 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 30C864073; Tue, 5 Mar 2019 15:52:28 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 9F67F3F45; Tue, 5 Mar 2019 15:52:22 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 2E58E264F; Tue, 5 Mar 2019 15:52:21 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 33BD9264F for ; Tue, 5 Mar 2019 15:52:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551801138; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vgL/3hLiY/mVg5cofBJDUeY8AAqKD1slUV6b2gsl3rk=; b=Bq+76iNiw9Egppva29DHA612hGU6Tys8/jVs0gdW8NOYSvQ9/5qGEN23mmifS9YVhqgTKbF54hv/R9IOXpbiaDysFj3wh2Bpsgo1gk0Gww8ZNRQHNOmKDfcvs/ZD8BFlmg5md32Sfa5qMipEfFJidvMp97p9sIlJcG3S7rOYLOg= Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp2056.outbound.protection.outlook.com [104.47.40.56]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-149-ocUGBJrdMgKqpSi6Z4Geww-1; Tue, 05 Mar 2019 10:52:16 -0500 X-MC-Unique: ocUGBJrdMgKqpSi6Z4Geww-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1224.NAMPRD84.PROD.OUTLOOK.COM (10.169.12.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Tue, 5 Mar 2019 15:52:14 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Tue, 5 Mar 2019 15:52:14 +0000 To: Michael Sweet Thread-Topic: [IPP] Updated stable draft of IPP Authentication Methods posted Thread-Index: AQHU0q7lBItiZ+reqEynp8Y9tft7qqX7xsSAgAAagYCAABa3gIAABC0AgAA11oCAAP9tgA== Date: Tue, 5 Mar 2019 15:52:14 +0000 Message-ID: References: <812F6E68-E304-4FA9-B11B-8ADDF06436D6@hp.com> <2723355E-059B-4EF8-BB67-8DF050D08D35@apple.com> <46698615-D1A6-413D-9E83-9B38ED84A89B@apple.com> <8FF54F79-03FE-469B-8102-04790B0AB755@hp.com> <20025728-8AD2-4473-B0A8-CBCC2AB3ECF2@apple.com> In-Reply-To: <20025728-8AD2-4473-B0A8-CBCC2AB3ECF2@apple.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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e5fc2c22-dbe3-4507-38d4-08d6a18289a4 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1224; x-ms-traffictypediagnostic: CS1PR8401MB1224: x-microsoft-exchange-diagnostics: =?utf-8?B?MTtDUzFQUjg0MDFNQjEyMjQ7MjM6b2R5aEhoc0FMNVlpYjkvb3FvTnY5ZG1h?= =?utf-8?B?U3pGKzlaVjNRQTZ1aFBwR2Zjb0NwTkEvWTdkVjNzbzFobXE0YVBhREc0Y1Fo?= =?utf-8?B?STdIS2M1M21RMnAwWjNYQUM4TG91dHBvUGhHQVFpeXNScFFSTWVWeFRwRTlk?= =?utf-8?B?NFRzM0JPSnBCVnlqUERDdXppZ2tJaFh6V21Sc0lGSng2eFZVSjdjdEFCbUpO?= =?utf-8?B?QXdkbEViTnpab1FEV3U5WERIRkkvbmdZY2duUWE0S21xSjNuUmRVOVJFNnJl?= =?utf-8?B?bERHS2pNcytJbFpSMlZ0VnBUV3dleTVlL2R5VHIrci8yZER4YjhZQkRYZmtQ?= =?utf-8?B?L09PeStDanJSQ2xWeWMycUErRmxPQWNoS09rbVZsYnZQYUM4MnlQTjBlWUFa?= =?utf-8?B?Q1F5SEFLZmU5K1R4QVBsSzdtSDNkcFRqcGdrY1lONGdIUHNnVjNqbFZoSFF0?= =?utf-8?B?YWw5anR0cDJFUytaNzhvekFldElPVGVjc2YzbHU1bjcxcVZ5b1RoVTVmc3ZV?= =?utf-8?B?T3NEYUxUZ1h3MlJtT0phb2wwWFpoUVNycy9pU1VQSnl1Z2xDZHZCNHlhRUJi?= =?utf-8?B?dC8xak1MZG5BV0V0Ky9vSnhKNjY2aVRONGFucHg3am44dzhFcmFIKzdNNnE1?= =?utf-8?B?NFBwSENtNk1EaUwyRWVEZ0o5alF4Z3BGZ1EzVXFmei9ieHA2TWsrSGl3UEtq?= =?utf-8?B?S2czUEQvaVZRTzdiUzFMUmJBRU0wZktROWkwY1BsaGk2WHF5WXJkVkNBN1hB?= =?utf-8?B?ay9qY0kwQWJYYlltR2cwVVdlUmY1RmozYkkxVThVT09vS0ppdkVpVFlycmZV?= =?utf-8?B?MjFRNG0zMzV1ZHJqQ1ovU3BxRWNSUUtlbnN6RzUvdGJWcStqWDdYa3RCQ0xl?= =?utf-8?B?TEV5TWZSd1l1SldWTDF0dndCQ0xaZjVFN0dEZWRvVGhkTE9qS2JrNnAzNTRP?= =?utf-8?B?K2NWME9oVjQ5M2pHL3RhT29EZ2E0azZ1d3FxS294UU1SRmZCYU9wNEQ4bmpm?= =?utf-8?B?cTZCRFJhNlVPUG81QWhXZjNRME51WXExb203OXYyL3M0TVRvM1FIQVppTUl1?= =?utf-8?B?OGdYRE5kMzRlN2J0WTZmdTNxMHdkc2d5WmVCNUUyQmpnTnZJVmU4cEFqc2Zt?= =?utf-8?B?WjZRTUNxVzZkK3p3cmE3U3J1UDNVYU8ycVBEeXZDN3oyT0NRTml6UEg3Rk9v?= =?utf-8?B?Ry8zRkJXckEwTEh4VEViaEdGVUdkMnhLY21rWWVHV1E5REZ5MjdBUHM1VHBX?= =?utf-8?B?TE84aWVzTkliY0VreGpWOHdvRnVVTHIzMzhWbEFMOVVESzN3Qy9GRGFxUmJw?= =?utf-8?B?UTVseDV1aURWRW5WY3lkZ3hyYzM2YUxuSWJJSE9YQ0tqQ0ttQ1RKcUtxekZY?= =?utf-8?B?MGVaeGxFTXpmMmlKYzlGY1NucUFPTEFyRjFrWjBjSndBU1ZRcTVxMGdlMzdr?= =?utf-8?B?S3UxSE1WTjlGU0RKaFBMSSs3dkV2eVVnamZOeDYySS96dmpYY0dtdmtWcmwz?= =?utf-8?B?UUpldWdoZ0Q1UC9DbmtGcXVQMGJlck9CU3dtUCtXUG9mNW8yTE9PRld5WnZZ?= =?utf-8?B?ZThESGpkanVlZ003TDJWejlQUlN6MTgxckViNnNTYVYxT3hwNDEwYUYwMDdZ?= =?utf-8?B?R0FlbmpiWXJZZzZnWTNTK0pmWkxmWUZJT3hMVDFDSFVYNWlnNmJWaDJGSEFa?= =?utf-8?B?MW1Sc3NNRkhNbDRXU2J0cUN0ZzB1WWhkU05reW9hUTc1Qll3c2tSRm9ISGND?= =?utf-8?B?Tm1XRVZXdU85U0JSZUtTQzRQTVQrd0JxYVlHcjlNblJhQnI2cVlnUVRxRUov?= =?utf-8?B?SVlXdHhLU1hlUkx3RjVkN1lxNlZKUnF5dUNabFBOcDZ5SFRoMGtXK2oyWmNp?= =?utf-8?Q?4GFftInJsx4HM=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 0967749BC1 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(366004)(346002)(376002)(136003)(199004)(6602003)(189003)(54094003)(5660300002)(68736007)(93886005)(66066001)(6506007)(54896002)(4326008)(446003)(11346002)(33656002)(105586002)(2906002)(106356001)(53936002)(53546011)(81166006)(25786009)(6512007)(99286004)(82746002)(6246003)(8936002)(316002)(236005)(8676002)(229853002)(81156014)(36756003)(476003)(97736004)(2616005)(7736002)(6436002)(99936001)(15650500001)(76176011)(6486002)(486006)(6916009)(478600001)(186003)(3846002)(26005)(14454004)(256004)(14444005)(83716004)(102836004)(71190400001)(71200400001)(86362001)(6116002); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1224; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: /DRgvuz0t+QF7CX37kQqnvt77PEA9wvY1NtXKsolQ8tP3tT7tmSjMjES1MJkuvvhCsS7SK8tgwrhdrPvUkM76XqG3RyPcXyjYWGhIt9tjPCw3Uvb+IJfebWvioPkcmxd1V4tG9hrLR34O+3SrWfe9jcluRRgZtKrSIp6syuwYOegMG+/PB5D0qnLMtIxSyBAYKw0jac8Gsw5g7QnRPKEmlmAJTF0eEyNzuYZWNN6HFnmZtGx6B08FrQQkypwGXYZDSLkXjYPc08Soz43bGXF+DGB/nAxXdMhVNgEx0rZjEsGzZhrsNTi3w+tIAIFsdiJt5fRQkL7vC57iUEpm7xsVeATgUYiwUdWS6lULzrSjLbMlmZrUx2dTXHNfi51cl/MYTPfEeNQEVvd8hdjpaDUaJztvwkUKzBlqZGJPFkAJfo= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: e5fc2c22-dbe3-4507-38d4-08d6a18289a4 X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Mar 2019 15:52:14.6245 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1224 Cc: PWG IPP Workgroup Subject: Re: [IPP] Updated stable draft of IPP Authentication Methods posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============3066534294271005018==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============3066534294271005018== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_CCBF5708-6EA7-47BF-81DE-F50EE0E4963C"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_CCBF5708-6EA7-47BF-81DE-F50EE0E4963C Content-Type: multipart/alternative; boundary="Apple-Mail=_81304EC4-1944-4F8B-BD91-E15294EE1130" --Apple-Mail=_81304EC4-1944-4F8B-BD91-E15294EE1130 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 OK, I added that into an updated 20190304 draft, which I just posted. > On Mar 4, 2019, at 5:37 PM, Michael Sweet wrote: >=20 > Smith, >=20 >> On Mar 4, 2019, at 4:25 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >>=20 >>=20 >>=20 >>> On Mar 4, 2019, at 2:10 PM, Michael Sweet > wrote: >>>=20 >>>>> One addition I'd like to see to see for the "requesting-user-name" = method is a note that some Clients use a constant identity as a privacy = defense (e.g., "mobile" from iOS Clients) when sending requests, so from = a Printer's perspective this method is basically useless. In the = context of GDPR, this falls under a need for explicit consent - a = password challenge or Client UI requesting permission to provide the = real user name is required. At Apple we decided to always hide the = requesting user on iOS for basic privacy reasons, relying on = authentication where such information is genuinely needed. >>>>=20 >>>> Do you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. "Client = Security Considerations"? There seems to be two different statements: = what is done in the field, and what a Client or Printer ought to do. >>>=20 >>> I was thinking of this being in section 4.2. As far as the general = recommendations for clients, I think we need to make a note of privacy = concerns, .i.e., recommend that Clients don't just throw the current = username in there without getting explicit permission from the User. >>=20 >> I am fine with that - how's this for an updated section 4.2: >>=20 >> 4.2. The 'requesting-user-name' IPP Authentication Method >>=20 >> The 'requesting-user-name' IPP Authentication Method [RFC8011] = indicates that the Client is to provide the =E2=80=9Crequesting-user-name=E2= =80=9D operation attribute [RFC8011] in its IPP operation request. The = Printer uses this unauthenticated name as the identity of the User = operating the Client. This method is not recommended if job accounting = or access authorization is important, since the Printer does not = challenge the Client to prove the identity claimed in the = =E2=80=9Crequesting-user-name=E2=80=9D. Some Clients always send a fixed = identity name (e.g. =E2=80=9Cmobile=E2=80=9D) as a privacy defense when = sending requests. As such, from a Printer's perspective, this method is = increasingly undependable. >=20 > I would add "also" to the sentence, e.g., "Also, some Clients always = send ..." >=20 >> I wonder if we need to call out the notion of authentication as a = form of explicit consent to share information, especially within the = context of privacy concerns such as GDPR compliance? Where might we put = that? The start of Section 4 "Client Authentication Methods"? Or down in = Security Considerations? >=20 > Right now I hesitate to put that wording in this document. If IDS is = going to tackle the privacy/information gathering problem, I think we = are probably better off deferring that discussion to their work since = there isn't a lot we can say in a few sentences here. >=20 > But FWIW, I think an authentication challenge and the subsequent = providing of credentials does constitute explicit consent WRT the = username and password; there is still the issue of *informed consent* to = deal with - how does the user know why they are being asked for a = username and password? >=20 > (I also feel like we may end up with an update to my IPP Privacy = Attributes document at some point...) >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer --Apple-Mail=_81304EC4-1944-4F8B-BD91-E15294EE1130 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 OK, = I added that into an updated 20190304 draft, which I just posted.
     

    On Mar 4, 2019, at 5:37 PM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    On Mar = 4, 2019, at 4:25 PM, Kennedy, Smith (Wireless & Standards Architect) = via ipp <ipp@pwg.org> = wrote:



    On Mar = 4, 2019, at 2:10 PM, Michael Sweet <msweet@apple.com> wrote:

    One addition I'd like to see to see for the = "requesting-user-name" method is a note that some Clients use a constant = identity as a privacy defense (e.g., "mobile" from iOS Clients) when = sending requests, so from a Printer's perspective this method is = basically useless.  In the context of GDPR, this falls under a need = for explicit consent - a password challenge or Client UI requesting = permission to provide the real user name is required.  At Apple we = decided to always hide the requesting user on iOS for basic privacy = reasons, relying on authentication where such information is genuinely = needed.

    Do = you want this in section 4.2 "The 'requesting-user-name' IPP = Authentication Method" (using numbering from the non-rev documents), or = in 5.1.1. "General Recommendations" (for Clients), or 7.2. = "Client Security Considerations"? There seems to be two different = statements: what is done in the field, and what a Client or Printer = ought to do.

    I was thinking of this being in section = 4.2.  As far as the general recommendations for clients, I think we = need to make a note of privacy concerns, .i.e., recommend that Clients = don't just throw the current username in there without getting explicit = permission from the User.

    I am fine with that - how's this for an = updated section 4.2:

    4.2. The 'requesting-user-name' IPP Authentication = Method

    The 'requesting-user-name' IPP Authentication Method = [RFC8011] indicates that the Client is to provide the = =E2=80=9Crequesting-user-name=E2=80=9D operation attribute [RFC8011] in = its IPP operation request. The Printer uses this unauthenticated name as = the identity of the User operating the Client. This method is not = recommended if job accounting or access authorization is important, = since the Printer does not challenge the Client to prove the identity = claimed in the =E2=80=9Crequesting-user-name=E2=80=9D. Some Clients = always send a fixed identity name (e.g. =E2=80=9Cmobile=E2=80=9D) as a = privacy defense when sending requests. As such, from a Printer's = perspective, this method is increasingly = undependable. 

    I would add "also" to the sentence, = e.g., "Also, some Clients always send ..."

    I wonder if we need to = call out the notion of authentication as a form of explicit consent to = share information, especially within the context of privacy concerns = such as GDPR compliance? Where might we put that? The start of Section 4 = "Client Authentication Methods"? Or down in Security = Considerations?

    Right now I hesitate to put that = wording in this document.  If IDS is going to tackle the = privacy/information gathering problem, I think we are probably better = off deferring that discussion to their work since there isn't a lot we = can say in a few sentences here.

    But FWIW, I think an authentication = challenge and the subsequent providing of credentials does constitute = explicit consent WRT the username and password; there is still the issue = of *informed consent* to deal with - how does the user know why they are = being asked for a username and password?

    (I also feel like we may end up with an = update to my IPP Privacy Attributes document at some point...)

    ______________________________________________________= ___
    Michael Sweet, Senior Printing = System Engineer

    = --Apple-Mail=_81304EC4-1944-4F8B-BD91-E15294EE1130-- --Apple-Mail=_CCBF5708-6EA7-47BF-81DE-F50EE0E4963C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlx+mysACgkQqskbKLDW 1N2Txw//ZQ8jC3KRq/6wSuSUI8la+3Sy3Lw+r1btCgBFGmUsj1YMhYhqyVnd6a7l GQz069cbOLYtmqRgufwfgOsBHzjVjvE0QudWAV++09kBfKrFrd1ojBK7ONdE+/Zr Ta/E+Kzt8PtQ4R85XTL9VQ+ZYsMBVwlNfiQLERi5TOsQ0ERdPR5nzBvsCjMrhzyl wxkjZLQl8p0v3wBp+QIgPl1CI0P5Xpp1hX334YD+33yOOx73FF49zKFVnsO07zda mxHpwzjYQ+QsoP3fLrXhMKloZKpE9Q/Uj7ZACMSGmW9ls48AImd8gqGmhgOA+VQO JN7GYZNJPRK8pGt/CQZN4suOEqmB05qrUF4ozVlv/ACSeaH9SNFykv06O2/z0AuR 8SeG0e204GC2+vvtud/MM/ETmXOeF6QtoXKLovRvROVbc84qZ3eqhXlsNjlrAGJu jbWVfbQUW1su3vWluaHO1x//ugEtRrRPbYEpODYXiqJYm3ToazZzkCgW2+CZ/J2U hhfw60F2Qm7si2756umN4lwThsM203wi//OmX0J0kjDlg985vYhQEKTCqueTP2UV kDzpE/oB8GBb+CJbNUqLGbxJOgEuSC0z9vM+x2Ww51wVn/l8sjxppyL2FjhoSL01 Vx6r1s83hpycueL7KTlaR6mZjCTVOpDuWCJukALnWIg8mOxuOWI= =rDwI -----END PGP SIGNATURE----- --Apple-Mail=_CCBF5708-6EA7-47BF-81DE-F50EE0E4963C-- --===============3066534294271005018== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============3066534294271005018==-- From ipp-bounces@pwg.org Wed Mar 6 10:20:30 2019 Return-Path: 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 EB3721312AC for ; Wed, 6 Mar 2019 10:20:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.392 X-Spam-Level: X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, TRACKER_ID=1.306, URIBL_BLOCKED=0.001] autolearn=no 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 mEwSkSRmYWgc for ; Wed, 6 Mar 2019 10:20:27 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id A3A82131232 for ; Wed, 6 Mar 2019 10:20:27 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 872363F4B; Wed, 6 Mar 2019 18:20:25 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 9609426AA; Wed, 6 Mar 2019 18:20:19 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id CE2133F32; Wed, 6 Mar 2019 18:20:18 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 8F9F824D3 for ; Wed, 6 Mar 2019 18:20:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551896415; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hnwRyhBMkq80OZ+xz2xFn7w35hS4/agghWpqvLUuvA4=; b=c7Y2hqgfJyjcVialm5wR8sjhaPp+8c6mfap3Grp5kmugsDiOHx+qx2KJ1DO7UiiCj0ZmAywtyUymlPyrgS81whZ4fP8O7iuVITuIeOqjS+bviLuNycNP+2xmFlOUVVtW1R9Xg1yz7nCDSeXvVY1tSmym0uryZgcwMmTBXthaIwQ= Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01lp2055.outbound.protection.outlook.com [104.47.34.55]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-121-YjgKKr6wPTaO-7L7LQtA8A-1; Wed, 06 Mar 2019 13:20:11 -0500 X-MC-Unique: YjgKKr6wPTaO-7L7LQtA8A-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0680.NAMPRD84.PROD.OUTLOOK.COM (10.169.16.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Wed, 6 Mar 2019 18:20:09 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Wed, 6 Mar 2019 18:20:08 +0000 To: Michael Sweet Thread-Topic: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? Thread-Index: AQHUz6ygHr0UwLDskEmAk4liLFoBzaX1x4gAgAkrkoA= Date: Wed, 6 Mar 2019 18:20:08 +0000 Message-ID: <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> In-Reply-To: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 6a8a5568-534e-4bdb-180e-08d6a2605d92 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0680; x-ms-traffictypediagnostic: CS1PR8401MB0680: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0680; 23:jiLXQHTN8MlsJbK9eltthulqmk9NSsF9cbtBoVe?= =?us-ascii?Q?NqcazRPcVpIxyuk6aGOBlVIjleksw/x4qU1W6Xn7d1xuuGqOMcB/Z9pwGDfl?= =?us-ascii?Q?P5BJyWEOYAW7pNfd2iUmrlkBImXqDMiXm2e+ZYObBHhIqSpGgiHPEZ3VHHS8?= =?us-ascii?Q?kLSzJBJhuVUOQetkJChTDPcsKHDn6cRaf9G1Heryd8lWoPtSLzzrVS6GCXwB?= =?us-ascii?Q?AgeiyvNT95o8vkgxrV3M1v8/uoaqOUp1QCG58W3LFZHeStUiufGhn6BbsqU/?= =?us-ascii?Q?7i8BrlZUSN8nAvBPCg38rtP2mPh0hxLZh2jqxNIAWSbMBpF85EEWk3cohuzo?= =?us-ascii?Q?G4J+5Xg0RRHyDRpvy/O6bKYRh7CN2oUEJoOdG8BW8nadT2Z3pCasPBIIONHC?= =?us-ascii?Q?SrNKZpL/zReoQUGGO0U66dtLSgNyR8zDLD9MDEPmtc/B84SQgY13ZtcK62+e?= =?us-ascii?Q?NRAillJg8Nx0AU4fKKW40JvO7XWTJlIKDSlhhZNrg0dB1jIenuJIP/dWVhr3?= =?us-ascii?Q?JE6qzlLpr3qr/M3NVjouCuucJ/BesqJUgA8qbP9hdDmzKEcJmonVEa68Oyi1?= =?us-ascii?Q?S4AbWZJWa6Fzfdhveo0yKGHJeA0+B7vZTp/DzMNGUupu9s/CQFVMY1gzlkb2?= =?us-ascii?Q?lfRbGVDRxjyFxP8A9aPUKxGjNqNMwK0TT1+kX5VlTNe+EIKKUSgo46cQliAs?= =?us-ascii?Q?y0wtkFj4sqyRDXQlTQIMwm8SySdAwtOZPQclzhYUD5/EXA8pxmWR4EpLx/9/?= =?us-ascii?Q?oIppSkAxzHoy1HLLh1huvXHiESX3KvRe/82sVfPH/BrCpjxKXyPZmuIWcuZJ?= =?us-ascii?Q?LYE5V91qyq9zlFNo1x52HQYI2ibMht0gdMSdgPYwnQZDlC4NVZ9NLuqs02Gq?= =?us-ascii?Q?+HqRYizIxG32uXCKTkS3aZa7TKXWuo5lC22R6nGulDX4ww+u6e02pKeGvqCo?= =?us-ascii?Q?iSnSFfhv9goxdm8V0XKan9ADnC6CY98QiIi2EYQmuATKsKc6hFJkcpJudCmL?= =?us-ascii?Q?8mXTVQkVAwxZN4RbqhsNT1AwBm1gskyxNxN28mdnyWOBgwmUi8EAkSxf7SDB?= =?us-ascii?Q?3V+M4tJd3G+Iwf9vN4FoftFdwQprpZa5KTFS507+y8sO4YYO8lWG+zxclvoF?= =?us-ascii?Q?Vm3vDx8oVT2i3SG0GHRzGPBW2JQrzCFombR1WrQDLRSSmi2ChLvGPCaV1mqi?= =?us-ascii?Q?h9IHAzlaACuJ9QxGuOWMEJ6RYoHk9EQPsL45C6nuoQkG/z8GMzx701hlxmts?= =?us-ascii?Q?0V5CPm+a7lUbsThEbGcoOQoZKd1Dv+SSu9ScwgRyX7lCUCcetP8JSMQQ2yfq?= =?us-ascii?Q?wVJOw58WyZ05XwHJPgSTE0uI=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 0968D37274 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(366004)(39860400002)(346002)(136003)(199004)(189003)(6602003)(81156014)(14444005)(102836004)(256004)(6116002)(81166006)(8676002)(36756003)(7736002)(8936002)(3846002)(82746002)(68736007)(97736004)(33656002)(14454004)(66066001)(229853002)(5660300002)(25786009)(186003)(4326008)(6436002)(2906002)(6486002)(106356001)(86362001)(316002)(26005)(236005)(54896002)(446003)(486006)(2616005)(478600001)(476003)(6512007)(11346002)(99936001)(53936002)(6916009)(105586002)(71200400001)(71190400001)(76176011)(6246003)(99286004)(6506007)(53546011)(83716004); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0680; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 8rXqXvhF/aNo4YQOWAn36l7UVUfgIZAxo/xtZN+/wesVnYVaYz8t1xXhbcqaT3VmHwKuyr+cnNqU7ZjwpqvMiBWqVIHHQoSwkZ6ABinyOrnywr32tM7P+gE4rofkyDUF8ax+8sHHgM5skFpj1Rz+S2Jyp51wNrk0WR0itJSm4xcS5+LJ+nHd3c3pQY08fLUnxDa1DBZmL/T2lfw3rIVT9rtKW7aImf/+3lRncy243kk3F8Mc7M9EcUzrnxcw1T4sCPi3HTmaNkTSAJ6LsNQEQLq+GT9ys54x4FNLXt/r/7Vlzd8GH0WhGAXDTd/iNaSLB8Ufg9NmWohnRgfS4OiN/yM7evAqivCmlu2fVPvxMmNt0CKpINOO/xesiJ8T+ApT9ShBeMBHKX1TzhBJPj68TQnZTsldmw715LdfhXiZdUo= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 6a8a5568-534e-4bdb-180e-08d6a2605d92 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 18:20:08.9138 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0680 Cc: PWG IPP WG Reflector Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============4694103997949327525==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4694103997949327525== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_0BC37D00-EF49-46D8-BD95-6AAC33D46A55"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_0BC37D00-EF49-46D8-BD95-6AAC33D46A55 Content-Type: multipart/alternative; boundary="Apple-Mail=_A344E3EE-5284-4035-B47A-9382388A19C9" --Apple-Mail=_A344E3EE-5284-4035-B47A-9382388A19C9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I have a draft of IPP Enterprise Printing Extension (EPE) I'm chipping = away at - here's what it has thus far: Added: job-password-length-supported (from Job Password Repertoire = registration) job-password-repertoire-configured/-supported (from Job Password = Repertoire registration) job-print-password/-default/-supported (to be debated) job-storage/-default/-supported (to be debated) Removed: feed-orientation/-default/-supported job-save-disposition/-etc (all related Job Template, Job Description and = Printer Description attributes) job-creation-attributes-supported job-hold-until-time/-supported job-ids/-supported (REQUIRED) job-spooling-supported media-col.media-tooth media-col.media-grain media-col.media-thickness media-col-database printer-detailed-status-messages which-jobs-supported Cancel-Jobs Cancel-My-Jobs Close-Job Kept: job-password job-password-encryption proof-print/-default/-supported Additional keywords for "which-jobs" ('proof-print' and 'stored' defined = locally, 'saved' to be deprecated) I have a few questions too: Questions: job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, = why not? job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? If = not, why not? job-delay-output-until-time/-supported --> Job Extensions v1.1? If not, = why not? job-phone-number/-default/-supported --> Job Extensions v1.1? Separate = registration? (Use case is ambiguous...) job-recipient-name/-default/-supported --> Job Extensions v1.1? Separate = registration? (Use case is ambiguous...) job-retain-until/-default/-supported --> Job Extensions v1.1? If not, = why not? job-retain-until-time/-default/-supported --> Job Extensions v1.1? If = not, why not? > On Feb 28, 2019, at 3:17 PM, Michael Sweet wrote: >=20 > These all have a clear focus on jobs and job submission/creation and = are definitely not limited to the scope of Enterprise Printing. There = is a slight process issue we need to discuss, however: the new Job = Extensions will have conformance requirements for required operations = and attributes that were not in v1.0 of Job Extensions but *were* in = v1.0 of JPS2 - the errata process doesn't allow us to change conformance = requirements without going through PWG Last Call and Formal Vote, but = then we are kindof merging JOBEXT and JPS2 into a single errata update = and publishing a new Enterprise Printing specification with updated JPS2 = content. Fuzzy logic... :) We should account for this in Process 4.0 somehow. >=20 > Anyways, since this constitutes all of the non-obsoleted/migrated = content from JPS2, I'd prefer to update things in one shot rather than = processing two documents. +1 --Apple-Mail=_A344E3EE-5284-4035-B47A-9382388A19C9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
    I have a draft of IPP Enterprise Printing Extension (EPE) I'm = chipping away at - here's what it has thus far:

    Added:
    job-password-length-supported (from Job Password Repertoire = registration)
    job-password-repertoire-configured/-supported (from Job = Password Repertoire registration)
    job-print-password/-default/-supported (to = be debated)
    job-storage/-default/-supported (to be debated)

    Removed:
    feed-orientation/-default/-supported
    job-save-disposition/-etc (all related Job = Template, Job Description and Printer Description = attributes)
    job-creation-attributes-supported
    job-hold-until-time/-supported
    job-ids/-supported (REQUIRED)
    job-spooling-supported
    media-col.media-tooth
    media-col.media-grain
    media-col.media-thickness
    media-col-database
    printer-detailed-status-messages
    which-jobs-supported
    Cancel-Jobs
    Cancel-My-Jobs
    Close-Job

    Kept:
    job-password
    job-password-encryption
    proof-print/-default/-supported
    Additional keywords for "which-jobs" = ('proof-print' and 'stored' defined locally, 'saved' to be = deprecated)

    I have a few = questions too:

    Questions:
    job-cancel-after/-default/-supported --> Job Extensions = v1.1? If not, why not?
    job-delay-ouptut-until/-default/-supported --> Job = Extensions v1.1? If not, why not?
    job-delay-output-until-time/-supported = --> Job Extensions v1.1? If not, why not?
    job-phone-number/-default/-supported = --> Job Extensions v1.1? Separate registration? (Use case is = ambiguous...)
    job-recipient-name/-default/-supported --> Job Extensions = v1.1? Separate registration? (Use case is = ambiguous...)
    job-retain-until/-default/-supported --> Job Extensions = v1.1? If not, why not?
    job-retain-until-time/-default/-supported = --> Job Extensions v1.1? If not, why = not?


    On Feb = 28, 2019, at 3:17 PM, Michael Sweet <msweet@apple.com> = wrote:

    These all have a clear focus on jobs and job = submission/creation and are definitely not limited to the scope of = Enterprise Printing.  There is a slight process issue we need to = discuss, however: the new Job Extensions will have conformance = requirements for required operations and attributes that were not in = v1.0 of Job Extensions but *were* in v1.0 of JPS2 - the errata process = doesn't allow us to change conformance requirements without going = through PWG Last Call and Formal Vote, but then we are kindof merging = JOBEXT and JPS2 into a single errata update and publishing a new = Enterprise Printing specification with updated JPS2 content.  Fuzzy = logic... :)

    We should account for this in Process 4.0 = somehow.


    Anyways, = since this constitutes all of the non-obsoleted/migrated content from = JPS2, I'd prefer to update things in one shot rather than processing two = documents.

    +1


    = --Apple-Mail=_A344E3EE-5284-4035-B47A-9382388A19C9-- --Apple-Mail=_0BC37D00-EF49-46D8-BD95-6AAC33D46A55 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyAD1gACgkQqskbKLDW 1N0vUBAAiETBWm6kLgVrx6J55I2C2g5RuCB6tmWAV/cNA+QtXgbYyjtI5OYdE5OB zWvs5fyKm6nP6hux3TOJI8BBKJIp+eoKPGeodb/u4r6L2irmLyDXMjtbKBPLYQIR 09h38bsSeFHkGygONpuZOPTkPlOfmwbKtZMZoKvoX0auXpkXwbcMLhjf1Eqxe7+8 Ayickic+4iZ8/syQwKRIIrahV285K+SdPMz+OVY6g0AFApPc5e83wKt26H2EjtMg FKw780eVnyP2F8E+KNWaSxmGHPuZdx0YJmHjHsnofLudOFqZWTSGcRKSY4NG24rk Jd1NCD60zUv13TfOfuF3fe//eTOiY9hERVVS2A1jNFS9mQ/m2bQMupRlyM5WvTpc E8fPdJjCDpGNtifYirGcOGB7jqKJXl4FkzFBsfW50Im6Z1hiHbfglo9cojmhZ05E OXyt3MWqSTZ8LozzP96bRylQHejlDqDZrMQOqZiv/ijPdRfgXX1D0KlKoNvXAor8 dcakRfL9MXvYRLVm1m8R7hn2PINOM80j9r3cyPW6TL7rBi+7rdUvu3FLGHZlcROa 2YUIoKJPgvISJwtwKOfOrCBqmisNWUEnTrjAtJH4q0r/auf25BWm8EQAF0Mi+Dvh XudGkwax1LyzM855Y7qTCTDefaJJUxoom97tg1bUkGWT3PP279o= =WFu/ -----END PGP SIGNATURE----- --Apple-Mail=_0BC37D00-EF49-46D8-BD95-6AAC33D46A55-- --===============4694103997949327525== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4694103997949327525==-- From ipp-bounces@pwg.org Wed Mar 6 10:44:46 2019 Return-Path: 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 2AB8B1310FC for ; Wed, 6 Mar 2019 10:44:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 U3ubt_S0JLOz for ; Wed, 6 Mar 2019 10:44:41 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id BEA591224E8 for ; Wed, 6 Mar 2019 10:44:38 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 8725E3F4D; Wed, 6 Mar 2019 18:44:37 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 540C526AA; Wed, 6 Mar 2019 18:44:32 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 7BED73F32; Wed, 6 Mar 2019 18:44:30 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id 9FFB1315 for ; Wed, 6 Mar 2019 18:44:29 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x26IaUMl064405; Wed, 6 Mar 2019 10:44:23 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=mqVSKNkaosQCcW6aWL+nUTQ7UoE1MJlYOPOP5zCAgcU=; b=sTSy6vMkMj4OJDAroQdqYTrGxp4b1zy+UO1okfM8r5Cd+BoyBEKOXVRyzEMuz3sPA6It 3fs+S7ocsSmpkykCo7zaY2Yo1GPu0l8vaMm65F71lvkJKlmR38W4KzQQ4Ev6fLTdydgz bx/sGUefG9IXg/qisXrDw+mPZbg7LLWjDUUXf4BArcMPETM7wxHe4FPGkqhiLBMXNrFL w7LHLnTIGb/gL55ce4HH0hyoMdDyVi3OLRtpai/ZZA1M9pW1anmxRsU57V40KbNK0kAd rf1PHZsHKNTok0pNgdf/suU2gsu2vGwExW8sB/vPQtgHrzsCUQnVdpzeWCDatT5n1/AU 7g== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2qyscc92mj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 06 Mar 2019 10:44:23 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNY00FJIK1X7A50@ma1-mtap-s03.corp.apple.com>; Wed, 06 Mar 2019 10:44:23 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNY00100IJBUV00@nwk-mmpp-sz11.apple.com>; Wed, 06 Mar 2019 10:44:22 -0800 (PST) X-Va-A: X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-Va-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-Va-R-CD: c5f53e861a532cef1a8e83cb2834246c X-Va-CD: 0 X-Va-ID: 3048372f-4c28-4282-b6f3-20a6958f8633 X-V-A: X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-V-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-V-R-CD: c5f53e861a532cef1a8e83cb2834246c X-V-CD: 0 X-V-ID: d271eecf-5fca-41e4-83ac-a0e56e1ae4b1 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-06_12:,, signatures=0 Received: from [17.235.6.111] by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNY00ABXK1VJO60@nwk-mmpp-sz11.apple.com>; Wed, 06 Mar 2019 10:44:22 -0800 (PST) In-reply-to: <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> Date: Wed, 06 Mar 2019 13:44:19 -0500 Message-id: References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> To: "Kennedy, Smith (Wireless & Standards Architect)" X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-06_12:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============5900360913429203992==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5900360913429203992== Content-type: multipart/alternative; boundary="Boundary_(ID_xcsXSpxBCyLUlt5WumO42Q)" --Boundary_(ID_xcsXSpxBCyLUlt5WumO42Q) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Smith, > On Mar 6, 2019, at 1:20 PM, Kennedy, Smith (Wireless & Standards Architect) wrote: > ... > Kept: > job-password > job-password-encryption > proof-print/-default/-supported > Additional keywords for "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be deprecated) OK, so I'll define the standard which-jobs values in Job Extensions, and you'll define the new ones for EPE? > I have a few questions too: > > Questions: > job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, why not? More advanced job management seems more enterprise-y to me, but I'm good either way. > job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? If not, why not? > job-delay-output-until-time/-supported --> Job Extensions v1.1? If not, why not? Likewise, these seem like an enterprise job scheduling feature. > job-phone-number/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...) > job-recipient-name/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...) Recipient/contact information for the job seems like an enterprise or light-production use case. > job-retain-until/-default/-supported --> Job Extensions v1.1? If not, why not? > job-retain-until-time/-default/-supported --> Job Extensions v1.1? If not, why not? I believe these were intended to resolve the ambiguity with how long a proof print/stored job is retained. Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?) >> On Feb 28, 2019, at 3:17 PM, Michael Sweet > wrote: >> >> These all have a clear focus on jobs and job submission/creation and are definitely not limited to the scope of Enterprise Printing. There is a slight process issue we need to discuss, however: the new Job Extensions will have conformance requirements for required operations and attributes that were not in v1.0 of Job Extensions but *were* in v1.0 of JPS2 - the errata process doesn't allow us to change conformance requirements without going through PWG Last Call and Formal Vote, but then we are kindof merging JOBEXT and JPS2 into a single errata update and publishing a new Enterprise Printing specification with updated JPS2 content. Fuzzy logic... :) > > We should account for this in Process 4.0 somehow. > >> >> Anyways, since this constitutes all of the non-obsoleted/migrated content from JPS2, I'd prefer to update things in one shot rather than processing two documents. > > +1 > > _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_xcsXSpxBCyLUlt5WumO42Q) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Smith,

    On Mar 6, 2019, at 1:20 PM, = Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    ...
    Kept:
    job-password
    job-password-encryption
    proof-print/-default/-supported
    Additional keywords for = "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be = deprecated)
    OK, so I'll define the standard which-jobs values in = Job Extensions, and you'll define the new ones for EPE?

    I have a few questions too:

    Questions:
    job-cancel-after/-default/-supported --> = Job Extensions v1.1? If not, why = not?

    More advanced job management seems more enterprise-y to = me, but I'm good either way.

    job-delay-ouptut-until/-default/-supported --> Job = Extensions v1.1? If not, why not?
    job-delay-output-until-time/-supported --> = Job Extensions v1.1? If not, why = not?

    Likewise, these seem like an enterprise job scheduling = feature.

    job-phone-number/-default/-supported --> Job Extensions = v1.1? Separate registration? (Use case is = ambiguous...)
    job-recipient-name/-default/-supported --> Job Extensions = v1.1? Separate registration? (Use case is = ambiguous...)
    =
    Recipient/contact information for the job seems = like an enterprise or light-production use case.

    job-retain-until/-default/-supported --> Job Extensions = v1.1? If not, why not?
    job-retain-until-time/-default/-supported --> Job = Extensions v1.1? If not, why = not?
    I believe these were intended to resolve the ambiguity = with how long a proof print/stored job is retained.  Also, I don't = think we want a job-retain-until-time-default, since the value is an = absolute dateTime value (unless we make -time an integer and add a -date = version for dateTime?)


    On Feb = 28, 2019, at 3:17 PM, Michael Sweet <msweet@apple.com> = wrote:

    These all have a clear focus on jobs and job = submission/creation and are definitely not limited to the scope of = Enterprise Printing.  There is a slight process issue we need to = discuss, however: the new Job Extensions will have conformance = requirements for required operations and attributes that were not in = v1.0 of Job Extensions but *were* in v1.0 of JPS2 - the errata process = doesn't allow us to change conformance requirements without going = through PWG Last Call and Formal Vote, but then we are kindof merging = JOBEXT and JPS2 into a single errata update and publishing a new = Enterprise Printing specification with updated JPS2 content.  Fuzzy = logic... :)

    We should account for this in Process 4.0 = somehow.


    Anyways, = since this constitutes all of the non-obsoleted/migrated content from = JPS2, I'd prefer to update things in one shot rather than processing two = documents.

    +1



    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_xcsXSpxBCyLUlt5WumO42Q)-- --===============5900360913429203992== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5900360913429203992==-- From ipp-bounces@pwg.org Wed Mar 6 11:27:14 2019 Return-Path: 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 E96AD1311CD for ; Wed, 6 Mar 2019 11:27:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 wl0HCX8MPaze for ; Wed, 6 Mar 2019 11:27:13 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8E0130F2C for ; Wed, 6 Mar 2019 11:27:13 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id DA1543F9B; Wed, 6 Mar 2019 19:27:09 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 10D0C315; Wed, 6 Mar 2019 19:27:06 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B0F063F32; Wed, 6 Mar 2019 19:27:04 +0000 (UTC) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) by www.pwg.org (Postfix) with ESMTPS id 430C8315 for ; Wed, 6 Mar 2019 19:27:04 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x26JHEun062858 for ; Wed, 6 Mar 2019 11:27:03 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=QbR16lQzhXwA30KqDfB0W5KS6Rb5tZ/d6YuwcozoaQM=; b=bd/6Y1d2xwbYiNA3QYf0lJSy3fbu5De/T75cH3BFYCA9L29e2wWAWVEFUZ2lPxbsFgsA 9hymzJLA+Sn9B0YVjY+K9UDSB61+SLPl25IOyiXCrcQX+OBOoPofxtd1FtOeiqVo1ZHn 3JSNpCBGNqiHtg2VobItfAI4ux/fgU9kC6rF0ypTP/VZq+GN6KYwd8OvLI4fzWY2vZn9 MSyiwRKuNUqWGNz/Nt6JeXDPE3ME1YJmihp28aDmeLEC7uZrHK2NZfJ7z/1jIV1JyM2o RLA6b0o6KZ1g+u+2q1d2Lc2N0deDF2Nua0Ef9+ZCs5qS/2hjUtrMrReuTxetoXqLTSPN mw== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2qysq4w0tc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 06 Mar 2019 11:27:03 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNY00JOTM10INE0@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Wed, 06 Mar 2019 11:27:03 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNY00900LY8KU00@nwk-mmpp-sz11.apple.com>; Wed, 06 Mar 2019 11:27:02 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: 70cfd2a49edfa29fe8fb91fbea5811c9 X-Va-R-CD: 406c0bfea6a77fff171f91c3e6c7fb3c X-Va-CD: 0 X-Va-ID: fd4a7681-ba87-4c0d-be79-5c3b5c1be3c0 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 70cfd2a49edfa29fe8fb91fbea5811c9 X-V-R-CD: 406c0bfea6a77fff171f91c3e6c7fb3c X-V-CD: 0 X-V-ID: d061fd78-ff21-47f4-a119-8199e01bdfee X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-06_12:,, signatures=0 Received: from [17.235.6.111] by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNY000TLM10UW50@nwk-mmpp-sz11.apple.com>; Wed, 06 Mar 2019 11:27:02 -0800 (PST) Date: Wed, 06 Mar 2019 14:27:00 -0500 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-06_12:, , signatures=0 Subject: [IPP] RFC: DEPRECATED and OBSOLETED definitions X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============4399954818412210899==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4399954818412210899== Content-type: multipart/alternative; boundary="Boundary_(ID_rh2eGICTjRvwbIMCOILXww)" --Boundary_(ID_rh2eGICTjRvwbIMCOILXww) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All, Here is my proposed text for deprecations and obsoletions in the conformance section of new IPP specifications: The term DEPRECATED is used for previously defined and approved items that SHOULD NOT be used or implemented. The term OBSOLETED is used for previously defined and approved items that MUST NOT be used or implemented. Thoughts? _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_rh2eGICTjRvwbIMCOILXww) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All,

    Here = is my proposed text for deprecations and obsoletions in the conformance = section of new IPP specifications:

    The term DEPRECATED is used = for previously defined and approved items that SHOULD NOT be = used or implemented. The term OBSOLETED is used for = previously defined and approved items that MUST NOT be used or = implemented.

    Thoughts?

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    = --Boundary_(ID_rh2eGICTjRvwbIMCOILXww)-- --===============4399954818412210899== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4399954818412210899==-- From ipp-bounces@pwg.org Wed Mar 6 11:33:35 2019 Return-Path: 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 5AD3D1275F3 for ; Wed, 6 Mar 2019 11:33:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 6SylRcFbU2I9 for ; Wed, 6 Mar 2019 11:33:32 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 9532A1224E8 for ; Wed, 6 Mar 2019 11:33:32 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 422133F9B; Wed, 6 Mar 2019 19:33:31 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 16CEB3F48; Wed, 6 Mar 2019 19:33:15 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 31F883F32; Wed, 6 Mar 2019 19:33:13 +0000 (UTC) Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) by www.pwg.org (Postfix) with ESMTPS id 6A3722618; Wed, 6 Mar 2019 19:33:12 +0000 (UTC) Received: by mail-yw1-xc2a.google.com with SMTP id v201so11012847ywa.9; Wed, 06 Mar 2019 11:33:12 -0800 (PST) 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; bh=CC3vSwuhqyQWUJvHZWXtTarTL/Wns68zlotSZdk+U3o=; b=P3Apn9g+xV4VI74Ytc7uDes0zmt2+LIkFwwqpOaGfrS4pc1sY4/IPhCCrO7bkAiEh6 pf1IIuxD3RnduejvJdRmmDqkeI8Lsq5lTGiSrtPEMU+qeXUAub11UDiywb8/X1CB/cv0 2ORlUy5a6VdRKUqpLkrPFNCYEnKuJ7BKYS4y6DMqjT7Yih2yHi1adMJtB0XSUDycHwDH +wvGySBOPl1PE+7UBeCrauaWRUP6YYem9IOzb53CQtyxHDWln6F6V8XfuAvjklf/HWBz rivgDMvM6vHgeDwLr3X9x5n20WpDYMR46KMA80L8q426Li6HJEo6bUkAjULDr4VE7H8y z6uw== 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; bh=CC3vSwuhqyQWUJvHZWXtTarTL/Wns68zlotSZdk+U3o=; b=p2jCeullf3Hww5ei1wT2TxLqmVnWc9N7ZUz0HIwdXsCCRh95VZnpczpq6N2CCHAkV8 8MFmGnozin52+O41NXqqnkJaEimQy7WhmZbjxEUKJD7fH1u95eIv3gtfn4/ReGOBuu8U f4KIMszd8webhdN/6tWNNvflgAg2U+4xlCKCOg5WNLiHVgUZvjf23cPragSeilfNVO0a Us1+a4MkGC6eZr1TuspeW7QffBzP1KipuaJsv9UhbgtVZV8V5Z89MEFdPgF0tvdnMxig Izd7FzPEh+DqneBUXVF0U0SLS8/BVRTb9OwyfgIMNgjlnWwpQgBsM6gLRHGCjvOg9gdX iKhg== X-Gm-Message-State: APjAAAWT8TfLs8afWl86cS/DDGDE6UxRNiwAG1KMT4KuM5CUf2k/m80I aRGSxTbH3gQIeHFlr5KAmNgRbdyi8WDJKyKeDdmhzA== X-Google-Smtp-Source: APXvYqxCndofxvqfbi3RoZhwC/ukGr5WNXkO4t429+k3IrfONqu/j6BpWRGnjCIh3hajQXdAePM+yBrjpgDXTluIbO0= X-Received: by 2002:a25:2605:: with SMTP id m5mr8192867ybm.194.1551900791442; Wed, 06 Mar 2019 11:33:11 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 6 Mar 2019 14:32:58 -0500 Message-ID: To: "ids@pwg.org" , Uptane Forum , tms_wg@trustedcomputinggroup.org, MPWG , tnc@trustedcomputinggroup.org, neteq@trustedcomputinggroup.org, "ipp@pwg.org" , Ira McDonald Subject: [IPP] Fwd: [tc-forum] NIST Threshold Cryptography Workshop 2019: Live Webcast X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============2121243320107895751==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2121243320107895751== Content-Type: multipart/alternative; boundary="000000000000669bcc0583720f4b" --000000000000669bcc0583720f4b Content-Type: text/plain; charset="UTF-8" FYI ---------- Forwarded message --------- From: 'Mouha, Nicky W. (IntlAssoc)' via tc-forum Date: Wed, Mar 6, 2019 at 2:06 PM Subject: [tc-forum] NIST Threshold Cryptography Workshop 2019: Live Webcast To: tc-forum@list.nist.gov Dear subscribers of the NIST Threshold Crypto forum, For the workshop, *in-person registration closed *on March 4, 2019. We are offering a *free live webcast option*. https://appam.certain.com/profile/form/index.cfm?PKformID=0x50009abcd *WEBCAST option*: Webcast registration is not required to view the live stream, but registered viewers will receive a reminder and updates prior to the webcast. You may participate by emailing your questions or comments to ntcw2019@nist.gov or join our Twitter chat using *#NTCW2019*. Requirements: You will need a broadband connection and a current browser with Adobe Flash and/or HTML 5 support. Caption features may not be available on iOS or Android devices. If you're having trouble viewing the live stream, please try *refreshing the page* to reconnect to the live video. You can also try another browser such as Chrome. If you still can't see the video you may have a firewall issue. Each live webcast will provide an alternate YouTube link the day of the event. A full recording will also be available within one week of the event. *All visitors to the NIST campus must be pre-registered. There is no onsite registration for meetings held at NIST.* Regards, Nicky On behalf of the Threshold Cryptography Team -- To unsubscribe from this group, send email to tc-forum+unsubscribe@list.nist.gov Visit this group at https://groups.google.com/a/list.nist.gov/d/forum/tc-forum --- You received this message because you are subscribed to the Google Groups "tc-forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to tc-forum+unsubscribe@list.nist.gov. --000000000000669bcc0583720f4b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    FYI

    ---------- Forwarded message ---------
    From: 'Mouha, Nicky W. (IntlAssoc)' = via tc-forum <tc-forum@list.nist.gov>
    Date: Wed, Mar 6, 2019 at 2:= 06 PM
    Subject: [tc-forum] NIST Threshold Cryptography Workshop 2019: Liv= e Webcast
    To: tc-forum@list.ni= st.gov <tc-forum@list.nist= .gov>


    Dear subscribers of the NIST Threshold Crypto forum,

    For the workshop, in-person registration closed on March 4, 201= 9. We are offering a free live webcast option.=C2=A0=C2=A0


    WEBCAST option: Webcast registration is not required to view th= e live stream, but registered viewers will receive a reminder and updates p= rior to the webcast. You may participate by emailing your questions or comm= ents to ntcw2019@nist.gov=C2=A0or join our Twitter chat using #NTCW2019.=

    Requirements: You will need a broadband connection and a current brows= er with Adobe Flash and/or HTML 5 support. Caption features may not be avai= lable on iOS or Android devices. If you're having trouble viewing the l= ive stream, please try refreshing the page to reconnect to the live video. You can also try= another browser such as Chrome. If you still can't see the video you m= ay have a firewall issue. Each live webcast will provide an alternate YouTu= be link the day of the event. A full recording will also be available within one week of the event.

    All visitors to the NIST campus must be pre-registered.=C2=A0 There= is no onsite registration for meetings held at NIST.

    Regards,
    Nicky
    On behalf of the Threshold Cryptography Team

    --
    To unsubscribe from this group, send email to tc-forum+unsubscribe@list.nist= .gov
    Visit this group at https://groups.google.com/a/list.nist.gov= /d/forum/tc-forum
    ---
    You received this message because you are subscribed to the Google Groups &= quot;tc-forum" group.
    To unsubscribe from this group and stop receiving emails from it, send an e= mail to tc-forum+unsubscribe@list.nist.gov.
    --000000000000669bcc0583720f4b-- --===============2121243320107895751== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2121243320107895751==-- From ipp-bounces@pwg.org Wed Mar 6 12:41:28 2019 Return-Path: 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 96F2013126B for ; Wed, 6 Mar 2019 12:41:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.27 X-Spam-Level: X-Spam-Status: No, score=-2.27 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 7U1A51tpmfFD for ; Wed, 6 Mar 2019 12:41:23 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 56FA81311CE for ; Wed, 6 Mar 2019 12:41:21 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id D05EF3F52; Wed, 6 Mar 2019 20:41:20 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 7CCF226AA; Wed, 6 Mar 2019 20:41:14 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 2EBDC3F32; Wed, 6 Mar 2019 20:41:13 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 3C8C224D3 for ; Wed, 6 Mar 2019 20:41:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551904870; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=K3uYIqsCSll2buBOIG3iRi1hhj2Ddwuii5NQvdzrTWI=; b=h4BrjIAt+NNe9vbeINUDj0BgBN4/c5YzNOJ0inN+U/W9r2kTlfZGSs/r4HziObSeELdUCoiJwDZrl2PRb2BT71A+RahD8BdpiPNNLYdtinKTIE7uqIYF2b/cmuD8ZystXzjIa3pDPEz+Lou+EILoC63p3JQT4WfjR3mwVE6UVHg= Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp2054.outbound.protection.outlook.com [104.47.40.54]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-236-qAesD-pPPaWHZ4xxOubH0Q-1; Wed, 06 Mar 2019 15:41:08 -0500 X-MC-Unique: qAesD-pPPaWHZ4xxOubH0Q-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1015.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.19; Wed, 6 Mar 2019 20:41:06 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Wed, 6 Mar 2019 20:41:06 +0000 To: Michael Sweet Thread-Topic: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? Thread-Index: AQHUz6ygHr0UwLDskEmAk4liLFoBzaX1x4gAgAkrkoCAAAbDgIAAIJ8A Date: Wed, 6 Mar 2019 20:41:06 +0000 Message-ID: References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 976c5c75-7fe6-4ce1-e241-08d6a2740e8f x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1015; x-ms-traffictypediagnostic: CS1PR8401MB1015: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB1015; 23:9FsYURFMuu+hAu1BTjDqv1qRj2gAQUdi/+sR+8Y?= =?us-ascii?Q?/vZceHYJoZk7+xsRABLtpGNRfG8xFdpbsZH4YPEmTQk++jZoogwnWrFdosII?= =?us-ascii?Q?c6LiOeyXbnumIl/ElzT4aaKbKiVejptFWepOhyVOJUgYSRuOWjlOMRG5nmPz?= =?us-ascii?Q?b5dbzxNBGs1q0f6OWaTo/86+jgByXK5Dudwf+OvcTRE+fCuPvP1815w6oDs2?= =?us-ascii?Q?G3ULPFBF1AombpeArfQhV8Y1jImpwg99JL2ojr25bcZvfRxPdUyUrHPt8mLv?= =?us-ascii?Q?fUZ/jjzUVxGsDUZ4M9zUXjmKbKcXejUDGg9niSzPSeECP1OlCLBFfgXIuXbu?= =?us-ascii?Q?4KVxUtVOSrJ9y3t5MEWuH3oPUvMSXmztEX+HL5gLDnrSPKhq9G6Ybz57nfvG?= =?us-ascii?Q?AwQrSHi9LAjazXYLiw87seGIAlrzljVu7cDRPZm1U7E61eiwpsScLT53WcYV?= =?us-ascii?Q?FAgTtSUsn1rfyv9CXpZAXGzUonCRHwcIB03wD9d6gs/6NxDYaynvQ7Q71jhi?= =?us-ascii?Q?1KBOihz8Bp0UvToNPDrq+GLV4esfv4uiWnj3vwmDqUUfq6fqxSWWdOZdJHr7?= =?us-ascii?Q?W5ZG4ci44zoIUVNrMrTH1b+vSc5O1FRufvUifO5XZPlMDuDOYRMd0J7rJ2Wt?= =?us-ascii?Q?7AipIe2Xa9aS30/HB5P2XL8Cah0jlszAvAhvIcjKXWeRr/0EHrctIo6tGVVy?= =?us-ascii?Q?O9RhP5edx2shvKm1y2ljN1dhU8KsWNszoOOM3xZabzWsqU0oWkhuf6rThtIj?= =?us-ascii?Q?uIgq7u+ID73ojg8nBAtueGaPr9jpPnxfuP80JEi8wxhJk2i9IedsMySUT7Ev?= =?us-ascii?Q?XWzfjJVocWv6NhWRzbeGuQ2SKC6eYvwvsGO05TC+eDrZIo4qQfb4QhUeScwU?= =?us-ascii?Q?sGuRd0NVUD0baF7i5nAPGjYfFftnP069wVsbPGXSk1jR7Ds//mjoVZ0IK9YS?= =?us-ascii?Q?tDV2VLYWEVSks+HJYRqcV/FgfFH7Tb/PZRWw4jz3TX82FS5rLQeZkSliKJkL?= =?us-ascii?Q?DLWloPh4x9GHSQy4P4m9PHieE0vvSDZHHfj+zIe5fhp4WXhcZg03vYydx0Qe?= =?us-ascii?Q?XuqeskbnYvnMwDUY7X3Ev6h/5vkZRT4zXrEf7asG3NLv3QjMtaRliW1G5E/H?= =?us-ascii?Q?TH22Fn6SJfn5wuPxhCIY/lTuQCxOypmYXtw7yI7+NJEfxwTfYVU+x+WeMJOP?= =?us-ascii?Q?XFAy2RLKLsItyxNo1hjwc9jYLEwjiNHSS9pKMKtzNkWTjvuiNGA6szkPOoaZ?= =?us-ascii?Q?Y8XiV4eKAMgzcUwPMX0WVs27rTMuNexxCP1j5QlIZ1+70ydwKE7zA3cnK/R7?= =?us-ascii?Q?W8VBNMNN622kvHdVfsvpxAFKye3mwCEXLwuxVVBSaveDl?= x-microsoft-antispam-prvs: x-forefront-prvs: 0968D37274 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(376002)(39860400002)(136003)(396003)(6602003)(199004)(189003)(186003)(14444005)(81166006)(81156014)(14454004)(83716004)(71190400001)(102836004)(82746002)(229853002)(33656002)(66066001)(6916009)(71200400001)(478600001)(53936002)(8676002)(86362001)(2906002)(316002)(76176011)(5660300002)(99286004)(25786009)(6506007)(7736002)(53546011)(106356001)(6486002)(6512007)(97736004)(105586002)(476003)(11346002)(26005)(93886005)(2616005)(486006)(4326008)(8936002)(68736007)(6436002)(3846002)(256004)(6116002)(6246003)(54896002)(36756003)(99936001)(236005)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1015; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: T0lxlu9sja2P79Hj9M0DeA4uR9Nx3kRdtwQb8JadYZ3mPRPao/oarUWfRiSVuNJiTspb4kLsrSv6Ie3QoNEYYMNIgIJGglfza55W/xPo2g8eaDp6zRDSWiZSRtomTJZ8+iXezY2KiHg5se0F/xUfqq8bslLoXTjm49VV7PeX8CJ/QMsYjmRxgrd1huShlHFuuFc8Ckl/0FZbVCiesd3Y1uGqf+3jLYh3pBG1TSdtyaKDaoRx55E8K2Q16kv1ruueyiCrZHhuxaADIlGMRLxViP/o372zqGJqoi1KPgMT+UPE0wPbpcrZ0xHn1dmXMFctyCYKPXyjNn8ImbFn4KpfWP0g01Qi8fpIsGidBMFCfE3hsN+jr7wm2kEJIzSFatmcGQlKAUQ+iwGZWkV2OZFrQ9n8KhYDOpO9/nQcveQZt6k= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 976c5c75-7fe6-4ce1-e241-08d6a2740e8f X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 20:41:06.3099 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1015 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============7627191363215052987==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============7627191363215052987== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_689EE48E-0E01-412D-9D33-7275B7AC23AF"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_689EE48E-0E01-412D-9D33-7275B7AC23AF Content-Type: multipart/alternative; boundary="Apple-Mail=_0556891A-8E0E-48BA-AFC2-8B2832496C1E" --Apple-Mail=_0556891A-8E0E-48BA-AFC2-8B2832496C1E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 6, 2019, at 11:44 AM, Michael Sweet wrote: >=20 > Smith, >=20 >> On Mar 6, 2019, at 1:20 PM, Kennedy, Smith (Wireless & Standards = Architect) > wrote: >> ... >> Kept: >> job-password >> job-password-encryption >> proof-print/-default/-supported >> Additional keywords for "which-jobs" ('proof-print' and 'stored' = defined locally, 'saved' to be deprecated) >=20 > OK, so I'll define the standard which-jobs values in Job Extensions, = and you'll define the new ones for EPE? That's what I was thinking, and then I'll reference Job Extensions v1.1. >=20 >> I have a few questions too: >>=20 >> Questions: >> job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, = why not? >=20 > More advanced job management seems more enterprise-y to me, but I'm = good either way. No problem - I will leave it in EPE. >=20 >> job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? = If not, why not? >> job-delay-output-until-time/-supported --> Job Extensions v1.1? If = not, why not? >=20 > Likewise, these seem like an enterprise job scheduling feature. I will leave these in EPE. >=20 >> job-phone-number/-default/-supported --> Job Extensions v1.1? = Separate registration? (Use case is ambiguous...) >> job-recipient-name/-default/-supported --> Job Extensions v1.1? = Separate registration? (Use case is ambiguous...) >=20 > Recipient/contact information for the job seems like an enterprise or = light-production use case. OK >=20 >> job-retain-until/-default/-supported --> Job Extensions v1.1? If not, = why not? >> job-retain-until-time/-default/-supported --> Job Extensions v1.1? If = not, why not? >=20 > I believe these were intended to resolve the ambiguity with how long a = proof print/stored job is retained. I thought they could be used more generally but I'm fine with them = staying in EPE. > Also, I don't think we want a job-retain-until-time-default, since = the value is an absolute dateTime value (unless we make -time an integer = and add a -date version for dateTime?) Hmmm, how about just having "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and not bother with = "job-retain-until-date" (dateTime)? >=20 >=20 >>> On Feb 28, 2019, at 3:17 PM, Michael Sweet > wrote: >>>=20 >>> These all have a clear focus on jobs and job submission/creation and = are definitely not limited to the scope of Enterprise Printing. There = is a slight process issue we need to discuss, however: the new Job = Extensions will have conformance requirements for required operations = and attributes that were not in v1.0 of Job Extensions but *were* in = v1.0 of JPS2 - the errata process doesn't allow us to change conformance = requirements without going through PWG Last Call and Formal Vote, but = then we are kindof merging JOBEXT and JPS2 into a single errata update = and publishing a new Enterprise Printing specification with updated JPS2 = content. Fuzzy logic... :) >>=20 >> We should account for this in Process 4.0 somehow. >>=20 >>>=20 >>> Anyways, since this constitutes all of the non-obsoleted/migrated = content from JPS2, I'd prefer to update things in one shot rather than = processing two documents. >>=20 >> +1 >>=20 >>=20 >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer --Apple-Mail=_0556891A-8E0E-48BA-AFC2-8B2832496C1E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

    On Mar 6, 2019, at 11:44 AM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    On Mar = 6, 2019, at 1:20 PM, Kennedy, Smith (Wireless & Standards Architect) = <smith.kennedy@hp.com> wrote:
    ...
    Kept:
    job-password
    job-password-encryption
    proof-print/-default/-supported
    Additional keywords for = "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be = deprecated)

    OK, so I'll define the standard = which-jobs values in Job Extensions, and you'll define the new ones for = EPE?

    That's what I was = thinking, and then I'll reference Job Extensions v1.1.


    I have a few questions too:

    Questions:
    job-cancel-after/-default/-supported --> = Job Extensions v1.1? If not, why = not?

    More advanced job management seems more = enterprise-y to me, but I'm good either = way.

    No problem - I = will leave it in EPE.


    job-delay-ouptut-until/-default/-supported --> Job = Extensions v1.1? If not, why not?
    job-delay-output-until-time/-supported --> = Job Extensions v1.1? If not, why = not?

    Likewise, these seem like an enterprise = job scheduling feature.

    I will leave these in EPE.


    job-phone-number/-default/-supported --> = Job Extensions v1.1? Separate registration? (Use case is = ambiguous...)
    job-recipient-name/-default/-supported --> Job Extensions = v1.1? Separate registration? (Use case is = ambiguous...)

    Recipient/contact information for the = job seems like an enterprise or light-production use = case.

    OK


    job-retain-until/-default/-supported --> Job Extensions = v1.1? If not, why not?
    job-retain-until-time/-default/-supported --> Job = Extensions v1.1? If not, why = not?

    I believe these were intended to resolve = the ambiguity with how long a proof print/stored job is = retained.

    I = thought they could be used more generally but I'm fine with them staying = in EPE.

     Also, I don't think we want a = job-retain-until-time-default, since the value is an absolute dateTime = value (unless we make -time an integer and add a -date version for = dateTime?)

    Hmmm, = how about just having "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and not bother with = "job-retain-until-date" (dateTime)?




    On Feb 28, 2019, at 3:17 PM, Michael Sweet <msweet@apple.com> = wrote:

    These = all have a clear focus on jobs and job submission/creation and are = definitely not limited to the scope of Enterprise Printing.  There = is a slight process issue we need to discuss, however: the new Job = Extensions will have conformance requirements for required operations = and attributes that were not in v1.0 of Job Extensions but *were* in = v1.0 of JPS2 - the errata process doesn't allow us to change conformance = requirements without going through PWG Last Call and Formal Vote, but = then we are kindof merging JOBEXT and JPS2 into a single errata update = and publishing a new Enterprise Printing specification with updated JPS2 = content.  Fuzzy logic... = :)

    We should account for this in Process 4.0 = somehow.


    Anyways, since this constitutes all of = the non-obsoleted/migrated content from JPS2, I'd prefer to update = things in one shot rather than processing two = documents.

    +1



    ______________________________________________________= ___
    Michael Sweet, Senior Printing = System Engineer

    = --Apple-Mail=_0556891A-8E0E-48BA-AFC2-8B2832496C1E-- --Apple-Mail=_689EE48E-0E01-412D-9D33-7275B7AC23AF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyAMGAACgkQqskbKLDW 1N0hFA/9EX4ESAByP6/mlR2kQNZgLdnkYD0kFQlarwXj2YyN3Vo4Hjr0Gheu7EBI GaNpCjhSqDg59a4MTYQzJGjj9uOig8Tr9/MJtoyWG9neDm1FyrKqTxvm940/K4Rd 5i23eouVK7mvQYA9qJ8nWbMxHg/dnV6oiIE5JoW+OnS1CCiN6C6eU4mM0BbxMcjs JZ7a4KXNwupyv+3zlN9GmFVe9U2P/nl32VYYiPQVDuv/1hqLXRn3NBloxmp/VqAf sKUoBB3cd35TcDnlBxt/CrRb3mSZhbEFqGvRkPGzpVTXssv45uhTRfmGB2Scqabs OL+z8j/AY0fdkKc7JVuxqAeOv9qO/WoLqjDq2qal/rD0s9tKiJB5jYFom6MyIM8+ XqBEYt1nIRXxsJ5MKqwy4+lTbQRtGHBLQKdFFGQP3KHQqAltna6Wv/A841dp7Q/2 eqDxQM5w5pVVDdgUPsgcrDSSkcJzaaUuzikSJrUJV3Khnp5bUVkfLXMJNQyo3TJ2 7Npvo74m9jxUbUcTLHTUbmGb/gfh7UULO6bp0z1VQWuUwTeU6dSA4u2x/KAzomIV 5ZhItJAJsYoXgMgZI7Nxl80HWUgCjvd2+rDTwB87JnjRQc99TIhtNKiDJB995TEf Z9iPIt5+4tUiq2KI/J1DJGBzlO6HqZk1nxplfHj4EDytW616VRw= =dwgB -----END PGP SIGNATURE----- --Apple-Mail=_689EE48E-0E01-412D-9D33-7275B7AC23AF-- --===============7627191363215052987== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============7627191363215052987==-- From ipp-bounces@pwg.org Wed Mar 6 13:03:14 2019 Return-Path: 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 D654E126F72 for ; Wed, 6 Mar 2019 13:03:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 i8faulbHSDN2 for ; Wed, 6 Mar 2019 13:03:10 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 79EDE126C15 for ; Wed, 6 Mar 2019 13:03:10 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 068D93F4C; Wed, 6 Mar 2019 21:03:10 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 9396826AA; Wed, 6 Mar 2019 21:03:05 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id AB42F3F32; Wed, 6 Mar 2019 21:03:04 +0000 (UTC) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) by www.pwg.org (Postfix) with ESMTPS id 121BB2618 for ; Wed, 6 Mar 2019 21:03:03 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x26KvR82011385; Wed, 6 Mar 2019 13:02:59 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=2DjMWdFhPZL10Ls3PCb3JjDY6GrKReXmMN0WfjisN48=; b=qvRrIBGulm/oEespQMi5Z66Li51qt4VQSA+yydc1QuyjsHD6XkltVf10cWmz+7LjD/qZ UhrCSh3hoLRD9I8yx1shZUPpPp+ZiG/y+lZSakFEvMaExetjhtql6y7lXZu1S69sLmke fl4jboRT2PiQsj3DLPzKrrokL4nEWCSKytJ4tjk6SFfTMmi0l1Rac22zVQXRcvX8MaSw +O5of6QjevtTSLY98jByk1QUkiDoENd15tImgpYNmfD6DOJfKRfIuLjW9Qw7ms5dTlGn SULdIFX5FMelfzoKpCHpCn4eAY+rIkw6xjBtREcjK0gRakSsmplLkG5uasXps4f3fh/N RA== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2qysq4xm92-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 06 Mar 2019 13:02:59 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PNY009OVQGX4710@ma1-mtap-s01.corp.apple.com>; Wed, 06 Mar 2019 13:02:59 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PNY00800PKIFO00@nwk-mmpp-sz09.apple.com>; Wed, 06 Mar 2019 13:02:57 -0800 (PST) X-Va-A: X-Va-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-Va-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-Va-R-CD: c5f53e861a532cef1a8e83cb2834246c X-Va-CD: 0 X-Va-ID: c753eccb-28f0-436a-81e7-8a0420df1262 X-V-A: X-V-T-CD: 81ca60fce39c2560b6c4a7e5841f9b8f X-V-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-V-R-CD: c5f53e861a532cef1a8e83cb2834246c X-V-CD: 0 X-V-ID: 27675025-5e93-417e-afcb-d4a4aa8afd68 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-06_13:,, signatures=0 Received: from [17.235.6.111] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PNY00KU8QGTS940@nwk-mmpp-sz09.apple.com>; Wed, 06 Mar 2019 13:02:56 -0800 (PST) In-reply-to: Date: Wed, 06 Mar 2019 16:02:52 -0500 Message-id: <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> To: "Kennedy, Smith (Wireless & Standards Architect)" X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-06_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============4739483341011764021==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4739483341011764021== Content-type: multipart/alternative; boundary="Boundary_(ID_wXxlN9JgJfZh4lbp3O2qRw)" --Boundary_(ID_wXxlN9JgJfZh4lbp3O2qRw) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Smith, > On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp wrote: > ... >> Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?) > > Hmmm, how about just having "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) and not bother with "job-retain-until-date" (dateTime)? Let's discuss this at the next concall - I can see a use for both (retain the job for 24 hours, retain the job until the next scheduled update), and a Client can calculate the number of seconds to a specific date/time, but there are still some vagaries due to submission delays and whether the IPP job ticket is used directly and immediately or if it gets "relayed" to the destination output device that is doing the retaining... _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_wXxlN9JgJfZh4lbp3O2qRw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Smith,

    On Mar 6, 2019, at 3:41 PM, = Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> = wrote:
    ...
     Also, I = don't think we want a job-retain-until-time-default, since the value is = an absolute dateTime value (unless we make -time an integer and add a = -date version for dateTime?)

    Hmmm, how about just having = "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) = and not bother with "job-retain-until-date" = (dateTime)?

    Let's = discuss this at the next concall - I can see a use for both (retain the = job for 24 hours, retain the job until the next scheduled update), and a = Client can calculate the number of seconds to a specific date/time, but = there are still some vagaries due to submission delays and whether the = IPP job ticket is used directly and immediately or if it gets "relayed" = to the destination output device that is doing the = retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_wXxlN9JgJfZh4lbp3O2qRw)-- --===============4739483341011764021== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4739483341011764021==-- From ipp-bounces@pwg.org Wed Mar 6 13:42:50 2019 Return-Path: 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 A1999130DD6 for ; Wed, 6 Mar 2019 13:42:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 p72He5-KP5Ay for ; Wed, 6 Mar 2019 13:42:48 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 99498130DEC for ; Wed, 6 Mar 2019 13:42:48 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id AB7DC3F4D; Wed, 6 Mar 2019 21:42:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id A4EDD2618; Wed, 6 Mar 2019 21:42:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B4C023F46; Wed, 6 Mar 2019 21:42:39 +0000 (UTC) Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) by www.pwg.org (Postfix) with ESMTPS id D4E152618 for ; Wed, 6 Mar 2019 21:42:38 +0000 (UTC) Received: by mail-yw1-xc32.google.com with SMTP id x21so11424714ywx.11 for ; Wed, 06 Mar 2019 13:42:38 -0800 (PST) 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=0uVLJCJBqhItk6zy+9IhQbNcByhUFrnUl7VHf+rttZU=; b=jo8I1o4R82AbPb6bIxOUqS+RNkeJtDU+IZO9ThH+uiPu7Jj5GLfSL/2LUUWSusmKMj SqtHmfHq1ij0oTmpjuEvZRRlnjBkRFdWe19gq/7zwMKGSgnBXXWPLYUjmhR6WO8CcsZY bgH84xju+scbCs+FkA/cUQYPdCXQwDnw+mRuOJRRPlK5q/QOB6J1bR4SfBfL/KWlJOCx e48w3A08cmcHKgS7uItmFrxyPpPSNMRUHIgD9qbkwMSfWWiGvTH39AF/55n+QtP8jkH5 1pZW/KsqL8TcbtRtca5coFKdD4044SaP5PrBmwc3NSkIYVAG7fGe9lHKJ9wN0soUnrJ+ pziw== 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=0uVLJCJBqhItk6zy+9IhQbNcByhUFrnUl7VHf+rttZU=; b=GUDEixEZzKoinjntPf9S08WLQMer94G5vzgnkGcc856U8pEYO6s53yCx/J+XG1RnBz zZ5/i1vmlMhW8QrR7gsIeoGbvI8tRFjfjK1a2oH0iom7BnWZCR9gSSHktZZhNTWPzdRr NDCmBBuX8ANkAK3MJiI81iHf3f/4Qqm1ZMfYxyj1jRdk5fmFEiHgcd7uGU1H0utN51nB 9oXstPiNpEDc64Gc/iNAdE6/0xkzc5XBUdsgcUBPAPtWvvdgDVsMGpBM2eceB9wKv7ge MQaaEuTxorarVtY2h9guSF/HwhYH23bXFBQdnSG4++AT6vnB235sMpLYlgYDy7f1VVN+ SuRw== X-Gm-Message-State: APjAAAUQVP4QLMXUTJQCzcrmtnAU3RWgvPusUsKHk5k/VR6Pha8gS3oc +xPpeDcY5nZLz7taRDPtbh/zgQ3q9E1UGuUbCHc= X-Google-Smtp-Source: APXvYqy8cBrGCw9DH5ietgmFnNP6yVJcQ9SQ/pNeNag05JC6PP9jq1btUq1qwywtM3bUVSNqZLSM8GbFzQGdUH7H7qA= X-Received: by 2002:a81:5f86:: with SMTP id t128mr7620544ywb.467.1551908557932; Wed, 06 Mar 2019 13:42:37 -0800 (PST) MIME-Version: 1.0 References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> Date: Wed, 6 Mar 2019 16:44:48 -0500 Message-ID: To: Michael Sweet Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============0295755413623841712==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0295755413623841712== Content-Type: multipart/alternative; boundary="00000000000051cc3b058373dea6" --00000000000051cc3b058373dea6 Content-Type: text/plain; charset="UTF-8" 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp wrote: > Smith, > > On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards > Architect) via ipp wrote: > ... > > Also, I don't think we want a job-retain-until-time-default, since the > value is an absolute dateTime value (unless we make -time an integer and > add a -date version for dateTime?) > > > Hmmm, how about just having "job-retain-until" (type2 keyword) and > "job-retain-until-time" (integer) and not bother with > "job-retain-until-date" (dateTime)? > > > Let's discuss this at the next concall - I can see a use for both (retain > the job for 24 hours, retain the job until the next scheduled update), and > a Client can calculate the number of seconds to a specific date/time, but > there are still some vagaries due to submission delays and whether the IPP > job ticket is used directly and immediately or if it gets "relayed" to the > destination output device that is doing the retaining... > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --00000000000051cc3b058373dea6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Ira McDonald (Musician / Software Archite= ct)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TC= G Metadata Access Protocol SG
    Chair - Linux Found= ation Open Printing WG
    Secretary - IEEE-ISTO Printer Working Group
    Co= -Chair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Designated Exp= ert - IPP & Printer MIB
    Blue Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    ma= ilto: blueroof= music@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-49= 4-2434

    <= /div>

    <= br>
    On Wed,= Mar 6, 2019 at 4:03 PM Michael Sweet via ipp <ipp@pwg.org> wrote:
    Smith,
    <= br>
    On Mar 6, 2019, at 3:41 PM, Kennedy, Smit= h (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote:
    ...
    =C2=A0Also, I don't think we want a job-retain-until-time-default= , since the value is an absolute dateTime value (unless we make -time an in= teger and add a -date version for dateTime?)

    Hmmm, how about just having "job-retain-until" (type2 = keyword) and "job-retain-until-time" (integer) and not bother wit= h "job-retain-until-date" (dateTime)?

    Let's discuss this at the next concall - I can see a = use for both (retain the job for 24 hours, retain the job until the next sc= heduled update), and a Client can calculate the number of seconds to a spec= ific date/time, but there are still some vagaries due to submission delays = and whether the IPP job ticket is used directly and immediately or if it ge= ts "relayed" to the destination output device that is doing the r= etaining...

    _________________________________________________________
    Michae= l Sweet, Senior Printing System=C2=A0Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --00000000000051cc3b058373dea6-- --===============0295755413623841712== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0295755413623841712==-- From ipp-bounces@pwg.org Wed Mar 6 13:48:50 2019 Return-Path: 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 31FCA129508 for ; Wed, 6 Mar 2019 13:48:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 UM7cXIwX2Nn8 for ; Wed, 6 Mar 2019 13:48:47 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 24915124D68 for ; Wed, 6 Mar 2019 13:48:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 5ADE224D3; Wed, 6 Mar 2019 21:48:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 19DCF2618; Wed, 6 Mar 2019 21:48:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B9F843F46; Wed, 6 Mar 2019 21:48:38 +0000 (UTC) Received: from mail-yw1-xc35.google.com (mail-yw1-xc35.google.com [IPv6:2607:f8b0:4864:20::c35]) by www.pwg.org (Postfix) with ESMTPS id B8F1C2618 for ; Wed, 6 Mar 2019 21:48:37 +0000 (UTC) Received: by mail-yw1-xc35.google.com with SMTP id n12so11440884ywn.13 for ; Wed, 06 Mar 2019 13:48:37 -0800 (PST) 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=Hf03vnGc3ifMtSoTWi9y25SEgq8Blo7yarTGM2HdPm0=; b=qH1fOoY0i9k+sS1JM0uXjDuyFusMe4F7KUuY19BNDH2qazOj4Gqlto6P1fenHd4LC7 /80D6BMYZSV2mQSH4le4/HC1X9KRfafop0GzBe7O5cVbwpG1U/M8h7DEtNWr7kqC5tvZ VdKm9K4JGl4CsoKlgqFM7PejZhqwrhza3gUiK+9K4IqwrABkFkw9aIRZsdso1FkNcSFj UxoEAA9RKy1LqEUe66CGrY9qyc/Bca1boSKqARKZqh5+INhUVmeDhOu8s9reWemRJb0F TsWDRqY4FJ0C0u6TRNsdT5EC0ikHZWIiJnOy2eSzEleOsl067kkrHsmK6iqFkGJJ6KLW v+Cg== 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=Hf03vnGc3ifMtSoTWi9y25SEgq8Blo7yarTGM2HdPm0=; b=mGrtVRnzJVS9d9gjL7LD26pzcMq+L+O3w0MJ5LRORtGzhMUq0zeCKjcURJipjgqGYA T8cv/41yYsuwh3l0VjC9hdloTytN3fBe4OU93H4JYfLpweQn5J2xrgCJAGoL4OJrP4ol IEIuJNBSBSTCLX7/H2yWd2AX6sdZf/4xglEAZLJEqRiF0gnLu/qcqOd/tdhgpiLHbDxx 4k/VNXT8asyAU6wp577yLHnV1HG8rdgrnG/laMIhymdWLG3NBCxBn/jPgqzfQ3z3KJRS QF5+6MAaNZ55m25UQsTqa6jnYYaNi0oCRFHrkS5zpv96F0HoiyZQf7LEgbHYmtr37knh IO6A== X-Gm-Message-State: APjAAAUkBQ4C3IYE6KEw+VjTjXQ77waBIV4n8Tp8GMjGTa2B15gsP9+/ GqqgPEAi+LsrUvDXCQy6qhUVwnnpDUA873ACXgU= X-Google-Smtp-Source: APXvYqxIdA+pyum5aiBBMnXPjR6k/xvCGnR5eqTR0TdZ5iwm7/THer0IVXonBt8BSAa71AuMnbGbgAtdgJV4c1lGqZs= X-Received: by 2002:a25:3b45:: with SMTP id i66mr8573189yba.308.1551908916968; Wed, 06 Mar 2019 13:48:36 -0800 (PST) MIME-Version: 1.0 References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> Date: Wed, 6 Mar 2019 16:50:49 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============8072293032523374874==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8072293032523374874== Content-Type: multipart/alternative; boundary="000000000000b84167058373f3e0" --000000000000b84167058373f3e0 Content-Type: text/plain; charset="UTF-8" Hi, I just read this entire thread carefully. I agree with all of your joint conclusions (good work Smith and Mike), *except* for "job-retain-until-xxx". I consider the lack of "job-retain-until-xxx" an architectural mistake in IPP/1.1. So I'd like it to be present in Job Extensions, so that some version lower than IPP/2.2 (Enterprise) can reliably use it. I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED in IPP/2.1 and above. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp wrote: > Smith, > > On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards > Architect) via ipp wrote: > ... > > Also, I don't think we want a job-retain-until-time-default, since the > value is an absolute dateTime value (unless we make -time an integer and > add a -date version for dateTime?) > > > Hmmm, how about just having "job-retain-until" (type2 keyword) and > "job-retain-until-time" (integer) and not bother with > "job-retain-until-date" (dateTime)? > > > Let's discuss this at the next concall - I can see a use for both (retain > the job for 24 hours, retain the job until the next scheduled update), and > a Client can calculate the number of seconds to a specific date/time, but > there are still some vagaries due to submission delays and whether the IPP > job ticket is used directly and immediately or if it gets "relayed" to the > destination output device that is doing the retaining... > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --000000000000b84167058373f3e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    I just read this entire = thread carefully.

    I agree with all of your joint c= onclusions (good work Smith and Mike),
    *except* for "job-ret= ain-until-xxx".

    I consider the lack of "= job-retain-until-xxx" an architectural mistake
    in IPP/1.1.= =C2=A0 So I'd like it to be present in Job Extensions, so that
    some version lower than IPP/2.2 (Enterprise) can reliably use it.
    I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED
    in IPP= /2.1 and above.

    Cheers,
    - Ira
    =
    Ira McDonald (Musician / Software Architect)=
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TCG M= etadata Access Protocol SG
    Chair - Linux Foundati= on Open Printing WG
    Secretary - IEEE-ISTO Printer Working Group
    Co-Ch= air - 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
    mailt= o: blueroofmus= ic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2= 434



    On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp <ipp@pwg.org> wrote:
    Smith,<= br>

    On Mar 6, 2019, at 3:41 PM, Kenn= edy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote:
    ...
    =C2=A0Also, I don't think we want a job-retain-until-tim= e-default, since the value is an absolute dateTime value (unless we make -t= ime an integer and add a -date version for dateTime?)

    Hmmm, how about just having "job-retain-until"= ; (type2 keyword) and "job-retain-until-time" (integer) and not b= other with "job-retain-until-date" (dateTime)?
    <= /blockquote>
    Let's discuss this at the next concall - I c= an see a use for both (retain the job for 24 hours, retain the job until th= e next scheduled update), and a Client can calculate the number of seconds = to a specific date/time, but there are still some vagaries due to submissio= n delays and whether the IPP job ticket is used directly and immediately or= if it gets "relayed" to the destination output device that is do= ing the retaining...

    _________________________________________________________
    Michae= l Sweet, Senior Printing System=C2=A0Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --000000000000b84167058373f3e0-- --===============8072293032523374874== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8072293032523374874==-- From ipp-bounces@pwg.org Wed Mar 6 13:51:08 2019 Return-Path: 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 56B751295EC for ; Wed, 6 Mar 2019 13:51:08 -0800 (PST) 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=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 1v2X1HieJAcH for ; Wed, 6 Mar 2019 13:51:03 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id A3BE0129508 for ; Wed, 6 Mar 2019 13:51:03 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 871083F4D; Wed, 6 Mar 2019 21:51:03 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1A1C82618; Wed, 6 Mar 2019 21:50:59 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 460123F46; Wed, 6 Mar 2019 21:50:57 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 8FD4924D3 for ; Wed, 6 Mar 2019 21:50:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551909054; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=K78HHrxRce03fDcU17lMiibWTk17TTvieTT438ZTp6c=; b=RQapiRbfvOGRABR3QO5U875d9DTIieUm2SgPI9m/TrVQw64m1DqzpbEiFLEfOo0E7DuwXLajjuemPS0uHaRGUVmsCciTyywgXs5OwUHn+/Vn7bP58e1N85WmsB1H4dsgXalUO3CU9Cv6NMeDKvOsqpiDPNXZUn1l8jr1xgYsfPs= Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp2050.outbound.protection.outlook.com [104.47.40.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-228-pW35AbhpNTWb0-SSt0eNNQ-1; Wed, 06 Mar 2019 16:50:53 -0500 X-MC-Unique: pW35AbhpNTWb0-SSt0eNNQ-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0999.NAMPRD84.PROD.OUTLOOK.COM (10.169.16.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Wed, 6 Mar 2019 21:50:51 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Wed, 6 Mar 2019 21:50:51 +0000 To: Michael Sweet Thread-Topic: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? Thread-Index: AQHUz6ygHr0UwLDskEmAk4liLFoBzaX1x4gAgAkrkoCAAAbDgIAAIJ8AgAAGFwCAAA1nAA== Date: Wed, 6 Mar 2019 21:50:51 +0000 Message-ID: <3F74F614-47E3-453C-8CA3-80A0F9F86420@hp.com> References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e19b5ac8-f42d-4c29-118c-08d6a27dcd1e x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0999; x-ms-traffictypediagnostic: CS1PR8401MB0999: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0999; 23:NNE5oASTMjtkn4CYh0dVGggbXWaX//GPJbykmW5?= =?us-ascii?Q?IIzc43Gvjn9a+l53wHGHAC/U2bht54hEh5KRroNvg+3PW4l8kiH7qn8qXLiX?= =?us-ascii?Q?rJzGriUPlqT2SKqQGo+U6Dub+psnNTptRI9OZRIuR8EJyGb+MQGt58Go/UyP?= =?us-ascii?Q?ZA8T5buSDwARURYITWXpJY1qbvU41wCOEH8xkfpNTuHY0jFd9zGgYfctIGql?= =?us-ascii?Q?dwtnBiyfONsfCGBDyGsS67MugfcRCoO3adF0e6QNoYJpkiZPYDHMxQFBRqlf?= =?us-ascii?Q?Q1deqFSsV11PZ049TMJDEb9hBkVmXjhghcS8D7GfeVE2HzT0Q0wG1mzqHfj1?= =?us-ascii?Q?TxvQdKoxBRFKrFi2OXGP8DbSZksOaKlrh0uqZixlEqG/9JMnbrZHRsiC/RNY?= =?us-ascii?Q?Er1Ub8QKrrxMUqgNv/J8n6HIdfVw9Fb/jneTw2dS/xi5d4UxkcBZo6LZv3y+?= =?us-ascii?Q?6+tPOGHyxZRLaS8ASIH1+cXguvQXhu1jc24xktFRSlRq+B2fJId+ktFoRHmF?= =?us-ascii?Q?nAJKasLalBWtLLWsCMJyEPxLIQjGTzkILkF0+KDhabwwffhxfne/HEm/qOqF?= =?us-ascii?Q?mZbY96AXOIwlT2s76NtXljRvApZiequkuN4t+Y5cHlDcsVtiAuADpOBAAer0?= =?us-ascii?Q?bH2CHhvOOqDAsG7iWXS04WNaoMoHPipfQMlqtLyQocLFJZioFjM3G1zmL44I?= =?us-ascii?Q?5JQyjpvS1DURjR4BAUfSQktsGVelnERzEhCUVawwF4AMLj9mXoz7+tBA8bn/?= =?us-ascii?Q?Vzj21p+hX/Mx20mVi2TaxfuloORP45DyIVJgFznLt/uz+vlbrqeSDsC5UyMH?= =?us-ascii?Q?8LBTL4B9AwwxpCPvgC+TIisFk0JSSwL2jQuXErEkAGiZziIqtFC9oZPaCEQj?= =?us-ascii?Q?4fgNjbBBLxv1ZlPwK9YRZ5iUR2nAQnQiDwmNbjy45dYfNboPRsSJwu1DFyiq?= =?us-ascii?Q?IAOol3ogORD7/lQn/rqscjXk7vC/Gf9OEUswR3k3RLfy2YIu14SYfbdkUqpH?= =?us-ascii?Q?wRcPFGFRQzQ6MWKp4Ui837zi7e04ksTVrltlq6679+yAFWmzkTvNyaobb4dA?= =?us-ascii?Q?1ERYBkKGF3d3IUD4/vob5ca7yWXq/h7f/HhL54e+WyPkGs+KhoQGuIKorHuC?= =?us-ascii?Q?QT2bNy5hpBjjJYvkXEKHuAA2zAT7jiWqes7uvzeQiigaEYip2/F/eGJaSJKX?= =?us-ascii?Q?OE19NP0Go512anQUuKttNIeAF1hNeTdcP/3N+RJ9Oz3NTCEzhILhmrfhOaI5?= =?us-ascii?Q?2o3io5ZiYSLaCAzExGeQPCwGabw442Y/N5xvVTBMVqku1Z3Dz9NO9voBEpdl?= =?us-ascii?Q?o0gmZP9NfPw9/ADlPN7KZ4HIJcSabdlr/tNCaDOLAFk7e?= x-microsoft-antispam-prvs: x-forefront-prvs: 0968D37274 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(39860400002)(346002)(366004)(136003)(199004)(189003)(6602003)(6512007)(8936002)(54896002)(82746002)(4326008)(229853002)(36756003)(6486002)(6916009)(86362001)(6436002)(7736002)(478600001)(83716004)(81156014)(316002)(71200400001)(11346002)(446003)(476003)(81166006)(66066001)(71190400001)(8676002)(256004)(2616005)(14444005)(99286004)(2906002)(5660300002)(93886005)(99936001)(486006)(97736004)(68736007)(14454004)(186003)(26005)(76176011)(53546011)(33656002)(53936002)(3846002)(25786009)(6246003)(105586002)(6116002)(236005)(102836004)(106356001)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0999; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: k2UdBj+9c3yxrLpjFgmm2j2rBzMgiGm1A8OuY2OA0182szxRfMV7g4uzm8NTNo5d4ZPT1lA8S5tmO6STaSRW+azXMV6wTv7567eaPlD/VGLdFYvIX5opw/rgYAdnKwN36ECln0Ghs8jzRjQ7D1mprRERw4gpBjbbAYH/D8Rp4Ba8uvM3HR/MuAtO3juvUJsdnSWM8KaVVLqcwhrJJdASYWhcriCfo0AckzhxkrbNaLrX6E5U0gsaUKghau3Lt8tvc5m4QSDRIGMZLw+wBpNSIykRSeywlFZaBYuzR+Nzyj93+7p1sSM6F7s8OJk5hB0cW1tQ6DdpwrxsBf72gPv+KIfRIopWtovDTZgfGL2bRqz9ZrvXvl+Z51n/VbSEGlMzcFVEOLT8id7rlwVnErbbTeoedP4rAhlgoOYsvd5le70= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: e19b5ac8-f42d-4c29-118c-08d6a27dcd1e X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 21:50:51.4554 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0999 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============4222142556755171116==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4222142556755171116== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F4DA2BF5-5780-4ED4-A5D1-F7D516241338"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_F4DA2BF5-5780-4ED4-A5D1-F7D516241338 Content-Type: multipart/alternative; boundary="Apple-Mail=_B6F6E96F-27A0-4407-ABEE-5FCD3966F12C" --Apple-Mail=_B6F6E96F-27A0-4407-ABEE-5FCD3966F12C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Perhaps we need to be clear in the definition of "job-retain-until-time" = that relative times are measured starting from the time specified by the = Job's "date-time-at-completed"? Smith > On Mar 6, 2019, at 2:02 PM, Michael Sweet wrote: >=20 > Smith, >=20 >> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >> ... >>> Also, I don't think we want a job-retain-until-time-default, since = the value is an absolute dateTime value (unless we make -time an integer = and add a -date version for dateTime?) >>=20 >> Hmmm, how about just having "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and not bother with = "job-retain-until-date" (dateTime)? >=20 > Let's discuss this at the next concall - I can see a use for both = (retain the job for 24 hours, retain the job until the next scheduled = update), and a Client can calculate the number of seconds to a specific = date/time, but there are still some vagaries due to submission delays = and whether the IPP job ticket is used directly and immediately or if it = gets "relayed" to the destination output device that is doing the = retaining... >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 --Apple-Mail=_B6F6E96F-27A0-4407-ABEE-5FCD3966F12C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Perhaps we need to be clear in the definition of = "job-retain-until-time" that relative times are measured starting from = the time specified by the Job's "date-time-at-completed"?

    = Smith



    On Mar 6, 2019, at 2:02 PM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    On Mar 6, 2019, at 3:41 PM, = Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> = wrote:
    ...
     Also, I = don't think we want a job-retain-until-time-default, since the value is = an absolute dateTime value (unless we make -time an integer and add a = -date version for dateTime?)

    Hmmm, how about just having = "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) = and not bother with "job-retain-until-date" = (dateTime)?

    Let's discuss this at the next concall - I can see a use for = both (retain the job for 24 hours, retain the job until the next = scheduled update), and a Client can calculate the number of seconds to a = specific date/time, but there are still some vagaries due to submission = delays and whether the IPP job ticket is used directly and immediately = or if it gets "relayed" to the destination output device that is doing = the retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer


    = --Apple-Mail=_B6F6E96F-27A0-4407-ABEE-5FCD3966F12C-- --Apple-Mail=_F4DA2BF5-5780-4ED4-A5D1-F7D516241338 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyAQLoACgkQqskbKLDW 1N0wMg//ca6ICaGUIwblZ3NU0aMcMv+0HsPPVWavyMLQSbWAnAonPvHkSVhOjFTV 93s/5awl6dgfGfzXCIKieW1+tOAMz8cOJF/5/lpqvsDwJDSWrGpg8BvOriaSiJVD 68/5tKWF1dI4UK+/l6DmuAhp7J9MZgAf+d4MzZW3Txk4Ehk5BnEI7+8Oy1YD3Nfx AkzIIA+H7Rv9z72pwdUfIxecOyARw2szVDn8w54h1AZvJ/PMDib/MqL5zxDtUEea OHofIjXaV9Z8FGSYa/qel1qsjddvoZ8dLua7n1eXPuHNKCFS9kBGalKyInkITPya 2y91MgAOq0IqgjIhY9Lmk9Yn+w6B9ETfC9rLHfyVP+XK79YCNP0avnBkA5cDeLD8 0Gfjyqus2WBd8v/G2fv3HVpYSigjjb/DXpcVMGRC1epmtY04bMkOs9F8bdcys6in SzgdItBMXvY9QFtJy1yNoZcYx/d7mc1UCZf43IzUUcsvbX2l43qaSlAJ0QIcLTSx FZYZ/9XUIkqooSeW60T6i1KaC15ogEYsai+vfvMQh70XOOLgaL2HNS/jU//XeC3X n8Bn1K3guj0uS5FVBM5KnzTG21fCpK6j3FrE2BCIL/o/enMtuaW6PweswB0eQ2sb cgiZbp9vO8IzgEIlafRChZnIBCoyzr7gGc9bUpM5WkISEfOVXNQ= =sISl -----END PGP SIGNATURE----- --Apple-Mail=_F4DA2BF5-5780-4ED4-A5D1-F7D516241338-- --===============4222142556755171116== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4222142556755171116==-- From ipp-bounces@pwg.org Wed Mar 6 13:52:42 2019 Return-Path: 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 508B7129508 for ; Wed, 6 Mar 2019 13:52:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.709 X-Spam-Level: X-Spam-Status: No, score=-0.709 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 0Z4NoWF_NRHc for ; Wed, 6 Mar 2019 13:52:40 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 22A5A124D68 for ; Wed, 6 Mar 2019 13:52:40 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id EBEDC3F50; Wed, 6 Mar 2019 21:52:39 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id DE28F26AA; Wed, 6 Mar 2019 21:52:36 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 8F3313F46; Wed, 6 Mar 2019 21:52:35 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 978472618 for ; Wed, 6 Mar 2019 21:52:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551909153; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VQU+FrkfSN3CpqCGzFerlV1d0JWrhpP7RaImaJWqHaM=; b=Vef+hbSETaUaIbD2gTPfD1PkpD/zMEFmJl/lwqjvOw/mOU2mBbiYJimeynuhp/FOVlZmM67jJ5pkCNNIunXJIpNGehzq3PBd0JbQ093/UReA6CgnEjI2pMR7/DORgLlV+ozxPu6001hoYpCePzF0CIZt5RAOeSMUTDnmA1MJSx0= Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03lp2054.outbound.protection.outlook.com [104.47.40.54]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-18-6Fny1fpZMze9MBBpQFXURA-1; Wed, 06 Mar 2019 16:52:20 -0500 X-MC-Unique: 6Fny1fpZMze9MBBpQFXURA-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0997.NAMPRD84.PROD.OUTLOOK.COM (10.169.24.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.16; Wed, 6 Mar 2019 21:52:19 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1665.020; Wed, 6 Mar 2019 21:52:19 +0000 To: Ira McDonald Thread-Topic: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? Thread-Index: AQHUz6ygHr0UwLDskEmAk4liLFoBzaX1x4gAgAkrkoCAAAbDgIAAIJ8AgAAGFwCAAA1mgIAAAGoA Date: Wed, 6 Mar 2019 21:52:18 +0000 Message-ID: References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 57710bf5-3cc4-4acd-68f2-08d6a27e014c x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0997; x-ms-traffictypediagnostic: CS1PR8401MB0997: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0997; 23:wcKy9+P6mosB1j8VRfF6yB1BSPBwdN5ZgzT4mKU?= =?us-ascii?Q?H3+h0DGmxR3tmUc/E4iD4g9ZWu/jnrp+y6n5K22li3n+45E/JxK3j/A1PRCs?= =?us-ascii?Q?mRMnJB8/YhTbOnW94VKnLl0EZlBir0I53lLUt4X3WtZRMjpQZ7/YX6lu661s?= =?us-ascii?Q?LUJ+szE7x5YgwISZ4pJ5JRAYjg4IXpzB/S436lOI2+MOR4NC3RKih5D0S8wH?= =?us-ascii?Q?GbGpS32WFr2ZYLIoC43kpzu9rA1V6bQOPNsPd+5Sgj9UxYJ5h4hy0TvzS96Q?= =?us-ascii?Q?qRO6ydDr2e+3yUXl/uIO8Il4iF6VHeMhWFtmJbcJJGbMMf0CdWRo1KSALOyV?= =?us-ascii?Q?BK8uds6UXciR3qZjNNFEIjMvUVfCyQ5wIdWEbwhY6D8pNMUR5QwCMLzyVWZ9?= =?us-ascii?Q?3o9Mh9SWUpQv/xC5UJolf+k+QQ7ku8SMteVQlYRo9wJ396H2nobo6zqQD2qJ?= =?us-ascii?Q?27y0i72GB3giB6f68fgzxd8cLL4/YkrOSBFBMzJLsIUbtrU9+34ai0+LwQL9?= =?us-ascii?Q?Z+t+E9N8L86OxklDOgiJED+rwkPhIwCrMSSJf6SiS3maHX73qDy9EUIwrLWE?= =?us-ascii?Q?gjR2Y+Dd/3nD0fNXUx+B/Xvjw8fDfHqWfsWPgjo5zMHKnvyFCV/USOmDwoZx?= =?us-ascii?Q?tb7g6lXWT34PTu1Bd+ZrNu8vp6V02KWbE30Dj5nIxWYCb4hWCaBwNgguzw7N?= =?us-ascii?Q?jUSw25/4z9LDR6yDPO3KtluUgrNZZ8735MR7S7J5Em1m9CLHxzkiUGRDRO7Z?= =?us-ascii?Q?4spNZw3kTzdl268mT4+XNgq4oQAg+NGPDzixLuhOJy0jCUvxiweAwwZBXuVD?= =?us-ascii?Q?BDcU6V2nf6SizFRZAvSAqaktBj+z8zhgkSgIdU3PF5wQHQbjZo8GMUoQqeg2?= =?us-ascii?Q?xMCX+wG04jmJkRa7jigsr6ORS3sBKe6t2oDU5z4v1fLi+EUvVNfKhQVCVAWd?= =?us-ascii?Q?SKZ2EPjhBxyNwhr9LNwwxBx/swjNz5P7ecnT7didP/9TPspsuo07P2qHhFmj?= =?us-ascii?Q?AEiF/PJEC5QANgL8op+uCFFC8Z+VxQ0gQSEGGPsE8VxfEXLfSeWPuBZcMYQM?= =?us-ascii?Q?oJTYy9AvOqF6XwKwiS4tgZBdTo+RpAoIuA9Q6GLLo7+O9BOok4ccFBs5TkYB?= =?us-ascii?Q?aQi4wntzLoCZOUIrgIO0lfAWxNBQ31InxpwBLdJ0Fv21KNVlA+9BKRNUDJ7G?= =?us-ascii?Q?kEMmODYorsurGCNnJTYuGwHYxxdaGUAJzPydSkBQ7aaksjlXpWzJ/moap+EJ?= =?us-ascii?Q?/6VAI8/7q/4k0FGSl9pFRIl1I0MVX13AHvxvvWUvQXzahYX1iGkZIpqFVi8a?= =?us-ascii?Q?xrg86+oMu2IssO7rdWMSP3xNV8uhxpkyPtl5m0q3ZxO69qHs6O/KsnyepA0d?= =?us-ascii?Q?I/j9prpbmqORaWTcMnPY0RiiOuZaszFVmkISqHyeEmtuZaOumd5999T9bBF0?= =?us-ascii?Q?Actn3Z8j3yBrpFPNDcEHvb0AK8IteZmWLEC9BqP9PVQKB7KWfVqDp+J0brQJ?= =?us-ascii?Q?4E6f6vXC+c/tE0E98AgqpGl1AVIJSuSSvONzOsBW32LzMM9X6hSrir+Mre0Z?= =?us-ascii?Q?OIF6kO9wKituVkgOX+u4TvxYqfGQ35bq6tChVwEY=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 0968D37274 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(376002)(366004)(39860400002)(396003)(199004)(6602003)(189003)(476003)(2616005)(6506007)(81166006)(81156014)(6246003)(19273905006)(66066001)(6916009)(11346002)(8676002)(446003)(8936002)(68736007)(71200400001)(256004)(486006)(71190400001)(83716004)(105586002)(53936002)(106356001)(33656002)(99936001)(14444005)(7736002)(1411001)(606006)(25786009)(4326008)(2906002)(26005)(86362001)(6486002)(5070765005)(229853002)(6512007)(236005)(54896002)(14454004)(76176011)(6306002)(478600001)(5660300002)(966005)(97736004)(102836004)(54906003)(6436002)(186003)(3846002)(36756003)(66574012)(93886005)(6116002)(53546011)(99286004)(316002)(82746002)(21314003)(16351025005)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0997; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 8b4Z5fHbFY79M6XU5ENltMsTJpaW2u0zGI/NS3UIy/rlo1MHZW7462VbyplSyZzwySfH7mB7xnxiuqSgJNqX0QzK9l2ABYjSlzZjrRIv9ZcLES40jnfp3IkkOUR1GaFjetEJC+87BHf+jF0yNkyDoz1BB2y0bpk+uwXUgUF2P7kG/LlRgtitnIQB8CP3Imypj/DCe9GJHuQbMvicMWkHTa1SrJugwxJpk4Zh+Y24oTFFmtURK6zoND3A1543HekAwTPmXirHGEydi9MjiarNb12Gm/pGClgpJ4xE/360NUF7g2Oy6g+ZGl383GTtU/refXNvsBEHzA3QMbgd9OQSMGvO+jmvkr2n/yWUAAfzwH/B8jGGPZqhyVtr7JUGnGeYWkx2uGk+wtGBRuEOFMixB5EUmHkMA+6BQVEE3OYPU5M= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 57710bf5-3cc4-4acd-68f2-08d6a27e014c X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2019 21:52:18.9856 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0997 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8739721650475822452==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8739721650475822452== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_31EC5961-075E-450B-BF56-992883B328D3"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_31EC5961-075E-450B-BF56-992883B328D3 Content-Type: multipart/alternative; boundary="Apple-Mail=_1E4A06C2-08C0-49FD-BD53-B76668E53143" --Apple-Mail=_1E4A06C2-08C0-49FD-BD53-B76668E53143 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Ira, I support the move to Job Extensions for the reasons you provided below, = and because I think it might be useful in a more general case. Smith > On Mar 6, 2019, at 2:50 PM, Ira McDonald = wrote: >=20 > Hi, >=20 > I just read this entire thread carefully. >=20 > I agree with all of your joint conclusions (good work Smith and Mike), > *except* for "job-retain-until-xxx". >=20 > I consider the lack of "job-retain-until-xxx" an architectural mistake > in IPP/1.1. So I'd like it to be present in Job Extensions, so that > some version lower than IPP/2.2 (Enterprise) can reliably use it. > I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED > in IPP/2.1 and above. >=20 > Cheers, > - Ira >=20 > 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/highnorthinc = > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp > wrote: > Smith, >=20 >> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >> ... >>> Also, I don't think we want a job-retain-until-time-default, since = the value is an absolute dateTime value (unless we make -time an integer = and add a -date version for dateTime?) >>=20 >> Hmmm, how about just having "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and not bother with = "job-retain-until-date" (dateTime)? >=20 > Let's discuss this at the next concall - I can see a use for both = (retain the job for 24 hours, retain the job until the next scheduled = update), and a Client can calculate the number of seconds to a specific = date/time, but there are still some vagaries due to submission delays = and whether the IPP job ticket is used directly and immediately or if it = gets "relayed" to the destination output device that is doing the = retaining... >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = --Apple-Mail=_1E4A06C2-08C0-49FD-BD53-B76668E53143 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Ira,

    I support the = move to Job Extensions for the reasons you provided below, and because I = think it might be useful in a more general case.

    Smith



    On Mar 6, 2019, at 2:50 PM, Ira McDonald <blueroofmusic@gmail.com> wrote:

    Hi,

    I just read this entire = thread carefully.

    I agree with all of your joint conclusions (good work Smith = and Mike),
    *except* for = "job-retain-until-xxx".

    I consider the lack of "job-retain-until-xxx" an = architectural mistake
    in IPP/1.1. So I'd like it = to be present in Job Extensions, so that
    some = version lower than IPP/2.2 (Enterprise) can reliably use it.
    I suggest making it RECOMMENDED in IPP/2.0 and = REQUIRED
    in IPP/2.1 and above.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Wed, Mar 6, 2019 at 4:03 PM Michael = Sweet via ipp <ipp@pwg.org> wrote:
    Smith,

    On Mar = 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) = via ipp <ipp@pwg.org> wrote:
    ...
     Also, I don't think we want a = job-retain-until-time-default, since the value is an absolute dateTime = value (unless we make -time an integer and add a -date version for = dateTime?)

    Hmmm, how about just = having "job-retain-until" (type2 keyword) and "job-retain-until-time" = (integer) and not bother with "job-retain-until-date" = (dateTime)?

    Let's discuss this at the next concall - I can see a use for = both (retain the job for 24 hours, retain the job until the next = scheduled update), and a Client can calculate the number of seconds to a = specific date/time, but there are still some vagaries due to submission = delays and whether the IPP job ticket is used directly and immediately = or if it gets "relayed" to the destination output device that is doing = the retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

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

    = --Apple-Mail=_1E4A06C2-08C0-49FD-BD53-B76668E53143-- --Apple-Mail=_31EC5961-075E-450B-BF56-992883B328D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyAQRIACgkQqskbKLDW 1N0wKw//SoIoede+AMvmmtE9zlYNre78t4RSgfpNs0HkviChy9n0s9Igj/TAf1oB YvPx2LcEachA1os1N7NwIvXt1T4zJTgX4NOjD01yF6cH9YmZraJ//KDdmBzOOd7Q AgSQ+TKZKw/ZS0DLw62HrDqQyKHA3g1B5pSc6LeBRL7SaC8+8Fi1XZzW4/24G2PK CSRgdtTbqDaK8Zh//Eom38jQMeskE8e9Ym/QemHmPPmnvV/jy3VxdZ9uyxV3W2pF F3LO4v3OVpZefZNAqP6EcJrw5j/e1ki1t/DZNEeVyUppkkqvd4cs2gscH+WzpJgC DUvwSQEX1WK3D6GAttE+4iwsmczGMuAv1MRlwkn6Ujj6KiSaqilNqLOgG8bHiKJd Nk1LbTu1BYX2j6+rOcZFnhJSqVLGSO02K8dIKpNAwkVQfah5Q4pieiBxNIgB5F9l dzK92L696KMjFsapfBoGUGg7J5IOPKBlCr067KhXe/60QM333OjqjACodU5ubvhi /rbs+B9b0BEBtjbTKECq7XdyWIteokamdYAxZZe/mWBJhugSb8OgfNKgShD4Fpdg Efkwdlo01VZ4vsBk0rJhO1ieK2YeGNBRJD1Ff/DqnR8w2p64H1zhRT/udvgnmcWc nZN+TTeCzpo62AwN7VBxLrBYwfpaY7RxpCEywct0ADcFRdnqSlI= =uYcK -----END PGP SIGNATURE----- --Apple-Mail=_31EC5961-075E-450B-BF56-992883B328D3-- --===============8739721650475822452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8739721650475822452==-- From ipp-bounces@pwg.org Wed Mar 6 18:11:47 2019 Return-Path: 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 48A45131071 for ; Wed, 6 Mar 2019 18:11:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 9TFROJKokmm3 for ; Wed, 6 Mar 2019 18:11:45 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id DA14512F1AC for ; Wed, 6 Mar 2019 18:11:44 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id A897A3F9B; Thu, 7 Mar 2019 02:11:42 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 64E5C2618; Thu, 7 Mar 2019 02:11:38 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id AE4AF24D3; Thu, 7 Mar 2019 02:11:37 +0000 (UTC) Received: from mail-yw1-xc32.google.com (mail-yw1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) by www.pwg.org (Postfix) with ESMTPS id DDA7C24D3; Thu, 7 Mar 2019 02:11:36 +0000 (UTC) Received: by mail-yw1-xc32.google.com with SMTP id c67so12025857ywa.7; Wed, 06 Mar 2019 18:11:36 -0800 (PST) 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; bh=8+R/t4TY1N6BBCopG6ISgfEQWvI1b2yD7zIey2FtBKE=; b=Rn+rVmnFou9eAKSRlnoBvU/uq48RFiwcFFXjmpGFcQdh04iYpKnxyMNhLq/tcH6o97 mlPYZeHHn2jF5qN+7psokzI2DcKeLO61uRcDoBUl5PHHcDzftbi/cWCV/474IjoKRf9A grv4cIId9TB0ZOV9GxU/710funPRlHTSDHeTb4tlI1uS+x9Xksp3o5Z81O70WN6FcrTw kjY2wmh/Z6lGNpsmHxWUPKQQyMP5GPt6omRqkuiqijYPNdbpOY/pCc/xZUBi7h5bP1ch 1QsFFC3FYmapNwIppN4Kv9NAomEPncHgnjb6IydO04l7KLFZgxKM/gCRRpEGj/pKDmk8 ksQQ== 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; bh=8+R/t4TY1N6BBCopG6ISgfEQWvI1b2yD7zIey2FtBKE=; b=C8cYi6xSRG8MOUwRFfTMSWpdgJ4vkMvvGHrvbu3xx5ZwmDqVpg+Wci/14yosxXYydV 6+ZMoQkmC73bMnDiXObDk3Nwumpdb1ji+f/Ww6HMpvm2QVp31k99sK/mNEJg6p1p4C12 B9RXtXK1YQ7C9yxjhyw1VONAavRVBrPF81ngzrO23JHRkEE4vnrDfOnBeC3vjsd2HO9W N3vf0XLsweRLgnDJ+R/yocHqjGxJsCcHbwrUFj98CEanFTuysF4Qz/QcU5ZA/7YSGhIA Qst9Jm7kUqxmNaSXx74U3PKzm3CwMajnh8+N5bur32q1EtDuNANuFNEZbxK0qT17uqz8 EFAg== X-Gm-Message-State: APjAAAWj0O/2a33MYPe5Gmpb75HJTt4tHqvpy1r03GzfC1G056KXtzIK cUlQiJsYZFajoiMamrl6sjinp9OQDC24KrMNYwQJAA== X-Google-Smtp-Source: APXvYqzhlPDj6V2R5TybefaC3zmq+gzUYGYq1rIZkNG7FnaTY94itcfw00qHG7Khhcj+MjsvSmKZenATtGVlajYu6bg= X-Received: by 2002:a25:2605:: with SMTP id m5mr9465114ybm.194.1551924695669; Wed, 06 Mar 2019 18:11:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 6 Mar 2019 21:11:23 -0500 Message-ID: To: "ids@pwg.org" , "ipp@pwg.org" , Uptane Forum , MPWG , tms_wg@trustedcomputinggroup.org, neteq@trustedcomputinggroup.org, tnc@trustedcomputinggroup.org Subject: [IPP] Fwd: [tc-forum] NISTIR 8214: Final Publication and Public Comments X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6192442665679221342==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6192442665679221342== Content-Type: multipart/alternative; boundary="00000000000034234c058377a008" --00000000000034234c058377a008 Content-Type: text/plain; charset="UTF-8" FYI ---------- Forwarded message --------- From: 'Mouha, Nicky W. (IntlAssoc)' via tc-forum Date: Wed, Mar 6, 2019 at 4:37 PM Subject: [tc-forum] NISTIR 8214: Final Publication and Public Comments To: tc-forum@list.nist.gov Dear subscribers of the NIST Threshold Crypto forum, Thanks to everyone who provided feedback for the Draft NISTIR 8214 --- Threshold Schemes for Cryptographic Primitives. We have taken all comments in consideration. The final version of NISTIR 8214 is now online: https://csrc.nist.gov/publications/detail/nistir/8214/final We have also posted online a "diff" that highlights the changes made with respect to the draft you reviewed. It also includes a table with the feedback received during the public comment period, as well as annotations and links to the corresponding changes in the NISTIR. Regards, Nicky On behalf of the Threshold Cryptography Team -- To unsubscribe from this group, send email to tc-forum+unsubscribe@list.nist.gov Visit this group at https://groups.google.com/a/list.nist.gov/d/forum/tc-forum --- You received this message because you are subscribed to the Google Groups "tc-forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to tc-forum+unsubscribe@list.nist.gov. --00000000000034234c058377a008 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    FYI

    =
    ---------- Forwarded message ---------
    From: 'Mouha, Nicky W. (IntlAssoc)' v= ia tc-forum <tc-forum@list.nist.gov>
    Date: Wed, Mar 6, 2019 at 4:3= 7 PM
    Subject: [tc-forum] NISTIR 8214: Final Publication and Public Comme= nts
    To: tc-forum@list.nist.gov= <tc-forum@list.nist.gov>


    Dear subscribers of the NIS= T Threshold Crypto forum,


    Thanks to everyone who provided=C2=A0feedback for the Draft NISTIR 821= 4 --- Threshold Schemes for Cryptographic Primitives. We have taken all com= ments in consideration.

    The final version of NISTIR 8214 is now online:

    We have also posted online a "diff" that highlights the chan= ges made with respect to the draft you reviewed. It also includes a table w= ith the feedback received during the public comment period, as well as anno= tations and links to the corresponding changes in the NISTIR.

    Regards,

    Nicky
    On behalf of the Threshold Cryptography Team

    --
    To unsubscribe from this group, send email to tc-forum+unsubscribe@list.nist= .gov
    Visit this group at https://groups.google.com/a/list.nist.gov= /d/forum/tc-forum
    ---
    You received this message because you are subscribed to the Google Groups &= quot;tc-forum" group.
    To unsubscribe from this group and stop receiving emails from it, send an e= mail to tc-forum+unsubscribe@list.nist.gov.
    --00000000000034234c058377a008-- --===============6192442665679221342== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6192442665679221342==-- From ipp-bounces@pwg.org Thu Mar 7 08:58:15 2019 Return-Path: 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 CEC70131163 for ; Thu, 7 Mar 2019 08:58:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 ktbmFX7jww98 for ; Thu, 7 Mar 2019 08:58:12 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7B11314A9 for ; Thu, 7 Mar 2019 08:58:12 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id F23283F9C; Thu, 7 Mar 2019 16:58:09 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1865226AA; Thu, 7 Mar 2019 16:58:04 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id E04913F46; Thu, 7 Mar 2019 16:58:02 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id 0273F269F for ; Thu, 7 Mar 2019 16:58:01 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27Gv4uf038050; Thu, 7 Mar 2019 08:57:59 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=T+lFyjsUGYwHO6jtxWkyj32vDrcAct4rQ1s+1PsnUxs=; b=to4j0w+K+JpIWriE9gpSv+4QRzyLrIrF6WJSEhjzfpjZSh8JGRrlFsgyacFClnjtzqx2 5MyTiTix7O60pi7GCExlKgw/PrSbljEg17DPUNqJhrttqJnDqJ83s+9khEYPJWPdHu+T Vva3E/H03qcm0YbWZxCt3jXB0yc7Lj7Na2FH6nlCT1979iJHMPY2LowsePN35vwg1i1J 3O9PA3fRwD8EFfEB3qqPAd79pIvWoDfSxILLu9OzAQhyI4RXVzmP9PnrCeNqgkoLHTYM sPTNxbGEFFku1Q9c33EZpQAFZnfaCYG6Mew/YUCSpm4CE9bwRw5+Zy/IEqQ0jHXbwaCU JQ== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2qyqd40nkn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 07 Mar 2019 08:57:59 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO00092Z9SNOVE0@ma1-mtap-s03.corp.apple.com>; Thu, 07 Mar 2019 08:57:59 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000M009QTED00@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 08:57:59 -0800 (PST) X-Va-A: X-Va-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-Va-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-Va-R-CD: c5f53e861a532cef1a8e83cb2834246c X-Va-CD: 0 X-Va-ID: 08417bab-f732-4496-a826-52e2b69fc12f X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-V-R-CD: c5f53e861a532cef1a8e83cb2834246c X-V-CD: 0 X-V-ID: 18a27b1b-edc6-4b3b-99e2-6d081d3aae27 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_08:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO0004OF9SKS890@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 08:57:59 -0800 (PST) In-reply-to: Date: Thu, 07 Mar 2019 11:57:55 -0500 Message-id: References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_08:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============6802625102569163632==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6802625102569163632== Content-type: multipart/alternative; boundary="Boundary_(ID_Qw4wWjCGif/pe/EoTlldFA)" --Boundary_(ID_Qw4wWjCGif/pe/EoTlldFA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Well, if we put job-retain-until in Job Extensions 1.1, then we should probably put job-delay-output-until in JOBEXT as well (since now we'll have a bunch of Job Template attributes in JOBEXT that control scheduling/job lifecycle decisions) Just remember that in JOBEXT all of this will be OPTIONAL anyways. I will also post a RFC for another attribute to close the last lifecycle hole (how long a job stays in history). > On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp wrote: > > Hi, > > I just read this entire thread carefully. > > I agree with all of your joint conclusions (good work Smith and Mike), > *except* for "job-retain-until-xxx". > > I consider the lack of "job-retain-until-xxx" an architectural mistake > in IPP/1.1. So I'd like it to be present in Job Extensions, so that > some version lower than IPP/2.2 (Enterprise) can reliably use it. > I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED > in IPP/2.1 and above. > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp > wrote: > Smith, > >> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp > wrote: >> ... >>> Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?) >> >> Hmmm, how about just having "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) and not bother with "job-retain-until-date" (dateTime)? > > Let's discuss this at the next concall - I can see a use for both (retain the job for 24 hours, retain the job until the next scheduled update), and a Client can calculate the number of seconds to a specific date/time, but there are still some vagaries due to submission delays and whether the IPP job ticket is used directly and immediately or if it gets "relayed" to the destination output device that is doing the retaining... > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_Qw4wWjCGif/pe/EoTlldFA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Well,= if we put job-retain-until in Job Extensions 1.1, then we should = probably put job-delay-output-until in JOBEXT as well (since now we'll = have a bunch of Job Template attributes in JOBEXT that control = scheduling/job lifecycle decisions)

    Just remember that in JOBEXT all of = this will be OPTIONAL anyways.

    I will also post a RFC for another = attribute to close the last lifecycle hole (how long a job stays in = history).


    On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp <ipp@pwg.org> = wrote:

    Hi,

    I just read this entire thread = carefully.

    I = agree with all of your joint conclusions (good work Smith and = Mike),
    *except* for = "job-retain-until-xxx".

    I consider the lack of "job-retain-until-xxx" an = architectural mistake
    in IPP/1.1.  So I'd like = it to be present in Job Extensions, so that
    some = version lower than IPP/2.2 (Enterprise) can reliably use it.
    I suggest making it RECOMMENDED in IPP/2.0 and = REQUIRED
    in IPP/2.1 and above.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Wed, Mar 6, 2019 at 4:03 PM Michael = Sweet via ipp <ipp@pwg.org> wrote:
    Smith,

    On Mar = 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) = via ipp <ipp@pwg.org> wrote:
    ...
     Also, I don't think we want a = job-retain-until-time-default, since the value is an absolute dateTime = value (unless we make -time an integer and add a -date version for = dateTime?)

    Hmmm, how about just = having "job-retain-until" (type2 keyword) and "job-retain-until-time" = (integer) and not bother with "job-retain-until-date" = (dateTime)?

    Let's discuss this at the next concall - I can see a use for = both (retain the job for 24 hours, retain the job until the next = scheduled update), and a Client can calculate the number of seconds to a = specific date/time, but there are still some vagaries due to submission = delays and whether the IPP job ticket is used directly and immediately = or if it gets "relayed" to the destination output device that is doing = the retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

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

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_Qw4wWjCGif/pe/EoTlldFA)-- --===============6802625102569163632== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6802625102569163632==-- From ipp-bounces@pwg.org Thu Mar 7 09:06:47 2019 Return-Path: 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 0DA711277DB for ; Thu, 7 Mar 2019 09:06:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 4GqSCItwkMUP for ; Thu, 7 Mar 2019 09:06:45 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2781277CD for ; Thu, 7 Mar 2019 09:06:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id B60C63F4C; Thu, 7 Mar 2019 17:06:44 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 0D7A424D3; Thu, 7 Mar 2019 17:06:41 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 4379A3F46; Thu, 7 Mar 2019 17:06:39 +0000 (UTC) Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) by www.pwg.org (Postfix) with ESMTPS id CFE6D269F for ; Thu, 7 Mar 2019 17:06:38 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27H42JZ018180 for ; Thu, 7 Mar 2019 09:06:38 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=zxJmePgofno4tQ1LFrikQsF0Xg2PFMoeic4Gdv9ET0A=; b=oUU0xc4lBchqusLozoghc0B0hRv/LoZQ11fYHOpqjrcUL60mdPqbCBdG3YF3EYtKA9/8 Ev+FsW+KeBeCrBSkwTQBL0R9Stoc35AdSAgIDMSc3lQnFZqpXTnaYLfZ8acpg9wxk9X7 7T1Xa8pRgt38E47naIL8du0aBnZ8wALfQepsKB0R+uwVPxky3xoQM6/rHDztHHECTIUz Y55wIdT1yLPI3UcRATSOyfnnGtgVUVpvEXSilwZ45Nt+ORNP4GFZiB4AvZCZE0gVnkr8 YGcA9WiYzw/KhmqzPcUxbdnC+Hwo9TvUE+wjTcAyh6FY9PWo6cUBVSZ4RyVj+lKrkgsz 2g== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2r0ac459p5-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 07 Mar 2019 09:06:38 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO0000BWA6YMY90@ma1-mtap-s03.corp.apple.com> for ipp@pwg.org; Thu, 07 Mar 2019 09:06:36 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000K00A3RRR00@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:06:36 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: a3c7f7a0287aa937acd93c602b979a4f X-Va-R-CD: 1214055ef245cb6e27d6ed140ec1289c X-Va-CD: 0 X-Va-ID: 83936f0c-cc69-4626-ab42-a2c7f0c39a41 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: a3c7f7a0287aa937acd93c602b979a4f X-V-R-CD: 1214055ef245cb6e27d6ed140ec1289c X-V-CD: 0 X-V-ID: 775993b7-a457-41ae-ad70-9fdb42d386fa X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_09:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO000HCIA6XMU20@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:06:36 -0800 (PST) Date: Thu, 07 Mar 2019 12:06:33 -0500 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_09:, , signatures=0 Subject: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, For your consideration, the following two Printer Description attributes would allow a Client to discover (and potentially the administrator to configure since the values are settable) how long a Job will stay in the history phase. (I also considered "job-history-xxx" and "job-history-time-xxx" for the names; "interval" seemed the most consistent with other existing attributes, particularly with notifications) -------- job-history-interval-configured (integer(0:MAX)) This Printer Description attribute specifies the minimum number of seconds that a Job will remain in the history phase of its lifecycle [STD92]. Printers SHOULD have a default configured value of at least 60 seconds to allow Clients to discover the disposition of any Jobs that have reached a terminating state. This attribute MUST be supported if the "job-history-interval-supported" (section N.M.P) attribute is supported. job-history-interval-supported (rangeOfInteger(0:MAX)) This Printer Description attribute specifies the range of values that are supported for the "job-history-interval-configured" Printer Description attribute. This attribute MUST be supported if the "job-history-interval-configured" (section N.M.P) attribute is supported. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Mar 7 09:21:14 2019 Return-Path: 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 44041131163 for ; Thu, 7 Mar 2019 09:21:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 TX13WFo83uOJ for ; Thu, 7 Mar 2019 09:21:11 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 06757131414 for ; Thu, 7 Mar 2019 09:20:56 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 9AA163F52; Thu, 7 Mar 2019 17:20:56 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 3185426AA; Thu, 7 Mar 2019 17:20:52 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B42233F46; Thu, 7 Mar 2019 17:20:50 +0000 (UTC) Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) by www.pwg.org (Postfix) with ESMTPS id 15F8E24D3 for ; Thu, 7 Mar 2019 17:20:50 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27HH2Ua058334 for ; Thu, 7 Mar 2019 09:20:49 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : message-id : date : subject : in-reply-to : to : references; s=20180706; bh=sC+WGClUe+Qu8EZAX8Fa93A9aX/wOB93G7W7O6xqGEg=; b=p+Z1XN2DBVrNsHS4IaDqryeHIc4cHGeVK1YeDFjbTJCT9sshW0QDyVOg8HQULMQSQJF1 AUg8nDtenjlscpXV5PqYZRMkogqVfMwVQHV3dMPOtc1P/33GS7mdrZTKWfpGime+u8Mk lwJUJD+dqNs+C60fobhmhgV++VeO5J9slAGwGISzaAg61h8CNKxcuL3PFfgeCEEiartW N1rDXFU83rAtNA1BLkOZVGplgWxsFMyqCNbw8A58Uy6R8iQ2brf2m77nWiXeWAq1rLB9 9gzru7RZ381wvEg4D1ApXt+9dqgb6ziLztz2TVZFNrxB6fOIPAgCw7e14nD47FSPmWlt GQ== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2qyq9uv84u-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 07 Mar 2019 09:20:49 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO000896AUKD380@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Thu, 07 Mar 2019 09:20:46 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000F00ATXS800@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:20:46 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: 2ba23575614c14dc06ca9bc8897f7a7f X-Va-R-CD: a4a652d10e13906618d6e0edf3171ff5 X-Va-CD: 0 X-Va-ID: bddeea70-b2ce-4a46-963b-17c21e6c28e8 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 2ba23575614c14dc06ca9bc8897f7a7f X-V-R-CD: a4a652d10e13906618d6e0edf3171ff5 X-V-CD: 0 X-V-ID: debf4c7d-4b4e-4ec2-abf1-c0a769d57063 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_09:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO000HUWAUJMU20@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:20:45 -0800 (PST) Message-id: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> Date: Thu, 07 Mar 2019 12:20:43 -0500 In-reply-to: To: PWG IPP Workgroup References: X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_09:, , signatures=0 Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============2459258943012637165==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2459258943012637165== Content-type: multipart/alternative; boundary="Boundary_(ID_k0A2hYwCklKYSB1645wm3Q)" --Boundary_(ID_k0A2hYwCklKYSB1645wm3Q) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Oh, and as I was writing this up I thought of maybe the following as well (since IPP/1.1 is vague about what the history contains): job-history-attributes-configured (1setOf keyword) This Printer Description attribute lists the Job attributes that will be retained in the history phase of each Job. IPP/1.1 [STD92] specifies that at least the "job-id", "job-printer-uri", "job-state", and "job-state-reasons" attributes MUST be retained in the history phase. This attribute MUST be supported if the "job-history-attributes-supported" (section N.M.P) attribute is supported. job-history-attributes-supported (1setOf keyword) This Printer Description attribute lists the Job attributes that can be retained in the history phase of each Job. This attribute MUST be supported if the "job-history-attributes-configured" (section N.M.P) attribute is supported. > On Mar 7, 2019, at 12:06 PM, Michael Sweet wrote: > > All, > > For your consideration, the following two Printer Description attributes would allow a Client to discover (and potentially the administrator to configure since the values are settable) how long a Job will stay in the history phase. > > (I also considered "job-history-xxx" and "job-history-time-xxx" for the names; "interval" seemed the most consistent with other existing attributes, particularly with notifications) > > -------- > > job-history-interval-configured (integer(0:MAX)) > > This Printer Description attribute specifies the minimum number of seconds that a Job will remain in the history phase of its lifecycle [STD92]. Printers SHOULD have a default configured value of at least 60 seconds to allow Clients to discover the disposition of any Jobs that have reached a terminating state. > > This attribute MUST be supported if the "job-history-interval-supported" (section N.M.P) attribute is supported. > > > job-history-interval-supported (rangeOfInteger(0:MAX)) > > This Printer Description attribute specifies the range of values that are supported for the "job-history-interval-configured" Printer Description attribute. > > This attribute MUST be supported if the "job-history-interval-configured" (section N.M.P) attribute is supported. > > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_k0A2hYwCklKYSB1645wm3Q) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Oh, = and as I was writing this up I thought of maybe the following as well = (since IPP/1.1 is vague about what the history contains):

    job-history-attributes-configured (1setOf keyword)

    This Printer Description = attribute lists the Job attributes that will be retained in the history = phase of each Job. IPP/1.1 [STD92] specifies that at least the "job-id", = "job-printer-uri", "job-state", and "job-state-reasons" attributes MUST = be retained in the history phase.

    This attribute MUST be supported if the = "job-history-attributes-supported" (section N.M.P) attribute is = supported.


    job-history-attributes-supported = (1setOf keyword)

    This Printer Description attribute lists the Job attributes = that can be retained in the history phase of each Job.

    This = attribute MUST be supported if the "job-history-attributes-configured" = (section N.M.P) attribute is supported.


    On Mar 7, 2019, at 12:06 PM, Michael Sweet = <msweet@apple.com> wrote:

    All,

    For your consideration, the = following two Printer Description attributes would allow a Client to = discover (and potentially the administrator to configure since the = values are settable) how long a Job will stay in the history phase.

    (I also considered "job-history-xxx" and = "job-history-time-xxx" for the names; "interval" seemed the most = consistent with other existing attributes, particularly with = notifications)

    --------

    job-history-interval-configured (integer(0:MAX))

    This Printer Description attribute specifies = the minimum number of seconds that a Job will remain in the history = phase of its lifecycle [STD92]. Printers SHOULD have a default = configured value of at least 60 seconds to allow Clients to discover the = disposition of any Jobs that have reached a terminating state.

    This attribute MUST be supported if the = "job-history-interval-supported" (section N.M.P) attribute is = supported.


    job-history-interval-supported (rangeOfInteger(0:MAX))

    This Printer Description attribute specifies = the range of values that are supported for the = "job-history-interval-configured" Printer Description attribute.

    This attribute MUST be supported if the = "job-history-interval-configured" (section N.M.P) attribute is = supported.


    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer


    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_k0A2hYwCklKYSB1645wm3Q)-- --===============2459258943012637165== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2459258943012637165==-- From ipp-bounces@pwg.org Thu Mar 7 09:23:59 2019 Return-Path: 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 6796D12716C for ; Thu, 7 Mar 2019 09:23:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 6x73yIQn6p-o for ; Thu, 7 Mar 2019 09:23:57 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 5B82B12786D for ; Thu, 7 Mar 2019 09:23:56 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 2AFCD3F4E; Thu, 7 Mar 2019 17:23:56 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1C69924D3; Thu, 7 Mar 2019 17:23:51 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 1C1683F46; Thu, 7 Mar 2019 17:23:50 +0000 (UTC) Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by www.pwg.org (Postfix) with ESMTPS id E4A7124D3 for ; Thu, 7 Mar 2019 17:23:48 +0000 (UTC) Received: by mail-yw1-xc29.google.com with SMTP id n12so13939786ywn.13 for ; Thu, 07 Mar 2019 09:23:48 -0800 (PST) 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=+KH1/MzV5k/ZH1RJBwyFYApy+o5AauWFIQvvyuhg14M=; b=cozYTF0Hn3p1rxkG5I+t/oldjC3VYxd9xUikA7bUY0cseGyCeBTIux3s4QIMtE5nzz 6ach9rUyzl/5M3QsZejF5nrqe1XHvjYg61iKdqjzrIoVvSICSTh96KE/133bOEg8Y4Md VnQXU23lA7z7CvA+aegJi8Cv68SjQnY2WwEOVo6+YE05/AFW2mq1kAaWHzho8J5/dfHW ajtflQojbE22fcXtCfkKmPIwuHiXvSEHNDWc+6rPShoFbxk267OFqORMnX+wUP1wZ1eG /4AbUhtC4tX/UVlA3b2NznpYuaJjbvBiiLvhrGkwXGJs8WMPmD5tXKKKkUCTXRk6b515 HJkw== 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=+KH1/MzV5k/ZH1RJBwyFYApy+o5AauWFIQvvyuhg14M=; b=hOOMycFL+fsfeuU1yjpTCwNCq5fxk6LuTbfWcbX8BkUvr/k20ehbRX0Kxxac99AQGO QmPOfp6N2sKstFJ0YtYfRc7CYPS/RN3vaFQweYMiyvRwLmHKC4cXeocnllnHAskbpNC8 rX6FM0qJkV4ySYHvoL6i8jxHaI0J8ohcT01Ji/o5ja4RJDCFKmc/UouNBJFcv+o4S0iY jQjfxukvwmto1zooZoCf81Mci8VUayxm3CUVsAeyq2pYgXq1F1POYc8plDHWSrUzpoxc EpH6QNWaypfqT6a1qjK1/JlaXVC03w98Q+fJXqcDmJSZqq2t/JsHaxNsdbE5+SROPk2H ECTg== X-Gm-Message-State: APjAAAVdkLA/WSz5HzBwv2UBHNKQbW/IPFP2icmE2CHWs9Oia+cuOYlB SLpjLpTWaLPRjDj/jDaCPzD/EDJk8sNyJYqFAaU= X-Google-Smtp-Source: APXvYqxjSA74hZmml7Tr2S0WnJgE+gjFCs+n0eksC4U/K2n4Cd+lXEhI5uMDrBnb1fhCvbnL3q51QX26+WiYsOX78NM= X-Received: by 2002:a81:5f86:: with SMTP id t128mr11267442ywb.467.1551979428022; Thu, 07 Mar 2019 09:23:48 -0800 (PST) MIME-Version: 1.0 References: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> In-Reply-To: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> Date: Thu, 7 Mar 2019 12:23:35 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============5341027241005642662==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5341027241005642662== Content-Type: multipart/alternative; boundary="000000000000818ef50583845ee7" --000000000000818ef50583845ee7 Content-Type: text/plain; charset="UTF-8" Hi Mike, Yes, to all three of these proposed attributes. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp wrote: > Oh, and as I was writing this up I thought of maybe the following as well > (since IPP/1.1 is vague about what the history contains): > > job-history-attributes-configured (1setOf keyword) > > This Printer Description attribute lists the Job attributes that will be > retained in the history phase of each Job. IPP/1.1 [STD92] specifies that > at least the "job-id", "job-printer-uri", "job-state", and > "job-state-reasons" attributes MUST be retained in the history phase. > > This attribute MUST be supported if the "job-history-attributes-supported" > (section N.M.P) attribute is supported. > > > job-history-attributes-supported (1setOf keyword) > > This Printer Description attribute lists the Job attributes that can be > retained in the history phase of each Job. > > This attribute MUST be supported if the > "job-history-attributes-configured" (section N.M.P) attribute is supported. > > > On Mar 7, 2019, at 12:06 PM, Michael Sweet wrote: > > All, > > For your consideration, the following two Printer Description attributes > would allow a Client to discover (and potentially the administrator to > configure since the values are settable) how long a Job will stay in the > history phase. > > (I also considered "job-history-xxx" and "job-history-time-xxx" for the > names; "interval" seemed the most consistent with other existing > attributes, particularly with notifications) > > -------- > > job-history-interval-configured (integer(0:MAX)) > > This Printer Description attribute specifies the minimum number of seconds > that a Job will remain in the history phase of its lifecycle [STD92]. > Printers SHOULD have a default configured value of at least 60 seconds to > allow Clients to discover the disposition of any Jobs that have reached a > terminating state. > > This attribute MUST be supported if the "job-history-interval-supported" > (section N.M.P) attribute is supported. > > > job-history-interval-supported (rangeOfInteger(0:MAX)) > > This Printer Description attribute specifies the range of values that are > supported for the "job-history-interval-configured" Printer Description > attribute. > > This attribute MUST be supported if the "job-history-interval-configured" > (section N.M.P) attribute is supported. > > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --000000000000818ef50583845ee7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    Yes, to all three o= f these proposed attributes.

    Cheers,
    - I= ra

    =
    Ira McDonald (Musician / Softwa= re Architect)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-= Chair - TCG Metadata Access Protocol SG
    Chair - L= inux Foundation Open Printing WG
    Secretary - IEEE-ISTO Printer Working G= roup
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Desi= gnated Expert - IPP & Printer MIB
    Blue Roof Music / High North Inchttp://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc=
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2= =A0 906-494-2434

    <= /div>

    On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp <<= a href=3D"mailto:ipp@pwg.org">ipp@pwg.org> wrote:
    Oh, and as I was writing this up I thought of maybe the following a= s well (since IPP/1.1 is vague about what the history contains):

    job-history-attributes-configured (1setOf keyword)

    <= /div>
    This Printer Description attribute lists the Job attributes that = will be retained in the history phase of each Job. IPP/1.1 [STD92] specifie= s that at least the "job-id", "job-printer-uri", "= job-state", and "job-state-reasons" attributes MUST be retai= ned in the history phase.

    This attribute MUST be s= upported if the "job-history-attributes-supported" (section N.M.P= ) attribute is supported.


    job-histo= ry-attributes-supported (1setOf keyword)

    This Prin= ter Description attribute lists the Job attributes that can be retained in = the history phase of each Job.

    This attribute= MUST be supported if the "job-history-attributes-configured" (se= ction N.M.P) attribute is supported.


    On Mar 7, 2019, at 12:06 PM, Michael Sweet <msweet@apple.com> wr= ote:

    All,

    For your consideration, the following two Printer = Description attributes would allow a Client to discover (and potentially th= e administrator to configure since the values are settable) how long a Job = will stay in the history phase.

    (I also considered "job-history= -xxx" and "job-history-time-xxx" for the names; "interv= al" seemed the most consistent with other existing attributes, particu= larly with notifications)

    --------

    job-history-interval-confi= gured (integer(0:MAX))

    This Printer Description attribute specifies = the minimum number of seconds that a Job will remain in the history phase o= f its lifecycle [STD92]. Printers SHOULD have a default configured value of= at least 60 seconds to allow Clients to discover the disposition of any Jo= bs that have reached a terminating state.

    This attribute MUST be sup= ported if the "job-history-interval-supported" (section N.M.P) at= tribute is supported.


    job-history-interval-supported (rangeOfInt= eger(0:MAX))

    This Printer Description attribute specifies the range = of values that are supported for the "job-history-interval-configured&= quot; Printer Description attribute.

    This attribute MUST be supporte= d if the "job-history-interval-configured" (section N.M.P) attrib= ute is supported.


    ______________________________________________= ___________
    Michael Sweet, Senior Printing System Engineer

    =

    _____= ____________________________________________________
    Michael Sweet, Seni= or Printing System=C2=A0Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --000000000000818ef50583845ee7-- --===============5341027241005642662== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5341027241005642662==-- From ipp-bounces@pwg.org Thu Mar 7 09:37:51 2019 Return-Path: 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 08486124184 for ; Thu, 7 Mar 2019 09:37:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.281 X-Spam-Level: X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 upQCdaG40Mnr for ; Thu, 7 Mar 2019 09:37:47 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id C01B812716C for ; Thu, 7 Mar 2019 09:37:47 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 1FB603FCB; Thu, 7 Mar 2019 17:37:46 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1006126AA; Thu, 7 Mar 2019 17:37:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A4D2A3F46; Thu, 7 Mar 2019 17:37:38 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 9B3E1269F for ; Thu, 7 Mar 2019 17:37:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551980255; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=98jF7WGrFotNy4qvceCQUjHD6+Y3bQD60CEpDFtbXa0=; b=lG65e3IWkMkKU45DQbwPk0UDCC42DA7Xg8G/7R64TldM0IWCkeiLSgmPDYJw5Tpb8nIlUGrmmYDRIgjEW84IpmMBP2+nw98EPN1bQBShSMZMJu93u6ljxLKXbsS9TRmkuPOvCvixErkorKFDr9e0re9y+n4tjWjOB+G1D0H+i0c= Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-by2nam05lp2050.outbound.protection.outlook.com [104.47.50.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-264-RW6TsWJMOT-O9Gnn0AsFSw-1; Thu, 07 Mar 2019 12:37:32 -0500 X-MC-Unique: RW6TsWJMOT-O9Gnn0AsFSw-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1286.NAMPRD84.PROD.OUTLOOK.COM (10.169.97.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.18; Thu, 7 Mar 2019 17:37:30 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1686.018; Thu, 7 Mar 2019 17:37:30 +0000 To: Ira McDonald , Michael Sweet Thread-Topic: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes Thread-Index: AQHU1QhA3ZtQzxRNuk6njtkm0pXomaYAah+AgAAAzYCAAAPhAA== Date: Thu, 7 Mar 2019 17:37:30 +0000 Message-ID: <5E50B70A-EF28-4E22-AABA-196265FFA2E7@hp.com> References: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c0859237-890d-4beb-867f-08d6a32392fd x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1286; x-ms-traffictypediagnostic: CS1PR8401MB1286: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB1286; 23:pnAp74pVTkYMX3TYpxjZXa3ahiSXyg1BPZF/yrO?= =?us-ascii?Q?jxJsBCWPEo3NHebienEHSm/csDlelzUGJ7kvEB5oGb3ILZm4OJDtOupE4elX?= =?us-ascii?Q?HDMk3pcv9qHlfWTa/R5V18oF7/Jq7X1OWcw1zQ8kcTPa1p6o9B2jT0ck6oYk?= =?us-ascii?Q?ORCeZyBVBXYU91IRCUnuv01fwBNc+eGzJNOVcHtKkDVVMuw0tVo1qWhLcCh0?= =?us-ascii?Q?j2+l4IDoqjN+0hSFbe2n8/W1uxCqPmwKs71YYhUEqfdnF8/SyC6fXLbvZCmg?= =?us-ascii?Q?UVsPbNb5gcObfzu2ebT55P0BPqUy/GJAIRVougbXUS0u7dQMeaPJprYTnSjb?= =?us-ascii?Q?iIz3nvrUlp5voooPgdgimVW2C+Tadw1z8GbbO3APxHyu/PnE+TyreBEPCn7d?= =?us-ascii?Q?nebIuKCYgPoIkQFdEuStMt/9GJ01WJGqHp+b4k3qK0wvXSBrCj94urU0O8ld?= =?us-ascii?Q?KTvP1tbZpCPx4quM7qpnchBMuoMmnFxfUNZC0sBQlkE7hZMTWlhY9IejgsGT?= =?us-ascii?Q?pUctSTOBkX5XVCheUxpZi1FYiWGIFCz655yxVa0lGEF3OM+tFWTybKZAPy/m?= =?us-ascii?Q?s5yeivVnvGZbILonrg7o9HgR0TmrJqUTP+Wybf9Ii9A/SWGcU3rrFP+9Gny+?= =?us-ascii?Q?jsiF1Z5OGhUnR0ggDnRZfNxzdd/C62C75OK2FENoImqbLo8c1df+wYCbjoNH?= =?us-ascii?Q?4sNQTFCl61bANZwcx/Qp1JMy83CgEuvSohEmWmaKoOszP94kulKcyTdFteCZ?= =?us-ascii?Q?f4YWweFKc48jsWxfdREWVMCKlkNK3k4rZTakLUXZlFkq0Pg2ihqdovC57Yf/?= =?us-ascii?Q?g2eljoCTXj6+DEHW/2z8mC2BG6bhUY1El81cGuVXwyRqTqMlHnJ4nm1vTfhE?= =?us-ascii?Q?8pmdq2b3KYspIQquurkoUzbi7HPc5Orz6zX+DqmJVRWb4h4tjwSY19nJERGk?= =?us-ascii?Q?wOFiKzDH3DyVILKK0MyqAWHgFjKZUfXzYM7GwUOAAfb4kWgMeD9e82c7x8aP?= =?us-ascii?Q?80yko1QKWPVqaCFjLSclPeCVlAgvQ8CQf3xEsTd68nWw1A5aLdPSeIFEo6Yf?= =?us-ascii?Q?8ylhdfLHvRYENg70AQupcG0nsqu0ehVCk/acObzKB2xjd+F7TY1HnWCusSrL?= =?us-ascii?Q?vwNHGu4/vhJJ26I2+zJWCqLP+IygCVAThmHpc65guZSjMwfk2dmiVsnFSLKS?= =?us-ascii?Q?CsVcMQpr57PbEE267tKdsSI1CKLNERP+MZFnlGP3qsjTCQ/AR1fWEsypt6Tg?= =?us-ascii?Q?Yb2iAxWjJVLtD5P33J/zentRUuunq9LG0r4wrKMXARZmLlHmh/m2vWqyMN0M?= =?us-ascii?Q?NRPwGqCblCX9F69lpSl4DV8cJxCJxQpj2q438h443h+Nn2wnukuCsl8XC2NR?= =?us-ascii?Q?X2Nuq3E0oRyAhUO94X8hVSQ/cBY4sr1ro1Ccy6a7gGY/FtlGXI/ZUOn9OkWP?= =?us-ascii?Q?hDVfIbpPQzAnH7WFh0Ped3BzXcJsGk7gsx2B5MeeRPGYdeoLrPaLPsVeIo4L?= =?us-ascii?Q?QakHrMy0tPU6axV6pMDcGOn72sU9+1yIypT4=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 096943F07A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(346002)(136003)(39860400002)(396003)(6602003)(199004)(189003)(966005)(5660300002)(14454004)(606006)(53546011)(76176011)(478600001)(68736007)(99286004)(6506007)(19273905006)(8936002)(110136005)(486006)(81156014)(316002)(8676002)(476003)(7736002)(82746002)(446003)(11346002)(6116002)(81166006)(2616005)(3846002)(97736004)(102836004)(71200400001)(71190400001)(105586002)(186003)(66066001)(6486002)(83716004)(5070765005)(99936001)(26005)(256004)(14444005)(53936002)(36756003)(86362001)(2906002)(6512007)(54896002)(236005)(6306002)(6436002)(66574012)(25786009)(6246003)(33656002)(4326008)(106356001)(229853002)(21314003)(16351025005)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1286; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: rYIkqqvPS7vGCnC078pUDN5nKf9/UuaZ/BH/uBCw0qHnbfiFNGbQIpMQGco6CfMarwMTv/OChhTUacXWot7NW5k/sZ0wgTqMunorKXQlpm7tovjZP8DiqohzqTGwD/MvG984O16011FTBJJNpH2Ul6eZADEfsKZpVpbX/lfyipSnSdi6d3zMkfdTHIQIFJwfgDpx80Du6ji4FPMmIwnt/3kxi0m9h8G7Ns03/3dcoosoaCusuSmYYDwQy66q/1XSMAdaNqZdnQNRkcJZo5fFaGygTFzXDYSFxrcxH0OD4LbfVRDBG0F8/E7BJ+92vOwckyWtE3sKvYiGgWajXZpZVVTPbNOXh+LJTeZAU9eteuPMelXwXYw2opySPeNWRt8qL0qOkPae1Xv7jyh4MSfj4ADoZNLRcbP6h3ZeNywqins= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: c0859237-890d-4beb-867f-08d6a32392fd X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 17:37:30.3254 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1286 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============5233713588616997916==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5233713588616997916== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_7BC00215-2980-4CE1-A062-D94194DCB464"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_7BC00215-2980-4CE1-A062-D94194DCB464 Content-Type: multipart/alternative; boundary="Apple-Mail=_B453DD91-D3AE-4674-BFB4-B0F7B9822382" --Apple-Mail=_B453DD91-D3AE-4674-BFB4-B0F7B9822382 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii +1 for all 3 of them. To what spec do we want to add these? Job Extensions v1.1? Enterprise = Printing Extensions? Or System Service? > On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp wrote: >=20 > Hi Mike, >=20 > Yes, to all three of these proposed attributes. >=20 > Cheers, > - Ira >=20 > 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/highnorthinc = > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp > wrote: > Oh, and as I was writing this up I thought of maybe the following as = well (since IPP/1.1 is vague about what the history contains): >=20 > job-history-attributes-configured (1setOf keyword) >=20 > This Printer Description attribute lists the Job attributes that will = be retained in the history phase of each Job. IPP/1.1 [STD92] specifies = that at least the "job-id", "job-printer-uri", "job-state", and = "job-state-reasons" attributes MUST be retained in the history phase. >=20 > This attribute MUST be supported if the = "job-history-attributes-supported" (section N.M.P) attribute is = supported. >=20 >=20 > job-history-attributes-supported (1setOf keyword) >=20 > This Printer Description attribute lists the Job attributes that can = be retained in the history phase of each Job. >=20 > This attribute MUST be supported if the = "job-history-attributes-configured" (section N.M.P) attribute is = supported. >=20 >=20 >> On Mar 7, 2019, at 12:06 PM, Michael Sweet > wrote: >>=20 >> All, >>=20 >> For your consideration, the following two Printer Description = attributes would allow a Client to discover (and potentially the = administrator to configure since the values are settable) how long a Job = will stay in the history phase. >>=20 >> (I also considered "job-history-xxx" and "job-history-time-xxx" for = the names; "interval" seemed the most consistent with other existing = attributes, particularly with notifications) >>=20 >> -------- >>=20 >> job-history-interval-configured (integer(0:MAX)) >>=20 >> This Printer Description attribute specifies the minimum number of = seconds that a Job will remain in the history phase of its lifecycle = [STD92]. Printers SHOULD have a default configured value of at least 60 = seconds to allow Clients to discover the disposition of any Jobs that = have reached a terminating state. >>=20 >> This attribute MUST be supported if the = "job-history-interval-supported" (section N.M.P) attribute is supported. >>=20 >>=20 >> job-history-interval-supported (rangeOfInteger(0:MAX)) >>=20 >> This Printer Description attribute specifies the range of values that = are supported for the "job-history-interval-configured" Printer = Description attribute. >>=20 >> This attribute MUST be supported if the = "job-history-interval-configured" (section N.M.P) attribute is = supported. >>=20 >>=20 >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >>=20 >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = > _______________________________________________ > ipp mailing list > ipp@pwg.org > = https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=3Dpwg.org = --Apple-Mail=_B453DD91-D3AE-4674-BFB4-B0F7B9822382 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii +1 = for all 3 of them.

    To = what spec do we want to add these? Job Extensions v1.1? Enterprise = Printing Extensions? Or System Service?

    On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp <ipp@pwg.org> = wrote:

    Hi Mike,

    Yes, to all three of these proposed = attributes.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221  = Grand Marais, MI 49839  906-494-2434


    On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via = ipp <ipp@pwg.org> = wrote:
    Oh, and as I was writing this up I thought of maybe the = following as well (since IPP/1.1 is vague about what the history = contains):

    job-history-attributes-configured (1setOf keyword)

    This Printer Description = attribute lists the Job attributes that will be retained in the history = phase of each Job. IPP/1.1 [STD92] specifies that at least the "job-id", = "job-printer-uri", "job-state", and "job-state-reasons" attributes MUST = be retained in the history phase.

    This attribute MUST be supported if the = "job-history-attributes-supported" (section N.M.P) attribute is = supported.


    job-history-attributes-supported = (1setOf keyword)

    This Printer Description attribute lists the Job attributes = that can be retained in the history phase of each Job.

    This = attribute MUST be supported if the "job-history-attributes-configured" = (section N.M.P) attribute is supported.


    On Mar 7, 2019, at 12:06 PM, Michael Sweet = <msweet@apple.com> wrote:

    All,

    For your = consideration, the following two Printer Description attributes would = allow a Client to discover (and potentially the administrator to = configure since the values are settable) how long a Job will stay in the = history phase.

    (I also considered = "job-history-xxx" and "job-history-time-xxx" for the names; "interval" = seemed the most consistent with other existing attributes, particularly = with notifications)

    --------

    job-history-interval-configured = (integer(0:MAX))

    This Printer Description = attribute specifies the minimum number of seconds that a Job will remain = in the history phase of its lifecycle [STD92]. Printers SHOULD have a = default configured value of at least 60 seconds to allow Clients to = discover the disposition of any Jobs that have reached a terminating = state.

    This attribute MUST be supported if = the "job-history-interval-supported" (section N.M.P) attribute is = supported.


    job-history-interval-supported (rangeOfInteger(0:MAX))

    This Printer Description attribute specifies = the range of values that are supported for the = "job-history-interval-configured" Printer Description attribute.

    This attribute MUST be supported if the = "job-history-interval-configured" (section N.M.P) attribute is = supported.


    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer


    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain= =3Dpwg.org

    = --Apple-Mail=_B453DD91-D3AE-4674-BFB4-B0F7B9822382-- --Apple-Mail=_7BC00215-2980-4CE1-A062-D94194DCB464 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyBVtgACgkQqskbKLDW 1N35Dg//dw7Nzi8QMJgbMVUHu8uvtNAeZUCV4lOEX0+MaqyWBL3xJznTLpu1c+hu eclztOFm5uifBZjd1xEHjKTJU8g7CRFoWvR9umstRNSFt5XYPesvmr+vd+LYCEEZ e+7OcJ3QtecaV3d7DdeXN6gdQj8bTckW0NpE/Apte+pH2lxUOE7IquqNPa+we2bs V4KZjTKhXLTSuEyMAjI9zy4O5lnXSBRFlXkMVvcPyBV2cBdGqlA4KCeyNzrpouQj ezrVKJfMFYBtbxK+9LeHTk7so+iwX0biMYBwmBJQgwhygArfAa8Dikdus4nw8DJ8 uUulwFm4Az3A31O0rQdC4LBR/IBJt0APKqFanK7/x89diBeT5kMuLnUZ/lqc34+D +kTMxzVFb6HI7Jdd4vUL1tN+a1RMbNqt8oUYcmw1MKdL1DAVnaQnbYJN2U4tU0RL E+eR9YUhwpegxT9YOBdHlO2nNn027iPRw7r6o5UqLSOq+CacU9q1OBlL4AXL+GzT TUaHsMTBeOXwziCut9AGk3u6kK4jhr6KBCZGpqSBlRc+/GQ0peo5FsnTeckD6L3R I5YkNxxo/Sl/YJ9J7zVjhdGFZYma+aGl6NrxZhy9Tg87vUCathDnJObTWo3xkLri 1Cu2ixvqSzoRf//2BExrkto0lKSKFlV8SXnDCeRogISTh/xSIHc= =wRbS -----END PGP SIGNATURE----- --Apple-Mail=_7BC00215-2980-4CE1-A062-D94194DCB464-- --===============5233713588616997916== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5233713588616997916==-- From ipp-bounces@pwg.org Thu Mar 7 09:39:38 2019 Return-Path: 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 A5132124BA8 for ; Thu, 7 Mar 2019 09:39:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 OgXnKSYiy0ET for ; Thu, 7 Mar 2019 09:39:36 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 4B27E124184 for ; Thu, 7 Mar 2019 09:39:36 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 39B233F52; Thu, 7 Mar 2019 17:39:36 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 7BB0926AA; Thu, 7 Mar 2019 17:39:30 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A66A73F46; Thu, 7 Mar 2019 17:39:29 +0000 (UTC) Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) by www.pwg.org (Postfix) with ESMTPS id 553BC269F for ; Thu, 7 Mar 2019 17:39:28 +0000 (UTC) Received: by mail-yw1-xc2f.google.com with SMTP id 189so13998721ywi.3 for ; Thu, 07 Mar 2019 09:39:28 -0800 (PST) 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=NDkm/8GNkVfVnI+m89432QvNQEhTEq+9adZPBTerU7A=; b=UNOGtReIhlICqvyIvPCB8wRezD6mgVFNEx8/vvcwiuYraAq7w96yCXtopKq0FIJzth uCJPS0AWHQu3cU4/E54DIXrCzLfbSbDXwBSz/9h/Z0xBKspGJBd+a/QY06S9GdAMuqxL h+kbE7ihOUso5HNzCyhwfiq2+Xuci28Lsos3k9uGgjYxWafZHvduR4+EPNvO4czhcPym FgYt985aC/geMBuRHMW9Gx6s09OpenuYnD5ZnhsA5uIp/v3jSyKH7ccAUjSGVbre4oSG aGcE8WhkGD3X8CpTlJvHTQWVaqdhG16tjxOPl42UHSAdoCBdNOXZF1CzksWVdfQ5Oauz zrIg== 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=NDkm/8GNkVfVnI+m89432QvNQEhTEq+9adZPBTerU7A=; b=GJEuleOiB8jLo8BaUlo4HKU3S0G8LmIizi3MzUFDjzZj5Yx/NX86evxjtzyJFbtnHu hayfpSF6p0ndX3rc63WHmgCUTUjehsoDmam9UROsv9ixmYvDNiIaFvN6LDtO+yjOTq9R djhdiCr/rPddQZQKK5XizNn+hZPMeSnLmXMTMImLIaT9BFSIOUyLhPHPbrrhzrPh7yS7 HKho7G4Ce2DrSo45rKuD6bnn4v7dwSqwt3nCT0D/8Ca4une8pWvC+PBGQXIkivKiXm3i uDoRK870pzxzFYbJYWW0lH2vCgcqyQrzIWzi0TO8I3RlfJrNPmj1EoO6+x9mk8onuqAv qdvQ== X-Gm-Message-State: APjAAAWJqdW9vh3zjMXp/r9Jo6uWLp1odMctEvDF0lCiaoQ0NVNW88Ix DZa0jjvhjfTrYXRQhYRCprKzFa5cBurExnS+rlQ= X-Google-Smtp-Source: APXvYqyunjw5OUQKIyfLg4Yyb+ggq0t0bhaAWV79MiTF6GLGJ3KwzcSpx+5T0aC3t/hskjnjgn/hmDruui+fnkmSy0k= X-Received: by 2002:a25:646:: with SMTP id 67mr12161426ybg.472.1551980367354; Thu, 07 Mar 2019 09:39:27 -0800 (PST) MIME-Version: 1.0 References: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> <5E50B70A-EF28-4E22-AABA-196265FFA2E7@hp.com> In-Reply-To: <5E50B70A-EF28-4E22-AABA-196265FFA2E7@hp.com> Date: Thu, 7 Mar 2019 12:39:14 -0500 Message-ID: To: "Kennedy, Smith (Wireless & Standards Architect)" , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============2319309616798424713==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2319309616798424713== Content-Type: multipart/alternative; boundary="0000000000007ea3fc05838496bc" --0000000000007ea3fc05838496bc Content-Type: text/plain; charset="UTF-8" Hi, I hope Job Extensions, because I see them as filling holes in original IPP/1.1. All printers implement some Job History (perhaps pretty short-lived). 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 12:37 PM Kennedy, Smith (Wireless & Standards Architect) wrote: > +1 for all 3 of them. > > To what spec do we want to add these? Job Extensions v1.1? Enterprise > Printing Extensions? Or System Service? > > On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp wrote: > > Hi Mike, > > Yes, to all three of these proposed attributes. > > 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/highnorthinc > > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp wrote: > >> Oh, and as I was writing this up I thought of maybe the following as well >> (since IPP/1.1 is vague about what the history contains): >> >> job-history-attributes-configured (1setOf keyword) >> >> This Printer Description attribute lists the Job attributes that will be >> retained in the history phase of each Job. IPP/1.1 [STD92] specifies that >> at least the "job-id", "job-printer-uri", "job-state", and >> "job-state-reasons" attributes MUST be retained in the history phase. >> >> This attribute MUST be supported if the >> "job-history-attributes-supported" (section N.M.P) attribute is supported. >> >> >> job-history-attributes-supported (1setOf keyword) >> >> This Printer Description attribute lists the Job attributes that can be >> retained in the history phase of each Job. >> >> This attribute MUST be supported if the >> "job-history-attributes-configured" (section N.M.P) attribute is supported. >> >> >> On Mar 7, 2019, at 12:06 PM, Michael Sweet wrote: >> >> All, >> >> For your consideration, the following two Printer Description attributes >> would allow a Client to discover (and potentially the administrator to >> configure since the values are settable) how long a Job will stay in the >> history phase. >> >> (I also considered "job-history-xxx" and "job-history-time-xxx" for the >> names; "interval" seemed the most consistent with other existing >> attributes, particularly with notifications) >> >> -------- >> >> job-history-interval-configured (integer(0:MAX)) >> >> This Printer Description attribute specifies the minimum number of >> seconds that a Job will remain in the history phase of its lifecycle >> [STD92]. Printers SHOULD have a default configured value of at least 60 >> seconds to allow Clients to discover the disposition of any Jobs that have >> reached a terminating state. >> >> This attribute MUST be supported if the "job-history-interval-supported" >> (section N.M.P) attribute is supported. >> >> >> job-history-interval-supported (rangeOfInteger(0:MAX)) >> >> This Printer Description attribute specifies the range of values that are >> supported for the "job-history-interval-configured" Printer Description >> attribute. >> >> This attribute MUST be supported if the "job-history-interval-configured" >> (section N.M.P) attribute is supported. >> >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> >> > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=pwg.org > > > --0000000000007ea3fc05838496bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    I hope Job Extensions, b= ecause I see them as filling holes in original IPP/1.1.
    All print= ers implement some Job History (perhaps pretty short-lived).
    =
    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
    Sec= retary - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PWG Intern= et Printing Protocol WG
    IETF Designated Expert - IPP & Printer MIBBlue Roof Music / High North Inc
    http://s= ites.google.com/site/blueroofmusic
    http:= //sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box= 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434

    <= /div>


    On Thu, Mar 7, 2019 at 1= 2:37 PM Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    =
    +1 for all 3 of them.

    To what spec do w= e want to add these? Job Extensions v1.1? Enterprise Printing Extensions? O= r System Service?

    On Mar 7, 2019, at 10:23 AM, Ira Mc= Donald via ipp <ipp@pwg= .org> wrote:

    Hi Mike,
    <= div>
    Yes, to all three of these proposed attributes.

    Cheers,
    - Ira

    = Ira McDonald (Musician / Software Architect)
    Co-Chair - TCG Trusted Mobi= lity Solutions WG
    Co-Chair - TCG Metadata Access Protocol SG
    <= /div>
    Chair - Linux Foundation Open Printing WG
    Secretar= y - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PWG Internet Pr= inting Protocol WG
    IETF Designated Expert - IPP & Printer MIB
    Blu= e Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusichttp= ://sites.google.com/site/highnorthinc
    mailto:=C2=A0blueroofmusic@gmail.com
    PO = Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434



    On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp <ipp@pwg.org> wrote:
    =
    Oh, and as I w= as writing this up I thought of maybe the following as well (since IPP/1.1 = is vague about what the history contains):

    job-history-a= ttributes-configured (1setOf keyword)

    This Printer= Description attribute lists the Job attributes that will be retained in th= e history phase of each Job. IPP/1.1 [STD92] specifies that at least the &q= uot;job-id", "job-printer-uri", "job-state", and &= quot;job-state-reasons" attributes MUST be retained in the history pha= se.

    This attribute MUST be supported if the "= job-history-attributes-supported" (section N.M.P) attribute is support= ed.


    job-history-attributes-supporte= d (1setOf keyword)

    This Printer Description attrib= ute lists the Job attributes that can be retained in the history phase of e= ach Job.

    This attribute MUST be supported if = the "job-history-attributes-configured" (section N.M.P) attribute= is supported.


    = On Mar 7, 2019, at 12:06 PM, Michael Sweet <msweet@apple.com> wrote:

    All,

    For your consideration, the following two Pri= nter Description attributes would allow a Client to discover (and potential= ly the administrator to configure since the values are settable) how long a= Job will stay in the history phase.

    (I also considered "job-hi= story-xxx" and "job-history-time-xxx" for the names; "i= nterval" seemed the most consistent with other existing attributes, pa= rticularly with notifications)

    --------

    job-history-interval-= configured (integer(0:MAX))

    This Printer Description attribute speci= fies the minimum number of seconds that a Job will remain in the history ph= ase of its lifecycle [STD92]. Printers SHOULD have a default configured val= ue of at least 60 seconds to allow Clients to discover the disposition of a= ny Jobs that have reached a terminating state.

    This attribute MUST b= e supported if the "job-history-interval-supported" (section N.M.= P) attribute is supported.


    job-history-interval-supported (range= OfInteger(0:MAX))

    This Printer Description attribute specifies the r= ange of values that are supported for the "job-history-interval-config= ured" Printer Description attribute.

    This attribute MUST be sup= ported if the "job-history-interval-configured" (section N.M.P) a= ttribute is supported.


    _________________________________________= ________________
    Michael Sweet, Senior Printing System Engineer

    <= /div>

    _____________________________= ____________________________
    Michael Sweet, Senior Printing System=C2=A0= Engineer

    ___________________= ____________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    _________________= ______________________________
    ipp mailing list
    ipp@pwg.org
    https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnW= WIGXtnT?domain=3Dpwg.org

    --0000000000007ea3fc05838496bc-- --===============2319309616798424713== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2319309616798424713==-- From ipp-bounces@pwg.org Thu Mar 7 09:42:48 2019 Return-Path: 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 ED7B31277D6 for ; Thu, 7 Mar 2019 09:42:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.281 X-Spam-Level: X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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 kzDOI9xSZK8Z for ; Thu, 7 Mar 2019 09:42:45 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 97EAB1277D8 for ; Thu, 7 Mar 2019 09:42:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 418E73F9C; Thu, 7 Mar 2019 17:42:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id D92BD269F; Thu, 7 Mar 2019 17:42:37 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 166B93F46; Thu, 7 Mar 2019 17:42:37 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id EB509269F for ; Thu, 7 Mar 2019 17:42:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551980555; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BxFErP7I3BHu4POOSr9mD4O8YqWTtwqyEaVmb1YJboA=; b=mAK0wxC/ZNAFQplOLnELedKTfnRrXio2Ehek2IkjD043zxSLkuZ3TAZJcc9q+zO/SBC7SH/LkF4HZhyBnEJkmAzMsxzBI970I87MMNNWwV3wNtBQw2pYY6KZYybrw8usl3JdHIqnSU+BFdVtb0jp414ydwwA5dYDd/sJUoR9HDM= Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-by2nam05lp2059.outbound.protection.outlook.com [104.47.50.59]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-1-Uevz366nORejrwaj28Cz4A-1; Thu, 07 Mar 2019 12:42:33 -0500 X-MC-Unique: Uevz366nORejrwaj28Cz4A-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1286.NAMPRD84.PROD.OUTLOOK.COM (10.169.97.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.18; Thu, 7 Mar 2019 17:42:31 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1686.018; Thu, 7 Mar 2019 17:42:31 +0000 To: Ira McDonald Thread-Topic: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes Thread-Index: AQHU1QhA3ZtQzxRNuk6njtkm0pXomaYAah+AgAAAzYCAAAPhAIAAAH4AgAAA6gA= Date: Thu, 7 Mar 2019 17:42:31 +0000 Message-ID: <2632F4D9-FE84-4548-93E1-19D0D18746BE@hp.com> References: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> <5E50B70A-EF28-4E22-AABA-196265FFA2E7@hp.com> In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 053b93b0-3ec3-4538-73d3-08d6a3244693 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1286; x-ms-traffictypediagnostic: CS1PR8401MB1286: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB1286; 23:/8XLq4SqUSJ68sFbl+RIEVANNO/a9UjoY6Pp6HY?= =?us-ascii?Q?owrt2fRQxA7jiI7O+BBsHxmnRegU0+ryw5EQ26J6ew2MlxgWcOiS/QF6tOxx?= =?us-ascii?Q?0foyE5juW7RRcGy0GvLbzNj19rMhYP3eAA1ongRf8KepcAV4I7RAOPZHW7n4?= =?us-ascii?Q?hmvngfqZxAPqpACXsGDfaHqFqyligi5RvJvjfF3fA+Px/M+qu30DbTv9ml/D?= =?us-ascii?Q?92KuhmI4JMkPpPmrxbkZYUS0VO48hXh0/PWkyVZTEFgw1kXjTMa1Y5uqFjgq?= =?us-ascii?Q?vL7T385RvQ+Q9ajkm45oY2t/aZ8F+8/TdemHCsqa1uHX46tZgXOnsQZafsR4?= =?us-ascii?Q?U/2gPrS/bh2VEbWoXHuwvnJVBdvzFGjE4Or+4GN1el/1TLCM+PRAscZDbG7+?= =?us-ascii?Q?KhqE8nTHUoNuHeYj3aEaNk2rk6T11ea7lFUd1/OEkOFL8m+1Hy20eWrS8GAh?= =?us-ascii?Q?fd6hn1Mc4dVRY9RCKWkCMl6jwsKcdjPqRcvYWPB2XCoMBjCMRT0YeCT1Qlv6?= =?us-ascii?Q?PjvAueEm7mi5l7i5pcBYcadIFgfqKZDtjuGdvsFwgT8hc67RWXdyMxMxqjWH?= =?us-ascii?Q?J0FCEfv5S0klduciEo9KksLXdTxr8ZYsg6iDhtRdUf+m57MIZH8mvzCSZc10?= =?us-ascii?Q?NJNcY7MSGQYGgTfekzrKyBloaygswU0T8unnS0/nj8kSBw7b+ILTcx9aTvmw?= =?us-ascii?Q?DQ0uWXyZdYgQPHV1H2d3ZdmmTwzhayJHlHOw6ciXXmRONoYnn0+WFo/kbVJb?= =?us-ascii?Q?28vVZWrrhgRam9/iN6LXc6rw84w7exGeYw73k9gVCRLrMmAzpga+gdwD0cGz?= =?us-ascii?Q?WrGavFPqT4IZhx1eJEgU4m8xbwzOTEfs7lJa1rS5QsqJq05E/KSz9FGMGWR7?= =?us-ascii?Q?UR/smebfbAkjvfk822nY3iFchbQxN+Xr4kfi+HB7GTi66IMSLIUZP9PUkwzi?= =?us-ascii?Q?UJSjvVLCjqspPh0CsemomtA6CDMoZQ6xrvNcwmAbEWOo4nHhmt9BMSRnFUi3?= =?us-ascii?Q?jJO8FJLAq1XybBEEm/MxQYtpq7wo3ia2UIIPSXAnO7bCGHrDg+6wUUkOQW+9?= =?us-ascii?Q?wZD31UHpJIB7hQVew/BSY+SL7YrfIegurdChpevsvswcRfnvP4jH39q0fzlR?= =?us-ascii?Q?oyV3dbdWlNsVgx9q3kXT+K/6UueeOpmzo+V34bAXpjuXsQWO1rLuBk31wcFZ?= =?us-ascii?Q?Y/fc9tPptvPAIefeCrO9vJcoYzqooETiw+py1Wzn59bqjKChIyoln15ibyUP?= =?us-ascii?Q?Y0Tva3D5zeOZtsQf9udJ2Ndo4+k31wEM2ascIatCE4/k9pmU6Be9QyvSmMEo?= =?us-ascii?Q?60//Vu8KSvQuiXgd2C4fWGAh+tQ39E3eFPxwZNd4VjnHqw2pT7KOUJrbZM+f?= =?us-ascii?Q?y993dMHtfz+txgQeooRtXdJLjqaBEwxSIbVXp+FuKgfFOkwXcHmuzRAUWOYe?= =?us-ascii?Q?O2e9FO/CgCr1DqGwvNEb+XNRlRP8LGJQbtBQXBwUINujy8MfW2rb82jVwm0n?= =?us-ascii?Q?aqo74Fc+vz0dMtbahtf/EAIlGXOUxkQrxjTkfiupkAQRfYBD4wzcmRtUYIt5?= =?us-ascii?Q?p1eww3mK8mjQjbU2VVCQJKvtbalD/XiOgDRzJyutR1DXNk9u5LJq5kj4FQ1+?= =?us-ascii?Q?uVLKC0AOuhVyWECGLPv5Yiv5Zhr34jBeqnTlUfR+kpK7Yb2HFwLGBD9yHB+n?= =?us-ascii?Q?tinG2?= x-microsoft-antispam-prvs: x-forefront-prvs: 096943F07A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(396003)(39860400002)(136003)(366004)(376002)(346002)(6602003)(189003)(199004)(14444005)(53936002)(256004)(99936001)(6916009)(26005)(2906002)(36756003)(86362001)(71200400001)(71190400001)(102836004)(5070765005)(83716004)(186003)(105586002)(6486002)(66066001)(25786009)(6246003)(33656002)(229853002)(106356001)(4326008)(236005)(6306002)(54896002)(6512007)(66574012)(6436002)(6506007)(99286004)(93886005)(19273905006)(14454004)(5660300002)(606006)(966005)(76176011)(478600001)(68736007)(53546011)(7736002)(316002)(8676002)(476003)(1411001)(97736004)(446003)(11346002)(6116002)(82746002)(3846002)(81166006)(2616005)(81156014)(8936002)(486006)(54906003)(21314003)(16351025005)(563064011)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1286; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: UUJJ5bfMFcEZrwjK8vEFTIqTjOOXrvC+TmCbycJOU30hsUVscA8OSSxnUxKESOHJc25VuLDy9kpjj47tVRrYfhVEYbG3ndCk7N+g+CvpPDSFQu6VekpXsqRe3rkfM9mNjJKYSQdM3B/ic4vqWvkPmjquCxDV0PpWXV5H7jZ3syG+o5zJ/nSfstCBbdD40bX60uUt9mQIpvni3jko8ALhvx6dNqX611pmycJyBMNlQlbTWJZgfpXGJRNd1cFTsmRZTQBeh2h7kbENtBltdXwM0FutqXnCNvkDiBiDOXNs+KJLkwd08G6QM6UHOTeR1G+4FXsXM5YkcTkUQ/U6eQTT1/DF7ay0lCpstTzogLSlmltFOu7Q8zHPIdrlua7aTYF6ypv4m4o/nqzIuDy/t+KlNCrp8BfipPP8nha4gRYaxa0= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 053b93b0-3ec3-4538-73d3-08d6a3244693 X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 17:42:31.6491 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1286 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============2264813545806852721==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2264813545806852721== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_84B5B4B6-27F4-48C8-970B-9537F77FD13B"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_84B5B4B6-27F4-48C8-970B-9537F77FD13B Content-Type: multipart/alternative; boundary="Apple-Mail=_B65F785B-09CE-4FF8-9756-FF6F991AE774" --Apple-Mail=_B65F785B-09CE-4FF8-9756-FF6F991AE774 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Defining them in Job Extensions v1.1 seems to be what Mike is = recommending in the other thread about JPS2v2. Smith > On Mar 7, 2019, at 10:39 AM, Ira McDonald = wrote: >=20 > Hi, >=20 > I hope Job Extensions, because I see them as filling holes in original = IPP/1.1. > All printers implement some Job History (perhaps pretty short-lived). >=20 > Cheers, > - Ira >=20 > 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/highnorthinc = > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Thu, Mar 7, 2019 at 12:37 PM Kennedy, Smith (Wireless & Standards = Architect) > wrote: > +1 for all 3 of them. >=20 > To what spec do we want to add these? Job Extensions v1.1? Enterprise = Printing Extensions? Or System Service? >=20 >> On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp > wrote: >>=20 >> Hi Mike, >>=20 >> Yes, to all three of these proposed attributes. >>=20 >> Cheers, >> - Ira >>=20 >> 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/highnorthinc = >> mailto: blueroofmusic@gmail.com >> PO Box 221 Grand Marais, MI 49839 906-494-2434 >>=20 >>=20 >>=20 >> On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp > wrote: >> Oh, and as I was writing this up I thought of maybe the following as = well (since IPP/1.1 is vague about what the history contains): >>=20 >> job-history-attributes-configured (1setOf keyword) >>=20 >> This Printer Description attribute lists the Job attributes that will = be retained in the history phase of each Job. IPP/1.1 [STD92] specifies = that at least the "job-id", "job-printer-uri", "job-state", and = "job-state-reasons" attributes MUST be retained in the history phase. >>=20 >> This attribute MUST be supported if the = "job-history-attributes-supported" (section N.M.P) attribute is = supported. >>=20 >>=20 >> job-history-attributes-supported (1setOf keyword) >>=20 >> This Printer Description attribute lists the Job attributes that can = be retained in the history phase of each Job. >>=20 >> This attribute MUST be supported if the = "job-history-attributes-configured" (section N.M.P) attribute is = supported. >>=20 >>=20 >>> On Mar 7, 2019, at 12:06 PM, Michael Sweet > wrote: >>>=20 >>> All, >>>=20 >>> For your consideration, the following two Printer Description = attributes would allow a Client to discover (and potentially the = administrator to configure since the values are settable) how long a Job = will stay in the history phase. >>>=20 >>> (I also considered "job-history-xxx" and "job-history-time-xxx" for = the names; "interval" seemed the most consistent with other existing = attributes, particularly with notifications) >>>=20 >>> -------- >>>=20 >>> job-history-interval-configured (integer(0:MAX)) >>>=20 >>> This Printer Description attribute specifies the minimum number of = seconds that a Job will remain in the history phase of its lifecycle = [STD92]. Printers SHOULD have a default configured value of at least 60 = seconds to allow Clients to discover the disposition of any Jobs that = have reached a terminating state. >>>=20 >>> This attribute MUST be supported if the = "job-history-interval-supported" (section N.M.P) attribute is supported. >>>=20 >>>=20 >>> job-history-interval-supported (rangeOfInteger(0:MAX)) >>>=20 >>> This Printer Description attribute specifies the range of values = that are supported for the "job-history-interval-configured" Printer = Description attribute. >>>=20 >>> This attribute MUST be supported if the = "job-history-interval-configured" (section N.M.P) attribute is = supported. >>>=20 >>>=20 >>> _________________________________________________________ >>> Michael Sweet, Senior Printing System Engineer >>>=20 >>=20 >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >>=20 >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp = >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> = https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=3Dpwg.org = --Apple-Mail=_B65F785B-09CE-4FF8-9756-FF6F991AE774 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
    Defining them in Job Extensions v1.1 seems to be what Mike is = recommending in the other thread about JPS2v2.

    Smith



    On Mar 7, 2019, at 10:39 AM, Ira McDonald <blueroofmusic@gmail.com> wrote:

    Hi,

    I hope Job Extensions, = because I see them as filling holes in original IPP/1.1.
    All printers implement some Job History (perhaps pretty = short-lived).

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Thu, Mar 7, 2019 at 12:37 PM = Kennedy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    +1 for all 3 of them.

    To what spec do we want to add these? = Job Extensions v1.1? Enterprise Printing Extensions? Or System = Service?

    On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi Mike,

    Yes, to all three of = these proposed attributes.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221  = Grand Marais, MI 49839  906-494-2434


    On Thu, Mar 7, = 2019 at 12:21 PM Michael Sweet via ipp <ipp@pwg.org> wrote:
    Oh, and as I was = writing this up I thought of maybe the following as well (since IPP/1.1 = is vague about what the history contains):

    job-history-attributes-configured = (1setOf keyword)

    This Printer Description attribute lists the Job attributes = that will be retained in the history phase of each Job. IPP/1.1 [STD92] = specifies that at least the "job-id", "job-printer-uri", "job-state", = and "job-state-reasons" attributes MUST be retained in the history = phase.

    This = attribute MUST be supported if the "job-history-attributes-supported" = (section N.M.P) attribute is supported.


    job-history-attributes-supported (1setOf keyword)

    This Printer Description = attribute lists the Job attributes that can be retained in the history = phase of each Job.

    This attribute MUST be supported if the = "job-history-attributes-configured" (section N.M.P) attribute is = supported.


    On Mar = 7, 2019, at 12:06 PM, Michael Sweet <msweet@apple.com> wrote:

    All,

    For your consideration, the following two Printer Description = attributes would allow a Client to discover (and potentially the = administrator to configure since the values are settable) how long a Job = will stay in the history phase.

    (I also = considered "job-history-xxx" and "job-history-time-xxx" for the names; = "interval" seemed the most consistent with other existing attributes, = particularly with notifications)

    --------

    job-history-interval-configured = (integer(0:MAX))

    This Printer Description = attribute specifies the minimum number of seconds that a Job will remain = in the history phase of its lifecycle [STD92]. Printers SHOULD have a = default configured value of at least 60 seconds to allow Clients to = discover the disposition of any Jobs that have reached a terminating = state.

    This attribute MUST be supported if = the "job-history-interval-supported" (section N.M.P) attribute is = supported.


    job-history-interval-supported (rangeOfInteger(0:MAX))

    This Printer Description attribute specifies = the range of values that are supported for the = "job-history-interval-configured" Printer Description attribute.

    This attribute MUST be supported if the = "job-history-interval-configured" (section N.M.P) attribute is = supported.


    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer


    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    _______________________________________________
    ipp mailing = list
    ipp@pwg.org
    https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain= =3Dpwg.org


    = --Apple-Mail=_B65F785B-09CE-4FF8-9756-FF6F991AE774-- --Apple-Mail=_84B5B4B6-27F4-48C8-970B-9537F77FD13B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyBWAYACgkQqskbKLDW 1N0ZLA//fnnUDDCYPVX+7CiZ2FDp2b72+IdxPr1oxATpygFqoBKaT9gCDbDDHJhr 3C/XUlR3YVDueHZQVq0VmAe5Ti+2tYdfApnA/d7ixvYbGsYsf8KRKIuXe+kNJaY/ efxd2KTohnUHHQx/obZyW8WQ1T0AdjHQsqmDenTbmEmnlZZBODCuFxQHiEI1luFk HsXqfVOc4Yo1dagosMXhbBP3jqHD5WyXo7aFPVVL7i4+2SUaHyyF8udlYoHWCcaf M4lniOzh7qIvagzAYUslEm2Y9r3V36hLhYNBpENvoO54Aug2QZbBHl3PKbozYRf/ SeJqgLQR8dacEK7YxC5rOpbDmQL7phxJuWW9gqczPRkeHnDY/8DUNpfoQDTrI6HL e0KsM/+w6EEAM18hDipUx0HBL/OfAOAIwF1czGJn4KCeMk8s6TazBM1hOkGFEpNb g4jXwYJKLQoUYYz2TqjToMxHHCDa7Up9ieK1Pa2rk9bJO8blTjipG0ueoKd5hSYc qqjNixMkNKFceD6NEG9GOND2rKX3tqZs/afrOPQvxmstxyHoHQV2iSGgDTnmJ8sw L2CIKbTodGwPUuD9f6+HhgySRpET5XOsxmgRG3X23J7cicYavH7adJVefYqntRBI QPhjogFdEKkLhtzyrnydvPSu+bCw8SjBCw8saubsDsiF/qt99K0= =BLyt -----END PGP SIGNATURE----- --Apple-Mail=_84B5B4B6-27F4-48C8-970B-9537F77FD13B-- --===============2264813545806852721== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2264813545806852721==-- From ipp-bounces@pwg.org Thu Mar 7 09:43:58 2019 Return-Path: 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 EE64A1277E0 for ; Thu, 7 Mar 2019 09:43:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.709 X-Spam-Level: X-Spam-Status: No, score=-0.709 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 ZpMpLixXf74t for ; Thu, 7 Mar 2019 09:43:53 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id B16E3130F04 for ; Thu, 7 Mar 2019 09:43:53 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 551173F4E; Thu, 7 Mar 2019 17:43:53 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 9E53D3F48; Thu, 7 Mar 2019 17:43:47 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 19B553F47; Thu, 7 Mar 2019 17:43:46 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 0AFAF24D3 for ; Thu, 7 Mar 2019 17:43:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1551980623; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tEo6uakCqfdogs4SasqgTaek1WEWxI00pt8xrQOjZwc=; b=nYXKjlQ0XVoEw0yZvLbiprmqfYOwq2oig/R22p+iojbLGSmUR9qPKSB8RT0J77TeyYw9U0LE/q/FaQ6e8OOYlCRTPtLJpoq/9BzghSWnr0O0RkXcT4baM9txCJTqcUTUTRg+pttQJaLgGzOfz+qtuu/SZCh1VSEiyLPMQzi4F2o= Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-bn3nam04lp2052.outbound.protection.outlook.com [104.47.46.52]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-325-Ark3Wk42OJ-rohXEbil1-w-1; Thu, 07 Mar 2019 12:43:42 -0500 X-MC-Unique: Ark3Wk42OJ-rohXEbil1-w-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1317.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.18; Thu, 7 Mar 2019 17:43:41 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1686.018; Thu, 7 Mar 2019 17:43:41 +0000 To: Michael Sweet Thread-Topic: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? Thread-Index: AQHUz6ygHr0UwLDskEmAk4liLFoBzaX1x4gAgAkrkoCAAAbDgIAAIJ8AgAAGFwCAAA1mgIABQH+AgAAMx4A= Date: Thu, 7 Mar 2019 17:43:40 +0000 Message-ID: References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b403f96f-0f15-41a7-8f8d-08d6a3246fe4 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1317; x-ms-traffictypediagnostic: CS1PR8401MB1317: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB1317; 23:HVsRVzGj4Dp1H8tVNne9YcNbbiFrX0tgAQgEQIZ?= =?us-ascii?Q?PxJyASzasc2EXjvZBVKipDzlHG4cYDZPtoJioGbhEEBIlIKEsGmatkhBiDEj?= =?us-ascii?Q?FtqJJH3TtbvkPBe+X8Tz6sSLoB3zw8/jEmerLb7ROlIuRkHLlbPZgqjxVBGq?= =?us-ascii?Q?f8rf5tGpCz0QsSDqBLCjFRoQ8+4CS/DsK4v3sVpCxUS22NkKZ2dOQZ3Q6guK?= =?us-ascii?Q?xMFUSSV+Pxn5ZLy3itcbGR5o5gvn1e0nVFWOmqXYBbGaL+ymguwobUo6RoOj?= =?us-ascii?Q?0NlHfnXcnezVdXxBDRJTLt/BsUNpyYYFllpRzooMPzPraQPTXAWBjkfD4Dnm?= =?us-ascii?Q?bh7jNAvQ4UwTxQ1CPkIiGpDtLOxb0utG0IoS6bq3uW/XVcKvuGj32ffl9GKx?= =?us-ascii?Q?7g4pKBb1iC8vhlXqyG+M18YfNdCSPODy08BKcl3BUd2YKs5+xQHDrd/Xysk6?= =?us-ascii?Q?JCaw3w/SbKzHTnlIWQchQD5kndINO/KfJQ3RPDkfxG+IwUQgZlx7k4mMS9/9?= =?us-ascii?Q?4/l/+ByJ3lmQaQ4PxglQQymjUS4DCCGUHat03AOvFcmLdpFwxajpV6ZxxBPr?= =?us-ascii?Q?dXUgXBLpvAnjWJ5NCiMlEX6duaVzomWqXvgKYL9XNxNxQRRoArL1xMXn6LrH?= =?us-ascii?Q?VfXK8xO2AF7IWmEUgR68ckzXbZZf6s5JRUiNTt9MGo/Qg3lXnz1MxbQcG3If?= =?us-ascii?Q?3++bLGo/0C9lBXfg+MwH50aIS8IfhD9aXsLMPSuYV4KE02Smrsn1ghAzjOID?= =?us-ascii?Q?CpnYcxMg4ntZkhwQ/F1Kj56kHVQL4BnGpwnz1UPyfaLp6jXZovkBlWRwGf/h?= =?us-ascii?Q?MhSDpkHn/IF+uHoxiiHykDaWhuQbZ8IBOmo186XnYVbcJhSWnuJNDFLI7Vaz?= =?us-ascii?Q?uvXzzWWieQQAuHjcQaFZ1TuFJCNJBU/bnaweYpIg75SkwPHQZ4g0fogT0o/2?= =?us-ascii?Q?aV5OjtV6GQ233Fc8mJlkqp7y+0be6Uk03MQQoh7SVHm5TGLdzqB5cv17j8Su?= =?us-ascii?Q?pPIoSzn/p9umIz8SzvIdbeqOt7s1LQmLyq9RQ8LuMwHnlGH4mKRP3N8b40ci?= =?us-ascii?Q?ieu+aMMM8QhwWvOn7Q3w0jgH6BJ98secPc71bu8h9UeOPVVugnc4Pinj8uRP?= =?us-ascii?Q?sOwG7u7PYlfOViFcQG9QC9SIKy7n3FjZ2mx9XjtUCoCMhWsKxpVyb0iqcUDZ?= =?us-ascii?Q?f0qK3BpU9BefOONOhkAn9n849rZApjLjzHPEKW7+eJL92Xr04g462Vy6JOVM?= =?us-ascii?Q?b/GX/twlPzzR8muGsFZ6KePZFsdLNKCniYx2QleaoBnE1VZC9M2UBN7mHvU4?= =?us-ascii?Q?+gtaJCDap1clOipKKvIMUkjQojyV5v0r8Rv42wT6kHTiczmANHrWPKMtd7X0?= =?us-ascii?Q?7GcXR7tpA1KqQIGsswvKCOt9b624ykr6hjpy+WVk9evJa0KKrv5ia412l6l+?= =?us-ascii?Q?LYK5qRu2RrJyYrGJY4VgLZzOjNH1/TIoh+EIQpONvNlRmWc/QRnsWzRK4WiU?= =?us-ascii?Q?YOSqN8BYYKpPMPNaq1jLm7cS5XA3c/aW9i8Qn63L2BxkabM4l7ilIRcLsyti?= =?us-ascii?Q?2vMOO8VP8sTtmdcWQJg=3D=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 096943F07A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(396003)(346002)(39860400002)(376002)(189003)(199004)(6602003)(71190400001)(54906003)(229853002)(6512007)(105586002)(86362001)(2906002)(83716004)(71200400001)(54896002)(6436002)(5660300002)(6306002)(53936002)(66574012)(236005)(6486002)(446003)(11346002)(97736004)(476003)(14444005)(93886005)(5070765005)(486006)(186003)(106356001)(82746002)(256004)(36756003)(2616005)(8936002)(3846002)(4326008)(14454004)(25786009)(6116002)(99286004)(478600001)(66066001)(316002)(6506007)(76176011)(102836004)(7736002)(99936001)(68736007)(26005)(81166006)(53546011)(81156014)(8676002)(6916009)(19273905006)(33656002)(966005)(6246003)(606006)(21314003)(16351025005)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1317; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: erWzhZUh8K3l0PsAL0w/j3mEYHszI7d9bqk1EKDXtyf+bajwPf/4/uQ83d1mH47GZYbSxynh9hM3Iq21NRj2XKBee6OtzUshFwXI43wx+dDm/K/hgfVUhybxu5xApIEiBGxL9yzbo4DNIy1YB/Wf5sIb50WTgVp9tWSd79O7Gx8xgGbBy47eftMnuQMbzyKz0Lj6GiffagD4O6Nnm73IcdwqQmvlFShF8CuB0zBmuAx+l2vHJLFo4hDUbkbYAcYzNOPO34pbu9g4eqNMKHBKjNX1U7NCcCazTknNnmjKu3TaDEemq8aU+ImLYZVblyEEwKDlppReIiiDbG9iiBJd4bjdSlvzPZeZGpEaaq773DMEt2s2ORmo5PV1ljn9hGAD7BnhQAJWzPQuA+nuBYC+orLyhPOx3EOdQuyCgtI2uUI= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: b403f96f-0f15-41a7-8f8d-08d6a3246fe4 X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 17:43:40.9252 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1317 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8699683404692473452==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8699683404692473452== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_A4734783-912E-46AB-8767-160DD6097158"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_A4734783-912E-46AB-8767-160DD6097158 Content-Type: multipart/alternative; boundary="Apple-Mail=_ED648EDA-1CC9-4F59-8D9C-0CF186673F59" --Apple-Mail=_ED648EDA-1CC9-4F59-8D9C-0CF186673F59 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I'm good with all of these being in Job Extensions v1.1: job-delay-output-until... job-retain-until... job-history-interval-supported/-configured > On Mar 7, 2019, at 9:57 AM, Michael Sweet via ipp wrote: >=20 > Well, if we put job-retain-until in Job Extensions 1.1, then we should = probably put job-delay-output-until in JOBEXT as well (since now we'll = have a bunch of Job Template attributes in JOBEXT that control = scheduling/job lifecycle decisions) >=20 > Just remember that in JOBEXT all of this will be OPTIONAL anyways. >=20 > I will also post a RFC for another attribute to close the last = lifecycle hole (how long a job stays in history). >=20 >=20 >> On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp > wrote: >>=20 >> Hi, >>=20 >> I just read this entire thread carefully. >>=20 >> I agree with all of your joint conclusions (good work Smith and = Mike), >> *except* for "job-retain-until-xxx". >>=20 >> I consider the lack of "job-retain-until-xxx" an architectural = mistake >> in IPP/1.1. So I'd like it to be present in Job Extensions, so that >> some version lower than IPP/2.2 (Enterprise) can reliably use it. >> I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED >> in IPP/2.1 and above. >>=20 >> Cheers, >> - Ira >>=20 >> 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/highnorthinc = >> mailto: blueroofmusic@gmail.com >> PO Box 221 Grand Marais, MI 49839 906-494-2434 >>=20 >>=20 >>=20 >> On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp > wrote: >> Smith, >>=20 >>> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >>> ... >>>> Also, I don't think we want a job-retain-until-time-default, since = the value is an absolute dateTime value (unless we make -time an integer = and add a -date version for dateTime?) >>>=20 >>> Hmmm, how about just having "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and not bother with = "job-retain-until-date" (dateTime)? >>=20 >> Let's discuss this at the next concall - I can see a use for both = (retain the job for 24 hours, retain the job until the next scheduled = update), and a Client can calculate the number of seconds to a specific = date/time, but there are still some vagaries due to submission delays = and whether the IPP job ticket is used directly and immediately or if it = gets "relayed" to the destination output device that is doing the = retaining... >>=20 >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >>=20 >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp = >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp = >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > = https://protect-us.mimecast.com/s/LqgrC82A5AhMX1GLfnkXWj?domain=3Dpwg.org --Apple-Mail=_ED648EDA-1CC9-4F59-8D9C-0CF186673F59 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I'm = good with all of these being in Job Extensions v1.1:

    job-delay-output-until...
    job-retain-until...
    job-history-interval-supported/-configured


    On Mar 7, 2019, at 9:57 AM, Michael Sweet via ipp <ipp@pwg.org> = wrote:

    Well,= if we put job-retain-until in Job Extensions 1.1, then we should = probably put job-delay-output-until in JOBEXT as well (since now we'll = have a bunch of Job Template attributes in JOBEXT that control = scheduling/job lifecycle decisions)

    Just remember that in JOBEXT all of = this will be OPTIONAL anyways.

    I will also post a RFC for another = attribute to close the last lifecycle hole (how long a job stays in = history).


    On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp <ipp@pwg.org> = wrote:

    Hi,

    I just read this entire thread = carefully.

    I = agree with all of your joint conclusions (good work Smith and = Mike),
    *except* for = "job-retain-until-xxx".

    I consider the lack of "job-retain-until-xxx" an = architectural mistake
    in IPP/1.1.  So I'd like = it to be present in Job Extensions, so that
    some = version lower than IPP/2.2 (Enterprise) can reliably use it.
    I suggest making it RECOMMENDED in IPP/2.0 and = REQUIRED
    in IPP/2.1 and above.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Wed, Mar 6, 2019 at 4:03 PM Michael = Sweet via ipp <ipp@pwg.org> wrote:
    Smith,

    On Mar = 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) = via ipp <ipp@pwg.org> wrote:
    ...
     Also, I don't think we want a = job-retain-until-time-default, since the value is an absolute dateTime = value (unless we make -time an integer and add a -date version for = dateTime?)

    Hmmm, how about just = having "job-retain-until" (type2 keyword) and "job-retain-until-time" = (integer) and not bother with "job-retain-until-date" = (dateTime)?

    Let's discuss this at the next concall - I can see a use for = both (retain the job for 24 hours, retain the job until the next = scheduled update), and a Client can calculate the number of seconds to a = specific date/time, but there are still some vagaries due to submission = delays and whether the IPP job ticket is used directly and immediately = or if it gets "relayed" to the destination output device that is doing = the retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

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

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    _______________________________________________
    ipp = mailing list
    ipp@pwg.org
    https://protect-us.mimecast.com/s/LqgrC82A5AhMX1GLfnkXWj?domain= =3Dpwg.org

    = --Apple-Mail=_ED648EDA-1CC9-4F59-8D9C-0CF186673F59-- --Apple-Mail=_A4734783-912E-46AB-8767-160DD6097158 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyBWEsACgkQqskbKLDW 1N00gA//QiFWQFaDCTF/+b9dK3cvpb5sti1JHJhvK2+tmV5T8N4cb2KwC/wodPAN EBzjPrR5wsu7Carqju9I/4MNdDqQWMd3Er6AxS5uNTJxwr1KI4ufUC9m93ZolV5C 1LnD61p3e0EkI06XM0AeK3sDNyEV3zGlnjGDqD07jumIBdqg3MYKfJfMW/nLcNgO kxbnwlIg1S3wT24gpqDZrdExKuJWzE9oyJ2QXKDMVz0GVuX+gkmGZ2uPUMbY5dVf lTdl32rznc0EYGG8PvLLqI5TE0YkIOVJ4sU5bfvy1W3LXC/IU3PZUS7YMjTZtLsy Ow6u1eDi5zQAZj1J+oBHQ0Tb+DoQ78HKgfYfni07V2Jz/gEw0F+/fabtqsp+M/kV WAnnPHiAGX22pGUTESZF2j64mbCktcVOxWizRAaMhGYQohLSWxh2HzE6uOkVhIcu 7tq4KjKca+PewCILTTpPqJ5RsLMNJV5HiUG29O/lUND9a8D0uh1BsWmIbngoma9V p3/DsgqDwqLq/vjf+1doKR7/ayPjD7ybVeyLlT9O7zd8NgqyKRJiGVh+mUd2c8aB wFiAzPCmsDSZyOXfCNcYOXoQZFA0I+GqI9j5ofg3RKL6+Jo4tAsqoWMlwTuAJzhL fDWMWKvBUs0c01NlWscNOdmRbu6JnZwPE0V22oH55G11AYHzAPs= =YSfM -----END PGP SIGNATURE----- --Apple-Mail=_A4734783-912E-46AB-8767-160DD6097158-- --===============8699683404692473452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8699683404692473452==-- From ipp-bounces@pwg.org Thu Mar 7 09:48:02 2019 Return-Path: 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 13B8F124BA8 for ; Thu, 7 Mar 2019 09:48:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.281 X-Spam-Level: X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, RCVD_IN_DNSWL_NONE=-0.0001, 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=rsharepoint.onmicrosoft.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 NzCH2LAwiodt for ; Thu, 7 Mar 2019 09:47:59 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id A4014124184 for ; Thu, 7 Mar 2019 09:47:59 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 7C2EE3F4E; Thu, 7 Mar 2019 17:47:59 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id E382E26AA; Thu, 7 Mar 2019 17:47:50 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 347823F46; Thu, 7 Mar 2019 17:47:49 +0000 (UTC) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-eopbgr810082.outbound.protection.outlook.com [40.107.81.82]) by www.pwg.org (Postfix) with ESMTPS id 342FD269F for ; Thu, 7 Mar 2019 17:47:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rsharepoint.onmicrosoft.com; s=selector1-ricohusa-com01c; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=nOgSsEPdY5Pcj+n6WGcwcLQOCFoiZFQpx4BKZd1luxI=; b=bY7XhUwSoqeE5iYl4F1asyFrYqS77XNijELpbfz4/fpN02RLrl/UeUuUqXiUcH2uPPVjPhY+Hsz6xZArKBcwAViSK/M7oOum8KTNjmQcePIZshm3mDbmR0csirXocdG/VzBn1cHWQncx3OpoPRpI9PhdrlxESHh8cxcDcOxrP/o= Received: from BN7PR17MB2242.namprd17.prod.outlook.com (20.176.24.140) by BN7PR17MB2129.namprd17.prod.outlook.com (20.176.23.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.18; Thu, 7 Mar 2019 17:47:45 +0000 Received: from BN7PR17MB2242.namprd17.prod.outlook.com ([fe80::5138:f808:1a2e:e86f]) by BN7PR17MB2242.namprd17.prod.outlook.com ([fe80::5138:f808:1a2e:e86f%4]) with mapi id 15.20.1686.018; Thu, 7 Mar 2019 17:47:45 +0000 To: Ira McDonald , "Kennedy, Smith (Wireless & Standards Architect)" Thread-Topic: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes[EXTERNAL] Thread-Index: AQHU1Qgt7XBwoH1S20epTmyC0M2k+6YAah+AgAAAzYCAAAPkAIAAAHwAgAACYcQ= Date: Thu, 7 Mar 2019 17:47:45 +0000 Message-ID: References: <424C1AE7-38A7-483C-85B0-C200A702B143@apple.com> <5E50B70A-EF28-4E22-AABA-196265FFA2E7@hp.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=ulrich.wehner@ricoh-usa.com; x-originating-ip: [52.14.141.67] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 47258ba0-5424-4e11-6151-08d6a325019f x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BN7PR17MB2129; x-ms-traffictypediagnostic: BN7PR17MB2129: x-ms-exchange-purlcount: 5 x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; BN7PR17MB2129; 23:rZSmZuufzQ6Fxpea8s+iNFdcJeAkEgk0JfDuzhhRh?= =?us-ascii?Q?zyhM9DSAaWRpy4bhY4Sl6n0Ed45nppoMfug1XD+GB73CwNyFYjXeX6LgHVEj?= =?us-ascii?Q?0ZDcp4d7PFDQ9ryugDjW4YgedMN+WvdnKEHU1dkeMTDn5WJOjE7E2cworBg8?= =?us-ascii?Q?adKCumcC6/4p7WvRRb1wKCSbtG47IgGDmia2EBrs1q2OxVT/t6AtWfI3kxws?= =?us-ascii?Q?LQwAca7ss94oVx1WYiCzhr5qOtvptHfMpubrFJl2ZUUyLU2z2yvhfCF321M0?= =?us-ascii?Q?ggCse0kVVlcXGYPsz+svDcj9qv3BQAKvUYVrKuN+qmVn1YkhuHZKhiiJyDsg?= =?us-ascii?Q?bQGkvGv7IqViYVPYdtzpMV+OKmHKPJ43jgZays8NCwYVIKPKSgFfzKEC+AGh?= =?us-ascii?Q?LKdhInfr4U5kJhLQU7A/cNzoUhDJOvnaArc2kZNcz+y/bPOIxHOeUf926AEN?= =?us-ascii?Q?Eq8iD2h0h8TXGrlttThKmk7DUeyB21xmyCkDMqTuP7jZkjl6LfVnG1gzj27J?= =?us-ascii?Q?ZHq73zuoUX0JUTMUDOSCw9334Ls5MuFE2efuo4z1H8GRUwWMU2EYmGZRnTg9?= =?us-ascii?Q?RcoabtCxTbYR7TU8MMVDYksy0EsoY8YM46BolOJRPpCLhkHUcplDGp06caIb?= =?us-ascii?Q?5lmzl2YSndZE9gZJuLc++/CDce8aU/WOzh/rOKNKq+0ODUR5JbOQ5u+1rjEm?= =?us-ascii?Q?nqQikQMY3NIAVc5jhbIB/MMNu7QHnB+uXRwjvYl/2lyA09C8BWjtvwZgeaUB?= =?us-ascii?Q?PQn4ielxKT7e+WhbFHYNcqHB0KWuzfuatHJAILKqF1uqC6ZdqxnpAw7PnLbf?= =?us-ascii?Q?ZxA38i4j0DBdNkj8yldqmLMrV/NCc5urvG24zxVe0zsKHpqR9xsIrjZIf7l6?= =?us-ascii?Q?VRlvx6kzz4wXmr+ddoZ0MoiuC8qmp9V6iss4Rp6pkGPr062SvLNLSE1Ux4nI?= =?us-ascii?Q?l7r+cP0xmWgknZPkXRt+bRfxNIdy15YooOHcyNHGW7/6orOrOGYChWWGSc3F?= =?us-ascii?Q?xVo/wIktW2CM4SDFuFFMJWmPPkY676ti2nB+fFjy6RYyXo3nDCsYb05yg+pq?= =?us-ascii?Q?7R9iHxiXKEvHNsYYVPthvG5OZc6FuvAm/cxNhHiaUnW9GvZmsg0LK7IzGO6Y?= =?us-ascii?Q?3qgsKHcEP3Zlfr+xt9rci1KzScxYTO70Wi9OQcllMyzMicT/HZzIfdzXXXKu?= =?us-ascii?Q?SqwiHTlUrka4u73pVKZ78KW9TP3dZQPZfiKSo1TNcQUzdPi1vw8OPj91v+Jm?= =?us-ascii?Q?wJFy+8hjqLhM11eiT7KpjqBJ7BcPoGK/PoXF4dX8rRYHuRCeghRJ5tdtfpPS?= =?us-ascii?Q?TLVLoMiRs68pfM5eW8Zh/xOz7upZixWWpfGuxu0CRX0Et9nusrSd9atdX7Vv?= =?us-ascii?Q?mmHjdzksOMlqokOiY2yi7KbBWHZ/HkTOlia9UyPhxKDE4UIN4LfFgcoCkn37?= =?us-ascii?Q?fEJrgzLYJmza2jL+sZCsEoi6Yj+8NLimDF0SFttfvWlpeeUKGJho7fSm53g5?= =?us-ascii?Q?+/JGopGpTRxAg=3D=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 096943F07A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(396003)(376002)(39860400002)(136003)(189003)(199004)(229853002)(14454004)(97736004)(3846002)(6116002)(33656002)(478600001)(606006)(66066001)(68736007)(966005)(6436002)(6246003)(2906002)(316002)(110136005)(19273905006)(5070765005)(106356001)(102836004)(7736002)(186003)(105586002)(26005)(74316002)(14444005)(71200400001)(71190400001)(53546011)(52536013)(55236004)(66574012)(6506007)(93886005)(99286004)(11346002)(476003)(236005)(486006)(76176011)(5660300002)(7696005)(9686003)(54896002)(6306002)(256004)(446003)(86362001)(55016002)(4326008)(53936002)(81166006)(81156014)(8936002)(25786009)(8676002)(21314003)(16351025005)(563064011); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR17MB2129; H:BN7PR17MB2242.namprd17.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ricoh-usa.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: co9kiv3PxtPSk4UcOMjaxHjb0xXKXokPyxpRmOCoFTV1JbwH2cQJVM3tTldh6qdjUQIxKcv3nMM846F9Tf/JsRRSo3dseKXjXC4zW7j2V7EhIzUcR8OTs54uJe5PHbJ+GNMteaVjd/rwhfKNaDvZOjUNLEw+PhajRb1vcQ6QMpljg1w/enH1HqsJmsZG8TirKOGQWR/Qe0BguGDA9xMDrvINrQ3znmZyqNooQ+ee59Xt+MS2kAm4YmA7j8HtxNysZoPaToOTYEIt8dAKN/KHppRRfEWYCEnIYCi3ALoyGt9cAriI2hrdsJx1mGUF9zR89OVOPcSNFelcJJCjZjfyNoLGBJg3OOB3U1ASUJ89ltW9e1REX64hVZQSr2UDieCBYQlLbeI/1oNcAhiTzwzyJU/gki0/OcQEWwhUY0g5d5c= MIME-Version: 1.0 X-OriginatorOrg: ricoh-usa.com X-MS-Exchange-CrossTenant-Network-Message-Id: 47258ba0-5424-4e11-6151-08d6a325019f X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2019 17:47:45.4072 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: cbdb0d78-6a1f-4b73-98a2-ed310274376c X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR17MB2129 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer Description attributes[EXTERNAL] X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Uli Wehner via ipp Reply-To: Uli Wehner Content-Type: multipart/mixed; boundary="===============8649174146848380214==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8649174146848380214== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BN7PR17MB224207166BA374964B6D43F9A44C0BN7PR17MB2242namp_" --_000_BN7PR17MB224207166BA374964B6D43F9A44C0BN7PR17MB2242namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ira Ours do keep jobs in history until they scroll of the screen if you will. W= eeks even months. However if you send hundreds of 1 pagers, they drop off q= uickly. 60 seconds sounds like a good default for the print controller to k= eep track of them Sent from my Sprint Samsung Galaxy S9. -------- Original message -------- From: Ira McDonald via ipp Date: 3/7/19 12:40 (GMT-05:00) To: "Kennedy, Smith (Wireless & Standards Architect)" , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Printer = Description attributes[EXTERNAL] Hi, I hope Job Extensions, because I see them as filling holes in original IPP/= 1.1. All printers implement some Job History (perhaps pretty short-lived). 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 12:37 PM Kennedy, Smith (Wireless & Standards Archit= ect) > wrote: +1 for all 3 of them. To what spec do we want to add these? Job Extensions v1.1? Enterprise Print= ing Extensions? Or System Service? On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp > wrote: Hi Mike, Yes, to all three of these proposed attributes. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 12:21 PM Michael Sweet via ipp > wrote: Oh, and as I was writing this up I thought of maybe the following as well (= since IPP/1.1 is vague about what the history contains): job-history-attributes-configured (1setOf keyword) This Printer Description attribute lists the Job attributes that will be re= tained in the history phase of each Job. IPP/1.1 [STD92] specifies that at = least the "job-id", "job-printer-uri", "job-state", and "job-state-reasons"= attributes MUST be retained in the history phase. This attribute MUST be supported if the "job-history-attributes-supported" = (section N.M.P) attribute is supported. job-history-attributes-supported (1setOf keyword) This Printer Description attribute lists the Job attributes that can be ret= ained in the history phase of each Job. This attribute MUST be supported if the "job-history-attributes-configured"= (section N.M.P) attribute is supported. On Mar 7, 2019, at 12:06 PM, Michael Sweet > wrote: All, For your consideration, the following two Printer Description attributes wo= uld allow a Client to discover (and potentially the administrator to config= ure since the values are settable) how long a Job will stay in the history = phase. (I also considered "job-history-xxx" and "job-history-time-xxx" for the nam= es; "interval" seemed the most consistent with other existing attributes, p= articularly with notifications) -------- job-history-interval-configured (integer(0:MAX)) This Printer Description attribute specifies the minimum number of seconds = that a Job will remain in the history phase of its lifecycle [STD92]. Print= ers SHOULD have a default configured value of at least 60 seconds to allow = Clients to discover the disposition of any Jobs that have reached a termina= ting state. This attribute MUST be supported if the "job-history-interval-supported" (s= ection N.M.P) attribute is supported. job-history-interval-supported (rangeOfInteger(0:MAX)) This Printer Description attribute specifies the range of values that are s= upported for the "job-history-interval-configured" Printer Description attr= ibute. This attribute MUST be supported if the "job-history-interval-configured" (= section N.M.P) attribute is supported. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp _______________________________________________ ipp mailing list ipp@pwg.org https://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=3Dpwg.org --_000_BN7PR17MB224207166BA374964B6D43F9A44C0BN7PR17MB2242namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
    Ira

    Ours do keep jobs in history until they scroll of the screen if you wi= ll. Weeks even months. However if you send hundreds of 1 pagers, they drop = off quickly. 60 seconds sounds like a good default for the print controller= to keep track of them



    Sent from my Sprin= t Samsung Galaxy S9.


    -------- Original message --------
    From: Ira McDonald via ipp <ipp@pwg.org>
    Date: 3/7/19 12:40 (GMT-05:00)
    To: "Kennedy, Smith (Wireless & Standards Architect)" &l= t;smith.kennedy@hp.com>, Ira McDonald <blueroofmusic@gmail.com>
    Cc: PWG IPP Workgroup <ipp@pwg.org>
    Subject: Re: [IPP] RFC: job-history-interval-configured/-supported Pri= nter Description attributes[EXTERNAL]

    Hi,

    I hope Job Extensions, because I see them as filling holes in original= IPP/1.1.
    All printers implement some Job History (perhaps pretty short-lived).<= br>

    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.g= oogle.com/site/highnorthinc
    mailto: bluero= ofmusic@gmail.com
    PO Box 221  Grand Marais, MI 49839  906-494-2434



    On Thu, Mar 7, 2019 at 12:37 PM Kenne= dy, Smith (Wireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    +1 for all 3 of them.

    To what spec do we want to add these? Job Extensions v1.1? Enterprise = Printing Extensions? Or System Service?

    On Mar 7, 2019, at 10:23 AM, Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi Mike,

    Yes, to all three of these proposed attributes.

    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/highnorthinc
    mailto:&nb= sp;    blue= roofmusic@gmail.com
    PO Box 221  Grand Marais, MI 49839  906-494-2434



    On Thu, Mar 7, 2019 at 12:21 PM Micha= el Sweet via ipp <ipp@p= wg.org> wrote:
    Oh, and as I was writing this up I thought of maybe the following as w= ell (since IPP/1.1 is vague about what the history contains):

    job-history-attributes-configured (1setOf keyword)

    This Printer Description attribute lists the Job attributes that will = be retained in the history phase of each Job. IPP/1.1 [STD92] specifies tha= t at least the "job-id", "job-printer-uri", "job-s= tate", and "job-state-reasons" attributes MUST be retained in the history phase.

    This attribute MUST be supported if the "job-history-attributes-s= upported" (section N.M.P) attribute is supported.


    job-history-attributes-supported (1setOf keyword)

    This Printer Description attribute lists the Job attributes that can b= e retained in the history phase of each Job.

    This attribute MUST be supported if the "job-history-attributes-c= onfigured" (section N.M.P) attribute is supported.


    On Mar 7, 2019, at 12:06 PM, Michael Sweet <msweet@apple.com> wrote:

    All,

    For your consideration, the following two Printer Description attributes wo= uld allow a Client to discover (and potentially the administrator to config= ure since the values are settable) how long a Job will stay in the history = phase.

    (I also considered "job-history-xxx" and "job-history-time-x= xx" for the names; "interval" seemed the most consistent wit= h other existing attributes, particularly with notifications)

    --------

    job-history-interval-configured (integer(0:MAX))

    This Printer Description attribute specifies the minimum number of seconds = that a Job will remain in the history phase of its lifecycle [STD92]. Print= ers SHOULD have a default configured value of at least 60 seconds to allow = Clients to discover the disposition of any Jobs that have reached a terminating state.

    This attribute MUST be supported if the "job-history-interval-supporte= d" (section N.M.P) attribute is supported.


    job-history-interval-supported (rangeOfInteger(0:MAX))

    This Printer Description attribute specifies the range of values that are s= upported for the "job-history-interval-configured" Printer Descri= ption attribute.

    This attribute MUST be supported if the "job-history-interval-configur= ed" (section N.M.P) attribute is supported.


    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer


    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    ______________= _________________________________
    ipp mailing list
    ipp@pwg.org
    http= s://protect-us.mimecast.com/s/fxgUCmZ6o6hYpnWWIGXtnT?domain=3Dpwg.org

    --_000_BN7PR17MB224207166BA374964B6D43F9A44C0BN7PR17MB2242namp_-- --===============8649174146848380214== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8649174146848380214==-- From ipp-bounces@pwg.org Thu Mar 7 09:51:47 2019 Return-Path: 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 7BEE612787D for ; Thu, 7 Mar 2019 09:51:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 noYT86KLB0yI for ; Thu, 7 Mar 2019 09:51:45 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 45D41124BA8 for ; Thu, 7 Mar 2019 09:51:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id ED3B93F9C; Thu, 7 Mar 2019 17:51:44 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id CD87526AA; Thu, 7 Mar 2019 17:51:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id D7D9E3F46; Thu, 7 Mar 2019 17:51:39 +0000 (UTC) Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) by www.pwg.org (Postfix) with ESMTPS id 6586E24D3 for ; Thu, 7 Mar 2019 17:51:39 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27HpWkO037622 for ; Thu, 7 Mar 2019 09:51:39 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=P01C8uXAyVQzCTrg/UGLZO/ZE7j6xFnpJy0N4cJ8+NA=; b=D34O+EQdSHbUIsKNq+Ka1Yt9778cme94rjXexLS9c4gxUToJChR4Tg5wIzcNhvNRGuj+ iFZBjHJNfy/rlAm0myNUnj/5GkVfdIi6u9bC8HcvltP5GTSbfG/yxM+x9ZK4AMj2LWK5 9wI2UqpsflFkOvcImeQ6m0nVHEO+lMxfJPjP6V+wfnxBG9JnxOMGkMjjXxUJl1dsSUqy Kwxp1oOHpvGwYWTUzkuaUXuqRwwPew4SEE3Dluzg3uYikDf8Rij7RMKXIqEHzQlyIjFD 8+yknmfGIfUybV+N1YQV+IZM8QtTvxfLOSnwjWsTxjkqSQ1eXsBl01pzx5JYxPZBBTJm zw== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2r0ac464tk-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 07 Mar 2019 09:51:39 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO000DISCA1WM80@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Thu, 07 Mar 2019 09:51:37 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000M00BRCJG00@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:51:37 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: fe24999f18162aa28929e2164f0cb9d5 X-Va-R-CD: d9eb1effa02e4af84378c0595c7d08ac X-Va-CD: 0 X-Va-ID: 8db87277-cbcb-40ea-98c7-583745e1fbab X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: fe24999f18162aa28929e2164f0cb9d5 X-V-R-CD: d9eb1effa02e4af84378c0595c7d08ac X-V-CD: 0 X-V-ID: b23750b8-45dd-46c0-aa80-86e6793cfac6 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_09:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO0009AFC9XZJ00@nwk-mmpp-sz12.apple.com>; Thu, 07 Mar 2019 09:51:36 -0800 (PST) Date: Thu, 07 Mar 2019 12:51:33 -0500 Message-id: <8437B20E-AABA-43D2-B0CD-5166E1B48AA3@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_09:, , signatures=0 Subject: [IPP] RFC: IPP Job Extensions v1.1 or v2.0? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I mentioned this in a previous thread, but wanted to bring this up in a new thread to discuss separately. We are in the process of updating PWG 5100.7-2003: IPP Job Extensions (JOBEXT), and based on previous discussions have decided to incorporate parts of PWG 5100.11-2010: IPP Job and Printer Extensions - Set 2 (JPS2) that have more general usefulness, with the remaining enterprise functionality going into a new IPP Enterprise Printing Extensions specification to replace 5100.11 (which will be obsoleted, like we did for the original overrides spec many years ago). Many of the attributes coming from 5100.11 are OPTIONAL, so adding them to Job Extensions v1.1 poses no problem for our defined standards errata process - no change in conformance for the original 5100.7 so the 5100.7-2019 update will be backwards-compatible with any implementation conformaing to 5100.7-2003. However, JPS2 also defines four new REQUIRED operations and a REQUIRED operation attribute (job-ids). Keeping these in a 5100.11 errata update would pose no problem, but PWG Process/3.0 says nothing about cross-spec errata updates. Using a conservative interpretation of the approved process, we would need to change the major version number of the Job Extensions specification to increase the conformance requirements, and then use the "long" process (verification of prototyping, PWG Last Call, and PWG Formal Vote) instead of the "short" process (PWG Call for Objections). An alternative is to make these operations RECOMMENDED and job-ids conditionally required - then there is no conformance increase and we can use the short process for an errata update. Since IPP Everywhere already makes most of these operations REQUIRED already, the practical reality is that they will be required attributes. Thoughts? _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Mar 7 13:43:18 2019 Return-Path: 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 BEB121311A7 for ; Thu, 7 Mar 2019 13:43:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 kszp6VG3WS4N for ; Thu, 7 Mar 2019 13:43:16 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 261321311A6 for ; Thu, 7 Mar 2019 13:43:16 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 8DA8C24D3; Thu, 7 Mar 2019 21:43:15 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id C209F26AA; Thu, 7 Mar 2019 21:43:08 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B3CC53F45; Thu, 7 Mar 2019 21:43:07 +0000 (UTC) Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) by www.pwg.org (Postfix) with ESMTPS id 8E6BE24D3 for ; Thu, 7 Mar 2019 21:43:06 +0000 (UTC) Received: by mail-yw1-xc2e.google.com with SMTP id z191so14637869ywa.6 for ; Thu, 07 Mar 2019 13:43:06 -0800 (PST) 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=9k4Q5KqRdKQk+LthCoAncHyghAssajY8Ry7rGwyEetM=; b=d5ZKu11oRXLEHxrdMxYjXwE1wLCJ1SKrKX/Z1lHVm1Bm7/fL83b6wPZAKUv/cff/N5 9xdGagUh2zUclUBhufUWvQoVOtRXQqHF6AXvOV4S/WHV/DC4RYo9Q2znyz1qTcRU5N6u FxgK8lx97GUtx25B99u3bO7fQIOx8W92DuFCTQvbF+PXyF0eUeBNoJ2z5FiKCjn+XeZg GXdThzVoaFOMxqQu3Ehpi4Z2rpWhCQcCSdHsuQqcdtawnT/QfjxL3I0IgVtXKz21XiiG hftJIRv2D55LuBuTmLPO0maUKZMgIpkWMlA+v4tu7amtgJfEHjuqXkI4RdH0B6deVHNf 1h1w== 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=9k4Q5KqRdKQk+LthCoAncHyghAssajY8Ry7rGwyEetM=; b=DhhdrF/XXgt9eMqk4EV0/MPxpe+kV6p/07KgUZKBhRJpEFebXxYxBQbtwegHFCq94Z GSM4KKOS2jh+aXCO/2cbePY3fptt+oFbmdZ8NE8Xw1n8h8KiXNPnye0l4uPvYxe2WRzI GoVnl2uiwlChonWdX/1SrDVE22ctz/kpXYPKt/eDsWkV1/zXMm4YDsoRJht+x0ZYOYeu Hyw9OhSW8YuWXFjObgbcEzStVdvCvErqRycU2o7DUKMLr4dgOy+yyNV/Xd4JfTTiyaWF p9fK7PW7TBghM+pUGhSiipQ3972zWjxULO19lwG+3mBvFwWKDsey72tirAew5UsSukM3 a2ug== X-Gm-Message-State: APjAAAVS7uIpDe7myhW4thljsDsUObARHD9KqCWGHJAp/Jjcc5ah2E3N 4COpW2rP3KolVrwodpzkWiC67Cu3HUDIxkAwmLA= X-Google-Smtp-Source: APXvYqxdbvgRX1FNXBP80pZUfAaMj87E8BvG0P6xYph3PoMB+Gw6KPBqBXvmsGnXUtBVPFCSxzlawwG4sRoikqmBFd0= X-Received: by 2002:a25:f810:: with SMTP id u16mr13531447ybd.290.1551994985731; Thu, 07 Mar 2019 13:43:05 -0800 (PST) MIME-Version: 1.0 References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> In-Reply-To: Date: Thu, 7 Mar 2019 16:42:52 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============0101144822553527924==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0101144822553527924== Content-Type: multipart/alternative; boundary="000000000000d15af9058387fd9d" --000000000000d15af9058387fd9d Content-Type: text/plain; charset="UTF-8" Hi Mike, Even in a minor errata version, I thought we could add a RECOMMENDED (SHOULD) attribute, because it doesn't break backward compatibility? Shouldn't the retention and job history attributes (and probably others) be RECOMMENDED in Job Extensions? I shudder at perpetuating IPP specs that are a basket of OPTIONAL attributes. That doesn't help interoperability particularly. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 11:58 AM Michael Sweet wrote: > Well, if we put job-retain-until in Job Extensions 1.1, then we should > probably put job-delay-output-until in JOBEXT as well (since now we'll have > a bunch of Job Template attributes in JOBEXT that control scheduling/job > lifecycle decisions) > > Just remember that in JOBEXT all of this will be OPTIONAL anyways. > > I will also post a RFC for another attribute to close the last lifecycle > hole (how long a job stays in history). > > > On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp wrote: > > Hi, > > I just read this entire thread carefully. > > I agree with all of your joint conclusions (good work Smith and Mike), > *except* for "job-retain-until-xxx". > > I consider the lack of "job-retain-until-xxx" an architectural mistake > in IPP/1.1. So I'd like it to be present in Job Extensions, so that > some version lower than IPP/2.2 (Enterprise) can reliably use it. > I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED > in IPP/2.1 and above. > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp wrote: > >> Smith, >> >> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards >> Architect) via ipp wrote: >> ... >> >> Also, I don't think we want a job-retain-until-time-default, since the >> value is an absolute dateTime value (unless we make -time an integer and >> add a -date version for dateTime?) >> >> >> Hmmm, how about just having "job-retain-until" (type2 keyword) and >> "job-retain-until-time" (integer) and not bother with >> "job-retain-until-date" (dateTime)? >> >> >> Let's discuss this at the next concall - I can see a use for both (retain >> the job for 24 hours, retain the job until the next scheduled update), and >> a Client can calculate the number of seconds to a specific date/time, but >> there are still some vagaries due to submission delays and whether the IPP >> job ticket is used directly and immediately or if it gets "relayed" to the >> destination output device that is doing the retaining... >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > --000000000000d15af9058387fd9d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    Even in a minor err= ata version, I thought we could add a RECOMMENDED
    (SHOULD) attrib= ute, because it doesn't break backward compatibility?

    Shouldn't the retention and job history attributes (and probabl= y others) be
    RECOMMENDED in Job Extensions?

    <= div>I shudder at perpetuating IPP specs that are a basket of OPTIONAL
    =
    attributes.=C2=A0 That doesn't help interoperability particularly.=

    Cheers,
    - Ira

    =
    <= div dir=3D"ltr">Ira McDonald (Musician / Software Architect)
    Co-Chair - = TCG Trusted Mobility Solutions WG
    Co-Chair - TCG Metadata Access = Protocol SG
    Chair - Linux Foundation Open Printin= g WG
    Secretary - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO= PWG Internet Printing Protocol WG
    IETF Designated Expert - IPP & Pr= inter MIB
    Blue Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434



    On Thu, Mar 7= , 2019 at 11:58 AM Michael Sweet <ms= weet@apple.com> wrote:
    Well, if we put job= -retain-until in Job Extensions 1.1, then we should probably put job-delay-= output-until in JOBEXT as well (since now we'll have a bunch of Job Tem= plate attributes in JOBEXT that control scheduling/job lifecycle decisions)=

    Just remember that in JOBEXT all of this will be OPTION= AL anyways.

    I will also post a RFC for another att= ribute to close the last lifecycle hole (how long a job stays in history).<= /div>


    On Mar 6, = 2019, at 4:50 PM, Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi,

    I just read this entire thread carefully.
    <= br>
    I agree with all of your joint conclusions (good work Smith a= nd Mike),
    *except* for "job-retain-until-xxx".

    I consider the lack of "job-retain-until-xxx" an= architectural mistake
    in IPP/1.1.=C2=A0 So I'd like it to be= present in Job Extensions, so that
    some version lower than IPP/2= .2 (Enterprise) can reliably use it.
    I suggest making it RECOMMEN= DED in IPP/2.0 and REQUIRED
    in IPP/2.1 and above.

    <= /div>
    Cheers,
    - Ira

    Ira McDo= nald (Musician / Software Architect)
    Co-Chair - TCG Trusted Mobility Sol= utions 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 P= rotocol WG
    IETF Designated Expert - IPP & Printer MIB
    Blue Roof M= usic / High North Inc
    http://sites.google.c= om/site/blueroofmusic
    http://sites.googl= e.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Gr= and Marais, MI 49839=C2=A0 906-494-2434

    <= /div>


    =
    On Wed, Mar 6, 2019 at 4:03 PM Michae= l Sweet via ipp <ipp@pw= g.org> wrote:
    Smith,

    On Mar 6, 2019,= at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp &l= t;ipp@pwg.org> wrot= e:
    ...
    =C2=A0Also, I don't think we want a job= -retain-until-time-default, since the value is an absolute dateTime value (= unless we make -time an integer and add a -date version for dateTime?)

    Hmmm, how about just having "job-= retain-until" (type2 keyword) and "job-retain-until-time" (i= nteger) and not bother with "job-retain-until-date" (dateTime)?

    Let's discuss this at the n= ext concall - I can see a use for both (retain the job for 24 hours, retain= the job until the next scheduled update), and a Client can calculate the n= umber of seconds to a specific date/time, but there are still some vagaries= due to submission delays and whether the IPP job ticket is used directly a= nd immediately or if it gets "relayed" to the destination output = device that is doing the retaining...

    _________________________________________________________
    Mic= hael Sweet, Senior Printing System=C2=A0Engineer

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

    _________________________________________________________
    Michae= l Sweet, Senior Printing System=C2=A0Engineer

    --000000000000d15af9058387fd9d-- --===============0101144822553527924== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0101144822553527924==-- From ipp-bounces@pwg.org Thu Mar 7 13:45:38 2019 Return-Path: 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 7B7421311CB for ; Thu, 7 Mar 2019 13:45:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 zuCOpnO865qu for ; Thu, 7 Mar 2019 13:45:36 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 74FFC1311A7 for ; Thu, 7 Mar 2019 13:45:36 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 328B03F4D; Thu, 7 Mar 2019 21:45:36 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id F1C5B24D3; Thu, 7 Mar 2019 21:45:30 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 172DB3F45; Thu, 7 Mar 2019 21:45:29 +0000 (UTC) Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) by www.pwg.org (Postfix) with ESMTPS id 39D9E24D3 for ; Thu, 7 Mar 2019 21:45:28 +0000 (UTC) Received: by mail-yw1-xc31.google.com with SMTP id s204so14650131ywg.2 for ; Thu, 07 Mar 2019 13:45:28 -0800 (PST) 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=eCWXPHdVSi8vxtNXtBQdQLEJAVRPnXgZ6g0DthHEM4E=; b=pujFsZ7/PlWF3SU60hvlVSxtrCPAK3ymjeDuUyRsPRDocpjnX0YXi/opZo8Esu0aaC 1f8w/KeOYeLtV2dXk65a8l809roqgo1iSqB68DhnaNPV3IGgnnEQcBaKe1c+OWBcQHke phOJg+vcgeO7ohPjFYlGVabB9jBrz1aBD87g4z/gJ50UjF9WRrjQd/Pdr2okhR5WWIs8 Klb7bAyYbvb7eU8aMRjaHI8M8GxeQ140hTGJAwdwLCW590Ne4EwtYbRFMA1A41dMaI8C OP/7KPnk3yXHUPB8JaBzGG6oWMd3L5qbT7ROTIc+2sX7LviEwFFZU7A33JOSV+fayWxU s+DA== 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=eCWXPHdVSi8vxtNXtBQdQLEJAVRPnXgZ6g0DthHEM4E=; b=p73TZFLXf8SYMX/SQd7qIKRDVtUBN1h13PlQhiXLmtOZhVWDrThsQeEztMiXer5v3X lUZvPvfKuXnfZ/ewS619Gig7KT8xMVSpNv/7DdJgI/9/CDeRZ7TkmkokoKVGZKzqfbvA 5xXsK3CmXXKu1M47H3xDFzaH0BK6EjHqU6ov9nKvZrr+PCtJq+HjpkVPHJSb+zVtSeDG 7CeMHuzQY1xdL35r/55pSqx9V7OUmy1NgFV6NGwKlzagCDyamwCl/57ncO1yJuEM/X8C YVyH6pRsAkGFpO3f/SOkmMR4Ug5GIko344f3noXw48eZ0+SOMjNOdhwnV29K0hG3o6VQ rHCA== X-Gm-Message-State: APjAAAVaNR+kfkOigBjML5Lez8lRKTtZzice0P8/d8b9Z5yKL6dm6kJ4 +BJ5cMIQnf/D3Qjmsf57By/RafXhSTVj6/jagm7ERw== X-Google-Smtp-Source: APXvYqyj0uKKuhXAxWl7vGPGaYEwOnZXokYmgxXGL52T3X4WIAxe353oZts/rUFlNtpuxLrMOGkWrpzGL4WN/JeVVuI= X-Received: by 2002:a81:3808:: with SMTP id f8mr379749ywa.227.1551995127574; Thu, 07 Mar 2019 13:45:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 7 Mar 2019 16:45:12 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: DEPRECATED and OBSOLETED definitions X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============4980023760213039832==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4980023760213039832== Content-Type: multipart/alternative; boundary="00000000000045b749058388064a" --00000000000045b749058388064a Content-Type: text/plain; charset="UTF-8" Hi Mike, +1. Except that we want to be able to (and have already) marked *operations* (and not just attributes) as DEPRECATED. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Mar 6, 2019 at 2:27 PM Michael Sweet via ipp wrote: > All, > > Here is my proposed text for deprecations and obsoletions in the > conformance section of new IPP specifications: > > The term DEPRECATED is used for previously defined and approved > items that SHOULD NOT be used or implemented. The term OBSOLETED is used > for previously defined and approved items that MUST NOT be used or > implemented. > > > Thoughts? > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --00000000000045b749058388064a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    +1.=C2=A0

    Except that we want to be able to (and have already) m= arked *operations*
    (and not just attributes) as DEPRECATED.
    =

    Cheers,
    - Ira

    <= div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature= ">
    Ira McDonald (Musician / Software Architect)
    Co-Chair - TCG Tr= usted Mobility Solutions WG
    Co-Chair - TCG Metadata Access Protoc= ol SG
    Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PWG I= nternet Printing Protocol WG
    IETF Designated Expert - IPP & Printer = MIB
    Blue Roof Music / High North Inc
    htt= p://sites.google.com/site/blueroofmusic
    = http://sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    P= O Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434



    On Wed, Mar 6, 2019= at 2:27 PM Michael Sweet via ipp <ipp@pw= g.org> wrote:
    All,

    Here= is my proposed text for deprecations and obsoletions in the conformance se= ction of new IPP specifications:

    The term DEPREC= ATED is used for previously defined and approved items=C2=A0that=C2=A0SHOUL= D NOT be used or=C2=A0implemented.=C2=A0The term OBSOLETED is used for prev= iously=C2=A0defined and approved items that MUST NOT be=C2=A0used or implem= ented.

    Thoughts?

    _= ________________________________________________________
    Michael Sweet, = Senior Printing System Engineer

    __________________= _____________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --00000000000045b749058388064a-- --===============4980023760213039832== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4980023760213039832==-- From ipp-bounces@pwg.org Thu Mar 7 13:47:33 2019 Return-Path: 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 A15C81311B0 for ; Thu, 7 Mar 2019 13:47:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 OoxmBcVD5xJX for ; Thu, 7 Mar 2019 13:47:32 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id EF0B91311A7 for ; Thu, 7 Mar 2019 13:47:31 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id A9A7C3F4D; Thu, 7 Mar 2019 21:47:31 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 498F326AA; Thu, 7 Mar 2019 21:47:24 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 0C6303F45; Thu, 7 Mar 2019 21:47:22 +0000 (UTC) Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) by www.pwg.org (Postfix) with ESMTPS id 010F7269F for ; Thu, 7 Mar 2019 21:47:21 +0000 (UTC) Received: by mail-yw1-xc30.google.com with SMTP id v201so14643867ywa.9 for ; Thu, 07 Mar 2019 13:47:20 -0800 (PST) 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=ZKbXJtsXj7VPx0tHYx+yyNxykWJkjZtTqtGHmhvE7dA=; b=Nh2jsn7QRk4xP2B/sumdeo+aSSepVkt4cL12q/ESqNhZ+yQARKPSVpRD/bZpRdWEK7 rI3nadb9dSFnXb8gP0/CYdF2hfi9tVJyWav+M7SS6AOb35eVOQ6mR/6i9iZRu6YUIH9a 4rglz12IbHCebG18sz+D8sC55HHGPGqXv1T4cA5QorsCXRKJM4O57TvrPfsMtQvUjPmT Yfk1MspEn+u4ISyc8Iu/vI3gMAq1i2+GXukJvwKYONVA2m8wNvgJsI204XVQy9ftlJph FeSKEHNhlz1y/xE2FvD2+i880bx3TssZdOo1NocfYQNzYNAgULiC7828gTWyQrrGe1oN JU4w== 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=ZKbXJtsXj7VPx0tHYx+yyNxykWJkjZtTqtGHmhvE7dA=; b=QAuGPVLSbsNRXt8+u+c9kZNQE33E554i8DweRW0StI9tazWHT8Of6SYvuXvOZUuNjA fdynCaJ2nP1StLRGGof+c3vGx1ODGeRpQ28Nv48XTHHGEkEdUZt06qgUwQIDpkx+U1ho 4f9PJKX4OVgLw0Xl6Qrc2HI1NeX8dvoMr9Fo48ZQVnfDvKoJNlNp3vK4QP1mFuNXVcdn 2g2xsjAK7rw/67HVYSEEqAoFhODty2stNEENacd0dW0qJFot0AKXht+LBhQfyQRRURac ctk2VEzEDm7LPe4fiAy3QzvVyS/jcs3c7ZswxZKcOnHZwGFuVmTej53BfD80hlLWqaxG RjzQ== X-Gm-Message-State: APjAAAVbWf8GIZplotoEqqnU+Muic1XJs7LIyQzVF9a0UZp1B065dZpX f10ktzcYwp8zbnSNI2K7AMlKf/+tgDslRMWNalEAyw== X-Google-Smtp-Source: APXvYqzOOCBbcqqwT0BihR9JrxZyoLt6FlL37vb2x+0HffDUhHgavbiSOJbg6ExRvMp/YkjVykFVgteubM+/gGQ/lJA= X-Received: by 2002:a25:2605:: with SMTP id m5mr13255418ybm.194.1551995240285; Thu, 07 Mar 2019 13:47:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 7 Mar 2019 16:47:07 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: DEPRECATED and OBSOLETED definitions X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6077496236963532248==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6077496236963532248== Content-Type: multipart/alternative; boundary="000000000000fd89900583880c96" --000000000000fd89900583880c96 Content-Type: text/plain; charset="UTF-8" Hi, That last may have been a dumb response. But I don't like the term "items". Should we enumerate operations, features, attributes, and values? 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 4:45 PM Ira McDonald wrote: > Hi Mike, > > +1. > > Except that we want to be able to (and have already) marked *operations* > (and not just attributes) as DEPRECATED. > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Wed, Mar 6, 2019 at 2:27 PM Michael Sweet via ipp wrote: > >> All, >> >> Here is my proposed text for deprecations and obsoletions in the >> conformance section of new IPP specifications: >> >> The term DEPRECATED is used for previously defined and approved >> items that SHOULD NOT be used or implemented. The term OBSOLETED is used >> for previously defined and approved items that MUST NOT be used or >> implemented. >> >> >> Thoughts? >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> > --000000000000fd89900583880c96 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    That last may have been = a dumb response.

    But I don't like the term &qu= ot;items".=C2=A0 Should we enumerate operations, features,
    <= div>attributes, and values?

    Cheers,
    - Ir= a

    <= div>
    Ira McDonald (Musician / Softwar= e Architect)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-C= hair - TCG Metadata Access Protocol SG
    Chair - Li= nux Foundation Open Printing WG
    Secretary - IEEE-ISTO Printer Working Gr= oup
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Desig= nated Expert - IPP & Printer MIB
    Blue Roof Music / High North Inchttp://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc<= /a>
    mailto:     blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2= =A0 906-494-2434

    <= /div>

    On Thu, Mar 7, 2019 at 4:45 PM Ira McDonald <blueroofmusic@gmail.com> wrote:
    <= /div>
    Hi Mike,

    +1.=C2=A0

    Except that we want to be able to (and have already) marked *operations*
    (and not just attributes) as DEPRECATED.

    = Cheers,
    - Ira

    Ira McDonald (Musi= cian / Software Architect)
    Co-Chair - TCG Trusted Mobility Solutions WG<= /div>
    Co-Chair - TCG Metadata Access Protocol SG
    Chair - Linux Foundation Open Printing WG
    Secretary - IEEE-ISTO Prin= ter Working Group
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG=
    IETF Designated Expert - IPP & Printer MIB
    Blue Roof Music / Hig= h North Inc
    http://sites.google.com/site/bl= ueroofmusic
    http://sites.google.com/site= /highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais= , MI 49839=C2=A0 906-494-2434

    =
    =


    On Wed, Mar 6, 2019 at 2:27 PM Michael Sweet = via ipp <ipp@pwg.org> wrote:
    All,

    Here is my proposed text for deprecations and obs= oletions in the conformance section of new IPP specifications:
    The term DEPRECATED is used for previously defined and appro= ved items=C2=A0that=C2=A0SHOULD NOT be used or=C2=A0implemented.=C2=A0The t= erm OBSOLETED is used for previously=C2=A0defined and approved items that M= UST NOT be=C2=A0used or implemented.

    = Thoughts?

    ______________________________________________= ___________
    Michael Sweet, Senior Printing System Engineer

    =
    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --000000000000fd89900583880c96-- --===============6077496236963532248== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6077496236963532248==-- From ipp-bounces@pwg.org Thu Mar 7 13:50:54 2019 Return-Path: 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 A0E381311B6 for ; Thu, 7 Mar 2019 13:50:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 qHbkMJ1lkX0M for ; Thu, 7 Mar 2019 13:50:52 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAA71311B0 for ; Thu, 7 Mar 2019 13:50:52 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 1A559269F; Thu, 7 Mar 2019 21:50:52 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id ADCFE26AA; Thu, 7 Mar 2019 21:50:48 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 2AA3A3F45; Thu, 7 Mar 2019 21:50:48 +0000 (UTC) Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) by www.pwg.org (Postfix) with ESMTPS id A7E9024D3 for ; Thu, 7 Mar 2019 21:50:47 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27LlXtI022277; Thu, 7 Mar 2019 13:50:46 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=yIfdk/hEvtYh2iSeUt7j+W4q50q3jz3bFpabJdM651E=; b=RIjmyjodwaWrgJpAARcZXbxF0FyBezoNNwAgTTOs8GvVmANAYzuBFXMWV+2vdgB7xa3T wZvQ7c9Sox3bPNWhoSCqyNzYC6G+o0ESlmHLdeqe895N8S65oyp8MVIAjD33ZdUGO/aa LpHXU1LFLl9DQisP31KkflyFtt3dhqrJMvk9WFE8hojrop7vIy9DG/l8kLzLLsmw3Idz nHaHpAYl2WxkaDcxB+75mFL23z0KmrjnKpB7wtto+bmFABj3u+FsUefuWtU3G9i+A9iq wZzVhxfoTkf/JmaTzV/Rs8+L+tptlhbgzlUTS1UB1Uw/ZR8CsQRWjtMy5CwrmxmlTU/Z cA== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2qysn9grgw-13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 07 Mar 2019 13:50:46 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO000G9GNCHOA60@ma1-mtap-s03.corp.apple.com>; Thu, 07 Mar 2019 13:50:44 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000L00N3MGF00@nwk-mmpp-sz13.apple.com>; Thu, 07 Mar 2019 13:50:44 -0800 (PST) X-Va-A: X-Va-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-Va-E-CD: 859288fb2452c01c047889677ad50330 X-Va-R-CD: dc509dfe50ef767f6802432139379487 X-Va-CD: 0 X-Va-ID: c675747b-03b0-4375-a246-eb65112298b4 X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: 859288fb2452c01c047889677ad50330 X-V-R-CD: dc509dfe50ef767f6802432139379487 X-V-CD: 0 X-V-ID: b298bb85-41ea-421e-8763-6f6fc3150dd5 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_13:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO000K8INCH9B60@nwk-mmpp-sz13.apple.com>; Thu, 07 Mar 2019 13:50:43 -0800 (PST) In-reply-to: Date: Thu, 07 Mar 2019 16:50:41 -0500 Message-id: References: To: Ira McDonald X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: DEPRECATED and OBSOLETED definitions X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============2422957132255232928==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2422957132255232928== Content-type: multipart/alternative; boundary="Boundary_(ID_6iBBXTqGFt47cUM7Ty8oZg)" --Boundary_(ID_6iBBXTqGFt47cUM7Ty8oZg) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Ira, > On Mar 7, 2019, at 4:47 PM, Ira McDonald via ipp wrote: > > Hi, > > That last may have been a dumb response. > > But I don't like the term "items". Should we enumerate operations, features, > attributes, and values? I originally enumerated things (like we do in the IPP registry process document), which is "operations, attributes, attribute syntaxes, values, and status codes", but that seemed like too much so I opted to shorten things to "items" since it covers any usage. _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_6iBBXTqGFt47cUM7Ty8oZg) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Ira,


    On Mar = 7, 2019, at 4:47 PM, Ira McDonald via ipp <ipp@pwg.org> = wrote:

    Hi,

    That last may have been a dumb = response.

    But = I don't like the term "items".  Should we enumerate operations, = features,
    attributes, and = values?

    I = originally enumerated things (like we do in the IPP registry process = document), which is "operations, attributes, attribute syntaxes, values, = and status codes", but that seemed like too much so I opted to shorten = things to "items" since it covers any usage.

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_6iBBXTqGFt47cUM7Ty8oZg)-- --===============2422957132255232928== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2422957132255232928==-- From ipp-bounces@pwg.org Thu Mar 7 13:53:11 2019 Return-Path: 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 B2BCF130F84 for ; Thu, 7 Mar 2019 13:53:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 ubwZhFZb7vRO for ; Thu, 7 Mar 2019 13:53:10 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 318BF130DC8 for ; Thu, 7 Mar 2019 13:53:10 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 0DED23F47; Thu, 7 Mar 2019 21:53:09 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id B9E4826AA; Thu, 7 Mar 2019 21:53:04 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 64F123F45; Thu, 7 Mar 2019 21:53:03 +0000 (UTC) Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) by www.pwg.org (Postfix) with ESMTPS id 77CA7269F for ; Thu, 7 Mar 2019 21:53:02 +0000 (UTC) Received: by mail-yw1-xc2a.google.com with SMTP id n12so14644900ywn.13 for ; Thu, 07 Mar 2019 13:53:02 -0800 (PST) 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=2zuo+MJjzi00pY95bcmvrgIyhAKg/nyKZdd1KxreqyQ=; b=qsM5oDGKa5rqq1Iz0+Oc1rl1HOsPG+KPpn4eAVeeFXGLVktDXEQ0BkziZbo6c9j2Ij vRltevwsKvh4CXV11LdRzW2V5yObN6i3shKUcAnwBVZDQhlzdesV/2F6CVFHdFAji+lJ Ctcg51oVfjph9sWQLIC/bDRWuvuD8PlypjZP3rtWWVnQ3cMFk5U3OsxnlbhmWAihbljB DZeBevVUQ2042HUORMn5iQ44WHwz9CFookAm3MG+zjvwCWduevXSAjh9D7uPIUiioIcN agVVoZIkNGJKS8FgMjWWoxSZjbunBK3mAvJF8YYezHm7ijdNDAcExtgY90wiMi5o83bU dxMg== 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=2zuo+MJjzi00pY95bcmvrgIyhAKg/nyKZdd1KxreqyQ=; b=ZvCgUNGNV8dw8MdbOxnwIjF3tiC2Hc6DSrYkanIH95upmjGXqpN3/JHomeC06TqpVp e2pN5xkEP//glQfWcr2QJBn4IDiQuedOkOvgvED7jLjjCAqasEmCQNEvvevWF+hLTRtb 9HMZIeiPTzCd/J2UYPYDxnHD5BNIcaa9267tQrIy2KE5cmWYz+TnzxSjy1gf5N1Nuazx i80bslHEEaHjmp7kmwie3h4F0DIXrC3YndpEL3RfiUoNwnfuSkJmpStu55wxlXvRY96b eNNi+CkI4Hh94oJJi/KduuX4U3MSoBzLLBL4d4ZEdUVrhXgF0ETWwTzzBo+AhRudxo6L dOMg== X-Gm-Message-State: APjAAAWlGTqHEvxIpx8Q93FHaJasin45qCw2dNhQkwTUlJT79zk21Yj/ qfMU3dvI8jEM6qoHAnU1HkJFoWnDJUhrYA57sqs= X-Google-Smtp-Source: APXvYqx7tSI3frWxwFSwqjJee+nx5ili+sfMC+eYERl9StmOjFnCeZO5Y86BfPbk1bGxzrDxVOl4QntG9nHsyW/cc7w= X-Received: by 2002:a81:6841:: with SMTP id d62mr12097012ywc.507.1551995581638; Thu, 07 Mar 2019 13:53:01 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 7 Mar 2019 16:52:48 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: DEPRECATED and OBSOLETED definitions X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============4053195882081494860==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4053195882081494860== Content-Type: multipart/alternative; boundary="000000000000562a610583882182" --000000000000562a610583882182 Content-Type: text/plain; charset="UTF-8" Hi Mike, In ITU-T specs, I've seen "protocol elements" used to avoid ultimately vague words like "items" (which sounds like the stock of a convenience store...). 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 4:50 PM Michael Sweet wrote: > Ira, > > > On Mar 7, 2019, at 4:47 PM, Ira McDonald via ipp wrote: > > Hi, > > That last may have been a dumb response. > > But I don't like the term "items". Should we enumerate operations, > features, > attributes, and values? > > > I originally enumerated things (like we do in the IPP registry process > document), which is "operations, attributes, attribute syntaxes, values, > and status codes", but that seemed like too much so I opted to shorten > things to "items" since it covers any usage. > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > --000000000000562a610583882182 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    In ITU-T specs, I&#= 39;ve seen "protocol elements" used to avoid ultimately vague
    words like "items" (which sounds like the stock of a conve= nience store...).

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architec= t)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TCG= Metadata Access Protocol SG
    Chair - Linux Founda= tion Open Printing WG
    Secretary - IEEE-ISTO Printer Working Group
    Co-= Chair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Designated Expe= rt - IPP & Printer MIB
    Blue Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    ma= ilto: blueroof= music@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-49= 4-2434

    <= /div>

    <= /div>

    On Thu, Mar 7, 2019 at 4:50 PM Michael Sweet <msweet@apple.com> wrote:
    = Ira,


    On Mar 7, 2019, at 4:4= 7 PM, Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi,

    <= /div>
    That last may have been a dumb response.

    But I don't like the term "items".=C2=A0 Should we enumerate= operations, features,
    attributes, and values?

    I originally enumerated things (like we do = in the IPP registry process document), which is "operations, attribute= s, attribute syntaxes, values, and status codes", but that seemed like= too much so I opted to shorten things to "items" since it covers= any usage.

    _________________________________________________________
    Michae= l Sweet, Senior Printing System=C2=A0Engineer

    --000000000000562a610583882182-- --===============4053195882081494860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4053195882081494860==-- From ipp-bounces@pwg.org Thu Mar 7 13:55:29 2019 Return-Path: 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 E018E130F84 for ; Thu, 7 Mar 2019 13:55:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.271 X-Spam-Level: X-Spam-Status: No, score=-2.271 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.428, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 7YzyK84YuS98 for ; Thu, 7 Mar 2019 13:55:27 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 787CA1311A7 for ; Thu, 7 Mar 2019 13:55:27 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 42C9F3F4C; Thu, 7 Mar 2019 21:55:27 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1E2E326AA; Thu, 7 Mar 2019 21:55:20 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id EE5013F45; Thu, 7 Mar 2019 21:55:18 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id D398F269F for ; Thu, 7 Mar 2019 21:55:17 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x27Lq9qv048782; Thu, 7 Mar 2019 13:55:16 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=q/EmVGE2421qhUVJFyA640AVZt2S+s/v6YOR+qMpTLE=; b=sVVrWkDXEm64uV4pVVixIEWpmFZsqLPNygp5LjgOHhwOaIFoR302f+9bKg7pUA6fxKiG TFym2sX1vz6LLP3Kz0gU/wRJB6ismOWUHC7ny9REvykeov4DcIQ563zO0bLvqCXPksQm KDCGJRGZhuCbXl6Np+iofdmYnwOHUEOvPH2kAA7228MKkBkB11lsuc24SCoS/qjYuWdM 3BTqqe0SzQkitFCHxvzZ0R1BS4Xv+VVSufwfxZ2RUV/jS7cgh01jBdPh+HBEO9l+TfE8 wwLTD5VcGozUdeh3uJDoMwWxYa/tgKw5ebiG9BxzJD9Om2L4x3Mk9m6hbUtbtFHr04rm Qg== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2qyqd45pne-9 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 07 Mar 2019 13:55:16 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO0008AFNJY4AE0@ma1-mtap-s01.corp.apple.com>; Thu, 07 Mar 2019 13:55:13 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO000L00N3GA600@nwk-mmpp-sz13.apple.com>; Thu, 07 Mar 2019 13:55:11 -0800 (PST) X-Va-A: X-Va-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-Va-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-Va-R-CD: c5f53e861a532cef1a8e83cb2834246c X-Va-CD: 0 X-Va-ID: acfa104c-d7ef-488a-a0e1-19e9d1f0c4fd X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: 3e184dc9e4a451171a3ccc3ad32b52d5 X-V-R-CD: c5f53e861a532cef1a8e83cb2834246c X-V-CD: 0 X-V-ID: 636a7751-74d4-48a6-a792-5c2d14e987da X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-07_13:,, signatures=0 Received: from [17.235.9.19] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO0003YPNJXOR70@nwk-mmpp-sz13.apple.com>; Thu, 07 Mar 2019 13:55:11 -0800 (PST) In-reply-to: Date: Thu, 07 Mar 2019 16:55:09 -0500 Message-id: <620A7C17-1244-406E-9C08-DF54DB82987F@apple.com> References: <7C4D92D8-B6AC-4E47-B89A-99B7D6450757@apple.com> <869DA79D-43EC-4DDE-A6A6-908AAA76B2BE@hp.com> <5754ED4D-FDAE-4CAC-92EA-90261F9FF811@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-07_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] What to remove from latest JPS2v2 draft to create first draft of "IPP Enterprise Printing Extensions"? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============5337674583477487020==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5337674583477487020== Content-type: multipart/alternative; boundary="Boundary_(ID_BfCq4/cpKyp4UBR+7SlFkA)" --Boundary_(ID_BfCq4/cpKyp4UBR+7SlFkA) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Ira, Yes, RECOMMENDED/SHOULD is OK, and I am making most of the attributes RECOMMENDED anyways. I think the real question is whether we make the JOBEXT update a 1.1 or 2.0? (see my other message...) > On Mar 7, 2019, at 4:42 PM, Ira McDonald wrote: > > Hi Mike, > > Even in a minor errata version, I thought we could add a RECOMMENDED > (SHOULD) attribute, because it doesn't break backward compatibility? > > Shouldn't the retention and job history attributes (and probably others) be > RECOMMENDED in Job Extensions? > > I shudder at perpetuating IPP specs that are a basket of OPTIONAL > attributes. That doesn't help interoperability particularly. > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Thu, Mar 7, 2019 at 11:58 AM Michael Sweet > wrote: > Well, if we put job-retain-until in Job Extensions 1.1, then we should probably put job-delay-output-until in JOBEXT as well (since now we'll have a bunch of Job Template attributes in JOBEXT that control scheduling/job lifecycle decisions) > > Just remember that in JOBEXT all of this will be OPTIONAL anyways. > > I will also post a RFC for another attribute to close the last lifecycle hole (how long a job stays in history). > > >> On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp > wrote: >> >> Hi, >> >> I just read this entire thread carefully. >> >> I agree with all of your joint conclusions (good work Smith and Mike), >> *except* for "job-retain-until-xxx". >> >> I consider the lack of "job-retain-until-xxx" an architectural mistake >> in IPP/1.1. So I'd like it to be present in Job Extensions, so that >> some version lower than IPP/2.2 (Enterprise) can reliably use it. >> I suggest making it RECOMMENDED in IPP/2.0 and REQUIRED >> in IPP/2.1 and above. >> >> 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/highnorthinc >> mailto: blueroofmusic@gmail.com >> PO Box 221 Grand Marais, MI 49839 906-494-2434 >> >> >> >> On Wed, Mar 6, 2019 at 4:03 PM Michael Sweet via ipp > wrote: >> Smith, >> >>> On Mar 6, 2019, at 3:41 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp > wrote: >>> ... >>>> Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?) >>> >>> Hmmm, how about just having "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) and not bother with "job-retain-until-date" (dateTime)? >> >> Let's discuss this at the next concall - I can see a use for both (retain the job for 24 hours, retain the job until the next scheduled update), and a Client can calculate the number of seconds to a specific date/time, but there are still some vagaries due to submission delays and whether the IPP job ticket is used directly and immediately or if it gets "relayed" to the destination output device that is doing the retaining... >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_BfCq4/cpKyp4UBR+7SlFkA) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Ira,

    Yes, = RECOMMENDED/SHOULD is OK, and I am making most of the attributes = RECOMMENDED anyways.

    I think the real question is whether we make the JOBEXT = update a 1.1 or 2.0?

    (see my other message...)


    On Mar 7, 2019, at 4:42 PM, Ira = McDonald <blueroofmusic@gmail.com> wrote:

    Hi Mike,

    Even in a minor errata version, I = thought we could add a RECOMMENDED
    (SHOULD) = attribute, because it doesn't break backward compatibility?

    Shouldn't the retention = and job history attributes (and probably others) be
    RECOMMENDED in Job Extensions?

    I shudder at perpetuating IPP specs = that are a basket of OPTIONAL
    attributes.  = That doesn't help interoperability particularly.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Thu, Mar 7, 2019 at 11:58 AM Michael = Sweet <msweet@apple.com> wrote:
    Well, if we put job-retain-until in Job = Extensions 1.1, then we should probably put job-delay-output-until in = JOBEXT as well (since now we'll have a bunch of Job Template attributes = in JOBEXT that control scheduling/job lifecycle decisions)

    Just remember that in = JOBEXT all of this will be OPTIONAL anyways.

    I will also post a RFC for another = attribute to close the last lifecycle hole (how long a job stays in = history).


    On Mar 6, 2019, at 4:50 PM, Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi,

    I just read this entire = thread carefully.

    I agree with all of your joint conclusions (good work Smith = and Mike),
    *except* for = "job-retain-until-xxx".

    I consider the lack of "job-retain-until-xxx" an = architectural mistake
    in IPP/1.1.  So I'd like = it to be present in Job Extensions, so that
    some = version lower than IPP/2.2 (Enterprise) can reliably use it.
    I suggest making it RECOMMENDED in IPP/2.0 and = REQUIRED
    in IPP/2.1 and above.

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Wed, Mar 6, 2019 at 4:03 PM Michael = Sweet via ipp <ipp@pwg.org> wrote:
    Smith,

    On Mar 6, 2019, at 3:41 PM, Kennedy, Smith = (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote:
    ...
     Also, I don't think we want a = job-retain-until-time-default, since the value is an absolute dateTime = value (unless we make -time an integer and add a -date version for = dateTime?)

    Hmmm, how about just = having "job-retain-until" (type2 keyword) and "job-retain-until-time" = (integer) and not bother with "job-retain-until-date" = (dateTime)?

    Let's discuss this at the next concall - I can see a use for = both (retain the job for 24 hours, retain the job until the next = scheduled update), and a Client can calculate the number of seconds to a = specific date/time, but there are still some vagaries due to submission = delays and whether the IPP job ticket is used directly and immediately = or if it gets "relayed" to the destination output device that is doing = the retaining...

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

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

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer


    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_BfCq4/cpKyp4UBR+7SlFkA)-- --===============5337674583477487020== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5337674583477487020==-- From ipp-bounces@pwg.org Thu Mar 7 13:59:20 2019 Return-Path: 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 13017130FF3 for ; Thu, 7 Mar 2019 13:59:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 4NSPLaWbKLju for ; Thu, 7 Mar 2019 13:59:17 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED9A1275E9 for ; Thu, 7 Mar 2019 13:59:17 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 8EB893F4A; Thu, 7 Mar 2019 21:59:15 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 90CFC24D3; Thu, 7 Mar 2019 21:59:10 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 8D52C3F45; Thu, 7 Mar 2019 21:59:08 +0000 (UTC) Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by www.pwg.org (Postfix) with ESMTPS id 742E424D3 for ; Thu, 7 Mar 2019 21:59:07 +0000 (UTC) Received: by mail-yw1-xc29.google.com with SMTP id u70so193627ywf.7 for ; Thu, 07 Mar 2019 13:59:07 -0800 (PST) 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=dJUMba6hNuxWNBnEIo8GDbEwz75xQjv0KIZQIed95+g=; b=hGgo/VQfKtV8DLXHaMeRpIs86cwXNfzdX8euooXDhEWQG9a+ppWn47hgOkPR5GU9Vl az20SDLfhYqCXvQQ8yIvA+5q21aNSKSYgtySOjMxD8ytaJFmWBpR+oBV15A7XyYJd1/E QcNQHzQ0vEgoT9ZGbjQAkPmGXqc/0Z2j52Bkc5p2E74V9bGHWzOBTdd399jqDyAeaMWV RROUcpmlTghOBQefJtHAMDM/YO/hotY7oJ+YgVqqJClA8AxG7OcVjv9nkQp/mOPz4ut8 MNHOUszOh9eK4brX1PeiWWas+nseH2GtCXB75OyWsgbj8FbdGNbpexdEdLmJfxvthY+8 w5dg== 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=dJUMba6hNuxWNBnEIo8GDbEwz75xQjv0KIZQIed95+g=; b=S+jDTr82Po4d5arXWB6f4qDIwI+VUCYtd2euHxBtKI0p65lFZXFVtont9rpCymiRxI MRSwrh06RA3pjV5shAM7eej+aD5UcWGqcIyHQ3Jku0KpJbwnbyxDEVDnfW/1AoL0Fzdf ior4D/I8B7LTg20R4jwO4ir9ilUYzZy35W8wmcNWI39FuP136pkoUQ4eoqJxAUeiUVAb n8VmkTPTBBd/4a0DW+9F8pwyo0AbDFoTtGfzKWX8STnOuruFdv/MRIJDQEXrK1gCVPWq 55JVapKAobDSOznElbyns/6UqsUiEdBv3Xj9Cs+N/MXFjmr2JFRBYR1f7J7fWgqMzkti Y5Xg== X-Gm-Message-State: APjAAAXT4j3az5j6VEaSVNV85dMd5pkzK9J0dSIuteCwBT7m2SbslyBO l4CCxNTmK8VnID2G84ZfK/myNs6i33Ybx+MiMO4= X-Google-Smtp-Source: APXvYqyl9KmOi0zJI7foc3/1OMm/3/Sdh2Eb7VlcC6tFcPjD7nYe5WEB+Y1AS+aLZMdqmPEvsuB+gEx7K3NkNf44rpk= X-Received: by 2002:a25:646:: with SMTP id 67mr13128484ybg.472.1551995946594; Thu, 07 Mar 2019 13:59:06 -0800 (PST) MIME-Version: 1.0 References: <8437B20E-AABA-43D2-B0CD-5166E1B48AA3@apple.com> In-Reply-To: <8437B20E-AABA-43D2-B0CD-5166E1B48AA3@apple.com> Date: Thu, 7 Mar 2019 16:58:53 -0500 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: IPP Job Extensions v1.1 or v2.0? X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============2720771178373419510==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2720771178373419510== Content-Type: multipart/alternative; boundary="00000000000016f80e058388378f" --00000000000016f80e058388378f Content-Type: text/plain; charset="UTF-8" Hi Mike, I actually favor v2.0, with a firm hand making attributes filling holes in IPP/1.1 (retention, history, etc.) as REQUIRED and as many as possible remaining attributes as RECOMMENDED. I hope we stop using OPTIONAL in IPP specs and reserve it for "experimental" or "narrow-use" new stuff in Registrations. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Mar 7, 2019 at 12:51 PM Michael Sweet via ipp wrote: > All, > > I mentioned this in a previous thread, but wanted to bring this up in a > new thread to discuss separately. > > We are in the process of updating PWG 5100.7-2003: IPP Job Extensions > (JOBEXT), and based on previous discussions have decided to incorporate > parts of PWG 5100.11-2010: IPP Job and Printer Extensions - Set 2 (JPS2) > that have more general usefulness, with the remaining enterprise > functionality going into a new IPP Enterprise Printing Extensions > specification to replace 5100.11 (which will be obsoleted, like we did for > the original overrides spec many years ago). > > Many of the attributes coming from 5100.11 are OPTIONAL, so adding them to > Job Extensions v1.1 poses no problem for our defined standards errata > process - no change in conformance for the original 5100.7 so the > 5100.7-2019 update will be backwards-compatible with any implementation > conformaing to 5100.7-2003. > > However, JPS2 also defines four new REQUIRED operations and a REQUIRED > operation attribute (job-ids). Keeping these in a 5100.11 errata update > would pose no problem, but PWG Process/3.0 says nothing about cross-spec > errata updates. > > Using a conservative interpretation of the approved process, we would need > to change the major version number of the Job Extensions specification to > increase the conformance requirements, and then use the "long" process > (verification of prototyping, PWG Last Call, and PWG Formal Vote) instead > of the "short" process (PWG Call for Objections). > > An alternative is to make these operations RECOMMENDED and job-ids > conditionally required - then there is no conformance increase and we can > use the short process for an errata update. Since IPP Everywhere already > makes most of these operations REQUIRED already, the practical reality is > that they will be required attributes. > > Thoughts? > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --00000000000016f80e058388378f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    I actually favor v2= .0, with a firm hand making attributes filling
    holes in IPP/1.1 (= retention, history, etc.) as REQUIRED and
    as many as possible rem= aining attributes as RECOMMENDED.

    I hope we stop u= sing OPTIONAL in IPP specs and reserve it
    for "experimental&= quot; or "narrow-use" new stuff in Registrations.

    <= /div>
    Cheers,
    - Ira

    = Ira McDonald (Musician / Software Architect)
    Co-Chair - TCG Trusted Mobi= lity Solutions WG
    Co-Chair - TCG Metadata Access Protocol SG
    <= /div>
    Chair - Linux Foundation Open Printing WG
    Secretar= y - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PWG Internet Pr= inting Protocol WG
    IETF Designated Expert - IPP & Printer MIB
    Blu= e Roof Music / High North Inc
    http://sites.= google.com/site/blueroofmusic
    http://sit= es.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221= =C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434



    On Thu, Mar 7, 2019 at 12:51= PM Michael Sweet via ipp <ipp@pwg.org> wrote:
    All= ,

    I mentioned this in a previous thread, but wanted to bring this up in a new= thread to discuss separately.

    We are in the process of updating PWG 5100.7-2003: IPP Job Extensions (JOBE= XT), and based on previous discussions have decided to incorporate parts of= PWG 5100.11-2010: IPP Job and Printer Extensions - Set 2 (JPS2) that have = more general usefulness, with the remaining enterprise functionality going = into a new IPP Enterprise Printing Extensions specification to replace 5100= .11 (which will be obsoleted, like we did for the original overrides spec m= any years ago).

    Many of the attributes coming from 5100.11 are OPTIONAL, so adding them to = Job Extensions v1.1 poses no problem for our defined standards errata proce= ss - no change in conformance for the original 5100.7 so the 5100.7-2019 up= date will be backwards-compatible with any implementation conformaing to 51= 00.7-2003.

    However, JPS2 also defines four new REQUIRED operations and a REQUIRED oper= ation attribute (job-ids). Keeping these in a 5100.11 errata update would p= ose no problem, but PWG Process/3.0 says nothing about cross-spec errata up= dates.

    Using a conservative interpretation of the approved process, we would need = to change the major version number of the Job Extensions specification to i= ncrease the conformance requirements, and then use the "long" pro= cess (verification of prototyping, PWG Last Call, and PWG Formal Vote) inst= ead of the "short" process (PWG Call for Objections).

    An alternative is to make these operations RECOMMENDED and job-ids conditio= nally required - then there is no conformance increase and we can use the s= hort process for an errata update.=C2=A0 Since IPP Everywhere already makes= most of these operations REQUIRED already, the practical reality is that t= hey will be required attributes.

    Thoughts?

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --00000000000016f80e058388378f-- --===============2720771178373419510== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2720771178373419510==-- From ipp-bounces@pwg.org Fri Mar 8 12:51:22 2019 Return-Path: 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 02AEA1274A1 for ; Fri, 8 Mar 2019 12:51:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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=apple.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 0Vv5lWcF1bVw for ; Fri, 8 Mar 2019 12:51:20 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 24E85126DFA for ; Fri, 8 Mar 2019 12:51:20 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id A4E0E3F4B; Fri, 8 Mar 2019 20:51:18 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 28564269F; Fri, 8 Mar 2019 20:51:15 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id EFB76266A; Fri, 8 Mar 2019 20:51:13 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id 747DF266A for ; Fri, 8 Mar 2019 20:51:13 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x28KkVst036158 for ; Fri, 8 Mar 2019 12:51:12 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=Em0IgliQM+2w5Haj6DpSFK2Xsaj8MUKAX/7V1MCzp/s=; b=rh7WQw++XBNoSgwgK0KyxcFWAhNe0VkW1FBSNe5SUi9F7G7AhWsSVKWVi7s3wgx05Gcf 8kokzPzCmzXrateIlh1f7HzqYH8X5Kk8dh6AnGG2ZCh2rKBWfDvFr1gpnd0ukaHT7+Z3 5xDpr2WKMEK9nBLNfQkfKbWQlOyNWlpBIzd0HqSy8zC9uOaiwL9ZH84CeYRmzZrVPm1G 9c99hDwfy8uN/RDIMoLnzHe/EuxqpQe3u86+8Ht08WvlmoiPiMk/O/33JyC2ZP0Dsjsr V/t8+z+lIg6Y9K3e1j7ZEba26BgAm/6WYM8qtIz8/T+phbhL0LLFATHhccsANbo9ON9I EA== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2qyqd4ubnq-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 08 Mar 2019 12:51:12 -0800 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0PO200BTFF9BD650@mr2-mtap-s01.rno.apple.com> for ipp@pwg.org; Fri, 08 Mar 2019 12:51:11 -0800 (PST) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0PO200A00EWFS200@nwk-mmpp-sz12.apple.com>; Fri, 08 Mar 2019 12:51:11 -0800 (PST) X-Va-A: X-Va-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-Va-E-CD: 79f29c7c933374d32fe361e5f68ebe91 X-Va-R-CD: dd78dfa6784de98994b147083c50939a X-Va-CD: 0 X-Va-ID: b838c36b-0edb-499d-ba00-270422e5e0da X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 79f29c7c933374d32fe361e5f68ebe91 X-V-R-CD: dd78dfa6784de98994b147083c50939a X-V-CD: 0 X-V-ID: b9b57cd7-c266-4ec1-b40c-636b8fa8c669 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-08_18:,, signatures=0 Received: from [17.235.62.131] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0PO200FBYF965K60@nwk-mmpp-sz12.apple.com>; Fri, 08 Mar 2019 12:51:09 -0800 (PST) Date: Fri, 08 Mar 2019 15:51:06 -0500 Message-id: <768B6CC1-2C8F-496A-BA75-8B880475E8F8@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-08_18:, , signatures=0 Subject: [IPP] Updated prototype draft of IPP Job Extensions v1.1 posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted an updated prototype draft of the IPP Job Extensions v1.1 specification to: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext11-20190308.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext11-20190308.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext11-20190308-rev.pdf This version of the specification adds operations, attributes, and values from JPS2 (which will be obsoleted/retired), adds the new job-retain-until-xxx and job-history-xxx attributes, and has some other cleanup from prior reviews of the document. All of the newly-added content is currently RECOMMENDED. Aside from needing a full review, we also need to make a decision about whether to promote this specification to v2.0 (where we can change the conformance requirements as desired) or leave it as a v1.1 errata update. So far we have one vote in favor of making this a 2.0 document... _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Sat Mar 9 06:15:47 2019 Return-Path: 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 68CD9127968 for ; Sat, 9 Mar 2019 06:15:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 s8caoV4Xn2HK for ; Sat, 9 Mar 2019 06:15:45 -0800 (PST) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 25ED71276D0 for ; Sat, 9 Mar 2019 06:15:45 -0800 (PST) Received: by www.pwg.org (Postfix, from userid 1002) id 6DA243F46; Sat, 9 Mar 2019 14:15:44 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 53ACC26AA; Sat, 9 Mar 2019 14:15:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 2AF0D3F32; Sat, 9 Mar 2019 14:15:38 +0000 (UTC) Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) by www.pwg.org (Postfix) with ESMTPS id 6C0502645; Sat, 9 Mar 2019 14:15:37 +0000 (UTC) Received: by mail-yw1-xc30.google.com with SMTP id r188so361725ywb.12; Sat, 09 Mar 2019 06:15:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=67fJpsViYYZGFrXugZOoIcY7xFqqXiJt/Pru/FdquCE=; b=nzEV7iwl8T712RMRf/EnD06TM7Kd7xtsakuPPq3qeu6IGhx1dMMDRLr0wi/aITNbxi ikSGV25L7vQb1SCw5xo7Bi/BjRHQUStG/ocBltNS7h1IP+N2O43fnHY5QtknoNp8XUC9 VhtQFjcusgsF/ZgDbrs6haABQvNE32WDxnXAn/xbahPBE8TzQDPZHsUQ/n9w/UuWJ3/7 1ChdmYMnWNOmrztfNIWGsDxFPVANVZ00Z9aqpxvaqmJjbuyI9MfRQdWhiGGJOJcQ7PiW Xkm5ylQVUUkFKFtBOEIigX0jBcEIL2oj9jZVyS3fRl1cuxKoDi+BPR1EL6yK3gOJobE8 BmCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=67fJpsViYYZGFrXugZOoIcY7xFqqXiJt/Pru/FdquCE=; b=goJuBas5ioG/t3TCy3zqoJmhpTLcT5IaSM3e+5aFbGWQnkmekeS0zwJR9E1Q5tAZIv tzqDVahS4yfLnrxUAYXeRI5+YgEPtZh+aCepRrVehA8N4ZTo1laxxd1RfzwNQSGuqCOT PZALaL8Hs/5/HqU7Y2hUolCefUazCV8VP9u7VPPSv2Qfdj8SCd9UwqEzVoR+Arf6lVxD M5pFFHQE3OY1XIQommfPZDaJMsDvRzdZldRv4eFvINGvkellH2waZLvMzSlr5fQmyByJ a4zD6EPlar5TZGInvf6x0deG03kpMFxxfJKda+6n78WdxeX9Ce+uTlxlirelpjinQtDe 399Q== X-Gm-Message-State: APjAAAWsMuJw536t5chvO7P5/ZLh3AyMgT4LZQvcyO4wmE0wi8XIu3CN G+gKA9agPU2kjFvKTHJlIukC/ZcAz/jzd9kJWrG5o6TX X-Google-Smtp-Source: APXvYqw6l0IPkZ3TWEaPEXCHDKUM65rsy7LRXTywj1UXOQysog+DDz134pvlG78W2Ij9q4ZRtpMNyA1J1S7E0M0p4eE= X-Received: by 2002:a81:5f86:: with SMTP id t128mr19247986ywb.467.1552140936343; Sat, 09 Mar 2019 06:15:36 -0800 (PST) MIME-Version: 1.0 Date: Sat, 9 Mar 2019 09:15:22 -0500 Message-ID: To: "ipp@pwg.org" , tms_wg@trustedcomputinggroup.org, MPWG , "ids@pwg.org" , Ira McDonald Subject: [IPP] FYI: IRTF Privacy Enhancements and Assessments Proposed Research Group (PEARG) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============0147272868288813460==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0147272868288813460== Content-Type: multipart/alternative; boundary="00000000000026f7e30583a9f992" --00000000000026f7e30583a9f992 Content-Type: text/plain; charset="UTF-8" Hi, A recent submission to the IETF's ISE (Independent Stream Editor), led to a recommendation for engagement with this excellent long-term research group. Watching their mailing list would be useful for anyone interesting in state-of-the-art privacy protection modifications to new and existing protocols. https://irtf.org/pearg 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 --00000000000026f7e30583a9f992 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    A recen= t submission to the IETF's ISE (Independent Stream Editor),
    l= ed to a recommendation for engagement with this excellent long-term
    research group.=C2=A0 Watching their mailing list would be useful for an= yone
    interesting in state-of-the-art privacy protection modificat= ions to new
    and existing protocols.


    Cheers,
    - Ira

    <= div>
    Ira McDonald (Musician / Softwar= e Architect)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-C= hair - TCG Metadata Access Protocol SG
    Chair - Li= nux Foundation Open Printing WG
    Secretary - IEEE-ISTO Printer Working Gr= oup
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Desig= nated Expert - IPP & Printer MIB
    Blue Roof Music / High North Inchttp://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc<= /a>
    mailto:     blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2= =A0 906-494-2434

    <= /div>
    --00000000000026f7e30583a9f992-- --===============0147272868288813460== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0147272868288813460==-- From ipp-bounces@pwg.org Thu Mar 14 09:02:56 2019 Return-Path: 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 A6EA01279AD for ; Thu, 14 Mar 2019 09:02:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.271 X-Spam-Level: X-Spam-Status: No, score=-2.271 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.428, 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 JczqfIOQHOmu for ; Thu, 14 Mar 2019 09:02:53 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id C503C130E16 for ; Thu, 14 Mar 2019 09:02:48 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id AC3403F51; Thu, 14 Mar 2019 16:02:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id C25863BA9; Thu, 14 Mar 2019 16:02:35 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 28FD63BA9; Thu, 14 Mar 2019 16:02:35 +0000 (UTC) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) by www.pwg.org (Postfix) with ESMTPS id 12D692618 for ; Thu, 14 Mar 2019 16:02:33 +0000 (UTC) Received: by mail-yw1-xc2c.google.com with SMTP id z191so4819950ywa.6 for ; Thu, 14 Mar 2019 09:02:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UBbTrwsouYdObtVdG8mye4+5CfuF16z51iJQWVmuYbs=; b=OyvyKEWnGigH8Q25T6B254KGFfguEfQoznQTXT47WvNivHfhZvf9qJeKNR3ujiiJgn zxxRcBTLn3YuHtOicAGEBsI9G6Nz78ecIFKuNEX+yamNNs3Ez0jURpb0C+CVrDR6ej6i CDSz92mtrNziledTh5FSk0UMcy1u3BP7QPar73uYTwkAyfhOC0o9Qpb6l3TeesZhhHxo aPSNONDzZtAaW7+wWH7pA5oM5eYgQTMVdrP8kk1+/DSC26VPN19gmTu57TB7VFDNCGD3 M1eCsGVa8VmQVbmt6pNWxdCto5JVhWubUsqGoPNAaavRcm/jmd9Ua3wSANvFUvVdt1gD QiOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UBbTrwsouYdObtVdG8mye4+5CfuF16z51iJQWVmuYbs=; b=s5FrgEZ5E26LIXuLQUo8kYA1i/yZCaw8W0uXYR5BrI5ghrH8tCJpOLoJJGsFUYV2cX BYEdQ4xfXe0nBWTorSVkAl2PQKSAT7gLJYVYfRdAIYJwL8xVuPYFnjtcTkCrsrN4j78d J5FevQSwmCkQ00x/DovXPy7tNr3khy8+joAF0vW7tATHTFZuxxZmfWFIgzj2rWTE7DPX RX6J6bBmf0vdsG3Etl8oSQE3/BDGf92W59I8IMerbd2DNy04zImIcguozWVR/SYNdmnc oTCmhhHRwTP5uR/Ow6Eaarh+LkpUazGfKJ2sloMogAhSxQsz7L9/fyzVNxV9mtxIA5nv aU4w== X-Gm-Message-State: APjAAAXmsNUtfXZ0CTn7tUrGZ0Eh7AiqosEOW/xzz88gjEOG1E0h09b6 lGPLGDU8pGJGb4ZZEcmZFfV7xZOPPNyBbSBNQO2glEDW X-Google-Smtp-Source: APXvYqyK8kXfIwoUVLEeAaz9pPDAmTxChaWDvphYP2AllxknhA10PGDVDi6xG5Enf5WZyRzLUm8PSXI8f4M/cCPKE6M= X-Received: by 2002:a25:ea02:: with SMTP id p2mr41334568ybd.41.1552579351777; Thu, 14 Mar 2019 09:02:31 -0700 (PDT) MIME-Version: 1.0 Date: Thu, 14 Mar 2019 12:02:17 -0400 Message-ID: To: "ipp@pwg.org" , Ira McDonald Subject: [IPP] IPP WG Agenda 3:00-4:30pm US Eastern (14 March 2019) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============5102635024426670753==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5102635024426670753== Content-Type: multipart/alternative; boundary="000000000000bf985a0584100c29" --000000000000bf985a0584100c29 Content-Type: text/plain; charset="UTF-8" Hi, Our next IPP WG call will be Thursday 14 March 2019 at 12:00-1:30pm US Pacific / 3:00pm-4:30pm US Eastern NOTE: Please USE the *new* WebEx and Audio Bridge below ------------------------------------------------------- Meeting information ------------------------------------------------------- Topic: IPP WG Every 2 weeks on Thursday 3:00-4:30 pm US Eastern (GMT-05:00) ------------------------------------------------------- WebEx online meeting (join WebEx first, before audio bridge) ------------------------------------------------------- 1. Go to https://ieee-isto.webex.com/ieee-isto/j.php?MTID=m8952a7e2500bbe43a428c15193736ec0 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: Printing123 4. Click "Join". ------------------------------------------------------- Audio Bridge (join audio second w/ unique access code from WebEx) ------------------------------------------------------- Call-in toll-free number (US/Canada): +1 866 469-3239 <%28866%29%20469-3239> Call-in toll number (US/Canada): +1 650 429-3300 <%28650%29%20429-3300> Call-in toll number (US/Canada): +1 408 856-9570 <%28408%29%20856-9570> Global toll-free call in numbers and other audio options ("Call Me Back" or VoIP) are listed once you join the WebEx meeting. Unique attendee access code: Displayed in the WebEx meeting Agenda: (1) PWG IP Policy, Minute Taker, Roll Call, and Agenda Review - Mike as minute taker? -- Status of all IPP documents in progress up-to-date below -- Discussion or review topics for today? (2) Approve IPP minutes from previous meetings - http://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20190228.pdf -- IPP WG call on 02/28/19 (3) Status/Review of various IPP mailing list notes - http://www.pwg.org/archives/ipp/2019/019945.html -- W3C approves WebAuthn (Mike) - http://www.pwg.org/archives/ipp/2019/019948.html -- IPP Everywhere PWG-Raster and PDF Requirement (Sean Kau) - http://www.pwg.org/archives/ipp/2019/019958.html -- RFC: DEPRECATED and OBSOLETED definitions (Mike) - http://www.pwg.org/archives/ipp/2019/019959.html -- NIST Threshold Cryptography Workshop 2019: Live Webcast (Ira) - http://www.pwg.org/archives/ipp/2019/019966.html -- NISTIR 8214: Final Publication and Public Comments - http://www.pwg.org/archives/ipp/2019/019968.html -- RFC: job-history-interval-configured/-supported Printer Description attributes (Mike) - http://www.pwg.org/archives/ipp/2019/019985.html -- FYI: IRTF Privacy Enhancements and Assessments Proposed Research Group (PEARG) (Ira) (4) Status of AMSC and ISO liaisons w/ PWG (Paul) - https://ftp.pwg.org/pub/pwg/general/sc/pwg-sc-call-minutes-20181105.htm - https://ftp.pwg.org/pub/pwg/general/sc/pwg-sc-call-minutes-20181217.htm -- see PWG SC minutes from 5 November 2018 -- see PWG SC minutes from 17 December 2018 (5) LCRC Review of IPP Authentication Methods (Smith) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- PWG Last Call ended 28 February 2019 -- Schedule - PWG Formal Vote in Q1/Q2 2019 (6) Status of Safe G-Code (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190117-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- PWG Last Call ended 28 February 2019 - LCRC review pending -- Schedule - PWG Formal Vote in Q1/Q2 2019 (7) Status of IPP 3D Printing Extensions v1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d11-20190201-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- PWG Call for Objections ends 29 March 2019 -- Schedule - Publication as PWG Candidate Standard in Q2 2019 (8) Status of IPP Everywhere 1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20190128-rev.pdf - http://www.pwg.org/archives/ipp/2019/019856.html - http://www.pwg.org/archives/ipp/2019/019857.html -- Stable draft - PWG F2F discussion in February 2019 -- Defer PWG Last Call until IPP Everywhere 1.1 Self-Cert is ready -- Schedule - Stable working drafts/beta tools in Q1/Q2 2019 (9) Status of IPP Everywhere 1.1 Self-Certification Manual 1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeveselfcert11-20180704-rev.pdf -- Prototype draft - PWG F2F discussion in February 2019 -- If we use Github to host the PWG website, how to submit printers? -- Consensus - Mike to update to separate submission process from self-cert process -- Future stable URL for submissions (backport to 1.0 tools/process) -- Schedule - Stable working drafts/beta tools in Q1/Q2 2019 (10) Status of IPP System Service (Ira/Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsystem10-20190130-rev.pdf -- Prototype draft - PWG F2F review in February 2019 -- Prototyping tasks being tracked as a Github project in "ippserver" -- Schedule - Stable working draft and PWG Last Call in Q2 2019 (11) Status of PWG MFD Alerts 1.1 (Ira) - http://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190216-rev.pdf -- Stable draft - PWG F2F review in February 2019 -- Need to add "changes" sections, will address in IPP WG last call comments -- IPP WG Last Call ends 14 March 2019 -- Schedule - PWG Call for Objections in Q1/Q2 2019 (12) Status of IPP Document Object v1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippdocobject11-20190129-rev.pdf -- Prototype draft - PWG F2F discussion in February 2019 -- Prototyping tasks being tracked as a Github project in "ippserver" -- Need to add DEPRECATED and OBSOLETE terminology definitions -- Schedule - Stable draft and IPP WG Last Call in Q1/Q2 2019 (13) Review of IPP Job Extensions v1.1 (Mike) - http://www.pwg.org/archives/ipp/2019/019976.html - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext11-20190308-rev.pdf -- Prototype draft - PWG F2F discussion in February 2019 -- Need to add DEPRECATED and OBSOLETE terminology definitions -- Lots of additions from JPS2 - publish as v1.1 or v2.0? -- Schedule - Stable draft and IPP WG Last Call in Q1/Q2 2019 (14) Status of IPP Enterprise Printing Extensions v2.0 (formerly JPS2) (Smith) - http://www.pwg.org/archives/ipp/2019/019932.html - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext2v20-20190214.docx -- Interim draft (former JPS2) - PWG F2F review in February 2019 -- Proposal - Obsolete original JPS2 entirely (undesirable attributes/definitions) -- New spec named "IPP Enterprise Printing Extensions v2.0" (note the version) -- New registrations for loose ends -- Focus on Enterprise Printing use cases -- Discussion on the IPP mailing list to determine which content stays, which content moves, and which content is deprecated or obsoleted -- Moved Cancel-Jobs, Cancel-My-Jobs, and Close-Job operations to the Job Ext v1.1 errata updates -- Schedule - Prototype draft Q3 2019 (15) Status of IPP Encrypted Jobs and Documents (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrustnoone10-20190131-rev.pdf -- Interim draft - PWG F2F discussion in February 2019 -- Schedule - Prototype draft Q3 2019 (16) Open Printing update (Ira) -- OP monthly calls (02/12/19) and (03/05/19) -- OP website renovation major progress using Jekyll - new developer team -- GSoC 2019 OP project edits closed (02/06/19) -- GSoC 2019 Linux Foundation mentor application accepted (02/26/19) -- GSoC 2019 Potential students discuss ideas w/ mentors until (03/25/19) -- GSoC 2019 Student application period begins (03/25/19) (17) Next steps - IPP WG call on Thu 28 March 2019 at 3:00-4:30pm US Eastern -- regular topics - IPP WG call on Thu 11 April 2019 at 3:00-4:30pm US Eastern -- slide review for April 2019 PWG/OP F2F - IPP sessions on Wed/Thu 17-18 April 2019 during PWG/OP F2F -- see agenda on PWG meetings page 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 --000000000000bf985a0584100c29 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    <= div dir=3D"ltr">
    Hi,

    Our next IPP WG call will be Thursday 14 March 2019 a= t
    12:00-1:30pm US Pacific / 3:00pm-4:30pm US Eastern

    NOTE: Please USE the *new* WebEx and A= udio Bridge below

    -------------------------------= ------------------------
    Meeting information
    ------------------------= -------------------------------
    Topic: = = IPP WG
    Every 2 weeks on Th= ursday 3:00-4:30 pm US Eastern (GMT-05:00)

    = -------------------------------------------------------
    WebEx online mee= ting (join WebEx first, bef= ore audio bridge)
    -----------------------------------------------= --------
    1. Go to https://ieee-i= sto.webex.com/ieee-isto/j.php?MTID=3Dm8952a7e2500bbe43a428c15193736ec0<= br>2. If requested, enter your name and email address.
    3. If a password = is required, enter the meeting password: Printing123
    4. Click "Join= ".

    -------------------------------------------------------
    Audio Bridge (join au= dio second w/ unique access code from WebEx)
    --------------------= -----------------------------------
    Call-in toll-free number (US/Canada): +1 866 = 469-3239
    Call-in toll number (US/Canada): +1 650 429-3300
    Call-in toll number (US/Canada): +1= 408 856-9570

    Gl= obal toll-free call= in numbers and other audio options ("Call Me Back" or VoIP) are listed once you joi= n the WebEx meeting.

    Unique attendee access code:=C2=A0 Displayed in= the WebEx meeting

    Agenda= :
    (1) PWG IP Policy, Minute Taker, Roll Call, and Agenda Revi= ew
    - Mike as minute taker?
    -- Status of all IPP documents in progress up-to-date below
    -- Discussion or review topics for today?

    (2) App= rove IPP minutes from previous meetings

    (3) Status/Review of various IPP mailing list notes
    -- W3C approves WebAuthn (Mike)
    -- IPP Everywhe= re PWG-Raster and PDF Requirement (Sean Kau)
    -- RFC: DEPRECATED and OBSOLETED definitions= (Mike)
    -- NIS= T Threshold Cryptography Workshop 2019: Live Webcast (Ira)
    -- NISTIR 8214: Final Publicat= ion and Public Comments
    - http://www.pwg.org/archives/ipp/2019/019968.html<= /div>
    -- RFC: job-history-interval-configured/-supported Printer Descri= ption attributes (Mike)
    - http://www.pwg.org/archives/ipp/2019/019985.html<= /div>
    -- FYI: IRTF Privacy Enhancements and Assessments Proposed Resear= ch Group (PEARG) (Ira)

    (4) Status of AMSC and ISO liaisons w/ PWG (Paul)

    -- Stable draft - PWG F2F di= scussion in February 2019
    -- PWG Last Call ended 28 F= ebruary 2019
    -- Schedule - PWG Formal Vote in Q1/Q2 2019

    (6) Status of Safe G= -Code (Mike)
    -=20 https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode= 10-20190117-rev.pdf
    -- Stable draft - PWG F2F discussion in February 2019
    -- PWG Last Call ended 28 F= ebruary 2019 - LCRC review pending
    -- Schedule - PWG Formal Vote in Q1/Q2 2019

    (7) Status of IPP 3D Printing Extensions = v1.1 (Mike)
    -- Stable draft -=C2=A0 PWG F2F discussion in February 2019
    = -- PWG Call for Objections = ends 29 March 2019
    -- Schedule - Publication as PWG Ca= ndidate Standard in Q2 2019

    - http://www.pwg.org/archives/ipp/2019/019857.html
    -- Stable draft - PWG F2F discussion in February 2019
    -- Defer PWG Last Cal= l until IPP Everywhere 1.1 Self-Cert is ready
    -- = Schedule - Stable working drafts/beta tools in Q1/Q2 2019

    (9) Status of IP= P Everywhere 1.1 Self-Certification Manual 1.1 (Mike)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeveselfcert11-20180704-rev.pdf
    --=20 Prototype draft - PWG F2F discussion in February 2019
    -- If we use Github to host the PWG website, how to sub= mit printers?
    -- Consensus - Mike to update to separate submission proce= ss from self-cert process
    -- Future stable URL for submissions (backport= to 1.0 tools/process)
    -- Schedule - Stable working drafts= /beta tools in Q1/Q2 2019

    (10) Status of IP= P System Service (Ira/Mike)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsystem10-20190130-r= ev.pdf
    -- Prototyp= e draft=20 - PWG F2F review in February 2019
    -- = Prototyping tasks being tracked as a Github project in "ippserver"= ;
    -- Schedule - Stable working draft and PWG Last Call in Q2 2019
    <= div>

    -- Prototyping tasks being tracked as a Github project in "ippserver&q= uot;
    -- Need to add DEPRECATED and OBSOLETE terminology defi= nitions
    -- Schedule - Stable draft and IPP WG Last Call in Q1= /Q2 2019

    (13) Review of IPP Job Extensions v1.1 (Mike)
    -- Prototype draft -=C2= =A0 PWG F2F discussion in February 2019
    -- Need to add DEPRECATED and OBSOLETE terminology definitions
    -- Lots of addit= ions from JPS2 - publish as v1.1 or v2.0?
    -- Schedule = - Stable draft and IPP WG Last Call in Q1/Q2 2019

    = (14) Status of IPP Enterprise Printing Extensions v2.0 (formerly JPS2) (Smi= th)
    -- Interim draft (former JPS2) - PW= G F2F review in=C2=A0 February 2019
    -- = Proposal - Obsolete original JPS2 entirely (undesirable attributes/definiti= ons)
    -- New spec named "IPP Enterprise Printing Extensions v2.0&quo= t; (note the version)
    -- New registrations for loose ends
    -- Focus on Enterprise P= rinting use cases
    -- Discussion on the IPP mailing list to determine whi= ch content stays, which content
    =C2=A0=C2=A0 moves, and which content i= s deprecated or obsoleted
    -- Moved Cancel-Jobs, Cancel-My-Jobs, and Clos= e-Job operations to the Job Ext v1.1 errata updates
    -- Schedule -= Prototype draft Q3 2019

    (15) Status of IPP Encrypted Jobs and Documents (Mike)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd= -ipptrustnoone10-20190131-rev.pdf
    -- Interim draft - PWG F2F discussion= in February 2019
    -- Schedule - Prototype dra= ft Q3 2019

    (16) Open Printing update (Ira)<= /div>
    -- OP monthly calls (02/12/19) and (03/05/19)
    -- OP= website renovation major progress using Jekyll - new developer team
    -- GSoC 2019 OP project edi= ts closed (02/06/19)
    -- GSoC 2= 019 Linux Foundation mentor application accepted (02/26/19)
    -- GSoC 2019 Potential students discuss ideas w/ mentors until (03/25/19)
    -- GSoC 2019 Student application period begins (03/25/19)

    (17) Next steps

    <= div>
    - IPP WG= call on Thu 28 March 2019 at 3:00-4:30pm US Eastern
    -- regular topics

    - IPP WG= call on Thu 11 April 2019 at 3:00-4:30pm US Eastern
    -- slide review for April 2019 PWG/OP F2F

    - IPP se= ssions on Wed/Thu 17-18 April 2019 during PWG/OP F2F
    -- see agend= a on PWG meetings page

    Cheers,
    - Ira
    =
    Ira McDonald (Musician / Software Architect)
    Co-Chair - TCG Tru= sted Mobility Solutions WG
    Co-Chair - TCG Metadata Access Protoco= l SG
    Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PWG In= ternet Printing Protocol WG
    IETF Designated Expert - IPP & Printer M= IB
    Blue Roof Music / High North Inc
    http= ://sites.google.com/site/blueroofmusic
    h= ttp://sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO= Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434

    --000000000000bf985a0584100c29-- --===============5102635024426670753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5102635024426670753==-- From ipp-bounces@pwg.org Thu Mar 14 12:25:51 2019 Return-Path: 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 C0B3412DF72 for ; Thu, 14 Mar 2019 12:25:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.709 X-Spam-Level: X-Spam-Status: No, score=-0.709 tagged_above=-999 required=5 tests=[BAD_ENC_HEADER=0.001, BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, 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 YBa5cTxcX6dG for ; Thu, 14 Mar 2019 12:25:49 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 027DB1279A1 for ; Thu, 14 Mar 2019 12:25:48 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 92DC43F9B; Thu, 14 Mar 2019 19:25:48 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 0A21C266B; Thu, 14 Mar 2019 19:25:44 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id DD3853B9E; Thu, 14 Mar 2019 19:25:42 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 42D8C2618 for ; Thu, 14 Mar 2019 19:25:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1552591540; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=A00MNYYKnyGevqJMiORtlJpCeDnTbB/CoafBq2YAbdI=; b=EjsvNrQu0qjE+gJCvKcCbBNLEs6rw75m2XpH7/IVdZYHetj/JJe/TY5aZ+gxFSMY2kmWHC4OurvyXCF2v0TeG8uXh0A1Y6PoNTZPRV4ximmq2+IXhpY7NSNkMPKF+FYwZIDvEZ4Zrs5DF5M88MQPPQ6NhUT8DVwZ1gxLeMgAJoo= Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-bn3nam04lp2050.outbound.protection.outlook.com [104.47.46.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-229-1vOFR_XkPEiy-8ghpWOp5Q-1; Thu, 14 Mar 2019 15:25:38 -0400 X-MC-Unique: 1vOFR_XkPEiy-8ghpWOp5Q-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0663.NAMPRD84.PROD.OUTLOOK.COM (10.169.96.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19; Thu, 14 Mar 2019 19:25:37 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1709.011; Thu, 14 Mar 2019 19:25:37 +0000 To: Michael Sweet Thread-Topic: [IPP] W3C Approves WebAuthn Thread-Index: AQHU0rHsng+LBZHnPUmhFVFgct9RaaYLkgGA Date: Thu, 14 Mar 2019 19:25:36 +0000 Message-ID: <9ACC7A03-291B-4107-9CF5-33A47C26AD62@hp.com> References: In-Reply-To: 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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 2993fb40-04d0-423b-75d9-08d6a8b2d638 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0663; x-ms-traffictypediagnostic: CS1PR8401MB0663: x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; CS1PR8401MB0663; 23:nOZp75DWzWGnKKoqiU5sq3r4T+OrbN7Lj048OxL?= =?us-ascii?Q?AYQR3RIl6929dq1zON5YFVNuYhBJOOsVP8bCo8rRetfDRkYoDVhsbXxij0Nm?= =?us-ascii?Q?M3XTXZkbdw0CaAyh4cSgxROewjbEinonz/pbskEgeAIJZWPZp9xeBmIHoXoX?= =?us-ascii?Q?F7BBdJR9gvwrLKe2XbG6ZwJw3eXkniQBn0ldrGkuPNj7jd/+AOKdvSAfUVnd?= =?us-ascii?Q?rw8ncwGwOO1SqY5WHxuFmY1YuT2SKBId6uw3dwhBXZffcCB4t28W1bPvXdYZ?= =?us-ascii?Q?WX4e2QGZ1y9Uj6WY1HUhDfHY0CTIBAOQ/QjFq8MiBNHWdX3uzy6iKK/hvStU?= =?us-ascii?Q?VBnHWewAVJpof/jxg+jR2PMfO3aEAZdzzO1MvzS9epGk45r8e25qqVJtMgzi?= =?us-ascii?Q?H7iGWZ/v46x52c9Hacx0gtlKeOETFSYNZ95AKd+SJhkqYlC9PXApHhgTMJBt?= =?us-ascii?Q?m9gUC407QadyYOG47ghBr1UrLLHl84Zqov47vXvbSbAMxWkRKW9IAVUjnNlp?= =?us-ascii?Q?fIr6GlqOk8kKXf3AMPI3xNiW8RvlzO/nwrWV7/bFup/SIqnoIG78kj9PQiI7?= =?us-ascii?Q?hZbOA+V0zBlAtezGQcWYRU8Jha1w4hA+etGDVGywJiEDeOt95RMRunCuAyvN?= =?us-ascii?Q?H9y0A52ZMnd01yG16SoJ8a1VSxHiBmroz4OoGYlqwDXJV3CKyVcwiWdesSr+?= =?us-ascii?Q?vhkE/TRZYunac/wMycDL4/O5VTvFy4LD7VmdHdhObp9W47HG/pe2OPDlSM4X?= =?us-ascii?Q?ELhhViNOCcir9KcOdwkPJeAUWkS0tDj/E6XFskKBFbcl7Dp9KorEU4iuN48a?= =?us-ascii?Q?CepjmmslsdVq6Yh6YEAMBt1x3H13IxjbNZLUFCSNaD2v9aoWTJFaeBuOw5hI?= =?us-ascii?Q?+9Fv58pFMhTy7cDXSl4QZDV3AusQuPjqzjuLscExAbjLWiAKc4D+4k2mv8/8?= =?us-ascii?Q?D8ERGF1si9wWNcLhmhbrsf43DZj/suqpxZlBkfhNCYD17KcGx5nKODj/kcwM?= =?us-ascii?Q?SF8n96YXOeJr2tZVBkvpWcFdemJpe1dKSrTDwEAU9e3CrvMqYZTF9zTPW0eb?= =?us-ascii?Q?PsnO3Ip+rqe1nZZwZQvG32sxP6BLJq/zkl/Z/P86LKoF4MEFb0xLka0Jbh9J?= =?us-ascii?Q?4lZCYfW2a5IP1HdYv0xYqE03S/eHwUrjEjbh3/gHh/Q7hLpkcu5n865TKQ/u?= =?us-ascii?Q?LdrJQz/MSqjp23p/KYmJMTTV3cynsoDLjOkf7kiVk8aMyrwNeWzyyptkEZJ4?= =?us-ascii?Q?1bhoOquM9fh9yZMe36MlI6qEY4cvuppLoamntwYG2EOj9mlpmnL0V541KO81?= =?us-ascii?Q?KYzkveT9IuhxcLvSPFzQPLDRTNo0NfmOYSpkyf+oSVvRpqZ9e+ZEtK3mU69H?= =?us-ascii?Q?eQ3n9jofDgSEDJa5UOfKKvVL28Qo=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 09760A0505 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(136003)(376002)(366004)(346002)(199004)(189003)(6602003)(81166006)(7736002)(4326008)(97736004)(81156014)(8676002)(25786009)(2906002)(82746002)(53936002)(83716004)(236005)(6916009)(6246003)(66066001)(71200400001)(33656002)(606006)(478600001)(71190400001)(6512007)(36756003)(6486002)(6436002)(229853002)(26005)(966005)(105586002)(106356001)(186003)(14454004)(446003)(6506007)(53546011)(6116002)(76176011)(5660300002)(102836004)(8936002)(54896002)(6306002)(3846002)(68736007)(99286004)(4744005)(86362001)(256004)(476003)(316002)(11346002)(14444005)(99936001)(2616005)(486006); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0663; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: OdOdCbRkbCCaG8+VwZ3xRjUEY1FAinAlsdbOV45WkpwcQoUEoMlauQ3pe449ZsoJI4Pk6WV7QfB3qRcSR5sGNIHE/DIlUgqN0zzsoIOoFvdaxQVAREEIh8LITyaBW6Op6V+dArsMM5Rx6zUEQc8WZB65jnD/uFMWaSA15TQLvvzAkiJsTNMF4kgjgDEkKDEPdSEaosgthdAVbOpPBSZEwdb5lgO3HiHSUjkXllr4bKP0mO/xqx3IxtXkTB1skRReucJkWErvt5aU4lK27hn1JgHsERZUlgFtzxSBarripA8rwmC5G4iFvHbIlCDWKHoYh4EvKM3Jgq2cY59YFfBVDCHY1YVcJVy8QGKXG6P6KuLSroJ2oWH/nCIJfSsb0rGlgepUM4Z1G4Vd+El8R/EdhdNWDe9D2F0jLq2pfDESdaU= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 2993fb40-04d0-423b-75d9-08d6a8b2d638 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2019 19:25:36.9802 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0663 Cc: PWG IPP Workgroup Subject: Re: [IPP] W3C Approves WebAuthn X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============3013234945686770974==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============3013234945686770974== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F410F4D8-5A68-44F7-A82F-196A3E2C4454"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_F410F4D8-5A68-44F7-A82F-196A3E2C4454 Content-Type: multipart/alternative; boundary="Apple-Mail=_2F9D121E-66EF-4DC1-8930-3E2E5E50D2AA" --Apple-Mail=_2F9D121E-66EF-4DC1-8930-3E2E5E50D2AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Mike, I've been meaning to ask about this in the context of IPP Authentication = Methods. Should we update IPP Authentication Methods with this before = finishing it off? Or is WebAuthn outside the scope of IPP? Smith > On Mar 4, 2019, at 10:43 AM, Michael Sweet via ipp = wrote: >=20 > All, >=20 > Haven't had a chance to see if this could at all be used with IPP, but = WebAuthn is a new standard for authenticating without traditional = passwords: >=20 > https://www.w3.org/2019/03/pressrelease-webauthn-rec.html = = > https://www.w3.org/TR/webauthn/ = = >=20 > See also the related FIDO2 project information: >=20 > https://fidoalliance.org/fido2/ = >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = --Apple-Mail=_2F9D121E-66EF-4DC1-8930-3E2E5E50D2AA Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Hi Mike,

    I've been meaning to ask about this in the context of IPP Authentication Methods. Should we update IPP Authentication Methods with this before finishing it off? Or is WebAuthn outside the scope of IPP?

    Smith



    On Mar 4, 2019, at 10:43 AM, Michael Sweet via ipp <ipp@pwg.org> wrote:

    All,

    Haven't had a chance to see if this could at all be used with IPP, but WebAuthn is a new standard for authenticating without traditional passwords:

    https://www.w3.org/2019/03/pressrelease-webauthn-rec.html
    https://www.w3.org/TR/webauthn/

    See also the related FIDO2 project information:

    https://fidoalliance.org/fido2/

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

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

    --Apple-Mail=_2F9D121E-66EF-4DC1-8930-3E2E5E50D2AA-- --Apple-Mail=_F410F4D8-5A68-44F7-A82F-196A3E2C4454 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyKqq8ACgkQqskbKLDW 1N33Gg/+PTAM3GH9J3Cn5KJAc/LETB79rGd4X4GdoRLTzcpD31QWvWFrEN1wANLC CfaiYCzHbYdSRJjUINS7YsF9Y1fIX7FRB63slK6/xhwSDkbHFJpgUXmUOGWh/OxS 227i4mixAy2E+c88AvJnZdGIr9tJpdI2wsYgCO+0NkJtA4a2r4VhTFKdkGFaXIqr 1PAOKnUPA1hkMUYIw5tq6klOhY15AKOgJtyK9OPFVjWMpXYmbSNYQj5Uinhif4PX j7pKccEuS/DszmoWZ0Mi6j8YpV+zg2mf15XxvtDHx8vvKLlESAMggLTa3kiwb+sQ U4oweZHNU6tkLTX9Am5rgj87O5RbAF+Hm5efyBXH/otAFVjwIVnM9czVkpjAVqTL FiuPRQBHuu1MN7XJcC8UgVrsC1cCcZgCv+4wjszSs/k/ZBAaxXwzrRFpYJFY88/v cw+FiN+BIAwTBYvytfZnQCBl4/E8tDb5u1dLhLjBkNXeFRga9/trT4j39z+Dv0z/ uSQGAct1vpQ8yNrH0ugh/6BS9cSDjiui/pHf6XgnrxvGHQni2lqObBYIqaO3YXNm fs8zynOXqJTa+0lsrzywinJ/wXlHrv9KhmzJjDF1fmrANvO0bdNw47Z22ALcPI/h QgtL8dNFv6jiH5aKs03+DMSiSutfTQIcnUUrQwn/EU9ou4fht8w= =8N6L -----END PGP SIGNATURE----- --Apple-Mail=_F410F4D8-5A68-44F7-A82F-196A3E2C4454-- --===============3013234945686770974== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============3013234945686770974==-- From ipp-bounces@pwg.org Thu Mar 14 13:54:58 2019 Return-Path: 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 EA5D8130FF3 for ; Thu, 14 Mar 2019 13:54:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 dw2f5i-ElpaR for ; Thu, 14 Mar 2019 13:54:57 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 10AB2130F32 for ; Thu, 14 Mar 2019 13:54:56 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 337C03F9B; Thu, 14 Mar 2019 20:54:56 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id AEB1B266B; Thu, 14 Mar 2019 20:54:52 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 23D6B3B9E; Thu, 14 Mar 2019 20:54:51 +0000 (UTC) Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) by www.pwg.org (Postfix) with ESMTPS id B8F062618 for ; Thu, 14 Mar 2019 20:54:50 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2EKknWh022621; Thu, 14 Mar 2019 13:54:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=cnJid9k9k0AcdfDLhUSxc/ThcoFQ90hbORZJqk45TYA=; b=iyLePepWOO665q511QlFMKSyynPsQtNw5sd+SlGrvFswKAI3nI5Hrj3hhI9yp4gNON4M M+Btcj3e/DB/es3zVscUhp2fLI73ukfJGpLSKCJLigTlaNqBOzpsgIprKML+/4onPfOQ b2b7ve110/mBRg00ThXIy6PZplisUxJ9FXcsKq9l8S33HTWNS3EaxUitpwsmjbUUl7v3 TCEYijBD4efqbbOcdCz551eHn5Y0bjO3FWy4E4aayHaENIYBq0Y53f+fjJ78UdpOL6N5 iNSIPIrO9pjxMxlE+6nQWxYPDI/RqxrkPgRzD5SfsfYn3bWW4fjX1NylbGwEFxB6vDgh /w== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2r4da9wumj-8 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 14 Mar 2019 13:54:47 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POD002HLJF6JS30@ma1-mtap-s01.corp.apple.com>; Thu, 14 Mar 2019 13:54:45 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POD00A00J7J2Q00@nwk-mmpp-sz09.apple.com>; Thu, 14 Mar 2019 13:54:44 -0700 (PDT) X-Va-A: X-Va-T-CD: e144540b7342dfdd5f6898b05c7d1e1b X-Va-E-CD: 79ec9a540cd8bff85d63f4253aeca9fc X-Va-R-CD: d09b725416e5cf6c72a26e95059da46e X-Va-CD: 0 X-Va-ID: d5cd8bce-68e1-434c-b212-1f7eced2f4b0 X-V-A: X-V-T-CD: 499a24534fbaffe09fd540dd02388733 X-V-E-CD: 79ec9a540cd8bff85d63f4253aeca9fc X-V-R-CD: d09b725416e5cf6c72a26e95059da46e X-V-CD: 0 X-V-ID: 77647092-341f-4a7b-b2a9-c58486fe9256 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-14_11:,, signatures=0 Received: from [17.235.29.106] (unknown [17.235.29.106]) by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POD00L3FJF67600@nwk-mmpp-sz09.apple.com>; Thu, 14 Mar 2019 13:54:43 -0700 (PDT) In-reply-to: <9ACC7A03-291B-4107-9CF5-33A47C26AD62@hp.com> Date: Thu, 14 Mar 2019 16:54:34 -0400 Message-id: <2715B76C-5E2E-454E-8C19-A350483F5603@apple.com> References: <9ACC7A03-291B-4107-9CF5-33A47C26AD62@hp.com> To: Smith Kennedy X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-14_11:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] W3C Approves WebAuthn X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" Smith, This appears to be outside the scope, at least for now. I could see it being combined with OAuth 2 (like SAML), but until we can see where it goes I wouldn't want to put that in a best practices document... > On Mar 14, 2019, at 3:25 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp wrote: > > Hi Mike, > > I've been meaning to ask about this in the context of IPP Authentication Methods. Should we update IPP Authentication Methods with this before finishing it off? Or is WebAuthn outside the scope of IPP? > > Smith > > > >> On Mar 4, 2019, at 10:43 AM, Michael Sweet via ipp wrote: >> >> All, >> >> Haven't had a chance to see if this could at all be used with IPP, but WebAuthn is a new standard for authenticating without traditional passwords: >> >> https://www.w3.org/2019/03/pressrelease-webauthn-rec.html >> https://www.w3.org/TR/webauthn/ >> >> See also the related FIDO2 project information: >> >> https://fidoalliance.org/fido2/ >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Thu Mar 14 13:56:45 2019 Return-Path: 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 72FEE131038 for ; Thu, 14 Mar 2019 13:56:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, 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 2N5W9qKwKQoT for ; Thu, 14 Mar 2019 13:56:42 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id CF075130F32 for ; Thu, 14 Mar 2019 13:56:42 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 911063F4D; Thu, 14 Mar 2019 20:56:42 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 8A230266B; Thu, 14 Mar 2019 20:56:38 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 33D91266B; Thu, 14 Mar 2019 20:56:37 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 7B17D2618 for ; Thu, 14 Mar 2019 20:56:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1552596994; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=988oI5kZMOtFln4PV/4wYdXKRyBcuONSJBCbM324QZg=; b=TnQylFcBMEgiwkXzMR3EMXDJn9vaSLd6BwGVGVjLR44lVNRNgsl3nPptAUG5vNSQHikfh9c4FBCsZHi8JZKoIT3PGPnu/GrBj03WX6e0p+Drmb6V8rgaYMI4yAMsYT9nSWnxXzikMPY2j0E6yfKOkZLavgzTsWUyyEcSGAgyHEg= Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-co1nam04lp2056.outbound.protection.outlook.com [104.47.45.56]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-146-Em5nsVnHNTat9nwU1GMZjA-1; Thu, 14 Mar 2019 16:56:33 -0400 X-MC-Unique: Em5nsVnHNTat9nwU1GMZjA-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.14; Thu, 14 Mar 2019 20:56:31 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1709.011; Thu, 14 Mar 2019 20:56:31 +0000 To: Michael Sweet Thread-Topic: [IPP] W3C Approves WebAuthn Thread-Index: AQHU0rHsng+LBZHnPUmhFVFgct9RaaYLkgGAgAAY3ACAAACJgA== Date: Thu, 14 Mar 2019 20:56:31 +0000 Message-ID: <65CA7BDA-A6CF-4E7C-84CF-F0BCB33A51EE@hp.com> References: <9ACC7A03-291B-4107-9CF5-33A47C26AD62@hp.com> <2715B76C-5E2E-454E-8C19-A350483F5603@apple.com> In-Reply-To: <2715B76C-5E2E-454E-8C19-A350483F5603@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 598731f0-7594-4922-0da3-08d6a8bf8923 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1270; x-ms-traffictypediagnostic: CS1PR8401MB1270: x-microsoft-antispam-prvs: x-forefront-prvs: 09760A0505 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(396003)(136003)(346002)(366004)(39860400002)(376002)(189003)(6602003)(199004)(6246003)(102836004)(83716004)(26005)(966005)(14444005)(486006)(606006)(6506007)(2906002)(6306002)(256004)(53546011)(476003)(5660300002)(236005)(54896002)(2616005)(446003)(8936002)(68736007)(11346002)(6512007)(6486002)(76176011)(229853002)(66066001)(6436002)(6116002)(105586002)(186003)(97736004)(4326008)(81166006)(3846002)(81156014)(33656002)(71190400001)(36756003)(99286004)(53936002)(14454004)(478600001)(25786009)(316002)(82746002)(7736002)(6916009)(86362001)(106356001)(99936001)(71200400001)(8676002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1270; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 2/k61gJarISPag+vimiDerUBBc2zbHq9XmuQvN1H0Ng7uP18vgQx9V/oQSie6yl6ZuJNDZ6crb2ar7Zp6+46Fikq9yh9YGDCpF0EeVr4NEJm83ERTczMfv9UQbuoTsxNUgID4srpIzVHlZXSATQuSWB8KTszz9i3GEV2FFQA0P9RtdC0stw2SRTa5wxCcbFkosejZTqy9iKi9xOC2Eg9pydkuSPj+nlgiYWruItzobPvIQVmZXMkO+Ln5fnJaXJAG1zcRbNbcWyHJrAbqs0VNP+d0dcNNDTeiqqwnuMGHTJKjcyfpzXTyw3nLSMrhqhVXu6sB+j028PIkATb8+FbPdWDmz/4Go7gKUe+0ZMQ7UDxOcGsPHIUYOkLbSBgu1GWTuMv9JQXgk69xp5O0yh3ugXxZbxdIfGovBA0EHpcZmc= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 598731f0-7594-4922-0da3-08d6a8bf8923 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2019 20:56:31.0207 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1270 Cc: PWG IPP Workgroup Subject: Re: [IPP] W3C Approves WebAuthn X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8761390131127277769==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8761390131127277769== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_297E58AB-8751-4D06-AFE7-1865726B188D"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_297E58AB-8751-4D06-AFE7-1865726B188D Content-Type: multipart/alternative; boundary="Apple-Mail=_F98CDB2A-A90D-4641-AD67-026C001F07BE" --Apple-Mail=_F98CDB2A-A90D-4641-AD67-026C001F07BE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Good! =F0=9F=98=8A So we can move forward instead of waiting. Smith > On Mar 14, 2019, at 2:54 PM, Michael Sweet wrote: >=20 > Smith, >=20 > This appears to be outside the scope, at least for now. I could see it = being combined with OAuth 2 (like SAML), but until we can see where it = goes I wouldn't want to put that in a best practices document... >=20 >=20 > > On Mar 14, 2019, at 3:25 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp wrote: > > > > Hi Mike, > > > > I've been meaning to ask about this in the context of IPP = Authentication Methods. Should we update IPP Authentication Methods with = this before finishing it off? Or is WebAuthn outside the scope of IPP? > > > > Smith > > > > > > > >> On Mar 4, 2019, at 10:43 AM, Michael Sweet via ipp = wrote: > >> > >> All, > >> > >> Haven't had a chance to see if this could at all be used with IPP, = but WebAuthn is a new standard for authenticating without traditional = passwords: > >> > >> https://www.w3.org/2019/03/pressrelease-webauthn-rec.html = = > >> https://www.w3.org/TR/webauthn/ = = > >> > >> See also the related FIDO2 project information: > >> > >> https://fidoalliance.org/fido2/ = > >> > >> _________________________________________________________ > >> Michael Sweet, Senior Printing System Engineer > >> > >> _______________________________________________ > >> ipp mailing list > >> ipp@pwg.org > >> https://www.pwg.org/mailman/listinfo/ipp = > > > > _______________________________________________ > > ipp mailing list > > ipp@pwg.org > > https://www.pwg.org/mailman/listinfo/ipp = >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer --Apple-Mail=_F98CDB2A-A90D-4641-AD67-026C001F07BE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Good!= =F0=9F=98=8A So we can move forward instead of waiting.

    Smith



    On Mar 14, 2019, at 2:54 PM, Michael Sweet <msweet@apple.com> = wrote:

    Smith,

    This appears to be outside the scope, at least for now. I could see it = being combined with OAuth 2 (like SAML), but until we can see where it = goes I wouldn't want to put that in a best practices document...


    > On Mar 14, 2019, at 3:25 PM, Kennedy, Smith (Wireless & = Standards Architect) via ipp <ipp@pwg.org> wrote:
    >
    > Hi Mike,
    >
    > I've been meaning to ask about this in the context of IPP = Authentication Methods. Should we update IPP Authentication Methods with = this before finishing it off? Or is WebAuthn outside the scope of = IPP?
    >
    > Smith
    >
    >
    >
    >> On Mar 4, 2019, at 10:43 AM, Michael Sweet via ipp <ipp@pwg.org> wrote:
    >>
    >> All,
    >>
    >> Haven't had a chance to see if this could at all be used with = IPP, but WebAuthn is a new standard for authenticating without = traditional passwords:
    >>
    >> https://www.w3.org/2019/03/pressrelease-webauthn-rec.html >> https://www.w3.org/TR/webauthn/
    >>
    >> See also the related FIDO2 project information:
    >>
    >> https://fidoalliance.org/fido2/
    >>
    >> _________________________________________________________
    >> Michael Sweet, Senior Printing System Engineer
    >>
    >> _______________________________________________
    >> ipp mailing list
    >> ipp@pwg.org
    >> https://www.pwg.org/mailman/listinfo/ipp
    >
    > _______________________________________________
    > ipp mailing list
    > ipp@pwg.org
    > https://www.pwg.org/mailman/listinfo/ipp

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    = --Apple-Mail=_F98CDB2A-A90D-4641-AD67-026C001F07BE-- --Apple-Mail=_297E58AB-8751-4D06-AFE7-1865726B188D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyKv/0ACgkQqskbKLDW 1N0LqA/8Dp/WSyIJqPA7DTFcfZyM/MVeCb1vw8N6SbLohhMEF3hTE9vvfdo52kSF z6nxpNBkJDvW4JmOSsig0LoBuSKRTWpR8cKgg1a9TS9fi+saEvXOzZWxpinRlI6o LARYNtj7/9jpyiYgQfbJCt5liygD8293c7O6GexHLBm/I0DYdfQSAniuu+ZM8RsX 1/WEJ7SO1ZmzKIZFNgoff/b+AqdGpy4EpKE/OI2N6Jd6EPKM2k2iaUMlm1/CA+LY 0nE6wiL4/bt43arZLGNQq0we0RiYB6GyIz47gmEYHTO6Y/wVBKbzu02jtB/XnE3x ee2/SMh8BfH1uoUNUfeau3BNV/putw7J1x0m2gctykFMG0mfMYJboFxCQoxRYTJK avEjL0hQG49J1utwJw2zDjNEGlnL6kEtYOvZcFVB48Onyl7BjYtIbJ0EMjjgmXw6 xEOW7vyFjtjDI88WZIkRu2zhd97faMeEywgGv9RfGkq2n2xddBox20VumyaeoydQ xsBJfYlWirVT+KDCatbqFFT62cCU8Buc0h04PT7ES+ChbOf6CcgUo77/LDzKkEcZ 3gacaggIbaOYfNiPMqjYPvoX9RsAh9/voWJsOORBG8iQZ8I+BVNOpQgVQbmuL/pc uPPMVAMv7BS0mYXwaQ0uwI6WnPl/UNsbmIWgmy5IbJ4M0X815ko= =LLMk -----END PGP SIGNATURE----- --Apple-Mail=_297E58AB-8751-4D06-AFE7-1865726B188D-- --===============8761390131127277769== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8761390131127277769==-- From ipp-bounces@pwg.org Fri Mar 15 06:22:01 2019 Return-Path: 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 E0789131280 for ; Fri, 15 Mar 2019 06:22:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 Ri1h0ojawP5j for ; Fri, 15 Mar 2019 06:22:00 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 0A329131272 for ; Fri, 15 Mar 2019 06:21:59 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 8372D3F9B; Fri, 15 Mar 2019 13:21:59 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id EF05C23E3; Fri, 15 Mar 2019 13:21:55 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 879553BA9; Fri, 15 Mar 2019 13:21:54 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id 00BD02618 for ; Fri, 15 Mar 2019 13:21:53 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FDGjRx044635 for ; Fri, 15 Mar 2019 06:21:53 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=zZ8fkg8Ljta0UHVwsVbTC1/VeJHH19GRozlSxi9j7vA=; b=sr+kNi+BQiMe65UW3a5UqKVgWL3xhn4dSuhx6gXWaeuFj1y9j1dNhZ64zJboPlFwkpgy 3kJMkpgfKFtY95kYhqlWuP1xSPvgtiw07dS3HNnbnFw0Q+2p6bcMiFSXznwQIOpt/4jl vPu97ltEKelXqy9Ot1RfAbcbm5yJ8sxrZYwiSZNcp0f7nOVY2XGDtnqH5jjj/7B7vMYN S1lmBNrHjj0ncE4OxOL+3bmq+alnsPxsLbbuzAJLhWcSBqMIDdj92BkOI1m3t9cL5Ylh TZJskudaIHAFrMgeBr/FQdn9aZXZ4eRP/ah5/6mdYWbMhk4A+CrDcmI+1deXuFJEogTr aA== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2r4d1d8yjg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 15 Mar 2019 06:21:53 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POE0014RT4G7650@mr2-mtap-s01.rno.apple.com> for ipp@pwg.org; Fri, 15 Mar 2019 06:21:52 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POE00F00SUE3K00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:21:52 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 44017dd867b90dec783889eb4644055b X-Va-R-CD: 827fb2aa8ee5943ffb39d82b989b2bee X-Va-CD: 0 X-Va-ID: 7dad8c06-5bc8-411f-b766-19ebadf5aef0 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 44017dd867b90dec783889eb4644055b X-V-R-CD: 827fb2aa8ee5943ffb39d82b989b2bee X-V-CD: 0 X-V-ID: 758d5eb3-5500-49af-8360-90aff13c31ea X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_09:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POE00EFRT4EEP90@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:21:52 -0700 (PDT) Date: Fri, 15 Mar 2019 09:21:49 -0400 Message-id: <2E159866-6DD6-40F0-92FD-4035F1F670BF@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_09:, , signatures=0 Subject: [IPP] Minutes from yesterday's concall posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted the minutes from yesterday's IPP workgroup conference call to: https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20190314.pdf Our next conference call is on March 28, 2019 at 3pm ET. Many thanks to Smith for taking the minutes this week! _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Mar 15 06:53:17 2019 Return-Path: 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 671AE129441 for ; Fri, 15 Mar 2019 06:53:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 UKKBQ764W5B6 for ; Fri, 15 Mar 2019 06:53:15 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 28246129AA0 for ; Fri, 15 Mar 2019 06:53:15 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 6379D3F52; Fri, 15 Mar 2019 13:53:14 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id D80922894; Fri, 15 Mar 2019 13:53:09 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id D7CEF3BA9; Fri, 15 Mar 2019 13:53:08 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id 116BD23E3 for ; Fri, 15 Mar 2019 13:53:07 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FDlJdT031259 for ; Fri, 15 Mar 2019 06:53:07 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : content-transfer-encoding : date : subject : message-id : to; s=20180706; bh=UA+eiXLDAGnPbD3k/IxBvAAZt6CIJA4xP7+0q5ouqF4=; b=o2QTwrWzm3MhQ+lxYYx4nk6WBZHWgXPgXEUHeHaI2GzbGRtdlm2VTupwUBENB/jf4C8k 3zwH1BNr78PepJbGyIojRJ8wPP9pX3id0SIazo59rqA6OAwmKEllFAJ0IMSaeTI0d2bs JXFByqeDHB4HPHZbWnZSdYyxcQ7N5yUvcKhDn3dctc3b9Br4JmACCOMSqOu4y0T+chd8 nD1YVbbNueKw+Q9KXRALUvk5Cawn0UU3Dm9ObhGgndE+sl5Lbij5DeRy+eFkmtaYiJgU 0pnyW/vQ3vzf72CUehHMIpO/aRwqE48MXAXceny7BhJKHcjgVvngCsozyK2zssidiz4B Rg== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2r4b24mc5s-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 15 Mar 2019 06:53:07 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POE00MMUUKIM900@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Fri, 15 Mar 2019 06:53:06 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POE00F00UFF2100@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:53:06 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: f70c7fa98dae15940f4a859b1f6b069b X-Va-R-CD: 296324b8c7689ca990e7d5815c3aa9f3 X-Va-CD: 0 X-Va-ID: 916ba86b-ccf4-4cff-ab69-cf4c95e56591 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: f70c7fa98dae15940f4a859b1f6b069b X-V-R-CD: 296324b8c7689ca990e7d5815c3aa9f3 X-V-CD: 0 X-V-ID: f295dc57-e4ca-499f-8fe8-137d4945ebda X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_09:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POE00L0BUKGUB00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:53:06 -0700 (PDT) Date: Fri, 15 Mar 2019 09:53:03 -0400 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_09:, , signatures=0 Subject: [IPP] RFC: Relationship between job-retain-until-xxx and job-password X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ipp-bounces@pwg.org Sender: "ipp" QWxsLAoKSW4gcmV2aWV3aW5nIHRoZSBtaW51dGVzIGZyb20geWVzdGVyZGF5J3MgY29uY2FsbCwg SSBzYXcgdGhlIGZvbGxvd2luZyBzdW1tYXJ5IG9mIGRpc2N1c3Npb25zIHJlZ2FyZGluZyBqb2It cGFzc3dvcmQgYW5kIGpvYi1yZXRhaW4tdW50aWwteHh4IGluIHRoZSBuZXcgSVBQIEVudGVycHJp c2UgUHJpbnRpbmcgRXh0ZW5zaW9uczoKCgnigKIgZGlzY3Vzc2VkIGpvYi1yZXRhaW4tdW50aWwg YW5kIGpvYi1yZXRhaW4tdW50aWwtdGltZSBhbmQgam9iLXJldGFpbi11bnRpbC1kYXRlCgkJ4oCi IGNvbnNlbnN1cyB3YXMgdG8ga2VlcCBqb2ItcmV0YWluLXVudGlsICh0eXBlMiBrZXl3b3JkKSBh bmQgam9iLXJldGFpbi11bnRpbC1kYXRlIChkYXRlVGltZSkKCQkJ4oCiIFNlbWFudGljcyBmb3Ig am9iLXJldGFpbi11bnRpbC10aW1lIGNvdWxkIGJlIHNwZWNpZmllZCB0aGF0IHRoZSBpbnRlZ2Vy IGlzIHRoZSBudW1iZXIgb2Ygc2Vjb25kcywgZXRjLiBvbmNlIGl0IGhhcyBlbnRlcmVkIGl0cyB0 ZXJtaW5hbCBzdGF0ZSAoZS5nLiBjYWxjdWxhdGVkIGFzICJkYXRlLXRpbWUtYXQtY29tcGxldGVk IiArICJqb2ItcmV0YWluLXVudGlsLXRpbWUiKS4KCQkJ4oCiIHdoYXQgdG8gZG8gYWJvdXQgImpv Yi1wYXNzd29yZCIgSm9icyB0aGF0IHRoZSBKb2IgaXNuJ3QgYSBSZXRhaW5lZCBKb2IKCeKAoiAi am9iLXBhc3N3b3JkIiBzaG91bGQgYmUgZGlzYWxsb3dlZCB3aGVuICJqb2ItcmV0YWluLXVudGls IiBvciAiam9iLXJldGFpbi11bnRpbC10aW1lIiBhcmUgc3BlY2lmaWVkCgnigKIgbWF5YmUgdGhl IGJldHRlciByZWNvbW1lbmRhdGlvbiBmb3IgYSAic2VjdXJlIHByaW50IiB0aGF0IGRvZXNuJ3Qg Z2V0IGFnZWQgb3V0IGlzIHRvIHVzZSAiam9iLXByaW50LXBhc3N3b3JkIiBhbmQgaGF2ZSBpdCBi ZSAic2F2ZS1vbmx5Ij8KCQnigKIgU2hvdWxkIHRoZXJlIGJlIGFkZGl0aW9uYWwgZGlzcG9zaXRp b25zPwoKU29tZSBvZiBteSBvd24gdGhvdWdodHM6CgoxLiBJIHRob3VnaHQgdGhlIGNvbnNlbnN1 cyB3YXMgdG8gcHV0IGpvYi1yZXRhaW4tdW50aWwteHh4IGluIEpPQkVYVD8gVGhleSBhcmUgZGVm aW5lZCBpbiB0aGUgY3VycmVudCBkcmFmdCBvZiBKT0JFWFQuLi4KCjIuIE15IGlzc3VlIHdpdGgg anVzdCBoYXZpbmcgam9iLXJldGFpbi11bnRpbC10aW1lIChkYXRlVGltZSkgaXMgdGhhdCB0aGVy ZSBpcyBubyB3YXkgKHNob3J0IG9mIGRlZmluaW5nIGtleXdvcmQvbmFtZSB2YWx1ZXMgZm9yIGpv Yi1yZXRhaW4tdW50aWwpIHRvIHNheSAiYnkgZGVmYXVsdCwgcmV0YWluIGFsbCBqb2JzIGZvciBh IHllYXIiLiAgRm9yIGV4YW1wbGUsIENVUFMgY2FuIGJlIGNvbmZpZ3VyZWQgdG8gcmV0YWluIGpv YnMgKCJQcmVzZXJ2ZUpvYkZpbGVzIikgaW5kZWZpbml0ZWx5LCBub3QgYXQgYWxsLCBvciBmb3Ig YSBzcGVjaWZpZWQgbnVtYmVyIG9mIHNlY29uZHMgYWZ0ZXIgY29tcGxldGlvbi4gIFRoZXJlIGlz IG5vICJyZXRhaW4gdW50aWwgZGF0ZS90aW1lIiBmdW5jdGlvbmFsaXR5IGJlY2F1c2Ugd2UndmUg bmV2ZXIgbmVlZGVkIGl0IGluIENVUFMsIGJ1dCBJIGNhbiBzZWUgYSBwb3RlbnRpYWwgbmVlZCBm b3IgbGVnYWwgZG9jdW1lbnRzL2pvYnMgdGhhdCAiZXhwaXJlIiBhZnRlciBhIHNwZWNpZmljIGRh dGUgYW5kIHRpbWUuCgogIFRMO0RSOiBJZiB3ZSBnZXQgcmlkIG9mIGFueXRoaW5nIGl0IHNob3Vs ZCBiZSAiam9iLXJldGFpbi11bnRpbC10aW1lIChkYXRlVGltZSkiIGFuZCAqbm90KgogICJqb2It cmV0YWluLXVudGlsLWludGVydmFsIChpbnRlZ2VyKDA6TUFYKSkiLgoKMy4gQXMgZm9yIGpvYi1w YXNzd29yZCBub3QgYmVpbmcgY29tcGF0aWJsZSB3aXRoIGpvYi1yZXRhaW4tdW50aWwteHh4LCB3 aHk/ICJqb2ItcGFzc3dvcmQiIGp1c3QgaG9sZHMgdGhlIGpvYiB1bnRpbCB0aGUgVXNlciBlbnRl cnMgdGhlIHBhc3N3b3JkL2NvZGUgYXQgdGhlIHByaW50ZXIgLSB0aGUgc2VtYW50aWNzIG9mIHJl dGFpbmluZyBhIGpvYiBkb24ndCBraWNrIGluIHVudGlsIHRoZSBqb2IgcmVhY2hlcyBhIHRlcm1p bmF0aW5nIHN0YXRlLCBhbmQgUElOIHByaW50aW5nIHdpbGwgbGlrZWx5IGhhdmUgdGhlIHNhbWUg bGVnYWwgcmVxdWlyZW1lbnRzIFdSVCBkb2N1bWVudCByZXRlbnRpb24gYXMgYW55IG90aGVyIGtp bmQgb2YgcHJpbnRpbmcuCgo0LiBXUlQgImpvYi1wcmludC1wYXNzd29yZCIsIHdoYXQgaWYgKGFu ZCBJIGhhdmVuJ3QgdGhvdWdodCB0aGlzIGNvbXBsZXRlbHkgdGhyb3VnaCB5ZXQpIHdlIGRlZmlu ZSBhbm90aGVyIHBhcmFsbGVsIGF0dHJpYnV0ZSwgImpvYi1wYXNzd29yZC1hY3Rpb24gKHR5cGUy IGtleXdvcmQpIiB0aGF0IGRlZmluZXMgdGhlIHNlbWFudGljcyBvZiB0aGUgImpvYi1wYXNzd29y ZCIgYXR0cmlidXRlLCB3aXRoIHRoZSBkZWZhdWx0IGJlaW5nICJob2xkLWpvYiIgdG8gcHJlc2Vy dmUgdGhlIDEuMCBzZW1hbnRpY3MuIFNvbWV0aGluZyBsaWtlOgoKam9iLXBhc3N3b3JkLWFjdGlv biAodHlwZTIga2V5d29yZCkKClRoaXMgb3BlcmF0aW9uIGF0dHJpYnV0ZSBzcGVjaWZpZXMgaG93 IGEgSm9iIGlzIHByb2Nlc3NlZCB3aGVuIHRoZSAiam9iLXBhc3N3b3JkIiAoc2VjdGlvbiBOLk0u UCkgb3BlcmF0aW9uIGF0dHJpYnV0ZSBpcyBpbmNsdWRlZCBpbiBhIEpvYiBDcmVhdGlvbiByZXF1 ZXN0LiAgU3RhbmRhcmQga2V5d29yZCB2YWx1ZXMgaW5jbHVkZToKCi0gJ2hvbGQtam9iJzogVGhl IEpvYiBpcyBwbGFjZWQgaW4gdGhlICdwZW5kaW5nLWhlbGQnIHN0YXRlIGFuZCBpcyByZWxlYXNl ZCB3aGVuIHRoZSAiam9iLXBhc3N3b3JkIiB2YWx1ZSBpcyBlbnRlcmVkIGF0IHRoZSBQcmludGVy J3MgY29uc29sZS4KLSAncHJvY2Vzcy1hbmQtcmV0YWluJzogVGhlIEpvYiBpcyBwbGFjZWQgaW4g dGhlICdwZW5kaW5nJyBzdGF0ZSBhbmQgaXQgc2NoZWR1bGVkIGZvciBwcm9jZXNzaW5nIHdpdGhv dXQgd2FpdGluZyBmb3IgdGhlIFVzZXIgdG8gZW50ZXIgdGhlICJqb2ItcGFzc3dvcmQiIHZhbHVl IGF0IHRoZSBQcmludGVyJ3MgY29uc29sZS4KLSAncmV0YWluLW9ubHknOiBUaGUgSm9iIGlzIHBs YWNlZCBpbiB0aGUgJ2NvbXBsZXRlZCcgc3RhdGUgYXMgc29vbiBhcyBhbGwgRG9jdW1lbnRzIGFy ZSByZWNlaXZlZCBieSB0aGUgUHJpbnRlci4KCk9uY2UgaW4gYSB0ZXJtaW5hdGluZyBzdGF0ZSwg dGhlIEpvYiBpcyByZXRhaW5lZCBhY2NvcmRpbmcgdG8gdGhlIGN1cnJlbnQgdmFsdWUgb2YgaXRz ICJqb2ItcmV0YWluLXVudGlsLXh4eCIgYXR0cmlidXRlcy4KCjUuIEFsc28gV1JUICJqb2ItcHJp bnQtcGFzc3dvcmQiLCBpZiB3ZSBhZG9wdCAiam9iLXByaW50LWFjdGlvbiIgdGhlbiB3ZSBjYW4g YW1lbmQgdGhlIHNlbWFudGljcyBvZiAiUmVzdWJtaXQtSm9iIiB0byByZXF1aXJlIHRoZSBvcmln aW5hbCAiam9iLXBhc3N3b3JkIiB2YWx1ZSB0byBnZXQgYm90aCB0aGUgZGVzaXJlZCByZXByaW50 IGJlaGF2aW9yICphbmQqIGJldHRlciBzdXBwb3J0IHRoZSBzZWN1cml0eSBjaGFyYWN0ZXJpc3Rp Y3MgaW1wbGllZCBieSAiam9iLXBhc3N3b3JkIi4KClRob3VnaHRzPwoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pY2hhZWwgU3dlZXQs IFNlbmlvciBQcmludGluZyBTeXN0ZW0gRW5naW5lZXIKCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fCmlwcCBtYWlsaW5nIGxpc3QKaXBwQHB3Zy5vcmcKaHR0 cHM6Ly93d3cucHdnLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwcAo= From ipp-bounces@pwg.org Fri Mar 15 06:57:08 2019 Return-Path: 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 920D712D826 for ; Fri, 15 Mar 2019 06:57:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 cZYICJkYb_f9 for ; Fri, 15 Mar 2019 06:57:06 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id A2DF512D4E9 for ; Fri, 15 Mar 2019 06:57:06 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 250CC3F4E; Fri, 15 Mar 2019 13:57:06 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id CBF142894; Fri, 15 Mar 2019 13:57:01 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 42DC93BA9; Fri, 15 Mar 2019 13:57:00 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id D069D3F5 for ; Fri, 15 Mar 2019 13:56:59 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FDlH2g031072 for ; Fri, 15 Mar 2019 06:56:59 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : content-transfer-encoding : date : subject : message-id : to; s=20180706; bh=FxsZS6pHiepVJEoj0b3iipJfHR8OIzEgGwUWNfAOEBM=; b=n3eSLbK6E/O7Q605xIs+9qxCqpHfmOok4fo4WVlnf9nMoJPa7BpOc9azf9o7U+4NgRHq B7o1FvCh4wMw3INpWbjOtvXD4b+30ugDU4POE7jWJj5mWYL5B8lIhdrE8VSgKNr0NDvP k58+YVG5/5TYrzNHGKC6fAMzDPUjULj/rVWnzevgvDz+hnJB6dp/GLsagzercnxtF1Hc W9x8tkiPsKqdMS7N7H+OuABLc/DlTAj4509lpMuH0edo2/xGLZCbs0W2NnlFWYdUlG6J LIPFwnpARRmf+f9/qU1omppomcBkKfsTjdCA9KTGEsV67mUrCLh/R25pv0rvLaek6jwO tw== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2r4b24mebr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 15 Mar 2019 06:56:59 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POE00MD4UQYM930@ma1-mtap-s01.corp.apple.com> for ipp@pwg.org; Fri, 15 Mar 2019 06:56:59 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POE00F00UFF2100@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:56:58 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 9f69385cfca2cf543d3e6b97c3876f69 X-Va-R-CD: 1baf2e4d49c88da026122c26493ac241 X-Va-CD: 0 X-Va-ID: 07bc81e9-a272-448f-994c-382c9a027a6d X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 9f69385cfca2cf543d3e6b97c3876f69 X-V-R-CD: 1baf2e4d49c88da026122c26493ac241 X-V-CD: 0 X-V-ID: 928c2e65-730a-49a7-902c-29bea67f58ff X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_09:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POE00L54UQWUB00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 06:56:58 -0700 (PDT) Date: Fri, 15 Mar 2019 09:56:56 -0400 Message-id: <3878F207-378B-4628-878F-14E80CE38E62@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_09:, , signatures=0 Subject: [IPP] RFC: IPP Document Object update version X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ipp-bounces@pwg.org Sender: "ipp" QWxsLAoKSW4gcmV2aWV3aW5nIHRoZSBtaW51dGVzIGZyb20geWVzdGVyZGF5J3MgSVBQIGNvbmNh bGwgSSBzYXcgdGhlIGZvbGxvd2luZyBjb21tZW50cyByZWdhcmRpbmcgdGhlIElQUCBEb2N1bWVu dCBPYmplY3QgdjEuMSBlcnJhdGEgdXBkYXRlOgoK4oCiIFByb3RvdHlwaW5nIGdvaW5nIG9uCgog IEkgYmVsaWV2ZSB0aGlzIGlzIGFjdHVhbGx5IGNvbXBsZXRlIGluIGlwcHNlcnZlciwgYW5kIHRo ZXJlIGFyZSBvZiBjb3Vyc2UgYSBMT1Qgb2YgSVBQIChQREYpIHByaW50ZXJzIHdpdGggZG9jdW1l bnQgb2JqZWN0IHN1cHBvcnQgYWxyZWFkeSwgc28gSSB0aGluayBhbnkgcHJvdG90eXBpbmcgcmVx dWlyZW1lbnQgaGFzIGJlZW4gbWV0LiAobm90IHRoYXQgdGhlcmUgaXMgb25lIGZvciBhbiBlcnJh dGEgdXBkYXRlKQoK4oCiIE5lZWQgdG8gYWRkICJEZXByZWNhdGVkIiBhbmQgIk9ic29sZXRlIiBk ZWZpbml0aW9ucwoKICBUaGVzZSB3aWxsIGJlIGluY2x1ZGVkIGluIHRoZSBuZXh0IChzdGFibGUp IHVwZGF0ZSwgcGVyIG91ciBwcmlvciBkaXNjdXNzaW9ucy4KCuKAoiBXaWxsIGJlIFBXRyBDYWxs IGZvciBPYmplY3Rpb25zIGJlY2F1c2UgaXQgaXMgYSAxLjEgKGVycmF0YSB1cGRhdGUpIGJ1dCBz aG91bGQgaXQgYmUgYSAyLjA/CgogIEdpdmVuIHRoYXQgdGhlcmUgaXMgTk9USElORyBORVcgaW4g dGhpcyBzcGVjLCBqdXN0IGEgZ2VuZXJhbCBjbGVhbnVwIGFuZCBhIHJlbGF4YXRpb24gb2YgdGhl IG11bHRpcGxlIGRvY3VtZW50IHN1cHBvcnQgcmVxdWlyZW1lbnQsIEkgc2VlIG5vIHJlYXNvbiB0 byBtYWtlIHRoaXMgMi4wLiBBbnkgMS4wIGNvbXBsaWFudCBpbXBsZW1lbnRhdGlvbiBpcyBhbHNv IDEuMSBjb21wbGlhbnQuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KTWljaGFlbCBTd2VldCwgU2VuaW9yIFByaW50aW5nIFN5c3RlbSBF bmdpbmVlcgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K aXBwIG1haWxpbmcgbGlzdAppcHBAcHdnLm9yZwpodHRwczovL3d3dy5wd2cub3JnL21haWxtYW4v bGlzdGluZm8vaXBwCg== From ipp-bounces@pwg.org Fri Mar 15 07:41:50 2019 Return-Path: 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 43F6B130DE3 for ; Fri, 15 Mar 2019 07:41:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 7Ex9Wy6rxjSK for ; Fri, 15 Mar 2019 07:41:46 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 99075130EAA for ; Fri, 15 Mar 2019 07:41:46 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id F39653F4F; Fri, 15 Mar 2019 14:41:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 5DACC2894; Fri, 15 Mar 2019 14:41:41 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 65C7B3BA9; Fri, 15 Mar 2019 14:41:39 +0000 (UTC) Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by www.pwg.org (Postfix) with ESMTPS id 7F9EC2618 for ; Fri, 15 Mar 2019 14:41:38 +0000 (UTC) Received: by mail-yw1-xc29.google.com with SMTP id 189so7429621ywi.3 for ; Fri, 15 Mar 2019 07:41:38 -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=7WIWGrcr3yWYI9LLDX3jYtlyFWBhvuPjR5Zx9bJqgn0=; b=h9dCKeGgVIk7s8otuMs7MUeuFYYRZRQ+mxndEFGnf9OKqMRWMgfvPqybcGaJC2Av8c lmdUp7zaludchl/1KV8E21BmokAgsA3FUIuzgD6YzxSB+7yZJio/nkCHGS4La7w5B+mi ZmgaVMaGlkCnVS8u6DB0hzyRQ5C751MwWUxlxvC0c9Ps3vD/9eV+bg0/XLGFbLJBAOnn jze/oCWiAu61/YIUe0OHdl6lGP0JeJq2bnVgusbQ/ezCWdQHdeUIXG3TXeJHVkDcl60Q qro2mstOSMMqKI5TFeQL3vX04zxkrBfJhvWzJPuhSjJFqPpUMNpbXUj8ZbWnHgsuADqF iG4A== 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=7WIWGrcr3yWYI9LLDX3jYtlyFWBhvuPjR5Zx9bJqgn0=; b=Dh90y8HZAFXu77jxz+SsDKDRH5nPbxVdNPVRLCHbaVeuiElGN4qRAoLXqxiVbzf7qQ L2ElEjJvjoFlbQiQ//xfK3bQhLnnEc+HJIuLjoVuMVFeP17X43+lOnL9ceigoeTJ+InM z+5g4QfTryzV3OjRIp2NNpGnnUfSsySiN86zvGafUqbeZd2CL/FEtO6f22lQKTL1lNjQ 4X3CJ2bWlpkSnwAfyW/Z8iE7JggR3VHHqs/nWNEoHOYxhugKGXa4uB8rWDfP8mQkdcbx yHY0Nx4z2OkQ7Nwl+VREwOfrnB8/8cmzNUbDYcGPF1r5VIlAdsjetaS+0BaSQrtc9J4d xX4Q== X-Gm-Message-State: APjAAAULlqzpsmy2hfT+1Z0YtlFdw3Ewcx4o/4BfAxGhdlyBvc7QwDZq tPpDHb2eqI/EXcGYKr8A1Q98aCRdXoJNKJJtxmM= X-Google-Smtp-Source: APXvYqxZxOTNZLJok9Hxqztds6hVCfaEm8EmMGrKuYe3Xs8uqAetC49Luvhzi/ayg+SeAJ5NDhuUje2izApFF93Bp0c= X-Received: by 2002:a0d:c9c2:: with SMTP id l185mr3170914ywd.227.1552660897589; Fri, 15 Mar 2019 07:41:37 -0700 (PDT) MIME-Version: 1.0 References: <3878F207-378B-4628-878F-14E80CE38E62@apple.com> In-Reply-To: <3878F207-378B-4628-878F-14E80CE38E62@apple.com> Date: Fri, 15 Mar 2019 10:41:25 -0400 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: IPP Document Object update version X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6342514228783679436==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6342514228783679436== Content-Type: multipart/alternative; boundary="00000000000041ecc8058423095e" --00000000000041ecc8058423095e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mike, I agree with your rationale that Document Object should be v1.1 (no new content). For Job Extensions (because of adding three operations, especially), I think and the folks yesterday on IPP WG call agreed that v2.0 was preferable. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Mar 15, 2019 at 9:57 AM Michael Sweet via ipp wrote: > All, > > In reviewing the minutes from yesterday's IPP concall I saw the following > comments regarding the IPP Document Object v1.1 errata update: > > =E2=80=A2 Prototyping going on > > I believe this is actually complete in ippserver, and there are of > course a LOT of IPP (PDF) printers with document object support already, = so > I think any prototyping requirement has been met. (not that there is one > for an errata update) > > =E2=80=A2 Need to add "Deprecated" and "Obsolete" definitions > > These will be included in the next (stable) update, per our prior > discussions. > > =E2=80=A2 Will be PWG Call for Objections because it is a 1.1 (errata upd= ate) but > should it be a 2.0? > > Given that there is NOTHING NEW in this spec, just a general cleanup an= d > a relaxation of the multiple document support requirement, I see no reaso= n > to make this 2.0. Any 1.0 compliant implementation is also 1.1 compliant. > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --00000000000041ecc8058423095e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    I agree with your r= ationale that Document Object should be v1.1 (no new content).
    For Job Extensions (because of adding three operations, especi= ally), I think and
    the folks yesterday on IPP WG call agreed that= v2.0 was preferable.

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Arch= itect)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair -= TCG Metadata Access Protocol SG
    Chair - Linux Fo= undation Open Printing WG
    Secretary - IEEE-ISTO Printer Working GroupCo-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
    <= a style=3D"color:rgb(102,0,204)" href=3D"http://sites.google.com/site/highn= orthinc" target=3D"_blank">http://sites.google.com/site/highnorthincmailto: bluer= oofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906= -494-2434


    On Fri, Mar 15, 2019 at 9:57 AM Michael Sweet via ipp <ipp@pwg.org> wrote:
    All,

    In reviewing the minutes from yesterday's IPP concall I saw the followi= ng comments regarding the IPP Document Object v1.1 errata update:

    =E2=80=A2 Prototyping going on

    =C2=A0 I believe this is actually complete in ippserver, and there are of c= ourse a LOT of IPP (PDF) printers with document object support already, so = I think any prototyping requirement has been met. (not that there is one fo= r an errata update)

    =E2=80=A2 Need to add "Deprecated" and "Obsolete" defin= itions

    =C2=A0 These will be included in the next (stable) update, per our prior di= scussions.

    =E2=80=A2 Will be PWG Call for Objections because it is a 1.1 (errata updat= e) but should it be a 2.0?

    =C2=A0 Given that there is NOTHING NEW in this spec, just a general cleanup= and a relaxation of the multiple document support requirement, I see no re= ason to make this 2.0. Any 1.0 compliant implementation is also 1.1 complia= nt.

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --00000000000041ecc8058423095e-- --===============6342514228783679436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6342514228783679436==-- From ipp-bounces@pwg.org Fri Mar 15 08:01:57 2019 Return-Path: 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 ABF01130DE6 for ; Fri, 15 Mar 2019 08:01:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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=apple.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 ZBg7QqwsQaLl for ; Fri, 15 Mar 2019 08:01:55 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 86DA3130DE3 for ; Fri, 15 Mar 2019 08:01:55 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 37A8A3F47; Fri, 15 Mar 2019 15:01:55 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id D70FE2894; Fri, 15 Mar 2019 15:01:49 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id AF00323E3; Fri, 15 Mar 2019 15:01:48 +0000 (UTC) Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) by www.pwg.org (Postfix) with ESMTPS id ED06F23E3 for ; Fri, 15 Mar 2019 15:01:47 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FEuxlW023470; Fri, 15 Mar 2019 08:01:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=rJdweRcIeN6OzF1aYT4EeSQIlK+IPk5cLA7rnB8j4J4=; b=PE4YKtUj3gepN1urV79G72pJwh+KzO01KQeOAOHvvn1DjXhmoGUXfC6/rFFt/xjjxi8J RfBvBv7O82aVPtTQ2rMLgcnxTraA8cZ5IeNkbMrC/klk30Ercno8qxZf7F4JR3mCvtLT Vr2SmHjdy756rP0bO8anps7Z6lTp/OQ0d1K6C+QURL9l//pb20Jz51H5yFxEoXuQkgpC zNY21XCvDJ3vP8kRpoENDbvCETPhIItZo0NbvY2r9M1a/KbWG4bgIwcnw706LJSN1cqC ogVjjtljFleHjXQp9N4Ck+LcVH41rm45EG3wTf5uvVIuZg4ve9egS6ZDux7FBD8Ej0ua Iw== Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2r4x155x6k-25 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 15 Mar 2019 08:01:47 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POE008KDXQWTV20@ma1-mtap-s02.corp.apple.com>; Fri, 15 Mar 2019 08:01:46 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POE00800XIMJT00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 08:01:45 -0700 (PDT) X-Va-A: X-Va-T-CD: 670a24ae296eaf6dc00d9725bda32b87 X-Va-E-CD: 60923d9333ce17015c3b284177d9b948 X-Va-R-CD: 3047c2b0988263c2e0f473e5544645f0 X-Va-CD: 0 X-Va-ID: b2db7076-c0dd-4a69-ae56-cf7c0fba92d6 X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: 60923d9333ce17015c3b284177d9b948 X-V-R-CD: 3047c2b0988263c2e0f473e5544645f0 X-V-CD: 0 X-V-ID: 272e3223-a6c8-4894-aa4a-e0976c8232c5 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_10:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POE00LPWXQBUB20@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 08:01:25 -0700 (PDT) In-reply-to: Date: Fri, 15 Mar 2019 11:01:23 -0400 Message-id: <1032EA80-9C0F-4DCA-B32A-EC3C860C571F@apple.com> References: <3878F207-378B-4628-878F-14E80CE38E62@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_10:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: IPP Document Object update version X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============3038104527822032292==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============3038104527822032292== Content-type: multipart/alternative; boundary="Boundary_(ID_uOO7Mtp556vJb++AJA4I5g)" --Boundary_(ID_uOO7Mtp556vJb++AJA4I5g) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable Ira, > On Mar 15, 2019, at 10:41 AM, Ira McDonald via ipp = wrote: >=20 > Hi Mike, >=20 > I agree with your rationale that Document Object should be v1.1 (no = new content). >=20 > For Job Extensions (because of adding three operations, especially), I = think and > the folks yesterday on IPP WG call agreed that v2.0 was preferable. I'm in the process of posting JOBEXT 2.0 now; will summarize the = conformance changes from 1.0... >=20 > Cheers, > - Ira >=20 > 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/highnorthinc = > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Fri, Mar 15, 2019 at 9:57 AM Michael Sweet via ipp > wrote: > All, >=20 > In reviewing the minutes from yesterday's IPP concall I saw the = following comments regarding the IPP Document Object v1.1 errata update: >=20 > =E2=80=A2 Prototyping going on >=20 > I believe this is actually complete in ippserver, and there are of = course a LOT of IPP (PDF) printers with document object support already, = so I think any prototyping requirement has been met. (not that there is = one for an errata update) >=20 > =E2=80=A2 Need to add "Deprecated" and "Obsolete" definitions >=20 > These will be included in the next (stable) update, per our prior = discussions. >=20 > =E2=80=A2 Will be PWG Call for Objections because it is a 1.1 (errata = update) but should it be a 2.0? >=20 > Given that there is NOTHING NEW in this spec, just a general cleanup = and a relaxation of the multiple document support requirement, I see no = reason to make this 2.0. Any 1.0 compliant implementation is also 1.1 = compliant. >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_uOO7Mtp556vJb++AJA4I5g) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable Ira,

    On Mar 15, 2019, at 10:41 AM, = Ira McDonald via ipp <ipp@pwg.org> wrote:

    Hi Mike,

    I agree with your rationale that = Document Object should be v1.1 (no new content).

    For Job Extensions (because of adding = three operations, especially), I think and
    the = folks yesterday on IPP WG call agreed that v2.0 was = preferable.

    I'm = in the process of posting JOBEXT 2.0 now; will summarize the conformance = changes from 1.0...

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Fri, Mar 15, 2019 at 9:57 AM Michael = Sweet via ipp <ipp@pwg.org> wrote:
    All,

    In reviewing the minutes from yesterday's IPP concall I saw the = following comments regarding the IPP Document Object v1.1 errata = update:

    =E2=80=A2 Prototyping going on

      I believe this is actually complete in ippserver, and there are = of course a LOT of IPP (PDF) printers with document object support = already, so I think any prototyping requirement has been met. (not that = there is one for an errata update)

    =E2=80=A2 Need to add "Deprecated" and "Obsolete" definitions

      These will be included in the next (stable) update, per our prior = discussions.

    =E2=80=A2 Will be PWG Call for Objections because it is a 1.1 (errata = update) but should it be a 2.0?

      Given that there is NOTHING NEW in this spec, just a general = cleanup and a relaxation of the multiple document support requirement, I = see no reason to make this 2.0. Any 1.0 compliant implementation is also = 1.1 compliant.

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

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

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_uOO7Mtp556vJb++AJA4I5g)-- --===============3038104527822032292== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============3038104527822032292==-- From ipp-bounces@pwg.org Fri Mar 15 08:28:34 2019 Return-Path: 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 3E1E9130E25 for ; Fri, 15 Mar 2019 08:28:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 E5V-qzxoMmmG for ; Fri, 15 Mar 2019 08:28:32 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 1268F12D4F0 for ; Fri, 15 Mar 2019 08:28:32 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 88FC13F4F; Fri, 15 Mar 2019 15:28:31 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 0820C23E3; Fri, 15 Mar 2019 15:28:28 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 12CE03BA9; Fri, 15 Mar 2019 15:28:27 +0000 (UTC) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) by www.pwg.org (Postfix) with ESMTPS id 78E882618 for ; Fri, 15 Mar 2019 15:28:26 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FFRGoH054321 for ; Fri, 15 Mar 2019 08:28:25 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=IXrflFKF+/3DozV31ib72jHITXlrtvFF+9y8qrBsBK4=; b=TbhHVoeGlOEzbz/LzhO42l4noSd4P2I/g8Cw1EpYbrvyulQ3QaWkwqWlHZ5RkPy50YvZ JhUXbEDRYYEV6BAAHUTFbsa/lPsBC8tTjz59evQfyd5phE5RdFtPc4S66wFiORDbDDpL mg3Ue0GH8MsoNlcRttRtm+kaSnE/QP6EV4OdyeCrieubgL3dKpYO4c/fao6sO+PzhYVX cZFtchr2TwI1vvJgXbLs2k8y9i8zEjLVk1gFh8cHwy1YUFL9kYoXEgOf+WlJI/p7TTZI dgQqAJ8ZxqHTeFy/HyojzKCSOh5wxHHRA9g77pcQBdX5kjABYRZmuEwYF13nFXHbieTA eA== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2r4dc6nb16-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 15 Mar 2019 08:28:25 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POE00FETYZ9REA0@mr2-mtap-s01.rno.apple.com> for ipp@pwg.org; Fri, 15 Mar 2019 08:28:22 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POE00100YYIPZ00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 08:28:22 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 111a67b3685dcb5f2f0d6f197b1e34f9 X-Va-R-CD: ca1cfb374876a7dfdea2f7aaaf17041d X-Va-CD: 0 X-Va-ID: 1490a00d-90a4-4dd2-b39a-7a4199130ebe X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 111a67b3685dcb5f2f0d6f197b1e34f9 X-V-R-CD: ca1cfb374876a7dfdea2f7aaaf17041d X-V-CD: 0 X-V-ID: d34f2b1b-3126-40c3-b486-d8a208fa1f1d X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_10:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POE00MFVYWLKB00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 08:26:47 -0700 (PDT) Date: Fri, 15 Mar 2019 11:26:45 -0400 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_10:, , signatures=0 Subject: [IPP] Updated IPP Job Extensions v2.0 draft posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted an updated prototype draft of the IPP Job Extensions v2.0 (JOBEXT) specification to: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext20-20190315.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext20-20190315.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext20-20190315-rev.pdf This bumps the version to 2.0 so this update is no longer an errata but a full revision. Conformance changes are (NC-JPS2 means no change from JPS2): - REQUIRED job-ids operation attribute (NC-JPS2) - REQUIRED job-mandatory-attributes operation attribute (was OPTIONAL) - REQUIRED Cancel-Jobs, Cancel-My-Jobs, and Close-Job operations (NC-JPS2) - RECOMMENDED Resubmit-Job operation (was REQUIRED - see comment in document) - RECOMMENDED errors-count and warnings-count Job/Document Status attributes (was OPTIONAL) - RECOMMENDED print-content-optimize-actual Job/Document Status attribute (was OPTIONAL, see below) - RECOMMENDED job-cancel-after Job Template attribute (new) - RECOMMENDED job-delay-output-until-xxx Job Template attributes (was OPTIONAL) - RECOMMENDED job-hold-until-time Job Template attribute (was OPTIONAL) - RECOMMENDED job-retain-until-xxx Job Template attributes (new) - CONDITIONALLY REQUIRED xxx-default and xxx-supported Printer Description attributes for all of the RECOMMENDED Job Template attributes (was OPTIONAL/unspecified) - CONDITIONALLY REQUIRED document-charset-xxx and document-natural-language-xxx Printer Description attributes for the corresponding operation attributes (was OPTIONAL/unspecified) - REQUIRED job-creation-attributes-supported Printer Description attribute (was OPTIONAL) - REQUIRED job-history-attributes-xxx and job-history-interval-xxx Printer Description attributes (new) - REQUIRED job-ids-supported Printer Description attribute (NC-JPS2) - REQUIRED job-mandatory-attributes-supported Printer Description attribute (new) - REQUIRED job-spooling-supported Printer Description attribute (was OPTIONAL) - REQUIRED media-col-database Printer Description attribute (was OPTIONAL) - REQUIRED which-jobs-supported Printer Description attribute (NC-JPS2) WRT "print-content-optimize", I know we currently have it REQUIRED in IPP Everywhere, however I am not aware of any Client software that uses it. Something to talk about for IPP Everywhere 1.1, then we can sync up the conformance between the two documents. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Mar 15 09:13:57 2019 Return-Path: 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 27512126DFA for ; Fri, 15 Mar 2019 09:13:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, 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=apple.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 eqYOJ-7oeZ2g for ; Fri, 15 Mar 2019 09:13:55 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 90743126E5C for ; Fri, 15 Mar 2019 09:13:55 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 7FB453F4C; Fri, 15 Mar 2019 16:13:54 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 4057E3F5; Fri, 15 Mar 2019 16:13:51 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 8C2633BA9; Fri, 15 Mar 2019 16:13:49 +0000 (UTC) Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) by www.pwg.org (Postfix) with ESMTPS id 26DCB3F5 for ; Fri, 15 Mar 2019 16:13:49 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2FGBLdX022951 for ; Fri, 15 Mar 2019 09:13:48 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=PsY+ulPN2nOdZ6cIO9sCOG09N+NtwDih8NlUlEcL4Lo=; b=tMTOoWfA/SPmOsgB632u6ltC8Cbf3iXmFfBj8SZGvrt3CJI4R24ruFdVK+l9vRW3ch5o Q+VS74OdMPuYc+8Z50w70rnccnFwYkESFexpla9Zq9j4rRpbK6fL2I/yqFcC+6EW2hNA 4LZPi0eQ72AEF0gxtlFyA/NNONxDG0YKyEx+V/q9VfDeuX/+99Q+H/BggVa5faGOx+Ik EdlMrof3ffpk5bZ6MoU50mdr6hky14E8nVwJlpOHLIp0QhMRysYXq1rvWAnj/So2mCol 4Q6AE4qaEUueSHC+/AWuwrH/J1iX7sEgK2juVVX8nxIEB4hXMSv3uJU84a2pXkj2Vzu9 Aw== Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2r4daajb8c-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 15 Mar 2019 09:13:48 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz13.apple.com (nwk-mmpp-sz13.apple.com [17.128.115.216]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POF00NJE13059Q0@mr2-mtap-s03.rno.apple.com> for ipp@pwg.org; Fri, 15 Mar 2019 09:13:48 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz13.apple.com by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POF0070011PLH00@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 09:13:48 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 4fbda6203a144e8f51cdac56edfb94a2 X-Va-R-CD: 053f4b24a5cb7d8bdb77a107f4978ef6 X-Va-CD: 0 X-Va-ID: f5a9c07f-5b58-4e37-ad6d-afd4aa95f952 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 4fbda6203a144e8f51cdac56edfb94a2 X-V-R-CD: 053f4b24a5cb7d8bdb77a107f4978ef6 X-V-CD: 0 X-V-ID: 4e87d5b6-4414-4515-a44f-1258f014bb64 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-15_11:,, signatures=0 Received: from [17.235.10.93] by nwk-mmpp-sz13.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POF00M2G12XKB20@nwk-mmpp-sz13.apple.com>; Fri, 15 Mar 2019 09:13:47 -0700 (PDT) Date: Fri, 15 Mar 2019 12:13:45 -0400 Message-id: <3EAC8F00-B4D3-4172-B16A-4197E9A21287@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-15_11:, , signatures=0 Subject: [IPP] Draft slides for the April F2F posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted draft slides for the April 2019 F2F meeting to: https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1.pdf https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1.pptx _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Fri Mar 15 09:38:32 2019 Return-Path: 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 5C63F130E3F for ; Fri, 15 Mar 2019 09:38:32 -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, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 dQMEBAdXOUJS for ; Fri, 15 Mar 2019 09:38:30 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 13AF6130DE7 for ; Fri, 15 Mar 2019 09:38:30 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id D7D713F4D; Fri, 15 Mar 2019 16:38:29 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id CBF9D2894; Fri, 15 Mar 2019 16:38:24 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 8ECBF3BA9; Fri, 15 Mar 2019 16:38:23 +0000 (UTC) Received: from esa13.xerox.iphmx.com (esa13.xerox.iphmx.com [68.232.143.63]) by www.pwg.org (Postfix) with ESMTPS id B54653F5 for ; Fri, 15 Mar 2019 16:38:21 +0000 (UTC) Received: from mail-by2nam01lp2056.outbound.protection.outlook.com (HELO NAM01-BY2-obe.outbound.protection.outlook.com) ([104.47.34.56]) by ob1.xerox.iphmx.com with ESMTP/TLS/AES256-GCM-SHA384; 15 Mar 2019 11:38:18 -0500 Received: from MWHPR11MB1885.namprd11.prod.outlook.com (10.175.54.8) by MWHPR11MB1342.namprd11.prod.outlook.com (10.169.230.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.13; Fri, 15 Mar 2019 16:38:17 +0000 Received: from MWHPR11MB1885.namprd11.prod.outlook.com ([fe80::c154:625d:4901:eaeb]) by MWHPR11MB1885.namprd11.prod.outlook.com ([fe80::c154:625d:4901:eaeb%9]) with mapi id 15.20.1709.011; Fri, 15 Mar 2019 16:38:17 +0000 To: PWG IPP Workgroup Thread-Topic: [IPP] Draft slides for the April F2F posted Thread-Index: AQHU20oxh89bTZ5wJEy2DJE2nSJwY6YMbwyA Date: Fri, 15 Mar 2019 16:38:16 +0000 Message-ID: <937CE550-51C1-483E-B2F8-745C0B45A54D@xerox.com> References: <3EAC8F00-B4D3-4172-B16A-4197E9A21287@apple.com> In-Reply-To: <3EAC8F00-B4D3-4172-B16A-4197E9A21287@apple.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.17.0.190309 authentication-results: spf=none (sender IP is ) smtp.mailfrom=Christopher.Rizzo@xerox.com; x-originating-ip: [50.53.147.90] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 063e317d-9d16-4ee7-afaa-08d6a964a05c x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:MWHPR11MB1342; x-ms-traffictypediagnostic: MWHPR11MB1342: x-ms-exchange-purlcount: 3 x-microsoft-antispam-prvs: x-forefront-prvs: 09778E995A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(39860400002)(376002)(346002)(396003)(189003)(199004)(446003)(68736007)(58126008)(5660300002)(25786009)(53936002)(229853002)(6306002)(72206003)(71200400001)(82746002)(36756003)(54896002)(71190400001)(33656002)(6512007)(2906002)(14454004)(6486002)(316002)(606006)(6436002)(186003)(26005)(66066001)(7736002)(6916009)(476003)(81156014)(486006)(8676002)(966005)(3846002)(81166006)(236005)(8936002)(106356001)(105586002)(83716004)(11346002)(102836004)(86362001)(97736004)(76176011)(256004)(478600001)(2616005)(6246003)(99286004)(53546011)(6506007)(6116002)(24704002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR11MB1342; H:MWHPR11MB1885.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: Rcjsfm5wbQLVg4XwGEeSKKBSM8C02rv5Quzgt310T+sM1mDXKpkc0xZhqQuR30Yrxrg6MQhGY2OkmI8dt349Zl/BHYh5udG18r/tCumbLAy3cVJir95Kisv8K16D2w+EeHoSgdvuqwLNh7lz79PEK18+DLNp13TagEXJOOuiEYZr82FCbeiKzY+/JKYPT5+cx++mLVIiHIBnQKeQb5E8Te3qFliRR/G045aydHy2kWA8CGEKnsL3LB/RXlh4SYGVZKipaOg8MNvDJZ+orYy0NwUZ9r89aLBqjzGAakETdw+L1TPiMCF2XvIOB2jSccCsW6ZQp0xYSl+Mygs0Y70o5b0IscKk4ACi3+wxRv2rvDrCM/Z9immLZL7TYXxjQa8LYb0XNKYDAZVO3VXJFTZD4mOlAx49dTgOwUUBoD0kaXw= MIME-Version: 1.0 X-OriginatorOrg: xerox.com X-MS-Exchange-CrossTenant-Network-Message-Id: 063e317d-9d16-4ee7-afaa-08d6a964a05c X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2019 16:38:16.9974 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 9c2a31bd-e798-488d-986b-90156ac8f29b X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1342 Subject: Re: [IPP] Draft slides for the April F2F posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Rizzo, Christopher via ipp" Reply-To: "Rizzo, Christopher" Content-Type: multipart/mixed; boundary="===============0401086742605274569==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0401086742605274569== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_937CE55051C1483EB2F8745C0B45A54Dxeroxcom_" --_000_937CE55051C1483EB2F8745C0B45A54Dxeroxcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SW4gdGhlIG1lZXRpbmcgSXJhIG1lbnRpb25lZCB0aGVyZSBpcyBhICJzdXJ2ZXkgbW9ua2V5PyIg c2l0ZSB3ZSBzaG91bGQgdXNlIHRvIHNwZWNpZnkgb3VyIGF0dGVuZGFuY2UgZm9yIHRoZSB1cGNv bWluZyBGMkYuDQoNCkkgY2Fubm90IGZpbmQgYSByZWZlcmVuY2UgdG8gdGhpcyBzaXRlLiAgQ2Fu IHNvbWVvbmUgcHJvdmlkZSBpdD8NCg0KVGhhbmtzLA0KQ2hyaXMNCg0KQ2hyaXN0b3BoZXIgUml6 em8NClhlcm94IENvcnBvcmF0aW9uDQpHREcvRGlzY292ZXJ5L0FkdmFuY2UgVGVjaG5vbG9neQ0K MjY2MDAgU1cgUGFya3dheSBBdmUuDQpXaWxzb252aWxsZSwgT1IgOTcwNzAtOTI1MQ0KUGhvbmU6 ICg1ODUpIDMxNC02OTM2DQpFbWFpbDogQ2hyaXN0b3BoZXIuUml6em9AeGVyb3guY29tDQoNCiJU aGUgcmVhbGl6YXRpb24gY2FtZSBvdmVyIG1lIHdpdGggZnVsbCBmb3JjZSB0aGF0IGEgZ29vZCBw YXJ0IG9mIHRoZSByZW1haW5kZXIgb2YgbXkgbGlmZSB3YXMgZ29pbmcgdG8gYmUgc3BlbnQgaW4g ZmluZGluZyBlcnJvcnMgaW4gbXkgb3duIHByb2dyYW1zLiINCi1NYXVyaWNlIFdpbGtlcywgTWVt b2lycyBvZiBhIENvbXB1dGVyIFBpb25lZXINCg0KRnJvbTogaXBwIDxpcHAtYm91bmNlc0Bwd2cu b3JnPiBvbiBiZWhhbGYgb2YgUFdHIFdvcmtncm91cCA8aXBwQHB3Zy5vcmc+DQpSZXBseS1Ubzog Im1zd2VldEBhcHBsZS5jb20iIDxtc3dlZXRAYXBwbGUuY29tPg0KRGF0ZTogRnJpZGF5LCBNYXJj aCAxNSwgMjAxOSBhdCA5OjE0IEFNDQpUbzogUFdHIFdvcmtncm91cCA8aXBwQHB3Zy5vcmc+DQpT dWJqZWN0OiBbSVBQXSBEcmFmdCBzbGlkZXMgZm9yIHRoZSBBcHJpbCBGMkYgcG9zdGVkDQoNCkFs bCwNCg0KSSBoYXZlIHBvc3RlZCBkcmFmdCBzbGlkZXMgZm9yIHRoZSBBcHJpbCAyMDE5IEYyRiBt ZWV0aW5nIHRvOg0KDQogICAgICAgICAgICAgICAgaHR0cHM6Ly9mdHAucHdnLm9yZy9wdWIvcHdn L2lwcC9zbGlkZXMvaXBwLXdnLWFnZW5kYS1hcHJpbC0xOWQxLnBkZg0KICAgICAgICAgICAgICAg IGh0dHBzOi8vZnRwLnB3Zy5vcmcvcHViL3B3Zy9pcHAvc2xpZGVzL2lwcC13Zy1hZ2VuZGEtYXBy aWwtMTlkMS5wcHR4DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KTWljaGFlbCBTd2VldCwgU2VuaW9yIFByaW50aW5nIFN5c3RlbSBF bmdpbmVlcg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xw0KaXBwIG1haWxpbmcgbGlzdA0KaXBwQHB3Zy5vcmc8bWFpbHRvOmlwcEBwd2cub3JnPg0KaHR0 cHM6Ly93d3cucHdnLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwcA0KDQo= --_000_937CE55051C1483EB2F8745C0B45A54Dxeroxcom_ Content-Type: text/html; charset="utf-8" Content-ID: <9A38638B6741544BA1636604B09059EF@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJZdSBNaW5j aG8iOw0KCXBhbm9zZS0xOjIgMiA0IDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0KCXtmb250 LWZhbWlseToiXEBZdSBNaW5jaG8iO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05v cm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2lu LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli cmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt cHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3Jp dHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5t c29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFt ZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBp bjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9u dC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFu LmFwcGxlLXRhYi1zcGFuDQoJe21zby1zdHlsZS1uYW1lOmFwcGxlLXRhYi1zcGFuO30NCnNwYW4u RW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFt aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERl ZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9 DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGlu IDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlv bjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVl IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj5JbiB0aGUgbWVldGluZyBJcmEgbWVudGlvbmVkIHRoZXJlIGlzIGEgJnF1b3Q7 c3VydmV5IG1vbmtleT8mcXVvdDsgc2l0ZSB3ZSBzaG91bGQgdXNlIHRvIHNwZWNpZnkgb3VyIGF0 dGVuZGFuY2UgZm9yIHRoZSB1cGNvbWluZyBGMkYuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkg Y2Fubm90IGZpbmQgYSByZWZlcmVuY2UgdG8gdGhpcyBzaXRlLiZuYnNwOyBDYW4gc29tZW9uZSBw cm92aWRlIGl0PzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsPG86cD48L286cD48L3A+ DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DaHJpczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPkNocmlzdG9waGVy IFJpenpvPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj5YZXJveCBDb3Jwb3Jh dGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj5HREcvRGlz Y292ZXJ5L0FkdmFuY2UgVGVjaG5vbG9neTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0 O2NvbG9yOmJsYWNrIj4yNjYwMCBTVyBQYXJrd2F5IEF2ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+ DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z aXplOjEwLjVwdDtjb2xvcjpibGFjayI+V2lsc29udmlsbGUsIE9SIDk3MDcwLTkyNTE8bzpwPjwv bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjpibGFjayI+UGhvbmU6ICg1ODUpIDMxNC02 OTM2PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPkVtYWlsOiBD aHJpc3RvcGhlci5SaXp6b0B4ZXJveC5jb208bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjpibGFjayI+ PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPiZxdW90O1RoZSByZWFsaXphdGlv biBjYW1lIG92ZXIgbWUgd2l0aCBmdWxsIGZvcmNlIHRoYXQgYSBnb29kIHBhcnQgb2YgdGhlIHJl bWFpbmRlciBvZiBteSBsaWZlIHdhcyBnb2luZyB0byBiZSBzcGVudCBpbiBmaW5kaW5nIGVycm9y cyBpbiBteSBvd24gcHJvZ3JhbXMuJnF1b3Q7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+ DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu NXB0O2NvbG9yOmJsYWNrIj4tTWF1cmljZSBXaWxrZXMsIDxpPg0KTWVtb2lycyBvZiBhIENvbXB1 dGVyIFBpb25lZXI8L2k+PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBj bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpi bGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xv cjpibGFjayI+aXBwICZsdDtpcHAtYm91bmNlc0Bwd2cub3JnJmd0OyBvbiBiZWhhbGYgb2YgUFdH IFdvcmtncm91cCAmbHQ7aXBwQHB3Zy5vcmcmZ3Q7PGJyPg0KPGI+UmVwbHktVG86IDwvYj4mcXVv dDttc3dlZXRAYXBwbGUuY29tJnF1b3Q7ICZsdDttc3dlZXRAYXBwbGUuY29tJmd0Ozxicj4NCjxi PkRhdGU6IDwvYj5GcmlkYXksIE1hcmNoIDE1LCAyMDE5IGF0IDk6MTQgQU08YnI+DQo8Yj5Ubzog PC9iPlBXRyBXb3JrZ3JvdXAgJmx0O2lwcEBwd2cub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwv Yj5bSVBQXSBEcmFmdCBzbGlkZXMgZm9yIHRoZSBBcHJpbCBGMkYgcG9zdGVkPG86cD48L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGwsPG86 cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgaGF2 ZSBwb3N0ZWQgZHJhZnQgc2xpZGVzIGZvciB0aGUgQXByaWwgMjAxOSBGMkYgbWVldGluZyB0bzo8 bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+ Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsgPC9zcGFuPjxhIGhyZWY9Imh0dHBzOi8vZnRwLnB3Zy5vcmcvcHViL3B3Zy9pcHAvc2xpZGVz L2lwcC13Zy1hZ2VuZGEtYXByaWwtMTlkMS5wZGYiPmh0dHBzOi8vZnRwLnB3Zy5vcmcvcHViL3B3 Zy9pcHAvc2xpZGVzL2lwcC13Zy1hZ2VuZGEtYXByaWwtMTlkMS5wZGY8L2E+PG86cD48L286cD48 L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBjbGFzcz0iYXBw bGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8L3NwYW4+PGEg aHJlZj0iaHR0cHM6Ly9mdHAucHdnLm9yZy9wdWIvcHdnL2lwcC9zbGlkZXMvaXBwLXdnLWFnZW5k YS1hcHJpbC0xOWQxLnBwdHgiPmh0dHBzOi8vZnRwLnB3Zy5vcmcvcHViL3B3Zy9pcHAvc2xpZGVz L2lwcC13Zy1hZ2VuZGEtYXByaWwtMTlkMS5wcHR4PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk1pY2hhZWwgU3dlZXQsIFNlbmlvciBQcmludGlu ZyBTeXN0ZW0gRW5naW5lZXI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh c3M9Ik1zb05vcm1hbCI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX188bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi PmlwcCBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxhIGhyZWY9Im1haWx0bzppcHBAcHdnLm9yZyI+aXBwQHB3Zy5vcmc8L2E+ PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBo cmVmPSJodHRwczovL3d3dy5wd2cub3JnL21haWxtYW4vbGlzdGluZm8vaXBwIj5odHRwczovL3d3 dy5wd2cub3JnL21haWxtYW4vbGlzdGluZm8vaXBwPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+ DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp dj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_937CE55051C1483EB2F8745C0B45A54Dxeroxcom_-- --===============0401086742605274569== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0401086742605274569==-- From ipp-bounces@pwg.org Fri Mar 15 09:44:59 2019 Return-Path: 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 80687130E79 for ; Fri, 15 Mar 2019 09:44:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, 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 ZjW6euDyuhLU for ; Fri, 15 Mar 2019 09:44:56 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 49CC912705F for ; Fri, 15 Mar 2019 09:44:56 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id E74B73F52; Fri, 15 Mar 2019 16:44:54 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id DA7DD2894; Fri, 15 Mar 2019 16:44:48 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 5FEA92894; Fri, 15 Mar 2019 16:44:47 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 8294C2618 for ; Fri, 15 Mar 2019 16:44:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1552668284; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JDS13j3EILzXATNEfwp3vwM5kkA5mICPWXB6fP8WAj0=; b=Wjhx5hxLs8SSC1342o9xeLMoliCywtNZDarlInLhJmj6QVde7pkBjnX9y5nUHcmbxecmONqAi07moVpaKt7gahDp0rnNrWJ/zeRk1Nr4oxQHUQZst/TDvDnDDGp+ZNt5Xy//eBOyaqkJUV1d66aFwAmzX8P8r7YG700nCkjomcw= Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-by2nam05lp2057.outbound.protection.outlook.com [104.47.50.57]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-55-ljL1dDEkMUar2CgTnGUzGg-1; Fri, 15 Mar 2019 12:44:42 -0400 X-MC-Unique: ljL1dDEkMUar2CgTnGUzGg-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB1288.NAMPRD84.PROD.OUTLOOK.COM (10.169.12.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.14; Fri, 15 Mar 2019 16:44:41 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1709.011; Fri, 15 Mar 2019 16:44:40 +0000 To: Michael Sweet Thread-Topic: [IPP] RFC: Relationship between job-retain-until-xxx and job-password Thread-Index: AQHU2zaKBc5HELr9CUareW/7oe7KcKYM5lGA Date: Fri, 15 Mar 2019 16:44:40 +0000 Message-ID: <00239C4D-D794-4962-88E2-A00CBE1F654B@hp.com> References: In-Reply-To: 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.51.156] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ba45a5b8-8e6f-44a4-556e-08d6a9658523 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB1288; x-ms-traffictypediagnostic: CS1PR8401MB1288: x-microsoft-antispam-prvs: x-forefront-prvs: 09778E995A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(376002)(346002)(366004)(396003)(189003)(199004)(6602003)(14454004)(106356001)(256004)(14444005)(76176011)(6436002)(6116002)(102836004)(81166006)(81156014)(66066001)(6506007)(26005)(2616005)(186003)(11346002)(229853002)(476003)(7736002)(86362001)(486006)(5660300002)(446003)(68736007)(105586002)(71200400001)(6246003)(71190400001)(2906002)(36756003)(316002)(606006)(83716004)(4326008)(53546011)(6486002)(99286004)(8936002)(236005)(6512007)(54896002)(6306002)(97736004)(3846002)(53936002)(82746002)(33656002)(99936001)(25786009)(966005)(6916009)(478600001)(13513002)(21314003); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB1288; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: e4atWStNLsWYHPn+LVj6FlZHH34IMmWCjbvlsEbRnbfB5QghHfQRCkAlvKVTrvye68/EmCimK/LkddZ39VJz4FwnycYbf4X3Aw0dtREmohAWjMIzRt485YzO1kyR25C63Jt6x2gRyycS8zZXKNrI3TJf61fYXVsK33bFLrwaCBVDmOJQorCPKGFa5+eK9lDqb+ZrguveXlowjVLZvULmHVSLIsVrGIYiVa4ZN8ldLzQ6HAB/d1fGtExDv6v3NdjKAbBDik/+CAT3hxM9Z0eHUdvyDVUkmbt81kxSL8yTMvhGk3ONlynzEYKuKwgFVrvycAizeEmtTKf4Bn0YbQZ6u/aHor73E/K9oDDXjjbSnp5RCnju9I7AGTznVJapvOqf5sorbSokQ3o7KsJWVLBGRtug3QT/r146NrcAiBGc2qg= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: ba45a5b8-8e6f-44a4-556e-08d6a9658523 X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2019 16:44:40.9019 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB1288 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: Relationship between job-retain-until-xxx and job-password X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============1176059809572883634==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============1176059809572883634== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_7385CB59-23A2-4124-B863-C040D5794920"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_7385CB59-23A2-4124-B863-C040D5794920 Content-Type: multipart/alternative; boundary="Apple-Mail=_B8856E29-3518-4007-9A83-CA83FE8A3BB1" --Apple-Mail=_B8856E29-3518-4007-9A83-CA83FE8A3BB1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 15, 2019, at 7:53 AM, Michael Sweet via ipp = wrote: >=20 > All, >=20 > In reviewing the minutes from yesterday's concall, I saw the following = summary of discussions regarding job-password and job-retain-until-xxx = in the new IPP Enterprise Printing Extensions: >=20 > =E2=80=A2 discussed job-retain-until and job-retain-until-time and = job-retain-until-date > =E2=80=A2 consensus was to keep job-retain-until (type2 keyword) and = job-retain-until-date (dateTime) > =E2=80=A2 Semantics for job-retain-until-time could be specified that = the integer is the number of seconds, etc. once it has entered its = terminal state (e.g. calculated as "date-time-at-completed" + = "job-retain-until-time"). > =E2=80=A2 what to do about "job-password" Jobs that the Job isn't a = Retained Job > =E2=80=A2 "job-password" should be disallowed when "job-retain-until" = or "job-retain-until-time" are specified > =E2=80=A2 maybe the better recommendation for a "secure print" that = doesn't get aged out is to use "job-print-password" and have it be = "save-only"? > =E2=80=A2 Should there be additional dispositions? >=20 > Some of my own thoughts: >=20 > 1. I thought the consensus was to put job-retain-until-xxx in JOBEXT? = They are defined in the current draft of JOBEXT... >=20 > 2. My issue with just having job-retain-until-time (dateTime) is that = there is no way (short of defining keyword/name values for = job-retain-until) to say "by default, retain all jobs for a year". For = example, CUPS can be configured to retain jobs ("PreserveJobFiles") = indefinitely, not at all, or for a specified number of seconds after = completion. There is no "retain until date/time" functionality because = we've never needed it in CUPS, but I can see a potential need for legal = documents/jobs that "expire" after a specific date and time. >=20 > TL;DR: If we get rid of anything it should be "job-retain-until-time = (dateTime)" and *not* > "job-retain-until-interval (integer(0:MAX))". Yeah this was a typo. I meant to say this: =E2=80=A2 consensus was to keep "job-retain-until" (type2 keyword) and = "job-retain-until-time" (integer) and NOT implement = "job-retain-until-date" (dateTime) >=20 > 3. As for job-password not being compatible with job-retain-until-xxx, = why? "job-password" just holds the job until the User enters the = password/code at the printer - the semantics of retaining a job don't = kick in until the job reaches a terminating state, and PIN printing will = likely have the same legal requirements WRT document retention as any = other kind of printing. If the goal is to protect the Job, the "job-password" only prevents the = first printing by holding it in the 'pending-held' state. If you also = specify "job-retain-until" =3D 'indefinite', that will cause the Job to = be available for reprinting by others. So the normative language we were = talking about was to say that "job-password" and "job-retain-until" MUST = NOT or SHOULD NOT both be specified, or that "job-retain-until" MUST be = 'no-retain' etc. (the keywords in the JPS2v2 draft from Feb. 14 are = broken). However...your next comments may obviate all of this. >=20 > 4. WRT "job-print-password", what if (and I haven't thought this = completely through yet) we define another parallel attribute, = "job-password-action (type2 keyword)" that defines the semantics of the = "job-password" attribute, with the default being "hold-job" to preserve = the 1.0 semantics. Something like: >=20 > job-password-action (type2 keyword) >=20 > This operation attribute specifies how a Job is processed when the = "job-password" (section N.M.P) operation attribute is included in a Job = Creation request. Standard keyword values include: >=20 > - 'hold-job': The Job is placed in the 'pending-held' state and is = released when the "job-password" value is entered at the Printer's = console. > - 'process-and-retain': The Job is placed in the 'pending' state and = it scheduled for processing without waiting for the User to enter the = "job-password" value at the Printer's console. > - 'retain-only': The Job is placed in the 'completed' state as soon as = all Documents are received by the Printer. >=20 > Once in a terminating state, the Job is retained according to the = current value of its "job-retain-until-xxx" attributes. I like it! I'll update my EPE draft to specify that and we can discuss = that first draft at our next IPP WG meeting. >=20 > 5. Also WRT "job-print-password", if we adopt "job-print-action" (guessing you mean "job-password-action"...) > then we can amend the semantics of "Resubmit-Job" to require the = original "job-password" value to get both the desired reprint behavior = *and* better support the security characteristics implied by = "job-password". >=20 > Thoughts? I like that too! >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = --Apple-Mail=_B8856E29-3518-4007-9A83-CA83FE8A3BB1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

    On Mar 15, 2019, at 7:53 AM, Michael Sweet via ipp <ipp@pwg.org> = wrote:

    All,

    In reviewing the minutes from yesterday's concall, I saw the following = summary of discussions regarding job-password and job-retain-until-xxx = in the new IPP Enterprise Printing Extensions:

    =E2=80=A2 discussed job-retain-until and job-retain-until-time = and job-retain-until-date
    =E2=80=A2 consensus was to keep job-retain-until (type2 = keyword) and job-retain-until-date (dateTime)
    =E2=80=A2 Semantics for job-retain-until-time = could be specified that the integer is the number of seconds, etc. once = it has entered its terminal state (e.g. calculated as = "date-time-at-completed" + "job-retain-until-time").
    =E2=80=A2 what to do about "job-password" Jobs = that the Job isn't a Retained Job
    =E2=80=A2 "job-password" should be disallowed when = "job-retain-until" or "job-retain-until-time" are specified
    = =E2=80=A2 maybe the better recommendation for a "secure print" = that doesn't get aged out is to use "job-print-password" and have it be = "save-only"?
    =E2=80=A2 Should there be additional dispositions?

    Some of my own thoughts:

    1. I thought the consensus was to put job-retain-until-xxx in JOBEXT? = They are defined in the current draft of JOBEXT...

    2. My issue with just having job-retain-until-time (dateTime) is that = there is no way (short of defining keyword/name values for = job-retain-until) to say "by default, retain all jobs for a year". For = example, CUPS can be configured to retain jobs ("PreserveJobFiles") = indefinitely, not at all, or for a specified number of seconds after = completion. There is no "retain until date/time" functionality because = we've never needed it in CUPS, but I can see a potential need for legal = documents/jobs that "expire" after a specific date and time.

    TL;DR: If we get rid of anything it should be "job-retain-until-time = (dateTime)" and *not*
    "job-retain-until-interval (integer(0:MAX))".

    Yeah this = was a typo. I meant to say this:

    =E2=80=A2 consensus was to keep "job-retain-until" (type2 = keyword) and "job-retain-until-time" (integer) and NOT implement = "job-retain-until-date" (dateTime)



    3. As for job-password not being compatible with job-retain-until-xxx, = why? "job-password" just holds the job until the User enters the = password/code at the printer - the semantics of retaining a job don't = kick in until the job reaches a terminating state, and PIN printing will = likely have the same legal requirements WRT document retention as any = other kind of printing.

    If the goal is to protect the Job, the "job-password" = only prevents the first printing by holding it in the 'pending-held' = state. If you also specify "job-retain-until" =3D 'indefinite', that = will cause the Job to be available for reprinting by others. So the = normative language we were talking about was to say that "job-password" = and "job-retain-until" MUST NOT or SHOULD NOT both be specified, or that = "job-retain-until" MUST be 'no-retain' etc. (the keywords in the JPS2v2 = draft from Feb. 14 are broken).

    However...your next comments may obviate all of = this.


    4. WRT "job-print-password", what if (and I haven't thought this = completely through yet) we define another parallel attribute, = "job-password-action (type2 keyword)" that defines the semantics of the = "job-password" attribute, with the default being "hold-job" to preserve = the 1.0 semantics. Something like:

    job-password-action (type2 keyword)

    This operation attribute specifies how a Job is processed when the = "job-password" (section N.M.P) operation attribute is included in a Job = Creation request. Standard keyword values include:

    - 'hold-job': The Job is placed in the 'pending-held' state and is = released when the "job-password" value is entered at the Printer's = console.
    - 'process-and-retain': The Job is placed in the 'pending' state and it = scheduled for processing without waiting for the User to enter the = "job-password" value at the Printer's console.
    - 'retain-only': The Job is placed in the 'completed' state as soon as = all Documents are received by the Printer.

    Once in a terminating state, the Job is retained according to the = current value of its "job-retain-until-xxx" attributes.

    I like it! = I'll update my EPE draft to specify that and we can discuss that first = draft at our next IPP WG meeting.


    5. Also WRT "job-print-password", if we adopt = "job-print-action"

    (guessing you mean = "job-password-action"...)

    then we can = amend the semantics of "Resubmit-Job" to require the original = "job-password" value to get both the desired reprint behavior *and* = better support the security characteristics implied by = "job-password".

    Thoughts?

    I like that too!

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

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

    = --Apple-Mail=_B8856E29-3518-4007-9A83-CA83FE8A3BB1-- --Apple-Mail=_7385CB59-23A2-4124-B863-C040D5794920 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyL1nMACgkQqskbKLDW 1N0oGg//XdRq+9mD0E5zIo7eQSObIFYXo4Q+9mVaK4K4ml00hhB+rTAwILC6za76 txAS6t7JNTdch7g4vQ9Qw93Q6W42aTiqiVw/u2yn1OfjtdnSBKEzL4s5o7peqzrV 9quX7Ic4ltSlUb+FPnjy8tjbrmHEpASlG9Yc32JadKJ5CwoGfqJ64UikrvBwhy9G q9DLoddtINeTQdFOX894GFEHoC6mTGNcBkxQneiEO6OTtSON6rsoz1PJRWtl4vLm ATNXy4VwtPbMbLgVggdLch6JlNrgpg9pf3fMg4M+BPROJt0/uFhjXYyX0oG3hF7e my0Yy1qfjD/EXUG2T4O2SIi4rgOlOv5m8rPltyzSYHGlBeJP0LKlWDMEErpUel+J xq535/W327HO/dH+eP2IECYGZ0Y8AFCnBrWWLKq/1zssSmw4w2Dg9qZNWPEzuqHX LuN6DiA+heGIzDQxo9ZXfbLrkSglpRKkyPNxt8Kjbv2T7OJh6JxV2zFJ6GGFRJsq m+2EzwSXcCtKmZLPEef5xQtMhzuq23LCQffDb7xMWl57tSPLVHdFartaZFr4cDj5 1dkxbuZijz7QyW0ZIoT/ggj/bGOwresydDMd53FSIej51TDz4gWe6gsVxUE6sYbt nder5aCvTDFF3ixqw8FtKOfA1XW9VJHy9gj1pH2FCIquVObs7RY= =4DTc -----END PGP SIGNATURE----- --Apple-Mail=_7385CB59-23A2-4124-B863-C040D5794920-- --===============1176059809572883634== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============1176059809572883634==-- From ipp-bounces@pwg.org Fri Mar 15 09:46:10 2019 Return-Path: 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 A4ACB130E79 for ; Fri, 15 Mar 2019 09:46:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.282 X-Spam-Level: X-Spam-Status: No, score=-0.282 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.428, 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 4Ruxn3JxUzfv for ; Fri, 15 Mar 2019 09:46:07 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 9F126130E6F for ; Fri, 15 Mar 2019 09:46:07 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 79E2A3F4D; Fri, 15 Mar 2019 16:46:07 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 536253F5; Fri, 15 Mar 2019 16:46:02 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 333023BAA; Fri, 15 Mar 2019 16:46:01 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 451182618 for ; Fri, 15 Mar 2019 16:46:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1552668359; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=JdXIbVNBf2IRYFM7RA6vcqtMK6vjUIBOn7TPzSEybGE=; b=lazsW/BmpO8Q2o3teemjo2KQc+ShRDaVMc0crvU03Lu5f0tVrlAtf8ulr1IrnXir5DquJjzu63N5EGdf1z448RWI3gVr3PQ+eD8MJi9+cZ4lO6kX8WRdlahIdBaB8vYm/3OkOdI1Y1cA3cT6Tr8kc+uQmra9IPhDws8Txq5HetI= Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02lp2052.outbound.protection.outlook.com [104.47.37.52]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-295-vkgLYef5Pmy2cbLVweOqLA-1; Fri, 15 Mar 2019 12:45:53 -0400 X-MC-Unique: vkgLYef5Pmy2cbLVweOqLA-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0838.NAMPRD84.PROD.OUTLOOK.COM (10.169.24.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.14; Fri, 15 Mar 2019 16:45:51 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1709.011; Fri, 15 Mar 2019 16:45:51 +0000 To: "Rizzo, Christopher" Thread-Topic: [IPP] Draft slides for the April F2F posted Thread-Index: AQHU20opFRqvC22nSU6b01kKjJCVYqYM5GYAgAACHQA= Date: Fri, 15 Mar 2019 16:45:51 +0000 Message-ID: References: <3EAC8F00-B4D3-4172-B16A-4197E9A21287@apple.com> <937CE550-51C1-483E-B2F8-745C0B45A54D@xerox.com> In-Reply-To: <937CE550-51C1-483E-B2F8-745C0B45A54D@xerox.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.51.156] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 90dcea1f-da99-4b99-affa-08d6a965af2d x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0838; x-ms-traffictypediagnostic: CS1PR8401MB0838: x-microsoft-antispam-prvs: x-forefront-prvs: 09778E995A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(366004)(346002)(39860400002)(136003)(199004)(189003)(6602003)(81156014)(2906002)(6916009)(76176011)(966005)(26005)(81166006)(186003)(256004)(99286004)(71190400001)(71200400001)(446003)(11346002)(83716004)(99936001)(106356001)(105586002)(33656002)(8676002)(486006)(102836004)(478600001)(6506007)(5660300002)(21615005)(476003)(97736004)(2616005)(53546011)(53936002)(236005)(3846002)(54896002)(6306002)(6512007)(6246003)(6486002)(7736002)(229853002)(14454004)(66066001)(68736007)(6116002)(606006)(86362001)(4326008)(316002)(8936002)(25786009)(36756003)(82746002)(6436002)(24704002); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0838; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: siAVEXSCj+Em3wYmqaZ0NfUcy7kI7X+eI31uQobrZ+sSEMZqqIOlPQLfAwNEAu7wtjya9I8g0TxLNPO9S+utdUiTk7EIR6UmrEWPo/xrUatW9AFqNy5zSrpgapXS7GEHx4XwkNs+2Da+NE0b1iyPzZ/UiXaK2R/LmMYjQI6hUY2Y4DZnMb0voac6wGA1I4S3NgSsIxYE6ekKLPRrChYqNXr1kvJoELl6ykz0JNQpA9oPowEnIzcOiWUWG1db84AggjdtygdTxoU5j5FBLwm/G+oRizU+2TKSTHh6fcaLCqgMLk/hNJw1+nYlp2jTWWiDM95AmJI+EfNrfWYChA1FawtvyaCbHfg76LX425LMeQmp67LCvuz0v1aze52ryyQeAbESWYr3pgsASvhLmfuVF8OY+w+ijWo9cx8/WOy9tAU= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 90dcea1f-da99-4b99-affa-08d6a965af2d X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2019 16:45:51.3500 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0838 Cc: PWG IPP Workgroup Subject: Re: [IPP] Draft slides for the April F2F posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============0055667492259294906==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============0055667492259294906== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_72BCCD2F-2DE6-4BF9-8608-0DEA76412D2E"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_72BCCD2F-2DE6-4BF9-8608-0DEA76412D2E Content-Type: multipart/alternative; boundary="Apple-Mail=_612730EA-1B56-4B5A-B72F-5AC492BA2FB2" --Apple-Mail=_612730EA-1B56-4B5A-B72F-5AC492BA2FB2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Chris, It is on the meeting page = (https://www.pwg.org/chair/meeting-info/april-2019-lexington.html = ). The = link to click on is PWG April 2019 Face-to-Face Meeting Survey = . Smith /** Smith Kennedy Chair, IEEE ISTO Printer Working Group HP Inc. */ > On Mar 15, 2019, at 10:38 AM, Rizzo, Christopher via ipp = wrote: >=20 > In the meeting Ira mentioned there is a "survey monkey?" site we = should use to specify our attendance for the upcoming F2F. >=20 > I cannot find a reference to this site. Can someone provide it? >=20 > Thanks, > Chris >=20 > 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 = >=20 > "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 >=20 > From: ipp on behalf of PWG Workgroup = > Reply-To: "msweet@apple.com" > Date: Friday, March 15, 2019 at 9:14 AM > To: PWG Workgroup > Subject: [IPP] Draft slides for the April F2F posted >=20 > All, >=20 > I have posted draft slides for the April 2019 F2F meeting to: >=20 > = https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1.pdf = > = https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1.pptx = >=20 > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > = https://protect-us.mimecast.com/s/DOzzC9rB5BF61BL2ioHdd3?domain=3Dpwg.org = --Apple-Mail=_612730EA-1B56-4B5A-B72F-5AC492BA2FB2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Chris,

    It is on the = meeting page (https://www.pwg.org/chair/meeting-info/april-2019-lexington.htm= l). The link to click on is PWG April = 2019 Face-to-Face Meeting Survey.

    Smith

    /**
        Smith = Kennedy
        Chair, IEEE ISTO Printer = Working Group
        HP Inc.
    */

    On Mar 15, 2019, at 10:38 AM, Rizzo, Christopher via ipp = <ipp@pwg.org> = wrote:

    In the = meeting Ira mentioned there is a "survey monkey?" site we should use to = specify our attendance for the upcoming F2F.
     
    I cannot = find a reference to this site.  Can someone provide it?
     
    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
     
    From: ipp <ipp-bounces@pwg.org>= on behalf of PWG Workgroup <ipp@pwg.org>
    Reply-To: "msweet@apple.com" <msweet@apple.com>
    Date: Friday, March 15, 2019 = at 9:14 AM
    To: PWG Workgroup <ipp@pwg.org>
    Subject: [IPP] Draft slides for = the April F2F posted
     
    All,
     
    I have posted draft slides for the April 2019 F2F meeting = to:
     
            &= nbsp;       https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1= .pdf
            &= nbsp;       https://ftp.pwg.org/pub/pwg/ipp/slides/ipp-wg-agenda-april-19d1= .pptx
     
    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer
     
    _______________________________________________
    ipp mailing list
    ipp@pwg.org
     
    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://protect-us.mimecast.com/s/DOzzC9rB5BF61BL2ioHdd3?domain= =3Dpwg.org

    = --Apple-Mail=_612730EA-1B56-4B5A-B72F-5AC492BA2FB2-- --Apple-Mail=_72BCCD2F-2DE6-4BF9-8608-0DEA76412D2E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyL1r4ACgkQqskbKLDW 1N36PQ//QJISAYee1dJJAr77DsVl1VP1xQAnNICBYimdueeeivkuPLoy/PgLW+Cc 2+U22D8+0ZJxysjSRnWe+b23CEEnbGPXNyHO/vhVXvc/9WRtwdCrnj8cUlIDeP8u kC5IkTwN1ZJBxl9LXoHdpdoMV5kj3TXpO4p+FHvMW6dRSW12ahv2oGEPKtgBNBWk RPukO661fnHe6660yp2ABXsK6DNrK+ugosJYhI0FVsy8GxKDk4oVp14xZDjmhu9V oZaGFAtSAdhRkRbjkJVo5KpUjxNYdZ0QCvkZbKZRhfq4zFD1ltoVcTaK986+Q0Nz XCsioaZVfbtt0KGctsVZNlX2Q1RQFd/3lbTj2YbAddV857Ou6XK3bPUVHYNNPpxt GiHU4bEJCHBMYKDXh8Ma2a/JO3CF3hqeWuqEYauGQKG0gZfmE3/1KJ8cHCh7K1+V QiGb5383fA/w1U2n2+64fij1dGMhOQxEzqieyWy6NntEUIgNiD1rrO2W1EFMOo8N HmyV8ftftdJ7awrxtUtXdeD9Zet7EpGWqVCJjel9imYvpe9ESTA3sgCudequYY9T HQu4loxtKqQqW1lZLkBqj67VvwoxVLMWO9tIhyIR8kP34BRPx5RvZjlBU0E0/JYc Mxm1vEoFjB1HhjibpRk2VsoVoBN4E+K7S+nVb0Edwt0+O4bW274= =ujIB -----END PGP SIGNATURE----- --Apple-Mail=_72BCCD2F-2DE6-4BF9-8608-0DEA76412D2E-- --===============0055667492259294906== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============0055667492259294906==-- From ipp-bounces@pwg.org Fri Mar 15 10:52:31 2019 Return-Path: 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 E2A3E12958B for ; Fri, 15 Mar 2019 10:52:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 HANJPhntdw7h for ; Fri, 15 Mar 2019 10:52:29 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 196851277D7 for ; Fri, 15 Mar 2019 10:52:29 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 8D7B83F4D; Fri, 15 Mar 2019 17:52:27 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 0445A3BAA; Fri, 15 Mar 2019 17:52:22 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 1903F23E3; Fri, 15 Mar 2019 17:52:22 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 5F7B623E3 for ; Fri, 15 Mar 2019 17:52:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1552672339; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=C3J9uz77KajKgVvjVdR67s8Zyf1A1uBB3AttwWPExnU=; b=iKjq343etmBYN0Qa9TSUI5zwL8ANZq8l4XoenIyIGgSip13Y4/NDxh3pahGlVRMgXpeka2Ot14PwVHlZyEVdcTMfmj+r1GqN+pdETo+HXN7D74Fz5S9PlnP5CUPPOUWWxX3+WJ1n7SoO/hoKQYF4/FEGbiS2DCK4E4KyFhPQui4= Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03lp2050.outbound.protection.outlook.com [104.47.41.50]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-176-BydeZOZLMZCPuAcnxjYfuA-1; Fri, 15 Mar 2019 13:52:14 -0400 X-MC-Unique: BydeZOZLMZCPuAcnxjYfuA-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0856.NAMPRD84.PROD.OUTLOOK.COM (10.169.16.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.14; Fri, 15 Mar 2019 17:52:13 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::11f2:3d86:916f:9340%8]) with mapi id 15.20.1709.011; Fri, 15 Mar 2019 17:52:13 +0000 To: Michael Sweet Thread-Topic: [IPP] RFC: Relationship between job-retain-until-xxx and job-password Thread-Index: AQHU21fRuIIommX2Eke7nW6LA9iOcg== Date: Fri, 15 Mar 2019 17:52:13 +0000 Message-ID: References: <00239C4D-D794-4962-88E2-A00CBE1F654B@hp.com> In-Reply-To: <00239C4D-D794-4962-88E2-A00CBE1F654B@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.51.156] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ee5d09f6-1122-4b3b-603d-08d6a96ef488 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0856; x-ms-traffictypediagnostic: CS1PR8401MB0856: x-microsoft-antispam-prvs: x-forefront-prvs: 09778E995A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(39860400002)(346002)(376002)(136003)(189003)(199004)(6602003)(33656002)(105586002)(2616005)(99936001)(5660300002)(186003)(14454004)(446003)(11346002)(106356001)(86362001)(6506007)(68736007)(36756003)(6916009)(25786009)(97736004)(66066001)(316002)(486006)(7736002)(14444005)(99286004)(102836004)(83716004)(26005)(476003)(82746002)(4326008)(6246003)(8936002)(76176011)(256004)(6512007)(6436002)(6486002)(236005)(2906002)(229853002)(54896002)(81166006)(81156014)(3846002)(53546011)(53936002)(71190400001)(71200400001)(6116002)(478600001)(13513002)(21314003); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0856; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: nxWdk6dY3/5LGtnB+8+9lFOjgwMcI0WrakNydfkABBysF/EubT9L84+w1rj0JX8TfN5PVCSCGmUlEPyev7iKvvCBPxc+7wvPSGZLyy82tC0+FlY8vjXbLL6gEOo+dk7jRyCgHCc9EovFyAw3r6I2hOCPHcArUmUXkXjhUm1HoyAVJensh53AuWBMRtGvewOb7l6Hr80ccKwNFh2BvoBW/aSpiueiQTLTAci1bq7eyuoYAhSNhFJSsgQWsZWq7zRflPNIQyIGE5ap2+RJ3Wd6eixqb32mONpxiyLK56jK8cLJmPNPzYl0hnD+CtIH3Q846ZjTE9WPJtHhZYKRtIg5/bw160Q+4puAagZZyvvFyvL2cK1V6JU3Pa5BKzcYoz38zarXDzwNXaGbcIq3KxRTfFHChtX7F/aYHyrLy3FSF/w= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: ee5d09f6-1122-4b3b-603d-08d6a96ef488 X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2019 17:52:13.2677 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0856 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: Relationship between job-retain-until-xxx and job-password X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============5889668002239962027==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5889668002239962027== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_10CCD2A0-6AF6-4700-A507-13A9B654DD28"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_10CCD2A0-6AF6-4700-A507-13A9B654DD28 Content-Type: multipart/alternative; boundary="Apple-Mail=_EB6917E5-9471-4BDC-B0B9-C88E9772C8B5" --Apple-Mail=_EB6917E5-9471-4BDC-B0B9-C88E9772C8B5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 15, 2019, at 10:44 AM, Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: >=20 >> 4. WRT "job-print-password", what if (and I haven't thought this = completely through yet) we define another parallel attribute, = "job-password-action (type2 keyword)" that defines the semantics of the = "job-password" attribute, with the default being "hold-job" to preserve = the 1.0 semantics. Something like: >>=20 >> job-password-action (type2 keyword) >>=20 >> This operation attribute specifies how a Job is processed when the = "job-password" (section N.M.P) operation attribute is included in a Job = Creation request. Standard keyword values include: >>=20 >> - 'hold-job': The Job is placed in the 'pending-held' state and is = released when the "job-password" value is entered at the Printer's = console. >> - 'process-and-retain': The Job is placed in the 'pending' state and = it scheduled for processing without waiting for the User to enter the = "job-password" value at the Printer's console. >> - 'retain-only': The Job is placed in the 'completed' state as soon = as all Documents are received by the Printer. >>=20 >> Once in a terminating state, the Job is retained according to the = current value of its "job-retain-until-xxx" attributes. >=20 > I like it! I'll update my EPE draft to specify that and we can discuss = that first draft at our next IPP WG meeting. OK, more questions: 1. Should "job-password-action" be an operation attribute, or a Job = Template attribute? 2. We would want the semantic to be that if the "job-password-action" = was 'retain-only' or 'process-and-retain' then the "job-password" value = would become a "hidden Job Status attribute" so that the Printer would = require the "job-password" to be entered before any reprints could = occur. 3. I'm not clear on the semantic meaning of 'process-and-retain'? --Apple-Mail=_EB6917E5-9471-4BDC-B0B9-C88E9772C8B5 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii


    On Mar 15, 2019, at 10:44 AM, Kennedy, Smith (Wireless & = Standards Architect) via ipp <ipp@pwg.org> wrote:

    4. WRT "job-print-password", what if (and I = haven't thought this completely through yet) we define another parallel = attribute, "job-password-action (type2 keyword)" that defines the = semantics of the "job-password" attribute, with the default being = "hold-job" to preserve the 1.0 semantics. Something like:

    job-password-action (type2 keyword)

    This operation attribute specifies how a Job = is processed when the "job-password" (section N.M.P) operation attribute = is included in a Job Creation request. Standard keyword values = include:

    - 'hold-job': The Job is placed in = the 'pending-held' state and is released when the "job-password" value = is entered at the Printer's console.
    - = 'process-and-retain': The Job is placed in the 'pending' state and it = scheduled for processing without waiting for the User to enter the = "job-password" value at the Printer's console.
    - = 'retain-only': The Job is placed in the 'completed' state as soon as all = Documents are received by the Printer.

    Once = in a terminating state, the Job is retained according to the current = value of its "job-retain-until-xxx" attributes.

    I like it! I'll update my EPE = draft to specify that and we can discuss that first draft at our next = IPP WG = meeting.

    OK, more questions:

    1. Should = "job-password-action" be an operation attribute, or a Job Template = attribute?

    2. = We would want the semantic to be that if the "job-password-action" was = 'retain-only' or 'process-and-retain' then the "job-password" value = would become a "hidden Job Status attribute" so that the Printer would = require the "job-password" to be entered before any reprints could = occur.

    3. I'm = not clear on the semantic meaning of 'process-and-retain'?

     
    = --Apple-Mail=_EB6917E5-9471-4BDC-B0B9-C88E9772C8B5-- --Apple-Mail=_10CCD2A0-6AF6-4700-A507-13A9B654DD28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyL5kkACgkQqskbKLDW 1N0xFA//fv3OnD4AgW8CWbgvAypPhCclwgdypsg+n9YEut76SmALU/y77trJjxhv o7cpONaz50sfG7OFFsj3UZ+McL68sb5DfmEslBzoyFzBFw+7eYfcS3deIWrktYWe jORcRjHI5IYV6bOHNGpmqDCzQfKh37jIkUHDeqcnMMvZAT5PTC410JrGnsezXgF0 eDfJL7/931ig+xKGp2RafFEEkYA71yTq5pEyb+Wu1X7eM/3/g9ea8/gtt4WSald7 fZE46zDqrvkw4ejYIFFTVODIG6lFQBMxkYWt71/luV8XfUrwVenIE87KHdMzOtSp dD1cNLB6J3Dbe6RNPCNqEGZf9XhAh3YWa8HQT0Wia72v6zdOLi5/Ukl6F9aeOEl1 dB5JbG1CmocKhaAg0HHNIOvKVd2bDYbSnjm2AGjlmUY4GKVVeniopFwuLH/JwDa5 TqOwyONd1ihzYEcAxc6zagTnhBJ8AX38ldhpMxcnqK5ITPDravg8kuLmllr0x8Vx Iv7EtF6but+I5g3mEpRowlHGtMnXGcepRbTmBjUDHhWO9ToF6rOhAd3jf2x9YdE2 C6MryAvsNTodHMnz0ip7DA+VD/RTMQXArVR8MRTWm5O1YMrYgYSxKg1hia9OyGek yDIjKXT1VmUOQ2QtcxCtjJY1lwyty7jhZR0koKWYsx9JKja6abI= =UFCr -----END PGP SIGNATURE----- --Apple-Mail=_10CCD2A0-6AF6-4700-A507-13A9B654DD28-- --===============5889668002239962027== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5889668002239962027==-- From ipp-bounces@pwg.org Fri Mar 15 11:20:32 2019 Return-Path: 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 05010130EB1 for ; Fri, 15 Mar 2019 11:20:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 6xdShAvM6oij for ; Fri, 15 Mar 2019 11:20:30 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 13F79130EB9 for ; Fri, 15 Mar 2019 11:20:30 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id AA81B3F4A; Fri, 15 Mar 2019 18:20:29 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1832623E3; Fri, 15 Mar 2019 18:20:26 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 60E833BA9; Fri, 15 Mar 2019 18:20:24 +0000 (UTC) Received: from mail-yw1-xc34.google.com (mail-yw1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) by www.pwg.org (Postfix) with ESMTPS id 9CBF023E3 for ; Fri, 15 Mar 2019 18:20:23 +0000 (UTC) Received: by mail-yw1-xc34.google.com with SMTP id x129so8023074ywc.1 for ; Fri, 15 Mar 2019 11:20:23 -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=zSwlhlYQpQGgUwNO7czK9SbRgYGuYVl/iKg6chVG1rE=; b=syReqj+vkna1uK1lUYbxBgpyhqZlmfYfQSHiRHp1Su5J+Tg7LpPGwz9xe7ZOdCrg2m BRUJWbjaMAxeX1/Jl30yRMyQMvBqKiGMinMqBmYWwcx2qQlm9C3QQjCnR23/Bjv1EUe0 RunP5F3P0lwuPrRnQmTazjDSyDlQBM2tD1KkvbOGpWzRYb5F5cCU4Fjk7/5URV5JM4Qg ji1PuMfbqYrJbsSe66L3g9SuC2YV56kvvex7VWDmEJXN9q4EwP8/fYYsVmwq7Pxfh+28 PsE22RRX++6BWdTFbT/cUCh7yZd5i8PXyZumNYLq37vrCJYQUUzr2hq0Srxq+OBrTqtx ZBWQ== 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=zSwlhlYQpQGgUwNO7czK9SbRgYGuYVl/iKg6chVG1rE=; b=UcIyUtWPcsj21oTsTjxZSes1IQ5RdFGmDqv8Fr6YJQsps/Q8lOiIulDj1gApL7/rtR wC3jrc70eCYCIly3cyVED5OCvwhk952P4RYyI5WraNkCip6kjm9kk8F6N9CB6n+0Jsfs Nde9TWQBmMz66t+FUCbnrdcPDVioNfVZpcPu2aWQoGjrW08DHwnq8k/IOPpgGvmhj/MU DeYIYV4HuhDu2sMzAmvBpAhqDyG4SnytkV0K6HUId1u3V3AIhQ/EViwcZmXSwzavKhox Z5S/zv8HBf4aHOrrkkxvnvf/TyJHi073f7/AOSoEa7nVkHCfSQpswM7WkNQ0QfQ/ETsO yJXQ== X-Gm-Message-State: APjAAAUCIU4w2aJt07qR0YrLsfD8GwFzEWCvfpgDsD8UJA4g2pWRP0Ql l092/jfZp9G3jaGCl39wTV9oK31fXRuqhx8qXQY= X-Google-Smtp-Source: APXvYqzwAV5FsTUGrSUxQyjh9VAVV8BHlE3kmIqAg60xRIdhVQtSTVkbSjIHzE7EDKgJ9Sjn6L2TNfl9Kt26cBPOpmo= X-Received: by 2002:a81:4c91:: with SMTP id z139mr3971034ywa.315.1552674022682; Fri, 15 Mar 2019 11:20:22 -0700 (PDT) MIME-Version: 1.0 References: <2E159866-6DD6-40F0-92FD-4035F1F670BF@apple.com> In-Reply-To: <2E159866-6DD6-40F0-92FD-4035F1F670BF@apple.com> Date: Fri, 15 Mar 2019 14:20:09 -0400 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] Minutes from yesterday's concall posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6246480715071217981==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6246480715071217981== Content-Type: multipart/alternative; boundary="00000000000092f63d05842617ec" --00000000000092f63d05842617ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, As already noted in a later thread by Smith, there is a significant typo in these minutes: =E2=80=A2 consensus was to keep "job-retain-until" (type2 keyword) and "job-retain-until-time" (integer) and NOT implement "job-retain-until-date" (dateTime) There was a strong consensus against "job-xxx-until-date" attributes - they're clumsy and hard to use in a user friendly Client UI. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Mar 15, 2019 at 9:22 AM Michael Sweet via ipp wrote: > All, > > I have posted the minutes from yesterday's IPP workgroup conference call > to: > > > https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20190314.pd= f > > Our next conference call is on March 28, 2019 at 3pm ET. > > Many thanks to Smith for taking the minutes this week! > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --00000000000092f63d05842617ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    As already noted in a la= ter thread by Smith, there is a significant typo in these minutes:

    =E2=80=A2 consensus was to = keep "job-retain-until" (type2 keyword) and=20 "job-retain-until-time" (integer) and NOT implement=20 "job-retain-until-date" (dateTime)

    There was a strong consensus against "= ;job-xxx-until-date" attributes - they're clumsy
    and har= d to use in a user friendly Client UI.

    Cheers,
    - Ira

    Ira McDonald (Musicia= n / 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 WGIETF Designated Expert - IPP & Printer MIB
    Blue Roof Music / High N= orth Inc
    http://sites.google.com/site/bluer= oofmusic
    http://sites.google.com/site/hi= ghnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, M= I 49839=C2=A0 906-494-2434



    On Fri, Mar 15, 2019 at 9:22 AM Michael Sweet via = ipp <ipp@pwg.org> wrote:
    =
    All,

    I have posted the minutes from yesterday's IPP workgroup conference cal= l to:

    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20190314.pd= f

    Our next conference call is on March 28, 2019 at 3pm ET.

    Many thanks to Smith for taking the minutes this week!

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --00000000000092f63d05842617ec-- --===============6246480715071217981== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6246480715071217981==-- From ipp-bounces@pwg.org Fri Mar 15 17:33:56 2019 Return-Path: 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 B524712787F for ; Fri, 15 Mar 2019 17:33:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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=apple.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 M6EMcSi8DIwU for ; Fri, 15 Mar 2019 17:33:53 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id F2A5C127873 for ; Fri, 15 Mar 2019 17:33:52 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id B03193F4B; Sat, 16 Mar 2019 00:33:50 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 021FC23E3; Sat, 16 Mar 2019 00:33:46 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 216DD3BA9; Sat, 16 Mar 2019 00:33:43 +0000 (UTC) Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) by www.pwg.org (Postfix) with ESMTPS id 7B6932618 for ; Sat, 16 Mar 2019 00:33:42 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2G0WPgF007802; Fri, 15 Mar 2019 17:33:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=gg63vKvuIsxxJotyM9QzqK1mHNRf7GoJN2aH13/MEwE=; b=aLIHI+FDgHGhBGRcIdw0T0kS3U8QYNeBmZ7fmJ13e9/3iIM7/vagY+WdkE8dE/Iucxef Uz8vMyA4tt5KnyURkvRrPYj/JnMnwHsr8pJ63bse2N2uvj+cC/mjh41DKwK6Z1JBoFql KrTivsbHfOvmmigftr1D/6wRbYOFitizRsmGlXU4u6fVaIIYdlm0GC/vMaAzyWE3U6Ha OPiZimRiKTROEsX0Sj+pGdAnw7ShynTiLgjCBoMZgYEKDxpELPTfddK6tUQDlbvjr14q q7jwNiWK8t/rAMFqbm1JZyNHXGCylz8m8umnh17KD9C/enHbz3jHjFKxp1cgVqLMjjTL 8w== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2r4x15ge4b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 15 Mar 2019 17:33:41 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POF00DU1O846QA0@ma1-mtap-s01.corp.apple.com>; Fri, 15 Mar 2019 17:33:41 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POF00F00O0GRL00@nwk-mmpp-sz11.apple.com>; Fri, 15 Mar 2019 17:33:40 -0700 (PDT) X-Va-A: X-Va-T-CD: 670a24ae296eaf6dc00d9725bda32b87 X-Va-E-CD: ae49567c740043bcd7a1d0bbc775b670 X-Va-R-CD: b468ff01ba160168299a1d46f0a89242 X-Va-CD: 0 X-Va-ID: d07b74f9-f984-449a-ab5b-0aa583ec75d5 X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: ae49567c740043bcd7a1d0bbc775b670 X-V-R-CD: b468ff01ba160168299a1d46f0a89242 X-V-CD: 0 X-V-ID: 267db1d4-c7c0-490f-8aba-98975379a7a2 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-16_01:,, signatures=0 Received: from [17.235.18.108] (unknown [17.235.18.108]) by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POF007KZO83EJ00@nwk-mmpp-sz11.apple.com>; Fri, 15 Mar 2019 17:33:40 -0700 (PDT) In-reply-to: Date: Fri, 15 Mar 2019 20:33:31 -0400 Message-id: <60358BFE-3114-4880-86D6-04B089E2DC32@apple.com> References: <2E159866-6DD6-40F0-92FD-4035F1F670BF@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-16_01:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] Minutes from yesterday's concall posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: ipp-bounces@pwg.org Sender: "ipp" SXJhLAoKSSd2ZSBwb3N0ZWQgdXBkYXRlZCBtaW51dGVzIHdpdGggdGhlIGNvcnJlY3Rpb24uCgpB bHNvLCB0aGUgdGhyZWUgYXR0cmlidXRlcyB3ZXJlICJqb2ItcmV0YWluLXVudGlsICh0eXBlMiBr ZXl3b3JkIHwgbmFtZShNQVgpIiwgImpvYi1yZXRhaW4tdW50aWwtaW50ZXJ2YWwgKGludGVnZXIo MDpNQVgpKSIsIGFuZCAiam9iLXJldGFpbi11bnRpbC10aW1lIChkYXRlVGltZSkiLgoKVGhlIC10 aW1lIHN1ZmZpeCBtYXRjaGVzIHdoYXQgd2UgaGF2ZSBmb3Igam9iLWhvbGQtdW50aWwtdGltZSwg am9iLWRlbGF5LW91dHB1dC11bnRpbC10aW1lLCBwcmludGVyLWN1cnJlbnQtdGltZSwgZXRjLiBk YXRlVGltZSBhdHRyaWJ1dGVzLCBhbHRob3VnaCB3ZSBhbHNvIGhhdmUgdGltZS1hdC14eHggYW5k IG5vdGlmeS1sZWFzZS1leHBpcmF0aW9uLXRpbWUgd2hpY2ggYXJlIChpbnRlZ2VyKSBwcmludGVy LXVwLXRpbWUgdmFsdWVzIGFuZCBkYXRlLXRpbWUtYXQteHh4IChkYXRlVGltZSkgdmFsdWVzLi4u CgpUaGUgLWludGVydmFsIHN1ZmZpeCBtYXRjaGVzIHdoYXQgaXMgdXNlZCB3aGVuIGFuIGF0dHJp YnV0ZSByZXByZXNlbnRzIGEgdGltZSBpbnRlcnZhbCAoZS5nLiBkb2N1bWVudC1kYXRhLWdldC1p bnRlcnZhbCwgbm90aWZ5LWdldC1pbnRlcnZhbCwgbm90aWZ5LXRpbWUtaW50ZXJ2YWwsIHJldHJ5 LWludGVydmFsLCByZXN0YXJ0LWludGVydmFsKSBhbHRob3VnaCB3ZSBjb3VsZCBhbHNvIHVzZSAt ZHVyYXRpb24gKGUuZy4gbm90aWZ5LWxlYXNlLWR1cmF0aW9uKS4KCgo+IE9uIE1hciAxNSwgMjAx OSwgYXQgMjoyMCBQTSwgSXJhIE1jRG9uYWxkIHZpYSBpcHAgPGlwcEBwd2cub3JnPiB3cm90ZToK PiAKPiBIaSwKPiAKPiBBcyBhbHJlYWR5IG5vdGVkIGluIGEgbGF0ZXIgdGhyZWFkIGJ5IFNtaXRo LCB0aGVyZSBpcyBhIHNpZ25pZmljYW50IHR5cG8gaW4gdGhlc2UgbWludXRlczoKPiAKPiDigKIg Y29uc2Vuc3VzIHdhcyB0byBrZWVwICJqb2ItcmV0YWluLXVudGlsIiAodHlwZTIga2V5d29yZCkg YW5kICJqb2ItcmV0YWluLXVudGlsLXRpbWUiIChpbnRlZ2VyKSBhbmQgTk9UIGltcGxlbWVudCAi am9iLXJldGFpbi11bnRpbC1kYXRlIiAoZGF0ZVRpbWUpCj4gCj4gVGhlcmUgd2FzIGEgc3Ryb25n IGNvbnNlbnN1cyBhZ2FpbnN0ICJqb2IteHh4LXVudGlsLWRhdGUiIGF0dHJpYnV0ZXMgLSB0aGV5 J3JlIGNsdW1zeQo+IGFuZCBoYXJkIHRvIHVzZSBpbiBhIHVzZXIgZnJpZW5kbHkgQ2xpZW50IFVJ Lgo+IAo+IENoZWVycywKPiAtIElyYQo+IAo+IElyYSBNY0RvbmFsZCAoTXVzaWNpYW4gLyBTb2Z0 d2FyZSBBcmNoaXRlY3QpCj4gQ28tQ2hhaXIgLSBUQ0cgVHJ1c3RlZCBNb2JpbGl0eSBTb2x1dGlv bnMgV0cKPiBDby1DaGFpciAtIFRDRyBNZXRhZGF0YSBBY2Nlc3MgUHJvdG9jb2wgU0cKPiBDaGFp ciAtIExpbnV4IEZvdW5kYXRpb24gT3BlbiBQcmludGluZyBXRwo+IFNlY3JldGFyeSAtIElFRUUt SVNUTyBQcmludGVyIFdvcmtpbmcgR3JvdXAKPiBDby1DaGFpciAtIElFRUUtSVNUTyBQV0cgSW50 ZXJuZXQgUHJpbnRpbmcgUHJvdG9jb2wgV0cKPiBJRVRGIERlc2lnbmF0ZWQgRXhwZXJ0IC0gSVBQ ICYgUHJpbnRlciBNSUIKPiBCbHVlIFJvb2YgTXVzaWMgLyBIaWdoIE5vcnRoIEluYwo+IGh0dHA6 Ly9zaXRlcy5nb29nbGUuY29tL3NpdGUvYmx1ZXJvb2ZtdXNpYwo+IGh0dHA6Ly9zaXRlcy5nb29n bGUuY29tL3NpdGUvaGlnaG5vcnRoaW5jCj4gbWFpbHRvOiBibHVlcm9vZm11c2ljQGdtYWlsLmNv bQo+IFBPIEJveCAyMjEgIEdyYW5kIE1hcmFpcywgTUkgNDk4MzkgIDkwNi00OTQtMjQzNAo+IAo+ IAo+IAo+IE9uIEZyaSwgTWFyIDE1LCAyMDE5IGF0IDk6MjIgQU0gTWljaGFlbCBTd2VldCB2aWEg aXBwIDxpcHBAcHdnLm9yZz4gd3JvdGU6Cj4gQWxsLAo+IAo+IEkgaGF2ZSBwb3N0ZWQgdGhlIG1p bnV0ZXMgZnJvbSB5ZXN0ZXJkYXkncyBJUFAgd29ya2dyb3VwIGNvbmZlcmVuY2UgY2FsbCB0bzoK PiAKPiAgICAgICAgIGh0dHBzOi8vZnRwLnB3Zy5vcmcvcHViL3B3Zy9pcHAvbWludXRlcy9pcHB2 Mi1jb25jYWxsLW1pbnV0ZXMtMjAxOTAzMTQucGRmCj4gCj4gT3VyIG5leHQgY29uZmVyZW5jZSBj YWxsIGlzIG9uIE1hcmNoIDI4LCAyMDE5IGF0IDNwbSBFVC4KPiAKPiBNYW55IHRoYW5rcyB0byBT bWl0aCBmb3IgdGFraW5nIHRoZSBtaW51dGVzIHRoaXMgd2VlayEKPiAKPiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBNaWNoYWVsIFN3 ZWV0LCBTZW5pb3IgUHJpbnRpbmcgU3lzdGVtIEVuZ2luZWVyCj4gCj4gX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBpcHAgbWFpbGluZyBsaXN0Cj4gaXBw QHB3Zy5vcmcKPiBodHRwczovL3d3dy5wd2cub3JnL21haWxtYW4vbGlzdGluZm8vaXBwCj4gX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiBpcHAgbWFpbGlu ZyBsaXN0Cj4gaXBwQHB3Zy5vcmcKPiBodHRwczovL3d3dy5wd2cub3JnL21haWxtYW4vbGlzdGlu Zm8vaXBwCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KTWljaGFlbCBTd2VldCwgU2VuaW9yIFByaW50aW5nIFN5c3RlbSBFbmdpbmVlcgoK X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaXBwIG1haWxp bmcgbGlzdAppcHBAcHdnLm9yZwpodHRwczovL3d3dy5wd2cub3JnL21haWxtYW4vbGlzdGluZm8v aXBwCg== From ipp-bounces@pwg.org Fri Mar 15 17:49:49 2019 Return-Path: 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 F322312787F for ; Fri, 15 Mar 2019 17:49:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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=apple.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 EiTh5is-XScv for ; Fri, 15 Mar 2019 17:49:46 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 6A66C1279B3 for ; Fri, 15 Mar 2019 17:49:46 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 5C0303F4E; Sat, 16 Mar 2019 00:49:45 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id C28DE2894; Sat, 16 Mar 2019 00:49:40 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A8E623BA9; Sat, 16 Mar 2019 00:49:38 +0000 (UTC) Received: from nwk-aaemail-lapp02.apple.com (nwk-aaemail-lapp02.apple.com [17.151.62.67]) by www.pwg.org (Postfix) with ESMTPS id 3D2B523E3 for ; Sat, 16 Mar 2019 00:49:38 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp02.apple.com [127.0.0.1]) by nwk-aaemail-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2G0lGEo046376; Fri, 15 Mar 2019 17:49:36 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=KlNT8Sa56GqqNVeR9c//AksWkOXXQhcAwrDGKHfVWlg=; b=uTaem8YPg+1xM4lSMfC2503aHlCdXfiv2h5RO6B14KzUN8zMsP4H+fpoi5uzTz5kJRJI kJDLk5Wran3BNRZlNhTvWQnQXw4o0kvCKCbccaP5PMhQUCpTXTPXzB/wYntOqM4oHnMS TQlQ80gMvHt0Y+8zATyLxHMgxALyz2h+tj2nZvUWuU4V5FOUj996ArbIsJjbX6MNEfRW 4nqVZ6MyRx0yKS5exevsZIsajWDSgL+31ZOwWvhV1xJim+D6uhPgm0qsSv/Sv1lvKJhD QvhyfnpOYNtjn5tJoISY9nqg/hz7l8tGvKUtLuhJe6MmJkzIPR0Zh/gEF0IRiaom/55w VA== Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by nwk-aaemail-lapp02.apple.com with ESMTP id 2r4axv9wpq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 15 Mar 2019 17:49:36 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POF002QGOYO9GO0@mr2-mtap-s03.rno.apple.com>; Fri, 15 Mar 2019 17:49:36 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POF00D00OR2DD00@nwk-mmpp-sz11.apple.com>; Fri, 15 Mar 2019 17:49:36 -0700 (PDT) X-Va-A: X-Va-T-CD: e144540b7342dfdd5f6898b05c7d1e1b X-Va-E-CD: 8af68d5ef78ed0e082ebd6acefa5ff90 X-Va-R-CD: 04756427fec1dc13917274e39398d95a X-Va-CD: 0 X-Va-ID: fa66c863-eabf-4fd6-a44c-0669d21778c8 X-V-A: X-V-T-CD: 499a24534fbaffe09fd540dd02388733 X-V-E-CD: 31c147b0e269cbcd3d82202ef6e3a30c X-V-R-CD: f02267b5b0ed603922f0f1778ea68ed4 X-V-CD: 0 X-V-ID: cefd37e6-49d4-4f28-8fdc-7fe3c0e25cbd X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-16_01:,, signatures=0 Received: from [17.235.18.108] (unknown [17.235.18.108]) by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POF008RHOYN7T00@nwk-mmpp-sz11.apple.com>; Fri, 15 Mar 2019 17:49:36 -0700 (PDT) In-reply-to: Date: Fri, 15 Mar 2019 20:49:27 -0400 Message-id: <192B77BE-153C-45A8-870C-24257F0DD803@apple.com> References: <00239C4D-D794-4962-88E2-A00CBE1F654B@hp.com> To: Smith Kennedy X-Mailer: Apple Mail (2.3445.102.3) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-16_01:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: Relationship between job-retain-until-xxx and job-password X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" Smith, > On Mar 15, 2019, at 1:52 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp wrote: >> ... >> I like it! I'll update my EPE draft to specify that and we can discuss that first draft at our next IPP WG meeting. > > OK, more questions: > > 1. Should "job-password-action" be an operation attribute, or a Job Template attribute? Good question. Ordinarily we would make it a Job Template attribute, but I can see the argument for not exposing too many details of "job-password" usage and "job-password-encryption" is also an operation attribute. Of course, the 'job-password-wait' keyword in "job-state-reasons" will expose the fact that a job is held for a password at the console, but we're stuck with that so an operator or user knows some action is required... OK, I think I'm slightly more in favor of it being an operation attribute, if for any other reason that I think there will be less chance for an implementor to mess things up... :) > 2. We would want the semantic to be that if the "job-password-action" was 'retain-only' or 'process-and-retain' then the "job-password" value would become a "hidden Job Status attribute" so that the Printer would require the "job-password" to be entered before any reprints could occur. I think we should require job-password for any action - yes, a new semantic for Resubmit-Job, but I think one we can get away with since the combination of job-password and Resubmit-Job was not fully specified... (unlike save-disposition and proof-print) > 3. I'm not clear on the semantic meaning of 'process-and-retain'? Print it (without password) and then retain for later reprint (using the password). So basically: - 'hold-job' is "hold the job until the password is entered, then print and retain" - 'process-and-retain' is "print the job immediately and then retain" - 'retain-only' is "do not print the job but retain the job for possible later printing" Any subsequent reprints require the password. I guess the question is whether the "job-retain-until" for the resubmitted job should be "none" or the copied job should also have the same job-password-xxx values? (I can see the latter actually being a benefit) _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Sun Mar 17 09:56:03 2019 Return-Path: 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 7CD4812D550 for ; Sun, 17 Mar 2019 09:56:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 mKU2mqs14kjp for ; Sun, 17 Mar 2019 09:56:01 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id E7F6B12D826 for ; Sun, 17 Mar 2019 09:56:00 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 7AC623F4C; Sun, 17 Mar 2019 16:55:59 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 213063592; Sun, 17 Mar 2019 16:55:50 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 0299C3A7D; Sun, 17 Mar 2019 16:55:49 +0000 (UTC) Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) by www.pwg.org (Postfix) with ESMTPS id 5082523E3 for ; Sun, 17 Mar 2019 16:55:48 +0000 (UTC) Received: by mail-yw1-xc2e.google.com with SMTP id z191so11113270ywa.6 for ; Sun, 17 Mar 2019 09:55:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FEtlKGkbdm9ZCgbn9C4f5vhsJZcZaIWfr/7AEMq2EEo=; b=iPiMYz4XKoysYe/Wgq+iMTvGkHZRp5VIYfxMOtygPfHuGdBx4q01kjV3sbEsfZKr20 +nXVE/MrPpVB5oc7a2DxsZO9EkN7cU9MQEMY+Jvdla0XU0Z92ZkiDskKGxioekT99N/7 SIjOapkH2lR316YEE/G+uxuKwEyPV/tyYBcBuwKs4LINWOJY+qA3uDyHwSqfZz25AuxH e0rnEtGaxLnhTIeoPw5pg3Qg8iphkO6OnLx4NZkrhbJFudbWCBbRAAGJsqZFZGKaePzc Zagsr4FE82ZXfzC1gSuX1ER1667wbRDcMbIffN/uDzMEZjmz+ujmDE2+4nclWPdWdAHi ylCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FEtlKGkbdm9ZCgbn9C4f5vhsJZcZaIWfr/7AEMq2EEo=; b=FfQaG7ZUGVY9sfLdDD1hPxR5dSk+/Bls3RSwKxnm+txUdnuTaMNwUxl7D0twA6aKWZ 9vkZIVd9jESfmK6zfoM9FB0HUSMZDIpiiHam6djArcTHoVd/Wa7nkoMnMQt8A8RHvCdL 9atdjLMuVyVffEDHvMBDReVKabneBhSk3kX0EBUvW3MdctpGbuJxOweWrrXI3SmW8Sp/ tc/R/+EVJBmAxxVdIo5NUKBi1pU+YbLyMHKpqCDNMWI3tQ6wfpWswcQucLKrdEu70bXn 9xdaIsBq5BVp7JYaj+d/b7W/NTFAfIc7nCs5ZkJO/8c+st8Rj56tENOqhY5Pb0lZ6cdv 7FwA== X-Gm-Message-State: APjAAAX/c0ohH06WZsUASlyS5kV+LLfuG1CjFmMdeKZyxtHlfNcz4cOk 3zewnauqKT6G3o8gPSaapwdDPcxxb9ft6heoIGXxVTTT X-Google-Smtp-Source: APXvYqxFyJdKh3LAc+rji3cPLKLuDItHfpob1r1Xzif0lxM7B6XAGN5KrMsri2u4xcS80tgLv7LNR9lIPM7IxhGWL04= X-Received: by 2002:a81:5f86:: with SMTP id t128mr11355015ywb.467.1552841747329; Sun, 17 Mar 2019 09:55:47 -0700 (PDT) MIME-Version: 1.0 Date: Sun, 17 Mar 2019 12:55:35 -0400 Message-ID: To: "ipp@pwg.org" , Ira McDonald Subject: [IPP] Posted MFD Alerts Stable draft (17 March 2019) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============8107299634772095676==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8107299634772095676== Content-Type: multipart/alternative; boundary="000000000000bdf65f05844d2497" --000000000000bdf65f05844d2497 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I've just posted a new *Stable* draft of MFD Alerts (was PWG 5105.3-2012) with corrections per PWG F2F review in February 2019 and IPP WG Last Call in March 2019 at: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190317.docx - Word clean version https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190317-rev.docx - Word source w/ redlines https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190317.pdf - PDF clean version https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190317-rev.pdf - PDF w/ redlines This document has completed IPP WG Last Call (without comments, except for the Overview of Changes) and is now ready for PWG Call for Objections (errata update). Cheers, - Ira ----------------------------------------------------- Change History 17 March 2019 - Stable draft revision (Ira McDonald) =E2=80=93 changes per IPP WG last ca= ll (March 2019). - Revised entire document to justify all paragraphs (but not tables). - Revised section 2.1 Conformance Terminology to add =E2=80=9CDEPRECATED=E2= =80=9D (used) and =E2=80=9COBSOLETE=E2=80=9D (for completeness). - Added section 10 Overview of Changes. --000000000000bdf65f05844d2497 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    I've=C2=A0 just posted a new *Stable* draft of MFD Alerts (was PWG 5105.3-2012)
    with corrections per PWG F2= F review in February 2019 and IPP WG Last
    Call in March 2019= at:

    - Word clean version

    <= div>https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfda= lerts11-20190317-rev.docx
    - Word source w/ redlines

    - PDF clean version
    - PDF w/ redlines

    This document has completed IPP WG Last Call (without comments, except
    for the Overview of Changes) and is now ready for PWG Call for Obj= ections
    (errata update).

    Cheers= ,
    - Ira

    --------------------------------= ---------------------
    Change History
    17 March 2019

    - Stable draft = revision (Ira McDonald) =E2=80=93 changes per IPP WG last call (March 2019)= .
    - Revised entire document to justify all paragraphs (but not tables).<= br>- Revised section 2.1 Conformance Terminology to add =E2=80=9CDEPRECATED= =E2=80=9D (used) and =E2=80=9COBSOLETE=E2=80=9D (for completeness).
    - Ad= ded section 10 Overview of Changes.


    --000000000000bdf65f05844d2497-- --===============8107299634772095676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8107299634772095676==-- From ipp-bounces@pwg.org Mon Mar 18 08:16:11 2019 Return-Path: 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 C23FE1310F2 for ; Mon, 18 Mar 2019 08:16:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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=apple.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 WyNHvPmpX6B6 for ; Mon, 18 Mar 2019 08:16:09 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id AF12713108E for ; Mon, 18 Mar 2019 08:16:09 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 9AD6F3F9C; Mon, 18 Mar 2019 15:16:06 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 66EE927B3; Mon, 18 Mar 2019 15:16:03 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 20C6B378A; Mon, 18 Mar 2019 15:16:02 +0000 (UTC) Received: from nwk-aaemail-lapp03.apple.com (nwk-aaemail-lapp03.apple.com [17.151.62.68]) by www.pwg.org (Postfix) with ESMTPS id A8F052618 for ; Mon, 18 Mar 2019 15:16:01 +0000 (UTC) Received: from pps.filterd (nwk-aaemail-lapp03.apple.com [127.0.0.1]) by nwk-aaemail-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2IF1jju045316 for ; Mon, 18 Mar 2019 08:16:01 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=PBrFBDC1QSoUaOhoawy/h9qzdV0TMz1TrZhRj2uHmIk=; b=TNo6q4heXlWl66JICsm4hatO6CAEchMPbjF+WZlQ2sQFQhPnoI0ME2fTlcwJxY3mZ8Oh weavfWIHEIWG1qOqfcwgynDOjqszFqCcqHXOV/o7TCX6Ow4lh2rvaNkkBgCkNLjayMi6 vH0GzdKijDml7k2FMFrz4XEnmuxLmFiN/xjQ1exs8CrSXVjVp43qyLt7Ftak9mlt87xG PpS/Dh/RiK2slCLrU6n6CSjsD04Z6Ek2/Dh6XYeF5N9q1xqXzCZLaYX3KpmO7uVHEO5p XTTpJlGKzV6C0pXtzKYAoWTc2FIBLpaWHcB/LfzvKkpavAckQHY1RqTjFvodCZIYcVDt HQ== Received: from ma1-mtap-s03.corp.apple.com (ma1-mtap-s03.corp.apple.com [17.40.76.7]) by nwk-aaemail-lapp03.apple.com with ESMTP id 2r9gsx17ne-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 18 Mar 2019 08:16:01 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s03.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POK00DMLIEN5OA0@ma1-mtap-s03.corp.apple.com> for ipp@pwg.org; Mon, 18 Mar 2019 08:16:00 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POK00I00ID51W00@nwk-mmpp-sz09.apple.com>; Mon, 18 Mar 2019 08:16:00 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 4fdad8bcc23ed1e8b274fbb55dffe666 X-Va-R-CD: 100bc2c99c6d62efd5885fb587410681 X-Va-CD: 0 X-Va-ID: 08d1e56f-c69c-4c26-8260-c2473c4f8f20 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 4fdad8bcc23ed1e8b274fbb55dffe666 X-V-R-CD: 100bc2c99c6d62efd5885fb587410681 X-V-CD: 0 X-V-ID: d8312e0f-437b-46c1-84a6-6c10bef2fa99 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-18_10:,, signatures=0 Received: from [17.235.51.187] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POK0036PIELGH70@nwk-mmpp-sz09.apple.com>; Mon, 18 Mar 2019 08:15:59 -0700 (PDT) Date: Mon, 18 Mar 2019 11:15:57 -0400 Message-id: To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-18_10:, , signatures=0 Subject: [IPP] Updated stable draft of IPP Document Object v1.1 posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted an updated stable draft of the IPP Document Object v1.1 specification to: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippdocobject11-20190318.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippdocobject11-20190318.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippdocobject11-20190318-rev.pdf This update includes the new DEPRECATED and OBSOLETE terminology and updates the change history with the rationale for the changes. As a process reminder, errata don't need prototype reports to go to stable status, but FWIW there are a few hundred million IPP printers in service that implement this specification so I think we're good... :) _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Mar 18 08:39:14 2019 Return-Path: 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 5299A13115C for ; Mon, 18 Mar 2019 08:39:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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=apple.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 pr5b5S6Kps6D for ; Mon, 18 Mar 2019 08:39:11 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 1B78F1310FB for ; Mon, 18 Mar 2019 08:39:10 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 7A4D73F4C; Mon, 18 Mar 2019 15:39:10 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 9FBD627B3; Mon, 18 Mar 2019 15:39:06 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 4B8F923E3; Mon, 18 Mar 2019 15:39:05 +0000 (UTC) Received: from ma1-aaemail-dr-lapp01.apple.com (ma1-aaemail-dr-lapp01.apple.com [17.171.2.60]) by www.pwg.org (Postfix) with ESMTPS id C66C523E3 for ; Mon, 18 Mar 2019 15:39:04 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp01.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2IFVUtt023441 for ; Mon, 18 Mar 2019 08:39:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=OitcDCYyZGl8GhkzMLbjHGpudW2y3hbKLznm0/eunto=; b=S5PBski6UnFe4l7KyeUDMxISwJa2NATPvwna4OWugpWlMl+PU/VoF2tr5Sn9Yz69BfjI t+VeKsgyIGNo3dUJBsgUsETvT64ZcRuKcsBq7U6NTp9wzTP0ua8YNuAVXJuSM0ujOHJn aF1j0ZxsSWvBhF0wyqdp88ZOjmFN2iiAmt+45TfzCDXHLPq9LrbMGdoIfp+O4te2Smuk wquXr2uu3SEUlUxRhCRMWnu1PhBR2PtYwxmfL/ygIXoI5KQqeaMn/GQtvCV6McDuXLpS Y/SwoJG3uM7ng9x5AADRgD72YHA+zurIhaiT3LWIZ6CAk6O73ZHxdVMZSk10nSzuq0h5 vA== Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by ma1-aaemail-dr-lapp01.apple.com with ESMTP id 2r8yt7jdn6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 18 Mar 2019 08:39:03 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz09.apple.com (nwk-mmpp-sz09.apple.com [17.128.115.80]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POK005XDJH2XE60@ma1-mtap-s02.corp.apple.com> for ipp@pwg.org; Mon, 18 Mar 2019 08:39:03 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz09.apple.com by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POK00B00JEZF700@nwk-mmpp-sz09.apple.com>; Mon, 18 Mar 2019 08:39:02 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: b7bffb5a68ee5f338e9a941508de35e3 X-Va-R-CD: c161cea2e8fad147b6202c8f62cbec25 X-Va-CD: 0 X-Va-ID: c1ff88db-0659-4a11-a28e-d453619a7853 X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: b7bffb5a68ee5f338e9a941508de35e3 X-V-R-CD: c161cea2e8fad147b6202c8f62cbec25 X-V-CD: 0 X-V-ID: 24ffa74e-f3cf-4246-8e27-83898a5ca3ec X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-18_10:,, signatures=0 Received: from [17.235.51.187] by nwk-mmpp-sz09.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POK000OQJGYQ220@nwk-mmpp-sz09.apple.com>; Mon, 18 Mar 2019 08:39:00 -0700 (PDT) Date: Mon, 18 Mar 2019 11:38:58 -0400 Message-id: <9770ACD5-B1D1-409F-A882-0BCBBEEFB2C3@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-18_10:, , signatures=0 Subject: [IPP] LCRC draft of PWG Safe G-Code Subset for 3D Printing posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D Printing best practice document to: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt The only comment and change is to fix two broken section references in table 1. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Mar 18 12:59:40 2019 Return-Path: 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 944BD12798C for ; Mon, 18 Mar 2019 12:59:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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_PASS=-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 0kQcUFxt3aOz for ; Mon, 18 Mar 2019 12:59:38 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 44050127987 for ; Mon, 18 Mar 2019 12:59:38 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id EA2933F9C; Mon, 18 Mar 2019 19:59:37 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 33DDF27B3; Mon, 18 Mar 2019 19:59:34 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id B9377378A; Mon, 18 Mar 2019 19:59:32 +0000 (UTC) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) by www.pwg.org (Postfix) with ESMTPS id F1BF723E3 for ; Mon, 18 Mar 2019 19:59:31 +0000 (UTC) Received: by mail-yw1-xc2c.google.com with SMTP id q128so13946984ywg.8 for ; Mon, 18 Mar 2019 12:59:31 -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=0F7R5QS/SEUXPph9/Kzt5r8FN8z8V3PfP5dW+/VC2R4=; b=biPKpmoNgJvV8F8RgU9bRVS0Btzy0Rt/EXrS2Mh9mUXC9WhlY1oB9XaQuPb9dtZtTi B8j+FGvTVYuDb4ajPc2Uyz5FWFtZPih9J8gWlV3vX61V3yc85vxIH61XUmxMsSWGI8GL 81XVQ9A7+6KKQFnxtUUTBLjr5NX2hzvjlgRm5NnrZKL81i2MHd5ZtV6qRVfkBmJB3Wv4 dIKTH8NTtjJwC36K7CfKSpfj4PsyNzOXxJUyLUTzghbQruunk+YZ/LZQDcvSj7IQ0B5N 9c9FnRIAUWkBgLYIRM2Cp7PyfzARkLCktBMZjC4EQH3G99/mvrHhBz2Kz9BqJJjKLYLQ eXBQ== 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=0F7R5QS/SEUXPph9/Kzt5r8FN8z8V3PfP5dW+/VC2R4=; b=Wxm+ODcHbm5sjEHBIU1WE2lhWw156xmYIT635U5M2z/kKybCtuL0j5u0VT4LSdOtTb uBXPdcgPn4C2E49ZM3DhhjVmhKtS7dMMVeT/fbLVV+IKgz0MPAC66SOC3OpcN/0RtGSS Phu+6XEzGlPWnNqe77gBmWqaw8U1VheXexY7ISJrUFCgVXfLSdnAGS19k2tDXwi9t4Ig 0RcUG34TvJHdl2X+Z/7sQOVhAk2C2kdNLy0/hqv+HXniT6LAZCQyuAUIJO8mg28uNxFQ 8ZEW9v+nk7AkJL0x9wQDd9ygbFRs2v8tKSVBhJSxyw36JGrpIF0Ij2QfYilInIQZeRjP +7QQ== X-Gm-Message-State: APjAAAUNrN+xxRdJBnO4gDQBMO5wOXZ0PNbLUZx1m8eoUZJgWjpKVhzj aXbyM1KptH7zdFJnNwswaadzJOawGoaGbW+j3zM= X-Google-Smtp-Source: APXvYqyxks+zI+AyYX3NalpxVbhYTGrnqLRpjDsxZXVrE9K/kBBL8i3b/Br8h/fyeztTICmV+aVI44qBCkqbh1JnIjU= X-Received: by 2002:a0d:c9c2:: with SMTP id l185mr15670966ywd.227.1552939171195; Mon, 18 Mar 2019 12:59:31 -0700 (PDT) MIME-Version: 1.0 References: <9770ACD5-B1D1-409F-A882-0BCBBEEFB2C3@apple.com> In-Reply-To: <9770ACD5-B1D1-409F-A882-0BCBBEEFB2C3@apple.com> Date: Mon, 18 Mar 2019 15:59:19 -0400 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] LCRC draft of PWG Safe G-Code Subset for 3D Printing posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============4400622754191857862==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4400622754191857862== Content-Type: multipart/alternative; boundary="000000000000a82d7a058463d396" --000000000000a82d7a058463d396 Content-Type: text/plain; charset="UTF-8" Hi Mike, Two "successful" downloads of the LCRC plaintext file still yield a zero-length file. Same info from the PWG direct FTP site. Huh? 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Mar 18, 2019 at 11:39 AM Michael Sweet via ipp wrote: > All, > > I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D Printing > best practice document to: > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf > https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt > > The only comment and change is to fix two broken section references in > table 1. > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --000000000000a82d7a058463d396 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    Two "successfu= l" downloads of the LCRC plaintext file still yield a zero-length
    file.=C2=A0 Same info from the PWG direct FTP site.=C2=A0 Huh?

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architect)
    Co-Chair - TCG= Trusted Mobility Solutions WG
    Co-Chair - TCG Metadata Access Pro= tocol SG
    Chair - Linux Foundation Open Printing W= G
    Secretary - IEEE-ISTO Printer Working Group
    Co-Chair - IEEE-ISTO PW= G Internet Printing Protocol WG
    IETF Designated Expert - IPP & Print= er MIB
    Blue Roof Music / High North Inc
    = http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gmail.comPO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434



    On Mon, Mar 18, = 2019 at 11:39 AM Michael Sweet via ipp <i= pp@pwg.org> wrote:
    All,

    I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D Printing = best practice document to:

    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https:= //ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https:/= /ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 htt= ps://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://ftp.pw= g.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt

    The only comment and change is to fix two broken section references in tabl= e 1.

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

    _______________________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --000000000000a82d7a058463d396-- --===============4400622754191857862== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4400622754191857862==-- From ipp-bounces@pwg.org Mon Mar 18 13:22:03 2019 Return-Path: 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 74BF212F1A2 for ; Mon, 18 Mar 2019 13:22:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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_PASS=-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=apple.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 ceMWjHL3em-C for ; Mon, 18 Mar 2019 13:22:01 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 859C012E036 for ; Mon, 18 Mar 2019 13:22:01 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id D51613F4C; Mon, 18 Mar 2019 20:21:58 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id B2EF427B3; Mon, 18 Mar 2019 20:21:53 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 6BA43378A; Mon, 18 Mar 2019 20:21:53 +0000 (UTC) Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) by www.pwg.org (Postfix) with ESMTPS id A40D223E3 for ; Mon, 18 Mar 2019 20:21:52 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2IKLkoR049222; Mon, 18 Mar 2019 13:21:51 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : subject : from : in-reply-to : date : cc : message-id : references : to; s=20180706; bh=82awpcLrMdIfLma902ZsPhrONCrvB8GT4+C5KH+oHLI=; b=BxmK8Ka3T74cQKyL1IVWCBZ9O0bjGFAK0e2iwW/hFk95N31ZB0rOu6TqYzzwKTN5Nsau KVzX/VbtHH9Bs75ZU8G6Riawf//4kVO/HCD/KMbNNGuONQ6tqTlJmPXvTMDDK9alz0UH o5XK2w3Qlj6tAP4BQvjjCpMIBmGyM8Yr5WgC/vSYc85pihzaUdkklB5TFlTZZ8UYk1gC CT36R5YdHk1qH8oq3zyxDpdC7k2GmCDs/PlvjVSUIQBr+CNcA7xbiyW+c7ApV6n6Eg60 AZW+3n5VSxslefbziYDZTCatjpqMUe+IIpv1NR7bxsxsD2b8WncHw7qX5+Hxg2LNJjvF mw== Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 2ragxrsnu5-15 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 18 Mar 2019 13:21:50 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POK00I6DWKD2D10@mr2-mtap-s01.rno.apple.com>; Mon, 18 Mar 2019 13:21:49 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POK00H00WBFK500@nwk-mmpp-sz12.apple.com>; Mon, 18 Mar 2019 13:21:49 -0700 (PDT) X-Va-A: X-Va-T-CD: 670a24ae296eaf6dc00d9725bda32b87 X-Va-E-CD: 5677b6fedd7ea35282dbbcec2dc8800e X-Va-R-CD: 598df3cb39ed6cd384294eccb1d090f8 X-Va-CD: 0 X-Va-ID: 856f17a6-60fa-4058-b897-4c31cd18230b X-V-A: X-V-T-CD: b9f258579cf7b6da936a7bc8b179fbc8 X-V-E-CD: 5677b6fedd7ea35282dbbcec2dc8800e X-V-R-CD: 598df3cb39ed6cd384294eccb1d090f8 X-V-CD: 0 X-V-ID: 3d05d0e9-102c-4f0d-bc8e-92068e83d79b X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-18_13:,, signatures=0 Received: from [17.235.51.187] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POK002TMWKA1P60@nwk-mmpp-sz12.apple.com>; Mon, 18 Mar 2019 13:21:48 -0700 (PDT) In-reply-to: Date: Mon, 18 Mar 2019 16:21:45 -0400 Message-id: <66457872-874A-4FEB-B340-1F5BCBC85A2F@apple.com> References: <9770ACD5-B1D1-409F-A882-0BCBBEEFB2C3@apple.com> To: Ira McDonald X-Mailer: Apple Mail (2.3445.104.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-18_13:, , signatures=0 Cc: PWG IPP Workgroup Subject: Re: [IPP] LCRC draft of PWG Safe G-Code Subset for 3D Printing posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: multipart/mixed; boundary="===============5700662216273214810==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5700662216273214810== Content-type: multipart/alternative; boundary="Boundary_(ID_tINFrRdAcx4rVR1gy+BX1w)" --Boundary_(ID_tINFrRdAcx4rVR1gy+BX1w) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Hmm, I think my FTP software has trouble with short files (or something else unfortunate is happening) - was having the same problem with uploading the IPP WG web page, too. Try it now (uploaded via SSH...) > On Mar 18, 2019, at 3:59 PM, Ira McDonald wrote: > > Hi Mike, > > Two "successful" downloads of the LCRC plaintext file still yield a zero-length > file. Same info from the PWG direct FTP site. Huh? > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Mon, Mar 18, 2019 at 11:39 AM Michael Sweet via ipp > wrote: > All, > > I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D Printing best practice document to: > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf > https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt > > The only comment and change is to fix two broken section references in table 1. > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp _________________________________________________________ Michael Sweet, Senior Printing System Engineer --Boundary_(ID_tINFrRdAcx4rVR1gy+BX1w) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable Hmm, = I think my FTP software has trouble with short files (or something else = unfortunate is happening) - was having the same problem with uploading = the IPP WG web page, too.

    Try it now (uploaded via SSH...)


    On Mar 18, 2019, at 3:59 PM, Ira McDonald <blueroofmusic@gmail.com> wrote:

    Hi Mike,

    Two "successful" downloads of the LCRC = plaintext file still yield a zero-length
    file.  = Same info from the PWG direct FTP site.  Huh?

    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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Mon, Mar 18, 2019 at 11:39 AM = Michael Sweet via ipp <ipp@pwg.org> wrote:
    All,

    I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D = Printing best practice document to:

            https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.d= ocx
            https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.p= df
            https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-r= ev.pdf
            https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt<= br class=3D"">
    The only comment and change is to fix two broken section references in = table 1.

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

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

    _________________________________________________________
    Michael Sweet, Senior Printing = System Engineer

    = --Boundary_(ID_tINFrRdAcx4rVR1gy+BX1w)-- --===============5700662216273214810== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5700662216273214810==-- From ipp-bounces@pwg.org Mon Mar 18 13:25:13 2019 Return-Path: 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 1B66913118C for ; Mon, 18 Mar 2019 13:25:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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_PASS=-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 gulWMdK6Cf_0 for ; Mon, 18 Mar 2019 13:25:10 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id B93C2131181 for ; Mon, 18 Mar 2019 13:25:10 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id AD5213B9D; Mon, 18 Mar 2019 20:25:10 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 5054523E3; Mon, 18 Mar 2019 20:25:05 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id D90F6378A; Mon, 18 Mar 2019 20:25:03 +0000 (UTC) Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) by www.pwg.org (Postfix) with ESMTPS id DA3BC23E3 for ; Mon, 18 Mar 2019 20:25:02 +0000 (UTC) Received: by mail-yw1-xc2f.google.com with SMTP id 189so14019957ywi.3 for ; Mon, 18 Mar 2019 13:25:02 -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=DywA0qqnB5xdk8mpDgJf7dPcWpTVynt/ntkpA9DD29A=; b=C3YtNcEcmL1N6FMwgIimKemzaxH1CHLyq0g1MVije6m6QnqNwAq3kj+QwYljW6d5Wx Sj5loWJxwebd2WN7jGid0AomWX3w3Ur2mCUXZy0taIoekWVp/OdRXWq4RBvTMMwXfRy7 /C5OsI+76FMHKtfUmXLmRkoyFE/Zs+zcDtHVfVqGZhBZXUQ8qzvySg4E/BtWSl9n7aBQ MQbuR2h8eBGMmF0F1GKGr1Pn0GNKpAfBHbfnsAHDg7z7/TLJmKd21exHcPjT30RJ11xO 2/FsK6lYY1MWhJPX01R16T/v+cS2ow25RMFHpzVph8w1pPIrg+0PJEGbGDS3qMJRZ1Bb xqSg== 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=DywA0qqnB5xdk8mpDgJf7dPcWpTVynt/ntkpA9DD29A=; b=RUKt4ycVNllJDnnzIWmes5CFVGogMeIZhueuP3I3zmMGAWjFVKHTR4jESKSffkdJJ4 I3w5clQq+BFRkrqkGtd9FbVsjNZswG4d+4DFa8rMfKQyXGkzGkX1sTYWZ6Vu8rxrpSpr SEH5wx8Enwbi9OTLDYqLGfx3MImaxIHBFz2GbhpsEOqbZXOlzCgTRWKrgA/dEXnAPXG9 Mcl5tVIOD+AzIK1XEUgE4ojnqOJHJNuHx2fcqQ3zU1ZZGLUHFyqACu0jxVMBBDPR/RZZ Iqkwy8KmD2+x1ZlosuKXgUv22APElccHNXH7dYSsefLVjkqn7CJsJX5XwTBrGqXzJLoS zbKg== X-Gm-Message-State: APjAAAVMBWdDb5eDyaFu/h2Q6DeAHS/5Uk6UYuvNbgRDaUYXwNJyLL9O vCIvQS1SbD4mMZR6/F9nMFSYLM8mvV07L4hwV3g= X-Google-Smtp-Source: APXvYqzN1E+VEc5AJNKgMovwAfh9xhHrt4A0XED+++8hBC7TJBvWA/J0bUObTNrVFDTcQTKnSP36n7aL7cUq3wvJGrE= X-Received: by 2002:a81:1a48:: with SMTP id a69mr15743012ywa.507.1552940702107; Mon, 18 Mar 2019 13:25:02 -0700 (PDT) MIME-Version: 1.0 References: <9770ACD5-B1D1-409F-A882-0BCBBEEFB2C3@apple.com> <66457872-874A-4FEB-B340-1F5BCBC85A2F@apple.com> In-Reply-To: <66457872-874A-4FEB-B340-1F5BCBC85A2F@apple.com> Date: Mon, 18 Mar 2019 16:24:50 -0400 Message-ID: To: Michael Sweet , Ira McDonald Cc: PWG IPP Workgroup Subject: Re: [IPP] LCRC draft of PWG Safe G-Code Subset for 3D Printing posted X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============8909145571433655152==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8909145571433655152== Content-Type: multipart/alternative; boundary="000000000000e80fb00584642e0a" --000000000000e80fb00584642e0a Content-Type: text/plain; charset="UTF-8" Hi Mike, Yes it works OK now - thanks. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Mon, Mar 18, 2019 at 4:21 PM Michael Sweet wrote: > Hmm, I think my FTP software has trouble with short files (or something > else unfortunate is happening) - was having the same problem with uploading > the IPP WG web page, too. > > Try it now (uploaded via SSH...) > > > On Mar 18, 2019, at 3:59 PM, Ira McDonald wrote: > > Hi Mike, > > Two "successful" downloads of the LCRC plaintext file still yield a > zero-length > file. Same info from the PWG direct FTP site. Huh? > > 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/highnorthinc > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Mon, Mar 18, 2019 at 11:39 AM Michael Sweet via ipp > wrote: > >> All, >> >> I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D >> Printing best practice document to: >> >> >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf >> >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf >> https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt >> >> The only comment and change is to fix two broken section references in >> table 1. >> >> _________________________________________________________ >> Michael Sweet, Senior Printing System Engineer >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> > > _________________________________________________________ > Michael Sweet, Senior Printing System Engineer > > --000000000000e80fb00584642e0a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Mike,

    Yes it works OK now= - thanks.

    Cheers,
    - Ira

    <= /div>
    Ira McDonald (Musician / Software Architect)
    C= o-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TCG Metada= ta Access Protocol SG
    Chair - Linux Foundation Op= en Printing WG
    Secretary - IEEE-ISTO Printer Working Group
    Co-Chair -= IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Designated Expert - IP= P & Printer MIB
    Blue Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    mailto: blueroofmusic@gm= ail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-494-2434


    On = Mon, Mar 18, 2019 at 4:21 PM Michael Sweet <msweet@apple.com> wrote:
    Hmm, I th= ink my FTP software has trouble with short files (or something else unfortu= nate is happening) - was having the same problem with uploading the IPP WG = web page, too.

    Try it now (uploaded via SSH...)


    On Mar 18, 2019, at 3:59 PM, = Ira McDonald <blueroofmusic@gmail.com> wrote:

    Hi Mike,<= /div>

    Two "successful" downloads of the LCRC p= laintext file still yield a zero-length
    file.=C2=A0 Same info fro= m the PWG direct FTP site.=C2=A0 Huh?

    Cheers,<= /div>
    - Ira

    Ira McDonald (Musician / S= oftware Architect)
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TCG Metadata Access Protocol SG
    Chai= r - Linux Foundation Open Printing WG
    Secretary - IEEE-ISTO Printer Work= ing 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/blueroofmu= sic
    http://sites.google.com/site/highnor= thinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 498= 39=C2=A0 906-494-2434



    On Mon, Mar 18, 2019 at 11:39 AM Michael Sweet via ipp = <ipp@pwg.org> wr= ote:
    All,

    I have posted the LCRC draft of the PWG Safe G-Code Subset for 3D Printing = best practice document to:

    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https:= //ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.docx
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https:/= /ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318.pdf
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 htt= ps://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf
    =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://ftp.pw= g.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt

    The only comment and change is to fix two broken section references in tabl= e 1.

    _________________________________________________________
    Michael Sweet, Senior Printing System Engineer

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

    _________________________________________________________
    Michae= l Sweet, Senior Printing System=C2=A0Engineer

    --000000000000e80fb00584642e0a-- --===============8909145571433655152== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8909145571433655152==-- From ipp-bounces@pwg.org Mon Mar 18 14:23:37 2019 Return-Path: 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 2BF79130DE6 for ; Mon, 18 Mar 2019 14:23:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.276 X-Spam-Level: X-Spam-Status: No, score=-2.276 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_PASS=-0.001, URIBL_GREY=0.424] autolearn=no 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 Oj3vfquToOst for ; Mon, 18 Mar 2019 14:23:35 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id C652A1276D0 for ; Mon, 18 Mar 2019 14:23:34 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 3636E3F4A; Mon, 18 Mar 2019 21:23:34 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1E73927B3; Mon, 18 Mar 2019 21:23:28 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id EE1A02618; Mon, 18 Mar 2019 21:23:26 +0000 (UTC) Received: from mail-yw1-xc35.google.com (mail-yw1-xc35.google.com [IPv6:2607:f8b0:4864:20::c35]) by www.pwg.org (Postfix) with ESMTPS id 0902E2618 for ; Mon, 18 Mar 2019 21:23:26 +0000 (UTC) Received: by mail-yw1-xc35.google.com with SMTP id e76so14146259ywa.9 for ; Mon, 18 Mar 2019 14:23:25 -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; bh=zRhSlbD8lRxcb+8BFFhMJ8pilheWpY9n7Z4kd3b7vFI=; b=XEl92c1jsLN8ngR2LlqFPHUf5vG6amHZGiR59JiCVwHq8tR6UoL/w0jM3DzVExy1OZ U8yPgLROqjj+Sa3Er3ykY3+WNkoF/Zgk0uTnbZIBVmGVPn8+4C2xN7Fd57ZQWG6wtSRH Z24TQkt3FGRVa6Roi1UwgTqX7LGnuKBjb8uWMsBpS1bKM693gSOvk5g/BylRWQDHtwSW PFZeWu1WpFGh4ZzebpuQtq/dBOmA6w+Up+DciUAffxX0fMFefQd2Q+5nzjY+PL2qT+04 GNc9mbBrUyRlAjnALRVth7vV4RSp9jmYTFc7CmlCcI0i5xc1kfU+lXCyvfh8MmO7WKlV 9vHQ== 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; bh=zRhSlbD8lRxcb+8BFFhMJ8pilheWpY9n7Z4kd3b7vFI=; b=gIdWhPDFdhkfbt5iKd7/ZB6es2anOs4/PyvPd6UzpFAOTX/tUHG33mXr76AxG/6/+j KM45BJmG5SvWZ9CKiKyWDPRfntNOh45gD/DwmoFyrerWIj/gle1U2/DnUHVvB2fFuBjh NWMnAzdUkHIpDRDJACAtrto9XofsspzhKID0Msx2F3nhWDRKWKsj6JjUpmCefS1DCkQa Q/7FXyPIepIt/yziVJDRvmrOg4vbPKZQj5aGeveN0Tx1uOjdX5OYaluqEYLHTfQ9qOo7 Sd/asktVCrvjX3M+hW3O9SGGA/3CPfU57uKZPLX2nFftZYZ5POeM1o6onRpCs1rhUDGf UvSA== X-Gm-Message-State: APjAAAWh5RgY2806E5CNTUpr0tkoyc+7LO/zLkY6oK5vIWea1z9PpB1q chs4tTCKSqTVBGkwA+VLKyvBqSsPabikeFVhyOF5Mg== X-Google-Smtp-Source: APXvYqxDBlqkfnXeFPEJuFdH3XGAmp8MP8T1RjeAmwmVxJBEG1nZNLjtOueT+ia9Q0nNo8OozcMqHoPsAu9e6cK4ao0= X-Received: by 2002:a81:5f86:: with SMTP id t128mr16280555ywb.467.1552944204982; Mon, 18 Mar 2019 14:23:24 -0700 (PDT) MIME-Version: 1.0 References: <518040d0ad234bc5bf997bdcf8aff3ca@ENA13-200.nrc.na.int> <8e94a9762fbe49e2a05961e3016f3c36@ansi.org> In-Reply-To: <8e94a9762fbe49e2a05961e3016f3c36@ansi.org> Date: Mon, 18 Mar 2019 17:23:12 -0400 Message-ID: To: "ipp@pwg.org" , Ira McDonald Subject: [IPP] Fwd: 3D Printing and Transportation International Conference X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============5339900177464697263==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5339900177464697263== Content-Type: multipart/alternative; boundary="000000000000b1b180058464ff34" --000000000000b1b180058464ff34 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FYI - the actual conference is 20-21 November 2019 in Washington, DC. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 ---------- Forwarded message --------- From: James McCabe Date: Mon, Mar 18, 2019 at 4:45 PM Subject: 3D Printing and Transportation International Conference To: fyi *From:* Gibson, Nelson *Sent:* Friday, March 15, 2019 2:44 PM *To:* AMSC ; James McCabe *Subject:* 3D Printing and Transportation International Conference Dear Jim and AMSC, Hello. I am a senior program officer at the Transportation Research Board . I would like to reach out to America Makes & ANSI Additive Manufacturing Standardization Collaborative (AMSC) to share a Call for Papers for an upcoming TRB conference. The standing committee volunteers I most often work with tend to be involved in ASTM or AASHTO so this is somewhat new ground for me. I am sharing a Call for Papers for a conference the Transportation Research Board is sponsoring. You and others you know might be interested in it based on your subject area. The first International Conference on 3D Printing and Transportation will be held November 20-21, 2019 in Washington DC. The conference will share knowledge and information on how 3D printing impacts transportation through innovations in freight movement, manufacturing, infrastructure construction and more. Here is a link to the main conference website www.cvent.com/d/nbqrhb Click here to go directly to the call for papers . The conference is accepting extended abstracts or full papers for potential publication in the *Transportation Research Record *. Please share as you believe is appropriate and I am happy to answer any questions you may have. Sincerely, --Nelson *Nelson Gibson, PhD, PE* Senior Program Officer, Materials and Construction Transportation Research Board The National Academies of Sciences, Engineering, and Medicine 500 Fifth Street, NW | Washington, D.C. 20001 202-334-2953 | ngibson@nas.edu | www.TRB.org *TRB 99th Annual Meeting is January 12=E2=80=9316, 2020* ######################################################################## --000000000000b1b180058464ff34 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    FYI - the actual conference is 20-21 November 2019 in= Washington, DC.

    Cheers,
    - Ira

    Ira McDonald (Musician / Software Architect= )
    Co-Chair - TCG Trusted Mobility Solutions WG
    Co-Chair - TCG = Metadata Access Protocol SG
    Chair - Linux Foundat= ion Open Printing WG
    Secretary - IEEE-ISTO Printer Working Group
    Co-C= hair - IEEE-ISTO PWG Internet Printing Protocol WG
    IETF Designated Exper= t - IPP & Printer MIB
    Blue Roof Music / High North Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/site/highnorthinc
    ma= ilto: blueroof= music@gmail.com
    PO Box 221=C2=A0 Grand Marais, MI 49839=C2=A0 906-49= 4-2434

    <= /div>

    <= br>
    -------= --- Forwarded message ---------
    From: James McCabe <jmccabe@ansi.org>
    Date: Mon, Mar 18, 2019 at 4:4= 5 PM
    Subject: 3D Printing and Transportation International ConferenceTo: <AMSC@maillist.ansi.org<= /a>>


    fyi

    =C2=A0

    From: Gibson, Nelson <NGibson@nas.edu>
    Sent: Friday, March 15, 2019 2:44 PM
    To: AMSC <AMSC= @ansi.org>; James McCabe <jmccabe@ansi.org>
    Subject: 3D Printing and Transportation International Conference<= /u>

    =C2=A0

    Dear Jim and AMSC,

    =C2=A0

    Hello. I am a senior program officer at the Transportation Research Board. I would like to reach out to America Mak= es & ANSI Additive Manufacturing Standardization Collaborative (AMSC) t= o share a Call for Papers for an upcoming TRB conference. The standing comm= ittee volunteers I most often work with tend to be involved in ASTM or AASHTO so this is somewhat new ground for m= e.

    =C2=A0

    I am sharing a Call for Papers for a conference the = Transportation Research Board is sponsoring. You and others you know might = be interested in it based on your subject area. The first International Con= ference on 3D Printing and Transportation will be held November 20-21, 2019 in Washington DC. The conference will sh= are knowledge and information on how 3D printing impacts transportation thr= ough innovations in freight movement, manufacturing, infrastructure constru= ction and more.

    =C2=A0

    Here is a link to the main conference website www.cvent.com/d/nbqrhb

    =C2=A0

    Click here to go directly to the = call for papers. The conference is accepting extended abstracts or full papers for potential publication in the Transportation Resea= rch Record.

    =C2=A0

    Please share as you believe is appropriate and I am = happy to answer any questions you may have.

    =C2=A0

    Sincerely,

    =C2=A0

    --Nelson

    =C2=A0

    =C2=A0

    Nelson Gibson, PhD, PE

    Senior Program Officer, Materia= ls and Construction

    Transportation Research Board

    The National Academies of Scien= ces, Engineering, and Medicine

    500 Fifth Street, NW | Washingt= on, D.C. 20001

    = 202-334-2953 |=C2=A0 ngibson@nas.edu | www.TRB.org
    TRB 99th Annual Meeting is January 12=E2=80=9316, 20= 20

    =C2=A0

    ########################################################################
    --000000000000b1b180058464ff34-- --===============5339900177464697263== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5339900177464697263==-- From ipp-bounces@pwg.org Mon Mar 18 15:26:31 2019 Return-Path: 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 35E59124B91 for ; Mon, 18 Mar 2019 15:26:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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=apple.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 ddYfvG2nvsB7 for ; Mon, 18 Mar 2019 15:26:29 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABCA12008F for ; Mon, 18 Mar 2019 15:26:29 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 6FE9E3FCD; Mon, 18 Mar 2019 22:26:28 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id E05F02708; Mon, 18 Mar 2019 22:26:24 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 6B66E378A; Mon, 18 Mar 2019 22:26:23 +0000 (UTC) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by www.pwg.org (Postfix) with ESMTPS id EADE92708 for ; Mon, 18 Mar 2019 22:26:22 +0000 (UTC) Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x2IMGonf023451 for ; Mon, 18 Mar 2019 15:26:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-transfer-encoding : content-type : sender : from : date : subject : message-id : to; s=20180706; bh=YBtUY+R3ZFQaoCUlBorNpv7tB/SFZvB5s01is75j/go=; b=X1SLpRP97Wsdxffi+1on5YLW7GC4xHIckJmtYOR0xOfxQK46m3TtylpS29Q8/5/O+oNb ytbyrFDK1LtgaluFvI+t+MnTA8lpxTmYmna7iMt6kCJnKV9IWy8QVEmpMI/OEzJz5LNx gqQYdLFa1dz6bSk8it5/dNGLOR+GDsapuCbpd3s8YkYXrQO6xn/i2vGjNnz9qHLdHhtR 1fMT5tc2yv4t0IOjQsb26xBdgXLTO1KWeI8p5n3s+QKmyDj+Q6+UXVfA7A9zlMSEPZz/ 2wzkBkWT7BxuFJbw8YnCtzQ/NJ6jVWqkefnPAJuSrrSp70/3lSpvXcFrvDSSkU6iOQgN 3g== Received: from mr2-mtap-s03.rno.apple.com (mr2-mtap-s03.rno.apple.com [17.179.226.135]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2ragpxc826-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 18 Mar 2019 15:26:22 -0700 MIME-version: 1.0 Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by mr2-mtap-s03.rno.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPS id <0POL00F552BXO5K0@mr2-mtap-s03.rno.apple.com> for ipp@pwg.org; Mon, 18 Mar 2019 15:26:21 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) id <0POL00L002AQWX00@nwk-mmpp-sz10.apple.com>; Mon, 18 Mar 2019 15:26:21 -0700 (PDT) X-Va-A: X-Va-T-CD: 6dd86a8f7e615dc06f775907aaa1dbc0 X-Va-E-CD: 96b4bd9b930c7c1cce37fed95cc6f62c X-Va-R-CD: 7405cb86d23c958719a054430748d1d3 X-Va-CD: 0 X-Va-ID: a367cc47-570a-4235-a5eb-71e0401a56cc X-V-A: X-V-T-CD: 36faa17af2f4ed37308c61fb93ff57b8 X-V-E-CD: 96b4bd9b930c7c1cce37fed95cc6f62c X-V-R-CD: 7405cb86d23c958719a054430748d1d3 X-V-CD: 0 X-V-ID: fefba4b8-0158-492d-a0d5-60e5c78c3b01 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-03-18_13:,, signatures=0 Received: from [17.235.51.187] by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.3.20181024 64bit (built Oct 24 2018)) with ESMTPSA id <0POL00L1T2BUIF00@nwk-mmpp-sz10.apple.com>; Mon, 18 Mar 2019 15:26:20 -0700 (PDT) Date: Mon, 18 Mar 2019 18:26:17 -0400 Message-id: <25094559-E38E-44C2-9C33-52CF39172B34@apple.com> To: PWG IPP Workgroup X-Mailer: Apple Mail (2.3445.104.8) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-18_13:, , signatures=0 Subject: [IPP] FYI: Progress on IPP Everywhere v1.1 Self-Certification Tools X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Sweet via ipp Reply-To: Michael Sweet Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ipp-bounces@pwg.org Sender: "ipp" All, I've been working on the v1.1 tools and have a very early alpha version of the submission tool pushed to the Github repository. Feel free to play around with it if you like - I still need to finish up the rest of the validation tests and make sure that the feature detection is working as designed. _________________________________________________________ Michael Sweet, Senior Printing System Engineer _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp From ipp-bounces@pwg.org Mon Mar 25 07:30:43 2019 Return-Path: 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 A3B081203EE for ; Mon, 25 Mar 2019 07:30:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, MAILING_LIST_MULTI=-1, SPF_PASS=-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 d_UD0oEwx-_V for ; Mon, 25 Mar 2019 07:30:41 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 2808112040A for ; Mon, 25 Mar 2019 07:30:41 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 9D3DE3F9C; Mon, 25 Mar 2019 14:30:40 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id E83733B9E; Mon, 25 Mar 2019 14:30:36 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 6551F3B9E; Mon, 25 Mar 2019 14:30:36 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id AE5E42491 for ; Mon, 25 Mar 2019 14:30:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1553524233; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YWgx4QahElnhaqOgARua03qO5ARtj5dEOooi/I/9Qto=; b=axBZXpxdIHLsHcJKPc6THuV9j/DH7Xq/qd154Mwhsze4wZrjcYx2YBi9ROinGRvb4PmGyqKgDzKA36f6uSBFzu2GoCbpAgLES73a9NFlIKjOLXm14HkJZkH0U11PhE+WVs1HyoQe14eAMSuH+xu5ws+ao9j3lKKXq7RMf23FepQ= Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01lp2053.outbound.protection.outlook.com [104.47.33.53]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-37-GP5q7qWFNhev69z43S6Xig-1; Mon, 25 Mar 2019 10:30:32 -0400 X-MC-Unique: GP5q7qWFNhev69z43S6Xig-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0487.NAMPRD84.PROD.OUTLOOK.COM (10.169.13.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.16; Mon, 25 Mar 2019 14:30:30 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898%2]) with mapi id 15.20.1730.019; Mon, 25 Mar 2019 14:30:30 +0000 To: Michael Sweet Thread-Topic: [IPP] RFC: Relationship between job-retain-until-xxx and job-password Thread-Index: AQHU21fS1+W3/SIrr0uH8d4FsuqGfKYNbYaAgA8KYAA= Date: Mon, 25 Mar 2019 14:30:30 +0000 Message-ID: References: <00239C4D-D794-4962-88E2-A00CBE1F654B@hp.com> <192B77BE-153C-45A8-870C-24257F0DD803@apple.com> In-Reply-To: <192B77BE-153C-45A8-870C-24257F0DD803@apple.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: [15.65.254.6] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c72b940e-d9f9-4074-1049-08d6b12e6f04 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0487; x-ms-traffictypediagnostic: CS1PR8401MB0487: x-microsoft-antispam-prvs: x-forefront-prvs: 0987ACA2E2 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(346002)(376002)(39860400002)(366004)(396003)(15594002)(189003)(6602003)(199004)(6506007)(86362001)(6436002)(3846002)(105586002)(14444005)(229853002)(36756003)(76176011)(33656002)(7736002)(6486002)(6916009)(6512007)(82746002)(305945005)(53546011)(2906002)(83716004)(5660300002)(6246003)(106356001)(26005)(186003)(53936002)(102836004)(256004)(71200400001)(71190400001)(99286004)(6116002)(93886005)(99936001)(97736004)(81166006)(81156014)(8936002)(446003)(476003)(2616005)(478600001)(11346002)(25786009)(486006)(66066001)(68736007)(316002)(14454004)(4326008)(13513002)(21314003); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0487; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: ApL1jEAnGfLNieq0GwyTclNRuZly4QBBlp9qjs/z2wHfbFffGh/45oS6kUuLpBp/9eG7NSkixFCOoslTGKfPSSzac3+aMu8sodUAnD/Dl0A2YJ7AwpJlDbF3AxuOC9SzxzzCW/ML2csO7GOalIy96ZMCUEUnW7OSvM3aYxRZbzgtm2AocAQY6UtkTV/uXyVeJT/6D5TyUd5FlvfI9VLm6Akx7mhJtiW1ubWkDc3cHeZQszOngzh8xXLTB4ZSELzALHMKH+WE/UmCaQcxCEqzwtt+rTtwQw/gKkMQN3DcrY+SKJ5P4twaHyM3UIY2zr96j17zGgmabpswdoBXoH1D1mKEyCrwv6blsqDqaJAx1cpAZEbxUkSQOKtGQP9c+pG0sNnVRvTvob03bS0hu8tR/1KdQvnpP4wQCy4FTQTGazQ= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: c72b940e-d9f9-4074-1049-08d6b12e6f04 X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2019 14:30:30.7141 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0487 Cc: PWG IPP Workgroup Subject: Re: [IPP] RFC: Relationship between job-retain-until-xxx and job-password X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============2086403396139914709==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2086403396139914709== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_47CEBE9E-3B26-4FF5-A40B-FBBACE63CDF8"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_47CEBE9E-3B26-4FF5-A40B-FBBACE63CDF8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 15, 2019, at 6:49 PM, Michael Sweet wrote: >=20 > Smith, >=20 >> On Mar 15, 2019, at 1:52 PM, Kennedy, Smith (Wireless & Standards = Architect) via ipp wrote: >>> ... >>> I like it! I'll update my EPE draft to specify that and we can = discuss that first draft at our next IPP WG meeting. >>=20 >> OK, more questions: >>=20 >> 1. Should "job-password-action" be an operation attribute, or a Job = Template attribute? >=20 > Good question. Ordinarily we would make it a Job Template attribute, = but I can see the argument for not exposing too many details of = "job-password" usage and "job-password-encryption" is also an operation = attribute. >=20 > Of course, the 'job-password-wait' keyword in "job-state-reasons" will = expose the fact that a job is held for a password at the console, but = we're stuck with that so an operator or user knows some action is = required... >=20 > OK, I think I'm slightly more in favor of it being an operation = attribute, if for any other reason that I think there will be less = chance for an implementor to mess things up... :) In my first draft (to be posted soon) it will be an operation attribute. >=20 >> 2. We would want the semantic to be that if the "job-password-action" = was 'retain-only' or 'process-and-retain' then the "job-password" value = would become a "hidden Job Status attribute" so that the Printer would = require the "job-password" to be entered before any reprints could = occur. >=20 > I think we should require job-password for any action - yes, a new = semantic for Resubmit-Job, but I think one we can get away with since = the combination of job-password and Resubmit-Job was not fully = specified... (unlike save-disposition and proof-print) Oh, ok. But the funny thing is that now I feel like we have come full circle. = =F0=9F=98=8A Originally I was concerned about the awkward semantics of = "job-password" and "job-save-disposition". If we had proposed = "job-password-action" as we are describing here, and updated the = semantics of "job-password" so that in all cases the password is = required for any action, then we could have left JPS2 as is and my use = case would have been resolved. I suppose we'd still have contend with = the ambiguous semantics of "job-save-disposition", though. >=20 >> 3. I'm not clear on the semantic meaning of 'process-and-retain'? >=20 > Print it (without password) and then retain for later reprint (using = the password). >=20 > So basically: >=20 > - 'hold-job' is "hold the job until the password is entered, then = print and retain" > - 'process-and-retain' is "print the job immediately and then retain" > - 'retain-only' is "do not print the job but retain the job for = possible later printing" >=20 > Any subsequent reprints require the password. I guess the question is = whether the "job-retain-until" for the resubmitted job should be "none" = or the copied job should also have the same job-password-xxx values? (I = can see the latter actually being a benefit) I'm a little worried about 'retain-only'. If the semantics of = "job-password" are going to be updated / clarified to require that the = password be required for any subsequent reprint (via Resubmit-Job or = otherwise), then is 'retain-only' just for supporting something like = "job-save-disposition" --> "save-disposition" =3D 'save-only'? But for = 'save-only' the "processing" job state is saving it. So 'retain-only' = sounds like it is bypassing processing and going straight from 'pending' = to 'completed'. --Apple-Mail=_47CEBE9E-3B26-4FF5-A40B-FBBACE63CDF8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyY5gQACgkQqskbKLDW 1N34wQ//WixZmtM91OJ6FneN2cHqZsLhlQvjmZ7en9fFYv6QRXLT2xIHDhrhgxrU LAIzLdc/QSl/Yfh/zRNik8TRKJXGxWCs7ZvIntrUjo/3JlT5NBIdJD13Y5x2AbWu dKuoshhs4zRU/UpIvB5IH0i7sWlE3+M9+zFrUksw6m8Qgrxv6cS36cbq9gFYt5db i+pCj6E7bywabmkN5un+8UCira7yEwWyB/iBhdaEVQr3gUS8pFknVxUmowRHzCyp ej5D44qIrkfSElInZMcUxssY26srsgQKD5jvTnq4V05HTGRqPt41ozpTPAy1CHPp i3DDYCFgPFC++AIqOEmO5rLaOWr+EgR64vqrZVzC5PLw4CaCvP4ygGOAhOXeGVjM aU/+JmcodsBwP3azZ1LwG04PNaScyNTUeDPfQZcCL8iPzDnWTfSSgR+VX1tbQ9tF bmi6Hu3Pfi2zIVd7zB000U2olGApYjyYeOoNsOUQ21OkxbjpxNWTUoYq3AeoPLjS RjSkk7HSD6CSpDLDp/4amQrQ9fqiVgRRn8oxKHjrsGKIkCDG8tZWEHDPtvQrt5CX TATAlpzMcc4vFtcNFOvuevKW+minwlohvYz6dCxT+7bAIOgNxx6k/ieiJN24+/Jb pR8XQDs7HwapvyFLpyjKYVGWCWz509vK9vTkzcVxMrnpuMqxd4w= =sC+K -----END PGP SIGNATURE----- --Apple-Mail=_47CEBE9E-3B26-4FF5-A40B-FBBACE63CDF8-- --===============2086403396139914709== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2086403396139914709==-- From ipp-bounces@pwg.org Wed Mar 27 08:00:12 2019 Return-Path: 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 A6A39120311 for ; Wed, 27 Mar 2019 08:00:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 nwEhhUKGGEkv for ; Wed, 27 Mar 2019 08:00:10 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id C913212030D for ; Wed, 27 Mar 2019 08:00:09 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 869AE3FD1; Wed, 27 Mar 2019 15:00:08 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id CA1A02667; Wed, 27 Mar 2019 15:00:04 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id E0E6E3B9E; Wed, 27 Mar 2019 15:00:03 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 91FDE2689 for ; Wed, 27 Mar 2019 15:00:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1553698801; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=uEn0QrVYRiaGrNo+YyVU2hzBD4sl9aMJfq9VRCv2E5k=; b=f6WUzRajDT9r7s96zrHaipxmHlHu8hzDaQTIgarRshyPJLimWpFeuwy/00VgZ7xn/5rvhkcAWY6RkgVg5/dcz3jis+S8L447UcG4j1UlWTgagbgRjHxz8tKEj/DYcoxeqk7XfP59MQIUN7o7aJSdFSMJQkbP8AZSr9/1ST+YkyU= Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01lp2054.outbound.protection.outlook.com [104.47.34.54]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-57-1SGarT52O2K_BCOAV-YgwQ-1; Wed, 27 Mar 2019 10:59:59 -0400 X-MC-Unique: 1SGarT52O2K_BCOAV-YgwQ-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0853.NAMPRD84.PROD.OUTLOOK.COM (10.169.16.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.18; Wed, 27 Mar 2019 14:59:57 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898%2]) with mapi id 15.20.1730.019; Wed, 27 Mar 2019 14:59:57 +0000 To: PWG IPP WG Reflector Thread-Topic: First draft of "IPP Enterprise Printing Extensions" posted for review Thread-Index: AQHU5K2+TOFjkpfTo0Og0sw05sTZAQ== Date: Wed, 27 Mar 2019 14:59:57 +0000 Message-ID: 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 7173d7af-d19f-4503-2b16-08d6b2c4e111 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0853; x-ms-traffictypediagnostic: CS1PR8401MB0853: x-microsoft-antispam-prvs: x-forefront-prvs: 0989A7979C x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(376002)(346002)(39860400002)(136003)(199004)(189003)(6602003)(105586002)(6512007)(256004)(6306002)(8676002)(316002)(7736002)(6916009)(4744005)(486006)(6486002)(33656002)(6506007)(236005)(14454004)(86362001)(6436002)(53936002)(476003)(5660300002)(966005)(478600001)(83716004)(71200400001)(186003)(54896002)(606006)(97736004)(2906002)(81156014)(102836004)(82746002)(26005)(36756003)(99936001)(99286004)(106356001)(25786009)(68736007)(81166006)(8936002)(66066001)(71190400001)(6116002)(2616005)(3846002); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0853; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: mCHabk8zzLA5Y3R+qUF7vKs9/HT8+vYEjr9r4XjU87oAvkoltiuyn25O2A/lbFS3PDbdF7TYF3kJIKKKIQvg1gD1RgGX78awVlT8o5x/+RfniiysEzMgm+Uk3NmUZw3WDmW2A1XuZpiCtVoe0cyMlreitr4jtO0L/P9s3EsEQ1CBAZZfkyY08Lp5SU1uC4TlhFjo/g/OUaaG59MGEye1rqDTLaI61ur9dEk9L5awszV9RA5NutJk00bYPMOPNDA98cNqRlzwIM+iycacqSdpkc5f7IZ0XFE/3xqyfNwWhzDjP+abIgGN1xY6uDTKai486Wv83APJiIvM7RJpOTMqnfb7M/PTx/RfJ1CxVDCy/b16Qv+vzhE3NtGkQx5WmZ4kpkVysj46z+AkbJONv4xEKplPNBPaULZ2MqpxaotcX+k= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: 7173d7af-d19f-4503-2b16-08d6b2c4e111 X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Mar 2019 14:59:57.7986 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0853 Subject: [IPP] First draft of "IPP Enterprise Printing Extensions" posted for review X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============2670463173644094477==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============2670463173644094477== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_A8EF3A96-257A-4FF9-81AF-2E7B677E42F0"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_A8EF3A96-257A-4FF9-81AF-2E7B677E42F0 Content-Type: multipart/alternative; boundary="Apple-Mail=_21160E1D-256E-435D-9ADD-4D85C3DDB891" --Apple-Mail=_21160E1D-256E-435D-9ADD-4D85C3DDB891 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings, I have just posted the first draft of "IPP Enterprise Printing = Extensions". Please review offline and I hope we have a chance to = discuss this at sometime in the near future. https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf = Cheers, Smith /** Smith Kennedy Wireless & Standards Architect - IPG-PPS Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC = Forum / USB-IF Chair, IEEE ISTO Printer Working Group HP Inc. */ --Apple-Mail=_21160E1D-256E-435D-9ADD-4D85C3DDB891 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Greetings,

    I have just posted the first draft of "IPP Enterprise = Printing Extensions". Please review offline and I hope we have a chance = to discuss this at sometime in the near future.

    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx<= /div>
    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf

    Cheers,

    Smith

    /**
        Smith = Kennedy
        Wireless & Standards Architect - = IPG-PPS
        Standards - IEEE ISTO PWG / = Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF
      =   Chair, IEEE ISTO Printer Working Group
      =   HP Inc.
    */



    = --Apple-Mail=_21160E1D-256E-435D-9ADD-4D85C3DDB891-- --Apple-Mail=_A8EF3A96-257A-4FF9-81AF-2E7B677E42F0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlybj+wACgkQqskbKLDW 1N1YXQ//U5a5P509+txJ4XzAmLRMBWLty542BoE06H59hD+KQreKDK9AMyTYv3Vt 3n/uAjzR1x6WAsCimL6JrPfolmYKV10pIlEkdPZG8Q/AQrzrv2oz3rl4K0aodkX0 z58rNse/9aVqxaWXOOgB+fXwOqN2PNboPD77EbRVJ6RM3d78tkj8ukBjvUozFPvN FuteU77/vuywFjuoF+KNuUYjQrtZcVaGhIg2vTG2X7hSEqcuUZgl5BljOYDwq6jb W+F8uR1ribokZu7bxB84Q/QV9FF/sAaqfe+56lYUy8LVXMW3cazC27yuCw4OHx+q pZ0pp7beUYL3DC+81j+4amDmCz/HQ30ZUMwmdeWmx1ngs56qQtvv9yKJvYu1uo5Z 0dT6KUkcZyIjpzAcmXcVrj8crHYnEvFy6EKN/MzdveIen3wdyBnsW9ujDYtzl5nG b3cW8su8BteQbZzc0IkPd88UHtClxbmveoYVCDUVU4shAeh7hP60fSUSWinzafPU sJXJer22IEPH2j1WF3sCYFgMqJbs4TqgSHGDcNSv0e6C/brkVrD63XzI/gY+zMTp twbZJR41ozDMvolHxsnlR6W8GqvKH3Rt5IZBMsUnp/L2W/KC+2JOSqc7eVxsquwm Iddqb0SEcdn96DQgD8R9jXVGcDMB4LO7O3+qlG9KJYSsi9g7l50= =WS8e -----END PGP SIGNATURE----- --Apple-Mail=_A8EF3A96-257A-4FF9-81AF-2E7B677E42F0-- --===============2670463173644094477== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============2670463173644094477==-- From ipp-bounces@pwg.org Wed Mar 27 11:53:33 2019 Return-Path: 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 AC884120368 for ; Wed, 27 Mar 2019 11:53:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 kUBFEOQGfJ_u for ; Wed, 27 Mar 2019 11:53:30 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id B9E58120364 for ; Wed, 27 Mar 2019 11:53:30 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 250FF3F9B; Wed, 27 Mar 2019 18:53:30 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1A0E326DC; Wed, 27 Mar 2019 18:53:25 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A18D22689; Wed, 27 Mar 2019 18:53:23 +0000 (UTC) Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) by www.pwg.org (Postfix) with ESMTPS id AF50E2689 for ; Wed, 27 Mar 2019 18:53:22 +0000 (UTC) Received: by mail-yw1-xc33.google.com with SMTP id w66so946490ywd.4 for ; Wed, 27 Mar 2019 11:53:22 -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; bh=mAK/GIKHk9YwsbQlTIPxE22dE9b7VYiRhmwL51fyzm8=; b=KLnVXFBWUSTaRd2iaR01w5Iq1S/s3cdsHOoaR+3ZCD56eTzT1qybfQgvhjVwgxsxaH 7rj2N3iOzRvupArasYVAAVnWwm9O7M+whO8Gmv8VmSF3TD7tNfwFJoCNnIGLjSnOp/zR ZrTukDIOwPmo512s+oazrhSj5zjoKL+bPZ6UE2ZIi04A1nulnwcroAz2njVLH107BMED eMvCX7FRBrbGl4rKRv2w4DJvdQVVe0qbAcYK/4I9srFMk5X+Mm28tkexYR9ppDFEu1iA pWNpkJWwS4OxFhUyiLLVH93mqi64q4hU+YtutrS0o8F8aiCNrC6uupzj2n/gC2EyJxso seRQ== 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; bh=mAK/GIKHk9YwsbQlTIPxE22dE9b7VYiRhmwL51fyzm8=; b=GMCv+qhCGvDioz/QFvlzW378ARUw6MDTWJAVTBtxgUlKvUevFEo+5nFxHze5c4Mi4n 0l2P4HTQr9w3JVtha/ZSZjGWgYOrKOEm3UguLRM/9X1E2St2b0C8FzuAxaMUh9RDNmUP CAZn5Az6AmEqpfDom6u6zBGZJSQM99kCf6Bm9v8LLmeChddHQcbo+/fc6I9XIUGqPMu5 zuS1u7P8MLJ9fdQhdo55L6W7Y3l2M35OT/L6O3yG0Tj9sYdRZBHjElzhIxo7Qgbmc350 PA9Q8nbRqCXIgjq6tY1i6ccJ0rW6GUdx5BfD9D9vJzf7qeOcrOC/JrR6N5Zjy5XhQz0E Y+YQ== X-Gm-Message-State: APjAAAV294Z40soFPZiIGD+kp3XNssm+RRYDkQCbkCcuGaDHzeHf4qg1 dtoHoJNVXKyrF9QaER9ZgAQ/p9i6WGnso+BXy1A= X-Google-Smtp-Source: APXvYqxHWJAO7Fz7+I3LAUJarjq39egRt/sXcdOyBCEW8tUutYamrE9GumextoxxmJSqoAEObPLPggKUOKC7TjX7SVM= X-Received: by 2002:a25:e686:: with SMTP id d128mr31172736ybh.193.1553712802038; Wed, 27 Mar 2019 11:53:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 27 Mar 2019 14:53:10 -0400 Message-ID: To: hcd_tc@collaborate.ccusersforum.org, "ipp@pwg.org" , Ira McDonald Subject: [IPP] Fwd: [saag] TLS WG report from IETF104 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============5753119028504526520==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============5753119028504526520== Content-Type: multipart/alternative; boundary="000000000000a60891058517f379" --000000000000a60891058517f379 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FYI ---------- Forwarded message --------- From: Christopher Wood Date: Wed, Mar 27, 2019 at 2:15 PM Subject: [saag] TLS WG report To: TLS met on Monday and Tuesday. Several documents are ready for submission to the IESG. The WG is prepared to address comments when they come. draft-ietf-tls-dtls13-30 is nearly complete with a few issues to address. Initial interop between Mint and NSS was completed prior to the meeting, with mbedTLS support coming soon. The document will not go through another WGLC once interop is complete and issues are resolved. draft-ietf-tls-subcerts is ready for WGLC having received formal analysis since its last update. draft-ietf-tls-oldversions-deprecate is also ready for WGLC after deprecating DTLS 1.0 in addition to TLS 1.0 and 1.1. The WG discussed draft-ietf-tls-certificate-compression and the outstanding issue regarding how to include the compressed certificate in the transcript. Participants signalled disinterest in changing the current draft. Authors will write up the changes and chairs will begin the WGLC process. draft-ietf-tls-tls13-cert-with-extern-psk will likely be ready for WGLC with experimental status after more review. There are no implementations nor formal analysis for the design. The WG discussed updates to draft-ietf-tls-esni, including an initial multi-CDN solution and improved robustness. Participants raised concerns about the current solution=E2=80=99s operational impacts and unkno= wn edge cases. Representative ESNI clients also expressed the desire to minimize performance regressions for any solution. Authors will work with members in the DNS community for additional feedback going forward, though not block on that feedback. draft-sy-tls-resumption-group and draft-wood-tls-external-psk-importer have rough consensus to adopt as WG items. Chairs will confirm on the list. The WG discussed draft-kinnear-tls-client-net-address and general NAT detection use cases. Concerns around client usage of address information were raised. Authors will continue engaging on the list for further discussion. Draft-tschofenig-tls-cwt was also presented with no time for comments or questions. The WG also discussed draft-sullivan-tls-opaque as a way to add OPAQUE to TLS 1.3. Concerns around PAKE usefulness and lack of formal analysis were raised. This PAKE will also be discussed in the CRFG. draft-stebila-tls-hybrid-design discussed a framework for supporting multiple key exchange algorithms in TLS 1.3. Participants signaled an interest in choosing one design general that minimizes complexity instead of surveying different design decisions. Concerns about immaturity of the field of key exchange combiners were raised. The WG also discussed draft-wang-tls-raw-public-key-with-ibc. This document will not be adopted, and the authors will request codepoint allocations from the designated experts. Draft-belyavskiy-fakesni was discussed. Participants raised concerns about the proposed approach and its efficacy when compared to the attacks listed in draft-ietf-tls-sni-encryption. _______________________________________________ saag mailing list saag@ietf.org https://www.ietf.org/mailman/listinfo/saag --000000000000a60891058517f379 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

    FYI
    <= /div>

    ---------- Forwarded message ---------
    From: Christopher Wood <christopherwood07@gmail.com>
    Date: Wed, Mar 27, 2019 at 2:15 PM
    Subject: [saag] TLS WG report<= br>To: <saag@ietf.org>


    TLS met on Monday and Tuesday. Several documents are ready for
    submission to the IESG.=C2=A0 The WG is prepared to address comments when they come.

    draft-ietf-tls-dtls13-30 is nearly complete with a few issues to
    address. Initial interop between Mint and NSS was completed prior to
    the meeting, with mbedTLS support coming soon. The document will not
    go through another WGLC once interop is complete and issues are
    resolved.

    draft-ietf-tls-subcerts is ready for WGLC having received formal
    analysis since its last update. draft-ietf-tls-oldversions-deprecate
    is also ready for WGLC after deprecating DTLS 1.0 in addition to TLS
    1.0 and 1.1.

    The WG discussed draft-ietf-tls-certificate-compression and the
    outstanding issue regarding how to include the compressed certificate
    in the transcript. Participants signalled disinterest in changing the
    current draft. Authors will write up the changes and chairs will begin
    the WGLC process.

    draft-ietf-tls-tls13-cert-with-extern-psk will likely be ready for
    WGLC with experimental status after more review. There are no
    implementations nor formal analysis for the design.

    The WG discussed updates to draft-ietf-tls-esni, including an initial
    multi-CDN solution and improved robustness. Participants raised
    concerns about the current solution=E2=80=99s operational impacts and unkno= wn
    edge cases. Representative ESNI clients also expressed the desire to
    minimize performance regressions for any solution. Authors will work
    with members in the DNS community for additional feedback going
    forward, though not block on that feedback.

    draft-sy-tls-resumption-group and draft-wood-tls-external-psk-importer
    have rough consensus to adopt as WG items. Chairs will confirm on the
    list.

    The WG discussed draft-kinnear-tls-client-net-address and general NAT
    detection use cases. Concerns around client usage of address
    information were raised. Authors will continue engaging on the list
    for further discussion. Draft-tschofenig-tls-cwt was also presented
    with no time for comments or questions.

    The WG also discussed draft-sullivan-tls-opaque as a way to add OPAQUE
    to TLS 1.3. Concerns around PAKE usefulness and lack of formal
    analysis were raised. This PAKE will also be discussed in the CRFG.

    draft-stebila-tls-hybrid-design discussed a framework for supporting
    multiple key exchange algorithms in TLS 1.3. Participants signaled an
    interest in choosing one design general that minimizes complexity
    instead of surveying different design decisions. Concerns about
    immaturity of the field of key exchange combiners were raised.

    The WG also discussed draft-wang-tls-raw-public-key-with-ibc. This
    document will not be adopted, and the authors will request codepoint
    allocations from the designated experts. Draft-belyavskiy-fakesni was
    discussed. Participants raised concerns about the proposed approach
    and its efficacy when compared to the attacks listed in
    draft-ietf-tls-sni-encryption.

    _______________________________________________
    saag mailing list
    saag@ietf.org
    https://www.ietf.org/mailman/listinfo/saag
    --000000000000a60891058517f379-- --===============5753119028504526520== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============5753119028504526520==-- From ipp-bounces@pwg.org Wed Mar 27 11:58:51 2019 Return-Path: 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 D0F5D12032D for ; Wed, 27 Mar 2019 11:58:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 10qIAUwWmoWu for ; Wed, 27 Mar 2019 11:58:49 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 83A4A1202DF for ; Wed, 27 Mar 2019 11:58:49 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 5032C3F4A; Wed, 27 Mar 2019 18:58:48 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 4F6E626DC; Wed, 27 Mar 2019 18:58:44 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 166152491; Wed, 27 Mar 2019 18:58:43 +0000 (UTC) Received: from mail-yw1-xc31.google.com (mail-yw1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) by www.pwg.org (Postfix) with ESMTPS id 529AC2491 for ; Wed, 27 Mar 2019 18:58:42 +0000 (UTC) Received: by mail-yw1-xc31.google.com with SMTP id j128so13309931ywg.12 for ; Wed, 27 Mar 2019 11:58:42 -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; bh=63fIAlDth7nho4iXHzzFWKEmOmfbXGdqY1Ll9BdFp5s=; b=p6YI80NzJiw4ihXKrrjZ7CKLD+5qI49sWztR+ZuOB83kTxkrpsHkyRzscha4JFvdWD aFWW2UgGjOHpOzsOd+KKqfsBVvIqUoKeAwpTkEyc+zigBm3/zXA8kiYhCvvJCUN9tCCM NL8EM+BRUP2i06g4cNOXCtZbvMnbQybRcRdSEewSlgPYDA57phu8qVeucYN6zLqlgZd9 8NAARF7lqIQMHdsW4tcFc939fyVKlX3yTzRpq9TMtAqfWmoCn1jFfkdFffRwIbSpF/qC 7lKKtwGs+AEb2X+AguW8TdsRgWT9vMVDd/VYbicmrAOfkt4U4XRb+gjYcM48IRcK/JAP BrVQ== 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; bh=63fIAlDth7nho4iXHzzFWKEmOmfbXGdqY1Ll9BdFp5s=; b=OcNfn2Yr9IF3NbZfpi9OqNlS2SB+KUiGwUtSJ7UI8iYKb25BGoW12Ng6Nvu5cReO0M m7gj5AW/tEvG1g4onbgR+q6C8sGWorY5LciUb51QpktI23DskjA8GFTMigxhZXfENPI3 z2r25ZWizurRx8GleAntyv7uQ5gQeQAJy4lxhPipfCbSEskhwckd0CvBGNofnDcau1bk kg/MRlF0hO3SMBwW9dgTzw7PVyZPr/8qzg1ABlQBo8m3li9evNzoD/UneQ2cmqtv1VSS 3olsXRY0iogu2Y9Eo48WlSYO1hFaWto1uTkTxXxK/az+DI2g6viaAJID+EY1tXL7RLyg JcUw== X-Gm-Message-State: APjAAAWtm2rrnNrNfdlW4r9y9OCPKDarnQmCzUEexWqmYbl09WiTZdPb eF0BfVxCmQ7yjR20BVnEaayINIKGS3jfrCupiBA= X-Google-Smtp-Source: APXvYqxbuK6U+ZX7keTqyJAGRY4EyhLBT8XX3Eoog+yCDcEHuY6s+M6W7dRfRbCZH4avojbBCcsVjl6miDo5e4lizl0= X-Received: by 2002:a81:2e88:: with SMTP id u130mr29880896ywu.98.1553713121667; Wed, 27 Mar 2019 11:58:41 -0700 (PDT) MIME-Version: 1.0 References: <2025160620.59.1553707579919.JavaMail.tommy@smtp.sendgrid.net> In-Reply-To: <2025160620.59.1553707579919.JavaMail.tommy@smtp.sendgrid.net> Date: Wed, 27 Mar 2019 14:58:29 -0400 Message-ID: To: hcd_tc@collaborate.ccusersforum.org, "ipp@pwg.org" , tms_wg@trustedcomputinggroup.org, MPWG , neteq@trustedcomputinggroup.org, Ira McDonald Subject: [IPP] Fwd: Webcast Recording Available for Webcast: NIST Threshold Cryptography Workshop 2019 X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============4728723058036222241==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4728723058036222241== Content-Type: multipart/alternative; boundary="000000000000b330c4058518068d" --000000000000b330c4058518068d Content-Type: text/plain; charset="UTF-8" FYI ---------- Forwarded message --------- From: Crissy Robinson Date: Wed, Mar 27, 2019 at 1:26 PM Subject: Webcast Recording Available for Webcast: NIST Threshold Cryptography Workshop 2019 To: Dear Ira McDonald: Thank you for registering for *Webcast: NIST Threshold Cryptography Workshop 2019* on March 11 - 12, 2019 The webcast recording and presentations can be found at *https://www.nist.gov/news-events/events/2019/03/nist-threshold-cryptography-workshop-2019 * *Get Social:* Follow @USNISTGOV and join our Twitter Chat. For any questions or comments, please email ntcw2019@nist.gov *#NTCW2019* Thank you! Registrant Details First name Ira Last name McDonald Company name High North Inc Email Address blueroofmusic@gmail.com Thank you for your registration. --000000000000b330c4058518068d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

    FYI


    ---------- Forwarded message ---------
    From: Crissy Robinson <<= a href=3D"mailto:event-information@certain.com">event-information@certain.c= om>
    Date: Wed, Mar 27, 2019 at 1:26 PM
    Subject: Webcast= Recording Available for Webcast: NIST Threshold Cryptography Workshop 2019=
    To: <blueroofmusic@gmail= .com>


    =20 =20 =09 =09 =09 =20 =09
    =09 =09
    3D""
    =C2=A0
    Dear Ira McDonald:
    =C2=A0
    Thank you for registering for Webcast: NIST Threshold Cryptography = Workshop 2019 on March 11 - 12, 2019
    =C2=A0
    The webcast recording and presentations can be found at=C2=A0https://www.nist.gov/news-events/eve= nts/2019/03/nist-threshold-cryptography-workshop-2019
    =C2=A0
    Get Social:
    Follow @US= NISTGOV=C2=A0and join our Twitter Cha= t.=C2=A0For any questions or comments, please email ntcw2019@nist.gov=C2=A0
    =C2=A0
    #NTCW2019
    =C2=A0= =C2=A0
    Thank you!
    =C2=A0
    =C2=A0
    =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09

    =09 =09 Registrant Details =09
    First name=C2=A0 Ira=C2=A0
    Last name=C2=A0 McDonald=C2=A0
    Company name=C2=A0 High North Inc=C2=A0
    Email Address=C2=A0 blueroofm= usic@gmail.com=C2=A0


    Thank you for your re= gistration.
    =09
    =09 3D""
    =09 =09
    --000000000000b330c4058518068d-- --===============4728723058036222241== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4728723058036222241==-- From ipp-bounces@pwg.org Wed Mar 27 14:21:56 2019 Return-Path: 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 CA899120045 for ; Wed, 27 Mar 2019 14:21:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.271 X-Spam-Level: X-Spam-Status: No, score=-2.271 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.428, 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 KSr-aLIfS-tL for ; Wed, 27 Mar 2019 14:21:53 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id E4D98120033 for ; Wed, 27 Mar 2019 14:21:52 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 655223F4C; Wed, 27 Mar 2019 21:21:51 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 363C32491; Wed, 27 Mar 2019 21:21:43 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 1ABBB3BB7; Wed, 27 Mar 2019 21:21:42 +0000 (UTC) Received: from mail-yw1-xc29.google.com (mail-yw1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by www.pwg.org (Postfix) with ESMTPS id 7994F2667 for ; Wed, 27 Mar 2019 21:21:40 +0000 (UTC) Received: by mail-yw1-xc29.google.com with SMTP id x129so12907091ywc.1 for ; Wed, 27 Mar 2019 14:21:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Qt98Zgs5hVjUATvMjEIx0HdGqzFinylxlZ4g2108xrs=; b=aHpH/THZPmMj8oxEI0tpeOknmN47jWfpHhfAeBeJvyx/FpiOrLQ6ViRHjkH2rSD7XH Kss+mlfApFokMcmhjhryqY+B8pIirFC3tQimeje0BZ8ya7WrFuXO1AXY6p1A4E4pk+Rn PoclPt37xeUl21i4wo2nx55U4iB25ZpmbDBt0Uratkm5rqYs6OFSHYNw0yM+RoIRW4/s UjbBXO5AfVoS8S9hO6GzhGRR6yrt1DWmXZS2nzvU+RpAhsN/hSMQ+BFpZlaxwaOs6zVa ZAHUHyt0Mw/BJUgFNgBWHbrlgOGQ2f5PmiyeSgZE4z5TmeJlk0P+l8LxqTQUJmzkRUyS IpRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Qt98Zgs5hVjUATvMjEIx0HdGqzFinylxlZ4g2108xrs=; b=KOQkqOki/7AcpIc0Wzzr4tdit4VPEkgG0D8A43MyJ9Cq271kpxG2MYDC9uzu7g8Cdp SVM+zqC7IatuyqOPdzzvKSHdKS97eTUKOlanIX+t19BxLLUSqvj06x8i6sh6sxHg8FBx lQ7lIbIeHQ+ZFEeBMH99nJbbJZyZw3Sp3IZiqKE+iBXAJU5qmx+edOcBOxYqv/Hr96ac o/K8Dnn5o5HrHsX+R0oFaqXj3ADMJGs+0g0QhY3L98GDWI0qWFrwQ2mic1UYGTBoIrD2 gCeP8nW8H7TpB0p0Hl4XyX4Se8DHSCjyd62DrxnLDQFbceQ9S7VSz8CTUprwxar1wTyR 0Chg== X-Gm-Message-State: APjAAAXhib2OD8AGQ+SppZMMEQPfmI38E3pOZzpacA8PYSS08m46tF6M ANw0662a4sFpD5v9PwIyHhlS21krE+1lmA8giEgW2eHS X-Google-Smtp-Source: APXvYqwi3zC5W0lEVfI4I9Q04q/D7UNVjeWNyNb2A9aYhfkioj2vosIn9AihPlgNVXJ7uJvcCgs2+1R1vj6joswlgiI= X-Received: by 2002:a25:ea02:: with SMTP id p2mr32033005ybd.41.1553721699292; Wed, 27 Mar 2019 14:21:39 -0700 (PDT) MIME-Version: 1.0 Date: Wed, 27 Mar 2019 17:21:27 -0400 Message-ID: To: "ipp@pwg.org" , Ira McDonald Subject: [IPP] IPP WG Agenda 3:00-4:30pm US Eastern (28 March 2019) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============8246605841418213288==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8246605841418213288== Content-Type: multipart/alternative; boundary="000000000000f75d2605851a055b" --000000000000f75d2605851a055b Content-Type: text/plain; charset="UTF-8" Hi, Our next IPP WG call will be Thursday 28 March 2019 at 12:00-1:30pm US Pacific / 3:00pm-4:30pm US Eastern NOTE: Please USE the *new* WebEx and Audio Bridge below ------------------------------------------------------- Meeting information ------------------------------------------------------- Topic: IPP WG Every 2 weeks on Thursday 3:00-4:30 pm US Eastern (GMT-05:00) ------------------------------------------------------- WebEx online meeting (join WebEx first, before audio bridge) ------------------------------------------------------- 1. Go to https://ieee-isto.webex.com/ieee-isto/j.php?MTID=m8952a7e2500bbe43a428c15193736ec0 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: Printing123 4. Click "Join". ------------------------------------------------------- Audio Bridge (join audio second w/ unique access code from WebEx) ------------------------------------------------------- Call-in toll-free number (US/Canada): +1 866 469-3239 <%28866%29%20469-3239> Call-in toll number (US/Canada): +1 650 429-3300 <%28650%29%20429-3300> Call-in toll number (US/Canada): +1 408 856-9570 <%28408%29%20856-9570> Global toll-free call in numbers and other audio options ("Call Me Back" or VoIP) are listed once you join the WebEx meeting. Unique attendee access code: Displayed in the WebEx meeting Agenda: (1) PWG IP Policy, Minute Taker, Roll Call, and Agenda Review - Volunteer as minute taker? -- Status of all IPP documents in progress up-to-date below -- Discussion or review topics for today? (2) Approve IPP minutes from previous meetings - http://ftp.pwg.org/pub/pwg/ipp/minutes/ippv2-concall-minutes-20190314.pdf -- IPP WG call on 02/28/19 (3) Status/Review of various IPP mailing list notes - http://www.pwg.org/archives/ipp/2019/019991.html -- RFC: Relationship between job-retain-until-xxx and job-password (Mike) - http://www.pwg.org/archives/ipp/2019/019996.html -- Draft slides for the April F2F posted (Mike) - http://www.pwg.org/archives/ipp/2019/020010.html -- Fwd: 3D Printing and Transportation International Conference (Ira) - http://www.pwg.org/archives/ipp/2019/020011.html -- FYI: Progress on IPP Everywhere v1.1 Self-Certification Tools (Mike) - http://www.pwg.org/archives/ipp/2019/020014.html -- Fwd: [saag] TLS WG report from IETF104 (Ira) - http://www.pwg.org/archives/ipp/2019/020015.html -- Fwd: Webcast Recording: NIST Threshold Cryptography Workshop 2019 (Ira) (4) Status of AMSC and ISO liaisons w/ PWG (Paul) - https://ftp.pwg.org/pub/pwg/general/sc/pwg-sc-call-minutes-20190225.htm -- see PWG SC minutes from 25 February 2019 (5) LCRC Review of Safe G-Code (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgsafegcode10-20190318-rev.pdf - https://ftp.pwg.org/pub/pwg/ipp/wd/lcrc-pwgsafegcode10.txt -- Stable draft - PWG F2F discussion in February 2019 -- PWG Last Call ended 28 February 2019 -- Schedule - PWG Formal Vote in Q2 2019 (6) LCRC Review of IPP Authentication Methods (Smith) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- PWG Last Call ended 28 February 2019 - technical changes! -- Schedule - second IPP WG Last Call in Q2 2019 (7) Status of IPP 3D Printing Extensions v1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d11-20190201-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- PWG Call for Objections ends 29 March 2019 -- Schedule - Publication as PWG Candidate Standard in Q2 2019 (8) Status of IPP Everywhere 1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeve11-20190128-rev.pdf - http://www.pwg.org/archives/ipp/2019/020011.html -- Stable draft - PWG F2F discussion in February 2019 -- Defer PWG Last Call until IPP Everywhere 1.1 Self-Cert is ready -- Schedule - Stable working drafts/beta tools in Q2 2019 (9) Status of IPP Everywhere 1.1 Self-Certification Manual 1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeveselfcert11-20180704-rev.pdf - http://www.pwg.org/archives/ipp/2019/020011.html -- Prototype draft - PWG F2F discussion in February 2019 -- If we use Github to host the PWG website, how to submit printers? -- Consensus - Mike to update to separate submission process from self-cert process -- Stable URL for submissions (backport to 1.0 tools/process) -- Schedule - Stable working drafts/beta tools in Q2 2019 (10) Status of IPP System Service (Ira/Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsystem10-20190130-rev.pdf -- Prototype draft - PWG F2F review in February 2019 -- Prototyping tasks being tracked as a Github project in "ippserver" -- Schedule - Stable working draft and PWG Last Call in Q2 2019 (11) Status of PWG MFD Alerts 1.1 (Ira) - http://ftp.pwg.org/pub/pwg/ipp/wd/wd-pwgmfdalerts11-20190317-rev.pdf -- Stable draft - PWG F2F review in February 2019 -- Added "Overview of Changes" section -- PWG Call for Objections ends 12 April 2019 -- Schedule - Publication as PWG Candidate Standard in Q2 2019 (12) Status of IPP Document Object v1.1 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippdocobject11-20190318-rev.pdf -- Stable draft - PWG F2F discussion in February 2019 -- Prototyping tasks being tracked as a Github project in "ippserver" -- Schedule - IPP WG Last Call in Q2 2019 (13) Status of IPP Job Extensions v2.0 (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobext20-20190315-rev.pdf -- Prototype draft - for IPP WG and PWG F2F review -- Lots of additions from JPS2 - publish as v2.0 -- Schedule - Stable draft and IPP WG Last Call in Q2 2019 (14) Status of IPP Enterprise Printing Extensions v2.0 (formerly JPS2) (Smith) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf -- Initial draft - for IPP WG and PWG F2F review -- Selected content from former JPS2 w/ new Job Retention content -- Schedule - Prototype draft Q3 2019 (15) Status of IPP Encrypted Jobs and Documents (Mike) - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipptrustnoone10-20190131-rev.pdf -- Interim draft - PWG F2F discussion in February 2019 -- Remove S/MIME and use only PGP -- Schedule - Prototype draft Q3 2019 (16) Open Printing update (Ira) -- OP monthly calls (02/12/19) and (03/05/19) and (04/02/19) -- OP website renovation major progress using Jekyll - new developer team -- GSoC 2019 OP project edits closed (02/06/19) -- GSoC 2019 Linux Foundation mentor application accepted (02/26/19) -- GSoC 2019 Student application period begins (03/25/19) -- GSoC 2019 Student application period ends (04/09/19) -- GSoC 2019 Accepted student proposals announced (05/06/19) (17) Next steps - IPP WG call on Thu 11 April 2019 at 3:00-4:30pm US Eastern -- slide review for April 2019 PWG/OP F2F - IPP sessions on Wed/Thu 17-18 April 2019 during PWG/OP F2F -- see agenda on PWG meetings page - IPP WG call on Thu 25 April 2019 at 3:00-4:30pm US Eastern -- debrief April 2019 PWG/OP F2F 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 --000000000000f75d2605851a055b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    Our next IPP WG call will be Thursday 28 March 201= 9 at
    12:00-1:30pm US Pacific / 3:00pm-4:30pm US Eastern

    NOTE: Please USE the *new* WebEx and= Audio Bridge below

    -----------------------------= --------------------------
    Meeting information
    ----------------------= ---------------------------------
    Topic: IPP WG
    Every 2 weeks on Thursday 3:00-4:30 pm US= Eastern (GMT-05:00)

    -------------------------------------------------------
    WebEx onli= ne meeting (join WebEx firs= t, before audio bridge)
    -----------------------------------------= --------------
    1. Go to https://= ieee-isto.webex.com/ieee-isto/j.php?MTID=3Dm8952a7e2500bbe43a428c15193736ec= 0
    2. If requested, enter your name and email address.
    3. If a pas= sword is required, enter the meeting password: Printing123
    4. Click &quo= t;Join".

    ------------------------------------------------------= -
    Audio Bridge (j= oin audio second w/ unique access code from WebEx)
    --------------= -----------------------------------------
    Call-in toll-f= ree number (US/Canada): +1 866 469-3239
    Call-in toll num= ber (US/Canada): +1 650 429-3300
    Call-in toll number (US= /Canada): +1 408 856-9570

    Global toll-free call in numbers and other audio opti= ons ("Call Me Back" or VoIP) are listed once you join th= e WebEx meeting.

    Unique attendee access code:=C2=A0 Displayed in the= WebEx meeting

    <= span class=3D"gmail-m_-1788310161571561638gmail-m_6680213732158378097gmail-= m_8358460675102674886gmail-m_192412009110476038gmail-m_-9126277490835470395= gmail-m_678064946033773462m_-5854844899963712439gmail-m_351410749831127369g= mail-m_8437451791190766936gmail-m_-1214368787200127712gmail-m_1427353356034= 466677gmail-m_3588819687867355882gmail-m_4023217239496825783gmail-m_-349312= 7813630782611gmail-m_2636967438664975264gmail-m_287092529376793352gmail-m_-= 8110256533119532108gmail-m_-1421859593700570328gmail-m_-172113590160972163g= mail-m_-3552494186533607003gmail-m_-450012683051888877gmail-m_-715881909385= 2740809gmail-m_-5208763249917800182gmail-m_8332558219262867178gmail-m_-4355= 62576303993954gmail-il">Agenda:
    (1) PWG IP Policy, Minut= e Taker, Roll Call, and Agenda Review
    - Volunte= er as minute taker?
    -- Status of all IPP do= cuments in progress up-to-date below
    -- Discussion or review topi= cs for today?

    (2) Approve IPP minutes from= previous meetings

    (3) Status/Review of various IPP mailing li= st notes
    http://www.pwg.org/archives/ipp/2019/019991.html
    -- RFC: Relationship between job-retain-until-xxx and job-password = (Mike)
    -- Draf= t slides for the April F2F posted (Mike)
    -- Fwd: 3D Printing and Transportation Inter= national Conference (Ira)
    -- FYI: Progress on IPP Everywhere v1.1 Self-Certification = Tools (Mike)
    - http://www.pwg.org/archives/ipp/2019/020014.html
    -- Fwd: [saag] TLS WG report from IETF104 (Ira)
    -- Fwd: Webcast Recording:= NIST Threshold Cryptography Workshop 2019 (Ira)
    (4) Status of AMSC and ISO liaisons w/ PWG (Paul)
    =
    -- see PWG SC minutes from 25 February 2019

    =
    -- Stable draft - PWG F2F discussion in February 2019
    -- PWG Last Call ended 28 F= ebruary 2019
    -- Schedule - PWG Formal Vote in Q2 2019

    (6) LCRC Review of IPP Authenticati= on Methods (Smith)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190304-rev.pdf=C2=A0=C2= =A0=C2=A0
    -- Stable draft - PWG F2F discussion in February 2= 019
    -- PWG Last Call ended 28 F= ebruary 2019 - technical changes!
    -- Schedule - second IPP WG Last Call in Q2 2019

    (7) Status of IPP 3D Printing Extensions v1.1 (Mike)
    -- Stable draft -=C2=A0 PWG F2F discussion in February 2019
    = -- PWG Call for Objections = ends 29 March 2019
    -- Schedule - Publication as PWG Ca= ndidate Standard in Q2 2019

    - http://www.pwg.org/archives/ipp/2019/020011.htm= l
    -- Stable draft - PWG F2F discussion in February 2019
    -- Defer PWG Last Cal= l until IPP Everywhere 1.1 Self-Cert is rea= dy
    -- Schedule - Stable working drafts/beta tools= in Q2 2019

    (9) Status of IPP Everywhere 1.1 Self-Certification Manual 1.1 (= Mike)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeveselfcert11-20= 180704-rev.pdf
    -=20 http://www.pwg= .org/archives/ipp/2019/020011.html
    --=20 Prototype draft - PWG F2F discussion in February 2019
    -- If we use Github to host the PWG website, how to sub= mit printers?
    -- Consensus - Mike to update to separate submission proce= ss from self-cert process
    -- Stable URL for submissions (backport to 1.0= tools/process)
    -- Schedule - Stable working drafts/beta t= ools in Q2 2019

    (10) Status of IPP System Service = (Ira/Mike)
    - https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsystem10-20190130-rev.pdf
    -- = Prototype draft=20 - PWG F2F review in= February 2019
    -- Prototyping tasks being tracked as a Github pro= ject in "ippserver"
    -- Schedule - Stable working draft and PWG= Last Call in Q2 2019


    -- Prototyping tasks being tracked as a Github project in "ippserver&q= uot;
    -- Schedule - IPP WG Last Call in Q2 2019

    (13) Status of IPP Job Extensio= ns v2.0 (Mike)
    -- Protot= ype draft - for IPP WG and PWG F2F review
    -- Lo= ts of additions from JPS2 - publish as v2.0
    -- Schedul= e - Stable draft and IPP WG Last Call in Q2= 2019

    (14) Status of IPP<= /span> Enterprise Printing Extensions v2.0 (formerly JPS2) (Smith)
    -- Ini= tial draft - for IPP WG and PWG F2F review
    -- Selected content from former JPS2 w/ new Job R= etention content
    -- Schedule - Prototype draft Q3 2019=

    (15) Status of IPP Encrypted Jobs and Documents (Mike)<= br>- https://ftp.pwg.org/pub/p= wg/ipp/wd/wd-ipptrustnoone10-20190131-rev.p= df
    -- Interim draft - PWG F2F discussion in February 2019
    -- Remove S/MIME and use only PGP
    =
    -= - Schedule - Prototype draft Q3 2019

    (16) Open Printing update (Ira)<= /div>
    -- OP monthly calls (02/12/19) and (03/05/19) and (04/02/19)
    <= /div>
    -- OP website renovation major progress using Jekyll - new develo= per team
    -- GSoC 2019 OP project edi= ts closed (02/06/19)
    -- GSoC 2= 019 Linux Foundation mentor application accepted (02/26/19)
    -- GSoC 2019 Student application p= eriod begins (03/25/19)
    -- GSoC 2019 Student application p= eriod ends (04/09/19)
    -- GSoC 2019 Accepted student proposals ann= ounced (05/06/19)

    (17) Next steps
    - IPP WG call on Thu 11 April 2019 at 3:00-4:30pm US Eastern
    -- slide review for April 2019 PWG/OP F2F

    - IPP sessions on Wed/Thu 17-18 April 2019 during P= WG/OP F2F
    -- see agenda on PWG me= etings page

    - IPP WG call on Thu 25 April 2019 at 3:00-4:30pm US Eastern
    -- debrief April 2019 PWG/OP F2F

    Cheers,
    - Ira


    Ira McDonald (Music= ian / 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 Print= er Working Group
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<= br>IETF Designated Expert - IPP & Printer MIB
    Blue Roof Music / High= North Inc
    http://sites.google.com/site/blu= eroofmusic
    http://sites.google.com/site/= highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais,= MI 49839=C2=A0 906-494-2434

    <= /div>
    <= /div>
    --000000000000f75d2605851a055b-- --===============8246605841418213288== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8246605841418213288==-- From ipp-bounces@pwg.org Thu Mar 28 14:23:16 2019 Return-Path: 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 570D612003F for ; Thu, 28 Mar 2019 14:23:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 MDs32ILN-27y for ; Thu, 28 Mar 2019 14:23:13 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id AE1921202C1 for ; Thu, 28 Mar 2019 14:23:13 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id EFFA54072; Thu, 28 Mar 2019 21:23:12 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 136F42491; Thu, 28 Mar 2019 21:23:09 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id 8F62B3B9E; Thu, 28 Mar 2019 21:23:08 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [63.128.21.162]) by www.pwg.org (Postfix) with ESMTPS id 13B842491 for ; Thu, 28 Mar 2019 21:23:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1553808186; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=3nqcsQ8k4THI9iU46sIlZeggHog5D+YG7B5pUo3abtQ=; b=cUwCKmknKbOiK+ps0b8x0BXpoEc9iZiw3ElZazxfEuUNS7rfWeCM/5pvS2z8nHT3LZq9UZJQL/Q1uV80DUIZI2Z0LBdO0/wxt0IN/R0NIUycs5YlJcExEO8ho9MJTj1TQ+RfrAot15K56XzvF6tOSqCGIbKIfNdIXFb0MpCdXkY= Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-co1nam05lp2051.outbound.protection.outlook.com [104.47.48.51]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-110-v_J9_w8wONC6IV4h0_O1nw-1; Thu, 28 Mar 2019 17:23:04 -0400 X-MC-Unique: v_J9_w8wONC6IV4h0_O1nw-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1SPR00MB04.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.16; Thu, 28 Mar 2019 21:23:02 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898%2]) with mapi id 15.20.1730.019; Thu, 28 Mar 2019 21:23:02 +0000 To: PWG IPP WG Reflector Thread-Topic: Updated draft of IPP Authentication Methods available and ready for second IPP WG Last Call Thread-Index: AQHU5axsx60RTfwHfUu+LVjfj2JZLw== Date: Thu, 28 Mar 2019 21:23:02 +0000 Message-ID: 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: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d6db848a-3942-411b-3752-08d6b3c38f81 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1SPR00MB04; x-ms-traffictypediagnostic: CS1SPR00MB04: x-microsoft-antispam-prvs: x-forefront-prvs: 0990C54589 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(39860400002)(346002)(136003)(396003)(6602003)(189003)(199004)(26005)(68736007)(8676002)(6486002)(6506007)(36756003)(102836004)(81156014)(81166006)(7736002)(14444005)(606006)(256004)(5660300002)(476003)(97736004)(106356001)(105586002)(2616005)(15650500001)(6436002)(8936002)(99286004)(966005)(33656002)(186003)(99936001)(316002)(53936002)(478600001)(25786009)(82746002)(486006)(6916009)(83716004)(2906002)(71200400001)(14454004)(71190400001)(6306002)(86362001)(6116002)(3846002)(66066001)(6512007)(54896002)(236005); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1SPR00MB04; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: T1QCTMmNjWPYLCtuhnUFWWhKlsH0ftOB1Lwra3iN4y0RVkDs/49ZdiFniCmUdgk+j6bbuRVfCSRPNlWIybeo0KFMaGNubX7ULsBzvi+VqiNKUrzjn8u89FzfpUqRpFZNxBD4bpB2OjtVeKDJEYAHfimb0yqnIybg8k1TP1ZoeNFMzJ+N/yCfwE25WXe2q68B2/bEHrcVElraROLM90GFOUlqq6gykFeOfyPT4yKRODuknNo0Q1xlCGsQSeq1/v7wN9M4W0H2IHKx26Vq1uRNJV0ctd1CDSvwLbLzzHOzfBAsGCIhg0u0w4afapA3dIvZ8+vXvmr72Fw8PvR5l+sZp4GR6Ijo4cV/Cnt3YtPwF9hmiKboRKgXLUS4yaR506ZGT11Urj8aJxJX6/ty6uUZF/KgFTTIbPmgq+VLlf2pwos= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: d6db848a-3942-411b-3752-08d6b3c38f81 X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Mar 2019 21:23:02.5637 (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-Transport-CrossTenantHeadersStamped: CS1SPR00MB04 Subject: [IPP] Updated draft of IPP Authentication Methods available and ready for second IPP WG Last Call X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============8631266425892551507==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============8631266425892551507== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_14914CE0-9C4C-4B1F-8BB7-80AA0C7F7E62"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_14914CE0-9C4C-4B1F-8BB7-80AA0C7F7E62 Content-Type: multipart/alternative; boundary="Apple-Mail=_1293B225-10BB-46E7-AE51-77D08A08D15D" --Apple-Mail=_1293B225-10BB-46E7-AE51-77D08A08D15D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Greetings, I've just posted an updated draft of IPP Authentication Methods that = resolves all the issues we identified in this afternoon's IPP WG = meeting. https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328.odt = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328.pdf = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328-rev.odt = https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328-rev.pdf = If we could start a new IPP Work Group Last Call on this draft ASAP, we = would have time to complete that, run the PWG Last Call, and then have = it in PWG Formal Approval vote during our F2F. The two areas that should = have particular focus in these Last Calls are: the text in section 4 on = page 15 (lines 196-217 in the clean versions above); and the UML = Sequence Diagrams to see if they better illustrate the steps that = concern authorization and authentication, and how they represent the = steps needed to allow the Authorization Service to evaluate whether the = IPP operation request can be authorized or not. Cheers, Smith /** Smith Kennedy HP Inc. */ --Apple-Mail=_1293B225-10BB-46E7-AE51-77D08A08D15D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Greetings,

    I've just posted an updated draft of IPP Authentication = Methods that resolves all the issues we identified in this afternoon's = IPP WG meeting.

    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328.odt<= /div>
    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328.pdf&= nbsp;
    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328-rev.odt<= /a>
    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328-rev.pdf<= /a> 

    If we could start a new IPP Work Group Last Call on this = draft ASAP, we would have time to complete that, run the PWG Last Call, = and then have it in PWG Formal Approval vote during our F2F. The two = areas that should have particular focus in these Last Calls are: the = text in section 4 on page 15 (lines 196-217 in the clean versions = above); and the UML Sequence Diagrams to see if they better illustrate = the steps that concern authorization and authentication, and how they = represent the steps needed to allow the Authorization Service to = evaluate whether the IPP operation request can be authorized or = not.

    Cheers,

    Smith

    /**
        Smith = Kennedy
        HP Inc.
    */

    = --Apple-Mail=_1293B225-10BB-46E7-AE51-77D08A08D15D-- --Apple-Mail=_14914CE0-9C4C-4B1F-8BB7-80AA0C7F7E62 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlydOzUACgkQqskbKLDW 1N0qrA//UfEK0BeOBVoFE5+aUXhWNBwv2IBdokDz1E/4joB0df8bCsiQ0xBvV6A3 YGWJpDWcIwwtCifI7JbZhU2stC5IFtttZhy6IGzjnoHXn14EI3dfeac4hITFFKu2 7ZCv6/LCz+KI7leE4ZcOB6mNRJaObmFomiwYX0NoNGMn/WvBUxW7LB7sR1fmeE/q 6Uf5uQWoE5dJYspA817QeDLgAngK3tCNlHAnXcjY0N8yADwilZ/LArkHe6Ly132D gJVCEP4W6r16squqiMaBWAn8P+1TTDdyKJIw9Cq/T+RTyAPFVebfUjsfhSCzTlm8 LPgGzHcHSQPpFYOJk1pIte4//651xEgPl6UWsEU6jp/Fg5NC6orepAIfhSAYHcXS p/tVOkzAiFsFoCdWCFSYCuyG2WK7Pe27zE8Jm1GDcGf+xTirHBwS/ilEwHd9YUC8 V9Hp5gbuviXr+VgNEXfrblrTZAEVJIvlBozk8IEUdUETcd9Dbxb1vC56Z+PRB0yj Msc+z+hsMlnK27dmnA9HDNCOIMFM7GlEuGyOg6QvUx91KgZsIbEI+pbbIgQC+dCw AC41CpcrgbB3543BV2LLUNpzYsHNYXhHGDUg/hNuk8hbq6VQeOUx76Q5ipPwpQsM 7odLGWffEo8Zbbu1udFIXVCA3OfAjkSbHD88iqlhY3ISxbdCy5Q= =hu6X -----END PGP SIGNATURE----- --Apple-Mail=_14914CE0-9C4C-4B1F-8BB7-80AA0C7F7E62-- --===============8631266425892551507== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============8631266425892551507==-- From ipp-bounces@pwg.org Fri Mar 29 06:19:50 2019 Return-Path: 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 C255612036C for ; Fri, 29 Mar 2019 06:19:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 ODJShxMtd3kf for ; Fri, 29 Mar 2019 06:19:47 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9271202CE for ; Fri, 29 Mar 2019 06:19:44 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 384C23F4F; Fri, 29 Mar 2019 13:19:43 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 991121C9D; Fri, 29 Mar 2019 13:19:38 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id AC40D3BB7; Fri, 29 Mar 2019 13:19:37 +0000 (UTC) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) by www.pwg.org (Postfix) with ESMTPS id E965D1C9D for ; Fri, 29 Mar 2019 13:19:36 +0000 (UTC) Received: by mail-yb1-xb2b.google.com with SMTP id x79so833973ybg.2 for ; Fri, 29 Mar 2019 06:19:36 -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=4iiF1yiD8tshNO1XYcOi8de9py1AJe/IXglkCRE8vys=; b=IGRi/Rc5vo2tfzZZbH0Nh4JQWD11EOJFE03QJSYAvy6CbK5bjVUmaYaGmKitD3RxGZ 9c/QKTjGsr8KXNBk6VWiIAmuIcnFa4F61Gy0IJvr2PspAu+kyNZViQwmXFEyiQ4jW3fo zMm93YL8c1Si2AVNMr2QVnVAZ+U4izdHtBRoxKjycIJfnEZ0gsyyQe0BsenBLjAgUM35 5eviAU74YuSB0OzmXajoD0ZfYEaBFownliwa5Cp/fruDSPtKOYnHu7Pe2xnI77qzulcE K/kDZbeek05vIAFTaa6bh3Ze7sZP9wCfvcy0tEVnCDiuDEo0v1VBSkbwSgVMCAFQy6IA os9Q== 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=4iiF1yiD8tshNO1XYcOi8de9py1AJe/IXglkCRE8vys=; b=MYQAi86Wvtso+5eoGIu4Ne4J8nKK5VKglBJzfatWuQfaRJnKG9u1aFQBEPJfNrMMqw QWFM9vr+9pOLBx55yktb7d2UFa668D8jAL2ndsGJE9W2efGvibfj2oWOas6XltzK8s1Y Tp0FC4wB8g/EZrOx/6DW1NFD0xqRlJTi0FXFKgHciXZKuf23x1fU5Lj7ICL6aKrBgLNW OAx2KpmGLhADbSPM75pjxR34z6f4O/EYOChmgmSaeOB9WtLBWxmVBVPhiPth5Umufc5C GBvJ16ws88QaSdMdE5CudwecAYkfDIts+mrUE9HcqJaM+nXNX0Q2gCM2siuN3n389dGj r1Kg== X-Gm-Message-State: APjAAAXjeKRB6enaldHb0waTIi4BR0T2ZudzY8ho4U2Tg+wZexcyvTjZ xAuA2Dk/SMWFWIS6+97bNyWoPwea3phvV3SKtVs= X-Google-Smtp-Source: APXvYqyDiDYHoMbwZXIKFC/qgmKZ7Y/Ai7K15l+uYxaB+uH+gteRCgJYxm9MK3jM7K5UyJUl65eRVvXweIIvKLvtAh4= X-Received: by 2002:a25:20c2:: with SMTP id g185mr39105359ybg.308.1553865576207; Fri, 29 Mar 2019 06:19:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 29 Mar 2019 09:19:23 -0400 Message-ID: To: "Kennedy, Smith (Wireless & Standards Architect)" , Ira McDonald Cc: PWG IPP WG Reflector Subject: Re: [IPP] First draft of "IPP Enterprise Printing Extensions" posted for review X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6370702938556172431==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6370702938556172431== Content-Type: multipart/alternative; boundary="000000000000b2df8205853b850d" --000000000000b2df8205853b850d Content-Type: text/plain; charset="UTF-8" Hi Smith, A naming comment: The short name "ippepe" is too close to "ippeve". We usually use "x" for extensions, so I suggest "ippepx" as a more recognizably unique short 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Wed, Mar 27, 2019 at 11:00 AM Kennedy, Smith (Wireless & Standards Architect) via ipp wrote: > Greetings, > > I have just posted the first draft of "IPP Enterprise Printing > Extensions". Please review offline and I hope we have a chance to discuss > this at sometime in the near future. > > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf > > > Cheers, > > Smith > > /** > Smith Kennedy > Wireless & Standards Architect - IPG-PPS > Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum > / USB-IF > Chair, IEEE ISTO Printer Working Group > HP Inc. > */ > > > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > --000000000000b2df8205853b850d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    <= br>
    On Wed,= Mar 27, 2019 at 11:00 AM Kennedy, Smith (Wireless & Standards Archite= ct) via ipp <ipp@pwg.org> wrote:
    Greetings,

    I have just posted t= he first draft of "IPP Enterprise Printing Extensions". Please re= view offline and I hope we have a chance to discuss this at sometime in the= near future.


    Cheers,

    Smith

    /**
    =C2=A0 =C2=A0 Smith= Kennedy
    =C2=A0 =C2=A0 Wireless & Standards Architect - IPG-PPS
    = =C2=A0 =C2=A0 Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / = NFC Forum / USB-IF
    =C2=A0 =C2=A0 Chair, IEEE ISTO Printer Working Group<= br>=C2=A0 =C2=A0 HP Inc.
    */



    ___________= ____________________________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailman/listinfo/ipp
    --000000000000b2df8205853b850d-- --===============6370702938556172431== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6370702938556172431==-- From ipp-bounces@pwg.org Fri Mar 29 08:10:22 2019 Return-Path: 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 A1EC0120233 for ; Fri, 29 Mar 2019 08:10:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, 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 brvw2IhfCV0l for ; Fri, 29 Mar 2019 08:10:19 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 5906D12022A for ; Fri, 29 Mar 2019 08:10:19 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 5A65E3FD1; Fri, 29 Mar 2019 15:10:16 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id C9DBC26DC; Fri, 29 Mar 2019 15:10:11 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id C96513BB7; Fri, 29 Mar 2019 15:10:10 +0000 (UTC) Received: from us-smtp-delivery-162.mimecast.com (us-smtp-delivery-162.mimecast.com [216.205.24.162]) by www.pwg.org (Postfix) with ESMTPS id 21D532667 for ; Fri, 29 Mar 2019 15:10:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hp.com; s=mimecast20180716; t=1553872208; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=D7vpXAtwp1asQxYrUo4iEGdUPM5T5G1pE0HdQYnFdAw=; b=XHYTYoEHYKYg9MmXrDikCy0t6j6X6XcyvptxIwDZwpc9yizJbWIMmsq+WsiWRARp43czkR6/pACWR9GJH06IP2GPFwPYFaLnW57tz09J+B10SN2JQOw6GgkUjzcBjo0ZsgY6zD+gs8KhYIP+FNv96/n96qY9dL05JFArQSTtpGo= Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2051.outbound.protection.outlook.com [104.47.44.51]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-289-Oev0t0pGOLC-gWkAFT2iqw-1; Fri, 29 Mar 2019 11:10:03 -0400 X-MC-Unique: Oev0t0pGOLC-gWkAFT2iqw-1 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM (10.169.98.7) by CS1PR8401MB0822.NAMPRD84.PROD.OUTLOOK.COM (10.169.15.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.17; Fri, 29 Mar 2019 15:10:01 +0000 Received: from CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898]) by CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b5d9:13ce:fdf6:6898%2]) with mapi id 15.20.1730.019; Fri, 29 Mar 2019 15:10:01 +0000 To: Ira McDonald Thread-Topic: [IPP] First draft of "IPP Enterprise Printing Extensions" posted for review Thread-Index: AQHU5K2+aOGVKDbPWkejlMSFeu6zeaYimrGAgAAe6AA= Date: Fri, 29 Mar 2019 15:10:01 +0000 Message-ID: <194A949D-8683-4645-ACC8-C2529B6488AD@hp.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [66.232.89.139] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b423096c-8172-4b3e-18da-08d6b4589dcf x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(49563074)(7193020); SRVR:CS1PR8401MB0822; x-ms-traffictypediagnostic: CS1PR8401MB0822: authentication-results: spf=none (sender IP is ) smtp.mailfrom=smith.kennedy@hp.com; x-microsoft-antispam-prvs: x-forefront-prvs: 0991CAB7B3 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(366004)(346002)(136003)(396003)(39860400002)(376002)(189003)(6602003)(199004)(8936002)(3846002)(81166006)(8676002)(105586002)(106356001)(81156014)(316002)(6916009)(2906002)(6116002)(6512007)(6306002)(236005)(26005)(4326008)(2616005)(6506007)(54896002)(53936002)(229853002)(186003)(53546011)(99286004)(486006)(11346002)(6486002)(476003)(446003)(6436002)(99936001)(36756003)(25786009)(66574012)(86362001)(19273905006)(14454004)(97736004)(83716004)(1411001)(6246003)(606006)(102836004)(71190400001)(71200400001)(33656002)(68736007)(14444005)(256004)(66066001)(5660300002)(82746002)(7736002)(966005)(76176011)(478600001)(16351025005)(563064011)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:CS1PR8401MB0822; H:CS1PR8401MB1270.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: aXUAjiZKfFtoWsZ2aWYJMrC9PDhSA5Y4rG641TQ/HC1P/epcitd5Mbtc9Zetgr//crpypxSq5JtbNhDiBsYldtGcu2+nmC5ZklzYmw2wB8p6I/gQnLQsOrJWSwD9piwiNjocZRJzv716UtTpNpjTywNERcIgcULQa/qBy7+8l3C/v1F4eQZ+g62kNUY+Hlksf7az69ESiSRIqih7PDNsdPWDEC55NBgHakXBjtVeiKFhiGeOXC3g/cqbaVEIhbxMvmj/E3IfYLulvC/QRne43rnvxK+tqyk+cMcL8aq2BpGF7NFn5wjU6LgN9edD/l/pZCR96t/YdwOFcOY15/xC4mmxMjmK1uhXchsBOg+6x1BhPxswi+owKeerwalwJFEjMd4/C8qrQxoZ7fq7XNY3F5u1058comzdd+Ts9tZ5s5g= MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-Network-Message-Id: b423096c-8172-4b3e-18da-08d6b4589dcf X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Mar 2019 15:10:01.5159 (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-Transport-CrossTenantHeadersStamped: CS1PR8401MB0822 Cc: PWG IPP WG Reflector Subject: Re: [IPP] First draft of "IPP Enterprise Printing Extensions" posted for review X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Kennedy, Smith \(Wireless & Standards Architect\) via ipp" Reply-To: "Kennedy, Smith \(Wireless & Standards Architect\)" Content-Type: multipart/mixed; boundary="===============7671766605592484340==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============7671766605592484340== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_C7AF980E-C941-41DF-A3F5-F8F925ECEC77"; protocol="application/pgp-signature"; micalg=pgp-sha256 --Apple-Mail=_C7AF980E-C941-41DF-A3F5-F8F925ECEC77 Content-Type: multipart/alternative; boundary="Apple-Mail=_BFCF06B0-C704-40B0-95D8-8659B2A5675D" --Apple-Mail=_BFCF06B0-C704-40B0-95D8-8659B2A5675D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii OK - it'll use that name for the next revision, if that is OK, rather = than republishing. Smith > On Mar 29, 2019, at 7:19 AM, Ira McDonald = wrote: >=20 > Hi Smith, >=20 > A naming comment: The short name "ippepe" is too close to "ippeve". >=20 > We usually use "x" for extensions, so I suggest "ippepx" as a more > recognizably unique short name. >=20 > Cheers, > - Ira >=20 > 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/highnorthinc = > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 >=20 >=20 >=20 > On Wed, Mar 27, 2019 at 11:00 AM Kennedy, Smith (Wireless & Standards = Architect) via ipp > wrote: > Greetings, >=20 > I have just posted the first draft of "IPP Enterprise Printing = Extensions". Please review offline and I hope we have a chance to = discuss this at sometime in the near future. >=20 > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx = > https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf = >=20 > Cheers, >=20 > Smith >=20 > /** > Smith Kennedy > Wireless & Standards Architect - IPG-PPS > Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC = Forum / USB-IF > Chair, IEEE ISTO Printer Working Group > HP Inc. > */ >=20 >=20 >=20 > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp = --Apple-Mail=_BFCF06B0-C704-40B0-95D8-8659B2A5675D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii OK = - it'll use that name for the next revision, if that is OK, rather than = republishing.

    Smith



    On Mar 29, 2019, at 7:19 AM, Ira McDonald <blueroofmusic@gmail.com> wrote:

    Hi = Smith,

    A = naming comment:  The short name "ippepe" is too close to = "ippeve".

    We = usually use "x" for extensions, so I suggest "ippepx" as a = more
    recognizably unique short 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/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO = Box 221  Grand Marais, MI 49839  906-494-2434


    On Wed, Mar 27, 2019 at 11:00 AM = Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote:
    Greetings,

    I have just posted the first draft of = "IPP Enterprise Printing Extensions". Please review offline and I hope = we have a chance to discuss this at sometime in the near = future.

    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx<= /div>
    https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf

    Cheers,

    Smith

    /**
        Smith = Kennedy
        Wireless & Standards Architect - = IPG-PPS
        Standards - IEEE ISTO PWG / = Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF
      =   Chair, IEEE ISTO Printer Working Group
      =   HP Inc.
    */



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

    = --Apple-Mail=_BFCF06B0-C704-40B0-95D8-8659B2A5675D-- --Apple-Mail=_C7AF980E-C941-41DF-A3F5-F8F925ECEC77 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEX4TM/E2Pr7lTZzy2qskbKLDW1N0FAlyeNUgACgkQqskbKLDW 1N1FKw//Zz8ghn4ok83P8SCRcjll4cxUhLJaJEFRA9v3cGEtojPte7xTGwE1sHDC Ur5HAKCnOdnCdMISzeD3H37pJUhmpxbgV6NZJZivF9HQeOOVdd7Nu/Volw1WB9Pc NSibwQXhSpvDuL7mUOEVOi48yLhD8aLUZBzU8qiVR2HRsgcc/9m93MXvF1IonS3l D8k+AWH1W58W1O7rVJjxI5DDyK+qFDe75oMqbVemU1qFka8qRZAToCpxevrGT7g1 kiAj+uVSxVuyWEyiBJBvV8VjFXZlCYyHH9xWy1tuUaz01PIFxOfbQwXCEXiGSFKN wZGw5Ut1BzmQx4zol0l45asX8QUYQ/8lKArRF3E8mPfJ0AVpC3sgjBb+GMLJQzFD ozHNVo+izLHLMux60a3m3Vw3g6GetFPCD6/fJu7xldE5lYOFjJZP8WIh22i/tayk tNLIBRbQRaCTLN5WhBHzY3oRjv4m6fF4HT7SkA39A+gFqFO4zyFltIU4VJTyfTxg ikmHm2/Ii0DJ8LjVIpSwvYPVICJ8XCdLWfs/F9UbNN2eiAIAug8Ccqp6zN8LV1Mo N9UdaViV7DE3jwgFj3ebH6rwT22YP5h8bE3XealmxvATOSb9N0Po7Zss4whwCHtA dw+btgKPr4jepBRv2SaJ8nCo/yrpovoqbX1f4BYJhtKVricU4Nk= =FS2I -----END PGP SIGNATURE----- --Apple-Mail=_C7AF980E-C941-41DF-A3F5-F8F925ECEC77-- --===============7671766605592484340== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============7671766605592484340==-- From ipp-bounces@pwg.org Fri Mar 29 10:54:52 2019 Return-Path: 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 CF66E1202B8 for ; Fri, 29 Mar 2019 10:54:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.71 X-Spam-Level: X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, MAILING_LIST_MULTI=-1, 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 acD_qTwm8-y9 for ; Fri, 29 Mar 2019 10:54:50 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 13B451202D9 for ; Fri, 29 Mar 2019 10:54:45 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 287503F51; Fri, 29 Mar 2019 17:54:42 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 08A9726DC; Fri, 29 Mar 2019 17:54:37 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id A9A043BB7; Fri, 29 Mar 2019 17:54:35 +0000 (UTC) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) by www.pwg.org (Postfix) with ESMTPS id AE8B42491 for ; Fri, 29 Mar 2019 17:54:34 +0000 (UTC) Received: by mail-yw1-xc2c.google.com with SMTP id d132so983602ywa.2 for ; Fri, 29 Mar 2019 10:54:34 -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=xIRQ6J8Yk2MWhAzl5vdOyMqu1OvRzJQ9oDrHRfNxGqI=; b=olacgyl+FlFYdu3Y+c5dWl2c5DTvOTgzDGodc3e8tSntaUL5g+zL3KBqrQ5RTGIt4N FsMfgOnIjbx8bggPi5qWoppI831o63K5c1CMPlcX2MLsQcgsmc+KLX+jR5op2tsi5WHx ysv4j313hIIsTYs6o+6MqvdY4I+RQoSMOkiGF24nRYZ1L1LegX+gt/rAtEM1D72BQS9M WxjllWxx9I/QhVe/yNrO2yaYEWceyDzihh5L4Pe3TvS32xD2yj+ctgo+W4qlHWi3ViBg YLzIN7k93ZBEM6zzdwkRpm4Owe41FqgA5WSLURxsM+EoOyThles8jwaymEuhZPKw7AGB xpqA== 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=xIRQ6J8Yk2MWhAzl5vdOyMqu1OvRzJQ9oDrHRfNxGqI=; b=rRpRsLW3nqHwR8bIUnaQhXPkJft7RgL0BcWuWra1CCWmVu2AmrGuM2ThqBKulpSxra MvPC9SYqfm+qP1tLF8gN2a3g/bjtxF026MKcenlI0adp32ljP7NEczQfVe+J1u9svMD3 DvCI80UBFGHyRNMwySg8k3FD8zpKM6CiEToDK0lKbzB7XiWgrdsCov3h4EzPXXhDRL4i 9CXKzlgUExnGAQLrarmtSlYnhOJ58d3rCMc9tnw7qVgyPdlMD//h9Ghxo3ttjOqHwfJq xb/mIxGhVGXWw33soapGEvXNn73VDskTvGphdvopcfKFoA9yaxo8Iww22gSnzakZWrwq Jifw== X-Gm-Message-State: APjAAAWPGVgQTXCunh8oevOFBoCaeDTzqfhD9AEekIwykZDEPeKiZIsn rE0RKfCqXwqjvWgX6kD9LkgZ0ZjEHBL5IuDHhRY= X-Google-Smtp-Source: APXvYqzkygJW5BKou2VU4O3hvEhV49uTG+ApFQOA0npuJbh1nWqYRhMVvYpUhPD0oYpL+ln9GsaCZp8LZDhIIT9rha4= X-Received: by 2002:a0d:cc12:: with SMTP id o18mr43608000ywd.501.1553882074021; Fri, 29 Mar 2019 10:54:34 -0700 (PDT) MIME-Version: 1.0 References: <194A949D-8683-4645-ACC8-C2529B6488AD@hp.com> In-Reply-To: <194A949D-8683-4645-ACC8-C2529B6488AD@hp.com> Date: Fri, 29 Mar 2019 13:54:21 -0400 Message-ID: To: "Kennedy, Smith (Wireless & Standards Architect)" , Ira McDonald Cc: PWG IPP WG Reflector Subject: Re: [IPP] First draft of "IPP Enterprise Printing Extensions" posted for review X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============4766529030253574030==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============4766529030253574030== Content-Type: multipart/alternative; boundary="0000000000000b85c605853f5dcd" --0000000000000b85c605853f5dcd Content-Type: text/plain; charset="UTF-8" Hi Smith, Thanks - certainly no need to republish this version. 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 On Fri, Mar 29, 2019 at 11:10 AM Kennedy, Smith (Wireless & Standards Architect) wrote: > OK - it'll use that name for the next revision, if that is OK, rather than > republishing. > > Smith > > > > On Mar 29, 2019, at 7:19 AM, Ira McDonald wrote: > > Hi Smith, > > A naming comment: The short name "ippepe" is too close to "ippeve". > > We usually use "x" for extensions, so I suggest "ippepx" as a more > recognizably unique short 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/highnorthinc > > mailto: blueroofmusic@gmail.com > PO Box 221 Grand Marais, MI 49839 906-494-2434 > > > > On Wed, Mar 27, 2019 at 11:00 AM Kennedy, Smith (Wireless & Standards > Architect) via ipp wrote: > >> Greetings, >> >> I have just posted the first draft of "IPP Enterprise Printing >> Extensions". Please review offline and I hope we have a chance to discuss >> this at sometime in the near future. >> >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.docx >> >> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippepe-20190327.pdf >> >> >> >> Cheers, >> >> Smith >> >> /** >> Smith Kennedy >> Wireless & Standards Architect - IPG-PPS >> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC >> Forum / USB-IF >> Chair, IEEE ISTO Printer Working Group >> HP Inc. >> */ >> >> >> >> _______________________________________________ >> ipp mailing list >> ipp@pwg.org >> https://www.pwg.org/mailman/listinfo/ipp >> >> > > --0000000000000b85c605853f5dcd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi Smith,

    Thanks - certainly= no need to republish this version.

    Cheers,
    <= div>- 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 No= rth Inc
    http://sites.google.com/site/bluero= ofmusic
    http://sites.google.com/site/hig= hnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marais, M= I 49839=C2=A0 906-494-2434



    On Fri, Mar 29, 2019 at 11:10 AM Kennedy, Smith (W= ireless & Standards Architect) <smith.kennedy@hp.com> wrote:
    OK - it&= #39;ll use that name for the next revision, if that is OK, rather than repu= blishing.

    Smith



    On Mar 29, 2019, at 7:19 AM, Ira Mc= Donald <blu= eroofmusic@gmail.com> wrote:

    Hi Smith,

    A naming comment:=C2=A0 The short name "ippepe&qu= ot; is too close to "ippeve".

    We usually= use "x" for extensions, so I suggest "ippepx" as a mor= e
    recognizably unique short 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 No= rth Inc
    http://sites.google.com/site/blueroofmusic
    http://sites.google.com/si= te/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Mara= is, MI 49839=C2=A0 906-494-2434

    =


    On Wed, Mar 27, 2019 at 11:00 AM Kennedy, Smi= th (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote:
    Greetings,

    I = have just posted the first draft of "IPP Enterprise Printing Extension= s". Please review offline and I hope we have a chance to discuss this = at sometime in the near future.


    Cheers,=

    Smith

    /**
    =C2=A0 =C2=A0 Smith Kennedy
    =C2=A0= =C2=A0 Wireless & Standards Architect - IPG-PPS
    =C2=A0 =C2=A0 Stand= ards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<= br>=C2=A0 =C2=A0 Chair, IEEE ISTO Printer Working Group
    =C2=A0 =C2=A0 HP= Inc.
    */



    ______________________________= _________________
    ipp mailing list
    ipp@pwg.org
    https://www.pwg.org/mailma= n/listinfo/ipp

    --0000000000000b85c605853f5dcd-- --===============4766529030253574030== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============4766529030253574030==-- From ipp-bounces@pwg.org Fri Mar 29 15:40:46 2019 Return-Path: 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 3658B120354 for ; Fri, 29 Mar 2019 15:40:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_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 f8Rw84Gx-7JA for ; Fri, 29 Mar 2019 15:40:43 -0700 (PDT) Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id CA6C9120255 for ; Fri, 29 Mar 2019 15:40:43 -0700 (PDT) Received: by www.pwg.org (Postfix, from userid 1002) id 8F6D43F4C; Fri, 29 Mar 2019 22:40:41 +0000 (UTC) Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id EBEB326DC; Fri, 29 Mar 2019 22:40:37 +0000 (UTC) X-Original-To: ipp@pwg.org Delivered-To: ipp@pwg.org Received: by www.pwg.org (Postfix, from userid 1002) id F0BFD3BB7; Fri, 29 Mar 2019 22:40:35 +0000 (UTC) Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) by www.pwg.org (Postfix) with ESMTPS id 220932491 for ; Fri, 29 Mar 2019 22:40:35 +0000 (UTC) Received: by mail-yb1-xb36.google.com with SMTP id k10so1450797ybd.3 for ; Fri, 29 Mar 2019 15:40:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=HUW76tWih7CvBsBued7I7ZRmF+OD8mJw5CbJYRINQw8=; b=izl9GJnYMQjrSsyxQMu41NNW469PPLLo5B4TpCMHcrAJIBM6s+bok1JsO4qYEhZnUB 91GkAUPXyqY2LJL6tgXOWwD7Wzu6RBGdetRlWkjswrWdcTQazrnmbRxHCwDJGqPYsl4T qJzsPlnTM00/7B560W9yl1tYEoWfieSrqnW/z1tVOL77DldB8DWyLZbspSP6vwU0thfY MH4HqScGtHiwQ3eqLa1zhW0ShLb3rt5hFVHLRxgRKcpvTYorLQ1slzxqiX4J6DPSG8Jf LlrNCqj7y6luIMNzAvlFSgfotHhME2m5tmtvuS8g1Xp5jGR9F80vDzosDSGiMTS9o2ah Ndig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HUW76tWih7CvBsBued7I7ZRmF+OD8mJw5CbJYRINQw8=; b=nWry0L6gTsARag6FGenco9MFNaOPHI0kTPWrw1nl5xEPXfgBxHf2BG7KARqZUFKCYA 7qSD+geEgnNG9pg6Yb5prjUNcxZ75tGu37vti4b0DATmkOaI1oq1Dn4s0V1HeUEzY7KP 8fthAZDVnHm2VRp6Rvgkh6QhQTzF4skWnN8PjDEncJgOSEyaktmCD6gUKiW2km4ovuu2 Rjw5NachXXHcUDOyK2xw9g9CME4rtEjxGbMZLCMGS4L/Wgr/d+55dAQ5R/kTmg3p8PsG Wz5Bb0gFYWq/kikEb4OympP/MSYsRb+Hftn5avuoqLFr2pI/eMOtAE4C5exJyryW4HIj KuLQ== X-Gm-Message-State: APjAAAX/QNK7sI5WBVjk7jCpwj0G61iZjQqBOyH/WJT5f5U6GoXzeyak lc3J5EUILMNBOaB256Dk33PpUbDEgz6WTLV5ZAyFq0r/ X-Google-Smtp-Source: APXvYqyGqmBDsBZkq3Gl0cjTwf5nKLCWzG2I08emRYSP0Bz6L1/neG+X85eGTkLZBuszbVzSgAl0c4OvbqSUacoZMg8= X-Received: by 2002:a25:48c:: with SMTP id 134mr5409095ybe.472.1553899234110; Fri, 29 Mar 2019 15:40:34 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 29 Mar 2019 18:40:22 -0400 Message-ID: To: "ipp@pwg.org" , Ira McDonald , "Kennedy, Smith (Wireless Architect)" Subject: [IPP] WG Last Call: IPP Authentication Methods v1.0 (ends 10 April 2019) X-BeenThere: ipp@pwg.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Ira McDonald via ipp Reply-To: Ira McDonald Content-Type: multipart/mixed; boundary="===============6927648277820204913==" Errors-To: ipp-bounces@pwg.org Sender: "ipp" --===============6927648277820204913== Content-Type: multipart/alternative; boundary="000000000000ddb07f0585435b1c" --000000000000ddb07f0585435b1c Content-Type: text/plain; charset="UTF-8" Hi, This message begins the second IPP WG Last Call of the IPP Authentication Methods v1.0 available at: https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328.pdf https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190328-rev.pdf Please respond with any feedback or comments by doing a "reply all" to this message. This last call will end on 10 April 2019 at 10pm PT. This best practice was reviewed yesterday by the IPP WG, based on the PWG Last Call Review Comments (LCRC), and all reported technical and editorial issues have been resolved. Note: Smith emphasizes that two areas that should have particular focus in this IPP WG Last Call are: (a) the text in section 4 on page 15 (lines 196-217 in the clean version (above); and (b) the UML Sequence Diagrams, to see if they better illustrate the steps that concern authorization and authentication, and how they represent the steps needed to allow the Authorization Service to evaluate whether the IPP operation request can be authorized or not. Cheers, - Ira (IPP WG Co-Chair) 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/highnorthinc mailto: blueroofmusic@gmail.com PO Box 221 Grand Marais, MI 49839 906-494-2434 --000000000000ddb07f0585435b1c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
    Hi,

    This message begins the = second IPP WG Last Call of the IPP
    Authentication Methods v1.0 av= ailable at:


    Please respond with any feedback or comments by doing a "reply all&quo= t; to
    this message.

    This last call will end on 10 April 2019 at 10pm PT.

    This best practice was reviewed yesterday by the IPP WG, based on the
    PWG Last Call Review Comments (LCRC), and all reported technical and
    editorial issues have been resolved= .

    =
    Note:=C2= =A0 Smith emphasizes that two areas that should have particular focus
    <= /span>
    in this IP= P WG Last Call are:

    (a) the text in section 4 on page 15 (lines 196-217 in the clean = version
    (a= bove); and

    (b) the UML Sequence Diagrams, to see if they better illustrate=20 the steps
    that concern authorization and authentication, and how they=20 represent the
    steps needed to allow the Authorization Service to=20 evaluate whether the
    IPP operation request can be authorized or not.

    Cheers,
    - I= ra (IPP WG Co-Chair)

    Ira McDonald (Mus= ician / 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 Pri= nter Working Group
    Co-Chair - IEEE-ISTO PWG Internet Printing Protocol W= G
    IETF Designated Expert - IPP & Printer MIB
    Blue Roof Music / Hi= gh North Inc
    http://sites.google.com/site/b= lueroofmusic
    http://sites.google.com/sit= e/highnorthinc
    mailto: blueroofmusic@gmail.com
    PO Box 221=C2=A0 Grand Marai= s, MI 49839=C2=A0 906-494-2434

    <= div style=3D"display:inline">
    --000000000000ddb07f0585435b1c-- --===============6927648277820204913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp --===============6927648277820204913==--