Re: [Autoconf] Fwd: WGLC for the AUTOCONF charter

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Mon, 23 August 2010 07:17 UTC

Return-Path: <cjbc@it.uc3m.es>
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 C449D3A67CC for <autoconf@core3.amsl.com>; Mon, 23 Aug 2010 00:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level:
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 TaZ+LSzmu2OW for <autoconf@core3.amsl.com>; Mon, 23 Aug 2010 00:17:46 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 01EA13A6988 for <autoconf@ietf.org>; Mon, 23 Aug 2010 00:17:45 -0700 (PDT)
X-uc3m-safe: yes
Received: from [192.168.4.76] (24.Red-80-36-142.staticIP.rima-tde.net [80.36.142.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 18061843660; Mon, 23 Aug 2010 09:18:14 +0200 (CEST)
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
In-Reply-To: <FDC5D667-0E9F-4AC6-A114-16BB703183BF@thomasclausen.org>
References: <61114C29-AE94-432F-A678-E81DAF050931@gmail.com> <FDC5D667-0E9F-4AC6-A114-16BB703183BF@thomasclausen.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-SeDNXFIK0YGrTPQSaUJV"
Organization: Universidad Carlos III de Madrid
Date: Mon, 23 Aug 2010 09:19:50 +0200
Message-ID: <1282547990.9202.3.camel@acorde.it.uc3m.es>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.2
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17588.003
Cc: autoconf@ietf.org
Subject: Re: [Autoconf] Fwd: WGLC for the AUTOCONF charter
X-BeenThere: autoconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: cjbc@it.uc3m.es
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 Aug 2010 07:17:47 -0000

Hi all,

I generally agree with the proposed charter, with the comment I
mentioned in the meeting:

- Opening the door for service discovery, in addition to address
autoconfiguration, might be a bit too much, especially given our
performance in the past.

Thanks,

Carlos

On Sat, 2010-08-21 at 07:50 +0200, Thomas Heide Clausen wrote:
> Dear All,
> 
> 
> (sorry, traveling and so only catching up on mails now)
> 
> 
> It appears that this email made it to me, but not onto the 'list - for
> which we apologize. 
> 
> 
> The original WGLC deadline was set to August 26, in view of the
> message not making it last time around, the new WGLC deadline is
> August 30, 2010 (Ryuji, I have edited your email to that effect).
> 
> 
> Kindly provide your feedback, even if it is to express agreement with
> the proposed charter.
> 
> 
> Sincerely yours,
> 
> 
> Thomas
> 
> Begin forwarded message:
> 
> > From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
> > 
> > Date: August 17, 2010 19:05:04 GMT+02:00
> > 
> > Subject: WGLC for the AUTOCONF charter
> > 
> > Hi all, 
> > 
> > This is another WGLC for our new charter. 
> > We had good consensus at the meeting, but will confirm the consensus
> > on the list again.
> > 
> > The deadline for this WGLC is going to be Aug 30.
> > 
> > Please give us your opinion.
> > 
> > regards,
> > ryuji
> > 
> > ps. We'll send out the summary of the another WGLC for RFC5889. 
> > 
> > 
> > Ad-Hoc Network Autoconfiguration (autoconf)
> > -------------------------------------------
> > 
> > Current Status: Active
> > 
> > Chairs:
> > Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
> > Thomas Clausen <T.Clausen@computer.org>
> > 
> > Internet Area Directors:
> > Ralph Droms <rdroms.ietf@gmail.com>
> > Jari Arkko <jari.arkko@piuha.net>
> > 
> > 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:
> > 
> > RFC 5889 presents one possible IPv6 addressing model for ad hoc
> > nodes. In this model the ad hoc routers need to configure their
> > network interface(s) with addresses valid in the ad hoc network, and
> > may configure additional prefixes for use by attached nodes.
> > 
> > After completing the work on RFC 5889, the main purpose of the
> > AUTOCONF WG is to standardize how existing IPv6 address
> > configuration
> > tools can be used for address configuration. 
> > 
> > 1. DHCPv6 operation over MANET, including: 
> > 
> >  - A DHCPv6-based mechanism for configuring required interface
> >    addresses for the routers in the ad hoc network. This mechanism
> >    is expected to produce addresses with properties outlined in RFC
> >    5889. This mechanism uses the existing DHCPv6 protocol unchanged,
> >    and assumes a central node that can allocate addresses on a
> >    first-come-first-served basis. Other nodes in the ad hoc network
> >    will relay messages to the central node in order to help a new
> >    node get an address for itself. This mechanism is only suitable
> >    for deployments were a central node can be set up. It should be
> >    noted that many existing deployments employ Internet gateways
> >    that can act as such a central node as well. Future extensions
> >    such as central node election may make this mechanism suitable
> >    for also for stand-alone ad hoc networks.
> > 
> >  - A DHCPv6-based mechanism for delegating a prefix(es) to each
> >    router for use by applications running on the routers themselves,
> >    or for configuration of attached hosts/networks. This mechanism
> >    works in a similar manner to the one above, but allocates
> >    prefixes instead of addresses.
> > 
> > Both mechanisms should be independent from operation of any specific
> > MANET routing protocol, although may exploit information maintained
> > by
> > such a routing protocol, if available.
> > 
> > The working group will adapt and/or reuse existing protocols
> > whenever
> > reasonable and possible. No new duplicate address detection
> > mechanisms
> > are will be specified; it is expected that address uniqueness is
> > guaranteed by the central node alone.
> > 
> > 2. Analysis of Problem Space for distributed address configuration
> > and
> >  service discovery.
> > 
> > 
> > The working group plans to establish design teams for rapidly
> > advancing
> > towards initial submissions for these two work items. 
> > 
> > Goals and Milestones:
> > 
> > -Dec 2010 First working group draft of the "DHCPv6 operation over
> > MANET"
> > -Dec 2010 First working group draft of the "Analysis of Problem
> > Space"
> > -Sep 2011 Submission of the "DHCPv6 operation over MANET" to the
> > IESG for
> > publication as BCP
> > -Sep 2011 Submission of the "Analysis of Problem Space" the IESG for
> > publication as Informational RFC
> > -Sep 2011 Rechartering or Closing 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