Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt
Bharat Joshi <bharat_joshi@infosys.com> Wed, 02 April 2008 00:20 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 63AE33A6C63; Tue, 1 Apr 2008 17:20:34 -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 26D8A3A68C7; Tue, 1 Apr 2008 01:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 6WU5ar-zHtnQ; Tue, 1 Apr 2008 01:38:12 -0700 (PDT)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [61.95.162.82]) by core3.amsl.com (Postfix) with ESMTP id AD6B23A6E6B; Tue, 1 Apr 2008 01:38:11 -0700 (PDT)
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by kecgate06.infosys.com with InterScan Message Security Suite; Tue, 01 Apr 2008 14:09:05 +0530
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 1 Apr 2008 14:08:06 +0530
Received: from [10.10.11.154] (10.66.216.45) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server id 8.1.240.5; Tue, 1 Apr 2008 14:08:06 +0530
Subject: Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
In-Reply-To: <060801c89361$d409ec30$6401a8c0@china.huawei.com>
References: <060801c89361$d409ec30$6401a8c0@china.huawei.com>
Organization: Infosys Technologies Ltd
Date: Tue, 01 Apr 2008 13:54:28 +0530
Message-ID: <1207038268.3298.54.camel@magadha>
MIME-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4)
X-OriginalArrivalTime: 01 Apr 2008 08:38:06.0472 (UTC) FILETIME=[B5093080:01C893D3]
X-Mailman-Approved-At: Tue, 01 Apr 2008 17:20:33 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "rainab@cisco.com" <rainab@cisco.com>, "dward@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 Spencer, Thanks for reviewing this document. I shall add clarification you have asked for in the next revision. Please see my response in line. Thanks, Bharat > I have been selected as the General Area Review Team (Gen-ART) reviewer for > this draft (for background on Gen-ART, please see > http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). > > Please resolve these comments along with any other Last Call comments you > may receive. > > Thanks, > > Spencer > > Document: draft-ietf-pim-bsr-mib-04.txt > Reviewer: Spencer Dawkins > Review Date: 2008-03-31 (LATE) > IETF LC End Date: 2008-03-26 > IESG Telechat date: (if known) > Summary: Ready for publication as a Proposed Standard > > Comments: there are a small number of questions I tagged as "Clarity:" in > the notes below. If this draft is revised, it would be worth looking at > these questions. > > 4. Overview > > This MIB module contains four tables. The tables are: > > 1. The Candidate-RP Table, which contains one row for each multicast > group address prefix for which the local router is to advertise > itself as a Candidate-RP. This table exists on routers that are > configured as Candidate-RP. > > Clarity: I'm reading this as "configured to advertise itself as > Candidate-RP" - right? That seems to be the terminology used in the MIB > descriptions, and is more clear to me (if I understood correctly here). Ok. I agree that adding 'configured to' in the statement makes it more explicit. > Clarity: There are a decent number of multicast abbreviations that aren't > expanded on first use. If the document gets respun after Last Call, it would > be worth making sure these terms are expanded on first use (otherwise the > RFC Editor has to either ask you or guess). > Ok. I shall expand them on their first usage. If require, I will add them in the terminology section. > 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. > This status object can be set to active(1) without > setting any other columnar objects in this entry > > All writable objects in this entry can be modified > when the status of this entry is active(1)." > > ::= { pimBsrCandidateRPEntry 10 } **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt Spencer Dawkins
- Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.t… Spencer Dawkins
- Re: Gen-ART Review of draft-ietf-pim-bsr-mib-04.t… Bharat Joshi
- RE: Gen-ART Review of draft-ietf-pim-bsr-mib-04.t… Bharat Joshi