Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt
"Spencer Dawkins" <spencer@wonderhamster.org> Mon, 31 March 2008 19:06 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 E72E328C527; Mon, 31 Mar 2008 12:06:16 -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 CEAEA28C4CD; Mon, 31 Mar 2008 12:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, STOX_REPLY_TYPE=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 pNtnW077H52M; Mon, 31 Mar 2008 12:06:05 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 4AF0328C500; Mon, 31 Mar 2008 12:04:22 -0700 (PDT)
Received: from s73602 (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JgPIS0v3u-0000dg; Mon, 31 Mar 2008 15:04:04 -0400
Message-ID: <060801c89361$d409ec30$6401a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@wonderhamster.org>
To: bharat_joshi@infosys.com, rainab@cisco.com
Subject: Gen-ART Review of draft-ietf-pim-bsr-mib-04.txt
Date: Mon, 31 Mar 2008 14:02:46 -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: V01U2FsdGVkX19sH2giyI2nh+H0Z3VYfPBbHSpEHWzwGmtjraI dd38QfA/DGNkKSINqylknK+EbhB07w9Vs4+Sc3kBFloPx96Wcg ejWWhO+7DGrZ2f0zbBg8J2BP2jI+q4N2Fpw2bD/eO4=
Cc: Mike McBride <mmcbride@cisco.com>, Stig Venaas <venaas@uninett.no>, General Area Review Team <gen-art@ietf.org>, dward@cisco.com, ietf@ietf.org
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
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). 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). 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. 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 } _______________________________________________ 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