IETF Logo Mail Archive

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

Erik Nordmark <erik.nordmark@sun.com> Thu, 25 March 2010 00:20 UTC

Return-Path: <erik.nordmark@sun.com>
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 7AB653A6C0B for <autoconf@core3.amsl.com>; Wed, 24 Mar 2010 17:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 FRjUb1YVzSIu for <autoconf@core3.amsl.com>; Wed, 24 Mar 2010 17:20:39 -0700 (PDT)
Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by core3.amsl.com (Postfix) with ESMTP id 3ED603A6B39 for <autoconf@ietf.org>; Wed, 24 Mar 2010 17:20:21 -0700 (PDT)
Received: from jurassic.Eng.Sun.COM ([129.146.17.59]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id o2P0KMpc023909 for <autoconf@ietf.org>; Thu, 25 Mar 2010 00:20:34 GMT
Received: from [10.7.251.248] (punchin-nordmark.SFBay.Sun.COM [10.7.251.248]) by jurassic.Eng.Sun.COM (8.14.4+Sun/8.14.4) with ESMTP id o2P0KL4C920466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Mar 2010 17:20:22 -0700 (PDT)
Message-ID: <4BAAAC46.3000905@sun.com>
Date: Wed, 24 Mar 2010 17:20:22 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.8) Gecko/20100302 Lightning/1.0b1 Thunderbird/3.0.2
MIME-Version: 1.0
To: autoconf@ietf.org
References: <20100219134216.D3CBE28C1CF@core3.amsl.com> <4BAA341F.4030505@sun.com> <7849F9F2-EBEA-401B-AF06-C9A345E06ADA@gmail.com> <4BAA942F.5050506@gmail.com>
In-Reply-To: <4BAA942F.5050506@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 25 Mar 2010 00:20:40 -0000

On 03/24/10 03:37 PM, Alexandru Petrescu wrote:

> ... because whereas it _is_ indeed desirable to identify a router with
> an IP address, it is not necessarily the case that that IP address is
> the address of an interface. E.g. OSPF does so with a Router ID being
> an address (an IPv4 address), and different than any IPv6 addresses it
> may have on an interface (be them link-local addresses)


This is an aside, hence I'm not copying the IESG, but I think IS-IS got 
this right by using a MAC address as the router ID. Having factory 
assigned router IDs simply things a fair bit. Hence I don't think it is 
necessarily desirable to identify a router using an IP address.

    Erik

v2.23.0 | Report a Bug | By Email