[IPP] Clarification of Best Practice Conformance Terminolgy - MUST is allowed
Ira McDonald via ipp <ipp@pwg.org> Mon, 18 May 2020 20:25 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 95DF93A0D6E for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 May 2020 13:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.798
X-Spam-Level:
X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKu7zBN-rzBK for <ietfarch-ipp-archive@ietfa.amsl.com>; Mon, 18 May 2020 13:25:38 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 467BF3A0BEB for <ipp-archive2@ietf.org>; Mon, 18 May 2020 13:25:38 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id DFC733A80; Mon, 18 May 2020 20:25:37 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id E14C63A8E; Mon, 18 May 2020 20:25:34 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 3FB0D5058; Mon, 18 May 2020 20:25:34 +0000 (UTC)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) by mail.pwg.org (Postfix) with ESMTPS id 929967FC for <ipp@pwg.org>; Mon, 18 May 2020 20:25:33 +0000 (UTC)
Received: by mail-vs1-xe2b.google.com with SMTP id 1so6424380vsl.9 for <ipp@pwg.org>; Mon, 18 May 2020 13:25: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=I6dFiFGlLdlBgBkZPYR1gD2UWOe1dF6THXFLpS/iwrg=; b=oMuM0sd9/1lxHSCgg1x4bzFbTRAcqGSvjlpwHkQBlj+NruPEmfIOyvflGiaP3ibpv5 tuFyMO7pKngIcOv3gloXyrQxPlrKRjWHAhqIO6aNa9AjdXVnr+I49dK46HVdc79vJ9Dt XYQPooH+0gIJw0GV/bWAD2YBvFqtBOaGCRsvScKA2/EJnFzLVU5mVxG/lK+Pl45loHXf vosS4K0FGheAJFKtrfOuPAwGwuR5BqTQScVCMcnZXn/QyYY1f7GVVQ0u5wmjpd5jja/q Sr4SQ5daFq+loTmfK0yr1zqXhVYRFnl5FPkVP9lcnzj67EIPiyvz//SJWCShzB/GjyC5 f32A==
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=I6dFiFGlLdlBgBkZPYR1gD2UWOe1dF6THXFLpS/iwrg=; b=giutre5muKYos/3L3IbTMaklA3wJID0dZxMg+vxfYLcdGBr+8XSuS0XSokH9dgwLCy wvhsSZnUpQNHjiRuiPlTD+LB4SLz9bMIp5nXnz+v2JTzJ4QuieocieTd2H+7bGprj4YC tv74UhgNNzHAkUL4+Ynep+Up8R4WWSpR8oFgDwRxzKKQcbwHw6CkUIVSfg8pwFh3YLKU +ezEA0smklE45EdAQblsgeUBevxIfNF02bkJlMRqyrbE33hSelsDtWVV0Rpy8d0FQGf0 Y39oNoDSQbh9KS3fPVnWQqB0M6IjxOXdzWj7TXfDflC98kHDRtNaU8LiL7vuFJAhOUGk 8KOA==
X-Gm-Message-State: AOAM531vl348wh63+7Yyun377TL+dlXShgUPdY+aIbo47hSXR5hV2dPJ D+U1RojDHlNG418Bj+0zENxM3ug6pSkYCq/4Mplovg==
X-Google-Smtp-Source: ABdhPJxwOqngTPgfviIIqmPawoJSWu5JzVZzjBPwXeOJL4GTuI4AZx2t7o0xMwj281eSzMl1lu23HFbLQbFq19xLVbg=
X-Received: by 2002:a67:d981:: with SMTP id u1mr672848vsj.240.1589833532399; Mon, 18 May 2020 13:25:32 -0700 (PDT)
MIME-Version: 1.0
Date: Mon, 18 May 2020 16:25:20 -0400
Message-ID: <CAN40gStXHT=vbwLhQVT2rkP2F7_dfQjFjFpaRQH0j8g0h9eUQg@mail.gmail.com>
To: "ipp@pwg.org" <ipp@pwg.org>, Ira McDonald <blueroofmusic@gmail.com>
Subject: [IPP] Clarification of Best Practice Conformance Terminolgy - MUST is allowed
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="===============3754293806495142542=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
Hi, Mentioned during our Joint PWG/OP Summit Virtual F2F two weeks ago. Discussed further on our PWG Steering Committee call today. Background: Both PWG Requirements documents and PWG Best Practices documents have always had to go through the same PWG Process steps as PWG standards-track documents (i.e., WG Last Call, PWG Last Call, and PWG Formal Vote). Obviously, PWG Requirements documents need to be able to use MUST for specific requirements (that constrain future or updated standards-track specs). And this has been our existing PWG practice. Consensus: PWG Best Practice documents can also use MUST (sparsely) for key requirements (that constrain implementation, deployment, and/or configuration of standards-track protocols). Cheers, - Ira (PWG Secretary) 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 (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] Clarification of Best Practice Conformance … Ira McDonald via ipp