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

Stig Venaas <stig@venaas.com> Wed, 19 January 2011 17:44 UTC

Return-Path: <stig@venaas.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 3DAD628C10D for <rtg-dir@core3.amsl.com>; Wed, 19 Jan 2011 09:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.337
X-Spam-Level:
X-Spam-Status: No, score=-102.337 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 TqOgRT2qLUEa for <rtg-dir@core3.amsl.com>; Wed, 19 Jan 2011 09:43:59 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id 2364E28C0EA for <rtg-dir@ietf.org>; Wed, 19 Jan 2011 09:43:59 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:983b:1c82:efb4:44ad] (unknown [IPv6:2001:420:4:ea0c:983b:1c82:efb4:44ad]) by ufisa.uninett.no (Postfix) with ESMTPSA id E59697FDA; Wed, 19 Jan 2011 18:46:36 +0100 (CET)
Message-ID: <4D37237A.3070703@venaas.com>
Date: Wed, 19 Jan 2011 09:46:34 -0800
From: Stig Venaas <stig@venaas.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> <4D35D59A.9090306@cisco.com> <04eb01cbb73a$f7476ab0$e5d64010$@huawei.com> <AANLkTimO6qrM+OpnpkmYSeS3RWrg-EKS_KZMssvnNkJP@mail.gmail.com>
In-Reply-To: <AANLkTimO6qrM+OpnpkmYSeS3RWrg-EKS_KZMssvnNkJP@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rtg-dir@ietf.org, draft-ietf-pim-registry.all@tools.ietf.org, Adrian.Farrel@huawei.com, 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: Wed, 19 Jan 2011 17:44:00 -0000

On 1/19/2011 8:02 AM, Jamal Hadi Salim wrote:
> For completion sake: i am assuming the logical conclusion here is for
> Stig to move
> those refs to informative, correct?

I will. Based on the below, I should make all references informational,
even if the document using the code point is standards track.

That makes sense to me :)

Stig
>
> cheers,
> jamal
>
> On Tue, Jan 18, 2011 at 1:10 PM, Adrian Farrel<Adrian.Farrel@huawei.com>  wrote:
>> Hi,
>>
>> A Normative reference is one that must be read to understand the document in
>> hand.
>>
>> A reference used to say "this code point was created in the referenced document"
>> does not require the referenced document to be read. That would make it
>> Informational.
>>
>> A
>>
>>> -----Original Message-----
>>> From: Stig Venaas [mailto:svenaas@cisco.com]
>>> Sent: 18 January 2011 18:02
>>> To: Jamal Hadi Salim
>>> Cc: rtg-ads@tools.ietf.org; rtg-dir@ietf.org; draft-ietf-pim-
>>> registry.all@tools.ietf.org
>>> Subject: Re: RtgDir review: draft-ietf-pim-registry-03
>>>
>>> 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
>>
>>