RE: Last Call on draft-ietf-pim-registry-03.txt
Adrian Farrel <Adrian.Farrel@huawei.com> Wed, 12 January 2011 13:23 UTC
Return-Path: <Adrian.Farrel@huawei.com>
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 E91823A6B27 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level:
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=-0.957, BAYES_00=-2.599, 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 fWlAJ2YHRPx1 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:23:43 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 8657B28C0E9 for <ietf@ietf.org>; Wed, 12 Jan 2011 05:23:42 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEW008A9VZDR8@usaga01-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 05:26:01 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LEW004JSVZBF0@usaga01-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 05:26:01 -0800 (PST)
Date: Wed, 12 Jan 2011 13:25:59 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: RE: Last Call on draft-ietf-pim-registry-03.txt
In-reply-to: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
To: 'Mykyta Yevstifeyev' <evnikita2@gmail.com>, 'The IETF' <ietf@ietf.org>
Message-id: <01bc01cbb25c$41590700$c40b1500$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-gb
Content-transfer-encoding: 7bit
Thread-index: AQKkr0ca3wjOiQC5JrjJaFD3Dw+ep5IbVd4A
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
Cc: stig@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Wed, 12 Jan 2011 13:23:44 -0000
Hi Mykyta, > I am writing to provide some review on the draft-ietf-pim-registry, > that is currently in Last Call, Many thanks for reviewing. > Furstly, this document does not explain the abreviatures once they has > appeared in the title, abstract and main text. Good catch. It looks like a number of the acronyms we expected to be "well-known" are not. I find: PIM RFC (wow, that is a real surprise) On the other hand, some *are* well-known and don't need to be expanded: IANA IGMP IETF For reference, see http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt > Moreover, the initial contents of the regsitry does not mention that > values that are Unassigned. Yeah, probably worth adding an entry... 11-14 Unassigned > What is more, the document does not have > clear regsitry format description, eg. Message Type - an integer, > values from 0 to 15 are assigned etc. I propose to create the > separate section and name it 'Regsitry Description' and place a number > of sub-section tehre that would describe the regsutry as detailed as > possible. You are right. The description of the Message Type should be included. In particular the range is very important. This should be added to the end of the paragraph in Section 3. > And in this occasion out the follwoing IANA Considerations' > Section: > > 'IANA is asked to create the 'name' regsitry following Section 2 of > this document." I am not sure what your suggestion is here. Section 3 begins with exactly this request (using different words). > So I recommend not to publih this document in the current view, Agreed. Thanks for catching these issues which can be fixed. > stop > the Last Call, if posible, and work on it a bit more. No, I don't think so. The purpose of a last call is not necessarily to have everyone agree that a document is perfect. The purpose is to catch exactly the type of issue you have raised. I do not believe that your input here (which *is* valuable) results in changes to the I-D that make a fundamental difference to the document that would necessitate a further last call. Thanks, Adrian
- Re: Last Call on draft-ietf-pim-registry-03.txt Stig Venaas
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- RE: Last Call on draft-ietf-pim-registry-03.txt Adrian Farrel
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- RE: Last Call on draft-ietf-pim-registry-03.txt Adrian Farrel
- Re: Last Call on draft-ietf-pim-registry-03.txt Donald Eastlake
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Doug Ewell
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Michelle Cotton
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Re: Last Call on draft-ietf-pim-registry-03.txt Lars Eggert
- RE: Last Call on draft-ietf-pim-registry-03.txt Dearlove, Christopher (UK)
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Last Call on draft-ietf-pim-registry-03.txt Julian Reschke
- Use of "unassigned" in IANA registries Paul Hoffman
- Re: Use of "unassigned" in IANA registries Iljitsch van Beijnum
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Paul Wouters
- Re: Use of "unassigned" in IANA registries Martin Rex
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Mykyta Yevstifeyev
- Re: Use of "unassigned" in IANA registries Julian Reschke
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Spencer Dawkins
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Eric Rosen
- Re: Use of "unassigned" in IANA registries Lars Eggert
- Re: Use of "unassigned" in IANA registries Martin Rex
- Re: Use of "unassigned" in IANA registries t.petch
- Re: Use of "unassigned" in IANA registries Phillip Hallam-Baker
- Re: Use of "unassigned" in IANA registries t.petch
- Re: Last Call on draft-ietf-pim-registry-03.txt Stig Venaas
- Re: Last Call on draft-ietf-pim-registry-03.txt Mykyta Yevstifeyev