[Autoconf] Summary of re-chartering discussions.

Ryuji Wakikawa <ryuji.wakikawa@gmail.com> Tue, 20 July 2010 06:32 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 360623A68CD for <autoconf@core3.amsl.com>; Mon, 19 Jul 2010 23:32:15 -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 QkXj48R41EeC for <autoconf@core3.amsl.com>; Mon, 19 Jul 2010 23:32:13 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id D31673A694C for <autoconf@ietf.org>; Mon, 19 Jul 2010 23:32:13 -0700 (PDT)
Received: by pvd12 with SMTP id 12so2967982pvd.31 for <autoconf@ietf.org>; Mon, 19 Jul 2010 23:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:date:cc:content-transfer-encoding:message-id:to :x-mailer; bh=SLWXBS8s/fTwoyT9vAL7Dvh5mdt6awRH7C2yX56FLFc=; b=cwuTFt3O7LEdrf3/NFA9Spv2EbDIcxTbtOhcW6R0iD2U5QKdPF7PyFtLDWTeTqt8IS giWg8/TGnqCf1V/vtNCQUG3aAm4TcTTITLYf3GAaI3tizbjZ+i2mZhzonMsg0TCHs7rx 1WTl3y4IUcENIkJDAwrqE++9j9DN3WdDHg3jM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:to:x-mailer; b=jv03zf8aA02kzbVOLp8zV0g7p4R/qbZV49JFfbDCWlRauT/A3DKOTncklmw3AGIH3C rPzGres46gxE0c0ikRy7JE8G8NRvwt9TrlslHayM/d0IsTxBiup+E24BUrrPTXDDAK7H /td2+5d2uo/Gb+w7vTMQTMb2SCPzwoA2QZY3U=
Received: by 10.114.61.8 with SMTP id j8mr8788804waa.119.1279607548369; Mon, 19 Jul 2010 23:32:28 -0700 (PDT)
Received: from [10.0.1.2] (c-98-248-44-75.hsd1.ca.comcast.net [98.248.44.75]) by mx.google.com with ESMTPS id k17sm563358rvf.7.2010.07.19.23.32.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 23:32:27 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1081)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Date: Mon, 19 Jul 2010 23:32:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <88FBF3FE-D9BE-4085-B73D-DCA08BA454CF@gmail.com>
To: "autoconf@ietf.org autoconf@ietf.org" <autoconf@ietf.org>
X-Mailer: Apple Mail (2.1081)
Cc: Thomas Clausen <thomas@thomasclausen.org>
Subject: [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: Tue, 20 Jul 2010 06:32:15 -0000

Hi all,

Thanks for all your comments. We have roughly following opinions. 

- Centralized and/or De-centerized 
- Existing protocols (DHCP and/or ND) vs. new autoconf protocols
- SIngle or Multiple AUTOCONF protocol(s)
- Security issue
- Informational link characteristics document

Chairs will prepare for the detailed summary by the Friday meeting in Maastricht.
We may ask some folks to present their opinion based on the comments we received for the new charter proposal.

Here is my general comment (more like impression) as one of co-chair.
It's important to note that several folks agree on the Jari's proposed milestone. 

>1. Design space survey (Informational)
>2. The simple solution (such as DHCP) (PS)
>3. Limitations of the simple solution (Informational)
>4. Recharter for work on the more general solution

I do agree on the importance of non-centerized approach for MANET and knew
many past works exist for AUTOCONF (I had one proposal, too).  
However, as a co-chair, we see high hurdles to get the new protocol(s) out.

First, we have to define requirements of such new autoconf protocol(s), 
for example:  router's address, Global prefix, centralized-,
non-centerized scenarios, single and/or multiple centralized servers,
security...  
Considering fact that people aim at so many different manet scenarios, 
how can we agree on those requirements?

Second, how can we select (a) past proposed autoconf protocol(s) or
inventing a new protocol..
We don't know yet whether there is "a protocol" supporting all the requirements of 
MANET scenarios. Maybe there is, but we need some investigation.

I am afraid to say that It will require a few more years to define only 
requirements, then protocol standardization for !? years.

Don't you think we need some exercise with the simple solution first
before tackling with these huge issues?  
At the coming AUTOCONF charter, the simplest solution may be defined
as just an experimental RFC. Then, we'll have the document of
"limitations of the simple solution (informational)". 
After having these documents, it's not too late to produce "an
AUTOCONF protocol (PS)".

Let's say if the Jari's proposed milestone takes 1- 1.5 years, we will
have better strategy for "An AUTOCONF protocol (PS)" in those years.
Some of folks may feel waste of time for the Jari's proposed charter,
but i believe this is worth to pay for AUTOCONF activity.

Anyway, let's continue rechartering discussion in Maastricht.

thanks,
ryuji