IETF Logo Mail Archive

Re: [Autoconf] Next steps?

"Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl> Mon, 22 March 2010 22:13 UTC

Return-Path: <Ronald.intVelt@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 840C93A68E5 for <autoconf@core3.amsl.com>; Mon, 22 Mar 2010 15:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.485
X-Spam-Level: **
X-Spam-Status: No, score=2.485 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, 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 SGZqNjDX0-ba for <autoconf@core3.amsl.com>; Mon, 22 Mar 2010 15:13:21 -0700 (PDT)
Received: from mailoutb.tno.nl (mailoutb.tno.nl [134.221.1.17]) by core3.amsl.com (Postfix) with ESMTP id 5FD903A67E1 for <autoconf@ietf.org>; Mon, 22 Mar 2010 15:13:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.51,290,1267398000"; d="scan'208";a="7898277"
Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1b.tno.nl with ESMTP; 22 Mar 2010 23:13:38 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 22 Mar 2010 23:13:38 +0100
Message-ID: <7877C5C0B5CC894AB26113CF06CF886301238DE8@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <4BA7E52C.9050403@piuha.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Autoconf] Next steps?
Thread-Index: AcrKCSZuvvpYBY1aTz6paY8XpdxRKgAA4GeA
References: <1266925311.4036.71.camel@acorde.it.uc3m.es><4B882EB5.4070605@gmail.com> <4BA7E52C.9050403@piuha.net>
From: "Velt, R. (Ronald) in 't" <Ronald.intVelt@tno.nl>
To: <autoconf@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Autoconf] Next steps?
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, 22 Mar 2010 22:13:22 -0000

Jari, all, 

> 
> > In the solution space I am interested in the use of link-local 
> > addresses and of multicast link-scoped addresses.
> >
> > I hope these are not forbidden by the IPv6 addressing architecture 
> > document, which seems to be sent to the IESG now.
> 
> Actually, I *do* want to see the working group's solutions 
> build on top of the address model that we have just 
> completed. And it does discourage the use of link-local 
> addresses. Lets not return to that discussion, I would be 
> more interested in discussing what gaps we have the 
> technology and what possible solutions we might need to do.
> 

Then, to put it bluntly, we have been had. Time and again it has been
mentioned that the document presented *an* addressing architecture
model, not *the* model. I would think that the scope of solutions would
be subject of a re-chartering discussion.

Ronald
This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html

v2.8.7 | Report a Bug | By Email