Re: Query on SNMP Error Fields

"Randy Presuhn" <randy_presuhn@mindspring.com> Fri, 14 May 2010 18:28 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 693363A6BB6 for <ietf@core3.amsl.com>; Fri, 14 May 2010 11:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5yQ9g9ulJCa for <ietf@core3.amsl.com>; Fri, 14 May 2010 11:28:42 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 7C6B93A6BA1 for <ietf@ietf.org>; Fri, 14 May 2010 11:28:42 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=cL8sBdxHgptJ4CTldR/RsjcGGW7gRlFSfj3TofdBuDeshVrypWYNfwlkfd55SUqd; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:x-mimeole:X-ELNK-Trace:X-Originating-IP;
Received: from [99.38.145.190] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1OCzce-0001Sp-Tk for ietf@ietf.org; Fri, 14 May 2010 14:28:33 -0400
Message-ID: <003901caf393$47dba700$6801a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
References: <AANLkTinANdMt2CKIbEgKHPb54gjjQXi87HBHPWPwtfhW@mail.gmail.com>
Subject: Re: Query on SNMP Error Fields
Date: Fri, 14 May 2010 11:28:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a91fc720532780359004a6b914ed1338350ebbe55c5fa6f4350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.38.145.190
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2010 18:28:43 -0000

Hi -

> From: "deepak rajaram" <deepak.rajaram@gmail.com>
> To: <ietf@ietf.org>
> Sent: Friday, May 14, 2010 4:18 AM
> Subject: Query on SNMP Error Fields
...
> While the SNMP RFC(1157/2571/SNMPv3) mentions the behavior of "Error Status"
> and "Error Index" field as "will be set in the response" and the value of
> these fields in all set/get/getnext request is zero, It does not mention if
> it is *mandatory* for these fields to have zero in set/get/getnext. Could
> these fields be modifiable in set/get/getnext.

As the comments in the ASN.1 say, the values of these two fields are
sometimes ignored.  In my opinion it would be legal but unwise to
use non-zero values in those requests. Some over-zealous implementor's
code might actually check for zero, and you'd be in the position of explaining
why your implementation doesn't interoperate with deployed systems.

Be conservative in what you send...

Likewise, if your implementation checks those values in any situation other
than the situations spelled out in the specifications, you could also find
yourself explaining why your implementation doesn't interoperate with
deployed systems.

Be liberal in what you accept....

Randy
Randy