Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt

"Spencer Dawkins" <spencer@wonderhamster.org> Tue, 01 April 2008 23:18 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D5D23A6EEE; Tue, 1 Apr 2008 16:18:31 -0700 (PDT)
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 1D00B3A68BD; Tue, 1 Apr 2008 16:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.059
X-Spam-Level:
X-Spam-Status: No, score=0.059 tagged_above=-999 required=5 tests=[AWL=-0.546, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, STOX_REPLY_TYPE=0.001, TVD_FINGER_02=2.134]
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 xVV6XPGiMyEq; Tue, 1 Apr 2008 16:18:29 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 8D8863A6E25; Tue, 1 Apr 2008 16:16:28 -0700 (PDT)
Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JgpiF3ZZ2-0000Sa; Tue, 01 Apr 2008 19:16:27 -0400
Message-ID: <08ad01c8944e$45e0a7d0$6401a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: Bharat Joshi <bharat_joshi@infosys.com>
References: <060801c89361$d409ec30$6401a8c0@china.huawei.com> <1207038268.3298.54.camel@magadha>
Subject: Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt
Date: Tue, 01 Apr 2008 09:02:33 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Provags-ID: V01U2FsdGVkX183wVhzor4XuPWks5MjKbDmsShPNNgNZJday9G HR545hhg/Oo/kD7/Mzhbr7B7pSOdLt6vabspJst1DncZHtVqwJ 3sVMxrQtMU7clgBCaAOAyPZYNHA3XotjlKzQdYf3oo=
Cc: ietf@ietf.org, General Area Review Team <gen-art@ietf.org>, rainab@cisco.com, dward@cisco.com, Stig Venaas <venaas@uninett.no>, Mike McBride <mmcbride@cisco.com>
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi, Bharat,

What follows is my suggestion only, so please filter it appropriately...

>> 5.  Definitions
>>
>>    pimBsrCandidateRPStatus OBJECT-TYPE
>>        SYNTAX     RowStatus
>>        MAX-ACCESS read-create
>>        STATUS     current
>>        DESCRIPTION
>>                "The status of this row, by which new entries may be
>>                created, or old entries deleted from this table.
>>
>> Clarity: I'm sorry, but I don't get "status by which new entries may be
>> created/old entries deleted" - is that actually how it works? I would 
>> have
>> thought the status was the side effect of creation/deletion, not how
>> creation/deletion actually happens. s/by which new/used to identify when
>> new/? but I'm guessing here.
>>
>
> The 'RowStatus' object is used for two purposes. One is to provide the
> current status of a Row and another is to create/delete a specific Row.
> So this statement looks ok.

Your explanation is very helpful. It would be great if your explanation 
ended up in the description itself. Perhaps something like

        DESCRIPTION
                "The status of this Row, used for two purposes - to create 
or
                 delete a specific Row from this table, and to provide the
                 status of a Row in this table"

If you're using a technique that's commonly used in MIB-land, fine, but 
manipulating an object by changing its "status" violates the principle of 
least astonishment, at least for this reader :-)

Either way - thanks for the quick response. Gen-ART reviewers love quick 
responses because we can remember why we wrote what we wrote...

Spencer 


_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf