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

"Holtzer, A.C.G. (Arjen)" <arjen.holtzer@tno.nl> Fri, 02 July 2010 13:21 UTC

Return-Path: <arjen.holtzer@tno.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 7E0783A681A for <autoconf@core3.amsl.com>; Fri, 2 Jul 2010 06:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level:
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 IKirURWnjt84 for <autoconf@core3.amsl.com>; Fri, 2 Jul 2010 06:21:41 -0700 (PDT)
Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by core3.amsl.com (Postfix) with ESMTP id 0DEEB3A67C2 for <autoconf@ietf.org>; Fri, 2 Jul 2010 06:21:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,526,1272837600"; d="scan'208";a="36664491"
Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1a.tno.nl with ESMTP; 02 Jul 2010 15:21:51 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 02 Jul 2010 15:21:51 +0200
Message-ID: <C67EC3A73E6A814B8F3FE826438C5F8C02A00D5E@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D0333FC2D@GLKMS2100.GREENLNK.NET>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] Call for comments to a new AUTOCONF charter proposal.
Thread-Index: AcsYeoMVeeYlzuj3RBWPZfhqutHWLAAgD0NAADsO1tA=
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>
From: "Holtzer, A.C.G. (Arjen)" <arjen.holtzer@tno.nl>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>, "Charles E. Perkins" <charles.perkins@earthlink.net>, Jari Arkko <jari.arkko@piuha.net>, autoconf@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: Fri, 02 Jul 2010 13:21:42 -0000

Hello autoconfers,

I support this "two-case"-approach, Christopher mentions: so
standardizing one centralized and one decentralized solution (or one
stateful and one stateless solution, just like in the current IPv6
standards). I agree that the solution should make use of existing
protocols as much as possible (e.g. DHCP, ND, ...), but my choice would
be not to state in the charter that DHCP must be used in all solutions
coming out of the WG.

draft-bernardos-manet-autoconf-survey-05 shows there are already many
proposals existing, making it a good starting point for going into
solution space. Actually even more than just a starting point since many
of the proposals have already been around for a while. So I support this
doc.

Best regards,
Arjen

> 
> 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.
> 
> 
This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html