Re: [Autoconf] WG Review: Recharter of Ad-Hoc Network Autoconfiguration (autoconf)

"Teco Boot" <teco@inf-net.nl> Wed, 04 March 2009 19:19 UTC

Return-Path: <teco@inf-net.nl>
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 74BFC3A68EF; Wed, 4 Mar 2009 11:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[AWL=0.407, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
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 Mwy9IJvkja2L; Wed, 4 Mar 2009 11:19:15 -0800 (PST)
Received: from hpsmtp-eml19.kpnxchange.com (hpsmtp-eml19.KPNXCHANGE.COM [213.75.38.84]) by core3.amsl.com (Postfix) with ESMTP id BDC5428C1C0; Wed, 4 Mar 2009 11:18:25 -0800 (PST)
Received: from cpsmtp-eml101.kpnxchange.com ([213.75.84.101]) by hpsmtp-eml19.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 4 Mar 2009 20:18:52 +0100
Received: from M90Teco ([86.83.9.22]) by cpsmtp-eml101.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 4 Mar 2009 20:18:52 +0100
From: "Teco Boot" <teco@inf-net.nl>
To: "'Alexandru Petrescu'" <alexandru.petrescu@gmail.com>
References: <20090304163257.82E843A6B2E@core3.amsl.com> <49AEBBEA.7020400@gmail.com>
In-Reply-To: <49AEBBEA.7020400@gmail.com>
Date: Wed, 4 Mar 2009 20:18:51 +0100
Message-ID: <000001c99cfe$0d927ca0$28b775e0$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acmc79FWlnGjsPWCS7Spy46jOjk7QgAC8Zyw
Content-Language: nl
X-OriginalArrivalTime: 04 Mar 2009 19:18:52.0184 (UTC) FILETIME=[0DAD0980:01C99CFE]
Cc: autoconf@ietf.org, iesg@ietf.org, T.Clausen@computer.org
Subject: Re: [Autoconf] WG Review: Recharter of Ad-Hoc Network Autoconfiguration (autoconf)
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: Wed, 04 Mar 2009 19:19:16 -0000

Inline.

|-----Oorspronkelijk bericht-----
|Van: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] Namens
|Alexandru Petrescu
|Verzonden: woensdag 4 maart 2009 18:36
|CC: autoconf@ietf.org; iesg@ietf.org; T.Clausen@computer.org
|Onderwerp: Re: [Autoconf] WG Review: Recharter of Ad-Hoc Network
|Autoconfiguration (autoconf)
|
|I would like to suggest: add explicitely that the practical addressing
|model should work at least with manual and static routes.  And that the
|practical addressing model should not be preconditioned by the use of
|OLSR nor DYMO in the ad-hoc network.

I think the addressing model has little to do with the method how to assign
and configure the addresses. This is a next step. I wonder if any model
exclude what you are asking for. Worried for some reason???

I would not suggest working with static routes in a mobile ad hoc network.

I agree on the last one, the model should apply to other MANET Routing
Protocols as well. OSPF-MANET is an important one, not forgetting others,
including multicast.
 
|Also suggest: specifically mention which link-layers are being
|considered for ad-hoc networks.  I personally consider 802.11, 802.15.4,
|wired Ethernet, USB and eventually 802.16.  If anybody else considers
|other link-layers please mention them.

I consider other link layers, but I will not mention them. I do not know all
details or even a complete list. And if I would, it doesn't help. I think it
is sufficient and more useful to describe the MANET link characteristics.

Teco.


|
|Alex
|
|IESG Secretary a écrit :
|> A modified charter has been submitted for the Ad-Hoc Network
|> Autoconfiguration working group in the Internet Area of the IETF.  The
|> IESG has not made any determination as yet.  The modified charter is
|> provided below for informational purposes only.  Please send your
|comments
|> to the IESG mailing list (iesg@ietf.org) by Wednesday, March 11, 2009.
|>
|> Ad-Hoc Network Autoconfiguration (autoconf)
|> -------------------------------------------------------------
|> Last Modified: 2009-02-18
|>
|> Current Status: Active Working Group
|>
|> Additional information is available at tools.ietf.org/wg/autoconf
|>
|> Chair(s):
|> Ryuji Wakikawa [ryuji.wakikawa@gmail.com]
|> Thomas Clausen [T.Clausen@computer.org]
|>
|> Internet Area Director(s):
|> Jari Arkko [jari.arkko@piuha.net]
|> Mark Townsley [townsley@cisco.com]
|>
|> Internet Area Advisor:
|> Jari Arkko [jari.arkko@piuha.net]
|>
|> Mailing Lists:
|> General Discussion: autoconf@ietf.org
|> To Subscribe: https://www.ietf.org/mailman/listinfo/autoconf
|> Archive:
|> http://www.ietf.org/mail-archive/web/autoconf/current/maillist.html
|>
|> Description of Working Group:
|>
|> In order to communicate among themselves, ad hoc nodes (refer to RFC
|> 2501) need to configure their network interface(s) with local
|addresses
|> that are valid within an ad hoc network. Ad hoc nodes may also need to
|> configure globally routable addresses, in order to communicate with
|> devices on the Internet. From the IP layer perspective, an ad hoc
|> network presents itself as a L3 multi-hop network formed over a
|> collection of links.
|>
|> The main purpose of the AUTOCONF WG is to describe the addressing
|model
|> for ad hoc networks and how nodes in these networks configure their
|> addresses. It is required that such models do not cause problems for
|ad
|> hoc-unaware parts of the system, such as standard applications running
|> on an ad hoc node or regular Internet nodes attached to the ad hoc
|> nodes. This group's effort may include the development of new protocol
|> mechanisms, should the existing IP autoconfiguration mechanisms be
|found
|> inadequate. However, the first task of the working group is to
|describe
|> one practical addressing model for ad hoc networks.
|>
|> Once this sole work item is completed, the group can be rechartered to
|> work on additional issues.
|>
|> Goals and Milestones:
|>
|> Apr 2009 Submit initial draft on address configuration in ad hoc
|networks
|> Sep 2009 Submit address configuration draft to IESG as Informational
|or
|> close WG
|>
|> _______________________________________________
|> 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