Re: [Autoconf] Autoconf addressing model

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 05 March 2009 16:48 UTC

Return-Path: <alexandru.petrescu@gmail.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 8981428C210 for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 08:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.186
X-Spam-Level:
X-Spam-Status: No, score=-2.186 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 jYn9fVa2qZjW for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 08:48:19 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id 6F66C3A6A79 for <autoconf@ietf.org>; Thu, 5 Mar 2009 08:48:19 -0800 (PST)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-1.2) with ESMTP id n25Gl10A008352; Thu, 5 Mar 2009 17:47:01 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by nephilia.intra.cea.fr (8.13.8/8.13.8) with ESMTP id n25GmlYD010481; Thu, 5 Mar 2009 17:48:47 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id n25GmlGT022513; Thu, 5 Mar 2009 17:48:47 +0100
Message-ID: <49B0026F.5070905@gmail.com>
Date: Thu, 05 Mar 2009 17:48:47 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <499F0BA7.90501@piuha.net> <49AD5184.6080300@gmail.com> <000101c99c3c$3121a870$9364f950$@nl><49AD9760.3080909@gmail.com> <49AD98D4.3@earthlink.net><49AD9EA8.6040803@gmail.com> <49ADA17B.9040600@earthlink.net><49ADAF7C.1050509@gmail.com> <49ADB9FB.6050600@earthlink.net> <49AE3A3A.5000305@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5D783@xmb-rtp-208.amer.cisco.com> <49AE9827.5090309@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5D803@xmb-rtp-208.amer.cisco.com> <49AEBA6D.7030903@gmail.com> <7FB7EE0A621BA44B8B69E5F0A09DC76407B5DB1F@xmb-rtp-208.amer.cisco.com> <49AF97FA.70200! 07@gmail.com> <002201c99d76$017d4b20$0477e160$@nl> <49AFAA15.9! 060905@gmail.com> <003a01c99d8e$f47ba2f0$dd72e8d0$@nl> <49AFD85E.50403! 01@gmail.com> <004a01c99d9b$542e1e10$fc8a5a30$@nl> <49AFDE93.60! 904@gmail.com> <004b01c99da1$dc4ab9b0$94e02d10$@nl> <49AFEB3C! .8010703@gmail.com> <004c01c99da7$ee315700$ca940500$@nl> <49AFF! 2B7.2060600@gmail.com> <005701c99db0$adbc6620$09353260$@nl>
In-Reply-To: <005701c99db0$adbc6620$09353260$@nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Autoconf addressing model
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, 05 Mar 2009 16:48:20 -0000

Teco Boot a écrit :
[...]
> OK, this is a basic setup.
> Just depict what you have:
> +--------+
> |        | fe80::1/64    (the LL address-prefix)
> | Router +--------------
> |        | 2001:db8::1/64 (the address prefix configured on
> +--------+                 this interface)

I agree with this starting point.

I'm wondering what others in the WG think about this starting point in 
depicting a practical addressing architecture for AUTOCONF.  I would 
really appreciate to have some oppinions about this.

> Maybe use ll::1 as short presentation for fe80::1/64
> And p::1/64 for the address prefix, and define the prefix p:: somewhere in
> the diagram.

No, not for the moment.

> |If you don't want then I can depict it.
> |
> |> |For me, whereas the 2001:db8::/64 information is enough to add in
> |> |radvd.conf, or to add with ifconfig,  the problem is that I can't
> |just
> |> |say "ifconfig eth0 add fe80::1" and I must say "ifconfig eth0 add
> |> |fe80::1/10", otherwise error.
> |>
> |> Try ifconfig eth0 inet6 add fe80::1/64
> |> Or  ip -6 addr add fe80::1/64 dev eth0
> |>
> |> I think you tried to add an IPv4 address, with failing DNS lookup.
> |
> |No, it wasn't DNS lookup error, but I avoid saying ifconfig fe80::1/64
> |because the prefix fe80::/64 is not an on-link prefix (even though
> |fe80::1 is an address on that link).  If I write ifconfig 2001:db8::1/64
> |then the 2001:db8::/64 becomes an on-link prefix.
> 
> I would say it is mandatory for interfaces to have a link-local address (RFC
> 4291). And I think they are on-link by definition.
> Or are you interested in a less common or a rare setup?

Right, I agree with you.  Have a link-local address on every physical 
interface.  I'm not yet interested in less common setup.

Alex