Re: [Autoconf] Last Call: draft-ietf-autoconf-adhoc-addr-model (IP Addressing Model in Ad Hoc Networks) to Informational RFC

Jari Arkko <jari.arkko@piuha.net> Fri, 26 March 2010 18:40 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: autoconf@core3.amsl.com
Delivered-To: autoconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBA743A6B5F; Fri, 26 Mar 2010 11:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[AWL=1.284, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 YX6a8sjAQ-oN; Fri, 26 Mar 2010 11:40:01 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 03C423A6B45; Fri, 26 Mar 2010 11:40:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1D18A2CEC0; Fri, 26 Mar 2010 20:40:24 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTTWsrAg-6FT; Fri, 26 Mar 2010 20:40:23 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 422F82CD07; Fri, 26 Mar 2010 20:40:22 +0200 (EET)
Message-ID: <4BACFF95.1040204@piuha.net>
Date: Fri, 26 Mar 2010 11:40:21 -0700
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: Erik Nordmark <erik.nordmark@sun.com>
References: <20100219134216.D3CBE28C1CF@core3.amsl.com> <4BAA341F.4030505@sun.com> <4BACF717.6030206@piuha.net> <4BACFB8B.70701@sun.com>
In-Reply-To: <4BACFB8B.70701@sun.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: autoconf@ietf.org, ietf@ietf.org
Subject: Re: [Autoconf] Last Call: draft-ietf-autoconf-adhoc-addr-model (IP Addressing Model in Ad Hoc Networks) to Informational RFC
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ad-Hoc Network Autoconfiguration WG discussion list <autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/autoconf>
List-Post: <mailto:autoconf@ietf.org>
List-Help: <mailto:autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/autoconf>, <mailto:autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2010 18:40:02 -0000

Erik,

> This paragraph talks about the requirements of the routing protocols, 
> not about the need for routers to move around:
>    Routing protocols running on a router may exhibit different
>    requirements for uniqueness of interface addresses; some have no such
>    requirements, others have requirements ranging from local uniqueness
>    only, to uniqueness within, at least, the routing domain (as defined
>    in [RFC1136]).
>
> The only requirement I know if in the *routing protocols* is around 
> router ID uniqueness.
> If you disagree, then can you please explain why there is a need to 
> refer to routing protocols in the above paragraph?

I can see why the text in the document may be confusing. But I think the 
primary reason we require uniqueness is the one that I explained in the 
previous e-mail. I would also like to point out that there are *some* 
routing protocols that *do* require unique IDs -- I'm told that this is 
the case with OLSR, for instance. So as far as I can tell the text is 
factually correct, even though I do agree with you that for most routing 
protocols its not the case.

Jari