IETF Logo Mail Archive

Re: [Autoconf] Summary of re-chartering discussions.

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Wed, 21 July 2010 00:22 UTC

Return-Path: <ryuji.wakikawa@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 382B73A697D for <autoconf@core3.amsl.com>; Tue, 20 Jul 2010 17:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 W7qlo92jvK0b for <autoconf@core3.amsl.com>; Tue, 20 Jul 2010 17:22:12 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4B37C3A680B for <autoconf@ietf.org>; Tue, 20 Jul 2010 17:22:12 -0700 (PDT)
Received: by vws13 with SMTP id 13so1244485vws.31 for <autoconf@ietf.org>; Tue, 20 Jul 2010 17:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=7xDLFXhzG447wW7Wr2Z7OKMZIzWhVdZiokYx3LePpZM=; b=bS8zrSyjo6/Umr+UrWJMuFilIM18orApps/c7usjjAgEkOSoN/UFTH6/KXOpeAtPtT Amsp2SiiVPJwTaV9a2oWZOIAIpaLUjoczUZ4LwNy/MGNERrZtVLr8ql74Bn3NlEEKG97 QEUkZePNJjZKjerPi/Gk7gtAXW04B/nM8oIjM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=tjogUWx3Ioa7QM/bS0najwfWFtSQ+eNjBZmFXmLfwqLXDjPsDWNJh2lPe/STlZBDNa vHL55mTSZlmIaPTV7jh4WV4nRaZliGkJF/GrEnWeH0iSurwYCNYNBV57myViL6qor4bN gkw2OlTtnBel4fKU/15bhxSEnlz33zZkfT+34=
Received: by 10.224.11.129 with SMTP id t1mr1053496qat.59.1279671747806; Tue, 20 Jul 2010 17:22:27 -0700 (PDT)
Received: from macbookpro-ryuji.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id m24sm28648157qck.5.2010.07.20.17.22.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 17:22:27 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
In-Reply-To: <4C456182.4090700@piuha.net>
Date: Tue, 20 Jul 2010 17:22:20 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <75DF3A67-95F7-4324-9F5E-385530EF1602@gmail.com>
References: <88FBF3FE-D9BE-4085-B73D-DCA08BA454CF@gmail.com> <4C456182.4090700@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1081)
Cc: "autoconf@ietf.org autoconf@ietf.org" <autoconf@ietf.org>, Thomas Clausen <thomas@thomasclausen.org>
Subject: Re: [Autoconf] Summary of re-chartering discussions.
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, 21 Jul 2010 00:22:13 -0000

Hi Jari,

Thanks for clarification. 

I agree with you to take a look at current solutions first.
I expect that AUTOCONF WG can finish this work very quickly and move to the real AUTOCONF work soon after that.

regards,
ryuji

On 2010/07/20, at 1:42, Jari Arkko wrote:

> Ryuji, all,
> 
> For what it is worth -- and having followed the discussions -- I don't mind the working group picking up the distributed design work immediately in the new charter. However, I still want to see the specification of what current protocols (DHCP) can achieve unchanged. The description of the limitations of that solution is a natural step of developing the distributed solution, along with design space analysis and other steps that people have mentioned.
> 
> Jari
>

v2.23.0 | Report a Bug | By Email