Re: [Autoconf] Updated ad hoc addressing model document
Thomas Heide Clausen <thomas@thomasclausen.org> Thu, 04 February 2010 12:43 UTC
Return-Path: <Thomas@ThomasClausen.org>
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 A0C943A683D for <autoconf@core3.amsl.com>; Thu, 4 Feb 2010 04:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 0YMk9S2oFxIe for <autoconf@core3.amsl.com>; Thu, 4 Feb 2010 04:43:37 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id B019628C0D7 for <autoconf@ietf.org>; Thu, 4 Feb 2010 04:43:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 30D1F430350; Thu, 4 Feb 2010 04:44:24 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.0.2.6] (sphinx.lix.polytechnique.fr [129.104.11.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 2330743034D; Thu, 4 Feb 2010 04:44:22 -0800 (PST)
Message-Id: <0CD59086-0DBF-40A6-8EC4-3289E65054A1@thomasclausen.org>
From: Thomas Heide Clausen <thomas@thomasclausen.org>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <008c01caa0fe$0eee3530$2cca9f90$@nl>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 04 Feb 2010 13:43:08 +0100
References: <be8c8d781001260409qd23d4era0eac47eaeb3dba2@mail.gmail.com> <8DCBF4A4-7879-4148-A8FE-9A73219536B9@gmail.com> <008c01caa0fe$0eee3530$2cca9f90$@nl>
X-Mailer: Apple Mail (2.936)
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
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 12:43:38 -0000
Dear Teco, Thanks for your review. See comments below. On Jan 29, 2010, at 17:13 PM, Teco Boot wrote: > Ryuji, Thomas, > > I commented on the document. > I don't see any reflection in the document, nor received questions > for clarification. > > I am quite uncomfortable with a large drawback of the proposed > addressing model, which makes it unacceptable for the deployed MANETs > I am involved in. > My requirement is that L3 communication between nodes, that have L2 > connectivity, must be possible in all conditions, including conditions > with a non-operational MANET protocol. I would wonder if you have a MANET if you are not running a MANET protocol? That said, I am not sure I understand what the drawbacks you identify are. The document takes the "most conservative" approach, i.e. a network in which interfaces are configured in accordance to this, should allow any operation. The document, as I read it, uses "should", which does not prohibit alternatives (with the usual caveat concerning a "should"). I believe that if you have no "MANET protocol", but still want L3 communication between identified interfaces (IP addresses), then you would want a mechanism/protocol assigning these addresses? For the reasons outlined in that document, those addresses should (to allow any operation / any protocol to operate) satisfy the suggested rules in the document. If you do deviate from the "should", the usual caveats for a "should" apply -- and it might be OK for your deployment? Cheers, Thomas > Maybe this drawback is overlooked or underestimated. > > And the text on link locals does not describe how IPv6 works. LLs are > used in MANETs for multiple purposes. We can't without. > > My other comments are textual or on incompleteness. Especially, the > document doesn't describe anything useful for assigning globals. > > Regards, Teco > > >> -----Oorspronkelijk bericht----- >> Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] >> Namens >> Ryuji Wakikawa >> Verzonden: woensdag 27 januari 2010 9:00 >> Aan: Emmanuel Baccelli >> CC: autoconf@ietf.org >> Onderwerp: Re: [Autoconf] Updated ad hoc addressing model document >> >> Hi all, >> >> Emmanuel updated the document according to the WG last call. >> Please confirm the changes specially if you sent comments during >> WGLC. >> >> We will pass this document to Jari for the next stage soon. >> >> thanks, >> ryuji >> >> >> On 2010/01/26, at 4:09, Emmanuel Baccelli wrote: >> >>> Folks, >>> >>> here's an updated version of the ad hoc addressing model document, >> following the comments gathered during working group last call. We >> took >> as much as possible on board, as discussed on the mailing list. >> Please >> review this revision, and let us know if you have further comments. >>> >>> http://www.ietf.org/id/draft-ietf-autoconf-adhoc-addr-model-02.txt >>> >>> Regards, >>> >>> Emmanuel >>> >>> >>> _______________________________________________ >>> Autoconf mailing list >>> Autoconf@ietf.org >>> https://www.ietf.org/mailman/listinfo/autoconf >> >> _______________________________________________ >> Autoconf mailing list >> Autoconf@ietf.org >> https://www.ietf.org/mailman/listinfo/autoconf > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf
- [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