From autoconf-bounces@ietf.org Tue Jul 15 09:00:51 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EC3E3A6881; Tue, 15 Jul 2008 09:00:51 -0700 (PDT) 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 7C6FA3A6881 for ; Tue, 15 Jul 2008 09:00:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.499 X-Spam-Level: X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_71=0.6, MIME_8BIT_HEADER=0.3] 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 35Bs-fHLmyAm for ; Tue, 15 Jul 2008 09:00:49 -0700 (PDT) Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 99E1D3A67EC for ; Tue, 15 Jul 2008 09:00:49 -0700 (PDT) Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps id 1KImxm-0003vj-QS for ; Tue, 15 Jul 2008 18:01:16 +0200 Received: from i74goofy.tm.uni-karlsruhe.de ([141.3.64.67]) by irams1.ira.uni-karlsruhe.de with esmtpsa for id 1KImxm-0000WG-MN; Tue, 15 Jul 2008 18:01:14 +0200 Message-ID: <487CC9C8.5000201@tm.uni-karlsruhe.de> Date: Tue, 15 Jul 2008 18:01:12 +0200 From: =?ISO-8859-1?Q?J=E9r=F4me_H=E4rri?= User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: autoconf@ietf.org Subject: [Autoconf] updated ID related to the transmission of position and mobility information X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Dear Autoconf WG members, I recently updated an ID related to the transmission of position and mobility information for MANET protocols. This ID describes an extension to the node metric TLV defined in the MetricTLV document by the MANET WG to specify a configurable structure to exchange position and mobility information for MANET protocols. Although the initial scope of this draft was MANET protocols, a configurable structure for the transmission of position or mobility information might also be of some interest for the Autoconf WG. In preparation of the upcoming IETF meeting,I would appreciate if you could review this document and provide comments on the use and benefit from this drafts for AUTOCONF. You may find the ID at this address: http://tools.ietf.org/id/draft-haerri-manet-position-signaling-01.txt Another ID describing the problem statement behind the proposal of using and transmitting position and mobility information may also be found here: http://tools.ietf.org/id/draft-haerri-manet-position-problem-statement-01.t= xt Best Regards, Jerome H=E4rri _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Jul 15 18:38:36 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E45F3A6B78; Tue, 15 Jul 2008 18:38:35 -0700 (PDT) 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 EAE0C3A6B78 for ; Tue, 15 Jul 2008 18:38:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 LWMzr3HUfNIR for ; Tue, 15 Jul 2008 18:38:29 -0700 (PDT) Received: from smtpsal.upv.es (marfik.cc.upv.es [158.42.249.14]) by core3.amsl.com (Postfix) with ESMTP id 2FB453A6A37 for ; Tue, 15 Jul 2008 18:38:29 -0700 (PDT) Received: from pop.upv.es (deneb.cc.upv.es [158.42.3.51]) by smtpsal.upv.es (8.13.6/8.13.6) with ESMTP id m6G1cu2M016785 for ; Wed, 16 Jul 2008 03:38:56 +0200 Received: from smtp.upv.es (celaeno.cc.upv.es [158.42.249.55]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id m6G1cus12954 for ; Wed, 16 Jul 2008 03:38:56 +0200 (METDST) Received: from localhost (gomeisa.cc.upv.es [158.42.249.25]) by smtp.upv.es (8.13.6/8.13.6) with ESMTP id m6G1ctK7018446 for ; Wed, 16 Jul 2008 03:38:56 +0200 Received: from bas8-ottawa23-1177551064.dsl.bell.ca (bas8-ottawa23-1177551064.dsl.bell.ca [70.48.0.216]) by webmail.upv.es (IMP) with HTTP for ; Wed, 16 Jul 2008 03:38:55 +0200 Message-ID: <1216172335.487d512ff0e42@webmail.upv.es> Date: Wed, 16 Jul 2008 03:38:55 +0200 From: Jaime Lloret Mauri To: autoconf@ietf.org MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) 3.2.8 X-Originating-IP: 70.48.0.216 Subject: [Autoconf] First Call for Papers InfoSys 2009 [ICNS, ICAS, INTENSIVE], Valencia (Spain), April 21-25, 2009 X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Please consider to contribute and encourage your team members and fellow scientists to contribute to the following federated events. Thanks for forwarding the information on this Call for Submissions to those potentially interested to submit. =3D=3D=3D=3D=3D Call for Submissions =3D=3D=3D=3D=3D=3D=3D InfoSys 2009, April 21-25, 2009 - Valencia/Spain see: http://www.iaria.org/conferences2009/InfoSys09.html InfoSys 2009 is a federated event focusing on advances topics concerning the networking, services, autonomic and autonomous systems, and intensive servi= ces and applications. InfoSys 2009 continues the tradition of well-established conferences, ICNS = and ICAS, and adds new trends on intensive services and applications (INTENSIVE= ). Submission deadline: November 1st, 2008 >> ICNS 2009, The Fifth International Conference on Networking and Services http://www.iaria.org/conferences2009/ICNS09.html >> ICAS 2009, The Fifth International Conference on Autonomic and Autonomous Systems http://www.iaria.org/conferences2009/ICAS09.html >> INTENSIVE 2009, The First International Conference on Intensive Applicat= ions and Services http://www.iaria.org/conferences2009/INTENSIVE09.html Submissions must be electronically done using the =93Submit a Paper=94 butt= on on the entry page of each conference. For details on the each conference's topics, see the individual Call for Pa= pers for each conference. Unpublished high quality contributions in terms of Regular papers and Forum posters are welcome. Workshop proposals and Panel proposals on challenging topics are encouraged. Extended versions of selected papers will be published in IARIA on-line Jou= rnals (http://www.iariajournals.org) and in Special issues of different journals mentioned on the entry page of each conference. Submissions will be peer-reviewed, published by IEEE Computer Society Press, posted in IEEE Digital Library, and indexed via all the IEEE indexing agreements. -------------------------------- IARIA Publicity Board -------------------------------- _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Jul 24 05:18:56 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 070CD3A6806; Thu, 24 Jul 2008 05:18:56 -0700 (PDT) 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 4108F3A6806 for ; Thu, 24 Jul 2008 05:18:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.097 X-Spam-Level: ** X-Spam-Status: No, score=2.097 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] 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 Kp7h8Fawdoot for ; Thu, 24 Jul 2008 05:18:54 -0700 (PDT) Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by core3.amsl.com (Postfix) with ESMTP id ECD513A67FA for ; Thu, 24 Jul 2008 05:18:53 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,246,1215381600"; d="scan'208,217";a="7164904" Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1a.tno.nl with ESMTP; 24 Jul 2008 14:19:37 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 24 Jul 2008 14:19:36 +0200 Message-ID: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG status Thread-Index: Acjth4mjlpHT3Ua4TuC9ZcHV5GIeCQ== From: "Velt, R. (Ronald) in 't" To: Subject: [Autoconf] WG status X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0414261056==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --===============0414261056== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8ED87.89D1E3E9" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8ED87.89D1E3E9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Is the Autoconf WG dead or does it just smell that way? The meeting that was scheduled for August 1 seems to have disappeared from the IETF-72 agenda. No reply from the WG chairs to Teco's inquiry on document status. No response from the WG chairs to off-list email... What's going on? Regards, Ronald in 't Velt This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/disclaimer/email.html ------_=_NextPart_001_01C8ED87.89D1E3E9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable WG status

Dear all,

Is the Autoconf WG dead or does it just sm= ell that way? The meeting that was scheduled for August 1 seems to have dis= appeared from the IETF-72 agenda. No reply from the WG chairs to Teco's inq= uiry on document status. No response from the WG chairs to off-list email..= . What's going on?

Regards,
Ronald in 't Velt 

This e-mail and its contents are subject to the DISCLAIMER at http://w=
ww.tno.nl/disclaimer/email.html
------_=_NextPart_001_01C8ED87.89D1E3E9-- --===============0414261056== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============0414261056==-- From autoconf-bounces@ietf.org Thu Jul 24 13:03:06 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7E113A6A6E; Thu, 24 Jul 2008 13:03:06 -0700 (PDT) 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 D43563A6A6E for ; Thu, 24 Jul 2008 13:03:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.095 X-Spam-Level: ** X-Spam-Status: No, score=2.095 tagged_above=-999 required=5 tests=[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 z8Cv6xWRwpeE for ; Thu, 24 Jul 2008 13:03:04 -0700 (PDT) Received: from mailouta.tno.nl (mailouta.tno.nl [134.221.1.16]) by core3.amsl.com (Postfix) with ESMTP id B5EEF3A67F5 for ; Thu, 24 Jul 2008 13:03:03 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,248,1215381600"; d="scan'208";a="7185167" Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1a.tno.nl with ESMTP; 24 Jul 2008 22:02:49 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 24 Jul 2008 22:02:49 +0200 Message-ID: <7877C5C0B5CC894AB26113CF06CF886301238BA5@ms-dt01thalia.tsn.tno.nl> In-Reply-To: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] WG status Thread-Index: Acjth4mjlpHT3Ua4TuC9ZcHV5GIeCQAP569g References: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> From: "Velt, R. (Ronald) in 't" To: Subject: Re: [Autoconf] WG status X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Replying to my own message. Maybe I'm the sole remaining subscriber to the list.... Found something: http://www.ietf.org/mail-archive/web/wgchairs/current/msg06321.html Some words of explanation from someone in the know would be welcome. Ronald ________________________________ From: autoconf-bounces@ietf.org [mailto:autoconf-bounces@ietf.org] On Behalf Of Velt, R. (Ronald) in 't Sent: donderdag 24 juli 2008 14:20 To: autoconf@ietf.org Subject: [Autoconf] WG status Dear all, Is the Autoconf WG dead or does it just smell that way? The meeting that was scheduled for August 1 seems to have disappeared from the IETF-72 agenda. No reply from the WG chairs to Teco's inquiry on document status. No response from the WG chairs to off-list email... What's going on? Regards, Ronald in 't Velt This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Thu Jul 24 13:15:10 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B43A23A6A76; Thu, 24 Jul 2008 13:15:10 -0700 (PDT) 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 EC74E28C0F6 for ; Thu, 24 Jul 2008 13:15:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 3b6FcH4f3-Zr for ; Thu, 24 Jul 2008 13:15:09 -0700 (PDT) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by core3.amsl.com (Postfix) with ESMTP id 1F55B3A6A29 for ; Thu, 24 Jul 2008 13:15:09 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dMZI8gmso7zgiQg5NWd5ivy416jdPUBfKeDkmLiqyJwjxpwkTebLweEMm/f8Jnfv; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [75.26.137.116] (helo=[10.166.255.89]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KM7DQ-0008Nq-RJ; Thu, 24 Jul 2008 16:15:09 -0400 Message-ID: <4888E2CA.4040606@earthlink.net> Date: Thu, 24 Jul 2008 13:15:06 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Velt, R. (Ronald) in 't" References: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> <7877C5C0B5CC894AB26113CF06CF886301238BA5@ms-dt01thalia.tsn.tno.nl> In-Reply-To: <7877C5C0B5CC894AB26113CF06CF886301238BA5@ms-dt01thalia.tsn.tno.nl> X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f525bbec62f083a52c4f08ebf6e0b899e1a350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 75.26.137.116 Cc: autoconf@ietf.org Subject: Re: [Autoconf] WG status X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Hello Ronald, You're not the only person on the list. In fact, I think we have some important things to discuss in the working group. Maybe we should at least have a bar-BOF even if there isn't a formal meeting scheduled. Regards, Charlie P. Velt, R. (Ronald) in 't wrote: > Replying to my own message. Maybe I'm the sole remaining subscriber to > the list.... > > Found something: > http://www.ietf.org/mail-archive/web/wgchairs/current/msg06321.html > > Some words of explanation from someone in the know would be welcome. > > Ronald > > ________________________________ > > From: autoconf-bounces@ietf.org > [mailto:autoconf-bounces@ietf.org] On Behalf Of Velt, R. (Ronald) in 't > Sent: donderdag 24 juli 2008 14:20 > To: autoconf@ietf.org > Subject: [Autoconf] WG status > > > Dear all, > > Is the Autoconf WG dead or does it just smell that way? The > meeting that was scheduled for August 1 seems to have disappeared from > the IETF-72 agenda. No reply from the WG chairs to Teco's inquiry on > document status. No response from the WG chairs to off-list email... > What's going on? > > Regards, > Ronald in 't Velt > > > > > This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf > > > _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri Jul 25 01:58:30 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32D903A6A8A; Fri, 25 Jul 2008 01:58:30 -0700 (PDT) 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 11EFC3A6A8A for ; Fri, 25 Jul 2008 01:58:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.795 X-Spam-Level: X-Spam-Status: No, score=0.795 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, 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 ikj6PMF9wuiO for ; Fri, 25 Jul 2008 01:58:28 -0700 (PDT) Received: from mailoutb.tno.nl (mailoutb.tno.nl [134.221.1.17]) by core3.amsl.com (Postfix) with ESMTP id CBC553A67A8 for ; Fri, 25 Jul 2008 01:58:27 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,252,1215381600"; d="scan'208";a="1680115" Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1b.tno.nl with ESMTP; 25 Jul 2008 10:58:27 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 25 Jul 2008 10:58:27 +0200 Message-ID: <7877C5C0B5CC894AB26113CF06CF886301238BA8@ms-dt01thalia.tsn.tno.nl> In-Reply-To: <4888E2CA.4040606@earthlink.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] WG status Thread-Index: Acjtyfl9hjsbxBKWRs6oTuRUOszM+gAZra6A References: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> <7877C5C0B5CC894AB26113CF06CF886301238BA5@ms-dt01thalia.tsn.tno.nl> <4888E2CA.4040606@earthlink.net> From: "Velt, R. (Ronald) in 't" To: "Charles E. Perkins" Cc: autoconf@ietf.org Subject: Re: [Autoconf] WG status X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Hello Charlie, Thanks very much for your reply! I agree that there are important matters to discuss. Currently I am re-reading the 'link types' discusssion. An Irish bar-BOF sounds like an excellent idea, for more reasons than one. Should we be the only two persons to turn up, then I'm buying :-) Looking forward to seeing you in Dublin, Ronald >-----Original Message----- >From: Charles E. Perkins [mailto:charles.perkins@earthlink.net] >Sent: donderdag 24 juli 2008 22:15 >To: Velt, R. (Ronald) in 't >Cc: autoconf@ietf.org >Subject: Re: [Autoconf] WG status > > >Hello Ronald, > >You're not the only person on the list. In fact, I think we >have some important things to discuss in the working group. >Maybe we should at least have a bar-BOF even if there isn't a >formal meeting scheduled. > >Regards, >Charlie P. > > > >Velt, R. (Ronald) in 't wrote: >> Replying to my own message. Maybe I'm the sole remaining >subscriber to >> the list.... >> >> Found something: >> http://www.ietf.org/mail-archive/web/wgchairs/current/msg06321.html >> >> Some words of explanation from someone in the know would be welcome. >> >> Ronald >> >> ________________________________ >> >> From: autoconf-bounces@ietf.org >> [mailto:autoconf-bounces@ietf.org] On Behalf Of Velt, R. >(Ronald) in 't >> Sent: donderdag 24 juli 2008 14:20 >> To: autoconf@ietf.org >> Subject: [Autoconf] WG status >> >> >> Dear all, >> >> Is the Autoconf WG dead or does it just smell that way? >The meeting >> that was scheduled for August 1 seems to have disappeared from the >> IETF-72 agenda. No reply from the WG chairs to Teco's inquiry on >> document status. No response from the WG chairs to off-list email... >> What's going on? >> >> Regards, >> Ronald in 't Velt >> >> >> >> >> This e-mail and its contents are subject to the DISCLAIMER at >> http://www.tno.nl/disclaimer/email.html >> >> _______________________________________________ >> Autoconf mailing list >> Autoconf@ietf.org >> https://www.ietf.org/mailman/listinfo/autoconf >> >> >> > > This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Fri Jul 25 06:37:47 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D2BC28C1B5; Fri, 25 Jul 2008 06:37:47 -0700 (PDT) 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 C3F8C28C190 for ; Fri, 25 Jul 2008 06:37:45 -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 X1FdZf1xG0WK for ; Fri, 25 Jul 2008 06:37:44 -0700 (PDT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id BD6BA28C1B5 for ; Fri, 25 Jul 2008 06:37:44 -0700 (PDT) Received: from [192.168.0.13] (82.159.30.238.dyn.user.ono.com [82.159.30.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id 412A87E7C0A; Fri, 25 Jul 2008 15:37:45 +0200 (CEST) From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano To: "Charles E. Perkins" In-Reply-To: <4888E2CA.4040606@earthlink.net> References: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno. nl> <7877C5C0B5CC894AB26113CF06CF886301238BA5@ms-dt01thalia.tsn.tno.nl> <4888E2CA.4040606@earthlink.net> Organization: Universidad Carlos III de Madrid Date: Fri, 25 Jul 2008 15:37:33 +0200 Message-Id: <1216993053.4895.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Cc: autoconf@ietf.org Subject: Re: [Autoconf] WG status 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2052926310==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org --===============2052926310== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-14lh3liVLJHaTssThuIp" --=-14lh3liVLJHaTssThuIp Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hi all, I'd definitely join to a bar-BOF like meeting :-D Regards, Carlos El jue, 24-07-2008 a las 13:15 -0700, Charles E. Perkins escribi=F3: > Hello Ronald, >=20 > You're not the only person on the list. In fact, I think we have some > important things to discuss in the working group. Maybe we should > at least have a bar-BOF even if there isn't a formal meeting scheduled. >=20 > Regards, > Charlie P. >=20 >=20 >=20 > Velt, R. (Ronald) in 't wrote: > > Replying to my own message. Maybe I'm the sole remaining subscriber to > > the list.... > > > > Found something: > > http://www.ietf.org/mail-archive/web/wgchairs/current/msg06321.html > > > > Some words of explanation from someone in the know would be welcome. > > > > Ronald=20 > > > > ________________________________ > > > > From: autoconf-bounces@ietf.org > > [mailto:autoconf-bounces@ietf.org] On Behalf Of Velt, R. (Ronald) in 't > > Sent: donderdag 24 juli 2008 14:20 > > To: autoconf@ietf.org > > Subject: [Autoconf] WG status > > =09 > > =09 > > Dear all,=20 > > > > Is the Autoconf WG dead or does it just smell that way? The > > meeting that was scheduled for August 1 seems to have disappeared from > > the IETF-72 agenda. No reply from the WG chairs to Teco's inquiry on > > document status. No response from the WG chairs to off-list email... > > What's going on? > > > > Regards,=20 > > Ronald in 't Velt=20 > > > > =09 > > =09 > > > > This e-mail and its contents are subject to the DISCLAIMER at http://ww= w.tno.nl/disclaimer/email.html > > > > _______________________________________________ > > Autoconf mailing list > > Autoconf@ietf.org > > https://www.ietf.org/mailman/listinfo/autoconf > > > > > > =20 >=20 > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf --=20 Carlos Jes=FAs Bernardos Cano http://www.netcoms.net GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67 --=-14lh3liVLJHaTssThuIp Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkiJ1xcACgkQNdy6TdFwT2eS7QCgqWfbGXVZRF5zYGc3IwYMYVCR wJgAn0apE03mf3PRc4KAYYPT41tD5j1D =KlhM -----END PGP SIGNATURE----- --=-14lh3liVLJHaTssThuIp-- --===============2052926310== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============2052926310==-- From autoconf-bounces@ietf.org Sun Jul 27 05:41:26 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79EEB3A6820; Sun, 27 Jul 2008 05:41:26 -0700 (PDT) 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 822763A6820 for ; Sun, 27 Jul 2008 05:41:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.595 X-Spam-Level: X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 LsnPSlDTjmTi for ; Sun, 27 Jul 2008 05:41:19 -0700 (PDT) Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 0E7BE3A67CF for ; Sun, 27 Jul 2008 05:41:19 -0700 (PDT) Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id E56C719873D; Sun, 27 Jul 2008 15:41:24 +0300 (EEST) Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 84117198661; Sun, 27 Jul 2008 15:41:24 +0300 (EEST) Message-ID: <488C6CF6.4040101@piuha.net> Date: Sun, 27 Jul 2008 13:41:26 +0100 From: Jari Arkko User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: "Velt, R. (Ronald) in 't" References: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> In-Reply-To: <7877C5C0B5CC894AB26113CF06CF886301238BA0@ms-dt01thalia.tsn.tno.nl> X-Virus-Scanned: ClamAV using ClamSMTP Cc: autoconf@ietf.org Subject: Re: [Autoconf] WG status X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org The working group has not made a lot of progress since IETF-71. We are waiting on a new revision for -manetarch. The chairs and I talked about what the program for the meeting should be, and we did not come up with a lot of material. As a result, the chairs decided to cancel the meeting. However, let me also state that I really want the WG to complete the architecture document. Not just for its own sake but also because I believe this document will be useful in getting the IP and ad hoc routing communities on the same page and discussing with the same terms. I believe we are close to completing this document, and we only need the final push. Not a trivial task, but please do not give up now. With this in mind, I have asked the chairs to organize ad hoc meeting(s) to progress this and possibly the other documents. One goal that you could take for the week is to have a new version of -manetarch by the end of the week. Regular WG meetings will continue in IETF-73 or whenever the WG has made enough progress. Jari _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Mon Jul 28 07:54:51 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0036F3A6A1D; Mon, 28 Jul 2008 07:54:51 -0700 (PDT) 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 480E23A6A1D for ; Mon, 28 Jul 2008 07:54:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 k0uaQ+RFblRP for ; Mon, 28 Jul 2008 07:54:43 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by core3.amsl.com (Postfix) with ESMTP id 9413F3A69DE for ; Mon, 28 Jul 2008 07:54:40 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id d23so2152588fga.41 for ; Mon, 28 Jul 2008 07:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=qqzaowIZuAHr7uQ1eXAxV0M9KBNwfCD07qsVMLIjZUM=; b=UIDNsjdbKfk6wIOelK40EZOLNhIQxoHKIBm8aGchlMsUIdBDHqsf6gfMvYt1s4AQEx lkImRDQEhCQD60Ql9nRRozbn4XcpNoCQTZQ82JhBK7He2cVtC9MABqQlM8fBTXXUwzG4 mpMWY24snO8MnDkx7u13F3qzoW52KRbKBqrvY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=RXZWKv1brMGeDcCZEMX6L7AgSASziPxeKkujSXWoWuqt21Wl9RKd/DE/a27XipaYHf i5Wg74aQUiLG3OvGqSDtjyt1TNdZiSGjw7kkSQkfmDgtkz/PuxOuwcNK5GEo8fooNjZp u2oGpL5PnAaNl0k6H8KWZrUX0HgSfqg0GzueY= Received: by 10.86.80.17 with SMTP id d17mr2653436fgb.47.1217256888921; Mon, 28 Jul 2008 07:54:48 -0700 (PDT) Received: by 10.86.58.10 with HTTP; Mon, 28 Jul 2008 07:54:48 -0700 (PDT) Message-ID: Date: Mon, 28 Jul 2008 16:54:48 +0200 From: "Hasnaa Moustafa" To: autoconf@ietf.org In-Reply-To: MIME-Version: 1.0 References: Subject: Re: [Autoconf] Autoconf Digest, Vol 30, Issue 4 X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1732947424==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org --===============1732947424== Content-Type: multipart/alternative; boundary="----=_Part_41911_24165484.1217256888905" ------=_Part_41911_24165484.1217256888905 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I would be so interested to join the bar-BoF. Then waiting for more details. Kind regards, Hassnaa Date: Thu, 24 Jul 2008 13:15:06 -0700 > From: "Charles E. Perkins" > Subject: Re: [Autoconf] WG status > To: "Velt, R. (Ronald) in 't" onald.intVelt@tno.nl > > Cc: autoconf@ietf.org > Message-ID: <4888E2CA.4040606@earthlink.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Hello Ronald, > > You're not the only person on the list. In fact, I think we have some > important things to discuss in the working group. Maybe we should > at least have a bar-BOF even if there isn't a formal meeting scheduled. > > Regards, > Charlie P. > ------=_Part_41911_24165484.1217256888905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
 
I would be so interested to join the bar-BoF. Then waiting for more details. 
 
Kind regards,
Hassnaa

Date: Thu, 24 Jul 2008 13:15:06 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Subject: Re: [Autoconf] WG status
To: "Velt, R. (Ronald) in 't" <R
 

onald.intVelt@tno.nl>
Cc: autoconf@ietf.org
Message-ID: <4888E2CA.4040606@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


Hello Ronald,

You're not the only person on the list.  In fact, I think we have some
important things to discuss in the working group.  Maybe we should
at least have a bar-BOF even if there isn't a formal meeting scheduled.

Regards,
Charlie P.
------=_Part_41911_24165484.1217256888905-- --===============1732947424== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============1732947424==-- From autoconf-bounces@ietf.org Tue Jul 29 09:48:02 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83DEE3A691E; Tue, 29 Jul 2008 09:48:02 -0700 (PDT) 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 CA2BA3A6910 for ; Tue, 29 Jul 2008 09:47:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.177 X-Spam-Level: X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, 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 zIXJcYRDCfbz for ; Tue, 29 Jul 2008 09:47:58 -0700 (PDT) Received: from server9.hosting2go.nl (server9.hosting2go.nl [83.137.194.84]) by core3.amsl.com (Postfix) with ESMTP id 4176C3A691E for ; Tue, 29 Jul 2008 09:47:58 -0700 (PDT) Received: (qmail 15731 invoked from network); 29 Jul 2008 18:48:03 +0200 Received: from unknown (HELO M90Teco) (130.129.21.55) by server9.hosting2go.nl with SMTP; 29 Jul 2008 18:48:03 +0200 From: "Teco Boot" To: Date: Tue, 29 Jul 2008 18:47:35 +0200 Message-ID: <036c01c8f19a$e00b6580$a0223080$@nl> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acjxms0tOWB44oBoSrqC9eV4kArkRA== Content-Language: nl Subject: [Autoconf] New solution draft published X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org All, Our Autoconf solution draft is just published: http://www.ietf.org/internet-drafts/draft-boot-autoconf-brdp-00.txt The document is a cleaned up version of my previous proposal. Now it should be fully in line with the Autoconf charter for globally unique and topologically correct address autoconfiguration for Internet connected ad hoc networks (also called Subordinate MANETs in some documents). Non-Autoconf pieces of the proposal are taken out. Please comment on the document, our goal (not requirements) is publish updates frequently. Regards, Teco & Arjen. _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Jul 29 10:23:56 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A55C3A6A5C; Tue, 29 Jul 2008 10:23:56 -0700 (PDT) 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 141993A69FF for ; Tue, 29 Jul 2008 10:23:56 -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 9ptVQaIOGLSl for ; Tue, 29 Jul 2008 10:23:55 -0700 (PDT) Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 440413A6A5C for ; Tue, 29 Jul 2008 10:23:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=B70TyOeouugcVZZULBNyY+8Y12ayHRY5oy8xHd77VzjT3UjxnX59rF0+O/H0KwWc; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [130.129.18.220] by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KNsvf-0002oK-Ke for autoconf@ietf.org; Tue, 29 Jul 2008 13:24:07 -0400 Message-ID: <488F5235.6020108@earthlink.net> Date: Tue, 29 Jul 2008 10:24:05 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: autoconf@ietf.org X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f5262dbe26a9a9324c22999a0b771c5a3b9350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 130.129.18.220 Subject: [Autoconf] BarBOF proposal X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Hello folks, I propose that we meet at 9:00pm tomorrow to discuss various aspects related to making progress in the [autoconf] working group. I'd like to lead the discussion for a few minutes at the beginning, along two lines of thought: 1) What do we really want to accomplish in the working group? How can get put the group in gear? 2) Is it time to revise the notion of "on-link" to more closely reflect the reality of wireless communications and its range-based limitations? Regards, Charlie P. _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Tue Jul 29 14:19:15 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 395593A6A41; Tue, 29 Jul 2008 14:19:15 -0700 (PDT) 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 77C1C28C112 for ; Tue, 29 Jul 2008 14:19:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 rRcyDId-6iRJ for ; Tue, 29 Jul 2008 14:19:13 -0700 (PDT) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by core3.amsl.com (Postfix) with ESMTP id 2CE1F28C0ED for ; Tue, 29 Jul 2008 14:19:13 -0700 (PDT) Received: by fg-out-1718.google.com with SMTP id d23so2526618fga.41 for ; Tue, 29 Jul 2008 14:19:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=CB1BV6x5W7vAMiyL0/h8V+6R+vSqkoKTd4WszWWAjqE=; b=afYNClLZaOlSkXPw9Abb7vZo4rPVho+HxGv0GJNHPPCgj/VFvNKQrFkd4pWs1vBec9 eH8qmw5BNPFF75L/24XqkfhhMxXfeFq0WndtfPCxUEIDHvG43RC62NJVN8AeNwuPCWON TQ8XLWtzYDEHJSKN8h5IzAgPbSgrhX36Hh0ag= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=h6TxCqCjvq8BSGjt7P1XQtuJI9HGfzektqp2dx3pF3curF6MAHvXe3SK38KOrfWN2c ZAkUWN2HpK5OnD3OWRUYtQXJ/y3aNinwWfidMOaNtST+7TADTT6Bm25cIFBbrmz+ivMR t4uN11NFpi7yiEffJljKxygJKPdqW2KM/pUoo= Received: by 10.86.1.1 with SMTP id 1mr4094377fga.61.1217366364313; Tue, 29 Jul 2008 14:19:24 -0700 (PDT) Received: by 10.86.58.10 with HTTP; Tue, 29 Jul 2008 14:19:24 -0700 (PDT) Message-ID: Date: Tue, 29 Jul 2008 23:19:24 +0200 From: "Hasnaa Moustafa" To: autoconf@ietf.org In-Reply-To: MIME-Version: 1.0 References: Subject: Re: [Autoconf] Autoconf Digest, Vol 30, Issue 7 X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1307536204==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org --===============1307536204== Content-Type: multipart/alternative; boundary="----=_Part_71312_12320423.1217366364331" ------=_Part_71312_12320423.1217366364331 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Have you chosen a room for the meeting? Kind regards, Hassnaa Date: Tue, 29 Jul 2008 10:24:05 -0700 From: "Charles E. Perkins" Subject: [Autoconf] BarBOF proposal To: autoconf@ietf.org Message-ID: <488F5235.6020108@earthlink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hello folks, I propose that we meet at 9:00pm tomorrow to discuss various aspects related to making progress in the [autoconf] working group. I'd like to lead the discussion for a few minutes at the beginning, along two lines of thought: 1) What do we really want to accomplish in the working group? How can get put the group in gear? 2) Is it time to revise the notion of "on-link" to more closely reflect the reality of wireless communications and its range-based limitations? Regards, Charlie P. ------------------------------ _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf End of Autoconf Digest, Vol 30, Issue 7 *************************************** ------=_Part_71312_12320423.1217366364331 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Have you chosen a room for the meeting?
 
Kind regards,
Hassnaa
 
 
Date: Tue, 29 Jul 2008 10:24:05 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Subject: [Autoconf] BarBOF proposal
To: autoconf@ietf.org
Message-ID: <488F5235.6020108@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello folks,

I propose that we meet at 9:00pm tomorrow to
discuss various aspects related to making progress
in the [autoconf] working group.

I'd like to lead the discussion for a few minutes
at the beginning, along two lines of  thought:

1) What do we really want to accomplish in
   the working group?  How can get put the
   group in gear?

2) Is it time to revise the notion of "on-link" to
   more closely reflect the reality of wireless
   communications and its range-based
   limitations?

Regards,
Charlie P.


------------------------------

_______________________________________________
Autoconf mailing list
Autoconf@ietf.org
https://www.ietf.org/mailman/listinfo/autoconf


End of Autoconf Digest, Vol 30, Issue 7
***************************************
 

------=_Part_71312_12320423.1217366364331-- --===============1307536204== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============1307536204==-- From autoconf-bounces@ietf.org Wed Jul 30 07:19:22 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 322303A695D; Wed, 30 Jul 2008 07:19:22 -0700 (PDT) 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 A9F5A3A695D for ; Wed, 30 Jul 2008 07:19:19 -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 yi08fa4CyVOt for ; Wed, 30 Jul 2008 07:19:17 -0700 (PDT) Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 1453A3A686C for ; Wed, 30 Jul 2008 07:19:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=fIKV0u0ifioJZXUdZp0Hydace1PfHziCwn14tQcM7Zj6KqOtLOIIQhqobKMJkbeo; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [130.129.18.220] by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KOCWD-0005xZ-Nq for autoconf@ietf.org; Wed, 30 Jul 2008 10:19:10 -0400 Message-ID: <48907859.20104@earthlink.net> Date: Wed, 30 Jul 2008 07:19:05 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: autoconf@ietf.org X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f520f0e850e463011bfe6986036aa4aebf9350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 130.129.18.220 Subject: [Autoconf] BarBOF meeting place X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Hello folks, Let's meet in the upstairs meeting room on the second floor over the IETF registration area. There are tables there and lots of chairs. The time is still 9:00pm (i.e., 2100). Regards, Charlie P. _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Jul 30 08:32:37 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89FD63A6AC3; Wed, 30 Jul 2008 08:32:37 -0700 (PDT) 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 4566A3A688B for ; Wed, 30 Jul 2008 08:32:36 -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=[AWL=0.000, 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 u8uDA4Qa+QQ2 for ; Wed, 30 Jul 2008 08:32:35 -0700 (PDT) Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 62E373A6AC3 for ; Wed, 30 Jul 2008 08:32:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=HOxupnX7UlULX6aGBAjZZ2a7jFh/z0YpwLkxHyTaks9BN1cDS/MrZvL8tTNmuGpz; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:Subject:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [130.129.65.159] (helo=[172.16.4.200]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1KODfF-0000LB-ND for autoconf@ietf.org; Wed, 30 Jul 2008 11:32:34 -0400 Message-ID: <48908990.2030104@earthlink.net> Date: Wed, 30 Jul 2008 08:32:32 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: autoconf@ietf.org Content-Type: multipart/mixed; boundary="------------020700030201090505060800" X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f521cf362b5605da9857b420aa0083f927e350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 130.129.65.159 Subject: [Autoconf] BarBOF --> Silken Thomas Suite at 9:00pm [Fwd: [rt.amsl.com #9819] Room for 9:00pm tonight?] X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --------------020700030201090505060800 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello folks, I've gotten an "official" meeting room, namely the Silken Thomas Suite. So, see you there at 9:00pm! I'll try to go by the IETF registration area just before 9:00pm in case anyone has gone there for the meeting. Regards, Charlie P. > Charlie, > > You can use Silken Thomas Suite. > > Marcia > > On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: > >> > >> > Hello Marcia, >> > >> > Several people will be joining me in a meeting >> > this evening at 9:00pm. I reckon we would meet >> > at the IETF registration area and then move to >> > another room somewhere. >> > >> > Can you tell me if we can have a room for >> > this purpose? >> > >> > Thanks in advance, >> > Charlie P. >> > >> > > > > > > --------------020700030201090505060800 Content-Type: message/rfc822; name="[rt.amsl.com #9819] Room for 9:00pm tonight?.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="[rt.amsl.com #9819] Room for 9:00pm tonight?.eml" X-Account-Key: account6 X-Mozilla-Keys: Return-Path: Received: from noehlo.host ([127.0.0.1]) by mx-coward.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP id 1kocyh4Gd3Nl36K0; Wed, 30 Jul 2008 10:21:17 -0400 (EDT) Received: from mail.ietf.org ([64.170.98.32]) by mx-coward.atl.sa.earthlink.net (EarthLink SMTP Server) with ESMTP id 1kocyg31U3Nl36K1 for ; Wed, 30 Jul 2008 10:21:17 -0400 (EDT) Received: by core3.amsl.com (Postfix, from userid 30) id 157713A695D; Wed, 30 Jul 2008 07:21:00 -0700 (PDT) Subject: [rt.amsl.com #9819] Room for 9:00pm tonight? From: "Marcia Beaulieu via RT" Reply-To: agenda@ietf.org In-Reply-To: <48906439.1090107@earthlink.net> References: <48906439.1090107@earthlink.net> Message-ID: Precedence: bulk X-RT-Loop-Prevention: rt.amsl.com RT-Ticket: rt.amsl.com #9819 Managed-by: RT 3.6.5 (http://www.bestpractical.com/rt/) RT-Originator: mbeaulieu@amsl.com To: charles.perkins@earthlink.net MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 Date: Wed, 30 Jul 2008 07:21:01 -0700 X-ELNK-Received-Info: spv=0; X-ELNK-AV: 0 X-ELNK-Info: sbv=0; sbrc=.0; sbf=00; sbw=000; Charlie, You can use Silken Thomas Suite. Marcia On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: > > Hello Marcia, > > Several people will be joining me in a meeting > this evening at 9:00pm. I reckon we would meet > at the IETF registration area and then move to > another room somewhere. > > Can you tell me if we can have a room for > this purpose? > > Thanks in advance, > Charlie P. > --------------020700030201090505060800 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --------------020700030201090505060800-- From autoconf-bounces@ietf.org Wed Jul 30 09:52:33 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE98428C3A0; Wed, 30 Jul 2008 09:52:32 -0700 (PDT) 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 614D028C3A1 for ; Wed, 30 Jul 2008 09:52:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.272 X-Spam-Level: X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.327, 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 eZziMTOAqBiF for ; Wed, 30 Jul 2008 09:52:28 -0700 (PDT) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by core3.amsl.com (Postfix) with ESMTP id 59FBE28C39B for ; Wed, 30 Jul 2008 09:52:27 -0700 (PDT) Received: by yw-out-2324.google.com with SMTP id 3so54016ywj.49 for ; Wed, 30 Jul 2008 09:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:in-reply-to:subject :references:message-id:content-type:content-transfer-encoding :mime-version:date:cc:x-mailer; bh=FKd2BqcxDppAFTN+mHohgXywwWBm+OkBza4K73cAAQo=; b=tFHK10uMw228EKuPumhH/o8UM3cNTV8/yH6y0JLlwz4/afJA0sXoVU6a4gsbn+v/Ek W+mVKJTLFadr+z6kct7H7klitFFi9+uy9wmHjwTnvy7LRLjp3mEXrFDGZ9QWXD4jl1Kb Xw4TVidy4MHhAzqzky8sIkNp1dXVz8VLVzRko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:subject:references:message-id:content-type :content-transfer-encoding:mime-version:date:cc:x-mailer; b=WV+f4wrRdqt94plUKCW9ImClurs4Mx7T2qqaDFJhjbQ2BPNWgW5RZDX69c9StkIPQn /XweJXWLGHV8lmo0YA0N9CYoLXLfM8v0Ag47F6wcw8jtmFQdFd8RXsjGYlZ+QH7WEaYd 5ovcuwMadw0YPqnapeyoDS+5n6N3vTHPvG5oo= Received: by 10.114.195.19 with SMTP id s19mr8847905waf.110.1217436760753; Wed, 30 Jul 2008 09:52:40 -0700 (PDT) Received: from ?172.17.3.147? ( [130.129.65.86]) by mx.google.com with ESMTPS id j29sm2598390waf.49.2008.07.30.09.52.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 30 Jul 2008 09:52:40 -0700 (PDT) From: Ryuji Wakikawa To: Charles E. Perkins In-Reply-To: <48908990.2030104@earthlink.net> References: <48908990.2030104@earthlink.net> Message-Id: <5F8CA7C4-09DE-4505-B2C9-DFCF93BE06B8@gmail.com> Mime-Version: 1.0 (Apple Message framework v928.1) Date: Thu, 31 Jul 2008 01:52:31 +0900 X-Mailer: Apple Mail (2.928.1) Cc: autoconf@ietf.org Subject: Re: [Autoconf] BarBOF --> Silken Thomas Suite at 9:00pm [Fwd: [rt.amsl.com #9819] Room for 9:00pm tonight?] X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-2022-jp"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Hello Charlie, Thanks for setting this up. I will join the barbof tonight. regards ryuji On 2008/07/31, at 0:32, Charles E. Perkins wrote: > > Hello folks, > > I've gotten an "official" meeting room, namely > the Silken Thomas Suite. > > So, see you there at 9:00pm! I'll try to go by > the IETF registration area just before 9:00pm in > case anyone has gone there for the meeting. > > Regards, > Charlie P. > > >> Charlie, >> >> You can use Silken Thomas Suite. >> >> Marcia >> >> On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: >> >>> > > Hello Marcia, >>> > > Several people will be joining me in a meeting >>> > this evening at 9:00pm. I reckon we would meet >>> > at the IETF registration area and then move to >>> > another room somewhere. >>> > > Can you tell me if we can have a room for >>> > this purpose? >>> > > Thanks in advance, >>> > Charlie P. >>> > >> >> >> >> >> >> > > > > > 差出人: "Marcia Beaulieu via RT" > 日時: 2008年7月30日 23:21:01:JST > 宛先: charles.perkins@earthlink.net > 件名: [rt.amsl.com #9819] Room for 9:00pm tonight? > 返信先: agenda@ietf.org > > > Charlie, > > You can use Silken Thomas Suite. > > Marcia > > On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: >> >> Hello Marcia, >> >> Several people will be joining me in a meeting >> this evening at 9:00pm. I reckon we would meet >> at the IETF registration area and then move to >> another room somewhere. >> >> Can you tell me if we can have a room for >> this purpose? >> >> Thanks in advance, >> Charlie P. >> > > > > > > > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Jul 30 11:00:18 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A4B228C3B4; Wed, 30 Jul 2008 11:00:18 -0700 (PDT) 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 C9D8D28C3B4 for ; Wed, 30 Jul 2008 11:00:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.649 X-Spam-Level: X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=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 N0bxF8wJ1LNF for ; Wed, 30 Jul 2008 11:00:16 -0700 (PDT) Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by core3.amsl.com (Postfix) with ESMTP id 2976B28C39C for ; Wed, 30 Jul 2008 11:00:16 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,280,1215381600"; d="scan'208";a="13596687" Received: from unknown (HELO BoolfightMaN-Laptop.local) ([130.129.65.2]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 30 Jul 2008 20:00:29 +0200 Message-ID: <4890AC3C.4020500@inria.fr> Date: Wed, 30 Jul 2008 20:00:28 +0200 From: Emmanuel Baccelli User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: autoconf@ietf.org References: <48908990.2030104@earthlink.net> <5F8CA7C4-09DE-4505-B2C9-DFCF93BE06B8@gmail.com> In-Reply-To: <5F8CA7C4-09DE-4505-B2C9-DFCF93BE06B8@gmail.com> Subject: Re: [Autoconf] BarBOF --> Silken Thomas Suite at 9:00pm [Fwd: [rt.amsl.com #9819] Room for 9:00pm tonight?] X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Me too, cheers Emmanuel Ryuji Wakikawa a e'crit : > Hello Charlie, > > Thanks for setting this up. I will join the barbof tonight. > > regards > ryuji > > On 2008/07/31, at 0:32, Charles E. Perkins wrote: > >> >> Hello folks, >> >> I've gotten an "official" meeting room, namely >> the Silken Thomas Suite. >> >> So, see you there at 9:00pm! I'll try to go by >> the IETF registration area just before 9:00pm in >> case anyone has gone there for the meeting. >> >> Regards, >> Charlie P. >> >> >>> Charlie, >>> >>> You can use Silken Thomas Suite. >>> >>> Marcia >>> >>> On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: >>> >>>> > > Hello Marcia, >>>> > > Several people will be joining me in a meeting >>>> > this evening at 9:00pm. I reckon we would meet >>>> > at the IETF registration area and then move to >>>> > another room somewhere. >>>> > > Can you tell me if we can have a room for >>>> > this purpose? >>>> > > Thanks in advance, >>>> > Charlie P. >>>> > >>> >>> >>> >>> >>> >>> >> >> >> >> >> 差出人: "Marcia Beaulieu via RT" >> 日時: 2008年7月30日 23:21:01:JST >> 宛先: charles.perkins@earthlink.net >> 件名: [rt.amsl.com #9819] Room for 9:00pm tonight? >> 返信先: agenda@ietf.org >> >> >> Charlie, >> >> You can use Silken Thomas Suite. >> >> Marcia >> >> On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: >>> >>> Hello Marcia, >>> >>> Several people will be joining me in a meeting >>> this evening at 9:00pm. I reckon we would meet >>> at the IETF registration area and then move to >>> another room somewhere. >>> >>> Can you tell me if we can have a room for >>> this purpose? >>> >>> Thanks in advance, >>> Charlie P. >>> >> >> >> >> >> >> >> >> _______________________________________________ >> Autoconf mailing list >> Autoconf@ietf.org >> https://www.ietf.org/mailman/listinfo/autoconf > > _______________________________________________ > Autoconf mailing list > Autoconf@ietf.org > https://www.ietf.org/mailman/listinfo/autoconf > > _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Jul 30 12:18:50 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60E353A6C57; Wed, 30 Jul 2008 12:18:50 -0700 (PDT) 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 5945F3A6C55 for ; Wed, 30 Jul 2008 12:18:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.51 X-Spam-Level: X-Spam-Status: No, score=0.51 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_14=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 8ET7NLpFo5dy for ; Wed, 30 Jul 2008 12:18:48 -0700 (PDT) Received: from mxav02.cc.niigata-u.ac.jp (mxav02.cc.niigata-u.ac.jp [133.35.17.130]) by core3.amsl.com (Postfix) with ESMTP id 436D73A6C58 for ; Wed, 30 Jul 2008 12:18:48 -0700 (PDT) Received: from mxav02.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 5DBCE454178 for ; Thu, 31 Jul 2008 04:19:01 +0900 (JST) Received: from chamame.ie.niigata-u.ac.jp (chamame.ie.niigata-u.ac.jp [133.35.169.34]) by mxav02.cc.niigata-u.ac.jp (Postfix) with SMTP id 534F54540A6 for ; Thu, 31 Jul 2008 04:19:01 +0900 (JST) Received: (qmail 3069 invoked from network); 31 Jul 2008 04:19:02 +0900 Received: from unknown (HELO neccomputer.ie.niigata-u.ac.jp) (133.35.156.66) by chamame.ie.niigata-u.ac.jp with SMTP; 31 Jul 2008 04:19:02 +0900 Message-Id: <7.0.0.16.2.20080731041824.05d8fa18@ie.niigata-u.ac.jp> X-Mailer: QUALCOMM Windows Eudora Version 7J rev1.0 Date: Thu, 31 Jul 2008 04:19:01 +0900 To: Emmanuel Baccelli ,autoconf@ietf.org From: mase In-Reply-To: <4890AC3C.4020500@inria.fr> References: <48908990.2030104@earthlink.net> <5F8CA7C4-09DE-4505-B2C9-DFCF93BE06B8@gmail.com> <4890AC3C.4020500@inria.fr> Mime-Version: 1.0 Subject: Re: [Autoconf] BarBOF --> Silken Thomas Suite at 9:00pm[Fwd: [rt.amsl.com #9819] Room for 9:00pm tonight?] X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-2022-jp"; Format="flowed" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Me too. Thanks, Kenichi At 03:00 08/07/31, Emmanuel Baccelli wrote: >Me too, >cheers >Emmanuel > >Ryuji Wakikawa a e'crit : > > Hello Charlie, > > > > Thanks for setting this up. I will join the barbof tonight. > > > > regards > > ryuji > > > > On 2008/07/31, at 0:32, Charles E. Perkins wrote: > > > >> > >> Hello folks, > >> > >> I've gotten an "official" meeting room, namely > >> the Silken Thomas Suite. > >> > >> So, see you there at 9:00pm! I'll try to go by > >> the IETF registration area just before 9:00pm in > >> case anyone has gone there for the meeting. > >> > >> Regards, > >> Charlie P. > >> > >> > >>> Charlie, > >>> > >>> You can use Silken Thomas Suite. > >>> > >>> Marcia > >>> > >>> On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: > >>> > >>>> > > Hello Marcia, > >>>> > > Several people will be joining me in a meeting > >>>> > this evening at 9:00pm. I reckon we would meet > >>>> > at the IETF registration area and then move to > >>>> > another room somewhere. > >>>> > > Can you tell me if we can have a room for > >>>> > this purpose? > >>>> > > Thanks in advance, > >>>> > Charlie P. > >>>> > > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > >> > >> 差出人: "Marcia Beaulieu via RT" > >> 日時: 2008年7月30日 23:21:01:JST > >> 宛先: charles.perkins@earthlink.net > >> 件名: [rt.amsl.com #9819] Room for 9:00pm tonight? > >> 返信先: agenda@ietf.org > >> > >> > >> Charlie, > >> > >> You can use Silken Thomas Suite. > >> > >> Marcia > >> > >> On Wed Jul 30 05:53:04 2008, charles.perkins@earthlink.net wrote: > >>> > >>> Hello Marcia, > >>> > >>> Several people will be joining me in a meeting > >>> this evening at 9:00pm. I reckon we would meet > >>> at the IETF registration area and then move to > >>> another room somewhere. > >>> > >>> Can you tell me if we can have a room for > >>> this purpose? > >>> > >>> Thanks in advance, > >>> Charlie P. > >>> > >> > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Autoconf mailing list > >> Autoconf@ietf.org > >> https://www.ietf.org/mailman/listinfo/autoconf > > > > _______________________________________________ > > Autoconf mailing list > > Autoconf@ietf.org > > https://www.ietf.org/mailman/listinfo/autoconf > > > > >_______________________________________________ >Autoconf mailing list >Autoconf@ietf.org >https://www.ietf.org/mailman/listinfo/autoconf _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf From autoconf-bounces@ietf.org Wed Jul 30 16:22:13 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49E2A3A68A1; Wed, 30 Jul 2008 16:22:13 -0700 (PDT) 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 5165C3A68A1 for ; Wed, 30 Jul 2008 16:22:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.356 X-Spam-Level: * X-Spam-Status: No, score=1.356 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001] 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 g+r5+aVauthY for ; Wed, 30 Jul 2008 16:22:10 -0700 (PDT) Received: from mailoutb.tno.nl (mailoutb.tno.nl [134.221.1.17]) by core3.amsl.com (Postfix) with ESMTP id 1783B3A67AC for ; Wed, 30 Jul 2008 16:22:09 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.31,282,1215381600"; d="scan'208,217";a="1725265" Received: from ms-dt01thalia.tno.nl (HELO ms-dt01thalia.tsn.tno.nl) ([134.221.225.157]) by mailhost1b.tno.nl with ESMTP; 31 Jul 2008 01:22:24 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 31 Jul 2008 01:22:24 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sweater Thread-Index: Acjym2tIfVtAfXlWRnKa6NU3gbdeYA== From: "Holtzer, A.C.G. (Arjen)" To: Subject: [Autoconf] sweater X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1275189443==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org This is a multi-part message in MIME format. --===============1275189443== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8F29B.1F775292" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8F29B.1F775292 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Hi, Someone left his/her sweater in the Silken Thomas Suite after the meeting. It can now be found among the lost properties at the reception. Regards, Arjen This e-mail and its contents are subject to the DISCLAIMER at http://www.tn= o.nl/disclaimer/email.html ------_=_NextPart_001_01C8F29B.1F775292 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" sweater

Hi,

Someone left his/her sweater in the Silken= Thomas Suite after the meeting. It can now be found among the lost propert= ies at the reception.

Regards,
Arjen 

This e-mail and its contents are subject to the DISCLAIMER at http://w=
ww.tno.nl/disclaimer/email.html
------_=_NextPart_001_01C8F29B.1F775292-- --===============1275189443== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============1275189443==-- From autoconf-bounces@ietf.org Thu Jul 31 01:21:54 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FBC63A6ABD; Thu, 31 Jul 2008 01:21:54 -0700 (PDT) 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 268FA3A6AE9 for ; Thu, 31 Jul 2008 01:21:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.237 X-Spam-Level: X-Spam-Status: No, score=-0.237 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, 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 9fXFQ7kcHfS4 for ; Thu, 31 Jul 2008 01:21:49 -0700 (PDT) Received: from server9.hosting2go.nl (server9.hosting2go.nl [83.137.194.84]) by core3.amsl.com (Postfix) with ESMTP id 9C9393A6ABD for ; Thu, 31 Jul 2008 01:21:48 -0700 (PDT) Received: (qmail 31677 invoked from network); 31 Jul 2008 10:14:49 +0200 Received: from unknown (HELO M90Teco) (130.129.21.55) by server9.hosting2go.nl with SMTP; 31 Jul 2008 10:14:49 +0200 From: "Teco Boot" To: References: In-Reply-To: Date: Thu, 31 Jul 2008 10:14:21 +0200 Message-ID: <002401c8f2e5$8227ad10$86770730$@nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0025_01C8F2F6.45B07D10" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acjy2ud4zOkYCaZQRseNwLtracT/DgAClDDA Content-Language: nl Subject: Re: [Autoconf] Follow-up barBOF meeting X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Dit is een meerdelig bericht met een MIME-indeling. ------=_NextPart_000_0025_01C8F2F6.45B07D10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Now size <50k for not getting bounced. Teco. > -----Oorspronkelijk bericht----- > Van: Teco Boot [mailto:teco@inf-net.nl] > Verzonden: donderdag 31 juli 2008 8:59 > Aan: 'autoconf@ietf.org' > Onderwerp: Follow-up barBOF meeting > > All, > IMHO we should refine the manetarch. > Here quite old review input, sent to authors of manetarch some weeks > after Philly. > Another old comment is that we should take out section 3 "MANET > Categories" from the PS document and put it into manetarch. > Regards, Teco ------=_NextPart_000_0025_01C8F2F6.45B07D10 Content-Type: text/plain; name="Autoconf-manetarch-teco-190308a.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Autoconf-manetarch-teco-190308a.txt" Marking: link: 12x links: 3x interface: 38x interfaces: 37x SBI: 8x All marked with qqq; c/qqq // to undo this change My remarks start with "Teco:" MANET Autoconfiguration (AUTOCONF) I. Chakeres Internet-Draft Motorola Intended status: Informational J. Macker Expires: May 11, 2008 Naval Research Laboratory T. Clausen LIX, Ecole Polytechnique November 8, 2007 Mobile Ad hoc Network Architecture draft-ietf-autoconf-manetarch-07 Status of this Memo Abstract This document discusses Mobile Ad hoc NETworks (MANETs). It presents the initial motivation for MANET and describes unaccustomed characteristics and challenges. It also defines a MANET, other MANET entities, and MANET architectural concepts. Chakeres, et al. Expires May 11, 2008 [Page 1] =0C Internet-Draft MANET Architecture November 2007 Table of Contents Chakeres, et al. Expires May 11, 2008 [Page 2] =0C Internet-Draft MANET Architecture November 2007 1. Introduction A Mobile Ad hoc NETwork (MANET) consists of a loosely connected domain of routers. A MANET is characterized by inclusion of one or more MANET qqq interfaces; qqq interfaces that are distinguished by = their potentially significant time-vary asymmetric reachability amongst neighboring routers. These routers organize and maintain a routing structure among themselves. These routers may communicate over dynamic wireless channels with asymmetric reachability, may be mobile, and may join and leave the network at any time. These MANETs' characteristics create challenges in several areas. Teco: Asymmetric reachability: Interfaces used where RFC4861 uses link = property. Usage not incorrect, but somewhat confusing for some of us. This document is focused on IP networking, though many of MANETs' concepts and issues span the protocol stack. This document is meant to complement [RFC2501] in describing and defining MANET. 2. Terminology 2.1. Borrowed Terminology This document employs the following definitions: Node (N) any device (router or host) that implements IP. Router (R) a node that forwards IP packets not explicitly addressed to itself. Host (H) any node that is not a router, i.e. a host does not forward packets addressed to others. Chakeres, et al. Expires May 11, 2008 [Page 3] =0C Internet-Draft MANET Architecture November 2007 qqq link a communication facility or medium over which nodes can communicate at the qqq link layer, i.e., the layer immediately = below IP. Examples are Ethernets (simple or bridged), PPP qqq links, = X.25, Frame Relay, or ATM networks as well as internet (or higher) layer "tunnels", such as tunnels over IPv4 or IPv6 itself. Teco: Why not mentioning also a wireless link? MANET is all about = wireless (radio) links. Asymmetric Reachability Asymmetric reachability describes two properties of certain qqq interface types' underlying communication facilities. First, = non- transitive communication means packets from X can reach Y, and packets from Y can reach Z, but packets from X may not reach Z. Second, non-bidirectional communication means that packets from X can reach Y but packets from Y may not reach X. Many radio/ wireless qqq interfaces exhibit these properties. Teco: Again, interface used where RFC4861 uses link. Not incorrect, but = confusing. Neighbor In the context of routing, two routers are neighbors if one can send/receive routing protocol IP packets to the other without passing through any intermediaries at the same layer. qqq interface A node's point of attachment to a communication qqq link. Teco: Correct. Semi-Broadcast qqq interface (qqq SBI) A broadcast capable qqq interface that may exhibit asymmetric reachability. Multiple access wireless radio qqq interfaces are = often qqq SBI. Note that since a qqq SBI *may* exhibit asymmetric = reachability, it also may not. Teco: Text is correct, but why introducing this new term? I think an = interface is broadcast capable or not. I am not aware of something in = between. Definition is almost equivalent with definition of MANET = interface (below). I suggest simply remove this SBI definition. Proposed text changes for = removal provided. Routing Domain (Domain) A routing domain is an interconnected network with a coherent routing policy and a consistent metric framework. Border Router (BR) A border router participates in multiple routing domains, and often multiple routing protocols. A BR defines the border between its multiple routing domains. A BR is responsible for presenting a consistent picture of the nodes reachable through itself to each routing domain. A BR determines the routing information to propagate between different routing domains. 2.2. MANET Terminology The following terminology is specific to MANETs: Chakeres, et al. Expires May 11, 2008 [Page 4] =0C Internet-Draft MANET Architecture November 2007 MANET qqq interface A MANET qqq interface is distinguished by its potentially = significant time-varying asymmetric reachability (e.g., qqq SBI) amongst = potential neighboring routers. A more detailed discussion of MANET qqq interface characteristics is presented in Section 4.2. The addressing constraints for a MANET qqq interface are discussed in Section 5.2. Teco: Remove " (e.g., qqq SBI)". Suggestion: add word "wireless" or "radio": > A MANET interface is MANET Router's point of attachment to a = wireless communication link. > It is distinguished from non-MANET interfaces by its potentially = significant > time-varying asymmetric reachability amongst potential > neighboring routers. A more detailed discussion of MANET > interface characteristics is presented in Section 4.2. The > addressing constraints for a MANET interface are discussed in > Section 5.2. MANET Router (MNR) A MANET router is distinguished by having one or more MANET qqq interfaces. A MANET router may also have zero or more = non-MANET qqq interfaces. A MANET router is responsible for hiding MANETs' challenging characteristics from nodes that are not MANET-aware. A MANET router with a single MANET qqq interface is illustrated in Figure 1. Teco: Original comment: What is a non-MANET interface? Personally I have some experience with = links that had time-varying asymmetric reachability. Some are history = (10Base5, 10baseT; both with cabling problems) and some are very actual = (satcom systems which may experience problems with crypto, HPA, LNA or = other problems). Would you call these interfaces MANET Interfaces and the attached = routers MANET Routers? I would definitely not. Teco:=20 After update MANET interface: now the term wireless link is used in = MANET interface definition. MANET Neighborhood a set of neighboring routers that can communicate via MANET qqq interfaces without passing through any other routers (intermediaries at the same layer). Teco: I do not understand what is meant. Look for example at figure 2. = What is the MANET Neighborhood? PR1 and PR2 and PR3? Maybe yes, seen by = PR2. But PR2 should exclude itself from the set, so it is only PR1 and = PR3. PR1 thinks only PR2 is the MANET Neighborhood.=20 In text, a new definition pops up: # A MANET neighborhood is # typically composed of several MANET routers, with each MANET router # being densely connected to other MANET routers. What is densely? Is a single link (as figure 2) densely? I don't think = so. Maybe skip this term completely? MANET a routing domain containing MANET routers. A example MANET is=20 illustrated in Figure 3. <~~~~~~+~~~~~~> MANET | qqq interface ''''''''''''' ' MANET ' ' Router ' ''''''''''''' Figure 1: MANET Router with One MANET qqq interface Dependent upon the deployment and management strategy, coalescing and fragmentation of MANETs may be a supported feature. In other words, if a communication path between two previously separated MANET routers or MANETs becomes available, the two MANETs may merge to form a single larger MANET. Similarly, if a communication path between two MANET routers disappears and no alternative path between the routers exists, then the MANET may be partitioned into two separate MANETs. When discussing MANETs' connectivity to other networks, such as the Internet, a MANET is bounded by border routers (BR). That is, a MANET's BR form a border between a MANET and other routing domains. Chakeres, et al. Expires May 11, 2008 [Page 5] =0C Internet-Draft MANET Architecture November 2007 3. MANET Motivation Discussion The Internet Protocol (IP) core design tenets -- connectionless networking and packet-based forwarding -- are ideally suited for use in highly dynamic contexts, such as MANETs. Yet, some additional functionality is required to meet the unique challenges and opportunities present in MANETs. 3.1. Packet Radio Networks The initial motivation for MANETs was called Packet Radio (PR) networking [FL01]. In PR, each router is equipped with a single Teco: Is this really initial? RFC2501 was 1999, FL01 2001. I did not = verify, but I doubt the claim is valid. wireless qqq interface. Each router may be mobile, and the routers = may be or may become spatially distributed such that all routers cannot communicate directly. That is, two routers might require one or more intermediate routers to forward (route) packets on their behalf. In the example shown in Figure 2: for PR1 to send packets to PR3, the intermediary PR2 must relay the packets. This implies that PR2 must receive the packet from PR1 on its qqq interface and determine that = it must retransmit the packet over the same qqq interface as the one = where the packet was received, in order for the packet to reach PR3. From the point of view of PR2, both PR1 and PR3 are neighboring routers, whereas PR1 and PR3 are not themselves neighboring routers of one another. Communication Range <~~~~~~+~~~~~~> <~~~~~~+~~~~~~> Single | <~~~~~~+~~~~~~> | MANET +-|-+ +-|-+ +-|-+ qqq interface |PR1| |PR2| |PR3| +---+ +---+ +---+ Figure 2: Basic Packet Radio Network 3.2. Packet Radio Networks and the Internet Packet Radio networks inspired several architecture related challenges, including how to interconnect Packet Radio networks and other networks, especially fixed networks like the ARPANET. Another related challenge was how to deal with the large disparity between different node and qqq interface characteristics present in different networks. Teco: here the term link better suits what is meant. > other networks, especially fixed networks like the ARPANET. Another > related challenge was how to deal with the large disparity between > different node and wireless link characteristics present in = different > networks. These aspects of Packet Radio networks helped stimulate the early development of the Internet Protocol; an architecture based on Chakeres, et al. Expires May 11, 2008 [Page 6] =0C Internet-Draft MANET Architecture November 2007 connectionless networking and packet-based forwarding that enables interconnection of heterogeneous devices over heterogeneous communication technologies. 3.3. Packet Radio Networks and MANETs Chakeres, et al. Expires May 11, 2008 [Page 7] =0C Internet-Draft MANET Architecture November 2007 4. MANET qqq interface Characteristics Inheriting from Packet Radio as described above, primary particularities of MANETs are the characteristics and qualities of MANET qqq interfaces, and the challenges these entail for protocol = design and development. 4.1. Qualities - Wireless, Mobile, Ad hoc In MANETs several qualities impact protocol design. The most fundamental qualities are wireless qqq interface characteristics, mobility, and ad hoc interaction. Wireless qqq interfaces often exhibit more challenging = characteristics when compared to wired qqq interfaces. Many protocols (e.g., IPv6 neighbor discovery [RFC4861]) were not designed to operate in wireless networks with asymmetric reachability. Wireless qqq = interfaces may also exhibit very dynamic time varying performance (e.g., packet loss, data rate), and the factors have a significant impact on local communication. Mobility can also exacerbate communication issues, making it more challenging to attain, establish, and maintain network relationships between nodes. Ad hoc networking further compounds problems by allowing nodes to join and leave the network, or even form new networks, at will. 4.2. Challenges MANET characteristics result in many challenges. These challenges reveal themselves in many forms, and MANET specific protocols must often be developed. 4.2.1. Semi-Broadcast qqq interface Teco: Can be changed in MANET Interface Given a wireless SBI that exhibits time-varying asymmetric reachability and spatially distributed MANET routers, each MANET router may have a different unique partial view of the MANET. That is, each node may see a different set of neighboring MANET routers. Teco: SBI can be changed in MANET Interface. And maybe better reflect = link property. And "each node may see a different set of neighboring = MANET routers" is not specific for MANET routers, all routers exhibit = this. Proposed text: > A MANET Interface exhibits time-varying asymmetric reachability to = other > spatially distributed MANET routers, depending on connectivity = provided by the wireless links. Chakeres, et al. Expires May 11, 2008 [Page 8] =0C Internet-Draft MANET Architecture November 2007 Communication Range <~~~~~~~~+~~~~~~~~> <~~~~~~~~+~~~~~~~> Single |<~~~~~~~~+~~~~~~~~>| SBI +--|-+ +--|-+ +--|-+ |MNR1| |MNR2| |MNR3| +----+ +----+ +----+ MNR1 MNR2 MNR3 ------------------------- Neighboring MNR2 MNR1 MNR2 Routers MNR3 Figure 4: Semi-Broadcast qqq interface (SBI) Neighboring Routers Teco: Can be changed in MANET Interface In picture, three MANET interfaces are depicted, what is meant by Single = SBI? Replace with simply "MANET"? The possibly unique set of neighboring MANET routers perceived by each MANET router often requires MANET routers to send packets out the same wireless qqq interface as the one over which they were = received. Topologically, this act of forwarding out the same qqq interface may cause a packet to reach a different set of MANET routers by traversing the wireless communication medium in a new location. An example is provided in Figure 4, where each MANET router is capable of reaching a different set of MANET routers. The act of forwarding packets out of the same qqq interface as the = one over which they were received often results in duplicate IP packets being received by MANET routers with more than one neighboring MANET router, while also reaching a new subset of MANET routers. Thus, duplicate packet detection is often an inherent part of MANET protocol designs. 4.2.2. Fuzzy Relationships Between Nearby MANET Routers & MANET Routers' Extended Neighborhoods Defining the process of determining neighboring MANET routers' existence, continued existence, and loss of existence is a fundamental challenge in MANETs. Relationships with neighboring MANET routers are hard to define due to the MANET qqq interface characteristics. Teco: Just remove term "interface". The characteristic is not about the = interface, but about the link to other nodes. > Defining the process of determining neighboring MANET routers' > existence, continued existence, and loss of existence is a > fundamental challenge in MANETs. Relationships with neighboring > MANET routers are hard to define due to the MANET characteristics. Historically, two nodes are either neighbors or not neighbors and several simple mechanisms have been used to determine neighbor relationships: single packet reception, acceptable loss rates, and simple handshakes. [RFC4861], for example, employs an initial exchange of messages to determine neighborship or absence thereof. In networks with MANET qqq interface the types of neighbor = relationships Teco: Proposed text: > In a MANET, the types of neighbor relationships expand, as do the mechanisms to detect and maintain the state of such Chakeres, et al. Expires May 11, 2008 [Page 9] =0C Internet-Draft MANET Architecture November 2007 relationships. Wireless network qqq interfaces may exhibit unidirectional = communication. Teco: Here Thomas Narten is going to yell. And he is right. If an = interface exhibit unidirectional communication, it is stuck. Buy a new = one;-).- It is about the connectivity to other nodes, this is about the = link. Proposed text: > Wireless networks may exhibit unidirectional communication. Dynamic wireless networks may also experience significant time varying packet delivery between the same pair of wireless network qqq interfaces, so simple loss rates may not be sufficient to define = a Teco: replace "interfaces" with "nodes": > nodes, so simple loss rates may not be sufficient to define a neighbor relationship. Similarly, as nodes (and, hence, qqq = interfaces) Teco: just remove " (and, hence, interfaces)". move relatively to each other, past loss rates may not reflect future communication capabilities. In MANETs' with qqq SBI, MANET routers within the same small = geographic region are often densely connected with other nearby MANET routers. These routers form a set of extended neighbor relationships. This set is referred to as a MANET neighborhood. A MANET neighborhood is typically composed of several MANET routers, with each MANET router being densely connected to other MANET routers. Teco: Just remove "In MANETs' with SBI, ". And think of rewording this text, eliminating "MANET neighborhood" or = "extended neighbor relationships". Proposed text: > A large group of MANET routers within the same small geographic > region are often densely connected with each other. Due to movement > of the MANET routers, the neighbor relationship changes over time. These more dynamic neighbor relationships do not sit well with certain Internet Protocols designed assuming a fixed Ethernet like model to communication qqq links (bidirectional, transitive, and = stable). Given the fuzzy neighbor relationships between MANET routers, the addressing model often associated with a Ethernet qqq link is not logical. For example, in an Ethernet network nodes are often told that a particular range of addresses are "on-qqq link". In MANETs' a MANET router often cannot make assumptions that a particular set of MANET routers is always (directly) reachable. Instead, MANET routers must detect and determine neighboring MANET routers, and handle changes to this set over time. 4.2.3. MANET Membership Given MANETs' characteristics (mobile, wireless, ad hoc), determining a MANETs' membership is difficult, if not impossible in certain scenarios. Chakeres, et al. Expires May 11, 2008 [Page 10] =0C Internet-Draft MANET Architecture November 2007 /----------------------\ /----------------------\ | MANET | | MANET | | +----+ +----+ +----+ | | +----+ +----+ +----+ | | |MNR1+-+MNR2+-+MNR3| | | |MNR1+-+MNR2+-+MNR3| | | +-+--+ +----+ +----+ | | +----+ +----+ +-+--+ | | | | | | | | +-+--+ | Change | +-+--+ | | |MNR4| | in | |MNR7| | | +----+ | Time | +----+ | | \ | \----------------------/ | +----+ | | |MNR5| | | +----+ | /----------------------\ | / \ | | MANET | | +----+ +----+ | | +----+ +----+ +----+ | | |MNR6| |MNR7| | | |MNR6+-+MNR4+-+MNR5| | | +----+ +----+ | | +----+ +----+ +----+ | \----------------------/ \----------------------/ Figure 5: MANET(s) At one moment a MANET might consist of a certain set of nodes, and the next the MANET could partition into several MANETs. Later it might re-merge or merge with a new set of nodes and form a larger MANET. Teco: Text below is about Border Routers. I think this needs a separate section. I proposed this many times = before... Certain routers in a MANET might connect to other routing domains. These routers are called Border Routers (BRs), and they often run multiple routing protocol instances. BRs are responsible for choosing the routing information to announce between the various attached routing domains. BRs should also present a consistent picture of the nodes reachable through them. As MANET membership changes, so does the connectivity of BRs within the MANET. Therefore, a BR may be challenged to present a consistent set of reachable nodes. It may even choose not to announce any routing information about the MANET to other routing domains. 5. Addressing & the MANET Prefix Model This section presents an architectural model for MANETs which preserves the integrity of the conventional IP addressing architecture while allowing for the particularities of MANET qqq interfaces. Chakeres, et al. Expires May 11, 2008 [Page 11] =0C Internet-Draft MANET Architecture November 2007 5.1. General Address Architecture This architectural model considers MANET routers as simply routers with nodes possibly attached. These attached nodes may be attached "behind the router"; that is, the router may be responsible for announcing the location of a particular address or set of addresses (i.e. a subnet prefix). This configuration implies that, from the point of view of these nodes and the applications running on them, they are not exposed to the specific characteristics of MANET qqq interfaces. Teco: First MANET characteristics, then MANET: > This configuration implies that, from the point of view of these > nodes and the applications running on them, they are not exposed to > the specific characteristics of a MANET and MANET interfaces. =20 A MANET router can be delegated zero or more prefixes. For example, if a MANET router is delegated a prefix p::, then subnet prefixes derived from this prefix (e.g, p:1::/64, p:2::/64, ...) may be assigned to the MANET routers' non-MANET qqq interfaces(s), and nodes = on these qqq interfaces may be assigned addresses from within this = prefix, and configured with this prefix according to the address autoconfiguration mechanisms governing these qqq interfaces = ([RFC4861] and [RFC4862]). This concept is illustrated in Figure 6. MANET qqq interfaces are specifically *NOT* configured with this = prefix. The configuration of these MANET qqq interfaces is detailed in Section 5.2. Teco: I do not agree on this restriction, I posted this before. I do not = see any reason not configuring for example p::3/64 on the MANET = interface. It is unique, it overlaps with the delegated prefix but this = is OK. I know Thomas C. prefers a /128, but I saw problems with IP = stacks, they assumed a /128 is stub. Why not using a link local and = using the loopback as global unique address?=20 MANET <~~~~~~+~~~~~~> qqq interface | Delegated | Prefix ''''''''''''''''''''' =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ' MANET ' <=3D=3D=3D P::/62 =3D ' Router ' =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ''''''''' : ' Assigned : ' : ' Prefix : '++--------+' = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D : '|Loopback |' <=3D=3D=3D P:1::/64 =3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D : '|P:1::L/64|' = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D : =3D : '+---------+' =20 =3D Other =3D : ''''''''''''' Assigned =3Dqqq interfaces=3D : Prefix =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D : = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +...+...........+ <=3D=3D=3D P:2::/64 =3D : : = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +------+--+ +--+------+ |P:2::1/64| * * * |P:2::K/64| +---------+ +---------+ Chakeres, et al. Expires May 11, 2008 [Page 12] =0C Internet-Draft MANET Architecture November 2007 Figure 6: MANET Router and Prefixes Example 5.2. MANET qqq interface Configuration MANET qqq interface specific behaviors are exclusively exposed to the MANET routers. These behaviors may include asymmetric reachability, semi-broadcast qqq interfaces, fuzzy MANET router neighbor = relationships, changing MANET membership, rapid topology dynamics, etc. Teco: Interface and link behavior are mixed up. Text is a short and = incomplete summary of section 4.=20 I suggest to remove this paragraph. The following characteristics deserve particular mention, since they distinguish the configuration and behavior of MANET qqq interface(s): Teco: Proposed text, after removal previous paragraph: > The MANET Interface characteristics as described in section 4 = deserve particular mention, since they > distinguish the configuration and behavior of MANET interface(s): Unique Prefixes MANET qqq interfaces that are known to exhibit the above mentioned properties must be configured with unique prefixes. The reason Teco: Recently the term "disjoint" was introduced, which is a better = term. for this requirements is so that no two MANET qqq interfaces are configured to appear within the same IP prefix. One way to achieve this is /128 (IPv6) or /32 (IPv4) prefixes. It is worth noting that prefix lengths shorter than /128 (IPv6) or /32 (IPv4) are possible on the MANET qqq interfaces, as long as the prefixes = are unique to a single MANET qqq interface. Note that the above statements are not an exception, but simply a clarification that MANET are no different from other networks in this respect. Teco: Remark on /128: I reject this proposal. qqq link-local Multicast/Broadcast Scope On a MANET qqq interface, a packet sent to a qqq link-local = multicast or all-ones broadcast address reaches the MANET qqq interfaces of neighboring MANET routers, regardless of their configured addresses. qqq link-local multicast/broadcast packets are never forwarded and since a MANET may span several hops, nodes cannot assume that a packet sent to a qqq link-local multicast/broadcast address will reach all routers within a MANET. Teco: Only 1-hop neighbors are reached. Proposed text: > On a MANET interface, a packet sent to a link-local multicast or > all-ones broadcast address (IPv4) reaches the MANET interfaces of > 1-hop neighboring MANET routers, regardless of their configured > addresses. Link-local multicast/broadcast packets are never > forwarded and since a MANET may span several hops, nodes cannot > assume that a packet sent to a link-local multicast/broadcast > address will reach all routers within a MANET. Teco: And I do not think this is a problem! 5.3. Routers and Hosts in a MANET The MANET addressing model presented in this section makes a clear separation between the role of MANET router and host in a MANET, recognizing that: o MANET qqq interface characteristics are only exposed to = MANET-aware routers running appropriate protocols; o nodes and networks/subnets on non-MANET qqq interface(s) are not subjected considering MANET characteristics; o applications on hosts and protocols run unmodified. MANET protocols are protocols developed to work on MANET qqq = interfaces Chakeres, et al. Expires May 11, 2008 [Page 13] =0C Internet-Draft MANET Architecture November 2007 and to be MANET-aware. The MANET WG is chartered to develop routing protocols for MANET qqq interfaces. The Autoconf WG is chartered to develop autoconfiguration protocols for MANET qqq interfaces and = MANET routers. Teco: only address autoconfiguration protocols! Note that this addressing framework is similar to how routing in the existing Internet is structured. Routers run their routing protocol over router interconnects with various characteristics to which only the routing protocols are privy. On the other hand, hosts connect to routers over qqq interfaces with well-defined characteristics. 6. MANETs' Place in the Network Stack ------=_NextPart_000_0025_01C8F2F6.45B07D10 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf ------=_NextPart_000_0025_01C8F2F6.45B07D10-- From autoconf-bounces@ietf.org Thu Jul 31 01:33:55 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8353E3A68AE; Thu, 31 Jul 2008 01:33:55 -0700 (PDT) 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 105C33A6840 for ; Thu, 31 Jul 2008 01:33:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.466 X-Spam-Level: X-Spam-Status: No, score=-5.466 tagged_above=-999 required=5 tests=[AWL=0.233, 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 SPLqGbZqcl+k for ; Thu, 31 Jul 2008 01:33:52 -0700 (PDT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 81EDA3A6780 for ; Thu, 31 Jul 2008 01:33:52 -0700 (PDT) Received: from [130.129.23.64] (unknown [130.129.23.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id 627227F9250 for ; Thu, 31 Jul 2008 10:33:55 +0200 (CEST) From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano To: autoconf@ietf.org Organization: Universidad Carlos III de Madrid Date: Thu, 31 Jul 2008 10:32:31 +0200 Message-Id: <1217493151.4903.21.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Subject: [Autoconf] Dave Thaler's presentation at intarea meeting 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1052271077==" Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org --===============1052271077== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-V70r3Z3DWWHKGCsvRaI1" --=-V70r3Z3DWWHKGCsvRaI1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable http://www3.ietf.org/proceedings/08jul/slides/intarea-2.pdf http://tools.ietf.org/html/draft-thaler-ip-model-evolution very interesting IMHO, might be helpful -- for the MANET link discussion we are currently having -- to take a look at it. Regards, Carlos --=20 Carlos Jes=FAs Bernardos Cano http://www.netcoms.net GPG FP: D29B 0A6A 639A A561 93CA 4D55 35DC BA4D D170 4F67 --=-V70r3Z3DWWHKGCsvRaI1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkiReJ8ACgkQNdy6TdFwT2d2cACeMjNuo51JCZitvD5DbNOnDUun 76oAnjxXLwBc2LaPYQYF1uqY4nqJp8AU =GWdB -----END PGP SIGNATURE----- --=-V70r3Z3DWWHKGCsvRaI1-- --===============1052271077== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf --===============1052271077==-- From autoconf-bounces@ietf.org Thu Jul 31 04:32:58 2008 Return-Path: X-Original-To: autoconf-archive@megatron.ietf.org Delivered-To: ietfarch-autoconf-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9027928C17F; Thu, 31 Jul 2008 04:32:58 -0700 (PDT) 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 4BB5228C171 for ; Thu, 31 Jul 2008 04:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.275 X-Spam-Level: X-Spam-Status: No, score=-0.275 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599, 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 xFgqywrNyFBE for ; Thu, 31 Jul 2008 04:32:56 -0700 (PDT) Received: from server9.hosting2go.nl (server9.hosting2go.nl [83.137.194.84]) by core3.amsl.com (Postfix) with ESMTP id 7768B28C162 for ; Thu, 31 Jul 2008 04:32:54 -0700 (PDT) Received: (qmail 27586 invoked from network); 31 Jul 2008 13:33:06 +0200 Received: from unknown (HELO M90Teco) (130.129.21.55) by server9.hosting2go.nl with SMTP; 31 Jul 2008 13:33:06 +0200 From: "Teco Boot" To: "'Ian Chakeres'" , "'Thomas Clausen'" , "'Christopher Dearlove'" , , , , Date: Thu, 31 Jul 2008 13:32:36 +0200 Message-ID: <004801c8f301$34adee70$9e09cb50$@nl> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjzASF3A6V75277QrebUqGvrK6KMg== Content-Language: nl Cc: autoconf@ietf.org Subject: [Autoconf] IPv6 addresses used for MANET protocols X-BeenThere: autoconf@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Ad-Hoc Network Autoconfiguration WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: autoconf-bounces@ietf.org Errors-To: autoconf-bounces@ietf.org Dear authors of the MANET protocol documents, I want your opinion on IPv6 source addresses used for std MANET protocols (DYMO/OLSRv2/PacketBB). The current documents do not specify this, maybe for being neutral on v4 / v6 or not burning your hands. IMHO LL addresses are appropriate, as to my knowledge all existing IPv6 IGP routing protocols use these and packets are send single hop only. There MUST be very good reasons to deviate, and even then we SHOULD think twice before proposing something like that. Are we 100% sure all packets are single hop? Using LL when a message is sent multihop could be possible when using /128 LL prefixes, but this is something I dislike. I would use a ULA for this. Using LL as unique addresses in a MANET (globally unique link local addresses) is OK only if InterfaceID's are globally unique (u=1, as specified in rfc4291). For other LL addresses we could use fully random InterfaceID's and take an extremely low risk on duplicate. Passive DAD reduces change on collisions, and we could think on address spoofing protection (e.g. SeND or something like that). This is applicable also for globally unique link local addresses, if someone needs this. Regards, Teco _______________________________________________ Autoconf mailing list Autoconf@ietf.org https://www.ietf.org/mailman/listinfo/autoconf