Re: [Autoconf] new charter

Paul Lambert <paul@marvell.com> Mon, 23 February 2009 07:59 UTC

Return-Path: <paul@marvell.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 32CC13A67A1 for <autoconf@core3.amsl.com>; Sun, 22 Feb 2009 23:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 nOhhvYkziS9U for <autoconf@core3.amsl.com>; Sun, 22 Feb 2009 23:59:28 -0800 (PST)
Received: from maili.marvell.com (host2.marvell.com [65.219.4.2]) by core3.amsl.com (Postfix) with ESMTP id 2D1833A672F for <autoconf@ietf.org>; Sun, 22 Feb 2009 23:59:28 -0800 (PST)
Received: from MSI-MTA.marvell.com (msi-mta.marvell.com [10.68.76.91]) by maili.marvell.com (Postfix) with ESMTP id C62625F22A; Sun, 22 Feb 2009 23:59:45 -0800 (PST)
Received: from sc-owa01.marvell.com ([10.93.76.21]) by MSI-MTA.marvell.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 22 Feb 2009 23:59:45 -0800
Received: from SC-vEXCH2.marvell.com ([10.93.76.134]) by sc-owa01.marvell.com ([10.93.76.21]) with mapi; Sun, 22 Feb 2009 23:59:45 -0800
From: Paul Lambert <paul@marvell.com>
To: "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, Jari Arkko <jari.arkko@piuha.net>
Date: Sun, 22 Feb 2009 23:59:38 -0800
Thread-Topic: [Autoconf] new charter
Thread-Index: AcmTnvM+ZAFJhF1ZRtKaQTlKsJTmRAB67RdQ
Message-ID: <7BAC95F5A7E67643AAFB2C31BEE662D01489D12D@SC-VEXCH2.marvell.com>
References: <499F0BA7.90501@piuha.net> <1235161786.4633.73.camel@localhost> <499F1924.8090801@piuha.net> <1235163918.4633.78.camel@localhost>
In-Reply-To: <1235163918.4633.78.camel@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Feb 2009 07:59:45.0597 (UTC) FILETIME=[B11986D0:01C9958C]
Cc: "autoconf@ietf.org" <autoconf@ietf.org>
Subject: Re: [Autoconf] new charter
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: Mon, 23 Feb 2009 07:59:29 -0000

I'm glad to see IPv4 be in scope in the new charter.  I've been lurking on the list for awhile hoping to find existing or emerging IETF solutions for ad hoc address assignment.  Specifically there is a real need for IP address assignment solutions for 802.11 ad hoc networks.  There are unique issues when security is included based on WPA2 or WPA2 using WPS (Wi-Fi Protected Setup).

Security for WPA2 is connection oriented and requires the pair-wise establishment of the keying relationships.  This means that WPA2 secured multicast can not be used for peer discovery or address assignment in an 802.11 ad hoc network.  New mechanisms are required for rapid peer identification and IP address assignment.

I'd be very interested in collaborating on solutions for the specific issues of 802.11 ad hoc networks.

Regards,

Paul



> -----Original Message-----
> From: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] On
> Behalf Of Carlos Jesús Bernardos Cano
> Sent: Friday, February 20, 2009 1:05 PM
> To: Jari Arkko
> Cc: autoconf@ietf.org
> Subject: Re: [Autoconf] new charter
>
> OK, understood. If we finally go to new solutions space (if existing IP
> autoconfiguration mechanisms cannot be used), then this would have to be
> discussed, I guess, because there IPv4 vs IPv6 might have an impact.
>
> thanks for the clariffication,
>
> Carlos
>
> El vie, 20-02-2009 a las 22:57 +0200, Jari Arkko escribió:
> > I intentionally made the new charter not say anything about that. My
> > belief is that the type of architecture document that we are looking at
> > can easily talk about both IPv4 and IPv6.
> >
> > Jari
> >
> > Carlos Jesús Bernardos Cano wrote:
> > > Hi Jari,
> > >
> > >     One quick comment (I haven't read the proposed text in detail
> yet): are
> > > we considering IPv6 only? IPv6 and IPv4? IPv4 only? previous charter
> > > focused only on IPv6 solutions...
> > >
> > >     Kind Regards,
> > >
> > >     Carlos
> > >
> > > El vie, 20-02-2009 a las 21:59 +0200, Jari Arkko escribió:
> > >
> > >> In the light of the new direction for the working group,
> > >> we are planning to update the charter as follows. Comments
> > >> appreciated.
> > >>
> > >> Jari & the chairs
> > >>
> > >> ----
> > >>
> > >> Ad-Hoc Network Autoconfiguration (autoconf)
> > >> -------------------------------------------------------------
> > >> Last Modified: 2009-02-18
> > >>
> > >> Cuurent Status: Active Working Group
> > >>
> > >> Additional information is available at tools.ietf.org/wg/autoconf
> > >>
> > >> Chair(s):
> > >> Ryuji Wakikawa [ryuji.wakikawa@gmail.com]
> > >> Thomas Clausen [T.Clausen@computer.org]
> > >>
> > >> Internet Area Director(s):
> > >> Jari Arkko [jari.arkko@piuha.net]
> > >> Mark Townsley [townsley@cisco.com]
> > >>
> > >> Internet Area Advisor:
> > >> Jari Arkko [jari.arkko@piuha.net]
> > >>
> > >> Mailing Lists:
> > >> General Discussion: autoconf@ietf.org
> > >> To Subscribe: https://www.ietf.org/mailman/listinfo/autoconf
> > >> Archive:
> > >> http://www.ietf.org/mail-archive/web/autoconf/current/maillist.html
> > >>
> > >> Description of Working Group:
> > >>
> > >> In order to communicate among themselves, ad hoc nodes (refer to RFC
> > >> 2501) need to configure their network interface(s) with local
> addresses
> > >> that are valid within an ad hoc network. Ad hoc nodes may also need
> to
> > >> configure globally routable addresses, in order to communicate with
> > >> devices on the Internet. From the IP layer perspective, an ad hoc
> > >> network presents itself as a L3 multi-hop network formed over a
> > >> collection of links.
> > >>
> > >> The main purpose of the AUTOCONF WG is to describe the addressing
> model
> > >> for ad hoc networks and how nodes in these networks configure their
> > >> addresses. It is required that such models do not cause problems for
> ad
> > >> hoc-unaware parts of the system, such as standard applications
> running
> > >> on an ad hoc node or regular Internet nodes attached to the ad hoc
> > >> nodes. This group's effort may include the development of new
> protocol
> > >> mechanisms, should the existing IP autoconfiguration mechanisms be
> found
> > >> inadequate. However, the first task of the working group is to
> describe
> > >> one practical addressing model for ad hoc networks.
> > >>
> > >> Once this sole work item is completed, the group can be rechartered
> to
> > >> work on additional issues.
> > >>
> > >> Goals and Milestones:
> > >>
> > >> Apr 2009 Submit initial draft on address configuration in ad hoc
> networks
> > >> Sep 2009 Submit address configuration draft to IESG as Informational
> or
> > >> close WG
> > >>
> > >> _______________________________________________
> > >> Autoconf mailing list
> > >> Autoconf@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/autoconf
> > >>
> >
> --
>  Carlos Jesús Bernardos Cano     http://www.netcoms.net
>  GPG FP: D29B 0A6A 639A A561 93CA  4D55 35DC BA4D D170 4F67
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   WEEDEV 2009: 2nd Workshop on Experimental Evaluation and
>         Deployment Experiences on Vehicular networks
>                   http://www.weedev.org/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++