Re: [Autoconf] Call for comments to a new AUTOCONF charter proposal.

Henning Rogge <henning.rogge@fkie.fraunhofer.de> Tue, 29 June 2010 06:03 UTC

Return-Path: <henning.rogge@fkie.fraunhofer.de>
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 302003A6966 for <autoconf@core3.amsl.com>; Mon, 28 Jun 2010 23:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[AWL=-0.309, BAYES_50=0.001, HELO_EQ_DE=0.35, RCVD_IN_PBL=0.905]
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 nA3UWEgfggbW for <autoconf@core3.amsl.com>; Mon, 28 Jun 2010 23:03:29 -0700 (PDT)
Received: from mailguard.fgan.de (a.mx.fkie.fraunhofer.de [IPv6:2001:638:401:102:1aa9:5ff:fe5f:7f22]) by core3.amsl.com (Postfix) with ESMTP id 9DE683A694C for <autoconf@ietf.org>; Mon, 28 Jun 2010 23:03:28 -0700 (PDT)
Received: from rufsun5.fkie.fgan.de ([128.7.2.5] helo=mailhost.fgan.de) by mailguard.fgan.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1OTTuz-0002cC-Jy; Tue, 29 Jun 2010 08:03:37 +0200
Received: from stream.fkie.fgan.de ([128.7.5.148] helo=stream.localnet) by mailhost.fgan.de with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <henning.rogge@fkie.fraunhofer.de>) id 1OTTuz-0003PG-BN; Tue, 29 Jun 2010 08:03:37 +0200
From: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
To: autoconf@ietf.org
Date: Tue, 29 Jun 2010 08:03:28 +0200
User-Agent: KMail/1.13.3 (Linux/2.6.32-22-generic; KDE/4.4.4; i686; ; )
References: <BFD8FF22-FD36-436E-9985-7BFA2E234081@gmail.com>
In-Reply-To: <BFD8FF22-FD36-436E-9985-7BFA2E234081@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart24575389.ZAUrvoIjuh"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Content-Transfer-Encoding: 7bit
Message-Id: <201006290803.34192.henning.rogge@fkie.fraunhofer.de>
X-Virus-Scanned: yes (ClamAV 0.96.1/11276/Tue Jun 29 03:59:38 2010) by mailguard.fgan.de
X-Scan-Signature: 1e9a6bb74562192ca4a04316780810e4
Subject: Re: [Autoconf] Call for comments to a new AUTOCONF charter proposal.
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: Tue, 29 Jun 2010 06:03:30 -0000

On Tue June 29 2010 06:20:28 Ryuji Wakikawa wrote:
> Description of Working Group:
> 
> RFC 5889 presents one possible IPv6 addressing model for ad hoc nodes. In
> this model the ad hoc routers need to configure their network interface(s)
> with addresses valid in the ad hoc network, and may configure additional
> prefixes for use by attached nodes.
> 
> After completing the work on RFC 5889, the main purpose of the AUTOCONF WG
> is to standardize how existing IPv6 address configuration tools can be
> used for address configuration:
> 
> 1. A DHCPv6-based mechanism for configuring required interface addresses
> for the routers in the ad hoc network. This mechanism is expected to
> produce addresses with properties outlined in RFC 5889. This mechanism
> uses the existing DHCPv6 protocol unchanged, and assumes a central node
> that can allocate addresses on a first-come-first-served basis. Other
> nodes in the ad hoc network will relay messages to the central node in
> order to help a new node get an address for itself. This mechanism is only
> suitable for deployments were a central node can be set up. It should be
> noted that many existing deployments employ Internet gateways that can act
> as such a central node as well. Future extensions such as central node
> election may make this mechanism suitable for also for stand-alone ad hoc
> networks.
I don't think elections are a good way to add redundancy for an address 
configuration system. The dependency of a single node in the whole network to 
configure the addresses will be a bottleneck for larger mesh networks.

> 2. A DHCPv6-based mechanism for delegating a prefix(es) to each router for
> use by applications running on the routers themselves, or for
> configuration of attached hosts/networks. This mechanism works in a
> similar manner to the one above, but allocates prefixes instead of
> addresses.

I don't see a difference between 1 and 2, for IPv6 case 1 is just case 2 with 
a prefix length of 128 (or 64 if we use the IPv6 autoconf postfix).

--------------
Does this proposal mean the autoconf group will not work on a distributed 
address configuration scheme for mesh networks ?

Henning Rogge
-- 
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961,   Fax +49 228 9435 685
mailto:henning.rogge@fkie.fraunhofer.de http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0