Re: [Autoconf] Updated ad hoc addressing model document
"Charles E. Perkins" <charles.perkins@earthlink.net> Thu, 04 February 2010 18:13 UTC
Return-Path: <charles.perkins@earthlink.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 12E1728C0FA for <autoconf@core3.amsl.com>;
Thu, 4 Feb 2010 10:13:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
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 zmKdhOBWSQS5 for
<autoconf@core3.amsl.com>; Thu, 4 Feb 2010 10:13:50 -0800 (PST)
Received: from elasmtp-galgo.atl.sa.earthlink.net
(elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by core3.amsl.com
(Postfix) with ESMTP id F3F7D3A693E for <autoconf@ietf.org>;
Thu, 4 Feb 2010 10:13:49 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=Ojg77E/3HHPH21qplbeqq1VXxHHAZyTolhZPXGCFtf0rtthWbPlujvNdY7UXx48l;
h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [12.204.153.98] (helo=[10.166.254.21]) by
elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim
4.67) (envelope-from <charles.perkins@earthlink.net>) id 1Nd6Dq-0007rl-Ul;
Thu, 04 Feb 2010 13:14:35 -0500
Message-ID: <4B6B0E85.5050101@earthlink.net>
Date: Thu, 04 Feb 2010 10:14:29 -0800
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
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>
In-Reply-To: <005501caa5a5$9b0fc7d0$d12f5770$@nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f521bd244cff9cf4200f298b096c3a7638b350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 12.204.153.98
Cc: autoconf@ietf.org, 'Thomas Heide Clausen' <thomas@thomasclausen.org>
Subject: Re: [Autoconf] Updated ad hoc addressing model document
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, 04 Feb 2010 18:13:51 -0000
Hello Teco, On 2/4/2010 6:22 AM, Teco Boot wrote: > > Up to now, all IP addressing models I am aware of provide 1-hop L3 > communication between nodes that have L2 connectivity. > If I get your point, what you mean is that when two nodes share a link, they can use L3 protocols to communicate. As far as I understand it, the addressing model does not change this. IP supports point-to-point communication between such "adjacent" nodes. How adjacency is discovered is usually considered out of scope. Either subnet prefixes are "assigned" (suddenly, it doesn't look like a Manet anymore) or "discovered" (oops, we're running new protocols) or "assumed". In the latter case, you'd better make your assumptions minimal, or else (protocol-wise) you are moving back into traditional a fixed network model. I know it's nicer there and all. > The proposed addressing model for MANETs breaks this. Now there > is a need for something clever. This clever thing could be > stopped. > I do not agree with this. See above. I also do not agree that we must avoid being clever. However, I agree that simpler is better, all the while adhering to Einstein's famous dictum. > There is no reason not using link-locals for 1-hop traffic. > If you say this is a particular and specific setup, is this a > qualification for IPv6? > If not, what are you referring to? > I read this, and had to smile. Of course there's no reason to avoid link-locals for 1-hop traffic as long as you _know_ it's one hop. In fact, blast away. But for people who are running networks without such comforts, assurance of availability for a L2 communication channel is often necessary or at least highly desirable. Then suddenly your link-local address is potentially (a) invalid (b) unavailable or (c) ambiguous. These are normally considered poor indicators for IP-based communications. And that is the problem needing solution in the general case, which has motivated the current form of the addressing model document. Regards, Charlie P.
- [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