Re: [rrg] Last call for revised ILNP documents

Tony Li <tony.li@tony.li> Sun, 22 January 2012 20:27 UTC

Return-Path: <tony.li@tony.li>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 393F721F851E for <rrg@ietfa.amsl.com>; Sun, 22 Jan 2012 12:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.8
X-Spam-Level:
X-Spam-Status: No, score=-101.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0j-BNbm1NsS for <rrg@ietfa.amsl.com>; Sun, 22 Jan 2012 12:27:43 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by ietfa.amsl.com (Postfix) with ESMTP id 7A24521F851D for <rrg@irtf.org>; Sun, 22 Jan 2012 12:27:43 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta12.westchester.pa.mail.comcast.net with comcast id QkE81i00127AodY5CkTj2R; Sun, 22 Jan 2012 20:27:43 +0000
Received: from sjc-vpn4-173.cisco.com ([128.107.239.233]) by omta19.westchester.pa.mail.comcast.net with comcast id QkTV1i00u52qHCY3fkTY14; Sun, 22 Jan 2012 20:27:41 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Tony Li <tony.li@tony.li>
In-Reply-To: <20120122200304.GA25328@laperouse.bortzmeyer.org>
Date: Sun, 22 Jan 2012 12:27:28 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <F30C8B80-51E2-45EA-B467-F44BC520A23E@tony.li>
References: <3707_1327261632_4F1C67BF_3707_53111_1_3D73ACA7-24DC-46B4-B933-0775F9E01E80@tony.li> <20120122200304.GA25328@laperouse.bortzmeyer.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1084)
Cc: rrg@irtf.org, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [rrg] Last call for revised ILNP documents
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jan 2012 20:27:44 -0000

Stephane,

Thank you very much for your comments.

Tony


On Jan 22, 2012, at 12:03 PM, Stephane Bortzmeyer wrote:

> On Sat, Jan 14, 2012 at 10:18:03AM -0800,
> Tony Li <tony.li@tony.li> wrote 
> a message of 27 lines which said:
> 
>> Given the extent of the changes, it's appropriate that the RG review
>> and comment, with a full two week review cycle and consensus check.
> 
> I've read the documents (except the IPv4-specific ones) and I believe
> they are mostly complete and clearly explain how ILNP works.
> 
> There is just one thing which seems to be absent: I do not find
> clearly stated how are the identifier and locator stored in the IPv6
> packet. From some paragraphs, I guess the locator use the high-order
> 64 bits of the IPv6 address and the identifier the low-order bits but
> I was not able to find it clearly written.
> 
> Another point is more a detail: the documents seem to mandate that
> there is a state in the machine for every ILNP correspondent (the
> ILCC). This is no problem for a HTTP server (there is already the TCP
> state) but more problematic for active authoritative DNS servers:
> today, they are able to sustain a very high activity because they have
> absolutely zero state. May be the ILCC could be made optional for
> stateless servers? (There is no need to receive locator updates for
> the ultra-short transactions of the DNS.)
> 
> Otherwise, there is a typo in the references,
> draft-irtf-rrg-ilnp-noncev6 is written draft-irtf-rrg-ilnp-nonce6 in
> the docs (no 'v').