Re: [RTG-DIR] RtgDir review: draft-ietf-pim-registry-03

Stig Venaas <svenaas@cisco.com> Tue, 18 January 2011 17:59 UTC

Return-Path: <svenaas@cisco.com>
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5DDF3A6FE2 for <rtg-dir@core3.amsl.com>; Tue, 18 Jan 2011 09:59:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 demkkV-PkoPc for <rtg-dir@core3.amsl.com>; Tue, 18 Jan 2011 09:59:25 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id E62F03A6F6C for <rtg-dir@ietf.org>; Tue, 18 Jan 2011 09:59:25 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACpkNU2rR7Ht/2dsb2JhbACkVHOoOpoFhVAEhG+GL4Mk
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 18 Jan 2011 18:02:03 +0000
Received: from [10.33.12.88] ([10.33.12.88]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0II23tc000163; Tue, 18 Jan 2011 18:02:03 GMT
Message-ID: <4D35D59A.9090306@cisco.com>
Date: Tue, 18 Jan 2011 10:02:02 -0800
From: Stig Venaas <svenaas@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Jamal Hadi Salim <hadi@mojatatu.com>
References: <AANLkTi=PaZc+OgTfWXZQh7Hw-6WHk90QBzEEtG46ZQe8@mail.gmail.com>
In-Reply-To: <AANLkTi=PaZc+OgTfWXZQh7Hw-6WHk90QBzEEtG46ZQe8@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 18 Jan 2011 10:09:21 -0800
Cc: rtg-dir@ietf.org, draft-ietf-pim-registry.all@tools.ietf.org, rtg-ads@tools.ietf.org
Subject: Re: [RTG-DIR] RtgDir review: draft-ietf-pim-registry-03
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 18:02:17 -0000

On 1/17/2011 5:57 AM, Jamal Hadi Salim wrote:
> Hello,
>
> I have been selected as the Routing Directorate reviewer for this draft.
> The Routing Directorate seeks to review all routing or routing-related
> drafts as they pass through IETF last call and IESG review. The purpose
> of the review is to provide assistance to the Routing ADs. For more
> information about the Routing Directorate, please see
> http://www.ietf.org/iesg/directorate/routing.html

Thanks, I agree with your comments. Just one question.

[...]
> Nits:
>
> There is an interesting nit in that you have RFC 3973 as a normative
> reference (which sounds deserving in the context of this document)
> but that RFC is an experimental RFC.

I'm not sure whether it is important, but I am wondering what is the
right solution here. Is it OK to have a normative reference, or should
it be an informative reference?

I'm sure it must be common that registries are created and need to
reference e.g. experimental RFCs. In some cases the registry reference
is not even an RFC. Perhaps it then makes more sense to list them as
informative references?

Stig

>
> cheers,
> jamal