IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Thu, 13 January 2011 21:11 UTC

Return-Path: <julian.reschke@gmx.de>
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 72CCC3A6BD8 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 13:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.027
X-Spam-Level:
X-Spam-Status: No, score=-104.027 tagged_above=-999 required=5 tests=[AWL=-1.428, 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 JG9bYrKg+OPJ for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 13:11:58 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 3323D3A6BC9 for <ietf@ietf.org>; Thu, 13 Jan 2011 13:11:57 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 21:14:18 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp041) with SMTP; 13 Jan 2011 22:14:18 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+/az1FkcS/X+IfuWYJKqZej005ToE8G5H8bZlO3+ GuWqmtlkttAZOu
Message-ID: <4D2F6B19.1030407@gmx.de>
Date: Thu, 13 Jan 2011 22:14:01 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Michelle Cotton <michelle.cotton@icann.org>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <C954A3DF.2B01C%michelle.cotton@icann.org>
In-Reply-To: <C954A3DF.2B01C%michelle.cotton@icann.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "stig@cisco.com" <stig@cisco.com>, Adrian Farrel <adrian.farrel@huawei.com>, '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: Thu, 13 Jan 2011 21:11:59 -0000

On 13.01.2011 21:43, Michelle Cotton wrote:
>
> Many believe it makes it very clear to the users of the registry what is
> available for assignment.  Something we will be rolling out soon (for those
> registries with a finite space) will be small charts showing how much of the
> registry space is unassigned, assigned and reserved (utilizing the
> unassigned entries).
> --Michelle
> ...

Exactly my point -- we should distinguish between the actual registry 
contents (assigned / reserved), and how it's presented.

Best regards, Julian

v2.23.0 | Report a Bug | By Email