Re: [IPP] Adding a section 3.5 "Design Requirements" to IPP Authentication Methods
Ira McDonald via ipp <ipp@pwg.org> Tue, 02 July 2019 13:36 UTC
Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E923E1200B7 for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 2 Jul 2019 06:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ff3AfbyCUsJy for <ietfarch-ipp-archive@ietfa.amsl.com>; Tue, 2 Jul 2019 06:36:51 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 30A7C120075 for <ipp-archive2@ietf.org>; Tue, 2 Jul 2019 06:36:51 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 846D0617B; Tue, 2 Jul 2019 13:36:50 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id B63B427B3; Tue, 2 Jul 2019 13:36:44 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 609F73D83; Tue, 2 Jul 2019 13:36:44 +0000 (UTC)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) by mail.pwg.org (Postfix) with ESMTPS id 2D42A27B3 for <ipp@pwg.org>; Tue, 2 Jul 2019 13:36:43 +0000 (UTC)
Received: by mail-yb1-xb34.google.com with SMTP id l22so1306634ybf.4 for <ipp@pwg.org>; Tue, 02 Jul 2019 06:36:43 -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=IqMlGq/w/jRG2MPxBpyJXNo4nU5w9YQR7TraGw8U09s=; b=CAoueZW40W/li8r3Y3hALK0GuKi1Cvzl4D2Kf2DZTMNWBQX96qfEr7zv8SbcSNZnEH 55Jgn5sFhgVpAZXLrS5WG1xJCrEK5D9ygwGuHcnTJrN88oQD0QN6beYf5KzFOYcvxkn+ qCTQybXmdeJvawhgv4a+5nlvieusxH6DyN2uepRAlPYCOBzTCqEnAVUXVVL1evverYt6 1BAGi5E2WAT8tm2xO+B3mTCNdyioWfVsxvYlGuSFhVzoLmQ5KOmS3MICBRBTKNYNjc9u OExmPzqZGN3fJnLQiy34A/UrTetIVylGkQrtFjKHIDJn1XHmvBAILHA0ZX3k10RWXeUS oBEA==
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=IqMlGq/w/jRG2MPxBpyJXNo4nU5w9YQR7TraGw8U09s=; b=HK+ZasS+E+6Vttr70EoBPWf2yy5fXsyCS71wcZfhIensZfHrrgJggTBrv8pfdXUTwW yICRwBewoapgKIhEG5hEud7xJo7aCm0mUMHgVxRQHtk7+tzU2GUytFLxoOsXI2D4LbHY xi4vGaXRiOrW6uy5lt0ji3+bNY1wTU/PncAN+flpHSroZBbVGmWlSB6dffiL1GUn4ZuV 0KCXlxFq0W0kRMWL7kaspmzQ+zO/uz4fOQbuEbnCaa/eE+rWehodGk6kU3pSuvzDNCmO Ms2WChm15K7v+NcMtc8L4fFm70KmVhdVk0j/osv+J+fpnlq61RNooq35UvW6kI0UcaxJ Xnog==
X-Gm-Message-State: APjAAAWPwb0I0+plzA8eyqPGGXWZVs/wBzm18XGbtvUvk/u6ySezLbtW yFqumTquSNgeTmAL5/pro0h/W30fJccsVvRMk0I=
X-Google-Smtp-Source: APXvYqy7w5ExA+uhIEgV6xK1cFpFmOkm6wMOOGZSvJUjqZwfOliCPFP5D9072w8ct1KWCswhfRsFPNgidVZzpAKSMS0=
X-Received: by 2002:a25:6c82:: with SMTP id h124mr19542728ybc.55.1562074602399; Tue, 02 Jul 2019 06:36:42 -0700 (PDT)
MIME-Version: 1.0
References: <19BBBF85-58F5-4426-9829-E634753FD2A3@hp.com> <15407B5F-66C9-4284-817D-E163576B5508@msweet.org> <95698169-A488-4A0A-A1B8-577CFBFDD807@hp.com>
In-Reply-To: <95698169-A488-4A0A-A1B8-577CFBFDD807@hp.com>
Date: Tue, 02 Jul 2019 09:38:06 -0400
Message-ID: <CAN40gSuAf-9nN6=TOX1rwu0jP+YAJKW=rb4Hc+f5Nj2aQwRmfw@mail.gmail.com>
To: "Kennedy, Smith (Wireless & Standards Architect)" <smith.kennedy@hp.com>, Ira McDonald <blueroofmusic@gmail.com>
Cc: PWG IPP Workgroup <ipp@pwg.org>
Subject: Re: [IPP] Adding a section 3.5 "Design Requirements" to 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 <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Ira McDonald via ipp <ipp@pwg.org>
Reply-To: Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/mixed; boundary="===============1767497921791277131=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Hi, Looks fine to me with Mike's suggested edits. 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 Tue, Jul 2, 2019 at 8:21 AM Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp@pwg.org> wrote: > I like it! > > Unless there are any other suggestions, I'm going to run with that, and > post an updated document later this morning. > > Smith > > > > On Jul 1, 2019, at 6:49 PM, Michael Sweet <msweet@msweet.org> wrote: > > Smith, > > Quick feedback: > > - End initial sentence with "are to:" (add "to")? > - Item 1: "currently defined for IPP" is awkward > - Add "and" at the end of item 1. > - Item 2: "Describe implementation considerations for authentication ..." > (identification has already happened, you are describing the items that > were identified during the development of the document) > - Item 2: "protocol technical concerns" should read "technical protocol > concerns" > > That would make it: > > 3.5 Design Requirements > > The design requirements for this IPP Authentication Methods Best Practice > document are to: > > 1. Illustrate how each authentication method integrates into IPP > interaction flows; and > 2. Describe implementation considerations for authentication in general, > including factors that influence user experience and technical protocol > concerns. > > > On Jul 1, 2019, at 3:20 PM, Kennedy, Smith (Wireless & Standards > Architect) via ipp <ipp@pwg.org> wrote: > > Greetings, > > From our LCRC review of IPP Authentication Methods, it was pointed out in > the review that the document was lacking a "Design Requirements" subsection > to section 3. We decided to post a draft here on the reflector, and once > consensus was reached, to add that to the final draft to be used in the PWG > Formal Vote of Approval. > > > 3.5 Design Requirements > > The design requirements for this IPP Authentication Methods Best Practice > document are: > > 1. Illustrate how each authentication method currently defined for IPP > integrates into IPP interaction flows; > 2. Identify and describe points to be considered in implementing Client or > Printer support for authentication in general, including factors that > influence user experience as well as protocol technical concerns. > > > Thoughts? > > Smith > > /** > Smith Kennedy > HP Inc. > */ > > _______________________________________________ > ipp mailing list > ipp@pwg.org > https://www.pwg.org/mailman/listinfo/ipp > <https://protect-us.mimecast.com/s/NaEyCmZ6o6hjkD2Y5HGAJTC?domain=pwg.org> > > > ________________________ > Michael Sweet > > > _______________________________________________ > 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
- [IPP] Adding a section 3.5 "Design Requirements" … Kennedy, Smith (Wireless & Standards Architect) via ipp
- Re: [IPP] Adding a section 3.5 "Design Requiremen… Michael Sweet via ipp
- Re: [IPP] Adding a section 3.5 "Design Requiremen… Kennedy, Smith (Wireless & Standards Architect) via ipp
- Re: [IPP] Adding a section 3.5 "Design Requiremen… Ira McDonald via ipp