Re: Last Call on draft-ietf-pim-registry-03.txt

Mykyta Yevstifeyev <evnikita2@gmail.com> Sat, 15 January 2011 01:28 UTC

Return-Path: <evnikita2@gmail.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 46EAD3A6CEB for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 17:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level:
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[AWL=-0.625, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, 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 KWHboFotysMv for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 17:28:32 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 39B373A6CE8 for <ietf@ietf.org>; Fri, 14 Jan 2011 17:28:32 -0800 (PST)
Received: by fxm9 with SMTP id 9so3738466fxm.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 17:30:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4m3WoEbnTyAUizz0xhEAY5crIdx7CQS7blCi6428wlc=; b=C6lzkNg5yFPrWiZUFttks6/+ePpco36PCITuq8vmxZ1G2wyJZ1eH8txx0uNmwnyEre hdYLUtFAdp41Ga6uVuHjrXpyBG4opMw6U9Lkv3UuMHYmlQpZZPWi89UvOgtyAOCk6QjT iog3dpQdrlWjqQ3SKxtNd6lsxtdjnCvKPQVwI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=IQcqQZAhkBhDNiJZR/cv+JTJ5xk6Ek6OH5KoeGBKB/Ig4FB2KLykGodJZ8vTn3IFwo A96+hExwnpeM6eEV/oGaY3/CkGK4fDRTs2Sw2JpOzgsB8lLGDPpNAlyluNDRlSN4OyN9 qWzncV5BKC1MGA8xAVJCXspvtlexLwIY1gBPk=
Received: by 10.223.98.197 with SMTP id r5mr1479344fan.68.1295055058479; Fri, 14 Jan 2011 17:30:58 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n7sm713489fam.35.2011.01.14.17.30.56 (version=SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 17:30:57 -0800 (PST)
Message-ID: <4D30F8E4.3020809@gmail.com>
Date: Sat, 15 Jan 2011 03:31:16 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: stig@cisco.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com> <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: The IETF <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-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: Sat, 15 Jan 2011 01:28:33 -0000

Hello all,

Summarizing all LC comments received so far, I'd like to propose the 
author of draft-ietf-pim-registry-03.txt the following changes to his 
document:

1. Abstract

Explain the abbreviations.

2. Introduction

Explain the abbreviations.

3. Add a new section directly after Introduction named '2. Registry 
Description' with the following content:

   2.1. The Name of the Registry

    The name of created registry is 'Protocol Independent Multicast 
(PIM) Message Types'.

2.2. The Format of the Registry

    The 'Protocol Independent Multicast (PIM) Message Types' registry
    consists of 3 values: Packet Type, Description and Reference. They
    are described below:

      Packet Type - an integer; values form 0 to 15 are assigned.

      Description - a brief decryption of packet type.

      Reference - the reference document, that defines the packet type.

2.3. Registration Procedures

    New assignments to 'Protocol Independent Multicast (PIM) Message Types'
    registry SHALL be made following the 'IETF Consensus' policies.
    [RFC5226]

2.4. The Initial Contents of the Registry

    This section contains the initial contents of the 'Protocol 
Independent Multicast (PIM)
  Message Types' registry.

   +---------+-------------------------------------+------------------+
    |  Type  | Description                         | Reference         |
    +--------+-------------------------------------+-------------------+
    |0       | Hello                               |[RFC3973] [RFC4601]|
    |1       | Register                            |[RFC4601]          |
    |2       | Register Stop                       |[RFC4601]          |
    |3       | Join/Prune                          |[RFC3973] [RFC4601]|
    |4       | Bootstrap                           |[RFC4601]          |
    |5       | Assert                              |[RFC3973] [RFC4601]|
    |6       | Graft                               |[RFC3973]          |
    |7       | Graft-Ack                           |[RFC3973]          |
    |8       | Candidate RP Advertisement          |[RFC4601]          |
    |9       | State Refresh                       |[RFC3973]          |
    |10      | DF Election                         |[RFC5015]          |
    |11-14   | Unassigned                          |this document      |
    |15      | Reserved                            |this document      |
    +--------+-------------------------------------+-------------------+

2.5. Sub-Registries

    No sub-registries are currently defined in 'Protocol Independent 
Multicast (PIM)
  Message Types' registry.

4. Security Consideration: renumber

5. IANA Considerations: renumber, modify in the following way:

IANA is asked to create the Protocol Independent Multicast (PIM)
  Message Types' registry following Section 2 of this document.

6. Other sections: renumber.

I suppose the author will accept my proposal that makes the registry 
description more clear.

All the best,
Mykyta Yevstifeyev