[IPP] MIB objects as IPP attributes
William Wagner via ipp <ipp@pwg.org> Thu, 12 September 2019 03:08 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 6EB6B12025D for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 11 Sep 2019 20:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=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 mrUrRTG7cZSU for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 11 Sep 2019 20:08:48 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 844471200B7 for <ipp-archive2@ietf.org>; Wed, 11 Sep 2019 20:08:48 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 42FCFC8B2; Thu, 12 Sep 2019 03:08:47 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id A30763D83; Thu, 12 Sep 2019 03:08:44 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id 225C85352; Thu, 12 Sep 2019 03:08:43 +0000 (UTC)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) by mail.pwg.org (Postfix) with ESMTPS id C741926BC for <ipp@pwg.org>; Thu, 12 Sep 2019 03:08:41 +0000 (UTC)
Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id 8FOeic1WWWwBZ8FTMiXLpm; Thu, 12 Sep 2019 03:08:40 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1568257720; bh=3v3cSiMwyjoBQNona1PHXbjV5yk2zkD+Iu4vFwLozU4=; h=Received:Received:MIME-Version:To:From:Subject:Date:Content-Type; b=0OH520L21qnR/4oLSSEa/co6fCsZNHzmMXpSb/7TrphXjTNExqNr0Z5xemsWqfTEe xCn0SBsck7LkB5/jTb0zFc9TM/IKYc0ahVrE7vLetOqOPZj52lxHukn3zfQu+BGvBD uCkU/oV0CS64tVvQXOM5cmegggnd/gUbDu+4c4ULShwo51dd4Eo76iMhbN+cre6KWH N7Zkp0u0x6uQFb6Hfwp8KE3X9iNcWNBj3tHFJkQl0Et9Do+/Vr7C+izonznUrL9wTF TVkoDolm5EzEqJp+uUJpQZqR9tIg7y9kipUETOJ1vbrjwWrpEOG3v+uJcv1fiKbhVE 7aEiG9K/DzAhA==
Received: from [IPv6:::ffff:172.20.103.162] ([50.226.135.163]) by resomta-ch2-06v.sys.comcast.net with ESMTPA id 8FTLiaKPHSITP8FTMiRN7S; Thu, 12 Sep 2019 03:08:40 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedufedrtdeggdeikecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecuogfpohfkffculddutddmnecujfgurhepggfvhffuffgkrfgtsegrtddtredttdejnecuhfhrohhmpeghihhllhhirghmucghrghgnhgvrhcuoeifrghmfigrghhnvghrsegtohhmtggrshhtrdhnvghtqeenucfkphephedtrddvvdeirddufeehrdduieefnecurfgrrhgrmhephhgvlhhopeglkffrvheimeemmehffhhffhemudejvddrvddtrddutdefrdduiedvngdpihhnvghtpeehtddrvddviedrudefhedrudeifedpmhgrihhlfhhrohhmpeifrghmfigrghhnvghrsegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihhpphesphifghdrohhrghenucevlhhushhtvghrufhiiigvpedt
X-Xfinity-VMeta: sc=10;st=legit
MIME-Version: 1.0
To: PWG IPP Workgroup <ipp@pwg.org>
Date: Wed, 11 Sep 2019 23:08:40 -0400
Importance: normal
X-Priority: 3
Message-Id: <20190912030843.225C85352@mail.pwg.org>
Subject: [IPP] MIB objects as IPP attributes
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: William Wagner via ipp <ipp@pwg.org>
Reply-To: William Wagner <wamwagner@comcast.net>
Content-Type: multipart/mixed; boundary="===============7279941913982955485=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
This is probably just me being very rusty, but several of the new MIB originated attributes in the System spec have we wondering how they would be used, particularly when querying attributes that are part of a MIB table. For example, a query of log id would result in an integer response, which may refer to one of the 10 power log entries retained. Will a query of an element in a power log entry (e.g., power-state-message) refer to the log entry identified in the log id response ? How does one query elements in other power log entries? Sorry if I am being thick. Bill Wagner
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] MIB objects as IPP attributes William Wagner via ipp
- Re: [IPP] MIB objects as IPP attributes Michael Sweet via ipp