Re: [Autoconf] DHCP and AUTOCONF (was: Call for comments to a new AUTOCONF charter proposal.)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Tue, 06 July 2010 15:31 UTC

Return-Path: <alexandru.petrescu@gmail.com>
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 C071F3A69A0 for <autoconf@core3.amsl.com>; Tue, 6 Jul 2010 08:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.073
X-Spam-Level:
X-Spam-Status: No, score=0.073 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_50=0.001, HELO_EQ_FR=0.35]
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 l68gxp5d9Bn7 for <autoconf@core3.amsl.com>; Tue, 6 Jul 2010 08:30:58 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.1]) by core3.amsl.com (Postfix) with ESMTP id 8B2613A6A2B for <autoconf@ietf.org>; Tue, 6 Jul 2010 08:30:58 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.0) with ESMTP id o66FUxYZ016646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <autoconf@ietf.org>; Tue, 6 Jul 2010 17:30:59 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id o66FUx71012317 for <autoconf@ietf.org>; Tue, 6 Jul 2010 17:30:59 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id o66FUwMB031119 for <autoconf@ietf.org>; Tue, 6 Jul 2010 17:30:59 +0200
Message-ID: <4C334C32.4080106@gmail.com>
Date: Tue, 06 Jul 2010 17:30:58 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: autoconf@ietf.org
References: <BFD8FF22-FD36-436E-9985-7BFA2E234081@gmail.com> <201006290803.34192.henning.rogge@fkie.fraunhofer.de> <ABE739C5ADAC9A41ACCC72DF366B719D0333F14C@GLKMS2100.GREENLNK.NET> <4C2A723E.3020806@piuha.net> <4C2B801B.1070004@earthlink.net> <ABE739C5ADAC9A41ACCC72DF366B719D0333FC2D@GLKMS2100.GREENLNK.NET> <AANLkTilopimg_lJkGSEFnZ5A9Fv8EzH-eI1zGnANs0n-@mail.gmail.com> <4C2E16A3.1080007@earthlink.net> <AANLkTilk7qGwYVY43WhW_bm_LCgBSw7WsM-sj6dcizSo@mail.gmail.com>
In-Reply-To: <AANLkTilk7qGwYVY43WhW_bm_LCgBSw7WsM-sj6dcizSo@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Autoconf] DHCP and AUTOCONF (was: 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, 06 Jul 2010 15:31:02 -0000

Hi Emmanuel,

Le 03/07/2010 12:17, Emmanuel Baccelli a écrit :
> Hi Charlie,
>
> I agree with you about trying to avoid the dichotomy
> centralized/decentralized.

I agree to try to avoid the dichotomy centralized-decentralized because
DHCP has already many features exhibiting decentralization:

-DHCPv6 dst address is multicast: several servers can be in that group.
-several DHCP Servers running on the the same address with VRRP.
-Several Relays per a DHCP Server.
-DHCP Reconfigure message to let a Server suggest a Client another
  Server.
-RA tell the Node there's a better DHCP Server available.
-there are surely more.

> If some people want to work on a DHCP-dependent solution, let them
> try. If some other people want to work in parallel on a
> DHCP-independent solution, why not let them do it too?

I don't know, it's too simply put.  I'd evaluate the work quantity
needed for each, and prefer reuse.

Alex

>
> In my mind, these two solutions could be pretty complementary.
>
> Emmanuel
>
>
>
> On Fri, Jul 2, 2010 at 6:41 PM, Charles E. Perkins
> <charles.perkins@earthlink.net
> <mailto:charles.perkins@earthlink.net>> wrote:
>
> Hello Emmanuel and all,
>
> Thanks for supporting the consideration of decentralized approach.
> I'm pretty sure we could get at least one good working solution in
> time a lot faster than it took to agree that not everything is an
> Ethernet.
>
> However, it's important to avoid making a sharp dichotomy between
> "centralized" and "decentralized" approaches.  My big concern was
> that somehow the DHCP model was going to be considered the only
> viable choice because people (outsiders?) consider it to be the only
>  known quantity.  There are other ways to have more centralized or
> less centralized procedures, with or without proxy assistance,
> perhaps hybridized approaches, and with improved availability via
> elections.
>
> Those are just a few of the options, and probably all of them are way
> better than trying to shoehorn DHCP where it does not seem to fit.
> Flushing years of development and wisdom down the toilet just because
> they doesn't spell DHCP seems really wrong to me.
>
> Another point to keep in mind -- DHCP was designed and built from day
> one to be a _managed_ solution for autoconfiguration. It seems quite
> clear to me that most of the interesting development and inspiration
> for ad hoc networks has gone towards enabling networking in
> environments where no such tightly managed administration is
> possible. Thus, in my view, DHCP almost tautologically disqualifies
> itself from consideration without major structural redesign.  How is
> it, then, that DHCP keeps cropping up in the discussion?
>
> Regards, Charlie P.
>
>
>
>
> On 7/1/2010 2:28 AM, Emmanuel Baccelli wrote:
>
>
>
> On Thu, Jul 1, 2010 at 11:02 AM, Dearlove, Christopher (UK)
> <Chris.Dearlove@baesystems.com
> <mailto:Chris.Dearlove@baesystems.com>
> <mailto:Chris.Dearlove@baesystems.com
> <mailto:Chris.Dearlove@baesystems.com>>>
>
> wrote:
>
> Charles Perkins
>> I'd be happy if it were possible for [autoconf] to be allowed to
>> consider the excellent body of work that was seen already years ago
>> -- the same body of work that motivated me and others to create and
>> spend a lot of time over the last years and years.
>
> If Charlie can find a few like-minded people to work on that, why not
> add this as a parallel activity? The rationale of why two cases
> should be straightforward to make, they are almost chalk and cheese
> in e.g. centralised versus non-centralised. This is actually added
> safety to the group producing something, as if one succeeds and the
> other fails, that's still good.
>
>
>
> I also think this parallel approach could be appropriate too.
>
>
> Unfortunately, I can't offer to be one of those people. Although I
> should be able to contribute at the read and comment level, more than
> that is needed. I only didn't make the suggestion earlier as it needs
> people (with all due respect to Charlie, plural) to do the work.
>
>
>
> I'd be happy to help out on the matter. So I guess we have a plural
> + contributors ;)
>
> cheers,
>
> Emmanuel
>
>
>
> _______________________________________________ Autoconf mailing
> list Autoconf@ietf.org <mailto:Autoconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/autoconf
>
>
>
>
>
> _______________________________________________ Autoconf mailing
> list Autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/autoconf