Re: [Autoconf] Updated ad hoc addressing model document
Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Tue, 09 February 2010 17:56 UTC
Return-Path: <cjbc@it.uc3m.es>
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 0750228C169 for <autoconf@core3.amsl.com>;
Tue, 9 Feb 2010 09:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.35
X-Spam-Level:
X-Spam-Status: No, score=-5.35 tagged_above=-999 required=5 tests=[AWL=0.349,
BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3,
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 UU-yd2fXGxG2 for
<autoconf@core3.amsl.com>; Tue, 9 Feb 2010 09:56:12 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by
core3.amsl.com (Postfix) with ESMTP id CDE433A7230 for <autoconf@ietf.org>;
Tue, 9 Feb 2010 09:56:11 -0800 (PST)
X-uc3m-safe: yes
Received: from [163.117.139.72] (acorde.it.uc3m.es [163.117.139.72]) (using
TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
requested) by smtp01.uc3m.es (Postfix) with ESMTP id A2E55BAB1AC;
Tue, 9 Feb 2010 18:57:16 +0100 (CET)
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
In-Reply-To: <4B71A08F.9060904@earthlink.net>
References: <be8c8d781001260409qd23d4era0eac47eaeb3dba2@mail.gmail.com>
<8DCBF4A4-7879-4148-A8FE-9A73219536B9@gmail.com>
<008c01caa0fe$0eee3530$2cca9f90$@nl> <4B631699.7040504@earthlink.net>
<009001caa10d$8729a2a0$957ce7e0$@nl> <4B6347DA.1040004@earthlink.net>
<00a601caa19e$7122c810$53685830$@nl>
<C8A0698C-B04F-475B-B750-842C8786778F@thomasclausen.org>
<005501caa5a5$9b0fc7d0$d12f5770$@nl>
<6CD290EC-969F-4421-B5C9-0558A4A5A865@thomasclausen.org>
<003501caa63a$7b15ca20$71415e60$@nl>
<93EB52DC-5869-450B-B1BE-8870D010BEF5@thomasclausen.org>
<007401caa681$61506090$23f121b0$@nl>
<1265735848.4511.97.camel@acorde.it.uc3m.es> <4B71A08F.9060904@earthlink.net>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature"; boundary="=-EW3SbbQvzp+99PQUIPcf"
Organization: Universidad Carlos III de Madrid
Date: Tue, 09 Feb 2010 18:57:23 +0100
Message-ID: <1265738243.4511.105.camel@acorde.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.2
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17162.002
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Updated ad hoc addressing model document
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: cjbc@it.uc3m.es
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: Tue, 09 Feb 2010 17:56:13 -0000
Hello Charlie, On Tue, 2010-02-09 at 09:51 -0800, Charles E. Perkins wrote: > Hello Carlos, > > Questions/comments inline: > > > On 2/9/2010 9:17 AM, Carlos Jesús Bernardos Cano wrote: > > >> Agreed that standard "not that clever" behavior of the IP stack is > >> putting prefixes, configured on interfaces, in the routing table? > > What "not that clever" agent is putting them there? > > >> Agreed that putting other prefixes is 'something clever'? If an prefix::iid/lprefix on-link address is configured in one interface, then a route to that prefix prefix:://lprefix is configured and I can communicate with other addresses of the same prefix on the same L2 link. If the address is off-link, something else is needed to communicate. A good example of the above are link-locals. With current document, we always need something else to communicate. This is not something I'm necessarily against, I just said that I agree that something else is needed with current addressing model. Carlos > > "other prefixes" == ??? > > >> Agreed that with the proposed addressing model, under conditions that > >> the 'something clever' is not functioning, L3 communication fails for > >> links between two nodes that have L2 communication? > > > > I agree with this. > > But the document says: > > => If L2 communication is enabled between a pair of interfaces, IP > => packet exchange is enabled regardless of the IP subnet configuration > => on each of these interfaces. > > Thus, Teco's assertion is wrong. > > It seems to me that each of the three parts quoted above > are either highly questionable, mysterious, or wrong. > > What's to agree with? > > Regards, > Charlie P. -- Carlos Jesús Bernardos Cano http://www.netcoms.net GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67
- [Autoconf] Updated ad hoc addressing model docume… Emmanuel Baccelli
- Re: [Autoconf] Updated ad hoc addressing model do… Zach Shelby
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Ryuji Wakikawa
- Re: [Autoconf] Updated ad hoc addressing model do… Ryuji Wakikawa
- Re: [Autoconf] Updated ad hoc addressing model do… Ulrich Herberg
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Templin, Fred L
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Zach Shelby
- Re: [Autoconf] Updated ad hoc addressing model do… Alexandru Petrescu
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Thomas Heide Clausen
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Carlos Jesús Bernardos Cano
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Carlos Jesús Bernardos Cano
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Teco Boot
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins
- Re: [Autoconf] Updated ad hoc addressing model do… Charles E. Perkins