RE: [midcom] RE: Last Call: 'Definitions of Managed Objects forMiddlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)

Juergen Quittek <quittek@netlab.nec.de> Sun, 08 October 2006 22:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWhOX-0002P3-Us; Sun, 08 Oct 2006 18:45:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWhOX-0002Oj-1Y for midcom@ietf.org; Sun, 08 Oct 2006 18:45:17 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GWhOR-0004JB-KZ for midcom@ietf.org; Sun, 08 Oct 2006 18:45:17 -0400
Received: from [192.168.1.128] (unknown [91.89.53.224]) by kyoto.netlab.nec.de (Postfix) with ESMTP id D32EB1BAC4D; Mon, 9 Oct 2006 00:45:09 +0200 (CEST)
Date: Mon, 09 Oct 2006 00:45:05 +0200
From: Juergen Quittek <quittek@netlab.nec.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: RE: [midcom] RE: Last Call: 'Definitions of Managed Objects forMiddlebox Communication' to Proposed Standard (draft-ietf-midcom-mib)
Message-ID: <53BF315D9FC50C3DBCBD2182@[192.168.1.128]>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F0B511B1C@is0004avexu1.global.avaya.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F0B511B1C@is0004avexu1.global.avaya.com>
X-Mailer: Mulberry/3.1.6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: midcom@ietf.org, Martin Stiemerling <stiemerling@netlab.nec.de>, Pyda Srisuresh <srisuresh@yahoo.com>
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: midcom.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Errors-To: midcom-bounces@ietf.org

Hi Dan,

I added the note that you suggested in the text below
to all occurrences of error code 'inconsistentValue'.

Thanks,

    Juergen


--On 26.09.2006 12:54 Uhr +0300 Romascanu, Dan (Dan) wrote:

> Thanks, I have just one comment on one of the points, see below.
>
> Dan
>
>
>
>
>
>> -----Original Message-----
>> From: Juergen Quittek [mailto:quittek@netlab.nec.de]
>
>
>> >> 4. Several DESCRIPTION clauses (e.g. midcomRuleAdminStatus,
>> >> midcomRuleStorageType) include SNMP-specific error messages when
>> >> describing the behavior of the object. This is OK, as the
>> MIDCOM-MIB
>> >> is designed to be used with SNMP as MIDCOM protocol, yet I would
>> >> include a note on this subject because this is not
>> customary within
>> >> other MIB documents which are written with a
>> protocol-independent orientation.
>> >>
>> > [suresh] I will leave to Juergen or Martin to comment on this.
>>
>> We assume that you refer to error code 'inconsistentValue'
>> that we mention in several DESCRIPTION clauses.
>>
>> We think this is still customary in recent MIB modules from
>> where we got the idea to use this error code.  See, for
>> example, RFCs 4001, 4087, 4131, 4149, 4268, 4368, 4444, and 4546.
>
> You are correct, however discussions between MIB Doctors recently led us
> to the conclusion that it would be useful to make clear in texts of new
> documents that errors like 'inconsistentValue' are specific to the usage
> of the SMIv2 MIB module with SNMP, while if the MIB is used by other
> protocols there probably would be similar errors under different names.
>
> As I said, no special problem here, as SNMP is the MIDCOM protocol, but
> a note like the following cannot harm.
>
> 'Note that this error code is SNMP specific. If the MIB module is used
> with other protocols than SNMP, errors with similar semantics specific
> to those protocols should be returned.'
>
>



_______________________________________________
midcom mailing list
midcom@ietf.org
https://www1.ietf.org/mailman/listinfo/midcom