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

Mykyta Yevstifeyev <evnikita2@gmail.com> Fri, 14 January 2011 14:02 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 495CF3A6B87 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.282
X-Spam-Level:
X-Spam-Status: No, score=-2.282 tagged_above=-999 required=5 tests=[AWL=-0.643, 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 END86HAX3FdA for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:02:12 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 4BEAF3A6B7A for <ietf@ietf.org>; Fri, 14 Jan 2011 06:02:12 -0800 (PST)
Received: by bwz12 with SMTP id 12so2723854bwz.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 06:04:37 -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=xx29gQzVLZkeQz8MMbC/3rE95Kd2nSqxRWYvH2w3fYQ=; b=vRDHxhqrbnUkHKHe/iH+5AX+2xohs7lZpTxSCL+RPpEdxxzBcpEE5d+puFCtJaAH7/ HeLZFEseS2r/l/vlitJrv+ZiB+sxa2qnNlA+mG1NhXFIE1hfgbL+99p/HYCAYWdDoAtj Su138SZkk5u0QiIFMbQ7s9e/p/x9acP7kS+P4=
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=gD8b+ayPEpxbTq6qG02FlVP/Ca6sgNQe9tjtRSH+h5JXBBoEKA5rEbgB0wbvBL+sFE BwpvBUFde9ufhYtBml49xvyWgRaJIBeGrk0LQzVOvzPtrMbQlgOJLd7DLOULqbmJ1dlc WBO+sHYo0rlLUm1AoeJIRD4Bckkjb5anwLuxU=
Received: by 10.204.126.230 with SMTP id d38mr630458bks.120.1295013876960; Fri, 14 Jan 2011 06:04:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm1318750bkj.13.2011.01.14.06.04.34 (version=SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 06:04:35 -0800 (PST)
Message-ID: <4D305806.6070502@gmail.com>
Date: Fri, 14 Jan 2011 16:04:54 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de> <01da01cbb264$2f1462d0$8d3d2870$@huawei.com> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com> <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell> <4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com> <4D2F2402.401@gmx.de> <4D2F24DC.4070908@gmail.com> <4D2F261A.6040105@gmx.de>
In-Reply-To: <4D2F261A.6040105@gmx.de>
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: Fri, 14 Jan 2011 14:02:13 -0000

13.01.2011 18:19, Julian Reschke wrote:
> On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
>> <...>
>> Documents that create a new namespace (or modify the definition of an
>> existing space) and that expect IANA to play a role in maintaining
>> that space (e.g., serving as a repository for registered values) MUST
>> provide clear instructions on details of the namespace. In
>> particular, instructions *MUST* include:
>> <...>
>> 5) Initial assignments and reservations. Clear instructions should be
>> provided to identify any initial assignments or registrations. In
>> addition, any ranges that are to be reserved for "Private Use",
>> "Reserved", **"Unassigned"**, etc. should be *clearly indicated*.
>> <...>
>
> Yes.
>
> There's still no "MUST" applying to unassigned code points. Note the 
> "In addition" and "should".
There is MUST before the list of the criteria for the documents defining 
the registry.  This MUST applies to everything mentioned in this list.

Mykyta
>
>> ...
>
> Best regards, Julian
>