RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSupported' is sema ntically wrong
"Sharon Chisholm" <schishol@nortelnetworks.com> Thu, 12 February 2004 21:02 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15401 for <entmib-archive@lists.ietf.org>; Thu, 12 Feb 2004 16:02:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNyE-0005Il-7V; Thu, 12 Feb 2004 16:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ArNxf-0005Hv-In for entmib@optimus.ietf.org; Thu, 12 Feb 2004 16:01:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15332 for <entmib@ietf.org>; Thu, 12 Feb 2004 16:01:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ArNxc-0003ip-00 for entmib@ietf.org; Thu, 12 Feb 2004 16:01:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArNwe-0003bc-00 for entmib@ietf.org; Thu, 12 Feb 2004 16:00:24 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1ArNvj-0003Ny-00 for entmib@ietf.org; Thu, 12 Feb 2004 15:59:27 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1CKww728991 for <entmib@ietf.org>; Thu, 12 Feb 2004 15:58:58 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <1FNH79F9>; Thu, 12 Feb 2004 15:58:58 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A2A67BA@zcard0ka.ca.nortel.com>
From: Sharon Chisholm <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSupported' is sema ntically wrong
Date: Thu, 12 Feb 2004 15:58:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Hi Well, if we are to pick from the three, I think "unavailable" aligns best with resolving this issue. Sharon -----Original Message----- From: David T. Perkins [mailto:dperkins@dsperkins.com] Sent: Thursday, February 12, 2004 3:51 PM To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org Subject: Re: [Entmib] RE: [psg.com #307] AutoReply: 'notSupported' is semantically wrong HI, For me, the term "notReportable" is worse than "notSupported". The terms "notSupported", "unknown" and "unavailable" are used in MIB modules indicate an appropriate value cannot be obtained by the access or instrumentation code. Mods: section 3.1, pp 3 section 3.4 TC AdminState TC OperState TC UsageState TC AlarmStatus TC StandbyStatus Object entStateAdmin Object entStateOper Object entStateUsage Object entStateAlarm Object entStateStandby At 01:53 PM 2/11/2004 -0500, Sharon Chisholm wrote: >Hi > >That last bit should read > >""A value >of 'notReportable' means that this resource is unable to report [this] >state." > >Sharon > >-----Original Message----- >From: Chisholm, Sharon [CAR:0S00:EXCH] >Sent: Wednesday, February 11, 2004 1:51 PM >To: 'entmib@ietf.org' >Subject: FW: [psg.com #307] AutoReply: 'notSupported' is semantically wrong > > >The following is the proposed resolution to entstate-307. The issue >will be considered closed pending the proposed edit being done. > >Replace the enumeration 'notSupported' with 'notReportable' in each of >the TCs and any references within the text. > >For each of the (TC, object definition) pairs, move the following sort >of text from the object definition to the textual convention: > >"A value >of 'notApplicable' means that this resource is unable to report [this] >state." > >Sharon > >-----Original Message----- >From: entity-state [mailto:rt+entity-state@rt.psg.com] >Sent: Tuesday, January 13, 2004 2:50 AM >To: Chisholm, Sharon [CAR:0S00:EXCH] >Subject: [psg.com #307] AutoReply: 'notSupported' is semantically wrong > ><clip> > >----------------------------------------------------------------------- >-- >Keith McCloghrie [kzm@cisco.com] > >" >> 'notSupported' is semantically wrong, because a compliant >implementation >> obviously supports the MIB, but it can return 'notSupported' for >> every object in the MIB. Presumably, the intended semantics is that >> the agent would return the right value if only it knew the right >value; >> i.e., 'unknown' is the desired semantics. Also, why is each >definition >> of 'notSupported' defined in an object's DESCRIPTION, not in the >TC's >> DESCRIPTION ?" /david t. perkins _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib
- RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSu… Sharon Chisholm
- RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSu… Sharon Chisholm
- RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSu… David T. Perkins
- RE: [Entmib] RE: [psg.com #307] AutoReply: 'notSu… Sharon Chisholm