Re: [Autoconf] Autoconf addressing model

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 05 March 2009 15:41 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 07B1128C187 for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 07:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.185
X-Spam-Level:
X-Spam-Status: No, score=-2.185 tagged_above=-999 required=5 tests=[AWL=0.064, 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 LY0laNVhZhrC for <autoconf@core3.amsl.com>; Thu, 5 Mar 2009 07:41:17 -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 F056B3A6899 for <autoconf@ietf.org>; Thu, 5 Mar 2009 07:41:16 -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 n25Fdxsn024958; Thu, 5 Mar 2009 16:39:59 +0100
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by nephilia.intra.cea.fr (8.13.8/8.13.8) with ESMTP id n25FfiX8020057; Thu, 5 Mar 2009 16:41:44 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id n25FfhQo014731; Thu, 5 Mar 2009 16:41:43 +0100
Message-ID: <49AFF2B7.2060600@gmail.com>
Date: Thu, 05 Mar 2009 16:41:43 +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> <49A944FF.9000102@gmail.com> <003001c99b2c$a3fcf4a0$ebf6dde0$@nl><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>
In-Reply-To: <004c01c99da7$ee315700$ca940500$@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 15:41:18 -0000

Teco Boot a écrit :
> Hi Alex,
> 
> |> This "fe80::1/128" is an invalid address prefix.
> |> Address fe80::1 is OK, Address prefixes fe80::1/64 and 2001:db8::1/64
> |are
> |> also OK.
> |
> |Ah ok!  I'd normally picture what are the parameters I need to set up
> |the network you illustrated on linux.  So would this be ok:?
> |
> |  /------\
> |/        \ fe80::1       (the address)
> || Router |--------------
> |\        / 2001:db8::/64 (the prefix of the subnet on which
> |  \------/                 this interface is attached)
> |
> 
> Now you don't depict the address in subnet 2001:db8::/64.

Right, I didn't, and I should have had.  How would you depict a Router 
with one interface, a global subnet prefix, an address within that 
prefix, and a link-local address?  Without indulging any confusion.

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.

> |> You are free using loopback interfaces or not.
> |> I explain why I have an advantage. This is not crashing protocols, it
> |is
> |> eliminating unneeded terminated sessions.
> |>
> |> I do not accept a comment that I have no advantage. I have also
> |different
> |> scenarios, some have benefits from a loopback interface, some have
> |not. I am
> |> waiting on an answer from you, on your standpoint to be interoperable
> |with
> |> me or not. I hope your routing protocol doesn't crash when receiving a
> |host
> |> prefix. If so, I do not want to be compatible with you.
> |
> |Well my answer is that as of now I don't use any routing protocol, and
> |only put manual prefixes in the routing tables.
> 
> OK for me.
> I hope you can live with different settings, preferred by others.

Well yes but let's first find the most common common settings.

Alex